Related
Hi experts
One of my friend brought his Htc stuck at Htc logo even I cannot make factory reset in boot mode.. When I click factory reset nothing happens.. Don't know where to start? Can somebody tech me
I made gold card successfully
Thank you
Give some more info please
1) what is written on the top part of the screen when in boot mode
it should look similar to this:
Code:
---AlphaRev---
SAGA pvt ship S-off RL
HBOOT-6.98.1002
RADIO-3805.04.02.01_M
eMMC-boot
2) can you access RECOVERY from the boot mode menu
if yes make a picture of it and attach it here
Also see here, there are some ways to restore from white screen issue.
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0002
RADIO - 3805.06.02.03_M
eMMC - boot
and if i press recovery showing recovery symbol and phone get off and vibrating 3 times
And i downloaded this file
RUU_Saga_hTC_Asia_WWE_1.48.707.1_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199476_signed.exe
when i try to update ..its stuck at rebooting to bootloader
I have a similar problem. But mine is s-off and unrooted, it occurred when I tried updating with the system OTA update (about 230mb in size). It updated, showed the circular green stuff on the black screen, booted a few times then just stuck at the HTC screen on the white background.
-Revolutionary-
SAGA PUT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO- 3822.10.08.04_M
eMMC-boot
Mar 10 2011, 14:58:38
Please would appreciate your help
sharaz191 said:
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0002
RADIO - 3805.06.02.03_M
eMMC - boot
and if i press recovery showing recovery symbol and phone get off and vibrating 3 times
And i downloaded this file
RUU_Saga_hTC_Asia_WWE_1.48.707.1_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199476_signed.exe
when i try to update ..its stuck at rebooting to bootloader
Click to expand...
Click to collapse
It seems that your problem is complicated. Stock software and no recovery access makes it difficult to give an appropriate advice. Maybe something wrong was flashed on this phone or the worst case - "fried" eMMC chip. You can try to search across the forum for any similar or try various solutions but I cannot advice how to proceed. Sorry
linkin8k said:
I have a similar problem. But mine is s-off and unrooted, it occurred when I tried updating with the system OTA update (about 230mb in size). It updated, showed the circular green stuff on the black screen, booted a few times then just stuck at the HTC screen on the white background.
-Revolutionary-
SAGA PUT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO- 3822.10.08.04_M
eMMC-boot
Mar 10 2011, 14:58:38
Please would appreciate your help
Click to expand...
Click to collapse
There are at least 10 other threads from the past 2 weeks with exactly the same problem. Do some reading, the solution is simple...
Please just tell me what to do or give me the thread cause I have searched and can't find precisely what will help. Just post something please I beg you.
here you go
Sent from my HTC Desire S using Tapatalk
Can I solve by jtag?
sharaz191 said:
Can I solve by jtag?
Click to expand...
Click to collapse
Surely simpler to return under warranty?
Swyped from my Desire S using XDA Premium
Tried everything in the thread and it won't still work.
I downloaded RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30.0822U_3822.10.08.04_M_release_219480_signed and used it. It showed successful but got stuck at the htc logo white screen again. When i tried using the ruu again it showed the old version which it supposedly upgraded was still in the phone.
Please help am so frustrated
linkin8k said:
I downloaded RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30.0822U_3822.10.08.04_M_release_219480_signed and used it. It showed successful but got stuck at the htc logo white screen again. When i tried using the ruu again it showed the old version which it supposedly upgraded was still in the phone.
Please help am so frustrated
Click to expand...
Click to collapse
Hint - flash hboot 0.98.2000
After use the latest RUU 2.10.401.8
Sent from my HTC Desire S using Tapatalk
Thanks for the quick reply. I have already tried flashing hboot_0.98.0000_361a7ba6_0310 onto it using android flasher in "fastboot usb plug" but it reboots and gets stuck at the htc logo again until i remove the battery.
Also here is what androidflasher shows me :
sending "hboot" (1024kb)...
OKAY [0.191s]
writing "hboot"...
(bootloader) image update is bypassed!
OKAY [0.030s]
finished.total time:0.221s
rebooting into bootloader...
OKAY [0.248s]
finished.total time:0.248s
rebooting....
finished. total time: 0.244s
**update**
was able to flash 4ext recovery using android flasher onto my device and tried updating with the ruu again. It still gets stuck at the htc logo white background (so i painfully remove battery again) but when i try running the ruu again from my pc it shows that i have the same version as the ruu.
Still stuck at white screen. Help!!!
linkin8k said:
**update**
was able to flash 4ext recovery using android flasher onto my device and tried updating with the ruu again. It still gets stuck at the htc logo white background (so i painfully remove battery again) but when i try running the ruu again from my pc it shows that i have the same version as the ruu.
Still stuck at white screen. Help!!!
Click to expand...
Click to collapse
see the version of the bootloader
if it is still 6.98.xxxx this is you problem. Flash 0.98.2000 with PG88IMG.zip from the SDcard or try 2.00.2002 - you can find this in the forums also
linkin8k
I have the same problem and I have not found the solution up here.
can anybody tell me can i solve this by JAG?i can do jtag my self
thanks for the replies sorry i couldn't post yesterday was trying to be in a festive mood.
**my progress**
I have tried all i can to update the bootloader, from putting the pg88img file in through root of sd to update through 4ext recovery to tryin to use android flasher to put the 0.98.2000 it won't just update.
please what else can i do?? is there a hboot installer for windows for me to try??
please help AmidaBuddha u have done a lot but i still need a little help. thanks
As much as i know would be the last possible solution to replace the bootloader with dd command inside adb shell or try to flash it with fastboot (to make this the htc drivers [if you are using windows] and the android sdk with the given android plattform-tools must be installed, if some parts are not present look at the index thread)
Walkthrough:
fastboot:
reboot your device to bootloader and put it in fastboot mode
open commanline at your pc
attach device to pc
cd to the directory where the hboot.img is ( extract it from the pg88img.zip file)
Code:
fastboot devices
(your device should show up as some letters and digits at the right of it should stand recovery, also the adb daemon is started if it wasn't running before)
fastboot flash hboot hboot.img
this replaces your current hboot with the hboot.img file, don't interrupt the process or pull the usb cable, this can brick your device, i'm not responsible if something goes wrong.
dd:
put the needed .img file of the bootloader at the root of your sd (extract it from the pg88img.zip file) and rename it to hboot.img
reboot to recovery
Open commandline at your pc
attach device to pc
Code:
adb devices
(your device should show up as some letters and digits at the right of it should stand recovery, also the adb daemon is started if it wasn't running before)
adb shell
(this opens the adb command shell, from where you can execute shell commands right at your device)
dd if=/dev/block/mmcblk0p18 of=/sdcard/backup.img
(this backups your current bootloader partition to the backup.img file)
dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18
(this replaces your bootloader partition with the boot.img)
exit
(exits adb shell)
adb reboot bootloader
(reboots your device to bootloader)
this backups your current bootloader to /sdcard/backup.img and replaces it with the boot.img, but beware this is hard stuff and be carefull, don't stop the execution of the any dd command and never pull the usb-cable while it writes your bootloader, this definitly can brick your device, i'm not responsible if something goes wrong, good luck.
Tectas thanks, see what i get using fastboot:
on command line:
c:\users>fastboot devices
SH14HTJ05*** fastboot
c:users> cd c:\temp
c:\temp>fastboot flash hboot hboot.img
sending `hboot` <1024 kb>... OKAY
writing `hboot`... INFOimage update is bypassed!
OKAY
on phone under bootloader menu:
Can not roll back hboot version
........
will try dd option now.
I don't like starting new threads especially but I have searched and searched and not come up with an answer/problem quite the same as mine. I am not a TOTAL noob and do understand s-on, s-off, htcdev unlock etc. Here goes
I got a Sensation from a friend who acuired it from God knows when but he asked me if it can be fixed. Its currently stuck in fastboot mode. Its Locked S-OFF however NOTHING I try works. Here is some info
BOOTLOADER
*** Locked ***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.0000
eMMC-boot
Jan 13 2012,17:33:34
CID
Is already Super CID = 11111111
RECOVERY
There is no custom recovery flashed and trying to flash recovery via fastboot fails saying "remote: not allowed"
FASTBOOT COMMANDS
Fastboot commands work to get cid etc but get a "remote: not allowed" to erase or flash boot,img, any rom or any hboot or ANYTHING
BOOTLOADER FLASHING
If I try to flash a firmware file through Bootloader, it parses the P58IMG.zip but fails on Bootload saying Fail-PU Partition update failed
FLASH SHIPPED RUU
Trying a shipped ROM also fails. Goes smoothly, reads current image on phone as 1.45.401.3 but once it starts updating, it sticks in waiting for boatloader and gives ERROR[171] while phone has restarted in FASTBOOT mode
HTCDEV Unlock
I thought I would give the HTCDEV method a go even though I know this is redundant since I am already supposedly s-off but even that fails cuz no lock, unlock screen comes up. Flashing of Unlock_boot.bin goes fine
I am at a TOTAL loss now cuz since I am already S-OFF, I should have been able to flash recover or flash a rom or boot image to get phone working again. NOTHING works!!
Any ideas anyone? Apologies if this has been covered before and I couldnt find it.
tabi13 said:
I don't like starting new threads especially but I have searched and searched and not come up with an answer/problem quite the same as mine. I am not a TOTAL noob and do understand s-on, s-off, htcdev unlock etc. Here goes
I got a Sensation from a friend who acuired it from God knows when but he asked me if it can be fixed. Its currently stuck in fastboot mode. Its Locked S-OFF however NOTHING I try works. Here is some info
BOOTLOADER
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.0000
eMMC-boot
Jan 13 2012,17:33:34
CID
Is already Super CID = 11111111
RECOVERY
There is no custom recovery flashed and trying to flash recovery via fastboot fails saying "remote: not allowed"
FASTBOOT COMMANDS
Fastboot commands work to get cid etc but get a "remote: not allowed" to erase or flash boot,img, any rom or any hboot or ANYTHING
BOOTLOADER FLASHING
If I try to flash a firmware file through Bootloader, it parses the P58IMG.zip but fails on Bootload saying Fail-PU Partition update failed
FLASH SHIPPED RUU
Trying a shipped ROM also fails. Goes smoothly, reads current image on phone as 1.45.401.3 but once it starts updating, it sticks in waiting for boatloader and gives ERROR[171] while phone has restarted in FASTBOOT mode
HTCDEV Unlock
I thought I would give the HTCDEV method a go even though I know this is redundant since I am already supposedly s-off but even that fails cuz no lock, unlock screen comes up. Flashing of Unlock_boot.bin goes fine
I am at a TOTAL loss now cuz since I am already S-OFF, I should have been able to flash recover or flash a rom or boot image to get phone working again. NOTHING works!!
Any ideas anyone? Apologies if this has been covered before and I couldnt find it.
Click to expand...
Click to collapse
Have you tried playing with fastboot commander? Mabe try formatting all partitions, then installing RUU or PG58IMG ?Or try with different RUUs? The last thing I can think of is to lock the bootloader back, and try to send it to HTC with warranty.
Even fastboot commander, the same as entering commands manually can not flash anything or erase any partition. Dead end there.
tabi13 said:
Even fastboot commander, the same as entering commands manually can not flash anything or erase any partition. Dead end there.
Click to expand...
Click to collapse
what about locking it back to s-on? did you tried it? does it "run" a custom rom ?
First off to use all the fastboot commands you need to have a eng Hboot on the device. You can not use all fastboot commands with a stock Hboot which is what the Hboot 1.27.0000 that you have is. Click on this link to download the JuopunutBear eng Hboot and follow the below instructions to flash it via fastboot.
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip jb_hboot.zip
If you still can not get the device up and going using fastboot after flashing the eng Hboot, or if the Hboot will not flash you may have screwed up partitions on the the device. There is a fastboot or a adb command you can use to get a read out of the partitions but I can not remember it right now, just google it you will find it. I mention this because of the "Fail-PU Partition update failed" message you mentioned.
If it does flash the eng Hboot then you should be able to flash a custom recovery or anything else you want to flash via fastboot. If all else fails though do as gallardo5 sayed and flash the stock ROM via RUU while in fastboot and connected to your computer via USB. Then you can try to start from scratch rooting and installing a custom recovery.
T-Macgnolia said:
First off to use all the fastboot commands you need to have a eng Hboot on the device. You can not use all fastboot commands with a stock Hboot which is what the Hboot 1.27.0000 that you have is. Click on this link to download the JuopunutBear eng Hboot and follow the below instructions to flash it via fastboot.
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip jb_hboot.zip
If you still can not get the device up and going using fastboot after flashing the eng Hboot, or if the Hboot will not flash you may have screwed up partitions on the the device. There is a fastboot or a adb command you can use to get a read out of the partitions but I can not remember it right now, just google it you will find it. I mention this because of the "Fail-PU Partition update failed" message you mentioned.
If it does flash the eng Hboot then you should be able to flash a custom recovery or anything else you want to flash via fastboot. If all else fails though do as gallardo5 sayed and flash the stock ROM via RUU while in fastboot and connected to your computer via USB. Then you can try to start from scratch rooting and installing a custom recovery.
Click to expand...
Click to collapse
Oh yes, I should have mentioned it. I did even try flashing the JB-hboots, both GB and ICS versions. Neither worked.
It gives error on erase cache, oem rebootRUU reboots back to fastboot and then flashing fails
I think you are spot on about the partitions about being mssed up. Even if they can be read out (i saw the commands somewhere myself) can they be repaired at all?
p.s. Thanks for your help
One more thing I should have mentioned and dont know how I missed, the FASTBOOT page says *** Locked *** not *** Unlocked ***. I dont know if this can/should be changed.
I am sorry in advance if I am being silly
tabi13 said:
One more thing I should have mentioned and dont know how I missed, the FASTBOOT page says *** Locked *** not *** Unlocked ***. I dont know if this can/should be changed.
I am sorry in advance if I am being silly
Click to expand...
Click to collapse
If you have a messed up partition you can not fix it without replacing the whole board. And about the locked in fastboot that is why your fastboot commands are not working. But the fact that you can not flash the eng Hboot sorta tells me you got a bad partition and it will not take the flash. Blackwing had the same issue with his Sensation and all the best guys I know that are over on the IRC Help Now channel could not come up with a fix and finally diagnosed it as bad partitions. Hid was the exact same it would give aerroron erase cache. Find the command to get a read out on the partitions and post the read out here.
T-Macgnolia said:
If you have a messed up partition you can not fix it without replacing the whole board. And about the locked in fastboot that is why your fastboot commands are not working. But the fact that you can not flash the eng Hboot sorta tells me you got a bad partition and it will not take the flash. Blackwing had the same issue with his Sensation and all the best guys I know that are over on the IRC Help Now channel could not come up with a fix and finally diagnosed it as bad partitions. Hid was the exact same it would give aerroron erase cache. Find the command to get a read out on the partitions and post the read out here.
Click to expand...
Click to collapse
Tmac.. I solved one guys FAIL-PU errors.. If the op can boot to recovery.. Maybe we can fix it.. Remember I said we CAN so there's a possibility
Edit: but not now.. Or at least until 20th August.. I'm out of station (as I need to do remotely everything)
Sent from my HTC Sensation 4G using xda premium
gameshp, let me know when you can help me out. IF my friend hasnt given up by then. Thank you
I have the same situation, so I'm really hoping for a solution.
-Revolutionary-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
eMMC-boot
Jan 13 2012,17:33:34
hey ppl im ready ..check your PM's ..and let me know
Did you try to navigate back to "HBOOT" and do a "Factory reset"?
If it does not work, maybe you should flash firmware using JTAG.
marcusgolden said:
I have the same situation, so I'm really hoping for a solution.
-Revolutionary-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
eMMC-boot
Jan 13 2012,17:33:34
Click to expand...
Click to collapse
No you don't have the same problem, cause your bootloader is unlocked
Flash the firmware again and try to flash recovery
So my son rooted his AT&T HTC One X (Evita) and put AOKP 10.something (doesn't remember) but never got 4G data to work. He lived with it that way for a while because WiFi works and he has plenty of access at college. But recently he got fed up and wanted to go back to his stock rom to get 4G working again. He doesn't remember exactly what he did but he recalls going into recovery, wiping the cache, then updating TWRP to 2.5. That's when things went wrong. We get:
HTC
quietly brilliant
This build is for development purposes only...
It sits this way for a few minutes then the screen goes blank, but it appears the phone is still on because, when plugged-in to the USB port on my PC I don't get the alert sound that USB has disconnected. Then it reboots. Does this over and over.
I can get into the bootloader by holding-down power and volume-down.
Bootloader tells me:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-ON BL
HBOOT-1.14.0002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
June 11 2012, 14:36:28
HBOOT​
I can also get into TWRP, but can't find any ROMS to install.
I've rooted a few of my androids and can follow instructions, but I'm not real familiar with all the tools and acronyms. Also, I have zero experience with the HTC One X. If there's a newb's guide for unbricking the Evita please point me in the right direction. Otherwise, please be gentle with me and I'll try not to make an ass of myself. ;^)
So far I've downloaded HTC Sync and Minimal ADB/Fastboot. The phone is plugged-in and charging. So I plan to pick up on this tomorrow night. If I understand things:
Install the drivers
Connect the phone
Pray that it is still in USB Debugging mode
Verify ADB detects the phone
Use ADB to push my choice of ROMs to the root of the sdcard internal storage device
Go into TWRP
Wipe the entire phone including system
Install the ROM
Wave dead chicken over head while singing the theme song from Evita
Reboot when done
Is that right?
Or should I use flashboot (never have before)?
Does "*** UNLOCKED ***" on the bootloader screen mean the bootloader is unlocked (as opposed to carrier unlock)?
Should I update TWRP to 2.6 first? If so, can I just push with ADB and Install with TWRP 2.5??
Do I need to S-OFF to flash TWRP or ROM? If so, how?
What the heck is an RUU file and do I need one?
And finally for tonight, while I know there's no such thing as the "best" ROM, which ROMs should I look at if my priorities are stability, functionality and battery life (most to least important)? I tend to put a ROM on my phone and not change for months, even years.
Thanks in advance for any assistance.
http://forum.xda-developers.com/showthread.php?t=1671237
That will help you
Sent from my HTC One XL using xda premium
Adb won't work because that requires the ROM to be booted into an os. You don't need it yet anyhow. You will need fastboot though. You'll want to get rid of TWRP 2.5 because it's full of bugs. Here's how to install TWRP 2.6:
Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can enter recovery on your phone. Select mount from the menu, then mount usb storage while connected to a pc, it will now show up as a removable drive so you can copy a ROM to the device. For stability, stock ROMs are the best option, you'll find those here.
One you've downloaded a ROM, you need to extract the boot.img from the root of the zip and place it in your fastboot folder on your pc, we'll come back to that later. Now copy your entire ROM zip onto the phone. Enter recovery, do a full wipe (cache/dalvik cache/factory reset/system), go to install menu, install ROM.
Now, reboot to bootloader, connect to pc, make sure it shows fastboot usb on the screen. You now need to flash the boot.img because the phone is s-on. Do that by entering this command:
Code:
fastboot flash boot boot.img
Now you should be able to reboot the phone into the ROM.
Sent from my Evita
Thanks both Ken and Timaaa. You guys rock.
I'm leaning towards giving utkaar099's Stock/Deodexed JB 4.1.1 ROM and the HTC ATT 3.18 radio a try. I haven't figured S-OFF yet but once I get the ROM on and working I'm sure I'll figure it out.
I wanted to say thanks again for the help. The phone is now running again with the stock/deodexed JB 4.1.1.
I haven't tried flashing a radio file yet. I'm unclear if I have to S-OFF before flashing the radio. Still reading, but if you have a chance to answer this question I'd appreciate it.
S-off isn't required for flashing radios, you can just flash them in recovery. Just make sure you don't flash radio+RIL, or the cm radios, and you'll be fine.
Sent from my Evita
Thanks again timmaaa.
My pleasure :thumbup:
Sent from my HTC One XL using XDA Premium 4 mobile app
***TAMPERED****
****UNLOCKED****
Evita pvt ship s-on rl
hboot-2.14.0000
radio-0.24p.32.09.06
opendsp-v34.1.0.45.1219
emmc-boot
nov 26 2012, 18:37:14:206
fastboot is working... but fastboot usb stopped working...
i accidentally did a factory reset while trying to fix my error on flashing a custom rom. )':
You haven't described your full problem with anywhere near enough detail, so I'm gonna guess.
You've corrupted your sd card by doing the factory reset. Enter recovery and select mount, connect your phone to the pc, mount usb storage, format sd card to fat32 in Windows then you can copy a ROM across to flash. You're gonna need to work out why fastboot isn't working so you can flash the boot.img though because you're s-on.
Sent from my Evita
ive got fastboot usb working again. ill try what you mentioned. do you know the the recovery i need to flash?
Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you have TWRP recovery on your phone.
Sent from my Evita
sorry, i forgot to say i had TWRP working.
i just cant seem to get a rom working for the life of me.
Are you remembering to flash the boot.img via fastboot after installing the ROM?
Sent from my Evita
i flashed... screen just goes black after i reboot.
What ROM are you flashing?
Sent from my Evita
timmaaa said:
What ROM are you flashing?
Sent from my Evita
Click to expand...
Click to collapse
i was trying venom... someone directed me to this forum.
even though my device says envita... i couldve swore it was quad core with tegra 3. i cant look it up because og my situation though, i havent been able to boot up past recovery in hours.
If it says Evita it's definitely the dual core. You might have a bad download, have you checked the md5?
Sent from my Evita
timmaaa said:
If it says Evita it's definitely the dual core. You might have a bad download, have you checked the md5?
Sent from my Evita
Click to expand...
Click to collapse
im just looking for anything that will make it work again. i think i messed up trying the other forums ROMs. i gotta fix that kernel problem.
You need to make sure you only download ROMs from this forum, you're very lucky you didn't brick. Try one from here and make sure you flash the boot.img and it should work.
Sent from my Evita
im almost finished dowloading one now.
thanks for your help... i thought i was screwed.
I've looked everywhere for something like this, and so far no one has experienced this.
Okay, so check this out:
I've already rooted and S-Off and SuperCID and all of that, the works. Had ViperROM XL and everything. I got curious to try out KarbonRom 4.4, and tried to flash it in TWRP, didn't work obviously, blah blah blah, short story is, I RELOCKED and installed the AT&T 3.18 RUU. At that point, TAMPERED was gone, and I had RELOCKED there instead, S-Off and SuperCID persisted.
I used the WinDroid Toolkit to originally root and S-Off my Evita. I tried it again. I succeeded in unlocking the bootloader, no problems there. When I go to flash TWRP on it, it says it succeeds. Now, here's when things get weird: I go to push Superuser, and at first it gave me all kinds of hassle, saying the toolkit wasn't detecting my phone, to saying it failed and to try again in a few moments. It was only until I booted back to stock and tried pushing Superuser that it gave me a success message and began to reboot to recovery. It's here that the phone fails to do this, every time. The screen goes black, and when plugged into my PC a Found New Hardware message pops up, asking me to search for drivers for QHSUSB_DLOAD, or something or other. I'm like, "no, that's not right." So after figuring out the 2-button reset to go back to HBOOT, I try to manually boot into recovery; no dice. Same results. So basically, I cannot access any recovery. Furthermore, my HBOOT says UNLOCKED and S-Off and CID-11111111, but TAMPERED is MIA. Not sure if that has anything to do with this, but I certainly did not have this problem the first time I unlocked everything. For your information, I'm on 2.14 HBOOT, 3.18 RUU. Thanks for any points in the right direction.
First thing, you didn't need to relock your bootloader to run the RUU, having s-off means that isn't necessary. Secondly, ditch the toolkit, it's unnecessary and causing problems.
I think you're possibly a bit confused about what you need to be doing. If your end goal was to flash a KitKat ROM why were you attempting to root the stock ROM? The tampered flag is missing from your bootloader because you don't have a custom recovery installed. Exactly which version of TWRP did the toolkit say it was installing? Hopefully all you need to do is flash a working recovery, then you can flash a ROM.
Download the modified version of TWRP 2.6.3.0 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now hopefully you can enter recovery.
Sent from my Evita
timmaaa said:
First thing, you didn't need to relock your bootloader to run the RUU, having s-off means that isn't necessary. Secondly, ditch the toolkit, it's unnecessary and causing problems.
I think you're possibly a bit confused about what you need to be doing. If your end goal was to flash a KitKat ROM why were you attempting to root the stock ROM? The tampered flag is missing from your bootloader because you don't have a custom recovery installed. Exactly which version of TWRP did the toolkit say it was installing? Hopefully all you need to do is flash a working recovery, then you can flash a ROM.
Download the modified version of TWRP 2.6.3.0 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now hopefully you can enter recovery.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the swift reply, I'm gonna go ahead and give this a try. To answer your question, through trying to flash KarbonRom, I wiped and factory reset without backing anything up, silly, I know, but I live a little too dangerously I suppose. I tend to get to cocky with this stuff, through all the devices I've rooted and so on. After failing to flash it, I knew I was stuck, which is why I came to the conclusion the only way out was to revert to stock RUU. If there was anything else I could do, I wasn't thinking of it. In hindsight, I suppose I could have ADB Sideloaded Viper XL again. Also, I was unaware that I didn't need to relock the bootloader to install the stock RUU, this is news to me, so thank you for that. I'll reply again after trying your link.
EDIT: This worked, thank you again. You've made me wiser in the ways.
One thing I forgot to mention. The QHSUSB_DLOAD that your phone was showing up as when connected to your PC usually means that a device is bricked. So, under no circumstances should you use that toolkit ever again, because whatever it was doing wasn't good at all.
Sent from my Evita
timmaaa said:
One thing I forgot to mention. The QHSUSB_DLOAD that your phone was showing up as when connected to your PC usually means that a device is bricked. So, under no circumstances should you use that toolkit ever again, because whatever it was doing wasn't good at all.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the heads up, I'll keep it in mind. It seems the most reliable way to do this stuff is just do it yourself. I'm still green to the ways of adb and fastboot, I've always let one-clicks and toolkits do the work for me, but I'm learning that just doing it yourself is the most reliable method. Thanks again, man, your insight has always helped me out of tough situations.
Doing it yourself is definitely the most reliable method. It might seem daunting at first, but I can assure you it's totally simple, and once you've done it a couple times you'll see that. The manual way is the best way, hands down. A bonus is that it feels great to learn something and to have an extra bit if control over your device.
Sent from my Evita