So this evening decided to go back to CM11 after using stock for a while on my N4. So I downloaded the latest CM11 nightly, along with the latest PA gapps. I did a full wipe in recovery, then flashed CM11, followed by a flash of the gapps. However, it immediately appeared that the gapps file must have been bad (gave me the red exclamation triangle android background). So rebooting leaves me in a endless bootloop. Only problem is I don't have another gapps file saved on my SDcard. And to make matters worse (yeah I know) I didn't nandroid my system prior to this, though I do have everything (apps, etc) saved on my SDcard. Now my problem is, I need to find a way of loading a new gapps file onto my phone. I have tried ADB, but I suspect that as a result of the factory reset I no longer have USB debugging on, as I can't connect to the device in ADB. I am becoming more than a little stressed right now, as I need to get this phone back up and running. Does anyone have any idea what I might do next?? I am not a total newbie to flashing roms, been at it a few years now, but this is the first time I've been stuck like this. Ugh! Please help! :crying::crying::crying:
joeski27 said:
So this evening decided to go back to CM11 after using stock for a while on my N4. So I downloaded the latest CM11 nightly, along with the latest PA gapps. I did a full wipe in recovery, then flashed CM11, followed by a flash of the gapps. However, it immediately appeared that the gapps file must have been bad (gave me the red exclamation triangle android background). So rebooting leaves me in a endless bootloop. Only problem is I don't have another gapps file saved on my SDcard. And to make matters worse (yeah I know) I didn't nandroid my system prior to this, though I do have everything (apps, etc) saved on my SDcard. Now my problem is, I need to find a way of loading a new gapps file onto my phone. I have tried ADB, but I suspect that as a result of the factory reset I no longer have USB debugging on, as I can't connect to the device in ADB. I am becoming more than a little stressed right now, as I need to get this phone back up and running. Does anyone have any idea what I might do next?? I am not a total newbie to flashing roms, been at it a few years now, but this is the first time I've been stuck like this. Ugh! Please help! :crying::crying::crying:
Click to expand...
Click to collapse
Nobody has a suggestion? This isn't looking good...
What is strange to me is, even after doing another factory reset, it still boots to the same CM boot screen and is stuck in a boot loop. I have no idea what is going on here. And at the very least, at least I have everything still on my SDcard (backups of apps in TB, and all my other locally saved stuff...just that now I have no idea of how to get to any of it, or how to load on a working rom & gapps so I can have something to boot to!)
Do a full wipe, flash CM11 without Gapps. It should boot but you won't be able to sign in to google and all that jazz. Just use the browser and download another gapps, then flash it.
Your computer won't detect ADB because ADB is only when android is running. If you're running a sideload-enabled recovery, you can push a zip and flash it through ADB.
exb0 said:
Do a full wipe, flash CM11 without Gapps. It should boot but you won't be able to sign in to google and all that jazz. Just use the browser and download another gapps, then flash it.
Your computer won't detect ADB because ADB is only when android is running. If you're running a sideload-enabled recovery, you can push a zip and flash it through ADB.
Click to expand...
Click to collapse
I've tried this now (wipe, and then flash of CM) and its STILL stuck at the damn CM boot animation. I just don't understand what the problem is here. I have never, ever had something like this happen before. Could it be a bad nightly? And if so, how the hell am I going to get another flashable rom onto my SDcard??
joeski27 said:
I've tried this now (wipe, and then flash of CM) and its STILL stuck at the damn CM boot animation. I just don't understand what the problem is here. I have never, ever had something like this happen before. Could it be a bad nightly? And if so, how the hell am I going to get another flashable rom onto my SDcard??
Click to expand...
Click to collapse
Hmmm, yeah it could be.
1 : Download a ROM. Check the MD5 checksum.
2 : Copy the ROM to your ADB folder and rename it to something easy (eg: Rom.zip)
3 : Fire up CMD, Navigate it to your ADB folder
4 : Boot your phone into recovery, find for a function called "ADB Sideload" or something along those lines.
5 : In CMD, type in "adb sideload *romname*.zip
6 : ??
7 : Enjoice.
This can be done for any type of flashable files.
or yknow. just return back to stock and do everything all again if you're uncomfortable doing this.
exb0 said:
Hmmm, yeah it could be.
1 : Download a ROM. Check the MD5 checksum.
2 : Copy the ROM to your ADB folder and rename it to something easy (eg: Rom.zip)
3 : Fire up CMD, Navigate it to your ADB folder
4 : Boot your phone into recovery, find for a function called "ADB Sideload" or something along those lines.
5 : In CMD, type in "adb sideload *romname*.zip
6 : ??
7 : Enjoice.
This can be done for any type of flashable files.
or yknow. just return back to stock and do everything all again if you're uncomfortable doing this.
Click to expand...
Click to collapse
So I don't know if anything is different, but I am doing this on a Mac running Mavericks. But I do have the latest SDK installed with a fresh download of tools. I am running CMW recovery 6.0.4.3, which does have sideload, and I attempted to use it a moment ago but it didn't work....will try again now...
joeski27 said:
So I don't know if anything is different, but I am doing this on a Mac running Mavericks. But I do have the latest SDK installed with a fresh download of tools. I am running CMW recovery 6.0.4.3, which does have sideload, and I attempted to use it a moment ago but it didn't work....will try again now...
Click to expand...
Click to collapse
Ah, it shouldn't matter that much. Instead of CMD just use terminal(that's what it's called in OSX right?).
didn't work? what error did you get?
joeski27 said:
So I don't know if anything is different, but I am doing this on a Mac running Mavericks. But I do have the latest SDK installed with a fresh download of tools. I am running CMW recovery 6.0.4.3, which does have sideload, and I attempted to use it a moment ago but it didn't work....will try again now...
Click to expand...
Click to collapse
Yeah its not working, just brings up the splash of command prompts that comes up with you don't enter a proper adb command.
joeski27 said:
Yeah its not working, just brings up the splash of command prompts that comes up with you don't enter a proper adb command.
Click to expand...
Click to collapse
Enable sideload on your phone and then try using "adb devices", do you get anything? or random splash of commands again?
exb0 said:
Enable sideload on your phone and then try using "adb devices", do you get anything? or random splash of commands again?
Click to expand...
Click to collapse
No that's what I've been countering the whole time; I have ADB sideload set on the phone, and then after cd'ing my way to the folder with adb, I try "adb devices" and nothing, doesn't see the device at all. WTF?
joeski27 said:
No that's what I've been countering the whole time; I have ADB sideload set on the phone, and then after cd'ing my way to the folder with adb, I try "adb devices" and nothing, doesn't see the device at all. WTF?
Click to expand...
Click to collapse
sounds like a driver issue. You're gonna have to fix that or there's almost no way of fixing your phone :/
Hang on....sideload looks like its working! But I ain't out of the woods yet, won't celebrate til it gets there, AND if it boots...
Now I guess the best bet is to try a fresh rom rather than a fresh gapps, would you say? I'm downloading both now, just wondered which would be my best bet. I mean at this point I just need something that will allow me to boot.'
By the way when a sideload is performed where is the sideloaded file saved? Just wondering where to find it when the time comes to flash.
joeski27 said:
Hang on....sideload looks like its working! But I ain't out of the woods yet, won't celebrate til it gets there, AND if it boots...
Click to expand...
Click to collapse
#prayforjoeski27 goodluck!
---------- Post added at 05:38 AM ---------- Previous post was at 05:37 AM ----------
joeski27 said:
Now I guess the best bet is to try a fresh rom rather than a fresh gapps, would you say? I'm downloading both now, just wondered which would be my best bet. I mean at this point I just need something that will allow me to boot.
Click to expand...
Click to collapse
try flashing a rom without gapps first. if the rom boots then wipe and reflash rom with gapps.
exb0 said:
#prayforjoeski27 goodluck!
---------- Post added at 05:38 AM ---------- Previous post was at 05:37 AM ----------
try flashing a rom without gapps first. if the rom boots then wipe and reflash rom with gapps.
Click to expand...
Click to collapse
Sounds like a plan. This time I'm loading the latest snapshot release of CM rather than the damn nightly, lol. At least we know that that version *should* reliably boot up....and we'll know shortly...going to save the rom to the appropriate folder, rename, and sideload....
joeski27 said:
Sounds like a plan. This time I'm loading the latest snapshot release of CM rather than the damn nightly, lol. At least we know that that version *should* reliably boot up....and we'll know shortly...going to save the rom to the appropriate folder, rename, and sideload....
Click to expand...
Click to collapse
I think all nightlies should boot up (i mean it IS cyanogen mod...). I think you just got a bad download. Remember to check MD5 if it's available!
exb0 said:
I think all nightlies should boot up (i mean it IS cyanogen mod...). I think you just got a bad download. Remember to check MD5 if it's available!
Click to expand...
Click to collapse
WOO HOO! Friggin thing booted, baby! Hello CM welcome screen! Never looked so beautiful!
So now I just need to 1) get a fresh gapps, 2) load it on to my SD via android file transfer, do a fresh wipe in recovery, flash CM again, followed by the fresh gapps, and I should be in business...yes?
joeski27 said:
WOO HOO! Friggin thing booted, baby! Hello CM welcome screen! Never looked so beautiful!
So now I just need to 1) get a fresh gapps, 2) load it on to my SD via android file transfer, do a fresh wipe in recovery, flash CM again, followed by the fresh gapps, and I should be in business...yes?
Click to expand...
Click to collapse
Congrats!
You can try just flashing gapps on top of it, that's what I do. but if you're worried you can do a full wipe and flash it again. Completely up to you!
exb0 said:
Congrats!
You can try just flashing gapps on top of it, that's what I do. but if you're worried you can do a full wipe and flash it again. Completely up to you!
Click to expand...
Click to collapse
Hey thanks a million for the help on this one! Like I said, I've done quite a bit with rom tinkering over the last few years, but sideloading was a first for me tonight. Though it is very good to know for the future! More importantly, however (and this is really not like me) in the future I either A) have to make sure I have enough SD space for nandriods, or B) keep a previous, working zip of a rom on the SD when I go to flash a new one (which is what I have always done but have not recently).
Again, thanks a bunch!!!! :highfive:
joeski27 said:
Hey thanks a million for the help on this one! Like I said, I've done quite a bit with rom tinkering over the last few years, but sideloading was a first for me tonight. Though it is very good to know for the future! More importantly, however (and this is really not like me) in the future I either A) have to make sure I have enough SD space for nandriods, or B) keep a previous, working zip of a rom on the SD when I go to flash a new one (which is what I have always done but have not recently).
Again, thanks a bunch!!!! :highfive:
Click to expand...
Click to collapse
No problem as long as you're willing to learn I'm willing to help! if you ever run into any other problems feel free to PM me. I'll try to help as much as I can. :good:
Related
I seem to have messed up the process. I successfully unlocked and rooted my Nexus 7 but during wipe process using JROM flasher something didn't go right and now I'm stuck at the google logo screen forever. I can boot into fast recovery mode but that's about it. I can't do anything.
I've had this done before on my nexus phone but it seems I managed to f it up this time.
I thought I had a rom zip file copied on to the Nexus 7 but it doesn't show in the menu. Now I'm stuck at the logo screen not having access to any roms to install. How do I reset all of this to factory? I've already checked most of the threads regarding this and haven't been able to find a solution yet.
calavera-pw said:
I seem to have messed up the process. I successfully unlocked and rooted my Nexus 7 but during wipe process using JROM flasher something didn't go right and now I'm stuck at the google logo screen forever. I can boot into fast recovery mode but that's about it. I can't do anything.
I've had this done before on my nexus phone but it seems I managed to f it up this time.
I thought I had a rom zip file copied on to the Nexus 7 but it doesn't show in the menu. Now I'm stuck at the logo screen not having access to any roms to install. How do I reset all of this to factory? I've already checked most of the threads regarding this and haven't been able to find a solution yet.
Click to expand...
Click to collapse
before you do anything, use your recovery to see if the rom zip is located in /data/media/0/. if its there, flash it from that location.
Are you able to boot into recovery?
If yes, it could be as simple as plugging your tablet into the computer and mounting the usb, drag and drop the rom, and flash it without using a toolkit (only recovery). I'm not familiar with jrom flasher, but i will say the more variables there are, the more chance of a problem.
If no, you're best off running the stock factory image through your computer, found here: https://developers.google.com/android/nexus/images#nakasi. I had your problem at one point, and could not even boot into recovery. After trying to install cwm through adb (which failed), and a number of toolkits, the factory image was what brought my nexus back to life.
I remember reading that sometimes a wipe can delete your recovery as well as your system (and whatever else you have on your n7), although i dont know if that was ever fixed, as i got my tab replaced a month or two ago and havent rooted it again yet. There was some type of command or .zip or something that should be used to keep recovery after wipes. When i expirienced problems such as yours, it was also from a bad wipe from a toolkit. Using just the recovery afterwards, i never expirienced any issues, even without the recovery fix.
I would definitely try simms suggestion first if you can access recovery. If that fails, try one of the above processes.
PS, even if you can access recovery, if at this point you just want to go completely stock, the factory image will work regardless.
cheers
Thanks for the help guys, I've been struggling for the past 3~4 hours but I found a solution.
What I did was use JROMFlasher and upload a rom zip to the sdcard directly and go from there.
calavera-pw said:
Thanks for the help guys, I've been struggling for the past 3~4 hours but I found a solution.
What I did was use JROMFlasher and upload a rom zip to the sdcard directly and go from there.
Click to expand...
Click to collapse
Guys..I have the similar problem..I am not able to upload rom zip to sdcard using JROMFlasher..Also USB mounting is not working for me ..
Is there any other way to move ROM to sdcard?:crying:
appoos said:
Guys..I have the similar problem..I am not able to upload rom zip to sdcard using JROMFlasher..Also USB mounting is not working for me ..
Is there any other way to move ROM to sdcard?:crying:
Click to expand...
Click to collapse
ADB
Sent from my Galaxy Nexus
Pirateghost said:
ADB
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
This dint work in my windows 8
appoos said:
This dint work in my windows 8
Click to expand...
Click to collapse
You're holding it wrong. ADB works on my Win8 machine
Pirateghost said:
You're holding it wrong. ADB works on my Win8 machine
Click to expand...
Click to collapse
can you tell me the procedure..
appoos said:
can you tell me the procedure..
Click to expand...
Click to collapse
no.
in the other thread that YOU created, you were given links to follow and the instructions are already there. i dont hold hands
I could do it with ADB..thanks guys
hello,
i checked all over the forums and i didn't find any solution for my problem
i wanted to install a new version of slim mako update, but first i wanted to wipe ALL my nexus 4
so i entered to CWM--> mount and storage--> and " format system, format data, format cache, format sdcard".
basically i deleted all my phone files, and now when i turning it on i see only the google logo and no any change.
please someone help me
thanks for the helpers :highfive:
Push ROM with adb or flash factory image with fastboot.
Sent from my Nexus 4 using Tapatalk 4 Beta
El Daddy said:
Push ROM with adb or flash factory image with fastboot.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
thanks for your fast help
can you please tell me how to that?or put me a link for how doing that?
because i searching and can't find how to do it, and i tried something that i found and its not working
thanks again
EDIT:
i pushed the rom with that guide http://forum.xda-developers.com/showthread.php?t=1995688
but i still has nothing that i can do to flash the rom.
please help me
SherDroidx said:
thanks for your fast help
can you please tell me how to that?or put me a link for how doing that?
because i searching and can't find how to do it, and i tried something that i found and its not working
thanks again
EDIT:
i pushed the rom with that guide http://forum.xda-developers.com/showthread.php?t=1995688
but i still has nothing that i can do to flash the rom.
please help me
Click to expand...
Click to collapse
use adb to push the rom to your phone. search XDA on how to set up and use ADB, its quite simple, you need the android sdk dev kit installed, and its just a few commands to push the rom to your phone.
ScumDroid said:
use adb to push the rom to your phone. search XDA on how to set up and use ADB, its quite simple, you need the android sdk dev kit installed, and its just a few commands to push the rom to your phone.
Click to expand...
Click to collapse
thanks for help
can you kindly post for me the links?
because i tried to push the rom and succeed but when i click install rom from zip(from recovery)
it says that the folder empty.
and now i'm very confused and upset, so if you can please post some links
very appreciate your help!!!
SherDroidx said:
thanks for help
can you kindly post for me the links?
because i tried to push the rom and succeed but when i click install rom from zip(from recovery)
it says that the folder empty.
and now i'm very confused and upset, so if you can please post some links
very appreciate your help!!!
Click to expand...
Click to collapse
ill be home from work in a few hours, ill help you then.
SherDroidx said:
hello,
i checked all over the forums and i didn't find any solution for my problem
i wanted to install a new version of slim mako update, but first i wanted to wipe ALL my nexus 4
so i entered to CWM--> mount and storage--> and " format system, format data, format cache, format sdcard".
basically i deleted all my phone files, and now when i turning it on i see only the google logo and no any change.
please someone help me
thanks for the helpers :highfive:
Click to expand...
Click to collapse
I assume you are using Windows and know how to get into the bootloader.
1. Download the adt-bundle for your OS from here: http://http://developer.android.com/sdk/index.html#download
2. Unzip it.
3. Start cmd.
4. Connect your phone to the computer via USB.
5. Using cmd, use the command "cd" (change directory) to change directory to the one where your unzipped files are. You can find out where they are by copying the adress that is shown when you are looking at the files in the file explorer (the icon next to the forward-arrow).
6. Boot up your phone to the bootloader. Then boot to the recovery.
7. Download a ROM of choice to your computer.
8. In cmd type "adb devices". IF it says that your device is offline then type "adb usb reboot".
9. Type "adb push ROM-NAME.zip /sdcard/0/ROM-NAME.zip"
10. Flash the ROM.
I have this problem too phone won't boot past the Google logo still have recovery still have my ROM zip on internal storage is there no way to fix this in recovery? does anyone know what causes this problem?
verniqu scotch
many thanks for your kindness and help appreciate it so much!!!
i tried what you said, i had a progress but no.
the phone shows me the logo of google, and then the logo of slimbean rom that i flashed(of any other rom), i have waited for more a half hour
and it stuck on the rom logo and no change
i tried flash rom from sideload (cmd--> adb sideload rom-name.zip) the phone shows me a progress and successful at end, but nothing after.
is that mean my phone can't be restored any more?
and thanks again for your kindness
SherDroidx said:
many thanks for your kindness and help appreciate it so much!!!
i tried what you said, i had a progress but no.
the phone shows me the logo of google, and then the logo of slimbean rom that i flashed(of any other rom), i have waited for more a half hour
and it stuck on the rom logo and no change
i tried flash rom from sideload (cmd--> adb sideload rom-name.zip) the phone shows me a progress and successful at end, but nothing after.
is that mean my phone can't be restored any more?
and thanks again for your kindness
Click to expand...
Click to collapse
Have you actually wiped (factory reset, NOT wiped the sd-card) the phone before flashing the ROM? It seems to me like the problem is either that you didn't wipe or that the ROM is faulty. Try with another ROM.
Your other two options are to either try with some other ROM:s or just restore back to stock.
i have wipe everything on phone- factory/cache/dalvik, format sdcard/data/system/mount
i tried several roms, slimbean, cyanogen, aokp, but no one of them works,
i tried to flash google original image(Factory Images "occam" for Nexus 4 from google site) but it stuck on the nexus x logo and nothing more,
mil0X said:
Have you actually wiped (factory reset, NOT wiped the sd-card) the phone before flashing the ROM? It seems to me like the problem is either that you didn't wipe or that the ROM is faulty. Try with another ROM.
Your other two options are to either try with some other ROM:s or just restore back to stock.
Click to expand...
Click to collapse
i have wipe everything on phone- factory/cache/dalvik, format sdcard/data/system/mount
i tried several roms, slimbean, cyanogen, aokp, but no one of them works,
i tried to flash google original image(Factory Images "occam" for Nexus 4 from google site) but it stuck on the nexus x logo and nothing more,
I've heard ranting and raving about Malladus and I decided to flash it yesterday. It won't take the flash no matter what I do.
I've tried: Flashing 1.2.4, downloading both again to make sure it wasn't a download issue, using different gapps package, using a different lg apps package, using CWM, using TWRP, side-loading... ETC
Bottom line: My phone will not take the ROM. It flashes the LG logo and gets stuck at a black screen where the back-light is on but nothing is displayed on the screen.
I am an experienced flasher and I have no idea what is going on. I am backed up and can get into TWRP to restore so I am all good as far as not being bricked goes but I really want to try out this damn rom.
Any help would be much appreciated. Thanks.
Bump I'm having the same problem, I'm on Verizon.
NBushyy said:
Bump I'm having the same problem, I'm on Verizon.
Click to expand...
Click to collapse
Yeah same here. Verizon. Forgot to mention it.
Still a problem. Bumping.
I am in the boat with you. I thought it was just me.
Same Black Screen issue
Did anyone have any luck resolving this? Ive tried with both twrp and cwm and same issue...?
Same problem on my Verizon model. Using twrp 2.6.3.3. Other roms work fine.
How long have you left it at the black screen? Sometimes a fresh load can take up to 10 minutes.
Also, the rom will work without gapps and lgapps, so try just loading the rom. I know you downloaded twice, but did you check the md5 sum either time?
heleos said:
How long have you left it at the black screen? Sometimes a fresh load can take up to 10 minutes.
Also, the rom will work without gapps and lgapps, so try just loading the rom. I know you downloaded twice, but did you check the md5 sum either time?
Click to expand...
Click to collapse
I left it there for a good 15 minutes. I also had it plugged into my laptop. It kept detecting the phone as plugged in. Seems like it is stuck in a bootloop or something. I also tried installing only the ROM without the gapps and lgapps and had the same result. I also checked the MD5 sum and it matched. (I know I'm kinda hijacking this original post, but I think we are all having the exact same issue)
try this
trackstar1414 said:
I left it there for a good 15 minutes. I also had it plugged into my laptop. It kept detecting the phone as plugged in. Seems like it is stuck in a bootloop or something. I also tried installing only the ROM without the gapps and lgapps and had the same result. I also checked the MD5 sum and it matched. (I know I'm kinda hijacking this original post, but I think we are all having the exact same issue)
Click to expand...
Click to collapse
Can you restore your nandroid and flash say, CleanROM 1.0 or DigitalDream 2.1? OR try this:
1. Hold the power button until the device is OFF.
2. Download LG drivers to the PC (LG VZW_United_WHQL_v2.11.1) and LG mobile support tool (B2CAppSetup).
3. Install these packages.
4. Plug in you USB cable into the phone but not the computer.
5. Hold volume up and insert the USB cable to the PC- the phone should boot to 'download mode'.
6. Open the support tool and click Options>Upgrade Recovery, follow the prompts.
7. At the first prompt indentify your phone using IMEI/ESN, then click OK
8. Let it do its thing, the phone will reboot and most likely have a bunch of error messages and some FC's. Just hit okay to all messages, the phone will settle after 2 minutes or so.
9. Download freegee from market and reflash recovery of your choice.
10. Make sure you have a ROM saved to the SD to flash
11. Use freegee to reboot to recovery
12. Once in recovery you can reflash the ROM as normal.
13. Reboot and Profit!
*$* Or you could go back to Stock and start fresh!
*$* BEFORE ANY FLASH ALWAYS STOP and MAKE A NANDROID BACKUP!
Good Luck and if you get stuck let me know
geosnipe said:
Can you restore your nandroid and flash say, CleanROM 1.0 or DigitalDream 2.1? OR try this:
1. Hold the power button until the device is OFF.
2. Download LG drivers to the PC (LG VZW_United_WHQL_v2.11.1) and LG mobile support tool (B2CAppSetup).
3. Install these packages.
4. Plug in you USB cable into the phone but not the computer.
5. Hold volume up and insert the USB cable to the PC- the phone should boot to 'download mode'.
6. Open the support tool and click Options>Upgrade Recovery, follow the prompts.
7. At the first prompt indentify your phone using IMEI/ESN, then click OK
8. Let it do its thing, the phone will reboot and most likely have a bunch of error messages and some FC's. Just hit okay to all messages, the phone will settle after 2 minutes or so.
9. Download freegee from market and reflash recovery of your choice.
10. Make sure you have a ROM saved to the SD to flash
11. Use freegee to reboot to recovery
12. Once in recovery you can reflash the ROM as normal.
13. Reboot and Profit!
*$* Or you could go back to Stock and start fresh!
*$* BEFORE ANY FLASH ALWAYS STOP and MAKE A NANDROID BACKUP!
Good Luck and if you get stuck let me know
Click to expand...
Click to collapse
I am able to restore my nandroid backup so I'm not completely stuck without a phone. I will try flashing one of the other ROMs and see how it goes now. Thanks for the help so far.
trackstar1414 said:
I am able to restore my nandroid backup so I'm not completely stuck without a phone. I will try flashing one of the other ROMs and see how it goes now. Thanks for the help so far.
Click to expand...
Click to collapse
I was able to install the digital dream rom without any issue. At this point I think its the sequence I did everything. I did the latest ota before installing any Recovery. I used the loki method to install the recovery. In looking at all the roms, it appears that malladus may not be "loki patched" for people already on 12b? Other roms I have tried mention that so thats why I'm speculating this. I am by no means a developer so I might be out in left field on this one. I guess I'll stick with stock or another ROM for now until his next update.
It also looks like people are discussing this on the main ROM forum as well so hopefully it will work in the future.
Thanks again for the help and suggestions.
trackstar1414, say thanks by using the "Thanks' button like this.. keep me informed, CHEERS!
trackstar1414 said:
I was able to install the digital dream rom without any issue. At this point I think its the sequence I did everything. I did the latest ota before installing any Recovery. I used the loki method to install the recovery. In looking at all the roms, it appears that malladus may not be "loki patched" for people already on 12b? Other roms I have tried mention that so thats why I'm speculating this. I am by no means a developer so I might be out in left field on this one. I guess I'll stick with stock or another ROM for now until his next update.
It also looks like people are discussing this on the main ROM forum as well so hopefully it will work in the future.
Thanks again for the help and suggestions.
Click to expand...
Click to collapse
Wanted to share this if you haven't read it..
http://forum.xda-developers.com/showthread.php?t=2449670
I had issues originally and had to flash back to 1.2.3.
What I ended up doing was switching to CWM 6.0.4.4 ( I was using TWRP 2.6.3.3).
His boot skipped the set up wizard as well, which was odd.
His was also the only ROM I ever got stuck on the fastboot screen while using twrp.
Try ( at your own risk obviously) flashing back to an older malladus (wipe all and boot till you get through the set up wizard),
Then back to recovery, do a wipe, without wiping the system partition, Data Cache and Davlik, and flash back to 1.2.5.
I didn't try it on 1.2.5. But that's how I got into 1.2.4.
Srvisg0d said:
I've heard ranting and raving about Malladus and I decided to flash it yesterday. It won't take the flash no matter what I do.
I've tried: Flashing 1.2.4, downloading both again to make sure it wasn't a download issue, using different gapps package, using a different lg apps package, using CWM, using TWRP, side-loading... ETC
Bottom line: My phone will not take the ROM. It flashes the LG logo and gets stuck at a black screen where the back-light is on but nothing is displayed on the screen.
I am an experienced flasher and I have no idea what is going on. I am backed up and can get into TWRP to restore so I am all good as far as not being bricked goes but I really want to try out this damn rom.
Any help would be much appreciated. Thanks.
Click to expand...
Click to collapse
Are you on 12B OTA? If so, that would be your issue. I took the 12B OTA and tried flashing Malladus and got the same issue you have. You can revert your phone to 11A and that should resolve your issue. http://forum.xda-developers.com/showthread.php?t=2448960 it will erase everything on your phone and go back to unroot.
Hey guys,
I've known about this whole modding thingy going on for android phones, and i've decided to give it a shot myself.
I took a backup of everything (copied everything.. didn't use any app for that. not too smart of me..)
Anyway,
I looked around and decided to install Hells Core kernel on my phone, along with Cyanogen Mod.
So after installing the SDK on my computer, unlocking the phone, rooting the phone with SuperSU and Clockwork Mod,
I got to installing the kernel.
I put it on my phone, rebooted into recovery mode, reset all data (dalvik cache and all..)
then I installed the kernel from a zip file I put on the phone, and it all went smoothly.
However, when I reboot my phone - it's all messed up!
The screen is all half yellow, and half is just black - not even text.
In the yellow part, you can hardly tell that it's the first welcome screen - because the text is too big to fit the screen.
Anyway, the whole phone is fk3d up.
I just wanna put it back to the original stock kernel and rom...
How do I do that now?
Thanks a lot guys..
This is urgent >_<
Just flash cm again without doing any wipes. It'll get rid of the kernel
Sent from my Nexus 5
jd1639 said:
Just flash cm again without doing any wipes. It'll get rid of the kernel
Sent from my Nexus 5
Click to expand...
Click to collapse
I haven't got CM on my phone,
and I can't connect it to the computer because it needs get past the welcome screen - which I can't click on any buttons!
****EDIT ****
nvm, I managed to do it
I used android toolkit, and now the computer can access the phone's internal memory.
Thanks!
***** EDIT #2 ******
Nop, doesn't work yet...
when I copy the other kernels zip's, everything seems okay
but when I reboot my nexus to install from the recovery mode, the zip are corrupted - and when I access from my computer it shows they're 0 bytes.
as if nothing was copied..
What can I do ???
***** EDIT #3 ******
Well, managed to get the phone to work!
Not getting anywhere near Hellscore now..
What I did was run 'install zip from sideload', and then from the pc I used 'adb sideload <FRANCOROCKS>.zip', and that worked
Phone's now up and running, installing my apps again.. lol
Scared to change the ROM though.. after all this >_<
capzul said:
I haven't got CM on my phone,
and I can't connect it to the computer because it needs get past the welcome screen - which I can't click on any buttons!
****EDIT ****
nvm, I managed to do it
I used android toolkit, and now the computer can access the phone's internal memory.
Thanks!
***** EDIT #2 ******
Nop, doesn't work yet...
when I copy the other kernels zip's, everything seems okay
but when I reboot my nexus to install from the recovery mode, the zip are corrupted - and when I access from my computer it shows they're 0 bytes.
as if nothing was copied..
What can I do ???
***** EDIT #3 ******
Well, managed to get the phone to work!
Not getting anywhere near Hellscore now..
What I did was run 'install zip from sideload', and then from the pc I used 'adb sideload <FRANCOROCKS>.zip', and that worked
Phone's now up and running, installing my apps again.. lol
Scared to change the ROM though.. after all this >_<
Click to expand...
Click to collapse
Because you did all this the wrong way. Learn and study before flashing anything, it's not about some simple zip flash. that simple zip file can brick your phone if flashed without knowledge.
hells core kernal is not a CM based kernal that's why you got broken screen. there is a separate thread for cm based kernals. do flash a custom rom like Mahdi slimkat etc they offer great features but only after fully understanding what you are doing
hassi4042 said:
Because you did all this the wrong way. Learn and study before flashing anything, it's not about some simple zip flash. that simple zip file can brick your phone if flashed without knowledge.
hells core kernal is not a CM based kernal that's why you got broken screen. there is a separate thread for cm based kernals. do flash a custom rom like Mahdi slimkat etc they offer great features but only after fully understanding what you are doing
Click to expand...
Click to collapse
Well, I flashed the kernel before I put the ROM, so this happened with HC kernel on stock ROM.
:X
you probably flashed the wrong version of the kernel
You did get the CM Version of Hells Core, right?
This happens to me all the time, just reflash the Roms .zip and you'll be fine.
Sorry to say that, but from your comments it's obvious that you messed up with wrong kernel's version and is not a fault of this specific kernel.
Also the zero kb downloads show bad downloads on your side again.
Sent from my ONDA A9 Core4
capzul said:
Hey guys,
I've known about this whole modding thingy going on for android phones,
Click to expand...
Click to collapse
Lol
Sent from my Nexus 4 using Tapatalk
Hello, this is my first post here and I have searched for a similar post or issue but have been unsuccessful finding anything.
Please forgive me if I have posted in the wrong area, missed a solution somewhere and/or have not explained anything correctly/clearly.
My Nexus 7 (2012) (I installed Cyanogen on it (and updated it once) through their installer and it has run perfectly for months) started rebooting randomly one morning. I turn it on and it seems to be normal, then it will suddenly reboot. The time between reboots varies ranging from 30 seconds to a few minutes. I can not install or update any apps and any settings changed are reset back to what they were previously upon reboot. I have tried a factory reset and while it appears to wipe everything (all caches and data) when I reboot it is the same as before the reset (I also receive this message (after all other processes are complete) during the data wipe "E: unknown volume "/sdcard/.android_secure" "). I am able to turn on developer options but then the random reboot occurs and it is turned off. I have plugged it to my computer and see it listed, but can not access anything on it.
My intention is to wipe it using my computer (fastboot?) but I am at a standstill due to the rebooting and being unable to turn on developer options.
Any ideas or suggestions would be greatly appreciated.
Have you tried flashing another ROM in recovery? Perhaps try to see if you can access the filesystem while in recovery or if the bootloader brings anything up on your computer.
kcipopnevets said:
Have you tried flashing another ROM in recovery? Perhaps try to see if you can access the filesystem while in recovery or if the bootloader brings anything up on your computer.
Click to expand...
Click to collapse
Thanks for the reply. Sorry for my delay in replying. I've been rather frustrated with this.
I flashed the official image (downloaded from the google site) using fastboot and it seemed to work as all messages said complete but when I rebooted, it was back to it's current state. I am at a loss. I also tried adb sideloading but that just hangs when it gets to installing. It does not reboot randomly when it is in recovery.
pdn190 said:
Thanks for the reply. Sorry for my delay in replying. I've been rather frustrated with this.
I flashed the official image (downloaded from the google site) using fastboot and it seemed to work as all messages said complete but when I rebooted, it was back to it's current state. I am at a loss. I also tried adb sideloading but that just hangs when it gets to installing. It does not reboot randomly when it is in recovery.
Click to expand...
Click to collapse
No worries!
So CyanogenMod is still installed? Oh my. Has anything at all changed? If you still have custom recovery installed, why not try a near stock ROM?
kcipopnevets said:
No worries!
So CyanogenMod is still installed? Oh my. Has anything at all changed? If you still have custom recovery installed, why not try a near stock ROM?
Click to expand...
Click to collapse
Yes. No matter what I do, when I reboot it's still Cyanogen. Being a semi-novice at this, I didn't backup the stock ROM I had before installing Cyanogen. It feels like a virus, but I pretty much installed the exact same apps on both my phone and tablet and the phone has been fine.
I used this image(nakasi kot49h). Should I try a earlier version?
Thank you.
pdn190 said:
Yes. No matter what I do, when I reboot it's still Cyanogen. Being a semi-novice at this, I didn't backup the stock ROM I had before installing Cyanogen. It feels like a virus, but I pretty much installed the exact same apps on both my phone and tablet and the phone has been fine.
I used this image(nakasi kot49h). Should I try a earlier version?
Thank you.
Click to expand...
Click to collapse
You can always try. Also make sure you check md5 before flashing, that may explain why stock didn't flash correctly.
And I still can't get anything to work. Most recently I tried using wugfresh and EVERYTHING works except when it writes bootloader.img at the start. I feel like I am close but then it reboots back to cyanogen. lol