Database Info

[Q] Cannot load Recovery Clockwork

I'm trying to root my Nexus S 2.3.4 and so far I have unlocked it but when trying to flash Recovery Clockwork in the Command Prompt I get the error mesage "signature verification failed".
Any help would be appreciated.

XCarBoneX said:
I'm trying to root my Nexus S 2.3.4 and so far I have unlocked it but when trying to load Recovery Clockwork I get the error mesage "signature verification failed".
Any help would be appreciated.
Click to expand...
Click to collapse
How are you trying to flash your recovery?

krohnjw said:
How are you trying to flash your recovery?
Click to expand...
Click to collapse
I'm using [GUIDE] Step by Step ROOT Nexus S via ClockworkMod Recovery image (i9020/T only)
http://forum.xda-developers.com/showthread.php?t=895545

XCarBoneX said:
I'm using [GUIDE] Step by Step ROOT Nexus S via ClockworkMod Recovery image (i9020/T only)
http://forum.xda-developers.com/showthread.php?t=895545
Click to expand...
Click to collapse
You're getting Signature verification failed using fastboot flash recovery filename.img?
If so ensure a few things - 1.) you've got the correct file name and 2.) you have a good download of the img.

Filename is correct and img seems OK.
Boot Nexus S into Recovery Mode with USB debugging on
Command prompt:
fastboot flash recovery recovery-clockwork-3.0.2.4-crespo.img
error: cannot load 'recovery-clockwork-3.0.2.4-crespo.img
Win 7 64-bit SP1
Android 2.3.4 GRJ22 unlocked
Device Manager:
ADB Interface
Android Original ADB Interface
fastboot devices in Command shows:
33332EFE0C9300EC

XCarBoneX said:
Filename is correct and img seems OK.
Boot Nexus S into Recovery Mode with USB debugging on
Command prompt:
fastboot flash recovery recovery-clockwork-3.0.2.4-crespo.img
error: cannot load 'recovery-clockwork-3.0.2.4-crespo.img
Win 7 64-bit SP1
Android 2.3.4 GRJ22 unlocked
Device Manager:
ADB Interface
Android Original ADB Interface
fastboot devices in Command shows:
33332EFE0C9300EC
Click to expand...
Click to collapse
The error message did not say anything about signature verification failed. The problem is fastboot cannot find the file you specify in the command line.
SOLUTION: you have to go into the folder that you saved the "recovery-clockwork-3.0.2.4-crespo.img" (for example, if you saved the file in C:\android\) using the following commands:
Code:
c:
cd android
fastboot flash recovery recovery-clockwork-3.0.2.4-crespo.img

I have already set Path variables in Windows for the Andriod tools folder which contains Fastboot and the Recovery image file.
Could the problem be with the Android driver or Android 2.3.4 GRJ22?

XCarBoneX said:
I have already set Path variables in Windows for the Andriod tools folder which contains Fastboot and the Recovery image file.
Could the problem be with the Android driver or Android 2.3.4 GRJ22?
Click to expand...
Click to collapse
No - Fastboot can't find the file.
c:\Downloads>fastboot flash recovery fakefile.img
error: cannot load 'fakefile.img'
This takes place before checking if your device is connected, if you are unlocked to write the recovery, etc.
You're sure the cwd of the cmd prompt is the directory you downloaded the file to? Alternatively provide the full path to the recovery image.
Edit: Rereading your post above you have the recovery file in the directory as the tools. This won't resolve via the path. You either need to cd into that dir or provide the full path. Fastboot takes a local img file as the argument (local to your cwd unless you specify the full path).

Got it!!
Firmly rooted in Mother Earth.
You were absolutely correct with the cd\ command.
Running Cyanogen 7.02
Thanks so much!!

To fix hanging on cyanogen screen:
Factory data reset
wipe cache
advanced
wipe dalvik
All's good in Roots Reggae land.

XCarBoneX said:
Not quite done yet.
On reboot it hangs on the cyanogen screen.
Click to expand...
Click to collapse
You can either try reflashing or hook it up via adb and run a logcat - it will show you what it's hanging on or waiting on. Unless it's stuck *very* early on you should be able to adb shell and then run logcat.

Same problem here - Fastboot repeatedly returns "error: cannot load recovery.img" when trying to load CWM
Tried this solution:
suksit said:
SOLUTION: you have to go into the folder that you saved the "recovery-clockwork-3.0.2.4-crespo.img" (for example, if you saved the file in C:\android\) using the following commands:
Code:
c:
cd android
fastboot flash recovery recovery-clockwork-3.0.2.4-crespo.img
Click to expand...
Click to collapse
but I get "The system cannot find the path specificed." when "cd android" is entered.
- ";C:\Program Files (x86)\Android\android-sdk\platform-tools;C:\Program Files (x86)\Android\android-sdk\tools" is the path
EDIT: Fixed.
1) Moved .img file to root in C:
2) c:
3) cd\
4) fastboot flash recovery recovery.img
Got it finally.

Help, Moto g won't boot up any rom

I unlock the g bootloader got it to root I have the latest cwm recovery been trying different ones also, but some how when I try to install any rom that's out there it won't boot up it only stays on the boot screen . Any ideas

Me too
I have this problem too.

Guys, please search the forum before posting, so your issues would get resolved quickly.
OK, Now towards your problem.
A lot of people are getting the same error and the results from corruptioning of /data. First try factory reset from fastboot, then reboot. If it doesn't help then do a factory reset again and reboot your phone. If doesn't seen to help either then the only option left is to flash stock firmware through PC. Search the forum and you will get the desired result. Beaware that you will end up losing all your apps and SD card data.

