Develop Bugs

I think CWM screwed me

I should be able to flash a backup I made with CWM recovery in CWM recovery, correct? Or would I have to adb push it?
I moved to 4.2.1 but not a fan of it at this point and want to go back using a backup (4.1.2) I made with CWM, but it won't flash. So at this point I'm trying to save my photos, notes, texts, and my titanium backup of apps and do a complete wipe using wugs (unroot/relock then reroot/unlock). Or should I be able to get away with just doing a format on my sdcard/system/cache/data and data/media (options in CWM)? Since going to 4.2.1 I have also lost a significant amount of free space.
BTW I have tried TWRP before and went back because I didn't like the layout but damn if your recovery can't even handle its own backups what the hell is it good for? TWRP here I come again.

you know it moves everything to a folder called 0 on the internal memory, right...?

A lot of the following is probably overkill but what I'd do is...
1. Backup everything I wanted to keep when in Android 4.2.1 onto my PC (Nandroid backups, photos, music, etc.)
2. Flash the factory 4.1.2 image
3. Boot up to make sure it's working
4. Restore nandroid in CWM
Chances are there are easier ways of doing this but I'd be happy knowing that is 100% right then have the potential for it going wrong

derekwilkinson said:
you know it moves everything to a folder called 0 on the internal memory, right...?
Click to expand...
Click to collapse
Bud I have tried to flash it out of every folder I have access to in CWM Recovery
The folder's I have tried, after choosing install zip from sdcard:
sdcard/0/clockworkmod/backup/ - 4 backups in here but wont flash any of them - says no files found when I try to flash one
sdcard/clockworkmod/backup/ - can actually see 2 backups in here (ones I don't want, just wanted to see where they were placed in 4.2)
sdcard/legacy/ - no files found
But stupid me did just realize the CWM backups I have been creating aren't zips? So I need to figure out how to get to sdcard/clockworkmod/backup and place my backup folders here. So I will be able to see them when I choose Backup and Restore - Restore

CWM can't see the backups in the '0' folder, it stores them on /data/media (or is it /media/data??) so unless you have a file manager with root access you won't get them back

EddyOS said:
CWM can't see the backups in the '0' folder, it stores them on /data/media (or is it /media/data??) so unless you have a file manager with root access you won't get them back
Click to expand...
Click to collapse
My my my you are the man. It looks like it is data/media/clockworkmod/backups.
I am going to try to Restore my latest 4.1.2 nandroid tonight, after I had a chance to back every thing up, but I'm guessing it's going to keep the current file structure though.

The best way to upgrade to 4.2.1 from 4.1.2 is
1.Flash all factory images from fastboot apart from recovery,@ recovery step flash twrp 2.3.3.0 and you are all set to no '/0' bug,
2. Downgrade to 4.1.2 ? Flash factory images of 4.1.2 , just keep the recovery as twrp 2.3.3.0, at present it is the best possible recovery for maguro for handling the '/0' bug , it doesnot delete the layout file.
And restoring nandroids in between the versions can make every file very clumsy, take some time and flash stock images to get rid of that.

BaMaDuDe87 said:
My my my you are the man. It looks like it is data/media/clockworkmod/backups.
I am going to try to Restore my latest 4.1.2 nandroid tonight, after I had a chance to back every thing up, but I'm guessing it's going to keep the current file structure though.
Click to expand...
Click to collapse
After downgrading you will still have the /0/ folder with all data. So many apps wont recognize that the backups are there available to be restored. You can just point to the "new" backup location that now exists in the /0/ directory.
Example: Titanium backup will tell you there is no restore data unless you go into preference and point it to the right folder in /0/.
Example 2: Nova launcher will not see the backups. Manually move them via Root explorer or similar from the /0/data/ to the /data/
..and so on.

I guess I will be flashing the factory image then.
1. Backup everything I need/want (photos, notes, sms, and grab latest copy of titanium backup folder)
2. Format system/cache/sdcard just because
3. fastboot - factory image (4.1.2)
4. Phone should still be unlocked/rooted (on current bootloader/radios correct?)
5. fastboot - twrp
5. Restore everything else
Or use Wugs to take back to stock, then fastboot unlock, root, add CWM recovery might be the easier way at this point. Restore nandroid and everything else. Then add TWRP and remove CWM.
Sorry trying to talk this out with you guys and wrap my head around what I am in for. I know it's not hard, just frustrating to think I could possibly lose some things.

Better Recovery TWRP
BaMaDuDe87 said:
I guess I will be flashing the factory image then.
1. Backup everything I need/want (photos, notes, sms, and grab latest copy of titanium backup folder)
2. Format system/cache/sdcard just because
3. fastboot - factory image (4.1.2)
4. Phone should still be unlocked/rooted (on current bootloader/radios correct?)
5. fastboot - twrp
5. Restore everything else
Click to expand...
Click to collapse
Not to be bossy but the latest version of TWRP seems to do a better job handling user folder /0. Its also touchscreen and [email protected]$$ so there is really no comparison....:highfive:

Yea I tried it, thought I was more comfortable with CWM and this bit me in the ass, so TWRP it is when I get everything straightened out

[Q] Cloning the /data partition between devices

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi there!
What I'm trying to do is to "pre-configure" 70 devices (you read that right, 70) to have identical software/wallpaper/security settings/etc.
All devices are identical GT-N5100 with 4.1.2 (JZO54K.N5100XXBMD1) Android version.
The thing is, we absolutely _should_ keep the warranty and OTAs, therefore flipping the "System state" flag is definitely not what I want here.
I already tried backing up the device with adb backup, but this kind of backup doesn't contain all applications (specifically, those with android:allowBackup=false are not exported) and most of the settings (disabled apps' list or security settings)
So I came to a point that I _need_ to replace the whole /data partition. Which, obviously, requires custom recovery.
The main concern is, how to avoid triggering that "System state"?
Let's say I'll flash an alternate recovery image, backup/restore the system, then restore the original recovery, without booting into Android. Would that work, or since we change the flash counter, it will also cause the flag to change to "Modified"?
If it changes, could TriangleAway restore it back? Mind that I won't be able to wipe /data at this point, it defeats the purpose.
Again, I don't need root access on these tablets at all, I only need to have identical /data partition between them.
Any ideas?
Did anyone check that "recovery trick" I described?
Thanks in advance.

