[Q] Splash Screen Backup - General Questions and Answers

Hi all,
After getting very frustrated with out-of-space messages on my UK HTC Desire (Virgin Mobile) I've been getting it ready for flashing with a custom rom, probably something like Gingerburst.
Anyhow. Today (after a lot of reading; I assure you!) I used Unrevoked to root my device - that went painlessly. I had imagined that I wanted s-off so was a little surprised when it didn't do it. The plan is now to use AlphaRev to sort out the s-on/s-off issue - only I don't want their Joker splash screen.
I actually quite like my stock HTC (white, no quietly brilliant) and black Virgin Media splash screens. Is there a way to back this up so I can restore it after I've AlphaRev'd it?
I hope so! Thanks in advance for your help. Apologies if this is a repeat; I did search fairly extensively and didn't manage to find anyone doing the same thing - or trying to.
(Out of interest do I really need s-off to get the most out of rooting and flashing custom roms? If not, I'll probably leave it!)
Thanks!
Smii

Some more in-depth and circuitous searching has turned up a chap who used a linux program (name escapes me) to unpack the boot.img file from the nandroid backup and push a particular file (his wifi settings) back up to his phone.
If I was to a) get a handle on the exact methodology and b) find out where in the boot.img file the splash screen is, I suppose I could conceivably do the same? Run AlphaRev 1.8, then push my original splash over the top? Hopefully it wouldn't undo the s-off.
Can anyone confirm that the splash screen is included in the nandroid backup?

Related

Ok, I give up --- cant get out of G1 bootie, skateboards & CM/JF recovery -- help

