Develop Bugs

[Q] Stuck In a Broken ROM and cant get back into CWM recovery mode(Error Message)

Hi,
i found a simliar thread that was talking about a similar subject, but didn't answer my question. i have lost it and cant find that same thread for help.
rooted -flashed bad rom - everything keeps closing(apps, Google sync)--- cant get int to recovery mode because of error
****I unlocked bootloader and rooted my GalaxyNex. then installed ROM maneger. i flashed CWM,then backed up my ROM. i tested it by flashing my backed up ROM, after i had messed around and my phone went back to normal. i was feeling safe. i noticed that i was having trouble getting into the recovery mode because of the belly open with exclamation Point. i read that it is because CWM was losing permission? i found that i just had to re-flash CWM every time right before i go into recover mode. i flashed a ROM from ROM maneger and everything worked until i turned the phone on. i cant sync Google account, and basically all apps close immediately (no key board too). I cant get into recovery mode and i cant down load ROM maneger to try to re-flash CMW to restore from older ROM.
I am sorry if this is already been answered i have try to find my situation but i couldn't.

I tried to re-flash the clock work recover image through the terminal of my mac but it says permission denied... i guessing i need to find a way to re flash to stock from fastboot is this possible ?

Pull the battery and hold power + volume and get into fast boot. Flash stock images from here
Sent from my Galaxy Nexus using xda premium

joshnichols189 said:
Pull the battery and hold power + volume and get into fast boot. Flash stock images from here
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Thanks I got really lucky i was able to re flash Clock work recovery in fast boot with the command
./fastboot flash recovery recovery-clockwork-5.5.0.4-toro.img
then i was able to get into the proper recovery mode and re flash my backed up image.
if i wanted to re flash a original image would the terminal command look like this
./fastboot flash recovery "Imagename" ? i might have just got lucky but i am guessing thats how you re-flash something to your phone?
now that i have gotten back to the beginning, why is it that i have to re flash CMW every time to get in correct recovery mode? or how do i stop it from giving me the recovery error when trying to get to the correct recovery mode?
thanks again

Glad your good! Hate to see these threads but we all go through it sooner or later
Sent from my Galaxy Nexus using xda premium

billycurtis said:
now that i have gotten back to the beginning, why is it that i have to re flash CMW every time to get in correct recovery mode? or how do i stop it from giving me the recovery error when trying to get to the correct recovery mode?
thanks again
Click to expand...
Click to collapse
After you fastboot flash the CWM image, use ADB, a terminal, or a file explore to remove or rename the file /system/recovery-from-boot.p

Huge mistake

Was trying to do a clean flash, I did not put ROM on phone , did the format and all the other steps to flash clean then realized, now I cannot get past the google screen on phone? help asap!

Try booting back into recovery and wiping data and cache and reinstalling your ROM, if best try doing a restore from a backup.
Sent from my Paranoid Galaxy Nexus!

HOW?
moises93 said:
Try booting back into recovery and wiping data and cache and reinstalling your ROM, if best try doing a restore from a backup.
Sent from my Paranoid Galaxy Nexus!
Click to expand...
Click to collapse
how do I get back in? I do volume down and power and get stuck on screen with android and start button and cant do anything ?

okay
andysom25 said:
how do I get back in? I do volume down and power and get stuck on screen with android and start button and cant do anything ?
Click to expand...
Click to collapse
okay I'm back in clockwork but my recovery wont show up so I have nothing to restore to , what do I do ?

GOT IT
andysom25 said:
okay i'm back in clockwork but my recovery wont show up so i have nothing to restore to , what do i do ?
Click to expand...
Click to collapse
everything should be fine now thank you !

This happened once to me. What saved me was the Nexus Root Toolkit by Wugfresh.
I just allowed it to flash the image that I already had downloaded (but forgot to put in phone). Give that a shot if nothing else is working for you. Luckily I had fastboot drivers already installed.

[Q] Galaxy Nexus bricked after Android 4.3 upgrade

Hi guys!
As soon as Google released the factory images for our GNex I downloaded the yakju one and flashed it. All was running fine.
Then I tried to root with Galaxy Nexus Toolkit option for yakju 4.2.2
SuperSU was installed but said no su binary available.
After searching for a while I saw the Chainfire's root method was doing the job for the Galaxy Nexus with 4.3, and applied it to my Nexus.
I can't remember exactly but I think the first restart was fine but I'm not sure.
Now my Nexus is stuck in a boot loop and it can't pass the boot animation. The phone start and show the Google logo, then most of the times I can see the boot animation but suddenly it restarts and the process start again.
Things I've tried before posting:
- Full wipes
- Installing CM10.1 and Gapps from CWM Recovery.
- Restore a backup from CWM Recovery
- Clean install of factory images (takju and yakju, 4.1, 4.22, 4.3)
- Restoring the factory image with ODIN as said in the HOWTO guide in this forum.
- Factory reset with factory images (tajku and yakju, 4.2.2, 4.3) with Galaxy Nexus Toolkit
- OMAP Flash trying to restore some flash memory issues?
By now, nothing works and I'm starting to think that there might be a hardware problem with my Nexus.
So, what you think? Can anybody help me?
Thanks in advance!

