Successful Unlock Procedure...!!!! FULLY TESTED and Close to Perfect...!!!! - Xiaomi Redmi Note 4 Guides, News, & Discussion

Pre-requesites ::fingers-crossed:
1- Unlock premission granted.
2- Proper drivers installed.
3- ADB console should be able to detect your device via "adb devices" command.
4- In Developers setting tick on 'OEM Unlock' and turn on 'USB Debugging'.....Turn on 'USB Debugging Security' (Not necessary only telling you because i did that)
5-Not mandatory to attach the account under Mi Unlock Status bcoz many tried (Me also) but failed so don't worry if it fails for you also but do try to attach first.
6- MOST IMPORTANT THING - WAITING/PATIENCE. Kindly wait for atleast 7-8 days before trying unlocking or else like many you'll get "couldn't verify device" etc etc.
Now after 7-8 days :
1- Use older version of Mi Unlock App (because i used older version myself).
2-Log in and connect the device in fastboot mode and hit unlock and VOILA. Unlocked successfully.:laugh::victory:
I have attached the screens where i got permission sms on 9th March and Unlocked on 15th March (Yes like many I've been a fool and tried many times unlocking before waiting 7-8 days and FAILED ofcourse)
And there is no thing such as Unlocked only on Developer ROM or Global Stable ROM, it will unlock in any MIUI version whether Global Stable or Developer Version, its just a matter of Waiting for some days. I was convinced that i have to switch to Dev ROM but i tried on stable V8.1.15 and it unlocked successfully.:good::highfive:

abhipanthi said:
Pre-requesites ::fingers-crossed:
1- Unlock premission granted.
2- Proper drivers installed.
3- ADB console should be able to detect your device via "adb devices" command.
4- In Developers setting tick on 'OEM Unlock' and turn on 'USB Debugging'.....Turn on 'USB Debugging Security' (Not necessary only telling you because i did that)
5-Not mandatory to attach the account under Mi Unlock Status bcoz many tried (Me also) but failed so don't worry if it fails for you also but do try to attach first.
6- MOST IMPORTANT THING - WAITING/PATIENCE. Kindly wait for atleast 7-8 days before trying unlocking or else like many you'll get "couldn't verify device" etc etc.
Now after 7-8 days :
1- Use older version of Mi Unlock App (because i used older version myself).
2-Log in and connect the device in fastboot mode and hit unlock and VOILA. Unlocked successfully.:laugh::victory:
I have attached the screens where i got permission sms on 9th March and Unlocked on 15th March (Yes like many I've been a fool and tried many times unlocking before waiting 7-8 days and FAILED ofcourse)
And there is no thing such as Unlocked only on Developer ROM or Global Stable ROM, it will unlock in any MIUI version whether Global Stable or Developer Version, its just a matter of Waiting for some days. I was convinced that i have to switch to Dev ROM but i tried on stable V8.1.15 and it unlocked successfully.:good::highfive:
Click to expand...
Click to collapse
What error were you getting when trying to attach account ? Something like 86012 with chinese text ?
Please provide link to drivers.

abhishekr700 said:
What error were you getting when trying to attach account ? Something like 86012 with chinese text ?
Please provide link to drivers.
Click to expand...
Click to collapse
Yes the same one 86012 with some Chinese text... And till the end of unlocking I got that so I skipped it altogether and unlocked successfully.

Had to wait 7-10 days after I got unlock code to work.
Prior attempts were all FAIL at 50%....

abhipanthi said:
Yes the same one 86012 with some Chinese text... And till the end of unlocking I got that so I skipped it altogether and unlocked successfully.
Click to expand...
Click to collapse
Okay, I thought the error is with my phone so I factory reset it lol.
vignesh1985 said:
Had to wait 7-10 days after I got unlock code to work.
Prior attempts were all FAIL at 50%....
Click to expand...
Click to collapse
Thanks bud, I will wait and retry.

abhishekr700 said:
Okay, I thought the error is with my phone so I factory reset it lol.
Thanks bud, I will wait and retry.
Click to expand...
Click to collapse
Same error I got multiple trials... Be patient, give try after 10+ days... Gud luk....
I tried all other differetn solutions, nothign worked.

Yes, the universal truth is Absolutely Nothing will work before the waiting period. If you got all the right things and still stuck on 50% then just wait and don't waste your energy and precious time doing things which are unnecessary and frustrating...

vignesh1985 said:
Same error I got multiple trials... Be patient, give try after 10+ days... Gud luk....
I tried all other differetn solutions, nothign worked.
Click to expand...
Click to collapse
Yeah, I'm waiting.
abhipanthi said:
Yes, the universal truth is Absolutely Nothing will work before the waiting period. If you got all the right things and still stuck on 50% then just wait and don't waste your energy and precious time doing things which are unnecessary and frustrating...
Click to expand...
Click to collapse
This is really really frustrating man

abhipanthi said:
Yes, the universal truth is Absolutely Nothing will work before the waiting period.
Click to expand...
Click to collapse
Speaking from my experience with the Redmi Note 3 SE (Kate): Sorry, no. In many cases, unlock was possible after 3 days. In many other cases, it did not work. My device included, I never managed to unlock the bootloader. Tried different computers, software, waiting, dancing around a camp fire. No success. Finally I sold the RN3 phone, and I hope you are right and it will be better with my soon arriving RN4X TW-Edition.

I know the feeling...
dieterhaack said:
Speaking from my experience with the Redmi Note 3 SE (Kate): Sorry, no. In many cases, unlock was possible after 3 days. In many other cases, it did not work. My device included, I never managed to unlock the bootloader. Tried different computers, software, waiting, dancing around a camp fire. No success. Finally I sold the RN3 phone, and I hope you are right and it will be better with my soon arriving RN4X TW-Edition.
Click to expand...
Click to collapse
The sole reason is to create this thread was only this that people (like myself) who love to mod their device don't waste their precious time and energy finding a way to achieve which can't be achieved without waiting enough. I know waiting is frustrating but it is the solution.
And Best of Luck for your new device and I'm sure you'll be able to do whatever you wish for.. :good:

Related

Report Your Problems with the Official ASUS Bootloader Unlock Tool Here

There's a bunch of threads about the bootloader unlock tool existing, not any real place to aggregate reports of problems with it. So, if you've attempted to unlock your bootloader using the official ASUS tool and are having problems, please post your situation.
Reported instances:
myself
DeathStolas
ASUS_Khang
Rattraps123
m3t4lw01f
creison
both are experiencing bootloader unlock limbo. The tool seems to have worked, but going into fastboot shows two progressive screens:
1) Unlock Successfully reboot in 5 seconds
2) FASTBOOT CMD WAITING...
RESULT: FAIL(can not mount the necessary partition)
Clearing the cache goes through the loop again. Mind you, this loop only happens when you're trying to get to the bootloader. If you go to recovery or normally boot, you won't have any issues.
However, any commands sent via fastboot fail, so the bootloader is still locked. Attached is an image of the second bootloader screen.
ASUS_Khang is already getting in touch with technical folks to investigate as well, but I figure it best to see if anyone else is having issues with the official tool.
Having your device encrypted prevents the unlock tool from working it seems...had to factory reset then I could run it and it "worked".
I, too, have the Unlock Successfully reboot in 5 seconds message though, so at this point I'm hoping ASUS comes through.
EDIT: Now I am getting the:
FASTBOOT CMD WAITING...
RESULT: FAIL(can not mount the necessary partition)
Error when I reboot to the bootloader (I did nothing else, just used the phone for a bit and decided to try rebooting again).
If it matters, I did NOT have a PIN set on my phone when I ran the tool and it complained at me when running it, but allowed me to continue. Shot in the dark here that maybe that's related. Wondering if other people had a PIN or not when they ran and are having the same errors...

			
				
