Database Info

Recovery problems

I had a couple problems so i unrooted then rerooted then i kept trying to flash recovery 1.6.2 but it kept comming up with file not found on the sdcard so i put the file in the tools folder and used android commander. It came up with 2 # then the screen went blank and it sat there so after a few minutes i did a battery pull and now i cant boot into recovery. It just sits at the boot screen.

xxwckdxx said:
I had a couple problems so i unrooted then rerooted then i kept trying to flash recovery 1.6.2 but it kept comming up with file not found on the sdcard so i put the file in the tools folder and used android commander. It came up with 2 # then the screen went blank and it sat there so after a few minutes i did a battery pull and now i cant boot into recovery. It just sits at the boot screen.
Click to expand...
Click to collapse
how long has it sat there? sometimes you have to give it a few minutes after going thru all that.

By the way if i dont try to boot into recovery it loads fine how can i reload the reocvery?

Probably 5 minutes and no go

How were you loading it in the first place? Have you checked to see if its on your card? When pushing the image, are you using the exact image name, i.e, v1.6.2-(color).img.? Also, are you holding the end-home keys at the same time long enough to see it come up?

when i first was trying i opened the terminal i had on the phone and typed flash_image recovery /sdcard/recovery-1.6.2.img and it kept comming up with bad filename(wwhich i had renamed the file to that so i dont know why) then i put it in the tools folder and tried the same from commander and it got me to here ;\

What method are you using? Try amon ras or the method used to push it to your card thru root.

havent heard of amon ras.....i just pushed it to the sdcard again and tried the same command and end up with the same thing iam trying to unroot again

nope came up with bootloader error for the unroot

tried using kitchen to reroot but it comes up with errors

Okay, these are Amon RAs methods just depending on what your using:
Install
There are several ways to install a custom recovery, choose the one that suits you most (I probably forgot a few).
via adb -> Requires a custom recovery (with test-keys)
Code:
Copy recovery-RA-heroc-v1.6.2.img to the root of your sdcard
Boot into your current custom recovery (boot while holding HOME)
Connect your Hero via usb to your pc/mac/...
adb shell
$su (not required if you have root already)
#mount -a
#flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.imgvia fastboot + adb -> In case you don't have a custom recovery, so when you get signature fail errors
Code:
adb shell reboot bootloader
fastboot boot recovery-RA-heroc-v1.6.2.img
adb shell mount /sdcard
adb push recovery-RA-heroc-v1.6.2.img /sdcard/recovery-RA-heroc-v1.6.2.img
adb shell flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.img
adb shell reboot
Or thru adb try this:
cd C:\android-sdk-windows\tools
adb shell
adb push recovery-RA-heroc-v<name>/sdcard
adb shell reboot
adb push recovery-RA-heroc-v1.5.2.img /sdcard
Pushing is equivalent of copy the file to the root of your sdcard. By the time you finished reading this it should be done. You'll know its done because the ouput will say something like transferred X bytes in X secs.
adb shell reboot
This will cause the phone to restart automatically. Wait till it is fully booted to continue.
adb shell
su
cd /sdcard/
flash_image recovery recovery-RA-heroc-v1.5.2.img
FLASHING TO THE RECOVERY TAKES SEVERAL SECONDS-- BE PATIENT. ENTER THE NEXT COMMAND ONLY AFTER THE COMMAND PROMPT RETURNS TO THE # (ROOT SYMBOL).
reboot recovery
This was complements of theresthatguy's method. Hope this helps.

to tell you the truth 1.6.2 is basically the same as 1.5.2 the only diff is the power off option and the carebear color so if you have 1.5.2 you should just keep it since you are having trouble installing it

VoLoDaR1 said:
to tell you the truth 1.6.2 is basically the same as 1.5.2 the only diff is the power off option and the carebear color so if you have 1.5.2 you should just keep it since you are having trouble installing it
Click to expand...
Click to collapse
I had 1.2.3 or whatever it was thats why i was gonna just shoot to 1.6.2 i had done it before but i dont know what happened this time. I tried the way thru adb and it has been sitting so far 10 minutes and it is still sitting at the boot screen

The first one wont work i cant get into recovery.....the second one i get "fastboot is not recognized as a internal command"and the third is the one i have been trying....

im not sure man i had trouble flashing it also try renameing it to something simple like 1.6.2.img and go to better terminal emulator type in su enter than type in the comands to flash it
flash_image /sdcard/1.6.2.img enter
do not enter mount-a before this this was the problem i was having after you hit enter just type in reboot recovery and you should have 1.6.2 also maKE sure this file is the only file on your sd card that helps good luck man let me know what happens

