Help! Rooted, Now No Fingerprint Scanner - HTC One Max

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

Related

Can I get some help

So I got my replacement from Sprint after bricking my phone by downgrading from s-off..
Now I tried to brick this one and seems like it turned off before I disconected and now I can't boot it up, and the downgrade tool won't detect it, I get a dim blinking red light.
Also when I try to boot up the phone it boots into the bootloader and it says Locked and under it it says security warning, what do I have to do?
Help please :/
Do I just re-do it?
anyone?
Run the ruu.
Check the sticky on how to get back to stock
Sent from my PG86100 using Tapatalk
RUU and redo.
oohaylima said:
RUU and redo.
Click to expand...
Click to collapse
Yeah.
Or wait. Unlock your phone?
The reason it shows security warning is because you probably flashed something then locked your phone. thats what happens to me after locking my phone.
But now why would you try to downgrade after you bricked your phone. haha
iTzLOLtrain said:
Yeah.
Or wait. Unlock your phone?
The reason it shows security warning is because you probably flashed something then locked your phone. thats what happens to me after locking my phone.
But now why would you try to downgrade after you bricked your phone. haha
Click to expand...
Click to collapse
Your right but you don't need to unlock it again. Just run the 2.17 ruu exe through the bootloader and when your phone is hooked to the computer check in your device manager menu ( if you have windows) to make sure you have your drivers. It should say My HTC or adb android.
fourthhorseman said:
Your right but you don't need to unlock it again. Just run the 2.17 ruu exe through the bootloader and when your phone is hooked to the computer check in your device manager menu ( if you have windows) to make sure you have your drivers. It should say My HTC or adb android.
Click to expand...
Click to collapse
Correct me if I'm wrong. But if he unlocks his phone it should be able to boot up and not show security warning. Also you need to run ruu while your phone is on fasboot USB if not your phone will just reboot
Sent from my PG86100 using Tapatalk
I got past this already, the problem is phone didn't brick, after 4~ hrs of trying to get it to brick I got it, and everything went smooth after that even revolutionary got done in the first try until..
I got to MeanRom and couldn't receive texts or calls, and I got error code 16
marioca said:
I got past this already, the problem is phone didn't brick, after 4~ hrs of trying to get it to brick I got it, and everything went smooth after that even revolutionary got done in the first try until..
I got to MeanRom and couldn't receive texts or calls, and I got error code 16
Click to expand...
Click to collapse
"1. Go to data menu; enter ##3282# on the dialpad.
2. Click on "Edit Mode" on the menu that appears.
3. Enter your MSL # and hit "OK"
4. Choose "Data Profile" from the listed options.
5. Press your menu button on the phone and select "Restore" from the menu that appears. Then hit "OK.
6. Phone should reboot. Once it's back up, wait for it to start hands-free activation. Once this is complete you should be good as new!"
If that doesn't work just call Sprint and tell them you are getting the Error 16 message and they will get you back going. Happened to me months ago after using revolutionary and the phone call took less than 5 minutes.
Edit: If you don't know your MSL number you can get a free app off the Play Store named MSL Reader that will find it for you.
iTzLOLtrain said:
Correct me if I'm wrong. But if he unlocks his phone it should be able to boot up and not show security warning. Also you need to run ruu while your phone is on fasboot USB if not your phone will just reboot
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Your right, if he unlocks it it will allow him back into his ROM. I was just saying it wasn't nessasary to have to unlock again. When I was unrooting my phone to work on the down grade all I did was lock the phone and run the straight stock ruu 2.17 through the fastboot from my PC and every thing cleared up. You just need the drivers installed minus HTC sync
Sent from my PG86100 using XDA

I think i brick my evo help

