Hello....I am getting the following error when trying to unlock the bootloader through fastboot even after I obtained 288bytes unlock.bin file from the OnePlus website. My network is still locked to T-Mobile, but I have heard of people unlocking the bootloader while network is still locked.
Unlocking Bootloader...
Sending 'cust-unlock' (0 KB) OKAY [ 0.000s]
Writing 'cust-unlock' FAILED (remote: 'Error - Verify Failed ! (4:-2)')
fastboot: error: Command failed
FAILED (remote: 'Please flash unlock token first.')
fastboot: error: Command failed
Tried with the bin file in the platform tools folder and same error as below:
PS C:\Users\alvcr\Desktop\platform-tools> fastboot flash cust-unlock unlock.bin
target reported max download size of 805306368 bytes
sending 'cust-unlock' (0 KB)...
OKAY [ 0.015s]
writing 'cust-unlock'...
FAILED (remote: Error - Verify Failed ! (4:-2))
finished. total time: 0.032s
Please help. Thanks.
U have to get unlock token from oneplus. Or have a bypass for it. Which i do. But wont release
I have the bin file as mentioned in my original post. Just don't know what the 'Verify Failed ! (4:-2))' error means.
Alcross888 said:
I have the bin file as mentioned in my original post. Just don't know what the 'Verify Failed ! (4:-2))' error means.
Click to expand...
Click to collapse
It means you have the wrong unlock token. The only workaround I know of is to convert your variant to Europe with the MSM from another thread. That won't require a unlock.bin code and you can just unlock the bootloader simply by fastboot flashing unlock. If I had another bypass, I would share it with you, some people are just not willing to be very helpful.
TheSayaMan said:
It means you have the wrong unlock token. The only workaround I know of is to convert your variant to Europe with the MSM from another thread. That won't require a unlock.bin code and you can just unlock the bootloader simply by fastboot flashing unlock. If I had another bypass, I would share it with you, some people are just not willing to be very helpful.
Click to expand...
Click to collapse
Ohh thank you so very much brother. That was very kind of you to help me. Will a my data be erased if I convert to the EU version and also is there any way or tool to unlock my network that is tied to T-Mobile
Alcross888 said:
Ohh thank you so very much brother. That was very kind of you to help me. Will a my data be erased if I convert to the EU version and also is there any way or tool to unlock my network that is tied to T-Mobile
Click to expand...
Click to collapse
sim unlock is totally different, I can't help you with that, but yes, your phone will be wiped, so back everything up. I had the same problem as you have. I received a unlock token code that won't verify either and EU is the only workaround I know. You can always MSM back to T-Mobile if you decide not to stay with EU but then you will require a unlock token again.
TheSayaMan said:
sim unlock is totally different, I can't help you with that, but yes, your phone will be wiped, so back everything up. I had the same problem as you have. I received a unlock token code that won't verify either and EU is the only workaround I know. You can always MSM back to T-Mobile if you decide not to stay with EU but then you will require a unlock token again.
Click to expand...
Click to collapse
Ohh okay. I heard someone say that
Unlocked bootloader without unlock_token must be done while in OOS11, as OOS12+ ABL will check that a token is needed
I am on Android 12.
Alcross888 said:
Ohh okay. I heard someone say that
Unlocked bootloader without unlock_token must be done while in OOS11, as OOS12+ ABL will check that a token is needed
I am on Android 12.
Click to expand...
Click to collapse
yes but when you MSM to EU, you will be back on 11 so you can. Just do it before you update back to 12.
Oh okay...so I can still unlock the bootloader although Im now on Android 12 since I get downgraded to 11 after the EU conversion right? That's great brother. Thank you so very much for a the help. I greatly appreciate it.
Alcross888 said:
Oh okay...so I can still unlock the bootloader although Im now on Android 12 since I get downgraded to 11 after the EU conversion right? That's great brother. Thank you so very much for a the help. I greatly appreciate it.
Click to expand...
Click to collapse
yes correct, and no problem anytime. When you convert to EU it will put you back on 11. Then unlock bootloader first. Then you can update back to 12 and it won't matter because your bootloader will already be unlocked.
TheSayaMan said:
yes correct, and no problem anytime. When you convert to EU it will put you back on 11. Then unlock bootloader first. Then you can update back to 12 and it won't matter because your bootloader will already be unlocked.
Click to expand...
Click to collapse
Thanks a million for clarifying bro.
Alcross888 said:
Thanks a million for clarifying bro.
Click to expand...
Click to collapse
Your welcome
Related
There are several references in the bootloader to the /persistent partition. one of which is in very close proximity to the string "failed to erase bootloader unlock key"
Check OEM Unlock : No memory!...mmc read failure /persistent....Partition table doesn't exist...failed to erase partition...failed to erase bootloader unlock key
Click to expand...
Click to collapse
Could anyone dump their /persistent partition and compare its contents with that of their unlock.bin
If the bootloader unlock key is indeed flashed to the /persistent partition then removing it would essentially reverse unlocking the bootloader.
Any Dev's already tried this?
Anyone on the verge of unlocking willing to dump /persistent before and after the unlock procedure?
OllieD said:
There are several references in the bootloader to the /persistent partition. one of which is in very close proximity to the string "failed to erase bootloader unlock key"
Could anyone dump their /persistent partition and compare its contents with that of their unlock.bin
If the bootloader unlock key is indeed flashed to the /persistent partition then removing it would essentially reverse unlocking the bootloader.
Any Dev's already tried this?
Anyone on the verge of unlocking willing to dump /persistent before and after the unlock procedure?
Click to expand...
Click to collapse
If you put the instructions for dump the that partition maybe you catch some attention!
Enviado do meu LG-H815 através de Tapatalk
OllieD said:
There are several references in the bootloader to the /persistent partition. one of which is in very close proximity to the string "failed to erase bootloader unlock key"
Could anyone dump their /persistent partition and compare its contents with that of their unlock.bin
If the bootloader unlock key is indeed flashed to the /persistent partition then removing it would essentially reverse unlocking the bootloader.
Any Dev's already tried this?
Anyone on the verge of unlocking willing to dump /persistent before and after the unlock procedure?
Click to expand...
Click to collapse
This is a nice idea.
This is how to dump the persistent partition:
1. Get inside download mode and follow the following guide:
http://lgviet.com/forum/threads/huong-send-command-tren-lg-g4-android-6-0-marshmallow.53972/
2. Run with Send_Command.exe the following command:
Code:
dd if=/dev/block/mmcblk0 bs=8192 skip=23808 count=256 of=/data/media/0/persistent.img
3. Pull out the usb cable and the battery
4. Turn on your phone and connect it to computer
I attached my LOCKED H815L persistent partition
Al0n said:
This is a nice idea.
This is how to dump the persistent partition:
1. Get inside download mode and follow the following guide:
http://lgviet.com/forum/threads/huong-send-command-tren-lg-g4-android-6-0-marshmallow.53972/
2. Run with Send_Command.exe the following command:
Code:
dd if=/dev/block/mmcblk0 bs=8192 skip=23808 count=256 of=/data/media/0/persistent.img
3. Pull out the usb cable and the battery
4. Turn on your phone and connect it to computer
I attached my LOCKED H815L persistent partition
Click to expand...
Click to collapse
Thank you for this Al0n,
Now all I need is someone with an unlocked device to send me their persistent partition and a copy of their Unlock.bin.
Hi,
That is great ! I hope it will work so everybody can freely unlock and the relock his bootloader when needed. My phone was unlocked but it went into endless bootloop and now I got it repaired and now I'm afraid to unlock it again.
thewhisper said:
Hi,
That is great ! I hope it will work so everybody can freely unlock and the relock his bootloader when needed. My phone was unlocked but it went into endless bootloop and now I got it repaired and now I'm afraid to unlock it again.
Click to expand...
Click to collapse
I'm dabbling with the idea of unlocking myself.
I have a 506 tied to a 2 year contract, it was an upgrade I took 3 months ago which was about the time the issue became more public.
I would rather test this theory first before I have to argue with Carphone Warehouse that unlocking does not void my warranty as per EU law.
Given that the bootloop is a common hardware fault the Customer should not have such problems getting it resolved, regardless of what we have done software wise.
OllieD said:
I'm dabbling with the idea of unlocking myself.
I have a 506 tied to a 2 year contract, it was an upgrade I took 3 months ago which was about the time the issue became more public.
I would rather test this theory first before I have to argue with Carphone Warehouse that unlocking does not void my warranty as per EU law.
Given that the bootloop is a common hardware fault the Customer should not have such problems getting it resolved, regardless of what we have done software wise.
Click to expand...
Click to collapse
An even simpler test someone could try to relock bootloader is try:
fastboot erase unlock
I will try in a few days
Enviado desde mi LG-H815 mediante Tapatalk
Hi guys,
I checked the serial of my repaired phone and it seems that they changed my motherboard with new IMEI and serial. I checked my imei at imeidata.net and it decoded my IMEI and from there I saw it is with 604 serial, which means it is built in april this year. Can I now feel safe from bootloop again ? I'm still hasitating to unlock my bootloader again as I'm afraid if it bootloops I will not be covered by my waranty anymore. First time my phone was with bootloader unlocked and they repaired it but it was younger than an year. In june it makes it first year so I think after it they will not cover it by waranty if it is unlocked. What you think ? Am I safe from bootloop or not ?
thewhisper said:
Hi guys,
I checked the serial of my repaired phone and it seems that they changed my motherboard with new IMEI and serial. I checked my imei at imeidata.net and it decoded my IMEI and from there I saw it is with 604 serial, which means it is built in april this year. Can I now feel safe from bootloop again ? I'm still hasitating to unlock my bootloader again as I'm afraid if it bootloops I will not be covered by my waranty anymore. First time my phone was with bootloader unlocked and they repaired it but it was younger than an year. In june it makes it first year so I think after it they will not cover it by waranty if it is unlocked. What you think ? Am I safe from bootloop or not ?
Click to expand...
Click to collapse
wrong topic.And mate bootloop full random i think all G4 infected.No joker motherboard number.
My mate 60x moterboard and get bootloop.
I still stick to my thoughts that no device is safe. its luck of the draw.
Your chance of boot loop is simply a case of how badly manufactured your particular device is, how much you stress it and how old it is.
The issue seems to take on average 6 - 9 months before it cripples most devices.
This is a decent amount of time for LG to play the blame game, argue warranties and swap around/fix as few devices as possible until the G4 is end of life.
Most users upgrade their phones every year or two, so they will be hoping the majority of users will upgrade to a G5.
Now that my thread has been completely de-railed,
Any unlocked users willing to help out?
I still need someone to try:
fastboot erase unlock
and someone to dump their /persistent partition and send me it along with their unlock.bin.
OllieD said:
Any unlocked users willing to help out?
I still need someone to try:
fastboot erase unlock
and someone to dump their /persistent partition and send me it along with their unlock.bin.
Click to expand...
Click to collapse
I'm not sure when I will go back to stock or maybe sell my phone. Could be in a couple of days because the cam on CM13 isn't good as expected but then I would try
Just tried that erase command. Result:
Code:
C:\Android-SDK\platform-tools>fastboot flash unlock unlock.bin
target reported max download size of 536870912 bytes
sending 'unlock' (1 KB)...
OKAY [ 0.031s]
writing 'unlock'...
(bootloader) Erase userdata and cache
(bootloader) -----------------------------------------------------------
(bootloader) Bootloader Unlock key flash Success
(bootloader) -----------------------------------------------------------
OKAY [ 2.402s]
finished. total time: 2.449s
C:\Android-SDK\platform-tools>fastboot erase unlock
erasing 'unlock'...
FAILED (remote: cannot erase this partition in unlocked state)
finished. total time: 0.016s
Sadly, I forgot to dump my /persistent partition BEFORE the unlock. Anyway, I've got my dump of /persistent after the unlock and my unlock.bin right here, zipped up and ready. But i can't upload nor post a link yet since i'm new to the forums.
GaryBlack said:
Just tried that erase command. Result:
Code:
C:\Android-SDK\platform-tools>fastboot flash unlock unlock.bin
target reported max download size of 536870912 bytes
sending 'unlock' (1 KB)...
OKAY [ 0.031s]
writing 'unlock'...
(bootloader) Erase userdata and cache
(bootloader) -----------------------------------------------------------
(bootloader) Bootloader Unlock key flash Success
(bootloader) -----------------------------------------------------------
OKAY [ 2.402s]
finished. total time: 2.449s
C:\Android-SDK\platform-tools>fastboot erase unlock
erasing 'unlock'...
FAILED (remote: cannot erase this partition in unlocked state)
finished. total time: 0.016s
Sadly, I forgot to dump my /persistent partition BEFORE the unlock. Anyway, I've got my dump of /persistent after the unlock and my unlock.bin right here, zipped up and ready. But i can't upload nor post a link yet since i'm new to the forums.
Click to expand...
Click to collapse
Can you dump "unlock" partition?
Also, can you attach your unlock.bin file and your device-id?
Al0n said:
Can you dump "unlock" partition?
Also, can you attach your unlock.bin file and your device-id?
Click to expand...
Click to collapse
I'd gladly dump the unlock partition if i knew how. Could you give a few tips how to (or how i can find out the arguments/numbers needed for dd command)
Unfortunately, I can't attach files yet. But i can pm you a link to my unlock.bin.
DeviceID is:
BE4A51BE0E3459D56EE2ED45AC22765A
8849D9523196EB990DBE496426A41945
GaryBlack said:
I'd gladly dump the unlock partition if i knew how. Could you give a few tips how to (or how i can find out the arguments/numbers needed for dd command)
Unfortunately, I can't attach files yet. But i can pm you a link to my unlock.bin.
DeviceID is:
BE4A51BE0E3459D56EE2ED45AC22765A
8849D9523196EB990DBE496426A41945
Click to expand...
Click to collapse
as mentioned above:
dd if=/dev/block/mmcblk0 bs=8192 skip=23808 count=256 of=/data/media/0/persistent.img
Click to expand...
Click to collapse
OllieD said:
as mentioned above:
Click to expand...
Click to collapse
I've done this. It's in the zip file. I thought Al0n was talking about another partition, not /persistent
GaryBlack said:
I've done this. It's in the zip file. I thought Al0n was talking about another partition, not /persistent
Click to expand...
Click to collapse
Sorry I had no notification about your PM.
Just checked the files and was disappointed to see no unlock key in the persistent image...
However the final byte of the partition has been flipped from a 0 to a 1, on the two persistent images I have seen from unlocked devices it was 0.
It would be interesting to see if flipping it back to 0 relocks the boot-loader.
I would try flipping it on my locked device but I no longer have root.
OllieD said:
However the final byte of the partition has been flipped from a 0 to a 1, on the two persistent images I have seen from unlocked devices it was 0.
It would be interesting to see if flipping it back to 0 relocks the boot-loader.
I would try flipping it on my locked device but I no longer have root.
Click to expand...
Click to collapse
Just tried this. Had to flash back to lollipop for Send_Command to work for some reason.
Hex-editied my persistent.img and re-flashed it. No change on the bootloader state. However, I have noticed that the checkbox "Allow OEM unlock" in developer options persists, even over KDZ flashes, but after i flashed the modded persistent.img, the setting was unchecked. Maybe they're related?
OllieD said:
I still stick to my thoughts that no device is safe. its luck of the draw.
Your chance of boot loop is simply a case of how badly manufactured your particular device is, how much you stress it and how old it is.
The issue seems to take on average 6 - 9 months before it cripples most devices.
This is a decent amount of time for LG to play the blame game, argue warranties and swap around/fix as few devices as possible until the G4 is end of life.
Most users upgrade their phones every year or two, so they will be hoping the majority of users will upgrade to a G5.
Now that my thread has been completely de-railed,
Any unlocked users willing to help out?
I still need someone to try:
fastboot erase unlock
and someone to dump their /persistent partition and send me it along with their unlock.bin.
Click to expand...
Click to collapse
here they claim they relocked it... do you think LG can find out .. is it really relocked.?
am afraid to unlock due to the bootloop issue... will this work?
i have h811
http://forum.xda-developers.com/tmobile-g4/help/relock-bootloader-h811-t3372970
Hello.
This is very simple
My phone wont boot up, I've tried everything, litteraly (can't access TWRP btw), I have only fastboot...
Please help... Also I have stock rom for phone, but can't do sh*t with it, cant boot on phone, not via fastboot....
target reported max download size of 471859200 bytes
sending 'recovery' (33114 KB)...
OKAY [ 1.057s]
writing 'recovery'...
OKAY [ 0.806s]
finished. total time: 1.865s
hiSuite recovery reports, that phone is not capable to recover...
Please I need help
What recovery did you flashed? If you were previusly on Nougat you should flash this recovery.
Potato997 said:
What recovery did you flashed? If you were previusly on Nougat you should flash this recovery.
Click to expand...
Click to collapse
But does it work on stock recovery image flashing? EMUI Updater? And ohhh, my bootloader is locked BTW, can't flash ****
If your bootloader is locked you have to unlock it..
Potato997 said:
If your bootloader is locked you have to unlock it..
Click to expand...
Click to collapse
Don't you understand? I can't, I don't have access to system, so I can't get data to fill in the form to get bootloader unlock code
PLEASE HELP
Hi
b0xgam1ng said:
Don't you understand? I can't, I don't have access to system, so I can't get data to fill in the form to get bootloader unlock code
PLEASE HELP
Click to expand...
Click to collapse
Try this: dc-unlocker.com/how-to-read-huawei-bootloader-unlock-code
b0xgam1ng said:
Don't you understand? I can't, I don't have access to system, so I can't get data to fill in the form to get bootloader unlock code
PLEASE HELP
Click to expand...
Click to collapse
Man, you can enter in fastboot mode?
Phone is listed as serial number on PC at fastboot command: devices?
gtdaniel said:
Man, you can enter in fastboot mode?
Phone is listed as serial number on PC at fastboot command: devices?
Click to expand...
Click to collapse
Yes, can do that, and it shows my device... But yhat litteraly all what I have, beside EMUI rom flash... Again, bootloader is locked, I dont have phone id or something to get the code... Also cant flash recovery.img, because bootloader is again... Locked
Help
b0xgam1ng said:
Yes, can do that, and it shows my device... But yhat litteraly all what I have, beside EMUI rom flash... Again, bootloader is locked, I dont have phone id or something to get the code... Also cant flash recovery.img, because bootloader is again... Locked
Help
Click to expand...
Click to collapse
Try this bootloader code: 2279225322717395
Then tell me if you can unlock bootloader.
gtdaniel said:
Try this bootloader code: 2279225322717395
Then tell me if you can unlock bootloader.
Click to expand...
Click to collapse
Holly ****! It actually worked, just out of curiousity, how did you got this code? Thanks
b0xgam1ng said:
Holly ****! It actually worked, just out of curiousity, how did you got this code? Thanks
Click to expand...
Click to collapse
I have a magic touch...
gtdaniel said:
I have a magic touch...
Click to expand...
Click to collapse
Hahahaha, anyway, thanks alot, now I flashed lineageOS and it's pefect, you litteraly saved my life, thanks
No problem, man!
I am glad it worked out and you can revive your phone!
gtdaniel said:
I have a magic touch...
Click to expand...
Click to collapse
wait, what? where did you get that code, and what kind of unlock code is it?
mjz2cool said:
wait, what? where did you get that code, and what kind of unlock code is it?
Click to expand...
Click to collapse
Its from Huawei and is bootloader unlock code.
gtdaniel said:
Its from Huawei and is bootloader unlock code.
Click to expand...
Click to collapse
isn't the unlock code specific to a device normally?
mjz2cool said:
isn't the unlock code specific to a device normally?
Click to expand...
Click to collapse
yes.
gtdaniel said:
yes.
Click to expand...
Click to collapse
so how did you get the code for someone else's phone?
mjz2cool said:
so how did you get the code for someone else's phone?
Click to expand...
Click to collapse
It-s a bootloader code based by IMEI/SN.
Hi.
I´ve a similar problem. My phone stucks on huawei logo. Bootloader is locked but I have bootloader code.
So, when i try to send it with fastboot command, it shows me this error
C:\Telefonia>fastboot oem unlock 143172182xxxxxx
...
FAILED (remote: Command not allowed)
finished. total time: 0.013s
Does anyone knows what´s the problem and how can I solve it.
Thanks in advance. Regards
Posting a new thread was my last resort, so here goes.
I'm looking for a TWRP recovery for a HTC One M9e PCE. It's obviously a rarer model so finding stuff for it is incredibly hard. While searching the forum I came to the conclusion that there once was a file named twrp-3.0.0.2-HIMAR.img hosted on androidfilehost. But all the links are dead.
Does anyone have a copy of that image lying around? I would greatly appreciate if someone would upload it again. If I'm not mistaken the author of that recovery was mars3712, if that helps.
EDIT: I'm aware that there's a repo on github also, though unfortunately it's on a 5.1 base. The device in question is 6.0 MM. Would it matter?
http://www.mediafire.com/folder/2wd1oprpj5ija/HTC_M9_PCE
twrp-3.0.2-0-himar2.img and twrp-3.0.2-1-himar2.img
Click to expand...
Click to collapse
both working perfect on my HTC M9 PCE better use newer
in 10min in folder will be uploaded
2PRGIMG_HIMAR_ML_UHL_M60_SENSE70GP_HTC_Europe_2.32.401.1_Radio_1.1550V70.2508.0304_HU[W.T]_release_488703_combined_signed_2_4.zip
Click to expand...
Click to collapse
to install from sd format sd download rom rename to 2PRGIMG.zip place on sd power and vol- (or + dont remember) and rom should install auto in download mode
Amazing, thanks for the upload. Apparently I need S-OFF to flash this. I've flashed some janky TWRP on this phone before and it never needed S-OFF. Any thoughts? Already running the ROM you posted.
Code:
[email protected]:~/Downloads$ sudo fastboot flash recovery twrp-3.0.2-1-himar2.img
target reported max download size of 134217728 bytes
sending 'recovery' (13544 KB)...
OKAY [ 0.753s]
writing 'recovery'...
(bootloader) Image verification failed...
FAILED (remote: Err! Stop flashing due to S-ON...
)
finished. total time: 1.395s
You unlock bootloader at htcdev.com right?
I will back home in 2/3 hours and look on problem
GeoEgbA said:
You unlock bootloader at htcdev.com right?
I will back home in 2/3 hours and look on problem
Click to expand...
Click to collapse
Yes, the phone is unlocked.
Sorry just back home 2days away. So you must relock bootloader fastboot oem lock restart phone and again unlock bootloader but may use Unlock_code.bin if you have it from first unlock, if no then again generate it on htcdev
I did 2 tests, install clean rom from sd (2PRGIMGizip) and after try flash recovery and get same error as you, one dev i have s-on seccond s-off in both case after flash rom do
fastboot oem lock
Click to expand...
Click to collapse
then
fastboot flash unlocktoken Unlock_code.bin
Click to expand...
Click to collapse
I used old tocken from first unlocking and after this
htc_fastboot flash recovery twrp-3.0.2-1-himar2.img
Click to expand...
Click to collapse
and work perfect in both case
So lock and relock bootloader
Try this and give feedback if all ok, i didnt sleep over 50h so my english grama may be little wrong
Will check here in fiew hs now i go rest.
GeoEgbA said:
Sorry just back home 2days away. So you must relock bootloader fastboot oem lock restart phone and again unlock bootloader but may use Unlock_code.bin if you have it from first unlock, if no then again generate it on htcdev
I did 2 tests, install clean rom from sd (2PRGIMGizip) and after try flash recovery and get same error as you, one dev i have s-on seccond s-off in both case after flash rom do
then
I used old tocken from first unlocking and after this
and work perfect in both case
So lock and relock bootloader
Try this and give feedback if all ok, i didnt sleep over 50h so my english grama may be little wrong
Will check here in fiew hs now i go rest.
Click to expand...
Click to collapse
Hello, do you happen to have the different region (CID HTC__621) RUU for my HTC One M9s (himaruhl)? Thank you very much!
Thanks for the information you provided
---------- Post added at 01:35 PM ---------- Previous post was at 01:28 PM ----------
I have installed twrp data password
Hello,
I have been rooted my phone for a couple of months, but got it broken a few weeks ago. Then I have with the help of this forum restored my phone with a rollback.
But since my phone works again many features are disabled and I seem to have only a testkey. Could someone please help me if I get back to the original version?
Thanks in advance (Sorry for my bad English!).
UselessIdiot said:
Hello,
I have been rooted my phone for a couple of months, but got it broken a few weeks ago. Then I have with the help of this forum restored my phone with a rollback.
But since my phone works again many features are disabled and I seem to have only a testkey. Could someone please help me if I get back to the original version?
Thanks in advance (Sorry for my bad English!).
Click to expand...
Click to collapse
Yup bro, i'm bricking my mate 8 countless already..and twice got test-keys..haha..the easiest solution is with go to eRecovery..yup, but need strong wifi signal..Btw, what is your mate 8 variant?
You can try my tuto in this link - https://forum.xda-developers.com/mate-8/general/solved-nrd90m-test-keys-nougat-stock-t3841805
ceriqdesign said:
Yup bro, i'm bricking my mate 8 countless already..and twice got test-keys..haha..the easiest solution is with go to eRecovery..yup, but need strong wifi signal..Btw, what is your mate 8 variant?
You can try my tuto in this link - https://forum.xda-developers.com/mate-8/general/solved-nrd90m-test-keys-nougat-stock-t3841805
Click to expand...
Click to collapse
It says "Getting package info failed"
My internet connection should be ok.
But I didn't try factory reset yet.
Shall I try?
ceriqdesign said:
Yup bro, i'm bricking my mate 8 countless already..and twice got test-keys..haha..the easiest solution is with go to eRecovery..yup, but need strong wifi signal..Btw, what is your mate 8 variant?
You can try my tuto in this link - https://forum.xda-developers.com/mate-8/general/solved-nrd90m-test-keys-nougat-stock-t3841805
Click to expand...
Click to collapse
A few informations:
Huawei Mate 8
Original model number: NXT-L29C432B582 (current: NXT-L29)
Original build number: QHC0215C28010192 (current: NRD90 test-keys)
IMEI: 868407020986939/868407020966378
Android version: 7.0
EMUI version: 5.0
UselessIdiot said:
A few informations:
Huawei Mate 8
Original model number: NXT-L29C432B582 (current: NXT-L29)
Original build number: QHC0215C28010192 (current: NRD90 test-keys)
IMEI: 868407020986939/868407020966378
Android version: 7.0
EMUI version: 5.0
Click to expand...
Click to collapse
Did you already unlocked bootloader and have TWRP installed?if yes you can try the method using HuRUpdater..use B583 and download all update.zip, update_data_full_public.zip and NXT-L29_hw_eu.zip from Firmware Finder.
UselessIdiot said:
A few informations:
Huawei Mate 8
Original model number: NXT-L29C432B582 (current: NXT-L29)
Original build number: QHC0215C28010192 (current: NRD90 test-keys)
IMEI: 868407020986939/868407020966378
Android version: 7.0
EMUI version: 5.0
Click to expand...
Click to collapse
Download b560 fullota-MF-PV !!!
Flash it using twrp open Kirin edition the one here on the forums
First flash the update zip and then the second file with it
U will be back to stock & receive updates
If anything happens & the system ask for reset simply erase data and redo the process and that's it {I did this many times since I always brick my phone with testing & always worked}
ceriqdesign said:
Did you already unlocked bootloader and have TWRP installed?if yes you can try the method using HuRUpdater..use B583 and download all update.zip, update_data_full_public.zip and NXT-L29_hw_eu.zip from Firmware Finder.
Click to expand...
Click to collapse
The Bootloader is unlocked but TWRP isn't installed.
UselessIdiot said:
The Bootloader is unlocked but TWRP isn't installed.
Click to expand...
Click to collapse
Try to unlock bootloader once again..that happened to me too..after unlock again should be can flash twrp..
ceriqdesign said:
Try to unlock bootloader once again..that happened to me too..after unlock again should be can flash twrp..
Click to expand...
Click to collapse
>fastboot flash recovery twrp-3.0.2-0-next.img
target reported max download size of 471859200 bytes
sending 'recovery' (22020 KB)...
OKAY [ 0.626s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.637s
OEM-Unlock is not Enabled
And I cant relock the bootloader.
ceriqdesign said:
Try to unlock bootloader once again..that happened to me too..after unlock again should be can flash twrp..
Click to expand...
Click to collapse
Update: I hate myself XD
I did a factory reset.
Tried to unlock FRP.
When I wanted to enter the Wi-Fi password, I noticed that I have no keyboard but only the google language input. And I can not change that either. (The voice input does not work of course)
Thank you for your help :angel:
UselessIdiot said:
Update: I hate myself XD
I did a factory reset.
Tried to unlock FRP.
When I wanted to enter the Wi-Fi password, I noticed that I have no keyboard but only the google language input. And I can not change that either. (The voice input does not work of course)
Thank you for your help :angel:
Click to expand...
Click to collapse
I'm sorry..but there always a way to the solution..don't give mate..haha..just give a try..download gboard from another phone then transfer to your phone..
ceriqdesign said:
I'm sorry..but there always a way to the solution..don't give mate..haha..just give a try..download gboard from another phone then transfer to your phone..
Click to expand...
Click to collapse
I can't transfer Gboard from another phone, bacause my phone is stuck in the establishment phase.
I can't give my PC access to my files.
So i cant fill in my google account and because the FRP is still active i cant bypass the google protection. xD
Done! My mobile phone works again XD
But I would like to get away from the test keys.
UselessIdiot said:
Done! My mobile phone works again XD
But I would like to get away from the test keys.
Click to expand...
Click to collapse
did you already tried HuRUpdater method?
ceriqdesign said:
did you already tried HuRUpdater method?
Click to expand...
Click to collapse
TWRP isn't installed.
>fastboot flash recovery twrp-3.1.0-0-next.img
target reported max download size of 471859200 bytes
sending 'recovery' (22108 KB)...
OKAY [ 0.629s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.639s
Could this possibly be related to the not activated oem unlock or FRP (which I can not enable because I can not relock the bootloader)?
UselessIdiot said:
TWRP isn't installed.
>fastboot flash recovery twrp-3.1.0-0-next.img
target reported max download size of 471859200 bytes
sending 'recovery' (22108 KB)...
OKAY [ 0.629s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.639s
Could this possibly be related to the not activated oem unlock or FRP (which I can not enable because I can not relock the bootloader)?
Click to expand...
Click to collapse
is it your oem unlock grey out? what your FRP status?is it still lock?
try this TWRP..download link https://github.com/OpenKirin/androi...leases/download/3.1.1-1/twrp-3.1.1-1-next.img or this one https://mega.nz/#!Y40XCQRD!YGebCrwhMOOTsvyH7d9PMEhJI8x4tg49Ab604_Qbnj8
ceriqdesign said:
is it your oem unlock grey out? what your FRP status?is it still lock?
try this TWRP..download link https://github.com/OpenKirin/androi...leases/download/3.1.1-1/twrp-3.1.1-1-next.img or this one https://mega.nz/#!Y40XCQRD!YGebCrwhMOOTsvyH7d9PMEhJI8x4tg49Ab604_Qbnj8
Click to expand...
Click to collapse
OEM unlock is grey out. FRP still Lock.
Recovery img from dlink doesn't work.
FAILED (remote: Command not allowed)
UselessIdiot said:
OEM unlock is grey out. FRP still Lock.
Recovery img from dlink doesn't work.
FAILED (remote: Command not allowed)
Click to expand...
Click to collapse
try look at this video https://www.youtube.com/watch?v=1CuNxOHgS5E or this https://www.youtube.com/watch?v=fKJuxkfQzmw.. might be help you bro..i'm also stuck in FRP before but forgot how i managed to solved it.
ceriqdesign said:
try look at this video https://www.youtube.com/watch?v=1CuNxOHgS5E or this https://www.youtube.com/watch?v=fKJuxkfQzmw.. might be help you bro..i'm also stuck in FRP before but forgot how i managed to solved it.
Click to expand...
Click to collapse
I bypassed the FRP but in fastboot mode it still shows "FRP lock".
Still cant flash TWRP
">fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (25236 KB)...
OKAY [ 0.718s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.728s"
UselessIdiot said:
I bypassed the FRP but in fastboot mode it still shows "FRP lock".
Still cant flash TWRP
">fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (25236 KB)...
OKAY [ 0.718s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.728s"
Click to expand...
Click to collapse
sorry..but have you renamed twrp to recovery.img?
if it showed FRP Lock in bootloader with green font it's mean that the bypassed is not successful..did you try both method in the video?
p9 lite VNS-L31C185B397 android7.0 emui5.0.4 icannot find twrp (i try mor than 7 type noting is work ) or Stock room to get boot .img to root with magisk
Any ideas or help I would be very thankful .......
hassan-sky said:
p9 lite VNS-L31C185B397 android7.0 emui5.0.4 icannot find twrp (i try mor than 7 type noting is work ) or Stock room to get boot .img to root with magisk
Any ideas or help I would be very thankful .......
Click to expand...
Click to collapse
Working TWRP
hassan-sky said:
Null
Click to expand...
Click to collapse
hassan-sky said:
Null
Click to expand...
Click to collapse
hassan-sky said:
Null
Click to expand...
Click to collapse
-Alf- said:
Working TWRP
Click to expand...
Click to collapse
"FAILED (remote: image verification error)" from fastboot.
-Alf- said:
Working TWRP
Click to expand...
Click to collapse
"FAILED (remote: image verification error)" from fastboot.
hassan-sky said:
"FAILED (remote: image verification error)" from fastboot.
Click to expand...
Click to collapse
Are you sure that bootloader is unlocked? (With unlocked BL you will see that message each time when you reboot: "Your device has been unlocked and can't be trusted").
Try to relock and then unlock the bootloader. (Sometimes the phone and other tools shows phone is unlocked and it is unable to flash recovery.)
-Alf- said:
Are you sure that bootloader is unlocked? (With unlocked BL you will see that message each time when you reboot: "Your device has been unlocked and can't be trusted").
Try to relock and then unlock the bootloader. (Sometimes the phone and other tools shows phone is unlocked and it is unable to flash recovery.)
Click to expand...
Click to collapse
I have used PotatoNV-next-v2.0.1 to open bootloader ,He has given me new code
and yes i see the message"Your device has been unlocked and can't be trusted").
in fastboot mode :
phone unlock
frp unlock
when I tried to relock bootloader With the code he gave me :
FAILED (remote: stat not match)
hassan-sky said:
when I tried to relock bootloader With the code he gave me :
FAILED (remote: stat not match)
Click to expand...
Click to collapse
Then try unlock bootloader again using BL unlock code.
-Alf- said:
Are you sure that bootloader is unlocked? (With unlocked BL you will see that message each time when you reboot: "Your device has been unlocked and can't be trusted").
Try to relock and then unlock the bootloader. (Sometimes the phone and other tools shows phone is unlocked and it is unable to flash recovery.)
Click to expand...
Click to collapse
I have used PotatoNV-next-v2.0.1 to open bootloader ,He has given me new code
and yes i see the message"Your device has been unlocked and can't be trusted").
in fastboot mode :
phone unlock
frp unlock
when I tried to relock bootloader With the code he gave me :
FAILED (remote: stat not match)
-Alf- said:
Then try unlock bootloader again using BL unlock code.
Click to expand...
Click to collapse
FAILED (remote: password wrong)
hassan-sky said:
I have used PotatoNV-next-v2.0.1 to open bootloader ,He has given me new code
and yes i see the message"Your device has been unlocked and can't be trusted").
in fastboot mode :
phone unlock
frp unlock
when I tried to relock bootloader With the code he gave me :
FAILED (remote: stat not match)
FAILED (remote: password wrong)
Click to expand...
Click to collapse
Get BL unlock code using paid service for 4$/€. (dc-unlocker or hcu-client).
-Alf- said:
Get BL unlock code using paid service for 4$/€. (dc-unlocker or hcu-client).
Click to expand...
Click to collapse
ok,and Thank you for being patient
hassan-sky said:
ok,and Thank you for being patient
Click to expand...
Click to collapse
No problem.
did it work? I have the same issue I think. but i don't want to buy a code if PotatoNV already did the job and the problem is elsewhere
Elfenfreund said:
did it work? I have the same issue I think. but i don't want to buy a code if PotatoNV already did the job and the problem is elsewhere
Click to expand...
Click to collapse
As far as I know Potatonv method was made for Kirin 960/659/655. On 650 may or may not work correctly...
-Alf- said:
As far as I know Potatonv method was made for Kirin 960/659/655. On 650 may or may not work correctly...
Click to expand...
Click to collapse
oh i see. thank you
-Alf- said:
Get BL unlock code using paid service for 4$/€. (dc-unlocker or hcu-client).
Click to expand...
Click to collapse
I'm also getting the error FAILED (remote: image verification error) bootloader unlocked with PotatoNV.
What if my device (VNS-L23) isn't listed on those sites?
Mago6246 said:
What if my device (VNS-L23) isn't listed on those sites?
Click to expand...
Click to collapse
Ask Mr. Valdemaras
https://www.dc-unlocker.com/search?q=Vns-l23