Hi, I understand probably not very many people still use Honor 6 these days but maybe somone might be able to help. I got it second hand with official B380 ROM (Android 4.4.2), tried upgrading to B521 (A5.1.1) which didn't finish and caused bootloop. It's L60-H04 version (EU distribution).
the problem: the phone is soft bricked (stuck in bootloop), I can't get to recovery mode, and the three button method with a full ROM on SD card doesn't work either (upgrade either doesn't start at all or gets stuck before finishing); I can get to fastboot mode but flashing doesn't work either, I get the "remote command not allowed" method both when manually using fastboot and typing all the commands and when using Huawei multitool. I assume this means the bootloader is locked. (Although when I check bootloader status it says unlocked, however I've read this might happen but in reality it could still be locked).
I assume it means both boot and recovery are damaged, so flashing (fastboot, adb) seems to be the only option. Unfortunately, the phone is second hand so I have no documentation, don't know the imei and serial number to request the bootloader unlock code.
So, is there any other way to get the code? Or does anyone have any other suggestion how to unbrick? Any help is appreciated.
SOLVED - solved by using paid tools DC-Phoenix and HCU-client
The Xiaomi Mi 5s from a friend is broken. Screen is black, no response from touch. Fingerprint sensor seems to be dead as well. Phone is working in three states:
- normal boot, but it is locked.
- fastboot
- something else I think it is some Xiaomi Bootloader
USB debugging is disabled. Fastboot is useless, and Xiaomi bootloader enables ADB in sideload mode, which is useless as well.
I have tried everything I could think of before posting this here for some ideas.
I tried to unlock the phone using a pc mouse, and even programmed a teensy to automatically draw the unlock pattern simulating a mouse. The thing is that I don't know if I am drawing it properly, or if MTP is still disabled even if I got the phone unlocked.
I also tried to boot into a recovery (I tried twrp and a stock recovery images) but as soon as I try "fastboot boot recovery.img" y fails, because bootloader is locked by xiaomi.
I will try to find a usbC to hdmi and see if I can mirror the screen, but I fear it will not work.
Replacing screen is the last option i'm willing to try.
Hi all.
I read that my oneplus 9 was able to test the beta of android 12 and found that I could do so in developer options and choose the dsu loader. Did that and now my device won't work at all. I can't get into recovery and factory reset it or anything it just restarts itself and i get an error message saying the device is corrupted and won't boot. Is it any way to fix this or have my own foolishness killed this phone? Please help
Illusions_887 said:
Hi all.
I read that my oneplus 9 was able to test the beta of android 12 and found that I could do so in developer options and choose the dsu loader. Did that and now my device won't work at all. I can't get into recovery and factory reset it or anything it just restarts itself and i get an error message saying the device is corrupted and won't boot. Is it any way to fix this or have my own foolishness killed this phone? Please help
Click to expand...
Click to collapse
Not all hope is gone. If there is an msm tool for your variant your in luck. I have the global unlocked op9 and there isn't one yet. Although you can use a fastboot rom from xda. And there is always last resort of calling OnePlus customer service and getting a remote session . Explain to them you tried the beta release and now phone is unuseable . Hope you get it fixed as I bricked my op8 a month or so ago and it's a bad feeling. I also read the developer previews were not for north American devices. Maybe you saw that as well.
Illusions_887 said:
Hi all.
I read that my oneplus 9 was able to test the beta of android 12 and found that I could do so in developer options and choose the dsu loader. Did that and now my device won't work at all. I can't get into recovery and factory reset it or anything it just restarts itself and i get an error message saying the device is corrupted and won't boot. Is it any way to fix this or have my own foolishness killed this phone? Please help
Click to expand...
Click to collapse
If you can boot to fastboot mode. Then fastboot format userdata I think
Didn't work. Think my bootloader is locked as well since I haven't unlocked it at all. Just read online that you could test the android beta by using that dsu thing and now my phone is gone. It was completely stock hadn't touched a thing except that I got into developer options. I didn't think i could brick a phone without mixing with ROMs and stuff.
Can you get it to bootloader?
Power off completely, then 3-button hold (vol up + vol down + power) till bootloader screen.
If you can, and you can get fastboot to recognize the device, you might have a shot at fastboot oem unlock, and then possibly a fastboot rom.
If not, then you might ask Oneplus support for an MSM tool
reaper000 said:
Can you get it to bootloader?
Power off completely, then 3-button hold (vol up + vol down + power) till bootloader screen.
If you can, and you can get fastboot to recognize the device, you might have a shot at fastboot oem unlock, and then possibly a fastboot rom.
If not, then you might ask Oneplus support for an MSM tool
Click to expand...
Click to collapse
No luck with OEM unlock. Contacted oneplus here in sweden and will send the phone to them on Monday hoping they can fix it. Never thought i could mess upp a phone so much by just tinkering with settings within the phone but you live and learn all the time i guess. Bit sad since I got the phone two days ago
I'm attempting to fix a OP7P I've had laying around for a while, but I am having trouble getting it to boot anything. It does boot into fastboot and EDL but the bootloader is locked, and any attempts I've made to revert the firmware with the MSM Tool doesn't get me past the OnePlus logo with the "Powered by Android" blurb at the bottom. I've both tried the stock T-Mobile MSM Tool and the method to convert to international, but neither booted. I'm posting here with the hope that someone has any ideas on what's going on and how I might go about fixing it. I can't quite remember if I had done any modifications in the past either, but I don't believe I had since I didn't use it for very long at all.
deltajordan said:
I'm attempting to fix a OP7P I've had laying around for a while, but I am having trouble getting it to boot anything. It does boot into fastboot and EDL but the bootloader is locked, and any attempts I've made to revert the firmware with the MSM Tool doesn't get me past the OnePlus logo with the "Powered by Android" blurb at the bottom. I've both tried the stock T-Mobile MSM Tool and the method to convert to international, but neither booted. I'm posting here with the hope that someone has any ideas on what's going on and how I might go about fixing it. I can't quite remember if I had done any modifications in the past either, but I don't believe I had since I didn't use it for very long at all.
Click to expand...
Click to collapse
It stuck on logo ?
This is what the screen looks like that it's stuck on. Does this for both recovery and system. (Not my phone, just an example image)
deltajordan said:
I'm attempting to fix a OP7P I've had laying around for a while, but I am having trouble getting it to boot anything. It does boot into fastboot and EDL but the bootloader is locked, and any attempts I've made to revert the firmware with the MSM Tool doesn't get me past the OnePlus logo with the "Powered by Android" blurb at the bottom. I've both tried the stock T-Mobile MSM Tool and the method to convert to international, but neither booted. I'm posting here with the hope that someone has any ideas on what's going on and how I might go about fixing it. I can't quite remember if I had done any modifications in the past either, but I don't believe I had since I didn't use it for very long at all.
Click to expand...
Click to collapse
Use my boot image and intro post here
Post in thread 'urgent: oneplus 7 pro TWRP bootloop' https://forum.xda-developers.com/t/urgent-oneplus-7-pro-twrp-bootloop.4413775/post-86554665.
Anyone have this problem and solved it? I have an ASUS Zenfone Max Plus M1 (ZB570TL ) - (X018D) and i have tried every Rom you can think of from WW to CTC to CN, also tried dump firmware but nothing will stick and let this device actually fully boot up after flashing it, it just goes to the POWERED BY ANDROID screen and after 30 secs it will reboot itself back to the POWERED BY ANDROID screen and then reboot again and so on..
HOLDING VOL+ and POWER buttons in gets me to the:
- RECOVERY MODE - Just reboots back to Powered by Android screen and back to bootloop, no android guy recovery...
- FASTBOOT - Lets me have Fastboot but i cant flash anything or unlock bootloader as it errors and shows its Locked...
- NORMAL BOOT - Just reboots back to the Powered by Android and then reboots after 30 secs right back there....
There is no RECOVERY MODE that i can Factory Reset, Update.zip, clear cache...
I Flashed with SP Flashtool over 20 Firmwares and all finish with the popup Finished and green checkmark and i watch the flash process all the way without error, unplug the device and turn it on and back to Powered by Android screen and reboots itself after 30 secs... THIS IS CRAZY its like its a GAG Phone or something just messing with me like ( Jokes on you big guy ) ive never seen anything like it, its like the locked bootloader is telling the device not to allow any Firmware to install by tricking the SP Flashtool that yes it did install but didnt allow it to write to the actual system or let you get into recovery mode to factory reset the device or update from sdcard... im just wondering if its a waste of time to bother finding a UFI Box flasher that doesnt need the dongle so i could try flashing the EMMC files if that would help or not... its not a hardware problem or it wouldnt accept flashing or let it power on and enter fastboot mode....
Is this a GAG Device or has anyone actually had this exact problem and has solved it? If i could just get it to boot up into the system i could use Magisk and make a patched-boot.img thats unlocked bootloader and root but theres no ZenUI or anything but the Powered by Android screen....
Any Help would be awesome as i just put new screen, battery, back cover and buttons on this device thinking it would be a good little phone for my daughter... i cant even get any info on the device as theres no box or sticker with IMEI or Serial Number or info on the last working Firmware its all a shot in the dark... Anyways if anyone has the way to get this device working or has backup rom or links to an actual way thats not ASUS as they are just waste of time for 30 mins then you need to take it in to our service center and pay more money and im done putting money in this and could have bought her a new phone for what ive got into this Gag Phone....
Thankz...... Kixx
Judging from the whole situation, you screwed up several things honestly.
The fact it goes stuck on the splash screen and refuses to neither boot on recovery nor the system itself seems to tell 2 things:
the boot.img and recovery.img got screwed up way too much- or literally got flashed for the wrong device, hence the whole rejection to boot;
i assume SP Flashtool, even if got tricked, got a bit of a mess on the internal partitions to be flashed thru. Sounds like a big red flag because ADB can be highly of help (i don't own an X01BD but an X00HD- still an asus device- but i used simple ADB instead of things like QFIL or SP Flashtool to get things going);
On second point, if you wanna try to unlock the bootloader (since fastboot is the only one to be alive and usable- this means your device will be salvageable...atleast by a significant chunk):
you can give it an attempt by checking over my own collection post.
There you will find at the bottom some tiny guide on how to unlock the bootloader-
if you don't have a secondary rooted device, you can always rely using a laptop or pc.
What really matters is that you'll have ADB downloaded on your machine, because it could be of help to progress thru with the stuff.
After unlocked the bootloader, you can slowly approach to flash TWRP for your own device- even tho, it seems nobody so far has done anything for this specific model...
Atleast, on the bright side, unlocking the bootloader will give you the chance to flash manually the partitions via ADB, and maybe the official zendesk site for it can help if unpacking one of the update zips and see the contents inside- or generally pushing the following .zip update file via ADB and wait for the magic to happen.
I'm not sure on how to help with the region tho.
I guess, if you have the box of the device, it could give you a clue if it is a WW (WorldWide), CN (China), JP (Japan), etc. model- afterall, these letters do not lay around without a reason.
Of course, if you flash the wrong region to the wrong regional model:
then the recovery and system partitions get to screw up big time, just like the scenario you're having right now.
As a last thing, the patched boot.img file only gets to work after you got android to work-
otherwise, patching the pre-rooted boot.img file will be of no use since a functioning ROM isn't there at all.
Sadly, i don't own the device nor never had such screw-ups of this kind, but i hope it will help you up.
Ya i can flash the firmware correctly in SP Flashtool it comes back with green checkmark, all the firmware is for the correct device, its just when i had it given to me it had broken screen and bad battery, so i buy new screen, battery, backcover for it and when i booted it up it just sticks on the first screen shown ( Powered by Android ) then after like 30 secs it reboots back to that screen.. I can hold the vol + and power and get the menu to pick RECOVERY or FASTBOOT or REBOOT, recovery just reboots to powered by android screen then reboots after 30 secs, fastboot lets me use adb and fastboot but cant flash it says failed locked, and fastboot oen unlock or any of the commands to do with unlocking or flashing just gets me failed locked, but fastboot does work. Only way to root or unlock bootloader the device needs full boot into system so i can enable adb debugging or usb debug in developer settings so the computer will let the device get past the failed error locked part....
Do you know how to get the usb debugging turned on so the computer can grant full access to the device then il be able to actually crack into it and flash through fastboot..
Or where the usb debugging file is in the system.img if i extract it, use text editor and give the bool a yes that its been accepted then repack the system,img and flash it usinh sp flashtools, then i might ge able yo get it up and running....
After flashing all kinds of firmware for this device they all pass the flashing except for a few of them, ones that dont work wont even let the device boot to show system thing, then flashing correct firmware it allows the first screen again and the menu to pick fastboot but wont fully boot up..
Im thinking there must be somekind of lock the device put on from letting you oem unlock bootloader or booting into recovery mode because the firmware is working or it wouldnt take it using SP Flash Tools or even let it boot up as it would either reboot instantly or not even turn on, if the boot partition or recovery partition was courupt or broken or damaged it wouldnt take it during the flashing process it would fail....
If you know how i can activate the usb in developer settings from a file in system.img file after ectracting it then thats prob my BEST OPTION OR BUY A USED MOTHERBOATD OFF EBAY...
Lol
KixxTheManz said:
Ya i can flash the firmware correctly in SP Flashtool it comes back with green checkmark, all the firmware is for the correct device, its just when i had it given to me it had broken screen and bad battery, so i buy new screen, battery, backcover for it and when i booted it up it just sticks on the first screen shown ( Powered by Android ) then after like 30 secs it reboots back to that screen.. I can hold the vol + and power and get the menu to pick RECOVERY or FASTBOOT or REBOOT, recovery just reboots to powered by android screen then reboots after 30 secs, fastboot lets me use adb and fastboot but cant flash it says failed locked, and fastboot oen unlock or any of the commands to do with unlocking or flashing just gets me failed locked, but fastboot does work. Only way to root or unlock bootloader the device needs full boot into system so i can enable adb debugging or usb debug in developer settings so the computer will let the device get past the failed error locked part....
Do you know how to get the usb debugging turned on so the computer can grant full access to the device then il be able to actually crack into it and flash through fastboot..
Or where the usb debugging file is in the system.img if i extract it, use text editor and give the bool a yes that its been accepted then repack the system,img and flash it usinh sp flashtools, then i might ge able yo get it up and running....
After flashing all kinds of firmware for this device they all pass the flashing except for a few of them, ones that dont work wont even let the device boot to show system thing, then flashing correct firmware it allows the first screen again and the menu to pick fastboot but wont fully boot up..
Im thinking there must be somekind of lock the device put on from letting you oem unlock bootloader or booting into recovery mode because the firmware is working or it wouldnt take it using SP Flash Tools or even let it boot up as it would either reboot instantly or not even turn on, if the boot partition or recovery partition was courupt or broken or damaged it wouldnt take it during the flashing process it would fail....
If you know how i can activate the usb in developer settings from a file in system.img file after ectracting it then thats prob my BEST OPTION OR BUY A USED MOTHERBOATD OFF EBAY...
Lol
Click to expand...
Click to collapse
Well, as far as i can tell and did unlock 2 asus devices of the same model (still, X00HD):
i didn't needed to go thru android, since Asus never had an "OEM Unlock" thing to enable once unlocked dev settings-
yet, i'm speaking about the X00HD since, again, i never owned an X01BD, but i am trying to apply the same reasoning even if it is an entire different model but still same brand.
Dunno, in my case i was able to get the bootloader unlocked by going getvar all and got the secret key to unlock it just as easily by experimenting and finding cmds to use over this device's forum in here while being in Fastboot mode.
Before stepping my feet to Fastboot, tho, i even tried to get my hands at an OEM Unlocker apk made by Asus:
but to no avail it only worked on devices with really old firmware and since my device was updated to the latest Oreo FW, it was impossible to perform since things got patched overtime.
Sadly, i really don't know how to modify values over system.img files myself and tick up variables by inspecting over hex editors and such.
Least i know is getting the Brotli binaries and some other specific tool on GitHub to extract stuff from Android .img files, but that's all my skills really get limited to since i'm no dev myself nor either someone who can reverse engineer things just as well.
I think you could be out of luck on that regard.
Only thing that remains is going to a particular mode where it is required putting the phone apart and touch 2 specific pins on the board to enter it.
I currently forgot the name of this mode, but i do know by fact it's a common thing between Huawei devices.
If even this thingie won't help, then i really dunno myself.
Maybe someone else could be of help instead of me lol.
Ya ill try touching the two pins but what two oins and touch them with whst? Give me a roll out on what to do, i just dont understand why it accepts firmware but wont let me boot up into it or recovery mode or flash anything because at first it flashes then when it completes it fails and says remote unknown locked
Also im going to try find a way to format or partition the main system partitions maybe the system.img is landing on a different section of the harddrive... just need tge partitions for thus device
KixxTheManz said:
Ya ill try touching the two pins but what two oins and touch them with whst? Give me a roll out on what to do, i just dont understand why it accepts firmware but wont let me boot up into it or recovery mode or flash anything because at first it flashes then when it completes it fails and says remote unknown locked
Click to expand...
Click to collapse
Aight, to start with: i'll share out a couple of links.
First, here's a picture on where the testpoints of the device are.
As of second, you need some tweezers or something that is able to touch such testpoints inside the board (unrelated, but the GH page to PotatoNV has a guide what to do with the testpoints- even tho, the page redirects you to a tool that only works with Huawei devices. Don't test it on that asus device.).
Not sure about the flashing tool, honestly, but i do know for a fact i couldn't share software in here due to rules of this forum.
Since this is, i suppose, a device with a Qualcomm SoC:
maybe you could use stuff like QFIL Flash Tool for the job (dunno about partitions, for that you should get some linux knowledge- since android uses the linux kernel to communicate with everything inside the device).
Also, i've got something intriguing right now:
apparently the forum for the X01BD effectively exists over XDA lol (turns out the X01BD is a Zenfone Max Plus M2 and not an M1).
Maybe you can check out here for further custom ROMs and recoveries, plus more proper help on the matter- as of firmware dumps, you could try hopping over Android FileHost, firmware.mobi, or steep your feet into some unknown forum that has the firmware dumps of this specific device and restore it logically (or simply doing a google search by doing [insert model number here] firmware dump - if google only gets you to shady sites, stick to the XDA forum on the device).