i need help... Can't unlock bootloader - HTC One Max - HTC One Max

Hello ! So I got this one max, it suddenly started to bootloop out of no where. So I decided to unlock bootloader and flash a stock rom.
However, after flashing the unlocktoken, the screen on my one max asks if I'm sure I want to proceed, I select yes but the phone just restarts and the phone doesn't unlock.I said to myself maybe if i flash a firmware it will work, i typed "fastboot oem rebootRUU" but the phone just restarted instead of giving me the black screen with grey HTC logo

HTC DEV website is where you need to go and follow on-screen instructions to completely and successfully unlock your bootloader.
For stock rom flashing you don't need to unlock bootloader unless you're planning on Rooting and installing Custom Recovery, at this point it seems that you're stock. You need to either adb a custom recovery and flash a firmware or you're stuck and only need to adb over stock IMG file perhaps or something of the sort. I would recommend googling this and see what you find.
I myself have a problem... I cannot seem to re-lock my bootloader, I have followed every single guide in the entire world... Including Scotty's Guide here on XDA. I even tried to GURU Zip Aroma Installer, didn't work either. It's a waste of time.
Sometimes you get stuck bad. GL

Related

[Q] Used HTC Unlock method, and now?

Hi there
First, I know that it might be a stupid question, but I'm new to Android.
I've read about the official unlocking method HTC offers and yesterday I tried it out, worked all fine.
But what has changed? What can I do now which I couldn't before? I don't get it! Can I flash ROMs now? How?
I can only see that it now says "UNLOCKED" at the top of the bootloader. Also, I've read about Clockwork-Mod and TW and so on, so I tried to "install" Clockwork-Mod. Failed. Now it crashes when trying to open "Recovery" in bootloader.
But main question: What can I do now, with unlocked phone?
Thanks! And don't laugh about my English... I've tried my best
Install TWRP recovery, there is a sticky in the dev section. Then you can indeed flash ROMs however since you are s-on still you will have to flash a bit differently. Search the dev section for joeykrim's flash image gui. It has all the instructions you need to flash a custom rom.
A little further explaination, since you are still s-on the kernels don't flash correctly unless you flash using fastboot or joeys gui. If you don't flash this way you can end up in a bootloop or have broken wifi and 4g etc.
3VO Sent
luckyluke02 said:
Hi there
First, I know that it might be a stupid question, but I'm new to Android.
I've read about the official unlocking method HTC offers and yesterday I tried it out, worked all fine.
But what has changed? What can I do now which I couldn't before? I don't get it! Can I flash ROMs now? How?
I can only see that it now says "UNLOCKED" at the top of the bootloader. Also, I've read about Clockwork-Mod and TW and so on, so I tried to "install" Clockwork-Mod. Failed. Now it crashes when trying to open "Recovery" in bootloader.
But main question: What can I do now, with unlocked phone?
Thanks! And don't laugh about my English... I've tried my best
Click to expand...
Click to collapse
New to Android ... One of these days I should put together a guide from start to finish.
Here are a few more details in addition to the great answer already provided in the above post. A link to my applciation, Flash Image GUI, which makes loading custom kernels a little bit simplier and possible without a computer attached to the device.
There are basically three partitions we look to commonly customize on the Android device, boot, recovery and system. Of course, there are times when we customize or upgrade other partitions but they aren't as common or as required.
Boot holds the booting kernel.
Recovery holds the recovery kernel and recovery binary.
System holds the android system.
On many HTC devices, some or all of these partitions are locked by the bootloader which is essentially a very low level write protection.
The s-off revolutionary method removes write protection on all partitions.
The HTC unlock method removes write protection on some partitions and also depends on the mode the device is booted into. This is the first time HTC has made an official unlock method through their stock bootloader. Who knows if they will improve it in the future by unlocking all partitions or if they still stick to their current model.
Hope that helps a bit more background/history to the context! Good luck!

[Q] cant unlock bootloader or flash stock rom htc legend help

