Related
So I'm assuming that the "One Click Root" method is not going to work in Donut. Is that correct?
If so, I'll need to downgrade to Cupcake first. Does anyone have a download link? Is there anything I need to do before applying the update.zip to downgrade?
Thanks for your support
OolonColuphid said:
So I'm assuming that the "One Click Root" method is not going to work in Donut. Is that correct?
If so, I'll need to downgrade to Cupcake first. Does anyone have a download link? Is there anything I need to do before applying the update.zip to downgrade?
Thanks for your support
Click to expand...
Click to collapse
Go read the many stickies on rooting. You don't downgrade to Cupcake, you downgrade all the way back to RC29.
cigar3tte said:
Go read the many stickies on rooting. You don't downgrade to Cupcake, you downgrade all the way back to RC29.
Click to expand...
Click to collapse
Your suggestion doesn't make any sense since there are plenty of devices that shipped with 1.5 (i.e. rogers dream), which happen to be quite incompatible with 1.0 firmware. It is therefore impossible to downgrade to rc29.
If you're *very lucky*, the bootloader you have won't enforce versions and might actually allow downgrading to 1.5, in which case the 1c-root procedure will work.
lbcoder said:
Your suggestion doesn't make any sense since there are plenty of devices that shipped with 1.5 (i.e. rogers dream), which happen to be quite incompatible with 1.0 firmware. It is therefore impossible to downgrade to rc29.
If you're *very lucky*, the bootloader you have won't enforce versions and might actually allow downgrading to 1.5, in which case the 1c-root procedure will work.
Click to expand...
Click to collapse
My apologies, only thought of the G1.
lbcoder said:
Your suggestion doesn't make any sense since there are plenty of devices that shipped with 1.5 (i.e. rogers dream), which happen to be quite incompatible with 1.0 firmware. It is therefore impossible to downgrade to rc29.
If you're *very lucky*, the bootloader you have won't enforce versions and might actually allow downgrading to 1.5, in which case the 1c-root procedure will work.
Click to expand...
Click to collapse
Are you saying that I wouldn't be able to root using the "traditional" method?
OolonColuphid said:
Are you saying that I wouldn't be able to root using the "traditional" method?
Click to expand...
Click to collapse
Post your phone info before you ask that.
cigar3tte said:
Post your phone info before you ask that.
Click to expand...
Click to collapse
Sorry. It's a US T-Mobile G1
I would like to know the answer to this too. I was updating to 4.1.999, something went wrong and now im on 1.6 dev phone firmware. Im not sure if i can go back to rc29 or not or if i should even try. Won't going back to RC29 with the new SPL brick my phone?
(Current) Details are
G1 / Dream phone
firmware 1.6
hard SPL
Build: dream_devphone-userdebug 1.6 DRC83 14721 test-keys
Normal recovery console
Thanks
HardSPL won't brick phones, not to the same degree as dangerSPL anyways.
If you have a REAL SPL (i.e. Engineering, or Hard -- can't imagine why anyone would want that though since it doesn't offer any real advantage over Engineering), then there is ABSOLUTELY NO REASON to go flashing nbh's/downgrade to rc29. The reason for this is that these bootloaders do NOT enforce signatures, and DO allow full access to the system. The only reason for going to rc29 is if you have a RECENT VERSION UNHACKED device that is CARRIER BRANDED (and happens to be compatible).
If you have Engineering SPL or similar, then the ONLY thing that nbh's will do is RISK CREATING A BRICK.
Yes, you can brick *any* time you write an NBH, IPL, or SPL (not just the deathspl). Chances are low, but if something goes wrong, its dead.
sprarky said:
I would like to know the answer to this too. I was updating to 4.1.999, something went wrong and now im on 1.6 dev phone firmware. Im not sure if i can go back to rc29 or not or if i should even try. Won't going back to RC29 with the new SPL brick my phone?
(Current) Details are
G1 / Dream phone
firmware 1.6
hard SPL
Build: dream_devphone-userdebug 1.6 DRC83 14721 test-keys
Normal recovery console
Thanks
Click to expand...
Click to collapse
lbcoder said:
If you have a REAL SPL (i.e. Engineering, or Hard -- can't imagine why anyone would want that though since it doesn't offer any real advantage over Engineering), then there is ABSOLUTELY NO REASON to go flashing nbh's/downgrade to rc29. The reason for this is that these bootloaders do NOT enforce signatures, and DO allow full access to the system. The only reason for going to rc29 is if you have a RECENT VERSION UNHACKED device that is CARRIER BRANDED (and happens to be compatible).
If you have Engineering SPL or similar, then the ONLY thing that nbh's will do is RISK CREATING A BRICK.
Yes, you can brick *any* time you write an NBH, IPL, or SPL (not just the deathspl). Chances are low, but if something goes wrong, its dead.
Click to expand...
Click to collapse
OK cool. Thanks for that. That confirms a few things for me.
Now this might seem a little ignorant but how do i get my root back now? I have done several searches but couldn't really find anything that confirms the exact method for this situation.
If there is no reason to go back to RC29 and do that whole process again then whats the other way of doing it?
As i now have the normal recovery console back any attempt to try and flash CM's just results in the phone telling me i cant su (or don't have root)
Thanks again
Sounds like you have acess to fastboot with your spl you could use fastboot to flash cyanogen's or whichever recovery image you choose, then you would be able flash any rom's you would like through recovery
jackslim said:
Sounds like you have acess to fastboot with your spl you could use fastboot to flash cyanogen's or whichever recovery image you choose, then you would be able flash any rom's you would like through recovery
Click to expand...
Click to collapse
Yeah i do! that sounds exactly like what i need to do. You know of a how-to anywhere for doing this?
Cheers
Do you already have fastboot installed on your pc?? If not a simple search of theese forums can yield you instructions on setting up fastboot. Once you have it installed you can open up a terminal and go the directory in which your recovery image is stored and run the command
fastboot flash recovery cm-recovery1.4.img assuming you're using cyanogen's recovery
jackslim said:
Do you already have fastboot installed on your pc?? If not a simple search of theese forums can yield you instructions on setting up fastboot. Once you have it installed you can open up a terminal and go the directory in which your recovery image is stored and run the command
fastboot flash recovery cm-recovery1.4.img assuming you're using cyanogen's recovery
Click to expand...
Click to collapse
Hey,
Thanks for your help. Managed to get it all working they way you described after some searching and a few hours. Thanks again dude.
OolonColuphid - Hope i didn't hijack your thread too badly. Does any of the above information help you out at all? I found it fairly easy to flash the recovery from fastboot then flash back to whatever i want via the recovery console.
Cheers,
Sean
Alright, I've been doing some reading up on rooting and it sounds interesting. I tried following the steps on theUnlockr.com but keep running into issues. Just FYI, I recently upgraded to 1.6 Donut from 1.5 thru a phone update so it is NOT stock in my phone. Please let me know what I need to do (in lamens terms) so I can get this going.
G1/Dream
Firmware 1.6 Donut
Build Number: DRC83
Please let me know what I need to do (in lamens terms) so I can get this going.
ephayzee said:
Alright, I've been doing some reading up on rooting and it sounds interesting. I tried following the steps on theUnlockr.com but keep running into issues. Just FYI, I recently upgraded to 1.6 Donut from 1.5 thru a phone update so it is NOT stock in my phone. Please let me know what I need to do (in lamens terms) so I can get this going.
G1/Dream
Firmware 1.6 Donut
Build Number: DRC83
Please let me know what I need to do (in lamens terms) so I can get this going.
Click to expand...
Click to collapse
You're phone is still considered stock because it has unmodified software on it, even though you have 1.6 it's through the official OTA update whether installed manually or recieved in due time over your network. You can root your phone, pretty much just follow the steps outlined in this guide found on theese forums
http://forum.xda-developers.com/showthread.php?t=442480
jackslim said:
You're phone is still considered stock because it has unmodified software on it, even though you have 1.6 it's through the official OTA update whether installed manually or recieved in due time over your network. You can root your phone, pretty much just follow the steps outlined in this guide found on theese forums
http://forum.xda-developers.com/showthread.php?t=442480
Click to expand...
Click to collapse
Good looking man, thanks!
Does FlashRec still work on donut, or have they patched that exploit?
OolonColuphid said:
Does FlashRec still work on donut, or have they patched that exploit?
Click to expand...
Click to collapse
OMG! can u not read!
Its only going to be a matter of time before people will need to send phones back under warranty for whatever reasons so a guide for unrooting will be needed.
Any takers?
G2 already has one, but obviously we will need different rom/hboot etc to go back to our stock.
Not just unrooting, but going completely back to stock, i.e. S-ON and stock ROM.
As you say, we should be able to base it on this - http://forum.xda-developers.com/showthread.php?t=835971
Although we have several different stock ROMs, e.g. European, Asian, Vodafone UK, etc.
this is already covered in the FAQ (easy tutorial @ dev forum)
http://forum.xda-developers.com/showpost.php?p=9143411&postcount=2
gtrab said:
this is already covered in the FAQ (easy tutorial @ dev forum)
http://forum.xda-developers.com/showpost.php?p=9143411&postcount=2
Click to expand...
Click to collapse
That just says to use Visionary to turn off rooting. Or did I miss something ?
As I said, I think we need to cover how to return a phone completely to stock, and I don't think it includes all that you'd really need to do, or if you didn't use Visionary in the first place, e.g. the kind of stuff in the G2 post that I linked.
steviewevie said:
That just says to use Visionary to turn off rooting. Or did I miss something ?
As I said, I think we need to cover how to return a phone completely to stock, and I don't think it includes all that you'd really need to do, or if you didn't use Visionary in the first place, e.g. the kind of stuff in the G2 post that I linked.
Click to expand...
Click to collapse
It does say to flash an RUU to S-ON which in the past I would have said would work, but seeing how the G2 forums are not suggesting that its that simple my guess would be that its not that simple.
I had to flash the PC10img thing taken from the stock ROM to restore root and s-on. But no idea how to extract that PC10img thing, not that I have looked into it either.
That info was from one of the guides in the dev section I'm sure.
Sent from my HTC Vision using XDA App
What might work now will probably not work once an OTA update comes out for the DZ though, as per the problem on the G2 they've had which has led to quite a few semi-bricks (possibly full bricks in some cases ?).
Done some research, it would seem that flashing an RUU would work fine for those of us already rooted, if an OTA were to come out those who rooted after the OTA would have issues unless an RUU for the same OTA was released as well. (this is basically because the RUU's currently available will be older than the software the phone is on so the RUU would fail leaving you with a semi-bricked phone as described above, basically it would flash stock hboot and recovery then fail to flash the /system so you would be left with no root or recovery and no rom.
Flashing the ruu would give rise to accepting the OTA too, if you really wanted to do that, but it might block root.
you just need the RUU for your correct original phone version
OR use a gold card
eg. I have debranded mine from bell NAM 1.34.666.5 to euro generic 1.34.405.5
To go back to stock, I can:
1.- grab the bell 1.34.666.1 RUU (its slightly previous, but is the correct original version for my phone)
OR
2.- run the euro generic 1.34.405.5 with a golcard inserted
gtrab said:
you just need the RUU for your correct original phone version
Click to expand...
Click to collapse
Isn't that dangerous though once we get any OTAs, and could lead to this ?
http://forum.xda-developers.com/showthread.php?t=838484
Or am I missing something ?
steviewevie said:
Isn't that dangerous though once we get any OTAs, and could lead to this ?
http://forum.xda-developers.com/showthread.php?t=838484
Or am I missing something ?
Click to expand...
Click to collapse
Yes thats what I was getting at in my post above, any RUU you flash needs to be of the same or newer version of what your previously flashing. You cannot GoldCard to flash an RUU to S-ON or you get left with the semi-brick where you have stock recovery and hboot, but no rom installed.
So if an OTA comes out, you can't accept it, s-off then use an older RUU to s-on again. You would have to flash an RUU of that OTA version (if one is released).
Basically its best to not accept any OTA if you can avoid it and just wait for a custom rom of the same, that way we can always use the older RUU's to s-on if we need it.
I successfully downgraded my rooted/S-OFF'd phone to an earlier ROM last night. I simply followed this method - http://forum.xda-developers.com/showthread.php?t=832503
I'm of the firm belief that this is the onyl way to do it if you are at S-OFF. If you have S-OFF, then flashing an older RUU will probably brick your phone.
Well yesterday I perm root and s-off my european Desire Z with World/Euro generic 1.34.405.5. Somehow everything went bad after flashing recovery mode, so I decided to unroot it and bring it back to original settings.
I found there are 2 methods, one is to run the original ruu, and the other one was to copy the exact World/Euro generic 1.34.405.5 PC10img.zip to the root of my sd card.
Then entered to bootloader, and the phone recognize the archive, I simply apply it, and now I am back again to original stock.
However now I tried again and I am happily root, and S-Off following the amazing gtrab guide (http://forum.xda-developers.com/showthread.php?t=835777)
buzmay said:
I found there are 2 methods, one is to run the original ruu, and the other one was to copy the exact World/Euro generic 1.34.405.5 PC10img.zip to the root of my sd card.
Click to expand...
Click to collapse
That's the thing I keep saying though, flashing the original RUU worked for you because you weren't trying to downgrade the ROM, it was the same version that you already had on (just S-OFF etc). If you had a later version on your phone (e.g. via an OTA update) and were trying to flash to an earlier one, you would have bricked it trying the straight RUU method.
So what should be done is download and install an RUU - say 1.234.987, so you're on 1.234.987 - then root / S-OFF / custom ROM the phone. If anything goes wrong, reinstall the 1.234.987 RUU.
By the way - that's a fake RUU
DanWilson said:
So what should be done is download and install an RUU - say 1.234.987, so you're on 1.234.987 - then root / S-OFF / custom ROM the phone. If anything goes wrong, reinstall the 1.234.987 RUU.
Click to expand...
Click to collapse
During that process, if the stock HBOOT/recovery that is installed by that RUU decides that what you're trying to flash is "older" than your custom ROM, you're screwed though. That's why the "debranding" guide has extra steps in it, i.e. gold card and editing the misc partition.
steviewevie said:
During that process, if the stock HBOOT/recovery that is installed by that RUU decides that what you're trying to flash is "older" than your custom ROM, you're screwed though. That's why the "debranding" guide has extra steps in it, i.e. gold card and editing the misc partition.
Click to expand...
Click to collapse
I hate HTC.
Love the phones, love the Sense, hate the security.
Why not give us a command like the N1? WHY!?
So you should backup the system partition before S-OFF and so on? Like so a dd? (Following on from previous post)
DanWilson said:
So you should backup the system partition before S-OFF and so on? Like so a dd? (Following on from previous post)
Click to expand...
Click to collapse
The system partition isn't changed in S-OFF, that's the boot partition (just allows writing to the system partition).
The gold card and editing of the misc partition should work fine, as per this thread - http://forum.xda-developers.com/showthread.php?t=832503
It worked for me last night to flash to an older stock ROM (which also gave me S-ON again, removing my S-OFF).
steviewevie said:
The system partition isn't changed in S-OFF, that's the boot partition (just allows writing to the system partition).
The gold card and editing of the misc partition should work fine, as per this thread - http://forum.xda-developers.com/showthread.php?t=832503
It worked for me last night to flash to an older stock ROM (which also gave me S-ON again, removing my S-OFF).
Click to expand...
Click to collapse
Cool. Confused. I believe you though.
But you are saying just to make a gold card, and edit the misc partition?
Nice
DanWilson said:
Cool. Confused. I believe you though.
But you are saying just to make a gold card, and edit the misc partition?
Click to expand...
Click to collapse
Following that guide that I linked worked for me. Yes, I turned my SD card into a gold card and edited the misc partition. Then it is fooled into thinking you're restoring a ROM of the same version that it already is running, so it lets you do it.
Actually, I do wonder whether both steps are necessary (i.e. gold card *and* editing misc), because I thought the whole point of the gold card was that it avoided those checks, so perhaps you can do one or the other ? I am only thinking out loud here, and may well be missing something, so I don't suggest trying it other than as in that guide.
Right now, the previous rage/Visionary rooting methods do *not* work with the latest 1.72 ROMs for the Desire Z.
UPDATE - If you have upgraded to 1.72 already without S-OFF, then a temp root has been achieved for 1.72, which gives you the capability to downgrade to an earlier ROM (e.g. 1.34) where you can permanent root. The "psneuter" procedure is at via this procedure - http://forum.xda-developers.com/showthread.php?t=905261
UPDATE 2 - This "psneuter" procedure can be used to achieve permanent root. If you obtain S-OFF at an earlier ROM level, *then* update to 1.72, you can get permaroot with psneuter, then use the usual methods to lock this in as a permanent root. This is because the S-OFF means the NAND write protection will not be enabled. If you are already at 1.72 without S-OFF, you will have to downgrade, obtain S-OFF, then upgrade again.
This ROM version is being rolled out as an OTA update to European DZ users. So far it doesn't seem to have been rolled out to other DZ carriers, e.g. Bell, Vodafone, though I suspect that it is only a matter of time.
This update does not *yet* affect the G2 running the stock T-Mobile ROM, though again I suspect this update will make its way to the G2 in time (so you might wish to turn off automatic checks for updates if you want to avoid the possibility).
This is an example of what is in the warning thread at the top of the forum, i.e. don't upgrade to this until we know how you can root it, assuming you are interested in root (which I think most, though not all, people here are).
I've tried all kinds of stuff but nothing works.
I've even made a goldcard with a PC10IMG.zip (rom extracted from RUU) but it gives me an error: MAIN VERSION OLD
So flashing back to an older version.............forget it!!
RUU, Visionary and Gfree method will not work with this stupid update!
Does anyone know what's in the 1.72 release that we're missing ? (And therefore whether its worth S-On & de-rooting)
Ramsfan_Jim said:
Does anyone know what's in the 1.72 release that we're missing ? (And therefore whether its worth S-On & de-rooting)
Click to expand...
Click to collapse
The Virtuous ROM includes all the stuff in 1.72 already. So there's no point derooting and going S-ON, just install Virtuous.
Sticky worthy untill a solution is found.
rmk40 already found a solution to rooting these newer builds, but it requires changes to the SuperUser app. He's submitted those to the author but there hasn't been a new version release yet.
Hm,I`m now on stock 1.34.405.5 Firmware (RUU_Vision_HTC_WWE_1.34.405.5_Radio_12.28b.60.140e _26.03.02.26_M)
but rooted and S-OFF with UBERROOT method!
Now if I flashing this Firmware I still have S-OFF but I lose
Root and can`t Root again right?
The same happens if I trie this Root and S-OFF method and flashing
the new Firmware:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
If you are desperate to try it, nandroid backup, google "extract rom.zip from ruu" and install through recovery.
..sent from my CyanogenMod'd HTC Vision
That will not work. I've already tried it.
maus010 said:
That will not work. I've already tried it.
Click to expand...
Click to collapse
Why not?
..sent from my CyanogenMod'd HTC Vision
Glad there is a dedicated thread for this. I have applied the OTA (stupid me... should have read this forum first) and am now looking forward to getting root again so i can do SetCPU to underclock when screen off..
I'm happy to do any testing for those who get anythin working.
Also noticed in this new ROM (OTA) that when i plug in my wall charger, it goes straight into "CAR PANEL"?!
When i use the official HTC cable it does not - but when using a mini USB cable + micro USB adapter, it goes straight into car mode.
Does this have the same issue if you just flash the radio?
wileykat said:
Why not?
Click to expand...
Click to collapse
Because it gives me an error: MAIN VERSION OLD
So it wil not flash.
As long as you still have a custom recovery (i.e. Clockwork), I can help. See the thread I just created here:
http://forum.xda-developers.com/showthread.php?t=886999
If not, sorry I cannot help. Obtaining root again is for the black hats around here.
I wont root my DZ since setCPU profiles dont work.
rmk40 said:
As long as you still have a custom recovery (i.e. Clockwork), I can help. See the thread I just created here:
http://forum.xda-developers.com/showthread.php?t=886999
If not, sorry I cannot help. Obtaining root again is for the black hats around here.
Click to expand...
Click to collapse
Thanks for your help.
But the OTA update also flashed the bootloader and recovery back to stock.
The only thing positive with this update is the batterylife.
It hase improved bigtime!
Agree - battery seems heaps better.
Is anyone working on this? Got my DZ and subconsciously accepted.
Am now because I need to keep using the damn power button to wake it up!
zappoo said:
Also noticed in this new ROM (OTA) that when i plug in my wall charger, it goes straight into "CAR PANEL"?!
When i use the official HTC cable it does not - but when using a mini USB cable + micro USB adapter, it goes straight into car mode.
Click to expand...
Click to collapse
There's a note in the manual for the DZ that says if you use an adapter it will think it's plugged into a car kit.
Today I accidently turned it on (the thing in the bootloader) and now I can't turn it off no matter what so I can do a revert to stock .img, I used the PDI15.img or w.e that would revert back to stock forgetting that I had the newest radio and now I can't revert to stock or turn S-OFF. Please help
Current Configurations:
GLACIER PVT SHIP S-ON
HBOOT - 0.86.0000
MICORP - 0429
RADIO - 26.09.04.26_M
eMMC - BOOT
More Info:
When I use a PDIMG or w/e file it errors out as being old
Can you still boot? Like into your rom? If so just try rooting using visionary and using a root explorer to push the gfree files to data/local/ then just follow the normal rooting procedure
Sent from my HTC Glacier using XDA Premium App
Nicgraner said:
Can you still boot? Like into your rom? If so just try rooting using visionary and using a root explorer to push the gfree files to data/local/ then just follow the normal rooting procedure
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
Yeah I can still boot into my rom, bootloader, and recovery and okay will try that
EDIT: Okay I did, I tried turning S-OFF but it says something about eMMC power cycle failed
XxKOLOHExX said:
Yeah I can still boot into my rom, bootloader, and recovery and okay will try that
EDIT: Okay I did, I tried turning S-OFF but it says something about eMMC power cycle failed
Click to expand...
Click to collapse
dude! I noticed this also this morning. I am rooted(using setcpu and root explorer just fine) but in hboot it says s=on. I was also wanting to flash the stock .img and start fresh. thought I was the only one having this problem. tried everything you did and got the same results.
What ROM are you on? AFAIK, gfree, requires the stock kernel to do what it does. How on earth did you turn S-ON? That sort of thing shouldn't just happen out of nowhere.
How is the progress on fixing your phone?
jdkoren said:
What ROM are you on? AFAIK, gfree, requires the stock kernel to do what it does. How on earth did you turn S-ON? That sort of thing shouldn't just happen out of nowhere.
Click to expand...
Click to collapse
currently on Evil D mTGB v1.0, Faux 0.0.7 CFS lv leak kernel. everything works fine, no FC's or anything. just having the same issues as XxKOLOHExX. I really have no idea how it turned on by itself, I dont remember doing anything out of the ordinary
I was trying to get back to stock from the rom i was on. (MIUI) and when I used the stock .img though the bootloader it went all good till it rebooted, then it said failed because the file was old and now I am stuck with s-on and I don't know how to turn it off
How did you get to the stock bootloader? Did you have eng bootloader at one point? What meth of root did you use? Alot of info missing.
Now download the stock radio.img and push it via adb or just download the PD15IMG.zip (radio only not rom included). Once this is done you can revert back to stock rom/radio using standard PD15IMG.zip (radio+rom). Now depending on the type of root you used it would depend if you still have radio flag on/off even if your reverted back to stock bootloader.
PS: You can get PD15IMG.zip (stock radio) from master radio thread and PD15IMG.zip (stock radio/rom) by doing search.
PermROOT said:
How did you get to the stock bootloader? Did you have eng bootloader at one point? What meth of root did you use? Alot of info missing.
Now download the stock radio.img and push it via adb or just download the PD15IMG.zip (radio only not rom included). Once this is done you can revert back to stock rom/radio using standard PD15IMG.zip (radio+rom). Now depending on the type of root you used it would depend if you still have radio flag on/off even if your reverted back to stock bootloader.
PS: You can get PD15IMG.zip (stock radio) from master radio thread and PD15IMG.zip (stock radio/rom) by doing search.
Click to expand...
Click to collapse
It flashed the bootloader when I flashed the PD15IMG.zip, it just stop when I did the whole procedure. Nope never flashed an Engineer Bootloader. I used theunlockr.com sites method
I tried that, it uziped then tried to flash the radio then just went back to the original menu for the bootloader
If you used the VISIONary+ (TempROOT) and root.sh (PermROOT) meth then you already had engineering hboot (0.85.2007) pushed though terminal on "/dev/block/mmcblk0p18". Now you did something in between is what I would like to know.
As you flashed new radio (26.09.04.26_M) which I am clear. But what I like to know is how did you end up with default hboot (0.86.0000)? If you had S=OFF you didn't lose it via flashing new radio. Which PD15IMG.zip did you install? Now when you say PD15IMG.zip what do you mean? It can be anything as its default mt4g system based image. Stock PD15IMG.zip = (Sense 2.2.1 Rom/Radio 26.03.02.26_M). Did you install leaked PD15IMG.zip from Panache? or GB2.3.3S?
Are you not 1 of the Royal dev's? who try to take over Silence's IG if I recall. I am just assuming here but this is why you do "NOT" dump system image via hboot. What you should have done was do complete total system wipe (format /data; /system) and then flash new edify based CWMR flashable rom.
PermROOT said:
If you used the VISIONary+ (TempROOT) and root.sh (PermROOT) meth then you already had engineering hboot (0.85.2007) pushed though terminal on "/dev/block/mmcblk0p18". Now you did something in between is what I would like to know.
As you flashed new radio (26.09.04.26_M) which I am clear. But what I like to know is how did you end up with default hboot (0.86.0000)? If you had S=OFF you didn't lose it via flashing new radio. Which PD15IMG.zip did you install? Now when you say PD15IMG.zip what do you mean? It can be anything as its default mt4g system based image. Stock PD15IMG.zip = (Sense 2.2.1 Rom/Radio 26.03.02.26_M). Did you install leaked PD15IMG.zip from Panache? or GB2.3.3S?
Are you not 1 of the Royal dev's? who try to take over Silence's IG if I recall. I am just assuming here but this is why you do "NOT" dump system image via hboot. What you should have done was do complete total system wipe (format /data; /system) and then flash new edify based CWMR flashable rom.
Click to expand...
Click to collapse
Yeah I know that, I Was trying to go back to stock everything using the unrooting method(PD15IMG.zip). Using this file I was able to get through the first step and it rebooted, then it went back to bootloader and now it won't take the PD15IMG.zip saying that it is an older file. Yes I am one of the devs, That's why before posting I tried everything I could think of, gfree, old unrooting methods, etc. I didn't use a dump lol I'm not that noobish haha
Thats where you got owned as the PD15IMG.zip (stock rom/radio) just reverted back to hboot (0.86.0000) from eng hboot (0.85.2007). While you attempted to go further you couldn't do to security turning on (S=ON). Now this normally wouldn't be problem but since you had newer radio (26.09.04.26_M) it wouldn't replace it with old.
All you had to do was follow few simple meths which you should have learned it over the years. Go back same way you came by first reverting back to original radio image and then after doing complete system wipe you should have reverted back to original factory based via stock pd15img.
Ill post back with solution soon let me think this out. I don't want to brick your phone trying to manually push the radio.img nor the eng_hboot.img. As if you try to push radio now would fail on write and give you hard brick. Since S=ON and if you try to push eng_hboot.img who knows what will happen as no R/W access on mmcblk could could also fail thus giving bad flash which can also brick the device. Ill see what happens and post back at... you folks just made more extra work for me.
PermROOT said:
Thats where you got owned as the PD15IMG.zip (stock rom/radio) just reverted back to hboot (0.86.0000) from eng hboot (0.85.2007). While you attempted to go further you couldn't do to security turning on (S=ON). Now this normally wouldn't be problem but since you had newer radio (26.09.04.26_M) it wouldn't replace it with old.
All you had to do was follow few simple meths which you should have learned it over the years. Go back same way you came by first reverting back to original radio image and then after doing complete system wipe you should have reverted back to original factory based via stock pd15img.
Ill post back with solution soon let me think this out. I don't want to brick your phone trying to manually push the radio.img nor the eng_hboot.img. As if you try to push radio now would fail on write and give you hard brick. Since S=ON and if you try to push eng_hboot.img who knows what will happen as no R/W access on mmcblk could could also fail thus giving bad flash which can also brick the device. Ill see what happens and post back at... you folks just made more extra work for me.
Click to expand...
Click to collapse
Thank you so much for the help
PermROOT said:
Thats where you got owned as the PD15IMG.zip (stock rom/radio) just reverted back to hboot (0.86.0000) from eng hboot (0.85.2007). While you attempted to go further you couldn't do to security turning on (S=ON). Now this normally wouldn't be problem but since you had newer radio (26.09.04.26_M) it wouldn't replace it with old.
All you had to do was follow few simple meths which you should have learned it over the years. Go back same way you came by first reverting back to original radio image and then after doing complete system wipe you should have reverted back to original factory based via stock pd15img.
Ill post back with solution soon let me think this out. I don't want to brick your phone trying to manually push the radio.img nor the eng_hboot.img. As if you try to push radio now would fail on write and give you hard brick. Since S=ON and if you try to push eng_hboot.img who knows what will happen as no R/W access on mmcblk could could also fail thus giving bad flash which can also brick the device. Ill see what happens and post back at... you folks just made more extra work for me.
Click to expand...
Click to collapse
lol sorry for the extra work, just dont wanna have the chance of bricking my phone but like XxKOLOHExX I wanted to revert back to stock from mTGB using the stock PD15IMG_Glacier_TMOUS_1.17.531.2_Radio_12.28b.60.140e_26.03.02.26_M_release_155771_signed. everything he described is happening to me also, step by step. I rooted with the visionary+ and permroot method(unlockr). I did download and flash the 26.08.04.30 radio. heres what I see in hboot
GLACIER PVT SHIP S-ON
HBOOT-0.86.0000
MICROP-0429
RADIO-26.08.04.30_M3
eMMC-boot
Sep 27 2010, 11:12:59
so what youre saying is that we should try flashing the stock radio first, wipe the whole phone(including sdcard?), then flash the stock PD15IMG? Ill give it a shot real quick, thanks
*edit* hboot wont even let me flash the stock radio, itll say checking but wont actually let me update it
Well clarknick27 the problem here is that root.sh to gain PermROOT via VISIONary+ just push the 0.85.2007 eng hboot and giving temporary S=OFF, the true security flag as we know it is controlled in the radio. So when you try to revert back using stock PD15IMG (rom/radio) it reverted back to the stock 0.86.0000 hboot thus turning on the security flag on.
What you all should have done is reverted back same way you installed it. Which would have been first use PD15IMG.zip (stock radio) and then use stock PD15IMG.zip (radio/rom). I still need some sleep lol I just wokeup after sleeping 2hours.
The MT4G I tested on I rooted it via VISIONary+ and then flashed GB Leak rom not the PD15IMG.zip (leak radio/rom) which contained the 0.89.0005 hboot. So after flashing stock radio PD15IMG.zip (radio 26.03.02.26_M) I was able to flash stock PD15IMG.zip (rom/radio) without problem. Which is same as I suspected even after S=ON due to same version radio no problem. If I had newer radio after that point it would be locked out. Let me go to sleep and wakeup and ill see what happens from there. As I have clean MT4G ill have to reroot it first.
BTW XxKOLOHExX and clarknick27 just in case my account gets disabled. Do the following and report it here and ill see from there.
1) Which working rom you currently have installed on the device?
I know trying to reroot using gfree may give you similar result as my test: http://forum.xda-developers.com/showthread.php?t=1066966 < not important but unable to root on newer rom.
2) What happens when you try to reroot it using VISIONary+ (TempROOT) and root.sh (PermROOT)?
Did you try it? If so what is the end result? so post back. Ill check and go from there.
PermROOT said:
BTW XxKOLOHExX and clarknick27 just in case my account gets disabled. Do the following and report it here and ill see from there.
1) Which working rom you currently have installed on the device?
I know trying to reroot using gfree may give you similar result as my test: http://forum.xda-developers.com/showthread.php?t=1066966 < not important but unable to root on newer rom.
2) What happens when you try to reroot it using VISIONary+ (TempROOT) and root.sh (PermROOT)?
Did you try it? If so what is the end result? so post back. Ill check and go from there.
Click to expand...
Click to collapse
1) currently running Evil D's mTGB v1.0 rom with Faux's 0.0.7 CFS LV leak kernel. tried rooting with visionary and terminal first, no success. I then tried out the gfree method, and got "Attempting to power cycle eMMC...failed. Module failed to load: No such file or directory."
2) I installed Visionary using Astro file manager, then run Visionary. I click on "temproot now" and it starts, but then the screen goes black and doesnt do anything. I have let it sit on the black screen for well over 15mins before with no luck. I can click on "attempt to permroot" and it will ask for permissions and reboot and everything. my s=on but I still have root access and 0.86.000 bootloader. this is what I see using terminal before rebooting to see if s=off
Did you do the Radio S=OFF using gfree? If so that would explain why you still have root as security is disabled on the device totally. If thats the case then just push the eng bootloader manually via adb or though terminal and reboot. For now XxKOLOHExX is locked lets see what I find ill post back for him.
PermROOT said:
Did you do the Radio S=OFF using gfree? If so that would explain why you still have root as security is disabled on the device totally. If thats the case then just push the eng bootloader manually via adb or though terminal and reboot. For now XxKOLOHExX is locked lets see what I find ill post back for him.
Click to expand...
Click to collapse
thanks for taking the time to help out, Ill give it a shot
*edit* just tried pushing the eng bootloader through adb and it didnt stick or flash, rebooted into hboot and it still says 0.86.0000, s=on, 26.08.04.30_M3 radio
Alright, so today I tried unrooting my htc evo using the two step guide found here on the forums.
First I set my s-on using the method described, and then when I tried to update it said "update failed" and something about the firmware being too new.
I have no way of returning back to root right now because my unrevoked doesn't seem to recognize my phone right now. I'm on android 2.2 right now and anything less, my phone won't update to.
I think the only way of fixing this would be the newest signed, unrooted 2.3 update. Does anybody here have it? It should be about 180MB around and named PC36IMG.
I've looked pretty much everywhere for it. I really need to unroot for warrenty purposes.
thanks in advance, so much
Here you go...it was in dev section
http://forum.xda-developers.com/showthread.php?t=884060
In order to run a 2.2 pc36img, your radio and hboot have to match the ones in the zip
Yeah, I used unrevoked. Hopefully this works, if not, I have no idea what I'm going to do.
if you flash the 4.53 pc36img.zip in hboot you should be good. lemme know
do I need to follow the entire ruu guide or can I just place an ruu update in the root of my sd card and load it from hboot?
everything went great. Thanks!