I am new to android. I got sick of apps not being able to write to my SD card so I eventually got the guts to attempt rooting (which worked) and then I even convinced myself to try and install TWRP because I heard I can type commands in there to get my device still rooted after encrypting since superSU does not work after encryption (not tried it yet).
I updated to a new version of TWRP 2.8 I think? Any way, what kind of safety net do I have now? I am in the process of doing a fresh backup (everything ticked) with this new version of TWRP and I will trash the old one once this is done. I had zero intentions of flashing custom OS' on my Galaxy S4 mini (I9195 LTE) for fear of bricking my first ever brand new android phone.
Once this backup is created (and duplicated on every damn hard drive I have for backup purposes...) what kind of protection is this? Could I experiment with Cyanogen Mod and have no fear of it failing to load, have problems with it once installed, something go wrong and phone won't boot up? Would I be able to load my backup into TWRP and magically the phone would be in the state it is in today, rooted and everything?
If there are any things I should know I would appreciate being made aware of them before I dare proceed with any (what I assume would be potentially dangerous things) flashing custom roms etc because I want to always ensure I can get my phone to exactly the state it is now, with all my google apps still installed and everything. With everything ticked on my backup, is there anything that wouldn't be able to be restored, as in apps/data or anything?
Sorry for sounding like a noob, but as far as android and flashing is concerned, I am a noob.
tldr; Essentially I just want to be informed, as well as I can be, as to what I can now do (that I have TWRP installed and made a backup) and what I still shouldn't do, what isn't covered in a backup with all boxes ticked etc.
Morthawt said:
I am new to android. I got sick of apps not being able to write to my SD card so I eventually got the guts to attempt rooting (which worked) and then I even convinced myself to try and install TWRP because I heard I can type commands in there to get my device still rooted after encrypting since superSU does not work after encryption (not tried it yet).
I updated to a new version of TWRP 2.8 I think? Any way, what kind of safety net do I have now? I am in the process of doing a fresh backup (everything ticked) with this new version of TWRP and I will trash the old one once this is done. I had zero intentions of flashing custom OS' on my Galaxy S4 mini (I9195 LTE) for fear of bricking my first ever brand new android phone.
Once this backup is created (and duplicated on every damn hard drive I have for backup purposes...) what kind of protection is this? Could I experiment with Cyanogen Mod and have no fear of it failing to load, have problems with it once installed, something go wrong and phone won't boot up? Would I be able to load my backup into TWRP and magically the phone would be in the state it is in today, rooted and everything?
If there are any things I should know I would appreciate being made aware of them before I dare proceed with any (what I assume would be potentially dangerous things) flashing custom roms etc because I want to always ensure I can get my phone to exactly the state it is now, with all my google apps still installed and everything. With everything ticked on my backup, is there anything that wouldn't be able to be restored, as in apps/data or anything?
Sorry for sounding like a noob, but as far as android and flashing is concerned, I am a noob.
tldr; Essentially I just want to be informed, as well as I can be, as to what I can now do (that I have TWRP installed and made a backup) and what I still shouldn't do, what isn't covered in a backup with all boxes ticked etc.
Click to expand...
Click to collapse
The backup covers /system (Android OS with settings) /data (all user apps with settings) /EFS (Latest TWRP should backup this, too - MOST IMPORTANT as it stores your IMEI and baseband code) /boot (kernel) + caches (not that important)
In any case your phone has a "DOWNLOAD" mode integrated in the bootloader that will allow you to restore all partitions except "EFS" by flashing the stock firmware via ODIN. So as long as you have a EFS backup and nandroid backup and you don't screw up the phones bootloader (You could do this by flashing a firmware for another (incompatible) Samsung model via ODIN) you're on the safe side. You stock rom backup or a custom rom backup can easily be restored via TWRP. Even if TWRP brakes, you can flash it again via ODIN as long as your bootloader is fine.
LS.xD said:
The backup covers /system (Android OS with settings) /data (all user apps with settings) /EFS (Latest TWRP should backup this, too - MOST IMPORTANT as it stores your IMEI and baseband code) /boot (kernel) + caches (not that important)
In any case your phone has a "DOWNLOAD" mode integrated in the bootloader that will allow you to restore all partitions except "EFS" by flashing the stock firmware via ODIN. So as long as you have a EFS backup and nandroid backup and you don't screw up the phones bootloader (You could do this by flashing a firmware for another (incompatible) Samsung model via ODIN) you're on the safe side. You stock rom backup or a custom rom backup can easily be restored via TWRP. Even if TWRP brakes, you can flash it again via ODIN as long as your bootloader is fine.
Click to expand...
Click to collapse
Ok, so Odin is the only thing that could screw my phone up, given that I have a backup? What about if I attempt to install an incompatible rom via TWRP? Is that just as dangerous? Also if I were to some how screw up the bootloader, how would I fix that? In what circumstance might the bootloader get screwed up? From putting a custom mod on? Or is the bootloader getting screwed something specifically I would have to foolishly mess with?
If I download a cyanogen mod zip file and do the install through TWRP, would that essentially wipe everything and start completely fresh with the new OS as a virgin clean OS? Then I am correct, I hope, that if I want to get back my phone how it is now, with the stock firmware, rooted I would just do an install on TWRP and choose the backup and it would just make everything as it is currently? Even if it were screwed up and unable to boot into an OS? If that is the case, I would be a lot more open to trying different mods.
If I do try a custom rom like Cyanogen, is there an official way to get the google apps like playstore and gmail etc on it? I have seen random guides with strange links like "trust us this is a legit download!" Hmm...
Sorry for all the questions guys, I am just trying to become educated on key things before I attempt any other further things.
Morthawt said:
Ok, so Odin is the only thing that could screw my phone up, given that I have a backup? What about if I attempt to install an incompatible rom via TWRP? Is that just as dangerous? Also if I were to some how screw up the bootloader, how would I fix that? In what circumstance might the bootloader get screwed up? From putting a custom mod on? Or is the bootloader getting screwed something specifically I would have to foolishly mess with?
If I download a cyanogen mod zip file and do the install through TWRP, would that essentially wipe everything and start completely fresh with the new OS as a virgin clean OS? Then I am correct, I hope, that if I want to get back my phone how it is now, with the stock firmware, rooted I would just do an install on TWRP and choose the backup and it would just make everything as it is currently? Even if it were screwed up and unable to boot into an OS? If that is the case, I would be a lot more open to trying different mods.
If I do try a custom rom like Cyanogen, is there an official way to get the google apps like playstore and gmail etc on it? I have seen random guides with strange links like "trust us this is a legit download!" Hmm...
Sorry for all the questions guys, I am just trying to become educated on key things before I attempt any other further things.
Click to expand...
Click to collapse
Asking is good. Better safe than sorry
Yes, in case flash TWRP via ODIN, restore the backup and you should be fine.
Bootloader repair is about 40$ on ebay.
. Before flashing any new (different) rom,perform a NANDROID BACKUP" + manually internal SD Crad backup and then a FULL WIPE (/system /data /cache /dalvik cache /internal SD (Virgin like)
- If you just install a newer version of the same rom e.g. 03/01/2015 -> 03/14/2015 you only need to wipe /cache /dalvik cache (Not so virgin like)
- You can restore all apps/settings from NANDROID backups with "Titanium Backup" on your new OS
- I never heard of flashing a custom rom via recovery messed up the bootloader on Samsung phones, (In rare cases the EFS but you got the backup)
- Use only THIS GApps and make sure you pick the right version (For Android 4.4.x / 5.0.x / 5.1.x) -> Smallest (Pico bundle) will totally do it, you can install any other needed apps (also google's apps) from the pklaystore. Legit and safe.
Make sure you READ and UNDERSTOOD everything before you start flashing a custom rom.
LS.xD said:
Asking is good. Better safe than sorry
Yes, in case flash TWRP via ODIN, restore the backup and you should be fine.
Bootloader repair is about 40$ on ebay.
. Before flashing any new (different) rom,perform a NANDROID BACKUP" + manually internal SD Crad backup and then a FULL WIPE (/system /data /cache /dalvik cache /internal SD (Virgin like)
- If you just install a newer version of the same rom e.g. 03/01/2015 -> 03/14/2015 you only need to wipe /cache /dalvik cache (Not so virgin like)
- You can restore all apps/settings from NANDROID backups with "Titanium Backup" on your new OS
- I never heard of flashing a custom rom via recovery messed up the bootloader on Samsung phones, (In rare cases the EFS but you got the backup)
- Use only THIS GApps and make sure you pick the right version (For Android 4.4.x / 5.0.x / 5.1.x) -> Smallest (Pico bundle) will totally do it, you can install any other needed apps (also google's apps) from the pklaystore. Legit and safe.
Make sure you READ and UNDERSTOOD everything before you start flashing a custom rom.
Click to expand...
Click to collapse
Oh I will read everything before trying anything serious like this. I felt as if I was smashing my phone into the ground when I rooted it lol, so dangerous :S, even though I was following a guide. But now that I have all the tickboxes ticked and backed up and I have also copied that backup to 2 different hard drives... I should be safe with that.
So for my additional questions.
Is it possible but unlikely/impossible etc that a custom OS rom install through TWRP would break TWRP to the point of being non-functional to perform restores? (if so I know I could follow the guide again to install TWRP again)
Just to clarify, I should wipe everything except EFS right? When I do a completely new OS rom, perform the install and it should work or it will break. Regardless if it is broken and non functional OR it worked and I don't like it for some reason, I do the same thing again, boot to TWRP, format everything except EFS and install my backup and then the next time my phone is ready for use it will be as if nothing was ever done to it. Does that sound about right? If so, I might have an experiment with Cyanogen.
Also, you said you never heard of the bootloader being screwed over by a TWRP-based rom install. Does that also cover incorrect roms for a different model of the handset or completely different phones? I guess what I mean is, is it safe to perform an OS mod install via TWRP (in case you got the wrong one) and more dangerous to do it through odin if it is the wrong one?
I have a Samsung Galaxy S4 mini GT-I9195 LTE. I see the latest "stable" release is only version 10 of cyanogen mod? Yet there is v11 and v12 versions all without any stable release. Does that mean 11 and 12 won't work on my S4 mini or that it would be a mistake to install it on my phone? Or is there a method I can tell which one would be the best one to get for my phone (newest best)?
Lastly, as for odin, since I have TWRP and a backup of my phone as it is now, is there any reason to use odin for anything other than maybe reinstalling TWRP? If so, what else would require me to use odin that TWRP couldn't do?
Thanks so much for answering my questions, it is really making me feel more confident with the whole process. I don't like going into things blind, I'm a computer techie and like to know what I am doing and why I am doing it. This phone customization business is entirely new to me beyond changing settings and themes lol.
Is it possible but unlikely/impossible etc that a custom OS rom install through TWRP would break TWRP to the point of being non-functional to perform restores? (if so I know I could follow the guide again to install TWRP again)
--> You could flash a wrong zip containing a recovery (Probably you will not do)
Just to clarify, I should wipe everything except EFS right? When I do a completely new OS rom, perform the install and it should work or it will break. Regardless if it is broken and non functional OR it worked and I don't like it for some reason, I do the same thing again, boot to TWRP, format everything except EFS and install my backup and then the next time my phone is ready for use it will be as if nothing was ever done to it. Does that sound about right? If so, I might have an experiment with Cyanogen.
--> Yes
Also, you said you never heard of the bootloader being screwed over by a TWRP-based rom install. Does that also cover incorrect roms for a different model of the handset or completely different phones? I guess what I mean is, is it safe to perform an OS mod install via TWRP (in case you got the wrong one) and more dangerous to do it through odin if it is the wrong one?
--> Every rom has an updater-script that (normally) checks the compatiblity before TWRP installs it
I have a Samsung Galaxy S4 mini GT-I9195 LTE. I see the latest "stable" release is only version 10 of cyanogen mod? Yet there is v11 and v12 versions all without any stable release. Does that mean 11 and 12 won't work on my S4 mini or that it would be a mistake to install it on my phone? Or is there a method I can tell which one would be the best one to get for my phone (newest best)?
--> Stable means NO BUGS, Nightlies are updated nearly every day with the latest commits as they are in development status. May or may not contain bugs. Check out the specific rom thread on xda. Stability of the rom / bugs are discussed there by the users every day. So you can check out which version will work.
Lastly, as for odin, since I have TWRP and a backup of my phone as it is now, is there any reason to use odin for anything other than maybe reinstalling TWRP? If so, what else would require me to use odin that TWRP couldn't do?
--> Restore the phone to fully stock firmware. Such official firmware can be found at SamMobile.com
And most important: Press "thanks" at the botom of my posts
(had to remove quotes due to outside links preventing my posting.)
If I were to flash a stock firmware rom with odin, would it destroy TWRP? At which point I could flash it back on again? Or would TWRP still be there?
I think I am going to actually try Cyanogen, once I decide on a build to try. Are there any "minimum requirements" for cyanogen major versions? Like I could see I shouldn't install CM12 on my S4 mini and should instead try ones prior to 12? Or is it pretty much just a features and updates thing and 12 would work just as effectively (in terms of just "working smoothly" discounting any bugs etc) as 10?
Thanks button pressed on them, because truly your information is extremely helpful.
If I were to flash a stock firmware rom with odin, would it destroy TWRP? At which point I could flash it back on again? Or would TWRP still be there?
--> TWRP will be replaced by the stock recovery. You can instantly flash TWRP again.
I think I am going to actually try Cyanogen, once I decide on a build to try. Are there any "minimum requirements" for cyanogen major versions? Like I could see I shouldn't install CM12 on my S4 mini and should instead try ones prior to 12? Or is it pretty much just a features and updates thing and 12 would work just as effectively (in terms of just "working smoothly" discounting any bugs etc) as 10?
--> Your phone got enough permorfance to handle any kind of android version available. Bugs and performance are rom related.
LS.xD said:
If I were to flash a stock firmware rom with odin, would it destroy TWRP? At which point I could flash it back on again? Or would TWRP still be there?
--> TWRP will be replaced by the stock recovery. You can instantly flash TWRP again.
I think I am going to actually try Cyanogen, once I decide on a build to try. Are there any "minimum requirements" for cyanogen major versions? Like I could see I shouldn't install CM12 on my S4 mini and should instead try ones prior to 12? Or is it pretty much just a features and updates thing and 12 would work just as effectively (in terms of just "working smoothly" discounting any bugs etc) as 10?
--> Your phone got enough permorfance to handle any kind of android version available. Bugs and performance are rom related.
Click to expand...
Click to collapse
So when they say 5.x isn't coming to the S4 mini, that's a sales thing only?! Not based on performance limitations of my phone's hardware?
EDIT: Should I wipe Preload?
Morthawt said:
So when they say 5.x isn't coming to the S4 mini, that's a sales thing only?! Not based on performance limitations of my phone's hardware?
Click to expand...
Click to collapse
Just like that. I use 5.x on both of my phones
Galaxy Ace II -> performance is okay, with 4.4.4 it runs as hell, better than ever with stock firmware [Last official Android is 4.1]
HTC One S -> Flying on a Lollipop [Last official Android is 4.1]
LS.xD said:
Just like that. I use 5.x on both of my phones
Galaxy Ace II -> performance is okay, with 4.4.4 it runs as hell, better than ever with stock firmware [Last official Android is 4.1]
HTC One S -> Flying on a Lollipop [Last official Android is 4.1]
Click to expand...
Click to collapse
I am having trouble finding any specific information about the S4 mini LTE and CM12. I don't know if I should try the last version of CM11 instead? Not sure to try a CM12 or CM11 at the moment. I am sat here ready to perform the wipe but I just can't make my mind up which to try :|
Which reminds me, if I use the latest CM11, will there be any further security updates and things? Or are updates only on the nightlies? I would hope they will update CM11, I'd hate to think the only way you get updates is on the bleeding unstable edge :S ?
Morthawt said:
I am having trouble finding any specific information about the S4 mini LTE and CM12. I don't know if I should try the last version of CM11 instead? Not sure to try a CM12 or CM11 at the moment. I am sat here ready to perform the wipe but I just can't make my mind up which to try :|
Which reminds me, if I use the latest CM11, will there be any further security updates and things? Or are updates only on the nightlies? I would hope they will update CM11, I'd hate to think the only way you get updates is on the bleeding unstable edge :S ?
Click to expand...
Click to collapse
Possible security issues can be fixed later by modules. By the way, stock firmware is also updated just a few times and stays at this state. If you want as less trouble as possible a CM11 variant will be more sensefull for your purpose. Feel free to get some more informations HERE
LS.xD said:
Possible security issues can be fixed later by modules. By the way, stock firmware is also updated just a few times and stays at this state. If you want as less trouble as possible a CM11 variant will be more sensefull for your purpose. Feel free to get some more informations HERE
Click to expand...
Click to collapse
I am on the latest CM11 snapshot Amazing! Although I am confused by some of the options. Is there any documentation on the OS? I see for Network modes things like "2G | 3G", or "2G | 2G + 3G" and "2G | 3G | 2G + 3G" . I pretty much can assume I know that 2G | 3G means 2 or 3G but when it comes to ones with +'s that is just confusing. 2G and 3G at the same time? No idea lol.
Unfortunately the compass sensor does not work. I may have to either risk trying a CM12 or go to CM10 :/ What would you recommend?
Morthawt said:
Unfortunately the compass sensor does not work. I may have to either risk trying a CM12 or go to CM10 :/ What would you recommend?
Click to expand...
Click to collapse
2G = GSM Data
3G = UMTS / HDPA / WCDMA Data
Do you often need the compass sensor?
SlimKAT is a fast, lightweight rom and should be working.
LS.xD said:
2G = GSM Data
3G = UMTS / HDPA / WCDMA Data
Do you often need the compass sensor?
Click to expand...
Click to collapse
Not always but when I am using offline navigation software, it is very handy to see realtime if I am pointed in the right direction instead of having to wait for enough distance to be detected to determine what way I am pointing. I don't like limitations. Period. That is the root of why I am messing with... well, root and roms. I could not use software to write to my SD card because of some security "enhancement" which just crippled the functionality of having an android phone. First I rooted and used SDFIX or what ever it is, now I am testing roms to see if I can find a good one. I have the latest (this year) stable AICP installing and gaps currently. I will give this one a whirl and see what I think. I was disappointed that I could not find a nice "Hey.. this is why you should choose our rom!" page. Nothing. Just a download link and ability to get the source code.
I want to read about all the amazing reasons and features why AICP (or any rom for that matter) is a great choice. But I found no such page.
Morthawt said:
Not always but when I am using offline navigation software, it is very handy to see realtime if I am pointed in the right direction instead of having to wait for enough distance to be detected to determine what way I am pointing. I don't like limitations. Period. That is the root of why I am messing with... well, root and roms. I could not use software to write to my SD card because of some security "enhancement" which just crippled the functionality of having an android phone. First I rooted and used SDFIX or what ever it is, now I am testing roms to see if I can find a good one. I have the latest (this year) stable AICP installing and gaps currently. I will give this one a whirl and see what I think. I was disappointed that I could not find a nice "Hey.. this is why you should choose our rom!" page. Nothing. Just a download link and ability to get the source code.
I want to read about all the amazing reasons and features why AICP (or any rom for that matter) is a great choice. But I found no such page.
Click to expand...
Click to collapse
If you can't find any custom rom that fits your needs, you can also choose a modified (debloated) stock firmware if you need 100% functionality.
LS.xD said:
If you can't find any custom rom that fits your needs, you can also choose a modified (debloated) stock firmware if you need 100% functionality.
Click to expand...
Click to collapse
Those exist in the TWRP zip format? Where can I find those?
Morthawt said:
Those exist in the TWRP zip format? Where can I find those?
Click to expand...
Click to collapse
I should have read before I answered Seems not to exist for your phone. I don't know the reason.
I've seen that dual booting is possible on some phones. Was curious to know if that is possible on the OnePlus 6? I would love to be able to have DP3 of Android P to mess around with. Restart, and use my stable stock rooted OS for work / productivity.
surface13 said:
I've seen that dual booting is possible on some phones. Was curious to know if that is possible on the OnePlus 6? I would love to be able to have DP3 of Android P to mess around with. Restart, and use my stable stock rooted OS for work / productivity.
Click to expand...
Click to collapse
Probably possible later in the future, but not until a stable or official TWRP. You could take a nandroid of your ROM, then install Android P, then take a nandroid of that too, to restore whenever you please. ALWAYS be sure to disable secure lock screen in settings before you backup any TWRP or before trying to reboot recovery to flash or restore any ROM. It causes an issue with decryption that will make the phone inacessable without wiping entire data partition in TWRP.
Just a thought. If I have TWRP installed, I can essentially have current rom release on 1 slot, and have DPP on the other. Then I just switch between slots as I want. Only problem with this is the update process to newer release rom's. Is this correct?
Sorry if the question sounds weird, it's probably because I don't fully understand this. I know that the OnePlus 6 has two software slots, an A slot and a B slot, and I also have a vague idea about what those slots are doing during an update.
Looking around, I found a thread that recommends flashing software on both slots, saying that it could fix some issues. I'm currently on Oreo, and I'm planning to get back to 9.0.4., but I remember that during 9.0.2. I think, when I was upgrading from Oreo again, I locally installed the same update file twice. I installed it once, everything went well, I went back to the local upgrade menu after the restart, and installed it again. And the phone seemed to be faster for some reason, that's what I'm trying to achieve again.
The thread that I found mentioned how to flash the software on both slots while on TWRP, would locally installing it twice achieve the same effect? Or is there something else that I can do?
Thank you very much in advance
TheMadKing said:
Sorry if the question sounds weird, it's probably because I don't fully understand this. I know that the OnePlus 6 has two software slots, an A slot and a B slot, and I also have a vague idea about what those slots are doing during an update.
Looking around, I found a thread that recommends flashing software on both slots, saying that it could fix some issues. I'm currently on Oreo, and I'm planning to get back to 9.0.4., but I remember that during 9.0.2. I think, when I was upgrading from Oreo again, I locally installed the same update file twice. I installed it once, everything went well, I went back to the local upgrade menu after the restart, and installed it again. And the phone seemed to be faster for some reason, that's what I'm trying to achieve again.
The thread that I found mentioned how to flash the software on both slots while on TWRP, would locally installing it twice achieve the same effect? Or is there something else that I can do?
Thank you very much in advance
Click to expand...
Click to collapse
Yupp. Same effect ??
whizeguy said:
Yupp. Same effect ??
Click to expand...
Click to collapse
Thank you!
By all means, read @Neffy27 's FAQ if you are starting out. even as a refresher for stuff you may have forgotten.
-But do think a bit about what you are doing:
-Do not modify your phone unless you are willing to toss it into the trash, as that could well be the result, no matter how well planned.
-Always have a spare on hand. I used my old Moto G3 when my MZP died suddenly. Worked just fine. You know, things really haven't changed all that much since Gingerbread...
-If you are going to be getting the latest OTA stuff by doing a full flash you might want to reflect on just how much, or little, you would gain. We all like to think that if we have the latest security patch we are somehow more safe, though I don't believe I have ever heard of a phone being affected by something just because it is not on the latest patch. I was running my old Moto z play on an aug '18 (if I remember correctly) patch with no problems up until a few weeks ago when it was done in by an expanding battery envelope which cracked the display. Consider, also, that many of the custom roms that are available are not updated at all - it takes a ton of work to try to get/keep a custom ROM current, AND working! Yet you never hear of viruses or the like.
- Be aware that if you modify ANYTHING on your phone, even as little as a new boot logo to cover up the unlocked bootloader message, you will prevent your phone from taking any further OTA updates. Some mods, like adding TWRP, may still allow it to try to download and install an OTA, but when it reboots to finish that install, it will fail since it needs to re-boot through stock recovery to complete. And it will continue offering you that update.
- There is a difference between the partition structure in our phones on 8.x, and those on 9. 9 is not full Treble, only a "partial" Treble, and really only the addition of a second set of partitions which OTA updates can use to update the system - instead of modifying the single partition set, it modifies the other (a or b) set and boots to that on update completion. If it fails it can always boot the other set. Theoretically! Makes it safer than the old way of doing OTA updates, but this may cause problems if you try to flash a 2 partition set phone with a single partition set ROM. I don't believe anyone has run any experiments on this, so YOU, when you flash things without thinking about the situation, may get an unusable phone. I do not know the answer here. If you read these forums which detail other's problems, you may trod a bit more hesitantly!
-The idea here is to have fun, and sometimes to experiment with new things. To a newbie, losing the use of a $200 phone can be a tough life lesson. Let's help them out by helping them to be cautious!
Agreed. I've been running stock with January 2018 patch, TWRP installed and Magisk for root and successful safety net bypass.
I'm looking to see if running Lineage will help streamline any update processes. It looks like they have their own recovery too.
Maintaining root has become a pain in my ass the past few years.
Sent from my moto x4 using Tapatalk
SR3TLAW said:
Agreed. I've been running stock with January 2018 patch, TWRP installed and Magisk for root and successful safety net bypass.
I'm looking to see if running Lineage will help streamline any update processes. It looks like they have their own recovery too.
Maintaining root has become a pain in my ass the past few years.
Sent from my moto x4 using Tapatalk
Click to expand...
Click to collapse
I would be careful about lineage as folks don't seem to be able to get back to stock from it.
I agree about maintaining root. I will likely just stay on stock with this one.
So downgraded from Beta 2 of A14 to A13 and now cant get past the stage of the setup to transfer datat from an old device. It either says setting has stopped working or if i click on dont copy, it will then go to the checking info page then back again to transfer data. Have tried different A13 builds and different roms, all with the same build. Thanks.
Spell out the adb tools used.. version #
Steps used to "downgrade" your mentioning many different roms, especially confusing because you must flash (all ?) partitions to downgrade especially bootloader and such.
If you used factory web flasher or not. Or another all in one tool. Even just adb tools and double click flash-all.
I thinking you need to use factory flasher, wipe all, flash all partitions. Keep bootloader UNLOCKED.
The statement of trying to transfer data makes no sense since you likely can't get past system installation to get to transfer data.
So post steps please of your methods to get to your post question.
Maybe a better spot to post question, lots of great people in this thread!
June 7, 2023 - Beta 3 UPB3.230519.008 Global - Android 14 "Upside Down Cake" - Pixel 7 Pro [Cheetah]
Android 14 Beta program for the Pixel 7 Pro [Cheetah] Download links in the middle of the OP. Welcome to the Android 14 Developer Preview! This first release is for developers only, to help with early development, testing, and feedback...
forum.xda-developers.com
SAMVREMIX said:
So downgraded from Beta 2 of A14 to A13 and now cant get past the stage of the setup to transfer datat from an old device. It either says setting has stopped working or if i click on dont copy, it will then go to the checking info page then back again to transfer data. Have tried different A13 builds and different roms, all with the same build. Thanks.
Click to expand...
Click to collapse
Yeah...even after you downgraded successfully enough to get to the setup page/stage, maybe it was not downgraded successfully 100%.
I suggest using Google's official Android Flash Tool to reflash the full factory image to all partitions to try and get everything properly set up.
A couple of things to be sure of: best to use platform-tools r33.0.3 (in case flashing in fastbootd is necessary), make sure to check "force flash all partitions" and make sure not to check "skip secondary".
If for some reason you think flashing to both slots would be best, it hasn't been confirmed that the Android Flash Tool does this, so then you should try badabing2003's PixelFlasher to flash to both slots....
Hope this helps...
simplepinoi177 said:
Yeah...even after you downgraded successfully enough to get to the setup page/stage, maybe it was not downgraded successfully 100%.
I suggest using Google's official Android Flash Tool to reflash the full factory image to all partitions to try and get everything properly set up.
A couple of things to be sure of: best to use platform-tools r33.0.3 (in case flashing in fastbootd is necessary), make sure to check "force flash all partitions" and make sure not to check "skip secondary".
If for some reason you think flashing to both slots would be best, it hasn't been confirmed that the Android Flash Tool does this, so then you should try badabing2003's PixelFlasher to flash to both slots....
Hope this helps...
Click to expand...
Click to collapse
Have got it all sorted now. Went back to 05 May beta and that's working fine. Was using the official flashing tool and flashing all partitions and wiping butbthar was where I was getting the issue.. But now if I just wipe it works all ok.
SAMVREMIX said:
So downgraded from Beta 2 of A14 to A13 and now cant get past the stage of the setup to transfer datat from an old device. It either says setting has stopped working or if i click on dont copy, it will then go to the checking info page then back again to transfer data. Have tried different A13 builds and different roms, all with the same build. Thanks.
Click to expand...
Click to collapse
Same issue with me as well but the problem is I can't use android flash tool because oem unlocking and usb devugging was not enabled tried sideloading the OTA zip of android 13 may patch but still the same error stucked on initial screen setup please provide any leads Thanks
shivdubey said:
Same issue with me as well but the problem is I can't use android flash tool because oem unlocking and usb devugging was not enabled tried sideloading the OTA zip of android 13 may patch but still the same error stucked on initial screen setup please provide any leads Thanks
Click to expand...
Click to collapse
i have the same problem, any help?
Had the same issue, I sideloaded latest Android 14 beta 2 OTA image for my pixel 5 and that fixed the problem.
OTA images for Google Pixel | Android Developers
Instructions for downloading and appying preview OTA images for Pixel devices.
developer.android.com
A14 Beta 2.1 was just released and includes the following fix aimed at addressing this issue:
Fixed an issue that prevented users from completing device setup after opting a device running an Android 14 beta build out of the beta program. However, this fix is not backward compatible, so users that want to opt out of the beta program should take the following steps beforeopting out:
Update the device to Android 14 Beta 2.1, either through the over-the-air (OTA) update prompt, or by downloading an OTA image and then applying the update manually.
Reset the pin, pattern, or password that's used on the device by navigating to Settings > Security & privacy > Screen lock. You can use the same pin, pattern, or password that was used previously, but you need to go through the setup flow.
Opt out of the beta program by following the instructions listed for the "How can I opt out and return to a public Android release" question in the FAQ section of the Android Beta Program page.