forgotter said:
Guys, please search the forum before posting, so your issues would get resolved quickly.
OK, Now towards your problem.
A lot of people are getting the same error and the results from corruptioning of /data. First try factory reset from fastboot, then reboot. If it doesn't help then do a factory reset again and reboot your phone. If doesn't seen to help either then the only option left is to flash stock firmware through PC. Search the forum and you will get the desired result. Beaware that you will end up losing all your apps and SD card data.
Click to expand...
Click to collapse
I have factory reset from fastboot a couple of times also been Goin to stock a few times, been searching everywhere I haven had any luck the phone just been doing the same thing all the time.
I have rooted, install roms, an customized over 20 android devices I have own an never had this problem

chente323 said:
I have factory reset from fastboot a couple of times also been Goin to stock a few times, been searching everywhere I haven had any luck the phone just been doing the same thing all the time.
I have rooted, install roms, an customized over 20 android devices I have own an never had this problem
Click to expand...
Click to collapse
So here's a detailed instruction for you to follow.
1. In fast boot mode connect phone to PC.
2. In CMD (adb) in PC type the command "fastboot devices" without quotes and post the reply to me.
3. In the CMD, type the command "adb erase userdata","adb erase cache" without quotes. (It will wipe all your data and SD card)
4. Now download the firmware (new firmware download it in case there may be issues with the old one you have downloaded) and also TWRP-2.7.0.0.falcon by dhacker. Copy both the files in the adb folder.
5. Rename the twrp-2.7.0.0.falcon.IMG to recovery.img
6. Connect your phone to PC in fastboot mode and flash the recovery by topping command "fastboot flash recovery recovery.img"without quotes.
7. On your phone scroll to recovery option and long press volume up key until the phone vibrates. The phone will boot into recovery.
8. In recovery goto advanced-file manager. And check whether your /datafilleris empty or not (it will be empty)
9. In recovery go to wipe and wipe /system /data /cache. Next reboot your phone to boot loader mode.
10. Flash any firmware from your PC through fastboot. Then reboot your phone.
If it doesn't help either reply to me, there's other workaround too.

forgotter said:
So here's a detailed instruction for you to follow.
1. In fast boot mode connect phone to PC.
2. In CMD (adb) in PC type the command "fastboot devices" without quotes and post the reply to me.
3. In the CMD, type the command "adb erase userdata","adb erase cache" without quotes. (It will wipe all your data and SD card)
4. Now download the firmware (new firmware download it in case there may be issues with the old one you have downloaded) and also TWRP-2.7.0.0.falcon by dhacker. Copy both the files in the adb folder.
5. Rename the twrp-2.7.0.0.falcon.IMG to recovery.img
6. Connect your phone to PC in fastboot mode and flash the recovery by topping command "fastboot flash recovery recovery.img"without quotes.
7. On your phone scroll to recovery option and long press volume up key until the phone vibrates. The phone will boot into recovery.
8. In recovery goto advanced-file manager. And check whether your /datafilleris empty or not (it will be empty)
9. In recovery go to wipe and wipe /system /data /cache. Next reboot your phone to boot loader mode.
10. Flash any firmware from your PC through fastboot. Then reboot your phone.
If it doesn't help either reply to me, there's other workaround too.
Click to expand...
Click to collapse
This is the same thing a friend told me to do we did it had no luck Did it 2 times just in case I dint do it right the first time

Moto g not booting up.
I hope you have an unlocked boot loader.
The first thing you need to find out is that are your phone's partition writable and readable.
1. Download the latest CM11 nightly to your PC rename it to "CM.zip" and extract the contents to adb folder (adb folder should be in C drive i.e. C:/adb ). You will get boot. img , system (folder), and others.
1. connect your phone to PC in fastboot mode.
2.In adb type the below commands one by one without quotes. And let one command get processed before typing other.
"fastboot devices" (in response it must show you something like TJ9*****)
"fastboot erase userdata"
"fastboot erase cache"
"fastboot push C:/adb\system /system/"
"fastboot flash boot boot.img"
"fastboot flash recovery recovery.img"(flash the philz recovery now)
"fastboot push C:/adb\boot.img /data/"(to verify whether /data is writable or not)
"fastboot push C:/adb\boot.img /cache/"(to verify whether /cache is writable or not)
"fastboot push C:/adb\CM.zip /data/media/0/"(to push the CM11rom to sdcard to flash it through recovery)
Then boot your phone to recovery. And see the logs, it should show
/system mounted
/data mounted
/sd-ext error mounting /sd-ext
/cache mounted
If it shows /data can't be mounted or error mounting /data. Then go to wipe and wipe /data and /sdcard and then again push CM.zip to /data/media/0/. If you don't see this error, then choose to wipe to install a new rom. After this remount /system /data /cache and flash the CM11.zip or you can flash stock firmware through mfastboot.
This method will definitely work since I, myself had this very same issue and got it resolved the very same way.
P.S. Try this method and only of you get some error then reply as I an sure it will solve your issue.

