Related
So I just bought this phone, came in Monday, got it activated the same day, was excited! I had many Android phones and rooted without any problems. This one was far easiest the root. I had the stock ROM of course, followed the easy bootloader unlock method, bam! Phone fully unlocked! Fast boot and ADB were openly available, used ADB to reboot into bootloader again to flash CMW with fast-boot. Sweet, now I have recovery! That was a lot less painful process then I had with any phone. After reaching the recovery menu via ADB reboot recovery, I flashed SuperUser for root, and was cheering in victory, then did a clean factory reset to start using my phone as if new (with SU and CMW). At this point I had no idea I could access CMW without a computer (which I should I knew I could after so many roots and unlocks), and this option for a extended reboot to recovery menu was infront of me, waiting to be flashed. http://forum.xda-developers.com/showthread.php?t=1884282 .
Now, I went ahead and try to flash this zip for those extended options, and that is where I went wrong. The zip file screwed my phone so that it would get stuck on the Sprint Logo, and then I realized I forgot to make a nandroid backup. I went ahead and try to fix it, I didn't want to deoxed my phone, wanted to keep it as Factory OEM as possible. Look a glance at the guy's update script, and realized he removed a necessary .odex file and did not include it in the stock power menu to flash back to normal, so now I was stuck w/o that necessary .odex file and a phone that gets stuck at the sprint loading screen. At this point I was still okay, but was questioning this uploader's work, he never mentioned that a deoxded was needed, and his "stock" wasn't stock, it was deoxded without the .odex.
I wanted to clean the "contamination" and start over without a clean untouched ROM, which was a terrible idea. Still forgetting to make a nandroid backup though, and went ahead and found a system dump and system images (system.img.ext4, etc), did a FULL Wipe with (no nandroid backup!) And now my system partition and user data partition in wiped clean. Of course I tried flashing the system.img.ext4 and userdata.img.ext4 and what not with fastboot to get back to clean slate but that wasn't the case. Now I got stuck on WARNING BOOTLOADER UNLOCKED, and it will not even go to a sprint logo boot.
Now I realize I never made a nandroid backup, and kept putting myself in a bigger hole without making one from the start. I tried everything, fastboot flashing, I even make a system.zip update file for CMW to copy a system dump directly to the system partition, phone boots up, flickers, goes to CMW (thought that was going to work for a second). Now I'm stuck with a semi-bricked phone not-so-brand-new-anymore Motorola Photon Q, desperately searching for a way to flash it back in working order.
I have tried and flash various system dumps from users to no avail, and there not any full roms available that can get me out of this mess. Is it anyway method I'm missing to flashing these system dumps to get my phone back online, or will I be stuck without a phone until a rom comes out? I have been using these provided dumps
http://forum.xda-developers.com/showthread.php?t=1856456
http://forum.xda-developers.com/showthread.php?t=1874359 (Bought a Hotfile prem to download this, regular was taking forever, I could reup on my faster FTP if someone wants to give it a shot).
Please help if you know a way to get my beloved phone online! I only had it for a day and I'm in love with it, have no idea where I don't hear more about this awesome phone, I was sold when I saw it in the sprint store. (Reminds me of my old galaxy s1, it was a champ!)
*EDIT*
Problem solved! Thanks arrghhh for his backup files!
1. Use fastboot to flash TWRP to recovery.
2. Make a folder and put these files in that folder!
https://dl.dropbox.com/u/12691845/system.ext4.win
https://dl.dropbox.com/u/12691845/system.ext4.win.md5
https://dl.dropbox.com/u/12691845/boot.emmc.win
https://dl.dropbox.com/u/12691845/boot.emmc.win.md5
3. Place this folder in the following directory.
[Root_of_SD_card] / TWRP / BACKUPS / T0695022LP / [your folder] ( so if your folder is called "argh_restore", it should be found in [Root_of_SD_card] / TWRP / BACKUPS / T0695022LP / argh_restore ) , and inside that folder, the files you downloaded.
4. Boot into recovery, I assume you know how to do this since you unlocked your bootloader to mess up your phone in the first place .
5. TWRP should load, press restore, your folder should show up, select it, select system and boot, enable MD5 checking, and restore your phone.
**IF YOUR FOLDER DOES NOT SHOW UP, directory may be incorrect. You can make a backup and see where it goes to figure out where to place your backup folder!
6. Reboot your phone, your good to go!!
PS. This backup is NOT CLEAN stock! It is stock with deoxed, battery & toggle mod, and extended menu mod, I BELIEVE. Those are the only mods really available so that's my assumption, but arrghhh may know since it is HIS backup that he provided. So far, I've been using phone all day, seems to be running well. Just like stock! Also, I can't forget, shabby's awesome SuperUser mod for root! (You won't need CMW since you have TWRP, but if you want to swtich recovery, thats up to you. CMW is most popular recovery but TWRP is really great as well)!
I'd say you're going to NEED a nandroid backup to restore...
I was hoping flashing the de-odexed would work for ya. Would a nandroid backup of the system partition work? Hopefully it does, because that's about all I can think of to provide for you...
And lesson learned, I hope. Anytime, you do ANYTHING in recovery - MAKE A BACKUP!!
Edit - I re-read your post, did you try flashing the full de-odexed version? Seems like you have some hatred of it, lol... but if it saves your butt who cares.
I did flash a odex system dump, a deoxed system dump, and a system.img.ext4 dump to no avail.
But when the issue first occurred after I flashed the new power menu, I never flash the deoxed version to get the new menu to work. I know it was needed the issue but wanted to restore the original odex. I wanted to keep the phone system as OEM as possible (had some bad experience with modding to much, things don't work they way they use too). I could have done that to fix the issue before, but since I wiped it won't make a difference now (formatted /system /data /cache in CMW).
A Nandroid backup should definitely work I can though!!!!
If I can use someone working Motorola photon Q Nandroid backup I should be able to do a restore all of the system files I wiped (I'm not sure if any other partition other then the /system in the Nandroid backup would have to be restored to get the phone working, I know there /data but I think /system adds the files on first boot to /data?). I can still fully boot into recovery/fastboot but just need recover the system files back.
Sorry to hear you had problems i have supplied links in previous posts to all files Deodexd and back to original odex
PhotonQ stock Deodexd
PhotonQ stock Odexd
hope one of these help you get going
Yea, I meant try flashing the de-odexed version... even now after you're busted. Rangerbry kindly posted both tho. Hopefully that gets you back in business.
Just read he formated /system tho i can upload all that unless someone beats me to it
Sent from my XT897 using Tapatalk 2
Rangerbry said:
Just read he formated /system tho i can upload all that unless someone beats me to it
Click to expand...
Click to collapse
I get that he wiped /system. I thought what you posted would restore that? I guess not "all" of it eh?
I can take a nandroid backup of /system, but at this point it's been modified - it's far from OEM...
I have a few old nandroid backups, but I don't know if I kept the completely stock one. I should have in retrospect, so I'm going to hope I can find it...
Edit - the only backup of /system I have is a .win file for TWRP... sorry.
If it works I'll take it! lol. Stock would be nice but I have no choice at the moment. I could use a modded rom until a stock rom comes out, just don't want to be with a paper weight lol. I'm trying the Photon Q stock Odexed.zip right now though.
I have a full stock pull i keep on hard drive but cant get it till after work
Sent from my XT897 using Tapatalk 2
Ya may need full stock pull, flashed odex with no avail .
SleepyPanchoo said:
Ya may need full stock pull, flashed odex with no avail .
Click to expand...
Click to collapse
Well here's the system.ext4.win file and the md5.
Not sure if it'll work for you at all, since the file was extracted using TWRP, and you are on CWM... I looked at my CWM backups, and I didn't take a full CWM backup it seems :/ At least I can't find it...
I know shabby has stock images pulled from the Motorola Photon Q here : http://forum.xda-developers.com/showthread.php?t=1856456
I did fastboot flash the system.img.ext4 (523 mb - seems like a full system image!) he has provided to no avail. But I'm thinking it should have worked? Its looks like a full system.img that should write all the necessary data to the /system partition to get me going, unless I have to rename system.img.ext4 to system.img before flashing, I'd have to get that a try and see if that makes a difference.
I can give that try as well and see that will fix my phone. Thanks for all the help you guys are giving me. I thought I was alone!
SleepyPanchoo said:
I can give that try as well and see that will fix my phone. Thanks for all the help you guys are giving me. I thought I was alone!
Click to expand...
Click to collapse
No prob and last i checked this is XDA no ones ever alone in getting problems fixed here. Still going to be several hrs until i get home tho
Sent from my XT897 using Tapatalk 2
arrrghhh said:
Well here's the system.ext4.win file and the md5.
Not sure if it'll work for you at all, since the file was extracted using TWRP, and you are on CWM... I looked at my CWM backups, and I didn't take a full CWM backup it seems :/ At least I can't find it...
Click to expand...
Click to collapse
Just flashed TWRP 2.2.2.2 gonna give your system.img a shot!
Looks like it help me resotre your nandroid backup of your /system partition, but still doesn't boot. This is the file sizes I see when I go to backup in TWRP
System ( 224 MB )
Data ( 0 MB )
Boot ( 10 MB )
Recovery ( 10 MB )
Cache ( 16 MB )
Don't think data should be 0 MB? Maybe a full nandroid backup would work?
*EDIT*
I'm using shabby's stock images to fastboot flash userdata.img.ext4 but does not seem to have any effect. Data is still the same size. I may need a full nandroid backup to get this phone recovered, guess I will have to wait Rangerbry to upload that backup. hopefully that will work.
SleepyPanchoo said:
Looks like it restored your nandroid backup of your /system partition, but still doesn't boot. This is the file sizes I see when I go to backup in TWRP
System ( 224 MB )
Data ( 0 MB )
Boot ( 10 MB )
Recovery ( 10 MB )
Cache ( 16 MB )
Don't think data should be 0 MB? Maybe a full nandroid backup would work?
Click to expand...
Click to collapse
Did you restore "everything" or what was checked on restore?
I did restored everything but it seems the nandroid backup you gave me was a system-only backup. Data, cache, etc was not included in this backup. I made a backup of my wiped phone and overwritten the empty system backup with the /system backup you provided me, then restored it. Even though system is there phone still gets stuck on "WARNING BOOTLOADER UNLOCKED" screen. I may need a full entire backup (/system /data /boot /recovery /cache), if that doesn't work I'm not sure what will.. :/.
*Maybe Sprint can reflash back to stock or replace?
SleepyPanchoo said:
I did restored everything but it seems the nandroid backup you gave me was a system-only backup. Data, cache, etc was not included in this backup. I made a backup of my wiped phone and overwritten the empty system backup with the /system backup you provided me, then restored it. Even though system is there phone still gets stuck on "WARNING BOOTLOADER UNLOCKED" screen. I may need a full entire backup (/system /data /boot /recovery /cache), if that doesn't work I'm not sure what will.. :/.
*Maybe Sprint can reflash back to stock or replace?
Click to expand...
Click to collapse
Why would you need my /data? Or /cache!?! That doesn't make any sense.
I can provide a backup of /boot and /recovery.
Edit - Hrm... Well, /recovery shouldn't be needed. boot.emmc.win / md5
Wouldn't data have some required files for android to work? I know it contains user data as well (such as apps) but a nandroid backup, factory reset, then 2nd android backup that is given out can be made. Im sure cache is not necessary, but I'm trying everything at the moment, nothing seems to work when it feels like it should...!! I guess I can give your /boot a try. Don't think its /recovery since Im using your recovery now lol.
Had to replace my M8 and was hoping I could just nandroid from a prior backup on the previous (identical).
I created the folder structure, and TWRP will run the restore process, but it fails at system each time.
Any suggestions? Looks like I can restore data fine. Using CleanROM.
Thanks!
[Update] Flashing CleanROM over seems to retain most apps/settings as long as I don't wipe first (assume this is the same as wiping/flashing CleanROM then restoring data only).
Malaclypse5 said:
Had to replace my M8 and was hoping I could just nandroid from a prior backup on the previous (identical).
I created the folder structure, and TWRP will run the restore process, but it fails at system each time.
Any suggestions? Looks like I can restore data fine. Using CleanROM.
Thanks!
Click to expand...
Click to collapse
I did it but it was a while ago. I'm pretty sure you need to be on the same version of TWRP that you created the Nandroid with.
Duckman_UF said:
I did it but it was a while ago. I'm pretty sure you need to be on the same version of TWRP that you created the Nandroid with.
Click to expand...
Click to collapse
Thanks, good to know it's possible. I'm pretty sure I'm on the same version (when I installed recovery this time I just fastbooted the same image from the same adb directories I had setup last time).
Malaclypse5 said:
Thanks, good to know it's possible. I'm pretty sure I'm on the same version (when I installed recovery this time I just fastbooted the same image from the same adb directories I had setup last time).
Click to expand...
Click to collapse
That will work!
Duckman_UF said:
That will work!
Click to expand...
Click to collapse
I still fail at restoring system, but restoring data got me most of the way there (hopefully its stable! seems just fine so far).
Any suggestions I'd love to hear em (always thought this should be seamless but first time trying) and thanks for your feedback!
Malaclypse5 said:
I still fail at restoring system, but restoring data got me most of the way there (hopefully its stable! seems just fine so far).
Any suggestions I'd love to hear em (always thought this should be seamless but first time trying) and thanks for your feedback!
Click to expand...
Click to collapse
I don't quite understand why you would want to restore system. Flashing the rom is just as easy and much cleaner. There may be a problem with device ID from the old phone - really have no idea.
But going from one device to another I would flash the rom, restore data - done. You should have an identical phone.
berndblb said:
I don't quite understand why you would want to restore system. Flashing the rom is just as easy and much cleaner. There may be a problem with device ID from the old phone - really have no idea.
But going from one device to another I would flash the rom, restore data - done. You should have an identical phone.
Click to expand...
Click to collapse
Thanks! The only thing I lost by not restoring system are zip's/mods I flashed in twrp seperately, also Xposed framework settings (some didn't carry over). Thanks for the support!
OP, do you have Titanium Backup? It can extract from a Nandroid. Menu>Extract from Nandroid Backup. It takes a while, even if your backup isn't compressed, but it works just fine.
If you DON'T have Titanium, skip Google Play and just Google it. Buy it from his website. Costs you less, developer makes more money (Google doesn't get a cut) and you get a text file for a license. This is much easier than dealing with the license app. Just download the latest version whenever there's an update and stick it on your SD card/internal, and install it upon flashing a new ROM. Text license goes in the root of either. App will pick it up on first run. Real easy. And it can do a ton of other things, too.
I'm done it twice now on two separate Verizon refurbs to find the M8. It has always worked wonderfully for me. Saves a lot of time in setting back up. You do have to create a new TWRP folder though by doing in a quick backup on the new phone, the moving the backup into the new TWRP folder otherwise it won't see it. TWRP will create a new folder with a different set of numbers In your original TWRP folder. You just move it to that. I did it successfully with Viper one Rom twice now.
Hello Guys,
Since I totally bricked my old Nexus 5 16GB(KTU84P) I am going to get a new one. But I am thinking of getting the 32GB version this time.
Now before it got bricked I made a full nandroid back-up with the help of the Nexus Root Toolkit and TWRP.
Now here are a few (stupid) questions:
~Is it possible to restore a nandroid backup from one phone to another and even in this case a "different" version of the phone?
(I've skipped over this thread real fast http://forum.xda-developers.com/showthread.php?t=728266 which says it is possible for phones of the same model)
~If it is possible how should it be done?
~And well if the first question isn't possible, is there a way to read out out the created back-up files which TWRP created and manually restore them(preferable the data partition)
I hope you guys can help me out
Kind regards
Yes, you can do it. Just make sure you're not restoring the efs partition or you'll have another brick on your hands.
Sent from my Nexus 5 using XDA Free mobile app
Also don't use toolkits next time. Please use the manual methods which are better, safer and teach you the basis you need to recover.
All guides and info threads can be found in general > sticky roll-up thread
Sent from my Nexus 5 using Tapatalk
When you run into issues, as many do after nandroid restoring from one device to another... Wiping and Flashing stock with fastboot is the Fix.
Thought I'd cover that up front. ?
jd1639 said:
Yes, you can do it. Just make sure you're not restoring the efs partition or you'll have another brick on your hands.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
rootSU said:
Also don't use toolkits next time. Please use the manual methods which are better, safer and teach you the basis you need to recover.
All guides and info threads can be found in general > sticky roll-up thread
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Hey guys sorry I didn't answer immediately, but after I saw the posts I immediately ordered a new Nexus 5 (32GB this time). I got it delivered today and like you said I've done the unlocking, custom recovery and rooting manually this time instead of using a toolkit. Which was to be honest way easier than I thought but also way faster than using a toolkit.
But now I've kinda run into a other 'problem'
When I restore my previous made backup (the one from the bricked phone) I first of all only get the options to restore the 'system' partition and the 'data' partition (which is totally fine cause those are the only ones I actually need).
But when I restore the system partition a lot of apps crash on default(It is basically bricked then), and even when I just restore the data partition the same thing happens. (To be completely fair this problem might come from the fact that I used the MD5 verification option when I made the backup but I can't really remember that. but some of my backup files end with the .MD5 extension) Saying this I also used the restore option with check MD5 verification, but needless to say I get the message that they verifications don't match.
So here are a few questions again.
~Like I said before I only really care about the 'data' partition, Is there an option that I still can use TWRP to restore it properly?
~If the above is not possible is there a manual way to read out the made backup file using a program like 'Ext2Explore'(This crashes though when I open the file)
Or did I just completely screw up by checking the MD5 verification?
Once again kind regards
p.s. If the problem isn't clear tell me and and I'll try to explain it in a different way
You missed quote from post #4. ?
I believe that with a new device.... It should be a clean start. And I read post after post in different device sections of issues from restoring from other devices.
And so I never recommend it. It can, possibly, bring lots of issues.
But to each their own.
Good luck. ?
KJ said:
You missed quote from post #4. ?
I believe that with a new device.... It should be a clean start. And I read post after post in different device sections of issues from restoring from other devices.
And so I never recommend it. It can, possibly, bring lots of issues.
But to each their own.
Good luck. ?
Click to expand...
Click to collapse
Ohh right, sorry I completely read over your post my bad. But then again If I have to wipe the device wouldn't that totally remove the point of restoring the data partition ? or is the wipe command just for the system partition?
sambo940 said:
Ohh right, sorry I completely read over your post my bad. But then again If I have to wipe the device wouldn't that totally remove the point of restoring the data partition ? or is the wipe command just for the system partition?
Click to expand...
Click to collapse
What I'm getting at, is don't restore the data partition. You can try, but I often read of lots of issues doing it.
Yes, I implied wipe the device clean. Flash stock. Start fresh.
Now if you had a titanium backup of user apps on your pc... I'd say you'd have a much easier time restoring that to the new phone.
Just my 2 cents of course.
KJ said:
What I'm getting at, is don't restore the data partition. You can try, but I often read of lots of issues doing it.
Yes, I implied wipe the device clean. Flash stock. Start fresh.
Now if you had a titanium backup of user apps on your pc... I'd say you'd have a much easier time restoring that to the new phone.
Just my 2 cents of course.
Click to expand...
Click to collapse
I made a clean start yes. Unfortunately I don't have a titanium backup and I get that storing the data partition to a other device isn't a good idea. But well I never had the intention of making a back up and restoring it to another device but unfortunately my other phone got completely bricked. And yes in hindsight I should have made backups in multiple ways.
But like I said I don't really care about the system(including the apps and app settings) it is literally all about the actual data (pictures and stuff), that is also the reason why I asked if there is a way to manually read/open the back-up files.
sambo940 said:
I made a clean start yes. Unfortunately I don't have a titanium backup and I get that storing the data partition to a other device isn't a good idea. But well I never had the intention of making a back up and restoring it to another device but unfortunately my other phone got completely bricked. And yes in hindsight I should have made backups in multiple ways.
But like I said I don't really care about the system(including the apps and app settings) it is literally all about the actual data (pictures and stuff), that is also the reason why I asked if there is a way to manually read/open the back-up files.
Click to expand...
Click to collapse
The pictures are gone. A nandroid doesn't back those up or anything on the internal sdcard
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
The pictures are gone. A nandroid doesn't back those up or anything on the internal sdcard
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Well that certainly is a bummer, and also very misleading from the nexus toolkit. From now on I shall back-up my phone more properly and well stop using those darn toolkits,
Thank you for your time.
sambo940 said:
Well that certainly is a bummer, and also very misleading from the nexus toolkit. From now on I shall back-up my phone more properly and well stop using those darn toolkits,
Thank you for your time.
Click to expand...
Click to collapse
Did you make an adb backup in the tool kit? That would have your pics. But a flashable nandroid you flash in recovery would not.
Sent from my Nexus 5 using XDA Free mobile app
sambo940 said:
I made a clean start yes. Unfortunately I don't have a titanium backup and I get that storing the data partition to a other device isn't a good idea. But well I never had the intention of making a back up and restoring it to another device but unfortunately my other phone got completely bricked. And yes in hindsight I should have made backups in multiple ways.
But like I said I don't really care about the system(including the apps and app settings) it is literally all about the actual data (pictures and stuff), that is also the reason why I asked if there is a way to manually read/open the back-up files.
Click to expand...
Click to collapse
Would Nandroid Manager be what you're looking for? EDIT: as above, it won't find and restore any of your pictures/music, as a nandroid backup does not include any of these. There is a chance you find and restore your apps and settings if you so wish. I've used that app before.
Incidentally, I successfully transferred all of my data and ROM from one Nexus 5 to another (had to RMA)
The process I used is:
- Unlock bootloader, install custom recovery on new N5
- Nandroid backup on old N5
- Copy whole /sdcard partition from old to new N5. Basically, all files and folders on the 'root' of the drive when connected to PC. This included all photos, music and the nandroid backup itself.
- Restore nandroid backup on new N5 (only /system, /data and boot.img / kernel), as if you were restoring any nandroid backup really. Though do not restore efs partition as advised above (it wasn't backed up, but worth mentioning again anyway).
Took a while, but the ROM and settings were carried over successfully.
jd1639 said:
Did you make an adb backup in the tool kit? That would have your pics. But a flashable nandroid you flash in recovery would not.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Nope, I did not. And the ignorant person that I am just assumed that the nandroid backup would back up everything since the toolkit says "Make full Backups"
So well I guess I just have to accept the fact that I lost those things
eddiehk6 said:
Would Nandroid Manager be what you're looking for? EDIT: as above, it won't find and restore any of your pictures/music, as a nandroid backup does not include any of these. There is a chance you find and restore your apps and settings if you so wish. I've used that app before.
Incidentally, I successfully transferred all of my data and ROM from one Nexus 5 to another (had to RMA)
The process I used is:
- Unlock bootloader, install custom recovery on new N5
- Nandroid backup on old N5
- Copy whole /sdcard partition from old to new N5. Basically, all files and folders on the 'root' of the drive when connected to PC. This included all photos, music and the nandroid backup itself.
- Restore nandroid backup on new N5 (only /system, /data and boot.img / kernel), as if you were restoring any nandroid backup really. Though do not restore efs partition as advised above (it wasn't backed up, but worth mentioning again anyway).
Took a while, but the ROM and settings were carried over successfully.
Click to expand...
Click to collapse
Not exactly what I was looking but I'll keep it in the back of my head in case something similar might happen in the future(lets hope not) Thanks.
Install Foldersync and set your sdcard to sync to a computer wirelessly
Sent from my Nexus 5 using Tapatalk
eddiehk6 said:
Would Nandroid Manager be what you're looking for? EDIT: as above, it won't find and restore any of your pictures/music, as a nandroid backup does not include any of these. There is a chance you find and restore your apps and settings if you so wish. I've used that app before.
Incidentally, I successfully transferred all of my data and ROM from one Nexus 5 to another (had to RMA)
The process I used is:
- Unlock bootloader, install custom recovery on new N5
- Nandroid backup on old N5
- Copy whole /sdcard partition from old to new N5. Basically, all files and folders on the 'root' of the drive when connected to PC. This included all photos, music and the nandroid backup itself.
- Restore nandroid backup on new N5 (only /system, /data and boot.img / kernel), as if you were restoring any nandroid backup really. Though do not restore efs partition as advised above (it wasn't backed up, but worth mentioning again anyway).
Took a while, but the ROM and settings were carried over successfully.
Click to expand...
Click to collapse
I am assuming that you used a tool like Android File Transfer.
So what I'm trying to do is the same thing, backup my entire old N5 32GB as I had also requested an RMA of the device. Is it accurate in stating that you want me to copy every folder that shows up on the AFT window (Note: I am using a MAC) and copy that onto a folder on my computer. Then copy over everything on the new device (bootloader unlocked, rooted, same TWRP version installed) and restore via the Nandroid backup from my old phone (which was also transferred as indicated above).
dcxgod said:
I am assuming that you used a tool like Android File Transfer.
So what I'm trying to do is the same thing, backup my entire old N5 32GB as I had also requested an RMA of the device. Is it accurate in stating that you want me to copy every folder that shows up on the AFT window (Note: I am using a MAC) and copy that onto a folder on my computer. Then copy over everything on the new device (bootloader unlocked, rooted, same TWRP version installed) and restore via the Nandroid backup from my old phone (which was also transferred as indicated above).
Click to expand...
Click to collapse
I didn't use AFT, just plugged straight into PC, sorry no experience with Mac
Basically both phones were connected, and I copied the whole "/sdcard" straight from one phone to another, without making an initial copy to the PC
You want to replicate the same file structure
Hey guys, I'm rather new to the world of customising Android devices. I just have SO MANY QUESTIONS right now. And I'm sure I'm not the only one, which is why I created this thread to help myself and other people.
Basically, I'll be asking a bunch of questions related to the topic, and this can help other people who are new to all this too.
So, I've got a rooted device. It's on lollipop 5.0, has an unlocked bootloader, TWRP recovery, and Xposed framework.
A few questions to start off with:
1) Can I flash multiple .zip/.img files one after another? Or do I need to always wipe my phone's cache after each flash?
2) Say I wanna update TWRP recovery. Do I have do something before flashing it? CAN I flash a newer version over the previous one?
3) Same question as 2) but for Xposed framework instead.
4) I have Xposed framework installed with some modules running on my phone. Should I disable these modules before updating my Xposed?
5) The latest version of Xposed is v86 as given here: http://forum.xda-developers.com/showthread.php?t=3034811
Can v86 work for lollipop?
6) Similarly, can one download any TWRP version and flash it for their device? Or do each build have a different, specific version of TWRP?
7) Are the latest recovery mods and Xposed frameworks always guaranteed to be stable? Or is it safer to stay on the older ones? Which ones would you recommend?
8) Now, the custom ROMS. What are the necessary things to do before flashing one of these?
9) After flashing a custom ROM, can you flash another on top of it? Or do you have to restore back to your original stock ROM?
10) Does flashing and switching between custom ROMs cause any damage to the phone? Or is there any such potential?
11) Since backing up is a must, I'll ask some about that too. Which would you suggest to be the best backing up method?
12) Does creating a NANDroid backup or a backup from within custom recovery(TWRP in my case) equal to creating a backup of stock ROM?
13) Do I need to copy that backup into PC(to restore later), or will it be safe in my phone's memory after flashing a custom ROM?
I guess that's about it for now. Everyone, please answer if you have done these before. And of course, add your own questions too. This can save a lot of time for a lot of people. I could add more questions in if people request it.
**Answer mentioning the question number for simplicity of searching.
Answers!
1) Can I flash multiple .zip/.img files one after another? Or do I need to always wipe my phone's cache after each flash?
Click to expand...
Click to collapse
You can, but it is more recommended to wipe cache and dalvik cache with each flash.
2) Say I wanna update TWRP recovery. Do I have do something before flashing it? CAN I flash a newer version over the previous one?
Click to expand...
Click to collapse
You'll have to wipe dalvik cache and cache and just flash it normally. It might be stuck at 90% but a force reboot fixes it. It is because you are already in recovery. If it is stuck, leave it for 15 mins and come back. This is just to ensure that it really is stuck.
3) Same question as 2) but for Xposed framework instead.
Click to expand...
Click to collapse
Yep, works, except you wont be stuck.
4) I have Xposed framework installed with some modules running on my phone. Should I disable these modules before updating my Xposed?
Click to expand...
Click to collapse
No need
5) The latest version of Xposed is v86 as given here: http://forum.xda-developers.com/showthread.php?t=3034811
Can v86 work for lollipop?
Click to expand...
Click to collapse
Yup, just flash it via recovery
6) Similarly, can one download any TWRP version and flash it for their device? Or do each build have a different, specific version of TWRP?
Click to expand...
Click to collapse
Each build is different for each device, so for example, I can't flash a TWRP for s7 edge on my s4.
7) Are the latest recovery mods and Xposed frameworks always guaranteed to be stable? Or is it safer to stay on the older ones? Which ones would you recommend?
Click to expand...
Click to collapse
In example, xposed and supersu framework and binary lets you choose if you want a stable file or a test one for developers. TWRP and other stuff have (what I know) different versions and as stated, these versions behave different on different device. During testing with my S4, I found that TWRP 2.8.7.0 is the most stable build for my device.
8) Now, the custom ROMS. What are the necessary things to do before flashing one of these?
Click to expand...
Click to collapse
Make a nandroid backup of your whole device and back it up on you computer. Then wipe everything except your external sdcard and either store it on an sdcard or "adb sideload" it.
9) After flashing a custom ROM, can you flash another on top of it? Or do you have to restore back to your original stock ROM?
Click to expand...
Click to collapse
Not on top of it, you'll have to do as the answer to question 8, make a backup, wipe everything and then flash. No need to go back to stock ROM and then flash it
10) Does flashing and switching between custom ROMs cause any damage to the phone? Or is there any such potential?
Click to expand...
Click to collapse
There is always the risk of bricking but as far as software, it is always revertable. As long as you have a backup of course.
11) Since backing up is a must, I'll ask some about that too. Which would you suggest to be the best backing up method?
Click to expand...
Click to collapse
Nandroid backup is the best one.
12) Does creating a NANDroid backup or a backup from within custom recovery(TWRP in my case) equal to creating a backup of stock ROM?
Click to expand...
Click to collapse
It creates a backup of your current state, lets say, you are in Cyanogenmod 13, making a Nandroid backup will backup everything on cyanogenmod so that if you flash another ROM and still want to go back, you'll have everything restored, including app data and apps.
13) Do I need to copy that backup into PC(to restore later), or will it be safe in my phone's memory after flashing a custom ROM?
Click to expand...
Click to collapse
It will take up a lot of space on your device (since it is a backup of your whole device) so it is recommended to copy it to your computer and remove it from the phone. But, as always, make sure you copy the whole "BACKUPS" folder because the folder inside that folder has your device ID and it is required by TWRP to have the folder the exact ID of your phone to prevent anything bad from happening (bricks).
Hope, I answered all the questions as you wanted and if you have a new question, post it here and I'll reply as soon as possible
Hey, thanks a lot for answering. It helps a lot.
A few other questions I have:
14) So if I were to get CM13, and then create a backup of it, and then get another rom, say ASOP, create a backup of that too, and then switch to yet another rom, say Resurrection Remix, create a backup of that too.
Now, is it possible for me to be able to SWITCH between multiple roms, with ALL my data saved individually on each rom perfectly the way I wanted?(of course, wipe cache and data before restoring the backup)
If so, then I could just keep Nandroids of my favorite roms, can keep switching between them, never having to flash and start from scratch ever again!
Sent from my ASUS_T00J using XDA-Developers mobile app
15) Since I don't have otg cable, nor an sd card reader, I'm gonna have to keep the nandroid on my sd. Which means a lot of space is needed.
Can this workaround be possible:
- I use TWRP to backup only system and boot data. I save this on sd card.
- I use Titanium backup to save only user app and data. I save this on PC.
So now, when my device crashes while flashing something, I can restore backup from TWRP(do I clear cache and data before this as well?), and once my system rom is back, I can copy titanium backup via USB and restore it.
Sent from my ASUS_T00J using XDA-Developers mobile app
16) Suppose I flashed CM13, and it's really buggy. Can I switch back to the previous rom whose nandroid I had just by restoring it? Is it really that simple?
Sent from my ASUS_T00J using XDA-Developers mobile app
ShinraTensei04 said:
Hey, thanks a lot for answering. It helps a lot.
A few other questions I have:
14) So if I were to get CM13, and then create a backup of it, and then get another rom, say ASOP, create a backup of that too, and then switch to yet another rom, say Resurrection Remix, create a backup of that too.
Now, is it possible for me to be able to SWITCH between multiple roms, with ALL my data saved individually on each rom perfectly the way I wanted?(of course, wipe cache and data before restoring the backup)
If so, then I could just keep Nandroids of my favorite roms, can keep switching between them, never having to flash and start from scratch ever again!
Sent from my ASUS_T00J using XDA-Developers mobile app
Click to expand...
Click to collapse
14) You can, but you would need tons of space.
Sent using a ks01lte (gt-i9506) running cm 13
---------- Post added at 05:59 AM ---------- Previous post was at 05:56 AM ----------
ShinraTensei04 said:
15) Since I don't have otg cable, nor an sd card reader, I'm gonna have to keep the nandroid on my sd. Which means a lot of space is needed.
Can this workaround be possible:
- I use TWRP to backup only system and boot data. I save this on sd card.
- I use Titanium backup to save only user app and data. I save this on PC.
So now, when my device crashes while flashing something, I can restore backup from TWRP(do I clear cache and data before this as well?), and once my system rom is back, I can copy titanium backup via USB and restore it.
Sent from my ASUS_T00J using XDA-Developers mobile app
Click to expand...
Click to collapse
You do not have to have an sdcard reader to view your sdcard on your PC. You know how when you make a backup it is stored in /sdcard/TWRP/BACKUPS/CERIALNM/nameofbackup? Well, connect your phone to your pc and move the "backups" folder, then, when you need to restore it, add it to the twrp folder and restore it.
Sent using a ks01lte (gt-i9506) running cm 13
---------- Post added at 06:01 AM ---------- Previous post was at 05:59 AM ----------
ShinraTensei04 said:
15) Since I don't have otg cable, nor an sd card reader, I'm gonna have to keep the nandroid on my sd. Which means a lot of space is needed.
Can this workaround be possible:
- I use TWRP to backup only system and boot data. I save this on sd card.
- I use Titanium backup to save only user app and data. I save this on PC.
So now, when my device crashes while flashing something, I can restore backup from TWRP(do I clear cache and data before this as well?), and once my system rom is back, I can copy titanium backup via USB and restore it.
Sent from my ASUS_T00J using XDA-Developers mobile app
Click to expand...
Click to collapse
Also, on the titanium backup part, not a bad idea... You can then copy the data and system or boot to your pc and bam.
Sent using a ks01lte (gt-i9506) running cm 13
What I meant was: Let's say I bricked my phone. Now, according to you, I place backup on pc. Okay. But now, how do I place this backup onto the sd on my phone when my pc can't even detect the phone(cuz it's dead yo). Doesn't this impose on me to keep the backup in sd(as I don't have reader or otg).
About the titanium, so you're saying I can do that? Backup only user apps+data and restore after restoring only system+boot.
Another question:
16) Can the backup of user apps+data made on, say, 'X' rom, be restored on 'Y' rom via titanium, on condition they are same Android version(suppose 5.0), without ANY chance of incompatibility. More importantly, can it have any chances of leading to a brick/bootloop.
* I read somewhere that if you backed up system apps of 'X' rom, then changed to 'Y' rom, and restored the system apps of 'X' rom onto 'Y' rom, it bricks the phone.(which is why I ask this question)
17) "Backing up 'system' in TWRP is completely different from backing up 'system' on titanium. This is because TWRP backs up entire system with system apps, while titanium only backs up the apps." This is true, right?
Sent from my ASUS_T00J using XDA-Developers mobile app
ShinraTensei04 said:
What I meant was: Let's say I bricked my phone. Now, according to you, I place backup on pc. Okay. But now, how do I place this backup onto the sd on my phone when my pc can't even detect the phone(cuz it's dead yo). Doesn't this impose on me to keep the backup in sd(as I don't have reader or otg).
About the titanium, so you're saying I can do that? Backup only user apps+data and restore after restoring only system+boot.
Another question:
16) Can the backup of user apps+data made on, say, 'X' rom, be restored on 'Y' rom via titanium, on condition they are same Android version(suppose 5.0), without ANY chance of incompatibility. More importantly, can it have any chances of leading to a brick/bootloop.
* I read somewhere that if you backed up system apps of 'X' rom, then changed to 'Y' rom, and restored the system apps of 'X' rom onto 'Y' rom, it bricks the phone.(which is why I ask this question)
17) "Backing up 'system' in TWRP is completely different from backing up 'system' on titanium. This is because TWRP backs up entire system with system apps, while titanium only backs up the apps." This is true, right?
Sent from my ASUS_T00J using XDA-Developers mobile app
Click to expand...
Click to collapse
You adb sideload a functioning ROM and once you boot you copy the backup you can flash it via twrp. As for the second question, I have not tested it but it sounds possible.
16) You should not be in a bootloop if you backup like that, the fact that it is even the same android version is making it more likely to work and what I know, you can even switch the backup via phones. I don't use titanium because I always do nandroid backups.
17) Yup, that's true, twrp sees "system as the partition system while titanium sees it as the whole phones software, hence why it is called " system".
Thanks for asking these question and hopefully some day, you can teach others.
RAZERZDAHACKER said:
You adb sideload a functioning ROM and once you boot you copy the backup you can flash it via twrp. As for the second question, I have not tested it but it sounds possible.
16) You should not be in a bootloop if you backup like that, the fact that it is even the same android version is making it more likely to work and what I know, you can even switch the backup via phones. I don't use titanium because I always do nandroid backups.
17) Yup, that's true, twrp sees "system as the partition system while titanium sees it as the whole phones software, hence why it is called " system".
Thanks for asking these question and hopefully some day, you can teach others.
Click to expand...
Click to collapse
Hm... so whenever I brick my phone, I MUST adb sideload to a working rom first, and only then restore the backup I made? Even if I already have a backup saved onto the sd card of my bricked phone? Can I not restore that via TWRP instead? I ask this because if I were to adb sideload first, I'd lose root, unlocked bootloader, and yes, TWRP. So, I'd have to get ALL that done again, and only then restore my backup.
18) Does restoring a backup I made(when I had root access, unlocked BL, custom recovery, xposed) RETAIN all that? Meaning after I restore to that backup, I will still have all that.
Thanks for answering, I'm learning quite a bit. And yeah, I'll make sure to help others with this information too.
ShinraTensei04 said:
Hm... so whenever I brick my phone, I MUST adb sideload to a working rom first, and only then restore the backup I made? Even if I already have a backup saved onto the sd card of my bricked phone? Can I not restore that via TWRP instead? I ask this because if I were to adb sideload first, I'd lose root, unlocked bootloader, and yes, TWRP. So, I'd have to get ALL that done again, and only then restore my backup.
Click to expand...
Click to collapse
You won't lose TWRP or unlocked bootloader, but I will try today by making backup of "cache" and flash it via my sdcard as soon as possible.
18) Does restoring a backup I made(when I had root access, unlocked BL, custom recovery, xposed) RETAIN all that? Meaning after I restore to that backup, I will still have all that.
Click to expand...
Click to collapse
Yup, it makes a backup of every little part of the system (if you include cache and dalvik, I don't, but some do).
Thanks for answering, I'm learning quite a bit. And yeah, I'll make sure to help others with this information too.
Click to expand...
Click to collapse
Okay, made a backup of "cache and the flashing went fine, my hypothesis is that you have to make the backup on the sdcard and not on the phone and move it to the sdcard.
RAZERZDAHACKER said:
You won't lose TWRP or unlocked bootloader, but I will try today by making backup of "cache" and flash it via my sdcard as soon as possible.
Click to expand...
Click to collapse
Actually, when you adb sideload, you need to flash stock fastboot and recovery .img files(at least for my phone), and the bootloader does in fact get locked again, along with losing root. I know cuz I already have done adb sideloading before. So, doesn't that make flashing backup via sd card and TWRP without sideload the only thing I can do? I'm just trying to keep a backup without losing root, unlocked BL, TWRP, even if I gotta give up some space... Just wanna make sure it's safe to do it like that.
RAZERZDAHACKER said:
Yup, it makes a backup of every little part of the system (if you include cache and dalvik, I don't, but some do).
Click to expand...
Click to collapse
I only have "System(1125 mb)", "Data(3480 mb)", and "Cache(0 mb)" listed in TWRP. My cache is 0 mb.... nothing to backup on there?
19) Do I have to unlink my linked apps before creating a Nandroid, or will creating one while linked allow me to retain the link even after wiping data and then restoring the Nandroid?
ShinraTensei04 said:
Actually, when you adb sideload, you need to flash stock fastboot and recovery .img files(at least for my phone), and the bootloader does in fact get locked again, along with losing root. I know cuz I already have done adb sideloading before. So, doesn't that make flashing backup via sd card and TWRP without sideload the only thing I can do? I'm just trying to keep a backup without losing root, unlocked BL, TWRP, even if I gotta give up some space... Just wanna make sure it's safe to do it like that.
Click to expand...
Click to collapse
You wont lose anything during a complete nandroid backup, and, apparently, some devices loose stuff during adb sideload.
I only have "System(1125 mb)", "Data(3480 mb)", and "Cache(0 mb)" listed in TWRP. My cache is 0 mb.... nothing to backup on there?
Click to expand...
Click to collapse
Nothing....... Yet.
19) Do I have to unlink my linked apps before creating a Nandroid, or will creating one while linked allow me to retain the link even after wiping data and then restoring the Nandroid?
Click to expand...
Click to collapse
Unlink? What do you mean? (Not quoting Justin Bieber)
RAZERZDAHACKER said:
Unlink? What do you mean? (Not quoting Justin Bieber)
Click to expand...
Click to collapse
There's this thing you can do where you move your apps from internal storage to sd card COMPLETElY, thereby saving a lot of space on internal memory. It works because a 'link' is created between the app+data(now in sd) back to it's internal location counterpart(where it would have been otherwise). This way, the apps and system think your apps are in internal, but in fact are in sd(you can see that more internal is free by checking space used up via any file manager though).
In order to do this, a second partition on the sd card is to be made with an ext2/ext4 format, and use a linking app( like Apps2sd).
ShinraTensei04 said:
There's this thing you can do where you move your apps from internal storage to sd card COMPLETElY, thereby saving a lot of space on internal memory. It works because a 'link' is created between the app+data(now in sd) back to it's internal location counterpart(where it would have been otherwise). This way, the apps and system think your apps are in internal, but in fact are in sd(you can see that more internal is free by checking space used up via any file manager though).
In order to do this, a second partition on the sd card is to be made with an ext2/ext4 format, and use a linking app( like Apps2sd).
Click to expand...
Click to collapse
Yea I've used one of those, I first thought the app used the "MV" Unix command but yea you need a sec. Partition to do that on the sdcard, but you don't have to do that on your nandroid backup.
RAZERZDAHACKER said:
Yea I've used one of those, I first thought the app used the "MV" Unix command but yea you need a sec. Partition to do that on the sdcard, but you don't have to do that on your nandroid backup.
Click to expand...
Click to collapse
So can I backup linked apps with their links' data saved, so when I install the linking app again, they can be relinked automatically?
Sent from my ASUS_T00J using XDA-Developers mobile app
Thanks for those questions and answers. I posted this before but appearantly in the wrong place. It seems to be quite right here. Thanks to helping people!
Hi XDA experts
I am newly registered in the forum, but experienced in modding (more or less). But I am (for now) strictly a user, not developer.
So far I got along very well, with my beloved Galaxy S4 jfltexx. I got from stock to rooted stock, from there to cm, instantly back to stock, used it for a long time and am just now on cm13 nightly, which is truly awesome!
It is so awesome that I would really like to help other people out, even if they have no idea about this. Meaning I wish to modify other peoples phones for them. However, when it comes to other peoples property I can't really fight my way through technical terms I don't understand anymore, hoping that the outcome will be as I wished. I pretty much know what most of all these technical terms mean, but I don't always understand how they are related to each other. I know, explaining this will take a while, but I would REALLY appreciate it if someone would take the time...
1) The bootloader, can it be replaced? What would be the purpose of that? UNLOCKING does not mean REPLACING, does it??
What do custom ROMs typically consist of? An entire working system? Parts of a working system? Sometimes this sometimes that?
I'm asking the question because I got the impression that some custom ROMs require the user to have a certain (usually stock) ROM in order to flash it. For example, if I had a Galaxy S6 edge running 5.1.1, could I upgrade to noble ROM Marshmallow?
I also have the feeling that the ROM or system or whatever is somewhat seperate from the kernel. What is this relation? Do custom ROMs not always come with a compatible kernel? Is there only one kernel compatible to the rest of the system, or is there a chance to run a system with a kernel not particularly designed for it? How to get a 'wrong' kernel?
Where to get stock ROMs and who provides them? If I wanted to upgrade from Lollipop to Marshmallow, but am rooted and don't get OTA updates, what do I do? Assuming that Nandroids are bound to a single device (e.g. MY phone) who can provide a stock ROM that runs on my device and how does he get it?
Can I run pure Android on any phone, or is it (always?) necessary to adjust it? I understand that my hardware buttons of the S4 would probably not work on pure Android, but the rest?
Is there ANY phone SOLD with open bootloader and root? A phone that actually wants its users to play with the system?
Thanks guys
NoBullsh1t said:
Thanks for those questions and answers. I posted this before but appearantly in the wrong place. It seems to be quite right here. Thanks to helping people!
Click to expand...
Click to collapse
It happnes alot that people post in wrong section
Hi XDA experts
I am newly registered in the forum, but experienced in modding (more or less). But I am (for now) strictly a user, not developer.
So far I got along very well, with my beloved Galaxy S4 jfltexx. I got from stock to rooted stock, from there to cm, instantly back to stock, used it for a long time and am just now on cm13 nightly, which is truly awesome!
Click to expand...
Click to collapse
Yup, kinda same, excpet im ks01lte but I moved from stock to rooted stock (5.1.1) then cm13, then stock + xposed 4.4.2 then cm11 and now back to cm13 nightly
It is so awesome that I would really like to help other people out, even if they have no idea about this. Meaning I wish to modify other peoples phones for them. However, when it comes to other peoples property I can't really fight my way through technical terms I don't understand anymore, hoping that the outcome will be as I wished. I pretty much know what most of all these technical terms mean, but I don't always understand how they are related to each other. I know, explaining this will take a while, but I would REALLY appreciate it if someone would take the time...
Click to expand...
Click to collapse
1) The bootloader, can it be replaced? What would be the purpose of that? UNLOCKING does not mean REPLACING, does it??
Click to expand...
Click to collapse
The bootloader can be replace, however, if you fail here, there is no comming back (you'll need a complete board replacement because the bootloader acts as a BIOS), the purpose of replacing it is various reasons, change of splash screen during boot etc. Some bootloaders are locked to only be able to flash certain ROMs (OEMs do this to not allow people to tinker with their devices) but it is nearly always un-lockable (except for some devices, I own an Acer tablet that has a locked bootloader that cant be un-locked) and no, unlocking it does not mean changing it.
What do custom ROMs typically consist of? An entire working system? Parts of a working system? Sometimes this sometimes that?
Click to expand...
Click to collapse
Yea, sometimes this sometimes that, in example, ported marshamllow touchwiz ROMs rely on some files in the stock ROM so the "update" doesn't take up much space.
I'm asking the question because I got the impression that some custom ROMs require the user to have a certain (usually stock) ROM in order to flash it. For example, if I had a Galaxy S6 edge running 5.1.1, could I upgrade to noble ROM Marshmallow?
Click to expand...
Click to collapse
That is because of the bootloader (again lol), from my experience with the s4, before flashing cm13, I had to go to 5.1.1 because of the bootloader was changed during the OTA, so as stated before, it only allowed a certain type of ROMs to be flashed.
I also have the feeling that the ROM or system or whatever is somewhat seperate from the kernel. What is this relation? Do custom ROMs not always come with a compatible kernel? Is there only one kernel compatible to the rest of the system, or is there a chance to run a system with a kernel not particularly designed for it? How to get a 'wrong' kernel?
Click to expand...
Click to collapse
The kernel tells the system what to do, some kernels are specified for battery optimization, so the kernel tells the cpu to slow down and save juice, while some other kernels offer the ability to overclock the device (mostly used on older devices to make it faster, but it drains more juice and can result into app crashing), the kernel, is not separated from the system, in fact, you can't even compile a ROM without a kernel. There is not only one kernel for lets say cm, you can flash another kernel, just make sure it is compatible with your android version. To get a wrong kernel, flash one that isn't for your device or android version.
Where to get stock ROMs and who provides them? If I wanted to upgrade from Lollipop to Marshmallow, but am rooted and don't get OTA updates, what do I do? Assuming that Nandroids are bound to a single device (e.g. MY phone) who can provide a stock ROM that runs on my device and how does he get it?
Click to expand...
Click to collapse
Your OEM provides them, samsung has a website called sammobile and uploads all the stock ROMs there. If you want to upgrade, just flash it via recovery or in your case, odin (for samsung phones). To give your backup to someone else, the other person must have the exact same phones, in example, you (jfltexx) can't give it to me (ks01lte), I must have jfltexx and then (assuming you did the backup on twrp) I'd have to change the serial number to my device.
Can I run pure Android on any phone, or is it (always?) necessary to adjust it? I understand that my hardware buttons of the S4 would probably not work on pure Android, but the rest?
Click to expand...
Click to collapse
Your hardware buttons will work on pure android (aosp), I don't see why not, you said you are running cm13, that is altered pure android and it works fine, see pure android as cm withou all the features.
Is there ANY phone SOLD with open bootloader and root? A phone that actually wants its users to play with the system?
Thanks guys
Click to expand...
Click to collapse
There are a few devices like that, one plus was a company that wanted to do that, it came with root, unlocked bootloader and cyanogenmod running, they separated unfortunatly and evolved to using "oxygen os" and does nor provide a un-locked bootloader but provides a simple tool to root and unlock. I don't know any companies that have unlocket bootloaders because they don't want the average consumer to mess up their device and blame it on the OEM.
"Can I run pure Android on any phone, or is it (always?) necessary to adjust it? I understand that my hardware buttons of the S4 would probably not work on pure Android, but the rest?
Your hardware buttons will work on pure android (aosp), I don't see why not, you said you are running cm13, that is altered pure android and it works fine, see pure android as cm withou all the features."
I mean is there like a website from google where I can dowoad a non device specific aosp and flash that to my S4 to make it run? Wouldn't there be for example drivers missing? Isn't that what I have to be greateful to Cyanogenmod for, making up to date android compatible with older devices?
---------- Post added at 07:49 PM ---------- Previous post was at 07:42 PM ----------
So I can actually make a jfltexx Nandroid and install it on another jfltexx by easily changing the serial number???
NoBullsh1t said:
"Can I run pure Android on any phone, or is it (always?) necessary to adjust it? I understand that my hardware buttons of the S4 would probably not work on pure Android, but the rest?
Your hardware buttons will work on pure android (aosp), I don't see why not, you said you are running cm13, that is altered pure android and it works fine, see pure android as cm withou all the features."
I mean is there like a website from google where I can dowoad a non device specific aosp and flash that to my S4 to make it run? Wouldn't there be for example drivers missing? Isn't that what I have to be greateful to Cyanogenmod for, making up to date android compatible with older devices?
Click to expand...
Click to collapse
Yes, be greatful, it is free, open source and full of active devs and memebers. I'm still not sure what you mean, do you mean on-screen navigation bar? Because you can change that in cyanogenmod settings.
---------- Post added at 07:49 PM ---------- Previous post was at 07:42 PM ----------
So I can actually make a jfltexx Nandroid and install it on another jfltexx by easily changing the serial number???
Click to expand...
Click to collapse
Yea, you know how your backup is located in /sdcard/TWRP/BACKUPS/SERIALNO? The device you want to flash it to should make a backup of the tiniest partition (usually cache, it's 5mb) and youll get acces to the serial number, then you just swap it and delete the tiniest partition.
So I have the OP6 for a while now. Everytime a new version released I download the new official zip file and then flash it with twrp. (follow this post - https://forum.xda-developers.com/showpost.php?p=76596833&postcount=3)
So I did it for 9.0.4, I first took nandroid backup, flash the new firmware, flash twrp, reboot to recovery, flash magisk. And then when I tried to reboot the system I got a message "Shutting down..." when the android system tried to load so I was stuck at bootlooping.
I thought that maybe something in the installation went wrong, so I might just get it restored. I did the restore using the latest twrp (v9.91) and now the system is completly corrupt, the phone no longer able to load anyhing (no oneplus loading screen with the rolling dot) and I when it boot to twrp it no longer can decrypt the filesystem (doesn't ask for my password).
I don't know I could I meesed this up, I did the same step every new upgrade. Apperiate any insight to my situasion.
What do you think caused this? Can I decrypt the files on my phone somehow and restore them?
Thank you in advanced.
b217260 said:
So I have the OP6 for a while now. Everytime a new version released I download the new official zip file and then flash it with twrp. (follow this post - https://forum.xda-developers.com/showpost.php?p=76596833&postcount=3)
So I did it for 9.0.4, I first took nandroid backup, flash the new firmware, flash twrp, reboot to recovery, flash magisk. And then when I tried to reboot the system I got a message "Shutting down..." when the android system tried to load so I was stuck at bootlooping.
I thought that maybe something in the installation went wrong, so I might just get it restored. I did the restore using the latest twrp (v9.91) and now the system is completly corrupt, the phone no longer able to load anyhing (no oneplus loading screen with the rolling dot) and I when it boot to twrp it no longer can decrypt the filesystem (doesn't ask for my password).
I don't know I could I meesed this up, I did the same step every new upgrade. Apperiate any insight to my situasion.
What do you think caused this? Can I decrypt the files on my phone somehow and restore them?
Thank you in advanced.
Click to expand...
Click to collapse
Ok this is a giant pain in the backside but I have done this before and I know it works. Here is a step by step guide to restore.
1. https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 go here and download the fastboot rom for the rom YOU HAD ON THE PHONE WHEN YOU MADE THE NANDROID BACKUP. Step by step on how to install it is there.
2. Install the rom and boot up the phone. Don't bother signing in to google or downloading apps or any of that. Just get through all the menus.
3. Install TWRP. Bluspark TWRP is recommended.
4. Install Magisk, but make sure IT IS THE SAME VERSION OF MAGISK AS WAS INSTALLED IN THE NANDROID BACKUP
5. Reboot to system and make sure the phone still works, then reboot to TWRP
6. Restore Nandroid backup.
I know this is a giant hassle, but it works every time. I haven't found a better way to restore a backup since this whole A/B partitioning started.
Thank you for making the time writing this, it is relief to hear that you figure this out. Will try this first in the morning.
I did a bad mistake running the flash-all.bat thinking it will only flash the partitions of the system.
Well it is all gone now...Dam if only I wait until the morning I might not made this mistake.
tabletalker7 said:
Ok this is a giant pain in the backside but I have done this before and I know it works. Here is a step by step guide to restore.
1. https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 go here and download the fastboot rom for the rom YOU HAD ON THE PHONE WHEN YOU MADE THE NANDROID BACKUP. Step by step on how to install it is there.
2. Install the rom and boot up the phone. Don't bother signing in to google or downloading apps or any of that. Just get through all the menus.
3. Install TWRP. Bluspark TWRP is recommended.
4. Install Magisk, but make sure IT IS THE SAME VERSION OF MAGISK AS WAS INSTALLED IN THE NANDROID BACKUP
5. Reboot to system and make sure the phone still works, then reboot to TWRP
6. Restore Nandroid backup.
I know this is a giant hassle, but it works every time. I haven't found a better way to restore a backup since this whole A/B partitioning started.
Click to expand...
Click to collapse
This guide can also be used to restore from other roms;
b217260 said:
I did a bad mistake running the flash-all.bat thinking it will only flash the partitions of the system.
Well it is all gone now...Dam if only I wait until the morning I might not made this mistake.
Click to expand...
Click to collapse
What did you do?
---------- Post added at 02:14 PM ---------- Previous post was at 02:13 PM ----------
petran07 said:
This guide can also be used to restore from other roms;
Click to expand...
Click to collapse
I guess so. I never had to use a backup to restore on a custom ROM yet.
tabletalker7 said:
What did you do?
Click to expand...
Click to collapse
After extracting the stock zip flasher, there is file "flash-all.bat" on the root of the folder. (Guess I needed to use the "flash-all-partitions-fastboot.bat)
Thinking it will only flash the android system partitions I've run it and realize that my internal stoarge was formatted.
Really stupid mistake from my part, sorry for couldn't verify your guide.
Hoping that someone who read this in the future won't do my mistake.
b217260 said:
After extracting the stock zip flasher, there is file "flash-all.bat" on the root of the folder. (Guess I needed to use the "flash-all-partitions-fastboot.bat)
Thinking it will only flash the android system partitions I've run it and realize that my internal stoarge was formatted.
Really stupid mistake from my part, sorry for couldn't verify your guide.
Hoping that someone who read this in the future won't do my mistake.
Click to expand...
Click to collapse
It's my bad. I always store my backups on an SD card with my OTG card reader. I forget others don't think like I do sometimes
tabletalker7 said:
Ok this is a giant pain in the backside but I have done this before and I know it works. Here is a step by step guide to restore.
1. https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 go here and download the fastboot rom for the rom YOU HAD ON THE PHONE WHEN YOU MADE THE NANDROID BACKUP. Step by step on how to install it is there.
2. Install the rom and boot up the phone. Don't bother signing in to google or downloading apps or any of that. Just get through all the menus.
3. Install TWRP. Bluspark TWRP is recommended.
4. Install Magisk, but make sure IT IS THE SAME VERSION OF MAGISK AS WAS INSTALLED IN THE NANDROID BACKUP
5. Reboot to system and make sure the phone still works, then reboot to TWRP
6. Restore Nandroid backup.
I know this is a giant hassle, but it works every time. I haven't found a better way to restore a backup since this whole A/B partitioning started.
Click to expand...
Click to collapse
tabletalker7, can you please explain a little technical detail? If i follow your procedure, what is the difference from me just restoring boot, system and data from a Nandroid backup of a system that used to boot? What causes the restored system to no longer boot?
Because you seem to be suggesting a solution for the the problem I had. I normally do plenty of backups and play around with the system quite a lot, but Op6 burned me: I was unable to restore from a backup like I always did on other phones. I tried suggestions from other posters to no avail. So I set up a clean system from a fastboot rom and reinstalled everything from Titanium. I wonder, after I set pretty much identically, should I just risk and to once more try to restore from that Nandroid that was failing to restore (that only had system and data btw)? I'd greatly appreciate if you can enlighten.
b217260 said:
So I have the OP6 for a while now. Everytime a new version released I download the new official zip file and then flash it with twrp. (follow this post - https://forum.xda-developers.com/showpost.php?p=76596833&postcount=3)
So I did it for 9.0.4, I first took nandroid backup, flash the new firmware, flash twrp, reboot to recovery, flash magisk. And then when I tried to reboot the system I got a message "Shutting down..." when the android system tried to load so I was stuck at bootlooping.
I thought that maybe something in the installation went wrong, so I might just get it restored. I did the restore using the latest twrp (v9.91) and now the system is completly corrupt, the phone no longer able to load anyhing (no oneplus loading screen with the rolling dot) and I when it boot to twrp it no longer can decrypt the filesystem (doesn't ask for my password).
I don't know I could I meesed this up, I did the same step every new upgrade. Apperiate any insight to my situasion.
What do you think caused this? Can I decrypt the files on my phone somehow and restore them?
Thank you in advanced.
Click to expand...
Click to collapse
Had faced this many times. ...after trying diff options and failed Qualcome MSM method works perfectly.
Yep, You cant restore data i think as it being already formated as per knowd based on your steps above on diff posts
ahacker said:
tabletalker7, can you please explain a little technical detail? If i follow your procedure, what is the difference from me just restoring boot, system and data from a Nandroid backup of a system that used to boot? What causes the restored system to no longer boot?
Because you seem to be suggesting a solution for the the problem I had. I normally do plenty of backups and play around with the system quite a lot, but Op6 burned me: I was unable to restore from a backup like I always did on other phones. I tried suggestions from other posters to no avail. So I set up a clean system from a fastboot rom and reinstalled everything from Titanium. I wonder, after I set pretty much identically, should I just risk and to once more try to restore from that Nandroid that was failing to restore (that only had system and data btw)? I'd greatly appreciate if you can enlighten.
Click to expand...
Click to collapse
1. Changing Android security updates makes changes to phone encryption. It will make the data itself on the backup unreadable to the operating system. That is why people playing with many different custom ROMs had problems with data stored on their phones.
2. By using the fastboot rom you ensure that both partitions have the same operating system. A/B partitioning seems like a great idea on paper but it seems to be executed in the most horrible way possible.
tabletalker7 said:
1. Changing Android security updates makes changes to phone encryption. It will make the data itself on the backup unreadable to the operating system. That is why people playing with many different custom ROMs had problems with data stored on their phones.
2. By using the fastboot rom you ensure that both partitions have the same operating system. A/B partitioning seems like a great idea on paper but it seems to be executed in the most horrible way possible.
Click to expand...
Click to collapse
Thanks a lot. It is plausible and I remeber seeing folder names to which random hex strings were appended (I did not see file contents though). But after last restores I verified that the folder names in /data/data folder were looking allright. Twrp apparently could decrypt the data partition, but the system would still not boot. If I were to encypr the data partition I'd use the whole partition as one encrypted block and not bother doing it on file or folder basis, which is more error-prone. Another sourse of doubt is that I never played with OS version upgrades nor with installing other roms.
Can you also please answer the following? Do you think I can try to restore my boot+system to a different slot and then come back to my original slot if my playing there is unsuccesfull? Being scared that restoring a previous state can fail is a major problem.
ahacker said:
Thanks a lot. It is plausible and I remeber seeing folder names to which random hex strings were appended (I did not see file contents though). But after last restores I verified that the folder names in /data/data folder were looking allright. Twrp apparently could decrypt the data partition, but the system would still not boot. If I were to encypr the data partition I'd use the whole partition as one encrypted block and not bother doing it on file or folder basis, which is more error-prone. Another sourse of doubt is that I never played with OS version upgrades nor with installing other roms.
Can you also please answer the following? Do you think I can try to restore my boot+system to a different slot and then come back to my original slot if my playing there is unsuccesfull? Being scared that restoring a previous state can fail is a major problem.
Click to expand...
Click to collapse
I would not recommend doing that. While you may have different roms on different partitions you only have one data partition. That is asking for trouble
tabletalker7 said:
I would not recommend doing that. While you may have different roms on different partitions you only have one data partition. That is asking for trouble
Click to expand...
Click to collapse
I would have data backed up, sure.
What bothers me is that an essential property of a digital automaton is that if you start it from the same state it will continue the same. Nandroid used to capture all that mattered for identical runs. It no longer does, something is missing, such as some encryption keys for data partition, as you seem to suggest. This bothers me.
ahacker said:
I would have data backed up, sure.
What bothers me is that an essential property of a digital automaton is that if you start it from the same state it will continue the same. Nandroid used to capture all that mattered for identical runs. It no longer does, something is missing, such as some encryption keys for data partition, as you seem to suggest. This bothers me.
Click to expand...
Click to collapse
What bothers you here are things I call "security". If the nandroid backup has the encryption keys to decrypt it, then the data is not secure.
tabletalker7 said:
What bothers you here are things I call "security". If the nandroid backup has the encryption keys to decrypt it, then the data is not secure.
Click to expand...
Click to collapse
Nandroid backups should be encrypted when created with a user supplied key. Twrp allowed this since ages ago. Not allowing the user to restore a backup is not a right substitution for this.
ahacker said:
Nandroid backups should be encrypted when created with a user supplied key. Twrp allowed this since ages ago. Not allowing the user to restore a backup is not a right substitution for this.
Click to expand...
Click to collapse
TWRP didn't do this. Android didn't do this. Ya know, if this is anywhere near as horrible for you as you are making it sound, my advise for you would be to buy Apple products. Bottom line is a new feature was added to Android, and your backup does work.
tabletalker7 said:
TWRP didn't do this. Android didn't do this. Ya know, if this is anywhere near as horrible for you as you are making it sound, my advise for you would be to buy Apple products. Bottom line is a new feature was added to Android, and your backup does work.
Click to expand...
Click to collapse
-It is as horrible as not being able to restore a full backup. No more, no less.
-Twrp has an ability to encrypt your backups, with your experience you must know this.
-You are suggesting someone to switch to iphone only because they point out that the things are wrong or dont add up.
-It is quite a common knowlege that you get good security out of encryption if you make things explicit and clear. And not how you may think it is. Cause you don't seem to know where the keys are stored for the data partition. Obviousely, because the phone eventually decrypts your data, the keys must be stored somewhere or derived from you swipe pattern.
tabletalker7 said:
Ok this is a giant pain in the backside but I have done this before and I know it works. Here is a step by step guide to restore.
1. https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 go here and download the fastboot rom for the rom YOU HAD ON THE PHONE WHEN YOU MADE THE NANDROID BACKUP. Step by step on how to install it is there.
2. Install the rom and boot up the phone. Don't bother signing in to google or downloading apps or any of that. Just get through all the menus.
3. Install TWRP. Bluspark TWRP is recommended.
4. Install Magisk, but make sure IT IS THE SAME VERSION OF MAGISK AS WAS INSTALLED IN THE NANDROID BACKUP
5. Reboot to system and make sure the phone still works, then reboot to TWRP
6. Restore Nandroid backup.
I know this is a giant hassle, but it works every time. I haven't found a better way to restore a backup since this whole A/B partitioning started.
Click to expand...
Click to collapse
Following these instructions seems to be the only way of restoring a nandroid backup (at least for my Op6 bought on AliExpress from China). Important: step 1 wipes your sdcard, so the backup you want to restore must be on otg usb stick.
After spending many hours I managed to restore a backup at least once. Fortunately for me I have no plans of upgarding Android and will likely forever stick with the following set:
1) 5.1.11-OREO-OnePlus6Oxygen_22_OTA_015_all_1808102118_770880-FASTBOOT.zip (found here)
2) twrp-3.2.3-x_blu_spark_v9.85_op6.img + twrp-3.2.3-x_blu_spark_v9.85_op6.zip (found here)
3) Magisk-v18.1.zip (found here)
My plan is to fully debloat the phone and then I will keep everything unchanged for years, because nowadays updates are more about twisting your arms than giving you usefull features. I almost got to that state, but one little glitch forced me to roll back and the whole hell with the Nandoid backups on Op6 started.
PS: It's very interesting what is really going on with this A/B system. There must be a storage where the encryption keys are stored (if it is the encryption that does prevent the phone from restoring. Which I doubt because Twrp sees the files fine). There also probbaly stored what slot is used. That information does not get captured by the Nandroid backup.
(Btw, It seems that blu_spark Twrp is really NOT encrypting your backups with the passwod you supply. Official Twrp does. I have plenty of old encypted backups, from wich I could not extract any personal data (/data/data folder) but yesterday I could extract my private information from a backup done by blu_spark Twrp. This is serious iussue. I'll double check and will post if confirmed.)
Not confirmed, I was looking at unencrypoted file.