Root Need help getting back to stock

[hoamskilet]

I need some help getting my rezound back to stock so i can send it in since i got a replacement phone.

Quick background......Using resources here I had no trouble unlocking my phone and flashing a rom. Everything worked fine until my phone started acting up by not making any external noises (wouldn't ring out loud, play music, notifications, etc....). I think it's a hardware issue but Verizon wouldn't touch it without being put back to stock. I got a replacement phone via insurance, but i still need to get the old one back to stock so i can send it back.


I must have missed something along the way because I've got it re-locked, but now I can't get past the bootloader screen. Any option I pick from there results in it going to the black screen with the triangle/red exclamation point. For some reason now I can't access it/do anything via the command prompt screen (which obviously I have the drivers installed since I unlocked originally and recently used the command prompt to relock) and for some reason I can't get the phone to recognize any ph98img file on the external SD card.

I'm pretty much completely stuck right now and just wanna run the thing over with my car. Any help would be greatly appreciated

 

[scotty85]

you can re-unlocke it if you need to,to use recovery or get back to an OS.

in a nutshell,you just need to lower the main version,relock the bootloader,then run an ruu.

some more specific directions here: http://androidforums.com/rezound-al...ndly-root-guide-start-finish.html#post3997776

 

[kitcostantino]

you can re-unlocke it if you need to,to use recovery or get back to an OS.

in a nutshell,you just need to lower the main version,relock the bootloader,then run an ruu.

some more specific directions here: http://androidforums.com/rezound-al...ndly-root-guide-start-finish.html#post3997776

I am completely new to the Rezound world, and have spent the last few days reading up on the Rezound and have read many of your posts, Scotty. I have a Rezound that had the last stock ota installed. I flashed twrp as a recovery. then my battery got low and it wouldn't charge. finally, I found your root thread (fastboot installing amon ra.) and fixed it. thank you for that. currently, i'm running infected (flashed the boot img for it after install to get kernel goodies) and I am wondering how to get back to stock so I can do the s-on flashing method you describe AND be able to put it to stock for selling it. my recovery is still amon ra. my hboot should still be .27 and I have the full ~600 mb ruu. (checked it 5 times or so). I have your mini-adb_rezound set up fully (used it to flash amon ra). I *think* I need to relock, get stock recovery (can't find a link), change the version number, flash the ruu, and profit. likely though, I will re-root using your guide and set it up to flash full roms without having to flash the boot.img separately. am I missing anything, man? the phone functions perfectly on cm 10.1 . I have a stock backup from twrp backup but I figure it probably won't work with amon-ra I imagine) it would be messed up AT LEAST as bad as it was originally. thank you for your work.

 

[acejavelin]

I am not sure I understand what you are trying to get at. It sounds like you are already on the latest firmware installed if you where on the latest OTA before you started... The recovery you have installed is a matter of choice, you should use the recovery recommended by the ROM developer to install the ROM, and if you use the "fastboot boot recovery.zip" method it doesn't matter what recovery you actually have installed.

What is the end result you are trying to get at? It looks like you have everything you need to get there...

Also, if you have an Amon Ra nandroid, you could always just fastboot boot Amon Ra and restore it, irregardless if you have TWRP or CWM as the installed recovery.

 

[scotty85]

I am completely new to the Rezound world, and have spent the last few days reading up on the Rezound and have read many of your posts, Scotty. I have a Rezound that had the last stock ota installed. I flashed twrp as a recovery. then my battery got low and it wouldn't charge. finally, I found your root thread (fastboot installing amon ra.) and fixed it. thank you for that. currently, i'm running infected (flashed the boot img for it after install to get kernel goodies) and I am wondering how to get back to stock so I can do the s-on flashing method you describe AND be able to put it to stock for selling it. my recovery is still amon ra. my hboot should still be .27 and I have the full ~600 mb ruu. (checked it 5 times or so). I have your mini-adb_rezound set up fully (used it to flash amon ra). I *think* I need to relock, get stock recovery (can't find a link), change the version number, flash the ruu, and profit. likely though, I will re-root using your guide and set it up to flash full roms without having to flash the boot.img separately. am I missing anything, man? the phone functions perfectly on cm 10.1 . I have a stock backup from twrp backup but I figure it probably won't work with amon-ra I imagine) it would be messed up AT LEAST as bad as it was originally. thank you for your work.

if you need to get back to 100% stock,relocked,you just need to relock,then run the ruu. no need for stock recovery.

you also do not need to go back to stock,then reroot to get the benefits of fastboot booting recovery for s on flashing.as was said above, at any time you can fastboot boot amon(or twrp for that matter) and flash a new rom. no need to run an ruu first.

if you fastboot booted amon to fix your charge prollem,then twrp is still installed. if you need to you can go back to amon and restore it. fastboot booting twrp will let you restore the kernel as well when you restore the backup.

hope that helps

 

[kitcostantino]

Thank you guys for responding. I guess I must have properly installed among race, because when I boot into recovery, it goes to amon ra. I think I DL amon-ra 3.15 and installed it. Really, I am just trying to grasp how to make the phone factory again (locked no tampered on boot) and trying to make sure I understand how to get back there. I had a of incredible, but for some reason all of it was easier. Twrp works right on it too. (Mic died, so its a kids toy running JB cm now) I was amazed to see the rezound was that much different. But I was stoked to see the main version tweak. If other phones were only that simple to downgrade. The super-simplified question would be what do I have to do before I relock and will I need anything else stock installed coming from a perm amon-ra recovery running aosp JB? or will it simply let me relock as is then run the ruu via boot? I think so from the answer above. Thanks guys!

 

[scotty85]

Really, I am just trying to grasp how to make the phone factory again (locked no tampered on boot) and trying to make sure I understand how to get back there.

running the ruu will remove tampered. unfortunately,youre stuck with relocked while s on. in order to to get back to locked youd have to run jpbears tool to s-off.

The super-simplified question would be what do I have to do before I relock and will I need anything else stock installed coming from a perm amon-ra recovery running aosp JB? or will it simply let me relock as is then run the ruu via boot? I think so from the answer above. Thanks guys!

that is correct. relock bootloader,run ruu. thats it. you can run a PH98IMG from the sd card(or from fastboot with the phone in RUU mode),or you can run a .exe on the PC with the phone in fastboot.

you do not need to do anything first,the ruu replaces images in all partitions with thr correct ones,so it doesnt matter what recovery or what rom youre running.

only thing out of place is the telltale relocked if youre still s on. otherwise,the ruu makes it 100% out of the box stock

 

[kitcostantino]

Scotty, you're the man. That's exactly what I was trying to figure out. Is the bear s-off risky difficult? Or are the people that have it screw up on them just doing something wrong? So far I have owned and rooted OG droid, OG INC, droid x, about 5 droid bionics, and now the rezound. The of droid root I used was my introduction to ADB (and this site). All ADV shell commands, etc. I'm no stranger to following directions to a T. But if it is a hit or miss randomly, it may not be worth s off. I just wish I had read about flashing s on via fast boot before I rooted using the all in one rezound toolkit. Takes a while with a new device to figure out who is the good source of information. you definitely hold that title with the rezound man. thanks.

 

[scotty85]

Scotty, you're the man. That's exactly what I was trying to figure out. Is the bear s-off risky difficult? Or are the people that have it screw up on them just doing something wrong? So far I have owned and rooted OG droid, OG INC, droid x, about 5 droid bionics, and now the rezound. The of droid root I used was my introduction to ADB (and this site). All ADV shell commands, etc. I'm no stranger to following directions to a T. But if it is a hit or miss randomly, it may not be worth s off. I just wish I had read about flashing s on via fast boot before I rooted using the all in one rezound toolkit. Takes a while with a new device to figure out who is the good source of information. you definitely hold that title with the rezound man. thanks.

the "wire trick" is a bit tricky,but not dangerous if you follow closely the directions(use an insulated wire,touch the correct points) ihave run the tool 2(or is it 3?) time on my own phone,done several friends rezounds,and done several other supported htc phones,including my jetstream tablet.

where folks have trouble,is they rush into it without haveing read or have open the troubleshooting tips,and panic if something goes wrong. generally,i believe things really only went wrong if people got tired of trying,or in the windows days if something screwed with the adb/fastboot connections.

only linux is supported now. if youre proficient in that,you wont need this: http://androidforums.com/rezound-al...me-pointers-running-juopunut-bear-ubuntu.html

otherwise it may come in useful. im definately not an expert in linux,so ifn i could do it,anyone should be able to

 

[kitcostantino]

soo...didn't run the main version tool...figured it didn't matter. kinda screwed myself. hboot is a newer version and the ruu is failing. (4.03.605.2) my hboot is .28. gonna try to fastboot fix it because I can't boot anything except fastboot. learning curves..

edit...removed sd card, reconnected and now flashing (hopefully) via all in one. (black htc screen grey htc letters...) unless it is just a brick.. hopefully this works. it did say it erased the boot. whoops..

well, signature fail again. do I try for s-off or do I try to push the main ver tool in a relocked state... I bet neither will work.

Gonna try this: Mainver problems? Not anymore!!

and this is the error output in cmd prmpt:
c:\mini-adb_vigor>fastboot flash zip PH98IMG.zip
sending 'zip' (631741 KB)... OKAY [ 57.939s]
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 145.252s

Well, looks like the "noob defeated" thead guy had the same issue as me hoping this stock rooted rom gets me bk on track.

 

[scotty85]

soo...didn't run the main version tool...figured it didn't matter. kinda screwed myself. hboot is a newer version and the ruu is failing. (4.03.605.2) my hboot is .28. gonna try to fastboot fix it because I can't boot anything except fastboot. learning curves..

edit...removed sd card, reconnected and now flashing (hopefully) via all in one. (black htc screen grey htc letters...) unless it is just a brick.. hopefully this works. it did say it erased the boot. whoops..

well, signature fail again. do I try for s-off or do I try to push the main ver tool in a relocked state... I bet neither will work.

Gonna try this: Mainver problems? Not anymore!!

and this is the error output in cmd prmpt:
c:\mini-adb_vigor>fastboot flash zip PH98IMG.zip
sending 'zip' (631741 KB)... OKAY [ 57.939s]
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 145.252s

Well, looks like the "noob defeated" thead guy had the same issue as me hoping this stock rooted rom gets me bk on track.

flashing the main version zip in recovery is far easier than modifying android info text documents. you also are not able to edit the document in a full,signed file from htc,as youve found,changing the document breaks the signiture.

unforutunately,it doesnt matter anyway. there is no way around the hboot check,it doesnt matter how low youve changed main version. above you said you were on hboot 2.27,wich i assumned meant you had arrived where you are by running the leaked ruu.

since youre on hboot 2.28,you need a new gameplan.

assuming you have a nandroid of your stock,most current OTAed rom(4.05.605.14):
1)re-unlock bootloader
2)boot wichever recovery you need to restore the backup
3)restore backup
4)s-off