forgotter said:
I hope you have an unlocked boot loader and have TWRP(2.7 by dhacker) installed.
The first thing you need to find out is that are your phone's partition writable and readable.
1. Download the latest CM11 nightly to your PC and extract the contents to adb folder. You will get boot. img , system (folder), and others.
1. connect your phone to PC in fastboot mode.
2.In adb type the below commands one by one without quotes. And let one command get processed before typing other.
"fastboot devices" (in response it must show you something like TJ9*****)
"fastboot erase userdata"
"fastboot erase cache"
"fastboot push system /system"
"fastboot flash boot boot. img"
"fastboot flash recovery recovery.img"(flash the philz recovery now)
"fastboot push boot.img /data"(to verify whether /data is writable or not)
"fastboot push boot. img /cache"(to verify whether /cache is writable or not)
"fastboot push CM.zip /data/media/0/"(to push the CM11rom to sdcard to flag it through recovery)
Then boot your phone to recovery. And see the logs, it should show
/system mounted
/data mounted
/sd-ext error mounting /sd-ext
/cache mounted
If it shows /data can't be mounted or error mounting /data.Then go to wipe and wipe /data and /sdcard. If you don't see this error, then chose to wipe to install a new rom. After this remount /system /data /cache and flash the CM11. zip.
This method will definitely work since I, myself had this very same issue and got it resolved the very same way.
P.S. Try this method and only of you get some error then reply as I an sure it will solve your issue.
Click to expand...
Click to collapse
Thanks I will give it a try tomorrow since it's wife phone I don't have it w me now. I'll get back at u let u know if it work

forgotter said:
So here's a detailed instruction for you to follow.
1. In fast boot mode connect phone to PC.
2. In CMD (adb) in PC type the command "fastboot devices" without quotes and post the reply to me.
3. In the CMD, type the command "adb erase userdata","adb erase cache" without quotes. (It will wipe all your data and SD card)
4. Now download the firmware (new firmware download it in case there may be issues with the old one you have downloaded) and also TWRP-2.7.0.0.falcon by dhacker. Copy both the files in the adb folder.
5. Rename the twrp-2.7.0.0.falcon.IMG to recovery.img
6. Connect your phone to PC in fastboot mode and flash the recovery by topping command "fastboot flash recovery recovery.img"without quotes.
7. On your phone scroll to recovery option and long press volume up key until the phone vibrates. The phone will boot into recovery.
8. In recovery goto advanced-file manager. And check whether your /datafilleris empty or not (it will be empty)
9. In recovery go to wipe and wipe /system /data /cache. Next reboot your phone to boot loader mode.
10. Flash any firmware from your PC through fastboot. Then reboot your phone.
If it doesn't help either reply to me, there's other workaround too.
Click to expand...
Click to collapse
Hi forgotter! I have the same problem... won't boot with any ROM. I've followed your instructions but stil stucked on the boot logo. I will try the second method you provided now, hope that works :crying:

@notnowjohn
Didn't know why first method didn't worked for you but the second one would definitely work. If you get any error then reply to me, and yes in my second method post by mistake there are some extra space added after full stop (.) e.g. in boot. img (it is boot.img ) do please avoid that.

forgotter said:
I hope you have an unlocked boot loader and have TWRP(2.7 by dhacker) installed.
The first thing you need to find out is that are your phone's partition writable and readable.
1. Download the latest CM11 nightly to your PC and extract the contents to adb folder. You will get boot. img , system (folder), and others.
1. connect your phone to PC in fastboot mode.
2.In adb type the below commands one by one without quotes. And let one command get processed before typing other.
"fastboot devices" (in response it must show you something like TJ9*****)
"fastboot erase userdata"
"fastboot erase cache"
"fastboot push system /system"
"fastboot flash boot boot. img"
"fastboot flash recovery recovery.img"(flash the philz recovery now)
"fastboot push boot.img /data"(to verify whether /data is writable or not)
"fastboot push boot. img /cache"(to verify whether /cache is writable or not)
"fastboot push CM.zip /data/media/0/"(to push the CM11rom to sdcard to flag it through recovery)
Then boot your phone to recovery. And see the logs, it should show
/system mounted
/data mounted
/sd-ext error mounting /sd-ext
/cache mounted
If it shows /data can't be mounted or error mounting /data.Then go to wipe and wipe /data and /sdcard. If you don't see this error, then chose to wipe to install a new rom. After this remount /system /data /cache and flash the CM11. zip.
This method will definitely work since I, myself had this very same issue and got it resolved the very same way.
P.S. Try this method and only of you get some error then reply as I an sure it will solve your issue.
Click to expand...
Click to collapse
Hi again Sir, I've followed all the instructions, but when I check the logs it says "Can't Mount" of "Can´t open" for everything.
This is what i saw during the proccess
"fastboot devices" (in response it must show you something like TJ9*****) T08830R89M
"fastboot erase userdata" OK
"fastboot erase cache" OK
"fastboot push system /system" Doesnt do anything, show adb commands
"fastboot flash boot boot. img" I deleted the space between . img. Phone says Mismatched partition size (boot)
"fastboot flash recovery recovery.img"(flash the philz recovery now) Phone says Mismatched partition size (Recovery)
"fastboot push boot.img /data"(to verify whether /data is writable or not) Doesnt do anything, show adb commands
"fastboot push boot. img /cache"(to verify whether /cache is writable or not). Again deleted the space between . img. Doesnt do anything, show adb commands
"fastboot push CM.zip /data/media/0/"(to push the CM11rom to sdcard to flag it through recovery) Doesnt do anything, show adb commands
Its anthing more I can do??
Thank you very much! I can believe I brick my phone

