Related
i tryed to root my phone everything was going alright, but wen i went to boot it up i got stuck on
ASUS IN SEARCH OF INCREDIBLE and a loading logo, i can not get in to my bootloader
my pc detects it but fast boot and adb do not detect it
what do i do :crying::crying::crying::crying:
FluidArc said:
i tryed to root my phone everything was going alright, but wen i went to boot it up i got stuck on
ASUS IN SEARCH OF INCREDIBLE and a loading logo, i can not get in to my bootloader
my pc detects it but fast boot and adb do not detect it
what do i do :crying::crying::crying::crying:
Click to expand...
Click to collapse
Probably you soft bricked your phone. I got into a similar situation when I applied OTA after root. Dont worry, its very easy to recover your phone. It should be able to boot in Fasboot mode. If it does, follow follow this guide:
.theandroidsoul.com/how-to-unbrick-asus-zenfone-2-works-on-ota-fail-too-82039/ (Add www at the start)
Download the latest pre-rooted system .img from here:
mega.co.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw
Download the stuff needed and then just follow the guide. Hopefully you recover your device. Best of luck!
EDIT: Forgot to add but did you install the adb drivers? Probably thats the reason Fastboot and adb dont detect it. Or did you go into the fastboot mode in the phone? If not, do that first. To do it, follow these steps:
1. Power your device down.
2. Press and hold the power and volume up button.
3. Release the power button when it vibrates.
4. Release the volume up button once the ASUS splashscreen appears.
5. Now the device should be in Fasboot mode.
6. Then connect your phone to your PC (dont forget to install the drivers!) using the USB Cable and go to the folder where the flashtools are.
7. Hold Shift and right click > then click open command window here
8. Type "fastboot devices". Enter the command two times. (Cause the first time it will start daemon or something like that)
If your device shows up, congrats! You are in fastboot mode and it is working.
now what do i do
i do not know what ferwere i am on and my recovery is broken how to i get it up and runing
dh_711 said:
Probably you soft bricked your phone. I got into a similar situation when I applied OTA after root. Dont worry, its very easy to recover your phone. It should be able to boot in Fasboot mode. If it does, follow follow this guide:
.theandroidsoul.com/how-to-unbrick-asus-zenfone-2-works-on-ota-fail-too-82039/ (Add www at the start)
Download the latest pre-rooted system .img from here:
mega.co.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw
Download the stuff needed and then just follow the guide. Hopefully you recover your device. Best of luck!
EDIT: Forgot to add but did you install the adb drivers? Probably thats the reason Fastboot and adb dont detect it. Or did you go into the fastboot mode in the phone? If not, do that first. To do it, follow these steps:
1. Power your device down.
2. Press and hold the power and volume up button.
3. Release the power button when it vibrates.
4. Release the volume up button once the ASUS splashscreen appears.
5. Now the device should be in Fasboot mode.
6. Then connect your phone to your PC (dont forget to install the drivers!) using the USB Cable and go to the folder where the flashtools are.
7. Hold Shift and right click > then click open command window here
8. Type "fastboot devices". Enter the command two times. (Cause the first time it will start daemon or something like that)
If your device shows up, congrats! You are in fastboot mode and it is working.
Click to expand...
Click to collapse
Once happened to my zf2, what i did is formatting cache from the adb then my device could be detected, thus i could enter the recovery mode
Sent from my ASUS_Z00AD using XDA Free mobile app
i can not enter recovery
dawnsleeper said:
Once happened to my zf2, what i did is formatting cache from the adb then my device could be detected, thus i could enter the recovery mode
Sent from my ASUS_Z00AD using XDA Free mobile app
Click to expand...
Click to collapse
it is fix all good guys thx
FluidArc said:
i can not enter recovery
Click to expand...
Click to collapse
Hey,
Could you please help me (or anyone for that matter).....I've soft bricked my phone and I'm a little weary about following any other steps incase I fully brick the phone.
I have a Zenfone 2 that was CN Z00A 2.20.40.63 , I tried to root because random chinese apps kept downloading on my phone and obv it soft bricked (kept looping at boot).....since then I have tried a lot of stuff without luck and my brain is fried from all the information.... I went to the recovery mode but ADP couldn't find my phone and then I loaded a recovery image on my SD calling it MOFD_SD.ZIP but that didn't work due to signature verification error. Now after reading what you wrote I can see that fastboot is recognizing my device....I would go through with the process but I'm afraid if I screw this one up it could be the end of fastboot working and therefore me being royally screwed.
Since my phone was naturally CN Z00A 2.20.40.63 I'm wondering if the pre-rooted images on the site you mentioned above will work? There is no download for CN Z00A 2.20.40.63 and I want to know whether it's safe to use CN Z00A 2.20.40.61 (or a WW image) or whether I have to try another option (if you have any suggestions).
If anyone could reply with help it would be greatly greatly appreciated.
dh_711 said:
Probably you soft bricked your phone. I got into a similar situation when I applied OTA after root. Dont worry, its very easy to recover your phone. It should be able to boot in Fasboot mode. If it does, follow follow this guide:
.theandroidsoul.com/how-to-unbrick-asus-zenfone-2-works-on-ota-fail-too-82039/ (Add www at the start)
Download the latest pre-rooted system .img from here:
mega.co.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw
Download the stuff needed and then just follow the guide. Hopefully you recover your device. Best of luck!
EDIT: Forgot to add but did you install the adb drivers? Probably thats the reason Fastboot and adb dont detect it. Or did you go into the fastboot mode in the phone? If not, do that first. To do it, follow these steps:
1. Power your device down.
2. Press and hold the power and volume up button.
3. Release the power button when it vibrates.
4. Release the volume up button once the ASUS splashscreen appears.
5. Now the device should be in Fasboot mode.
6. Then connect your phone to your PC (dont forget to install the drivers!) using the USB Cable and go to the folder where the flashtools are.
7. Hold Shift and right click > then click open command window here
8. Type "fastboot devices". Enter the command two times. (Cause the first time it will start daemon or something like that)
If your device shows up, congrats! You are in fastboot mode and it is working.
Click to expand...
Click to collapse
Captain_Hindsight said:
Hey,
Could you please help me (or anyone for that matter).....I've soft bricked my phone and I'm a little weary about following any other steps incase I fully brick the phone.
I have a Zenfone 2 that was CN Z00A 2.20.40.63 , I tried to root because random chinese apps kept downloading on my phone and obv it soft bricked (kept looping at boot).....since then I have tried a lot of stuff without luck and my brain is fried from all the information.... I went to the recovery mode but ADP couldn't find my phone and then I loaded a recovery image on my SD calling it MOFD_SD.ZIP but that didn't work due to signature verification error. Now after reading what you wrote I can see that fastboot is recognizing my device....I would go through with the process but I'm afraid if I screw this one up it could be the end of fastboot working and therefore me being royally screwed.
Since my phone was naturally CN Z00A 2.20.40.63 I'm wondering if the pre-rooted images on the site you mentioned above will work? There is no download for CN Z00A 2.20.40.63 and I want to know whether it's safe to use CN Z00A 2.20.40.61 (or a WW image) or whether I have to try another option (if you have any suggestions).
If anyone could reply with help it would be greatly greatly appreciated.
Click to expand...
Click to collapse
Well, I'm not sure if it'll work but check this out (Scroll down to No. 4 - Changing from CN to WW version):
forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
I'm no expert, but to be honest the state your device is in, I don't see any other options. Because when my device (it had WW firmware) got soft-bricked, I followed the guide by androidsoul and it did recover my phone. Not sure about yours since its a CN one.
If you like living on the edge and are really desperate, go ahead try this out, if not, better wait for someone with more knowledge then me.
EDIT: I forgot but since ADB isn't working, you can't use this method. So the only option I see that you have is flashing a pre-rooted rom.
A BIG SORRY for a long post. But I am sure its worth reading step by step. Because many peoples are stucked in same situation, no straight forward solution for this issue is available till now. All solutions are based on 50/50 success ratio.
I think if my issue is resolved then it can become WORLD's FIRST SOLUTION to UNBRICK NOTE 5 PRO with 100/100 success ratio.
About Me: I am an ordinary Android user since years. I know how to root and install TWRP and Custom ROMs on any Android Phone. I am not a Developer, every thing discussed here is purely gained by experiments by playing with my phone.
After playing with my bricked phone I reach at a point where I am hopeless and I think at this stage a Developer can help me only, who have deep knowledge of android OS. That's why I called Devs to help me.
About Phone I have Note 5 Pro Global (whyred)M1803E7SG. Phone is under warranty but unfortunately Front Glass of my phone is broken few months ago but still working, so Mi Service Center refused to accept my phone under warranty due to broken Front Glass. Tried to repair my phone by a local Phone Service Shop, thay have all professional tools like UMT, Avangers, MedusaPro etc. but they were also unable to repair my phone. Now I have no option left other than I should repair it by myself.
Phone was on ARB4, was working fine. Bootloader Unlocked and I have rooted it long time ago and was playing with it since it is rooted by flashing different Custom ROMs on daily basis.
Currently phone was working fine on Masik X 4.1 ROM. Some days ago I flashed Masik X 5.0 ROM via TWRP on my phone and after reboot phone became dead and went to EDL 9008 mode. I noticed that I flashed Masik X 5.0 for Note 6 Pro (tulip) ROM on it mistakenly.
Journey Stats Here:
1 - After bricking my phone I tried to flash fastboot ROM for whyred in EDL mode, phone flashed successfully but still stucked in EDL mode. Tried all fastboot ROMs from ARB2 to ARB4 but still no sign of life, phone was not coming out of EDL mode. Also tried "test anti4.zip" files as well but phone is still in EDL mode after a successful flashing.
2 -After that I tried to flash fastboot ROM of Note 6 Pro (tulip) in EDL mode, after flashing complete when I tried to turn ON my phone, I noticed that phone try to start with vibrate and charging light blinks for a while but nothing on Screen and phone dead again. I checked with USB cable attached to laptop, nothing appear in Device Manager. Here I opened my phone and bring it to EDL mode via Test Point method.
3 - Then after searching on internet I saw on a forum where another person was in same situation. He mentioned his phone display was turning ON on a Mi 6X (wayne) ROM but with "Press any key to shutdown" message on screen. So tried same with Mi 6X (wayne) ROM. Phone is turning ON with "Press any key to shutdown". So I started playing with Mi 6X ROM. I started replacing Mi 6X ROM file with Note 5 Pro files one by one and flashing my phone again and again with every one new file (took so many hours in playing with my phone:crying. Initially had many issues like: missing keymaster64.mbn file as Mi 6X uses keymaster64.mbn but Note 5 Pro is using keymaster.mbn file (so corrected .xml and .bat files according to need), Unable to mount Persist partition in TWRP (corrected it by terminal method in TWRP by using command "make_ext4fs /dev/block/bootdevice/by-name/persist", phone was going to Fastboot for a while, Not going to recovery mode, No USB detection on laptop in Device Manager. Fastboot lasts for a half second and then phone goes off.
In short at the end finally I noticed only three files "abl.elf, pmic.elf, xbl.elf" from Mi 6X ROM are responsible for turning my phone ON.
4 - So I replaced "abl.elf, pmic.elf, xbl.elf" files from Mi 6X ROM with Note 5 Pro ROM files and flashed my phone with this new modified ROM in EDL mode. Phone turned on without any "Press any key to shutdown" message on screen. Now phone can go to fastboot mode and detected on USB on my laptop. But not going to Recovery mode, after pressing Vol UP + Power Button, only a black screen and nothing happening on my laptop Device Manager (no driver at all). In fastboot mode I flashed "PitchBlack-whyred-2.9.0-20190501-1030-OFFICIAL" recovery (initially I tried TWRP Recovery for whyred but in TWRP phone was not detected as MTP device on my laptop, so I used Pitchblack Recovery) and after issuing boot command to recovery.img I can go to Pitchblack recovery mode, phone detected on USB port as "Note 5 Pro", MTP drive appear in My Computer, I can copy/paste files in phone Storage. In Recovery mode I flashed Official "miui_HMNote5Global_V10.3.1.0.PEIMIXM_d4d2c9f2aa_9.0" ROM. Phone flashed successfully but after reboot phone went to EDL mode again. So I revived it again with modified ROM.
5 - After revival I tried to boot phone in normal way, I noticed that MI Splash screen is blinking with behavior: Splash screen appears fine for a while and on second blink Screen is inverted then 3rd blink Screen fine and 4th blink screen inverted and so on till I reach to MIUI10 welcome screen. On welcome screen the behavior is same like once fine then inverted. But here my touch screen is not working, I can't go after this screen. Phone is not allowing to touch Next button. I can charge my phone with charger connected. Phone detected as "Note 5 Pro" on my laptop.
6 - I rebooted phone to fastboot mode, tried to flash "whyred_global_images_V10.3.1.0.PEIMIXM_20190522.0000.00_9.0_global_8201319a7e" with MiFlash but can't flash due to "Product Mismatch" warning by MiFlash. Tried Mi 6X ROM and MiFlash started flashing fine.
7 - Then I flashed "boot.img, recovery.img, cust.img, system.img" files by using fastboot flash xx xxx.img commands for Note 5 Pro. Fastboot flashed all files successfully. But after rebooting phone behavior is same like blinking inverted screen and touch not working.
8 - Now I am helpless at this stage. Tried all ways to revive my phone. Nothing else is remaining as I think. No other file is remaining which I can try.
HELP REQUIRED FROM A Developer
I reached on a stage where my phone is now "Semi Unbricked" but is still useless for me. But I hope some Developer can help me to revive my phone.
My Note 5 Pro is converted to Mi 6X but touch screen is not working. Screen is working fine in Pitchblack Recovery mode, phone is responding in Fastboot mode but as it is the fastboot mode of Mi 6X on a Note 5 Pro so it is useless for my phone.
Kindly assist me further so I can replace Mi 6X fastboot with original Note 5 Pro fastboot so that I can flash Note 5 Pro ROM on it.
Waiting for a very positive and prompt reply.
Regards!
I'm not an expert as well, and my information needs to be verified by someone smarter than me, but if you are getting a mismatch when u are trying to flash miui V10.3.1.0 then edit the flash_all.bat and try to remove those (fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *whyred" || echo Missmatching image and device
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *whyred" || exit /B) (it's in the beginning) and don't leave any space.
When in edl mode, try to flash miui and select flash_all.bat which is now edited and it should flash.
Before doing those things make sure u have whyred device (redmi note 5 pro)
Verity. said:
I'm not an expert as well, and my information needs to be verified by someone smarter than me, but if you are getting a mismatch when u are trying to flash miui V10.3.1.0 then edit the flash_all.bat and try to remove those (fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *whyred" || echo Missmatching image and device
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *whyred" || exit /B) (it's in the beginning) and don't leave any space.
When in edl mode, try to flash miui and select flash_all.bat which is now edited and it should flash.
Before doing those things make sure u have whyred device (redmi note 5 pro)
Click to expand...
Click to collapse
Thank for the hint. But my problem is not solved.
I removed those two lines from "flash_all.bat" and bring my phone to fastboot mode. Selected whyred fastboot files with edited "flash_all.bat", phone started flashing perfectly and there was no warning "Product mismatch" . But after completing flash successfully phone rebooted and went to EDL mode again.
I also tried the flashing flash_all.bat modified files in EDL mode but result is same.
I again revived phone with my modified ROM which is still useless for me.
Any other hint plzzzzzzzzzz
Verity. said:
I'm not an expert as well, and my information needs to be verified by someone smarter than me, but if you are getting a mismatch when u are trying to flash miui V10.3.1.0 then edit the flash_all.bat and try to remove those (fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *whyred" || echo Missmatching image and device
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *whyred" || exit /B) (it's in the beginning) and don't leave any space.
When in edl mode, try to flash miui and select flash_all.bat which is now edited and it should flash.
Before doing those things make sure u have whyred device (redmi note 5 pro)
Click to expand...
Click to collapse
My intention is to get back the fastboot mode of whyred. So I can flash fastboot ROM of whyred in fastboot mode. I think this is the only way to unbrick my phone.
yawarniazi said:
My intention is to get back the fastboot mode of whyred. So I can flash fastboot ROM of whyred in fastboot mode. I think this is the only way to unbrick my phone.
Click to expand...
Click to collapse
I know it's pretty obvious but have you tried to flash with method I provided with a disconnected battery?
It's weird it doesn't want to leave the edl state, I'm intrigued indeed. Let's hope someone has some ideas that'll revive your phone, at that state I'm out of ideas. If I'll happen to know something new I'll let you know.
Is there any way exist that I can extract fastboot.img file from whyred ROM? Possible to make a falshable zip and flash it via TWRP???
Anyone can help me plzzzzzzzzzz???????????
yawarniazi said:
Is there any way exist that I can extract fastboot.img file from whyred ROM? Possible to make a falshable zip and flash it via TWRP???
Anyone can help me plzzzzzzzzzz???????????
Click to expand...
Click to collapse
a quick check says there's no such file in the firmware package. have you tried to flash correct boot.img file? what i know is fastboot is inside boot.img
kekesed97 said:
a quick check says there's no such file in the firmware package. have you tried to flash correct boot.img file? what i know is fastboot is inside boot.img
Click to expand...
Click to collapse
I already have mentioned in OP that I also flashed "boot.img, recovery.img, cust.img, system.img) in fastboot mode. Flashing went successful but nothing change in behavior of phone's display. Screen is blinking. But if I flash fastboot ROM of whyren in fastboot mode of wayne (which is currently installed on my whyred phone) then phone become dead and go to EDL mode again.
In next post I am going to post "abl.elf, pmic.elf, xbl.elf" files of both whyred and wayne.
Some body please compare these files from both phones and let me know the reason why my whyred phone is turning ON on wayne files only but not on its original whyred files.
I am helpless after reaching this stage, kindly assist me further please.
Kindly compare these files from whyred and wayne
Here are "abl.elf, pmic.elf, xbl.elf" files of both whyred and wayne.
Some body please compare these files from both phones and let me know the reason why my whyred phone is turning ON on wayne files only but not on its original whyred files.
I tried to flash Note 6 Pro (tulip) files as well but after successful flashing phone is totally dead, if I try to turn it ON then it vibrates little and then nothing ( nothing on USB of my laptop, no EDL at all). After that testpoint method is the only way to bring my phone to EDL mode again.
I tried to flash Mi A2 (jasmine) Android ONE files, jasmine is the Global variant of Mi 6X wayne (I believe hardware of both phones is same), but after successful flashing phone goes to EDL mode.
I am helpless after reaching this stage, kindly assist me further please.
Any body knows about display/touch driver files inside Android OS???
My touch screen is not working at all on MIUI Welcome screen. I want to embed Display Driver files in ROM so I can go forward ahead of this Welcome Screen.
I have tried so many ROMs from different Xiaomi models, replaced so many files one by one, spent too much time on doing this all. But the only combination of files works mentioned below:
abl.elf (must be from wayne ROM)
pmic.elf (must be from wayne or tulip ROMs, both working)
xbl.elf (must be from wayne ROM)
All other files from whyred ROM are OK to flash to bring my phone alive.
ROMs Used:
whyred_global_images_V10.3.1.0.PEIMIXM_20190522.0000.00_9.0_global_8201319a7e
wayne_images_V10.3.3.0.PDCCNXM_20190514.0000.00_9.0_cn_1d4725ac4d
tulip_global_images_V10.3.2.0.PEKMIXM_20190426.0000.00_9.0_global_2264f9bd86
Now I concluded all this mess as: I can never go back to whyred original ROM. The only way left is to use my phone as a Mi 6X by name if touch screen of my mobile gets start working.
Some body please help me in replacing Display Driver files of whyred with wayne files.
Kindly assist me to pass through this step. I want to see what's working and what's not after MIUI Welcome Screen. e.g. IMEI, BT, WIFI, SOUND, CALL etc......
Please help
Have you tried to flash the vendor partition with fastboot command?
Gerr1 said:
Have you tried to flash the vendor partition with fastboot command?
Click to expand...
Click to collapse
Yes tried "fastboot flash vendor vendor.img" , vendor.img flashed successfully but phone's blinking behavior is same as before.
yawarniazi said:
Yes tried "fastboot flash vendor vendor.img" , vendor.img flashed successfully but phone's blinking behavior is same as before.
Click to expand...
Click to collapse
Whats about your persist partition? Did it exists, it could be broken from your falseflash action, so you have to repair this first before you flash the right firmware for your device.
link for a mi mix3 but its very similar for the redmi note 5 https://xiaomifirmware.com/guides-and-tips/how-to-restore-persist-partition-on-mi-max-3/
Gerr1 said:
Whats about your persist partition? Did it exists, it could be broken from your falseflash action, so you have to repair this first before you flash the right firmware for your device.
link for a mi mix3 but its very similar for the redmi note 5 https://xiaomifirmware.com/guides-and-tips/how-to-restore-persist-partition-on-mi-max-3/
Click to expand...
Click to collapse
Did this as well but problem is still not solved.
How to backup unlocked bootloader files?
At last I managed to repair 50% of my phone.
I flashed "whyred_global_images_V9.2.4.0.NEIMIEK_20180210.0000.00_7.1_global" version along with replacing abl.elf, pmic.elf, xbl.elf files, now touch screen of my phone is working and is in original condition ( no inverse screen at all anymore ). But blinking problem still exists. But this way at least I can use my phone to some extent. Can connect to Wifi, Can Receive/Dial calls, bluetooth working perfect. Means everything working perfect except Camera and Display which is blinking every second and I need to wait after every second to touch an option or type anything on my phone. Camera is not opening.
I can go to fastboot mode, but this time fastboot mode is working in a blank screen mode (no fastboot wallpaper on screen) but fastboot working perfect. This time I can go to Stock recovery mode by pressing Vol UP + Power Button. Can wipe data in Recovery mode. Tried to choose MiAssistant option and phone connected to my Laptop as a "adb sideload" mode. Tried to send rom.zip file via adb sideload command but getting error "adb: failed to read command: No error" and phone reboot imediately.
Tried to update my phone via Updater App, Updater App prompted me about found OTA update "V9.2.13.0.NEIMIEK", downloaded OTA, tapped on "Reboot & Update", phone rebooted, update process started, but after starting update phone reboot on initial stage and update failed and rebooted phone.
Tried to apply update by manually downloaded full rom "miui_WHYREDGlobal_V9.2.13.0.NEIMIEK_2c4578fa45_7.1.zip", process started without any error, but in the middle of progress bar phone become dead and went to EDL Mode again. I think its due to reason: when phone started writing "abl.elf, pmic.elf, xbl.elf" files then its become dead and went to EDL Mode.
Recovered it again by modified (abl.elf, pmic.elf, xbl.elf) rom "whyred_global_images_V9.2.4.0.NEIMIEK_20180210.0000.00_7.1_global" in EDL mode.
After a little research I came to know its due improper unlocked bootloader. So I tried to unlock bootloader again by "MiFlash Unlock" app, MiFlash Unlock prompted me that Bootloader is already unlocked and there is no need to unlock it again.
Just want to know is there any way I can backup my UNLOCKED BOOTLOADER and write it back to my phone???
I decied to relock my bootloader and Unlock it again. But I am afraid in doing it of "locking my bootloader forever". Because till now "Unlocked Bootloader" is the only thing exists on my phone who is allowing me to flash anything on my phone.
Kindly tell me if backing up Unlocked bootloader is possible?
Where the files "abl.elf, pmic.elf, xbl.elf" exists on my phone?
I want to replace them with original "whyred" files after rooting my phone with Root Browser. OR via adb shell commands.
Please help
You can't backup ubl. Also, think twice before relocking bootloader, it's possible you'll wait for like two weeks until you can unlock it again.
Verity. said:
You can't backup ubl. Also, think twice before relocking bootloader, it's possible you'll wait for like two weeks until you can unlock it again.
Click to expand...
Click to collapse
That's why I stopped myself to Relock Bootloader.
Any help on replacing abl.elf, pmic.elf, xbl.elf files?
I don't know where these files are stored on my device.
I tried flashing these files in fastboot mode, flashing done successful but phone goes to EDL Mode again.
fastboot flash abl abl.elf
fastboot flash pmic pmic.elf
fastboot flash xbl xbl.elf
I am near to unbrick my phone. But stucked with these 3 files.
Found everything like abl, pmic, xbl and persist etc etc etc....
inside /dev/block/
By using
adb shell
su
cd /dev/block
Can anybody help me in reconstructing this directory by replacing my original whyred files instead of abl.elf, pmic.elf, xbl.elf wayne files?
Kindly help pleaseeeeeeeeeeeeeeeeee. So many developers on this forum but no one is ready to help me. Very disappointed
I am fed-up now. Tried every thing to repair this phone but no success at all.
Tried Relock/Unlock bootloader. Relocked and then unlocked again successfully but no impact on phone condition.
Phone is accepting "abl.elf, pmic.elf, xbl.elf" files only from Mi 6X China (wayne).
Screen blinking behavior still exists.
Problem:
Unlocked phone is seemingly stuck in bootloop. Need guidance fixing it.
Explanation:
Hey guys,
I bought a used Nokia 6 (2018) and want to install a custom ROM on it. Last year, I used the paid service to have it unlocked - worked like a charm! So thanks again for that! After reading up on the topic, I set up drivers, adb and fastboot on my PC (Win10). I used
fastboot erase cache
fastboot erase userdata
fastboot erase boot
fastboot erase systemto prepare the phone and then
fastboot boot twrp-3.3.1-1-PL2.imgto get into TWRP. Next is where I ****ed up I think.
I followed a guide and moved twrp-installer-3.3.1-0-PL2.zip on to my SD card. In TWRP, I chose "install" and then picked said installer. After that, I chose the option to reboot.
That must have been the wrong thing to do, because now the phone only boots into download mode. When I hold the power button it does not shut down, but instead instantly reboots into download mode.
When I type
fastboot devicesI still get
PL2GAR9811701240 fastbootand Windows plays the "connect" sound, when I plug it in. Yet all fastboot commands (boot, flash, reboot) now return
FAILED (Write to device failed (Unknown error))What can I do at this point? Can I somehow revert to stock? How is that done? Can I use this guide and the linked stock ROM?
If you'd like more information, just ask away. I'm glad for any guidance at this point, so thanks in advance for your help!
Hello everyone.
Yesterday I bricked my Xiaomi Redmi Note 8 Pro, and today I managed to unbrick it without requiring anything special (no need for a Authorized Service Account).
I use Linux, so the scripts inside the Stock ROM end with the .sh file extension. If you're using Windows, use the .bat files.
Phone:
Xiaomi Redmi Note 8 Pro 128GB - Begonia (with NFC).
Bricked state:
Constant boot loop;
No access to bootloader;
No access to system;
Access to fastboot.
Phone requirement:
You must be able to load fastboot mode.
PC requirements:
1. You'll need adb tools (SDK Platform-Tools) to communicate with your phone. Official link is below;
2. Download and unpack the Stock ROM linked below.
Instructions:
1. You need to make sure your phone has some power in it;
2. Unpack the Stock Rom and enter its folder (begonia_global_images_V10.4.2.0.PGGMIXM_20191024.0000.00_9.0_global);
3. Put your phone into fastboot mode (Key Combo: Hold the Power button + Volume Down button until the fastboot logo appears);
4. Connect your phone to your PC;
5. Run the flash_all.* scripts according to your operating system:
5.1. Linux: "./flash_all.sh";
5.2. Windows (untested; I'm not using Windows): Run "flash_all.bat" (How to Run a BAT File on Windows);
6. Wait something between 5min to 10min. It's quite fast, and the flashing process is verbose enough.
7. Profit.
F.A.Q.:
1. How did you find this?
Well, none of the unbrick methods in the forum were working, except for the Authorised Service Account one which I didn' t test. I desperately wanted to unbrick my phone by myself, and I thought that it couldn't get worse (it could with a completely blank screen, but I got away with it).
2. Where did you get the Stock ROM from?
I can't remember. It likely was from a xda forum post but I'm unsure. If I can find the original post containing the Stock ROM I used I'll write it here.
3. Which Miui and Android version did you have prior to the brick?
MIUI Global 11.x + Android 9.
4. Which Miui and Android version does the Stock ROM you installed have?
MIUI Global 10.4.2 + Android 9.
5. Can I install any Stock ROM?
As long as it's compatible with your phone version, yes. I recommend not installing a Android 10 Stock ROM because of this: https://forum.xda-developers.com/showpost.php?p=82743011&postcount=3
6. What if can't enter fastboot mode (phone screen in dead blank)?
You won't be able to unbrick your phone using this method. It is worth trying to enter fastboot mode even though your phone has a dead screen, because fastboot might be working anyway (you'll have to test this yourself, as in trying to load fastboot with a blank screen). Read the next question.
7. How can I test if fastboot mode is working?
"adb devices" returns nothing;
"fastboot devices" returns your device (proof it works). Since "fastboot devices" finds your device, you can run the appropriate scripts.
8. What about your Mi Unlock Status before and after the brick?
Before: Unlocked.
After: Unlocked (I thought it would lock the bootloader again, but it didn't).
9. My phone is bricked and I don't know how much battery my phone has left. What should I do?
You should let it turn off due to 0% battery and charge it fully. I do not recommend you flash like I did, without knowing how much battery I had (yes, I took my chances there). As far as I know, any phone in fastboot mode does not charge its battery.
10. Why is fastboot working in your case?
I don't know. I suspect flashing the preloader and the lk from this OP Redmi Note 8 Pro - The Megathread helped, but it's just a hunch.
11. Will you attempt to flash a Custom ROM again?
After taking a break, yes.
12. Is this phone now unbrickable?
As long as fastboot mode works, perhaps. More feedback is required.
Files:
SDK Platform-Tools (adb/fastboot): https://developer.android.com/studio/releases/platform-tools
Stock ROM used: http://bigota.d.miui.com/V10.4.2.0.PGGMIXM/begonia_global_images_V10.4.2.0.PGGMIXM_20191024.0000.00_9.0_global_270117fdb2.tgz
Feedback:
Due to my job I'm currently very short on time during the week to follow this thread, so it would be immensely helpful to have your feedback on this procedure.
Feedback from people who's phones are bricked with blank screens would be very appreciated, specifically if they can enter fastboot mode without any visual cues from their phones. If any bricked state allows fastboot mode, it seems this phone is easily unbrickable.
Thanks:
strongst for his understanding and in reopening this thread.
Compass.
Thread open again
strongst
Forum Moderator
Hi there,
Is there anyway to fix the hardbrick without the authorized account?? If not how can i find someone to do this for me?
andrewff2 said:
Hi there,
Is there anyway to fix the hardbrick without the authorized account?? If not how can i find someone to do this for me?
Click to expand...
Click to collapse
Yes, if you can access fastboot mode in your phone like I mentioned above. If hardbrick means loss of access to fastboot mode/recovery/system/basically everything, you'll need to find some other unbrick method.
If fastboot mode is working for you, you can unbrick your device by yourself with nothing else than the fastboot command and the Stock ROM. No need for any extra tools/programs.
inb4: The fastboot command is in the SDK Platform-Tools package I linked in the OP.
Compass.
Compass Linux said:
Yes, if you can access fastboot mode in your phone like I mentioned above. If hardbrick means loss of access to fastboot mode/recovery/system/basically everything, you'll need to find some other unbrick method.
If fastboot mode is working for you, you can unbrick your device by yourself with nothing else than the fastboot command and the Stock ROM. No need for any extra tools/programs.
inb4: The fastboot command is in the SDK Platform-Tools package I linked in the OP.
Compass.
Click to expand...
Click to collapse
Yeah i tried this method but fastboot cannot even detect device
andrewff2 said:
Yeah i tried this method but fastboot cannot even detect device
Click to expand...
Click to collapse
That's a shame.
It's worth trying different USB ports, cables etc.
I usually enter fastboot mode first and only then I connect the phone to my PC.
Then "./fastboot devices" and my phone is listed.
Compass.
Compass Linux said:
Yes, if you can access fastboot mode in your phone like I mentioned above. If hardbrick means loss of access to fastboot mode/recovery/system/basically everything, you'll need to find some other unbrick method.
If fastboot mode is working for you, you can unbrick your device by yourself with nothing else than the fastboot command and the Stock ROM. No need for any extra tools/programs.
inb4: The fastboot command is in the SDK Platform-Tools package I linked in the OP.
Compass.
Click to expand...
Click to collapse
Yeah i tried this method but fastboot cannot even detect device in windows appear com5 in Windows but fastboot do nothing just white led that blinks
andrewff2 said:
Yeah i tried this method but fastboot cannot even detect device in windows appear com5 in Windows but fastboot do nothing just white led that blinks
Click to expand...
Click to collapse
I can't give support in this area, but do you have the proper Windows drivers installed?
If you do and it still doesn't work, try a different computer. If you can use a Linux machine somehow it's worth trying. With Linux I didn't need to install anything besides the SDK Platform-Tools package to communicate with my phone.
I think you can unbrick your phone, because fastboot mode is loading (if it's loading it should reply to fastboot commands).
Compass.
Compass Linux said:
I can't give support in this area, but do you have the proper Windows drivers installed?
If you do and it still doesn't work, try a different computer. If you can use a Linux machine somehow it's worth trying. With Linux I didn't need to install anything besides the SDK Platform-Tools package to communicate with my phone.
I think you can unbrick your phone, because fastboot mode is loading (if it's loading it should reply to fastboot commands).
Compass.
Click to expand...
Click to collapse
Thanks for the help man but no the only thing is the white led that sometimes blink nothing more no vibration no sound no screen nothing.....
I'm trying to find someone who can help me with this but no one responds... sad
andrewff2 said:
Thanks for the help man but no the only thing is the white led that sometimes blink nothing more no vibration no sound no screen nothing.....
I'm trying to find someone who can help me with this but no one responds... sad
Click to expand...
Click to collapse
It seems the only solution for you is this (for now): [GUIDE] [begonia] UNBRICK - stuck on DA mode / Authorised Service Account required
Which you've probably read already.
I think you either do that or wait to see if another unbrick method appears.
Compass.
I have the same problem as yours and tried your solution but after i run flash_all.bat it just opens and closes in a split-second and i have no idea whether it works or not. Should I wait a couple of minutes or just try again?
advan93 said:
I have the same problem as yours and tried your solution but after i run flash_all.bat it just opens and closes in a split-second and i have no idea whether it works or not. Should I wait a couple of minutes or just try again?
Click to expand...
Click to collapse
That's not normal.
What you should see are various files being flashed along with their progress meter.
I'm assuming you're double clicking the .bat file. Instead of doing that, open a CMD Prompt and use that instead.
Compass.
Hi everyone, I am in a real pickle. I can boot into fastboot mode but when I do so I am not able to flash any recovery img or infact any operations on it only " fastboot devices " gives a positive response, else everything just stucks in command line. So my next step was to use the realme Flash tool. in that too when I click on available devices it shows my phone but after that it just quits the fastboot mode and the phone asks me to press any key to reboot.
Guys please help me if there is any way around it as i have tried everything. Can we reset the bootloader itself using some tool if yes then please let me know
Thanks in advance
katti205 said:
Hi everyone, I am in a real pickle. I can boot into fastboot mode but when I do so I am not able to flash any recovery img or infact any operations on it only " fastboot devices " gives a positive response, else everything just stucks in command line. So my next step was to use the realme Flash tool. in that too when I click on available devices it shows my phone but after that it just quits the fastboot mode and the phone asks me to press any key to reboot.
Guys please help me if there is any way around it as i have tried everything. Can we reset the bootloader itself using some tool if yes then please let me know
Thanks in advance
Click to expand...
Click to collapse
This happened twice with me.
Once, my device driver wasn't properly installed.
Second time I didn't gave cmd permission to access my phone.
Was there a pop up on your phone where it asks you something like "do you want this pc to control your phone"?
use diffrent port