Develop Bugs

[Q] Undo old permaroot & S-OFF from pre-gfree, or update to new S-OFF?

Hi guys,
I've been reading through the forums over the past two days but I have to admit it's hard to find what I am looking for now that the G2 forum and the DZ forum are merged, and the search isn't getting me anywhere for this one.
I have Bell Canada Desire Z permarooted and S-OFF'd, with CWMod. I did this before the newer gfree method and from what I can gather this can lead me to some kind of endless loop if I try to flash back to the a Bell RUU or other RUUs for that matter. It also worries me that I can't try new radios, etc.
I am getting very poor battery life compared to others so I want to have my phone replaced. I have an extended warranty from FutureShop so I probably don't even need to reset the phone to stock again (they swap on the spot) but I would like to anyway. It will also allow me to test the battery again with the stock ROM.
So, how do I go about flashing back to the Bell ROM and turning S-ON, and unrooting? Keeping in mind that I used the pre-gfree method. I believe it was Visionary R12 and gtab's guide.
Also as the title implies, I was wondering if it's possible to use the new (better) S-OFF even if I am already S-OFF'd the old way?
Any help is appreciated!

You can use gfree and achieve "real" S-OFF without having to unroot.
Just run it. Worst that'll happen is it fails if you happen to be on a kernel it doesn't like. If this happens, no harm is done, just a reboot.

Just run gfree from where you are, as the previous poster said.
That will put you in a much safer position, where you can get stuck in that boot loop that you can if you've only got the eng hboot.
Then you can flash whichever ROM you want. Then you can undo gfree if you want via its new options (see the Wiki).
Regarding your point about the merger, IMHO this issue isn't anything to do with the DZ specifically, and lots of users are posting about similar stuff with their G2s. It's all the same

Thanks guys,
I've done gfree (which is MUCH easier than the thread and wiki make it look - they need to simplify the text, it's overwhelming to look at given how simple the procedure is) and flashed the Bell RUU.
Now I am just about to root, and use gfree to undo the S-OFF I guess?
Will let you know how that turns out. Thanks again!

Ok,there is a new gfree method to get root and S-Off.
And gfree can now also be used to set radio S-ON.
But what about the backup "part7backup-1291675121.bin"
which gfree created at my sdcard?
No longer needed?
And with the new root and S-Off method,is it now possible to
to flash stock RUU 1.34.405.5 to get all original?
Because with old UBERROOT method this doesn`t work!

Ganii said:
Ok,there is a new gfree method to get root and S-Off.
And gfree can now also be used to set radio S-ON.
But what about the backup "part7backup-1291675121.bin"
which gfree created at my sdcard?
No longer needed?
And with the new root and S-Off method,is it now possible to
to flash stock RUU 1.34.405.5 to get all original?
Because with old UBERROOT method this doesn`t work!
Click to expand...
Click to collapse
I'd keep that backup file as it is a dump of your original partition 7 before gfree mods it. You can dd i back and put everything back to how it was, if you ever need to. Do you need to keep it on the phone? No.. store it somewhere on your PC.
With the old "fake" S-OFF you would get stuck if you flashed a stock rom because it would overwrite the engineering HBOOT which was the only thing making your phone think it had S-OFF. With gfree method, you have real S-OFF, so this should be fine.
See http://forum.xda-developers.com/showthread.php?t=838484 for details.
tl;dr You should be fine.

