Failed Update 3/29/12 (Red Exclamation) Fix[[All Firmware]] - Asus Eee Pad Transformer Prime

WARNING
If your bootloader is unlocked and you flashed a custom recovery, YOU WILL BRICK YOUR DEVICE BY ATTEMPTING THE STEPS BELOW!
Description
This method will allow you to apply any ICS or Honeycomb update to your tablet, no matter what the SKU of the update. This makes it possible to switch SKU's (eg. from WW to US) or to downgrade from ICS to Honeycomb. This means non US tablets can install the 9.4.2.13 US version or downgrade to 9.4.2.11 or even Honeycomb if experiencing problems.
Requirements
root access
ADB access
Disclaimer
While this process appears to work on everyone's device, you have to assume all risks due to unforeseen circumstances and need to understand there is a risk of bricking your tablet during the update. Although someone else was successful in downgrading from ICS to Honeycomb, there has been a report of a TFP bootlooping. Everyone else has been successful in downgrading from ICS 9.4.2.13 to ICS 9.4.2.11.
UPDATE: 2 reports so far of tablets bootlooping after downgrading to Honeycomb.
Notes
It's possible OTA updates will not apply when switching SKUs. However, you can always switch back to the proper SKU once an update is available. The Honeycomb update may wipe all data so ensure a full backup of apps & data is performed (eg. by using Titanium Backup) It's not recommended to restore "system" data using Titanium Backup when changing between Android versions When downgrading to a previous version of ICS, "Launcher" will force close requiring to wipe Launcher data in the Apps menu. Voodoo Rootkeeper may not be able to restore root after updating to 9.4.2.13. The "blob" file is contained within a ZIP file contained within the downloaded ZIP file.
Instructions
1. Download one of the updates (eg. US_epaduser9_4_2_13UpdateLauncher.zip) from here: http://support.asus.com/download.asp...2&hashedid=n/a (older firmwares are available at the end of this post) 2. Extract files from within zip 3. Extract files again from the extracted zip 4. Copy extracted "blob" file to root of folder of the removable Micro SD card or some other folder 5. Through ADB shell or Terminal Emulator, run the following: (May take from 5 to 20 minutes) Code: su dd if=/Removable/MicroSD/blob of=/dev/block/mmcblk0p4
If copying the "blob" file to the SD card in the keyboard dock, use: dd if=/Removable/SD/blob of=/dev/block/mmcblk0p4 If copying it to the internal memory, use: dd if=/sdcard/blob of=/dev/block/mmcblk0p4
6. Reboot only if the following is displayed: Note: This may take up to 10 min so be patient
1068769+1 records in 1068769+1 records out 547210197 bytes transferred in 153.991 secs (3553520 bytes/sec)
7. Update process will automatically launch 8. OPTIONAL: Once booted up, root device by using Mempodroid Root or some other method that supports the new version.
8. Now install new firmware. Go to Settings-About Tablet-system firmware
Older Firmwares
8.8.3.33 US: http://dl.dropbox.com/u/8822437/Upda...er8_8_3_33.zip

we already have this In developement section. its been there for the longest time now. good info though

demandarin said:
we already have this In developement section. its been there for the longest time now. good info though
Click to expand...
Click to collapse
I know just reposted it for those that don't visit the forum often

It worked.....yes

So I have WW version and was rooted and tried to OTA update to 4.2.2 and got the red triangle.
After much looking on these threads and help from a user I proceeded to do the dplpkgfile method, copy file and command etc to cache and cache/recovery. temp unroot and tried recovery.
It still wouldnt work so did a factory reset and still no go.
Even tried manually installing firmware by placing it on an sd card, that failed as did renaming the firmware on the sd card and trying recovery
So I am at a loss.. I havent modified build.prop or frozen any apps.. Don't know what else I can try to get this thing to update.. Should I try to do full unroot with Super SU?
Appreciate any help
Cheers

Related

[How-To] Update to Jellybean if you're having problems with OTA

