FORUMS
Remove All Ads from XDA

ASUS JellyBean 4.2.1 updates - a warning

12,752 posts
Thanks Meter: 15,732
 
By sbdags, Recognized Contributor on 24th March 2013, 01:04 AM
Post Reply Email Thread
Now I have your attention.

Yeah, I have no idea when it will be released but I thought I would just post a heads up on what has been going on over with the TF300 guys.

There are a lot of people who have now hard bricked their devices (probably 10 to 20 reported cases).

The issue is around the way Asus have implemented their latest boot loader - they seem to have changed the type of partitions it wants to use. I don't understand the full technical details but if you upgrade with the wrong combination of custom recovery it seems very easy to brick the device.

If you are unlocked and are not on TWRP 2.4.4.0 and don't flash a full ASUS STOCK FIRMWARE first it seems this is the most likely cause.

So for every one who is unlocked:

1. Don't try to flash OTA updates under any circumstances - this is the fastest way to hard brick. Noone has recovered from this

2. Make sure you are on TWRP 2.4.4.0 before updating and that includes flashing the FULL ASUS FIRMWARE hosted on their site. CWM is not supported currently.

3. Do not flash just a bootloader blob file from recovery until it can be confirmed it is safe to do so.


Anyway - no news from Asus yet but hopefully enough people will read this so we don't end up like the unfortunate TF300 crowd who have more bricked devices appearing every day as people don't read and think they can just update as they have been used to doing in the past.

BTW there is difficulty downgrading from 4.2.1 to 4.1.1 although one user has successfully done it - it seems very complicated to achieve. I will write it up once we understand it fully.

Please heed the warning folks. (This does not apply to stock locked users who can OTA from 4.1.1 to 4.2.1)
The Following 42 Users Say Thank You to sbdags For This Useful Post: [ View ] Gift sbdags Ad-Free
 
 
24th March 2013, 01:09 AM |#2  
sbdags's Avatar
OP Recognized Contributor
Flag Kenilworth, Coventry
Thanks Meter: 15,732
 
Donate to Me
More
Here is some info from PJC21 (does one of my themes) that may hep some of our expert users understand moreL

Quote:
Originally Posted by pjc21

Thought I'd start new thread for 4.2.1 Update Discussions, issues and other info

So first thing:

I have found out on 4.2.1 if you do fastboot command

Code:
fastboot -i 0x0b05 getvar all
The "bootloader" "recovery" & "boot" partitions are now in basic format, which means the fastboot format command will no longer work on these partitions as it is not a recognized format in fastboot, I never did try this on 4.1.1 when these partitions where in emmc format but believed it would have worked - anyone confirm this?

Code:
C:\android-sdk\platform-tools>fastboot -i 0x0b05 getvar all
(bootloader) version-bootloader: 1.0
(bootloader) version-baseband: 2.0
(bootloader) version: 0.4
(bootloader) serialno: 
(bootloader) mid: 001
(bootloader) product: Cardhu
(bootloader) secure: yes
(bootloader) unlocked: no
(bootloader) uart-on: yes
(bootloader) partition-size:bootloader: 0x0000000000800000
(bootloader) partition-type:bootloader: basic
(bootloader) partition-size:recovery: 0x0000000000800000
(bootloader) partition-type:recovery: basic
(bootloader) partition-size:boot: 0x0000000000800000
(bootloader) partition-type:boot: basic
(bootloader) partition-size:system: 0x0000000030000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x000000001ac00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x00000006b3680000
(bootloader) partition-type:userdata: ext4
all:
finished. total time: 0.105s
Not sure what this means as I cannot find any info on basic format & android
Anyone got any info on this?

The Following 3 Users Say Thank You to sbdags For This Useful Post: [ View ] Gift sbdags Ad-Free
24th March 2013, 01:34 AM |#3  
Recognized Developer / Recognized Contributor
Thanks Meter: 4,114
 
Donate to Me
More
Quote:
Originally Posted by sbdags

Here is some info from PJC21 (does one of my themes) that may hep some of our expert users understand moreL

It rather helps confuse me more.

Bootloader, recovery and boot partitions never had a filesystem and could never be formatted with fastboot. It can only format ext4. Other partition types can simply be erased or flashed as raw image.

(At least I learned something new - I didn't know that fastboot has ext4 support at all)
The Following User Says Thank You to _that For This Useful Post: [ View ]
24th March 2013, 03:10 AM |#4  
Member
Thanks Meter: 15
 
More
I'll just wait until you release cromi 4.2.1 . Asus can shove their update up their collective Assus, see what I did there, ah good times.
The Following 5 Users Say Thank You to iamborba For This Useful Post: [ View ] Gift iamborba Ad-Free
24th March 2013, 03:24 AM |#5  
Thats OK's Avatar
Senior Member
Thanks Meter: 278
 
More
Great thread!
Damn important stuff!
Who knows what will come of this.

Man I feel for those guys who bricked
The TF300 forum hasn't been a real happy place since the push.
24th March 2013, 03:28 AM |#6  
sbdags's Avatar
OP Recognized Contributor
Flag Kenilworth, Coventry
Thanks Meter: 15,732
 
Donate to Me
More
CROMI 4.0 for the TF300 is already out. I've been moonlighting. Not bad going since I don't actually have a TF300.

Been a long week
The Following 3 Users Say Thank You to sbdags For This Useful Post: [ View ] Gift sbdags Ad-Free
24th March 2013, 07:36 AM |#7  
Moscow Desire's Avatar
Retired Senior Moderator
Flag Somewhere in a Deep Cave on the Troll Kings Throne
Thanks Meter: 6,967
 
Donate to Me
More
Thread Temp Stickied as possible Warning
In light of what happened in the 300 forums as of late, I will temporarily Stick this as a Notice to 700 users.

Remember folks, don't be so quick to start flashing away with new updates. You never know what can happen.

MD's Rule #1 - NEVER take an OTA on a rooted device with unlocked Bootloader. Just asking for trouble. (yes, some people have been lucky)

Give the Dev's a chance to look things over first before you just "assume" everything is OK.

MD
The Following 7 Users Say Thank You to Moscow Desire For This Useful Post: [ View ] Gift Moscow Desire Ad-Free
24th March 2013, 07:46 AM |#8  
MartyHulskemper's Avatar
Senior Member
Thanks Meter: 414
 
More
Quote:
Originally Posted by iamborba

I'll just wait until you release cromi 4.2.1 . Asus can shove their update up their collective Assus, see what I did there, ah good times.

Redditor? I saw what you did there. Hehehe.
The Following User Says Thank You to MartyHulskemper For This Useful Post: [ View ] Gift MartyHulskemper Ad-Free
24th March 2013, 09:33 AM |#9  
Member
Thanks Meter: 2
 
More
hi to poster number one every time i do a full system update with asus full firmware via TWRP ir deletes TWRP will that make a difference?
The Following User Says Thank You to dady613 For This Useful Post: [ View ] Gift dady613 Ad-Free
24th March 2013, 06:29 PM |#10  
buhohitr's Avatar
Senior Member
Thanks Meter: 1,824
 
More
Quote:
Originally Posted by dady613

hi to poster number one every time i do a full system update with asus full firmware via TWRP ir deletes TWRP will that make a difference?

If you flash a full Asus firmware, it will remove your custom recovery (twrp). You need to reflash twrp again.
24th March 2013, 06:30 PM |#11  
rlm0n0's Avatar
Member
Flag Chicago
Thanks Meter: 15
 
More
Good looking out dudes.....
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes