Database Info

[Q] Can't unbrick. Tried nigh everything.

Greetings! First of all, I would like to thank anyone who takes the time to help me diagnose and resolve this issues, let alone anyone who takes the time to read this thread.
I've been having issues with my Xoom (ICS 4.0.0) for about 3 weeks now.
A brief history of the issue's occurrence:
-I unrooted the device and returned it to stock.
-Everything was fine and dandy until one day it spontaneously said something along the lines of 'Android is upgrading..', and then performed a reset.
-Since resetting, it bootloops.
The device only turns on when plugged into a charger and hard reset.
The device only turns off when allowed to boot loop for minutes and then hard reset (it simply does not reset, and just turns off).
I'm not the most technically-savvy person with android devices but here are some things I've done/noted.
When trying to use adb commands, it does not recognize the device or properly issue commands.
I've tried wiping data/clearing cache to no avail.
EDIT: I've tried fastbooting, but the bootloader will not unlock. When trying to unlock, it simply resets and then acts as though it was never unlocked.
I have no idea how to return it to a stock image. All I know is that I have a micro-SD and some spare time.
Could anyone help me understand what exactly is going on with my Xoom?
If I can provide you with any more information, please let me know.
Thanks again. (=

If it was stock and spontaneously upgraded it sounds like a bad OTA upgrade. I've been rooted from the start so never have taken an OTA upgrade...don't you need to accept it or can it just upgrade on it's own?
Anyway, can you get it into fastboot mode?
Volume up and power, then at dual core screen, press volume down...if you see something like "entering fastboot mode" you're not bricked. You do not have to re lock your bootloader. Just make sure you have downloaded the correct stock files for your Xoom model to your PC and flash it.
If you haven't done so, just google 'recovering Xoom using fastboot' and you should get some good information.
Good luck!

Remember to grab the MZ604 files if you have the Wifi only version of the Xoom.
http://developer.motorola.com/products/software/ <------ Grab the files here. The files are for the US version of the Wifi Xoom only.
Instructions to return it to stock
1) First you need the Moto Drivers - Read this thread to START you - http://forum.xda-developers.com/showthread.php?t=981578
Should have these drivers installed if you have rooted your Xoom before.
2) Make sure you have the latest SDK - adb and fastboot should be in /platform-tools -
http://developer.android.com/sdk/index.html
Should have the android SDK if you have rooted your Xoom before.
3) Place all the downloaded stock image files into the SDK Tools folder.
4) If you are booting up from scratch, you can get the Xoom in fastboot mode by doing the following. Use command prompt to perform the rest of the steps
Hold VolDown and Power button will boot unit for fastboot mode
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
If you Xoom is booted up already follow the commands below using command prompt to perform the steps
adb reboot bootloader <---- reboots the Xoom into fastboot mode.
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
As Always If This Was Helpful Hit the Thanks!

Yeah, what Mjamocha said...

okantomi said:
Yeah, what Mjamocha said...
Click to expand...
Click to collapse
LOL Thanks.

okantomi said:
Anyway, can you get it into fastboot mode?
Click to expand...
Click to collapse
Yes, I can. But so far nothing has been successful in terms of fastboot commands.
okantomi said:
You do not have to re lock your bootloader. Just make sure you have downloaded the correct stock files for your Xoom model to your PC and flash it.
Click to expand...
Click to collapse
When I try to execute fastboot commands such as 'fastboot flash boot boot.img'.. it says the following:
Device still locked. Device must be unlocked first. Failed to process command error(0x8)
Whenever I try to unlock the bootloader, it appears to be successful at first and then the device reboots. But it just reboots to a bootloop, and the bootloader still says its locked. Perhaps I made a mistake in communication. The bootloader is currently locked and will not unlock, as just described.
When I try to unlock it and it reboots, even if I access the fastboot menu right away, it still says the device is still locked.
Thoughts?

