Database Info

I need assistance on how to get back to my stock Gingerbread ROM. HTC Sensation XE

I have my HTC Sensation XE which has originally the 2.3.4 Gingerbread.
I would like to have an assistance on how to do it?
Do I need to flash specific firmwares? Where could I get it? and is it safe to use the backup I made before with that Gingerbread Rom?
Thank you.
I used SUPERCID method.. Therefore I'm not exactly sure whats my CID number and RUU but im pretty sure its either HTC__038 or HTC__044 asia or wwe_asia.
If it helps , I had some Starhub apps, Singtel or whatever, so I assume its more of an HTC__044 CID number?
Thank you.

If you did superCID you don't need to worry about which ruu you use. There is a stock GB ruu link in the s-on section of the sticky guide to everything in the dev forum.
Sent from my HTC Pyramid using xda premium

stringer7 said:
If you did superCID you don't need to worry about which ruu you use. There is a stock GB ruu link in the s-on section of the sticky guide to everything in the dev forum.
Sent from my HTC Pyramid using xda premium
Click to expand...
Click to collapse
Thank you for the response. But im trying to get the OTA also.
That's why I want to be sure about my RUU. and CID ^^, Thank you.

ardom said:
Thank you for the response. But im trying to get the OTA also.
That's why I want to be sure about my RUU. and CID ^^, Thank you.
Click to expand...
Click to collapse
OK, you can find your original cid by entering "getprop ro.cid" in terminal emulator.
Sent from my HTC Pyramid using xda premium

stringer7 said:
OK, you can find your original cid by entering "getprop ro.cid" in terminal emulator.
Sent from my HTC Pyramid using xda premium
Click to expand...
Click to collapse
I had changed my CID when i rooted mine i used supercid method and changed it to 11111111 i forgot my original ru. Im nt sure exactly too if its wwe_asia or asia but im sure its either of the two. I had Starhub app too so i have a premonition that it could be htc__044 or asiawwe singapore version.
Im confused lol. I Want to go back to my stock ruu and cid. Or least the cid so i could restore my backup if possible. Then if ever i ota update. Less prblems could be encountered.
Sent from my HTC Sensation XE with Beats Audio

What are the steps I need to do?
Which to flash? any firmware?
THank you.

This is a prime example of making sure you check for the RUU BEFORE you flash anything new
Do what is said above and it will tell you your original CID. We can then see if we can find the RUU

Good luck. I just updated my xe to ics by simply reading a lot of posts on this site. And simply following all instructions.
At first tho, I mistakenly flashed sensation and not sensation xe. But again, found the correct files here on this site. All sorted and now have beats audio back, now with sense and ics latest.
So many helpful people here, so I hope you too get your fine sorted to the way you want yours. Although curious as to why you wanna go back to gb.
Surely ics is better?
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA

hi
hi guys, do you have any link for official Gingerbread RUU 1.73 with beats audio for sensation XE? i just turn my sensation XE to s-on and flash the RUU but i flashed a wrong ruu.thanks guys.i want to update my sensation XE to ics through system update

Are you S-ON again now? If so, you'll need to S-OFF before you can flash the XE RUU (which you can find here):
https://www.yousendit.com/download/M3BtWmd2YWJ6NE5qQTlVag

Its already 1111111 for my CID. Im planning to go back to stock gb so i can get the ota ics and try it out.
Sent from my HTC Sensation XE with Beats Audio

Yes my phone is s-on again, so how do I flash the ruu?and just s-off? No need to do rooting?thanks

Help ~ Loop boot
I was gonna revert to my stock Gingerbread 2.3.4, I was trying to achieve ICS 4.x and Cyanogen mod 9, but I n00bed it up and wound up in a boot loop. I've read several different tutorials and I gathered I need to flash back to Stock GB. Do I just need a link to a Stock GB that fits my CID?
CID = T-MOB010
No Super CID
No RUU
Thanks much

soldierforus said:
I was gonna revert to my stock Gingerbread 2.3.4, I was trying to achieve ICS 4.x and Cyanogen mod 9, but I n00bed it up and wound up in a boot loop. I've read several different tutorials and I gathered I need to flash back to Stock GB. Do I just need a link to a Stock GB that fits my CID?
CID = T-MOB010
No Super CID
No RUU
Thanks much
Click to expand...
Click to collapse
yes yes stock GB would do ..also ..you have stock ICS for that cid too want that ?
GB RUU for TMOB USA
ICS RUU for TMOB USA (post #1 section #3 has the link to RUU's)
but
care to explain more what happened ?..it probably might be a small solution
small details would do ..
complete details present in the bootscreen (a screenshot would do too)
also
a complete output of the following command (except IMEI and serail number)
fastboot getvar all
then i can give you a perfect solution

ganeshp said:
yes yes stock GB would do ..also ..you have stock ICS for that cid too want that ?
GB RUU for TMOB USA
ICS RUU for TMOB USA (post #1 section #3 has the link to RUU's)
but
care to explain more what happened ?..it probably might be a small solution
small details would do ..
complete details present in the bootscreen (a screenshot would do too)
also
a complete output of the following command (except IMEI and serail number)
fastboot getvar all
then i can give you a perfect solution
Click to expand...
Click to collapse
Sorry to double post, I thought this may be a dead thread since the previous post had a question and no reply in 4 months.
_____________________________________________
The Details:
Boot loop began after I flashed to firmware 3.32 using:
Universal Firmware 3.32 Universal (Non-TMOUS): Since I am on TMO, I gather I should have used the TMOUS flash?
DOWNLOAD: http://d-h.st/afS
MD5: 8f50e9f4f3fab7edcd4013015703f81c
From this tutorial: http://forum.xda-developers.com/showthread.php?p=21711154#post21711154
I later I found a cynaogen tutorial to help with boot loop and followed these steps:
1) Set to factory reset
2)Cleared Delvick (sp?) Cache
____________________________________________
Current Boot Screen:
Revolutionary
Pyramid PVT SHIP S-OFF RL
HBOOT 1.27.1100
RADIO-11.22.3504.07_M
OpenADSP-v02. 6. 0. 226.00.0131
eMMC-boot
_____________________________________________
Getvar all Results:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.1100
(bootloader) version-baseband: 11.22.3504.07_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.32.401.3
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5810000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3816mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 617f0a98
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.490s
So how do the RUU's function exactly? I read the glossary term in wiki, but I don't fully understand the concept. They will update my ROM through window? I guess I need to be able to kill this boot loop first though.
Thanks again

