AOKP JB 4 TORO + Verizon Galaxy Nexus Boot Loop [Not resolved] - Samsung Galaxy Nexus

Had AOKP ICS.
Booted into CWM
Factory reset
Wiped cache
Formatted /system
wiped devlick (sp?)
Installed AOKP JB Build 4 and Gapps
Everything worked fine.
Phone running well.
Reboot phone.
Phone boots, goes into AOKP boot loader and promptly halts, phone reboots, now stuck at Google splash screen with unlocked boot loader icon.
Pull battery, reboot, same issue.
Boot into recovery
Can't flash backup.
Follow the above steps to re-flash:
Factory reset
Wiped cache
Formatted /system
wiped devlick (sp?)
Flashed AOKP JB Build 4
Flashed Gtools
Fixed permissions
Issue persists.
Still have ICS files on SD CARD
Follow above steps but this time I flash AOKP ICS.
SAME ISSUE! Boot loader for AOKP ICS halts and reboots.
/frown.
Help?

Download the factory images and fastboot flash the bootloader and both radios
Sent from my Galaxy Nexus using Tapatalk 2

Zepius said:
Download the factory images and fastboot flash the bootloader and both radios
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
"both radios"?

bk201doesntexist said:
"both radios"?
Click to expand...
Click to collapse
yes. the vzw version has the LTE radio and CDMA radio.

Zepius said:
yes. the vzw version has the LTE radio and CDMA radio.
Click to expand...
Click to collapse
"Sorry, you are limited to 8 thanks per day"
Thanks mate. I'm on GSM so... Didn't know that.
Edit: You got me thinking; So there's 2 radio partitions on toro? How does fastboot comply with that?

bk201doesntexist said:
"Sorry, you are limited to 8 thanks per day"
Thanks mate. I'm on GSM so... Didn't know that.
Edit: You got me thinking; So there's 2 radio partitions on toro? How does fastboot comply with that?
Click to expand...
Click to collapse
Fastboot flash radio
Fastboot flash radio-cdma
2 different comnands
Sent from my Galaxy Nexus using Tapatalk 2

Well...?
Did you ever get it to work? I'm having the same issue and would love to know what you did to get your phone back to "normal"
-Chlorine
Ecaz said:
Had AOKP ICS.
Booted into CWM
Factory reset
Wiped cache
Formatted /system
wiped devlick (sp?)
Installed AOKP JB Build 4 and Gapps
Everything worked fine.
Phone running well.
Reboot phone.
Phone boots, goes into AOKP boot loader and promptly halts, phone reboots, now stuck at Google splash screen with unlocked boot loader icon.
Pull battery, reboot, same issue.
Boot into recovery
Can't flash backup.
Follow the above steps to re-flash:
Factory reset
Wiped cache
Formatted /system
wiped devlick (sp?)
Flashed AOKP JB Build 4
Flashed Gtools
Fixed permissions
Issue persists.
Still have ICS files on SD CARD
Follow above steps but this time I flash AOKP ICS.
SAME ISSUE! Boot loader for AOKP ICS halts and reboots.
/frown.
Help?
Click to expand...
Click to collapse

I don't know if this will help or not, nor do I know if this will help your situation. My phone was in the same state, boot loop hell! After doing the same processes you did I tried a fix permission and rebooted the phone. It worked! I can't reboot yet because I need to copy my files from my phone before moving forward with any trail and errors of rebooting, etc. I hope this helps you.
-Chlorine

Related

Newbie help with VZN GN

