Lost root after JH7_OTA update. - Captivate Q&A, Help & Troubleshooting

After doing the Clockwork JH7-OTA "patch", I fiddled with the phone, and then thought I needed to re-root, and well, Now I'm feeling kind of stuck. I lost root, and I can't get recovery mode to "flash" me back to a known working point.
For reference I had used Unleash the Beast to previously Root/strip bloatware. Thanks.

Yes
I'm not sure about the clockwork update specifically but when you do any ROM update you loose root so I guess that is normal.

yes, after clockwork update you need to root your phone again. And after that also modify your settings.db to allow sideloading.

Took the long road back, and recovered the OS via Odin3 method.
Lesson learned.

Related

Installing Update using Clockwork and OTA JH7 taking an hour?

The bar has not filled up...What to do? Quit and try again?
USed Clockwork mod to find and install OTA'JH7.zip
Searched for it
found it
Installing hangup and nothing in the bar indicating anything is being done
Did you have any lagfixes installed prior to trying to update?
Rhiannon224 said:
Did you have any lagfixes installed prior to trying to update?
Click to expand...
Click to collapse
My history is as follows:
Stock to Root
Back to stock
Installed JH7 via mini Kies
BAck to stock
(Learned how to use adb to get into download mode)
Loaded Froyo "Officical beta"
Wanted to try the Clockwork mod so I went back to stock using ODIN
Installed the Zip files in proceeded to install Clockwork then searched for and found the OTA file
There are two files out there. JH7_OTA.zip and JTA_OTA_STOCK.zip
The latter did not work and hung up on install..I loaded the former and it installed.
Now a few questions regarding Clockwork
I dropped the Cognition 2.2 5 in my root directory..Can I load that in the same way? Then go back to the JH7 when the Official 2.2 froyo comes out? Whether rooted or not?
If I want to root the phone I will have two update.zips in the root directory (Clockwork and the root upadate.zip)...Must I remove Clockwork? IS it loaded or does it execute from the zip every time? Can I rename the Root update.zip to something else now that I can "find" it with Clickwork?
I like the clockworkmod and will definitely pay for it if it allows me to change ROMS I place on the SD on the fly rooted or unrooted (would never need to go back to JH6 and deal with adb if so)
Final question,,,Shoudl I use clockwork to "reset the battery?"
I do not intend to do any lagfixing beyond whatever is in Cognition since that seems to be more of a problem than it may be worth
Thanks...Its been two weeks since i became an Andriod fan and i have learned alot.....and still am
Read the Cog wiki, there have been so many versions I can't remember all of them and the install instructions, some you needed to flash through Clockwork. Cog 2.2 5 Is Froyo whicj means you can not use Clockwork to flash anything with Froyo running because Froyo is not an official release and is BETA it is not signed, Koush hasn't found a way to sign it in order for Clockwork to work with it yet. Clockwork is worth having the paid version yes. You must be rooted to use ROM Manager so unrooting you loose access.
If you are using JH7 that you flashed check if you have SuperUser in your apps drawer, if so you are rooted. Get used to Odin if you are going to mod your phone you will use it more than you think and it becomes less scarey the more you use it.
You've already modded your phone so OTA updates will not work for you, mini kies will so go ahead and flash away, you will eventually have to flash with Odin to update with mini kies so go have fun. Also, those guys on the dev section will have the official up as soon as it comes out. We had JH7 within a few hours, none of us could do the OTA and AT&T bricked a lot of phones so I will only use stuff from Samsung anyways.
Rhiannon224 said:
Read the Cog wiki, there have been so many versions I can't remember all of them and the install instructions, some you needed to flash through Clockwork. Cog 2.2 5 Is Froyo whicj means you can not use Clockwork to flash anything with Froyo running because Froyo is not an official release and is BETA it is not signed, Koush hasn't found a way to sign it in order for Clockwork to work with it yet. Clockwork is worth having the paid version yes. You must be rooted to use ROM Manager so unrooting you loose access.
If you are using JH7 that you flashed check if you have SuperUser in your apps drawer, if so you are rooted. Get used to Odin if you are going to mod your phone you will use it more than you think and it becomes less scarey the more you use it.
You've already modded your phone so OTA updates will not work for you, mini kies will so go ahead and flash away, you will eventually have to flash with Odin to update with mini kies so go have fun. Also, those guys on the dev section will have the official up as soon as it comes out. We had JH7 within a few hours, none of us could do the OTA and AT&T bricked a lot of phones so I will only use stuff from Samsung anyways.
Click to expand...
Click to collapse
Yeah I have two phones and one is the guinea pig. I have my main phone on the pre release of Froyo. I am practicing getting the second phone eventually from Cognition2.2 5 to Samsung's official release. I have used ODIN probably 10 times to get back to JH6 where I have to use the adb SDK to get into recovery/Download modes.
The OTA updates did not work for either phone which is why I began modding and learning, Mini Kies was the only way to get JH7 until now with Clockwork.

