Hi, I have my HTC one x, running CM10. I was prompted for an update to 10.1 so I downloaded and installed, but the phone would not boot, so I downloaded the build I was running before the 10.1 and installed it. The install went fine, however the phone gets stuck in a boot loop while the CM logo is spinning, and wil not progress further than that point. I figure I probabley have to wipe my phone and do a clean install, so how would I extract all of my contacts pictures and app information from the phone? Or is there a different way that I could reinstall the ROM and get it to boot past the logo? thanks!
EDIT: I have since wiped the phone, but i do have backups obtained from TWRP, when I go to restore them the keep bootlooping, can I extract data from them?
If you are on hboot 2.20, and restore a TWRP backup of a "different" ROM than is currently on the phone, then you need to flash the boot.img of the "old" ROM (in your case CM10.0) via fastboot.
There is no way that I know of to extract app data or other user data from a TWRP backup. But I'm guessing that flashing the boot.img will get you back to the old ROM. From there, use Titanium Backup to backup your app data.
The default on Android is for your contacts to save to the Gmail cloud. So unless you turned this off, you shouldn't need to backup or migrate contact info. Just login to Gmail on your computer to see if the contact info is there. Really this is the way Android is meant to be used (contacts, calendar, Gmail is on the cloud and doesn't require any action by the user to backup), so its always a surprise to me that people turn this off.
Related
I shattered the screen on my Nexus 5, and G was kind enough to send a replacement (refurbished). Since I have TWRP Nandroid backups, I thought it would be an easy matter to unlock/root/TWRP the new replacement phone, copy over the backup files, then restore. However, TWRP does not seem to be working - I get a bootloop, with an android mascot with a red triangle and the words "no command" when I select "Recovery".
My original N5: unlocked, rooted, TWRP, Android 4.4.4
Replacement N5:
- originally with Android 4.4.0
- unlocked, rooted and TWRP installed with Nexus Root Toolkit (NRT)
- system was then upgraded to 4.4.2, 4.4.3, 4.4.4
- went into fastboot, tried to select Recovery....and nothing.
Is this an issue with TWRP? Should I try flashing a different version?
Is this an issue with the process? Should I use NRT to "Return to Stock", THEN let the system update itself to 4.4.4, THEN try unlock/root/TWRP and recovery?
Is this an issue with the root process? Should I use CF Auto Root and try to re-root, re-install SuperSU, etc. on the current system?
TIA
Ed
That's stock recovery. Do yourself a favour and flash recovery properly without using a toolkit.
Thank you - that was absolutely correct. Apparently NRT either didn't install TWRP, or didn't flash an error message saying TWRP install failed (or I missed it).
I downloaded a TWRP flash image, and after some tweaking with drivers, managed to flash it just fine.
I then copied over my original N5 TWRP backup, and restored it. Aside from some minor data location problems (e.g., Evernote detected new SD Card, re-sync'd all notes), it worked fine and the new phone is in the exact same state/configuration as the original phone.
Now to go track down the "TWRP restore to a different device" threads.
Thanks!
The rule really is never restore EFS from another device.
Old device, backup system, boot and data
New device, make a small backup to generate the serial number folder. Then copy the backup from the old device.
Hi all,
So I'm far from a noob at at all of this (doing the custom android thing for years). But I'm not exactly constantly fiddling with my phone all the time anymore either. Basically I get a set-up that works for me, and I stick with it.
I've patiently been waiting to update to Lollipop. And today I did it. I did it by flashing the required factory images with fastboot.
AND IT WORKS. No problem. It boots. I go through the initial set-up. I can let it restore all my apps and passwords from the google servers, etc. So far so good.
My problem is that I cannot root. After I try, it bootloops (stuck at the Google splash, with my unlocked icon).
I tried to root before my first boot. I tried after the initial boot (before set-up and signing in). I tried rooting after setting it all up, and singing in, and letting google restore all of my apps. No matter which sequence I try, it will reboot a couple times at the first Google splash, and then fall back to Recovery.
(So, I'm on back on my rooted 4.4.4 nandroid, I think it's Mahdi Rom-- I forget)
Vital Stats:
Trying to install factory images of 5.0.1, all stock (system, boot (kernel), radio, bootloader)
Factory reset
(the above works fine)
TWRP 2.8.1.0
SuperSU-v2.40 (flashed via recovery)
Any ideas? Thanks for any help.
No, but could you try the previous version of SuperSU? Just to rule out the new version that I haven't tested please?
I updated to 5.0.1 earlier
Flashed all the img files exact userdata and then booted in to Android.
I then flashed TWRP 2.8.1.0 and used that to flash SuperSU 2.37
All that worked fine.. I then did a play update and SuperSU updated to 2.40
All working fine as far as I can tell. Apps needing root are working!
iowabeakster said:
Hi all,
So I'm far from a noob at at all of this (doing the custom android thing for years). But I'm not exactly constantly fiddling with my phone all the time anymore either. Basically I get a set-up that works for me, and I stick with it.
I've patiently been waiting to update to Lollipop. And today I did it. I did it by flashing the required factory images with fastboot.
AND IT WORKS. No problem. It boots. I go through the initial set-up. I can let it restore all my apps and passwords from the google servers, etc. So far so good.
My problem is that I cannot root. After I try, it bootloops (stuck at the Google splash, with my unlocked icon).
I tried to root before my first boot. I tried after the initial boot (before set-up and signing in). I tried rooting after setting it all up, and singing in, and letting google restore all of my apps. No matter which sequence I try, it will reboot a couple times at the first Google splash, and then fall back to Recovery.
(So, I'm on back on my rooted 4.4.4 nandroid, I think it's Mahdi Rom-- I forget)
Vital Stats:
Trying to install factory images of 5.0.1, all stock (system, boot (kernel), radio, bootloader)
Factory reset
(the above works fine)
TWRP 2.8.1.0
SuperSU-v2.40 (flashed via recovery)
Any ideas? Thanks for any help.
Click to expand...
Click to collapse
Try not doing that? When you go through the initial configuration, choose "Set up as a new device". Maybe the restore is somehow corrupting SuperSU?
BirchBarlow said:
Try not doing that? When you go through the initial configuration, choose "Set up as a new device". Maybe the restore is somehow corrupting SuperSU?
Click to expand...
Click to collapse
It happens even if I try to root before setting anything up at all.
albert_htc,
Are you saying: I should also flash the stock recovery first. Then boot for the first time. Then re-flash TWRP. Then flash SuperSU.
I never flashed the stock recovery. TWRP was on already on it.
Thanks guys. I'll give it another rip (doing stock recovery, then flashing back to TWRP) sometime soon.
iowabeakster said:
It happens even if I try to root before setting anything up at all.
albert_htc,
Are you saying: I should also flash the stock recovery first. Then boot for the first time. Then re-flash TWRP. Then flash SuperSU.
I never flashed the stock recovery. TWRP was on already on it.
Thanks guys. I'll give it another rip (doing stock recovery, then flashing back to TWRP) sometime soon.
Click to expand...
Click to collapse
Yes, flash the factory image using the batch file so every partition gets re-flashed. Now I'm thinking maybe your recovery is corrupt.
Run flash-all.bat and when your device reboots, go through all of the initial configuration and download all of the Gapps updates. Once that's all completed, go ahead and route using TWRP. If you find yourself still having the same problem, try live booting TWRP to flash SuperSU.
BirchBarlow said:
Yes, flash the factory image using the batch file so every partition gets re-flashed. Now I'm thinking maybe your recovery is corrupt.
Run flash-all.bat and when your device reboots, go through all of the initial configuration and download all of the Gapps updates. Once that's all completed, go ahead and route using TWRP. If you find yourself still having the same problem, try live booting TWRP to flash SuperSU.
Click to expand...
Click to collapse
I'm not going to flash over my user data, nandroids, app back-ups, etc. I'll stay with kit kat forever on my nexus 5 before I do that. Version numbers aren't that important. Hours wasted getting things set-up again are.
My recovery works fine. Both on kit kat and lollipop. My only problem is a boot loop when I flash SuperSU (via TWRP), on lollipop. I will try flashing stock recovery, though and then reflashing TWRP.
iowabeakster said:
I'm not going to flash over my user data, nandroids, app back-ups, etc. I'll stay with kit kat forever on my nexus 5 before I do that. Version numbers aren't that important. Hours wasted getting things set-up again are.
My recovery works fine. Both on kit kat and lollipop. My only problem is a boot loop when I flash SuperSU (via TWRP), on lollipop. I will try flashing stock recovery, though and then reflashing TWRP.
Click to expand...
Click to collapse
It's a tedious process, but it really isn't all that hard to back everything up to a computer, and you can do it easily with fastboot and a single command line.
Or what I'd recommend doing is just booting up, backing up all folders to a PC and then resetting and restoring later, backup apps with Titanium Backup (what I always do). A lot of us flashed factory images when Lollipop came out, so it isn't that bad once you start on the road.
Have you tried rooting from the bootloader via Chainfire's cf-auto root? I know I've read that sometimes rooting from recovery doesn't work properly, and that only certain zips will work. I've used the auto root each time (from stock fastboot flashing 5.0 & 5.0.1) with lollipop and it works fine. Link
Unzip and run batch file in bootloader. It will wipe everything if you haven't already unlocked bootloader (fastboot oem unlock). If you are already unlocked it won't wipe anything.
snappycg1996 said:
It's a tedious process, but it really isn't all that hard to back everything up to a computer, and you can do it easily with fastboot and a single command line.
Or what I'd recommend doing is just booting up, backing up all folders to a PC and then resetting and restoring later, backup apps with Titanium Backup (what I always do). A lot of us flashed factory images when Lollipop came out, so it isn't that bad once you start on the road.
Click to expand...
Click to collapse
I just backed the /sdcard, to my PC. I just re-ran titanium.
I can deal with "/sdcard issues" from updating to lollipop easy enough. That's a 30 second fix. I can deal with setting up my email accounts to my email client app. I can deal with launcher settings, and all the other apps, widgets, etc. Those are things that I can slowly get back to where I want. They aren't critical. But yeah, very tedious.
I think "starting over" may be much more tedious for me than most people though. I run ssh servers and clients on all PCs, servers, and phones (disabling passwords and using rsa encryption keys for security). It's very nice, once I get it all set up in that I can access everything (from anything) very easily. I do need root for that though also.
But if I can't just hit a "restore" to get it all my ssh addresses, keys, fingerprits, etc back to where it was and then I have to: reverify new fingerprints, generate new keys, re-enable passwords to transmit new keys for everything, then disable passwords (for all machines) ... well... I just get very very grumpy.
anactoraaron said:
Have you tried rooting from the bootloader via Chainfire's cf-auto root? I know I've read that sometimes rooting from recovery doesn't work properly, and that only certain zips will work. I've used the auto root each time (from stock fastboot flashing 5.0 & 5.0.1) with lollipop and it works fine. Link
Unzip and run batch file in bootloader. It will wipe everything if you haven't already unlocked bootloader (fastboot oem unlock). If you are already unlocked it won't wipe anything.
Click to expand...
Click to collapse
I'll check that out. Thanks.
Yesterday I downloaded the TWRP app and attempted to update TWRP via the app. It said the process failed. Later on in the day I rebooted my phone and on reboot I am stuck at the White screen with the HTC logo.
My phone is s-off and I have been running stock verizon KitKat ROM that has been rooted. I have text messages with information I cant afford to lose. I was able to pull my photos off the device using a USB cable, and I am able to get into TWRP and browse the data on the device.
Is there anyway I can flash an RUU or ROM that will NOT DELETE any of the data on my phone so that I can get the phone to boot again?
Any help is appreciated.
Thanks in advance!
ljx2k said:
Yesterday I downloaded the TWRP app and attempted to update TWRP via the app. It said the process failed. Later on in the day I rebooted my phone and on reboot I am stuck at the White screen with the HTC logo.
My phone is s-off and I have been running stock verizon KitKat ROM that has been rooted. I have text messages with information I cant afford to lose. I was able to pull my photos off the device using a USB cable, and I am able to get into TWRP and browse the data on the device.
Is there anyway I can flash an RUU or ROM that will NOT DELETE any of the data on my phone so that I can get the phone to boot again?
Any help is appreciated.
Thanks in advance!
Click to expand...
Click to collapse
Make a nandroid backup, It may boot later on. I've only flashed twrp using adb so I don't have any insight on what you did. If at a last resort you can run an ruu (after you saved said nandroid to a PC) then after the ruu add the nandroid back to the phone and flash it and see if it boots.
Another thing is to use twrp file manager and see if you can get a file like this one that hold the messages database, I found in a quick Google Search. /data/data/com.android.providers.telephony/databases/mmssms.db
You may be able to re-add it back to a ROM after ruu? Honestly not too sure
Wish I had more info,
Best of luck.
ljx2k said:
Yesterday I downloaded the TWRP app and attempted to update TWRP via the app. It said the process failed. Later on in the day I rebooted my phone and on reboot I am stuck at the White screen with the HTC logo.
My phone is s-off and I have been running stock verizon KitKat ROM that has been rooted. I have text messages with information I cant afford to lose. I was able to pull my photos off the device using a USB cable, and I am able to get into TWRP and browse the data on the device.
Is there anyway I can flash an RUU or ROM that will NOT DELETE any of the data on my phone so that I can get the phone to boot again?
Any help is appreciated.
Thanks in advance!
Click to expand...
Click to collapse
I'd recommend making a backup in twrp. Then you can ruu back to stock KitKat, reflash twrp WITH FASTBOOT, make sure it boots, then restore the data partition only and see what you get.
cntryby429 said:
I'd recommend making a backup in twrp. Then you can ruu back to stock KitKat, reflash twrp WITH FASTBOOT, make sure it boots, then restore the data partition only and see what you get.
Click to expand...
Click to collapse
Thanks for the suggestions everyone. I did make a nandroid backup in TWRP just in case i needed it. I reached out to DOTTAT and he suggested flashing his Android 6.0 RUU he had in one of his posts that did not overwrite data and he sent me a link to the file.
I downloaded it and flashed it using adb in fastboot and sure enough that got my phone to boot and simultaneously upgraded me which I was planning on doing soon anyway. On boot I was no longer rooted but since the phone is S-OFF I just installed TWRP using adb and then installed SuperSU and all is good.
Once again thanks everyone for the help!
Any time I've tried to restore a backup it has completely bricked my phone. I tried just backing up the default options and restoring bricked, so when I had my phone rooted and setup perfectly with XXX no limits on Android 10 and all my apps installed, I made a FULL backup in case I bricked it with smurf kernel or something. Long story short, I ended up bricking it via other methods and tried to restore my full backup only to be completely bricked again. Not even recovery works after installing a backup. I've found that no matter what I backup, if I restore it it completely bricks my phone to the point where it only automatically boots into fastboot and I have to install a system image and start over every time. Am I doing something wrong or does TWRP 3.3.1-70 not support restoring yet?
jld2k6 said:
Any time I've tried to restore a backup it has completely bricked my phone. I tried just backing up the default options and restoring bricked, so when I had my phone rooted and setup perfectly with XXX no limits on Android 10 and all my apps installed, I made a FULL backup in case I bricked it with smurf kernel or something. Long story short, I ended up bricking it via other methods and tried to restore my full backup only to be completely bricked again. Not even recovery works after installing a backup. I've found that no matter what I backup, if I restore it it completely bricks my phone to the point where it only automatically boots into fastboot and I have to install a system image and start over every time. Am I doing something wrong or does TWRP 3.3.1-70 not support restoring yet?
Click to expand...
Click to collapse
Stop trying to restore the complete backup.
Flash the ROM and restore data only.
I don't see a point in backing up the ROM, when you can just as easily flash it then restore data.
tech_head said:
Stop trying to restore the complete backup.
Flash the ROM and restore data only.
I don't see a point in backing up the ROM, when you can just as easily flash it then restore data.
Click to expand...
Click to collapse
It's just a hassle because installing Android 10 factory image via fastboot fails every time. If I fiddle around and brick, I have to fastboot install Android pie, root it and install twrp, download Android 10, install it via local updater then flash magic to the other slot then reboot and install my xxx no limits module before I can restore my data. Compared to just getting TWRP up and running and restoring my backup I'm looking at a time consuming process to get to that point. I wish I knew why flashing Android 10 via fastboot bricks every time because that's a major cause of this headache while figuring out what does and doesn't work on Android 10. I already have titanium backup backing up nightly to Google drive so by the time I get to the point I can flash my data I might as well just restore my apps + data in TB. If I could get TWRP to successfully restore my backups I'd be given a lot of freedom to tinker around freely without worry of this time consuming restoration. I think next time I'm gonna try backing up into a flashable zip and seeing if I can successfully restore my image via fastboot when I inevitably brick again while messing around
tech_head said:
Stop trying to restore the complete backup.
Flash the ROM and restore data only.
I don't see a point in backing up the ROM, when you can just as easily flash it then restore data.
Click to expand...
Click to collapse
I haven't actually tried this. Are you talking about flashing the rom, and (within the same instance of TWRP), then restoring? Or are you talking about flashing the ROM, booting it, then going back into TWRP and restoring data?
just a quick question?? why are you always downgrading to a9?? when you can simply
1. flash a10 ( i save one on my PC in case a problem arises)
2. set up the phone
3. in pc, open a10 rom, locate for its boot.img amd store in phone
4. install magisk.apk and patch boot img , then copy to pc
5. install patched boot.img via fastboot
congrats,, back on track.. it only took me about 10-15 min to restore a bricked device up to being rooted and twrp installation
Hello,
This is my story:
I have my Mix 2S for few months for now and I have been trying many custom roms (Pixel Experience, LineageOS etc.). Today I wanted to restore backup with PE and then my problems begin.
Everything was fine until I rebooted, after that I could only boot into recovery. So I got into recovery and decided to format data. Data formatted without any problems, I copied by backup with all files from computer, wiped everything and then tried to restore PE. It couldn't restore data, so I decided to restore ROM only (I have lost clean zip, my connection is slow, so I have to download it for an hour (tomorrow I will try). Then I tried to reboot, the effect was similar but...
I can't get into my recovery because there is a password. I know my password because I set it by myself but I believe that restore was not fully fine.
I use OrangeFox recovery (10.3 if I remember good), my phone has an unlocked bootloader, I can get into fastboot but I can't flash anything because nothing happens. I tried to install driver for it but I don't see the difference.
I had a fingerprint set in system. I have the whole backup.
My phone version is 6/128.
I can't find anything, maybe stress makes me a fool.
EDIT
I found a solution, the whole problem was caused by Windows 10 feature that blocks files from the Internet. I had to unlock recovery file (TWRP) and now I can do anything with my phone.