Hi guys, my friend's Atrix HD is in a trouble, exactly as the post title say. He device has bl locked again with no system to boot, there's some way to install a rom in this situation?
Any way to get into fastboot? If you can get into fastboot, try flashing a stock ROM with RSD Lite.
Myth tools will adb a rom over if you can get into the boot loader
Hard Bricked Atrix HD MB886
oscar the grouch said:
Myth tools will adb a rom over if you can get into the boot loader
Click to expand...
Click to collapse
Hi, I have tried everything, even I bought the fastboot cable and it can give it life to my phone. Fail on RSD, MYThool, on Cmd with fastboot.
[Q] Enable USB Debugging mode with fastboot or adb commands?
audit13 said:
Any way to get into fastboot? If you can get into fastboot, try flashing a stock ROM with RSD Lite.
Click to expand...
Click to collapse
It not seems to work, i can get into adb via stock recovery and can get fastboot normally. My question is: Is it possible to enable usb debugging mode using adb or fastboot commands?
ErickST18 said:
My question is: Is it possible to enable usb debugging mode using adb or fastboot commands?
Click to expand...
Click to collapse
No, it is not possible. This would be a massive security issue, as it would defeat the entire purpose of having that setting in the phone, since it would allow full access to your phone without logging into the OS.
Pro-tip: You should really leave that setting turned off until you actually need it, because otherwise anyone can plug in a USB cable and get full access to send fastboot commands to your device (including bypassing lock screens).
quasihellfish said:
No, it is not possible. This would be a massive security issue, as it would defeat the entire purpose of having that setting in the phone, since it would allow full access to your phone without logging into the OS.
Pro-tip: You should really leave that setting turned off until you actually need it, because otherwise anyone can plug in a USB cable and get full access to send fastboot commands to your device (including bypassing lock screens).
Click to expand...
Click to collapse
Thank you for the reply bro. The thing is, i'm giving this error and i don't know what to do, it's driving me crazy. Hope you can help me, i've attached a image with screen error below.
ErickST18 said:
Thank you for the reply bro. The thing is, i'm giving this error and i don't know what to do, it's driving me crazy. Hope you can help me, i've attached a image with screen error below.
Click to expand...
Click to collapse
No idea. Looks like you need to contact the dealer
ErickST18 said:
Thank you for the reply bro. The thing is, i'm giving this error and i don't know what to do, it's driving me crazy. Hope you can help me, i've attached a image with screen error below.
Click to expand...
Click to collapse
I think this is like a hard brick, but worse. I think its a dead device and at minimum needs its motherboard replaced with a new/used one that has a working ROM on it.
palmbeach05 said:
I think this is like a hard brick, but worse. I think its a dead device and at minimum needs its motherboard replaced with a new/used one that has a working ROM on it.
Click to expand...
Click to collapse
As i thought, well thank you for the reply. I'll keep trying anyway.
Related
OMGOGOMOGMOGM SOMEONE PLEASE HELP
I just flashed the aokp rom http://forum.xda-developers.com/showthread.php?t=2250601&page=12 with safestrap recovery thing a majiger cant remember the name of it but anyway, i flashed it and when i tapped reboot it comes up with a black screen showing this format
Invalid flash mode (s)
10..9b(*) (sha-5b08bc, 2012-12-03:10:39)
eMMC info: size 8gb
Device is LOCKED, Status code: 0
Battery Low:
Transfer Mode:
USB connected
Failed to hab check for boot: 0x56
Fastboot Reason: Boot Failure
usb Connected
This is exactly whats on my screen right now and its scaring the hell out of me, SOMEONE PLEASE HELP I DID EVERY INSTRUCTION TO FLASHING THE ROM WITH THE RECOVERY IM USING AND THIS HAPPENED.
:crying ::crying: :crying: :crying: :crying: :crying: :crying: :crying: :crying: :crying:
Face palm man. You need an unlocked bootloader for that rom says so in the info so you clearly didn't follow directions like you said to such as using cwm not safestrap. This is why we must read before acting hastily. You may be able to use rsd to flash stock but don't count on it.
Sent from my PACMAN MATRIX HD MAXX
deeje00 said:
Face palm man. You need an unlocked bootloader for that rom says so in the info so you clearly didn't follow directions like you said to such as using cwm not safestrap. This is why we must read before acting hastily. You may be able to use rsd to flash stock but don't count on it.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
yea i was gonna say the same i also think new people see that safestrap thread thats stickied which is why they install ss and not cmw.
Sent from my MB886 using xda premium
This might help: http://forum.xda-developers.com/showthread.php?t=2231249
deeje00 said:
Face palm man. You need an unlocked bootloader for that rom says so in the info so you clearly didn't follow directions like you said to such as using cwm not safestrap. This is why we must read before acting hastily. You may be able to use rsd to flash stock but don't count on it.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
i actually have the same problem. My phone is unlocked before already, but the problem is i cant get in to any bootloader or fastboot or anything. I can only tell the phone is on when i plug to computer and rsdlite sees the device, but fails to flash anything because it is not in the fastboot mode...
do you know how i can figure this out?
legendnexus said:
i actually have the same problem. My phone is unlocked before already, but the problem is i cant get in to any bootloader or fastboot or anything. I can only tell the phone is on when i plug to computer and rsdlite sees the device, but fails to flash anything because it is not in the fastboot mode...
do you know how i can figure this out?
Click to expand...
Click to collapse
Did you flash a rom using Safestrap too?
audit13 said:
Did you flash a rom using Safestrap too?
Click to expand...
Click to collapse
is it a right source to try?
http://forum.xda-developers.com/showthread.php?t=1995220
legendnexus said:
is it a right source to try?
http://forum.xda-developers.com/showthread.php?t=1995220
Click to expand...
Click to collapse
That thread is for locked bootloaders. Do you have a locked bootloader? Did you flash a rom using safestrap?
Did you try this? http://forum.xda-developers.com/showthread.php?t=2231249
Or this? http://forum.xda-developers.com/showthread.php?t=2262726
audit13 said:
That thread is for locked bootloaders. Do you have a locked bootloader? Did you flash a rom using safestrap?
Did you try this? http://forum.xda-developers.com/showthread.php?t=2231249
Or this? http://forum.xda-developers.com/showthread.php?t=2262726
Click to expand...
Click to collapse
Yeah i unlocked the bootloader before. so it seems like useless for my case. Plus i cant even boot into fastboot mode, how am i gonna install it lol
And as I said before; the problem is i cant get in to any bootloader or fastboot or anything. I can only tell the phone is on when i plug to computer and rsdlite sees the device, but fails to flash anything because it is not in the fastboot mode.
I tried both methods but they both fail where the phone need to be in fastboot mode, which is apparently not happening...
legendnexus said:
Yeah i unlocked the bootloader before. so it seems like useless for my case. Plus i cant even boot into fastboot mode, how am i gonna install it lol
And as I said before; the problem is i cant get in to any bootloader or fastboot or anything. I can only tell the phone is on when i plug to computer and rsdlite sees the device, but fails to flash anything because it is not in the fastboot mode.
I tried both methods but they both fail where the phone need to be in fastboot mode, which is apparently not happening...
Click to expand...
Click to collapse
Damn, seems like those are the only two methods that could work.
The good thing is that you can't re-lock the bootloader.
You might want to send a PM to skeevy to see if he can help.
Is there any warranty left on your phone? I've seen posts where people were able to go back to AT&T to exchange the phone or send it in for repair.
legendnexus said:
Yeah i unlocked the bootloader before. so it seems like useless for my case. Plus i cant even boot into fastboot mode, how am i gonna install it lol
And as I said before; the problem is i cant get in to any bootloader or fastboot or anything. I can only tell the phone is on when i plug to computer and rsdlite sees the device, but fails to flash anything because it is not in the fastboot mode.
I tried both methods but they both fail where the phone need to be in fastboot mode, which is apparently not happening...
Click to expand...
Click to collapse
How have you tried to get into fastboot? Try turning your phone off, hold both volume buttons and press the power button a few times then use volume down to scroll to "ap fastboot" and use volume up to select.
Sent from my MB886 using Tapatalk
When you plug in the phone to charge do you see at least the boot logo?
may need to connect pins 1 & 4 together in micro usb charger port to phone within the plug itself and it will charge.
Swiftb12305 said:
yea i was gonna say the same i also think new people see that safestrap thread thats stickied which is why they install ss and not cmw.
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
I feel like it's causing more problems than it's solving with new people that try to flash their phones, they see light at the end of the tunnel and assume it's the exit, when in fact it's a dadgum train.
legendnexus said:
Yeah i unlocked the bootloader before. so it seems like useless for my case. Plus i cant even boot into fastboot mode, how am i gonna install it lol
And as I said before; the problem is i cant get in to any bootloader or fastboot or anything. I can only tell the phone is on when i plug to computer and rsdlite sees the device, but fails to flash anything because it is not in the fastboot mode.
I tried both methods but they both fail where the phone need to be in fastboot mode, which is apparently not happening...
Click to expand...
Click to collapse
Have you tried a fastboot cable?
audit13 said:
Damn, seems like those are the only two methods that could work.
The good thing is that you can't re-lock the bootloader.
You might want to send a PM to skeevy to see if he can help.
Is there any warranty left on your phone? I've seen posts where people were able to go back to AT&T to exchange the phone or send it in for repair.
Click to expand...
Click to collapse
nope no warranty left..
penser said:
How have you tried to get into fastboot? Try turning your phone off, hold both volume buttons and press the power button a few times then use volume down to scroll to "ap fastboot" and use volume up to select.
Sent from my MB886 using Tapatalk
Click to expand...
Click to collapse
exactly the same way you wrote. but unfortunately it doesnt work.
SVLAN said:
When you plug in the phone to charge do you see at least the boot logo?
Click to expand...
Click to collapse
ahahaha nothing!! no single pixel power up, forget about the logo lol
HD-man said:
may need to connect pins 1 & 4 together in micro usb charger port to phone within the plug itself and it will charge.
Click to expand...
Click to collapse
anthony2424 said:
Have you tried a fastboot cable?
Click to expand...
Click to collapse
I research on that i guess fasboot cable is connecting the pins 1 & 4 together in micro usb cable. I tried that too, however result is the same.
doesnt work.
That was my last hope (fastboot cable), so i even try other combinations connecting different pins together, but it didnt work too )))
I have a beautiful brick as you guys can understand.
I am thinking to order a broken lcd atrix hd online and replace the boards right now. Do you guys think it is logical?
or like replacing the storage with a used one.
I dont know what else to do, out of ideas
I am aware I haven't replied in a while, my atrix had a hardware issue, but I got a nexus 10!! Anyways, when plugging the phone in does the LED light up green?
Sent from my Nexus 10 using XDA Premium 4 mobile app
Nope, no lights
Sent from my Nexus 5 using Tapatalk
Hm sounds like a hardware issue, check the pins in the phones micro USB port if other cables don't make a the LED turn green while the phone is off.
Sent from my Nexus 10 using XDA Premium 4 mobile app
I updated my phone to Nexus to 5.1 last night and it got stuck in the boot animation but I figured it would be done when I woke up. Much to my dismay that was not the case so I tried to factory reset and now I get this message that says "No OS found." Tried to plug it up to the computer but it won't connect. I think it may have something to do with the OEM Lock but I cant fix that without the phone turning on. Please help!
How exactly did you upgrade your phone?
Sent from my Benzo'd Google N6 on VZ
lostnthought said:
I updated my phone to Nexus to 5.1 last night and it got stuck in the boot animation but I figured it would be done when I woke up. Much to my dismay that was not the case so I tried to factory reset and now I get this message that says "No OS found." Tried to plug it up to the computer but it won't connect. I think it may have something to do with the OEM Lock but I cant fix that without the phone turning on. Please help!
Click to expand...
Click to collapse
Please provide more info. Stock or custom recovery?
Evolution_Freak said:
Please provide more info. Stock or custom recovery?
Click to expand...
Click to collapse
Custom Recovery.. TWRP v2.8.2
lostnthought said:
Custom Recovery.. TWRP v2.8.2
Click to expand...
Click to collapse
From bootloader, enter the following fastboot commands:
fastboot format cache
fastboot format userdata
This should allow you to get back into TWRP and flash a ROM.
DebianDog said:
How exactly did you upgrade your phone?
Sent from my Benzo'd Google N6 on VZ
Click to expand...
Click to collapse
This may sound silly but I'm not 100% sure. A system notification had been on my screen for over two weeks saying that I had a system update to 5.1 and I finally decided to download and install said update and then it sent me to recovery mode. I don't know why I did but I hit fix permissions.. Just fiddling trying to figure everything out and this is where we are.
Evolution_Freak said:
From bootloader, enter the following fastboot commands:
fastboot format cache
fastboot format userdata
This should allow you to get back into TWRP and flash a ROM.
Click to expand...
Click to collapse
I can get into recovery mode but there isn't a ROM that I can find.. It's gone. And like I said it won't connect to the computer via USB port. (Tried several ports,as well as, different cords) Can't enable OEM lock
lostnthought said:
I can get into recovery mode but there isn't a ROM that I can find.. It's gone. And like I said it won't connect to the computer via USB port. (Tried several ports,as well as, different cords) Can't enable OEM lock
Click to expand...
Click to collapse
I'm not asking you to boot to recovery. Boot to bootloader.
lostnthought said:
I can get into recovery mode but there isn't a ROM that I can find.. It's gone. And like I said it won't connect to the computer via USB port. (Tried several ports,as well as, different cords) Can't enable OEM lock
Click to expand...
Click to collapse
move a rom via a computer to your phone. either connect the recovery to your computer and move it, or connect to a computer and adb push it to your phone.
Sorry, I guess I misread your post. I thought you said can't get to recovery. From TWRP you should be able to enable MTP transfer. Then your PC should see it and you can transfer files as @simms22 suggested.
lostnthought said:
"No OS found."
Click to expand...
Click to collapse
From TWRP, perhaps you wiped the System partition? Heh, I did that just last night... woops... "round 2"!
As a side note, if you're trying to use adb/fastboot from Windows... I had nothing but problems myself, even with the proper drivers. At worst, I had to open the Device Manager, find the phone, and force-install ("update") the driver to Android->Composite USB Device before it would be recognized. Absurd, but pains of working from Windows. (Conversely, I've had pain-free experiences from OSX and Ubuntu.)
vormund said:
From TWRP, perhaps you wiped the System partition? Heh, I did that just last night... woops... "round 2"!
As a side note, if you're trying to use adb/fastboot from Windows... I had nothing but problems myself, even with the proper drivers. At worst, I had to open the Device Manager, find the phone, and force-install ("update") the driver to Android->Composite USB Device before it would be recognized. Absurd, but pains of working from Windows. (Conversely, I've had pain-free experiences from OSX and Ubuntu.)
Click to expand...
Click to collapse
you dont need adb to move anything to your phone when using twrp. just connect to twrp using the mtp option.
Hey everyone I'm looking here as my last resort before sending my phone back to Motorola.
Bought a Nexus 6 from motorola uk which was delivered yesterday, switched phone on and all the Google apps on the phone updated, then had a notification OTA to download and install android 5.1 which I did, towards the end of the install process I had an error with the green android and a red exclamation mark.
I powered the device off with the power button and it turned back on and ever since it says "Android is starting" "Optimizing app 1 of 125" once it goes through all the apps it gets to the android boot screen then just goes back to the "Android is starting" "Optimizing app 1 of 125" over and over and over. (Infinite bootloop)
Pointers: The phone is not unlocked or rooted as I'm a noob its just fresh out the box, also I never opened/unlocked the developer options.
I have tried various recovery mode fixes, wiping cache and wiping all data and then rebooting the device with no luck.
Is there anyway I can hook my N6 up to my computer and fix this with a tool kit etc? I'm willing to try but I'd need basic instructions and reassurance it wouldn't muck up my warranty if it didn't work as my only other option is to exchange for a new device.
Any help, advice etc would be hugely appreciated. Thanks
Markh2001 said:
Hey everyone I'm looking here as my last resort before sending my phone back to Motorola.
Bought a Nexus 6 from motorola uk which was delivered yesterday, switched phone on and all the Google apps on the phone updated, then had a notification OTA to download and install android 5.1 which I did, towards the end of the install process I had an error with the green android and a red exclamation mark.
I powered the device off with the power button and it turned back on and ever since it says "Android is starting" "Optimizing app 1 of 125" once it goes through all the apps it gets to the android boot screen then just goes back to the "Android is starting" "Optimizing app 1 of 125" over and over and over. (Infinite bootloop)
Pointers: The phone is not unlocked or rooted as I'm a noob its just fresh out the box, also I never opened/unlocked the developer options.
I have tried various recovery mode fixes, wiping cache and wiping all data and then rebooting the device with no luck.
Is there anyway I can hook my N6 up to my computer and fix this with a tool kit etc? I'm willing to try but I'd need basic instructions and reassurance it wouldn't muck up my warranty if it didn't work as my only other option is to exchange for a new device.
Any help, advice etc would be hugely appreciated. Thanks
Click to expand...
Click to collapse
Read the guide on how to fastboot flash a factory image. No toolkit necessary.
Would you mind posting a link to a guide? I forgot to add that I don't want my phone to become rooted by trying to fix this issue, I want to keep it stock like it was, also does not have developer options enabled stop me from going further.
Sorry for the questions I'm a noob to this and quite anxious.
AndroidSlave said:
Read the guide on how to fastboot flash a factory image. No toolkit necessary.
Click to expand...
Click to collapse
Would you mind posting a link to a guide? I forgot to add that I don't want my phone to become rooted by trying to fix this issue, I want to keep it stock like it was, also does not have developer options enabled stop me from going further.
Sorry for the questions I'm a noob to this and quite anxious.
Can anyone still please help! I'm a noob and so need instructions on what to do! Please!
Markh2001 said:
Can anyone still please help! I'm a noob and so need instructions on what to do! Please!
Click to expand...
Click to collapse
If you connect the phone to the pc is it recognised in bootloader mode? Do you have adb installed onyour pc?
gee2012 said:
If you connect the phone to the pc is it recognised in bootloader mode? Do you have adb installed onyour pc?
Click to expand...
Click to collapse
All foreign language to me what your saying, trying my best to self learn right now. I'm downloading the adroid SDK and extracting the files, really want to sort this myself. Any pointers to getting into bootloader mode? And adb on the PC?
Markh2001 said:
All foreign language to me what your saying, trying my best to self learn right now. I'm downloading the adroid SDK and extracting the files, really want to sort this myself. Any pointers to getting into bootloader mode? And adb on the PC?
Click to expand...
Click to collapse
Look here http://forum.xda-developers.com/showthread.php?t=2588979 for easy adb installation. Read this too http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481.
To get into bootloader mode power down the device and after that press volume down + power. Here`s a guide to setup the sdk/adb http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/.
gee2012 said:
If you connect the phone to the pc is it recognised in bootloader mode? Do you have adb installed onyour pc?
Click to expand...
Click to collapse
I've made the fastboot adb folder on my PC and attached my phone whilst it was in bootloader mode, I types in the command box adb devices and there is no list of attached devices.
I presume this is because I didn't enable developer options or USB debugging?
Markh2001 said:
I've made the fastboot adb folder on my PC and attached my phone whilst it was in bootloader mode, I types in the command box adb devices and there is no list of attached devices.
I presume this is because I didn't enable developer options or USB debugging?
Click to expand...
Click to collapse
When in bootloader mode type : fastboot devices
-Edit- just read that your bootloade is still locked so i`am afraid there is nothing you can do to fix the issue as you cannot flash firmware with a locked bootloader. Best is to claim warranty because of a software issue while updating.
gee2012 said:
When in bootloader mode type : fastboot devices
-Edit- just read that your bootloade is still locked so i`am afraid there is nothing you can do to fix the issue as you cannot flash firmware with a locked bootloader. Best is to claim warranty because of a software issue while updating.
Click to expand...
Click to collapse
Sorry to be a noob but how do I do this? Is this on the PC I presume?
Markh2001 said:
Sorry to be a noob but how do I do this? Is this on the PC I presume?
Click to expand...
Click to collapse
There is nothing you can do with a locked bootloader, claim warranty/RMA
gee2012 said:
When in bootloader mode type : fastboot devices
-Edit- just read that your bootloade is still locked so i`am afraid there is nothing you can do to fix the issue as you cannot flash firmware with a locked bootloader. Best is to claim warranty because of a software issue while updating.
Click to expand...
Click to collapse
Thought this would be the case, I went into adb fastboot and typed in fastboot devices and its showing some letters and numbers next to fastboot on screen if that helps.
In the future I presume I should make sure to enable developer options first so I can get out if this mess?
Also would it be best when I get my new n6 just to sideload the latest update marsmellow by getting the factory image from the Google website? Last question can I skip from 5.0 straight to 6.0 sideloading or do I have tobdo it one at a time?
Thanks for trying to help matey
Markh2001 said:
Thought this would be the case, I went into adb fastboot and typed in fastboot devices and its showing some letters and numbers next to fastboot on screen if that helps.
In the future I presume I should make sure to enable developer options first so I can get out if this mess?
Also would it be best when I get my new n6 just to sideload the latest update marsmellow by getting the factory image from the Google website? Last question can I skip from 5.0 straight to 6.0 sideloading or do I have tobdo it one at a time?
Thanks for trying to help matey
Click to expand...
Click to collapse
Next time enable usb debugging and ENABLE OEM UNLOCK, both in developer options. You can flash the latest firmware available directly in fastboot by flashing the individual img files.
Here is a link to setup adb/platform-tools https://www.google.nl/url?sa=t&rct=...orial/&usg=AFQjCNGolazOWoMssTikMpokJ6TtwEND5A.
gee2012 said:
There is nothing you can do with a locked bootloader, claim warranty/RMA
Click to expand...
Click to collapse
This is getting very weird now as I just typed into the adb fastboot window : fastboot oem unlock and its giving me a message on my screen to click yes and unlock the bootloader?
Markh2001 said:
This is getting very weird now as I just typed into the adb fastboot window : fastboot oem unlock and its giving me a message on my screen to click yes and unlock the bootloader?
Click to expand...
Click to collapse
Well click the power button and in the next screen scroll down with the volume button to select yes and push power.
gee2012 said:
There is nothing you can do with a locked bootloader, claim warranty/RMA
Click to expand...
Click to collapse
It says this on my Nexus 6 phone screen.
Unlock bootloader?
If you unlock the bootloader, you will be able to install custom operating system on this phone.
A custom OS is not subject to the same testing as the original OS, and can cause your phone and installed applications to stop working properly.
To prevent unauthorized access to your personal data, unlocking the bootloader will also delete all personal data from your phone (a "factory data reset".)
Press the volume up/down buttons to select yes or no. Then press power button to continue.
Yes (Unlock bootloader, may void warranty)
No. ( Do not unlock bootloader and restart phone)
Markh2001 said:
It says this on my Nexus 6 phone screen.
Unlock bootloader?
If you unlock the bootloader, you will be able to install custom operating system on this phone.
A custom OS is not subject to the same testing as the original OS, and can cause your phone and installed applications to stop working properly.
To prevent unauthorized access to your personal data, unlocking the bootloader will also delete all personal data from your phone (a "factory data reset".)
Press the volume up/down buttons to select yes or no. Then press power button to continue.
Yes (Unlock bootloader, may void warranty)
No. ( Do not unlock bootloader and restart phone)
Click to expand...
Click to collapse
Click yes, see my above post
gee2012 said:
Click yes, see my above post
Click to expand...
Click to collapse
Okay but will I be able to relock and put it back to the way it was? Can you please stay around to help me do this step by step?! I'd appreciate it a million
Markh2001 said:
Okay but will I be able to relock and put it back to the way it was? Can you please stay around to help me do this step by step?! I'd appreciate it a million
Click to expand...
Click to collapse
Sure, but first we have to get the phone working again,
...and I thought it had worked but as it turns out, it did not. I found out it did not when I tried to root to which the phone proceeded to tell me it was lock.
Now, when I go into Recovery Mode, the phone does not come up in ADB even when trying to unlock after using the ASUS unlocker tool... Is the ADB bridge fried forever? How do I reinstate it to be able to root? I don't mind wiping, I just want to recover the possibility to root. Any way to do that? God I feel dumb right now...
Edit: I've gotten ADB to recognize the phone in Recovery Mode by installing the exact Manufacturer and Model ADB drivers but the second I get into Fastboot mode, it's like the side USB-C suddenly becomes non-existent, same goes for the bottom one. Feels like a kill.switch from ASUS to me :/
Edit 2: Is there a way to flash while in Recovery? Or in normal OS operations? (sounds like a bad idea but I'm out of ideas as of now)
So neither of the two USB ports in the phone seem to work for you in bootloader mode?
dennis96411 said:
So neither of the two USB ports in the phone seem to work for you in bootloader mode?
Click to expand...
Click to collapse
Exactly, the bootloader is also unlocked after using ASUS's tool .apk, I am on 1910.44 WW, I tried different ADB's while in Windows, tried to copy DeviceID, it all works when in normal boot OR in recovery mode but the second I am in fastboot mode, both USB's stop working. As if ASUS locked the access when I mistakenly tried to gain root while the bootloader was locked. Maybe if I could lock it back but that would require me being in fastboot afaik.
Can I lock it back while in recovery? If so, what would be the prompt?
I would be very careful about locking the bootloader at this point. I heard it can cause a brick if the planets aren't aligned correctly.
Jokes aside, does device manager refresh itself when you plug or unplug the phone in fastboot mode? That would indicate it saw something from the phone.
dennis96411 said:
I would be very careful about locking the bootloader at this point. I heard it can cause a brick if the planets aren't aligned correctly.
Jokes aside, does device manager refresh itself when you plug or unplug the phone in fastboot mode? That would indicate it saw something from the phone.
Click to expand...
Click to collapse
Sadly no, tried 3 different computers, a plethora of cables, different USB ports. It's like the Fastboot killed the function altogether so as of now, I have yet to find a way to get the phone recognized while in fastboot.
WhyKlwd said:
Sadly no, tried 3 different computers, a plethora of cables, different USB ports. It's like the Fastboot killed the function altogether so as of now, I have yet to find a way to get the phone recognized while in fastboot.
Click to expand...
Click to collapse
Is there an option to apply a full OTA from the stock recovery?
dennis96411 said:
Is there an option to apply a full OTA from the stock recovery?
Click to expand...
Click to collapse
Before anything, thanks for helping, it's greatly appreciated!
So, no sadly, when I get in Recovery Mode my options are:
Reboot system now
Reboot to bootloader
Wipe data/factory reset
Power off
As anyone would, I tried kicking into bootloader from recovery hoping that it would trigger something different to give me fastboot but to no avail, I wiped a couple of times as well, that didn't pan out.
Edit: I feel like my best chance at this point is when ASUS releases a new WW firmware update, that it HOPEFULLY brings Fastboot Mode to it's original value... But according to a thread somewhere on XDA, it does not install a full partitioned recovery so I'm not having my hopes up...
The other thing would be to butcher a USB-C cable and see if I get a response when connected on the orange USB-C but that's also a risk to take. So that doesn't work, that USB-C gets no response whatsoever.
What firmware version are you on? You could try grabbing the stock firmware zip of the firmware you're on now from https://www.asus.com/Phone/ROG-Phone-II/HelpDesk_Download/, and increase the firmware version in the zip name - for example, if you're on the latest .44 build now, change the .44 in the zip name to .45. Then simply push it to the root of your internal storage, and reboot. After boot you should get a message that a system update file has been found, and that you can install it.
I don't know if this will fix your problem, but it should reflash the stock partitions. And yes, it's true that it far from flashes all partitions, but it's worth a try at least.
HomerSp said:
What firmware version are you on? You could try grabbing the stock firmware zip of the firmware you're on now from https://www.asus.com/Phone/ROG-Phone-II/HelpDesk_Download/, and increase the firmware version in the zip name - for example, if you're on the latest .44 build now, change the .44 in the zip name to .45. Then simply push it to the root of your internal storage, and reboot. After boot you should get a message that a system update file has been found, and that you can install it.
I don't know if this will fix your problem, but it should reflash the stock partitions. And yes, it's true that it far from flashes all partitions, but it's worth a try at least.
Click to expand...
Click to collapse
I did put the stock firmware but I hadn't thought of changing the name to "force" the phone to try and update! Sadly, when it reached 100%, it said install failed and while trying fastboot mode, it still didn't restore ADB but that was brilliant and definitely worth the try. Thanks for your suggestion, here's hoping the next legit firmware will do it!
EDIT: AND YET IT DID WORK!!! That must have fixed it after all... I unplugged, replugged while in bootloader and finally, that USB chime! T-T
Thanks both of you for your suggestions, 3 brains work better than one!
WhyKlwd said:
I did put the stock firmware but I hadn't thought of changing the name to "force" the phone to try and update! Sadly, when it reached 100%, it said install failed and while trying fastboot mode, it still didn't restore ADB but that was brilliant and definitely worth the try. Thanks for your suggestion, here's hoping the next legit firmware will do it!
EDIT: AND YET IT DID WORK!!! That must have fixed it after all... I unplugged, replugged while in bootloader and finally, that USB chime! T-T
Thanks both of you for your suggestions, 3 brains work better than one!
Click to expand...
Click to collapse
Nice, glad to see it worked! I tried it myself and it also said update failed, but it had flashed, so I think the error message may just be because the firmware version doesn't change.
I'm assuming fastboot works now then? Do keep in mind that you'll need the abl, xbl and xbl_config images from the edl unlock thread to be able to actually unlock the bootloader without using the Asus tool.
HomerSp said:
Nice, glad to see it worked! I tried it myself and it also said update failed, but it had flashed, so I think the error message may just be because the firmware version doesn't change.
I'm assuming fastboot works now then? Do keep in mind that you'll need the abl, xbl and xbl_config images from the edl unlock thread to be able to actually unlock the bootloader without using the Asus tool.
Click to expand...
Click to collapse
Yeah it works, or at least it did long enough for me to be able to root. I haven't tried it since but I would assume that it fixed it, tomorrow I'll most likely do a RAW flash to fix all potential risks as well as try the latest CN firmware. EDL never worked, that's what got me in that situation in the first place... well that and me not paying full attention.
Hey everybody
My friend gave me his Mi 9t Pro to repair it as he bricked it accidentally and he knew I had experience with changing ROMs and recoveries.
From what I know, what he did is tried to change dpi and then phone jumped into bootloop.
Let me just state that:
- bootloader is locked
- there is no custom recovery
- I have no authorization for ADB
I am stuck and would be really thankful for any ideas. Wiping data is not an option at the moment as we want to recover data from the phone.
Dropping battery to 0% and then charging didn't work.
Adb is only possible at the very short moment phone gets into boot animation, but as I have no authorization I can't pull files from it.
For whatever I tried ADB sideload when connected with Mi Assistant in recovery didn't help me neither.
If you have any ideas please share them with me, I'll appreciate that a lot
Hilus said:
Hey everybody
My friend gave me his Mi 9t Pro to repair it as he bricked it accidentally and he knew I had experience with changing ROMs and recoveries.
From what I know, what he did is tried to change dpi and then phone jumped into bootloop.
Let me just state that:
- bootloader is locked
- there is no custom recovery
- I have no authorization for ADB
I am stuck and would be really thankful for any ideas. Wiping data is not an option at the moment as we want to recover data from the phone.
Dropping battery to 0% and then charging didn't work.
Adb is only possible at the very short moment phone gets into boot animation, but as I have no authorization I can't pull files from it.
For whatever I tried ADB sideload when connected with Mi Assistant in recovery didn't help me neither.
If you have any ideas please share them with me, I'll appreciate that a lot
Click to expand...
Click to collapse
I can't see any way you're going to keep the data. Recovering the phone is going to wipe everything. Without an unlocked bootloader I can't see any way your going to be able to access the data first before restoring the phone.
As far as restoring the phone, if you can access the official recovery, then you should, hopefully, be able to flash an official recovery ROM from there, or so I believe, I've never actually tried it.
If that fails, then you will need to EDL flash the phone.
This involves taking off the back to put the phone in EDL mode, then paying someone, who has an authorised account, to remotely flash the phone for you.
Robbo.5000 said:
I can't see any way you're going to keep the data. Recovering the phone is going to wipe everything. Without an unlocked bootloader I can't see any way your going to be able to access the data first before restoring the phone.
As far as restoring the phone, if you can access the official recovery, then you should, hopefully, be able to flash an official recovery ROM from there, or so I believe, I've never actually tried it.
If that fails, then you will need to EDL flash the phone.
This involves taking off the back to put the phone in EDL mode, then paying someone, who has an authorised account, to remotely flash the phone for you.
Click to expand...
Click to collapse
Yeah, that's kinda hard situation :/
I can't really flash recovery ROM, cause official recovery has no option for that and adb sideload didn't want to install 'update.zip'. just rebooted the phone and that's all.
I've seen that it's actually possible to put device into EDL without having to disassemble the phone, but fastboot command just reboots the phone.
Thanks for answering either way
Hilus said:
Yeah, that's kinda hard situation :/
I can't really flash recovery ROM, cause official recovery has no option for that and adb sideload didn't want to install 'update.zip'. just rebooted the phone and that's all.
I've seen that it's actually possible to put device into EDL without having to disassemble the phone, but fastboot command just reboots the phone.
Thanks for answering either way
Click to expand...
Click to collapse
Have you tried updating ROM through Mi PC Suite (latest version)?
0xFast said:
Have you tried updating ROM through Mi PC Suite (latest version)?
Click to expand...
Click to collapse
I tried through MiFlash, but it only allows fastboot ROMs, and because bootloader is not unlocked I couldn't flash it. But that's a good idea, I'll try Mi PC Suite, I'll let you know how it ends.
0xFast said:
Have you tried updating ROM through Mi PC Suite (latest version)?
Click to expand...
Click to collapse
I tried, but seeing that mipcsutie is same program as mi assistant, I cannot do anything because it doesn't recognize my phone.
Which version? I'm using https://c.mi.com/thread-1015363-1-0.html on Redmi 6 (locked bootloader & bootloop) and successfully restore. Make sure you've correct driver installed.
---------- Post added at 12:13 AM ---------- Previous post was at 12:10 AM ----------
Because not possible if your bootloader was locked to enter EDL mode, then AFAIK you need Mi Account with authorization to flashing with EDL mode.
Hilus said:
I've seen that it's actually possible to put device into EDL without having to disassemble the phone, but fastboot command just reboots the phone.
Click to expand...
Click to collapse
Are you talking phones in general, or this phone specifically. For this phone the only way is to take the back off and do the 'Test point' method. I've never heard of anyone successfully entering EDL mode using any other method.
Hilus said:
I can't really flash recovery ROM, cause official recovery has no option for that and adb sideload didn't want to install 'update.zip'. just rebooted the phone and that's all.
Click to expand...
Click to collapse
ADB sideload needs the phone to be put into ADB sideload mode first, so to speak. This is why you have the ADB sideload option in TWRP. You don't have this option in the standard recovery.
Hilus said:
I tried, but seeing that mipcsutie is same program as mi assistant, I cannot do anything because it doesn't recognize my phone.
Click to expand...
Click to collapse
0xFast said:
Which version? I'm using https://c.mi.com/thread-1015363-1-0.html on Redmi 6 (locked bootloader & bootloop) and successfully restore. Make sure you've correct driver installed.
Click to expand...
Click to collapse
Also make sure you're using a good USB cable and also try a different USB port.
Also try using your friends PC. I assume they have previously connected the phone to the PC successfully before, so they should have the correct drivers already installed.
Robbo.5000 said:
Are you talking phones in general, or this phone specifically. For this phone the only way is to take the back off and do the 'Test point' method. I've never heard of anyone successfully entering EDL mode using any other method.
ADB sideload needs the phone to be put into ADB sideload mode first, so to speak. This is why you have the ADB sideload option in TWRP. You don't have this option in the standard recovery.
Also make sure you're using a good USB cable and also try a different USB port.
Also try using your friends PC. I assume they have previously connected the phone to the PC successfully before, so they should have the correct drivers already installed.
Click to expand...
Click to collapse
If you connect via 'Mi Assistan' option in recovery the phone connects to pc using adb sideload.
I tried different cables and ports, and I have correct drivers.
0xFast said:
Which version? I'm using https://c.mi.com/thread-1015363-1-0.html on Redmi 6 (locked bootloader & bootloop) and successfully restore. Make sure you've correct driver installed.
---------- Post added at 12:13 AM ---------- Previous post was at 12:10 AM ----------
Because not possible if your bootloader was locked to enter EDL mode, then AFAIK you need Mi Account with authorization to flashing with EDL mode.
Click to expand...
Click to collapse
As I mentioned before, I am not able to enable USB debugging, which is required for this program to work as far as I can see.
Hilus said:
As I mentioned before, I am not able to enable USB debugging, which is required for this program to work as far as I can see.
Click to expand...
Click to collapse
In this case your only option now is to EDL flash. Sorry. Search for guides on how to do this, within these forums. XDA admins have been removing contact details of anyone with an authorised account, who will remotely flash for you. These people charge for doing this, so it's against XDA policy to give details of people who perform paid for services. You will find recent posts from people who've got details of these people who can EDL flash, that will kindly allow you too PM them for details of such persons.
Hilus said:
As I mentioned before, I am not able to enable USB debugging, which is required for this program to work as far as I can see.
Click to expand...
Click to collapse
AFAIK, USB debugging not required just adb sideload to work.
Have you tried looking at the .bat files miflash executes from the fastboot images. You can flash system etc.. without dating perhaps this will reset the dpi