G1 DREAM (really is a dream, right now, a little bad one a little embarrassing)
been 5 mos since I took root via Cyanogenmod's latest G1 stable and last theme was PHRASh Then I thought about checking out
some other themes and clockwork orange caught my eye... Orange is my favorite color, so wehen I saw there was some Orange theme I must've had a dare encounter with myself-- i recall actually installing the Orange theme..... when i asked the phone to flash the theme, it went into permanent G1. Gave it about 12 minutes. Rebooted into recovery (home menu power) and then did what I think got me in deep droid doo doo -- I attempted to restore to my last backup whch was the day before (and ironically the BEST backup i ever made I had it all humming so nice and fast) Guys -- instead of hitting restore to last backup... I actually hit nandroid backup. I know. That was a really bad day and its been a worse 50 hours. I know -- and Ive learned -- OK?
Since that time.... 50ish hours Ive lost track of what Ive done, but its a potpourri
bootloader is dev spl skateboarding, recovery is Cyanogenmod JesusFreke 1.4 recovery.
DREAM DREA100 PVT 320
HSPL10.95.3000
CPLD-4
RADIO 2,22.19.361
OCT 29 2008
SERIAL0 -- (fastboot i have fastboot as well)
at first flash of bootloader it says "NO IMAGE FOUND!"
If I press Home when it restarts in perpetual cyclical hell I get into CMJF recovery. I have executed every single option numerous times -- and have not been able to successfully flash anything else -- and now I dont know WHAT to flash. I even tried to go back to root!
If I dont press Home or Camera, I get this....
the awful permanent G1 screen. Forever and ever.
I have Wiped backed up, tried to get update.zip and just about ANYTHING into my sdcard but I dont think they have been successful installations to flash. I am not ADB enabled yet. Surely someone knows what this is all about and I am willing to take a flame for posting in the wrong forum if I can get something out of this, I will pitch in later and help y'all keep these forums in workin' order!
every optioon on the recovery screen which is recovery CM and JF 4.2
When I try to load files according to the instructions in xda and cm i cannot get it in fast enough on the g1 running on the frozen G1 screen because I dont known the time of mount the SDCARD has and when it begins (I know it opens for a while and then closes)
So i got droidexplorer and its almost impossible to get the file in there. I can get it in, and see it, and reboot the phone (and computer)( restore usb connection and I see the update.zip on the sdcard. Then I unmount the phone and reflash and it says something about not being able to find the file.
Whats next? Please dont assume I know what I am doing, I am sure you can tell -- but I am really good at following instructions!
Hello anyone?
I have been up all night trying to fix this phone and i am still not able to do so. I
I cannot get into recovery anymore ------
i am stuck on the hardspl and I have found fastboot again. But I cannot use frastboot if I cannot get any commands into it. Anyone?
ok i get it -
thanks for the help guys! I now have my phone working at a blitzing pace and i am leaving it alone for now. I dare myself to leave it unchanged for a week. Thanks mostly to one of the Dudes on Cyanogenmod.com -- who helped me piece together the missing parts.
Actually -- let me summarize even if only I am reading this
Androids levels of defenses are 1. HardSPL 2. Recovery and 3. normalcy. Lose normalcy (Ok, a beauty of a ROM) you have recovery to get the ROM back -- but the trick is -- can you get the necessary IMG file on your SDcard to update.zip with? Can you figure out ADB and push the update.zip? Can you figure out Fastboot and what it REALLY does and what you can and cannot do with FB? If you can do any of these or FB with ADB, then you have a good chance. Just dont lose the HardSPL. If you give up after frustration and while grinding your teeth waving a white flag, flash the DREAIMG.img file, then you have given up root and FB. But at least you are at RC29, the level where the froot can be found. It is weird hanging out in Android 1.0 lemme tell ya. Feels so 1980'ish with bellbottoms in late decline.
But now its android time at CM with Phrash.
Later

un-root a mt3g 1.2/fender

Hello...
I've been frantically googling and checking the forums, I have a mt3g 1.2 (3.5mm) that needs to be exchanged to t-mobile, I rooted following the stock fender w/ root method, and need to revert it back to the stock settings as shipped. So far, my search has turned up no resolve. I was hoping someone here could provide me with the proper sappimg.nbh to restore. I've got the one for the original MT3G, but it (as expected) damages touch-screen capabilities. Can someone please help?
As far as I know, it's not possible until T-Mobile releases an OTA update for either the Fender or MyTouch 3.5mm. That was explained in the rooting instructions here on XDA...
merlino211 said:
Hello...
I've been frantically googling and checking the forums, I have a mt3g 1.2 (3.5mm) that needs to be exchanged to t-mobile, I rooted following the stock fender w/ root method, and need to revert it back to the stock settings as shipped. So far, my search has turned up no resolve. I was hoping someone here could provide me with the proper sappimg.nbh to restore. I've got the one for the original MT3G, but it (as expected) damages touch-screen capabilities. Can someone please help?
Click to expand...
Click to collapse
If you use the stock rom http://www.theandroidkitchen.com/fileshare/MyTouch3g32A/?download=MT3G32AFender-1.0-fixed-signed.zip and then you should have touchscreen. It's only with custom roms that touchscreen does not work.
Couldn't you just flash the Mytouch splash image and turn in in like that?
It looks pretty stock after that.
shawn1224 said:
Couldn't you just flash the Mytouch splash image and turn in in like that?
It looks pretty stock after that.
Click to expand...
Click to collapse
... you got the splash image handy?
kbeezie said:
... you got the splash image handy?
Click to expand...
Click to collapse
you can find the stock mt3g splash screen if u search on here but not the fender one... i got the stock myt3g splash on my 1.2...
ceas909 said:
you can find the stock mt3g splash screen if u search on here but not the fender one... i got the stock myt3g splash on my 1.2...
Click to expand...
Click to collapse
That's what I'm saying though, no one seems to have the fender one. Far as the op's situation, might have tried flashing one of those "32A" roms, which obviously won't work at this point, probabbly best to just try the rom from my signature (the one linked as Rooted), which is basically the stock rom and touchscreen and all that should work.
kbeezie said:
That's what I'm saying though, no one seems to have the fender one. Far as the op's situation, might have tried flashing one of those "32A" roms, which obviously won't work at this point, probabbly best to just try the rom from my signature (the one linked as Rooted), which is basically the stock rom and touchscreen and all that should work.
Click to expand...
Click to collapse
yea he has a 1.2, so yea i think his best bet is to get the stock mt3g splash screen and the stock fender rom... the only problem is that between the fender and the 1.2 the build number is different..the 1.2 is 2.10.531.4 CL119339 release-keys where the fender is 2.10.531.3 CL111099 release-keys .... but a simple edit of the build prop could make it display the correct buid numbers in the about phone menu..
I've actually attempted to just replace the splash with the original mytouch splash. This can be achieved by applying a proper SPL that will allow it to be replaced... PROBLEM being that after repacing the SPL with the ones linked: theunlockr[.]com/2010/03/10/how-to-change-your-splash-screen/
Once this process is taken, the radio functions and all seems well, EXCEPT that now when I place calls, my speaker does nothing. Phones can receive the calls and hear me, but I hear nothing. the end result is to reflash the phone with the rooted rom, minus the mt3g splash... This part is where my frustration is kicking in as their guide claims this is specific for the fender/mt3g 1.2, but yet bricks the speaker somehow.
UPDATE!!
Click to expand...
Click to collapse
It appears that the guide on unlockr is wrong for this phone. I was successfully able to get the splash back on the phone by implementing the steps of adding the splash DURING the initial radio and recovery image restores, at which point the sappimg used is the engineering 2010. Once the splash was loaded at this point, I was able to continue with the install, install the rom, but a fresh install would *not* boot into the OS, just hung on a black screen after the animated "android" splash. Upon restoring a nandroid back-up, the phone booted to the OS in its formerly operational state, mt3g splash included.... I'm going to attempt a factory reset from the phones main options purely to see if it'll boot or hang on the black screen again.
Update 2.0
Click to expand...
Click to collapse
Methods were all successful, factory reset worked to bring the phone back to the android setup wizard WHILE retaining the splash screen with no blank screen as described earlier... Process was as followed:
Performing the unlockr guide; during the following steps:
fastboot flash radio radio.img
fastboot flash hboot hboot.nb0 (the 0 at the end of this line is a zero not an oh).
fastboot flash recovery recovery.img
fastboot reboot-bootloader
the phone is currently running the SPL for the Engineering SPL 1.33.2010... I modified the above process to reflect
fastboot flash splash1 splash.nb
fastboot flash radio radio.img
fastboot flash hboot hboot.nb0 (the 0 at the end of this line is a zero not an oh).
fastboot flash recovery recovery.img
fastboot reboot-bootloader
Recovered from the rooted fender stock image, which then took me to a blank screen. Recovered from a nandroid back-up, which restored the phone to my state just prior to (re)flashing. After nandroid backup is restored and successfully making calls, factory reset was done and test calls were successfully made from the freshly reset version of fender/wroot stock.... A bit hackish and unorthodox, but it answered the question I was so valiantly struggling to find resolve to.
It appears the stock fender /w root reverts the hboot version to the non-engineering, which functions fine with the speaker.... Hope this helps someone else who was in the same boat as me.
merlino211 said:
I've actually attempted to just replace the splash with the original mytouch splash. This can be achieved by applying a proper SPL that will allow it to be replaced... PROBLEM being that after repacing the SPL with the ones linked: theunlockr[.]com/2010/03/10/how-to-change-your-splash-screen/
Once this process is taken, the radio functions and all seems well, EXCEPT that now when I place calls, my speaker does nothing. Phones can receive the calls and hear me, but I hear nothing. the end result is to reflash the phone with the rooted rom, minus the mt3g splash... This part is where my frustration is kicking in as their guide claims this is specific for the fender/mt3g 1.2, but yet bricks the speaker somehow.
It appears that the guide on unlockr is wrong for this phone. I was successfully able to get the splash back on the phone by implementing the steps of adding the splash DURING the initial radio and recovery image restores, at which point the sappimg used is the engineering 2010. Once the splash was loaded at this point, I was able to continue with the install, install the rom, but a fresh install would *not* boot into the OS, just hung on a black screen after the animated "android" splash. Upon restoring a nandroid back-up, the phone booted to the OS in its formerly operational state, mt3g splash included.... I'm going to attempt a factory reset from the phones main options purely to see if it'll boot or hang on the black screen again.
Methods were all successful, factory reset worked to bring the phone back to the android setup wizard WHILE retaining the splash screen with no blank screen as described earlier... Process was as followed:
Performing the unlockr guide; during the following steps:
fastboot flash radio radio.img
fastboot flash hboot hboot.nb0 (the 0 at the end of this line is a zero not an oh).
fastboot flash recovery recovery.img
fastboot reboot-bootloader
the phone is currently running the SPL for the Engineering SPL 1.33.2010... I modified the above process to reflect
fastboot flash splash1 splash.nb
fastboot flash radio radio.img
fastboot flash hboot hboot.nb0 (the 0 at the end of this line is a zero not an oh).
fastboot flash recovery recovery.img
fastboot reboot-bootloader
Recovered from the rooted fender stock image, which then took me to a blank screen. Recovered from a nandroid back-up, which restored the phone to my state just prior to (re)flashing. After nandroid backup is restored and successfully making calls, factory reset was done and test calls were successfully made from the freshly reset version of fender/wroot stock.... A bit hackish and unorthodox, but it answered the question I was so valiantly struggling to find resolve to.
It appears the stock fender /w root reverts the hboot version to the non-engineering, which functions fine with the speaker.... Hope this helps someone else who was in the same boat as me.
Click to expand...
Click to collapse
Or you can just goto the thread in the link of my sig ("rooted"), you want to make sure when you're reading guides that they are for your specific phone, some people have bricked their fenders or 1.2 cuz they got the wrong radio/spl intended for the older MyTouch3G
I made sure to use the right guide on the unlockr, the problem came specifically from where they had the SLP change guide... Either way, problem is fixed now and it'll be in the hands of the t-mobile store tomorrow. If I ever doubtfully get a question about the root from them after it ships back, I'll play dumb and inquire if maybe someone else did it while it was waiting to ship
merlino211 said:
I made sure to use the right guide on the unlockr, the problem came specifically from where they had the SLP change guide... Either way, problem is fixed now and it'll be in the hands of the t-mobile store tomorrow. If I ever doubtfully get a question about the root from them after it ships back, I'll play dumb and inquire if maybe someone else did it while it was waiting to ship
Click to expand...
Click to collapse
i hope they dont catch the build number being different.. as i stated in eairler post the build nmbers in the about phone menu are different from the fender and the 1.2
ceas909 said:
i hope they dont catch the build number being different.. as i stated in eairler post the build nmbers in the about phone menu are different from the fender and the 1.2
Click to expand...
Click to collapse
In my experience most sales reps are completely ignorant of that kind of thing, changing the boot screen may be enough to make em go along with it. IF you're dealing directly with the company on the other hand that may be a different story.
It's being shipped back via the store under the 14 day buyers resource. I have had two of these so far, both have suffered from the screen oddly self-scrolling... Figure maybe a bad lot produced, as t-mobile tech support has not even heard of such a problem before. I finally settled on buying a nexus one, which arrives tomorrow. The store doesn't even check the phones out except to make sure all parts and accessories are contained in the box, there it will sit for (they said, roughly a week) before it's shipped back to T-mobile. By then, I figure liability of the phone is officially out of my hands.
merlino211 said:
It's being shipped back via the store under the 14 day buyers resource. I have had two of these so far, both have suffered from the screen oddly self-scrolling... Figure maybe a bad lot produced, as t-mobile tech support has not even heard of such a problem before. I finally settled on buying a nexus one, which arrives tomorrow. The store doesn't even check the phones out except to make sure all parts and accessories are contained in the box, there it will sit for (they said, roughly a week) before it's shipped back to T-mobile. By then, I figure liability of the phone is officially out of my hands.
Click to expand...
Click to collapse
I think you mean buyer's remorse, also I was under the impression that Limited Editions could not be 'returned' , merely exchanged or serviced.
If you don't have a contract, you could sell the phone once you put the working stock rooted rom onto it.
jesus... some of you really hurt my head over this phone.
So flashing the stock mytouch splash screen doesnt work if youre on a 1.2 or are most of you guys worrying because you have fenders?? Also can someone give me the mytouch splash screen???
You can find it here
http://theunlockr.com/2010/03/10/how-to-change-your-splash-screen/

How to Root CDMA Desire! HOOT 0.98

How to Root CDMA Desire! HOOT 0.98
Original post can be found HERE/
As many of us have researched, the Hoot on the desire is 0.98 and is hard to find any other instructions to root. Im a DROID user on the Cell South network and Last night got my hands on a Desire. The root was tricky but my friends desire is running Cyanogenmod no problem
Note: I take no resposability if you brick your phone an/or any other devices. This is just how i did it.
Instructions:
1: Download unReVoked Rooting tool. Click Here
(This tool works best if you are on linux ubuntu, windows users must install HTC Sync for the ADB Drivers)
2:Linux:
>Extract reflash, Open Terminal, Place your desire in Charge Only Mode with Debugging enabled.
> Plug in the phone and give it a few seconds to be reconized fully.
> In terminal type: cd /path/to/unrevoked then chmod +x reflash then sudo ./reflash and finally
> If it asks you for a password, use your root/user password. Unrevoked should start working and detect the phone.
Windows:
>Again Phone must be in Charge Only Mode with Debugging Enabled.
>Download the unrevoked package, Run the EXE. If you have HTC Sync installed it should detect the phone.
>Works same as Linux, Patience is a virtue.
(DO NOT CLOSE THE PROGRAM UNTIL IT SAYS ITS DONE!!. YOU WILL BRICK YOUR ****)
3. Unrevoked will begin working its magic, Your phone will reboot about 2-3 times. Be Patient!
> When its all over you will be brought to the recovery menu. (Green writing)
> Ours spit out some error code, but i restarted the phone and re entered recovery mode by holding down (Vol Down + Power)\
>You will be brought to a white screen HTC Labeled, Wait for hoot then do volume down to recovery, Push power.
4. After you have re-entered, Go down to manage and backup to Backup your stock ROM.
>Push back after the process has completed.
> Wipe the Device, then press back
> Go to mount and unmount storage.
> Mount your storage card to the computer.
5: After you have your phone plugged in make a folder on the memory card called Roms and Kernels (Whatever you prefer really).
> Go download the latest nightly/stable rom from the BravoC thread.
Click here for BravoC Roms
6:After download, Place the zip into the memory card in the Roms and Kernels folder i asked to make.
> On the android, when the file is done copying, unmount the memory card from the pc.
> Then in recovery menu, install zip file.
> Choose from SD Card
> Go to Roms and Kernels Folder.
> Select the file you downloaded.
> Click yes and enjoy!
7. You can download the Google Addon for your desire Here
YOU HAVE SUCCESSFULLY ROOTED and flashed YOUR DESIRE, This works on Cellular South, US Cellular, and other BravoC Desires with the 0.98 Hoot.
Don't forget to say thanks!
I have been looking to do this for a long time. And it worked great, the only problem is I don't understand the rom.
in the second step when it says:
> If it asks you for a password, use your root password. Unrevoked should start working and detect the phone.
you should use your user password, not the root password.
(of course your user must be a member of the sudoers group)
No need for passwords. But wish I had my HTC Clock and Calendar back.
You lose some you gain some buddy. there is a clock, look up fancy widget 1. 3 apk in your google box. and you can get it free.. Not gnna post a link cause of the rules. but its the ported HTC clock.
Thanks, but didn't care for that clock, saw one for $2 but couldn't get it to display so I uninstalled it. I know about "Win some, loose some" After all I have had a WinMobile phone for a couple years. And started flashing ROM's since the Touch Pro. My problem is, by the time I find a perfect ROM, I upgrade to a different phone. Did that with the TP1, and again with the TP2. Now the search begins again with the Desire. Actually the only problem I had with the stock 2.1 rom was that I kept running out of room. But thanks for the help and I am off again to find the perfect CDMA ROM!!!
awesome! just got my desire last night. to be sure after i root i will lose clock and calender? also (sorry, maybe a noob question) i like the sence, wasnt a big fanof AOSP and i notice all the Rom's here seem to be for GSM not CDMA. if i was to root and run the stock 2.1 and get rid of all the junk apps in it would that be possible? and lastly, does anybody know if there is a RUU for Csouth's desire incase i need to go back to original like we could with the hero?
leadfoot9281 said:
awesome! just got my desire last night. to be sure after i root i will lose clock and calender? also (sorry, maybe a noob question) i like the sence, wasnt a big fanof AOSP and i notice all the Rom's here seem to be for GSM not CDMA. if i was to root and run the stock 2.1 and get rid of all the junk apps in it would that be possible? and lastly, does anybody know if there is a RUU for Csouth's desire incase i need to go back to original like we could with the hero?
Click to expand...
Click to collapse
1. You shouldn't lose clock and calender.
2. After you root, install Titanium Backup. It will allow you to uninstall those apps you don't want.
3. No RUU's available for CDMA at this time. Make sure you do a nandroid backup immediately after rooting
uhh buddy there is a RUU out for it. Thats what the recovery menu basically is, the installer for the zip file. Cyanogen Mod is the ROM. To keep your Cellular South ROM you just backup like the instructions say, if you ever want to go back you Wipe the device and restore the image from your SD Card. Theres a link to Cyan in the main post. RC1 Came out yesterday!
[SP]JESTER said:
uhh buddy there is a RUU out for it. Thats what the recovery menu basically is, the installer for the zip file. Cyanogen Mod is the ROM. To keep your Cellular South ROM you just backup like the instructions say, if you ever want to go back you Wipe the device and restore the image from your SD Card. Theres a link to Cyan in the main post. RC1 Came out yesterday!
Click to expand...
Click to collapse
when i said RUU i meant a stock RUU put out by Csouth just like they gave us for the hero. it would put your phone back exactly like it was when you took it out of the box so if you needed to take it back to the store for whatever reason you could simply use it to go back to original.
ok guys one more question, i got root just fine. gonna keep running my stock rom but when i installed titanium backup (never used it before) it said busybox not installed and i dont have root access. i do have root cuz shoot me is working. i searched busybox in market and it says wont work for the desire yet.. any ideas? i ran into this problem with SU on my hero and had to change to the chainsDD version of SU. could this be the same thing?
ALSO: trying to use ADB and it says permission denied.
EDIT . Spoke to soon and did unrevoked forever and seems to all be working now.
Hi,
I am new to this sort of thing. I just got my phone and I am following this guide and I am thinking about trying it on my phone. Here's what I've got:
HTC Desire
Running Android 2.1
Alltel is my service provider
This is the information I get when I boot up my phone while holding the "back" button:
Bravoc DVT2 Ship S-ON
HBOOT-0.98.0000
MicroP-051e
Touch Panel-SYNT0101
Radio-2.05.10.08.11
Jul. 5, 2010, 19:14:11
Will this guide work with my phone?
The sole reason I'm wanting to do this is because I want to use a Wii remote with emulators on my phone. I am aware that there is an Android app that will do so, but that app doesn't work with phones that use HTC's "sense". I'm also aware that there are certain third-party wireless bluetooth controllers, but don't want to use them. So, I've been told that my only option is to root the phone so that I can have a custom ROM on it. If there is another way to do this without rooting, I'd love to know what that is.
Any information pertaining to any of this would be very helpful. Thanks in advance.
hovage said:
Hi,
I am new to this sort of thing. I just got my phone and I am following this guide and I am thinking about trying it on my phone. Here's what I've got:
HTC Desire
Running Android 2.1
Alltel is my service provider
This is the information I get when I boot up my phone while holding the "back" button:
Bravoc DVT2 Ship S-ON
HBOOT-0.98.0000
MicroP-051e
Touch Panel-SYNT0101
Radio-2.05.10.08.11
Jul. 5, 2010, 19:14:11
Will this guide work with my phone?
The sole reason I'm wanting to do this is because I want to use a Wii remote with emulators on my phone. I am aware that there is an Android app that will do so, but that app doesn't work with phones that use HTC's "sense". I'm also aware that there are certain third-party wireless bluetooth controllers, but don't want to use them. So, I've been told that my only option is to root the phone so that I can have a custom ROM on it. If there is another way to do this without rooting, I'd love to know what that is.
Any information pertaining to any of this would be very helpful. Thanks in advance.
Click to expand...
Click to collapse
Rooting is the only way to flash a custom Rom and yes unrevoked will work with your hboot. Not sure about any of the wii stuff your talking about tho.
Sent from my HTC Desire CDMA using XDA App
Thanks. And one other question I forgot to ask: Suppose I do this and an update to android 2.2 comes out for my phone. What should I do then?
If they give you a ruu just do it like normal, but as soon as they do cone out with a ruu for it whether its uscc or cellular south, there will be a custom Rom made from it.
Sent from my HTC Desire CDMA using XDA App
Fail
unrevoked "fails to push recovery image"
any advice?
blind_fury6342 said:
unrevoked "fails to push recovery image"
any advice?
Click to expand...
Click to collapse
Check the MD5 checksum for the Reflash_Package.exe
Most likely a corrupted installation.
I have the same phone/hboot/ etc...
I was able to root with unrevoked, no problem. I did get an error in the recovery at the end but per this guide, that seems to be normal.
I was able to run a backup in nandroid, which also worked, but I noticed S-on didn't change to S-off. Is this normal for this phone? Should I try rerunning unrevoked?
dills2214 said:
I have the same phone/hboot/ etc...
I was able to root with unrevoked, no problem. I did get an error in the recovery at the end but per this guide, that seems to be normal.
I was able to run a backup in nandroid, which also worked, but I noticed S-on didn't change to S-off. Is this normal for this phone? Should I try rerunning unrevoked?
Click to expand...
Click to collapse
I had this same issue. I did some research and there is a thread on unrevoked wiki that has an updated unrevoked-forever.zip to flash that gives us successful S-off. There seems to be a problem with S-off ing this route though. After it was complete, the APN info was gone and MMS settings were blank. I used APN backup/restore to put APN info back in, but still would not send/receive. I had to restore MMS via Goldcard, which changed back to S-on. Any ideas?
Since this seems to be the only generic CDMA Desire thread, I have some questions for other CDMA Desire owners. First, the only rom I can find with everything working is CM, but not sure I like the way it looks. I'm looking for a Sense rom. Anyone running a stable one? Second, I have found a rom called Ultimate Droid 2.3 and 2.4 for CDMA desire that looks worth trying. Anybody running it or tried it yet? 3rd, is there any other good forums specifically for CDMA desire? I am sick of having to weed through the billions of GSM threads to find a CDMA one...
link to Ultimate Droid roms: http://theultimatedroid.com/forum/index.php?/forum/33-htc-desire-releases-cdma/

[Q] Quasi-Bricked?

Hello! I'm a long-time lurk and this is my first post. Why? Because you folks at XDA are extremely knowledgeable and very helpful! I actually enjoy reading the forums and usually can find my answer using search. Call me a masochist, I guess. I just wish I had the chops to develop and not just be a continuous noobish sponge. I have successfully rooted my own Inspire with Bubby’s method and have flashed several radios and ROMs, no problem (knock on wood).
Anywho, I have searched and have seen similar issues to mine, but I have what I consider a more unique problem (which, if I’m wrong, I’m sure you fine folks will let me know). I attempted to root my brother’s Inspire over the weekend and it is currently showing a black screen with three vibrations and amber light (If I try to go to Hboot manually, I get five whole vibrations with a green light). I can, though, pull the battery for 5 minutes or so, then the phone will boot normally. Although I think it’s on the downgraded ROM, because it shows the funky AT&T splashscreen instead of HTC. What I did was attempt root with Bubby’s and got stuck at the boot screen when the phone was trying to flash the PD98IMG.zip (downgrade I believe) after making the goldcard. It would show that it was trying to read the zip, however I never would get the “volume up to upgrade” option. I tried this three times. When that failed, I tried rooting with the Ace Hack Kit and after creating the goldcard image, when the script tried to reboot the phone to install the downgrade, I got the black screen, amber light with the 3 vibrations. My problem is that I don’t have root, can’t get to recovery from the Hboot screen (shows red exclamation with triangle) and was unable to install Clockworks Mod thru ROM manager because I’m not rooted, so no SuperUser privileges.
What can I do at this point? Maybe off base, but I believe I have somehow corrupted the boot partition or the like, including screwing up Hboot. Is it possible to fix this if I am not able to reboot without pulling the battery? I have tried going thru Bubby’s and the Ace kit again, but always fail when the phone reboots.
Thanks for your help!
I am far from an expert, or even a novice, but to me it sounds like you have a corrupted download for the bubbys one click.... Have you checked the Md5 on the downloaded file?
Sent from my Inspire 4G using XDA App
I could lie and say yes, but no I didn't check md5 the first go around (although I did the 2nd time I reinstalled, after it screwed up). I did have all antivirus programs uninstalled and firewall turned off.
It does sound like you got the downgrade rom without root. Go back to the hack kit. With the gold card in the phone, turn on usb debugging and connect to the pc in the charge only mode. Run menu number 3 in the hack kit.
Sent from my Desire HD using Tapatalk
@OP:
Follow the files and instructions in this post to get back to stock so u can start fresh. I followed these to get back to stock only today evening, and it worked.
--------------------
TO RETURN TO STOCK:
Make sure you S-ON (if able) BEFORE you Unroot. The S-On tool needs root permissions to function.
--------------------
Turn the phone on, connect to computer, and perform step 1. Make sure USB debugging is enabled.
Step 1 (S-On):
Run Bubby323's S-On tool: S-On Tool
Step 2 (STOCK ROM in ZIP FORMAT):
Place this .zip file on the root of your SD card. Disable fast boot in settings > applications. Turn off your phone. Hold down the volume down button and the power button at the same time. The phone will reboot into hboot. It will load the ROM automatically. Follow the steps to flash the ROM.
http://www.multiupload.com/JELMZNSKDF
I did this like a couple hours back, and mine's back to stock.
Note: I consolidated the links here from various posts on this forum.
Diablo: Was posting the reply below, when I saw your message. Would you still recommend I follow your steps to unroot, return to stock and run hack again?
Update: Well, I went thru Bubby’s root process again and was able to get the phone rooted (had to pull battery and wait 4 minutes when it needed to reboot). And I have confirmed root was successful. I also used Bubby’s fix to Eng S-Off (couldn’t hurt, right?). The phone now has the latest Android Revolution with Sense and the radio has been flashed (including full wipe and EXT4 wipe). However, it STILL won’t reboot correctly. I can boot directly into Clockwork from ROM Manager, but if I try to reboot normally (hold down power button and select restart), I get the black screen, amber light and 3 vibrations. Again, pull battery and wait 4 minutes and either power button to boot normally or power and volume down to get to Hboot works fine and goes to Clockwork from Hboot fine also. I guess I can keep up with the batter pull only when I have to manually restart, but WTH? There has got to be a fix for the reboot issue. Any ideas?
fernandezhjr said:
It does sound like you got the downgrade rom without root. Go back to the hack kit. With the gold card in the phone, turn on usb debugging and connect to the pc in the charge only mode. Run menu number 3 in the hack kit.
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Thanks, but tried that earlier on and couldn't continue on with steps in hack kit.
ogarlen said:
...I also used Bubby's fix to Eng S-Off (couldn't hurt, right?)...
Click to expand...
Click to collapse
Well, actually, wrong, it could hurt. I'm not saying that's the cause of your problems, but you really should've read up a little more before clicking on stuff so nonchalantly.
Eng s-Off means the engineering bootloader. If that process were to fail while in the midst of performing it on your phone, it would most likely hard-brick it.
Not to mention it's unnecessary. It was only included in that rooting method at the time for flashing radios, I believe, and since then a safer method for doing so has come into standard usage that doesn't require eng s-Off.
It's also one method of resolving the cwr blackscreen people were having, where you're actually in cwr, but the screen is black so you can't see what your doing. Not the same black screen your seeing, I don't think, because you're able to at least get into cwr.
ogarlen said:
Thanks, but tried that earlier on and couldn't continue on with steps in hack kit.
Click to expand...
Click to collapse
The vibrations with the blinking led, I have seen a few posts with this. Sadly, I haven't seen anyone post a fix yet.
Sent from my Desire HD using Tapatalk
Fernandezhjir: I understand your sentiment, however my situation does seem to be a little different than the other posts, so there may be hope yet.
Scott: You're absolutely right (as if you need me to confirm that) that it could hurt. My sarcasm didn't come over very well without a wink-smiley or the like. As I mentioned before, I have read the forums and the other posts on the difference between radio s-off and eng s-off and how dangerous it can be. Actually Bubby's program fairly adequately describes that taking that step can possibly brick your phone and when you should consider taking the risk. I was desperate and dumb and poking fun at myself in my post.
Any advice with my current situation? Everything on the phone is working fine unless I try to normal restart, then I get the amber light with 3 vibrations. Again, battery pull for 4+ minutes then resinsert and power works and I can get to Hboot and Clockwork okay.
ogarlen said:
Fernandezhjir: I understand your sentiment, however my situation does seem to be a little different than the other posts, so there may be hope yet.
Scott: You're absolutely right (as if you need me to confirm that) that it could hurt. My sarcasm didn't come over very well without a wink-smiley or the like. As I mentioned before, I have read the forums and the other posts on the difference between radio s-off and eng s-off and how dangerous it can be. Actually Bubby's program fairly adequately describes that taking that step can possibly brick your phone and when you should consider taking the risk. I was desperate and dumb and poking fun at myself in my post.
Any advice with my current situation? Everything on the phone is working fine unless I try to normal restart, then I get the amber light with 3 vibrations. Again, battery pull for 4+ minutes then resinsert and power works and I can get to Hboot and Clockwork okay.
Click to expand...
Click to collapse
Heh. Now that you explain it, I can see the sarcasm. I'm usually good a picking up on it, but you know how these internet textual posts go....smilies are crucial...
As to your problem, there seem to be a few posts in recent days describing the led/vibrations type of symptom.
I don't know if they're interrelated or not. I don't have an answer, but I'm curious and will drop in if I manage to come across any pertinent information.
Thanks for the replies! I will continue to research and update this thread if I find a solution. I really believe that it has something to do with the startup processes or boot cache or some other $10 phrase related to what happens when the phone is attempting to startup normally. I appreciate all help.
Sent from my Inspire 4G using XDA App
Just wanted to add a quick update for anyone searching that comes across this post: The phone in question is now working flawlessly (knock on wood). Restarting, power down and battery pulls work with no problems (no vibrations or flashes). I am honestly unsure what I did to cause this error or what the resolution was and can only speculate. Since my last post, I have made a Nandroid backup and flashed a couple ROMs (namely AR with Sense, then Virtuous Unity with full wipes in between), so I assume that somewhere in there the corrupted boot files (or whatever) were corrected. All's well that ends well...
Here is just something to add to everyone's good advice that you received. Search for the RUU in the development section. It can fully restore your phone back to stock out of the box condition. In situations such as this it is worth having saved on your computer.
Wolf_2 said:
Here is just something to add to everyone's good advice that you received. Search for the RUU in the development section. It can fully restore your phone back to stock out of the box condition. In situations such as this it is worth having saved on your computer.
Click to expand...
Click to collapse
Not quite true. If you've rooted and have S-OFF, that will survive a complete RUU update. You have to S-ON your device before applying the RUU if you want true "out-of-the-box" restoration.
seems like you got yourself a good taste of rom flashing issues. that's a good thing. i know that you have everything working flawlessly now, BUT i would still HIGHLY recommend that you download the Super Wipe script from the Android revolution thread and use that to completely wipe and format your partitions, then do a FULL wipe through clockwork and then install whatever ROM you would like. but i cant stress enough, MAKE SURE that the Md5 sums match always. this can be the difference between a working rom and a bricked phone. also i would like to add that through my experience i usually find that the first time you root the inspire, the very first rom you install on it almost always has issues. that's how it is for me atleast. Ive rooted plenty of Inspire's and all of them have had some sort of issue on the first flash. and as always, follow the directions per rom to the T or else it might not work.
P.S. Some roms run better with matching Radio and RIL. flashing these is AWLAYS good practice to get your phone to tunr the best possible.
Wolf_2 said:
Here is just something to add to everyone's good advice that you received. Search for the RUU in the development section. It can fully restore your phone back to stock out of the box condition. In situations such as this it is worth having saved on your computer.
Click to expand...
Click to collapse
Gene Poole said:
Not quite true. If you've rooted and have S-OFF, that will survive a complete RUU update. You have to S-ON your device before applying the RUU if you want true "out-of-the-box" restoration.
Click to expand...
Click to collapse
Thats why I posted the full steps in the guide , to s-on and ruu back to stock. On a side note bubbies s-on tool does not always work.
On another side note, Genepoole would be interested in wrighting a script for the s-on/return t stock process to make it a little more automated? The steps right now are flashing back to stock then re rooting, then entering gfree s-off on then re running the ruu.
mudknot2005 said:
On another side note, Genepoole would be interested in wrighting a script for the s-on/return t stock process to make it a little more automated? The steps right now are flashing back to stock then re rooting, then entering gfree s-off on then re running the ruu.
Click to expand...
Click to collapse
I have actually considered this. The current methods require a complete downgrade just like rooting when all you really need for gfree to work is the radio and kernel from the downgrade ROM.
Gene Poole said:
Not quite true. If you've rooted and have S-OFF, that will survive a complete RUU update. You have to S-ON your device before applying the RUU if you want true "out-of-the-box" restoration.
Click to expand...
Click to collapse
You are correct. I should have re phrased that differently. I know that S-Off would survive the RUU procedure so I should have said "almost out of the box". The RUU is still a very handy thing to have.
Gene Poole said:
I have actually considered this. The current methods require a complete downgrade just like rooting when all you really need for gfree to work is the radio and kernel from the downgrade ROM.
Click to expand...
Click to collapse
Please, sir.
Seriously, this would be, imo, a profound contribution to this phone.

