Develop Bugs

[Q] State of system r/w access?

What's the current state of R/W access with the Desire atm? I want to modify a pre-flashed ROM by adding/removing some system files, i remember with the Modaco method I had to boot into the dodgy recovery and it was touch and go, but how do I go about it now? can I remount with adb and change stuff?
I started on the Hero which was a lot easier and havn't done much with the desire since.

short answer, yes you can remount with adb and change system stuff.
It has to be in recovery, and even then I find problems sometimes. havent quite figured out where said problems originate from. These are intermittent.

Hmm
nzdcoy said:
short answer, yes you can remount with adb and change system stuff.
It has to be in recovery, and even then I find problems sometimes. havent quite figured out where said problems originate from. These are intermittent.
Click to expand...
Click to collapse
What kind of problems are we talking about here?

alias_neo said:
What kind of problems are we talking about here?
Click to expand...
Click to collapse
we now have a file overlay system that gives us write access to /system/ even when the desire is booted, its fairly new so i dont know weather it was included in the rom you are using.

once the new unrEVOked is out we'll get S-OFF and then you can do what you want when booted into Android

EddyOS said:
once the new unrEVOked is out we'll get S-OFF and then you can do what you want when booted into Android
Click to expand...
Click to collapse
i didnt know unrevoked has got us a hard spl awsome that means we can get rid of that nasty htc splash

Hmm
Is that confirmed yet that we will get it or not? I remember reading it had been done, but nothing about the Desire.

[GUIDE] Perm-root, write access, Clockwork recovery and overclocking on the Desire Z