soldierforus said:
Sorry to double post, I though this may be a dead thread since the previous post had a question and no reply in 4 months.
_____________________________________________
The Details:
Boot loop began after I flashed to firmware 3.32 using:
Universal Firmware 3.32 Universal (Non-TMOUS): Since I am on TMO, I gather I should have used the TMOUS flash?
DOWNLOAD: http://d-h.st/afS
MD5: 8f50e9f4f3fab7edcd4013015703f81c
From this tutorial: http://forum.xda-developers.com/showthread.php?p=21711154#post21711154
I later found a cynaogen turoial to help with bootloop and followed these steps:
1) Set to factory reset
2)Cleared Delvick (sp?) Cache
____________________________________________
Current Boot Screen:
Revolutionary
Pyramid PVT SHIP S-OFF RL
HBOOT 1.27.1100
RADIO-11.22.3504.07_M
OpenADSP-v02. 6. 0. 226.00.0131
eMMC-boot
_____________________________________________
Getvar all Results:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.1100
(bootloader) version-baseband: 11.22.3504.07_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.32.401.3
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5810000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3816mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 617f0a98
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.490s
So How the RUU's function exactly. They will update my ROM through window? I guess I need to be able to kill this boot loop first though.
Thanks again
Click to expand...
Click to collapse
for RUU ..you need to connect the phone in bootloader to pc ..and then just double click on it ...that will do
one last try for flashing custom rom ..still not worked then go for RUU
btw what recovery you are using ?
if using cwm ...can you switch to 4EXT recovery ?
get the recovery image from the below db link (recovery.img inside the zip)
4EXT DB link
and flash it via fastboot
fastboot flash recovery recovery.img
got to the recovery
4EXT->wipe|format->format all partitions except sdcard
then back to main menu ...and flash the rom (what ever custom rom you want)
then reboot and see..if it still stuck at boot logo
then extract the boot.img from the rom zip file
and flash it manually
fastboot flash boot boot.img
then reboot
still stuck ?
then reflash the firmware (be sure to check the md5 of the firmware you have downloaded)
still stuck?
then RUU

No-Go
ganeshp said:
for RUU ..you need to connect the phone in bootloader to pc ..and then just double click on it ...that will do
one last try for flashing custom rom ..still not worked then go for RUU
btw what recovery you are using ?
if using cwm ...can you switch to 4EXT recovery ?
get the recovery image from the below db link (recovery.img inside the zip)
4EXT DB link
and flash it via fastboot
fastboot flash recovery recovery.img
got to the recovery
4EXT->wipe|format->format all partitions except sdcard
then back to main menu ...and flash the rom (what ever custom rom you want)
then reboot and see..if it still stuck at boot logo
then extract the boot.img from the rom zip file
and flash it manually
fastboot flash boot boot.img
then reboot
still stuck ?
then reflash the firmware (be sure to check the md5 of the firmware you have downloaded)
still stuck?
then RUU
Click to expand...
Click to collapse
So it wouldn't let me flash 4ext, it says: "cannot load 'recovery.img'" I didn't unzip it or even leave the zip in the root, I took only the recovery.img and left it in to sd root.
You said to flash the custom ROM, but this is my first attempt, and although I have downloaded CM9, the instructions I have read from other tutorials tell me I have to upgrade first to firmware 3.32, then to firmware 3.33, then I can install CM9, which will give me ICS/4.x Am I correct so far?
I don't even know if the 3.32 flash was a success (Do you?) since now I am in a boot loop. Could it be because I should have used the TMOUS instead of the non-TMOUS universal for 3.32? I picked the non-TMOUS because I didn't realize what TOUS stood for at the time, and the other link said universal (and the android-info had my cid/mid)
Also thanks for the RUU links, but I don't know what good the ICS will do if I don't have it yet. Those RUU's will do what exactly? Update to the latest ROM ? Also, is that for all roms or just 3rd party? Looking at the getvar log I sent you, I gather the 3.32 did work, So I should download the ICS 3.32 RUU link you sent me. That's what I am going to try now
EDIT
________________________________
I re-installed cm9, AND EUREKA!!!!!! My first custom ROM. Many thanks to all who helped! Now which RUU do I use, and how often should I run it?

soldierforus said:
So it wouldn't let me flash 4ext, it says: "cannot load 'recovery.img'" I didn't unzip it or even leave the zip in the root, I took only the recovery.img and left it in to sd root.
You said to flash the custom ROM, but this is my first attempt, and although I have downloaded CM9, the instructions I have read from other tutorials tell me I have to upgrade first to firmware 3.32, then to firmware 3.33, then I can install CM9, which will give me ICS/4.x Am I correct so far?
I don't even know if the 3.32 flash was a success (Do you?) since now I am in a boot loop. Could it be because I should have used the TMOUS instead of the non-TMOUS universal for 3.32? I picked the non-TMOUS because I didn't realize what TOUS stood for at the time, and the other link said universal (and the android-info had my cid/mid)
Also thanks for the RUU links, but I don't know what good the ICS will do if I don't have it yet. Those RUU's will do what exactly? Update to the latest ROM ? Also, is that for all roms or just 3rd party? Looking at the getvar log I sent you, I gather the 3.32 did work, So I should download the ICS 3.32 RUU link you sent me. That's what I am going to try now
EDIT
________________________________
I re-installed cm9, AND EUREKA!!!!!! My first custom ROM. Many thanks to all who helped! Now which RUU do I use, and how often should I run it?
Click to expand...
Click to collapse
RUU is rom update utility.. It's official htc file
Ruu is complete software for your phone
It wipes everything.. Rom, recovery firmware.. Everything and flashes the corresponding stock One...
So when you run ics ruu.. You will have complete ics stock rom of tmobile US
And the recovery flash you did earlier was wrong..
You need to keep that recovery file in the adb folder (it should be in pc) Then the command will fetch the file.. As you have kept it on top of sdcard.. It can't find it..
Sent from my pyramid.. Through blazing fast sonic waves