notnowjohn said:
Hi again Sir, I've followed all the instructions, but when I check the logs it says "Can't Mount" of "Can´t open" for everything.
This is what i saw during the proccess
"fastboot devices" (in response it must show you something like TJ9*****) T08830R89M
"fastboot erase userdata" OK
"fastboot erase cache" OK
"fastboot push system /system" Doesnt do anything, show adb commands
"fastboot flash boot boot. img" I deleted the space between . img. Phone says Mismatched partition size (boot)
"fastboot flash recovery recovery.img"(flash the philz recovery now) Phone says Mismatched partition size (Recovery)
"fastboot push boot.img /data"(to verify whether /data is writable or not) Doesnt do anything, show adb commands
"fastboot push boot. img /cache"(to verify whether /cache is writable or not). Again deleted the space between . img. Doesnt do anything, show adb commands
"fastboot push CM.zip /data/media/0/"(to push the CM11rom to sdcard to flag it through recovery) Doesnt do anything, show adb commands
Its anthing more I can do??
Thank you very much! I can believe I brick my phone
Click to expand...
Click to collapse
Don't worry your phone is fine.
Whenever adb shows m mismatched partition it's fine and usual.
I understand your problem now, I just think if I your device now , I would have repaired it within minutes. Never mind, follow the below steps .
Download the philz recovery to your PC, flash it through fastboot on your phone. Then go to recovery on your phone immediately and choose wipe-wipe data and sdcard. And then flash the stock firmware through mfastboot or install any ROM through recovery.

Anyone report which step what must i do to solve this prob

sinkadorable said:
Anyone report which step what must i do to solve this prob
Click to expand...
Click to collapse
Read post #7 on page 1.

I cant push system to device. What tools must be i have?

If you can't push system to device don't worry , it's of no use at all because you'll format it before flashing the rom. But if you're flashing through recovery then make sure to push CM. zip to /sdcard/.
You need adb tools on your PC, just search Google for adb tools and download it. You need stock firmware of your phone on PC if you'd flash the rom through mfastboot and you need philz recovery ( to flash it on your phone.)
If you can't get anything or don't understand anything then do search the forum for help because all the things are already mentioned and if i had to answer it mostly would be copy-paste. But still if you need help, I am there. Just post your problem.