I have to laugh at the fact that someone on XDA unlocked the bootloader successfully with none of these problems and then ASUS give an "Official Unlock Tool" that screws up the phone of any who uses it... In the words of Alanis Morrisett - "Isn't it Ironic"...
m3t4lw01f said:
Having your device encrypted prevents the unlock tool from working it seems...had to factory reset then I could run it and it "worked".
I, too, have the Unlock Successfully reboot in 5 seconds message though, so at this point I'm hoping ASUS comes through.
EDIT: Now I am getting the:
FASTBOOT CMD WAITING...
RESULT: FAIL(can not mount the necessary partition)
Error when I reboot to the bootloader (I did nothing else, just used the phone for a bit and decided to try rebooting again).
If it matters, I did NOT have a PIN set on my phone when I ran the tool and it complained at me when running it, but allowed me to continue. Shot in the dark here that maybe that's related. Wondering if other people had a PIN or not when they ran and are having the same errors...
Click to expand...
Click to collapse
Same problem. I unlocked without pin. Bootloader is unlock with withe spash screen but always ...unlock successfully... reboot after 5 sec.
Same problem here. I used the official unlocker tool and it did what it said it was going to do, but... I got the mythical "Bootloader 5 sec reboot".
asus is working on a fix.
playingmax said:
asus is working on a fix.
Click to expand...
Click to collapse
I'm sure that they are, but it would be interesting to see a source for that claim.
darkdragon505 said:
I'm sure that they are, but it would be interesting to see a source for that claim.
Click to expand...
Click to collapse
There's an official ASUS rep in another threads keeping us in the loop on what's happening.
He even sacrificed his own device and ended up with the same problem.
Going to need a little patience here while we wait for some more info.
m3t4lw01f said:
There's an official ASUS rep in another threads keeping us in the loop on what's happening.
He even sacrificed his own device and ended up with the same problem.
Going to need a little patience here while we wait for some more info.
Click to expand...
Click to collapse
Sounds good. Can't wait till this is all sorted out and I can continue on with installing Cyanogenmod for my SO. She is really excited since it's her first Android phone.
darkdragon505 said:
I'm sure that they are, but it would be interesting to see a source for that claim.
Click to expand...
Click to collapse
here you go
http://myzen.asus.com/2015/10/13/official-bootloader-unlock-for-zenfone-2-is-now-available/
look at Khang Thai (ASUS REP) reply. they are working on a fix.
Kona67 said:
Same problem. I unlocked without pin. Bootloader is unlock with withe spash screen but always ...unlock successfully... reboot after 5 sec.
Click to expand...
Click to collapse
Same issue ... I tried without a pin .. now added a pin and it asked me for it when trying to run the app again ... but that didn't help !
Help Ausus!!!
Mine says unlock failed rebooting in 5,4,3,2,1.
any way to relock bootloader as zenfone 6,5,and 4 have
When the 5 second bootloader issue is fixed you should hear about it here first, we have an Asus employee helping us: http://forum.xda-developers.com/zenfone2/general/official-asus-ze551ml-bootloader-unlock-t3224747
https://fsfe.org/news/2012/news-20121106-01.en.html
Enviado do meu iPhone usando o Tapatalk
Looks like a user has solved the 5 second reboot issue. Check out the rather convoluted method here: http://forum.xda-developers.com/showthread.php?p=63498472