Can you get into recovery? With the Xoom off (to make sure it's really off, hold volume up + power for a few seconds), hit the power button and when you see the M logo, wait a very brief moment (like a fraction of a second) and hit the volume down button. When it says "recovery" on the top left, hit the volume up. If you can get in there, either restore a nandroid (if you have one) or do a factory reset.

slacka-vt said:
Can you get into recovery? With the Xoom off (to make sure it's really off, hold volume up + power for a few seconds), hit the power button and when you see the M logo, wait a very brief moment (like a fraction of a second) and hit the volume down button. When it says "recovery" on the top left, hit the volume up. If you can get in there, either restore a nandroid (if you have one) or do a factory reset.
Click to expand...
Click to collapse
Yes, I can get into android recovery. However, within a second of switching into recovery mode, the robot falls down and there appears to be a red triangle caution sign containing an exclamation point.
When trying to do a factory reset, it says all data is wiped (as normal). Upon rebooting, it continues to bootloop. So essentially the factory reset and cache clear options in the Android Recovery menu do not produce the expected results.
Pretty odd. I didn't mess with the Xoom at all prior to this issue.

Try flashing just a recovery img to hopefully get your recovery working again. I think you can flash a custom recovery even if the bootloader is locked (i could be wrong but worth a shot) I attached the Rogue "recovery-rogue-1.3.0.img". Try a "fastboot flash recovery recovery-rogue-1.3.0.img"
EDIT: Sorry, I guess you can't flash a custom recovery with a locked bootloader.

slacka-vt said:
Try flashing just a recovery img to hopefully get your recovery working again. I think you can flash a custom recovery even if the bootloader is locked (i could be wrong but worth a shot) I attached the Rogue "recovery-rogue-1.3.0.img". Try a "fastboot flash recovery recovery-rogue-1.3.0.img"
EDIT: Sorry, I guess you can't flash a custom recovery with a locked bootloader.
Click to expand...
Click to collapse
Yeah, just tried it to no avail. Thanks so much for your help anyway. (=
I'm not sure what to do now.

I would keep trying to unlock it using different USB cables and different USB ports on your computer. I've had unlocks fail a bunch of times and for some reason, it was because of a $hity USB cable and/or a bad port on my computer.

slacka-vt said:
I would keep trying to unlock it using different USB cables and different USB ports on your computer. I've had unlocks fail a bunch of times and for some reason, it was because of a $hity USB cable and/or a bad port on my computer.
Click to expand...
Click to collapse
I hear ya. I've tried 2 different cords and 3 different computers. I'm using a Mac (10.6.8) right now, but have used 2 PCs (Vista + 7).

Out of curiosity, when you tried to flash the custom recovery, did you get the same "device still locked" error or did it appear to flash but then recovery failed?

slacka-vt said:
Out of curiosity, when you tried to flash the custom recovery, did you get the same "device still locked" error or did it appear to flash but then recovery failed?
Click to expand...
Click to collapse
I got the 'device still locked' error. Weird, huh?

How about trying to lock it again even though it says it's locked -maybe it's stuck in an "in-between state"? Try a "fastboot oem lock" and if it finishes then try a "fastboot oem unlock". I know, I'm grabbing at straws here. I thought I bricked my Xoom last week. All I did was an "adb reboot bootloader" and the device went to a black screen. Volume Up + Power did nothing. I ended up buying a T5 (Torx 5) bit at the store, removed the back cover and disconnected the battery for 30 seconds using a piece of paper to separate the contacts. The Xoom booted right up after that.

slacka-vt said:
How about trying to lock it again even though it says it's locked -maybe it's stuck in an "in-between state"? Try a "fastboot oem lock" and if it finishes then try a "fastboot oem unlock". I know, I'm grabbing at straws here. I thought I bricked my Xoom last week. All I did was an "adb reboot bootloader" and the device went to a black screen. Volume Up + Power did nothing. I ended up buying a T5 (Torx 5) bit at the store, removed the back cover and disconnected the battery for 30 seconds using a piece of paper to separate the contacts. The Xoom booted right up after that.
Click to expand...
Click to collapse
Yeah I tried that. Won't lock or unlock successfully. Locking produces no difference, and unlocking produces the same 'device still locked' error. This is getting out of hand! Thanks so much for your advice. You think I should open it up?

I hate to be so persistently annoying about this, but could anyone possibly suggest a method of working around the locked bootloader?
Is there anything I can do with an SD card to remedy the device's stubborn foolery?

I think you should give it a try, I have bricked my xoom a few times and have always been able to flash the stock imagine to recover. You really have nothing to lose by pulling the battery pin just be careful.
Sent from my Xoom using xda premium

I don't know if I'm technically-equipped enough to do that. )=
Sounds easy, but I imagine it would be rather easy to screw something up? Essentially what I should do is unseat the battery, right?

cherlamperter said:
I don't know if I'm technically-equipped enough to do that. )=
Sounds easy, but I imagine it would be rather easy to screw something up? Essentially what I should do is unseat the battery, right?
Click to expand...
Click to collapse
I have looking for a utube how to guide but no luck, I just might make one for you so you will know what to expect. Give me a few and I will get back to ya.
Sent from my Xoom using xda premium

Officially desperate. Please help. Will pay in form of just about anything.

Hi all,
Here is my sad saga.
Today, I decided I wanted to move up to ICS. I had 2.3.4 on a Koodoo phone that I decided was ready for the brave new world of ICS (bought it off Kijiji, now running it on Rogers which means I have no option of bringing it into a shop).
Ran into some issues but some good folks saved my butt in a number of tough spots. However, my grave seems to have been dug deeper by the minute. Essentially, I have managed to upgrade to 4.0.3. but am stuck with no 3G connection, hence no phone signal. This is a HUGE issue since I require my phone for work (foolish move #1 of the night).
Here are things I have tried and the challenges I have faced thus far:
1) CWM. Have not been able to access it or install it successfully. However have somehow managed to root the device. I did it through a one-click root/CWM tool I found online but have never been able to access CWM from the recovery screen, only stock recovery.
2) Changing the radio baseband version. Fail, since I have no CWM. Or Root Explorer because...
3) I can't access the google Market as I have no data connection. And did I mention no wireless? I live out in a rural area (sad story #1). It's ethernet only, sadly
4) Also, I have very limited access to a PC. I do have one at work, but I have my own macbook. Although I could use the PC at work to try some stuff out, I can't be spending my entire day Googling for help. Seems like employers would frown greatly on it. I've already spent a solid 4 hours on the forums and Internet tonight trying to find something that works. Absolutely no dice.
5) Attempted to get back to 2.3.6. No joy. Phone won't budge from 4.0.3. and I think it has to do a huge part with no CWM.
6) Factory reset a number of times. Still stuck on 4.0.3. with no 3G connection.
7) Reset APNs to default. Still no luck. Perhaps it isn't the radio baseband after all?
8) Also tried entering and leaving airplane mode a number of times. Zero luck.
9) I have a pretty low comfort level with PCs to be honest. I am open to all instructions, as long as they are detailed and written For Dummies.
Please help. I really, truly do not know what else to do or where else to turn but the forums. I've tried everything I could think of and I'm afraid this will impact my job since I need to be in constant phone contact for work. I'm exhausted from stress and worry. I swear this will be the last time I experiment with my phone (I know I've said it before, but this time I MEAN it!)
Thank you all you kind-hearted folk out there for anything you can do to help.