yeah i renamed it to recovery-1.6.2.img and i just downloaded better terminal but how do you get the keyboard up?

just tap the screen

do you have g talk

sent pm to you

ieatstarz1 said:
adb push recovery-RA-heroc-v1.5.2.img /sdcard
Pushing is equivalent of copy the file to the root of your sdcard. By the time you finished reading this it should be done. You'll know its done because the ouput will say something like transferred X bytes in X secs.
adb shell reboot
This will cause the phone to restart automatically. Wait till it is fully booted to continue.
adb shell
su
cd /sdcard/
flash_image recovery recovery-RA-heroc-v1.5.2.img
FLASHING TO THE RECOVERY TAKES SEVERAL SECONDS-- BE PATIENT. ENTER THE NEXT COMMAND ONLY AFTER THE COMMAND PROMPT RETURNS TO THE # (ROOT SYMBOL).
reboot recovery
This was complements of theresthatguy's method. Hope this helps.
Click to expand...
Click to collapse
This is what worked for me.
The 1.6.2 version did exactly to me like it is doing to you. I couldn't boot in to the recovery screen.
Sooo. I pushed the 1.5.2 image to the sdcard and then I
adb shell
su
flash_image recovery /sdcard/recovery-RA-heroc-v1.5.2.img
I was then able to boot into the 1.5.2 recovery
I then pushed the 1.6.2 image again and then it worked.

110 Error RUU 1.56 Fix - 100% unroot too!

Update - 2/21/2011
If you have bricked an HTC EVO this will likely NOT work for you and this is the wrong info to be reading. I have gotten a few emails from this link about EVO 110 errors.
12/26/2010 - This thread is super old now:
If you ran the 1.56 RUU and your phone no longer turns on visit htc.com, go to support, choose Hero (Sprint) and download the 2.1 system update.
Remove battery from your phone and start it up again, then run the exe file that you just downloaded -
http://member.america.htc.com/downlo...2.27.651.6.exe
------All the info below is kept for reference -------
(As of 3/31/2010 - I am 10 for 10 for getting these back and working!! 3/3 of going back to 100% stock)
Edit: I have no longer kept track... its been over a month and I know personally I've done about 15 more of these... with about half being return to stock.
If you need to contact me, PLEASE EMAIL instead of using private messages, it'll probably turn into a google talk chat anyways, so add me on there, [email protected] (Its just easier than having to log in here and reply to private messages, since I get emails on the go as well.)
So you just ran the 1.56 RUU and got a 110 error. Now your screen turns on and stays black and if you plug the phone into USB you see the HTC logo. Unplug it and see the RUU menu.
Like you, I decided to attempt to roll back using the RUU 1.56. I was hit with the 110 error, and nothing but fastboot would work, I was able to launch ./fastboot-mac oem boot to get into the system.
I tried ./fastboot-mac boot image/bootname.img and a billion other things like everyone else who is having the issue, but just like them I had no success. In the second post below are the steps to resolve this issue. This will either take you to your first Nandroid backup or to whatever ROM you choose to flash once you get recovery back. I have not found a way to get back to 100% stock, but at least your phone wont be a brick.
EDIT:As of 3/30/2010 @ 8:30 PM I was able to get my phone completely 100% to stock. I was able to do this by retrieving a Nandroid restore from someone who used flashrec to make their initial backup. This restore does not touch the recovery image but I was able to boot into my recovery then write the HTC recovery back on top of it. I now have 100% un-rooted phone. See Post number 2 for the right way to do this.?
I've helped a few people over log me in now.
I'm willing to continue doing this but it is cutting into my family time, I will do this for a "respectable" amount of money.
Feel like I've helped you??
Buy me some coffee!

