Hey guys,
beforehand: I'm totally new to this topic, so please be patient.
I got my HTC Flyer Wifi & 3G [P510e] back from reparation and the guys there also updated my Flyer to Honeycomb (3.2.1). Since I cannot use my touch buttons anymore, I would like to do a downgrade to Gingerbread again.
I've searched here and found this topics:
http://forum.xda-developers.com/showthread.php?t=1428104
http://forum.xda-developers.com/showpost.php?p=19607833&postcount=3
Now I'm not sure what to do: do I need to S-OFF my Flyer to make a downgrade, like shown in the following thread?
http://forum.xda-developers.com/showthread.php?t=1358758
Which Gingerbread-Version do I have to use, how can I find that out? And where do I get it from?
And the most important thing: what is the worst thing that could happen if I mess up something?
My Flyer is currently S-ON, my HBOOT-Version is HBOOT-1.11.0011 (see attached file) and it's a german version, if that is important to know.
I would appreciate it if someone would help me with this. Normally I'd ask my ex-boyfriend to do this for me, but since we broke up, I want to manage this kind of stuff on my own. :fingers-crossed:
Katzenmuetze said:
Hey guys,
beforehand: I'm totally new to this topic, so please be patient.
I got my HTC Flyer Wifi & 3G [P510e] back from reparation and the guys there also updated my Flyer to Honeycomb (3.2.1). Since I cannot use my touch buttons anymore, I would like to do a downgrade to Gingerbread again.
I've searched here and found this topics:
http://forum.xda-developers.com/showthread.php?t=1428104
http://forum.xda-developers.com/showpost.php?p=19607833&postcount=3
Now I'm not sure what to do: do I need to S-OFF my Flyer to make a downgrade, like shown in the following thread?
http://forum.xda-developers.com/showthread.php?t=1358758
Which Gingerbread-Version do I have to use, how can I find that out? And where do I get it from?
And the most important thing: what is the worst thing that could happen if I mess up something?
My Flyer is currently S-ON, my HBOOT-Version is HBOOT-1.11.0011 (see attached file) and it's a german version, if that is important to know.
I would appreciate it if someone would help me with this. Normally I'd ask my ex-boyfriend to do this for me, but since we broke up, I want to manage this kind of stuff on my own. :fingers-crossed:
Click to expand...
Click to collapse
if you are not s-off now,then your 2nd and third links are not really of any use.
depending on wether you want to use htcdev for root,or a temporary root exploint you need to use either this thread:
http://forum.xda-developers.com/showthread.php?t=1307759 (for htcdev)
or your first link:
http://forum.xda-developers.com/showthread.php?t=1428104
the disadvantage to htcdev for root,is that it will leave a watermark that shows you have unlocked the bootloader,and as the unlock website states,this could void "all or parts of your warranty"
the disadvantage of the other link,is that the root exploit(taco root) is kind of a funky exploit,and while safe, is a little tricky to use if youre not used to doing things like this.
after you have downgraded to gingerbread,you can use revolutionary to s-off( http://revolutionary.io/ ) this leaves the door open to upgrade to honeycomb with s-off later,if you desire. it will also let you install a custom recovery,and add root access so that you can modify the stock gingerbread rom,or flash a custom GB rom, so that you can continue to operate on GB without pesky OTA notifications.
last and not least,if you cannot find a GB ruu that supports your CID (carrier identification) you will need a goldcard to downgrade to a different carrier or unbranded RUU. (directions to make a gold card: http://www.addictivetips.com/mobile...-gold-card-for-htc-desire-without-hex-editing)
just holler if you have further questions.
if you decide to go the htcdev route,i have a guide with some download links that may simplify that process somewhat for you,and can reproduce it here if you desire.
scotty1223 said:
if you decide to go the htcdev route,i have a guide with some download links that may simplify that process somewhat for you,and can reproduce it here if you desire.
Click to expand...
Click to collapse
That would be great, thank you.
TSGM said:
That would be great, thank you.
Click to expand...
Click to collapse
sorry for the delayed reply.
here is my "htcdev" guide:
i sometimes refer folks to my rezound guide in other forums,so i decided to make a slightly more "universal" version that i could replicate in other forums,so everyone has a dedicated guide,and there are not accidents with accidental application of rezound specific details or files. devices i am familiar with i will try and tweak and add device specific recovery downloads/info. whatever device youre working on,please feel free to post in this thread,i will be happy to assist you
before we get started,however,be aware that htcdev does have its limitations. it can be used if you only wish to add root access to delete bloat and run a few root requiring apps,but IMO it is best used as a "steppig stone" to get root for downgrade,or for other exploits to run. if s-off is availble on any "downgradeable to" firmware,i do highly recomend to try and achieve that goal if you wish to activly flash roms. im happy to help with this,as well,if needed.
the basic steps will be:
1)unlock with htcdev
2)temporarily or permanently flash a recovery
3)flash root files
before you start,go ahead and download these files:
-mini-adb.zip: mini-adb.zip
-the latest custom recovery image of your choice, for your device(for the flyer,use http://hyuh.net/files/flyer/downgrade/recovery.img md5 bb366b025dcc454ffe8b21b8bf0c72d0)
-superuser files: for froyo use superuser 3.07 (found on revolutionary public wiki). for GB,HC or ICS,use the latest superSU from this thread on xda (the download link is where is says: CWM installable ZIP: CWM-SuperSU-v0.96.zip )
-go to HTCdev - Unlock Bootloader and register an account
1)unlock with htcdev
first thing you need is drivers for adb to see your phone. if you have htc sync installed,you should allready have drivers. if not,you can install htc sync,or install these modified htc drivers from revolutionary
most guides simply say "follow the directions to unlock with htcdev" but im gonna go thru it with ya the mini-adb.zip file is all the files that htcdev is telling you to download and put into a folder,so allready this should be a lil easier
1)prepair ADB
-unzip your mini-adb.zip file. this is native funtionality in windows 7. you otherwise may need a utility such as "7-zip" to extract,or unzip it. place the unzipped folder onto the root of your C drive on your PC(sorry, you mac guys will need to develop this for yourself,i dont have a mac). root means the top level,not inside any folders. so just copy and paste,or drag and drop the folder onto C with everything else that is there. you may want to rename it to "mini-adb_devicename" since youll be putting some device specific files in here. (directions from here forward will assume this folder to be named "mini-adb_vigor",as an example)
-open a command window. on windows 7,click the start bubble in the lower left and type "command" in the search box. xp i believe is similar or the same. doing this should open a small black command window.
-change to your mini-adb_vigor directory. type the following at the prompt in your cmd window:
cd c:\mini-adb_vigor
your command promt should change to "c:mini-adb_vigor>" provided you: 1)unzipped the miniadb zip 2)put the folder on your c drive 3)entered the name of the folder correctly ("mini-adb_vigor" in this case)
-now make sure usb debugging is checked in settings/apps/development,and plug your phone into your PC with a usb cable
-make sure your phone is being recognized- type:
adb devices
if your drivers are installed correctly,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
2)unlock using htcdev
-go to HTCdev - Unlock Bootloader and sign in to your account. chose your device from the "select your device bar"(or "other supported devices" if its not listed) and click the green "begin unlock bootloader" button underneath.
-click yes to procede,then read the warnings before checking the boxes and clicking yes to continue,as they are basically explaining that your warranty is now void,and any repairs that your phone needs that may have been a result of unlocking your bootloader and messing with your phones operating system may no longer be covered under mfgr warranty
*check your hboot screen. if you allready have an htc compatible hboot, then skip ahead to the next step,you dont need this.if you have a pink **locked** at the top of the hboot screen,then it is compatible with htcdev. if you dont have a compatible hboot,then download the RUU for the new hboot. right click it,and run as administrator. plug in your phone when prompted to. it will ugrade your hboot to the htcdev unlock compatible version.
-steps 1-4 are describing how to get your phone into bootloader mode and connect it to your PC,wich we have done above. ignore these steps and simply type in your cmd window:
adb reboot bootloader
it may take several seconds,but this command should boot your phone into the "fastboot" screen wich is white with a bunch of colored writing. once this happens,make sure your phone is still being seen in fastboot. type:
fastboot devices
again,this should return your phones serial number.
-click the green procede to step 5 bubble.
-steps 5-7 are telling you how to find the files and utilities inside your mini-adb folder. you have them,so ignore steps 5-7.
-click the green procede to step 8 bubble.
-heres where steps are important,steps 8-10 are telling you how to get your unlock token,and send it to htc. its phone specific(so they prolly know your serial number,meid,etc) so no,you cant use your buddys unlock token and not have htc know that youve unlocked your bootloader. copy this line either from below,or from step 8,and paste it into the prompt in your cmd window. you have to right click to paste in cmd,you cannot control/v :
fastboot oem get_identifier_token
-after yuo hit enter,you will get a bunch of letters that are your identifier token. not much i can say,other than follow the directions in steps 9 and 10 to copy and submit your identifier token to HTC. make sure you get the characters as shown in the pic,with no extra lines or letters. note that you can also hit the "enter" key on your PC to copy,as well as right clicking.
-click the green submit button. wait patiently for an email containing your unlock code. (dont worry,it should come pretty fast )
-save the unlock_code.bin that htc sends you directly to your mini-adb folder(if your PC automatically downloads somewhere else,no biggie. just move the unlock code to mini-adb folder)
-click the link in your email to get the rest of the unlock instructions
-step 12 is where them magic happens copy from below,or from htc dev:
fastboot flash unlocktoken Unlock_code.bin
-youll see the purdy screen pictured in step 13. use the vol rocker to chose "yes unlock bootloader" and select it with the power button. your phone will reboot,performaing a factory data reset in the process. your data is gone,sorry this boot may take a bit longer than they normally do,dont freak out this is normal
as you can see,once the adb files are put in one place to download,its not hard to use,and the commands are pretty simple. below is what you will see in your command window,the red are my inputs.
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:UsersScott>[COLOR="Red"]cd c:\mini-adb_vigor[/COLOR]
c:mini-adb_vigor>[COLOR="red"]adb devices[/COLOR]
List of devices attached
HTxxxxxxxxxx device
c:mini-adb_vigor>[COLOR="red"]adb reboot bootloader[/COLOR]
c:mini-adb_vigor>[COLOR="red"]fastboot devices[/COLOR]
HTxxxxxxxxxx fastboot
c:mini-adb_vigor>[COLOR="red"]fastboot oem get_identifier_token[/COLOR]
... INFO
INFO< Please cut following message >
INFO<<<< Identifier Token Start >>>>
INFO2ADC7C0C0F1BAF92074BAE9B0035CB6A
INFO021839BFA7465CD0788664688DCCFDEA
INFO33A2FD2C96C7308DD3C57A517DBA8E14
INFO8048F98A9FEA06B8F2AD05D4D3497CFE
INFO6FCCC1DC4E31E0C6F54CEA18D9A80C82
INFO27C33E209D472E6C11753E9D7BCBCE6D
INFO90D9F226E827B6C26165A029B6F7DFF2
INFO63E382B4C82F9F6D866C01B9823ED1BC
INFO0EEFA859327E6B5AC4C24533C9DFA7AF
INFODBD70D55E4666B4B41828B76FFBD010C
INFO1B916E350EFF199EA5B096FF3337FE19
INFO40E6CA9E7F1DD5B33D8D4780DD775289
INFO953404686AEC4C3CB6F1BBB9DC69BA13
INFO8738C00DAFF280ECF02D0C7A66E13855
INFO1D756616732FF47915EAD551A6933E08
INFO10C541C7RD02C14991E83CC49FCA4B92
INFO<<<<< Identifier Token End >>>>>
OKAY [ 0.069s]
finished. total time: 0.070s
c:mini-adb_vigor>[COLOR="red"]fastboot flash unlocktoken Unlock_code.bin[/COLOR]
sending 'unlocktoken' (0 KB)... OKAY [ 0.143s]
writing 'unlocktoken'... INFOunlock token check successfully
OKAY [ 0.011s]
finished. total time: 0.156s
c:mini-adb_vigor>
2)flash a recovery
if you want to run stock,do not permanently install your recovery. keeping the stock recovery on the phone will ensure that you recieve OTAs without a hitch,wich i know is important to alot of users. YES,the OTA will break root. its no big deal. one good thing about htcdev is that you will always be able to reroot after,simply by following steps 2 and 3 again to launch recovery,flash superser.
once youve either skipped past all the setup,or have re-set up and are ready to root,chose either of the following options to either permantly or termporarily install a recovery:
1)temporary recovery:
-move the recovery image file you downloaded above and place it into the mini-adb folder.
-put the superuser zip file onto your phones sd card
-enable usb debugging once again,as above. open a cmd window,if its not still open from unlocking.
-if you had to re-open a cmd window,dont forget to change back to your mini-adb directory:
cd c:\mini-adb_vigor
-make sure youre connected by typing:
adb devices
-should return serial number
-check the md5 of your recovery image:
md5sums <recoveryname>.img
**make sure the resulting md5 matches the one that is listed for the image that you downloaded. ** (if no md5 is listed,post in the thread,i can download and compare my md5 to yours.this is not as good as getting an md5 from the one who linked the file,but its better than nothing)
-boot to bootloader:
adb reboot bootloader
-check for connectivity:
fastboot devices
-should return serial number
-temporarily launch your recovery to phone memory:
fastboot boot <recoveryname>.img
-youll see a (really fast) green status bar on the top right as your PC sends the recovery to your phone. youll then see the HTC splash screen,then your recovery.
in your command window you will see(red are my inputs):
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:UsersScott>[COLOR="Red"]cd c:\mini-adb_vigor[/COLOR]
c:mini-adb_vigor>[COLOR="Red"]adb devices[/COLOR]
List of devices attached
HTxxxxxxxxxx device
c:mini-adb_vigor>[COLOR="red"]md5sums recovery-ra-vigor-3.14-gnm.img[/COLOR]
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[c:mini-adb_vigor]
recovery-ra-vigor-3.14-gnm.img 915d5e3cb662076f36f3d6e54759e951
c:mini-adb_vigor>[COLOR="red"]adb reboot bootloader[/COLOR]
c:mini-adb_vigor>[COLOR="red"]fastboot devices[/COLOR]
HTxxxxxxxxxx fastboot
c:mini-adb_vigor>[COLOR="red"]fastboot boot recovery-ra-vigor-3.14-gnm.img[/COLOR]
downloading 'boot.img'... OKAY [ 1.518s]
booting... OKAY [ 0.005s]
finished. total time: 1.523s
2)permanently install your recovery
-move the image file you downloaded above and place it into the mini-adb folder.
-enable usb debugging once again,as above. open a cmd window,if its not still open from unlocking.
-if you had to re-open a cmd window,dont forget to change back to your mini-adb directory:
cd c:\mini-adb_vigor
-make sure youre connected by typing:
adb devices
-should return serial number
-check the md5 of your recovery image:
md5sums <recoveryname>.img
**make sure the resulting md5 matches the one that is listed for the image that you downloaded. ** (if no md5 is listed,post in the thread,i can download and compare my md5 to yours.this is not as good as getting an md5 from the one who linked the file,but its better than nothing)
-boot to bootloader:
adb reboot bootloader
-check for connectivity:
fastboot devices
-should return serial number
-permanently flash your recovery to phones recovery partition:
fastboot flash recovery <recoveryname>.img
-youll see a (really fast) green status bar on the top right as your PC sends the recovery to your phone,then a (really,really fast) red bar as it flashes it. amon ra is now permanently on your phone when you need it. be aware that you can no longer accept OTAs,unless you reinstall the stock recovery at some point before the next OTAs are pushed.
-to get to recovery,push the power button to select hboot. once in hboot wait for the green writing to flash and disapear,then select recovery.
*note that you can still launch recovery by using the command from scenario 1 above.
-youll then see the HTC splash screen,then your recovery.
and the code(again,red my inputs):
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:UsersScott>[COLOR="red"]cd c:\mini-adb_vigor[/COLOR]
c:mini-adb_vigor>[COLOR="red"]adb devices[/COLOR]
List of devices attached
HTxxxxxxxxxx device
c:mini-adb_vigor>[COLOR="red"]md5sums recovery-ra-vigor-3.14-gnm.img[/COLOR]
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[c:mini-adb_vigor]
recovery-ra-vigor-3.14-gnm.img 915d5e3cb662076f36f3d6e54759e951
c:mini-adb_vigor>[COLOR="red"]adb reboot bootloader[/COLOR]
c:mini-adb_vigor>[COLOR="red"]fastboot devices[/COLOR]
HTxxxxxxxxxx fastboot
c:mini-adb_vigor>[COLOR="red"]fastboot flash recovery recovery-ra-vigor-3.14-gnm.img[/COLOR]
sending 'recovery' (7074 KB)... OKAY [ 1.659s]
writing 'recovery'... OKAY [ 5.179s]
finished. total time: 6.840s
3)flash superuser root files*
there is not much to explain with this one. if booted to recovery from above,use the recovery menu on your phone to:
-make a backup of your stock,unrooted rom. completely optional,but a very good idea,IMO.
-wipe cache
-wipe dalvik cache
-install zip from sd card(chose your superuser file)
-reboot
*congratulations,youre rooted
if your device has procedures to s-off,or procedures to downgrade to more exploitable firmware,you can procede with that now
for the flyer we can use these directions: http://forum.xda-developers.com/showthread.php?t=1307759
after we downgrade to gingerbread,we can root with revolutionary:
http://forum.xda-developers.com/showthread.php?t=1194709
after yoou have s-off on gingerbread,you can update back to honeycomb:
http://forum.xda-developers.com/showthread.php?t=1358758&highlight=honeycomb+easy+s-off
if youre considering leaving htcdev unlock,read this if you want to flash roms: http://androidforums.com/rezound-all-things-root/587430-s-want-flash-roms-read.html
s-off is better,and worth whatever extra efforts to achieve if available.
*hope it helps,holler if you have questions
donate to my device fund
Click to expand...
Click to collapse
gave you some links at the end to downgrade,then s-off,then upgrade back to honeycome,as well as a link that may be of some value if youre considering just unlocking via htcdev and leaving it at that. htcdev is a PITA if your intent is to flash different roms,and its even more dificult as there is no other option to chagne roms other than manually installing the boot image(i have verified that fastboot booting the recovery on the flyer does NOT provide the same advantages it does on the rezound,and other htc phones.
i will be happy to help you with any questions you have about htcdev vs s-off,or with the unlock procedure. if you just want to be rooted on the stock HC rom,htcdev unlock works,but thats about it
we can also help you with the downgrade etc. after yovue completed this,but will save that for later so we dont overwhelm you with info
Related
The release by HTC of an unlockable bootloader (v 1.51.0000) for the Droid Eris has created a potential opportunity for rescue of some soft-bricked Eris handsets.
Are you an owner of one of these units? There is a decent chance of recovery back to a working state!
(Props go to Android Forums user "scotty85" for figuring this out.)
This (v 1.51.0000) bootloader is rather quirky - it does not allow direct flashing of individual partitions using fastboot - but it does allow flashing of zip files containing recovery, boot, and system partitions via fastboot with the phone in "RUU mode" once the bootloader is unlocked with a procedure from HTC.
If your phone can be booted into its' bootloader (HBOOT, FASTBOOT, or RUU mode), but can not successfully boot all the way up - or it gets stuck in a bootloop during booting, and you only have a stock recovery on the phone, this might be the approach for you.
Rather than write up the whole method to begin with, I'll just ask for responses to see if anyone is interested. And then take it from there if I get some nibbles.
If you think you have a phone you want to try to rescue, speak up - and say a few words about whether the phone can get into different bootloader modes, which bootloader version you have on the phone, and so forth.
Note: at the moment, getting this to work requires getting the fastboot program running on your PC - it is not a phone-only method. The amount of effort at the command line is minimal, but you will need to be able to get your PC talking to your phone to do this.
bftb0
I have a friend who is in this exact situation. Any help you can provide would be great.
Yatyas said:
I have a friend who is in this exact situation. Any help you can provide would be great.
Click to expand...
Click to collapse
Take your time, and read and understand this whole post before you begin.
[size=+2]Files Needed:[/size]
Collect all the files you will need, get them on to the root folder of your SD card, and verify their MD5 signatures (the copy that makes it to your SD card, not the copy on your computer) :
"rom.zip" - the 1.51.0000 bootloader install payload - here **
MD5: daab6bcbe78c41938a95c4963c5c44e8
custom recovery - either Amon_RA's ("recovery-RA-eris-v1.6.2.img"), or scary alien's trackball-free derivatives here (e.g. the New 1.7.1 version)
"ErisMiscReset_v0.9.zip" here
"MTD_Inspect_v0.9.zip" here
"ErisMTDNuke_v0.9.zip" here (also, please see disclaimer here)
"Eris_RootROM_v2.19.605.1_PB00IMG.zip" from shipped-roms.com. Note that this (also) is renamed to PB00IMG.zip at the appropriate time. **
A custom (dev) ROM, or even a fully stock ROM such as the HTC Eris March 2011 OTA Stock ROM - v2.41.605.6
[size=+2]Installation Method:[/size]
Note:
A less thorough method than what is described here, but shorter, is reported here. Even though I built the "ErisMTDNuke_v0.9.zip" repair tool, I do not advocate using it unless it is confirmed to be absolutely necessary. Moreover, in almost every case, having the Eris S-OFF bootloader on a rooted phone is an advantage, and (also) having the "misc" partition "MainVer" value reset back to a low value after fooling with RUUs or PB00IMG.zip installs is a good idea to prevent future disasters. The short method does not document either of these two steps.
Note #2: In any of these procedures, it is important to do so with A FULLY CHARGED PHONE. Do not let the phone sit idle for long periods of time in HBOOT, FASTBOOT, or RUU modes - even with the Eris plugged in to a USB port, in those modes it will discharge very rapidly - about two hours or so. That little green light is your friend.
- get fastboot on a PC working and communicating with the phone in its' current state (with the phone in fastboot mode or RUU mode). Doubtful if I will reply to inquiries about Windows and driver installs - it's covered in gory detail all over the place. Same goes with getting a copy of "fastboot.exe" for windows. (Google is your friend).
- Install the "rom.zip" file for the 1.51.0000 bootloader, (Rename to PB00IMG.zip and install it by booting the phone into HBOOT mode**)
- register with htcdev.com for unlocking this new Eris bootloader & follow the bootloader unlocking instructions (you can skip downloading & running the RUU, as you have installed the bootloader already)
- create a zip file with a custom recovery image in it (named "recovery.img"), and an "android-info.txt" file with MainVer set to 2.42.0000 (see step #3 of this XDA post).
- using fastboot and the phone in RUU mode, flash this zip file ("fastboot flash zip zipfilename.zip") Again, see step #3 of the link above.
- power off the phone and boot into the custom recovery and flash the ErisMiscReset_v0.9.zip file (watch for any errors - stop if you see errors!).
- in the same recovery session flash the MTD_Inspect_v0.9.zip file and determine if you have massive (bad block) corruption in any of /boot, /system, or /data. (See instructions here)
- If the above mentioned partitions only have one or two bad blocks, skip the next step.
- Flash (in recovery) ErisMTDNuke_v0.9.zip
- Re-lock the 1.51.0000 bootloader (phone in fastboot mode) with "fastboot oem lock"
- Flash the Eris Root ROM (from shipped-roms.com), using the HBOOT+PB00IMG.zip install method. The objective of this step is primarily to get rid of the 1.51.0000 bootloader, and install the 1.49.2000 S-OFF bootloader. Note this will stomp on your custom recovery (unless you use the battery pull trick), but that's OK.**
- get the custom recovery back onto the phone - using either the standard Eris rooting tools (Dummies or One-Click), or simply flash it using fastboot (e.g. "fastboot flash recovery recovery-RA-eris-v1.6.2.img")
- one last time: in the custom recovery, flash the ErisMiscReset_v0.9.zip file
- Install a ROM and be happy.
** after using any PB00IMG.zip file, it is a really good idea to rename it ASAP, so that you don't accidentally re-install it by inadvertently powering up the phone in HBOOT mode.
bftb0
not much to add. if the notion of downloading the sdk,installing fastboot,adb,etc. is a bit overwhelming you can use this file: http://www.mediafire.com/?hzf1u4bowjewhdq it contains adb and fastboot,and a utility called md5sums,and the needed files to make them work.
simply download,extract(unzip),and place the extracted folder onto the root of the C drive on your PC.
open a command window in windows 7 by clicking the start bubble,and type "command" in the search box. i believe xp is the same,or similar.
once you have a small,black command window open,you can change to the "mini-adb" directory by typing this command:
Code:
cd c:\mini-adb
you can call that folder anything you want,but when you "cd" to it,you must type the exact name the folder is called.
for drivers to get the eris recognized by the PC,you can install htc sync,or use these modified htc drivers from revolutionary public wiki
just holler if you have any questions with any of the above
i got several stuck at 1.49.000000 s on . i dont know if they have the stock recovery on them or not . does have fastbootusb though and hboot
highhacker said:
i got several stuck at 1.49.000000 s on . i dont know if they have the stock recovery on them or not . does have fastbootusb though and hboot
Click to expand...
Click to collapse
Hopefully we can fix them. Do you have any questions to get started?
wrong nv items wont boot or boot into recovery
Hey guys this phone is on an endless bootloop. I installed the 1.51. hboot unlock the bootloader, flash aman recovery 1.6.2 via Ruu successfully but when I try to boot into recover it continues to bootloop. I already install recovery via hboot but no success. I am willing to try anything with this phone for educational purposes for I dont need the phone but is something that I started over a year ago when I did the mistake with the wrong NV items. I can successfully follow all the step until step 4 but when is time to boot recovery it simply wont or any other file. Tried via regular FASTBOOT recovery.img but no luck. I Still have the S-ON on hboot 1.51. Any suggestions????
@obonilla30
obonilla30 said:
Any suggestions????
Click to expand...
Click to collapse
I started a reply and then saw that you were communicating with the right folks over on Android Forums. I was going to send you to exactly the same thread that you found.
If I may make a suggestion - both your posts here and also over there at AF leave quite a bit open to interpretation. For instance, when you mention "bootlooping", you didn't say whether this was for entering recovery from a coldstart (Vol-Up+End/Power), or via navigating from either Fastboot mode (Send+End/Power) or HBOOT mode (Vol-Down+End/Power), and then traversing the menus there to boot the recovery partition. It might be that you tried all three - but you didn't say so. Slow down a little bit and fill in as much detail as you can.
There are TWO methods suggested over in that AF thread - one is to flash (w/ unlocked 1.51 bootloader in RUU mode) a custom recovery to the recovery partition, and the other is to flash a stripped-down version of the (custom) recovery to the boot partition. (You could actually do both in the same flashing operation if you wanted - but note that you can't just rename one of the custom recovery images to "boot.img", because they are too big. But scary alien and scotty85 over there on AF put together something that will fit into the boot partition). That gives you two different ways to get a privileged execution environment running.
cheers
bftb0
PS Not to rehash old painful memories, but do you recall what exactly it was you did when you "did the mistake with the wrong NV items"?
S###
scotty1223 said:
Hopefully we can fix them. Do you have any questions to get started?
Click to expand...
Click to collapse
Well these "steps" got me no where . First step was put the hboot on my sd card and boot into hboot . still have Hboot 1.49.0000 (PB0010000) S-ON ((( That don't work . I got a box full of eris all 1.49.0000 s-on that show some kind of semi recovery on them where i can flash an update.zip and clear to factory .etc.. Still all stuck on three green androids.. Not very good with adb on pc but tried it in fastbootusb mode on phone and gave the command fastboot flash zip zipfilename.zip (my zip) and said remote not allowed . I have 15 tabs up on firefox and is just too much back and forth . is there a Dummy guide
highhacker said:
Well these "steps" got me no where . First step was put the hboot on my sd card and boot into hboot . still have Hboot 1.49.0000 (PB0010000) S-ON ((( That don't work . I got a box full of eris all 1.49.0000 s-on that show some kind of semi recovery on them where i can flash an update.zip and clear to factory .etc.. Still all stuck on three green androids.. Not very good with adb on pc but tried it in fastbootusb mode on phone and gave the command fastboot flash zip zipfilename.zip (my zip) and said remote not allowed . I have 15 tabs up on firefox and is just too much back and forth . is there a Dummy guide
Click to expand...
Click to collapse
You will always get "remote not allowed" with a S-ON bootloader, or with the 1.51.000 bootloader in the locked state. And you will probably also get that error even with a 1.51.0000 bootloader in an unlocked state if you try putting a "boot.img" or "recovery.img" file in the zip. Don't bother using fastboot with a 1.4x.00 S-ON bootloader - it doesn't ever work for anything useful.
Note also that the steps given above need to be performed in sequence and each step needs to succeed. There is no point in doing a 2nd or 3rd step if the first step fails.
As for the PB00IMG.zip install of the 1.51.0000 bootloader, when you boot the phone into HBOOT mode, you should see SOMETHING different happen - even if it is a failure of some sort - than how HBOOT behaves when there is no PB00IMG.zip file on the SD card. If the phone behaves identically whether or not you have the SD card in place, then that means you mis-spelled the name of the PB00IMG.zip file, or didn't put it in the top-level folder of the SD card. Even in the case where it is there on the card, but corrupted, you will see a different behavior of the HBOOT from when there is no PB00IMG.zip file present.
Unfortunately, your post above gives no details about this. That means that anybody that is willing to try and help you is forced to guess about what you are seeing your phone do.
bftb0
defiantely the first step is to get 1.51 onto the phone. in addition to the above,make sure that your sd card is formatted FAT32. i cant remember if this is important for the eris,but it is crucial for other dervices..
what you should see when a properly named PB00IMG file is placed on the root of the sd card,is a quick flash of green writing,then status bars on the upper right corner of the screen as the phone finds and checks the file,followd by a "do you want to update" prompt.
another common error with a PxxxIMG file on any devices,is that the decive must see PxxxIMG.zip. in the case of the eris,the file on the phone must be "PB00IMG.zip". the common error part comes from naming the file with windows. lots of folks will type in the .zip,forgetting that windows naturally adds and hides the file extension. therefore,typing in "PB00IMG.zip" actually names the file to "PB00IMG.zip.zip" in rarer cases,not typing in the ".zip" with windows if configured differently may end up in the file just being "PB00IMG" wish will not be found either.
so to recap
-check sd card for FAT32
-check the name of PB00IMG on the sd card. try adding or removing the ".zip"
-make sure PB00IMG is on the top level of the sd,not hidden inside a folder.
let us know how that goes
once you get the 1.51 hboot onto the phone,the next step is to unlock it. just holler if you have questions on htcdev's directions.
One of the simple mistakes that people make is when they rename the "rom.zip" file, they rename it as
PBOOIMG.zip (PB "oh-oh" IMG.zip)
instead of the correct spelling
PB00IMG.zip (PB "zero-zero" IMG.zip)
As scotty and I both pointed out, if you have a correctly named file on there in the top-level folder, you will see *something* different happen, even if the file is corrupted.
If you don't see something different happen, then the problem is the SD card format, a mis-spelling of the file name (I recall some people transferring files from their PCs, ending up with a file named "PB00IMG.zip.zip"), or the file is not in the top-level folder of the SD card.
bftb0 said:
You will always get "remote not allowed" with a S-ON bootloader, or with the 1.51.000 bootloader in the locked state. And you will probably also get that error even with a 1.51.0000 bootloader in an unlocked state if you try putting a "boot.img" or "recovery.img" file in the zip. Don't bother using fastboot with a 1.4x.00 S-ON bootloader - it doesn't ever work for anything useful.
Note also that the steps given above need to be performed in sequence and each step needs to succeed. There is no point in doing a 2nd or 3rd step if the first step fails.
As for the PB00IMG.zip install of the 1.51.0000 bootloader, when you boot the phone into HBOOT mode, you should see SOMETHING different happen - even if it is a failure of some sort - than how HBOOT behaves when there is no PB00IMG.zip file on the SD card. If the phone behaves identically whether or not you have the SD card in place, then that means you mis-spelled the name of the PB00IMG.zip file, or didn't put it in the top-level folder of the SD card. Even in the case where it is there on the card, but corrupted, you will see a different behavior of the HBOOT from when there is no PB00IMG.zip file present.
Unfortunately, your post above gives no details about this. That means that anybody that is willing to try and help you is forced to guess about what you are seeing your phone do.
bftb0
Click to expand...
Click to collapse
Well that was agood guess. The first step change rom.zip to PB00IMG.ZIP (I ASSUME THAT IS ZERO ZERO ) . it does somthing fast and i can see no image somthing like
Loading .....(PB00DIA0.zip)
no image
loading ......(PB00DIA3.zip)
no image
loading ......(PB00DIA2.ZIP)
no image or wrong image
. i have to keep flipping between fastboot and hboot to try and read what it says . basically it goes for another 5 or 6 lines with no image or wrong image ..
tried re downloading rom.zip and renaming it againg . same srrors..
have you tried renaming "PB00IMG" without the zip?
you can also try flashing it as an RUU,wich eliminates the sd card,and the name of the file from the equation.
place rom.zip(for 1.51 hboot) into the folder containing fastboot and hboot..
-place the phone in fastboot.
-assuming you leave rom.zip named "rom.zip",open a cmd window and enter the following:
fastboot oem rebootRUU
fastboot flash zip rom.zip
it will do some stuff on the screen,then say "finished". then:
fastboot reboot-bootloader
thaT should boot you back into fastboot,where you should see 1.51.0000 locked hboot.
if you get a "failed" error instead of the above results,let us know what that error is and we can hopefully figure out what to do to make the flash work
if you get the 1.51 hboot,next step is to unlock it
highhacker said:
Well that was agood guess. The first step change rom.zip to PB00IMG.ZIP (I ASSUME THAT IS ZERO ZERO ) . it does somthing fast and i can see no image somthing like
Loading .....(PB00DIA0.zip)
no image
loading ......(PB00DIA3.zip)
no image
loading ......(PB00DIA2.ZIP)
no image or wrong image
. i have to keep flipping between fastboot and hboot to try and read what it says . basically it goes for another 5 or 6 lines with no image or wrong image ..
tried re downloading rom.zip and renaming it againg . same srrors..
Click to expand...
Click to collapse
The behavior you describe is EXACTLY how HBOOT mode behaves ... when there is no file named PB00IMG.zip on the root folder of the SD card. When I said "you will see something different happen", what I meant is something in addition to that list of file names rapidly scrolling by.
No doubt you are finding this frustrating.
In the past, there were two other reasons why this occurred:
1) People were using Windows Explorer on the PC. By default, it has an option turned on which is something like "hide file name extensions of known file types". With this (default) behavior, it is possible to rename the file PB00IMG.zip.zip, and yet what would be seen on-screen in Windows Explorer would only be "PB00IMG.zip". Turn that option off, or just use the DIR command from a command prompt to see if that is what happened.
2) Other users reported banging their heads into this without any luck, and then mysteriously solving the problem by formatting the SD card some other way than they previously had done. I don't have any further insight into the details here, other than this: the SD card should NOT be partitioned. If you got a box of phone which were previously rooted, it is possible you have a partitioned card (esp. if the phone had a 2.1 dev ROM on it)
The method scotty details above should allow you to side-step this problem, although you will have to get fastboot communicating with the phone (PC driver installs, etc).
To re-iterate though: if HBOOT discovers a file on the SD card named PB00IMG.zip, you will see something happen in addition to that list of file names rapidly scrolling by and disappearing. If you don't see anything additional - then HBOOT is not finding the file (for some reason or another).
bftb0
I am having an issue getting Amon recovery on my soft-bricked Eris.
I have the 1.51 bootloader unlocked but when I go to run the commands I get the following:
C:\adb>fastboot.exe flash zip recovery.zip
sending 'zip' (3817 KB)...
OKAY [ 0.827s]
writing 'zip'...
FAILED (remote: not allow)
finished. total time: 0.842s
If I try the RUU method it just sits at parsing:
C:\adb>fastboot oem rebootRUU
...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\adb>fastboot erase cache
erasing 'cache'...
OKAY [ 2.980s]
finished. total time: 2.980s
C:\adb>fastboot flash zip recovery.zip
sending 'zip' (3817 KB)...
OKAY [ 0.842s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
Also running the RUU_Desire_C_Verizon_WWE_2.36.605.1_release_signed_with_driver.exe and replacing the rom.zip did not work or trying to flash Eris_LeakV3_v2.36.605.1_PB00IMG.ZIP
The version it says I have it 2.42.0.0
Any ideas?
Thanks!
sorry it took me a couple days to reply to this. i believe the prollem your having is due to the android info document,specifically the hboot pre-update value. i had the same prollem starting in this post.
the android info i was using that was hanging at 'parsing' was:
Code:
ModelID: DESI****
ModelID: PB001****
ModelID: PB00100
CIDNUM: 11111111
CIDNUM: VZW__001
hbootpreupdate: 3
MainVer: 2.42.0.0
i pulled the one from the rom.zip extracted from the 1.51 hboot ruu and it worked fine.heres what it looked like:
Code:
CIDNUM:11111111
modelid: PB0010000
cidnum: VZW__001
cidnum: UTSI_001
mainver: 2.42.0.0
hbootpreupdate:12
try repacking your recovery with that android info,if its not what youre allready using.
zmanzbo,
What were the contents of the "recovery.zip" file you were trying to flash? (specifically, were there any .img files contained in it?)
Even when the 1.51.0000 bootloader is in the unlocked state, the flash will be disallowed if you have certain .img files in there (radio.img or recovery.img iirc - but don't quote me on that, I would need to go and re-read scotty's notes over in the AF thread).
Apologies for the vagueness - I'm afk at this time and am typing this from my phone.
bftb0
Well I got it working. I went to the link Scotty posted and downloaded tiny rescue recovery flashed that and then was able to run the various files listed in the original post bu bftb0. After that I was able to flash Eris_RootROM_v2.19.605.1_PB00IMG.zip. I am back in business now.
What was weird is that the contents of my recovery.zip were just the recovery.img and android-info.txt. The android-info.txt file had the same info as the 2nd one Scotty posted.
Thanks alot for the help here. Really appreciate it!
Cheers!
cool.
I'm glad you put the 1.49.2000 S-OFF bootloader on the phone afterward. It is always a good idea to have that bootloader (rather than the 1.51.0000 "unlockable" bootloader) installed, as the ways in which rescue/repair can be performed are more numerous (in case anything goes wrong in the future).
bftb0
If there's further discussion of this elsewhere that I've missed, please point me to it.
I'm trying to root my INC4G, but neither the manual nor scripted Fireballas method is successful.
-I have re-flashed the stock RUU, I am using a USB 2.0 port. All the basic ADB commands are fuctional in and out of fastboot, etc.
When I run the manual version, all is well up through restoring the fakebackup.ab file. When I enter the "while" command (without accepting restore yet on phone) I get the endlessly repeating error message mentioned by Aldo101t on the fireballas thread (post #54 and others). Accepting the restore on the phone handset does NOT stop the endless error loop in the Command line, and a prompt never becomes available again. I'm working on a Vista machine and I've tried the process through both the default 64-bit Command.exe and what I believe is the 32-bit version CMD.exe in the C:\Windows\SysWow64\ directory.
When I run the script version, all is well until I get the following:
----------------------------------------------------------------------------------------------------------------------
= Step 2: SuperCID =
========================
Your phone's CID is being modified to SuperCID. Once complete, your
phone will reboot to the bootloader.
/dev/block/mmcblk0p4: cannot open for read: Permission denied
remote object '/sdcard/mmcblk0p4' does not exist
The system cannot find the file specified.
cannot stat 'mmcblk0p4': No such file or directory
/sdcard/mmcblk0p4MOD: cannot open for read: Permission denied
rm failed for /data/local.prop, No such file or directory
< waiting for device >
...
(bootloader) cid: VZW__001
OKAY [ 0.012s]
finished. total time: 0.013s
Just above, you should see (bootloader) cid: 11111111
1) Yes, my cid is 11111111. Keep going.
2) No, my cid is VZW__001. Factory reset and try again.
3) No, my cid is VZW__001. Exit the script.
Select an option:
----------------------------------------------------------------------------------------------------------------------
Hitting option 2 to factory reset and repeat brings the same result each time.
Is there a specific permissions problem that I could resolve manually with a file manager? Or do I need to manually create a dummy file that can then be overwritten?
Any suggestions very welcome. I'd have posted this to the Fireballas forum, but I don't have posting privileges.
Thanks!
D
drenkin said:
If there's further discussion of this elsewhere that I've missed, please point me to it.
I'm trying to root my INC4G, but neither the manual nor scripted Fireballas method is successful.
-I have re-flashed the stock RUU, I am using a USB 2.0 port. All the basic ADB commands are fuctional in and out of fastboot, etc.
When I run the manual version, all is well up through restoring the fakebackup.ab file. When I enter the "while" command (without accepting restore yet on phone) I get the endlessly repeating error message mentioned by Aldo101t on the fireballas thread (post #54 and others). Accepting the restore on the phone handset does NOT stop the endless error loop in the Command line, and a prompt never becomes available again. I'm working on a Vista machine and I've tried the process through both the default 64-bit Command.exe and what I believe is the 32-bit version CMD.exe in the C:\Windows\SysWow64\ directory.
When I run the script version, all is well until I get the following:
----------------------------------------------------------------------------------------------------------------------
= Step 2: SuperCID =
========================
Your phone's CID is being modified to SuperCID. Once complete, your
phone will reboot to the bootloader.
/dev/block/mmcblk0p4: cannot open for read: Permission denied
remote object '/sdcard/mmcblk0p4' does not exist
The system cannot find the file specified.
cannot stat 'mmcblk0p4': No such file or directory
/sdcard/mmcblk0p4MOD: cannot open for read: Permission denied
rm failed for /data/local.prop, No such file or directory
< waiting for device >
...
(bootloader) cid: VZW__001
OKAY [ 0.012s]
finished. total time: 0.013s
Just above, you should see (bootloader) cid: 11111111
1) Yes, my cid is 11111111. Keep going.
2) No, my cid is VZW__001. Factory reset and try again.
3) No, my cid is VZW__001. Exit the script.
Select an option:
----------------------------------------------------------------------------------------------------------------------
Hitting option 2 to factory reset and repeat brings the same result each time.
Is there a specific permissions problem that I could resolve manually with a file manager? Or do I need to manually create a dummy file that can then be overwritten?
Any suggestions very welcome. I'd have posted this to the Fireballas forum, but I don't have posting privileges.
Thanks!
D
Click to expand...
Click to collapse
why not go to unlimited.io and s-off it. DONE
Aldo101t said:
why not go to unlimited.io and s-off it. DONE
Click to expand...
Click to collapse
I'd love to. But their step 12, "get temproot somehow-" appears to be the same part of the Fireballas process that won't work for me. If there's some other way to manage temproot--or if the Fireballas script is actually succeeding at temproot if only I knew to rip the cables out of the phone at the correct instant before the script crashes--please let me know what to try. I've never seen the shell prompt change from $ to #.
Did the unlimited.io process work for you, despite the same endless-error symptom through Fireballas? If so, can I ask how you achieved temproot?
Thanks for responding, above! : )
?
Sent from my ADR6410LVW using xda app-developers app
drenkin said:
I'd love to. But their step 12, "get temproot somehow-" appears to be the same part of the Fireballas process that won't work for me. If there's some other way to manage temproot--or if the Fireballas script is actually succeeding at temproot if only I knew to rip the cables out of the phone at the correct instant before the script crashes--please let me know what to try. I've never seen the shell prompt change from $ to #.
Did the unlimited.io process work for you, despite the same endless-error symptom through Fireballas? If so, can I ask how you achieved temproot?
Thanks for responding, above! : )
Click to expand...
Click to collapse
I USED THE AUTOMATED script in a different cmd window, you need to factory reset first then run it til the scrolling starts then accept restore, if it works properly the scroll stops. then adb reboot. when the phone has a screen with the droid eye on it and no icons(your done with this cmd window). it is in tempt root, then go back to the first cmd window you ruued on and finish the process. make sure usb debugging is on, after the ruu, you have to boot the rom (stock)to turn it on.
are you on a 32bit windows 7 and the enviornmental variables set. and the sdcard will get wiped s-offing so use a spare 8bg to 16gb no larger,and has to have an sdcard installed inthe phone to work. you can also go to unlimited.io for support and help. except the temp root deal they won't support that
Do you have a different machine you could use with a different OS? If so you may want to try that. 64 bit Windows 7 worked for me as far as temp root.
Good Luck
Interesting!
Aldo101t, thanks for mentioning using separate Command prompt windows, it led me to back up even further from a single instruction set and try the original root script by Bin4ry: it got me to a # prompt, and proper temproot...from which I could continue with the manual version of the Fireballas instructions and change out my VZW_001 id...and get the unlock code from HTCDev.
Currently have TWRP recovery installed, and about to flash ViperLTE Rom.
Thanks to Aldo101t and DavDoc for nudges and moral support. : )
drenkin said:
Interesting!
Aldo101t, thanks for mentioning using separate Command prompt windows, it led me to back up even further from a single instruction set and try the original root script by Bin4ry: it got me to a # prompt, and proper temproot...from which I could continue with the manual version of the Fireballas instructions and change out my VZW_001 id...and get the unlock code from HTCDev.
Currently have TWRP recovery installed, and about to flash ViperLTE Rom.
Thanks to Aldo101t and DavDoc for nudges and moral support. : )
Click to expand...
Click to collapse
your welcome, glad you got root.
Hey guys, I need to return my phone to verizon because of a simcard/PUK lock error. I'm on the current OTA update (2.06) but still unlocked, rooted and S-off. I need to go back to bone stock if possible. Can I still follow the guide in this thread to go back to stock??
http://forum.xda-developers.com/showthread.php?t=2017525
Anyone?
scheirere said:
Anyone?
Click to expand...
Click to collapse
You don't have to relock your phone all you have to do is flash the ENG Bootloader then you can run the RUU. Make sure you have all the drivers you need installed first or it WILL fail.
ENG Bootloader:
http://forum.xda-developers.com/showthread.php?t=2156713
Also this won't take away your S-Off the only way to get to S-On is by running a special command. Once S-Off always S-Off.
zone23,
Thanks a million! One more question....I'm not familiar with RUU. Do you have a link to were I might find that file?
Thanks again,
Eric
scheirere said:
zone23,
Thanks a million! One more question....I'm not familiar with RUU. Do you have a link to were I might find that file?
Thanks again,
Eric
Click to expand...
Click to collapse
Yes try here:
http://forum.xda-developers.com/showpost.php?p=37277937&postcount=66
Oh and don't forget to hit thanks on that post.
Ok, now I'm a little confused. I downloaded both files. The modded ENG bootloader and the RUU zip file from the links. But what order. Sorry but I'm not familiar with this stuff and don't want to dig myself into a deeper hole by bricking this thing.
Is this the proceedure?
1. adb reboot bootloader
2. fastboot oem rebootRUU (using the RUU_DLX_WL_JB_45.exe file?)
3. fastboot flash zip ModdedPL832IMG.zip
Anything else I'm missing? Also, what drivers? The same ones I installed when I rooted the phone?
Thanks in advance guys!
scheirere said:
Ok, now I'm a little confused. I downloaded both files. The modded ENG bootloader and the RUU zip file from the links. But what order. Sorry but I'm not familiar with this stuff and don't want to dig myself into a deeper hole by bricking this thing.
Is this the proceedure?
1. adb reboot bootloader
2. fastboot oem rebootRUU (using the RUU_DLX_WL_JB_45.exe file?)
3. fastboot flash zip ModdedPL832IMG.zip
Anything else I'm missing? Also, what drivers? The same ones I installed when I rooted the phone?
Thanks in advance guys!
Click to expand...
Click to collapse
This first:
1. adb reboot bootloader
2. fastboot oem rebootRUU
3. fastboot flash zip ModdedPL832IMG.zip
4. Profit
making sure that the .zip is in the same folder as fastboot
then run the RUU after you reboot the phone.
Yes it should be the same drivers you used when rooting.
Looks like I spoke too soon on those downloaded files. The download of the RUU file bombed out on me and I didn't realize it. When I go back to the site in the link, and try to download the file now, it just sits waiting. I guess the site is down? Any other links or locations?
Downloads working now maybe keep trying they say they are under a DDOS attack. Here it is from hotfile but I can't confirm this as real.
HERE
OK, I got partway thru the steps. everything went well until I tried to fastboot flash the ModdedPL832img file. I get a message "writing 'zip'....FAILED (remote not allowed)"
Any ideas/suggestions?
scheirere said:
OK, I got partway thru the steps. everything went well until I tried to fastboot flash the ModdedPL832img file. I get a message "writing 'zip'....FAILED (remote not allowed)"
Any ideas/suggestions?
Click to expand...
Click to collapse
After step 1, but before step 2, do this:
fastboot devices
If you don't get a device id, then you don't have the proper drivers installed.
If you get a device id, then try step 2 again ...
If that doesn't work, then I don't know
Maybe try a different USB port on your computer also use the OEM cable if you can.
Thanks guys for the suggestions. Unfortunately, still no luck. Same results when flashing the Modded file. I did try adb devices as suggested and got the device ID. So I think the drivers are OK. I also tried another USB port just to see if it helped. No go.
Just because I'm pretty new to this stuff, here's a detailed list of what I'm doing.....
1.) ADB reboot bootloader (from a command prompt)
Phone reboots to bootloader screen with Fastboot USB in red, hightlighted.
The screen no longer displays the "TAMPERED" heading at the top. So it looks like I'm making some progress.
2.) fastboot oem rebootRUU (from a command prompt again)
Phone screen goes from white to black with nothing but a large HTC logo in white.
Nothing else happens at this point. I've let the phone sit for 30 minutes with no apparent change and nothing on the host PC.
I then went thru my computer to the directory were the RUU_DLX.... file resides and executed (double clicked) it. I get an RUU - InstallShield screen and then I go thru the HTC rom update utility steps. After a few steps the utility does it's thing and the phone then reboots.
3.) ADB reboot bootloader again
Phone reboots into bootloader screen
4.) fastboot flash zip ModdedPL832IMG.zip (from a command prompt)
Phone does nothing but the command screen returns:
sending 'zip' (485 KB)...OKAY [ 0.266s]
writing 'zip'...FAILED (remote: not allowed)"
pretty much immediately
Am I doing this correctly?
At this point the bootloader screen no longer says tampered. Can I just relock the bootloader so it's s-on again?
BTW, here's what the bootloader screen shows:
*** UNLOCKED ***
MONARUDO PVT SHP S-OFF
CID-22222222
HBOOT-1.33.0001
RADIO-1.00.00.1023_3
OpenDSP-v4.120.240.0920
eMMC-boot
Oct 23 2012,21:34:05
Or can I just send the phone back as it is?
Bootloader uses a different driver than ADB. My advise is to boot into the bootloader then verify in device manager that the driver is loaded. See attached. Flashing the RUU will not get you S-On you need a command to do that and I don't know what it is off the top of my head I have never used it.
this thread will let you unlock your bootloader without htcdev,or let you change your hboot watermark from relocked or locked back to stock.
originally,we used a zip file flashable in recovery. i have found it to work on gsm m7_ul devices with 1.44 hboot and CW recovery. it did not work with twrp. if the following is too scary,feel free to test the zip files. that thread,info,and downloads can be found here. since not all recoverys are working,these values can be changed with simple adb commands.
advantages
-no hassle with htcdev,tokens,or unlock codes
-no submitting your phones personal info to htc
-the ability to get back to 100% stock without any visual traces or records of having been s off or unlocking your bootloader.
prerequsites
*you must be s off.
*you must have superuser installed(see this thread if you need help installing superuser. use the keep bootloader locked directions)
read this:
this will not work if your s on. its not a way to magically unlock
the usual disclaimers:
use this info at your own risk. if it melts your phone into a little pile of aluminum goo,its not my fault.
it has been successfully tested on t6ul with MID 0P3P51000. i feel it is safe for other t6ul users,all MIDs,however,you are welcome to dump and we can verify the flag locations if you have concern.
if you have a different variant than t6ul,please pm me for more info prior to trying this.
credits
-beaups for giving me the echo comand,so yall didnt need to dump,edit with a hex editor,and copy back
-strace for originally discovering the location of the lock status flag(check out this thread for more info)
-kdj67f for fearlessly testing on vzw m7_wlv and putting up some screenshots in post 2. thanks!
-matthew0776 for fearlessly testing for sprint m7_wls
*pradeepvizz for getting the ball rolling for t6 users-dumping partitions,testing commands and providing screenshots. make sure to give him a big thanks
*[email protected] for testing on sprint t6
*droidrev71 and oneandroidnut for testing vzw t6
IF you are an advanced user with adb/fastboot set up and some basic knowlede of the cmd window,you can skip to #2
1)set up adb
-download this file
-install drivers: if you have htc sync installed,you should allready have drivers. if not,you can install htc sync,or install these modified htc drivers from revolutionary (driver mirror)
-unzip your miniadb_v1031.zip file. this is native funtionality in windows 7. you otherwise may need a utility such as "7-zip" to extract,or unzip it. place the unzipped folder onto the root of your C drive on your PC. root means the top level,not inside any folders. so just copy and paste,or drag and drop the folder onto C with everything else that is there. you may want to rename it to "miniadb_m7" since youll be putting some device specific files in here.
-open a command window. on windows 7,click the start bubble in the lower left and type "command" in the search box. xp i believe is similar or the same. doing this should open a small black command window.
-change to your miniadb_m7 directory. type the following at the prompt in your cmd window:
cd c:\miniadb_m7
your command promt should change to "c:miniadb_m7>" provided you: 1)unzipped the miniadb_v1031 zip file,and 2)put the folder on your c drive,and 3)entered the name of the folder correctly ("miniadb_m7" in this case)
-now make sure usb debugging is checked in developer options(you will need to turn it on first),and plug your phone into your PC with a usb cable
-make sure your phone is being recognized- type:
adb devices
if your drivers are installed correctly,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,then enter this command:
adb reboot bootloader
this should take your phone to the "fastboot" screen,wich is white with colored letters. this is one mode of your bootloaders interactive modes. at the top youll see fastboot devices as confirmation youre in fastboot.
now enter:
fastboot devices
again,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,you can enter the following to boot back to the phones OS:
fastboot reboot
and now,youve installed adb/fastboot and tested youre phones drivers. if at either spot,you have trouble and dont get your serial number back,there is some sort of connection issue. use these steps to troubleshoot:
troubleshooting connectivity issues:
-try a reboot of the PC
-try different usb cables and ports
-dont use a usb hub
-dont use usb 3.0
-make sure nothing capable of comunicating with the phone is enabled and running. htc sync,pdanet,easy tether,and even itunes have all been known to cause issues.
-windows 8 has been known to have issues. try a windows 7 or older machine
failing the above,
-i use these drivers for fastboot and adb(donwload and run as admin): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe (mirror)
failing that,try manually updating the drivers in the following manner:
-put the phone in fastboot mode(select fastboot from the hboot menu)
-open device manager on the PC
-plug in phone,watch for it to pop up in device manager.
-update drivers with device manager,pointing the wizard to the extracted
driver download folder from above
note that you can check the connectivity of the phone,and make sure drivers are working by in the following manner:
-open cmd window. change to directory containing adb/fastboot utilities
-adb with the phone in the booted OS,usb debug enabled,enter:
adb devices in a cmd window
-fastboot with phone in fastboot,enter:
fastboot devices in cmd window
in either case,a properly connected phone with working drivers installed should report back the phones serial number.
Click to expand...
Click to collapse
this process,in your cmd window,should look something like this:
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>[COLOR="red"]cd c:\miniadb_m7[/COLOR]
c:\miniadb_m7>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FAxxxxxxxxxx device
c:\miniadb_m7>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\miniadb_m7>[COLOR="red"]fastboot devices[/COLOR]
FAxxxxxxxxxx fastboot
c:\miniadb_m7>[COLOR="red"]fastboot reboot[/COLOR]
rebooting...
finished. total time: 0.037s
c:\miniadb_m7>
2)reset your "lock status flag"
to LOCK your bootloader,enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
verify you are now locked
_____________________________________________________________________________________________
to UNLOCK your bootloader,enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
verify you are now unlocked
Please Note:
*you must remove the tampered banner as well in order for the fingerprint scanner to work.
remove your tampered banner
This looks great! few quick questions before i attempt it. So will this let me get root and use of the finger print scanner? say if i unloocked installed custom recovery root all that, then relocked would the finger print scanner work? thanks very much!!!!
hectorz321 said:
This looks great! few quick questions before i attempt it. So will this let me get root and use of the finger print scanner? say if i unloocked installed custom recovery root all that, then relocked would the finger print scanner work? thanks very much!!!!
Click to expand...
Click to collapse
yes thats right.. i have got a custom recovery, root and a custom rom as well and i have LOCKED and also removed TAMPERED banner and i can use my fingerprint scanner happily
Thanks scott!! that was really quick work from you! i am glad that i choose to PM you and requested this!
hmmmm by looks of it you have to unlock with htc dev first to get s off, trying to install custom recovery without bootloader ulocked gives you an error
C:\max>fastboot flash zip recovery.zip
target reported max download size of 1554698240 bytes
sending 'zip' (7553 KB)...
OKAY [ 1.143s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 1.944s
hectorz321 said:
hmmmm by looks of it you have to unlock with htc dev first to get s off, trying to install custom recovery without bootloader ulocked gives you an error
C:\max>fastboot flash zip recovery.zip
target reported max download size of 1554698240 bytes
sending 'zip' (7553 KB)...
OKAY [ 1.143s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 1.944s
Click to expand...
Click to collapse
correct. youll need to be s off to install recovery as a zip file while locked.
custom made recovery zips do not have htc's official signiture required for s on flashing.
Can verify that this works to get fingerprint scanner working again on uk version of htc one max great work
I can also confirm that the unlock command works.. both of them works!
---------- Post added at 04:08 AM ---------- Previous post was at 04:04 AM ----------
@scotty1223 Will i need to UNLOCK in order to flash a zip from recovery? i am trying to flash elementx kernel zip which contains a zip file..
pradeepvizz said:
[/COLOR]@scotty1223 Will i need to UNLOCK in order to flash a zip from recovery? i am trying to flash elementx kernel zip which contains a zip file..
Click to expand...
Click to collapse
nope. should not have to. once youre s off,the normal unlock rules go out the window.
the ONLY reason you would have to be unlocked is if you wanted to use fastboot flash to install a recovery or kernel,or to use fastboot boot to temporarily boot a recovery.
zip files in recovery,or ruu zip files flashed from fastboot/ruu mode do not need the bootloader unlocked
scotty1223 said:
nope. should not have to. once youre s off,the normal unlock rules go out the window.
the ONLY reason you would have to be unlocked is if you wanted to use fastboot flash to install a recovery or kernel,or to use fastboot boot to temporarily boot a recovery.
zip files in recovery,or ruu zip files flashed from fastboot/ruu mode do not need the bootloader unlocked
Click to expand...
Click to collapse
Thanks Scott! i was trying to install flar2's elementalx's kernel from the One on our MAX and was getting bootloops sometimes and i was not sure if the kernel was installed..
I did try to install once with LOCKED and UNLOCKED.. the phone kept bootlooping ..
Tried it on my butterfly s and it worked too
Sent from my HTC Butterfly s using xda premium
for me it didnt work
i was unlocked via htc dev... locked it again and unlocked it with
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
but fingerprint sensor does not work ...
i have a german o2 phone !
B-Man2005 said:
for me it didnt work
i was unlocked via htc dev... locked it again and unlocked it with
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
but fingerprint sensor does not work ...
i have a german o2 phone !
Click to expand...
Click to collapse
deleted
---------- Post added at 02:15 PM ---------- Previous post was at 02:12 PM ----------
have you removed your tampered flag as well?
B-Man2005 said:
for me it didnt work
i was unlocked via htc dev... locked it again and unlocked it with
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
but fingerprint sensor does not work ...
i have a german o2 phone !
Click to expand...
Click to collapse
You must leave it locked. The phone is reacting to finding htcu
Sent from my HTC PG09410 using Tapatalk 2
daorderdillon said:
Tried it on my butterfly s and it worked too
Sent from my HTC Butterfly s using xda premium
Click to expand...
Click to collapse
again,not a good idea without any knowedge of what was in that spot.
Thanks Scotty . Worked great on my Sprint Max .I'm also s-off , rooted and using fingerprint scanner ??
Sent from my HTC0P3P7 using Tapatalk
scotty1223 said:
again,not a good idea without any knowedge of what was in that spot.
Click to expand...
Click to collapse
Don't forget to bring some other tricks to us too
Sent from my HTC Butterfly s using xda premium
Now is the time for everyone who has not donated to the great devs we have to break out their paypal! This initial great group of devs are helping us all out by creating a foundation for rom/kernel/whatever devs to provide us their magic from now on. Without these guys laying the framework none of that would be possible. Remember that we are very lucky that this mostly obscure device is getting the fabulous development support it is at this time. So show your support and DONATE!!
now make sure usb debugging is checked in developer options(you will need to turn it on first),and plug your phone into your PC with a usb cable
Click to expand...
Click to collapse
How do I enable USB debugging on my phone? I can't seem to find it in settings.
mustasusi said:
How do I enable USB debugging on my phone? I can't seem to find it in settings.
Click to expand...
Click to collapse
go to settings/about/software information/more/ and keep pressing build number until it says u r now a developer
daorderdillon said:
go to settings/about/software information/more/ and keep pressing build number until it says u r now a developer
Click to expand...
Click to collapse
Thank you very much +1!
They hid it well on 4.3...
General Information
This Has Been Made To Help Those How Have No Clue What There Doing When Upgrading There Firmware Note And Want A One Click That Mimiks HTC RUU
New From Prism Pirate Chest of goodies here it is FUU For The HTC Evo 3D
FUU Definition
Firmware Update Utility
There are a few Firmware flashing threads and lots of zips and good and bad instructions. However, i noticed that many users asked about what they get when they flash what they download and also about how to flash it with S-OFF on various threads. This confusion has occasionally lead to people losing their custom kernels and custom recoveries and/or their SDcard partitions being unintentionally wiped.
I am writing this because i believe in "responsible" sharing. Since the full RUU's aren’t shared but only components (modified as well as unmodified) with often insufficient documentation, which in turn leads to a lot of confusion among the lesser informed users, i will try to catch some of that. I believe that sharing full RUU's would be a lot safer, as only those who actually know enough about it can disassemble them. RUU’s do always reassure users that there is a guaranteed and safe way to go back.
FUU How To
[*]Download the firmware you want
[*]then run the installer
[*]install it to folder you want to any folder will do
[*]then run the tool and upgrade or downgrade your firmware
Prerequisites:All you need is a Windows System with current drivers and maybe HTC Sync Manager installed, it is better to have HTC Sync uninstalled and only the drivers left. Just try if the FUU runs without HTC Sync. On my system, i am always greeted with an “Error 170" if i try to run the FUU on a booted Android - it doesn’t recognize the phone with ADB. This is a typical driver and/or ADB error. Solution here: make sure you have the latest driver suite. FailSafe way to get them is to install HTC Sync Manager (remove it if you don’t like it afterwards but leave the drivers in the sytem!).
ZIP Flash HowTo
Step-By-Step:1. If device is booted into Android, reboot into bootloader by running:
Code:
adb reboot bootloader
1.a Or else, if your device is in a different state or you just prefer the button method:
Press Power for 15 seconds and hold Vol Down at the same time, when the screen and charging LED go dark immediately release Power but keep holding Vol Down until you see the bootloader screen. Notice: If the device refuses to reboot, you might need to hold it to a bright light with its light sensor. This is a very specific bug in the HTC ONE. The light trick always works.
2. Now place the Firmware_named_something.zip into your adb/fastboot folder
3. Now run:
Code:
fastboot oem rebootRUU
4. Followed by:
Code:
fastboot flash zip Firmware_named_something.zip
(replace "Firmware_named_something.zip" with the name of your zip)
5. Now check the console output. It should approximately look like this:
“flush" certainly means “Flash" so press the arrow up key on your keyboard and enter to run the flash command again without reboot...
Important: the flash process halts at around 75% to 90% on phone screen! This is normal and a safety precaution! The last few percent is the reboot, which is NOT happening automatically, so you get a chance to check the console output before reboot to make sure it is safe to reboot! The bar will only fill up to 100% once you type the following command:
6.
Code:
fastboot reboot-bootloader
Error handling strategies:IF IT SAYS "FAILED" do not immediately reboot the device If you reboot with a FAIL it could not boot up anymore! It could brick! If no flash is being accepted you have to find out what is causing the malfunction before rebooting your phone. Keep it alive while trying to figure out the error. It might be your cable, your USB ports (dont use hubs! Always straight-to-mainboard connections), it might be USB 3.0 which is not good yet, it might be bad configuration of your ADB and Fastboot... there are many possible sources for flash fails.
The least dangerous FAILED messages are listed below and are safe to reboot:
Safe to reboot / Flash didn't happen Errors (if you encounter one of them, you can just reboot. Nothing changed):
- 12 signature fail (unknown yet but safe to reboot)
- 23 parsing image fail (means something wrong with the image in the zip)
- 32 header error (means the zip couldn’t be read and unzipped properly)
- 41 Wrong Model ID (means its not the right device)
- 42 Wrong Customer ID (wrong CID means you gotta swap cid first as explained below)
- 90 hboot pre-update (means it only flashed hboot and you have to run the process again immediately to flash all other partitions WITHOUT a reboot inbetween).
- 99 UNKOWN (is not yet clear but safe to reboot, might indicate a defunct S-OFF or S-ON)
- 155 you did not lock your bootloader (Needs a relock for S-ON phones that want to update the firmware.)
In fact, if it aborts before the "(bootloader) start image[hboot] unzipping & flushing..." line it actually didn't write anything and you can probably just reboot. If you see it flashing stuff though (the stages after that line) and then it stops with a FAILED, chances are a little higher that something is now broken. In that case do NOT reboot but do as i said above.
For Error 12 “signature fail" do:
- might indicate that a signed firmware package is required. This would only happen with S-ON phones though.
For Error 23 "parsing image fail" do:
- change image names in the zip to stock image names like “hboot.img" or “radio.img" or whatever failed there....
For Error 32 "header error" do:
- Sorry i haven’t found the exact cause yet and don’t know a definite solution.
- Make sure there is only one . (dot) in the filename, before the extension. fastboot reads anything after the first dot it sees as the extension. If that is not zip, it fails.
- If that doesn’t help, you can also try: make the zip new with recommended settings, re-run the command, check your connections...
For Error 42 "Wrong Customer ID" and: 41 "Wrong Model ID" do:
Code:
fastboot getvar all
Read that output, take note of your CID and MID and then edit the "android-info.txt" in your firmware.zip accordingly (For Wrong MID change the MID in the text, for wrong CID add your CID to the text).
For “Error 90 hboot pre-update..." do:
- Run the same flash command again which you just ran (press arrow up on your keyboard to get to the previous command in console)
- Don’t reboot in-between! (It wouldn’t brick you but it would just make you run the flash command twice again)
- This might be caused by the newer encrypted RUU's, they need their hboot to be flashed first so it can then decrypt the rest of the ROM.zip. Look at an encrypted ROM.zip from a RUU, you will notice that you can mostly extract the hboot without decrypting the ROM.zip, but you can't extract much else.)
For “Error 99 UNKNOWN" do:
- Check with other zip’s if they work!
- Check if your S-OFF is correct
- Tell me if you find out what’s causing an unknown error here!
For “Error 155 relock bootloader" do:
- run the fastboot command “fastboot oem lock" - only applies to S-ON phones that want to update the firmware. There a relocked bootloader is required. This error won’t show on S-OFF phones.
- Error 155 can also mean that you need SuperCID. On a few occasions this was shown when the RUU/FUU refused to run because of wrong region lock.
For “Error 170 Check USB" do:
- Sometimes shown when running a RUU or FUU. Indicates issues with drivers or ADB/Fastboot binaries. One way to solve is to run the exe with the phone already in Fastboot mode. Else you will have to dig into your windows driver system and try to fix there. Best option: re-install HTC Sync manager. Also, avoid USB 3 ports (the blue ones) - they have a complete new driver stack and that doesn’t work with ADB and Fastboot.
I always test all of these zips on my own device. But as always, flash at own risk. You're writing to critical parts of your phone. If anything goes wrong along the way, you might be bricked.
FUU Downloads (Windows only)
Update: added Hboot 1.58 FUU
Download
MD5: 995a8b883a5e39af471a93a84b4ff52d
This FUU is A Stock Hboot. Contents: Firmware from ramjet73 So You should be good to Go. This package does wipes SDcard So Remove It Be For you Run it.
Update: added Hboot 1.57
Download
MD5: 87acbac59f169b32900e58f34e3390e1
This FUU is A Stock Hboot. Contents: Firmware from ramjet73 So You should be good to Go. This package does wipes SDcard So Remove It Be For you Run it.
Update: added Hboot 1.50
Download
MD5: 233943ae4117d2fe64726afed8231b18
This FUU is A Stock Hboot. Contents: Firmware from ramjet73 So You should be good to Go. This package does wipes SDcard So Remove It Be For you Run it.
Update: added Hboot 1.40
Download
MD5: 054e40f479b2075a20f12d5426d44bc3
This FUU is A Stock Hboot. Contents: Firmware from ramjet73 So You should be good to Go. This package does wipes SDcard So Remove It Be For you Run it.
Update: added Hboot 1.30
Download
MD5: 04b13923379267a82d93cf913de62040
This FUU is A Stock Hboot. Contents: Firmware from ramjet73 So You should be good to Go. This package does wipes SDcard So Remove It Be For you Run it.
Update: added Hboot 1.04 ENG
Download
MD5: 476a819ce37ff8fae2960de9dc2969a2
This FUU is A Stock Hboot. Contents: Hboot from ramjet73 So You should be good to Go. This package does wipes SDcard So Remove It Be For you Run it.
CreditsThank You Sneakyghost For The Tool And The Op
ramjet73 My mentor for HBOOT Modding
ramjet73 For The Hboots Witch I Modify Of off
DisclaimerYou are aware that writing to the security protected partitions increases your risk to lose the device exponentially. You understand and agree that i cannot be held responsible for such or any other damages. The flash process is theoretically safe and tested on various phones at time of posting, however you are the brains behind the wheel and you are solely responsible for the execution of the process. I will not accept any responsibility. The method itself is developed by Google and HTC, i only provide access and information to it and you execute it.
You understand that you should not do it if you are not willing to accept this risk.
Five star guide flashalot much appreciated
Sent from my PG86100 using XDA Premium 4 mobile app
Nice job!! Thank you!
busventinc said:
Five star guide flashalot much appreciated
Sent from my PG86100 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Cant take credit for the guide thank @Sneakyghost
I just made the proper edits for the evo and my one s
newdad23 said:
Nice job!! Thank you!
Click to expand...
Click to collapse
No problem
Thanks so much for this Flashalot!
Question on these, apologize in advance if its off base or nonsense.
Currently have a friend who is running 1.58 hboot S-ON, unlocked bootloader (htcdev) with MIUI 3.2.22 ROM. Would it be possible to use these to downgrade his hboot version and run revolutionary S-OFF and/or install JB ROM? Or would it be best to relock, revert fully to stock and use JuopunutBear method?
Thanks in advance
snackle said:
Thanks so much for this Flashalot!
Question on these, apologize in advance if its off base or nonsense.
Currently have a friend who is running 1.58 hboot S-ON, unlocked bootloader (htcdev) with MIUI 3.2.22 ROM. Would it be possible to use these to downgrade his hboot version and run revolutionary S-OFF and/or install JB ROM? Or would it be best to relock, revert fully to stock and use JuopunutBear method?
Thanks in advance
Click to expand...
Click to collapse
This is for s-off only sorry this is what you need
http://forum.xda-developers.com/showthread.php?p=31617712 it has it instructions on how to s-off
Sent from my PC36100 using Tapatalk 2
Flashalot said:
This is for s-off only sorry this is what you need
http://forum.xda-developers.com/showthread.php?p=31617712 it has it instructions on how to s-off
Sent from my PC36100 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the quick reply Flashalot
Exactly what I was expecting but figured I should ask just in case. Thanks again for your time.
snackle said:
Thanks for the quick reply Flashalot
Exactly what I was expecting but figured I should ask just in case. Thanks again for your time.
Click to expand...
Click to collapse
FYI, depending on the current firmware level of the phone you may not be able to run an ruu after the 2.89 base (they don't exist) without being s-off. If jbear doesn't work for you see..
See my reference post in Unknownforce's Ultimate Unbricking and hboot Downgrade Tool thread. It is known to work by bricking it twice.
Sent from my TouchPad using Tapatalk
mpgrimm2 said:
FYI, depending on the current firmware level of the phone you may not be able to run an ruu after the 2.89 base (they don't exist) without being s-off. If jbear doesn't work for you see..
See my reference post in Unknownforce's Ultimate Unbricking and hboot Downgrade Tool thread. It is known to work by bricking it twice.
Sent from my TouchPad using Tapatalk
Click to expand...
Click to collapse
Thanks for the heads up mpgrimm2. I believe he has a nandroid backup from just after he completed the htc unlock, still running stock rom. If it does turn out to be 2.95.651.6, would he able to restore this nandroid and continue with jbear method?
I know jbear will need to be mostly stock if not full stock. That nand backup may work depending on if jbear requires a relock and stock recovery or not but I don't recall. Things got a little vague when they moved support off of xda to their own site and stopped supporting windows based installers.
I'm sure Ramjet73 had some FAQ's in his thread for the old windows version that would answer it though.
Either way I know Unknownforce's Tool will work for s-off.
Sent from my "Up All Night Sleep All Day" Nexus 5!