have you flashed the new bootloader #4?
Sent from my Galaxy Nexus using Tapatalk 4 Beta

lovejoy777 said:
have you flashed the new bootloader #4?
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yes, each Android stock version or custom ROM I've tried, was with it's bootloader.
I mean, bootloader #3 for 4.2.2 and #4 for 4.3

strange. i had issues here is what i did.
fastboot flashed #4 bootloader
then fastboot reboot-bootloader
factory reset in twrp
flashed 4.3 rom
flashed chainfires root-fix
reboot
hope this helps in some way. i will post a link of the rom i used incase your version is screwed.
cheers
steve
Sent from my Galaxy Nexus using Tapatalk 4 Beta
---------- Post added at 03:07 PM ---------- Previous post was at 03:06 PM ----------
http://forum.xda-developers.com/showthread.php?t=null
Sent from my Galaxy Nexus using Tapatalk 4 Beta

lovejoy777 said:
strange. i had issues here is what i did.
fastboot flashed #4 bootloader
then fastboot reboot-bootloader
factory reset in twrp
flashed 4.3 rom
flashed chainfires root-fix
reboot
hope this helps in some way. i will post a link of the rom i used incase your version is screwed.
cheers
steve
Sent from my Galaxy Nexus using Tapatalk 4 Beta
---------- Post added at 03:07 PM ---------- Previous post was at 03:06 PM ----------
http://forum.xda-developers.com/showthread.php?t=null
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thank you a lot, I read you in other posts from today and yesterday looking for a solution to my problem.
By now nothing solved it, but I'll keep on trying.
All your help is welcome, thanks!

Even after installing factory image takju jwr66v I'm stuck in the boot loop:
- Google logo -> boot animation -> restart.
- (sometimes) Google logo -> restart.
I've flashed it with flash-all.bat script and manually and nothing.
Any idea?

u tried odin flash? i
Sent from my Galaxy Nexus

paarthdesai said:
u tried odin flash? i
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Yes, I tried.
After 20 or more reboots, it showed the screen:
"Android is upgrading...
Optimizing app XX of XX"
And then, bootloop again.......
So extrange.

For me it's the same, after flashing 4.3. ALWAYS stuck at Google logo, I never even saw a bootanimation. And both TWRP and CWM can't restore a backup, when restoring data they suddenly show FAILED and they stop. Thank you Jellybean 4.3, just to try your laggy, choppy experience I'm now stuck at Google logo.

ledoweb said:
For me it's the same, after flashing 4.3. ALWAYS stuck at Google logo, I never even saw a bootanimation. And both TWRP and CWM can't restore a backup, when restoring data they suddenly show FAILED and they stop. Thank you Jellybean 4.3, just to try your laggy, choppy experience I'm now stuck at Google logo.
Click to expand...
Click to collapse
So sorry to read another case.
In mine I can see the bootanimation most of the times.
I really can't understand how the Nexus can't boot properly even after a full wipe or a factory reset using the official factory images (or after ODIN)
As I told before, I'm starting to think about hardware problems, caused or not by the 4.3 upgrade.

i just wanna make sure.
when you are flashing the factory images. are you also doing a data wipe/factory reset?
what happens if you relock then unlock? are you able to even issue the fastboot oem lock/unlock commands?
also. there has actually been times where i thought my phone was stuck forever in the bootloop. then i just let it sit(full battery) and checked it once in a while to make sure it wasnt getting too hot, and it has fixed itself. i would get worried as heck thinking that i was screwed because all the methods i tried just refused to work(including a nandroid restore with the data error mentioned above) and somehow it fixed itself and finally booted up. then once it was booted fully i went with factory img restores.

ashclepdia said:
i just wanna make sure.
when you are flashing the factory images. are you also doing a data wipe/factory reset?
what happens if you relock then unlock? are you able to even issue the fastboot oem lock/unlock commands?
also. there has actually been times where i thought my phone was stuck forever in the bootloop. then i just let it sit(full battery) and checked it once in a while to make sure it wasnt getting too hot, and it has fixed itself. i would get worried as heck thinking that i was screwed because all the methods i tried just refused to work(including a nandroid restore with the data error mentioned above) and somehow it fixed itself and finally booted up. then once it was booted fully i went with factory img restores.
Click to expand...
Click to collapse
Yes, I'm doing a wipe/factory reset before and after flashing stock factory images, and I've tried without doing any wipe and still nothing.
I can use all fastboot commands (lock, unlock included), flash custom recovery images, etc
Now, with CM10.1 without Gapps installed, sometimes the phone can complete a boot and show the lockscreen or even permit me navigate through the launcher but suddenly, it shows some airtfacts in the screen and restarts again.
Thanks!

