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
Help! My DNA isn't working. I just used the unlock bootloader (Still s-on) and I had my recovery flashed so as usual I wiped all data and had a rom ready to sideload, but when I went to sideload everything said "Couldn't mount" and I couldnt do anything. So I got the RUU and I started to flash it and all of a sudden I keep getting error:178 image file. I saw someone else had this problem and they had a rom flashed and they got back in after unlocking it again but I dont have a rom installed so I have nothing. (Yes I relocked the bootloader when trying to flash the RUU and I did run it as an Admin.) Someone please help me
Edit: Phone is now fixed, I went to IRC and a guy named Beaups took remote control and fixed it. Im not sure if thats his XDA username or not but if you guys see him make sure to give him a thanks Night everyone
Halcyon7 said:
Help! My DNA isnt working. I just used the unlock bootloader (Still s-on) and I had my recovery flashed so as usual I wiped all data and had a rom ready to sideload, but when I went to sideload everything said "Couldnt mount" and I couldnt do anything. So I got the RUU and I started to flash it and all of a sudden I keep getting error:178 image file. I saw someone else had this problem and they had a rom flashed and they got back in after unlocking it again but I dont have a rom installed so I have nothing. (Yes I relocked the bootloader when trying to flash the RUU and I did run it as an Admin.) Someone please help me
Click to expand...
Click to collapse
Did you use this?
http://forum.xda-developers.com/showthread.php?t=2017525
I am unfamiliar with sideload but seems like with the correct files and the right person with sideload experience, you should be ok, Someone will step up here, may take a bit.
Its ok its very fixable, at this point. Just be very careful and very patient.
The worst thing you can do with something like this is get in a hurry or try to fix it while you're still very stressed out.
I'm passing on this advice because I almost screwed up yesterday because I made a boo boo and was in a huge hurry.
I'm going to wait for someone who knows more about this particular issue to chime in, but you have my word, I will help you resolve it after I do some more research while I wait for someone with more information or experience to post some info.
Sent from my HTC6435LVW using Xparent Red Tapatalk 2
In the original unlock downloader thread, there is a link to an irc chatroom, I would suggest you go there as well as look for help here, and be patient waiting for some one to respond ...
Sent from my HTC6435LVW using Tapatalk 2
rootntootn said:
Did you use this?
http://forum.xda-developers.com/showthread.php?t=2017525
I am unfamiliar with sideload but seems like with the correct files and the right person with sideload experience, you should be ok, Someone will step up here, may take a bit.
Click to expand...
Click to collapse
Thats pretty much what I did but I keep getting that error:178 image file problem when its trying to finish (I am using the RUU_DLX_WL_JB_45_VERIZON_WWE_1.15.605.4_Radio_1.00.00.1023_3_NV_VZW_1.98_002_release_290923_signed.exe RUU) Also my phone is recognized as 2.04 when I haven't flashed anything
I had a similar situation recently. I am unlocked and s-off and i accepted the 2.04 update. I needed to go back to the original firmware but the ruu wouldnt flash and gave me an error 158 image error. The only way i was able to run the ruu was to revert my hboot and radio from http://forum.xda-developers.com/showpost.php?p=38379254&postcount=19. Im sure there is another way, but this helped me.....good luck.
Halcyon7 said:
Help! My DNA isnt working. I just used the unlock bootloader (Still s-on) and I had my recovery flashed so as usual I wiped all data and had a rom ready to sideload, but when I went to sideload everything said "Couldnt mount" and I couldnt do anything. So I got the RUU and I started to flash it and all of a sudden I keep getting error:178 image file. I saw someone else had this problem and they had a rom flashed and they got back in after unlocking it again but I dont have a rom installed so I have nothing. (Yes I relocked the bootloader when trying to flash the RUU and I did run it as an Admin.) Someone please help me
Click to expand...
Click to collapse
Re-Unlock your bootloader with your Unlock token (Unlock_code.bin) then do a fastboot flash recovery recovery.img and use the CWM recovery that is 6.0.2.8 (i believe is the most recent version) and you should be able to sideload your rom ... or if sideloading doesnt work just do an adb push rom.zip /sdcard/rom.zip and that will put the rom that you want to use on the root of the sdcard and then you can flash that there...
This should hopefully get you working again...
beasleyj62 said:
I had a similar situation recently. I am unlocked and s-off and i accepted the 2.04 update. I needed to go back to the original firmware but the ruu wouldnt flash and gave me an error 158 image error. The only way i was able to run the ruu was to revert my hboot and radio from http://forum.xda-developers.com/showpost.php?p=38379254&postcount=19. Im sure there is another way, but this helped me.....good luck.
Click to expand...
Click to collapse
I keep getting this when I flash the hboot
C:\Users\owner\AppData\Local\Android\android-sdk\platform-tools>fastboot flash z
ip PL83IMG.zip
sending 'zip' (434 KB)...
OKAY [ 0.205s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 0.274s
and when I flash the Radio I get
C:\Users\owner\AppData\Local\Android\android-sdk\platform-tools>fastboot flash z
ip PL83IMG.zip
error: cannot load 'PL83IMG.zip': Unknown error
you re-locked your bootloader.....
try what .torrented suggested or re-unlock and try to re-flash the zips.
beasleyj62 said:
you re-locked your bootloader.....
try what .torrented suggested or re-unlock and try to re-flash the zips.
Click to expand...
Click to collapse
I can unlock it at anytime....
see if you can flash after you unlock again
Did you flash the stock recovery back to your phone before you tried the ruu?
Sent from my HTC Droid DNA
All I needed to run the RUU was the ENG Hboot. Flash it then you should be able to install the RUU provided you have the correct drivers installed.
Sent from my HTC6435LVW using xda app-developers app
He is still s-on.
Sent from my HTC Droid DNA
Andro X said:
Did you flash the stock recovery back to your phone before you tried the ruu?
Sent from my HTC Droid DNA
Click to expand...
Click to collapse
How would I go about doing that?
beasleyj62 said:
see if you can flash after you unlock again
Click to expand...
Click to collapse
I didnt work. This is my 2nd DNA so I have done this before and it worked successfully(The first one had a screen problem)
I'm away from my pc right now but if you look around the forum for the link to stock recovery, it might help as suggested above
Sent from my HTC6435LVW using Tapatalk 2
Halcyon7 said:
How would I go about doing that?
Click to expand...
Click to collapse
The RUU flashes a stock recovery... all that is required for running the RUU is a LOCKED bootloader...
Did you by chance take the OTA op? because if you did the RUU wont work...
beasleyj62 said:
I'm away from my pc right now but if you look around the forum for the link to stock recovery, it might help as suggested above
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
I only found 1 link on my computer doctors forum but that link wasn't it
.torrented said:
The RUU flashes a stock recovery... all that is required for running the RUU is a LOCKED bootloader...
Did you by chance take the OTA op? because if you did the RUU wont work...
Click to expand...
Click to collapse
No I haven't. I used the s-off facepalm method and I did everything as it said and now when I went into recovery nothing will mount and my device when trying to use the RUU says its a 2.04. So I didnt take the ota but thats what it is recognized as
So I bought a Thunderbolt off eBay. Seller said it just had a cracked screen. Replaced that and come to find it's in a boot loop. It won't boot into the ROM or into Recovery. No big deal..
I go into hboot, unlock the bootloader, great.
Now, however, I am trying to install a recovery, and it won't even boot into recovery, just shows the splash image and then reboots into a loop. I've tried installing, CWM (touch and non), amon-ra, and one other one, all with the same results.
I tried flashing the latest ruu to get back to step 1, but I get the message that the mainver is older than currently installed and it won't let me install the ruu.
Any ideas?
Search for a setmainver.zip file on here that should spoof your version #.
The new way to root isn't posted on xda and is on santods forums
Sent from my SCH-I535 using xda app-developers app
tburns said:
Search for a setmainver.zip file on here that should spoof your version #.
The new way to root isn't posted on xda and is on santods forums
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
That requires flashing from recovery; I can't even get into recovery.
Crap that's right. Can u get into fastboot? If u can do this:
"Fastboot getvarall" to get your version.
If you can get the RUU as phxxx.zip (forget the numbers) to flash in the boot loader you can edit the android text file version # to the same as your phone using 7zip. Edit the mainver line to =or> than yours
Cant do this with an exe ruu.
Hope this helps
I have the 2.11.605.19 ruu zip its little over 400mb. U can upload it if u need it.
Sent from my SCH-I535 using xda app-developers app
tburns said:
Crap that's right. Can u get into fastboot? If u can do this:
"Fastboot getvarall" to get your version.
If you can get the RUU as phxxx.zip (forget the numbers) to flash in the boot loader you can edit the android text file version # to the same as your phone using 7zip. Edit the mainver line to =or> than yours
Cant do this with an exe ruu.
Hope this helps
I have the 2.11.605.19 ruu zip its little over 400mb. U can upload it if u need it.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Okay, I hadn't thought of that; I'll give it a shot, thanks!
I tried it; hboot reads the file, gets to "parsing" and then stops. Do I need to do anything special, or has anyone already gotten something like this to work?
Relocked bootloader (derp), and now it is checking the file... and no option to install.. gah..
Tried installing via fastboot:
c:\android>fastboot oem rebootRUU
...
OKAY [ 0.162s]
finished. total time: 0.166s
c:\android>fastboot flash zip PG05IMG.zip
sending 'zip' (454974 KB)...
OKAY [ 74.499s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 151.845s
Hmm. Did you use 7zip to open and edit? I don't use windows too often?
Also I think you have to make your edits with notepad+ in windows (free). Sorry I use Linux..
This should solve the verification error your getting.
Sent from my SCH-I535 using xda app-developers app
What hboot version did the thunderbolt have when you bought it? You may have only have needed to finish running the revolutionary tool.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
What hboot version did the thunderbolt have when you bought it? You may have only have needed to finish running the revolutionary tool.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
hello, i'm having the same problem,no recovery,no booting up normal, my hboot is 1.08.0000,my radio is 2.03.00.0201r,fastboot allows me to flash a recovery,but won't go to it,just boot to the splash screen,then rebots non stop untill i pull the battery
Are you s off?
Sent from my HTC6500LVW using Tapatalk
disconnecktie said:
Are you s off?
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
sadly no
I think I messed up my phone partitions...
Background: I installed Haunted Carbon a couple of weeks ago. It worked great. I saw that NIN updated the haunted kernel to X.2.3.6 so I thought I'd update my kernel. I'm a noob in working with custom ROMs and thought it would just be a simple flash...boy was I wrong. Nothing on my phone works anymore.
When I boot into TWRP, and click on the command line icon on the bottom of the screen, I keep seeing the error: "E:Unable to mount '/sd-ext'"
When I try to wipe everything but my SD card, it says that the wipe as FAILED.
It says it's E:Unable to mount /usb-otg & /sd-ext​
Any ideas on how I can fix my phone? By the way, I tried using fastboot to load the original kernel onto the phone but it just hangs (it says it tries to copy, but just sits there forever..). I honestly think my phone partitions are messed up.
Phone:
TWRP 2.5 (i'm able to boot into it)
S-Off
... any other details I'm missing?
I'm not even able to install a ROM in TWRP at this point... it just says "failed" when I try.
Also, sorry if I'm missing any key details in my posts! I'm a noobie at custom ROMming, but feel free to ask me anything and I'll try to answer as best I can!
This should get you fixed up
http://forum.xda-developers.com/showthread.php?t=2443108
bigdaddy619 said:
This should get you fixed up
http://forum.xda-developers.com/showthread.php?t=2443108
Click to expand...
Click to collapse
Thx bigdaddy! I'm trying QBKing's unbrick instructions... if those don't work, I'll definitely be giving your link a run!
Quick update:
My TWRP stopped working... can't even boot into it from the bootloader. I tried reinstalling it through fastboot, but no files want to transfer (tried both that and boot.img through fastboot usb).
any ideas on how i can fix? i'm fresh out of ideas ((
What happens when you try to boot to recovery from the bootloader? What were you doing just prior to not being able to access recovery?
Download the latest version of TWRP and try to re-install it. Prior to that, use the "fastboot erase recovery" command while connected via Fastboot USB mode.
FinZ28 said:
What happens when you try to boot to recovery from the bootloader? What were you doing just prior to not being able to access recovery?
Download the latest version of TWRP and try to re-install it. Prior to that, use the "fastboot erase recovery" command while connected via Fastboot USB mode.
Click to expand...
Click to collapse
Hi Fin!
I was just trying to install an updated kernel with GooManager... it turns out that the kernel probably wasn't compatible with Carbon. Also, erasing recovery failed... the msg I received is below:
fastboot erase recovery
erasing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.005s
Fr0HiKE said:
Hi Fin!
I was just trying to install an updated kernel with GooManager... it turns out that the kernel probably wasn't compatible with Carbon. Also, erasing recovery failed... the msg I received is below:
fastboot erase recovery
erasing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.005s
Click to expand...
Click to collapse
Okay, so what happens when you try to boot into recovery?
I have a thought on how to fix this if you're shut out of recovery Take a look at the link below.
http://forum.xda-developers.com/showthread.php?t=2197909
This will unroot your phone, but you'll have a working device once again. You can then go back through the steps to root it again.
Sent from my HTC EVO 4G LTE
This just recently happened and I'm s-on it would but only white screen would just show so what I did was I tries vipers flash boot img 1.2 and it work
Sent from my EVO using XDA Premium 4 mobile app
bravo1565 said:
This just recently happened and I'm s-on it would but only white screen would just show so what I did was I tries vipers flash boot img 1.2 and it work
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
He's S-off.
Sent from my HTC EVO 4G LTE
FinZ28 said:
He's S-off.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
I'm actually S-on! Still having issues
Fr0HiKE said:
I'm actually S-on! Still having issues
Click to expand...
Click to collapse
Okay. I was going off your original post. What Hboot are you on?
Can you do without your phone for a couple of days? If so, shoot me a PM.
Sent from my HTC EVO 4G LTE
FinZ28 said:
Okay. I was going off your original post. What Hboot are you on?
Can you do without your phone for a couple of days? If so, shoot me a PM.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
I'm on HBOOT 2.09, and yes I can do without my phone for a couple of days (using a backup atm, HTC EVO Shift ). PMing you now!
Fr0HiKE said:
I'm on HBOOT 2.09, and yes I can do without my phone for a couple of days (using a backup atm, HTC EVO Shift ). PMing you now!
Click to expand...
Click to collapse
Check your PM.
Sent from my HTC EVO 4G LTE