[Q] Splash Screen Freezing on Custom ROMS? (S-ON Unlocked doubleshot) - T-Mobile myTouch 4G Slide

With the kind assistance of Coug76 (who pointed me to Hasoon's fantastic rooting kit!) I was able to get SuperUser access to my unlocked S-ON Doubleshot. Hooray!
Now I'm trying to install a new ROM. I tried the latest CM9 and I also tried Pyr-o-ice 1.1.1. Both times everything seemed to be going well, but on reboot I just got the splash screen. Most recently I let it sit for 12 minutes (I timed myself, so I wouldn't be tempted to lose patience!) just in case... but it seems to be truly frozen.
The first two times I went through Clockwork, copying the .zip file to the sdcard and then choosing "install from sdcard". The most recent time I went through Recovery, making sure to wipe the data first.
After that didn't work (splash screen for twelve minutes) I vaguely remembered someone saying somewhere (I've read a lot of posts here over the last 48 hours!) that HTC users need to flash the boot image separately. I figured it was worth a try, although I'm not sure if Clockwork does that on its own or not, so after installing from the zip file and trying to boot, I copied the boot.img from the pyr-o-ice .zip file onto the sdcard and then I went into fastboot and typed "fastboot flash boot boot.img".
Same behavior--splash screen still frozen. I also see that the "Read Before Posting" thread says "people who used HTC unlock and have s-on will have trouble flashing roms that are not gingerbread based". I did use HTC's unlock tool, so maybe that's my problem? If so, could someone recommend a good gingerbread ROM for me?
Finally, after restoring from a good nandroid backup (I've used it before, earlier today) the screen is still frozen. Is there any chance that this is because I flashed the other boot.img? I would have thought that the nandroid restore would have fixed that?
Thanks!
-=Benjamin

Oh, I just realized that I wasn't flashing the boot.img on my sdcard, I was flashing whatever random boot.img was sitting in the same folder as fastboot. Ok, fair enough. But the rest is still a mystery, and my nandroid recovery still isn't booting.

silly noob

Oh, no question about it! I'm just glad that I knew enough to get the damn thing working again.
But in the future I do want to try custom ROMs, for sure. So, is it true, then, that before I load a ROM via Clockwork, I need to first flash the boot.img from that particular ROM? If so, it makes Clockwork's ROM Manager seem... not very useful.
Thanks!

whirr said:
Oh, no question about it! I'm just glad that I knew enough to get the damn thing working again.
But in the future I do want to try custom ROMs, for sure. So, is it true, then, that before I load a ROM via Clockwork, I need to first flash the boot.img from that particular ROM? If so, it makes Clockwork's ROM Manager seem... not very useful.
Thanks!
Click to expand...
Click to collapse
Clockwork being on your phone makes it much easier to boot into fastboot and recovery modes instead of using the power and volume down method. It's also good for backup and recovery purposes. I was too much of a chicken to try it but if you're feeling brave, you can use the juniptobear method (hope I spelled that right) to gain S-Off. The link below is for the all in one S-Off kit by Hasoon2000 and will take you where you need to go to do this. If you do this, you won't have to use that extra step (flashing the boot.img file) to load a new ROM.
http://forum.xda-developers.com/showthread.php?t=1696373

eparico said:
Clockwork being on your phone makes it much easier to boot into fastboot and recovery modes instead of using the power and volume down method. It's also good for backup and recovery purposes. I was too much of a chicken to try it but if you're feeling brave, you can use the juniptobear method (hope I spelled that right) to gain S-Off. The link below is for the all in one S-Off kit by Hasoon2000 and will take you where you need to go to do this. If you do this, you won't have to use that extra step (flashing the boot.img file) to load a new ROM.
http://forum.xda-developers.com/showthread.php?t=1696373
Click to expand...
Click to collapse
I have S-Off (as it says in hboot) and I got the splash screen freeze.
I have not yet flashed the boot, maybe it says S-Off even though something reset it to S-On? Anyway I am going to flash the boot.img to see if it fixes the splash screen freeze issue (If it does then maybe my hboot is wrong).
---------- Post added at 04:05 AM ---------- Previous post was at 03:55 AM ----------
UPDATE 1:
Flashing the boot.img did not seem to make a difference it did "Okay" but no difference in the splash freeze.
F:\Android\ROM\Unziped>fastboot flash boot boot.img
< waiting for device >
sending 'boot' (4058 KB)... OKAY [ 0.858s]
writing 'boot'... OKAY [ 7.424s]
finished. total time: 8.283s
I am making a n00b mistake some ware but I can't find it. The boot.img on my F: drive is the correct one, even though I should not need to do that since i have S-Off.
UPDATE 2:
FOUND IT, Ok the noob mistake was that I did the 'wipe' only on the cache and I needed to do the 'wipe' on the factory reset 'and' cache.
Ha ha stupid problems... Feels good though now its running. g-apps.... *worked like a charm! Its all working good now.

Related

CWM won't stick...Even with locked bootloader

I rooted according the directions found here: http://www.droidfiles.us/nexus-s-4g/root-nexus-s-4g/ after getting a new Nexus S 4G.
Even after locking the bootloader. It goes to the Android-with-box then to the Exclaimation-point-inside triangle. When I volume-up and power-button from that screen, an "Android Recovery <3e>" comes up...
Does anyone know what might be going on? And how do I get my custom recovery to stick?
Well, that's my post, so ill try to help. First, and don't take this the wrong way, but did you follow those instructions to a T? When you boot into bootloader, your pushing CWM to you phone with the fastboot command?
Sent from my Nexus S 4G using XDA App
mikeyinid said:
Well, that's my post, so ill try to help. First, and don't take this the wrong way, but did you follow those instructions to a T? When you boot into bootloader, your pushing CWM to you phone with the fastboot command?
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
No offense taken...it's a valid questions since humans have trouble following directions.
To answer your Q, yes, I followed it to a tee. I'm going to retry now...from scratch. Gonna load the stock imgs and go from the beginning...
TonyArmstrong said:
No offense taken...it's a valid questions since humans have trouble following directions.
To answer your Q, yes, I followed it to a tee. I'm going to retry now...from scratch. Gonna load the stock imgs and go from the beginning...
Click to expand...
Click to collapse
Apparently alot of people have this issue, me included. I seen some posts about using root explorer to change the name of the recovery image if it shows up in system /ext. Sounds crazy but I hear it doesn't show up on all phone's. IV come to terms with having to fastboot every time I flash but I'd love to see a fix. Have you tried Amons recovery?
TonyArmstrong said:
No offense taken...it's a valid questions since humans have trouble following directions.
To answer your Q, yes, I followed it to a tee. I'm going to retry now...from scratch. Gonna load the stock imgs and go from the beginning...
Click to expand...
Click to collapse
Have you flashed recovery through Rommanager when your phone boots up?
You have to flash a non-stock kernel, the recovery gets overwritten on reboot. So if you flash CWM and reboot without flashing a custom kernel you will be back to stock recovery.
Edit: oops maybe I was wrong lol, maybe it isnt the kernel. im assuming you flashed the recovery in fastboot?
mbh87 said:
You have to flash a non-stock kernel, the recovery gets overwritten on reboot. So if you flash CWM and reboot without flashing a custom kernel you will be back to stock recovery.
Edit: oops maybe I was wrong lol, maybe it isnt the kernel. im assuming you flashed the recovery in fastboot?
Click to expand...
Click to collapse
No, I dont think your wrong bro. It makes sense. Ill test your theory soon.
Tony, when you push CWM, are you able to boot into recovery by hitting volume down twice to recovery and hitting power? If so, I suggest you flash this ROM. Its stock rooted and you will not have problems with CWM sticking. You dont even have to wipe to flash it...
I've read on some methods for rooting that there is a file /system/etc/install-recovery.sh (or something like that, should be able to find it by mounting system in recovery and adb shell ls /system/etc then using adb shell rm -r /system/etc/install-recovery.sh).
Though after I fastboot flashed the recovery, booted into recovery, did a nandroid, I formatted /system before I flashed CM7, so that would've killed the file anyways.
david1171 said:
I've read on some methods for rooting that there is a file /system/etc/install-recovery.sh (or something like that, should be able to find it by mounting system in recovery and adb shell ls /system/etc then using adb shell rm -r /system/etc/install-recovery.sh).
Though after I fastboot flashed the recovery, booted into recovery, did a nandroid, I formatted /system before I flashed CM7, so that would've killed the file anyways.
Click to expand...
Click to collapse
I just had CWM, never had any issues. Im not sure what dictates whether that file is there or not. Im guessing that since tony is so quiet though he got it figured out..
whats amazing is i dont have this script and its one of the things holding the one click up :x
also its part of init.rc so technically a new kernel would.. in theory wipe that out...
mikeyinid said:
Have you flashed recovery through Rommanager when your phone boots up?
Click to expand...
Click to collapse
I did flash CWM through Rom Manager. That didn't work the first few times. It stalled...
mikeyinid said:
Tony, when you push CWM, are you able to boot into recovery by hitting volume down twice to recovery and hitting power? If so, I suggest you flash this ROM. Its stock rooted and you will not have problems with CWM sticking. You dont even have to wipe to flash it...
Click to expand...
Click to collapse
I got it to stick -- or at least i thought I had it. I followed the initial instructions provided in a previous thread. And per the instructions, I download Rom Manager and I installed CWM through it (again).
I'm going to wipe my phone fully -- reinstall the base 2.3.4 with the the stock recovery, via the IMG files for GRJ22 and start over...See what happens then.
Wait, I'm confused. Why would you flash stock images when your already stock? If you follow the instructions in the link you posted in the op there is no reason you shouldn't be rooted. Have you actually even booted into recovery?
TonyArmstrong said:
I got it to stick -- or at least i thought I had it. I followed the initial instructions provided in a previous thread. And per the instructions, I download Rom Manager and I installed CWM through it (again).
I'm going to wipe my phone fully -- reinstall the base 2.3.4 with the the stock recovery, via the IMG files for GRJ22 and start over...See what happens then.
Click to expand...
Click to collapse
Sent from my Nexus S 4G using XDA App
I realllyyy don't suggest flashing a recovery with rom manager. I'm not bashing ROM Manager, I'm a paid user, but the way that it flashes recoveries is unsafe. I've had it almost brick my Evo and I've seen it brick other phones.
Just use fastboot... if you can't get that working, you probably shouldn't be messing with the phone.
mikeyinid said:
Wait, I'm confused. Why would you flash stock images when your already stock? If you follow the instructions in the link you posted in the op there is no reason you shouldn't be rooted. Have you actually even booted into recovery?
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
I'm rooted successfully. I feel more comfortable (with recovery acting flaky) with unrooting and starting over from scratch...
Call me kooky, but a bone-stock unrooted phone with no user data, no nothing, is how I got it, so why not return it to that state and start over. That's the only way I know to insure that whatever I do is not influenced by any data, bad file permissions, etc. that could hose rooting and installing recovery.
TonyArmstrong said:
I'm rooted successfully. I feel more comfortable (with recovery acting flaky) with unrooting and starting over from scratch...
Call me kooky, but a bone-stock unrooted phone with no user data, no nothing, is how I got it, so why not return it to that state and start over. That's the only way I know to insure that whatever I do is not influenced by any data, bad file permissions, etc. that could hose rooting and installing recovery.
Click to expand...
Click to collapse
OCD, I know the feeling lol. What got it to stick?
derekwilkinson said:
I realllyyy don't suggest flashing a recovery with rom manager. I'm not bashing ROM Manager, I'm a paid user, but the way that it flashes recoveries is unsafe. I've had it almost brick my Evo and I've seen it brick other phones.
Just use fastboot... if you can't get that working, you probably shouldn't be messing with the phone.
Click to expand...
Click to collapse
I used fastboot to install CWM initially (fastboot flash recovery recovery-xxxxx.zip -- can't remember the filename right now). The directions for rooting the NS4G state explicitly to use ROM Manager to flash the recovery to "make sure it sticks" after initially pushing it to the phone via fastboot.
It's obviously a hack, but apparently it works more often than it fails.
I'm a paid user of ROM Manager as well. I have to admit, it was fine to flash Amon Ra to my Evo. Since I'm new(er) to the NS4G, I'm going to defer to those with more expertise and follow the directions given.
TonyArmstrong said:
I used fastboot to install CWM initially (fastboot flash recovery recovery-xxxxx.zip -- can't remember the filename right now). The directions for rooting the NS4G state explicitly to use ROM Manager to flash the recovery to "make sure it sticks" after initially pushing it to the phone via fastboot.
It's obviously a hack, but apparently it works more often than it fails.
I'm a paid user of ROM Manager as well. I have to admit, it was fine to flash Amon Ra to my Evo. Since I'm new(er) to the NS4G, I'm going to defer to those with more expertise and follow the directions given.
Click to expand...
Click to collapse
well the "make sure it sticks" flashing with rom manager doesn't make any sense. the only way the recovery would be overwritten is if the ROM you flash over writes it or in fastboot
mikeyinid said:
OCD, I know the feeling lol. What got it to stick?
Click to expand...
Click to collapse
Yeah, I'm very anal when it comes to this kind of stuff...I was a developer for a little bit (Java middleware, then on to the front-end stuff) where regression testing was important. Sometimes, it's best to reload things piece by piece to see what breaks what. Then go from there.
I haven't gotten it to stick yet; gonna get some sleep and start over tomorrow. I used fastboot to push the stock boot, bootloader, system, recovery, and userdata IMGs a moment ago, and the phone is back to bone stock.

Desire s stuck after 2.3.5 update

i tried to update via phone (after the notification), but after green bar was full, my phone rebooted and stuck in white screen with htc logo... if i try to enter in recovery i see this
h*tp://i39.tinypic.com/xdxnc5.jpg
it seems to be s-off (i bought it used) ...what have i to do for make it work again??
tnx.. and sorry for my bad english
same problem here, help is needed!
A golden rule: never update OTA on a modified device (custom ROM even modified Stock one, custom Recovery, Revolutionary hboot!, etc.)
How to fix:
do not pull battery!
flash a custom recovery (e.g. 4EXT) with the fastboot command (search for a how-to)
reboot to recovery, wipe all partitions and install custom ROM
Ok, to late with the battery, have already pulled that one out!
I also have S-Off on my phone, really dont understand the how to fix a recovery??
And is it really neccessary to flash a new ROM for this?
An official release that screwes the phones up?
I think the general issue is that an 'Official' OTA upgrade should not screw up your phone - enough testing by HTC should make sure of that.
Hoever, if you have modified your phone (e.g. by rooting it, installing custom recovery etc) then you can not expect to blame HTC when their upgrade doesn't work as expected. They can't be held responsible for problems caused by modifications you make to the phone.
But all I have done is S-Off, I have not installed another ROM or anything else?
So the update should work I really think!
Can I install a custom recovery without have to be able to start the phone?
Akerhage said:
But all I have done is S-Off, I have not installed another ROM or anything else?
So the update should work I really think!
Can I install a custom recovery without have to be able to start the phone?
Click to expand...
Click to collapse
The OTA flashes a new hboot also.
If you S-OFFed with Revolutionary your hboot has to be version 6.98.000x. This hboot has a protection and cannot be overwritten. This is the point where the update process is interrupted. The result is a bootloop, because the new system is incomplete.
If you can boot to bootloader (hboot) you should be able to flash a custom recovery with the fastboot command (in the 4EXT Recovery thread there is an attachement - a zip file that contains recovery.img). Extract the archive and flash it with this command from cmd (there is a guide how to make fastboot working in my signature):
Code:
fastboot flash recovery {path to file on your PC}/recovery.img
If this works reboot to recovery, wipe all partitions and flash a custom ROM. Then your phone should be working again.
Then if you want the OTA flash a 0.98.2000 hboot, then use the 1.47.401.4 RUU (if you are using European unbranded) or the corresponding for your brand/region to return back to complete Stock and S-ON. Then you will be prompted to update and you will have the latest OTA on your device
Okay, I have now fixed the 4EXT Recovery and it is working!
Do I have to put a new ROM on the SD-card or is there another way to install a ROM (from cmd with the ROM on the computer etc?)
I dont have an adapter to the SD-card, but maybe I can put the ROM on the sdcard with a command in cmd aswell?
What ROM do you recommend to use? (sense, no sense doesnt matter)
Edit: I did a backup as well, thinking that I should do that...
Can you link to zip file you used for recovery i have exactly same issue and same software versions as you have.
@ Mooler. First of follow the guide that was posted here regarding the adb-drivers.
After that download this: http://forum.xda-developers.com/attachment.php?attachmentid=631186&d=1308596026
Then install that one as described with the cmd-command.
After that just put a custom ROM or a shipped ROM on the SD-card, wipe data/cache and install the ROM you want. That solved the problem for me!
Good Luck and thanks for the help I got here! Xda always delivers
Damn this phone! After hours of fixing with this problem!
I managed great, installed new kernels, radios, ROMs etc. And the first thing I did was to drop it on the floor so the whole damn display cracked!
Thanks for both of you.
I managed to restore the phone quickly after i got the correct recovery file. 30 mins and custom ROM was up and running. Good bye official update.
Akerhage: sad to here, it really was hours of reading and trying before you get it right.

Need help regarding root and custom ROM's

Hi guys, I had a little play around with my phone a while back before ICS came out and was a bit unsuccessful. From what I can gather, it was the Super CID part of the guide that I missed out, and when I installed the custom ROM it got stuck in a bootloop.
I was unable to sort this out in the short space of time that I had, so I gave it to a friend and he changed the hboot to 1.17.2008.
Currently the phone says S-OFF but no root detected through Titanium Backup. I am a little unsure about what I need to do next to either get it back to stock or at least to a point of being able to install a custom ROM.
Also I do have Clockwork Mod installed.
I installed Android SDK, and HTC sync to find out my CID and after a lot of forum searching I came to a point where i'm stuck now on which RUU I need.
I think this is the one that I need as I am with Vodafone UK and have the normal Sensation
RUU_Pyramid_Vodafone_UK_1.24.161.1_Radio_10.39.9007.00P_10.11.9007.09_M2_release_190798_signed.exe
I also read that the software version part of the RUU could be anything higher than what I already have on my phone, in this case it being Android 2.3.4 Software Version 1.50.161.1
If I am wrong then please point me in the right direction.
Am I right in thinking that I can install using CWM and this should sort it out, or am I missing a ton of stuff?
Hopefully someone will be able to help me out with this one.
P.S I am not too good at understanding some of the abbreviations and slang that you guys use so could you dumb it down for me please :silly:
OK:
For root look up SuperSU then you can install it through ClockworkMod, "Install Zip from SDcard".
If you're on 1.24.161 (I had also installed that) it doesn't seem to let you apply OTA.
For some RUUs look at: http://shipped-roms.com/index.php?category=android&model=Pyramid
I found and installed 1.27.161 then went through the OTA updates to get to 3.32.161 (Vodafone UK with ICS). I only did this to get a backup just in case I need to send it back.
If you have SuperCID you can install 3.32.401 or 3.33.401 which are WWE RUUs, i.e. unbranded so no Vodafone crap.
fastboot getvar cid ------------------------- to find out what you have
fastboot oem writecid 11111111 ---------- to write SuperCID
fastboot reboot-bootloader ----------------- restart bootloader
fastboot getvar cid ------------------------- check it's been written correctly
x.xx.161.xxxx == Vodafone UK == CID "VODAP001"
x.xx.401.xxxx == WWE == CID "HTC__001"
Of course both can be installed with Super CID.
As you have S-OFF you can install a custom ROM, CID is not important. However a couple of points to note:
i) Get the Superwipe scrips from the ARHD thread, This ensures a completely clean phone prior to installing a new ROM. The RUU process automatically does this.
http://forum.xda-developers.com/showthread.php?t=1098849
ii) You need to ensure that the firmware has been updated to the version recommended by the custom ROM, There is a thread "User Friendly Firmware" that you can look at to help on that. So you'l need to read the custom ROM thread to ensure you have the right version installed.
http://forum.xda-developers.com/showthread.php?t=1459767
Note that installing an RUU or Custom ROM will NOT remove S-OFF from your phone. However, if you install a new RUU you'll need to reinstall your custom recovery, ClockworkMod, via a PG58IMG.zip file is easiest. I'm assuming you know about the generic file PG58IMG.zip and its various uses.
You should try reading this: http://forum.xda-developers.com/showthread.php?t=1192300
It's a very useful step-by-step guide!
Thanks for the hasty response, had to leave for work so I have only just got chance to look at this.
If I have read this right then I write the "su-2.3.6.3-efgh-signed.zip" to my SD card and follow the relevant steps to get root.
Then optionally go through the process to get Super-CID and then download:-
RUU_Pyramid_Vodafone_UK_1.27.161.1_Radio_10.42.9007.00P_10.11.9007.15_M_release_191974_signed.exe
this should then enable me to receive the ICS OTA update that I have been getting the notification for, for ages
or
RUU_PYRAMID_ICS_HTC_Europe_3.32.401.5_Radio_11.69.3504.00U_11.22.3504.07_M_release_246089_signed.exe
And then I can write any custom ROM after this?
Hope you can understand this.
P.S I have done a backup into CWM just in case this goes wrong
Spalding89 said:
Thanks for the hasty response, had to leave for work so I have only just got chance to look at this.
If I have read this right then I write the "su-2.3.6.3-efgh-signed.zip" to my SD card and follow the relevant steps to get root.
Then optionally go through the process to get Super-CID and then download:-
RUU_Pyramid_Vodafone_UK_1.27.161.1_Radio_10.42.9007.00P_10.11.9007.15_M_release_191974_signed.exe
this should then enable me to receive the ICS OTA update that I have been getting the notification for, for ages
Click to expand...
Click to collapse
Yes
or
RUU_PYRAMID_ICS_HTC_Europe_3.32.401.5_Radio_11.69.3504.00U_11.22.3504.07_M_release_246089_signed.exe
And then I can write any custom ROM after this?
Click to expand...
Click to collapse
You don't need to install either to install a custom ROM. However, If you install this you'll automatically get the 3.32 firmware and radio. Then as long as the custom ROM has that as a requirement you're fine. Just need to SuperWipe then install.
The x.xx.401..... RUU has less bloatware, i.e. NO Voda crap.
I also found the 3.33.401..... RUU at: http://htcfanboys.com/download/rawdealer/?action=browse&folder=4141
If you just want a custom ROM, install the appropriate firmware (as detailed in the custom ROM's OP) from the XDA forum I mentioned then SuperWipe and install it through CWM.
MAKE SURE that you take regular Nandroid backups with CWM, just in case !!!!
Hope you can understand this.
P.S I have done a backup into CWM just in case this goes wrong
Click to expand...
Click to collapse
Thanks for the help
I now have successfully move over to ICS using the RUU that you posted the 3.33.401.1 version.
The only niggle I have now is that after installing Titanium Backup to restore my apps and data it says that I have no root? no SuperUser, and I can't seem to get into recovery, as if its not even there.
So I went through the process of downloading the appropriate file from this thread "http://forum.xda-developers.com/showthread.php?t=1192300"
and trying to get the phone to install it itself through the Vol down + Power way but it did nothing.
I then tried doing it the cmd method and it still doesn't work.
When I type in the command - "fastboot flash recovery recovery.img"
it comes up with " OKAY [ 0.341s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.342s"
I'm sure everything that I have done is right but if not then could someone please shed some light into this problem please
Thanks
Spalding89 said:
Thanks for the help
I now have successfully move over to ICS using the RUU that you posted the 3.33.401.1 version.
The only niggle I have now is that after installing Titanium Backup to restore my apps and data it says that I have no root? no SuperUser, and I can't seem to get into recovery, as if its not even there.
So I went through the process of downloading the appropriate file from this thread "http://forum.xda-developers.com/showthread.php?t=1192300"
and trying to get the phone to install it itself through the Vol down + Power way but it did nothing.
I then tried doing it the cmd method and it still doesn't work.
When I type in the command - "fastboot flash recovery recovery.img"
it comes up with " OKAY [ 0.341s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.342s"
I'm sure everything that I have done is right but if not then could someone please shed some light into this problem please
Thanks
Click to expand...
Click to collapse
You'll need to install recovery via the PG58IMG.zip method. Do a search for "PG58IMG-CWM5020.zip" or some such term. It'll need to be renamed to be exactly "PG58IMG.zip" on the root of the SD card. Then the next time you go into the boot loader it'll ask you if you want to install it. When it's finished it will ask you to press power to reboot, at this stage you either need to have deleted the file, renamed it to something like PG58IMG-CWM5020.zip or removed the SDcard or it goes in to a bit of a loop.
You should then be able to get into recovery and install SuperSU.zip as before.
I tend to keep a copy of the CWM in the PG58IMG.zip format on my SDcard.
The Power Vol- possibly isn't working as you have FastBoot enabled in setting. To make sure just pop the battery out, wait a few secs and try again.
EDIT:
Found one for you: http://forum.xda-developers.com/showpost.php?p=28365583&postcount=4509
Just checked the MD5 with my copy of PG58IMG-CWM5020.zip and it's exactly the same.
Thanks again
This worked great first try, it must have been the file I downloaded because this is the exact way that I did it before.
Now I will try to open recovery an write superuser.
Followed Step 3 of this thread - http://forum.xda-developers.com/showthread.php?t=1192300
And after installing Titanium Backup so that i could restore my backup, it comes up with the error message that i have no root.
What have I done wrong this time?
Installing SU is a straighforward install zip from within the custom recovery.
Did it come back with any messages. Step 3 is a little muddled, confuses nandroid backup with installing the zip.
i) Do a Nandroid backup first.
ii) Install Zip from SDcard
choose zip from SDcard
Yes - Install xxxxxx.zip
Osh Bosh should have root.

