Related
Hello all,
Since my TF701T returned from RMA (touch screen issues), it has drained the battery like hell.
So I decided to flash original firmware again (done that before sending it), only to find out it now failed with this error:
Verifying update package...
E:failed to open /sdcard/T4_SDUPDATE.zip (No such file or directory)
So I renamed the zip to that file, but it didn't help.
This package is for "K00C" devices; this is a "tf701t"
In custom recovery log, one can find this:
ro.build.product=tf701t
ro.product.device=tf701t
Installed CWM, then flashed 2 custom ROMs (CROMbi KK and last AOKP), either system is stuck on boot or systemui fails permanently preventing using the tablet.
Then I flashed the original firmware with CWM instead of stock recovery, system stuck on boot-loop, except with 11.4.1.17, boot up but systemui fails again.
It's like the tablet Asus sent me back is not really a TF701T ?
Any help would be highly appreciated as the tablet is unusable at the moment, only boot-loader and stock/custom recovery are accessible.
Can you provide a logcat of the boot process from an adb connection please. Also the recovery.log from cwm (it's in /tmp/recovery.log so adb pull /tmp/recovery.log recovery.log)
It sounds like your system partition is not getting setup correctly or /data is corrupted somehow.
Also for stock you have to flash the zip inside the zip - you did do that right?
Let me get this straight:
You are on the 11.4.1.17 bootloader? That would mean you had the latest stock 4.4.2 firmware installed right?
The T4_SDUPDATE.zip is WW JB 4.3 firmware, is it not? You tried to flash that in stock recovery?
I read about one user who tried to downgrade from 4.4.2 to 4.3 yesterday and that also failed.
Another user contacted Asus support and they told him a downgrade is not possible from 4.4.2. No idea if that is true. The Asus reps are not always well informed....
sbdags said:
Can you provide a logcat of the boot process from an adb connection please. Also the recovery.log from cwm (it's in /tmp/recovery.log so adb pull /tmp/recovery.log recovery.log)
It sounds like your system partition is not getting setup correctly or /data is corrupted somehow.
Also for stock you have to flash the zip inside the zip - you did do that right?
Click to expand...
Click to collapse
berndblb said:
Let me get this straight:
You are on the 11.4.1.17 bootloader? That would mean you had the latest stock 4.4.2 firmware installed right?
The T4_SDUPDATE.zip is WW JB 4.3 firmware, is it not? You tried to flash that in stock recovery?
I read about one user who tried to downgrade from 4.4.2 to 4.3 yesterday and that also failed.
Another user contacted Asus support and they told him a downgrade is not possible from 4.4.2. No idea if that is true. The Asus reps are not always well informed....
Click to expand...
Click to collapse
Thanks for replying. Turns out I made a series of misleading mistake
First: custom recovery was installed, so it would not install an original firmware (device identifier incorrect, k00c while expecting tf701t).
Second: tried installing a custom ROM using Aroma, but the full wipe option didn't worked and ROM would boot loop!
Third: started using a modified ZIP of the original firmware without device identifier check, which was not allowed to install in stock recovery.
Bootloader was still on 10.26, however the closest thing to work was to flash original 11.4 firmware in CWM
At the end I use the original firmware ZIP and copied it to /sdcard/S4_SDUPDATE.zip, flashed stock recovery, and it installed flawlessly. That's when I realized the full wipe never occurred, all data where still there!
Hi guys, I've been working on my ATT m7 for a day or so now.
Story:
I was on CWM recovery and CyanogenMod 11 M7 without any issues for a long time, rooted, S-OFF, etc. Phone all of a sudden got a bunch of force closes and errors such as "com.google.gapps has encountered an error and needs to close" it would repeatedly appear. I tried killing apps, force closing apps, etc to no avail.
I restarted the phone and it froze on the HTC logo. Hard reset, same thing. Wouldn't go past HTC logo. No big deal, went into recovery, cleared cache, Dalvik, reboot, hangs on HTC logo. Kept trying this, same result. Decided to just factory wipe and try that. Used adb to pull my files off the phone, then factory wiped, still no luck, hangs on HTC logo. Tried reflashing previously working CyanogenMod zip, no luck.
Flashed TWRP recovery and tried all of the above again, still no luck. Strangely, TWRP says it looks like my phone is not rooted and asks to install su. I verified root through adb shell, but TWRP still reports no root. Also verified in TWRP going to console and "whoami" gives "root" so not sure what's going on there.
Tried an RUU that looked like it was working, but then randomly failed out ERR 155.
Then I just happened to notice my bootloader says I now have S-ON! Wtf?
Not really sure what to try at this point, you guys have any suggestions?
Edit:
Just tried flashing a stock ATT Sense OTA zip but TWRP gives errors:
Full SELinux support is present
E: Unable to mount '/cache'
E: Unable to mount '/cache'
MTP Enabled
Installing '/sdcard/TWRP/ATT_Sense6_OTAPkg.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
file_getprop: failed to stat "/system/build.prop": No such file or directory
E: Error executing updater binary in zip '/sdcard/TWRP/ATT_Sense6_OTAPkg.zip'
Error flashing zip '/sdcard/TWRP/ATT_Sense6_OTAPkg.zip'
Updating partition details
E: Unable to mount '/cache'
eguh.
wingman358 said:
Hi guys, I've been working on my ATT m7 for a day or so now.
Story:
I was on CWM recovery and CyanogenMod 11 M7 without any issues for a long time, rooted, S-OFF, etc. Phone all of a sudden got a bunch of force closes and errors such as "com.google.gapps has encountered an error and needs to close" it would repeatedly appear. I tried killing apps, force closing apps, etc to no avail.
I restarted the phone and it froze on the HTC logo. Hard reset, same thing. Wouldn't go past HTC logo. No big deal, went into recovery, cleared cache, Dalvik, reboot, hangs on HTC logo. Kept trying this, same result. Decided to just factory wipe and try that. Used adb to pull my files off the phone, then factory wiped, still no luck, hangs on HTC logo. Tried reflashing previously working CyanogenMod zip, no luck.
Flashed TWRP recovery and tried all of the above again, still no luck. Strangely, TWRP says it looks like my phone is not rooted and asks to install su. I verified root through adb shell, but TWRP still reports no root. Also verified in TWRP going to console and "whoami" gives "root" so not sure what's going on there.
Tried an RUU that looked like it was working, but then randomly failed out ERR 155.
Then I just happened to notice my bootloader says I now have S-ON! Wtf?
Not really sure what to try at this point, you guys have any suggestions?
Edit:
Just tried flashing a stock ATT Sense OTA zip but TWRP gives errors:
Full SELinux support is present
E: Unable to mount '/cache'
E: Unable to mount '/cache'
MTP Enabled
Installing '/sdcard/TWRP/ATT_Sense6_OTAPkg.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
file_getprop: failed to stat "/system/build.prop": No such file or directory
E: Error executing updater binary in zip '/sdcard/TWRP/ATT_Sense6_OTAPkg.zip'
Error flashing zip '/sdcard/TWRP/ATT_Sense6_OTAPkg.zip'
Updating partition details
E: Unable to mount '/cache'
eguh.
Click to expand...
Click to collapse
you can not flash OTA, these are patches, not complete rom and when flashed over the appropriate rom version, must be done using stock recovery, not twrp.
What version of twrp are you using? CM11 need block:by-name support in the recovery kernel.
For your s-on issue, you probably have used 'fastboot oem writesecureflag3' command by mistake
alray said:
you can not flash OTA, these are patches, not complete rom and when flashed over the appropriate rom version, must be done using stock recovery, not twrp.
What version of twrp are you using? CM11 need block:by-name support in the recovery kernel.
For your s-on issue, you probably have used 'fastboot oem writesecureflag3' command by mistake
Click to expand...
Click to collapse
Thanks for the info... do you recommend trying a stock rom or CM11? I'm on the latest TWRP, it's v2.8.0.2.
And regarding the command 'fastboot oem writesecureflag3' I've never seen it before, and certainly haven't issued it by hand. Whether the command was issued by some tool or file I've tried, I don't know.
EDIT:
I think the reason for the RUU failure may be due to the version, I believe it was trying to flash 1.xx over 3.xx. Does that sound right? Also, is it correct that I need stock recovery and locked bootloader for a RUU??
wingman358 said:
Thanks for the info... do you recommend trying a stock rom or CM11? I'm on the latest TWRP, it's v2.8.0.2.
And regarding the command 'fastboot oem writesecureflag3' I've never seen it before, and certainly haven't issued it by hand. Whether the command was issued by some tool or file I've tried, I don't know.
EDIT:
I think the reason for the RUU failure may be due to the version, I believe it was trying to flash 1.xx over 3.xx. Does that sound right? Also, is it correct that I need stock recovery and locked bootloader for a RUU??
Click to expand...
Click to collapse
Well somehow I was able to flash a stock ROM ([ROM][4.4.2] - AT&T 4.18.502.7 Stock Rooted from this thread). Then flashed PA_gapps over (with dalvik and cache wipe before and after flashes).
On boot, it cleared the HTC logo (finally!). Then it hit me with "Google search has stopped unexpectedly" and goes back to the HTC logo... wtf... then it popped up "Dialer has stopped unexpectedly"... then the home screen came up, and it rebooted itself.
After rebooting, I swiped to unlock the screen and it showed the dreaded white HTC logo... ugh, then it hits me in quick succession with "Hangouts has stopped" "Google Play Music has stopped" "Youtube has stopped" and so on. If I hit the screen off button then turn it on, it showed the lock screen. The lock screen seemed fine, the clock worked, and swiping to unlock worked, but when it unlocked instead of the home screen it showed the white HTC logo. Eventually it rebooted itself. After I think the third time rebooting itself, the android setup/configuration came up. "_____ has stopped" keeps popping up.
I was able to restore contacts and stuff by signing into my google account, but I am almost continually getting "_____has stopped" pop-ups, and if I let the phone sit for a few minutes it reboots itself maybe every 5 minutes or so. Also I don't think I have cell service (it just shows an X with no bars). It seems normal aside from those (not much home screen lag, apps open, wifi seems to work).
I did a permissions fix from recovery which completed without errors, but it didn't seem to help.
wingman358 said:
Well somehow I was able to flash a stock ROM ([ROM][4.4.2] - AT&T 4.18.502.7 Stock Rooted from this thread). Then flashed PA_gapps over (with dalvik and cache wipe before and after flashes).
Click to expand...
Click to collapse
Why flashing gapps over a stock sense rom?
alray said:
Why flashing gapps over a stock sense rom?
Click to expand...
Click to collapse
Great question... I've been in the habit of always flashing gapps after flashing rom, does gapps come with stock rom??
wingman358 said:
Great question... I've been in the habit of always flashing gapps after flashing rom, does gapps come with stock rom??
Click to expand...
Click to collapse
Yes, wipe everything and reflash the rom
alray said:
Yes, wipe everything and reflash the rom
Click to expand...
Click to collapse
That did it! Wiped, reflashed, and no more force closes, not one. Thanks a bunch alray!!!
I have a Consumer Cellular XT1064 running 21.11.17.titan_retuaws.retuaws.en.US.na with an unlocked bootloader and am having trouble applying the lollipop ota upgrade patch. When I attempt to apply the patch in stock recovery, I get an error durning "Patching system files". The error reads "assert failed: apply_patch(*/system/framework/framework-res.apk" followed by a series of letters and numbers, and ultimately ending with "installation aborted".
I previously successfully applied the ota and was running Lollipop using this guide. While attempting to root, I couldn't get twrp to persist after a full boot nor could I successfully install supersu, so I decided to start from scratch (probably a bad move) and followed those same steps again, but this time ran into the assert failed error described above. I tried re-locking the bootloader, thinking that may help, but got error messages during the process, so that's a no-go. I've scoured the forums and web for another solution, but haven't come up with anything so far.
Maybe there are some files/settings that aren't being completely restored to 4.4.4 stock through the manual flashing process? I can't get RSD Lite to recognize this phone (even though it recognizes my Droid Maxx just fine).
Any other thoughts or suggestions would be much appreciated.
Solution for XT1064 assert failed errors when applying Lollipop ota
After much trial and error, I successfully found a way to get rid of the assert failed errors and get back to Lollipop. Thanks to diamondjoker5, I obtained the original retail firmware 21.11.23 and used fastboot commands to flash it over the 21.11.17 firmware. I then let the phone fully boot into 21.11.23, powered off, then followed the original ota update procedure once again, without any errors.
Hi all, new to the forums here. Sorry if this is in the wrong section. So I was trying to update my nexus 6 to 6.0.1 from 6.0 and I got this error
supported API: 3
Finding update package...
Opening update package...
Verifying update package...
Installing Update...
Source: google/shamu/shamu:6.0/MRA58K/2256973:user/release-keys
Target: google/shamu/shamu:6.0.1/MMB29K/2419427:user/release-keys
Verifying current system...
"EMMC:/dev/block/platform/msm_sdcc.1/by-name/boot:8393958:28495c2ab9b8a2210fc396d8af35c29bc885fce9:8398054:bb5e73e0be23e9709b0acfd83db5c62140" has unexpected contents
E: Error in @/cache/recovery/block.map
(Status 7)
Installation aborted
Now I looked up status 7 errors and how to fix, but none had pertained to my particular issue, so I figured I'd check before doing anything drastic. For some info, I have rooted, unlocked bootloader, flashed a custom recovery and rom, but when Marshmallow came out, I flashed stock image for 6.0 to my phone through nexus root toolkit, which removed custom recovery, flashed to stock, but kept bootloader unlocked. So now I'm on clean stock 6.0 and I received the OTA and I tried to install it and this is the message I get. Any ideas on how to get my phone to update? Oh, and BTW if it matters, I'm on T-Mobile. Thanks in advanced!
First of all, don't rely on toolkits, it's really easy to do those steps yourself using fastboot.
Also it says that your boot.img is not stock, or stock enough, so you should reflash everything again, including boot, if you are really after the OTA. But at this point why are you trying to use the OTA, when you could just update to 6.0.1 byt flashing the boot.img and system.img, and radio. You clear cache and dalvik. and when it finishes rebooting and optimizing applications you'll have your 6.0.1.
istperson said:
First of all, don't rely on toolkits, it's really easy to do those steps yourself using fastboot.
Also it says that your boot.img is not stock, or stock enough, so you should reflash everything again, including boot, if you are really after the OTA. But at this point why are you trying to use the OTA, when you could just update to 6.0.1 byt flashing the boot.img and system.img, and radio. You clear cache and dalvik. and when it finishes rebooting and optimizing applications you'll have your 6.0.1.
Click to expand...
Click to collapse
Hey, that would be great! The only problem is I'm not particularly skilled in that field lol. Does the boot.img, system.img and radio come from the stock factory image, or do I have to download those separately? And would I install those with a particular program? Thanks, sorry for being such a noob
It's in the factory package mmb29k. Download it, and extract it, you'll have the bootloader, the radio, and a zip file with all the rest. You don't need the bootloader, it hasn't changed since the marshamllow preview. Extract the files from the zip file, then flash radio, boot.img and system.img.
For flashing you need fastboot, but the toolkit already installed it, it just calls it when you push buttons.
As for the flashing, everything is explained in the pinned post.
I was trying to flash custom rom to my phone but keep on getting "error executing updater binary in zip" . Trying out the options I accidentaly wiped internal storage and with it the recovery. Now i am not having any OS in my phone
I have downloaded couple of rom from Cyanogen for MOTO X (ghost) but each of them give same error ,using twrp 2.8.7.0 as recovery (haven't tried by changing with other because its the only thing left there)
Also tried
flasing custom ROM
but here the problem is "downgraded security version update gpt_main version failed"
Was running on Android 5.1 before this all happened
PLEASE HELP DONT WANT T HARD BRICK MY PHONE
You have to flash stock rom using Rsd lite and u will be good to go
can't find a stock rom asia retail android 5.1
and can't flash 4.4 it shows downgraded security version update gpt_main version
Use the TWRP here (thanks to @rrvvrr) - http://forum.xda-developers.com/attachment.php?attachmentid=3171698&d=1424260997
Its 2.8.5.0. it resolves the script error on xt1052 which official verions have.
Here's the XT1052 IMAGE https://mega.nz/#!U9lRFBgD!POchMYI96ZTy16M_PGSZ4aIjo6ktpaHKaJAmp6XBUR4
while flashing the new recovery to my device using cmd is there any risk for hard brick(when I wont be able to open custom recover or bootloader)
Shivam248 said:
while flashing the new recovery to my device using cmd is there any risk for hard brick(when I wont be able to open custom recover or bootloader)
Click to expand...
Click to collapse
I recommend you flash the factory image through RSDLite once and then proceed to flash CM if you want
rsd dosen't recognize device
I just have the firmware of android 4.4 for my device but lastly it was running on 5.1 so i need that and i cant find that for my device
Can you please describe the step by step procedure to do
Thanks
athulele said:
Use the TWRP here (thanks to @rrvvrr) - http://forum.xda-developers.com/attachment.php?attachmentid=3171698&d=1424260997
Its 2.8.5.0. it resolves the script error on xt1052 which official verions have.
Here's the XT1052 IMAGE https://mega.nz/#!U9lRFBgD!POchMYI96ZTy16M_PGSZ4aIjo6ktpaHKaJAmp6XBUR4
Click to expand...
Click to collapse
My phone wiped everything and is bricked atm. I'm trying to flash the image you posted here but it fails every time at the partition and system stages. It won't work in RSDLite so I tried doing it in cmd but fails at those two points. Do you know why this might be?
Thanks