Hey guys. I rooted my thunderbolt, and put the Liquid-ICS-v1.5-MR3-Mecha rom and the clockworkmod with touch recovery on it. All was great for the first day, second day while listening to music my music stopped and my phone could no longer see my 32gb sd card. I powered off, and reseated the sd card. Booted back up and i was able to listen to music again, for about 5 minutes, then same thing. I blew out the port with air duster and tried it again, it worked for a bit longer, but alas, it happened again. After the 4th try it could no longer read my sd card. I have an upgrade in march so i figured ill deal with it. About a week later my phone started rebooting alot. I never installed anything other than angry birds and Google play music so i could listen to my backed up music once my sd card stopped working. After about a day of rebooting randomly, it finally went into a bootloop, not getting passed the white screen. I could sometimes pull the battery and turn it back on and it would boot normally. After a while i wasn't even able to do that, so i booted into recovery, which also couldnt mount my sdcard, and wiped data, cache and dalvick. My phone booted up into liquid and I had to re set everything back up. After rebooting it, it went back to the bootloop problems. I then wiped everything again, this time wiping system as well. Nothing booted up after that past the white htc screen. I could still get into hboot and recovery though. hboot also couldnt load the sdcard when i put nothing but PG05img.zip for some reason. never found it, always came up with an error. But it would say it was trying to load pg05diag.zip instead. tried naming the zips as that too, but that didnt work either. Tried using adb to push a new rom but it would error out. Used fastboot to flash different recoveries hoping one would be able to read my sd card and i could flash a new rom. None worked, tried amon ra, twrp, and the non touch cwm. so I tried following a return to stock guide, using the tbolt.zip. that seemed promising, but I couldnt flash a new rom. My phone seemed unable to work with it. I managed to get rid of revolutionary, was still s-off, and still had amon ra. So i tried returning to stock using some .exe ruu's. but all get stuck at 56% updating the system. but I am now left with this screen:
MECHA XD SHIP S-ON
HBOOT-1.03.0000
MICROP-/
RADIO-1.49.00.0406w_1
eMMC-boot
Jan 22 2011.0.1: 10:43
RUU
I can also get the black htc screen with the 4 white triangles in the corners.
I have searched and searched and followed every guide I believed would fix it.
But at this point I believe it is bricked. Those 2 screens are all I can get to. Any help would be greatly appreciated
EDIT. I can re-lock and unlock via the HTC dev tool, but thats about it. I have used to the most up to date ruu I can find and even the oldest, when I run the ruu the wizard shows no previous version. They all get stuck at Updating system at 56%. The only way I can get to the ruu/hboot screen is to turn my phone on, plug it into the computer and then un plug it. I cant flash an zips, cant ADB, fastboot is very slim on what I can do. I have tried everything I can find. I will probably be using my insurance to get a new phone this weekend til I can upgrade, just wondering if There was any last ditch option I could try.
So you can no longer boot into recovery?
Sent from my ADR6400L using xda premium
Correct, those 2 screens are the only I can see, Hboot, which is really just the RUU screen i guess, and a black screen with htc in the center and a white triangle with exclamation points in the corners
I could do fastboot getvar all,
the only thing i can wipe is cache
Im not sure what all i can do with fastboot, but i tried flashing a new recovery and that failed, I can copy and paste the results of the recovery flash attempt once the phone charges a little.
heres the wipe results
C:\XXXXXXXXXXX\adt-bundle-win
k\platform-tools>fastboot erase userdata
erasing 'userdata'...
FAILED (remote: not allowed)
finished. total time: 0.019s
C:\XXXXXXXXXXX\adt-bundle-win
k\platform-tools>fastboot erase cache
erasing 'cache'...
OKAY [ 0.470s]
finished. total time: 0.473s
C:\XXXXXXXXXXX\adt-bundle-win
k\platform-tools>fastboot erase data
erasing 'data'...
FAILED (remote: not allowed)
finished. total time: 0.006s
C:\XXXXXXXXXXX\adt-bundle-win
k\platform-tools>fastboot erase system
erasing 'system'...
FAILED (remote: not allowed)
finished. total time: 0.006s
here is my results of getvar all
\\C:\XXXXXXXXXX\adt-bundle-windows-x86
k\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.03.0000
(bootloader) version-baseband: 1.49.00.0406w_1
(bootloader) version-cpld: None
(bootloader) version-microp: /
(bootloader) version-main:
(bootloader) serialno: XXXXXXXXXXXXXX
(bootloader) imei: 355195000000017
(bootloader) product: mecha
(bootloader) platform: HBOOT-7630
(bootloader) modelid: PG0510000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3669mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-1abb52a0
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
(bootloader) region-id: not support
all: Done!
finished. total time: 0.035s
The version main comes up blank.
this is my results when trying to flash a new recovery with fastboot
\platform-tools>fastboot flash recovery recovery-ra-mecha-3.06-gnm.img
sending 'recovery' <5776 KB>...
OKAY [ 0.959s ]
writing 'recovery' ...
<bootloader> signature checking...
FAILED <remote: 12 signature verify fail>
finished. total time: 1.959s
Your phone looks like it switched itself back to s on. I think your h boot may be corrupted.
Sent from my ADR6400L using Tapatalk 2
so are you confirming that is bricked?
I have a couple hboot PG05IMG.zip files you can flash. Hopefully this will restore your hboot to get your phone up and running again. Uploading it now... will post when they are finished.
If your phone is bricked, then trying this definitely won't hurt. Who knows... it may unbrick you.
Sent from my ADR6400L using xda premium
**Note: This will return your phone back to stock unrooted, but should hopefully get you running again**
I'm sure you know that these files must be renamed to PG05IMG.zip and be located on the root of your SD card in order to be flashed in hboot. Please check MD5 before flashing these files... it's VERY important.
FIRST FILE: http://db.tt/lBPkS4Jy
MD5: c64b4367086fff4f51ec3d5d766a0456
Rename this file to PG05IMG.zip and flash in hboot.
If your phone won't mount the SD card, pull it out of your phone and use your computers SD port or get a USB SD card reader (like $10 at Walmart) to put this file on the root of your SD card.
**You may have one update (update number 8?) that is bypassed, which is fine**
After this is finished, reboot and your phone SHOULD boot up looking fully stock with its dreadful bloat. Once it looks "good", get back to the root of your SD card and delete the file named PG05IMG.zip that you just used or rename it to anything except other than PG05IMG.zip
SECOND FILE: http://db.tt/Jy7jk9gZ
MD5: abda920f3e159fb05c00d8c54a5b8768
Put this next file on the root of the SD and rename it to PG05IMG.zip
Flash in hboot. Once finished, reboot your phone and you are done. Don't forget to take this PG05IMG.zip file off of your SD or rename it to something else.
Let me know if this worked for you.
Sent from my ADR6400L using xda premium
yeah its a no go. The only way I can turn my phone on is to plug it into either the computer or the wall, and when i do that it shows the black ruu error screen. (black with htc in middle and 4 white triangles in corners, then if i unplug my phone it will show the hboot screen, but all that shows is Ruu highlighted in orange, and the hboot version and stuff. buttons do nothing and it doesnt try to load anything from sdcard. I verified the sd card works on a different phone.
muddydog4 said:
yeah its a no go. The only way I can turn my phone on is to plug it into either the computer or the wall, and when i do that it shows the black ruu error screen. (black with htc in middle and 4 white triangles in corners, then if i unplug my phone it will show the hboot screen, but all that shows is Ruu highlighted in orange, and the hboot version and stuff. buttons do nothing and it doesnt try to load anything from sdcard. I verified the sd card works on a different phone.
Click to expand...
Click to collapse
Dang, yeah, I'm sure it's bricked then. I'm sorry man.
Sent from my ADR6400L using xda premium
RBarnett09 said:
Dang, yeah, I'm sure it's bricked then. I'm sorry man.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
Thanks for the suggestions though
Flash the RUU in my signature with the command
fastboot flash zip PG05IMG.zip
should fix you right up
trter10 said:
Flash the RUU in my signature with the command
fastboot flash zip PG05IMG.zip
should fix you right up
Click to expand...
Click to collapse
I don't think he is able to see his device in adb. That would be the best way if he could.
Sent from my ADR6400L using Tapatalk 2
Alright thanks, I download it and give it a try when i get home. I can do some fastboot commands btw. Definately not adb though. And ive been having trouble keeping my phone charged, it doent quite charge right now that it's in this state.
Alright thank you so much man. It worked! I'm back to stock and setting it up. Ill report any problems. I'll probably go back to custom roms eventually but give me a couple days to get bored of stock first.Thank you again.
Update. The entire left side of my screen (1/4 in) didnt respond to touches, made hitting "q" annoying in portait and space in landscape really annoying. It stopped working a few months ago when I was still on stock the first time. And it didnt work on Liquid. But now it works? Weird but you seemed to have solved every problem I had, even if that one was unintentional ;P
Update** It stopped working again as soon as I updated that it was working lol
Trter10 works miracles again! Its good to see you lurking still! We miss you over here in the TB forums.
Sent from my ADR6400L using xda premium
Update**
There are a lot bugs. Have to reboot a couple times to get service, and some times it does go into a boot loop. Still beats having a brick lying around though thats for sure. Sd card still doesnt work though which was kind of dissapointing but what evs. It says its got a unrecognizable file system but won't format it, and says it was removed. Plus the all in one tool doesnt see my phone either.
It's doing an awful lot of boot looping and random restarts, haven't had service in about an hour when it does get through though. But htc sync still cant see my phone along with any other program like revolutionary or your tool. I think im just going to avoid the head ache and just send it back. I used my phone while i was bored at work a lot and since it's just being frustrating it hardly seems worth the effort. Thanks though guys.
**You may have one update (update number 8?) that is bypassed, which is fine**
Along that idea. I'm stuck rolling back from ICS to 2.3.4 +/-. I've tried a couple MUUs they seem to be only different in the last couple decimal places.
But in both instances, they both "bypassed" 1. bootloader, as well as item 8. They unpack fine, they seem to install fine, I'm prompted to press the power key upon completion. I do so. The phone starts to reboot up for normal use, but it hangs at the first sceen, which is white with green letters in the middle htc and it just stays there. I'm trying your two files in this post to see if they will get me moving. What do you think about bypassing 1. bootloader?
Thanks
Mike
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.
Greetings!
I've inherited a EVO 3D that has issues. I'm new at this, but had 3 other old HTCs. I read a lot that i could for the last 12 hours in various forums and made a few mistakes/discoveries. I tried a few but i think i am stuck and i couldnt see anything else that can help so here i am. groveling for help. My first post too!
The 3D when turned on shows the HTC with white background splash screen for maybe 30-45 secs and blanks out. then reboots again ad nauseaum. In short, the phone cant boot to Android.
when plugged into the usb, seems to heat up under the camera area but not the battery, it actually drained the battery (or so i think ) because i was able to boot it before, and after i left it plugged in for an hour, it was hot and will not charge (red light blinks) i found out later voltage was below 3.0v used my old raphael to charge the batt (that works) so i can continue working on the 3D.
- i found the hboot power+vol down and was able to get into fastboot usb.
- was able to unlock using htc method
- tried loading cwm 4.0.1.4 - says success but wont enter recovery mode - just same splash screen
- tried loading cwm 5 (latest) says success but wont enter recovery mode - same as above
- found out about the RUU method. flashed back stock recovery and locked again and using the PC86IMG.zip method in hboot and a sd card. new 2.08.651.3 stock RUU was loaded successfully. but alas, still stuck in reboot/splash page.
edit: i noticed it "bypassed" one of the TP. not sure what that meant. when i was installing the stock RUU.
i dont know about the S-on or off, cant see it from hboot. can i?
i dont know if this has been rooted but the previous owner said no. it was still locked until i unlocked it.
so now, when i try recovery or factory reset, it immediately reboots and show splash screen only ad nauseaum. ( i waited as much as 5 reboots )
Help please? let me know if u have any questions.
Thank You!
CK
U should use the latest cwm not the touch one.an push it via fastboot read up on it on website below
www.rootofallevo.com
Sent from my PG86100 using XDA App
Go get flash image gui from the market. Put your recovery of choice on your SD card and flash it via flash image gui. Hboot 1.5 recovery partition is marked as "read only" hence the s-on, which can be seen in bootloader. The way around it is to fastboot into your device and flash zips that way or flash kernels and recoveries via flash image gui app.
Thanks Jwolf1,
I did try both CWM 4 and latest CWM 5 that is 3D specific. but it just reboots immediately and cycles over and over again and wont go into recovery. But! I may be missing a step or two. I havent found a post yet or a faq where there are more detailed steps to do this. maybe you can point me to one thats EVO 3D specific?
I tried the link but unfortunately, all it shows is the domain name is for sale.
CK
Thanks Jabawockee,
would i be able to use Flash image gui even if i cant get get the phone to boot aside from getting into hboot? if its possible, please let me know where i can find the instructions so i can read up.
CK
Oops that was on my part wrong link here's the right onewww.therootofallevo.com
Sent from my PG86100 using XDA App
Thanks jwolf1
I went to the site but i dont see anything that could help my case.
do you have other suggestions?
it seems that everyone expects recovery to fire up after a fastboot boot or a pc836img.zip boot from sdcard. i just cant seem to get to that page
I was observing that everytime i run a fastboot flash recovery something, i see it being loaded, but i dont see it being "written" (the progress bar on the right hand side is just a blip. no color) but when i try a recovery.img that is with the stock rom i have. i do see color in the progress bar when writing. not sure if that means anything.
I'm trying to find out if i can wipe cache and dalvik without going into recovery (since i cant boot the phone properly) but so far, all indications is ... no.
also, is there a way to peek inside the phone to see if the partitions are corrupted?
Thank You.
Ck
Is ur phone unlocked becuase if not this could be a problem if its locked
Sent from my PG86100 using XDA App
OP: You have my big thanks for trying to find an answer by yourself BEFORE you ask for it. A simple rule that n00bs are constantly failing to comprehend.
Odoslané z môjho HTC EVO 3D X515m cez Tapatalk
Hi Jwolf1,
yes, I unlocked my phone with the HTC method.
CK
Thanks Terepan,
still hoping to figure this out...
CK
new info...
I think i may have found the issue...
while trying over and over again, i notice i wasnt getting consistent responses to a certain command. in particular,
fastboot getvar all
on most cases, i get the following response on the cmd line
getvar:all FAILED (Status read failed (Too many links))
but once in a while i get
(bootloader) version : 0.5
(bootloader) version-bootloader: 1.50.0000
(bootloader) version-baseband: 0.97.10.0808
.
.
.
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
So i think the problem is, when i try writing to recovery, the message may say OKAY. but i am not sure that its being written in.
when i try a "fastboot erase recovery"
i always get "FAILED (Status read failed (Too many links)) "
another problem could be that the boot-mode is FASTBOOT
Is this the same as the one that we are suppose to turn off in the settings?
if yes, since i cant get in the phone settings. how do i turn it off?
if no, then it doesnt matter?
and is the security: on an issue? maybe why i cant erase recovery or load recovery ? i do noticed a difference in the screen on the phone when i load a "signed" recovery vs CWM and TWRP.
Anyone? help?
Thanks.
CK
Is it correct to.say you have a Sprint Cdma 651.3 hboot 1.50 based Evo3D?
When u enter hboot/bootloader you should see either "s-on" or "s-off" near the top and either "locked, unlocked, or relocked".
I had a problem with that Ruu.zip file Mr.Esp posted, maybe a bad download. Find another link (i did) or.run the 651.5 based Ruu for the updated radio (i did).
Note: you have to relock before running the Ruu.
See this:
http://forum.sdx-developers.com/index.php?topic=18852.0
SOLVED-Stock Hboot1.50 HTC Unlock/ RUU 651.3 flash problems (1-14-12)
I don't know if.it will help you or not but I had some issues getting certain recovery files loaded & booting to them afterwards to flash files from. I have the details & step by step scenarios of what I did that may help if you are overlooking a step. See the ROM/recovery issues thread in my signature.
Here (posts 1 & 10th ) :
http://forum.xda-developers.com/showthread.php?t=1450466
[Solved]Hboot 1.5 Rom/Recovery install issues (fastboot/FlashimageGui/RomMgr) 2-4-12
It sounds like the kernel/boot.img may not be correctly loaded after a ROM flash, but I'm not sure.
Sent from my "up all night, sleep all day" Evo3D!
mpgrimm2,
Thanks for the help! Thanks for inspiration!
i ended up inadvertantly fixing the damn thing. it was a hardware issue but i dont know which one.
I got fed up of 4-5 nights of not sleeping and got myself another "broken" evo 3d.
It had a broken digitizer so i was going to perform the swap. as i disassembled the first 3vo. i had the mainboard out and i figure, why not test it? hooked it up to the usb and hand held a batter and lo and behold i saw "normal" recognition pattern by the pc!
I slowly assembled it again, testing it at each and every connection to see if everything is still the same or maybe some other component may be causing the issue, and i finally have a whole 3vo working! booting! now i can even fastboot boot cwm ! damn! no more boot loops!
i am not sure if its was me pressing on the mainboard and maybe a chip got a connection back or maybe just one of the cable has a loose connection but now its fully functional again. (i'm thinking more of the former than the latter)
reason why is because of the heating issue it has. i wont be surprised if the issue comes back or if others has the same issues.
so for others with the same symptoms, try disassembling it and pressing down on the part where it heats up. one of those with the heat shields (using only finger and thumb!) good luck!
CK
My evo 3d is exactly the same problem. I have disassembled and reassembled it, also pressed down the part with heat shields, but no lucky to me:-(
xdapyro said:
I think i may have found the issue...
while trying over and over again, i notice i wasnt getting consistent responses to a certain command. in particular,
fastboot getvar all
on most cases, i get the following response on the cmd line
getvar:all FAILED (Status read failed (Too many links))
but once in a while i get
(bootloader) version : 0.5
(bootloader) version-bootloader: 1.50.0000
(bootloader) version-baseband: 0.97.10.0808
.
.
.
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
So i think the problem is, when i try writing to recovery, the message may say OKAY. but i am not sure that its being written in.
when i try a "fastboot erase recovery"
i always get "FAILED (Status read failed (Too many links)) "
another problem could be that the boot-mode is FASTBOOT
Is this the same as the one that we are suppose to turn off in the settings?
if yes, since i cant get in the phone settings. how do i turn it off?
if no, then it doesnt matter?
and is the security: on an issue? maybe why i cant erase recovery or load recovery ? i do noticed a difference in the screen on the phone when i load a "signed" recovery vs CWM and TWRP.
Anyone? help?
Thanks.
CK
Click to expand...
Click to collapse
I never have erased a recovery I have flashed over the old one... Seems to overwrite that part the recovery is stored...
Haven't had any issues doing it this way...
Subaochen,
Try plugging the mainboard while disassembled, just mainboard and battery. thats how i found out mine works. then you can slowly reassemble step by step. if yours doesnt connect normally during that time, check the board over. if you can identify which part overheats then you know where to press...
Good Luck!
CK
reaper24,
I have tried "fastboot flash recovery any.img" multiple times without success, until i disassembled it and then, everything was just normal. could also be a dirty connection for me. altho when i run the RUU, it "seems" to work properly since i was able to upgrade to latest stock ROM.
I do have S-ON so i guess i would never be able to erase recovery nor boot.
hopefully everyone have the patience to troubleshoot their unit. i had to learn patience with mine.
boot loops are really the discouraging to say to least.
Sincerely,
CK
xdapyro said:
Subaochen,
Try plugging the mainboard while disassembled, just mainboard and battery. thats how i found out mine works. then you can slowly reassemble step by step. if yours doesnt connect normally during that time, check the board over. if you can identify which part overheats then you know where to press...
Good Luck!
CK
Click to expand...
Click to collapse
Thanks xdapro first!
I have tried again but not lucky:-(
Maybe my situation is not the hardware failure, just the wrong kernel or boot? When I accepted the OTA while the phone was rooted and after have a full reboot, the phone just stuck at the htc splash screen and boot loop.
I guest that, when I accepted OTA, the bootloader was updated to Hboot 1.5. But because the phone is rooted, kernel or boot partition is not updated by OTA, so the security signature is not the same between the new bootloader and the old kernel, so the boot loop.
I have tried RUU and all custom recoveries I can find, all failed, the recovery seemed installed ok, but can not boot into recovery. Also, I have tried fastboot boot recovery.img, just directly boot into the HTC splash screen and boot loop.
Anyone can give any hints? thanks a lot in advance!
Just a heads up, you have to "relock" the phone before flashing the Stock RUU's.
From "fastboot USB" Type: fastboot oem lock
It will erase the recovery in the process. I have had bad ruu downloads before. If the exe doesn't work, get the zip version.
The basic problem I have is that the software won't apply to my phone correctly.
Software number: 1.02.605.6. Should show 2.01.605.11
Any help would be awesome.
Here is more information that I think could be useful. Please request any additional information or clarification.
I delocked, then I ran the new RUU, then unlocked it back up. I got to the point of basically having everything stock, and it showed the new 2.01.605.11 software number, but obviously I wanted everything back, so I flashed my nand backup using amon ra. I must have missed something because I'm basically back to the same spot I used to be which was that the update would randomly shut my phone down and end on this error "E:Error in /cache/fumo/OTAPkg.zip" in the recovery screen and i'd have to battery pull to make things restart..
I'm not sure if it's different now, but my baseband version shows:
0.95.00.1118r, 0.95.00.1223r
i know the first one is the new baseband. I do not have the 5 signal bars though, although I did when everything was stock for a minute before i started messing with things again.
ON the bootloader screen it shows hboot v2.11
So I think i'm really close just missing something. Is it not cool to just flash my old recovery file that i made before starting this stuff? Did I include too much information when I created it(check too many boxes).. I'm not even sure how to ask this question to be honest.
When I try to do the update itself at this point, it will download and start to apply, and then give me the same error like this one.
'E:Error in /cache/fumo/OTAPkg.zip'
Since doing everything I currently cannot use wifi, it shows "error" in the settings menu which I know is similiar to other errors people have gotten.
I would greatly appreciate any help and explanation!
Have you tried relocking your phone and doing a factory reset via the bootloader? The OTA will pop up once factory reset. This is how to applied the OTA with ease, hope this helps!
I actually did a factory reset before any of this. I should have included that in the OP. Honestly I think it was still locked when I factory reset, but I know it worked in some form because I no longer had amon-ra recovery. I'm like right on the verge of understanding all this kernal stuff on another level but obviously not there yet since I can't figure this OTA out.
So you were rooted debloated but otherwise stock, and you just relocked *which means its still rooted right?* and then factory reset, then the update will apply.. then you unlock it again.. and then you can flash back to your debloated nand backup?
Maybe i'm not understanding flash and recover.. can i not use those interchangeably?
Could my problem be that I did the factory reset before locking it back up? I thought with some methods factory reset wasn't necessary (RUU resets things regardless)..
I believe I relocked, did a factory reset, then once stock rom loaded up I downloaded and installed update. After installing the OTA was when I unlocked again, thats odd I believe once re-locked you lose root access and doing a factory reset will grant you stock unrooted rom. Try deleting the OTA zip from the sd card and redownload. The wifi not working means you had a kernel installed, reinstall stock kernel from NilsP thread and make sure to use Scott's flash tool to flash the boot.img from the kernel. You can get the boot.img from kernel in the PH98IMG.zip which resides in the kernel folder.
You might as well run the RUU for 2.01.605.11. It is the update and will probably fix everything for you. It will get you back to stock, you will just have to unlock the phone after you run the RUU and then reinstall Amon Ra to get root back.
thurst0n said:
I delocked, then I ran the new RUU
Click to expand...
Click to collapse
I've already run the new RUU.
And then you did a restore of a nandroid. Your mainver is now updated and your are trying to run an older mainver, probably why you are having so many issues. Rerun the RUU and act like it is a brand new phone that you just picked up. if you want to run a rom, install from scratch.
richii0207 said:
I believe I relocked, did a factory reset, then once stock rom loaded up I downloaded and installed update. After installing the OTA was when I unlocked again, thats odd I believe once re-locked you lose root access and doing a factory reset will grant you stock unrooted rom. Try deleting the OTA zip from the sd card and redownload. The wifi not working means you had a kernel installed, reinstall stock kernel from NilsP thread and make sure to use Scott's flash tool to flash the boot.img from the kernel. You can get the boot.img from kernel in the PH98IMG.zip which resides in the kernel folder.
Click to expand...
Click to collapse
Ok Im going to sort of "Start over soon" if I can't finnegal a way here shortly.
But I swear it showed 'relocked' in bootloader, and i was still rooted. Relocking it forces everything back to stock, but it sitll shows the updated radio, and hboot2.11
I really don't think I ever flashed a kernal unless you count amon-ra as being a kernal. Again i'm new to this and some of the terminology confuses, me so explanation to the steps helps too.
EmerikL said:
And then you did a restore of a nandroid. Your mainver is now updated and your are trying to run an older mainver, probably why you are having so many issues. Rerun the RUU and act like it is a brand new phone that you just picked up. if you want to run a rom, install from scratch.
Click to expand...
Click to collapse
Ok so basically you're saying I can't have my cake and eat it too? I will have to reset my phone up with apps and settings etc.. I don't use a ROM, I just froze and uninstalled many many things, and installed other things etc..
Is the 'E:Error in /cache/fumo/OTAPkg.zip' caused by the mainver discrepency?
I was trying to prevent starting from scratch, but I suppose backing up from my nandroid is essentially flashing a rom.. right?
Would it possible to achieve my old setup using TI as opposed to amon-ra recovery?
thurst0n said:
Ok so basically you're saying I can't have my cake and eat it too? I will have to reset my phone up with apps and settings etc.. I don't use a ROM, I just froze and uninstalled many many things, and installed other things etc..
Is the 'E:Error in /cache/fumo/OTAPkg.zip' caused by the mainver discrepency?
I was trying to prevent starting from scratch, but I suppose backing up from my nandroid is essentially flashing a rom.. right?
Would it possible to achieve my old setup using TI as opposed to amon-ra recovery?
Click to expand...
Click to collapse
I restored a nand I made before the OTA after I accepted the OTA so it can be done. I wasn't having any issues, certainly not the one you are having. My software says 1.02.605.6 since flashing the older ROM but I still show the new radios listed in baseband, and I'm not getting that error. My mainver is at 2.x. You can check what mainver your phone is on in fastboot using the following command:
fastboot getvar all
But that error is not really a mainver error, at least not like the ones that have been happening. That file you mentioned the error about is the OTA update and your phone seems to be trying to run it or something. I think what is happening is that you are restoring your nand cache and there's a trace of the OTA in there so your phone wants to run the OTA. I would bet that if you delete the OTAPkg.zip file you'll be fine. Either it's there and your phone is trying to run it or your phone thinks it's there and it's not. You might want to look in settings and see what it says about having an update.
Also, wipe your cache and dalvik cache in recovery and see if that fixes it. Especially if that OTA file isn't there, then it must be something else in your cache that wants to run the update.
If that doesn't work, then RUU again and then try restoring your nand without the cache checked. Or if you made a nand right after the RUU restore that. If you didn't, make one after you get RUU and rooted in case you need to revert back. I'm kicking myself cuz I was so excited to get my phone back how I wanted it I forgot to make one myself after I RUU'd today and of course I didn't realize it until right after I confirmed I wanted to flash the custom ROM.
feralicious said:
I restored a nand I made before the OTA after I accepted the OTA so it can be done. I wasn't having any issues, certainly not the one you are having. My software says 1.02.605.6 since flashing the older ROM but I still show the new radios listed in baseband, and I'm not getting that error. My mainver is at 2.x. You can check what mainver your phone is on in fastboot using the following command:
fastboot getvar all
But that error is not really a mainver error, at least not like the ones that have been happening. That file you mentioned the error about is the OTA update and your phone seems to be trying to run it or something. I think what is happening is that you are restoring your nand cache and there's a trace of the OTA in there so your phone wants to run the OTA. I would bet that if you delete the OTAPkg.zip file you'll be fine. Either it's there and your phone is trying to run it or your phone thinks it's there and it's not. You might want to look in settings and see what it says about having an update.
Also, wipe your cache and dalvik cache in recovery and see if that fixes it. Especially if that OTA file isn't there, then it must be something else in your cache that wants to run the update.
If that doesn't work, then RUU again and then try restoring your nand without the cache checked. Or if you made a nand right after the RUU restore that. If you didn't, make one after you get RUU and rooted in case you need to revert back. I'm kicking myself cuz I was so excited to get my phone back how I wanted it I forgot to make one myself after I RUU'd today and of course I didn't realize it until right after I confirmed I wanted to flash the custom ROM.
Click to expand...
Click to collapse
Getvar All shows this
Code:
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.11.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.01.605.11
(bootloader) serialno: 000000
(bootloader) imei: 000000000
(bootloader) product: vigor
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PH9810000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4184mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bc948b45
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
I need to go to work now, but I appreciate everyones help in this! I must be looking in the wrong spot or it's not there, cuse the OTApkg.zip i cannot find at the moment, i swear i've downloaded it like 20 times over the past 2 weeks haha
feralicious said:
I restored a nand I made before the OTA after I accepted the OTA so it can be done.
Click to expand...
Click to collapse
Same here.
thurst0n said:
Getvar All shows this
Code:
< waiting for device >
(bootloader) version-bootloader: 2.11.0000
(bootloader) version-main: 2.01.605.11
I need to go to work now, but I appreciate everyones help in this! I must be looking in the wrong spot or it's not there, cuse the OTApkg.zip i cannot find at the moment, i swear i've downloaded it like 20 times over the past 2 weeks haha
Click to expand...
Click to collapse
First of all, I would edit your post and delete your serial number and imei as I believe that is sensitive info.
So you are updated based on what you posted, did you check your baseband in settings? That will confirm your radio update. I would try wiping your cache and dalvik cache in recovery. I do think there's some trace of that update and your phone is trying to update but that file isn't there so it errors out.
After you wipe power down, pull battery and then reboot. Hopefully that fixes it.
Then go into settings and see if it shows any updates available for you.
Sent from my ADR6425LVW using Tapatalk
So, i tried to do the WireTrick and it f-ed up my phone. i lost recovery + rom and can't flash anything cuz i'm on HBOOT 1.58 S-ON. (UNLOCK HTCdev).
I wanna relock it and run the Sprint RUU.exe but i'm getting the follow error;
_____________________________________________________
C:\rootevo3dnew>fastboot oem lock
...
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [PG_ERROR] htc_pg_hdr_get(114):
(bootloader) sd_read_sector error
(bootloader) [PG_ERROR] htc_pg_part_hdr_get(166):
(bootloader) htc_pg_hdr_get failed
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 134086008 (0x7FDFD78)
FAILED (status read failed (Too many links))
finished. total time: 1.014s
________________________________________________________
Is there any other way to get Lock/Relock?
MANY THX
Sorry I may be wrong and hopefully someone will correct me if I am because I cant remember for sure but since your unlocked, you could install recovery thru bootloader with PG86100.zip. Once you get recovery then you could at least get your phone will working again...
Sent from my Rooted S-OFF EVO 3D
Hit that thanks button if I helped.
scottypeterson said:
Sorry I may be wrong and hopefully someone will correct me if I am because I cant remember for sure but since your unlocked, you could install recovery thru bootloader with PG86100.zip. Once you get recovery then you could at least get your phone will working again...
Sent from my Rooted S-OFF EVO 3D
Hit that thanks button if I helped.
Click to expand...
Click to collapse
No, I can't cuz I still s-on...
Axhole said:
So, i tried to do the WireTrick and it f-ed up my phone. i lost recovery + rom and can't flash anything cuz i'm on HBOOT 1.58 S-ON. (UNLOCK HTCdev).
I wanna relock it and run the Sprint RUU.exe but i'm getting the follow error;
_____________________________________________________
C:\rootevo3dnew>fastboot oem lock
...
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [PG_ERROR] htc_pg_hdr_get(114):
(bootloader) sd_read_sector error
(bootloader) [PG_ERROR] htc_pg_part_hdr_get(166):
(bootloader) htc_pg_hdr_get failed
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 134086008 (0x7FDFD78)
FAILED (status read failed (Too many links))
finished. total time: 1.014s
________________________________________________________
Is there any other way to get Lock/Relock?
MANY THX
Click to expand...
Click to collapse
Is there some reason you can't reinstall a recovery using adb? If you boot to bootloader, I would think you could flash your recovery image using adb commands. Then you should be able to reinstall your rom. I installed my recovery with s-on this way with no issues.
Barring that, I am not sure if the wire trick works on 1.58, I did it before I allowed my hboot to upgrade, but what happens if you try it again? Do you have anything to lose?
Just boot into bootloader, enter fastboot then in fastboot connect usb cable.
In PC you can flash downloaded recovery using "fastboot flash recovery recovery_name.img" command, just make sure that recovery image is in the same dir as fastboot.exe.
Guys, come on. I can't flash/boot recovery. that's the why i wanna relock it. when i try to boot an img, i get the msg "FAILED (remote: reproduce boot image with on-flash ramdisk error)", as far as i know it's cuz the ramdisk is empty. HELP PLEASE. lol.
Helppp!!!
Damn it! Nobody? Any one? I'm phoneless...
http://forum.xda-developers.com/showthread.php?t=1677053
read this thread. there is a command that will restore the backups in the folder with the exe file.
"(bootloader) Lock successfully..."
That line is there, more likely than not you're locked successfully. Run the RUU and see what happens
Axhole said:
Damn it! Nobody? Any one? I'm phoneless...
Click to expand...
Click to collapse
U can flash a zip ruu u just need to dl a signed ruu that u were currently on and run it then extract the zip from the .exe if ur on Windows search in the start menu %temp% delete everything and if it leaves some files that's fine then run the ruu .exe then look in the newest of the 2 folders it creates then find a file in the folder with another folder in it open that folder and find rom.zip move it to desktop and rename PG86IMG.zip place on sd and boot in bootloader and press vol + and u can try the wire trick again if u want
Sent from my PG86100 using xda premium
rockerdudelive said:
http://forum.xda-developers.com/showthread.php?t=1677053
read this thread. there is a command that will restore the backups in the folder with the exe file.
Click to expand...
Click to collapse
i tried that... no good ;-/
beneath-a-burning-turtle said:
"(bootloader) Lock successfully..."
That line is there, more likely than not you're locked successfully. Run the RUU and see what happens
Click to expand...
Click to collapse
NO my friend... it's like, "ok, you got it", then next line you have "NO WAIT, you can't get it" lol. STILL a big "UNLuCKy" ;0)
kickyoace said:
U can flash a zip ruu u just need to dl a signed ruu that u were currently on and run it then extract the zip from the .exe if ur on Windows search in the start menu %temp% delete everything and if it leaves some files that's fine then run the ruu .exe then look in the newest of the 2 folders it creates then find a file in the folder with another folder in it open that folder and find rom.zip move it to desktop and rename PG86IMG.zip place on sd and boot in bootloader and press vol + and u can try the wire trick again if u want
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
i did that and it just reboot with no changes... no errors. darn it!
Axhole said:
NO my friend... it's like, "ok, you got it", then next line you have "NO WAIT, you can't get it" lol. STILL a big "UNLuCKy" ;0)
Click to expand...
Click to collapse
Trust me, I think you got it. When I had a stroke of stupidity and relocked to take ota (which you should NEVER do), it gave me that EXACT line after it said locked successfully and I was locked just fine. Ran the ruu and was back to stock
Sent from my PG86100 using xda app-developers app
I went through similar issues but never got full update to New hboot I had to reunlock my phone flash stock rooted Rom then do wire trick but as previously stated I was still on 1.5 hboot and not sure if wire trick works on 1.58
Sent from my PG86100 using xda app-developers app
I just wanna said to y'all that I really appreciate all the help. I went to a sprint store and the technician told me that my cellphone has a "hardware failure". New cellphone, end of story. Thanks y'all.
I purchased a EVO 4G LTE for my sister a little while back and recently she had her boyfriend attempt to root it for her, and since I'm here it obviously didn't go over all too well. All he said he did was follow a video (which he gave me) on how to root for the newer software version. "Something happened and it didn't work so I watched another video and tried that" The phone is currently unlocked with S-ON and he flashed a working version of TWRP and cm10 couldn't figure it out and here we are. help please. Rooted using Linux. i did some reading and found out i had to flash the boot.img through fastboot. it just hangs at <waiting for device> in the terminal. Apologies if this has been answered, if so please point me in the right direction.
http://forum.xda-developers.com/showthread.php?t=1917106
Scroll down to see how to replace the files with the files from the cm10 rom that he flashed to the phone.
I forgot to mention I too am running linux, i tried to open this in wine and it wont save the files to my system. i will try this at a friends house asap and report back, thanks
BusstopBill44 said:
I forgot to mention I too am running linux, i tried to open this in wine and it wont save the files to my system. i will try this at a friends house asap and report back, thanks
Click to expand...
Click to collapse
Is adb configured right?
I use Linux and when I was son I was able to flash boot.img without problems
Sent from my EVO using xda app-developers app
jesuscash said:
Is adb configured right?
I use Linux and when I was son I was able to flash boot.img without problems
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
I'm not really sure what he did or why he even tried. How can I check adb to see if that was done correctly?
tilltheend714 said:
http://forum.xda-developers.com/showthread.php?t=1917106
Scroll down to see how to replace the files with the files from the cm10 rom that he flashed to the phone.
Click to expand...
Click to collapse
Alright, we have made some progress, I went to a buddys house and flashed the boot.img using said method flashed gapps as well.Now, i have no touch function but it does boot to the homescreen, any advice?
BusstopBill44 said:
Alright, we have made some progress, I went to a buddys house and flashed the boot.img using said method flashed gapps as well.Now, i have no touch function but it does boot to the homescreen, any advice?
Click to expand...
Click to collapse
I'm guessing it's on the latest firmware (3.16)? That update breaks the touch panel on all non-3.16 roms (which would include cm)...the only way to downgrade is to flash the tp.img from the previous firmware (3.15), which requires s-off. I would recommend going that route as it makes things a lot easier. For example, once you're s-off you won't have to fastboot flash kernels anymore. Check out the dirty racun thread in Original Development for more info. If you decide to s-off, you can flash the old tp.img zip from the 3.15 firmware to get the touch panel working for cm:
http://themikmik.com/showthread.php...dio-Collection&p=220556&viewfull=1#post220556
Otherwise, if you don't want to go s-off then you'll need to flash a sense Rom that's using the 3.16 base (which I think most if not all are now). I recommend Viper4g, runs great and has tons of tweaks like cm.
Sent from my EVO LTE
BusstopBill44 said:
Alright, we have made some progress, I went to a buddys house and flashed the boot.img using said method flashed gapps as well.Now, i have no touch function but it does boot to the homescreen, any advice?
Click to expand...
Click to collapse
Boot into bootloader and check the radio. If its 1.12.11.1210 then he took the 3.16 OTA and your only choices are what premo15 said.
premo15 said:
I'm guessing it's on the latest firmware (3.16)? That update breaks the touch panel on all non-3.16 roms (which would include cm)...the only way to downgrade is to flash the tp.img from the previous firmware (3.15), which requires s-off. I would recommend going that route as it makes things a lot easier. For example, once you're s-off you won't have to fastboot flash kernels anymore. Check out the dirty racun thread in Original Development for more info. If you decide to s-off, you can flash the old tp.img zip from the 3.15 firmware to get the touch panel working for cm: (Had to remove link)
Otherwise, if you don't want to go s-off then you'll need to flash a sense Rom that's using the 3.16 base (which I think most if not all are now). I recommend Viper4g, runs great and has tons of tweaks like cm.
Sent from my EVO LTE
Click to expand...
Click to collapse
Thanks, i decided to try and go S-OFF. I flashed the correct RUU for 3.16 and I get an error message after I flash the RUU,zip
/RabiesShot_LINUX$ sudo ./fastboot flash zip RUU.zip
< waiting for device >
sending 'zip' (659905 KB)...
OKAY [ 45.943s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 122.961s
BusstopBill44 said:
Thanks, i decided to try and go S-OFF. I flashed the correct RUU for 3.16 and I get an error message after I flash the RUU,zip
/RabiesShot_LINUX$ sudo ./fastboot flash zip RUU.zip
< waiting for device >
sending 'zip' (659905 KB)...
OKAY [ 45.943s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 122.961s
Click to expand...
Click to collapse
Did you run babyracun before relocking and running the ruu?
tilltheend714 said:
Did you run babyracun before relocking and running the ruu?
Click to expand...
Click to collapse
Wow, I completely looked past that, thought I read that whole page thoroughly. It looks like after I failed at that RUU it no longer has TWRP installed, I really hate asking but what can I possibly do now?
BusstopBill44 said:
Wow, I completely looked past that, thought I read that whole page thoroughly. It looks like after I failed at that RUU it no longer has TWRP installed, I really hate asking but what can I possibly do now?
Click to expand...
Click to collapse
re-flash twrp
bigdaddy619 said:
re-flash twrp
Click to expand...
Click to collapse
another error, $ sudo ./fastboot flash recovery openrecovery-twrp-2.4.2.0-jewel.img
sending 'recovery' (8032 KB)...
OKAY [ 1.277s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.107s
and tried it with 2.4.1.0, which i had before, as well.
BusstopBill44 said:
Wow, I completely looked past that, thought I read that whole page thoroughly. It looks like after I failed at that RUU it no longer has TWRP installed, I really hate asking but what can I possibly do now?
Click to expand...
Click to collapse
I don't know if you can just install TWRP again or if you'll have to go through the HTCdev unlock again. You'll need the Unlock_code.bin for the Dirtyracun process anyway so you might as well get it again.
tilltheend714 said:
I don't know if you can just install TWRP again or if you'll have to go through the HTCdev unlock again.
Click to expand...
Click to collapse
^^^^ true
I don't know if this will work since you've already tried dirtyracun; but I just used this method to achieve s off. It's ridiculously easy, and took me 5 minutes..
http://forum.xda-developers.com/showthread.php?t=2163013
tilltheend714 said:
I don't know if you can just install TWRP again or if you'll have to go through the HTCdev unlock again. You'll need the Unlock_code.bin for the Dirtyracun process anyway so you might as well get it again.
Click to expand...
Click to collapse
alright, some progress, got my unlock from HTCDEV got the unlock token, restarted the whole S-OFF process over,got through the ruu.zip. it installed, It rebooted itself instead of allowing me to "sudo ./fastboot reboot bootloader." It booted to a stock rom (which is now 3.15), I was in shock that I had her phone working again. restarted to bootloader, noticed it was locked and s-on went back to the directions and had me unlock through the unlock_token and finall had me run "sudo ./RabiesShot...which is giving me errors.
Starting up...
Testing connection...
Test 1: Rebooting into bootloader
Waiting fastboot (18/60)
Waiting...
Test 2: Booting device...
Waiting ADB... (60/60)
Test 2: Booting FAILED
Reboot device manually
Connection test failed!
After this error I rebooted into bootloader and im S-ON with unlocked. can i jump right into s-off'ing it
BusstopBill44 said:
alright, some progress, got my unlock from HTCDEV got the unlock token, restarted the whole S-OFF process over,got through the ruu.zip. it installed, It rebooted itself instead of allowing me to "sudo ./fastboot reboot bootloader." It booted to a stock rom (which is now 3.15), I was in shock that I had her phone working again. restarted to bootloader, noticed it was locked and s-on went back to the directions and had me unlock through the unlock_token and finall had me run "sudo ./RabiesShot...which is giving me errors.
Starting up...
Testing connection...
Test 1: Rebooting into bootloader
Waiting fastboot (18/60)
Waiting...
Test 2: Booting device...
Waiting ADB... (60/60)
Test 2: Booting FAILED
Reboot device manually
Connection test failed!
After this error I rebooted into bootloader and im S-ON with unlocked. can i jump right into s-off'ing it
Click to expand...
Click to collapse
Yeah, you should be able to run rabies shot again. Did you enable USB Debugging befor trying to run rabies shot? And are you running linux 32-bit?
tilltheend714 said:
Yeah, you should be able to run rabies shot again. Did you enable USB Debugging befor trying to run rabies shot? And are you running linux 32-bit?
Click to expand...
Click to collapse
thanks, and after all that s-off/on nonsense I cant s-off with a 32 gb microsd....grrrr
BusstopBill44 said:
thanks, and after all that s-off/on nonsense I cant s-off with a 32 gb microsd....grrrr
Click to expand...
Click to collapse
You can try this
http://forum.xda-developers.com/showthread.php?t=2163013
But that requires root. You don't have a 2gb card laying around anywhere?