I am stuck. This is my first phone with an A/B Partition and I have managed to erase everything except my bootloader. I can use fastboot and flash but i can not get this thing to reboot into system or TWRP. Can anyone help me here?
I have tried the guide using flashall_aft cmd and I cant seem to get a flashall to work either.
Keep phone in fastboot mode..
Extract boot.img from the last firmware you are in and flash it using fastboot command...and reboot bootloader..now AFT will work.
Since you are in TWRP, AFT will not work cus you are in modified boot image. Do not wipe anything now...just do above...AFT will work.
This phone AB partition scheme is dicey and little mistake phone wont boot. Lucky you, still fastboot is availble
I am only able to access bootloader with active slot as b. Tryed using commands to switch to slot a but I am having no luck. I cant flash the system or recovery, only the boot.img and a reboot just takes me back to the bootloader.
PS C:\Users\Custom\Desktop\payload_dumper-win64\payload_output> flashall_aft.cmd
flashall_aft.cmd : The term 'flashall_aft.cmd' is not recognized as the name of a cmdlet, function, script file, or
operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try
again.
At line:1 char:1
+ flashall_aft.cmd
+ ~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (flashall_aft.cmd:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
zdaddi said:
PS C:\Users\Custom\Desktop\payload_dumper-win64\payload_output> flashall_aft.cmd
flashall_aft.cmd : The term 'flashall_aft.cmd' is not recognized as the name of a cmdlet, function, script file, or
operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try
again.
At line:1 char:1
+ flashall_aft.cmd
+ ~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (flashall_aft.cmd:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
Click to expand...
Click to collapse
Is the flashall_aft.cmd file in that directory? I.e can you see it ?
Get raw firmware zip, extract and run flashall in raw firmware folder. Firmware comes with script. It will restore Android file system. Boot to system and update fw and you're back to square one.
Phone is bricked now
I cant get it to turn on at all
zdaddi said:
Phone is bricked now
I cant get it to turn on at all
Click to expand...
Click to collapse
Is it the battery being drained completely?
No. I left it on the charger over night
If you can't boot into bootloader by any means you may want to look into intensively technical unbrick methods. There are guides in this forum. If you have tampered to the point where its practicality is outweighed, you made a mistake unfortunately RIP your device.
amscova said:
If you can't boot into bootloader by any means you may want to look into intensively technical unbrick methods. There are guides in this forum. If you have tampered to the point where its practicality is outweighed, you made a mistake unfortunately RIP your device.
Click to expand...
Click to collapse
could you post a link to the guide that you are talking about? I will give it a shot. I have been tinkering with phones based off of guides on xda for over a decade now. I dont want to ruin one now if i can help it. Thanks
zdaddi said:
could you post a link to the guide that you are talking about? I will give it a shot. I have been tinkering with phones based off of guides on xda for over a decade now. I dont want to ruin one now if i can help it. Thanks
Click to expand...
Click to collapse
Think this will be the only one
https://forum.xda-developers.com/zenfone-5z/how-to/qfil-testpoint-edl-zs620kl-t3950926
And this
https://forum.xda-developers.com/zenfone-5z/how-to/discuss-unbrick-zenfone-5z-zs620kl-t3889459
Getting the phone to boot into fastboot again will be the biggest hurdle. Once you do that you'll be able to get going again
Same issue
Hey Zdaddi,
Did you manage to solve this problem? i am facing the same problem.. i am able to load into fastboot mode but nothing works after that.. i have tried the flashall_aft.cmd on latest firmware as well as tried asus aft tool. the tool gave an error that unable to boot into recovery.. not the screen is always on in fasboot mode. as soon as i try to go to start mode or recovery the bootloader restarts and the same scrren comes again.. Any suggestions would be helpful please
Related
Dear All,
I hard bricked my ZE551ML 64GB by using the following sequence:
'fastboot flash fastboot droidboot.img'
'fastboot flash fastboot recovery.img'
'fastboot flash fastboot boot.img'
'fastboot flash fastboot system.img' <-- got error only at this stage
So don't do it it is totally wrong.
Now I got the usb logo when i go to fastboot, see attached image.
I can see a procedure for Zenfone 5 to recover from this error here:
http://www.asus-zenfone.com/2014/11/how-to-unbrick-zenfone-5-and-zenfone-6_8.html
My question is does the same procedure exists for Zenfone 2 and where to download all the files?
Thanks
I believe most of the programs there should also work for the ZF2. I would give this procedure a try, and I wish I could get my hands on a Bricked device to try this. But remember, DON'T use the ZF5/6 images!
Get the stock images for the ZF2 from: https://www.asus.com/Phones/ZenFone_2_ZE551ML/HelpDesk_Download/
EdoIsa said:
I believe most of the programs there should also work for the ZF2. I would give this procedure a try, and I wish I could get my hands on a Bricked device to try this. But remember, DON'T use the ZF5/6 images!
Get the stock images for the ZF2 from: https://www.asus.com/Phones/ZenFone_2_ZE551ML/HelpDesk_Download/
Click to expand...
Click to collapse
What are FZ DnX, IFWI, FW DnX and OS images files ?
How to extract them from the site you mentioned?
Another issue, is my PC refuses to regonise the ZF2 when connecting to USB, saying MTP Android USB driver failed to install....
I have no experience with FZ DnX, IFWI, FW DnX files, but the OS image file is on the site I posted.
Follow my link. Once there, expand the list 'Firmware' and download firmware Version WW_2.15.40.10. Once its downloaded, open the zip file. Inside should be a System.img file. Extract the System.img file into your Fastboot folder. This is the OS image the guide is referring to.
Ask around for the meaning of the other files. Meanwhile, I will research more about those files later tomorrow and get back with any info I can find. Good luck!
cde2006 said:
Another issue, is my PC refuses to regonise the ZF2 when connecting to USB, saying MTP Android USB driver failed to install....
Click to expand...
Click to collapse
install driver manually. see attachment.
When you plug your phone into the computer, does the phone show up in the device management? Typing devmgmt.msc into the windows 7 start menu or the start run menu on XP is the fastest way to get to Device Manager.
Is the device already known by your computer?
What does device manager think it is?
If its unknown, please let us know what the Hardware Ids and Compatible Ids for this device show up as. In device manageer, you can open the devices properties and under the details tab choose Hardware Ids and Compatible Ids. you could screen shot these with Alt + PrtScn and use mspaint to save them off. Otherwise you have to use Ctrl + C to copy them out . You can choose all lines by selecting the first and while holding Shift, select the last. Then you can Ctrl + C to copy all of them out.
Looks like you've flashed incorrectly.
Should be
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
What you've essentially done (or tried to do) is flashed over fastboot with 4 different images. Only the first line of commands you used is correct.
Chinaphonearena said:
Looks like you've flashed incorrectly.
Should be
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
What you've essentially done (or tried to do) is flashed over fastboot with 4 different images. Only the first line of commands you used is correct.
Click to expand...
Click to collapse
Yes got this sequence from this forum,,, anyway I go the phone replaced now and all is fine.
Thanks people for the help.
I won't be rooting this phone until there is a more safe proven way to do it.
I think that avoiding flashing droidboot and recovery, and making sure file hashes match, everything should be fine.
Same issue
---------- Post added at 04:05 AM ---------- Previous post was at 04:02 AM ----------
cde2006 said:
Dear All,
I hard bricked my ZE551ML 64GB by using the following sequence:
'fastboot flash fastboot droidboot.img'
'fastboot flash fastboot recovery.img'
'fastboot flash fastboot boot.img'
'fastboot flash fastboot system.img' <-- got error only at this stage
So don't do it it is totally wrong.
Now I got the usb logo when i go to fastboot, see attached image.
I can see a procedure for Zenfone 5 to recover from this error here:
http://www.asus-zenfone.com/2014/11/how-to-unbrick-zenfone-5-and-zenfone-6_8.html
My question is does the same procedure exists for Zenfone 2 and where to download all the files?
Thanks
Click to expand...
Click to collapse
I put my 64gb sd in my ZF2 that I originally partitioned for my LG Optimus Pro and I moved a bunch of apps to the SD with link2sd and the first time I rebooted, the same screen with the USB logo and a full progress bar showed up. It won't recognize any fastboot or adb commands even though the ASUS adb is showing up in device manager. Nothing else shows up. In devices and printers I get Moorefield. The phone randomly reboots and goes back to the same screen over and over and each time the asus adb disappears from device manager and then returns. I found a guide on the zenfone 5 that looks promising, using the intel flash tool, however it requires the ZenFone 2 raw firmware files and I can't find them... Hopefully someone could help me salvage my ZF2 cuz I was really beginning love the phone... Thanks ahead of time for anyone that looks into this for me!
i can give you the files you look for. the easiest was is to flash with intel flash tool. Here you can read how th etool works and you found a link there.
I load your files up now here.
sry, had only the files for V5. I will load down and put it here.
boot error and bricked zenfone 2
i have same problem with my phone please send moorefields or other intel based boot drivers.. tanks
please tutor how to fixed it, thanks for advice
cde2006 said:
Yes got this sequence from this forum,,, anyway I go the phone replaced now and all is fine.
Thanks people for the help.
I won't be rooting this phone until there is a more safe proven way to do it.
Click to expand...
Click to collapse
Lol @ "got sequence on this forum" and "more safe proven way."
You didn't read the instructions carefully enough and made a big mistake as a result. The correct sequence was given. You just didn't read it carefully. Lesson learned.
Hopefully you can unbrick it.
No offense, but this type of thing is what happens when people just copy/paste and don't understand what they're doing.
What you did was overwrite the fastboot partition each time you flashed. You flashed a 2GB system img on top of your fastboot partition. This probably seemed like it locked up and you either unplugged or turned it off. This likely caused a corrupt partition.
Reading is key when you do anything with your phone.
This is perfectly safe. This is the way it works for all devices. It has nothing to do with the files or the phone. This was 100% user error. Simple as that.
ze550ml hard brick
http://forum.xda-developers.com/zenfone2/help/zenfone2-ze550ml-hard-bricked-t3148174#post61657126
my ze550ml hard brick too. please help me
sorry for bad english.
hardbrick zenfone 2
konsolen said:
i can give you the files you look for. the easiest was is to flash with intel flash tool. Here you can read how th etool works and you found a link there.
I load your files up now here.
Click to expand...
Click to collapse
Hello, i have the same issue with my zenfone 2, I download the firmware files from Asus website, but the Intel flash tool can't found a flashable image file. My question is to, if you have the firmware files that send it to me?
same issues here please help,
same issues here please help,
Hi all,
I installed TWRP on my Honor 7x, that went well.
Yesterday I decided to try to get Lineage working so:
- I installed EMUI 8, that went pretty smooth
- I installed Lineage OS 15.1. (without GApps)
- I flashed TWRP.
The issue I have now is that:
1) I can't install any APK in Lineage. Probably needs a factory reset/dalvik cache wipe.
2) I can't boot into TWRP. It stays stuck on the splash screen forever. This also means I can't install OpenGapps, SuperUser access (afaik), or anything else that requires root.
3) The bootloader is saying "FRP: Locked", which means I can't flash a new TWRP or a different ROM. When I try it fails with "command not allowed"
3) "fastboot oem unlock" fails saying I need to enable it in the developer options, but it's grayed out in the developer options because it's already unlocked.
4) I wanted to try the "dload" method but I can't find a good explanation on how to do it, and Huawei recently took all their downloads down, which means I can't find any UPDATE.app even if I knew how.
5) The other solution that *might* work is using "fastboot oem frp-unlock", but I need an unlock code for that (I assume the same one that you request for an OEM unlock from Huawei), and Huawei closed down the site that generated the codes.
So I'm stuck in a weird limbo where I can't move forward (install Gapps and use my phone as normal) nor backwards (go back to EMUI8).
Does anyone have any idea how I can fix this situation?
Shadowsalyer said:
Hi all,
I installed TWRP on my Honor 7x, that went well.
Yesterday I decided to try to get Lineage working so:
- I installed EMUI 8, that went pretty smooth
- I installed Lineage OS 15.1. (without GApps)
- I flashed TWRP.
The issue I have now is that:
1) I can't install any APK in Lineage. Probably needs a factory reset/dalvik cache wipe.
2) I can't boot into TWRP. It stays stuck on the splash screen forever. This also means I can't install OpenGapps, SuperUser access (afaik), or anything else that requires root.
3) The bootloader is saying "FRP: Locked", which means I can't flash a new TWRP or a different ROM. When I try it fails with "command not allowed"
3) "fastboot oem unlock" fails saying I need to enable it in the developer options, but it's grayed out in the developer options because it's already unlocked.
4) I wanted to try the "dload" method but I can't find a good explanation on how to do it, and Huawei recently took all their downloads down, which means I can't find any UPDATE.app even if I knew how.
5) The other solution that *might* work is using "fastboot oem frp-unlock", but I need an unlock code for that (I assume the same one that you request for an OEM unlock from Huawei), and Huawei closed down the site that generated the codes.
So I'm stuck in a weird limbo where I can't move forward (install Gapps and use my phone as normal) nor backwards (go back to EMUI8).
Does anyone have any idea how I can fix this situation?
Click to expand...
Click to collapse
small chance you enable root from developer options. (i think it will be adb only)
if so , maybe can use adb shell and "dd" to write recovery to correct partition.
problem is many of the available twrp do not boot on custom rom .
example code. (if you do wrong , it may be bad)
Code:
dd if=/ext_sdcard/twrp_Recovery_ramdisk.img of=/dev/block/mmcblk0p32
It seems like I'm allowed to use dd in ADB shell, but before I run it, what do you mean by " problem is many of the available twrp do not boot on custom rom . "? I thought recovery was independent of the ROM? And does it mean flashing twrp like that could brick my phone?
Shadowsalyer said:
It seems like I'm allowed to use dd in ADB shell, but before I run it, what do you mean by " problem is many of the available twrp do not boot on custom rom . "? I thought recovery was independent of the ROM? And does it mean flashing twrp like that could brick my phone?
Click to expand...
Click to collapse
Like what you have , twrp stuck on splash screen
I managed to unlock the FRP with DC-unlocker. Sucks that it costs money but it worked!
Now Im stuck in a TWRP boot loop though.
Shadowsalyer said:
I managed to unlock the FRP with DC-unlocker. Sucks that it costs money but it worked!
Now Im stuck in a TWRP boot loop though.
Click to expand...
Click to collapse
At this point you should have access to fastboot though, right? I'd try a different TWRP instead. Perhaps try this one: https://drive.google.com/file/d/1ZYo7Ndte3vlLcUSadD6jIgfBi1oxa0Pb/view?usp=drivesdk
Just to clarify, it gets stuck on TWRP splash screen. When I turn off the phone, it immediately boots up again into TWRP. I tried getting into fastboot mode with all kinds of combinations of button presses, but no luck. Not even Volume Up + USB cable works
smokinjoe2122 said:
At this point you should have access to fastboot though, right? I'd try a different TWRP instead. Perhaps try this one: https://drive.google.com/file/d/1ZYo7Ndte3vlLcUSadD6jIgfBi1oxa0Pb/view?usp=drivesdk
Click to expand...
Click to collapse
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.
Shadowsalyer said:
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.
Click to expand...
Click to collapse
I have seen this happen before , solution was to wait for dead battery, or disassemble to unplug battery
---------- Post added at 04:51 PM ---------- Previous post was at 04:47 PM ----------
Shadowsalyer said:
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.
Click to expand...
Click to collapse
This is because after the frp unlock, it needed to see a factory reset, and it usually needs to be done with stock recvery.
So will have to wait till battery is dead and and plug in usb while holding volume button. Should then load to fastboot. Where it is best to flash stock recovery to clear the recovery bootloop. The bootloop is do to the fact yo unlocked frp and now phone needs to wipe/data
Shadowsalyer said:
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.
Click to expand...
Click to collapse
it sucks this happened to yu but im glad i am not the only one that dc-unlocker deleted my fastboot after i unlocked the frp and i cant boot fastboot for nothing if you find a solution please contact me. my phone is doing the exact same thing booting straight too twrp no mater what combinations i use
dcraffam said:
it sucks this happened to yu but im glad i am not the only one that dc-unlocker deleted my fastboot after i unlocked the frp and i cant boot fastboot for nothing if you find a solution please contact me. my phone is doing the exact same thing booting straight too twrp no mater what combinations i use
Click to expand...
Click to collapse
i just took mine apart and discconected the battery and still no luck that program deleted my fastboot
Please can you tell me the process to install twrp I have the L24
I waited all the way till the battery drained, stuck in the USB, and it booted to ROM! Sadly it immediately shut off again because the battery is dead (even with keeping the USB in). I'm going to keep trying though.
I can't get into fastboot mode. I can get into the ROM by letting the battery drain completely on the TWRP splashscreen, and then sticking in the USB cable. However, no button combination or "adb reboot bootloader" or rebooting to bootloader from the ROM brings me to the bootloader. I wonder if it's still there. Any ideas?
Shadowsalyer said:
I can't get into fastboot mode. I can get into the ROM by letting the battery drain completely on the TWRP splashscreen, and then sticking in the USB cable. However, no button combination or "adb reboot bootloader" or rebooting to bootloader from the ROM brings me to the bootloader. I wonder if it's still there. Any ideas?
Click to expand...
Click to collapse
Seems to be a f-up situation either way.
You have adb DD available, found out before.
Don't know if maybe flashing stock recovery is good idea at this point.
I think fastboot.img can be flashed with DD too, but don't try till someone can confirm.
If flash stock recovery clears the loops, maybe best to do full-ota manual flashing.
I managed to get an UPDATE.APP file and extract fastboot.img from it, as well as all the other .img files. If someone can tell me what to flash and how (with dd), I think Im set.
Shadowsalyer said:
I managed to get an UPDATE.APP file and extract fastboot.img from it, as well as all the other .img files. If someone can tell me what to flash and how (with dd), I think Im set.
Click to expand...
Click to collapse
Fastboot.img is the large part the bootloader. If flashing it goes bad, might be dead phone after, just rember that.
Will add a list of partition names and command s for you soon.
here is a list of oreo partitions and there /dev/blk/** number
and here is an example of code to save images with dd assuming you put the images on your extrnal-sdcard in folder called oreo-images
Code:
dd if=/dev/block/mmcblk0p5 of=/mnt/ext_sdcard/oreo-images/fastboot.img
Do that save first and compare the md5 of the file from update.app to this file.
or just check the md5 before making the copy
Code:
adb shell md5sum /dev/block/mmcblk0p5
If you are conviced you need to flash the images, here is example of writing the image assuming files are in sdcard folder oreo-update-images
Code:
dd if=/mnt/ext_sdcard/oreoupdate-images/fastboot.img of=/dev/block/mmcblk0p5
As I have said, this might be bad advise , I have not done fastboot.img flashing before. But on other devices it is same as lk.img or uboot.img, There is danger in flashing it incorrectly. That is why my suggestion was to flash no-check-recovery and do manael update with "echo -update_package" commands.
Along with the statement that fastboot.img is similar to lk.img or uboot.img on other phones, Your fastboot cannot be gone. because phone boots.
but do let us know how it goes.
I agree it would be better to flash recovery if possible. I assume I need the NoCheck-Recovery image from this thread? https://forum.xda-developers.com/honor-7x/how-to/manual-update-to-oreo-beta-emui-8-bnd-t3767044
And what partition do I have to flash it to? I'm guessing either /dev/block/mmcblk0p28 (erecovery ramdisk) or /dev/block/mmcblk0p32 (recovery ramdisk)? I'm not sure what the difference is between erecovery and normal recovery.
(didn't flash fastboot yet, wanted to see if recovery was doable).
Shadowsalyer said:
I agree it would be better to flash recovery if possible. I assume I need the NoCheck-Recovery image from this thread? https://forum.xda-developers.com/honor-7x/how-to/manual-update-to-oreo-beta-emui-8-bnd-t3767044
And what partition do I have to flash it to? I'm guessing either /dev/block/mmcblk0p28 (erecovery ramdisk) or /dev/block/mmcblk0p32 (recovery ramdisk)? I'm not sure what the difference is between erecovery and normal recovery.
(didn't flash fastboot yet, wanted to see if recovery was doable).
Click to expand...
Click to collapse
To recovery_ramdisk. 32
What about check md5 of fastboot partition, that will be helpful to know if it did get wiped out.?
Hmm seems like I'm not allowed to use dd after all:
HWBND-H:/ $ dd if=/storage/7C96-7E17/BND-RECOVERY-NoCheck.img of=/dev/block/mmcblk0p32
dd: /dev/block/mmcblk0p32: Permission denied
And here I was thinking I was close to solving it...
Also can't run md5sum on the fastboot partition, since that needs root as well.
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
On the screen I get: your device is corrupted and cannot be trusted and cannot reboot
Simply disable Developer options and the any settings you altered there will revert to baseline.
If that doesn't get it then it's not Developer options...
blackhawk said:
Simply disable Developer options and the any settings you altered there will revert to baseline.
If that doesn't get it then it's not Developer options...
Click to expand...
Click to collapse
Thanks for answering
The device may boot into a bootloader or an error on the screen
EranG90 said:
Thanks for answering
The device may boot into a bootloader or an error on the screen
Click to expand...
Click to collapse
You locked the bootloader while running modified software.
Unlock it again
Code:
fastboot oem unlock
craznazn said:
You locked the bootloader while running modified software.
Unlock it again
Code:
fastboot oem unlock
Click to expand...
Click to collapse
Thank you
I have now done that and the screens are in the same condition as in the pictures
It is good? Should I keep waiting? (I don't know really what to do, I am new at this. I don't know even if the device got the commend from the pc)
We can't really help you until you confirm what you did to get it in this state in the first place?
Did you install the OxygenOS 12 Developer Preview?
Did you try rooting by replacing the stock boot.img?
Please confirm what caused this in the first place as changing something in the developer settings alone would not cause this.
djsubterrain said:
We can't really help you until you confirm what you did to get it in this state in the first place?
Did you install the OxygenOS 12 Developer Preview?
Did you try rooting by replacing the stock boot.img?
Please confirm what caused this in the first place as changing something in the developer settings alone would not cause this.
Click to expand...
Click to collapse
Sorry like I said before I am new at this
I have change somting in the DSU option. I think this was the Acronyms
I believe I chosed GSI+"Somting"
then the device rebbot with qualcomm screen and then the error apper
EranG90 said:
Sorry like I said before I am new at this
I have change somting in the DSU option. I think this was the Acronyms
I believe I chosed GSI+"Somting"
then the device rebbot with qualcomm screen and then the error apper
Click to expand...
Click to collapse
OK, If you used DSU to try out the Android 12 Developer Preview your bootloader needs to be unlocked, try running :
fastboot oem unlock
Bear in mind it will wipe the phone though, then reboot back into the Android 11 rom, set it up and THEN try DSU.
You need to have previously allowed bootloader unlocking in your developer options (see below)
djsubterrain said:
OK, If you used DSU to try out the Android 12 Developer Preview your bootloader needs to be unlocked, try running :
fastboot oem unlock
Bear in mind it will wipe the phone though, then reboot back into the Android 11 rom, set it up and THEN try DSU.
Click to expand...
Click to collapse
Thank you
I have run this command and waited 40 min with thoose screen and stop becuse I did't saw nothing in progressing.
It is good? Should I keep waiting? (I don't know really what to do, I don't know even if the device got the command from the pc)
EranG90 said:
Thank you
I have run this command and waited 40 min with thoose screen and stop becuse I did't saw nothing in progressing.
It is good? Should I keep waiting? (I don't know really what to do, I don't know even if the device got the command from the pc)
Click to expand...
Click to collapse
Thank you so mach
I fixed my Pc usb and done the command and unlock oem
now I got only bootloader in my device
the recovery and the start options reboot the phone to the bootloader only
What I need to do now do get androird 11 back to the device?
EranG90 said:
Thank you so mach
I fixed my Pc usb and done the command and unlock oem
now I got only bootloader in my device
the recovery and the start options reboot the phone to the bootloader only
What I need to do now do get androird 11 back to the device?
Click to expand...
Click to collapse
If you're stuck on bootloader only you can try running these commands in fastboot :
fastboot -w
fastboot --set-active=a
fastboot reboot
If the phone does not boot properly then try these :
fastboot -w
fastboot --set-active=b
fastboot reboot
"fastboot -w" wipes your userdata. The "fastboot --set-active" command tells the phone which A/B slot you want to use, "fastboot reboot" is the command to restart the phone.
If you just keep getting sent back to fastboot and it won't boot then you're likely going to have to use the MSM tool to restore the phone to factory settings.
djsubterrain said:
If you're stuck on bootloader only you can try running these commands in fastboot :
fastboot -w
fastboot --set-active=a
fastboot reboot
If the phone does not boot properly then try these :
fastboot -w
fastboot --set-active=b
fastboot reboot
"fastboot -w" wipes your userdata. The "fastboot --set-active" command tells the phone which A/B slot you want to use, "fastboot reboot" is the command to restart the phone.
If you just keep getting sent back to fastboot and it won't boot then you're likely going to have to use the MSM tool to restore the phone to factory settings.
Click to expand...
Click to collapse
Really really thank you
I have tried all 4 commands (-w, --setactive=a/b and reboot)
all of them after I turn off and back on my phone show me the bootloader
can you send me a link to how I use the MSM tool to restore the phone to factory settings?
You have a LE2120 so there is no msm package publicly available yet.
In the screenshots, it shows that your fastboot drivers are not installed. Did you fix that first? The command take less than a second to run.
craznazn said:
You have a LE2120 so there is no msm package publicly available yet.
In the screenshots, it shows that your fastboot drivers are not installed. Did you fix that first? The command take less than a second to run.
Click to expand...
Click to collapse
Yes all the commands are run very fast it is no longer whiting for device
and the device state is unlock
what can I do to get android 11 on my phone? I am really new in this
EranG90 said:
Yes all the commands are run very fast it is no longer whiting for device
and the device state is unlock
what can I do to get android 11 on my phone? I am really new in this
Click to expand...
Click to collapse
try
Code:
fastboot reboot fastboot
and what shows up?
https://forum.xda-developers.com/t/...u-via-msm-no-unlock-bin-needed.4272837/unread
You can download and take the flashall.bat from this conversion guide and download your version of oneplus9pro rom to your pc then use payload dumper to extract all images, then place the flashall.bat in the same folder as all your files you dumped then plug ur phone in(while it is on bootloader screen) and double click the flashall.bat
craznazn said:
try
Code:
fastboot reboot fastboot
and what shows up?
Click to expand...
Click to collapse
thank you for answring
that what show up:
Rebooting into fastboot OKAY [ 0.004s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Shooter7889 said:
https://forum.xda-developers.com/t/...u-via-msm-no-unlock-bin-needed.4272837/unread
You can download and take the flashall.bat from this conversion guide and download your version of oneplus9pro rom to your pc then use payload dumper to extract all images, then place the flashall.bat in the same folder as all your files you dumped then plug ur phone in(while it is on bootloader screen) and double click the flashall.bat
Click to expand...
Click to collapse
Thank you
I will try anything to fix that but I am new in all this
Where I am download the flashall.bat? where I save it? How to run it?
I have download the global version for onplus9pro. What I need to do with it?
https://androidfilehost.com/?fid=14943124697586337355
This is the link to the op's zip(he created for the thread for converting tmobile variants to EU). . Click the link and download the zip, put it on your pc, then u have to extract all files. The flashall.bat is one off the files in that zip.. Then Google search the Chinese version of tue latest op9pro OS11.. Get it on your pc. U have to use payload dumper(which you will need to search android get on ur pc, extracted as well). Then once u get payload dumper ready, and ur rom, take them payload.bin from ur rom folder and put it in the payload input folder. Then double click the payload.bin and it will slowly extract all your files and put them into the payload output folder. Once it's done take the flashall.bat and put it in there. Then ur ready to plug ur phone in(in bootloader mode) and double click the flashall.bat
Shooter7889 said:
https://androidfilehost.com/?fid=14943124697586337355
This is the link to the op's zip(he created for the thread for converting tmobile variants to EU). . Click the link and download the zip, put it on your pc, then u have to extract all files. The flashall.bat is one off the files in that zip.. Then Google search the Chinese version of tue latest op9pro OS11.. Get it on your pc. U have to use payload dumper(which you will need to search android get on ur pc, extracted as well). Then once u get payload dumper ready, and ur rom, take them payload.bin from ur rom folder and put it in the payload input folder. Then double click the payload.bin and it will slowly extract all your files and put them into the payload output folder. Once it's done take the flashall.bat and put it in there. Then ur ready to plug ur phone in(in bootloader mode) and double click the flashall.bat
Click to expand...
Click to collapse
And honestly, you could prob just download the zip I mentioned, the first one just to get the flashall.bat, and just extract it, plug ur phone in(in bootloader mode) and click the flashall.bat. It would put the EU version of OS on your phone. Use cld then use the loavl update in system settings to switch to ur variant after. Much easier.
Okay so when I flashed Magisk boot image my device activated boot problems. And when I tried to access recovery mode via adb (from Android Studio), my phone entered a bootloop from which I cannot exit.
Vol down + power buttons does not work. Neither does volum up + power. But when I press vol up+vol down+power my PC emits sound of connected device. I think that it is a problem of A/B partition, but I need to get to fastboot to fix it.
Any solution? I have already tried battery running out.
marcos_rgn said:
... my PC emits sound of connected device.
Click to expand...
Click to collapse
Yes, but what's it seeing?
You can poke around in Device Manager (View Devices by Connection can be helpful) and find which "device instance" is there.
You can also simply adb devices and fastboot devices to see if anything is there.
You could also try UsbLog.exe. Just run it and plug/unplug things.
.
Renate said:
Yes, but what's it seeing?
You can poke around in Device Manager (View Devices by Connection can be helpful) and find which "device instance" is there.
You can also simply adb devices and fastboot devices to see if anything is there.
You could also try UsbLog.exe. Just run it and plug/unplug things.
Click to expand...
Click to collapse
This is with usblog.exe.
I have checked and adb devices and fastboot devices are empty even while device is connected (in that 3 seconds window). I have runned some commands with "wait-for-device" and they didnt work.
So you have the MediaTek ROM bootloader there.
I've played with some of the MediaTek stuff (and even started to write a native Windows MTK client), but I'm no expert.
There are two modes, 0e8d/0003 (ROM) and 0e8d/2000 (preloader).
You might look here: https://github.com/bkerler/mtkclient
Try holding the VolUp while rebooting to try to get 2000.
I hope that you have a copy of your original boot? You can flash it back and see if things work.
It's always good to have a good recovery before you get deep in modification.
you can flash with this spflash tool to take back your phone.
SP Flash Tool v5.2044 Edited By Kurdish Gsm Team (Free Downlowd)
SP Flash Tool v5.2044 Modefiad Version With Auth Bypass Button
www.firmware4mobile.com
here is the video tutorial
Renate said:
I hope that you have a copy of your original boot? You can flash it back and see if things work.
It's always good to have a good recovery before you get deep in modification.
Click to expand...
Click to collapse
I have stopped boot loop by flashing boot.img and vbmeta.img with MTK client, thank you!
Generally speaking, if I want to return to default ROM, what files should I flash? What are the "software pieces" that Magisk touches and modify?
marcos_rgn said:
What are the "software pieces" that Magisk touches and modify?
Click to expand...
Click to collapse
Normally, Magisk only needs to have the boot image replaced.
The instructions tell you to optionally make the vbmeta inactive, but Magisk ignores all that verification anyway.