So after trying multiple times to update my tablet an failing everytime. I checked the last_log file in /cache/recovery and found out that the reason the update was failing because I've deleted Netflix.apk from /system/app.
Since I did not backup the application I had no way to use the OTA, however after a few hours research I found out a method to completely restore the system to stock.
Part 1: Restoring Tablet to Stock
1. Download the system dump that matches your current software:
9.4.2.28
WW - http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF201/WW_epaduser9_4_2_28UpdateLauncher.zip - MD5 - 68D41197B399967B7F6789E47683A0D7
US - http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF201/US_epaduser9_4_2_28UpdateLauncher.zip - MD5 - DF17D3129378E9A7F81C58AF7BF5396B
TW - http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF201/TW_epaduser9_4_2_28UpdateLauncher.zip- MD5 - 3999B0E052211AA53ED1DB5D06A02AD3
2. Unzip the compressed firmware file to the root directory of a MicroSD card (external). Only extract this once so your sdcard should look something like this:
/MicroSD/US_epad-user-9.4.2.28.zip
3.With your Transformer turned on, insert the MicroSD into the MicroSD card slot.
4. An exclamation mark should appear in the notification area.
5. Tap the mark and proceed with the update.
6. Your tablet should now reboot and proceed to update the tablet, if you get an error try redownloading the update and trying again.
Part 2: Rooting your Tablet
Voodoo root keeper didn't save my root after part 1, so to root it I used Debugfs automated root:
http://forum.xda-developers.com/showthread.php?t=1706588
After your tablet is rooted you should use OTA root keeper to backup your root.
Part 3: Manual Update to Jellybean
1.Download the dlpkgfile for your system, I uploaded the US file: <--------------- US ONLY don't try if your tablet is not on US firmware, it might brick
http://www.mediafire.com/?ddcl3k233kxsvv8
WW version dlpkgfile <--------------- WW ONLY don't try if your tablet is not on WW firmware, it might brick
The WW update file (thanks for kikistans for uploading):
http://dropbox.com/s/uiui6ha6hrg2mg1/dlpkgfile
http://www.mediafire.com/download.php?kzr30e1vufbgee9
2. Place the dlpkgfile on your tablet's storage, MAKE SURE THE dlpkgfile does not have a .zip extension, the file has no extension!
3. Download ES File manager and go to settings>root settings and tick all the boxes.
4. Copy dlpkgfile to /cache
5. Go to /cache/recovery and create a new file named command
6. Open the file as a text and place the following code in it and save:
--update_package=/cache/dlpkgfile
7. Turn off the tablet
8. Press and hold volume down+power until the tablet vibrates then release power and keep holding volume down
9 When a text shows on the boot logo screen release volume down and click volume up
10. The tablet should now start updating, it'll take about 30 minutes and once the tablet boots you'll have jellybean
11. Restore root with root keeper
This method should work for everyone with a locked bootloader:good:
Edit:
Sorry I've been busy, it seems like some people are missing 3 files, follow this thread if you're missing those files:
http://forum.xda-developers.com/showthread.php?t=1909820
Also some people are reporting that their tablet is get bricked, MAKE SURE THAT YOU'RE USING THE RIGHT FIRMWARE UPGRADE
new-tilus has reported that this method worked for his stock unlocked tablet.
I used the last part more our less. Ota rootkeeper claims I have root. But I don't. Photocopier still keeps root access, but I cannot gain any new root access.
Sent from my SAMSUNG-SGH-I717 using xda premium
It doesnt work for me. Im on .28 stock WW version. It starts but then appears android with red trangle
lukcinek said:
It doesnt work for me. Im on .28 stock WW version. It starts but then appears android with red trangle
Click to expand...
Click to collapse
Same here, no success for me either...
Didn't work
Sent from my Transformer Prime TF201 using xda premium
Do we really need to go thru the hardship? Isn't ASUS going to fix it?
I think it must be noted that the OTA update for a WW variant will not work on a US variant, a DE will not work on TW and so on. The SKU for the OTA must match the SKU of the Prime in question.
It works. It doesnt befor becouse I didnt delete .bin from name of the file
Uh, fix what? ASUS is in the business of doing firmware updates for stock + unlocked devices.
Spidey01 said:
Uh, fix what? ASUS is in the business of doing firmware updates for stock + unlocked devices.
Click to expand...
Click to collapse
It seems to work here, I did exactly what "Protato" wrote and it's been loading the new JB for more than 10 minutes and no triangle yet
It worked I am on JB 4.1.1, forllow the instructions "literally" and it will work!
by far the simplest instructions to follow
i was having the same issue as most of you, i was (stock) rooted and applied the OTA update. i did have OTA root keeper, but my update failed and i lost root. i did a factory reset of 9.4.2.28 (US version) after a backup, then i rooted using DebugfsRoot_Generic. i more or less performed part 3 of this thread although i had to add three missing files to /system/xbin/ (maybe if i would have applied the stock 9.4.2.28 file i could have skipped this step). i forgot to restore my backup before i applied the update so i lost root. updating and keeping root may require SuperSU instead of SuperUser, from what i read last night. i hope this helps, thanx to all the people out there, especially @Wipeout and @Trekest from the post below, as well as @sparkym2 for Debugfs and @1wayjonny for Universal Naked Driver 0.7 and @Protato. good luck, i wish this thread was around yesterday evening, it would have saved me hours...
missing files from the below thread post #111
http://forum.xda-developers.com/showthread.php?t=1907804&page=12
Got red triangle, will try again.
work for me! thanks
Anybody remember how to have Flash working again.
For me it works on default browser, but it's not working anymore on Boat Browser.
I saw a thread this morning, but now I can't remember where it is.
Thanks if any link will be passed here.
1. Downloaded US version (mine is US build) - checked MD5 version to be the same.
2. Extracted once and copied the .zip to the root of external memory card.
3. Upgrade file detected - proceed with upgrade
4. Reboot. Then progress bar for upgrade.
5. Device started with a message that upgrade process completed. I am still seeing 4.0.3
Sorry posted too early.. still need to follow step 2 & 3.
-----------------------
*** PERFECT ***
All steps worked EXACTLY as explained in OP :good:. I am running JB now. Even I managed to restore root explained. Thanks you very much !!!
Thanks for this! I applied steps 1 through 3 and no problems updating to Jelly Bean! Although I protected root. I lost root after update:/ Oh well. small price to pay for Jelly Bean!
ES file explorer will not allow copy of needed file.
bimbobo said:
It seems to work here, I did exactly what "Protato" wrote and it's been loading the new JB for more than 10 minutes and no triangle yet
It worked I am on JB 4.1.1, forllow the instructions "literally" and it will work!
Click to expand...
Click to collapse
Can't get Es file ex. to allow me to copy the file to the cache folder, says copy failed? Any suggestions?
sly.cooper said:
1. Downloaded US version (mine is US build) - checked MD5 version to be the same.
2. Extracted once and copied the .zip to the root of external memory card.
3. Upgrade file detected - proceed with upgrade
4. Reboot. Then progress bar for upgrade.
5. Device started with a message that upgrade process completed. I am still seeing 4.0.3
Sorry posted too early.. still need to follow step 2 & 3.
Click to expand...
Click to collapse
Yeah, this happened to be too.
Battery is too drained now. Charging and will try again when I have enough juice.
StephanBotha said:
Yeah, this happened to be too.
Battery is too drained now. Charging and will try again when I have enough juice.
Click to expand...
Click to collapse
You still need steps 2 and 3
still got red andy. everything worked up until that.
Protato said:
So after trying multiple times to update my tablet an failing everytime. I checked the last_log file in /cache/recovery and found out that the reason the update was failing because I've deleted Netflix.apk from /system/app.
Since I did not backup the application I had no way to use the OTA, however after a few hours research I found out a method to completely restore the system to stock.
Part 1: Restoring Tablet to Stock
1. Download the system dump that matches your current software:
9.4.2.28
WW - http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF201/WW_epaduser9_4_2_28UpdateLauncher.zip - MD5 - 68D41197B399967B7F6789E47683A0D7
US - http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF201/US_epaduser9_4_2_28UpdateLauncher.zip - MD5 - DF17D3129378E9A7F81C58AF7BF5396B
TW - http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF201/TW_epaduser9_4_2_28UpdateLauncher.zip- MD5 - 3999B0E052211AA53ED1DB5D06A02AD3
2. Unzip the compressed firmware file to the root directory of a MicroSD card (external). Only extract this once so your sdcard should look something like this:
/MicroSD/US_epad-user-9.4.2.28.zip
3.With your Transformer turned on, insert the MicroSD into the MicroSD card slot.
4. An exclamation mark should appear in the notification area.
5. Tap the mark and proceed with the update.
6. Your tablet should now reboot and proceed to update the tablet, if you get an error try redownloading the update and trying again.
Part 2: Rooting your Tablet
Voodoo root keeper didn't save my root after part 1, so to root it I used Debugfs automated root:
http://forum.xda-developers.com/showthread.php?t=1706588
After your tablet is rooted you should use OTA root keeper to backup your root.
Part 3: Manual Update to Jellybean
1.Download the dlpkgfile for your system, I uploaded the US file:
http://www.mediafire.com/?ddcl3k233kxsvv8
2. Place the dlpkgfile on your tablet's storage.
3. Download ES File manager and go to settings>root settings and tick all the boxes.
4. Copy dlpkgfile to /cache
5. Go to /cache/recovery and create a new file named command
6. Open the file as a text and place the following code in it and save:
--update_package=/cache/dlpkgfile
7. Turn off the tablet
8. Press and hold volume down+power until the tablet vibrates then release power and keep holding volume down
9 When a text shows on the boot logo screen release volume down and click volume up
10. The tablet should now start updating, it'll take about 30 minutes and once the tablet boots you'll have jellybean
11. Restore root with root keeper
This method should work for everyone with a locked bootloader:good:
Click to expand...
Click to collapse
still got red andy, followed instructions to the tee!