Dont worry more with 50% error while unlocking the beast

Warning:all the following attempts should be made by you only .and you know what you are going to do.
Description:-
Its really got tough to officially unlock redmi note 3 pro for us .many of us lose their hopes .but now get ready to unlock your beast in seconds officially on any rom.either global stable or global dev rom.
Here is the procedures :
1.make sure you are on the latest global or china rom
2.make sure you have same account logged on both parties.
3.make sure you can find your phone on i.mi.com
4.now try unlocking ,if you succeed then its good otherwise go ahead
5.boot in fastboot mode,and connect to pc
6.open device manager and search for android phone at top.now in sub menu
what is that
if it is "android bootloader interface" ,actually provided latest on native on windows 10 .uninstall it and install from universal clockworkmod adb driver now try again .if succeded then good .otherwise go ahead
6.if not then search for xiaomi 1.3 driver on google.and install it
7.now you must succeed
TIPS
1. keep trying for at least a week daily (if you are new to face this )
2.looking like xiaomi do it in batch rather than trying of daily
3.also ,one thing i would like to include that .i had reapplied for unlocking from different account mentioning the 50% error with same phone number but different mi account account number and got permission message today for other mi account but remained stuck with old one.and finally unlocked today.
special thanks to @zmajdk
xda team
miui team[emoji3] [emoji3] [emoji3] [emoji3]
Sent from my Redmi Note 3 using Tapatalk
In starting
now get ready to unlock your beast in seconds officially on any rom.
Click to expand...
Click to collapse
In the end
1. keep trying for at least a week daily
Click to expand...
Click to collapse
I have never been able to figure out this signature thing
Tyaginator said:
In starting
In the end
I have never been able to figure out this signature thing
Click to expand...
Click to collapse
sorry for that,but this is only for who fed up with trying and trying ,thanks for your response ,i am new at here