first cell phone model you have and that you had changed baseband before all ... You can also try a new version of CMW in case, can also be kernel problem that uses TO in the mobile ...

So you have a nexus with barely PC access running ics minus a recovery. Good news is your in luck. You need proper tools to do the job. Easiest method is either on that Mac or at work, install the phones drivers. search Google for the fastboot binary for the operating system your using. Once the drivers are installed boot to fast boot not recovery but the screen where you choose recovery. Open a terminal on the PC and type fastboot devices. No period. Should return a serial number on the screen. Your good to go. When you download the fastboot program, put it in a folder on the PC. Also put cwm for your phone in a .img format not a .zip. That should give you a name like cwm-2.5.5.0.img. When you open the terminal, navigate to the folder with both files. After typing fastboot devices and seeing the number type fastboot flash recovery cwm-and-whatever.img
That should give you cwm.
Also you got root have you tried downloading rommanager apk from the net putting it on the sd then installing. Once it installs try to flash recovery from the app
Sent from my Galaxy Nexus using Tapatalk 2

You have to relax first lol. When you're panicky nothing gets done so calm down. Do what the guy above says. Install cwm with fast boot. First install the android sdk then get the drivers. Get fast boot file down as well. Remember that the command fastboot flash whatever varies from operating systems.
With cwm installed, do a test. Backup your efs folder , which is essentially extremely important. You would better do a nandroud backup. Then, try various radios. See if that's your issue. If not change to trying out new roms . Worse case scenario go back to your 2.3.6 rom by flashing with cwm or install cyanogen mod 7.
Best of luck
Sent from my Nexus S using Tapatalk 2

dreamsforgotten said:
So you have a nexus with barely PC access running ics minus a recovery. Good news is your in luck. You need proper tools to do the job. Easiest method is either on that Mac or at work, install the phones drivers. search Google for the fastboot binary for the operating system your using. Once the drivers are installed boot to fast boot not recovery but the screen where you choose recovery. Open a terminal on the PC and type fastboot devices. No period. Should return a serial number on the screen. Your good to go. When you download the fastboot program, put it in a folder on the PC. Also put cwm for your phone in a .img format not a .zip. That should give you a name like cwm-2.5.5.0.img. When you open the terminal, navigate to the folder with both files. After typing fastboot devices and seeing the number type fastboot flash recovery cwm-and-whatever.img
That should give you cwm.
Also you got root have you tried downloading rommanager apk from the net putting it on the sd then installing. Once it installs try to flash recovery from the app
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Follow dreamsforgotten's instructions should get you out of the problem.
And yeah, relax.

You flashed the wrong ROM. the i9020a never got 4.0.3, it went straight from 2.3.6 to 4.0.4. you flashed a ROM for the i9020/i9023. This means that you have a US modem, a problem with those in the gingerbread days is that if you toggled 3G off, you lost it.
Now, I'm not 100% sure this will fix your issue, it *will* bring you back to proper stock image for your phone. Also, keep in mind, that you are responsible for anything you do to your phone, I in no way take any responsibility.
Instructions are for windows
Start by downloading the factory image:
Factory image for your phone
(ref) https://developers.google.com/android/nexus/images
Uncompress this file, you will need the following files:
Image-sojua-imm76d.zip
bootloader-crespo-i9020xxkl1.img
radio-crespo-i9020uckj1.img
Put these all in a folder, you'll need them shortly
Now you need to connect your phone to the computer. follow this guide, part 1 ONLY:
http://forum.xda-developers.com/showthread.php?t=1007782
You should still be in the bootloader when you do the following steps, (turn phone off, press and hold the volume down, power up the phone)
Grab a copy of fastboot.exe and put it in the folder with the IMG files (PM me if you can't find one)
Now, test to make sure your phone is seen by fastboot:
Open a cmd prompt and go to the folder where the img files and fastboot are stored.
Type: fastboot devices
you should get a response like this:
C:\temp\nexus image files>fastboot devices
xxxxxxxxxxxxxxxx fastboot
(x's will be alphanumeric)
This means that fastboot can now see your device. if you get nothing, something went wrong above.. troubleshoot that.
If everything is good, start flashing:
fastboot flash bootloader bootloader-crespo-i9020xxkl1.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo-i9020uckj1.img
fastboot reboot-bootloader
fastboot -w update image-sojua-imm76d.zip
Reboot your phone and be *Very* patient with the first boot.
You should now be good.

Thanks all so very much for all the help! It was extremely helpful and really helped to get my head around things.
What I ended up doing was (for those who might be stuck in the same situation as me):
1) Wipe everything. EVERYTHING. Used fastboot into CWM to help me do that.
2) Put in Kustom Kream found here:
http://forum.xda-developers.com/showthread.php?t=1399956
3) CM9 from here:
http://download.cyanogenmod.com/?type=nightly&device=crespo
* Not super stable to be honest; I've had at least three times where my entire phone randomly shut down and went into the CM9 boot screen and was stuck there until I did a battery pull. Reinstalled each time through CWM. Hope this gets fixed soon!
I found that Kustom Kream put CWM AND rooted my phone AND had everything working in terms of radio bands, sending SMS, etc. I originally had major issues with radios but now I have KB3 although the signal is kind of weak. Maybe because I live in a relatively far out suburban area?
But this solved my problems. Good luck to anyone out there stuck where I am, I feel your pain!

I would recommend that you at least flash a radio that is designed to work with your model - ucjk. That way you won't have any issues if you toggle to 2G.
Sent from my Galaxy Nexus

