Database Info

[Q] virtous quattro

Hello people. I am using the HTC sensation z710e and it is running the sense o maniac ics room but I am having trouble flashing the virtuous quattro rc2 Ro. I downloaded the kernel for it and firmware and everything but when I try to flash it it just comes up cannot assertand some codes . Any body have a solution. And yes I wiped the data cache and dalvik cache before and restarted .

First of all do a nandroid backup. Then try to download files again, check md5 sum. Before flashing new rom make a full wipe. Hope this helps you

First make shure you Super CID your phone: http://forum.xda-developers.com/showthread.php?t=1192300 Step 4.
Then you need to flash the firmware directly from HBoot not in CWM oder something like this. look at http://forum.xda-developers.com/showthread.php?t=1412618 for more information. you need to place PG58IMG.zip on the top of your SDCard then you can flash it over HBoot...

hm im confused, ive already done a full backup and done the thing with file PG518.zip in hboot but iit still doesnt work.

Which firmware did you use? Quattro alpha2 and alpha3 need different firmwares.

im using the one ono there page, comb_keneral-WOB, if you know if its a different one can you please give me the link? you will be thanked XD OH FYI im now using the alpha 2 file again.

For Virtuous Quattro alpha 2, you should use this firmware.

THANK ALL OF YOU. YOU EACH GOT A THANKS. But..... I flashed it sucessfully ETC and when I rebooted the phone it is stuck as the virtous quattro blue image. It is not bricked as i pulled out the battery and it could go into the hboot menu thing. Anything? It;s been like this for 20 minutes and I dont know how much longer my battery will last

sensation lover said:
THANK ALL OF YOU. YOU EACH GOT A THANKS. But..... I flashed it sucessfully ETC and when I rebooted the phone it is stuck as the virtous quattro blue image. It is not bricked as i pulled out the battery and it could go into the hboot menu thing. Anything? It;s been like this for 20 minutes and I dont know how much longer my battery will last
Click to expand...
Click to collapse
Did you superwipe before flashing the ROM? Probably a good idea in the circumstances.

yeah i did that wipe already but it still isnt booting, i flashed back to the sense o maniac (sense 3.5 +android 4.0.3) rom and it worked. I tried ot flash back but it just gets stuck at the boot, still can charge when off and go into recovery. WHY inst this working for me !!!

I had the same issues after flashing the newest firmware (updatet 20.1) with alpha2 just wipeted everything und installed alpha3, After that it worked great.
Sent from my HTC Sensation using XDA App

el_fixit said:
I had the same issues after flashing the newest firmware (updatet 20.1) with alpha2 just wipeted everything und installed alpha3, After that it worked great.
Sent from my HTC Sensation using XDA App
Click to expand...
Click to collapse
That's what I was going to suggest next
Wipe --> 3.24 firmware --> Quattro alpha3.

Jellytime v7 not booting

Hi,
as the title says I cant get jellytime to boot on my DS. I did a full wipe and flashed boot image, since I am HTCdev unlocked and s-on. Do any of you experience the same problem/ is there a solution to this problem?
I would have posted this in the jellytime thread, but i have not met my 10 posts quotum yet.
Thanks :fingers-crossed:

Stupid question, but did you flash the Rom between full wipe and flash boot.img?

eyahl said:
Stupid question, but did you flash the Rom between full wipe and flash boot.img?
Click to expand...
Click to collapse
yes is wiped, then installed the rom and then flashed boot image. also downloaded the rom again, and tried a couple clean installs but no luck. im sure i use the right boot image.

Upgrade your hboot, goodness me. they are tutorials all over the development and general section. I personally lean to revolutionary 7.x
Sent from my HTC Desire S using xda app-developers app

my hboot is 2.00.002, i thought that was good. am i wrong?

did you download from the OP link or a mirror provided in the thread, as I read there was issue with corrupt mirror in thread.
I suggest that you consider re-downloading or check md5sum of your download , could be you corrupt which would explain.

i checked md5sum and others who downloaded from there were able to boot, so i dont think that is the issue

giel123 said:
Hi,
as the title says I cant get jellytime to boot on my DS. I did a full wipe and flashed boot image, since I am HTCdev unlocked and s-on. Do any of you experience the same problem/ is there a solution to this problem?
I would have posted this in the jellytime thread, but i have not met my 10 posts quotum yet.
Thanks :fingers-crossed:
Click to expand...
Click to collapse
That's problem with s-on. Did you reflash boot image in fastboot? fastboot flash boot boot.img (from jellytime.zip you just installed, first install jellytime.zip and than reflash boot.img in fastboot, it works. If you want to restore previous version, you need to reflash boot.img from that version as S-ON phone cannot write boot partition in recovery.)