[Hardbrick] Oneplus 2 Only fastboot, OEM and device locked.

So, as this is my first ever thread to this website and the reason why i have created this account, I am somewhat new to the XDA forums...
Nevertheless, i will state my problem here:
Right now, my phone and my limited knowledge about it have come to an dead end. with the help of online tutorials and so on, (I have downloaded almost 40 gigabytes worth of space to do stuff to my phone), i was able to only get the fastboot mode to work again.
It started with me uninstalling a system app from google (I don't know which one exactly, but i had the resurrection remix 5.69 or something like it, and in that ones system app remover it was one of the lowest google apps). I don't know if this is important, but at the time i did that i was in plane mode.
After some time i ran into some loading issues with games and restarted my phone. the first time i got in, i booted up normally and could do my pattern normally, but then there was only a black screen and i could pull that info bar thing down. as soon as i wanted to open the settings, everything froze and i decided to restart the phone. Once it was shut down i then got greeted by a bootloop which i aborted by shutting down after about 3 minutes. then nothing was working anymore, so i wanted to see if the fastboot mode was still available. it was, but after shutting down from that and trying again ( just to be sure) even that was gone.
so i went online and downloaded basically everything you can find online to recover a harbricked op2.
turns out, after i got my fastboot working again, the OEM and the device were locked (still not sure if those are different things or the same) and because i couldnt get in the android system, i could not enable it.
the ADB commands do not work at all because there is no device detected for it, though it is detected for fastboot. the command fastboot OEM unlock does not work because OEM unlocking is disabled...
so far i have been able to connect my phone in 3 modes and names for those, them being:
Android Bootloader interface (Fastboot)
Qualcomm HS-USB Diagnostics 900E (Connected while holding VolUp)
RELINK HS-USB QDLoader 9008 (Connected while holding VolUp + VolDown)
I am also unable to flash anything on the phone because the OEM is locked
I will not be able to answer for some time (probably 2-3 weeks) but i wanted to start this thread so I could already have an answer when i come back home again (traveling with fam, and its somewhat hard to take a PC tower with you on trips)
Thanks for helping me! :fingers-crossed:
I'm having the exact same issue as OP.
I'm not sure exactly what I did, but I can only boot to fastboot. Typing fastboot continue does not work, I can't flash ANYTHING or use any of the recovery tools, because my device is locked, and there's no system to boot to so I can run fastboot oem unlock (have to turn on debugging, which I can't do). I have read just about every guide there is, and also downloaded a boatload of purported "fix" tools/drivers/packages. My phone remains able to boot only into fastboot, and I can't get anything working.
Installing the device drivers did work for me, so I'm about half a step ahead of some other people with this issue, but none of the tools or scripts I've found, or manual methods, have brought my OP2 back to life.
I'm really, really hoping someone here is able to help with this.
Only way is restore with Qualcomm tool
Sent from my SM-N920C using Tapatalk
Coolmfarshard said:
Only way is restore with Qualcomm tool
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
Sorry, but could you link us that?
Also,does this really work with a locked device and locked OEM? Please do not tell us things if you don't know if they work.
http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449
Lonemaster said:
Sorry, but could you link us that?
Also,does this really work with a locked device and locked OEM? Please do not tell us things if you don't know if they work.
Click to expand...
Click to collapse
Its working bro tried several phones with this tool
You cant know its working or not without trying
Coolmfarshard said:
Its working bro tried several phones with this tool
You cant know its working or not without trying
Click to expand...
Click to collapse
Ok, Thanks. Don't know what i was thinking back then.
I will reply again when i am Home and tried it. (Currently i am just using Internet cafes.)
MickyFoley said:
http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449
Click to expand...
Click to collapse
Oh, it is that one. I had already tried this one, in all listed modes posted above. The problem with that one is that everytime I hit the start button, the green progress bar does not show up and it does not a single thing... because I am staying at a place with a internet café for 3 days, I can download some stuff and try it again.
EDIT: I don't know if that was the reason It didn't work, but I may or may not have forgotten to install the driver because it was deleted off the onedrive page and I just forgot about it afterwards. if I can find a replacement for it, I will ink it here for future users with the same problem. otherwise, I would be GLaD if someone would do that for me...
Have you tried flashing a stock ROM with the qcom download tool
abdur10567 said:
Have you tried flashing a stock ROM with the qcom download tool
Click to expand...
Click to collapse
I am not sure if it is that one (it gets pretty messy wehen you have downloaded 50 gigs), but i think it wouldn't let Me because of the locked OEM.
Lonemaster said:
So, as this is my first ever thread to this website and the reason why i have created this account, I am somewhat new to the XDA forums...
etc. etc.
Thanks for helping me! :fingers-crossed:
Click to expand...
Click to collapse
For some reason, after doing it for the what felt like the billionth time whith the restore tool it finally worked (I have NO ****ING IDEA why tho.)
Thanks for everybody who helped me.

