I've tried to flash the two different ROMs out for JB and for some reason it is not getting past the Nexus Logo Boot screen. I can flash any ICS ROM but JB never gets past the boot screen. I've been flashing ROMs since the OG Droid and have never experienced this before.
Steps already taken:
1) Full wipe
2) Format of system and data
3) executed Super Wipe Script
4) Battery Pulls
5) Backed out of CWM and unmounted system and data
6) Flashed Various AOKP and AOSP ROMs and tried to JB ROM from those ICS ROMs
7) Performed a factory restore of the phone using WugFresh's ToolKit (un-rooted and locked phone) and then Rooted, unlocked, and flashed CWM again
8) Flashed Team Win Recovery and re-flashed JB ROMs
I have tried everything I can think of and yet nothing has worked. Has anyone Else experienced this or does anyone have any suggestions on what I can possibly do to get past the Nexus Boot screen? Thanks in advance.
how long are you waiting after the install?
Zepius said:
how long are you waiting after the install?
Click to expand...
Click to collapse
Average wait time is 20 minutes but I've waited up to 4 hours.
which rom are you flashing?
try this one: http://www.teambamf.net/topic/4064-romtoro-jellybamf-13/
it works for me perfectly (thanks adrynalyne)
Zepius said:
which rom are you flashing?
it works for me perfectly (thanks adrynalyne)
Click to expand...
Click to collapse
I've tried Liquid Vicious Versions 1-3 and BAMF Versions 1.0 and 1.2. Thanks for the updated BAMF...I'll try that one now.
I am having the same problem as you, I flashed multiple JB roms and it is stuck at the X screen. I can flash ics roms easily tho.
I had the freeze at logo issue a few times while I was trying to get my JB up and running.
1. I got superwipe from http://forum.xda-developers.com/showthread.php?p=20473980
2. I dl JellyBelly and GApps from http://rootzwiki.com/topic/28677-rom-jelly-belly-v17-07012012-jellybean-41-its-all-about-speed/
3. Cleared cache/factory reset
4. Flashed and used superwipe
5. Flashed JellyBelly then GApps
I had to wait about 5 minutes while it booted. Hope this helps, yall.
I'll definitely try those steps...Thanks!
Sent from my HTC One X using Tapatalk 2
keno23 said:
I'll definitely try those steps...Thanks!
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Glad to pass along the help I got earlier :highfive:
consultant.ben said:
I had the freeze at logo issue a few times while I was trying to get my JB up and running.
1. I got superwipe from http://forum.xda-developers.com/showthread.php?p=20473980
2. I dl JellyBelly and GApps from http://rootzwiki.com/topic/28677-rom-jelly-belly-v17-07012012-jellybean-41-its-all-about-speed/
3. Cleared cache/factory reset
4. Flashed and used superwipe
5. Flashed JellyBelly then GApps
I had to wait about 5 minutes while it booted. Hope this helps, yall.
Click to expand...
Click to collapse
Unfortunately it did not work...same Nexus Bootscreen forever. Thanks though.
i have the same the problem with my phone , i flash the jb rom it works fine the first time booting i setup my account download my apps every thing works fine BUT when i re-start the phone the phone got stock on the google logo and don't re-start again, so guess what i have to try another rom so i try a regular ICS rom guess what on the first boot the phone got stock on the boot logo so i try another ICS rom and the same thing happing stock again on the boot logo, so i have to do flash the google factory rom to my phone got back to work
Same her.. infinite boot loop.. I'm tired of unbricking back to stock
Flash all kinds of from and kernel combo and still got boot loop.. I hope someone can help us with this..
Try mROM http://forum.xda-developers.com/showthread.php?t=1763823
Make sure wipe/factory reset and also wipe caches while you're at it. Also make sure that CWM is updated.
keno23 said:
Unfortunately it did not work...same Nexus Bootscreen forever. Thanks though.
Click to expand...
Click to collapse
Same here, I've tried just about every rom out there now and have cleaned the phone out several times. Wonder if there is anyone who had a boot longer than 20 minutes and finally was able to get it to boot, wonder what they did to get it to boot. I've waited hours with some of these roms and still no luck.
nothingshocking said:
Same here, I've tried just about every rom out there now and have cleaned the phone out several times. Wonder if there is anyone who had a boot longer than 20 minutes and finally was able to get it to boot, wonder what they did to get it to boot. I've waited hours with some of these roms and still no luck.
Click to expand...
Click to collapse
Are you wiping dalvik and system cache along with doing data wipe?
mb9023 said:
Are you wiping dalvik and system cache along with doing data wipe?
Click to expand...
Click to collapse
wipe data/factory reset -> wipe cache partition -> wipe dalvik -> format /system -> format /data -> format/cache. I've tried super wipe. All Roms never get passed the boot animation. I get past the "Google" unlock symbol, but it just sits at the boot animation. It doesn't reboot or anything, just sits there for hours or when I get bored looking at it after about 30 minutes or so.
@nothingshocking
We have the same problem.. I been flashing all kinds of jb rom since last week..I'm not new in flashing rom and kernel so I know what doing.. it so weird that it only stay in Google logo (x) when I flash jb rom..but if I flash ics it will boot up.. hayzzz I hope someone can help us with this issue.. calling all great dev. I hope u can help us..
Sent from my Galaxy Nexus using XDA Premium App
landrian18 said:
@nothingshocking
We have the same problem.. I been flashing all kinds of jb rom since last week..I'm not new in flashing rom and kernel so I know what doing.. it so weird that it only stay in Google logo (x) when I flash jb rom..but if I flash ics it will boot up.. hayzzz I hope someone can help us with this issue.. calling all great dev. I hope u can help us..
Sent from my Galaxy Nexus using XDA Premium App
Click to expand...
Click to collapse
Not going to happen man...I've tried EVERYTHING and have gotten feedback from various devs to no avail. All I get is Nexus boot logo FOREVER.
Solution is to flash it back to stock (plus unroot and re-lock) and then take it in to a store and get another one shipped to you since it's still under the annual warranty. As for the issue for bringing it in, just say it boot loops at random times (that's not technically a lie).
Sent from my Galaxy Nexus using Tapatalk 2
Have you tried flashing the JB Boot loader and then flashing the JB ROM??
It is from jakeday and his Jelly Belly ROM
adclem said:
Have you tried flashing the JB Boot loader and then flashing the JB ROM??
It is from jakeday and his Jelly Belly ROM
Click to expand...
Click to collapse
That doesn't work either. Thanks though.
Sent from my HTC One X using Tapatalk 2
Related
After installing Cyanogenmod 9 on the One X I started to notice extremely poor signal, Mobile and Wi-Fi. Also the phone would crash and randomly reboot when doing simple tasks such as opening messages etc.
Upon trying to get into recovery to install a different rom, the phone now flashes on a black screen and restarts the phone.
To try and solve this issue, I unrooted the phone and restored to stock recovery.
I then re-rooted the phone and installed clockworkmod recovery again.
I can now access clockworkmod recovery although it seems to have no effect. Installations of any rom fail and cyanogenmod always pops straight back up again after rebooting.
Has anyone else had this issue?
Does anyone have a way to fix this? Possibly to force the phone completely back to stock?
You can try first "SuperWipe" (from ARHD's thread) and flash a new ROM (don't forget boot.img before...)
Kamiil29 said:
You can try first "SuperWipe" (from ARHD's thread) and flash a new ROM (don't forget boot.img before...)
Click to expand...
Click to collapse
Thanks for your quick reply, how do I do the super wipe? and where can I download the One X stock roms from?
AndyB said:
Thanks for your quick reply, how do I do the super wipe? and where can I download the One X stock roms from?
Click to expand...
Click to collapse
Unfortunately I can't help you with SuperWipe, but you can find the HOX stock ROMs here.
Sent from my HTC One X using Tapatalk 2
Ran superwipe and tried to install the stock rom. Superwipe ran fine and did the job, although the rom installation still failed as it was doing before and I am now stuck with a htc bootloop. The device won't boot into recovery either. Any ideas anyone?
AndyB said:
Ran superwipe and tried to install the stock rom. Superwipe ran fine and did the job, although the rom installation still failed as it was doing before and I am now stuck with a htc bootloop. The device won't boot into recovery either. Any ideas anyone?
Click to expand...
Click to collapse
Did you try holding down the Power and Volume Down buttons while in the bootloop to enter the bootloader? Hold them down until the lights start to flash, the screen goes off and then the bootloader comes up.
If you can get into recovery with that, factory reset, clear cache and dalvik cache (under advanced) then try install the ROM.
I'm not the best person to be helping, but I hope that works for you!
I had a similar problem once where the phone would just sit on the HTC One X screen, and trying to go into recovery just put the phone back to the HTC screen. I fixed it by flashing the boot.img, factory reseting, clearing out caches and installing the ROM again. No problems since.
I'm afraid if this doesn't work, I may have to abandon you and let someone else take over, as I'm no expert, but I'll see what I can do to help.
Edit: sorry, it is 2AM here and I need some rest for an early start at 6AM. I will check up on this thread when I wake.
Sent from my HTC One X using Tapatalk 2
FIXED!!!
To anyone else having this problem, I downloaded ARHD Flashboot 7.0.0 and ARHD 7.0.0, followed the instructions on what to do and installed ARHD successfully.
This has now completely gotten rid of Cyanogenmod and seems to have got clockworkmod working again.
It's probably work using the "Fix Permissions" option in ROM manager before you attempt this as I believe that is what got clockworkmod working and able to install files again. (I may be wrong)
Thankyou for everyone's assistance.
AndyB said:
To anyone else having this problem, I downloaded ARHD Flashboot 7.0.0 and ARHD 7.0.0, followed the instructions on what to do and installed ARHD successfully.
This has now completely gotten rid of Cyanogenmod and seems to have got clockworkmod working again.
It's probably work using the "Fix Permissions" option in ROM manager before you attempt this as I believe that is what got clockworkmod working and able to install files again. (I may be wrong)
Thankyou for everyone's assistance.
Click to expand...
Click to collapse
Glad you got if working
Sent from my HTC One X using Tapatalk 2
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.
After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Did you wipe data and cache when you flashed the new rom?
nyyankees1237 said:
After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Click to expand...
Click to collapse
a few questions:
and i can verify the issue is something on your end, because the ROM you tried was mine, and nobody has had that issue (not booting it)
do this...
1. make sure you have the latest version of clockwordmod, don't use twrp
2. re-download my ROM (just for sake of not adding any other variables to your issue, because mine should boot)
3. put ROM on external SD card
before continuing... take a quick look at my thread here in QA titled "flashing ROMs correctly every time" .... so you can get some instruction on verifying MD5 of the download... don't worry, the thread will explain that you...
now proceed
4. boot to recovery
5. do a factory reset - 3 times do this, just to be thorough. people will say you don't need to, but like i said, just for the sake of removing variables
6. go to mounts and storage, format system 3 times - (yes, through recovery as well)
7. flash ROM, and reboot
EDIT*** i will say this, ALWAYS format system when flashing a new ROM
cobraboy85 said:
a few questions:
and i can verify the issue is something on your end, because the ROM you tried was mine, and nobody has had that issue (not booting it)
do this...
1. make sure you have the latest version of clockwordmod, don't use twrp
2. re-download my ROM (just for sake of not adding any other variables to your issue, because mine should boot)
3. put ROM on external SD card
before continuing... take a quick look at my thread here in QA titled "flashing ROMs correctly every time" .... so you can get some instruction on verifying MD5 of the download... don't worry, the thread will explain that you...
now proceed
4. boot to recovery
5. do a factory reset - 3 times do this, just to be thorough. people will say you don't need to, but like i said, just for the sake of removing variables
6. go to mounts and storage, format system 3 times - (yes, through recovery as well)
7. flash ROM, and reboot
EDIT*** i will say this, ALWAYS format system when flashing a new ROM
Click to expand...
Click to collapse
thanks for the info, will try this all out soon. I've been flashing roms for years now and have never run into anything like this, and as previously stated, this didn't occur solely with your rom which has me thinking something has happened to the phone itself. will get back to you soon and once again thank you
chucktdriscoll said:
Did you wipe data and cache when you flashed the new rom?
Click to expand...
Click to collapse
of course, wiped data, cache, & delvik
nyyankees1237 said:
of course, wiped data, cache, & delvik
Click to expand...
Click to collapse
my point is...
coming from a cm based ROM, or aokp, whatever you said... you would want to format system as well.
nyyankees1237 said:
After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Click to expand...
Click to collapse
I was having some of the same issues. I downloaded XquiziT's Superwipe and ran it by installing from external sd card. I ran it three times to clear everything out, then I wiped data, cache and the rest three times.
No probs for me after that.
Will definitely give that a try as well! Thank you! Will post my results when the holiday is over.
Happy thanksgiving
Sent from my SGH-T999 using xda app-developers app
Few hours before this post I flashed a rooted version of android 4.3 from the thread by "Carlos_Manuel". However, following that the supersu was not working I flashed the supersu binaries over the ROM from TWRP. Since then, it is stuck in boot loop at the Google Logo. Tried flashing PA, Sourcery, CM but nothing seems to work. What should I do?
Flash the official Google image: http://forum.xda-developers.com/showthread.php?t=2376687
check dreams rom thread and see my post there
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Fix it by flashing factory images! do a full wipe, you can get imprtant stuff from your Nexus by using adb pull commands!
Users was blaming me when they screwed their Nexus with the root files!
I can successfully even flash old root files and no bootloops but ofc. root wont work if using those old root files.
OP, did you factory reset between ROM flashes?
beekay201 said:
OP, did you factory reset between ROM flashes?
Click to expand...
Click to collapse
pulling files then flashing 4.2.2 stock image to start fresh
NyPlaya513 said:
Ok, I am paranoid and want to be sure about this. I am in the same boat as the OP. I have a 32gb toro on twrp 2.5. I am under the impression that flashing the stock images will flash my sdcard partition and I want to pull some files if that is the case. Is there anyway to pull the files or am I stuck and need to start fresh.
Click to expand...
Click to collapse
You cant use the stock images they are for gsm not toro/cdma, have to use a custom zip only one is that light speed one in development right now I am waiting for muzzys but, full wipe, flash rom, gapps, supersu.
NeoMagus said:
You cant use the stock images they are for gsm not toro/cdma, have to use a custom zip only one is that light speed one in development right now I am waiting for muzzys but, full wipe, flash rom, gapps, supersu.
Click to expand...
Click to collapse
nvm pulling files
If you tried wiping just cache/dalvik after the flash I dont know there may be another way to get it to boot or not but yeah the factory image will start it over fresh and get you out of it
NeoMagus said:
If you tried wiping just cache/dalvik after the flash I dont know there may be another way to get it to boot or not but yeah the factory image will start it over fresh and get you out of it
Click to expand...
Click to collapse
nvm got the toolkit to pull files via adb for me on my parallels
agent47er said:
Few hours before this post I flashed a rooted version of android 4.3 from the thread by "Carlos_Manuel". However, following that the supersu was not working I flashed the supersu binaries over the ROM from TWRP. Since then, it is stuck in boot loop at the Google Logo. Tried flashing PA, Sourcery, CM but nothing seems to work. What should I do?
Click to expand...
Click to collapse
"just wipe data" in recovery after flashing, solve bootloop issue
dexviajiboy said:
"just wipe data" in recovery after flashing, solve bootloop issue
Click to expand...
Click to collapse
thanks for your help.. but I ended up flashing factory image of 4.3 which fixed the problem. Also I wnted to ask if you know of any 4.3 kernels that have implemented high performance audio mod. So far I have tried Faux and Hybrid but both dont have it.
agent47er said:
thanks for your help.. but I ended up flashing factory image of 4.3 which fixed the problem. Also I wnted to ask if you know of any 4.3 kernels that have implemented high performance audio mod. So far I have tried Faux and Hybrid but both dont have it.
Click to expand...
Click to collapse
i dont think there's any kernel for now, give it some time and you'll get one
Hi!
So, first off, I'm completely new to all of this. I've had my Nexus for about a year now, and after much reading, thinking and research I decided to root it and flash Paranoid Android. I did a terrible job, clearly.
I used Nexus root toolkit 1.7.2 and was running Jellybean 4.3.
First problem was that my root wouldn't go into custom recovery mode, all I got was an open droid on its side with a red exclamation point. That was scary.
I unrooted using toolkit and rerooted. The custom recovery worked this time, so from there I flashed Paranoid Android 3.99
It started to reboot in PA, and it's still going.
I can't get into recovery mode. I can't get the battery out.
Every time I try to get into recovery mode it starts to reboot. Right now, I have a glowing brick of glass and metal
So, yeah. Anyone got a solution?
Thanks.
megsto said:
Hi!
So, first off, I'm completely new to all of this. I've had my Nexus for about a year now, and after much reading, thinking and research I decided to root it and flash Paranoid Android. I did a terrible job, clearly.
I used Nexus root toolkit 1.7.2 and was running Jellybean 4.3.
First problem was that my root wouldn't go into custom recovery mode, all I got was an open droid on its side with a red exclamation point. That was scary.
I unrooted using toolkit and rerooted. The custom recovery worked this time, so from there I flashed Paranoid Android 3.99
It started to reboot in PA, and it's still going.
I can't get into recovery mode. I can't get the battery out.
Every time I try to get into recovery mode it starts to reboot. Right now, I have a glowing brick of glass and metal
So, yeah. Anyone got a solution?
Thanks.
Click to expand...
Click to collapse
UPDATE:
I successfully flashed the stock rom.:laugh: I used nexus toolkit, just had to use the advanced settings that sounded scary at first.
Could someone provide or link to a step by step indepth guide to flashing PA. Starting from before root. I don't trust myself again.
Boot into your custom recovery
Factory Reset
Flash ROM
Flash Gapps
Wipe cache & dalvik cache
Reboot
Anu6is said:
Boot into your custom recovery
Factory Reset
Flash ROM
Flash Gapps
Wipe cache & dalvik cache
Reboot
Click to expand...
Click to collapse
Thanks!
Further question, I don't know if you know anything about this, but since I reset to stock ROM, my back softkey and volume keys don't work.
Any ideas? Should I start a new thread concerning this issue?
megsto said:
Thanks!
Further question, I don't know if you know anything about this, but since I reset to stock ROM, my back softkey and volume keys don't work.
Any ideas? Should I start a new thread concerning this issue?
Click to expand...
Click to collapse
No, sorry... can't help you there.
Did a quick google search and found reports of volume keys not functioning for some people after a 4.3 update but nothing in regards to the back button.
As it's not a problem I'm familiar with, the most I could suggest is a reboot. If you do plan on flashing a custom ROM though, hopefully that resolves it.
Issue seemed to have fixed itself. Odd.
Thanks for your help!
Good to know
Anu6is said:
Boot into your custom recovery
Factory Reset
Flash ROM
Flash Gapps
Wipe cache & dalvik cache
Reboot
Click to expand...
Click to collapse
Can I flash the new paranoid android beta using toolkit whit the zip on my computer whitout custom recovery?
Gadgervais said:
We can use stock recovery to install it? We don't need clockworkmod recovery? If I want to try the new beta cause I already have kit Kat and stay wit it I can do the same steps?
Click to expand...
Click to collapse
Stock recovery cannot flash custom ROMs