Troubles Unrooting/Removing Clockwork URGENT!

Here's the story:
A while back, I rooted my Nexus One without unlocking using the bait and switch method, and had been using various custom ROMs.
Recently, the power button hasn't been working well, so I called HTC to get a swap. Obviously, before sending my phone back, I need to unroot it.
I tried to restore my phone using the method in the XDA guides, but it hung on each step, and it didn't actually do anything. So, I flashed the non-rooted stock ERE27 through ROM Manager (this, I suspect was a huge mistake.)
Now, I have an rooted phone, that fails on any update attempt and so is stuck on 2.1, and worse, Clockwork Recovery is still on there. I've tried to unroot my phone again using both the bait and switch method, and the freenexus method, but both have run into errors. I've also tried installing Universal Androot and clicking Unroot, but it just tells me my phone isn't rooted.
So, I can't root my phone to attempt to flash the recovery, and I can't find a way to remove Clockwork Recovery, but I need to send this phone back to HTC within the next 7 days, or else I'm gonna be out $530.
Any ideas?
First: hate to be a douche, but someone's gotta say it: this is the wrong subforum for a question thread. Take a quick glance over the rules stickied at the top of the forum. There's a Q&A forum for things like this.
Second: HTC has typically honored the warranty for known hardware problems (of which the power button is probably the biggest) even for unlocked/rooted devices. They find for me, no problems. So relax.
Last, try using ClockworkMod recovery to flash CM 6 stable, then from that ROM, try flashing back to stock recovery. After that you should be able to flash a stock OTA ROM. You can't change recovery without root access, which you can't get on a stock ROM. So you have to change recovery first. And on your new phone, you should really just fastboot OEM unlock. Trying to deceive HTC makes them not want to give us this option anymore.
Yup no worries I had to send mine in because the trackball got stuck and they got it under warranty ... I had my phone running a custom recovery and rom and they didn't even ask about it.

[Q] Rooting my captivate, can't copy root file to phone

