• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root *****10/4/13*****New OTA DO NOT DOWNLOAD IF YOU'RE ROOTED

ok to make sure peeps who read the op will see and know, this is what i did to the op:
1/31/2013:
DO NOT ACCEPT THIS OTA!!!!!
Proximity sensor improvements while on a call or listening to voicemail
- Ability to output audio/video to HDTV (and other external displays via MHL cable
- WiFi Connection improvements
- Bluetooth compatibility improvements
- Android process/application shutdown resolved
Click to expand...
looks like no new hboot, but the radios is updated.

here is a word of warning from captain throwback:
CapThrowback said:
Anyone that is S-ON and rooted with a custom recovery should AVOID RELOCKING taking this OTA AT ALL COSTS!!!!

If you do, you won't be able to access your recovery.

See here, for example: http://forum.xda-developers.com/showthread.php?t=2126626

You shouldn't do it anyway, as is stated multiple times in this thread and in bold print in the topic, but I felt I should reiterate due to the current finality of the touch panel situation.

The new tp_SYN3032.img (touch panel image) prevents any access to the touch screen in custom recovery, or in custom (non-stock) ROMs. I initially flashed the full firmware and had this happen to me. Rolling back to the version from the previous ROM version (3.15) gets it working again, but it was a hassle to deal with.

I also posted up some stock rooted full ROM versions of the OTA here in case anyone really wants to try it. And of course my firmware thread has the full firmware minus the problem images already posted.

So please, use the above resources, and do not learn the hard way!!
Click to expand...
 
UPDATE: A TWRP update has been released that restores touch screen functionality (2.4.1.0). So if any poor saps actually took the OTA while S-ON, at least they can still flash stuff.

But again, people wouldn't have been in that predicament if they hadn't updated in the first place :rolleyes:.
 
so none of the yukky from the last update, I can just grab the full update and go? last time i just updated radios.
 
I'm not sure if anyone else has seen this but it's kind of a big deal when flashing Firmware.

In Post #864 I think Fuses is saying that if you've skipped any of the Firmware updates and then flash the newest one you will brick your phone.

http://forum.xda-developers.com/showthread.php?t=1704612&page=87

If I'm reading that wrong then someone please correct me.

I'm not on the newest yet. But I do have the previous.
 
EarlyMon said:
/facepalm

The case for keeping current with radios. :(

edit - presuming that's cause and not coincidence.
Click to expand...

According to Fuses, this is the case. :(

Also the good Cap'n updated the OP for the Firmware downloads page:

http://forum.xda-developers.com/showpost.php?p=37558328&postcount=888
Originally Posted by Fuses
radio + bootloaders. In this case only bootloaders matters. Bootloader mismatch after flashing OTA firmware on top of the old firmware is causing these bricks. Long story short, device crashes during boot-sequence.
Originally Posted by Captain_Throwback
This is the same thing that was causing the firmware downgrade bricks. Thanks for your input Fuses. Warnings added to OP and downloads post. Those SBL partitions are really touchy.
Click to expand...
 
Wow, what a hassle! :confused:

I wonder if there is anything in this update that is even worth flashing?

One guy said his 3g was better since flashing, but I don't know how he can say that definitively, too many variables can influence it, as far as I can tell.

I haven't had the prox issue to speak of and don't care about the sound on camera... My bluetooth works with what I have to pair it with.

Almost the only reason to update I can see is to be current in case another comes out I do want to take, so I don't skip this one by accident. :(
 
Tried flashing the radios last night (3.15 then 3.16, in that order) but they didn't stick. I was trying flash them through the bout loader (hboot 1.12.2222), might try flashing through TWRP. Any thoughts on the subject?
 
CYNICALifornia said:
Tried flashing the radios last night (3.15 then 3.16, in that order) but they didn't stick. I was trying flash them through the bout loader (hboot 1.12.2222), might try flashing through TWRP. Any thoughts on the subject?
Click to expand...

did you get an error? or did it flash correctly in the bootloader, but nothing happened? did you name the file correctly? was on it on the sd card and not in any folder?
 
ocnbrze said:
did you get an error? or did it flash correctly in the bootloader, but nothing happened? did you name the file correctly? was on it on the sd card and not in any folder?
Click to expand...

Sends like it flashed correctly in the boot loader buy nothing happened. The name was correct and the file was on the root of my SD. No errors.

Had me scratching my head a bit.
 
glad I havent updated yet. no service for 2 hours, then i see this. looking grim...
 
EarlyMon said:
If you've not been staying up with firmware updates (via s-off), then flash them incrementally, in order, to avoid the problems.

Verify md5 before flashing, and verify that the flash took.
Click to expand...

I was going incrementally, thanks to the advice in the thread.


Also, I was checking md5s, and doing a nandroid before trying anything.


EarlyMon said:
Don't try flashing PJxxxx.zip files through TWRP - they're not the right format
Click to expand...

I wasn't. I was trying to flash them through the bootloader.
 
CapThrowback said:
Are you sure you're not updated? What does it say in your "About phone" settings?
Click to expand...

This was my exact thought as well.

It doesn't really do anything that you notice, except it will change your info on the "About Phone" / Software / Baseband screen. Here it will show your baseband (radio) number, your PRI, and PRL. This is where you'll see it.

You can see your baseband number on your bootloader screen info as well. ;)
 
Granite1 said:
This was my exact thought as well.

It doesn't really do anything that you notice, except it will change your info on the "About Phone" / Software / Baseband screen. Here it will show your baseband (radio) number, your PRI, and PRL. This is where you'll see it.

You can see your baseband number on your bootloader screen info as well. ;)
Click to expand...

That is how I know it didn't stick. It's really odd, but no?
 
CYNICALifornia said:
That is how I know it didn't stick. It's really odd, but no?
Click to expand...

Ok, I got my radios updated, not when I try to flash this, it boots into the bootloader. If I select 'reboot, it just brings me back to the boot loader.

I did the md5 and it was good. I ran super wipe three times before flashing.

What am I missing? I just wanna be on JB like all the cool kids...
 
CYNICALifornia said:
Ok, I got my radios updated, not when I try to flash this, it boots into the bootloader. If I select 'reboot, it just brings me back to the boot loader.

I did the md5 and it was good. I ran super wipe three times before flashing.

What am I missing? I just wanna be on JB like all the cool kids...
Click to expand...
Came here to report the same problem. MD5 checked out, but the install just screws up everything and you're stuck on the bootscreen.

I was able to go back to recovery just fine though and restore a nandroid backup that I made just prior to flashing the radio/firmware and the update. Incidentally though, when I check the PRL/Radio/PRI -- it's still the newest version despite doing a full nandroid restore from a pre-firmware-update state. Any thoughts on that?

Edit: I did a dirty flash for the 3.16 update; I didn't wipe at all and got the same result.
 
ocnbrze said:
besides superwipe what did you actually wipe? do not just rely on superwipe.
Click to expand...

I tried both running super wipe and manually wiping cache, dalvik, system, and data. Same result.





NeoteriX said:
Came here to report the same problem. MD5 checked out, but the install just screws up everything and you're stuck on the bootscreen.

I was able to go back to recovery just fine though and restore a nandroid backup that I made just prior to flashing the radio/firmware and the update. Incidentally though, when I check the PRL/Radio/PRI -- it's still the newest version despite doing a full nandroid restore from a pre-firmware-update state. Any thoughts on that?

Edit: I did a dirty flash for the 3.16 update; I didn't wipe at all and got the same result.
Click to expand...

I feel better knowing it may not be me... Also kudos to EarlyMon who taught me to ALWAYS make a nandroid before trying anything.
 
I'm reading some of the XDA posts on this -- do you know what version of TWRP you're running? There is some suggestion there that if you updated to 2.4.1 like me (latest version has the touchscreen fix for people that might have been impacted by the earlier version of the firmware update) that might be a cause of the problems.
 
You must log in or register to reply here.
Back
Top Bottom