Database Info

CM9 constant reboot. Help restore phone

I followed the instructions exactly on this page: http://forum.xda-developers.com/showthread.php?t=1663169
CM9 seemed to work fine for a while. I installed Titanium Backup and brought back my apps and just a bit of system data (contacts, voicemail, texts, etc). After I had restored those things, it said it suggested a reboot. I did that, but now it just reboots over and over. I can't get in to the OS for more than a few seconds before it reboots again. Help please!
As that thread specifies, I have a MX2 from CSpire. For now I don't care so much about getting CM9 working as just getting my phone back to a working state. I have both a nandroid and titanium backup on the sd card. I just need very specific instructions on how to get back to the way it was (2.3.6) given that I can't get in to the OS.
Edit: Pulling the battery doesn't resolve anything

Does it let you stay in long enough to remove the app/settings you restored? Are you able to get into recovery mode at all?
If you can get into recovery you might first want to try Fix Permissions and see how that works. If this does not solve it then consider doing a factory wipe and start restoring your apps/settings again one by one and rebooting in between until you get to the particular one that started your reboot problem.
What ROM were you on prior to CM9? Although they should be largely universal sometimes there are some slight changes in custom ROMs that might work well in many other ROMs but not in a select few. Other times it is an app that is not compatible.
The post below might be of some help since your phone seems to have a different method of getting into recovery than what I have dealt with so far.
http://forum.xda-developers.com/member.php?u=4395758

Factory Restore DX2
This might help. It's a factory restore, like you just bought it. http://forum.xda-developers.com/showthread.php?t=1317707

After much sweat, tears, and button pressing, I have gotten it back to stock CM9 and it seems to be behaving as expected. I am going to install apps one by one and reboot between every install. Hopefully I'll find the culprit soon enough.

Dropping data and no calls/texts. Advice please.

Just in case this post gets moved, I want to identify my device as the Verizon Samsung Galaxy S3 (i535).
To give a little background on my issue, I have an issue with the device. When I first got it back in July, first thing I did was root the device. Naturally, since it was a new device, I was working with experimental methods... a couple weeks ago I thought to download CyanogenMod 10.1 (nightly build) to flash it with 4.2 and rid myself of the persistent OTA update that as we all know could not effectively install because of the measures I took to root. So, I boot into recovery and flash my custom rom. BAM! As it turns out, I did not have an unlocked bootloader and my phone was now teetering on the verge of being a $600 paperweight. I got that dumb yellow triangle saying unofficial firmware detected or some nonsense like that... Anyway, I look around the internet and decided that I was going to revert back to a stock rom using Odin, and then proceed to unlock my bootloader and root the device (I followed method 3 here) I used some touch recovery console that I have never heard of before (backups incompatible with ClockworkMod recovery) and something must have failed because my back up would not flash. I took the hit on losing most everything and reflashed successfully the custom rom mentioned earlier.
After about a week, I noticed the device began to drop data. 4G would just stop at random parts of the day, and I would have to disable and enable the data to get it to reconnect. At this point I was still able to make and receive phone calls and texts. After about 3 days of this, I concluded it was more than likely a bug in the custom rom, and that I could not live with it... so I redid the a fore mentioned tutorial and left the phone as a stock/unlocked/rooted device. The data issue continued, but with a twist. I was now unable to make or receive phone calls or texts. No matter what I did, I could not do anything and the 4G would only stay connected for a matter 5 minutes or so. When I logged into my vzw account, it identified my device as an unknown non-verizon device. Customer service walked me through various soft/hard reset techniques and nothing worked. They also suggested I try a new SIM card, which failed to work.
So, I turn to the bright minds of the android community. I have already decided not to invoke the Verizon warranty offered, where the result is they take my malfunctioning phone in flawless cosmetic condition and replace it with a "like-new" phone in working condition, because I think it's garbage that a warranty would give out used crap (should fix or replace). I have not contacted Samsung customer support yet because I wanted to see what my options were. I've already attempted flashing different radios and nothing seem to make any difference. If I have to, I will revert it back to stock again and invoke Samsung's warranty program, but I would much rather keep the phone. As it sits, I am stuck with my Motorola Droid Razr Maxx, and that just doesn't cut it.
So I ask, is there anything that can be done? Anyone know of a fix for my situation? I saw something about this in my quest for an answer and I don't know if my situation is a fit for this fix. If anyone has any knowledge of my issue and a work around for it, it would be greatly appreciated. I am at my whits end.

