Jb flash issue again - Samsung Galaxy Nexus

Been running jb for a bit now, tried sourcery, flashed fine, Ran added a mod or 2 phone stout down and that was it, I had this same issue with one of the first flash able jb roms where now, I can flash a from fine, but it just boot loops, I try to restore a back up and it give me an error while restoring data, I've tried doing advanced restores of everything but data, flashed clean aokp flashed the jb I was running before no matter what, same thing. New from boot loops restoring backup fails at data. Any ideas?
Sent from my Xoom using xda app-developers app

Also, last time this happened I reverted back to stock, locked boot loader, and started from scratch, losing everything, pictures, app backups, and I'd like to ha void doing this again if at all possible
Sent from my Xoom using xda app-developers app

What recovery are you using? Update your recovery through fastboot to cwm 6.0.1.0 or twrp 2.2.0.
Sent from my i9250

Related

Boot loop in jb roms

Before this I was in gummy toro ..then the first day that vicious jb roms out I manage to flash jb roms.. and its working.. then I try to flash different jb roms and it stock in Google animation..did everything clean flash delete all..then flash jb roms and again boot loop.. I unbrick my nexus using g.n. toolkit v7 back to stock..then set up everything then I try to flash a jb roms again yet again stock in boot loop.. any help pls... thanks in advance.
Sent from my Galaxy Nexus using XDA Premium App
landrian18 said:
Before this I was in gummy toro ..then the first day that vicious jb roms out I manage to flash jb roms.. and its working.. then I try to flash different jb roms and it stock in Google animation..did everything clean flash delete all..then flash jb roms and again boot loop.. I unbrick my nexus using g.n. toolkit v7 back to stock..then set up everything then I try to flash a jb roms again yet again stock in boot loop.. any help pls... thanks in advance.
Click to expand...
Click to collapse
What are you using to flash? ADB, ClockworkMod Recovery? My rule for ROMS has been: download to phone and ensure download was completed successfully, reboot to CWM recovery, wipe cache, wipe Dalvik, install ROM, wipe Dalvik again, reboot.
If you can provide any more info regarding your process I can try and help you out.
Which galaxy nexus version is yours? Which Roms did you install? Did all three wipes?
Sent from my Galaxy Nexus using xda app-developers app
@ooddiittyy,
I'm using the one from gnex toolkit v7(clockwork mod touch recovery) I did wipe data /factory reset 3times,wipe cache and wipe dalvik and I also format system,cache and data..reboot and stock in boot loop.. I did that to 3jb roms and same thing happens..so I restore to ics.and this time boot up well. This is the first time I've in counter something like this..been flashing since vibrant.
Sent from my Galaxy Nexus using XDA Premium App
landrian18 said:
I'm using the one from gnex toolkit v7(clockwork mod touch recovery)
Click to expand...
Click to collapse
this makes me die a little inside.
also, cwm touch is known to have issues with flashing stuff.
Oh.. so I think I should use rom manager.. to flash vicious-toro v3..
Sent from my Galaxy Nexus using XDA Premium App
Coming from gummy toro I manage to flash liquid vicious toro v1to v3 with no problem..then vanirbean rom and when I flash [email protected]_jelly that when its all started...I can flash ics rom and I can restore..but I can't flash jb roms..
Sent from my Galaxy Nexus using XDA Premium App
Try re downloading the rom again if its stuck at the Google animation let it sit for 5 to 15 minutes. It should boot up on its own. If not then there's something else wrong. But when I'm stuck at the Google logo with any jb rom I just let it sit. And eventually it boots up fine.
Sent from my Galaxy Nexus using xda premium
Thanks for the reply..I just flash it again I'm using 2 different jb rom and 2 different kernel..still stock in boot loop..I've waited for 30mins each in boot loop..before I had the vicious rom for almost a week then try different rom and this is what I got.. hayzz...
Sent from my Galaxy Nexus using XDA Premium App
did you change out your recovery to the regular cwm?
@zepius . Yep I did.. get it from from manager...
Sent from my Galaxy Nexus using XDA Premium App
landrian18 said:
Thanks for the reply..I just flash it again I'm using 2 different jb rom and 2 different kernel..still stock in boot loop..I've waited for 30mins each in boot loop..before I had the vicious rom for almost a week then try different rom and this is what I got.. hayzz...
Sent from my Galaxy Nexus using XDA Premium App
Click to expand...
Click to collapse
OK. Hmm. Go into recovery wipe everything 3x data/cache/dalvik cache flash the rom (don't flash a kernel) just the rom go back and reboot system now and see if that helps.
Edit: make sure u have over 50% battery before doing this.
Sent from my Galaxy Nexus using xda premium
I did that last night..wipe 3× everything.. did flash just rom, then rom with kernel, and also I did try wipe just cache and dalvik.. and also I did try format system, cache and data...
Edit: this is the first time it happen to me..even though I unbrick ,luck bootl. Factory reset .. its so weird...
Sent from my Galaxy Nexus using XDA Premium App
hey all,
not to highjack this thread, but I'm suddenly having the same issue.
I was on VanirBEAN v7 with the Popcorn Kernel that came with it.
I then flashed Franco's latest (384 GPU version).
Had no problems until last night when I let the phone run the battery all the way out and die completely. I let it charge for a bit, then tried booting and I'm stuck at the Google logo or get a reboot during the boot animation, depending on what I'm doing.
So here's what I've tried. All of these come with a wipe/cache/Davlik inbetween:
flash Vicious Toro JB V3 (stays on Google logo)
flash VanirBEAN v7 (reboots at VanirBEAN animation)
flash AOKP build 37 (reboots on the TeamKang animation)
selectively restore boot and system for AOKP 37 from a previous stable backup (reboots at the Android boot animation since in the ROM I had it set to not show the TeamKang boot animation)
I'm really at a loss right now. I'm trying a full restore on the backup I did before installing my first JB ROM.
edit: tried a full restore and i'm getting "Error while restoring /data!"... ugh.
Is my only choice to try Wugfresh's toolkit and restore stock and relock?
No one tried to fix permissions?
3x wipes, superwipe scripts..
That's not gonna help. If you wiped it once, it isn't there anymore.
I used wugfresh to back from fresh start and still if I flash jb rom I'm stock in jb rom.. done with 3 different jb rom. Same on all of them.. and yes I also did fix permission... I also did about mount and unmount regarding the system,cache and data... I'm tired of flashing and waiting in boot loop so I restore to ics gummy. I hope someone can help us with this...
Sent from my Galaxy Nexus using XDA Premium App
landrian18 said:
I used wugfresh to back from fresh start and still if I flash jb rom I'm stock in jb rom.. done with 3 different jb rom. Same on all of them.. and yes I also did fix permission... I also did about mount and unmount regarding the system,cache and data... I'm tired of flashing and waiting in boot loop so I restore to ics gummy. I hope someone can help us with this...
Sent from my Galaxy Nexus using XDA Premium App
Click to expand...
Click to collapse
I suppose you could try reinstalling the bootloader, or using one of the recent JB bootloaders and see if that helps. I can't think of a good reason why this should be happening based on what you've described, however. I assume you've checked obvious stuff like the MD5 sums on all your downloaded ROMs, etc?
Hi everybody!
I have identical issue, I did all possible, now I´m close to give it up. Yes, I checked all downloaded files by MD5 sums, I tried latest CWM, latest TWRP, gnex-JB-bootloader (…lc03). Today I tried also “Super_Wipe_Lite_Nexus”, but I can´t jump boot animation. I´m flashing roms long time, but this magic never happened. What else we should try to clear/delete?

tried many things to get to JB. still getting stuck?

Hey guys.
I was running paranoid android 4.0.4 and t was good but I wanted to go to JB. I tried for a long time and it kept getting stuck at the bootloader loop screen.
I formatted sdcard, went back to stock. Back to square one. got TWRP and rooted it.
It tells me there is an update I can go from 4.0.4 to 4.1 and I allow it and it STILL gets stuck at the bootloader loop.
I tried to manually put in a ROM again, the black AOKP one and still stuck in the loop.
I haven't got a custom launcher or anything. pretty much running stock and wanted to get to JB...
my phone is maguro.
Anyone have any ideas?
anyone?!
Are you talking about an OTA Official update? If so you need stock recovery, bootloader and radio. You can't flash an OTA without these. If you really want to go down this route, you will need to flash factory images for your device and start from fresh.
Sent from my Galaxy Nexus using xda app-developers app
Have you tried CM10? I have had great luck on Euroskank. I tried AOKP this morning and ended up stuck in a bootloop but Euroskank AOSP and AOKP have both been great. Also I use the 0726 gapps.
Sent from my Galaxy Nexus using xda app-developers app
Xfanatic said:
Have you tried CM10? I have had great luck on Euroskank. I tried AOKP this morning and ended up stuck in a bootloop but Euroskank AOSP and AOKP have both been great. Also I use the 0726 gapps.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
thanks! I will try these tomorrow!
Download the following: Superwipe zip, and Jelly Bean Bootloader zip
http://d-h.st/jcO Bootloader
http://www.mediafire.com/?lxpw84fwtm5cj6w Superwipe Script
Use clockworkmod and flash the superwipe choosing install zip from sd first the the same for the bootloader then flash your rom. Let it boot up which can take a couple minutes at the boot screen
What worked for me was the Galaxy Nexus Toolkit. It allows you to wipe the entire system and replace it with a factory image. The factory image for stock JB is available now, so it's as easy as a couple clicks. It's the only thing that worked for me completely, i.e., no sdcard0 bug.
NB: It wipes EVERYTHING!!!!! Backup anything important.

Nandroid Restore Help

I'm new to Samsung Android phones, and new to the E4GT, so I need a little help.
I always flash the zip for the EL26 CWM5 recovery like instructed, soooo, here is my issue.
I'm running AOSP and thought I would try CM10 JB, soooo, I flashed into EL26, performed a full nandroid to my Ext SD. I flashed JB and gave it a shot. For issues known to all, I wanted to switch back
So, I went into recovery, flashed the EL26 recovery and rebooted recovery, I then restore the nandroid backup I just made, rebooted, went to the Samsung screen (with the yellow !). After some time, about 20-30 seconds, it goes to a black screen indefinately until I pull the battery.
Any ideas? I have yet to get a nandroid to work on this device. Had no issues at all on my 3D. I'm sure I'm doing something wrong.
TIA,
Tee Jay
You need to flash the AOSP kernel. Well first can you boot into recovery or download mode
Sent from my SPH-D710 using XDA
g_ding84 said:
You need to flash the AOSP kernel. Well first can you boot into recovery or download mode
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Yeah I can get into recovery fine, so I flashed an AOSP kernel and then my wifi didn't work.
Is it not connecting?
Sent from my SPH-D710 using XDA
g_ding84 said:
Is it not connecting?
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Nope, won't even turn on. But if I do a full clean flash of the exact ROM, it works fine.
I'm by far no expert but I'd say the kernel is being replaced by the gb recovery kernel when you flash back for your safe recovery.I personally keep a couple various recoveries so I can nandroid backup on the kernel native to the Rom and then the backup will contain the proper kernel.I think I got that right.so....nandroid b4 recovery has been my habit.
Had this issue before, minus the yellow triangle....anytime you're on an aosp rom and do a nand via el26, the nand stores the last kernel used (which is GB el26). After you restore, wipe cache and dalvik and then flash an aosp kernel, probly one from chris41g. Reboot and should he good to go.
Sent from my SPH-D710 using xda app-developers app
dante32278 said:
Had this issue before, minus the yellow triangle....anytime you're on an aosp rom and do a nand via el26, the nand stores the last kernel used (which is GB el26). After you restore, wipe cache and dalvik and then flash an aosp kernel, probly one from chris41g. Reboot and should he good to go.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Right, I tried that with my AOKP backup, I was able to boot. But then my WiFi wasn't working because of something to do with the Kernel I'm assuming

Rom Manager Recovery 6.0.1.4

Ive been using recovery 5.0.2.7 and I flashed new Recovery 6.0.1.4 threw rom manager today and it almost screwed my phone. I booted into 6.0.1.4 and it would not flash anything. I rebooted and my phone was stuck on boot loop. Luckily I made a backup on the old recovery. it took forever when i restored (30 mins stuck on restoring). and it didnt even say complete. I had to pull battery, powered back on and restore had actually completed (lucky) ....Has anybody flashed recovery 6.0.14 and experienced this issue?
Sent from my SGH-T989 using xda premium
Hoezack said:
Ive been using recovery 5.0.2.7 and I flashed new Recovery 6.0.1.4 threw rom manager today and it almost screwed my phone. I booted into 6.0.1.4 and it would not flash anything. I rebooted and my phone was stuck on boot loop. Luckily I made a backup on the old recovery. it took forever when i restored (30 mins stuck on restoring). and it didnt even say complete. I had to pull battery, powered back on and restore had actually completed (lucky) ....Has anybody flashed recovery 6.0.14 and experienced this issue?
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Yea, It almost ruined my phone as well. I ended up having to restore to an older version. It wouldnt let me flash anything, constantly hung or restarted, and never actually told me that it finished, though when I rebooted it turned out that it did finish flashing, although much of it was messed up, almost like it only flashed certain parts of the rom.
I've had very similar experience with 6.0.1.4.
I'm glad I'm not alone, I thought it was just something I did wrong.
Sent from my SGH-T989 using xda premium
mth785 said:
I'm glad I'm not alone, I thought it was just something I did wrong.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Why they have released the update is puzzle to me? Its bad. 5.0.2.7 is the best.
ksrikanthreddy777 said:
Why they have released the update is puzzle to me? Its bad. 5.0.2.7 is the best.
Click to expand...
Click to collapse
5.0.2.7 cache wipes and fix permissions do not work for ics hence the scripts. 6.0.1.2 worked great. i've had problems with 6.0.1.3 and eventually started using twrp. no regrets.
I'm using sk8's CWM 6.0.something touch recovery and everything is working.
Sent from my SAMSUNG-SGH-T989 using xda premium
I didn't flash 6.0.1.4 from ROM Manager (blackwing version), but I flashed it from CWM and I just got a boot loop while trying to install CM9 09-23 Nightly.
Did a battle pull, and tried to do stuff in CWM6 and it was super slow and nothing would flash. I couldn't even wipe caches or do a factory reset.
I ended up doing a Restore (which never finished) but did a battery pull and luckily I was able to boot into my previous ROM.
I never had any issues with 5.0.2.7 thanks to Darkside Super Wipe and Cache scripts, even flashing ICS and JB ROMs.
freedom_xda said:
I didn't flash 6.0.1.4 from ROM Manager (blackwing version), but I flashed it from CWM and I just got a boot loop while trying to install CM9 09-23 Nightly.
Did a battle pull, and tried to do stuff in CWM6 and it was super slow and nothing would flash. I couldn't even wipe caches or do a factory reset.
I ended up doing a Restore (which never finished) but did a battery pull and luckily I was able to boot into my previous ROM.
I never had any issues with 5.0.2.7 thanks to Darkside Super Wipe and Cache scripts, even flashing ICS and JB ROMs.
Click to expand...
Click to collapse
Yeah I had the same problem so I had to go back to 5.0.2.7.... Wit this version I have no problems backing and restoring roms.....Also with this version I can flash any rom ics, aokp, gb
Sent from my SGH-T989 using xda app-developers app
I'm currently using sk8's cwm6.0.1.4 and no issues so far.
pepe7053 said:
Yeah I had the same problem so I had to go back to 5.0.2.7.... Wit this version I have no problems backing and restoring roms.....Also with this version I can flash any rom ics, aokp, gb
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
I had the same issue with 6.0.1.4 non-touch. But the touch version is working just fine.
Make sure you wipe dalvik cache and wipe partition before flash.
wow, I also had flashed the non-touch recovery and that's when I started getting all my problems.
I'm still using v5.0.26 and darkside superwipe, no issue at all roms
Twrp 2.2.2 is stable
another case of a product becoming a paid product while losing quality in the process.
Im currently running a Nandroid backup using 6.0.1.4 and its hella slow... like 20+ mins and still running, this is beyond bad. On 5.0.2.7 it ran in about 5mins.
Is the touch recovery better?
Edit: Now its at almost 40 mins... yeesh
Hoezack said:
Ive been using recovery 5.0.2.7 and I flashed new Recovery 6.0.1.4 threw rom manager today and it almost screwed my phone. I booted into 6.0.1.4 and it would not flash anything. I rebooted and my phone was stuck on boot loop. Luckily I made a backup on the old recovery. it took forever when i restored (30 mins stuck on restoring). and it didnt even say complete. I had to pull battery, powered back on and restore had actually completed (lucky) ....Has anybody flashed recovery 6.0.14 and experienced this issue?
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
I had the same exact problem with it yesterday. I was trying to restore my backup, so I tried to do a wipe/reset and it wouldn't do anything. So I just restored my backup anyway and it would always just stop at restoring secure.android. So I took out the battery and rebooted and my backup was restored. So I tried ROM manager to flash back to 5.0.2.7. But it constantly forced closed. So long story short, I'm now using twrp and I like it better.
Omg I thought I was the only one with this problem. Took me forever to get my phone working again. Had to Odin back to stock. 6.0.1.4 touch was working fine though (installed using Odin)
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Hmm.. ROM manager flashed 6.0.1.4 just fine on my phone. I've done this procedure about 4 times too. Weird.
Sent from my SAMSUNG-SGH-T989 using xda premium
Khameleon said:
Im currently running a Nandroid backup using 6.0.1.4 and its hella slow... like 20+ mins and still running, this is beyond bad. On 5.0.2.7 it ran in about 5mins.
Is the touch recovery better?
Edit: Now its at almost 40 mins... yeesh
Click to expand...
Click to collapse
on 6.0.1.4 and 6.0.1.5, mine just hangs on "backing up .android_secure" and the progress bar never moves. I've waited up to 40 minutes with no progress. I've never completed a backup since I switched from 5.0.2.7. I'm going to switch to another recovery.

Phone Dead, Bad Night, Help Wanted

I flashed TWRP 2.5 and then flashed Task's AOKP 4/9 ROM and everything went down hill from there. The phone kept rebooting after a minute or so, so I did a factory reset and reflashed the ROM. That didn't help, it actually made it worse in that it would not get past the kernel splash screen. So I did another wipe and the same thing. I wiped again and flashed an older version of AOKP 4/5 and again would only get to the kernel splash. After another hour or so I decided I'll just go back to rooted stock, so using Odin 3 3.07 I flashed my trusted root69.stock_ATT_I747UCALG1 image and now it just stays on the Samsung screen.
I've run out of thoughts on what the hell is the problem and thought I'd ask.
Anyone have any suggestions on what I can do to get this paper weight working again?
dhostetter said:
I flashed TWRP 2.5 and then flashed Task's AOKP 4/9 ROM and everything went down hill from there. The phone kept rebooting after a minute or so, so I did a factory reset and reflashed the ROM. That didn't help, it actually made it worse in that it would not get past the kernel splash screen. So I did another wipe and the same thing. I wiped again and flashed an older version of AOKP 4/5 and again would only get to the kernel splash. After another hour or so I decided I'll just go back to rooted stock, so using Odin 3 3.07 I flashed my trusted root69.stock_ATT_I747UCALG1 image and now it just stays on the Samsung screen.
I've run out of thoughts on what the hell is the problem and thought I'd ask.
Anyone have any suggestions on what I can do to get this paper weight working again?
Click to expand...
Click to collapse
Not sure about the problem with aokp. But your bootloop just pull the battery, reinstall battery, go into stock recovery, factory reset and voilà
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
KorGuy123 said:
Not sure about the problem with aokp. But your bootloop just pull the battery, reinstall battery, go into stock recovery, factory reset and voilà
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
This will do it. Flashing back to 4.0.4 will bootlopp until you factory reset in stock recovery
Sent from my SAMSUNG-SGH-I747 using xda premium
Same thing happened to me. Boot loop with 4/9 AOKP task so I Odin to the same file as you but that ran just fine. I would try to Odin again.
Oh and after stock with root I flashed 4/9 and all was good. By chance did you have custom boot animation?
Sent from my SGH-I747 using xda premium
drock212 said:
Same thing happened to me. Boot loop with 4/9 AOKP task so I Odin to the same file as you but that ran just fine. I would try to Odin again.
Oh and after stock with root I flashed 4/9 and all was good. By chance did you have custom boot animation?
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
Yes I had a custom boot image.
Getting ready to factory reset and reboot. Hope all goes well.....
dhostetter said:
Yes I had a custom boot image.
Getting ready to factory reset and reboot. Hope all goes well.....
Click to expand...
Click to collapse
I think it's the custom boot causing this issue. Anyway good luck. I know my heart skipped a beat when my phone would boot loop while to get into recovery. Once I Odined back to stock with root first/only thing I downloaded was goomanager and installed TWRP then flashed 4/9.
Sent from my SGH-I747 using xda premium
drock212 said:
I think it's the custom boot causing this issue. Anyway good luck. I know my heart skipped a beat when my phone would boot loop while to get into recovery. Once I Odined back to stock with root first/only thing I downloaded was goomanager and installed TWRP then flashed 4/9.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
I'm back up and running again. A little embarrassed I forgot the factory reset last night.
Thanks for the reminder!
AOKP is a great ROM.
When flashing ROMs always follow these steps and you will be fine.
1- nandroid backup
2- format system
3- wipe cache
4- wipe Dalvik
5- factory reset.
Most suggest doing each 3 times.
6- install ROM and reboot
7- flash gapps
Let sit for 10 minutes.
Follow those instructions and everything will be fine.
Sent from my SGH-I747M

Categories

Resources