[Q] upgarde snaufu...

was running viperXL 3.2.5 and wiped and went to cm10.1 now i used goo manager to download xhata (sorry i butchered it) now i can only boot into spash screen and bootloader. i used fastboot to reflash twrp and still only boots to the custom spash... hboot 1.09 s-off..... im kinda lost here. should have syuck with viper, why screw with perfection.
What is xhata? Is it a rom?
I'm not sure we can install roms with Goo Manager on this phone.
If you installed a rom for the quad-core Tegra One X, your phone will not boot and you're lucky you didn't get a brick. You need to do a full wipe and reflash.
first off not a noob. it was the evita rom. i still have bootloader access and can get half way into recovery( spash screen then twrp spash...) then reboot into custom splash. it was the rom... http://forum.xda-developers.com/showthread.php?t=2075783 so if anyone has any ideas please help, just dont start with the usual u screwed up flashing roms i know better. and the odd part is after reflashing the recovery via fastboot i get Twrp spash before going back to the phone main splash and boot looping.... and yes im s-off
No need to be so defensive. If we don't know exactly what you flashed, all we can do is ask. Its not meant as an insult. But its always better to ask the seemingly "obvious" questions first, get them out of the way.
If there is a "usual thing" that gets mentioned, its because the mistake of flashing ROMs for the ENDEAVORU in fact happens so often. Downloading from GooManager is not a great idea either, and often a red flag that someone installed a ROM for the wrong version of the phone.
Did the phone operate properly when you were on CM10.1?
What version of TWRP, and what fastboot command did you use to flash it?
I asked the "usual" questions because:
-You have less than 100 posts. That's often a sign of someone who is new to this.
-You used a rom name I've never heard of, and suggested you weren't sure of the name yourself. That's usually a big red flag for someone who flashed some random rom they found via Google.
-You mentioned using Goo Manager. That's a non-standard method for this phone, and an awful lot of people have bricked their phones trying to flash roms through apps that aren't well-supported. CWM Touch was notorious for this when the One X first came out.
If you don't want people to assume things, you need to state them up front.
On topic: There appears to be a bug in the latest TWRP that causes issues for some people. Try rolling back to an earlier version.
iElvis said:
On topic: There appears to be a bug in the latest TWRP that causes issues for some people. Try rolling back to an earlier version.
Click to expand...
Click to collapse
Yeah, I saw that too, and why I asked the OP what version of TWRP.
i had problems with that rom on version 4.0.1 and 4.1.0 had alot of errors and trouble. i haven't tried 4.2.0 though, i have been having better luck with rom after clearing out recovery cache running "fastboot erase cache" and running only twrp 2.3.3.1.
i flashed the second to last release of twrp (latest gave mount issues), viper was running great, cm 10.1 avatar was running fine just didnt like how plain it was so i used goo manager to download hatkaXL and when the download finished i picked select and flash.. then the usual warning about flashing and it rebooted, hit spash screen where it still is hours later. i then tried manually boot into recovery, it hit the bootloader i selected recovery and it seemed to try and load. next step was back to fast boot and to reflash twrp (fastboot flash recovery recovery.img ) flashed 100% success and still wont boot into recovery just the bootloader, and i wasnt trying to get all defensive, i sent first post using the wifes phone and posted quick, had a guy hooking up my satellite at same time as phone crashed. has anyone tried the new version of cwm for the evita? maybe flashing that may get me back, i have roms and backups on the pc that i can seem to side load but never boot as well.
well after repeated flashing of recovery and (fastboot erase cache) it finally booted to recovery, now to see if my backup will load.

