Hi Guys.
I don't know if this is the right forum, please tell me if so.
I think that I've screwed up bigtime when i tired to upgrade my recovery image. Here is what happende.
I have rooted my Hero a long time ago, so what i did was trying to follow this guide for installing the latest recovery image: http://forum.xda-developers.com/showthread.php?t=645253
when i tired to flash the recovery image using this command: flash_image recovery /sdcard/recovery.img. I was using Terminal Emulator.
What happened was i got a lot of error messages saying that the phone was out of memory. This resulted in that i couldn't get acces to the recovery menu when rebooting my phone and that i cant access my phone rom.
I then tired to flash the recovery image using the installation guide of this thread: http://forum.xda-developers.com/showthread.php?t=561124
The thing is that i can see that the phone is mounted through the "fastboot devices" commando
When i try to flash the recovery image using fastboot i get this error message:
C:\android-sdk-windows\tools>fastboot boot recovery.img
downloading 'boot.img'... FAILED (remote: not allow)
finished. total time: 0.001s
HELP! What can i do? Is my hero 'saveable or is it bricked?
//Mads
First of all its not bricked don't worry. Do you still have old recovery of Amon_Ra or not ? If have than put latest version of Amon_Ra recovery into your sdcard & reboot your phone into old recovery of Amon_Ra Than just follow these commands
Code:
adb shell
$su (not required if you have root already)
#mount -a
#flash_image recovery /sdcard/recovery-RA-hero-v1.7.0.1.img
when its done just type adb reboot . your phone will reboot
Hope it helps
Hi, it's good to hear. I think that my old recovery mode was screwed up during the attempt to upgrade. because if i tries to boot into it it just stops at the HERO bootscreen and goes no futher. If i just try to boot normally it goes to a black screen and then nothing else happens. Tried to let it boot for 30 min without anything happening.
The only thing i can access is fastboot.
when i try adb shell it says the following:"
C:\android-sdk-windows\tools>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
you need to update your drivers that means you are not having latest drivers .. there was a thread i guess download drivers & check how to set up correct adb drivers on windows .. & by the way do you have installed HTC Sync ? make sure you have installed HTC Sync because it finds all htc drivers i guess than try
Code:
adb shell reboot bootloader
fastboot boot recovery-RA-hero-v1.7.0.1.img
adb shell mount /sdcard
adb push recovery-RA-hero-v1.7.0.1.img /sdcard/recovery-RA-hero-v1.7.0.1.img
adb shell flash_image recovery /sdcard/recovery-RA-hero-v1.7.0.1.img
adb shell reboot
Thx for the help, but that didn't work either.
I found this guide http://forum.xda-developers.com/showthread.php?t=714519 which did the work. So now i'm back at 1.5 for a little while, just need to root right away The good thing is that my phone is working
Thx for the help.
Glad to hear it Men .. Well come abroad
Related
I can't seem to get the custom recover working on my eris. I followed the "adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery-ra-eris.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery-ra-eris.img
4. Close the command prompt and turn off you phone."
to the tee and everything seemed to work.I didnt recieve any error msg on the cmd console but when I boot up holding the Vol+ and power I get and Android under a ! in a triangle and a message that says "E:Can't open /cache/recovery/command then I only get 4 options and none of them are to flash a rom so I always reboot system. I really want to put a rom on here but I have no idea what went wrong. Im sorry if this is a redundant post. I combed a hundred of them and couldnt find anything like this. Thank you for any help in advance.
Oh and before I forget I tried the adb fastboot bootloader version as well. Everytime I do it it sits in the command console stating "waiting for device". Im plugged in so I dont understand what Im doing wrong.
Curious to know... are you using windows or mac? have you tried:
adb shell reboot recovery
to see if that does anything?
Maybe you have a different version of the recovery saved than I do, but mine is named "recovery-RA-eris-v1.6.2.img"...maybe you just had an input error somewhere along the line? forgot a capital letter or something? I had the same error myself and following the directions I got the recovery image back
Im running windows 7 and I have both recovery-RA-eris-v1.6.2.img and the recovery-RA-eris.img. I have been using the v1.6.2 and I just modify the command to look like this "adb push recovery-ra-eris-v1.6.2.img /sdcard" How would I use adb shell reboot recovery would I just sub that in place of something? kinda getting discouraged because I have tried this 10x now. I have checked and the usb debugging is on and I do have the eris 2.1 root and not the leak. I wonder is there any way I can flash this with something from the droid mkt place like SUFBS? Or maybe change a rom's name to look like an update zip?Just looking for ways to make this work Im so jealous of everyone that has got it to work.
here is another question and it might be that this is why its not working with the fastboot option but on this website's walk through thefuzz4.net it states to "You will have FASTBOOT highlighted in red like it is here" Now Im not a pro at this but what does this mean? How do I highlight text in the command shell? I would post the full url but since Im new it wont let me post urls yet.
Dachix said:
here is another question and it might be that this is why its not working with the fastboot option but on this website's walk through thefuzz4.net it states to "You will have FASTBOOT highlighted in red like it is here" Now Im not a pro at this but what does this mean? How do I highlight text in the command shell? I would post the full url but since Im new it wont let me post urls yet.
Click to expand...
Click to collapse
when hes saying fastboot will be highlighted in red he's referring to booting your phone into the standard recovery mode (when power is off) hold volume up and power.
Walking Taco seriously love that name. The only options I get when I hold down vol+ and pwr is 1. reboot system now 2. apply sdcard update 3. Wipe Data/ factory reset 4. Wipe cache partition and all are in purple and at the bottom on the phones screen is "E:Can't open/cache/recovery/command"
The website fuzz4net says to:
WINDOWS USERS
From your tools directory in the sdk do the following command
adb fastboot bootloader
You will have FASTBOOT highlighted in red like it is here
Now on your computer do the following
Fastboot flash recovery recovery-RA-eris-v1.6.2.img
Ok after that completes pull the battery then power back up with Vol Up + Power to enter recovery
But when I get done ...after the last step the cmd.exe window states <waiting for device> any ideas? Thanks for helping too. Leave it to me to hit a snare
almost forgot when it gets to <waiting for device> nothing happens I literally have left and come back 3 hours later and no progress was made
Dachix said:
almost forgot when it gets to <waiting for device> nothing happens I literally have left and come back 3 hours later and no progress was made
Click to expand...
Click to collapse
I honestly don't know man, I would factory wipe it and try and start from the beginning. I followed the fuzz's instructions and was rooted in less than a half hour. Sorry brother.
Thanks!
ROOTED!!!!!! Here is what I did:
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery-ra-eris.v1.6.2.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery-ra-eris.v1.6.2.img
This was not working until I deleted the spaces in between img/sdcard for all the commands. Then and I do not know why but when I would turn odd my phone the vol+ pwr on it would not work so instead I used the adb shell reboot recovery command like droidfreak suggested then BOOYAH the custom recovery was loaded thank you all for helping me.
Dachix said:
ROOTED!!!!!! Here is what I did:
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery-ra-eris.v1.6.2.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery-ra-eris.v1.6.2.img
This was not working until I deleted the spaces in between img/sdcard for all the commands. Then and I do not know why but when I would turn odd my phone the vol+ pwr on it would not work so instead I used the adb shell reboot recovery command like droidfreak suggested then BOOYAH the custom recovery was loaded thank you all for helping me.
Click to expand...
Click to collapse
Awesome news! Have fun with your rooted phone!
Hi all im trying to get adb setup with my Evo 3D (came here as a noob the other day but its all really simple compared to other phones i've done)
anyhow this is the first time i've tried using adb and it just refuses to work, as many of the rom devs say when you install the firmware for the rom you reboot into recovery by either reboot and pull sd card then enter bootloader (works fine OFC) or use adb via
Code:
adb reboot recovery
but it just says error: device not found, fastboot works fine via usb, i can reboot bootloader fine just stuck for answers as to why adb isn't
EDIT: Nevermind i worked it out now lol adb doesn't work VIA bootloader lol! ADMIN PLEASE REMOVE
hi everyone,
I'm coming from this thread http://forum.xda-developers.com/showthread.php?t=1834761
I have been stuck for more than one week now and i didn't find any solution.
My problem is that I'm currently stock in a clockworkmod recovery boot loop on my Asus Transformer Prime without adb/fastboot connection:
1 - I had install CM9 stable on my Transformer Prime, after a wide data and then send throw "adb push" the CM9.zip,
2 - I reboot by CM9 in recovery mod to install Gapps,
3 - I install the Gapps zip,
4 - I ask to clockworkmod to reboot,
5 - Since then I'm in a clockworkmod recovery boot loop without adb/fastboot connection (witch used to be working),
If kown how can I get adb/fastboot connection back to be able to find my device with the adb command " adb devices " and then be able to send this command => " dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1 "
Thank you for your understanding,
Kind regards,
Adb and fastboot are two different things... Fastboot is obtained buring booting process with vol down pressed, then not selecting recovery with volume up. So you should have fastboot access.
In this case I would suggest to fastboot flash TWRP (see on their website for instructions) it will perhaps fix things or at least give you adb access.
If you use cwm take the old 5.8.2.0 modded for not looping with reboot to recovery feature, or stay with twrp.
I would look at the following thread for unbricking the TF201:
http://forum.xda-developers.com/showthread.php?t=1514088
Sounds like you might fall into Option 1a.
I was having your same issue but it was because I rebooted into recovery from the reboot option on the CM10 rom. In any event, I couldn't get adb to work or recognize my device no matter what. I then decided to use my macbook pro. I can tell you that using adb on a mac is much easier as you don't have to download the drivers or sdk, just the platform tools. Here's a link: http://forum.xda-developers.com/showthread.php?t=1387527. I know this may not help if you or someone you know doesn't have a mac, but it saved me.
So I'm in the process of trying to Root my ZTE Smarttab 10 on firmware v03b.
Ive been following instructions on the following pages:
http://forum.xda-developers.com/showthread.php?t=1629630
http://forum.xda-developers.com/showthread.php?t=1473555
The instructions are spread out across those threads and my problem starts kind of early in the process.
My goal is to use ADB to boot in to the Bootloader and then use a recovery rom to use TWRP to install a rom.
What i have done:
I have installed the ZTE Drivers
I have installed the SDK tools and updated it.
Now when the tablet is running normally I can see it in ADB and is able to run the command.
ADB Reboot Bootloader
This reboots the devices to a black screen (I assume this is the bootloader) and windows recognizes that a device is there.
The problem is that when I try to see this from ADB i cannot see the device when running ADB Devices.
This makes the next step impossible as I need to use ADB to boot a recovery rom.
So I would have posted in the development treads listed above but as I dont have 10 posts (this being my first post) I cannot post in the threads above.
I'm confident that this is a driver problem and I have uninstalled and re-installed all the drivers related to this including SDK.
But no luck yet.
Where other people say they have succeeded is when in the device manager they have ADB interface and ZTE Handset ADB interface listed.
This is the state where I'm at but I still cannot see the device in ADB.
Anyone have any insight on this kind of problem and can offer any help for a solution or direction to get to the solution.
Thank you for your help and attention!
//Nagarutu
Vodafone (ZTE) SmartTab10 3.2 HoneyComb
You can't use adb in bootloader mode, you want fastboot. So when you do 'adb reboot bootloader'. It reboots to the black screen (that is the bootloader). Try typing 'fastboot devices' and see if you're device comes up. It should if you have all drivers installed correctly and fastboot on your system. Then you'll be able to do 'fastboot flash recovery recovery.img' to install the custom recovery, then a 'fastboot reboot' and lastly an 'adb reboot recovery' will get you into your custom recovery to flash a new rom. Don't forget to make a backup.
matt4321 said:
You can't use adb in bootloader mode, you want fastboot. So when you do 'adb reboot bootloader'. It reboots to the black screen (that is the bootloader). Try typing 'fastboot devices' and see if you're device comes up. It should if you have all drivers installed correctly and fastboot on your system. Then you'll be able to do 'fastboot flash recovery recovery.img' to install the custom recovery, then a 'fastboot reboot' and lastly an 'adb reboot recovery' will get you into your custom recovery to flash a new rom. Don't forget to make a backup.
Click to expand...
Click to collapse
Thank you for the help ! it cleared things up for me.
Now the trouble's continue.
With the firmware im on (v03b) you cannot use the fastboot flash method but only fastboot.
And they way it is supposed to be done is that you run
fastboot boot recovery.img (recovery being a twrp recovery for my device)
When its booted to TWRP i should be able to see it in ADB to be able to run the following commands to it:
--> adb remount
--> adb shell
--> ln -s /system/xbin/su /system/bin/su
However I cannot get it to show in ADB (or fastboot) when its booted in to TWRP.
Any ideas?
I managed to solve the last bit to.
Now it was actually a driver problem, so i just updated the driver in device manager and located the ADB driver from ZTE and it worked to boot in to TWRP and then to flash the device.
Now I have CM10 installed and is smiling!
Took me 4 days but damn it its done!
Thanks for the help!
Glad you've figured it out
1a
2a
3a
4a
5a
Hey Guys & Girls,
I was recently trying to follow along with this pretty rag-tag guide that I came across to avoid rooting my phone:
https://spoofaholics.wordpress.com/converting-a-joystick-to-a-system-app-without-root/
I am using an HTC 10 that I had unlocked the Bootloader to right before attempting to follow the guide. It may be worth mentioning I did not use the link he provided to a full SDK download, I only installed Fastboot and ADB like I had done when I unlocked the Bootloader because it seemed to be all that was needed. I am using TWRP version 3.1.1-0-pme.img.
Time to get to the actual problem. The folders are all in the right places and instead of rebooting my phone in Bootloader mode completely manually I use the command "adb reboot download" (then go to bl mode) just to try and make sure everything is connected and working.
At this point I should be able to use the command " fastboot boot twrpgm.img" (renamed it) to have TWRP open on my phone, right? Unfortunately when I put the command in this occurs:
JohnDoes-MBP:~ JohnDoe$ cd Desktop/platform-tools
JohnDoes-MBPlatform-tools Brian$ ./adb reboot download
adb server version (31) doesn't match this client (39); killing...
* daemon started successfully *
JohnDoes-MBPlatform-tools JohnDoe$ ./fastboot boot twrpgm.img
downloading 'boot.img'...
OKAY [ 1.213s]
booting...
FAILED (remote: unlock device to use this command)
finished. total time: 1.263s
JohnDoes-MBPlatform-tools JohnDoe$
Why am I getting this error even though my Bootloader is unlocked? Could it be referring to something else?
FAILED (remote:unlock device to use this command)
And yep, those are Mac terminal commands I'm using. Even though it's a Windows guide I've tried it on both Windows and Mac, but my Mac is always with me. I get the exact same failed message on both OS.
Misc Info
My HTC 10 is running Nougat 7.0
I've rooted, and unrooted the phone after trying this so TWRP is definetely working.
All help is appreciated.