pluiz halp!
forgotter said:
If you can't push system to device don't worry , it's of no use at all because you'll format it before flashing the rom. But if you're flashing through recovery then make sure to push CM. zip to /sdcard/.
You need adb tools on your PC, just search Google for adb tools and download it. You need stock firmware of your phone on PC if you'd flash the rom through mfastboot and you need philz recovery ( to flash it on your phone.)
If you can't get anything or don't understand anything then do search the forum for help because all the things are already mentioned and if i had to answer it mostly would be copy-paste. But still if you need help, I am there. Just post your problem.
Click to expand...
Click to collapse
I'm having similar issues as everyone else here. I unlocked my bootloader following Motorola's instructions on their website, then I used Superboot to root the phone (which I don't think worked as CWM and TWRP kept asking to install SU on reboot). After that I put CM 11 M4 on sdcard and flashed.
This is where it went wrong. I rebooted and got a bootloop, so I looked around online and ended up wiping everything and trying again. It still didn't work so I followed instructions to reflash stock firmware, this didn't work either. By this time the phone had been on ages and went dead. Now it won't turn back on and won't register as charging from USB or from wall plug.
I have no idea what to do as nothing worked before hand and now I can't access it to resolve the issue.
I'm panicking atm because I'm contracted to Virgin Mobile in the UK and this voids the warranty. I just don't know what to do D:

jamiethomaswhite said:
I'm having similar issues as everyone else here. I unlocked my bootloader following Motorola's instructions on their website, then I used Superboot to root the phone (which I don't think worked as CWM and TWRP kept asking to install SU on reboot). After that I put CM 11 M4 on sdcard and flashed.
This is where it went wrong. I rebooted and got a bootloop, so I looked around online and ended up wiping everything and trying again. It still didn't work so I followed instructions to reflash stock firmware, this didn't work either. By this time the phone had been on ages and went dead. Now it won't turn back on and won't register as charging from USB or from wall plug.
I have no idea what to do as nothing worked before hand and now I can't access it to resolve the issue.
I'm panicking atm because I'm contracted to Virgin Mobile in the UK and this voids the warranty. I just don't know what to do D:
Click to expand...
Click to collapse
Plug the phone to wall charger and leave it to charge for the whole night, the next when you'd restart the phone it should boot up. Sometimes the phone discharged itself to such a level that it didn't have enough juice left to show the battery charging status even.
After that follow instructions from post #7 on page 1 and paste all output commands you see. Well, the phone should boot up.

forgotter said:
If you can't push system to device don't worry , it's of no use at all because you'll format it before flashing the rom. But if you're flashing through recovery then make sure to push CM. zip to /sdcard/.
You need adb tools on your PC, just search Google for adb tools and download it. You need stock firmware of your phone on PC if you'd flash the rom through mfastboot and you need philz recovery ( to flash it on your phone.)
If you can't get anything or don't understand anything then do search the forum for help because all the things are already mentioned and if i had to answer it mostly would be copy-paste. But still if you need help, I am there. Just post your problem.
Click to expand...
Click to collapse
now my phone was stuck on UBL warning message and cannot enter recovery
when i flash recovery fastboot say Mismatched partition size (Recovery) :crying:

sinkadorable said:
now my phone was stuck on UBL warning message and cannot enter recovery
when i flash recovery fastboot say Mismatched partition size (Recovery) :crying:
Click to expand...
Click to collapse
Mismatched partition size is usual , no need to worry about that. What do you mean by UBL warning message? And yes, after you flash recovery, enter in recovery mode and wipe data and sdcard and then flash any ROM from fastboot.
And if you get into an error or solution doesn't work then post your problem but detailed so I can get to the main cause of the problem.

Problem [BOOTLOADER]

Describing my problem :
Since yesterday my OPO did some random reboots. I was running Paranoid Android and it worked perfectly...
Yesterdayevening after it rebooted another time, my OPO didn't start at all... It seems that my bootloader won't load the OS.
This morning, I did a complete wipe and I've put the stock ROM from the CM site back on my OPO ( XNPH33R signed boot).
-Fastboot works
-Recovery works
-Bootloader won't load OS. ( only the One Plus logo pops up (not the bootanimation)). After that it reboots over and over...
Update 1 17:30 5/10/2014 :
I'm in a bootloop, I have no ROM. I have the TWRP recovery. And the bootloader is LOCKED.
So I tried to unlock the bootloader with the toolkit for the OnePlus one. ( I tried it also manually with cmd).
----WHAT IT DOES in CMD/ Phone-------
In CMD : " OKAY [0.012 s]
Finished. total time : 0.012 s
OPO : It opens up my TWRP recovery but it does not unlock the bootloader
Update 2 19:52 5/10/2014 :
I've been able to unlock the bootloader...
with the command " fastboot oem device-info" , I received :
Bootloader tampered : True
Bootloader unlocked : False ( because the toolkit only did " fastboot oem unlock " , I did an adb sideload with a zip "OnePlusOne-OnlyBootloaderToggle" from the thread
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912. Now my bootloader is back UNLOCKED.
I hope the bootloop will stop when I do a factory / reset.
10:40 6/10/2014 :
I tried several times to flash stock roms from the official site / from the forum. None of them 'work'.
Can someone please help me?? He still bootloops!!! How frustrating thazt is,I tried everything from threads on the forum. Nobody is ansering my thread. Any reason for that ?

My suggestion is this: grab one of the recovery flashable versions of CM11S from here, boot into your TWRP recovery and use adb to push the ROM zip to your phone, then use the install function in TWRP to flash it.
To push the zip to your phone you first need to put it in your adb/fastboot folder (wherever you have adb.exe and fastboot.exe located on your PC), make sure your phone is booted into TWRP and connected to your PC, open a command prompt from within your adb/fastboot folder (shift + right click anywhere in the folder, then select open command prompt here), and issue this command:
Code:
adb push <name of file.zip> /sdcard/
*Please note the '<' and '>' symbols are not included in the command.
From there just flash the ROM like you would flash any other ROM.
Transmitted via Bacon

Failure with E:
timmaaa said:
My suggestion is this: grab one of the recovery flashable versions of CM11S from here, boot into your TWRP recovery and use adb to push the ROM zip to your phone, then use the install function in TWRP to flash it.
To push the zip to your phone you first need to put it in your adb/fastboot folder (wherever you have adb.exe and fastboot.exe located on your PC), make sure your phone is booted into TWRP and connected to your PC, open a command prompt from within your adb/fastboot folder (shift + right click anywhere in the folder, then select open command prompt here), and issue this command:
Code:
adb push <name of file.zip> /sdcard/
*Please note the '<' and '>' symbols are not included in the command.
Transmitted via Bacon
Click to expand...
Click to collapse
Pushing the zip into sdcard :good:
Installing the zip gives a message about E:
example :
something with E: path
E: unable to wipe
E: error executing updater binary in zip 'sdcard/cm11.0... .zip
Proberly more

Are you sure you're attempting to flash one of the recovery flashable zips? What's the full filename?
Transmitted via Bacon

timmaaa said:
Are you sure you're attempting to flash one of the recovery flashable zips? What's the full filename?
Transmitted via Bacon
Click to expand...
Click to collapse
cm-11.0-XNPH33R-bacon-signed
Links
1. Recovery flashable zips of the complete ROMz:
XNPH22R
XNPH25R
XNPH33R
From your link
EDIT-----
1. I had flashed the stock recovery back.
2. Did a factory reset
3. Wiped cache
4. Wiped media
5. Flashed TWRP back
6. ADB push zip in /sdcard/
7. Flashed the zip SUCCESSFUL after these steps
I still have a bootloop

Have you tried to format your internal sd card and flash your zip. Remember if you format though you will lose everything on your sdcard. Make sure you backup everything first if you want to try this. Also if you do this you will have to push your zip back to the phone

Who can even solve this?...
playya said:
Have you tried to format your internal sd card and flash your zip. Remember if you format though you will lose everything on your sdcard. Make sure you backup everything first if you want to try this. Also if you do this you will have to push your zip back to the phone
Click to expand...
Click to collapse
My internal storage was already formatted. I just have the TWRP and the zip on my phone.
[Q] In the TWRP recovery menu in 'Advanced' what has to be between Copy Log to SD and Terminal Command? There is a blank spot ,there should be button normally?
How is it even possible i have nothing but the recovery and the zip and I still got a bootloop...
Is there somebody that knows something else that i can try?
Is it possible to flash perhaps with odin?

VictorByttebier said:
My internal storage was already formatted. I just have the TWRP and the zip on my phone.
[Q] In the TWRP recovery menu in 'Advanced' what has to be between Copy Log to SD and Terminal Command? There is a blank spot ,there should be button normally?
How is it even possible i have nothing but the recovery and the zip and I still got a bootloop...
Is there somebody that knows something else that i can try?
Is it possible to flash perhaps with odin?
Click to expand...
Click to collapse
definitely not odin thats Samsung my friend. Partition SD Card is whats missing in TWRP for you. I asked about formatting internal because a similar thing happened to my friend. We had to format internal then adb push recovery and rom and all was well again. If you have tried this recently then my bad but if you have not it wont hurt to try it again in that order
format internal
adb push recovery
adb push rom
reboot
Take a look in here as well http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061

Bootloop fixed
It finally worked!!! How weird that i already found a zip like on the thread but with XNPH33R and also with the persist and recovery.img and flash-all etc... but it didn't work.
Now i just have to update from the settings
At beginning I was convinced that a bootloop could be fixed with factory/reset would do it. Like it always worked on my previous smartphone.
Thank you playya and timmaaa for the responses!:good: You are awesome! See me sitting here with a

Verizon HTC One (M8) Cheat Sheet...

Below is a cheat sheet I've made to help others keep the commands they'll need and general information organized and consolidated in one place... When I first started using Android years ago I kept one of these so I could refer to it if I forgot a command or a small piece of info and I thought I'd share one for the m8.
Make sure to check out the note at the end of this post regarding Dottat's updated ADB files. They prevent the need to flash ruu's twice as you'll see outlined in this post.
Edit Note:​I highly recommend running ruu's via adb. It may look more intimidating than the exe or hboot methods,
but if they were to fail you'd see exactly where it failed in the running log. You can avoid having to wait
for an initial boot of the stock rom if your intentions are to wipe to stock and then install a custom
recovery and whatever your rom/rom(s) of choice are. I personally wipe my phone from recovery, then
wipe via the adb commands below, run the ruu, and then factory reset from stock recovery. I'll then
install a custom recovery and my rom of choice. It's up to you, but I've found this to be the quickest
method of insuring a full-wipe to stock and then into my rom of choice. The wiping above is redundant
and not necessary, but I'll do it if I've got a problem I simply cannot figure out. To be honest the ruu should
wipe everything for you and then running a factory reset w/stock recovery installed should fix any
4g/LTE issues. ​***Verizon ADB Information***
--MOST but NOT ALL of this is Universal (Not Carrier Dependent)--
All commands beginning with "fastboot" must be performed at Bootloader
All commands beginning with ADB are performed from a phone that is in Rom
-You may skip the "adb reboot bootloader" step if you're already
at the bootloader
Firmware/RUU/Recovery instructions are available in their specific threads
*This is just a cheat sheet*
Basic ADB Commands:​
Recovery Flashing: (TWRP Current Standard)
adb reboot bootloader
fastboot flash recovery recoveryimgname.img
Firmware Flashing:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip firmwarename.zip
*you should be prompted to flash a second time here*
fastboot flash zip firmwarename.zip
fastboot reboot-bootloader
HBoot Flashing:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip hbootfilename.zip
RUU Commands​
Wipe By ADB:*optional*(though a wipe is recommended either by recovery or adb)
adb reboot bootloader
fastboot oem task 28
fastboot oem task 29
Install RUU via ADB:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip 0P6BIMG.zip
Install RUU via HBoot:
Rename ruu .zip to 0P6BIMG.zip and copy to root of external sdcard
Boot to your bootloader and enter hboot if you're in fastboot mode
Hboot should automatically read the RUU file and begin unpacking (progress bar at top right)
Follow onscreen prompts after it unpacks...
*sdcard must be formatted to fat32 to read RUU* formatting the sdcard through the android os
will accomplish this. It will mount vfat when you read it by computer or in twrp this is okay.
SELinux Terminal Commands:​
1) Grant su level permissions via terminal by typing "su"
2) Enable SELinux status by typing "setenforce x" where x is the variable below
setenforce 0 =Permissive
setenforce 1 =Enforcing
GPE Install Instructions:​
Begin with SuperCID:***May no longer be necessary***
1) Get current cid information via;
fastboot oem readcid
Write down your current cid reading
2) Change your cid to 11111111 via;
fastboot oem writecid 11111111
(check cid again with fastboot oem readcid to varify)
3) Reboot to the bootloader
4) Following the reboot back to the bootloader
verify your cid is 11111111
And Then Install Rom Via:
5)Wipe /data; /cache; /system; Dalvik
6)Format /system; /data; /cache to f2fs -optional *Must use Elite Kernel for GPE 5.1*
7)Install Rom
8)Reboot
Remove GPE:***these are just my recommendations***
1) Revert CID via fastboot oem writecid (your stock cid ex: fastboot oem writecid VZW__001
2) Wipe everything /data, /cache, /system, /dalvik
Click Here for dottat's firmware and ruu master collection
Below, on this first page, dottat has linked a file containing updated adb files to be used when installing his ruu's. They correct the issues many have had requiring two flashes of his ruu's. Full information available through his posts in this thread. You can either replace the files in his .zip with your current adb folders files, or use it (after unzipping) as an updated lightweight adb interface folder.