NeverGone\RU said:
Hi there!
What I'm trying to do is to "pre-configure" 70 devices (you read that right, 70) to have identical software/wallpaper/security settings/etc.
All devices are identical GT-N5100 with 4.1.2 (JZO54K.N5100XXBMD1) Android version.
The thing is, we absolutely _should_ keep the warranty and OTAs, therefore flipping the "System state" flag is definitely not what I want here.
I already tried backing up the device with adb backup, but this kind of backup doesn't contain all applications (specifically, those with android:allowBackup=false are not exported) and most of the settings (disabled apps' list or security settings)
So I came to a point that I _need_ to replace the whole /data partition. Which, obviously, requires custom recovery.
The main concern is, how to avoid triggering that "System state"?
Let's say I'll flash an alternate recovery image, backup/restore the system, then restore the original recovery, without booting into Android. Would that work, or since we change the flash counter, it will also cause the flag to change to "Modified"?
If it changes, could TriangleAway restore it back? Mind that I won't be able to wipe /data at this point, it defeats the purpose.
Again, I don't need root access on these tablets at all, I only need to have identical /data partition between them.
Any ideas?
Did anyone check that "recovery trick" I described?
Thanks in advance.
Click to expand...
Click to collapse
Gosh your spinning your wheels on something so simple.
Install saferoot.zip on all 70 devices
On the completed master clone device
create a admin google account for system apps
add the admin google account and make sure play store has the admin account selected.
pay for Ti Backup Pro and install
set google account back to original google account if available.
setup Ti Backup to save on SD, etc... note: Ti Backup has a lot of options in pro, you will have to make sure things are set to your needs.
For example, remove Google store from apps, so you have control over updates.
Remove admin google account
Do a full backup on SD
Remove Ti Backup Pro from backed up apps
Copy SD to spare 2GB (minimum) SD chip(s)
Insert SD chip in each device to be slave cloned
If each device has already gone through initial setup, do a factory reset.
When google account is needed use the admin account for syncing the Ti backup Pro
Start Ti Backup Pro and do not change system ID by ignoring.
Set Ti Backup pro to use the SD card and do a restore missing apps + system data.
When prompted after starting... select XML.
Be sure to deselect the check box for ignore system...
Reboot and make sure everything looks good, if not you may need to restore again using Snapshot.
remove Ti Backup, and uninstall root within SuperSu as a wipe for reinstall.
Reboot again and you are done.
All wallpaper, Icons and folders, along with app settings will all be the same.
This is a 90% accurate way to do it, as I have no idea what apps you are using, custom or paid. You will need to fine tune what options you may need to add in the procedures given.

