Is there a possibility to enter stock recovery via USB cable and ADB in SW Upgrade Mode?
Can anyone check this as my phone is in repair centre?
1. Turn off the phone
2. Connect USB cable with Vol+ button (phone enters in SW Update mode)
3. Open command prompt and from ADB folder type "adb reboot recovery"
4. Is this working?
I'll be very grateful if someone would check this. Thanks in advance.
Please, it is very urgent. If it works I could today pick-up phone from my Operator before they send it to repair. They're sending it tommorow.
Much thanks and sorry for double posting...
EDIT:
@fjsw: thanks for checking.
No it doesn't work
output:
error: device not found
I'm in recovery...
I turned on my bricked OB, waiting for bootloop, plug USB and "adb reboot recovery"
Sorry for my bad english
edit: I inserted some files from Nova v8zip to CM7-SelfKANG4.zip and flashed this edited CM.zip... Bootloop, plug USB and "adb reboot recovery" .. but, I flashed again CM.zip, now no-edited, reboot system from recovery and i got Error sreen.. So I flash firmware with http://forum.xda-developers.com/showthread.php?t=1111771
AFAIK it doesn't work. I tried it too (when i bricked my OB {CM7-->stock} but it didn't work!
Wow it's been an "old-time" thread to reply, since the first post August 7, 2011. yet it still replied today.
AFAIK, "Android Debug Bridge" need operating system to run (to debug). It need USB Debugging that running with Android, so ADB can't run without Android OS running..
CMIIW.
redy2006 said:
Wow it's been an "old-time" thread to reply, since the first post August 7, 2011. yet it still replied today.
AFAIK, "Android Debug Bridge" need operating system to run (to debug). It need USB Debugging that running with Android, so ADB can't run without Android OS running..
CMIIW.
Click to expand...
Click to collapse
Exactly. I think AntoSVK isn't right. He should edit his post and accurately describe his case...
How to unlock Lg-Ku5900.
radkor said:
Exactly. I think AntoSVK isn't right. He should edit his post and accurately describe his case...
Click to expand...
Click to collapse
How to unlock Lg-Ku5900 .Screen, must enter your email and password.
kanokphone said:
How to unlock Lg-Ku5900 .Screen, must enter your email and password.
Click to expand...
Click to collapse
Do a search before you post...
http://forum.xda-developers.com/showthread.php?t=1448803
This also will remove phone lock if you forget unlock code or pattern.
Click to expand...
Click to collapse
Related
ok here is what i have done
rooted and cwm after unlocking boot loader then installed arhd 3.5
relocked bootloader to return to stock then tried to flash the rru file but it wouldnt work phone wouldnt boot so unlocked bootloader again but now stuck on start up screen
is it fixable or have i broken it altogether ??
thanks
can you get into recovery?
MacHackz said:
can you get into recovery?
Click to expand...
Click to collapse
yes i can get to cwm recovery but i have no file to flash as i deleted it after it installed correctly also my cwm backup is on my hdd as well
First wrong sector to post
Second download the All In One Toolkit and push your .zip via adb to your phone
m3dd0g said:
First wrong sector to post
Second download the All In One Toolkit and push your .zip via adb to your phone
Click to expand...
Click to collapse
ohh ok i didnt know ...where should i post
tried to do that says device not found ........but when i use normal fastboot devices command it shows a serial number
grud1e said:
ohh ok i didnt know ...where should i post
tried to do that says device not found ........but when i use normal fastboot devices command it shows a serial number
Click to expand...
Click to collapse
Go to cwm, press install zip from sideload, then on your pc type 'adb sideload <filename of update.zip>'
MacHackz said:
Go to cwm, press install zip from sideload, then on your pc type 'adb sideload <filename of update.zip>'
Click to expand...
Click to collapse
thanks i tried that and i just get a load of text showing in the cmd box but nothing happens text show various adb commands but funnily enough shows no sideload command ??
grud1e said:
thanks i tried that and i just get a load of text showing in the cmd box but nothing happens text show various adb commands but funnily enough shows no sideload command ??
Click to expand...
Click to collapse
Can you post a screenshot, or host a meeting on TeamViewer so I can see/help?
MacHackz said:
Can you post a screenshot, or host a meeting on TeamViewer so I can see/help?
Click to expand...
Click to collapse
yes i can dl team viewer and host a meeting ....you prefer mac or windows
grud1e said:
yes i can dl team viewer and host a meeting ....you prefer mac or windows
Click to expand...
Click to collapse
Mac is best, just PM me or whatever with the meeting code
MacHackz said:
Mac is best, just PM me or whatever with the meeting code
Click to expand...
Click to collapse
aye mac is best just plugged it into another usb and its side loading right now so hopefully it will be ok perhaps it dont like usb 3 for some reason
i will let you know how it goes
thanks
grud1e said:
aye mac is best just plugged it into another usb and its side loading right now so hopefully it will be ok perhaps it dont like usb 3 for some reason
i will let you know how it goes
thanks
Click to expand...
Click to collapse
Good news sometimes USB ports play up, I have a bad history with them. Once one malfunctioned during a re-partition of my old Galaxy S2 and bricked it -.-
PHEW
MacHackz said:
Good news sometimes USB ports play up, I have a bad history with them. Once one malfunctioned during a re-partition of my old Galaxy S2 and bricked it -.-
Click to expand...
Click to collapse
yippee not bricked returned to working ...thanks for you help
grud1e said:
yippee not bricked returned to working ...thanks for you help
Click to expand...
Click to collapse
Great enjoy
Moved to Q&A for you. Remember, all questions go in Q&A and never in development.
So have you managed to return it to stock after?
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,
I tried to reboot and it is stopped at the LG screen as shown in the attach photo. I dont know what to do now, as I think it cant even connect and to the dock (still charging but not recognised at all by the PC). It would be great and very appreciated if anyone knows what I need to do? Otherwise it is an expensive paperweight now.
Thanks in advance.
P/S: This is my 1st post in XDA, so if anything wrong with my post please let me know, I will change. Thanks again.
Update
I managed to make it work again. this is what you have to do is boot it to bootloader mode, then go to recovery mode and use the "apply update from adb" function (sideload in other words) to install the Android 6.0.1 again.
Link to download Android 6.0.1.
To put the watch in bootloader mode, follow the instruction in my youtube video here.
As soon as it is in bootloader mode, your computer should see the watch as an android device now.
In Bootloader mode, go to recovery mode (use the virtual buttons on screen), then go to the "apply update from adb" option.
Now, at this step, you need to open command line on your computer and type "adb sideload <android file>", where the <android file> is the one you download earlier. You can just type "adb sildeload" then leave a space and drag the file to the running Cmd window.
Now just wait for it to complete and restart itself.
Hope this helps.
This may not help, but try pressing the side button in for 20-30 seconds. Shortly after it stops vibrating, it will start rebooting again and then you can stop pressing the button.
JimSmith94 said:
This may not help, but try pressing the side button in for 20-30 seconds. Shortly after it stops vibrating, it will start rebooting again and then you can stop pressing the button.
Click to expand...
Click to collapse
Hi, I think I messed up with the wrong kernel is the reason of this issue, and I have been able to get to the fastboot menu, do you know how revert it back to the factory/out of box condition? Thanks.
I haven't tried this, but it may work for you: http://forum.xda-developers.com/wat...recovery-stock-recovery-image-v1-1-1-t3124452
JimSmith94 said:
I haven't tried this, but it may work for you: http://forum.xda-developers.com/wat...recovery-stock-recovery-image-v1-1-1-t3124452
Click to expand...
Click to collapse
Thanks for ur help. I have manage to make it works again.
johnnyle7 said:
Thanks for ur help. I have manage to make it works again.
Click to expand...
Click to collapse
Please let us know how you did it, in case or when I or others need to do the same.
JimSmith94 said:
Please let us know how you did it, in case or when I or others need to do the same.
Click to expand...
Click to collapse
should I update my post with the solution?
johnnyle7 said:
should I update my post with the solution?
Click to expand...
Click to collapse
Either that or post a new reply. I know we would appreciate it.
johnnyle7 said:
I tried to reboot and it is stopped at the LG screen as shown in the attach photo. I dont know what to do now, as I think it cant even connect and to the dock (still charging but not recognised at all by the PC). It would be great and very appreciated if anyone knows what I need to do? Otherwise it is an expensive paperweight now.
Thanks in advance.
P/S: This is my 1st post in XDA, so if anything wrong with my post please let me know, I will change. Thanks again.
Update
I managed to make it work again. this is what you have to do is boot it to bootloader mode, then go to recovery mode and use the "apply update from adb" function (sideload in other words) to install the Android 6.0.1 again.
to download Android 6.0.1.
To put the watch in bootloader mode, follow the instruction in my youtube video here.
As soon as it is in bootloader mode, your computer should see the watch as an android device now.
In Bootloader mode, go to recovery mode (use the virtual buttons on screen), then go to the "apply update from adb" option.
Now, at this step, you need to open command line on your computer and type "adb sideload <android file>", where the <android file> is the one you download earlier. You can just type "adb sildeload" then leave a space and drag the file to the running Cmd window.
Now just wait for it to complete and restart itself.
Hope this helps.
Click to expand...
Click to collapse
Hi There,
I have the same problem after the update.
I followed your steps but to enter into recovery mode I had to enable USB debugging mode which cannot be done as the watch keeps on rebooting.
Please let me know is there any other way to enable usb debugging mode to enter into recovery?
I get this error on my pc when I enter into recovery " error device '(null)' not found adb"
rayyansyed said:
Hi There,
I have the same problem after the update.
I followed your steps but to enter into recovery mode I had to enable USB debugging mode which cannot be done as the watch keeps on rebooting.
Please let me know is there any other way to enable usb debugging mode to enter into recovery?
I get this error on my pc when I enter into recovery " error device '(null)' not found adb"
Click to expand...
Click to collapse
Can anybody help me out in bringing my watch to life?
Great post. . . .
Driver Issue
I can get into the fastboot menu but my pc cannot recognize it. What is the appropriate method to connecting it. I have tried different cables, google driver, adb driver but the device doesnt even show up.
Can anyone help me how to unlock the bootloader via fastboot since I cannot get in the software as I have a bootloop. I greatly appreciate it as I have been figuring out this for the past 5 hours. Thank you.
Hello Guys, I messed up as I did not unlock bootloader first before flashing it from fastboot. Now I have a bootloop. Can anyone help me how to reflash CN. I have a lock bootloader. Thank you very much.
Anybody?? Please help.
Any other phone if you don't flick oem unlock first in developer ootions it's a hardbrick. The Asus unlock tool apk does this. Did you install that first and unlock first? Hope you can recover
Sent from my ASUS_Z01QD using Tapatalk
DanXbix said:
Any other phone if you don't flick oem unlock first in developer ootions it's a hardbrick. The Asus unlock tool apk does this. Did you install that first and unlock first? Hope you can recover
Sent from my ASUS_Z01QD using Tapatalk
Click to expand...
Click to collapse
I totally forgot to unlock first from the Asus Apk. I am hoping I can Unbrick it. Thank you.
tzdu25 said:
I totally forgot to unlock first from the Asus Apk. I am hoping I can Unbrick it. Thank you.
Click to expand...
Click to collapse
You're FUBAR for now, nobody has figured out a way to flash the phone without an unlocked bootloader. Just use it as a brick until someone finds out QDL9008 or other ways to flash it.
Your's ROG 2 can be boot into recovery mode?
If you can -- "adb sideload software.zip"
nenebear said:
Your's ROG 2 can be boot into recovery mode?
If you can -- "adb sideload software.zip"
Click to expand...
Click to collapse
you can't with locked bootlader
hashcheck said:
you can't with locked bootlader
Click to expand...
Click to collapse
Now. With rog phone 2, although unlock booloader, you still cant flash zip file via recovey mode
That's correct, I tried ADB sideloading zip files but getting a fail message.
tzdu25 said:
That's correct, I tried ADB sideloading zip files but getting a fail message.
Click to expand...
Click to collapse
Yes. Is lock
Your only option is to go to ASUS service center in your area and ask them to repair it. If they accept to service it they will of course charge you for it which is better than having a bricked phone. Other than that your only option is to send the phone back to China there you can claim that the phone got a bootloop and since you didn't unlock the bootloader you are still covered by warranty meaning you will only pay shipping fees.
Thank you Rashad83. I just sent it to Asus Service Center with a fee.
Did you guys changing the Boot Slot?
Check your current boot slot by hitting -
fastboot oem device-info
Then change the slot to "B" if you're currently in "A"
Slot change command -
fastboot set_active_b
tzdu25 said:
Thank you Rashad83. I just sent it to Asus Service Center with a fee.
Click to expand...
Click to collapse
Now, i can fixed
Guys, Please obtain an ASUS Raw firmware to recover your devices. Do not fall for tricks by various users around which asks to pay for them.
Just use Google and find yourself the correct RAW firmware for your model.
tzdu25 said:
Can anyone help me how to unlock the bootloader via fastboot since I cannot get in the software as I have a bootloop. I greatly appreciate it as I have been figuring out this for the past 5 hours. Thank you.
Click to expand...
Click to collapse
Check Here
Hi, I've managed to unbrick my ROG Phone II Tencent Edition 8/128 with a locked bootloader having "slot _a" error. Link to other thread: https://forum.xda-developers.com/rog-phone-2/how-to/repair-rog2-phone-edl-modeofficial-t4012175
My equipment for flashing, for sure you already have ADB installed in your computer, my computer is an x64 Intel Windows 10 laptop, I used USB 2.0 not USB 3.0
Credit to @johnny886 for the sharing the tool,
"If your phone can only enter EDL mode (9008 mode)
this firmware is glad to help you. It can be flashed in through
the QPST tool, or it can be flashed in through the Xiaomi miflash tool.
To use the QPST tool, you must change the EMMC to UFS. No matter which tool you use, -(I personally did not use this, I just downloaded the file and followed grewookie's instruction below)
you must restore the factory settings after the phone is turned on, otherwise the storage
of the phone will recognize the error! !! !!
Factory settings must be restored after booting! !! !!
The firmware is made through the official package UL-ASUS_I001_1-ASUS-16.0631.1910.35-1.1.207-user.zip
without any modification, Suitable for repairing phones that can only enter edl mode(9008 mode).
File Downlaod link: https://drive.google.com/open?id=1Pk...Sf6cDq7SuJiBBu"
Credits to @greywookiee for the super clear instruction:
"Here's some instructions I put together that would have helped save me a lot of time. Please correct anything I missed:
After you have downloaded the zip file, here are the step-by-step instructions:
1. Extract the zipped folder wherever you want on your PC.
2. Open a CMD window.
3. cd /d <whatever path it is to the "\ASUS_ROG2_ZS660KL_QPST_Firmware\images" folder> e.g., "cd /d D:\RogPhoneII\ASUS_ROG2_ZS660KL_QPST_Firmware\imag es"
4. Make sure your PC is connected to the side port of your phone and the phone is in fastboot mode (Volume UP button + Power button).
5. Check and make sure your PC is connected properly by entering "fastboot devices" in the command window. You should see the ID of your device.
6. Then enter "fastboot oem enter-dload" in the command window. This will put the phone in emergency download mode (EDL). My phone went all black.
7. Open "\ASUS_ROG2_ZS660KL_QPST_Firmware\MiFlash2018-5-28-0" folder. Launch "XiaoMiFlash.exe".
8. Click "refresh". You should see a device in the list.
9. Click "select" and navigate to the "\ASUS_ROG2_ZS660KL_QPST_Firmware\images" folder.
10. Click "flash". Wait until it says "success".
11. After it's done, you'll hold down the UP button, Down button, and Power button on the phone at the same time until it shuts down.
12. Hold Up button and Power button at same to boot into fastboot mode again. Select Recovery mode by using the Up/Down buttons on the phone. Press the Power button to select.
13. Select "wipe data" from the drop down list. Go down the list of "no" until you get to the "yes" and press the Power button.
14. Select "reboot now".
15. Done."
Rashad83 said:
Your only option is to go to ASUS service center in your area and ask them to repair it. If they accept to service it they will of course charge you for it which is better than having a bricked phone. Other than that your only option is to send the phone back to China there you can claim that the phone got a bootloop and since you didn't unlock the bootloader you are still covered by warranty meaning you will only pay shipping fees.
Click to expand...
Click to collapse
How to send a phone to China for a warranty contacts
Methods and as many details as possible
So I could send mine from Canada as well
I am in warranty but I am not in China.
---------- Post added at 02:16 PM ---------- Previous post was at 02:15 PM ----------
dungnghien said:
Now, i can fixed
Click to expand...
Click to collapse
Can you please help me warranty claim this phone in China. Please.
I have an expensive brick laying around.
So using a root app disabler I disabled "telephony service" and when I restarted it shutdown immediately, on the newest WW rom it doesnt have a recovery so I cant go in there and wipe to factory reset. Right now I'm getting slot_b is unbootable. My computer recognizes the phone as "Android Bootloader Interface" but when I run "adb devices" it doesnt show up and I cant run fastboot commands even though I'm plugged into the side usb port. Please help me.
trustedenemy said:
So using a root app disabler I disabled "telephony service" and when I restarted it shutdown immediately, on the newest WW rom it doesnt have a recovery so I cant go in there and wipe to factory reset. Right now I'm getting slot_b is unbootable. My computer recognizes the phone as "Android Bootloader Interface" but when I run "adb devices" it doesnt show up and I cant run fastboot commands even though I'm plugged into the side usb port. Please help me.
Click to expand...
Click to collapse
Was the boot img rooted, is that why you have no recovery? If so, just boot to fastboot mode and flash stock boot instead of root, that should have recovery
trustedenemy said:
So using a root app disabler I disabled "telephony service" and when I restarted it shutdown immediately, on the newest WW rom it doesnt have a recovery so I cant go in there and wipe to factory reset. Right now I'm getting slot_b is unbootable. My computer recognizes the phone as "Android Bootloader Interface" but when I run "adb devices" it doesnt show up and I cant run fastboot commands even though I'm plugged into the side usb port. Please help me.
Click to expand...
Click to collapse
Can you go to bootloader screen ?
If you can
Just use the full stock Rom
Flash it
---------- Post added at 04:45 PM ---------- Previous post was at 04:42 PM ----------
https://drive.google.com/file/d/1M2V1Jh2CS5vt1xbQYlDvhxfu0yB6hmZi/view
Download the Full Rom
Extract it
Use the exe file to install with bootloader screen
Ok that was able to get me back to recovery, I tried to wipe and then boot into android, didn't work got the "your device is corrupt and cannot be trusted and will not boot". Still isn't recognized in adb devices so I don't know how I would proceed from here. My device is the Tencent Edition if that helps with raw firmware/rom.
P.S Thank you guys so much for your help I really appreciate it.
trustedenemy said:
Ok that was able to get me back to recovery, I tried to wipe and then boot into android, didn't work got the "your device is corrupt and cannot be trusted and will not boot". Still isn't recognized in adb devices so I don't know how I would proceed from here. My device is the Tencent Edition if that helps with raw firmware/rom.
P.S Thank you guys so much for your help I really appreciate it.
Click to expand...
Click to collapse
Did you fix it ?
rowihel2012 said:
Did you fix it ?
Click to expand...
Click to collapse
No, I still cannot boot into android and it still isnt recognized in adb devices, but I can get into recovery now.
trustedenemy said:
No, I still cannot boot into android and it still isnt recognized in adb devices, but I can get into recovery now.
Click to expand...
Click to collapse
But you get fastboot mode, just plug the USB in side port and flash latest raw WW Rom.
Here's the link to 1908.21
https://drive.google.com/file/d/13Mgz9GhopE-DUsGT3N_5qC283cKkUxYb/view?usp=drivesdk
Once in fastboot mode (the first menu you see, before selecting recovery, start, power off etc is fastboot mode) check your device is recognised with fastboot devices cmd and then run flashall_AFT.cmd that'll get back your working rom . But also, delete or move the original zip from that same extracted folder, the raw rom with the same name confuses the flashall_AFT.cmd
So I flash the most recent firmware you linked and double checked in recovery that it was pushed to the device and it was, but when I try to boot into android I get the asus logo for a second and then it restarts and it will give me a screen that says "Your device is corrupt. It cant be trusted and will not boot" and then has a link to google support .
trustedenemy said:
So I flash the most recent firmware you linked and double checked in recovery that it was pushed to the device and it was, but when I try to boot into android I get the asus logo for a second and then it restarts and it will give me a screen that says "Your device is corrupt. It cant be trusted and will not boot" and then has a link to google support .
Click to expand...
Click to collapse
Did you let the raw rom flash entirely? It should take a minimum of 10 minutes... The phone should reboot twice (I think) as it completes... Maybe try again, but I'm not familiar with that message...
If the phone doesn't reboot, I would let it run for a half hour or so before rebooting...
There we go, I got it to work man, I was just being impatient with the firmware flash but now I got it to work I appreciate your help and patience so much let me got through and thank your comments and then you can flag a mod to take down this thread. Thank you
trustedenemy said:
There we go, I got it to work man, I was just being impatient with the firmware flash but now I got it to work I appreciate your help and patience so much let me got through and thank your comments and then you can flag a mod to take down this thread. Thank you
Click to expand...
Click to collapse
Excellent, glad you got it working again
trustedenemy said:
There we go, I got it to work man, I was just being impatient with the firmware flash but now I got it to work I appreciate your help and patience so much let me got through and thank your comments and then you can flag a mod to take down this thread. Thank you
Click to expand...
Click to collapse
Yes this way always fix bootloap problem
Thanks asus for this easy flashing