For whatever reason last time my battery died my phone's not properly booting anymore.
I flashed stock rom and kernel, wiped dalvik cache, battery stats cache partition, fixed permissions...
I remember last time I had a bootloop resulting from something I did with build.prop I was able to get a verbose realtime log of the booting over USB, but I don't remember how I did it.
logcat's not found in my sbin, it's in /system/bin, and when I run it from there it stops when trying to boot into main.
I have adb and fastboot.
In recovery (ie, CWM or TWRP), do a full backup (NANDROID) and then:
data/factory reset
format /system
format /boot
Now flash a Stock ROM for your phone again. This should sort out just about any non-hardware issue.
if i restore that backup will i have my /data back? Would restoring put it in the same state of affairs that led to the bootloop?
Is there a way to partially restore a nandroid backup? I'm trying to get app data and such back.
You can restore either the whole partition via cwm or parts of it via app extractor. You can also edit the data partition and restore the edited version.
Related
in the recovery mode, when you perform a wipe, what exactly does it wipe from the phone?
I was in the process of updating from JF 1.31 to JF 1.41 and one of the themes I had was messing with my phone so I performed a wipe ( alt + W). when I rebooted I was still running JF 1.41 w/o root or any of my information (apps, data, etc). So I would assume everything but the current ROM is wiped? meaning I still have to telnet to get root again?
after upgrading the JF 1.41 I performed a NAND restore...
I had previously moved the caches / apps to my sdcard do I need to do this again? iI am assuming with the NAND restore I am all set, but if I had to performed the wipe w/o the NAND restore I would need to move them again?
and what are the commands to clear the caches? I know it's listed somewhere but I can't seem to find it.
If you installed JF1.4.1 then you have root. Once you root then you don't have to re-root unless you re-flash with the unmodified RC30 image.
I'm not sure about nandroid backup and restore, having never gotten around to using it, but I would think that if you did a nandroid backup of JF1.3.1 then restoring it from JF 1.4.1 would return you to JF 1.3.1 -- that's a complete guess, though.
Wipe formats the /system and /data partitions, so you'll have to re-do all of your cache moves and moving your apps to sd.
well I must have lost root or messed it up somewhere with the NAND restore as when I open up terminal and type in SU I get the following:
error type 3
error: activity class {koushikdutta.superuser/koushikdutta.superuser.superuserrequestactivity} does not exist
....root also does not show up in the SU whitelist app.
I think at this point I am just going to backup my apps/info with mybackup, wipe and start from scratch without NAND for now....eventually creating another NAND after a fresh install.
try reinstalling super user, also you apps should still be on you sdcard, just repush mountd and init files recreate syslinks and reboot, first reboot may seem like its stuck but just wait for it atleast 5min-10min
bornsteinSAE said:
in the recovery mode, when you perform a wipe, what exactly does it wipe from the phone?
Click to expand...
Click to collapse
It formats /data and /cache.
I did a nandroid backup bit it said fatal error while backing up bpws...or something like that...(one more thing...will nandroid backup...backup my apps if I lost them??)
Sent from my XT720 using XDA App
vari9 said:
I did a nandroid backup bit it said fatal error while backing up bpws...or something like that...(one more thing...will nandroid backup...backup my apps if I lost them??)
Click to expand...
Click to collapse
For some reason we can't back up all the partitions in nandroid. It should be enough to backup system and data. Optional: boot, logo (if you modified M boot logo), cache (usually not necessary), sd data (if you use ext partition on SD card).
With nandroid of system and data (and the others, but only if you use them) you should expect to be able to go back to exactly how your phone was at the time you made the backup. But you will lose changes you made after you made the backups.
When I'm about to start testing ROMs, I backup system and data. To go back to my pre-testing ROM I restore system and data and then wipe cache partition.
Mioze7Ae said:
When I'm about to start testing ROMs, I backup system and data. To go back to my pre-testing ROM I restore system and data and then wipe cache partition.
Click to expand...
Click to collapse
You want to say system and boot ?
Because changing a room modify system.img and boot.img
The boot.img is the same on all the ROMs thanks to the locked bootloader.
Yeah, I never even bother changing boot.img from the sbf version. If I did I'd probably use the Russian one because I think it was the most recently compiled.
Ok, I wasn't knowing that I always flash boot.img that come with ROM.
For 2 days or so I've been having random reboots and today after one I couldn't boot up my phone.Tried wiping dalvik cache and cache, flashing new boot.img and backuping and restoreing.
ROM: ViperS 1.6.3(clean install)
Kernel at that time: SebastianFM 1.5.2
Logcat attached
steelclaw said:
For 2 days or so I've been having random reboots and yoday after oen I couldn't boot up my phone.Tried wiping dalvik cache and cache, flashing new boo.img and backuping and restoreing.
ROM: ViperS 1.6.3(clean install)
Kernel at that time: SebastianFM 1.5.2
Logcat attached
Click to expand...
Click to collapse
Can you please attach a dmesg?
I also tried installing ViperS 1.63 and restoring only the data partition from the backup but again I get stuck at the splash screen.
a quick look at the logs seems like modem initialization has failed
reflash the firmware and see
also ..do a clean flash of vipers rom ..then boot it up ..setup the basic stuff
then go back to recovery and do any other things you want (another kernel, restore data etc etc )
As I said restoring data from the backup to a freshly installed ROM causes bootloops again, therefore I think that the problem is somehow connected to the data partition.
Side note: Just before the phone shut down I turned on my mobile data.Maybe it is indeed a problem with the radio?
HBOOT-1.27.1100
Radio-11.24A.3504.31_M
PS. Anyway I can get my data back from a nandroid backup?
Update:
If I wipe out the data the phone can boot normally.
steelclaw said:
As I said restoring data from the backup to a freshly installed ROM causes bootloops again, therefore I think that the problem is somehow connected to the data partition.
Side note: Just before the phone shut down I turned on my mobile data.Maybe it is indeed a problem with the radio?
HBOOT-1.27.1100
Radio-11.24A.3504.31_M
PS. Anyway I can get my data back from a nandroid backup?
Update:
If I wipe out the data the phone can boot normally.
Click to expand...
Click to collapse
Your data partition had errors. I assume the wipe/format cleaned and corrected the problem.
Yes but is there anyway I can get my data back because I have some really important stuff there.
steelclaw said:
Yes but is there anyway I can get my data back because I have some really important stuff there.
Click to expand...
Click to collapse
It's possible.
You'll need to restore the /data image you have backed up.
Reboot into 4EXT and mount the /data partition.
Make an Adv. Backup of the current /data partition.
Restore the old backup.
Run this.
Code:
e2fsck -f /dev/block/mmcblk0p23
Code:
adb pull /data/ .
The entire /data directory will be pulled from the phone to the folder in which you keep your ADB executable.
From there you can selectively copy files to the phone.
or an easy way to do is from titanium backup app
you can extract data of apps /phone from nandroid backup
Thanks both of you.
Update:
Most of my data is corrupted but luckly the one I needed was still intact
long story short: just to assure myself for everything to go smoothly while installing Lineage OS 14.2 i stupidly decided to tick the 'system' box on factory reset for TWRP along with the standard data, cache and dalvik. now i tried to system restore the backup i have on my sd card and it says error 225 at the end and its stuck on boot!
what have i done wrong? can you no longer restore if you tickbox the 'system' thing; does the backup option not backup literally everything? did my files corrupt? will the 'format data' option (deleting everything on internal storage), then trying to restore fix it? HELP.
phone is a Samsung Galaxy J3 2016 (J320fn) fwiw
idklol123 said:
long story short: just to assure myself for everything to go smoothly while installing Lineage OS 14.2 i stupidly decided to tick the 'system' box on factory reset for TWRP along with the standard data, cache and dalvik. now i tried to system restore the backup i have on my sd card and it says error 225 at the end and its stuck on boot!
what have i done wrong? can you no longer restore if you tickbox the 'system' thing; does the backup option not backup literally everything? did my files corrupt? will the 'format data' option (deleting everything on internal storage), then trying to restore fix it? HELP.
phone is a Samsung Galaxy J3 2016 (J320fn) fwiw
Click to expand...
Click to collapse
If you wiped everything, you can't just restore the system only, the default restore that restored all partitions that were backed up, is what you need.
Or, you can boot into TWRP, then select the wipe option, then select advanced wipes, then select the system, data, cache and dalvik cache partitions then swipe the slider to wipe. After the wipe is finished, flash your LineageOS ROM and gapps.
After flashing the ROM and rebooting the device, if you want to try to restore the backup that you made, boot into TWRP, when retoring a backup, it isn't necessary to do any kind of wipes because it automatically formats the partitions before restoring the backed up data to each partition.
Sent from my LGL84VL using Tapatalk
Droidriven said:
If you wiped everything, you can't just restore the system only, the default restore that restored all partitions that were backed up, is what you need.
Or, you can boot into TWRP, then select the wipe option, then select advanced wipes, then select the system, data, cache and dalvik cache partitions then swipe the slider to wipe. After the wipe is finished, flash your LineageOS ROM and gapps.
After flashing the ROM and rebooting the device, if you want to try to restore the backup that you made, boot into TWRP, when retoring a backup, it isn't necessary to do any kind of wipes because it automatically formats the partitions before restoring the backed up data to each partition.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
i solved. it turns out i just didnt have enough memory to extract the system restore into internal storage.
what do you mean though? the only problem im having in the stock OS now is that my phone will randomly stop charging and/or display different battery %'s (one time it said i had 89% for 15 minutes straight without charging it. i rebooted it and then it said it was at 94%), as well as im unable to manually update (says my original OS was modified in a non authorized manner)
is there anything i can do in TWRP in regards to either of these things? maybe re flash stock OS? (how would i go about doing that without losing all my data?)
I keep trying to do backups but it gets about half way through and the error 255. I don't understand what I'm doing wrong. Is it not possible to backup through twrp on xt1955-5. If not any suggestions on other means. Something that would include my accounts as well would be great. I have an google acct that google refuses to give back. Be cause they say can't verify. I know password but 2sv got messed up. Which is a bunch of bs. They track everything. I would prefer to never have to go through this again. Any help would be great.
First question. What all are you trying to backup? Second, to where? Third, do you have adequate space for said backup?
Also, if you have a pin or code enabled for access to the device I would disable it for the backup process.
I'm trying to back up system and data only to my ext sd with 50g avail but only needing 12g
Pbsipher1 said:
I'm trying to back up system and data only to my ext sd with 50g avail but only needing 12g
Click to expand...
Click to collapse
I was able to use TWRP to create a backup on an SD card. I'm running Android 10 and rom RR.
You might try other avenues like titanium or migrate. A quick internet search might lead you to a better procedure and app.
I've been having the same trouble. I just restored my XT1955-5 to stock RETAIL. Then installed TWRP and Magisk. I set my phone up as I like it, and want to back it up - everything I can possibly backup - boot, data, system, system image, efs, persist1, persist2, fsg, vendor, vendor image, dsp, and boot logo.
Before I tried to backup anything, I made sure that I mounted all of the partitions in TWRP.
The first few times I tried to back them all up at once, I got the error 255. So I started backing up the partitions one by one. The only partition that would NOT backup was the data partition. I still get the error 255 on the data partition backup. But all the others worked fine. I even went back and selected all the partitions except the data partition, and it backed up in one large backup just fine. So I don't know what the deal is with the data partition, but I can grab it with adb pull, so I guess I'm good to go.
I even booted back into the system and turned off the screen lock PIN - changed it to none. But I still couldn't backup the data partition via TWRP.
This should work for you from adb to backup your data partition:
Code:
adb push mmcblk0p64-data.img /dev/block/mmcblk0p64
Thanks tom2112 I'll give it a try what can it hurt. I also heard u have to be decrypted in order to backup data but can't seem to get decryption to stick
i was no able to backup using that command got
adb: error: stat failed when trying to push to /dev/block/mmcblk0p64: permission deni
Tom2112 said:
I've been having the same trouble. I just restored my XT1955-5 to stock RETAIL. Then installed TWRP and Magisk. I set my phone up as I like it, and want to back it up - everything I can possibly backup - boot, data, system, system image, efs, persist1, persist2, fsg, vendor, vendor image, dsp, and boot logo.
Before I tried to backup anything, I made sure that I mounted all of the partitions in TWRP.
The first few times I tried to back them all up at once, I got the error 255. So I started backing up the partitions one by one. The only partition that would NOT backup was the data partition. I still get the error 255 on the data partition backup. But all the others worked fine. I even went back and selected all the partitions except the data partition, and it backed up in one large backup just fine. So I don't know what the deal is with the data partition, but I can grab it with adb pull, so I guess I'm good to go.
I even booted back into the system and turned off the screen lock PIN - changed it to none. But I still couldn't backup the data partition via TWRP.
This should work for you from adb to backup your data partition:
Code:
adb push mmcblk0p64-data.img /dev/block/mmcblk0p64
Click to expand...
Click to collapse
ed
Hmm... if it is "permission denied" that sounds like you need root permissions to back it up. I'm sorry, but I'm not good enough with ADB to tell you how to get higher privs. Maybe ADB SHELL then SU, but I don't honestly know.