gooberdude said:
Gosh your spinning your wheels on something so simple.
Install saferoot.zip on all 70 devices
On the completed master clone device
create a admin google account for system apps
add the admin google account and make sure play store has the admin account selected.
pay for Ti Backup Pro and install
set google account back to original google account if available.
setup Ti Backup to save on SD, etc... note: Ti Backup has a lot of options in pro, you will have to make sure things are set to your needs.
For example, remove Google store from apps, so you have control over updates.
Remove admin google account
Do a full backup on SD
Remove Ti Backup Pro from backed up apps
Copy SD to spare 2GB (minimum) SD chip(s)
Insert SD chip in each device to be slave cloned
If each device has already gone through initial setup, do a factory reset.
When google account is needed use the admin account for syncing the Ti backup Pro
Start Ti Backup Pro and do not change system ID by ignoring.
Set Ti Backup pro to use the SD card and do a restore missing apps + system data.
When prompted after starting... select XML.
Be sure to deselect the check box for ignore system...
Reboot and make sure everything looks good, if not you may need to restore again using Snapshot.
remove Ti Backup, and uninstall root within SuperSu as a wipe for reinstall.
Reboot again and you are done.
All wallpaper, Icons and folders, along with app settings will all be the same.
This is a 90% accurate way to do it, as I have no idea what apps you are using, custom or paid. You will need to fine tune what options you may need to add in the procedures given.
Click to expand...
Click to collapse
I would do exactly this, but I need to keep devices "stock" for warranty purposes — I won't see any of them after sending them to customer. Hence, having root = "System state: modified" = no warranty. Yea I can unroot afterwards, but it might also fail and keep the "System modified" flag in place. Risky.
Thanks anyway, let's see how it goes.

NeverGone\RU said:
I would do exactly this, but I need to keep devices "stock" for warranty purposes — I won't see any of them after sending them to customer. Hence, having root = "System state: modified" = no warranty. Yea I can unroot afterwards, but it might also fail and keep the "System modified" flag in place. Risky.
Thanks anyway, let's see how it goes.
Click to expand...
Click to collapse
I don't have any system state modified on my tablet. Saferoot does not flash. And will allow OTA and Kies to update without issues. You should at least look up the thread for saferoot and see its function. It installs the root not flashes it. The flash counter is what you are worried about. Though triangle away will reset the counter, and once cleared can be removed, if flashing a root. What keeps the counter coming back is the use of flashed custom ROMs.
I use to follow the popular threads on flashing and found that saferoot is exactly what it says, and I will not do any other rooting without it. That is how good it is.

Changed phones APN settings, can't text/call

So I was in the country out of service trying to connect to a network. Under mobile network settings I saw APN settings which I never saw before and decided to mess with (yes I know, awful idea). So now that I'm back in a service area, I have a data connection but can't text or call. And of course, APN settings is gone from my mobile network settings and shows varoous CDMA settings like before, my ROM is Dirty Unicorns 4.4.4.
If anyone has any info on how I can fox my apn settings so I can text and call again that'd be great! Thanks!

emfajardo2 said:
So I was in the country out of service trying to connect to a network. Under mobile network settings I saw APN settings which I never saw before and decided to mess with (yes I know, awful idea). So now that I'm back in a service area, I have a data connection but can't text or call. And of course, APN settings is gone from my mobile network settings and shows varoous CDMA settings like before, my ROM is Dirty Unicorns 4.4.4.
If anyone has any info on how I can fox my apn settings so I can text and call again that'd be great! Thanks!
Click to expand...
Click to collapse
This app is basically a shortcut to apn settings. You can change any settings you need, and even a reset to default that might help you.
https://play.google.com/store/apps/details?id=it.appando.app.changeApn
The weird thing is, APn settings should only be for data, calls and texts should still work. You can also reflash the ROM zip and wipe dalvik cache and cache from recovery, that would reset your system partition but keep all the data settings and personalized stuff.

dopy25 said:
This app is basically a shortcut to apn settings. You can change any settings you need, and even a reset to default that might help you.
https://play.google.com/store/apps/details?id=it.appando.app.changeApn
The weird thing is, APn settings should only be for data, calls and texts should still work. You can also reflash the ROM zip and wipe dalvik cache and cache from recovery, that would reset your system partition but keep all the data settings and personalized stuff.
Click to expand...
Click to collapse
I have tried reflashing ROM, even going back to stock, wiping dalvik cache and cache in the process. Still same error with phone and text.

