This is my wifes phone, who has always refused to have her phone altered in any way. Today, it started getting hung on the yellow sprint screen. A couple of times, another reboot would get past it. But now it's stuck for good.
She has some pics and thousands of contacts and SMS messages on it that she doesn't want to loose, so kind of afraid to do a factory reset or odin a fresh ROM. I don't know if she allowed it to take the latest firmware updates, so I don't know for sure what version is on it.
Can I odin CWM or TWRP only so that I can do a nandroid backup?
Once I know all the data is backed up, I can try the factory reset and/or odin rooted stock rom and use titanium backup to restore data.
Thanks
I don't know the answer but in my head I'd think you would have to have a working rom to back up in the first place. Maybe she ran out of memory? Flashing the stock Rom won't delete anything. Just did that a few days ago.
I went ahead and flashed CWM and did a nandroid backup. I used my other phone to look at the backup with Titanium Backup.
It looks like I will be able restore contacts and other apps/data. Not sure which item in the backup is for SMS history. In TB, I see a line that says "Messaging" and "Messaging+" and i don't see "com.adroid.providers.telephone".
I know the SMS's are in the backup, I extracted the tars in linux and see the folder /data/data/com.android.providers.telephony/
Used odin to flash the pre-rooted OD2 lollipop. It stayed on the yellow screen for several minutes, but I did notice that it played the full boot tune, which it hadn't been before. After a few minutes, it finished booting and started the setup wizard!
Related
So I tried to restore my previous ROM after giving another a try and it all fails. I wiped data/delvik/swap and then restored to the latest stored image. Phone starts to boot and then just freezes. I let it sit for about 8-10 minutes (phone usually takes a minute at most to boot) and then just did a hard reset by taking the battery out. I thought maybe the last file was corrupt so I removed the latest image and restored an older one. STILL no go. Freeze right at the second splash screen. Did I do something wrong? I have done this before and it worked fine. Im lost.
Hmmm anyone have an answer to this?
what rom is it and is the phone rooted?
The phone is Rooted and at that time I was on Kings Eris 2.1 sense ROM. Do you need a special ROM?
Problem I am trying to solve: As soon as the device boots I get the notification "preparing network" and when I try to dial a number on the stock ROM and get "Mobile Network not available"
A Nandroid restore CM11 appears to connect to the mobile network (I can dial a number but get "your account could not be validated" because the device has not been successfully activated on the network yet)
Here is how I arrived at such a dilemma.
okay, I am gonna try to format this in a way where you can skip some sections that might be a little "ranty" while still making it informational while still requesting some assistance.
A little background (feel free to skip this part) I have been rooting and ROMing phones for a few years to support my Cyanogenmod fix. I buy my phones on eBay or Craigslist, and verify I can setup a recovery, then backup the rooted Stock ROM (to activate the device and update PRL, etc.) then install the CM version of my desire and transfer over all my settings and backup files and restore them so I have had the same look and feel for the operating system of my phone for the last few years. I am on TIng (a Sprint MVNO) and have had zero problems performing these hardware upgrades from my droid, to my galaxy nexus to my second galaxy nexus, to my galaxy S3 to my second Galaxy S3 on a regular basis using their website.
Last Friday, I picked up a Galaxy S4 (running NAE) at the local Sprint store and once verified by the Sprint employee as being a clean ESN, I was set to start my process of rooting, installing recovery (I chose TWRP), then Nandroid backup of the stock ROM, then install CM 11 M6 and copy over my backup files (Titanium Backup) from my S3 and restore them, then Nandroid backup of the CM 11 install, then restore of Stock NAE ROM to activate the phone. Here is where things get a little fishy.
For awhile now, I had been always used Clockwork in the past but several comparisons score TWRP a little higher for features and functionality so I decided to use that for my recovery. It installed CM just fine and it seemed to perform Nandroid backups without any problems (or so I thought). I attempted to restore my Nandroid Stock ROM to activate the device and upon boot I saw the familiar Cyanogenmod screen. I tried it again, but same thing. No big deal, I'll find a stock rooted NAE ROM, copy it to the SD card, install using TWRP, activate, Nandroid backup, then restore my CM Nandroid backup and be up and running. I installed the Stock Rooted NAE ROM using Odin and lose my TWRP recovery so I reinstall TWRP and make a Nandroid backup of the Stock Rooted NAE ROM using TWRP. I make sure my TWRP restore can restore my CM11 Nandroid backup and it does. Okay, I should be all set. I have a nandroid backup of stock and CM11. All I need to do is restore stock, activate and I am up. I attempted to restore my Nandroid Stock ROM backup to activate the device and upon boot I saw the familiar Cyanogenmod screen for the second time. At this point, I am a little frazzled as logically this has never happened in the history of all the devices I have worked with.
I start checking the forums to see if anyone has experienced this and see nothing. I see many "how-to" guides that cover all kinds of things for the Spring GS4 that include wiping the data and cache multiple times over and over using a recovery called PHILZ.
I abandon TWRP, restore Stock Rooted NAE ROM and as far as I can tell, I am ready to begin from scratch using PHILZ. Install PHILZ recovery, install CM 11 M6 and copy over my backup files (Titanium Backup) from my S3 and restore them, then Nandroid backup of the CM 11 install, then restore of Stock NAE ROM to activate the phone. This time I am able to successfully restore a Nandroid backup of Stock rooted ROM but I am seeing a little red x and zero bars for the mobile network connectivity.
I start checking the forums to see if anyone has experienced this and see a few people that have lost mobile network connectivity and claim loading a modem using Odin is the fix. I try NAE-Modem-Only.tar using Odin and that does not improve anything. I also try loading TriForceROM5.4 having read that any TW ROM can be used to access the menu to activate a device
Now I am stuck.
There is nothing I can do to get mobile network to work on a stock ROM. As soon as the device boots I get the notification "preparing network" and when I try to dial a number on the stock ROM and get "Mobile Network not available"
A Nandroid restore CM11 appears to connect to the mobile network (I can dial a number but get "your account could not be validated" because the device has not been successfully activated on the network yet).
this issue is resolved.
I followed the steps to "unroot / unbrick" my phone using multiple stock ROMS and finally, the stock ROM L720VPUFNAE_L720SPTFNAE_SPR performed a full reset on my device (all partitions). I wish I remembered the page that linked me to the download of that ROM but googling that name should provide you a few places to get it.
not sure if that helps anyone else but my appreciation to QBKING77 for his multiple "How-To" videos.
Hi all,
Some time ago i asked, and received, some support on these forums on how to properly carry out a nandroid backup... following the sound advice i got, i carried out my backup (using TWRP for the record, with all the options checked), and stored it away for a rainy day... said day came yesterday, when i messed up my system and rendered it instable (i tried to manually delete the dalvik cache directory in order to free up the 2,5GB of space it was taking)... since i knew there was i high chance of this ending in disaster, the last thing i did before the delete was carry out another nandroid, so i could easily return to where i had left off... how wrong i turned out to be
as soon as i the system became instable following my experiment of deleting the d. cache directory, i recovered the latest nandroid (i.e. the one i had made just hours before) and everything seemd to go smoothely until the first reboot... when the following happened:
- first reboot after recovery took ages, much like the first reboot following the flashing of a new rom... not the end of the world, but that was the first sign that all was not well
- the status bar disappeared, and there was no way of making it come back (i.e. nothing to do with the launcher, i typically use apex but i i tried switching to both nova and touchwiz which i also kept up to date but the stats bar was nowhere to be seen)
- even if not having a status bar with all the info on it is acceptable (which of course it isn't, but lets just say), the sytem became completely instable after 5minutes of operation... with each app taking turns to shutting down until i kept getting the message "system UI has closed" over and over, to the point that doing a reboot was challenging since i barely had the time to press on the screen between instances of this bloody error message appearing...
...i did of course try and return to my older nandroid backup, but... lo and behold... exactly same behaviour...
so now i have resorted to formatting the internal memory card and flashing a new rom and basically starting over... just what i hope the nandroid would spare me basically :/
question is: does this sort of error sound familiar to anyone? can someone give me a tip maybe on what i may have done wrong?
any opinion, tips& advice much appreciated
I have the exact same problem. It happens on TW Lollipop ROMs. Haven't found a fix. I'm using Philz Touch Recovery and the old no knox bootloader.
Anyone? I have researched this but cannot find any similar problems reported... it can't just be me and pavelcheto...
Maybe it a recovery fault. Faulty backup or faulty restore.
No problems with my older backups. I restored my KitKat TW backup, working fine. Restoring CM12 backups also works fine. I've looked for a new recovery, Philz is discontinued, CWM hasn't been updated for a year and I really don't like TWRP.
I use TWRP 2.8.3.0 and never have (and hopefully never will) encountered any issues with restoring backups.
Considering i recovered 2 separate backups for a total of 3 times (i tried recovering the first backup twice) i doubt the issue was with the recovery itself... however since pavelcheto had no issues with the kk recovery maybe it could be lollipop related?
Anyone successfully recovered a lollipop nandroid backup?
platypus78 said:
Considering i recovered 2 separate backups for a total of 3 times (i tried recovering the first backup twice) i doubt the issue was with the recovery itself... however since pavelcheto had no issues with the kk recovery maybe it could be lollipop related?
Anyone successfully recovered a lollipop nandroid backup?
Click to expand...
Click to collapse
I recovered my lollipop gpe backup a couple of times without a problem.
Data encryption may cause restoring problems.
I have restored CM12 backups (based on 5.0.2) serveral times, no problem there. I've had issues only with TouchWiz Lollipop ROMs, I have tried different custom roms, all get bugged at restore.
pavelcheto said:
I have tried different custom roms, all get bugged at restore.
Click to expand...
Click to collapse
Just to make sure I understand correctly : you mean all TW custom roms you've restored have had problems?
Wonder if anyone else has managed a bug-free restore of a 5.x TW?
Yes, but only on Lollipop. KitKat TW roms restore just fine. I am using Philz Touch Recovery. I have tried 3 different TW Lollipop roms and they all fail to restore properly. No wallpaper, black wallpaper and no status bar. And after a minute or two System UI starts crashing. If then I do factory reset from recovery and the rom starts normally (welcome guide and stuff) and works fine.
bumping this thread because i cant seem to find a solution for this anywhere.
TheAwesomeBit said:
bumping this thread because i cant seem to find a solution for this anywhere.
Click to expand...
Click to collapse
There's no solution for this as per comments above. TW LP is not restorable. You can flash a new lollipop ROM tho'
Sent from my GT-I9505
Help! I'm trying to upgrade my wife's 9505 and I'm stuck.
She was running Stock (rooted) kit-kat, and I went to upgrade her to CM12.1
First, being a good boy, I took both a TiBu backup and a nandroid backup.
I did then manage to upgrade to CM12.1, but found a few issues (some missing phone numbers, etc that weren't sync'd with google), so I took a nandroid of CM12.1, wiped, and then restored the stock kit-kat nandroid.
That kinda worked, but some things are playing up - Waze doesn't work, SwiftKey comes up with an error trying to save the language file, the Daily Mail app and Gallary don't show any pictures, etc. Basically, not very usable.
So, I copied off the missing phone numbers, etc. and then thought that I'd wipe and restore the CM12.1 nandroid to get back to where I wanted to be - but it's just stuck at the CM12.1 animated boot logo and has been for ages.
So, I can't go back to kit kat, and I can't get back to CM12.1
Any suggestions/ideas?
It smells like some kind of file-system protection issue type thingy, but I tried the usual Fix Permissions, etc - all to no avail.
Someone please help (I'm really in the dog-house at the moment!!)
Thanks
Sorted! I had to basically wipe everything! Data, Media/photos, the works. Something really got screwed up, but I think I've got it going again now...
I have a Samsung s8 snapdragon 950U, T-mobile, running android 7.0, baseband - G950USQU2BQK5, build - nrd90m.G950USQS2BQL1. A couple weeks ago the mic stopped working so that I could not use speech-to-text which I rely on heavily. Nothing fixed it until I reflashed the phone with the same firmware. Before that I performed a ROM backup using clockworkmod and moved the backup files to my computer. I also used Titanium to backup system data like sms messages. After that, just as I was going to restore data, I get TMobile message that I’ve never seen before about a firmware update. I figured if it’s Oreo the update would fail because I have a custom ROM. Stupidly I chose to update and the next thing I know I have Android 8 – NOT rooted. That prevented me from using Titanium to restore settings.
Stupidly again, I decided to go back to the android 7 firmware and proceeded to root and flash the phone as I did before. This time it failed. I tried the SAMPWN and SAMFAIL methods repeatedly without success. Now I have bricked phone that just loops through a screen that says “Installing system update” followed immediately by another blue screen with a defunct android that says “no command.” I can get to download mode which Odin sees, but not to recovery, or anything that Smart Switch(which isn’t so smart) sees.
I have been downloading the Oreo firmware G950USQU4CRE9_G950UOYN4CRE9 for the past 4 hours hoping that I can maybe flash that. HELP! Can I somehow restore the nandroid backup using my computer? What should I do. I just need a working phone or I’m in big trouble.
frankygoes said:
I have a Samsung s8 snapdragon 950U, T-mobile, running android 7.0, baseband - G950USQU2BQK5, build - nrd90m.G950USQS2BQL1. A couple weeks ago the mic stopped working so that I could not use speech-to-text which I rely on heavily. Nothing fixed it until I reflashed the phone with the same firmware. Before that I performed a ROM backup using clockworkmod and moved the backup files to my computer. I also used Titanium to backup system data like sms messages. After that, just as I was going to restore data, I get TMobile message that I’ve never seen before about a firmware update. I figured if it’s Oreo the update would fail because I have a custom ROM. Stupidly I chose to update and the next thing I know I have Android 8 – NOT rooted. That prevented me from using Titanium to restore settings.
Stupidly again, I decided to go back to the android 7 firmware and proceeded to root and flash the phone as I did before. This time it failed. I tried the SAMPWN and SAMFAIL methods repeatedly without success. Now I have bricked phone that just loops through a screen that says “Installing system update” followed immediately by another blue screen with a defunct android that says “no command.” I can get to download mode which Odin sees, but not to recovery, or anything that Smart Switch(which isn’t so smart) sees.
I have been downloading the Oreo firmware G950USQU4CRE9_G950UOYN4CRE9 for the past 4 hours hoping that I can maybe flash that. HELP! Can I somehow restore the nandroid backup using my computer? What should I do. I just need a working phone or I’m in big trouble.
Click to expand...
Click to collapse
update: i was able to flash the oreo firmware basically puts me back at step 2. becasue i backed up when rooted my backups now cannot be restored, or can they, at least in part? Is there any way i can restore some of the data in either the nandroid or titanium backups to my nonrooted oreo s8?