[Q] Strange thing happened Whilst Rooting Desire - Desire Q&A, Help & Troubleshooting

Hi, ive just tried s-off and rooting my HTC desire so that I can flash custom ROM's, this is my first time doing this ever and ive been studying it for weeks, I cant say I was calm about doing it, in fact I was bricking myself all the way through, however it seems to have gone well other than one slight thing.
After careful study I decided to go with a video and step-by-step insturctions on the unlockr site, including links to all the required files.
I have the Revo Stock hboot now and also have clockworkmod on my phone, I followed the root instructions to the letter as well as follow the video, however decided to use clockworkmod first to make a backup and restore image to my sdcard first incase anything went wrong, I then installed the superuser.zip file, it said this all went fine and installed successfully and enjoy, after a reboot of the phone, I have no superuser in the apps menu ?
Tried installing it again, once again it said successful and enjoy, but still no superuser in the apps menu ?
If I wanted to just root my phone again now, im not sure which way to do it as I now have a strange hboot version on my phone ?
Im also new to these forums and wasnt sure if this was the right place to post this, any help would be greatly appreciated.

hi, post all info from hboot/fastboot screen

-Revolutionary-
BRAVO PVT4 SHIP S-OFF
HBOOT-6.93.1002
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.14
Aug 10 2010, 17:52:10
HBOOT
(VOL UP ETC..............)

If is not working via recovery try to download it from market or push it manually(adv, qtadb)
Sent from my HTC Desire using XDA Premium App

Thanks, I had a look on market and was gonn ask if that was the same superuser, so although I dont have the app yet am I pretty much still routed ?
I was gonna run unrevoked 3 last night to try and root a different way but thought i'd wait for a reply on this thread first, should I try that or is there no need ?

Just tried downloading superuser onto my phone then thought I test it, so I downloaded titanium backup too, when I ran titanium it said unable to gain root access, this program will not work, any clues anyone ? My info is above, and suggests that I'm rooted.

After using Revolutionary you have to flash this superuser.zip from recovery to get root access (you didn't do this, did you?:
http://downloads.androidsu.com/superuser/Superuser-3.0.7-efgh-signed.zip
So uninstall superuser and Titamnium Backup, boot into recovery, flash the superuser.zip and then try again.

Yes I did do this, my first post clearly states I tried this twice, then rebooted the phone, went into the apps menu and no superuser, so I tried to manually download superuser from market.
Although it says its installed and completed successful / enjoy, its like the root part of the whole process isn't taking effect ?

You may not have enough free space on the /system partition and although the .zip reports a successfull installation, it may not install.

Seanie280672 said:
Yes I did do this, my first post clearly states I tried this twice, then rebooted the phone, went into the apps menu and no superuser, so I tried to manually download superuser from market.
Although it says its installed and completed successful / enjoy, its like the root part of the whole process isn't taking effect ?
Click to expand...
Click to collapse
Okay sorry missed that. I recommend to ask Revolutionary in their IRC channel.
Sent from Sandvold's ICS using Transparent XDA App

TVTV said:
You may not have enough free space on the /system partition and although the .zip reports a successfull installation, it may not install.
Click to expand...
Click to collapse
Ok, how would I free up space on this partition, I take it you mean the phone rather than the SDcard ? I have most of my apps moved to the SDcard now, well the apps I can move anyway, some dont allow it.
I installed quick system info from market, it would appear out of the 250mb supplied I only have 70kb left, god knows where all this space has gone, but now im in catch 22, it would appear the reason I cant root is beacuse I dont have enough system space, but I cant delete any system apps cos im not rooted, any idea's anyone ?
Tried a reset of the phone but it didnt change anything in the system folder or available space.

Well, in layman's terms, the Desire has three user-visible partitions, excluding the SD card. Those are:
1) Data (/data): this is the partition where all your apps, app data, contacts and settings reside. This is also where the Dalvik-cache lives;
2) Cache (/cache): this partition is, as the name states, a cache partition;
3) System (/system): this is where your ROM resides. This is the partition where the .zip you're installing from Recovery is trying to copy its contents to, namely "Superuser.apk" and "su". In order for this procedure to succeed, you must have at least 900 kB free on this partition (Superuser.apk + su = ~860 kB, if you're trying to install Superuser 3.0.7).
If you're saying that you've checked the free space on your /system partition with a tool and it reports that you only have 70 kB free, that might be your problem. You can free up some space on the /system partition by deleting some files (which are safe to delete, namely some ringtones, a couple of wallpapers), but i must know what ROM are you using, first. Can you please provide that info?
P.S. - The above-mentioned procedure requires you to use ADB shell, so if you're not familiar with that or you just don't wanna mess with stuff like that, you can always install a pre-rooted ROM of your choice.

Hi, thanks for the info, it was very helpful, the ROM details are below, to me its just the stock Froyo ROM, but ive since unlocked the phone, S-OFF'd it and installed CWM, the HBOOT has also changed.
Andriod version 2.2
BB version: 32.48.00.32U_5.11.05.14
Kernal version: 2.6.32.15-ge2c73db
[email protected]#1
Build number: 2.22.351.3 CL283825 release-keys
Software number 2.22.351.3
Browser version Webkit 3.1
Hope this helps
I was also thinking of installing a pre-rooted ROM to get past this, As this would be my first time doing this I wasnt too sure which one to go for, the one I fancied is called PyramidMod007_v11_b-STOCK, would this go straight on ? the radio required is pretty much the same as my existing radio.
As mentioned earlier, I have a strange HBOOT version on my phone now, those details are as follows:
-Revolutionary-
BRAVO PVT4 SHIP S-OFF
HBOOT-6.93.1002
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.14
Aug 10 2010, 17:52:10
HBOOT
(VOL UP ETC..............)