So I decided to root my phone and upgrade to JB. But after I unlocked the bootloader, rooted the phone, flashed CWM Recovery and downloaded "Vicious JellyBean V2- No SU Zip necessary- Francos kernel and WiFi fix Zip" then went in to fastboot mode and installed it, my phone is hanging up on the new multicolored x splash screen and will not load. I waited 30 mins, I bricked it. So I went back into fastboot mode and reinstalled the JB, but still same thing.
So I am without a phone because I dont know what to do. :crying:
Any help is greatly appreciated!!!!! TIA
what do you mean by fastboot mode. You should have been flashing it through clockwork. Did you wipe your data, cache and Dalvik cache before hand? Or make a nandroid backup before installing Liquid?
If not sounds as if you are going to need the toolkit or push the stock files via adb to flash back to stock then start again
Get this set up.
I don't feel like debugging for two hours via text and reply.
I'll recover as much as I can.
Edit:
http://www.teamviewer.com/en/index.aspx?utm_expid=60202728-6
Lol, meant to paste that link.
Once that's installed I'll remote connect to your PC and try to fix this.
NeoMagus said:
what do you mean by fastboot mode. You should have been flashing it through clockwork. Did you wipe your data, cache and Dalvik cache before hand? Or make a nandroid backup before installing Liquid?
If not sounds as if you are going to need the toolkit or push the stock files via adb to flash back to stock then start again
Click to expand...
Click to collapse
I wiped with toolkit didnt cache or Dalvik cache. I have a replacement device coming today and want to try again. Is there a link to somewhere with step by step directions. I would assume the replacement device has factory settings so do I have to wipe, etc?
skinnytoo2 said:
I wiped with toolkit didnt cache or Dalvik cache. I have a replacement device coming today and want to try again. Is there a link to somewhere with step by step directions. I would assume the replacement device has factory settings so do I have to wipe, etc?
Click to expand...
Click to collapse
Manual Method
Toolkit Method
Just download a JB rom from the Development forum after you've unlocked bootloader, flashed a custom recovery, and have rooted your phone. Most are bug and glitch free...
I reflashed JB and it worked!!! Thanks guys!! Love JB
skinnytoo2 said:
I reflashed JB and it worked!!! Thanks guys!! Love JB
Click to expand...
Click to collapse
grats. next time, please dont incorrectly use the term 'brick'
brick = unable to turn on. no bootloader mode [fastboot], no recovery, no download.

[Q] boot loop on reboot