||M^nnu|| said:
Yes, I'm doing a wipe/factory reset before and after flashing stock factory images, and I've tried without doing any wipe and still nothing.
I can use all fastboot commands (lock, unlock included), flash custom recovery images, etc
Now, with CM10.1 without Gapps installed, sometimes the phone can complete a boot and show the lockscreen or even permit me navigate through the launcher but suddenly, it shows some airtfacts in the screen and restarts again.
Thanks!
Click to expand...
Click to collapse
its sounding more and more like the time i accidentally left mine in a freezer(worked in a kitchen. set it down after using in an industrial freezer that goes -10F !! for over and hour. it just wouldnt boot. after warming up it was as if /data was corrupted. i couldnt do ANYTHING.)
i was pleasantly surprised when it just fixed itself after insane amount of tries of wipes, installs, restores.
good luck! i hope it gets back in working order.
(im also wondering if it might have something to do with the supersu install, as ive read that there has been issues with it and people not being able to get to the symlinked /data things such as the legacy symlink. have you checked to see if there is a "supersu removal" zip you can flash? just in case that helps? or maybe try to fastboot boot the 4.2.2 boot.img? wondering if installing cm10.1 and then fastboot boot the CM stock boot img just in case something isnt installing right with that)

Try fastboot erase commands instead of factory reset in recovery

Maybe this can sounds stupid but, did you check MD5 of the downloaded image? I don't know, just to discard some reasons

Sdobron said:
Try fastboot erase commands instead of factory reset in recovery
Click to expand...
Click to collapse
just DO NOT fastboot erase bootloader
lol
just had to say it.
this was gonna be the next thing i mentioned also
especially the fastboot erase data

ashclepdia said:
just DO NOT fastboot erase bootloader
lol
just had to say it.
this was gonna be the next thing i mentioned also
especially the fastboot erase data
Click to expand...
Click to collapse
Thanks haha..didn't think about anyone doing that but you never know lol.
MD5 check would be advised too.

just something to mention. when i tried to install 1st time then tried to return to 4.2 my twrp backups did not boot i tried alsorts and had to wait untill a good 4.3 rom was posted. my 1st 4.3 rom still gets stuck on bootloop. whos 4.3 have you tried?
Sent from my Galaxy Nexus using Tapatalk 4 Beta

OP what computer OS are you trying to do this from? I am wondering if something isnt flashing right due to a windows issue and as others like Sdobron mentioned check the MD5 of the tar.

lovejoy777 said:
just something to mention. when i tried to install 1st time then tried to return to 4.2 my twrp backups did not boot i tried alsorts and had to wait untill a good 4.3 rom was posted. my 1st 4.3 rom still gets stuck on bootloop. whos 4.3 have you tried?
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Click to expand...
Click to collapse
i am using the shiny ota rom from baldwinguy
you can find it at rootzwiki. i dont know if its posted over here
i havent had any issues at all.(i am also now running faux kernel, he tweeted the 4.3 update just now. running awesome right now)
here is the link
http://rootzwiki.com/topic/36706-ro...tock-android-43-jss15j-no-bugs/page__st__4810

[Q] Softbrick/bootloop

So, I decided to root my wifes Galaxy S2 due to it being a little older and to get more out of it for her, however I seem to have got my self stuck in a bootloop.
-Downloaded Odin, flashed CWM recovery and rooted phone all relatively easy and with no issues. However I wanted to get CM 10.1.2 stable cuase thats what i run on my Nexus 4. Before i flashed, i ran a Nandroid backup from cwm and did a wipe data/factory reset and rebooted. this is where i got the boot loop, on the T-mobile screen. Tried restoring from the back up, and still boot looped. tried flashing CM and it boot looped on the CM splash screen. On the CM forum it seems someone else had this issue and that kinda how i got pointed here. CM Admin suggested downloading an updated Bootloader. I honestly looked all over this site and couldnt find ANYTHING. I can still get into Download mode, and Recovery mode with no issues.
Thanks for your time
CWM v 5.0.2.6
Samsung T989 (JB 4.1.2)
Rooted