[Q] Manually update TF201 to Jelly Bean

Greetings All,
I am attempting to update my TF201 to Jelly Bean but am not having any luck. The OTA update failed initially, and now when I search for updates, the tablet says there are none. I then decided to get the update file manually, but I can't get my tablet to discover that the update is present and ready to be installed. Can't figure out what I am doing wrong. Everything I have read thus far says to download the update, extract the zip file (resulting in another zip file with a slightly different name - I am on the WW version of the tablet BTW) to the root of the tablets internal storage, and reboot the device. Once it boots up again, it should detect the update and prompt me to install it.
Regardless of whether I put it on the internal storage, or on the external SD card, I cannot get this thing to detect the update and prompt me to install. I have also attempted extracting the second zip file so I end up with a META-INF folder and the blob. Putting this in the root of the internal storage and the root of the SD card didn't work either.
The device is currently rooted, and has been reset to factory several times during this process.
Any suggestions? Have I missed something totally obvious here?
Thanks!
Edit: Currently running ICS, on the stock 9.4.2.28 build from Asus.
Can't post links right now but trekest has a method that worked for me
Sent from my Zio using xda app-developers app
McJesus15 said:
Can't post links right now but trekest has a method that worked for me
Sent from my Zio using xda app-developers app
Click to expand...
Click to collapse
This one?
http://forum.xda-developers.com/showpost.php?p=32099246&postcount=154
Followed it to the letter. Rebooted the tablet once I had done everything specified via shell and the tablet simply rebooted. Still on ICS. Tried to replace the build.prop as mentioned at the bottom (after backing up my existing one of course), and it still simply rebooted.
Update: After a few more reboots, the tablet detected the update file. Unfortunately, the dlpkgfile I got was the US version (I need the WW version). An alternate download link from the one listed in the link above also gave me the US version (even though the poster said it was WW). Once I find the WW version, I should be able to get this update wrapped up.
I had the same problem.
In my case the solution was to copy the extracted ZIP file to the root folder, rename it to 'dlpkgfile' then reboot.
When it restarted, I then had the prompt that a system update was available but on checking the root folder, the 'dlpkgfile' file had been deleted so I repeated the process above, then clicked the update notification & away it went & did the update normally.
Hope that helps.
magrath1 said:
I had the same problem.
In my case the solution was to copy the extracted ZIP file to the root folder, rename it to 'dlpkgfile' then reboot.
When it restarted, I then had the prompt that a system update was available but on checking the root folder, the 'dlpkgfile' file had been deleted so I repeated the process above, then clicked the update notification & away it went & did the update normally.
Hope that helps.
Click to expand...
Click to collapse
Seems to have worked. Thanks!
I backed up my root from ICS, but when I started VooDoo again, my root backup was gone. Is there a working root tool available yet? Or is JB rooting still being worked on? I've been poking around the forum but have only turned up rooting tools that work for ICS thus far.
dochouse said:
Seems to have worked. Thanks!
I backed up my root from ICS, but when I started VooDoo again, my root backup was gone. Is there a working root tool available yet? Or is JB rooting still being worked on? I've been poking around the forum but have only turned up rooting tools that work for ICS thus far.
Click to expand...
Click to collapse
Yeah. Same here.
Apparently it can be done by rolling back to an old ICS version, updating to .28, backing up root with RootKeeper, re-flashing JB & restoring root. Seems like a lot of trouble though.
Think I'll just wait until someone meare learned than I comes up with a working exploit...I'm sure it won't be too long.
magrath1 said:
I had the same problem.
In my case the solution was to copy the extracted ZIP file to the root folder, rename it to 'dlpkgfile' then reboot.
When it restarted, I then had the prompt that a system update was available but on checking the root folder, the 'dlpkgfile' file had been deleted so I repeated the process above, then clicked the update notification & away it went & did the update normally.
Hope that helps.
Click to expand...
Click to collapse
I just tried doing this several times and on my tablet the update starts but then at about one third in it stops and fails. I have repeated the process 5 times using all the suggestions and even re downloading the file and same thing, I am just going to wait but so far no OTA available yet when I do the firmware update check it just tells me no update available for my device .
Finally tried using Baxbuda's manual method by downloading the firmware from Asus then renaming the file EP201_SDUPDATE.zip and copying the file to my MicroSD card and started the update using the power + vol. down, then releasing the power button and pressing the vol. up and it completed the upadate and I now have JB and so far it is fast and smooth with no issues to report
Jesse6749 said:
I just tried doing this several times and on my tablet the update starts but then at about one third in it stops and fails. I have repeated the process 5 times using all the suggestions and even re downloading the file and same thing, I am just going to wait but so far no OTA available yet when I do the firmware update check it just tells me no update available for my device .
Finally tried using Baxbuda's manual method by downloading the firmware from Asus then renaming the file EP201_SDUPDATE.zip and copying the file to my MicroSD card and started the update using the power + vol. down, then releasing the power button and pressing the vol. up and it completed the upadate and I now have JB and so far it is fast and smooth with no issues to report
Click to expand...
Click to collapse
Tried both of the reported method and I had no luck at all. With the Power+vol down. then releasing power and then pressing vol.up... when is this done?
The following worked for me.
-------------------------------------------------------
To update to new firmware versions for the tablet.
Download the appropriate update from ASUS support website for the TF201 Transformer Prime Tablet
Extract the zip file within the downloaded zip file from ASUS support.
Get an SD card of some sort.
Create the Folder \ASUS
Create the folder \ASUS\Update within the ASUS folder
Copy and Paste the US-epad-user-x.x.x.x.zip file into the \ASUS\Update folder.
Plug the SD card into the Tablet. It will show a triangle with ! in the system area.
Tap on it to start the update process.
anyone managed to root a tf201 with the latest asus jellbean rom on? seems a real pain to have to flash down to the factory rom, unlock, root then install a custom rom.
when i say "real pain" i mean, it's a heap more hassle than trying out a few custom roms on my i9300!

