I have a friend who has the Skyrocket.
He is rooted and has TWRP installed, but he is still running the stock rom and kernel.
Today his phone randomly rebooted and now it is stuck on the samsung logo. We have been able to take out the battery and boot into TWRP no problem.
We do have a backup from a while back and he is also considering trying a new rom at this point, but we'd like to be able to get this to boot.
Anyone have any ideas on how to get this thing to boot? What could have caused this?
Any help is greatly appreciated.
If the backup is a nandroid backup made in twrp restore that in twrp
jd1639 said:
If the backup is a nandroid backup made in twrp restore that in twrp
Click to expand...
Click to collapse
We do have a twrp backup and can restore it, but we're hoping to find something that will fix the boot issue.
Do you think it could possible fix the problem if we flashed a new kernel and then tried to boot? Can't hurt, right?
iLuvMudkips said:
We do have a twrp backup and can restore it, but we're hoping to find something that will fix the boot issue.
Do you think it could possible fix the problem if we flashed a new kernel and then tried to boot? Can't hurt, right?
Click to expand...
Click to collapse
You could try the kernel our you could also try wiping just cache and dalvik. I assume you're trying to save the data.
jd1639 said:
You could try the kernel our you could also try wiping just cache and dalvik. I assume you're trying to save the data.
Click to expand...
Click to collapse
We aren't trying to save the data. We already have a backup. We're trying to get this thing to boot without flashing a new rom or reverting to a backup.
iLuvMudkips said:
We aren't trying to save the data. We already have a backup. We're trying to get this thing to boot without flashing a new rom or reverting to a backup.
Click to expand...
Click to collapse
read the stickys, this one is right above your post, short answer wipe caches and if still a no go then do a factory reset, still a no go then restore, still a no go then read the sticky
Related
my one s recently developed a strange issue, where if i try to run a nandroid backup, it will mostly finish, then reboot itself without fully completing the process, leaving me with a bunk backup and stuck on one rom for now. also, and the more important of my 2 concerns, is that i don't know if it will do this during a rom flash, nor do i want to find out, seeing as i have no current working backup. doe's anyone have any ideas as to how i could fix this?
mercenaryhmster said:
my one s recently developed a strange issue, where if i try to run a nandroid backup, it will mostly finish, then reboot itself without fully completing the process, leaving me with a bunk backup and stuck on one rom for now. also, and the more important of my 2 concerns, is that i don't know if it will do this during a rom flash, nor do i want to find out, seeing as i have no current working backup. doe's anyone have any ideas as to how i could fix this?
Click to expand...
Click to collapse
At a guess you got a high Hboot so that means when you restore its not restoring the boot.img. You need to flash that in fastboot.
Darknites said:
At a guess you got a high Hboot so that means when you restore its not restoring the boot.img. You need to flash that in fastboot.
Click to expand...
Click to collapse
nope, i have hboot 1.06, and either way that wouldn't, and shouldn't, cause a nandroid to fail during backup, nor for the phone to reboot by itself.
mercenaryhmster said:
nope, i have hboot 1.06, and either way that wouldn't, and shouldn't, cause a nandroid to fail during backup, nor for the phone to reboot by itself.
Click to expand...
Click to collapse
Oh if you mean you cant make a backup try a newer recovery or if its already up to date try an old one.
Edit, just to add I use TWRP 2.2.2.0 and it works fine.
Darknites said:
Oh if you mean you cant make a backup try a newer recovery or if its already up to date try an old one.
Edit, just to add I use TWRP 2.2.2.0 and it works fine.
Click to expand...
Click to collapse
tried using twrp 2.3, 2.2, cwm touch, regular cwm, does it on all of them.
mercenaryhmster said:
tried using twrp 2.3, 2.2, cwm touch, regular cwm, does it on all of them.
Click to expand...
Click to collapse
Not sure then sorry.
Do you have enough free space on your sdcard partition?
You can also try (un?)mounting /data and /system before you start the backup.
Just as an update, I solved my problem. It seems that there were some corrupted files on my data partition, and they were causing nandroid to fail and reboot randomly. So, since I was planning on wiping anyway, I wiped and set up viper again, and successfully made a nandroid after.
Edited the build.prop file by adding 1 line, restarted phone and now I keep getting System UI has stopped message.
Any way I can edit the file to fix my phone?
Have you tried to clear the cache in recovery? If that doesn't work, try a full factory reset.
If the phone is running a stock rom, try flashing just the system.img file in fastboot.
Before doing any of this, make sure you backup your data.
audit13 said:
Have you tried to clear the cache in recovery? If that doesn't work, try a full factory reset.
If the phone is running a stock rom, try flashing just the system.img file in fastboot.
Before doing any of this, make sure you backup your data.
Click to expand...
Click to collapse
Thank you, I ended up backing up the data and cache via USB, then did a flash of Cataclysm ROM. I'll let you know if it works.
Can I just restore the data ASAP after installation or do I need Google to finish restoring my backup first?
Edit: Well, restored data, stuck with the boot screen loop again, then goes to Android is upgrading... and shows it optimizing 10 apps, and back to the boot logo.
Did the phone boot without restoring data?
audit13 said:
Did the phone boot without restoring data?
Click to expand...
Click to collapse
No, I made sure it was completed.
Now Play Store keeps quitting when I try to install apps. I can only install specific ones.
I recommend flashing a stock rom to make sure there isn't a hardware problem. Don't restore anything until you are sure the phone works.
audit13 said:
I recommend flashing a stock rom to make sure there isn't a hardware problem. Don't restore anything until you are sure the phone works.
Click to expand...
Click to collapse
Alright, I was able to get all my apps installed besides United Airlines and can't update Chrome.
So the stock rom works fine?
audit13 said:
So the stock rom works fine?
Click to expand...
Click to collapse
Yes, thank you.
I don't think I want to do another custom ROM for now.
The stock rom is the best with the bloat taken out .I think the kernel can be improved though. I use EX
I installed OnePlus Switch to create a backup. After it completed the backup process, the phone became stuck and now its in a bootloop. It was running stock OS with no root or any modifications. Please help.
I find this hard to believe because it doesn't really make a 100$ backup like TB does but have you tried to reboot into recovery and try to clean the cache?
RiTCHiE007 said:
I find this hard to believe because it doesn't really make a 100$ backup like TB does but have you tried to reboot into recovery and try to clean the cache?
Click to expand...
Click to collapse
Yea, doesn't make sense why this would happen.
I break my system a lot (currently testing which of my favorite Xposed modules work with Pie) . I've had to set up from scratch like 6 times in the past week. Every TWRP restore results in a boot loop, both custom and stock. Has anyone made it work and, if so, how? It surprises me that our TWRP is official if it can't restore a backup.
Encrypted?
arkansawdave74 said:
I break my system a lot (currently testing which of my favorite Xposed modules work with Pie) . I've had to set up from scratch like 6 times in the past week. Every TWRP restore results in a boot loop, both custom and stock. Has anyone made it work and, if so, how? It surprises me that our TWRP is official if it can't restore a backup.
Click to expand...
Click to collapse
I'm having the same problem. This is my first a/b device and everything I thought I knew after flashing ROMs for years just doesn't seem to work on this architecture. Like you said twrp backup restore always results in a bootloop. Also any full custom ROMs I've tried appear to overwrite twrp and install its own recovery. Even gsi's don't boot and then twrp freezes and back to stock I go. This thing has me stumped.
Skippy12359 said:
I'm having the same problem. This is my first a/b device and everything I thought I knew after flashing ROMs for years just doesn't seem to work on this architecture. Like you said twrp backup restore always results in a bootloop. Also any full custom ROMs I've tried appear to overwrite twrp and install its own recovery. Even gsi's don't boot and then twrp freezes and back to stock I go. This thing has me stumped.
Click to expand...
Click to collapse
I noticed when installing RR that it actually needs that Lineage recovery to factory reset after the install. A TWRP factory reset wouldn't help it, and it wouldn"t boot after the install. Funny how they try so hard to stop us tinkerers, then steal all our cool ideas for their stock ROMs. I see Linux phones in my future.
I wonder if a factory reset with that Lineage recovery would help after a TWRP restore? Next time I may try that.
Damn! I just got it. I'm typing this on a restored crDroid Official. The boot.img is in ramdisk, so only backup system and data. Yay!
WoKoschekk said:
Encrypted?
Click to expand...
Click to collapse
Just saw this. No. I had flashed dm-verity. Good thinking.
arkansawdave74 said:
Damn! I just got it. I'm typing this on a restored crDroid Official. The boot.img is in ramdisk, so only backup system and data. Yay!
Click to expand...
Click to collapse
So your saying because recovery is in the boot image that we need only to backup system and data and then a restore of same will not go into a bootloop? That would mean the problem has been backing up and then restoring the boot image. System as root and no recovery partition is just hard to grasp at this point. For me restoring data in a backup of stock results in twrp error 255.
Skippy12359 said:
So your saying because recovery is in the boot image that we need only to backup system and data and then a restore of same will not go into a bootloop? That would mean the problem has been backing up and then restoring the boot image. System as root and no recovery partition is just hard to grasp at this point. For me restoring data in a backup of stock results in twrp error 255.
Click to expand...
Click to collapse
I spoke too soon. This was the 1st time I'd flashed dm-verity on the install. That's why it worked. It won't work if /data is encrypted. I just made a backup with boot as well and it restored fine.
arkansawdave74 said:
I spoke too soon. This was the 1st time I'd flashed dm-verity on the install. That's why it worked. It won't work if /data is encrypted. I just made a backup with boot as well and it restored fine.
Click to expand...
Click to collapse
Which version of dm- verify are you using and what steps did you take to get crdroid to boot?
Skippy12359 said:
Which version of dm- verify are you using and what steps did you take to get crdroid to boot?
Click to expand...
Click to collapse
I'm not sure where I got it Or else I would link you. But this is the one I'm using this one. I flashed it after formatting /data and also after installing the ROM. One of those is proper, but I couldn't remember. I think it's supposed to be after you install, but before 1st boot.
https://www.mediafire.com/download/uxldj5okanllfza
arkansawdave74 said:
I'm not sure where I got it Or else I would link you. But this is the one I'm using this one. I flashed it after formatting /data and also after installing the ROM. One of those is proper, but I couldn't remember. I think it's supposed to be after you install, but before 1st boot.
https://www.mediafire.com/download/uxldj5okanllfza
Click to expand...
Click to collapse
That's the same one I've been using. So crdroid actually booted for you after doing a normal wipe in TWRP?. Assuming you had stock pie installed.
Skippy12359 said:
That's the same one I've been using. So crdroid actually booted for you after doing a normal wipe in TWRP?. Assuming you had stock pie installed.
Click to expand...
Click to collapse
Yup. I've restored it twice and made another with boot included and it booted as well. I hope it works with RR too, but I've got a helluva headache. I may stop messing with it for now.
Oh, I had wiped dalvic (actually ART), system, and data. I don't think boot was an option during wipe.
You know, I've only had one device before thar force encrypted, and back then, TWRP couldn't decrypt /data except by formatting. Now it can. That's why I didn't suspect it was an encryption issue.
I was still using a Galaxy S5 with crDroid 7.1.2 built by me until last week. It died, may it rest in peace.
Skippy12359 said:
That's the same one I've been using. So crdroid actually booted for you after doing a normal wipe in TWRP?. Assuming you had stock pie installed.
Click to expand...
Click to collapse
If, when you boot TWRP, it asks you to decrypt, dm-verity didn't work, and it might not work with stock. I'm only figuring it out at the moment.
arkansawdave74 said:
If, when you boot TWRP, it asks you to decrypt, dm-verity didn't work, and it might not work with stock. I'm only figuring it out at the moment.
Click to expand...
Click to collapse
My goal was to have twrp backup of stock pie which is really great in my opinion and also be able to flash Q gsi's like I do on my Moto g6. So far any backup restore of stock just bootloops and any gsi just hangs at boot logo or boots back to recovery.
arkansawdave74 said:
If, when you boot TWRP, it asks you to decrypt, dm-verity didn't work, and it might not work with stock. I'm only figuring it out at the moment.
Click to expand...
Click to collapse
It does appear to be an encryption issue with a stock rom TWRP backup restore not booting. Formatting data in TWRP and rebooting always results in a bootloop. Until I can format data to remove encryption and get it to boot and the security setting says it's not encrypted, I don't think a backup will ever boot. Out of ideas at this point.
Skippy12359 said:
It does appear to be an encryption issue with a stock rom TWRP backup restore not booting. Formatting data in TWRP and rebooting always results in a bootloop. Until I can format data to remove encryption and get it to boot and the security setting says it's not encrypted, I don't think a backup will ever boot. Out of ideas at this point.
Click to expand...
Click to collapse
For stock, I wonder if you could boot TWRP after all those fastboot commands and flash dm-verity before booting stock. You may be able to keep stock from encrypting. I don't know for sure though.
Hello,
On Xiaomi Mi 10 Ultra with TWRP 3.4.2b-0623 wzsx150, i did a full backup (all partitions) then after some moding and all on phone. decided to restore the full backup trought TWRP
the phone goes on bootloop and didnt want to start.
i already fixed the phone by flashing rom again, but i'm wondering why a TWRP full restore give a bootloop ? any help to understand to avoid this next time
thanks a lot
This is late but this happened to me before aswell. You have to flash the rom which you've done the backup on and then just restore the data partition.
Does your device keep in a frozen black screen?
Psych0t1c20 said:
This is late but this happened to me before aswell. You have to flash the rom which you've done the backup on and then just restore the data partition.
Click to expand...
Click to collapse
i did it with same rom, but i think the issue is from me restoring all partition, i think i need to choose only ones needed
Rovyo said:
i did it with same rom, but i think the issue is from me restoring all partition, i think i need to choose only ones needed
Click to expand...
Click to collapse
If you are restoring to the same device of the backup, just restore it and then wipe data.
Reboot and it will work perfectly.
VD171 said:
If you are restoring to the same device of the backup, just restore it and then wipe data.
Reboot and it will work perfectly.
Click to expand...
Click to collapse
exactly what i have did, but i checked all partitions when i did the restore i think i need to uncheck some of them in order to avoid the bootloop