It sounds like you've done your homework on your problem.. The only thing in your post I didn't see was your sim card.. Maybe pulling it wait 2min restart. Shut down and insert,, or maybe a reprovision of the sim may be in order..
Ahaaaa....!!!

If your IMEI is intact, I would say to flash to ICS and reprovision the phone as suggested above. If it is not, you need to restore it with that backup that you made some time ago.
If it were me, I would reprovision, that is easy to do and I honestly think that it will work for you. If that works for you, reroot and restore your backup for TW ROM and you will be fine.

HHF2 said:
If your IMEI is intact, I would say to flash to ICS and reprovision the phone as suggested above. If it is not, you need to restore it with that backup that you made some time ago.
If it were me, I would reprovision, that is easy to do and I honestly think that it will work for you. If that works for you, reroot and restore your backup for TW ROM and you will be fine.
Click to expand...
Click to collapse
Well that's just it... I don't know anything about the IMEI and how to determine if that is the issue. If by reprovision you mean reflash back to stock, that is it's current state, and that did not resolve the issue.
As for the other comment in regards to the SIM card... I have already attempted that method, and it did not work. Also, a new SIM card was also tried, and had no success.

mkruluts said:
Well that's just it... I don't know anything about the IMEI and how to determine if that is the issue. If by reprovision you mean reflash back to stock, that is it's current state, and that did not resolve the issue.
As for the other comment in regards to the SIM card... I have already attempted that method, and it did not work. Also, a new SIM card was also tried, and had no success.
Click to expand...
Click to collapse
Google reprovision, it is a number combination that you enter on the keypad that resets your phone. I had a similar problem that you are having and that fixed our for me. You also need to know that when you do this, it will erase all of your information on the phone. It will be just like it was when you unpacked it and powered it on the first time.
You will have to be on ICS because they removed the option to do this with JB. Just search for the code to enter and you will be fine.

HHF2 said:
Google reprovision, it is a number combination that you enter on the keypad that resets your phone. I had a similar problem that you are having and that fixed our for me. You also need to know that when you do this, it will erase all of your information on the phone. It will be just like it was when you unpacked it and powered it on the first time.
You will have to be on ICS because they removed the option to do this with JB. Just search for the code to enter and you will be fine.
Click to expand...
Click to collapse
Ok. So I tried the reprovsioning mentioned above. When my phone rebooted I was on data and able to make phone calls. Score! However, I checked the IMEI and it said 0. So, thinking that it was just a matter of time before my device began to stop working again... I did the IMEI fix. Now my phone is placing calls and holding data without issue. The OTA updates are flooding in and installing without issues.
I would like to point out, while I feel better having done the combination of both reprovisioning and IMEI fix, ultimately the initial reprovisioning did appear to resolve the issue.
Thanks to everyone for the assistance provided.

tf700 Major, strange problem after update!

Everyone help! I just updated my tf700 to the newest update which was supposed to be minor. Everything went smooth but upon boot up everything went wrong. Every single app force closes upon unlocking the lock screen. I get a pop up for just about every single app that's trying to start saying sorry the app has closed. Oddly, any app that was originally on the device works OK. I did a normal reboot and then again I saw the upgrading message and another message saying optimizing apps and it counts through the apps its optimizing. Then again when I reboot fully it does the same thing. I did a cold reboot and it seemed a little smoother but then again I had the same force closes and error messages. And still only the stock apps will function, anything and everything else force closes upon opening.
I've never even heard of errors or problems such as this. I have no idea what to do and I have lots of data on the device I don't want to lose and can't lose. By the way I am rooted and I did not uninstall any stock apps. Just froze a couple. Build # now 10.6.1.14.10-20130801
Please any and all suggestions!
Ps - under kernel version it says (concerned about name cancer):
3.1.10-gba9af5
[email protected] #1
Thu Aug 1 17:00:24 cst 2013