Edit: This guide is for EXPERIENCED users ONLY! For less experienced users please check UBERROOT easy full Root, S-OFF, SuperCID AND SIM UNLOCK for DZ/G2/DHD inc Voda .
Remember to always read and research before rooting! Discussion can be found starting on post #101 - #118 ~TheRomMistress
__________________________________________​
Please be aware that I am not responsible for any bricks etc. This is playing around with the phone internals, so be careful.
To get full write access to the Desire Z, we now have an Engineering HBOOT which was posted by MrPaveL (Thanks for that!).
To get your device to the engineering hboot stage [this is not full radio S-OFF, but 99% of people won't need radio S-OFF], please follow the guide below.
If you want full Radio S-OFF, SuperCID or want to remove the simlock on your phone, please follow this guide on instead. Once you have full Radio S-OFF you can use any Desire Z HBOOT and still have access to flash ROMs etc.
Credit goes out to scotty2, and all of the wonderful folks at #G2ROOT!
Donate to scotty2 (for root): [email protected] (PayPal)
This guide was derived from the guide for the G2, created by unrevoked512 on http://forum.xda-developers.com/showthread.php?t=833965. Also many thanks to vro25 for improvement suggestions.
You will need the following files:
VISIONary r14
wpthis-Z.ko MD5 c73c5e77c91d306c418983c002b60b93
hboot_7230_0.84.2000_100908.nb0 MD5 2ce1bdd5e4c1119ccfcecb938710d742
Step 1
Download and run VISIONary r14
Leave everything uncheck and click "temp root" now.
Once that's done click "Attempt Permroot Now!"
You now have permaroot.
Step 2
Push the files wpthis-Z.ko and hboot_7230_0.84.2000_100908.nb0 to /data/local/
Note: You might want to verify the MD5 sums, particularly for the hboot file, as if your download was corrupted, the file will brick your phone.
Step 3
Open a terminal on your phone, or open an adb shell from your computer.
Step 4
Code:
$ su
# insmod /data/local/wpthis-Z.ko
Note: make sure your screen is on before doing this as it will raise a root request on your phone (if you haven't previously granted it) - click ok on your phone to grant root.
It should return:
Code:
init_module 'wpthis-Z.ko' failed (Function not implemented)
That is good.
Step 5
FINAL WARNING: THIS STEP COULD SEVERELY DAMAGE YOUR PHONE. USING THE INCORRECT FILE COULD CAUSE IRREPARABLE DAMAGE, MAKING YOUR PHONE NOTHING MORE THAN A BRICK.
That noted, if you would like S-OFF, go ahead and run this command in your terminal.
Code:
# dd if=/data/local/hboot_7230_0.84.2000_100908.nb0 of=/dev/block/mmcblk0p18
Step 6
I think this is optional, but there are controversial opinions at the moment. In any case it will not hurt to run
Code:
# sync
to make absolutely sure everything will be saved.
Now reboot your phone gracefully and check that everything sticks.
Step 7 (optional)
This step is optional, if you want to install Clockwork Recovery.
Download ROM Manager from the market and install Clockwork, telling it that you have an HTC G2 when it asks. It will work without problems on the Desire Z.
Step 8 (optional)
This step is optional if you want to install an overclocked kernel. You might want to do a nandroid backup first, in case you want to go back later (just restore boot).
This overclocked kernel seems to crash the phone after Youtube videos are played in fullscreen. This issue is being investigated, but could take a while to resolve, since HTC hasn't released the actual DZ kernel source...
I have now recompiled the overclocked kernel for the Desire Z (all credit goes again to coolbho3000 for publishing the source!), to get the FM Radio to work as well. To get it to work please follow the guide on http://forum.xda-developers.com/showthread.php?t=834219, but instead of the zImage posted there (which breaks FM Radio on the Desire Z), get the one from http://www.opencodes.org/node/14 . You still need to use the bcm4329.ko file from the other thread. Also note that this will change your kernel version to 2.6.32.17 (instead of 2.6.32.21 stock). Please blame HTC for not releasing the newest kernel source. In any case I have not spotted any disadvantages...
So far I have not spotted any problems with this kernel, but if you do, let me know.
PS Bacon-bits by cyanogen do not fully work on the DZ. It won't boot with that ramdisk and the lights hack seems to fail as well. It is probably safest to wait for a full CM release, but this guide gets you 90% of bacon-bits.

stridger said:
Hi all,
I have just managed to get clockwork recovery work on the Desire Z. It's a bit hacky at the moment, and will probably get much easier in the due course. I am not going to post every little step that you can find out by googling, and please be aware that I am not responsible for any bricks etc. This is playing around with the phone internals, so be careful.
The reason it is this hacky is that we do not have an engineering bootloader for the Desire Z yet.
Download wpthis-Z.ko and wpthis-pre-OTA.ko from
http://content.modaco.net/dropzone/wpthis-Z.ko and
http://unforgiven512.udderweb.com/downloads/wpthis-pre-OTA.ko and put them in /data/local on the phone.
Download newest version of ROM Manager
Disable write protection via wpthis-Z.ko
Flash clockwork recovery from ROM Manager
Reboot into recovery
Make a nandroid backup !!!!!
Mount /data in Clockwork
Use wpthis-pre-OTA.ko in recovery to disable write protection.
You now have a fully working recovery. (note you will need to use wpthis-pre-OTA.ko step everytime you boot into recovery and want to write something from recovery [not needed for nandroid backups])
Click to expand...
Click to collapse
Your a genius dude Keep up the good work
We need quality devs like you to get this party started
JD

As soon as I did this step:
Disable write protection via wpthis-Z.ko
EDIT:
this is exactly what I did:
$ su
# insmod /data/local/wpthis-Z.ko
got this as result: failed (Function not implemented)
then all applications stopped working, ROM Manager crashed as soon as I select G2 from confirmation dialog when trying to flash Clockwork.
I then tried GMails and got loads of error popups, had to restart phone to get back to normal
EDIT: I do have Visionary installed set to Root on boot.

schriss said:
As soon as I did this step:
Disable write protection via wpthis-Z.ko
EDIT:
this is exactly what I did:
$ su
# insmod /data/local/wpthis-Z.ko
got this as result: failed (Function not implemented)
then all applications stopped working, ROM Manager crashed as soon as I select G2 from confirmation dialog when trying to flash Clockwork.
I then tried GMails and got loads of error popups, had to restart phone to get back to normal
EDIT: I do have Visionary installed set to Root on boot.
Click to expand...
Click to collapse
I urge you not to do anything in this direction, if you haven't even got permroot yet. Look at the G2 permroot forums, where all of these things are answered. The error is supposed to appear. Please be very careful if you don't want to end up with a brick.

I was afraid to do the G2 permanent root because it involved dd command and some G2 HBOOT file. There was one Desire Z user who ended up stuck in bootloader and have seen no other desire Z owners confirming this to work.
I guess I wait...
Sent from Desire Z

I flashed the desire z rom on my g2 yesterday after root, is my g2 now considered a desire z? if so it should be okay for me to follow these instructions right?

schriss said:
I was afraid to do the G2 permanent root because it involved dd command and some G2 HBOOT file. There was one Desire Z user who ended up stuck in bootloader and have seen no other desire Z owners confirming this to work.
Click to expand...
Click to collapse
You don't need the eng hboot to get permroot... You just need to temproot with write-protection disabled. But as you say, it's best to wait until the right tools come out.

stridger said:
You don't need the eng hboot to get permroot... You just need to temproot with write-protection disabled. But as you say, it's best to wait until the right tools come out.
Click to expand...
Click to collapse
Exactly, that's what the logic sugests.
I was hoping to:
Temp root with Visionary (already done)
Disable write protection via wpthis-Z.ko
then try "sync" command to write changes.
Then, after reboot, I should have perm root and nand on read-only.
But I got scared by the errors I got after I disabled write protection.

g1junky said:
I flashed the desire z rom on my g2 yesterday after root, is my g2 now considered a desire z? if so it should be okay for me to follow these instructions right?
Click to expand...
Click to collapse
amazing,
thanks for reporting,
good news

g1junky said:
I flashed the desire z rom on my g2 yesterday after root, is my g2 now considered a desire z? if so it should be okay for me to follow these instructions right?
Click to expand...
Click to collapse
You've probably still got a G2 hboot, right ? Like the G2 eng hboot ? If so, then it's still really a G2 running a Desire Z ROM. But I can't answer your main question, I'm sure someone else will be able to though.

g1junky said:
I flashed the desire z rom on my g2 yesterday after root, is my g2 now considered a desire z? if so it should be okay for me to follow these instructions right?
Click to expand...
Click to collapse
No, your phone still has the G2 partition layout, so none of this is probably needed for you as your bootloader should already show S-OFF...

I have a g2 so most of this doesnt pertain to me, but as im trying to help someone currently stuck in a hard place thought maybe u could help.
My question has to do with after clockwork is installed. Why do u have to run wpthis.ko in recovery. Shouldnt wp be turned off in recovery? thats how the phone updates stock.

fastludeh22 said:
I have a g2 so most of this doesnt pertain to me, but as im trying to help someone currently stuck in a hard place thought maybe u could help.
My question has to do with after clockwork is installed. Why do u have to run wpthis.ko in recovery. Shouldnt wp be turned off in recovery? thats how the phone updates stock.
Click to expand...
Click to collapse
I just tested doing a nand restore without using wpthis-Z.ko and it *seems* to be working. I haven't flashed anything yet so i can't be sure but it seems like it worked

Sphaerophoria said:
I just tested doing a nand restore without using wpthis-Z.ko and it *seems* to be working. I haven't flashed anything yet so i can't be sure but it seems like it worked
Click to expand...
Click to collapse
Well, for me it was able to flash system, but not boot. My guess would be hboot wouldn't work either. [Obviously it won't return an error... It will think it had written, when in fact it hadn't.]
As for the post before that, the fact that stock recovery can flash images says nothing about other recoveries being able to do the same. Stock recovery could disable wp for example.
In any case it would be nice to have permanent write-access...

stridger said:
Well, for me it was able to flash system, but not boot. My guess would be hboot wouldn't work either. [Obviously it won't return an error... It will think it had written, when in fact it hadn't.]
As for the post before that, the fact that stock recovery can flash images says nothing about other recoveries being able to do the same. Stock recovery could disable wp for example.
In any case it would be nice to have permanent write-access...
Click to expand...
Click to collapse
Dont take this as arguement, cause as ive said i dont have a z, just going by what ive thought to be right. With that being said, the fact that wp is off in stock recovery does say something. The bootloader is what sets wp on/off so if the bootloader is loading the recovery(which it thinks is stock) wp SHOULD be off. i guess a good way to test would be after a nandroid, flash a zip thats only a boot.img and see if it takes.
Heres another question then, what about using the g2 eng recovery?

stridger said:
No, your phone still has the G2 partition layout, so none of this is probably needed for you as your bootloader should already show S-OFF...
Click to expand...
Click to collapse
i tried the G2 method for obtaining clockwork and it didn't work it says it flashed from the app but when i try to backup rom im still on the stock recovery.. would u recommend i try the D-Z method?

fastludeh22 said:
Dont take this as arguement, cause as ive said i dont have a z, just going by what ive thought to be right. With that being said, the fact that wp is off in stock recovery does say something. The bootloader is what sets wp on/off so if the bootloader is loading the recovery(which it thinks is stock) wp SHOULD be off. i guess a good way to test would be after a nandroid, flash a zip thats only a boot.img and see if it takes.
Heres another question then, what about using the g2 eng recovery?
Click to expand...
Click to collapse
wp is definately off in recovery but the problem is probably "your update-binary or updater-script (don't use update-script)" in koush's own words. Anyways i hope we find a way around this soon

FYI: Method updated to reflect the fact that we now have an ENG hboot.

stridger said:
Follow G2 guide on http://forum.xda-developers.com/showthread.php?t=833965, but instead of wpthis-*.ko use the file http://content.modaco.net/dropzone/wpthis-Z.ko. ALSO DO NOT FLASH THE hboot-eng.img INSTEAD USE THE FILE ON http://www.multiupload.com/4U9P14R86Y. IF YOU FLASH THE WRONG FILE IT COULD POTENTIALLY BRICK YOUR DEVICE! .
Click to expand...
Click to collapse
Good work.
Just a suggestion, but I think it would be a lot clearer if, instead of two lots of "follow this except don't do this bit", you were to copy out the whole procedure and change those two bits appropriately ?
Just trying to help minimise the chances of bricks.

steviewevie said:
Good work.
Just a suggestion, but I think it would be a lot clearer if, instead of two lots of "follow this except don't do this bit", you were to copy out the whole procedure and change those two bits appropriately ?
Just trying to help minimise the chances of bricks.
Click to expand...
Click to collapse
Yes, I agree and would like to do that, but wanted to ask unforgiven512 first to integrate it into his guide, as it seems to much overhead to maintain two guides of essentially the same procedure...
Now both devices have a fully working eng bootloader, we really need to merge these two forums into an "HTC VISION" one!

[Q] Visionary broke my Tmobile G2 phone - PLEASE HELP !!

I installed Visionary and everything was working perfect... But I made the stupid mistake to press Permroot and my G2 shut down and never bootup to Andrid OS..
I only see the HTC green logo .. I tried everything on recovery mode.. but I only get the HTC logo and the phone dont go anywere..
I tried to install the original G2 stock ROM but then the update fail saying Im trying to flash a older update. The room in the phone is newer than the update Im trying to install..,
Someone knows were I can find a Custom room that works in my Tmobile G2 USA...?
I need to install the room in recovery mode...ONLY .. because my phone do not boot-up.... So the ADB is disabled and the phone do not work... I only have access to recovery mode...
PLUS the phone is NOT rooted...
And Please dont tell me to do factory Reset.. because I did all that..If Im here is because I have tried everything and I dont get this phone to work.
Is there a room or a custom room somewhere that can be installed in my G2 by Recovery mode..?
If there is ,, can someone give me the link...?
My HBOOT screens says the following
VISION PVT SHIP S-ON
HBOOT- 0.82.0000
MICROP-0425
RADIO-26.03.02.26_M
eMMc-boot
Sep 2 2010, 17:59:38

boyfrom75 said:
I installed Visionary and everything was working perfect... But I made the stupid mistake to press Permroot and my G2 shut down and never bootup to Andrid OS..
I only see the HTC green logo .. I tried everything on recovery mode.. but I only get the HTC logo and the phone dont go anywere..
I tried to install the original G2 stock ROM but then the update fail saying Im trying to flash a older update. The room in the phone is newer than the update Im trying to install..,
Someone knows were I can find a Custom room that works in my Tmobile G2 USA...?
I need to install the room in recovery mode...ONLY .. because my phone do not boot-up.... So the ADB is disabled and the phone do not work... I only have access to recovery mode...
PLUS the phone is NOT rooted...
And Please dont tell me to do factory Reset.. because I did all that..If Im here is because I have tried everything and I dont get this phone to work.
Is there a room or a custom room somewhere that can be installed in my G2 by Recovery mode..?
If there is ,, can someone give me the link...?
My HBOOT screens says the following
VISION PVT SHIP S-ON
HBOOT- 0.82.0000
MICROP-0425
RADIO-26.03.02.26_M
eMMc-boot
Sep 2 2010, 17:59:38
Click to expand...
Click to collapse
Try the following link:
http://forum.xda-developers.com/showthread.php?t=842495

I already did try the link. But I dont understand what option to take..
The one of the options I think will work needs to have the phone ADB running ..
But my ADB is disabled because I can't get to the Android OS and the phone is not rooted..
I was reading that you can connect the phone to the Computer to fix it..
How do I do that ? What program do I need to run it ? But I dont like that option,,,, is to complicated..
Is there a way to fix the phone using the SD card on Recovery mode ?

boyfrom75 said:
I already did try the link. But I dont understand what option to take..
The one of the options I think will work needs to have the phone ADB running ..
But my ADB is disabled because I can't get to the Android OS and the phone is not rooted..
I was reading that you can connect the phone to the Computer to fix it..
How do I do that ? What program do I need to run it ? But I dont like that option,,,, is to complicated..
Is there a way to fix the phone using the SD card on Recovery mode ?
Click to expand...
Click to collapse
1) Just to clarify: VISIONary is a complete fail. Root using the rage method, then you can actually control what's happening to your device.
2) Did you ever flash clockwordmod recovery?
If you can boot into clockwork recovery you just need to flash another ROM.

