Related
hey, i fashed a new radio but apparently i had the wrong recovery img. i am stuck in a boot loop now cant get past it, not able to get to fastboot by pressing Back/Power key, or Vol/Power keys...
So is it finally DONE... Bricked i mean
any help d'be great
thx.
have the same problem and haven't found a solution yet..
Feels like that the unit is done... :-(
guess that the only solution is to get it JTAG flashed.. something "normal" users doesn't do.
Someone here at the forum had a similar unit but it wasn't the radio that was flashed when it went wrong.
He managed to get out of the boot loop by starting the computer with fastboot and "waiting for device".
Then he tried to connect the phone a couple of times.
After a while he managed to get the connection to work and fastboot to boot recovery.
I have tried this but with no luck....
Would like to see some Jtag information to this device.
What radio did you flash? And what hboot do you have?
When your phone is turned on, try connect with USB and type in CMD.
Code:
fastboot devices
and
Code:
adb devices
If your serial number pops up on (or both) of these, let me know, and I'll help you.
none of these will show me the device.
the radio I flashed was:
myTouch-radio-2_22_23_02.zip
Status right now is that the unit only shows boot logo.
Got no fastboot / hboot / revovery mode.
The only differense that works is to start with scroll wheel pressed, then it starts whit blank screen and blue led
(radio boot?)
Is it possible to replace radio with serial cable?
i have the same issue, but to be honest its kinda been fun and a learning curve wouldnt have done it unless i had a spare phone, but i think ill make up a serial cable this weekend and see what i can get out of the phone
More information can be found in this thread:
http://forum.xda-developers.com/showthread.php?t=533240&highlight=boot+loop
/Mippen
Not sure if this is related or not, but I had a similar issue when I recently flashed the new radio and still had the old recovery on my device.
I fixed it by pulling out the battery, unplugging the device and then putting the battery back to (to stop the constant reboots). Then I could hold the back key and power it on to get into fastboot. Once it booted up into fastboot I was then able to load the correct recovery via the "fastboot boot recoveryXYZ.img" command and boot the correcy recovery rom (in my case it was the hero recovery rom as I flashed the new radio).
After that I was able to flash the correct SPL and recovery to the phone, reboot and finally install my new rom
Hope this helps!
I'm stuck at the very first image that appears on Orange Boston and i can't boot normally and i can't enter recovery mode either :|.
I flashed Cyanogen mod 6.1.0 RC4 this morning.Everything went well till i installed Adobe Flash Player 10.1.I rebooted my phone i realised that my wireless couldn't find my wi-fi network that was right next to the phone .The phone was laggier to.Then i turned it off.And wen i turned it back it would be stuck.And even the recovery mode is stuck before it even starts up (.
With my luck in life i doubt they would believe me with a lame excuse at Orange.If any of you know a good way to start at least the recovery mode so i can back-up my previous rom them please help.I'm very Desperate i tried a lot of things.
B42iso said:
I'm stuck at the very first image that appears on Orange Boston and i can't boot normally and i can't enter recovery mode either :|.
I flashed Cyanogen mod 6.1.0 RC4 this morning.Everything went well till i installed Adobe Flash Player 10.1.I rebooted my phone i realised that my wireless couldn't find my wi-fi network that was right next to the phone .The phone was laggier to.Then i turned it off.And wen i turned it back it would be stuck.And even the recovery mode is stuck before it even starts up (.
With my luck in life i doubt they would believe me with a lame excuse at Orange.If any of you know a good way to start at least the recovery mode so i can back-up my previous rom them please help.I'm very Desperate i tried a lot of things.
Click to expand...
Click to collapse
what kind of phone and recovery image do you have? I'll try to help, but just out of curiosity, did you post this in YOUR phone's forum Q&A section?
It's Gigabyte Codfish and it's named Orange Boston.It has alot of names around the world like 20 or 30 :|.The Recovery image is the latest Clockworkmod Recovery since i had to use it for Cyanogen.
Sadly my Phones not listed anywhere in the forum.
The thing is everything started to lag and my wi-fi started malfunctioning after I installed Adobe Flash Player 10.1 and after 1 Reboot and 1 power-off then turn-ons it stopped.
My phone has 2 boot images.The first one's with orange sqares and the second one is the Orange Logo/Cyanogenmod Logo depending on what i flashed,but it stops at the first one with the orange squares.
This happens at the Recovery mode to.If i could at least start the recovery mod i would re-flash my old os and then fix the rest of the problems.
B42iso said:
It's Gigabyte Codfish and it's named Orange Boston.It has alot of names around the world like 20 or 30 :|.The Recovery image is the latest Clockworkmod Recovery since i had to use it for Cyanogen.
Sadly my Phones not listed anywhere in the forum.
The thing is everything started to lag and my wi-fi started malfunctioning after I installed Adobe Flash Player 10.1 and after 1 Reboot and 1 power-off then turn-ons it stopped.
My phone has 2 boot images.The first one's with orange sqares and the second one is the Orange Logo/Cyanogenmod Logo depending on what i flashed,but it stops at the first one with the orange squares.
This happens at the Recovery mode to.If i could at least start the recovery mod i would re-flash my old os and then fix the rest of the problems.
Click to expand...
Click to collapse
ok, so firstly (and don't be offended) you should never ever ever flash a rom that isn't supported in a forum for your phone! second, try holding volume down and power and see if you get the bootloader/fastboot and pm me/reply here again. third, why did you flash rc4 (not yet "stable") and WHAT PHONE IS IT FOR?
Nothing happens and it says nothing at startup so Volume down + power isn't the right one for mine.I know the recovery mode (camera button+volume up+power) and something i'm not sure what it is but it says exit ftm mode (camera buton+volume down+power).
Well i used rom manager and it's for my phone the Z71 phone models that includes mine too.exit FTM mode does the same thing it shows the same image at the start and only writes a little text at the top left saying "exit FTM mode".
I'm not offended I'm really angry at myself so np.And RC4 is way more stable then RC1 cause RC1 drained my battery very fast.Adobe FLash player 10.1 has to be the culprit.My phone started to act strange only after i installed it.Before it worked like a miracle with RC4.Maybe another method would be to reset the apps in the internal memory but i guess that requieres recovery mode too...
I got it!The fastboot mode for me is Volume down+End Call+Power.
It's showing the same image at the beggining BUT the usb is recognised .This means with some Command Prompt magic we might be able to restore the previous Clockwork mod recovery cause the original does not have any special options and i can't really use my backup.
It's night time here I'll await your reply,I'll be here after school.This could help alot of people cause i heard about this kind of problem before but no explanation was given on how to solve it.
B42iso said:
I got it!The fastboot mode for me is Volume down+End Call+Power.
It's showing the same image at the beggining BUT the usb is recognised .This means with some Command Prompt magic we might be able to restore the previous Clockwork mod recovery cause the original does not have any special options and i can't really use my backup.
It's night time here I'll await your reply,I'll be here after school.This could help alot of people cause i heard about this kind of problem before but no explanation was given on how to solve it.
Click to expand...
Click to collapse
well, that's good. just to clarify, you have gained access to fastboot right?
also, you never answered what phone the rc4 you flashed was for, so, what phone was it for?
here is a link to adb (command prompt) - which is again for cdma hero's, so the guide may be off a little, but see if it helps... http://forum.xda-developers.com/showthread.php?t=690362
I said it's for Z71 phone types.It's a group of .... how do i say....no name phones or not so famous phones that includes mine to.Rom Manager automatically downloads the right version for my phone.I already looked up what's "Z71 phones" on the cyanogen forums. I'm not sure if fastboot works properly i've never seen it before on this phone,but the usb cable is recognised and that means it has to work.I'll look at the guide now...
I plugged in the device in to a fresh laptop withouth drivers.It said "Android Sooner Single ADB Interface".On my pc it's recognised cause i had the software tools programe installed when i made the official update and it installed the drivers by itself.
I'm still trying to get adb list my device cause it's not appearing .Probably wrong drivers?
Edit: Beside this tutorial you gave me looks like one that works with a normal working phone.There's a part that asks fo USB Debugging enabled.It was enabled before it crashed and never started again but i doubt it counts now.
Edit: Never mind i'm stupid it's right under the first post .
God my phone scared the crap out of me :|.After playing with fastboot and trying to get is listed in adb devices,which is stupid cause i had to type fastboot devices instead.I plugged it out for a little time it turned off and id didn't show a thing after i plugged it back now it's frozen with a dark orange low battery icon.It's probably dead low.I'll wait for it.Ps: I've never seen that battery icon :| so i pray it's not another nuisance problem to deal with.
Edit:Now that i think of it.... it was around 35% battery and after the incident i used it un-plugged to trying to get something started.
Here's the real guide by the same guy for fastboot: http://forum.xda-developers.com/showthread.php?t=532719.
YEEEEYYYY!!!!
Rejoice Brothers and Sisters.Thx to GOD, il Duce's support with help and for giving me strenght to not be depressed i made it .
Ok so I entered Fastboot mode and started command prompt.Connected my device to my pc and i showed command prompt the directory of adb for me it was
"B:\android-sdk-windows\tools" i copied from my sd card my nandroid backup files for my old ROM and i put them inside the tools folder.Then i did the following in Command Prompt:
these should take some time and you have to do them 1 by 1
fastboot erase boot
fastboot erase recovery
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata data.img
fastboot flash recovery recovery.img
fastboot reboot
After reboot don't be scared like i was :| it's only stuck for a litle time because it's the first start up after the flash. That's all ^^.
Credits: il Duce,brandenk,nephron and Me for broking,experimenting and fixing my phone.
B42iso said:
Rejoice Brothers and Sisters.Thx to GOD, il Duce's support with help and for giving me strenght to not be depressed i made it .
Ok so I entered Fastboot mode and started command prompt.Connected my device to my pc and i showed command prompt the directory of adb for me it was
"B:\android-sdk-windows\tools" i copied from my sd card my nandroid backup files for my old ROM and i put them inside the tools folder.Then i did the following in Command Prompt:
these should take some time and you have to do them 1 by 1
fastboot erase boot
fastboot erase recovery
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata data.img
fastboot flash recovery recovery.img
fastboot reboot
After reboot don't be scared liek i was :| it's only stuck for a litle time because it's the first start up after the flash. That's all ^^.
Credits: il Duce,brandenk,nephron and Me for broking,experimenting and fixing my phone.
Click to expand...
Click to collapse
COOL glad you got it working! I don't really know how I helped, sounds like you did most of the work, but glad I could help
Warning! You were right that ****ing ROM is 1 of the culprits ^^.I couldn't help myself but to try it withouth Adobe Flash player.It lasts as long as you don't power-off and then trun your phone back on.
So this is confirmed.I'm too lazy to report this to Cyanogen u.u... or should I?
Well i succesfully restored my phone again.SO guys with Z71 phones out there don't use Cyanogen 6 RC4 YET,cuase you amy end up like me .
I reported this to Cyanogen.Btw I would laugh hard if this became a famous tutorial lol.
Hi I tried using the method to upgrade my motorola greco xt502 (z71, boston orange clone) to CyanogenMod 6 V6.1.0-RC4 for z71 and now cant even boot into clockworksmod recovery. it says entering recovery with motorola icon and stuck there.Please Help .
nand backup please
B42iso said:
Rejoice Brothers and Sisters.Thx to GOD, il Duce's support with help and for giving me strenght to not be depressed i made it .
Ok so I entered Fastboot mode and started command prompt.Connected my device to my pc and i showed command prompt the directory of adb for me it was
"B:\android-sdk-windows\tools" i copied from my sd card my nandroid backup files for my old ROM and i put them inside the tools folder.Then i did the following in Command Prompt:
these should take some time and you have to do them 1 by 1
fastboot erase boot
fastboot erase recovery
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata data.img
fastboot flash recovery recovery.img
fastboot reboot
After reboot don't be scared like i was :| it's only stuck for a litle time because it's the first start up after the flash. That's all ^^.
Credits: il Duce,brandenk,nephron and Me for broking,experimenting and fixing my phone.
Click to expand...
Click to collapse
happy for you, i have the same problem but i have no nand backup, i'm a noob, can you please upload a nand backup on mediafire or something like that?
saybron said:
happy for you, i have the same problem but i have no nand backup, i'm a noob, can you please upload a nand backup on mediafire or something like that?
Click to expand...
Click to collapse
Sorry man... this was ages ago, i don't have the files anymore, if I do have them then it's on my old desktop that's in another town and I won't be going there soon, cause i have university here.
thanks
B42iso said:
Sorry man... this was ages ago, i don't have the files anymore, if I do have them then it's on my old desktop that's in another town and I won't be going there soon, cause i have university here.
Click to expand...
Click to collapse
No problem, thanks man!
Hi,
I have refereed to earlier threads for same problem but could not resolve the issue. That's why I am initiating a new thread.
I was trying to unlock my htc one s and was trying to install a custom rom. But I don't know which step goes wrong. Now my phone is not starting and I am not even able to go to recovery mode by volume button. When I try to start the phone it stuck on 'this build is for development purpose only'.
Please help.
Regards,
Meher Chandan
It is kind of difficult to help since you are not telling what you have already done...
However, I'm just guessing that your phone may be in a reboot loop with fast reboot/poweroff enabled. This means it is never really powered off. Try to hold down the power button when you see the HTC screen, at least for 10 seconds (more may be required). That should force a hard shutdown. After that, you should be able to boot into fastboot, and so, into recovery.
FWIW, I've installed CM 12.1 and I still got the red warning message. It does not bother me, however.
I got similar case in the old day. Boot up the phone first to wakeup it and force it power off and immediately connect to PC when the screen goes blank.
Try "c:\>adb reboot bootloader" now, sometimes it will fail and report device not found(then unplug the usb cable, reboot it and power off and connect to PC again), you might be need to try many times to make it success(I'v tried like 10 times) and once you get it working, it will reboot into bootloader and now fastboot(c:\>fastboot devices) and recovery also working.
meherchandan said:
Hi,
I have refereed to earlier threads for same problem but could not resolve the issue. That's why I am initiating a new thread.
I was trying to unlock my htc one s and was trying to install a custom rom. But I don't know which step goes wrong. Now my phone is not starting and I am not even able to go to recovery mode by volume button. When I try to start the phone it stuck on 'this build is for development purpose only'.
Please help.
Regards,
Meher Chandan
Click to expand...
Click to collapse
There is boot.IMG file on your ROM.zip (you have installed) extract it in your fastboot folder and reboot your phone into boot loader and then goto your PC command promot and flash boot.IMG (fastboot flash boot boot.img) from fast boot folder.
Sent from my One S using Tapatalk
My phone is not rooted and I used it on normal basis. Last week my phone suddenly hang. When I tried to restart it enters a bootloop. The error is somehow bad, that I was not able to enter recovery mode or fastboot mode. I decide to disassemble the phone and disconnect the battery, it was then I was able to enter fastboot mode.
I decided to flash stock ROM using the fastboot mode. But to my horror, the batch seems to produce errors. The batch does erase the partition but when flash command write, it was erroneous,
I already follow every instruction from various forums. I wasn't able to find a proper forum that gives a satisfactory explanation on a correct fix and most of them were not logical. ex: Fixing a deadboot phone. The title is clear DEADBOOT, but as I read the instruction, it instructs me to wipe data and cache. Other instruct me to go into fastboot. This is total nonsense!!
Okay, now my phone is Deadboot. I was not able to enter recovery, enter fastboot mode, When connected to power, the LED is DEAD. Pressing the buttons will give no response in any way.
I tried flashing using QFIL using EDL mode but fail. Do anyone have any idea any logical sugestion to fix my superbricked phone?
Your help is appreciated and please no illogical or garbage answer. Thank you.
But your phone must be can to entering fastboot or recovery mode,If the situation is completely dead and cant access anything,sorry,that means its broken
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).