[ROM] OTA Update 1.32.651.6 | Update.zip Format - EVO 4G Android Development

This is a download for the stock evo OTA update (1.32.651.6), rooted and in update.zip format. Please note that you will NOT be able to just flash this on your phone and have root. This is here for you to be able to have a totally stock rom (with root, superuser, and debugging turned on) once you root your Evo. You should be able to flash this without wiping, however if you have any problems then wipe.
Base: Supersonic_1.32.651.6
Download: http://geekfor.me/evo/21/ota1326516
Radio: http://geekfor.me/evo/radio/radio139000531/

Thanks, flipz!

Just saying that this also breaks 4G, I was running the debugging recovery PC36IMG.zip from toastcfh before this and 4G was working fine.

angeltk said:
Just saying that this also breaks 4G, I was running the debugging recovery PC36IMG.zip from toastcfh before this and 4G was working fine.
Click to expand...
Click to collapse
Did you upgrade your radio? This is a 100% copy of the rom with the minor tweaks required to make it root. I have had several testers confirm that 4g works perfectly fine with the radio update. I'll be making my way towards the city today and confirming it for myself. I can't test it from home.

4g works, confirmed.

efuse said:
4g works, confirmed.
Click to expand...
Click to collapse
Thanks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

has anyone successfully flashed this over their .1 "stock" rom? any FC/other issues?

flipzmode said:
Did you upgrade your radio? This is a 100% copy of the rom with the minor tweaks required to make it root. I have had several testers confirm that 4g works perfectly fine with the radio update. I'll be making my way towards the city today and confirming it for myself. I can't test it from home.
Click to expand...
Click to collapse
Yes, I flashed the radio that toast posted earlier. 4G connects and shows 2 bars, just no data gets passed through (ie, web pages don't load, speedtests don't run) tested after a reboot too.

flipzmode said:
You should be able to flash this without wiping
Click to expand...
Click to collapse
Please explain. I have the Toast root, Flipz original .1 rooted RUU & Toast radio update. I can flash this with the same procedure as the .1 rooted RUU? Are you saying that I do not need to clear data and davlic cache? Also, I assume I will have to reinstall all apps?
Thanks!
PS- If my SD card is working and I have the new radio, is there a reason for me to flash this rom?

Thanks flipz! You're the man!

Thank you Flipz.
Market is working shows all my apps and installs are running faster then ever.
Shows Handcent.

Flashed over stock rooted and got a boot loop. Oh well.

just want to clarify do we need to flash both this:
Base: Supersonic_1.32.651.6
AND the radio? or is the radio already included in Base: Supersonic_1.32.651.6????

Freelancerx said:
just want to clarify do we need to flash both this:
Base: Supersonic_1.32.651.6
AND the radio? or is the radio already included in Base: Supersonic_1.32.651.6????
Click to expand...
Click to collapse
Yes, you need to flash BOTH the ROM, and the newest radio seperately.

thx flipz for the rom

does 4g work without the radio update?

If I already flashed the radio subsequent to rooting using toast's method, I assume this ROM flash will not overwrite the radio, correct?

KyleMac said:
If I already flashed the radio subsequent to rooting using toast's method, I assume this ROM flash will not overwrite the radio, correct?
Click to expand...
Click to collapse
Nope it wont

Thanks flipz! Flashed this over your original RUU 1.32.651.1 w/o wiping and didn't have any issues. I was able to connect to Killeen/Fort Hood 4G network indoors with the following results 1655 kbps (down) 911 kbps (up). This portion of the post is being done using WiFi Tether (not the Sprint Hotspot) connected to 4G
Again great work!!!!!

KyleMac said:
If I already flashed the radio subsequent to rooting using toast's method, I assume this ROM flash will not overwrite the radio, correct?
Click to expand...
Click to collapse
I'd already flashed the radio and can confirm that this won't overwrite the radio.

Related

[Q] Slow 3G data speeds on GT-i9020a on AT&T network