Try posting this in the Q n A section. I know, posting a question in the QnA forum probably sounded like a CRAZY idea, but guess what, that is where this belongs.

tehseano said:
Try posting this in the Q n A section. I know, posting a question in the QnA forum probably sounded like a CRAZY idea, but guess what, that is where this belongs.
Click to expand...
Click to collapse
this guy is obviously new cut him some slack.....
just follow the instruction on the link carefully
idk why people are having trouble with VISONary i used it to root my phone n it worked....
im new on the forums but i know a thing or two about rooting

That's why I'm using Rom manager.. because its easier for my self.. as soon as you flash clock work recovery.. I believe that you can't go wrong.. I also did something similar and my phone also staid at the HTC screen.. but went back into recovery mode and clicked on restore and went in on my old Rom
sent from g2 using DHD Rom

boyfrom75 said:
I already did try the link. But I dont understand what option to take..
The one of the options I think will work needs to have the phone ADB running ..
But my ADB is disabled because I can't get to the Android OS and the phone is not rooted..
I was reading that you can connect the phone to the Computer to fix it..
How do I do that ? What program do I need to run it ? But I dont like that option,,,, is to complicated..
Is there a way to fix the phone using the SD card on Recovery mode ?
Click to expand...
Click to collapse
Ok, this is a snip from the link in the second post, it sounds like your are stuck in a boot loop with s-on, if so then this part is the part you need to try:
"*if you have stock or eng-recovery installed.
will the phone attempt to boot android at all? where is it stuck at?
a good min after it starts to try to boot, type these commands:
adb remount
adb shell
if you can get in shell then theres still hope. back out shell for a second and start here:
put the cwm recovery.img and wpthis.ko in your sdk folder
adb remount
adb push wpthis.ko /data/local/wpthis.ko (specific for your kernel)
adb push recovery.img /data/local/recovery.img
adb shell
# insmod /data/local/wpthis.ko (should get same function not implemented error as when u rooted first time)
# dd if=/data/local/recovery.img of=/dev/block/mmcblk0p21 (now wait a min or 2 to give it time to finish)
#sync (give it another min or to just to be safe)
#reboot recovery
at this point you should be in cwm recovery. follow instructions above for flashing with s-on."
So now you are gonna have to install Andriod SDK to your computer and the drivers for the G2, there is gonna be a lot of reading and some downloading on your part to do this. Next your gonna have to download cwm recovery.img and wpthis.ko in your sdk folder and then follow the instructions above to recover your phone. Unfortunatly there is no one click fix. Its gonna take a lot of reading and understanding to do this on your part. Gonna have to learn to use ADB there a guide for that and run some basic command promts. Im no Dev or anything but I taught myself by doing a lot of reading, watching videos and a lot of searching. Hope you find the will to do it and recover you phone. Plus we are here to help walk you through some of it but your also gonna have to do some leg work to. GOOD LUCK.