[Q] Backing up stock bootloader/recovery

I'm getting a Desire S soon and was looking up some information about rooting and flashing custom ROMs. If I'm correct, I need to use Revolutionary (or similar) to put my phone in the S-OFF state.
Is it possible to make a backup of the original rom, bootloader and recovery in case I need to return to stock for warranty purposes?
I've read something about needing a RUU to revert, is it possible to generate one from the stock enviroment? (if necessary, rooted with GingerBreak.)
The only real guide to returning to S-ON I could find (see below) just says discontinued, and as far as I can tell, there's nothing about it in the stickies.
I apologize in advance if I missed anything in the stickies, there's a lot of information to go through.
http://forum.xda-developers.com/showthread.php?t=1187231
Actually, you've got it licked. Unless you've got an incredibly slow and limited connection (like me) an RUU is the way out. Of course, I did mine the easy way:
- S-OFF using a tool of your choice
- Flash a recovery (started with CWM, now on 4EXT Touch)
- Back up the phone via recovery
- Keep a copy of the recovery on your PC or external drive
That way, you're certain to have a ROOTED system to return to should you ever change your mind - or should things go horribly wrong.
By the way, the RUU won't return you to S-ON (why on earth would you want to S-ON?!). But I have the files and can give you a link should you really want to consider S-ON (bearing in mind you could accidentally brick your phone if you take a wrong turn while in S-ON mode). Unless you want to re-sell your DS ...
You can't back up stock anything. To allow you to back up anything you need to break the very thing you're trying to back up. Try backing up your computer in the state before you install a backup program on it - doesn't make a lot of sense, does it?
RUU is the thing you're looking for, that contains all the system in stock form. This is what it's for.
Saipro said:
Actually, you've got it licked. Unless you've got an incredibly slow and limited connection (like me) an RUU is the way out. Of course, I did mine the easy way:
- S-OFF using a tool of your choice
- Flash a recovery (started with CWM, now on 4EXT Touch)
- Back up the phone via recovery
- Keep a copy of the recovery on your PC or external drive
That way, you're certain to have a ROOTED system to return to should you ever change your mind - or should things go horribly wrong.
By the way, the RUU won't return you to S-ON (why on earth would you want to S-ON?!). But I have the files and can give you a link should you really want to consider S-ON (bearing in mind you could accidentally brick your phone if you take a wrong turn while in S-ON mode). Unless you want to re-sell your DS ...
Click to expand...
Click to collapse
Thanks simple and clear.
Thanks for the help! The information about returning to S-ON was mostly hypothetical. Hi (my provider) has cooked up some scheme involving the 'leasing' of phones and I wanted to know if it was possible to completely return it to it's stock state, if it ever becomes necessary.
s0und0ut said:
Thanks simple and clear.
Click to expand...
Click to collapse
If only you would click the "Thanks" button instead. Thanks
Hellrespawn said:
Thanks for the help! The information about returning to S-ON was mostly hypothetical. Hi (my provider) has cooked up some scheme involving the 'leasing' of phones and I wanted to know if it was possible to completely return it to it's stock state, if it ever becomes necessary.
Click to expand...
Click to collapse
returning to stock s-on is pretty easy,you just replace the hboot with the hboot-eng one(search!) then flash the ruu!
djisgod said:
returning to stock s-on is pretty easy,you just replace the hboot with the hboot-eng one(search!) then flash the ruu!
Click to expand...
Click to collapse
Most often, it doesn't come off that easy. You'd first have to return to stock recovery. Or end up with some weird recovery screen which you can't get past. Repackaging the stock recovery (from any RUU) as a PG88IMG.zip, then flashing it would get you out of the dilemma (flashed a hundred things that way as I've an aversion for adb/fastboot commands. And you can't accidentally flash the wrong stuff unless you truly work hard at it). Solved!

Categories

Resources