edit the ruu - Droid Eris Android Development

Is it possible to edit the mr2 ruu or make one that will put on the root 2.1 over the leak 2.1?

No, since S-ON would be still active in hboot/ruu mode

Related

Stock Hero Problem

The problem that I am having right now is actually getting my Hero back to stock only. I recently searched the forums and found a few guides here and there to get back to Android 1.5, but the problem is that I follow those and then I try to downgrade and I get told only that I have a bootloader issue.
Now the only thing I could think of or know right now is that the bootloader is wrong. Which is keeping me from going back to original stock for the Hero.
Is there a possible way for me to fix this? I have tried many things, but not sure if any of you around here have some suggestions. One thing I wanted to ask and see if some one would have is whether you would be willing to upload your original backup for you phone.
If you were, then I assume that would possibly fix the bootloader issue.
Keep in mind I am no phone expert and I am just trying to throw out suggestions.
I hope that I can get some help!
Everything except Hboot back to stock using the method in this post >> http://forum.xda-developers.com/showthread.php?t=657086
Is there a way for me to get the HBoot back to the original and not to what it is right now?
V4ND3RP00L said:
Is there a way for me to get the HBoot back to the original and not to what it is right now?
Click to expand...
Click to collapse
Depends, if you never ran the 2.1 ruu then your hboot is still stock. Also, running the 1.56 ruu will flash the stock hboot (only an option if you have the older hboot already though).
If you have run the 2.1 ruu.exe then your hboot has been updated and you will be unable to run the 1.56 ruu. No fix yet, but maybe after the official 2.1 ruu is released.
Hold vol down on initial power on to get into fastboot. If you see Hboot 1.41.0000 then you have the original. 1.47.0000 is the 2.1 test rom hboot.
I flashed the leak when it was released and that caused the HBoot to upgrade. I will just wait until the official upgrade is out and for now I will be using a custom ROM.
Use damage control 2.07.2 stock if you want the closest thing to the sprint 2.1.

[Q] Problem with RUU_Buzz_Froyo_HTCCN_CHS

I've flash with a froyo rom , and now, I just want to get back to eclair or a baked froyo, that rom is full of problem : not a real android market(htc market) chinese apps, and the worst : I can't use the web browser but I can get my emails.
So if someone got an idea to root that rom or to roll back to a previous version , I'm open to your propositions.
I've already try with unrevoked/an other RUU rom (with and without a goldcard).
I used the froyo rom from shipped-roms
You need to do a full wipe from recovery before flashing the new rom.
thanks for the idea ;
I've tried, but the recovery mod doesnt load properly.
unrevoked shows that somes files aren't found while it's pass from HBOOT to HBOOT USB PLUG , and i'm not able to select recovery with the volume button in the HBOOT menu.
I think you have to wait for alpha rev :/
Same thing happened to me. Now my phone is not syncing Google or facebook contacts. The rom is very much limited. What i foundout was, the ruu update. Has also upgraded the hoot to version .83 from .80. That is the reason other ruus and unrevoke crash. Downgrading the hboot will do the trick. There are methods avaiable for desire but im not. sure they will work with. Wildfire. If the hoot is same for desire and wildfire rename the zip file. As PC49IMG.zip should downgrade the hoot. Any help is apnpreciated.
alparev will not help cos u need root for it, least on website is info Requirements:
The only requirement right now is that the ROM you're running is rooted.
adrienlm said:
unrevoked shows that somes files aren't found while it's pass from HBOOT to HBOOT USB PLUG , and i'm not able to select recovery with the volume button in the HBOOT menu.
Click to expand...
Click to collapse
yes, becos adbd is in other place, not in system.img as usual but in boot.img and adbd is different from every other adbd

Urevoked S-Off + 3.70 RUU = S-Off still but no more ENG HBOOT

