Develop Bugs

[Q] OTA Update 2.29.405.5 unbrandet but Rooted - possible?

Hi
I have a 2 month old Desire (SLCD I believe!?), with 2.2 (2.29.405.2) installed out of the box.
The first thing I did when I got home with my new phone was to root it with unr3voked, to be able to uninstall facebook/twitter apps etc.
(Unfortunately that cant´t be done, for some reason? - It was fairly easy on my old X10 mini!)
Anyway I left them there, and live with it, not that much of a problem to me
Now I have just received the 2.29.405.5 OTA update, and not knowing any better, I tried to install it.
Got to the bootloader(I presume that is the correct name? - Rainbow coloured screen) and it said no file named "Update.zip" found?
I then just rebooted , and did nothing more(wanted to do a little read up about it first).
everything works as normal, but I would like to have the update though.
Now I read several places that I can´t OTA update a rooted phone
Question is, can I Unroote without wipping the phone or can I do the update in some other way?
Supplementary questions: How do I make a "Nandroid backup (I have read about it, but I don´t know how to do it
What is a "Goldcard" - And do I need one? (unbranded and unlocked phone out of the box)
Btw. The phone is Danish, if that is of any relevance

sorry but not possible, the root modify your bootloader so when the update OTA will check it, it will fail your update.
OTA is only for undranded and unrooted phone.

tozneno said:
sorry but not possible, the root modify your bootloader so when the update OTA will check it, it will fail your update.
OTA is only for undranded and unrooted phone.
Click to expand...
Click to collapse
Thank you for the answer.
It was unfortunately as I expected
Can anyone answer me about the Nandroid and Goldcard thing?

Nandroid: Boot into Recovery and select 'Backup' from the menu (it might be called 'Nandroid' depending on the custom Recovery you used)
Gold card: No you don't need it

Actually, applying OTA 2.29.405.5 to a rooted stock phone is pretty simple if you have S-OFF from AlphaRev. At least this specific OTA, as it has no hboot inside it, so it won't overvrite hboot and you would keep the S-OFF and fastboot capabilities.
First, OTA flashing process uses stock recovery, so you'd need to flash stock recovery (grab it from the RUU - there is actually a recovery.img within this OTA, but I haven't tried using that...) via fastboot. Then just apply the OTA from a fully booted phone - wait until the first complete reboot after it finishes.
Second, you flash your customized recovery back using fastboot again.
Third, you boot into recovery, mount system partition, and, using adb shell, chmod 06755 /system/bin/su to regain root.
I've done that and it works without problems. One issue is that if you modified something this update touches on /system partition (vending.apk in my case) it will fail verification and throw an error 7. Everything the OTA updates must be exactly as in stock 2.29.405.2.
But I still wouldn't try it without a nandroid backup handy.

Latest 1 Click Root

Hi all,
I rooted my evo 4G forever ago, but a friend of mine recently tried to root her phone and simply has the big exclamation mark on it now. I'm not sure what she did, but she's bringing it over tonight. I was wondering, does anyone have any idea what is needed to get that sucker back up and running?
Will it respond to the latest 1 click roots? unrevoked? simple root? what's the game plan?

If you get the exclamation mark when trying to get into recovery, that means you're rooted with no recovery. When she gets to the bootloader, is she s-off?
If s-off, then rooted, and then flash the file I attached in the bootloader. Place on sdcard, boot into the bootloader, apply update, reboot, reboot into recovery, then you'll be on amon_ra 2.4 recovery.
And for latest 1 click, unrevoked. Download the hboot drivers, install then uninstall htc sync, enable usb debugging on phone, from applications > development.
http://unrevoked.com/#evo
IF you can only get into the bootloader, phone not booting, ect, run the 3.70 RUU. Rename the file to PC36IMG, then place on the root of the sdcard, flash in the bootloader like previously. The RUU will return you to stock, unrooted; then you can root using unrevoked.
http://dl.dropbox.com/u/19699565/3.70 RUU Zip.zip

Thanks. She's dropping the phone off tonight. Now I've got the plan of what to do! I'll execute accordingly, and update if there's any odd snags, but I assume there will be none.
Thanks again.