Hey guys,
Got a very weird problem here. I have previously flashed a CM10 nightly to my One X (international) and everything has been fine for around 3 weeks. Decided i wanted to try our the ViperX ROM. Previously upon flashing this ROM it just bootlooped but after another try with a slightly different method, i managed to get it to boot and all was merry. After titanium restore i rebooted, and this once again put me into a bootloop. Cannot get the ROM to boot. Why is this!!! Switched back to CM10. :good:
You need to do
fastboot flash boot boot.img
You may have done
fastboot boot boot.img
BenPope said:
You need to do
fastboot flash boot boot.img
You may have done
fastboot boot boot.img
Click to expand...
Click to collapse
Still doesnt boot man, im sure i flashed the boot image properly. This is the rundown of my flash process:
1: install from sd
2: in recovery, factory reset, wipe cache, wipe dalvic cache
3: Boot into fastboot and flash the boot.img
4: Reboot.
So it booted but into viper X, but after restoring with Titanium i was unable to get it to boot again.
I also tried "fastboot erase cache" to no avail
In fastboot type fastboot erase cache
Jamekerr said:
So it booted but into viper X, but after restoring with Titanium i was unable to get it to boot again.
Click to expand...
Click to collapse
Did you restore system apps or data?
Where does it stop booting, what is on the screen?
With tb, make sure you restore user apps only, none of the system apps.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
eyosen said:
With tb, make sure you restore user apps only, none of the system apps.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
Sorry forgot to mention I also used the "fast book erase cache" command.
As for titanium I restored all user apps and data and now that you mention it that could be the problem. I'll have another crack tomorrow and let you know.
Main reason I want to switch is I need much better battery life than CM10 but only temporarily. Can anyone recommend viperx as being a significant improvement?
BenPope said:
Did you restore system apps or data?
Where does it stop booting, what is on the screen?
Click to expand...
Click to collapse
It comes up with "HTC" vibrates then the viper crawls across the screen and it stops at the "htcONE" logo.
Restored apps and app data and guess what. Still doesn't boot. WHY! Going to just try apps, no data at ALL. Will report back.
I dunno why it won't start, double check you have the right boot.img (download it again and flash it again), in recovery erase cache and dalvik cache.
same issue
Hi i am also getting the same problem, i used the viper rom and others but it goes past the HTC logo looks as though it works but the lock ring is froze up and then it reboots itself over and over doing the same thing each time. Ive tried One_X_All-In-One_Kit_v1.2 and the manual CMD fastboot tutorial i dont know what to do to fix this, can anyone help me please?
EDIT* I seem to have it working now (fingers crossed), i used 'Nocturnal_Special_Edition_4.0_Odex' so thx to their good work that i now have a working rom for my phone phew
EDIT 20 MIN LAter* OK looks like i did something i shouldnt, it seemed to work, i made a change in the settings and then it rebooted and continued to reboot over and over so i tried installing a rom again and now it just stays at the htc quietly brilliant screen, what have i done this phone is now not so brilliant as its looking more and more that ive goosed it Any help apreciated.
boot.img
Help please
Hello,
I have 1x (CID 203) unlocked and rooted with cwm recovery. I had Cyanogenmod 10 nighly on it, well in hope of no bugs like in CM10 I flashed this http://forum.xda-developers.com/showthread.php?t=1763240 to it. Well it seemed to work a moment but then the device started rebooting randomly. I couldn't boot to recovery (strange?), the recovery screen flashed less than a second and the phone started to boot normally again. After a few tries (and reflashing recovery) I luckily got into the recovery. Tried to restore a nandroid backup which I made earlier yesterday. CWM said that the restore was successful but the device didnt boot anymore. Only shows htc logo and cyanogenmod loading screen. But nothing happens. Well, then I flashed Android Revolution HD 10.3. (with wiping the system data and so on) but it wont load any longer than the htc one logo screen. Rom installed fine and I flashed the boot.img.
Now I'm able to get into recovery and fastboot and charge my phone but how could I safely and surely return my phone to stock or make the ARHD work without completely bricking it? I'm thinking that relocking my device is not very safe if the RUU fails to install. What do you think? Can the firmware updates cause this problem to happen? Can I flash ARHD 9.7.2 to my device? Too bad I can't ask these questions in the ARHD thread....
In bootloader my phone says
Code:
hboot-0.94.0000
radio 1.1204.104.14
Any advice is highly appreciated, I'm not ready to bury my phone yet
Edit. ARHD 9.7.2 flashed correctly. Any ideas why the ARHD 10.3 keeps bootlooping? Yes, I have flashed the correct boot.imgs.
BenPope said:
I dunno why it won't start, double check you have the right boot.img (download it again and flash it again), in recovery erase cache and dalvik cache.
Click to expand...
Click to collapse
If I restore apps only it does boot however any sort of data and it refuses to. Very annoying as I am not able to retain texts accounts etc. I have a feeling it's because I originally backed up on a jellybean ROM and the data just doesn't want to work on ics
Squbbe said:
Hello,
I have 1x (CID 203) unlocked and rooted with cwm recovery. I had Cyanogenmod 10 nighly on it, well in hope of no bugs like in CM10 I flashed this http://forum.xda-developers.com/showthread.php?t=1763240 to it. Well it seemed to work a moment but then the device started rebooting randomly. I couldn't boot to recovery (strange?), the recovery screen flashed less than a second and the phone started to boot normally again. After a few tries (and reflashing recovery) I luckily got into the recovery. Tried to restore a nandroid backup which I made earlier yesterday. CWM said that the restore was successful but the device didnt boot anymore. Only shows htc logo and cyanogenmod loading screen. But nothing happens. Well, then I flashed Android Revolution HD 10.3. (with wiping the system data and so on) but it wont load any longer than the htc one logo screen. Rom installed fine and I flashed the boot.img.
Now I'm able to get into recovery and fastboot and charge my phone but how could I safely and surely return my phone to stock or make the ARHD work without completely bricking it? I'm thinking that relocking my device is not very safe if the RUU fails to install. What do you think? Can the firmware updates cause this problem to happen? Can I flash ARHD 9.7.2 to my device? Too bad I can't ask these questions in the ARHD thread....
In bootloader my phone says
Code:
hboot-0.94.0000
radio 1.1204.104.14
Any advice is highly appreciated, I'm not ready to bury my phone yet
Edit. ARHD 9.7.2 flashed correctly. Any ideas why the ARHD 10.3 keeps bootlooping? Yes, I have flashed the correct boot.imgs.
Click to expand...
Click to collapse
Try the fast boot erase cache command and see if that solves the boot issue. If not make sure in recovery your have cleared cache partition performed a factory reset and also cleared the dalvik cache. Again if none of these work try re flashing the boot.img or perhaps try another rom that is known to be stable.