Just FYI.
I had Unrevoked forever (S-Off), and decided to experiment and apply the RUU (exe) to upgrade to 3.70 SW and S-Off remained as expected and I am able to flash custom recoveries, Radios and ROMs... pretty much anything but HBOOT ( nand is still unlocked too). When I try any HBOOT even from previous Officiall RUUs it says "Bypass" and then flashes an error briefly stating "cannot downgrade HBoot".
I'm sure a few others have encounter just wanted to start a thread in case some one knows a workaround or fix.
I repeat ONLY ability to downgrade HBOOT is lost nothing else... kinda wierd if you ask me... but what do I know?
Ok cool...
Sent from my supersonic.
this is a new security thing with hboots 2.02 and 2.10. you need to flash a patch and then the eng hboot. there is a patch floating around for 2.02 but i dont think there is one for 2.10 yet...
Why do you need the eng hboot anymore anyways? CM was the only rom that ever required it and that has long been fixed.
for ext. hboot commands. like flashing splash screens manually and stuff.

[Q] How to dump HBOOT?

Hi all,
I've an HTC Wildfire with a branded ROM by Fastweb (ITA).
I didn't update to Froyo, so my phone can still be rooted.
Before rooting I want to be sure to be able to come back to stock ROM and hboot.
For my phone no RUU is avalaible, the only software package is the OTA update to Froyo (I haven't downloaded it for now).
As no RUU exists, I know that there's no easy way to restore my phone for warranty; isn't it?
What I'm asking is; if I get a temporary root (so no unrevoked) can I dump some phone address to get an hboot backup?
Using dd I should be able to dump, and if S-OFF also to restore the hboot, right?
I can't find information on this issue, everybody tells to use unrevoked!
May you help me?
[edit] fixed thread title, sorry!
I'm guessing you need NAND unlock (S-OFF), as if you could read/write HBOOT with temp root, people wouldn't be stuck un-rootable on Froyo
Yeah, you're right; I will never be able to write it until I'm S-OFF...but I still shall be able to read it, isn't it?
If i have a dump, I can put the phone in S-OFF with XTC clip and restore it.
But I still don't have any idea about on which /dev/ the hboot is stored
You cannot see the partition under /dev its hidden by hboot.
you need i think the diag file, i have that but thats also a nogo to downgrade or s-off, it says at-cmd timeout [email protected]=7,0 ok but phone reboots and not s-off.
ah, ok...so it seems it's not possible to backup the hboot?
they have been very clever this time...
thanks for your support.

[Q] Need to unroot froyo 2.2

I have looked and looked but probably not in the right places... I have a rooted Evo 4G with froyo 2.2. I used unrevoked forever and know how to get the s-on back... I just would like to update the phone to the newest update and root it again. Is it still necessary to get s-on back then load the original ruu rom? I would think I just need to remove the unrevoked then update. The phone works I just want newer firmware on it... My apologies if I did not look for my response properly, but all I see is a reload the IMG file... I dont want to set back to factory... just wanted to post this question. Thank You
Mee2 said:
I have looked and looked but probably not in the right places... I have a rooted Evo 4G with froyo 2.2. I used unrevoked forever and know how to get the s-on back... I just would like to update the phone to the newest update and root it again. Is it still necessary to get s-on back then load the original ruu rom? I would think I just need to remove the unrevoked then update. The phone works I just want newer firmware on it... My apologies if I did not look for my response properly, but all I see is a reload the IMG file... I dont want to set back to factory... just wanted to post this question. Thank You
Click to expand...
Click to collapse
There is absolutely no reason to unroot. All you have to do is flash a custom stock ROM based on the newest firmware. A whole bunch are available for flashing in the Development forum.
It is much easier to leave the phone S-OFF and then either flash a rooted stock ROM or run a stock RUU. Then all you would need to do to obtain full root again (with stock ROM) would be to install a custom recovery and then flash a superuser.zip file, rather than turning the phone back S-ON and then going through a potentially complicated procedure just to reroot and possibly turn the phone back S-OFF.
Thank You guys sounds like a custom rom is the way to go... it would get rid of that IQAgent also... I'll look around for a nice looking rooted rom.

Categories

Resources