help- bricked it, no recovery, what now?

Hey yall. I had the phone for 6 days before I bricked it. I am wondering if there is any stock recovery mode or anything or what I shsould do? I think something went wrong due to using the root toolbox pro app. I have done some backups within the ap as well as Titanium Backup but now the phone will not boot up and I dont know if/how to put it in factory recovery mode. Soft reset does nothing. The Motorola logo will show on startup but then the screen just blacks out forever, not off, just colored black.
A few details, the phone was rooted with Motofail2go, with no recovery and bootloader still locked as far as I know.
Should I take it to Sprint for a factory reset? Is this even an option? What are my other options?
Next time I will probably use the Moto unlock key so I can open the bootloader all legit like and have a recovery mode...

Try holding power button and the down volume key to power off. Once you power off press and hold them again. This should boot you into fastboot, Motorola's adb shell basically. This can take a couple tries, make sure the phone is powered down completely before hitting volume down and power button to get into fastboot. If you can boot into fastboot you can unlock using this guide: http://www.droid-life.com/2012/08/20/how-to-unlock-the-motorola-photon-q-bootloader/
Once unlocked flash the custom recovery of your choice (I like twrp). You can boot into custom recovery by holding volume up and the power button from a powered down state. Here is the link for instructions on how to flash twrp:
http://forum.xda-developers.com/showthread.php?t=1887070
Then you can download one of the stock backups for the Q posted in the development section and restore them using the custom recovery. Most of the ones I have seen have been compatible with twrp.
The only way to download the stock rom backups is to remove the sd card from your phone, plug your sd card into a PC or other device with a card reader, download the stock backups, and place the stock backup rom files on your sd card. Finally place the sd card with the stock backup downloads into your phone.
These backups and information on how to go through this process can be found in this thread on page 2: http://forum.xda-developers.com/showthread.php?t=2001226
The key is to make a backup of your existing rom with twrp and then move the stock backups from your sd card to the twrp/backups/yourdeiceserial/ directory. That creates a backup directory which twrp knows to look for backups in.
Don't feel bad, I've been in that state several times since getting the Q, live and learn.
Sent from my XT897 using xda app-developers app

UnicronAlpha99 said:
Try holding power button and the down volume key to power off. Once you power off press and hold them again. This should boot you into fastboot, Motorola's adb shell basically. This can take a couple tries, make sure the phone is powered down completely before hitting volume down and power button to get into fastboot. If you can boot into fastboot you can unlock using this guide: http://www.droid-life.com/2012/08/20/how-to-unlock-the-motorola-photon-q-bootloader/
Once unlocked flash the custom recovery of your choice (I like twrp). You can boot into custom recovery by holding volume up and the power button from a powered down state. Here is the link for instructions on how to flash twrp:
http://forum.xda-developers.com/showthread.php?t=1887070
Then you can download one of the stock backups for the Q posted in the development section and restore them using the custom recovery. Most of the ones I have seen have been compatible with twrp.
Don't feel bad, I've been in that state several times since getting the Q, live and learn.
Sent from my XT897 using xda app-developers app
Click to expand...
Click to collapse
If that does not work you could drop it in water or something. You have not officially unlocked boot loader so you still have warranty. Or you could just tell sprint it quit working and act completely clueless. At least its bricked with warranty still intact.

matt2k12 said:
Hey yall. I had the phone for 6 days before I bricked it. I am wondering if there is any stock recovery mode or anything or what I shsould do? I think something went wrong due to using the root toolbox pro app. I have done some backups within the ap as well as Titanium Backup but now the phone will not boot up and I dont know if/how to put it in factory recovery mode. Soft reset does nothing. The Motorola logo will show on startup but then the screen just blacks out forever, not off, just colored black.
A few details, the phone was rooted with Motofail2go, with no recovery and bootloader still locked as far as I know.
Should I take it to Sprint for a factory reset? Is this even an option? What are my other options?
Next time I will probably use the Moto unlock key so I can open the bootloader all legit like and have a recovery mode...
Click to expand...
Click to collapse
Both of the methods above are very effective. When I had the first photon I bricked it and just dropped it in water and did a claim. Depending on the insurance you have that way may cost you $100. The other method should work. When I first got this phone I did the exact same thing and to go back and unlock then flash twrp and in stall a stock backup someone had posted.
Sent from my XT897 using Tapatalk 2

UnicronAlpha99 said:
Try holding power button and the down volume key to power off. Once you power off press and hold them again. This should boot you into fastboot, Motorola's adb shell basically. This can take a couple tries, make sure the phone is powered down completely before hitting volume down and power button to get into fastboot. If you can boot into fastboot you can unlock using this guide: http://www.droid-life.com/2012/08/20/how-to-unlock-the-motorola-photon-q-bootloader/
Click to expand...
Click to collapse
Thanks for the response. Is there anything extra extra special about getting into factory fastboot mode? I can't seem to get it done. Is there an official set of instructions anywhere? Does the phone need to be plugged into the PC? It was always my understanding (for the last week) that Power and Vol Down was the soft reset mode which reboots the phone. Therefore it always tries to reboot in normal mode. This is what keeps happening. It never powers completely down using this method.
Anyhow, once I follow your instructions, the Moto logo appears, no Sprint logo appears, the phone "powers on" but the screen is blacked out (not off). After waiting for a while at the blank/black screen, or holding down several buttons like vol or camera I get the first attachment: "Process system is not responding. Would you like to close it?" When I wait nothing happens. When I push OK nothing happens. By chance, I held down power during the notification and the power menu came up behind the ANR notice (second/third attachments). So obviously there are some things working but the main system isn't booting up. And either factory fastboot is nuked or I can't figure it out. When I power down from this accessible power menu and try to do the fastboot (Power / Vol Down) I still havent gotten it to work.
Any other ideas before I take drastic measures?
Since I bought it from Amazon would that be my best route for return or should I go thru a Sprint store?
Thanks in advance.

