Related
Samsung I9103 Galaxy R Repair Dead By USB Cable no need JTAG NO Need Disassembly Phon
Download Links:X0X0X
Password:forum.sptbox.net
how to enter APX mode:
hold "vol up"+"home" then connect usb cable to dead phone
after repair done phone will auto in download mode
full flash it by Odin all will ok
Enjoy free dead repair soft now
=======================
---------------
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
iKevinShah said:
also for hard bricked phones :/ ???
Click to expand...
Click to collapse
If you can enter APX Mode then it's rescuablr
Herpderp Defy.
I have use this method and custom kernel = 0.
Nice work! But instruction is now enough full. It took about 3 hours of time to make sure that the phone worked.
Klajnor said:
I have use this method and custom kernel = 0.
Nice work! But instruction is now enough full. It took about 3 hours of time to make sure that the phone worked.
Click to expand...
Click to collapse
Do U mind sharing how to?
I'll try do it, but my english is bad. I thing will be difficult to understand what i mean.
Klajnor said:
I have use this method and custom kernel = 0.
Nice work! But instruction is now enough full. It took about 3 hours of time to make sure that the phone worked.
Click to expand...
Click to collapse
Could you tell what you did in a step by step manner, so that even the others facing the problem can use this method to solve it.
Mini step-by-step instruction:
0) Download and unpack archive to directory like c:\repair
1) Entering APX mode. Turn off phone. Hold Volume Up + Home buttons 10-15 second and plugin phone in usb port.
Install drivers from folder drivers in archive. After installing the device driver is defined as NVIDIA USB Boot-recovery driver for Mobile devices. It is mean that phone in APX mode.
You may try this method to enter APX mode: remove battery and unplug phone from PC. Hold Volumel Up + Home and plug phone to PC. Phone must be in APX mode now. Put buttery in phone.
2) Before do something do do nandroid backup. Copy it to PC.
Backup /efs to safe your IMEI.
3) Enter to APX mode, install driver and start GT-I9103.bat. If you have some errors - try again without rebooting phone. Or unplug-plug USB and try again.
Phone reboot in download mode.
4) Use Odin to flash ogiginal samsung ROM. I used сhinese ZCLA1 2.3.6. You must use PIT file to repartition file system of phone. p5.pit is on archive. If you try flash without PIT process will be fault.
5) When flashing finished load phone in recovery mode. Wipe /cache and try wipe /data.
Load android and format internal memory. Reboor in recovery mode again. Wipe all.
6) Now you have 100% work phone with custom counter equal zero, without yellow triangle and etc.
Take root and restore /efs to restore IMEI.
Take CWM, custom kernel and everything what you need.
Enjoy!
PS I have about 2-3 hours to sure phone work normal. If you know in advance - can be done in 15-20 minutes.
Google translate of my instuction( russian to english):
Training
0. Set unpack, better to go somewhere in the root directory, so in a way no spaces or other characters. But this is only a recommendation based on a small knowledge of Windows, I have a normal flash and the folder e: \ - = Samsung Galaxy R = - \ - = Dead Repair = - \
APX Mode
1.1 The largest shamanism - to be APX Mode. More or less reliable way, which I was able to do it - with the phone off hold down Volume Up + Home and plug the cord into the USB port. This method is reliable if the phone is alive.
If your phone firmware is broken (and it will be so if, immediately after the flash nvflash is not a normal firmware) - will have to catch this moment, because phone might try to get recovery (as it too may not be).
If you can not do it you can do: take out the battery, hold down Volume Up + Home and insert the cord into the computer. Once the phone is switched to battery mode APX return to the place, because flashing at a certain moment the phone off the USB port (just a guess, but without the flash batteries did not work).
1.2 After that, the phone went into the mode of APX, he determined on the computer as a device driver without APX. The driver is included. No problems with installation on Win 7 Pro SP1 x64 I do not have arisen. After installing the device driver is defined as NVIDIA USB Boot-recovery driver for Mobile devices. If you do so - then everything is fine.
2.1 What is necessary to have to start:
Actually set to restore the phone. He is quite self-sufficient.
Any firmware. I sewed the latest version of the Chinese I9103ZCLA1 2.3.6 firmware
Of course, Odin, the phone cord, and so you need to flash.
Be sure to make backup / efs. After nvflash IMEI, I folded to form 000004999900001 (well something like that, do not remember exactly).
If the actions are performed to reset the custom kernels - can be done at the beginning of nand backup. Yes, in general nand backup is needed in any case. Theoretically, such a scheme is possible: backup - nvflash - odin - cwm - restore. We get the phone in the same form but with zeroing counter. I am due to its krivorukost could not verify. In order not to repeat my mistakes - make a copy after the backup on your computer. It was quite unpleasant to lose all the settings over the last month (but then I blame myself, accidentally formatted the card).
2.2 Connecting the phone to APX to a PC, run GT-I9103.bat. If everything went without a problem - the script is complete without error and the phone goes into download mode. If there was a mistake - you can try again to flash.
For example when I have an error like in the image - just twitched and started the lace zanogo bat. I think if the phone was left in the mode of APX. My heart skipped a beat, but the second attempt the phone flashed fine.
Firmware
We sew a 3.1 firmware odin. Most importantly - do not forget to specify the file pit. It is a complete recovery. Bit to bit the same as there, that this firmware.
Without nutrition ask you not to succeed, because file system is a mess of half-dead sections. Sewed only some parts of the firmware. Once downloaded, the phone displays a picture of a bunch of Korean characters and English phrases like "Software update failure".
3.2 After the firmware partition / data, as I understand it, is not formed. I would suggest the following algorithm:
We go in and format the built-in recovery / cache.
Ship, and through him the android usb-format the drive. I then have to format it, just in case a recovery.
I do not know what will be if you try to install the firmware as soon as CWM, try to format all of them, and make recovery backup. I just have no backup at hand (accidentally formatted the same section of CWM / emmc and it was an external card, where to store my backups).
03.03 Well, after much room for activities. CWM and restore from backup or set up from scratch - you decide.
Conclusions:
When the curve could theoretically restore the firmware. Maybe even a bit boot-loader. I got the impression that the APX - a mode of the chip, not software. If iron is not dead - should help. In general, an hour and a half I have had the phone without a flash, probably the same at the time will resize partition to pull the cord and battery.
Resets the counter custom kernels, lost the yellow triangle. In general, if you flash the original firmware - can be easily dragged into service.
The method is not the easiest, there are many pitfalls, such as in the beginning, I forgot about the PIT, could not understand why the work is already in the phone memory is not working correctly, etc.
On the other hand, this method is not much harder than flashing the phone or through the odin cwm. Just add a few points.
Phone neubivaemy. Like my last samsung i780 (where I really made a mistake and did not start flashing in the sequence. And vykovyrivanie three parts of the firmware exe file - also had a very high risk). So much suffering in the firmware, but it is still alive. In general, I would say that acting on the instructions (or at least about following it) phone can not be killed. I love samsung for it.
Click to expand...
Click to collapse
Klajnor said:
Mini step-by-step instruction:
0) Download and unpack archive to directory like c:\repair
1) Entering APX mode. Turn off phone. Hold Volume Up + Home buttons 10-15 second and plugin phone in usb port.
Install drivers from folder drivers in archive. After installing the device driver is defined as NVIDIA USB Boot-recovery driver for Mobile devices. It is mean that phone in APX mode.
You may try this method to enter APX mode: remove battery and unplug phone from PC. Hold Volumel Up + Home and plug phone to PC. Phone must be in APX mode now. Put buttery in phone.
2) Before do something do do nandroid backup. Copy it to PC.
Backup /efs to safe your IMEI.
3) Enter to APX mode, install driver and start GT-I9103.bat. If you have some errors - try again without rebooting phone. Or unplug-plug USB and try again.
Phone reboot in download mode.
4) Use Odin to flash ogiginal samsung ROM. I used сhinese ZCLA1 2.3.6. You must use PIT file to repartition file system of phone. p5.pit is on archive. If you try flash without PIT process will be fault.
5) When flashing finished load phone in recovery mode. Wipe /cache and try wipe /data.
Load android and format internal memory. Reboor in recovery mode again. Wipe all.
6) Now you have 100% work phone with custom counter equal zero, without yellow triangle and etc.
Take root and restore /efs to restore IMEI.
Take CWM, custom kernel and everything what you need.
Enjoy!
PS I have about 2-3 hours to sure phone work normal. If you know in advance - can be done in 15-20 minutes.
Google translate of my instuction( russian to english):
Click to expand...
Click to collapse
Nice!
Now many people in this forum should be able to get their Galaxy R back to life from the dead thanks to you!
Just one suggestion brother, keep on monitoring this thread if any person has any doubts or is facing any problem while trying to solve using your instructions, you could help them better.
I am going to directly link this post in the FAQ section.
Cheers (with a bottle of super fine Russian Vodka) !
Great job Klajnor! молодец!
'cooleagle' said:
Nice!
Just one suggestion brother, keep on monitoring this thread if any person has any doubts or is facing any problem while trying to solve using your instructions, you could help them better.
Click to expand...
Click to collapse
Ок. I will monitor this theme when it possible
One suggestion: Volume Up + Home doesn't bring any effect. To enter APX mode I had to press Volume Up + Home + Power button. Interesting that this is the way to reach recovery on some Galaxy handsets.
Volume Up + Home + Power button - it is also work. I wrote Hold Volume Up + Home buttons 10-15 second and plugin phone in usb port. I thing this way is more reliable
Hi,tried the above method for I9103 but when i proceed the steps it shows the download mode initialzed and the window shuts up and the fone remain dead,no response on fone. Installed drivers for APX and Iam using XP Sp3.
What window shuts up? bat script? If you mean bat - then that normal. If you want see result of it work use cmd.exe to run script.
Turn on phone in download mode( vl_up + home + power or vl_up + home and plug phone in usb) and try flash any firmware via onid (don't remember use pit file from firmware or from repair folder).
After restoration, at me runs not into a downloading mode, and in mode NVFLASH Recovery Mode
Just to report, there is no APX mode on my SGR
Wait is it just black screen?
Yesss it is
how is that possible?
Any chance to create this for P7500 / P7510?
Guys, sorry for OT.
http://forum.xda-developers.com/showthread.php?p=25125344#post25125344
According for the thread link above, does this method helps to solve it?
Thanks for your attention
i want to reset my binary without jig can anyone guide me with proper steps & i dont want to ruin my phone
Hi all,
So I got soft bricked Samsung Galaxy S6.
Here are the issues:
- The person got it when he tried to root it
- Stuck in boot logo (Samsung S6, Powered by Android) and does not go further
- I can flash original firmware (Vodafone, Australia) through ODIN successfully, but the problem remains
- Cannot access recovery mode, tried to flash both stock recovery and custom (TWRP, all versions available at twrp.me)
- Have tried both Kies3 and SmartSwitch, emergency recovery went smooth, flashed successfully, but the problem remains
- After each successful flashing, I try to boot into recovery mode in order to clear cache, but it does not boot into recovery at all
- Tried all versions of ODIN and used all cables at home
- Another strange behavior, it can power on only when it is connected to cable. So it either stuck or can boot into Download mode when I press combination. But if I disconnect, after some time it switches off and cannot power on unless you connect it to the cable. Does it mean that the person ticked NAND erase as it is also related to energy dependency of the memory? I don't believe it to be battery issues as I saw this issue on another phone too (Samsung A9)
It is weird. I just want to understand, why I am not able to boot into recovery mode even after successful flashing stock ROM?
Any help is appreciated
Hi, I too have similar issue. Would like to know how you got it resolved.
tanzeeb210 said:
Hi, I too have similar issue. Would like to know how you got it resolved.
Click to expand...
Click to collapse
I could not solve it. Sold the phone for spare parts
Seems like motherboard issue
oscar_ferreiro said:
I could not solve it. Sold the phone for spare parts
Seems like motherboard issue
Click to expand...
Click to collapse
its seems like battery issue more for me than the board!
you should replace or disconect her first before selling the device... could worth the try...
oscar_ferreiro said:
Hi all,
So I got soft bricked Samsung Galaxy S6.
Here are the issues:
- The person got it when he tried to root it
- Stuck in boot logo (Samsung S6, Powered by Android) and does not go further
- I can flash original firmware (Vodafone, Australia) through ODIN successfully, but the problem remains
- Cannot access recovery mode, tried to flash both stock recovery and custom (TWRP, all versions available at twrp.me)
- Have tried both Kies3 and SmartSwitch, emergency recovery went smooth, flashed successfully, but the problem remains
- After each successful flashing, I try to boot into recovery mode in order to clear cache, but it does not boot into recovery at all
- Tried all versions of ODIN and used all cables at home
- Another strange behavior, it can power on only when it is connected to cable. So it either stuck or can boot into Download mode when I press combination. But if I disconnect, after some time it switches off and cannot power on unless you connect it to the cable. Does it mean that the person ticked NAND erase as it is also related to energy dependency of the memory? I don't believe it to be battery issues as I saw this issue on another phone too (Samsung A9)
It is weird. I just want to understand, why I am not able to boot into recovery mode even after successful flashing stock ROM?
Any help is appreciated
Click to expand...
Click to collapse
Same issue here, any idea to solve that? (I'm Brazilian, sorry for some typing wrong)
I don't opened the device (yet), but if is a battery issue, someone tried to fix?
My device is SM-G920I, i tried to flash this FW: G920IDVU3FQD1_G920IXSA3FQC3_XSA without sucess, i will try with a "pit" file that i've found here on XDA and update here, but until the moment, the problem remains
Update: The PIT file does not solved the problem, after this I decided to open the device and swap the battery, but the problem remained, i'm buying a new board today, i think this board can't be saved
I've had similar problem with my Note4. It would sucessfuly apply firmware via Odin but refuse to boot. (tried multiple times)
I then did a flash via SmartSwitch (takes forever) but the phone worked again.
any update for this ? i have the same issue
Hi, I've had a rooted android for a couple of years now. Today I wanted to run the new Magisk root so that I could use apps that prevent rooted phones from using them. Following the instructions here (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445) I went to SuperSU and clicked 'Wipe Root' which then sent my device into constant bootlooping.
I can only get the blue screen saying 'Odin Mode' and a big down arrow saying 'Downloading... Do not turn off target' or a constant bootlooping.
I followed the instructions here though when I have put the four BL, AP, CP and CSC files and click Start, all that happens is in the log on the left it says: <OSM> All threads completed . (succeed 0/ failed 0). From what I can make out, the Odin software on the laptop is not communicating at all with the Samsung S6 in Download mode.
Could someone please help!
bestfootie said:
Hi, I've had a rooted android for a couple of years now. Today I wanted to run the new Magisk root so that I could use apps that prevent rooted phones from using them. Following the instructions here (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445) I went to SuperSU and clicked 'Wipe Root' which then sent my device into constant bootlooping.
I can only get the blue screen saying 'Odin Mode' and a big down arrow saying 'Downloading... Do not turn off target' or a constant bootlooping.
I followed the instructions here though when I have put the four BL, AP, CP and CSC files and click Start, all that happens is in the log on the left it says: <OSM> All threads completed . (succeed 0/ failed 0). From what I can make out, the Odin software on the laptop is not communicating at all with the Samsung S6 in Download mode.
Click to expand...
Click to collapse
Had to come back and add on to my previous post - I sorted it. It was simply a driver issue... Make sure you download all the correct Samsung USB Drivers people if you're having similar issues...
I finally restored my Android to Stock Android (albeit the latest Android system 7.1).
Hi,
Just got my Mi4c and I was able to flash my recovery to TWRP by (ketut.kumajaya's twrp-3.0.2-0-libra-aqua-20161007.img). From there, I wiped all partitions and uploaded roms (MTP) for installation. However, when installing a rom, the installation finishes without errors but reboot always takes me back to TWRP. I've tried ketut.kumajaya's cm13, xiaobai112220's cm12.1 and AndropaX's Resurrection Remix N but the same thing happens. Under the mount menu System is unchecked.
Does anyone have a clue as to what the problem is, or any suggestions on how to debug the issue?
Any help is appreciated. Thank you!
hollyrogers123 said:
Hi,
Just got my Mi4c and I was able to flash my recovery to TWRP by (ketut.kumajaya's twrp-3.0.2-0-libra-aqua-20161007.img). From there, I wiped all partitions and uploaded roms (MTP) for installation. However, when installing a rom, the installation finishes without errors but reboot always takes me back to TWRP. I've tried ketut.kumajaya's cm13, xiaobai112220's cm12.1 and AndropaX's Resurrection Remix N but the same thing happens. Under the mount menu System is unchecked.
Does anyone have a clue as to what the problem is, or any suggestions on how to debug the issue?
Any help is appreciated. Thank you!
Click to expand...
Click to collapse
How about flashing a miui rom by using computer and flash again or change a TWRP？
Sakura_Sa233 said:
How about flashing a miui rom by using computer and flash again or change a TWRP？
Click to expand...
Click to collapse
Thanks for the suggestions.
I decided to try another TWRP first since it was the simpler of the two. I fastboot boot-ed an older version of TWRP (3.0.0) and then **** happened =(
When TWRP loaded, the touchscreen did not work. I reset the phone then to my surprise and excitement the CM alien appeared. But that was short-lived because after the rom fully loaded up the touchscreen still wasn't working and I am now stuck in the CM welcome screen (Power, Vol up and down buttons do). It seems like the touchscreen is now completely broken and no amount of resetting and re-flashing recovery would fix it.
Anyone have ideas for my current situation? T.T I'll probably be trying to get back to stock recovery to see if that helps at all
Don't panic, touchscreen should work inside the recovery after 5-10 minutes.
I suggest flashing TS TWRP, though.
http://www.teamsuperluminal.org/ts-twrp-2-8-7-2-mi4c/
Cozzmy13 said:
Don't panic, touchscreen should work inside the recovery after 5-10 minutes.
I suggest flashing TS TWRP, though.
Click to expand...
Click to collapse
Having gotten over the initial shock of possibly losing $100 in record time, I'm strangely calm and hardly hopeful at this point.
After leaving the phone for the night, the touchscreen never did return. I put the phone in EDL mode and MiFlash-ed it hoping to return to stock (libra_images_V7.1.4.0.LXKCNCK_20151209.0000.6_5.1_cn), to which MiFlash reported successful but the screen never lit up. The last few lines of the log are as follows:
Code:
[00000C60]COM10 131.68 ApplyPatch sector 12, offset 424, value NUM_DISK_SECTORS-34., size 8
[00000C60]COM10 131.68 ApplyPatch sector NUM_DISK_SECTORS-23., offset 424, value NUM_DISK_SECTORS-34., size 8
[00000C60]COM10 131.68 ApplyPatch sector 1, offset 48, value NUM_DISK_SECTORS-34., size 8
[00000C60]COM10 131.68 ApplyPatch sector NUM_DISK_SECTORS-1., offset 48, value NUM_DISK_SECTORS-34., size 8
[00000C60]COM10 131.70 ApplyPatch sector 1, offset 32, value NUM_DISK_SECTORS-1., size 8
[00000C60]COM10 131.70 ApplyPatch sector NUM_DISK_SECTORS-1., offset 24, value NUM_DISK_SECTORS-1., size 8
[00000C60]COM10 131.70 ApplyPatch sector NUM_DISK_SECTORS-1, offset 72, value NUM_DISK_SECTORS-33., size 8
[00000C60]COM10 131.70 ApplyPatch sector 1, offset 88, value CRC32(2,5632), size 4
[00000C60]COM10 131.70 ApplyPatch sector NUM_DISK_SECTORS-1., offset 88, value CRC32(NUM_DISK_SECTORS-33.,5632), size 4
[00000C60]COM10 131.71 ApplyPatch sector 1, offset 16, value 0, size 4
[00000C60]COM10 131.71 ApplyPatch sector 1, offset 16, value CRC32(1,92), size 4
[00000C60]COM10 131.71 ApplyPatch sector NUM_DISK_SECTORS-1., offset 16, value 0, size 4
[00000C60]COM10 131.73 ApplyPatch sector NUM_DISK_SECTORS-1., offset 16, value CRC32(NUM_DISK_SECTORS-1.,92), size 4
[00000C60]GetFactoryObject(1457): The specified service does not exist.(0x800704db)
[00000C60]SaveFlashResult(1478): The specified service does not exist.(0x800704db)
More than touchscreen, I've lost the entire display now. In its bricked state, the phone is most of the time undetected by the computer, and enters EDL mode only when it feels like. I've since been plugging and unplugging the phone hoping to catch it in that state again.
Thanks for the suggestion. Will give TS's TWRP a try if I can ever get the device to fastboot again.
hollyrogers123 said:
...
Click to expand...
Click to collapse
So, you only have edl now and it mostly doesn't work.
Does MiFlash detect the phone at least sometimes?
Maybe your download was corrupted, did you check the checksum?
Do adb devices and fastboot devices right after you plug the phone in and check for any life signs.
Does the charging led appear when you plug the phone in?
Did you use Windows 32 bit for flashing? I see that being a problem around the forums.
Try this to enter EDL.
I found this:
You don't have to open phone to make shortcut.
1: Turn off your phone, (must be charged at least 30%)
2: plug cable usb to PC
3: after that it is coming a very FAST two movement: Plug USB to phone and then Vol+ together with Vol- till it blinks red LED.
I did it and it works!! After this you can install driver and recognise your COM port. (Do it with driver signature disabled)
Good Luck!!
Click to expand...
Click to collapse
I avoid flashing using utilities just because I don't know what incopetent monkey programmed it and how it might randomly destroy my phone.
It you can't fix it and you bought it from a good store, return it claiming that you were prompted to update your software and it never booted back up.
Good luck!
Cozzmy13 said:
So, you only have edl now and it mostly doesn't work.
Does MiFlash detect the phone at least sometimes?
Maybe your download was corrupted, did you check the checksum?
Do adb devices and fastboot devices right after you plug the phone in and check for any life signs.
Does the charging led appear when you plug the phone in?
Did you use Windows 32 bit for flashing? I see that being a problem around the forums.
Try this to enter EDL.
I avoid flashing using utilities just because I don't know what incopetent monkey programmed it and how it might randomly destroy my phone.
It you can't fix it and you bought it from a good store, return it claiming that you were prompted to update your software and it never booted back up.
Good luck!
Click to expand...
Click to collapse
The md5 is correct.
Charging LED does not turn on.
fastboot and adb do not detect. lsusb sees it sometimes, most of the time the connection of the device makes lsusb hang with no output and immediately unfreeze the moment I unplug the device.
I'm using Windows 7 64-bit VM for MiFlash on a debian host.
Update:
Holding Vol+ and Vol- for about 1 minute DOES get the device edl!
But it seems the Linux host is causing problems when transferring the connection to the guest. Some qcserial process was using it and VMware disconnecting the device from it and connecting it in the Win 7 guest somehow screws it up. What I did ultimately:
1. Use the key combination to get the device into edl and detected by Linux
2. Connect device to the guest using VMware menu (and not work)
3. While device is connected to the guest, use the key combination to re-enter edl and this time it got detected in the Windows 7 guest!
Hopefully this helps someone who's facing the same issues with getting their device detected by VMs.
Managed to re-flash but I'm still stuck with the same black screen unfortunately.
Thank you once again!
hollyrogers123 said:
Managed to re-flash but I'm still stuck with the same black screen unfortunately.
Click to expand...
Click to collapse
What did you flash this time?
Can you get into fastboot at least now?
Cozzmy13 said:
What did you flash this time?
Can you get into fastboot at least now?
Click to expand...
Click to collapse
Not into fastboot. After the flashing completes successfully, I'm still unable to turn on the device, it seems to be stuck in edl mode. I've tried:
Lastest China Dev libra_images_6.12.1_20161201.0000.00_5.1_cn
Lastest China Stable libra_images_V8.1.2.0.LXKCNDI_20161120.0000.00_5.1_cn
and an older version libra_images_V7.1.4.0.LXKCNCK_20151209.0000.6_5.1_cn
hollyrogers123 said:
Not into fastboot. After the flashing completes successfully, I'm still unable to turn on the device, it seems to be stuck in edl mode. I've tried:
Lastest China Dev libra_images_6.12.1_20161201.0000.00_5.1_cn
Lastest China Stable libra_images_V8.1.2.0.LXKCNDI_20161120.0000.00_5.1_cn
and an older version libra_images_V7.1.4.0.LXKCNCK_20151209.0000.6_5.1_cn
Click to expand...
Click to collapse
I really don't know what could you do next..
You need trying install all from beginning.
Sorry, but you trying to install versions, that only compatible with devices, that was unlocked from xiaomi site. There a good instruction, but on Russian language. I also had a device with version that is newer than that version from witch you can unlock bootloader.
Try to install first version before 6.1.14 China.
1. Fastboot on phone.
2. Download any firmware before 6.1.14.
3. Unpack tgz and gz on PC.
4. Execute miflash.
5. Connect phone to PC.
6. miflash - Browse - folder with unpacked firmware - Refresh.
7. Choose flash all except data and storage
8. After uploading device reboot itself.
Next install custom recovery
1. fastboot on device.
2. Download TWRP 2.8.7.1 For MI4C EN v2.7z. In future you can upgrade it to 3.0.2.0, but special for Mi4c.
3. Open archive.
4. Connect phone to PC.
5. Open terminal from admin and execute recovery.bat from archive.
6. Simply press enter in terminal.
7. After all terminal itself would close and phone go to recovery.
PS: wait few minutes, its a problem with this version TWRP.
Maybe this can help you. Sorry my English far from good.
weter11 said:
You need trying install all from beginning.
Sorry, but you trying to install versions, that only compatible with devices, that was unlocked from xiaomi site. There a good instruction, but on Russian language. I also had a device with version that is newer than that version from witch you can unlock bootloader.
Try to install first version before 6.1.14 China.
1. Fastboot on phone.
2. Download any firmware before 6.1.14.
3. Unpack tgz and gz on PC.
4. Execute miflash.
5. Connect phone to PC.
6. miflash - Browse - folder with unpacked firmware - Refresh.
7. Choose flash all except data and storage
8. After uploading device reboot itself.
Next install custom recovery
1. fastboot on device.
2. Download TWRP 2.8.7.1 For MI4C EN v2.7z. In future you can upgrade it to 3.0.2.0, but special for Mi4c.
3. Open archive.
4. Connect phone to PC.
5. Open terminal from admin and execute recovery.bat from archive.
6. Simply press enter in terminal.
7. After all terminal itself would close and phone go to recovery.
PS: wait few minutes, its a problem with this version TWRP.
Maybe this can help you. Sorry my English far from good.
Click to expand...
Click to collapse
Thank you for your input.
I tried libra_images_6.1.7_20151221.0000.11_5.1_cn_b09dac70a0 but after flashing the same thing happens. The screen remains black and I cannot get it to fastboot at all.
Can you first access to twrp and restore stock firmware?
If not people wrote that the best firmware to unlock bootloader is 6.5.24 cn-en for fastboot. Maybe now it help. Try to install this version.
hollyrogers123 said:
Thank you for your input.
I tried libra_images_6.1.7_20151221.0000.11_5.1_cn_b09dac70a0 but after flashing the same thing happens. The screen remains black and I cannot get it to fastboot at all.
Click to expand...
Click to collapse
what you need is an older mi flash, 2015 Jun or something, that works! (with an official old fb rom)
And don't even think about flash all except storage! just flash ALL!! Then let the phone boot fully at least once.
also, when ib edl mode (press vol- and power for a looonf time) or in fastboot mode you need to plug the phone to a computer with usb cable - try to put it in a different usb port, and different good quality cable is a must! once in edk or fb, you must open command prompt and type: fastboot devices - or press refresh in miflash, otherwise the phone won't stay in those states!
If you can't fix it with all this help found on Internet, then it must be hardware error!
oh, and golden f rule n1: - After flashing twrp always boot from it too! 1. fastboot flash recovery twrp. img
2. fastboot boot twrp.img
3. then un twrp reboot to recovery
i recently have same issue like you, i try to flash many rom and new room via fastboot, but realize that after flash rom via twrp, just boot to fastboot then reboot and you will boot to system
sry for my bad english
Hey guys,
decided to flash the latest DBT Firmware via Odin to get back to stock completely. (G930FXXU3ESA3)
After flashing the firmware through Odin the phone reboots and then installs an update and erases data (blue background).
After a second reboot I end up with a blue screen and the simple error: "No command".
I can not get into recovery, as I end up with the same error message wether booting into recovery or the system.
I CAN however get into downloadmode and flash twrp, after that I can boot into system but I want to keep the whole system vanilla, without TWRP.
Installing TWRP keeps the device encrypted, no matter what. I can wipe, then install no-verity-encrypt and as soon as I reboot the device is encrypted again.
Ive tried: Different Firmware Version (December 2018), 3 different cables, different odin versions.
Edit: attached an Image of the message that Pops up after about 30sec on the no command screen.
Ok, so your device will take UK Unbranded BTU firmware. You can get it from a few sources and even direct from Samsung servers with Samtool.
Forget all that flashing TWRP and non verify nonsense, if you can get into download mode you can flash firmware, obviously make sure the firmware downloaded is not corrupt etc.
I've used Odin V10 -13 to flash BTU and every version flashed it correctly. Sometimes you do get that "installing update" and then "erasing" but that's fine just leave the phone for a few minutes it should eventually reboot normally.
FLASH No verity.zip
VIA TWRP
https://forum.xda-developers.com/attachment.php?attachmentid=4490455&d=1525176288
cooltt said:
Ok, so your device will take UK Unbranded BTU firmware. You can get it from a few sources and even direct from Samsung servers with Samtool.
Forget all that flashing TWRP and non verify nonsense, if you can get into download mode you can flash firmware, obviously make sure the firmware downloaded is not corrupt etc.
I've used Odin V10 -13 to flash BTU and every version flashed it correctly. Sometimes you do get that "installing update" and then "erasing" but that's fine just leave the phone for a few minutes it should eventually reboot normally.
Click to expand...
Click to collapse
Just tried the latest BTU with Odin 3.13.1, same problem. Its reboots into the blue screen, applying system update to about 32% and then switches to "Erasing". After about 1min it reboots, shows "Installing System update" for a second and I end up with "No command" again. And from there on it just constantly reboots into the "No command" screen.
This seems like the same problem. I can not enter stock recovery to wipe though...
Things ive tried so far:
- Different firmware Versions (all oreo since downgrading is impossible)
- Formating with pit files
- Different Odin Versions
- Unplugging and replugging the battery
- Installing TWRP, wiping data and then installing stock recovery through TWRP
Did u try in Odin nand erase and repatition option? If not try it ( make sure u have pit file extracted or downloaded from the net)
Scorpionea said:
Did u try in Odin nand erase and repatition option? If not try it ( make sure u have pit file extracted or downloaded from the net)
Click to expand...
Click to collapse
Did a efs backup through TWRP just in case, then flashed the latest DBT firmware with nand erase -> still the same problem.
I can only guess that this was caused by using a backup from another phone back when Oreo came out, this probably messed something up really badly. Very weird, im kinda lost.
Killuminati91 said:
Just tried the latest BTU with Odin 3.13.1, same problem. Its reboots into the blue screen, applying system update to about 32% and then switches to "Erasing". After about 1min it reboots, shows "Installing System update" for a second and I end up with "No command" again. And from there on it just constantly reboots into the "No command" screen.
This seems like the same problem. I can not enter stock recovery to wipe though...
Things ive tried so far:
- Different firmware Versions (all oreo since downgrading is impossible)
- Formating with pit files
- Different Odin Versions
- Unplugging and replugging the battery
- Installing TWRP, wiping data and then installing stock recovery through TWRP
Click to expand...
Click to collapse
Ok, from the no command screen do the following.
Hold power until phone switches off, then press power+home+volume up. The phone should now boot into original recovery screen. Select "wipe/factory reset" and then reboot device. Job done.
cooltt said:
Ok, from the no command screen do the following.
Hold power until phone switches off, then press power+home+volume up. The phone should now boot into original recovery screen. Select "wipe/factory reset" and then reboot device. Job done.
Click to expand...
Click to collapse
Tried that, recovery is simply not working. If I hold vol - + power + home to restart and switch immediatly to vol + I boot into the usual blue screen with No command. I even tried unplugging the battery to shut off the phone and boot into recovery from there but that is not working either. Sorry should have stated that more clearly.
If I flash TWRP however, I can easily boot into TWRP with the recovery button combo.
Killuminati91 said:
Tried that, recovery is simply not working. If I hold vol - + power + home to restart and switch immediatly to vol + I boot into the usual blue screen with No command. I even tried unplugging the battery to shut off the phone and boot into recovery from there but that is not working either. Sorry should have stated that more clearly.
If I flash TWRP however, I can easily boot into TWRP with the recovery button combo.
Click to expand...
Click to collapse
Ok it's a tricky one so one more thing I would suggest is download and install Samsung smart switch on your PC, place the phone in download mode plug it into lap top and choose emergency software recovery in smart switch
Edit. I just remembered before that try this button combo from the no command screen volume up+volume down+power.
cooltt said:
Ok it's a tricky one so one more thing I would suggest is download and install Samsung smart switch on your PC, place the phone in download mode plug it into lap top and choose emergency software recovery in smart switch
Edit. I just remembered before that try this button combo from the no command screen volume up+volume down+power.
Click to expand...
Click to collapse
Hmmh. Searched a lot for the version that still supported emergency recovery. (which seems to be 4.0). If I go into download mode, start smartswitch and try to use emergency recovery there is nothing for me to select.
Volume up + down and power gives me the terminal like look which I attached in the first post with all those error messages.
Killuminati91 said:
Hmmh. Searched a lot for the version that still supported emergency recovery. (which seems to be 4.0). If I go into download mode, start smartswitch and try to use emergency recovery there is nothing for me to select.
Volume up + down and power gives me the terminal like look which I attached in the first post with all those error messages.
Click to expand...
Click to collapse
The EFS partition is corrupt or blank, it's the only logical explanation but the TWRP back up should solve that, without looking at it my self and running some commands i cant help your further.
cooltt said:
The EFS partition is corrupt or blank, it's the only logical explanation but the TWRP back up should solve that, without looking at it my self and running some commands i cant help your further.
Click to expand...
Click to collapse
TWRP backup was created after I ran into problems though. Ive checked some more things and it seems like the serial number that is displayed (in combination rom and or Z3X) is not the same SN that is printed on the back of the phone. Could this be related? And how would I go about changing it back to the one on the sticker? The IMEI is correct.
Had someone who was more into the whole thing contact me here but when I wanted to "donate" only half of what he was asking he refused to help me.
Killuminati91 said:
TWRP backup was created after I ran into problems though. Ive checked some more things and it seems like the serial number that is displayed (in combination rom and or Z3X) is not the same SN that is printed on the back of the phone. Could this be related? And how would I go about changing it back to the one on the sticker? The IMEI is correct.
Had someone who was more into the whole thing contact me here but when I wanted to "donate" only half of what he was asking he refused to help me.
Click to expand...
Click to collapse
Thats because he's a scammer. Never donate to get your phone fixed! Donate to Rom developers and things you like but never to get the phone fixed, they're usually lying.
The serial number should be the same ON the phone as displayed IN phone. Tell me the story about the phone, how did you get it? what region? where are you? what firmware was installed? Can you still flash a ROM with TWRP? Can you check OEM unlock?
---------- Post added at 04:53 PM ---------- Previous post was at 04:51 PM ----------
nmnmnmnmnmnmnmnmnm
Pretty sure he was just trying to remote repair for a price, which is not allowed on XDA. Would obviously donated on my own if he actually fixed it.
Bought the phone unlocked directly from a provider (simply - germany - dbt - g930f) back in 2016. Tripped kn0x after a few months, installed a few custom roms until Oreo came out.
This is where I messed up I think: I used a TWRP backup from someone else that he had shared here on XDA, which probably included his /efs too.
Since then I had constant connection problems, weak internet connection, dropped calls and so on.
Broke my screen and then decided to repair it myself. Bought a new frame, screen, battery, usb-port, earpiece and vibrator - managed to assemble all of that.
I can install all latest official firmwares (bootloader 3) through Odin. If I leave it at that I have no recovery and end up with the initially shown screen and "No command".
If i install TWRP from there and simply root with magisk or apply dm-verity-fix I can boot into the stock firmware with everything working.
I can also install ROMs. Just going completely vanilla is not possible anymore. OEM Unlock is checked, USB debugging works.
Edit: What is also astounding: If I flash version DBT-G930FXXS3ERHD-20180918145033 (oldest possible Oreo Version) I can enter recovery and do a factory reset and wipe cache.
If I do that however I am stuck at the Galaxy S7 Logo, not even bootlooping.
Killuminati91 said:
This is where I messed up I think: I used a TWRP backup from someone else that he had shared here on XDA, which probably included his /efs too.
Click to expand...
Click to collapse
awww.....come on man you should have said this at the start! Of course you can't use someone else's EFS data, it's unique to your handset. Custom Rom's patch some but not all EFS data that's why they work and in your case that's why Stock firmware isn't going too.
Anyway if this is the problem (and i suspect it is) there is only one way to fix it with Octopus box which can write all the important info back onto the EFS. Your IMEI, Serial, Mac address etc. Odin reads the info from the EFS prior to nand write start, if the phone serials don't match it will always fail at some point.
You can install a custom via twrp but it will not work correctly due to EFS data miss match. Octopus box is your answer.
cooltt said:
awww.....come on man you should have said this at the start! Of course you can't use someone else's EFS data, it's unique to your handset. Custom Rom's patch some but not all EFS data that's why they work and in your case that's why Stock firmware isn't going too.
Anyway if this is the problem (and i suspect it is) there is only one way to fix it with Octopus box which can write all the important info back onto the EFS. Your IMEI, Serial, Mac address etc. Odin reads the info from the EFS prior to nand write start, if the phone serials don't match it will always fail at some point.
You can install a custom via twrp but it will not work correctly due to EFS data miss match. Octopus box is your answer.
Click to expand...
Click to collapse
Dang it. Thank you! Off to find someone who can do this via remote access or in Berlin.
Same situation right now with my S7. Damn.
Hi everyone. Did you guys find any way to resolve this issue? i have exactly the same issue here.. but in my case i cannot use twrp cuz i never installed it before... the issue happened right after i tried to enter the recovery mode by pressing the buttons...
my wife's galaxy s7 touch screen was acting weird and i tried to get into the recovey mode..which is pretty muh easy to do... but once i tried the no command msg came up and now i have exatly the same case as the guy that opened this thread....also done everything hes done....any clue about this anyone?
id appreciate some help..
thanks in advance
Diego Boffa
Anyone?
I have exactly the same error with "fail to open recovery_cause(No such file or directory)#
My Tablet is now stuck with a blue "android dead" screen saying "No command".
My history to disaster:
- i've recovered a "broken" Samsung Tablet (sm-T585) with corrupted file system via
* Download Mode works -> TWRP install -> Mount option -> use ADB to recreate EFS partition -> re-flash stock image (android 8) with odin
- device works fine
- then i've noticed it can only be used with a certain cell provider (o2)
- then i've tried to flash an older version of the stock rom (android 7) due some problems in Android 8 (often some slow downs while operating)
- this doesn't work, the flash don't start
- therefore nothing should be happend, or?
- then i've can't get anymore in the stock recovery to wipe all data
...therefore the mess began:
* i can't flash TWRP anymore
* i can't flash stock recovery anymore
* i only can get into download mode
* i can only flash a certain rom type successfully (green PASS within odin), but with the final stuck with boot loop, with the mentioned blue screen
* other rom version can't flashed
I hopefully ask you guys here, if anyone can help me?
Any help would be very appreciated ...
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).