I don't think the OP knows what adb is... you gotta do some more reading get over your fear of using your computer to fix your phone. Its really nothing to be afraid of and its not at all complicated.
Sent from my HTC Vision using XDA App

I'm gonna assume he knows what ADB is and if that's the case, your only option is using one of the full updates...from tmobile. It would have to be a new version of course, for your recovery to allow it. Trying reading through thr RUU threads, perhaps something or someone there can help.
Goodluck, and sry.
Sent from my HTC Vision using XDA App

android602 said:
That's why I'm using Rom manager.. because its easier for my self.. as soon as you flash clock work recovery.. I believe that you can't go wrong.. I also did something similar and my phone also staid at the HTC screen.. but went back into recovery mode and clicked on restore and went in on my old Rom
sent from g2 using DHD Rom
Click to expand...
Click to collapse
Brah its not even rooted yet
Sent from my T-Mobile G2 using XDA App

Not only does he not know what adb is... he didn't even have usb debugging enabled... Not sure that affect's whether or not he can use adb in the recovery or not... but just saying

omarsalmin said:
Not only does he not know what adb is... he didn't even have usb debugging enabled... Not sure that affect's whether or not he can use adb in the recovery or not... but just saying
Click to expand...
Click to collapse
USB debugging does need to be enabled. I know this because I always forget that step when I'm trying to use ADB on a new Android device.
If OP wants a working phone again, he'd better take his pretty-looking paperweight back to get it replaced (just drop it in your toilet first).

