Related
for some reason today i started getting random reboots here and there. when i got home i decided to wipe my phone and do a clean install. everything went well, successful wipe and complete flash of the rom, but when it restarted after the flash it was still the same as before. nothing changed, all my apps, wallpaper, settings everything had been untouched. i even did fastboot wipe userdata. it was like i didnt do anything at all. then i tried wiping my internal sd card, same thing successful wipe, but it all comes back again. i did it a couple of times from the phone settings and also from my computer. then i flashed the ruu from the bootloader, everthing flash normal but when it restarted nothing changed. also tried changing my recovery to cwm but that didnt work either. tried flashing the eng bootloader and it said fail-pu.
right now im running energy rom june 19th, 4 ext recovery, joupunutbear 1.93.2222
any help or advise would be great.
msndroid said:
for some reason today i started getting random reboots here and there. when i got home i decided to wipe my phone and do a clean install. everything went well, successful wipe and complete flash of the rom, but when it restarted after the flash it was still the same as before. nothing changed, all my apps, wallpaper, settings everything had been untouched. i even did fastboot wipe userdata. it was like i didnt do anything at all. then i tried wiping my internal sd card, same thing successful wipe, but it all comes back again. i did it a couple of times from the phone settings and also from my computer. then i flashed the ruu from the bootloader, everthing flash normal but when it restarted nothing changed. also tried changing my recovery to cwm but that didnt work either. tried flashing the eng bootloader and it said fail-pu.
right now im running energy rom june 19th, 4 ext recovery, joupunutbear 1.93.2222
any help or advise would be great.
Click to expand...
Click to collapse
The outlook isn't good, sorry to say that. Most likely, the internal memory chips have failed. Basically, it won't write anymore on it, meaning what you have on it right now may be stuck, permanently. This is because of the "Fail-PU" error. Before doing anything like the wire trick below, try to ensure that the RUU you're trying to flash is a correct one. It would be great if you could get a picture (or describe) what it says when the ruu flash is done. But since you have problems wiping, this may not be the issue. Try the wire trick, as described below with caution.
Unfortunately, there isn't much you can do. I've heard that sometimes if you do the wire trick, it can temporarily fix the error. Heed this. Do the wire trick on its own, meaning do not connect the phone to a computer, or run the Juopunutbear's S-OFF program, or anything of that nature. Just do the exact same wire trick (same timing too) you did to obtain s-off, but without using the s-off program, or plugging it in the computer.
Keep us updated if that trick works for you.
It would also be a good idea to flash a RUU after doing the wire trick (again, without the s-off program, or plugging it in the computer!!!)
Again, best of luck!
this is what came up.
i used this ruu
http://d-h.st/z70
msndroid said:
this is what came up.
i used this ruu
http://d-h.st/z70
Click to expand...
Click to collapse
Have you tried the trick i mentioned earlier and then flashing the RUU?
yes, i've tried it a couple of times. ill try again in the morning but i think its a lost cause though. thanks for your help.
msndroid said:
yes, i've tried it a couple of times. ill try again in the morning but i think its a lost cause though. thanks for your help.
Click to expand...
Click to collapse
theres another thing you could try too.
Boot into fastboot and then type in this command:
fastboot oem boot
Pull out your battery
Put back in.
Flash the RUU
Keylogger_0 said:
theres another thing you could try too.
Boot into fastboot and then type in this command:
fastboot oem boot
Pull out your battery
Put back in.
Flash the RUU
Click to expand...
Click to collapse
no good. i pulled the battery as soon as the htc screen came on and also when the boot animation started. still getting the same results with the ruu.
i noticed this though. isnt it supposed to be bootloader instead of misc?
INFOaARM_Partion[0].name=misc
I'm assuming you know how to use fastboot, flash your stock SHP or ENG hboot via fastboot via:
fastboot erase cache
fastboot rebootRUU
fastboot flash zip en_hboot.zip
Place the attached zip of choice be it sh or en in your adb folder and try those commands, let me know your results.
If he flashes eng hboot, redownloads ruu to ensure good download, and try flashing ruu in bootloader again... I bet it would work
Sent from my HTC VLE_U using Tapatalk 2
msndroid said:
no good. i pulled the battery as soon as the htc screen came on and also when the boot animation started. still getting the same results with the ruu.
i noticed this though. isnt it supposed to be bootloader instead of misc?
INFOaARM_Partion[0].name=misc
Click to expand...
Click to collapse
Actually, I checked it out for my phone with fastboot oem boot too. It lists the partition 0 being the misc partition too. So I think that's fine. My device is fully functional (wipe/flash capabilities included) *knocks on wood* so I think that partition is normal.
Dark Nightmare said:
I'm assuming you know how to use fastboot, flash your stock SHP or ENG hboot via fastboot via:
fastboot erase cache
fastboot rebootRUU
fastboot flash zip en_hboot.zip
Place the attached zip of choice be it sh or en in your adb folder and try those commands, let me know your results.
Click to expand...
Click to collapse
tried both and it gave me this....
C:\adb>fastboot flash zip sh_hboot.zip
sending 'zip' (396 KB)... OKAY [ 0.246s]
writing 'zip'... FAILED (remote: not allowed)
finished. total time: 0.563s
To be honest I think the emmc chip although it's s-off it thinks its still s-on, my best guess would be to try s-off again, see what happens.
Sent from my SGH-T679 using xda app-developers app
msndroid said:
tried both and it gave me this....
C:\adb>fastboot flash zip sh_hboot.zip
sending 'zip' (396 KB)... OKAY [ 0.246s]
writing 'zip'... FAILED (remote: not allowed)
finished. total time: 0.563s
Click to expand...
Click to collapse
Boot into fastboot, and then type in this command
fastboot oem readsecureflag
This command should return with a value of 0
If not, let us know.
Keylogger_0 said:
Boot into fastboot, and then type in this command
fastboot oem readsecureflag
This command should return with a value of 0
If not, let us know.
Click to expand...
Click to collapse
yup thats what i got.
C:\adb>fastboot oem readsecureflag
... INFOsecure_flag: 0
OKAY [ 0.007s]
finished. total time: 0.007s
I kinda gave up on the phone. Ill just buy a galaxy nexus by the end of the month. But if there's still any suggestions I can do to try to fix it, I'm willing to do so, just incase it happens to someone else. Thanks for helping.
Sent from my myTouch_4G_Slide using xda app-developers app
msndroid said:
I kinda gave up on the phone. Ill just buy a galaxy nexus by the end of the month. But if there's still any suggestions I can do to try to fix it, I'm willing to do so, just incase it happens to someone else. Thanks for helping.
Sent from my myTouch_4G_Slide using xda app-developers app
Click to expand...
Click to collapse
You could try to claim warranty, but the thing is, it's already modified so most likely, they won't touch it. A fail-pu error usually means a hardware failure. Most likely, your chip failed and will not write any more.
Another thing you could try to do is brick it, and then claim warranty. You can always say that it turned off and never turned on again.
Keylogger_0 said:
You could try to claim warranty, but the thing is, it's already modified so most likely, they won't touch it. A fail-pu error usually means a hardware failure. Most likely, your chip failed and will not write any more.
Another thing you could try to do is brick it, and then claim warranty. You can always say that it turned off and never turned on again.
Click to expand...
Click to collapse
The warranty is not the same as the tmobile insurence is it? Because I took that off thinking I wouldn't need it. Also stupid question, how would I go about bricking it?lol
Sent from my myTouch_4G_Slide using xda app-developers app
msndroid said:
The warranty is not the same as the tmobile insurence is it? Because I took that off thinking I wouldn't need it. Also stupid question, how would I go about bricking it?lol
Sent from my myTouch_4G_Slide using xda app-developers app
Click to expand...
Click to collapse
HTC usually has warranty too. The thing is, they will most likely refuse it if you have modified the phone.
Bricking can be easy. But, bricking with a Fail-PU error isn't always easy.
PM me later, and I will try to assist you. I'm a bit busy right now so just send me a PM to remind me.
Keylogger_0 said:
HTC usually has warranty too. The thing is, they will most likely refuse it if you have modified the phone.
Bricking can be easy. But, bricking with a Fail-PU error isn't always easy.
PM me later, and I will try to assist you. I'm a bit busy right now so just send me a PM to remind me.
Click to expand...
Click to collapse
Will do. Thanks I appreciate it
Sent from my myTouch_4G_Slide using xda app-developers app
Hi,
I'm having similar issue with my phone, tried a lot of things when I enter command
fastboot oem readsecureflag
I'm getting this:
(bootloader) secure_flag: 3
OKAY [ 0.010s]
finished. total time: 0.011s
If anybody is still checking that thread appreciate any help.
Thanks.
Guys, i tried searching on google and xda, and am either confused or SOL. I have been given a 100% stock evo lte with hboot 1.19. (yes, I've read the countless posts of how lame this is, nothing i can do about it.) All i want is that sweet CM10 so i can get a taste of jellybean. Plain and simple. Nothing too fancy or crazy. Could someone kindly direct me to a step-by-step? I dont care about s-off if i dont need it, I just want to go from stock to cm10, I'm just not sure where to start or what to do first.
Thank you for your time.
Sent from my EVO using xda app-developers app
I'll break in down into the big chunks, but there are directions for each of these on the forums
Unlock the bootloader, put on TWRP, flash CM10, flash gapps, fastboot flash the kernel
http://androidforums.com/evo-4g-lte-all-things-root/606748-how-install-kernels-h-boot-1-15-a.html
I'll just say TeamWin has been awesome with their recovery, dumlock is built into their latest recovery, probably the least ideal but it does give you the most control over your phone, it will boot recovery from within boot and allow you to use the recovery as you normally would and the directions are very easy to follow
All those directions are for hboot 1.15, have we confirmed that this is safe for 1.19? I cant afford to brick this phone
Sent from my EVO using xda app-developers app
Mockingbird946 said:
All those directions are for hboot 1.15, have we confirmed that this is safe for 1.19? I cant afford to brick this phone
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
It says 1.15 because thats when I wrote the guide.
1.15=1.19 for the methods needed to flash things
That + at the end means anything above 1.15
Okay, so i'm getting stuck when i try to flash twrp recovery
c:\Android\platform-tools>fastboot flash recovery openrecovery-twrp-2.1.8-jewel.
img
sending 'recovery' (7220 KB)...
FAILED (command write failed (Too many links))
finished. total time: 0.001s
c:\Android\platform-tools>fastboot flash recovery openrecovery-twrp-2.1.8-jewel.
img
sending 'recovery' (7220 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.637s
Any ideas why this is happening to me? One thread suggested using a different USB port, no dice...
so im guessing you unlocked the bootloader, you booted back to the bootloader and selected fastboot, did you unplug the usb and plug it back in for good measure? once in a while fast boot will not recognize usb, if you checked all that and still cant get it, use the adbtools package rather then sdk
WOOHOO! So it took several wipes and re-flashes, but I am now running CM10!!! Thank you so much! The only problem is my SD card won't mount, any ideas?
Sent from my EVO using xda app-developers app
Mockingbird946 said:
WOOHOO! So it took several wipes and re-flashes, but I am now running CM10!!! Thank you so much! The only problem is my SD card won't mount, any ideas?
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
I believe thats a known issue at this point.
These are nightlies, so all the bugs arent squashed yet
Mockingbird946 said:
WOOHOO! So it took several wipes and re-flashes, but I am now running CM10!!! Thank you so much! The only problem is my SD card won't mount, any ideas?
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
I know at least one person that was having that problem in cm10 was able to fix it by formatting the sd card in Windows. There are instructions here:
http://forum.xda-developers.com/showthread.php?t=1812774
Just make sure to backup the contents on your pc first if possible.
Sent from my EVO LTE
premo15 said:
I know at least one person that was having that problem in cm10 was able to fix it by formatting the sd card in Windows. There are instructions here:
http://forum.xda-developers.com/showthread.php?t=1812774
Just make sure to backup the contents on your pc first if possible.
Sent from my EVO LTE
Click to expand...
Click to collapse
Tried this, still no dice. Someone on another thread said using ICS SD Binder worked, but I don't know what settings to use in the app... I'm worried I'll mess something up if I pick the wrong options!
Sent from my EVO using xda app-developers app
Figured out what my problem was. I was formatting the external SD... I formatted the internal from windows through recovery mount. Works like a charm. Thanks again to all who helped me on this!
Sent from my EVO using xda app-developers app
I had to get a new Evo this weekend because my old one went into a coma. Now I havent been on here too much lately due to my new job, so the last time I rooted/s-off-ed something was about a year ago. So forgive me. I was able to successfully after many Many MANY tries to do so. I just kept putting in the same code over and over, literally. then came to part to 'root' it. I follwed 'bigdaddy619's' instuctions to a "t". (or at least I felt I did.) im sure I got all the drivers updated as well. I even followed along with a video on YouTube However, I was unsuccessful in my attempts to root. I kept getting the same error, and if I did NOT get the error, then it just got stuck on "sending file <8024mb>", or something of that nature. That seriously happened about 8 times. the green bar on the fastboot screen filled up and nothing happened. Nothing happened at all. I know its supposed to be somewhat instantaneous on rooting, but I even waited a good 5 mins.
To avoid possible encounter with the forum police (sarcasm) I tried other ways to do so.I think I may end up regretting doing so. I downloaded GooManager and installed to the open recovery script which I believe is twrp 2.6.0.0. It says it installed sucessfully, but of course I was unable to boot into recovery. When I tried, I only got the exclamation mark in a triangle over-the-phone picture.I then went t Twrps website and downloaded the PJ75IMG which is twrp 2.3.x.x. When I tried fastboot-that, it failed and said something along the lines of, this version is older. So itried to find a way to delete TWRP which I could not.... Dealing anything on the HBOOT screen makes me nervous
so my questions are:
1. DO I just need to flash an RUU and start from scratch? (that would be my least favorite option.)
2. Is there some other way to 'root' without starting over?
3. Do I need to delete any htc/android/google affiliated programs on my computer?
4. im lost.
I have HBOOT 2.09, Software 3.16.651.3
check pm
Good day!
Can you kindly post what you did to resolve this issue? I have the EXACT same issue. I have unlocked the bootloader with no problem but flashing recovery gives me fail over and over....
Thanks in advance.
enochbenjamin said:
Good day!
Can you kindly post what you did to resolve this issue? I have the EXACT same issue. I have unlocked the bootloader with no problem but flashing recovery gives me fail over and over....
Thanks in advance.
Click to expand...
Click to collapse
What command are you using to flash the recovery? Is the recovery file in your ADB tools folder?
Sent from my EVO using xda premium
FinZ28 said:
What command are you using to flash the recovery? Is the recovery file in your ADB tools folder?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
I am on a mac so I just have an android folder on my desktop and I am running:
./fastboot-mac flash recovery openrecovery-twrp-2.6.0.0-jewel.img
sending 'recovery' (8204 KB)... OKAY
writing 'recovery'... FAILED (remote: image update error)
enochbenjamin said:
I am on a mac so I just have an android folder on my desktop and I am running:
./fastboot-mac flash recovery openrecovery-twrp-2.6.0.0-jewel.img
sending 'recovery' (8204 KB)... OKAY
writing 'recovery'... FAILED (remote: image update error)
Click to expand...
Click to collapse
What's your bootloader version?
Sent from my EVO using xda app-developers app
jocarog said:
What's your bootloader version?
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Hboot 2.09/3.16 software version.
Sent from my EVO using xda premium
In my case after moonshining 5 times or more , my DNA got hang/stuck no response at all and status in PC waiting for device.
I have to press power button until power off and start up again.
That alway happened like that (i tried more than 10 times with same result) , looks like moonshining never finished its job,
because my DNA always get stuck. In hboot status is TAMPERED and LOCK
I have tried revone but always got error 2 result.
Now got stuck with firmware 2.06 and on android software number 1.15.605.4 710RD
I tried to return to firmware 1,15 so that could flash to StockRUU 1,15 but failed
D:\Android>fastboot flash zip PL83IMG.zip
sending 'zip' (434 KB)...
OKAY [ 0.201s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
Afterwards now wifi I to died after trying moonshine-s-off, I have tried factory the re-set but wifi continue to error
Please help what should i do.
Sorry for my bad english.
HBOOT-1.33.0001
RADIO-1.01.04.0308
Ruu
Sent from my dlx using XDA Premium 4 mobile app
Jaggar345 said:
Ruu
Sent from my dlx using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Could not the Ruu, because of stock of the ruu only had the version 1,15
pisang_aza said:
Could not the Ruu, because of stock of the ruu only had the version 1,15
Click to expand...
Click to collapse
Sounds like you have the same issue i am. Check my thread out and follow it. So far ive been stuck though. got a warranty claim though and got my new DNA. i have 2 more days before i have to send this one back
http://forum.xda-developers.com/showthread.php?t=2552804
I messed up when going to sense 6 and am trying to ruu back and apply the updates. Well I did RUU earlier today and it worked fine. Now I can't for some reason. Running rooted stock from Android Development forum and adb and fastboot both work fine. I get error 155. Tried relocking the bootloader, rebooting both phone and pc. Don't know what else to do. Sprint btw. Using the exe file. Worked fine hours ago.
cstrife999 said:
I messed up when going to sense 6 and am trying to ruu back and apply the updates. Well I did RUU earlier today and it worked fine. Now I can't for some reason. Running rooted stock from Android Development forum and adb and fastboot both work fine. I get error 155. Tried relocking the bootloader, rebooting both phone and pc. Don't know what else to do. Sprint btw. Using the exe file. Worked fine hours ago.
Click to expand...
Click to collapse
I've tried the zip as well and errors out as well...
C:\Program Files (x86)\Android\sdk\platform-
target reported max download size of 1542111
sending 'zip' (1271680 KB)...
OKAY [ 49.560s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (status read failed (Too many links))
finished. total time: 56.335s
I am at a loss. The stock rom I downloaded won't let me update to 4.4.2 or sense 6. I have both updates downloaded I just need to get back to stock so I can take the updates or a rom that will allow me to. The stock roms available are missing files that are needed for the update.
BTW: Hboot 2.49.0000 Perhaps I have to downgrade Hboot or something really could use some help here. Pretty much stuck on this for 24 hours.
Sorry I keep bumping but I am at a loss and may have to return. I can find way to take OTA. RUU fails after it says erasing user data and gets to about 2% and then says sending till it fails. I've done just about everything I can think of really could use some outside ideas here...
EDIT: At worst could someone upload a stock nandroid with all the apps so I can take the OTA?
cstrife999 said:
Sorry I keep bumping but I am at a loss and may have to return. I can find way to take OTA. RUU fails after it says erasing user data and gets to about 2% and then says sending till it fails. I've done just about everything I can think of really could use some outside ideas here...
EDIT: At worst could someone upload a stock nandroid with all the apps so I can take the OTA?
Click to expand...
Click to collapse
Are you s-off?
Sent from my HTC6525LVW using Tapatalk
dottat said:
Are you s-off?
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Yes sir.
Sent from my HTC0P3P7 using XDA Free mobile app
cstrife999 said:
Yes sir.
Sent from my HTC0P3P7 using XDA Free mobile app
Click to expand...
Click to collapse
Did you try putting that ruu.zip on a fat32 formatted sd card and letting the phone attempt to ruu from boot?
Md5 of the zip matches ?
Can you post a copy of the output of
Fastboot getvar all
Edit out your serial and imei....
Sent from my HTC6525LVW using Tapatalk
dottat said:
Did you try putting that ruu.zip on a fat32 formatted sd card and letting the phone attempt to ruu from boot?
Md5 of the zip matches ?
Can you post a copy of the output of
Fastboot getvar all
Edit out your serial and imei....
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
No ex SD card laying about. Flyhalf just sent me a ROM to try and help me out. I'm gonna download it and give it a shot. Either way thanks for calming me a bit. I rarely get into these situations lol
Sent from my HTC0P3P7 using XDA Free mobile app
cstrife999 said:
No ex SD card laying about. Flyhalf just sent me a ROM to try and help me out. I'm gonna download it and give it a shot. Either way thanks for calming me a bit. I rarely get into these situations lol
Sent from my HTC0P3P7 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah I told him you were stuck. Let us know how you make out. One way or another I'm sure you can get er back as long as you remain s off.
Sent from my HTC6525LVW using Tapatalk
dottat said:
Yeah I told him you were stuck. Let us know how you make out. One way or another I'm sure you can get er back as long as you remain s off.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Yea I took a walk to get some LTE its literally a block away lol almost done with the download I'll reflash twrp and get right back at your. Thanks so much man
Sent from my HTC0P3P7 using XDA Free mobile app
Worked great thank you so much!!!!
Sent from my HTC0P3P7 using XDA Free mobile app