I just recently bought a GT-i9020a with AT&T 3G compatible bands as a replacement for my Nexus One. The first thing I noticed when doing some 3G data transfer speed tests like on the SpeedTest.net mobile app is how much slower the Nexus S is compared to my Nexus One. I get anywhere between 1000-1900 kbps download and 500-1000kbps upload on the Nexus One. On this new Nexus S I'm lucky to get a third of those speeds both up and down. I've done the speed tests in the same location with both phones with the same SIM card and get consistently the same results.
I've gone into the *#*#4636 "Testing" setting and my preferred network type defaults to: GSM/CDMA auto (PRL)
BTW, my status icon indicates a 3G signal with 4 full bars service. I'm running stock 2.3.4 Android - unrooted/unmodded. Build # GRJ22. Baseband: I9020AUCKD1.
Any help/suggestions?
Your upload is faster than your download?
Anyways, I get around 4Mbps down and 0.35Mbps up on 3G.
i9020a on Fido/Rogers network.
Sent from my Nexus S (2.3.4) using XDA App
Woops, my bad, got the upload/download mixed up. Fixed the original post.
Dig around. The stock radio is capped on the 9020a. You need to root and flash one of the uncapped radios. Not fun but well worth it.
rveez said:
I just recently bought a GT-i9020a with AT&T 3G compatible bands as a replacement for my Nexus One. The first thing I noticed when doing some 3G data transfer speed tests like on the SpeedTest.net mobile app is how much slower the Nexus S is compared to my Nexus One. I get anywhere between 1000-1900 kbps download and 500-1000kbps upload on the Nexus One. On this new Nexus S I'm lucky to get a third of those speeds both up and down. I've done the speed tests in the same location with both phones with the same SIM card and get consistently the same results.
I've gone into the *#*#4636 "Testing" setting and my preferred network type defaults to: GSM/CDMA auto (PRL)
BTW, my status icon indicates a 3G signal with 4 full bars service. I'm running stock 2.3.4 Android - unrooted/unmodded. Build # GRJ22. Baseband: I9020AUCKD1.
Any help/suggestions?
Click to expand...
Click to collapse
mikeruoc said:
Dig around. The stock radio is capped on the 9020a. You need to root and flash one of the uncapped radios. Not fun but well worth it.
Click to expand...
Click to collapse
+1 i dont have an i9020a, but i have read a thread where every user that "uncapped" their radio fixed it.
Is there a benefit to one radio over another.
Also the steps I need to take are:
1. Unlock bootloader
2. Gain root access
3. Flash the baseband/radio
Is this correct?
Thanks.
Agree. Phone I got is running a custom ROM with different radio. Signal isn't that great in my house, just pulled down a 2.3 mbps download. Upload not so good, but I'm on 1 bar.
Sent from my Nexus S using XDA App
I use an i9020A on AT&T as well. I had to flash the uncapped KB3 radio to mine to get decent upload speeds. On average, my download speed tends to be somewhere between 1.5Mbps and 2.5Mbps while uploads are usually between 1.0-1.5Mbps.
The default radio (KD1) that came with the OTA 2.3.4 upgrade was capped.
Can't remember which posting I found it in here at XDA so I just uploaded the file here: http://www.mediafire.com/?tz06t4d4yaucusg
I had I9020AUCKD1 stock. I dont remember the speeds but they were pretty junky.
The first thing i did after unlocking and rooting is flash a radio. I flashed this one:
http://forum.xda-developers.com/showpost.php?p=12727000&postcount=82
And now I get these speeds:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
These are about the same speeds I had with my N1 so I'm satisfied. btw I'm on ATT and live in the bay area, CA. YMMV.
ranphi said:
I use an i9020A on AT&T as well. I had to flash the uncapped KB3 radio to mine to get decent upload speeds. On average, my download speed tends to be somewhere between 1.5Mbps and 2.5Mbps while uploads are usually between 1.0-1.5Mbps.
The default radio (KD1) that came with the OTA 2.3.4 upgrade was capped.
Click to expand...
Click to collapse
When I choose that KB3.zip to apply the installation gets aborted. The list of errors includes:
"E: Can't find misc"
"Writing Radio assert failed: write_raw_image("/tmp/radio.img", "radio")"
"E: Error in /sdcard/XXKB3-GRI54-radio=nexxus-unsigned.zip"
(Status 7)
Installation aborted.
Anyone know what I'm doing wrong?
rveez said:
When I choose that KB3.zip to apply the installation gets aborted. The list of errors includes:
"E: Can't find misc"
"Writing Radio assert failed: write_raw_image("/tmp/radio.img", "radio")"
"E: Error in /sdcard/XXKB3-GRI54-radio=nexxus-unsigned.zip"
(Status 7)
Installation aborted.
Anyone know what I'm doing wrong?
Click to expand...
Click to collapse
What commands are you using?
denimjunkie82 said:
What commands are you using?
Click to expand...
Click to collapse
- Install zip from sdcard
- Choose zip from sdcard
- selected the .zip to apply
rveez said:
- Install zip from sdcard
- Choose zip from sdcard
- selected the .zip to apply
Click to expand...
Click to collapse
I've never flashed a radio from recovery before. It's possible that the zip isn't signed or not supported for recovery flashing.
I prefer fastboot for radios since it requires less steps for the phone to do, less chance of error IMO.
unzip the zip and pull out the radio.img and place it in your fastboot directory
check that the MD5 is ebc55ccf390a9c310f4f3e8b6f178e59
fastboot devices to make sure your fastboot detects your phone
fastboot flash radio radio.img
rveez said:
When I choose that KB3.zip to apply the installation gets aborted. The list of errors includes:
"E: Can't find misc"
"Writing Radio assert failed: write_raw_image("/tmp/radio.img", "radio")"
"E: Error in /sdcard/XXKB3-GRI54-radio=nexxus-unsigned.zip"
(Status 7)
Installation aborted.
Anyone know what I'm doing wrong?
Click to expand...
Click to collapse
What version of CWM are you using? You'll need to be at 3.0.2.4 at least to successfully flash that radio.
Also, some peeps that downloaded radio files via their phone's browser had issues. Downloading via a computer and then transferring the file to their phone enabled them to successfully flash.
HTH. Good luck!
ranphi said:
The default radio (KD1) that came with the OTA 2.3.4 upgrade was capped.
Click to expand...
Click to collapse
Does this apply to all other variants as well? Since my 9020T is also running 2.3.4 and KD1!
Okay I successfully got the radio flashed to the KB3. It really does improve my 3G speeds as described by others here!
Now I have no use for my device to be rooted. I know how to re-lock the bootloader but I'm not quite sure what I need to do to restore a recovery image. Unfortunately I don't have a backup to restore from.
Where can I get a recovery that has my i9020a/GRJJ22/2.3.4 with the KB3 radio?
Thanks.
So is the consensus now that for AT&T and the 9020a, the best radio is KB3?
I have not seen anything better. Anyone else?
iboj007 said:
So is the consensus now that for AT&T and the 9020a, the best radio is KB3?
Click to expand...
Click to collapse
zero383 said:
Your upload is faster than your download?
Anyways, I get around 4Mbps down and 0.35Mbps up on 3G.
i9020a on Fido/Rogers network.
Sent from my Nexus S (2.3.4) using XDA App
Click to expand...
Click to collapse
If you want faster uncapped speeds on the fido/rogers network just flash KB3 radio...heres what I get now...use to get your speeds on KB2.
I have an i9020a on 2.3.6 baseband kf1, is there one that I can flash so my speeds are not capped?