blackknightavalon said:
USB debugging does need to be enabled. I know this because I always forget that step when I'm trying to use ADB on a new Android device.
If OP wants a working phone again, he'd better take his pretty-looking paperweight back to get it replaced (just drop it in your toilet first).
Click to expand...
Click to collapse
WATER DAMAGE! Haha I don't think warranty covers that
I just read somewhere that in order for VISIONary to perm root you need to have S-OFF. OP made a boo boo by attempting to perm root with S-OFF.

omarsalmin said:
WATER DAMAGE! Haha I don't think warranty covers that
I just read somewhere that in order for VISIONary to perm root you need to have S-OFF. OP made a boo boo by attempting to perm root with S-OFF.
Click to expand...
Click to collapse
actually all the older guides (including the one I used to root my phone) said you ran perma root first then do s-off.
the perma root method in visionary was made before we even had s-off (only like a day before, but still before).
It sounds to me like your having the same problem that some people have been having with the rage method, only because you have s-on still your stuffed.
Basically for some reason newer phones seem to be getting a corrupt rom when perma rooting by any method. If you had s-off you could manually flash a recovery then a new rom.

Lennyuk said:
It sounds to me like your having the same problem that some people have been having with the rage method, only because you have s-on still your stuffed.
Basically for some reason newer phones seem to be getting a corrupt rom when perma rooting by any method. If you had s-off you could manually flash a recovery then a new rom.
Click to expand...
Click to collapse
The OP here used Visionary, not rage. Not sure which problem with rage you're referring to, because I've never seen anyone stuck in a boot loop just because they did rage.
His phone also seems to have been messed with before he got it, e.g. it's a G2 but running the DZ radio (which is fine, but implies someone has been doing things to it).

steviewevie said:
The OP here used Visionary, not rage. Not sure which problem with rage you're referring to, because I've never seen anyone stuck in a boot loop just because they did rage.
His phone also seems to have been messed with before he got it, e.g. it's a G2 but running the DZ radio (which is fine, but implies someone has been doing things to it).
Click to expand...
Click to collapse
2 people last week on the same day got partial bricks by using rage, I had to talk both of them through flashing a recovery manually in order to install a non corrupt rom.
I have a feeling the perma root process is corrupting roms on newer devices, not sure on the why though.

Lennyuk said:
2 people last week on the same day got partial bricks by using rage, I had to talk both of them through flashing a recovery manually in order to install a non corrupt rom.
Click to expand...
Click to collapse
You said this the other day, but I asked you for links and I don't think you replied (but maybe I missed that).
Are you sure they didn't use Visionary first ? That's usually what corrupts the ROM. Because rage is very very simple, it's not like Visionary which does complicated stuff. I really don't see how rage on its own can corrupt a ROM.
If you have any links to threads where people have not used Visionary, only rage, and have corrupted the ROM, then I'd be very interested.

steviewevie said:
You said this the other day, but I asked you for links and I don't think you replied (but maybe I missed that).
Are you sure they didn't use Visionary first ? That's usually what corrupts the ROM. Because rage is very very simple, it's not like Visionary which does complicated stuff. I really don't see how rage on its own can corrupt a ROM.
If you have any links to threads where people have not used Visionary, only rage, and have corrupted the ROM, then I'd be very interested.
Click to expand...
Click to collapse
Come on man, I shouldn't have to prove myself...
but here you go
http://forum.xda-developers.com/showthread.php?t=871288
and
http://forum.xda-developers.com/showthread.php?t=871552
both using RAGE and not VISIONARY.