GantMan007 said:
Thanks. She's dropping the phone off tonight. Now I've got the plan of what to do! I'll execute accordingly, and update if there's any odd snags, but I assume there will be none.
Thanks again.
Click to expand...
Click to collapse
You shouldn't, but if she doesn't stick around, when you return it, you should just ham it up just cause.
And if you do incur trouble, post in the thread here or shoot me a pm.

S-OFF still showing after OTA?

My wife got her replacement Inc2 today after the one she got last week just died. She was on Froyo so I might of.. swapped her phones.. anyways, I rooted, went to the bathroom and the stupid ota ran I guess because when I came back the phone was on GB 2.3.3 however my boot screen shows S-OFF. Can anyone help me to verify that S-OFF is indeed still off. I can post any screen shots etc.. I am still a noob when it comes to the Inc2.

If your boot screen says S-Off, you are S-Off
Sent from my stock, bloated ADR6350 using XDA Premium App

Did you flash clockworkmod recovery when you rooted? I didn't think the OTA would take if you had a custom recovery. In any event, since you're still s-off, you're fine.

I actually hadn't flashed recovery yet. Went ahead and flashed recovery. Superuser installed but busybox keeps failing. I am manually installing them since the patch I found also includes a rooted kernel but it is for Froyo.
The biggest deal for me is I am still S-OFF. I'm just confused as to how I managed to remain S-OFF after the OTA went through. If I can't get busybox installed I'll probably install Ginger Sense to obtain it.

kujayhawks77 said:
I actually hadn't flashed recovery yet. Went ahead and flashed recovery. Superuser installed but busybox keeps failing. I am manually installing them since the patch I found also includes a rooted kernel but it is for Froyo.
The biggest deal for me is I am still S-OFF. I'm just confused as to how I managed to remain S-OFF after the OTA went through. If I can't get busybox installed I'll probably install Ginger Sense to obtain it.
Click to expand...
Click to collapse
Alpharev changed ur hboot to a higer version than the one in the OTA.. this is why it kept you S-OFF.. if I'm wrong someone correct me.

So basically I just got really lucky and kept my S-OFF even though the OTA went through.

kujayhawks77 said:
So basically I just got really lucky and kept my S-OFF even though the OTA went through.
Click to expand...
Click to collapse
No. stock hboot is .97. alpharev bumped you up to 1.something.. idk I used XTC clip.. since your hboot is newer than the OTA.. it keeps you S-OFF, pretty smart by alpha.

So does this open a gateway to first root in Froyo and then go gingerbread and retain the root?

Only way to be able to tell is to have someone repeat my steps which were: stock froyo, run AlphaRevX, did not flash recovery, Run OTA (this happened by accident I did not intend for the OTA to go through) after the OTA is finished reboot and if it is indeed a "gateway" then S-OFF would still be on. (After seeing S-OFF was on (and making sure it was okay) I went ahead and installed cwm recovery at that point)
Now when I use the term "gateway" I say this loosely because it doesn't fix anything for anyone who is already on GB. If indeed this works, it would only work for a small percentage who get Froyo and don't flash clockwork before running the OTA.

I just got my Inc2 as a replacement for my fascinate, came with 2.1 might try your steps and see if my root will stay after doing the OTA

tnez said:
I just got my Inc2 as a replacement for my fascinate, came with 2.1 might try your steps and see if my root will stay after doing the OTA
Click to expand...
Click to collapse
2.1??? I think you are mistaken, sir

beenz said:
2.1??? I think you are mistaken, sir
Click to expand...
Click to collapse
He was mistaken cause it is sense 2.1 but android 2.2
Sent from my Incredible 2 using XDA Premium App

kujayhawks77 said:
Only way to be able to tell is to have someone repeat my steps which were: stock froyo, run AlphaRevX, did not flash recovery, Run OTA (this happened by accident I did not intend for the OTA to go through) after the OTA is finished reboot and if it is indeed a "gateway" then S-OFF would still be on. (After seeing S-OFF was on (and making sure it was okay) I went ahead and installed cwm recovery at that point)
Click to expand...
Click to collapse
I've been wondering about this. I got my Dinc2 early July and I'm still on stock, unrooted Froyo. Somehow the OTA update to GB hasn't hit yet. Could I run ApharevX to get S-off and stop there for now? I am happy with bloated stock for the time being and want to be able to receive OTA updates, but would like to have the option down the road to add Clockworkmod and flash custom ROMs. From kujayhawks experience it seems that this should be possible.
Basically, if I achieve S-off with AlpharevX now, will I be able to pretty much do anything later?
P.S. First post, though I've been lurking around for a while. Great forum/community.

