Need serious help resetting phone - HTC One X

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.

Related

Urgent Help required, phone faulty after update

Hey there,
I have been running a froyo villainrom (1.6 i think) on my DHD and it was all running fine. I decided to update to the new CM7 so did a backup and wiped everything then flashed the new rom. It stayed on the loading screen for more than 20 mins. Eventually it turned off, each time i turned it on it did the same thing until finally it booted but I was greeted with force closes of the quick start, the keyboard, plus a whole lot of other stuff i dont remember. I decided to reflash CM7 and I ended up with the same problem, except this time it told me my SD card was faulty, I tried rebooting, removing and replacing teh SD card and kept getting the same error. Even my computer wont mount it
I got a spare card from the draw and put CM7 on that and the exact same problem occured, although this time when put into a PC i got the option of formatting it so I did. I then downloaded a CLeanDHD rom and flashed that after wiping everything once again. I still get force closes and cant get past inputting my google account details without the phone reseting again.
I cant restore to my backup as the phone does not recognise the card I made the backup on, nor can I access that card using my computer.
Any help is greatly appreciated.
Im using clockwork mod 3.0.0.6
Thanks in advance
02keilj said:
Hey there,
I have been running a froyo villainrom (1.6 i think) on my DHD and it was all running fine. I decided to update to the new CM7 so did a backup and wiped everything then flashed the new rom. It stayed on the loading screen for more than 20 mins. Eventually it turned off, each time i turned it on it did the same thing until finally it booted but I was greeted with force closes of the quick start, the keyboard, plus a whole lot of other stuff i dont remember. I decided to reflash CM7 and I ended up with the same problem, except this time it told me my SD card was faulty, I tried rebooting, removing and replacing teh SD card and kept getting the same error. Even my computer wont mount it
I got a spare card from the draw and put CM7 on that and the exact same problem occured, although this time when put into a PC i got the option of formatting it so I did. I then downloaded a CLeanDHD rom and flashed that after wiping everything once again. I still get force closes and cant get past inputting my google account details without the phone reseting again.
I cant restore to my backup as the phone does not recognise the card I made the backup on, nor can I access that card using my computer.
Any help is greatly appreciated.
Im using clockwork mod 3.0.0.6
Thanks in advance
Click to expand...
Click to collapse
who is your provider? im not 100% on this on the desire hd, but on the standard desire, you would find your providers RUU rom then flash that to return you to stock then youd have too reroot. but like i said, imma desire user who just got a dhd, so ask some1 with alil more knowldge
Did you do a full wipe, before flashing CM7? If not run one now (i.e wipe /system / cache /data and /dalvik-cache from CWR) before re-flashing CM7. With multiple FC's that is normally the issue, going back to a non cm ROM, not entirely sure about CleanDroid, is problematic without carrying out a full wipe also and may even require using an older version of CWR, see CleanDroid thread for more info on that.
Thanks for the replies guys, yes I did a full wipe of cache/dalvik and factory before flashing.
If i were to try and install a stock rom and was greeted with force closes again, what would that mean about having to re-root the device? I dont want to really loose root access if im going to have to keep trying to fix it
Ok so ive decided to restore it to stock rom. Will this be possible if my phone cant connect to the PC to sync with HTC sync?
02keilj said:
Thanks for the replies guys, yes I did a full wipe of cache/dalvik and factory before flashing.
If i were to try and install a stock rom and was greeted with force closes again, what would that mean about having to re-root the device? I dont want to really loose root access if im going to have to keep trying to fix it
Click to expand...
Click to collapse
it's 90% about wiping problem. maybe you missed "format data"
make sure you have cwm 3.0.0.6 and do full wipe ( i personally recommended full wipe 1.3 here http://forum.xda-developers.com/showthread.php?t=868720 , don't do it manually if this is your first time flashing custom rom. )
before that, make sure you have the working .zip rom. check md5 before transfer to sdcard. then do this step .
cwm -> install zip from sdcard -> choose zip from sdcard -> full wipe 1.3.zip -> choose zip from sdcard -> "your-rom-to-flash".zip -> reboot .
hedayat7 said:
it's 90% about wiping problem. maybe you missed "format data"
make sure you have cwm 3.0.0.6 and do full wipe ( i personally recommended full wipe 1.3 here http://forum.xda-developers.com/showthread.php?t=868720 , don't do it manually if this is your first time flashing custom rom. )
before that, make sure you have the working .zip rom. check md5 before transfer to sdcard. then do this step .
cwm -> install zip from sdcard -> choose zip from sdcard -> full wipe 1.3.zip -> choose zip from sdcard -> "your-rom-to-flash".zip -> reboot .
Click to expand...
Click to collapse
Thanks, I have made sure I didnt miss the full wipe. Ive re-tried wiping and flashing between CM7 and CleadDHD at least 20 times with the same problems. I think ill format my SD card and then copy the files across again. Ill also try the Full wipe 1.3 and see if that helps.
Im wondering if my friend makes a backup of his DHD through Clockwork 3.0.0.6 and then copies the backup file from his SD card to mine, will I be able to restore that backup?
Then from there I can factory reset again to wipe his saved settings?
Thanks for the replies so far guys
Is it possible my clockwork is faulty? I treid updating it through rom manager prior to flashing CM7 and it failed but i assumed it just reverted back to what I already had before. Is there a way I can reinstall clockwork through the current version?
nice idea .. take your friend's sd card that have nandroid backup, and then restore back the nandroid. i think it will work.
hedayat7 said:
nice idea .. take your friend's sd card that have nandroid backup, and then restore back the nandroid. i think it will work.
Click to expand...
Click to collapse
I will probably make a copy of it rather than use theirs, just in case it ruins their card like it did mine. Would I have to copy their EXT partition data too? If so I can easilly do that in ubuntu yes?

HELP! Boot loop on stock ROM

Hi guys!
I am sorry if this has already been answered somewhere, but I searched pretty thoroughly and I couldn't find a solution
I am trying to S-OFF an HTC Desire for a friend of mine and install CyanogenMod using this guide http://forum.xda-developers.com/showthread.php?t=1016084.
We rooted the phone without any issues, but before going through Alpharev I decided to make a nandroid backup through the phone's original recovery image (just as advised on Alpharev's site: "We try to leave the current ROM and datastructures completely intact. It is, however, advised to ALWAYS nandroid backup your phone before you run this procedure.
You will then always have a correct/current backup to fall back on in case something breaks."). So I just went into the Backup and Recovery menu and I chose backup.
Unfortunately after backing up, the phone went into a boot loop. We tried taking-out the battery and even doing a hard reset but nothing helped. Eventually we flashed the original RUU from O2 (it's an O2 Germany phone) and this fixed the issue.
I am a bit concerned since I wasn't able to find anyone who had the same problem and it is a bit weird that the phone should go into a boot loop without even installing another ROM or anything - just trying to do a backup of the stock ROM. I am thus a bit hesitant to go on with the S-OFF...
Any help would be deeply appreciated!
Well, first of all, you don't need to be S-Off to install CyanogenMod7. Only root. Usually, people do S-Off so they can change the Boot Splash image.
Make a Gold Card for your SD. Some Desire's need it, some don't. Better safe than sorry.
Secondly, after root, I would goto the market and install ROM Manager. Then flash to the latest Clockwork Recovery.
Then,I would make sure I have a recent Recovery image (NandBackup)
Download Gapps.zip to the root of the SD.
Download the CyanogenMod7 to the root of the SD, boot phone to recovery, Wipe cache memory, also goto Advanced and wipe the Delvik memory.
Then Install from SD, do the CM7, then after it finishes, Select Install from SD again, and install the Gapps.zip
Why your backup failed, who knows. I suppose you were using Unrevoked?
Thanks! Do you know why the boot loop could happen?
Moscow Desire said:
Well, first of all, you don't need to be S-Off to install CyanogenMod7. Only root. Usually, people do S-Off so they can change the Boot Splash image.
Make a Gold Card for your SD. Some Desire's need it, some don't. Better safe than sorry.
Secondly, after root, I would goto the market and install ROM Manager. Then flash to the latest Clockwork Recovery.
Then,I would make sure I have a recent Recovery image (NandBackup)
Download Gapps.zip to the root of the SD.
Download the CyanogenMod7 to the root of the SD, boot phone to recovery, Wipe cache memory, also goto Advanced and wipe the Delvik memory.
Then Install from SD, do the CM7, then after it finishes, Select Install from SD again, and install the Gapps.zip
Why your backup failed, who knows. I suppose you were using Unrevoked?
Click to expand...
Click to collapse
I suppose, there was some code that didn't get deleted due to the rooting process, if you used unrevoked. Although it rarely happens, sometimes it does.
Or maybe it didn't like some Application. Who knows. All it takes, is 1 peice of bad code.
With AlphaRev, although many use it, I believe it changes your bootloader code.
And, you can sometimes have problems as well.
But follow the steps I mentioned, and you should be ok.
Just make sure you create and use the Gold Card first.
The boot loop is a common issue with the first nandroid. All you had to do was restore the nandroid you just made.
Sent from my HTC Desire using XDA Premium App
TheGhost1233 said:
The boot loop is a common issue with the first nandroid. All you had to do was restore the nandroid you just made.
Sent from my HTC Desire using XDA Premium App
Click to expand...
Click to collapse
Right - I thought about that, but then I was hesitant, because I figured if it went into a boot loop then it probably did not create the backup image properly... So can I still restore the backup image now? It is saved on the sdcard so it should be intact after the RUU, right?
It "should be", but, one can only assume so.
Typically, I make a couple of backups each week. One never knows. Yeah, it will tell you successsful. but, better safe than sorry.

Sorry if this has been posted already...

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

[SPH-L710] CWM image.zip backup got phone stuck in Samsung Logo Loop

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!

Stuck on boot after re-installing stock recovery

Hi, when I got the phone I rooted it by installing TWP recovery, it was all working fine after that until an OTA update popped up, after some research I learned that in order to install OTA updates you need to install stock recovery. Firstly, not knowing entirely what I was doing I installed the stock recovery for the wrong software version. The phone booted however and I tried to install the OTA update, upon restarting I was met with the "red triangle" error screen. I restarted the phone and it booted up fine.
Then having found the correct stock recovery (4.16.401.10) I installed it and ran the update again. It seemed to be going fine with the loading bars moving along nicely when it got stuck on the HTC bootup logo. From here I restarted it and now the phone turns on, shows the htc logo, then gets stuck on a black screen,
Please help, Thanks.
http://forum.xda-developers.com/htc-one-m8/help/boot-loop-problem-t3194508
ckpv5 said:
http://forum.xda-developers.com/htc-one-m8/help/boot-loop-problem-t3194508
Click to expand...
Click to collapse
Hi, thanks for that, I guess I should have searched around harder. One question though, you mention that there is a way to restore just system to keep your data, I don't wanna loose all of my data so I'd like to do that, I'm just not sure how to apply that to your guide, what is it that I have to do differently to keep my data?
Thanks.
DarwinW said:
Hi, thanks for that, I guess I should have searched around harder. One question though, you mention that there is a way to restore just system to keep your data, I don't wanna loose all of my data so I'd like to do that, I'm just not sure how to apply that to your guide, what is it that I have to do differently to keep my data?
Thanks.
Click to expand...
Click to collapse
2 options :
1.
In step 8, select dalvik cache, cache, system but don't select data
In step 9, tick only boot & system and don't tick data
or
2.
Make a nandroid backup of your current ROM
Do all the steps, once completed the OTA reinstall TWRP and restore only data from your earlier made nandroid backup
Thank you so much, you're amazing. Just creating a backup now. So once I've flashed the stock rom and the TWRP recovery to restore my data, if I then install the stock recovery again, should it all work fine? or does changing the recovery at any point stop OTA updates working?
The reason I rooted my phone to start with was to use titanium backup to restore apps from a previous phone, so if I can get the phone all stock just with my data, then I don't really need root.
Thanks!
DarwinW said:
Thank you so much, you're amazing. Just creating a backup now. So once I've flashed the stock rom and the TWRP recovery to restore my data, if I then install the stock recovery again, should it all work fine? or does changing the recovery at any point stop OTA updates working?
The reason I rooted my phone to start with was to use titanium backup to restore apps from a previous phone, so if I can get the phone all stock just with my data, then I don't really need root.
Thanks!
Click to expand...
Click to collapse
That's almost same as option 1 above. You need stock recovery for OTA to work.
Most important is the system part must be stock with nothing changed.
Personally, I always do option 2 to make sure OTA is successfully done .. then restore data.
One thing to note ... you don't need to relock bootloader doing all these process.
Also, now that I've created the backup (stored to the phones storage), how do I transfer that to my PC, since the phone doesn't boot, the computer doesn't recognize the storage.
Thanks.
In TWRP you have option to enable MTP then both your internal storage and microSD can be opened on PC
Make sure to use TWRP 2.8.4.0 or newer or latest. I'm still on TWRP 2.8.6.0
It seems I'm on an older version of twrp (2.7.0.2), I made the backup using this version. If I update to a newer version now will the restore work properly?
Thanks.
Usually yes we can restore a backup made with older TWRP version but I'm not so sure about 2.7.0.2 as that is the buggiest TWRP among all versions but very popular because it is included in one very old and not updated toolkit.
Why don't install latest/newer TWRP then redo the backup then transfer to PC.
I'm having trouble viewing files on my pc, I select "mount" from the main twrp menu, it then shows a screen to select which partitions to mount, I tick them, then nothing happens. There's no button to actually start the mount.
I did mentioned enable MTP function ... see below on the right side you should see Disable MTP or Enable MTP (beside Mount USB Storage) .. not those partitions to mount (but in the same screen)
I think you were right about that version being buggy. Those buttons on the bottom were missing. Just installed the latest twrp and I can mount now as the buttons to mount are showing up. Hopefully all will be fine now
Thanks.
Hi, I'm following the guide now and when I try to wipe the phone it doesn't work, I get:
Wipe Complete
Failed
"Unable to mount /cache
failed to wipe dalvik"
This error repeats a few times.
Thanks.
EDIT** scratch that, sorted it
Horray! Everything has now worked out and my phone is back to it's old self with the update, thank you so much ckpv5! you're the best.

Categories

Resources