The lolipop ruu avialable at the HTC site.
I am downloading it now.
It's not allowing me to post the direct link
http :// dl3. htc .com /application/RUU_M8_UL_L50_SENSE60_ATT_MR_Cingular_US_4.28.502. [email protected]_40.45.C33065.00_F_relea se_426617_signed_2.exe.
HTC One (M8) Maintenance Release Instructions 4.7.2015
This software upgrade available for your HTC One provides the following key enhancements:
· Upgrade to Android 5.0.2 Lollipop
· Improved OS software design
· Better visibility for Recents and Calendar
· Enhanced notifications
· New recent apps
· Improved settings
· Screen Pinning
· Share your device
· New battery settings panel
· Other planned fixes, updates, and enhancements
Instructions again from the HTC site :
Performing the ROM Update:
1. Download and save the HTC One™ update to your PC.
2. Connect your device to your PC via the supplied USB cable.
3. If the device is not recognized by the PC, ensure you have HTC Sync Manager installed and then disconnect and reconnect the device from the USB cable.
4. Once the device is properly recognized on the PC, locate the HTC One™ ROM Update that you downloaded. Double-click on the file to launch the system update wizard.
5. Follow all of the system update wizard instructions shown on your PC.
6. Once the update is complete, click Finish in the Wizard and the device will reboot.
7. Once the device reboots, the initial setup wizard will appear.
8. Once the initial setup process is complete, the device is ready for use.
Note : If the ROM update wizard fails to recognize the device, close the wizard and then follow the steps below:
· From a powered off state, hold VOLUME DOWN while powering on the device.
· Use the volume buttons to scroll to FASTBOOT and then press the POWER button to select it.
· Connect the device to the PC while in this state and attempt the ROM update again.
To exit FASTBOOT manually, use the volume keys to navigate to REBOOT and press the POWER button to select it.
sameerbk said:
The lolipop ruu avialable at the HTC site.
I am downloading it now.
It's not allowing me to post the direct link
http :// dl3. htc .com /application/RUU_M8_UL_L50_SENSE60_ATT_MR_Cingular_US_4.28.502. [email protected]_40.45.C33065.00_F_relea se_426617_signed_2.exe.
HTC One (M8) Maintenance Release Instructions 4.7.2015
This software upgrade available for your HTC One provides the following key enhancements:
· Upgrade to Android 5.0.2 Lollipop
· Improved OS software design
· Better visibility for Recents and Calendar
· Enhanced notifications
· New recent apps
· Improved settings
· Screen Pinning
· Share your device
· New battery settings panel
· Other planned fixes, updates, and enhancements
Instructions again from the HTC site :
Performing the ROM Update:
1. Download and save the HTC One™ update to your PC.
2. Connect your device to your PC via the supplied USB cable.
3. If the device is not recognized by the PC, ensure you have HTC Sync Manager installed and then disconnect and reconnect the device from the USB cable.
4. Once the device is properly recognized on the PC, locate the HTC One™ ROM Update that you downloaded. Double-click on the file to launch the system update wizard.
5. Follow all of the system update wizard instructions shown on your PC.
6. Once the update is complete, click Finish in the Wizard and the device will reboot.
7. Once the device reboots, the initial setup wizard will appear.
8. Once the initial setup process is complete, the device is ready for use.
Note : If the ROM update wizard fails to recognize the device, close the wizard and then follow the steps below:
· From a powered off state, hold VOLUME DOWN while powering on the device.
· Use the volume buttons to scroll to FASTBOOT and then press the POWER button to select it.
· Connect the device to the PC while in this state and attempt the ROM update again.
To exit FASTBOOT manually, use the volume keys to navigate to REBOOT and press the POWER button to select it.
Click to expand...
Click to collapse
This is the link http://www.htc.com/us/support/htc-one-m8-att/news/
Anyone want one pre-rooted?
Unable to Update
sameerbk said:
The lolipop ruu avialable at the HTC site.
I am downloading it now.
It's not allowing me to post the direct link
http :// dl3. htc .com /application/RUU_M8_UL_L50_SENSE60_ATT_MR_Cingular_US_4.28.502. [email protected]_40.45.C33065.00_F_relea se_426617_signed_2.exe.
HTC One (M8) Maintenance Release Instructions 4.7.2015
This software upgrade available for your HTC One provides the following key enhancements:
· Upgrade to Android 5.0.2 Lollipop
· Improved OS software design
· Better visibility for Recents and Calendar
· Enhanced notifications
· New recent apps
· Improved settings
· Screen Pinning
· Share your device
· New battery settings panel
· Other planned fixes, updates, and enhancements
Instructions again from the HTC site :
Performing the ROM Update:
1. Download and save the HTC One™ update to your PC.
2. Connect your device to your PC via the supplied USB cable.
3. If the device is not recognized by the PC, ensure you have HTC Sync Manager installed and then disconnect and reconnect the device from the USB cable.
4. Once the device is properly recognized on the PC, locate the HTC One™ ROM Update that you downloaded. Double-click on the file to launch the system update wizard.
5. Follow all of the system update wizard instructions shown on your PC.
6. Once the update is complete, click Finish in the Wizard and the device will reboot.
7. Once the device reboots, the initial setup wizard will appear.
8. Once the initial setup process is complete, the device is ready for use.
Note : If the ROM update wizard fails to recognize the device, close the wizard and then follow the steps below:
· From a powered off state, hold VOLUME DOWN while powering on the device.
· Use the volume buttons to scroll to FASTBOOT and then press the POWER button to select it.
· Connect the device to the PC while in this state and attempt the ROM update again.
To exit FASTBOOT manually, use the volume keys to navigate to REBOOT and press the POWER button to select it.
Click to expand...
Click to collapse
Hi
I downloaded tried to update but when i click on .exe file window pops up and asking for accept and closing.. Can you suggest how to do update
Thank You
Mallikarjuna
Same problem
I just used the RUU mentioned in the link above to upgrade and I had no issues. I am stock, no root, no custom recovery and no unlocked bootloader.
Great, just great that AT&T managed to carry over the IQ Agent Service issue with this update. Grrrrrr!
Good to know the RUU works. I'm S-OFF, custom recovery etc... But running a stock ROM. I guess I'll just start picking them off one at a time. Just doesn't make sense. I just ran another RUU on this a couple of weeks ago (same configuration) with no issues
dottat said:
Anyone want one pre-rooted?
Click to expand...
Click to collapse
can you supply a pre-rooted version?
thanks
ekoandrew said:
can you supply a pre-rooted version?
thanks
Click to expand...
Click to collapse
I did here
http://forum.xda-developers.com/showthread.php?t=3015680
EXE/ZIP RUU's M8_ATT Lolli/Kitkat (s-off only)(newest)
unlocked, s-on
Will this process work with unlocked bootloader, S-on, TWRP recovery, and current android version 4.4.2? I'm new to all of this so I'm nearly clueless.
Thanks in advance.
dwatkins144 said:
Will this process work with unlocked bootloader, S-on, TWRP recovery, and current android version 4.4.2? I'm new to all of this so I'm nearly clueless.
Click to expand...
Click to collapse
With s-on, you will need to relock the bootloader using fastboot command: fastboot oem lock
Other than that, it will run fine on any AT&T branded device. Current Android version doesn't matter, it will bring you up to 5.0 (unlike an OTA, which normally expects/required the immediate previous Android version).
But keep in mind, that unlike OTA, the RUU will wipe the phone. So backup anything you want to keep by your method of choice, before you RUU.
If anyone is still facing issues updating, try enabling the USB Debugging mode and then connect.
Also check that all the drivers are properly installed.
I was able to update after getting the above 2 things done.
Hope it helps
i am using att device but not on att network, will it disable the unlocked sim?
JusTeN_ said:
i am using att device but not on att network, will it disable the unlocked sim?
Click to expand...
Click to collapse
No, your SIM will still be unlocked.
redpoint73 said:
No, your SIM will still be unlocked.
Click to expand...
Click to collapse
And in Hboot its says S-ON and Locked, Like here https://www.google.co.il/search?hl=....img..0.0.0.Z_C2y76VVWE#imgrc=Lf9K7EqUeLhUPM:
I need to relock anyway?
JusTeN_ said:
And in Hboot its says S-ON and Locked, Like here https://www.google.co.il/search?hl=....img..0.0.0.Z_C2y76VVWE#imgrc=Lf9K7EqUeLhUPM:
I need to relock anyway?
Click to expand...
Click to collapse
No, RUU will run fine with bootloader either LOCKED or RELOCKED.
UNLOCKED will make the RUU fail.
I am not on AT&T network and in Kuwait trying to update my device with the download following RUU: RUU_M8[email protected]50319A_40.45.C33065.00_F_release_426617_signed_2.exe
Every time I try to update it; it restarts in bootloader and stuck on sending 0/6.............
Please advise what to do...
*** Software status: Official ***
*** LOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.19.0.0000RADIO-1.16.21331931.LA11G
OpenDSP-v38.2.2-00542-M8947.0311
OS-1.58.502.1 (4.28.502.1)
eMMC-boot 2048MB
fawad81 said:
I am not on AT&T network and in Kuwait trying to update my device with the download following RUU: RUU_M8[email protected]50319A_40.45.C33065.00_F_release_426617_signed_2.exe
Every time I try to update it; it restarts in bootloader and stuck on sending 0/6.............
Please advise what to do...
*** Software status: Official ***
*** LOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.19.0.0000RADIO-1.16.21331931.LA11G
OpenDSP-v38.2.2-00542-M8947.0311
OS-1.58.502.1 (4.28.502.1)
eMMC-boot 2048MB
Click to expand...
Click to collapse
Try a factory reset and then try running the ruu again.
Sent from my HTC6535LVW using Tapatalk
I got this htc m8 unlocked bootloader s-off should I just relock bootloader and then ruu?
Related
Hi Everyone / Anyone,
Got this HTC ONE X+ (64GB) (Not AT&T as only has "HTC" logo on phone) phone from another user who i think spoil the
phone with Cyanogenmod as it keeps reboot and stuck in CYM screen with spining arrows.
Read some posts here and managed to reboot into recovery screen and get some data. It cannot charge properly,
so flash with latest TWRP v2.6.3.0 and now can fully charge to LED turns green.
Some of info of this phone are:
*** UNLOCKED ***
ENRC2B_U PVT SHIP S-ON RL
HBOOT : 1.72.0000
CPLD : None
MICROP : None
RADIO : 3.1204.171.33
eMMC-bootmode : disabled
CPU-bootmode : disabled
HW Secure boot : enabled
MODEM PATH : OFF
Jun 21 2013, 17:36:36
Run fastboot getvar all and some info are:
Version-main : 2.18.707.5
Platform : HBOOT-T30S
Modelid : PM3511000
Cidnum : HTC__044
Battery-status : good
dev-power : 91
partition-layout : None
commitno-bootloader : None
My problem now its seem the HBOOT is very new and not able to find suitable version of 2.18.707.5 image.
Tried run RUU from various sources (WWE, EUROPE,..) cannot flash into the phone. I do not know where
is the reliable ones now and not sure what's next? Have used Hansoon AIO kit and WinDroid, these are helpful
but my phone status does not allow the kit to execute fully.
Now the CYM screen is gone and only show HTC logo screen and cannot proceed to boot further. Of course it
seem the ROM (Custom or stock) are gone as previous user did not make any backup and spoil it.
Summary of what i can do with the phone now:
Reboot phone into recovery mode or Fastboot. Can link PC and phone show FastBoot USB. Can fastboot to phone for lock / unlock.
Observed feedback from TWRP there is no root folder as suggest to install SuperUSR but not sure is it successful.
HELP, Need advice and help to find and load back factory stock ROM or any version suitable for it.
Think it does not have a proper root loaded too.
Installing a custom ROM will be easy
Wipe all excluding the Internal Storage from TWRP
Just "adb push" the ROM file to the SDCARD once the installation is done
boot into fastboot
flash the kernel from the fastboot........
that should get ur phone booted refer to this tutorial for installing a custom ROM
GoRiLaz301 said:
Hi Everyone / Anyone,
Got this HTC ONE X+ (64GB) (Not AT&T as only has "HTC" logo on phone) phone from another user who i think spoil the
phone with Cyanogenmod as it keeps reboot and stuck in CYM screen with spining arrows.
Read some posts here and managed to reboot into recovery screen and get some data. It cannot charge properly,
so flash with latest TWRP v2.6.3.0 and now can fully charge to LED turns green.
Some of info of this phone are:
*** UNLOCKED ***
ENRC2B_U PVT SHIP S-ON RL
HBOOT : 1.72.0000
CPLD : None
MICROP : None
RADIO : 3.1204.171.33
eMMC-bootmode : disabled
CPU-bootmode : disabled
HW Secure boot : enabled
MODEM PATH : OFF
Jun 21 2013, 17:36:36
Run fastboot getvar all and some info are:
Version-main : 2.18.707.5
Platform : HBOOT-T30S
Modelid : PM3511000
Cidnum : HTC__044
Battery-status : good
dev-power : 91
partition-layout : None
commitno-bootloader : None
My problem now its seem the HBOOT is very new and not able to find suitable version of 2.18.707.5 image.
Tried run RUU from various sources (WWE, EUROPE,..) cannot flash into the phone. I do not know where
is the reliable ones now and not sure what's next? Have used Hansoon AIO kit and WinDroid, these are helpful
but my phone status does not allow the kit to execute fully.
Now the CYM screen is gone and only show HTC logo screen and cannot proceed to boot further. Of course it
seem the ROM (Custom or stock) are gone as previous user did not make any backup and spoil it.
Summary of what i can do with the phone now:
Reboot phone into recovery mode or Fastboot. Can link PC and phone show FastBoot USB. Can fastboot to phone for lock / unlock.
Observed feedback from TWRP there is no root folder as suggest to install SuperUSR but not sure is it successful.
HELP, Need advice and help to find and load back factory stock ROM or any version suitable for it.
Think it does not have a proper root loaded too.
Click to expand...
Click to collapse
---------- Post added at 02:55 PM ---------- Previous post was at 02:48 PM ----------
GoRiLaz301 said:
Hi Everyone / Anyone,
Summary of what i can do with the phone now:
Reboot phone into recovery mode or Fastboot. Can link PC and phone show FastBoot USB. Can fastboot to phone for lock / unlock.
Observed feedback from TWRP there is no root folder as suggest to install SuperUSR but not sure is it successful.
HELP, Need advice and help to find and load back factory stock ROM or any version suitable for it.
Think it does not have a proper root loaded too.
Click to expand...
Click to collapse
The Stock Nandroid backup of ur frimware can be found here
To use this u have to put that in the TWRP backups folder which will be a one hectic process to do
Best is to install a custom rom and copy the files to the TWRP folder through MTP......if u want to have Stock ROm
[email protected] said:
Installing a custom ROM will be easy
Wipe all excluding the Internal Storage from TWRP
Just "adb push" the ROM file to the SDCARD once the installation is done
boot into fastboot
flash the kernel from the fastboot........
that should get ur phone booted refer to this tutorial for installing a custom ROM
---------- Post added at 02:55 PM ---------- Previous post was at 02:48 PM ----------
The Stock Nandroid backup of ur frimware can be found here
To use this u have to put that in the TWRP backups folder which will be a one hectic process to do
Best is to install a custom rom and copy the files to the TWRP folder through MTP......if u want to have Stock ROm
Click to expand...
Click to collapse
--------------
in the link regarding "installing a custom ROM" instruction, it seem the phone status permit booting into the phone to "Enable USB Debuggin"
However my case now it will not boot into the normal phone interfaces, it will stuck at "HTC" logo screen and nothing happens afterwards.
I can not only access the Fastboot / Recovery / HBOOT screen of the phone. Any normal reboot will stuck in HTC screen.
also running "adb devices" does not detect the phone and report a serial no. It did run and show opening a port no. 50xx and end successfully.
please advice
i install the Android SDK and followed all instructions carefully but "adb devices" did not return any serial no. of the phone.
in fact the result return blank, nothing is listed.
NOTE the phone can only be connected via USB through recovery mode in Fastboot USB link.
Even when reboot the phone as normal while showing the stucked HTC screen logo, the usb link cannot be established.
please advice.
In CUSTOM Recovery the USB debugging is enabled by default...so that step of booting into phone and enabling the USB debugging doesn't matter...
the device won't get recognized if u had not installed the HTC drivers...
try installing the latest drivers from here
Install this and try
Code:
adb devices
And what are u planning on do install a custom ROM or Flash the Stock Nandroid backup from the thread I provided.....????
I can only help u knowing what u are trying to do.....
GoRiLaz301 said:
--------------
in the link regarding "installing a custom ROM" instruction, it seem the phone status permit booting into the phone to "Enable USB Debuggin"
However my case now it will not boot into the normal phone interfaces, it will stuck at "HTC" logo screen and nothing happens afterwards.
I can not only access the Fastboot / Recovery / HBOOT screen of the phone. Any normal reboot will stuck in HTC screen.
also running "adb devices" does not detect the phone and report a serial no. It did run and show opening a port no. 50xx and end successfully.
please advice
Click to expand...
Click to collapse
GoRiLaz301 said:
i install the Android SDK and followed all instructions carefully but "adb devices" did not return any serial no. of the phone.
in fact the result return blank, nothing is listed.
NOTE the phone can only be connected via USB through recovery mode in Fastboot USB link.
Even when reboot the phone as normal while showing the stucked HTC screen logo, the usb link cannot be established.
please advice.
Click to expand...
Click to collapse
I am trying to get this phone to get to normal functional phone for any region.
Since i got this phone from previous owner, think without any proper ROM backup and got loop in cym logo so am trying to bring this phone "alive" again. It seem not getting anywhere or my procedure is wrong with lack of real ROM in sdcard. At least i managed to figure out somehow get the latest CWM or TWRP and let the phone charge fully. Previously it always show "low battery to flash" message when powered using [ POWER + VOL ] combination.
Not trying to do anything funny to this phone, rather to try my best revive it back to a fully functional phone as the original HTC ONE X+ 64GB International edition. Think this phone is a ASIA WWE edition as it bought locally and with the HTC printed silkscreen, not AT&T.
Sincerely hope u or anyone can help me. I will try to use the "adb device" command again, seem with this way to communicate and push ROM inside the phone, nothing else can get it pass the HTC logo screen now... I am puzzled using Fastboot seem communicating ok with the phone but not adb command.... Keep update....
GoRiLaz301 said:
I am trying to get this phone to get to normal functional phone for any region.
Since i got this phone from previous owner, think without any proper ROM backup and got loop in cym logo so am trying to bring this phone "alive" again. It seem not getting anywhere or my procedure is wrong with lack of real ROM in sdcard. At least i managed to figure out somehow get the latest CWM or TWRP and let the phone charge fully. Previously it always show "low battery to flash" message when powered using [ POWER + VOL ] combination.
Not trying to do anything funny to this phone, rather to try my best revive it back to a fully functional phone as the original HTC ONE X+ 64GB International edition. Think this phone is a ASIA WWE edition as it bought locally and with the HTC printed silkscreen, not AT&T.
Sincerely hope u or anyone can help me. I will try to use the "adb device" command again, seem with this way to communicate and push ROM inside the phone, nothing else can get it pass the HTC logo screen now... I am puzzled using Fastboot seem communicating ok with the phone but not adb command.... Keep update....
Click to expand...
Click to collapse
Fine and clear..
have u tried the drivers I have put in the previous post.........????
Try different USB ports to on ur PC too.......that will work sometimes.......:fingers-crossed:
have install drivers from "installing a custom ROM" page... maybe will try a different USB port after checking and re-install the drivers again.
GoRiLaz301 said:
have install drivers from "installing a custom ROM" page... maybe will try a different USB port after checking and re-install the drivers again.
Click to expand...
Click to collapse
These are the latest HTC drivers can u try this and report whether ur device is recognized in adb recovery mode......
Please try by uninstalling the previous driver u had.........
BTW is it Windows 8.......????????
ok noted but how to uninstall the previous HTC drivers ?
by the way, i also noted that if left the phone to boot after power on, connecting it to PC will be detected but windows cannot install any drivers to it. it will be recognized as HTC MP DEVICE or something similar but with unknown drivers. This normal and ok?
Yesterday feedback in POWER + VOL mode, phone can be recognized as HTC device without USB driver device installation problem.
mine now using Win 7 Home Premium 64-Bit Ed. with latest service packs and updates. Have another PC running Win Vista Biz 32-Bit ed. but not using this one as slower and many software think will affect the phone n PC connection.
Earlier before your help, have found and load TWRP version 2.6.3.0 whereas now the version is 2.4.4.0, will earlier or this 2.4xx version be any difference and affect the connection with adb?
Later will try again the USB drivers and other set up and adb too, not free to do it now...
keep update....
GoRiLaz301 said:
ok noted but how to uninstall the previous HTC drivers ?
by the way, i also noted that if left the phone to boot after power on, connecting it to PC will be detected but windows cannot install any drivers to it.
it will be recognised as HTC MP DEVICE or something similar but will unknown drivers. This normal and ok?
Yesterday feedback in POWER + VOL mode, phone can be recognised as HTC device without USB driver problem.
mine now using Win 7 Home Premium 64-Bit Ed. with latest service packs and updates. Have another PC running Win Vista Biz 32-Bit ed. but not using this one as slower and many software think will affect the phone n PC connection.
Later will try again the USB drivers and other set up and adb too, not free to do it now...
keep update....
Click to expand...
Click to collapse
From the control panel OFC
If u had installed HTC drivers u must be able to see it like this uninstall that...
O Haa haa )
Blunder me ! That's right ! Think bit exhaust after a few sleepless nights figuring out why and hows on this phone....
Now that u mentioned on HTC Driver, before u I have read post on recommended SDK Manager installation.
It is suggested to install SDK Manager with only "Android SDK Platform Tools" + "Google USB Driver" only.
did install these and later use your method to install with "USE AN EXISTING IDE" option of "installer_r22.3-windows.exe" (latest version)
But now did not see the SDK MANAGER program in Control Panel - Programs list... Should have uninstalled.
Think should uninstall the following:
[Windows Mobile Device Center], [Windows Mobile Device Center Driver Update]?
These 2 should be default software of windows or HTC Sync for sync with mobile / usb devices...
Also have installed "Universal Adb Driver" from other post too, think to uninstall this too...
Any recommendation?
GoRiLaz301 said:
Now that u mentioned on HTC Driver, before u I have read post on recommended SDK Manager installation.
It is suggested to install SDK Manager with only "Android SDK Platform Tools" + "Google USB Driver" only.
did install these and later use your method to install with "USE AN EXISTING IDE" option of "installer_r22.3-windows.exe" (latest version)
But now did not see the SDK MANAGER program in Control Panel - Programs list... Should have uninstalled.
Also have installed "Universal Adb Driver" from other post too, think to uninstall this too...
Any recommendation?
Click to expand...
Click to collapse
SDK Manager wont show up on Control panel AFAIK....
it will be a zip file which u have to extract.....
in the extracted folder u will be able to see android-sdk-windows\platform-tools from where u have to open the cmd to execute the abd/fastboot commands
I have the setup of android-sdk-windows and the HTC drivers I pointed to....
It works flawlessly so i recommend to uninstall Universal Adb driver since that isn't helping ur phone recognized anyways.....
Install the Drivers I pointed to and try wether ur phone is getting recognized....:fingers-crossed:
Note : Alternately u can try this installer also which is a small package with the necessary adb and fastboot files......
---------- Post added at 06:43 PM ---------- Previous post was at 06:32 PM ----------
GoRiLaz301 said:
Think should uninstall the following:
[Windows Mobile Device Center], [Windows Mobile Device Center Driver Update]?
These 2 should be default software of windows or HTC Sync for sync with mobile / usb devices...
Also have installed "Universal Adb Driver" from other post too, think to uninstall this too...
Any recommendation?
Click to expand...
Click to collapse
[Windows Mobile Device Center], [Windows Mobile Device Center Driver Update]?
these drivers can be there ...they are or the installation of bluetooth drivers for our phones I guess....
Just uninstall the Universal USB driver .....
If you have HTC Sync I beleive u must be having the HTC driver as I showed on the Screen shot.....
Anyways if u dont see that in the control panel install the one I gave.....U must be fine
ok these r my latest updates:
1) Uninstall HTC SYNC, HTC DRIVER, HTC BMP DRIVER, IPT INSTALLER (Internet Pass-Thru), Universal ADB Driver
2) Install latest Java JRE 7u51 (32 & 64 Bit), Java JDK 7u51 (32 & 64 Bit), detected no older java versions, reboot PC;
3) installer_r22.3-windows.exe (for SDK Manager), created C:\AndroidSDK for SDK Manager and Platform_tools, uninstall default SDK Manager in C:\Program files, Reboot PC;
4) Created Start SDK.bat and run from desktop successfully into directory C:\AndroidSDK\Platform_tools, reboot PC;
5) Install latest HTC Driver using provided link and downloaded with filename HTCDriver_4.10.0.001.msi , reboot PC
Next is to test the USB connection to phone, Q?
1) My phone cannot power on to normal JellyBean OS (as think no ROM);
2) Can only ON to POWER + VOL-DWN mode, to HBOOT > FastBoot, is this right way to test as given in the instruction of http://http://forum.xda-developers.com/showthread.php?t=2213910
2A) If need to let PC detect a working phone and install drivers, have another model [HTC ONE X], can connect USB to this working phone first to test drivers / USB?
Pause here before proceed as concern might spoil the flow of progress if taken wrong step before testing ADB command, please advice.
GoRiLaz301 said:
ok these r my latest updates:
1) Uninstall HTC SYNC, HTC DRIVER, HTC BMP DRIVER, IPT INSTALLER (Internet Pass-Thru), Universal ADB Driver
2) Install latest Java JRE 7u51 (32 & 64 Bit), Java JDK 7u51 (32 & 64 Bit), detected no older java versions, reboot PC;
3) installer_r22.3-windows.exe (for SDK Manager), created C:\AndroidSDK for SDK Manager and Platform_tools, uninstall default SDK Manager in C:\Program files, Reboot PC;
4) Created Start SDK.bat and run from desktop successfully into directory C:\AndroidSDK\Platform_tools, reboot PC;
5) Install latest HTC Driver using provided link and downloaded with filename HTCDriver_4.10.0.001.msi , reboot PC
Next is to test the USB connection to phone, Q?
1) My phone cannot power on to normal JellyBean OS (as think no ROM);
2) Can only ON to POWER + VOL-DWN mode, to HBOOT > FastBoot, is this right way to test as given in the instruction of http://http://forum.xda-developers.com/showthread.php?t=2213910
2A) If need to let PC detect a working phone and install drivers, have another model [HTC ONE X], can connect USB to this working phone first to test drivers / USB?
Pause here before proceed as concern might spoil the flow of progress if taken wrong step before testing ADB command, please advice.
Click to expand...
Click to collapse
FIne....
From bootloader boot into recovery.....
try whether u r device is recognized.......
If recognized PROFIT for the hectic work done......
then u can push a rom to ur SDCARD using adb push command......
then install as usual from the recovery........
ok, this is what the usb detected after boot into Recovery (TWRP screen) and captured a screen shot,
is it ok?
JACK POT !!!!
ADB DEVICES listed my device s/n. in recovery mode.!
GoRiLaz301 said:
ok, this is what the usb detected after boot into Recovery (TWRP screen) and captured a screen shot,
is it ok?
Click to expand...
Click to collapse
Absolutely Fine........
What I meant in While in TWRP connect ur phone to PC
double click on your Start SDK shortcut and in the CMD type
Code:
adb devices
Ur result must be like this
YES, it did show the device listed with serial no.
Now i into the [Recovery Installation] section and at the BACKUP part (pt. 15), now should i also tick Recovery + Cache to perform full backup of actual ROM? (this seem not applicable to me, is it?)
So, it's impossible to write a guide that will guarantee S-OFF but this will at least help to give you the best possible chance.
If you encounter issues attempting S-OFF using Windows, try it under Linux. Users have reported successful attempts with their device on Linux when Windows previously failed them. Easiest method if you don't already have Linux installed somewhere is to setup a bootable USB flash drive and run Linux from it. Details on that can be found here
BEFORE YOU DO ANYTHING MAKE A BACKUP UP YOUR DEVICE (INCLUDING BOOT.IMG)
Instructions for S-OFF (from rumrunner website):
Stuff in green is my on additional information/notes.
Prerequisites
32-bit Linux (Ubuntu is preferred)
Live CD’s are fine.
Live USB is fine.
Native install is fine.
VM’s are unsupported.
64-bit Linux may work with 32 bit libraries, but is unsupported.
Or Windows
HTC drivers installed and working – fastboot AND adb drivers
HTC sync removed (not closed – REMOVED)
Install HTC Sync from here (it will install drivers and the sync manager app) and then remove the Sync Manager app (See attached picture).
All other phone software removed or disabled (Samsung Kies, PDANet, etc.)
VM’s are unsupported.
ALL firewalls and internet security applications should be totally disabled. If you get stuck with rows and rows of dots during the connection test process, it’s network filtering or other network issue!
This includes anti-virus applications as well.
Do NOT clutter our support channels with support requests on an unsupported OS configuration.
A working internet connection
USB debugging enabled on your device
Fast boot disabled on your device (settings -> battery -> UNcheck “fast boot”)
Your device must be HTCDEV unlocked or rooted unless using rumrunner with a device blocked by htcdev (e.g. m7wlv)
Additional that weren't covered:
Backup your device
Flash an unsecured kernel
ZARA_CL: KitKat / Jelly Bean
ZARA_UL: KitKat / Jelly Bean
Instructions
Once you confirm you meet the above pre-requisites, it’s time to get started.
Read all of the directions on this page before proceeding to the downloads page.
Ensure device is booted to android with usb debugging enabled.
USB 2.0 ports are preferred.
USB 3.0 ports are known to cause connectivity problems
You should not be connected using any hubs which may cause connectivity issues
Use the original HTC usb cable or a cable that you know to work with adb and fastboot on this device
Ensure that lock screen security is disabled on your device.
no passcode lock
no pattern lock
no face lock
Download rumrunner for your device. Linux users – this must be to your ~/Downloads directory.
Linux users – do NOT try to download or run it from your Windows/Mac drive or a USB drive that is not formatted for native Linux use. It won’t work!
Download page is here. You want rumrunner_HTC_0.5.0 from the HTC Universal Downloads section.
Extract the archive
tar -zxf rumrunner<device>_<version>.tgz (Linux)
Unzip the file rumrunner<device>_<version>.zip (Windows)
Execute soju: linux: sudo ./soju windows: double-click soju.exe
Windows: Right-Click soju.exe and select "Run as administrator"
Agree to the terms and conditions you are prompted with in soju
Allow the exploit to do its work.
Your device will reboot several times throughout the process
If the process gets to "Pouring..." and your device boot-loops you have achieved S-OFF - This is a known issue with Jelly Bean devices and I don't know if it is a problem on KitKat. There is a file (/system/bin/hcheck) that causes a boot-loop when you are UNLOCKED and S-OFF.
If you get this problem do the following:
Hold down the power button until your phone turns off
Once off, press and hold the volume down and power buttons until your phone turns on
It will boot into the bootloader allowing you to verify you are in fact S-OFF
Press volume down to highlight "Recovery" and then press power
Once in recovery, mount the system partition
Then open the file manager. (in TWRP tap Advanced and then File Manager)
Navigate to the /system/bin folder and scroll down until you see the "hcheck" file.
Select the hcheck file and either delete or rename it.
Reboot the device and then...
Profit
This is pretty much all the extra stuff I can think of to help make your attempt to S-OFF your device go smooth.
Remember, if you're trying it through Windows and it just doesn't want to work, try Linux.
Unfortunately, I can't provide any pointers to those who try the Linux method as I am just not a Linux person.
GOOD LUCK!
Great guide Duir. You and Topper were the ones who helped me so much getting S-off. I know others will appreciate your help as much as I did.
Sent from my Virgin Mobile HTC Desire 601 cdma zara_cl
rumrunner problem
i try to s-off my device, but rumrunner doesn't work ( It can't download some updates somehow
Code:
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (6/120)
Waiting
Test 2: Booting device
Waiting for ADB (48/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (6/120)
FATAL: Download updated package at www.rumrunner.us
Press ENTER to exit
Are anyone know why?
Does your computer and phobe have access to the internet? Have you disabled all firewalls (including one in router) and disabled any anti-virus programs?
Sent from my Virgin Mobile HTC Desire 601 cdma zara_cl
iCreck said:
i try to s-off my device, but rumrunner doesn't work ( It can't download some updates somehow
Code:
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (6/120)
Waiting
Test 2: Booting device
Waiting for ADB (48/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (6/120)
FATAL: Download updated package at www.rumrunner.us
Press ENTER to exit
Are anyone know why?
Click to expand...
Click to collapse
That message is basically a network error due to firewall/antivirus.
Some things you can try:
Disable Windows Firewall
Disable Antivirus
Reboot
Make sure firewall and antivirus are still disabled.
Close as many background apps on your pc as possible.
Run soju.exe again (make sure you run it as administrator).
If it's still not working for you try Linux method.
It still not working. The first attempt due to rumrunner.us goes well. In log - Checking for updates...But second one got error.
Linux method have same error.
Then I try another s-off exploit: revone. And it work! But my device was re-S-ON, and I doubt it works for first time s-off
Sent from my HTC Desire 601
It makes me think file is no good or a network issue. U can try to download again. If it doesnt work, use a different network
http://forum.xda-developers.com/showthread.php?t=2609620&page=2
still not worked. i m trying six other networks, over windows and linux..and some my friends have same error on other devices..so i think this is rumrunner server issue
Wack! I suggest that u report the issue in the rumrunner or firewater irc
http://forum.xda-developers.com/showthread.php?p=54527533
U can try again now
Thanks it worked on my old desire 601
So we just managed to get our Huawei P9 Plus (VIE-AL10C00B106) successfully rooted
0.) *** if you have your Bootloader UNLOCK Code from Huawei, jump to STEP 3 ****
1.) downloaded DC-Unlocker, created a account, added 4 Credits(4EUR) to account. Device should have USB DEBUG Mode enabled and you need to enable 'Manufacture' mode: in dial pad type *#*#2846579#*#* - you enter the "Project Menu", go to "Background settings" -> "USB ports settings" and switch to "Manufacture mode". Dont forget to have your device Drivers (ADB) installed
2.) Once your P9 Plus is normal booted, start DC-Unlocker (here we tested 1.00.1299) , select "huawei phones" with "auto detect" and hit the Search-Button. Your device should be found and listed with IMEI, FW ect.
If you have entered your account details under "SERVER" in dc-unlocker, you can now use the "read bootloader" Button to get your bootloader unlock code - your Credits are GONE then. SAVE THIS CODE BEFORE CLOSING DC-UNLOCKER!!!!!!
3.) Boot your device in fastboot - screen should show "locked" as status on the white screen. Type command "fastboot oem unlock XXXXXXXX" (replace the XXXX with your unlock code from DC Unlocker)
4.) Phone Screen should show a WARNING Message and offer to press VOL UP to UNLOCK phone - WARNING, if you select UNLOCK and press PWR Button to agree, DEVICE WILL INSTANTLY RESETED TO MANUFACTUR DEFAULT
5.) Download the Root-SuperSU-v2.65.zip (DIRECT DOWNLOAD) and put it on a SD-Card
6.) Download the TWRP3.0.2_EMUI4.1_H95X File (DIRECT DOWNLOAD)
7.) Reboot your phone and re-enable USB DEBUG Mode, dont forget to ALLOW Debugging via PC if promped. Insert your SD-Card with the SuperSU Zip into your phone if not already done.
8.) RUN TWRP3.0.2_EMUI4.1_H95X, it will reboot your phone in Fastboot mode. By pressing 1 and then enter, you will Install TWRP 3.0.20. Follow the instructions, by pressing enter again your phone should reboot
9.) while rebooting, HOLD VOL UP and VOL DOWN together pressed until Phone tell you "booting", it should boot into TWRP now
10.) On TWRP, in the right Corner, you can Switch Language from Chinese to English (selectable, dont worry). Now go to INSTALL, move to EXT_SDCARD as source and select the SuperSU ZIP -> INSTALL
the installation of SuperSU may show mounting/unmount errors, but will be installed anyway.
After Operation is done, reboot your Phone into normal Mode. You should find SuperSU installed on your device now.
Working Firmware Versions :
VIE-AL10C00B102*
VIE-AL10C00B106
VIE-AL10C00B163
If anything goes wrong, you may RESTORE your phone to TOTAL Stock by downloading
*VIE-AL10_C00B102 (initial CN nonspecific_Android 6.0_EMUI4.1) firmware - DOWNLOAD HERE (LINK will be added later)
Put the UPDATE.APP File (~2.8GB) (content of SDupdate_Package.tar.gz) in an folder named "dload" on your MicroSD Card and reboot phone with holding VOL UP and VOL DOWN. If the Huawei Logo appears, keep Buttons pressed until DEVICE gives you a vibration impulse. Device should now completly restore initial Firmware from SD-Card. PHONE IS LOCKED again after is operation.
****** i will add Firmware Files B102(initial full release), B106(update) and B163(latest update) LATER to this thread, need to Upload them first ******
Thanks. Can Xposed work on ?
Faisal Alro8y said:
Thanks. Can Xposed work on ?
Click to expand...
Click to collapse
I flashed the framework and installed apk but it still keeps telling me "framework not running"
I'll try later again
not sure but is anyone having an issue trying to link google contacts and google calendar to the phone?
Yes, I had some problems but exported them from the web and inported them back in to the phone
Sathelp said:
Yes, I had some problems but exported them from the web and inported them back in to the phone
Click to expand...
Click to collapse
how did u do that?? so u exported it from Google contacts den used their Computer software to upload it all back in?? back there is no backup made to google moving forward yeah??
anyone knows when the international ROM will be out? i heard some variants actually allow for Google accounts to sync with the phone.
Yes, exported from the web page on my PC and put the file on my phone, then opened contacts on the phone, selected inport from the menu and imported them from the file I cresated. I found no other way at the time other than moving them to your sim card on another phone, then use that sim on your P9+
Calendar and contact sync adapter work fine here, we installed the apks I posted in the mate thread...
Does this unlock also work with the International versions for example VIE-L29 ?
Could anyone test if FlashFire works?
Guys here real TWRP with decrypt option. Chinese TWRP ****. My sources are clear and free for every one
http://forum.xda-developers.com/p9-plus/development/recovery-twrp-t3388330
Anyone could you please backup oeminfo p9 plus AL10 and share ? Thanks
Sent from my HUAWEI NXT-L29 using Tapatalk
somboons said:
Anyone could you please backup oeminfo p9 plus AL10 and share ? Thanks
Sent from my HUAWEI NXT-L29 using Tapatalk
Click to expand...
Click to collapse
Down Here:
Unzip to:
/storage/sdcard0/TWRP/BACKUPS/YOUR_SERIAL_NUMBER/2016-06-13--04-34-28_OEMinfo_A10/
Restore Backup with: TWRP
hi, i apologize for such a noob question, but i've never rooted a phone before so i'm wondering what are the benefits of rooting the Huawei P9 plus? i understand the basic gist of what rooting does and why you'd want it for phones with heavy, heavy bloat (like, say, a Samsung S5 from a US carrier). but the VIE-AL10 unit's bloatware can mostly be uninstalled (i have the china unlocked version), and with NiLS lockscreen, Nova Launcher, and the Android N theme that i got from this forum, i was able to get the phone running mostly like a normal, clean phone without any sign of those tacky Chinese bloat.
so i'm just wondering at this point what more can root do? what do you guys plan on doing, or have done, to your P9 plus after rooting?
thanks, and apologies again if this is a really dumb question for those experienced in this.
tested on L29.
Phone unlocks but I got stuck on Encryption unsuccessful loop. I did full format, but this removed the OS completely.
I have TWRP running though
Ok working unlocked rooted xposed.
Will rooting/unlocking the bootloader void the warranty or trigger some sort of counter that cannot be reset ?
How to turn phone into recovery after switching of the phone ? need to help my brother in abroad.
sam razzy said:
How to turn phone into recovery after switching of the phone ? need to help my brother in abroad.
Click to expand...
Click to collapse
Power plus volume up+ volume down.
Basically press all the buttons together.
who could help me to have the stock firmware for AL10 ?? Thanks
jvelasco said:
Down Here:
Unzip to:
/storage/sdcard0/TWRP/BACKUPS/YOUR_SERIAL_NUMBER/2016-06-13--04-34-28_OEMinfo_A10/
Restore Backup with: TWRP
Click to expand...
Click to collapse
Can you unpacke and upload only oeminfo ? I don't have P9 plus , I will add in my SRK Tool huawei.
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.
I decided to go back to - my Pixel 6 phone was in beta testing on Android 13. I decided to go back to android 12. I have left the beta testing program. The update was sent to the phone after my phone turned off and no longer turns on. Only in recovery mode. At the same time, it does not work to flash through ADB Error when applying the update: 7 (Error code: :Error opening the installation device). Maybe I need a OTA firmware from 2022-06-05
I am in this situation, I was using Android 13 for a while and recently installed Beta 2. After two days I found that I was returning to Android 12, opt-out from the Beta program, entered the update and the phone suddenly turned off. Of course, I didn't enabled USB Debugging. I started reading articles on Reddit that the phone was already bricked. I have been fighting this Pixel for 4 hours now, I will let you know if something can be fixed.
Okey. I was able to fix it! First and foremost, do not make my mistake and know what the difference between OTA image and Factory image is. I downloaded Factory and got errors with a wrong signature.
- OTA for phones with locked bootloader (sideload)
- Factory image for phones with unlocked bootloader (flashing)
The OTA image version cannot be older than the current one.
Download latest OTA image, you can download one here:
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
Download and install latest Google USB Driver (i recommend to reboot your PC after that):
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
Download and unzip Platform Tools:
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Open CMD in unzipped Platform Tools folder:
Turn your Pixel into recovery mode (Video here) - power button + volume down button, choose recovery mode using volume buttons and press power button, after that you should see black screen with small android image and No command text, then press and hold power button and press volume up.
Choose Wipe data/factory reset.
Connect your Pixel to the computer.
Go back to CMD and type adb devices, you should be able to see your Pixel in sideload status.
On Pixel choose Apply update from ADB
Still in CMD, type adb sideload path_to_the_OTA_zip_file for example:
adb sideload C:\Users\PixelUser\Downloads\oriole-ota-tpb3.220610.004-988fd1c3.zip
Wait until end of sideloading.
Done.
pindlosz1 said:
Okey. I was able to fix it! First and foremost, do not make my mistake and know what the difference between OTA image and Factory image is. I downloaded Factory and got errors with a wrong signature.
- OTA for phones with locked bootloader (sideload)
- Factory image for phones with unlocked bootloader (flashing)
The OTA image version cannot be older than the current one.
Download latest OTA image, you can download one here:
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
Download and install latest Google USB Driver (i recommend to reboot your PC after that):
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
Download and unzip Platform Tools:
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Open CMD in unzipped Platform Tools folder:
Turn your Pixel into recovery mode (Video here) - power button + volume down button, choose recovery mode using volume buttons and press power button, after that you should see black screen with small android image and No command text, then press and hold power button and press volume up.
Choose Wipe data/factory reset.
Connect your Pixel to the computer.
Go back to CMD and type adb devices, you should be able to see your Pixel in sideload status.
On Pixel choose Apply update from ADB
Still in CMD, type adb sideload path_to_the_OTA_zip_file for example:
adb sideload C:\Users\PixelUser\Downloads\oriole-ota-tpb3.220610.004-988fd1c3.zip
Wait until end of sideloading.
Done.
Click to expand...
Click to collapse
Yep, thanks for answer. It will helped me, but i already did it. My mistake was do not the wipe. It cause all trouble. Sorry what I didn't close this question.
That's okey, maybe somebody else will need help.
Grimmerio said:
Yep, thanks for answer. It will helped me, but i already did it. My mistake was do not the wipe. It cause all trouble. Sorry what I didn't close this question.
Click to expand...
Click to collapse
Hi.I also have this issue. Were you able to achieve this without usb debugging enabled?
You don't need USB Debugging if you want to sideload. OTA or “over-the-air” update can be flashed with relative ease and will not restore any of your app or system settings when applied. To go back to a previous Android version, you will want a “factory” image.
Hello, I can't solve the problem by cmd, I get a message that I can't read. What am I doing wrong? I was in android 13 beta 3.3 and I have left the beta program to go to A12 and it no longer works, I follow the steps but the error appears
martdtmor said:
Hello, I can't solve the problem by cmd, I get a message that I can't read. What am I doing wrong? I was in android 13 beta 3.3 and I have left the beta program to go to A12 and it no longer works, I follow the steps but the error appears
Click to expand...
Click to collapse
You should change name of the file. Like update.zip. and do you have all drivers installed?
Make sure that you perform a data wipe from recovery before attempting to sideload. This fixed the same issue for me.
elova78 said:
Make sure that you perform a data wipe from recovery before attempting to sideload. This fixed the same issue for me.
Click to expand...
Click to collapse
I have already done it and I get this
Have you attempted sideload since data wiping?
I have already solved it thanks to your advice
thank you very much and very grateful
Hopefully this helps someone, but for an experienced noob like me I had trouble getting into recovery mode because my device was seemingly stuck at the "Your device is corrupted" error screen.
@pindlosz1 directions helped, but to get into the recovery for my Pixel 5, I had to hold the key combination (power + volume down) for about 20 seconds or so. While holding them it went to the Google logo but _keep holding it down_ otherwise it goes back to the corrupted screen.
Eventually I made it to a menu where I could select recovery. The phone did, again, show me the corrupted device screen, but this time continuing went to _No command_ screen instead of a boot loop. From there, I pressed power and tapped volume down and was at a recovery menu.
Finally, the rest of the steps worked, _except_, upon restarting it still said corrupted device. However, I was able to continue and it loaded Android.