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 !
Related
Hello all,
I have Zenfone 2 on which I intended to use a custom ROM.
So the first thing was to unlock the bootloader.
On previous occasion, on my Nexus, I had used the - fastboot oem unlock - command and it had worked. So with that in mind, I booted into the bootloader and tried the command, but it failed - saying oem command unrecognized.
Then I searched online and apparently, to unlock the bootloader, Asus has launched an app! But to be able to install the app, I need to get a normal boot happening, which is not happening now.
In between all this, I tried the commands - fastboot flash recovery <recovery.img>, fastboot flash boot <boot.img> too. But none of these were successful, and each of them returned a 'Permission denied' message, probably coz the bootloader was locked.
Now the situation is that -
- Bootloader is locked.
- Phone is stuck in bootloader
- There is no recovery installed. In fact, from the bootloader, when I try to boot into 'Recovery Mode', it goes there for a second and returns back to the bootloader. Doesn't show the normal android image with a 'X' on top.
- There is no root access.
Now I think the first step is to get root access, and for this I want to try the method with installing CWM recovery and SuperSu.
But for this, I need to be able to push the SuperSu.zip to the phone, which I am not able to.
Can somebody please help!
r the drivers for fastboot & adb update to date?
Android version?
If the phone is stuck in bootloader, you can use Asus Flash Tool to flash .raw files and unbrick the phone.
Raw files: https://yadi.sk/d/FijRoAVJtvRiG
AFT: https://yadi.sk/d/NQCiY--IsQjBr (I use AsusFlashToolInstaller1.0.0.14.exe).
you can use Asus Flash Tool to flash .raw files and unbrick the phone.
Click to expand...
Click to collapse
Have to choose wipe the data or not?
hafiz019 said:
Have to choose wipe the data or not?
Click to expand...
Click to collapse
stay away from aft. if will f**k up yor device completely. AFT is too unstable. lot of times it bricks the device to unrecoverable state. tell me the bootloader version, ifwi version shown on screen while in bootloader mode.
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)
I unlocked bootloader of my phone, flashed TWRP then installed new ROM and then tried to boot bt the only thing I get on my screen is "the current image(boot/recovery) have been destroyed and cannot boot"
This screen repeats and I cn't do anything, not able to find any good tool or something to flash stock rom again...Please help am alrady dead
Dude, you just should flashing original/stock boot.img and recovery.img. And your phone already fixed.
Jus flash vbmeta and than flash twrp again . It will work fine and you won't get erro
Flash vbmeta
where did you got the file?
I have the same problem. Also cant flash vbmeta because the phone cant go into fastboot/recovery mode. It seems the only option is to flash it in edl mode and haven't found a tool that can do that
orl4nd said:
where did you got the file?
Click to expand...
Click to collapse
I found one in the pixel rom thread, it worked fine for me when i had this issue flashing candy rom
Ragzone said:
I have the same problem. Also cant flash vbmeta because the phone cant go into fastboot/recovery mode. It seems the only option is to flash it in edl mode and haven't found a tool that can do that
Click to expand...
Click to collapse
You have to flash the boot.img via adb to boot into Fastboot or Recovery.
Stuck at same problem.
I am also facing same problem. I can't open fastboot and the phone reboots to stock recovery after some time. Please help.
same problem for me
Ragzone said:
I have the same problem. Also cant flash vbmeta because the phone cant go into fastboot/recovery mode. It seems the only option is to flash it in edl mode and haven't found a tool that can do that
Click to expand...
Click to collapse
i have the same problem exactly. no access to adb commands nor recovery. please let me know if you could find a solution.
reza14 said:
i have the same problem exactly. no access to adb commands nor recovery. please let me know if you could find a solution.
Click to expand...
Click to collapse
I will keep trying the different flashing tools. Also let me know if you are succesful.
RMX1901CH unbirick
RMX1901CH
I was in the same state but unbirick.
When the power is off Press the volume minus and the power simultaneously.
If you are in fastboot mode
1.adb flashing command // fastboot flash recovery twrp-3.3.1-24- RMX1901-mauronofrio.img
2. after starting TWRP - connected with otg usb memory (StockROM.ozip)
3. USBOTG to mount
4.wipe dalvik / ARTCache & cache & system & data
* 5. INSTALL StockROM
* RMX1901_11_OTA_0190_all_fSt4F56aQlqf.ozip (China) A19
I haven't tried with older versions
The international version will show an inappropriate error, and it may be possible with the same language model
* 6. reboot
Japanese who cannot speak English
I did this way
Is this problem Solve? i face the same problem. what can i do?
Hatzey said:
I unlocked bootloader of my phone, flashed TWRP then installed new ROM and then tried to boot bt the only thing I get on my screen is "the current image(boot/recovery) have been destroyed and cannot boot"
This screen repeats and I cn't do anything, not able to find any good tool or something to flash stock rom again...Please help am alrady dead
Click to expand...
Click to collapse
Please help me.
same issue , can't do anything
the only way I found is , to know this user and pass in this tool so that I could test the firmware and post this here
Такая же проблема, помогите!!!
Long press volume down and power button , the phone will boot into fastboot mode. Flash vbmeta with disable verity command . It worked for me. No need do anything else.
volume down and power button for 10 sec
then flash stock recovery
then wipe data from stock rocovery
then back to bootloader and flash twrp recovery
then transfer stock rom zip on device
install it
done
Man i have the same problem, did you find any solution?
I already downloaded the qualcomm flash image loader, the pc detects the phone only when i press volume + and volume - and connect it, so i know i can do something, im gonna try with the EDL mode, any advance i'll let you know
how to do Flash vbmeta with disable verity command ???
Bricked with a locked bootloader - "This MIUI version can't be installed on this device"
I can get to "adb sideload" and fastboot, but the bootloader is locked
Can I unlock the bootloader with EDL? Can I access EDL with an EDL-cable? Or do I need to open the phone and short the EDL pins?
Can I recover the phone from a Linux computer? Or do I need Windoze?
Is it even possible to un-screw this phone?
Any help appreciated.
go vegan said:
Bricked with a locked bootloader - "This MIUI version can't be installed on this device"
I can get to "adb sideload" and fastboot, but the bootloader is locked
Can I unlock the bootloader with EDL? Can I access EDL with an EDL-cable? Or do I need to open the phone and short the EDL pins?
Can I recover the phone from a Linux computer? Or do I need Windoze?
Is it even possible to un-screw this phone?
Any help appreciated.
Click to expand...
Click to collapse
how did you do this?
Redmi 4A abdal said:
how did you do this?
Click to expand...
Click to collapse
1- Checking if this problem is still a problem with custom ROMs; it is, and thus I believe it to be a hardware fault.
2- Done testing, re-install stock stock ROM, lock bootloader via adb; bricked phone.
go vegan said:
1- Checking if this problem is still a problem with custom ROMs; it is, and thus I believe it to be a hardware fault.
2- Done testing, re-install stock stock ROM, lock bootloader via adb; bricked phone.
Click to expand...
Click to collapse
ok, you can run edl mode but its no good for you, its already locked by xiaomi, ( go ing to fastboot mode and give commands something like this " fastboot boot edl")
* do you see padlock lock sign when you go to fastboot mode
* try to flash vbmeta in fastboot mode
* try again to flash correct version miui fastboot rom with mi flashing tool with out selecting lock bootloader
I can get to fastboot by holding power+vol-down. There's no lock icon.
On Ubuntu, I don't think fastboot is compiled to support rebooting into edl. I tried editing the source, and I'm not sure if I did it right, but the binary I built did not boot the phone into edl.
Using these commands:
Code:
fastboot flash vbmeta /tmp/platform-tools/vbmeta.img
Code:
fastboot --disable-verity flash vbmeta /tmp/platform-tools/vbmeta.img
Code:
fastboot --disable-verity --disable-verification flash vbmeta /tmp/platform-tools/vbmeta.img
They all give the same result:
Code:
target reported max download size of 804274176 bytes
sending 'vbmeta' (4 KB)...
OKAY [ 0.006s]
writing 'vbmeta'...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: 0.007s
go vegan said:
I can get to fastboot by holding power+vol-down. There's no lock icon.
On Ubuntu, I don't think fastboot is compiled to support rebooting into edl. I tried editing the source, and I'm not sure if I did it right, but the binary I built did not boot the phone into edl.
Using these commands:
Code:
fastboot flash vbmeta /tmp/platform-tools/vbmeta.img
Code:
fastboot --disable-verity flash vbmeta /tmp/platform-tools/vbmeta.img
Code:
fastboot --disable-verity --disable-verification flash vbmeta /tmp/platform-tools/vbmeta.img
They all give the same result:
Code:
target reported max download size of 804274176 bytes
sending 'vbmeta' (4 KB)...
OKAY [ 0.006s]
writing 'vbmeta'...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: 0.007s
Click to expand...
Click to collapse
Try to unlock bootloader using cmd and then vbmeta
T.Y.M.SAI said:
Try to unlock bootloader using cmd and then vbmeta
Click to expand...
Click to collapse
I'm not sure what that means.
go vegan said:
I'm not sure what that means.
Click to expand...
Click to collapse
There are 2 ways to unlock bootloader
1. Official way using Mi flash tool
2. Unofficial way using cmd
There are lots of videos on how to unlock bootloader using cmd go and try them
Most important is to keep your phone charged
T.Y.M.SAI said:
1. Official way using Mi flash tool
2. Unofficial way using cmd
Click to expand...
Click to collapse
1- That requires access to a working phone.
2- All I'm finding is instructions for how to type "fastboot oem unlock" on a Windoze computer.
go vegan said:
1- That requires access to a working phone.
2- All I'm finding is instructions for how to type "fastboot oem unlock" on a Windoze computer.
Click to expand...
Click to collapse
Did you found a way to fix the phone or unlock bootloader?
You have 2 ways to get out of this situation.
1. Try to unlock the bootloader with the Mi account you used last time.
2. If couldn't unlock, then switch to EDL mode. Use a no auth programmer to flash the correct variant fastboot ROM and the device should boots up. Then add account again and wait for 168 hours for unlocking.
Since we've got no auth programmer for Sm6125 we could use EDL mode freely.
Hi there @go vegan , have you already fix your phone again? because i also got the same situation on my redmi 6. or is there anybody who can help? thanks
Hi all add me to the list with a k20pro.
The device was unlocked at the start, i got MIUI 12.5 global and flashed with miflashtool.
but wipe and lock was active.
now the phone comes up to the recovery menu and says the miui version is not for this device.
When I try to flash to another version, miflashtool says the device is locked,
when I try to unlock while using the account the device is registered in, miunlock says go to settings >developer options> mi unlock status.
Gave it to a repair shop for 1.5 months and nothing. I live in Iran so no authorized service centers here.
I have access to fast boot mode and recovery.
I tried xiaomitoll V2 which had a specific question asking if my device would show This MIUI version can't be installed on this device in phone is bricked option. It goes to get china official Rom but then errors.
I'm a noob here so any help would be great, tnx.
I have encountered the same problem a few hours ago with my beloved Redmi K20 Pro. My heart became gloomy thinking that I have no way left other than having to take to an authorized service centre where they will rip off the back cover. But then I stumbled upon this simple solution that took me a minute or two. This is how I solved it:
Entered the fastboot mode
Connected the phone to my laptop using the USB cable
Opened the official Mi Unlock Tool and logged in with my Mi account, and
Clicked on the beautiful UNLOCK button!
Boom! The phone is back to its vibrant life! I'm just happy again!
when I try to unlock while using the account the device is registered in, miunlock says go to settings >developer options> mi unlock status.
TECHtacian said:
I have encountered the same problem a few hours ago with my beloved Redmi K20 Pro. My heart became gloomy thinking that I have no way left other than having to take to an authorized service centre where they will rip off the back cover. But then I stumbled upon this simple solution that took me a minute or two. This is how I solved it:
Entered the fastboot mode
Connected the phone to my laptop using the USB cable
Opened the official Mi Unlock Tool and logged in with my Mi account, and
Clicked on the beautiful UNLOCK button!
Boom! The phone is back to its vibrant life! I'm just happy again!
Click to expand...
Click to collapse
Hi! Where can I download Mi Unlock Tool?
UnDevelopedDeveloper21 said:
Hi! Where can I download Mi Unlock Tool?
Click to expand...
Click to collapse
Apply for permissions to unlock Mi devices
en.miui.com
The solution to the problem is simple.
into fast boot mode,
Run unlock again!! Obviously it's locked. When unlocking is executed,
the same screen may appear again. Please do a reboot. You will definitely see the MIUI installation screen.
Device: Redmi note 7S
I found a solution and it worked for me:
1.Download the bat file and execute in your windows pc : https://drive.google.com/file/d/1NqPotx06yRuhPsOdEAdS4JNsk7qWWchF/view
2. After that use the MI unlocker tool to unlock the device.
3, Use mi flasher to flash the Rom.
After the hours of research in the internet i found the solution.
Thanks
Shiva5558 said:
Device: Redmi note 7S
I found a solution and it worked for me:
1.Download the bat file and execute in your windows pc : https://drive.google.com/file/d/1NqPotx06yRuhPsOdEAdS4JNsk7qWWchF/view
2. After that use the MI unlocker tool to unlock the device.
3, Use mi flasher to flash the Rom.
After the hours of research in the internet i found the solution.
Thanks
Click to expand...
Click to collapse
What do you mean by "execute in your windows pc"? Sorry for asking
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