(Zip attached includes fix and stock folders. Use the fix folder FIRST to get completely booted. You can use the stock folder if you want to get 100% stock after you have a running unrooted system but have RA recovery.)
Steps to resolve:
(You SHOULD have a Nandroid backup of some sort, if not download a ROM... Fresh1.1??)
1) Boot the phone to black screen
2) Plug phone into PC/MAC - The HTC logo should appear at this point
---- If you've been doing anything else, rerun the RUU and let it fail and reboot to the HTC logo.
3) PC - fastboot oem boot | MAC - ./fastboot oem boot
(Make sure you turn on USB Debugging under Settings --> Applications --> Developer)
4) Root your phone using asroot2
Code:
adb push asroot2 /data/local/
adb shell chmod 0755 /data/local/asroot2
adb shell
/data/local/asroot2 /system/bin/sh
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4775 su
5) This is where your Nandroid backup comes into play.
(Browse to your nandroid folder, find your first backup and copy all of the .img files except system and cache to your SD card root directory)
NOTE: At this point you should dismount the SD card if you mounted inside of Android OS(Sense/Launcher)
6) run adb shell (PC - adb shell | Mac - ./adb shell)
7) type su
8) Run the following commands (if you get out of memory errors, type su again and try once more)
NOTE: Do not copy the "#"'s in the commands, the # just means you are running as SU, as opposed to the "$"
Code:
# flash_image recovery /sdcard/recovery.img
# flash_image boot /sdcard/boot.img
# flash_image misc /sdcard/misc.img
9) now... type reboot recovery
This time you should get your recovery menu, should have been RA or whatever you used... from there I did a complete nandroid restore and my system booted.
Also, after I did this I did try to let it boot without doing a recovery and it wouldnt go anywhere... but I'm fairly impatient... it may have wanted to load. I figured it best to do an entire Nandroid restore though.
-------------------------------------------------------------
100% Stock Configuration Work Around
-------------------------------------------------------------
Non-Rooted Nandroid Backup:
nandroid.7z
I was able to get my phone completely 100% to stock. I was able to do this by retrieving a Nandroid restore from someone who used flashrec to make their initial backup. This restore does not touch the recovery image but I was able to boot into my recovery then write the HTC recovery back on top of it. I now have 100% un-rooted phone. I'm not sure how to go about posting a 127MB file, what do you think it the best place?
After restoring the Nandroid backup I tried this:
Code:
Dustan-Bonneys-MacBook:tools dustanbonney$ ./adb shell
$ su
su: permission denied
Then I rebooted to recovery (I used RA 1.5.2)
Code:
Dustan-Bonneys-MacBook:tools dustanbonney$ ./adb remount
remount succeeded
Dustan-Bonneys-MacBook:tools dustanbonney$ ./adb shell
/ # mount -a
mount: mounting /dev/block/mmcblk0p2 on /system/sd failed: No such file or directory
/ # cd /sdcard
/sdcard # flash_image recovery /sdcard/Stock/recovery.img
flashing recovery from /sdcard/Stock/recovery.img
/sdcard # reboot recovery
I was booted to the Triangle and exclamation mark... I pulled the battery and booted up normally.
Stock Kernel - 2.6.27-533ce29d [email protected] )
Stock Build - 1.56.651.2 CL85027 release-keys

Other things that should be mentioned:
If you used RA 1.6.2 - I was unable to get my boot.img or the stock boot.img from the RUU's rom.zip to flash back to the recovery partition. I had to use the RA 1.6.2.img and "flash_image recovery /sdcard/recoverynamegoeshere.img"
It seems that if you've flashed the radio update, the RUU does not write the radio back successfully. Others have had issues going back to the stock radio using the upgrade.zip option as well.
I attempted to use the boot.img, recovery.img, from the RUU's rom.zip with no success. I might try it again. I was able to get to stock recovery (Triangle and exclamation) and to the Hboot menu... but from hboot I had to run the RUU and rebrick the device cause I couldnt get anything at that point, even fastboot oem boot wouldnt load.
There have been times when I get weird issues writing the flash recovery, boot, or misc and when you reboot and load "fastboot oem boot" it wont look like it goes anywhere.... check "adb devices" and your device should be listed. From there do an "adb remount" and then "adb shell" and reflash once more and then "reboot recovery".
If all else fails, I'm available for a small fee.
[email protected]

Anxiously waiting your news. Just encountered this problem today.

Updated ...
imekul said:
Anxiously waiting your news. Just encountered this problem today.
Click to expand...
Click to collapse

Wow! If you've fixed this, I think you're everyone's hero now. We won't have to worry about using the RUU now

I was going to try something similar to this today, but i was unable to brick my phone using the 1.56.651.2 RUU. I was running Flipz updated radio and DamageControl v2.0r2.. The RUU completed successfully..
I was reading over the forum post in http://forum.xda-developers.com/showthread.php?t=645002 and i read that you could boot the system using the command 'fastboot oem boot' I was going to try to use FlashRec to do the work of Flashing the recovery, then booting into recovery and use nandroid.. but you beat me to it! Good work!