emfajardo2 said:
I have tried reflashing ROM, even going back to stock, wiping dalvik cache and cache in the process. Still same error with phone and text.
Click to expand...
Click to collapse
Well the app I linked will allow to change or add apn's if that's what you want.
However, do you have an EFS backup? Try restoring that. Also, check system network settings and make sure it is set to CDMA and not NV or GSM.
If you get on stock, try doing a profile/prl update.

dopy25 said:
Well the app I linked will allow to change or add apn's if that's what you want.
However, do you have an EFS backup? Try restoring that. Also, check system network settings and make sure it is set to CDMA and not NV or GSM.
If you get on stock, try doing a profile/prl update.
Click to expand...
Click to collapse
Unfortunately it looks like EFS backups have been erased after the multiple factory resets and wipes I've done. I called Sprint and they couldn't fix the issue and told me to take the phone to a store. At one point when I tried to update profile it said I must be in the USA, which I am. But that was fixed by some updates on their end and I can update profile/prl. However, now it'll say 4G with no bars and when I make a call, service goes out. Something strange that appeared temporarily but is now gone was a message saying the SIM card is invalid.
I also decided to look into phone identity and noticed that the my phone number section says unknown along with the MIN.

emfajardo2 said:
Unfortunately it looks like EFS backups have been erased after the multiple factory resets and wipes I've done. I called Sprint and they couldn't fix the issue and told me to take the phone to a store. At one point when I tried to update profile it said I must be in the USA, which I am. But that was fixed by some updates on their end and I can update profile/prl. However, now it'll say 4G with no bars and when I make a call, service goes out. Something strange that appeared temporarily but is now gone was a message saying the SIM card is invalid.
I also decided to look into phone identity and noticed that the my phone number section says unknown along with the MIN.
Click to expand...
Click to collapse
Yup, your IMEI, MEID, MIN were wiped. Do you have an old backup you can restore? It should also have the EFS within the backup so it would restore the IMEI, MEID, MIN.
If none of that works, try following this thread, it may have something you can benefit from.
http://forum.xda-developers.com/showthread.php?t=2161498

dopy25 said:
Yup, your IMEI, MEID, MIN were wiped. Do you have an old backup you can restore? It should also have the EFS within the backup so it would restore the IMEI, MEID, MIN.
If none of that works, try following this thread, it may have something you can benefit from.
http://forum.xda-developers.com/showthread.php?t=2161498
Click to expand...
Click to collapse
Eureka! I just remembered that I had backed up my phone earlier when it was working! Only issue is I'm not sure how to restore the backup.
I have a file with freegee, TWRP, and EFS_BACKUPS folders. I would post the folder but not sure if this is a privacy issue?
Anyways, any help in restoring this would be much appreciated!

emfajardo2 said:
Eureka! I just remembered that I had backed up my phone earlier when it was working! Only issue is I'm not sure how to restore the backup.
I have a file with freegee, TWRP, and EFS_BACKUPS folders. I would post the folder but not sure if this is a privacy issue?
Anyways, any help in restoring this would be much appreciated!
Click to expand...
Click to collapse
Is it just an EFS backup? Did you use the "create flashable EFS.zip"? Or is it only the backup in freegee? You can post screenshots, I wouldn't recommend posting the IMEI or any of that but if it is just a screenshot of the backup then you're ok because everyone has the same name of the backup. I think it is m9kefs1, m9kefs2, m9kefs3. If you are looking at those files, you need to push them using ADB. I think the directions are in that thread I linked. If you created a flashable zip (also directions in that thread) all you need to do is flash the zip it created like any other zip you'd flash in recovery. (TWRP in your case) Just boot into recovery and select install, then from zip. And choose your zip.

dopy25 said:
Is it just an EFS backup? Did you use the "create flashable EFS.zip"? Or is it only the backup in freegee? You can post screenshots, I wouldn't recommend posting the IMEI or any of that but if it is just a screenshot of the backup then you're ok because everyone has the same name of the backup. I think it is m9kefs1, m9kefs2, m9kefs3. If you are looking at those files, you need to push them using ADB. I think the directions are in that thread I linked. If you created a flashable zip (also directions in that thread) all you need to do is flash the zip it created like any other zip you'd flash in recovery. (TWRP in your case) Just boot into recovery and select install, then from zip. And choose your zip.
Click to expand...
Click to collapse
Here is a picture of the EFS backup folder I have:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So does this mean I must use adb? It wouldn't work to compress a folder with the files correct?

