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

[GSM] Recovery doesnt work/Cant flash any Rom

Hi, i just got my Galaxy Nexus and unlocked+rooted it with the Toolkit v6.1.
Then i flashed CWM Recovery and tried flashing a Rom (Slim ICS), but i got the error: E: Can't open /sdcard/Base_3.6.zip (bad) Installation aborted.
What is also unnormal: I can't boot into Recovery normally. When i try to get into recovery via Fastboot, i get Screen with a green Android, laying down, chest open, with a red sign in it. Well, doesnt look so good...
I was only able to recovery when i flashed it via Rom Manager and then booted to it via Rom Manager. Whats also strange: After Wiping & trying to flash (back @ stock settings), the recovery seemed to be gone again. I had to reflash it again via Rom Manager, to make it work.
I got the impression, that there is something wrong with my phone's permissions. Any ideas how i can fix that?
Thx for the help!

W4yl4nder said:
..I was only able to recovery when i flashed it via Rom Manager and then booted to it via Rom Manager..
Click to expand...
Click to collapse
thats the problem, flash the recovery via fastboot. rom manager really sucks, im surprised so many people use it. in the end, it causes more headaches than it prevents. btw, you should try twrp recovery instead, its much better than cwm recovery.

Please don't use toolkits or all-in-one's or one-click's unless you understand what they do and how they do it. There's simply no need for a toolkit on this device.
Code:
> fastboot oem unlock
> fastboot flash clockworkmod-recovery.img recovery
Then you know that it's done, and done properly. I bet if you do that, you'll then be able to boot directly into recovery.

codesplice said:
Please don't use toolkits or all-in-one's or one-click's unless you understand what they do and how they do it. There's simply no need for a toolkit on this device.
Code:
> fastboot oem unlock
> fastboot flash clockworkmod-recovery.img recovery
Then you know that it's done, and done properly. I bet if you do that, you'll then be able to boot directly into recovery.
Click to expand...
Click to collapse
actually, it's 'fastboot flash recovery clockworkmod-recovery.img'.
Sent from my Transformer Prime TF201

bk201doesntexist said:
actually, it's 'fastboot flash recovery clockworkmod-recovery.img'.
Sent from my Transformer Prime TF201
Click to expand...
Click to collapse
That too, sorry. Got my head twisted up trying to handle [ CODE ] tags from my phone.

i got the recovery now (forgot to delete auto-reflash-recovery-on-boot file :/), but its still not working. when trying to flash a rom i still get the same error (also in twrp recovery).

W4yl4nder said:
i got the recovery now (forgot to delete auto-reflash-recovery-on-boot file :/), but its still not working. when trying to flash a rom i still get the same error (also in twrp recovery).
Click to expand...
Click to collapse
Verify that the zip is good?

help phone is not booting

yesterday i was in the franco kernel updater app and i saw a new nightly to i wanted to flash it but by mistake i looks like flashed milstone version so the device got root access to restart the device and flash the kernel
but the device rebooted to stuck at Google logo for 15min so i pulled out the battery re-insert it and press the power button and nothing happens still stuck at Google logo with no boot loop or restarting it self
i can get to CWM and fastboot but when i start the device its stuck at that :crying:
my phone is on that way since yesterday and i cant leave it like this for longer time since iam travailing nor can i wipe every thing on it and get a fresh start cuz i do have important things on the sdcard
plz help
i do believe its a kernel related issue but what can i do ?? i cant push a .zip kernel to flash it in CWM

jik saw said:
yesterday i was in the franco kernel updater app and i saw a new nightly to i wanted to flash it but by mistake i looks like flashed milstone version so the device got root access to restart the device and flash the kernel
but the device rebooted to stuck at Google logo for 15min so i pulled out the battery re-insert it and press the power button and nothing happens still stuck at Google logo with no boot loop or restarting it self
i can get to CWM and fastboot but when i start the device its stuck at that :crying:
my phone is on that way since yesterday and i cant leave it like this for longer time since iam travailing nor can i wipe every thing on it and get a fresh start cuz i do have important things on the sdcard
plz help
i do believe its a kernel related issue but what can i do ?? i cant push a .zip kernel to flash it in CWM
Click to expand...
Click to collapse
what rom zip files do you have on your sdcard.

thanked for error.
tried flashing a boot.img via fastboot?standard or from another dev's kernel not in AK format (zimage)
or
tried flash another rom that you have zip inside phone?if you dirty flash,you simple don't loose anything..and the boot.img it's reflashed.
WRONG SECTION;READ THE RULES

jik saw said:
yesterday i was in the franco kernel updater app and i saw a new nightly to i wanted to flash it but by mistake i looks like flashed milstone version so the device got root access to restart the device and flash the kernel
but the device rebooted to stuck at Google logo for 15min so i pulled out the battery re-insert it and press the power button and nothing happens still stuck at Google logo with no boot loop or restarting it self
i can get to CWM and fastboot but when i start the device its stuck at that :crying:
my phone is on that way since yesterday and i cant leave it like this for longer time since iam travailing nor can i wipe every thing on it and get a fresh start cuz i do have important things on the sdcard
plz help
i do believe its a kernel related issue but what can i do ?? i cant push a .zip kernel to flash it in CWM
Click to expand...
Click to collapse
Try restoring from nand backup or reinstall the ROM
Sent from my Galaxy Nexus using xda premium

As nexxusdev is implying, just flash your ROM again.
Sent from my Galaxy Nexus using xda premium

nexxusdev said:
what rom zip files do you have on your sdcard.
Click to expand...
Click to collapse
i have none not even the kernel zip file
sert00 said:
thanked for error.
tried flashing a boot.img via fastboot?standard or from another dev's kernel not in AK format (zimage)
or
tried flash another rom that you have zip inside phone?if you dirty flash,you simple don't loose anything..and the boot.img it's reflashed.
WRONG SECTION;READ THE RULES
Click to expand...
Click to collapse
i will try to flash boot.img from another kernel and will see what happens
and i dont have any flash zip files in my sd card but i learned the lesson i will always leaves a kernel zip and rom zip file in case
and sorry for that but i was in hurry my primary phone is messed up
Chance Ill said:
Try restoring from nand backup or reinstall the ROM
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
iam on stock JB
obtained said:
As nexxusdev is implying, just flash your ROM again.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
its stock JB rom flashed it over with galaxy nexus toolkit and downloaded the rom from google's site so its not a zip flashable
thanks all for replys and sorry for thw wrong section

im not sure but i remember on my g2x you could hook up phone from recovery mode and mount it on the computer with sd card .. have you looked around in CWM? This is your fault to be honest you deserve this for not making a NAND back up. ALWAys MAKE A BACK UP! period. There is a reason why devs and everyone else stress' it so much.

Sert00 is right. Flash any [previously] working ROM on it. It will be a dirty flash and some stuff won't work, but you'll be able to backup your data. You'll reflash again later
ed116 said:
im not sure but i remember on my g2x you could hook up phone from recovery mode and mount it on the computer with sd card .. have you looked around in CWM? This is your fault to be honest you deserve this for not making a NAND back up. ALWAys MAKE A BACK UP! period. There is a reason why devs and everyone else stress' it so much.
Click to expand...
Click to collapse
Unfortunately, at least with these beta realeases of JB, usb mount via recovery almost never work.
Try what sert00 told you.

jik saw said:
yesterday i was in the franco kernel updater app and i saw a new nightly to i wanted to flash it but by mistake i looks like flashed milstone version so the device got root access to restart the device and flash the kernel
but the device rebooted to stuck at Google logo for 15min so i pulled out the battery re-insert it and press the power button and nothing happens still stuck at Google logo with no boot loop or restarting it self
i can get to CWM and fastboot but when i start the device its stuck at that :crying:
my phone is on that way since yesterday and i cant leave it like this for longer time since iam travailing nor can i wipe every thing on it and get a fresh start cuz i do have important things on the sdcard
plz help
i do believe its a kernel related issue but what can i do ?? i cant push a .zip kernel to flash it in CWM
Click to expand...
Click to collapse
fastboot is all you need. find a stock rom and flash
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase cache ???
fastboot erase data
this should work

thank u guys soooooooooooooooooooooooooooooooooooo much
iam very very very very great full to all of u for ur help and for giving me some ideas
i have solved it by extract the .tar imge file that i downloaded from here
and searched for the boot.img file flashed it over galaxy nexus toolkit and now the device restarted and android is upgrading 156 app lol
thanks again and sorry for the wrong section and hey .... why not editing the thread to make it a helpful guide to those who brick their phones like what i just did

djjonastybe said:
fastboot is all you need. find a stock rom and flash
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase cache ???
fastboot erase data
this should work
Click to expand...
Click to collapse
he didn't want to lose anything...also the data of apps
@jig saw
happy to read that!and from now on,leave inside the phone all the stuff you could need in case similar to what happened you!cheers!:laugh:

sert00 said:
he didn't want to lose anything...also the data of apps
@jig saw
happy to read that!and from now on,leave inside the phone all the stuff you could need in case similar to what happened you!cheers!:laugh:
Click to expand...
Click to collapse
no thank god i didnt lose any thing and the OS is operating normal
i really appreciate that mate
and lesson well learned i'm making folder in the sdcard for buck up stuff
cheers ^_^

Phone continually reboots

Alright this is extremely complicated to explain so bear with me.
Somethings to explain first:
- I have an HTC One V CDMA VM USA phone
- I have tried this multiple times
Okay first off, I've unlocked bootloader and rooted my phone (SuperSU). I decided to flash ClockWork Mod as my recovery. So I boot my phone in recovery and flash the AOKP rom. I make a nandroid backup. I then wipe everything (cache, delvik, data). I flash rom then gapps. I flashed JellyBoot5.zip to make sure my kernel files are correct (I'm using AOKP stable build Oct 17 2012). I then boot into bootloader and flash the boot.img "fastboot flash boot boot.img"
It would continually run in "Initiating Swagger" - so I tried to delete and reflash again. Only this time I am stuck in a complete boot loop. It would say "Initiating Swagger" then load up the start up screen, stutter for 2 seconds, move again, freeze, reboot. It is stuck in this process again and again and again. I flashed the correct kernel according to the author of AOKP.
This isn't my first time doing this. I have already unlocked the bootloader two previous times (I used RUU on my device twice already just to get it back to stock.
Here's the freaking kicker though, when i restored my back up it did the exact same thing on stock rom as it did the AOKP rom. This makes me seem there isn't a corrupted download or anything like that but wow is this starting to get on my nervous. I need extreme help. I've looked everywhere on the internet and nothing came up. I even used Jellyboot5 and which
What the heck is it? Is it a performance issue, or a SuperSU position. Or could it be something with the kernel?
I've yet to hear the right suggestion so I'm all ears.

Ok u need to flash a diff kernel
Problem solved
Sent from my One V using xda app-developers app

first thing first, don't restore all your data from sense roms until you boot up the rom for the first time.
second thing, after you boot up into the rom, go to Settings - Performance and lower down the maximum overclock to a respectable position (1024).
do this and keep me in the loop. i will be glad to help you further,

Which boot.img are you flashing with fastboot? You need to open the kernel zip file with 7zip, copy the boot.img to your fastboot folder, flash the Rom, flash gapps, flash the kernel zip all in recovery. Then reboot into bootloader, and flash the boot.img using fastboot. I have used jellyboot5 and sickkernel V2 successfully with AOKP.

riggerman0421 said:
Which boot.img are you flashing with fastboot? You need to open the kernel zip file with 7zip, copy the boot.img to your fastboot folder, flash the Rom, flash gapps, flash the kernel zip all in recovery. Then reboot into bootloader, and flash the boot.img using fastboot. I have used jellyboot5 and sickkernel V2 successfully with AOKP.
Click to expand...
Click to collapse
you don't flash the kernel zip in recovery. lol.

Jesus go and find there is a thread with.all the android terms...what it means and how to do it
It will help u so much
Do not flash the kernel in zip tru ur phone
Hot
Sent from my One V using xda app-developers app

cybervibin said:
Jesus go and find there is a thread with.all the android terms...what it means and how to do it
It will help u so much
Do not flash the kernel in zip tru ur phone
Hot
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
Relax man, I don't know a lot about this stuff.
1ceb0x said:
you don't flash the kernel zip in recovery. lol.
Click to expand...
Click to collapse
You don't? So if Jellyboot5 is in a zip, I just extract the boot.img, but I don't flash the actual zip, correct? I've flashed a different kernel but no luck.
Could you give me maybe some exact directions to using the AOKP rom, I used the ones on his post but for me they aren't detailed enough. I will hit thanks for sure
I'll let you know if this works later on. I can't do anything till tonight because I'm at school right now.

patbushnell said:
Relax man, I don't know a lot about this stuff.
You don't? So if Jellyboot5 is in a zip, I just extract the boot.img, but I don't flash the actual zip, correct? I've flashed a different kernel but no luck.
Could you give me maybe some exact directions to using the AOKP rom, I used the ones on his post but for me they aren't detailed enough. I will hit thanks for sure
I'll let you know if this works later on. I can't do anything till tonight because I'm at school right now.
Click to expand...
Click to collapse
ok man listen tight
put the rom in ur sd card, boot in recovery flash the ROM
now the tricky part
that jellyboot5(right click on it-its should be in a img format!
now open command prompt(hope u have the fastboot files,if not just write fastboot files in google)
now boot ur phone in fastboot(press the poer button and volume down for 15+ sec)
connect via usb it shud show fastboot usb
now direct the cmd to the directory(like cd:\android\)
paste the boot file in that and rename to boot.img
now write "fastboot flash boot boot.img"
and then fastboot reboot
done
now

cybervibin said:
ok man listen tight
put the rom in ur sd card, boot in recovery flash the ROM
now the tricky part
that jellyboot5(right click on it-its should be in a img format!
now open command prompt(hope u have the fastboot files,if not just write fastboot files in google)
now boot ur phone in fastboot(press the poer button and volume down for 15+ sec)
connect via usb it shud show fastboot usb
now direct the cmd to the directory(like cd:\android\)
paste the boot file in that and rename to boot.img
now write "fastboot flash boot boot.img"
and then fastboot reboot
done
now
Click to expand...
Click to collapse
I followed that literally word for word, still freezing and rebooting constantly.. It runs but just continues to reboot.

when you root your phone lots of strange things happen......that used to happen to me from a while and it jst got solved by itself ...i dint install any rom or anything it just went .......so be patient

patbushnell said:
I followed that literally word for word, still freezing and rebooting constantly.. It runs but just continues to reboot.
Click to expand...
Click to collapse
Ur doing something wrong ur cdma right
Sent from my One V using xda app-developers app

cybervibin said:
Jesus go and find there is a thread with.all the android terms...what it means and how to do it
It will help u so much
Do not flash the kernel in zip tru ur phone
Hot
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
1ceb0x said:
you don't flash the kernel zip in recovery. lol.
Click to expand...
Click to collapse
He has the CDMA VM version. If you will look at the op for both jmz's and Simon's kernels, you need to flash the zip in recovery to install needed lib files and modules to get Wi-Fi working properly. Please do your research.

Your running out of memory. Dont restore the sense crap
Sent from my One V using Tapatalk 2

cybervibin said:
Ur doing something wrong ur cdma right
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
Yep! Here, check out this video. It's everything I'm doing.
http://www.youtube.com/watch?v=IIqT-xd0AqU&feature=youtu.be

donhashem.dh said:
when you root your phone lots of strange things happen......that used to happen to me from a while and it jst got solved by itself ...i dint install any rom or anything it just went .......so be patient
Click to expand...
Click to collapse
That happens when you don't know what you're doing.
Sent from my One V using xda app-developers app

i cant understand man its all mirrored!! IN THE VIDEO PLEASE UPLOAD A NEW ONE

soham_sss said:
That happens when you don't know what you're doing.
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
So do you have any idea what's wrong?

and AOKP nov9 build is come! FLASH that

riggerman0421 said:
He has the CDMA VM version. If you will look at the op for both jmz's and Simon's kernels, you need to flash the zip in recovery to install needed lib files and modules to get Wi-Fi working properly. Please do your research.
Click to expand...
Click to collapse
oh, ok, sorry for my ignorance. i thought he is flashing the whole boot.img from recovery (if it is in a zip format).so you need to flash boot.img through fastboot, go to recovery, full wipe everything (system, data, cache partition), flash your rom and after that flash the jellyboot.zip that has the needed files. reboot and if you did everything correctly, it SHOULD work!

Have to reflash kernel everytime aosp

I have been having many issues flashing roms on this phone, the number one issue is that my phone often gets stuck in boot loop after flashing aosp/cm/aokp etc roms. What I figured out is that everytime I reboot the device it will get stuck in boot loop, the only solution is to flash kernel via fastboot quite inconvenient as I do not always have my netbook with me. Perhaps it could have something to do with the update, however I have used the ruu to stock many times and this last time I did not update. Unless the hboot got permanently up dated and using the ruu back to stock doesn't revert back to the old one...
In any case am I the only one having these issues? I really don't mind sense and I love all the cool widgets but I want Jellybean so I would rather not go back to ics.

dude, both the kernels sense and aosp are seperate, only solution is take a backup via cwm or TWRP AND restore it whjen u want

I understand sense kernels are different than aosp, my problem is that after I flash rom+gapps+kernel reboot into fastboot fastboot boot boot.img that phone boots up and all is well except when I reboot as in turn power off then on my phone will bootloop. I was under the impression that once you fastboot boot boot.img you only had to reflash the kernel when you want to flash a new rom. I have to fastboot everytime my phone is shut down.
Also I just did a nandroid back up of stock rom with out flashing kernel in fastboot after using slickkernel(I forget the actual name) from aosp. So it appears that the kernel is only lasting at the intitial boot everything else gets defaulted to stock kernel.

md1008 said:
I understand sense kernels are different than aosp, my problem is that after I flash rom+gapps+kernel reboot into fastboot fastboot boot boot.img that phone boots up and all is well except when I reboot as in turn power off then on my phone will bootloop. I was under the impression that once you fastboot boot boot.img you only had to reflash the kernel when you want to flash a new rom. I have to fastboot everytime my phone is shut down.
Also I just did a nandroid back up of stock rom with out flashing kernel in fastboot after using slickkernel(I forget the actual name) from aosp. So it appears that the kernel is only lasting at the intitial boot everything else gets defaulted to stock kernel.
Click to expand...
Click to collapse
ok try this, download sick kernel fastboot it, the flash the image via cwm

I figured out my own mistake, I was using fastboot boot boot.img which does not flash the kernel but is more of a test drive. So I now did this and all is right with the world fastboot flash boot boot.img. I do not have a lot of experience with fastboot or bootloaders. Sorry to clutter the Q&A

Ohhhh lol good
Sent from my One V using xda premium

Out of curiosity, could you provide detailed instructions on what you did? I am having the same issue as you were, I believe.

mastertr said:
Out of curiosity, could you provide detailed instructions on what you did? I am having the same issue as you were, I believe.
Click to expand...
Click to collapse
Here are the steps
*Download rom, gapps, kernel
*in recovery factory reset, wipe system ( optional)
*install ROM, gapps, kernel
*reboot into boot loader(hboot)
*Mount USB and extract boot.IMG from ROM and put it in c:/Android
*make sure phone days fastboot, if not press power button
*open up adb
*CD c:/Android
*fastboot flash boot boot.img
*restart phone and out sticks
Important part is to add flash to the fastboot commands
Sent from my SGH-T999 using xda premium

Here
http://forum.xda-developers.com/showthread.php?t=1996665
Sent from my One V using xda premium