Can't flash JB roms on HTC One S C2

First of, a bunch of thanks to you for helping me get from a complete and utter noob to a just complete noob. Managed to root, install roms and get out of a LOT of soft bricks (i just don't give up!) with your awesome help, all by searching older posts. However, this time i find myself in a pickle.
I own an HTC One S C2 with Hboot 2.0.9, had stock ICS when i bought it with no option to update to JB (which is why i rooted it in the first place). Something about this particular version of the phone not being updated by HTC global, which i found out about after i bought it, duh. Anyway. I've tried installing JB roms from this thread http://forum.xda-developers.com/showthread.php?t=2239265 with no luck. Phone just keeps getting into HTC logo screen loops. Right now i am on backtobasics v3 rom. Here's how i tried installing them JB roms and also the rom i am using right now (using TWRP 2.4.1 because newest version wouldn't work with backtobasics rom):
(note: some roms had sliiiightly different directions, i just followed each and every one's description closely)
1) Download Rom.zip
2) Extract boot.img from Rom.zip to fastboot folder
3) Enter Recovery
4) Mount SD card
5) Copy Rom.zip to SD card
6) Unmount
7) Wipe data, system, cache, dalvik cache and factory reset
8) Install Rom.zip
9) Reboot Bootloader
10) Go to fastboot USB mode
11) dem commands: fastboot flash boot boot.img then fastboot erase cache then fastboot reboot
12) BOOM! HTC LOGO LOOPS!
I've also tried installing a RUU but i couldn't find any for my CID. Then i thought about getting a SuperCID but, frankly, i scrached that thought the minute i saw the how to do it thread. Here's the phone info
version-bootloader: 2.09.0001
version-baseband: 16.05.20.24_M
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: FA335W400602
imei: 352911052281278
product: villec2
platform: HBOOT-8260
modelid: PJ4021000
cidnum: BSTAR301
battery-status: good
battery-voltage: 4170mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: f616909f
hbootpreupdate: 11
gencheckpt: 0
Thank you, in advance, for any advice you may be able to provide me with

Mkay, since i got no answer i went back to searching again! Unfortunately, i still have no asolution to my problem
From what i understand i have to: find a RUU to get from android version 4.0.3 up to JB version. Then i will be able to flash JB roms. But there is no RUU for CID BSTAR301.
I did find a thread with nandroid backup for a BSTAR301 which updates the version without a RUU but it was for HTC One X, i guess i shouldn't use that at all.
I am thinking about doing a SuperCID to install a RUU, then get back to my actual CID and flash a custom JB rom..
Would appreciate any advice

Tateh said:
Mkay, since i got no answer i went back to searching again! Unfortunately, i still have no asolution to my problem
From what i understand i have to: find a RUU to get from android version 4.0.3 up to JB version. Then i will be able to flash JB roms. But there is no RUU for CID BSTAR301.
I did find a thread with nandroid backup for a BSTAR301 which updates the version without a RUU but it was for HTC One X, i guess i shouldn't use that at all.
I am thinking about doing a SuperCID to install a RUU, then get back to my actual CID and flash a custom JB rom..
Would appreciate any advice
Click to expand...
Click to collapse
Yes, in your case S-OFF, Changing CID to something which has a JB RUU would do the trick. I think SuperCID is not necessary.
Sent from my Nexus 7 using Tapatalk HD

heakit Purpose
khan.orak said:
Yes, in your case S-OFF, Changing CID to something which has a JB RUU would do the trick. I think SuperCID is not necessary.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
THANK you! Currently trying to S-OFF it!

Tateh said:
THANK you! Currently trying to S-OFF it!
Click to expand...
Click to collapse
did you get S-OFF?

Not yet.. So exhausted. I tried the moonshine method but, just like trhe instructions state, i should have JB and be on stock for it to work properly, which is not possible since my phone has a BSTAR301 CID and is stuck on 4.0.3 with no stock roms available.
From what i've read, my only hope of S-OFF is to wait for the fellas working on Revolutionary method for S-OFF to release the correct version for this phone. I just hope it's soon and I thank them for their efforts, i'm so disappointed at this phone

Tateh said:
Not yet.. So exhausted. I tried the moonshine method but, just like trhe instructions state, i should have JB and be on stock for it to work properly, which is not possible since my phone has a BSTAR301 CID and is stuck on 4.0.3 with no stock roms available.
From what i've read, my only hope of S-OFF is to wait for the fellas working on Revolutionary method for S-OFF to release the correct version for this phone. I just hope it's soon and I thank them for their efforts, i'm so disappointed at this phone
Click to expand...
Click to collapse
same here. I just wrote to them asking for that

S-OFF done
I did S-OFF already. Now i need to know what CID put in my phone?? and which RUU install on it??
My MID is: PJ4021000
so i don't know if the Europe RUU's work in my phone. Maybe the radio have problem or no?? because the RUU say MID version: PJ4020000. Someone knows about this??

I have heard that JB update for BSTAR is now available.
Sent from my HTC One S using Tapatalk 4 Beta

khan.orak said:
I have heard that JB update for BSTAR is now available.
Sent from my HTC One S using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yeah it's done. But I would change CID not have to wait for another update Brightstar in so long.

