Related
Ok so I used to have a Samsung Captivate and knew how to root and flash ROMs, was pretty used to it.
I tried to do the same on my HOX, but ran into a bootloop and subsequently I think I've deleted everything on my phone. I used Hasoon2000's All in one kit and unlocked my bootloader, flashed TWRP v 2.3.3.0, but my problem arose after I tried to flash the kernel. It stayed in bootloop so I figured I'd back out and just restore back to the backup I made before flashing the kernel. However, after "successfully" restoring back I was still stuck in bootloop somehow. I know this isn't supposed to happen, it's supposed to restore back to the exact state of your phone at the time.
Anyways, I thought maybe I just needed to wipe things. I looked around and found a source that said to wipe cache, dalvik, factory reset, and system. Wipe those 4, but not external storage or android secure. So I wiped those 4 and I intended to try the backup again but it turns out that cleared everything on my phone. Now when I hit "restore" there is nothing to select. I also used to have a custom rom on the virtual sdcard, but that's gone too.
When in TWRP and I go into "install" the only thing in /sdcard is now TWRP. After looking around, it looks like my only option is to mount the phone to my computer via TWRP and somehow download the standard OS for my One X again. Also in the Mount menu it lists "mount system, mount data, mount cache, mount sd card" I can only check the first 3 options and when I do my computer asks me if I want to format it. I guess I can't mount the sd card because I deleted everything?
If anyone has the time to help me out that would be AMAZING. Right now I don't even care about being able to flash my custom ROM, I just want to get my phone back to functionality. I would love a conversation and would be willing to gmail chat if willing.
Also my phone is the ATT version, 2.20 (or I guess it was before I deleted everything).
Thank you in advance for any help.
I guess the fastest way to get your phone working again is using RUU file, you ll find how to do it here (method 2) or here
It stayed in bootloop so I figured I'd back out and just restore back to the backup I made before flashing the kernel. However, after "successfully" restoring back I was still stuck in bootloop somehow. I know this isn't supposed to happen, it's supposed to restore back to the exact state of your phone at the time.
Click to expand...
Click to collapse
Restoring backup doesnt restore kernel ( boot.img ), you have to flash it manually with fastboot.
Dude. U think htc offers same freedom as Samsung . U are WRONG. If u flash a rom or restore a backup. U also need to flash boot.img separately from pc. Use fastboot flash boot boot.img. i assume you know the basics. Htc don't have s-off , so writing to nand protected system storage is restricted. If u read a little you might have got this. This will solve boot loop prob
Sent from my HTC One X using Tapatalk 2
Fixed
Thanks Yasounet. I managed to flash viper in the end.
I'm freaking out and need some help. I recently rooted my S3 and everything went smoothly. I was running stock android 4.1.2 I think (multi-window feature) with root. Wanted to flash the cyanogemon 10.1 rom. I got titanium back up,backed up eveything. Flashed it. Seemed to be working normally but as I tried to restore my apps and things from the titanium back up it went all wrong. "Unfortunately,Email has stopped,the process android,process media has stopped. Also says process.acore has stopped and process.gapps has stopped pop up that is constant. I freaked out and tried to go back to normal and now I'm screwed.
I tried recovery and it tells me I dont have a OS on my phone. I than decided to Unroot the phone and start from a fresh stock android but it seemed like it worked 50%. I see the background and it shows me the set up google account for the phone but the pop up messages haven't stopped.If I go into the normal recovery and wipe data/factory reset will it solve the issue? And if it will should I choose to wipe cache partition first before doing so?
Which recovery do you have? Also I never backup system apps such as email, because they change when going from 1 rom to the next. No OS means you wiped system, without having another ROM saved on your sd card. If your computer still sees the internal and external memory and your custom recovery is still working, you should be able to save a new rom, do a full wipe-system, data, cache, dalvik cache. Then flash rom you already saved to your memory. I take it you didn't do a Android backup after you rooted and flashed custom recovery?
sent from somewhere
Miguelcoo1 said:
I'm freaking out and need some help. I recently rooted my S3 and everything went smoothly. I was running stock android 4.1.2 I think (multi-window feature) with root. Wanted to flash the cyanogemon 10.1 rom. I got titanium back up,backed up eveything. Flashed it. Seemed to be working normally but as I tried to restore my apps and things from the titanium back up it went all wrong. "Unfortunately,Email has stopped,the process android,process media has stopped. Also says process.acore has stopped and process.gapps has stopped pop up that is constant. I freaked out and tried to go back to normal and now I'm screwed.
I tried recovery and it tells me I dont have a OS on my phone. I than decided to Unroot the phone and start from a fresh stock android but it seemed like it worked 50%. I see the background and it shows me the set up google account for the phone but the pop up messages haven't stopped.If I go into the normal recovery and wipe data/factory reset will it solve the issue? And if it will should I choose to wipe cache partition first before doing so?
Click to expand...
Click to collapse
Ok, first I'll describe what you did and how that (most likely) messed up your phone. Then I'll describe what you can do to fix it.
Problem
It seems like your original flash of CM10.1 went smoothly. It must have been something to do with your Titanium Backup (TiBu) restores. More than likely, you tried to restore too much. In TiBu, the different apps have different colors: Red, Yellow, Green, and White. In the menu, you can see the following Legend:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
White: User Application. These are apps that you installed from the Play Store or sideloaded by directly installing an apk. These are safe to restore.
Red: System Application. These are system files that heavily rely on which Android version (4.1.x vs. 4.2.x) and whether you're on TW or AOSP. I always try to avoid restoring these backups (even when just upgrading to a newer version of the same Rom). Some people will say that you can restore the Data only for these, but my motto is: caution will help prevent mistakes (ground-shaking, I know).
Green: System Service with Useful Data: These are system apps that have useful information (such as User Accounts, etc.). I treat these the same as Red Backups, but am a bit more likely to restore the data of them (green means go, right?).
Yellow: These backups are system data that can be restored as an xml file. These are inherently safer than the red and green ones, and I say restore away (I always restore my Call Log, Messages, and Wi-Fi Access Points).
The reason you were getting FCs was restoring a red or green backup. This can sometimes work, but has a lot of potential for issues when switching between TW and AOSP Roms. Most likely something in your /system folder is messed up due to restoring an app. Even when you flash a new Rom, it just overwrites items in your System folder, it doesn't wipe /System. So whatever is wrong in your /System folder is still there, regardless of what you flash.
Ok, now that we've identified what's wrong with your phone, we can now help solve it!
Solution/Fixes
Are you able to get into a custom Recovery? If not, you need to use Odin and follow The Rooting Guide to get back to a custom recovery (I recommend TWRP, but CWM is just as good).
Next, you want to download a Rom and put it on your device. I'd recommend (just for now), to get Freeza's stock TW Rom.
Now, before you try to flash this Rom, you'll have to wipe. In order to get rid of the FCs, you'll have to at least wipe System. I'd recommend a full wipe of your Internal SD Card (after backing up anything you want to save), but it's not technically necessary. Afterwards, you can wipe data and cache/dalvik cache.
Then you can flash your Rom. It seems like you know how to do this, but in case you don't, I have previously posted directions over here.
Hope this helps!
joeyhdownsouth said:
So you never had a custom recovery, like CWM or TWRP? Also I never backup system apps such as email, because they change when going from 1 rom to the next.
sent from somewhere
Click to expand...
Click to collapse
I did have a Custom Recovery. I believe it was TWRP. I think all this happened was because when it occured I might of went into the recovery and accidently wiped system. I know that the phone didn't have OS on it and was blank. It just stayed on the Samsung boot screen. About 20 minutes ago I tried to unroot the phone and start with stock android. I didn't have much important stuff on my phone so I don't mind. The problem is when I did that it seemed to work. Only to find out that the pop-ups still exist and are constantly popping up where I cant do anything.
I would it worked seeing as though I can go into my stock recovery mode. Could it be possible to just wipe everything there and factory reset it or would it brick the phone? Also if I can just factory reset it through the stock recovery should I wipe the cache partition first?
topherk said:
Ok, first I'll describe what you did and how that (most likely) messed up your phone. Then I'll describe what you can do to fix it.
Problem
It seems like your original flash of CM10.1 went smoothly. It must have been something to do with your Titanium Backup (TiBu) restores. More than likely, you tried to restore too much. In TiBu, the different apps have different colors: Red, Yellow, Green, and White. In the menu, you can see the following Legend:
White: User Application. These are apps that you installed from the Play Store or sideloaded by directly installing an apk. These are safe to restore.
Red: System Application. These are system files that heavily rely on which Android version (4.1.x vs. 4.2.x) and whether you're on TW or AOSP. I always try to avoid restoring these backups (even when just upgrading to a newer version of the same Rom). Some people will say that you can restore the Data only for these, but my motto is: caution will help prevent mistakes (ground-shaking, I know).
Green: System Service with Useful Data: These are system apps that have useful information (such as User Accounts, etc.). I treat these the same as Red Backups, but am a bit more likely to restore the data of them (green means go, right?).
Yellow: These backups are system data that can be restored as an xml file. These are inherently safer than the red and green ones, and I say restore away (I always restore my Call Log, Messages, and Wi-Fi Access Points).
The reason you were getting FCs was restoring a red or green backup. This can sometimes work, but has a lot of potential for issues when switching between TW and AOSP Roms. Most likely something in your /system folder is messed up due to restoring an app. Even when you flash a new Rom, it just overwrites items in your System folder, it doesn't wipe /System. So whatever is wrong in your /System folder is still there, regardless of what you flash.
Ok, now that we've identified what's wrong with your phone, we can now help solve it!
Solution/Fixes
Are you able to get into a custom Recovery? If not, you need to use Odin and follow The Rooting Guide to get back to a custom recovery (I recommend TWRP, but CWM is just as good).
Next, you want to download a Rom and put it on your device. I'd recommend (just for now), to get Freeza's stock TW Rom.
Now, before you try to flash this Rom, you'll have to wipe. In order to get rid of the FCs, you'll have to at least wipe System. I'd recommend a full wipe of your Internal SD Card (after backing up anything you want to save), but it's not technically necessary. Afterwards, you can wipe data and cache/dalvik cache.
Then you can flash your Rom. It seems like you know how to do this, but in case you don't, I have previously posted directions over here.
Hope this helps!
Click to expand...
Click to collapse
Well as of right I believe I just unrooted the phone and went back to stock android because when I try and go into recovery mode, it gives me the normal stock recovery. I thought it would work but needless to say the applications pop-ups saying it stopped working is still happening. I can see the google account set up but cant do anything because of the pop-ups and also theres a I icnon with a no symbol around it on the top left corner (dont know what that means). Is it possible to factory reset and wipe the data from this stock recovery? And if so should I wipe cache partition first?
Also thanks for the help. My head hurts trying to figure out how to fix this...It just seems like everything I try and do makes it worse or the same.
Miguelcoo1 said:
I did have a Custom Recovery. I believe it was TWRP. I think all this happened was because when it occured I might of went into the recovery and accidently wiped system. I know that the phone didn't have OS on it and was blank. It just stayed on the Samsung boot screen. About 20 minutes ago I tried to unroot the phone and start with stock android. I didn't have much important stuff on my phone so I don't mind. The problem is when I did that it seemed to work. Only to find out that the pop-ups still exist and are constantly popping up where I cant do anything.
I would it worked seeing as though I can go into my stock recovery mode. Could it be possible to just wipe everything there and factory reset it or would it brick the phone? Also if I can just factory reset it through the stock recovery should I wipe the cache partition first?
Click to expand...
Click to collapse
It's not gonna work because you wiped system, and now you have stock recovery. I would follow topherk's post above this one. Very well written.
sent from somewhere
Miguelcoo1 said:
Well as of right I believe I just unrooted the phone and went back to stock android because when I try and go into recovery mode, it gives me the normal stock recovery. I thought it would work but needless to say the applications pop-ups saying it stopped working is still happening. I can see the google account set up but cant do anything because of the pop-ups and also theres a I icnon with a no symbol around it on the top left corner (dont know what that means). Is it possible to factory reset and wipe the data from this stock recovery? And if so should I wipe cache partition first?
Also thanks for the help. My head hurts trying to figure out how to fix this...It just seems like everything I try and do makes it worse or the same.
Click to expand...
Click to collapse
You're doing well, don't get too frustrated.
Stock recovery is relatively limited and it won't be able to wipe what you need to wipe. When you do a factory reset in Stock (or custom) recoveries, you are just wiping the /data folder. Since we've identified that it's most likely an issue with /System, a Factory Reset won't do any good.
Your best bet it to get a Custom Recovery again through the Rooting Guide. That guide is really well-written and has pictures so it's easier to follow.
After you have CWM and TWRP, it's real easy to wipe everything (in TWRP 2.5.0.0, you just wipe internal sd card and you're good to go). Or you can do a comprehensive wipe by wiping /System, /Data, Cache and Dalvik Cache. Then you can flash a Rom (again, I'd recommend Freeza's). After you get Freeza's Rom up and running, I'd make a Nandroid Backup immediately (in a Custom Recovery). This will be the backup that you can return to whenever something doesn't flash well.
topherk said:
You're doing well, don't get too frustrated.
Stock recovery is relatively limited and it won't be able to wipe what you need to wipe. When you do a factory reset in Stock (or custom) recoveries, you are just wiping the /data folder. Since we've identified that it's most likely an issue with /System, a Factory Reset won't do any good.
Your best bet it to get a Custom Recovery again through the Rooting Guide. That guide is really well-written and has pictures so it's easier to follow.
After you have CWM and TWRP, it's real easy to wipe everything (in TWRP 2.5.0.0, you just wipe internal sd card and you're good to go). Or you can do a comprehensive wipe by wiping /System, /Data, Cache and Dalvik Cache. Then you can flash a Rom (again, I'd recommend Freeza's). After you get Freeza's Rom up and running, I'd make a Nandroid Backup immediately (in a Custom Recovery). This will be the backup that you can return to whenever something doesn't flash well.
Click to expand...
Click to collapse
Thanks for all the help. I'm downloading the GS3 Root Kit Zip so I can follow your instructions. I'm going to try and bring my phone back to life. I'll update when hopefully its fixed lol.
topherk said:
You're doing well, don't get too frustrated.
Stock recovery is relatively limited and it won't be able to wipe what you need to wipe. When you do a factory reset in Stock (or custom) recoveries, you are just wiping the /data folder. Since we've identified that it's most likely an issue with /System, a Factory Reset won't do any good.
Your best bet it to get a Custom Recovery again through the Rooting Guide. That guide is really well-written and has pictures so it's easier to follow.
After you have CWM and TWRP, it's real easy to wipe everything (in TWRP 2.5.0.0, you just wipe internal sd card and you're good to go). Or you can do a comprehensive wipe by wiping /System, /Data, Cache and Dalvik Cache. Then you can flash a Rom (again, I'd recommend Freeza's). After you get Freeza's Rom up and running, I'd make a Nandroid Backup immediately (in a Custom Recovery). This will be the backup that you can return to whenever something doesn't flash well.
Click to expand...
Click to collapse
Well I did everything but flash the rom. My question is in the link you gave me to flash Freeza's rom which one do I download, The first one on the top?
Miguelcoo1 said:
Well I did everything but flash the rom. My question is in the link you gave me to flash Freeza's rom which one do I download, The first one on the top?
Click to expand...
Click to collapse
I knew this question was going to pop up... I should've put it in my original post.
You're probably going to want to flash the Deodex MD4 one:
DeOdex:
Sprint Touchwiz Jelly Bean 4.1.2 L710VPBMD4
MD5: 77262D9D6CF1A6AF30A8981A95A75D57
Click to expand...
Click to collapse
I find that a lot of mods require DeOdex Roms, so in case you decide to flash one in the future, it'll help to have it. And the main negative of DeOdex is a slightly longer start-up time, so I recommend people use DeOdex.
topherk said:
I knew this question was going to pop up... I should've put it in my original post.
You're probably going to want to flash the Deodex MD4 one:
I find that a lot of mods require DeOdex Roms, so in case you decide to flash one in the future, it'll help to have it. And the main negative of DeOdex is a slightly longer start-up time, so I recommend people use DeOdex.
Click to expand...
Click to collapse
Ok, I'm downloading the massive zip file on my desktop and waiting for it to be finished. My question is how am I going to transfer the zip file into the sdcard? Could it be just as simple as putting the phone in download mode and connect to my computer to transfer the file? Also I wanted to know once I Flash the rom and Custom Recovery which would be TWRP to Backup does it back up everything or is there only a few things I do need to back up. I ask because as of right now my phone is shut off and doesn't have a OS on it. Just waiting on the zip file to finally flash the rom and back it up.
I also wanted to ask you about something I been thinking about. When all this mess happened because I backed up files I wasnt suppose to back up with titanium back up, the backup file still exist on my sdcard. Is it possible for me to delete everything other than just the apps and it will work fine? I ask because I'm planning on getting the Cyan 10.1 rom again because I loved it (for the few minutes it ran fine). Or should I just not do it and start fresh? Would it be possible to use those app back up files when I install titanium back up again?
Miguelcoo1 said:
Ok, I'm downloading the massive zip file on my desktop and waiting for it to be finished. My question is how am I going to transfer the zip file into the sdcard? Could it be just as simple as putting the phone in download mode and connect to my computer to transfer the file? Also I wanted to know once I Flash the rom and Custom Recovery which would be TWRP to Backup does it back up everything or is there only a few things I do need to back up. I ask because as of right now my phone is shut off and doesn't have a OS on it. Just waiting on the zip file to finally flash the rom and back it up.
I also wanted to ask you about something I been thinking about. When all this mess happened because I backed up files I wasnt suppose to back up with titanium back up, the backup file still exist on my sdcard. Is it possible for me to delete everything other than just the apps and it will work fine? I ask because I'm planning on getting the Cyan 10.1 rom again because I loved it (for the few minutes it ran fine). Or should I just not do it and start fresh? Would it be possible to use those app back up files when I install titanium back up again?
Click to expand...
Click to collapse
Ok, so from what I can tell, you've already wiped your internal memory. Since you can't load up into the Rom to copy the files, there are a couple of ways to get them on your phone:
Manual Copy: Take the external Micro SD card out and pop it into an adapter and insert it into your computer to copy the file (I've done this once or twice).
Recovery Mounting as USB: If you have TWRP 2.4.1.0 or 2.5.0.0, there should be an option which allows you to mount the phone as a usb mass storage. It should be in the mount menu.
ADB Copy: Connect the phone to the computer and boot the phone into download mode. You can then use adb to copy the file over to the phone. I'm personally not very good with adb, but there are good guides on here with how to do this. (Guide 1) (Guide 2)
Once you get a Rom up and running on your phone, you won't have to do these, but since it wasn't working before, this is the way to do it.
topherk said:
Ok, so from what I can tell, you've already wiped your internal memory. Since you can't load up into the Rom to copy the files, there are a couple of ways to get them on your phone:
Manual Copy: Take the external Micro SD card out and pop it into an adapter and insert it into your computer to copy the file (I've done this once or twice).
Recovery Mounting as USB: If you have TWRP 2.4.1.0 or 2.5.0.0, there should be an option which allows you to mount the phone as a usb mass storage. It should be in the mount menu.
ADB Copy: Connect the phone to the computer and boot the phone into download mode. You can then use adb to copy the file over to the phone. I'm personally not very good with adb, but there are good guides on here with how to do this. (Guide 1) (Guide 2)
Once you get a Rom up and running on your phone, you won't have to do these, but since it wasn't working before, this is the way to do it.
Click to expand...
Click to collapse
Ok, the phone is back and running good. I just flashed and its working great...Again, Thanks a lot. Thanks for being so patient with me lol. It's been a all day affair for me wit this. I just Backed up the Rom in the TWRP recovery mode and just backed up /System /Data /Boot. I also compressed it and put it on my external SD. Now that I got that out the way, I wanted to verify if my thought on using the back up files (apps only) from the last titanium backup (which messed up my phone) to maybe try and restore them to get the phone to how it was and wont lose my apps/games? Can this be done or would it be difficult to know the differences between a app and other files?
When I backup in twrp, I typically choose everything. The recovery and cache are typically so small it doesn't matter.
In terms of titanium backups, I'd say it's safe to restore any user apps, but no system apps, not even the green ones.
Glad to hear everything worked for you!
Sent from my SPH-L710 using xda app-developers app
topherk said:
When I backup in twrp, I typically choose everything. The recovery and cache are typically so small it doesn't matter.
In terms of titanium backups, I'd say it's safe to restore any user apps, but no system apps, not even the green ones.
Glad to hear everything worked for you!
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Believe me you saved me from disaster. I was going nuts trying to find a way to fix it. Glad you saw my thread and your patience to help. I'm thinking about backing up the rom again after updating all the normal stock apps but before I try and get my apps that I downloaded from the play store. I do have one quick question, The TWRP backup also backs up the apps that you have right?
I have one last question. If my backup file (titanium) is on my external SD how can I tell which apps I can restore when I download titanium back up again? Is there even a way to know?
Yeah, it's better to have a nandroid backup of your set-up phone. It makes a restore much more palatable.
In terms of TiBu, it should find your restore folder. If not, you can manually set it from the settings.
Sent from my SPH-L710 using xda app-developers app
topherk said:
Yeah, it's better to have a nandroid backup of your set-up phone. It makes a restore much more palatable.
In terms of TiBu, it should find your restore folder. If not, you can manually set it from the settings.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
I now learned to always have a nandroid backup to make life so much easier lol. My only concern with TiBu finding the restore folder on my External SD, I'm concerned that all this might happen again. So from what you told me just restore the user apps only..Nothing more? Thank you man, your a life saver.
No problem man, I enjoy helping people and it deepens my understanding of my own phone.
TiBu shouldn't restore your apps unless you tell it to. I always restore one app at a time, so I know exactly what I'm restoring. I have my TiBu to automatically backup my phone daily at 3am. It backs up everything, system and user apps. I just make sure that I only restore user apps when I flash a new Rom.
Sent from my SPH-L710 using xda app-developers app
topherk said:
No problem man, I enjoy helping people and it deepens my understanding of my own phone.
TiBu shouldn't restore your apps unless you tell it to. I always restore one app at a time, so I know exactly what I'm restoring. I have my TiBu to automatically backup my phone daily at 3am. It backs up everything, system and user apps. I just make sure that I only restore user apps when I flash a new Rom.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Sorry to bother you again but I just saw something that seems pretty fishy. I been practically on Wifi since I flashed the phone and now everything works. The issue i'm seeing though is that the signal bars are good with reception yet the 3g symbol isnt showing up. I tried to make a call and it seems like it works but I can't go on the internet. It just gives me the webpage not available screen. I dont think I have a data connection..Any ideas?
Update profile and prl.
Transmitted with a portable device using Xparent Blue Tapatalk 2
Hello, I recently rooted my wifes Note 2 that was on the latest OTA 4.3. Was not easy BTW. I did a back up in recovery of boot, system, and data. I figured I was good to go and start trying out other roms.
The first one I flashed was Macks Allstar 5.0 rom. Everything was great. Then my wife informed me that she did not have all of her contacts backed up to google and some were only saved to her phone. So then I figure I could just restore the original backup and extract the contacts and be able to install them to any rom.
Thats when everything went wrong. Everytime I tried restoring the back up,it would crash and recovery would do like a reboot. After many attempts I figured id try another version of recovery. After flashing many earlier versions of twrp and trying to restore, I finally was able to complete a restore from version 2.6. I was ecstatic. But then my heart sank again when boot always hangs on samsung logo. And that is where I'm stuck. I am able to flash other roms no problem but cant restore my original backup.
Needless to say my wife is ready to kill me.
Please if anyone could help me I would really appreciate it. I have searched throughout this forum and internet for hours and can not seem to find any help with this issue.
I am thankful to have been able to get this far with the help from the XDA community posts I never needed direct help even with prior phone rootings but this one has got me stumped. Thanks in advance
You need to flash Phil's recovery version 6.0.7.9. If you cant restore your backup with Phil's then I'm thinking you might be sol. Make sure you know where you saved the backup to. It's either on the phone's internal sd or external sd card. Choose the correct location in Phil's recovery and if it isn't corrupt it should work. You may also want to copy your backup onto your pc just in case because that's your only backup and doing a full wipe or odin restore could permanently delete it. Good luck.
tx_dbs_tx said:
You need to flash Phil's recovery version 6.0.7.9. If you cant restore your backup with Phil's then I'm thinking you might be sol. Make sure you know where you saved the backup to. It's either on the phone's internal sd or external sd card. Choose the correct location in Phil's recovery and if it isn't corrupt it should work. You may also want to copy your backup onto your pc just in case because that's your only backup and doing a full wipe or odin restore could permanently delete it. Good luck.
Click to expand...
Click to collapse
Thank you for your reply. I am at work right now and left the phone with my wife with a working rom. I will try phils recovery when I get home. As far as backups, I have two copies. One on my SD card and the other on PC but if they're both fried I guess that negates my efforts in redundancy. It's hard to believe the backup got corrupt so quickly. I have another backup of the 2nd rom I flashed and that one wont install as well.
Is there something I am doing wrong? If the backup file is corrupt, is there a way to extract contacts seperately out of backup?
Method b.
http://forum.xda-developers.com/showthread.php?t=2648855
My wife does that too. Sorry
ColeTrain! said:
Method b.
http://forum.xda-developers.com/showthread.php?t=2648855
My wife does that too. Sorry
Click to expand...
Click to collapse
Life of a married man. Haha!
Well, as my backup file was done with TWRP, I tried method B with TWRP recovery and it wont work so now I'm in the process of trying method A. Will update once I tried it.
I think my problem has to do with TWRP not playing friendly with 4.3 ROMS. If that is the case method A looks like it will work.:fingers-crossed:
alexandnen said:
Life of a married man. Haha!
Well, as my backup file was done with TWRP, I tried method B with TWRP recovery and it wont work so now I'm in the process of trying method A. Will update once I tried it.
I think my problem has to do with TWRP not playing friendly with 4.3 ROMS. If that is the case method A looks like it will work.:fingers-crossed:
Click to expand...
Click to collapse
That's exactly right. Bootloader isn't playing well with TWRP recovery. Phil"s 6.0.7.9 seems to be compatible in most ROM vs bootloader situations. Don't use latest version of Phil's recovery as it doesn't work as well and most people recommend this as well.
If Phil's recovery won't flash your restore then Odin all the way back to stock unrooted LK8 ROM then root it with the Toolkit and flash TWRP from the toolkit at the same time. Then see if you can restore at that point.
Looks like this project has come to an end. My wife likes her new rom and doesn't want to let me work on her phone anymore. She was able to get most of her contacts back I will make sure she backs her contacts to google and I will try to convince her to install Titanium backup to backup all her app data.
Unfortunately all I have is a work issued iphone that I have no interest in jailbreaking. I really don't see the point.
I am still confident that I could have eventually restored her backup successfully with the help here.
Thank you tx_dbx_tx and coletrain for your help.
Hi,
I rooted my phone today using Chainfire's Autoroot. After doing this, I installed CWM on my phone, specifically, CWM Touch 6.0.4.3. After this, I created an image.zip backup of the phone and its data. I then, in order to test it, loaded the image.zip. It said that it was successful, but when it rebooted, it got stuck at the samsung logo. I have tried using to boot into recovery to mess around with CWM, but it does not allow me to boot into recovery. I can boot into download mode however, and reinstalled CWM in the hopes that I would be able to access it, to no avail. I also tried rerooting the phone using CF Autoroot in the hopes that it might do something, however little a chance that may have been. I know that I can flash a stock rom, but I am trying to preserve as much information and data on my phone as possible. Should I attempt to flash a stock rom, reinstall CWM and try to reload the image.zip? Or is there some other route I should take?
Thank you for your time,
Dan
MLS_Dumpster said:
Hi,
I rooted my phone today using Chainfire's Autoroot. After doing this, I installed CWM on my phone, specifically, CWM Touch 6.0.4.3. After this, I created an image.zip backup of the phone and its data. I then, in order to test it, loaded the image.zip. It said that it was successful, but when it rebooted, it got stuck at the samsung logo. I have tried using to boot into recovery to mess around with CWM, but it does not allow me to boot into recovery. I can boot into download mode however, and reinstalled CWM in the hopes that I would be able to access it, to no avail. I also tried rerooting the phone using CF Autoroot in the hopes that it might do something, however little a chance that may have been. I know that I can flash a stock rom, but I am trying to preserve as much information and data on my phone as possible. Should I attempt to flash a stock rom, reinstall CWM and try to reload the image.zip? Or is there some other route I should take?
Thank you for your time,
Dan
Click to expand...
Click to collapse
Try wiping cache and dalvik and reboot
How would I go about doing this? I do not have access to recovery mode. Is there a program I can install to do this? Or can I accomplish this through ODIN? I know how to flash stuff using ODIN but not much else.
MLS_Dumpster said:
How would I go about doing this? I do not have access to recovery mode. Is there a program I can install to do this? Or can I accomplish this through ODIN? I know how to flash stuff using ODIN but not much else.
Click to expand...
Click to collapse
With your phone off, press and hold power home and volume up until you see the little blue text at the top then release, will put you in recovery to wipe cache and dalvik
mattzeller said:
With your phone off, press and hold power home and volume up until you see the little blue text at the top then release, will put you in recovery to wipe cache and dalvik
Click to expand...
Click to collapse
I accessed the recovery menu using your instructions, and wiped the cache partition. I tried to reboot and I have the same issue. What should I try next? I now have access to that menu if that opens up any possibilities. I am by no means an expert, but it appears as though this is a booting issue. I checked, through the recovery menu, and found all my data still on my phone, which is a good sign, but also leads me to believe that the main issue seems to pertain to the booting process.
Thanks again for your time.
MLS_Dumpster said:
I accessed the recovery menu using your instructions, and wiped the cache partition. I tried to reboot and I have the same issue. What should I try next? I now have access to that menu if that opens up any possibilities. I am by no means an expert, but it appears as though this is a booting issue. I checked, through the recovery menu, and found all my data still on my phone, which is a good sign, but also leads me to believe that the main issue seems to pertain to the booting process.
Thanks again for your time.
Click to expand...
Click to collapse
I would suggest hooking it to your computer, backing up any data you want to keep, do a factory reset
mattzeller said:
I would suggest hooking it to your computer, backing up any data you want to keep, do a factory reset
Click to expand...
Click to collapse
Whenever I try to hook up my phone to the computer, it doesn't show up on my computer unless the phone is fully booted. How would I go about hooking it up?
MLS_Dumpster said:
Whenever I try to hook up my phone to the computer, it doesn't show up on my computer unless the phone is fully booted. How would I go about hooking it up?
Click to expand...
Click to collapse
I use Philz, but somewhere you should see something about mounting USB, once you do that you can back up pictures and files and whatnot
mattzeller said:
I use Philz, but somewhere you should see something about mounting USB, once you do that you can back up pictures and files and whatnot
Click to expand...
Click to collapse
We just had a breakthrough; we were able to flash PhilZ touch onto the phone. We mounted the USB, and we were able to access the external sd card, but we still do not have access to the internal sd or boot. Theoretically, because we were able to flash PhilZ, this means the phone still has root access, and therefore, the data is still there. Now we have PhilZ working, would it be possible to make a backup of the data from the internal SD? I am looking in the menu and it gives me the option to backup to sdcard or sdcard1. How should I proceed? Is this the best option?
Thanks!
MLS_Dumpster said:
We just had a breakthrough; we were able to flash PhilZ touch onto the phone. We mounted the USB, and we were able to access the external sd card, but we still do not have access to the internal sd or boot. Theoretically, because we were able to flash PhilZ, this means the phone still has root access, and therefore, the data is still there. Now we have PhilZ working, would it be possible to make a backup of the data from the internal SD? I am looking in the menu and it gives me the option to backup to sdcard or sdcard1. How should I proceed? Is this the best option?
Thanks!
Click to expand...
Click to collapse
Yes, you can make a nandroid from there, so a backup to sdcard1. What exactly are you trying to save?
mattzeller said:
Yes, you can make a nandroid from there, so a backup to sdcard1. What exactly are you trying to save?
Click to expand...
Click to collapse
As much as possible, most importantly my contacts, and messages. We are backing up to sd card 1 now. Correct me if I am wrong, but our course of action now would be to take the backup and either a. restore it, or b. factory reset, root phone, install philZ again, and restore then, correct? I just want to be very clear with my options before proceeding with either.
Thanks again dude!
MLS_Dumpster said:
As much as possible, most importantly my contacts, and messages. We are backing up to sd card 1 now. Correct me if I am wrong, but our course of action now would be to take the backup and either a. restore it, or b. factory reset, root phone, install philZ again, and restore then, correct? I just want to be very clear with my options before proceeding with either.
Thanks again dude!
Click to expand...
Click to collapse
Contacts are backed up by Google, if you are having a booting problem, backing up and restoring will not fix it. Philz does not need to be re-flashed. If you are currently on stock, reflash a stock ROM without wiping internal storage, go in backup your messages with something like Titanium Backup.
mattzeller said:
Contacts are backed up by Google, if you are having a booting problem, backing up and restoring will not fix it. Philz does not need to be re-flashed. If you are currently on stock, reflash a stock ROM without wiping internal storage, go in backup your messages with something like Titanium Backup.
Click to expand...
Click to collapse
I understand now what it is we need to do. In the search of a usable stock ROM, we hear it is impossible to flash 4.4.2 without losing all the data on internal storage. Is this true? Is there a way around this? If there isn't a way around it, I understand, but it would just be very inconvenient. How should we approach this?
Thanks again!
Apparently, TWRP v2.8.6.2 compressed images to external SD cards are damaged, and it wiped my Recovery Mode and part of my previous Stock OS LRX22G.T800XXU1BOE2 installation.
I was able to Odin a Canadian copy of T800XXU1BOCC_T800XAC1BOC4_XAC, but it isn't working properly on my SM-T800.
Can somebody please point me to a US LRX22G.T800XXU1BOE2?
Thanks,
¿GJ?
¿GotJazz? said:
Apparently, TWRP v2.8.6.2 compressed images to external SD cards are damaged, and it wiped my Recovery Mode and part of my previous Stock OS LRX22G.T800XXU1BOE2 installation.
I was able to Odin a Canadian copy of T800XXU1BOCC_T800XAC1BOC4_XAC, but it isn't working properly on my SM-T800.
Can somebody please point me to a US LRX22G.T800XXU1BOE2?
Thanks,
¿GJ?
Click to expand...
Click to collapse
Always check sammobile.com
http://www.sammobile.com/firmwares/download/47566/T800XXU1BOE2_T800XAR1BOC5_XAR/
Ramer said:
Always check sammobile.com
http://www.sammobile.com/firmwares/download/47566/T800XXU1BOE2_T800XAR1BOC5_XAR/
Click to expand...
Click to collapse
Thanks, @Ramer - I checked Sammobile earlier this morning, and it wasn't there. They must have posted it later today.
I can't get to it right now, tho, their website may be having issues. I'll try later.
What do you mean the backup was damaged, what failed and which partition?
You can reflash recovery then just restore system. No need to do a full restore.
ashyx said:
What do you mean the backup was damaged, what failed and which partition?
You can reflash recovery then just restore system. No need to do a full restore.
Click to expand...
Click to collapse
Unfortunately. @ashyx - I'm not sure exactly where now. The recovery failure was almost instant (within the first 5 to 10 steps), and I remember that the error occurred right after a progress comment about EXT4. I lost the capability to boot up, and I lost the capability to get into Recovery Mode. My only option was to stay stuck in Download Mode, and hope that my battery didn't die before I was able to get a Odin image re-installed.
It was nerve-wracking.
I wasn't sure if the tablet would be charging while in Download Mode, and there was no way (that I knew of) to get out of Download Mode. I thought there was a high probability that I was about to permanently lose my brand-new tablet.
I paid for a subscription to Sammobile to get an older image installed until someone was able to get me the more recent stock image.
I'm too nervous to try and restore the image again without need, but I will definitely do it if you want me to. I understand the urgency to make sure that TWRP makes good images 100% of the time, and I am reluctant to do anything future to my tablet if I can't make a reliable back-up.
¿GJ?
Maybe your backup somehow got corrupted.
Which partitions were you actually trying to restore? For future reference if you made a backup of recovery don't restore it. Only restore it if you want to revert to a different version.
Also don't worry about bricking your device. As long as you still get download mode you will always be able to recover. I soft brick my tablet on a daily basis lol.
The only thing you need to flash to get into a bootable state is recovery. From recovery you can usually solve most issues. Even if your battery had died you would have been able to charge it and then power it back on. Also the tablet does charge in recovery mode.
Twrp can be a funny so and so sometimes. You just get the one time when it doesn't t behave as you expect. 99% of the time though its pretty solid.
I always find its good practise to restore a backup immediately after making it to ensure its sound. You don't want to wait until its too late to find out its corrupt.
ashyx said:
Maybe your backup somehow got corrupted.
Which partitions were you actually trying to restore? For future reference if you made a backup of recovery don't restore it. Only restore it if you want to revert to a different version.
Also don't worry about bricking your device. As long as you still get download mode you will always be able to recover. I soft brick my tablet on a daily basis lol.
The only thing you need to flash to get into a bootable state is recovery. From recovery you can usually solve most issues. Even if your battery had died you would have been able to charge it and then power it back on. Also the tablet does charge in recovery mode.
Twrp can be a funny so and so sometimes. You just get the one time when it doesn't t behave as you expect. 99% of the time though its pretty solid.
I always find its good practise to restore a backup immediately after making it to ensure its sound. You don't want to wait until its too late to find out its corrupt.
Click to expand...
Click to collapse
Thanks, @ashyx - Good advice on the partition recovery steps. Normally, I have automatically accepted the three defaults, and swiped. I will not do that anymore.
I have found TWRP to be very reliable in the past: If it's working fine, I always get a good backup. If it's failing on something, I always get a bad backup image, or always can't restore. I haven't had a random corruption yet. There was a problem I saw with TWRP and my Samsung GS3 a few years back where it would corrupt compressed archives, but uncompressed archives were fine. Maybe this is a replay on that problem.
I will backup my current CM12.1 image uncompressed, and then try just restoring my system & data partitions from the previous backup, and let you know what happens.
¿GotJazz? said:
Thanks, @ashyx - Good advice on the partition recovery steps. Normally, I have automatically accepted the three defaults, and swiped. I will not do that anymore.
I have found TWRP to be very reliable in the past: If it's working fine, I always get a good backup. If it's failing on something, I always get a bad backup image, or always can't restore. I haven't had a random corruption yet. There was a problem I saw with TWRP and my Samsung GS3 a few years back where it would corrupt compressed archives, but uncompressed archives were fine. Maybe this is a replay on that problem.
I will backup my current CM12.1 image uncompressed, and then try just restoring my system & data partitions from the previous backup, and let you know what happens.
Click to expand...
Click to collapse
I can assure you compressed backups should work fine. I have done it countless times. Probably just a one off for whatever reason, could be a failing sd card. You may find the backup is fine and will be ok to restore. I wouldn't be afraid to try again. When a backup fails to restore you usually only get an error message not a sudden crash and reboot.
Try making a compressed test backup by just backing up the cache partition then restore.
ashyx said:
I can assure you compressed backups should work fine. I have done it countless times. Probably just a one off for whatever reason, could be a failing sd card. You may find the backup is fine and will be ok to restore. I wouldn't be afraid to try again. When a backup fails to restore you usually only get an error message not a sudden crash and reboot.
Try making a compressed test backup by just backing up the cache partition then restore.
Click to expand...
Click to collapse
Well, as a point of reference, I just tried to restore system & data from my older (apparently corrupted) image.
I saw:
...
Wiping System...
Formatting System using make_ext4s function.
Restoring System...
E:extractTarFork() process ended with ERROR=255
I will follow your suggestion, and try writing a compressed Cache backup to see what happens.
¿GotJazz? said:
Well, as a point of reference, I just tried to restore system & data from my older (apparently corrupted) image.
I saw:
...
Wiping System...
Formatting System using make_ext4s function.
Restoring System...
E:extractTarFork() process ended with ERROR=255
I will follow your suggestion, and try writing a compressed Cache backup to see what happens.
Click to expand...
Click to collapse
Is this backup also encrypted. I have seen that error with encrypted backups in the official twrp. However this was fixed with an update pushed to the twrp repo which I have incorporated into the latest build.
Does your version of Twrp show your model number at the top?
ashyx said:
Is this backup also encrypted?
Click to expand...
Click to collapse
Yes.
ashyx said:
Does your version of Twrp show your model number at the top?
Click to expand...
Click to collapse
No, it just shows Team Win Recovery Project v2.8.6.2. It doesn't show any Samsung model numbers (If that is what you are asking).
I installed it using your All-In-One Root/Recovery tool.
Ok I think you're actually running an earlier build. I have updated builds below.
Install one of the f2s versions from the link below.
http://forum.xda-developers.com/gal...p-2-8-6-1-unofficial-sm-t800-805-807-t3074633
ashyx said:
Ok I think you're actually running an earlier build. I have updated builds below.
Install one of the f2s versions from the link below.
http://forum.xda-developers.com/gal...p-2-8-6-1-unofficial-sm-t800-805-807-t3074633
Click to expand...
Click to collapse
Thanks, @ashyx! I'll download the SM-T800 F2FS version right now.
BTW, I've been really interested in installing F2FS. One thing I have been worried about, though, is that once I go down the F2FS path, it may be easy to really mess things up. For example, if I update a ROM, I would always need to use a F2FS ROM, or I might lose all my data - is that right?
Normally you would only format the data and cache partition to f2fs. There isn't much point formatting system to f2fs.
Also f2fs requires a special kernel. Myself and Tkkg1994(Iron Rom) have been working together to get this working properly. Still testing.
We are almost there.
Once formatted to f2fs you would need to reformat back to ext4 and flash a kernel to return back to normal. You could then flash your backup.