So I have no access to a PC which means I can't create a flashable .zip for my phone, so would it be possible to manually flash images in TWRP and have it work? I know you can flash the .img files, but I'd rather ask here and know it will work, even if it is a tedious task to do, instead of try it and do it wrong or manage to hard brick it
**Edit**
I'm guessing an option could be Flashfire? I want to switch to CopperheadOS but I'm not sure how to do it without a PC
Managed to answer my own question after trial and answer
Since I didn't receive any responses, I took matters into my own hands and messed around with TWRP. I was successfully able to return to stock using images from Google. The only part you can't do is flash cache, bootloader, or radio. Radio doesn't change as far as I'm aware, so that is okay. I'm not sure what cache does, but I do know that flashing the bootloader is important. All I did was flash the matching update/OTA zip with the bootloader I had and it work. After booting, signing in, and restoring to a backup, I was able to update to the current version available for my device (Oreo, Nexus 5X). Now I know that I can flash stock images, you just need to flash .img files and make sure you have the right bootloader to go with them. I'm guessing there is no way to flash the bootloader with TWRP, and I won't try to because it isn't advised by anybody that uses TWRP, but I'll find more info. Maybe I can do this with Chainfire?
Any questions users have, I will try to answer to the best of my ability, and I'm sure others will see this because I get a few views every now and then
Related
I've been using Android for a good two years now, but have never ventured to the 'dark side'...
Now that I have my Nexus, I'd like to flash the Google Wallet package that lukegb has nicely posted here: http://forum.xda-developers.com/showthread.php?t=1365360
It's recommended that I make a backup etc, but I have absolutely no idea what I'm doing - the Android Development forum is messy and difficult to understand for a newbie like me. Could somebody please give me an outline of how to (I assume) root my phone, unlock the bootloader and install a custom recovery so that I can fix things if I mess up the Google Wallet flash?
Also, is it possible to relock the bootloader?
Thanks to anyone who responds!
The best walkthrough for you would be this one: http://forum.xda-developers.com/showthread.php?t=1352413
It is a very simple process on these devices as they were meant to have this done. With this walkthrough if you can follow directions you can unlock and root your' device.
Yes it is possible to revert back to a stock unrooted ROM image and re-lock the bootloader. The command will look something like this.
windows:
fastboot-windows oem lock
linux:
sudo ./fastboot-linux oem lock
Also I wouldn't call it the "dark side" more..."seeing the light"
Justin
Please be aware that I am a total noob but I will try to help anyway.
I agree with JTECJ and I will use this howto when I get my Galaxy Nexus. But isn't "fastboot-windows oem lock" only for re-locking the bootloader? It will not unroot it.
I think the safest way would be to unlock the bootloader and install CWM (ClockworkMod) right away using this http://forum.xda-developers.com/showthread.php?t=1357642 and make a Nandroid backup.
With this you should have a clean full backup of your unrooted phone.
I am currently researching if it would be possible to only boot and not flash CWM to make the cleanest backup possible.
I am also searching of a way to take the Nandroid backup out of the phone.
Do you know if we can have access to "/mnt/sdcard" to secure the backup without root acess?
You are correct that command was for relocking the boot loader. In order to return to a stock ROM image without root you have to flash an image without root. Which Google has made available. You can find more detail on returning to stock here: http://forum.xda-developers.com/showthread.php?t=1366806
Having a nandroid backup would not return you to stock simply because clockworkmod requires root access to perform nandroid backups. Which means even if that's the first thing you do, it is going to store a backup of a rooted ROM.
You can easily take the nandroid backup out of the phone through different means, if you can connect it to your computer, you can just navigate to the clockworkmod folder on the sdcard and copy it over from the backup folder.
The other option is adb pulls:
linux:
sudo ./adb pull /sdcard/clockworkmod/backup/{name} ~/Desktop/{name}
windows:
adb pull /sdcard/clockworkmod/backup/{name} {location}
Justin
This make everything clear now.
I didn't know that even if you can install CWM without root you need it to make a full backup (which make sense since you need access to all files).
And since I must have root anyway and that clean backup ROM are available I'll probably just buy Root Explorer for my file manager need and send my backup with smb.
This forum is awesome and so are you. Thank you.
Ok, so I've now successfully flashed CWM. But I have yet another question now. I'm being pushed the OTA volume bug fix - should I accept it? I'm just wondering since I now have a custom recovery installed if it might mess things up.
It won't install with CWM recovery...so no. I would recommend you try this Rom http://forum.xda-developers.com/showthread.php?t=1361108 I'm not sure it has the latest volume fix in it yet but will tomorrow if its completed. Or just pay the $9 to use the kitchen.
Danny80y said:
It won't install with CWM recovery...so no. I would recommend you try this Rom http://forum.xda-developers.com/showthread.php?t=1361108 I'm not sure it has the latest volume fix in it yet but will tomorrow if its completed. Or just pay the $9 to use the kitchen.
Click to expand...
Click to collapse
Thanks for that. Slightly off-topic, but could you please give me an explanation of how I flash this: http://forum.xda-developers.com/showthread.php?t=1365360&page=2
Where do I place the file? Do I have to rename it?
I haven't tried this but just put the zip on your "virtual SD" then boot into CWM choose flash zip from sd.....find the file....then flash....choose reboot...then test it out.
Danny80y said:
I haven't tried this but just put the zip on your "virtual SD" then boot into CWM choose flash zip from sd.....find the file....then flash....choose reboot...then test it out.
Click to expand...
Click to collapse
Worked! Thanks - have Google Wallet on my phone now! Off to Greggs and McDonald's for free lunch tomorrow!
lol all this for a free lunch : )
glad you got it working, and welcome to the dark side!
Justin
So ive been doing a lot of reading on rooting phones and the best way to go about doing this, but I still have a few questions about the whole process. First IM going to briefly write what I understand about the process and have it corrected and then ask my questions.
To root:
I will follow this guide http://forums.androidcentral.com/ve...ock-bootloader-root-verizon-galaxy-nexus.html
Basically I will make sure all drivers are updated on my computer (samsung and USB)
Use command prompt to unlock the boot loader and then install superboot for the GN
after this process is done and I reboot the phone I will be unlocked and ready to go
Modding
Done through CWM
1. I will download the mod that I want and place it in my phones internal memory.
2. boot into recovery mode with CWM
3. backup the phone with CWM (can anyone tell me where the back up is saved)
4. factory reset the phone
5. install zip from SD card (which will be the mod)
6. reboot back into recovery mode and install Gapps that I downloaded from the cryogen mod wiki through the "install zip from SD card" option. http://wiki.cyanogenmod.com/index.php?title=Latest_Version
7. Reboot phone and i will be good to go
SO my questions:
1. If i missed anything, can you guys quote my steps and add in what i left out in the correct order?
2. How do I update the phone to 4.0.4. If im guessing correctly, I would rename the file to update.zip, and before i modded my phone and after the factory reset I would install that zip onto the phone? I'm just slightly confused on the process
3. How do I uninstall a mod and go back to stock
4. How do I handle OTA updates? I know that with mods, I cant download the OTA automatically. I would guess i would have to uninstall the mod, download and install the update, and then thats where I dont know what to do
5. Is there a way to back up all my apps so when I install a mod or update a mod I can just have them all reinstalled back in and have all the settings restored, without having to download each individual app and change their settings back to what they were previously?
these are all the questions that come to mind presently. Some may arise later.
Thanks in advance, and if some of my questions have already been answered in a previous thread, can you guys just post a link to that thread?
Sent from my Transformer Prime TF201
You dl'ed android sdk yet or all the fastboot files you need?
Sent from my Galaxy Nexus using xda premium
You have it correct. Use titanium backup to save all your app data. And you have to restore a nand backup if you want to undo a mod you flashed. The mod usually instructs you to backup right before flashing, so you can just revert right back if you want.
I wouldn't worry about ota anymore. Being rooted always leads to you being able to flash the latest ota quicker than if you were stock and waiting for your number to be called. Trust me after years of this that's how it always happens.
corban227 said:
So ive been doing a lot of reading on rooting phones and the best way to go about doing this, but I still have a few questions about the whole process. First IM going to briefly write what I understand about the process and have it corrected and then ask my questions.
To root:
I will follow this guide http://forums.androidcentral.com/ve...ock-bootloader-root-verizon-galaxy-nexus.html
Basically I will make sure all drivers are updated on my computer (samsung and USB)
Use command prompt to unlock the boot loader and then install superboot for the GN
after this process is done and I reboot the phone I will be unlocked and ready to go
Modding
Done through CWM
1. I will download the mod that I want and place it in my phones internal memory.
2. boot into recovery mode with CWM
3. backup the phone with CWM (can anyone tell me where the back up is saved)
4. factory reset the phone
5. install zip from SD card (which will be the mod)
6. reboot back into recovery mode and install Gapps that I downloaded from the cryogen mod wiki through the "install zip from SD card" option. http://wiki.cyanogenmod.com/index.php?title=Latest_Version
7. Reboot phone and i will be good to go
SO my questions:
1. If i missed anything, can you guys quote my steps and add in what i left out in the correct order?
2. How do I update the phone to 4.0.4. If im guessing correctly, I would rename the file to update.zip, and before i modded my phone and after the factory reset I would install that zip onto the phone? I'm just slightly confused on the process
3. How do I uninstall a mod and go back to stock
4. How do I handle OTA updates? I know that with mods, I cant download the OTA automatically. I would guess i would have to uninstall the mod, download and install the update, and then thats where I dont know what to do
5. Is there a way to back up all my apps so when I install a mod or update a mod I can just have them all reinstalled back in and have all the settings restored, without having to download each individual app and change their settings back to what they were previously?
these are all the questions that come to mind presently. Some may arise later.
Thanks in advance, and if some of my questions have already been answered in a previous thread, can you guys just post a link to that thread?
Sent from my Transformer Prime TF201
Click to expand...
Click to collapse
There are some things that don't make sense in what you are doing.
1) Yes, you install the correct drivers;
2) Yes, you unlock your bootloader; however, if you want to save any data, it would be better if you root first (before unlocking your bootloader) -- see link in my sig, backup apps/etc. and even do a full backup. Don't forget to copy all of that OFF your device, as unlocking wipes even /sdcard.
3) If you are going to install a custom ROM, then there is no need to root the stock ROM you currently have, only to overwrite it with a custom ROM. Doesn't make sense.
4) If you are installing a custom ROM, you cannot "update" it to 4.0.4, unless the dev releases a 4.0.4 update for that particular ROM.
5) If you are sticking with the stock ROM, look at the link in my sig for either how to update to 4.0.4, or, better yet since you are unlocking your bootloader (which will wipe all your data anyway), flash the full 4.0.4 ROM.
6) OTA updates are only for stock ROMs.
7) You can use Titanium Backup once you are rooted to back up apps and app data.
efrant said:
There are some things that don't make sense in what you are doing.
1) Yes, you install the correct drivers;
2) Yes, you unlock your bootloader; however, if you want to save any data, it would be better if you root first (before unlocking your bootloader) -- see link in my sig, backup apps/etc. and even do a full backup. Don't forget to copy all of that OFF your device, as unlocking wipes even /sdcard.
3) If you are going to install a custom ROM, then there is no need to root the stock ROM you currently have, only to overwrite it with a custom ROM. Doesn't make sense.
4) If you are installing a custom ROM, you cannot "update" it to 4.0.4, unless the dev releases a 4.0.4 update for that particular ROM.
5) If you are sticking with the stock ROM, look at the link in my sig for either how to update to 4.0.4, or, better yet since you are unlocking your bootloader (which will wipe all your data anyway), flash the full 4.0.4 ROM.
6) OTA updates are only for stock ROMs.
7) You can use Titanium Backup once you are rooted to back up apps and app data.
Click to expand...
Click to collapse
What's the difference between a stock rom and a custom rom? I was looking at milestone 4. What is an example of a stock rom because I would prefer that to be able to still do ota updates.
Sent from my Galaxy Nexus
corban227 said:
What's the difference between a stock rom and a custom rom? I was looking at milestone 4. What is an example of a stock rom because I would prefer that to be able to still do ota updates.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
If you are asking that question, more reading is likely in order before you start flashing things.
But anyway: a stock ROM is the ROM Google puts out. They are found here, and instructions on how to flash are in my signature. All other ROMs are custom ROMs.
Gotcha. Ill look it up tonight
Sent from my Galaxy Nexus
I ended up reading more which lead to me unlocking and installing 4.0.4
Im happy with this now and I dont feel the need to custom mod. I need my phone to be functional all the time with out being too time consuming =D thanks for the help and leading me to my conclusion
I would seriously give aokp a try, I promise its worth it. Its the same as stock there's no extra work needed or anything to worry about or deal with. Its that good.
Id say stick with stock. I tried all the custom roms and while customisation options are good, nothing better than knowing your phone is 100 percent stable and secure with a locked bootloader.
biffsmash said:
Id say stick with stock. I tried all the custom roms and while customisation options are good, nothing better than knowing your phone is 100 percent stable and secure with a locked bootloader.
Click to expand...
Click to collapse
I wouldn't recommend re-locking your bootloader if you have unlocked it. Actually, I would recommend that, every time you buy a Nexus device, the first thing you should do is unlock the bootloader. Don't forget, having an unlocked bootloader does not mean you are not "stock". An unlocked bootloader doesn't affect anything (aside from what I mentioned below).
Why you ask? Good question:
Advantages of a locked bootloader
If you lose your device, no one can easily access your data, but only if, in addition to your bootloader being locked, you have the stock recovery installed AND you have USB Debugging disabled AND you have a password on your device. However, this "risk" (if you can call it that) can be mitigated by many apps that can remotely wipe your device.
Disadvantages of a locked bootloader
You cannot use fastboot commands, so you cannot flash or boot images, which can save your butt in certain occasions.
You cannot try out new radios (assuming no root).
You cannot backup your data (i.e., make an image of your device's memory (assuming no root).
You cannot root (on 4.0.4 and later).
You cannot manually update to the latest version of Android once Google starts rolling it out. You have to wait until Google decides it's your turn, which could be minutes to months after the update becomes available.
+1 to working without me thinking. I'm leaving the boot loader unlocked to install any updates Verizon doesn't push through but other than that its staying stock. Plus I really like vanilla ICS AS IT IS
Sent from my Transformer Prime TF201 using Tapatalk 2
My vzw nexus has been running mRom version x.x for sometime. I went to install the upgraded 4.2 rom via clockworkmod, (wipe cache and dalvik, flash over current rom) and it appeared to install successfully. However, when I rebooted I saw the lock screen for a split second and it just started to boot loop. I rebooted back into recovery and wiped all data and tried to reinstall the rom via through the new 0 partition, but I get the error symlink: some symlinks failed
E: Error in /sdcard/0/mRom_v3.0_JOP40C.zip (status 7)
I think that this may have something to do with the multiple users in 4.2, but don't quote me on it. I cannot get my computer to recognize my phone, when I go to mounts in cwm I can mount everything except the sdcard, although I think this problem was evident before I flashed. Any suggestions? I could try to restore to stock using galaxynexusrestore-- http://forum.xda-developers.com/showthread.php?t=1743939 but I have not tried it before so I cannot speak to weither it will work or not.
HELP!
Always always wipe data when changing an Android version. Unless it comes via OTA, which is specifically designed to fix all the little problems that will arise.
As to how to fix the problem, flashing a factory image
http://forum.xda-developers.com/showthread.php?t=1626895 will probably work. Just follow the rules for Toro. The toolkit you linked may work, but it's generally a better idea to not use them and actually familiarize yourself with how to fix things yourself, you'll be less likely to make mistakes in the future.
Same thing happened to me.
when i try to restore from backup Clockwork can't locate the backup file because the root file structure has changed to \0.
Is there an update to Recovery that fixes this?
Help!
Misread OP.
ironerd said:
Same thing happened to me.
when i try to restore from backup Clockwork can't locate the backup file because the root file structure has changed to \0.
Is there an update to Recovery that fixes this?
Help!
Click to expand...
Click to collapse
Clockwork dev said he knows about the issue and is working on a fix.
TWRP already has a patch out that solves the problem. If you decide to temporary move to TWRP it can be flashed through fastboot or Goomanager. CWM and TWRP backups are not compatible however.
http://teamw.in/androidmultiuser useful reading for how TWRP fixed it.
same problem, stuck at JB logo
Marisa said:
Clockwork dev said he knows about the issue and is working on a fix.
TWRP already has a patch out that solves the problem. If you decide to temporary move to TWRP it can be flashed through fastboot or Goomanager. CWM and TWRP backups are not compatible however.
http://teamw.in/androidmultiuser useful reading for how TWRP fixed it.
Click to expand...
Click to collapse
I was running stock JRO03O with Clockwork Recovery Mod and decided to flash the JB 4.2 ROM from Grouper (http://forum.xda-developers.com/showthread.php?t=1993545 - I can't post there since I'm too new).
The update must have succeeded, because I can see the new 0/ partition on my phone, but it won't boot past the "X" logo. I can boot into CWM and try various things, but of course because of the data structure changes, I can't actually recover to my last save. When I'm home, I'm hoping I can get the CWM backup off my phone to restore later, but without a terminal in CWM, I can't try to fix the path.
It's nice to hear that CW is working on a fix - I hope it's retroactive (I mean, helpful to those of use who already screwed up). Also, I've never flashed anything but OTA, so I didn't realize I needed to wipe data before flashing something that's supposed to be almost stock. I guess it matters how different from stock the ROM actually is.
What's next? I'll try to interface with my PC at home. If others have this problem, I'd be happy to hear your success (or fail) stories. I'll share mine once I've tried it.
The issue with non-OTA version updates is that the OTA is specifically designed to know what little bits and pieces need to be updated, removed, or left alone.
Flashing a ROM is usually intended as a fresh slate, as the dev cannot know exactly from where you started. Basically without the wipe, you could end up with old files loitering about the system and making it do things incorrectly at boot.
Koush
When trying to restore CWM backup move previous backups AND blobs folder to /data/media/clockworkmod if the folder does not exist simply create one or if unsure just go to recovery and make new backup, it will create necessary folders for you then move (or copy to be safe) files to location.... The blobs folder is what I was missing and why I kept getting error while trying to restore.
Click to expand...
Click to collapse
This should help your problem solving for the moment, if you're familiar enough with ADB to move the files that way it shouldn't take very long at all
thanks, and update of my status
Marisa said:
The issue with non-OTA version updates is that the OTA is specifically designed to know what little bits and pieces need to be updated, removed, or left alone.
Flashing a ROM is usually intended as a fresh slate, as the dev cannot know exactly from where you started. Basically without the wipe, you could end up with old files loitering about the system and making it do things incorrectly at boot.
Click to expand...
Click to collapse
Thanks for the extra insight. I wrestled with my phone all night and finally got it back to 4.1.1 (JRO030). Along the way I screwed up my adb or fastboot drivers, and for all my efforts I couldn't get any of my nexus toolkits to recognize the phone as in fastboot mode. Adb was fine, but fastboot was a no-go. I moved to a fresh computer after someone else had success with that, and read up on how to do a manual (adb command line) flash to factory image.
Now that that's done, I'm hoping I can restore from CWM to get back to where I was. If not, then yuck, but I'm optimistic.
So I was getting tired of the rom I was on and decided to switch. I am using the BUMP'd twrp by the way. I did something really stupid. I restored the stock rooted rom while searching. Apparently it auto updated. I can now no longer get past twrp recovery no matter what i do, restore, reinstall, wipe everthing. If someone can link me to a guide using adb to flash a stock iso or something? Please help this is my everyday device.
Rule one to flashing: never flash without a backup. It sounds like something went wrong but if you can actually get into TWRP you should be able to flash either an older backup (easiest) or wipe and reinstall your current ROM. If youre wanting to go to marshmallow anyway (And as someone that has used their G3 from Jellybean all the way through to marshmallow, I cant recommend it enough), see here: http://forum.xda-developers.com/lg-g3/development/stock-d855-30b-images-kdz-flashables-t3282012
Autoprime was nice enough to pack it into 3 seperate flashable zips. Follow those instructions TO THE LETTER.
IF you can't get into TWRP for whatever reason google "D855 6.0 marshmallow official update" and find something that shows you how to do it with the official flash tool supplied by LG. Can't link it cos im not sure if im allowed to link to outside websites here.
GL
not only did i use backups i een tried to install a new rom. nothing worked. thats why i was trying to get a tutorial on what to do from here.
I've been using the forums for a while but this is the first time I post on here, so I'm not so sure if I'm posting this in the right place. But I need any help I can get at this point.
So a while ago I unlocked and rooted my Moto Z Play by flashing TWRP recovery with the fastboot ADB tools. Things were fine, but then I accidentally let the phone do an automatic OTA update. When the phone was going to boot, it went straight to TWRP recovery and after I input my unlock pattern, it gave me a couple lines of text. In these lines was a red line of text saying "Unable to mount storage" and then it would go to the recovery menu. It won't boot past the recovery anymore.
I looked it up but I can't seem to find clear answers anywhere, as many that I have found have their storage indicating that they have "0mb" when they go to backup. I don't have that problem as all my storage is present and even MTP is enabled. Hopefully someone can help me out here anyway possible.
You can not install OTA updates on ROOTED phone with TWRP recovery.
For working OTA you must have stock recovery and NO ROOT.
If you have XT 1635-02 version, you can reflash your phone using this RSD LITE unbrick tool https://forum.xda-developers.com/ge...orola-usb-drivers-rsd-lite-firmware-t3042687- and you can try to use this firmware for Moto Z Play : https://androidfilehost.com/?fid=673791459329058517
Your phone data will be deteled.
Ax1qwer said:
Your phone data will be deteled.
Click to expand...
Click to collapse
This sounds a bit too hard for me. Usually it is sufficient to flash a firmware with a similar version like you currently have installed, omitting "erase userdata", meaning you do a dirty flash keeping the data.
Alternative, if you want to keep data but erase the phone installing a firmware, you may do backup in twrp and restore data after the phone runs. But keep in mind that a) there were some problems restoring Nandroid backups on Z Play and b) /data/media must be treated separately, which usually is the data you want to keep (mainly: photos and videos you made). You need to enter your phone pin to decrypt data to mount it, maybe that is the missing step.
If you cannot receive OTA updates on a phone with custom recovery, even after (say) restoring a full TWRP System Image backup. . . doesn't that imply, in practice, that you cannot ever return to a stock experience?
I have a stock Z Play with the latest 7.1.1 updates. If I decide to unlock and install LineageOS, there is no way to get back to stock? ever? I mean, I knew about the warranty, that safetynet won't pass, and that I can't re-lock the bootloader. I'm fine with all that. But I thought I could at least get back to the stock ROM, and continue to receive OTA updates. Instead, it sounds like running my backup would be hell: the phone would constantly nag me to install OTA updates, yet if I ever slipped up and said "yes" it would be bricked.
Is there no way to back up the original recovery partition too, so that you can make the OTA updater happy?
mark04 said:
Is there no way to back up the original recovery partition too, so that you can make the OTA updater happy?
Click to expand...
Click to collapse
The are several easy possibilities.
You can get some firmware which you install using fastboot flash. You may decide to only flash stock recovery. For a successful update you need to have system, boot, recovery, logo, oem (from memory, hope I got this right) in exactly the same version.
You can use fastboot boot to start recovery. Then you should be able to restore your recovery backup.
My usual way: if you have stock, never install twrp. Always boot it when needed using fastboot boot. Then you don't need to care about recovery when updating.
If an update does not work, your always can decide to install a full stock ROM, if you omit the command "erase userdata", your data usually survives fine. No guarantee of course, always do a backup. Don't forget data/media where personal things are stored and never covered by Nandroid backup of twrp.
tag68 said:
My usual way: if you have stock, never install twrp. Always boot it when needed using fastboot boot. Then you don't need to care about recovery when updating.
Click to expand...
Click to collapse
Aha---great suggestion, thanks! I would never have thought of that, even though I had to do it on another device once where the bootloader kept overwriting the recovery.
tag68 said:
If an update does not work, your always can decide to install a full stock ROM, if you omit the command "erase userdata", your data usually survives fine. No guarantee of course, always do a backup. Don't forget data/media where personal things are stored and never covered by Nandroid backup of twrp.
Click to expand...
Click to collapse
I was just reading up on how to wipe and install a full stock ROM (factory image). It seems reasonably straightforward, IF you can find the correct image. This worries me a little, because my device is RETUS and there aren't many of those images floating around. None on lolinet.com for example. Some people say to use a RETAIL image but does anyone actually understand how they are different, and what the repercussions might be?
mark04 said:
... and there aren't many of those images floating around. None on lolinet.com for example.
Click to expand...
Click to collapse
You may have a look at firmware.center. They have a lot, but I'm not sure if all are working fine. You may need to do a backup and try. But you nowhere get the safety it's right, because Lenorola does not release signed versions (which would also allow relocking).
Note: For me all the firmwares from there worked by now.
mark04 said:
Some people say to use a RETAIL image but does anyone actually understand how they are different, and what the repercussions might be?
Click to expand...
Click to collapse
Changing update channel is said to be possible, but I never tried it. If you really want it you may try searching a bit in xda forums of similar but older phones how experiences with this are.