Ok guys I just move to Pennsylvania from Florida a few days ago and i was having problems with my data connection so i decided to call sprint and spend about an hr on the phone with costumer service try everything to restart my service and get better data, but nothing work so she tell me my last option was to take it back to sprint, so I decided to relock and to run the RRU, so i did the relocked on fastboot comand window and the phone restart to fasboot and now says ***relocked*** and under it it says ***security warning*** I try everything (rebbot, factory reset, power of ect.) all the the phone does is restart to splash screen and go back to fastboot plz i need help asap, thanks.
prboy25 said:
Ok guys I just move to Pennsylvania from Florida a few days ago and i was having problems with my data connection so i decided to call sprint and spend about an hr on the phone with costumer service try everything to restart my service and get better data, but nothing work so she tell me my last option was to take it back to sprint, so I decided to relock and to run the RRU, so i did the relocked on fastboot comand window and the phone restart to fasboot and now says ***relocked*** and under it it says ***security warning*** I try everything (rebbot, factory reset, power of ect.) all the the phone does is restart to splash screen and go back to fastboot plz i need help asap, thanks.
Click to expand...
Click to collapse
Nothing to worry about. Please read my previous reply to a similar problem. Remember: if the phone does something it is not a brick, and since it is Android it can be fixed. So cheer up!!!
Are you working off the latest Jewel RUU here:
http://forum.xda-developers.com/showthread.php?t=1655733
Here all available RUU for Jewel
http://www.filefactory.com/f/b6eb73c80cc97030/
How to unroot/unbrick device video: (Thanks to qbking77)
If you have unlocked device, you should lock it first with command fastboot oem lock, otherwise you won't be able to install RUU.
http://www.youtube.com/watch?v=NChdbyaHy3k
georgikol said:
Nothing to worry about. Please read my previous reply to a similar problem. Remember: if the phone does something it is not a brick, and since it is Android it can be fixed. So cheer up!!!
Click to expand...
Click to collapse
thanks try to run the RRU one more time and it works

One Max soft brick, need help

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 ?

Kenzo Error Fix {Failed (remote: token verification failed, reboot the device)}.