bobstone said:
Just froze a couple.
Click to expand...
Click to collapse
There's your problem...
Sorry mate, but I can't help myself - attention everyone, here comes a rant:
I cannot believe how many people do not backup the data on their tablets! This is the second time in as many days that I read: "Something unexpected went wrong and I cannot loose my data".
If you did not back it up the question is not if you loose it, the question is WHEN!
This is a portable device! Pre-destined to be lost, stolen, dropped, submerged, spilled upon, run over by trucks - and those are everyday scenarios which are LIKELY. Don't even want to get into freak accidents... It's so easy to protect your data now-a-days! There's Dropbox in conjunction with Dropsync, there's Google Drive and a host of other solutions. There is no excuse for having only one copy of important data...... End of rant
To your problem. Before you apply a stock update you have to replace/unfreeze all stock apps. Usually the update just fails if you have frozen system apps - I do not know what went wrong in your case.
How did you update? OTA or manually?
It sounds as if your data partition is corrupted since the stock apps (installed in /system) work, but your user apps (installed in /data) do not. But that your system apps work is the good news! At least you didn't brick your tablet.
One of the stock apps is the file browser. See if you can copy your precious data to a microSD. And I'm only talking about data like pictures, files, video, projects. Don't worry about your apps.
If the file browser cannot see your data you're gonna have to get into the area of data recovery tools - lots of research ahead of you there.....
Another possibility may be - if you can access your tablet from your PC through USB - to ADB pull files off your tablet, check if your computer recognizes your tablet.
Once you have your data safe (or given up on it) you can perform a factory reset and possibly have to reflash the firmware.
BTW, if you did not protect root with Voodoo Rootkeeper before the update or if you flashed the full firmware (as opposed to doing an OTA update) you also lost root. And Asus plugged the hole Motochopper used in the latest firmware version. At this point 10.6.1.14.10 is not rootable without unlocking.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4

bobstone said:
Everyone help! I just updated my tf700 to the newest update which was supposed to be minor. Everything went smooth but upon boot up everything went wrong. Every single app force closes upon unlocking the lock screen. I get a pop up for just about every single app that's trying to start saying sorry the app has closed. Oddly, any app that was originally on the device works OK. I did a normal reboot and then again I saw the upgrading message and another message saying optimizing apps and it counts through the apps its optimizing. Then again when I reboot fully it does the same thing. I did a cold reboot and it seemed a little smoother but then again I had the same force closes and error messages. And still only the stock apps will function, anything and everything else force closes upon opening.
I've never even heard of errors or problems such as this. I have no idea what to do and I have lots of data on the device I don't want to lose and can't lose. By the way I am rooted and I did not uninstall any stock apps. Just froze a couple. Build # now 10.6.1.14.10-20130801
Please any and all suggestions!
Ps - under kernel version it says (concerned about name cancer):
3.1.10-gba9af5
[email protected] #1
Thu Aug 1 17:00:24 cst 2013
Click to expand...
Click to collapse
I would just wipe and start over, even if you get it functional again you could end up with problems.

Hmmm - I too think you are going to lose your data here as I can't see how you can recover without wiping if everything is force closing now.
BTW don't worry about the kernel version being cancer that is Asus naming convention. They have been using planets and have now run out so they are now using astrology instead of astronomy which is rather odd but there you go.
Previously we had mercury, venus, jupiter, uranus etc now we have aquarius and cancer......