HI hope someone can help me with this, i have tried without success to unlock my bootloader, i have updated to hboot 1.02 but when i try to do the fastboot flash unlocktoken Unlock_code.bin it sits at 0percent and doesn't move and no errors, i've tried this with my goldcard in and out of the phone and with cyanogen and b08 roms, also for some reason i can't flash the stock rom so i can get the required update from htc(thinking that's y the unlock code won't go), i've tried getting numerous ruu's and i was getting signature verification fails every time, i tried with windows the exe and also exracted the rom.zip and still no luck, i prefer using linux and adb though and tried numerous ways to get this to work with no success, i've also tried signing a rom.zip and the phone just says no signature, also tried renaming to LEGEIMG.zip and update.zip and just can't flash stock rom, also made a new goldcard thinking the other was bad and did the htcdev for the unlock code with a goldcard and without, also tried the ruu.exe in windows with new said goldcard and i think the other was bad because i get a different error now for reason it can't update my rom(was using the rom i originally rooted with which has sense). it says wrong bootloader version when i try and update, anyone know what i can do, i'm running outta ideas, thanks in advance
I Unlocked my bootloader with HTCdev. You said you tried. What went wrong?
If you have updated your phone to one of the ruus HTC gives you ( execute the exe ), there shouldn't be any problem : the HTC guide is clear and easy. If you have successuffly unlocked the bootloader, now you have to flash the clockwork recovery.
when i go to fastboot it stays on copying at 0 percent with the unlock_code.bin....My phone has root access before i ran the hboot update and still does but i can't flash the new ruu, it won't allow me to, i tried running the htc ruu and it fails with can't update, bootloader version incorrect, i tried with the b-08 rom, i can't get back to stock
Have you tried flashing this? ----> http://forum.xda-developers.com/showthread.php?t=1497357
If you don't install one of the updates given by HTC, bootloader unlock won't work. If you have the same problems that I had ( my Legend also wasn't rooted ) the RUUs won't install, right? I flashed first this one and then one of the HTC RUUs and after this everything worked perfectly.
nope, i didn't try that one yet, but the thing is my legend was rooted before i tried flashing these htc ruus, i just want my bootloader unlocked, i had cyanogen on it then flashed a rooted one with sense (b08) thinking that would let me update but it didn't, so i'm downloading that one you pointed me to now, i'll try and flash it and let you know how it goes.
When i flash that rom i get a main version is older error when i rename it to LEGEIMG and flash it via fastboot, what can i do now?
I followed Blayo's guide http://forum.xda-developers.com/showpost.php?p=22613990&postcount=62 with my already rooted Legend. Try to follow exactly. You said using a gold card - don't think this is even necessary. At least I did not use one, and it is working perfectly.
After flashing the new bootloader, did you really unlock?
(last step of guide above: follow the instructions on HTCdev from Step 8 to unlock)
Wait, all the RUUs you have to flash before unlocking are HTC's executable files ( .exe ). You have updated your phone executing them, haven't you? After that I just rebooted my phone to fastboot and connected it. I found the unlock code, sent it to HTCdev, received an e-mail with the file to complete unlock and then unlocked. I never used anything like UPDATE.zip or LEGEIMG. I tried following the BlaYo's instructions but they didn't work for me. I just did what HTC said ( easyer and safer ).
hmmmmm
hello guys... pwde ba ko mag unlock ng bootloader my x8 stiker is 11w48?
astig_king24 said:
hello guys... pwde ba ko mag unlock ng bootloader my x8 stiker is 11w48?
Click to expand...
Click to collapse
keyboard error?!
i solved my problem, i sold the phone and bought another legend. LOL, no seriously though, i did sell it and got another but i tried everything and couldn't unlock bootloader, i tried the exe files from htc, tried extracting the zip files, tried fastboot and renaming to LEGEIMG, just couldn't get it unlocked, so i flashed the latest cyanogen 7.2 and sold the darn thing, now i got another and made 50$ in the process as i bought the new one 50$ cheaper and i'm going to go through the htc channels to unlock the bootloader but does anyone know if i'll be able to flash cm7 after i do that?
bootloader
I have a similar problem with my Legend i had already rooted my legend following this guide http://chrg.zxq.net/htc-legend-root.html. I decided to unlock the bootloader folowing the guide on HTC dev to the letter and it worked fine bootloader unlocked. Only prolem is after rooting the phone again and flashing cm7 the bootloader is now locked again. What to do any ideas id be very greatfull.
sam0056 said:
I have a similar problem with my Legend i had already rooted my legend following this guide http://chrg.zxq.net/htc-legend-root.html. I decided to unlock the bootloader folowing the guide on HTC dev to the letter and it worked fine bootloader unlocked. Only prolem is after rooting the phone again and flashing cm7 the bootloader is now locked again. What to do any ideas id be very greatfull.
Click to expand...
Click to collapse
What do you mean with 'rooting again'? Once you have unlocked bootloader, you are able to flash a recovery, and then CM, which is rooted. See http://forum.xda-developers.com/showthread.php?p=24102979 for latest Recovery and latest CM7.2 builds
Ok just to update i flashed the HTC dev bin file again and had restore cm7 backup and bootloader is unlocked once again.
got her goin good now, unlocked bootloader with htcdev, fastboot flashed cwm, then i was able to flash cm7.2 and gapps no problem at all, now if we could only s-off the legend???
dantheman1977 said:
... now if we could only s-off the legend???
Click to expand...
Click to collapse
For what reason? It's quite similar
Because it's still not totally unlocked
dantheman1977 said:
i solved my problem, i sold the phone and bought another legend. LOL, no seriously though, i did sell it and got another but i tried everything and couldn't unlock bootloader, i tried the exe files from htc, tried extracting the zip files, tried fastboot and renaming to LEGEIMG, just couldn't get it unlocked, so i flashed the latest cyanogen 7.2 and sold the darn thing, now i got another and made 50$ in the process as i bought the new one 50$ cheaper and i'm going to go through the htc channels to unlock the bootloader but does anyone know if i'll be able to flash cm7 after i do that?
Click to expand...
Click to collapse
After unlocking boot loader:
1. Use htcsupertoolv3 to root
2. Install rom manager and titanium backup
3. Run titanium backup. It will ask you to update su. accept (i'm not sure if this step is required, but this is how i done it)
4. Copy recovery-clockwork-5.0.2.0-legend to your Android folder created during bootloader unlock
5. With your phone on fastboot mode open terminal in your PC android folder and type:
fastboot flash recovery recovery-clockwork-5.0.2.0-legend.img
Your phone will go to recovery mode.
6. Reboot your phone in normal mode
7. From now on, each time you want to go into recovery, use rom manager
Done
dantheman1977 said:
Because it's still not totally unlocked
Click to expand...
Click to collapse
So for what I have understood from HTCdev, you can do everything similar to S-OFF, with one exception: you cannot unlock a SIM lock.
Oops... said:
So for what I have understood from HTCdev, you can do everything similar to S-OFF, with one exception: you cannot unlock a SIM lock.
Click to expand...
Click to collapse
True, you can't. I'm not sure if flashing a custom rom will unlock it, as my phone sim card was unlocked from very beginning. Probably not?

[Q] First time poster and I really need help!

Hey guys. Need a big hand here. So I have a HTC One on contract from Three in the UK.
I rooted the phone and all that jazz and decided on putting a custom ROM on my device.
However while in TWRP I wiped the phone and seemingly all the contents on it, including TWRP.
Now I have a bricked phone that boots into recovery/ the bootloader only. I've tried flasing
RUU files on but it fails with the error code 140? I don't know much about this I'm quite a noob.
In recovery the information is as follows:
*** TAMPERED ***
*** RELOCKED ***
*** SECURITY WARNING ***
M7_UL PVT SHIP S-ON RH
HBOOT- 1.54.0000
RADIO-4A. 17. 3250. 14
OpenDSP-v31.120.274.0617
OS-2.24.401.0
eMMC-boot 2048MB
Please help me. I've read through wonderful guides by other patrons on this website but nothing seems to work.
I'm at my wits end.
Thank you in advance for any help.
I know very little about this, but just to brainstorm (and confirm a few basic facts):
When you rooted originally, did you use HTC's bootloader unlocker or a different method to unlock the bootloader?
How are you flashing ROMS? Are you doing everything through the phone (example, using one-touch-root apps) or are you using the Android Debug Bridge?
The bootloader typically comes with options to reboot, boot into recovery, factory reset, etc. Can you confirm that these options have disappeared (or never existed in the first place)?
My knee-jerk reaction is that you didn't use an HTC bootloader unlocker and, therefore, the HTC GUU detects a bootloader mismatch and aborts. Therefore, you need to see if there's a way to flash a stock HTC bootloader (which, I can tell you from experience, is usually a one-way-trip to super-bricking) or see if the bootloader you already have installed can be unlocked through the ADB.
In my very limited experience and understanding of Android, it's generally pretty difficult to wipe the recovery partition from within the phone - one generally as to flash it from ADB or screw with the bootloader in some way to wipe it. I wonder, therefore, whether the recovery partition is just fine but maybe the bootloader is throwing a fit because it's not the HTC default.
I'm sure you've tried or thought of all of this, but since nobody else is stepping up, I thought I'd help brainstorm a bit and keep the thread fresh.
Borden Rhodes said:
I know very little about this, but just to brainstorm (and confirm a few basic facts):
When you rooted originally, did you use HTC's bootloader unlocker or a different method to unlock the bootloader?
How are you flashing ROMS? Are you doing everything through the phone (example, using one-touch-root apps) or are you using the Android Debug Bridge?
The bootloader typically comes with options to reboot, boot into recovery, factory reset, etc. Can you confirm that these options have disappeared (or never existed in the first place)?
My knee-jerk reaction is that you didn't use an HTC bootloader unlocker and, therefore, the HTC GUU detects a bootloader mismatch and aborts. Therefore, you need to see if there's a way to flash a stock HTC bootloader (which, I can tell you from experience, is usually a one-way-trip to super-bricking) or see if the bootloader you already have installed can be unlocked through the ADB.
In my very limited experience and understanding of Android, it's generally pretty difficult to wipe the recovery partition from within the phone - one generally as to flash it from ADB or screw with the bootloader in some way to wipe it. I wonder, therefore, whether the recovery partition is just fine but maybe the bootloader is throwing a fit because it's not the HTC default.
I'm sure you've tried or thought of all of this, but since nobody else is stepping up, I thought I'd help brainstorm a bit and keep the thread fresh.
Click to expand...
Click to collapse
I unlocked the bootloader originally by getting a specific code from HTC and using it through the command prompt I think. I can go into the bootloader and it has all the fastboot, recovery, factory reset business there. Trying factory reset does nothing. I've downloaded HTC toolkit 2.2 and I tried initially pushing ROMS to flash to TWRP, but it would never detect my phone. Then I stupidly did a full wipe through TWRP and now that's disappeared. All that's left is the bootloader now. I've tried forcing RUU updates through the HTC toolkit but it always fails. So does running the normal RUU process. I can't seem to find the correct one for Three UK. The most I've been able to do is re-lock the bootloader and I'm running out of ideas. Thank you for your reply. I feel so helpless!.
If I've read your message correctly, you are doing everything through the HTC toolkit and not through the Android SDK. Frankly, I don't know how the former works. Especially if the HTC Toolkit isn't detecting your phone, you may want to run over to http://developer.android.com/sdk/ and fetch the SDK for your system and set it up. You don't need the ADT Bundle, just the SDK Tools link at the bottom. This may make it easier for other, more knowledgeable people debug your phone, since they all use the SDK. The weaponry you'll be using is all in the <sdk install location>/tools directory, so get a command prompt window pointed there (by the by, are you using Windows, Mac or Linux?)
If you already have your SDK up, or once you do, you'll want to get familiar with the fastboot command, described in this post: forum.xda-developers.com/showthread.php?t=2277112 . What we want to do is see whether we can flash a new recovery ROM.
As long as you don't attempt to flash over the bootloader, you shouldn't super-brick your phone. Based on the message in your original post, your bootloader may have relocked itself. If your first attempt at installing a new recovery ROM doesn't work, then you'll have to use the procedure you used originally to unlock your bootloader. If you've forgotten how to do that, then these instructions (which assume you're using the SDK) should help: http://wiki.cyanogenmod.org/w/Install_CM_for_m7.
You're currently using TWRP, which I've personally found buggy. Until you have a functioning phone again, you may want to use ClockworkMod (CWM) Recovery instead: http://www.clockworkmod.com/rommanager. It has fewer features, but at least they work properly. If flashing ROMs over fastboot is new to you, there are plenty of guides on the Interwebs to help you. I'll also try to walk you through it if you let me know where you're getting stuck. The critical thing, considering that there are many types of HTC One, is to make sure that you flash the ROM that exactly matches your phone. If you flash the wrong ROM, you probably won't break your phone any more than it is, but let's try not to test that theory. If you're not positive which phone you have, say so and we'll help you find out.
Let us know once you have CWM on your phone or where you got stuck. The advantage of using the SDK, too, is that you can copy and paste the output right back to the forum.
I hope I understood everything correctly. Let me know if I haven't.

can't OEM unlock!

hey everyone. trying to OEM unlock the TWRP bootloader. When I type "fastboot OEM unlock" it will reboot into TWRP bootloader, and nothing unlocks. I know this because when I type "fastboot oem device-info" it says "unlocked FALSE".
I have OEM unlock and USB debugging enabled.
This is a phone with previously successfully installed CM13, and now I'm trying to revert to stock/unrooted. I can't seem to flash the recovery at all here because I can't get the damn thing to unlock.
Any ideas?
Did you lock the bootloader ? If your flashing Roms and custom recoverys imagine its already unlocked. Bootloader won't lock itself. If you want full stock just flash any OS2 firmware with twrp. You can worry about stock recovery after. I would just leave the bootloader unlocked won't hurt anything.
I had the same issue not long ago. Finally, i used the mega unbrick guide, but warning, all the data is lost
Ps: Sorry for bad english
hey, thanks for the response. I have been following the following tutorial (and others similar for installing CM13):
(great, website won't let me post it here... it's the unlockr oneplus x guide)
so yes, I originally flashed the stock recovery and replaced it with the one from the tutorial. There were a few hiccups during setup, which may have affected why I can't easily update nightly now, so now I'm trying to revert to the unrooted stock state so I can try from scratch, hopefully fixing the issues I'm seeing now. The problem is that I can't flash the recovery using the stock recovery... I can't even update the damn recovery because it's locked. Is this what is meant by a 'soft brick' ?

Can't switch from stock

I'm really out of ideas to what's causing this so I could use some help.
My tablet has been fine for a long time and has had many roms on it previously. I have been on rooted stock however for over a year now and decided to try a rom again....
However I have tried 3 different roms now all with catastrophic problems. I install them fine through twrp along with gapps then reset Tablet but get a black screen with just a blinking charge light if it's plugged in. No boot logo or anything.
I managed to revert back to stock about 5 times today through flash mode and flash tool but I don't know what's going on.
I rooted, turned on debugging and reflashed twrp but it keeps happening across different android versions too. I thought maybe I had relocked bootloader so I tried to check through adb oem but it freezes, so I ran the unlock command just in case through adb and it was fine but still freezes.
Any ideas?
To add to this I just downloaded a dialer app on stock to check bootloader unlock status.
It says bootloader can be unlocked but nothing about its actual status. I'm more or less certain this is the issue now so can anyone advise what to do? I manually tried unlocking bootloader and it just restarted like everything was fine but nothing changed.
SabertoothTitan said:
To add to this I just downloaded a dialer app on stock to check bootloader unlock status.
It says bootloader can be unlocked but nothing about its actual status. I'm more or less certain this is the issue now so can anyone advise what to do? I manually tried unlocking bootloader and it just restarted like everything was fine but nothing changed.
Click to expand...
Click to collapse
I'm not an expert to be honest but I would try that:
put your tablet in fastboot mode, connect it to your pc and in fastboot type
"fastboot flash boot twrp.img"
Now you should have TWRP.
If this work your bootloader should be unlocked otherwise I think you should see some error in fastboot
Once you have twrp I suggest you to flash resurrection remix 5.7.0 (android 6.0.1). I suggest it just because it worked without problem with my tablet Z.
Something not clear to me: you started just with a rooted stock ROM or you unlocked bootloader, flashed TWRP and then your ROM?
I started with rooted stock rom, I am using dual recovery that seems to be working fine (it was faster since its just a bat file). I originally rooted using kingroot on stock which I used to flash stock rom prerooted with supersu with twrp.
If I try the same process with anything that isn't stock it's black screen on reboot. No Sony logo or anything.
Ive tried changing recovery to newest twrp, changing sd card to a different one, different ROMs including the one you mentioned because that's the one I wanted to try. I also tried with and without black kernel. None made any difference. Black screen boot everytime with just a blinking light on side like its got no OS installed at all.
Just to clarify, my bootloader should be unlocked. I've checked but if I run the adb command to check it just freezes like it's eternally loading. Using dialer go check it doesn't even display anything about it aside from the fact it can be unlocked.
what command do you type? "fastboot oem device-info"?
ok so I have an update, something is definitely messed up with my bootloader.
I tried to relock bootloader from fastboot but its also stuck in a loading cycle for no reason. It seems on some level my bootloader is unlocked because I can flash recoveries fine, but when I come to put a new ROM on the device it won't let me and black screens.
From fastboots I used the commands 'fastboot oem lock' and I just get '...' forever underneath. If I use 'fastboot devices' my device is listed, if I use 'fastboot -i 0x0fce oem unlock 0xbootloadercodehere' it fails the first time, then works the second time and says ok but its clearly done nothing when the device reboots. 'fastboot oem device-info' also leaves me with the '...' on command prompt forever too.
I have no idea what to do if bootloader is screwy at all.
-Pepe said:
what command do you type? "fastboot oem device-info"?
Click to expand...
Click to collapse
Yup that's what I used. I'm pretty sure bootloader is borked somehow though. I tried reinstall from Sony software too which hasn't changed anything.
SabertoothTitan said:
Yup that's what I used. I'm pretty sure bootloader is borked somehow though. I tried reinstall from Sony software too which hasn't changed anything.
Click to expand...
Click to collapse
I just tried with my XTZ and "fastboot oem device-info" just froze, it had 3 dot and nothing else. In my OPO it worked.
I'm gonna search something else...
Whats weird is my tablet also won't install anything on TWRP, I just tried installing SuperSU from it to see if it would work (having to use Kingroot atm) and it just does nothing.
I think this is the issue since I'm factory resetting before installing a ROM, which is therefore wiping my system and when I come to reset because TWRP isn't installing anything its acting like there isn't a system installed.
I can install via ADB fine, just when it comes to recovery... system says no. Its weird because its like its got a locked bootloader or something but even though I reinstalled using Sony software its still the same. If I try unlock bootloader again, I get an error first time then it says OKAY and does nothing.
SabertoothTitan said:
bootloader can be unlocked
Click to expand...
Click to collapse
According to an other post this should mean that your bootloader is locked but can be unlocked via Sony's code. At the same time I've read in the same post (can't find it) that people with unlocked bootloader still have "bootloader can be unlocked" even if they successfully unlocked it...
Unfortunately I can't try it myself because I'm on RR and the code *#*#7378423#*#* (this should be the code you used) doesn't do anything.
I have the code and have used it previously I have also retried it just to make sure.
When I type the dialer code above I get 'bootloader can be unlocked: yes' but nothing mentioning the actual current state of bootloader.
This is what's leading me to think it's a bootloader glitch because all posts I've seen should say 'bootloader unlocked: yes' or 'bootloader unlocked: no'. I get neither.
Been a few days and had no suggestions. Anyone got any ideas at all outside what I have mentioned? Getting pretty desperate because wifi is really bad on stock, getting constant slowdowns and stalls for no reason. I'm gonna end up trying to sell second hand if I can't do anything.
SabertoothTitan said:
Been a few days and had no suggestions. Anyone got any ideas at all outside what I have mentioned? Getting pretty desperate because wifi is really bad on stock, getting constant slowdowns and stalls for no reason. I'm gonna end up trying to sell second hand if I can't do anything.
Click to expand...
Click to collapse
Sorry, I'm out of ideas
The only thing I can tell you is what I did to my XPZ, but I doubt it may help you:
1) Unlock bootloader using Sony's guide
2) XPZ in fastboot mode → from pc "fastboot flash boot twrp.img" (assuming you have the proper TWRP image named twrp in the same folder of fastboot)
3) flashed RR 5.7.0 and Gapps
4) RR change the rocovery to CMrecovery but I "easily" changed back to twrp using a guide under RR thread.

Categories

Resources