Stuck in Nougat HELL : solved - Mate 8 Q&A, Help & Troubleshooting

I made the fatal mistake of upgrading to Nougat. ( NXT-L29C432502 # 16 on the OP list)
All looked great until I started to see the negative side of this Beta Nougat.
After much time of trying various fixes. I'm at a point that when Nougat loads for the initial launch.
Setting Language ,Enhanced Wifi,declining finger lock.
The software boot loops to the Language selection page.
No setting mode or dialer that will allow me to dload or enter USB Debugging.
I can dload by using my SD card which works using the power and volume buttons but does not install a full system
that will boot.
SK tools kit and ADB will not fully detect my device because of the USB Debugging not being turned on.
If I could get Debugging turned on I feel that I could resolve my disaster.
I hope I don't have to wait until March to get the "Full" Nougat update.
I'm embarrassed to admit how many days I've screwed with this device.

With srk tool you don't need usb debugging,you can use fastboot mode instead. You can flash recovery if needed.
Anyway try to downgrade using the rollback packages .

gm007 said:
With srk tool you don't need usb debugging,you can use fastboot mode instead. You can flash recovery if needed.
Anyway try to downgrade using the rollback packages .
Click to expand...
Click to collapse
I keep getting on the adb screen device null or can't find device.
Hisute can't find the device also.
No debugging. No ADB or device detection. I've done the Windows drivers and device manager USB updates.
I wish I still drank damn it.

I used DC-Unlocker and paid 15 euros and did an "FRP" wipe.
Now I'm back to an operating device on Nougat .
May attempt downgrade later I really need a "Bluetooth" working device.

kdkinc said:
I used DC-Unlocker and paid 15 euros and did an "FRP" wipe.
Now I'm back to an operating device on Nougat .
May attempt downgrade later I really need a "Bluetooth" working device.
Click to expand...
Click to collapse
With dc-unlocker you can unlock frp lock?

Related

[Q] FRP lock help--j700T Marshmallow

Hello,
I wonder if someone would help me FRP unlock my phone. It is a T-mobile sm-J700t 2015. I have searched the forum but don't see a clear answer.
I have tried (from Youtube) the USB cable method, the camera method and flashing the 10/2016 stock firmware through ODIN. In Odin I get an error: "Complete(Write) operation failed". I cannot turn on USB debugging of course because I cannot get into the device. Haven't tried updating with Kies yet because I'm nervous they'll patch any additional back doors I could try.
I am somewhat experienced at flashing and such and I think there must be a way to completely wipe the device and flash new firmware but I don't see instructions for that.
Thanks in advance!
Odin v3.10.7 & v3.12.3
Recovery: Haven't changed
USB installed from Samsung Kies (made sure Kies isn't running)
Firmware: J700TUVU2APJ3_J700TTMB2APJ3_TMB.tar.md5
Where I got firmware: https://qc3.androidfilehost.com/dl/...224401143/J700TUVU2APJ3_J700TTMB2APJ3_TMB.zip
Anyone? Still locked out of my phone. :crying:
Reboot normaly > go to settings > developer setting > oem unlock check yes
#gggirlgeek
Reboot normaly > go to settings > developer setting > oem unlock > check yes
I can't get into the phone at all. It is FRP (Google) locked because I did a factory reset from recovery. I can only manipulate it from PC or stock recovery. I have ADB, Odin and Samsung Kies on my PC if that helps.
What is the reason I am getting the ODIN error: "Complete(Write) operation failed"? Is it due to the FRP lock?
If not, would flashing the same stock firmware even help? (I have read that it's not possible to flash older firmware versions.)
Is the boot partition where the FRP status is stored? Is it possible to flash a new boot image to reset it?
I assume flashing a custom recovery would be useless? I doubt it could be done without USB debugging/ADB being enabled anyway.
One of the reason for that odin error is flashing an old build of stock ROM, your guess is right
Even if you are able to flash a stock FW via ODIN you'll still not be able to boot to your OS.
You have to login using the same google id that was previously logged in
OR you have to bypass the Google Account Login Screen.
There are varous method on youtube (i know you saw them) to bypass that screen (Side Sync method worked for me at the 10th attempt) inorder to install a 3rd party app either to
1. enable the developer option or enable OEM unlock ( to flash custom ROM or custom recovery)
OR
2. to overwrite the previous google account saved with your new account details. (THIS ONE HELPED ME)
WITH FRP LOCK ON, ODIN SHOULD NOT GIVE YOU ERROR ONLY IF YOU ARE FLASHING STOCK ROM. BUT STILL YOU WILL BE LOCKED WITH GOOGLE ACCOUNT LOGIN SCREEN BECAUSE OF FRP LOCK ON AND STOCK ROM
FRP info. is saved in Sboot. Flashing a new sboot works only for devices those were never upgraded to Android 6. For J7 2015 that was upgraded to android 6, flashing Sboot bricks the phone as said by a cell phone repair agent
Regards,
Sid
@saddam.khan999 : Thank you so much for replying. This is helpful. :highfive:
What did you do to get the sidesync to work? Mine wouldn't even connect to Sidesync on my PC.
Tried different USB ports, and even different PC's to get it to pop up on the phone. Tried old usb drivers too. Sidesync never senses it, and My Computer only show MTP folder that won't accept any file pasted to it.
You did this with Android 6.0.1 October 2016 update? They fix more holes every time.
Also, can you give me the link to the unlock tutorial you used with Sidesync? Just want to compare my method.
Hi,
gggirlgeek said:
This is helpful. :highfive:
Click to expand...
Click to collapse
How grateful I am to read the above line! Thanks :good:
gggirlgeek said:
You did this with Android 6.0.1 October 2016 update?
Click to expand...
Click to collapse
Yes on Android 6.0.1 but i dont remember the build date.
gggirlgeek said:
Also, can you give me the link to the unlock tutorial you used with Sidesync?
Click to expand...
Click to collapse
I tired two different tutorials of SideSync to crack it. Once I reach home in the next 10 hours from now. I'll search on youtube and give u the links. Right now I cannot remember it.
gggirlgeek said:
What did you do to get the sidesync to work? Mine wouldn't even connect to Sidesync on my PC.
Click to expand...
Click to collapse
I followed below step to fix popup issue
1. Uninstall all samsung apps like, Kies, SmartSwitch, SideSync everything.
2. Uninstall Samsung USB drivers
3. Install SmartSwicth (to get best drivers)
4. Now install SideSync (latest)
5. Open SideSync and check for OTA updates in your PC (update it if available)
I give up. I'm going to pay somebody. He can use one of those low-level programs to unlock it remotely. It only costs $15. Well worth it. Wish me luck!
gggirlgeek said:
I give up. I'm going to pay somebody. He can use one of those low-level programs to unlock it remotely. It only costs $15. Well worth it. Wish me luck!
Click to expand...
Click to collapse
@gsmDabbler this guy says he/she can solve FRP issue for 5$ on skype. I dont know if he's fake or real. Best of luck
1. At welcome screen push next.
2. Connect to wifi and push next.
3. Accept terms and conditions and push next
4. Attempt to sign in to your google account.
5. On loopback to sign in page, push back intel you see the welcome screen again.
6. Push emergency dialer.
7. Dial 112
8. Put in on speaker and when the disbatcher askes what is your emergency, quickly swipe where the speaker option is to your left and click on email.
9. Ask the disbatcher for the number for non-emergency. (EXTREAMLY IMPORTANT TO NOT SKIP THIS STEP)
10. Sign into your email.
11. Compose a new message.
12. On another device download drive.google.com/file/d/0B3quVdCaxqLfaG9VY2xjd3hhWmM/view?usp=drivesdk[/url]
13. Move this file to a microsd card, and put it into the j7.
14. Push attach
15. Locate your sdcard and select es file explorer.
16. Once attached to the email, click on the box inside the email that says es file explorer. If redirected to security setting check the box that says "Unknown Sources".
17. If then redirected to install screen for es file explorer, install app and skip the next step.
18. Push back intel your on the screen with your new composed email with attachment, and once again click on es file explorer, and then install...
19. After install, restart your phone.
20. On welcome screen, plug your j7 into a power source.
21. Toggle your power button off, and then back on.
22. Click on the far right last bubble.
23. On home screen of es file explorer, take the sdcard out of the j7 and put back into the extra device you downloaded es file explorer to, and download these 2 files.
drive.google.com/file/d/0B3quVdCaxqLfNVFvMHlOWnNnY2M/view?usp=drivesdk[/url]
&
drive.google.com/file/d/0B3quVdCaxqLfc0gyRTBTNGNXOTA/view?usp=drivesdk[/url]
24. Copy these files to your microsd card from earlier, and put back into your j7.
------------> continued to next post of mine!
gggirlgeek said:
Hello,
I wonder if someone would help me FRP unlock my phone. It is a T-mobile sm-J700t 2015. I have searched the forum but don't see a clear answer.
I have tried (from Youtube) the USB cable method, the camera method and flashing the 10/2016 stock firmware through ODIN. In Odin I get an error: "Complete(Write) operation failed". I cannot turn on USB debugging of course because I cannot get into the device. Haven't tried updating with Kies yet because I'm nervous they'll patch any additional back doors I could try.
I am somewhat experienced at flashing and such and I think there must be a way to completely wipe the device and flash new firmware but I don't see instructions for that.
Thanks in advance!
Odin v3.10.7 & v3.12.3
Recovery: Haven't changed
USB installed from Samsung Kies (made sure Kies isn't running)
Firmware: qc3.androidfilehost.com/dl/T2pLZbjUe0enTeLqQNLjsA/1482428974/385035244224401143/J700TUVU2APJ3_J700TTMB2APJ3_TMB.zip"]J700TUVU2APJ3_J700TTMB2APJ3_TMB[/URL].tar.md5
Where I got firmware: qc3.androidfilehost.com/dl/T2pLZbjUe0enTeLqQNLjsA/1482428974/385035244224401143/J700TUVU2APJ3_J700TTMB2APJ3_TMB.zip[/URL]
Click to expand...
Click to collapse
gggirlgeek said:
Hello,
I wonder if someone would help me FRP unlock my phone. It is a T-mobile sm-J700t 2015. I have searched the forum but don't see a clear answer.
I have tried (from Youtube) the USB cable method, the camera method and flashing the 10/2016 stock firmware through ODIN. In Odin I get an error: "Complete(Write) operation failed". I cannot turn on USB debugging of course because I cannot get into the device. Haven't tried updating with Kies yet because I'm nervous they'll patch any additional back doors I could try.
I am somewhat experienced at flashing and such and I think there must be a way to completely wipe the device and flash new firmware but I don't see instructions for that.
Thanks in advance!
Odin v3.10.7 & v3.12.3
Recovery: Haven't changed
USB installed from Samsung Kies (made sure Kies isn't running)
Firmware: J700TUVU2APJ3_J700TTMB2APJ3_TMB.tar.md5
Where I got firmware: https://qc3.androidfilehost.com/dl/...224401143/J700TUVU2APJ3_J700TTMB2APJ3_TMB.zip
Click to expand...
Click to collapse
Its simple. Just flash the latest firmware through odin and you'll be booted on stock.
Don't forget to turn on OEM unlock next time
?guys...no.. just Go to settings tap build 7 times go to developer options, turn on oem unlock, turn on usb debugging.ta dah.
mohitmallick17 said:
Its simple. Just flash the latest firmware through odin and you'll be booted on stock.
Don't forget to turn on OEM unlock next time
Click to expand...
Click to collapse
^^^^^^ Does flashing the latest firmware really work
?????????????????????????????????????????????
victhesunshine said:
^^^^^^ Does flashing the latest firmware really work
?????????????????????????????????????????????
Click to expand...
Click to collapse
Just take out your battery and reboot, turn oem unlock on and do whatever.its simple.
gggirlgeek said:
Hello,
I wonder if someone would help me FRP unlock my phone. It is a T-mobile sm-J700t 2015. I have searched the forum but don't see a clear answer.
I have tried (from Youtube) the USB cable method, the camera method and flashing the 10/2016 stock firmware through ODIN. In Odin I get an error: "Complete(Write) operation failed". I cannot turn on USB debugging of course because I cannot get into the device. Haven't tried updating with Kies yet because I'm nervous they'll patch any additional back doors I could try.
I am somewhat experienced at flashing and such and I think there must be a way to completely wipe the device and flash new firmware but I don't see instructions for that.
Thanks in advance!
Odin v3.10.7 & v3.12.3
Recovery: Haven't changed
USB installed from Samsung Kies (made sure Kies isn't running)
Firmware: J700TUVU2APJ3_J700TTMB2APJ3_TMB.tar.md5
Where I got firmware: https://qc3.androidfilehost.com/dl/...224401143/J700TUVU2APJ3_J700TTMB2APJ3_TMB.zip
Click to expand...
Click to collapse
Saw a same issue please check & follow this steps if it helps you some way.
Download the latest samfirm tool available on xda.
Open the samfirm tool. Enter model and region. Tick Auto and binary nature.
Click on Check update. It will show the latest firmware available on samsung server.
Then click on download. It will download four file full firmware. Then flash it through odin.
You need a strong internet connection to download the file.
fullofhell said:
Just take out your battery and reboot, turn oem unlock on and do whatever.its simple.
Click to expand...
Click to collapse
Not so simple.
During FRP Lock you are restricted to the google sign in page, locked out of everything else. Cannot even pull down the status bar. So no way to get to settings.
This can be done via ADB , but only if you had USB Debugging enabled prior.
I just obtained a used J7000T1 and FRP lock is activated , Even on the bootloader it displays "FRP Locked" . USB Debugging was never enabled .
If I find a way , I'll post. Any one have luck yet?
Once " FRP Locked " is off the bootloader, I'm sure we can just load a recovery / rom via Odin .... But that's where I am a stuck of course.
hightech316 said:
Not so simple.
During FRP Lock you are restricted to the google sign in page, locked out of everything else. Cannot even pull down the status bar. So no way to get to settings.
This can be done via ADB , but only if you had USB Debugging enabled prior.
I just obtained a used J7000T1 and FRP lock is activated , Even on the bootloader it displays "FRP Locked" . USB Debugging was never enabled .
If I find a way , I'll post. Any one have luck yet?
Once " FRP Locked " is off the bootloader, I'm sure we can just load a recovery / rom via Odin .... But that's where I am a stuck of course.
Click to expand...
Click to collapse
I had this happen last Feb when I got the phone and was trying to install twrp, and it says frp lock when I tried flashing the recovery tar via odin. I literally took out the battery rebooted back into the OS and turned on oem unlock and USB Debugging and it was fine then when I flashed twrp. I have never heard of this other issue u speak of. The phone has an unlocked bootloader to begin with. If u are stuck in a Google sign in page, I would download the Samsung z3 tool and make sure u have drivers installed and unlock the frp that way.it does have an option for frp lock
fullofhell said:
I had this happen last Feb when I got the phone and was trying to install twrp, and it says frp lock when I tried flashing the recovery tar via odin. I literally took out the battery rebooted back into the OS and turned on oem unlock and USB Debugging and it was fine then when I flashed twrp. I have never heard of this other issue u speak of. The phone has an unlocked bootloader to begin with. If u are stuck in a Google sign in page, I would download the Samsung z3 tool and make sure u have drivers installed and unlock the frp that way.it does have an option for frp lock
Click to expand...
Click to collapse
Thanks.
Drivers are installed.
Just cannot move from the google sign in.
There is a guide that shows how to use a USB drive with a shortcut apk on it , hooked up via OTG and is able to open settings. Although that did not work for me as well...
Maybe N version is different than MM ?
Almost the same problem here.....but in my j700f, I can't boot to recovery at all...can't flash stock firmware also due frp locked

[try][experimental] unlock and re-lock bootloader

Warning: The whole procedure is fully Experimental, this tool can brick your device, I will not responsible if you brick your device, try it with your own risk.
I have not tried the method yet, this tool performs so many function with NOKIA 6 too, but I didn't use the UNLOCK BOOT LOADER option yet, I want a tester who has already unlocked the bootloader and want to re-lock it, try it and give a feedback if it works
I would like to share a tool with you guys, this tool can perform many functions
Note: turn off your antivirus first then proceed
Download the tool from here
https://mega.nz/#!9Up1XJ5a!1nhxdqtIljdItjgPers9qM0ry8d4Dhc8HOX5pJ2mEQI
This tool is patched already so you do not need to crack it or use any BOX for it.
This tool works without box or modem
You only need to see if your PC is up to date and all drivers and frameworks are up to date or not
Now open you tool
REMEMBER: Turn off your Anti virus application before launching the app
Now an UI will appear, select "MIRACLE CRACK 2.27A" from there.
Now connect your device to your PC. Make sure your on DEVELOPER MODE
Then a new UI will appear, select on "ANDROID" Then "HOME ADB"
After that if you want to unlock your BOOTLOADER, reboot your device into download mode then select unclock bootloader from the options
Or RE-LOCK option is also available
Finally click start button
Done
Hit thanks button if you find this useful
happy flashing ​
Ok. I will test and report to you.
My data is too much I will weigh.
taicracker said:
Ok. I will test and report to you.
My data is too much I will weigh.
Click to expand...
Click to collapse
Okay sure, thank you, also try if custom recovery could be install by this tool or not...
May this tool will help many users in future.. :fingers-crossed:
Does the Nokia device have exclusive system keys such as Sony (DRM key) devices? Unlocking loses those keys. Can you tell me. And I will test this tool soon.
taicracker said:
Does the Nokia device have exclusive system keys such as Sony (DRM key) devices? Unlocking loses those keys. Can you tell me. And I will test this tool soon.
Click to expand...
Click to collapse
I don't know buddy about that, i didn't had any sony device in tha past.
Sorry...
I won't force you to test this tool my dear friend
Its up to you :good:
Tell me about this, if this work
Hope for the best :fingers-crossed:
Ok I will test
taicracker said:
Ok I will test
Click to expand...
Click to collapse
Sure
sltushar said:
Sure
Click to expand...
Click to collapse
Could not connect to phone. Do you have any solutions?
Log:
Welcome to use Miracle Box
(World's First Fuzzy Logic Based Tool)
Update:16-01-09
Connected OK.
Check Authentication...
Check the new version.
Abort by User
Fuzzy Logic Method is very safe and reliable !
Must fastboot mode.
Follow the prompts in the phone screen
Note:After Bootloader Unlock Need Flash
Must fastboot mode.
Follow the prompts in the phone screen
Note:After Bootloader Unlock Need Flash
Connecting to Phone,Wait..
Timeout. Please Check Pinouts or ReDo
Abort by User
Must fastboot mode.
Follow the prompts in the phone screen
Note:After Bootloader Unlock Need Flash
Connecting to Phone,Wait..
>>Timeout. Please Check Pinouts or ReDo
taicracker said:
Could not connect to phone. Do you have any solutions?
Log:
Welcome to use Miracle Box
(World's First Fuzzy Logic Based Tool)
Update:16-01-09
Connected OK.
Check Authentication...
Check the new version.
Abort by User
Fuzzy Logic Method is very safe and reliable !
Must fastboot mode.
Follow the prompts in the phone screen
Note:After Bootloader Unlock Need Flash
Must fastboot mode.
Follow the prompts in the phone screen
Note:After Bootloader Unlock Need Flash
Connecting to Phone,Wait..
Timeout. Please Check Pinouts or ReDo
Abort by User
Must fastboot mode.
Follow the prompts in the phone screen
Note:After Bootloader Unlock Need Flash
Connecting to Phone,Wait..
>>Timeout. Please Check Pinouts or ReDo
Click to expand...
Click to collapse
Do your computer has all driver and framework installed properly?
And do your phone is developer mode on, also make sure in developer mode allow oem unlock option is turned on.
Because my phone is working fine with it, just not ready right now for any brick, damaged, dead cause to device, because this is only the source right now i have.
Try rebooting to fastboot from ADB option on the tool, if it works then it might unlock the bootloader too, check the drivers..
Finger crossed :fingers-crossed:
sltushar said:
Do your computer has all driver and framework installed properly?
And do your phone is developer mode on, also make sure in developer mode allow oem unlock option is turned on.
Because my phone is working fine with it, just not ready right now for any brick, damaged, dead cause to device, because this is only the source right now i have.
Try rebooting to fastboot from ADB option on the tool, if it works then it might unlock the bootloader too, check the drivers..
Finger crossed :fingers-crossed:
Click to expand...
Click to collapse
The ADB system works well, maybe ROOT is.
But fastboot mode does not work. I also try to put the phone on fastboot mode with OST (edit fone information)
But Miracle Box does not work with fastboot of Nokia 6. (Wait for developer update)
You cracked the picture as old version, maybe it Nokia 6 not support )
taicracker said:
The ADB system works well, maybe ROOT is.
But fastboot mode does not work. I also try to put the phone on fastboot mode with OST (edit fone information)
But Miracle Box does not work with fastboot of Nokia 6. (Wait for developer update)
You cracked the picture as old version, maybe it Nokia 6 not support )
Click to expand...
Click to collapse
Well, i think i need to try it on my device, i will, but not now, later on
I just reconsider and can not Root with this tool always
taicracker said:
I just reconsider and can not Root with this tool always
Click to expand...
Click to collapse
Fine, can you try one more thing, see if it can flash recovery with this tool.
sltushar said:
Fine, can you try one more thing, see if it can flash recovery with this tool.
Click to expand...
Click to collapse
Are not! The fastboot (Flash) and ADB modes do not work, just see the phone's information. I tried the tool buttons but it does not work even ROOT.
taicracker said:
Are not! The fastboot (Flash) and ADB modes do not work, just see the phone's information. I tried the tool buttons but it does not work even ROOT.
Click to expand...
Click to collapse
Well, for me both worked, but i didn't tried tha bootloader option
I will try once i get professional job, since this is only the source right now
May be you're already rooted or custom recovery installed so its not working or may be driver problem, because my system is detecting in both adb and fastboot mode..
sltushar said:
Well, for me both worked, but i didn't tried tha bootloader option
I will try once i get professional job, since this is only the source right now
May be you're already rooted or custom recovery installed so its not working or may be driver problem, because my system is detecting in both adb and fastboot mode..
Click to expand...
Click to collapse
I flashed the software through OST and tried ROOT but failed. I tried the other options but failed. ^^. It's possible to share your gadget with your Nokia 6, and my TA-1000.
taicracker said:
I flashed the software through OST and tried ROOT but failed. I tried the other options but failed. ^^. It's possible to share your gadget with your Nokia 6, and my TA-1000.
Click to expand...
Click to collapse
May be, mine is TA-1021, May be both having different bootloader
Why dont you flash MENA firmware and try one more time, may be this work
Because it works on stock android, and your one is Chinese varient
sltushar said:
May be, mine is TA-1021, May be both having different bootloader
Why dont you flash MENA firmware and try one more time, may be this work
Because it works on stock android, and your one is Chinese varient
Click to expand...
Click to collapse
Ok. I will flash my TA-1025 firmware to my phone and try unlocking the bootloader again. Or wait for the updated Android 8.0 Oreo sure Unlock the bootloader (I think so) Because Nokia 8 can Unlock bootloader already.
taicracker said:
Ok. I will flash my TA-1025 firmware to my phone and try unlocking the bootloader again. Or wait for the updated Android 8.0 Oreo sure Unlock the bootloader (I think so) Because Nokia 8 can Unlock bootloader already.
Click to expand...
Click to collapse
Sure brother, i have somany tools, let see which one can unlock it
:fingers-crossed:
sltushar said:
Sure brother, i have somany tools, let see which one can unlock it
:fingers-crossed:
Click to expand...
Click to collapse
I tried flashing fw (nb0) of TA-1025 into my TA-1000 and tried ROOT with unlock bootloader but this tool is really not working.
Log:
http://forum.gsmhosting.com/vbb/12807875-post1.html
Miracle ViVo Tool 2.02 (New) 5th Jan 2018
http://forum.gsmhosting.com/vbb/12885172-post1.html
How to Use Miracle Video Tutor
http://video.amiraclebox.com
______________________________
www.dealer.amiraclebox.com
Buy 1 year Support Activation
Buy Huawei Activation Pack
________[Social Site]_________
https://facebook.com/amiracleteam
https://twitter.com/amiracleteam
______________________________
Must fastboot mode.
Follow the prompts in the phone screen
Note:After Bootloader Unlock Need Flash
Connecting to Phone,Wait..
Abort by User
Connecting to Phone,Wait..
Connecting to Phone,Wait..ok
checking info...
Model:TA-1025
Android Ver:7.1.1
Rooting...
ROOT Fail!

The Unofficial Official Nokia 8 Bootloader Unlock Method

If you try to use the bootloader unlocker apk from Nokia and your Nokia 8 has an android version that's past a certain version, the apk will flat out fail with a "Device not support." error message. And chances are, your Nokia 8 will be at an incompatible android version. So to unlock the bootloader, you will need to downgrade your phone to a legitimate version of android 8.1.0 so the apk will not error out and get you a verification code. This guide will show you how. NOTE THAT THIS METHOD WILL ERASE ALL INTERNAL DATA ON YOUR PHONE.
-
This update zip is what you need for the TA-1004: https://android.googleapis.com/pack.../f9cb380bd9c2bf1b6ddebcab9dcf389843eb2d39.zip
It may be different for the TA-1012, but according to that earlier post, it does not seem to be the case. Nevertheless, just to be safe, here's the zip for the TA-1012: https://android.googleapis.com/pack.../139c94fd08f52fbd3b852ab4ef5c6515fffb784e.zip (I don't have a TA-1012 so I wasn't able to test this particular zip.)
So basically, to make sure there's no problems, make sure in the Developer's options on the phone that OEM unlocking is enabled, then put your SD card into the phone. Plug the phone into your computer. Copy the update zip that you need somewhere onto the SD card. Disconnect the USB cable. Shut down the phone. Then, while holding down the Volume Up button, reconnect the USB cable. You should see a sad android with "No command" displayed. Now release the Volume Up button. Then hold down the power button and then JUST PRESS once on the Volume Up button. You should be at a recovery menu. Using the volume keys, scroll down to the 'Apply update on SD card' option and select it. Select the zip that you copied over to the SD card earlier and then let it install for a while. It will probably pop up with a 'timestamp too old' error, but just ignore this. The update will install anyway. Then once it's done, do a factory reset on the phone and then shut down. MAKE SURE THERE'S NO SIM CARD IN THE PHONE.
Now that's out of the way, boot the phone up again and just click through the first-time setup screens but DO NOT ENABLE WI-FI or any kind of internet connection. We don't want the phone to update itself back to Android 9. Now plug the phone in again. Copy the bootloaderunlocker apk from Nokia's website onto the phone. Install it. Put in the email address you want the unlock key emailed to. Then voila! You'll get the verification code. Put it into the form on Nokia's website and you'll be emailed an unlock.key file. From there, the site will tell you how to proceed.
A HUGE thanks to: THMSP and frankoid
They did all the work. <3
why another topic ?!
foxbatul said:
why another topic ?!
Click to expand...
Click to collapse
Because I don't expect people to dig around in all the Nokia 8 Guide threads to find the exact and, to my knowledge, only way to unlock the bootloader. Furthermore, I found this solution in a sort of unrelated thread, which would make the solution even harder to find for the average user.
S5Guy said:
Because I don't expect people to dig around in all the Nokia 8 Guide threads to find the exact and, to my knowledge, only way to unlock the bootloader. Furthermore, I found this solution in a sort of unrelated thread, which would make the solution even harder to find for the average user.
Click to expand...
Click to collapse
I understant but not.
Here it's not the place for lazy ones. Or for apple boys.
Unlock, modding, ROMs are for people with other approach. So this kind of topics make more noise instead to help.
Just my 2 cents.
BTW - thank you posting "downgrade to oreo" procedure.
it s the offline one ( my choice was to use "register to beta" and" unregister").
no need SD card or something, just a good wifi connection and patience.
Thanks for this. I just noticed that the "OEM unlocking" is disabled and greyed out on my TA-1012 device. Will it still work?
I cant get into the Phone without establishing an Internet connection, any tips?
Thank you so much OP this method worked perfectly I finally was able to unlock the bootloader
There seems no way for me to get past the Wifi selection page, how did all of you got into the system?
Ok solved this one, had to Update to P remove the Google Account linked to the Device and downgrade again.
It's Part of the Factory Reset Protection that you cant skip the Wifi and Update Screens.
Thank you for posting this guide, it got me to unlocking the bootloader on my TA-1004 after I received the described "Device not support" error.
I enabled "OEM unlocking" before downgrading my firmware and the option was grayed out for me afterwards. However the bootloader unlock still worked correctly other than being forced to us a Mac as none of my windows machines would show the device in fastboot mode.
ma401 said:
Thank you for posting this guide, it got me to unlocking the bootloader on my TA-1004 after I received the described "Device not support" error.
I enabled "OEM unlocking" before downgrading my firmware and the option was grayed out for me afterwards. However the bootloader unlock still worked correctly other than being forced to us a Mac as none of my windows machines would show the device in fastboot mode.
Click to expand...
Click to collapse
If only Nokia 8 had support for custom roms. Im stuck on the december security patch of Pie because it has a prerooted boot img posted somewhere on this forum. Ot would be fun to play around with a google-free custom rom like lineageOS. But sadly devs dont seem to give a damn about the phone
MDV106 said:
If only Nokia 8 had support for custom roms. Im stuck on the december security patch of Pie because it has a prerooted boot img posted somewhere on this forum. Ot would be fun to play around with a google-free custom rom like lineageOS. But sadly devs dont seem to give a damn about the phone
Click to expand...
Click to collapse
I think we can thank HMD for that by making unlocking the bootloader so difficult. I only ended up buying the Nokia 8 because I got it for such a good deal ($220 CAD) and needed a temporary phone to tide me over until I can get something better. I feel sorry for anyone who paid full price for this phone and I don't blame developers for moving to something more accessible.
S5Guy said:
If you try to use the bootloader unlocker apk from Nokia and your Nokia 8 has an android version that's past a certain version, the apk will flat out fail with a "Device not support." error message. And chances are, your Nokia 8 will be at an incompatible android version. So to unlock the bootloader, you will need to downgrade your phone to a legitimate version of android 8.1.0 so the apk will not error out and get you a verification code. This guide will show you how. NOTE THAT THIS METHOD WILL ERASE ALL INTERNAL DATA ON YOUR PHONE.
-
This update zip is what you need for the TA-1004: https://android.googleapis.com/pack.../f9cb380bd9c2bf1b6ddebcab9dcf389843eb2d39.zip
It may be different for the TA-1012, but according to that earlier post, it does not seem to be the case. Nevertheless, just to be safe, here's the zip for the TA-1012: https://android.googleapis.com/pack.../139c94fd08f52fbd3b852ab4ef5c6515fffb784e.zip (I don't have a TA-1012 so I wasn't able to test this particular zip.)
So basically, to make sure there's no problems, make sure in the Developer's options on the phone that OEM unlocking is enabled, then put your SD card into the phone. Plug the phone into your computer. Copy the update zip that you need somewhere onto the SD card. Disconnect the USB cable. Shut down the phone. Then, while holding down the Volume Up button, reconnect the USB cable. You should see a sad android with "No command" displayed. Now release the Volume Up button. Then hold down the power button and then JUST PRESS once on the Volume Up button. You should be at a recovery menu. Using the volume keys, scroll down to the 'Apply update on SD card' option and select it. Select the zip that you copied over to the SD card earlier and then let it install for a while. It will probably pop up with a 'timestamp too old' error, but just ignore this. The update will install anyway. Then once it's done, do a factory reset on the phone and then shut down. MAKE SURE THERE'S NO SIM CARD IN THE PHONE.
Now that's out of the way, boot the phone up again and just click through the first-time setup screens but DO NOT ENABLE WI-FI or any kind of internet connection. We don't want the phone to update itself back to Android 9. Now plug the phone in again. Copy the bootloaderunlocker apk from Nokia's website onto the phone. Install it. Put in the email address you want the unlock key emailed to. Then voila! You'll get the verification code. Put it into the form on Nokia's website and you'll be emailed an unlock.key file. From there, the site will tell you how to proceed.
A HUGE thanks to: THMSP and frankoid
They did all the work. <3
Click to expand...
Click to collapse
Hello i too tried unlocking my nokia 8 but the laptop doesnt recognise my phone in fastboot Mode.i need help i installed all drivers but the same problem arises
shivaji namburu said:
Hello i too tried unlocking my nokia 8 but the laptop doesnt recognise my phone in fastboot Mode.i need help i installed all drivers but the same problem arises
Click to expand...
Click to collapse
try fastboot -i 0x2e04 [Your_Command]
sumitinhome said:
try fastboot -i 0x2e04 [Your_Command]
Click to expand...
Click to collapse
Actually even pc doesnt detect the device and it doesn't show in my pc section
---------- Post added at 04:57 PM ---------- Previous post was at 04:55 PM ----------
sumitinhome said:
try fastboot -i 0x2e04 [Your_Command]
Click to expand...
Click to collapse
What is that i didn't get it will it work.....?
If possible put the command clearly ....to understand
shivaji namburu said:
Actually even pc doesnt detect the device and it doesn't show in my pc section
---------- Post added at 04:57 PM ---------- Previous post was at 04:55 PM ----------
What is that i didn't get it will it work.....?
If possible put the command clearly ....to understand
Click to expand...
Click to collapse
If pc is not detecting the phone the its driver problem. try to install proper drivers.
sumitinhome said:
If pc is not detecting the phone the its driver problem. try to install proper drivers.
Click to expand...
Click to collapse
I mean it detects when the phone is in nornal mode but when mobile is booted into fastboot mode it doesn't detect
shivaji namburu said:
I mean it detects when the phone is in nornal mode but when mobile is booted into fastboot mode it doesn't detect
Click to expand...
Click to collapse
Yes i understood, make sure you are using latest adb drivers.
More on it. Make sure you have USB debugging on from Developers options. Also make sure oem unlocking option is on.
1 - Connect your phone to pc while powered on.
2 - From adb folder open command prompt and type adb devices (If your device is detected in adb mode while powered on)
2.1 - if not detected in adb devices.. then go to developer settings and revoke USB debugging authorizations. then again repeat the above process in point no. 2.
3 - if detected now then type adb reboot bootloader, let it reboot in download mode.
4. then type 'fastboot flash unlock [your unlock key]' if this doesnt work then try 'fastboot -i 0x2e04 flash unlock [unlock key]'
5. after that either 'fastboot oem unlock' or 'fastboot -i 0x2e04 oem unlock'
See if this works.
Struck on Nokia Logo
S5Guy said:
If you try to use the bootloader unlocker apk from Nokia and your Nokia 8 has an android version that's past a certain version, the apk will flat out fail with a "Device not support." error message. And chances are, your Nokia 8 will be at an incompatible android version. So to unlock the bootloader, you will need to downgrade your phone to a legitimate version of android 8.1.0 so the apk will not error out and get you a verification code. This guide will show you how. NOTE THAT THIS METHOD WILL ERASE ALL INTERNAL DATA ON YOUR PHONE.
-
This update zip is what you need for the TA-1004: https://android.googleapis.com/pack.../f9cb380bd9c2bf1b6ddebcab9dcf389843eb2d39.zip
It may be different for the TA-1012, but according to that earlier post, it does not seem to be the case. Nevertheless, just to be safe, here's the zip for the TA-1012: https://android.googleapis.com/pack.../139c94fd08f52fbd3b852ab4ef5c6515fffb784e.zip (I don't have a TA-1012 so I wasn't able to test this particular zip.)
So basically, to make sure there's no problems, make sure in the Developer's options on the phone that OEM unlocking is enabled, then put your SD card into the phone. Plug the phone into your computer. Copy the update zip that you need somewhere onto the SD card. Disconnect the USB cable. Shut down the phone. Then, while holding down the Volume Up button, reconnect the USB cable. You should see a sad android with "No command" displayed. Now release the Volume Up button. Then hold down the power button and then JUST PRESS once on the Volume Up button. You should be at a recovery menu. Using the volume keys, scroll down to the 'Apply update on SD card' option and select it. Select the zip that you copied over to the SD card earlier and then let it install for a while. It will probably pop up with a 'timestamp too old' error, but just ignore this. The update will install anyway. Then once it's done, do a factory reset on the phone and then shut down. MAKE SURE THERE'S NO SIM CARD IN THE PHONE.
Now that's out of the way, boot the phone up again and just click through the first-time setup screens but DO NOT ENABLE WI-FI or any kind of internet connection. We don't want the phone to update itself back to Android 9. Now plug the phone in again. Copy the bootloaderunlocker apk from Nokia's website onto the phone. Install it. Put in the email address you want the unlock key emailed to. Then voila! You'll get the verification code. Put it into the form on Nokia's website and you'll be emailed an unlock.key file. From there, the site will tell you how to proceed.
A HUGE thanks to: THMSP and frankoid
They did all the work. <3
Click to expand...
Click to collapse
after this my phone struck on nokia logo, please help,,,,
i'm training to recovery mode \ download mode but not working both
gvreddy said:
after this my phone struck on nokia logo, please help,,,,
i'm training to recovery mode \ download mode but not working both
Click to expand...
Click to collapse
Factory reset by wiping cache and data via recovery. Start over and try again.

2.0.4DJB TCL 10 Pro Firmware Update

This is an untouched copy of the recent update for our devices. It has no file extension from TCL, but I'll leave info on how to download the firmware originally below, with it mirrored to Android File Host. Can just open this file like a Zip file
Original Link from TCL grabbed with LogCat
Code:
https://g2slave-ap-north-01.tclcom.com/64c9b63f5a85fdd27b552eec614f884add8fdb67/54/586054
Mirror Link: https://www.androidfilehost.com/?w=files&flid=322525
I have tried patching the Boot.img.p with Magisk, but it doesn't recognize the file format. Renamed it to just boot.img, still won't patch
KaptinBoxxi said:
This is an untouched copy of the recent update for our devices. It has no file extension from TCL, but I'll leave info on how to download the firmware originally below, with it mirrored to Android File Host. Can just open this file like a Zip file
Original Link from TCL grabbed with LogCat
Code:
https://g2slave-ap-north-01.tclcom.com/64c9b63f5a85fdd27b552eec614f884add8fdb67/54/586054
Mirror Link: https://www.androidfilehost.com/?w=files&flid=322525
I have tried patching the Boot.img.p with Magisk, but it doesn't recognize the file format. Renamed it to just boot.img, still won't patch
Click to expand...
Click to collapse
Completely new to this phone. Nice grab! I was able to use your download and 7z zip to extract boot.img from boot.img.p.
I tried to put this file into magisk but no luck.
Have you been able to unlock the bootloader yet?
I tried the fastboot OEM unlock and fastboot flashing unlock when in bootloader mode but it doesn't work.
With someone else's help I was able to locate where the boot.img is located on the phone but unable to extract it.
/dev/block/bootdevice/by-name/boot
Backup boot.img via terminal one-line command
I am trying to make an image backup of boot. The script must work on any android. I think on any Android the boot location is /dev/block/platform/???/by-name/boot My command line find /dev/block/
android.stackexchange.com
Screenshots attached.
JayTM said:
Completely new to this phone. Nice grab! I was able to use your download and 7z zip to extract boot.img from boot.img.p.
I tried to put this file into magisk but no luck.
Have you been able to unlock the bootloader yet?
I tried the fastboot OEM unlock and fastboot flashing unlock when in bootloader mode but it doesn't work.
With someone else's help I was able to locate where the boot.img is located on the phone but unable to extract it.
/dev/block/bootdevice/by-name/boot
Backup boot.img via terminal one-line command
I am trying to make an image backup of boot. The script must work on any android. I think on any Android the boot location is /dev/block/platform/???/by-name/boot My command line find /dev/block/
android.stackexchange.com
Screenshots attached.
Click to expand...
Click to collapse
I did the same thing you probably did to attempt to patch it with Magisk, no luck. I haven't had the time to try further recently. Enabling OEM Unlock and attempting to unlock the bootloader just leads to needing an unlock code, much like bootloader unlocking a Moto device.
I contacted TCL support a long time back when I first got the phone and they were 100% not willing to help with any USA based TCL 10 Pro unlocking. The customer service worker literally said they weren't allowed to help with US based devices. There's no downloads anywhere for the firmware either, which I think goes against Google's agreement to android on a device, but I'm not 100% sure on that.
KaptinBoxxi said:
I did the same thing you probably did to attempt to patch it with Magisk, no luck. I haven't had the time to try further recently. Enabling OEM Unlock and attempting to unlock the bootloader just leads to needing an unlock code, much like bootloader unlocking a Moto device.
I contacted TCL support a long time back when I first got the phone and they were 100% not willing to help with any USA based TCL 10 Pro unlocking. The customer service worker literally said they weren't allowed to help with US based devices. There's no downloads anywhere for the firmware either, which I think goes against Google's agreement to android on a device, but I'm not 100% sure on that.
Click to expand...
Click to collapse
Android 11 for the TCL 10L has been being pushed in italy. This a large file about 2 to 3 GB. I really hope when we see it on our phones you are able to pull the link from logcat as well. This should be the entire rom. All we have now is OTA patch files. I've tried so many things. I have all drivers fully working even the Qualcomm 9008 Diagnostic driver. I can put the phone into EDL mode.
To put phone into EDL mode you need usb debugging enabled and type in secret code into the dialer *#*#3424#*#* which enables the diagnostic port via toast notification. Then turn phone off, hold both volume up and volume down and plug phone into PC. You will be prompted with the Download mode screen. Hold volume up to enter EDL.
There are ways to backup in EDL mode, I'm just not well versed in commands.
JayTM said:
Android 11 for the TCL 10L has been being pushed in italy. This a large file about 2 to 3 GB. I really hope when we see it on our phones you are able to pull the link from logcat as well. This should be the entire rom. All we have now is OTA patch files. I've tried so many things. I have all drivers fully working even the Qualcomm 9008 Diagnostic driver. I can put the phone into EDL mode.
To put phone into EDL mode you need usb debugging enabled and type in secret code into the dialer *#*#3424#*#* which enables the diagnostic port via toast notification. Then turn phone off, hold both volume up and volume down and plug phone into PC. You will be prompted with the Download mode screen. Hold volume up to enter EDL.
There are ways to backup in EDL mode, I'm just not well versed in commands.
Click to expand...
Click to collapse
I'm wondering if I can pull some social engineering off, maybe be like "Hey my phone reset itself, can't boot it, but I read online something for a samsung phone called Odin and Fastboot and such? Some how you can install the system that way?" See what they say/link me to
KaptinBoxxi said:
I'm wondering if I can pull some social engineering off, maybe be like "Hey my phone reset itself, can't boot it, but I read online something for a samsung phone called Odin and Fastboot and such? Some how you can install the system that way?" See what they say/link me to
Click to expand...
Click to collapse
Good luck to you.
I contacted TCL support myself with no luck. They immediately put my case in pending close status.
Is there a way this ZTE tool can be modified to work for our device?
Axon 7 EDL Tool - Flash / Backup / Restore / Unlock in the EDL mode
Axon 7 EDL Tool BAT-program for Flash / Backup / Restore / Unlock the phone in EDL mode Qualcomm HS-USB QDLoader 9008 (COM ...) !!! Whatever you do, you do at your own risk !!!" !!! If you are not sure of yourself do not use this program ...
forum.xda-developers.com
All partitions are detected in EDL mode.
JayTM said:
Is there a way this ZTE tool can be modified to work for our device?
Axon 7 EDL Tool - Flash / Backup / Restore / Unlock in the EDL mode
Axon 7 EDL Tool BAT-program for Flash / Backup / Restore / Unlock the phone in EDL mode Qualcomm HS-USB QDLoader 9008 (COM ...) !!! Whatever you do, you do at your own risk !!!" !!! If you are not sure of yourself do not use this program ...
forum.xda-developers.com
All partitions are detected in EDL mode.
Click to expand...
Click to collapse
I'll check it out. If its possible to view the code in a tool like dnSpy or extract files from the exe with 7zip, its possible to use with our device, i'm sure as long as the commands are similar
Well you're in luck as it is just a .bat file program simple notepad++ will do.
I will be following this thread with intrest, root could be the deciding factor in me purchasing this device.
Tech101yt said:
I will be following this thread with intrest, root could be the deciding factor in me purchasing this device.
Click to expand...
Click to collapse
Have had the phone for less than 6 months and I'm already having LCD issues. When the display is off, just sitting on a table or something, it'll flash white randomly like its getting an electric signal at random. Its nothing I did. I've never hard dropped the thing. Everywhere I go pretty much is carpeted except work. If manufacturer warranty doesn't cover me, I'll stop recommending the phone to people
I actually switched to an Essential Phone recently. Way better experience, way cheaper too. I have around a dozen of them anyway and have been selling em on swappa (dunno if I'm allowed to say that here, but oh well) lol
@KaptinBoxxi Sounds like you have Ambient Display on for notifications.
mschoolbus said:
@KaptinBoxxi Sounds like you have Ambient Display on for notifications.
Click to expand...
Click to collapse
Nah its turned off. It flashes like a broken LCD would look. All snowy and stuff like an old TV. Its not notifications, just a bad LCD
that sucks... could try reseating the screen's ribbon cable :-/
can anybody share the full update rom about android 11?
top170 said:
can anybody share the full update rom about android 11?
Click to expand...
Click to collapse
I don't believe anyone has Logcatted the update process yet to get the firmware, but on the subject of this post, I do have some updates
I was digging through my Logcat from january and realized I missed something massive. I have yet to figure out the URL structure, but I have all the info for it.
So when you go to the following link, it gives a bunch of errors of missing info
https://g2master-sa-east.tclclouds.com/notify_new.php
For the firmware here on this post at least, each value from my device is
Code:
id = 0156260
curef = T799B-2ALCUS11
vk = 741ace917e3527af81412ca93b0fcce2de04a264
salt = 1611977254070885419
fv = 4DJ1LM10
tv = 4DJBLMB0
op = 1000
status = 999
mode = 2
cltp = 10
type = firmware
formatted from logcat
reportContent= {"id":"0156260","salt":"1611977254070885419","curef":"T799B-2ALCUS11","fv":"4DJ1LM10","tv":"4DJBLMB0","mode":"2","cltp":"10","type":"Firmware","op":"1000","status":"999","vk":"741ace917e3527af81412ca93b0fcce2de04a264"}
no matter what, I get the errors on the web page

Huawei P30 (ELE-L29 11.0.0.159 C431) TEST POINT AND DOWNGRADE PROBLEM

Hi, I want to unlock bootloader of my phome and root it via Magisk method. But recently I've discovered that there is no way to unlock bootloader when you upgraded to EMUI 11. Dc-Phoenix + HCU doesn't support after EMUI 10 software testpoint. So the only way is try to Hardware testpoint method. I disassembled the phone and reach the motherboard and testpoint pin without damaged it. I short the testpoint pin with metal ground, plugged the USB and managed to enable the testpoint mode (the screen was black.) But then I saw my computer cannot detect my phone in testpoint mode, there is no "Huawei USB COM 1.0" or "USB Ser". I find drivers for Huawei USB COM 1.0 but still no change at all. I check the "Device Manager -> Install Legacy Driver -> Install From Disc" but there is no Huawei Incorporated drivers. I think my PC's problem that cannot detect my device in testpoint mode is the drivers. Here is what I did step by step;
1- Battery fulled and power off, phones back cover removed carefully and reached the mothet board. Testpoint pin founded.
2- Huawei USB COM 1.0 drivers installed to PC (driver file from PotatoNV GitHub page.)
3- USB-A side plugged to PC and USB-C side is waiting
4- A conductive metal tool (mine is pointed tweezer) grabbed and shorted to pin to metal ground and I keep them so.
5- While keeping the testpoint shorted, I plugged the USB-C side to phone and waited couple of second.
Then when I look at the PC, there is no change. No device detected. First, I was think that I couldn't manage the testpoint shorting but when I plugged the Phone to PC without shorting, the Huawei boot screen appears. When I short the testpoint and plugged it, the screen is black which means the device is in test point mode. But then, PC is not detecting my phone. So my guess is that the problem is the drivers.
I find out I could use the HiSuite Proxy app to downgrade from EMUI 11 to EMUI 10 so I can use the DC-Phoenix + HCU, but I tried this method before disassembling the phone. It didn't work that time. 2 days ago, I tried again this method to downgrade and use the software testpoint and I successfully downgraded it. The problem was HiSuite 10.0.0.550 cannot flash EMUI 11 but HiSuite 10.1.... can flash EMUI 11. I was in 11.0.0.159 firmware version and downgraded to 10.1.0.150 firmware version.
After that day, I decided to start to unlock method by DC-Phoenix and HCU but before buying timed licence I want to be sure that everything is okey. First, I plugged to phone to PC and that is the end of the way. There is no way to connecting PC after downgrade. I searched it from XDA and find out that after some security patchs or firmware versions if you try to downgrade, your USB activities are locked. And when you reach to latest version (version before I downgrade from), USB problem is solved. This is about the Huawei's new security patch, I guess. Many of Huawei P40 user is complaining about same problem. They are telling that in P40 after 11.0.0.180 update, if they try to downgrade, there USB functions are limited (no fast charge, no OTG or USB driver, no PC connecting). So, if you're using your Huawei phone and you are in EMUI 11 and after some update you will be get this problem too. There is no way to unlock bootloader or root on EMUI 11. There is no way to downgrade. But I searched and find out that you can flash any stock rom by SigmaKey. It is very expensive but you can flash stock rom to downgrade. You need just dload files (that 3 zips) and unzip the update.app and ptable.app files. Do that for 3 zip packages. And you can flash roms without any problem.
What I tried and discovered is dload method won't work this USB problem. Everyone knows that you can't downgrade from EMUI 11 by dload method. I downgrade with HiSuite Proxy to EMUI 10.1.0.150 and after downgrade I tried to dload method to upgrade firmware to 10.1.0.161. Dload is failed in %94 and I restarted device. The version is upgraded to 10.1.0.161 and all user data formatted but USB problem is not solved. When I upgraded to latest firmware, the problem is solved. But I want to downgrade without any problem and root this phone.
My biggest advice to anyone who have the Huawei phone, DO NOT UPGRADE YOUR PHONE WITHOUT SEARCHING THE NEW VERSION. IT IS LIKE HUAWEI FORCING EVERYONE TO UPGRADING THERE PHONE OR CANNOT DOWNGRADE TO ANY FRIMWARE.
Does anyone has same problem with me? What is the solution for this? I removed the back of the phone for nothing? I have to unlock the bootloader and root this device. I would really appreciated if you can help me.
Experiencing the same problem, but i can get even in Tespoint mode. The Computer just wont list my phone and i can do absolutley nothing. Now the phone is a piece of Garbage?
Xynactra said:
Experiencing the same problem, but i can get even in Tespoint mode. The Computer just wont list my phone and i can do absolutley nothing. Now the phone is a piece of Garbage?
Click to expand...
Click to collapse
There is a way by SigmaKey Tools. But it's really expensive. In SigmaKey, there is a process that allowing you to flash the stock rom files (update.app and ptable.app). That means you can downgrade the firmware version without any problem or USB port lock. If you try to enable hardware test point and disassemble the phone, you can't connect the phone to PC in EMUI 11. So if you downgrade without USB port lock, you can enable the test point to. So there is only way to unlock bootloader and root Huawei phone is SigmaKey Tool. But too expensive for only one using.
I had the same problem. Phone was not detected in EDL mode. What i actually did to solve it is to pres left side of the board (so it makes contact with pins under it). holding it pressed i connected test point and usb c. and it all worked well
MrMutlu said:
There is a way by SigmaKey Tools. But it's really expensive. In SigmaKey, there is a process that allowing you to flash the stock rom files (update.app and ptable.app). That means you can downgrade the firmware version without any problem or USB port lock. If you try to enable hardware test point and disassemble the phone, you can't connect the phone to PC in EMUI 11. So if you downgrade without USB port lock, you can enable the test point to. So there is only way to unlock bootloader and root Huawei phone is SigmaKey Tool. But too expensive for only one using.
Click to expand...
Click to collapse
I have sigma box but it's all the same after downgrade usb function is locked.
Hi. Excuse me for writing in this section but i don't know who to talk to. I have Huawei Y6 2018 (ATU L21) and tried to flash via TWRP many custom ROMs witn no success. Everytime i get error 9 in TWRP. All Y6 roms in the net are like this one from the link below.
Huawei Honor 7A 2018 ATU-L21 hw eu HLRCF Atomu-L21 8.0.0.155(C432CUSTC432D1) Firmware 8.0.0 r1 EMUI8.0 05015CHD [androidhost.ru].zip - AndroidHost.RU
Download file - Huawei Honor 7A 2018 ATU-L21 hw eu HLRCF Atomu-L21 8.0.0.155(C432CUSTC432D1) Firmware 8.0.0 r1 EMUI8.0 05015CHD [androidhost.ru].zip
androidhost.ru
I also tried to open the zip file. There are two folders in it - "ReleaseDoc" and "Software". The software folder contains "dload" folder and in it "ATU-L21_hw_eu" folder with "update_sd_ATU-L21_hw_eu.zip" Also tried to flash this zip but again with no success and the same error. Where am i wrong. How to flash this ROM or maybe i have to install another version of TWRP. Mine is 3.3.1. Thanks in advance.
Pisonja said:
I had the same problem. Phone was not detected in EDL mode. What i actually did to solve it is to pres left side of the board (so it makes contact with pins under it). holding it pressed i connected test point and usb c. and it all worked well
Click to expand...
Click to collapse
Hi. I have the same problem. ele-l29 device open to go to edl with test points but it doesn't work.
It remains on a black screen but the PC does not show it on the devices. You say you pressed the left side ... but what?
novembre.973 said:
Hi. I have the same problem. ele-l29 device open to go to edl with test points but it doesn't work.
It remains on a black screen but the PC does not show it on the devices. You say you pressed the left side ... but what?
Click to expand...
Click to collapse
MrMutlu said:
Hi, I want to unlock bootloader of my phome and root it via Magisk method. But recently I've discovered that there is no way to unlock bootloader when you upgraded to EMUI 11. Dc-Phoenix + HCU doesn't support after EMUI 10 software testpoint. So the only way is try to Hardware testpoint method. I disassembled the phone and reach the motherboard and testpoint pin without damaged it. I short the testpoint pin with metal ground, plugged the USB and managed to enable the testpoint mode (the screen was black.) But then I saw my computer cannot detect my phone in testpoint mode, there is no "Huawei USB COM 1.0" or "USB Ser". I find drivers for Huawei USB COM 1.0 but still no change at all. I check the "Device Manager -> Install Legacy Driver -> Install From Disc" but there is no Huawei Incorporated drivers. I think my PC's problem that cannot detect my device in testpoint mode is the drivers. Here is what I did step by step;
1- Battery fulled and power off, phones back cover removed carefully and reached the mothet board. Testpoint pin founded.
2- Huawei USB COM 1.0 drivers installed to PC (driver file from PotatoNV GitHub page.)
3- USB-A side plugged to PC and USB-C side is waiting
4- A conductive metal tool (mine is pointed tweezer) grabbed and shorted to pin to metal ground and I keep them so.
5- While keeping the testpoint shorted, I plugged the USB-C side to phone and waited couple of second.
Then when I look at the PC, there is no change. No device detected. First, I was think that I couldn't manage the testpoint shorting but when I plugged the Phone to PC without shorting, the Huawei boot screen appears. When I short the testpoint and plugged it, the screen is black which means the device is in test point mode. But then, PC is not detecting my phone. So my guess is that the problem is the drivers.
I find out I could use the HiSuite Proxy app to downgrade from EMUI 11 to EMUI 10 so I can use the DC-Phoenix + HCU, but I tried this method before disassembling the phone. It didn't work that time. 2 days ago, I tried again this method to downgrade and use the software testpoint and I successfully downgraded it. The problem was HiSuite 10.0.0.550 cannot flash EMUI 11 but HiSuite 10.1.... can flash EMUI 11. I was in 11.0.0.159 firmware version and downgraded to 10.1.0.150 firmware version.
After that day, I decided to start to unlock method by DC-Phoenix and HCU but before buying timed licence I want to be sure that everything is okey. First, I plugged to phone to PC and that is the end of the way. There is no way to connecting PC after downgrade. I searched it from XDA and find out that after some security patchs or firmware versions if you try to downgrade, your USB activities are locked. And when you reach to latest version (version before I downgrade from), USB problem is solved. This is about the Huawei's new security patch, I guess. Many of Huawei P40 user is complaining about same problem. They are telling that in P40 after 11.0.0.180 update, if they try to downgrade, there USB functions are limited (no fast charge, no OTG or USB driver, no PC connecting). So, if you're using your Huawei phone and you are in EMUI 11 and after some update you will be get this problem too. There is no way to unlock bootloader or root on EMUI 11. There is no way to downgrade. But I searched and find out that you can flash any stock rom by SigmaKey. It is very expensive but you can flash stock rom to downgrade. You need just dload files (that 3 zips) and unzip the update.app and ptable.app files. Do that for 3 zip packages. And you can flash roms without any problem.
What I tried and discovered is dload method won't work this USB problem. Everyone knows that you can't downgrade from EMUI 11 by dload method. I downgrade with HiSuite Proxy to EMUI 10.1.0.150 and after downgrade I tried to dload method to upgrade firmware to 10.1.0.161. Dload is failed in %94 and I restarted device. The version is upgraded to 10.1.0.161 and all user data formatted but USB problem is not solved. When I upgraded to latest firmware, the problem is solved. But I want to downgrade without any problem and root this phone.
My biggest advice to anyone who have the Huawei phone, DO NOT UPGRADE YOUR PHONE WITHOUT SEARCHING THE NEW VERSION. IT IS LIKE HUAWEI FORCING EVERYONE TO UPGRADING THERE PHONE OR CANNOT DOWNGRADE TO ANY FRIMWARE.
Does anyone has same problem with me? What is the solution for this? I removed the back of the phone for nothing? I have to unlock the bootloader and root this device. I would really appreciated if you can help me.
Click to expand...
Click to collapse
the problem of edl mode: just build a cable with a 10k resistor and use that to go into edl mode. better if the cable is equipped with a 10k resistor exclusion button because the telephone with the resistor connected can ONLY work in edl. so if any software needs to exit edl mode (eg: switch to fastboot) you can exclude the resistance and make the cable work normally.
MrMutlu said:
Hi, I want to unlock bootloader of my phome and root it via Magisk method. But recently I've discovered that there is no way to unlock bootloader when you upgraded to EMUI 11. Dc-Phoenix + HCU doesn't support after EMUI 10 software testpoint. So the only way is try to Hardware testpoint method. I disassembled the phone and reach the motherboard and testpoint pin without damaged it. I short the testpoint pin with metal ground, plugged the USB and managed to enable the testpoint mode (the screen was black.) But then I saw my computer cannot detect my phone in testpoint mode, there is no "Huawei USB COM 1.0" or "USB Ser". I find drivers for Huawei USB COM 1.0 but still no change at all. I check the "Device Manager -> Install Legacy Driver -> Install From Disc" but there is no Huawei Incorporated drivers. I think my PC's problem that cannot detect my device in testpoint mode is the drivers. Here is what I did step by step;
1- Battery fulled and power off, phones back cover removed carefully and reached the mothet board. Testpoint pin founded.
2- Huawei USB COM 1.0 drivers installed to PC (driver file from PotatoNV GitHub page.)
3- USB-A side plugged to PC and USB-C side is waiting
4- A conductive metal tool (mine is pointed tweezer) grabbed and shorted to pin to metal ground and I keep them so.
5- While keeping the testpoint shorted, I plugged the USB-C side to phone and waited couple of second.
Then when I look at the PC, there is no change. No device detected. First, I was think that I couldn't manage the testpoint shorting but when I plugged the Phone to PC without shorting, the Huawei boot screen appears. When I short the testpoint and plugged it, the screen is black which means the device is in test point mode. But then, PC is not detecting my phone. So my guess is that the problem is the drivers.
I find out I could use the HiSuite Proxy app to downgrade from EMUI 11 to EMUI 10 so I can use the DC-Phoenix + HCU, but I tried this method before disassembling the phone. It didn't work that time. 2 days ago, I tried again this method to downgrade and use the software testpoint and I successfully downgraded it. The problem was HiSuite 10.0.0.550 cannot flash EMUI 11 but HiSuite 10.1.... can flash EMUI 11. I was in 11.0.0.159 firmware version and downgraded to 10.1.0.150 firmware version.
After that day, I decided to start to unlock method by DC-Phoenix and HCU but before buying timed licence I want to be sure that everything is okey. First, I plugged to phone to PC and that is the end of the way. There is no way to connecting PC after downgrade. I searched it from XDA and find out that after some security patchs or firmware versions if you try to downgrade, your USB activities are locked. And when you reach to latest version (version before I downgrade from), USB problem is solved. This is about the Huawei's new security patch, I guess. Many of Huawei P40 user is complaining about same problem. They are telling that in P40 after 11.0.0.180 update, if they try to downgrade, there USB functions are limited (no fast charge, no OTG or USB driver, no PC connecting). So, if you're using your Huawei phone and you are in EMUI 11 and after some update you will be get this problem too. There is no way to unlock bootloader or root on EMUI 11. There is no way to downgrade. But I searched and find out that you can flash any stock rom by SigmaKey. It is very expensive but you can flash stock rom to downgrade. You need just dload files (that 3 zips) and unzip the update.app and ptable.app files. Do that for 3 zip packages. And you can flash roms without any problem.
What I tried and discovered is dload method won't work this USB problem. Everyone knows that you can't downgrade from EMUI 11 by dload method. I downgrade with HiSuite Proxy to EMUI 10.1.0.150 and after downgrade I tried to dload method to upgrade firmware to 10.1.0.161. Dload is failed in %94 and I restarted device. The version is upgraded to 10.1.0.161 and all user data formatted but USB problem is not solved. When I upgraded to latest firmware, the problem is solved. But I want to downgrade without any problem and root this phone.
My biggest advice to anyone who have the Huawei phone, DO NOT UPGRADE YOUR PHONE WITHOUT SEARCHING THE NEW VERSION. IT IS LIKE HUAWEI FORCING EVERYONE TO UPGRADING THERE PHONE OR CANNOT DOWNGRADE TO ANY FRIMWARE.
Does anyone has same problem with me? What is the solution for this? I removed the back of the phone for nothing? I have to unlock the bootloader and root this device. I would really appreciated if you can help me.
Click to expand...
Click to collapse
USB/fast boot/fast charging and test point not working after downgrade.
I recently downgraded my Mate 20 Pro from EMUI 11.0 aware this would arise. I am now on EMUI 9.0 with USB/fast boot and fast charging working. I can't confirm if this fixed test point as I haven't opened my device yet.
Simple solution was to change the USB-C cable used to perform the downgrade to an alternative one. Everything sprung back to life, I have since reverted back to the original USB-C cable and everything works as expected.
You can find more information on the downgrade procedure I posted here
Helpful Information - Downgrading From EMUI 11 · Issue #127 · ProfessorJTJ/HISuite-Proxy
Professor JTJ if you can include this within the guide it may help others. The guide does mention about loss of fast charge, fast boot, USB and test point. And while I was initially affected too, o...
github.com
MrMutlu said:
Hi, I want to unlock bootloader of my phome and root it via Magisk method. But recently I've discovered that there is no way to unlock bootloader when you upgraded to EMUI 11. Dc-Phoenix + HCU doesn't support after EMUI 10 software testpoint. So the only way is try to Hardware testpoint method. I disassembled the phone and reach the motherboard and testpoint pin without damaged it. I short the testpoint pin with metal ground, plugged the USB and managed to enable the testpoint mode (the screen was black.) But then I saw my computer cannot detect my phone in testpoint mode, there is no "Huawei USB COM 1.0" or "USB Ser". I find drivers for Huawei USB COM 1.0 but still no change at all. I check the "Device Manager -> Install Legacy Driver -> Install From Disc" but there is no Huawei Incorporated drivers. I think my PC's problem that cannot detect my device in testpoint mode is the drivers. Here is what I did step by step;
1- Battery fulled and power off, phones back cover removed carefully and reached the mothet board. Testpoint pin founded.
2- Huawei USB COM 1.0 drivers installed to PC (driver file from PotatoNV GitHub page.)
3- USB-A side plugged to PC and USB-C side is waiting
4- A conductive metal tool (mine is pointed tweezer) grabbed and shorted to pin to metal ground and I keep them so.
5- While keeping the testpoint shorted, I plugged the USB-C side to phone and waited couple of second.
Then when I look at the PC, there is no change. No device detected. First, I was think that I couldn't manage the testpoint shorting but when I plugged the Phone to PC without shorting, the Huawei boot screen appears. When I short the testpoint and plugged it, the screen is black which means the device is in test point mode. But then, PC is not detecting my phone. So my guess is that the problem is the drivers.
I find out I could use the HiSuite Proxy app to downgrade from EMUI 11 to EMUI 10 so I can use the DC-Phoenix + HCU, but I tried this method before disassembling the phone. It didn't work that time. 2 days ago, I tried again this method to downgrade and use the software testpoint and I successfully downgraded it. The problem was HiSuite 10.0.0.550 cannot flash EMUI 11 but HiSuite 10.1.... can flash EMUI 11. I was in 11.0.0.159 firmware version and downgraded to 10.1.0.150 firmware version.
After that day, I decided to start to unlock method by DC-Phoenix and HCU but before buying timed licence I want to be sure that everything is okey. First, I plugged to phone to PC and that is the end of the way. There is no way to connecting PC after downgrade. I searched it from XDA and find out that after some security patchs or firmware versions if you try to downgrade, your USB activities are locked. And when you reach to latest version (version before I downgrade from), USB problem is solved. This is about the Huawei's new security patch, I guess. Many of Huawei P40 user is complaining about same problem. They are telling that in P40 after 11.0.0.180 update, if they try to downgrade, there USB functions are limited (no fast charge, no OTG or USB driver, no PC connecting). So, if you're using your Huawei phone and you are in EMUI 11 and after some update you will be get this problem too. There is no way to unlock bootloader or root on EMUI 11. There is no way to downgrade. But I searched and find out that you can flash any stock rom by SigmaKey. It is very expensive but you can flash stock rom to downgrade. You need just dload files (that 3 zips) and unzip the update.app and ptable.app files. Do that for 3 zip packages. And you can flash roms without any problem.
What I tried and discovered is dload method won't work this USB problem. Everyone knows that you can't downgrade from EMUI 11 by dload method. I downgrade with HiSuite Proxy to EMUI 10.1.0.150 and after downgrade I tried to dload method to upgrade firmware to 10.1.0.161. Dload is failed in %94 and I restarted device. The version is upgraded to 10.1.0.161 and all user data formatted but USB problem is not solved. When I upgraded to latest firmware, the problem is solved. But I want to downgrade without any problem and root this phone.
My biggest advice to anyone who have the Huawei phone, DO NOT UPGRADE YOUR PHONE WITHOUT SEARCHING THE NEW VERSION. IT IS LIKE HUAWEI FORCING EVERYONE TO UPGRADING THERE PHONE OR CANNOT DOWNGRADE TO ANY FRIMWARE.
Does anyone has same problem with me? What is the solution for this? I removed the back of the phone for nothing? I have to unlock the bootloader and root this device. I would really appreciated if you can help me.
Click to expand...
Click to collapse
Hi, just a stupid question. How to exit from hard test point mode? I wanna try it to unlock bootloader on other device, but I'm not sure if after that I can exit from this particular mode. Thank you
MrMutlu said:
Hi, I want to unlock bootloader of my phome and root it via Magisk method. But recently I've discovered that there is no way to unlock bootloader when you upgraded to EMUI 11. Dc-Phoenix + HCU doesn't support after EMUI 10 software testpoint. So the only way is try to Hardware testpoint method. I disassembled the phone and reach the motherboard and testpoint pin without damaged it. I short the testpoint pin with metal ground, plugged the USB and managed to enable the testpoint mode (the screen was black.) But then I saw my computer cannot detect my phone in testpoint mode, there is no "Huawei USB COM 1.0" or "USB Ser". I find drivers for Huawei USB COM 1.0 but still no change at all. I check the "Device Manager -> Install Legacy Driver -> Install From Disc" but there is no Huawei Incorporated drivers. I think my PC's problem that cannot detect my device in testpoint mode is the drivers. Here is what I did step by step;
1- Battery fulled and power off, phones back cover removed carefully and reached the mothet board. Testpoint pin founded.
2- Huawei USB COM 1.0 drivers installed to PC (driver file from PotatoNV GitHub page.)
3- USB-A side plugged to PC and USB-C side is waiting
4- A conductive metal tool (mine is pointed tweezer) grabbed and shorted to pin to metal ground and I keep them so.
5- While keeping the testpoint shorted, I plugged the USB-C side to phone and waited couple of second.
Then when I look at the PC, there is no change. No device detected. First, I was think that I couldn't manage the testpoint shorting but when I plugged the Phone to PC without shorting, the Huawei boot screen appears. When I short the testpoint and plugged it, the screen is black which means the device is in test point mode. But then, PC is not detecting my phone. So my guess is that the problem is the drivers.
I find out I could use the HiSuite Proxy app to downgrade from EMUI 11 to EMUI 10 so I can use the DC-Phoenix + HCU, but I tried this method before disassembling the phone. It didn't work that time. 2 days ago, I tried again this method to downgrade and use the software testpoint and I successfully downgraded it. The problem was HiSuite 10.0.0.550 cannot flash EMUI 11 but HiSuite 10.1.... can flash EMUI 11. I was in 11.0.0.159 firmware version and downgraded to 10.1.0.150 firmware version.
After that day, I decided to start to unlock method by DC-Phoenix and HCU but before buying timed licence I want to be sure that everything is okey. First, I plugged to phone to PC and that is the end of the way. There is no way to connecting PC after downgrade. I searched it from XDA and find out that after some security patchs or firmware versions if you try to downgrade, your USB activities are locked. And when you reach to latest version (version before I downgrade from), USB problem is solved. This is about the Huawei's new security patch, I guess. Many of Huawei P40 user is complaining about same problem. They are telling that in P40 after 11.0.0.180 update, if they try to downgrade, there USB functions are limited (no fast charge, no OTG or USB driver, no PC connecting). So, if you're using your Huawei phone and you are in EMUI 11 and after some update you will be get this problem too. There is no way to unlock bootloader or root on EMUI 11. There is no way to downgrade. But I searched and find out that you can flash any stock rom by SigmaKey. It is very expensive but you can flash stock rom to downgrade. You need just dload files (that 3 zips) and unzip the update.app and ptable.app files. Do that for 3 zip packages. And you can flash roms without any problem.
What I tried and discovered is dload method won't work this USB problem. Everyone knows that you can't downgrade from EMUI 11 by dload method. I downgrade with HiSuite Proxy to EMUI 10.1.0.150 and after downgrade I tried to dload method to upgrade firmware to 10.1.0.161. Dload is failed in %94 and I restarted device. The version is upgraded to 10.1.0.161 and all user data formatted but USB problem is not solved. When I upgraded to latest firmware, the problem is solved. But I want to downgrade without any problem and root this phone.
My biggest advice to anyone who have the Huawei phone, DO NOT UPGRADE YOUR PHONE WITHOUT SEARCHING THE NEW VERSION. IT IS LIKE HUAWEI FORCING EVERYONE TO UPGRADING THERE PHONE OR CANNOT DOWNGRADE TO ANY FRIMWARE.
Does anyone has same problem with me? What is the solution for this? I removed the back of the phone for nothing? I have to unlock the bootloader and root this device. I would really appreciated if you can help me.
Click to expand...
Click to collapse
A successful downgrade per the above is required in conjunction with a
Huawei (HarmonyOS) testpoint cable (Huawei USB COM 1.0)​Otherwise, whilst enabled Test Point mode will not work.
EnryP said:
Hi, just a stupid question. How to exit from hard test point mode? I wanna try it to unlock bootloader on other device, but I'm not sure if after that I can exit from this particular mode. Thank you.
Click to expand...
Click to collapse
If you used Test Point, the phone will be in Factory Mode only temporarily. If you do a hard reset for example, it will automatically exit the Factory Mode.
Loggsie said:
If you used Test Point, the phone will be in Factory Mode only temporarily. If you do a hard reset for example, it will automatically exit the Factory Mode.
Click to expand...
Click to collapse
Thank you for replying me.
So, for exit test mode I have to do an action such as a factory reset with softwares like DC Unlocker, SigmaKey etc.. but,for example, I can't just turn off the phone to leave it or use any button combination. Am I RIght?
EnryP said:
Thank you for replying me.
So, for exit test mode I have to do an action such as a factory reset with softwares like DC Unlocker, SigmaKey etc.. but,for example, I can't just turn off the phone to leave it or use any button combination. Am I RIght?
Click to expand...
Click to collapse
A hard reset is a simple rebooting of your phone using the hardware buttons i.e. holding power and volume down simultaneously (varies per device). A factory reset isn't needed, this is when you erase data.
Loggsie said:
A hard reset is a simple rebooting of your phone using the hardware buttons i.e. holding power and volume down simultaneously (varies per device). A factory reset isn't needed, this is when you erase data.
Click to expand...
Click to collapse
Okay, but let's suppose that I enter hardware test point mode but then I don't do (or I can't do) any action with the softwares mentioned before (let's suppose because PC doesn't recognize the phone) Is there a way to quit this mode? For example, what happen if the phone get turned off? Thank you again.
Edit: My bad, I confused hard reset with factory reset. Therefore to exit test point mode I can perform an hard reset (reboot the phone wth buttons combination)
EnryP said:
Okay, but let's suppose that I enter hardware test point mode but then I don't do (or I can't do) any action with the softwares mentioned before (let's suppose because PC doesn't recognize the phone) Is there a way to quit this mode? For example, what happen if the phone get turned off? Thank you again.
Edit: My bad, I confused hard reset with factory reset. Therefore to exit test point mode I can perform an hard reset (reboot the phone wth buttons combination)
Click to expand...
Click to collapse
Yes exactly this 'Therefore to exit test point mode I can perform an hard reset (reboot the phone wth buttons combination)'.
EnryP said:
Okay, but let's suppose that I enter hardware test point mode but then I don't do (or I can't do) any action with the softwares mentioned before (let's suppose because PC doesn't recognize the phone) Is there a way to quit this mode? For example, what happen if the phone get turned off? Thank you again.
Edit: My bad, I confused hard reset with factory reset. Therefore to exit test point mode I can perform an hard reset (reboot the phone wth buttons combination)
Click to expand...
Click to collapse
You can just disconnect the battery, unplug cable and connect battery back
It can be solve by modified cable by using 10k resistor between on red and green wire
USB will works on downgraded devices (TEST PONT, Fastboot, MTP, etc.)
{
"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"
}

Categories

Resources