Can any developer please please help me out quickly? i'm out of time seriously I need help but quick.
I'm trying to unlock my device Redmi Note 3 Snapdragon varient. All the other commands like
* adb devices
* adb reboot edl
* fastboot devices
* fastboot oem device-info
everyone of it is working fine but when I write
* fastboot oem unlock-go
I get the above mentioned error.
Does anybody know the solution to it? Before answering please consider that other commands are working except this one, I didn't found any proper solution that's why posted the problem here and I already did revoke USB debugging permissions and turned it on again but that didn't helped.
So please give me a working solution as quick as possible or else any help is appreciable.
enable oem unlock in developer options
Enable OEM Unlock option in Developer Options.
caesar13th said:
enable oem unlock in developer options
Click to expand...
Click to collapse
It's already enabled, I don't know what's causing the problem. Please help me with another solution. Ask everything at once, I will answer. But I really need a solution.
superboy123 said:
Enable OEM Unlock option in Developer Options.
Click to expand...
Click to collapse
It's already enabled, I don't know what's causing the problem. Please help me with another solution. Ask everything at once, I will answer. But I really need a solution.
Gurkirat_Singh said:
It's already enabled, I don't know what's causing the problem. Please help me with another solution. Ask everything at once, I will answer. But I really need a solution.
Click to expand...
Click to collapse
That fastboot oem unlock-go command won't work.
OK, follow these steps:-
a) Reboot to Fastboot mode by pressing Power and Vol down buttons for 10 seconds.
b) Download the MiUnlock tool and enter your credentials first. It will check whether your Mi account has permission to unlock (you must have permission from Xiaomi to unlock).
c) It will detect your phone as Mi Phone and proceed to unlock.
d) It will verify whether the Mi account in your phone and the credentials of the Mi account you entered on the PC are the same.
e) It will unlock your device for sure!
If it says some sort of verification error aka. the famous stuck at 50%, wait for some days like for a week and try again, it may work even in 2 days! Keep trying!
Good Luck!:good::highfive:
Thank you!
superboy123 said:
That fastboot oem unlock-go command won't work.
OK, follow these steps:-
a) Reboot to Fastboot mode by pressing Power and Vol down buttons for 10 seconds.
b) Download the MiUnlock tool and enter your credentials first. It will check whether your Mi account has permission to unlock (you must have permission from Xiaomi to unlock).
c) It will detect your phone as Mi Phone and proceed to unlock.
d) It will verify whether the Mi account in your phone and the credentials of the Mi account you entered on the PC are the same.
e) It will unlock your device for sure!
If it says some sort of verification error aka. the famous stuck at 50%, wait for some days like for a week and try again, it may work even in 2 days! Keep trying!
Good Luck!:good::highfive:
Thank you!
Click to expand...
Click to collapse
Thanks for the help but I don't even want to try that method first it's very problematic, it takes a lot of time and it's not even sure if it works. So if you can help me with the problem I'm having that would very very very appreciable :good:.
And why the command will not work, can you please tell me? Also this command gives the same error "fastboot OEM unlock bootloader". Hope you can help .
Gurkirat_Singh said:
Thanks for the help but I don't even want to try that method first it's very problematic, it takes a lot of time and it's not even sure if it works. So if you can help me with the problem I'm having that would very very very appreciable :good:.
And why the command will not work, can you please tell me? Also this command gives the same error "fastboot OEM unlock bootloader". Hope you can help .
Click to expand...
Click to collapse
It's not that problematic, actually it is the easiest way to unlock bootloader!
Unofficial bootloader is the very "problematic" method.
Anyhow, Are you looking for unofficial bootloader unlock? Then go here and follow the steps correctly, dont skip any step.
And for your second question, Xiaomi has complicated the bootloader unlock process by heavy encryption. That's why you couldn't unlock Redmi Note 3 as any Moto device!
superboy123 said:
It's not that problematic, actually it is the easiest way to unlock bootloader!
Unofficial bootloader is the very "problematic" method.
Anyhow, Are you looking for unofficial bootloader unlock? Then go here and follow the steps correctly, dont skip any step.
And for your second question, Xiaomi has complicated the bootloader unlock process by heavy encryption. That's why you couldn't unlock Redmi Note 3 as any Moto device!
Click to expand...
Click to collapse
OK that's why I'm having so much problem to unlock it. I just want to ask do you know any other way to fix the problem I'm having with this error. Cause the post you gave me tells how to unlock the RN3 temporary :crying: but the thread I followed helps to unlock it permanently :good: (how I know cause I used similar commands on my Canvas A1) and I followed almost every step properly.
I don't understand why companies emerged as custom ROMs stops supporting customisation, at least don't make it hard. I just wanted to flash my RN3 with a Custom ROM like CM13 cause MIUI is not supporting 4G networks properly of multiple operators that's why, for which I needed a custom recovery and for which I needed unlocked bootloader.
I just don't understand , all this so that no one could copy their ROM or I don't know for what . It's just makes things difficult for normal people and no one else. Locks can't keep a thief away. If anyone wants to break into their system than one will, if he/she uses right tools properly. Why make normal people lives' difficult?
ALSO I WANT TO ASK MORE THING, if in first case, I get into fastboot mode just after the ROM flash & before very first ROM boot and run this command and if in second case, the room gets booted and then I go into fastboot mode & run the command, DOES IT CREATES ANY CHANCE OF NON-OCCURRENCE OF THAT ERROR IN FIRST CASE?.
Gurkirat_Singh said:
OK that's why I'm having so much problem to unlock it. I just want to ask do you know any other way to fix the problem I'm having with this error. Cause the post you gave me tells how to unlock the RN3 temporary :crying: but the thread I followed helps to unlock it permanently :good: (how I know cause I used similar commands on my Canvas A1) and I followed almost every step properly.
I don't understand why companies emerged as custom ROMs stops supporting customisation, at least don't make it hard. I just wanted to flash my RN3 with a Custom ROM like CM13 cause MIUI is not supporting 4G networks properly of multiple operators that's why, for which I needed a custom recovery and for which I needed unlocked bootloader.
I just don't understand , all this so that no one could copy their ROM or I don't know for what . It's just makes things difficult for normal people and no one else. Locks can't keep a thief away. If anyone wants to break into their system than one will, if he/she uses right tools properly. Why make normal people lives' difficult?
ALSO I WANT TO ASK MORE THING, if in first case, I get into fastboot mode just after the ROM flash & before very first ROM boot and run this command and if in second case, the room gets booted and then I go into fastboot mode & run the command, DOES IT CREATES ANY CHANCE OF NON-OCCURRENCE OF THAT ERROR IN FIRST CASE?.
Click to expand...
Click to collapse
The thread I gave you was not temporary, it is permanent and it is temporary till you get the official unlock permission. Actually it's a permanent 'safe' solution.
Xiaomi did it for security of data, not to stop customising. If it had to stop users from customising, xiaomi wouldn't have given you warranty even if you root or it may not even have given you an option to unlock bootloader!
superboy123 said:
The thread I gave you was not temporary, it is permanent and it is temporary till you get the official unlock permission. Actually it's a permanent 'safe' solution.
Xiaomi did it for security of data, not to stop customising. If it had to stop users from customising, xiaomi wouldn't have given you warranty even if you root or it may not even have given you an option to unlock bootloader!
Click to expand...
Click to collapse
Thanks for all the support and help you gave me.
I got this error too but i forgot how to fix it.
Something about the 'disable driver signature' or the modified rom that you flash before you trying to unlock.
caesar13th said:
I got this error too but i forgot how to fix it.
Something about the 'disable driver signature' or the modified rom that you flash before you trying to unlock.
Click to expand...
Click to collapse
I unlocked the bootloader and also flashed the ROM successfully but still I'm not able to use the 4g service.
superboy123 said:
The thread I gave you was not temporary, it is permanent and it is temporary till you get the official unlock permission. Actually it's a permanent 'safe' solution.
Xiaomi did it for security of data, not to stop customising. If it had to stop users from customising, xiaomi wouldn't have given you warranty even if you root or it may not even have given you an option to unlock bootloader!
Click to expand...
Click to collapse
I unlocked the bootloader and also flashed the ROM successfully but still I'm not able to use the 4g service.
Gurkirat_Singh said:
I unlocked the bootloader and also flashed the ROM successfully but still I'm not able to use the 4g service.
Click to expand...
Click to collapse
By your name, I think you are an Indian, so which Sim you are using? You need to do a 4G pack recharge first to use LTE, VoLTE won't work in custom ROMs right now.
Edit: you could see this thread but this is a bit complicated: http://en.miui.com/thread-335643-1-1.html
superboy123 said:
By your name, I think you are an Indian, so which Sim you are using? You need to do a 4G pack recharge first to use LTE, VoLTE won't work in custom ROMs right now.
Edit: you could see this thread but this is a bit complicated: http://en.miui.com/thread-335643-1-1.html
Click to expand...
Click to collapse
I appreciate your help but the post you gave me is for non-asian countries so it will not work for me. As you already know I'm an Indian so that's why. Are you an Indian, only asking cause in that way you may already faced the problems i'm having.
I'm only familiar with only 2 4G networks for now. One is Airtel 4G, what they say have FDD LTE network, I don't what that is, but that's why it's not working on my phone, I contacted them and they said that my phone doesn't support it, I don't know why cause it support much more LTE Bands other than any smartphone in that price range. Second is Jio 4G, my sim gets detected, shows network in manual selection but doesn't get registered on them. I see only the message of 'No Service' or 'Emergency calls only' when I insert it.
@Gurkirat_Singh
It worked for me.
I had the same problem!
superboy123 said:
@Gurkirat_Singh
It worked for me.
I had the same problem!
Click to expand...
Click to collapse
What worked for you and how? Can you please answer/clarify my questions/doubts please also?
I tried that fix that I gave you and 4G started working for me. You cannot use jio on second sim slot. 2nd sim only connects to 2g.
superboy123 said:
I tried that fix that I gave you and 4G started working for me. You cannot use jio on second sim slot. 2nd sim only connects to 2g.
Click to expand...
Click to collapse
OK I'll try when got time and will update you with the result.

