Database Info

[Q] Phone shuts down.

My phone shuts down all by it's self once or twice a day. It occurs on multiple roms. I really want to find out why. Can someone tell me how I can log wat happens?
Since I don't know when and why it shuts down I would likely need a logger wich writes to a log file so I can look back what the problem is.
I suspect it to be a hardware problem... (Don't hope so but it happens on multiple roms)
Thanks everybody

What kernels have been used with the roms?
Sent from my HTC Sensation Z710e using XDA App

The used kernels were default kernels of the roms I used. Problem started wen using CM7 alpha. and now using Android Revolution with Faux123

Frazzy said:
My phone shuts down all by it's self once or twice a day. It occurs on multiple roms. I really want to find out why. Can someone tell me how I can log wat happens?
Since I don't know when and why it shuts down I would likely need a logger wich writes to a log file so I can look back what the problem is.
I suspect it to be a hardware problem... (Don't hope so but it happens on multiple roms)
Thanks everybody
Click to expand...
Click to collapse
Same for me, but ONLY with Revo HD ROM...

SadMac said:
Same for me, but ONLY with Revo HD ROM...
Click to expand...
Click to collapse
You don't have it in any other ROM?

I had the same problem before, I changed my kernel to bricked 0.91 and the problems are gone now.

I'm downloading Insertcoin rom now. I'll report back if the problem still occurs.

Frazzy said:
My phone shuts down all by it's self once or twice a day. It occurs on multiple roms. I really want to find out why. Can someone tell me how I can log wat happens?
Since I don't know when and why it shuts down I would likely need a logger wich writes to a log file so I can look back what the problem is.
I suspect it to be a hardware problem... (Don't hope so but it happens on multiple roms)
Thanks everybody
Click to expand...
Click to collapse
Change kernels. Go from 1.5ghz to 1.2 via daemon controller or another CPU adjuster.
The bricked 0.91 also fixes most issues too as stated above
Sent from my HTC Sensation in UR-Quan subspace.

Before you suspect Hardware.. Check first your software.. I'f i were you, i'll back up all my roms.. full / super wipe, then check it on by one.. lets say IC for first 2 days then ARHD on the 3nd-4th day.. If it does not shut down, it only means one thing, its not HARDWARE, it can be software.. Check also your chosen Kernel on your flashed ROM.. there might be an incompatibility running multiple different roms and kernels..
hope i'd help.. click thanks if i enlighten you so far..

Okay, I'm back from a weekend away.
What I did before I went away (Friday afternoon) is:
- Reboot to Recovery
- Wipe cache, wipe dalvik, wipe data
- install zip: Super-wipe (just to be sure)
- Install zip: InsertCoin 3.3.0
- install zip: InsertCoin 3.3.1
It all went well until Saturday evening. It was off when I got it out of my pocket. i tried to turn it on and it booted up. If it is on there is no problem at all. It stays on all the time...... Until I unlock my sim with my personal code. 2 seconds atfter that the phone turns off...
Since the problem reoccurred I tried the following things:
- Wipe cache, reboot (problem still exists)
- Wipe cache, wipe dalvik cache, reboot (problem still exists)
- Wipe cache, wipe dalvik cache, wipe data, reboot (problem still exists)
- Wipe cache, wipe dalvik cache, wipe data, Super-Wipe, re-install rom, reboot (problem still exists)
Is there a way to test the hardware to rule it out? The problem occurred in three different roms and got worse. I really can't see how this could be a software problem.
I'm now going to download the latest stock rom and see what happens...

I had the same problem I'm on tmobile sensation 4g in the us and I think all us sensations have the problem... When I was using any rom that was based on the experimental sense 3.5 base my phone would turn off/crash I tried all different Roms but the problem still occured, I though about it and installed revolution hd with sense 3.0 and still on the old base and the problem is gone. I'm waiting for the official release of the new sense 3.5. Hope it helps

I had the problem on 3.5 and non 3.5 based roms. CM7, Android revolution XE, android revolution sense 3.5 and Insert Coin XE sense 3.5. The last one I mentioned was the worst and I even couldn't get past the security code.
I now installed a shipped Rom. Let's see what happens.
In my first post I asked if there was a log file in which I can see why it shuts down. can anyone shed a light on that?

Frazzy said:
I had the problem on 3.5 and non 3.5 based roms. CM7, Android revolution XE, android revolution sense 3.5 and Insert Coin XE sense 3.5. The last one I mentioned was the worst and I even couldn't get past the security code.
I now installed a shipped Rom. Let's see what happens.
In my first post I asked if there was a log file in which I can see why it shuts down. can anyone shed a light on that?
Click to expand...
Click to collapse
I am having the same problems. I tried all of the same roms you have tried and as of last week I have decided to unroot my phone and return it to stock rom and recovery. after a week I am still getting the same random reboots. the only non stock part of my phone is that it is still S-Off, but I think im going to have to learn how to put stock S-On and go yell at the T-mobile guys to see if I can get a new phone.
If you can come up with anything better I would be willing to try it. the reboots are killing me.

This issue sucks. I'm glad I'm not the only one that has it though lol. I've also gone back to stock rom, no root/S-ON etc. Just to rule out the possibility that it's something funky going on with custom roms, kernels etc. So far I do still have random shutdowns, possibly a little less than I did before, but still there nonetheless. To get S-ON again, flash the RUU appropriate for your phone, then get into fastboot and type
fastboot oem writesecureflag 3
and then
fastboot reboot-bootloader
More on all this is here: http://forum.xda-developers.com/showthread.php?t=1201773
As far as logs to track down what is going on, I think it might be in lastkmsg. Unfortunately I don't know exactly where to find that or what to look for exactly.

And as stated twice before me, the problem still exists. I'm going to undo all changes to the Sensation and see what happens. If the problem is still there the phone will go back for warranty.
And again my old trustworthy HD2 saves the day as a backup...

I've never experience having a reboot with a super wipe then flashing a custom rom.. i do it almost everyday.. maybe its already a hardware since software installation (roms, and kernels) are clean when you do the flashing.. Has your phone experience some accidents? like fell on the ground?

Not that I know of.
I'm not new to flashing and I'm a real flashoholic. Nothing ever went wrong with flashing. Where other people would have problems with a certain ROM I could always enjoy the Rom without trouble.
I installed the eu version of the shipped roms. the problem seems to be different again. Nof it shuts down far less then before but I have to pull the battery to get it to boot up again.
I hope I have enough time today to S-on the phone. Does anybody know if the box states which version number it was shiped with? I know it's EU but there are different version numbers. (or is that not impotant)
Thanks for your help everybody.

I think the problem is the battery. I bought a new battery, the evo3d batery and so far I have not had this issue again.

Problem is solved. I got a free board swap and now everything is working again. So it was a hardware defect.
Thanks for the help all.

Constant Random Reboots

Hello!
So there is this annoying thing that's been going on since I firstly rooted my phone and started flashing ROM's, radios etc.
I've been using only ARHD ROM's since they have a great reputation, haven't tried others.
So, I started with ARHD 3.6.x ROM's and now I'm on the latest 6.2.1. XE ( No OC ).
So the problem for me all through my experience with my phone, is getting random reboots at mostly no specific times.
The most common is in this situation:
The phone is just sitting nicely in my pocket, I feel that somebody is calling me. I take the phone out of the pocket, want to answer by unlcoking the phone and ding! it just crashes.
When I turn it on, the random reboots just won't stop until I give the phone a rest and don't use it for a while. Because after a random reboot the reboots just keep on coming, if I use the phone.
This also happens when I just take the phone out of my picket and try to unlock it.
So, mostly it reboots when I try to unlock it.
This just makes the phone unreliable and many times people can't call me because I have no idea that it has crashed in my pocket.
I've been hoping that it would stop with the next version of ARHD but it didn't. The problem keeps comming back.
So I wanted to know: Is there any way to see, what is the soul purpose of those crashes? Is there anyway it's curable? Because I don't know if it's the HW or the SW. When I had stock everything and no root, these problems were not present.
My setup:
* Super CID
* Firmware from 3.24.401.1 & 3.25.401.101 RUU
* Android Revolution HD 6.2.1 XE
* Radio: 11.68.3504.00U_11.21.3504.13_2
* Kernel ( from about info ): 3.0.16-g5e58c5e [email protected] #1
* Any other info you need to help me fully?

the kernel could be the problem...try not to use it and see if it happens again..however i suggest to you to flash the insertcoin rom cause it is the best ics rom out there...trust me try it and you will not be disappointed

I have the same problem with all ROMs, including stock, except for the Virtuous Quattro alphas which I was able to run 20 days straight without a crash (impossible with other ROMs). Also the battery readings after a crash is weird, dropping from eg. 60% before the crash, down to 5% when booting after a crash. I contacted HTC about this and they told me it's probably a faulty mainboard. So I'm planning on sending it back in a few months.

I have the same problem with all sense roms GB and ICS its really frustrating I've had it for some time already
Sent from my HTC Sensation XE with Beats Audio using xda premium

Today I will try virtuous_quattro_alpha3_pyramid. If it's too buggy, will try the Inqusition. And if I still have any problem, give the InsertCoin a try. Will post my findigs as I get them.
Any idea what kernel to use? Which is the most stable?

not sure but crashes may have something to do with your applications being in sdcard. i have moved all my applications to phone memory (though i don't have many) and i have not had a forced reboot after that. also super-smooth/ultra-smooth rosie helped, with this tweak my phone is really fast now.
using leedroid rom.

If the phone didn't reboot on stock then it's a firmware/software issue - go back to fully stock and see if the problem still occurs.
If not then start from scratch and make sure the checksums match the downloaded file before you install then, especially the firmware and radio file.
From my hd2 days you might first try setting your network manually, as I did hear that even native Android phones can reset during auto network selection.

So now I am on Virtuos Inqusition and the reboots still occur. It's frustrating.
And ONLY when I take my phone out of my pocket to see what time is it.
So I met a guy who is on all stock, without root etc. and he's getting the same issues.
Anyone else having this problem?
Could it really be the HW fault?
Or still could just be because an official ICS ROM for the Sensation hasn't come out yet?

Full wiped?
Did you full wiped it before you upgraded to the latest verison? In many cases reason for reboots are kernel and/or cache related. So maybe something which is still in your cache could bring that output. Another possibility is when you restore apps and settings from System Tuner or Titanium backup. As you are using stock kernel I don't think it should be the problem generator.
1. Do a nandroid backup
2. Full wipe with Mike's script
3. Fresh install ICS rom you like (I'm using Insertcoin 4.5.4 + Ultrasmooth Rosie)
4. Check MD5
5. install custom ROM
6. Don't restore settings/apps from Google.
7. Don't restore apps/settings from Titanium etc...
Just try to use your phone without all your apps installed for a short time.
Good Luck, hope it helps...

Yes, I always Super-Wipe before a fresh install.
But I will re do everything, installing only the timetable for buses - addicted to that app.
Can I restore contacts from google or should that wait for a while?

Update
So, it's been a while that I've been using Virtous Inqusition with Google sync and nothing else. The original problem still exists, Could this be a HW issue?
I don't really want to go all stock to loose SuperCID and everything else.
So, I guess I have to stick with this problem and leave my Sensation unreliable.

Tomekks said:
So, it's been a while that I've been using Virtous Inqusition with Google sync and nothing else. The original problem still exists, Could this be a HW issue?
I don't really want to go all stock to loose SuperCID and everything else.
So, I guess I have to stick with this problem and leave my Sensation unreliable.
Click to expand...
Click to collapse
Do a full wipe and reflash the ROM also wipe the battery stats and perhaps try a different kernel maybe one closer to stock frequency
Sent from my HTC sensation 4g using Tapatalk

ICS Random Shutdowns

Hey guys, I'm having some issues on any ICS roms where my phone would shut down at around 50-60% battery and refuse to start back up. I'm running Virtuous Inquisition 4.0 after wiping everything in 4ext, using the Super CID and the firmware found here:
http://forum.xda-developers.com/showthread.php?t=1459767
After going back to Gingerbread, I don't have the issue anymore. Any idea what I could be doing wrong on ICS? I calibrate my battery each time I flash a ROM, so I have no idea what's going on here.

try a kernel with lower clock speed

Mb try different roms? Also you may try to change the kernel and wait for a 1 or 2 days to get your system stable. random boots definetely makes life harder.

For me, same problem. If battery is 60% turns off the sensation. When I restart, it boots up home screen, and turns off again. Only on the charger it goes again.
Stock Rom , Stock Bootloader, S=on
Google translate, sorry.

install this way i have not had that problem
http://forum.xda-developers.com/showthread.php?t=1542555
fresh install maybe idk but i had two phones and all good plus people on here doing it

Interesting Evo Design 4G dilemna created by my noobness

First off, I know I just signed up. I've been creeping for the past month or so.
So here is the situation:
Summary: I have a hardware problem on a rooted/unlocked htc evo design and have to return it to stock settings to return but have lost usb connection and cannot re-establish.
Hboot:
Unlocked
S-On
1.26.0000
Software Info:
version: 2.3.4
htc sense: 3.0
software number: DesignerEvo-0.5
Longer Version:
I bump into a tech-head tweak everything buddy of mine and he says i just have to "flash the new ics" to my phone.
15 hours of banging the head against the wall later i realize im trying to unlock/root/su/flash as though i have the evo 4g not the evo DESIGN 4g which i actually have. (and which i shortly discovered has nothing customized for it) After that I was off and away-ish...
so here is what i have done (don't mock me for saying it wrong):
- Unlocked the phone via htc dev site (it won't let me post links yet)
- Flashed/Installed Custom Recovery Clockwork mod 5.0.2.7
- Flashed su-2.3.6.3
- Flashed Designer Evo 0.5 found at sdx-developers (wont let me link)
- then for kicks flashed a a vaelek rom that said it was compatible-ish for the evo design from http://forum.xda-developers.com/showthread.php?t=1399351 it didnt see usb and other issues, so...
- then came back to Designer Evo
- installed setcpu to try to improve battery life...
Everything was fine for a couple of weeks (other than no ics and crappy battery life!)...
All of a sudden at random the phone powers off with battery reading charged. It will reboot, and within minutes power off again.
It does this in stock rom and custom.
If i keep it on charge it stays on.
If i remove it after charging, it holds power for a little while, but still powers off.
I thought conflict may have been between setcpu and a power savings app i had running and had forgotten to remove. removed, seemed to be okay then same.
I decided to come back on here figure out how to flash back to factory and unroot, and plugged it into computer (windows 7) via usb. "unknown device". reinstalled drivers. same problem. opened as ubuntu 11.x, still nothing. installed drivers nothing.
I dloaded a stock PH44img.zip w/ phone and put it on root and it would load at hboot, but do nothing after. may require s-off?
This is weird, I did a factory reset from recovery and on reboot it defaulted to the vaelek custom rom, so i went back to my oldest backup.
so... as i said, I think I have a hardware problem on a rooted/unlocked htc evo design and have to return it to stock settings to return but have lost usb connection and cannot re-establish.

Hang in there Vince...somebody is bound to point you in the right direction

I guessing people were off partying this weekend and have yet to respond?

ok this is crazy.... My design 4g is nowing doing the same thing.... Google brought me to this thread... anyone know anything?

Have you tried ruu'ing back to stock or flashing a different rom thru recovery
Sent from my PG06100 using xda app-developers app

shrekdaklown said:
Have you tried ruu'ing back to stock or flashing a different rom thru recovery
Sent from my PG06100 using xda app-developers app
Click to expand...
Click to collapse
Tried several roms . No luck..
tried to ruu via boot loader... It won't take. I may need to relock the boot loader.

Need help - any suggestions welcome!!!

Hi there,
I hope someone out there can help me fix my wife's sensation XE. We both have the same phone and generally the same ROM with no issues, but here's where we are now (apologies for length)
Background
A couple of months ago, she was running Viper 1.5.2. No issues, happy days
One day the screen just stopped responding while she was using either the official Facebook app or the stock browser (she can't remember which). She could wake the phone up but could not unlock it. The screen was perfectly responsive in recovery (4ext) so the problem was only apparent when the ROM was booted up.
I downloaded the latest version of Viper (as a more recent version had been released), fully wiped with superwipe.zip and flashed it.
Strangely, after flashing this, Aroma gave the option to reboot (as usual) and I selected yes, which then led to 'installation failed/installation aborted'. I then had to fully wipe again, flash the ROM again and say no to rebooting through Aroma, so I could manually reboot - which worked fine.
Unfortunately, the same problem with the screen was there right from the beginning as soon as the new version of Viper was booted up.
.
I went back to recovery and manually wiped data/cache/dalvik, as well as formatted system and boot, flashed the ROM again and it was still the same!!
I then fully formatted her SD card using Gparted and reflashed Viper, but it was still the same!!
I then went back to recovery, fully wiped everything again and flashed a different ROM (Elegancia 3.6.0 - sense 3.6) which worked fine straight away once it was booted up.
This seemed to clearly show that something about Viper ROMs had led to this.
Since then, I have flashed some other ROMs for her:
Elegancia 3.7.0 - worked fine
Viper 1.6.0 - screen locked up from the outset
Hypernonsense - worked fine
NB - Every time I flash any ROM, if the reboot option is selected in Aroma, the installation still fails. I have never, ever had this happen on my XE and I flash new ROMs all the time, from sense 3.6 to sense 4.x to MIUI.
The current problem
The problem is that her phone, is generally laggy, seems to run out of battery quickly and freezes a lot until it either catches up after several minutes (but is still then a bit laggy) or she has to pull the battery, regardless of what ROM she has been running. Again, mine has never had this problem and this has only been happening to her phone since the day that it first froze.
Her usage had not/has not changed, and the phone was running well before then, so I don't believe she is causing the lag/freezing/battery issues which she now has - it must stem from whatever caused the initial freeze on Viper 1.5.2.
I feel like due to the fact that full wipes, and formatting her SD card have not helped, the card cannot be the problem, plus I feel the fact that Aroma is no longer able to get the phone to reboot may point to a problem with the phone itself.
Can anyone help me to establish if there is a problem with the actual phone and if so, advise me if there is a way I can reflash/reset the phone itself, or whatever may be needed to get it back to how it was before this happened?
Also if it's not the phone itself and anyone might know what actually has happened, please, please enlighten me!!!
Many thanks for reading this and thanks in advance for any replies.
wildcardspv

wildcardspv said:
Hi there,
I hope someone out there can help me fix my wife's sensation XE. We both have the same phone and generally the same ROM with no issues, but here's where we are now (apologies for length)
Background
A couple of months ago, she was running Viper 1.5.2. No issues, happy days
One day the screen just stopped responding while she was using either the official Facebook app or the stock browser (she can't remember which). She could wake the phone up but could not unlock it. The screen was perfectly responsive in recovery (4ext) so the problem was only apparent when the ROM was booted up.
I downloaded the latest version of Viper (as a more recent version had been released), fully wiped with superwipe.zip and flashed it.
Strangely, after flashing this, Aroma gave the option to reboot (as usual) and I selected yes, which then led to 'installation failed/installation aborted'. I then had to fully wipe again, flash the ROM again and say no to rebooting through Aroma, so I could manually reboot - which worked fine.
Unfortunately, the same problem with the screen was there right from the beginning as soon as the new version of Viper was booted up.
.
I went back to recovery and manually wiped data/cache/dalvik, as well as formatted system and boot, flashed the ROM again and it was still the same!!
I then fully formatted her SD card using Gparted and reflashed Viper, but it was still the same!!
I then went back to recovery, fully wiped everything again and flashed a different ROM (Elegancia 3.6.0 - sense 3.6) which worked fine straight away once it was booted up.
This seemed to clearly show that something about Viper ROMs had led to this.
Since then, I have flashed some other ROMs for her:
Elegancia 3.7.0 - worked fine
Viper 1.6.0 - screen locked up from the outset
Hypernonsense - worked fine
NB - Every time I flash any ROM, if the reboot option is selected in Aroma, the installation still fails. I have never, ever had this happen on my XE and I flash new ROMs all the time, from sense 3.6 to sense 4.x to MIUI.
The current problem
The problem is that her phone, is generally laggy, seems to run out of battery quickly and freezes a lot until it either catches up after several minutes (but is still then a bit laggy) or she has to pull the battery, regardless of what ROM she has been running. Again, mine has never had this problem and this has only been happening to her phone since the day that it first froze.
Her usage had not/has not changed, and the phone was running well before then, so I don't believe she is causing the lag/freezing/battery issues which she now has - it must stem from whatever caused the initial freeze on Viper 1.5.2.
I feel like due to the fact that full wipes, and formatting her SD card have not helped, the card cannot be the problem, plus I feel the fact that Aroma is no longer able to get the phone to reboot may point to a problem with the phone itself.
Can anyone help me to establish if there is a problem with the actual phone and if so, advise me if there is a way I can reflash/reset the phone itself, or whatever may be needed to get it back to how it was before this happened?
Also if it's not the phone itself and anyone might know what actually has happened, please, please enlighten me!!!
Many thanks for reading this and thanks in advance for any replies.
wildcardspv
Click to expand...
Click to collapse
well, regarding the screen issue, use the battery all the way, til it shuts down. then rwmove the battery n press the powere button as if u were turning on ur phone. then let the phone be still over a night. then re-insert the battery n plug the phone into charge but BEWARE THAT U WILL NOT TOUCH THE SCREEN AT ALL, TIL IT'S FULLY CHARGED. i tried this solution, n it worked. maybe so did it for u :-??
n about the lags, i recommend u to install Seeder 2.00 which is recently released n can decrease the lags as much as possible. and also u could try out making 256/128MB swap with 100% swappiness using Kernel Tuner v4. alsi set these settings IN THE ORDER I'VE TYPED in venom tweaks --> misc --> minfree settings
4
8
16
32
48
64
got no more idea
------------------------------------------------
PRESS THE PRETTY "THANKS" BUTTON IF I HELPED
Sent from a shaked up HTC Sensation XE using xda premium

wildcardspv said:
Hi there,
I hope someone out there can help me fix my wife's sensation XE. We both have the same phone and generally the same ROM with no issues, but here's where we are now (apologies for length)
Background
A couple of months ago, she was running Viper 1.5.2. No issues, happy days
One day the screen just stopped responding while she was using either the official Facebook app or the stock browser (she can't remember which). She could wake the phone up but could not unlock it. The screen was perfectly responsive in recovery (4ext) so the problem was only apparent when the ROM was booted up.
I downloaded the latest version of Viper (as a more recent version had been released), fully wiped with superwipe.zip and flashed it.
Strangely, after flashing this, Aroma gave the option to reboot (as usual) and I selected yes, which then led to 'installation failed/installation aborted'. I then had to fully wipe again, flash the ROM again and say no to rebooting through Aroma, so I could manually reboot - which worked fine.
Unfortunately, the same problem with the screen was there right from the beginning as soon as the new version of Viper was booted up.
.
I went back to recovery and manually wiped data/cache/dalvik, as well as formatted system and boot, flashed the ROM again and it was still the same!!
I then fully formatted her SD card using Gparted and reflashed Viper, but it was still the same!!
I then went back to recovery, fully wiped everything again and flashed a different ROM (Elegancia 3.6.0 - sense 3.6) which worked fine straight away once it was booted up.
This seemed to clearly show that something about Viper ROMs had led to this.
Since then, I have flashed some other ROMs for her:
Elegancia 3.7.0 - worked fine
Viper 1.6.0 - screen locked up from the outset
Hypernonsense - worked fine
NB - Every time I flash any ROM, if the reboot option is selected in Aroma, the installation still fails. I have never, ever had this happen on my XE and I flash new ROMs all the time, from sense 3.6 to sense 4.x to MIUI.
The current problem
The problem is that her phone, is generally laggy, seems to run out of battery quickly and freezes a lot until it either catches up after several minutes (but is still then a bit laggy) or she has to pull the battery, regardless of what ROM she has been running. Again, mine has never had this problem and this has only been happening to her phone since the day that it first froze.
Her usage had not/has not changed, and the phone was running well before then, so I don't believe she is causing the lag/freezing/battery issues which she now has - it must stem from whatever caused the initial freeze on Viper 1.5.2.
I feel like due to the fact that full wipes, and formatting her SD card have not helped, the card cannot be the problem, plus I feel the fact that Aroma is no longer able to get the phone to reboot may point to a problem with the phone itself.
Can anyone help me to establish if there is a problem with the actual phone and if so, advise me if there is a way I can reflash/reset the phone itself, or whatever may be needed to get it back to how it was before this happened?
Also if it's not the phone itself and anyone might know what actually has happened, please, please enlighten me!!!
Many thanks for reading this and thanks in advance for any replies.
wildcardspv
Click to expand...
Click to collapse
Install TWRP (TeamWin Recovery Project) and use that to flash ViperS once more (after doing a full wipe of course). Since the only recovery that allows the installation of kernels on an S-ON device is 4ext, you will need to extract the boot.img file from the ViperS installer .zip and flash that using fastboot. Detailed instructions on how to flash a boot.img file through fastboot can be found here: http://forum.xda-developers.com/showthread.php?t=1752270
I don't really trust 4ext because 4ext gave me a lot of weird and nasty bugs. Using TWRP is worth a shot.