Hi again yall. You know once I got to thinking about it, I decided to check out the return policy on Amazon Wireless. They will accept any device under warranty for the first 30 days and it is up to Moto for the next 11 months of warranty coverage. They email me a packing label and it ships out 1 day and they ship out the new phone 1 day shipping. Hard to beat, just takes 2 days of shipping and some more fun times with my Epic, 10.1CM style, in the meantime.
Who's to say it wasnt some sort of hardware or software glitch that bricked the phone rather than my screwing around? Nobody knows and it isn't up to the consumer to prove his innocence. I bought everything legally, all the apps at the app store, and only ran the motofail2go root method. Wasn't running any custom Roms, Mods, or anything. I don't feel bad after they got me for another 2 grand for 24 months, and since I have been with Sprint for 10 years;l I have spent well over 10k or 15k with them lifetime.
If any other method pops up between now and when I ship it out I may give it a shot but if not, ah well, capitalism.

matt2k12 said:
Thanks for the response. Is there anything extra extra special about getting into factory fastboot mode? I can't seem to get it done. Is there an official set of instructions anywhere? Does the phone need to be plugged into the PC? It was always my understanding (for the last week) that Power and Vol Down was the soft reset mode which reboots the phone. Therefore it always tries to reboot in normal mode. This is what keeps happening. It never powers completely down using this method.
Anyhow, once I follow your instructions, the Moto logo appears, no Sprint logo appears, the phone "powers on" but the screen is blacked out (not off). After waiting for a while at the blank/black screen, or holding down several buttons like vol or camera I get the first attachment: "Process system is not responding. Would you like to close it?" When I wait nothing happens. When I push OK nothing happens. By chance, I held down power during the notification and the power menu came up behind the ANR notice (second/third attachments). So obviously there are some things working but the main system isn't booting up. And either factory fastboot is nuked or I can't figure it out. When I power down from this accessible power menu and try to do the fastboot (Power / Vol Down) I still havent gotten it to work.
Any other ideas before I take drastic measures?
Since I bought it from Amazon would that be my best route for return or should I go thru a Sprint store?
Thanks in advance.
Click to expand...
Click to collapse
Try using adb. If your computer has drivers on it for phone you might able to get into fast boot. If that does not work I would try Sprint store first. Have locked my phone up several times while hacking wife off in progress and have used adb every time. Only time i have been truely scared is when i soft bricked my nexus 7. had to stay at work for two hours after i got off to get it to recover because i was scared of her lol.
---------- Post added at 02:05 PM ---------- Previous post was at 01:57 PM ----------
If you get adb to recognize device you could take chance and officially unlock boot loader. Then flash twrp. There is a thread in general section about having trouble getting official update. It has a stock recovery in it. Trick would be moving files to recovery section of twrp

I have gotten the phone to soft power down and get into fast boot and custom recovery. It's a bit tricky with timing, I usually wait for the screen to go black after soft reset, let go, and immediately hold power and volume down. If you can not boot into fastboot I honestly don't know what you can do either than return the phone.
Sent from my XT897 using xda app-developers app

UnicronAlpha99 said:
I have gotten the phone to soft power down and get into fast boot and custom recovery. It's a bit tricky with timing, I usually wait for the screen to go black after soft reset, let go, and immediately hold power and volume down. If you can not boot into fastboot I honestly don't know what you can do either than return the phone.
Sent from my XT897 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the help Unicron. I think Brandons method might be my only alternative... but you know what? I already have the box packed up to ship back to Amazon! I am still a noob; I dunno if I could go the distance on this one. I have been updating my Android SDK files since I got the phone but I never got it to recognize boot up thru ADB fastboot. disclaimer* I havent tried it in a couple days since all teh SDK updates completed.
I dunno though I am a big time DIYer when possible. If it werent for the massive amount of tape I put on the box and packing label I would already be trying this method. I can't convince myself just yet. Amazon makes it too easy. I could have the *new* phone by Friday. Then I wouldn't be wasting my remaining work week trying to hack into my personal Christmas present in order to make it function...........................................
Edit - Yes I'm impatient. My job is too demanding and I am trying to set a good precedent for 2013. Wasting the first 3 work days on a phone is not how I intend to start off the year. There is probably a valuable lesson to be learned from this as far as hacking experience and to be honest with the responses here I think I could get it to boot up from PC in SDK/ADB mode and go from there. I just didnt know if that was possible until after I made the claim with Amazon. I still have an entire day today and tomorrow if I want to indulge myself. It doesnt matter if I mail the package today or Wednesday, I can still get it by Friday. I believe this thread is still valuable because we have patterns of repeating past failures and I may find use of it when I recieve my new phone and, darn it, it mysteriously bricks as well. in the same fashion.... the only thing I was really trying to do was get all my apps on my SD card... sad huh?
Edit 2 - Opened up the box, tried fastboot and adb, nothing. Off she goes.