Hm,little bit confused!
The backup I need to get original original partition 7
but not to get S-On.
To get S-On I can use the new gfree method,it`s now
possible with this!
I did the old UBERROOT method with real S-Off!
P.S.I read here about this:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2

Not 100% sure I understand the question...but:
You don't need that backup file. If you delete it nothing bad will happen. Paranoid people (like me) would copy it to a safe place, but there's no real need.
You can flash whatever roms you like, including stock ones, as long as you have real, radio (gfree) S-OFF.

Hi guys, thanks for the help! I got it all settled, it was easy.
As I mentioned above, I used gfree to do a true S-OFF, which was easy.
Then I ran Bell's RUU and it worked without any issues. I assume the RUU install also flashes the HTC recovery back to the phone, I didn't check but it must..
A little summary for anyone who needs help in the future..
If you rooted/S-OFF'd using a method older than the current rage/gfree method (the one in the wiki) then you need to redo the S-OFF using gfree.
Steps:
Use gfree -f to S-OFF again
Run the stock RUU file on your pc (you need HTC sync installed for this)
Temproot (first part of the wiki guide) the stock ROM
Use gfree -s on to S-ON your phone
Reboot, and everything should appear like stock (aside from still being sim-unlocked).

Were u sucessful in returning your phone to htc after u did the above?

I didn't have to return it to htc, just to future shop, and it was fine.
Sent from my GT-I9000 using XDA App

[Q] Reverting to Stock Completely

I have been having issues lately with my incredible (launch batch) overheating and shutting off without any cpu intensive processes running. My setup is
CyanogenMod 6.0.1-Inc
Rooted, S-Off
Radio BaseBand 2.15.00.07.28
I'd like to revert completely back to stock to see if the issue is a hardware problem, a particular application, or the rom itself (although based on http://forum.xda-developers.com/showthread.php?t=856369 it doesn’t seem like this’ll fix the issue, I would need stock anyways to RMA it). Problem is, I haven't been able to find any guide that is relatively recent. I have looked at the following guides/faqs:
http://unrevoked.com/rootwiki/doku.php/public/forever
http://forum.xda-developers.com/showthread.php?t=726791
but I am not sure if any of them are up to date, or are for my situation. From my understanding the procedure is something like flashing PB31img.zip (where to get this, I'm not sure) and re-locking the nand (to s-on) using unrevoked forever.
Is there any particular set of instructions that can be recommended to follow? Or do any of the guides listed above have the correct relative instructions for what I am trying to do?

Use this guide:
http://forum.xda-developers.com/showthread.php?t=786436
And use part 0 and part 2, DON'T USE PART ONE
I repeat, DO NOT USE PART ONE.
And you're done.

that looks exactly like what I needed, thanks! I'm not sure how I missed that post while searching the forums though. I'll try this tonight and report back.

Always glad to help

That guide worked like a charm. Granted, I'm still having the issues random reboot issues I was having before, but that's a whole other issue.
Thanks again wdfowty.

[Q] Is it possible to restore after flashing, S-OFF, etc.

Hi,
I must admit that I am still learning a lot of the terms and procedures relating to the various customisation which can be done to the DHD. Before I consider changing ROMs, rooting, etc. I need to be sure that I will be able to restore my phone back to a point that my warranty is preserved.
My current build number is 1.84.110.3 running Froyo (2.2.1).
If I got through the process of root, s-off, ROM flashing, etc. can I revert it back to how it was before I played with it? I suppose it would be possible to go to a ROM that I have found for my provider (T-Mobile UK):
RUU_Ace_TMO_UK_1.75.110.2_R_Radio_12.28e.60.140f_26.04.02.17_M2_SF
however, is it easy to put the phone back to S-ON and receive the updates over the air (hopefully back to 1.84.110.3)?
Thanks,
smacky_t

smacky_t said:
Hi,
I must admit that I am still learning a lot of the terms and procedures relating to the various customisation which can be done to the DHD. Before I consider changing ROMs, rooting, etc. I need to be sure that I will be able to restore my phone back to a point that my warranty is preserved.
My current build number is 1.84.110.3 running Froyo (2.2.1).
If I got through the process of root, s-off, ROM flashing, etc. can I revert it back to how it was before I played with it? I suppose it would be possible to go to a ROM that I have found for my provider (T-Mobile UK):
RUU_Ace_TMO_UK_1.75.110.2_R_Radio_12.28e.60.140f_26.04.02.17_M2_SF
however, is it easy to put the phone back to S-ON and receive the updates over the air (hopefully back to 1.84.110.3)?
Thanks,
smacky_t
Click to expand...
Click to collapse
i was just going to ask the same question... while I'm on 2.3.3 and with an Italian carrier i wanted to figure out the same thing.. if i go ahead with eng off s off and so on.. while i be able to restore it all back to stock for warranty purposes?

[Q] Semi-noob questions about rooting

First of all thanks in advance for help from all you lovely people.
I'm something of a semi-noob when it comes to Android phones, though I have a fair amount of experience with Windows Mobile HTC devices.
I've had a couple of Android tablets some cheap unbranded chinese crap and and an Advent Vega, both of which I succesfully rooted via different methods.
So I have a little (though I stress a little) familiarity with ADB and clockworkmod recovery.
I'd appreciate if someone could help me understand a few things about the Desire Z though. I have a Desire Z sold retail, with no network lock, with CID HTC__001.
1. If I root this device ( probably via this guide http://forum.xda-developers.com/showthread.php?t=1055581 ) would I be able to update to official ROMs in the future or does this always become difficult/impossible after rooting?
2. If i take a Nandroid backup immediately after rooting. Then later restore this backup and follow the guide I have seen for "unrooting" the device, would I then effectively be back to stock (or as close as possible)? If so should official OTA updates work again after this?
3. If 2 is wrong (which it could be since I am a noob!), is there anyway to get back to stock (or close enough for warranty returns/OTA updates) after rooting.
Again thanks for the help from all you knowledgable folk.

1) Rooting (and gfree) doesn't limit the ROMs you can flash, it completely opens it up. Running gfree gives you SuperCID and S-Off, so you can flash any ROM intended for our phone, regardless of what CID the ROM is intended for. But if you flash an official ROM, you will lose root again. Most ROMs have pre-rooted, but otherwise untouched (or at least, minimally modified) versions posted in the Development section. Once you are rooted, you should stick to those.
2 & 3) There are step-by-step instruction on how to unroot and return to stock in the Wiki: http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Returning_to_Stock

Perfect! Thanks for the help.
There's so many warnings and "I'm not reponsible if flashing this ends the world" type lines in the guides and rom threads, that it can make you quite unsure as to what the potential problems are even if you have a little experience.

[Q] Rooting + Custom Roms: What to care about?

OK, so first of all: YES, I have read almost every sticky about this.
I just want to make sure, I'll do everything right and not destroy my phone.
My Goal:
- Root access (to disable HTCs annoying startup sound and various apps )
- Installing a fast + battery-saving + stable Sense-Based ROM
- Having the possiblity to restore everything to factory default when needed
My Phone:
HTC Desire HD w/ Android Version 2.3.3
I've read that you cannot root your device with this version. Am I right?
My Questions:
- How can I make a backup of my original Android + HTC Sense files?
- Will there be any situation that I am not able to restore anything when my Phone is messed up? (I remember my old iPhone, if something went wrong with the JB, you just needed to go into iTunes, press Restore and everything is fine)
I don't want to make a Quick Shot like read one tutorial, do it like that and boom, Phone's messed up.
Can you recommend me tutorials for:
- Creating a backup?
- Rooting my phone?
- Installing a custom 2.3.3 ROM?
- What else I need to do to perform those 3 above steps?
(Yes, I've read the stickies as I said, but I always like other users to directly help me with my questions )
Thank you in advance Fellas

So OK, I've managed to come a little clearer:
1.: Permroot via Visionary - very easy, seems to work with any Android Version
2.: S-Off: http://forum.xda-developers.com/showthread.php?t=855403 + Radio-S-Off: http://forum.xda-developers.com/showthread.php?t=857537 - seems to be quite easy as well, BUT requires a downgrade
3.: I am able to install custom ROMs
So: To fully "unlock" my phone I'll probably need to downgrade it? But if I install custom ROMs I can basically choose any Android Version I want?
AND: What about Backups/Restore/etc. if anything goes wrong? Which security do I have?

WAIT!
Permroot Visionary only works on sense build 1.32 ONLY.
You will only gain temproot and have the options to:
[*] Backup data with Titanium Backup
[*] Directly downgrade to 1.32
You could use this guide to downgrade
http://forum.xda-developers.com/showthread.php?t=1152233
Follow the guide carefully, as mistake will bring upon the brick lord. But you'll be safe once you've downgrade to 1.32. Plus, if its bricked anyway, just install ruu using adb and you'll be back to your stock sense.
8penned from my blazing fast DHD

So if something goes wrong while Downgrading I still don't have a 100% brick?
PS: Yes I discovered Visionary didn't work for 2.3.3 (even Temproot didn't work). I now try to use GingerBreak to root it and backup my current Android Version using ROM Manager. But GingerBreak is running the second time for over half an hour and nothing changes (USB Debugging enabled, SD Card Mounted)

The critical "flashes" are the bootloader and the radio. At least the radio is flashed while downgrading. I am not sure about the bootloader.
But the risk to brick your phone is very very low. But it is possible.
Edit: If Gingerbreak does not work, you have to check your build number. It is in settings, phone info, software info. The build number has be be lower or equal 2.36. If it is higher, you have to use a build number 2.50 guide to root your phone.