Please follow the steps in order to get the FM apk back on rooted phone.
Download the file from https://mega.nz/#!OQcASYKZ!cNosL1J5y5YFpe25MgrW41LxUzEwlUyroVI0gxw0YXw
copy the file to adb folder on your PC
Open the command prompt as right click and open command prompt here and run below command in order
adb root
adb remount
adb push FM.apk /data/hw_init/product/app/HwFMRadio.apk
adb reboot
Hope this works for you. If there is any issue faced, just comment and we will see for a work around. There are few changes in the directories so not sure 100% if this will work but most probably it should based on the radio.apk location on stock phone.
shashank1320 said:
Please follow the steps in order to get the FM apk back on rooted phone.
Download the file from https://mega.nz/#!OQcASYKZ!cNosL1J5y5YFpe25MgrW41LxUzEwlUyroVI0gxw0YXw
copy the file to adb folder on your PC
Open the command prompt as right click and open command prompt here and run below command in order
adb root
adb remount
adb push FM.apk /data/hw_init/product/app/HwFMRadio.apk
adb reboot
Hope this works for you. If there is any issue faced, just comment and we will see for a work around. There are few changes in the directories so not sure 100% if this will work but most probably it should based on the radio.apk location on stock phone.
Click to expand...
Click to collapse
I have downloaded the FM.apk and pasted it in the adb folder
But when I give adb root , it says "adbd cannot run as root in production builds" what does that mean?
It seems like the above method doesn't work for installing the FM radio on Honor 6x model BLN-L21C185
Sent from my BLN-L21 using Tapatalk
talvigi said:
I have downloaded the FM.apk and pasted it in the adb folder
But when I give adb root , it says "adbd cannot run as root in production builds" what does that mean?
Click to expand...
Click to collapse
Are you rooted?
shashank1320 said:
Are you rooted?
Click to expand...
Click to collapse
Yes, I am rooted, SuperSU installed and verified by rootchecker app.
{
"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"
}
BTW you didn't tell me to reboot into recovery while inputting those commands, so update your guide please, and there was an error in the commands too, that's why it didn't work for me. Otherwise it should have work as per you.
Sent from my BLN-L21 using Tapatalk
@shashank1320
Sent from my BLN-L21 using Tapatalk
talvigi said:
Yes, I am rooted, SuperSU installed and verified by rootchecker app.
BTW you didn't tell me to reboot into recovery while inputting those commands, so update your guide please, and there was an error in the commands too, that's why it didn't work for me. Otherwise it should have work as per you.
Click to expand...
Click to collapse
That should be run on adb not recovery.
Please have a look at these screen shots, and think what is wrong with the push command,
Look at the below image
It is showing the path of the folder "app" we have created by over push command. It has two radio names, one app and one folder named radio.apk bcuz I've issued the command two time each time with a little change of inverted commas, and in my opinion not only the name is wrong but the apk file is also in the wrong folder.
And let see what's inside that radio.apk folder
And by clicking on that apk file what happens?
And then when I click install it says this,
Sent from my BLN-L21 using Tapatalk
talvigi said:
Please have a look at these screen shots, and think what is wrong with the push command,
Look at the below image
It is showing the path of the folder "app" we have created by over push command. It has two radio names, one app and one folder named radio.apk bcuz I've issued the command two time each time with a little change of inverted commas, and in my opinion not only the name is wrong but the apk file is also in the wrong folder. 
And let see what's inside that radio.apk folder 
And by clicking on that apk file what happens?

And then when I click install it says this,

And let see what's inside that radio.apk folder 
And by clicking on that apk file what happens?

And then when I click install it says this,