gustavoegg said:
Yeah it's done. But I would change CID not have to wait for another update Brightstar in so long.
Click to expand...
Click to collapse
Be sure to match MID or you'll end up having problems with future updates.
Sent from my HTC One S using Tapatalk 4 Beta

Episcopal yupdfir
khan.orak said:
Be sure to match MID or you'll end up having problems with future updates.
Sent from my HTC One S using Tapatalk 4 Beta
Click to expand...
Click to collapse
Where i can find a RUU for Model ID: PJ4021000?? Because i need update for OTA after install the RUU

gustavoegg said:
Where i can find a RUU for Model ID: PJ4021000?? Because i need update for OTA after install the RUU
Click to expand...
Click to collapse
You have to manually check the ANDROID-INFO.TXT to match CID + MID
Sent from my HTC One S using Tapatalk 4 Beta

Tateh said:
First of, a bunch of thanks to you for helping me get from a complete and utter noob to a just complete noob. Managed to root, install roms and get out of a LOT of soft bricks (i just don't give up!) with your awesome help, all by searching older posts. However, this time i find myself in a pickle.
I own an HTC One S C2 with Hboot 2.0.9, had stock ICS when i bought it with no option to update to JB (which is why i rooted it in the first place). Something about this particular version of the phone not being updated by HTC global, which i found out about after i bought it, duh. Anyway. I've tried installing JB roms from this thread http://forum.xda-developers.com/showthread.php?t=2239265 with no luck. Phone just keeps getting into HTC logo screen loops. Right now i am on backtobasics v3 rom. Here's how i tried installing them JB roms and also the rom i am using right now (using TWRP 2.4.1 because newest version wouldn't work with backtobasics rom):
(note: some roms had sliiiightly different directions, i just followed each and every one's description closely)
1) Download Rom.zip
2) Extract boot.img from Rom.zip to fastboot folder
3) Enter Recovery
4) Mount SD card
5) Copy Rom.zip to SD card
6) Unmount
7) Wipe data, system, cache, dalvik cache and factory reset
8) Install Rom.zip
9) Reboot Bootloader
10) Go to fastboot USB mode
11) dem commands: fastboot flash boot boot.img then fastboot erase cache then fastboot reboot
12) BOOM! HTC LOGO LOOPS!
I've also tried installing a RUU but i couldn't find any for my CID. Then i thought about getting a SuperCID but, frankly, i scrached that thought the minute i saw the how to do it thread. Here's the phone info
version-bootloader: 2.09.0001
version-baseband: 16.05.20.24_M
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: FA335W400602
imei: 352911052281278
product: villec2
platform: HBOOT-8260
modelid: PJ4021000
cidnum: BSTAR301
battery-status: good
battery-voltage: 4170mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: f616909f
hbootpreupdate: 11
gencheckpt: 0
Thank you, in advance, for any advice you may be able to provide me with
Click to expand...
Click to collapse
Hi, I have same problem with you. Have you got any solution?

Unfortunately not yet, I switched back to my old xperia ray while i wait for the revolutionary team to release a version for HTC One S

[Q] HTC One X (Evita) 3.18 RUU for S-ON

I have had this great phone for around 3-4 months now. In the second week of owning it, I already unlocked the bootloader and rooted my phone. It is not S-OFF, because I'm under the impression that you need to buy extra hardware.
What I want to know is if there is any way that I can flash 3.18 RUU on my AT&T branded (but I use T-Mobile) evita? If there is, can you provide me with a link?
Again, I'm already rooted and I'm bootloader unlocked. Thanks

You don't need to buy any hardware or modify your phone physically to gain s-off, all you need to do is follow the instructions on this thread.
If you have SuperCID (which you most likely do) and try to RUU while you're s-on you'll brick your phone. So my advice is to go to the s-off thread I linked to before, and follow the instructions.
Once you've done that you can run the 3.18 RUU.
Sent from my Evita

Thanks, mate. I appreciate the fast answer. Naturally, I hate being left behind; and seeing that most of the new ROMs require S-Off for the 3.4 kernel, I decided it was time to upgrade. I'll give it a try, as I'm currently trying to flash a ROM because I mistakenly flashed one of ^. Now, it's stuck on the the HTC splash screen, and I guess it's just the first boot scenario. However, it has taken a curious amount of time.

Yeah it's pretty much gonna be essential from now on anyway so you might as well get it outta the way.
What ROM did you try to flash? Also, what firmware/hboot are you currently on?
Sent from my Evita

I tried flashing CarbonROM. It gave me that (Status 7) error so I figured it was the 3.4 kernel giving me problems. After that, I tried flashing a previous version of CarbonROM, and it'd just stay stuck in the splashscreen (This is the ROM that I was discussing in my previous post). Now I tried to flash RageXL, and it's bootlooping. So I'm figuring that I should just go to a stock ROM and get this procedure done, and THEN flash a custom ROM. #BadLuckw3r3w0lv33

Ok. Yep it's the fact that you haven't yet upgraded via the RUU that these ROMs won't boot. Try flashing something like MagioRom or ViperXL just to get the s-off procedure done.
Sent from my Evita

Hmph. I'm pretty sure I've downloaded the latest Google and HTC USB drivers. Still, when I enter "adb reboot bootloader", this pops up:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device offline
I have enabled USB debugging on my HOXL. Perhaps, it's the HTC Sync Manager? I have no clue beyond that point. I even tried restarting my phone AND computer.
EDIT: Nevermind, I just manually rebooted to the bootloader and continued from there. I am now S-Off

:thumbup:
Sent from my Evita

Btw.... If I helped you, please press the thanks button.
Sent from my Evita

