Xiaomi device bricked after reboot - General Questions and Answers

My Xiaomi Redmi Note 8 Pro isn't booting anymore.
I'm stuck in the fastboot screen, I don't even reach the redmi logo in the boot, I need to recover the data on the phone but I have no idea about how to do that.
Any suggestions?
(Already tried going to recovery with power down + volume up, isn't working)

I'm stuck in the fastboot screen
Click to expand...
Click to collapse
I'm assuming you have Fastboot.
Was USB Debugging ON before the device got bricked? If yes then:
> Download TWRP Recovery for Redmi Note 8 Pro from twrp website. Rename the file to: twrp.img
> Download latest Xiaomi USB Drivers for PC from Internet.
> Download 15-Seconds-ADB-Installer for PC from Internet.
> After Installation is over, Restart PC > Windows Explorer > This PC/ My Computer > ADB Folder > Press SHIFT+Right Click Mouse+Open Powershell Window Here > New window opens
> Transfer the twrp.img file to ADB folder.
> Now you can try connecting the XRN8Pro to the PC (while the Fastboot screen is on)
> On the Powershell window you can type one by one:
1) fastboot devices
2) fastboot boot twrp.img
> Your XRN8Pro phone should boot to TWRP Custom Recovery.
> On PC open another Windows Explorer tab and check if your phones Internal Storage is displayed. If yes you can try to copy your phone data to PC.
> After that in TWRP recovery Press Reboot to Bootloader option, It will show Fastboot screen.
> Download XRN8Pro Stock Firmware/Fastboot ROM from Internet to Desktop only.
> Download Mi Flash Tool for XRN8Pro. Double Click on XiaoMiFlash.exe file.
> Connect XRN8Pro to PC (while fastboot screen is on)
> Then on MiFlash window click on folder to link to firmware file on desktop & click on refresh button, then click on Flash. It takes about 17 minutes (for RN8 devices) to flash MIUI ROM.

OldNoobOne said:
I'm assuming you have Fastboot.
Was USB Debugging ON before the device got bricked? If yes then:
> Download TWRP Recovery for Redmi Note 8 Pro from twrp website. Rename the file to: twrp.img
> Download latest Xiaomi USB Drivers for PC from Internet.
> Download 15-Seconds-ADB-Installer for PC from Internet.
> After Installation is over, Restart PC > Windows Explorer > This PC/ My Computer > ADB Folder > Press SHIFT+Right Click Mouse+Open Powershell Window Here > New window opens
> Transfer the twrp.img file to ADB folder.
> Now you can try connecting the XRN8Pro to the PC (while the Fastboot screen is on)
> On the Powershell window you can type one by one:
1) fastboot devices
2) fastboot boot twrp.img
> Your XRN8Pro phone should boot to TWRP Custom Recovery.
> On PC open another Windows Explorer tab and check if your phones Internal Storage is displayed. If yes you can try to copy your phone data to PC.
> After that in TWRP recovery Press Reboot to Bootloader option, It will show Fastboot screen.
> Download XRN8Pro Stock Firmware/Fastboot ROM from Internet to Desktop only.
> Download Mi Flash Tool for XRN8Pro. Double Click on XiaoMiFlash.exe file.
> Connect XRN8Pro to PC (while fastboot screen is on)
> Then on MiFlash window click on folder to link to firmware file on desktop & click on refresh button, then click on Flash. It takes about 17 minutes (for RN8 devices) to flash MIUI ROM.
Click to expand...
Click to collapse
Thanks for the reply, this game me some hope, but I don't think USB Debugging was enabled.
I've never rooted or changed rom, I just rebooted the phone and apparently I triggered the rm -rf / command.

BrickedXiaomi said:
Thanks for the reply, this game me some hope, but I don't think USB Debugging was enabled.
I've never rooted or changed rom, I just rebooted the phone and apparently I triggered the rm -rf / command.
Click to expand...
Click to collapse
No problem, even then TWRP should allow MTP file transfer to PC, so follow all the steps and tell me what happens ok

OldNoobOne said:
No problem, even then TWRP should allow MTP file transfer to PC, so follow all the steps and tell me what happens ok
Click to expand...
Click to collapse
I'll try tomorrow, thanks for all the precious details btw!

Just a question, shouldn't I unlock the phone with mi unlocker before that?

