This isn't my first android root but I'm stuck. I followed the video for rooting my Nexus 10. Got stuck in a boot loop but was able to flash cwm but still in boot loop. I tried doing the factory reset and now cwm is gone too and still stuck in boot loop. Do I need to reflash the stock recovery and if so where do I find that to download?
flash tbe cwm recovery again via fastboot, transfer your custom rom of choice from your desktop to your device, wipe data (factory reset), then flash that rom via cwm. btw, this is a galaxy nexus forums
Daethian said:
This isn't my first android root but I'm stuck. I followed the video for rooting my Nexus 10. Got stuck in a boot loop but was able to flash cwm but still in boot loop. I tried doing the factory reset and now cwm is gone too and still stuck in boot loop. Do I need to reflash the stock recovery and if so where do I find that to download?
Click to expand...
Click to collapse
simms22 said:
flash tbe cwm recovery again via fastboot, transfer your custom rom of choice from your desktop to your device, wipe data (factory reset), then flash that rom via cwm. btw, this is a galaxy nexus forums
Click to expand...
Click to collapse
Sorry! So I did try that but still get the android guy with the red ! when I try to go into recovery.
Daethian said:
Sorry! So I did try that but still get the android guy with the red ! when I try to go into recovery.
Click to expand...
Click to collapse
and the recovery flashed fine? did you "fastboot devices" to make sure fastboot can see your device? sometimes these recoveries need to ne flashed a few times before they take. try flashing it two or three times in a rom. did you try twrp recovery? you might like that recovery better.
op, rename/delete /system/recovery-from-boot.p and reflash your custom recovery;
RANT: GOD DAMN IT, WHERE'S MY NEXUS 10!!!??? BEEN WAITING FOR 2 GODAMN MONTHS! - Sorry, it's just that I've been going through some **** to get my hands on one - AND THERE'S PEOPLE WHO'S GOT 2!!!
FOLLOWUP:
I ran MSkip toolkit and it repaired everything. I got a failed on renaming my recovery images so my stock recovery images are just gone I guess? Anyway I'm good. Rooted and repaired thanks to Skips toolkit.
Thanks for all the help!
-------------
It appears to be flashing fine and yes it sees my device. I tried multiple reflashing this am and still no joy.
I reposted in the right place and got some help but not done yet. I think mod might delete this thread since I have the other one going.
simms22 said:
and the recovery flashed fine? did you "fastboot devices" to make sure fastboot can see your device? sometimes these recoveries need to ne flashed a few times before they take. try flashing it two or three times in a rom. did you try twrp recovery? you might like that recovery better.
Click to expand...
Click to collapse
Hi guys I've been searching and cant seem to find an answer. My xt907 is rooted and my boot loader is unlocked I'm running CWM. If i install any 4.3 roms they work great for initial boot but as soon as i reboot it hangs at the warning boot loader unlocked screen. And the only way i can get the phone working again is to get to ap fastboot and use the DROID_RAZR_M_Utility_1.20 to factory reset everything. If i flash a 4.2.2 rom i don't have any problems. Any ideas guys ? Ive searched and cant seem to find an answer anywhere. Thanks in advance!
My first flash of 4.3 did this... after that I used twrp and haven't had it happen since...
Sent from my XT907 using xda app-developers app
The latest TWRP+mounting system prior to data/system wipes will probably solve your problems. Also, if you have a backup stored, you shouldn't need to fastboot every time.
I've been having the same problem. I thought it might be because I was using CWM, so I thought I'd give it a go with TWRP 2.323. I made a backup, wiped System, Formatted Data and wiped cache and Dalvik cache and installed [ROM][4.4.1][Official][OSE Rom][XT907].
It installed and booted up fine. After a restart, it hung on the bootloader screen. After booting up into TWRP and restoring the backup, it's still hanging on the bootloader unlocked screen. Doh!
I just reinstalled the new ROM and will hope I don't have to restart while I'm out today. Any ideas on things I can try to get things working?
Ryan F said:
I've been having the same problem. I thought it might be because I was using CWM, so I thought I'd give it a go with TWRP 2.323. I made a backup, wiped System, Formatted Data and wiped cache and Dalvik cache and installed [ROM][4.4.1][Official][OSE Rom][XT907].
It installed and booted up fine. After a restart, it hung on the bootloader screen. After booting up into TWRP and restoring the backup, it's still hanging on the bootloader unlocked screen. Doh!
I just reinstalled the new ROM and will hope I don't have to restart while I'm out today. Any ideas on things I can try to get things working?
Click to expand...
Click to collapse
twrp 2323???
You need twrp 2630
see my goodies.
aviwdoowks said:
twrp 2323???
You need twrp 2630
see my goodies.
Click to expand...
Click to collapse
Okay, I downloaded xt907-twrp-2.6.3.0. In trying to flash with fastboot, it's hanging on <waiting for device>. USB Debugging is enabled and the device is showing up. Thanks for the help!
Ryan F said:
Okay, I downloaded xt907-twrp-2.6.3.0. In trying to flash with fastboot, it's hanging on <waiting for device>. USB Debugging is enabled and the device is showing up. Thanks for the help!
Click to expand...
Click to collapse
Fastboot!
Extract the recovery.img from the zip.
But why do that, just flash the zip from your twrp you now have installed
Ryan F said:
Okay, I downloaded xt907-twrp-2.6.3.0. In trying to flash with fastboot, it's hanging on <waiting for device>. USB Debugging is enabled and the device is showing up. Thanks for the help!
Click to expand...
Click to collapse
I believe the one that Avi has is a .zip, not a .xml, so it needs to be flashed in recovery. Load it up on your SD, boot into the recovery you have now, flash the new recovery, and then reboot recovery.
TWRP 2.6.3.0 flashed successfully. Unfortunately, that didn't help at all. My phone still froze on the boot screen. I then booted into the new recovery, wiped everything and reinstalled the rom. Now it won't even boot the first time into the ROM, it just freezes on the boot screen. Help!
*EDIT
I just reinstalled it again and formatted data on top of the wipes this time. It booted into the new rom this time, but it did not get past the boot screen after restarting still.
Ryan F said:
TWRP 2.6.3.0 flashed successfully. Unfortunately, that didn't help at all. My phone still froze on the boot screen. I then booted into the new recovery, wiped everything and reinstalled the rom. Now it won't even boot the first time into the ROM, it just freezes on the boot screen. Help!
*EDIT
I just reinstalled it again and formatted data on top of the wipes this time. It booted into the new rom this time, but it did not get past the boot screen after restarting still.
Click to expand...
Click to collapse
If your rom DL is corrupt?
Also
Arrrghhh has advice on twrp 263, http://forum.xda-developers.com/showthread.php?goto=newpost&t=2573153
It should apply to our 263 also.
---------- Post added at 11:40 PM ---------- Previous post was at 11:29 PM ----------
I use their version (Q)(EDIT ONLY 261 HAS USB MOUNT) and it has usb mount! But it is hard to navigate but I am used to it
Ryan F said:
TWRP 2.6.3.0 flashed successfully. Unfortunately, that didn't help at all. My phone still froze on the boot screen. I then booted into the new recovery, wiped everything and reinstalled the rom. Now it won't even boot the first time into the ROM, it just freezes on the boot screen. Help!
*EDIT
I just reinstalled it again and formatted data on top of the wipes this time. It booted into the new rom this time, but it did not get past the boot screen after restarting still.
Click to expand...
Click to collapse
Many people ran into this issue when 4.3 came out and then someone realized that we were forgetting something when wiping. It was something that we did when the BL was first unlocked, but everyone seemed to forget about it. We were forgetting to mount system, prior to performing wipes of the data/caches. Like Avi said, first, I would DL the ROM again and then place it in your SD. When you wipe, do the FDR option first. After that, go into mount and mount system. Then, go into the advanced wipe options and wipe data, system, cache/dalvik, and format data again. At this point, you can install the ROM as normal, don't re-mount system prior to installing, though. When I am done wiping, I always reboot recovery, but you don't have to do that.
aviwdoowks said:
If your rom DL is corrupt?
Also
Arrrghhh has advice on twrp 263, http://forum.xda-developers.com/showthread.php?goto=newpost&t=2573153
It should apply to our 263 also.
---------- Post added at 11:40 PM ---------- Previous post was at 11:29 PM ----------
I use their version (Q)(EDIT ONLY 261 HAS USB MOUNT) and it has usb mount! But it is hard to navigate but I am used to it
Click to expand...
Click to collapse
Okay, I downloaded the zips again to make sure. This freezing at bootloader screen has happened with every of the dozen or so roms I've tried installing over the past 6 months since I unlocked the bootloader.
RikRong said:
Many people ran into this issue when 4.3 came out and then someone realized that we were forgetting something when wiping. It was something that we did when the BL was first unlocked, but everyone seemed to forget about it. We were forgetting to mount system, prior to performing wipes of the data/caches. Like Avi said, first, I would DL the ROM again and then place it in your SD. When you wipe, do the FDR option first. After that, go into mount and mount system. Then, go into the advanced wipe options and wipe data, system, cache/dalvik, and format data again. At this point, you can install the ROM as normal, don't re-mount system prior to installing, though. When I am done wiping, I always reboot recovery, but you don't have to do that.
Click to expand...
Click to collapse
Could you clarify a little bit?
1.) Mount system
2.) Wipe (Factory Reset: data, cache, dalvik)
3.) Format data
4.) Install zips
What's the FDR option?
---------- Post added at 09:21 AM ---------- Previous post was at 09:07 AM ----------
Ryan F said:
1.) Mount system
2.) Wipe (Factory Reset: data, cache, dalvik)
3.) Format data
4.) Install zips
Click to expand...
Click to collapse
Following the above steps didn't solve it The rom installs fine, boots up for first time normally, but still freezes on the bootloader screen after a restart.
Try geting to the bootloader options & choose normal pwr up.
The new twrp will stick at the big M sometimes.
Then the file is bad or you are missing the install steps. FDR (Factory Data Reset) is the first option you get when you go into the wipe menu, before you go into advanced options. Make sure you're wiping system too, after you mount. If it doesn't work, then it's a bad file or you're still doing something wrong. Upgrading to the most current TWRP and mounting system fixed the issues for 99% of the people. The other 1% just have one of those phones that is "quirky."
okay not sure if your still having this problem. But i never did solve my issue just kept using 4.2.2. But i just flashed the new jbx kernel and a KitKat rom the other along with the newest version on safestrap and i have no issues. Everything flashed and installed perfectly and it boots like a champ. So maybe just skip over 4.3 like i did and see if you still have the issues. Sorry didnt see you were trying to flash 4.4. Only thing i can suggest is make sure you have newest safestrap and wipe out the old etc. But im sure everyone already touched on this stuff before me
beady1 said:
okay not sure if your still having this problem. But i never did solve my issue just kept using 4.2.2. But i just flashed the new jbx kernel and a KitKat rom the other along with the newest version on safestrap and i have no issues. Everything flashed and installed perfectly and it boots like a champ. So maybe just skip over 4.3 like i did and see if you still have the issues. Sorry didnt see you were trying to flash 4.4. Only thing i can suggest is make sure you have newest safestrap and wipe out the old etc. But im sure everyone already touched on this stuff before me
Click to expand...
Click to collapse
Part of your problem is because you are using SS. If you're BL is unlocked, get rid of SS and use CWM or TWRP. SS is not a real recovery replacement, your stock recovery is still there. That's probably part of the reason you had issues.
possibly but i have 0 issues now so its not a big deal.
I have the stable Cyanogenmod 10.1 installed on my phone now. I'm able to restart my phone without any consequences finally. Yay.
I also tried the cm-11-20131221-NIGHTLY-xt907.zip build. That one would initially start up fine, but a restart gave me the frozen bootloader screen. I tried it twice, redownloading it, too. Gah, it's frustrating not being able to try out different roms, but at least I have one that works!
Well, thanks for the help guys. I'd still like to be able to install other roms, so if anyone else has something I can try, I'll do it!
Just recently rooted my s4, was working fine or so I thought, went to flash NamelessROM, I don't think the rom is the issue, I had my s2 rooted and flashed on a weekly basis so I know about wiping, data cache, and dalvik, I flashed Rom then Gapps, and it was stuck on boot up, of course I made a nandroid and restored, but now I'm stuck on the yellow sprint screen, did my research and found it it's called a Yellow Brick, or referred to as. Found out a possible fix was downloading the kernel so I've chosen the Rooted NoData kernel to download and flash via odin. Is this what I should do or is there a better fix out there?
Sounds like you wiped everything. Can you boot into recovery?
Beezer80 said:
Sounds like you wiped everything. Can you boot into recovery?
Click to expand...
Click to collapse
Yes I can, and I tried to restore back from my nandroid which is how I'm stuck on yellow sprint screen now versus stuck on the boot for NamelessROM.
Do a factory reset in recovery and see if it boots.
That will wipe your accounts and what not but you can't boot anyway.
If it won't boot then you'll need to flash a ROM to get running. Do you still have the ROM you wish to flash on your SD card or internal storage?
Beezer80 said:
Do a factory reset in recovery and see if it boots.
That will wipe your accounts and what not but you can't boot anyway.
If it won't boot then you'll need to flash a ROM to get running. Do you still have the ROM you wish to flash on your SD card or internal storage?
Click to expand...
Click to collapse
Just got me stuck on NamelessROM boot up so I'm restoring off nandroid again. I think that flashing the kernel will fix it.
I'd get the ROM booting then play with the kernel. That's just me though.
Beezer80 said:
I'd get the ROM booting then play with the kernel. That's just me though.
Click to expand...
Click to collapse
trying that right now
JosephBallin said:
trying that right now
Click to expand...
Click to collapse
I'm trying to push a kernel through odin, I could possible try to find a way to put a kernel on my extsd and try and flash it through twrp? Would I just have to wipe cache and dalvik and flash? because when I try through odin it fails.
EDIT: I found a fix it involves unrooting most likely, but if I do I'll be back at VPUAMDC (Android 4.2.2) so could I still root with SafeRoot? Or what would be the way to root from that version?
Which firmware version did you root from? If it was MJA or MK2 you have to use one of those, you can't downgrade to MDC easily.
I have a 2012 Nexus 7. At the time it had a locked bootloader but it was rooted with cm11 & TWRP on board. I downloaded the Nexus toolkit & tried to upgrade to lollipop when it was officially released. Somewhere along the line, I think the system partition got corrupted. I can manually flash all IMG files except system. I can get into bootloader & recovery. I even tried flashing TWRP again to reflash cm. TWRP took but cm failed to install. Anyone else have this issue? The tablet appears to boot but it just gets stuck at the Google screen with the lock at the bottom. Never goes past that point. Any help to revive this tablet would be much appreciated.
Beast84 said:
I have a 2012 Nexus 7. At the time it had a locked bootloader but it was rooted with cm11 & TWRP on board. I downloaded the Nexus toolkit & tried to upgrade to lollipop when it was officially released. Somewhere along the line, I think the system partition got corrupted. I can manually flash all IMG files except system. I can get into bootloader & recovery. I even tried flashing TWRP again to reflash cm. TWRP took but cm failed to install. Anyone else have this issue? The tablet appears to boot but it just gets stuck at the Google screen with the lock at the bottom. Never goes past that point. Any help to revive this tablet would be much appreciated.
Click to expand...
Click to collapse
Can you enter recovery or fastboot mode? If so, use either to attempt and repair (format) the system partition, then reflash the ROM of your choice.
PrizmaticSmoke said:
Can you enter recovery or fastboot mode? If so, use either to attempt and repair (format) the system partition, then reflash the ROM of your choice.
Click to expand...
Click to collapse
I already did. I flashed stock recovery & factory reset. Still the same thing. I flashed TWRP, the roms flashed through there just fail
Bumping to see if anyone else can help...
Beast84 said:
I already did. I flashed stock recovery & factory reset. Still the same thing. I flashed TWRP, the roms flashed through there just fail
Click to expand...
Click to collapse
In Twrp recovery,
1. go to wipe menu and advanced wipe.
2. select system partition then tap repair.
3.Flash your rom
Paramesh96 said:
In Twrp recovery,
1. go to wipe menu and advanced wipe.
2. select system partition then tap repair.
3.Flash your rom
Click to expand...
Click to collapse
Ok so that worked to flash cm but will this continue to happen if I try flashing the official lollipop update? I'm trying to return to stock so I can give the tablet to my nephew. I don't want him jumping into recovery or bootloader & wrecking it for good