Database Info

[Q] problem flashing ICS roms

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 )

[Q] BRICKED - Sorry, need to ask for help

Hi. My Norwegian HTC ONE S (S4) cid: HTC__y13, unlocked with HTCDEV.
(I have spent 16 hours now trying to get any ROM back up, so yes I have been searching for everything)
I have been running Cyanogenmod but wanted to go back to stock because the official Jelly Bean is just around the corner. In Clockworkmod I went a bit crazy with deleting all /sdcard /data.... etc.. I dont know if this made the problem?
I thought the easiest way to go back to stock was with an RUU, but it stops in the middle of the installation. (the info file contains my cid: HTC__y13)
I later read that the phone must have S-OFF to use RUU, and S-OFF is not possible with HTC One S??
Also tested the trick with manualle installing the ROM.zip off %temp% (relocked, but fastboot returned (remote: 44 hboot version check fail)
I have tried to go back to custom rom, I install the zip from Clockworkmod, after reboot it shows the ROMS Logo, but it doesn`t start up, tried the Cyanogenmod I was running earlier + MIUI.US and Untøchåbles.
Last fix i tried was this, with the same result:
Yes, I just fixed my problem yesterday after some serious trial-and-error.
1) Use the All-in-One-Kit and flash your recovery back to stock
2) Boot into the bootloader and choose to "clear storage" and afterwards to reset to factory defaults.
3) Go back to the all-in-one-kit and flash a CWM recovery version again.
4) Reboot into recovery (CWM). Your /sdcard should now be mounted and visible.
5) Now, try the UTB rom (it worked for me), rename the zip file to something short (i.e. utb.zip), and push it to the sdcard using adb as follows:
Code:
adb push utb.zip /sdcard
6) While still in CWM, flash the zip.
The trick here is that only the stock recovery is capable of restoring access to the sdcard by it's proprietary "clear storage" option.
Good luck!
Sorry to bother you all, but is there any obvious reasons why my phone won`t boot?
Thank you in advance

You don't need soff to run ruu unless It's specific for this device. I never soff'd my amaze and still was able to flash ruu after renaming it
Sent from my HTC VLE_U using xda app-developers app

ERROR 155
Ok, maybe not... but I get ERROR 155 after a few minutes with RUU....
But If I only could get any custom rom running ...... argh!
I have a norwegian HTC one S, cid: HTC__y13, I can`t find an RUU for "Telenor" so I guess the "EUROPEAN" RUU is the correct one?

FIXED, Finally
Took only 20 hours of testing and failing....
Finally got the right RUU
1. Boot into bootloader
2. Flash stock boot - "ville_recovery_signed.img"
3. Clear Storage
4. Factory Reset
5. Most important of all.... get the right RUU... "RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655_signed"
Tried to delete this Thread but couldn`t figure out how...

ryvaenge said:
Took only 20 hours of testing and failing....
Finally got the right RUU
1. Boot into bootloader
2. Flash stock boot - "ville_recovery_signed.img"
3. Clear Storage
4. Factory Reset
5. Most important of all.... get the right RUU... "RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655_signed"
Tried to delete this Thread but couldn`t figure out how...
Click to expand...
Click to collapse
Thanks!
But I'm installing the RUU with TWRP recovery

What am I missing? Need an OS, haven't S-Off'd yet

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

[Q] SD card appears as only 48MB. how come?

Hi, seems like my One S's sdcard partition has corrupted. been using TWRP 2.500 and recently upadted to 2.6.30 to use the new Maximus Rom. During the rom installation, I wiped the sdcard sectrion by mistake so I couldn't get to flash the zip file, then, I've tried multiple times of recovery.img flashings via RUU mode or on the bootloader screen. Finally when I got the TWRP recovery mode again, it says the sdcard folder only accepts 48 MB so I cannot push any custom roms since they are bigger than 500MB... Any ideas? Should I send it to the repair shops? Please Help!! Thank you!
FYI, my phone was
Tampered, Unlocked, S-off
also, when I press mount button on TWRP, this list appears
Cache
Data
Internal SDcard
System
USB-OTG
but I select Internal SD, the computer says the removable disk has only 48MB of available space.(I wiped it multiple times!)

puwa said:
Hi, seems like my One S's sdcard partition has corrupted. been using TWRP 2.500 and recently upadted to 2.6.30 to use the new Maximus Rom. During the rom installation, I wiped the sdcard sectrion by mistake so I couldn't get to flash the zip file, then, I've tried multiple times of recovery.img flashings via RUU mode or on the bootloader screen. Finally when I got the TWRP recovery mode again, it says the sdcard folder only accepts 48 MB so I cannot push any custom roms since they are bigger than 500MB... Any ideas? Should I send it to the repair shops? Please Help!! Thank you!
FYI, my phone was
Tampered, Unlocked, S-off
also, when I press mount button on TWRP, this list appears
Cache
Data
Internal SDcard
System
USB-OTG
but I select Internal SD, the computer says the removable disk has only 48MB of available space.(I wiped it multiple times!)
Click to expand...
Click to collapse
Omg. Why the people dont read op before they are going to flash new Rom. Just follow the instructions.
Sent from my HTC One S

tominozh said:
Omg. Why the people dont read op before they are going to flash new Rom. Just follow the instructions.
Sent from my HTC One S
Click to expand...
Click to collapse
Could you please tell me at least it's repairable or not? I want your help..
Also, I wonder what part I missed so it happened...hmm

puwa said:
Could you please tell me at least it's repairable or not? I want your help..
Also, I wonder what part I missed so it happened...hmm
Click to expand...
Click to collapse
Yes, don't sweat it. It is repairable.
It's hard for my to tell what you missed, because you didn't write what you did. So just follow installation instructions in the first post of maximus Rom. (flash new firmware, modified recovery, then Rom).
Sent from my HTC One S

tominozh said:
Yes, don't sweat it. It is repairable.
It's hard for my to tell what you missed, because you didn't write what you did. So just follow installation instructions in the first post of maximus Rom. (flash new firmware, modified recovery, then Rom).
Sent from my HTC One S
Click to expand...
Click to collapse
thank you! so, for flashing a new firmware, what would be a good firmware to start? any recommendations? i tried the firmware.zip in the install kit but not worked. same 48MB limit on the /sdcard/. any ideas?
:laugh:

Just follow this. It worked for almost all of us..
http://forum.xda-developers.com/showthread.php?p=45621060

gelo01 said:
Just follow this. It worked for almost all of us..
http://forum.xda-developers.com/showthread.php?p=45621060
Click to expand...
Click to collapse
GRT!! Thanks so much for saving my LIFE!!

gelo01 said:
Just follow this. It worked for almost all of us..
http://forum.xda-developers.com/showthread.php?p=45621060
Click to expand...
Click to collapse
All of these steps work for me except flashing the recovery as a ZIP. I get the wrong CID error (code 42 if i remember correctly). Thing is, I flash the .img directly usign fastboot flash recovery and that works but then the install process says, in android, transfer ROM. At this point, I don't have access to the SD card and the ROM is not in my sd card (it was wiped anyway?)
*EDIT*
Ok I changed my CID to 1111111 and now it works to flash the firmware. I still get partitions errors it seems though.
What I did is flash the stock recovery, clear storage, factory reset, reflashed the firmware given in Maximus thread, then the TWRP given and still, I get problems with my sdcard not mounting?

GabeyC said:
All of these steps work for me except flashing the recovery as a ZIP. I get the wrong CID error (code 42 if i remember correctly). Thing is, I flash the .img directly usign fastboot flash recovery and that works but then the install process says, in android, transfer ROM. At this point, I don't have access to the SD card and the ROM is not in my sd card (it was wiped anyway?)
*EDIT*
Ok I changed my CID to 1111111 and now it works to flash the firmware. I still get partitions errors it seems though.
What I did is flash the stock recovery, clear storage, factory reset, reflashed the firmware given in Maximus thread, then the TWRP given and still, I get problems with my sdcard not mounting?
Click to expand...
Click to collapse
if you are talking about mounting usb storage in recovery, then no, you cannot do that on Maximus HD rom. (it's a modified TWRP to work on the new firmware)
You can sideload in TWRP or ADB push the rom to your sdcard.
I would give you a link to a page describing it, but search is unavailable right now, have to try later.
But just search that thread with keyword sideload. There you will find the exact commands to load the rom onto your sdcard.

tivofool said:
if you are talking about mounting usb storage in recovery, then no, you cannot do that on Maximus HD rom. (it's a modified TWRP to work on the new firmware)
You can sideload in TWRP or ADB push the rom to your sdcard.
I would give you a link to a page describing it, but search is unavailable right now, have to try later.
But just search that thread with keyword sideload. There you will find the exact commands to load the rom onto your sdcard.
Click to expand...
Click to collapse
Yea, that's exactly what I ended up doing... it's not clear on any thread though...
Thanks
I went back to CM, didn't like maximus so much and it didn't fix my EDGE only problem so

It went back to 48mb
Hi i had the same problem with my htc one s.So i paniced and for some reason i put s-on(I deleted the os from the pc using mount storage) I managed to fix it by installing the recovery as zip. Then i tried to adb sideload a rom but it didn't work. So i went to boot loader then to fast boot and did fastboot flash zip Energyrom.zip. That gave me an error so i went back to recovery to try to side load the rom again, but my sdcard went back to 48mb.I reflashed the recovery (the one from install package) same thing . What do i do????? I need help asap i want my phone back (IM ONLY 12) Please reply asap.

cyberusman said:
Hi i had the same problem with my htc one s.So i paniced and for some reason i put s-on(I deleted the os from the pc using mount storage) I managed to fix it by installing the recovery as zip. Then i tried to adb sideload a rom but it didn't work. So i went to boot loader then to fast boot and did fastboot flash zip Energyrom.zip. That gave me an error so i went back to recovery to try to side load the rom again, but my sdcard went back to 48mb.I reflashed the recovery (the one from install package) same thing . What do i do????? I need help asap i want my phone back (IM ONLY 12) Please reply asap.
Click to expand...
Click to collapse
I think the easiest way is to flash the stock recovery and then do a sdcard wipe then a factory reset.
After that, you go through the process as described in the maximus rom thread, you will have to flash with sideload. That should work afterward

I am doomed
Hi guys,
Yesterday I decided to try MaximusROM 10.0.0 HD on my HTC One S, which is s-OFF and with superCID. The problem is: I didn't flashed first the rom as it was said, and I just used the Installation Package, installing directly the firmware.zip and the modified recovery. I tried to follow the steps written before, but now my phone works with the stock rom but it says that there are only 48mb in sd card, and that means that I can't even take photos, because I have no memory left. I found out that my phone, when is booted up, in settings says that I have 15,96GB of space for applications. What can I do?

GabeyC said:
I think the easiest way is to flash the stock recovery and then do a sdcard wipe then a factory reset.
After that, you go through the process as described in the maximus rom thread, you will have to flash with sideload. That should work afterward
Click to expand...
Click to collapse
I think I need to to that process my sdcard appears to be 10 gig only. Do you have a link for stock recovery? mine is S4.

48 mb storage = new 3.16 firmware
fix = flash custom 2.6.1 twrp
Sent from my HTC One S using XDA Premium 4 mobile app

lost sd card 48mb
Hi I have big problem with my HTC one s I decided to install maximus hd but I need super cid and s-off facepalm metod everything I do original cid cange to 1111111... Get s-off acses and and install Rom then firmware and when Rom but Rom loads very slowly and sometimes
Black screen and not won't load Rom. And I decided to back s-on and back to original CID HTC_111 and install tricdroid beta 10.0 and then my sdcard 48mb. I try everything flash stock recovery delete all data and wipe but still 48mb try changing a few recovery cmrecovery all types and Twrp recovery but work one prefect Twrp 2.6.1.0 this recovery show me 12gb but I installed Rom on pc 48 I try again flash firmware from maximus hd but failed bicose I change my cid and back to s-on then. I try to go to s-off and change my cid to 11111111.
Noting happen my cid still htc_111 I can't do s-off my hboot is 2.16.0000 I read this forums I find many solutions but no-one don't help my. Try install three roms trickdroid magiobeta and source v14 still 48 I just want get my sd card please somebody. I try many thing relock boot loader try with ruu but still 48

help
dcvc said:
Hi I have big problem with my HTC one s I decided to install maximus hd but I need super cid and s-off facepalm metod everything I do original cid cange to 1111111... Get s-off acses and and install Rom then firmware and when Rom but Rom loads very slowly and sometimes
Black screen and not won't load Rom. And I decided to back s-on and back to original CID HTC_111 and install tricdroid beta 10.0 and then my sdcard 48mb. I try everything flash stock recovery delete all data and wipe but still 48mb try changing a few recovery cmrecovery all types and Twrp recovery but work one prefect Twrp 2.6.1.0 this recovery show me 12gb but I installed Rom on pc 48 I try again flash firmware from maximus hd but failed bicose I change my cid and back to s-on then. I try to go to s-off and change my cid to 11111111.
Noting happen my cid still htc_111 I can't do s-off my hboot is 2.16.0000 I read this forums I find many solutions but no-one don't help my. Try install three roms trickdroid magiobeta and source v14 still 48 I just want get my sd card please somebody. I try many thing relock boot loader try with ruu but still 48
Click to expand...
Click to collapse
Someone may be help me with this trouble :crying::crying::crying::crying::crying::crying::crying::crying::crying:
:crying::crying::crying::crying::crying::crying: Thanks for the help :crying::crying::crying::crying::crying:

same here what should we do i have managed to install magiorom but windows shows only 48mb all i want is to get back to stock but i messed up my cid i am on roger001 but i cannot find a correct rom as i have mi mid pj4010000 please help me get back to stock

[Q] ViperS JB 3.1.4 - stuck on htc white screen

Hi
Noob problem
HTC sensation XE
I had ViperS 3.1.2 and then updated via OTA to ViperS 3.1.3 and at last ViperS 3.1.4 (also via OTA). After that I got stuck on htc white screen.
I can go into recovery with 4ext and followed the steps form here - http://forum.xda-developers.com/showthread.php?t=2082978
1.Boot into Recovery
3.Wipe data/factory reset(Format /system,/cache,/data,etc)
4.Wipe Dalvik & Cache
[enable smart-flash before flashing] FOR S-ON users ONLY
5.Flash ROM [VIPERS JB ROM]
6.DONE
I have tried it with ViperS 3.1.2 (full rom) and ViperS 3.1.4 (full rom) and after I always get stuck on htc white screen.
Attached I posted the logs from ViperS 3.1.2 (full rom) and ViperS 3.1.4 (full rom) instalation
Since this is my 1st post, I'm unable to post it on the correct topic - http://forum.xda-developers.com/showthread.php?t=2216858
Every time I go into recovery mode with 4ext after installing the rom i get the message "4ext smartflash is currently set to update boot partition on next system start"
So apparently I have a problem on boot partition, because the update is never done.
Does anyone have an idea on to fix this?
I hope I'm not infringing any rules to post this question here.

Just to add some more info
I tried to restore a backup that I made, and still I get stuck on htc white screen.
I also tried to install ViperS 5.0.0 JB from here - http://forum.xda-developers.com/showthread.php?t=2531054 - and stillI get stuck on htc white screen.
Don't really now what else to try

smapxda said:
Just to add some more info
I tried to restore a backup that I made, and still I get stuck on htc white screen.
I also tried to install ViperS 5.0.0 JB from here - http://forum.xda-developers.com/showthread.php?t=2531054 - and stillI get stuck on htc white screen.
Don't really now what else to try
Click to expand...
Click to collapse
try this
format all partiotins except sdcard
enable smartflash
flash the rom
if it fails then flash the boot.img of the rom via fastboot command
the command is fastboot flash boot boot.img

Thanks for your reply
rzr86 said:
try this
format all partiotins except sdcard
enable smartflash
flash the rom
Click to expand...
Click to collapse
I actually had done this before
rzr86 said:
if it fails then flash the boot.img of the rom via fastboot command
the command is fastboot flash boot boot.img
Click to expand...
Click to collapse
And this solved the issue, I had already seen it in this post - http://forum.xda-developers.com/showpost.php?p=37229807&postcount=2 - before your reply.
I'm now putting ViperS 3.1.4 (full rom), because when I could start the phone it had the ViperS 5.0.0 JB (to many tries to fix the phone) and after a phew minutes I got to the conclusion that I prefer version 3.1.4

smapxda said:
Thanks for your reply
I actually had done this before
And this solved the issue, I had already seen it in this post - http://forum.xda-developers.com/showpost.php?p=37229807&postcount=2 - before your reply.
I'm now putting ViperS 3.1.4 (full rom), because when I could start the phone it had the ViperS 5.0.0 JB (to many tries to fix the phone) and after a phew minutes I got to the conclusion that I prefer version 3.1.4
Click to expand...
Click to collapse
I always forgot SmartFlash back in the days on S-ON.
Very scary to see this on a neatly new device

fool
STOP!! discussing about team venom, I hate it there are no tweaks, my one feels thousand times better then this!!

hi all, all can make is own choice to use it. plz Stop U
@PandaPower :
If u don't like it, because tweaks do not work, when it will be solve, u'll try it or no???
If no, let us talk about what we want and u talk in ure favourite ROm topic. thank u :good: