Develop Bugs

[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?

[Q] TWRP Unable to mount internal card

A100 rooted unlocked CarbonRom from pio. My rom works fine, I can still boot into it. But I've become a flasher lately, and want to keep trying other roms. When I boot to recovery and try to wipe data. I get an error that it failed, and the log says unable to mount '/data' (tw_mount). But like I said, i can still boot into my current rom"pio's awesome CarbonRom", I just wanted to try some other roms. I tried 'fastboot flashing a100-fstab-fixed-for-twrp-boot.img', that I got from 2nd post on http://forum.xda-developers.com/showthread.php?t=2431506 . I used the command 'fastboot flash recovery a100-fstab-fixed-for-twrp-boot.img' . Then recovery wouldn't boot at all, and just goes straight to CarbonRom, which I am glad it hasn't bricked. So I boot back into bootload from adb with fastboot, and and reinstalled twrp 2.2.2.1 with 'fastboot flash recovery openrecovery-twrp-2.2.2.1-a100.img' . So now I got a twrp working again, but I was a 2.6, and this one still doesn't mount data. Any tips?

bigbpc said:
A100 rooted unlocked CarbonRom from pio. My rom works fine, I can still boot into it. But I've become a flasher lately, and want to keep trying other roms. When I boot to recovery and try to wipe data. I get an error that it failed, and the log says unable to mount '/data' (tw_mount). But like I said, i can still boot into my current rom"pio's awesome CarbonRom", I just wanted to try some other roms. I tried 'fastboot flashing a100-fstab-fixed-for-twrp-boot.img', that I got from 2nd post on http://forum.xda-developers.com/showthread.php?t=2431506 . I used the command 'fastboot flash recovery a100-fstab-fixed-for-twrp-boot.img' . Then recovery wouldn't boot at all, and just goes straight to CarbonRom, which I am glad it hasn't bricked. So I boot back into bootload from adb with fastboot, and and reinstalled twrp 2.2.2.1 with 'fastboot flash recovery openrecovery-twrp-2.2.2.1-a100.img' . So now I got a twrp working again, but I was a 2.6, and this one still doesn't mount data. Any tips?
Click to expand...
Click to collapse
You flashed kernel over recovery, you really need to triple check commands like that.
fastboot flash boot a100-fstab-fixed-for-twrp-boot.img
Notice its flash boot, that portion tells where to flash the image to, when you said recovery it wrote it there instead.
Sent from my Galaxy Nexus using Tapatalk 2

pio_masaki said:
You flashed kernel over recovery, you really need to triple check commands like that.
fastboot flash boot a100-fstab-fixed-for-twrp-boot.img
Notice its flash boot, that portion tells where to flash the image to, when you said recovery it wrote it there instead.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thank you so much pio_masaki. I should have came to the forums first rather then try to put together fragmented information in my brain. I know little to nothing of adb and fastboot. You are awesome.

[Q] Possilble bricked brand new Nexus 7... please help!!!

Alrighty... so I just got the 2013 Nexus 7 (Asus), everything was fine, got it unlocked and rooted on Kit Kat 4.4, but I just ruined it.
I was checking out some font installer app... I made a backup of original fonts, installed a new font, didn't like it, reinstalled back original fonts, and then the Nexus would not turn back on after installing the backup. It was stuck on the Kit Kat boot logo. I tried a few things, nothing worked... went into recovery, tried restoring everything, and now it's saying I don't have an OS installed.
I cannot do anything but get into the bootloader which says fastboot mode and all that and I can still get into recovery.
I did not make any backups... I'm new to Android and now I learned my lesson. Any help please?
I got it as a gift so I can't even return it anywhere... no reciept.

ta_help said:
Alrighty... so I just got the 2013 Nexus 7 (Asus), everything was fine, got it unlocked and rooted on Kit Kat 4.4, but I just ruined it.
I was checking out some font installer app... I made a backup of original fonts, installed a new font, didn't like it, reinstalled back original fonts, and then the Nexus would not turn back on after installing the backup. It was stuck on the Kit Kat boot logo. I tried a few things, nothing worked... went into recovery, tried restoring everything, and now it's saying I don't have an OS installed.
I cannot do anything but get into the bootloader which says fastboot mode and all that and I can still get into recovery.
I did not make any backups... I'm new to Android and now I learned my lesson. Any help please?
I got it as a gift so I can't even return it anywhere... no reciept.
Click to expand...
Click to collapse
ROM sideload via recovery.
D
Sent from my AOSP on Flo using Tapatalk 4

DatDude123 said:
ROM sideload via recovery.
D
Sent from my AOSP on Flo using Tapatalk 4
Click to expand...
Click to collapse
Well now to make matters worse... I tried using the Nexus root toolkit to do the restore + lock or whatever the option was and it didn't work... but it looks like doing that caused my recovery mode to go bye bye.
So now when I scroll to recovery mode, it just restarts to the bootloader.
I still have the openrecovery.img file.. anyway I can inject it using an adb command or something to side load?

scratch that last reply, I used the command "fastboot flash recovery" and it's good.
now when I go to ADB sideload in recovery, it says unable to mount /system, unable to mount /cache and everything failed... failed to decrypt data and sideload failed.
When I type in a sideload command to terminal it just says error: closed

Flash the factory image from https://developers.google.com/android/nexus/images

I tried that, it still gives me error: closed when I try to flash it.
When I type 'adb devices' it just says my device is in recovery, even if I'm in the sideload, I know it's supposed to say sideload instead.
I just want to get it back to normal I don't care if I lose root and lock it someone help!!

ta_help said:
I tried that, it still gives me error: closed when I try to flash it.
When I type 'adb devices' it just says my device is in recovery, even if I'm in the sideload, I know it's supposed to say sideload instead.
I just want to get it back to normal I don't care if I lose root and lock it someone help!!
Click to expand...
Click to collapse
What exactly did you do when trying to flash the factory image?

[Q] How to Flash TWRP with no filesystem.(CWM will talk adb, but Fastboot won't)

I'm at an impasse with my HTC one. I was following the directions in this thread http://forum.xda-developers.com/showthread.php?p=49970264#post49970264. Long story short, I now have CWM v6.0.4.7 and S-Off, but no file system whatsoever.
I have ADB connectivity when in CWM using universal USB drivers, but I can't get Fastboot to communicate to my PC viea ADB (phone says Fastboot USB, but even with the latest Sync drivers installed and Sync removed I get nothing).
I have 3 different Rom packages (Viper 5.0, ecliptic 1.3, and a debloat 4.4.2) loaded in in the SD card directory. Every time I try to flash one of these roms I get a "format() expects 5 args, got for (status 7) error". I think this is due to the version of CWM that I'm running. I think the problem will be fixed by flashing TWRP.
This brings me to my request, been googling for hours to get back to the state where I can actually communicate with my phone, and I think I have a solution, but I haven't been able to figure out how to load TWRP onto my phone with the only means of successful communication being through CWM. Any direction here would be welcome. (I read something about wrapping TWRP into an update.zip file and got a little lost)
Critical phone info:
Recovery: CWM 6.0.4.7
M7_WLV Pvt Ship S-OFF RH
CID-VZW_001
HBOOT 1.56.0000
OpenDSP-v32.120.274.0909
OS-3.11.605.1
eMMC Boot 2048MB
edit: I just noticed that the HTC is showing up in my device manager as "My HTC" when in Fastboot. It's using driver version 2.0.7.23 from 11/1/2013. Still not sure why I can't talk to it in fastboot though.

wantasmartcookie said:
I'm at an impasse with my HTC one. I was following the directions in this thread http://forum.xda-developers.com/showthread.php?p=49970264#post49970264. Long story short, I now have CWM v6.0.4.7 and S-Off, but no file system whatsoever.
I have ADB connectivity when in CWM using universal USB drivers, but I can't get Fastboot to communicate to my PC viea ADB (phone says Fastboot USB, but even with the latest Sync drivers installed and Sync removed I get nothing).
I have 3 different Rom packages (Viper 5.0, ecliptic 1.3, and a debloat 4.4.2) loaded in in the SD card directory. Every time I try to flash one of these roms I get a "format() expects 5 args, got for (status 7) error". I think this is due to the version of CWM that I'm running. I think the problem will be fixed by flashing TWRP.
This brings me to my request, been googling for hours to get back to the state where I can actually communicate with my phone, and I think I have a solution, but I haven't been able to figure out how to load TWRP onto my phone with the only means of successful communication being through CWM. Any direction here would be welcome. (I read something about wrapping TWRP into an update.zip file and got a little lost)
Critical phone info:
Recovery: CWM 6.0.4.7
M7_WLV Pvt Ship S-OFF RH
CID-VZW_001
HBOOT 1.56.0000
OpenDSP-v32.120.274.0909
OS-3.11.605.1
eMMC Boot 2048MB
edit: I just noticed that the HTC is showing up in my device manager as "My HTC" when in Fastboot. It's using driver version 2.0.7.23 from 11/1/2013. Still not sure why I can't talk to it in fastboot though.
Click to expand...
Click to collapse
Did you previously have fastboot connectivity and have not changed anything on pc. Are you using Windows 8 by any chance? I'll see if I can figure out the zip. I know you can flash with a zip in RUU mode but I have not tried a recovery zip yet.

Gizmoe said:
Did you previously have fastboot connectivity and have not changed anything on pc. Are you using Windows 8 by any chance? I'll see if I can figure out the zip. I know you can flash with a zip in RUU mode but I have not tried a recovery zip yet.
Click to expand...
Click to collapse
I did have ADB connectivity in all modes. Using Windows 7 64 bit.

And a bit more info. Uninstalled the MyHTC driver and plugged the phone back int. The device showed up as "Android 1.0" when installing the drivers. Drivers successfully installed, HTC One showing up in device tree. Still no adb connectivity in fastboot.
The device shows up as Google Galaxy Nexus ADB Interface when CWM is running.
One other note, I've been running the all on my work laptop (which i just got) and noticed it's all USB 3.0 ports. Didn't realize it at first cause they weren't blue but they have the "SS" symbol (and now I know what that means). Going to try to get this up and running on my old tower PC.

wantasmartcookie said:
I did have ADB connectivity in all modes. Using Windows 7 64 bit.
Click to expand...
Click to collapse
Looks like there is not a way to make a zip to flash recovery via recovery.
But are you using fastboot commands like
"fastboot devices"
Or
"fastboot flash recovery recovery.img"
Seems like Windows 7 is loading a bad driver.

Gizmoe said:
Looks like there is not a way to make a zip to flash recovery via recovery.
But are you using fastboot commands like
"fastboot devices"
Or
"fastboot flash recovery recovery.img"
Seems like Windows 7 is loading a bad driver.
Click to expand...
Click to collapse
i'm using adb commands like get-serialno and fastboot commands like fastboot devices. I get no response when its in Fastboot mode, but it will respond when CWM is up. I'm currently looking into Flash_Image, but it looks like I need a binary that's specific to the one.

Flash a RUU get back to factory, then do twrp
Sent from my HTC6500LVW using XDA Premium 4 mobile app

aer0zer0 said:
Flash a RUU get back to factory, then do twrp
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Since he has no Rom and no fastboot access and an old recovery that uses less mounting arguments. That is not currently an option. I guess you could try and edit the updater script just to get a booting Rom but with the HTC one I am not sure if older update binaries will work even with the right updater script.

His recovery is the latest cwm actually. The issue he is getting (status 7) is because the format of the updater script in the rom zips isn't acceptable for the recovery. See this post from Phil.
http://forum.xda-developers.com/showthread.php?p=43707326
Sent from my HTC6500LVW using Tapatalk

You need to find a rom that has an updated updater script. I assume the status 7 error you get is (got 4 arguments, expects 5). You also said it shows up as a galaxy when in cwm. This leads me to believe you have the wrong driver installed. http://vzw1files.dyndns.org/ADB/ADB_Drivers.zip And as you already figured out usb3 doesnt play nice with adb.

disconnecktie said:
His recovery is the latest cwm actually. The issue he is getting (status 7) is because the format of the updater script in the rom zips isn't acceptable for the recovery. See this post from Phil.
http://forum.xda-developers.com/showthread.php?p=43707326
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
That basically was my point but I suppose it read a little different. The version of cwm doesn't accept the new format of 5 arguments. Philz and twrp do. I dont know the status of the current version of cwm but assumed they would have fixed that by now.

Gizmoe said:
That basically was my point but I suppose it read a little different. The version of cwm doesn't accept the new format of 5 arguments. Philz and twrp do. I dont know the status of the current version of cwm but assumed they would have fixed that by now.
Click to expand...
Click to collapse
He could try doing like Phil suggests and try swapping the updater-binary with one from a newer Rom to see if that would make it flash.
Sent from my HTC6500LVW using Tapatalk

@wantasmartcookie yes you should try a newer update binary and see what happens as @disconnecktie suggested.
Sent from my HTC6500LVW using Tapatalk

cmlusco said:
You need to find a rom that has an updated updater script. I assume the status 7 error you get is (got 4 arguments, expects 5). You also said it shows up as a galaxy when in cwm. This leads me to believe you have the wrong driver installed. http://vzw1files.dyndns.org/ADB/ADB_Drivers.zip And as you already figured out usb3 doesnt play nice with adb.
Click to expand...
Click to collapse
Just installed the drivers on my old PC (w/usb 2.0) and got the SDK installed and running. I was able to get Fastboot to respond. I flashed the latest TWRP 2.6.3.3 (and 2.6.3.0) and it goes into a boot loop. I see the HTC w/red text saying it boots into recovery. Screen goes black. normal HTC boot screen comes back an boot loops to that scream. I believe a few cuss words are in order at this point. At least I'm able to flash recoveries now. Going to go try Philz and possibly go back to CWM and see if I can get an image with the correct install format.
Appreciate the help from everyone in this thread so far.

Try this before you flash the recovery use the command
Code:
fastboot erase recovery
If that dosent work, flash back to stock recovery, reboot the phone, then flash back to twrp. By the way the latest twrp is 2.6.3.4. http://vzw1files.dyndns.org/RECOVERIES/ You could also flash twrp thru RUU mode with the zip file from that site.

Just recovered my phone! I was able to install the latest Philz recovery. Unchecked the "do not use old installer" option (after getting the expected 5 got 4 arg error) and installed Ecliptic 1.3. Thank you everyone for your help!

wantasmartcookie said:
Just recovered my phone! I was able to install the latest Philz recovery. Unchecked the "do not use old installer" option (after getting the expected 5 got 4 arg error) and installed Ecliptic 1.3. Thank you everyone for your help!
Click to expand...
Click to collapse
wantasmartcookie said:
Just installed the drivers on my old PC (w/usb 2.0) and got the SDK installed and running. I was able to get Fastboot to respond. I flashed the latest TWRP 2.6.3.3 (and 2.6.3.0) and it goes into a boot loop. I see the HTC w/red text saying it boots into recovery. Screen goes black. normal HTC boot screen comes back an boot loops to that scream. I believe a few cuss words are in order at this point. At least I'm able to flash recoveries now. Going to go try Philz and possibly go back to CWM and see if I can get an image with the correct install format.
Appreciate the help from everyone in this thread so far.
Click to expand...
Click to collapse
Congrats. I figured it was a pc issue being unable to use fastboot. Glad you got your phone back.

[Q] HTC One M8 (bricked?)

Hi guys I am trying to get my phone in some sort of working order. I have CWM Recovery 6.0.5.1 for some reason no matter what I do to change the recovery it stays the same. I've tried installing lower CWM and also tried installing TWRP which again it says it was installed but when i go to recovery it still shows the CWM recovery. I installed CM11 and it worked fine, when I installed gapps is when the problems started. I've tried install multiple roms now, and it just doesn't want to take anything

thetinyjesus said:
Hi guys I am trying to get my phone in some sort of working order. I have CWM Recovery 6.0.5.1 for some reason no matter what I do to change the recovery it stays the same. I've tried installing lower CWM and also tried installing TWRP which again it says it was installed but when i go to recovery it still shows the CWM recovery. I installed CM11 and it worked fine, when I installed gapps is when the problems started. I've tried install multiple roms now, and it just doesn't want to take anything
Click to expand...
Click to collapse
try restoring a stock nandroid backup. if you dont have one then download one from general thread. and also make a nandroid backup of your current rom. not so sure what your problem is but maybe returning to pure stock will help.

I am trying to load the nandroid but I cannot get this recovery to work right. I've tried installing openrecovery-twrp to install the nandroid but i cant get the CWM to remove. I really dont mind what bootloader is on there but anything just to install any rom

thetinyjesus said:
I am trying to load the nandroid but I cannot get this recovery to work right. I've tried installing openrecovery-twrp to install the nandroid but i cant get the CWM to remove. I really dont mind what bootloader is on there but anything just to install any rom
Click to expand...
Click to collapse
Install/flash via fastboot the official cwm 6.0.51 that you had. then try again. if your lucky then it might work.

thetinyjesus said:
I am trying to load the nandroid but I cannot get this recovery to work right. I've tried installing openrecovery-twrp to install the nandroid but i cant get the CWM to remove. I really dont mind what bootloader is on there but anything just to install any rom
Click to expand...
Click to collapse
Get TWRP Manager from the play store. Hit the three line menu thingy on the top left of the app, and pick install TWRP. Super easy.

Ok guys ive tried reinstalling the same CWM version and reinstalling CM11 with no luck. I cannot change the bootloader to TWRP because it appears to be stuck on the CWM. The problem started for me when I installed the gapps through CWM, as soon as I did that when the phone went to boot it now says please enter the password for android, then says it was the right password but data is corrupt and cant use phone.
Is there a way to attempt to just format the entire phone including partition size and start from scratch again?

thetinyjesus said:
Ok guys ive tried reinstalling the same CWM version and reinstalling CM11 with no luck. I cannot change the bootloader to TWRP because it appears to be stuck on the CWM. The problem started for me when I installed the gapps through CWM, as soon as I did that when the phone went to boot it now says please enter the password for android, then says it was the right password but data is corrupt and cant use phone.
Is there a way to attempt to just format the entire phone including partition size and start from scratch again?
Click to expand...
Click to collapse
How are you trying to flash these recoveries (they're not called bootloaders, that is something totally separate)?
Have you tried using TWRP Manager as I suggested earlier, or are you using ADB? And If you are using ADB and trying to flash it that way, what fastboot commands are you giving?
There is no way that your should be "stuck" with CWM.

Okay what i have to do is fastboot its the only thing i can get to work. Not at my computer but yeah i fastboot the recovery img via cmd in windows. Fastboot flash recovey i use ane it successfully does. Doesnt matter what img or recovery i use when i boot into recovery it still uses cwm. Also only way i can put a rom on is adb sideload but now thats even failing with status 7 error

Also when i try the command fastboot oemRUU or whatever the command is it reboots the phone shows CM logo and boots till asking for android pw

thetinyjesus said:
Okay what i have to do is fastboot its the only thing i can get to work. Not at my computer but yeah i fastboot the recovery img via cmd in windows. Fastboot flash recovey i use ane it successfully does. Doesnt matter what img or recovery i use when i boot into recovery it still uses cwm. Also only way i can put a rom on is adb sideload but now thats even failing with status 7 error
Click to expand...
Click to collapse
The status 7 error is because of an outdated recovery. Not much help, I know.
It's strange that the TWRP Manager doesn't work. I've helped others with problems flashing recovery, and it has worked for them.
You could also try ROM Toolbox to update your CWM, or ROM Manager, but ROM Toolbox is better/more complete. It has everything ROM Manager has plus some.
The other option that you may not want to take is to do a COMPLETE wipe of your phone. That always sucks.

Going to try those programs. Thank you btw and how do i perform the full wipe i was about to throw the phone out lol.

@thetinyjesus You could also try this app. No PC necessary.

Thanks but cannot use the app i cannot get the phone to boot. Do you have directions for a full wipe

thetinyjesus said:
Going to try those programs. Thank you btw and how do i perform the full wipe i was about to throw the phone out lol.
Click to expand...
Click to collapse
Actually, you full wipe in recovery. lol
If you haven't tried TWRP Manager yet, that would be my first choice.

Damn that didnt work than i tried all those format options in the bunked recovery with no luck it sucks

If you're using the command prompt to flash the recovery, provide a screenshot of your desktop so that we can see what you're doing and what "it's" doing.
Starting to think that it's more of an "operator" fault and not anything to do with the device that doesn't want to play along.

Okay once im back home ill show the output

Here is the output from flashing the recovery. Once again when I went to recovery it loaded with CWM.

Also here is the output from sideloading the cm file again (same error no matter what rom I try)
Windows CMD: C:\Users\Jimmy\Desktop\platform-tool>adb sideload cm.zip
sending: 'cm.zip' 100%
Phone: Installing update...
set_perm_recursive: "/system" not a valid uid
E: Error in /tmp/update.zip
(Status 7)
Installation aborted

Anyone?