Try doing full wipe, then flash boot.img and flash the rom last. That should work. Try using boot.img flasher software. It worked for me
Sent from my HTC Desire S using xda premium

giel123 said:
Hi,
as the title says I cant get jellytime to boot on my DS. I did a full wipe and flashed boot image, since I am HTCdev unlocked and s-on. Do any of you experience the same problem/ is there a solution to this problem?
I would have posted this in the jellytime thread, but i have not met my 10 posts quotum yet.
Thanks :fingers-crossed:
Click to expand...
Click to collapse
Or, if you have 4ext touch recovery and choosed the format all ( except sd ) function , that could be the problem. I noticed that, 4ext touch recovery's format all function sometimes didn't work properly! In that case you have to format the partitions individually. It happened to me with cooldroid. I used the format all function and sense kept crashing. When I formatted the partitions individually it worked!

johny.attila said:
Or, if you have 4ext touch recovery and choosed the format all ( except sd ) function , that could be the problem. I noticed that, 4ext touch recovery's format all function sometimes didn't work properly! In that case you have to format the partitions individually. It happened to me with cooldroid. I used the format all function and sense kept crashing. When I formatted the partitions individually it worked!
Click to expand...
Click to collapse
I've personally been using 4ext for over a year and have never experienced the problem you describe, I've probably used the format all (excluding sd) option hundreds of times...
if you genuinely believe there is an issue then report it on the 4ext thread
Sywepd form my DsereiS

It tought it's a common issue because I am not the only one, who experienced this That's the reason why I suggested to wipe individually

johny.attila said:
It tought it's a common issue because I am not the only one, who experienced this That's the reason why I suggested to wipe individually
Click to expand...
Click to collapse
I'm by no means having a go, just pushing the point as max the creator of 4ext would be keen to get any feedback on this issue..if it is one.
Who else has experienced the problem, do you have any thread references urls?
Sywepd form my DsereiS

One S[S4] wifi does not connect at any rom.

I rooted and unlocked my One S[S4] by this guide http://forum.xda-developers.com/showthread.php?t=1583427 and it went fine.
Wifi was working fine on stock Rom but when I flashed LeeDroid's Rom and booted the wifi didn't turn on. I just said error.
Then I tried Flashing Viper One S rom and no luck it gave the same error. I tried flashing the kernel and still didn't work.
Anyway I kept on trying different things and got the wifi to turn on but now it shows the connection but doesn't connect to it. It tries two three times and automatically turns off or the phone hangs and restarts.
Please help I need wifi and I can't get it to connect.
Baseband version: 1.08ts.50.02.16_10.08e.50.04L
Build Number: 2.31.401.5 CL81535

HELP!!
Anyone here can help me please. I'm stuck with this problem as I cannot find a direct solution and I have tried eveything I can but cannot get it to connect.

When you flashed it, did you flash the boot.img before, too? Do this!
And, also important: After each change of ROM, always also wipe "System" in Recovery! Maybe some ROMs don't do so automatically. And if you change from ROM A to ROM B, also factory reset your phone.
// you find the boot.img in the zip-file you flash
I would recommend to:
- choose a ROM (Viper?), transfer it to your sd-card
- get into bootloader, flash boot.img which comes in the zip-file
- from bootloader select recovery to boot (best use TWRP)
- go to wipe, choose to wipe system, androidsecure, dalvik- and cache and do a factory reset
- select install in recovery, install new ROM
I am pretty sure, everything will work after this

andryyyy said:
When you flashed it, did you flash the boot.img before, too? Do this!
And, also important: After each change of ROM, always also wipe "System" in Recovery! Maybe some ROMs don't do so automatically. And if you change from ROM A to ROM B, also factory reset your phone.
// you find the boot.img in the zip-file you flash
I would recommend to:
- choose a ROM (Viper?), transfer it to your sd-card
- get into bootloader, flash boot.img which comes in the zip-file
- from bootloader select recovery to boot (best use TWRP)
- go to wipe, choose to wipe system, androidsecure, dalvik- and cache and do a factory reset
- select install in recovery, install new ROM
I am pretty sure, everything will work after this
Click to expand...
Click to collapse
Yes, I flashed the boot.img before then flashed the ROM from recovery.
I just did a factory reset, did not specifically do the system wipe.
Let me try wiping the system and then flash the ROM. I'll get to you after trying.

akhrot91 said:
Yes, I flashed the boot.img before then flashed the ROM from recovery.
I just did a factory reset, did not specifically do the system wipe.
Let me try wiping the system and then flash the ROM. I'll get to you after trying.
Click to expand...
Click to collapse
Okay