BrickedXiaomi said:
Just a question, shouldn't I unlock the phone with mi unlocker before that?
Click to expand...
Click to collapse
You hadn't already? OMG! Sorry. Yup probably would need bootloader unlocking but you can try to lookup steps for Fastboot commands to unlock bootloader on the internet. But it shouldn't trigger a wipe of any sort or you might lose the data inside. Also, no harm in trying to load TWRP using Fastboot i think, just in case TWRP loads.

OldNoobOne said:
You hadn't already? OMG! Sorry. Yup probably would need bootloader unlocking but you can try to lookup steps for Fastboot commands to unlock bootloader on the internet. But it shouldn't trigger a wipe of any sort or you might lose the data inside. Also, no harm in trying to load TWRP using Fastboot i think, just in case TWRP loads.
Click to expand...
Click to collapse
As said, I never modified this phone, is basically as if it was brand new, OS side.

Maybe I can use https://forum.xda-developers.com/t/unlock-bootloader-without-losing-data.3864667/ to unlock the bootloader without loosing data?

BrickedXiaomi said:
Maybe I can use https://forum.xda-developers.com/t/unlock-bootloader-without-losing-data.3864667/ to unlock the bootloader without loosing data?
Click to expand...
Click to collapse
Wow thats great link, I hope it works so you don't lose data.
The link is fresh so you can also ask there. All the Best

Update: I've tried to contact Xiaomi about the issue.
They said they should be able to help me out with this stuff, and that I shouldn't flash my phone because it's really easy to brick.
I understand that it's the usual support recommendation, but it is possible that they know how to fix this issue?
What should I do, go for their way or go for myself?

BrickedXiaomi said:
Update: I've tried to contact Xiaomi about the issue.
They said they should be able to help me out with this stuff, and that I shouldn't flash my phone because it's really easy to brick.
I understand that it's the usual support recommendation, but it is possible that they know how to fix this issue?
What should I do, go for their way or go for myself?
Click to expand...
Click to collapse
Is your phone In-Warranty? If yes or no i would suggest go your own way, once purchased an used any device, don't connect with OEM servers ever again for any OTA update coz lots of recent cases about OEM(Original Equipment Manufatureres) killing devices with OTA updates and after that the phone doesnt boot, no recovery no fastboot too, so careful with contacting/updating through OEMs if out -of-warranty specially. Once out-of-warranty always use ROM channels to upgrade to new handroid versions instead of direct OTA upgrade/update, that way you may still be able to roll back the OS to previous version in case you don't like the new handroid version, lots of people don't like handroid 12 but they cant roll back to handroid 11 .

> recent cases about OEM(Original Equipment Manufatureres) killing devices with OTA updates
This is considered highly illegal in Europe, I could sue Xiaomi for that, in case, and would be an easy win.
Btw, I'm the one who bought this phone first, it's just out of warranty since I've bought it in nov-19.
After this data recovery I'll be out of the Android world forever, I just care about my data, currently.

BrickedXiaomi said:
> recent cases about OEM(Original Equipment Manufatureres) killing devices with OTA updates
This is considered highly illegal in Europe, I could sue Xiaomi for that, in case, and would be an easy win.
Btw, I'm the one who bought this phone first, it's just out of warranty since I've bought it in nov-19.
After this data recovery I'll be out of the Android world forever, I just care about my data, currently.
Click to expand...
Click to collapse
Yes they might not try doing that with uropean customers but they might try in other countries where there no proper legal system for things like these, also they wont do it with everyone in a particular country to avoid suspicion, theyre smart enough to know what theyre doing, but unofficially speaking many retailers have told me about such a thing (OTA Kill Device) happening in Weaker-Law-N-Order countries, so just saying precaution is always good.

BTW i've put my Retmi Noat 10 up for sale, its still in warranty & I havent used it in the last 10 months, no sim card, unused totally, just once I loaded Gcam to check how the camera is, shamshung is always better than chyneez phones mainly coz better build and component-life, chyneez devices only look shiny from outside but it doesnt last beyond 3-5 yrs, not built to last, just use-n-throw devices u knw. Such devices are only made for mass-surveillance in mind not with customers-focus. This A/B partition thing and super partition thing is adding more bad than good.