jcole20 said:
Below is a cheat sheet I've made to help others keep the commands they'll need and general information organized and consolidated in one place... When I first started using Android years ago I kept one of these so I could refer to it if I forgot a command or a small piece of info and I thought I'd share one for the m8.
***Verizon ADB Information***
--MOST but NOT ALL of this is Universal (Not Carrier Dependent)--
All commands beginning with "fastboot" must be performed at Bootloader
All commands beginning with ADB are performed from a phone that is in Rom
-You may skip the "adb reboot bootloader" step if you're already
at the bootloader
Firmware/RUU/Recovery instructions are available in their specific threads
*This is just a cheat sheet*
Basic ADB Commands:​
Recovery Flashing: (TWRP Current Standard)
adb reboot bootloader
fastboot flash recovery recoveryimgname.img
Firmware Flashing:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip firmwarename.zip
*you should be prompted to flash a second time here*
fastboot flash zip firmwarename.zip
fastboot reboot-bootloader
HBoot Flashing:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip hbootfilename.zip
RUU Commands​
Wipe By ADB:*optional*
adb reboot bootloader
fastboot oem task 28
fastboot oem task 29
Install RUU via ADB:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip 0P6BIMG.zip
Install RUU via HBoot:
Rename ruu .zip to 0P6BIMG.zip and copy to root of external sdcard
Boot to your bootloader and enter hboot if you're in fastboot mode
Hboot should automatically read the RUU file and begin unpacking (progress bar at top right)
Follow onscreen prompts after it unpacks...
*sdcard must be formatted to fat32 to read RUU* formatting the sdcard through the android os
will accomplish this. It will mount vfat when you read it by computer or in twrp this is okay.
SELinux Terminal Commands:​
1) Grant su level permissions via terminal by typing "su"
2) Enable SELinux status by typing "setenforce x" where x is the variable below
setenforce 0 =Permissive
setenforce 1 =Enforcing
GPE Install Instructions:​
Begin with SuperCID:***May no longer be necessary***
1) Get current cid information via;
fastboot oem readcid
Write down your current cid reading
2) Change your cid to 11111111 via;
fastboot oem writecid 11111111
(check cid again with fastboot oem readcid to varify)
3) Reboot to the bootloader
4) Following the reboot back to the bootloader
verify your cid is 11111111
And Then Install Rom Via:
5)Wipe /data; /cache; /system; Dalvik
6)Format /system; /data; /cache to f2fs -optional *Must use Elite Kernel for GPE 5.1*
7)Install Rom
8)Reboot
Remove GPE:***these are just my recommendations***
1) Revert CID via fastboot oem writecid (your stock cid ex: fastboot oem writecid VZW__001
2) Wipe everything /data, /cache, /system, /dalvik <-- Optional
*(suggested to use oem task commands)*
3) Format back to ext4 for everything if you changed to f2fs for any reason
4) Run ruu
If ruu doesn't work properly...
5) Run ruu a second time
Some General Tips​
-When typing a command like "fastboot flash recovery recoveryname.img" you can use the TAB key to
autocomplete a name or file directory... (This is true in just about every operating systems
command line or terminal interface) ex: if trying to go to C:\Windows and you're already in the
C:\ directory you simply need type "cd C:\w" and hit TAB and it should automatically complete the
field. If you happen to have a directory that comes before Windows alphabetically like "C:\Warez"
(not likely) hit Tab again and it will cycle through directories alphabetically.
Another example is I have twrp-2.8.5 and twrp-2.8.6 in my adb directory. So if it autocompletes
to "twrp-2.8.5.img", I hit tab again it will change to "twrp-2.8.6.img". In some instances you can
use this autocomplete feature to issue commands ie when using an apk decompiler/recompiler tool.
Instead of typing mkdir you can simply autotab to the correct command after typing "m" or "mk" etc.
-If you use the up arrow on your keyboard in Terminal/Command Prompt it will cycle through previous commands.
Example: When flashing firmware after "fastboot flash zip firmware.zip" when prompted to flash a second time you
can just hit UP Arrow on your keyboard and it will automatically go to your previous entry.
-I keep the latest RUU for my device in my adb/android studio (*/platform-tools) directory already
named "0P6BIMG.zip". This is a good practice simply because it streamlines the whole process so you
don't have to wait as a rather large file copies to said directory. I also keep a copy of said RUU
in a folder on my external sd-card. I do this so that if my computer, for whatever reason, was not
able to read the phones storage I can use the file manager in recovery to move it to root and RUU.
-If you have TiTanium Backup Pro you can set it to automatically update your apps. I like to keep an
updated copy of my apps on my external sd-card, my computer, and in cloud via GoogleDrive. This
makes restoring apps from a backup a painless process as I always have them available to me.
-I also keep a running backup of everything important to me on my computer. I have a folder
I've set up specifically for my running backups. Inside said folder I have a copy of my favorite
roms, my music, all the firmware for our device, the HBoot.zip(s), my pictures, all available RUUs,
an MD5 checking program, GApps packages, TWRP backups, TWRP .img(s), TWRP themes, and any other
tweaks/flashable.zips I find important. I highly suggest everyone who doesn't do this make this a
practice. It truly helps a lot.
EDIT: If someone wants me to upload the above as a .txt file I will.
Click to expand...
Click to collapse
That would be great in .txt format.