Nothing strange about your HBOOT. That's how it's supposed to "look" after using Revolutionary.
So you're running stock HTC FroYo. The way i see it, you shouldn't even bother rooting your current ROM, as FroYo is obsolete and you should move to Gingerbread. Browse through the development section, pick a ROM that you like and install it via Recovery (you don't need root for that). Mind you, you need to carefully read the requirements for each ROM. For example, some are made for the stock /system size (250 MB), some are made for the Data++ /system size (180 MB) etc. Also, some ROMs will not work without an EXT 3/4 partition on the SD card.

Thanks, I proceeded to try a couple of rom's out, tried the pyramid one first, but my phone was very very laggy with it, next I flashed the revolution rom, absolutly loving this rom, gonna stick with it for a bit I think, battery is much better on it, its nice as smooth, and boot times are amazing compared to the stock rom as well as now being rooted too.
I went for the apps2sd+ version of this rom, working fine on my current radio, I created a 1gb EXT3 partition on my SDcard prior to flashing using clockwork mod just incase, it said it required it.
Thanks for all your help guys, was so scared of bricking my phone through all of this, everything goes on about the risks all the time, but it was no where near as bad as that, guess they have to inform you though.

Well, the most dangerous procedures for your phone are when you're writing radios or HBOOTs. When you power up your phone, it first "boots" the Radio partition, then HBOOT and only afterwards it boots the kernel, OS etc. So if happen to frack up either one of these two partitions, Radio or HBOOT, you'll end up with a brick. Flashing ROMs or kernels, on the other hand, is perfectly safe.
Enjoy your "new" phone!

Have you tried unrevoked 3? It's work fine for me. I just ad to update superuser form the market after.

Related

[Q] problem flashing myns rls4

help with flashing myns 2.2
Hey guys I've been reading the threads for a while and finally decided to root my evo last night using unrevoked..I made a nandroid as well ad a ti backup. I download myns last night and I think I put it into the root if my SD card according to directions I found using astro. I keep on trying to flash the Rom from my recovery and it goes about 3/4 of the way then aborts and states E:can't symlink/system/bin/ then e: failures at line 15. Then finally symlink busybox system : xbin.. I have not partitioned my SD card yet since I have read places there is no need to.. if anyone could shed some light on this is really appreciate it..BTW I'm on stock froyo atm
Hey guys I've been reading the threads for a while and finally decided to root my evo last night using unrevoked..I made a nandroid as well ad a ti backup. I download myns last night on my phone and I think I put it into the root if my SD card according to directions I found using astro. I keep on trying to flash the Rom from my recovery and it goes about 3/4 of the way then aborts and states E:can't symlink/system/bin/ then e: failures at line 15. Then finally symlink busybox system : xbin.. I have not partitioned my SD card yet since I have read places there is no need to.. if anyone could shed some light on this is really appreciate it..BTW I'm on stock froyo atm
are you s-off, what recovery?
Could be a corrupt download so I would try to redownload the rom and then reinstall. But what hardware version and hboot do you have?
Yes s is on..and the recovery is clockwork..
Wrong section bud, don't post questions in here especially since you already posted in Q&A. But you need your S-OFF thats why your having problems.
definitely need s-off, but have you tried to DL it again?
yea i thought it might be on the wrong forum so i reposted it there after, i apologize. how do i get the s off. Im not very good at this.. im interested in alt his stuff but not very good yet..i thought when i rooted it would turn s off..and yea ive tried installing it several time with no luck and same error
in another thread someone told me that its not working bc im still s-on..how do i turn that off.. hardware version 0003
First, you need to verify whether s is on or off. To do this, power down your phone, and hold the volume down button while you power it back on. It will boot into a white screen with 3 Androids on skateboards at the bottom. The very first line at the top of the screen will indicate if s is off or on.
If you rooted with Unrevoked, s should be off. However, I believe that before you can flash custom roms, you need to unlock NAND by flashing the engineering SPL onto your phone. On the same screen where you see if s is on or off, it needs to say Hboot: 0.76.2000 on the second line. If it has any other version of the hboot, you will not be able to flash custom roms.
This is what I did 1 week ago when I rooted my girl's Evo (also a 0003):
1) Ran Unrevoked for root.
2) Installed ROM Manager to flash recoveries & TI for back-ups.
3) Put Myn's RLS 4 on root of SD, and tried to flash via recovery; got errors similar to yours.
4) Downloaded engineering spl and placed on root of SD
5) Went back into recovery and flashed the eng. spl (at this point, I tried to boot it and the phone had no rom and would loop at the white HTC EVO 4G screen).
6) Got the phone back in recovery by doing a battery pull, powering on while holding volume down, and selected recovery.
7) From the recovery, I flashed Myn's RLS 4, my favorite kernel, a custom boot screen, and then rebooted.
8) Opened a beer and relaxed.
Don't forget to wipe everything twice! Also, before you flash the eng. spl, make sure you go into ROM manager and use the option to "flash an alternate recovery" so you do everything with Amon recovery which does a better job wiping. However, with Amon you cannot navigate through all the folders on your SD card to find what you want to flash. All flashable files MUST be placed in a .zip format in the root of your SD card (meaning out in the open and NOT inside any folders)
I hate using ADB, and if you follow these steps precisely, you will not need it.
Good luck!
i will try what you say to do..im just nervous bc that sounds complicated with my limited computer skills..i just dont understand why s-on is still there..isnt that the point of rooting.. can i unroot and run unrevoked forever?..is there any difference ?
firmbiz94 said:
i will try what you say to do..im just nervous bc that sounds complicated with my limited computer skills..i just dont understand why s-on is still there..isnt that the point of rooting.. can i unroot and run unrevoked forever?..is there any difference ?
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App
Check your hboot version, and see what it is. If it is hboot 2.02, that is your problem. Unrevoked doesn't work (yet)with that hboot version. Currently, the only way to root that hboot version is the "boss" method. Can be found in the development section. You can check by doing the same thing the guy before mentioned, hold vol down, and power button together. Then you will see the version, at the bottom I think. When did you get your Evo? What hardware version are you? ( settings, about phone, hardware info) software info the same way, see if your build 3.29 or 3.30.
Edit: looks like the thread is now "like a pinecone" rather than "like a boss"
OP: Rooting does not turn s off. Root allows you to run programs that require root access. With root, you can run wireless tether, ROM Manager, Titanium back up, Shootme app for screen shots, etc.
However, to flash custom roms, you need to have NAND access and that is done by flashing the engineering hboot. You can find the engineering hboot here:
http://forum.xda-developers.com/attachment.php?attachmentid=342668&d=1276481802
Like k2buckley, if you have the 2.02 hboot, you need to follow this root guide:
http://forum.xda-developers.com/showthread.php?t=829045
It requires lots of ADB and this is for more advanced users. If you are going to try it, make sure your battery is completely charged before you start messing with it. I HIGHLY recommend you search YouTube for video tutorias on the root method you need to use and watch it from beginning to end (twice if you need to) to make sure this is something you feel you can do before you dive in.
Merged 2 threads.
I finaLly figured it out..I got frustrated and figured I'd flash unrevoked forever..I downloaded to SD card and flashed it..that turned nand off..then I flashed myns..and it worked..i couldn't believe it..thanks for your help guys..
I downloaded shootme to take a shot of my software to so you guys. But when I try to attach a file it doesn't do anything when I press search..anyways so far I really like the Rom and netarchy kernel..I think I'm gonna be addicted and flash often although I nandroid backed this one since I like it..any other suggestions for sense roms..I just want to have a blazing fast Evo..not sure if I wanna go aosp though..

hboot and s-off issue

