I'm having issues trying to downgrade to Andriod 12 from andriod 13 beta 3.
1. I've opted out of Beta
2. Software update notification received
3. Click on download and install
4. After a couple of mins get error message couldn't update 'Installation problem'
The screen remains on the update screen.
What am i doing wrong please help?
Device state: locked
edit:actually now I'm stuck in Fastboot Mode
Phone keeps rebooting back to Fastboot mode
With a locked bootloader, your only option to get fixed is to try sideloading an OTA - usually, the OTA has to be either the same as what you were most recently running or newer. Click the yellow How To Guide quick filter at the top of the list of threads for one of the root guides. Even though you're not rooting, one or two of them should tell how to sideload an OTA - just ignore things that reference root.
This is why the instructions for the Beta program say you should have an unlocked bootloader, as without an unlocked bootloader your choices to fix the situation are much more limited.
roirraW edor ehT said:
With a locked bootloader, your only option to get fixed is to try sideloading an OTA - usually, the OTA has to be either the same as what you were most recently running or newer. Click the yellow How To Guide quick filter at the top of the list of threads for one of the root guides. Even though you're not rooting, one or two of them should tell how to sideload an OTA - just ignore things that reference root.
This is why the instructions for the Beta program say you should have an unlocked bootloader, as without an unlocked bootloader your choices to fix the situation are much more limited.
Click to expand...
Click to collapse
thanks for that, any advice on how to ota pls?
Can't find any instructions sorry.
riz157 said:
thanks for that, any advice on how to ota pls?
Click to expand...
Click to collapse
You're welcome. Since I never do the OTA process, I always flash the full firmware zip (which you can't do with a locked bootloader), I can't advise any further than what I said about using the quick filter for the How To Guides. At least one or two of these threads should help you, although they may concentrate on doing so with rooting, as long as you ignore the root parts to the OTA method, you can still follow the instructions. You'll get better help to any questions in one of the threads that give OTA sideload instructions:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
roirraW edor ehT said:
Yo
You're welcome. Since I never do the OTA process, I always flash the full firmware zip (which you can't do with a locked bootloader), I can't advise any further than what I said about using the quick filter for the How To Guides. At least one or two of these threads should help you, although they may concentrate on doing so with rooting, as long as you ignore the root parts to the OTA method, you can still follow the instructions. You'll get better help to any questions in one of the threads that give OTA sideload instructions:
View attachment 5642011
Click to expand...
Click to collapse
much appreciated yes want to avoid root or unlocking the bootloader, why does google have it to make it so difficult to downgrade. Maybe take a leaf out of apple's book
To sideload you need USB debugging enabled. Reboot the device to recovery, either by powering off the device and holding power and volume up, let go of power when the phone vibrates, on the the android with an exclamation mark, tap on volume up I think it is. Or by typing in terminal
Code:
fastboot reboot recovery
since it's stuck in fastboot. In recovery tap on 'apply update from adb'
Then download the ota package from here.
Grab the platform tools (Google for it) and unzip it to c:\platform-tools if you're running windows. Open a terminal in the platform tools folder and type
Code:
adb sideload /path_to_ota.zip
Let it do its thing and you should be up and running. I wouldn't try to downgrade from the a13 beta, but you can try. Good luck!
riz157 said:
thanks for that, any advice on how to ota pls?
Can't find any instructions sorry.
Click to expand...
Click to collapse
Just a few things. You don't need USB debugging enabled for OTA updates (you can't boot into Android to enable it anyway).
Just be aware that with OTA's, you can't downgrade - only reinstall the same version or upgrade, so you need to make sure you're on Android 13 to reinstall ota version 13 (recovery mode will tell you your version).
Here's a video to help with the ota update.
riz157 said:
I'm having issues trying to downgrade to Andriod 12 from andriod 13 beta 3.
1. I've opted out of Beta
2. Software update notification received
3. Click on download and install
4. After a couple of mins get error message couldn't update 'Installation problem'
The screen remains on the update screen.
What am i doing wrong please help?
Device state: locked
edit:actually now I'm stuck in Fastboot Mode
Phone keeps rebooting back to Fastboot mode
Click to expand...
Click to collapse
Any luck with your device?
Alekos said:
Any luck with your device?
Click to expand...
Click to collapse
No luck finally contacted Google who will have this sorted.
riz157 said:
No luck finally contacted Google who will have this sorted.
Click to expand...
Click to collapse
What happened with the OTA updates? Did it complete? Getting the windows driver and fastboot/adb (platform-tools) to all work can be tricky..
what about the https:// flash.android .com/build/8151327?target=raven-user&signed=true Website?
jlede18 said:
what about the https:// flash.android .com/build/8151327?target=raven-user&signed=true Website?
Click to expand...
Click to collapse
Flash.android uses fastboot, which requires the bootloader to be unlocked. User can't unlock it since Android won't boot..
I don't think I'll be flashing beta version again lol, too much hassle to downgrade.
In the end decided to send in to Google to repair.
I think they will give me a replacement instead of repairing it.
Did anyone notice any major bugs with android 13, can't say I did?
Alekos said:
What happened with the OTA updates? Did it complete? Getting the windows driver and fastboot/adb (platform-tools) to all work can be tricky..
Click to expand...
Click to collapse
Decided against that, off to Google to fix
Alekos said:
Flash.android uses fastboot, which requires the bootloader to be unlocked. User can't unlock it since Android won't boot..
Click to expand...
Click to collapse
Copy that. Would of probably just been easier to reflash the beta back save everything, unlock the bootloader and then flash android 12
jlede18 said:
Copy that. Would of probably just been easier to reflash the beta back save everything, unlock the bootloader and then flash android 12
Click to expand...
Click to collapse
Yup, very easy to flash ota, but op didn't feel comfortable doing it unfortunately.
Might seem dumb but I used the web browser tool and flashed back to stock via that from 13 B3 it unlocks bootloader and flashes and re locks bootloader , back on stable 12 working fine then opted out of 13 beta
The way I did it was downloading the entire firmware from google and then changing the config to remove- w so your data doesn't get wiped. Then running the .su or .bat depending on your is. It worked for me. Cheers
Related
I'm not believing my eyes just yet, but honestly...
Want root? Well, then I have some good news for you:
THERE IS NO REASON TO UNLOCK YOUR BOOTLOADER TO ROOT YOUR SMARTWATCH 3!
The fastboot mode is available on locked bootloader...
And the best news I can come up with right now? It allows hot booting custom kernels! :victory:
Code:
~$ adb reboot bootloader
~$ fastboot oem unlock
...
(bootloader) : WARNING: Unlocking your device will void your warranty
(bootloader) : and erase your personal data from the device.
(bootloader) : Run "fastboot oem unlock" again to confirm.
(bootloader) : Device still locked.
OKAY [ 0.008s]
finished. total time: 0.008s
~$ fastboot reboot
rebooting...
finished. total time: 0.001s
~$ adb shell
[email protected]:/ $ su
[email protected]:/ #
I can't believe it myself, but it's TRUE! :victory:
I have rooted my device using the TWRP from this thread, this is what I did:
Made sure I had the developer options enabled;
Enabled the ADB debugging option;
Made sure the device accepted my PC as authorized;
download the TWRP image from this thread (for 5.0.2) or from this post (for 5.1.1);
Download Wear-SuperSU-v2.46.zip;
adb reboot bootloader, saw it actually boot to fastboot... this is how I looked at that time: http://images.sodahead.com/polls/001047815/gobsmacked-15792349304_xlarge.jpeg;
fastboot boot unofficial-twrp-2.8.3.0-tetra.img (incredibly I saw it boot TWRP! Well... this is like the face my colleagues where watching me pull at that moment: http://mcp53.files.wordpress.com/2012/11/gobsmacked.jpg?w=500);
adb push Wear-SuperSU-v2.46.zip /sdcard/ (installed the zip in recovery);
Reboot to system from TWRP;
Did root test;
Was seriously gobsmacked.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm investigating the possibility to have recovery on the locked device right now, which is actually something I did for many Xperia Z series devices already :angel:
What can we make of new after this?
Elpatii said:
What can we make of new after this?
Click to expand...
Click to collapse
Well, the good thing is, you can have root while you won't lose your warranty. Because unlocking bootloader === lost warranty.
What else we can do, the sky is basically the limit... or, the resolution is, of course
[NUT] said:
Well, the good thing is, you can have root while you won't lose your warranty. Because unlocking bootloader === lost warranty.
What else we can do, the sky is basically the limit... or, the resolution is, of course
Click to expand...
Click to collapse
Oh nice!
And with root in this Smartwatch, what do you think that we can make of more?
Elpatii said:
Oh nice!
And with root in this Smartwatch, what do you think that we can make of more?
Click to expand...
Click to collapse
Well, one of the things we might be able to do is create an app or a ROM modification, which will run on the phone smartwatch itself, allowing you access to the internal storage by USB cable, because that's not possible without a phone right now. Knowing Google, it was done by design, but it won't be hard to update the ROM to allow access to the internal storage through USB.
I'll be trying to get a recovery working on the device without overwriting the one in the recovery partition, which should then allow us to easily flash ROM modifications.
[NUT] said:
Well, one of the things we might be able to do is create an app or a ROM modification, which will run on the phone smartwatch itself, allowing you access to the internal storage by USB cable, because that's not possible without a phone right now. Knowing Google, it was done by design, but it won't be hard to update the ROM to allow access to the internal storage through USB.
I'll be trying to get a recovery working on the device without overwriting the one in the recovery partition, which should then allow us to easily flash ROM modifications.
Click to expand...
Click to collapse
Oh yeah, it's would be nice!
Continue to share your discovery
[NUT] said:
Well, the good thing is, you can have root while you won't lose your warranty. Because unlocking bootloader === lost warranty.
What else we can do, the sky is basically the limit... or, the resolution is, of course [emoji14]
Click to expand...
Click to collapse
Dude Great to see you here, i am very excited now as our SW3 will go in right direction, i have Asked Jerpelea about the Development of SW3 and he said it will start soon.
Also its a request Plz make a custom Kernel for this watch to Calibrate the Colors saturation and Gamma as its same yellowish Display as Honami had.
abbychauhan said:
Dude Great to see you here, i am very excited now as our SW3 will go in right direction, i have Asked Jerpelea about the Development of SW3 and he said it will start soon.
Also its a request Plz make a custom Kernel for this watch to Calibrate the Colors saturation and Gamma as its same yellowish Display as Honami had.
Click to expand...
Click to collapse
+1
Sent from my Xperia Z3
Is there a way to unlock the kernel and all four cores in the processor on latest LDZ22D build for Smartwatch 3?
[NUT] said:
I'm not believing my eyes just yet, but honestly...
Click to expand...
Click to collapse
Thanks for sharing your discovery!
I wrote an article that explores the bootloader vulnerability: http://spectrastudy.com/no-data-protection-on-sony-smartwatch-3-android-wear/
An Android Wear dev advocate at Google is now informed of it, it really should be fixed as it makes stealing data far too easy.
[NUT] said:
I'm not believing my eyes just yet, but honestly...
Want root? Well, then I have some good news for you:
THERE IS NO REASON TO UNLOCK YOUR BOOTLOADER TO ROOT YOUR SMARTWATCH 3!
The fastboot mode is available on locked bootloader...
And the best news I can come up with right now? It allows hot booting custom kernels! :victory:
Click to expand...
Click to collapse
Hi ive been trying to work this out above you said that there is away to root the watch on locked bootloader could you explain how? I can get into fastboot but theres no way to install TWRP on locked bootloader how would I flash the superuser zip on locked bootloader. Can it be done? Your method you explained is an unlocked bootloader method and with the stock recovery you can only sideload update.zips correct me if im wrong. Can you please explain the locked bootloader method??? Can it not be done on the latest build LCA43???
RJASSI21 said:
Hi ive been trying to work this out above you said that there is away to root the watch on locked bootloader could you explain how? I can get into fastboot but theres no way to install TWRP on locked bootloader how would I flash the superuser zip on locked bootloader. Can it be done? Your method you explained is an unlocked bootloader method and with the stock recovery you can only sideload update.zips correct me if im wrong. Can you please explain the locked bootloader method??? Can it not be done on the latest build LCA43???
Click to expand...
Click to collapse
fastbooting hotboot only. no flashing of custom recovery. only flash wear supersu after hotbooting.
˜xperia z3,d6653,5.1.1,v71,tapatalk
jemfalor said:
fastbooting hotboot only. no flashing of custom recovery. only flash wear supersu after hotbooting.
˜xperia z3,d6653,5.1.1,v71,tapatalk
Click to expand...
Click to collapse
Ok thanks for that
---------- Post added at 03:00 AM ---------- Previous post was at 02:28 AM ----------
jemfalor said:
fastbooting hotboot only. no flashing of custom recovery. only flash wear supersu after hotbooting.
˜xperia z3,d6653,5.1.1,v71,tapatalk
Click to expand...
Click to collapse
Just one other thing how can I check I have successfully rooted my device?
sideload an app and use its root feature. es explorer or terminal emulator
˜xperia z3,d6653,5.1.1,v71,tapatalk
RJASSI21 said:
Ok thanks for that
---------- Post added at 03:00 AM ---------- Previous post was at 02:28 AM ----------
Just one other thing how can I check I have successfully rooted my device?
Click to expand...
Click to collapse
jemfalor said:
sideload an app and use its root feature. es explorer or terminal emulator
˜xperia z3,d6653,5.1.1,v71,tapatalk
Click to expand...
Click to collapse
Or use ADB Shell to use the su command to gain root access.
[NUT] said:
Or use ADB Shell to use the su command to gain root access.
Click to expand...
Click to collapse
Ok thank you both the root features in es are very limited so its hard to tell I will try the su command later on thanks for that NUT
Edit: I did try TWRP on the latest firmware in the end LCA43 and it was successful im still yet to see if root was successful I dont have a superuser app is this normal?
This all works on the latest Android Wear build as well
RJASSI21 said:
Ok thank you both the root features in es are very limited so its hard to tell I will try the su command later on thanks for that NUT
Edit: I did try TWRP on the latest firmware in the end LCA43 and it was successful im still yet to see if root was successful I dont have a superuser app is this normal?
Click to expand...
Click to collapse
Yes, there is no app for wear (yet).
karl0ss said:
This all works on the latest Android Wear build as well
Click to expand...
Click to collapse
I will update the OP and subject after I confirmed it myself...
[NUT] said:
Or use ADB Shell to use the su command to gain root access.
Click to expand...
Click to collapse
Hi I dont think my smartwatch is rooted I ran the command but it just prints nothing I also tried system app mover app but it just keeps showing the looking for root message I cant grant root how do I do this I flashed the zip 4 times and moved it over twice what am I doing wrong?
Link To Main Thread
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
About
The WinDroid Toolkit is a Windows program built in Visual Studio using the C# programming language that simplifies the rooting process for many Android devices. The toolkit makes it easy to unlock your bootloader, flash a custom recovery and gain permanent root. It also includes other functions such as flashing kernels, pushing files and installing apps. If you find it helpful, give me a thanks and a donation if you can. If you find a bug or have a feature request, feel free to leave a reply. Thanks!
Download
WinDroid Toolkit
Changelog
Check out this document for current and past changelogs.
Supported Devices
Check out this spreadsheet for a list of currently supported devices.
Device not supported? Make a request here!
Contribute
Check out the source code on GitHub here.
Disclaimers
Please do not post, mirror, or take credit for this toolkit or any related work without explicit permission.
I am in no way responsible for any harm, damage, nuclear fission or bee infestation that may occur to your device through the use of this toolkit.
Reserved
Reserved.
WOW! That's just awesome!
Certainly I'll use this when my X Play arrives
Did anyone try this nifty tool yet? Looks promising!
that looks amazing, can anyone confirm it's working? I'm getting the XT1563 version soon
working flawlessly. thanks
Seems really promising! I am having a slight issue however.
After unlucking the bootloader succesfully, when i proceed to flash twrp, it says success. However, when I boot into recovery, i get the classic "Resting Android robot" saying "No Command"
SaladEsc said:
Seems really promising! I am having a slight issue however.
After unlucking the bootloader succesfully, when i proceed to flash twrp, it says success. However, when I boot into recovery, i get the classic "Resting Android robot" saying "No Command"
Click to expand...
Click to collapse
its because of the install-recovery.sh in system/etc folder
AnoopKumar said:
its because of the install-recovery.sh in system/etc folder
Click to expand...
Click to collapse
so you are suggesting to delete that file?
if so how can i becuase i have no root access
droider007 said:
so you are suggesting to delete that file?
if so how can i becuase i have no root access
Click to expand...
Click to collapse
after installing custom recovery using tool-kit and directly reboot to recovery from fastboot menu, then mount system and rename the install-recovery.sh :good:
Awesome tool. I just have one question. Is it possible to relock the bootloader without losing root? I unlocked bootloader manually, I boot twrp (not flashed, just boot) and installed SuperSU. So I still have the stock recovery, but I'd like to relock the bootloader without having to lose root.
ToYeD said:
Awesome tool. I just have one question. Is it possible to relock the bootloader without losing root? I unlocked bootloader manually, I boot twrp (not flashed, just boot) and installed SuperSU. So I still have the stock recovery, but I'd like to relock the bootloader without having to lose root.
Click to expand...
Click to collapse
Hallo , here is a Link with a Tut how to Unroot the Moto X Play.
My phone is hast not arrived yet. Can´t confirm the procedure. :silly:
Greeting... Kaz
i installed this program but when i reboot to recovery mod there`s "no command" (i followed the steps)
Serial Kazama said:
Hallo , here is a Link with a Tut how to Unroot the Moto X Play.
My phone is hast not arrived yet. Can´t confirm the procedure. :silly:
Greeting... Kaz
Click to expand...
Click to collapse
I want to relock the bootloader but keep root. I don't want to lose root or busybox as I need them for several functions. I just want to get rid of the annoying warning on boot that says I have an unlocked bootloader.
ToYeD said:
I want to relock the bootloader but keep root. I don't want to lose root or busybox as I need them for several functions. I just want to get rid of the annoying warning on boot that says I have an unlocked bootloader.
Click to expand...
Click to collapse
Then flash a different logo.bin
Sent from my XT1562 using XDA Free mobile app
rober788 said:
i installed this program but when i reboot to recovery mod there`s "no command" (i followed the steps)
Click to expand...
Click to collapse
That means you're still on stock recovery..
After rooting my moto battery life has benn reduced. Anyone has this problem too?
Hi guys! Just receive my new moto x play today and want to root it! Its good to go with this tool?!
Envoyé de mon Nexus 5 en utilisant Tapatalk
I've used the tool to unlock the bootloader and flash TWRP. Worked smooth and didn't really have any issues. I did had to flash TWRP twice, but that might have been an error on my part for not looking at my phone after the first flash attempt. SU installed via on screen notifications after booting into recovery, worked like a charm too.
I recommend this tool as it takes away a load of work, especially with the bootloader unlock.
When trying to boot in recovery i got "No Command" while the device is unlocked and i tried to flash new recovery...
EDIT:
You must enable "OEM unlock" after the reboot
This is the first carrier unlocked phone I've purchased. It's brand new and I bought it because I'm an M8 fanboy and my first M8 is dying. I'm on AT&T. I just got the phone and installed my SIM and setup my google accounts and all that stuff. I want to update Android but when I go to setting/about/software updates all it says is "checking". It's been checking for over an hour. Did I do something wrong? Is there a way to get the latest OTA Android for an AT&T M8?
My plan is to get to MM then unlock the bootloader and flash TWRP so I can start flashing custom ROM's. I never did anything to my original M8 but have done rooting etc on my old HTC Vivid and both my ASUS tablets.
Thanks in advance for your help.
Post fastboot getvar all result (remove serial & imei no.)
If it is a EU variant, then you can install RUU to update it to Marshmallow.
ckpv5 said:
Post fastboot getvar all result (remove serial & imei no.)
If it is a EU variant, then you can install RUU to update it to Marshmallow.
Click to expand...
Click to collapse
First, thanks for your reply ckpv5.
Second, not sure I'm following you. I can connect via ADB and it show this when I use the devices command:
device product:htc_europe model:HTC_One_M8 device:htc_m8
Is that the correct ADB command or am I just doing it wrong. Could you please provide more information. I'd really appreciate it. This is my first carrier unlocked phone so I'm a noob at this.
theandies said:
First, thanks for your reply ckpv5.
Second, not sure I'm following you. I can connect via ADB and it show this when I use the devices command:
device product:htc_europe model:HTC_One_M8 device:htc_m8
Is that the correct ADB command or am I just doing it wrong. Could you please provide more information. I'd really appreciate it. This is my first carrier unlocked phone so I'm a noob at this.
Click to expand...
Click to collapse
adb reboot bootloader
fastboot getvar all
Thanks for everyone's replies so far.
Here is what I get when doing the adb commands suggested.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now help me continue with getting this phone updated to at least MM.
:good:
theandies said:
Thanks for everyone's replies so far.
Here is what I get when doing the adb commands suggested.
Now help me continue with getting this phone updated to at least MM.
:good:
Click to expand...
Click to collapse
Download this RUU.zip
Rename it by deleting everything in name of the .zip except for 0P6BIMG (and .zip of course)
Place the renamed .zip onto your extSD card and put it into your phone. (the card must be formatted to FAT32 for this, and if it is 32gb or less, it probably already is)
Boot to bootloader and follow the prompts (vol up to confirm the flash ~ power button to reboot after it's flashed)
And that's it, super easy.
Make sure to delete the renamed .zip after the flash, or every time you boot to bootloader it'll try to update again
Good luck!
Awesome. Trying it now.
Can you school me on the information that I posted? I'm used to messing with WiFi only tablets and this is my first time messing this deep into a phone. I don't want to brick my brand new M8 so I'm going real slow.
Here is some more info if needed. I see it says s-off, is that correct? Also, once I update can I then proceed to flash TWRP and custom ROM's?
Thanks. Updated to Android 6!!! Now beware I'll have a lot more questions.
theandies said:
Thanks. Updated to Android 6!!! Now beware I'll have a lot more questions.
Click to expand...
Click to collapse
Cool! glad I could help.
A little info: since you are S-Off you shouldn't need to unlock the bootloader before you flash TWRP and ROMs, S-Off is all you'll need.
So it IS s-off! Cool. Any way you could tell me how you knew what RUU to use? Just trying to learn.
theandies said:
So it IS s-off! Cool. Any way you could tell me how you knew what RUU to use? Just trying to learn.
Click to expand...
Click to collapse
Your version-main in your getvar/ OS in your bootloader is your current firmware version. To find what you need for updating, the third series of numbers is what is important to match. In your case that was 401 which = WWE/Interanational
But that won't matter with your M8, only if you get a newer HTC device. The RUU I linked you to is not only the latest, but also the last firmware/ROM update for the M8. It won't be updated anymore and hasn't been for almost a year. In general, manufacturers and carriers will only update a device for two years.
xunholyx said:
Your version-main in your getvar/ OS in your bootloader is your current firmware version. To find what you need for updating, the third series of numbers is what is important to match. In your case that was 401 which = WWE/Interanational
But that won't matter with your M8, only if you get a newer HTC device. The RUU I linked you to is not only the latest, but also the last firmware/ROM update for the M8. It won't be updated anymore and hasn't been for almost a year. In general, manufacturers and carriers will only update a device for two years.
Click to expand...
Click to collapse
Understood. I have one more problem. My mobile data is not working. I checked all the APN settings and all of them are grayed out. Any ideas on what to do? I'll post a screenshot in a while. Just got to work.
I also tried *#*#4636#*#* but I really don't want to do anything with that yet as I really don't know what to do there and don't want to make things worse.
Texting and phone calls are working just fine.
Well snooping around the internet at work tonight I was able to figure out that I need to set my APN setting. More snooping and I found an APN setting that works......kind of. It will not go 4G LTE only HSPA. Here is a screen shot and the APN settings that get me HSPA.
I will try and duplicate the APN settings from my old phone in the mean time does anyone have a known good 4G (or 4G LTE) AT&T APN that will work with this phone? Hopefully I've posted enough information for the experts to help me get back up to speed.
Either of those APNs should work fine. Literally, the grayed out one (nextgenphone) is the one I'm on now, and it works flawlessly for me (3G, LTE, MMS, etc.). The one you entered (ATT Phone) I believe is actually the new/current one being used as default on most newer ATT phones, and should work fine as well. Your problem isn't APN, I think it's the RUU you used.
I would suggest using the AT&T RUU 6.20.502.5 from here (see RUU section): https://forum.xda-developers.com/showthread.php?t=2751432
Note the red text below the RUU. If you get Error 155 installing the RUU, you'll need to fastboot flash the firmware, before the RUU will install properly (peculiarity of US Marshmallow RUUs).
Reason you need the AT&T RUU, is that by flashing the Euro RUU, you installed the Euro radio, which is only intended to support LTE bands 3, 7, 8, 20. AT&T uses LTE bands 2, 4, 5, and 17. Therefore, you are missing support for every LTE band used by AT&T (the band or bands used by AT&T in you local area being the most important), and explains why everything works but LTE.
Great information redpoint73. I'll flash the other RUU this weekend.
Please bear with me, when you say flash via. fastboot you mean using ADB and pushing it though USB from my computer? Forgive me but as I said this is my first phone I've messed with this deep. My experience has been on ASUS tablets and most of the custom stuff done on them is usually flashed via SD card (or internal storage) 99% of the time. I can do it with the help of XDA I just don't want to render my new M8 inoperable.
theandies said:
when you say flash via. fastboot you mean using ADB and pushing it though USB from my computer?
Click to expand...
Click to collapse
If you read the red colored note regarding Error 155, under the RUUs in my Index thread (which I linked) you will see another link there, to a separate post/thread that will tell you exactly how to flash the firmware (if needed). Follow those instructions, and you will be good.
Flash via fastboot uses your computer and USB. But keep in mind that adb and fastboot are similar, but not exactly the same.
I see the RUU you suggested is an .exe file. Just connect via ADB and run that file? Also I downloaded the firmware you suggested as well. To avoid any issues should I flash that first before the RUU?
Thanks
theandies said:
I see the RUU you suggested is an .exe file. Just connect via ADB and run that file? Also I downloaded the firmware you suggested as well. To avoid any issues should I flash that first before the RUU?
Thanks
Click to expand...
Click to collapse
Just hook up your phone and double click on the download. The .exe will install a lot like software for your PC
If it fails to install booting to bootloader first before starting the RUU.exe sometimes helps.
On HTC's US website, there are both manual update instructions and a download for the RUU
I'm not sure if you'll need to flash the firmware first since you are already on Android 6, but it couldn't hurt to do so, and you might actually need to.
Awesome, this place is full of great people willing to help. I just wish I could reciprocate more.
theandies said:
Also I downloaded the firmware you suggested as well. To avoid any issues should I flash that first before the RUU?
Click to expand...
Click to collapse
It wouldn't hurt to flash firmware first. Only reason I would suggest folks to run the RUU first (and see if it works) is because not everyone is comfortable using fastboot commands to flash the firmware (and therefore may avoid having to learn how to do that). But if you are comfortable with the process to flash the firmware (it's not hard), then go ahead and do so before running the RUU.
Like xunholyx, I'm not sure if you need to flash the firmware first, or not. If you were coming from Lollipop, you definitely would need to. I have a feeling that you will indeed need to flash the US firmware before the RUU will install. Even though you are on Marshmallow firmware, it's the Euro one, so I think (but not sure) the RUU will still fail until you flash the US MM firmware.
EDIT - Forget it I found it........duh.
Thanks redpoint73. I'm going to flash the firmware first because of what you said (Euro phone vs. US).
I can't seem to find your post on how to do that again in the sea of posts. I thought I bookmarked it but it's not there. Can you be so kind as to link it up.
:good:
After updating the requisite firmware, I performed a clean flash of the latest CRDroid build (previously I was using the March 28) build. During the initial setup, as well as after through the regular settings page, I was unable to register any of my fingerprints to the biometric unlock. In the setup screen, the UDFPS lights up when pressed (see screenshot), but no matter how long I keep my finger pressed on it the print will not register. I have rebooted, clean flashed, and dirty flashed the ROM, and the problem appears every time. I have tried installing both with and without GApps. I even tried flashing LineageOS instead of CRDroid, and I had the same issue. What steps should I be taking to troubleshoot this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Do you have the backup of persist partion?
PattasuBalu said:
Do you have the backup of persist partion?
Click to expand...
Click to collapse
No, the only backup I have of my previous install is the Swift Backup of apps and settings.
Try going to stock and check if the fingerprint is working. If its working then it may be a bug. If not then I think you have over written the persist partition.
PattasuBalu said:
Try going to stock and check if the fingerprint is working. If its working then it may be a bug. If not then I think you have over written the persist partition.
Click to expand...
Click to collapse
What's the easiest way to revert to Stock? Should I just download one of the packages in the pinned post on this forum and sideload?
And if my persist partition is corrupted, what recourse do I have?
Try MSM tool. Probably one or both slots are derped. Also maybe you use wrong base firmware for these roms
sumfahg said:
What's the easiest way to revert to Stock? Should I just download one of the packages in the pinned post on this forum and sideload?
And if my persist partition is corrupted, what recourse do I have?
Click to expand...
Click to collapse
If persist partition is corrupted you have no other choice except to give your phone to OnePlus service center as this is unique for every phone.
EugenStanis said:
Try MSM tool. Probably one or both slots are derped. Also maybe you use wrong base firmware for these roms
Click to expand...
Click to collapse
MSM Tool worked fine, but I was also unable to enroll there. Seems my only choice is to find a OP service center and get the phone sent out.
sumfahg said:
MSM Tool worked fine, but I was also unable to enroll there. Seems my only choice is to find a OP service center and get the phone sent out.
Click to expand...
Click to collapse
Just dont forget to lock your bootloader and say that the new update broke your phone. BTW dont forget to take a backup of persist.img when you flash a new rom.
Yeah I have one stored in the cloud before I ever even unlocked bl. Can't just use any model persist partition..it's particular to each device. Sending in is only option or don't use fp option.
PattasuBalu said:
If persist partition is corrupted you have no other choice except to give your phone to OnePlus service center as this is unique for every phone.
Click to expand...
Click to collapse
There's also a way to re-register it. Had this happen on my 8. Just didn't work the same since.
mattie_49 said:
Yeah I have one stored in the cloud before I ever even unlocked bl. Can't just use any model persist partition..it's particular to each device. Sending in is only option or don't use fp option.
Click to expand...
Click to collapse
How did you back it up before unlocking the bootloader? Wouldn't you need to unlock the bootloader in order to root your device to access the root directory?
Also, is there any other root directory I should back up after I get my phone back, besides persist?
sumfahg said:
How did you back it up before unlocking the bootloader? Wouldn't you need to unlock the bootloader in order to root your device to access the root directory?
Also, is there any other root directory I should back up after I get my phone back, besides persist?
Click to expand...
Click to collapse
I think he took the backup via Partitions Backupper app which was the same app I used take a backup of my persist.img. But the app requires super user access to take backup.
TheKnux said:
There's also a way to re-register it. Had this happen on my 8. Just didn't work the same since.
Click to expand...
Click to collapse
Can you please mention the steps and what are the backsides of doing this?
sumfahg said:
How did you back it up before unlocking the bootloader? Wouldn't you need to unlock the bootloader in order to root your device to access the root directory?
Also, is there any other root directory I should back up after I get my phone back, besides persist?
Click to expand...
Click to collapse
Many ways to accomplish without root. And you back up the persist partition. Not root directory. Msm Read back with F8. Then find persist and send it to the root directory of C drive with Read back feature. . Password oneplus
sumfahg said:
How did you back it up before unlocking the bootloader? Wouldn't you need to unlock the bootloader in order to root your device to access the root directory?
Also, is there any other root directory I should back up after I get my phone back, besides persist
sumfahg said:
How did you back it up before unlocking the bootloader? Wouldn't you need to unlock the bootloader in order to root your device to access the root directory?
Also, is there any other root directory I should back up after I get my phone back, besides persist?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
You can backup persist and co with msm tool (read back modus)
PattasuBalu said:
Can you please mention the steps and what are the backsides of doing this?
Click to expand...
Click to collapse
Just search xda. Pretty sure it's on the OnePlus 8 or 8T forums.
if using qualcomm tools it need mbn file . i cant find that mbn file in the firmware folder . urgent hlp
fastboot oem asus-csc_lk
Andrologic said:
fastboot oem asus-csc_lk
Click to expand...
Click to collapse
Command not working
AmeNahar said:
Command not working
Click to expand...
Click to collapse
How is it not working? What do you get?
Andrologic said:
How is it not working? What do you get?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
AmeNahar said:
View attachment 5831065
Click to expand...
Click to collapse
Wrong fastboot. Do it from the bootloader page: 'fastboot reboot bootloader' or just turn on the device in bootoader mode without navigating to fastboot/fastbootd. Then use the same command. Should help.
Andrologic said:
Wrong fastboot. Do it from the bootloader page: 'fastboot reboot bootloader' or just turn on the device in bootoader mode without navigating to fastboot/fastbootd. Then use the same command. Should help.
Click to expand...
Click to collapse
i got <waiting for device> (side charger port) .can u give the actuall usb device driver ? if using fastbootd can detect . but from fastboot reboot bootloader just waiting for device
AmeNahar said:
i got <waiting for device> (side charger port) .can u give the actuall usb device driver ? if using fastbootd can detect . but from fastboot reboot bootloader just waiting for device
Click to expand...
Click to collapse
Same problem did you find any solution?!
I just found the solution
You should use side usb port for update just connect to the pc reboot to fast boot and run the command
havard20009 said:
I just found the solution
You should use side usb port for update just connect to the pc reboot to fast boot and run the command
Click to expand...
Click to collapse
cool. sorry for late reply.. my solution is change the usb cable ..i always use side port btw ..i flashed raw and flash A13 now . bcs i want to play new state(not working on rooted devices and bootloader unlocked) . thats the reason why im relocking my bootloader
*deleted.
Does relock the bootloader on official rom will give error and need to flash official rom again?
I want to root my Batman edition but scared it will give bootloop after relock bootloader in future. As the Batman official rom is never be found on the net, I would lose the Batman theme if flashed to normal version.
deddo86 said:
Does relock the bootloader on official rom will give error and need to flash official rom again?
I want to root my Batman edition but scared it will give bootloop after relock bootloader in future. As the Batman official rom is never be found on the net, I would lose the Batman theme if flashed to normal version.
Click to expand...
Click to collapse
It may give you a device corrupt error after re-lock that requires a factory reset or RAW flash meaning you may risk losing your Batman stuff - whatever that is. Best to root and leave it unlocked (you can still unroot it), or leave it alone...
Andrologic said:
It may give you a device corrupt error after re-lock that requires a factory reset or RAW flash meaning you may risk losing your Batman stuff - whatever that is. Best to root and leave it unlocked (you can still unroot it), or leave it alone...
Click to expand...
Click to collapse
The only reason I want to root it to take out the Batman theme. It's in Zip file inside the Asus Theme folder, I can extract it but all files are unreadable. Where's photos and videos are in .enc format and APKs cannot be open, even changed to .zip format.
It seems all Asus themes are like this not only for Batman theme. So my plan is to root it and take out the theme that may be inside System folder that only can be reach via root. Then relock the bootloader before selling it later.
deddo86 said:
The only reason I want to root it to take out the Batman theme. It's in Zip file inside the Asus Theme folder, I can extract it but all files are unreadable. Where's photos and videos are in .enc format and APKs cannot be open, even changed to .zip format.
It seems all Asus themes are like this not only for Batman theme. So my plan is to root it and take out the theme that may be inside System folder that only can be reach via root. Then relock the bootloader before selling it later.
Click to expand...
Click to collapse
Or unlock it and take a full system image backup with TWRP or something else and keep it stored. That way you can roll back and re-lock in case you want to sell the device one day.
You could also switch your active slot and leave one with the Batman theme on the inactive, but need to be very careful not to overwrite the Batman slot. Requires strickt manual management of where system updates are installed. Not recommended but possible.
AmeNahar said:
cool. sorry for late reply.. my solution is change the usb cable ..i always use side port btw ..i flashed raw and flash A13 now . bcs i want to play new state(not working on rooted devices and bootloader unlocked) . thats the reason why im relocking my bootloader
Click to expand...
Click to collapse
Excuse me can you share the raw file link and version information?
sorankira said:
Excuse me can you share the raw file link and version information?
Click to expand...
Click to collapse
sorry for late reply...the links and info availble on rog 6's forum
sorankira said:
Excuse me can you share the raw file link and version information?
Click to expand...
Click to collapse
[TOOL] RAW Firmware for ROG Phone 6 - can be used for CN -> WW converting
Too many people are trying to use firmware to make money, so I decided to release them for free! I got them from a site that distributes them for $10. DOWNLOAD Password is: https://androplus.org How to flash: Plug the USB Type-C cable into the...
forum.xda-developers.com
Can i relock and unlock after?
Effizio01 said:
Can i relock and unlock after?
Click to expand...
Click to collapse
Yes. I already 3 times unlock .root and relock bootloader