I don't think that trick will work. even if it would be possible to cheat that easy, encryption key is bonded* to bootloader lock state. so if you somehow magically managed to unlock bootloader without triggering factory reset, your data could no longer decrypted from android OS and is therefore lost.
Xiaomi support answered they can fix your phone, but they didn't say they can safe your data on it, right!? So try to get a full backup off your device in preloader mode (SLA/DAA bypass and VCOM drivers needed)
After that important step you can unlock bootloader with mtkclient, install TWRP and *proof me wrong (xiaomi devices are hackable/have weak security implementations). In any case do not perform factory reset, your backup is always only backup of android OS and therefore incomplete (there are several OS on every device)
btw fastboot doesn't require usb-debugging (that's adb, not fastboot)

Do you have a tutorial about it?
aIecxs said:
I don't think that trick will work. even if it would be possible to cheat that easy, encryption key is bonded to bootloader lock state. so if you somehow magically managed to unlock bootloader without triggering factory reset, your data could no longer decrypted from android OS and is therefore lost.
Xiaomi support answered they can fix your phone, but they didn't say they can safe your data on it, right!? So try to get a full backup of your device in EDL mode (patched firehose programmer and deep flash cable needed)
Click to expand...
Click to collapse

Related

Manually turn on USB debugging on Nexus 5?