Help me please
timmaaa said:
You don't need to buy any hardware or modify your phone physically to gain s-off, all you need to do is follow the instructions on this thread.
If you have SuperCID (which you most likely do) and try to RUU while you're s-on you'll brick your phone. So my advice is to go to the s-off thread I linked to before, and follow the instructions.
Once you've done that you can run the 3.18 RUU.
Sent from my Evita
Click to expand...
Click to collapse
Can i install 2.20 firmware after installing 3.8 firmware.. I have s-off and unlocked bootloader and had my AT&T htc one x evita rooted before i installed 3.18 firmware... please help i cant root my phone on 3.18....

hirias said:
Can i install 2.20 firmware after installing 3.8 firmware.. I have s-off and unlocked bootloader and had my AT&T htc one x evita rooted before i installed 3.18 firmware... please help i cant root my phone on 3.18....
Click to expand...
Click to collapse
If you are already s-off, just install custom recovery, then flash a rooted ROM or SU to get root.
Sent from my HTC One XL using xda app-developers app

Will this RUU work if I have a locked bootloader and s-on?

Chudawg62 said:
Will this RUU work if I have a locked bootloader and s-on?
Click to expand...
Click to collapse
As I said earlier in the thread, SuperCID + s-on + jb RUU = brick.
Sent from my Evita

guys can you please help me here?
my phone is
*** LOCKED ***
EVITA PVT SHIP S_OFF RL
CID-11111111
HBOOT-1.14.0002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Junn 11 2012,14:36:28
i dont understand thiss phone that well so can you please tell me if its safe to install the stock jellybean RUU on my phone?

Yes you're s-off so you can run the RUU with minimal risk.
Sent from my Evita

3.17 or 3.18?
Hi,
First off, thanks everyone - this forum has provided me a wealth of information.
I'm wondering if I can run non-sense based roms (ex. Cyanogenmod 10.2 or 11) without downgrading the touchpanel firmware. Here are my phone specs:
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.31a.32.45.16_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.08.111.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT27XXXXXXXX
(bootloader) imei: 359691XXXXXXXXX
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4050mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-de589c6eef
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Currently running ViperXL Android 4.2.2, stock kernel. Had to upgrade to HBOOT 2.15 to get rid of the random reboots and signal drop.
Before I upgraded HBOOT from 2.14 to 2.15 I was pretty sure I was on 3.17. I'm not even sure how to check this again? Would the upgrade to hboot 2.15 put me on 3.18? Sorry for the n0ob questions, help would be appreciated.

Current aosp ROMs no longer require you to down the ts firmware, they haven't since about June. You're a bit confused about the terminology, you didn't just upgrade to the 2.15 hboot, you upgraded to the 2.15 firmware, so you're currently on the 2.15 firmware. The hboot is only one component of the firmware as a whole.
Long story short, yes you can flash non-sense ROMs.
Sent from my Evita.

timmaaa said:
You don't need to buy any hardware or modify your phone physically to gain s-off, all you need to do is follow the instructions on this thread.
If you have SuperCID (which you most likely do) and try to RUU while you're s-on you'll brick your phone. So my advice is to go to the s-off thread I linked to before, and follow the instructions.
Once you've done that you can run the 3.18 RUU.
Sent from my Evita
Click to expand...
Click to collapse
can i run this RUU if i'm on CM10.2 ? and it says it will delete ALL from my phone, do i need to flash a rom and gapps right after i did that or will it still boot on CM10.2 ?

The RUU returns your phone to a stock configuration (ROM/recovery). You need to flash TWRP recovery again afterwards and then your ROM.
Sent from my Evita.

timmaaa said:
The RUU returns your phone to a stock configuration (ROM/recovery). You need to flash TWRP recovery again afterwards and then your ROM.
Sent from my Evita.
Click to expand...
Click to collapse
it doesn't work, i'm getting the usb connection error (170) but the cmd adb devices works just fine and the rumrunner s-off procedure went fine too...maybe i'm missing something ?

[Q] Stuck at HTC logo after failed stock update

Heyy, so i was wondering if yous could help me. I have a stock HTC Sensation EU, t-mobile version, which I had updated to the latest version (4.0.3 I think). During the upgrade-process something went wrong and now it doesn't go past the HTC logo. S-ON. When in Hboot it shows no found something.img. What is the way to fix this?
If possible I'd like to root it as well and use the Cyanogenmod.

HI, is it possible to you to go In Recovery Mod or Fastboot???
If it's yes,
Go here :
[GUIDE][N00b] Flash a ROM from 100% Stock!
This is a guide that give u all the way to unlock ur bootloader, change your stock recovery with a custom one (4ext).
Then u'll be able to install a ROM custom.
Here u can found a lot of ROM Developped for HTC SENSATION.
Sensation Android Development

blogodoblogodo said:
HI, is it possible to you to go In Recovery Mod or Fastboot???
If it's yes,
Go here :
[GUIDE][N00b] Flash a ROM from 100% Stock!
This is a guide that give u all the way to unlock ur bootloader, change your stock recovery with a custom one (4ext).
Then u'll be able to install a ROM custom.
Here u can found a lot of ROM Developped for HTC SENSATION.
Sensation Android Development
Click to expand...
Click to collapse
Seems good, i´ll try it out

blogodoblogodo said:
HI, is it possible to you to go In Recovery Mod or Fastboot???
If it's yes,
Go here :
[GUIDE][N00b] Flash a ROM from 100% Stock!
This is a guide that give u all the way to unlock ur bootloader, change your stock recovery with a custom one (4ext).
Then u'll be able to install a ROM custom.
Here u can found a lot of ROM Developped for HTC SENSATION.
Sensation Android Development
Click to expand...
Click to collapse
So it worked, but it didn't. I managed to install a custom rom, but after 10 seconds (if it even was that much), the system crashes and reboots, only to do the same thing again.
I used a RUU as well but I got a signing error (132) when using the RUU. I then tried installing the RUU through fastboot and I got further. I did however got the error saying the CID wasn't matching. In the .txt file from the zip I had added my CID, So I thought it had to work.
There is no official rom for my cid (T-MOB003) unfortunately.
This is starting to give me a headache