emfajardo2 said:
Here is a picture of the EFS backup folder I have:
View attachment 3091519
So does this mean I must use adb? It wouldn't work to compress a folder with the files correct?
Click to expand...
Click to collapse
I would store those somewhere safe period.
But you can also
1) Go to that thread I linked,
2) Download the flashable zip,
3) run it in recovery so it creates the restore zip.
4) go on your PC and replace the 3 files in the backup (that look like yours) with those files
5) Go back to recovery and run the restore zip.
That might do the trick without ADB. If that is too much for you, I can or autoprime can (the OP of that thread) create the file for you, you would have to send us those files. And I have no need for them, but in the wrong hands, they might be able to be used to put your IMEI and MIN on another phone. I am not sure it works that way but if you are not comfortable with that you can get on hangouts and send me a message and I will walk you through it if you send me screen shots during the process. (You would have to email those files, do not post them here)

dopy25 said:
I would store those somewhere safe period.
But you can also
1) Go to that thread I linked,
2) Download the flashable zip,
3) run it in recovery so it creates the restore zip.
4) go on your PC and replace the 3 files in the backup (that look like yours) with those files
5) Go back to recovery and run the restore zip.
That might do the trick without ADB. If that is too much for you, I can or PartimusPrime can (the OP of that thread) create the file for you, you would have to send us those files. And I have no need for them, but in the wrong hands, they might be able to be used to put your IMEI and MIN on another phone. I am not sure it works that way but if you are not comfortable with that you can get on hangouts and send me a message and I will walk you through it if you send me screen shots during the process. (You would have to email those files, do not post them here)
Click to expand...
Click to collapse
Thanks for all the help! I might have to contact you in hangout, I flashed the zip but not seeing a zip folder made in the EFS_backup

emfajardo2 said:
Thanks for all the help! I might have to contact you in hangout, I flashed the zip but not seeing a zip folder made in the EFS_backup
Click to expand...
Click to collapse
I don't remember if it is created if you don't have an efs.

Sorry for a very late reply but the problem has been resolved!
I was able to place my EFS backups in the zip created by dopy25, flash it in recovery, and then was able to gain network access by updating PRL and profile!

Twrp backup question

Please somebody could explain exactly what i need to backup in twrp? The system image and vendor image are needed? What they are in def? Thanks in advance...

From this forum, "the /vendor partition would only need backing up if you manually made changes to it yourself (for instance, if you use Layers). Otherwise, you can just use the vendor.img from the factory image if you need to restore /vendor."
From this forum, "According to TWRP in regards to System Image... this is a system read-only option that's intended to help you make a pure backup of your system image that you can later flash to receive over-the-air updates after having rooted or ROMed your device."
"The default backup options in TWRP are system, data, and boot. For most cases, this is sufficient for backing up a ROM. (Note that in some rare cases, boot isn’t available for backup on certain devices). If your device has the option, backing up android_secure and/or sd-ext may be a good idea. There’s usually no reason to back up cache or recovery (recovery not available for backup on some devices)." Answer found here.

enzippo said:
Please somebody could explain exactly what i need to backup in twrp? The system image and vendor image are needed? What they are in def? Thanks in advance...
Click to expand...
Click to collapse
Also make sure you backup your efs and keep atleast 2 copies eg 1 on phone and another on computer or in the cloud etc.
You only need to restore this if you loose your imei number due to corruption etc.

Best Way to Backup Rooted Verizon Note 4

Ok... So i FINALLY got my Verizon Note 4 upgraded to Android 6.0 (Running ModestRom.v9) and it is rooted and I have TWRP....
So since advanced Android documentation and procedures are all horribly biased and completely different everywhere you turn I will ask it here...
The TWRP backup I can attest does NOT work at all.... I backed up my KitKat 4.4 rooted installation and then after trying to downgrade back to it by restoring it - I got the boot screen loop and was never able to even start it again until I upgraded back up to Android 5.1
So is there a way to backup EVERYTHING (like take a complete image of the phones boot internal SSD etc....) so that NO MATTER WHAT STATE THE PHONE IS IN and what bootloader and OS is loaded I will always be able to revert back to my backup? Or is this just a fantasy?