aaronpw0621 said:
That would be great in .txt format.
Click to expand...
Click to collapse
When I get home (about an hour) I'll upload a .txt of the commands.
HTC One (M8) CM12.1.1
Edit: Okay downloadable .txt file is in OP

jcole20 said:
When I get home (about an hour) I'll upload a .txt of the commands.
HTC One (M8) CM12.1.1
Edit: Okay downloadable .txt file is in OP
Click to expand...
Click to collapse
:good: :good:

@jcole20 a lot of your fastboot reflashing can be removed by the use of the HTC_fastboot I have posted in various places. It does it automatically

dottat said:
@jcole20 a lot of your fastboot reflashing can be removed by the use of the HTC_fastboot I have posted in various places. It does it automatically
Click to expand...
Click to collapse
Thanks @dottat I didn't know. I've only had to reflash once. And that was the first time I ran your ruu (5.0.1). Following that initial hiccup, everytime after it's completed successfully on the first try.
I'll check into that and note it in op. I just wanted to consolidate all the commands we commonly use for people who have trouble remembering them.
HTC One (M8) CM12.1.1
Edit: oh I didn't know you were talking about your ruu.exe(s) ... Yeah, I'm so used to using adb for everything. I've got your exe for lollipop but I've only run it once. (Prior to my pm about something lingering after a ruu) ... I still haven't figured that out BTW. I'll make note in the op that your exes make the ruu adb info obsolete. Thank you again for all your help and work.

jcole20 said:
Thanks @dottat I didn't know. I've only had to reflash once. And that was the first time I ran your ruu (5.0.1). Following that initial hiccup, everytime after it's completed successfully on the first try.
I'll check into that and note it in op. I just wanted to consolidate all the commands we commonly use for people who have trouble remembering them.
HTC One (M8) CM12.1.1
Edit: oh I didn't know you were talking about your ruu.exe(s) ... Yeah, I'm so used to using adb for everything. I've got your exe for lollipop but I've only run it once. (Prior to my pm about something lingering after a ruu) ... I still haven't figured that out BTW. I'll make note in the op that your exes make the ruu adb info obsolete. Thank you again for all your help and work.
Click to expand...
Click to collapse
No that's not what I am talking about. Lol
Download this. Unzip it and you will see what I mean
https://www.androidfilehost.com/?fid=95916177934554784