you could flash the official RUU ，the problem will be solved…remember.，when you flash a ROM using recovery，you'd better format SYSTEM，that's important…
Sent from my HTC One S using xda app-developers app

andryyyy said:
Okay
Click to expand...
Click to collapse
I did exactly as you said but wifi doesn't connect. When I enter my wifi password it goes to connecting and quits stating the network out of range even when I'm standing besides the router and then it hangs and reboots.
All other things work fine, i.e bluetooth, mobile network etc.
I flashed the boot.img prior to flashing the ROM in TWRP. Wiped system, android.secure, cache and wiped data/factory reset. No luck.
I've no idea why is this happening. :S

harveychina said:
you could flash the official RUU ，the problem will be solved…remember.，when you flash a ROM using recovery，you'd better format SYSTEM，that's important…
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
The RUU is a .exe file and I'm on Ubuntu 12.10. I can't run RUU.
I borrowed a friend's laptop which was running on windows 7 but could'nt get the sync manager to sync my phone.
I'm stuck!!!

Strange .. you have neighbours you can ask to connect to their wifi for test?
Is your wifi "b/g" or "n" only?
Will write when I got another idea .. sorry.

andryyyy said:
Strange .. you have neighbours you can ask to connect to their wifi for test?
Is your wifi "b/g" or "n" only?
Will write when I got another idea .. sorry.
Click to expand...
Click to collapse
Yes, They can let me do that. I'll try that too.
Its b/g/n.
Its so frustrating, can't connect to wifi.
It's a T-Mobile phone with Hboot 1.14.0004 maybe this can help you think of something.
Thanks for your help.

akhrot91 said:
Yes, They can let me do that. I'll try that too.
Its b/g/n.
Its so frustrating, can't connect to wifi.
It's a T-Mobile phone with Hboot 1.14.0004 maybe this can help you think of something.
Thanks for your help.
Click to expand...
Click to collapse
Hey,
searched the Viper thread:
"Hello,
Did you do the 2.35 OTA from T-Mobile? If so then you can't get Wi-Fi working on any other rom then Trickdroid 7.0.0 or Stock 2.35. It all has to do with the way Wi-Fi is handled in 2.35 and hboot 1.14 not letting you downgrade those partitions.
You Could always SuperCID your phone and in stall the 2.31 RUU then install Viper. That has the same hboot so you shouldn't have any problems. I haven't tried this because I dont need to. Hope that helps.
Rsotbiemrptson"
To be sure, best wipe everything as before, then flash trickdroid 7.0.0
//edit: just editing CID is not enough, I guess .. I would modify mmcblk0p23 to 1.00.000.0 (see thread "downgrade/unbrick"), too. If that does not work, downgrade hboot, works fine. I think you are good with linux.

andryyyy said:
Hey,
searched the Viper thread:
"Hello,
Did you do the 2.35 OTA from T-Mobile? If so then you can't get Wi-Fi working on any other rom then Trickdroid 7.0.0 or Stock 2.35. It all has to do with the way Wi-Fi is handled in 2.35 and hboot 1.14 not letting you downgrade those partitions.
You Could always SuperCID your phone and in stall the 2.31 RUU then install Viper. That has the same hboot so you shouldn't have any problems. I haven't tried this because I dont need to. Hope that helps.
Rsotbiemrptson"
Click to expand...
Click to collapse
hi. I don't know this because I just got the phone from my cousin last night and he has no idea too. Where could check this if the OTA is done or not?
Okaaay. I tried Trickdroid v8.1.0 and it didn't work. I'm downloadiing the v7.0.0 right now to test it.
He must have dont the 2.30 OTA that's why wifi is not working on any other ROM.
Can you tell me a way other than virtual machine for me to apply the 2.31 RUU on Ubuntu/linux?

Shrink your ext3/4 partition using gparted and install win7
Virtualising and using "pass-through" will not work anyway. The phone switches its mode too often, you would need to "pass-through" it again and again.
You best use a laptop of a friend .. :/
But yes, try 7.0.0

So it worked?

andryyyy said:
Shrink your ext3/4 partition using gparted and install win7
Virtualising and using "pass-through" will not work anyway. The phone switches its mode too often, you would need to "pass-through" it again and again.
You best use a laptop of a friend .. :/
But yes, try 7.0.0
Click to expand...
Click to collapse
IT WORKED!! :laugh:
Thank you SO much andryyyy. I would've died without wifi on my phone.
Thanks again. :laugh::good:

Hi,
Try the following link
http://forum.xda-developers.com/showthread.php?t=2151142
I use Viper 2.1 and hboot 1.14.004. But, remember to use stock kernel when you flash your Viper rom.
Thank you