[Q] How to upgrade stock ROM/Firmware with rooted/CWM Phone?

Hello,
I have rooted the Galaxy Notes SGH-i317M, and install the CWM recovery.
The question is how can I do the stock update, for custom ROM it's look easy just ue CWM. I tried to search for the answers for the last few days, but nothings is conclusive?
1. I have tried with ODIN Mobile, while it was able to keep the root (with everroot), it lost the CWM (it sent back to stock recovery), so I have to reinstall it
2. With Desktop ODIN, then the root and CWM is gone, so have to reinstall it (both ODIN and CWM) and restore apps/data though a backup (like titanium backup)
And a side question is there a site that I can download the OTA update or I have to wait it push to the phone and don't install it, and follow this procedure?
Download the OTA package
Open it on your computer, and delete the recovery folder from inside the .zip file
Place the zip file on the root of your SD card
Unless you're able to mount the system and edit file permissions while in recovery, install OTA Rootkeeper from the market and run it
Reboot into CWM and make a backup
Flash the OTA package you put in your sdcard folder in step 3
Reboot, rerun OTA Rootkeeper, or chmod 4755 /system/bin/su while in recovery then reboot
Click to expand...
Click to collapse
Thanks

about ready to shooot HDX! Locking up while trying to transfer file

I am in the middle of this process by by kaeru00
Originally Posted by kaeru00
USE IT AT YOUR OWN RESPONSIBILITY because rewrite recovery partition.
How to use it.
1. install Towelroot and Supersu using KFHDX Toolkit v 0.94
2. If Disable OTA update , Airplane mode ON and Enable OTA update
3. If Install SafeStrap, uninstall safestrap on App.
4. Put "update-kindle-1X.3.1.0_user_310079820.bin" in SAME folder,
5. execute install.bat
6. reboot
7. put update-kindle-1X.3.1.0_user_310079820.bin" in internal storage.
8. Downgrade, wait a minute on the update menu, because display update button to take time.
9. disable OTA update.
This batch file works "kindle fire hdx 7" ONLY
This is tested on version 13.3.2.5 and 13.3.2.6.
Click to expand...
Click to collapse
i have done the install.bat and now i am trying to put the update.bin into internal storage but everytime it FREEZES up and i have to reboot the device.
I did get the file to the /sdcard but i am assuming i need to go to the root /... right? but eveytime i try and put the file there it freezing at around 80% and locks up the kindle, than i have to reboot?!
AGAHAHGHAAHHHHHH!!!! what i am doing worng?
The file should stay in /sdcard.
WELL THAN!!! (yeah i really try not to annoy yall with stupid questions, but we all start somewhere ..... )
I assumed it wasnt in the right spot because i was not seeing any update button......... gah.
thanks.
looks like i will take this to the appropriate thread. Sorry for posting a new one. Please feel free to delete this .

