Hi, i need your HELP with this problem, i have look around this forum looking for a solution about similar ISSUE and i haved done STEP by STEP the procedure and when done my HTC wont load THE RECOVERY. I have been reading solutions about 4 days ago..
THIS WHAT HAPPEND:I
I replaced the LCD Screen Display correctly and when i turn it on it went directly to the BOOTLODER, since then my Rezound its been booting with the white "HTC" screen for fews seconds then LOOP again. no recovery boot and niether OS
THIS WHAT I DID:
Hi, i need your HELP with this problem, i have look around this forum looking for a solution about similar ISSUE and i have done STEP by STEP the procedure and when done my HTC wont load THE RECOVERY. I have been reading solutions about 4 days ago...
THIS WHAT HAPPEND:
I replaced the LCD Screen Display correctly and when i turn it on it went directly to the BOOTLODER, since then my Rezound it’s been booting with the white "HTC" screen for few seconds then LOOP again. No recovery boot and neither OS
THIS WHAT I DID:
I download ruu, rom, and all recovery versions lists above and installed them correctly according the ADB SCREEN, but when I try to enter to recovery it stock in white screen logo HCT
MY REZOUND INFO:
TAMPERED
UNLOCKED
VIGOR PUT SHIP S-OM RL
HBOOT.2.28
RADIO 2.23.10.123R/2.23.10.0124R
INFOversion: 0.5
INFOversion-bootloader: 2.
INFOversion-baseband: 2.23
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 4.05.605
INFOserialno: HT1BJS214553
INFOimei: 990000339159446
INFOproduct: vigor
INFOplatform: HBOOT-8260
INFOmodelid: PH9810000
INFOcidnum: VZW__001
INFObattery-status: good
INFObattery-voltage: 3651m
INFOpartition-layout: Gene
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: c
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
RECOVERY INSTALLED AND NOT WORKED:
CWM-6.0.4.4-recovery
openrecovery-twrp-2.8.0.1F-vigor
recovery-clockwork-touch-6.0.3.1-vigor
recovery-ra-vigor-3.15-gnm
twrp-2.4.3.0-vigor
twrp-2.4.4.0-vigor
twrp-2.5.0.0-vigor
twrp-2.6.0.0-vigor ECT...
recovery-ra-vigor-3.14-gnm
I been doing this several times and different method as: rename recovery to PH98IMG.zip and installed from SD CARD, I been used ADB command "fastboot fast recovery recovery.img ect... all succeed but when calling the recovery partition it stuck.
ANY HELP about these issues i will appreciate it.
Hi, I'have same issue with my Rezound. Have you found a working solution
mofazar said:
Hi, I'have same issue with my Rezound. Have you found a working solution
Click to expand...
Click to collapse
What do you mean "same issue"? You replaced the screen and can't do anything now? That is the jist of what the OP said...
Are you locked, unlocked? S-on or S-off? Proper drivers loaded? Hboot loading and can you get a Fastboot response?
A little more detail would help here...
Sent from my MotoG3 using Tapatalk
i'have fastoot acces, device is recognized by PC and detected by fastboot prompt command
it's actually unlocked bootloader and s-on
i'have try to downgrade with unlocked and relocked bootloader but it's failed.
in unlocked the error is in : recovery partition update fail
in relocked : try with true update version.:crying::crying:
---------- Post added at 02:37 PM ---------- Previous post was at 02:32 PM ----------
Device is not rooted. i've try reflash many recovery, operating succefull but it can't boot into any recovery.
Can you boot recovery? Try
fastboot boot twrp.img
But replace "twrp.img" with the name of your recovery image file.
Please attach a screenshot or copy and paste terminal interactions.
Sent from my MotoG3 using Tapatalk
have you found a solution for this problem yet? i might be able to help. i know the rezound inside and out. i have replace the screen both speakers rooted downgraded upgraded flashed multiple roms used fastboot and adb options for sideloading and flashing.my device is s-on bootloader unlocked tampered and security warning. i would in ur situation is rom a stock ruu. one that matches ur hboot and raido. u r suppose to start the ruu from ur home screen with adb debugging on but since ur phone is boot looping i would try it starting off in fastboot usb. i have success starting it straight from there. the ruu installer will say rebooting phone to bootloader but it will be there already. should switch screens to a black background and with white htc logo and progress bar. remember to oem relock ur bootloader b4 starting the ruu. also all fastboot and adb should be installed on ur computer, along with htc drivers. all can be searched for on the forum. i searched minimal adb and fastboot.zip and htc drivers part1 and part2.zip. then make sure ur computer is seeing ur phone. i will reply asap but i is kinda busy. hope this helps if not i can help more.
dirtysan said:
have you found a solution for this problem yet? i might be able to help. i know the rezound inside and out. i have replace the screen both speakers rooted downgraded upgraded flashed multiple roms used fastboot and adb options for sideloading and flashing.my device is s-on bootloader unlocked tampered and security warning. i would in ur situation is rom a stock ruu. one that matches ur hboot and raido. u r suppose to start the ruu from ur home screen with adb debugging on but since ur phone is boot looping i would try it starting off in fastboot usb. i have success starting it straight from there. the ruu installer will say rebooting phone to bootloader but it will be there already. should switch screens to a black background and with white htc logo and progress bar. remember to oem relock ur bootloader b4 starting the ruu. also all fastboot and adb should be installed on ur computer, along with htc drivers. all can be searched for on the forum. i searched minimal adb and fastboot.zip and htc drivers part1 and part2.zip. then make sure ur computer is seeing ur phone. i will reply asap but i is kinda busy. hope this helps if not i can help more.
Click to expand...
Click to collapse
OP is S-on and no RUU exists for this software release... And with S-on no downgrade is possible. Although your points are mostly valid, if you had read the thread you know this had been covered.
Sent from my MotoG3 using Tapatalk
acejavelin said:
OP is S-on and no RUU exists for this software release... And with S-on no downgrade is possible. Although your points are mostly valid, if you had read the thread you know this had been covered.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
i was basically stating that a fresh start is always better. when something goes wrong i always resort back to stock. unlock bootloader root then flash custom rom. but thanks for the condescending attitude brah
dirtysan said:
i was basically stating that a fresh start is always better. when something goes wrong i always resort back to stock. unlock bootloader root then flash custom rom. but thanks for the condescending attitude brah
Click to expand...
Click to collapse
My intent was not to be condescending, in fact out most of your points were completely valid. My point was at that software release there is no RUU, thus no way to go back to a "known good" configuration... Sorry if I offended you, that wasn't my intent.
Sent from my MotoG3 using Tapatalk
acejavelin said:
My intent was not to be condescending, in fact out most of your points were completely valid. My point was at that software release there is no RUU, thus no way to go back to a "known good" configuration... Sorry if I offended you, that wasn't my intent.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
have u tried installing recovery with an adb push. if u have not tried already use windroid universal toolkit.
akura3 said:
Hi, i need your HELP with this problem, i have look around this forum looking for a solution about similar ISSUE and i haved done STEP by STEP the procedure and when done my HTC wont load THE RECOVERY. I have been reading solutions about 4 days ago..
THIS WHAT HAPPEND:I
I replaced the LCD Screen Display correctly and when i turn it on it went directly to the BOOTLODER, since then my Rezound its been booting with the white "HTC" screen for fews seconds then LOOP again. no recovery boot and niether OS
THIS WHAT I DID:
Hi, i need your HELP with this problem, i have look around this forum looking for a solution about similar ISSUE and i have done STEP by STEP the procedure and when done my HTC wont load THE RECOVERY. I have been reading solutions about 4 days ago...
THIS WHAT HAPPEND:
I replaced the LCD Screen Display correctly and when i turn it on it went directly to the BOOTLODER, since then my Rezound it’s been booting with the white "HTC" screen for few seconds then LOOP again. No recovery boot and neither OS
THIS WHAT I DID:
I download ruu, rom, and all recovery versions lists above and installed them correctly according the ADB SCREEN, but when I try to enter to recovery it stock in white screen logo HCT
MY REZOUND INFO:
TAMPERED
UNLOCKED
VIGOR PUT SHIP S-OM RL
HBOOT.2.28
RADIO 2.23.10.123R/2.23.10.0124R
INFOversion: 0.5
INFOversion-bootloader: 2.
INFOversion-baseband: 2.23
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 4.05.605
INFOserialno: HT1BJS214553
INFOimei: 990000339159446
INFOproduct: vigor
INFOplatform: HBOOT-8260
INFOmodelid: PH9810000
INFOcidnum: VZW__001
INFObattery-status: good
INFObattery-voltage: 3651m
INFOpartition-layout: Gene
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: c
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
RECOVERY INSTALLED AND NOT WORKED:
CWM-6.0.4.4-recovery
openrecovery-twrp-2.8.0.1F-vigor
recovery-clockwork-touch-6.0.3.1-vigor
recovery-ra-vigor-3.15-gnm
twrp-2.4.3.0-vigor
twrp-2.4.4.0-vigor
twrp-2.5.0.0-vigor
twrp-2.6.0.0-vigor ECT...
recovery-ra-vigor-3.14-gnm
I been doing this several times and different method as: rename recovery to PH98IMG.zip and installed from SD CARD, I been used ADB command "fastboot fast recovery recovery.img ect... all succeed but when calling the recovery partition it stuck.
ANY HELP about these issues i will appreciate it.
Click to expand...
Click to collapse
i have same specs on my phone s-on hboot ect... try this ruu
http://forum.xda-developers.com/showthread.php?t=2094412
after that use windroid universal toolkit for rooting and recovery flash. if u saved ur token u can just skip using windroid for root and just use it for twrp recovery. just flash ur token from fastboot.
Related
Guys, I can really use some help here.
I upgraded my Flyer to the first Honeycomb leak (I don't remember the exact upgrade procedure I used) and now I want to update to the latest official release.
Tried the simple downgrade guide with no luck, running RUU's give me image errors or even a crashed flyer (distorted screen). Putting the ROM as a zip on the SD card gives me the "Main version is older" error. Tried flashing HBOOTS, ROMs and Recoveries through fastboot, all fail with error "signature verification fail".
I currently have a flyer that only boots to the bootloader and I only have access to it using fastboot. Booting recovery brings me back to the bootloader.
The bootloader shows:
Code:
*** RELOCKED ***
FLYER PVT SHIP S-ON RL
HBOOT-1.11.0006
Fastboot getvar all:
Code:
INFOversion: 0.5
INFOversion-bootloader: 1.11.0006
INFOversion-baseband: 3821.08.00.26_M
INFOversion-cpld: None
INFOversion-microp: 0950
INFOversion-main: 3.10.405.1
INFOserialno: HT159T401521
INFOimei: 354672040168047
INFOproduct: flyer
INFOplatform: HBOOT-7230
INFOmodelid: PG4110000
INFOcidnum: HTC__E11
INFObattery-status: good
INFObattery-voltage: 3972mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 60a0efb2
INFOhbootpreupdate: 12
INFOgencheckpt: 0
I'm out of idea's on what to do, all suggestion are appreciated!
To get up and running unlock boot loader again using htcdev unlock, then flash recovery in fastboot and then you can load a rom like lee droid
Sent from my HTC Flyer P510e using xda premium
Search for globatrons thread for reverting to gb. He has a fix for misc older version
Sent from my HTC Flyer P510e using xda premium
mcord11758 said:
Search for globatrons thread for reverting to gb. He has a fix for misc older version
Sent from my HTC Flyer P510e using xda premium
Click to expand...
Click to collapse
I can't boot to recovery or Android, so I don't have access to ADB to push the misc_version file.
Bluediss said:
I can't boot to recovery or Android, so I don't have access to ADB to push the misc_version file.
Click to expand...
Click to collapse
See my first post
mcord11758 said:
To get up and running unlock boot loader again using htcdev unlock, then flash recovery in fastboot and then you can load a rom like lee droid
Sent from my HTC Flyer P510e using xda premium
Click to expand...
Click to collapse
I do feel stupid now... I already tried the HTCDEV unlock a few times, but that gave me errors... Doing it again now I discovered I was doing it wrong... I included the "INFO" string that every line starts with... Argh.
I'll flash the unlock.bin later this evening.
mcord11758 said:
To get up and running unlock boot loader again using htcdev unlock, then flash recovery in fastboot and then you can load a rom like lee droid
Sent from my HTC Flyer P510e using xda premium
Click to expand...
Click to collapse
And I was indeed going for LeeDroid!
The unlock was succesfull, but it took me some time to get a working recovery. I finally got recovery working with the recovery image from Globatron's "HC-3G-light.zip".
I'm flashing the GB RUU now, let's wait and see.
Everything working now. All came down to me xopy/pasting a bit to much "INFO" for the HTC Unlock.
Thanks for the help!
Sent from my Galaxy Nexus using xda premium
I'm stuck too, but running into the htcdev s-off bug
I pushed my unlock bin to my flyer, but I can't "continue" past selecting "Yes" in the official bootloader unlock step. I've searched the web, but no answers as to why.
I can't boot into android to run adb, and have no recovery. only fastboot. any ideas?
malaise76 said:
I pushed my unlock bin to my flyer, but I can't "continue" past selecting "Yes" in the official bootloader unlock step. I've searched the web, but no answers as to why.
I can't boot into android to run adb, and have no recovery. only fastboot. any ideas?
Click to expand...
Click to collapse
Are you using the H/W buttons (volume up/down and power button for "Continue")
I just bought this flyer 3G version It was working with 2.3.4 when i bought it.
I've searched the entire XDA forum ,modaco and loads of the other sites. Been attempting this for 4 hours straight x 3nights in a row.
I've managed to get Bootloader unlock via HTCdev but still on S-ON because my hboot is 1.11.011 Flashed the Paul obriens modified HC boot 11.11.0011 image. I got revolution CWM and i can get into it but now suddenly fail to adb into it.
FLYER PVT SHI{P
S-ON RL
HBOOT - 1.11.0011
MICROP=0950
RADIO-3822.10.08.07_M
eMMC-boot Oct 25 2011,16:55:07
I think my flyer is in limbo.
CID=044 which is the HTC Asia WWE one.
I tried: Installing some custom ROM's as soon as i achieved bootloader unlocked. Tried the latest LOeeDroid etc. BUT they all fail at the HTC boot screen. Even after waiting for 10 mins. Yes I did extract the boot.img and flashed via fastboot due to s-on but still stuck at HTC boot logo.
Ran the RUU's directly from fastboot mode (i just double clicked on the exe from my PC) -HTC Asia WWE . but they all fail on installtion/ signature. RUU_Flyer_hTC_Asia_WWE_1.48.707.4_Radio_20.3501.30 .089BU_3809.05.04.10_M_release_193927_signed RUU_Flyer_hTC_Asia_WWE_2.27.707.1_Radio_20.3504.30 .089BU_3809.07.04.06_M_release_204905_signed RUU_Flyer_hTC_Asia_WWE_2.27.707.2_Radio_20.3504.30 .089BU_3809.07.04.06_M_release_219276_signed
i tried the rom.zip extraction and renamed it to PG411MG.zip with the hope of the bootloader detecting and running it - it tried to install but failed -signature. I created a goldcard but not used this method yet as i had to format it and now i cant even connect to the PC -its as if it cant detect the device. I will try a ROM that is similar to my radio . But i cant connect to the Flyer -(adb- device not found)
Please help - ill gladly donate to a working solution. I dont know what else to do. I just want to get android working again passing the horrid HTC boot logo. i dont mind stock etc just need my flyer to work.
Been ROMing since HD2
UPDATE: SOLVED
none of the stock RUU I tried installing was successful because I had Unlocked the Bootloader.
All I needed to do was' fastboot oem lock' and it relocked. RUU will only install on locked bootloaders.
While still in fastboot I ran the RUU from my PC and it worked. Installing while tears of joy rolled down my tired eyes.
So I'm now on an older hboot and achieved S-off,rooted and made my flyer into a phone + Bluetooth.
Flash the stock rom
Get a guide on xda about it... Urs any flashing software and u will b alr9
Click THANKS button if I helped, or u liked my post.
Will be honored.
Hi, i think this problem may deserve a new thread, please forgive me if this has been solved somewhere else but nowhere have I found a problem like mine
On my journey ttrying to root and s-off and unlock, this is what i discovered:
fastboot oem writesecureflag 3 restores s-on
s-on is required for unlocking bootloader, s-off will go to disclaimer screen but wont respond if yes is selected, it will only say ***unlock*** (which it must, but it wont be truly unlocked, your phone needs to respond when selecting yes and MUST restart, if you need to remove battery, it wont be unlocked.
***Problem***: now I had s-off and ***LOCKED*** so I ran fastboot oem writesecureflag 3 to get s-on, unlocked through htcdev and heres the big problem:
Now:
***UNLOCKED***
HBOOT 1.49.0007 S-ON (RH - i think)
Cant change CID, flash recovery, doesnt read PG86IMG files, cant flash anything through fastboot, cant run RUU because of error 132 (signature error).
After trying to change CID with:
fastboot oem writecid HTC__621
Result =
gave a few errors
cidnum = 0202 ...???
Have hboot 1.49.0007, can unlock relock bootloader, have functioning ICS rom
fastboot getvar all
< waiting for device >
INFOversion: 0.5
INFOversion-bootloader: 1.49.0007
INFOversion-baseband: N/A
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 1.20.401.2
INFOserialno: HT23NV200556
INFOimei: 352647050653635
INFOproduct: shooter_u
INFOplatform: HBOOT-8260
INFOmodelid: PG863****
INFOcidnum: HTC__621
INFObattery-status: good
INFObattery-voltage: 5785mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: edba812f
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.510s
so please help... any1...
cybergurken said:
Hi, i think this problem may deserve a new thread, please forgive me if this has been solved somewhere else but nowhere have I found a problem like mine
On my journey ttrying to root and s-off and unlock, this is what i discovered:
fastboot oem writesecureflag 3 restores s-on
Click to expand...
Click to collapse
You should not have done that.
Also, if you are S-Off that is really all that matters. There is not really any reason to unlock the Bootloader. If you were S-Off and wanted to have an unlocked bootloader you should have just found a hboot like the revolutionary one or engineering and flashed PG86IMG.zip and that would have given you Unlocked and S-Off.
For the most part, you never want to do the fastboot oem writesecureflag 3.
When it does not respond to yes while unlocking and you have to pull the battery, it gets unlocked like it would when it responds to yes. Don't think what you assume is right, like you did. You should test it before making any assumption.
No offense, but friend from all your posts I think you are totally confused about all the stuff with hboots, unlocking, recovery, s-off/on.
EDIT : I see you edited it yourself.
Thnx 4 responding
mnomaanw said:
When it does not respond to yes while unlocking and you have to pull the battery, it gets unlocked like it would when it responds to yes. Don't think what you assume is right, like you did. You should test it before making any assumption.
No offense, but friend from all your posts I think you are totally confused about all the stuff with hboots, unlocking, recovery, s-off/on.
EDIT : I see you edited it yourself.
Click to expand...
Click to collapse
Hi, no offence taken...
However, Im still a newbie @ all of this, however, I might be wrong but 3 q's
1. Why would it hang on the "yes" option
2. If I pull out baattery, it says ***unlocked*** but I have no access to recovery, even after custom recovery flash in fastboot, it cant/wont/doesnt boot into recvoery @ all, ref. "my other posts", why would that happen
3. What is the real difference between unlocking bootloader, and s-oof, I have read many posts and I figured getting both would be on the safe side...
and lastly, xd, why would a bootloader not read/detect a PG86IMG file, that is also another problem,
Once again, tnks very much
Here's my problem, I've tried everything that I can find, and everything I can think of.
My Info:
***Tampered***
***Unlocked***
Jewel PVT SHIP S-ON RL <<<----That crap is my problem.
HBOOT-2.09.000
Radio- 1.12.11.1210
OpenDSP-v31.1.0.45.0815
eMMC-boot
Oct 18 2012, 15:46:20
I'm on Meanbean 3.09 Android v. 4.1.1 with 3.16.651.3. (More specifically 3.16.651.3 CL147243) as you can see, I'm still S-On though.
Can't flash any other rom, assuming it has to do with S-On. So what i'm trying to do is either RUU back to 3.15 or gain S-Off where i am now. My real problem comes when I boot into bootloader (it automattically goes into fastboot after bootloader loads is that normal?) and once i'm in Fastboot USB all I get from any way i've tried is [waiting for device...] no matter which method i try. I can reboot to bootloader from CMD prompt but once it's there I've got nothing. Sorry for the kind of scatter brained post but i'm all over the place ripping my hair out trying to fix this.
Thanks.
Patt
Use Moonshine to s-off
bigdaddy619 said:
Use Moonshine to s-off
Click to expand...
Click to collapse
Tried that, boots into Bootloader then get stuck on [waiting for Fastboot x/120] and counts to 120 then fails
Every program reboots into bootloader fine, then cant find the device one in fastboot.. I have all the ADB files, can control everything up until then from CMD
Phutt89 said:
Every program reboots into bootloader fine, then cant find the device one in fastboot.. I have all the ADB files, can control everything up until then from CMD
Click to expand...
Click to collapse
Are the drivers installed correctly? Sounds like a driver issue to me.
Do you get an answer when you type fastboot devices?
bigdaddy619 said:
Are the drivers installed correctly? Sounds like a driver issue to me.
Do you get an answer when you type fastboot devices?
Click to expand...
Click to collapse
I had all the drivers installed previously from when I originally rooted my phone, and then I used Windroid toolbox to install them again to make sure, Windroid even recognized that they were all installed and asked if I wanted to "repair" or "remove" them
Mother Eff Me, It's the whole stupid Windows 8 thing, Just ran it on my Girlfriends computer, and it's working fine. I hate this thing, Thanks guys, I appreciate the help!
FOR FUTURE NOTICE TO ANYONE ELSE HAVING MY PROBLEM HERE ARE MY SYMPTOMS USING WINDOWS 8
*Can boot into Bootloader from CMD while device is in sense more
*Once in bootloader then to Fastboot USB (You can hear the "Connecting sound") the device can not be recognized
ie: ;[Waiting for device] [error: no device found]
Stop what you are doing and get a machine with windows 7/Vista/XP or get a machine with Linux.
So I'm trying to flash the 1.58.502.1 RUU but I am s-on with an unlocked bootloader. And from the sound of things the only way to relock the bootloader is by going s-off which I don't want to pay $25 to do.
My current software is 1.12.502.8 but the current baseband matches up with the baseband from 1.58.502.1 (1.16.21331931. LA11G_20.31A.4145.02L). Are there any work arounds that you guys can think of, can I just flash the RUU since the basebands match up?
From what I've read it seems you do in fact need to S-OFF to relock the bootlooader.
Here's the thing,if you S-OFF than you won't need to relock the bootlooader to achieve what your looking to do .S-OFF enables you to flash all sorts of variations assuming they are for your specific device.
I will tell you that the $25 spent to have a safe hassle free S-OFF exploit is worth every cent.
You do not need to s-off to relock the bootloader.
"fastboot oem lock" from adb command prompt connection, while in fastboot mode is all you need to do.
Put your recovery back to stock first for safety but RUU should do that for you, better safe than sorry though...
- Sent from a payphone ...
Iconic24 said:
So I'm trying to flash the 1.58.502.1 RUU but I am s-on with an unlocked bootloader. And from the sound of things the only way to relock the bootloader is by going s-off
Click to expand...
Click to collapse
I don't know where you guys are getting this from. S-off is in no way required to relock the bootloader.
Further, s-off is not required to run an RUU (another common misconception, that I don't know where people get); unless you are trying to "break the rules" and either run an older RUU ("downgrade") or run another carrier's RUU.
Iconic24 said:
My current software is 1.12.502.8 but the current baseband matches up with the baseband from 1.58.502.1 (1.16.21331931. LA11G_20.31A.4145.02L). Are there any work arounds that you guys can think of, can I just flash the RUU since the basebands match up?
Click to expand...
Click to collapse
As long as you are using an AT&T RUU, you can run an RUU for any version number that is equal to or greater than the main version on the phone. The only thing you can't do is run an older RUU ("downgrade") with s-on.
But since you are on the oldest AT&T version (1.12) and there is no 1.12 RUU anyway; you can therefore run any AT&T RUU. This includes 1.58, 2.23, and any new RUUs that come in the future.
ruu
Oh my, I know this is necro thread but it is the closest to what I am trying to achieve and google search led me to it. So if I am on SkyDragon GPE 4.4.4 flashed on top of Stock Sense 4.4.2, hboot 3.16, tampered, unlocked, rooted, s-on there is no problem for me to go RUU and update to 5.x.x? However, shall I use RUU for 4.4.4 or 4.4..2? Thanks if anyone replies
?
i am thinking of just using a toolkit to root and unlock the bootloader but before i do that i gotta ask is it worth it ?
xCellHD said:
i am thinking of just using a toolkit to root and unlock the bootloader but before i do that i gotta ask is it worth it ?
Click to expand...
Click to collapse
Is it worth it to unlock the bootloader? That question is impossible to answer without knowing your individual desires, preferences and what you want from the device.
I gave an answer to a similar question a few days ago: http://forum.xda-developers.com/htc-one-m8/help/to-root-to-root-t3102598
If you are asking "is using a toolkit worthwhile"; I would say NO. The toolkits are not up to date, and therefore install obsolete versions of TWRP (which causes issues) and I personally recommend to do the steps "manually" as its not very hard, ande also a good learning experience that will yield better results.
My personal opinion, ditch the toolkits.
---------- Post added at 10:28 AM ---------- Previous post was at 10:22 AM ----------
innocencex said:
Oh my, I know this is necro thread but it is the closest to what I am trying to achieve and google search led me to it. So if I am on SkyDragon GPE 4.4.4 flashed on top of Stock Sense 4.4.2, hboot 3.16, tampered, unlocked, rooted, s-on there is no problem for me to go RUU and update to 5.x.x?
Click to expand...
Click to collapse
It sounds like you just flashed the GPE ROM, and did not "fully convert" to GPE with the RUU. You can confirm this by booting into hboot, if the hboot screen is white, its still the Sense hboot. GPE hboot is black.
Assuming you just flashed a GPE ROM, you can just RUU to current Sense RUU (5.0). You will need to relock the bootloader to RUU, since you are s-on.
innocencex said:
shall I use RUU for 4.4.4 or 4.4..2?
Click to expand...
Click to collapse
Just run the 5.0 RUU. No need to run intermediate RUUs or run them sequentially. OTAs need to be installed in sequence. RUUs do not.
redpoint73 said:
Is it worth it to unlock the bootloader? That question is impossible to answer without knowing your individual desires, preferences and what you want from the device.
I gave an answer to a similar question a few days ago: http://forum.xda-developers.com/htc-one-m8/help/to-root-to-root-t3102598
If you are asking "is using a toolkit worthwhile"; I would say NO. The toolkits are not up to date, and therefore install obsolete versions of TWRP (which causes issues) and I personally recommend to do the steps "manually" as its not very hard, ande also a good learning experience that will yield better results.
My personal opinion, ditch the toolkits.
---------- Post added at 10:28 AM ---------- Previous post was at 10:22 AM ----------
It sounds like you just flashed the GPE ROM, and did not "fully convert" to GPE with the RUU. You can confirm this by booting into hboot, if the hboot screen is white, its still the Sense hboot. GPE hboot is black.
Assuming you just flashed a GPE ROM, you can just RUU to current Sense RUU (5.0). You will need to relock the bootloader to RUU, since you are s-on.
Just run the 5.0 RUU. No need to run intermediate RUUs or run them sequentially. OTAs need to be installed in sequence. RUUs do not.
Click to expand...
Click to collapse
Sir I'm using GPe ROM to my HTC m8..it's S-ON "Unlocked" I can't unlock my bootloader.
Prvrt said:
Sir I'm using GPe ROM to my HTC m8..it's S-ON "Unlocked" I can't unlock my bootloader.
Click to expand...
Click to collapse
If it says UNLOCKED in bootloader, that means the bootloader is already unlocked.
Or are you trying to relock your bootloader?
It's not clear exactly what you are trying to do, or what steps you've already taken. I know you're new to the forum, so please try to provide as much detail as possible when asking for help. If youknow how, do fastboot getvar all, and post the result (delete IMEI and serial number before posting).
redpoint73 said:
If it says UNLOCKED in bootloader, that means the bootloader is already unlocked.
Or are you trying to relock your bootloader?
It's not clear exactly what you are trying to do, or what steps you've already taken. I know you're new to the forum, so please try to provide as much detail as possible when asking for help. If youknow how, do fastboot getvar all, and post the result (delete IMEI and serial number before posting).
Click to expand...
Click to collapse
Im trying to root my phone again and unlock the bootloader..but i cant access when my phone is in Hboot my phone cant read on my laptop..and after i open it connect but my USB debugging is in "charging only" and i put it back again in MTP and after i put it in Hboot it disconnect again.. idont know if my laptop or my debugging mode
Prvrt said:
Im trying to root my phone again and unlock the bootloader..but i cant access when my phone is in Hboot my phone cant read on my laptop..and after i open it connect but my USB debugging is in "charging only" and i put it back again in MTP and after i put it in Hboot it disconnect again.. idont know if my laptop or my debugging mode
Click to expand...
Click to collapse
You do not need to unlock the bootloader if it says "UNLOCKED" near the top of the screen in bootloader. This specifically means the bootloader is already unlocked.
However, you will (somewhat obviously) need fastboot working if you want to flash TWRP via fastboot. There other means to install TWRP, since you also have working OS (TWRP app for instance). However, working fastboot is really valuable (possibly even critical in some situations) when modding the phone, so my recommendation would be to troubleshoot the problem, and have fastboot working (even despite the existence of "workaround" methods to install TWRP).
You actually do not need debugging enabled to use fastboot (only for adb, which is related to fastboot by there are distinct differences - so try to keep that in mind). Although having debugging enabled would not hurt anything (and obviously you will need it, if you want to use adb).
Another thing to note, the MTP connection mode selected in OS (charge only, file transfer, etc.) has not bearing once you are no longer in OS (when in bootloader) and fastboot will work regardless of whether there is even a working OS.
Fastboot connectivity issues are most usually on the PC side. Try a different USB port, different cable, re-install HTC Sync and HTC drivers. You can also try going into Windows Device Manager, finding the phone, then pick the option to manually select drivers, and select the "generic" Android MTP drivers. I often have to do this to make my PC "see" the M8 on fastboot/adb.
redpoint73 said:
You do not need to unlock the bootloader if it says "UNLOCKED" near the top of the screen in bootloader. This specifically means the bootloader is already unlocked.
However, you will (somewhat obviously) need fastboot working if you want to flash TWRP via fastboot. There other means to install TWRP, since you also have working OS (TWRP app for instance). However, working fastboot is really valuable (possibly even critical in some situations) when modding the phone, so my recommendation would be to troubleshoot the problem, and have fastboot working (even despite the existence of "workaround" methods to install TWRP).
You actually do not need debugging enabled to use fastboot (only for adb, which is related to fastboot by there are distinct differences - so try to keep that in mind). Although having debugging enabled would not hurt anything (and obviously you will need it, if you want to use adb).
Another thing to note, the MTP connection mode selected in OS (charge only, file transfer, etc.) has not bearing once you are no longer in OS (when in bootloader) and fastboot will work regardless of whether there is even a working OS.
Fastboot connectivity issues are most usually on the PC side. Try a different USB port, different cable, re-install HTC Sync and HTC drivers. You can also try going into Windows Device Manager, finding the phone, then pick the option to manually select drivers, and select the "generic" Android MTP drivers. I often have to do this to make my PC "see" the M8 on fastboot/adb.
Click to expand...
Click to collapse
I try on cmd my phone response. I type unlocktoken it works and after I type unlock code bin it success too but my phone didn't show the logo of unlock code and didn't reboot. But in my cmd it says successfully
Prvrt said:
I try on cmd my phone response. I type unlocktoken it works and after I type unlock code bin it success too but my phone didn't show the logo of unlock code and didn't reboot. But in my cmd it says successfully
Click to expand...
Click to collapse
You previously indicated UNLOCKED. Does it say UNLOCKED near the top of the bootloader screen?
Also, please refrain from quoting my whole entire post; as it clutters up the thread. I know it's the default when responding. But just leave in what is directly relevant to your response, and delete the rest.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.20.502.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT45SWM06618
(bootloader) imei: XXXXXXXXXXXXXXX ( Deleted)
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.125s
Bootloader - Unlocked
Recovery - TWRP
Rooted - Yes
Custom ROM - Resurrection Remis 5.8.5 Final
if want to go back to stock what is procedure
i have below RUU
RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502. 5_combined.exe
can i run this exe after relock the bootloader?
hotspot problem
i'm using htc one m9 at&t in india. i'm unable to turn on hotspot or bluetooth tethering. i heard a solution that i need to unlock bootloader and install cutome rom or edit some line in sql editor. so my question which is the safest method? could anyone please tell me the answer:crying:
Ashok_gajjala said:
i'm using htc one m9 at&t in india. i'm unable to turn on hotspot or bluetooth tethering. i heard a solution that i need to unlock bootloader and install cutome rom or edit some line in sql editor. so my question which is the safest method? could anyone please tell me the answer:crying:
Click to expand...
Click to collapse
This forum section is for the M8, not the M9. Anything we say here about the M8, may or may not be correct for the M9.
have a simple question I'm on firmware 3.16.617.2 there is update 3.16.617.3 if I am s-on unlocked Bootloader and attempt to flash RUU advance to 3.16.617.3 from earlier .2 will this relock my Bootloader ? as I don't want to relock it again my goal is to stall unlocked S-on .