I apologiz if this has been answered, or beat into hte ground, or what. I cant really find an answer, and not sure what to search for either.
I recently noticed that my hboot is "s-on". I still have root, and su and everything. ?I want to update hboot from .76.2000 to the latest, which is 2.16.00.
I see I can go to this revolutionary website and generate a key which allows me to get s-off, but it looks like thats for rooting a brand new ohone. mine is already rooted, just has S-ON.
can I flash hboot 2.16.00, then flash that revolutionary patch/s-off and be in good shape, or would that mess something up? I'm trying to flash the anthrax kernel, and I need something higher than .76
Interestingly I had a very similar issue yesterday. If you have some qxdm files on the root of your sdcard, and can't mount the sdcard, this may work for you. I had to execute a couple of commands in fastboot mode. I am assuming with these steps that you have a computer, win/lin/mac whatever with adb already configured, etc.
Power off phone
Remove sdcard
Power on holding vol down
Select Fastboot
Connect USB to computer
Open cmd prompt/terminal on computer
Execute
Code:
fastboot oem enableqxdm 0
Execute
Code:
fastboot oem eraseconfig
Power off phone
Insert sdcard
Rejoice!
I really hope this works for you, I wasted a couple of hours digging around google to find this.
Flash the unrevoked forever zip through recovery, not sure if it's compatible with your hboot or radio, but it's worth a shot.
You can always RUU to like 3.70 and run unrevoked. I'd prefer that over updating to the latest and running revolutionary since unrevoked doesn't use a different hboot and is easier to unroot, but you can do either if you don't find a different way.
Happy New Year!
Supersonic Evo 4G | MIUI | Tapatalk
jasongthang said:
I apologiz if this has been answered, or beat into hte ground, or what. I cant really find an answer, and not sure what to search for either.
I recently noticed that my hboot is "s-on". I still have root, and su and everything. ?I want to update hboot from .76.2000 to the latest, which is 2.16.00.
I see I can go to this revolutionary website and generate a key which allows me to get s-off, but it looks like thats for rooting a brand new ohone. mine is already rooted, just has S-ON.
can I flash hboot 2.16.00, then flash that revolutionary patch/s-off and be in good shape, or would that mess something up? I'm trying to flash the anthrax kernel, and I need something higher than .76
Click to expand...
Click to collapse
What recovery where you using? And what did you wipe before this happened? You seem to have hit the sake thing as me, but my recovery was gone, as well as my Rom.
Sent from my PC36100 using xda premium
I'm using Amon Ra
I was following this guide [Guide][31 Dec] Rooting and Sense Guide! to try and flash everything decently and how it should be. I flash the newest radios/nv/wimax the way it shows. I got to the kernel, he recommended Anthrax, so I downloaded it and flashed it. The phone wouldnt boot past the splash screen.
So I pull the battery, and pwr+vol down because I want to get into recovery. Well it boots normally into the white hboot screen, and I happen to look at the security, it says S-ON. Huh, thats weird, but everything is working normally (i think) so I just go into recovery, and flash ChopSuey's kernel. THAT doesnt let me boot past the splash screen.
So looking more at Anthrax thread, I notice that you need to have a higher hboot int order to flash the Anthrax kernel successfully, i have .76.2000. Someone has a link for a .93 hboot, so I download and flash it. I flash the Anthrax kernel from recovery, but now the phone wont boot, it just keeps going back to the white hboot screen. I have the phone working now by just re-flashing the rom (evo classic), but I want to get the S-ON situation fixed, I want to have the proper hboot that I need, and I would LIKE to get the Anthrax kernel working, although I could go to another one if its just not going to work.
Is there a good write-up on just what exactly the hboot is and what it does? I never read up on it because it never seemed to be something I needed.
Thanks for your replies.
plainjane said:
Flash the unrevoked forever zip through recovery, not sure if it's compatible with your hboot or radio, but it's worth a shot.
You can always RUU to like 3.70 and run unrevoked. I'd prefer that over updating to the latest and running revolutionary since unrevoked doesn't use a different hboot and is easier to unroot, but you can do either if you don't find a different way.
Happy New Year!
Supersonic Evo 4G | MIUI | Tapatalk
Click to expand...
Click to collapse
Are you pretty much saying to just completely flash back to stock un-rooted, and start all over again? That would be fine with me, would that straighten out any hboot problems as well, as far as putting the hboot back to the way it should be, or was?
It's not a bad idea. RUU back to stock, accept the updates, then root using whatever the most current version is.
Ok, messed around and updated with a back-to-stock pc36img, the hboot version was still .93... So now I've successfully rooted with unrevoked. s-off, super user, everything is fine, but i'm still at the .93 hboot.
What exactly is hboot, and can I update it to 2.16.0001? How do i know which hboot i should be on?
Also, I apologize again but its been a while. My phone is running clockwork recovery. Can I just flash the amon ra recovery zip through clockwork?
jasongthang said:
Ok, messed around and updated with a back-to-stock pc36img, the hboot version was still .93... So now I've successfully rooted with unrevoked. s-off, super user, everything is fine, but i'm still at the .93 hboot.
What exactly is hboot, and can I update it to 2.16.0001? How do i know which hboot i should be on?
Also, I apologize again but its been a while. My phone is running clockwork recovery. Can I just flash the amon ra recovery zip through clockwork?
Click to expand...
Click to collapse
No reason the upgrade your HBoot. Latest doesn't necessarily mean best. I wouldn't go any higher than 0.97, personally, since that's the last version that's downgradable.
You'll be fine with what you have.
Captain_Throwback said:
No reason the upgrade your HBoot. Latest doesn't necessarily mean best. I wouldn't go any higher than 0.97, personally, since that's the last version that's downgradable.
You'll be fine with what you have.
Click to expand...
Click to collapse
Captain, any idea why some of us seem to be having trouble restoring back, while others aren't?
I'm almost at my wits end here. The hours I've put into this makes me feel like I'm close, but the honest truth is that I've yet to so much as get my device to stop showing up as a Qualcomm Diag Mgr, when I first turn the phone on, & haven't even gotten root or S-Off yet.
I've got a HW0004 evo, which I'd previously rooted with unrevoked & 2 - 3 months ago had rooted with unrevoked forever. I was running Decks, with a 32 gb sd card, which I was constantly having to run parted on b/c my sd-ext was losing it's filesystem, and my last attempt to fix this without going back to a 16 gb card was to switch from amonRA to TWRP 2.0, then repartition with a ext4 partition this time. It had been running smoothly for a week, if not longer, so I decided that I could go ahead & flash firerat's mod again, this time with a more accurate (and smaller) system partition. When I rebooted I started having this issue.
I'm somehow back to S-ON, 2.10.0001, 2.15.00.11.19 radio, with no access to adb. When I tried to flash the RUU that you posted over on MikMIk, to go back to stock 3.70, i had a ton of problems getting it to actually complete (everything from stopping in the middle of it, to going to a black screen, as if it had stopped, then coming back on & looking like it was going to finish, to stopping when I got to the reboot screen, but I'm pretty sure that it did finally flash. The only problem is that it still won't recognize my phone when I run unrevoked3, and it won't stay on long enough to let me figure out why.
ncadden said:
Captain, any idea why some of us seem to be having trouble restoring back, while others aren't?
I'm almost at my wits end here. The hours I've put into this makes me feel like I'm close, but the honest truth is that I've yet to so much as get my device to stop showing up as a Qualcomm Diag Mgr, when I first turn the phone on, & haven't even gotten root or S-Off yet.
I've got a HW0004 evo, which I'd previously rooted with unrevoked & 2 - 3 months ago had rooted with unrevoked forever. I was running Decks, with a 32 gb sd card, which I was constantly having to run parted on b/c my sd-ext was losing it's filesystem, and my last attempt to fix this without going back to a 16 gb card was to switch from amonRA to TWRP 2.0, then repartition with a ext4 partition this time. It had been running smoothly for a week, if not longer, so I decided that I could go ahead & flash firerat's mod again, this time with a more accurate (and smaller) system partition. When I rebooted I started having this issue.
I'm somehow back to S-ON, 2.10.0001, 2.15.00.11.19 radio, with no access to adb. When I tried to flash the RUU that you posted over on MikMIk, to go back to stock 3.70, i had a ton of problems getting it to actually complete (everything from stopping in the middle of it, to going to a black screen, as if it had stopped, then coming back on & looking like it was going to finish, to stopping when I got to the reboot screen, but I'm pretty sure that it did finally flash. The only problem is that it still won't recognize my phone when I run unrevoked3, and it won't stay on long enough to let me figure out why.
Click to expand...
Click to collapse
Well I know quite a few people that used TWRP had similar issues (sd card issues aside). But it could be firerat's that was the last straw. Let's say that you have bad blocks on your system partition, but then you use the mod to reduce the size if the partition to a size that *should* be big enough to accomodate everything, but due to your bad blocks, actually isn't. That would likely lead to corruption of your system partition, and everything would go downhill from there. Personally, I've tried to reproduce most of these issues on my device with TWRP and haven't had any success. My phone always works fine. I think it just comes down to everyone's devices being different, and the bad blocks causing device corruption one way or another with the ones that fail.
jasongthang said:
I apologiz if this has been answered, or beat into hte ground, or what. I cant really find an answer, and not sure what to search for either.
I recently noticed that my hboot is "s-on". I still have root, and su and everything. ?I want to update hboot from .76.2000 to the latest, which is 2.16.00.
I see I can go to this revolutionary website and generate a key which allows me to get s-off, but it looks like thats for rooting a brand new ohone. mine is already rooted, just has S-ON.
can I flash hboot 2.16.00, then flash that revolutionary patch/s-off and be in good shape, or would that mess something up? I'm trying to flash the anthrax kernel, and I need something higher than .76
Click to expand...
Click to collapse
I know how to fix this had the same problem a few months back
1 : Download the stock RUU executable for your PC
2 : Make sure you have the htc sync drivers installed on your PC
3 : Enable USB debugging in your phone's settings menu
4 : Hook your phone up to PC and run the RUU (This will return it 100% to stock)
5 : You will know need to root again. (this is the only way I got through this problem)
6 : After you root s will be off (delete or rename any PC36IMG.zip after you have used them from your SD card)
Here is the RUU that got me out of the same problem they won't let me post links yet just google this....
RUU_SuperSonic_GB_Sprint_WWE_4.53.651.1_Radio_2.15.00.0808_NV_2.15_release_209995_signed
My phone is back to....somewhat normal now, i think lol.
I may just be having issues with the particular rom I'm on. But everything seems fine.
I have reverted back to hboot eng .76.2 because I wasnt able to fastboot with .93, and I wanted to flash a custom boot image. When I flashed the .76 hboot, I wasnt able to boot my phone, i could only bounce between recovery and hboot. What seemed to fix this is reflashing the rom. I only wiped dalvik and cache, nothing else. This allowed me to boot right up normally, and I have fastboot commands. But I'm back to square one in that I don't have that anthrax kernel running anymore. I'm thinking of jumping back on the MIUI train though.