[Q] All ROMs get stuck in bootloop

Hey guys, I've spent the last 10ish hours or so trying to find and flash a ROM to my gnex that won't get stuck in a bootloop. I've tried Xylon, AOSPA Toro, Ato,421 Jelly Beer, and JB sourcery. I get the same problem with each. Here's been my procedure, with slight variations on when I wipe what caches and
Using Wugs Root Toolkit:
1- Flash stock and unroot
2 - unlock
3 - push root files to phone
4 - install root files with TWRP
5 - run super su and busybox installer
6 - Flash zip of ROM to phone
7 - install ROM files with TWRP
8 - GET STUCK IN BOOTLOOP
Any help is appreciated!
Did you install latest twrp?
Have you been able to boot stock?
Is the stock Rom version same as your custom Rom?
Odesláno z mého Galaxy Nexus pomocí Tapatalk 2
A1R80RN3 said:
Hey guys, I've spent the last 10ish hours or so trying to find and flash a ROM to my gnex that won't get stuck in a bootloop. I've tried Xylon, AOSPA Toro, Ato,421 Jelly Beer, and JB sourcery. I get the same problem with each. Here's been my procedure, with slight variations on when I wipe what caches and
Using Wugs Root Toolkit:
1- Flash stock and unroot
2 - unlock
3 - push root files to phone
4 - install root files with TWRP
5 - run super su and busybox installer
6 - Flash zip of ROM to phone
7 - install ROM files with TWRP
8 - GET STUCK IN BOOTLOOP
Any help is appreciated!
Click to expand...
Click to collapse
why arent you wiping data/cache in recovery? you need to do that.
standa75 said:
Did you install latest twrp?
Have you been able to boot stock?
Is the stock Rom version same as your custom Rom?
Odesláno z mého Galaxy Nexus pomocí Tapatalk 2
Click to expand...
Click to collapse
got the latest TWRP last night and yes, stock works fine. I've been going from 4.1.1 to 4.2.1/4.2.2. should I update the stock rom before flashing the new one?
Also I've tried wiping caches at every point possible, not wiping caches at all, and wiping them at different times, but still to no avail
A1R80RN3 said:
got the latest TWRP last night and yes, stock works fine. I've been going from 4.1.1 to 4.2.1/4.2.2. should I update the stock rom before flashing the new one?
Also I've tried wiping caches at every point possible, not wiping caches at all, and wiping them at different times, but still to no avail
Click to expand...
Click to collapse
You need to run factory reset in twrp/cwm.
Sent from my Galaxy Nexus
finally booted!!!
Here's what I did:
1 - After flashing to stock and unrooting I let the device (TORO, not ToroPLUS) update to 4.2.2.
2 - moved on to unlocking and rooting the phone
3 - flashed latest TWRP
4 - Pushed latest Xylon Rom
5 - booted into TWRP and installed xylon
6 -Wiped caches
7 - restored data
I don't know why this worked all of a sudden, but you have my exact steps on the try that DID work, so I hope that for anyone else who has this problem this was helpful, and thanks Zepius and standa75 for the help!
A1R80RN3 said:
finally booted!!!
Here's what I did:
1 - After flashing to stock and unrooting I let the device (TORO, not ToroPLUS) update to 4.2.2.
2 - moved on to unlocking and rooting the phone
3 - flashed latest TWRP
4 - Pushed latest Xylon Rom
5 - booted into TWRP and installed xylon
6 -Wiped caches
7 - restored data
I don't know why this worked all of a sudden, but you have my exact steps on the try that DID work, so I hope that for anyone else who has this problem this was helpful, and thanks Zepius and standa75 for the help!
Click to expand...
Click to collapse
When you unlocked, you wiped data partition. All you needed to do was use factory reset before flashing ROM
Sent from my Galaxy Nexus
you could try doing a full factory reset and format data in twrp. i've had otherwise unexplainable problems that were fixed by doing that, sometimes i think the internal memory just needs a good reformat.
download 2.5 here, http://www.teamw.in/project/twrp2/90
1) open adb
2) adb reboot bootloader
3) fastboot flash recovery >>>>your file here<<<<<<, so if you named your image file to be TWRP.img, type "fastboot flash recovery TWRP.img", assuming you are in the directory of the img file....
4) boot into recovery, do a full OS wipe, flash new rom, wipe dalvik and cache once more just in case (i think its a good habbit even its not needed most of the time, only takes like half a second anyways.....).
5) still failing? you are doing something wrong, read carefully and do it again.
If it is only 1 rom you can blame on faulty rom/corrupted files whatever, you tried that many roms it has to be your own problem.

