Hello everyone!
I have a mexican (Telcel) Moto G XT1032. I installed the GPE ROM on it, then did an update to Android 4.4.4.
Today I wanted to try AeroKernel. I booted onto TWRP and performed a boot backup.
After that I installed the new AeroKernel release from today. It worked fine, so I downloaded its tweaking app and started playing a bit with the undervolting. It worked fine for a while, so I marked the checkbox to keep the changes after a reboot.
Then I performed a reboot and, after the initial logo, got a black screen instead of the boot animation. So I went to TWRP and restored my boot backup. But still, black screen.
Anything I can do to restore the original volt values?
In advance, many thanks.
What I ended up doing:
- Went into TWRP, backup my data and move the backup to my PC.
- Restored GPE and updated to 4.4.4.
- Get the data backup from PC to my phone.
- Restored it with TWRP.
Took me some minutes but I'm OK again. :silly:
Related
Let me preface this: I don't need to use this phone regularly, as my Nexus One is now my primary, but it'd be nice to get this phone back to bootable again.
I loaded up the OpenRecovery version suggested for the CyanogenMod Alpha. From there I took a nandroid backup of my existing ROM (Telus Milestone) and then successfully booted up Cyanogen. After experiencing some of the bugs I decided it was time to roll back.
So I went back into OpenRecovery and restored the full nandroid backup. Well, now I boot up and all I get is the "M". Won't go any farther than that.
So then I tried to flash the GOT version of Telus 2.1 from RSD Lite. It flashed, and then rebooted to... again, the "M", didn't boot further after several minutes. Battery pull again.
Next try - the non-service Telus firmware via RSDLite
(A853_Telus_Firmware_SHOLS_U2_03.10.0__USASHLSMR2TLSB1B2B505F.0R_1FF.sbf). Rebooting... PHEW! Android bootup screen appears. And it boots, yay. Flashed the vulnerable recovery and returned to OpenRecovery. Nandroid restore but this time *only* system and data. Ick, and once again it hangs... bad backup? Trying a data wipe... it's still not happy, so I guess the system partition is the problem with my backup.
Anyways I have no idea why the backup won't boot, but I suppose I can set it aside, sleep, get done what I need to tomorrow and revisit it on the weekend.
the problem is in your backup. It happened to me twice now that I have to flash the original firmware because the backup also has a problem.
I think I've concluded what the problem is. The modded OpenRecovery that is suggested on the CM6 thread is no good at restoring the system partition. The backup I took from GOT OpenRecovery earlier in September restores fine from GOT OpenRecovery. But none of my backups restore to a bootable state from the other OpenRecovery.
So what I had to do was restore the older backup from GOT, then switch back to the modded recovery and restore only the data partition. And next time I try this I will take my final backup from GOT.
So, I was running Anerik's Unofficial CM12 but decided I wanted to try out the GPE 5.0.1 .
I followed "The Ultimate Guide to flash 5.0.1" by pfufle and it seemed to work fine.
I used Titanium Backup to restore a few apps and then restarted my phone because that's what you are supposed to do after restoring apps.
Only problem is that after the reboot, it would get past the Boot Logo (The Google logo with the unlocked padlock) but then stay on the Boot Animation (The 4 colours moving around) eternally (I left it there for around 20-25 mins.
I then got fed up of waiting and decided to retry flashing 5.0.1 by following the guide from the start and flashing gpe 4.4.4 then 5.0.1 etc.
Same problem. I tried maybe 4 times all of them ended with the same result.
I gave up and then went back to 4.4.2 from which I flashed Anerik's CM12 again.
I restored my apps via TB, restarted my phone but what do you know. Got past the Boot Logo but got stuck on the Boot Animation (The one with the CM Logo and the arrow spinning around) eternally.
I haven't checked if this problem happens in 4.4.2 and GPE 4.4.4.
How do I fix this?
Hi everyone!
I figured, why not give MIUI a try. I downloaded the rom, made a full TWRP backup, then installed the ROM. It just froze after the MIUI logo appeared, so I decided to restore.
All the while, I noticed a new red Oneplus logo where the old one had been white. But even after restoring my backup, the startup logo was still red, and my previous rom was freezing during the boot animation. I tried again, no luck.
Then I thought, I'll just load my old rom (Vanir/Exodus) from the downloaded zip OVER my restored rom, maybe that will fix things. It won't let me do that, however, due to an error in TWRP which I've never gotten -- "Error executing updater binary in zip".
So I went to the bootloader to update TWRP, and noticed the whole bootloader looks different and is in Chinese. So it must've been part of the MIUI ROM.
What do I do now? I'd love to just fix the bootloader but not sure how. Maybe if I did that I could then restore my backup. As a precaution, I've ADB Pulled the backup folder just in case I have to start over, then I can copy the backup folder back in and try to restore it........
Thanks for the help!
Well, I figured it out on my own. I went to download the latest version of CM12 from here, and ADB Pushed it while in TWRP. I then installed it, and it didn't give me that assert error. I rebooted, but powered down while it was starting up, went back to TWRP, and restored my backup, no problemo. I wonder what happened.
It would be nice to understand what the issue was that prevented me from restoring it initially, and what I could have done manually to update the particular thing that I needed to update.
Pretty sure it was an the firmware ColorOS uses and is incompatible with the newest roms based on the CM firmware
Not really sure where I should have put this but have a weird issue. I have a droid turbo xt1254 that I have rooted and flashed many times. The most recent, today, I accidentally did a full system wipe and when I went to reflash the rom already in twrp, it gave me an error.
I then tracked down cm13 for my phone, which had worked previously and reinstalled it but every time I reboot the phone, it goes straight into twrp.
I have found that If I reboot into the bootloader, I can choose factory and whichever rom I have installed works until I reboot.
Can anyone help me stop this and get it to boot straight into the rom?
Hi all,
A couple of days ago I flashed the OTA image for 8.1. Realising I don't have root and not finding a way to root 8.1 yet, I figured, hey, I'll go back to 8.0. Luckily I did a full backup using TWRP before upgrading.
TWRP 3.1.1 was unable to decrypt the filesystem and therefore restore anything (which I've read is a known issue). Neither could 3.2.1, and 3.2.1 couldn't see the OTG drive I have the backup on, either.
At this point I'd already wrecked the OS by trying to restore without first decrypting the filesystem (figured it'd just overwrite it so who cares). So I flashed the latest 8.0 factory image, started it up to make sure it boots, went back into TWRP and restored the full backup from the OTG drive.
This succeeds - but when rebooting all I get is the initial Google logo. Nothing else. No loop, no progress meter, nothing.
Am I missing a step? Anyone?
jethro1138 said:
Hi all,
A couple of days ago I flashed the OTA image for 8.1. Realising I don't have root and not finding a way to root 8.1 yet, I figured, hey, I'll go back to 8.0. Luckily I did a full backup using TWRP before upgrading.
TWRP 3.1.1 was unable to decrypt the filesystem and therefore restore anything (which I've read is a known issue). Neither could 3.2.1, and 3.2.1 couldn't see the OTG drive I have the backup on, either.
At this point I'd already wrecked the OS by trying to restore without first decrypting the filesystem (figured it'd just overwrite it so who cares). So I flashed the latest 8.0 factory image, started it up to make sure it boots, went back into TWRP and restored the full backup from the OTG drive.
This succeeds - but when rebooting all I get is the initial Google logo. Nothing else. No loop, no progress meter, nothing.
Am I missing a step? Anyone?
Click to expand...
Click to collapse
Had you ever tried restoring the backup before to verify it was stable? Perhaps there was some corruption in the backup file?
Well, it is able to restore the whole thing without an error. I think that counts as verifying that it's not corrupt...
I'm facing the same exact issue. I've got several previous backups of my Pixel, all of 8.1, and if I try restoring any partition except /data they restore successfully and boot as a fresh phone.
Now of course I need my data, but when I try to restore any of my previously backed up /data partitions, they either freeze during restoration or restore successfully. However if they do restore successfully, my phone won't boot anymore. After showing the Google logo, then animated G, it reboots back to recovery.
I tried most things as of now but to no avail. This really sucks!