[Q]I'm kinda confused on a bootloop problem

Hi guys,
I just got into flashing my phone a few weeks ago when my stock desire started giving me endless low memory notifications, so I was attracted by A2SD. Anyways I've read and read, then read some more and I've been able to answer all my own problems up to now.
I rooted, S-offed etc. I installed Pyramid with sense 3.0 as my first ROM but it felt laggy and frustrating to use. So after reading I decided to try CM7. It's super fast and stable but I was finding I just could not figure out how to install apps. It has no market app so I'd go to the market website and install then I just couldn't find the app anywere. Plus it would tell me I had apps installed I didn't, but did on the first rom. I just wiped everything when I installed CM7. I guess I was used to the user friendly sense but I was finding CM7 not as simple.
So as fast and stable as it is I wanted to play with some other ROMs so tonight I got MIUI. It installed nice but as soon as it loaded after about 5 seconds it would reboot. and again and again. I read about boot loops in the thread but couldn't find a definitive answer. I read the boot loop help thread and then tried formatting boot, system, cache, sd=ext and whatever else the instructions said. Wiped again, installed MIUI and same thing.
It's getting late and I need my phone for tomorrow so I thought I'd try Insertcoin. The problem doesn't seem to be just MIUI though because that ROM did the same bootloop. About 5 seconds after everything seems to load properly. Now I'm a little worried.
Tried the last known good ROM, CM7, and viola! Everything is good and stable again. I'm wondering about partition table I didn't flash a new HBOOT. Mostly because I'm not sure how to? I'm unsure about this step (from the alpharev site)
3) Flash HBOOT with your phone in fastboot mode (Back+POWER) -> 'fastboot flash hboot bravo_alphaspl.img' (change into the correct filename for the HBOOT you downloaded).
The part after the arrow is were I'm not sure.
The thing is MIUI says it will go on a stock HBOOT so I figured my bases were covered?
Sorry about the long thread and honestly I've read and I'm ready to ask the community for advice. I've solved several problems on my own and here I am! Hopefully got this in the right fora. Also hope I got all the relevant info in. Any advice or idea on why those two ROMs boot looped would be awesome I still want to try MIUI.
Cheers
Can you give more info, like how you partitioned your sd card. What info does the bootloader in the top left of the screen give you. Wright it all down here. Maybe then its easyer to help.
Sent from my HTC Desire using XDA App
Your phone setup NEEDS TO MATCH developer requirements for that rom... so read instruction and set your phone up
I can't help you with your boot problems,
but I can however help you understanding the
third point in the alpharev description, as I was
facing the same understanding problem 2 days ago.
The command 'fastboot flash hboot bravo_alphaspl.img' is used
via your cmd / konsole/ terminal on your pc.
So what you must do is,
- install android sdk
- connect your desire via usb, go into fastboot-mode
- navigate via cmd / konsole / terminal to the 'platform-tools' folder (there is
the fastboot script you need to trigger) within your android sdk folder
(- you can test if your device is found with the command "fastboot devices")
and..yeah. Enter the commands from the alpharev page in your terminal.
/*Just remembered, you need to install the desire usb drivers, when you
are using windows, or something like that. I'm not using windows, but I'm
sure it's easy to google if you need help on either the usb drivers OR
on how to install the android sdk under windows.*/
MarcelHofs said:
Can you give more info, like how you partitioned your sd card. What info does the bootloader in the top left of the screen give you. Wright it all down here. Maybe then its easyer to help.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
I used Gparted to partition the stock 8GB micro SD card that came with my Desire. I have a fat 32 partition followed by a 1000mb EXT4 partition. Bootloader info is:
-----AlphaRev-----
BRAVO PVT4 SHIP S-OFF
HBOOT- 0.93.0001
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.027
Aug 10 2010, 17:52:18
Hope this helps if you have any idea what the problem is. The only thing I haven't played with is the radio.
Malso thanks very much for the info I was really unsure how to proceed there! I'll flash the CM7 HBOOT. Cheers.
kotag82 Thats the problem I can't figure out why Pyramid and CM7 work and MIUI or Insertcoin don't I can't figure out where the difference is between CM7 and MIUI that would prevent one from working. I thought my phone was matched exactly for MIUI. an't figure out what changed that one would work and the other just reboots 5 seconds after loading. The flashing of both MIUI and Insertcoin seemed to go perfectly.
Wondering if a full SD format would help? I've read and re-read the MIUI thread it it really looks like I should be good to go?
Yeah never did get my MIUI working. Allways with the rebooting problem. Did get RunnyMede AIO going and I'm loving that. Except for the battery drain issue. It will be fine untill about 50% and then I'll use about a percent every few minutes even with the phone off and in my pocket!