Lennyuk said:
Come on man, I shouldn't have to prove myself...
but here you go
http://forum.xda-developers.com/showthread.php?t=871288
and
http://forum.xda-developers.com/showthread.php?t=871552
both using RAGE and not VISIONARY.
Click to expand...
Click to collapse
Sorry you took it that I was asking you to prove yourself. I wasn't, I was just asking for information, because I'm interested in the subject.
I'd seen those threads but do you know for certain they didn't try Visionary first, find it didn't work properly, then try rage ?
I could of course be wrong, but I don't see how rage can cause corruption because it doesn't do a lot, it just fires up a bunch of processes to exploit a way to get root. It's so much simpler than Visionary, which does a whole load of RAM disk stuff and other things that could be more risky if it goes wrong.
I suspect in those two cases that something else had already messed with their phones to cause the boot problem.

[Q] Semi-bricked Desire.

Greetings all.
I just recently semi-bricked my Desire, I was uing 'Oxygen 2 RC2' and tried to partition my sdcard through 'AmonRA Recovery' and something went wrong and I ended up with a semi-bricked phone. I couldn't establish any connection with my SIM or SD-card.
I was tipped to install a original RUU which after a few tries worked and I recived a phone with the latest official Sense rom, HBOOT-0.93.0001 and S-ON of course.
After 'fastboot oem enableqxdm 0' is fastboot mode I atleast had connection with my SIM and SD-card and now a I have a semiworking but not rooted phone.
Now I want to root my phone and take back my USB-connectitvity but after reading this I understand that I need root for the USB-brick fix, to work but how do a get root with 'HBOOT-0.93'? Paul O'Brians root method only works for 'HBOOT 0.80' and lower and 'UnrEVOked' only works when having USB connection.
So how do I go about getting root and fixing my USB-Brick on my phone?
Thanks /ZeD

I have found a couple of "downgrade" tools but they haven't helped me much since everyone workd from within a fully booted system with a working USB-link which I have not.
Can a downgrade be done with a simple but old RUU file?

An old RUU file will not work.. I have the same problem, and got the same guide on how to fix it. But I sent it in for repair just hourse before, so I didnt have the chance to try it out. I unrooted my Desire as well with no luck. But as I read the guide, a rootet phone is not necessary?

For me it was, I had a another kind of fault at first my USB-brick happend when installing the ariginal RUU. What I should have done was to install a old RUU with 'HBOOT 0.80', root that and do the USB-brick fix, but I didn't know that I would get one ^^.

Blubba10 said:
a rootet phone is not necessary?
Click to expand...
Click to collapse
From the first step in that guide .
1. Follow this r5 rooting guide to do Step 1 of the rooting.
That will give you a basic ROM to work with, with root capability.
Click to expand...
Click to collapse

Well, I installed RUU with Hboot 0.80.. And then innstalled updates.... How noob is that?! Just asking..

Blubba10 said:
Well, I installed RUU with Hboot 0.80.. And then innstalled updates.... How noob is that?! Just asking..
Click to expand...
Click to collapse
I don't fully understand what you mean but when you have that kind of USB-brick that I have you need a rooted phone to fix it and the old way of rooting a Desire where you don't need it plugged to the computer can only root phones with 'HBOOT 0.80' or lower, the 'unrEVOked' way of rooting a Desire can be used on phones with newer bootloaders but need 'USB Debugging' which can't be used when a USB-brick is in play.
This is what you call a catch22 .
I have now seen a thread where a dude fixed a USB-brick on a non-rooted phone but the exploit that was needed is nowhere to be found. Well, well the hunt is on.

the easiest way to downgrade.
http://forum.xda-developers.com/showthread.php?t=768256

mariosraptor said:
the easiest way to downgrade.
Click to expand...
Click to collapse
This might come of as being rude but thats not my intention but I have several thread on diffrent forums out about my issue and most of the answers I recieve is from people that doesn't read my first post.
I cant use that downgrade tool since I don't have any contact with my phone through the usb cable.

if you use a card reader to put the PB99 file on the root of your sd card? boot into hboot it will recognize the PB file and prompt for doangrade.
no need to be rude as no intention were to make you feel offended.
if it is of no help no hard feelings,
cheer up and have nice holidays and a Happy New Year!!!
Freddan80 said:
This might come of as being rude but thats not my intention but I have several thread on diffrent forums out about my issue and most of the answers I recieve is from people that doesn't read my first post.
I cant use that downgrade tool since I don't have any contact with my phone through the usb cable.
Click to expand...
Click to collapse

I'm just a bit tired of working with this **** all weekend and answering in my ' cry for help threads' with I don't have root so I cant do that or I don't have a usb connection so I cant do that.
For the USB-brick fix to work I need root and for the downgrade to work I need a connection, it's just one way around my problem which seem to work but I only get 'permission denied' or 'that location is nonexistent'.
If anyone with more knowhow than me wants to take a look, the only thing that would actually fix my issue is here.

My meaning was to say that I think i have the same usb-brick as you (phone is now sent in for repair). It was rooted, but I unrooted it to hboot 0.80 and innstalled updates, wich resulted in hboot 0.93 in hope for it to fix itself. It didnt. As you say, you need root to fix brick. The only solution wich seems to work is this: http://forum.xda-developers.com/showthread.php?t=879068.. It seems to work for some people, not for me... And not for you as well, if i understand your latest reply correctly..

