I unlocked the bootloader from HTCdev.com and followed the instructions from scott's roms for installing clean rom dev edition which booted fine. I noticed that the phone wouldn't turn on today and discovered these issues.
Also, I have CWM recovery installed (I read about all the issues after the fact having never had issues like this before with a myriad of phones/tablets i ASS-umed that it would be fine).
Currently the phone will not charge, the screen stays black, it shows up in adb in recovery mode (screen still black), cannot get into the bootloader, cannot run fastboot commands. I've tried to use adb push to get amon-ra on this to no avail.
This isn't mine, it's a friends and if anyone knows a method for me to get into the bootloader i'd be grateful. I know fastboot and adb well enough. Please PM me or answer on here. Thanks guys!
You aren't in terrible shape.
If you can use adb you are ok. Download amon ra and my zimage flasher here: http://forum.xda-developers.com/showthread.php?t=1419587
Extract zimage flasher and find the file dd inside.
Then do "adb push dd /tmp"
Then do "adb push amonra.img /tmp"
Then do "adb shell"
Then do "cd /tmp"
Then do "chmod 4755 dd"
Then do "./dd dd if=/tmp/amonra.img of=/dev/block/mmcblk0p23"
Then yank battery and USB and try to charge.
Related
i have had problems with Rom manager not flashing recovery correct leaving me with no recovery. so i had to manually flash recovery following these steps exact. I have personally bricked 2 ERIS phones lucky me.The first i thoought it was just something i did, lucky i had another to replace it...(the second BRICK eris).
So here is a solution to keep from having a BRICK
USE Amon RA's Recovery PERIOD.
credit to northmendo @droidforums
1. download flash_image Here Updated Link 3/17/10
2. Open the terminal and copy and paste the following commands.
adb shell [hit enter]
su [hit enter]
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system [hit enter]
3. In a new terminal window (don't close the original one).
adb push flash_image /system/bin [hit enter]
exit [hit enter]
4. Now in the original terminal window
chmod 755 /system/bin/flash_image [hit enter]
5. Now exit all termainl windows and reboot your phone.
6. Download
Amon_RA's recovery Here.
7. Mount your phones sd card and drop recovery-RA-eris-v1.6.2.img on to it and eject
your phone.
8. Open the Terminal and copy and paste the following commands with the phone connected
to your computer.
8. adb shell [hit enter]
9. su [hit enter]
10. flash_image recovery /sdcard/recovery-RA-eris-v1.6.2.img
11. To get into recovery turn off you phone and hold the Volume Up + Power until it boots into recovery.
That's it.
ROM Manager and Clockwork recovery does not work for the Eris.
ROM Manager and Clockwork recovery does not work for the Eris (as far as I know).
Edit: Oops, sorry for the double post.
I currently have the clockwork recovery installed on my eris, can I just download amon's recovery image and install it to switch to it? Or do I have to uninstall clockwork recovery and then install amon's?
trishuhh said:
I currently have the clockwork recovery installed on my eris, can I just download amon's recovery image and install it to switch to it? Or do I have to uninstall clockwork recovery and then install amon's?
Click to expand...
Click to collapse
try to flash it from rom manager,(under other recoveries) if Rom manager has worked for you with no problems. if it doesnt work follow instructions as listed in 1st post
I wouldn't use clockwork recovery, it messed up my installation to the point i couldn't flash any rom or restore any nand. When i would try to flash anything it would fail, It failed when i tried to use the root rom....After I tried flashing root rom i had a nice looking brick on my desk....(I even changed back to RA but Clockwork had messed up my phone so bad that RA didn't even work either....
YOU HAVE BEEN WARNED!!!!!
Yeah, use Amon's. It does every job you need, and is 100% stable and reliable.
t2noob said:
I wouldn't use clockwork recovery, it messed up my installation to the point i couldn't flash any rom or restore any nand. When i would try to flash anything it would fail, It failed when i tried to use the root rom....After I tried flashing root rom i had a nice looking brick on my desk....(I even changed back to RA but Clockwork had messed up my phone so bad that RA didn't even work either....
YOU HAVE BEEN WARNED!!!!!
Click to expand...
Click to collapse
yea you beat me too it, , i only used it because i had it for my DROID and thought maybe devs would try to add it to the list on rom manager.
ok, obviously a bit of an amateur here, how do you know which recovery image you have, i installed amon's, but i'm not sure if clockwork made it to my phone somehow, thinking about unrooting soon, that's why i ask, thanks.
jrhoades858 said:
ok, obviously a bit of an amateur here, how do you know which recovery image you have, i installed amon's, but i'm not sure if clockwork made it to my phone somehow, thinking about unrooting soon, that's why i ask, thanks.
Click to expand...
Click to collapse
reboot into recovery and read the bottom
Ok Please help a newbie out here im losing my mind. I downloaded flash, plugged phone into mac and set phone to debugging and mounted. Opened terminal from utilities on Mac. When I enter adb shell it says "command not found" if I try using ./ before adb as suggested on another forum for macs when i enter su it asks for password? Any how please help a brother out. Thanks
I flashed amons ras recovery from my phone it was easier for me I didn't use rom manger or terminal emulater
Sent from my FroyoEris using XDA App
Can someone help me get rid of clockwork recovery it showed up after I flashed a rom. How do you flash Amons recovery?
tkryan said:
Can someone help me get rid of clockwork recovery it showed up after I flashed a rom. How do you flash Amons recovery?
Click to expand...
Click to collapse
You do exactly what the first post says
Sent from my Eris
ufccowboyfan said:
Ok Please help a newbie out here im losing my mind. I downloaded flash, plugged phone into mac and set phone to debugging and mounted. Opened terminal from utilities on Mac. When I enter adb shell it says "command not found" if I try using ./ before adb as suggested on another forum for macs when i enter su it asks for password? Any how please help a brother out. Thanks
Click to expand...
Click to collapse
When you are doing this, are you in the correct directory? For example, my SDK is installed in /android , so first I would:
cd /android/tools
then
./adb shell
could someone help me with this. i really need to get the stock recovery image on my eris and im alittle noobie at this stuff. if any one could help id be sooooo happy
I'm not sure how to flash amons on a mac. I know for windows you put the recovery.img in the sdk tools folder, boot into fastboot and type
Fastboot flash recovery recovery.img
To get stock recovery (I assume you want your phone back to stock) then flash the official ruu. Will return your phone to 100% stock. You can find it on a sticky in the Eris general forums I believe.
Sent from my Eris using XDA App
I'm not sure on a mac, but on Windows you put the img in the tools folder of your sdk, boot into fastboot and type in adb:
Fastboot flash recovery recovery.img
To get stock recovery back, simply flash the official ruu found on a sticky in the Eris general forums I believe. Flashing the ruu will unroot your phone.
Sent from my Eris using XDA App
I installed Amon Ra as part of the root for leakers instructions some time ago. -- Is there a new version out? (Search was surprisingly not helpful) And what is the best way to update recovery?
Slugdoc said:
I installed Amon Ra as part of the root for leakers instructions some time ago. -- Is there a new version out? (Search was surprisingly not helpful) And what is the best way to update recovery?
Click to expand...
Click to collapse
There is no new version out; the first version (v1.6.2) is the only one that Amon_RA published.
IF there was a new version, you could flash it by using adb with the existing Amon_RA. You don't even need to push a version of "flash_image" to the phone, because it is already in /sbin in Amon_RA recovery. Just get the recovery image to your SD card, start an interactive shell (adb shell), and then
flash_image recovery /sdcard/<wherever-you-put-it>/recovery-RA-eris-v1.6.2.img
Yes, you can "flash a recovery partition by using the recovery" - because when you are interacting with it (the recovery boot), it lives entirely in a ramdisk.
The second easiest way is to have the engineering bootloader (1.49.2000 S-OFF) installed on your phone, and flash it with fastboot from the PC, as in
fastboot flash recovery recovery-RA-eris-v1.6.2.img
Note that neither of these two methods perform any integrity checks on the recovery image file that the normal "Flash .zip from sdcard" ROM installation method does. Therefore, it is imperative that someone using these methods is extremely diligent in cross-checking image MD5 signatures after it has been transferred to the SD card. Amon_RA also has the "md5sum" utility built into it's shell, BTW.
I mention this last point as a warning to newbs - they seem to routinely corrupt files when they transfer them to the SD card. (I suppose they are not using the "safely remove hardware" controls correctly, or they are getting truncated downloads).
bftb0
I rooted my thunderbolt. After flashing clockwork mod, I downloaded the rom of my choosing. Then when booting to recovery to flash the rom, I get kicked to the bootloader. Help!??!?
Ps: It seems its that clockwork mod wont take even though rom manager says flashed sucessfuly
EDIT: I did some more investigation and after redoing this
"Step 5
Next, enter the following commands:
adb shell
/data/local/psneuter
To unlock eMMC:
adb shell
/data/local/wpthis
exit
Step 6
Please pay attention – this is very important. This step involves a small chance of bricking if you mess up.
To push the eng bootloader:
adb push hbooteng.nb0 /data/local/
adb shell
/data/local/busybox md5sum /data/local/hbooteng.nb0
If the output does not match "6991368ee2deaf182048a3ed9d3c0fcb" exactly, stop, delete it, and re-download it. Otherwise, continue.
Now we will write the new bootloader.
dd if=/data/local/hbooteng.nb0 of=/dev/block/mmcblk0p18
Confirm proper write:
/data/local/busybox md5sum /dev/block/mmcblk0p18
If the output does not match "6991368ee2deaf182048a3ed9d3c0fcb," try again; if it still doesn’t work, seek help from chat.andirc.net in channel #thunderbolt. DO NOT REBOOT.
Now, reboot your phone and put the custom RUU (PG05IMG.zip) on your SD card. Then flash it. This will upgrade you to release firmware with an S-OFF bootloader.
Next, run this command:
adb reboot bootloader
After it flashes, you will be running release firmware with S-OFF."
I have working recovery with S-Off. Just thought I would update incase this happens to anyone else
I'm having the same issue after rooting but I used the one click process. Guess at this point I should just try to go.throughit again? Or should I go.through adb and follow your steps?
Thanks you!
Nevermind
Sent from my ADR6400L using XDA App
hi,my htc got stuck logo.i format my desire z with no backups.i unlocked bootloader with htcdev.com........temp root.....S-on..........nothing flashing any Rom...neither custom roms..Nor default roms.....plzzzz help....only fastboot is working....no adb.....plzzzzzzzzzz heellppppppp
klassikkamii said:
hi,my htc got stuck logo... ....only fastboot is working....no adb.....plzzzzzzzzzz heellppppppp
Click to expand...
Click to collapse
Hello,
I am not sure If someone can help in this case.
Please provide more information.
* Do you confirm, that you cannot boot in recovery from HBOOT?
* What is your exact HBOOT version? Do you have an "Engineering HBOOT"?
When only fastboot is working then I only see a little chance for your phone when you have an engineering HBOOT.
Best regards,
Catherall
P.S: Seems like you really tortured you helpless Desire Z
thxx for reply......i try to provide in detail.
* Do you confirm, that you cannot boot in recovery from HBOOT?
yes , i can boot in recovery-clockwork-3.0.2.4-vision.
* What is your exact HBOOT version? Do you have an "Engineering HBOOT"?
No i think i am on stock hboot but i dont know indeed.
More Detail are,
My Hboot Screen shoes it.
****Unlocked****
Vision pvt ship S-on
HBoot-0.85.0015
Microp-0425
Radio-26.10.04.03_M
emmc-boot
Dec 20,2011,16:21:13
Also,should know.i installed Clockwork Recovery.which is working perfectly.when i flash rom it all goes success.but when i reboot with hope ,stuck in logo.i flashed Villision1.0 ,Android_Revolution_HD-4G_7.0.3,C7 succesfully but never start normally just stuck in logo.i use also fastboot flash boot boot.img as well but nothing happened.same stucking.when i use adb commands or adb shell ,getting error device not found.plzz give me back earlier position as company setting it was gingerbread 2.3.3.
i am sorry abount my low english language capabality.
Get your phone back on track with proper unlocking (S-OFF)
klassikkamii said:
thxx for reply......i try to provide in detail.
* Do you confirm, that you cannot boot in recovery from HBOOT?
yes , i can boot in recovery-clockwork-3.0.2.4-vision.
* What is your exact HBOOT version? Do you have an "Engineering HBOOT"?
No i think i am on stock hboot but i dont know indeed.
My Hboot Screen shoes it.
****Unlocked****
Vision pvt ship S-on
HBoot-0.85.0015
Microp-0425
Radio-26.10.04.03_M
Also,should know.i installed Clockwork Recovery.which is working perfectly.when i flash rom it all goes success.but when i reboot with hope ,stuck in logo.
Click to expand...
Click to collapse
Two things are not clear to me:
1) How did you "unlock" you phone, did you use http://htcdev.com/bootloader/ method to get "****Unlocked****" in HBOOT? This is important to know for me.
When you indeed unlocked using http://htcdev.com/bootloader/ method, then you have to install an suitable "boot.img" every time you flash a new ROM.
Otherwise the old boot.img tries to boot the old ROM that was overwritten with the new one you flashed.
2) When you can boot ClockworkMod Recovery then you can connect using adb. Just use adb while booted into your custom recovery.
I really recommend to proper unlock your HTC Desire Z as described in
http://goo.gl/aXNr
The advantage of this method is, that you can flash any custom ROM without the need to flash the kernel of the ROM (boot.img) separately!
ATTENTION: Before doing anything like "fastboot oem lock"
you have to use "misc_version 0.1" and "flashgc". Do not continue without that!
When you do not know how to use that then ask (here or in freenode IRC channel #G2ROOT)!
Then you can go on to downgrade your phone:
[GUIDE] Downgrade G2 (2.3.X) & DZ (2.3.X) & mT4g (2.3.4) & DHD w/ S-ON to Stock Froyo
http://forum.xda-developers.com/showthread.php?t=1178912
Please make sure that you follow the steps described under the topic ***If you have used the "official" htcdev.com unlock option***
Then you can gain S-OFF (real unlock) using gfree
If you have questions then come to the awesome freenode IRC channel #G2ROOT.
Best regards,
Catherall
yes i unlocked with htcdev.com,so i will lock it again with "fastboot oem bootlock" command and will try to unlock as your advice.
i am so happy after seeing your advices.and i didn't know that i can use adb shell in recovery.you mean boot in recovery than use adb terminal from pc.ok i check it and try to apply it.and thankyou very much again for your help.
I will tell you results.
Attention
Before using fastboot oem lock make sure that downgrade would work.
Run the commands "misc_version 0.1" and "flashgc" successfully before doing anything like
fastboot oem lock!
Visit freenode IRC channel #G2ROOT
I am not 100% sure what happens on your semi-bricked phone with fastboot oem lock!
Best regards,
Catherall
one more plzz
ok i will make sure but plzzz tell me can i restore officialy stock rom with adb support ( may be with golcard support ) sothat i dont wanna take any risk.no downgrade,no s-off just my previous position.
I went to #G2Root but i didnt understand how talk anybody.i am not familiar on that.again thxx for your attention for me.
P.E : ok i tried adb commands while booted in recovery. adb devices command works and show serial number, but when i command ' adb shell ' got " # " instead " $ " so stuck again need more advice plzzzzzzzzzzzz.how can get " $ "
PLssss Help
i am getting " ~ # " Error in adb shell please helppp....
Options for S-OFF/root or reverting to Stock
Hello klassikkamii,
most custom Recoveries provide root access when you use "adb shell" to connect to them.
So adb shell returns "#" to indicate root access. When you get the prompt "$" then you have access as a user.
I would do the following steps. They allow you to get full S-OFF, Engineering HBOOT and a ROOTed ROM, or if you prefer return to stock ROM.
Returning the latest stock is much easier and safer when you do the following steps to change the internal software version number of the phone an make your SD card a goldcard.
Download misc_version 0.1:
http://forum.xda-developers.com/attachment.php?attachmentid=661216&d=1311237785
Download flashgc:
http://forum.xda-developers.com/attachment.php?attachmentid=819704&d=1324116910
And then use the following procedure to change version number and make a goldcard (as provided by Setherio in his guide [GUIDE] Downgrade G2 (2.3.X) & DZ (2.3.X) & mT4g (2.3.4) & DHD w/ S-ON to Stock Froyo:
1) Unzip misc_version_01.zip and flashgc.zip in the platform-tools directory.
2) Run the following commands from you platform-tools directory:
Code:
adb shell mount /data
adb push misc_version /data/local/tmp/misc_version
adb push flashgc /data/local/tmp/flashgc
adb shell chmod 777 /data/local/tmp/*
adb shell
Now you are in the phone shell with root access (indicated by the prompt "#").
Continue with the commands:
Code:
cd /data/local/tmp
./misc_version -s 1.00.000.0
This should return:
--set_version set. VERSION will be changed to: 1.00.000.0
Patching and backing up partition 17...
Continue to make you SD card a goldcard:
Code:
./flashgc
Note: If you get the following error, please make sure your sdcard is inserted in your phone: Error opening backup file.
Continue with the command
Code:
sync
Double check that you phone's software version number is set to 1.00.000.0 with the command:
Code:
dd if=/dev/block/mmcblk0p17 bs=1 skip=160 count=10
The first line of the command output must be:
1.00.000.010+0 records in
Exit the phone's shell with
Code:
exit
From here you can get an Engineering HBOOT and a custom, rooted ROM, or revert to a stock ROM. Both ways are about the same effort.
Please post how this worked out for you.
Best regards,
Catherall
still stuck
adb push misc_version /data/local/tmp/misc_version
Getting Error
failed to copy 'misc_version' to /data/loca/tmp/misc_version :Not a directory
As i am already with "~ #" i try direct command :cd /data/local/tmp
Got Error This :/sbin/sh: cd:can't cd to /data/local/tmp
if i use command for sd card,
adb push misc_version /Sdcard/misc_version
it show size of file or push succed but not in local/tmp.
i think if i would get "$" instead " ~#" May be i can do all u advice me.
Better do it interactive
Hello,
there might be several reasons why the command did not work.
Not having "$" is none of them.
Please come to freenode IRC and login to channel #G2ROOT. Ask for Catherall, I should be there for the next hours. When I am not there then check back later.
Best regards,
Catherall
ok i solved all Puzzle.solution was only use " GoldCard Method".i use command mmc2 instead mmc1 and voilaaaaaa i got my CID then everything was eassy.....in the End i really thanks to Catherall,You help me well...your information was helpfulln from your instructions i got my way thanksssss...
Guys,
I need help. I tried to work the solution myself and spend days reading different forums and tried different tricks but no luck.
So basically I was asked by my wife to root her Hero as she wanted a higer version of Android to install Viber and some other programmes. I did that using instructions on a Cyanogenmod wiki and everything went fine. However the new rom made the phone a bit slow and clumsy, so I thought I'd look for a different older version that works. I tried numerous roms and they all for some reason were not suitable - either wouldn't boot or were force closing etc...
So at the end of the day I read somewhere that for some ROM you need to install a CWM recovery and I was running a RA 1.7. So I tried to download a newer version of a recovery (to be honest I forgot which one - it was a week ago) and I flashed it and then I realised I have installed a recovery for CDMA and I have a GSM.
So, currently the phone boots and gets stuck at the HERO logo forever. There is no way I can boot into recovery. I have no problem to boot into fastboot, but any attempt to install a different recovery brings a failed signature error. I tried fastboot erase recovery and it did work, but no instalation is possible. When the phone is powered on and while on HERO logo I can run adb and can make it reboot from the command line, but when I try the instructions http://forum.xda-developers.com/showthread.php?t=1630519 I get past the first two lines:
Code:
adb push recovery-clockwork-2.5.0.7-hero.img /data/local/
adb push flash_image /data/local/
and then when I attempt this
Code:
adb shell chmod 777 /data/local/recovery-clockwork-2.5.0.7-hero.img
I get an error message
-exec /system/bin/sh failed no such file or directory
Please help!
PS. A screen shot in fastboot:
http://i3.photobucket.com/albums/y78/tsvet/fastboot.jpg
I managed to fix that with a stock rom and Hboot installation.
I was using a guide, https://forum.xda-developers.com/android/help/guide-how-to-lg-d-631-att-fastboot-t3130955, in hopes to use a custom recovery to restore my phone, it didn't take. Which lead to this problem.
During the process, I used ADB and inputed this command:
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
(I also ran this command to zero out the actual block partition)
dd if=/dev/zero of=/dev/block/mmcblk0p15
So I found this guide, after finding out that a tot file is the only way to restore.
https://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
I did well until the final part of step, which requires the phone to be in download mode. I realize the problem is that the phone is in fast boot instead of download/driver mode, and I have no idea how to switch it back.
Also, The fastboot reboot command does nothing, and it flatout rejects the reboot into bootloader command.