alternately,you could flash a stock 4.05.605.14 rom. just make sure its stock,as the jpbear team is very clear about that requirement.

once youre s off,there are no hboot checks,so you could run the ruu for 3.14.605.5.and let the phone OTA back to current.

things are usually easily fixed with s off. not so much while s on

 

[acejavelin]

scotty85... so lets just suppose, for discussion purposes only, because nobody would actually do this (read "I did this, and I am an idiot"), that someone rooted, installed custom recovery, did a nandroid and forgot to move a copy off the sd card, then wiped everything multiple times including the SD card, was on the latest hboot 2.28 and now want to S-OFF. How would one go about returning to stock to S-OFF?

 

[scotty85]

just flash a stock rom. I'm on my phone, so I can't link it at the moment, but a couple threads down there is a thread called newest global rom. there is a link there.

 

[acejavelin]

just flash a stock rom. I'm on my phone, so I can't link it at the moment, but a couple threads down there is a thread called newest global rom. there is a link there.

Oh, well that is simple... I didn't think the latest ROM had an RUU yet, guess I was worried for nothing. I am very proficient in Linux, so S-OFF should be simple from that point. Might give it a shot this weekend if I get some free time.

 

[scotty85]

It's not an ruu... It's a Rom,that you flash in recovery

 

[kitcostantino]