Bootloop, all original, can't access Recovery mode, bootloader locked,

Hi guys,
I'm stuck like some of you in the Bootloop with my Nexus 6P.
Some useful informations :
Bootloader is locked.
Can't access to Recovery mode : it keeps bootlooping.
Bootloader and OS are orignal (no mod of any kind).
Dev mod is not activated (well, I think)
Can't say if OEM unlock or USB debugging is enabled or not
Phone is not rooted
Android version : 7.x
Sorry if I creating a duplicated thread but I did not find any thread in the same config.
Thanks !
Bootloop plus no recovery equals BLOD...
CyberpodS2 said:
Bootloop plus no recovery equals BLOD...
Click to expand...
Click to collapse
Which means RMA ? Warranty time expired... 3 months ago.
If someone have clues or a solution, I'll take it
Thanks
Did you try tech support?
BookeurZ said:
Which means RMA ? Warranty time expired... 3 months ago.
If someone have clues or a solution, I'll take it
Thanks
Click to expand...
Click to collapse
Try RMA. My phone started doing the same thing(while i was trying to get directions on Maps Preview & downloading offline maps) and the warranty had expired last November. The support tech made an exception and processed a replacement(without me saying anything). I will not be getting the same color but i am fine with it. When asked if i should downgrade to Marshmallow, the tech said i could but he was confident that the replacement would not exhibit the same issue. Let's see what happens.:fingers-crossed:
Like the post above, try rma and hopefully get a replacement. In the meantime or if support doesn't get you a working phone try this. You can check if OEM and USB debugging is on if you try to unlock bootloader in fastboot. If it is you will be able to unlock it. Check this thread out if you haven't already. There is a section in post 1 for those that are locked. Some report success. You won't know till you try.
https://forum.xda-developers.com/nexus-6p/general/guide-fix-nexus-6p-bootloop-death-blod-t3640279