[Q] CyanogenMod 10.1 bootloop after installing new ROM

Hello everyone!
As the title said, I got a bootloop after trying to install Android 4.2.1 Jelly Bean.
How I did it:
1. Installed Android 4.2.1 Jelly Bean and Google apps for CyanogedMod 10.1 to my computer and transfered them to my phone's root.
2. Made a backup of the current version.
3. Installed first the ROM and then Google apps.
4. Rebooted my phone and now I got the bootloop.
I know that I didn't wipe data/cache/dalvik cache, that's probably the problem. I tried to resotre the backup I made but I get an error that says "MD5 mismatch!". I've also tried to wipe data/cache/dalvik cache and then install it again, I still get the same problem. The file isn't corrupted because I downloaded it several times and still same problem. I also tried to install it twice in a row but that doesn't work either. I can get into the bootloader and recovery menu.
Phone info:
HTC Desire S
HBOOT-2.00.0002
S-On
Revolutionary CWM v4.0.1.4
I'm pretty new to this so please give easy steps on what I could do.
Thank you!

As your phone is still s-on, you have to flash the boot.img (from the new rom) in fastboot every time you install a new rom.

teadrinker said:
As your phone is still s-on, you have to flash the boot.img (from the new rom) in fastboot every time you install a new rom.
Click to expand...
Click to collapse
Sorry for the noob question, but how do I do that?
EDIT: I forgot to mention that it bootloops on the CyanogenMod picture, not on the one with the HTC logo.

Google it... It has been mentioned innumerable times on this forum....
Tapatalked from Desire S running Andromadus

ipsvtt deciphers
Znipy said:
Sorry for the noob question, but how do I do that?
EDIT: I forgot to mention that it bootloops on the CyanogenMod picture, not on the one with the HTC logo.
Click to expand...
Click to collapse
dude, this is on the FIRST page of General forum
http://forum.xda-developers.com/showthread.php?t=1525100

And your MD5 mismatch almost certainly means that you created the NanDroid backup, then renamed it or moved it.

Everything works perfect now! Thank you!

Unable to boot after flashing ViperSAGA

Hello
After flashing (by mistake) ViperSAGA v1.1.0 update without v1.0.0 my phone didn't boot.
(1)The phone pass the splash HTC screen, turns black, restart and go into recovery.
So i tried to restore my backup (wich ran with RUU official ics) i get no errors but the phone did like previously (1)
i'm "**unlocked**" via HTC dev
HBOOT 2.02.002
I use CWM 5.0.2.0
I already read several post but i didn't find what to do.
I need help to revive my phone in any state (rooted, stock, any android version)
Sorry for bad english

boot.img?

I'm a noob, i don't know what is it or were can i find this...
Edit :
You mean i must try to flash boot.img from my backup ?

fastboot flash boot boot.img
Google it, don't ask me anything - I'm tired of answering the same all over again. Such a basic thing, and every week there's yet another noob that doesn't read.

Lee74 said:
I'm a noob, i don't know what is it or were can i find this...
Click to expand...
Click to collapse
Being 'A Noob' is no excuse for the failure/refusal of you and so many others to follow the Forum Rules - starting with;-
1. Search before posting.
Use one of our search functions before posting, whether you have a question or something new to share, it's very likely someone already asked that question or shared that news.
Click to expand...
Click to collapse
This is why people start to get fed up - at least a hundred people before you have asked the same question because they also failed to search or read before doing something.

.
GO into your recovery and wipe data, cache, dalvik cache and battery stats for best performance. Now flash ViperSAGA v1.0.0 then once that's installed you can flash v1.1.0 over it.
The reason why it stopped working is because v1.1.0 relies on all the apps and framework in v1.0.0 so it doesn't have many apps and just contains updates etc.
I hope this helped you. If it did, please click the thanks button!

Thanks for all your replies
I tried all you said :
-flash (fastboot) boot.img, reboot
or
-wipe data,cache... flash viperSAGA v1.0.0, flash viperSAGA v1.1.0, reboot
Nothing worked

Lee74 said:
Thanks for all your replies
I tried all you said :
-flash (fastboot) boot.img, reboot
or
-wipe data,cache... flash viperSAGA v1.0.0, flash viperSAGA v1.1.0, reboot
Nothing worked
Click to expand...
Click to collapse
Flashing the boot.img via fastboot should've helped.
Make sure you flashed the correct file, the one that is included in the zip file.
If the problem persists you could try other ROMs (I've been using CM10.1 by Flinny) or run ICS RUU.
Sent from my Desire S using xda app-developers app

I followed this guide http://forum.xda-developers.com/showthread.php?t=1525100 from step 4) and it worked, thanks all