Yeah that's one of the fix I have tried.
It's kind of strange that that doesn't work, cause we should be able to write to that folder but for me it's like it isn't there at all. I checked my spelling and checked with 'androlib' that the working folder for 'Android Terminal Emulator' was in fact 'jackpal.androterm.

SUCCESS!!!!
I finally found a terminal that could give me enough "root" to use the exploit that gave me enough "root" to flash the fix. My phone is fully working now. Time to root the sucker again .

Freddan80 said:
SUCCESS!!!!
I finally found a terminal that could give me enough "root" to use the exploit that gave me enough "root" to flash the fix. My phone is fully working now. Time to root the sucker again .
Click to expand...
Click to collapse
Woooow man tell me how you did it imediately i have the 100% exact same problem as you did...tried update.zip, signature error, tried exploit with Terminal Emulator, no premissions...pleaaase tell me how you did it i am really desperate

godina said:
Woooow man tell me how you did it imediately i have the 100% exact same problem as you did...tried update.zip, signature error, tried exploit with Terminal Emulator, no premissions...pleaaase tell me how you did it i am really desperate
Click to expand...
Click to collapse
I used 'Better Terminal Emulator' never could get 'Android Terminal Emulator' to work.
I then used the commands given in the link I posted but instead of using 'data/data/jackpal.androidterm/*', I used '/data/data/*.
and then I did what the other thread said, made them executableand ran the exploit and then flashed my modified USB-brick fix.

Omg omg omg this could really be it i will try it asap, will post how it went...and does your bt, radio and usb all work?
Edit: where did you get this "Better Terminal Emulator" and how did you install it? I tried looking in market but didnt found tthis app

here it is http://forum.xda-developers.com/showthread.php?p=10058480#post10058480.
godina said:
Omg omg omg this could really be it i will try it asap, will post how it went...and does your bt, radio and usb all work?
Edit: where did you get this "Better Terminal Emulator" and how did you install it? I tried looking in market but didnt found tthis app
Click to expand...
Click to collapse

Ok I give up
Tried to download Better Terminal Emulator Magic, but it has been removed from market, looked for Pro version, cant download because there is no paid app support in Slovenia, so I can not download any paid app...
Is there any way for me to get this Better Terminal Emulator or will I just have to send the phone to repairs?

godina said:
Is there any way for me to get this Better Terminal Emulator or will I just have to send the phone to repairs?
Click to expand...
Click to collapse
You can obtain a copy here, but I'm not to sure about support.

[Q] risks vs advantages of S-OFF'ing

