Ok so now i have a Rooted r800i (locked bootloader) on 2.3.3, zergRush method.
On 02 UK, bought it from 02...
so basically it's locked to 02 atm.
I have everything ready to go for the unlocking the bootloader process.. but when i attempt to put my Play in fastboot mode... it just goes to charging signal (the LED won't go blue).
Where do i go from here? :S
I basically just want CM7 and CWM.
Also
will i lose my current rom/data/apps ? (i know i will lose it when installing CM7) but i mean will i have the option to back it up before losing it?
you can't do much with a locked bootloader.
thought i knew how to unlock the bootloader now... i'm not so sure lol.
You must pay to unlock
Sent from my rooted R800a 2.3.3 BL locked
i read somewhere that if you cant get the blue light (fastboot) on 2.3.4, you have to downgrade to the oldest firmware & it will work, so i can unlock bootloader, is this true? :S
Not sure where you read that but it's not true at all check the service menu and it will say whether or not you can unlock the bootloader
Sent from my R800i using XDA App
AwaisKhan said:
i read somewhere that if you cant get the blue light (fastboot) on 2.3.4, you have to downgrade to the oldest firmware & it will work, so i can unlock bootloader, is this true? :S
Click to expand...
Click to collapse
you don't need to downgrade the firmware at all, just the fastboot thing on your phone and commands from a computer
Hi all,
I've just got my one x yesterday and about to flash android hd from mike. However i encounter some problem when proceeding on firmware upgrade.
My phone is still on 1.26 and i am trying to flash the pj46img.zip. bootloader has already been unlocked
1. I placed the pj46img on the root of SD, however when i boot into bootloader it is not going to search for the update, which looks abnormal (i previously owned a desire z and to my understanding it will search for the img.zip files before it let me netvigates the menu to fastboot/recovery. That's not my case on one x)
2. i checked my cid is showing "none" which i understand this is normal since i have unlocked via htcdev.com. I tried to relock my bootloader in order to get official ota flashed. However when i type "fastboot oem relock" it will show (bootloader) lock successfully following with "fail (read content is too long)"
And on hboot screen it is showing "relocked **security warning**" and i was not able to get to cwm thus can't flash in recovery as well.
It would be highly appreciated if someone can provide some checking or solution. Let me know if you need my clarification (sorry for poor english). At the moment i am sticking with leedroid
Thanks all in advance
Sent from my HTC One X using XDA
kahei036 said:
Hi all,
I've just got my one x yesterday and about to flash android hd from mike. However i encounter some problem when proceeding on firmware upgrade.
My phone is still on 1.26 and i am trying to flash the pj46img.zip. bootloader has already been unlocked
1. I placed the pj46img on the root of SD, however when i boot into bootloader it is not going to search for the update, which looks abnormal (i previously owned a desire z and to my understanding it will search for the img.zip files before it let me netvigates the menu to fastboot/recovery. That's not my case on one x)
2. i checked my cid is showing "none" which i understand this is normal since i have unlocked via htcdev.com. I tried to relock my bootloader in order to get official ota flashed. However when i type "fastboot oem relock" it will show (bootloader) lock successfully following with "fail (read content is too long)"
And on hboot screen it is showing "relocked **security warning**" and i was not able to get to cwm thus can't flash in recovery as well.
It would be highly appreciated if someone can provide some checking or solution. Let me know if you need my clarification (sorry for poor english). At the moment i am sticking with leedroid
Thanks all in advance
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
Go back and unlock it again then flash CWM and superuser.
Flash a stock rom or a backup if you did any?
After flashing the stock 1.26xx you will automatically have the update pop up, download and install.
This is what I did anyways. The bootloader can be unlocked and update official anyways.
And also I think you were suppose to type 'fastboot oem lock' not relock.
Hope this helps!
Cheers!
I'm trying this too....
Last night I tried to flash my stock ROM (O2 UK branded) - but downloaded the wrong RUU. So I couldn't flash a completely stock ROM.
I ended up putting Mike's stock ROM on, and tried to flash update.zip via CWM - but got errors.
I am presuming this is because it's not a completely stock ROM, flashed via RUU??
I have now got the correct RUU for my handset, so I am going to try both using PJ46IMG method - and update.zip via CWM
One thing - I am currently running Insert Coin 3.2.0 (which is 1.28 base), do I have to step down to a 1.26 ROM before flashing back the stock recovery, and re-locking bootloader, then running 1.26 RUU?
Or can I just go straight to flashing back stock recovery & re-locking bootloader, then flashing stock RUU?
kahei036 said:
Hi all,
I've just got my one x yesterday and about to flash android hd from mike. However i encounter some problem when proceeding on firmware upgrade.
My phone is still on 1.26 and i am trying to flash the pj46img.zip. bootloader has already been unlocked
1. I placed the pj46img on the root of SD, however when i boot into bootloader it is not going to search for the update, which looks abnormal (i previously owned a desire z and to my understanding it will search for the img.zip files before it let me netvigates the menu to fastboot/recovery. That's not my case on one x)
2. i checked my cid is showing "none" which i understand this is normal since i have unlocked via htcdev.com. I tried to relock my bootloader in order to get official ota flashed. However when i type "fastboot oem relock" it will show (bootloader) lock successfully following with "fail (read content is too long)"
And on hboot screen it is showing "relocked **security warning**" and i was not able to get to cwm thus can't flash in recovery as well.
It would be highly appreciated if someone can provide some checking or solution. Let me know if you need my clarification (sorry for poor english). At the moment i am sticking with leedroid
Thanks all in advance
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
How did you get on with the flashing img.zip? I seem to be stuck with it not flashing either
I successfully rooted my Wildfire S 510e but still with S-On and then installed Cyanogen Mod7; I subsequently needed to get the network unlocked so I got the appropriate SIM unlock code and that works. However, every time the phone is rebooted I have to re-enter the SIM unlock code which is annoying. So I looked around and other users suggested I reinstall the stock Gingerbread ROM. I followed the instructions which included relocking the bootloader and then running an RUU.
The bootlocker worked but the RUU failed although the phone still works OK but when I select the Recovery option there's no menu just a red triangle; if I then hold the volume up key and the start button a restricted menu is displayed e.g. install a zip file option is not available.
I've tried the HTCdev Unlock Bootloader but that fails because the Cyanogen ROM doesn't match the expected stock ROM in the RUU.
Questions:
1. Is there a way to unlock the bootloader with Cyanogen Mod7 installed?
2. Can I get the full Recovery menu reinstalled?
Any other tips appreciated.
Thanks
Marnhullman said:
I successfully rooted my Wildfire S 510e but still with S-On and then installed Cyanogen Mod7; I subsequently needed to get the network unlocked so I got the appropriate SIM unlock code and that works. However, every time the phone is rebooted I have to re-enter the SIM unlock code which is annoying. So I looked around and other users suggested I reinstall the stock Gingerbread ROM. I followed the instructions which included relocking the bootloader and then running an RUU.
The bootlocker worked but the RUU failed although the phone still works OK but when I select the Recovery option there's no menu just a red triangle; if I then hold the volume up key and the start button a restricted menu is displayed e.g. install a zip file option is not available.
I've tried the HTCdev Unlock Bootloader but that fails because the Cyanogen ROM doesn't match the expected stock ROM in the RUU.
Questions:
1. Is there a way to unlock the bootloader with Cyanogen Mod7 installed?
2. Can I get the full Recovery menu reinstalled?
Any other tips appreciated.
Thanks
Click to expand...
Click to collapse
If you have installed cyanogenmod 7, then you have probably unlocked the bootloader and installed the recovery.............if the recovery doesn't show up, try flashing it again via fastboot
And NO, I won't tell you how to because there are countless threads on this all over the forum
Hi guys,
Got a phone a need to revive. I received unusable. Mother gave it to my sisters friend and she said it doesnt work. I now see why cause he was trying to mod it.
I managed to once get into TWRP but cant anymore. It was UNLOCKED but now RELOCKED which I possibly made it a little harder for me.
So currently "fastboot getvars" reports back all the info. It's showing version-main 6.13.206.5 and I just want official O2 stock so can use the phone. Ideally sim unlocked but could hassle O2 for that later since it was my mother's contract.
Basically just want to get a working recovery image on and then flash stock. CID is 02__001
Any suggestion to revive this welcomed, please.
So it still have twrp on it ? If yes, boot to twrp recovery then restore the stock backup.
You can find all you need in my thread - https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Post #1 - how-to
Post #3 - you'll find the O2 stock backup
Post #5 - you'll find O2 firmware, install firmware after you restore the backup
ckpv5 said:
So it still have twrp on it ? If yes, boot to twrp recovery then restore the stock backup.
You can find all you need in my thread - https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Post #1 - how-to
Post #3 - you'll find the O2 stock backup
Post #5 - you'll find O2 firmware, install firmware after you restore the backup
Click to expand...
Click to collapse
No, I cannot get into it. When I select HBOOT, then select recovery it just shows white screen, ANDROID and then back to the menu. TWRP no longer works. That's what I'm trying to fix or put on a stock recovery image and then stock OS/firmware.
Just wondering if I need to UNLOCK it again and also do I need USB debug on. I cannot boot into OS so unable to set USB debug.
To UNLOCK bootloader can that be done if you can only get into bootloader menu? S-ON is enabled but not 100% that will stop recovering it? That's just for signed rom/firmware and I just need something stock.
You don't need usb debugging on to unlock the bootloader as it is done on fastboot mode (bootloader).
First I suggest you install the O2 firmware only then see whether you can boot to OS (assuming the OS is still stock base)
Second, re unlock bootloader with unlock_code.bin that you can get from htcdev.com, install twrp 3.x and restore the stock backup and relock bootloader and reflash firmware. This will get your device to fully stock.
So far, I don't see any RUU for your device version that you can get for free, only paid site has it.
Tainted said:
I managed to once get into TWRP but cant anymore. It was UNLOCKED but now RELOCKED which I possibly made it a little harder for me.
Click to expand...
Click to collapse
Relocking the bootloader renders the phone unable to boot into OS by definition, as it expects RUU to be run (but as mentioned, RUU is not available for your CID unless you pay - but it's not needed).
Also, you can't flash TWRP with a locked bootloader, again by definition. The primary limitation of an unlocked bootloader, is that it prohibits flashing unsigned recovery images.
So as suggested, simply unlock the bootloader again (with existing unlock bin code, or get a new one using the HTCDev.com process again). Then flash TWRP and a stock TWRP backup using ckpv5's backup collection (linked in his signature).
redpoint73 said:
Relocking the bootloader renders the phone unable to boot into OS by definition, as it expects RUU to be run (but as mentioned, RUU is not available for your CID unless you pay - but it's not needed).
Also, you can't flash TWRP with a locked bootloader, again by definition. The primary limitation of an unlocked bootloader, is that it prohibits flashing unsigned recovery images.
So as suggested, simply unlock the bootloader again (with existing unlock bin code, or get a new one using the HTCDev.com process again). Then flash TWRP and a stock TWRP backup using ckpv5's backup collection (linked in his signature).
Click to expand...
Click to collapse
ok, well made some progress.
unlocked the bootloader the official way. Very quick which I was surprised.
This then repoened up the recovery menu working.
then used fastboot to install latest twrp
then installed S.Team-JW-7.5.0.zip !!!
The install and everything looked good, no errors and now just not turning on. I think now it's a brick? Does not seem to be coming back to the bootloader menu and certainly does not try to boot.
Wondering if end of the line. Any suggestions? I assume need to get into TWRP and flash stock update from ckpv5.
Must say thanks for replies guys. ckpv5 you done some good work on here.
Tainted said:
The install and everything looked good, no errors and now just not turning on. I think now it's a brick? Does not seem to be coming back to the bootloader menu and certainly does not try to boot.
Click to expand...
Click to collapse
It's really hard to brick this phone (especially with s-on) just flashing TWRP and flashing ROMs. Probably not a brick.
At what point exactly did it shut down/not reboot? ROM installed with no errors, and when you tried to reboot, it went dark? You aren't specific on this point.
How much charge was on the battery when you were flashing the ROM? Did you leave it a long time flashing the ROM, or rebooting, that simply may have drained the battery to shutdown?
Try leaving the phone on charger for several hours, then hold power+vol up for a minute or so, and see if any change (even if just stuck on HTC logo screen).
redpoint73 said:
It's really hard to brick this phone (especially with s-on) just flashing TWRP and flashing ROMs. Probably not a brick.
At what point exactly did it shut down/not reboot? ROM installed with no errors, and when you tried to reboot, it went dark? You aren't specific on this point.
How much charge was on the battery when you were flashing the ROM? Did you leave it a long time flashing the ROM, or rebooting, that simply may have drained the battery to shutdown?
Try leaving the phone on charger for several hours, then hold power+vol up for a minute or so, and see if any change (even if just stuck on HTC logo screen).
Click to expand...
Click to collapse
Hi there,
Well I expect the bootloader to be separate from the rest so we can get into TWRP and normally get out of this situation?
The ROM install finished, battery was at about 80% and everything looked good and I let it reboot the phone. And then it went dead. Right now the PC keeps beeping as a device has just connected and then again as though it's disconnected. I'm watching the device manager and dont see it listed during the connect but device manager tree refreshes. My S7 edge shows up. It flash an orage dot twice, so appears to be a in loop.
I charged the phoned and no luck with any of the power+ vol +/- keys. No response from any of those? I let the phone sit till flat and no orange light and then charged it today and still nothing. Not sure if it's a bad battery but it was up at 83% showing in the TWRP menu and working plugged or unplugged.
It's become a challenge now to make it work, I havent had to mod phones since my HTC One which got heavily modded and then back to stock. I stopped doing that after modding every phone I had since HTC Desire Android 2.3. So been about 4 years since doing all this again. Never had one that was totally bricked.
Tainted said:
Well I expect the bootloader to be separate from the rest so we can get into TWRP and normally get out of this situation?
Click to expand...
Click to collapse
You are correct that bootloader (AKA hboot) is a separate partition, isn't touched by TWRP, and in fact is "protected", and can't be modified with s-on. Only an official signed zip (RUU, OTA, zip) can write to hboot when s-on, which is one of the reasons why I say this phone is hard to brick with s-on, just by flashing TWRP and flashing ROMs.
Tainted said:
Right now the PC keeps beeping as a device has just connected and then again as though it's disconnected. I'm watching the device manager and dont see it listed during the connect but device manager tree refreshes.
Click to expand...
Click to collapse
You won't connect to the phone by PC in any way, unless you can get the phone to power on, at least to bootloader.
A few additional suggestions/comments I made to another user (in another thread) who by strange coincidence has a very similar condition (apparent brick after flashing a ROM): https://forum.xda-developers.com/showpost.php?p=73062871&postcount=10
But to be honest, it's not looking too good, since the condition hasn't changed after charging and trying the button combos.
redpoint73 said:
You are correct that bootloader (AKA hboot) is a separate partition, isn't touched by TWRP, and in fact is "protected", and can't be modified with s-on. Only an official signed zip (RUU, OTA, zip) can write to hboot when s-on, which is one of the reasons why I say this phone is hard to brick with s-on, just by flashing TWRP and flashing ROMs.
You won't connect to the phone by PC in any way, unless you can get the phone to power on, at least to bootloader.
A few additional suggestions/comments I made to another user (in another thread) who by strange coincidence has a very similar condition (apparent brick after flashing a ROM): https://forum.xda-developers.com/showpost.php?p=73062871&postcount=10
But to be honest, it's not looking too good, since the condition hasn't changed after charging and trying the button combos.
Click to expand...
Click to collapse
Cheers for that. Not getting much except for the 2 brief flashes of orange light.
Any chance the battery is totally messed and this is the problem?
Tainted said:
Any chance the battery is totally messed and this is the problem?
Click to expand...
Click to collapse
It's possible. Or it might be something else like motherboard or emmc. It's impossible to say for sure.