Random Reboots Problem - please help

I simply have done all i can - and it seems that i cant do it right. Please consider to help me, because im noob.
Before i state my problem i should say that i have googled an crossed xda forum for 4 days and without any improvement.
Problem I have is that, my phone randomly reboots at no particular time or place - but here come the details:
First, for purpose of unlocking phone from SIM lock from carrier, it was S-OFFed and rooted by someone else (previous owner).
Rom was installed - Oxygen 2.3.2. and it worked for few months without bugs.
Then, one day it restarted and stuck in bootloops, but it came up for few seconds, or some time (but not for long), and then again restarted and so on. Eventually it held enough to do a factory reset which generally helped, but with one strange thing - clock couldnt sync and loosed about an hour for 5-6 hours (really strange).
Then i decided to try some other ROM hoping to resolve clock issue.
When I go into HBOOt it says:
--- AlphaRev ---
BRAVO PVT4 SHIP S-OFF
HBOOT-6.93.1002
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27
Aug 10 2010 17:52:10
Then i went here -> http://forum.xda-developers.com/show...p?t=1315961URL and done REALLY step by step whole procedure.
ROM was installed, along with -> http://forum.xda-developers.com/show....php?t=1408936
It worked flawllessly for about half an hour an then started rebooting on no particular action - sometimes went up for some time few secs to 10-20 mins an then reboot and sometimes it got stuck in endless loop (only pulling the battery helped).
Since it went wrong, i tried to RESTORE previosly made BACKUP of mentioned OXYGEN ROM, but sadly, same thing happened all the time.
I was devasteted, didnt know what to do so I decided to get back to STOCK ROM via RUU. (thought it would solve the problem)
I used RUU_Bravo_Froyo_HTC_WWE_2.29.405.14_Radio_32.49.00 .32U_5.11.05.27_release_224699_signed
Phone stayed S-OFF (obviosly for AlphaRev HBOOT) but have been preety stable comparing what was happening before, in terms: restarted few times for a day and allways rebooted back. Then i inserted other SIM card ant it began again with restarts as soon it went up and been up for 10-20 secs. After few reboots, it stabilised, but had different problem: couldnt add new account, and couldnt remove one I set up at the beginning (message said that i should do FACTORY reset if i want account removed). So I did factory reset - and NOTHING HAPPENED - evrything stayed exactly as it was - with account and everything.
Then i came across BORTAKs Guide ->http://forum.xda-developers.com/showthread.php?t=1275632 and followed step one, although it doesnt exactly match my probs - in terms that my phone boots up most of the time, but restarts randomly...
So I did what I was supposed to do and installed CyanogenMod after following step 10 Amon Ra's Recovery (I have PVT4 device) but same thing continues to happen - reboots, apparently on trying to add account on phone...
SORRY FOR SUCH LONG POST, but Im out of ideas, and new to this so PLEASE< PLEASE HELP me if u somehow can...
Thanks in advice
goxyendzy said:
I simply have done all i can - and it seems that i cant do it right. Please consider to help me, because im noob.
Before i state my problem i should say that i have googled an crossed xda forum for 4 days and without any improvement.
Problem I have is that, my phone randomly reboots at no particular time or place - but here come the details:
First, for purpose of unlocking phone from SIM lock from carrier, it was S-OFFed and rooted by someone else (previous owner).
Rom was installed - Oxygen 2.3.2. and it worked for few months without bugs.
Then, one day it restarted and stuck in bootloops, but it came up for few seconds, or some time (but not for long), and then again restarted and so on. Eventually it held enough to do a factory reset which generally helped, but with one strange thing - clock couldnt sync and loosed about an hour for 5-6 hours (really strange).
Then i decided to try some other ROM hoping to resolve clock issue.
When I go into HBOOt it says:
--- AlphaRev ---
BRAVO PVT4 SHIP S-OFF
HBOOT-6.93.1002
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27
Aug 10 2010 17:52:10
Then i went here -> http://forum.xda-developers.com/show...p?t=1315961URL and done REALLY step by step whole procedure.
ROM was installed, along with -> http://forum.xda-developers.com/show....php?t=1408936
It worked flawllessly for about half an hour an then started rebooting on no particular action - sometimes went up for some time few secs to 10-20 mins an then reboot and sometimes it got stuck in endless loop (only pulling the battery helped).
Since it went wrong, i tried to RESTORE previosly made BACKUP of mentioned OXYGEN ROM, but sadly, same thing happened all the time.
I was devasteted, didnt know what to do so I decided to get back to STOCK ROM via RUU. (thought it would solve the problem)
I used RUU_Bravo_Froyo_HTC_WWE_2.29.405.14_Radio_32.49.00 .32U_5.11.05.27_release_224699_signed
Phone stayed S-OFF (obviosly for AlphaRev HBOOT) but have been preety stable comparing what was happening before, in terms: restarted few times for a day and allways rebooted back. Then i inserted other SIM card ant it began again with restarts as soon it went up and been up for 10-20 secs. After few reboots, it stabilised, but had different problem: couldnt add new account, and couldnt remove one I set up at the beginning (message said that i should do FACTORY reset if i want account removed). So I did factory reset - and NOTHING HAPPENED - evrything stayed exactly as it was - with account and everything.
Then i came across BORTAKs Guide ->http://forum.xda-developers.com/showthread.php?t=1275632 and followed step one, although it doesnt exactly match my probs - in terms that my phone boots up most of the time, but restarts randomly...
So I did what I was supposed to do and installed CyanogenMod after following step 10 Amon Ra's Recovery (I have PVT4 device) but same thing continues to happen - reboots, apparently on trying to add account on phone...
SORRY FOR SUCH LONG POST, but Im out of ideas, and new to this so PLEASE< PLEASE HELP me if u somehow can...
Thanks in advice
Click to expand...
Click to collapse
Did you try to run RUU after flashing Alpharev downgrade to achieve S-ON gain, or you just ran it over Alpharev stock?
Also did you try to format sd card or to remove it from phone and than to boot it up?
It all seems like it was SIM unlocked by a "fake" code so that are the issues that can happen.
Plus: to gain SIM unlock you don't need S-off and root.
nlooooo said:
Did you try to run RUU after flashing Alpharev downgrade to achieve S-ON gain, or you just ran it over Alpharev stock?
Also did you try to format sd card or to remove it from phone and than to boot it up?
It all seems like it was SIM unlocked by a "fake" code so that are the issues that can happen.
Plus: to gain SIM unlock you don't need S-off and root.
Click to expand...
Click to collapse
I ran it over Alpharev... Im really new to this so i ask for help.
U say that i should:
1) flash AlphaRev downgrade to achieve S-ON gain (HOW exactly? please link to some guide if exists)
2) then run RUU
I tried formatting SD card later, removed it, even change card and latest ROM (Cyanogen) is on other SD card and its all the same...
Thanks for fast reply
goxyendzy said:
I ran it over Alpharev... Im really new to this so i ask for help.
U say that i should:
1) flash AlphaRev downgrade to achieve S-ON gain (HOW exactly? please link to some guide if exists)
2) then run RUU
I tried formatting SD card later, removed it, even change card and latest ROM (Cyanogen) is on other SD card and its all the same...
Thanks for fast reply
Click to expand...
Click to collapse
Yes, both steps. With that you will overwrite both hboot and radio to stock ones, that could be the things that made you problems. You will get S-on after flashing of RUU (I recomend 2.3) when your hboot is overwritten.
This is a good guide how to use ADB and fastboot (you will need fastboot for flashing of hboot):
http://androidforums.com/desire-all...fastboot-windows-updated-1st-june-2011-a.html
But reading your post I think that the problem is with unlocking (SIM). If a guy that sold you the phone said he did it with S-off and root he is laying, as I told you it can't be done with that. The problem can occur when you unlock the phone with a "fake code" that actually removes the part of phone's software used to check for carrier and not replacing critical parts (something like that).
There's a tool:
http://forum.xda-developers.com/showthread.php?t=943726
Try to run it and see what you will get.
nlooooo said:
Yes, both steps. With that you will overwrite both hboot and radio to stock ones, that could be the things that made you problems. You will get S-on after flashing of RUU (I recomend 2.3) when your hboot is overwritten.
This is a good guide how to use ADB and fastboot (you will need fastboot for flashing of hboot):
http://androidforums.com/desire-all...fastboot-windows-updated-1st-june-2011-a.html
But reading your post I think that the problem is with unlocking (SIM). If a guy that sold you the phone said he did it with S-off and root he is laying, as I told you it can't be done with that. The problem can occur when you unlock the phone with a "fake code" that actually removes the part of phone's software used to check for carrier and not replacing critical parts (something like that).
There's a tool:
http://forum.xda-developers.com/showthread.php?t=943726
Try to run it and see what you will get.
Click to expand...
Click to collapse
Thanks in advance, ill try everything when i setup everything properly. Will update on progress! :good:
OK, at fisrt I have removed both SIM and SD cards and then:
1) flashed AlphaRev downgrade to achieve S-ON
2) then run RUU
Inserted only SIM card, and for now without reboots - but this was only 15 mins ago, so ill keep informing about case after testing, in hope not to get another reboot ever.
What I realised is thatr I dont have recovery?
Is this supposed to be? And how will I resolve problem If something unwanted occur?
Thanks a lot for Your help!
goxyendzy said:
OK, at fisrt I have removed both SIM and SD cards and then:
1) flashed AlphaRev downgrade to achieve S-ON
2) then run RUU
Inserted only SIM card, and for now without reboots - but this was only 15 mins ago, so ill keep informing about case after testing, in hope not to get another reboot ever.
What I realised is thatr I dont have recovery?
Is this supposed to be? And how will I resolve problem If something unwanted occur?
Thanks a lot for Your help!
Click to expand...
Click to collapse
You have recovery, but it is stock one (pretty different to custom ones ).
Now after you flashed 2.3 RUU you probably have 1.02 hboot, so go here:
revolutionary.io
Download the tool and follow the process described to achieve s-off and root again (the problem you have have nothing connected with s-off and root but probably with some parts of system software which might be recovered now). During the process you will flash Clockworkmod recovery, from which you will install Superuser.apk. After that reboot the phone and go here:
4ext.net
Download Recovery updater, install it to your phone and flash 4ext recovery. Than from recovery you can restore backup you have from your old rom, but my suggestion is to go here:
http://forum.xda-developers.com/showthread.php?t=809328
and find something for you, cause I think that you have to start from scratch to have a proper software (cause you already had problems with previous one).
If you're up to Oxygen again go here:
http://download.oxygen.im/roms/
but I think that there are a few roms on previous link that are based on Oxygen, but a little bit modified with some extra options.
Well, thanks really, but for now I would like to live things as they are...
I dont mind beeng S-ON and not rooted, if phone doesnt reboot again. I just need it functioning, without advanced options.
Are U suggesting that STOCK ROM is not the way I should go?
goxyendzy said:
Well, thanks really, but for now I would like to live things as they are...
I dont mind beeng S-ON and not rooted, if phone doesnt reboot again. I just need it functioning, without advanced options.
Are U suggesting that STOCK ROM is not the way I should go?
Click to expand...
Click to collapse
It's the way I went for a long time until I started experimenting, mostly because a lack of space. After that I found the thread I posted (All things desire) and wanted to try some advanced roms (Sense 3.0, 3.5) even made some stuff on my own on that way.
http://forum.xda-developers.com/showthread.php?p=23101063#post23101063
My opinion is that stock roms are the best solution foe our device, cause it runs smoothest and I think that Sense is something that brings HTC devices above all other android devices. I've never been a fan of AOSP software but I tried it, just to see how it feels. I even used MIUI rom for some time as the first software option.
Anyway, the story with memory problem stays, but the main point for getting s-off and root again are diagnostic and flashing options cause on s-off device you can flash all crucial partitions that can cause problems (hboot and radio-see attachment) and change partition table layout to gain space (see alpharev.nl)
I hope I helped!
nlooooo said:
It's the way I went for a long time until I started experimenting, mostly because a lack of space. After that I found the thread I posted (All things desire) and wanted to try some advanced roms (Sense 3.0, 3.5) even made some stuff on my own on that way.
http://forum.xda-developers.com/showthread.php?p=23101063#post23101063
My opinion is that stock roms are the best solution foe our device, cause it runs smoothest and I think that Sense is something that brings HTC devices above all other android devices. I've never been a fan of AOSP software but I tried it, just to see how it feels. I even used MIUI rom for some time as the first software option.
Anyway, the story with memory problem stays, but the main point for getting s-off and root again are diagnostic and flashing options cause on s-off device you can flash all crucial partitions that can cause problems (hboot and radio-see attachment) and change partition table layout to gain space (see alpharev.nl)
I hope I helped!
Click to expand...
Click to collapse
Since there are no reboots yet (I really hope its in past) U have been more than helpful! :good:
I still havent inserted sd card, and been consedering of getting a new one (with higher speed).
Also, as I see that U R my countryman (ko ce kome ako ne svoj svome), U have earned a few drinks when U come to my town!
I will be updating how things are regarding of this case.
Cheers :highfive:
goxyendzy said:
Since there are no reboots yet (I really hope its in past) U have been more than helpful! :good:
I still havent inserted sd card, and been consedering of getting a new one (with higher speed).
Also, as I see that U R my countryman (ko ce kome ako ne svoj svome), U have earned a few drinks when U come to my town!
I will be updating how things are regarding of this case.
Cheers :highfive:
Click to expand...
Click to collapse
No problem, I'm holding you for your word!
If you have no reboots try to insert different carriers sim cards and see if it's still unlocked.
reboots again
nlooooo said:
No problem, I'm holding you for your word!
If you have no reboots try to insert different carriers sim cards and see if it's still unlocked.
Click to expand...
Click to collapse
Reboots again...
After half a day of normal usage, I tried inserting another SIM (but from same carrier) and it started again...
Not so often but from time to time it reboots.
So I guess, at the end it seems it is hardware fault.
One strange thing thou (and it makes me wonder): When I try removing account it says I should do Factory Reset if I want to change that basic acc. But afrer performing Factory Reset NOTHING happens? Account is still there, along with other settings and/or installed apps.
Any ideas?
Invitation still holds

