I am fairly new to Android, but am comfortable with command line operation on other Unix systems, etc. I read every thread I can find on this, but did not find my problem described exactly (there are some similar problems), so here it is:
My phone is a GSM Galaxy Nexus, about a month old. I rooted and unlocked it right away using post 1 from this guide: [VZW/SPRINT/GSM][Guide] Ultimate Galaxy Nexus Guide (Unlock/Root/Flash Roms/FAQ) - thanks Jubakuba!
I did NOT use any of the toolkits or automated methods.
A couple of days ago, I decided to try loading another ROM. I read through post 2 of the above guide. I followed the instructions in that thread and flashed a Trinity ROM. The flash seemed to go fine, and completed normally, but when I rebooted the phone, it was stuck in the Google Lock screen bootloop. I was able to restore a nandroid to get it back to where it was before, and the phone operates normally, no resets, reboots, nada. I inquired in Jubakubas thread as well as in the Trinity ROM thread in the developers section, and got some suggestions, which I tried. None of them worked. I also tried flashing a few other ROMS, a CM9 ROM and the RASCREAM ROM, and they all do the same thing. I have tried flashing these without wiping data or cache or dalvik cache, wiping some of them and wiping all of them, and the results are always the same - boot loop, which I can restore using CWM recovery and my nandroid.
One of the posters in the developers forum suggested taking the phone back to unrooted stock condition, so I did that, using this thread: [HOW-TO] [GSM & CDMA] Convert to latest yakju/takju/mysid build / Return to stock - another excellent guide, which worked exactly as described.
After that, my phone was back to as new, and I had to go through the whole start-up and restore applications, etc. I made a new nandroid so that recovery would be relatively painless, etc. Not too tough. I then Rooted the phone (it was always unlocked) and tried flashing a ROM again, with exactly the same results. Again, I was able to restore my nandroid and get back to operational.
I guess my question at this point is what on earth could be causing this? Some of the threads on boot loops where peoples phones start to boot loop spontaneously suggest a hardware problem, but the fact that I have NEVER had a boot loop in a month of use while running 4.0.4 stock rooted and unlocked seems to point more toward software as the cause. I will say one thing - I am learning how to use CWM and the bootloader commands! But, I would really like to be able to use some custom ROMS, not that there is anything really wrong with stock - this is a great phone. But, please HELP!
Reflash bootloader and radio through fastboot and please describe exactly (!) how you are going about flashing a custom Rom after
Sent from my Galaxy Nexus using Tapatalk 2
d0msen said:
Reflash bootloader and radio through fastboot and please describe exactly (!) how you are going about flashing a custom Rom after
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Okay, I booted into fastboot mode, then flashed the bootloader (bootloader-maguro-primela03.img) and radio (radio-maguro-i9250xxla02.img). I rebooted the bootloader, then went into recovery mode. From recovery mode, I selected "Install zip from sd card", "Choose zip from sd card", then selected the zip file in the /Download folder "TNP1536-384-Alpha86b-4.7-lto.zip". It went through its' install and said "System successfully corrupted" at the end and "Install from sdcard complete." I went back to reboot system rom and rebooted. Now, it is not looping anymore, but just sitting at the Google lock screen for about 2 minutes now. I will wait a few more minutes to see if it boots the rest of the way or starts looping, etc.
Okay, it has been 5-6 minutes with no additional changes, so I am pulling the battery. Powering it on now results in the same boot loop as before, so I will need to boot into bootloader mode and restore my nandroid.
are you wiping data when you flash the rom?
if not, you need to do that first inside of cwm
I would let it sit longer before pulling the battery
Sent from my Galaxy Nexus using xda premium
Anytime you flash a different ROM, you need to wipe - not optional. If you don't, you will have problems.
CYoung234 said:
"System successfully corrupted"
Click to expand...
Click to collapse
The
BOOM!
System successfully corrupted
Please freak out now
is a joke. By your account the kernel flashed successfully. Try flashing another kernel, perhaps not an Alpha version, although I've run that particular Alpha successfully. Do you have an app that sets kernel settings on boot by chance?
Hmmm thats a Kernel i think try another kernel.. Franco is a option ... maybe ur phone can't handle the undervolt of Trinity? I don't know worth a try download franco and post ur results here
Good luck
Is the Rom in the nandroid you're always restoring to something else than 4.0.3 or. 4 based? That would cause trinity to boot loop as it doesn't work on anything lower.
Aside try wiping everything (factory reset + format system under mounts and storage), then flashing something that is considered fairly stable like an aokp milestone build and see if you can boot it without flashing any custom kernel before. Report back
Sent from my Galaxy Nexus using Tapatalk 2
d0msen said:
Is the Rom in the nandroid you're always restoring to something else than 4.0.3 or. 4 based? That would cause trinity to boot loop as it doesn't work on anything lower.
Aside try wiping everything (factory reset + format system under mounts and storage), then flashing something that is considered fairly stable like an aokp milestone build and see if you can boot it without flashing any custom kernel before. Report back
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
The nandroid I am restoring to is stock 4.0.4. I will wipe everything, then try flashing a known stable aokp build, then report back.
efrant said:
Anytime you flash a different ROM, you need to wipe - not optional. If you don't, you will have problems.
Click to expand...
Click to collapse
I have tried this both ways. Wiping prior to flashing does not seem to be as universally accepted as you indicate. For example, in the Trinity ROM dev forum, a number of the more senior posters have the opinion that you should never wipe prior to flashing, that is is an un-necessary step. I do not personally know one way or the other, so I will make sure I wipe prior to flashing from now on.
CYoung234 said:
I have tried this both ways. Wiping prior to flashing does not seem to be as universally accepted as you indicate. For example, in the Trinity ROM dev forum, a number of the more senior posters have the opinion that you should never wipe prior to flashing, that is is an un-necessary step. I do not personally know one way or the other, so I will make sure I wipe prior to flashing from now on.
Click to expand...
Click to collapse
Perhaps they meant if flashing an update of the same ROM (?), just guessing. Even then it can be a good idea sometimes; new Android version (i.e. 4.0.3 > 4.0.4), significant framework changes, etc... but I err on the "safe" side.
Updating to the next nightly of CM9 I wipe absolutely nothing.
CYoung234 said:
I have tried this both ways. Wiping prior to flashing does not seem to be as universally accepted as you indicate. For example, in the Trinity ROM dev forum, a number of the more senior posters have the opinion that you should never wipe prior to flashing, that is is an un-necessary step. I do not personally know one way or the other, so I will make sure I wipe prior to flashing from now on.
Click to expand...
Click to collapse
What Trinity ROM? Unless I'm mistaken, there is no such thing as a Trinity ROM. Trinity kernel, yes, but ROM, no.
Sent from my Galaxy Nexus using Tapatalk 2
CMNein said:
Perhaps they meant if flashing an update of the same ROM (?), just guessing. Even then it can be a good idea sometimes; new Android version (i.e. 4.0.3 > 4.0.4), significant framework changes, etc... but I err on the "safe" side.
Updating to the next nightly of CM9 I wipe absolutely nothing.
Click to expand...
Click to collapse
Yes, pretty much this. If you are updating CM9 to the next build, no need to wipe. If you are going from CM9 to AOKP, then you need to wipe.
Updating: no need to wipe.
New ROM: wipe.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
What Trinity ROM? Unless I'm mistaken, there is no such thing as a Trinity ROM. Trinity kernel, yes, but ROM, no.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Just had a thought. Trinity is the unofficial support thread for Rascream (by Rascarlo), and Morfic did make a build of Rascream with the Linaro 4.7 tool chain.
OP, which Galaxy Nexus do you have?
efrant said:
What Trinity ROM? Unless I'm mistaken, there is no such thing as a Trinity ROM. Trinity kernel, yes, but ROM, no.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
You are correct, it is a kernel, not a ROM. I have tried 3 different Trinity kernels and one Franco kernel, all with the same results. The specific kernel I flashed for post #3 was TNP-1536-384-ALPHA86b-4.7-LTO.zip. The other two I tried were both stable releases. Morfic asked me to try the alpha kernel.
CMNein said:
Just had a thought. Trinity is the unofficial support thread for Rascream (by Rascarlo), and Morfic did make a build of Rascream with the Linaro 4.7 tool chain.
OP, which Galaxy Nexus do you have?
Click to expand...
Click to collapse
Google Galaxy Nexus i9250.
CYoung234 said:
Google Galaxy Nexus i9250.
Click to expand...
Click to collapse
Okay, was asking in the event that you were also flashing Rascream, or Morfic's build of it.
Re: wiping, since we now know that we're just talking kernel here, wiping dalvik + wiping cache is indeed approaching useless, so they weren't leading you astray. I can't think of what would be causing you to boot loop however.
d0msen said:
Is the Rom in the nandroid you're always restoring to something else than 4.0.3 or. 4 based? That would cause trinity to boot loop as it doesn't work on anything lower.
Aside try wiping everything (factory reset + format system under mounts and storage), then flashing something that is considered fairly stable like an aokp milestone build and see if you can boot it without flashing any custom kernel before. Report back
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
SUCCESS! I followed your advice (mostly - I did not factory reset + format system) and d/led AOKP Milestone 5 + GAPPS, flashed bootloader and radio from the bootloader, wiped data / reset, wiped dalvik cache, and booted into recovery and installed both zip files. It booted fine, and I am grabbing my apps and configuring now. I will let you know how it performs and use it for a few days. I will likely head in the Rascream / Trinity direction after using this one for a bit. But thank you to all who have posted.
CYoung234 said:
SUCCESS! I followed your advice (mostly - I did not factory reset + format system) and d/led AOKP Milestone 5 + GAPPS, flashed bootloader and radio from the bootloader, wiped data / reset, wiped dalvik cache, and booted into recovery and installed both zip files. It booted fine, and I am grabbing my apps and configuring now. I will let you know how it performs and use it for a few days. I will likely head in the Rascream / Trinity direction after using this one for a bit. But thank you to all who have posted.
Click to expand...
Click to collapse
This got me thinking: is trinity even compatible with a stock ROM (regardless of it being 4.0.4)? Maybe that is why you were having issues.
Related
hello all
i just upgraded to the Tmobile GS2 from my trusty old Nexus One. I must say I do miss my good ol' nexus but i am truly falling in love with the beast that is the GS2!
anyways, after having the device for you know, 10 hours, I decided it was time to root it. The root went smoothly, CWM, Titanium, and SU are all working properly.
However, I have tried to flash several kernels but I am not able to overclock using any overclocking app, and in ABOUT PHONE it says im just on kernel 2.6.35.11. Making me think that the kernel flash did not happen , although it did say that it was completed successfully each time. I have noticed bits and pieces of other people having a similar issue, although I havent found a fix.
Does anyone know why my GS2 wont take to the kernel I am flashing over it?
That's weird have you flashed bullet or synergy kernels cause they have boot animation, and so you will no 4Shore if it stuck. Also in about phone you will see the bullet or synergy.
Sent from my SGH-T989 using Tapatalk
bbobarino said:
That's weird have you flashed bullet or synergy kernels cause they have boot animation, and so you will no 4Shore if it stuck. Also in about phone you will see the bullet or synergy.
Click to expand...
Click to collapse
ah yes thank you for reminding me I forgot to mention this.
YES I DO GET THE BOOT ANIMATIONS. But nothing in ABOUT PHONE and SetCPU or any other similar app cant change the Governor or Max/Min settings.....Im super confused
Can you post a link to the kernel you're trying to install? Only certain ones are compatible with the Stock image you're running.
Are you wiping cache/dalvik? If yes, when?
tweak. said:
Can you post a link to the kernel you're trying to install? Only certain ones are compatible with the Stock image you're running.
Are you wiping cache/dalvik? If yes, when?
Click to expand...
Click to collapse
I have tried to install (http://forum.xda-developers.com/showthread.php?t=1348007) BULLET versions 2.9b and 2.7b! I have also tried the newest Synergy (http://forum.xda-developers.com/showthread.php?t=1333128) kernel.
I have been wiping cache from CWM after flashing kernel. The only way I know to wipe dalvik is from flashing via rom manager, but I dont like doing that so much. Should I be? Thank you for your help already, I will do whatever you tell me to lol
I should also note that I am not looking to run a custom ROM, at least not at this time. I have my stuff already set up very nicely and would like to keep everything as is (no wipe) , just get that kernel working....
This time, try going to "Advanced" while in CWM; then 'Wipe Dalvik Cache', you might get an ext-sd card error, but your dalvik will still wipe; and then try flashing the kernel.
If that fails, goto "Mounts and Storage" and wipe your cache partition, then dalvik, THEN try flashing.
Get back to us! Always nandroid backup before this procedure as well.
A lot of the custom roms here (with the exception of juggernaut) show a static name for the kernel, regardless of which one you have installed. Juggernaut is the only one that will show the true kernel version. You may very well have installed the new kernel, and just can't tell because the name doesn't show up in about phone.
tweak. said:
This time, try going to "Advanced" while in CWM; then 'Wipe Dalvik Cache', you might get an ext-sd card error, but your dalvik will still wipe; and then try flashing the kernel.
If that fails, goto "Mounts and Storage" and wipe your cache partition, then dalvik, THEN try flashing.
Get back to us! Always nandroid backup before this procedure as well.
Click to expand...
Click to collapse
Thank you! Your first method appears to have worked for me. I can now OC. Related question, what are the details on the new smartassv2 governor and lagfree governor. How do you all find that they compare to the interactive governor, which I am used to using on my N1.
During the time of me writing this response, my phone restarted itself automatically, something that has been happening with the my S2 regardless of which kernel (even stock), do you all experience this aswell? is there a fix?
to mstrk242: thank you for this note, I did not realize.
So I installed several versions of Jelly Bean. I tried TeamBAMF Leaked ROM, Jelly Belly Leaked, and Vicious Toro (Source). All of them soft brick my phone after a day or two. It will just boot loop constantly. New ROM and Wipe make no difference. A Restore doesnt work because it gives an error when restoring Data. Always happens after a reboot or powering on the device. For me to fix this, I must use ADB to push the stock google image to the phone. This is tiring as it happened 3 times. I love JB and the features but I can't deal with this soft brick. Anyone else having an issue? I tried turning off SetCPU as well and using the Kernels that come with the ROMs. I would really like to install JB. I am and have been using AOKP M5 with absolutely no issues.
I am ready to get a new phone through Asurion. This is a launch Verizon Nexus.
EDIT: Missed the fact that this is a Verizon Nexus so removing this comment.
asawoszc said:
Have you tried a stock version of Jelly Bean from the files on XDA? Sorry but it just sounds like you've tried custom ROM's. My other suggestion would be to put on 4.0.4 takju from Google's site and see if you get the Jelly Bean OTA update and if it resolves the issues in the short term. If it does then it must be the process you're going thru to put on the ROM's..... might be missing something simple like Dalvik cache wipe, etc. Just speaking in very general terms.
Click to expand...
Click to collapse
no, he shouldnt do any of what you said. he is on a VERIZON nexus. not a GSM. if he flashed takju there could be serious problems.
Apologies... I missed the last line. Will edit out my comment.
lacesout said:
So I installed several versions of Jelly Bean. I tried TeamBAMF Leaked ROM, Jelly Belly Leaked, and Vicious Toro (Source). All of them soft brick my phone after a day or two. It will just boot loop constantly. New ROM and Wipe make no difference. A Restore doesnt work because it gives an error when restoring Data. Always happens after a reboot or powering on the device. For me to fix this, I must use ADB to push the stock google image to the phone. This is tiring as it happened 3 times. I love JB and the features but I can't deal with this soft brick. Anyone else having an issue? I tried turning off SetCPU as well and using the Kernels that come with the ROMs. I would really like to install JB. I am and have been using AOKP M5 with absolutely no issues.
I am ready to get a new phone through Asurion. This is a launch Verizon Nexus.
Click to expand...
Click to collapse
try do and this if you are comfortable doing it.. note you will lose all data including in your /sdcard/
fastboot erase system
fastboot erase userdata
fastboot erase cache
flash the factory mysid images, then install CWM (not the touch one) or TWRP and flash this rom: http://forum.xda-developers.com/showthread.php?t=1744389
Zepius said:
try do and this if you are comfortable doing it.. note you will lose all data including in your /sdcard/
fastboot erase system
fastboot erase userdata
fastboot erase cache
flash the factory mysid images, then install CWM (not the touch one) or TWRP and flash this rom: http://forum.xda-developers.com/showthread.php?t=1744389
Click to expand...
Click to collapse
Thanks Zepius but I already did this. It's the only way for me to recover. My phone is fine now on AOKP M5 but I want to use Jelly Bean. Is there any reason JB would cause boot loops after 24 hours? It's just a pain in the ass because I can't simply recover through CWM. I need a PC. The first time this happened I had to back up my SDCARD from ADB. This took forever!!
BTW, I know how to Root, ROM, etc. I always do everything twice. Wipe Data/Dalvik/Cache and install the ROM twice.
just curious... which version of CWM are you using?
Oh man I have the same issue I just get stuck at the Google screen or the jb splash screen on my cdma nexus I tried everything and wiped every last thing on my phone I just gave up and said ile wait for the official update I guess. Anyway I hope this thread shed some light on the situation we having
Sent from my Galaxy Nexus using xda app-developers app
Use the superwipe from the android HD thread, flash the rom, everytime it boots let it sit at the google logo IT IS NOT FROZEN. It just takes a while sometimes.
What are you doing that's causing a soft-brick after 24 hours? I mean, the phone is just sitting on a table and BOOM - it freezes and it's soft-bricked?? Maybe give us the scenario that happens when it's soft-bricked. We need more concrete details. It could be something you're doing wrong.
Zepius said:
just curious... which version of CWM are you using?
Click to expand...
Click to collapse
I was using the latest (forgot which version) and I also tried CWM touch between the first two bricks. Same issue.
XfrostX said:
Use the superwipe from the android HD thread, flash the rom, everytime it boots let it sit at the google logo IT IS NOT FROZEN. It just takes a while sometimes.
Click to expand...
Click to collapse
Nope, it keeps boot looping. I had it sitting for over 30 min. It starts with Google then JB splash. Then boot loops and continues. Even when I wipe and install AOKP it still boot loops. I need to use Fastboot to wipe and flash stock image.
akira02rex said:
What are you doing that's causing a soft-brick after 24 hours? I mean, the phone is just sitting on a table and BOOM - it freezes and it's soft-bricked?? Maybe give us the scenario that happens when it's soft-bricked. We need more concrete details. It could be something you're doing wrong.
Click to expand...
Click to collapse
It happens as soon as I reboot or power off the phone. For instance, Saturday I went shark fishing so I powered down the phone to save battery. Power it up several hours later and it boot looped for 20 min.
I am using a AOKP restore I recovered through ADB. Once I flashed stock image, rooted, installed CWM, the restore worked perfectly.
lacesout said:
I was using the latest (forgot which version) and I also tried CWM touch between the first two bricks. Same issue.
Nope, it keeps boot looping. I had it sitting for over 30 min. It starts with Google then JB splash. Then boot loops and continues. Even when I wipe and install AOKP it still boot loops. I need to use Fastboot to wipe and flash stock image.
It happens as soon as I reboot or power off the phone. For instance, Saturday I went shark fishing so I powered down the phone to save battery. Power it up several hours later and it boot looped for 20 min.
I am using a AOKP restore I recovered through ADB. Once I flashed stock image, rooted, installed CWM, the restore worked perfectly.
Click to expand...
Click to collapse
Is it getting wet??
akira02rex said:
Is it getting wet??
Click to expand...
Click to collapse
Lol nope. The shark fishing trip was the third boot loop for me.
Same boat here... I can flash any ics and restore any backup... but some how every time I flash jb rom it just stay in nexus logo or in any kernel logo.. the first time the vicious jb rom out I manage to flash and boot well ..then after a few days tried different jb rom then boom! Infinite boot loop.. then since then I can't flash jb rom. Tried all kind of kernel and rom combo and also used all kinds of cwm..
Sent from my Galaxy Nexus using XDA Premium App
landrian18 said:
Same boat here... I can flash any ics and restore any backup... but some how every time I flash jb rom it just stay in nexus logo or in any kernel logo.. the first time the vicious jb rom out I manage to flash and boot well ..then after a few days tried different jb rom then boom! Infinite boot loop.. then since then I can't flash jb rom. Tried all kind of kernel and rom combo and also used all kinds of cwm..
Sent from my Galaxy Nexus using XDA Premium App
Click to expand...
Click to collapse
Interesting that you got it to work once, because I have the same issue you do but have never gotten it to boot past the Google animation. Wonder if there was a Rom that we flashed that caused the issue to begin with. I have tried so many JB roms now that I don't know which one I started with, but I think it was Vicous JB since that was the first one I saw released at the time. Just wish someone out there that has had our symptoms and finally got past them could tell us what they did.
Well at least I'm not the only having this issue. Hopefully someone can shed some light.
@nothingshocking
Its the [email protected]_jelly jb rom that I flash when this things all starts.. the vicious rom works for me since v1 to v3.. I'm trying other rom because of grs issue in vicious at that time. I'm not afraid to flash or be in softbrick because I know I can always use my backup and restore or there's toolkit just in case ,but this thing I'm really puzzled this is so weird.. I can flash any ics rom but not the jb rom.. someone suggest me to use jb bootloader and I did and same results.. I'm really hoping that someone of our bright dev can look in to this and help us..
Sent from my Galaxy Nexus using XDA Premium App
Same exact problem here. I would boot loop anytime I rebooted or powered down my phone. Today, I flashed the new clockwork recovery (v.6.0.0.?). So of course I rebooted my phone to see what it looked like. Well it looked cool but when I went to reboot my phone it was just stuck on the google screen. Wouldn't boot at all. Tried wiping data/cache/dalvik cache/format system/format cache/fix permission. Got desperate cuz nothing worked. Backups wouldn't restore. Got "installation aborted error". Finally did like the op and flashed stock image. Works fine now. Just seems like my phone doesn't like the JB at all. Has done this on every JB I flashed.
Sent from my Galaxy Nexus using xda premium
had this happen on my cdma toroplus any ics rom will install and work fine but no jelly bean rom will boot past the bootanimation
Maybe it has to do with hardware version? For those of you with problems like me, are you on a launch Nexus? That is what I have.
My SKU is SCHI515MSV
I am not sure if they redesigned the hardware at some time.
Verizon Samsung Galaxy Nexus - Toro
Bootloader version: PRIMELA03
Baseband version: I515
Android version 4.1.1
Miui.US 2.9.14.0
Clockwork recovery v5.5.0.4
I was previously running Vicious Jelly bean and installed Miui.US. Since then my phone constantly reboots within a few seconds of booting up. I have tried flashing to a different ROM and flashing back to stock several times using different tools and also from command line. I have also tried going back to stock via ODIN. All have failed and the phone always restores itself to the previous state. I have searched for recovery-from-boot.p in /system and other locations but cannot find it.
My Droid is currently unusable. Any tips or tricks are greatly appreciated.
Does anyone know what would cause the phone to keep restoring its previous state ? As I mentioned I have looked for the recovery-from-boot script and cannot find it. Thanks!
Dr01d4l1f3 said:
Verizon Samsung Galaxy Nexus - Toro
Bootloader version: PRIMELA03
Baseband version: I515
Android version 4.1.1
Miui.US 2.9.14.0
Clockwork recovery v5.5.0.4
I was previously running Vicious Jelly bean and installed Miui.US. Since then my phone constantly reboots within a few seconds of booting up. I have tried flashing to a different ROM and flashing back to stock several times using different tools and also from command line. I have also tried going back to stock via ODIN. All have failed and the phone always restores itself to the previous state. I have searched for recovery-from-boot.p in /system and other locations but cannot find it.
My Droid is currently unusable. Any tips or tricks are greatly appreciated.
Click to expand...
Click to collapse
I have attached the output I get from logcat. Please help!
***Removed logcat file***
1) did you wipe data/cache when you switched roms?
2) dont use odin, its not really supported for this phone. learn fastboot: http://forum.xda-developers.com/showthread.php?t=1626895
3) recovery-from-boot.p has nothing to do with what you are talking about. all that does is restore the stock recovery. ODIN is failing for another reason.
Zepius,
Thanks for the response.
1) did you wipe data/cache when you switched roms?
I have wiped data and cache several times after I switched. Both from within recovery and running command 'fastboot erase cache'
2) dont use odin, its not really supported for this phone. learn fastboot: http://forum.xda-developers.com/show....php?t=1626895
I have followed this manual and others and have become familiar with the process. I complete all the steps and issue the 'fastboot reboot' command. The phone reboots back into the previous state
3) recovery-from-boot.p has nothing to do with what you are talking about. all that does is restore the stock recovery. ODIN is failing for another reason.
I'm grasping for straws here, not sure what else I need/can do
Dr01d4l1f3 said:
Verizon Samsung Galaxy Nexus - Toro
Bootloader version: PRIMELA03
Baseband version: I515
Android version 4.1.1
Miui.US 2.9.14.0
Clockwork recovery v5.5.0.4
I was previously running Vicious Jelly bean and installed Miui.US. Since then my phone constantly reboots within a few seconds of booting up. I have tried flashing to a different ROM and flashing back to stock several times using different tools and also from command line. I have also tried going back to stock via ODIN. All have failed and the phone always restores itself to the previous state. I have searched for recovery-from-boot.p in /system and other locations but cannot find it.
My Droid is currently unusable. Any tips or tricks are greatly appreciated.
Click to expand...
Click to collapse
This is what do every time for ANY rom and never have issues.
I also restore data with TB after successful flash and startup, then I login into Google.
Using clockworkmod touch recovery 6.0.1.5
Under mounts & storage:
Format....system
Format....cache
Format....data
Then install ROM of your choice.
If installing custom kernel waiting until the device has fully booted up to setup screen and then reboot to recovery and install your favorite kernel.
If flashing mods and such you need to reboot after each flash otherwise you could bootloop or get stuck at Google logo....
If using twrp it has a feature that allows flashing multiple zips.....with miui it has caused intermittent problems on some users devices.
Hope this helps.....
Sent from my Galaxy Nexus
cdexsw said:
This is what do every time for ANY rom and never have issues.
I also restore data with TB after successful flash and startup, then I login into Google.
Using clockworkmod touch recovery 6.0.1.5
Under mounts & storage:
Format....system
Format....cache
Format....data
Then install ROM of your choice.
If installing custom kernel waiting until the device has fully booted up to setup screen and then reboot to recovery and install your favorite kernel.
If flashing mods and such you need to reboot after each flash otherwise you could bootloop or get stuck at Google logo....
If using twrp it has a feature that allows flashing multiple zips.....with miui it has caused intermittent problems on some users devices.
Hope this helps.....
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Ill never understand why people dont learn stuff like this before they start flashing roms in the first place. These steps are common knowledge and easily attainable information. Maybe this post will help some poor android noob fight the urge to post an unnecessary topic in the future and stop panicking and restoring their phone to stock when they soft brick it.
Dr01d4l1f3 said:
Zepius,
Thanks for the response.
1) did you wipe data/cache when you switched roms?
I have wiped data and cache several times after I switched. Both from within recovery and running command 'fastboot erase cache'
2) dont use odin, its not really supported for this phone. learn fastboot: http://forum.xda-developers.com/show....php?t=1626895
I have followed this manual and others and have become familiar with the process. I complete all the steps and issue the 'fastboot reboot' command. The phone reboots back into the previous state
3) recovery-from-boot.p has nothing to do with what you are talking about. all that does is restore the stock recovery. ODIN is failing for another reason.
I'm grasping for straws here, not sure what else I need/can do
Click to expand...
Click to collapse
Odin fails because it is not fully compatible with CDMA radios....meaning that it cannot flash the baseband/radio for cdma devices....well at least it doesn't for Verizon gnex.
You need to manually flash your devices images using fast boot. This can take awhile.....if you don't know what you are doing then READ first before doing so. Make sure you have the proper images.
Or look for P3Droid All-n-One-JB-Installer zip, flash it from cwm recovery. It will get you pure stock running a rooted jelly bean ROM. That's the best you can hope for....
Also before flashing follow the steps I listed above.....
Goodluck
Sent from my Galaxy Nexus
eqjunkie829,
Is it lonely up there on your high horse ? This is not the first time or the first phone I have rooted.
eqjunkie829 said:
Ill never understand why people dont learn stuff like this before they start flashing roms in the first place. These steps are common knowledge and easily attainable information. Maybe this post will help some poor android noob fight the urge to post an unnecessary topic in the future and stop panicking and restoring their phone to stock when they soft brick it.
Click to expand...
Click to collapse
cdexsw,
Thanks for the tip, I will try that.
cdexsw said:
Odin fails because it is not fully compatible with CDMA radios....meaning that it cannot flash the baseband/radio for cdma devices....well at least it doesn't for Verizon gnex.
You need to manually flash your devices images using fast boot. This can take awhile.....if you don't know what you are doing then READ first before doing so. Make sure you have the proper images.
Or look for P3Droid All-n-One-JB-Installer zip, flash it from cwm recovery. It will get you pure stock running a rooted jelly bean ROM. That's the best you can hope for....
Also before flashing follow the steps I listed above.....
Goodluck
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Zepius said:
2) dont use odin, its not really supported for thisany phone. learn fastboot: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
Odin is a leaked tool from Sammy, it is not supported on any device.
OP, read efrant's guide on flashing stock (sticky, general section)
Sent from my i9250
Hello guys!
As the title says, I keep on having boot loops after flashing any custom JB Roms (Jedi, LiquidSmooth, CM Nightly, Slimbean). I'm not new to flashing roms (I got LG units though, SU660 and KU5900). When I tried flashing ICS Roms, I don't have any problem. But I want JB that bad!
I followed KonstantinKeller's thread of restoring/recovering from a bad flash (going back to GB), rooted following Melvin's thread. Then did all the prerequisites..like the common wiping of data, clear cache & davlik. But then again after flashing JB roms listed above, I keep on having boot loops!
What did I do wrong? This ain't my first time flashing (first time on this phone -T989- though)
I read some posts with almost the same problem, but I don't think I found a solution for this. Any good soul that can extend their help is highly appreciated. Thank you in advance.
I got a bootloop before when trying to flash JB roms and what I did was restore to original state (using the bad flash recovery technique), and then not rooting it but installing cwm through Odin and dirty flashing the Rom in cwm. Once it flashed I used it for a few to make sure that everything was working correctly. Then I got the goo manager app and got twrp. After that I followed all the steps in the OP (Jedi jelly) and flashed the Rom. Now I'm running Jedi jelly 3.1 perfectly. Hope this method helps.
Sent from my SAMSUNG-SGH-T989 using xda premium
djtreo said:
Hello guys!
As the title says, I keep on having boot loops after flashing any custom JB Roms (Jedi, LiquidSmooth, CM Nightly, Slimbean). I'm not new to flashing roms (I got LG units though, SU660 and KU5900). When I tried flashing ICS Roms, I don't have any problem. But I want JB that bad!
I followed KonstantinKeller's thread of restoring/recovering from a bad flash (going back to GB), rooted following Melvin's thread. Then did all the prerequisites..like the common wiping of data, clear cache & davlik. But then again after flashing JB roms listed above, I keep on having boot loops!
What did I do wrong? This ain't my first time flashing (first time on this phone -T989- though)
I read some posts with almost the same problem, but I don't think I found a solution for this. Any good soul that can extend their help is highly appreciated. Thank you in advance.
Click to expand...
Click to collapse
are you using darkside scripts to wipe? because they will cause bootloops
skinsfanbdh said:
are you using darkside scripts to wipe? because they will cause bootloops
Click to expand...
Click to collapse
is there any way to reverse the loop that the darkside wipe is causing?
it REALLY sounds like the recovery u are using is TOO OLD. Make sure u are using the latest version of twrp (2.3.3) to flash all jellybean roms.
TWRP is backwards compatible and touch capable, so if you're worried about flashing GB or ICS ROMs it'll do the trick just fine
it is however a requirement for flashing all 4.1 ROMs.
Basic install instructions:
make sure u have root
download goo manager from play
open > menu > install open script recovery
agree to everything, but make sure t989 is in the downloaded image name
reboot to recovery u should see twrp
Hi everyone,
I wasn't used to consider myself a too-much-noob anymore, but now I've plenty of doubts.
So, here's my problem: I've decided to give the latest ParanoidAndroid release a try and my maguro was "oem locked". Then, I've run the command "fastboot oem unlock" and copied all files I needed (PA rom, GlaDos v2.2 and latest GApps) into my /sdcard folder (usual job). I've rebooted into recovery (latest touch CWM), formatted /system, /data, /cache (usual full wipe), searched for the files and flashed them.
When it was time to reboot, the phone got stuck at the first screen (black, with the white "Google" and the white opened padlock). In other words, the bootanimation didn't even start.
Then, I've re-downloaded the stuff, double-checked all Md5 sums, re-copied everything in the sdcard but the result didn't change.
I've tried to re-flash the stock unrooted rom, then repeating the steps without formatting /system. I've also tried to not flash the kernel. No way the rom could even boot.
Now I'm seriously wondering what's wrong with what I've done . For completeness, my bootloader version is LC03 and the radio is XXLJ1 (same as the fully stock android bundle that can be found here)
I've also checked (maybe too much quickly, I may admit) the threads for PA and GlaDos, but I haven't seen anyone complaining about the same problem...
Could you guys please help me?
First of all....
all you need to do to wipe is select
FACTORY RESET in custom recovery
Secondly:
GlaDos 2.2 is probably not going to work with PA3.0
- Based on stock Android kernel Jelly Bean 4.1.1 JRO03C
Click to expand...
Click to collapse
Pirateghost said:
First of all....
all you need to do to wipe is select
FACTORY RESET in custom recovery
Secondly:
GlaDos 2.2 is probably not going to work with PA3.0
Click to expand...
Click to collapse
Thank you for the reply, but i've also tried the factory reset you mean (no results) and, for GlaDos, my bad, I've linked an XDA thread instead of the "original" updated thread on rootzwiki
Endriu90 said:
Thank you for the reply, but i've also tried the factory reset you mean (no results) and, for GlaDos, my bad, I've linked an XDA thread instead of the "original" updated thread on rootzwiki
Click to expand...
Click to collapse
i have been looking forward to a new GladOS...thanks for the link
in recovery, all you have to do is factory reset then flash the rom. thats it
EDIT:
which version of PA 3.0 are you trying to install
Pirateghost said:
which version of PA 3.0 are you trying to install
Click to expand...
Click to collapse
I've tried with all releases which can be found here
Flash Kernel too
Hi,
When the new PA version was uploaded (20 Feb), this was the warning posted by the developer:
WARNING
As I didn't have so much time, I couldn't make it booting with default kernel (Need to update prebuilt kernel). So if you're gonna use it BE SURE YOU FLASH A CUSTOM 4.2.2 KERNEL!
Click to expand...
Click to collapse
So I recommend you download any latest 4.2.2 kernel (AK kernel or franco) and flash it alongwith the ROM.
Hope this helps.
Regards,
Neeraj
neerajvd said:
So I recommend you download any latest 4.2.2 kernel (AK kernel or franco) and flash it alongwith the ROM.
Click to expand...
Click to collapse
Thank you guys, I've solved (I've tried just with the factory reset as said by pirateghost, but I was used to format /system, /data and /cache when it was time to flash roms like AOKP and everything used to work properly) (I was used to do the same with the Nexus S).
Now I'm running the 15feb release with the stock android kernel (which comes with the stock 4.2.2 factory bundle) and everything just works as expected.
Anyway, I still can't get the reason why GlaDOS shouldn't work with the 20feb release. I mean, it's a custom kernel and it should work as well as AK or franco kernels, shouldn't it? If I'm wrong, could you briefly tell me why? (sorry, I won't move to other kernels, as I personally love GlaDOS and it provides my GNex with the optimal equilibrium performances/battery life)
EDIT:
alongside the 15feb release, I've tried to flash GlaDOS (just factory-resetting before flashing), but nothing boots. Restored the backup, now I'm still running PA with the stock kernel