[rom]the collective silver ics rom.....fixed power menu..transparent dialer 4/13/12

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SILVER ROM ICS
15 toggle mod and kernel thanks to RomRacer​
download link
ROM
Http://www.theandroidcollective.org/i727/SilverRom/silver_cream_sammywich.zip
SuperSU
Http://www.theandroidcollective.org/i727/SilverRom/CWN-SuperSU-v0.87.zip
if you do not want transparent pop up menus flash this
http://www.theandroidcollective.org/i727/SilverRom/notrans.zip​
Here are instructions.
Download bothzips
Put on sd card
Wipe/data/cache/dalvik cache
Flash rom
Flash supersu.zip
Boot system.
After boot is complete.
Shutdown. Wipe data/cache/dalvik and fix permissions.
Sign in google.
Sign in g+
Open the supersu ap. It will update binary.
You will not loose root.
Power options work.
For later.................
Screenshots.........nnnnnn
For later..............
Is TiBu working yet? And can I install this over another ICS Rom?
Love your rom. I tried the new ics but had tons of fc. Not only did tibu but also with waze and a few others. I went back to collective 3 for now. Patiently waiting for your next masterpiece
Skyrocket,
I was trying to follow your other thread ( no data loss gb rom ) and got lost...
Needless to say, I'm glad you've created a new one.
My question is: Is THIS rom your current 4.0.3 project? I'm still running 2.3.6 (NexusMod4) and would love to try out a stable (or at least somewhat stable) ICS rom.
Thanks in advance, and as always - thanks for the hours of time you and other devs put into these masterpieces!
yes this is my current ics android 4.0.3 rom
link has been removed from op
uploading updated version with changes ......tibu has been fixed so be patient i will update the op with new link asap
you can flash this from gb without wiping anything
yeah i accidentally added back the preloadinstaller
thats what causes the force closes and tibu not to work
silver03wrx said:
yes this is my current ics android 4.0.3 rom
you can flash this from gb without wiping anything
Click to expand...
Click to collapse
Well, I just attempted to flash it (without wiping first) and got stuck in a boot loop.
Any suggestions?
EDIT:
As I let it attempt to boot several times, it seems to get a little further into the boot animation. I've now seen just a little bit of blue swirls behind the earth.
TwiztedDotNet said:
Well, I just attempted to flash it (without wiping first) and got stuck in a boot loop.
Any suggestions?
EDIT:
As I let it attempt to boot several times, it seems to get a little further into the boot animation. I've now seen just a little bit of blue swirls behind the earth.
Click to expand...
Click to collapse
Yea same thing happen to me coming from NexusMod4 Im still trying to get it to not bootloop errgh
Sent from my SAMSUNG-SGH-I727 using xda premium
Yes restore yourbackup and wait for new upload
probs with the theme
I was running fine on the ICS rom (ics3.zip) and installed the theme. Now I'm getting lots of apps unable to run (handcent, lookout, juice defender, ROM manager). Ran fix perms in recovery (couldn't get into ROM mgr to try there) and didn't help... Just wanted to let you know.
I flashed mhx Superlite 4.5 over the previous version (ics3 I think) of Silver ICS and it fixed the freeze at shutdown issue for me. That rom has a wipe script too but that one wipes and formats data (also aligns disc partitions--not sure if yours does that).
I'm wondering if the freeze at shutdown issue has something to do with data not getting fully wiped.
I'm going to try flashing your latest rom over Superlite and see if I get the shutdown freeze again. I'll report back with results...
(I should mention that one person posted that they flashed mhx's rom and got the freeze at shutdown for the first time, so who the hell knows...)
I don't like being impatient, but I'm seriously sitting here biting my nails waiting for the download link to come back (with the latest version).
The suspense is killing me!!!
F5...F5...F5... ;-)
Sent from my SAMSUNG-SGH-I727 using xda premium
silver03wrx said:
download link
http://www.theandroidcollective.org/i727/silverrom/silverics.zip​
Click to expand...
Click to collapse
Uhm.. OK I give... Where's the link exactly?
robinsonj said:
Uhm.. OK I give... Where's the link exactly?
Click to expand...
Click to collapse
It's not currently available.
We're all "patiently" waiting for his latest release to be linked...
...and I almost have no finger nails left!