Update Fota Lollipop 43 to MM 13.6.5.30 (WW)

I try update via recovery ( put this file to external strorage only )
1. boot to recovery mode hold Power + Volume Down button
2. Using the Volume buttons to scroll and the Power button to select, choose "Enter
recovery mode
3. Choose apply update from external storage
4. select "reboot system now after finished update
http://fota.asus.com/delta_package/.../WW_PF500KL-12.2.2.43-13.6.5.30-fota-user.zip
This screenshoot from my phone +Station
Error Status 7
I have error:
System partition has unexpected contents
E:Error in /sdcard/UL-ASUS_TOON-WW-13.6.5.30-user.zip
(Status 7)
anyone can help me?!
Same issue as well
Getting the same "System partition has unexpected contents (Status 7 )" any idea whats wrong?
It's most likely because of root, and any changes like installing busybox, or having edited the build.prop . I had to wipe system on my padfone x reinstall lollipop 43 then install the marshmallow ota, then root 2.68 then dd the Xmodem.img I found for USA radio bands and the twrp 3.0.0.0 img to get everything working.
Also I'm not sure if flashing without wiping data partition works the same as well as starting from scratch, but I did do it all in one shot and first without data being wiped and worked fine. But I then wiped everything to see how much space I could recover in app storage. I saved myself about a gigabyte and a half to have a total of 4gb remaining after apps were installed (i have a lot of apps)
Gizoid1337 said:
It's most likely because of root, and any changes like installing busybox, or having edited the build.prop . I had to wipe system on my padfone x reinstall lollipop 43 then install the marshmallow ota, then root 2.68 then dd the Xmodem.img I found for USA radio bands and the twrp 3.0.0.0 img to get everything working.
Also I'm not sure if flashing without wiping data partition works the same as well as starting from scratch, but I did do it all in one shot and first without data being wiped and worked fine. But I then wiped everything to see how much space I could recover in app storage. I saved myself about a gigabyte and a half to have a total of 4gb remaining after apps were installed (i have a lot of apps)
Click to expand...
Click to collapse
Thanks ! It worked for me
I reinstalled ver 12.2.2.43 which really is my current version, and then proceed to install MM 13.6.5.30 with success
Gizoid1337 said:
It's most likely because of root, and any changes like installing busybox, or having edited the build.prop . I had to wipe system on my padfone x reinstall lollipop 43 then install the marshmallow ota, then root 2.68 then dd the Xmodem.img I found for USA radio bands and the twrp 3.0.0.0 img to get everything working.
Also I'm not sure if flashing without wiping data partition works the same as well as starting from scratch, but I did do it all in one shot and first without data being wiped and worked fine. But I then wiped everything to see how much space I could recover in app storage. I saved myself about a gigabyte and a half to have a total of 4gb remaining after apps were installed (i have a lot of apps)
Click to expand...
Click to collapse
Thanks to you I have updated my phone to marshmallow using twrp 3.0.0, which allowed me to re-unlock bootloader, and root my phone.
It can be done, you just need to remove a few lines in the updater-script file.
something with ro.fingerprint (that identifies the recovery, it was originally expecting stock).
Replace it inside the zip. Then transfer update to sd card or internal.
After that wipe system, then reflash .43, right after that flash the mm update.
Will take some time but it should work once everything is verified.
reflash bl unlock and twrp (just a precaution) , then you can leave.
It would say no os but ignore it.
First boot takes around 10-15 mins then presto you finally have it.
Haven't encountered any bugs yet and it freed up a lot of storage space. Makes me wonder why I had to wait for the update to come to me, so glad I'm done with that.
So that concludes the last major update for the padfone s.....
Can u help me pls? I've tried unroot ,wipe system data and reflash .43 which is my current rom but still got signature verification error. any suggestion to fix this? Thx
Justatechie said:
Thanks to you I have updated my phone to marshmallow using twrp 3.0.0, which allowed me to re-unlock bootloader, and root my phone.
It can be done, you just need to remove a few lines in the updater-script file.
something with ro.fingerprint (that identifies the recovery, it was originally expecting stock).
Replace it inside the zip. Then transfer update to sd card or internal.
.
Click to expand...
Click to collapse
which lines exactly ? cause i tried removing mine and im now getting an error in the zip
error 6 or something
dtgo said:
which lines exactly ? cause i tried removing mine and im now getting an error in the zip
error 6 or something
Click to expand...
Click to collapse
On Notepad++: (not sure about notepad, but you must get rid of ro.build.fingerprint lines and the abort command after)
Delete/Remove lines 7 through 9. If left alone or not deleted fully it will not accept the update because its looking at the recovery image.
It expects 5.0 stock recovery but it sees 6.0 twrp. (since it was built off the source of twrp 3.0.0 which is mainly compatable with 6.0+)
Thats about it.
NightbladeSinX said:
Can u help me pls? I've tried unroot ,wipe system data and reflash .43 which is my current rom but still got signature verification error. any suggestion to fix this? Thx
Click to expand...
Click to collapse
Thats odd.
You should probably Re-download or transfer the ww file again. Could just be a bad transfer of data.
Make sure you have twrp 3.0.0 and that system protection off. (it pops up on the first screen, but you can find it under twrp settings)
Justatechie said:
On Notepad++: (not sure about notepad, but you must get rid of ro.build.fingerprint lines and the abort command after)
Delete/Remove lines 7 through 9. If left alone or not deleted fully it will not accept the update because its looking at the recovery image.
It expects 5.0 stock recovery but it sees 6.0 twrp. (since it was built off the source of twrp 3.0.0 which is mainly compatable with 6.0+)
Thats about it.
Click to expand...
Click to collapse
thanks for the reply , i did that and got Error 6 but it just fails right there , no message or anything
dtgo said:
thanks for the reply , i did that and got Error 6 but it just fails right there , no message or anything
Click to expand...
Click to collapse
If it doesn't say anything about identifying the device model or checking system, then something is wrong.
Might be a bad edit or it might have gotten corrupted while transferring back into the zip.
I stick with N++ for the edits, sometimes windows file transfer can be a pain by itself while trying to replace the update script, 7zip might help.
dtgo said:
thanks for the reply , i did that and got Error 6 but it just fails right there , no message or anything
Click to expand...
Click to collapse
got it working thanks again man you've been a big help
Justatechie said:
On Notepad++: (not sure about notepad, but you must get rid of ro.build.fingerprint lines and the abort command after)
Delete/Remove lines 7 through 9. If left alone or not deleted fully it will not accept the update because its looking at the recovery image.
It expects 5.0 stock recovery but it sees 6.0 twrp. (since it was built off the source of twrp 3.0.0 which is mainly compatable with 6.0+)
Thats about it.
Thats odd.
You should probably Re-download or transfer the ww file again. Could just be a bad transfer of data.
Make sure you have twrp 3.0.0 and that system protection off. (it pops up on the first screen, but you can find it under twrp settings)
Click to expand...
Click to collapse
Thx for reply. i manage to get updated to 6.0.1 but now i lost root. i did mistake not flashing twrp before 1st boot n it replace twrp to stock rec. Is there any root method available yet? I've tried latest kingroot but it was unsuccessful. Any way is there any difference between WW and TW firmware version?
NightbladeSinX said:
Thx for reply. i manage to get updated to 6.0.1 but now i lost root. i did mistake not flashing twrp before 1st boot n it replace twrp to stock rec. Is there any root method available yet? I've tried latest kingroot but it was unsuccessful. Any way is there any difference between WW and TW firmware version?
Click to expand...
Click to collapse
You could probably flash recovery through fastboot, only if your bootloader is unlocked. If not it wont allow the flash. it would say FAILED cant flash unsigned image, but theres a chance that it might have been flashed, just check to see if changes have applied.
Assuming that you have went to the fastboot portion of your phone you can check its status.
if its not unlocked, then you have to find another way to root to flash your twrp recovery back on your phone.
Did this, but kept getting errors due to (probably) my use of xposed. Managed to soft brick my phone, and recovered it using http://forum.xda-developers.com/padfone-x/help/guide-restoring-stock-rom-recovery-t3179818
After that, had to edit updater-script to remove all checks.
What tripped me up was just how long the update reboot took. Almost half an hour. I was going to give up but decided to leave it while taking a short nap.
heres the updater script for anyone having issues
Please can someone help me?
I'm trying so hard to get this to work but I'm barely getting anywhere. What I've done (thanks to ninekaw9's guide):
- unlock bootloader
- wiped everything (yet there is still stuff in the file explorer, like the su install folder)
- using fastboot boot recovery:
-- use TWRP 2.8.7.0 to transfer files from sdcard to emmc
-- with TWRP 2.7.1.1:
--- installed WW 99.99.99.0 for KK (works)
--- installed WW 12.2.2.27 for LP & stock recovery (works)
--- installed WW 12.2.2.43 for latest LP (works)
- removed every abort line from updater script to get it to stop complaining about fingerprint/unexpected system contents
- installed modified FOTA WW 13.6.5.30 for MM (no OS change)
So after all that, I'm where I started but with no apps.
Before I found out 2.8.7.0 couldn't flash stock ROMs I flashed 12.2.2.43 after a full wipe and ended up with no System UI...
Outcomes from using different recovery to flash MM update:
2.7.1.1 with unmodified: apparently my phone is TW not WW (incorrect)
2.8.7.0 with unmodified: some weird fingerprint with omni-T00N and 5.1.1, even after wipe and stock 12.2.2.43 flash. Couldn't edit or replace the default.prop file, it would just get overwritten each time
stock with unmodified: couldn't even mount my SD card, so tried ADB sideload, got the unexpected system contents message
stock with modified (no sha1): would no longer allow me to ADB sideload (0.00x message)
TWRP (either) with modified (no prop): unexpected system contents
TWRP (either) with modified (no prop/sha1): seems to work, but upon boot to system, nothing appears to have changed.
I desperately want MM so I have a smaller system partition, then I can stop pushing updates to system to save space, and therefore won't need root so I can play Pokemon GO and use Sky Q.
That or I'm going to try Magisk... Has anyone used this on a Padfone?
If anyone can guide me through which files/folders I can delete from my phone to save space, that would be great. I know most folders are mounting points, but there's a lot of .sh files and other folders that I'm not familiar with.
I've asked in another thread where I can get TWRP 3.x for Padfone S, but nobody has replied!
Please can someone help me?
Nintynuts said:
I'm trying so hard to get this to work but I'm barely getting anywhere. What I've done (thanks to ninekaw9's guide):
- unlock bootloader
- wiped everything (yet there is still stuff in the file explorer, like the su install folder)
- using fastboot boot recovery:
- use TWRP 2.8.7.0 to transfer files from sdcard to emmc
- with TWRP 2.7.1.1:
- installed WW 99.99.99.0 for KK (works)
- installed WW 12.2.2.27 for LP & stock recovery (works)
- installed WW 12.2.2.43 for latest LP (works)
- removed every abort line from updater script to get it to stop complaining about fingerprint/unexpected system contents
- installed modified FOTA WW 13.6.5.30 for MM (no OS change)
So after all that, I'm where I started but with no apps.
Before I found out 2.8.7.0 couldn't flash stock ROMs I flashed 12.2.2.43 after a full wipe and ended up with no SystemUI...
Outcomes from using different recovery to flash MM update:
2.7.1.1 with unmodified: apparently my phone is TW not WW (incorrect)
2.8.7.0 with unmodified: some weird fingerprint with omni-T00N and 5.1.1, even after wipe and stock 12.2.2.43 flash. Couldn't edit or replace the default.prop file, it would just get overwritten each time
stock with unmodified: couldn't even mount my SD card, so tried ADB sideload, got the unexpected system contents messagestock with modified (no sha1): would no longer allow me to ADB sideload (0.00x message)
TWRP (either) with modified (no prop): unexpected system contents
TWRP (either) with modified (no prop/sha1): seems to work, but upon boot to system, nothing appears to have changed.
I desperately want MM so I have a smaller system partition, then I can stop pushing updates to system to save space, and therefore won't need root so I can play Pokemon GO and use Sky Q.
That or I'm going to try hiding root Magisk...
If anyone can guide me through which files/folders I can delete from my phone to save space, that would be great. I know most folders are mounting points, but there's a lot of .sh files and other folders that I'm not familiar with.
I've asked in another thread where I can get TWRP 3.x for Padfone S, but nobody has replied!
Please can someone help me?
Click to expand...
Click to collapse
I used twrp 3.0. Worked like a charm what I ended up doing was reflashing the .43 and then the update after replacing the updater script file here is a link to the thread with the 3.0 twrp http://forum.xda-developers.com/padfone-x/general/padfone-xs-to-stock-lollipop-root-t3263664
xantanion said:
I used twrp 3.0. Worked like a charm what I ended up doing was reflashing the .43 and then the update after replacing the updater script file here is a link to the thread with the 3.0 twrp http://forum.xda-developers.com/padfone-x/general/padfone-xs-to-stock-lollipop-root-t3263664
Click to expand...
Click to collapse
Thanks. No wonder I couldn't find it as it doesn't mention 3.0.0.0 or 3.x or any version number at all.
I have answered my own Q&A thread with a link so hopefully others can find it. Will try it now.
xantanion said:
I used twrp 3.0. Worked like a charm what I ended up doing was reflashing the .43 and then the update after replacing the updater script file here is a link to the thread with the 3.0 twrp http://forum.xda-developers.com/padfone-x/general/padfone-xs-to-stock-lollipop-root-t3263664
Click to expand...
Click to collapse
Thankfully it has worked many thanks. Unfortunately while Sky Q no longer complains about root, it does complain about my Padfone station being an external display, so still won't play videos

Categories

Resources