In between 4.2.2 and 4.3 problem.

I was on 4.2.2 XenonHD with LeanKernel. I directly flashed Cataclysm ROM with cache, dalvik cache wipe and factory reset on GooManager. It booted flawlessly the first time. Then after completing the startup I rebooted. But then I became stuck on the google logo (surprise surprise...)
I don't get it. Why did it boot perfectly the first time but not after a reboot?
Anyway, I tried to restore my nandroid backup of the 4.2.2 XenonHD ROM. But then I got stuk at the google logo again. Why?
I haven't backed up my mediafiles (music, photo's etc) yet, in case a factory image installation is needed. I assumed I didn't need to backup those mediafiles, becuase I already have a nandroid backup, meaning I can always go back to the last ROM.
Does anybody have a solution for this? I don't care if I end up booting in 4.2.2 or 4.3, as long as I can preserve my media files.
Or do I have no other options than installing factory boot image of 4.3, meaning my files will be gone?
Thanks in advance.
No as long as you don't flash userdata.img nothing will be wiped (I think maybe to be sure you have to check twice). You can use adb pull to pull the mediafiles if you want.
Sent from my Galaxy Nexus using XDA Premium HD app
Try factory reset and then try to restore from the backup..
lastforone said:
Try factory reset and then try to restore from the backup..
Click to expand...
Click to collapse
It didn't work. I can still see my files and everything in TWRP recovery.
Rapydax said:
It didn't work. I can still see my files and everything in TWRP recovery.
Click to expand...
Click to collapse
I had Purity ROM with A.S.K.P kernel when 4.3 came out, i grabbed the zip from one of the topic in development and flashed it VIA CWMRecovery, was pretty smooth but i wanted all my setting which wasn't possible so i reverted back to Purity, this is how i did it.
Factory Reset.
Format /system
Flashed 4.3
--
Factory Reset.
Format /system, /cache, cleared Dalvik Cache as well
Flashed PurityRom 4.2
Flashed A.S.K.P Kernel
Flashed CrossBreeder Mod
Booted into OS successfully.
Restored My Apps
Click to expand...
Click to collapse
had no problem, well yeh first boot took its time to load but it did, i knew that A.S.K.P will take its time to boot for the first time so i let it be for like 4-8 mins.

4.3 issues