Android users need help with my phone! I am trying to manually turn on USB debugging (to access files on phone through update thru ADB mode in recovery options, I can install the driver for the phone but won't work until USB debugging is turned on) while my phone cannot boot into the OS. Is there a secret way to turn on USB debugging through recovery mode? (I do not want to wipe the data, and phone unfortunately is not rooted)
USB debugging has nothing to do with adb via recovery. It is an Android only setting. Recovery cannot use it and does not need it.
Adb doesn't work in stock recovery. I wrote a useful thread for people who are new to adb, as you are. You can get to it via the link in my signature. The thread is called "adb and fastboot. What isn't?".
It teaches you how to set it up and use it correctly.
Sent from my Nexus 5 using Tapatalk
rootSU said:
USB debugging has nothing to do with adb via recovery. It is an Android only setting. Recovery cannot use it and does not need it.
Adb doesn't work in stock recovery. I wrote a useful thread for people who are new to adb, as you are. You can get to it via the link in my signature. The thread is called "adb and fastboot. What isn't?".
It teaches you how to set it up and use it correctly.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
My main issue is that I am trying to retrieve my non backuped data on the phone and the phone itself will not boot into the Android OS.
I have looked into unlocking the fastboot/bootloader but it will wipe the data which would be pointless.
The data on the phone is more critical to me than the phone itself (and yes I was dumb enough to not back it up, didn't expect a flagship phone less than a year to crash on me, but I have learned for next time).
I am looking for any possible way to retrieve the data. I have tried to access the phone from the computer but I cannot access it since USB debugging is turned off and the phone is not rooted or doesn't have any other modifications.
Is there any way at this point I can retrieve the data off the phone with a non bootable OS and locked and stock Android OS?
Y is it non bootable?
Sent from my Android 5.0 Nexus 5
You are stuck. Stock recovery, locked bootloader, and OS will not boot. As RootSU mentioned, USB debugging has nothing to do with this. Stock recovery will not connect to adb.
Unless you can get the phone to boot looks like data is lost. Sorry.
Yoda8232 said:
Is there any way at this point I can retrieve the data off the phone with a non bootable OS and locked and stock Android OS?
Click to expand...
Click to collapse
No.
Yoda8232 said:
didn't expect a flagship phone less than a year to crash on me
Click to expand...
Click to collapse
Expect it from every electronic device. Especially expensive and complicated ones.
So I actually had warranty left from Google (bought directly from Google) and was going to RMA it but I decided not to because the data on there is important to me and worth more than the phone itself (yes I should of backuped everything but oh well what can I do now). And I bought a new phone so this Nexus 5 will be my little side project to try and revive it; somehow.
I will try to keep going at it, I have small programming/coding skills but it would be nice to find a way to open up the USB debugging option on the locked stock phone somehow that doesn't bootup.
Any suggestions on where I should start to start testing different "procedures"?

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

[GUIDE] Bootloader Unlock On RUI 2.0 based on Android 11(R)

(26/09/21) Note.- This tool is primarily for realme 6Pro on RUI2.0, and is expected to work on it without issues. However deep-test apks sometimes work for other devices too... If it's working on yours then good, if not then there's nothing that can be done except find the correct one for your device [c.realme.com]. These tools have in-built checks and I have no idea which parameters it considers, if I had to guess I'd say a certain fw version requirement and the model of chipset. So if you have any device other than RMX2061/3 and this tool didn't work, I'm sorry.
If you've updated to realme UI 2.0 and want to unlock, this will allow you to do it.
Your warranty may now be void.​Warning.-
*After unlocking your phone ALL OF YOUR DATA WILL BE ERASED! Backup before you Proceed.*
*After unlocking Widevine L1 will be replaced by Widevine L3, which as of now can't be fixed/patched. If you already had L3 on locked bootloader... My condolences.*
*Safety-Net fails so some banking apps may not work and Play Store certification will be gone*
Prerequisites:
ADB and Fastboot.
Deeptesting APK for A11.
Steps for Unlock:-
Backup your data.​
Install deeptesting.apk.​
Open the app and click start applying.​
Wait for application to be summited and processed.​
Minimize the app and head over to developer settings and turn on OEM Unlock and USB Debugging.​
Open deeptesting again and click on start in-depth test, the phone will reboot to bootloader. OR manually do that by pressing volume - and power in switched off state.​
Connect phone to PC. Open ADB folder and use right click+shift and from the there click on open powershell/cmd here or type cmd in address bar.​
Type fastboot flashing unlock(cmd) or ./fastboot flashing unlock(powershell).​
Use volume and power button to select unlock the bootloader.​
Phone will format and reboot.
*If you had unlocked bootloader and updated from RUI 1.0 --> 2.0, you don't need to repeat this.*
*If you know how to unlock or have unlocked before, Congratulations! Also this guide isn't for you, but you may find the APK useful.*
*For people who are unlocking their device for the first time, make sure when re-locking, all partitions are stock, or you'll have a very bad day... or a week/month if there aren't any service center nearby.*
Thank you
key combinations for fastboot mode not working
dks4deepak said:
key combinations for fastboot mode not working
Click to expand...
Click to collapse
Use adb reboot-bootloader.
debdeep98 said:
Use adb reboot-bootloader.
Click to expand...
Click to collapse
when stuck at boot /recovery destroyed screen. there is no adb.
dks4deepak said:
when stuck at boot /recovery destroyed screen. there is no adb.
Click to expand...
Click to collapse
Locked on custom partitions?
Motherboard change is the only option now.
Good morning,
i tried this deep testing version on my realme 8 5g (android 11 UI 2.0),
but it doesn't work and the message comes out
"Failed to submit application. - This phone model does not support deep testing."
what can I do?
freder_ said:
Good morning,
i tried this deep testing version on my realme 8 5g (android 11 UI 2.0),
but it doesn't work and the message comes out
"Failed to submit application. - This phone model does not support deep testing."
what can I do?
Click to expand...
Click to collapse
Wait for realme to allow bl unlocks on 8 5G.
debdeep98 said:
If you've updated to realme UI 2.0 and want to unlock, this will allow you to do it.
Your warranty may now be void.​Warning.-
*After unlocking your phone ALL OF YOUR DATA WILL BE ERASED! Backup before you Proceed.*
*After unlocking Widevine L1 will be replaced by Widevine L3, which as of now can't be fixed/patched. If you already had L3 on locked bootloader... My condolences.*
*Safety-Net fails so some banking apps may not work and Play Store certification will be gone*
Prerequisites:
ABD and Fastboot.
Deeptesting APK for A11.
Steps for Unlock:-
Backup your data.​
Install deeptesting.apk.​
Open the app and click start applying.​
Wait for application to be summited and processed.​
Minimize the app and head over to developer settings and turn on OEM Unlock and USB Debugging.​
Open deeptesting again and click on start in-depth test, the phone will reboot to bootloader. OR manually do that by pressing volume - and power in switched off state.​
Connect phone to PC. Open ADB folder and use right click+shift and from the there click on open powershell/cmd here or type cmd in address bar.​
Type fastboot flashing unlock(cmd) or ./fastboot flashing unlock(powershell).​
Use volume and power button to select unlock the bootloader.​
Phone will format and reboot.
*If you had unlocked bootloader and updated from RUI 1.0 --> 2.0, you don't need to repeat this.*
*If you know how to unlock or have unlocked before, Congratulations! Also this guide isn't for you, but you may find the APK useful.*
*For people who are unlocking their device for the first time, make sure when re-locking, all partitions are stock, or you'll have a very bad day... or a week/month if there aren't any service center nearby.*
Click to expand...
Click to collapse
Deep testing apk you shared doesnt work on realmi 7i UI.2.0 Android 11
DeSmanAryPotter said:
Deep testing apk you shared doesnt work on realmi 7i UI.2.0 Android 11
Click to expand...
Click to collapse
Yeah it's for the 6Pro. When realme allows unlocks on 7i it'll work.
debdeep98 said:
If you've updated to realme UI 2.0 and want to unlock, this will allow you to do it.
Your warranty may now be void.​Warning.-
*After unlocking your phone ALL OF YOUR DATA WILL BE ERASED! Backup before you Proceed.*
*After unlocking Widevine L1 will be replaced by Widevine L3, which as of now can't be fixed/patched. If you already had L3 on locked bootloader... My condolences.*
*Safety-Net fails so some banking apps may not work and Play Store certification will be gone*
Prerequisites:
ABD and Fastboot.
Deeptesting APK for A11.
Steps for Unlock:-
Backup your data.​
Install deeptesting.apk.​
Open the app and click start applying.​
Wait for application to be summited and processed.​
Minimize the app and head over to developer settings and turn on OEM Unlock and USB Debugging.​
Open deeptesting again and click on start in-depth test, the phone will reboot to bootloader. OR manually do that by pressing volume - and power in switched off state.​
Connect phone to PC. Open ADB folder and use right click+shift and from the there click on open powershell/cmd here or type cmd in address bar.​
Type fastboot flashing unlock(cmd) or ./fastboot flashing unlock(powershell).​
Use volume and power button to select unlock the bootloader.​
Phone will format and reboot.
*If you had unlocked bootloader and updated from RUI 1.0 --> 2.0, you don't need to repeat this.*
*If you know how to unlock or have unlocked before, Congratulations! Also this guide isn't for you, but you may find the APK useful.*
*For people who are unlocking their device for the first time, make sure when re-locking, all partitions are stock, or you'll have a very bad day... or a week/month if there aren't any service center nearby.*
Click to expand...
Click to collapse
I can not install the app, how can I do?
Facux3 said:
I can not install the app, how can I do?
Click to expand...
Click to collapse
Device and Android version.
nice work
the adb folder is not opening , what to do ? im using windows 10
What do you mean? Access denied? Try downloading platform tools again.
p.pc said:
the adb folder is not opening , what to do ? im using windows 10
Click to expand...
Click to collapse
How about Realme X7 Pro?
lfnisme said:
How about Realme X7 Pro?
Click to expand...
Click to collapse
You can try. See if it works.
App not installed on realme X2 Pro
debdeep98 said:
If you've updated to realme UI 2.0 and want to unlock, this will allow you to do it.
Your warranty may now be void.​Warning.-
*After unlocking your phone ALL OF YOUR DATA WILL BE ERASED! Backup before you Proceed.*
*After unlocking Widevine L1 will be replaced by Widevine L3, which as of now can't be fixed/patched. If you already had L3 on locked bootloader... My condolences.*
*Safety-Net fails so some banking apps may not work and Play Store certification will be gone*
Prerequisites:
ABD and Fastboot.
Deeptesting APK for A11.
Steps for Unlock:-
Backup your data.​
Install deeptesting.apk.​
Open the app and click start applying.​
Wait for application to be summited and processed.​
Minimize the app and head over to developer settings and turn on OEM Unlock and USB Debugging.​
Open deeptesting again and click on start in-depth test, the phone will reboot to bootloader. OR manually do that by pressing volume - and power in switched off state.​
Connect phone to PC. Open ADB folder and use right click+shift and from the there click on open powershell/cmd here or type cmd in address bar.​
Type fastboot flashing unlock(cmd) or ./fastboot flashing unlock(powershell).​
Use volume and power button to select unlock the bootloader.​
Phone will format and reboot.
*If you had unlocked bootloader and updated from RUI 1.0 --> 2.0, you don't need to repeat this.*
*If you know how to unlock or have unlocked before, Congratulations! Also this guide isn't for you, but you may find the APK useful.*
*For people who are unlocking their device for the first time, make sure when re-locking, all partitions are stock, or you'll have a very bad day... or a week/month if there aren't any service center nearby.*
Click to expand...
Click to collapse
My device is realme x2 (Chinese rom). when I tried to install the deep testing app it says an app with same signature has already been installed . But I did not install that app never before. How can I do this?
My device is realme x2 (Chinese rom). when I tried to install the deep testing app it says an app with same signature has already been installed . But I did not install that app never before. How can I do this?

Rooting problem and strange phone behaviour while it

Hello. I'm an owner of a Xiaomi Redmi 9A and I have following rooting problems with it:
1. while beeing in phone's fastboot mode and after sending from the computer's terminal (after sucessfull connection):
"fastboot oem unlock"
the phone "thinks" for a short bit before restarting itself without doing anything
2. I have a Xiaomi account bound to the phone and when selecting the "check unlock state" the phone ask me to turn off wifi, enable the (paid) data transfer and bind the phone to the account
3. while using the official Xaiomi unlock tool (with was downloaded from the phone producer's website), the phone isn't even seen in it
Could anyone help me ?
Try installing usb drivers or the phone will never be detected.
VD171 said:
Try installing usb drivers or the phone . never be detected.
Click to expand...
Click to collapse
in case of adb and fastboot, I had used them on Linux.
Only the official unlocking tool was for Windows, on with the usb drivers were installed.
Linux detect it without any issue
Just use it to unlock on Linux:
XiaoMiTool V2 - Modding of Xiaomi devices made easy for everyone
XiaoMiTool V2 is a easy to use tool to install rom on your Xiaomi device. Modding made easy for everyone! Download it for free now!
xiaomitool.com
VD171 said:
Just use it to unlock on Linux:
XiaoMiTool V2 - Modding of Xiaomi devices made easy for everyone
XiaoMiTool V2 is a easy to use tool to install rom on your Xiaomi device. Modding made easy for everyone! Download it for free now!
xiaomitool.com
Click to expand...
Click to collapse
thanks, but it seem to don't work correctly with my phone.
After my phone had become detected when was in the fastboot mode and after clicking the "select" button in the app, the phone has rebooted to the normal mode and asked to scan again. It hasn't done anything except the mentioned above.
mcgiwer said:
thanks, but it seem to don't work correctly with my phone.
After my phone had become detected when was in the fastboot mode and after clicking the "select" button in the app, the phone has rebooted to the normal mode and asked to scan again. It hasn't done anything except the mentioned above.
Click to expand...
Click to collapse
Did you enable usb debugging on developer settings?
Did you allow the usb debugging for the actual computer?
VD171 said:
Did you enable usb debugging on developer settings?
Did you allow the usb debugging for the actual computer?
Click to expand...
Click to collapse
yes in both cases... I have even enabled the "oem unlock" option in the setting
Install windows on partition 30Gb, change cable
yaro666 said:
Install windows on partition 30Gb, change cable
Click to expand...
Click to collapse
The cable is new and I won't wipe my Linux to install a Windows (about with I have a bad opinion)
Make a dual boot, just resize partition, you need 30Gb and in 45min you will know what is the problem.
Or you can try to liveboot windows from usb stick.
yaro666 said:
Make a dual boot, just resize partition, you need 30Gb and in 45min you will know what is the problem.
Or you can try to liveboot windows from usb stick.
Click to expand...
Click to collapse
Question: Why do you push so much on me to install Windows?
This forum is dedicated to mobile phones and my topic is about anormal phone behaviour of a phone while attempt to root it. Wiping out a safe Linux and installing a Windows won't help at all....
I tryed to root the phone on friend's laptop with a Windows (with the latest drivers and software installed) and it didn't worked.
I suspect that the producer probably has fabrically instaled a damaged or improper firmware
As you wish. Windows is more device friendly. I just suggest to do it on W, nothing more.
You state that fastboot works, but Linux don't see your phone, like in case you don't have drivers for adb. We don't know if you installed everything on Linux properly
yaro666 said:
As you wish. Windows is more device friendly. I just suggest to do it on W, nothing more.
You state that fastboot works, but Linux don't see your phone, like in case you don't have drivers for adb. We don't know if you installed everything on Linux properly
Click to expand...
Click to collapse
hello. You had missread my post. I wrote that it isn't seen only in the unlock software. Fastboot and ADB detect it correctly

Categories

Resources