[Q] Desire; S-OFF, rooted to partition SD card, now won't get past hboot?

Hello all,
I've done a search on this but can't find anything describing a problem exactly the same as mine (although I have a feeling it is what people mean when they say bootloop?).
So with the eventual aim of freeing up the internal storage on my Desire by partitioning the SD card (and using link2sd), I have gained S-OFF with the Revolutionary method, got root with superuser.zip and used 4ext Recovery Touch to format the SD card by using this guide. Now this is where things went a bit wrong. 4ext kept saying I was in safe mode and didn't seem to be doing anything. I followed some more instructions from here to wipe the cache and possibly some other things (this is probably where I went wrong..). I do believe I now have a 2GB sd-ext partition (ext3) and 6GB FAT32 (it's an 8GB card).
Now, when I boot the phone it goes straight to the hboot screen (white screen with skateboarding androids). No matter what options I choose it won't boot into Android-proper. I can however, get back into Recovery (4ext) so I'm assuming I'm not in a huge amount of trouble and have perhaps just screwed up my stock install.
I was planning on keeping it stock (it is actually my girlfriends so I didn't want any hassle), but now I am thinking I could just install a new ROM? Just wondering what my best route from here is..
Should I attempt to go back to stock by following a guide like this (2nd post) with a 'Desire 2.3 RUU (PB99IMG)'? Will that work? Will it undo everything else I've done? Having read up on here about RUUs I'm a bit scared of that to be honest..!
Or should I follow post #1 on the troubleshooting guide and use 4ext to install a brand spanking new ROM?
Thanks for any advice.
No need to RUU, that would undo everything.
So you're already s-off, with 4ext installed, and you can boot into recovery :good: You've partitioned your sd card correctly too (ext4 should in theory be faster than ext3, you can convert it quite easily in 4EXT, but may not make much difference)
Now just install a new rom from scratch is the easiest way. Pick one from the development section, still plenty of choice. You can even find the stock rooted 2.3.3 Rom there somewhere if she wants that. Use the "wipe all partitions except sd card" option within 4EXT, then install the ROM.zip.
When you pick a ROM, you should also check which hboot is more optimal for space within each thread. You're currently still on stock hboot I take it, which has 250MB system size. A lot of ROMs have smaller system than this, so using a more efficient hboot with smaller system size (and larger internal memory (/data) partition ) is beneficial. You'll need to go to alpharev.nl to find the hboots, and I recommend to flash them using fastboot commands
Depending on the ROM, you may not need to use link2sd at all as it likely has an A2SD script built in, or you may need to activate it via terminal commands, read/search the individual rom thread for details.
If you're still worried about space, I always recommend to use an app like 'diskusage' to browse all your partitions.
Thanks, very helpful. I did originally partition the ext-sd as ext4 but when it didn't work I thought I should perhaps try ext3. I thought perhaps the Desire wasn't recognising the ext4 format. As it turns out I think it was just because I had done it all in safe mode? Will the Desire recognise a 2gb ext4 partition? If so, I may as well reformat again..!
Unfortunately I'm at work now so don't have the phone infront of me. I remember it says 'Revolutionary' in pink at the top in hboot, but I can't remember the numbers.
As for ROMS.. hmn so many options. Any recommendations for something stable and reasonably fast. Stable being the top priority I suppose. I'm tempted to try a JB ROM but I'm assuming that wouldn't be particularly fast or stable! Might be interesting to try though. I will use Apex Launcher over the top of it anyway...
Scamm0r said:
Thanks, very helpful. I did originally partition the ext-sd as ext4 but when it didn't work I thought I should perhaps try ext3. I thought perhaps the Desire wasn't recognising the ext4 format. As it turns out I think it was just because I had done it all in safe mode? Will the Desire recognise a 2gb ext4 partition? If so, I may as well reformat again..!
Unfortunately I'm at work now so don't have the phone infront of me. I remember it says 'Revolutionary' in pink at the top in hboot, but I can't remember the numbers.
As for ROMS.. hmn so many options. Any recommendations for something stable and reasonably fast. Stable being the top priority I suppose. I'm tempted to try a JB ROM but I'm assuming that wouldn't be particularly fast or stable! Might be interesting to try though. I will use Apex Launcher over the top of it anyway...
Click to expand...
Click to collapse
Try deleting the 4ext folder on your sd card to fix the safe mode issue, or also try going into wipe and select "Format all partitions (except sd card)."
I would recommend any of milwilds roms. My personal favourite is this one. Its very fast and stable, based on gingerbread, and its usually what i install on other peoples desires.
As for jb roms go, i wouldnt recommend one if your installing it for someone that doesnt know much about phones. They arent particularly fast, but the one i use (in my signature) is quite stable in my opinion.
Scamm0r said:
Unfortunately I'm at work now so don't have the phone infront of me. I remember it says 'Revolutionary' in pink at the top in hboot, but I can't remember the numbers.
Click to expand...
Click to collapse
If you don't remember changing hboot, you're still on stock hboot.
As for ROMS.. hmn so many options. Any recommendations for something stable and reasonably fast. Stable being the top priority I suppose. I'm tempted to try a JB ROM but I'm assuming that wouldn't be particularly fast or stable! Might be interesting to try though. I will use Apex Launcher over the top of it anyway...
Click to expand...
Click to collapse
I can also vouch for mildwild roms. These have much smaller system sizes, so best to change hboot before you install them as instructed above. Most of them fit into cm7r2 hboot, but check each thread for compatibility.
Thanks guys. Would you recommend that MW ROM over something like CyanogenMod 7.2.0.1 off their site? I see CM banded around quite alot, seems to be a go-to ROM for alot of people?
I'm home now, this is what I see on hboot:
-Revolutionary-
BRAVO PVT1 SHIP S-OFF
HBOOT-6.93.1002
MICROP-031d
TOUCH-PANEL-SYNT0101
RADIO-5.11.05.27
Also, before I do it. Any problems for the Desire to see a 2GB ext4 partition? With the rest as FAT32? She won't be putting alot of media on it as she has a separate iPod.
Thanks.
Scamm0r said:
Thanks guys. Would you recommend that MW ROM over something like CyanogenMod 7.2.0.1 off their site? I see CM banded around quite alot, seems to be a go-to ROM for alot of people?
I'm home now, this is what I see on hboot:
-Revolutionary-
BRAVO PVT1 SHIP S-OFF
HBOOT-6.93.1002
MICROP-031d
TOUCH-PANEL-SYNT0101
RADIO-5.11.05.27
Also, before I do it. Any problems for the Desire to see a 2GB ext4 partition? With the rest as FAT32? She won't be putting alot of media on it as she has a separate iPod.
Thanks.
Click to expand...
Click to collapse
I would go with mw over cm. Cm 7 feels old and stale, while milwilds redux ROM feels fresh and different. In terms of stability and speed they are pretty much the same.
2gb shouldn't be too much of an issue, but usually the max recommend ext partition is 1.5gb.
Thanks again. I'm now up and running. Looks very nice indeed! I'll be honest though, I bailed out of flashing a new hboot. Too scary. After incurring the girlfriend's wrath after one day with a dead phone, I wouldn't want to brick it entirely!
A couple of questions now..
- Do I need to install link2sd? I'm looking at 'diskusage' but I'm struggling to make much sense of it. I can see my sd-ext on there though which I guess is good!
- Are there any peculiarities installing generic apps like Facebook, Youtube etc? At first glance the market seems to work ok.
- Does the cpu underclocking (whilst screen off) work well? Is it risky at all if I use the generic settings?
Also, I was going to chuck Apex launcher on it for her (I love it, and she wants a scrolling dock) but it's not compatible. Any others that are good? Nova isn't compatible either
Scamm0r said:
Thanks again. I'm now up and running. Looks very nice indeed! I'll be honest though, I bailed out of flashing a new hboot. Too scary. After incurring the girlfriend's wrath after one day with a dead phone, I wouldn't want to brick it entirely!
A couple of questions now..
- Do I need to install link2sd? I'm looking at 'diskusage' but I'm struggling to make much sense of it. I can see my sd-ext on there though which I guess is good!
- Are there any peculiarities installing generic apps like Facebook, Youtube etc? At first glance the market seems to work ok.
- Does the cpu underclocking (whilst screen off) work well? Is it risky at all if I use the generic settings?
Also, I was going to chuck Apex launcher on it for her (I love it, and she wants a scrolling dock) but it's not compatible. Any others that are good? Nova isn't compatible either
Click to expand...
Click to collapse
No need to install link2sd. A2sd is installed by default and is already activated. Dont worry about it.
Apex and nova need 4+, so i would recommend holo or go launcher. i think the default cpu settings work good enough.
Scamm0r said:
Thanks again. I'm now up and running. Looks very nice indeed! I'll be honest though, I bailed out of flashing a new hboot. Too scary. After incurring the girlfriend's wrath after one day with a dead phone, I wouldn't want to brick it entirely!
A couple of questions now..
- Do I need to install link2sd? I'm looking at 'diskusage' but I'm struggling to make much sense of it. I can see my sd-ext on there though which I guess is good!
- Are there any peculiarities installing generic apps like Facebook, Youtube etc? At first glance the market seems to work ok.
- Does the cpu underclocking (whilst screen off) work well? Is it risky at all if I use the generic settings?
Also, I was going to chuck Apex launcher on it for her (I love it, and she wants a scrolling dock) but it's not compatible. Any others that are good? Nova isn't compatible either
Click to expand...
Click to collapse
You won't brick your phone by flashing an hboot, as long as you follow all the instructions . It's beneficial just in case your girlfriend starts installing many apps. App data still gets stored on the internal memory (/data) partition, so it may get the low memory warning again which kind of defeats the purpose of doing this in the first place.
Open diskusage again, choose /system. You'll see a lot of free space on this partition....that's basically all completely wasted on stock hboot. At least you can see you sd-ext partition fillling up though.
There's another way to flash hboot without fastboot commands if you prefer. I always recommend that way simply because it forces the user to understand a little about what they're doing, plus it's always handy to install adb and fastboot drivers anyway
So:
- Download the PB99IMG_cm7r2.zip from alpharev.nl, rename it to PB99IMG.zip exactly, not PB99IMG.zip.zip, put it on the root of your sd card
- Reboot directly into recovery, nandroid backup (hard to go wrong now, no need to worry)
- Power down, boot into bootloader (vol down + power)
- It should find the file, and ask you to flash it, select yes
- Reboot into recovery, full wipe and nandroid restore
- It's exactly the same, but enjoy the extra internal memory. Open diskusage again, you'll find that there's less free space on /system, and /data has increased
Thanks Eddie, you're right of course. How safe is that method compared to using Android Flasher? I already had that installed on my PC for one of the steps previous.
So the nandroid backup will keep the phone set up as it is? I know she will have been customising her homescreens etc already now that it's up and running haha. OR is it best to reinstall the ROM again anyway and start from scratch?
I presume the backup option in 4ext recovery is a nandroid backup? I think I did one of those before after I got MW up and running.
Thanks again.
Scamm0r said:
Thanks Eddie, you're right of course. How safe is that method compared to using Android Flasher? I already had that installed on my PC for one of the steps previous.
So the nandroid backup will keep the phone set up as it is? I know she will have been customising her homescreens etc already now that it's up and running haha. OR is it best to reinstall the ROM again anyway and start from scratch?
I presume the backup option in 4ext recovery is a nandroid backup? I think I did one of those before after I got MW up and running.
Thanks again.
Click to expand...
Click to collapse
Android flasher is the same as fastboot really. It's just a program so you don't type things. I've never used it personally, but it should work. I believe you flash the cm7r2.img directly (not the.zip file). All 3 of those methods (fastboot, android flasher, PB99IMG.zip are safe, get the same result eventually)
The thing to remember (which I should have mentioned before) whichever method you use, check the md5 sums of the .img files before you flash them (you should be able to see those long text/numbers on the alpharev page). Search for a program called md5check. (It just basically verifies the file against that md5 sum like a barcode so you know haven't downloaded a bad file.)
Nandroid backup is an exact image of the phone as it is. Homescreens, saved game data, texts, everything. So you won't lose anything after restoring it. I suggested that you change hboot before you install the rom for this exact reason, so you wouldnt have to backup and restore, but we're here now already

Categories

Resources