Related
Hi!
Yesterday i managed my Flyer to S-off via revolutionary tool.
Today i wanted to update to Honeycomb with this tutorial:
+
Google search: android.modaco.com Installing Honeycomb on your Flyer
Guide from Paul.
i got now stuck after the htcdev bootloader unlock.
i should transfer the cwm recovery file via fastboot into the flyer
command: fastboot flash recovery revolutionary-cwm-4.0.1.4-flyer.newhboot.img
Code:
< waiting for device >
sending 'recovery' (4682 KB)...
OKAY [ 0.753s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.198s
Why this is failed? i tried to do the next step, getting into clockworkmod recovery but nothing happens.
My Flyer shows now:
Code:
*** RELOCKED ***
*** Security Warning ***
FLYER PUT SHIP S-ON RL
HBOOT-1.11.0006
MICROP-0950
RADIO-3821.08.00.26_M
eMMC-boot
Aug 29 2011, 13:32:02
Fastboot 9v AC (because charging)
VOL UP
VOL DOWN
POWER
Bootloader
reboot
reboot bootloader
power down
What can i do now? any idea?
edit: adb don't work, fastboot works.
I'm going crazy tried to reunlock bootloader via htcdev. When i flash the unlock token i get same error
Code:
C:\Users\h0f1\Desktop\htc\android-sdk_r15-windows\android-sdk-windows\platform-t
ools>fastboot flash untlocktoken Unlock_code.bin
sending 'untlocktoken' (0 KB)...
OKAY [ 0.015s]
writing 'untlocktoken'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.019s
Why in the world would you use the htcdev unlock? Go to flyer development and follow globatron's honeycomb guide. Much better than voiding your warranty.
Sent from my PG86100 using Tapatalk
i did yesterday exactly those steps from globatron for soff and cw recovery.
For getting Honeycomb i used another guide yesterday.. because i found this site today..
I really dont know what to do now
Worst case run ruu of your stock software
Sent from my HTC Flyer P510e using xda premium
somehow it doesnt work
C:\Users\h0f1\Desktop\htc\android-sdk_r15-windows\android-sdk-windows\platform-t
ools>fastboot flash untlocktoken Unlock_code.bin
sending 'untlocktoken' (0 KB)...
OKAY [ 0.013s]
writing 'untlocktoken'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.017s
edit:
made it now with other version of fastboot... this is crazy..
so i unlocked again and now i can go on with the other steps?!
I would return to stock then use globatrons update method. Do you know your stock ruu
Sent from my HTC Flyer P510e using xda premium
is going back to stock via ruu possible when i changed hboot, radio and boot file?
the guide from paul says:
Do NOT under any circumstances run the RUU in it’s entirety nor ‘fastboot flash rom.zip’ – this will make irreversible changes that you don’t want!
Be careful if you flash any RUUs or do anything that could revert you to S-ON on a broken system – this could leave you stuck
i think i will recharge and go through the last 4 points..
im afraid
Try to get a new unlock token.
I can not see why running your ruu to stock.would be an issue but I am not 100% certain. I did a revert last week and the only thing I needed to do prior was relock hboot first which you are already locked.
Sent from my HTC Flyer P510e using xda premium
first i wanna say thanks for your help!
i did today the last two steps after recharging the battery.
last 2 steps are putting the new image onto sdcard via adb and second step was factory reset und dalvik wipe. All two steps worked fine for me, but after restart the flyer is going to a bootloop.
what should i do now?
Should i get back with the RUU?
Can i setup honeycomb after getting back with ruu with the tutorial from globatron?
best regards
tom
did you flash the zip through recovery
Sent from my HTC Flyer P510e using xda premium
^the tutorial say get into clockwork recovery mode and type into command "adb shell mount /sdcard && adb push stock-hc-flyer-system.zip /sdcard/"
this command finished after 3 minutes and i was also lookin at the sd card the file is on the sd card.. after this i wiped dalvik and made a factory reset in the clockwork recovery mode. Afterwards Reboot -> then bootloop
lool is it possible that i have to " install zip from sdcard" ? if yes i'm the dumbest flyer user on the world *g*
edit: i tried now to install the update via recovery, it says E: Can't open /sdcard/stock-hc-flyer-system.zip (bad)
h0f1 said:
lool is it possible that i have to " install zip from sdcard" ? if yes i'm the dumbest flyer user on the world *g*
edit: i tried now to install the update via recovery, it says E: Can't open /sdcard/stock-hc-flyer-system.zip (bad)
Click to expand...
Click to collapse
Re-download, it's corrupt.
ikingblack said:
Re-download, it's corrupt.
Click to expand...
Click to collapse
+1
Sent from my HTC Flyer P510e using xda premium
really i promise i will neveer ever never try to flash/hack/root anything. its just horrible thinking all the time you brick it or anything else xD
i tried to reboot bootloader via adb in the recovery mode, flyer turned off and now nothing happens. cant go into bootloader or something else.. trying to recharge again, maybe battery is low again (i hope..)
well i will go on tomorrow evening.
great work guys anyways, thanks
tom
h0f1 said:
really i promise i will neveer ever never try to flash/hack/root anything. its just horrible thinking all the time you brick it or anything else xD
i tried to reboot bootloader via adb in the recovery mode, flyer turned off and now nothing happens. cant go into bootloader or something else.. trying to recharge again, maybe battery is low again (i hope..)
well i will go on tomorrow evening.
great work guys anyways, thanks
tom
Click to expand...
Click to collapse
I don't know if it's possible to really stop it from booting or displaying anything on the screen. Recharge and once it's done hold power button for a long time.
Good Luck
help fully bricked htc flyer p510e
here is what i did step by step:
bought an htc flyer, then upgraded it officially to honeycomb
i did not like honeycomb so i unlocked bootloader with htc dev method
then flashed recovery and rooted....
changed the misc_version and downgrade back to gingerbread with fastboot flash zip rom.zip
it worked........gta 3 and gta vice city worked.......few months later the gta 3 and vice city started crashing( just like honeycomb)
so i got s-off with revolutionary.....and flashed honeycomb PG41IMG.zip
that worked...........few months later i wanted gta back so i could not take i tried flash back down but did not work...it would get stuck in RUU mode ...so i flashed PG41IMG.zip back and that worked ..i was not bricked...so i tried another method
i flashed fastboot express downgrader.nb0 and
flyer downgrader.nb0
then changed gingerbread rom.zip to PG41IMG.zip and placed it on sd card
went into bootloader and let it flash
the bootloader at this moment:
***security warning***
pvt chip s-on
hboot 1.10.000
..................
it does not show whether the bootloader is locked or unlocked......no recovery.......tablet does not boot.....only to bootloader and fastboot.....
i tried to flash the unlock token for bootloader but get
signature failed error....
i tried to flash the honeycomb PG41IMG.zip but get
checking header failed
remote[signature failed]
cant flash anything because of that ...cant flash recover to even turn off the verification signature check.....
plz help ...whether you help me to fix it back to gb or hc to dont care ..just want it to work
plz help me fast
battery charges but phone goes into fastboot .....
plz help
just ask if u need more information on the situation..
plz anyone
Should probably find a good RUU that is compatible, create a gold card and do a clean re-load of compatible ROM.
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
Hi,
Well, i got myself into this mess and after 3 days of trying to fix it, i give up and call for your assistance.
I had a working S-ON HBOOT 0.47 rooted Legend running CM7.2 and recently changed to Jelly_Bean_Extras_HomICS_2.0_Venus.
I liked the new rom but link2sd didn't work.
My guess was that i need to have it S-OFF.
So... i headed to HTCDEV but first i needed to be on one of the listed RUU.
My original RUU was RUU_Legend_HTC_ISR_2.05.461.52_Radio_47.39.35.09_7.08.35.21_release_140015_signed.zip
I used the LEGEIMG.zip method to flash the RUU and then i flashed the one from HTCDEV which holds "hboot_legend_7227_1.02.0000_111223.nb0" only.
Now the HBOOT got to be 1.02.0000
After flashing this, i got stuck.
No recovery - i get signature failed message - even after putting CWM update.zip on the SD.
No ADB - at all states, only fastboot sees the device.
RUU update gets fails either due to version 3.30.0000, signature or device.
fastboot flash - i thought i will manually flash the various parts. i get FAILED (remote: signature verify fail).
CID was HTC__K18
did a new goldcard based on the old mail i had (from 2010) with the goldcard file (thank you gmail).
but nothing seems to help.
I read a lot of forum posts and tried many things over these 3 days but i'm willing to start over, step by step, with anyone willing to assist.
Hopefully this step by step will assist me and will be a reference guide for others.
Guy
guyvago said:
Hi,
Well, i got myself into this mess and after 3 days of trying to fix it, i give up and call for your assistance.
I had a working S-ON HBOOT 0.47 rooted Legend running CM7.2 and recently changed to Jelly_Bean_Extras_HomICS_2.0_Venus.
I liked the new rom but link2sd didn't work.
My guess was that i need to have it S-OFF.
So... i headed to HTCDEV but first i needed to be on one of the listed RUU.
My original RUU was RUU_Legend_HTC_ISR_2.05.461.52_Radio_47.39.35.09_7.08.35.21_release_140015_signed.zip
I used the LEGEIMG.zip method to flash the RUU and then i flashed the one from HTCDEV which holds "hboot_legend_7227_1.02.0000_111223.nb0" only.
Now the HBOOT got to be 1.02.0000
After flashing this, i got stuck.
No recovery - i get signature failed message - even after putting CWM update.zip on the SD.
No ADB - at all states, only fastboot sees the device.
RUU update gets fails either due to version 3.30.0000, signature or device.
fastboot flash - i thought i will manually flash the various parts. i get FAILED (remote: signature verify fail).
CID was HTC__K18
did a new goldcard based on the old mail i had (from 2010) with the goldcard file (thank you gmail).
but nothing seems to help.
I read a lot of forum posts and tried many things over these 3 days but i'm willing to start over, step by step, with anyone willing to assist.
Hopefully this step by step will assist me and will be a reference guide for others.
Guy
Click to expand...
Click to collapse
Have actually flashed hboot 1.02 yet?
Have followed ALL the instructions at htcdev?
Have you followed all the instructions sent to you via email about how to unlock the locked hboot 1.02, the email also includes a unlock.bin attached to the email which you need in order to unlock your boot loader?
If you had read ANY of the other question thread about this subject (there are a few) you would have found out that after you unlock your boot loader with hboot 1.02 you can no longer use update.zip cwm recovery, you can only use the S-OFF recovery method...
Sent from my Legend using xda app-developers app
I was expecting feeling stupid, missing something simple.
Originally, I couldn't get to step 8 since it requires that the unit didn't respond to fastboot command and while trying to find a fix, i got stuck with only fastboot and didn't remember that this was the step i was stuck in.
Anyway, your response had me go back to htcdev just to prove my point and i found that i can continue.
Finally.
Now i am unlocked and can continue with S-OFF methods.
Thank you.
Guy
Currently the phone starts with:
*** LOCKED (OOW) ***
LEGEND PVT SHIP S-ON
HBOOT-1.02.0000
MICROP-0816
TOUCH PANEL-SYN07_0103
RADIO-7.08.35.21
Dec 23 2011, 16:36:48
Guy
Have actually flashed hboot 1.02 yet?
Have followed ALL the instructions at htcdev?
Have you followed all the instructions sent to you via email about how to unlock the locked hboot 1.02, the email also includes a unlock.bin attached to the email which you need in order to unlock your boot loader?
If you had read ANY of the other question thread about this subject (there are a few) you would have found out that after you unlock your boot loader with hboot 1.02 you can no longer use update.zip cwm recovery, you can only use the S-OFF recovery method...
Click to expand...
Click to collapse
Guess what, your phone is still locked, you typed it yourself, you still need to unlock it using the bin file sent to you in the email.
Don't feel stupid mate, this rooting thing can be confusing and fearsome at times. Even I had that "can't use update.zip" issue and thought my phone was f'ed till I realised I needed to flash the recovery image.
Sent from my Legend using xda app-developers app
ok.
now everything is ok.
flashed cwm.
got the rom back
and restored almost everything.
thank you
just to point out
Jelly_Bean_Extras_HomICS_2.0_Venus is not ROM
If you flashed a good ROM and your stuck in hboot, use fastboot and use the following command 'fastboot oem boot' that should force your phone to boot.
Hey, I am trying to root my HTC evo 3d phone with hboot 1.58. I followed all 12 steps on htcdev.com, except on the final step I punch in: fastboot flash unlocktoken Unlock_code.bin and enter, then noting happens. The phone is supposed to reboot with the unlock option..but nothing happens
Also, the phone is Sprint CDMA if that makes any difference, so no sim card
....................................................................................................................................................................
THREAD SUMMARY
K finally got th phone rooted so here is what you have to do. The following applied to my ***locked*** S-ON Sprint HTC Evo3d with hboot 1.58 but should work with any other version higher than hboot 1.40.
The purpose is to get S-OFF(ROOT the phone) and also continue to use your factory HbOOT 1.58 and main version in the end.
1. Brick the phone carefully following steps outlined in unknownforce's [TOOL] Ultimate Recovery Tool 3.1 (Unbrick, Downgrade, VM Radio Fix/Reset). Scroll down to the "Downgrade/Unbrick" section and begin the bricking process with the PG86IMG.zip he mentions in "things you'll need".(place the zip on SD card in the main directory and name it PG86IMG)
2. Once phone is bricked(indicated by SOLID and very dimly lit charge light with the AC charger connected. Also the phone will not turn on or boot), download latest version of URT 3.1(first link in [TOOL] thread), continue to the second step 2 which involves booting up with Linux live boot CD on your PC, OR you can use URTLiveCD 1.0 and you will not need Linux
I did it the hard way an used latest version of URT with Ubuntu v12.04 LiveCD. I would recommend URTLiveCD 1.0 as you will boot straight to the tool and will not need the Ubuntu terminal.
3. After successfully completing downgrade with URT 3.1 downgrade, boot up to your new HBOOT 1.40 bootloader screen and enter fastboot USB mode. CHECK THAT THE MAIN VERSION HAS BEEN LOWERED ALONG WITH THE HBOOT.
Log back into windows
3.(A) If you haven't done this yet, get a fastboot PC command directory to retrieve all phone identification info from the bootloader. I used ROOTEVO3DNEW to check my phone's identity info at this point(though there are many programs that do the same thing). Create a new folder in C:\ and name it rootevo3dnew. Unzip all rootevo3dnew.zip contents into that folder.
Now open the command prompt with the phone connected to PC in fastboot USB. Type cd \rootevo3dnew and enter. Now type the following: "fastboot getvar all" (without quotations) and enter. A list should appear. Check that you have: (bootloader) version-main: 0.01.651.1. If this number is still 2.95.XXX.XXX or something close to it, then YOU MUST BRICK THE PHONE AGAIN. See posts starting at #35 of this thread for a more detailed guide through the second brick. It may be very tricky but very much the same process!!!!!
4. After successfully lowering HBoot to 1.40 and the main-version to 0.01.651.1 you can run the 1.13 RUU.exe found HERE: http://d-h.st/h1p . Connect the phone to fastboot USB and RUN the .exe....after the 1.13 .exe successfully runs, your main version should now be 1.13.651.7...again, checking using your rootevo3dnew tool from 3.(A) above....
5. REVOLUTIONARY S-OFF. Very simple, download for windows(or Linux) and fill in your info and retrieve you BETA key. Run REVOLUTIONARY application (which will run in the command prompt) and after successfully completely revolutionary S-off, YOU ARE ROOTED...continue to step 6
6. RESTORE your main version to 2.95(from 1.13) by running the 2.89 zip (HERE . Place this .zip in your main directory(RENAME IT PG86IMG) on the SD card and let it unzip and install it from the bootloader.
After that, you are pretty much finished!! boot up to android(main version 2.89) and let system updates detect and bring you back to 2.95.xxx.xxx..
....
Download and Install a custom recovery. Rename that .zip PG86IMG and install from bootloader as you did with the 2.89 zip. Now you have a custom recovery where you can backup and restore, install ROMS or other software without having to rename it PG86IMG every time, wipe partitions and lots of other stuff...
Now, download this and place it on your SD main directory. Then, using your new recovery(by selecting "recovery" in bootloader menu), select "install from sdcard" and "choose zip from sdcard", select the SuperSU zip and let it install. Reboot, get to homepage, and install SuperSU from the play store. You now hae an administrative super APP that will let you choose which apps are given root access.
Custom ROMS can be installed the same way from the custom recovery. I am currently using Negalite BluRom and loving it
...
THE 6 STEPS OUTLINED HERE PRETTY MUCH COVER EVERYTHING FROM THIS THREAD
HUGE THANKS TO USERS MPGRIMM2 AND BRIAN706 FOR NEARLY 3 DAYS OF HARD WORK !!
Did you get your motherboard replaced at some point of time?
Can't think of a good sig
donkeykong1 said:
Did you get your motherboard replaced at some point of time?
Can't think of a good sig
Click to expand...
Click to collapse
My what? Yes I swapped out my 67370m dv6 pavilion mainboard for radeon HD 6550m graphics chipset. How did you know?
otto325 said:
My what? Yes I swapped out my 67370m dv6 pavilion mainboard for radeon HD 6550m graphics chipset. How did you know?
Click to expand...
Click to collapse
On the phone?
Can't think of a good sig
donkeykong1 said:
On the phone?
Can't think of a good sig
Click to expand...
Click to collapse
Oh ok, what the hell..No, I just got the phone on ebay for $30, currently locked and I am trying to root it. Some Brittney girl owned according to phone identity info left on the phone
Do I need to downgrade the hboot from 1.58 to 1.4? Sorry I'm really new to smartphones, any help is really appreciated
Just in case it was missed, the phone doesn't reboot upon flashing the unlock token. A prompt should appear on the device and you have to confirm the bootloader unlock.
He asked about the motherboard, because there is an issue if the motherboard has been swapped; sometimes the bootloader will not unlock. I think it's due to mismatched firmware.
Usually running the RUU will solve the issue.
You can download a copy here: https://copy.com/jF1Mm
The only problem is, if the phone had taken the latest Ota update and you are on main version 2.95 instead of 2.89, the RUU will not run because it won't let you downgrade.
You can also check your main version by running a fastboot getvar all.
Is there any chance your device is already s-off from a previous owner? It will say s-on or s-off on the bootloader screen.
If you're lucky enough to already have s-off, you can skip the bootloader unlock altogether.
Brian706 said:
Just in case it was missed, the phone doesn't reboot upon flashing the unlock token. A prompt should appear on the device and you have to confirm the bootloader unlock.
He asked about the motherboard, because there is an issue if the motherboard has been swapped; sometimes the bootloader will not unlock. I think it's due to mismatched firmware.
Usually running the RUU will solve the issue.
You can download a copy here: https://copy.com/jF1Mm
The only problem is, if the phone had taken the latest Ota update and you are on main version 2.95 instead of 2.89, the RUU will not run because it won't let you downgrade.
You can also check your main version by running a fastboot getvar all.
Is there any chance your device is already s-off from a previous owner? It will say s-on or s-off on the bootloader screen.
If you're lucky enough to already have s-off, you can skip the bootloader unlock altogether.
Click to expand...
Click to collapse
THANKS
main version 2.95.651.5. If I factory reset the phone and discard updates, will the main version reset to 2.89 making the RUU possible?
EDIT: factory reset and no updates did not bring main version down to 2.89
***LOCKED***
SHOOTER XC SHIP S-ON RL
HBOOT-1.58.0000
eMMC-boot
May 17 2012, 15:06:44
Also check most recent post (#508) in the guide thread.
http://forum.xda-developers.com/showthread.php?t=1889438&page=51
Factory reset won't affect your main version
As DK mentioned, a factory reset only resets your current build. It would only take you back to the point of the last OTA update.
Unfortunately, you can't lower the mainversion without the bootloader unlocked, so it's a catch 22 there.
As a long shot, you might look into the new towelroot, thought I really don't think it will work for this phone because HTC locks down the /system partition. It would at least be worth looking in to.
As far as the hboot downgrade method (I assume you mean THIS) it was intended to downgrade from 1.50 Gingerbread to 1.40 Gingerbread. I have no idea if it will work to downgrade from 1.58 ICS?? You might want to ask around a little about that.
Okay... I just saw your posts in the other thread, have you actually received the unlock token from HTC?
IE, you received a file via email named Unlock_Code.bin that you placed in your fastboot directory and then typed the command: fastboot flash unlocktoken Unlock_code.bin ??
Also, when you say nothing happens after running the command, something must happen whether it's the intended results or not. Can you tell us what the command prompt returns after running the command? Maybe just copy/paste it here.
There will either be an error or a confirmation after running the command.
Comes up as successful on the command prompt. But the phone does not reboot or direct to the unlock screen. I just remains on the fastboot USB screen and does nothing.
C:\rootevo3dnew>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.153s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.010s]
finished. total time: 0.163s
Thanks for that... That's a bummer. Looks to me like you have the motherboard swap issue. It really sucks that you can't RUU.
It looks like someone answered the question in the other thread though about the hboot downgrade method.
So I got the HBOOT downgrade(0.8.2) boot for a disk but it says the phone needs to be bricked before the downgrade..
That's where I'm at now basically, I'm going to do a little more reading on bricking...
Also would be good to have confirmed that this downgrade will work starting with hboot 1.58, so I don't mess anything up
mpgrimm2 may have found found his way over here from from the [Guide] thread
Also I hope I am downloading the correct RUU's. I had to fish them from various searches because the link supplied in Unknownforce's thread is invalid:
2.17 RUU:
http://d-h.st/ru0ow8ps0i01/PG86IMG_2.17.651.5.zip
1.13 RUU:
http://d-h.st/Xrp
mpgrimm2 said:
Well. Post that in Unknownforce's Ultimate Recovery Tool thread so you are not "off topic" here.
I haven't used the Evo3d in a while but you should probably look over my ...
Post 781 in Unknownforce's thread and the follow up posts right after.
Additional info you may need from my
[Guide]My Hboot 1.5x HTC Unlock/recovery/rom/kernel flashing notes 2-13-13
and
Post 11. My Gathered RUU .exe/.zip Links (& How to extract RUU zip yourself)
Click to expand...
Click to collapse
Fyi, I think Unknownforce indicated in one of his first 3 posts that u can brick with the last 2.95 PG86IMG.zip file he linked and then downgrade to 1.13 for s-off. Have to go check...
Keep in mind that you may want to considering posting any issues with the URT/Downgrade tool in Unknownforce's thread if you want any chance of assistance from him.
Bad link in his op but this post has it...
Unknownforce said:
Well, with the 2.95 OTA, they included the HBOOT in the firmware, so it's now much faster of a load time for PG86IMG when doing the brick.
I pulled the new PG86IMG.zip from the OTA update, and it's only 19MB, which takes only 15-20 seconds to fully load and be ready to press volume up to update... this will significantly cut down on the time it takes to downgrade, as you can re-try over and over very quickly now.
Here's the PG86IMG file -> http://d-h.st/3p8
Click to expand...
Click to collapse
And just as a reference for you later I will quote myself from Ramjet73's 2.95 ota update thread
mpgrimm2 said:
ramjet73 and others. I see we still don't have any source for the 2.95.651.6 RUU's. Since I just went ahead and reset my 2 Evo3d's back to stock/S-off as a backup here are the files I had to step through if you want to add or host them directly:
- PG86IMG 2.89.651.2.zip - 449.18 MB
Full RUU.zip for use in bootloader (rename to PG86IMG.zip & place on /sdcard)
- OTA_Shooter_ICS_35_S_Sprint_WWE_2.95.651.5-2.89.651.2_release_307948lagg6bmccb9c63ip.zip - 51.11 MB
2.89.651.2 update to 2.95.651.5 zip for use in bootloader (rename PG86IMG.zip & place on /sdcard ) or stock recovery (place in /sdcard/download )
This is the last official update that just downloaded to my phone after the other Ruu's/updates that were posted previously
- OTA_Shooter_ICS_35_S_Sprint_WWE_2.95.651.6-2.95.651.5_release_315505rm3j000awvlstw9z.zip - 10.59 MB
2.95.651.5 update to 2.95.651.6 zip for use in bootloader (rename PG86IMG.zip & place on /sdcard ) or stock recovery (place in /sdcard/download )
Wish someone with HTC/Sprint access would post up the latest full RUU. It was a bit of a pain stepping through the updates, but definitely easier being s-Off. Seems that if someone is S-On with the 2.95.651.6 update and can't get past step 13 of the HTC Unlock or needs to RUU back, their only option is Unknownforce's Hboot Downgrade Ultimate Toolkit and "Brick it Twice" to get back to an earlier version for Revolutionary S-Off and then go through the updates from 2.89 on up.
Hope this helps others.
EDIT:
I may be too tired at the moment to figure this out, but for some darn reason both the official OTA Updates would not flash from the bootloader on a stock 2.89.651.2 phone with S-Off (both phones actually). Didn't matter if it was renamed PG86IMG.zip or left as officially downloaded to sdcard/download and booting into the stock recovery. The MD5 of my 651.5 update file matches Ramjet73's as well. But If I connect to wifi, do a system update, let it download (how I got the files) and reboot automatically, it works fine and updates without issue.
Click to expand...
Click to collapse
Forgive me for being such a noob with this stuff.
I'm reading about hboot 1.58 needing to be bricked twice to be able to run the 1.13 RUU.
So to start, do I place the 18.7mb PG86IMG .zip (from the second quote in your last post) in the "download" folder of the sd card?
The stock
(OTA_Shooter_ICS_35_S_Sprint_WWE_2.95.651.6-2.95.651.5_release_315505rm3j000awvlstw9z)
Click to expand...
Click to collapse
is there, so do I remove that one and replace it?
I don't think so but just to be sure, I drop the 18.7 PG86IMG zip folder in downloads and begin the brick process, then run the hboot 0.8.2 to downgrade?
*EDIT* ok, place in the MAIN directory. It's working and is unloading the .zip in bootloader
I need a new data sync cable, mine has started intermittently losing connection off and on...going to wait until I have a new one before I go any further.
Also, the latest version of ubuntu that Linux offers did not work. I found an earlier version(12.04) and the boot disk works so I am good to go on that
What is Hboot 0.8.2 ? Are you using Unknownforce's URT 3.1 Tool and following the "Downgrade/Unbrick" section?
This one:
http://forum.xda-developers.com/showthread.php?t=1563342
Yep, that is an outdated/earlier version. You need to use the Ultimate Recovery Tool from Unknownforce's thread as I linked earlier (URT v3.1) and use the LiveCd link.
see here
Sent from my "Up All Night Sleep All Day" Nexus 5!
THANKS
Well I just did a dry run with the Linux boot disk and terminal. Extracted downgrade.zip to HOME folder, ran the commands. I'm getting the correct code returns in the terminal. I got up to the:
Code:
Step 1... Plug in Device while holding down Volume Down key...
Waiting for device...
Just a matter of getting a new data sync cable now and I can do this...
Again thanks for your help, I'm pretty new to this process I've never altered a devices firmware manually before so it's an awesome experience as well..
Will report back in a couple days, hopefully with a newly rooted phone
--------
Also, do you have a direct link to the correct 1.13 RUU EXE to run after the downgrade?
otto325 said:
Also, do you have a direct link to the correct 1.13 RUU EXE to run after the downgrade?
Click to expand...
Click to collapse
Yep. Previously...
mpgrimm2 said:
....
Additional info you may need from my
[Guide]My Hboot 1.5x HTC Unlock/recovery/rom/kernel flashing notes 2-13-13
and
Post 11. My Gathered RUU .exe/.zip Links (& How to extract RUU zip yourself) <<<--- HERE
Click to expand...
Click to collapse
Sent from my "Up All Night Sleep All Day" Nexus 5!
HTC preloaded some image files for the "stickers" in the duo effects camera. They are preloaded to /data/preload so you can either flash the zip at the bottom of the second post or manually copy them over to that directory. They (HTC) haven't fully implemented this yet... so you probably won't even notice them missing. The also preload calc and flashlight app this way too.
NOTE- This will work for S-on users provided their current software level is at or below this version. S-off users can user this either way.
OPTION 1)
Rename download file to 0P3PIMG.zip. Make sure you use an SD card formatted to fat32!! (otherwise the phone might not see it) Place file on physical SD card (not internal phone memory)... i repeat physical SD card. Boot up phone to bootloader mode and the phone will auto-detect the file and prompt to install it. Follow any remaining prompts to allow the RUU to flash the software to your phone.
-or-
OPTION 2)
Download file into working fastboot directory. Boot phone to fastboot mode and connect to pc. Type in the following commands.
fastboot oem rebootRUU
fastboot flash zip RUU_T6_Sprint_WWE_1.16.651.4.zip
first time you run this it will be short... so run it a second time
fastboot flash zip RUU_T6_Sprint_WWE_1.16.651.4.zip
The command prompt output will show you details as it flashes each partition and will show you when it has completed. At this time the green bar on the phone will appear 99% of the way across the screen.. Completely normal!~ Issue the next command to kick it out of RUU mode or optionally flash the custom recovery TWRP if you intend to root/flash custom roms and THEN issue the below command to get out of RUU mode.
fastboot reboot
(note) if you just want to reboot back to bootloader you can issue the command fastboot reboot-bootloader This will allow you to boot directly to recovery and start flashing/rooting fun.
I don't own this model phone... so if someone would like to capture the output of the command prompt I would be happy to add it to the OP similar to how I have my VZW ruu threads.
Downloads Do NOT mirror these elsewhere.
RUU Download link
https://www.androidfilehost.com/?fid=23622183712460121
Data preload apps/stickers
https://www.androidfilehost.com/?fid=23622183712460132
RUU Mode TWRP 2.7.1 (must be s-off or unlocked)
https://www.androidfilehost.com/?fid=23622183712460136
Getting error, too many links
I followed the directions, but when I do I get an error: FAILED (status read failed (Too many links))
output:
sending 'zip' (1271836 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOrom parsing start ...
INFOrom parsing finish ...
INFOzip header checking...
INFOzip info parsing...
INFORead zipped android_info fail
FAILED (status read failed (Too many links))
martinoj2009 said:
I followed the directions, but when I do I get an error: FAILED (status read failed (Too many links))
output:
sending 'zip' (1271836 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOrom parsing start ...
INFOrom parsing finish ...
INFOzip header checking...
INFOzip info parsing...
INFORead zipped android_info fail
FAILED (status read failed (Too many links))
Click to expand...
Click to collapse
Did your md5 check out fine?
dottat said:
Did your md5 check out fine?
Click to expand...
Click to collapse
Yes
8f380af56b92ac2c4e3055b9a43b5871 ruu_t6_sprint_wwe_1.16.651.4.zip
martinoj2009 said:
Yes
8f380af56b92ac2c4e3055b9a43b5871 ruu_t6_sprint_wwe_1.16.651.4.zip
Click to expand...
Click to collapse
Do you have an sd card to try it via option 1?
dottat said:
Do you have an sd card to try it via option 1?
Click to expand...
Click to collapse
I'm sure I do, I'll let you know, and thanks for the prompt reply!
martinoj2009 said:
I'm sure I do, I'll let you know, and thanks for the prompt reply!
Click to expand...
Click to collapse
Not a problem. Also, under my android file host I have a mini sdk zip. You try using that on your pc too...it's a newer version of Fastboot/adb. All you have to do is unzip it and use it from wherever you unzip it to.
dottat said:
Not a problem. Also, under my android file host I have a mini sdk zip. You try using that on your pc too...it's a newer version of Fastboot/adb. All you have to do is unzip it and use it from wherever you unzip it to.
Click to expand...
Click to collapse
So I did this, no errors, but when I rebooted it went right into Cyanogenmod. Am I missing a step?
martinoj2009 said:
So I did this, no errors, but when I rebooted it went right into Cyanogenmod. Am I missing a step?
Click to expand...
Click to collapse
How long did it take to run the zip?
dottat said:
How long did it take to run the zip?
Click to expand...
Click to collapse
It takes a while ~5mins, it loads the file, then checks the signature, and then says ROM parsing start (for 5 seconds) and then tells me to press the power button to reboot.
martinoj2009 said:
It takes a while ~5mins, it loads the file, then checks the signature, and then says ROM parsing start (for 5 seconds) and then tells me to press the power button to reboot.
Click to expand...
Click to collapse
You have to do it twice if the first time is short. Sometimes it can only update certain files first.
You are s off right?
dottat said:
You have to do it twice if the first time is short. Sometimes it can only update certain files first.
You are s off right?
Click to expand...
Click to collapse
Lol, shhhh, forgot to S-Off
martinoj2009 said:
Lol, shhhh, forgot to S-Off
Click to expand...
Click to collapse
OK... so if you aren't S-off AND this firmware is older than what you have it will fail. Only S-off can downgrade. You guys don't have a newer RUU yet and there were two OTAs after this one. Definitely S-off that thing while you still can (assuming it's not too late).
@dottat
I have developer edition device and have ruu for it to stock jellyben
But I found that I can't flash the ruu to go back to jellyben from sense 6 firmware and the error was the same as mentioned above in other comments .. android info fail too many links
And after a lot of trials, I found that the rug is fine not damaged so I flashed the firmware if sense 5.5 and then tried the ruu again and it works perfect
So from my point , I think that older jb ruus can't be flashed if u have sense 6 firmware
So only I need tho flash firmware zip of sense 5.5 not the whole system the try the ruu again although both sense 6 and sense 5.5 have hboot 2.49 but I think that the one that came with sense 6 have some modifications
Also I tried to flash from sd card but no go so the only solution is flashing hboot of sense 5.5
Maybe it's the same with Sprint devices but I think that it will be the same
mido.fayad said:
@dottat
I have developer edition device and have ruu for it to stock jellyben
But I found that I can't flash the ruu to go back to jellyben from sense 6 firmware and the error was the same as mentioned above in other comments .. android info fail too many links
And after a lot of trials, I found that the rug is fine not damaged so I flashed the firmware if sense 5.5 and then tried the ruu again and it works perfect
So from my point , I think that older jb ruus can't be flashed if u have sense 6 firmware
So only I need tho flash firmware zip of sense 5.5 not the whole system the try the ruu again although both sense 6 and sense 5.5 have hboot 2.49 but I think that the one that came with sense 6 have some modifications
Also I tried to flash from sd card but no go so the only solution is flashing hboot of sense 5.5
Maybe it's the same with Sprint devices but I think that it will be the same
Click to expand...
Click to collapse
Either way....without being s off you can't downgrade firmware anyways. On my vzw rezound, m7, m8, and t6 I can simply flash ruus up or down all day long.
dottat said:
Either way....without being s off you can't downgrade firmware anyways. On my vzw rezound, m7, m8, and t6 I can simply flash ruus up or down all day long.
Click to expand...
Click to collapse
Yes I know that I should be s-off
And that's why I said I should downgrade first to sense 5.5 firmware then flash the ruu
And I won't be able to downgrade without s-off
So I was writing only about the error when I already have a-off because it took me 2 days till I found this fix after many trials
posted a current RUU for s-off users here...
http://forum.xda-developers.com/htc...rint-ruu-3-02-651-5-s-off-pre-rooted-t2865704
i have some troubles here
im in the HBOOT 2.49 i need to downgrade to the first HBOOT to install this RUU i need to know if make S-OFF with sunshine how to downgrade can any one. explain me how to do it ...dotatt dude u r awesome i always follow ur work and u r the best ...
please help me a little i have the knowledge to do it i just need a direction thx in advance
w1n73rf3ll said:
im in the HBOOT 2.49 i need to downgrade to the first HBOOT to install this RUU i need to know if make S-OFF with sunshine how to downgrade can any one. explain me how to do it ...dotatt dude u r awesome i always follow ur work and u r the best ...
please help me a little i have the knowledge to do it i just need a direction thx in advance
Click to expand...
Click to collapse
IF sunshine doesn't work on your current rom (have you tried running it yet).... you need to unlock your bootloader and flash a 100% stock older rom. Then use that to s-off. Then flash whatever rom you want and sim unlock.