Related
Forgive me if I'm posting in the wrong section. Forgive me if I'm not allowed to post here yet. Just forgive me in general. I don't want to be banned or anything like that. I'm Extremely interested in android development.
I made a working port of ClockworkMod Recovery v5.0.2.8 for the Pantech Crossover. I wanted to do this before I started tinkering around with porting cm7.2. So that I would have a way to backup, restore, and flash new roms, etc... Or else when I make a noob mistake like yesterday and have a non booting phone resulting in having to flash my old boot.img with fastboot...anyways..
DANGER: DRAGONS AHEAD
FLASH AT YOUR OWN RISK
YOU HAVE BEEN WARNED
The method I used to flash the recovery was:
1)adb push recovery.img /sdcard/recovery.img
2)flash_image recovery /sdcard/recovery.img
3)repeat step 2 (for some reason it gave me a read error out of memory the first time)
Here's the link to the custom recovery:
http :// dl. dropbox .com /u/20070520/ recovery.img
I know I'm not supposed to post links yet. Remove spaces
I just hope that there are others with the Pantech Crossover that are interested in this and the possible future development of custom roms.
Also if anyone knows if there is a good way to get ahold of koush let me know, so I can give him what he needs to hopefully add this to Rom Manager. I couldn't message him on github because he doesn't have an email set up with it
And while I'm at it. Here's the method for rooting your crossover. I'm not going to provide the files since they can easily be found with a google search.
1: Find a copy of gingerbreak.apk and copy it to your sd card
2: Enable usb debugging and allow installation of non market apps
3: Install gingerbreak
4: Root device with Gingerbreak
5: You can uninstall Gingerbreak when its completed.
Sent from my rooted PantechP8000 using XDA
Thanks so much for this! I have a friend with a crossover and is always looking for my help with making it work better. I realize this is a newer thread, I was wondering how things were coming along with CM? Anything I can do to help perhaps?
crap i need a rom to fix my crossover the buttons are no longer mapped after a hard reset. please help.
Slow
Well, it's been slow goings so far. I downloaded the open source files for the p8000 and it looks like they just built the original rom from a generic build. I've been trying to get a more customized build setup but I need to do some more reading so far. One of the problems is that instead of an akmd(2) binary for orientation and compass it uses three separate modules. Plus the hci_attach is a bit different as well and so is the bluetooth. So that significantly hampers the ease of even a basic port.
As far as the gentleman with the question about a rom to fix your device. The best I can do right now is to upload a clockwork mod backup after I do a factory reset. I don't get much time to work on this between my wife and daughter.
Also, do you have adb access to your device? Surely it wouldn't be too difficult to adb push the correct keymapping files back to your phone.
You say a hard reset messed up your mappings? What problems were you experiencing prior to the reset?
Crossover
Hello,
I just wanted to let you know that there are people watching your thread. I am very interested in this as my parents have Crossovers and have recently rooted and unlocked them (well, I did) and set them up to work on Net10.
The only issue I've noted is that there are some failures, like the Market refusing to install apps no matter what is done. I'm going to install your ClockworkMod in hopes that later it might be useful.
I realize there isn't a large development scene for the P8k yet, and maybe there won't be but it's always a great hope that those with the capabilities might take pity. I was almost thinking that it might be my foray into actually looking deeper at the code than the small bit I've done.
Kind Regards,
Kaylus
Yup
kaylus said:
Hello,
I just wanted to let you know that there are people watching your thread. I am very interested in this as my parents have Crossovers and have recently rooted and unlocked them (well, I did) and set them up to work on Net10.
The only issue I've noted is that there are some failures, like the Market refusing to install apps no matter what is done. I'm going to install your ClockworkMod in hopes that later it might be useful.
I realize there isn't a large development scene for the P8k yet, and maybe there won't be but it's always a great hope that those with the capabilities might take pity. I was almost thinking that it might be my foray into actually looking deeper at the code than the small bit I've done.
Kind Regards,
Kaylus
Click to expand...
Click to collapse
I haven't had any problems with the market refusing to install apps but I do sometimes run across the no connection error with the market when on wifi. Although I did notice this before I rooted my crossover. Sometimes disabling and re-enabling the wifi helps. I really do think it is a bug somewhere in the original rom.
As far as the custom recovery image. Everything seems to be working pretty good. I use it mainly for restoring previous backups. I would say I've restored my backup at least a dozen times. Occasionally it states there was an error restoring .android secure but I have yet to track that down. I need to double check the recovery.fstab to make sure I have everything set right for the mount points.
stevotdo said:
I haven't had any problems with the market refusing to install apps but I do sometimes run across the no connection error with the market when on wifi. Although I did notice this before I rooted my crossover. Sometimes disabling and re-enabling the wifi helps. I really do think it is a bug somewhere in the original rom.
Click to expand...
Click to collapse
I'm actually completely stuck at this point. I'm rooted, unlocked, different carrier, APN set correctly. I can access data and voice -- but it just hangs at "Downloading..." on the market. If I factory reset it works initially but after reboot it fails. I'm not quite sure why this occurs and if it is just this phone or a side-effect of using it on a different carrier.
Strangely Wi-fi doesn't resolve it.
As far as the custom recovery image. Everything seems to be working pretty good. I use it mainly for restoring previous backups. I would say I've restored my backup at least a dozen times. Occasionally it states there was an error restoring .android secure but I have yet to track that down. I need to double check the recovery.fstab to make sure I have everything set right for the mount points.
Click to expand...
Click to collapse
I'll give your recovery a run and let you know, if you manage CM7 let me know I know it's a big undertaking. Thanks for the response.
Market Error
As far as the Android Market hanging. I see a few references to it being cause by the .android_secure folder becoming corrupted on the sd card.
One temporary fix suggest moving all the installed apk's back to the phone memory and deleting the .android_secure folder. Then rebooting and moving those apps back to the sd card.
That seems like some wasted time if it doesn't happen to work. I would just turn the phone off, remove the sdcard, and restart (granted any apps that were moved to the sdcard wont work until it is reinserted.) Then I would try to download and install an app. If that works then shutdown, insert sd, and reboot.
I'm really curious if the problems with .android_secure that you and i are having aren't just more bugs in the original rom.
Just as a poster above me said, I am watching this thread and really appreciate everything you are doing. Thanks again.
Well I appreciate the support. I just hope to be able to offer a rom sometime soon. Unfortunately I won't have anymore free time till Tuesday
crimson12 said:
Just as a poster above me said, I am watching this thread and really appreciate everything you are doing. Thanks again.
Click to expand...
Click to collapse
Not an issue, life first, then android development.
Sent from my Galaxy Nexus using Tapatalk
Pantech Crossover Update
Ahhhhh check out the pantech support page for the crossover. They finally have the Gingerbread update.
http:// pantechusa. com/xupgrade/ remove spaces.
Which is great because I soft bricked my phone (don't ask) and this was going to be the only way to fix it.
stevotdo said:
Ahhhhh check out the pantech support page for the crossover. They finally have the Gingerbread update.
http:// pantechusa. com/xupgrade/ remove spaces.
Which is great because I soft bricked my phone (don't ask) and this was going to be the only way to fix it.
Click to expand...
Click to collapse
Oh hell yes finally. Thanks for the notice!
Sent from my Galaxy Nexus using Tapatalk
Mildly related, but have you figured out how to root the gingerbread ROM? I've tried ginger break to no avail.
Sent from my Galaxy Nexus using Tapatalk 2
anyone have a stock image of the 2.2 for android my phone came preupgraded to 2.3.6 and i would like to have it rooted over being on gingerbread since a root method hasnt been found yet for the new firmware
Bricked?
I tried to use the pantech provided gingerbread update this morning. It got about an eighth of the way through and failed. It instructed me to reboot while holding volume up and home and power. That put it in software updating mode. I tried the upgrade 3 more times, it failed at the same point each time. Now my phone is stuck in S/W Updating mode and I can't seem to get it out. I've tried pressing volume up and down for 10 seconds, and pressing volume down and home while powering on, nothing seems to make a difference. Any thoughts about how to at least get me back to froyo?
formattdd said:
I tried to use the pantech provided gingerbread update this morning. It got about an eighth of the way through and failed. It instructed me to reboot while holding volume up and home and power. That put it in software updating mode. I tried the upgrade 3 more times, it failed at the same point each time. Now my phone is stuck in S/W Updating mode and I can't seem to get it out. I've tried pressing volume up and down for 10 seconds, and pressing volume down and home while powering on, nothing seems to make a difference. Any thoughts about how to at least get me back to froyo?
Click to expand...
Click to collapse
Nevermind, bad usb cable.
formattdd said:
Nevermind, bad usb cable.
Click to expand...
Click to collapse
Glad you got it working!
Sent from my Galaxy Nexus using Tapatalk 2
Yeah now I'm having the same regrets as above. No root.
Sent from my PantechP8000 using XDA
My wife has a droid charge this phone is 100% stock never been rooted at all. The phone keeps shutting off no matter what the charge is. its normally when she tried to take a pic I was thinking about rooting and installing a rom but not sure if this is more of a hardware issue
Try...
If it happens whenever she is trying to take a picture, perhaps there is a problem with the sd-card? I'd say first try reformatting the card through your phone, and then unmounting it, pulling it out and putting it back in; also try a different sd-card. If that doesn't seem to change anything, it could be a hardware issue, but before you send it back for a replacement I suggest you do a little test to see if it is indeed a hardware issue or a bad OS load. Go here: http://forum.xda-developers.com/showthread.php?t=1111486
and follow the instructions carefully. This will, using Odin, flash a brand new totally stock OS onto your charge & repartition, and it will not root your phone, very low risk. If after you do this the same issue is still present, it is probably a hardware issue and you should send it for a replacement. If you want to try that process and have any questions let me know.
PIT file that repartition your phone: http://www.imnuts.org/downloads/charge/odin/charge.pit
*Goes into PIT area of Odin
This is the stock file to download to get you a new unrooted copy of the stock rom that new droids are shipped with. (it is not the latest fp1 update you can just take that one OTA when you feel like it after you have flashed this):
http://www.imnuts.org/downloads/cha...L_ONE-LTE-CP_REV03_user_CL706183_ship.tar.md5
**Put into PDA section of Odin
jfl14609 said:
My wife has a droid charge this phone is 100% stock never been rooted at all. The phone keeps shutting off no matter what the charge is. its normally when she tried to take a pic I was thinking about rooting and installing a rom but not sure if this is more of a hardware issue
Click to expand...
Click to collapse
Have you done the new software FP1 OTA update yet? This should resolve your issue.
This is a known issue with the Charge. When the battery gets too low and you try to take a picture, the battery cannot supply enough amperage/voltage (I forget which) and it locks up. Undervolting your processor seems to alleviate this somewhat as it takes some load off the battery.
This has been established for some time, please search the forums...
Sent from my SCH-I510 using xda premium
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
Sooo it seems I have now bricked my beloved G2x. I have tried every recovery method on xda I can find (a few times), but still no luck.
I was trying to restore stock on my phone to catch the new OTA update, and it has failed...miserably.
Now, my phone gets to the little T-Mobile G2x splash screen and then reboots. I've tried NVflash'ing the firmware, I've tried kdz (which I absolutely cannot get to work right), I've tried sacrificing a chicken to the LG powers-that-be (okay, haven't tried that...YET), but nothing has worked.
Does anybody know of an absolute "unbrick" method?
Thanks in advance for the help!
Also, every now and then, the phone will actually make it to the initial "Touch the android to begin." screen, but my battery (which was 100% charged before this started) now says 0%, even when plugged in.
these links were in the first page of me searching "brick help"
http://forum.xda-developers.com/showthread.php?t=1611968&highlight=brick+help
http://forum.xda-developers.com/showthread.php?t=1180331&highlight=brick+help
http://forum.xda-developers.com/showthread.php?t=1619893&highlight=brick+help
I've tried those methods, and almost every other I could find. I've searched this forum for hours today before posting this, and no matter what I use, I get stuck in either a bootloop or i get a reboot after a minute of being booted. I've tried different recoveries, different ROMs, different flashing methods, and it all ends up the same way.
if you've actually tried things you might want to post exactly what you have tried what were the outcomes and so on and so on. I'm not going to assume what you have tried and assume what the process you did and where you might have messed up. I'm sure neither is anyone else. So unless you help me help you we together are not going to get anywhere.
To the best of my recollection, here's how it went down:
Started off with running Genesis v1 Beta 6.
Ran G2x batch clean up tool w/ CWM Touch
Flashed cyanogen_p999-ota.eng.feli.zip in CWM
* At this point my phone would not make it past more than 1 minute after booting. It would boot up, but after approx. 1 minute, it would reboot, no matter what I did w/ it. This happened several times
Wiped everything through CWM, flashed Genesis again (default install)
*Had same reboot issues listed above
Used NVFlash to push stock V21e firmware http://forum.xda-developers.com/showthread.php?t=1248644
*After this, My phone would not make it past the "T-Mobile G2x with Google" splash screen. You would hear the T-mobile jingle, then the screen would "get stuck" for about one minute, and then the phone would reboot and go through the LG logos to the splash screen and repeat endlessly until I performed a battery pull
Restored stock recovery using NVFlash
*Did a reboot and suddenly saw the boot animation from Genesis!? Not sure how that happened, but it never made it past the boot animation
Ran G2x batch clean up again to try to "clean" the phone, and pushed the V21e firmware again
*Same boot problem
Flashed stock recovery again, then attempted to use KDZ. KDZ will continue to force close midway through the operation, and I cannot get it to work
Pushed V21e yet again
*Now it started making it to the initial set-up "Touch the android..." dialog. I could actually make it through this part, and then the phone would reboot again
*Somewhere in the middle of this, my battery went from reading 95%(The few times it would actually boot) to reading 0%. I wiped battery stats in CWM, but it didn't fix it. "Hey, maybe my battery actually died," I thought, so it's now on the wall charger, waiting for me to try to rescue it again.
I'm going to *attempt* to install a nandroid in CWM, and pray that it fixes things, but if that does not work, I'm at a complete loss
mt3g said:
if you've actually tried things you might want to post exactly what you have tried what were the outcomes and so on and so on. I'm not going to assume what you have tried and assume what the process you did and where you might have messed up. I'm sure neither is anyone else. So unless you help me help you we together are not going to get anywhere.
Click to expand...
Click to collapse
+1
More info would be great!
If I were you, would give a shot of mansa_noob's clean up tool:
http://forum.xda-developers.com/showthread.php?t=1590523
It will reorganize your partitions. Then you just need to flash CWM recovery, then the stock ROM.
Edit:
Just saw your new post, wow that's interesting. I'm not too sure if the touch CWM has anything to do with it, how about to try the normal recovery version of the clean up tool, then maybe a different stock ROM?
Sent from my LG-P999 using xda premium
the only thing I can think of will get me flamed lol, don't use those clean up tools unless it is a last resort! I can say I've never had an issue with just flashing after going through mounts and storage (data, system,cache) and wiping the main things.
The fact that the phone can be booted and it is showing images on the screen means you are not bricked. On the other hand, I've yet to read the issues you are describing, ever. You got quite mess on your hands.
KDZ is your best bet, what do you mean it just "continues to force close"
DupleX01 said:
+1
Just saw your new post, wow that's interesting. I'm not too sure if the touch CWM has anything to do with it, how about to try the normal recovery version of the clean up tool, then maybe a different stock ROM?
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Tried CWM 5.0.2.0, also. I've tried both the stock ROM and the basic cyanogen ROM (Sorry, can't remember exactly where in the cycle those fell...I've repeated several steps several times)
Alright, so It's fixed! Thanks for the interest.
Just for the sake of somebody who (somehow) might have something similar, here's what fixed it....and be warned, this is QUITE unorthodox:
My phone was fully charged (turned off, showing the charged battery icon). I removed the battery, the SIM, and the SD card, and stuck my phone in the fridge for about 10 minutes...That's right, the fridge. I read somewhere that this may help when writing to the disk, and I figured "why not?"
I then pushed V21e using NVflash again, and, lo and behold, it works like a champ! Now just to get the latest OTA update, sit back, and wait for the latest and greatest ROMs to trickle down.
Also, sorry about the original post being kind of vague...It was posted after literal hours of searching and trying different things, and the frustration clouded my brain.
that is crazy lol, but glad something worked for you...
mt3g said:
the only thing I can think of will get me flamed lol, don't use those clean up tools unless it is a last resort! I can say I've never had an issue with just flashing after going through mounts and storage (data, system,cache) and wiping the main things.
The fact that the phone can be booted and it is showing images on the screen means you are not bricked. On the other hand, I've yet to read the issues you are describing, ever. You got quite mess on your hands.
KDZ is your best bet, what do you mean it just "continues to force close"
Click to expand...
Click to collapse
Hey buddy. I won't flame. You are absolutely right. I don't use the cleanup tool a lot either but then since my bluetooth issue is fixed I am slacking .
I am curious though why it did not work but will respond to op in a minute.
Sent from my LG-P999 using XDA
rtotheichie said:
Alright, so It's fixed! Thanks for the interest.
Just for the sake of somebody who (somehow) might have something similar, here's what fixed it....and be warned, this is QUITE unorthodox:
My phone was fully charged (turned off, showing the charged battery icon). I removed the battery, the SIM, and the SD card, and stuck my phone in the fridge for about 10 minutes...That's right, the fridge. I read somewhere that this may help when writing to the disk, and I figured "why not?"
I then pushed V21e using NVflash again, and, lo and behold, it works like a champ! Now just to get the latest OTA update, sit back, and wait for the latest and greatest ROMs to trickle down.
Also, sorry about the original post being kind of vague...It was posted after literal hours of searching and trying different things, and the frustration clouded my brain.
Click to expand...
Click to collapse
I am afraid if my theory is correct your flash (memory) may be going. The symptoms you have described and the fix you mention would suggest a data retention problem. If it breaks again (i hope that I am wrong and it won't) you may have to stick it in the fridge again but if that happens get rid of it fast!
Sent from my LG-P999 using XDA
rtotheichie said:
Alright, so It's fixed! Thanks for the interest.
Just for the sake of somebody who (somehow) might have something similar, here's what fixed it....and be warned, this is QUITE unorthodox:
My phone was fully charged (turned off, showing the charged battery icon). I removed the battery, the SIM, and the SD card, and stuck my phone in the fridge for about 10 minutes...That's right, the fridge. I read somewhere that this may help when writing to the disk, and I figured "why not?"
I then pushed V21e using NVflash again, and, lo and behold, it works like a champ! Now just to get the latest OTA update, sit back, and wait for the latest and greatest ROMs to trickle down.
Also, sorry about the original post being kind of vague...It was posted after literal hours of searching and trying different things, and the frustration clouded my brain.
Click to expand...
Click to collapse
Yet another proof of G2X's unbrickable fame with a happy ending.
Happy for you!
Sent from my LG-P999 using xda premium
Ok, I have a phone that I purchased used. When my S3 got the Jellybean update in December, I found out it had Clockwork Recovery Mod installed on it. It scared the hell out of me, but I went ahead with the update and it was fine. I am a complete newb to rooting and would never root my phone (I lack the skills). When the update went through in December, I was relieved. For more details on all that, see this thread: http://forum.xda-developers.com/showthread.php?t=2048805
Today's update was a different story. This update appears to have broken my phone.This time, it won't even boot up. It just say "System software not authorized by Verizon Wireless has been found on your phone and go to the nearest Verizon Wireless Store for help." Any suggestions on how to fix this? Am I completely screwed? I have almost no knowledge of rooting, ODIN, etc.
R: [Q] Help - I bricked my phone with latest VZW update
It's not bricked.. you should be able to get in download mode and flash a stock firmware with Odin..
edit: I'll link you the url's to the howto's as soon as I get to my pc
Sent from my GT-I9300 using xda premium
zeroblu3 said:
It's not bricked.. you should be able to get in download mode and flash a stock firmware with Odin..
edit: I'll link you the url's to the howto's as soon as I get to my pc
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
The weirdest thing just happened. Ok, I put in ODIN mode and pressed cancel. Then like 3 minutes later, it just started up all on its own. The update failed of course but the phone is working again. Weird. Was able to turn it off and restart.
I think I may trade this phone back into the same folks who sold it to me. I am clearly not cut out for this.
i'm glad the problem solved by itself
anyway if you still want to attempt to reset the phone to stock here is everything you should need to know :
http://forum.xda-developers.com/showthread.php?t=1762709 (take a look at section 5)
it's really not as hard as it looks...just be aware there is always a chance that something could go wrong....just take your time, read, and only go ahead if you are fully confident and willing to accept the risks...
let us know how it went and don't hesitate to ask for help if you are still in doubt after reading the forum
I hate how I am average Joe with my root knowledge and I could fix your phone without thinking twice.
It surprises me you have an xda account and can not even root and unlock boot loader.
You ask for help then say. Never mind.
Haha whatever works for you at the end of the day.
Sent from club Clean Rom
Hello, I'm a new owner of the AT&T HTC One X(L), purchased just yesterday from a previous owner. I'll try and make this thorough.
The problem is, I'm having a really hard time charging the device today after I let the battery drain all the way down from yesterday from when I purchased it. I've tried charging via USB to my laptop, directly to the wall, while its shut down, sleeping/idle, etc.. and nothing seems to get it charging quick at all. I'm using the stock HTC charger it came with, the previous owner had everything in the box and it's in great cosmetic condition.
The phone does charge some, but it was literally struggling to get between 20% and 35% for most of the day, and then later increased to 50% only to then drop back down again. And I haven't been using it at all, it's just sitting there trying to charge. How long should it reasonably take to charge this phone using the wall adapter?
Is there any chance the installed Android software (is there a custom ROM on the phone perhaps?) is causing this problem? The battery usage report says that 72% has been due to Android.. is that abnormally high by chance?
I've disabled all syncing, WiFi, screen brightness is on low, airplane mode, etc. In fact, the phone isn't even activated yet on my carrier. I've only used it thus far for WiFi at home, the browsing speed of which I'm happy with.
Some other stuff...
Recovery/bootloader reads:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHP S-ON RL
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Nov 26,2012
On the prior screen it also says "This build is for development purposes only, do not distribute outside of HTC, etc.." and then there's this little flashing "T" logo on the next white screen which shows up briefly before the phone boots up.
Any help would be much appreciated! Thanks for your time and patience.
You mentioned the "T" logo showing up during the boot process which leads me to believe it's running the T-Mobile Germany 4.2.2 stock ROM, which is technically a custom ROM in this context. The device should take about 3-4 hours to charge from zero to full. I personally think you've got a dodgy device. Have you contacted the seller regarding the issues you're having? Whoever had it previously didn't know what they were doing, it has a mismatched radio/firmware version for the ROM that's installed.
Sent from my Evita
timmaaa said:
You mentioned the "T" logo showing up during the boot process which leads me to believe it's running the T-Mobile Germany 4.2.2 stock ROM, which is technically a custom ROM in this context. The device should take about 3-4 hours to charge from zero to full. I personally think you've got a dodgy device. Have you contacted the seller regarding the issues you're having? Whoever had it previously didn't know what they were doing, it has a mismatched radio/firmware version for the ROM that's installed.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the reply. 3-4 hours from 0 to full is somewhat reassuring to hear, I assumed it wouldn't take more than an hour for some reason.
It's not the T-Mo "T" logo, it's a really different looking "T" that has a circle under it and the T flashes different colors. The T almost looks the same as the T in HTC. It only appears for a second or two and then the phone boots up. I need to take a picture of it with another device since it didn't work when I tried screen capturing that boot screen from the phone.
Is there anything else you can confirm one way or another from the info I've provided?
- So this isn't a different 3rd party custom ROM, just possibly one from T-Mo eventhough it's a branded ATT phone?
- Is this bootloader "unlocked" and is that why it says that and "tampered"? From what I've read, that's the standard msg it gives when that's the case, but isn't necessarily a red flag. Am I mistaken in my understanding though?
- Is 72% battery usage allocated to Android too high? If so, what should it be?
- Should I just try factory resetting it from the recovery screen?
droydr said:
Thanks for the reply. 3-4 hours from 0 to full is somewhat reassuring to hear, I assumed it wouldn't take more than an hour for some reason.
It's not the T-Mo "T" logo, it's a really different looking "T" that has a circle under it and the T flashes different colors. The T almost looks the same as the T in HTC. It only appears for a second or two and then the phone boots up. I need to take a picture of it with another device since it didn't work when I tried screen capturing that boot screen from the phone.
Is there anything else you can confirm one way or another from the info I've provided?
- So this isn't a different 3rd party custom ROM, just possibly one from T-Mo eventhough it's a branded ATT phone?
- Is this bootloader "unlocked" and is that why it says that and "tampered"? From what I've read, that's the standard msg it gives when that's the case, but isn't necessarily a red flag. Am I mistaken in my understanding though?
- Is 72% battery usage allocated to Android too high? If so, what should it be?
- Should I just try factory resetting it from the recovery screen?
Click to expand...
Click to collapse
Oh, I'm so dumb. I failed to look at your screenshots properly. The ROM that is installed is the Kickdroid ROM, which is a fully custom ROM that's based on the official Telstra release. The flashing T is the Telstra boot splash.
-Yes, if you see "unlocked" and "tampered" in your bootloader screen it means your bootloader is unlocked and you have root privileges. That's totally normal for a modified device.
-Under normal circumstances that amount of usage attributed to Android System world be considered high, but it all depends on how the phone is being used. If it's only been charging and nothing else has been active then I wouldn't worry very much.
-Under no circumstances should you ever perform a factory reset from the bootloader, it will corrupt your sd card. A factory reset should only be performed from within TWRP recovery, you can check if this is installed by selecting the recovery option from your bootloader. At this stage I don't think you should perform a factory reset until we've determined what you want from the device.
What would you like to get out of this device? Are you wanting to use custom ROMs or do you want to return it to stock?
Sent from my Evita
timmaaa said:
Oh, I'm so dumb. I failed to look at your screenshots properly. The ROM that is installed is the Kickdroid ROM, which is a fully custom ROM that's based on the official Telstra release. The flashing T is the Telstra boot splash.
-Yes, if you see "unlocked" and "tampered" in your bootloader screen it means your bootloader is unlocked and you have root privileges. That's totally normal for a modified device.
-Under normal circumstances that amount of usage attributed to Android System world be considered high, but it all depends on how the phone is being used. If it's only been charging and nothing else has been active then I wouldn't worry very much.
-Under no circumstances should you ever perform a factory reset from the bootloader, it will corrupt your sd card. A factory reset should only be performed from within TWRP recovery, you can check if this is installed by selecting the recovery option from your bootloader. At this stage I don't think you should perform a factory reset until we've determined what you want from the device.
What would you like to get out of this device? Are you wanting to use custom ROMs or do you want to return it to stock?
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the reply.
- Ok cool. I searched online for the Telstra logo and their T logo is for sure the one that I'm seeing. I'm assuming you don't suspect this to be the cause of the charging issue.
- So the device is unlocked and rooted, sounds fine as long as it isn't the source of the problem.
- I know this is a dumb question, but is there an ideal way for the phone to be charged? Does it need to be shut down completely for it to charge the fastest or even fully? Or can it be sleeping/idling and charge at the same rate? I've read about a variety of battery draining issues with respect to the HOX, but most are centered around WiFi and LTE uses where people were getting connected and disconnected which then caused a massive drain and bad overheating. I've yet to read something specifically about incredibly slow charging however.
My goals with this device:
- Just for it to function well and do the basics, I'm a very simple user.. calls, texts, and mild data use. I want to be able to charge it nightly within that 3-4 hour estimate and don't want any major battery issues and overheating. Today is literally my first full day with it and the first thing I needed to do was charge it, so I feel stuck at the beginning until this is resolved.
- I want to activate it on a wireless plan so it can really become my new phone, but I don't want to start this process if there's a permanent hardware or software issue with the device.
- I don't need to be on any custom ROM or on kitkat. I'm not a developer or anywhere close to being an Android wizard. I read that 4.2.2 is the last official update the HOX will receive, so I'd be absolutely fine with that. Sure, running kitkat or later Android versions might be nice down the road, but if it becomes clear that any custom ROM (now or in the future) is doing more damage than good, then I'd just want to be able to get it back to the 4.2.2 version HTC has released. I want to have that safety measure at bare minimum.
Under no circumstances should you ever perform a factory reset from the bootloader, it will corrupt your sd card. A factory reset should only be performed from within TWRP recovery, you can check if this is installed by selecting the recovery option from your bootloader. At this stage I don't think you should perform a factory reset until we've determined what you want from the device.
Ok thanks, I won't select the factory reset option from bootloader. However, I don't have an SD card in the phone and I don't think there's an SD slot on it unless I'm totally missing something?
I need to read about what TWRP recovery is and see if it's installed on my phone. Will need to get back to you on that once the phone has had more time to charge - I just want to let it sit undisturbed for 3-4 hours in shut down mode and see if it can increase past a 50% charge rate.
I only inquired about a factory reset thinking that it might be the safest way for me to start trying to troubleshoot the charging problem. It was just a random question I threw out there. I'm willing to do anything that could potentially improve my charging situation.
Whoever had it previously didn't know what they were doing, it has a mismatched radio/firmware version for the ROM that's installed.
- After reviewing my screenshots again, do you feel this is still the case? Is there mismatched software and radios afterall? And if so, would the factory reset via TWRP be one of your first suggestions to try and fix it?
- Do you think such mismatching software could potentially be the cause of its slow battery charging?
- Finally, is there any way for me to check to see if the battery itself is in good shape or faulty? Is there an app you could recommend I download where it can give me a detailed performance report which I could then share the results?
Thank you so much for your time, help, and continued patience.. it means a lot!
droydr said:
Thanks for the reply.
- Ok cool. I searched online for the Telstra logo and their T logo is for sure the one that I'm seeing. I'm assuming you don't suspect this to be the cause of the charging issue.
- So the device is unlocked and rooted, sounds fine as long as it isn't the source of the problem.
- I know this is a dumb question, but is there an ideal way for the phone to be charged? Does it need to be shut down completely for it to charge the fastest or even fully? Or can it be sleeping/idling and charge at the same rate? I've read about a variety of battery draining issues with respect to the HOX, but most are centered around WiFi and LTE uses where people were getting connected and disconnected which then caused a massive drain and bad overheating. I've yet to read something specifically about incredibly slow charging however.
Click to expand...
Click to collapse
The phone should charge fine while powered on, in fact I probably would recommend that because that way you can periodically check the progress. The slow charging could be due to a faulty battery or charger, not usually by a ROM though. The fact that it's unlocked should have absolutely nothing to do with it.
My goals with this device:
- Just for it to function well and do the basics, I'm a very simple user.. calls, texts, and mild data use. I want to be able to charge it nightly within that 3-4 hour estimate and don't want any major battery issues and overheating. Today is literally my first full day with it and the first thing I needed to do was charge it, so I feel stuck at the beginning until this is resolved.
- I want to activate it on a wireless plan so it can really become my new phone, but I don't want to start this process if there's a permanent hardware or software issue with the device.
- I don't need to be on any custom ROM or on kitkat. I'm not a developer or anywhere close to being an Android wizard. I read that 4.2.2 is the last official update the HOX will receive, so I'd be absolutely fine with that. Sure, running kitkat or later Android versions might be nice down the road, but if it becomes clear that any custom ROM (now or in the future) is doing more damage than good, then I'd just want to be able to get it back to the 4.2.2 version HTC has released. I want to have that safety measure at bare minimum.
Click to expand...
Click to collapse
You can leave Kickdroid on the phone, it will serve your needs and then some. However, you do need to do a little work to get the firmware up to date. You'll need to get s-off, which can be done pretty easily using the Rumrunner method. Then you need to flash the 2.15 firmware found in the beginning of this thread. You will need adb/fastboot installed on your PC, the easiest way is to Google search "minimal adb and fastboot", the first result will be the thread you're looking for. In order for adb/fastboot to work you need HTC drivers installed on your PC too, you can get those by installing HTC Sync Manager.
Under no circumstances should you ever perform a factory reset from the bootloader, it will corrupt your sd card. A factory reset should only be performed from within TWRP recovery, you can check if this is installed by selecting the recovery option from your bootloader. At this stage I don't think you should perform a factory reset until we've determined what you want from the device.
Ok thanks, I won't select the factory reset option from bootloader. However, I don't have an SD card in the phone and I don't think there's an SD slot on it unless I'm totally missing something?
Click to expand...
Click to collapse
There is no physical sd card slot. When people refer to the sd card we mean the virtual sd card (or internal storage).
I need to read about what TWRP recovery is and see if it's installed on my phone. Will need to get back to you on that once the phone has had more time to charge - I just want to let it sit undisturbed for 3-4 hours in shut down mode and see if it can increase past a 50% charge rate.
I only inquired about a factory reset thinking that it might be the safest way for me to start trying to troubleshoot the charging problem. It was just a random question I threw out there. I'm willing to do anything that could potentially improve my charging situation.
Click to expand...
Click to collapse
TWRP is a custom recovery that can be used for various tasks. You can make a full backup of your current system, you can restore a backup you've made. You can wipe the entire system (a task that takes place prior to flashing a ROM), or just parts. You can install a ROM, kernel, radio, or various other things.
Whoever had it previously didn't know what they were doing, it has a mismatched radio/firmware version for the ROM that's installed.
- After reviewing my screenshots again, do you feel this is still the case? Is there mismatched software and radios afterall? And if so, would the factory reset via TWRP be one of your first suggestions to try and fix it?
Click to expand...
Click to collapse
A factory reset won't help that issue, a factory reset basically removes all user data from the device. The mismatch is happening at a much lower level and can only be remedied by flashing the 2.15 firmware I mentioned above.
- Do you think such mismatching software could potentially be the cause of its slow battery charging?
Click to expand...
Click to collapse
No, I don't believe that is the case. Have you tried using a different charger and/or cable? It might be the charger that's the issue. You should only charge from an AC outlet as charging via usb from a PC or the like takes longer due to restrictions on the output.
- Finally, is there any way for me to check to see if the battery itself is in good shape or faulty? Is there an app you could recommend I download where it can give me a detailed performance report which I could then share the results?
Thank you so much for your time, help, and continued patience.. it means a lot!
Click to expand...
Click to collapse
I'm not familiar with any apps myself but I know there are many that claim to be able to report the health of the battery.
Sent from my Evita
timmaaa said:
You can leave Kickdroid on the phone, it will serve your needs and then some. However, you do need to do a little work to get the firmware up to date. You'll need to get s-off, which can be done pretty easily using the Rumrunner method. Then you need to flash the 2.15 firmware found in the beginning of this thread. You will need adb/fastboot installed on your PC, the easiest way is to Google search "minimal adb and fastboot", the first result will be the thread you're looking for. In order for adb/fastboot to work you need HTC drivers installed on your PC too, you can get those by installing HTC Sync Manager.
Click to expand...
Click to collapse
Thanks again for the reply and all the detail. This section appears to be my 'to do' list but I've been going around in circles with it for a few hours now with no results. The first problem is that Sync Manager on my computer won't recognize my device, it says no phone is plugged in yet my computer makes that alert sound when something new is connected via USB. I'm on a new Windows 8.1 laptop and can't figure it out for the life of me. Apparently this is an issue for others, as I've found out by cross reading HTC and Android forums about it. I don't know if there's some setting on the HOX itself I'm missing in order to start the sync process with my laptop or if it's a Windows issue, but I'm not getting anywhere.
I've read and followed the other pages you listed as well to do the S-off, ADB and fastboot, and ultimately the 2.15 firmware update, but even the 2nd step (S-off) fails because I can't get the darn Sync Mgr to work.
At this point, I would just like to get it back to how it was when the device was opened for the first time with Android 4.0.3. This is an AT&T branded phone for the USA, I don't want it to have anything to do with Telstra or Australian regions. I don't want any kind of custom ROM, radios, kernels, etc.
If I'm understanding you correctly, I can't factory reboot this to the way it originally came out of the box. By it being unlocked and rooted with technically a custom ROM, apparently it's past the point of no return.. I either get it to work via custom ROM or it'll be stuck as is.
I just want it to be true stock. And then once I'm comfortable with that and it's hopefully functioning better, I can then update it to the next Android releases that come directly from ATT. It's crazy how impossible that seems to achieve at this point.
droydr said:
Thanks again for the reply and all the detail. This section appears to be my 'to do' list but I've been going around in circles with it for a few hours now with no results. The first problem is that Sync Manager on my computer won't recognize my device, it says no phone is plugged in yet my computer makes that alert sound when something new is connected via USB. I'm on a new Windows 8.1 laptop and can't figure it out for the life of me. Apparently this is an issue for others, as I've found out by cross reading HTC and Android forums about it. I don't know if there's some setting on the HOX itself I'm missing in order to start the sync process with my laptop or if it's a Windows issue, but I'm not getting anywhere.
I've read and followed the other pages you listed as well to do the S-off, ADB and fastboot, and ultimately the 2.15 firmware update, but even the 2nd step (S-off) fails because I can't get the darn Sync Mgr to work.
At this point, I would just like to get it back to how it was when the device was opened for the first time with Android 4.0.3. This is an AT&T branded phone for the USA, I don't want it to have anything to do with Telstra or Australian regions. I don't want any kind of custom ROM, radios, kernels, etc.
If I'm understanding you correctly, I can't factory reboot this to the way it originally came out of the box. By it being unlocked and rooted with technically a custom ROM, apparently it's past the point of no return.. I either get it to work via custom ROM or it'll be stuck as is.
I just want it to be true stock. And then once I'm comfortable with that and it's hopefully functioning better, I can then update it to the next Android releases that come directly from ATT. It's crazy how impossible that seems to achieve at this point.
Click to expand...
Click to collapse
I should have been more clear, you don't actually want Sync Manager to work, you only wanted to install that to get the drivers. Your main obstacle is actually Windows 8.1, it isn't compatible with fastboot drivers. If you can get access to a PC with a lower version of Windows you should be fine. Then getting s-off should be pretty easy.
Kickdroid doesn't really have anything to do with the Australian region or Telstra as such. The dev merely used a Telstra ROM as a base to build Kickdroid onto.
Are you sure you actually want an at&t release? You may not be aware but at&t releases actually have features that are missing and deliberately broken. That's the only difference between running an at&t ROM and a non at&t ROM, you'll be missing features.
You can easily flash a ROM that is an earlier Android version without having to update the firmware on the device. You don't have to go back to ICS, anything that's from 4.0 up to and including 4.1 will be perfectly fine without any further modification. Have a look through our Android Development section and find one you think will suit you. There are plenty of ROMs in our development section that range from completely stock to customised. That's about as close to stock as you can get without getting s-off first.
Sent from my Evita
timmaaa said:
A factory reset should only be performed from within TWRP recovery, you can check if this is installed by selecting the recovery option from your bootloader.
Click to expand...
Click to collapse
I forgot to mention that I checked on this. When I selected Recovery from the bootloader screen, it took me to ClockworkMod Recovery v6.0.4.6 which I imagine you're familiar with in one way or another. It has 7 different options from its menu.. "reboot system now, install zip, wipe data/factory reset, wipe cache partition, backup and restore, mounts and storage, advanced". After researching it, I know it's a different app than TWRP so I didn't do anything with it per your advice.
You can use CWM if you want to, TWRP is better but it's entirely up to you. You can easily change by using this app:
https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools
Sent from my Evita
timmaaa said:
Kickdroid doesn't really have anything to do with the Australian region or Telstra as such. The dev merely used a Telstra ROM as a base to build Kickdroid onto.
Click to expand...
Click to collapse
Thanks for clearing that up. So it makes no difference if I have a Telstra or ATT logo on boot up. It just threw me for a loop is all because when you asked about it initially, I started thinking.. "yeah, why doesn't it have the ATT logo and does that have anything to do with my charging problem?"
timmaaa said:
Are you sure you actually want an at&t release? You may not be aware but at&t releases actually have features that are missing and deliberately broken. That's the only difference between running an at&t ROM and a non at&t ROM, you'll be missing features.
Click to expand...
Click to collapse
No, I'm not sure at all, that's why this is such a guessing game for me at this point. I'm just thinking that if I can just get things back to 'stock' first, then later I can move on and get involved in the custom ROM stuff if it sounds promising.
Ideally, I want to have freedom with my device and not be at the mercy of any carrier.. that's what interests me about Android to begin with, but right now I'm a little weary of what may be going on with my 'new' HOXL.
timmaaa said:
You can easily flash a ROM that is an earlier Android version without having to update the firmware on the device. You don't have to go back to ICS, anything that's from 4.0 up to and including 4.1 will be perfectly fine without any further modification. Have a look through our Android Development section and find one you think will suit you. There are plenty of ROMs in our development section that range from completely stock to customised. That's about as close to stock as you can get without getting s-off first.
Click to expand...
Click to collapse
Thanks, I will look at that section next. I like the idea that I can potentially get back to something earlier right now even with my current situation. I've been focused on trying to do all the steps you outlined yesterday to fix what I have currently. Of course I would like to be on the 'latest' ROM that makes the HOXL run most efficiently, but perhaps baby steps to start off with would be best.
My goal right now is to simply make sure all my software, firmware, radios, kernels match up. What you said in the beginning about my phone currently being mis-matched really stood out to me and I badly want to fix that. Logically, I absolutely must have a stable, synchronized OS at bare minimum.
droydr said:
Thanks for clearing that up. So it makes no difference if I have a Telstra or ATT logo on boot up. It just threw me for a loop is all because when you asked about it initially, I started thinking.. "yeah, why doesn't it have the ATT logo and does that have anything to do with my charging problem?"
No, I'm not sure at all, that's why this is such a guessing game for me at this point. I'm just thinking that if I can just get things back to 'stock' first, then later I can move on and get involved in the custom ROM stuff if it sounds promising.
Ideally, I want to have freedom with my device and not be at the mercy of any carrier.. that's what interests me about Android to begin with, but right now I'm a little weary of what may be going on with my 'new' HOXL.
Thanks, I will look at that section next. I like the idea that I can potentially get back to something earlier right now even with my current situation. I've been focused on trying to do all the steps you outlined yesterday to fix what I have currently. Of course I would like to be on the 'latest' ROM that makes the HOXL run most efficiently, but perhaps baby steps to start off with would be best.
My goal right now is to simply make sure all my software, firmware, radios, kernels match up. What you said in the beginning about my phone currently being mis-matched really stood out to me and I badly want to fix that. Logically, I absolutely must have a stable, synchronized OS at bare minimum.
Click to expand...
Click to collapse
The mismatch I mentioned earlier exists only for 4.2.2 ROMs, basically any 4.2.2 ROM requires a certain set of firmware to be installed otherwise the phone will suffer signal losses and random reboots.
As another easier option you could just install the Beastmode Reloaded kernel, which is also a workaround for those problems. That way you can keep the ROM that's already installed and be up to date.
Sent from my Evita
timmaaa said:
The mismatch I mentioned earlier exists only for 4.2.2 ROMs, basically any 4.2.2 ROM requires a certain set of firmware to be installed otherwise the phone will suffer signal losses and random reboots.
As another easier option you could just install the Beastmode Reloaded kernel, which is also a workaround for those problems. That way you can keep the ROM that's already installed and be up to date.
Sent from my Evita
Click to expand...
Click to collapse
I found this thread, I assume this is what you're talking about?
http://forum.xda-developers.com/showthread.php?t=2165880
I see on page 73 the link for the 3.5 version. Now I need to figure out how to install this. Do I first DL something onto my computer and then send it to the phone somehow with the USB cable, or am I suppose to do this directly on the HOXL? I've never flashed or installed anything like this before. I'll I've done thus far is install some apps from Google Play.
Yes that's the right one. You can download it directly to the phone, or download it to the PC and transfer it to the phone.
If downloading it to your PC and using TWRP recovery, you can connect your phone to the PC using a usb cable, select mount from the TWRP main menu, then select mount usb storage and your phone will show up as a removable drive on your PC. Copy the file across, eject the removable drive, unmount usb storage from the phone screen and then you can install.
Go back to the TWRP home screen and select install, navigate to the file and select it, swipe to install (at this point an aroma installer will commence, select the options you would like, don't let it reboot system at the end), select wipe cache/dalvik, swipe to wipe, hit back, hit reboot system. Now the phone will reboot into the OS again and that's it.
Sent from my Evita
timmaaa said:
Yes that's the right one. You can download it directly to the phone, or download it to the PC and transfer it to the phone.
If downloading it to your PC and using TWRP recovery, you can connect your phone to the PC using a usb cable, select mount from the TWRP main menu, then select mount usb storage and your phone will show up as a removable drive on your PC. Copy the file across, eject the removable drive, unmount usb storage from the phone screen and then you can install.
Go back to the TWRP home screen and select install, navigate to the file and select it, swipe to install (at this point an aroma installer will commence, select the options you would like, don't let it reboot system at the end), select wipe cache/dalvik, swipe to wipe, hit back, hit reboot system. Now the phone will reboot into the OS again and that's it.
Sent from my Evita
Click to expand...
Click to collapse
I downloaded the 3.5 zip file from page 73 directly to my phone.
And then I followed your install instructions exactly and now my phone keeps turning on and off without being able to boot all the way. It starts on the white "T" logo Telstra screen and then goes to the white HTC screen and then turns off again. It's been doing this nonstop for the last 20 minutes or so now. I'm assuming I have a big problem? The device is unusable at this point, it just keeps turning on and off and is getting very warm all over.
droydr said:
I downloaded the 3.5 zip file from page 73 directly to my phone.
And then I followed your install instructions exactly and now my phone keeps turning on and off without being able to boot all the way. It starts on the white "T" logo Telstra screen and then goes to the white HTC screen and then turns off again. It's been doing this nonstop for the last 10 minutes or so. I'm assuming I have a problem? The device is unusable at this point, it just keeps turning on and off.
Click to expand...
Click to collapse
There are a small number of devices for which Beastmode isn't compatible, it looks like you've lucked out and have one of those devices. Out of interest, which settings did you choose during the installer?
You can get out of the boot loop by just continuing to hold the volume down button, the next time the loop starts it should enter the bootloader.
At this point you have no choice but to flash another ROM, so I'd head to the development section I linked you to earlier and find a 4.1 ROM that you think you might like and flash that.
PS. I noticed you posted the same thing in the Beastmode thread too, duplicate posts are against the rules here on XDA.
Sent from my Evita
---------- Post added at 03:29 AM ---------- Previous post was at 03:24 AM ----------
Because you're s-on you are going to need to get access to a PC that runs a lower version of Windows, you need to have a working adb/fastboot environment. Flashing a ROM is going to require you to also flash the boot.img from the ROM zip using fastboot, this is a limitation on s-on devices with a hboot later than 1.14.
Sent from my Evita
timmaaa said:
There are a small number of devices for which Beastmode isn't compatible, it looks like you've lucked out and have one of those devices. Out of interest, which settings did you choose during the installer?
You can get out of the boot loop by just continuing to hold the volume down button, the next time the loop starts it should enter the bootloader.
At this point you have no choice but to flash another ROM, so I'd head to the development section I linked you to earlier and find a 4.1 ROM that you think you might like and flash that.
PS. I noticed you posted the same thing in the Beastmode thread too, duplicate posts are against the rules here on XDA.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the reply. I wasn't sure you were going to see this anytime soon, so I wanted to post it in that kernel thread as well just in case anyone was reading over there. I apologize for that.
I chose the default settings during installation.
Anyway, I've been holding down the volume button now for the last few minutes and it's not entering bootloader. The loop continues.
There's no other way to get to the bootloader apart from holding volume down or trying the volume down + power combination. I also added a little to my previous post which you'll need to read.
Sent from my Evita
timmaaa said:
There's no other way to get to the bootloader apart from holding volume down or trying the volume down + power combination. I also added a little to my previous post which you'll need to read.
Sent from my Evita
Click to expand...
Click to collapse
I saw the added parts, thanks. Problem is, this forum isn't allowing me to post or edit my previous posts until 5 mins have past, so it's a struggle trying to communicate.
I've also edited my post in the beastmode thread.
Anyway, I finally got into bootloader with the volume + power combo. Feels good to at least achieve that.
FYI, my bootloader screen looks the same as when I first got the phone a few days ago. Just wanted to include this info here.
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHP S-ON RL
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Nov 26,2012
Just curious, now that I'm in bootloader, would it do me any good if I selected Recovery so it can then take me to Clockwork? And from there I could try rebooting? Or one of the other menu options?
At this point you have no choice but to flash another ROM, so I'd head to the development section I linked you to earlier and find a 4.1 ROM that you think you might like and flash that.
Because you're s-on you are going to need to get access to a PC that runs a lower version of Windows, you need to have a working adb/fastboot environment. Flashing a ROM is going to require you to also flash the boot.img from the ROM zip using fastboot, this is a limitation on s-on devices with a hboot later than 1.14.
Click to expand...
Click to collapse
I've found this ROM which looks fine. I'm not picky. I'd be happy with anything as long as it can get my device to function again.
http://forum.xda-developers.com/showthread.php?t=2244445
If there's a better 4.1 ROM you'd like to suggest, please feel free to do so.