dottat said:
No that's not what I am talking about. Lol
Download this. Unzip it and you will see what I mean
https://www.androidfilehost.com/?fid=95916177934554784
Click to expand...
Click to collapse
Lol... okay. Why isn't this in your 5.0.1 ruu thread? I wish I had known about this a couple of weeks ago... Thanks though. I did a quick google search for htc_fastboot and what came up was a question you asked someone in one of your ruu threads. I went to the op and all I saw was the exe and ruu.zip so I assumed you were talking about the .exe. Hah

jcole20 said:
Lol... okay. Why isn't this in your 5.0.1 ruu thread? I wish I had known about this a couple of weeks ago... Thanks though. I did a quick google search for htc_fastboot and what came up was a question you asked someone in one of your ruu threads. I went to the op and all I saw was the exe and ruu.zip so I assumed you were talking about the .exe. Hah
Click to expand...
Click to collapse
Have you read the stickied thread in general section?

dottat said:
Have you read the stickied thread in general section?
Click to expand...
Click to collapse
To be honest dottat, I've read so much with regards to this phone in the last month since I got it I don't remember everything that I've read through. I think, with regards to your ruu's, I've mainly used your posted threads in the Verizon Android Development section. I linked your ruu's in the OP now and I used the stickied master list here, but I've only had this phone for a month so I never needed a 4.4.4 ruu (hence not needing to find that master list). Your lollipop ruu has been bumped somewhat regularly so it's the only one I've ever really looked through except when googling something and your 4.4.4 ruu in the same section has come up.

jcole20 said:
To be honest dottat, I've read so much with regards to this phone in the last month since I got it I don't remember everything that I've read through. I think, with regards to your ruu's, I've mainly used your posted threads in the Verizon Android Development section. I linked your ruu's in the OP now and I used the stickied master list here, but I've only had this phone for a month so I never needed a 4.4.4 ruu (hence not needing to find that master list). Your lollipop ruu has been bumped somewhat regularly so it's the only one I've ever really looked through except when googling something and your 4.4.4 ruu in the same section has come up.
Click to expand...
Click to collapse
Here's the post....
http://forum.xda-developers.com/showthread.php?p=56890497
I just gave you the latest and greatest above. Its the awesome sauce man.

dottat said:
Here's the post....
http://forum.xda-developers.com/showthread.php?p=56890497
I just gave you the latest and greatest above. Its the awesome sauce man.
Click to expand...
Click to collapse
Thank you! Heh, I've got the .exes and .zips of your 4.4.4 and 5.0.1 ruus saved. I will probably ruu back to stock again using the above just because... I've still never figured out what broke audiofx for me even after reverting to stock via your ruus. It's been driving me nuts.
HTC One (M8) CM12.1.1
Edit: I'm thinking I flashed V4A via a .zip and didn't realize it, so audiofx wasn't working, it was working as the drivers for audiofx and audiofx was working as the gui for v4a. That's the only explanation I can think of, because your ruu's have been great and I know they are working to revert me completely to stock.
Edit 2: I went ahead and ran a ruu with your updated adb file(s). As usual went off without a hitch and everything seems perfect... booting into my rom of choice now. As usual everything is perfect dottat... thanks!

adb and fastboot

Hello, i want to reactivate my old acer A701 by flashing a newer img or zip.I have the following problems.When I try to do the recovery with a zip file on an sdcard i get the prop error.When i try to flash it by an img i always get i haven set the ANDROID_PRODUCT_OUT even when I do an export ANDROID_PRODUCT_OUT=/home/leopold/platform-tools.
A printenv shows the ANDROID_Product_OUT and the img is in platform-tools.
What is going wrong, what can i do?

You either apply Flash zip from sd from within Android's Recovery menu or you use external ADB Sideload command to flash a properly signed ZIP-file what contains the ROM, or you use external Fastboot Flash command to flash an IMG-file what requires device's bootloader is unlocked.

Hello and thank you,
like i wrote above, i want to flash it.Now i found at another place i have to write:
sudo ANDROID_PRODUCT_OUT="./" fastboot flashall recovery Az.img
when i do that, the flash is starting but then i get the error android-info.txt is missing.
So i guess i have a wrong image.
Does anybody have an image for the A701 with a newer android version.Or can give me a link.
My 4.1.1 does not recognice newer apps.
leopold

Take note that
Code:
fastboot flashall <ROM.IMG>
is to be used to flash a complete ROM, whereas
Code:
fastboot flash recovery <RECOVERY.IMG>
is to be used to flash only a Recovery.

Ok, i understand but i m lost.
I have some imagees and some zip files what should work on my a701.
If I use fastboot with img, i get no android-txt found.
if I work with adb reboot recovery and the zip files I will allways get the partition error prop undefined.
Can I supress the search for the android -txt?
What else can I do?
one of the zip files is from here https://acer.shreps.fr/, it is the said stable kitkat.

If you have access to a Windows computer then make use of a Flash Tool what's suitable to the tablet.

Unfortunately i can not find a flashtool for the nividia tegra3.
I have some zip files what should work on the a701 but all have the error check partition size [-Prop_UNDEFINED-) then the installation will be aborted.
Is there a way to eliminate the partition check.
Or does somebody have a zip or an img with a working update or recovery for a recent Android working on the a701?