Hey folks. I'm bailing on Gingerbread because it was causing me too many problems. I'm trying to get back on Firefly 3.0 and I'm stuck at getting the phone rooted.
Whenever I try to copy the Root.zip from the AIO folder over to the phone's root folder, I get an error about the parameter being incorrect. I'm not sure what to do at this point.
Use Fugu root? Easier.... Also depending on what Gingerbread you are on there are kernels that have the root scrip baked in them.
^ you misread he's not on gingerbread, he wants to flash firefly.
You don't need root to flash a ROM. Odin a kernel that has cwm baked in. boot into recovery and flash the ROM.
Thought he was on GB trying to get on... you know what ya I missread. @OP do what Studa said xD. Wonder why people think they need root to flash roms..... I blame Rom Manager.
I know I don't need to root the phone, but in order to get certain things done on the phone, it's necessary.
I'm actually at a wall right now. I used SamsungCaptivate-SGHi897-UCKB2-Rooted-One-Click which successfully booted my phone to ATT 2.2 firmware, but I can't get any Odin to pick up on it now. I've tried five different Odins.
At this point, I think once I get the phone up and running on Firefly, I'll be walking away from flashing until I get another phone. Then I can use this for testing, etc.
On a side note, before I started this project yesterday, my modem was messed up. Now it would seem I have a successful connection to wifi, which I couldn't get.
As great as that is, I still can't get Odin to pick up my phone. Any thoughts?
Was that kb2 package heimdall?
If so you have to uninstall the heimdall driver and reinstall the Samsung driver.
Either way I would reinstall the Samsung drivers but it is a must if you used heimdall add the drivers conflict.
Alright. That's done, but I'm on I896UXJL1-stock now, and I'm pretty sure in doing that through Odin 1.85 I unrooted the phone. Correct me if I'm wrong. That's why I used the ATT stuff, because it auto-rooted the phone.
So it would seem I have some issues to work through. I can either root my phone and be stuck with ATT firmware that I don't want, or I can unroot the phone and use Rogers stock and hope for the best with Firefly.
This is by far the most confusing computer-related issue I've ever worked with. There's too many options to play with and they all work differently.
Why would you be stuck on at&t firmware? Why do you need to root before flashing firefly? Why don't you root Rogers stock?
you're confusing everyone involved lol
Okay, so maybe I'm a little in the dark on the rooting issue. Basically, I'm going back to Firefly because I thought it was amazing. Fast, responsive, and no issues I can think of on my phone.
I'm rooting the phone because it's my understanding that in order to spoof my location in order to get certain apps (Google Music), I'd need to be rooted.
I'm having a hell of a time trying to get this done, and my biggest problem, to reiterate, is that I have about fifteen different Roms, all either ATT or Rogers, three different Pit files, and so, so many Odin programs.
I'm now on 2.1 with that Toronto stock firmware, in order to work around the 3e error in recovery mode when trying to put on Clockwork. Unfortunately, now I'm getting some other error in regards to the Update.Zip file, Status 7.
I apologize for confusing people, but I promise I've read as much as I can about the tools I'm using, but I'm running in circles, flashing back and forth trying to find solutions.
you do not need to root before flashing the rom. it will be rooted after and then you can do what you need to do to get your apps working if you need to (firefly contains canadian locale cause its based off of rogers froyo firmware) changing stuff before you flash so apps can work is a waste of time as the flash will overwrite the firmware you just tweaked.
now, since your on eclair i'm attaching an update.zip that contains cwm, put it in the root folder of your sdcard boot into recovery select reinstall packages twice and it should boot into cwm where you can then flash firefly.
You're a frickin' genius, Studa. Don't let anyone tell you otherwise. I've got Firefly on thanks to that Update file, and I'm getting the ball rolling on everything else. If I wasn't so broke, I'd donate, but I hope my thanks is good enough. I really appreciate the help. It cut through twelve hours of stupid.

Troubleshooting ZV8 update and rooting