I attempted flashing a new recovery image this way with no avail... I also attempted only
Code:
flash_image recovery /sdcard/recovery.img
and still was unable to boot the phone into recovery. I think it had to have been something with doing boot.img and recovery.img at the same time... I dont know what the misc.img does and I'm assuming data.img is userdata... but I did them all and then it worked...
Other users also tried flashrec and with no success... right track though.
chavo2005 said:
I was going to try something similar to this today, but i was unable to brick my phone using the 1.56.651.2 RUU. I was running Flipz updated radio and DamageControl v2.0r2.. The RUU completed successfully..
I was reading over the forum post in http://forum.xda-developers.com/showthread.php?t=645002 and i read that you could boot the system using the command 'fastboot oem boot' I was going to try to use FlashRec to do the work of Flashing the recovery, then booting into recovery and use nandroid.. but you beat me to it! Good work!
Click to expand...
Click to collapse

What do u mean by 3) PC - fastboot oem boot | MAC - oem boot?

blankd3ckskat3r said:
What do u mean by 3) PC - fastboot oem boot | MAC - oem boot?
Click to expand...
Click to collapse
if your using a pc type fastboot oem boot
if your using a mac type ./fastboot oem boot

This!
Thanks Regaw
regaw_leinad said:
if your using a pc type fastboot oem boot
if your using a mac type ./fastboot oem boot
Click to expand...
Click to collapse

Trying this right now.
So far, am getting lots of "mtd: write error" and "mtd: re-read error" Out of memory errors for flashing the recovery image. Guess I'll give this some time, and try to su again and reflash? Or should I kill it as soon as the Out of memory errors pop up and try again?

If you get errors like...
adb shell
su
flash_image recovery .........
(out of memory... etc)
Then...
just su again... so you really su twice
its what I had to do.
imekul said:
Trying this right now.
So far, am getting lots of "mtd: write error" and "mtd: re-read error" Out of memory errors for flashing the recovery image. Guess I'll give this some time, and try to su again and reflash? Or should I kill it as soon as the Out of memory errors pop up and try again?
Click to expand...
Click to collapse

Trying it a second time, and so far am getting a bunch of Out of memory errors. After the first one "finished," I did as you recommended and typed "su" a second time, and then typed the "flash_image recovery /sdcard/recovery.img" command.
So far, looks like it's giving the same errors the second time around.

This second attempt, it ended with "error writing recovery: No space left on device."
Just to be sure, I checked the SD card, and that has over 1 GB of free space.

If you're willing to allow something like logmein.com or some way for me to remote assist you, I would like to try. [email protected] if you're in.
imekul said:
This second attempt, it ended with "error writing recovery: No space left on device."
Just to be sure, I checked the SD card, and that has over 1 GB of free space.
Click to expand...
Click to collapse

Sounds awesome. Thanks. I'll e-mail you now.

Dun Dun Dun... The results are in!
imekul said:
Sounds awesome. Thanks. I'll e-mail you now.
Click to expand...
Click to collapse

dfbonney is the man!!
After a friendly little session on LogMeIn Express, I am good as new! How awesome!!

imekul said:
dfbonney is the man!!
After a friendly little session on LogMeIn Express, I am good as new! How awesome!!
Click to expand...
Click to collapse
We ended up just needing to run
Code:
adb shell
reboot
fastboot oem boot
adb shell
su
//flash commands here
that seemed to do it. so make sure if you're having issues to restart the device and try again!
Edit: Also, we didnt get data.img to work so we only did boot, recovery, and misc.img's

[Q] ClockworkModRecovery (Only wants to wipe data) [SOLVED - Read / Scroll Down]

Ok, so i have a fresh new stock of 21e flashed onto my phone. Rooted with no errors, and I have Clockwork ROM Manager installed.
If I use the app to boot into recovery my phone just automatically Wipes all data then loads back up as if a fresh install was done, so I thought I would check the problem out myself (Power and vol.down), and the only options I have in the Clockwork Boot Menu are as follows:
Android system recovery <3e>
Confirm wipe of all user data?
THIS CAN NOT BE UNDONE.
No
No
No
No
No
No
No
Yes -- delete all user data
No
No
No
Click to expand...
Click to collapse
If I go back one page the only options I have are as follows:
Android system recovery <3e>
Android system recovery utility
reboot system now
wipe data/factory reset
wipe cache partition
wipe cache partition and package recovery
wipe nv dynamic partition
Click to expand...
Click to collapse
I can not go back any further, they are my only options in boot recovery of which I find extremely odd. (Until this is sorted I can not install a new ROM/Kernel and fix my network)
Any help would be much appreciated.
Kind Regards.

