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!!
Related
Well, I guess I unintentionally softbricked my Hero...
So the story:
I downloaded via OTA the update. And i tried to install, but in the middle the install just stopped, and... stood still for a long long time... ok, battery ran out and i plugged the charger and tried to turn on ... annnd stucked at HERO sign...
i tried hard reset and nothing.. im trying that with the SDK and CMD and the fastboot devices doesn't show anything.
I tried to boot one of millions of customed ROMs and nothing, i guess i had to root earlier, or something /noob here.
I kinda ran out of options here and i don't know what to do...
Could you guys please help me out?
Taiwanese version of HTC Hero here.
yep, and i'm kinda desperate here too.
---
HERO CVT SHIP S-ON
HBOOT-1.76.0007 (HERO10000)
MICROP-010f
TOUCH PANEL-SYN0104
RADIO-6.35.08.29
Can you force into hboot/fastboot via holding volume down and power for a bit from cold start?
-------------------------------------
Sent via the XDA Tapatalk App
Yes, I Can access HBoot and fastboot...
aaaaaand i found my device at the fastboot devices.
HTxxxxxxxxxx64
Excellent then you should now be able to redo things ... let us know
OK, accessed the hero... then, tried to apply the update and...
E:Failure at line 11: run_program PACKAGE:checkspace -f /data 26214400 "ro.build.fingerprint=chunghwa/htc_hero/hero/hero:1.5CUPCAKE" FOTAERRORMESSAGES
actually i don't know what to do... :/
Try this ... http://forum.xda-developers.com/showpost.php?p=6714023&postcount=14
Basically go back into fastboot and try to install the official 1.5 (which will fail) but the process clears something up and allowed another member here to reflash cleanly ...
Try to wipe your data and then install the next ROM, i had the same problem
I do not think he has rooted or installed a modded recovery image if I read his first post correctly
i guess i had to root earlier, or something /noob here.
Click to expand...
Click to collapse
Yeah, i didn't root or anything... and i tried the other dude footsteps... and... blank, nothing...
and waiting for HTC Response team says something...
tried installing official rom, nothing.
tried updating the official update, also nothing.
tried wipe data, same thing.
well, i guess i have a new brick :/
If you can get it to fastboot ok and open the conversation, there must be something that can be done.
According to the definitive fastboot docs (http://android-dls.com/wiki/index.php?title=Fastboot) there might be a few options to try ...
HTML:
<pre>usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall 'flash boot' + 'flash system'
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline</pre>
Perhaps the -w to clear those areas might do it ...
Alternatively, I _believe_ you could flash the 1.62 recovery image to the phone in fastboot and then wipe from in there, or flash an 'update.zip' style rom from in here as well ...
Good luck, someone more knowledgeable than I may have other ideas ...
Broken Root???????
WELLLLLL...
I'm not sure how I did it, but I cannot open my custom recovery image. Happened a couple weeks after I flashed a new image. When I tried to apply an update.zip, the image froze at the 'opening update package' stage. I tried multiple roms and wipes to fix the problem, but none worked.
I've flashed multiple images through the terminal, and cannot open any. I've tried using flashrec again, but command line error always pops up. The error in fastboot when trying to load the image is as follows "Wrong or no image!"
This error reoccurs several times as the image recovery is attemped to be retrieved several times.
My rom is Darchdroid 262, and works 100%.
chachi said:
If you can get it to fastboot ok and open the conversation, there must be something that can be done.
According to the definitive fastboot docs (http://android-dls.com/wiki/index.php?title=Fastboot) there might be a few options to try ...
Click to expand...
Click to collapse
I was having a play with those commands yesterday to see if it was possible to restore to a ROM through fastboot but had no luck unfortunately.
chachi said:
If you can get it to fastboot ok and open the conversation, there must be something that can be done.
According to the definitive fastboot docs there might be a few options to try ...
HTML:
<pre>usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall 'flash boot' + 'flash system'
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline</pre>
Perhaps the -w to clear those areas might do it ...
Alternatively, I _believe_ you could flash the 1.62 recovery image to the phone in fastboot and then wipe from in there, or flash an 'update.zip' style rom from in here as well ...
Good luck, someone more knowledgeable than I may have other ideas ...
Click to expand...
Click to collapse
tried the fastboot -w and... not allow. I will try with the gold card.
Yeah, i'll try the 1.62, but the ADB don't find my device.
Try this,...
Go into fastboot on your phone.
Open CMD and type the following, obviously you will have to change slightly depending on where you extracted the sdk to.
cd c:\sdk\tools
fastboot oem rebootRUU
Then try running one of the 1.5 RUU .exe files on your pc/lappy.
ddotpatel said:
Try this,...
Go into fastboot on your phone.
Open CMD and type the following, obviously you will have to change slightly depending on where you extracted the sdk to.
cd c:\sdk\tools
fastboot oem rebootRUU
Then try running one of the 1.5 RUU .exe files on your pc/lappy.
Click to expand...
Click to collapse
i tried running one of the southeast asia RUU, the 2.73.728.5 file yesterday, and... nothing show up. Sayin' ive got to use the correct one.
The thing i thinked about is to rewrite the checksum in the update (the taiwanese 1.5 to 2.1 the one i've tried to update), verifying if its cupcake (in the fact that the update stopped in the middle), so if delete the verification code, it will continue the installation, and hopefuly, boot correctly.
-
update: ok trying to update again, then he says:
Error in checkspace (Status 256)
run_program PACKAGE:checkspace -f /data 26214400 "ro.build.fingerprint=chunghwa/htc_hero/hero/hero:1.5/CUPCAKE" FOTAERRORMESSAGES
Instalation aborted.
Click to expand...
Click to collapse
OK,... Now this,...
cd c:\sdk\tools
fastboot oem rebootRUU
fastboot erase cache
then try running the RUU again....... ?
Customer ID error... can't it erase the previous update?
it hasn't the original taiwanese RUU available?
the 2.73.751.13 file?
Customer ID Error?.... Ahaaaa,..... We might be on to something. Try with a goldcard now.
Use an old RUU with 1.5, not the new 2.1 ROM.
If you need to know how to make a goldcard follow BTDAGs guide linked in my signature.
ddotpatel said:
Customer ID Error?.... Ahaaaa,..... We might be on to something. Try with a goldcard now.
Use an old RUU with 1.5, not the new 2.1 ROM.
If you need to know how to make a goldcard follow BTDAGs guide linked in my signature.
Click to expand...
Click to collapse
This is beginning to sound like a happy ending is more than a remote possibility now
chachi said:
This is beginning to sound like a happy ending is more than a remote possibility now
Click to expand...
Click to collapse
Don't speak too soon, we might not be on to a winner just yet,.... Fingers crossed.
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...
Alright well i'm using the zedomax tutorial from htcevohacks. and i'm stuck at step Step 8:
Next, open up a command prompt and type:
cd \hbootdowngrade217
adb push misc_version /data/local/
adb shell /data/local/misc_version -s 1.10.651.2<<<<<now after i type that in i get Denied permissions.... WHY PLEASE HELP
adb reboot bootloader
fastboot getvar mainver
If you get back mainver: 1.10.651.2, you are good to go, go to the next step.
could anyone please help me with this
Spazzpyro said:
Alright well i'm using the zedomax tutorial from htcevohacks. and i'm stuck at step Step 8:
Next, open up a command prompt and type:
cd \hbootdowngrade217
adb push misc_version /data/local/
adb shell /data/local/misc_version -s 1.10.651.2<<<<<now after i type that in i get Denied permissions.... WHY PLEASE HELP
adb reboot bootloader
fastboot getvar mainver
If you get back mainver: 1.10.651.2, you are good to go, go to the next step.
could anyone please help me with this
Click to expand...
Click to collapse
Are you sure you are rooted?
well i'm using the directions for temp root... and when i go through that it says i am.. i'm relcocked hboot 1.5 s-on i re rooted it and then unrooted it again and tried this method again and i'm still getting the same thing
When u do adb shell, do u have $ or #?
cd \hbootdowngrade217
adb push misc_version /data/local/
adb shell /data/local/misc_version -s 1.10.651.2
adb reboot bootloader
fastboot getvar mainver
those are the codes i'm using if thats what u mean
Spazzpyro said:
cd \hbootdowngrade217
adb push misc_version /data/local/
adb shell /data/local/misc_version -s 1.10.651.2
adb reboot bootloader
fastboot getvar mainver
those are the codes i'm using if thats what u mean
Click to expand...
Click to collapse
No, I meant type adb shell and see if their is a # (meaning root) or a $ (meaning no root)
The downgrade thread here at xda made by unknownforce doesnt have that step anymore, its now in the last step. check it out its here
i got a # so i'm rooted i been looking on that thread
Are you giving that command while in android or recovey?
android
Is usb degugging on?
yeah
ok now i've got farther!!!! i think i was copy and pasting it thats why but now instead of it saying no permission or w.e its saying file not found... so whats the code i put in or file name? i got the hbootdowngrade217 file... in my root directory with the fastboot and adb...
ok nvm i'm back to square one same thing with no permission :-/
Did you go through steps again just to make sure you didn't miss a step
Try to restore with an official ruu. Download it and put it in your sd card. Let it boot and turn usb debugging on, then follow the instructions to temporarily root your phone and try again from there.
ONLY FOLLOW THIS GUIDE FOR WARRANTY REPLACEMENTS OR IF YOU NEED TO BE STOCK FOR A SALE. THERE IS NO OTHER REASON TO FOLLOW THIS GUIDE.
ALSO MAKE SURE YOU FOLLOW THE GUIDE PROPERLY. FAR TOO MANY ERRORS ARE BEING MADE BY NOT READING OR FOLLOWING STEPS IN ORDER.
This guide will help you get your phone back to stock after using any of the 5 S-Off methods that either have been or are currently available to us.
Credit to Scotty1223. I edited his One S guide for the DNA.
First post is for Facepalm and JTAG S-off only. RevOne instructions are in the second post. Moonshine and Rumrunner is in post 3.
***IF YOU HAVE A CUSTOM SPLASH SCREEN INSTALLED, THE STOCK SPLASH SCREEN MUST BE FLASHED BEFORE DOING ANYTHING! SEE FOURTH POST FOR LINKS AND INSTRUCTIONS FOR FLASHING THE STOCK SPLASH SCREEN***
***DO NOT ISSUE ANY OF THE WRITESECUREFLAG COMMANDS ON AN ENG HBOOT AS IT WILL BRICK THE DEVICE. JUST FOLLOW THE GUIDE.***
For those who want to return to stock and have used the JTAG method for achieving S-Off, this guide will also work for you. It all depends on what you did AFTER you got your JTAG phone back. If you wrote a new CID using fastboot and HTCDev unlocked, follow the guide as it is written out.
If you didn't write a new CID and use HTCDev unlock and just merely flashed a modified/ENG HBOOT, then the process would be: Fastboot flash stock hboot, RUU to stock, fastboot oem writesecureflag 3, then allow phone to update using the OTA process. You can find the commands/files/steps for these 3 simple steps below as well.
Files needed:
Lock bootloader zip: lock bootloader MD5: f335f78f9f46469c823da0c671026de5
3.06 RUU: 3.06 RUU
Steps:
1.Copy the "lock bootloader zip" onto root of internal storage and flash in recovery of your choice. Once it is flashed Reboot your phone.
2.Reboot into bootloader either using 4 in 1 power menu (if your ROM supports it). Or plug your phone into a USB port, turn on USB debugging and open a command prompt and type:
Code:
adb devices (Your device ID should be listed)
adb reboot bootloader
Verify you are **LOCKED** If not, re-flash the zip. If still not locked, try downloading the file again and re-flashing.
IF YOU ARE RUNNING ANY HBOOT THAT IS NOT THE 3.06 HBOOT (1.54 in bootloader), YOU MUST FLASH 3.06 HBOOT BEFORE CONTINUING - SEE POST 4
3. run the RUU as admin (right click, run as administrator)
4. After RUU completes and phone reboots, make sure usb debugging is on and in charge only mode and open cmd prompt
5. Run the following:
Code:
adb devices (your device should be listed)
adb reboot bootloader
fastboot devices (your device should be listed)
fastboot oem writecid VZW__001 (2 underscores)
fastboot reboot-bootloader
fastboot getvar cid (verify your stock CID)
fastboot oem writesecureflag 3
fastboot reboot-bootloader
*verify you are locked s-on
fastboot reboot
Should now be 100% stock, S-ON, with CID 100% stock as well.
Returning to stock from RevOne
It is pretty much the same process, but with a slight deviation.
AGAIN, IF YOU HAVE A MODIFIED/ENG HBOOT, DO NOT ISSUE ANY WRITESECURE FLAG COMMANDS. JUST FOLLOW THE GUIDE.
First, download these two files:
Files needed:
Lock bootloader zip: lock bootloader MD5: f335f78f9f46469c823da0c671026de5
3.06 RUU: 3.06 RUU
Steps:
1.Copy the "lock bootloader zip" onto root of internal storage and flash in recovery of your choice. Once it is flashed Reboot your phone.
2.Reboot into bootloader either using 4 in 1 power menu (if your ROM supports it). Or plug your phone into a USB port, turn on USB debugging and open a command prompt and type:
Code:
adb devices (Your device ID should be listed)
adb reboot bootloader
Verify you are **LOCKED** If not, re-flash the zip. If still not locked, try downloading the file again and re-flashing.
IF YOU ARE RUNNING ANY HBOOT THAT IS NOT THE 3.06 HBOOT (1.54 in bootloader), YOU MUST FLASH 3.06 HBOOT BEFORE CONTINUING - SEE POST 4
3. run the RUU as admin (right click, run as administrator)
4. After RUU completes and phone reboots, make sure usb debugging is on and in charge only mode and open cmd prompt
5. Run the following:
Code:
adb devices (your device should be listed)
adb reboot bootloader
fastboot devices (your device should be listed)
fastboot oem writesecureflag 3
fastboot reboot-bootloader
*verify you are locked s-on
fastboot reboot
You are now out of box stock.
Return to stock on Moonshine, Rumrunner and Firewater S-Off
Files needed:
Lock bootloader zip: lock bootloader MD5: f335f78f9f46469c823da0c671026de5
3.06 RUU: 3.06 RUU
Steps:
1.Copy the "lock bootloader zip" onto root of internal storage and flash in recovery of your choice. Once it is flashed Reboot your phone.
2.Reboot into bootloader either using 4 in 1 power menu (if your ROM supports it). Or plug your phone into a USB port, turn on USB debugging and open a command prompt and type:
Code:
adb devices (Your device ID should be listed)
adb reboot bootloader
You are locked. The s-off process removes the flag from displaying, but it is now locked.
IF YOU ARE RUNNING ANY HBOOT THAT IS NOT THE 3.06 HBOOT (1.54 in bootloader), YOU MUST FLASH 3.06 HBOOT BEFORE CONTINUING - SEE POST 4
3. run the RUU as admin (right click, run as administrator)
4. After RUU completes and phone reboots, make sure usb debugging is on and in charge only mode and open cmd prompt
5. Run the following:
Code:
adb devices (your device should be listed)
adb reboot bootloader
fastboot devices (your device should be listed)
fastboot oem writesecureflag 3
fastboot reboot-bootloader
*verify you are locked s-on
fastboot reboot
You are now out of box stock.
FLASHING THE STOCK HBOOT:
*Credit to .torrented*
1. download 3.06 HBOOT: 3.06 HBOOT
2. Rename stock hboot file to : PL83IMG.zip and place in the folder that contains your fastboot.exe file (On your computer)
3. Flash hboot
Code:
Step 1) adb reboot bootloader
Step 2) fastboot oem rebootRUU
Step 3) CD to directory containing hboot zip (i.e. cd C:\sdk\)
Step 4) fastboot flash zip PL83IMG.zip
*** When it says it is done in the terminal/cmdprompt execute the following ***
[The green bar only fills up about 75% of the way]
Step 5) fastboot reboot-bootloader
Flashing the Stock Splash Image
*All credit goes to E.T.Heil
1. Download the stock splash image here.
2. Rename file to splash1.img
3. Place the file in the same folder you have adb.exe and fastboot.exe located.
4. Plug in your phone to a USB port, turn on USB debugging and open a command prompt. cd to the directory your adb/fastboot is located
5. Run the following:
Code:
adb devices (your device ID should be displayed)
adb reboot bootloader
Once in the bootloader, run:
Code:
fastboot flash splash1 splash1.img
Once complete, reboot the phone using the menu or
Code:
fastboot reboot
updated with RevOne and Moonshine...
If anyone sees anything I missed let me know. Otherwise guide is complete.
Thank you so much for making this post. This is exactly what I needed. I am not quite sure which method I uses but it was the first one that required changing the CID, unlocking via htc dev and all that stuff. Would that be facepalm? Sorry if this is a dumb question, it was so long ago that I don't quite remember.
Imacellist said:
Thank you so much for making this post. This is exactly what I needed. I am not quite sure which method I uses but it was the first one that required changing the CID, unlocking via htc dev and all that stuff. Would that be facepalm? Sorry if this is a dumb question, it was so long ago that I don't quite remember.
Click to expand...
Click to collapse
Yes that was the Facepalm method. So follow the OP guide for that.
I love you! (no homo).
when i run RUU i get error 155 so i tried to flash the 1.15 hboot and i get this error in cmd
D:\Documents and Settings\Jonathan\My Documents\HTC\adt-bundle-windows-x86-20130
219\sdk\platform-tools>fastboot flash zip PL83IMG.zip
sending 'zip' (2047 KB)...
OKAY [ 0.375s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 0.562s
am i doing something wrong? i want to get my phone back to complete stock because i flashed a rom after moonshining without making a backup first. so i really want to get to stock so i can do the whole process over again (moonshine again if needed)
Prodiigy said:
when i run RUU i get error 155 so i tried to flash the 1.15 hboot and i get this error in cmd
D:\Documents and Settings\Jonathan\My Documents\HTC\adt-bundle-windows-x86-20130
219\sdk\platform-tools>fastboot flash zip PL83IMG.zip
sending 'zip' (2047 KB)...
OKAY [ 0.375s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 0.562s
am i doing something wrong? i want to get my phone back to complete stock because i flashed a rom after moonshining without making a backup first. so i really want to get to stock so i can do the whole process over again (moonshine again if needed)
Click to expand...
Click to collapse
Possibly a bad download, Download the HBOOT again and give it another go.
Also, with that error you are getting during the RUU process, did you lock the bootloader back up before running the RUU? That error sometimes shows up from not doing that.
I don't know if this will help anyone or not, or if this was known and I was just being stupid, but I was getting the ERROR [155] as well when running the RUU and I knew my hboot was correct as well as locked so that wasn't the problem, so I attempted to run the RUU again and saw that it was saying my current version was 1.28.xxxxxx which made me realize that that was the Sense 5 roms version number and not the actual version number of my phone causing it to fail. What I then did was i downloaded an AOSP based rom (but I would surmise that a sense 4 DNA rom would work as well) and flashed that then tried again. After doing that it showed the correct version number in the RUU and processed correctly!!
For a little more in site I was on the following setup:
Moonshine S-OFF
Joelz Stock Sense 5 <-- What caused the Error 155
Carbon ROM (Built by Pio) <--- What fixed the error (Would work with any AOSP or Sense 4 Rom ***Needs tested***)
**Edit**
Also incase anyone was wondering I was doing this to fix my phones radio, for some reason when flashing certain roms it gets stuck in Roaming no matter what you do. To fix it I just take my phone completely back to stock S-ON etc, then go into the bootloader and hit factory reset with the stock recovery and it seems to fix it, then S-Off and unlock again and go about my business. I couldn't actually find an answer besides "RMA the thing" to fix the radio roaming issue, so i figured i'd add that incase anyone else was/is in the same boat.
Hmm... I'll do a bit of testing on that with random Sense 5 vs AOSP/Sense 4 ROMs. If that is the case, I'll edit the guide.
I successfully restored my droid dna to untouched stock with this method. I had to exchange my DNA for a new one due to problems I was having and I am trying to do everything I can to make sure that there is no evidence of my tampering. One thing someone mentioned was to take the OTA's to get the device up to current 2.06 since I have been rooted and such since the first day it was available and am on 1.15. I have tried manually checking for software updates and it doesn't seem to find anything. It hasn't prompted me yet and I am wondering if because I am so far behind if they update system isn't checking or something else it wrong. Any thoughts? Any ways to manually update to 2.06 like flashing a new RUU (if that exists)? Thanks.
Just leave the phone on... I did it a few weeks back. It will eventually update.
Phaded said:
Just leave the phone on... I did it a few weeks back. It will eventually update.
Click to expand...
Click to collapse
Thanks. Verizon is only giving me 5 days to ship it back haha. So I just wanted to figure it out as quickly as possible.
Confirmed that on Sense 5 ROMs it randomly errors out. Editing guide.
I flashed the hboot zip and the hboot version is1.33 The phone is s-off and locked on viper rom. The RUU will reboot the phone into the black screen with the silver HTC logo, then the RUU stops working and asks to close the program. I downloaded three times and checked the md5 each time and its good. I am stuck. Any suggestions?
gris1016 said:
I flashed the hboot zip and the hboot version is1.33 The phone is s-off and locked on viper rom. The RUU will reboot the phone into the black screen with the silver HTC logo, then the RUU stops working and asks to close the program. I downloaded three times and checked the md5 each time and its good. I am stuck. Any suggestions?
Click to expand...
Click to collapse
The RUU itself crashes on the computer or the phone crashes and reboots?
Also the hboot I have linked should give you version 1.31 I do believe.
Thanks for this, worked perfectly!
Phaded said:
Return to stock on Moonshine S-Off
First, download the stock RUU
Stock RUU: 1.15 RUU: Mirror #1 or Mirror #2
Plug your phone into a USB port, turn on USB debugging and open a command prompt. cd to the directory that has adb/fastboot.
**NOTE** I noticed on the XDA mobile app that it breaks the echo command line up and makes it look like 2 separate commands. Do not separate it. The command starts at echo and ends at 33796.
Run:
Code:
adb devices (verify device ID is listed)
adb shell
su
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
exit
Your bootloader is now locked. Lets verify...
Reboot into bootloader either using 4 in 1 power menu (if your ROM supports it). Or plug your phone into a USB port, turn on USB debugging and open a command prompt and type:
Code:
adb devices (Your device ID should be listed)
adb reboot bootloader
Verify you are **LOCKED**
Click to expand...
Click to collapse
I am having issues not getting the phone to return to "Locked" status. I have and am running the stock ROM. Just reset back to factory. I am following the commands to the T. Below is what my CMD prompt shows that I typed in, or copied and pasted for the echo command. I was trying to follow the note about the echo command but I could see nothing wrong with it... also in the end I had to type exit command twice for it exit and go back to the prompt for the next folder.
C:\android-adb>adb devices
List of devices attached
FA2C2S510423 device
C:\android-adb>adb shell
[email protected]:/ # su
su
[email protected]:/ # echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 s
eek=33796
d of=/dev/block/mmcblk0p3 bs=1 seek=33796 <
4+0 records in
4+0 records out
4 bytes transferred in 0.007 secs (571 bytes/sec)
[email protected]:/ # exit
exit
[email protected]:/ # exit
exit
C:\android-adb>
Click to expand...
Click to collapse