I don't blame you, it sounds easier to exchange in your case any way. The main suggestion I have is if you are getting into any type of build.prop or operating system tweaks that have potential to lead to boot loops or cause the phone not to boot, then unlock the bootloader and install custom recovery.
The Moto-fail method seems limited to only be able to run apps that require root. For me this has no use as I want to be able to have complete control over all aspects of the Android OS. There is not a huge mod community for the Q as yet but I believe Cyanogen will be a reality as Interloper continues working on it. I came from an Epic with Cyanogen and soft-bricked it a minimum of 50 times. CWM was very forgiving on that phone, the Q is a lot more finicky and frustrating.
If you have insurance through the carrier then you are going to pay $150 for a refurb if something goes wrong and you hard brick the phone. If you unlock bootloader and install custom recovery then you have a fail-safe in the form of nandroid backups and restores. Then you can mod away with little fear.
Good luck on the new phone and I hope you don't give up after six days of modding with the Q!
Sent from my XT897 using xda app-developers app

matt2k12 said:
Thanks for the help Unicron. I think Brandons method might be my only alternative... but you know what? I already have the box packed up to ship back to Amazon! I am still a noob; I dunno if I could go the distance on this one. I have been updating my Android SDK files since I got the phone but I never got it to recognize boot up thru ADB fastboot. disclaimer* I havent tried it in a couple days since all teh SDK updates completed.
I dunno though I am a big time DIYer when possible. If it werent for the massive amount of tape I put on the box and packing label I would already be trying this method. I can't convince myself just yet. Amazon makes it too easy. I could have the *new* phone by Friday. Then I wouldn't be wasting my remaining work week trying to hack into my personal Christmas present in order to make it function...........................................
Edit - Yes I'm impatient. My job is too demanding and I am trying to set a good precedent for 2013. Wasting the first 3 work days on a phone is not how I intend to start off the year. There is probably a valuable lesson to be learned from this as far as hacking experience and to be honest with the responses here I think I could get it to boot up from PC in SDK/ADB mode and go from there. I just didnt know if that was possible until after I made the claim with Amazon. I still have an entire day today and tomorrow if I want to indulge myself. It doesnt matter if I mail the package today or Wednesday, I can still get it by Friday. I believe this thread is still valuable because we have patterns of repeating past failures and I may find use of it when I recieve my new phone and, darn it, it mysteriously bricks as well. in the same fashion.... the only thing I was really trying to do was get all my apps on my SD card... sad huh?
Edit 2 - Opened up the box, tried fastboot and adb, nothing. Off she goes.
Click to expand...
Click to collapse
FWIW, pressing vol down + power til it resets then pressing the camera button + power once the screen is black gets you to the Boot Mode Selection Menu, where you can start recovery, fastboot, BP tools (still not sure what that is entirely) and some others. Seems to be a fairly reliable/easy method for getting to both recovery and fastboot from any point.

befrosty8612 said:
FWIW, pressing vol down + power til it resets then pressing the camera button + power once the screen is black gets you to the Boot Mode Selection Menu, where you can start recovery, fastboot, BP tools (still not sure what that is entirely) and some others. Seems to be a fairly reliable/easy method for getting to both recovery and fastboot from any point.
Click to expand...
Click to collapse
Sure wish I would have known that ahead of time. Does this work without any recovery mode and with the bootloader still locked?

matt2k12 said:
Sure wish I would have known that ahead of time. Does this work without any recovery mode and with the bootloader still locked?
Click to expand...
Click to collapse
It does work without any recovery mode and I believe it still works without the bootloader being unlocked, I didn't know about this myself until after I had already unlocked it. Sorry I couldn't help out sooner.

befrosty8612 said:
It does work without any recovery mode and I believe it still works without the bootloader being unlocked, I didn't know about this myself until after I had already unlocked it. Sorry I couldn't help out sooner.
Click to expand...
Click to collapse
Awesome, I am wanting to do the backdoor root method again but, of course, may brick it. I dont think Amazon will keep sending me new ones.... but maybe!

befrosty8612 said:
FWIW, pressing vol down + power til it resets then pressing the camera button + power once the screen is black gets you to the Boot Mode Selection Menu, where you can start recovery, fastboot, BP tools (still not sure what that is entirely) and some others. Seems to be a fairly reliable/easy method for getting to both recovery and fastboot from any point.
Click to expand...
Click to collapse
For anyone concerned, I knew it would only be a matter of time until bricking my new device. This damn Root Toolbox Pro did it to me again, and on a simple, menial task. I am going to be working thru the motions on getting this to work.
Using the instructions quoted I did get stock recovery to work or at least flash on the screen for a split second. Seems like there is a timer on the recovery screen. I am having trouble with the fastboot prompt though on the PC. Do I do it in the "platform-tools" folder which contains fastboot or in the "tools" folder of the main SDK directory? I am really a noob, can you give me the cliff notes of how to get into ADB, fastboot, etc on the Photon Q in order to do a factory reset? I already have Android SDK installed and completely up to date so that is done. And Fastboot is installed. I'm just having trouble crossing the finish line here... I can get the fastboot page opened in the stock recovery but from there I'm lost. I dont know what to type into the command prompt, in what directory, or what.... Also when I open the command prompt in the SDK folder on the PC with fastboot in the directory and type "adb reboot bootloader" it says "device not found". Maybe (surely) that is the wrong prompt?
FWIW my phone is showing the dead android guy. I didnt do anything besides try and clear up my Play Store download list which required a reboot. The phone never started back up. I dont know how much damage was done or info was lost or whatever, but seeing as how I was rooted but still locked, I had no custom recovery. So no back ups. Is there anything to restore or am I looking at a full wipe and restore?