Loopy Frog said:
Ok, so i have a fresh new stock of 21e flashed onto my phone. Rooted with no errors, and I have Clockwork ROM Manager installed.
If I use the app to boot into recovery my phone just automatically Wipes all data then loads back up as if a fresh install was done, so I thought I would check the problem out myself, and the only options I have in the Clockwork Boot Menu are as follows:
If I go back one page the only options I have are as follows:
I can not go back any further, they are my only options in boot recovery of which I find extremely odd. (Until this is sorted I can not install a new ROM/Kernel and fix my network)
Any help would be much appreciated.
Kind Regards.
Click to expand...
Click to collapse
That's not ClockworkMod.
That's the stock Android recovery.

ah lol (embarrassing)
Thanks though... ok so it seems that my problem is that the copious amount of things that I try to install clockwork boot, it just wont happen. Any ideas?
Regards

Loopy Frog said:
ah lol (embarrassing)
Thanks though... ok so it seems that my problem is that the copious amount of things that I try to install clockwork boot, it just wont happen. Any ideas?
I am just about to see if I can do something with the LGDP2 V36 UMTS.
Regards
Click to expand...
Click to collapse
You can flash ClockworkMod Recovery with this.
[GUIDES/TOOLS]Making Developing/Flashing/Returning to Stock Easier
The Dark Lestat said:
1. Recovery Manager
This is a flashing tool that will let you install:
Stock Recovery
ClockworkMod Recovery
Touch ClockworkMod Recovery
Requirement:
You'll need to have the LG Thrill / Optimus 3D
You'll need to be rooted.
Superuser and SU have to be updated to the latest app and binary
Update Superuser in the market
Open Superuser app and go to the options
Scroll to the bottom and click "Su binary"
DOWNLOAD LINK: Recovery Manager - 18 MB
How To Use:
Extract the files with WinRar or 7zip
Launch "Recovery Manager.bat"
Make sure your phone is in "USB Debugging Mode" and is plugged in
Choose your option
Wait for the screen to refresh
Boot into recovery to verify it was flashed successfully
Click to expand...
Click to collapse

