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...
Related
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
ok so i was messing around and i was trying to get fastboot to work but i failed i ended up flashing and unknown pb00img file and know i have s-off (kinda what i wanted) no recovery a stock rom that i cant use (cant get past setup ) also my sdcard is corrupted i dont know for sure if i still have root but i can use adb and shell when the phone is booted but when i enter recovery i just see a triangle with a ! but adb dose see my device from there but i can enter shell so i dont think i can mount system at all i have tried to push a recovery to /data/local the flash it but when i gave the command inside shell flash_image /data/local recovery.img i get cant find or something any help would be awesome
thanks
Can you get into HBOOT by starting the phone holding VolDn? If you can, also confirm the exact hboot version (it should be 1.49.2000 S-OFF if you truly have S-OFF.)
yes i can enter hboot and you are correct it is 1.49.2000 S-OFF
if it helps
pb0010000
radio-2.40.00.01.22
also i no longer have the old options like simlock and clear storage now its only
fastboot (cant get to work)
recovery (adb yes shell no) thanks for the help
kylejjjjj said:
yes i can enter hboot and you are correct it is 1.49.2000 S-OFF
if it helps
pb0010000
radio-2.40.00.01.22
also i no longer have the old options like simlock and clear storage now its only
fastboot (cant get to work)
recovery (adb yes shell no) thanks for the help
Click to expand...
Click to collapse
So, if you go into hboot I believe that there is an option to press "Send" to enter fastboot. That does not work? Or do fastboot commands not work when you do that? (Fastboot commands generally not work unless you are in fastboot mode on hboot.)
Also, make sure that your phone's battery is well-charged when you try going into hboot. Hboot, as I understand it, eats the battery and will not charge the battery when you plug in in that mode.
Once you get into fastboot (and the phone responds to the "fastboot devices" command) getting recovery on there is possible.
i had trouble with windows 7 and fastboot but know im in ubuntu so its all cool i flashed a new recovery from there i with format my sd card then i will upload a new rom and flash it ya so now i have 1.49.2000 S-OFF and and amon ra recovery with gsb running yaa now all i need it service aunt disconnected it :,(
thank you so much for the help its hard when everyone you know has not a single idea what your saying when your talking about things like this
forums are my saviors
WARNING: This procedure applies to View only
If you are S-OFF on honeycomb, do not under any circumstances run this procedure.
Don't bother asking for help if you try to do this on a virtual machine, you won't get any
run on a real machine.
If you updated using the Official OTA and want to downgrade to GB this is the procedure you want.
Perform a HTC unlock using the HTC unlock website
Download this recovery MD5: cb0683f249e6ad2d754949719104c1a8
Boot the view to fastboot mode
Flash recover
Code:
fastboot flash recovery cwm-4.0.1.4-express-HC.img
Reboot to recovery
Proceed with the downgradre procedure below.
Downgrade
First download the RUU for the view: (Download here) (Zip version for Linux/MacOS)
Download and extract misc_version from this file
From the screen on the view, select "Mounts and storage->Mount sdcard"
Run the following commands:
Code:
adb push misc_version /
adb shell chmod 777 /misc_version
adb shell /misc_version -s 1.22.651.1
You will see a message about backing up and patching partition 29
Reboot to fastboot:
Code:
adb reboot bootloader
[*]Relock the bootloader:
Code:
fastboot oem lock
Run the RUU
How to run RUU for Linux/MacOS:
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip RUU_Express_Sprint_WWE_1.22.651.1_Radio_1.05.11.0531_NV_2.28_SPCS_release_198141_signed.zip
[color=blue][i]You will get error 90 after this first flash, so flash again[/i][/color]
fastboot flash zip RUU_Express_Sprint_WWE_1.22.651.1_Radio_1.05.11.0531_NV_2.28_SPCS_release_198141_signed.zip
At this point you can perform a Revolutionary S-OFF and re-upgrade to Honeycomb with S-OFF if you so wish.
Reserved for me.
Also reserved for me
Globaltron
I think I will need your help regarding this now... I'm stuck at the situation where I will have to go back to the stock GB as somehow my copy of HC is bad and a restore/recovery is impossible (somehow a mismatched MD5), now I'm stuck the recovery as I am not sure if the GB would work on a HC HBoot.
What exact hboot do you have?
Procedure added.
globatron said:
At this point you can perform a Revolutionary S-OFF and re-upgrade to Honeycomb with S-OFF if you so wish.
Click to expand...
Click to collapse
On your "[View]S-OFF Honeycomb, Custom recovery, root" topic, you wrote:
globatron said:
Do not perform this procedure if you are HTC unlocked, it will not work
Click to expand...
Click to collapse
So how would I upgrade to S-OFF Honeycomb, if one of the steps for HC->GB downgrade is to use the HTC unlock? Or is step 5 ("Relock the bootloader") undoing the HTC unlock?
Step 5 covers that.
globatron said:
Download this recovery download MD5: cb0683f249e6ad2d754949719104c1a8
[*]Boot the view to fastboot mode
[*]Flash recover
Code:
fastboot flash recovery cwm-4.0.1.4-express-HC.img
Click to expand...
Click to collapse
There is no "cwm-4.0.1.4-express-HC.img" in the compressed archive linked >.>.
ok, give me a sec...
EDIT: Fixed
Nice Job sir, Thanks for the development and share
Just a suggestion to Globatron:
When/if you build RUU for the downgrade, maybe it will be possible to check first whether the device is s-off in HC and if so, refuse to run.
Trying to save some support time.
Upon running the RUU, I get:
"ERROR [140]: BOOTLOADER VERSION ERROR - The ROM Update Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again."
What I did:
HTC Unlock (bootloader says ""UNLOCKED", and "S-ON")
Get into FASTBOOT, then:
Code:
C:\Android>fastboot flash recovery cwm-4.0.1.4-express-HC.img
sending 'recovery' (4712 KB)... OKAY [ 0.624s]
writing 'recovery'... OKAY [ 0.703s]
finished. total time: 1.328s
Then reboot bootloader, enter recovery (blue "REVOLUTIONARY" cwm), then:
Code:
C:\Android>adb push misc_version /
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
3581 KB/s (454748 bytes in 0.124s)
C:\Android>adb shell chmod 777 /data/local/tmp/misc_version
chmod: /data/local/tmp/misc_version: No such file or directory
C:\Android>adb /misc_version -s 1.22.651.1
Android Debug Bridge version 1.0.26
<bunch of how-to use ADB messages>
I think the problem is right there; what am I doing wrong?
Nothing it's my error, I mis-edited an update.
ok, updated now, also note the addition of step 3 ( you can run that at any point before the last command in step 4 )
globatron said:
Nothing it's my error, I mis-edited and update.
Click to expand...
Click to collapse
Code:
adb /misc_version -s 1.22.651.1
Running that just gives a massive "how to", such as (excerpt):
Code:
C:\Android>adb /misc_version -s 1.22.651.1
Android Debug Bridge version 1.0.26
-d - directs command to the only connected USB device
returns an error if more than one USB device is present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is running.
-s <serial number> - directs command to the USB device or emulator with the given serial number. Overrides ANDROID_SERIAL
And nothing about backing up / patching partition 29 >.>.
adb shell chmod 777 /data/local/tmp/misc_version
Question, after i run this command, I get No such file or directory.
Did i do something wrong?
Edit Sorry I see someone else already posted that
yea fixed...it's very late here so a few mistakes crept in. It should be all good now. I've gone back over it line by line this time.
Maine_Coon said:
Just a suggestion to Globatron:
When/if you build RUU for the downgrade, maybe it will be possible to check first whether the device is s-off in HC and if so, refuse to run.
Trying to save some support time.
Click to expand...
Click to collapse
Not possible to do it in that way, but yeah.
Thank you! It worked, and I am now back to Gingerbread =D.
OUTSTANDING!! Worked for me as well Thanks!!
Sinse a couple of weeks i'm tring differend methods to downgreade my HTC Legend, the result is 0, when i run the ruu a get error [170].
I already tryed Full updating guide from cyanogenmod, Unlockr's method and some others popular tutorials... and every time the downgreading fails !
From the HTCDev e tryed to unlock the bootloader of my device and of course i get another one(ERR) this time [191] ROM IS NOT SUPPORTED.
Whats wrong , just have no idea what to try, I just want to install cyanogenmod 7.1
My HBOOT version is 1.02 if its of importance
mister_president said:
Sinse a couple of weeks i'm tring differend methods to downgreade my HTC Legend, the result is 0, when i run the ruu a get error [170].
I already tryed Full updating guide from cyanogenmod, Unlockr's method and some others popular tutorials... and every time the downgreading fails !
From the HTCDev e tryed to unlock the bootloader of my device and of course i get another one(ERR) this time [191] ROM IS NOT SUPPORTED.
Whats wrong , just have no idea what to try, I just want to install cyanogenmod 7.1
My HBOOT version is 1.02 if its of importance
Click to expand...
Click to collapse
well if your hboot is 1.02 that means you have already updated your hboot. You just have to follow the instructions on htcdev.com.
pasanjay said:
well if your hboot is 1.02 that means you have already updated your hboot. You just have to follow the instructions on htcdev.com.
Click to expand...
Click to collapse
At step 9 the command prompt says <waiting for device> and nothing ... happens just like that http://forum.xda-developers.com/showthread.php?t=1392049
I forgot to say about this in the first post
If you get Error 170 just exit the RUU, leave the phone and restart the RUU. This happened to me.
Thanks for all, i'm done without downgrading using RUU ,thanks to android.mobility .bg , All what i needed was that :
* setted up adb
* testimage.zip from r4-legend-root.zip
* Hack 4 Legend v5
* VISIONary
And action:
1) adb shell
su
Install visionary and temproot the legend !
2) Open new ternimal window and unnzip the Hack 4 Legend somewere then pres Shift and R mouse button -open command window "here"
adb push flash_image /data/local/
adb push misc1-2.img /data/local/
3) chmod 755 /data/local/flash_image
4) cat /dev/mtd/mtd0 > /sdcard/misc_backup.img // not needed
5) /data/local/flash_image misc /data/local/misc1-2.img
exit
6) rename testimage.zip to LEGEIMG.zip and copy in the SD card
and update.zip (haven't permisssion to add url to update.zip) and some custom rom's zip .
Connect the your Legend again and run :
adb reboot bootloader and wait for checking the LEGEIMG.zip
After that turn off the device and boot in clockworkmod and install the custom rom
Just like title says. I cant access the bootloader or anything else besides fastboot. I just s-offed with the wire trick and it says "locked" at the top. Please help thanks
gearlo said:
Just like title says. I cant access the bootloader or anything else besides fastboot. I just s-offed with the wire trick and it says "locked" at the top. Please help thanks
Click to expand...
Click to collapse
You're at the bootloader right now. Use fastboot to flash the recovery and boot.img you were using before the s-off (controlbear makes a backup of it automatically so look in the folder it's in)
gearlo said:
Just like title says. I cant access the bootloader or anything else besides fastboot. I just s-offed with the wire trick and it says "locked" at the top. Please help thanks
Click to expand...
Click to collapse
I had the same issue. Fixed it using the steps from this page. Step 1 is all I had to do...
http://unlimited.io/juopunutbear-public-beta-0-1/troubleshooting/
ROM/Data Recovery
There are three ways to recover your ROM. Try each until one succeeds.
1. ControlBear -r (This is run with the phone at the JuopunutBear/Arrow screen). If this succeeds recovery is complete otherwise continue to step 2.
2. ControlBear -f (This is run with the phone at the fastboot screen). If this succeeds skip to step 4 otherwise continue to step 3.
3. fastboot flash boot boot_backup.img
4. fastboot flash recovery recovery_backup.img
This is done with the phone in fastboot mode, continue to step 4.
5. Boot the phone to android and install busybox from the market if not already installed.
6. adb push sdcard.img /data/local/tmp/
7. adb shell
8. $ su
9. # busybox dd if=/data/local/tmp/sdcard.img of=/dev/block/mmcblk1 conv=notrunc
10. Reboot the phone.