What don't make sense and I can't accept, I've updated this device 4 times now total and never had a problem like this. Also, I've updated a few devices with frozen apps and had no problems. Are frozen apps really the cause? I can't see it.
And if I do have to wipe, and I really don't want to, will I still be rooted after wiping and is there a way to back up things since I can't use 3rd party apps? (Also, I used voodoo)
It just seems like something went wrong with the update, say something initializing or cache problem, and im sure there's an easy fix.
Please, keep the ideas coming...

I guess, I just need to clerify , stock bootloader, stock ROM, but rooted??
Sent from my [email protected]
Sorry all was reading it on the app wow that really is not good lol

Correct, stock rom rooted. No interest in custom roms. I know there's gotta be something simple, maybe even a chkdsk in linux or something. I just hate to wipe n start over. My files seem to be intact and non stock apps start to open for a split second then they force close.

Any responses guys? Would really appreciate any help.
Thanks,
Sent from my rooted Galaxy S4

bobstone said:
Any responses guys? Would really appreciate any help.
Thanks,
Sent from my rooted Galaxy S4
Click to expand...
Click to collapse
I think you will have to wipe mate as said. Painful but can't see any other way around it.

bobstone said:
Correct, stock rom rooted. No interest in custom roms. I know there's gotta be something simple, maybe even a chkdsk in linux or something. I just hate to wipe n start over. My files seem to be intact and non stock apps start to open for a split second then they force close.
Click to expand...
Click to collapse
Yea, wipe, and no you won't keep root on a stock rom wipe. As I said previously even if you managed to "fix" the problem you would be creating potential for lockups/forced reboots. Your also not the first to have issues when upgrading with sys apps frozen, look around the forum, its been discussed before. Sucks, but there it is.

I have the same issue, and I can't remember freezing any apps. I don't have any critical data that I can't loose though. Still it sucks to have to wipe if there's another way.
Stock, locked bootloader, rooted. Temp unrooted using OTA Rootkeeper and did the OTA. Then upon the next reboot, all apps FC. All earlier updates has worked flawless. :/

vatvedt said:
I have the same issue, and I can't remember freezing any apps. I don't have any critical data that I can't loose though. Still it sucks to have to wipe if there's another way.
Stock, locked bootloader, rooted. Temp unrooted using OTA Rootkeeper and did the OTA. Then upon the next reboot, all apps FC. All earlier updates has worked flawless. :/
Click to expand...
Click to collapse
boy, i can't believe how close i was to actually going forward with this OTA when it "pooped" up in the notification area. good thing i had just been reading xda forums and i saw a couple posts bout ppl losing root and whatnot with said update.
now i am a happy camper on Cromi-x =D
best bet as a few already said is to try to extract your data from the thingy, and wipe it out, if you wanna take a n00b advice, if you're close to the end of your warranty period, go ahead and unlock it then proceed to cromi-x it. i was of the same position as you back when i bought it, not interested in custom roms and whatnot, just root...... but since my warranty was expiring next month anyways, and it had grown considerably sloppy and laggy, i figured out, why not? and i gotta tell you, it was the right thing to do.
hands down
anyways, good luck on your recovery.

I wiped and downgraded to .8 and will happily stay there for now. Maybe until I unlock the bootloader in the future.

vatvedt said:
I have the same issue, and I can't remember freezing any apps. I don't have any critical data that I can't loose though. Still it sucks to have to wipe if there's another way.
Stock, locked bootloader, rooted. Temp unrooted using OTA Rootkeeper and did the OTA. Then upon the next reboot, all apps FC. All earlier updates has worked flawless. :/
Click to expand...
Click to collapse
If you don't have it download Titanium Backup, hit Menu and wipe Dalvic cache. Reboot. The reboot will take a while because the Dalvic has to be rebuild - so don't panic
If that doesn't do it, I'm fresh out of ideas.

