Related
Okay, I did a ton of research on this, but when I flashed the ROM, I ended up with some major problems. I hope someone can help. Here's the deal:
Started with the stock ROM (Gingerbread 2.3.6), no overclocking
Backed up apps & data with Titanium Backup
Backed up contents of both internal and external SD card to my PC
Backed up phone to external SD card using CWM 6.0.1.2
Performed ROMwipe
Flashed odexed build, CM10_LINARO_20130118_ODEX_IRX120
Flashed DemonsBlood v8
Flashed Gapps
Rebooted
Now, the new ROM was working, but I started having trouble navigating and certain apps would force close, or I'd get messages that certain things had stopped working. Also, I could not figure out how to set up my home screens and wallpapers and settings and such the way I wanted. So I decided to go back to my stock ROM. But when I flashed my backup, the phone now acts as if it's been factory reset (although I can still boot back into CWM recovery). Also, when I download Titanium Backup, Facebook, and other apps, they force close upon launch.
I have wiped the ROM, fixed permissions, and tried again, with no success. I've copied the files I backed up to my PC back to the phone, but no joy there, either.
Ideally, I'd love to get my phone back to where it was before I attempted this - or, as a second choice, go forward and use the new ROM & Kernel, because I was pretty excited about trying it out. But I feel like I've lost a ton and now it's not working properly at all.
Can someone help me restore this? And tell me where I went wrong?
UPDATE: In CWM Recovery, I selected flash image from external SD card and selected CM10_LINARO_20130118_ODEX_IRX120, then rebooted. Now it gets stuck at the boot screen (Samsung Galaxy Exhibit 4G, Exclusively from T-Mobile). I tried booting into recovery, but no luck - same result, stuck at the boot screen. So I booted into HBOOT (vol down + power), got a warning about a custom ROM with a choice to reboot or proceed. Since I figured rebooting would just put me back at the boot screen, I chose to proceed. It is now showing the following:
ODIN MODE
PRODUCT NAME: SGH-T679
CUSTOM BINARY DOWNLOAD: NO
CURRENT KERNEL: SAMSUNG !!
Then there's the android icon and underneath it says:
Downloading...
Do not turn off target!!
Sigh. Help.
Okay, I got out of ODIN mode and managed to reboot into CWM recovery. Progress! I wiped the ROM, flashed CM10_LINARO_20130118_ODEX_IRX120, SpeedyGonzalez_OC_1.5.5, and Gapps, and rebooted.
So now I'm running CM10 Linaro, Odexed, with SGK. Okay. **deep breath** The first thing I see after the boot screen is "Welcome, choose your language" and then "Unfortunately, Google Search has stopped."
OK.
Signing in with Gmail . . . (screen does not auto-rotate at this point)
Contacting Google, then again "Unfortunately, Google Search has stopped."
Completed setup, then again "Unfortunately, Google Search has stopped."
Going to Play Store to get Titanium Backup. And a few more apps.
Auto-rotate now works.
Into Titanium Backup and I get this warning: "This device's Android ID has changed. This normally happens after a device replacement or factory reset. The Android ID is the most common way for apps to identify the device. Any app that relies on it for security/licensing purposes may stop working (or need to be reconfigured) unless you restore the previous Android ID now." with a choice: Keep the new one, or restore the old one (I only have the free version, so this choice is not available).
Should I get my apps back from Play Store or Titanium Backup or both? (I now know to restore the "app only" from Titanium Backup.)
I'm going to keep plugging away at this. Any suggestions for my next steps?
DarthJosef said:
Okay, I got out of ODIN mode and managed to reboot into CWM recovery. Progress! I wiped the ROM, flashed CM10_LINARO_20130118_ODEX_IRX120, SpeedyGonzalez_OC_1.5.5, and Gapps, and rebooted.
So now I'm running CM10 Linaro, Odexed, with SGK. Okay. **deep breath** The first thing I see after the boot screen is "Welcome, choose your language" and then "Unfortunately, Google Search has stopped."
OK.
Signing in with Gmail . . . (screen does not auto-rotate at this point)
Contacting Google, then again "Unfortunately, Google Search has stopped."
Completed setup, then again "Unfortunately, Google Search has stopped."
Going to Play Store to get Titanium Backup. And a few more apps.
Auto-rotate now works.
Into Titanium Backup and I get this warning: "This device's Android ID has changed. This normally happens after a device replacement or factory reset. The Android ID is the most common way for apps to identify the device. Any app that relies on it for security/licensing purposes may stop working (or need to be reconfigured) unless you restore the previous Android ID now." with a choice: Keep the new one, or restore the old one (I only have the free version, so this choice is not available).
Should I get my apps back from Play Store or Titanium Backup or both? (I now know to restore the "app only" from Titanium Backup.)
I'm going to keep plugging away at this. Any suggestions for my next steps?
Click to expand...
Click to collapse
i would suggest using TWRP recovery, backing up your internal, wipe cache 2x , wipe dalvik 2x , factory reset 2x, wipe rom 2x, and wipe internal 2x. then flash rom and gapps
Hi, I rooted my phone through jcase's guide and everything was fine. I wanted to reinstall the apps & data from my previous phone, so I went into Titantiam Backup Pro and clicked "Restore all missing apps + system data." I was following this guide:
lifehacker.com/5843206/how-to-upgrade-to-a-new-android-phone-and-take-everything-with-you
Surprisingly, I didn't need to transfer the backup from the sdcard of my old phone to my new phone. I tried but my computer wouldn't read the SD card. I was having a friend do it, but in the meantime I went to look at that option in my new phone and all my old apps and data were already ready to be restored. So I restored and everything was fine - I could play Candy Crush where I left off, etc.
So the guide and Titantiam Backup said a reboot is recommended and I haven't been able to get into my phone since doing that. It goes through the Moto X boot up screen and gets stuck at the blue Moto logo.
I've tried all the hardware reset uptions (Normal Powerup, Recovery, Factory) and the same thing happens and I get stuck at the same place.
Please can anyone give me some advice, I can give you any more info you may need.
Here's what the hard reset screen looks like when I load it: imgur.com/2XoGnvx
saltycoffee said:
Hi, I rooted my phone through jcase's guide and everything was fine. I wanted to reinstall the apps & data from my previous phone, so I went into Titantiam Backup Pro and clicked "Restore all missing apps + system data." I was following this guide:
lifehacker.com/5843206/how-to-upgrade-to-a-new-android-phone-and-take-everything-with-you
Surprisingly, I didn't need to transfer the backup from the sdcard of my old phone to my new phone. I tried but my computer wouldn't read the SD card. I was having a friend do it, but in the meantime I went to look at that option in my new phone and all my old apps and data were already ready to be restored. So I restored and everything was fine - I could play Candy Crush where I left off, etc.
So the guide and Titantiam Backup said a reboot is recommended and I haven't been able to get into my phone since doing that. It goes through the Moto X boot up screen and gets stuck at the blue Moto logo.
I've tried all the hardware reset uptions (Normal Powerup, Recovery, Factory) and the same thing happens and I get stuck at the same place.
Please can anyone give me some advice, I can give you any more info you may need.
Here's what the hard reset screen looks like when I load it: imgur.com/2XoGnvx
Click to expand...
Click to collapse
You might not be able to restore your data as its probably effecting the moto from booting. Try fastboot erase userdata , this will erase your phone back to factory settings
Try to just install the apps and see how it goes, there's also moto migrate which I believe restores or moves your apps from old phone to the moto, haven't used it but worth a try
Sent on my Moto X
flashallthetime said:
You might not be able to restore your data as its probably effecting the moto from booting. Try fastboot erase userdata , this will erase your phone back to factory settings
Try to just install the apps and see how it goes, there's also moto migrate which I believe restores or moves your apps from old phone to the moto, haven't used it but worth a try
Sent on my Moto X
Click to expand...
Click to collapse
The problem is the data was restored, but then when I rebooted my phone it won't get past the load screen. I don't care about the data now but I can't connect with adb or fastboot cause my computer doesn't recognize my device.
edit: it's also worth noting this is a Republic Wireless Moto X so I don't have access to the ROM/bootloader
saltycoffee said:
The problem is the data was restored, but then when I rebooted my phone it won't get past the load screen. I don't care about the data now but I can't connect with adb or fastboot cause my computer doesn't recognize my device.
Click to expand...
Click to collapse
Make sure you have the latest drivers, are you using a windows 8 computer?
Sent from my A2109A using Tapatalk 4
flashallthetime said:
Make sure you have the latest drivers, are you using a windows 8 computer?
Sent from my A2109A using Tapatalk 4
Click to expand...
Click to collapse
Okay, sorry, you were right, fastboot erase userdata did the trick. I was just unfamiliar with how to use it (cmd line). My phone is back to factory now, but it's on again! Now time to re-root :laugh:
Thanks.
edit: nvm, still got root access!
You don't want to restore system data. That is why you soft bricked. You probably came from a different version of android. Only restore app data and I'd only do the apps you really need to restore rather than doing them all.
Sent from my XT1060 using Tapatalk
Reposting this here…
Hi, all!
My Samsung Galaxy Ace (S5830) running under a custom ROM The Ultimatum (I've been using this custom firmware for a few weeks now, with no real problems up until now), is bootlooping with no apparent reason. On a rare occasion, most apps on the phone stopped responding and would crash upon opening, and would require a restart before they worked again. Well this happened to me a few hours ago, so I decided to reboot my phone. After coming back to check my phone, I had found it was still booting. This has gone on for several hours now, and I've tried turning it on and off, removing batteries and everything. It's stuck in bootloop. I found this was odd, as I have had no dramas with the firmware I've been using. I have not made ANY recent changes to the phone whatsoever, so I can hardly believe it would be my fault.
Now, my question is; how do I fix this without wiping all data and installing a clean ROM? I have a lot of stuff in the internal storage I can't afford to lose, and it's really important to me. A full wipe of all data would not be ideal. I can access recovery mode.
I have tried a suggestion a user here made and made a nandroid backup, did a full wipe, reinstalled the ROM (which allowed me to get out of the bootloop) and then restored the data from the backup (which stuck me back in a bootloop). Still no idea and I really don't want to lose this data. If it's too much effort to fix the loop, is it possible to extract the data from the backups on a PC and manage to restore it to a clean wipe?
Thanks in advance!
Fixed my problem by doing a clean installation, and using Titanium Backup to extract the data from my nandroid backup. It was quite a simple solution, really. No idea why no one seemed to suggest it, though.
Oh well, my problem is solved.
I thought I had finally reached nirvana with this device thanks to the help of so many here. I had TWRP, root, defeated encryption, and a nicely running Android. I was even able to make TWRP backups of /data and /boot (to be precise, at one point - not sure when it was but I think after initial Android setup - I was able to make a much more complete TWRP backup with many partitions never shown again but that disappeared at some point).
So I went on with my transition from my old Note3 phone to this device. I spent all day yesterday moving TiBackups of user apps, copying across data, making more limited TWRP backups (of data and boot the only options - except if I mounted system_root, which allowed me to include /system but that did not actually work either), polishing settings, and thinking I had it made! Throughout all of this I had no problems or signs of problems other than some apps not working on the new device and having to be replaced with alternatives which I completely expected.
At cocktail hour I decided to do a reboot to see the "finished product" of all this effort. When I did, the device tried to boot into Android: I saw the thinq logo but no boot animation, just the thinq logo for a very long time - followed by a screen blank and bootloop. I was able to enter TWRP and things looked "normal" from there. I kept trying to boot into system with no progress. I tried wiping /data, I tried restoring the backups I had made. Nothing changed - still bootlooping.
From within TWRP I can use adb shell to look around. I can see familiar stuff from my installed apps in /data/data and /data/app - including from one of the very last apps I installed (from Play not via TiBackup). I know this was not in any TWRP backup I had taken or restored. So this makes me think that my attempts to restore /data from backups or even wiping /data from TWRP have had no effect despite no errors showing. I wanted to see what was in /system so I mounted system and now in adb shell I can see familiar stuff in there too - including busybox installed into xbin. I can also mount vendor and in /vendor/etc I can see the fstab.judypn with encryptable for /data.
One thing I do NOT see is the result of one of the last things I did/tested. I installed Termux, installed the dropbear package, and copied the resulting dbclient binary to /data/local. After doing this I actually invoked /data/local/dbclient with success. Now, I do not see anything in /data/data/com.termux/files/usr related to dropbear nor do I see the dbclient in /data/local.
When I tried to power off from TWRP, the device never fully turned off. The animation showing the power level remained showing all the time but it was just a circle with lightening bolt but no actual power level showing. Removing power cable made no difference. Finally, I left the device in TWRP and powered on. At least I could blank the screen and prevent the battery from running dry.
All of this is with slot A current as reported by TWRP. I cannot seem to enter fastboot mode (I was previously able to do this from a power off condition by holding volume up and inserting USB). Of course, I am not able to achieve a real powered-off condition. Thankfully, I am still able to enter engineering mode and see the device in QFIL. But I have not tried anything here as of now. I can switch to slot b and get into download mode by holding power up and inserting USB. All attempts to use other TWRP boot options (save recovery and "power off") just put me into bootloop again.
I am stumped as to what is happening, how to "fix" this, or what to do.
Thanks for any suggestions.
Same thing happened to me. Yesterday.
I was going through my system programs, and nuked several of the extra Google Play items (Movies, Music, etc.). Same thing. Boot to V40 ThinkQ screen. Sat there for a while. Then reboot.
Nothing I did brought the old girl back to life. So I started over with kdz and redid everything again. Pain in the ass, but it's working again. Interestingly enough, loading the full kdz didn't relock the bootloader. I used both Refurbish and Partition DL on two separate attempts. Bootloader stayed unlocked throughout, and is still unlocked.
Had a devil of a time getting system to mount. Tried over and over again to get Magisk installed.
What finally worked was rebooting into recovery after pushing the .magisk file, and only then installing Magisk.
[NG]Owner
NGOwner said:
Same thing happened to me. Yesterday.
I was going through my system programs, and nuked several of the extra Google Play items (Movies, Music, etc.). Same thing. Boot to V40 ThinkQ screen. Sat there for a while. Then reboot.
Nothing I did brought the old girl back to life. So I started over with kdz and redid everything again. Pain in the ass, but it's working again. Interestingly enough, loading the full kdz didn't relock the bootloader. I used both Refurbish and Partition DL on two separate attempts. Bootloader stayed unlocked throughout, and is still unlocked.
Had a devil of a time getting system to mount. Tried over and over again to get Magisk installed.
What finally worked was rebooting into recovery after pushing the .magisk file, and only then installing Magisk.
[NG]Owner
Click to expand...
Click to collapse
Well, they say misery loves company and I do feel a bit better just knowing I am not alone here.
Since I could enter download mode, I too decided to try re-flashing the .kdz using LGUP's partition dl and specifically NOT checking boot_a, laf_a or boot_b as described here <https://forum.xda-developers.com/showpost.php?p=82206107&postcount=115>. I was not fast enough to get into TWRP on the automatic reboot and saw that I was brought to a bootable system and an Android start page with the boot loader still locked and TWRP still there.
So did the partition dl again and managed to catch TWRP. I mounted vendor but when I tried to push the fstab I got something I have not seen before "remote could not create file: Read-only file system" and 0 files pushed. To be sure, I used adb shell and cat'ed /vendor/etc/fstab.judypn and it contains force encrypt. So I know things are not quite right.
Trying again from the partition dl. And this time I managed the push. I think I missed re-doing the ramdisk and rebooting into recovery. I made sure to do that this time and now I can proceed. I seem to have managed to get back to a bootable Android with TWRP, Magisk, and defeated encryption once again.
So I wonder if I should try to restore anything from a backup or just redo all of yesterday's efforts (like the movie Groundhog Day)?
Can I ask which device and firmware you are using? Thanks
I would not use any backups aside from the backups in your google account. Redo all of yesterday's efforts (except the one thing that caused the reboot loop ... whatever that was!).
You said your bootloader was relocked after LGUP? Or did you mistype there?
Odd. Mine wasn't, not once. Despite multiple LGUP loads.
I've got a crossflashed Sprint LM-V405UA to US specs 20E.
And yes, misery does love company!
[NG]Owner
NGOwner said:
I would not use any backups aside from the backups in your google account. Redo all of yesterday's efforts (except the one thing that caused the reboot loop ... whatever that was!).
You said your bootloader was relocked after LGUP? Or did you mistype there?
Odd. Mine wasn't, not once. Despite multiple LGUP loads.
I've got a crossflashed Sprint LM-V405UA to US specs 20E.
And yes, misery does love company!
[NG]Owner
Click to expand...
Click to collapse
No, you are correct - I mistyped. My bootloader has remained unlocked (this time I got it right)
Nor sure it matters any, but mine if a 405QA with 20E.
I have read some recently (while searching for this bootloop problem) that LG seems to have long had a problem with bootloops on their devices. Not sure I saw anything specifically about the V40 though. Seems that in the past they were "fixed" with software updates. I do not expect any updates beyond 20E and wonder if 20a (which I think I had earlier) would be any different/better.
I have had great luck with Nandroid and TWRP backups in the past. They have really saved me (most often from myself but also from apps/mods gone wild). Indeed, I used TWRP restore yesterday with the previous night's auto-made backup on my Note 3. It seems that in doing something - maybe the TiBackup of all user apps/data - the phone got messed up and even reboots would not fix it. The TWRP restore certainly did!
I am new to the whole Magisk "systemless" root as I have always used SuperSu before. As I understand it (which is limited for sure) the idea here is to NOT modify system in any way. But I also note that this does not seem to preclude me from modifying things in system using my file manager, for example. And I did some of this sort of thing. If you are nuking pre-installed apps, that would be changing system as well, no? I wonder if that is the activity that caused this?
I am a bit hesitant to re-live yesterday. At least not until I have some idea of what I did that caused this. Not sure what I will do.
Thanks for all the help.
PS - given that I had TWRP backup (of at least /data) and how often I rely upon these in everyday life, I decided to at least try restoring and see what happened. Hard to imagine ending up worse that I was earlier this morning. I did the restore and rebooted to system. I was shocked, quite frankly, to see the system come right up and have many of my previously installed apps visible and working. I did find that I had to re-enable the modules in EdXposed (even though they showed as enabled already) since they were not working) and that brought them back to life.
So I guess I can move forward from here being careful, taking TWRP backups even more often, and rebooting more often to see what, if anything, kills this again.
NGOwner said:
Same thing happened to me. Yesterday.
I was going through my system programs, and nuked several of the extra Google Play items (Movies, Music, etc.). Same thing. Boot to V40 ThinkQ screen. Sat there for a while. Then reboot.
Nothing I did brought the old girl back to life. So I started over with kdz and redid everything again. Pain in the ass, but it's working again. Interestingly enough, loading the full kdz didn't relock the bootloader. I used both Refurbish and Partition DL on two separate attempts. Bootloader stayed unlocked throughout, and is still unlocked.
Had a devil of a time getting system to mount. Tried over and over again to get Magisk installed.
What finally worked was rebooting into recovery after pushing the .magisk file, and only then installing Magisk.
[NG]Owner
Click to expand...
Click to collapse
Well, this happened to me once again. I saw no reason why it should not do so. So I have been re-introducing apps from my TiBackup slowly and in under a strict protocol in an effort to (a) limit the damage done to my work and (b) try to isolate the culprit(s). I decided, since I found that I could restore TWRP backups of /data after re-doing the most of the TWRP install and defeat encryption process, that I would install apps slowly and execute them and in small groups. After each group I would do a reboot to see if that worked. If that worked, I would go into TWRP, run a backup, and name the backup of /data with something to id the app group that was added and seemed fine.
I started working backwards by the first letter of the app name. I first did U-Z and found that worked fine. Took a backup and went on to S-T. After this group it was bootloop time! So I put humpty-dumpty back together, restored the /data backup from U-Z, and this time installed only those apps starting with T. After this a no-problem reboot and a backup of /data and I will continue to plod on with those apps starting with S (and so on).
Horribly tedious. I can see no other way to proceed unless someone has a better idea.
PS - So I re-installed apps starting with S and basically had no problems. Hmmm. But I do recall that when testing execution of some of these apps the first time around, I decided to install busybox (Stericson), AdAway, and Afwall+ out of sequence. Before I did this I decided to check a bit more. I found that there is a Magisk busybox module and even though I have always used Stericson without troubles, I thought it best to use the Magisk module for this. I also found that Magisk has a setting for systemless hosts which could be affected by AdAway. So I enabled that before doing anything with AdAway. I also checked to see if AfWall+ might have any issues and found none. So I guess it is possible that using Stericson busybox or failing to use systemless hosts could have been an issue. I may never know for sure but at least so far I am fine after installing apps that I previously installed and had a bootloop. So FYI.
Alright, I'm a total idiot. I went and did this again, following the mantra: If it aint broke, you're not trying hard enough.
Setting all that aside, I went and tried to do some more debloating of my v40 (used this guide, that I was linked to from here), and wound up in "this fresh hell" again. Dammit! Crap.
So apparently there is a system application that is crucial to the boot of the phone that I uninstalled.
There is a fix to this, but it comes at a cost. Get into TWRP. Navigate to advanced, select Fix Recovery Reboot. Your phone will boot normally now. But you will lose root. And (so far) any attempt to reinstall Magisk to re-obtain root will result in the same bootloop again.
So here's where I need some help:
1) So if I wanted to reinstall my system partition to get back to stock from a KDZ, but still keep my installed apps, etc., how do I do that?
2) How do I get my Slot B to work correctly? It has only bootlooped there. Since I got my phone. Once I get my phone back to operational state with root, how do I make sure that Slot B works (so I have a backup I can fall back on if (when) I bork something else?
[NG]Owner
Hello everyone, I'm new to this platform, hope you guys will bear with my limited knowledge and help me out.
So, I have a Moto E4 plus device which was working fine, until one day, I used up its entire battery and it switched off. I took it and put it on charging, not knowing what was about to happen. When the battery was charged to 70% or something, I started the phone and unlocked it, but in like 10 seconds, it restarted automatically. I didn't download anything, never rooted the device, it was in original condition. Now, the phone is stuck in restart loop. Every time I restart the device, it works for 5 seconds, and then it goes in a loop of restarting again and again. I went to the recovery mode, backup up all the internal data in an SD card. The backup shows 13 files of 2GB each with an extension ".backup". I don't know how to access them.
Then, I did a hard reset and it worked just fine with no issues at all. Now, I need those files as they are very important for me, considering they have the last memories of someone I lost (not playing the emotional card, I hope you might feel the depth of the situation). Can anyone please help with accessing these files?
1. I did restore the files from recovery mode from that SD card, but the same issue reappears again.
2. I have all the 13 files copied with me in my PC
3. I tried wiping cache partition, it doesn't work
Need one of the two solutions
A. How to access these backup files, considering they are 13 files of 2 GB each with ".backup" extension
B. Accessing the files in recovery mode (the phone gives only a 5 seconds window which is eaten up in unlocking the screen)
Kindly give a solution which a layman can understand , hope you understand.
PS, I never even turned the developer's option on & the data is important, not the phone
Thank you!
deadmanspeaks said:
Hello everyone, I'm new to this platform, hope you guys will bear with my limited knowledge and help me out.
So, I have a Moto E4 plus device which was working fine, until one day, I used up its entire battery and it switched off. I took it and put it on charging, not knowing what was about to happen. When the battery was charged to 70% or something, I started the phone and unlocked it, but in like 10 seconds, it restarted automatically. I didn't download anything, never rooted the device, it was in original condition. Now, the phone is stuck in restart loop. Every time I restart the device, it works for 5 seconds, and then it goes in a loop of restarting again and again. I went to the recovery mode, backup up all the internal data in an SD card. The backup shows 13 files of 2GB each with an extension ".backup". I don't know how to access them.
Then, I did a hard reset and it worked just fine with no issues at all. Now, I need those files as they are very important for me, considering they have the last memories of someone I lost (not playing the emotional card, I hope you might feel the depth of the situation). Can anyone please help with accessing these files?
1. I did restore the files from recovery mode from that SD card, but the same issue reappears again.
2. I have all the 13 files copied with me in my PC
3. I tried wiping cache partition, it doesn't work
Need one of the two solutions
A. How to access these backup files, considering they are 13 files of 2 GB each with ".backup" extension
B. Accessing the files in recovery mode (the phone gives only a 5 seconds window which is eaten up in unlocking the screen)
Kindly give a solution which a layman can understand , hope you understand.
PS, I never even turned the developer's option on & the data is important, not the phone
Thank you!
Click to expand...
Click to collapse
Most likely that they are only usable to recovery that they were created with.
Was this Twrp? or stock recovery?
sd_shadow said:
Most likely that they are only usable to recovery that they were created with.
Was this Twrp? or stock recovery?
Click to expand...
Click to collapse
It was stock recovery, but I have my phone accessible in that state also. Is there any possibility to create a custom backup without actually booting up the phone or accessing those stock recovery files?