Related
Anyone know of a way to get into recovery mode (botton combo, one-click, etc.) on the 10.1 tab without having android sdk and adb installed on my PC? I am not new at flashing files in recovery mode, but going through help files/instructions on adk is a bit overwhelming.
I have the root zip file on my tab, I just need to get into recovery mode to flash it.
Thanks in advance...
It isn't possible without adb on a non-rooted device. You can attempt to boot into recovery mode by holding power and volume down on start up and selecting the android guy with "downloading" but it will say: "waiting for usb" and hang there. I was attempting to do this the other night.
Getting into recovery is dead simple though once you have adb going. Go to the android development section and go to rooting your tablet. Download the drivers > connect to the computer > run adb in command prompt once you have your sdk installed > then if you have your drivers fully installed and usb debugging mode is on just type in command prompt "adb reboot recovery" and it will send you directly to recovery mode to flash any zip file you please.
Thx, Really wish someone had a one-click option, I guess i'll just have to jump in
I've been trying to boot into recovery for a while now, but with no luck. I installed the full SDK platform, and the Manager app downloaded and installed all the available packages (took forever). The 'push' command seemed to work fine, and when I do "adb reboot recovery" the tablet reboots, but just goes into the battery charging screen. Any idea why this might be happening, and what I can do to get into recovery?
kentoe said:
It isn't possible without adb on a non-rooted device. You can attempt to boot into recovery mode by holding power and volume down on start up and selecting the android guy with "downloading" but it will say: "waiting for usb" and hang there. I was attempting to do this the other night.
Getting into recovery is dead simple though once you have adb going. Go to the android development section and go to rooting your tablet. Download the drivers > connect to the computer > run adb in command prompt once you have your sdk installed > then if you have your drivers fully installed and usb debugging mode is on just type in command prompt "adb reboot recovery" and it will send you directly to recovery mode to flash any zip file you please.
Click to expand...
Click to collapse
The mode that says "downloading" is not recovery mode. Just select the one on the left and you will get into stock recovery mode (unless you already have Clockwork installed).
Itaintrite said:
The mode that says "downloading" is not recovery mode. Just select the one on the left and you will get into stock recovery mode (unless you already have Clockwork installed).
Click to expand...
Click to collapse
I managed to do that, but it wouldn't show anything on my '/sdcard' directory, even when I renamed the root package to "update.zip"
In red, it says "E:unknown volume for path [/sdcard]" Not sure if I'm getting into real, stock recovery, or what - seems crazy that stock wouldn't be able to access its own sdcard directory.
Battery not recovery mode
I am in a similar situation, when I use adb to run recovery mode it sends me to teh battery charging screen. With the exception of that they only other things I can do are to hold power and vol to get option of using Fastboot or ODIN. I do not have any options ever to chose to go into recovery mode. Anyone know why this may be? I am running 3.1 IO version.
Thanks
You will need fastboot and recovery.img to boot into recovery in order to perform a factory reset.
Installing the sdk works best, as drivers needed are acquired from the process! ELse there are extracted contents available on net including just the drivers, adb (and fastboot!)
Check my thread #9
http://forum.xda-developers.com/show....php?t=1136958
bakobitz said:
I managed to do that, but it wouldn't show anything on my '/sdcard' directory, even when I renamed the root package to "update.zip"
In red, it says "E:unknown volume for path [/sdcard]" Not sure if I'm getting into real, stock recovery, or what - seems crazy that stock wouldn't be able to access its own sdcard directory.
Click to expand...
Click to collapse
I don't think the stock retail recovery is capable of flashing off SD storage. That's why the current rooting methods have you first flash either I/O recovery or a custom recovery.
Berner said:
I don't think the stock retail recovery is capable of flashing off SD storage. That's why the current rooting methods have you first flash either I/O recovery or a custom recovery.
Click to expand...
Click to collapse
The manual says to press the power and UP VOL button to get into recovery mode for update flash or wipe data ..
Pressing power and DOWN VOL enters fastboot mode
gunzo71 said:
The manual says to press the power and UP VOL button to get into recovery mode for update flash or wipe data ..
Pressing power and DOWN VOL enters fastboot mode
Click to expand...
Click to collapse
Go ahead and let know if you are able to enter recovery with the keys combination and wipe or factory reset the device, according to manual. Did not work for me, am on 3.1 honeycomb i/o galaxy tab 10.1 and many others.
engljeff said:
Anyone know of a way to get into recovery mode (botton combo, one-click, etc.) on the 10.1 tab without having android sdk and adb installed on my PC? I am not new at flashing files in recovery mode, but going through help files/instructions on adk is a bit overwhelming.
I have the root zip file on my tab, I just need to get into recovery mode to flash it.
Thanks in advance...
Click to expand...
Click to collapse
Use the quick boot app. Works well for me. Supports power off, recovery, and normal reboot for the free version. Oh yeah but that requires root.
Sent from my GT-P7510 using Tapatalk
mughalgxt said:
Go ahead and let know if you are able to enter recovery with the keys combination and wipe or factory reset the device, according to manual. Did not work for me, am on 3.1 honeycomb i/o galaxy tab 10.1 and many others.
Click to expand...
Click to collapse
yes it did.. thats why I said try that ..
On 3.1 IO too .. though I broke it within 3 weeks
gunzo71 said:
The manual says to press the power and UP VOL button to get into recovery mode for update flash or wipe data ..
Pressing power and DOWN VOL enters fastboot mode
Click to expand...
Click to collapse
This worked for me on Rogers 4G version
Hello there,my Wave 8 HD+ stuck in android boot logo. I downloaded the wave8hd_20151105_v1.8 update thru wireless update and install, it says error in installing:
E:error in /mnt/internal_sd/adupsfota/update.zip
(Status 7)
Installation aborted.
My tablet is now in recovery mode and cant move highlight due to no volume buttons available,i can only select the "reboot system now" option.
Any other alternative for volume button so that i could just do the factory reset??
I also followed the detailed instruction on bluewave website on how to update the said Tablet thru PC but to no avail.
i emailed both the Telecom Company from where i get my Bluewave Tablet and the Bluewave Customer support but until now they stiil haven't replied yet.
thank you very much for your immediate reply.
-Jovi
jovirex said:
Hello there,my Wave 8 HD+ stuck in android boot logo. I downloaded the wave8hd_20151105_v1.8 update thru wireless update and install, it says error in installing:
E:error in /mnt/internal_sd/adupsfota/update.zip
(Status 7)
Installation aborted.
My tablet is now in recovery mode and cant move highlight due to no volume buttons available,i can only select the "reboot system now" option.
Any other alternative for volume button so that i could just do the factory reset??
I also followed the detailed instruction on bluewave website on how to update the said Tablet thru PC but to no avail.
i emailed both the Telecom Company from where i get my Bluewave Tablet and the Bluewave Customer support but until now they stiil haven't replied yet.
thank you very much for your immediate reply.
-Jovi
Click to expand...
Click to collapse
maybe try to use adb and try to push the firmware manually.. if they have a firmware download available
toolhas4degrees said:
maybe try to use adb and try to push the firmware manually.. if they have a firmware download available
Click to expand...
Click to collapse
I did use the software Rockchip Batch Tool v1.7 provided by Bluewave in their website,install the 33GT driver for my tab(Tab can now be seen by my PC and download the correct firmware update(using my serial number at the back of said tablet) still provided by Bluewave,but still error in upgrade..
i just want to know how to change the highlighted option in recovery mode so i can wipe/factory reset my Tablet disregarding the said update..
there is an option in recovery mode "recover system from back up" but i could not choose to highlight and select the option..
any alternatives for the volume button??Btw,the firmware provided by Bluewave is in ".img" format,not "zip"..
thank you so much for your reply..
-Jovi
i have the same problem, got an error after wireless update.. please help!
to fix this... use your otg cable and connect a usb mouse then reboot it once its reboot use the mouse to move into the recovery mode... wipe data and cache then select update adb sideload once inside the sideload press the power button until it reboot.. once you see the bluewave and its start to have a loading in the lower right corner.. voila... your tablet is fix ... hope it help u
ohgnevets said:
i have the same problem, got an error after wireless update.. please help!
Click to expand...
Click to collapse
wave 8hd+
jho_zep said:
to fix this... use your otg cable and connect a usb mouse then reboot it once its reboot use the mouse to move into the recovery mode... wipe data and cache then select update adb sideload once inside the sideload press the power button until it reboot.. once you see the bluewave and its start to have a loading in the lower right corner.. voila... your tablet is fix ... hope it help u
Click to expand...
Click to collapse
hello, jho_zep, thank you so much for your reply, i am now able to move the highlight to select using my mouse, but still when i try to update from ADB, it tells me to send package to the device etc.. and i also tried to press the power button, it wont reboot the system, it would only shutdown the system.. another thing, i still cant get rid of the system update. " installing system update" then error comes in, my android is down.. i tried wipe date/ factory reset, still nothing.
Thanks in advance
Do you already solve your problem? because I have now the same problem as this.
I have pressed the wireless update then it restarted and it says an Error status 7.
I don't know what to do and how to deal with this problem.
can you help me?
My nextbook tablet rk3026 has a partition named metadata that holds the recovery boot commands. You could possibly try to wipe it and do a factory reset. I don't think it actually gets mounted so you would need to find a file the same size as the partition and dd to it. Or back up your system with rockchip flash tool then using a hex editor replace all data in metadata image with zeros. Obviously be careful. Here is a tool download with included guide credits to finless at freaktab(not sure if he is here at xda) for posting it.
http://freaktab.com/forum/developme...p-your-rk-device-rom-with-the-new-rk-2-1-tool
as always BACKUP and know if you don't do it correctly you may get a brick.
thank you for the response Destructos. but that solution won't help for my freakin weird tab 33gt HD+.
I get frustrated now
Problem solved
first thing to do is make sure that you have already installed the rkchip_usb driver in your computer.
What are the requirements?
1st of course your Tablet and Cable Connector
2nd Finless ROM Flash Tool v1.37
3rd Rokchip BatchTool v1.7
4th the update image/firmware for your Bluewave 8 HD+ that is downloadable from their official website
Steps:
1. off your tablet and connect it to the computer
2. open the Finless Rom Flash, uncheck all the boxes
3. turn ON your Tablet (be attentive) and while the blue screen is starting you may NOTICE that the ROM FLASH TOOL detected your device, it says "RKAndroid Mass Storage USB". when you have read that, press immediately the "Reboot Flash mode" and your device will in black screen. but ROM Flash tool still detected your device as "RKAndroid Mass Storage USB "
4. Open the Batch Tool, (you must know how to use it) find your image, then you will notice that the CONNECTED DEVICES below have color green, in that case you may now Click UPGRADE. wait for a minute and booooom, you device is functionable again.
have a feedback if it is helpful.
P.S.
before I go to that steps, when I am stuck in RECOVERY MODE of my device, I Click the Recover from BACKUP then my tablet restarts and it turns to BOOTLOOP and repeatedly saying NO COMMAND.
PLDC said:
first thing to do is make sure that you have already installed the rkchip_usb driver in your computer.
What are the requirements?
1st of course your Tablet and Cable Connector
2nd Finless ROM Flash Tool v1.37
3rd Rokchip BatchTool v1.7
4th the update image/firmware for your Bluewave 8 HD+ that is downloadable from their official website
Steps:
1. off your tablet and connect it to the computer
2. open the Finless Rom Flash, uncheck all the boxes
3. turn ON your Tablet (be attentive) and while the blue screen is starting you may NOTICE that the ROM FLASH TOOL detected your device, it says "RKAndroid Mass Storage USB". when you have read that, press immediately the "Reboot Flash mode" and your device will in black screen. but ROM Flash tool still detected your device as "RKAndroid Mass Storage USB "
4. Open the Batch Tool, (you must know how to use it) find your image, then you will notice that the CONNECTED DEVICES below have color green, in that case you may now Click UPGRADE. wait for a minute and booooom, you device is functionable again.
have a feedback if it is helpful.
P.S.
before I go to that steps, when I am stuck in RECOVERY MODE of my device, I Click the Recover from BACKUP then my tablet restarts and it turns to BOOTLOOP and repeatedly saying NO COMMAND.
Click to expand...
Click to collapse
Why is it, when I do this, my tablet can't be detected by the software? I'm stuck on recovery mode. When it's on the blue logo, still does nothing.
I can only see my device when I look for it on Device Manager under Android Phone. Why is that? It doesn't show the "Other Devices". I've installed the driver but to no avail, still fails me. Please help. Thanks!
IMPORTANT: It appearance that Huawei is no longer going to provide bootloader unlocking services for their devices. Because of this, this guide is of no use unless you can find a way to get a code or you just held onto the code.
Hello, this is a guide for unlocking the bootloader and rooting the Huawei Ascend XT. I am writing this because the current guide is not very well written and does not contain bootloader unlock instructions. This will be split into two parts: Part 1, unlocking the bootloader, and Part 2, rooting the phone.
PLEASE NOTE THAT FOLLOWING THESE INSTRUCTIONS WILL WIPE YOUR DEVICE. I AM NOT RESPONSIBLE FOR AND DAMAGE DONE TO YOUR PHONE!
THINGS YOU WILL NEED:
1. A Huawei Ascend XT with at least 60% of battery left
2. A computer with adb drivers, fastboot drivers, and the Huawei USB drivers
3. A Micro-SD card for your backups (THIS IS VERY IMPORTANT! PLEASE MAKE BACKUPS!)
4. TWRP for this phone. This can be found here: https://forum.xda-developers.com/android/general/huawei-ascend-xt-h1611-t3507933 (credits to enigma2446)
5. The ZIP containing SuperSU. This can be found here: https://forum.xda-developers.com/android/general/huawei-ascend-xt-h1611-t3507933
6. The SDK Platform Tools. These can be found on the android studio website.
PART 1: UNLOCKING THE BOOTLOADER1. Geting the Bootloader Unlock Code: You need to get your bootloader unlock code. You can get this by going to https://emui.huawei.com/en/plugin.php?id=unlock
(EDIT: It appears that this website is down. I have read that if you PM Huawei on Twitter or call them and provide all the details of your phone, they will give you a code. I have not tested this method, bit people have said it worked with the mate 10.) and signing into your Huawei ID. If you dont have one, create one. Then, follow the instructions given to you by Huawei to get the code.
2. Enabling the Enable OEM Unlock Option: To enable this option, you must enable developer options. To do this, go to Settings>About Phone and tap the Build number until it says "You are now a Developer". back out of About Phone, and go to Developer options. turn on "Enable OEM unlock" and press Enable.
3. Enable USB Debugging: While you are still in Developer options, enable the option 'USB debugging" and press OK.
4. Booting Into the Bootloader: once you have completed the first three steps, you can now boot into the bootloader. Connect your phone to your computer, and open the Platform Tools folder you should have downloaded and extracted. Shift-Right click, and press "Open Command Window Here" or "Open Powershell Window Here", depending on your version of windows. Once it is open, make sure your device is detected by typing "adb devices". If it displays your device, you are good to continue. If not, something is not set up right on your computer or phone. Once you verified that your phone is detected, type "adb reboot bootloader".
5. Unlocking the Bootloader: Once your phone has booted into the bootloader, you can now unlock the bootloader. YOUR PHONE WILL BE WIPED ONCE YOU TYPED THIS COMMAND. You can unlock it by typing "fastboot oem unlock <your bootloader unlock code>". Once it has finished, you can reboot your phone, and just run through the setup fast, because you will still have to wipe it again.
PART 2: ROOTING YOUR PHONE1. Move the TWRP image you downloaded (called
Xtrecovery) to your Platform Tools folder and rename it to "TWRP.img"
2. Insert Your Micro-SD Card
3. Move the SuperSU Zip you downloaded to the SD card
4. Re-Enable USB Debugging: Enable Developer options by going to Settings>About Phone and taping the Build number until it says "You are now a Developer". Back out of About Phone, and go to Developer options, and enable USB debugging, and press OK.
5. Boot Into the Bootloader: Type "adb reboot bootloader" into your open CMD window or Powershell window.
6. Verify That your Phone says that the Bootloader is unlocked
7. Type "fastboot boot TWRP.img"
8. TWRP should boot. Tap "Keep Read Only"
9. You should now be in TWRP. Go to Backup>Select Storage and choose your Micro-SD card and tap OK. Uncheck everything and check "Recovery". Then, Swipe the slider to back up your stock recovery partition.
10. Once it has finished backing up, reboot your phone to the bootloader.
11. Once it is in the bootloader, type "fastboot flash recovery TWRP.img" to flash TWRP as your recovery. (I believe this is the point where your warrenty will be invalidated by Huawei, so be careful.)
12. When it finishes flashing TWRP, reboot your phone to TWRP by holding down the power button and volume up
13. It should boot to TWRP. Tap "Keep Read Only", then go to (YOU ARE ABOUT TO WIPE IT AGAIN)Wipe>Format Data and type yes, and hit the enter button.
14. Once it finishes, go to Backup>Select Storage, select your SD card and hit OK, then check every box to backup all six partitions, and swipe to back them up. (At the end, it may seem to get stuck at 98-99%, DO NOT STOP IT! It is generating an MD5 checksum)
15. When it finishes backing everything up, go back to the home screen of TWRP, then go to Install, navigate to where you stored the SuperSU ZIP, select it, then swipe to flash it.
16. When it finishes flashing the SuperSU ZIP, tap "Clear Cache/Dalvik" and swipe to clear them.
17. Reboot your phone. IT WILL REBOOT MULTIBLE TIMES AND APPEAR TO BE STUCK SOMETIMES, BUT DONT TOUCH IT! This is normal and it will eventually boot like normal.
That's it!
Your phone should now be rooted and have SuperSU installed. Please note that this is a Systemless root, and will be removed if you factory reset your phone.Thanks to divineBliss for creating the original instructions.
What do we do after we get root to install custom ROMS? please advise
nedfred0 said:
What do we do after we get root to install custom ROMS? please advise
Click to expand...
Click to collapse
To install a custom ROM, you need the ROM you want to install, gapps depending on the ROM, and the proper firmware. The firmware you are on can be found under about phone and is the last 4 digets of the build number (in the format of B1xx). Once you are on the proper firmware, have your ROM and other things it may require, (every ROM is different), and a backup (just in case), you can flash the ROM from TWRP. Follow the instructions provided by the creator of the ROM to properly flash it.
Where do you get the USB driver at because I am not seeing it at http://consumer.huawei.com/us/support/phones/ascend-xt/
BTJustice said:
Where do you get the USB driver at because I am not seeing it at
Click to expand...
Click to collapse
The drivers come with HiSuite. Download it and you should be good to go.
randomness725 said:
The drivers come with HiSuite. Download it and you should be good to go.
Click to expand...
Click to collapse
Thanks. I tried that but couldn't get it to go so I downloaded these instead which did the job:
https://www.androidfilehost.com/?fid=817550096634745788
does this work on the new h1711 huawei assend xt2
xaneth201 said:
does this work on the new h1711 huawei assend xt2
Click to expand...
Click to collapse
It will not. The TWRP recovery image is device specific and might brick your device if you flash it to your phone.
bricked 1711
randomness725 said:
It will not. The TWRP recovery image is device specific and might brick your device if you flash it to your phone.
Click to expand...
Click to collapse
Well I did not see that, so yeah, I have bricked it. IT comes up and says it is unlocked, it used to sit there then boot into the system.
So I downloaded the TWRP, tried to reboot to recovery and nothing.
Now, it just gets to the yellow warning screen, then goes black. Just bought this today on a black friday sale for 49.00
But did it for a reason. Now I would like to be able to recover it....
I was able to run adb and fastboot, so know that the drivers work, but it looks like it won't even get there now.
And it won't even go to the recovery, so I guess this phone is a real brick.
Can't seem to get the back cover off to remove the battery either.
You need a copy of the stock H1711 recovery image to use
"fastboot flash recovery H1711-stock-recovery.img" to restore the stock recovery. Until someone creates a working H1711 TWRP, I don't know where you'll find a stock H1711 recovery image file.
scrungydoolittle said:
Well I did not see that, so yeah, I have bricked it. IT comes up and says it is unlocked, it used to sit there then boot into the system.
So I downloaded the TWRP, tried to reboot to recovery and nothing.
Now, it just gets to the yellow warning screen, then goes black. Just bought this today on a black friday sale for 49.00
But did it for a reason. Now I would like to be able to recover it....
I was able to run adb and fastboot, so know that the drivers work, but it looks like it won't even get there now.
And it won't even go to the recovery, so I guess this phone is a real brick.
Can't seem to get the back cover off to remove the battery either.
Click to expand...
Click to collapse
download hisuite, enable oem unlocking and usb debbuginig, you gotta also get tha password or the unlocking, denn u run cmd and type:
adb devices
i hope i helped
there is easy way to get unlock bootloader pass for all huawei
just by IMEI search on google "hardreset24 unlock bootloader" there is full info how to do it
BTJustice said:
Where do you get the USB driver at because I am not seeing it at http://consumer.huawei.com/us/support/phones/ascend-xt/
Click to expand...
Click to collapse
Here is the site for USB drivers for all Huawei models:
http://huaweiadvices.com/download-huawei-usb-drivers/
Good luck....
Does the phone even have a fastboot mode?
RomLord14495 said:
Does the phone even have a fastboot mode?
Click to expand...
Click to collapse
Sure it does
Notes on booting up the phone (from power off)
Bootloader (fastboot) = power + volume down + USB hooked to pc
eRecovery = power + volume up + USB hooked to PC
TWRP = power + volume up
Click to expand...
Click to collapse
Optionally you put phone into bootloader/fastboot or recovery modes by typing from an adb prompt "reboot bootloader" or "reboot recovery"
Hi there. The website link for submitting your imei to get the unlock code doesn't work. Does anyone know how to get this code now?
dominoes20 said:
Hi there. The website link for submitting your imei to get the unlock code doesn't work. Does anyone know how to get this code now?
Click to expand...
Click to collapse
You'll have to use DC Unlocker and pay to unlock until the page returns
Since unlocking the bootloader is no longer supported, I have a suggestion but am afraid to try myself.
So, download stock version of rom (aka fastboot rom). Extract, replace recovery.img with twrp (renamed to recovery.img). Restart phone in EDL mode, flash. In theory, edl is working fastboot mode so it shouldn't matter if bootloader is unlocked, correct?
ezopantyd said:
there is easy way to get unlock bootloader pass for all huawei
just by IMEI search on google "hardreset24 unlock bootloader" there is full info how to do it
Click to expand...
Click to collapse
Imma try this out, I’m stuck in a weird situation where my sd card slot broke. When I sent it in for service, they said it was rooted and refused to fix it. I specifically did not root it so that I could send it in for warranty service. So it’s mission to try and root, unlock boot loader etc so that I can have more storage space
---------- Post added at 11:50 AM ---------- Previous post was at 11:36 AM ----------
ezopantyd said:
there is easy way to get unlock bootloader pass for all huawei
just by IMEI search on google "hardreset24 unlock bootloader" there is full info how to do it
Click to expand...
Click to collapse
Can you be a little more specific? I didn’t get that info on google
Download Link: https://android.googleapis.com/pack.../f0095b7e9162d37af8f00140aea38d7922887a0a.zip
Enable Developer settings by going into Settings > Info > Tap "Build Number" a few times until a toast message says that you're now a developer
Activate "ADB Debugging"
Install THIS ADB Quick Installer with drivers if you don't have ADB installed yet
Open a CMD and type "adb start-server", connect your watch via USB and accept the connection on the watch
Then type "adb reboot recovery"
Your watch should display that it's in recovery mode now, swipe down to get more menu options
Select "Apply update from ADB" and swipe right
In the CMD cd to your Download folder
Type "adb sideload f0095b7e9162d37af8f00140aea38d7922887a0a.zip" and wait, it may appear stuck at some point but just wait!
After that's done select "Reboot" and swipe right
...
PROFIT!
It may or may not boot into Android Wear 2 at the first reboot. Leave it sitting for up to 15 Minutes and if it's still stuck on the boot animation force-turn-off the watch by holding the button. To prevent this you could also try to clear cache in the recovery before updating but I'm not 100% if that'd fix this, just a theory because a normal System Update would indeed wipe cache first.
Thanks, your guide worked perfectly, there are no replies so it seems doubtful but it's very clear and perfect.
Updated my watch to Android wear 2.0, as it got flashed from stock recovery means it should be stock OS from Asus
You are the man!!! For some reason it kept getting stuck after adding my Google account, so I did a full data and cache wipe afterwards, and now it's working smooth. I haven't had a chance to really play with it yet to get a good feel for it, though.
EpicLPer said:
Download Link: https://android.googleapis.com/pack.../f0095b7e9162d37af8f00140aea38d7922887a0a.zip
Enable Developer settings by going into Settings > Info > Tap "Build Number" a few times until a toast message says that you're now a developer
Install THIS ADB Quick Installer with drivers if you don't have ADB installed yet
Open a CMD and type "adb start-server", connect your watch via USB and accept the connection on the watch
Then type "adb reboot recovery"
Your watch should display that it's in recovery mode now, swipe down to get more menu options
Select "Apply update from ADB" and swipe right
In the CMD cd to your Download folder
Type "adb sideload f0095b7e9162d37af8f00140aea38d7922887a0a.zip" and wait, it may appear stuck at some point but just wait!
After that's done select "Reboot" and swipe right
...
PROFIT!
It may or may not boot into Android Wear 2 at the first reboot. Leave it sitting for up to 15 Minutes and if it's still stuck on the boot animation force-turn-off the watch by holding the button. To prevent this you could also try to clear cache in the recovery before updating but I'm not 100% if that'd fix this, just a theory because a normal System Update would indeed wipe cache first.
Click to expand...
Click to collapse
Can you please share a full rom zip, not only update zip?
---------- Post added at 20:16 ---------- Previous post was at 19:25 ----------
Anyone knows how to root the rom?
matze19999 said:
Can you please share a full rom zip, not only update zip?
---------- Post added at 20:16 ---------- Previous post was at 19:25 ----------
Anyone knows how to root the rom?
Click to expand...
Click to collapse
A full ROM will require someone to dump it from their watch.
Lrs121 said:
A full ROM will require someone to dump it from their watch.
Click to expand...
Click to collapse
Yeah, I know ^^
awesome finally. just flashed the 6.0.1 again its syncing now. had the watch lying around 3 weeks since i got tired of charging 2 times a day with webwear.
can go straight to recovery and sideload the update or should i wait out the 6.0.1 syncing with my phone ?
I just wanted to add that for #8 I have a Windows 10 PC and Minimal ADB installed and you can just drag the file to the CMD window instead of typing all of that.
My watch has definitely recognized that I'm a developer, but I don't the message to "accept the connection on the watch" anywhere.
I am typing the adb reboot recovery command in the outer shell of CMD, but get the message "error : device '(null)' not found.
Windows 10 machine. A little help, please?
EDIT: Got it!
I forced the Zenwatch into Recovery Mode manually and accepted to install update manually.
Hi
I'm trying to updae but cmd says:
error: protocol fault (no status)
and in watch:
You need adb 1.0.32 or newer to sideload to this device.
installation aborted
???
After enabling the developer-settings, you need to enter those settings and activate ADB-Debugging. After that your watch will be recognized and you get the "Accept connection" message on the watch.
Hello,
I flashed my Zen2 this morning and do not notice any lag like others are stating...actually runs pretty good. One thing I do notice however is that my phone shows an active connected bluetooth device (like when connected to a car stereo or speaker). This is different than my Moto2 watch when connected to the same phone. Also on the older Wear 1.5 software did not show as actively connected as a bluetooth device. Does this mean the Zen2 will be using more juice or that we can use it as a portable speaker to play music? Just seems odd as I have always had multiple watches connected to the same phone. I just grab whichever suits my needs for that day. Why would this change by updating from Wear 1.5 to Wear 2.0? I suspect we will notice more drain on both the phone and the watch...time will tell. As far as those concerned with updating just do it as Wear 2.0 works fine once you get used to the change.
Cheers
Thanks this procedure worked for me. I di have to power off and power back on when first boot hung on animation
Update is perfect
wait was good
Procedure worked great, easy and fast. I am receiving email notifications on the watch but no text messages. Any ideas?
i waited out the 6.0.1 syncing to my phone before sideloading aw2.0
what i did:
reboot to recovery
sideload update
factory reset watch
clear watch cache (i know its alrdy done by factory reset but still)
reboot
still got stuck at booting the 1st time. boot animation forever.
hard rebooted the watch and aw2.0 came up fine.
Full rom zip. Wipe system, data, cache, dalvik and flash the files in the zip with these commands:
fastboot format system
fastboot format userdata
fastboot flash system system.img
fastboot flash boot boot.img
optional:
fastboot flash cache cache.img
No update zip!
https://www.androidfilehost.com/?fid=961840155545583518
matze19999 said:
Full rom zip. Wipe system, data, cache, dalvik and flash the files in the zip with these commands:
fastboot flash system system.img
fastboot flash boot boot.img
optional:
fastboot flash cache cache.img
No update zip!
https://www.androidfilehost.com/?fid=961840155545583518
Click to expand...
Click to collapse
THX!
TheDantee said:
THX!
Click to expand...
Click to collapse
You're welcome bro
So I followed the steps, zero issues. Everything went like you said it would. When it rebooted I was still on 1.5....i rebooted again and same thing. Did a full factory reset and still won't take the update even though it seems to have been loaded. Tried clearing cache as well. Any ideas?
Sent from my S8
Well, ok..I have a huge problem.
I was in developer mode and it said i could switch my rom so i installed it and now my phone says "Your device is corrupt. It is not trusted and will not boot".
Any suggestions on how I can fix this?
Wow that can't be good. I'm new to the oneplus stuff, normally I would say boot into recovery and reflash to stock but since we do not have roms yet I have a feeling your going to have to take it back to tmobile or oneplus and exchange it.
He should still be able to recover it with a factory restore via the stock recovery. As far as I know (and I'm not an expert) a bad ROM flash doesn't touch the recovery partition.
from https://www.devicesfaq.com/en/reset/oneplus-nord-n200-5g
Restore with hard reset or Recovery mode OnePlus Nord N200 5GRestore with hard reset or Recovery mode your OnePlus Nord N200 5G can solve problems that have not been solved with a normal factory reset.
1- First turn off your OnePlus Nord N200 5G completely. If you can not unlock the screen, press and hold the power button for about 20 seconds and the phone will turn off.
2- Keep holding on volume down and power keys together for a few seconds in your OnePlus Nord N200 5G. In some devices according to the Android version the combination can be the power key and the volume key up.
3- When the OnePlus logo is displayed, release the buttons.
4- Move through the menu with the volume up and volume down keys until you reach the “Recovery Mode” option and press the power button to access.
If the device menu appears in Chinese characters, click here to see how to reset a mobile in Chinese
5- Use the volume up and volume down keys to select the “wipe cache partition” option and press the Power button to activate the option and clear the mobile cache.
6- After a few seconds you will return to the previous screen, with the volume buttons go to the option “wipe data / factory reset” and press the power button to enter. A screen with many NOes and a YES will appear, with the volume keys again go to the YES and press with the power key.
7- After finishing again with the volume keys, click on “reboot system now” and press the power key of your OnePlus Nord N200 5G, the device will reboot and take several minutes to start while restoring the device to its factory state and optimizing the applications pre-installed in the system Android 11, OxygenOS 11.
Click to expand...
Click to collapse
edale1 said:
He should still be able to recover it with a factory restore via the stock recovery. As far as I know (and I'm not an expert) a bad ROM flash doesn't touch the recovery partition.
from https://www.devicesfaq.com/en/reset/oneplus-nord-n200-5g
Click to expand...
Click to collapse
I can't even get into recovery. I can get into download mode but theres no way for me to restore it from that...
literally recovery mode is gone also. it's so weird, i did this from my phone's settings, it shouldn't have done this.
fogles2021 said:
I can't even get into recovery. I can get into download mode but theres no way for me to restore it from that...
literally recovery mode is gone also. it's so weird, i did this from my phone's settings, it shouldn't have done this.
Click to expand...
Click to collapse
phone off -> volume down + power (hold both in until phone's booted)
that doesn't work to get into recovery mode?
How about
volume up + volume down + power
to get into fastboot mode?
Can you connect via USB to run ADB commands?
edale1 said:
phone off -> volume down + power (hold both in until phone's booted)
that doesn't work to get into recovery mode?
How about
volume up + volume down + power
to get into fastboot mode?
Can you connect via USB to run ADB commands?
Click to expand...
Click to collapse
I can only boot into fastboot, recovery just boots back to "your device is corrupt'.
I can connect usb but i can't find drivers for the phone, its connect as QUSB.
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
There's the USB drivers.
Selecting recovery from within fastboot mode brings up the corrupt message as well? Very odd.
I'm seeing 2 options then. Take the phone back to the store you got it at to see if they can fix/replace it; or wait for the ROM to be released.
edale1 said:
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
There's the USB drivers.
Selecting recovery from within fastboot mode brings up the corrupt message as well? Very odd.
I'm seeing 2 options then. Take the phone back to the store you got it at to see if they can fix/replace it; or wait for the ROM to be released.
Click to expand...
Click to collapse
I've installed these and it still comes up as qusb bulk.
Yeah, selecting recovery from fastboot goes to corrupt message, too.
Just going to make a aservice request.
There was another report of this on the OnePlus forums a while ago, too, if I'm inferring what happened correctly: https://forums.oneplus.com/threads/...-the-oneplus-nord-n200.1460001/#post-23393026
The only real recourse right now is to submit a ticket as you've done and wait until you can send your device back and they send you a new one.
Once OnePlus releases a full stock ROM image, if they ever do, it will be possible to recover a bootloader-unlocked device from this state. But even then that won't work if you weren't bootloader unlocked beforezs the update.
---
While you've still got the device, though, could you try something for me? Could you install the android platform tools, see if you can get fastboot working on your computer, and try the fastboot command "fastboot set-active a"?
The Nord N200 5G is a A/B partitioned device, which means it has two of each system partition, one labeled "a" and one labeled "b". The update process is *supposed to* install all updates into the partition that you aren't currently using, then instruct the system to switch to it so it can update seamlessly.
I have no idea what went wrong in your update process, but if it did an incomplete update then instructed the system to use the other partition (and now for some reason doesn't switch back) this could help. I kind of doubt it will, since in my attempts at flashing bootloaders, if I put anything fully invalid in boot partition 'b', the phone automatically switches back to 'a' and boots into "safe mode".
But if for some reason it isn't corrupted enough to trigger that, maybe switching back to the "a" partition set could fix it. Or if you're already on "a", you could try switching to "b".
daboross said:
There was another report of this on the OnePlus forums a while ago, too, if I'm inferring what happened correctly: https://forums.oneplus.com/threads/...-the-oneplus-nord-n200.1460001/#post-23393026
The only real recourse right now is to submit a ticket as you've done and wait until you can send your device back and they send you a new one.
Once OnePlus releases a full stock ROM image, if they ever do, it will be possible to recover a bootloader-unlocked device from this state. But even then that won't work if you weren't bootloader unlocked beforezs the update.
---
While you've still got the device, though, could you try something for me? Could you install the android platform tools, see if you can get fastboot working on your computer, and try the fastboot command "fastboot set-active a"?
The Nord N200 5G is a A/B partitioned device, which means it has two of each system partition, one labeled "a" and one labeled "b". The update process is *supposed to* install all updates into the partition that you aren't currently using, then instruct the system to switch to it so it can update seamlessly.
I have no idea what went wrong in your update process, but if it did an incomplete update then instructed the system to use the other partition (and now for some reason doesn't switch back) this could help. I kind of doubt it will, since in my attempts at flashing bootloaders, if I put anything fully invalid in boot partition 'b', the phone automatically switches back to 'a' and boots into "safe mode".
But if for some reason it isn't corrupted enough to trigger that, maybe switching back to the "a" partition set could fix it. Or if you're already on "a", you could try switching to "b".
Click to expand...
Click to collapse
Can u give me a link to platform tools, also..my computer is detecting the phone as QUSB BULK:"
From one of my other threads:
------
USB DRIVERS
You may need to use the Google USB Driver from Android Studio to allow your PC to recognize your phone when it's in fastboot mode.
Download Android Studio & App Tools - Android Developers
Android Studio provides app builders with an integrated development environment (IDE) optimized for Android apps. Download Android Studio today.
developer.android.com
Android Studio won't install the USB Drivers by default, you'll need to install them through the SDK Manager (Android Studio -> Projects -> More Actions -> SDK Manager -> SDK Tools -> Google USB Driver checkbox -> Apply)
You'll need to manually install the drivers through the device manager while the phone is in fastboot mode and connected to the PC (right-click -> Update Drivers -> Browse Computer -> Let Me Pick -> Have Disk).
The drivers should be located at:
C:\Users\[username]\AppData\Local\Android\Sdk\extras\google\usb_driver\android_winusb.inf
You'll want the 'Android Bootloader Interface' driver.
Click to expand...
Click to collapse
------
Basically, you need to manually update the drivers through device manager.
edale1 said:
From one of my other threads:
------
------
Basically, you need to manually update the drivers through device manager.
Click to expand...
Click to collapse
I can't get it to work...
fogles2021 said:
I can't get it to work...
Click to expand...
Click to collapse
From the first update drivers dialog (your phone should be in fastboot mode):
"browse my computer for drivers"
"let me pick from a list of available drivers on my computer"
"have disk"
And the drivers should be at
Code:
C:\Users\[username]\AppData\Local\Android\Sdk\extras\google\usb_driver\android_winusb.inf
Once you select the .inf, you'll want to select this from the resultant list:
"Android Bootloader Interface"
fogles2021 said:
I can't get it to work...
Click to expand...
Click to collapse
Your phone is in EDL mode, also known as hard brick. It seems like the phone thinks both of your system partitions are empty or corrupt, as well as the bootloader is perhaps corrupt, due to which it is now gone to EDL mode as a last resort.
Typically, the only way to come out of it is to flash in EDL mode using MSMDownload Tool. Unfortunately for you, I don't see that Oneplus has released the MSMDownload Tool for the N200.
There are 4 things you can do at this stage.
1. If the phone is in return period, get it exchanged for another one.
2. Assuming the phone is under warranty, get it repaired under warranty
3. Wait for Oneplus to release the MSMDownload Tool for the N200. From past experience, Oneplus has eventually released it for every one of their phones. Once it is released, it is literally a 5 minute fix to get your phone to factory refreshed stage.
4. As a long shot, we can try to see if the bootloader is not corrupt, and if that is working, try to check if either of the 2 system partition is still intact, as @edale1 is suggesting above. Try the following
a. Press Volume Down+Power when phone is power off stage, and see if you can get the phone in fastboot mode.
b. Go to the folder when you have downloaded the Android SDK Toolkit. Alternately, search for the folder containing "fastboot.exe" on your hard drive. Open a command prompt in that folder containing fastboot.exe.
c. Run "fastboot devices" in the command prompt.
d. If you get a response of "no devices", then that means either phone is not in fastboot mode ( Go to Step a and repeat a,b,c until it is in fastboot mode) or bootloader is corrupt (nothing can be done other than Steps 1, 2 or 3 I have outlined above)
e. If you get a response of "XYZ fastboot" where XYZ is a random string/number, then bootloader is not corrupt. Proceed to Step f.
f. Type "fastboot getvar all" in the command prompt.
Wait for a lot of text to finish scrolling and look for the (bootloader) current-slot text
This should actually be toward the bottom without the need to scroll up.
The letter after this text will be the currently active partition slot for your device, either 'a' or 'b'
g. Follow @edale1's instruction above to change active partition to the *opposite* of whatever currently active partition e.g. if it says 'a' as the active partition in Step f above, then type in "fastboot --set-active=b" in command prompt, and vice-versa i.e. if it says 'b' as the active partition in Step f above, then type in "fastboot --set-active=a" in command prompt
h. If you get success in Step g, type "fastboot reboot" in command prompt, and keep your fingers crossed that it boots up normally. If not, that means both system partitions are corrupt. Follow Steps 1, 2 or 3 above.
Good luck!
fogles2021 said:
Well, ok..I have a huge problem.
I was in developer mode and it said i could switch my rom so i installed it and now my phone says "Your device is corrupt. It is not trusted and will not boot".
Any suggestions on how I can fix this?
Click to expand...
Click to collapse
No stock rom on oneplus/tmobile website
Im having a device corrupt error and cannot access phone anymore. Im trying to find the stock rom to flash with MSM tool but cantyfind it anywhere. You'd think oneplus would have it up on their website already. Anyone?
forum.xda-developers.com
Had the same problem, had to do a warranty replacement
I followed your mini guide but it says "Slotchange is not allowed in lock state"
Anyways to unlock it using fastboot ?
Ethanvio said:
I followed your mini guide but it says "Slotchange is not allowed in lock state"
Anyways to unlock it using fastboot ?
Click to expand...
Click to collapse
If you didn't enable OEM unlocking in developer options before you bricked your phone, you can't unlock those fastboot commands.