matt2k12 said:
For anyone concerned, I knew it would only be a matter of time until bricking my new device. This damn Root Toolbox Pro did it to me again, and on a simple, menial task. I am going to be working thru the motions on getting this to work.
Using the instructions quoted I did get stock recovery to work or at least flash on the screen for a split second. Seems like there is a timer on the recovery screen. I am having trouble with the fastboot prompt though on the PC. Do I do it in the "platform-tools" folder which contains fastboot or in the "tools" folder of the main SDK directory? I am really a noob, can you give me the cliff notes of how to get into ADB, fastboot, etc on the Photon Q in order to do a factory reset? I already have Android SDK installed and completely up to date so that is done. And Fastboot is installed. I'm just having trouble crossing the finish line here... I can get the fastboot page opened in the stock recovery but from there I'm lost. I dont know what to type into the command prompt, in what directory, or what.... Also when I open the command prompt in the SDK folder on the PC with fastboot in the directory and type "adb reboot bootloader" it says "device not found". Maybe (surely) that is the wrong prompt?
FWIW my phone is showing the dead android guy. I didnt do anything besides try and clear up my Play Store download list which required a reboot. The phone never started back up. I dont know how much damage was done or info was lost or whatever, but seeing as how I was rooted but still locked, I had no custom recovery. So no back ups. Is there anything to restore or am I looking at a full wipe and restore?
Click to expand...
Click to collapse
As abnormal as it seems, your situation seems pretty normal... at least from my shoes. I went through the same scenario... I didn't know what adb was, or fastboot, etc. So, here's what I know
the fastboot commands work even if adb doesnt see it in the list of devices attached. Somehow it just works (as long as the phone is in fastboot mode).
If you're able to get to the fastboot mode, things should be okay. Just open a windows explorer window to the Platform-Tools, hold the shift key and right click on a blank space within the window, then click open command window here.
you should be able to pass any adb (if the phone is on and recognized) or fastboot (if phone is in fastboot mode) commands from that command prompt.
Also, if you have a stock recovery, CMW, or TWRP image, this is the folder to copy those .img files to. Once you get your phone into fastboot mode and its plugged into the computer, just type into the command prompt:
Code:
fastboot flash recovery recovery.img
If you're just looking to reboot the phone into recovery
If you have a CWM or TWRP recovery just replace the recovery.img with whatever the .img file that you have. Also, as a tip instead of writing the entire file name, just press the first couple letters then press the tab key within the command prompt, it should fill in the rest. keep pressing tab until you get to the .img file name you want.
To avoid doing this again, maybe I can help... what were you trying to do to begin with? From the sound of it, you were trying to root the phone with the Root Toolbox Pro but it bricked, and then you tried to reboot into recovery and then got the red android... ?

befrosty8612 said:
As abnormal as it seems, your situation seems pretty normal... at least from my shoes. I went through the same scenario... I didn't know what adb was, or fastboot, etc. So, here's what I know
the fastboot commands work even if adb doesnt see it in the list of devices attached. Somehow it just works (as long as the phone is in fastboot mode).
If you're able to get to the fastboot mode, things should be okay. Just open a windows explorer window to the Platform-Tools, hold the shift key and right click on a blank space within the window, then click open command window here.
you should be able to pass any adb (if the phone is on and recognized) or fastboot (if phone is in fastboot mode) commands from that command prompt.
Also, if you have a stock recovery, CMW, or TWRP image, this is the folder to copy those .img files to. Once you get your phone into fastboot mode and its plugged into the computer, just type into the command prompt:
Code:
fastboot flash recovery recovery.img
If you're just looking to reboot the phone into recovery
If you have a CWM or TWRP recovery just replace the recovery.img with whatever the .img file that you have. Also, as a tip instead of writing the entire file name, just press the first couple letters then press the tab key within the command prompt, it should fill in the rest. keep pressing tab until you get to the .img file name you want.
To avoid doing this again, maybe I can help... what were you trying to do to begin with? From the sound of it, you were trying to root the phone with the Root Toolbox Pro but it bricked, and then you tried to reboot into recovery and then got the red android... ?
Click to expand...
Click to collapse
Thanks for the response. So, all I have to do is: go to fastboot and flash a stock recovery image file and it will automatically wipe the phone, cache, everything, and restore the operating system? Sounds awfully easy! I found some stock files in this post : http://forum.xda-developers.com/showthread.php?t=2001226&page=2 Are these the ones you used before?
Last question: I can flash CWM or TWRP but wont be able to access them if my bootloader is locked, correct? So flashing a stock recovery will allow me to have my stock phone back again, locked and un-rooted? I guess if I cant get it to work with the stock recovery then I can unlock the bootloader and do a CWM or TWRP recovery and then flash the stock .img files?
Thanks again for your help. I already had root with the motofail2go method which I like using but seems like when I try and use some generic root feature from apps from the app store that it will crash/brick the phone cuz obviously those apps are generalized and likely to brick certain percentage of devices....