EgoTrip26 said:
So, I decided to root my wifes Galaxy S2 due to it being a little older and to get more out of it for her, however I seem to have got my self stuck in a bootloop.
-Downloaded Odin, flashed CWM recovery and rooted phone all relatively easy and with no issues. However I wanted to get CM 10.1.2 stable cuase thats what i run on my Nexus 4. Before i flashed, i ran a Nandroid backup from cwm and did a wipe data/factory reset and rebooted. this is where i got the boot loop, on the T-mobile screen. Tried restoring from the back up, and still boot looped. tried flashing CM and it boot looped on the CM splash screen. On the CM forum it seems someone else had this issue and that kinda how i got pointed here. CM Admin suggested downloading an updated Bootloader. I honestly looked all over this site and couldnt find ANYTHING. I can still get into Download mode, and Recovery mode with no issues.
Thanks for your time
CWM v 5.0.2.6
Samsung T989 (JB 4.1.2)
Rooted
Click to expand...
Click to collapse
U need to flash the newest twrp recovery, a lot of ppl have been having issues with cwm lately so my advice would be to DL the twrp tar file and use that to root and not cwm
Sent from my SAMSUNG-SGH-T989 using xda premium

soupysoup said:
U need to flash the newest twrp recovery, a lot of ppl have been having issues with cwm lately so my advice would be to DL the twrp tar file and use that to root and not cwm
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
I will try that, I use TWRP for my Nexus 4. That being said, do i have to go back to stock and unroot, or just flash TWRP and attempt to install CM?

EgoTrip26 said:
I will try that, I use TWRP for my Nexus 4. That being said, do i have to go back to stock and unroot, or just flash TWRP and attempt to install CM?
Click to expand...
Click to collapse
Just flash recovery then cm rom.
Sent from my SGH-M919 using Tapatalk 2

Thanks a million!
Thanks to both of you for prompt response, Used TWRP and at least got CM to flash and startup, so far so good. hope it works as well on the S2 as it does on my phone!
Thanks again

[Very serious]Non-booting/non-changing/not working problem

I woke up today to a bootloop. After pulling out the battery, I cant turn it on, it was stuck at the google logo. I thought it was some rom issue or something. When I had the time, in the afternoon, I just boot to recovery, and wiped data+sd card. Turns out sd card was not wiped.
Just now, I found a way to boot it. (AFTER WIPING DATA) I used the gnex toolkit and boot with insecure image, and guess wat? My old rom boots. Everything was the way it was, and then it crashed and stuck on the google logo again.(I made sure i wiped things two to three times, data and sd) I did a few experiments:
1) Flash using ODIN
2) Flash CWM using toolkit--it changed back to twrp after reboot
3) Changing the icon on my homescreen after boot--- everything was the same again after booting
4) Flash stock image using toolkit
5) Wipe data using manual adb
6) Try to lock my bootloader
Everything I tried changing, change back to the original state after reboot. What is the problem?
Device: Galaxy Nexus
ROM: Purity 7 sept release
Kernel: Fancy r42
Logs in twrp are showing updating partition, not FAIL. So I really don't think there is a need to show the recovery log.
HELP ME!

are you flashing your recovery or just booting the recovery?
fastboot oem unlock
fastboot flash recovery recovery.img
use ClockWorkMod. I've heard nothing but problems with TWRP.

player911 said:
are you flashing your recovery or just booting the recovery?
fastboot oem unlock
fastboot flash recovery recovery.img
use ClockWorkMod. I've heard nothing but problems with TWRP.
Click to expand...
Click to collapse
umm, i can boot recovery. i cannot flash cwm. i tried, but when i reboot, it went back to twrp.
what is oem unlock for? coz its smth i havent tried.

jacktay94 said:
umm, i can boot recovery. i cannot flash cwm. i tried, but when i reboot, it went back to twrp.
what is oem unlock for? coz its smth i havent tried.
Click to expand...
Click to collapse
Oem unlock will unlock your bootloader and wipe the internal storage in the process. I saw you didn't use fastboot. You could try that. Flash the Factory image via fastboot. If that fails try omap flash.
Sent from my Galaxy Nexus using XDA Premium HD app

mrgnex said:
Oem unlock will unlock your bootloader and wipe the internal storage in the process. I saw you didn't use fastboot. You could try that. Flash the Factory image via fastboot. If that fails try omap flash.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Yup,I tried it already thru toolkit. Not working either.

Dude the toolkit blows, flash back to stock manually via adb command prompt. There are tutorials around here on how to do it. It's guaranteed to work if you don't screw it up.
Honestly flashing back to stock via adb should be something everyone should learn if you plan on flashing roms.

SoHaunted said:
Dude the toolkit blows, flash back to stock manually via adb command prompt. There are tutorials around here on how to do it. It's guaranteed to work if you don't screw it up.
Honestly flashing back to stock via adb should be something everyone should learn if you plan on flashing roms.
Click to expand...
Click to collapse
i did adb bro, its the last thing i tried, i learnt and try.
Sent to Samsung centre, they told me its my flash IC thats blown. sobs