xenakis said:
Basically, if I achieve S-off with AlpharevX now, will I be able to pretty much do anything later?
Click to expand...
Click to collapse
It appears from reports that S-off stays after the OTA to 2.3, so yea, that would seem to be the case.
If you turn S-off with AlphaRev, you might want to just go ahead and install Clockwork recovery at the same time. Doing so won't root or install SuperUser or anything, but you would be able to then backup your phone and be ready to flash if you wanted.

If you install clockwork recovery you won't be able to receive OTAs though, just keep that in mind. You can flash back to the stock recovery, but unless you are familiar with ADB, it won't necessarily be an easy process.

Researched and read guides, no luck, need some unique root help.

Alright, I'll try not to make this an incomprehensible mess. I have an evo with s-off that I reset to stock after playing around with some ROMs. I used the unrevoked method to achieve s-off back then. Anyway, after the reset, I don't have superuser permissions. I do still have s-off, but I have no recovery flashed and as far as I can tell I need to get superuser permission first thing anyway.
The superuser app in the store doesn't do anything. As far as I've been able to find out, I need to flash superuser from the sd card. However, since I don't have a recovery installed, I can't do that. And since I don't have superuser, I can't flash a recovery.. see the problem?
So since my bootloader is locked I figured I'd try the HTCDev method for unlocking it, but when I get to the steps with the command prompt commands, I just get a "waiting for device" message. I tried installing the modified unrevoked drivers, which worked, but I still get the "waiting for device".
Basically I'm unsure what I'm supposed to do. Rooting the phone from stock is so goddamn easy, I don't know why it's being so difficult when I already have s-off. Any help would be appreciated. I couldn't find anything relevant by searching here or elsewhere.

AnHero said:
Alright, I'll try not to make this an incomprehensible mess. I have an evo with s-off that I reset to stock after playing around with some ROMs. I used the unrevoked method to achieve s-off back then. Anyway, after the reset, I don't have superuser permissions. I do still have s-off, but I have no recovery flashed and as far as I can tell I need to get superuser permission first thing anyway.
The superuser app in the store doesn't do anything. As far as I've been able to find out, I need to flash superuser from the sd card. However, since I don't have a recovery installed, I can't do that. And since I don't have superuser, I can't flash a recovery.. see the problem?
So since my bootloader is locked I figured I'd try the HTCDev method for unlocking it, but when I get to the steps with the command prompt commands, I just get a "waiting for device" message. I tried installing the modified unrevoked drivers, which worked, but I still get the "waiting for device".
Basically I'm unsure what I'm supposed to do. Rooting the phone from stock is so goddamn easy, I don't know why it's being so difficult when I already have s-off. Any help would be appreciated. I couldn't find anything relevant by searching here or elsewhere.
Click to expand...
Click to collapse
OH my god, it's so easy.
Download the attached files and place them on the root of your SD card. Run the PC36IMG file through your bootloader, and accept the update. Power off the phone (not going to explain that), then boot back into the bootloader. That will give you the Recovery that you need to flash the superuser app. Just go to RECOVERY after these steps and you will see.

[Q] State of root access, 4.3