I have tried every method I can think of to get 4.3 to play nice with my phone. I have used Odin to flash stock and twrp, tried cwm recovery, tried beanstalk, hellybean, cm, and aokp. I changed twrp settings and infamous wipe. Everything I do always results with my phone getting stuck on the boot animation. Even if I clear caches, it will boot and get to the upgrading apps screen and then freeze and reboot and again stuck on the boot animation.
4.1.2 gets stuck on the kernel boot for me, 4.2.2 doesn't work with BT correctly. So frustrating.
Any suggestions are welcome.
4.3
dkrcubsfan said:
I have tried every method I can think of to get 4.3 to play nice with my phone. I have used Odin to flash stock and twrp, tried cwm recovery, tried beanstalk, hellybean, cm, and aokp. I changed twrp settings and infamous wipe. Everything I do always results with my phone getting stuck on the boot animation. Even if I clear caches, it will boot and get to the upgrading apps screen and then freeze and reboot and again stuck on the boot animation.
4.1.2 gets stuck on the kernel boot for me, 4.2.2 doesn't work with BT correctly. So frustrating.
Any suggestions are welcome.
Click to expand...
Click to collapse
Twrp 2.6.10 is the minimum. I am using 2.6.30. 2.6.00 will not work. Also wipe everything but SD. That includes android secure and preload.
stormannorman said:
Twrp 2.6.10 is the minimum. I am using 2.6.30. 2.6.00 will not work. Also wipe everything but SD. That includes android secure and preload.
Click to expand...
Click to collapse
Thanks, but I've tried all that.
Sent from my SGH-T989 using Tapatalk 4
dkrcubsfan said:
Thanks, but I've tried all that.
Sent from my SGH-T989 using Tapatalk 4
Click to expand...
Click to collapse
Twrp version 2.6.3.0 has bugs and is causing issues for a lot of people.
Make sure you use 2.6.1.0 and see how it goes.
Sent from my cellular telephone
kj2112 said:
Twrp version 2.6.3.0 has bugs and is causing issues for a lot of people.
Make sure you use 2.6.1.0 and see how it goes.
Sent from my cellular telephone
Click to expand...
Click to collapse
I have had Zero issues with 4.1 or 4.2 never bricked my phone---- until 4.3 I will tell you how i solved my problems - I have no boots, to 4.3 working but issues with data corruption and gapps crashing random apps crashing, finally after reading and reading i solved it.
1. Flash TWRP 2.6.1 (NOT 2.6.0, not 2.6.0.4 and especially NOT 2.6.3) any other recovery will not work properly - yes for some it may but some people seem to have some of the same problems.
2. Wipe data, Davlik, Cache and the prior rom. it has to be a clean wipe/flash
3. Flash Rom of choice (Black Liquid smooth is awesome)
4. Flash Standard gapps 08/13 (dont get fancy yet and flash slim gapps or inverted, just use the tried and true basic to get it working)
5. let the damn phone rest and settle 10 min minimum.
6. reboot to recovery, wipe Davlik and cache for good measure and fix permissions, reboot and enjoy.
dkrcubsfan said:
I have tried every method I can think of to get 4.3 to play nice with my phone. I have used Odin to flash stock and twrp, tried cwm recovery, tried beanstalk, hellybean, cm, and aokp. I changed twrp settings and infamous wipe. Everything I do always results with my phone getting stuck on the boot animation. Even if I clear caches, it will boot and get to the upgrading apps screen and then freeze and reboot and again stuck on the boot animation.
4.1.2 gets stuck on the kernel boot for me, 4.2.2 doesn't work with BT correctly. So frustrating.
Any suggestions are welcome.
Click to expand...
Click to collapse
if twrp keeps giving you problems like these maybe try doing it from cmw. ive read it gives way less problems than twrp:good:
Decimus Meridius said:
I have had Zero issues with 4.1 or 4.2 never bricked my phone---- until 4.3 I will tell you how i solved my problems - I have no boots, to 4.3 working but issues with data corruption and gapps crashing random apps crashing, finally after reading and reading i solved it.
1. Flash TWRP 2.6.1 (NOT 2.6.0, not 2.6.0.4 and especially NOT 2.6.3) any other recovery will not work properly - yes for some it may but some people seem to have some of the same problems.
2. Wipe data, Davlik, Cache and the prior rom. it has to be a clean wipe/flash
3. Flash Rom of choice (Black Liquid smooth is awesome)
4. Flash Standard gapps 08/13 (dont get fancy yet and flash slim gapps or inverted, just use the tried and true basic to get it working)
5. let the damn phone rest and settle 10 min minimum.
6. reboot to recovery, wipe Davlik and cache for good measure and fix permissions, reboot and enjoy.
Click to expand...
Click to collapse
This. 2.6.1.0 twrp.
Sent from my cellular telephone

Categories

Resources