flashing the main version zip in recovery is far easier than modifying android info text documents. you also are not able to edit the document in a full,signed file from htc,as youve found,changing the document breaks the signiture.

unforutunately,it doesnt matter anyway. there is no way around the hboot check,it doesnt matter how low youve changed main version. above you said you were on hboot 2.27,wich i assumned meant you had arrived where you are by running the leaked ruu.

since youre on hboot 2.28,you need a new gameplan.

assuming you have a nandroid of your stock,most current OTAed rom(4.05.605.14):
1)re-unlock bootloader
2)boot wichever recovery you need to restore the backup
3)restore backup
4)s-off

alternately,you could flash a stock 4.05.605.14 rom. just make sure its stock,as the jpbear team is very clear about that requirement.

once youre s off,there are no hboot checks,so you could run the ruu for 3.14.605.5.and let the phone OTA back to current.

things are usually easily fixed with s off. not so much while s on

well, i got the phone operational again by reinstalling Business ICS Sense after a complete wipe. Installed, booted, all good.
I love NilsP's roms. Been using them since the Samsung Omnia and really dug them on the OG Inc. To reflash to stock, I take it my only option is not to. Or to figure out how to re-sign the HTC RUU after I tweak it. I have one theory as to how to do that unconventionally, but perhaps android kitchen would be easier than a file-signing app. even at that, it it were that simple to hack the sig, someone way smarter and more knowledgeable would have done that by now. If I am on this rom, I imagine a mainver tweak isn't gonna do anything for me. I also found out the hard way, that as you say, my hboot is gonna stick me where I'm at until there is in fact a newer RUU. i wish i understood their numbering scheme (as the error was hboot version 13) enough to know if higher or lower was better. i tried 12 and I tried 14, but I am sure there has to be another way verifies. (probably in hboot itself.) At a loss on this one. at least it boots now.
I wish the Rezound had safestrap. Safestrap is a modified version of TWRP that allows a stock "slot" (partition} and up to 4 additional slots on the internal sd card. the stock is the no no zone...but is always kept intact so you can leave it unaltered to accept OTA's. the four additional slots are the wreckless-erase and install what you will till it won't boot slots. and if all else fails, battery pull, wait for the boot interrupting safestrap screen, press the menu button and boot into something else so you can wipe the offending partition. Hashcode is a smart dude. I don't know crap about writing scripts, apps, recoveries, etc. so maybe someone with those skills will decide to kang it for a port so to speak on the rezound. ironically, the first phone I read about with multi-boot capabilities was the OG INC. Thank you all for your help.