Redmi Note, Unlock bootloader (unoffical). oem unlock is not allowed while active

i tried to unlock my bootloader the offical way, but it apears to be impossible because their unlocking tool is very buggy and keep stucking at 50%.
so im doing it the unoffical way, after using this guide for unlocking https://forum.xda-developers.com/redmi-note-3/how-to/unlock-bootloader-twrp-root-7-2-3-t3359492.
im stuck in a point where it says cant unlock bootloader because OEM is locked, i tried it 2 times while checking it is on in my developer settings.
the device now is soft-brick(i know how to get it out of it), and idea how to unlock the bootloader?
ty, and sry for my english i tend to be confusing sometimes.
EDIT:::: GO TO COMMENT 6, Solution for me was just waiting a couple of days(using legit method)
PIC:
http://imgur.com/a/38RsO
555satan said:
i tried to unlock my bootloader the offical way, but it apears to be impossible because their unlocking tool is very buggy and keep stucking at 50%.
so im doing it the unoffical way, after using this guide for unlocking https://forum.xda-developers.com/redmi-note-3/how-to/unlock-bootloader-twrp-root-7-2-3-t3359492.
im stuck in a point where it says cant unlock bootloader because OEM is locked, i tried it 2 times while checking it is on in my developer settings.
the device now is soft-brick(i know how to get it out of it), and idea how to unlock the bootloader?
ty, and sry for my english i tend to be confusing sometimes.
PIC:
http://imgur.com/a/38RsO
Click to expand...
Click to collapse
Read my last post...
https://forum.xda-developers.com/redmi-note-3/help/unlocking-global-stable-rom-8-1-1-0-t3530467
You will be able to unlock officially.
And about soft brick ...
Use mi flash tool and flash mi Global stable rom.
Amirphp said:
Read my last post...
https://forum.xda-developers.com/redmi-note-3/help/unlocking-global-stable-rom-8-1-1-0-t3530467
You will be able to unlock officially.
And about soft brick ...
Use mi flash tool and flash mi Global stable rom.
Click to expand...
Click to collapse
so basiclly just wait 11 days and then try again?
555satan said:
i tried to unlock my bootloader the offical way, but it apears to be impossible because their unlocking tool is very buggy and keep stucking at 50%.
so im doing it the unoffical way, after using this guide for unlocking https://forum.xda-developers.com/redmi-note-3/how-to/unlock-bootloader-twrp-root-7-2-3-t3359492.
im stuck in a point where it says cant unlock bootloader because OEM is locked, i tried it 2 times while checking it is on in my developer settings.
the device now is soft-brick(i know how to get it out of it), and idea how to unlock the bootloader?
ty, and sry for my english i tend to be confusing sometimes.
PIC:
http://imgur.com/a/38RsO
Click to expand...
Click to collapse
I have the same problem, I have tried countless times, but it would still show the same error, even though in the past I have performed this method countless times with 100% success rate, but now, idk why this error shows up.. I have a feeling that reinstalling the windows and then following the procedure again might solve the issue, but I dont wanna go through all that deleting and reinstalling stuff.
No need ro reinstalling windows.
Just install adb drivers and confirm u are using same sim card number in slot 1...which is used for login into mi account in phone and pc.
Amirphp said:
Read my last post...
https://forum.xda-developers.com/redmi-note-3/help/unlocking-global-stable-rom-8-1-1-0-t3530467
You will be able to unlock officially.
And about soft brick ...
Use mi flash tool and flash mi Global stable rom.
Click to expand...
Click to collapse
Amirphp said:
No need ro reinstalling windows.
Just install adb drivers and confirm u are using same sim card number in slot 1...which is used for login into mi account in phone and pc.
Click to expand...
Click to collapse
i have all adb drivers installed and working(downloaded the clockwork ones so they are legit working), tried putting in the sim in slot 1 same issue.
it seems like a lot of people are having issues with that bootlocker, it's a shame i was happy to buy this device and now i regret every moment
EDIT:
today it worked, basiclly the solution is to wait, shame they dont mention it themself, no need to insert the sim

Categories

Resources