LGO3D wont accept sim card after flashing Acura Team 3D Max 2 v3.1

Hello everyone,
I got a huge problem, i installed the acura rom from here:
http://forum.xda-developers.com/showthread.php?t=1778299
Followed all the steps, rom installed fine, everythign seems to work, but it seems like the phone dont use my sim card, there is no need to enter a pin (on every other phone i need to enter a pin to use this sim card), i cant phone any1 and of course there is no mobile data.
Tryed another sim card, same problem. I guess the baseband version isnt compatible to my country/provider?
Iam using o2/netzclub and i live in germany.
Any ideas?
Edit, i think its not the baseband fault, my other roms work fine with this baseband version, so its up to the rom, it looks so great, i want to use it but i cant. It was the first rom which shows me realistic battery dran infos.
You need install a baseband, flash 21e, this works
http://forum.xda-developers.com/showthread.php?t=1667414
insestito said:
You need install a baseband, flash 21e, this works
http://forum.xda-developers.com/showthread.php?t=1667414
Click to expand...
Click to collapse
hey, thanks for answering, this baseband flashing look really risky, would this be the only way to get this one rom working?
Iam wondering why all the other roms work fine, but only this one needs this kind of baseband flashing?
Iam bit scared to brick my device,
right now, it looks like that:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I used other 21E based roms who worked fine, why this one not?
Did i get it right, baseband is independent from rom/kernel? Is it the same like whats called "modem" on a htc hd2 device?
Edit:
http://forum.xda-developers.com/showthread.php?t=1570937
I used this rom without problems, and its 21E based, so i dont get it...
Edit2: ThiaiZ 21E based rom also dont get any connection, now iam confused, is it safe to flash the basband like shown in the tutorial even without moding the usb cable?
mastergamer99 said:
hey, thanks for answering, this baseband flashing look really risky, would this be the only way to get this one rom working?
Iam wondering why all the other roms work fine, but only this one needs this kind of baseband flashing?
Iam bit scared to brick my device,
right now, it looks like that:
I used other 21E based roms who worked fine, why this one not?
Did i get it right, baseband is independent from rom/kernel? Is it the same like whats called "modem" on a htc hd2 device?
Edit:
http://forum.xda-developers.com/showthread.php?t=1570937
I used this rom without problems, and its 21E based, so i dont get it...
Edit2: ThiaiZ 21E based rom also dont get any connection, now iam confused, is it safe to flash the basband like shown in the tutorial even without moding the usb cable?
Click to expand...
Click to collapse
do not worry I do not think anything happens, I already miss and I have a lot of people do.
after flashing this baseband i wont be able to use my old rom what i used till now right?
download GetRIL
Try different RILs. For Acura I use V20p
If one does not work in 20 seconds - reload the backup and then try another one like V21E.
You will see also which Baseband you have at the moment.
I think you have incompatible RIL/Baseband combination
so, i flashed another baseband, at first i really thought my device is broken, cuz lg flash tool got an error. but i unpluged the device and was happy that it bootet up
But it was unusuable, there was not a single kb left on the phone flash, so it wasnt able to save anything, then i rootet it and it worked normal (lol :laugh
Then CMW>backup>acura 3d rom > connection work!
now iam testing the new rom
Thank you so much.
But, acording to the phone info the baseband is still the same?! still dont get it xD, its confusing, bbut it works, hope that the battery life is better now.
Man could you please describe us step by step what did you did?
The thing is I live in Brazil and I already have an GB baseband, but it is based on P920h v20a... I can flash v20a roms to v21d
But if I flash v21e roms I get no signal
I've already tried to flash 21e baseband and kdz and still got the same issues (even If after that I flash the Custom ROM)
No luck also with GetRIL
So I was almost giving it up because I thought that due my contry region code I wasn't able to flash v21e firmwares...
It seems that you had similiar issues, but I couldn't understand very well what procedures did you take to suceed.
So if you could describe it better I would be very thankfull.
I used the methode described here:
http://forum.xda-developers.com/showthread.php?t=1667414
didnt used a mod usb cable, just the normal one,
but it took me severel trys to success, like described there, u need to instal the 4 or 5 parts before, also dont forget to exchange the lgflash file.
Then connect the phone, change the com port to 41, start flash software, load the both downloaded files (.ddl and the ~500mb bin file). then unplug the phone and connect again (took me about 2 or 3 trys until the software startet flashing), else then shown in the description the lgflash software didnt show "pass", it showed "FAIL"
But the phone was able to boot, the flashed android was crap, before rooting nothing worked, but doesnt matter, flashed cmw and acura 3d max rom and now it works good, bettery life is better now, but still worser then my old hd2
The hd2 wasnt bad at all, from todays view its a bit slow, but it got fully workign ics cm9 support, this newer lg o3d is "highend" and we are stuck to gb, sad, but the phone was cheap.
back to topic, good luck at flashing
mastergamer99 said:
hey, thanks for answering, this baseband flashing look really risky, would this be the only way to get this one rom working?
Iam wondering why all the other roms work fine, but only this one needs this kind of baseband flashing?
Iam bit scared to brick my device,
right now, it looks like that:
I used other 21E based roms who worked fine, why this one not?
Did i get it right, baseband is independent from rom/kernel? Is it the same like whats called "modem" on a htc hd2 device?
Edit:
http://forum.xda-developers.com/showthread.php?t=1570937
I used this rom without problems, and its 21E based, so i dont get it...
Edit2: ThiaiZ 21E based rom also dont get any connection, now iam confused, is it safe to flash the basband like shown in the tutorial even without moding the usb cable?
Click to expand...
Click to collapse
I had the exact same thing happen to me, and all I did was install http://forum.xda-developers.com/attachment.php?attachmentid=1207477&d=1342660414 through ClockworkMod and now everything works FANTASTICLY!
I also tried installing the 21e baseband first, and it didn't work to fix the problem, so I'd try this.
Hope this helps!

[Q] ViperXL Phone call reboot

Having an issue with the ViperXL 3.2.6 rom from Venom.
Quite frequently I receive a call, and before the call can connect and show ringing the phone reboots. The phone will light up and immediately go to the ViperXL logo.
I have flashed 3.2.6 twice, once via updates OTA and the second time a clean flash and wiping the phone. So this determines its a ROM specific problem and not my device as it worked fine with 3.2.5.
Anyone have any suggestions?
Mods please move to QA if needed. I tried to post there, but for some reason that didn't work. Thanks!
LOGCAT !!!!!! LOG CAT
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
jd101506 said:
Having an issue with the ViperXL 3.2.6 rom from Venom.
Quite frequently I receive a call, and before the call can connect and show ringing the phone reboots. The phone will light up and immediately go to the ViperXL logo.
I have flashed 3.2.6 twice, once via updates OTA and the second time a clean flash and wiping the phone. So this determines its a ROM specific problem and not my device as it worked fine with 3.2.5.
Anyone have any suggestions?
Mods please move to QA if needed. I tried to post there, but for some reason that didn't work. Thanks!
Click to expand...
Click to collapse
Do you use the AOSP lockscreen with the incoming call workaround? I had this problem. Just turn off the incoming call workaround and use Tasker to unlock the phone when a call comes in.
RollTribe said:
Do you use the AOSP lockscreen with the incoming call workaround? I had this problem. Just turn off the incoming call workaround and use Tasker to unlock the phone when a call comes in.
Click to expand...
Click to collapse
I'll give that a shot. Should this not work, is there a good guide on here to relock, unroot, and flash the original rom? Should I need to go back for a warranty reason I'd like to know I have the ability to do it. SuperCID, unlocked, and on 3.2.6 currently. I do not have a backup of my original ROM as when I was flashing that particular backup it erased the SD card. Which was awesome. haha.
I did use the AOSP unlock method with the autounlock feature enabled since last week. Its odd, sometimes it worked, sometimes it didn't. Prior to updating to 3.2.6 I never had any problems.
Thanks!
CheesyNutz said:
LOGCAT !!!!!! LOG CAT
Click to expand...
Click to collapse
I can paste the whole Log if you want but... I only have three "red" issues it seems.
"E/Trace (29702): error opening trace file: No such file or directory (2)" x 5
"E/hwcomposer( 237): void qhwc::QueuedBufferStore::unlockBuffer(private_handle_t*) Invalid Handle" x 1
"E/SQLiteLog(29830): (5) statement aborts at 1: [PRAGMA journal_mode=TRUNCATE;]" x1
Have you tried a dirty flash of the Rom? Agree that it is most likely aosp lockscreen issue. Could also be too little voltage. Do a nandroid backup, and then try a dirty flash(only wipe dalvik and cache).
Sent from the HOXL dimension of S-OFF
c5satellite2 said:
Have you tried a dirty flash of the Rom? Agree that it is most likely aosp lockscreen issue. Could also be too little voltage. Do a nandroid backup, and then try a dirty flash(only wipe dalvik and cache).
Sent from the HOXL dimension of S-OFF
Click to expand...
Click to collapse
I did a dirty flash of the ROM prior to this current one. I have disabled the AOSP lockscreen and gone back to the stock one and it seems to be fine. I have received three calls on it so far with no random reboots, so far so good. Will report back if I have it again and i'll try a dirty flash if so.
Does anyone have a good step by step guide to bring the phone back to ATT spec? Supercid, relock, the stock rom etc? Assuming this guide will do me? http://www.youtube.com/watch?v=owjiYLQNbnI
At some point in the future I'll need to reformat in order to upgrade and I'd like to be ready for it.
Thanks everyone.
jd101506 said:
I did a dirty flash of the ROM prior to this current one. I have disabled the AOSP lockscreen and gone back to the stock one and it seems to be fine. I have received three calls on it so far with no random reboots, so far so good. Will report back if I have it again and i'll try a dirty flash if so.
Does anyone have a good step by step guide to bring the phone back to ATT spec? Supercid, relock, the stock rom etc? Assuming this guide will do me? http://www.youtube.com/watch?v=owjiYLQNbnI
At some point in the future I'll need to reformat in order to upgrade and I'd like to be ready for it.
Thanks everyone.
Click to expand...
Click to collapse
It depends what state your phone is in now. Is it SuperCID? If so, and you're S-ON the RUU will brick your phone. The safest way to RUU is with S-OFF. Are you planning on selling the phone? If so, I would just leave it S-OFF and bootloader unlocked and just run the RUU. This way, the phone is stock but if the next person wants to root it they can.
exad said:
It depends what state your phone is in now. Is it SuperCID? If so, and you're S-ON the RUU will brick your phone. The safest way to RUU is with S-OFF. Are you planning on selling the phone? If so, I would just leave it S-OFF and bootloader unlocked and just run the RUU. This way, the phone is stock but if the next person wants to root it they can.
Click to expand...
Click to collapse
Thanks for the information. Ironically a lot has happened since I last posted.
Unrooted and relocked the phone yesterday. After running the RUU, it booted up and I all was well. Phone was perfect coming out of the gate, and I installed all my apps and customization. Unfortunately, when I updated to the stock JB image using the OTA update from ATT it erased all my data. Puzzling. I tried updating again and it bricked the device. No power, no screen image, no charge LED, nothing.
Took it to ATT and my replacement is out for delivery today. I guess that's one way to do it...
Thanks to the community for all the help. Might end up rooting this new phone once I get sick of ATTs junkware.

[Q] Err.. Need advice.

So i'm having some trouble here.
Anything such as CM10.1 or any CM or related custom rom I install gets unstable after x amount of days.
And any CM based rom has the poorest battery life I could ever imagine. I've wiped everything multiple times. I've attempted to full restore and start over on a fully "reset" phone. It's killing me - as I'm an active college student who doesn't have time to sit around a wall outlet anymore [like I use to] to always have a good phone charge.
Anything else either turns out to be;
Unstable -or
Laggy -or
Fail to flash correctly -or
Camera and/or Gallery either isn't there, won't load, crashes, or fails to even hint about being usable.
I honestly am about to just dump this phone, as the screen is already cracked. And development slowed to a halt it seems.
I said screw it the other night, and went to install CleanRom 6.5, only to find that it starts installing [after clicking through my options in Aroma] andd loads for 1-4 seconds then says "DONE" with 0% completed and says everything installed perfectly. However when I go to reboot TWRP notified me I had no OS installed which made sense considering I've never had a rom install in <5 seconds.
Moving on though, anyone have any suggestions? And I do mean any? I've used the OneX tool for everything, AND done the usual [root/unlock/recovery/s-off -> custom rom] with that and manually to have no success between the two. Do I just have a busted device? Something faulty perhaps in the circuit board? I honestly haven't a clue. But all I know is, CM is and probably will forever be my favorite. However my phone died yesterday after 3 hours of sitting in my pocket and today I barely touched it compared to my normal use on sense based or other roms which I'll get 8+ hours out of. I just don't know what to do anymore. I use to consider myself a flash-a-holic where I'd be reinstalling ROM after ROM just to see what all the amazing and different features they have - then running new kernels. But now it isn't even usable.
My signal has also been in the toilet. A friend of mine has the same exact phone and we can put them right next to each other, he'll have full bars on AT&T and i'll have one or two [if i'm lucky]. I've flashed every radio up and down - back and forth. Flashed the radio and all else EXACTLY like his phone and I quickly found myself stuck in a hole with a better paperweight than phone. My last effort was to do wipe after wipe and battery calibration apps hoping that may be my problem and I'm stupid for over thinking it. But... if anything it made it worse.
Should I dump it? or is there hope. . .
I don't see how it could be my battery considering.. well... roms OTHER than those based on CM have been perfect on battery life just like they were when I first got the phone. But they don't have operable camera and/or gallery. I also uploaded a picture of my past 8~ hours with this phone. Note the past 2/3 hours. I know I've noticed some "slight" change..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What Hboot?
What recovery/version?
S-ON or S-OFF?
You said you'd tried wiping, have you tried RUU?
Edit: that said, don't just go flashing running RUUs, unless you're s-off.
As for battery drain, disable Google location services while you are on wi-fi. It really kills aosp roms For other issues see Exad's reply above. Easier to help with more information.
Sent from my HTC One X using xda premium
exad said:
What Hboot?
What recovery/version?
S-ON or S-OFF?
Click to expand...
Click to collapse
HBoot- 2.14.0000
TWRP- [tried the past couple versions, hoping maybe its just a bug with one but stuck with] 2.5.0.0
S-OFF
Venomtester said:
As for battery drain, disable Google location services while you are on wi-fi. It really kills aosp roms For other issues see Exad's reply above. Easier to help with more information.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Alright, I'll try that - even though I rarely use any GPS or related service.
RollTribe said:
You said you'd tried wiping, have you tried RUU?
Edit: that said, don't just go flashing running RUUs, unless you're s-off.
Click to expand...
Click to collapse
Yup.
TKTAB911 said:
HBoot- 2.14.0000
TWRP- [tried the past couple versions, hoping maybe its just a bug with one but stuck with] 2.5.0.0
S-OFF
Alright, I'll try that - even though I rarely use any GPS or related service.
Yup.
Click to expand...
Click to collapse
download twrp 2.6: http://goo.im/devs/OpenRecovery/evita/openrecovery-twrp-2.6.0.0-evita.img
Check md5
fastboot flash recovery OpenRecovery/evita/openrecovery-twrp-2.6.0.0-evita.img
fastboot reboot bootloader
fastboot erase cache
select bootloader on phone screen
select recovery on phone screen
Wipe
Advanced
Select everything, except sd card unless you want to wipe your sd card
check md5 of your rom on your pc.
copy and flash your rom.

Categories

Resources