Search for this HERE

blogodoblogodo said:
Search for this HERE
Click to expand...
Click to collapse
Well DEFINITELY not there.
Those are Sensation XL.
Here's for our Sensation http://forum.xda-developers.com/showthread.php?t=1672425

Hoooooooo, Nooo,
Sorry ,really sorry
I googled "T-MOB003 for SENSATION"
Sorry DrNickjen
Thank You Nicx59

Nicx59 said:
Well DEFINITELY not there.
Those are Sensation XL.
Here's for our Sensation http://forum.xda-developers.com/showthread.php?t=1672425
Click to expand...
Click to collapse
I have read that once, but I'll do it again; this time more thorougly.
The RUU I'm trying to install is RUU_PYRAMID_ICS_HTC_Europe_3.32.401.5_Radio_11.69.3504.00U_11.22.3504.07_M_release_246089_signed
fastboot getvar all returns
Code:
c:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.18.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.50.114.2
(bootloader) serialno: xxx
(bootloader) imei: xxx
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: T-MOB003
(bootloader) battery-status: good
(bootloader) battery-voltage: 4104mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 9d24123f
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Since my cidnum is not in the RUU, (and there isn't a RUU for my cid) I'll have to add it according to the guide. I'll get to that later. hboot version to install and version-main are both higher than currently installed, so that shouldn't be an issue.
My phone is S-ON, but unlocked so I'll have to relock it again. Followed instructions and device is *** RELOCKED ***. Displays, however, a security warning. I'll now proceed with the installation by executing the exe. If I'm right I should see an error.
Error: Customer ID incorrect, as expected. I'll now try to install manually.
Since my CID is different I'll change it in the .zip. 7z didn't allow me to change it in the archive itself so I've extracted the archive, changed android-info.txt to:
Code:
modelid: PG5813000
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__N34
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__A07
cidnum: HTC__304
cidnum: HTC__032
cidnum: HTC__016
cidnum: T-MOB003
mainver: 3.32.401.5
hbootpreupdate:12
DelCache:1
Note: When pasting this my CID was placed on the same line as mainver. Inserted an enter and repasted in android-info.txt.
What I did as well was unlock the bootloader again, changed recovery to the file inside the rom.zip, and relocked the bootloader. I read this was a fix for the problem.
THIS POST IS IN PROGRESS

HI its not necessary to show ure imei, plz, edit your post and Erase it.

blogodoblogodo said:
HI its not necessary to show ure imei, plz, edit your post and Erase it.
Click to expand...
Click to collapse
Thanks.

Just Hit ThAnks Button
So For you, is it good???

blogodoblogodo said:
Just Hit ThAnks Button
So For you, is it good???
Click to expand...
Click to collapse
Nope. I gave up fot the day because I couldn't het the PG58IMG flashed. It didn't have an effect in hboot so I tried using fastboot but i got an unknown error. The tries installing ViperS 2.0, which succeeded. On boot, however, the system crashed and rebooted automatically, just like the other rom's i've tried.
If only I could get a rom working...

DrNickjen said:
Nope. I gave up fot the day because I couldn't het the PG58IMG flashed. It didn't have an effect in hboot so I tried using fastboot but i got an unknown error. The tries installing ViperS 2.0, which succeeded. On boot, however, the system crashed and rebooted automatically, just like the other rom's i've tried.
If only I could get a rom working...
Click to expand...
Click to collapse
actually if you are still on gingerbread firmware you can't boot any ics or jb rom
flash this rom from recovery
http://d-h.st/bqL
if you still want to upgrade to ics then S-OFF the device from here
http://revolutionary.io/
after that flash 3.33 universal from here
http://forum.xda-developers.com/showthread.php?t=1459767
follow the instructions to the letter
and before flashing check md5 sums(important)
then flash any ics or jb rom from recovery

rzr86 said:
actually if you are still on gingerbread firmware you can't boot any ics or jb rom
flash this rom from recovery
http://d-h.st/bqL
if you still want to upgrade to ics then S-OFF the device from here
http://revolutionary.io/
after that flash 3.33 universal from here
http://forum.xda-developers.com/showthread.php?t=1459767
follow the instructions to the letter
and before flashing check md5 sums(important)
then flash any ics or jb rom from recovery
Click to expand...
Click to collapse
Flashed it using Cwm, first did a full wipe and it installed fine. It then booted en got to a black screen and rebooted. Wiping Dalvik cache + /cache didn't work as a solution.
Same thing as any other .zip I've installed through recovery.

DrNickjen said:
Flashed it using Cwm, first did a full wipe and it installed fine. It then booted en got to a black screen and rebooted. Wiping Dalvik cache + /cache didn't work as a solution.
Same thing as any other .zip I've installed through recovery.
Click to expand...
Click to collapse
can you post your bootloader details again and what rom did you try to flash now?
also did you try to follow the steps i gave you?

rzr86 said:
can you post your bootloader details again and what rom did you try to flash now?
also did you try to follow the steps i gave you?
Click to expand...
Click to collapse
UNLOCKED
Pyramid PVT SHIP S-ON RL
HBOOT-1.18.000
eMMC-boot
August 2nd 2011
Tried to flash the rom you linked to and yes I have.

DrNickjen said:
UNLOCKED
Pyramid PVT SHIP S-ON RL
HBOOT-1.18.000
eMMC-boot
August 2nd 2011
Tried to flash the rom you linked to and yes I have.
Click to expand...
Click to collapse
change the recovery to 4ext
before flash the rom enable smartflash from 4ext

rzr86 said:
change the recovery to 4ext
before flash the rom enable smartflash from 4ext
Click to expand...
Click to collapse
I love you omg it worked <3 <3
So, what do I have to do in order to get e.g. Cyanogenmod running?

DrNickjen said:
I love you omg it worked <3 <3
So, what do I have to do in order to get e.g. Cyanogenmod running?
Click to expand...
Click to collapse
First make a full backup of your device through 4ext.
Then just flash the zips from one of the following releases:
android1234567's release (here you have to flash rom and kernel seperately)
albinoman887's releease
And last flash gapps from here

DrNickjen said:
I love you omg it worked <3 <3
So, what do I have to do in order to get e.g. Cyanogenmod running?
Click to expand...
Click to collapse
see my previous post of what to do now
S-OFF
flash 3.33 universal(check md5 sums before flashing)
flash cyanogenmod rom
done
note:when you achieve S-OFF you won't need anymore the smartflash feature

Help i killed my Phone:D

I was on Maximus HD 10.0
Then i tried another rom. but i don't like, so i downloaded 10.2 latest nightly but it on my internal storage-->full wipe-->and then i can't install cm10.2 then i want to but another rom on my internal storage but i can't put anything on the phone without an running rom...
then i changed my recovery to CWM 6. cause i knower there was an option to mount usb storage, but it don't work nothings happened when i click on it. Pleas help me i can do nothing
Some more Infos:C:\test>fastboot getvar all
version: 0.5
version-bootloader: 2.16.0000
version-baseband: 1.20.50.05.16
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-OFF
serialno: *************
imei: **************
product: vle
platform: HBOOT-8960
modelid: PJ4010000
cidnum: 11111111
battery-status: good
battery-voltage: 4128mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-4958290506
hbootpreupdate: 11
gencheckpt: 0
all: Done!
finished. total time: 0.078s

Jojo1992 said:
I was on Maximus HD 10.0
Then i tried another rom. but i don't like, so i downloaded 10.2 latest nightly but it on my internal storage-->full wipe-->and then i can't install cm10.2 then i want to but another rom on my internal storage but i can't put anything on the phone without an running rom...
then i changed my recovery to CWM 6. cause i knower there was an option to mount usb storage, but it don't work nothings happened when i click on it. Pleas help me i can do nothing
Some more Infos:C:\test>fastboot getvar all
version: 0.5
version-bootloader: 2.16.0000
version-baseband: 1.20.50.05.16
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-OFF
serialno: SH26RW404047
imei: 359901049107937
product: vle
platform: HBOOT-8960
modelid: PJ4010000
cidnum: 11111111
battery-status: good
battery-voltage: 4128mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-4958290506
hbootpreupdate: 11
gencheckpt: 0
all: Done!
finished. total time: 0.078s
Click to expand...
Click to collapse
I hope this Infos can help to solve my Problem, i have access via Fastboot!
The best would be if i can go back to stock.

Jojo1992 said:
I hope this Infos can help to solve my Problem, i have access via Fastboot!
The best would be if i can go back to stock.
Click to expand...
Click to collapse
You need the old firmware like you had before you updated to Maximus.
Run a RUU.exe and clear storage/factory reset in bootloader when you have the stock recovery back on.
From your other thread I posted more details
http://forum.xda-developers.com/showpost.php?p=47586067&postcount=7

tivofool said:
You need the old firmware like you had before you updated to Maximus.
Run a RUU.exe and clear storage/factory reset in bootloader when you have the stock recovery back on.
From your other thread I posted more details
http://forum.xda-developers.com/showpost.php?p=47586067&postcount=7
Click to expand...
Click to collapse
i downloaded an 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
then i make this:
fastboot devices
fastboot oem lock
then start RUU, but error no connection to device but in cmd i get a connection

I have a CID 111111 is that the Problem?

Jojo1992 said:
I have a CID 111111 is that the Problem?
Click to expand...
Click to collapse
I've never changed my CID, no need to. So I'm not an expert.
But from what I have read here:
"You can use any ruu while s-OFF, just simply plug phone to computer and run ruu. No need to relock bootloader.
For the supercid, it is recommended to change it back to original with fastboot command.
Fastboot oem write cid xxxxxxxx.
There has been a few bricks takin Jb ota while still supercid. "
So, not a problem, unless you install a OTA (over the air) update while SuperCid.
Here's a good guide from another forum
http://androidforums.com/one-s-all-things-root/691874-guide-how-run-ruu-your-htc-one-s.html
Glancing at that, I noticed it recommends running the RUU on the PC as administrator, maybe it's something simple like that.

tivofool said:
I've never changed my CID, no need to. So I'm not an expert.
But from what I have read here:
"You can use any ruu while s-OFF, just simply plug phone to computer and run ruu. No need to relock bootloader.
For the supercid, it is recommended to change it back to original with fastboot command.
Fastboot oem write cid xxxxxxxx.
There has been a few bricks takin Jb ota while still supercid. "
So, not a problem, unless you install a OTA (over the air) update while SuperCid.
Here's a good guide from another forum
http://androidforums.com/one-s-all-things-root/691874-guide-how-run-ruu-your-htc-one-s.html
Glancing at that, I noticed it recommends running the RUU on the PC as administrator, maybe it's something simple like that.
Click to expand...
Click to collapse
I changed my CID back to HTC__102
and tried zwo different RUU.exe one ICS on JB but both have an error...
i relocked my boot loader how can i unlock again?

Jojo1992 said:
I changed my CID back to HTC__102
and tried zwo different RUU.exe one ICS on JB but both have an error...
i relocked my boot loader how can i unlock again?
Click to expand...
Click to collapse
When trying the RUU did you go to bootloader (fastboot USB)?
To Unlock
Locate your Unlock_code.bin on your pc, probably saved it somewhere or it is still in your fastboot folder.
Type this into your command prompt window fastboot flash unlocktoken Unlock_code.bin
or go through the process of getting a new one http://forum.xda-developers.com/showthread.php?t=1583427
Nice tool (Windroid)
http://forum.xda-developers.com/showthread.php?t=2471151

tivofool said:
When trying the RUU did you go to bootloader (fastboot USB)?
To Unlock
Locate your Unlock_code.bin on your pc, probably saved it somewhere or it is still in your fastboot folder.
Type this into your command prompt window fastboot flash unlocktoken Unlock_code.bin
or go through the process of getting a new one http://forum.xda-developers.com/showthread.php?t=1583427
Nice tool (Windroid)
http://forum.xda-developers.com/showthread.php?t=2471151
Click to expand...
Click to collapse
Yes I was in fast boot USB
I will try it one time again and when it don't work then unlock again

Jojo1992 said:
Yes I was in fast boot USB
I will try it one time again and when it don't work then unlock again
Click to expand...
Click to collapse
Oh yeah, I've also read from someone that they got error 155 then they flashed stock recovery and relocked bootloader and then RUU proceeded to work.

tivofool said:
Oh yeah, I've also read from someone that they got error 155 then they flashed stock recovery and relocked bootloader and then RUU proceeded to work.
Click to expand...
Click to collapse
I unlocked and now i could flash:
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
that worked for me.
So which is the latest CM what i could install now?
Hboot: 1.14.0002
UNLOCKED
S-OFF
Running:
Android 4.0.4 HTC Sense4.1 Softwarenumber:2.31.401.5

Jojo1992 said:
I unlocked and now i could flash:
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
that worked for me.
So which is the latest CM what i could install now?
Hboot: 1.14.0002
UNLOCKED
S-OFF
Running:
Android 4.0.4 HTC Sense4.1 Softwarenumber:2.31.401.5
Click to expand...
Click to collapse
Glad you were able to get the RUU working. But right now you won't be able to flash many ROMs with that low of a Hboot. You will need to update the firmware.
Since you put your CID back, you would have to put back stock recovery and relock bootloader. Then you could go through settings and do the OTA to update to 2.15 hboot.
Or...this firmware update thread
http://forum.xda-developers.com/showthread.php?t=2322755

tivofool said:
Glad you were able to get the RUU working. But right now you won't be able to flash many ROMs with that low of a Hboot. You will need to update the firmware.
Since you put your CID back, you would have to put back stock recovery and relock bootloader. Then you could go through settings and do the OTA to update to 2.15 hboot.
Or...this firmware update thread
http://forum.xda-developers.com/showthread.php?t=2322755
Click to expand...
Click to collapse
where can i find stock recovery?
flash it like this or?: fastboot flash recovery recover.img
and relock bootloader with: fastboot oem lock ???

Jojo1992 said:
where can i find stock recovery?
flash it like this or?: fastboot flash recovery recover.img
and relock bootloader with: fastboot oem lock ???
Click to expand...
Click to collapse
There is a stock recovery here
http://www.modaco.com/topic/353006-...ch-recovery-for-the-htc-one-s-stock-download/
The SECOND download is the stock one
Unless you change the name of the recovery the command will probably look more like this:
fastboot flash recovery ville_recovery_signed.img
And yes
fastboot oem lock
after you have flashed the stock recovery of course

tivofool said:
Since you put your CID back, you would have to put back stock recovery and relock bootloader. Then you could go through settings and do the OTA to update to 2.15 hboot.
[/url]
Click to expand...
Click to collapse
Or he could just change cid to HTC__001 and flash jb ruu. (The European version)
Sent from HTC One S using android 4.2.2 sense 5

tominozh said:
Or he could just change cid to HTC__001 and flash jb ruu. (The European version)
Sent from HTC One S using android 4.2.2 sense 5
Click to expand...
Click to collapse
That don't work
I tried:
RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4
I will try it over ota now --> my Handy ist loading the update 4.1.1 i will report as soon as it is ready
Ok edit:
Hboot 2.15.0000
Unlocked
can i now flash CM10.2?
O.T.: Is CM10.2 running stable?

Jojo1992 said:
That don't work
I tried:
RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4
I will try it over ota now --> my Handy ist loading the update 4.1.1 i will report as soon as it is ready
Ok edit:
Hboot 2.15.0000
Unlocked
can i now flash CM10.2?
O.T.: Is CM10.2 running stable?
Click to expand...
Click to collapse
Eh.. It is stable besides for some bootlooping. Like you start it up and it bootloops a few times before finally loading. I like the Avatar Rom which is CM 10.2 based, and noticed a little bootlooping. But it wasn't terrible, just something that happened a few times.
So if that doesn't bother you, go for it. Other than that you would need to stick with sense based roms for stability.
Gosh, so many to choose from you will have to try some out.
http://forum.xda-developers.com/showthread.php?t=2243895

tivofool said:
Eh.. It is stable besides for some bootlooping. Like you start it up and it bootloops a few times before finally loading. I like the Avatar Rom which is CM 10.2 based, and noticed a little bootlooping. But it wasn't terrible, just something that happened a few times.
So if that doesn't bother you, go for it. Other than that you would need to stick with sense based roms for stability.
Gosh, so many to choose from you will have to try some out.
http://forum.xda-developers.com/showthread.php?t=2243895
Click to expand...
Click to collapse
Is the Avatar Rom really 10.2 based? cause on their page they tell 10.1 based or?
but i can install now any rom or?
with the flashed rue which i have actually i don't get mobile internet working. just wlan

Jojo1992 said:
Is the Avatar Rom really 10.2 based? cause on their page they tell 10.1 based or?
but i can install now any rom or?
with the flashed rue which i have actually i don't get mobile internet working. just wlan
Click to expand...
Click to collapse
Ya, guess you are right, 10.1
You can flash any as long as they don't require hboot 2.16 (which they state in the first page OP)

tivofool said:
Ya, guess you are right, 10.1
You can flash any as long as they don't require hboot 2.16 (which they state in the first page OP)
Click to expand...
Click to collapse
ok thank you very much for the help!