Asus Transformer TF303K bricked ? - Upgrading, Modifying and Unlocking

Hi,
I appeal for the community help to try to get rid of my tablet "boot-loop" !
Here is the situation today :
My tablet no more boots on Android. It starts on what I believe is the bootloader (see screenshot) but this original bootloader doesn't allow me (through volume +/-) to choose between the usual recovery/boot/reboot choices. I can't do anything except a long press on power to switch off the device. On this "bootloader" screen, I fortunately can send fastboot commands.
What I can do :
- fastboot reboot => ok, the device reboots and comes back to the same screen
- fastboot continue => most of the time (if not always) it does nothing, but some few times (I can't manage when exactely) it continues the boot and goes to the loading screen with ASUS image and loading spinner, but the boot doesn't go further : I let it a full night and the device was still on this screen.
- fastboot flash boot boot.img => ok. The image (from a zip downloaded on ASUS website asus.com/Tablets/ASUS_Transformer_Pad_TF303K/HelpDesk_Download ) is flashed successfully.
- fastboot erase xxx => ok, clean the partition
- fastboot oem unlock => FAILED (remote: Invalid signature, fail to unlock!!)
How I finally get here :
I wanted to root/unlock my device, except I may acted as a newbee ! Finally, today, I don't really know what is the whole set of commands I have sent.
I saw too late that ASUS provide an unlocker tool. The problem was I was under an official but too recent android version to run this tool.
Some information :
A few month ago, I had this issue, and, by insisting I managed to boot normally and fully on android. At this time, I told myself that I will never switch off the device, but, this happened !
So, today I need your help :
Do you know how I can get rid of this bootloop ?
Does the screenshot is really what is called the bootloader ? (even with no volume +/- control ?)
I saw it exists a tool named "ASUS Flash Tool" but it needs "raw" images and not zips like we can download on the ASUS website. Does anybody know what are this raw files made of, and how I could eventually convert a zip to this raw format ?
If anybody have original backups of the TF303k, they may be very helpful for me !
Thanks for any help or advices ! :fingers-crossed:

An ultime little up... :crying:
Edit : Or if anybody have a TF303K, if you can send me a backup of your system partitions, I'll really apreciate it ! :fingers-crossed:

virtcs said:
Hi,
I appeal for the community help to try to get rid of my tablet "boot-loop" !
Here is the situation today :
My tablet no more boots on Android. It starts on what I believe is the bootloader (see screenshot) but this original bootloader doesn't allow me (through volume +/-) to choose between the usual recovery/boot/reboot choices. I can't do anything except a long press on power to switch off the device. On this "bootloader" screen, I fortunately can send fastboot commands.
What I can do :
- fastboot reboot => ok, the device reboots and comes back to the same screen
- fastboot continue => most of the time (if not always) it does nothing, but some few times (I can't manage when exactely) it continues the boot and goes to the loading screen with ASUS image and loading spinner, but the boot doesn't go further : I let it a full night and the device was still on this screen.
- fastboot flash boot boot.img => ok. The image (from a zip downloaded on ASUS website asus.com/Tablets/ASUS_Transformer_Pad_TF303K/HelpDesk_Download ) is flashed successfully.
- fastboot erase xxx => ok, clean the partition
- fastboot oem unlock => FAILED (remote: Invalid signature, fail to unlock!!)
How I finally get here :
I wanted to root/unlock my device, except I may acted as a newbee ! Finally, today, I don't really know what is the whole set of commands I have sent.
I saw too late that ASUS provide an unlocker tool. The problem was I was under an official but too recent android version to run this tool.
Some information :
A few month ago, I had this issue, and, by insisting I managed to boot normally and fully on android. At this time, I told myself that I will never switch off the device, but, this happened !
So, today I need your help :
Do you know how I can get rid of this bootloop ?
Does the screenshot is really what is called the bootloader ? (even with no volume +/- control ?)
I saw it exists a tool named "ASUS Flash Tool" but it needs "raw" images and not zips like we can download on the ASUS website. Does anybody know what are this raw files made of, and how I could eventually convert a zip to this raw format ?
If anybody have original backups of the TF303k, they may be very helpful for me !
Thanks for any help or advices ! :fingers-crossed:
Click to expand...
Click to collapse
Exactly the same here!! Any news? How to fix this 'always boot to fastboot but I can still get into system by using fastboot boot boot.img command'?!
EDIT 1: This ASUS specific fastboot command seems to be a big life saver because it RESETS the Tampered Flag to False: "fastboot oem reset-dev_info"! Hurray!

fastboot oem reset-dev_info
Click to expand...
Click to collapse
Yeah, this did it for me too! Thanks a lot!
How did you get knowledge of this flag?
Je\/er
hackwerk said:
Exactly the same here!! Any news? How to fix this 'always boot to fastboot but I can still get into system by using fastboot boot boot.img command'?!
EDIT 1: This ASUS specific fastboot command seems to be a big life saver because it RESETS the Tampered Flag to False: "fastboot oem reset-dev_info"! Hurray!
Click to expand...
Click to collapse

Jever2000 said:
Yeah, this did it for me too! Thanks a lot!
How did you get knowledge of this flag?
Je\/er
Click to expand...
Click to collapse
If you are thankful, please press Thanks button under my posts
The Tampered Flag is an OEM specific thing, and all fastboot oem commands are specific per brand and type.
As the ASUS TF303K is a clone of the (ASUS) Google Nexus 7 (2013)(Flo), I read ALL stuff on the Nexus 7 (2013) everywhere. You'll see this command a lot.
Unfortunately the Nexus is unlockable (fastboot oem unlock), and ours is NOT in any way.
One of the best posts is this one.
Still hope ANY one can help us unlocking the bootloader, or help us on how to flash another ROM (Nexus 7 2013?) to our device using Qualcomm tools (QPST / QFil / MiFlash etc etc)? :'(

hackwerk said:
EDIT 1: This ASUS specific fastboot command seems to be a big life saver because it RESETS the Tampered Flag to False: "fastboot oem reset-dev_info"! Hurray!
Click to expand...
Click to collapse
It didn't do the job for me
I still get an endless waiting screen when fastbooting boot.img.
Can anybody would accept to dump its partitions ? (system, boot, and recovery) ? This should do the trick and may not require root ! Thanks so much !

Related

ROOT Elephone S7 4gb on Windows 10x64 at last!

For those that, like me, could not get driver recognition on the latest Win 10 x64 no matter what you tried. And ,yes, using every tutorial I could find on this and two "other Forums". Odin failed to see my device (still can't) Cydia impactor allows rebooting into fastboot and D/L but doesn't connect in either alt. mode. Yes, drivers all removed and replaced in varying states (usbdeview, etc.).
But ADB/Fastboot works!
Make sure you have your adb/fastboot drivers installed universally (Check this Fabulous Forum)
Download device-specific TWRP - I used this one for the 4gb version - https://www.dropbox.com/s/b7u3k1mgpppxlyx/recovery.img?dl=0
L.Shift-R. click in the folder you downloaded to (Open Command Window Here) - "adb devices" (to make sure device registers) then - "adb reboot bootloader" gets you into fastboot. - "fastoot boot {your-recovery-name}.img"
I got a fully functional TOUCH CAPABLE TWRP. Which I proceeded to load this - https://www.dropbox.com/s/j1owqv7mjkdpo75/UPDATE-SuperSU-v2.46.zip?dl=0 - and, VOILA! ROOT!!
I had similar issues with my laptop and drivers. Used a friend laptop in the end to "see" the phone and install twrp.
Sent from my S7 using Tapatalk
When I try to boot the recovery.img with fastboot it says that my OEM is locked. I check OEM unlock in developer options, then I do: adb reboot bootloader, then fastboot oem unlock. A warning appears saying to press VOLUME UP button to continue, voiding the warranty or VOLUME DOWN to go back. I try to press VOLUME UP and nothing happens... how did you do it?
vaskovass said:
When I try to boot the recovery.img with fastboot it says that my OEM is locked. I check OEM unlock in developer options, then I do: adb reboot bootloader, then fastboot oem unlock. A warning appears saying to press VOLUME UP button to continue, voiding the warranty or VOLUME DOWN to go back. I try to press VOLUME UP and nothing happens... how did you do it?
Click to expand...
Click to collapse
Hi there, I have the same issue. No success
I found a way, instead of volume up, use the home button this worked for me.. however after I unlocked the OEM and flashed TWRP the phone didn't want to boot anymore. It was stuck on Elephone logo with warning: "Orange State: The phone has been unlocked and can't be trusted. Your device will boot in 5s", however it didn't boot and stayed like that for almost an hour. Had to flash back the stock firmware to boot. Tried 1 more time the procedure to root but again the same. Maybe I do something wrong?
stock fw flash back
Hi, please can you help me with how you flashed back the stock firmware?
I get an error message with twrp : invalid zip file format.
Thank you in advance!
dnsgtr said:
Hi, please can you help me with how you flashed back the stock firmware?
I get an error message with twrp : invalid zip file format.
Thank you in advance!
Click to expand...
Click to collapse
I read somewhere the is a zip inside the update.zip & is that one that is flash able with twrp.
Have a look
During the main time I managed to flash the 0218 stock rom.
I still got the orange message but the phone finally boot. Then I just called the twrp recovery img via atb. I did nothing only touch the reboot in the twrp screen and since then "Orange status...." again.
May be the twrp recovery img is not the right one...
Bad command "fastoot boot {your-recovery-name}.img"
after OEM alow (informacion phone/compilacion number touch fast 9 times/access/alow oem)
fastboot oem unlock
"fastboot boot {your-recovery-name}.img" for me is fastboot boot recovery.img and all OK
bat still not working (phone not thrust unlocked bootloader cleaning data in 5..4..3..2..1.. and rebot)

How to wipe android partitons while NO access to Fastboot? PLZ help

Hi,
I have a unique problem. I cant go into fastboot. Yes, fastboot on my OPT is not a opltion.
I cant instal TWRP. I can't wipe the OS to flash a new one.
My question is this:
Is there a way to wipe the partitions on a android phone via windows or something?
This problem is created by me. Somehow I flash OOS over CM (??)
So when my phone boots (bootloader is unlocked) I will see 2 boot sequences wich prevents me from accesing the fastboot menu.
The solution I see is this: Enter TWRP --> Wipe all but USB-OTG ...
Anyway, I hope there is a android Einstein here because I'm at a loss..
Feel free to ask any questions and pls help me!
Grt TwoChill
TowChill said:
Hi,
I have a unique problem. I cant go into fastboot. Yes, fastboot on my OPT is not a opltion.
I cant instal TWRP. I can't wipe the OS to flash a new one.
My question is this:
Is there a way to wipe the partitions on a android phone via windows or something?
This problem is created by me. Somehow I flash OOS over CM (??)
So when my phone boots (bootloader is unlocked) I will see 2 boot sequences wich prevents me from accesing the fastboot menu.
The solution I see is this: Enter TWRP --> Wipe all but USB-OTG ...
Anyway, I hope there is a android Einstein here because I'm at a loss..
Feel free to ask any questions and pls help me!
Grt TwoChill
Click to expand...
Click to collapse
Here you can find a recovery guide:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I'd recommend methode 2, because it seems more east to do.
Good luck!
TowChill said:
Hi,
I have a unique problem. I cant go into fastboot. Yes, fastboot on my OPT is not a opltion.
I cant instal TWRP. I can't wipe the OS to flash a new one.
My question is this:
Is there a way to wipe the partitions on a android phone via windows or something?
This problem is created by me. Somehow I flash OOS over CM (??)
So when my phone boots (bootloader is unlocked) I will see 2 boot sequences wich prevents me from accesing the fastboot menu.
The solution I see is this: Enter TWRP --> Wipe all but USB-OTG ...
Anyway, I hope there is a android Einstein here because I'm at a loss..
Feel free to ask any questions and pls help me!
Grt TwoChill
Click to expand...
Click to collapse
If you are getting two boot screens, please confirm if this is what you see in your first boot screen:
some text which goes like "Your device cannot be trusted etc etc. fastboot oem lock something something"
If yes, press the volume buttons at this screen, which will take you to an "Options menu"
This will have options to power off, restart, recovery, fastboot, back to previous page.
use volume down buttons to move selection to fastboot and press power button to select fastboot.
This will take you to bootloader.
Alternatively:
Is the device getting identified by your computer when connected?
If yes, and if you have adb tools installed, try this command, after connecting to computer and selecting usb configuration as transfer files
adb devices
The result of this should show your device
then type:
adb reboot bootloader
This should take you to your bootloader screen.
pvramk said:
If you are getting two boot screens, please confirm if this is what you see in your first boot screen:
some text which goes like "Your device cannot be trusted etc etc. fastboot oem lock something something"
If yes, press the volume buttons at this screen, which will take you to an "Options menu"
This will have options to power off, restart, recovery, fastboot, back to previous page.
use volume down buttons to move selection to fastboot and press power button to select fastboot.
This will take you to bootloader.
Alternatively:
Is the device getting identified by your computer when connected?
If yes, and if you have adb tools installed, try this command, after connecting to computer and selecting usb configuration as transfer files
adb devices
The result of this should show your device
then type:
adb reboot bootloader
This should take you to your bootloader screen.
Click to expand...
Click to collapse
Thank you for your replay.
I have done all of this and i do understand how this works.
I have adb drivers installed, my computer does reconizes my phone and everything works even the reboot to bootloader via CMD. (adb devices, it shows, etc)
When my phone then tries to access the bootloader, it will show those messeges " this devices cant be trusted etc etc." afther 5 seconds again I see the the android logo (with a few lines of static on the bottom) (( that clearly is not right )) but it will show me again the same message " this devices cant be trusted etc etc" ... then it will just show me the battery icon and power precentage (this if I choose to boot to bootloader) or else it starts normally..
Clearly the flashing of CM failed. And with a sideload to install OxygenOS I can use it.. But it does prevents me from accessing the fastboot mode..
So Is there an alternative way to install TWRP without using the fastboot mode? Or is there an other way i can try to wipe the partitions inc. the os?
From there I know what to do.
TowChill said:
Thank you for your replay.
I have done all of this and i do understand how this works.
............
So Is there an alternative way to install TWRP without using the fastboot mode? Or is there an other way i can try to wipe the partitions inc. the os?
From there I know what to do.
Click to expand...
Click to collapse
well if you are rooted you can try using an app called flashify or flashfire to install twrp
pvramk said:
well if you are rooted you can try using an app called flashify or flashfire to install twrp
Click to expand...
Click to collapse
Thanks! Unfortunatly my phone isn't rooted anymore ..
I'm screwed right?
TowChill said:
Thanks! Unfortunatly my phone isn't rooted anymore ..
I'm screwed right?
Click to expand...
Click to collapse
When the display shows the battery % check if fastboot devices shows your device?
If not I'm sorry, I would not be of any more help to you my friend.
Hope someone more knowledgeable comes along and clears your problem....
TowChill said:
Thank you for your replay.
I have done all of this and i do understand how this works.
I have adb drivers installed, my computer does reconizes my phone and everything works even the reboot to bootloader via CMD. (adb devices, it shows, etc)
When my phone then tries to access the bootloader, it will show those messeges " this devices cant be trusted etc etc." afther 5 seconds again I see the the android logo (with a few lines of static on the bottom) (( that clearly is not right )) but it will show me again the same message " this devices cant be trusted etc etc" ... then it will just show me the battery icon and power precentage (this if I choose to boot to bootloader) or else it starts normally..
Clearly the flashing of CM failed. And with a sideload to install OxygenOS I can use it.. But it does prevents me from accessing the fastboot mode..
So Is there an alternative way to install TWRP without using the fastboot mode? Or is there an other way i can try to wipe the partitions inc. the os?
From there I know what to do.
Click to expand...
Click to collapse
If nothing works, try method 2 from the Hard Brick guide from Naman Bhalla.

[BRICKED] Stuck in android 8.1 bootloop

I just bricked my phone :crying: :crying:
I wanna get back to the official rom, after trying android P (without make it work).
(the rom is from http://en.miui.com/download-354.html)
But I run the wrong script and take the flash_all_lock.img
And my device is stuck on android 8.1 bootloop (It boot, but i get an animated line loop ...)
Any ideas or tricks before i get it back to warranty ?
Thanks
Unlock bootloader and flash again. You can find a guide to unlock bootloader at the beginning of this guide.
BubuXP said:
Unlock bootloader and flash again. You can find a guide to unlock bootloader at the beginning of this guide.
Click to expand...
Click to collapse
But since I flashed the official rom with data whipe, I'm unable to go to dev option and enter OEM Unlocking .... And Fastboot respond me that my device is locked
Seems like my only option left is to boot into EDL mode ...
But seems fastboot oem edl does not work I don't lnow how to handle the problem
droopeur said:
Seems like my only option left is to boot into EDL mode ...
But seems fastboot oem edl does not work I don't lnow how to handle the problem
Click to expand...
Click to collapse
Have you tried to switch the active slot?
Try if it boots using
fastboot set_active a
or
fastboot set_active b
If not working, can you enter recovery (power on with Volume up button pressed)?
If you can enter recovery, hold down the power button for 3-5 seconds and then press and release the Volume up button, to make commands appear. Then your only hope is to install the OTA update zip from there (copy the OTA in a microSD card, there is a thread where you can find the link to the OTA zip).
In my opinion, "OEM unlocking" in developer options MUST be always keep active, because incidents like this could happen, and because even without modding, an OTA could go wrong resulting in your same situation.
I was in your same situation (OEM unlocking disabled and then I locked bootloader with a custom ROM installed) with a Nexus 5X.
I don't remember well how I fixed it, but I remember entering in Qualcomm download mode (should be the same EDL mode) and loading a file found after many hours of research in strange forums and sites.
BubuXP said:
Have you tried to switch the active slot?
Try if it boots using
fastboot set_active a
or
fastboot set_active b
Click to expand...
Click to collapse
In fact, both work, but my phone still stucked at the bootloader (infinite line animation in both cases).
BubuXP said:
If not working, can you enter recovery (power on with Volume up button pressed)?
If you can enter recovery, hold down the power button for 3-5 seconds and then press and release the Volume up button, to make commands appear. Then your only hope is to install the OTA update zip from there (copy the OTA in a microSD card, there is a thread where you can find the link to the OTA zip).
Click to expand...
Click to collapse
Yes I can enter recovery and I have already tried this, but I always end up with the error:
Code:
E: Unknow volume for path [/sideload/package.zip]
Verifying update package...
Update package verification took 17.3 s (result 0)
Installing update...
E:Error il /sideload/package.zip (Status 1)
Installation aborted
BubuXP said:
In my opinion, "OEM unlocking" in developer options MUST be always keep active, because incidents like this could happen, and because even without modding, an OTA could go wrong resulting in your same situation.
I was in your same situation (OEM unlocking disabled and then I locked bootloader with a custom ROM installed) with a Nexus 5X.
I don't remember well how I fixed it, but I remember entering in Qualcomm download mode (should be the same EDL mode) and loading a file found after many hours of research in strange forums and sites.
Click to expand...
Click to collapse
Yes of course !
But I revert to stock rom with Mi Flash and I click on Flash all and lock, since the telephone should have been "brand new" it should not have any problems but ...
I have to enter EDL mode, but don't know how to do it since modified fastboot executables does not activate it it just reboot the phone...
Deep flash cable may help but not shure if it works, or I may have to disassemble the device to find EDL pins...
after unlock bootloader type fastboot flashing unlock_critical and flash with miflash tool
LUNARIO said:
after unlock bootloader type fastboot flashing unlock_critical and flash with miflash tool
Click to expand...
Click to collapse
But since I can't activate OEM I can't unlock bootloader....
try this http://www.xiaomitool.com/ not sure if it works on our phone but maybe can unlock the bootloader so you can use miflash
Have you sideloaded the zip? I think it's better to copy the OTA zip to microSD than ADB sideload.
droopeur said:
I have to enter EDL mode, but don't know how to do it since modified fastboot executables does not activate it it just reboot the phone...
Deep flash cable may help but not shure if it works, or I may have to disassemble the device to find EDL pins...
Click to expand...
Click to collapse
There should be only two methods for entering EDL:
1- request authorization in en.miui.com forum. Sometimes the admins accept requests to give an account one EDL flash permission (but I don't know if it works with AndroidOne devices).
2- finding the test point in the phone's motherboard.
Hi guys,
i tried to install this twrp but it doesnt work...
so i searched on internet and i found another article, i tried to check the current partition and install in another way
for first:
fastboot getvar current-slot
after i do this
fastboot boot_b recovery.img
and then
fastboot set_active b
so nothing to do....but right now my MI A2 lite not boot.
i try again to check my partition but this time i have no replay.
i have unlocked bootloader but i cant go to recovery and i cant boot!!
someone can help me please?
I HAVE THE SAME PROBLEM
everything you said is completely simillar to mine. Can someone help us? Or did you already fix it? Please help me i need my phone working.
I have same problem fastboot flash but after that, it started to reboot automatically. The phone was automatically turning off and on. I again did a "clean all and lock" via miflash tool but still now, no result!
I can boot into recovery without having any problem. But when I boo to setup country date....etc, it starts its auto rebooting process,
Any help ?
droopeur said:
But since I can't activate OEM I can't unlock bootloader....
Click to expand...
Click to collapse
Same situation here. I am desperate!! Did you solve it?
Isso resolve
steledama said:
Same situation here. I am desperate!! Did you solve it?
Click to expand...
Click to collapse
gadgetsfarm.com/download-mi-a2-lite-fastboot-rom-v9-6-4-download/[/url]
How to unbrick?
Hey guys. I bricked my Mi2 Lite as well. Is there any step by step way to unbrick?
had the same problem, was stuck in the bootloop even after I flashed img with MiFlash! NOTE: MY BOOTLOADER WAS UNLOCKED!!! (LUCKLY I DID NOT TRIED FLASH ALL AND UNLOCK!)
headed to this thread
Code:
fastboot flashing unlock
fastboot flashing unlock_critical
did not work, I get error saying FAILED
but after i used
Code:
fastboot oem edl
I went to MiFlash and used "Clean all" option (again note DON'T use "Clean all and lock"!!!). It took around 5 minutes to flash and my notif. light blinked whole the time. After it say "Success" I was able to normaly boot the phone again
Find "Mi A2 Lite toolkit V 1.0.4.2" and use it to flash stock 8.1, it will do all the magic with a few clicks, just don't interrupt it until your phone restarts and you get the "Welcome" screen. After you can do the upgrade to Pie via OTA.
Hi, where i can find MI A2 Lite Tool Kit? i open my device and i can put in EDL mode., my computer detect my pone in EDL mode, but i can not know do.
I like bypass FRP, can anybody help me
Thanks.
mr_techno said:
Find "Mi A2 Lite toolkit V 1.0.4.2" and use it to flash stock 8.1, it will do all the magic with a few clicks, just don't interrupt it until your phone restarts and you get the "Welcome" screen. After you can do the upgrade to Pie via OTA.
Click to expand...
Click to collapse
Hi all,
I also had same problem and I just resolve it.
My phone was in bootloop mode after stock rom flashing...
You don't need apply "fastboot oem edl" !
Just be sure your device is unlocked.
Download first stock rom (V9.6.4.0.ODLMIFF Firmware for Mi A2 Lite). If you flash last ROM, it don't work.
Flash it with XiaoMiFlash tool (don't forget to enable "Clean All") in bottom of the tool.
After reboot, you can apply OTA updates.
Enjoy !

X2 Pro: "Your device is corrupt. It can’t be trusted and may not work properly."

X2 Pro: "Your device is corrupt. It can’t be trusted and may not work properly."
Hi everybody,
my Aquaris X2 Pro worked fine with rooted BQ 1.7.3 firmware (Android 8.1 based) - Magisk was installed and worked fine and also the xposed framework.
Today the device was normally working as it suddenly just reboots
After that the usual "unlocked bootloader" screen appears but then it only shows a screen with the message "Your device is corrupt. It can’t be trusted and may not work properly."
I can select "continue" - but that only leads back to the "unlocked bootloader" warning screen --> a boot loop :crying:
Does anybody know how I can bring back my device back to work - without losing all my settings and stuff?
And any idea what happened (so that I can prevent it to do so in future)?
Hmm, I'm not 100% sure, but I think I saw that message / boot process once as I tried to root my X2 Pro.
I had done a
Code:
fastboot flashing unlock / unlock-critical
but no
Code:
fastboot oem unlock
(or the other way round? Definitely only done one of them - I was following instructions from a thread here)
and was trying to boot a magisk patched boot-img via
Code:
fastboot boot magisk_patched.img
So, it looked like the bootloader was "NOT fully" unlocked and it detected booting a "not correctly signed" bootloader.
Perhaps check your unlock status via
Code:
fastboot getvar all
But note - UNLOCKING again will wipe your data ... and can only be done if the setting in developer options is active (I fear that THAT may have changed on your device)
You could also try booting the second slot
Code:
fastboot getvar current-slot
and then
Code:
fastboot set_active a/b
(if current-slot gives a, boot b and vica versa).
Last idea: try flashing ONLY the stock boot.img. If you can do this, this should re-enable you to boot. You will loose root, but may be able to backup (most) of your settings via Helium
Thanks a lot for your help!
Inbetween I had to go the hard way and reflashed the newest BQ factory image v2.0.2 (based on Android 9) to both parts _a and _b - losing all my data...
after that I patched the boot.img for magisk and reflashed that to my _a boot partition (and still have the original boot.img in _b).
It did cost me a bit of my spare time - but it wasn't as hard as I expected...
I was able to restore a lot of my settings with Titanium backup....
merlinwv said:
I had done a
Code:
fastboot flashing unlock / unlock-critical
but no
Code:
fastboot oem unlock
Click to expand...
Click to collapse
That was exactly what I did - the first time I only did a "flashing unlock", no "unlock-critical" - so now I had to do it to flash the complete factory image, and therefore it wiped all my data again
merlinwv said:
I was following instructions from a thread here)
Click to expand...
Click to collapse
I used the BQ batch script to flash it, but did not execute the erase commands.
But that did not help to keep my data as I needed to execute a "unlock-critical"...
merlinwv said:
So, it looked like the bootloader was "NOT fully" unlocked and it detected booting a "not correctly signed" bootloader.
Click to expand...
Click to collapse
Hmm, it worked for several months without problems - don't know why it suddenly complained about it.
merlinwv said:
Perhaps check your unlock status via
Code:
fastboot getvar all
Code:
fastboot getvar current-slot
Click to expand...
Click to collapse
Very interesting commands which I didn't know - I already wondered how I can get that information
merlinwv said:
Last idea: try flashing ONLY the stock boot.img. If you can do this, this should re-enable you to boot. You will loose root, but may be able to backup (most) of your settings via Helium
Click to expand...
Click to collapse
That would be a great idea :good: which I could've tried - but I didn't...; maybe next time - although I hope the problem will never come back
Bodenseematze said:
Thanks a lot for your help!
...
I used the BQ batch script to flash it, but did not execute the erase commands.
But that did not help to keep my data as I needed to execute a "unlock-critical"...
Click to expand...
Click to collapse
You are most welcome
The erase commands are not the ones doing the factory-reset - if you want to keep your data during a "factory-flash" you need to comment/delete the lines which flash the userdata-partition.
But I do not know if you can flash the factory image without unlocked critical (=boot) flashing. I never tried this myself. Some phones allow flashing of correctly signed boot images even when critical is locked, others prevent ALL flashing then.
Of course, for "he who knows what he is doing" there is always the possibility to flash in EDL-mode (turn off, afterwards keep vol+, Vol- and Power pressed - will bring you to a special flash mode that allows flashing even when locked - but via a special serial interface etc. pp.). Google it - this would have helped you regarding "loose of userdata when doing unlock critical". But of course - you need to edit the file because in EDL mode, normally userdata is flashed, too.
Just something to keep in mind for the next time
Hmm, it worked for several months without problems - don't know why it suddenly complained about it.
That would be a great idea :good: which I could've tried - but I didn't...; maybe next time - although I hope the problem will never come back
Click to expand...
Click to collapse
I think that perhaps an update was installed (explanation for the reboot?!) that switched to the other boot-slot and did a more thorough check of the boot-chain. This was the reason to suggest trying the other boot-slot (which would then be the pre-update version, that may still boot - and even have root)
merlinwv said:
Of course, for "he who knows what he is doing" there is always the possibility to flash in EDL-mode
Click to expand...
Click to collapse
Again: very interesting information! :good:
merlinwv said:
I think that perhaps an update was installed (explanation for the reboot?!)
Click to expand...
Click to collapse
I hope that wasn't the reason, because I explicitly switched off all automatic updates. And I did not do a manual update!
merlinwv said:
that switched to the other boot-slot and did a more thorough check of the boot-chain. This was the reason to suggest trying the other boot-slot (which would then be the pre-update version, that may still boot - and even have root)
Click to expand...
Click to collapse
I tried to switch to the other slot and boot it - but that didn't help either and led to the same problem...
What I didn't tried was to only flash the boot.img - will do this next time

Recovering data on a DEAD Redmi Note 8 PRO

Hello,
I hope this is the right section for this post.
I've been using a Note 8 Pro with zero issues until one week ago when I accidentally dropped the phone in the water.
After a few seconds submerged the display turned off and I felt an intense heat coming from the zone of the battery.
Having no chance to recover the phone (tried with Isopropyl Alcohol too) I decided to open it and manually dry/clean each component, having seen the situation inside gave me the phone is dead but I still want to recover some pictures/data from it.
Before opening the open Minitool was not detecting any device on my Windows Laptop, after cleaning each component Minitool is instead detecting the phone via USB, but I still can't extract any data because the "Usb debugging" option is not tuned on (and no the device is not rooted).
Is there any option to extract data from the phone? There's a way to turn on USB Debugging via ADB on a non-rooted phone?
Thanks,
Andrea.
how about trying your luck with a service ? most of the time they do have access to special programs, which have a better functionality than adb.
Thanks for the hint, but I am not happy with the idea of someone playing with my data
1. Try reboot phone to recovery
2. Connect it to your computer (download Platform-tools)
3. In the folder with Platform-tools open cmd
4. In cmd - adb shell
5. cd storage/emulated/0
6. ls
7. Now, using the commands, drag files from your phone to your PC
Thanks for your hint.
No luck so far, I think because the phone is not in recovery mode.
I can hear the phone starting up several times (hear the jingle) so I think it's in a reboot loop and I don't know how to boot it into recovery mode wo a working display (tried with power/volume up combination with no luck).
From the windows taskbar I can see that the phone is recognized for a few seconds before it restarts.
EDIT: trying to switch the phone on with the combination "power/volume down" brings to a kind of stable state and I can now see the phone in the windows taskbar recognized as a generic "android device". Still no luck when trying to access the phone as there's no device in windows and no device obtained through "adb devices" command.
EDIT1: I think that the phone is in "FASTBOOT" mode. If I type "fastboot devices" I can see it detected but still can't access it.
Any idea? Should I give up?
If it's popping up and down you need something to keep track.
You can try my UsbLog.exe (in the sig), it just sits there and shows what devices appear (if they have a driver) and disappear.
Try these to see if anything is working:
Code:
C:\>fastboot devices
C:\>fastboot getvar all
C:\>fastboot oem device-info
Yes it's popping up and down when it's booted in recovery mode whilst is stably connected when in fastboot mode but in this case I can't access the internal memory of the device.
I didn't get the purpose of logging the devices connecting to the USB as I can see the device connected for a while and correctly recognized as Redmi Note 8 pro but as it keeps popping out windows have no time to show it's folder.
As for the code you wrote: i will try asap but already tried with "fastboot devices" and I get the phone correctly listed but still can't access its memory as told.
Renate said:
If it's popping up and down you need something to keep track.
You can try my UsbLog.exe (in the sig), it just sits there and shows what devices appear (if they have a driver) and disappear.
Try these to see if anything is working:
Code:
C:\>fastboot devices
C:\>fastboot getvar all
C:\>fastboot oem device-info
Click to expand...
Click to collapse
After rebooting the phone in fastboot mode I can see it recognized as a generic android device from windows (still can't access the storage folder of the device).
fastboot devices----> I get the device listed with a series of numbers/letters
fastboot getvar all---> I get a list of information on token/token version/partition type and size/baseband/bootloader etc.
fastboot oem device-info----> FAILED (remote: unknown command)
So I think it's clear that the device is in Fastboot mode and instead is in a boot loop when started in revocery mode.
Is there a way to extract data from fastboot mode?
Thanks,
Andrea.
If you put a custom recovery on it in the first place you can try reflashing recovery from fastboot.
Fastboot doesn't allow you to read anything.
oem device-info is obviously an oem command that might not be on any device.
You've got a Mediatek processor. That has some low level equivalent to Qualcomm EDL, but I have no experience with that.
If you can get there you can download the user data partition, but it's probably encrypted. Also no experience with that.
The easiest is if you can get the system to mount/decrypt the partition.
You've tried the normal system too?
Is this A/B? Have you tried changing slots?
How much time does it stay up in recovery? Do you have ADB? Maybe try:
Code:
# stop recovery
Does that prevent it from looping?
So I should try to flash a custom recovery like TWRP for example?
What you mean with "normal system too"?
Changing slots you mean changing usb port?
It stays in recovery less than one second so I can't give any command via ADB.
EDIT: cant' flash any custom recovery because the bootloader is locked.
If I Try to unlock the bootloader via MiUnlock I get a warning saying that all data will be erased.
Any idea on how to unlock the bootloader wo wiping all the data?
Sephiroth79 said:
So I should try to flash a custom recovery like TWRP for example?
What you mean with "normal system too"?
Changing slots you mean changing usb port?
It stays in recovery less than one second so I can't give any command via ADB.
EDIT: cant' flash any custom recovery because the bootloader is locked.
If I Try to unlock the bootloader via MiUnlock I get a warning saying that all data will be erased.
Any idea on how to unlock the bootloader wo wiping all the data?
Click to expand...
Click to collapse
There is a mediatek bootloader unlocked you just have to boot in Brom mode and it'll unlock it please follow this
PS: press all buttons
MysticNoOb said:
There is a mediatek bootloader unlocked you just have to boot in Brom mode and it'll unlock it please follow this
PS: press all buttons
Click to expand...
Click to collapse
My bootloader is unlocked!
Thank you very much.
Now I am going to try to flash a custom recovery mode via fastboot in order to access the internal memory of the phone.
EDIT: I've just flashed twrp-3.6.2_9-0-begonia.img but still can't boot into recovery mode.
Any hint on how to extract data from the system now?
You really want to boot the normal system because that's the best way to get decrypted data.
I realized that you don't have ADB enabled there.
You should look at B. Kerler's https://github.com/bkerler/mtkclient/
If you can pull the boot image off your device then I might be able to fix it so that you have ADB.
You'd have to flash it back in fastboot or mtkclient.
You can also pull a copy of userdata off the device with mtkclient.
As far as booting into recovery, there's a way.
Here's how, if you don't have A/B (that is you flashed TWRP into recovery and not recovery_a or recovery_b)
then you can fastboot flash a special file into the misc partition and it wil boot into recovery next reboot.
To return things to normal you have to flash the empty file to the misc partition.
Code:
C:\>fastboot flash misc misc-rec.img
C:\>fastboot reboot
Only do this if you don't have partitions that end in _a or _b
I really don't know if I have partitions A and B as you mentioned and I think there's no way to check actually.
I confirm I don't have "USB Debugging" active on the phone.
So if I understand correctly I should do the following:
- Flash misc-reg.img via Fastboot
- Boot into recovery just rebooting the system after flashing the above file;
- use MTKclient to dump userdata or boot image to enable ADB on (I will need help with mtkclient I suppose).
Is it correct?
EDIT: flashed TWRP first and misc-rec then rebooted via Fastboot/Reboot but nothing happens.
Sephiroth79 said:
My bootloader is unlocked!
Thank you very much.
Now I am going to try to flash a custom recovery mode via fastboot in order to access the internal memory of the phone.
EDIT: I've just flashed twrp-3.6.2_9-0-begonia.img but still can't boot into recovery mode.
Any hint on how to extract data from the system now?
Click to expand...
Click to collapse
TWRP cant boot because you used wrong one. Search again in that unlock bootloader channel and use suitable one.
Kirasu2080 said:
TWRP cant boot because you used wrong one. Search again in that unlock bootloader channel and use suitable one.
Click to expand...
Click to collapse
Hmmm, I am almost sure that the TWRP I've flashed was listed under Redmi Note 8 pro page. Can you please indicate more precisely where should I sera
EDIT: I think I've downloaded and flashed the correct TWRP file.
@Renate can you please detail your method so I can try to extract data from the phone?
Sephiroth79 said:
Hmmm, I am almost sure that the TWRP I've flashed was listed under Redmi Note 8 pro page. Can you please indicate more precisely where should I sera
EDIT: I think I've downloaded and flashed the correct TWRP file.
@Renate can you please detail your method so I can try to extract data from the phone?
Click to expand...
Click to collapse
1/Yeah it's official. You "flashed correct TWRP." Downgrade to Miui Android 9 (_9 in it's name) to boot into that TWRP and lose your data.
2/In unlock bootloader video above, search other video in his channel playlist and find TWRP video suitable for your Miui version.
Kirasu2080 said:
1/Yeah it's official. You "flashed correct TWRP." Downgrade to Miui Android 9 (_9 in it's name) to boot into that TWRP and lose your data.
2/In unlock bootloader video above, search other video in his channel playlist and find TWRP video suitable for your Miui version.
Click to expand...
Click to collapse
Can't find the right video, can you kindly send me a link (I am on the latest Miui version and I am in Europe)?
In all the videos I've seen on his page he is using the device to install TWRP etc.
I think I just need the correct TWRP version for my MIUI release and then I'll flash TWRP and misc-reg.img. Is it right?
Sephiroth79 said:
Can't find the right video, can you kindly send me a link (I am on the latest Miui version and I am in Europe)?
In all the videos I've seen on his page he is using the device to install TWRP etc.
I think I just need the correct TWRP version for my MIUI release and then I'll flash TWRP and misc-reg.img. Is it right?
Click to expand...
Click to collapse
Use brp 3.5.2 v3.1 or V3.6 to decrypt Miui 12.5

Categories

Resources