zdanman said:
Ok... So i FINALLY got my Verizon Note 4 upgraded to Android 6.0 (Running ModestRom.v9) and it is rooted and I have TWRP....
So since advanced Android documentation and procedures are all horribly biased and completely different everywhere you turn I will ask it here...
The TWRP backup I can attest does NOT work at all.... I backed up my KitKat 4.4 rooted installation and then after trying to downgrade back to it by restoring it - I got the boot screen loop and was never able to even start it again until I upgraded back up to Android 5.1
So is there a way to backup EVERYTHING (like take a complete image of the phones boot internal SSD etc....) so that NO MATTER WHAT STATE THE PHONE IS IN and what bootloader and OS is loaded I will always be able to revert back to my backup? Or is this just a fantasy?
Click to expand...
Click to collapse
Twrp is the only way I know of to make a backup of your phone and it's setup. I have backups of RR, Modest and n seven port. Not sure what you did wrong. Just make sure you backup to external SD card.
Sent from my SM-N910V using Tapatalk

No.... TWRP definitely does not back up everything completely...
I attached a picture of the contents of the TWRP backup that I had TWRP restore from my sd card. I had TWRP complete the restore then wiped the cache and rebooted... It was stuck in a boot loop... i pulled the sd card... still stuck in a boot loop. I then wiped the datliv cache.. still stuck in boot loop.
TWRP backups are garbage and obviously DO NOT backup everything needed for a complete restore... Even on my PC i am able to boot in recovery and create a complete image of the boot sector and all. I can then restore that exact bit by bit image of my ssd and the computer will be EXACTLY as it was when i made the backup...
There needs to be a solution.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

zdanman said:
No.... TWRP definitely does not back up everything completely...
I attached a picture of the contents of the TWRP backup that I had TWRP restore from my sd card. I had TWRP complete the restore then wiped the cache and rebooted... It was stuck in a boot loop... i pulled the sd card... still stuck in a boot loop. I then wiped the datliv cache.. still stuck in boot loop.
TWRP backups are garbage and obviously DO NOT backup everything needed for a complete restore... Even on my PC i am able to boot in recovery and create a complete image of the boot sector and all. I can then restore that exact bit by bit image of my ssd and the computer will be EXACTLY as it was when i made the backup...
There needs to be a solution.
Click to expand...
Click to collapse
They've been working for me. ?? I've used it a few times now, heh — I am not used to Samsung bloatwear, and have def. "over-debloated" a few times.
If it helps, just as safeguard I still have ROM Manager (lol —if I put money into something, including TiBu, it's on my phone. Well, except that stupid Go Launcher (PRIME!) malware... ugh. I had a pretty flagship Moto once that was otherwise JUICED, but I had NEVER seen such a bad launcher! I would have used EMACS as my launcher I was so desperate (and yes you can!), but instead went to the Market aka "play store" (still hate it) and paid for first thing that had high stars. I was younger and stupid.) My twrp though doesn't have a launch drawer app at all; just boot into recovery. Not sure if I over debloated that or if I have to download something from the Market. (I hate the Market so much I use aptoide as default "app fetcher". MUCH more trustworthy, and they have apps Goolag doesn't let in.)
If it helps, I can report that ROM Manager still works? It recognizes my TWRPs and makes its own backups (full system) just like it's still 2011, and it knows TWRP is my recovery. And clockwork looks exactly the way you may remember, too. They haven't refreshed their UI at all. —And I don't mind that ONE bit. I mind TiBu's stupid UI because it is stupid, but ROM Manager just doesn't NEED much more of a UI imo. Open, backup or restore, reboot, profit).
BUT to use TWRP on the note, I have to boot into recovery. The last twrps I've had (on my last HTC Ones) have had an app drawer app, but I don't. Still, I've been backing up/restoring just fine from recovery. And I've just got a stock-ish xposed 6.0.1 Verizon (NO, wait: I just flashed Paul Pizz ROM, duh —btw that rom's quite lovely. SNAPPY!)
Can you boot into recovery and backup from there? I'd give that a few goes, save to phone, open on laptop, compare.

zdanman said:
No.... TWRP definitely does not back up everything completely...
I attached a picture of the contents of the TWRP backup that I had TWRP restore from my sd card. I had TWRP complete the restore then wiped the cache and rebooted... It was stuck in a boot loop... i pulled the sd card... still stuck in a boot loop. I then wiped the datliv cache.. still stuck in boot loop.
TWRP backups are garbage and obviously DO NOT backup everything needed for a complete restore... Even on my PC i am able to boot in recovery and create a complete image of the boot sector and all. I can then restore that exact bit by bit image of my ssd and the computer will be EXACTLY as it was when i made the backup...
There needs to be a solution.
Click to expand...
Click to collapse
Lol nothing can back up a partition that is in use when you attempt backup. Have to do a nandroid backup not a recovery. Btw my recovery completely installs working os from clean wipe.

i have a question? where is the android device ID stored?