Ok what does this mean? Something with the bootlaoder obviously. Does it need to be unlocked?
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recover
y qrecovery1.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (5962 KB)...
OKAY [ 0.479s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.755s
C:\Program Files (x86)\Android\android-sdk\platform-tools>
And on the phone screen it says "invalid image size for partition recovery" twice for both times I tried this method.

You will need to flash the system image as well if you want those, as the recovery image will only flash the recovery. The files in that link are for twrp only... so you'll have to be able to get there first.
With the custom recoveries, I'm not 100% sure whether or not you will be able to use them without being unlocked. I would wait to see if anyone else can answer that question for you, but if you did try it without an unlocked bootloader, you at least have the stock recovery to fall back on if needed.
Sent from my XT897 using xda app-developers app
---------- Post added at 09:16 PM ---------- Previous post was at 09:12 PM ----------
I'm thinking it could either be that your phone is full and the image you're flashing is too large to fit on the space available...
Or you're trying to flash custom software on a locked phone.
Hopefully someone is able to answer that a little better...
Sent from my XT897 using xda app-developers app

You can't alter the stock recovery (flash a custom recovery like twrp or cwm) in fastboot without having the bootloader unlocked. Your options are to unlock your bootloader, flash custom recovery, create a backup of your current setup, download one of the stock working backups, place it in the backups folder for twrp on your external sd card, and restore one of the known working backups in the development section (befrosty linked to one). Or you could use RSD lite to return to stock using a stock factory firmware flash. That involves connecting your phone to your PC and flashing the phone back to factory stock. Information on RSD Lite and links to the FXZ's can be found here.
http://forum.xda-developers.com/showthread.php?t=2095536
Sent from my XT897 using xda app-developers app

Managed to brick my wife's Moto G Power twice trying to put a new image on it. Help Please.

*hangs head in shame*
Ok, I'm stumped and I need help.
Last time I rooted a phone, it was our old HTC Thunderbolts... Things have changed significantly since then, or so it would appear.
Trying to fix my wife's phone after a Verizon OTA update seems to have jumped her phone from Android 10 to 11, and in the process nerfed the hotspot (which we need, as we're rural with no landline broadband available)
I'm working on a Moto G Power (sofia XT2041-4), bought late last year off the shelf from Best Buy.
Home PC is a Windows 10 box. I do not have a linux environment available to me.
I am \ was trying to put LinageOS on it, but honestly don't care what OS it is as long as we can turn the hotspot on ourselves, regardless of what Verizon wants. Over a decade ago, I rooted our phones with ICS image, so I have some outdated experience here. CalyxOS looks nice but I don't think it'll work on Moto G Power.
So, here's where I'm at in the last 48 hours.
I have gone in and gotten the unlock key from motorola, and successfully undone the OEM Lock. (I know this is the case because it tells me I'm an idiot and I should lock it, every time it boots up now). This also managed to wipe the phone, which, oops, read to the end of the paragraph BEFORE unlocking and deleting pictures of the grandkids which came in since the last backup.
Somehow last night, I managed to get it to be a brick, but used LMSA to unbrick it, but that version is still the OTA updated Android 11, so same problem with the hotspot.
I have installed the Android SDK, newest motorola drivers, and also the standalone 'Minimal ADB and Fastboot' on my PC
I've managed to get TWRP installed in the recovery portion of the phone. (note: may have been wiped now, but I can get it back on I believe)
Following this video, I managed to bring TWRP up, wiped the device, then copied the Lineage OS image to the microSD card, as well as Open GApps. The only thing I couldn't get to work, other than, you know, the new OS, is I didn't see a place to enable advanced boot options, so I have to get back to the bootloader via Volume Down and Power from a full shutdown state.
When I try to install the LinageOS (17.1), it looks like it's installing, goes through steps 1 and 2, then a slew of error messages in the log.
I've got the 4 image files I pulled out of one of the LineageOS zip files (Boot, Product, System, VBMeta) in the 'Minimal ADB and Fastboot' directory.
I can run 'fastboot flash boot boot.img' from the 'Minimal ADB and Fastboot' directory and it succeeds.
When I try to run Product, System or VBMeta in the same way (cmdline = fastboot flash product product.img), all of them fail the Preflash Validation and it comes back with 'FAILED (remote failure)'
During this process, somehow I bricked my wife's phone AGAIN, but just got it reset with LMSA for the second time. So, I may have wiped out everything I've done previously on the phone, which may or may not be a good thing. But, I believe everything I've done up to this point is repeatable (which is somewhat why I wrote all of the above details out)
Edit: Progress is Made! - Ok, now that I've got FASTBOOTD figured out, I was able to flash the Boot, Product, System and VBMeta into active partition A. But when I use the command 'flashboot reboot' it just keeps coming back to the fastboot flashload screen with the green android with it's access panel open. I tried to get back into TWRP via entering 'Recovery Mode' at the loader, but apparently it got wiped. I'm guessing I should flash it back into the recovery slot ("fastboot flash recovery twrp-3.4.0-0-sofia-test9") and then maybe try to recover from Partition A via TWRP?
Things I'm not sure about
First, I'm pretty sure I'm not in FastbootD. I don't see a big red FASTBOOTD at the top, and according to this thread, means I'm not in it.
Update: Ok, I realized I didn't have the 'platform tools', which I have now downloaded, and once I was back in fastboot, I was able to run 'Flashboot reboot flashboot' and now I know I'm in FlashbootD. Not sure what I'm supposed to do in here at this point, but hey, I've now got the correct interface.
I think FASTBOOTD should be something I'm interacting with on the Moto G Power, but for the life of me, I can't figure out how to get to it.
Update on this, see above.
I feel like I've got to be CLOSE to getting this thing working, but damned if I can seem to cross the finish line.
Help?
Further Edit: So, I tried another OS, ResurrectionOS, just to see if it was an issue with the image.
Started with another reset with LMSA (I love that tool... It zeroes out all the stupid things I'm doing on the Moto G Power during this process)
Rebooted into FastBootD mode (with the nice red at the top)
Flashed all four of the images. No errors noted during the process
Wiped the Data
Rebooted... And right back to the bootloader. Cannot seem to get out of the boot loader to get the new OS to initialize.
Again, Help?

Did you ever solve this riddle?

[ HELP ] ASUS Zenfone Max Plus M1 - Cant get any Firmware to boot this device into system after flash...

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).