lost root after update to 1.6? - G1 General

First of all let me say sorry for posting this without searching first, but I'm at a bar with no WiFi.
I rooted my buddies g1 using the onetouch method. He later accepted the 1.6 update after I gave it back. Now I can't access recovry to get to the nandroid backup i made. What are my options?
It seems he lost root becuase in terminal I can't get Su access

You lost root. downgrade down to 1.5 again and do a one click root. then flash a rooted donut rom so it doesn't bring up the option to update.

Thanks for the quick reply. I figured id have to do it again so no big deal. I will just have to beat him up if he does again lol

he shouldnt be getting OTA's from a rooted ROM

B-man007 said:
he shouldnt be getting OTA's from a rooted ROM
Click to expand...
Click to collapse
it happened to me when I had the stock spl. I flashed over the engineers, and it went away.

Related

Can the Sprint Hero be rooted after the new update/patch?

Hey guys...I have been reading posts from different forums and have heard that the Sprint Hero can't be rooted using the steps provided here (and in other forums) if it has the new firmware update that came out on Nov. 18th. Is that true?
I was still able to root after updating; however, I applied the update as a .zip file through the recovery ROM instead of OTA. Most of the posts I've seen say that you can still root it as well.
Yes, it can still be rooted.
I re-installed the original rom, got the update OTA and than re reooted as before
pm sent to evening newbs
I had a rooted stock ROM, was able to successfully apply the OTA update and still maintained root access afterwards.
Awesome! Thank you guys for the quick responses! You guys are awesome. I'ma root right away. TheUnlockr.com said that root can't be achieved post update. I guess they were wrong. Thanks again and God bless!
best method, post firmware update?
Actually...can anyone post a link to the method they used post firmware update? There seems to be a lot of confusion as to which method still works. A link or two to an easy, understandable (I'm a newb), set of directions (that still works after the patch) would be SO helpful! Thanks in advance!
I rooted before the update using the flashrec method without any problems. Then after restoring the original Sprint image which unrooted, I did the OTA update. I again used the flashrec method. All the steps worked until I turned off the phone and tried to boot to the black screen with green writing (i forgot what this screen was called with the nandroid). When doing this my screen gets stuck on the HTC logo. Any suggestions?
alexthearmo said:
Awesome! Thank you guys for the quick responses! You guys are awesome. I'ma root right away. TheUnlockr.com said that root can't be achieved post update. I guess they were wrong. Thanks again and God bless!
Click to expand...
Click to collapse
I never said it couldnt be rooted, I said it couldnt be rooted using the Flashrec method (which is what everyone is telling me since I dont have a Sprint Hero myself). There is always a way to root, I told you that you probably had to find the original Sprint RUU to downgrade back to the original Sprint firmware and then you could have rooted using FlashRec at that point.
But if there another way, or if anyone has a link to the original Sprint RUU, please share.
Hey...just so you guys know...I rooted fine using the Unlockr's method (not the one click root, but the command prompt way). Worked fine...Even with the new sprint update. So now I have Root, AND my phone sleeps great!! (as it should post update).
Also...flashed a recovery image...had some problems...finally found out it has to be be an image that says heroc (with the letter "c"), otherwise the phone won't boot into recovery mode...it'll just get stuck at the HTC screen in the beginning and you'll need to take your battery out.
I hope this info helps someone...it took me a while to figure it all out. God bless!
-alex
I concur I messed up the Nandroid backup the first time because I didn't wait for the Hero to boot back up before I started typing in commands and I got a little ahead of myself but all is well now

Um, I dont think the OTA affects root ability

well I did the OTA.... and ive rooted it following toasts tut... i got it to boot in recover mode... and im doing a NAND backup... oh just finished actually... i swear im not lying lol..
i finished the NAND backup and did a system reebot within the recovery... now let me get this straight tho... within the recovery is where I would flash a new rom yes? if I were to power off the Evo, root is gone right, this is only like a softspl ?
crap...EDIT:
um crap... nvm apparently i didnt update...
i swear I downloaded, installed, restarted the phone to allow install... but it shows software number 1.32.651.1.
maybe because I did a factory reset? then that would mean that this update is rather a patch (ie like a cab fix)??
or did the update not apply?
Ya, I had to download and install the update twice. There is no way root is worth the SD card bug, so until there is root for the patched ROM, no root for me.
The thing is right now we have ghetto root. The other devs have specifically said the update conflicted with root. Best not to install it if you care about it.
Aridon said:
The thing is right now we have ghetto root. The other devs have specifically said the update conflicted with root. Best not to install it if you care about it.
Click to expand...
Click to collapse
I don't. Not gonna bother rooting until after the official 2.2 ROM releases in August or so.

lost root access somehow. running eugene373 froyo

So i have been using eugenes initial build of the jpm froyo. Installed all the updates he had for it at the time using clockwork. It was kind of laggy so i was toying around with the oclf by ryan za. It asked to install/root through its own root feature. Now since i have done so. I lost root access. Does anyone know any way i can re-root my phone without having access to a computer. Losing root access has disabled my ability to flash any of the updates that have come out in recent weeks and its paining me i heard others have experianced this losing root glitch. And got flamed when i asked this question on eugene373s former rom thread.
Any advice.
Ps. ( having a blutooth keyboard and mouse hooked up to this phone on 2.2 Is the best thing since sliced bread)
agooz20 said:
So i have been using eugenes initial build of the jpm froyo. Installed all the updates he had for it at the time using clockwork. It was kind of laggy so i was toying around with the oclf by ryan za. It asked to install/root through its own root feature. Now since i have done so. I lost root access. Does anyone know any way i can re-root my phone without having access to a computer. Losing root access has disabled my ability to flash any of the updates that have come out in recent weeks and its paining me i heard others have experianced this losing root glitch. And got flamed when i asked this question on eugene373s former rom thread.
Any advice.
Ps. ( having a blutooth keyboard and mouse hooked up to this phone on 2.2 Is the best thing since sliced bread)
Click to expand...
Click to collapse
Im assuming in the OCLF app now there is an option to "unroot" your phone? for ****s and giggles click that see if it didnt just get mixed up since you told it to root when you were already rooted. If that doesnt work download Galaxy S Rooter from the market and try that. if THAT doesnt work i would say wipe data and try either of them one more time. and if all fails youll most likely have to flash stock firmware and root from there
I have actualy tried both of those options. Haha, I'm looking at my final option of flashing back to stock via odin, but that requires a computer which I do not have access to. I figured id see if anyone had some other root reroot option I didn't know about.... or if there is a way to unroot from this semii rooted stage I'm stuck in. The phone thinks it rooted but when I try to use any program that requires root access it force closes the app etc.

2.3.3 OTA Flashed Recovery Image and now have access, but no root?

Ok here is the deal! I have a friend who recently took the OTA and obviously now he has broken his root access. The phone is still S-OFF in the hboot and so I decided to try loading a new recovery image since it would not load recovery. Well that worked great, but still no root access when in the rom! I am wondering if I will get root access back after wiping the phone clean and installing a new rom? I'm sure this has been covered that due to the new hboot there is no answer for root access, but I had to try anyways since I do have recovery access! The following information is what all the phones current settings;
Android Version
2.3.3
Baseband Version
2.15.00.05.02
Software number
4.24.651.1
PRI Version
2.15_003
PRL Version
60680
HBoot Version
2.16.0001
Radio
2.15.00.05.02
Update!!!! I got ROOT access back by using the same method I used to take the first OTA around the first of JUNE.
http://forum.xda-developers.com/showpost.php?p=14548586&postcount=44
If you can get into recovery you have it whipped in that all you need to do is flash the su-2.3.6-gb-wal_fix-signed.zip file and BAM you have root access again.
silly454 said:
Update!!!! I got ROOT access back by using the same method I used to take the first OTA around the first of JUNE.
http://forum.xda-developers.com/showpost.php?p=14548586&postcount=44
If you can get into recovery you have it whipped in that all you need to do is flash the su-2.3.6-gb-wal_fix-signed.zip file and BAM you have root access again.
Click to expand...
Click to collapse
I'm glad you figured this out. For next time try searching for.the answer before you post. This specific topic is covered at least several times after every ota.
Sent from my PC36100 using XDA Premium App

Error while trying to update to 4.4 (D800)

Hey all. I have a rooted D800 (AT&T variant) with stock recovery and on firmware version D80010q. I am trying to update to the KitKat, but It's giving me an error every time I download and try to update. The error is: Err: 0x1111004. When the phone reboots, it says "This device is suspected in rooting. Software update is not available for rooted device".
I have tried using OTA rootkeeper to temporarily unroot, but it doesn't seem to work. Is there any way for me to get the update without having to flash back to stock?
This is my problem too. Hopefully there is a way.
Sent from my LG-D800 using xda app-developers app
Maybe doing a factory reset from stock recovery?
Sent from my LG-D805 using xda app-developers app
rohan611 said:
Hey all. I have a rooted D800 (AT&T variant) with stock recovery and on firmware version D80010q. I am trying to update to the KitKat, but It's giving me an error every time I download and try to update. The error is: Err: 0x1111004. When the phone reboots, it says "This device is suspected in rooting. Software update is not available for rooted device".
I have tried using OTA rootkeeper to temporarily unroot, but it doesn't seem to work. Is there any way for me to get the update without having to flash back to stock?
Click to expand...
Click to collapse
Its due to the custom recovery you have on it..Go back to stock dont root and update...maybe try root keeper to see if that can help
antawnm26 said:
Its due to the custom recovery you have on it..Go back to stock dont root and update...maybe try root keeper to see if that can help
Click to expand...
Click to collapse
nope. as i said in the OP< i have a stock recovery.
rohan611 said:
nope. as i said in the OP< i have a stock recovery.
Click to expand...
Click to collapse
then try root keeper it will disable root but back up root path and reinstate it once the update is done
antawnm26 said:
then try root keeper it will disable root but back up root path and reinstate it once the update is done
Click to expand...
Click to collapse
as i said in the OP...I tried root keeper to temporarily unroot and it didn't work. I'm going back to stock and going from there.
rohan611 said:
as i said in the OP...I tried root keeper to temporarily unroot and it didn't work. I'm going back to stock and going from there.
Click to expand...
Click to collapse
lol..yeah i read each statement in your OP just wanted to get to that last part of you saying your going back to stock and going from there, because thats your next option....
Let us know if you went back to stock then did the update and it worked.
I've read that some people kept root through their OTA. Why are some people able to update and others aren't. I've been reading up on this for the VZW update whenever that happens. I hope I haven't kept all this bloatware on my phone for no reason!!
Sent from my VS980 4G using Tapatalk
hinduboy74 said:
Let us know if you went back to stock then did the update and it worked.
Click to expand...
Click to collapse
I reverted back to stock using the instructions in the Stickied post. I was then able to update to D80010o. I had to call to request a rep to push out the D80010q update again though. They're calling it a "security update" so you should use that phrase when talking to the rep so that they don't get confused and think that you're just requesting that they push out the KitKat update.
Once I got the D80010q update, the KitKat update was available and I was able to update. Unfortunately, I didn't try to root it prior to updating - though to be honest, I don't really feel the need to root anymore. Only reason I had it rooted before was to get the multitasking button, but I'm okay with using an S3 layout (Menu, Home, Back) since that's the phone I'm coming from.
I have posted this in Other thread too.. may be this helps (Or save some time)
1.What ever the phone came with (never saw the version)
2. Rooted: Then just froze the apps I don't need (DID NOT DELETE) NO Exposed Or anything fancy. PURE STOCK just at&T bloat froze.
3. Then the Silent update came... I guess it was 10q (few weeks back), It was fine... ROOT remained.
4. Kitkat update came..
5. I de-froze all the apps before the update..
6. Tried to installed KITKAT after download... (After 1 of 2) it says Err: 0x111004
Once booted it said this update is not for rooted device. (or something similar)
7. I thought may be it recognized SuperSU/Super USer so I Uninstalled (Removed complete ROOT through the app) Download again the Kitkat.. Same ERROR And SAME message. I went it Recovery (Button combo) to complete wipe (Noticed RED Rooted below on the screen on Recovery) did the complete wipe and Still No Luck.
8. Go back to Complete stock through flash method as I realized ROOTED written on recovery so no wipe will help that...
9. chat with AT&T asked them to push 10q the silent updated.
10. once it was done I asked her if she can push Kitkat too.. she did.
The only thing was lost all the data in the process.. But I kept my pic's Auto backup through g+ so they are safe.. rest everything I lost which I don't care anyway. (Chat etc)
SO the BOTTOM LINE IS... If you see ROOTED on your stock recovery NO matter what you do... It will not update. If you dont see it.. then your are fine I Guess ("I guess" is the keyword)
Edit:
Also I'm not sure if there are 2 versions of root methods... So if anyone has Root and was able to update to kitkat.. Can you link which Root method you guys used.. Thanks in advance.
streetsmart999 said:
Also I'm not sure if there are 2 versions of root methods... So if anyone has Root and was able to update to kitkat.. Can you link which Root method you guys used.. Thanks in advance.
Click to expand...
Click to collapse
I used ioroot to root while on D80010d. I think some people who have had success rooted while on D80010o
rohan611 said:
I used ioroot to root while on D80010d. I think some people who have had success rooted while on D80010o
Click to expand...
Click to collapse
That is correct. I was on D80010o all four times I updated to Kit-kat and kept root everytime.
streetsmart999 said:
1.What ever the phone came with (never saw the version)
2. Rooted: Then just froze the apps I don't need (DID NOT DELETE) NO Exposed Or anything fancy. PURE STOCK just at&T bloat froze.
3. Then the Silent update came... I guess it was 10q (few weeks back), It was fine... ROOT remained.
4. Kitkat update came..
5. I de-froze all the apps before the update..
6. Tried to installed KITKAT after download... (After 1 of 2) it says Err: 0x111004
Once booted it said this update is not for rooted device. (or something similar)
7. I thought may be it recognized SuperSU/Super USer so I Uninstalled (Removed complete ROOT through the app) Download again the Kitkat.. Same ERROR And SAME message. I went it Recovery (Button combo) to complete wipe (Noticed RED Rooted below on the screen on Recovery) did the complete wipe and Still No Luck.
8. Go back to Complete stock through flash method as I realized ROOTED written on recovery so no wipe will help that...
9. chat with AT&T asked them to push 10q the silent updated.
10. once it was done I asked her if she can push Kitkat too.. she did.
The only thing was lost all the data in the process.. But I kept my pic's Auto backup through g+ so they are safe.. rest everything I lost which I don't care anyway. (Chat etc)
SO the BOTTOM LINE IS... If you see ROOTED on your stock recovery NO matter what you do... It will not update. If you dont see it.. then your are fine I Guess ("I guess" is the keyword)
Edit:
Also I'm not sure if there are 2 versions of root methods... So if anyone has Root and was able to update to kitkat.. Can you link which Root method you guys used.. Thanks in advance.
Click to expand...
Click to collapse
Same thing happened to me. I followed your advice in the other thread and did a reset using the LG flash tool, following rootjunky's guide on youtube and using the files from his website. Everything went smoothly except for at the end I got the same check flag error thing, but it completed the reset perfectly.
I then chatted with ATT and had him push the update to my phone which brought me up to d80010o. It finally went through the update and didn't get me the root error. So I think I'm in the green now. He said that he didn't have an option to push the kit kat update to my phone but it told him to have me do it through the software update in the settings. Which I tried and it said it was up to date. But he said that since they roll out in batches my phone might just not be ready for it yet. I will keep trying though and I'm one step further than I was before. At least it let me update. Shout out to ATT though, chat service is on point.

Categories

Resources