EDIT: Just read two posts above... just a stock rom to get s-off. is there an easier way to upgrade my old ubuntu (10.?) to 12.04 than making a live cd? (i read the instructions, and i know a usb instance won't work, but I actually have a dual boot setup with xp and ubuntu 10.?. Seems i can't upgrade it directly, but i REALLY don't know crap about ubuntu.

EDIT 2: this is my info pulled via aio rezound kit. and for the afore mentioned, im downloading ubuntu 12.04 now.

version: 0.5
version-bootloader: 2.28.0000
version-baseband: 2.23.10.012
version-cpld: None
version-microp: None
version-main: 2.01.605.11
serialno: HTxxxxxxxxx
imei: zzzzzzzzzzzzzz
product: vigor
platform: HBOOT-8260
modelid: PH9810000
cidnum: VZW__001
battery-status: good
battery-voltage: 3730mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: cecc19f7
hbootpreupdate: 11
gencheckpt: 0

looking at the hboot pre-update being 11, almost makes me think i could relock and flash the ruu i was trying to earlier, but hboot still registers on screen in fastboot 2.28.000000, so that's out.

so, is this legit?
http://www.teambamf.net/topic/3768-rezound-support-files-etc/ as in flash firmware, flash ruu, then you're stock? minus i think i would fastboot oem relock, right?

ah, may as well just s-off.

 

[scotty85]

in a nuutshell,the builds just get numerically higher is they progress:
-1.00.605.3(release firmware)
-1.02.605.6
-2.11.605.11
-3.14.605.12
-3.14.605.13(OTA to prepair for global)
-4.05.605.14

those above are the official "release keys" builds OTAed to phones. there are some leak that fit in between some of them. unfortunately,each one as included a new hboot,so you cant flash any of them with a main version change.

its also not so simple as resigning an ruu after you modify it. in order for an s on phone to flash official htc files,it has to have htc's official signiture.

you really are making this more complicated than you need to.

htcdev unlock is only letting you have access to boot,system,and recovery. so all you need to replace to get back to stock is boot,system and recovery. the thread mentioned a couple posts up( http://androidforums.com/rezound-all-things-root/716364-newest-global-rom.html ) will replace those partitions if you flash the firmware and rom,making you 100% stock. its a pretty good substitute for an RUU

you can then procede with s off if you wish,by making a live cd or updating your dual boot partition. the live cd process must not be that hard,ifn i figured it out its been quite a while since i did it,so i cant recal any of the details ATM.

safestrap sounds like something i personally wouldnt touch with a 10 foot pole ive still got a few forums to check,so i havent looked at your bamf link just yet.

im a fan of nils myself. good stuff. i also had(still have) and OG inc

imo,its well worth the efforts to s-off.

hope that has answered your questions.

 

[kitcostantino]

XHa. Yeah, i am. My curiosity has screwed me over a couple of times. i just didnt understand that flashing a stock rooted rom would replace everything. That is way easier. I dl'd that file and it got to the last %, had the full data size and hung, so really, i was just impatient. Ill re-download it now.

Safestrap kinda hoses the preinstall partition, but in all honesty, it is a ridiculously awesome, incredibly stable way to flash roms and tweak with little to no recourse. How-To Safestrap (Updated for v3.04) | Hash-of-Codes i was apprehensive about it, but it has never once hurt my phones. Considering motorola phones are the only ones it has been made for, i doubt it could work on htc phones when rewritten for such. Thank you again for de-caffinating my battle plan for the rezound. Sometimes i overlook the KISS approach trying to figure out how things work. (You know, Keep It Simple Stupid n . Thanksude!

the team bamf stuff is waaay depricated. maybe one day htc will wise up and just post their RUU's to keep people from having to search, poke, prod, and guess

Edit dos: i felt like i had read that post and tried to go that route. Once i clicked on the link, i remembered why i didnt. The rom file download doesnt load. The hosting page says in a banner at the top that they are expecting a fix for speed issues. The file never loads though and it was at least 3 days ago.

Finally got it downloaded. Mirror 13...well, not. but i did get it this morning. now im gonna do this:

first,let me be a little clearer. sometimes my answers are general,and refering to what one could do in any situation. however,i think youre beoming a little condfused,since in this particular case,my response is specific to this thread,flashing the linked rom and the official,signed by htc firmware package.

this thread is for the folks that are stock,and want to continue being stock,and need a manual way to achieve that.

as obscuro(brenuga) said,the OTA is a bunch of patch files,along with firmware.zip that the stock recovery installs. it is not a full rom.

when one cannot OTA,updating the full rom manually will come in 2 stages:
1)flash the rom itself in recovery
2)flash the official firmware.zip file in bootloader

firmware.zip in this case(OTA to build 4.05.605.14) contains the following images/files:
-adsp
-android info
-boot
-hboot
-mdm9k
-mdmrcdata
-mdmmrfg
-radio
-rcdata
-recovery
-rfg
-sbl3
-tp_atmel
-tz

as you can see,alot of things get updated,not the least of wich is the boot image. this is why i stated above that if you were flashing the matching rom prior to flashing this firmware package,that you would not need to flash a boot image seperately,as firmware.zip is doing it for you.

there are other situations-for folks on custom roms that want the newer radios,or folks that want to restore a nandroid backup,and prolly other situations as well. those folks will likely need a new boot image,and new recovery after flashing firmware.zip. there are many wAys to skin the "flash a new boot image cat". easiest IMO is to just fastboot boot recovery as obsurco explained. more info on that here: http://androidforums.com/rezound-all-things-root/587430-s-want-flash-roms-read.html but again,my answers were directed mainly towards the folks that want the stock rom and firmware.



i always like to be on the newest firmware when s off. when s on,i personally am alot more cautious,as you cannot go back to what you had before if the new firmware blocks an exploit,or has some sort of bugs or issues.

in all honesty,if you dont want the global software,there prolly is not a tremendous need to update the firmware only. if you like 3.14.605.13,the firmware thats with it is likely suiting you just fine.

hope that clears it up some for you guys. also,just thot id point out that being s-off makes all this nonsense tremendously easier

Scotty, thank you for your work and PATIENCE! ;}

and if, for some reason, anyone else has problems with the download, here's a dropbox link.. till it crashes or is used up.

i tend to be a man of my word...


http://db.tt/eDCMt41r