I soft-bricked my ONE MAX after doing the update to Android 4.4.2 (Kitkat) yesterday.
It definitely turns on, but cant get past the htc one logo. Although, prior to that, screen goes green and pink.
Bootloader shows
*** TAMPERED***
*** RELOCKED***
T6UL PVT SHIP S-ON RH
HBOOT-2.46.0000
RADIO-4T.21.3218.01
OpenDSP-v33.120.274_T6.0829
QSC-
OS-1.19.708.2
eMMC-boot 2048MB
Oct 5 2013, 16:14:06.0
FYI, my phone isn't rooted. Although I did try in the past, I've used one click root (Didn't work) and the SUPER TOOL from Kwongger (Also didnt work for me). So I relocked the boot loader, couple of weeks its fine, just after updating to kitkat yesterday when it started happening.
Since its not rooted, I believe that's one of the reasons its not letting me flash a ROM or recovery. It's just saying device not found when using Squabbis kit.
I really need help, please.
Ok, You may follow these steps if your phone is an international version cause the rom in this post is for international version only. You may search the forum for a rom fitting your phone if it is not the international one but the procedures remain the same... ( Please note that my phone was not rooted too).
First of all
Last time I was facing the same problem. A special Thank to Pradeepvizz for his help.
So to install recovery, You need to unlock your bootloader AGAIN cause I also relocked my bootloader and getting the TAMPERED RELOCKED AND S ON. My phone freeze at boot on the HTC Screen.
1. Re - unlock your bootloader using the same unlock.bin file,( fyi, i've done it by htcdev.com), I think your adb and fastboot drivers working fine if you've been able to unlock before.
2. I follow the procedures of punk9 from - One Max Android Development > [Guide] S-OFF / Root.Your HTC One Max. to know how to install a recovery software using cmd prompt.
3. I've used TWRP as recovery (DON'T USE CWM, i'VE GOT MANY ISSUES WITH,and i was not the only one to get issues) downloaded from - One Max Original Android Development > [RECOVERY] TWRP 2.6.3.0 touch recovery posted by Flyhalf205.
4. I've downloaded and install a clean stock rom already rooted with original kernel which i downloaded from One Max Android Development > [ROM] HTC One MAX Stock ROM | ROOT | INTERNATIONAL | DEODEXED |1.54.401.1 posted by pradeepvizz.
5. After the rom successfully installed, reboot, (btw, it took more than 5mins to boot the first time for me, so if you find that it is screw at HTC Screen, be patient...)
After configuration (language setup, wifi connection, google account and so on), I've S-OFF my phone using firewater. PLEASE make sure your phone is connected to internet during the process. I've follow these step to S-OFF my phone: One Max General > Firewater S-OFF posted by pradeepvizz.
After, these procedures I've noticed, when booting in fastboot mode, that the TAMPERED STAMP and S-ON disappeared and change to UNLOCKED and S-OFF.
When I switch my phone on, I get the Red message (watermark) about the disclaimer and you may remove it by following this guide( I did not do it cause the red watermark does not matter to me) : One Max Android Development > ★ ☆ [MOD] Remove Red Text on Splash screen | hboot | Vzw/Spr/Int | 11-30-13 | ☆ ★ posted by santod040..
Althought I've unlocked my bootloader via htcdev, I've noticed that fingerprint sensor working fine but anyway you may search the forum to get the solution for this issue.
Hope It helps.
hellxprexx said:
Ok, You may follow these steps if your phone is an international version cause the rom in this post is for international version only. You may search the forum for a rom fitting your phone if it is not the international one but the procedures remain the same... ( Please note that my phone was not rooted too).
First of all
Last time I was facing the same problem. A special Thank to Pradeepvizz for his help.
So to install recovery, You need to unlock your bootloader AGAIN cause I also relocked my bootloader and getting the TAMPERED RELOCKED AND S ON. My phone freeze at boot on the HTC Screen.
1. Re - unlock your bootloader using the same unlock.bin file,( fyi, i've done it by htcdev.com), I think your adb and fastboot drivers working fine if you've been able to unlock before.
2. I follow the procedures of punk9 from - One Max Android Development > [Guide] S-OFF / Root.Your HTC One Max. to know how to install a recovery software using cmd prompt.
3. I've used TWRP as recovery (DON'T USE CWM, i'VE GOT MANY ISSUES WITH,and i was not the only one to get issues) downloaded from - One Max Original Android Development > [RECOVERY] TWRP 2.6.3.0 touch recovery posted by Flyhalf205.
4. I've downloaded and install a clean stock rom already rooted with original kernel which i downloaded from One Max Android Development > [ROM] HTC One MAX Stock ROM | ROOT | INTERNATIONAL | DEODEXED |1.54.401.1 posted by pradeepvizz.
5. After the rom successfully installed, reboot, (btw, it took more than 5mins to boot the first time for me, so if you find that it is screw at HTC Screen, be patient...)
After configuration (language setup, wifi connection, google account and so on), I've S-OFF my phone using firewater. PLEASE make sure your phone is connected to internet during the process. I've follow these step to S-OFF my phone: One Max General > Firewater S-OFF posted by pradeepvizz.
After, these procedures I've noticed, when booting in fastboot mode, that the TAMPERED STAMP and S-ON disappeared and change to UNLOCKED and S-OFF.
When I switch my phone on, I get the Red message (watermark) about the disclaimer and you may remove it by following this guide( I did not do it cause the red watermark does not matter to me) : One Max Android Development > ★ ☆ [MOD] Remove Red Text on Splash screen | hboot | Vzw/Spr/Int | 11-30-13 | ☆ ★ posted by santod040..
Althought I've unlocked my bootloader via htcdev, I've noticed that fingerprint sensor working fine but anyway you may search the forum to get the solution for this issue.
Hope It helps.
Click to expand...
Click to collapse
Super thanks for taking your time to reply to my post. I tried following this but it's not working. Only thing I can think of is because I was able to do a factory reset, so Im guessing maybe the usb debugging is/was disabled so its saying here that "Device not found". I cant unlock my bootloader anymore
timflores07 said:
Super thanks for taking your time to reply to my post. I tried following this but it's not working. Only thing I can think of is because I was able to do a factory reset, so Im guessing maybe the usb debugging is/was disabled so its saying here that "Device not found". I cant unlock my bootloader anymore
Click to expand...
Click to collapse
Impossible, it has to work.
timflores07 said:
Super thanks for taking your time to reply to my post. I tried following this but it's not working. Only thing I can think of is because I was able to do a factory reset, so Im guessing maybe the usb debugging is/was disabled so its saying here that "Device not found". I cant unlock my bootloader anymore
Click to expand...
Click to collapse
You don't need USB debugging to unlock, make sure your phone shows fastboot USB mode and that should be shown on the phone. You probably are in HBOOT and that is why it says device not found.
timflores07 said:
Super thanks for taking your time to reply to my post. I tried following this but it's not working. Only thing I can think of is because I was able to do a factory reset, so Im guessing maybe the usb debugging is/was disabled so its saying here that "Device not found". I cant unlock my bootloader anymore
Click to expand...
Click to collapse
I'm guessing a problem about your cable or your connection, or adb drivers. Are all the items needed in same folder? in directory c:/ ?? Adb, fastboot drivers and unlock.bin should be in same folder. No need to enable usb debugging when unlocking. it will take place only when flashing the rom or recovery. Did you follow the procedures from htcdev??
I did not give the procedures of unlocking bootloader as htcdev procedures are clear. check your connection, re install adb and fast boot drivers. use another usb port on your pc.
It must work.
I am curious to know how you are trying to install KitKat on a Sprint One Max as HTC has not yet released the update? If you are trying to use the release for the HTC One, that may be your problem. Rooting is fairly simple using HTCDev to unlock the bootloader, Use TWRP 2.6... and SuperSU 1.91. If you will need to be able to install a custom rom (none of which are available for Sprint yet), you will ultimately want S-Off. For this you will need to use the rumrunner tool as your One Max is using Hboot 2.46. Once you're S-Off you will be able to remove your tampered flag and re-lock which will once again enable your fingerprint scanner.
FYI if you were forced to factory reset, you will need to re-enable adb bugging in settings - developer options, AND disable fast boot in settings - power. Then start over from scratch.
hellxprexx said:
I'm guessing a problem about your cable or your connection, or adb drivers. Are all the items needed in same folder? in directory c:/ ?? Adb, fastboot drivers and unlock.bin should be in same folder. No need to enable usb debugging when unlocking. it will take place only when flashing the rom or recovery. Did you follow the procedures from htcdev??
I did not give the procedures of unlocking bootloader as htcdev procedures are clear. check your connection, re install adb and fast boot drivers. use another usb port on your pc.
It must work.
Click to expand...
Click to collapse
Bro, thanks I finally got it working. My girlfriend was actually the one who worked with it, followed your guide and other people's. Apparently, my htc drivers weren't updated thats why it wasnt working on my laptop. Again, thanks to the people that took their time to provide some help.
neodiver said:
I am curious to know how you are trying to install KitKat on a Sprint One Max as HTC has not yet released the update? If you are trying to use the release for the HTC One, that may be your problem. Rooting is fairly simple using HTCDev to unlock the bootloader, Use TWRP 2.6... and SuperSU 1.91. If you will need to be able to install a custom rom (none of which are available for Sprint yet), you will ultimately want S-Off. For this you will need to use the rumrunner tool as your One Max is using Hboot 2.46. Once you're S-Off you will be able to remove your tampered flag and re-lock which will once again enable your fingerprint scanner.
FYI if you were forced to factory reset, you will need to re-enable adb bugging in settings - developer options, AND disable fast boot in settings - power. Then start over from scratch.
Click to expand...
Click to collapse
I did it while checking for updates. Here's a screenie
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
andrdnl said:
Impossible, it has to work.
Click to expand...
Click to collapse
It's good to see "CONFIDENCE". Makes people try harder and more careful to follow instructions.
It's not confidence, it's based on some experince
Sent from my HTC One max using Tapatalk
andrdnl said:
It's not confidence, it's based on some experince
Sent from my HTC One max using Tapatalk
Click to expand...
Click to collapse
Best teacher is experience
timflores07 said:
Bro, thanks I finally got it working. My girlfriend was actually the one who worked with it, followed your guide and other people's. Apparently, my htc drivers weren't updated thats why it wasnt working on my laptop. Again, thanks to the people that took their time to provide some help.
Click to expand...
Click to collapse
Happy it helps bro!
HTC one max need help
andrdnl said:
Impossible, it has to work.
Click to expand...
Click to collapse
will it work for me
***TAMPERED***
***UNLOCKED***
T6WHL PVT SHIP S-ON
H-BOOT-2. 49 . 0000
RADIO 1.48.50.0425
OPENDSP-v33.120.274_T6.0829
QSC-
OS-3.02.651.5
eMMC-boot 2048MB
Apr 28 2014 15:06: 18.0
guys just pm me I know how to fix bricked phone Specially HTC one max....
guys just pm me I know how to fix bricked phone Specially HTC one max....
BootLoad Freezes
Hello.
I'm sorry I don't speak English very well. I'm French.
I have a HTC One max of origin Stock (no hack)
Overnight my phone will not start.
So I started by "Volume -" + "On"
The bootload load.
But if I chosen any choice FASTBOOT / RECOVERY / FACTORY REST Etc ...
The phone freezes.
If I stay pressed the power button restarts (HTC Green Screen make WHITE) but after black screen.
Black on the screen my computer detects a device: QHSUSB_DLOAD
I found lots of tutorial but for phone S-OFF or UNLOCKED while my phone is:
LOCKED
T6UL PVT SHIP ON S-HR
HBOOT-2.49.0000
RADIO 4T.36.3218.06
OpenDSP-v33.120.274_T6.0829
I have no ADB is housed and no USB debugging mode when the phone was working.
Can you help me...? :angel:
thank you in advance
Hello guys.
I need help. My device (T6UL) is bricked. Windows detect it how HS-USB QDLoader 9008. To unbrick him, I need full eMMc dump (/dev/block/mmcblk0).
Anybody can do it?
Sorry for my English, i am from Russia.
Hi all of a sudden after years of trouble free and non interfered with use just this morning my HTC One Max 803s will simply NOT switch on...it is fully charged and nothing that I do will get even a glimmer of life on the screen...the tiny green LED in the top left hand corner, which usually indicates a fully charged phone, is on permanently...I have taken out the SD card and SIM and replaced them as this was all that I could think of doing...HELP and HELP again...any ideas anyone???...thanx in advance for all your help...kind regards dizzy
dizzyblond said:
Hi all of a sudden after years of trouble free and non interfered with use just this morning my HTC One Max 803s will simply NOT switch on...it is fully charged and nothing that I do will get even a glimmer of life on the screen...the tiny green LED in the top left hand corner, which usually indicates a fully charged phone, is on permanently...I have taken out the SD card and SIM and replaced them as this was all that I could think of doing...HELP and HELP again...any ideas anyone???...thanx in advance for all your help...kind regards dizzy
Click to expand...
Click to collapse
Are you able to reboot into recovery mode via TWRP ?
Related
Dear All,
I rooted my htc one max and now the fingerprint scanner is not working. Whenever I try to register my fingerprint, it shows ' X ' mark.
can someone please help me out to fix this issue.
Thanks in advance
sumitvrma said:
Dear All,
I rooted my htc one max and now the fingerprint scanner is not working. Whenever I try to register my fingerprint, it shows ' X ' mark.
can someone please help me out to fix this issue.
Thanks in advance
Click to expand...
Click to collapse
Hey man,
U miss one thing about our max fingerprint. You need to lock bootloader for the fingerprint function.
Take a ride here bro, http://forum.xda-developers.com/showthread.php?t=2540004
Dear sir,
thanks a lot for your quick reply, sadly I couldnt achieve s-off so I cannot lock back the bootloader but when I relock, phone fails to boot the rom.
sumitvrma said:
Dear sir,
thanks a lot for your quick reply, sadly I couldnt achieve s-off so I cannot lock back the bootloader but when I relock, phone fails to boot the rom.
Click to expand...
Click to collapse
No big deal, 4:36am still awake. lol.
Relocking bootloader using fastboot oem lock ?
Then bootloop or what?
Try wipe dalvik and cache.
Which variant your max? If hboot 2.49.000 you can use http://firewater-soff.com/instructions/ to get s-off. Then proceed lock/unlock your bootloader without htcdev(s-off required)
yes sir, re-locking thru oem lock.
it stays on bootloader, doesnt even go to recovery after that.
I unlocked it again to make the phone work again.
phone is on HBOOT 2.49
tried firewater and this is what happens
"
Do you understand the implications of these warnings?
(Yes/No)
Yes
Yes
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, ho
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, ho
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, ho
ld power for 60 seconds !!
=========================================================================
preparing, one moment
The first bottle is open
chugging..........
E:\sdk\platform-tools>
"
but it still says s-on
too late sir, you should better sleep
Finally done, tried this method
http://forum.xda-developers.com/showthread.php?t=2765383
without rom
Did you perform each and every step?
sumitvrma said:
Finally done, tried this method
http://forum.xda-developers.com/showthread.php?t=2765383
without rom
Click to expand...
Click to collapse
For that method where did you get HTC ONE 1.19.401.2 rom odex?
I am in the same boat. I am s-on and still stays tempered
Alright guys, Ive been trying to fix my friends DNA i guess from what he said is that he had a system update happen on his phone and it would just stay on the "HTC Quite Brilliant" Page. I tried a factory reset, and that didn't do anything, I went into recovery to wipe cache partition. I also tried wipe data/factory reset from recovery as well as hboot. so i got adb and i plugged the phone in while on fastboot. "adb devices" Shows nothing its just blank underneath the listed devices. So i figured that the drivers wont install i installed htc sync manager as advertised has the supporting drivers. Htc sync manager reads the device but doesn't say its a DNA it just says that its rom number. I tried to go to fastboot and put a previous dated RUU on but it had a error and just couldn't do anything with the phone. So now i went into the recovery and behind the menu screen it says "updating software from verizon wireless" but theres a issue with that is that the sim card in it isnt activated anymore so theres no data going to that phone if it is updating and if it downloaded the os to the phone it should be wiped since i did a factory reset 3 times and wiped cache 3 times as well.
So What i think is wrong is that:
I need usb Debugging on
S is on
Drivers wont install properly
I may need a active sim card to pass the updating?
MoNARUDO PVT S-ON RH
HBOOT-1.57.0000
Radio-1.01.01.1112
OpenDSP-v10.120.274.0520
OS-4.09.605.1
eMMC-boot 2048MB
Mar 13 2014, 19:19:14.0
I really hope that you guys can help me out thank you!
HTVdev
I tried to unlock the device to see if this would help out and i got it connected and i went and i got the token for the device and went to get the tocken and it came back with a error code
Error Code: 160.
Error Reason: MID Not Allowed.
Can someone please help me out here?
I was missing android sdk and i installed android sdk, and my device will read in adb but when i got to flash a udate it will read signature error. but im not using the word update im using "fastboot flash hboot hboot.img" and so forth and its not working i still cant get the hboot to unlock. please help me figure out if its possible to fix this phone im really determined to fix it and i need alittle bit of help.
Unfortunately, unless you can boot into the ROM, you cannot unlock this phone. I suggest contacting HTC support and let them know the update soft bricked the device and since you cannot unlock it, you need their help in getting it to boot again. HTC is very good when it comes to support, even for phones that are out of warranty. Support staff have been instructed to fix any m7 even if out of warranty period for the camera issue (talked to a rep personally on this issue today when making small talk). I am sure if their update borked your phone and it hasn't been tampered, they will fix it free of charge. What's the worse they can say, no?
Sent from my One using XDA Free mobile app
I contacted there support 2 times on the phone and once trying to live chat and i got hung up on twice.. so im at loss here
Im really not happy with htc they cant tell me anything to any cause to why there update would cause the softbrick on the phone itself did anyone else have a issue with 4.09 update bricking your phone?? and did anyone find a solution for it?
Hello all,
I'm a little desparate with an error that occurred some time ago. My HTC One was updated and suddenly was encrypted.
Factory reset is not working and Recovery option is not working as well.
What I've done so far, after several forum messages:
1. I tried to execute the HTC dev (unlock_code.bin) hint in a way to unlock the bootloader, but with no success at all. I always get the "*** LOCKED ***" (S-ON) option enabled. Then, I saw a lot of messages in foruns regarding the HBOOT version 1.55 that is installed in my device. It seems that with this version, it's not possible to change the configuration to S-OFF.
2. No fastboot commands work, including all the flash writing options. All of them with signature failures. Again in this case it seems to be a issue related to S-ON/S-OFF.
3. I couldn't run the cellphone in USB debugging (after the boot, I'm presented with the infamous: "type password to decrypt storage", which obviously I don't have the password).
4. Runrunner didn't work.
At this very moment my device is a paperweight... Does anybody have another idea about what could be done in this case?
All my problems seem to be focused on my inability to change the option S-ON to S-OFF.
Any help is very appreciated!
Paulo
Hey guys,
This one really has me stumped and I need some help. I have 5 Xiaomi Redmi Note 3 Pros - we're starting to use these at work. I bought two first to trial with, and they worked awesome on CM, and it was easy to unofficially unlock. I used this method. The next batch simply won't work with exactly the same process. I flash the device with 7.1.8.0 Global and the modified bootloader and whilst the flashing process goes OK, the device does not boot into MIUI afterwards. It flashes the MI logo twice, then shuts off. Plugging in the PC results in a blinking red light. Fastboot works, and I have been using that to reboot to EDL mode to try and fix it, but that's about it. Soft bricked.
So far I've tried both the original unofficial bootloader and the updated one from here and they both result in exactly the same behavior, both on Global ROM 7.1.8.0 and 7.3.6.0. Omitting this modified bootloader will result in the system being bootable on stock MIUI, but that's not what I want.
If I boot into fastboot and try to unlock the bootloader I get the following error: "FAILED (remote: oem unlock is not allowed)".
Has Xiaomi blocked unofficial unlocking or modified bootloaders via a hardware update? It's the only thing I can think of since I have two Xiaomi Redmi Note 3 Pros that worked flawlessly with this method (although I suspect they were slightly older stock). Is there any way around this? I have another 13 phones on the way and I don't really want to make 15 Mi accounts to unlock officially.
Why can't you unlock different phones on the same account?
razr96 said:
Why can't you unlock different phones on the same account?
Click to expand...
Click to collapse
Last time I checked it was one phone per month per account. Also, it takes ages, and doesn't always work (but neither does the unofficial unlock as I'm now discovering).
stephendt0 said:
Last time I checked it was one phone per month per account. Also, it takes ages, and doesn't always work (but neither does the unofficial unlock as I'm now discovering).
Click to expand...
Click to collapse
Well i can unlock an unlimited number of times on my account.
This is news to me... I'll try that then. Last time I tried official unlock it got to 50% and froze, so that's why I was trying to do the unofficial unlock. It also takes ages to get the code.
I'd still like to be able to unlock unofficially though.
stephendt0 said:
Hey guys,
If I boot into fastboot and try to unlock the bootloader I get the following error: "FAILED (remote: oem unlock is not allowed)".
Click to expand...
Click to collapse
I'm having the exact same issue!
I also tried to switch between stable MiFlash and XiaoMi Flash beta.
Yeah its really frustrating. I love these phones, but the bootloader unlock process is pure hell.
I found the solution:
Boot into a working ROM (e.g. 7.1.8 global)
1) Enabled Developer options
2) enable USB debugging
3) enable OEM unlocking (how could I miss this!?!)
After that you can flash the modified fastboot rom and unlock the bootloader.
Voila
I'll test this later and report back. I have a sneaky feeling it might not work...
Alright, an update.
Just before I went to do the unofficial unlock, I got a confirmation code saying that I am able to unlock officially. I tried this on one of my phones (China Dev ROM) and it worked great. I went to do the second one, and I got presented with this error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Damn.
I then tried what you mentioned. Flashed stock 7.1.8.0, enable OEM unlock (it was enabled when I enabled dev options anyway...) and then rebooted to fastboot. I then tried to flash the emmc_appsboot.mbn file from fastboot... no luck. I get "FAILED (remote: device is locked. Cannot flash images)", which is no surprise since the device still has a locked bootlaoder. I then thought alright, well I have the ROM installed with OEM unlock enabled, lets try booting to EDL mode and flashing the ROM with the modified bootloader but without wiping data. I did that, and no luck - just flashes the Mi Logo twice and shuts off. Gah! There's something special about these phones. They must be running a new hardware revision that prevents modified bootloaders from being installed. The only way I can think of unlocking a bunch of phones is to create a heap of different Xiaomi accounts and use the official unlock method, but that is a major hassle!! Really frustrated about this situation. Anyone able to offer some insight?
stephendt0 said:
Alright, an update.
Just before I went to do the unofficial unlock, I got a confirmation code saying that I am able to unlock officially. I tried this on one of my phones (China Dev ROM) and it worked great. I went to do the second one, and I got presented with this error:
Damn.
I then tried what you mentioned. Flashed stock 7.1.8.0, enable OEM unlock (it was enabled when I enabled dev options anyway...) and then rebooted to fastboot. I then tried to flash the emmc_appsboot.mbn file from fastboot... no luck. I get "FAILED (remote: device is locked. Cannot flash images)", which is no surprise since the device still has a locked bootlaoder. I then thought alright, well I have the ROM installed with OEM unlock enabled, lets try booting to EDL mode and flashing the ROM with the modified bootloader but without wiping data. I did that, and no luck - just flashes the Mi Logo twice and shuts off. Gah! There's something special about these phones. They must be running a new hardware revision that prevents modified bootloaders from being installed. The only way I can think of unlocking a bunch of phones is to create a heap of different Xiaomi accounts and use the official unlock method, but that is a major hassle!! Really frustrated about this situation. Anyone able to offer some insight?
Click to expand...
Click to collapse
Hey, after you enabled OEM unlock in the options reboot to edl and flash the ROM with the modified emmc_appsboot.mbn. After its done reboot to fastboot (Power & Vol Down) and perform "fastboot oem unlock-go". Sorry that my instructions were not clear enough.
cetchmoh said:
Hey, after you enabled OEM unlock in the options reboot to edl and flash the ROM with the modified emmc_appsboot.mbn. After its done reboot to fastboot (Power & Vol Down) and perform "fastboot oem unlock-go". Sorry that my instructions were not clear enough.
Click to expand...
Click to collapse
I don't see why that would work. I'll give it a try tomorrow anyway... have you had this exact issue before? I haven't seen it mentioned before, I did a lot of Googling before I made this thread.
stephendt0 said:
I don't see why that would work. I'll give it a try tomorrow anyway... have you had this exact issue before? I haven't seen it mentioned before, I did a lot of Googling before I made this thread.
Click to expand...
Click to collapse
The setting to "enable OEM unlock" is stored somewhere where MiFlash doesn't write during flashing.
If it is not enabled you get the error described in your first post (FAILED remote: unlock is not allowed).
You still need to edl flash the modified bootloader to unlock. Good luck
IT WORKED.
Oh my gosh. I could have sworn the "enable OEM unlock" option was active the entire time I was trying to unlock the bootloader, but nope. I must have forgot the first time around. The guide doesn't mention that this is necessary, although the screenshot indicates that it was enabled for them. It must have been turned on by default on some phones and turned off on some other phones. That must have been it. For some reason I also thought the system would be able to boot up with the modified locked bootloader, so I thought there was a problem there when it turned itself off.
In the end it was really simple:
Boot into stock ROM, enable "Enable OEM Unlock"
Reboot to EDL mode.
Flash ROM with modified bootloader
Reboot to fastboot
Unlock bootloader
Alright, consider it solved. And I feel like a massive idiot. Thanks! At least if someone else has issues with this they can at least know now that it was something silly :silly:
Hey,
What was causing the problem? Im trying to unlock bootloader from couple of days and I have no idea what to do now. I checked dev settings and enable OEM unlock every time when im trying to flash ROM with modified bootloader and every time: (FAILED remote: unlock is not allowed).
Do all in 64 bit windows then go to advance option n select raw and patch then it will work
Not works on marshmallow works on lollipop
Disclaimer: I hope you don't break your phone, but if you do, it's not my fault. Since you are choosing to modify your phone, you accept full responsibility for whatever happens to it, including any damage that may have occurred as a result of incorrectly flashing your device.
Hey guys, similar to all of @Some_Random_Username's unbrick threads, here are the EDL packages (also known as MSM tools or unbrick tools) that can revive a bricked OnePlus Nord N200 5G.
Important: This is only for the T-Mobile variant of the N200. This will not work on the factory unlocked variant and may or may not work for the Metro variant.
Downloads:
11.0.1.5.DE18CB
Original archive
Google Drive
7z format (thanks @edale1)
AnddoidFileHost
MEGA
zip format (thanks @nv270)
Rethink Files
Also available at https://onepluscommunityserver.com/
Instructions:
Launch MsmDownloadTool V4.0.exe.
On the login prompt select "Others" in the dropdown menu and click on Next.
Wait a few seconds until main window shows up.
Press Start button so that it waits for your device to be connected
Power off your device
Press and hold the volume up and down buttons to get into Qualcomm EDL mode.
Plug your device to your computer.
Should you not manage to do that and have adb access, you can use adb reboot edl instead
Wait ~300 seconds.
Enjoy your brand new device.
FAQ:
Does this work on Mac or on Linux?
Unfortunately no, tool is Windows only. You should need at least Windows 7.
Why is my antivirus freaking out when unzipping the archive or running the tool?
In an effort to protect reverse engineering from being done (and by extension prevent conversion process like it was done on 6T and 7Pro), OnePlus now use VM Protect V3 in their MSM tools. As this tries to detect debug environment, this is seen as malicious behaviour by some antivirus.
How can I check my device project ID?
Use getprop ro.boot.project_name. This however involve having ADB access or access to OxygenOS to use Termux or whatever terminal emulator you prefer.
My device isn't detected
Go to device manager and make sure your phone shows up as QDLOADER 9008.
If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed automatically by Windows Update. Download the latest one from Microsoft website at http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab (source https://www.catalog.update.microsof...updateid=8ee52ba0-bdef-4009-88cf-335a678dd67a ) and install it manually by right clicking on QHUSB_BULK and selecting "Update driver software" and "Browse my computer for driver software" to where you downloaded CAB file.
If you can't get into EDL mode by hardware keys, you may use adb reboot edl (will require your phone to still have ADB access)
MSM tool is stuck on "Param pre-processing"
Ensure you're using the Qualcomm drivers linked above.
MSM tool is stuck on "Sahara communication failed"
Unplug your phone, get in fastboot mode, turn off phone, wait 15 secondes and get back in Qualcomm EDL mode. You can also try using a USB 2.0 port instead of a 3.0 one.
What is SMT Download mode?
Just don't try to unlock that mode, it will wipe your IMEI and your Widevine certificate if you use it.
How can I fix "SMT config not found" error?
Please refer to https://forum.xda-developers.com/showpost.php?p=83448961&postcount=61
Credits:
@Some_Random_Username for help getting files and for the mirror
@edale1 and @nv270 for repacking and mirroring the files
@nache2001 for testing the tool out on his device
OnePlus for the device and OS
@Nache and others who have the unlocked version from the oneplus store and have the bootloader locked and phone bricked .. This version will not work with your phone as i just tried it myself today .. hopefully someone gets a hold of the msmdowmload from the tech support ..
patiently waiting for the unlock
So just to confirm: For those of us with Tmobile version, this will install default rom from OnePlus and get rid of all the bloatware from Tmobile and technically make our devices be like they are originally purchased from OP?
And of course, in order to use this our bootloader needs to be unlocked?
Will this lock bootloader again?
And do we unlock it with same code we got from OP first time?
Thanks!
xentonix said:
So just to confirm: For those of us with Tmobile version, this will install default rom from OnePlus and get rid of all the bloatware from Tmobile and technically make our devices be like they are originally purchased from OP?
And of course, in order to use this our bootloader needs to be unlocked?
Will this lock bootloader again?
And do we unlock it with same code we got from OP first time?
Thanks!
Click to expand...
Click to collapse
My understanding is the T-Mobile MSM Tools will restore a T-Mobile variant phone to the state it was in coming from T-Mobile; meaning if you debloated the phone, the bloat will be back.
You can use the MSM Tools even with a locked bootloader.
If your bootloader is unlocked, I believe this will lock it. (it may SIM lock your phone again as well, unsure...)
I think the same unlock token will work, but I'm hesitant to say 'yes' without someone testing it first.
xentonix said:
So just to confirm: For those of us with Tmobile version, this will install default rom from OnePlus and get rid of all the bloatware from Tmobile and technically make our devices be like they are originally purchased from OP?
And of course, in order to use this our bootloader needs to be unlocked?
Will this lock bootloader again?
And do we unlock it with same code we got from OP first time?
Thanks!
Click to expand...
Click to collapse
1. Nope, this will revert your device back to the T-Mobile stock ROM, including all the bloatware. Thsi does not convert your device into an unlocked variant.
2. This works whether your bootloader is locked or unlocked. If your bootloader is unlocked, using this tool will lock it again, and you will need to unlock it by flashing unlock_code.bin again.
edale1 said:
My understanding is the T-Mobile MSM Tools will restore a T-Mobile variant phone to the state it was in coming from T-Mobile; meaning if you debloated the phone, the bloat will be back.
You can use the MSM Tools even with a locked bootloader.
If your bootloader is unlocked, I believe this will lock it. (it may SIM lock your phone again as well, unsure...)
I think the same unlock token will work, but I'm hesitant to say 'yes' without someone testing it first.
Click to expand...
Click to collapse
lzgmc said:
1. Nope, this will revert your device back to the T-Mobile stock ROM, including all the bloatware. Thsi does not convert your device into an unlocked variant.
2. This works whether your bootloader is locked or unlocked. If your bootloader is unlocked, using this tool will lock it again, and you will need to unlock it by flashing unlock_code.bin again.
Click to expand...
Click to collapse
Thank you!
I read an article that was bit unclear and pointed to this so I wanted to confirm.
Also, from everything else I gathered, there is still no way to flash Tmob variant with non Tmob rom?
I was interested to try LineageOS but that's not available also seems like.
Phone's too new still. I think we need the MSM Tools for all the variants available before someone can figure out how to flash one variant into another, and we currently only have the T-Mobile variant's MSM Tools.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
incoming August 176 patch
I have update installed.
You can use restore image on Magisk uninstall before you start. If you encounter problem, you can use original boot image and run "mock patch"
Install update and switch to Magisk when you're prompted to restart, and let Magisk to install in unused partition, and restart after finished
If you have problem with CTS after update, install riru from Magisk and download safetynet fix, and install in Magisk as well (you have to reboot twice)
I've successful restored my N200 phone several times using the MSM, but this most recent time it appears the process was interrupted and I get the following error when turning on the phone. I can not boot the phone back into EDL mode to run MSM tool again. Every 10 or so boots the phone will boot into fastboot instead of throwing the error. I tried flashing a backed up boot.img and super.img, but no luck getting past the error. Any way to recover?
automatic ddr failed
Thank you! I could only get this to work by:
Unplug phone
Open MSMDownloadTool, don't click start
Hold down volume up and down
Plug phone into USB 2.0 port
Release volume up and down, verify device shows up as QDLOADER in Device Manager
Click "Enum" in MSMDownloadTool
Click on the device in the list and click "Start"
I got bootloader unlock code. I need SIM unlock "One Plus Nord N200 5G" by Metro. Help me!
towardsdawn said:
Thank you! I could only get this to work by:
Unplug phone
Open MSMDownloadTool, don't click start
Hold down volume up and down
Plug phone into USB 2.0 port
Release volume up and down, verify device shows up as QDLOADER in Device Manager
Click "Enum" in MSMDownloadTool
Click on the device in the list and click "Start"
Click to expand...
Click to collapse
I bricked my phone late last night and found this forum & thread; my problem was that each time my computer kept showing my phone as "Kedacom" until I scrolled through and found this post.
You guys saved my ass AND saved me a trip to T-Mobile too! I owe you guys big time!
I successfully flashed a metro-pcs device using the tool in this thread. I bricked my device using the dsu loader in developer options. "Oem unlocking" is greyed out. Can anyone point me to a good bootloader unlocking tutorial for this devicel? Is it possible to use this tool with a rom that has already been rooted? Thanks,
Noob here. One thing to note: device was not recognized in the beginning. I held vol up/down at the same time and then plugged in device. Although the screen was black, the device was shown as "connected" and had no issues flashing. After 300 secs, voila!
bleezycheesy said:
I successfully flashed a metro-pcs device using the tool in this thread. I bricked my device using the dsu loader in developer options. "Oem unlocking" is greyed out. Can anyone point me to a good bootloader unlocking tutorial for this devicel? Is it possible to use this tool with a rom that has already been rooted? Thanks,
Noob here. One thing to note: device was not recognized in the beginning. I held vol up/down at the same time and then plugged in device. Although the screen was black, the device was shown as "connected" and had no issues flashing. After 300 secs, voila!
Click to expand...
Click to collapse
You can try this tutorial. It worked for me on Tmobile, no idea about MetroPCS. Key line is
Code:
adb shell pm uninstall --user 0 com.qualcomm.qti.uim
MSMDownloadTool wipes the entire device and relocks the bootloader if it was unlocked, it doesn't care if you're rooted.
towardsdawn said:
You can try this tutorial. It worked for me on Tmobile, no idea about MetroPCS. Key line is
Code:
adb shell pm uninstall --user 0 com.qualcomm.qti.uim
MSMDownloadTool wipes the entire device and relocks the bootloader if it was unlocked, it doesn't care if you're rooted.
Click to expand...
Click to collapse
Thanks for the reference. It worked!
why no have msm tool for global n200 be2117,
jasmok said:
why no have msm tool for global n200 be2117,
Click to expand...
Click to collapse
OnePlus doesn't seem to want to release it.
bleezycheesy said:
Thanks for the reference. It worked!
Click to expand...
Click to collapse
no it doesn't works on metro variant