So, I have a brand new Nexus 7 that I am unable to get any custom ROM to boot on. I have no problems unlockings, rooting or installing custom recoveries. What happens once I flash the ROM is it boots up and then gets stuck at the bootloader (nexus X). Ive tried everything I can think of; used WUGs toolkit, mskips toolkit, used CWM and TWRP to flash, tried upgrading to different version of JB then flashing. Same thing happens everytime. If someone could help me out it would be appreciated.
UPGRAYED05 said:
So, I have a brand new Nexus 7 that I am unable to get any custom ROM to boot on. I have no problems unlockings, rooting or installing custom recoveries. What happens once I flash the ROM is it boots up and then gets stuck at the bootloader (nexus X). Ive tried everything I can think of; used WUGs toolkit, mskips toolkit, used CWM and TWRP to flash, tried upgrading to different version of JB then flashing. Same thing happens everytime. If someone could help me out it would be appreciated.
Click to expand...
Click to collapse
Did you perform a factory reset, wipe cache, wipe dalvik before you installed your custom rom?
Leonhan said:
Did you perform a factory reset, wipe cache, wipe dalvik before you installed your custom rom?
Click to expand...
Click to collapse
Yup
That's odd..
Can you flash back to stock without problems? ... ?
Rgrds,
Ged.
GedBlake said:
That's odd..
Can you flash back to stock without problems? ... ?
Rgrds,
Ged.
Click to expand...
Click to collapse
Yea, I have tried a couple stock ROMs and I have no problems flashing back to those. I've also tried about 3 custom ROMs and for all of them I get stuck at the bootloader during boot.
UPGRAYED05 said:
Yea, I have tried a couple stock ROMs and I have no problems flashing back to those. I've also tried about 3 custom ROMs and for all of them I get stuck at the bootloader during boot.
Click to expand...
Click to collapse
I don't think you're getting stuck at the bootloader (depicted by a GOOGLE ANDROID lying on it's back) and the word START adjacent to the power-on button...
UPGRAYED05 said:
'...it boots up and then gets stuck at the bootloader (nexus X)...'
Click to expand...
Click to collapse
...you're getting stuck at the boot animation... which implies /system is in play...
---
Which ROMs have you flashed? (custom and/or stock)... and how did you flash them?... via toolkit, fastboot or custom recovery (CWM/TWRP)?
Specifics, please ?.
Rgrds,
Ged.
GedBlake said:
I don't think you're getting stuck at the bootloader (depicted by a GOOGLE ANDROID lying on it's back) and the word START adjacent to the power-on button...
...you're getting stuck at the boot animation... which implies /system is in play...
---
Which ROMs have you flashed? (custom and/or stock)... and how did you flash them?... via toolkit or fastboot?
Specifics, please ?.
Rgrds,
Ged.
Click to expand...
Click to collapse
Your right, I am stuck at the boot animation. Sorry about the mix up. These are the two ROMs I have tried:
http://forum.xda-developers.com/showthread.php?t=1899024
http://forum.xda-developers.com/showthread.php?t=2077396
I have tried flashing them with WUGs toolkit, mskip's toolkit, TWRP and CWM. Same thing happens everytime, stuck at the animation. I have even let it sit there for like 12 hours to see if it would eventually work through the boot but it doesnt.
No one has any advice or can point me in the right direction?
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
What version are you on 4.2.1 or 4.2.2 ?
d
I've tried both, same results.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
I am thinking you may be installing a 4.2.1 rom to your 4.2.2 os or vice versa.
d
The ROMs I would like to flash are 4.2.2 but I've used most if not all the available stock ROMs as my starting point.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
You performed a factory reset (/data wipe) have you performed a /system wipe?
Sent from my Nexus 4 using Tapatalk 2
Have you just tried updating to a new kernel just to see if it sticks? No factory reset or wipe need when updating kernel but it wont hurt...
d
---------- Post added at 05:28 PM ---------- Previous post was at 05:13 PM ----------
So remember its:
Factory reset
install rom
install gapps
install kernel (some say to install AFTER booting into new rom but I have had no probs doing this way)
wipe data cache/dalvik (some say to do it twice)
boot
d
It really sounds like you are not doing a factory reset before trying to boot.
Sent from my Nexus 7 using Tapatalk HD
Related
I tried to install a new rom after updating TWRP 2.3.0.0. after all was complete it stuck on the boot screen. I then tried with the Nexus Root Toolkit to use a restore from backup. Same problem. I then tried to flash stock and unroot. Same problem. I then tried a number of things through TWRP from backups I had their. Same problem. At present I have no OS and I can only boot into TWRP, turn if off or look at the GOOGLE screen. I have run out of ideas and would appreciate any help offered.
If you have tried everything else (flashing a ROM zip etc.) Then you should flash the factory image from Google.
Don't use the script/batch file as that will wipe your internal storage.
Just flash system and boot.
Sent from my Nexus 7 using xda premium
Sometimes a rom takes a long time to boot for the first time, please be very patient. Also, try wiping everything from /system, and then re install a custom rom from your /sdcard partition. also make sure your roms are for the nexus 7 not galaxy nexus or other similar devices. ONE MORE THING 4.1.2 wont flash with 4.1.1 bootloader.
jmtend said:
I tried to install a new rom after updating TWRP 2.3.0.0. after all was complete it stuck on the boot screen. I then tried with the Nexus Root Toolkit to use a restore from backup. Same problem. I then tried to flash stock and unroot. Same problem. I then tried a number of things through TWRP from backups I had their. Same problem. At present I have no OS and I can only boot into TWRP, turn if off or look at the GOOGLE screen. I have run out of ideas and would appreciate any help offered.
Click to expand...
Click to collapse
There was a bug in TWRP V2.3.0.0 use fastboot to flash V2.3.1.0 and then reflash the rom
Sent from my BAKED Nexus
spaceman860 said:
There was a bug in TWRP V2.3.0.0 use fastboot to flash V2.3.1.0 and then reflash the rom
Sent from my BAKED Nexus
Click to expand...
Click to collapse
Got it working. Thanks all for your suggestions.
jmtend said:
Got it working. Thanks all for your suggestions.
Click to expand...
Click to collapse
How did you fix it? I have no OS and my internal SD card was erased too I don't know how to flash from fastboot
Adb push a ROM.
-Brought to you by Marino's Nexus 7-
AshleyPem28 said:
How did you fix it? I have no OS and my internal SD card was erased too I don't know how to flash from fastboot
Click to expand...
Click to collapse
I know many people hate the talk about toolkits but I was in the same situation and I used Wug's toolkit and it saved me. I downloaded 4.1.2 image directly from Google, as the toolkit only has 4.1.1.
I tried to return to stock on my own and it just went from bad to worse. I would of spent more time trying to fix it on my own but I was on a very tight time constraint. It will unroot your device but it is easy to root again.
Sent from my Nexus 7 using xda app-developers app
Billchen0014 said:
Sometimes a rom takes a long time to boot for the first time, please be very patient. Also, try wiping everything from /system, and then re install a custom rom from your /sdcard partition. also make sure your roms are for the nexus 7 not galaxy nexus or other similar devices. ONE MORE THING 4.1.2 wont flash with 4.1.1 bootloader.
Click to expand...
Click to collapse
THANK YOU the "ONE MORE THING" is all I needed to know for the same problem!
Hey folks. I'm trying to flash Cyanogenmod to my Nexus 7 running 4.2.1. I am rooted and unlocked. I downloaded the nightly 10.1 as well as the stable 10.0 along with Gapps. Flashing both with Clockworkmod recovery gets me stuck in a bootloop with both options, forcing me to restore to my backup.
This is my first time flashing a rom on this device, but I didn't wipe it or anything. Just flashed from my current setup. I'm wondering if I should restore to factory on my current first? Am I missing any steps in this process? I'd like to be able to just tap and install if possible. I had bad experiences with flashing when I had my Galaxy Captivate.
I appreciate any help with this. I have gone through several forums and threads, but none seem to be device or situation specific so I thought I would bring up this specific situation. Thanks for any help.
JavaMac said:
This is my first time flashing a rom on this device, but I didn't wipe it or anything. Just flashed from my current setup..
Click to expand...
Click to collapse
You left out the "how you flashed" part. If you were using something such as ROM Manager, it may have wiped for you. But typically, for manual flashing from the recovery you need to do a "factory reset" procedure prior to installing a new rom. (A wipe which erases everything in /data except what is /data/media)
I've used a CM10.1 nightly and sequentially flashing the gapps, no troubles. Perhaps different versions though, the devil is always in the details.
I flashed using Clockwork Recovery, both manually and from the app itself. Neither provided a solution.
JavaMac said:
I flashed using Clockwork Recovery, both manually and from the app itself. Neither provided a solution.
Click to expand...
Click to collapse
I'd also like to point out that I'm confused about why a factory reset would help this situation. If the new install is just writing over the boot, why should it matter?
JavaMac said:
I'd also like to point out that I'm confused about why a factory reset would help this situation. If the new install is just writing over the boot, why should it matter?
Click to expand...
Click to collapse
It doesn't just write over the boot.
/data is where all your downloaded apps, settings, and databases are...
Do a factory reset in cwm and cm will boot. It's that simple
Sent from my Nexus 7 using Tapatalk HD
Pirateghost said:
It doesn't just write over the boot.
/data is where all your downloaded apps, settings, and databases are...
Do a factory reset in cwm and cm will boot. It's that simple
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Success! TY.
I was trying to install CM10.1 for the 10th time and again it didn't work- I was stuck at the CM10.1 boot animation (I tried wiping my whole device, the cache everything). Then I decided to wipe the ROM (using TWRP) and my phone will no longer bootup at all- it is stuck at the "Google" logo. Help
All my Nandroid backups are gone... wtf do I do- is my phone broken for good?!?!?!?! :"O
Fastboot. Flash stock images. There are tutorials if you Google.
Sent from my Nexus 4 using Tapatalk 2
so, instead of wiping data(factory reset), you actually wiped the whole phone clean. you need to install adb on your computer, boot into your recovery, connect to your computer via usb, use the adb option to move your rom/gapps to your phone, then flash them via your recovery. you lost your data btw, youre gonna start fresh. next time, be careful.
If you can get to the bootloader you can flash factory images. Just out of curiosity, if it wasn't working why did you keep trying 10 times?
Sent from my Nexus 4 using xda app-developers app
simms22 said:
so, instead of wiping data(factory reset), you actually wiped the whole phone clean. you need to install adb on your computer, boot into your recovery, connect to your computer via usb, use the adb option to move your rom/gapps to your phone, then flash them via your recovery. you lost your data btw, youre gonna start fresh. next time, be careful.
Click to expand...
Click to collapse
Use toolkit to flash factory image lol
Underground_XI said:
Use toolkit to flash factory image lol
Click to expand...
Click to collapse
you know, ive got a bit of irony for you. a bit back, i had to flash the factory image at like 3am. i was a bit intoxicated and feeling lazy, so i decided to use a toolkit. i spent about an hour on it, kept getting errors and other issues with the toolkit itself. it never flashed anything. before i fell asleep, i took the 10 minutes to flash the factory image via fastboot
at4r1 said:
If you can get to the bootloader you can flash factory images. Just out of curiosity, if it wasn't working why did you keep trying 10 times?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Because I really wanted to try CM10.1 and I was trying different ways. I cleared the cache and tried, then cleared the Devk(something) cache and tried, and factory reset my phone too, it all didn't work- so I tried this and f'ed-up my phone
Underground_XI said:
Use toolkit to flash factory image lol
Click to expand...
Click to collapse
Since I was trying to flash CM10.1 can I just flash it with the Gapps from the get-go when my phone has no OS on it? Or does it need to have jelly bean ?
michaelsp9 said:
Since I was trying to flash CM10.1 can I just flash it with the Gapps from the get-go when my phone has no OS on it? Or does it need to have jelly bean ?
Click to expand...
Click to collapse
Like others said earlier I would flash the stock images with fastboot.
Tutorial is here: http://forum.xda-developers.com/showthread.php?t=2010312
It's a good thing I made a titaniumbackup and sent it to my drive before all this- at least I won't lose all my apps
I went from Paranoid Android 4.2.2 to the first Cyanogenmod 10.2 nightly and my phone worked great on the first boot, after rebooting it gets stuck on the google screen. I have tried going into recovery and wiping it etc. re-flashing stuff and can't, I have tried using the root toolkit to revert to stock 4.3 and unroot and 4.2.2 and unroot and neither has fixed it. I've even tried manually reverting to the stock bootloader etc and nothing. Theres no option for mounting storage to the pc with TWRP so I can't try redownloading the CM10.2 zip file either.
The point is I really need help as I think my problem is a rare case I can't find on the forums already.
Have you tried MANUALLY restoring Google's factory images? (With the fastboot command.)
Sent from my Nexus 4 with Tapatalk 4
SiMBol10 said:
I went from Paranoid Android 4.2.2 to the first Cyanogenmod 10.2 nightly and my phone worked great on the first boot, after rebooting it gets stuck on the google screen. I have tried going into recovery and wiping it etc. re-flashing stuff and can't, I have tried using the root toolkit to revert to stock 4.3 and unroot and 4.2.2 and unroot and neither has fixed it. I've even tried manually reverting to the stock bootloader etc and nothing. Theres no option for mounting storage to the pc with TWRP so I can't try redownloading the CM10.2 zip file either.
The point is I really need help as I think my problem is a rare case I can't find on the forums already.
Click to expand...
Click to collapse
Use efrant's guide to go back to 100% stock and start again
EddyOS said:
Use efrant's guide to go back to 100% stock and start again
Click to expand...
Click to collapse
AlbertoWayfarer said:
Have you tried MANUALLY restoring Google's factory images? (With the fastboot command.)
Sent from my Nexus 4 with Tapatalk 4
Click to expand...
Click to collapse
Thank you both so much it works again!
Good
Sent from my Nexus 4 with Tapatalk 4
This isn't my very first time with flashing/rooting/etc. but I'm not that adept with it.
Got my S4 2 days ago but managed to get time today to work on it. I rooted successfully and everything was running perfect. I flashed over the newest Beanstalk ROM w/ gapps and it ran fine the first time it ran.
I can't get passed the Samsung Galaxy S4 boot logo every time I try to reboot the phone though...
If I wipe the cache/dalvik and reflash it still doesn't boot passed logo.
If I wipe the cache/dalvik and then wipe data (including the internal SD card, completely wiping it clean), flashing the ROM will work the first time it runs; once I reboot or just power it off then power it back on, stuck at Galaxy S4 logo... I let the ROM run first time through, input only what is needed to get to the home screen (google account/wifi setup/phone name/etc.), then I've tried rebooting it, shutting it down and powering it back up, letting everything update and waiting half an hour and restarting it... all have the same result, stuck at boot logo
I'm using TWRP, I have a recovery for stock but I don't want to use stock.
If anyone can help me out I'd appreciate it.
Try flashing a different compatible kernel.
ObrienDave said:
Try flashing a different compatible kernel.
Click to expand...
Click to collapse
This is EXACTLY what I was about to try... I'm literally reflashing the ROM fresh right now, going to put the kernel on the SD card, then reboot into recovery and wiping cache then flashing the kernel.
Will using a recovery that was made on a different kernel have any effect if I decide to use the recovery? I've heard bad things about flashing the wrong kernel (even though I know the one I'm about to use is the correct one) and really screwing stuff up if not done properly. I just want to make sure I don't screw anything up permanently.
Thanks.
Spazzzin said:
This is EXACTLY what I was about to try... I'm literally reflashing the ROM fresh right now, going to put the kernel on the SD card, then reboot into recovery and wiping cache then flashing the kernel.
Will using a recovery that was made on a different kernel have any effect if I decide to use the recovery? I've heard bad things about flashing the wrong kernel (even though I know the one I'm about to use is the correct one) and really screwing stuff up if not done properly. I just want to make sure I don't screw anything up permanently.
Thanks.
Click to expand...
Click to collapse
Use twrp 2.5.0.2 because if your using 2.6 its bringing problems. Also report this to their thread for better help
Sent from my SPH-L720 using xda app-developers app
Since there are no recovery categories according to this page,
http://forum.xda-developers.com/showthread.php?t=2303917
I don't see where it would matter. No guarantees though.
I do know it is ESSENTIAL to match the type (TW or AOSP) ROM and kernel to avoid major problems.
I also recommend TWRP 2.5.0.2
D/L TWRP from here:
http://techerrata.com/browse/twrp2/jfltespr
ObrienDave said:
Since there are no recovery categories according to this page,
http://forum.xda-developers.com/showthread.php?t=2303917
I don't see where it would matter. No guarantees though.
I do know it is ESSENTIAL to match the type (TW or AOSP) ROM and kernel to avoid major problems.
I also recommend TWRP 2.5.0.2
D/L TWRP from here:
http://techerrata.com/browse/twrp2/jfltespr
Click to expand...
Click to collapse
How do you go about installing TWRP? I used Goomanager and installed it from there when I was following the rooting guide
Spazzzin said:
How do you go about installing TWRP? I used Goomanager and installed it from there when I was following the rooting guide
Click to expand...
Click to collapse
Flashing a different kernel didn't do anything, I still keep getting stuck at the boot logo :/
Spazzzin said:
How do you go about installing TWRP? I used Goomanager and installed it from there when I was following the rooting guide
Click to expand...
Click to collapse
Just flash it by odin by the link provided above. Make sure to use the tar file v 2.5.0.2
Sent from my SPH-L720 using xda app-developers app
---------- Post added at 09:22 PM ---------- Previous post was at 09:19 PM ----------
Spazzzin said:
Flashing a different kernel didn't do anything, I still keep getting stuck at the boot logo :/
Click to expand...
Click to collapse
By the way can you provide the steps and which files you flashing. Also redownload everything could be a bad download. Make sure to download them in computer and transfer them to your sd card
Sent from my SPH-L720 using xda app-developers app
I did a fresh install of the LiquidSmooth ROM and it's not hanging at boot logo whenever I reboot, and everything is working well. I suppose I'll stick with this for a while.
For my steps trying Beanstalk:
Boot into recovery (TWRP 2.6.0.0)
Factory reset;wipe cache/dalvik
Format Data
Factory reset;wipe cache/dalvik
Install ROM + Gapps
Wipe cache/dalvik
Reboot
I then tried doing that exact process, after letting it boot once I rebooted into recovery and flashed KT Kernel and wiped then rebooted and it hung at boot logo.
I did it again but I installed ROM + Gapps + Kernel then wiped then rebooted and it still hung at boot logo.
I'll download and prepare a new install of Beanstalk and give it another try tomorrow. I'll make sure to backup Liquid in case I want to switch back.
Thanks again for the help!
Glad it's working out for you.
If I may ask here; how do I know if a certain kernel is compatible with a ROM? I know to match the version (4.2, 4.3. etc,) and base (AOSP/ TW) but is there anything else specific that I need to watch out for that could cause problems with flashing a kernel on a ROM?
Spazzzin said:
If I may ask here; how do I know if a certain kernel is compatible with a ROM? I know to match the version (4.2, 4.3. etc,) and base (AOSP/ TW) but is there anything else specific that I need to watch out for that could cause problems with flashing a kernel on a ROM?
Click to expand...
Click to collapse
Not really unless the rom dev for some reason doesn't recommend using a certain one. Kernels will act differently for everyone even on the same device with the same rom. Just need to flash them and find out which one works the best for you (battery life, overheating, smoothness, etc).
Always have a backup handy just in case something doesn't work right.