Hey all,
I just wanted to pose a few questions. I've spent about 20 hours going through forums and articles to root my Verizon HTC One, and a heck of a lot of the information out there is very dated, and often contradictory. I've tried condensing it into a single procedure, but am having problems.
Here's the procedure for a brand new phone straight from a verizon store yesterday, running Android 4.3, with hboot 2.55, as I understand it; the information that I believe is now out of date, wrong, or not for 4.3/ 2.55; and the problem(s) I'm running into:
Procedure:
1) Unlock the bootloader and get s-off -- Firewater should be able to do this using the temproot method
2) Flash recovery mod, I was going to use CWM since it worked so nicely on my Incredible for 4 years -- this requires an unlocked bootloader and s-off, done the standard way via fastboot
3) Use CWM to flash superuser in recovery -- push the zip to sd, flash it from recovery
4) Happy times with my old set up back
Misinformation:
1) HTCdev -- no longer allowed for HTC One by Verizon, can't unlock bootloader this way. Renders a lot of the threads irrelevant now that this is not a valid route
2) rumrunner -- works for Android 2.2.4, not 2.3, and up to hboot 2.54
3) firewater "standard method" -- useless to anyone attempting to root a new device for the first time
4) "flash ARHD, then run firewater" -- again, not useful if you're trying to get CWM and SU on your phone for the first time
Problems:
1) The big one. Running temproot/ firewater, I acquire root access after running temproot, but when I run firewater after I get
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, hold power for 60 seconds !!
preparing, one moment
The first bottle is open
chugging..........
C:\adb>
Click to expand...
Click to collapse
with the adb shell crashing out, and my phone will freeze, requiring a hard reboot.
2) I got a few suggestions to use rumrunner (before I decided rumrunner was 2.2.4, from the sources I could find). The process would be going fairly smoothily, until it would crash with the error "looks like device is not rooted AND lacks an unsecure kernel. su or FU!!" I also once got an error about "unexpected process or ROM" but haven't been able to replicate it.
3) Found some advice for "flashing CWM without s-off"...that obviously didn't work, but I thought I might as well try
4) Not so much a problem as a concern...I'm a bit worried about my drivers. I think they are good and up to date, I got them from HTCsync, and have full adb and fastboot control to my device, but still...
The Jury
So, what's your take? Am I missing something obvious?

Update
atewsleybooth said:
So, what's your take? Am I missing something obvious?
Click to expand...
Click to collapse
Update
I tried going through the firewater procedure on OSX instead of Windows, with the exact same results (crashing out of adb shell). This leads me to believe that the problem is with the device, and not the computer. Does that sound right?
I switched cables, got one instance where I actually received "somebody pissed in the firewater reboot and try again." However, 2 reboots since with the same cable and port have both gone back to crashing out of the shell.

Rumrunnwr is only for 4.2.2. Firewater is for 4.3. You need to be complete stock and follow temproot method. Firewater was written for multiple devices so the whole HTC dev unlock and other methods won't work for the m7vzw. If you are on 4.4.2 then you are sol for now.

Gizmoe said:
Rumrunnwr is only for 4.2.2. Firewater is for 4.3. You need to be complete stock and follow temproot method. Firewater was written for multiple devices so the whole HTC dev unlock and other methods won't work for the m7vzw. If you are on 4.4.2 then you are sol for now.
Click to expand...
Click to collapse
I'm on full stock 4.3 device, running firewater using the temproot. I've made sure not to got to 4.4.2.

atewsleybooth said:
I'm on full stock 4.3 device, running firewater using the temproot. I've made sure not to got to 4.4.2.
Click to expand...
Click to collapse
Have u tried to factory reset the device?

Try redownloading the firewater file, mabey it was a bad download, or got corrupted somewhere along the way. If thays not the issue try below.
You shouldnt have to do this but its worth a shot. Once you aquire temp root, try pushing the su binary to /system/xbin, and the superuser.apk to /system/app. Then reboot the phone. This should technically give you root. Then try running firewater again to unlock and get s-off.

cmlusco said:
Try redownloading the firewater file, mabey it was a bad download, or got corrupted somewhere along the way. If thays not the issue try below.
You shouldnt have to do this but its worth a shot. Once you aquire temp root, try pushing the su binary to /system/xbin, and the superuser.apk to /system/app. Then reboot the phone. This should technically give you root. Then try running firewater again to unlock and get s-off.
Click to expand...
Click to collapse
I got it working. What I wound up doing was saying "No" to the first prompt from firewater, then restarting firewater, and saying "Yes." Twice this gave me "somebody pissed in the firewater," but on the third try, it went through. Not initiating firewater twice and canceling out of the first run would always crash my shell.
Go figure.

atewsleybooth said:
I got it working. What I wound up doing was saying "No" to the first prompt from firewater, then restarting firewater, and saying "Yes." Twice this gave me "somebody pissed in the firewater," but on the third try, it went through. Not initiating firewater twice and canceling out of the first run would always crash my shell.
Go figure.
Click to expand...
Click to collapse
Weird. Glad you got it to work though.