I tried to wipe via the stock recovery, but all the FC's was still there, and what's worse was that because of the FC's I couldn't finish (or quit) the "Set up your tablet" thingie. I always crashed on setting up a gmail account. Didn't matter if I was connected to the internet or not, or if I declined setting it up. So I had to do everything from the stock recovery.
Downloaded the .8 firwmare, unpacked the first .zip file, renamed the second .zip (to EP201_768_SDUPDATE.zip) and put it on an empty micro SD, made sure the SD-card was FAT32, booted to recovery (Power Vol down for 5 sec) and installed it via RCK, Android stock recovery.
Thanks for the tip, though. It might have worked. I don't know.

Bootloader won't unlock (4.1.2, getting ready for custom ROM)

Afternoon, y'all. Let me cut to the chase:
My objective: To install the custom ROM located at this link (http://forum.xda-developers.com/showthread.php?t=2591895). I don't want to lose my root functionality/benefits by taking the OTA 4.3 update (Titanium, Greenify, etc), but I want to be able to use apps like DashClock which don't work with 4.1.2.
My phone specs:
Model SCH-i535
Android Version 4.1.2
Baseband Version i535VRBMF1
Kernel Version 3.0.31-1152558 ([email protected] #1)
Build Number JZO54K.i535VRBMF1
Hardware version 1535.10
Phone IS ROOTED, and I used the Casual root tool located here: http://forum.xda-developers.com/showthread.php?t=2332825
[*]Apps I am using during this process (specific to root, backup, etc): Titanium Backup Pro (full backup made, including update.zip), ROM Manager, Root Checker, SuperSU
[*]Although I had a ton of frozen bloatware/system apps (all safe, I checked thoroughly before I did this a few months ago), I have unfrozen everything.
Previous experience: Before this S3, I had an HTC Thunderbolt which I successfully rooted and installed a custom ROM onto. So I have *some* experience, but I am no zen master.
Problems I've run into this time around:
Phone is rooted, but I am pretty sure the bootloader is NOT unlocked. Rootchecker confirms that the phone is rooted, and apps that require root access work just fine.
Related to the above point, when I run Casual (as I did just a few minutes ago), this is the log that appears in the window:
-Waiting for device...
Waiting for ADB device connection. When your OS recognizes the device, we will continue. Don't touch anything.
-Device found.
-Pushing exploit...
4298 KB/s (1283460 bytes in 0.291s)
-Pushing root tools...
2990 KB/s (96260 bytes in 0.031s)
4692 KB/s (1867568 bytes in 0.388s)
5424 KB/s (1872015 bytes in 0.336s)
-Rooting phone...
-This may take a few minutes.
Failure.
-installing superuser to system partition
-once root is confirmed you can flash the Insecure aboot
done
-Script Complete
This "FAILURE" is what catches my eye. I can't tell if the phone is "half-rooted" (no unlocked bootloader), or if it's just that Casual sees that my phone is already rooted so it doesn't bother trying to do it again (which is fine, I can understand that point, if it is true).
ClockworkRecovery Mod fails when trying to backup my current ROM (unlocked TouchWiz, no custom ROM installed yet). When I push "Backup Current ROM" in ROM Manager, it reboots the phone (crashes) and puts it into recovery mode, but there's nothing to recover. So my screen goes to the Yellow Triangle of Death screen and gives me a red error message in the top-left corner saying "secure kernel: fail". I had to reboot the phone using Volume Down+Home+Power, and it goes right back to a normal startup. This is what leads me to believe my bootloader is still locked, and I can't find a way to overcome that. I NEVER see the CWM menu to wipe cache, data, etc.
Titanium Backup failed to backup my SMS messages (everything else went fine). It gives me an XML error right away. I used a different app to back them up, which gave me no problems. Not sure if this is related to the larger problem, but I figured it was worth mentioning.
What I'm asking: I'm wanting to make sure that I've got all my bases covered. I know I've done my backups through Titanium Backup correctly, but I do remember that with my Thunderbolt I had to copy down some ID numbers related to the phone so I could sync it after installing a custom ROM (I haven't read any mention of this with the S3, so I'm a bit worried that I'm missing something).
CWM not working correctly is what's throwing me off- I don't want to get my phone stuck in bootloops like before. I want to backup my current setup, clean the cache/data/etc, install the ROM and then restore my apps and data.
I want to avoid resorting to ODIN and putting my phone back to stock (and risk getting the OTA 4.3 update, which I refuse to do) to be able to load this ROM, but if that's what I need to do, then so be it.
Any help, insights, etc would be immensely appreciated! I've read countless threads over the last few months (and especially in the last week), and the fact that there isn't much documentation regarding MF1 when it comes to installing bootchains and ODIN makes me feel like I'm groping in a dark a bit.
Many thanks!

Wow, long post.
Sounds like you're rooted, so download ez unlock v 1.2 to flash the insecure aboot. Then flash the rom after.
You should be good to go after that.
Edit : additionally, I wouldn't restore any apps or data from tibu in this case, going from 4.1.2 to 4.3 changes quite a bit of file structuring and could cause problems.
Sent from my SCH-I535 using Tapatalk 2

Thanks for the reply! And yes, sorry for the long post- I opted to be thorough and give all the relevant information up front instead of playing a cat-and-mouse game of having to post repeatedly with information I could've posted at the beginning.
I heard about EZ Unlock but wasn't sure if it was still appropriate to use in this case. Per your instructions, I will sideload the APK and make magic happen from there.
I DID encounter something new just about an hour ago- I used Casual but I got no errors this time. Hopefully that is a sign of good things to come.
And thanks for the heads up about TiBu backups not working well- that right there saved me a LOT of headaches, I'm sure.
This being the case, however, how would I link my device to Verizon/Google if no data is restored at all from the backup, like account information and such? And would I still be able to restore my SMS/call log (they're in an XML file, not in app data)?
Again, many thanks!

DuoDSG said:
Thanks for the reply! And yes, sorry for the long post- I opted to be thorough and give all the relevant information up front instead of playing a cat-and-mouse game of having to post repeatedly with information I could've posted at the beginning.
I heard about EZ Unlock but wasn't sure if it was still appropriate to use in this case. Per your instructions, I will sideload the APK and make magic happen from there.
I DID encounter something new just about an hour ago- I used Casual but I got no errors this time. Hopefully that is a sign of good things to come.
And thanks for the heads up about TiBu backups not working well- that right there saved me a LOT of headaches, I'm sure.
This being the case, however, how would I link my device to Verizon/Google if no data is restored at all from the backup, like account information and such? And would I still be able to restore my SMS/call log (they're in an XML file, not in app data)?
Again, many thanks!
Click to expand...
Click to collapse
Don't be sorry for the long post, much better to be detailed and explain as much as you can. Shows you did some research before asking. I wish everyone researched that much before posting.
Ez unlock is great to use in this case, it will brick your phone if you're on 4.3.
You can always restore your contacts from googles database, as far as restoring call logs and sms messages you should be OK. But if you encounter any lag or bugs it could have something to do with that.
Sent from my SCH-I535 using Tapatalk 2

All right, so I followed your instructions. I sideloaded EZ Unlock, which did the trick, and then I went into CWM Recovery, wiped the data, cache and dalvik.
Then I went ahead and loaded the ROM zip from the SD card, and VOILA! Without a hitch. The phone is snappier than EVER and it's just a matter of downloading the apps I want to again from the play store. Even the data speeds--whether on WiFi or 4G--are blazing fast, I never encountered speeds like this, even when I first got my phone stock from Verizon.
I was pleasantly surprised that my phone didn't have an identity crisis (as had happened when I rooted and loaded a custom ROM on my HTC Thunderbolt years ago). Right away it knew my phone number, and my Google account sync was flawless.
So far, extremely impressed. And I can breathe a sigh of relief that I OVERprepared for this instead of missing something crucial (so far! fingers crossed). Before, under 4.1.2, I used a combination of Greenify, freezing unwanted bloatware/system apps and Xposed Framework to get my phone to do incredible things, and I look forward to seeing how everything works under 4.3 without Verizon's slimy tentacles all over my phone again.
I will continue to update the thread as I run into issues or curious info that might be useful to anyone considering going through the same process. Surely my experience and effort can allow someone else to have an easier time than I did!
Thank you again for your help- it may have seemed simple, but the direction and reassurance you gave was all the help I needed to make it happen and not blow up my phone

TWRP backups not recognized

Let me start by saying that I am not new to rooting and flashing firmware, its just been a while since I last did it. I've had a nexus 5 for a few months with sprint in the US. I continually have reception issues and dropped calls so I took the phone in to a store. Before I could do that I had to reset everything to stock. I had no trouble doing any of that. I made a complete backup of my ROM before I did all that using TWRP. I went to the store and they told me to turn off lte in order to reduce dropped calls. After the I got home I set to work re-rooting and unlocking my bootlaoder. However when I went to restore in TWRP it would not recognize the backup even though it had been made only a few hours before. I spent several hours trying to get TWRP to recognize the backup. Whenever I navigated to the directory containing the backup the directory was always empty. I even tried zipping the backup and flashing it but it did not work. Eventually I decided to cut my losses and move on. I plan on taking the phone back to sprint tomorrow because I still have horrible reception issues. I really want to avoid having to go through the whole ordeal again but I am not sure what I did wrong. The only thing I can think of is that immediately after making the backup I moved it off the device onto my laptop but did not modify it in any way. I had some experience with CWM back when I had my old HP touchpad but none with TWRP, however they don't seem that different. Any help is greatly appreciated.

UserNumberZero said:
Let me start by saying that I am not new to rooting and flashing firmware, its just been a while since I last did it. I've had a nexus 5 for a few months with sprint in the US. I continually have reception issues and dropped calls so I took the phone in to a store. Before I could do that I had to reset everything to stock. I had no trouble doing any of that. I made a complete backup of my ROM before I did all that using TWRP. I went to the store and they told me to turn off lte in order to reduce dropped calls. After the I got home I set to work re-rooting and unlocking my bootlaoder. However when I went to restore in TWRP it would not recognize the backup even though it had been made only a few hours before. I spent several hours trying to get TWRP to recognize the backup. Whenever I navigated to the directory containing the backup the directory was always empty. I even tried zipping the backup and flashing it but it did not work. Eventually I decided to cut my losses and move on. I plan on taking the phone back to sprint tomorrow because I still have horrible reception issues. I really want to avoid having to go through the whole ordeal again but I am not sure what I did wrong. The only thing I can think of is that immediately after making the backup I moved it off the device onto my laptop but did not modify it in any way. I had some experience with CWM back when I had my old HP touchpad but none with TWRP, however they don't seem that different. Any help is greatly appreciated.
Click to expand...
Click to collapse
Did you put your backups in the correct sub-directory?
Should be something like: TWRP/BACKUPS/87095jgjg9034/nameofyourbackup

upndwn4par said:
Did you put your backups in the correct sub-directory?
Should be something like: TWRP/BACKUPS/87095jgjg9034/nameofyourbackup
Click to expand...
Click to collapse
Yes, I did. I even tried renaming the backup to "backup" and still had no luck.

Well, this is interesting. I went to Sprint today and they weren't much help but before I went there I reset everything back to stock. I made a backup yesterday and when I got home I put it on my phone and it was recognized immediately by TWRP and I was able to restore it. Not sure what I did wrong last time, if I did anything wrong at all.

UserNumberZero said:
Well, this is interesting. I went to Sprint today and they weren't much help but before I went there I reset everything back to stock. I made a backup yesterday and when I got home I put it on my phone and it was recognized immediately by TWRP and I was able to restore it. Not sure what I did wrong last time, if I did anything wrong at all.
Click to expand...
Click to collapse
Yeah, that's a bit odd. Glad you got it working now.
Sent from some device using XDA Premium mobile app