my htc m8 is lock bootloader i try to unlock but i cant n then i have done a funny mystic. i just go to my boot screen n flash a rom with my lock bootloader (with stock kernal) after that my phone start n still in boot mode it's not properly
can any know what should i do ?
i'm a sony user i thought htc flash process will like sony so i can fix it easily but it's not like that n now i'm in trouble
I don't follow what you did. You can't flash custom recovery with a locked bootloader, so how could you try to flash a ROM?
Also, you should never flash a ROM without knowing how to recover, and the easy way to do that would be to make a backup in TWRP custom recovery. But you never did that, since you never installed TWRP custom recovery.
What is the problem with unlocking the bootloader?
Basically, you need to give much more detail in order for us to provide any proper help. Describe in detail, each step you tried in sequence, what failed (with specific results, error messages, etc.), what specific files you used, etc.
Also, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Never assume one Android device is the same as others. They all have their own nuances and quirks. Even different phones made by the same manufacturer, will greatly differ in root methods, recovery procedures, etc. Read, research, learn and make sure you understand before you try anything.
Related
Hi!
So what I want to do is only to create a nandroid backup. I dont want to install a custom ROM and I dont want to root my phone. So I tried to boot recovery-RA-hero-v1.5.2, but got a "FAILED: (remote: not allowed)". I have figured out that this is because I have a locked bootloader.
Now for my question. I would prefer not to go through the complicated process of creating a gold card. Is it enough to change my SPL? Im not really sure what a bootloader is... it feels as if it should be enough to change my SPL, but I want to be sure before I try it. Any information or link to good information would be greatly appreciated!
Cheers,
edit: Also, another question: what kind of check is it that I run into when I fail loading the recovery image? Is it the CID? Or a SIM-lock?
Well, from what I have learned it wont help to change my SPL. The question is, must I root my phone to get a nandroid backup? One question that have risen is, what is a bootloader? Is it the same thing as an SPL? Any help would be a real lifesaver!
to create a nandroid backup you need the custom recovery image, period.
not sure what you are talking about bootloader and spl, that stuff is not related to the recovery image. to change the spl you need the custom recovery aswell.
SPL ≠ recovery ≠ bootloader.
Bootloader is an actual part of the software, that loads the OS.
recovery, like the Amon Ra 1.5.2. recovery, is a toolkit to flash and manage your hardware / software. Something like a BIOS in a regular computer, with added ability to partition, flash other parts of the phone, or like you wanted: to backup the ROM entirely.
SPL is something that operates before the bootloader: Secondary Program loader; the small lead-in to it. Hero phones however (tested with the GSM version, test sample: 2 phones) have no limitation so no need for special SPL's for most roms / recovery's. Using a non updated or not most recently updated HTC RUU, you can use Flashrec 1.1.2 or 1.1.3 to get the Amon RA recovery effortless.
I believe, correct me if I'm wrong: That the CID lock, which is the SIM-lock, is on SPL level. However, this should not interfere with one of the other three. It simply allows you (or rather denies) to use a certain SIM card and register on certain networks.
Disclaimer: I'm not an Android guru. I only recently looked into this matter. Please correct me if I'm wrong.
Additionally, read the Wiki's:
http://wiki.xda-developers.com/index.php?pagename=GSM Hero Guides
kendong2 said:
to create a nandroid backup you need the custom recovery image, period.
not sure what you are talking about bootloader and spl, that stuff is not related to the recovery image. to change the spl you need the custom recovery aswell.
Click to expand...
Click to collapse
But for some reason I cant make a nandroid backup with my phone at its current state, so something must be done.
Uniqron said:
SPL ≠ recovery ≠ bootloader.
Bootloader is an actual part of the software, that loads the OS.
recovery, like the Amon Ra 1.5.2. recovery, is a toolkit to flash and manage your hardware / software. Something like a BIOS in a regular computer, with added ability to partition, flash other parts of the phone, or like you wanted: to backup the ROM entirely.
SPL is something that operates before the bootloader: Secondary Program loader; the small lead-in to it. Hero phones however (tested with the GSM version, test sample: 2 phones) have no limitation so no need for special SPL's for most roms / recovery's. Using a non updated or not most recently updated HTC RUU, you can use Flashrec 1.1.2 or 1.1.3 to get the Amon RA recovery effortless.
I believe, correct me if I'm wrong: That the CID lock, which is the SIM-lock, is on SPL level. However, this should not interfere with one of the other three. It simply allows you (or rather denies) to use a certain SIM card and register on certain networks.
Disclaimer: I'm not an Android guru. I only recently looked into this matter. Please correct me if I'm wrong.
Additionally, read the Wiki's:
http://wiki.xda-developers.com/index.php?pagename=GSM Hero Guides
Click to expand...
Click to collapse
Thank you very much!
Correct me if Im wrong, but does not Flashrec actually flash the recovery on my phone? Preferable I would like to just load it once to create a nandroid-backup, so nothing is changed on the phone.
Also, if I want to do it on the most recent HTC RUU, must I root the phone then? Or is there some other way?
Another question: Heros that are produced today, do they have this lastest HTC RUU that flashrec does not work on?
Cheers,
1: you can always fastboot into recovery, without flashing it
2: flashrec exploits a bug in 2.6.27 kernel. It's not linked to RUU.
adwinp said:
1: you can always fastboot into recovery, without flashing it
2: flashrec exploits a bug in 2.6.27 kernel. It's not linked to RUU.
Click to expand...
Click to collapse
Hi! Just to clarify: I want to fastboot into a custom recovery that allows nandroid. This isnt always possible without some effort, is it? Because I failed with some error message on my first attempts, as described in my first post.
Anyhow, I tried to use flashrec and it worked. However, it flashed the recovery image on my computer. This is not what I wanted. I would also like an easy solution that works for the version av Hero that flashrec does not work for.
I then tried to change the SPL as described in to "update-hero-hboot-1.76.2007-signed". After this I tried running "fastboot boot recovery-RA-hero-v1.5.2.img". This worked. However, I am unsure if it worked because I changed SPL or becuase I already had changed the recovery image with flashrec. Could someone clarify this for me? I really want to understand this before I dare help my friends with their phones.
sandis84 said:
Hi! Just to clarify: I want to fastboot into a custom recovery that allows nandroid. This isnt always possible without some effort, is it? Because I failed with some error message on my first attempts, as described in my first post.
Click to expand...
Click to collapse
this is correct. from some softwarelevel (2.73.110.26?) upwards you can not fastboot a recovery image.
sandis84 said:
Anyhow, I tried to use flashrec and it worked. However, it flashed the recovery image on my computer. This is not what I wanted. I would also like an easy solution that works for the version av Hero that flashrec does not work for.
Click to expand...
Click to collapse
in fact it is too late for that. you can try to get the original recovery image and flash it over the custom image, but i don't see the benefit for that.
sandis84 said:
I then tried to change the SPL as described in to "update-hero-hboot-1.76.2007-signed". After this I tried running "fastboot boot recovery-RA-hero-v1.5.2.img". This worked. However, I am unsure if it worked because I changed SPL or becuase I already had changed the recovery image with flashrec. Could someone clarify this for me? I really want to understand this before I dare help my friends with their phones.
Click to expand...
Click to collapse
AFAIK fastbooting of the recovery works now because you already have the custom recovery image (which you got through flashrec), so yes, flashing the spl was unnecessary.
tbh i wouldn't mess with that stuff more, you have a good setup now, any unnecessary flashing (especially of the spl) brings the danger of bricking your phone...
Uniqron said:
I believe, correct me if I'm wrong: That the CID lock, which is the SIM-lock, is on SPL level. However, this should not interfere with one of the other three. It simply allows you (or rather denies) to use a certain SIM card and register on certain networks.
Click to expand...
Click to collapse
You are wrong!
CID Lock ≠ SIM Lock
The CID lock (carrier id) prevents you from flashing a different carriers ROM to your device (i.e. a ROM with a different CID). The SIM lock prevents you from using a different carriers SIM in your device.
Regards,
Dave
Need help here.. what next i suppose to do to make custom firmware?
already UNLOCKED and HBOOT 2.00.. try many times, but unsuccessful..
i940.photobucket.com/albums/ad243/imranmarzuk_2010/2012-07-19-526.jpg
i940.photobucket.com/albums/ad243/imranmarzuk_2010/2012-07-19-525.jpg
HTC_21st said:
Need help here.. what next i suppose to do to make custom firmware?
already UNLOCKED and HBOOT 2.00.. try many times, but unsuccessful..
i940.photobucket.com/albums/ad243/imranmarzuk_2010/2012-07-19-526.jpg
i940.photobucket.com/albums/ad243/imranmarzuk_2010/2012-07-19-525.jpg
Click to expand...
Click to collapse
hey, if you have used htcdev tool to unlock your bootloader , you need to LOCK again the bootloader in the same way, and then use Advanced ACE Hack Kit (12062012) w/ENG Support, after using this program use the clockworkmod recovery to flash a custom rom (android revolution hd, miui, ics. etc)
HTC_21st said:
Need help here.. what next i suppose to do to make custom firmware?
already UNLOCKED and HBOOT 2.00.. try many times, but unsuccessful..
i940.photobucket.com/albums/ad243/imranmarzuk_2010/2012-07-19-526.jpg
i940.photobucket.com/albums/ad243/imranmarzuk_2010/2012-07-19-525.jpg
Click to expand...
Click to collapse
Very little information to go on, but when people say unlocked boot loader. The issue is that flashing of roms is different and people fail to realize that.
After flashing a rom you have to flash the boot.img separately. Take the boot.img from what ever rom you want, put it in your fast boot folder. Boot phone into hboot. And run
Fastboot flash boot boot.img
Can't stress enough to everyone to please research before you attempt anything on a phone. Heck I spent a month reading the threads learning about roms/flashing/troubleshooting before I attempted to root.(this was my first android device)
Have another problem;
why my device turned off by it self when usb/charger is unpluged?
its there any problem at my mini usb socket?
or its is like that when got problem with software?
lordstein said:
hey, if you have used htcdev tool to unlock your bootloader , you need to LOCK again the bootloader in the same way, and then use Advanced ACE Hack Kit (12062012) w/ENG Support, after using this program use the clockworkmod recovery to flash a custom rom (android revolution hd, miui, ics. etc)
Click to expand...
Click to collapse
so, i'm totally wrong.. hehe.. very hard to understand, some tutorial i thing not completely step by step..
but i really try to root my self and result still can't success..
with this problem, where can i find some useful tutorial step by step for beginner like me?
marsdta said:
Very little information to go on, but when people say unlocked boot loader. The issue is that flashing of roms is different and people fail to realize that.
After flashing a rom you have to flash the boot.img separately. Take the boot.img from what ever rom you want, put it in your fast boot folder. Boot phone into hboot. And run
Fastboot flash boot boot.img
Can't stress enough to everyone to please research before you attempt anything on a phone. Heck I spent a month reading the threads learning about roms/flashing/troubleshooting before I attempted to root.(this was my first android device)
Click to expand...
Click to collapse
problem is, i cant see correct step from tutor.. stuck and confuse..
many thanks if u can give correct tutorial for me..
or u can personal message to me or email at [email protected]
thanks:angel:
Well after almost a week of Googling, I've given up.
My Dad's HTC One M7 seems to be soft bricked (i.e. No OS), and will only enter the fastboot menu. All options therein (factory reset, fastboot), just put the device back in fastboot mode.
I then tried to unlock the device on the HTC site. I got to the final stage (flashing with unlock code, which shows as successful on my computer), and the confirmation screen on my phone does not appear. It is still showing *LOCKED*.
Moving from here the only option seemed to be an RUU, however this only seems to work with S-OFF. My S is most definitely ON. To make it S-OFF, I think I'd need to boot onto an OS and enter debug mode.
I have an OTA file for my carrier which seems to be up to date. Is there any chance this would help?
So I'm sort of chasing my tail here, any help would be appreciated. One possible solution would be if I could possibly unlock a bricked device? (A rare request from what I gather, as most phones are bricked after custom ROMs).
I find it so frustrating that this has happened when I've never even rooted/unlocked the device. I'd never seen the bootloader menu before this.
Any help would be appreciated. Thank you.
m7misery said:
Well after almost a week of Googling, I've given up.
My Dad's HTC One M7 seems to be soft bricked (i.e. No OS), and will only enter the fastboot menu. All options therein (factory reset, fastboot), just put the device back in fastboot mode.
I then tried to unlock the device on the HTC site. I got to the final stage (flashing with unlock code, which shows as successful on my computer), and the confirmation screen on my phone does not appear. It is still showing *LOCKED*.
Moving from here the only option seemed to be an RUU, however this only seems to work with S-OFF. My S is most definitely ON. To make it S-OFF, I think I'd need to boot onto an OS and enter debug mode.
I have an OTA file for my carrier which seems to be up to date. Is there any chance this would help?
So I'm sort of chasing my tail here, any help would be appreciated. One possible solution would be if I could possibly unlock a bricked device? (A rare request from what I gather, as most phones are bricked after custom ROMs).
I find it so frustrating that this has happened when I've never even rooted/unlocked the device. I'd never seen the bootloader menu before this.
Any help would be appreciated. Thank you.
Click to expand...
Click to collapse
You need to ask in the m7 sections. This is the m8 area. What rom was it running? . I have a couple things to try if it's a Verizon one.
m7misery said:
Well after almost a week of Googling, I've given up.
My Dad's HTC One M7 seems to be soft bricked (i.e. No OS), and will only enter the fastboot menu. All options therein (factory reset, fastboot), just put the device back in fastboot mode.
I then tried to unlock the device on the HTC site. I got to the final stage (flashing with unlock code, which shows as successful on my computer), and the confirmation screen on my phone does not appear. It is still showing *LOCKED*.
Moving from here the only option seemed to be an RUU, however this only seems to work with S-OFF. My S is most definitely ON. To make it S-OFF, I think I'd need to boot onto an OS and enter debug mode.
I have an OTA file for my carrier which seems to be up to date. Is there any chance this would help?
So I'm sort of chasing my tail here, any help would be appreciated. One possible solution would be if I could possibly unlock a bricked device? (A rare request from what I gather, as most phones are bricked after custom ROMs).
I find it so frustrating that this has happened when I've never even rooted/unlocked the device. I'd never seen the bootloader menu before this.
Any help would be appreciated. Thank you.
Click to expand...
Click to collapse
maybe best to see if you can unlock it via HTC Dev(as u are in fastboot mode)
Then install custom recovery, full wipe and flash a new rom via adb sideload, that will give you the system back and it should boot.
m7misery said:
Moving from here the only option seemed to be an RUU, however this only seems to work with S-OFF.
.
Click to expand...
Click to collapse
This is false. RUU is designed to run on stock devices and will run just fine with S-on or S-off as long as you are running the correct RUU for your version (and also the RUU number needs to be equal or greater than what is on the phone, you can't "downgrade" while S-on).
But as mentioned previously, this forum section is for the M8 as clearly noted in the forum title. You need to get advice in the M7 forum, as advice given here (applicable to the M8) can be incorrect or even harmful to your device.
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.
Hi guys. I used to be up on my HTC flashing etc. but I've moved away from them over the last couple of years and a friend has come to me with a problem and I'm not sure what to suggest.
Please see attached image for reference to software/hboot/radio versions etc.
Basically I've quizzed him on what he's done to get to this state. He hasn't tried to flash a rom or new hboot, root, s-off or anything like that. In fact I'm pretty certain he wouldn't know where to start. He said it was charging overnight and in the morning it would only boot to hboot. Selecting any of the options from there results in a blank screen before eventually looping back to hboot.
Any help or guidance I what to try would be massively appreciated. Thanks!
Your friend has a variant of the M8, known as the M8s.
It might be tough to find an RUU tool to restore the device, or a stock TWRP backup (stock ROM).
If no RUU for that OS number, restoring a stock TWRP backup (if you can find the right one) would be an involved process:
- unlock bootloader
- install TWRP custom recovery
- restore the right stock TWRP backup
So not sure how far you want to go with this. My experience with the M8s is limited, and resources for the "s" variant are also limited.