No Luck :-(
Did your guide word for word, all went successfully.
However.... I can use root applications on the device etc...
Though it appears I can no longer get the clockwork boot anymore?

Loopy Frog said:
No Luck :-(
Did your guide word for word, all went successfully.
However.... I can use root applications on the device etc...
Though it appears I can no longer get the clockwork boot anymore?
Click to expand...
Click to collapse
Try: 3d+volume down+power button
hold til 3 sec after seeing the logo.

Loopy Frog said:
No Luck :-(
Did your guide word for word, all went successfully.
However.... I can use root applications on the device etc...
Though it appears I can no longer get the clockwork boot anymore?
Click to expand...
Click to collapse
You can also use the ROM Manager app to boot into recovery.

p-vlad said:
Try: 3d+volume down+power button
hold til 3 sec after seeing the logo.
Click to expand...
Click to collapse
Nope doesn't work. >_<
The Dark Lestat said:
You can also use the ROM Manager app to boot into recovery.
Click to expand...
Click to collapse
Yeah that's what I was using when it used to work, however now when I do it, It just "deletes all user data". Obviously because it is not having any response from the Clockwork recovery boot, and goes straight into:
Android system recovery <3e>
Confirm wipe of all user data?
THIS CAN NOT BE UNDONE.
No
No
No
No
No
No
No
Yes -- delete all user data
No
No
No
Click to expand...
Click to collapse
I just don't understand why My boot wont change from android to the clockwork boot. >_<

Is it being flashed properly?
Try doing the flashing manually. Download the recovery image from www.clockworkmod.com/rommanager (choose touch for P920, nothing else), then open adb in cmd and type the following commands with phone plugged in:
adb push <image name>.img /data/local/tmp
adb shell su -c "dd if=/data/local/tmp/<image name>.img of=/dev/block/mmcblk0p6 bs=4096"
adb shell "rm /data/local/tmp/<image name>.img"
Replace <image name> with the filename of the img. If everything checks out, you should be able to boot into CWM. If you get errors, post them here
(I took the commands from The Dark Lestat's batch file, props go to him. I was too lazy to search for it Don't judge me, it's 12.30am here)

pandaball said:
Try doing the flashing manually. Download the recovery image from www.clockworkmod.com/rommanager (choose touch for P920, nothing else), then open adb in cmd and type the following commands with phone plugged in:
adb push <image name>.img /data/local/tmp
adb shell su -c "dd if=/data/local/tmp/<image name>.img of=/dev/block/mmcblk0p6 bs=4096"
adb shell "rm /data/local/tmp/<image name>.img"
Replace <image name> with the filename of the img. If everything checks out, you should be able to boot into CWM. If you get errors, post them here
Click to expand...
Click to collapse
Thanks Panda, I'll give it ago later when I have time, and let ya know how I go.

Loopy Frog said:
Thanks Panda, I'll give it ago later when I have time, and let ya know how I go.
Click to expand...
Click to collapse
Also, I'll update the scripts with a newer version, so that it's simplified.

Holy Sh*t .. .
dont use Rom Manager to boot into recovery.. there where so many bad reports about that app.. if you want to boot into recovery.. do this.. .
install Terminal Emulator..
type in ..
su (enter)
reboot recovery (enter)
your phone will boot into what recovery you have .. .
hope that helps!

JastaPein said:
Holy Sh*t .. .
dont use Rom Manager to boot into recovery.. there where so many bad reports about that app.. if you want to boot into recovery.. do this.. .
install Terminal Emulator..
type in ..
su (enter)
reboot recovery (enter)
your phone will boot into what recovery you have .. .
hope that helps!
Click to expand...
Click to collapse
It's not using ROM Manager to BOOT into recovery.
It's using ROM Manager to install ClockworkMod that was the issue.

Very weird indeed. I also have flashed yhe 21E rom from LG. Next I rooted the phone and installed CWM touch. I have no problems with it.

JastaPein said:
Holy Sh*t .. .
dont use Rom Manager to boot into recovery.. there where so many bad reports about that app.. if you want to boot into recovery.. do this.. .
install Terminal Emulator..
type in ..
su (enter)
reboot recovery (enter)
your phone will boot into what recovery you have .. .
hope that helps!
Click to expand...
Click to collapse
Thanks, either/or this doesn't matter at this stage, I need to able to boot into recover for this or even clockwork to do it anyway. I'll keep this in mind nonetheless.
pandaball said:
Is it being flashed properly?
Try doing the flashing manually. Download the recovery image from www.clockworkmod.com/rommanager (choose touch for P920, nothing else), then open adb in cmd and type the following commands with phone plugged in:
adb push <image name>.img /data/local/tmp
adb shell su -c "dd if=/data/local/tmp/<image name>.img of=/dev/block/mmcblk0p6 bs=4096"
adb shell "rm /data/local/tmp/<image name>.img"
Replace <image name> with the filename of the img. If everything checks out, you should be able to boot into CWM. If you get errors, post them here
(I took the commands from The Dark Lestat's batch file, props go to him. I was too lazy to search for it Don't judge me, it's 12.30am here)
Click to expand...
Click to collapse
All went well, expect for the last string, see below;
I renamed "recovery-clockwork-touch-5.8.1.5-p920" - "x"
C:\Users\Astro\ADB>adb push x.img /data/local/tmp
3204 KB/s (5995063 bytes in 1.827s)
C:\Users\Astro\ADB>adb shell su -c "dd if=/data/local/tmp/x.img of=/dev/block/mmcblk0p6 bs=4096"
1463+1 records in
1463+1 records out
5995063 bytes transferred in 0.992 secs (6043410 bytes/sec)
C:\Users\Astro\ADB>adb shell "rm/data/local/tmp/x.img"
rm failed for /data/local/tmp/x.img, No such file or directory
Click to expand...
Click to collapse

Loopy Frog said:
All went well, expect for the last string, see below;
I renamed "recovery-clockwork-touch-5.8.1.5-p920" - "x"
Click to expand...
Click to collapse
I'm about to upload a newer version of it. Let me know if it works.

Alright.
Here's the new Recovery Manager with updated scripts. It should be a lot cleaner now.
Recovery Manager

The Dark Lestat said:
Alright.
Here's the new Recovery Manager with updated scripts. It should be a lot cleaner now.
Recovery Manager
Click to expand...
Click to collapse
You my friend, are truly amazing!! what ever your alterations were; it worked!
Thank you.

Loopy Frog said:
You my friend, are truly amazing!! what ever your alterations were; it worked!
Thank you.
Click to expand...
Click to collapse
I think it's because my scripts were thrown together in the previous one.
Anyways, it's cleaned up.
Glad it worked!

Is there a way to delete/uninstall an APK and its data from fastboot?

so i went into FKU franco kernel updater and changed my CPU max speed from 1500 back to the default but did not change my voltage settings back to default. now the device is softbrocked and just boots to the google nexus splash screen
I have tried flashing:
system.img
boot.img
bootloader.img
stock 4.4.4 kernel
yet regardless of flashing the above the device still is softbricked and wont get past the nexus google logo.
the only thing i have not flashed over is my user data and thats because i dont want to lose my pictures and video of my little boy that i didn't get to back up yet due to my dropbox just hitting its limit.
Im hoping I can remove the franco updater app and its user data and boot but maybe thats not possible?
Thanks for any and all help!

nextelbuddy said:
so i went into FKU franco kernel updater and changed my CPU max speed from 1500 back to the default but did not change my voltage settings back to default. now the device is softbrocked and just boots to the google nexus splash screen
I have tried flashing:
system.img
boot.img
bootloader.img
stock 4.4.4 kernel
yet regardless of flashing the above the device still is softbricked and wont get past the nexus google logo.
the only thing i have not flashed over is my user data and thats because i dont want to lose my pictures and video of my little boy that i didn't get to back up yet due to my dropbox just hitting its limit.
Im hoping I can remove the franco updater app and its user data and boot but maybe thats not possible?
Thanks for any and all help!
Click to expand...
Click to collapse
Do you have a custom recovery? If so, use adb while in recovery to pull your files. If not, then flash one then pull them.
Not sure why you mentioned "boot.img" then "stock 4.4.4 kernel", boot.img = the kernel lol
Don't know why your device won't boot even after flashing stock boot.img, but if you use TWRP you can use the file manager to delete the .apk/other files.

Lethargy said:
Do you have a custom recovery? If so, use adb while in recovery to pull your files. If not, then flash one then pull them.
Not sure why you mentioned "boot.img" then "stock 4.4.4 kernel", boot.img = the kernel lol
Don't know why your device won't boot even after flashing stock boot.img, but if you use TWRP you can use the file manager to delete the .apk/other files.
Click to expand...
Click to collapse
thanks, i deleted the franco files and still cant boot.
i want top pull files but it looks like I need ADB and currently i can only get into fastboot mode.
(i'm using wugfresh toolkit, i know some say manual is the way to go but right now this is what I have to go on and have had no issues thus far with it)
i was using the button pull files in the tool kit but its not detecting the device since im in fastboot mode.
i swear I did a factory reset before and my photos were still present but many articles online say in 4.4 that a factory reset will wipe your photos.

nextelbuddy said:
thanks, i deleted the franco files and still cant boot.
i want top pull files but it looks like I need ADB and currently i can only get into fastboot mode.
(i'm using wugfresh toolkit, i know some say manual is the way to go but right now this is what I have to go on and have had no issues thus far with it)
i was using the button pull files in the tool kit but its not detecting the device since im in fastboot mode.
i swear I did a factory reset before and my photos were still present but many articles online say in 4.4 that a factory reset will wipe your photos.
Click to expand...
Click to collapse
Don't use toolkits. You say you've had no issues but you have and that issue is that you don't know how to use adb and fastboot
Click the link in my signature to get to the sticky roll -up thread. From there you will find my "adb and fastboot. What is it?" thread. Please read it. You'll have ALL the information you need to get your photos etc off your sdcard
Stock recovery - factory reset wipes sdcard
Custom recovery - factory reset preserves sdcard
Sent from my Nexus 5 using Tapatalk

rootSU said:
Don't use toolkits. You say you've had no issues but you have and that issue is that you don't know how to use adb and fastboot
Click the link in my signature to get to the sticky roll -up thread. From there you will find my "adb and fastboot. What is it?" thread. Please read it. You'll have ALL the information you need to get your photos etc off your sdcard
Stock recovery - factory reset wipes sdcard
Custom recovery - factory reset preserves sdcard
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks,
since i can not boot, i am forced to use TWRP recovery and then go ingo CMD shell and ADB there however when I do ADB Devices i get the serial number showing its connected but then it says RECOVERY at the end.. much lke when you are in fastboot it says FASTBOOT at the end of the device.
i tried doing a pull using this:
adb shell
mount data
exit
adb pull data/media/0 c:\MyBackup
but when I do ADB Shell, the command prompt says this
~ # ←[6n
if t that prompt i type mount data then I get this:
mount data
mount: mounting /dev/block/mmcblk0p28 on /data failed: Device or resource busy
~ # ←[6n
im not sure how else to get to a working ADB to perform a proper pull if i cant boot into the device fully

nextelbuddy said:
Thanks,
since i can not boot, i am forced to use TWRP recovery and then go ingo CMD shell and ADB there however when I do ADB Devices i get the serial number showing its connected but then it says RECOVERY at the end.. much lke when you are in fastboot it says FASTBOOT at the end of the device.
i tried doing a pull using this:
adb shell
mount data
exit
adb pull data/media/0 c:\MyBackup
but when I do ADB Shell, the command prompt says this
~ # ←[6n
if t that prompt i type mount data then I get this:
mount data
mount: mounting /dev/block/mmcblk0p28 on /data failed: Device or resource busy
~ # ←[6n
im not sure how else to get to a working ADB to perform a proper pull if i cant boot into the device fully
Click to expand...
Click to collapse
It could say "device busy" if data is already mounted. Does twrp have a "mounts and storage" menu like CWM? Where you can mount data? If so, check if it is mounted there (would typicall say "unmount data" if it was mounted, otherwise it would say "mount data" if it is unbmounted)

nextelbuddy said:
Thanks,
since i can not boot, i am forced to use TWRP recovery and then go ingo CMD shell and ADB there however when I do ADB Devices i get the serial number showing its connected but then it says RECOVERY at the end.. much lke when you are in fastboot it says FASTBOOT at the end of the device.
i tried doing a pull using this:
adb shell
mount data
exit
adb pull data/media/0 c:\MyBackup
but when I do ADB Shell, the command prompt says this
~ # ←[6n
if t that prompt i type mount data then I get this:
mount data
mount: mounting /dev/block/mmcblk0p28 on /data failed: Device or resource busy
~ # ←[6n
im not sure how else to get to a working ADB to perform a proper pull if i cant boot into the device fully
Click to expand...
Click to collapse
ok so i went into TWRP and UNMOUNTED DATA
and then I went back in to cmd prompt and tried mount again and it worked i guess since theres no error. I typed EXIT and was brought back to normal windows command prompt. I then typed
adb pull data/media/0 C:\Users\srobertson\Desktop\Nexus 5 7-15-2014 DCIM
and when I hit enter it just shows a list of ADB commands as if it didnt recognize anything yet when I do ADB DEVICES it shows the device and ID

nextelbuddy said:
ok so i went into TWRP and UNMOUNTED DATA
and then I went back in to cmd prompt and tried mount again and it worked i guess since theres no error. I typed EXIT and was brought back to normal windows command prompt. I then typed
adb pull data/media/0 C:\Users\srobertson\Desktop\Nexus 5 7-15-2014 DCIM
and when I hit enter it just shows a list of ADB commands as if it didnt recognize anything yet when I do ADB DEVICES it shows the device and ID
Click to expand...
Click to collapse
If you're going to put spaces in your folder names, you'll have to enclose the entire path in "...
Example
adb pull data/media/0 "C:\Users\srobertson\Desktop\Nexus 5 7-15-2014 DCIM"
Best to avoid spaces though.
I'll put this in the guide, thanks.

rootSU said:
If you're going to put spaces in your folder names, you'll have to enclose the entire path in "...
Example
adb pull data/media/0 "C:\Users\srobertson\Desktop\Nexus 5 7-15-2014 DCIM"
Best to avoid spaces though.
I'll put this in the guide, thanks.
Click to expand...
Click to collapse
Thanks so much for your help
I ended up taking the leap and performing a Factory reset from TWRP and when I logged back into the phone I saw all my media was still present Whew.
just for posterity I went ahead and tried your code in ADB to make sure the quotes worked and it did so thank you very much and i will keep those notes handy for next time.

Updating / System Format HD 8 2015 Gen 5

I have a 2015 gen 5 OS 5.1.1 HD 8. I am trying to get it back to stock just to refresh. I try going to settings and doing a system refresh restarts and nothing.
click update shows no updates available. place up[date.bin file in the root of the device, shows update available. Then I click start update, validates update then restarts nothing.
My device is rooted and i dunno what else to do. I thought maybe its one of the packages thats disabled so I went to adb shell then su. Then ran pm list packages -d to show all disabled ones, then enabled those.
So i read that you can adb sideload an update.bin, so I go to put the device into recovery mode. Vol Down + power. Nothing Amazon screen boots then black then amazon screen then the fire screen.
tried every combination and dont know what to do.
So i've tried everything and cant seem to get it to work. Any suggestions?

Fixed
I fixed it. Guess I Messed up my recovery partition. Anyway I remembered from an old post that i had someone post the recovery file.
You must have root.
So copy recovery.img to the root of the device or /sdcard
then go to your command shell.
adb shell
su
DEV=$(ls /dev/block/platform/*/by-name/recovery); echo $DEV
dd of=$DEV if=/sdcard/recovery.img
exit
exit
adb reboot recovery
should reboot into recovery
then after downloading correct update.bin
adb sideload then filename of your update.
worked and am on my wiped device.
Thanks ...... to myself for messing it up and fixing it.