[Q] Unable to restore Nandroid Backup and boot

Hi guys,
nice to say hello to all of you.
I have been reading xda for a while and finally started playing with my old HTC Desire S. Kind of training in case I wanted to play with my actual device.
I wanted to unlock it thorugh htcdev, test some roms and back to stock version. Everything was fine but the last step.
At the beginning, I wanted to backup the system as it was, that's with the stock recovery. So I booted a custom recovery (not flashed) and made a nandroid backup with clockwork touch 5.8.1.5. Everything went fine.
After that, I started flashing custom recoveries and ROMs, just for fun. Some problem with that ROM, some with another, but I managed to run a couple or three.
Ok, end of the game. I want my copy back so I am restoring the nandroid.
I wipe everything, restore the nandroid through the same recovery, process finishes and says it's OK. Go back to fastboot and flash stock boot.img.
The result is I am stuck at htc logo.
I have tried flashing recovery.img also, fastboot deleting cache, relocking the bootloader...
I am pretty sure I am missing something with the booting process, but I have tried everything I know.
BTW, I have already tried RUU, but I am not capable of finding one with my CID, radio, etc.
I know it's an old device, but I would really love to solve it (because I am so f***ing pigheaded )
Thanks!!!
Grauchi said:
Hi guys,
nice to say hello to all of you.
I have been reading xda for a while and finally started playing with my old HTC Desire S. Kind of training in case I wanted to play with my actual device.
I wanted to unlock it thorugh htcdev, test some roms and back to stock version. Everything was fine but the last step.
At the beginning, I wanted to backup the system as it was, that's with the stock recovery. So I booted a custom recovery (not flashed) and made a nandroid backup with clockwork touch 5.8.1.5. Everything went fine.
After that, I started flashing custom recoveries and ROMs, just for fun. Some problem with that ROM, some with another, but I managed to run a couple or three.
Ok, end of the game. I want my copy back so I am restoring the nandroid.
I wipe everything, restore the nandroid through the same recovery, process finishes and says it's OK. Go back to fastboot and flash stock boot.img.
The result is I am stuck at htc logo.
I have tried flashing recovery.img also, fastboot deleting cache, relocking the bootloader...
I am pretty sure I am missing something with the booting process, but I have tried everything I know.
BTW, I have already tried RUU, but I am not capable of finding one with my CID, radio, etc.
I know it's an old device, but I would really love to solve it (because I am so f***ing pigheaded )
Thanks!!!
Click to expand...
Click to collapse
You can't flash roms from the recovery because you are not s off. If you have unlocked your bootloader then you have to flash using fastboot commands like the boot.img?
lilsafbig said:
You can't flash roms from the recovery because you are not s off. If you have unlocked your bootloader then you have to flash using fastboot commands like the boot.img?
Click to expand...
Click to collapse
Thank you @lilsafbig. In fact, I tried both, fastboot and recovery, and nothing worked.
Finally, I managed to create a Goldcard and install a new ICS version for my device. Was the only way I could recover a "stock" ROM, although it wasn't Orange one...

Categories

Resources