Hey,
i have a Moto G5(cedric , xt1677) .
i had recently flashed stock rom (CEDRIC_RETAIL_8.1.0_OPPS28.85-16-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml) using RSD LITE tool.
When i tried booting( volume down +power ) into recovery it wont boot and it would be looping the bootloader( the bootloader comes and goes then repeat). I tried quickly pressing start to boot the device but it wont boot and keeps restarting the bootloader page. So i removed the battery and tried pressing the power button only it booted the system successfully.
i tried usb debugging there was no notification and adb didn't detect it. (it was already on in dev options).
then i used magisk manager(it was already installed and i was getting root access) to boot into recovery. The device
booted into twrp recovery and i wiped the data and formatted the system and data partition.
then i tried booting into fastboot mode using twrp reboot>bootloader.
The bootloader kept looping(coming and going).
NOW i have NO OS TO BOOT INTO and I'm getting this bootloader loop.
Things I noted:
1. The oem unlcoking option was off when i boot the device.
And i turned it on.Still bootloader keeps looping.
2. NO MTP when device was in the os .
3. no usb debugging notification.
4.no detection by adb devices and fastboot devices.
Please help me!!!!!!!!
Don't use rsd lite - this is not the correct way to flash firmware on this device
All you need is the firmware & fastboot commands
Things that could try
Is the phone actually staying in fastboot mode & it's just the screen that is turning on & off?
fastboot devices
The above command will list connected devices - keep typing it in a command prompt when the screen is off to see if its still connected
If detected try flashing the entire firmware via fastboot including gpt & bootloader (firmware must be the same or newer than what you have on the device already)
You can also use the hard brick solution to boot the bootloader off an sd card
You can then flash gpt & bootloader via fastboot
https://forum.xda-developers.com/g5/how-to/rooted-moto-g5-run-morning-post-image-t3776012
TheFixItMan said:
Don't use rsd lite - this is not the correct way to flash firmware on this device
All you need is the firmware & fastboot commands
Things that could try
Is the phone actually staying in fastboot mode & it's just the screen that is turning on & off?
fastboot devices
The above command will list connected devices - keep typing it in a command prompt when the screen is off to see if its still connected
If detected try flashing the entire firmware via fastboot including gpt & bootloader (firmware must be the same or newer than what you have on the device already)
You can also use the hard brick solution to boot the bootloader off an sd card
You can then flash gpt & bootloader via fastboot
https://forum.xda-developers.com/g5/how-to/rooted-moto-g5-run-morning-post-image-t3776012
Click to expand...
Click to collapse
I tried several times.
fastboot devices command is not detecting my device.
My device is not in fastboot mode also.
It's just looping the bootloader and is not booting up due to the absence of an OS.
Can u tell me how to load bootloader through sd card?
well i tried writing the sd card with twrp.img using diskimagerev2 still nothing.
i tried writng the sd card with bootloader.img from firmware. nothing happened still looping .
If it could somehow enter twrp i cud just chamge the bootloader with the img file from firmware. Won't that work? Wouldn't it fix that looping?
i know that twrp is present in my device.But the method to access it is not working.
Vol down+ power - bootloader looping
adb fastboot- not detecting.
Any solutions?
EMZThe said:
I tried several times.
fastboot devices command is not detecting my device.
My device is not in fastboot mode also.
It's just looping the bootloader and is not booting up due to the absence of an OS.
Can u tell me how to load bootloader through sd card?
well i tried writing the sd card with twrp.img using diskimagerev2 still nothing.
i tried writng the sd card with bootloader.img from firmware. nothing happened still looping .
If it could somehow enter twrp i cud just chamge the bootloader with the img file from firmware. Won't that work? Wouldn't it fix that looping?
i know that twrp is present in my device.But the method to access it is not working.
Vol down+ power - bootloader looping
adb fastboot- not detecting.
Any solutions?
Click to expand...
Click to collapse
I gave you the link to the guide on how to write the sd card - please read it
Also twrp can only flash kernel or recovery images
Firmware must be flashed via fastboot
TheFixItMan said:
I gave you the link to the guide on how to write the sd card - please read it
Also twrp can only flash kernel or recovery images
Firmware must be flashed via fastboot
Click to expand...
Click to collapse
Hey, my phone had fell into water before i had the bootloader loop. The service centre told me to change the motherboard (lol) for 5000Rupees ( around 72$) . The are some shorts in the board. BTW the phone will boot if there is a firmware installed . The bootloader loop is the problem. Now should i try the mmcblk0.img method??
EMZThe said:
Hey, my phone had fell into water before i had the bootloader loop. The service centre told me to change the motherboard (lol) for 5000Rupees ( around 72$) . The are some shorts in the board. BTW the phone will boot if there is a firmware installed . The bootloader loop is the problem. Now should i try the mmcblk0.img method??
Click to expand...
Click to collapse
If you have dropped your phone into water the chances are it's water damaged
Stick it in a bowl of rice and put it in a hot cupboard for a few days
I doubt anything else will work - you may have to replace the motherboard due to water damage
TheFixItMan said:
If you have dropped your phone into water the chances are it's water damaged
Stick it in a bowl of rice and put it in a hot cupboard for a few days
I doubt anything else will work - you may have to replace the motherboard due to water damage
Click to expand...
Click to collapse
I had gone to the repair shop and then cleaned and heated the board to remove moisture. Still that bootloader loops.
So i guess it's a hardware issue. :crying:
EMZThe said:
I had gone to the repair shop and then cleaned and heated the board to remove moisture. Still that bootloader loops.
So i guess it's a hardware issue. :crying:
Click to expand...
Click to collapse
Never heat a phone that's water damaged - you will draw the water up through more components and cause more damage
Stick it a bowl of rice and an airing cupboard for a few days
Chances are you may need a motherboard replacement or just buy a new phone as other components may also be damaged
Hey there ,
I had gone to the service centre and they said the problem is with the board for which they asked for RS 5000 (around $70-75$).
Now I bought a new mi a2 .
Thanks you.
Related
Hey Folks,
Ran a bit of trouble with my new Zenfone 2 , got it just a couple of days ago and a system update seems to have messed up. The phone froze half way through the update process and I had to turn it off (ran out of patience) and when I booted it up it just loads up to the ASUS logo and stays there for eternity.
I was not able to get to the Recovery mode, had a war with the dead android guy with the red triangle, ( holding power and volume up didn't help). I did however manage to get the device recognized on the Platform tools command like when I connected to my PC. I tried the ADB reboot command, ADB reboot recovery, and they didnt help. I did manage to work a couple of fastboot commands, fastboot erase data and fastboot erase cache BUT, looks like that's got me into deeper trouble.
Ever since I did that, I cannot manually go into the recovery mode anymore using the power and volume keys. I get a white USB logo and something that looks like a battery status bar below it. No combination of keys seem to help.
To make it worse, my device is not recognized on my PC anymore, ADB devices command doesn't list it, and neither does fastboot devices. I did however notice that now on my device manager, the phone shows up as a 'ortable Device - MTP USB Device'. No ammount of uninstalling and re-installing various kinds of ADB and USB drivers seem to help.
I did see a few blogs that give a fix for the same issue on a zenfone 5, but being a noob (hate to admit it) at this, I dont wanna risk it unless I'm sure it will help.
Can anyone help me out on this please? Any kind of help would be much appreciated
Download the Lastest firmware from here
https://www.asus.com/support/Download/39/1/0/13/Lk0Sg1Ulh0Ph49Hl/32/
If you WW then download.
keep the zip file in SD card and rename it as MOFD_SDUPDATE.zip
Now go to bootloader and then recovery mode. it will automatically apply update. update may take time 10~20 mins
From your description you probably need to read this thread
http://forum.xda-developers.com/showthread.php?t=3162848
Sorry it's not good news
Sent from my ASUS_Z00AD using Tapatalk
It's showing error (status 7) . Help Me !!
stuck on usb logo
please help me my asus zenfone 2 z008d got the same problem from yesterday . its stuck on usb logo
Search xFSTK for repair/temporary fastboot, do the tutorial. Then goto recovery if still can. If recovery missing try to fastboot recovery. If failed then u must use Asus Flashtool to flash raw image. After that retry to flash droidboot, recovery, boot. Reboot to fastbootand go to recovery, then choose adb. Run adb sideload to flash full firmware.zip
I become an expert at unbricking hehe 
Stuck on USB logo...
Turn your phone off...
Start downloader ..flashing ifwi and fwr dnx and os image..connect phone.
Try flash os image on its own repeatedly ...ignore errors just keep doing it .
Then after 10 goes at it ..flash ifwi and dnx with it repeatedly till success.
Note that when it succeeds ..
Stop! and pause, keep an eye on your screen of phone..you see it flash , might take 5 mins before you see this start ..but when its finished ..you flash raw in flash tool after and it will reboot straight into system all by itself 
Me have been guilty of flashing raw before the flash of downloader...and a bet many others have too.
Ps select, wipe data in flash tool too.
i did update using the new firmware as u told by renaming the file to MOFD_SDUPDATE.zip
but after that my imei changed to 0049100491.....
then i formated whole using miracle box
now its stuck on asus logo and can't update now
hang on logo
please help
ritupaul91 said:
i did update using the new firmware as u told by renaming the file to MOFD_SDUPDATE.zip
but after that my imei changed to 0049100491.....
then i formated whole using miracle box
now its stuck on asus logo and can't update now
hang on logo
please help
Click to expand...
Click to collapse
You may want to reflash your phone using RAW firmware.
Sent from my ASUS_Z00A using XDA Labs
My Honor 7x (BND-L21) is totally bricked for the moment. I think there is Nougat and Oreo partitions at the same time because of Huawei Multi-Tool. Now I can't boot into recovery/eRecovery and the device stucks in the splash screen (bootloader unlocked). I think I have to rewrite all the partitions but I don't know how to do it... If anybody has a solution it will be greatly appreciated, I tried for 1 week!
If your device has a locked bootloader or frp follow these steps
First of charge your device for 1 hour in whatever mode it is..
https://www.androidfilehost.com/?fid=11050483647474828964
Then download the service rom from the above link
Extract the contents of the downloaded file. Copy the dload folder from the extracted files to a sdcard.. (Directly to it not on any directory)
Insert the sd card..
Press all the buttons until the emui logo comes.
After the flashing reaches 100 percent.. Reboot the device unlock the oem in developer option..
Step-2 (Computer)
Download adb drivers and fastboot and install them.
Download complete ota package for your device (make sure you have the correct build number because service rom has a different build number ) (download size will be above 2gb)
Extract all downloaded zip files. Then using huawei firmware extractor extract all contents of the update. app files.. (one update. App file in each zip files)
Copy
kernel. Img
Ramdisk. Img
System. Img
Cust. Img
Version. Img
Vendor. Img
And version. Img to the folder having adb files. And version and vendor files to sd card
//Make sure that the complete ota package you downloaded matches the os before the software brick(noughat or oreo) //
Open the adb folder and do shift plus right click to open command window there and connect your device in fastboot mode to pc
Use the below commands one by one each after completion
Fastboot devices(show your device if its connected)
Fastboot oem unlock (code obtained from huawei unlock page)
#factory rest occur
After tha enter fastboot mode again
Step-3
Fastboot flash ramdisk ramdisk.img
Fastboot flash recovery_ramdisk recovery_ramdisk. Img
Fastboot flash system system. Img
Fastboot flash cust cust.img
Flash twrp using
Fastboot flash recovery_ramdisk twrp. img
Boot your device to recovery mode.( Volume up plus power)
Flash version. Img to version partition and vendor. Img to vendor partition
If you want stock recovery back
Boot into fastboot mode
Enter the command
fastboot flash recovery_ramdisk recovery_ramdisk. Img
And do a reboot
Relock bootloader upto your wish..
Better keep oem unlocked in developer options
If you have both unlocked bootloader and frp follow from step 2
I heard huawei discontinued the unlock page
In that case use dc unlocker to find the code
It will cost some money
All credits to @mrmazak
Thank you I will try this but the dload method didn't worked when I tried 4 days ago...
I can't go into dload update mode (when I hold all the physical buttons the phone restarts and this appears (picture 1) and got stuck on this screen).
Also I don't know why but the phone doesn't charge, when I unplug it after 1h of charge, it shows the critical battery screen (picture 2) and it goes off...
Any help is reaaly appreciated!
Any other ideas?
gabrce said:
Any other ideas?
Click to expand...
Click to collapse
Though situation, if not charging. Bit to verify, try different cable and charging brick to make sure.
I changed twice the cable and nothing change...
Is there a method to factory reset the device in fastboot mode?
Maybe I should try HWOTA8?
gabrce said:
Maybe I should try HWOTA8?
Click to expand...
Click to collapse
Will need to de able to boot twrp for hwota to work.
So what should I do? Is there a method to flash twrp without fail? Because I can't boot into it...
gabrce said:
So what should I do? Is there a method to flash twrp without fail? Because I can't boot into it...
Click to expand...
Click to collapse
If battery is not charging, then it will not take a flash.
You can maybe try remove back cover and unplug battery, then reconnect see if it will take a charge.
As for your question about resetting with fastboot. You can wipe data, and maybe format system also. But I don't think that will help you.
My friend is asking help. His situation is similar. The phone is honor 6x.
My opinion is that something wrong with boot partition. you can ask some body extract the boot image from another phone. Then run "fastboot flash boot_ramdisk boot.img".
Hope it helps
Thank you for your answer.
This command didn’t work.
My phone got stuck for one month now...I’m desesperate...
gabrce said:
Thank you for your answer.
This command didn’t work.
My phone got stuck for one month now...I’m desesperate...
Click to expand...
Click to collapse
I try to help again.
Describe problem please
As I recall it is as follows
** Phone working,
** Attempts some backup or restore using multi-tool
** This made phone no longer boot
**Possible that nougat images flashes to Oreo partition tanle (or visa- versa)
**Now no recovery or erecovery will even boot.
**Also phone shuts off with low battery as soon as cable unplugged.
If this is the case, I see no way forward. Because the battery needs to hold something in order for flashing to complete
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 !
Hello,
I searched for this problem but i dont see any posts that is related to this. So i got my deluxe, its ZS750kl 2.15 6gb ram unit with nougat OS and it was working well. Last february 2018, it got its automatic system update for Taiwan CHT VoLTE support and battery optimization. A day after the update, it suddenly went into bootloop. My unit is not rooted, running with stock nougat OS with locked bootloader. It was never modified in any form. I do some observations and i noticed that sometimes it boots normally so i successfully done a factory reset but the same problem existed. I cant do a hard reset via vol. down+power since i have a locked bootloader. I am new with fastboot method and i dont know if it will help me solve the problem so i left it untouched from March until this week. Same problem still exist even the battery is totally drained over time.
Is there someone here with the same problem? Is there a possibility of system rollback before the february update?can i flash nougat stock rom hoping it will revert back to the previous OS without VoLTE support? I think the bootloop issue is with that update, since i saw some posts with the same problem but it was after the oreo update, not the same as mine so i concluded that the problem lies somewhere in between the feb. update and the oreo update.
I hope some will look into this and help me or guide me to step by step flashing of nougat stockrom using fastboot. Sorry, im new with the method, i usually flash through twrp but i cant because of locked bootloader.
Thank you in advance,hope you can help me with my problem.
Model: ZS750KL
Ram: 6gb
Frequency: 2.15
Firmware: WW_5.17.44.87_20180222
Location: Philippines
Hi there,
I hope I can post this here.
I don't have an answer but I have a similar problem. The Phone will not start anymore. I ran into bootloop and only fastboot is working.
Any thing i can do?
Hello,
Im looking for a solution too, my phone got bootloop only fastboot is working, partition protected, phone is locked i cannot put even in recovery mode. Any help would be really appricated.
Cheers.
Hey all,
These instructions are assuming you have a 2.15ghz 570KL. I'm not responsible if your phone gets bricked any further.
Grab the standalone adb/fastboot tools
https://developer.android.com/studio/releases/platform-tools
Grab recovery.img from 15.0210.1808.70, grab twrp-3.2.3-0-Z016-20181014.img
https://mega.nz/#F!EkFF1CJD!C8o2wXMARW3YJFOipDttbA
Grab the latest official update, make sure it's the right frequency (2.15ghz in this case)
https://www.asus.com/us/Phone/ZenFone-3-Deluxe-ZS570KL/HelpDesk_Download/
Move everything into an accessible folder
Copy the internals of the adb/fastboot such that twrp-3.2.3-0-Z016-20181014.img and fastboot.exe are in the same folder
Copy recovery.img to an sd card
Copy the official update to the same sd card
Put it in the phone
Open command prompt
Navigate to the folder using cd [filepath]
Example:
cd c:/users/MyUser/Desktop/Folder
run the following command
fastboot boot twrp-3.2.3-0-Z016-20181014.img
Boot phone to fastboot mode
Plug it in and pray.
It should boot into TWRP. Go to install, click the checkmark to switch from zip to images, then find Recovery.img. It should be located in the external_sd. Flash that to the recovery partition.
Reboot back into recovery (Power+Vol Down)
If it boots into a screen that says No Command! it means it was flashed successfully
Spam volume up, volume down, and power until the screen recovery loads
If it doesn't load after a few presses, do a hard reset (Power + Vol Down)
Try again until it works
Install the official update
Reboot and your phone should work again.
Good luck.
asianflipboy said:
Hey all,
These instructions are assuming you have a 2.15ghz 570KL. I'm not responsible if your phone gets bricked any further.
Move everything into an accessible folder
Copy the internals of the adb/fastboot such that twrp-3.2.3-0-Z016-20181014.img and fastboot.exe are in the same folder
Copy recovery.img to an sd card
Copy the official update to the same sd card
Put it in the phone
Open command prompt
Navigate to the folder using cd [filepath]
Example:
cd c:/users/MyUser/Desktop/Folder
run the following command
fastboot boot twrp-3.2.3-0-Z016-20181014.img
Boot phone to fastboot mode
Plug it in and pray.
It should boot into TWRP. Go to install, click the checkmark to switch from zip to images, then find Recovery.img. It should be located in the external_sd. Flash that to the recovery partition.
Reboot back into recovery (Power+Vol Down)
If it boots into a screen that says No Command! it means it was flashed successfully
Spam volume up, volume down, and power until the screen recovery loads
If it doesn't load after a few presses, do a hard reset (Power + Vol Down)
Try again until it works
Install the official update
Reboot and your phone should work again.
Good luck.
Click to expand...
Click to collapse
Hello There,
Thank you for tut*, do you have or know any method about i have exact same phone model but its stuck on boot and keep restarting, no recovery mode available only i can put in fastboot mode when i try to flash or anything it said partition protected... any help would be really appricated.
Cheers.
same problem, I have also opened a new thread but I have not received a reply.
In all cases following this mini-guide I am stopped at the boot twrp command. I'm getting unsigned file error.
I tried the original recovery (taken from the user link above) and the phone gets stuck on the android logo with a red triangle of danger.
ideas?
How did you unlock your bootloader? i cant follow the instructions given because my bootloader is not yet unlocked.
has anyone gotten the steps above to work without unlocking the bootloader?
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