Click to expand...
Click to collapse
You don't need to install. It will automatically after reboot.
shashank1320 said:
You don't need to install. It will automatically after reboot.
Click to expand...
Click to collapse
Well in that case it didn't install, so I have told you that it wasn't working on the phone. There still isn't any FM app on the screen.
Sent from my BLN-L21 using Tapatalk
talvigi said:
Well in that case it didn't install, so I have told you that it wasn't working on the phone. There still isn't any FM app on the screen.
Click to expand...
Click to collapse
We may need to get help from any dev here then
shashank1320 said:
We may need to get help from any dev here then
Click to expand...
Click to collapse
Hay @shashank1320, I have solved my FM radio problem by following another https://forum.xda-developers.com/showthread.php?t=3606037 thread in the forum, but the theme still doesn't work. I don't know what happened and where did I go wrong because my device's theme was absolutely fine and I wanted to tweak the FM radio but now the theme has gone.
Sent from my BLN-L21 using Tapatalk
talvigi said:
Hay @shashank1320, I have solved my FM radio problem by following another https://forum.xda-developers.com/showthread.php?t=3606037 thread in the forum, but the theme still doesn't work. I don't know what happened and where did I go wrong because my device's theme was absolutely fine and I wanted to tweak the FM radio but now the theme has gone.
Click to expand...
Click to collapse
May be you can download the firmware now and use dload to solve this..
shashank1320 said:
May be you can download the firmware now and use dload to solve this..
Click to expand...
Click to collapse
Actually I've forgot to tell you that I installed flashfire yesterday and it detected the small OTA update in my memory card and asked me to prepare and flash it, I just clicked yes and it rebooted to its environment and tried to flash the full package but failed. But later I saw that the FM radio was installed in that process. And later when I flashed the stock recovery and installed FF and again downloaded the same small OTA update and let the FF to flash in the hope that the theme would also come this way but it didn't come. Now I am stuck with the same theme, theme isn't my problem but why don't I have it? That's the question. I'll try the full software though.
I think now the best partner is FF as far as it has taken me out of the crowd.
Sent from my BLN-L21 using Tapatalk
So have you guys found any solution for the FM radio and themes problem of my honor 6x?
Sent from my iPhone using Tapatalk
talvigi said:
So have you guys found any solution for the FM radio and themes problem of my honor 6x?
Click to expand...
Click to collapse
Any plan for rebranding?
shashank1320 said:
Any plan for rebranding?
Click to expand...
Click to collapse
Haha, what happens after that? I don't think I would like a rebranded device.
Sent from my BLN-L21 using Tapatalk
talvigi said:
Haha, what happens after that? I don't think I would like a rebranded device.
Click to expand...
Click to collapse
Its just a change of region that's it and you will get everything included there FM, theme, twin app etc
shashank1320 said:
Its just a change of region that's it and you will get everything included there FM, theme, twin app etc
Click to expand...
Click to collapse
Well well well, please don't get me wrong but will I also be able to get OTA updates by debranding and how secure is it to use a lot of modifications while I only used the FF and am facing the consequences yet.
My device's security is a great concern for me and I never ever want to be an open hole.
Sent from my BLN-L21 using Tapatalk
talvigi said:
Well well well, please don't get me wrong but will I also be able to get OTA updates by debranding and how secure is it to use a lot of modifications while I only used the FF and am facing the consequences yet.
My device's security is a great concern for me and I never ever want to be an open hole.
Click to expand...
Click to collapse
Dont worry it will be full stock. I did 10 days back from China to India. For security concerns, you can relax here.i am yet to get the OTA as there wasn't any rollout yet
shashank1320 said:
Dont worry it will be full stock. I did 10 days back from China to India. For security concerns, you can relax here.i am yet to get the OTA as there wasn't any rollout yet
Click to expand...
Click to collapse
I have got a great news for you guy, I solved my honor 6x BLN-L21C185's theme and FM radio problem myself. It's a long story I'm going to create a thread on that.
But my new concern is that I am still on TWRP and I have got an OTA update B371, but it failed to flash due to costum recovery.
Now is it right that I will unzip the update.zip file and creat a dload folder in the SDcard and paste the unzipped things in it, Uninstall the Magisk from its own menu and than flash stock recovery of B361 by adb bootloader and then before start press and hold the three buttons to tell the recovery to update from the dload folder of the SDcard OR I'll have perform a factory reset on the device and download the OTA update again to upgrade to B371.
Sent from my BLN-L21 using Tapatalk
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?
Im trying to root my LG G3 and all the methods are not working for some reason. I have tried purpledrake, LG One Click GUI & script, ioroot, and towelroot without success. I dont know what else i can say to get assistance. What i really want to do is remove an absurd amount of bloatware that is on it.
Assuming you've already tried this method...
http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197
... post a pic of the CMD window after running the required commands from an administrative command prompt.
Ran into a problem where i am supposed to do "Send_Command.exe \\.\COMx < root" and i get imgur(dot)com/a/xgP66
Cant post links because i am a "new" member, sorry.
Reble548 said:
Ran into a problem where i am supposed to do "Send_Command.exe \\.\COMx < root" and i get imgur(dot)com/a/xgP66
Cant post links because i am a "new" member, sorry.
Click to expand...
Click to collapse
It seems that you don't have all the required file. Your computer can't find it.
Redownload them, put them all in the same folder (the root of your system drive is the easiest), and look for typing mistake in the file path
RapHaeL_4_4_4_ said:
Do you have ADB enable? And did you allowed your computer to communicate with the device?
Click to expand...
Click to collapse
Well i think ADB is enabled, shows as AndroidNet Sooner Single ADB Interface in the windows device manager. The computer is allowed to communicate to it.
Im also not 100% sure where exactly i am supposed to download the files from, i got LG_Root.zip from the "original guide". Is that the wrong place?
Reble548 said:
Im also not 100% sure where exactly i am supposed to download the files from, i got LG_Root.zip from the "original guide". Is that the wrong place?
Click to expand...
Click to collapse
Hello my friend. Try the One Click Method. All you have to do is have usb debugging enabled and adb installed on pc (I think, might not be needed). Also when asked you need to go to download mode.
http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
Reble548 said:
Well i think ADB is enabled, shows as AndroidNet Sooner Single ADB Interface in the windows device manager. The computer is allowed to communicate to it.
Click to expand...
Click to collapse
Just because you said "I think.."
Look in Settings > Developer option > USB Debugging
If you can't find it, ITS NOT ENABLE, and its because of this that every tool fail. look at this: http://www.kingoapp.com/root-tutorials/how-to-enable-usb-debugging-mode-on-android-5-lollipop.htm)
USB Debugging is on, id like to think im not that bad...
My problem with the LG One Click Root is it never gets pass 90% or "Rooting Phone..."
Reble548 said:
My problem with the LG One Click Root is it never gets pass 90% or "Rooting Phone..."
Click to expand...
Click to collapse
Have you tried this one?
http://forum.xda-developers.com/lg-g3/general/guide-update-to-lollipop-root-bumpd-twrp-t3048845
I really don't know what happen if this one don't work ...
Good luck
AT&T G3 D850 v.21q
Anyone have any luck with this distro? I've chased every script on every forum, but no results, good or bad. It seems the AT&T distribution of the newest OTA firmware upgrade (21q) of the last LGE device prior the G4 is as of yet just not a rootable device. Unfortunately...
Jepthah said:
Anyone have any luck with this distro? I've chased every script on every forum, but no results, good or bad. It seems the AT&T distribution of the newest OTA firmware upgrade (21q) of the last LGE device prior the G4 is as of yet just not a rootable device. Unfortunately...
Click to expand...
Click to collapse
Not any luck here either. I was trying to root my friend's LG3 and tried many guides many PC tools and One Click apks but had no success. And yes it is also 21q but its 850 not 855. I guess it doesnt matter anyway. Sad thing. Not being able to fully take control of your own device.
He wanted to remove some trash apks and install titanium backup to get ride of voice mate and some other stuff. It really really annoys me, I was so fkn sure I could help him. Hopefully they will make a tool for rooting this new firmware.
checobeltran said:
Not any luck here either. I was trying to root my friend's LG3 and tried many guides many PC tools and One Click apks but had no success. And yes it is also 21q but its 850 not 855. I guess it doesnt matter anyway. Sad thing. Not being able to fully take control of your own device.
He wanted to remove some trash apks and install titanium backup to get ride of voice mate and some other stuff. It really really annoys me, I was so fkn sure I could help him. Hopefully they will make a tool for rooting this new firmware.
Click to expand...
Click to collapse
Just FYI... took me all but 3 minutes. LG-G3 85021q.
{
"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"
}
What Method Did You USE?
owlick said:
Just FYI... took me all but 3 minutes. LG-G3 85021q.
Click to expand...
Click to collapse
May I ask what method you used to achieve root? I have had the same problems with D85021q as everyone else in this post.
Thanks for any help
D
DroidySmurf said:
May I ask what method you used to achieve root? I have had the same problems with D85021q as everyone else in this post.
Thanks for any help
D
Click to expand...
Click to collapse
+1
Edit: Success!! Finally got my D850 rooted and I"m on 21q! I used this:
http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197
The way I did it was I downloaded the Newest root method V03.zip file and extracted it. Next, I opened up the folder, right clicked in the window and opened up a command prompt. I made sure that adb found my device first then I typed in: root.bat at the command prompt.
Got the text saying that I had to manually put my phone into download mode. Did that and bam the script started doing it's thing. Pulled the battery to get out of download mode and voila, rooted.
Im so confused, I've tried following the forum thread and dont understand how to get this to work. I downloaded files and extracted to my desktop, then I enabled debugging, I'm not sure how to send the files to my phone?
Any help would be much appreciated!
Never mind, I had it rooted all along, for some reason, on the root checked basic app, it never prompted me to hit grant or deny for access, I hit grant this time when I opened app and, not it shows successfully rooted!!
Finally Worked
Egrier said:
+1
Edit: Success!! Finally got my D850 rooted and I"m on 21q! I used this:
http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197
The way I did it was I downloaded the Newest root method V03.zip file and extracted it. Next, I opened up the folder, right clicked in the window and opened up a command prompt. I made sure that adb found my device first then I typed in: root.bat at the command prompt.
Got the text saying that I had to manually put my phone into download mode. Did that and bam the script started doing it's thing. Pulled the battery to get out of download mode and voila, rooted.
Click to expand...
Click to collapse
Thank you so much for pointing me to that thread.
i tried at least 3 or 4 root methods for my wife's new phone (i need to root it and unlock bootloader before she gets it, i may have accidentally wiped her phone before : )
i will be sure to spread this around for those looking for d85021q exploits
http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197
This is the first site I got to work! Finally, after days of trying...
Now what can I do with my g3? can I put my boostmobile number onto it? can i remove at&t off of it?
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
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