Many non Noobies seem to be running across the same problems with rooting ZV8 updates. The answers are spread across three different threads so it seemed worth putting them all in one place up front.
First, big thanks MT for putting all this up so quickly.
If you are still on ZV7, first try
http://forum.xda-developers.com/showthread.php?t=1566729
However, I and many others have not been able to get an over the air update (step 6) to succeed and/or get a lot of permission denied errors in the All in One batch processes. If you can't get an OTA update to succeed first try
Originally Posted by drt054
use a terminal emulator, type in
su <enter>
echo 'ro.kernel.qemu=1' > /data/local.prop <enter>.
OR
Use root explorer to create /data/local.prop and type ro.kernel.qemu=1 then save it.
If the OTA update works, you're good, continue with MT's instructions, but SKIP OPTION 1 "Prepare for Update"
If, like me and many others you still can't get an OTA update to succeed Alternative 2 is the LGPST method here
http://forum.xda-developers.com/showthread.php?t=1466655
Again, the key is to not loose Clockwork Recovery. As long as you have done the create local.prop step and not done the All in One Option 1 "Prepare for Update" The LGPST ZV8 push will not erase Clockwork Recovery. Then you have ZV8 with Clockwork Recovery and you can get MT"s Broken Out v 1.1 here
http://forum.xda-developers.com/showthread.php?t=1577423
Or get back to a nandroid backup or rooted ZV7 to start over
http://forum.xda-developers.com/showthread.php?t=1348637
If you loose Clockwork Recovery or otherwise run into trouble, the sure fire way to get back on track is to go back to ZV7 and start over. Personally, reading through all the forums and despite several attempts, I was never able to get an All in One batch process to root ZV8, always permissions denied. But I was just trying to ZV8 with Clockwork Recovery to get to Broken Out anyway.
UPDATE 4/3/12
Another option for regaining CWM if you use LGPST
http://forum.xda-developers.com/showpost.php?p=24411050&postcount=83
MT is looking for ZV7 testers for an easy update
http://forum.xda-developers.com/showpost.php?p=24416908&postcount=86
I'm more than a Noob, but far from an expert, so if this contains errors or doesn't deserve it's own thread, feel free to suggest removal!
Cutterstark said:
If, like me and many others you still can't get an OTA update to succeed Alternative 2 is the LGPST method here
http://forum.xda-developers.com/showthread.php?t=1466655
Again, the key is to not loose Clockwork Recovery. As long as you have done the create local.prop step and not done the All in One Option 1 "Prepare for Update" The LGPST ZV8 push will not erase Clockwork Recovery. Then you have ZV8 with Clockwork Recovery and you can get MT"s Broken Out v 1.1 here
http://forum.xda-developers.com/showthread.php?t=1577423
Click to expand...
Click to collapse
Appears that you DO lose CWM with LGNPST. I just tried your method and I no longer had CWM. Maybe you missed a step in the OP? Otherwise, I lost CWM when I pushed ZV8 TOT. Also, just so you know, I did check/test CWM just prior to pushing and it worked just fine.
-Cybie
EDIT: I wanted to clarify and emphasize "Appears" in my reply above. Your method may work perfectly fine, but I had nothing but troubles getting things to work...
is this a bad place to ask how im supposed to go back to zv7? i dont have cwm anymore....
help me out
ejammer said:
is this a bad place to ask how im supposed to go back to zv7? i dont have cwm anymore....
help me out
Click to expand...
Click to collapse
See this Link... All the tools and instructions.
http://forum.xda-developers.com/showthread.php?t=1337386
Be sure to follow the part with which LGNPST Tool Part to install first!!!
-Cybie
yes am back to zv7 now trying to figure out how to do the all in one update steps from mt. it seems in the "prepare for update" steps it fails on copying local.prop or whatev its called.
ejammer said:
yes am back to zv7 now trying to figure out how to do the all in one update steps from mt. it seems in the "prepare for update" steps it fails on copying local.prop or whatev its called.
Click to expand...
Click to collapse
That is the same problem I had. Try the copy local.prop option described above and bypassing the prepare for update.
better yet, contact MT, he is working on an easy solution and needs ZV7 testers
http://forum.xda-developers.com/showpost.php?p=24416908&postcount=86
what if I am on zv6 still?
Son's Revo asked bout v8 OTA today. Didn't want to do it as I figured it would lose root. Currently we are on v6 and rooted (via AIO). Never went to v7, and now with v8 am trying to figure out how to get to v8 and keep root.
Do I need to get to v7 first prior to trying to get to v8 while keeping root or is there a way to go directly to v8 while maintaining root?
I posted in http://forum.xda-developers.com/showthread.php?p=25188375#post25188375 about trying to get to stock v7 not working for some reason so won't go into that here, but thought I would ask about a way to get to v8 with root WITHOUT having to go to v7 first.
I have a solid nandroid (which I just had to use to get a working phone again) I can use so don't mind testing things.
Thanks for any ideas...
***EDIT***
I went ahead and went to stock v7, rooted, and followed the v7 to v8 (save root) process MT created and all is well.

[Q] JB Root Help

I was running DynamicKat 2.1 and somehow lost SS recovery reboot. In the process of trying to restore it I wiped my phone and had to revert back to MJ5. It is up and running fine but I can't get it to root. I have been to this point a few times but the rldv.zip method from, http://forum.xda-developers.com/showthread.php?t=2559715 , I used before isn't working or Klingo Root, which I also used the first time I rooted my Note 3 isn't detecting phone. I just did this a few days ago to get root but for some reason now it isn't working. I need to get root back so I can boot into SS and get back to DynamicKat. Any tips or advice on something i am possibly overlooking this time would be great. Thanks in advance.
Try deleting your current USB drivers, plug in your phone, let Windows reinstall them, and try again. This always worked for me after reverting to MJ5 and Kingo wasn't detecting my phone.

Categories

Resources