I've been pondering whether or not to S-OFF my desire for a little while now but I'm not really sure if I should do it or not. Specifically because I can't find the risks of doing it (maybe I'm not looking hard enough though) and the potential benefits of doing it(i've seen some cool stuff such as widget locker themes but not much else).
If somebody could give me a good idea of whether or not it is worth it it'd be much appreciated
Sent using tapatalk. Get over it

the pros are that you will have r/w access to phone instead of r/o. also you can change your boot partitions to have more free internal memory.
but if you do not know what you're doing you can potentially brick your phone.
if you do so always check md5sums of downloaded files to avoid corrupted files.
jacketyjoe said:
I've been pondering whether or not to S-OFF my desire for a little while now but I'm not really sure if I should do it or not. Specifically because I can't find the risks of doing it (maybe I'm not looking hard enough though) and the potential benefits of doing it(i've seen some cool stuff such as widget locker themes but not much else).
If somebody could give me a good idea of whether or not it is worth it it'd be much appreciated
Sent using tapatalk. Get over it
Click to expand...
Click to collapse

mariosraptor said:
the pros are that you will have r/w access to phone instead of r/o. also you can change your boot partitions to have more free internal memory.
but if you do not know what you're doing you can potentially brick your phone.
if you do so always check md5sums of downloaded files to avoid corrupted files.
Click to expand...
Click to collapse
More internal storage is nice but what can I do with read and write access?
Is files being corrupted the only risk? is there any other way I can brick my phone (as in if I follow guides to the letter and the md5 checksums are the same).
Sent using tapatalk. Get over it

jacketyjoe said:
More internal storage is nice but what can I do with read and write access?
Is files being corrupted the only risk? is there any other way I can brick my phone (as in if I follow guides to the letter and the md5 checksums are the same).
Sent using tapatalk. Get over it
Click to expand...
Click to collapse
You get more internal storage through the r/w access, you can change partition tables, you can edit your boot animations/splashes and geeky stuff like that. If you're just a casual user there's not really any point in doing it, however if you like messing around with the ins and outs of your phone (which im guessing you are since your researching it), its a pretty cool thing to have. The only risk I know of is if you download a corrupt img that you're going to push to you phone or if somehow the connection between your pc and your phone is lost while your pushing the files, can brick the phone. So in order to avoid this make sure the md5 checksum is ok for the image you downloaded (use a program like hashcalc to check this) and make sure your phone has plenty of battery + dont trip over your usb cable while your pushing files

Personally I think there is no reason to S-off as long as you can't find a reason yourself why you would want to S-off. If you need to ask why you want to S-off don't do it. If you have a reason you can go for it. If you follow the procedures and check md5 (which should be in the procedures) there is no realistic risk, but I know form one person that he had a BSOD while using AlphaRev and that bricked his phone. That is just bad luck and can't be prevented.
So yes there is always a risk that something goes wrong, but that is the same risk that you get hit by a truck when you go outside even too you watch out.
I take no responsibility for what happens even too you should be good.

Another thing... as far as security goes, keep in mind that when you s-off, any app you give su rights too, also has full unrestricted access to your device
Sent from my HTC Desire using Tapatalk

xp4nd3r said:
You get more internal storage through the r/w access, you can change partition tables, you can edit your boot animations/splashes and geeky stuff like that. If you're just a casual user there's not really any point in doing it, however if you like messing around with the ins and outs of your phone (which im guessing you are since your researching it), its a pretty cool thing to have. The only risk I know of is if you download a corrupt img that you're going to push to you phone or if somehow the connection between your pc and your phone is lost while your pushing the files, can brick the phone. So in order to avoid this make sure the md5 checksum is ok for the image you downloaded (use a program like hashcalc to check this) and make sure your phone has plenty of battery + dont trip over your usb cable while your pushing files
Click to expand...
Click to collapse
Awesome, I'm still considering it. I know all about checking MD5 sums so you don't mess up everything, been flashing BIOS's on my computer for years
TheGhost1233 said:
Personally I think there is no reason to S-off as long as you can't find a reason yourself why you would want to S-off. If you need to ask why you want to S-off don't do it. If you have a reason you can go for it. If you follow the procedures and check md5 (which should be in the procedures) there is no realistic risk, but I know form one person that he had a BSOD while using AlphaRev and that bricked his phone. That is just bad luck and can't be prevented.
So yes there is always a risk that something goes wrong, but that is the same risk that you get hit by a truck when you go outside even too you watch out.
I take no responsibility for what happens even too you should be good.
Click to expand...
Click to collapse
I can find a few reasons but I'm not really sure its worth the risk. From what you guys are telling me the only risks are that you download a corrupt file, you accidentally pull out your phone or a freak of nature. From what I've been reading I'd be fine to RMA it if something went wrong though wouldn't I? If it was completely dead (i.e. brick) they wouldn't be able to tell what caused it would they?
AndroHero said:
Another thing... as far as security goes, keep in mind that when you s-off, any app you give su rights too, also has full unrestricted access to your device
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
Which is a good thing to have

jacketyjoe said:
Which is a good thing to have
Click to expand...
Click to collapse
not if the application is malicious with full access they can do things like make calls without showing the dialer and send sms's without permission .....

AndroHero said:
not if the application is malicious with full access they can do things like make calls without showing the dialer and send sms's without permission .....
Click to expand...
Click to collapse
Of course, if you avoid said malicious applications everything should be good
Sent using tapatalk. Get over it

Does flashing a new radio, kernel, recovery need s-off? How about partitioning my sd card with Amonra, do i need s-off? I confused with the s-off description and just want to be sure.

Ghettonine said:
Does flashing a new radio, kernel, recovery need s-off? How about partitioning my sd card with Amonra, do i need s-off? I confused with the s-off description and just want to be sure.
Click to expand...
Click to collapse
Nothing of the above actions require s-off.
Sent from my HTC Desire using Tapatalk

Ghettonine said:
Does flashing a new radio, kernel, recovery need s-off? How about partitioning my sd card with Amonra, do i need s-off? I confused with the s-off description and just want to be sure.
Click to expand...
Click to collapse
All s-off does is give you write access to security locked areas of the nand chip while the device is booted ......
Sent from my HTC Desire using Tapatalk

So you are able to use a Custom ROM without having S-Off? because i just rooted my Desire, and i didnt flash any custom ROM, but i do have S-ON, i thought that you would have S-off when you've rooted it?
Btw i rooted it with Unrevoked 3.22

mathiasb2 said:
So you are able to use a Custom ROM without having S-Off? because i just rooted my Desire, and i didnt flash any custom ROM, but i do have S-ON, i thought that you would have S-off when you've rooted it?
Btw i rooted it with Unrevoked 3.22
Click to expand...
Click to collapse
you can still flash a custom rom just with an unrevoked root. To s-off your device you need to follow another process for instance the one here.

xp4nd3r said:
you can still flash a custom rom just with an unrevoked root. To s-off your device you need to follow another process for instance the one here.
Click to expand...
Click to collapse
Thanks! Then I don't have to read up on that s-off, as I just want to be able to save to sdcard
Offtopic: do I need to download a special radio if I want to install the newest Leedroid? I'm on a 2.2 FroYo, with a 32.43.00.32.U_5.09.00.20 RADIO (atleast I guess that my radio it says in my baseband in software info)
- Mathias
Sent from my HTC Desire using XDA App

It would be good to update to the latest radio, leedroids mini-site has download links and md5 checksums for the radios (make sure you check the md5 checksums, if it is different it can potentially brick your phone).
Sent using tapatalk. Get over it

Well, finally S-OFF'ed my phone, it was rather painless. The problem is that I can't flash the oxygen hboot because I can't get the Android sdk working
Sent using tapatalk. Get over it