Related
So I need to return my Galaxy S3 back to Verizon because the headphone jack broke and thinks that headphones are constantly connected. My problem is I just don't want Verizon to know I've been installing Roms etc. Do you think I can get away with just restoring my phone back to my Stock Rooted backup and deleting superuser or should I go all the way back and ODIN to stock completely?
Odin back to stock and wipe/data factory reset from stock recovery...only takes 10min and could save you hundreds on car insurance!
Failed
droidstyle said:
Odin back to stock and wipe/data factory reset from stock recovery...only takes 10min and could save you hundreds on car insurance!
Click to expand...
Click to collapse
I tried that and fail on loading the “stock.vzw_root66.tar” file. I cannot get any further.
OK post your problems on the new emergency thread and we will help you. No need to hijack someone's thread with your problem. As for the op's dilemma like droidstyle said odin to a stock ROM not the root66 stock ROM since you are returning your phone so no traces of rooting are found.
I have a verizon Galaxy S 3 and I installed this and had no data wipe worked good at first.
http://forum.xda-developers.com/showthread.php?t=1974114
But now it will randomly reboot, doing some odd things. I am not to concerned with data loss but is there an easy was to go back stock with out losing everything, like games I have plays notes etc? Just want to go to the stock rom ota updates..
hunterboy2011 said:
I have a verizon Galaxy S 3 and I installed this and had no data wipe worked good at first.
http://forum.xda-developers.com/showthread.php?t=1974114
But now it will randomly reboot, doing some odd things. I am not to concerned with data loss but is there an easy was to go back stock with out losing everything, like games I have plays notes etc? Just want to go to the stock rom ota updates..
Click to expand...
Click to collapse
No. That is official stock. If you want to Odin flash another stock image, you will need to lose everything to see whether the reboots are gone or not. If you just flashed a no-wipe Odin stock image, I highly doubt that will do anything to resolve your random reboots and other issues.
I've looked around quite a bit, but can't find anyone who has had this problem when restoring. I was trying out Paranoid Android 3.10 D2VZW on my Galaxy SIII, and decided to go back to JellyBam 8.2.0 D2VZW. Both are 4.2.2 ROMs. I rebooted into CWM Recovery, wiped data and cache (can't remember if I wiped the Dalvik), and restored my JellyBam backup. The restore went fine, and I rebooted the system from CWM...nothing! Phone is completely black, no boot up at all. I tried the power button, a battery pull, booting into recovery, and booting into download. When I plug my phone into my computer (a Mac with Windows running in Parallels), I get QHSUSB_DLOAD. So far my research tells me this means my phone is hard-bricked. If I plug in without a battery, I get a red LED light that extinguishes after a few minutes. My understanding of hard-bricking is that it's caused by flashing ROMs not intended for my phone (i.e. an international version ROM). Why would my phone hard-brick if the last thing I did is restore a backup from a previously-working ROM built for my phone? I didn't check the md5, but if the md5 failed wouldn't the restore fail too? I literally can't do anything with my phone. No display, no Odin/download, no recovery. The only indications that it isn't completely fried are the red LED and my computer recognizing the QHSUSB_DLOAD and making a notification sound when it's connected or disconnected. I have no problem sending it to be JTAGed if need be, but I'm not 100% that it's hard-bricked. Any suggestions?
ransdell2 said:
I've looked around quite a bit, but can't find anyone who has had this problem when restoring. I was trying out Paranoid Android 3.10 D2VZW on my Galaxy SIII, and decided to go back to JellyBam 8.2.0 D2VZW. Both are 4.2.2 ROMs. I rebooted into CWM Recovery, wiped data and cache (can't remember if I wiped the Dalvik), and restored my JellyBam backup. The restore went fine, and I rebooted the system from CWM...nothing! Phone is completely black, no boot up at all. I tried the power button, a battery pull, booting into recovery, and booting into download. When I plug my phone into my computer (a Mac with Windows running in Parallels), I get QHSUSB_DLOAD. So far my research tells me this means my phone is hard-bricked. If I plug in without a battery, I get a red LED light that extinguishes after a few minutes. My understanding of hard-bricking is that it's caused by flashing ROMs not intended for my phone (i.e. an international version ROM). Why would my phone hard-brick if the last thing I did is restore a backup from a previously-working ROM built for my phone? I didn't check the md5, but if the md5 failed wouldn't the restore fail too? I literally can't do anything with my phone. No display, no Odin/download, no recovery. The only indications that it isn't completely fried are the red LED and my computer recognizing the QHSUSB_DLOAD and making a notification sound when it's connected or disconnected. I have no problem sending it to be JTAGed if need be, but I'm not 100% that it's hard-bricked. Any suggestions?
Click to expand...
Click to collapse
It's definitely hard bricked, whatever happened is very strange though, as a nandroid doesn't usually mess up your boot partition.
Flashing a rom not intended for your phone can cause a hard brick, but that's not the only way it can happen. Somewhere in the restore process your boot partition got corrupted. Your base coding somehow is not being recognized, and your computer and phone can't tell what's supposed to run. A jtag is really your only option.
TWRP offers you the option to disable the boot and recovery partition when restoring. After you fix your phone, I'd recommend trying that out so you're absolutely sure your boot partition doesn't get touched. Those really don't need to be restored anyway.
Sorry that happened to you.
Sent from my SCH-I535 using Tapatalk 2
Bummer. Thanks for the input. I kinda figured that was the case, but was hoping I was missing something. Guess I'm going to have it JTAGed, probably by Mobile Tech Videos. The process looks fairly simple. If the equipment costs were comparable to having someone else do it I might do it myself, but if that were the case everyone else would be doing that too! I'll let you know how it goes.
ransdell2 said:
Bummer. Thanks for the input. I kinda figured that was the case, but was hoping I was missing something. Guess I'm going to have it JTAGed, probably by Mobile Tech Videos. The process looks fairly simple. If the equipment costs were comparable to having someone else do it I might do it myself, but if that were the case everyone else would be doing that too! I'll let you know how it goes.
Click to expand...
Click to collapse
I think the price is reasonable if you factor in equipment and labor.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
I think the price is reasonable if you factor in equipment and labor.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Got my phone JTAGed by Patrick Walls (whose service is available on eBay for ~$35), and it works great. Fast service and great communication from Patrick. The phone came back unrooted with a stock 4.1.2 ROM. Of course I immediately re-rooted it and flashed a fresh JellyBAM ROM to it (with a huge feeling of trepidation), and so far everything is working, with the exception of the camera (I get "Can't connect to camera" after taking one picture, and a reboot is the only thing that enables the camera again, for one pictures, then can't connect, reboot, one pic, can't connect, etc.).
Having never hard-bricked before after many, many ROM changes on a Fascinate and about 10 ROM changes on my S3, I'm a little nervous about changing them now. Is my hesitation unfounded providing I don't mess with the bootchain? To root my phone I flashed the VRALEC bootchain, then TWRP, then rooted, then JellyBAM, then the VRBMD3 bootchain, as per this rooting guide:
http://forum.xda-developers.com/showthread.php?t=2046439
Now that I've put my phone back to the Jelly Bean bootchain, I should be free to flash ROMs built for my device without a serious concern about hard-bricking, right?
ransdell2 said:
Got my phone JTAGed by Patrick Walls (whose service is available on eBay for ~$35), and it works great. Fast service and great communication from Patrick. The phone came back unrooted with a stock 4.1.2 ROM. Of course I immediately re-rooted it and flashed a fresh JellyBAM ROM to it (with a huge feeling of trepidation), and so far everything is working, with the exception of the camera (I get "Can't connect to camera" after taking one picture, and a reboot is the only thing that enables the camera again, for one pictures, then can't connect, reboot, one pic, can't connect, etc.).
Having never hard-bricked before after many, many ROM changes on a Fascinate and about 10 ROM changes on my S3, I'm a little nervous about changing them now. Is my hesitation unfounded providing I don't mess with the bootchain? To root my phone I flashed the VRALEC bootchain, then TWRP, then rooted, then JellyBAM, then the VRBMD3 bootchain, as per this rooting guide:
http://forum.xda-developers.com/showthread.php?t=2046439
Now that I've put my phone back to the Jelly Bean bootchain, I should be free to flash ROMs built for my device without a serious concern about hard-bricking, right?
Click to expand...
Click to collapse
Glad you got it working.
There's always a risk of something going wrong and a hard brick reoccurring, you just had bad luck. I don't think your brick had anything to do with your bootchain.
I think what probably happened was when you made a nandroid in cwm, the boot partition somehow got corrupted. CWM by default restores your boot, recovery, data, system, and cache partitions. In the advanced restore section, you can restore one at a time but you have no way of simply disabling a particular partition from being restored. I think since the boot partition was messed up, it erased your good data and hard-bricked your phone.
TWRP by default only backs up your data, cache, and system partitions and leaves your boot and recovery partitions alone. If you restore that backup, then there's pretty much no way a hard brick can happen. I can't think of any reason why you really need to backup your recovery or boot partition.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Glad you got it working.
There's always a risk of something going wrong and a hard brick reoccurring, you just had bad luck. I don't think your brick had anything to do with your bootchain.
I think what probably happened was when you made a nandroid in cwm, the boot partition somehow got corrupted. CWM by default restores your boot, recovery, data, system, and cache partitions. In the advanced restore section, you can restore one at a time but you have no way of simply disabling a particular partition from being restored. I think since the boot partition was messed up, it erased your good data and hard-bricked your phone.
TWRP by default only backs up your data, cache, and system partitions and leaves your boot and recovery partitions alone. If you restore that backup, then there's pretty much no way a hard brick can happen. I can't think of any reason why you really need to backup your recovery or boot partition.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Great, thanks for the info! I'll make sure that the boot and recovery partitions aren't touched in the future. I've primarily used CWM, but am probably just going to stick with TWRP.
I'm having issues with my Galaxy S6. I used Odin to return to stock, and now I'm getting an "Unfortunately, IMS Service has stopped" error every 2 or 3 seconds. The phone is essentially unusable.
Other Galaxy phones have had similar issues, and I've tried some of their suggestions. I wiped Media Storage and factory reset the phone through the recovery. I tried to find the DRM app to wipe, but it's not there in the app manager. Does anybody have any suggestions? They are greatly appreciated.
Thanks in advance.
Im having that same issue. I bricked my phone for about a week and I had just got the tar files to open and return my device to stock. Is it saying you have service? Ive been looking this up everywhere and have no luck with the s6 problem.
boristhebladexx said:
I'm having issues with my Galaxy S6. I used Odin to return to stock, and now I'm getting an "Unfortunately, IMS Service has stopped" error every 2 or 3 seconds. The phone is essentially unusable.
Other Galaxy phones have had similar issues, and I've tried some of their suggestions. I wiped Media Storage and factory reset the phone through the recovery. I tried to find the DRM app to wipe, but it's not there in the app manager.
Click to expand...
Click to collapse
Why did you return to stock? If you are planning to return/exchange the phone, then you may run into trouble if it is unusable.
3 options:
1. Attempt to reflash stock via Odin and hope it fixes the problem.
2. Restore a nandroid.
3. Clean flash a custom rom.
sublimaze said:
Why did you return to stock? If you are planning to return/exchange the phone, then you may run into trouble if it is unusable.
3 options:
1. Attempt to reflash stock via Odin and hope it fixes the problem.
2. Restore a nandroid.
3. Clean flash a custom rom.
Click to expand...
Click to collapse
i tried to reflash stock again and the same message kept coming up. i thought that restoring would wipe root so i dont know how you could flash a custom rom onto it. would you do that through the Odin program??
LiquidPhoenix said:
i tried to reflash stock again and the same message kept coming up. i thought that restoring would wipe root so i dont know how you could flash a custom rom onto it. would you do that through the Odin program??
Click to expand...
Click to collapse
Did you try restoring a nandroid?
Sent from my SM-G920T using Tapatalk
sublimaze said:
Did you try restoring a nandroid?
Sent from my SM-G920T using Tapatalk
Click to expand...
Click to collapse
i never backed up a nandroid. im pretty new to android phones and the deep stuff because the only thing i ever learned was iphone. do they auto backup? and if so, how could i restore it??
thank you for your patience, i know its driving you crazy haha.
LiquidPhoenix said:
i never backed up a nandroid. im pretty new to android phones and the deep stuff because the only thing i ever learned was iphone. do they auto backup? and if so, how could i restore it??
Click to expand...
Click to collapse
Android lollipop gives you the option to transfer your apps to a new device when you setup the new device. You are also given this option when you flash a custom lollilop rom, because the setup wizard will see this as a new device. However, you should always make a backup of a good working rom setup prior to flashing a new rom or any mods. When I say a "good working rom ", I mean a rom that you might possibly want to go back to, in case your next rom flash doesn't go well or it has major issues that prevent you from using it as a daily driver (which you won't know until you flash it, obviously). The stock rom is definitely a "good working rom", and you should ALWAYS make a backup of stock before flashing anything else.
Since you don't have a backup of stock, then you are stuck with Odin getting you back to bone stock, which apparently isn't quite doing the job. The only other thing I can suggest is flashing a stock rooted rom (eg, no mods other than root). But make sure you clean flash, which also means mounting & wiping /system in recovery. I forgot how to do it in CWM/Phil's recovery, but in TWRP go to Mount, tap /system then go back to the main menu, go to Wipe > Advanced and select cache, dalvik cache, data and system, then swipe to erase. Now you have a totally clean slate.
sublimaze said:
Android lollipop gives you the option to transfer your apps to a new device when you setup the new device. You are also given this option when you flash a custom lollilop rom, because the setup wizard will see this as a new device. However, you should always make a backup of a good working rom setup prior to flashing a new rom or any mods. When I say a "good working rom ", I mean a rom that you might possibly want to go back to, in case your next rom flash doesn't go well or it has major issues that prevent you from using it as a daily driver (which you won't know until you flash it, obviously). The stock rom is definitely a "good working rom", and you should ALWAYS make a backup of stock before flashing anything else.
Since you don't have a backup of stock, then you are stuck with Odin getting you back to bone stock, which apparently isn't quite doing the job. The only other thing I can suggest is flashing a stock rooted rom (eg, no mods other than root). But make sure you clean flash, which also means mounting & wiping /system in recovery. I forgot how to do it in CWM/Phil's recovery, but in TWRP go to Mount, tap /system then go back to the main menu, go to Wipe > Advanced and select cache, dalvik cache, data and system, then swipe to erase. Now you have a totally clean slate.
Click to expand...
Click to collapse
Ive tried looking online for software thats compatible with my carrier (cricket) but I couldnt find it. The way that I bricked my phone was trying to flash TWRP recovery on my phone. Cricket is through at&t and has the locked bootloader. I used pingpong root to root it but apparently it wasnt compatible with my phone. I'm kinda stuck.
LiquidPhoenix said:
Ive tried looking online for software thats compatible with my carrier (cricket) but I couldnt find it. The way that I bricked my phone was trying to flash TWRP recovery on my phone. Cricket is through at&t and has the locked bootloader. I used pingpong root to root it but apparently it wasnt compatible with my phone. I'm kinda stuck.
Click to expand...
Click to collapse
I have never messed with Cricket phones. I know they piggyback on the AT&T network, but I don't know if the firmwares are different. You could go to a Cricket store and look at the display S6 to find out the exact firmware version, and try to find that on the web (posting in the AT&T forum might yield a faster response). But trying to flash TWRP was not a good idea. Good luck!
I was attempting to return the phone to stock so I could sell it. I flashed the Cricket firmware, and ever since then I get the IMS service error. I can't flash a new ROM because I unrooted through Pingpong Root. When I flash through Odin, I only flash the AP .tar. Would it make a difference if I flashed all 4 (BL, AP, CP, CSC)?
boristhebladexx said:
I was attempting to return the phone to stock so I could sell it. I flashed the Cricket firmware, and ever since then I get the IMS service error. I can't flash a new ROM because I unrooted through Pingpong Root. When I flash through Odin, I only flash the AP .tar. Would it make a difference if I flashed all 4 (BL, AP, CP, CSC)?
Click to expand...
Click to collapse
I tried this just now and all it said was "attempt thread failed (0/0)"
boristhebladexx said:
I was attempting to return the phone to stock so I could sell it. I flashed the Cricket firmware, and ever since then I get the IMS service error. I can't flash a new ROM because I unrooted through Pingpong Root. When I flash through Odin, I only flash the AP .tar. Would it make a difference if I flashed all 4 (BL, AP, CP, CSC)?
Click to expand...
Click to collapse
Yes it does make a difference to flash it into 4 different parts in case you have the entire firmware
Just wanted to throw my 2 cents in here, i woke to this lovely issue, which was rendering my phone unusable. I use a program call YouMail for voicemail, creeps my friends out when they get to my voice mail. Uninstall this program after wiping every cache imaginable, voila, no more issue. I haven't tried to reinstall it yet since i need to get some work done. Hope it helps in some way.
I have the same problem after flashing the stock firmware thru Odin on my S6 from Cricket. I also tried Factory Resert and Wiping the Cache, nothing seems to help at all. I get the annoying message about the IMS service. I've tried clearing the cache from contacts, ims service but no luck at at. Is there any other ROMs out there for the S6 from Cricket. Right now my phone is completely stock and has no service. Any word of advice would help, Thanks !
Edit: I flashed the CSC file thru odin and it got rid of the IMS error but now I have no service.
SRobby said:
Just wanted to throw my 2 cents in here, i woke to this lovely issue, which was rendering my phone unusable. I use a program call YouMail for voicemail, creeps my friends out when they get to my voice mail. Uninstall this program after wiping every cache imaginable, voila, no more issue. I haven't tried to reinstall it yet since i need to get some work done. Hope it helps in some way.
Click to expand...
Click to collapse
Not an expert in any sense of the term, so ignore this if it's dumb. When the OP and others having this issue are bringing your phones back up, does the issue start prior to phone setup? Or is your Google account restoring some app that could be causing the issue?
it didnt solve my problem
I have the s6 edge though ..do i have to wipe and install the rom again??
Unfortunately ims has stopped working pop up
I noticed the spinning sync icon at the top my s7 phone. It was constantly trying to sync my messengers app to the cloud. (I tuned the sync function off an it seems to have stopped the annoying message from popping up. :good::fingers-crossed:
eeee
boristhebladexx said:
I was attempting to return the phone to stock so I could sell it. I flashed the Cricket firmware, and ever since then I get the IMS service error. I can't flash a new ROM because I unrooted through Pingpong Root. When I flash through Odin, I only flash the AP .tar. Would it make a difference if I flashed all 4 (BL, AP, CP, CSC)?
Click to expand...
Click to collapse
just root the device an then install root unistaller
find all apps with the word ims
unistall all apps
restart phone
Magic!!!!
My trusty S6 running rooted Android 5.0.2 has decided to act up, more specifically, it crashes and reboots ever more frequently. I can run stress tests and other test apps fine, but when I actually load apps and start using them it crashes after anything from 20 secs to a couple of minutes. This has happened before, but then wiping, etc fixed it. My suspicion is that the nand flash has gone bad. So I'm wondering what the most comprehensive flash erase and reprogramming is that I can do? I've used FlashFire to reflash the CleanROM Lite 1.1 that I use and I've wiped data and cache. That made the device stay up for a couple of minutes instead of just seconds...
Some questions:
- is there any trick to rewrite more of the flash or identify bad blocks permanently?
- if I use Odin, does that provide additional options? An issue is that I haven't been able to find Odin files for OE2...
It's clear to me that I need a new phone, but given the timing of announcements and availability it would be really great if I could eek out a few more weeks on this one...
Odin would be the smart way to go. It has everything needed to wipe the phone, install new ROMs and root
Snowby123 said:
Odin would be the smart way to go. It has everything needed to wipe the phone, install new ROMs and root
Click to expand...
Click to collapse
Quick update: I did find OE2 for Odin somewhere and flashed that using Odin. It restored my S6 to life! So I assume that some flash sectors in the parts that don't get reflashed by FlashFire were corrupted and using Odin did the trick. Thanks for the nudge!