oem unlock is not allowed

I'm trying to unlock phone’s bootloader using
Code:
fastboot flashing unlock
, but getting error message:
Code:
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.021s
Checked fastboot devices command and it found my device connected.
I do not remember exactly, but think that USB debugging is off.
It's a phone with bootloop issue, so cannot get into recovery menu also.
Apologize is if it was already discussed.
jorgen.bumajnikov said:
I'm trying to unlock phone’s bootloader using
Code:
fastboot flashing unlock
, but getting error message:
Code:
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.021s
Checked fastboot devices command and it found my device connected.
I do not remember exactly, but think that USB debugging is off.
It's a phone with bootloop issue, so cannot get into recovery menu also.
Apologize is if it was already discussed.
Click to expand...
Click to collapse
Try this https://www.xda-developers.com/nexus-6p-bootloop-fix/
Sent from my Nexus 6P using Tapatalk
Minh Dao said:
Try this https://www.xda-developers.com/nexus-6p-bootloop-fix/
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Thanks, I saw this post and was trying to follow steps described there, but 9 steps is about unlocking bootloader and I cannot pass it...
Both OEM unlocking and USB debugging need to be enabled in Settings/Developer options before the bootloader can be unlocked.
redduc900 said:
Both OEM unlocking and USB debugging need to be enabled in Settings/Developer options before the bootloader can be unlocked.
Click to expand...
Click to collapse
in post I mention that it's phone with bootloop issue
And I told you why you can't unlock the bootloader.
redduc900 said:
And I told you why you can't unlock the bootloader.
Click to expand...
Click to collapse
so that's it - no way to make it work again at all? (
I tried this but I couldn't make it work.
rootmygalaxy.net/unlock-bootloader-on-huawei-devices/
which leads to
emui.huawei.com/en/plugin/unlock/detail
but no matter how hard I try, I keep getting:
"Please make sure the verification code and model number are correct. If your device has multiple IMEIs or MEIDs, please try another IMEI or MEID."
Try enabling OEM unlocking in developer options
Unfortunately can't when it's stuck bootlooping.
bcurran3 said:
Unfortunately can't when it's stuck bootlooping.
Click to expand...
Click to collapse
Follow the thread below, same one as before. You need to stick with this until it works.
https://forum.xda-developers.com/showthread.php?t=3640279
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Follow the thread below, same one as before. You need to stick with this until it works.
https://forum.xda-developers.com/showthread.php?t=3640279
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thanks. Yeah, I tried the freezer trick. In fact I put it in there and forgot about it for a week! HA! Didn't work. I'll need to try the hairdryer trick.
I'm REALLY hoping Google responds to the boot.img signature files request....that would make life so much simpler. I'm probably going to shelve this project for the 4th or 5th time and wait a few weeks. (I've been dealing with this since Feb or March.)
I did put in another call to Huawei today. The next available representative was nice but told me that Huawei global unlocks the bootloader for people in China but not the US. I had him open a case to get the bootloader unlock code and pass it up the chain. I doubt it will result in anything...but at least the request is officially in.
OP did you fix the boot looping issue? I am in the exact same spot - my phone is stuck in boot loop and my OEM is locked too
draxz said:
OP did you fix the boot looping issue? I am in the exact same spot - my phone is stuck in boot loop and my OEM is locked too
Click to expand...
Click to collapse
I just fixed my phone and thought I would post my method:
For the people with boot loader locked (You CANNOT do anything with it being locked) I just revived my phone:
You need to heat the phone by using a blow drier for about 5-10 mins while in boot loop - in my case I don't have a blow drier so I turned the stove to medium heat and kept the phone about 10 centimeters above the heat. After 10 mins the phone miraculously booted up and went to "Setup as new phone" (I had wiped the device earlier) after setting it up, I immediately went into the setting to unlock OEM and after 15 mins the phone went into the boot loop again. I followed the instructions on this page https://www.xda-developers.com/nexus-6p-bootloop-fix/, a huge thank you to XCnathan32 and voila the phone works. Thank you XCnathan32 and other, please thank him by clicking the thank you button on his page or by making a donation as a gift.
I wish I was having luck.
Over the past two weeks we've had multiple 100+ degree days in Los Angeles. I threw my 6p on the charger in my OUTSIDE office. The phone got hot as hell. I tried for days to get it to boot up with no joy. I did get the NO COMMAND screen a couple times. One time I actually got to it fast enough to interact and hit the right keys to go and wipe it again. (I wiped it months ago too.) One time I accidently hit install update from SD card (always makes me laugh as there is no SD card) and I think it said it was installing the update from the SD card (again I laughed) but my guess is that's just the default graphic to display from the menu choice even if it doesn't do anything.
Anyways, for 3-4 days in 103-111 degree heat I tried for multiple multiple hours. The phone would never boot to the setup screen for me to go and turn off the OEM unlocking. I thought maybe the cores were still going full bore since it was sitting on the charger and I tried pulling it off a few times...but the battery was never charged enough to do anything.
I'm still at a loss.
Any new developments or suggestions?
unlocked oem problem. help!
I tried everything. Heating. Draining. Freezing. Nothing works for me. I just need to unlock it so I can fix the bootloop issue. I badly need some help here guys. Thank you.
aphrodirish said:
I tried everything. Heating. Draining. Freezing. Nothing works for me. I just need to unlock it so I can fix the bootloop issue. I badly need some help here guys. Thank you.
Click to expand...
Click to collapse
If you bought your Nexus 6P via Google Store you can get a New Google Pixle XL even after the 1 Year device Guarantee
maybe your lucky enough
reddit.com/r/Nexus6P/comments/6y1tm2/official_6p_battery_shutdownbootloop_rma_thread
bcurran3 said:
I'm still at a loss. Any new developments or suggestions?
Click to expand...
Click to collapse
Get a good blow dryer or heat gun? A typical blow dryer will only reach ~140F on a good day. A decent heatgun will start around ~500F and go over 1000F. You're supposed to start with the device bootlooping and apply heat until the phone boots. My guess is you are not hot enough and/or not getting the heat to the right area on the back of the phone. Bear in mind this will just give you enough time to get into Dev Settings and toggle OEM Unlock so you can unlock your bootloader and flash a custom kernel like EX.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Update:
Based on "Google is replacing defective Nexus 6P units with Pixel XLs, but only in North America"
https://www.phonearena.com/news/Goo...h-Pixel-XLs-but-only-in-North-America_id98059
Just got off the phone with Google (10 hours ago) and confirmed they are replacing my dead/looping Nexus 6P out of warranty and swapping with a Pixel XL. It took me SIX MONTHS to get this resolved. I'm not happy about the time frame, but I guess I'm pseudo-satisfied with the end result.
For those who attempt a replacement, the KEY WORDS that seemed to make the customer service rep take notice was that mine started bootlooping after installing the 7.1.2 beta sometime in March. This is where her ears perked up and she started two "escalations" to get approval for "extend warranty" and replace my phone. Hope this helps you out.
The irony of this is, I'm going to give the Pixel XL to my wife, continue using my LG V20 for the moment, and try to determine if I want to spend the bucks on a Pixel 2 XL or a LG V30 later this year.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Try this
Try finding the OEM unlock code for your specific mobile from Huawei customer service site

Categories

Resources