I'm having problems flashing my Desire S with ICS based roms. GB roms work fine, but any ICS rom I flash gets stuck on boot on a lit up black screen. I have tried a variety of roms, flashed both on CWM and 4EXT but the issue persists. Is there some kind of special procedure for ICS roms ?
Did you
1. Wipe all partitions except SD
2. Wipe dalvik + cache
Edit : And the procedures same for flashing ics and gb roms, unless the OP specifically tells you to do otherwise
I did all possible wipes and It's still the same. Any more ideas ?
tomkow4 said:
I did all possible wipes and It's still the same. Any more ideas ?
Click to expand...
Click to collapse
did u u unlock with HTCDEV.com ? if u did just flash the boot.img inside the rom you want if u never then either the rom takes a long time to boot or your not doing the wipe properly
give me some specs of your phone
Ok, I'll run through my process. I did unlock my phone via HTCDEV, then rooted it via SuperOneClick (meaning I still have HBoot 2.00.0002 and S-ON), then flashed it by flashboot with CWM, now I have 4EXT. What I always did whas do a wipe data/factory reset and flashed. Now inspired by vodka69er I did that and clear dalvik, cache, format all but sd - and then flashed - still the same.
tomkow4 said:
Ok, I'll run through my process. I did unlock my phone via HTCDEV, then rooted it via SuperOneClick (meaning I still have HBoot 2.00.0002 and S-ON), then flashed it by flashboot with CWM, now I have 4EXT. What I always did whas do a wipe data/factory reset and flashed. Now inspired by vodka69er I did that and clear dalvik, cache, format all but sd - and then flashed - still the same.
Click to expand...
Click to collapse
If you unlocked via htcdev you need to extract the boot.img from your desired ROM. After flashing the ROM you need to flash the boot.img manually via adb. You have to do this each time you flash a new ROM.
Sent by my fingers to your head.
He's been able to flash the gb based roms , only trouble with the ics ones. That means he already knows to flash the boot img separately(unlocked with htcdev) or am I missing something
Vodka69er said:
He's been able to flash the gb based roms , only trouble with the ics ones. That means he already knows to flash the boot img separately(unlocked with htcdev) or am I missing something
Click to expand...
Click to collapse
This. Exactly. I mean I have a MIUI GB rom so, I guess it's not about flashing a rom but trouble with ICS ones. So I figured that those must have something different about them or have a specific prerequisite. Others have flashed their D S's, so I'm kind of lost.
Can you post what you see on your bootloader
Sent from a Desire S waiting for Kernel 3. WAKE UP HTC!!!!
*** UNLOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT - 2.00.0002
Radio - 3822.10.08.04_M
eMMC - boot
Aug 22 2011, 15:22:13
@op
I know that this is covering old ground, but I've not seen an actual answer
Have you ever used 'fastboot flash boot NAME.IMG' command?
Swyped from my DesireS
http://www.androidauthority.com/desire-s-root-s-off-hboot-2-00-0002-superoneclick-74470/ - this is the guide I followed.
On a side note, I did a full wipe of everything I could and still no luck with ICS roms. I think I'll leave it alone.
You still didn't answer the question that I asked in the above post, the guide that you have doesn't cater for separately flashing the boot , which is what you need to do. The guide only tells you gore to instal recovery and root
Which (as people have been saying) means that i suspect that your ICS installs have no kernels and therefore don't/can't boot
What ROM are you running now?
As after wiping all nothing should boot, unless CWM wipe all doesn't wipe boot?
Swyped from my DesireS
ben_pyett said:
You still didn't answer the question that I asked in the above post, the guide that you have doesn't cater for separately flashing the boot , which is what you need to do. The guide only tells you gore to instal recovery and root
Which (as people have been saying) means that i suspect that your ICS installs have no kernels and therefore don't/can't boot
What ROM are you running now?
As after wiping all nothing should boot, unless CWM wipe all doesn't wipe boot?
Swyped from my DesireS
Click to expand...
Click to collapse
To answer directly - I don't remeber/don't think so. But honestly didn't care much since my roms ran. Right now I'm on MIUI.
But the remark on the kernel got me thinking - I don't really know how to approach this, should I find some kernel and flash it?
On your pc you need to open the ICS ROM zip file and take out a file called boot.img
After flashing the Rom you must then use the fastboot command from your PC, as you did when you flashed your recovery.
You must then issue the command 'fastboot flash boot boot.img'
see below for the full instructions
HappyEmu said:
If you unzip your ROM's Zip-file (the one you want to flash, you'll find a file called "boot.img". Move it into the same folder as your adb and fastboot executables (Android SDK) and flash it using fastboot.
To be a little more specific:
1. Extract boot.img from ICS rom zip file and move it in the same folder as your fastboot.exe (Android SDK) on your PC
2. Flash the ICS Rom as usual from recovery (don't forget to first perform the full wipe/format including the boot partition)
3. Boot into fastboot mode, connect your phone to your PC and flash boot.img using fastboot
Code:
fastboot flash boot $pathToYourBootIMG\boot.img
4. Reboot
Click to expand...
Click to collapse
Swyped from my DesireS
Your GB room worked as they were running on the stock kernel
ICS won't work this way.
As Ben has mentioned you need to flash the boot.img
Sent from a Desire S waiting for Kernel 3. WAKE UP HTC!!!!
eyahl said:
If you unlocked via htcdev you need to extract the boot.img from your desired ROM. After flashing the ROM you need to flash the boot.img manually via adb. You have to do this each time you flash a new ROM.
Sent by my fingers to your head.
Click to expand...
Click to collapse
*Bump*
Sent by my fingers to your head.
suku_patel_22 said:
Your GB room worked as they were running on the stock kernel
ICS won't work this way.
As Ben has mentioned you need to flash the boot.img
Click to expand...
Click to collapse
4EXT seems to flash the kernel upon installation of specific roms, but I still did it manually and ... nothing. It still goes into a coma upon boot. Maybe I'll do a video of what I'm doing when I get back from work, cause now I'm having problems with some other roms - they freeze on bootscreen. Maybe it has something to do with my phone being S-ON?
tomkow4 said:
4EXT seems to flash the kernel upon installation of specific roms, but I still did it manually and ... nothing. It still goes into a coma upon boot. Maybe I'll do a video of what I'm doing when I get back from work, cause now I'm having problems with some other roms - they freeze on bootscreen. Maybe it has something to do with my phone being S-ON?
Click to expand...
Click to collapse
I suspect that you're suffering the problem on other ROMS now as you're wiping the boot partition and therefore have no kernel.
[Q] How long do you wait on boot? you must be patient as first boot can take a while (although not longer than 10minutes).
A video would be a great way of showing the problem...Try to capture everything....
Your bootloader screen....
All the partition wipes
The Rom flash
The fastboot boot.img flash
and then what happens after...
Kind of noobish on my end, but as I was making the video - and did everything according to protocol just as earlier - it worked . I flashed BlackICE 5.5. Christ. Thanks anyway for the patience guys (I assume )
Related
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.
my desire s is unlocked and on hboot 2.00.002, i flash a custom rom. and the phone works perfectly but everytime i reboot my phone i got stuck on htc logo. but when i connect my phone to the computer and flash the boot.img it boots normally. did i do something wrong or what? please help me
I understand you corretly, that you flash boot.img and phone boots to rom? And after reboot stuck on logo?
tyrone128 said:
my desire s is unlocked and on hboot 2.00.002, i flash a custom rom. and the phone works perfectly but everytime i reboot my phone i got stuck on htc logo. but when i connect my phone to the computer and flash the boot.img it boots normally. did i do something wrong or what? please help me
Click to expand...
Click to collapse
Are you serious? It's written so often here that even the lazy guys should have gotten it.
If you unlocked via HTCdev you need to flash the boot.img of your desired ROM each time you have flashed a new ROM.
Sent by my fingers to your head.
eyahl said:
Are you serious? It's written so often here that even the lazy guys should have gotten it.
If you unlocked via HTCdev you need to flash the boot.img of your desired ROM each time you have flashed a new ROM.
Sent by my fingers to your head.
Click to expand...
Click to collapse
i know that if you are unlocked by htcdev and you install a custom rom you must flash the boot.img to boot, does it also apply on every reboot but not flashing custom rom?
Nope, not on every reboot. Just everytime you flash a new rom you need to flash the boot.img
shrome99 said:
Nope, not on every reboot. Just everytime you flash a new rom you need to flash the boot.img
Click to expand...
Click to collapse
how come everytime i reboot my phone it gets stuck on htc logo? but if i boot into fastboot and flash the boot.img it all goes well.
hmm... never heard of that issue before. What ROM are you using?
shrome99 said:
hmm... never heard of that issue before. What ROM are you using?
Click to expand...
Click to collapse
endymion, and when i restore my stock backup using ext4 recovery i also get stuck on htc white screen
I too have the same proble. Stuck at HTC logo everytime i reboot. I have to flash boot.img. I had unlocked via HTCDEV.com
I dont have this problem with CM9 ICS, but I have this problem with Primo-S-2.1, Primo-S 3.0 ICS and Saga 3D v5.1.0.
Do any one have a solution..
PROXUSER do you know why.
Very strange, unheard of before, after every reboot? did you clear dalvik and cache partition before flash of ROM?
If you HTCdev then after every nee ROM flash you must flash boot.img
Swyped from my Desire S using XDA Premium
If you restore an old nandroid backup after flashing on a new ROM do you also have to reflash boot.img separately, or does 4EXT recovery take care of that?
yes, you have to flash it
MarcovitchZA said:
If you restore an old nandroid backup after flashing on a new ROM do you also have to reflash boot.img separately, or does 4EXT recovery take care of that?
Click to expand...
Click to collapse
I'd say that 4EXT would take care of it?
draghiciandrei said:
yes, you have to flash it
Click to expand...
Click to collapse
Are you sure? surely if you restore a nandroid backup then that should contain the correctly restored boot partition and therefore you shouldn't need to reflash boot.img seperatley!?
Bobbyaju said:
I too have the same proble. Stuck at HTC logo everytime i reboot. I have to flash boot.img. I had unlocked via HTCDEV.com
I dont have this problem with CM9 ICS, but I have this problem with Primo-S-2.1, Primo-S 3.0 ICS and Saga 3D v5.1.0.
Do any one have a solution..
PROXUSER do you know why.
Click to expand...
Click to collapse
ben_pyett said:
Very strange, unheard of before, after every reboot? did you clear dalvik and cache partition before flash of ROM?
If you HTCdev then after every nee ROM flash you must flash boot.img
Swyped from my Desire S using XDA Premium
Click to expand...
Click to collapse
Every time i Format data, then clear cache, clear Dalvik and then install custom rom. Still i have to fastboot boot.img everu time i reboot my phone
Ben, what you said is correct in case of S-Off phones. But for those that are HTC unlocked, the boot partition is not writable from Recovery, and is only accessible for modification via fastboot. So for S-Off users, recovery can restore boot partition, whereas for S-On HTCDevil unlocked bootloaders, the boot.img has to to flashed manually via fastboot every single time when flashing a new ROM, or restoring a previously backed up nandroid.
Hope that explains it.
enigmaamit said:
Ben
Hope that explains it.
Click to expand...
Click to collapse
It certainly does, appreciate it, horrible HTCdev and nasty s on devices
Swyped from my Desire S using XDA Premium
Bobbyaju said:
Every time i Format data, then clear cache, clear Dalvik and then install custom rom. Still i have to fastboot boot.img every time i reboot my phone
Click to expand...
Click to collapse
enigmaamit said:
Ben, what you said is correct in case of S-Off phones. But for those that are HTC unlocked, the boot partition is not writable from Recovery, and is only accessible for modification via fastboot. So for S-Off users, recovery can restore boot partition, whereas for S-On HTCDevil unlocked bootloaders, the boot.img has to to flashed manually via fastboot every single time when flashing a new ROM, or restoring a previously backed up nandroid.
Hope that explains it.
Click to expand...
Click to collapse
Ya i got you but why do i have to fastboot boot.img every time i reboot my device in the same rom-Primos v3.0 or Saga3D5.0.1 (not while installing a new custom rom).
I dont have to fastboot boot.img everytime to reboot when iam on CM9 rom.
Bobbyaju said:
Ya i got you but why do i have to fastboot boot.img every time i reboot my device in the same rom-Primos v3.0 or Saga3D5.0.1 (not while installing a new custom rom).
I dont have to fastboot boot.img everytime to reboot when iam on CM9 rom.
Click to expand...
Click to collapse
No, you don't have to flash the boot.img everytime you simply reboot... The flashing only needs to be done when changing a ROM, as the kernel has to be matched to the ROM you are flashing. For simply rebooting, this is unnecessary.
ben_pyett said:
I'd say that 4EXT would take care of it?
Are you sure? surely if you restore a nandroid backup then that should contain the correctly restored boot partition and therefore you shouldn't need to reflash boot.img seperatley!?
Click to expand...
Click to collapse
The boot.img needs also to be flashed with fastboot after a restore.
The recovery has no permission to write to the boot partition, because of this it doesn't matter if you restore or flash a new one, but the backup contains the right boot.img, recovery can read but can't write to boot.
Gesendet von meinem Desire S mit Tapatalk
write boot.img every reboot
i have the same problem.after every simple reboot phone need to write boot.img from fastboot.
also i havnt problem with cm9
Hey Guys,
yesterday I wanted to revert my ROM from CM10 to TrickDroid 7.1. In TWRP 2.2.1 I wiped caches and did a factory reset and then flashed TD 7.1 following torxx's instructions (wipe, install ROM, flash boot.img with his boot flash script, let the ROM boot). After the reboot the phone hang. The startup sound came through but then no further action for about 7 Minutes.
Was that too little time waiting? Or is there any other issue interfering the boot process after reverting from Android 4.1.1 to 4.0.4 Sense?
If anyone can help is much appreciated. Even if I look stupid afterwords
Burkhard
herzbert said:
Hey Guys,
yesterday I wanted to revert my ROM from CM10 to TrickDroid 7.1. In TWRP 2.2.1 I wiped caches and did a factory reset and then flashed TD 7.1 following torxx's instructions (wipe, install ROM, flash boot.img with his boot flash script, let the ROM boot). After the reboot the phone hang. The startup sound came through but then no further action for about 7 Minutes.
Was that too little time waiting? Or is there any other issue interfering the boot process after reverting from Android 4.1.1 to 4.0.4 Sense?
If anyone can help is much appreciated. Even if I look stupid afterwords
Burkhard
Click to expand...
Click to collapse
Perhaps your hboot does not allow flashing or boot.img? Have you tried the fastboot method of flashing boot.img? How about reverting to a nandroid of a sense based ROM, then flashing TD?
el_smurfo said:
Perhaps your hboot does not allow flashing or boot.img? Have you tried the fastboot method of flashing boot.img? How about reverting to a nandroid of a sense based ROM, then flashing TD?
Click to expand...
Click to collapse
Prior to CM10 I was on latest stock ROM. Before that I had custom ROMs. HBoot on my phone after the OTA update is 1.14. Flashing the boot image of CM10 was no problem.
In order to use the phone I reinstalled CM10 and it works.
The boot images were flashed within fastboot. I do not know any other way to flash a boot image.
I dont have a nandroid backup.
Checked MD5?
torxx said:
Checked MD5?
Click to expand...
Click to collapse
They correspond.
If nothing else helps I will try to install the latest RUU and then flash a ROM. But I wanna circumvent the relock and unlock procedure.
Btw: Did anybody notice that the unlock code changes after an update of HBoot? Nobody mentioned that when the new base was released.
Same here... But fine now
herzbert said:
They correspond.
If nothing else helps I will try to install the latest RUU and then flash a ROM. But I wanna circumvent the relock and unlock procedure.
Btw: Did anybody notice that the unlock code changes after an update of HBoot? Nobody mentioned that when the new base was released.
Click to expand...
Click to collapse
Hey there,
I was having the same problems as you messioned. I flashed the boot.img through fastboot myself and some how it then worked Did not have an problems with flashing the boot.img before. But maybe its worth a try.
Of course you need to use fastboot!!
Did not try yet to flash the RUU. There was an update of CM10 yesterday. The heavy battery drain is gone with this update and there is no urgent need to go back to TrickDroid right now.
herzbert said:
Prior to CM10 I was on latest stock ROM. Before that I had custom ROMs. HBoot on my phone after the OTA update is 1.14. Flashing the boot image of CM10 was no problem.
In order to use the phone I reinstalled CM10 and it works.
The boot images were flashed within fastboot. I do not know any other way to flash a boot image.
I dont have a nandroid backup.
Click to expand...
Click to collapse
HBoot 1.14 is the problem. Anything above 1.09 needs special steps to flash unlike simply flashing with twrp as with 1.09 and below.
Sent from my HTC VLE_U using Xparent SkyBlue Tapatalk 2
LikeaG2root said:
HBoot 1.14 is the problem. Anything above 1.09 needs special steps to flash unlike simply flashing with twrp as with 1.09 and below.
Alright, so, what are these special steps? Can you tell? If its not flashing the within recovery and push the boot.img via fastboot to the phone I would be very interested. My previous HBoot version was 1.13. Flashing ROMs was never a big deal. Also not going to CM9 and back to sense based ROMs.
Click to expand...
Click to collapse
I am on hboot 1.14 and it worked via fastboot. Like you mentioned yourself you reinstalled CM10 and it booted, therefore your previous flash of the boot.img didn't work. So just flash the boot.img via bootloader and fastboot and you should be good...
HighRoIIer said:
I am on hboot 1.14 and it worked via fastboot. Like you mentioned yourself you reinstalled CM10 and it booted, therefore your previous flash of the boot.img didn't work. So just flash the boot.img via bootloader and fastboot and you should be good...
Click to expand...
Click to collapse
I did also flash the boot.img via fastboot. Why do you say that anyway? Is there another method to flash a boot.img?
you didn't mention wiping System as part of the full wipe--needs done
Partially solved
rugmankc said:
you didn't mention wiping System as part of the full wipe--needs done
Click to expand...
Click to collapse
Right, I did not mention it because system is wiped by TWRP during flashing the ROM. So there was no need to wipe it seperately. But maybe my mistake was not to wipe data and the new "asec" folder messed things up.
I'll never know because yesterday I did a complete wipe including the SDCard. Afterwards I was able to install TrickDroid flawlessly.
Thank you all for your efforts.
I've spent hours, and obviously am not smart enough.
ATT One X, Followed the x-factor root exploit, but didn't realize how important the "and use a recovery ADB shell or install from an update.zip to install Superuser and su" sentence is.
Tried to install a custom ROM, TWRP works great but I wiped it and went for a new Viper install, flashed the boot.img, which I now realize probably won't boot because I don't have S-Off. It just circles. I run the latest SU.zip but it still won't work
I keep trying to install older ROM's but they don't work either. All I get is a black screen and it locks up. I assume because I have Hboot 1.14
So now I have a new hboot, new TWRP, it's "tampered" and "unlocked" but I can't boot up into an old OS, and I'm not S-Off'd so I can't boot into a new OS. The new GUI for S-Off looks like what I should have used, but it would appear that I need to boot into Android first.
What do I do?
You have to flash boot.img from fastboot
Download rom, check md5
Extract rom, copy boot.img
Paste boot.img in folder with fastboot
Copy rom zip to SD card
Wipe cache, dalvik cache, system, factory reset.
Flash rom
Reboot to bootloader
Fastboot flash boot boot.img
Reboot.
If 2.14 hboot, cm10.1 with 3.4 kernel is the only aosp rom with which the touchscreen will work.
All sense roms will work.
Sent from my HTC One X using xda app-developers app
---------- Post added at 08:00 PM ---------- Previous post was at 07:52 PM ----------
RollTribe said:
You have to flash boot.img from fastboot
Click to expand...
Click to collapse
I put the whole thing cut its also possible he didn't wipe properly or something
Sent from my HTC One X using xda app-developers app
exad said:
Download rom, check md5
Extract rom, copy boot.img
Paste boot.img in folder with fastboot
Copy rom zip to SD card
Wipe cache, dalvik cache, system, factory reset.
Flash rom
Reboot to bootloader
Fastboot flash boot boot.img
Reboot.
If 2.14 hboot, cm10.1 with 3.4 kernel is the only aosp rom with which the touchscreen will work.
All sense roms will work.
Click to expand...
Click to collapse
Ok, I did that and I get a variety of problems.
use TWRP to send over the .zip ROM
wipe cache (I let the ROM install do it and manually in TWRP, both the default and advanced and clicking the default "factory reset"
use "install" to select the correct zip with the boot.img copied to my HD for fastboot
reboot into bootloader, fastboot, use DOS, fastboot says "OKAY" twice
bulletproof and cleanROM both just lock up at the white HTC menu with the red developer font. ViperXL3.2.7 just reboots back into recovery mode.
Do I need to do something with SU or Superuser or is that after I actually get a ROM installed? My CID is nothing but 1's and these ROMS are double checked for the Evita
EDIT: Viper 2.4 loads another HTC boot screen with a snake, but then reboots.
Also, I'd be fine with putting it back to stock and starting over, but I've got a CID of 11111111 (didn't write down the original), S-On and software is 2.20, I keep reading about bricks when people tried that.
I have followed the various guides at least 5 times, such as this one http://forum.xda-developers.com/showthread.php?t=1957193 and nothing, I guess I need a way to step backwards.
chris948 said:
Do I need to do something with SU or Superuser or is that after I actually get a ROM installed? My CID is nothing but 1's and these ROMS are double checked for the Evita
Click to expand...
Click to collapse
You don't need SU to flash a ROM. Once the ROMs get booted up properly, they will be rooted by default.
What version of TWRP? The newer builds have been known to be problematic, with 2.5 not working at all with CleanROM (maybe others). Recommend version 2.3, or latest official CWM.
redpoint73 said:
You don't need SU to flash a ROM. Once the ROMs get booted up properly, they will be rooted by default.
What version of TWRP? The newer builds have been known to be problematic, with 2.5 not working at all with CleanROM (maybe others). Recommend version 2.3, or latest official CWM.
Click to expand...
Click to collapse
bingo, that's what I get for logging into a website and downloading the latest version. 2.3.3 and 2.3.1 didn't help but CWM and a different ROM finally did.
thanks
chris948 said:
Also, I'd be fine with putting it back to stock and starting over, but I've got a CID of 11111111 (didn't write down the original), S-On and software is 2.20, I keep reading about bricks when people tried that.
I have followed the various guides at least 5 times, such as this one http://forum.xda-developers.com/showthread.php?t=1957193 and nothing, I guess I need a way to step backwards.
Click to expand...
Click to collapse
I had this same problem, here's what I did:
1. wrote CID back to AT&T's CID (CWS__001), here's a list: http://droider.eu/infodocs/CID list.pdf
2. relocked bootloader
3. ran 2.20 RUU
4. unlocked booloader/ got superCID
5. installed TWRP custom recovery
6. Got S-OFF -THIS WAS THE STEP I SKIPPED THE FIRST TIME
7. ran 3.18 RUU
8. install whatever you want
Hope that helps
Hey Guys,
I have a rooted htc amaze 4g i rooted, s-on with Hasoon2000 tool. I currently have the clockworkmod recovery installed but have also installed team wins recovery and 4ext recovery in the past trying to figure out my problem but to no avail. Im currently running the newest version stock ruu for tmobile. I have been having the issue of getting my phone to boot my roms properly and cant figure out why. I have installed CM10 rom and The viper rom. for the amaze and both roms do the same thing. During flashing of the zip files in recovery everything seems to work fine with both roms and install properly. Once installed and i go to reboot the phone, it will get stuck on the boot screen of whichever rom I installed and never actually boots the phone fully. Im at a loss and have many hours trying to get the roms to boot but i can not figure out why both roms always get stuck on boot screen. The viper rom will flash my capacitative buttons on the bottom and vibrate periodically but still wont get past the boot screen, Sorry if i left out any information out or if im making a newbie mistake (which im hoping for). I have an understanding of things but im no expert by any means, just let me know if you need to know more.
Thanks!
zebediah101 said:
Hey Guys,
I have a rooted htc amaze 4g i rooted, s-on with Hasoon2000 tool. I currently have the clockworkmod recovery installed but have also installed team wins recovery and 4ext recovery in the past trying to figure out my problem but to no avail. Im currently running the newest version stock ruu for tmobile. I have been having the issue of getting my phone to boot my roms properly and cant figure out why. I have installed CM10 rom and The viper rom. for the amaze and both roms do the same thing. During flashing of the zip files in recovery everything seems to work fine with both roms and install properly. Once installed and i go to reboot the phone, it will get stuck on the boot screen of whichever rom I installed and never actually boots the phone fully. Im at a loss and have many hours trying to get the roms to boot but i can not figure out why both roms always get stuck on boot screen. The viper rom will flash my capacitative buttons on the bottom and vibrate periodically but still wont get past the boot screen, Sorry if i left out any information out or if im making a newbie mistake (which im hoping for). I have an understanding of things but im no expert by any means, just let me know if you need to know more.
Thanks!
Click to expand...
Click to collapse
i think you might have S-on boot into fastboot and list us everything there please!
Trozzul said:
i think you might have S-on boot into fastboot and list us everything there please!
Click to expand...
Click to collapse
Sorry if im misunderstanding you but i do have s-on as it says in bootloader. I booted into boot loader, selected fastboot and the contents are as follows:
*** Unlocked ***
Ruby PVT SHIP S-ON RL
Hboot-1.93.0002
eMMC-boot
Fastboot
Recovery
Factory Reset
Clear Storage
SimLock
Image CRC
zebediah101 said:
Sorry if im misunderstanding you but i do have s-on as it says in bootloader. I booted into boot loader, selected fastboot and the contents are as follows:
*** Unlocked ***
Ruby PVT SHIP S-ON RL
Hboot-1.93.0002
eMMC-boot
Fastboot
Bootloader
Reboot
Reboot Bootloader
Power Down
Click to expand...
Click to collapse
so yeah that's a easy fix, your gonna want to take a file out of the Rom (CM10.zip) its going to be called Boot.img and your going to put on your SD card of the phone along with the ROM and the preferred gapps if you want one. your going to need to flash these in this order
Boot.img >CM10.zip >Gapps! if you were to get s-off you don't need to do this you can flash stuff normally.
Trozzul said:
so yeah that's a easy fix, your gonna want to take a file out of the Rom (CM10.zip) its going to be called Boot.img and your going to put on your SD card of the phone along with the ROM and the preferred gapps if you want one. your going to need to flash these in this order
Boot.img >CM10.zip >Gapps! if you were to get s-off you don't need to do this you can flash stuff normally.
Click to expand...
Click to collapse
Do I take the original rom that i extracted the files from, compress the boot img, then compress the remaining files back into the cm10.zip minus the boot and flash in order? Or do i just extract the boot img out of cm10.zip and compress it to zip and flash, then do the same flash with an unaltered version of cm10.zip in proper order?
zebediah101 said:
Do I take the original rom that i extracted the files from, compress the boot img, then compress the remaining files back into the cm10.zip minus the boot and flash in order? Or do i just extract the boot img out of cm10.zip and compress it to zip and flash, then do the same flash with an unaltered version of cm10.zip in proper order?
Click to expand...
Click to collapse
No no no no your making it hard on yourself bro, zips are a little like folders but when you drag stuff out of it, it copys the file instead of moving it, not all flashes have to be .zip types like I said before go into the cm10.zip with winrar or 7zip and take out boot.img flash the boot.IMG and then the ROM followed by the gapps after, its a good question to ask, if I knew was much as I know about winrar before started flashing roms I would have asked the same thing
Trozzul said:
No no no no your making it hard on yourself bro, zips are a little like folders but when you drag stuff out of it, it copys the file instead of moving it, not all flashes have to be .zip types like I said before go into the cm10.zip with winrar or 7zip and take out boot.img flash the boot.IMG and then the ROM followed by the gapps after, its a good question to ask, if I knew was much as I know about winrar before started flashing roms I would have asked the same thing
Click to expand...
Click to collapse
Okay, i have a few updates. First off i changed my recovery from clockwork to ext cuz i read on another thread 4ext is what i wanted for my scenario with s-on. Secondly i got teamveoms rom 1.7.2.3 which they fixxed the flashing of faux123 kernel and tried flashing again. I
zebediah101 said:
Okay, i have a few updates. First off i changed my recovery from clockwork to ext cuz i read on another thread 4ext is what i wanted for my scenario with s-on. Secondly i got teamveoms rom 1.7.2.3 which they fixxed the flashing of faux123 kernel and tried flashing again. I
Click to expand...
Click to collapse
you can use any custom recovery with S-on you just need to take out the boot.img for every rom you want to flash, if you dont want to do this every time you need to get S-off, i think you can flash Sense Roms with s-on without the boot.img
(oh and sorry about not noticing that you have s-on in your first post, i was sort of skimming!)
Trozzul said:
you can use any custom recovery with S-on you just need to take out the boot.img for every rom you want to flash, if you dont want to do this every time you need to get S-off, i think you can flash Sense Roms with s-on without the boot.img
im sorry I didn't realize that my post didn't post all the way idk what happened there. I do have team venom
(oh and sorry about not noticing that you have s-on in your first post, i was sort of skimming!)
Click to expand...
Click to collapse
I'm sorry I didn't realize that my post didn't post all the way. I did get teamvenom 1.7.2.3 installed properly once the faux kernel installed like it should during aroma installer and its runnin good. I do like it but would like to try a few more roms for sure before I decide. I did try and do exactly what you said with extractin the boot.img out of cm10 and flashing them seperately with the boot.img flashed 1st then cm10zip second and I am still having the same problem. The HTC screen pops up first then the cryanogenmod boot screen and it gets stuck there. I used to have the same problem the tv 1.7.2.1 andd I then got the updated 1.7.2.3 version which fixxed the faux kernel flashing issue and after that it installed properly. But I still get the same problem with cm10. Sorry if i'm a pest just want me a jellybean Rom! Lol
zebediah101 said:
I'm sorry I didn't realize that my post didn't post all the way. I did get teamvenom 1.7.2.3 installed properly once the faux kernel installed like it should during aroma installer and its runnin good. I do like it but would like to try a few more roms for sure before I decide. I did try and do exactly what you said with extractin the boot.img out of cm10 and flashing them seperately with the boot.img flashed 1st then cm10zip second and I am still having the same problem. The HTC screen pops up first then the cryanogenmod boot screen and it gets stuck there. I used to have the same problem the tv 1.7.2.1 andd I then got the updated 1.7.2.3 version which fixxed the faux kernel flashing issue and after that it installed properly. But I still get the same problem with cm10. Sorry if i'm a pest just want me a jellybean Rom! Lol
Click to expand...
Click to collapse
hmmm i do not know what todo at this point, i think you wanna take it to the official forms for the device, sorry mate.
Edit: maybe try a Sense rom first? also what version of CWM did you have before? only X.x.x is important to know.