I used the 1 click toot method and thought I may return my fascinate. I decided against it and tried to root again with no luck. The root always has a bunch of FC's and eventually gets stuck. The generic ringer also starts with no way to stop it. Only a battery pull will restart the phone afterward. I have also already really installed the Samsung drivers for the phone. Anybody have any thoughts?
Did you go back to stock via odin...if not do so...and push root manually...instead of an app.
I did through Odin. Tried to push root manually last night. The phone froze right after the push and never recovered. Had to battery pull. I had all of the files pushed and got to the chmod and wait stage when it froze.
Hmm, maybe re push to stock in odin...make sure you are doing the correct files...though it sounds like you did...a second time around sometimes seems to hit the spot...droid used to give me the same issues with sbf.
Do a factory data reset after you redo the odin recovery. Make sure you are using the verizon file when pushing each flash and doing it in the proper order. Then manually root, dont use one click or an app.
Also remember to push the files one at a time and let the phone restart between each one booting back into download mode.
Sent from my SCH-I500 using XDA App
I've been working all weekend so I havent had too much time to deal with it. I wiped data and cache in the recovery menu initially and then the phone wouldn't allow me to sign back into my Google account. It kept telling me that I didn't have a data connection on 3g OR wifi. I finally did a factory reset through the privacy menu (not in recovery) and all seems to finally be working and completely stock. Now off to root and flash voodoo...
hey i had the same problem i made a post on how to fix it though.. go to the 0.00 internal storage issue mine was doing what u said plus more but i fixed it just follow the steps i set
http://forum.xda-developers.com/showthread.php?t=804457
Got it. Just for the record: Rooted, Flashed all three files with Odin to get "back to stock". Re-OTA'd. Somehow Busybox and Su were still there so I manually removed. Then changed my mind about returning the phone and attempted to root again with no luck. Re-flashed through Odin ok, then attempted root but errors prevented finish. Cleared data and wiped cache through recovery. Then my google account wouldn't resync b/c of network connection error, even though I had a working data connection the entire time. Tried booting into recovery and clear and wipe data again. No luck. Finally decided to use factory data reset from within settings. Now all clear, rooted again, re-synced my google account and all good. You guys rock. Thanks for the help.
Related
I was wondering if I do a factory reset, will my back up folders from rom manager and titanium back up be deleted?
Thanks in advance
Sent from my SGH-T959 using XDA App
I posted this in another thread about my experience with Factory Reset
If you have removed any bloatware I do not recommend it
------
Hello,
I just wanted to share my experience and possibly prevent other people from going through it.
I recently received my first Vibrant and it happen to be one of the defective units unable to enter recovery via HW. Of course at the time I did not realize this was a problem and was new to the phone and android in general.
I rooted the phone and removed 5 or 6 bloatware apps (Telenav, Audio Postcard, etc... Nothing important) So im installing and uninstalling apps you know how it goes and I think you know I just kinda want to clear everything out and remove all the user data. I understand the bloatware I removed will not come back but thats better for me so I wont have to remove it again. So I use ADB reboot into recovery and select Erase User Data.
It formats and I reboot. Right away nothing works and I get a constant force close loop of just about every app trying to open including TouchWiz which I didnt remove so it should be fine. Well I think this sucks at least you can always flash to stock. DING thats when it hit me and I realized I now had no way to get into recovery or download mode to even attempt running a recovery. SO I had to have my phone replaced. The replacement phone Is not defective and I can access everything via HW buttons. I wanted to see if i could duplicate my issue. So I do a backup of stock right away. Then I proceed to remove bloatware etc...
I factory reset and again force closes
I nandroid back to the stock reference I made and boots fine No defect in the phone No Problem this time correcting it. I do a factory reset at that point and works fine.
Point I guess is after all this is if you have a HW Locked defective phone and have removed bloatware NEVER RUN A FACTORY RESET unless you have put the bloat back on... Would have saved me from having to get a replacement though I guess that was better cuz now I have a phone that works properly.
So i got this lovely update from Verizon. I rooted using the one touch but never made any changes to the phone. Still using default UI etc. Just rooted to access saves, overclocking.
So the update reboots the phone, starts installing, and fails. Then i can go to the menu and reboot the phone. It will come all the way on, and immediately just shuts down and tried the update again. Stuck in this vicious cycle. Help?
Mount the SD card either in recovery or on a PC and see if there is a PG05IMG.zip on it. Remove it if so, then reboot.
tqhx said:
So i got this lovely update from Verizon. I rooted using the one touch but never made any changes to the phone. Still using default UI etc. Just rooted to access saves, overclocking.
So the update reboots the phone, starts installing, and fails. Then i can go to the menu and reboot the phone. It will come all the way on, and immediately just shuts down and tried the update again. Stuck in this vicious cycle. Help?
Click to expand...
Click to collapse
You can't install an OTA if your rooted, even if you haven't made any changes. The problem is the custom recovery (e.g. ClockworkMod)
When the update tries to install the updated recovery, it sees that the old stock recovery isn't there, and fails.
As far as recovering from that, I'm not entirely sure.
Seeing as you used the one touch root, I doubt you installed the S-Off eng bootloader. Try what the above poster suggested first.
Thanks for the replies guys. I did have s-off, but yeah ill tell you i tried what he suggested with no luck.
I ended up being ok i made another clockwork backup, did a full restore from a backup before the date of the update, then did just a data restore from the backup i had just made. Phone is back to normal. Thanks for the responses, ill give you both marks for being helpful
I'm in the same boat, except I was silly enough to not have a backup made. I do not see the PG05IMG.zip from recovery. Any other possible ways to fix this? If I have to clear all my data and start again, I'm ok with that though I'd obviously prefer not to do that.
Boot into clockwork recovery and wipe cache only.
Sent from my HTC Thunderbolt
This same issue has happened to me with the Verizon update. Long story on how it i clicked okay to the update. I told it reject at least 3 times already.
Anyway - i was stuck in this nasty reboot cycle. I was lucky to have a backup from March when I first rooted my TB. Not having a more recent backup is my bad.
So I have worked most of today with near factory settings from my recovered backup and now I am restoring todays backup to see if I can fix this reboot BS.
I did the Wipe Cache from ClockMod and when the phone rebooted it gave the prompt to reinstall the update which I cancelled. So success!!! Now I can clean up my junk apps and do a proper backup to protect myself in the future.
I've been trying to root my wife's HTC Rhyme and in my efforts, something hosed the WiFi. All I get is "ERROR" under WiFi in the wireless network settings menu. This happened to me once or twice on my incredible and a kernel re-flash fixed it. I really want to root it so that she can have the benefit of being able to completely backup everything. I've tried ZergRush, TocoRoot, SuperTool, OneClick, SuperOneClick... none of it worked. The only thing that I've been able to do successfully is unlock/re-lock the bootloader.
Is it possible to extract the ROM and/or all critical system files from a stock rooted phone and use them to restore another phone that is malfunctioning? I was thinking that if I found someone with a rooted HTC Rhyme who would be willing, they could send me whatever files I would need to completely restore the phone, WiFi and all.
Any help with at least the WiFi issue wold be appreciated. Rooting would be nice too but I don't want to be greedy.
Thanks.
I was able to install an RUU which fixed the WiFi issue, but now the phone is stuck in a boot-loop. I've flashed it three times (doing it twice each attempt) but its the same result every time. The phone boots normally the first time, then goes into loop on the next restart. Could be the wrong RUU, could be corrupted or maybe I'm doing it wrong. I don't know.
Please... Any suggestions would be most appreciated.
I fixed it.
RuLEoF2 said:
I fixed it.
Click to expand...
Click to collapse
So have you finally rooted your Rhyme successfully? Which tool did you use? Thanks!
itandy said:
So have you finally rooted your Rhyme successfully? Which tool did you use? Thanks![/QUOTE No root, but it's working and back to No root, but it's working and back to factory condition. factory condition.
I used CWM recovery to format all partitions I used CWM recovery to format all partitions (data, system, cache, devlog, etc.) as well as (data, system, cache, devlog, etc.) as well as the sdcard. the sdcard. Once that was done, I relocked the Once that was done, I relocked the bootloader and ran the RUU. bootloader and ran the RUU. This time I went This time I went through the entire setup process for the phone through the entire setup process for the phone (activation, market account, WiFi and so on) (activation, market account, WiFi and so on) without rebooting first. without rebooting first. After the setup, I After the setup, I rebooted and I started normally. rebooted and I started normally. About 20 About 20 minutes later, I got an android OTA update of minutes later, I got an android OTA update of some kind and now its fine. some kind and now its fine.
Not sure why setting up the phone would make Not sure why setting up the phone would make a difference, but formatting the partitions and a difference, but formatting the partitions and going completely clean-slate is probably what going completely clean-slate is probably what did the trick. did the trick. Something must have been stuck Something must have been stuck in memory from the first failed attempt and it in memory from the first failed attempt and it was corrupting the following attempts in some was corrupting the following attempts in some way. way.
I'd still like to root it, but anyway... it's fixed and I'd still like to root it, but anyway... it's fixed and my wife's is glad to get her phone back. my wife's is glad to get her phone back. Happy Happy ending. ending.
Thanks to all for your assistance.
Click to expand...
Click to collapse
RuLEoF2 said:
itandy said:
So have you finally rooted your Rhyme successfully? Which tool did you use? Thanks![/QUOTE No root, but it's working and back to No root, but it's working and back to factory condition. factory condition.
I used CWM recovery to format all partitions I used CWM recovery to format all partitions (data, system, cache, devlog, etc.) as well as (data, system, cache, devlog, etc.) as well as the sdcard. the sdcard. Once that was done, I relocked the Once that was done, I relocked the bootloader and ran the RUU. bootloader and ran the RUU. This time I went This time I went through the entire setup process for the phone through the entire setup process for the phone (activation, market account, WiFi and so on) (activation, market account, WiFi and so on) without rebooting first. without rebooting first. After the setup, I After the setup, I rebooted and I started normally. rebooted and I started normally. About 20 About 20 minutes later, I got an android OTA update of minutes later, I got an android OTA update of some kind and now its fine. some kind and now its fine.
Not sure why setting up the phone would make Not sure why setting up the phone would make a difference, but formatting the partitions and a difference, but formatting the partitions and going completely clean-slate is probably what going completely clean-slate is probably what did the trick. did the trick. Something must have been stuck Something must have been stuck in memory from the first failed attempt and it in memory from the first failed attempt and it was corrupting the following attempts in some was corrupting the following attempts in some way. way.
I'd still like to root it, but anyway... it's fixed and I'd still like to root it, but anyway... it's fixed and my wife's is glad to get her phone back. my wife's is glad to get her phone back. Happy Happy ending. ending.
Thanks to all for your assistance.
Click to expand...
Click to collapse
How did you get the ruu to run i keep getting a error 140 wrong bootloader version i tried ruu 1.26.605.11 and 1.26.605.6 i attempted to flash a ics rom and the phone got stuck on the splash screen so then i used my backup i made before i flash the ics rom and wouldnt boot so i extracted the boot.img from the ruu and flashed it to get the phone back up and running the phone is still rooted but i have no wifi no bluetooth no cam i been searching everywhere for a rhyme kernel bt no luck if anyone could help that would great
Click to expand...
Click to collapse
Ok, I have 2 Rezounds. Rooted mine, went s-off and loaded Liquidsmooth and Gaaps. Everything works fine after 1 week.
Went and did second phone (wife's) and everything seemed to go well, but I had 1 thing occur in this phone that did not happen in my phone. When in HBoot, it would constantly update and then force a restart. I couldn't get into Recovery, and my phone would not be recognized as an ADB device. Googled around and think it was something related to the PH98IMG file, so I deleted that off of my SD Card and bingo it worked.
So I flashed AICP KitKat and its Gaaps. I thought all was well until my wife tried to call someone and the screen blacked out (call was being made) and then the camera launched. We could not unfreeze the screen, even holding Pwr button - had to pull the battery.
I assumed it was the ROM, so I loaded CarbonROM - same thing.
I reset to factory, wiped everything and retried, same thing.
I restored my factory backup latest OTA (ICS), and it worked fine. I reinstalled my Amon recovery file. Rest phone again, and reloaded. Same problem - my phone screen locks up on outgoing calls.
Help..........
One thing, I assume you can flash the ROM and Gaaps back to back with no reboot. I did this, but also wiped all data and reinstalled them separately with a reboot between. Same results.
one additional item
Not sure why, but no matter how I reset or wipe, my contacts always reload. I am not selecting Google backup when going through setup screen. I have reset and wiped all cache, dalvik cache, and all other.
briggss3 said:
Not sure why, but no matter how I reset or wipe, my contacts always reload. I am not selecting Google backup when going through setup screen. I have reset and wiped all cache, dalvik cache, and all other.
Click to expand...
Click to collapse
Google will always restore your contacts, even if you uncheck the backup/restore options, they are part of your Google account.
As far as your other issues, it kind of sounds like a proximity sensor issue, try installing https://play.google.com/store/apps/details?id=com.incredicontrol.ProxSensorCalibrator&hl=en and see if you can calibrate it... although this doesn't explain the camera issue, it does explain why the screen goes blank during a call and will not come back on.
I wonder also if my HBoot was corrupted. I don't know why, but when I booted into Bootloader, it would go through the motions of updating and then prompting me to restart (no other option). I read that this was because my Bootloader was finding a PH98IMG file on the SD card - is this an update exe? So I deleted it and Bootloader worked.
Also, both phones hung up (dots) on Rumrunner "Pouring 2" phase, and I had to break the connection during this step. Rebooting showed s-off, but I reran the exe file and it went through and completed "successfully."
Is there any need to update my recovery file, currently Amon RA which i did from Scotty's Newbie Guides? I downloaded 7.2.2.2 TWRP and tried to flash it in recovery, but it says fail. I can not find instructions on doing this for newbies - only the one that references s-on users, but it just glosses over.
I'll do the Play store download and see if that works.
Thanks for your help. I am totally a novice, although I have learned alot after going through this. I read alot on the Android Forums and XDA before I post.
AmonRa could be your whole problem actually... Get TWRP 2.7.1.1 and either flash it via Fastboot, use the PH98IMG way, or try Flashify as a last resort.
The chances that your Hboot is corrupted is slim, but you can download the firmware zip from 4.5.605.14 and reflash with no issues, it will not change S-Off or unlock state.
Updated TWRP and tried the resound calibrator, still same bad result. Phone will work on the OTA recovery file (ICS), but will not work on any kitkat ROM installs. When making calls, I can not power off or anything, total loss of phone while call is active (unless I pull battery). Once call is hung up, then I get control back of the screen.
I can't seem to find anything, should I go s-on then relock and unlock it again maybe? If you think that's a good idea worth trying, let me know and I'll search for instructions on how to do that.
More I think about it, its proximity sensor issues. I replaced the glass just before rooting. I downloaded the calibration app, but can't find instructions. I will play around with that a bit and see what happens. I'll post back if I can't get that to work, I may have replaced the adhesive too close to (or touching) the sensor in the ear piece.
briggss3 said:
More I think about it, its proximity sensor issues. I replaced the glass just before rooting. I downloaded the calibration app, but can't find instructions. I will play around with that a bit and see what happens. I'll post back if I can't get that to work, I may have replaced the adhesive too close to (or touching) the sensor in the ear piece.
Click to expand...
Click to collapse
You can find more info here: http://forum.xda-developers.com/showthread.php?t=1904974
Hey guys, I was running stock ZVC (with stock recovery and bootloader) until just a few minutes ago, when I finally gave in and told the phone to apply the OTA update that was pushed out last week (the "ZVE" one). It started doing its thing, but next time I looked back at the device it was in recovery mode, just sitting there at the menu prompt...
I've since tried rebooting and powering off about half a dozen times, but it just keeps looping back to recovery mode. I also tried wiping the cache and rebooting, with no luck... It still loops back to recovery mode. I don't know what went wrong, but I'm assuming it could be related to one of two things that I didn't think about until afterwards:
1) The phone was rooted via Kingoroot, and root was still active when I tried to apply the update.
2) Just a FEW programs were frozen via TitaniumBackup (as well as Android's own app management system, using the "disable" feature), but these weren't system- or kernel-critical apps. They were things like LG Health, Sprint Money, etc...
Can anyone suggest a fix? Right now it just keeps rebooting into stock recovery and I've never had to deal with an issue like this, so I'm not sure what to do. I was obviously running the stock ROM, so I'm not set up to flash stuff. Although if it can be done with the default recovery, I suppose I could obviously do that... Once again, everything was stock on the phone except for Kingoroot, which was still enabled during the update.
I'm in a pickle here, guys. It's not like I'm any different than everyone who "needs their phone for work," but yeah, I need my phone for work... If I have to wipe data/factory reset, there's probably no way to pull some data off of the phone via PC first, is there? I suppose it's not that big of a deal, but I have some data and some program data that I hadn't gotten around to backing up yet, because I didn't think I'd need to until before I attempted to flash a new ROM or custom recovery.
Any help would be HUGE. Thanks...
EDIT: I took it into the Sprint store today a couple hours after I posted this, and they said I'd have to send it in to LG for warranty service. I don't know if the Sprint tech person knew what she was doing or not (because she had to use Google to figure out how to put the phone into download mode, even though she owns the same model), but she said that she couldn't establish a connection between the PC and the phone...
Now I'm not sure if that's the case, or if she just didn't have the right drivers installed, or if she was even in the right mode (I think she was using some Sprint-made flashing tool, but she did get it into download mode). She also seemed bored and like she just didn't wanna deal with it, so I don't know...
Assuming I can flash back to an earlier build like ZVB (and assuming I can even find it online), is that done from download mode or from recovery? By the way, we also tried just doing a factory reset and that didn't work either; just keeps rebooting to recovery...
Thanks...
EDIT 2: Fixed by flashing to stock via these instructions. Had to select Board DL and use a different key sequence as described here.