Database Info

Neither Win7 nor Mint recognise TF101 by USB since updating to ICS

I know it's probably a PEBCAK issue, but since upgrading to ICS neither my Win boot nor my Mint one recognise the Transformer on USB... Neither does adb or fastboot for what is worth...
Anyone else experiencing the issue?

+1
But since i transfer my data via Dock/USB it's not a big issue atm.

jordivf said:
I know it's probably a PEBCAK issue, but since upgrading to ICS neither my Win boot nor my Mint one recognise the Transformer on USB... Neither does adb or fastboot for what is worth...
Anyone else experiencing the issue?
Click to expand...
Click to collapse
My B50 was recognized by Win7 after successfully installing the device driver. A TF101 Drive was created with SD and External Storage available. I have a stock ICS, no root and no custom roms.

Mine did to. Although I had to go into device manager and uninstall the replug mine in and they reinstalled themselves. All but one that I can remember off hand but I just double-clicked it and it installed the 2nd time.

I had same issue... if you used CWM flashable package, you need to reflash bootloader. I've found link in dev section. From then everything is just fine.
Sent from my ICS TF101 by XDA HD app

You flash in CWM bootloader > http://forum.xda-developers.com/attachment.php?attachmentid=919716&d=1330205295 and your problem is solved
md5: 830CC58626C9772087203820BF22B96D
source: http://forum.xda-developers.com/showpost.php?p=22964131&postcount=47
reupload: http://www.mediafire.com/?h4pgduf8zsgmh96
E: gnufabio (Revolver ROM) use this boot image in his ROM, I think you can use this package for your US version TF

jozka.1 said:
You flash in CWM bootloader > http://forum.xda-developers.com/attachment.php?attachmentid=919716&d=1330205295 and your problem is solved
md5: 830CC58626C9772087203820BF22B96D
source: http://forum.xda-developers.com/showpost.php?p=22964131&postcount=47
Click to expand...
Click to collapse
I tried this method but got an error "status 7 installation aborted". Any solutions would be appreciated.

michael_duvalle said:
I tried this method but got an error "status 7 installation aborted". Any solutions would be appreciated.
Click to expand...
Click to collapse
Make sure you flash the update appropriate for your region.
The version linked might be for US, and you might have WW firmware. Etc. The version of the update and your firmware must match.

josteink said:
Make sure you flash the update appropriate for your region.
The version linked might be for US, and you might have WW firmware. Etc. The version of the update and your firmware must match.
Click to expand...
Click to collapse
It was the WW version I tried but still no joy.

michael_duvalle said:
It was the WW version I tried but still no joy.
Click to expand...
Click to collapse
You are rooted and flashing this in CWM, right?
(Just cheking to be sure about the basics here)

josteink said:
You are rooted and flashing this in CWM, right?
(Just cheking to be sure about the basics here)
Click to expand...
Click to collapse
Yes. I was originally on Prime 2.1.0, flashed ww-9.2.1.11-CWM-full-rooted.zip, then flashed ww-8.6.5.21-9.2.1.11-CWM-full-rooted.zip on top. No wipes were performed and everything else except the battery usage is working properly.

jozka.1 said:
You flash in CWM bootloader > http://forum.xda-developers.com/attachment.php?attachmentid=919716&d=1330205295 and your problem is solved
md5: 830CC58626C9772087203820BF22B96D
source: http://forum.xda-developers.com/showpost.php?p=22964131&postcount=47
Click to expand...
Click to collapse
You, Sir, are a genius.
Yup! That sorted the issue.

michael_duvalle said:
Yes. I was originally on Prime 2.1.0,
Click to expand...
Click to collapse
No wipes were performed
Click to expand...
Click to collapse
Well, this might be the culprit.
I ALLWAYS wipe when flashing Major changes (Honeycomb -> ICS / different custom-ROMs) and usually don't have any Problems.

schauol1 said:
Well, this might be the culprit.
I ALLWAYS wipe when flashing Major changes (Honeycomb -> ICS / different custom-ROMs) and usually don't have any Problems.
Click to expand...
Click to collapse
What would be the best way to fix this then. Should I revert to Honeycomb stock and update the official way or shall I just wipe and reflash ww-8.6.5.21-9.2.1.11-CWM-full-rooted.zip. Also, If I did the second method, what exactly should I wipe?
Cheers

michael_duvalle said:
I tried this method but got an error "status 7 installation aborted". Any solutions would be appreciated.
Click to expand...
Click to collapse
Which version CWM do you use? I use Rogue XM Recovery v1.3.0 and no problem.
You can flash the boot image from Android (terminal or ADB) :
extract bloob file from .zip to sdcard and
Code:
su
dd if=/sdcard/blob of=/dev/block/mmcblk0p4
wait several minutes for better safety and reboot your TF.

jozka.1 said:
Which version CWM do you use? I use Rogue XM Recovery v1.3.0 and no problem.
You can flash the boot image from Android (terminal or ADB) :
extract bloob file from .zip to sdcard and
Code:
su
dd if=/sdcard/blob of=/dev/block/mmcblk0p4
wait several minutes for better safety and reboot your TF.
Click to expand...
Click to collapse
When you mean extract blob from the zip and place to the root of SD, do you mean the internal SD or the Removable SD?

It doesn´t matter, I prefer internal memory.
Code:
dd if=[B]/sdcard/blob[/B] of=/dev/block/mmcblk0p4
this is path to blob (internal SD)

jozka.1 said:
It doesn´t matter, I prefer internal memory.
Code:
dd if=[B]/sdcard/blob[/B] of=/dev/block/mmcblk0p4
this is path to blob (internal SD)
Click to expand...
Click to collapse
I tried it in terminal and it said that the file was written in several seconds. Several minutes later I went back to it, rebooted and still no joy.

And before boot system did you saw flash new blob file?

jozka.1 said:
And before boot system did you saw flash new blob file?
Click to expand...
Click to collapse
Yes. I left terminal open for about 10 minutes, then rebooted.

Lost Root AND TWRP???

Now this makes absolutely zero sense. Here are the steps I followed during the short time (~3 weeks) I have had my TF700:
- Root Tablet
- Use Root Apps
- Unlock Bootloader
- Use Root Apps
- Set Up NvFlash
- Use Root Apps
- Install TWRP Via GooManager
- Use Root Apps
- Update TWRP Via GooManager (using the exact same method used on first install, maybe I did this wrong?)
- Flash US Sku JB via TWRP
- Use Root Apps (actually one of the things I did was try to apply a max CPU value and use the performance Governor via ROM Toolbox Pro)
I included the times I know for a fact that I used applications that require root access. I flashed JB on Monday night, then let the ROM break in overnight and was used very lightly since. Then just a few minutes ago I go into Voodoo to backup and protect my root before applying the minor update and it's telling me that I don't have root access. Then I fire up SuperSU to confirm and low and behold it informs me that there is no root binary present and that it can not install it. So then I reboot to recovery to see if I can just flash su from TWRP and I get the stock Andy laying on his back with his case open and a red exclamation point screen.
How in the hell could this have happened? Can I just re-root using the new JB method then re-install TWRP?
This really concerns me, it baffles me how this could have happened... Any help is greatly appreciated.
Sent from my unlocked Transformer Infinity

Would I be able to just download the newest TWRP, rename it recovery.blob, boot into fastboot, then execute the following commands:
fastboot -i 0x0B05 flash recovery recovery.img
fastboot -i 0x0B05 reboot
then flash SuperSU from there? Sorry if this is an obvious question.
Sent from my unlocked Transformer Infinity

Issue resolved, but I would still like to find out exactly what happened so I can potentially avoid this situation in the future.
Sent from my unlocked Transformer Infinity

I_EAT_BABIES said:
- Flash US Sku JB via TWRP
Click to expand...
Click to collapse
The stock firmware contains the stock recovery, so installing it overwrites your custom one.

_that said:
The stock firmware contains the stock recovery, so installing it overwrites your custom one.
Click to expand...
Click to collapse
^^this

_that said:
The stock firmware contains the stock recovery, so installing it overwrites your custom one.
Click to expand...
Click to collapse
Ah that makes sense. I'm glad it was supposed to happen; what had me worried was the possibility that something odd happened. Thanks!
Sent from my unlocked Transformer Infinity

[Q] Rooted Stock ICS to JB or CM - A Little help Please

Hey everyone. Just wanted to say that I have used these forms a lot in the past with rooting my Droids and phones however I now have the Infinity and I need some advice on how to do the following... I know enough to be Dangerous when dealing with flashing etc on Android so I like to run things by people and get suggestions... So
Currently:
ROOT Original Stock Rom 4.0.3
Kernel - 2.6.39.4
Build - IML74K.US_epad-9.4.5.26-20120720
- Notes: When I first got this when released I used the only rooting option I could find which was some sort of auto command line script.
- I then Installed TWRP via GooManager
- I then UnLocked the Device with the Asus tool they released.
I did that months ago and haven't messed with it since... I have used it more and more lately and its slow in terms or response etc. I see that JB is now out for it. I started to look into CM I believe its called cyanogenmod 10 (it is really that good?) is out. I also see Stock Rooted ROMs.
Here is what I want to do.
1) I have looked and believe that I am able to apply the NVFlash patch so I cant brick my device. What does this actually do and will it mess with my abilities to use Recovery Mangers / Flash Roms / Kernels etc? ... Also if I update the build to a higher number will it take this away?
2) At the time TWRP was the ONLY option for me. How can I remove TWRP and get ClockWork on this? *note I dont care about anything on the device currently.
3) Is installing CM as easy as put the Zip on the SD card and then boot into CWM and install? -- Where can I get the OFFICIAL CM10 download for the infinity?
4) Kernel related - I know that stock kernels dont have the CPU control ability / and also some extras needed for wi-fi tether to fully function does CM come with its own kernel? or Do I have to get it Separately.
5) Basically There are to many guides and posts about what to do its confusing at this point.
I want to Wipe it / Get CWM on there instead of TWRP and Install CM. And if it is safe install the NVFlash.
I will await your guidance. Just past links to what guides to do in order.
Thanks!

bigstack said:
1) I have looked and believe that I am able to apply the NVFlash patch so I cant brick my device. What does this actually do and will it mess with my abilities to use Recovery Mangers / Flash Roms / Kernels etc? ... Also if I update the build to a higher number will it take this away?
Click to expand...
Click to collapse
As long as you don't upgrade your bootloader past 9.4.5.26, you can obtain the required files from your tablet using the procedure described at http://androidroot.mobi/t3_nvflash/ . What it does is described in the dev thread about nvflash - it does not mess with any abilities to flash stuff the normal way.
After you have created your files and stored in a safe place, you can always use them with nvflash, even if you upgraded your bootloader or even if you erased it. It's a nice low-level way to access the internal storage without requiring any installed bootloader, OS or recovery. Don't ever lose your blobs, they are the only way to enable nvflash.
bigstack said:
2) At the time TWRP was the ONLY option for me. How can I remove TWRP and get ClockWork on this? *note I dont care about anything on the device currently.
Click to expand...
Click to collapse
Easiest way: fastboot flash recovery cwm.blob

_that said:
As long as you don't upgrade your bootloader past 9.4.5.26, you can obtain the required files from your tablet using the procedure described at . What it does is described in the dev thread about nvflash - it does not mess with any abilities to flash stuff the normal way.
After you have created your files and stored in a safe place, you can always use them with nvflash, even if you upgraded your bootloader or even if you erased it. It's a nice low-level way to access the internal storage without requiring any installed bootloader, OS or recovery. Don't ever lose your blobs, they are the only way to enable nvflash.
Easiest way: fastboot flash recovery cwm.blob
Click to expand...
Click to collapse
1) So Once I follow that Guide I can update my Bootloader to anything even the newest .30 + and It will still be there and allow be to fall back if necessary.... Im on the last parts of the guide nvflash --resume --rawdeviceread 0 2944 bricksafe.img but do I run that in the FastBoot (hold down volume or) the APX (hold up) It didnt work with up trying down now..... Also is there a guide on how to actually Restore to a non bricked device using this?
2) fastboot flash recovery cwm.blob
--figured this out read next post!
*Of course im guessing that once this NVflash is installed its there no matter what I flash or return to stock ?

1) OK I managed to get NVflash installed and ran the last couple commands... Need to find the files to save off
2) I also managed to run the fastboot flash recovery recovery.img to get CMW touch installed and that works..
3) Right now I have the 4.0.3 Stock Still... with the NVflash installed... The Kernel is: 2.6.39.4 and the Build is: 9.4.5.26-....
If I Download a Jellybean ROM or CM10 (isn't this based of jellybean) and Install it I can assume that I can wipe out all my data (which i want)... As for the Kernel / Bootloader .. What if it gets updated to .30 or above? Or That wont matter now that NVflash is installed... I guess basally is NVflash a 1 off... meaning that as long as u can get it installed it will ALWAYS be there even after the updates above to when you could NOT install it?

bigstack said:
When I run the Line for the NVflash i get
C:\adt-bundle-windows\sdk\platform-tools>nvflash --resume --rawdeviceread 0 2944
bricksafe.img
Nvflash started
[resume mode] (it just sits here forever and i kill it)
^C
Click to expand...
Click to collapse
You must run it in APX mode, and you need to run wheelie with your blob before that line.

_that said:
You must run it in APX mode, and you need to run wheelie with your blob before that line.
Click to expand...
Click to collapse
I literally just updated the post above this.. If you could read that and Let me know If what I have done is correct.

bigstack said:
I literally just updated the post above this.. If you could read that and Let me know If what I have done is correct.
Click to expand...
Click to collapse
First save your files. Make backup copies. Post a list of the files that you saved if you are unsure - after you update, it's too late to get more.
Re-read this thread, the guide and the nvflash thread again, they should answer all your questions about nvflash.
To install a custom ROM that is based on JB (which is pretty much all of them), you need to install the Asus JB firmware first to get the latest bootloader. This will overwrite your custom recovery, but you already know how to restore it. Then you can flash whatever ROM you want.

Ok Files that I saved off are screen shot on the attachment... EDIT apparently im not allow to attach files... soo listed
* Also Added note. The driver pack that I downloaded from there site listed the device as a Samsung device in Device manager. However I was still able to enter APX mode and install NVFlash... Not sure if this is a good thing though.
View attachment 1571433
blob.bin
blob.log
bootloader.ebt
bricksafe.img
create.bct
factort-config.img
recovery.bct
unlock-token.img
I have read multiple NVFlash threads and I found * If you intend to use NvFlash please STAY AWAY from the 9.4.5.30 UPDATE ... Is this only to be able to install it?
If I need to update to the newest Firmware on Asus site wont this be above .30? Also What one on Asus site should I take. I see a ASUS Transformer Pad TF700T Firmware: V10.4.4.23 Only for US SKU (Android 4.1.1) I am in US so I figure that is the right one? Unless someone has a newer one. But will this wipe out NVFlash?
Am I able to update to a JB based rom without losing my NVFlash?

bigstack said:
The driver pack that I downloaded from there site listed the device as a Samsung device in Device manager. However I was still able to enter APX mode and install NVFlash... Not sure if this is a good thing though.
Click to expand...
Click to collapse
Strange, but if it worked, it's good
Just for additional verification, post the content of blob.log, and the file sizes of these 3 files:
bigstack said:
blob.bin
bricksafe.img
unlock-token.img
Click to expand...
Click to collapse
bigstack said:
I have read multiple NVFlash threads and I found * If you intend to use NvFlash please STAY AWAY from the 9.4.5.30 UPDATE ... Is this only to be able to install it?
Click to expand...
Click to collapse
I already wrote:
"After you have created your files and stored in a safe place, you can always use them with nvflash, even if you upgraded your bootloader..."
You also didn't "install" nvflash, you just created files so that you can *use* it when you need it. You will be able to use nvflash as long as you have these files, and as long APX mode works - since this is a very low-level mode, you cannot break it unless you have a hardware defect.
bigstack said:
If I need to update to the newest Firmware on Asus site wont this be above .30? Also What one on Asus site should I take. I see a ASUS Transformer Pad TF700T Firmware: V10.4.4.23 Only for US SKU (Android 4.1.1) I am in US so I figure that is the right one? Unless someone has a newer one.
Click to expand...
Click to collapse
10.4.4.23 is obviously newer than 9.4.5.30, and it's the latest one.
Based on your original version
Build - IML74K.US_epad-9.4.5.26-20120720
Click to expand...
Click to collapse
the US firmware is the right one for you.

_that said:
Strange, but if it worked, it's good
Just for additional verification, post the content of blob.log, and the file sizes of these 3 files:
Click to expand...
Click to collapse
blob.log content:
Generating encrypted EBT file 'bootloader.ebt'...done.
Generating encrypted recovery BCT file 'recovery.bct'...done.
Generating encrypted create BCT file 'create.bct'...done.
Generating blob file 'blob.bin'...done.
Adding create BCT to blob file [wheelie]...done.
Adding recovery BCT to blob file [wheelie]...done.
Adding bootloader to blob file [wheelie]...done.
Adding odmdata to blob file [wheelie]...done.
Adding chip id to blob file [wheelie]...done.
file sizes:
blob.bin - 1.87 MB (1,964,842 bytes)
blob.log ~ 1K
bootloader.ebt - 1.79 MB (1,887,968 bytes)
bricksafe.img - 11.5 MB (12,058,624 bytes)
create.bct - 5.98 KB (6,128 bytes)
factory-config.img - 5.00 MB (5,242,880 bytes)
recovery.bct - 5.98 KB (6,128 bytes)
unlock-token.img - 8.00 MB (8,388,608 bytes)
_that said:
I already wrote:
"After you have created your files and stored in a safe place, you can always use them with nvflash, even if you upgraded your bootloader..."
You also didn't "install" nvflash, you just created files so that you can *use* it when you need it. You will be able to use nvflash as long as you have these files, and as long APX mode works - since this is a very low-level mode, you cannot break it unless you have a hardware defect.
10.4.4.23 is obviously newer than 9.4.5.30, and it's the latest one.
Based on your original version the US firmware is the right one for you.
Click to expand...
Click to collapse
Ok I take this as Its ALWAYS there even if I update to later versions.
Next step if to get that downloaded and installed. ( I assume put onto SD then run the update in CWM ?)
*ALSO can a mod take my account out of this limited mode. I cant post links, or images etc. Thanks

bigstack said:
blob.log content
...
file sizes
...
Click to expand...
Click to collapse
Looks fine. Make safe backups of these files, then you should be able to recover from any software-induced brick in the future.
Ah, btw - you should also make a backup of partition 18, just in case. It contains the GPT and it's 524288 bytes. However that one should be identical on all devices (with the same storage size at least), so in an emergency case you could also use a backup from someone else - in contrast to bricksafe, factory-config and unlock-token which are specific to your device.
bigstack said:
Next step if to get that downloaded and installed. ( I assume put onto SD then run the update in CWM ?)
Click to expand...
Click to collapse
Right.

_that said:
Ah, btw - you should also make a backup of partition 18, just in case. It contains the GPT and it's 524288 bytes.....
.
Click to expand...
Click to collapse
How would I go about doing this? what command do I run and from where?
Also was I correct about being able to Update to any build / firmware no matter what version as I always have the NVflash there because I did it before I was on .30
ISSUE
I downloaded and installed the Firmware update.. Installed it Via CWM it went well device was usable. But now I lost root and When I try to Boot to the recovery manager I it trys but then Fails and I get a Droid guy with a Red Triangle.
FIXED: Flashed CWM and then Installed the 3.1.3 Superuser you can download via CWM when normally booted.

bigstack said:
How would I go about doing this? what command do I run and from where?
Click to expand...
Click to collapse
Same environment as in the official guide (tablet in APX mode, etc.). From your PC, enter these commands:
wheelie --blob blob.bin
nvflash --resume --read 18 gpt.img
bigstack said:
Also was I correct about being able to Update to any build / firmware no matter what version as I always have the NVflash there because I did it before I was on .30
ISSUE
I downloaded and installed the Firmware update.. Installed it Via CWM it went well device was usable. But now I lost root and When I try to Boot to the recovery manager I it trys but then Fails and I get a Droid guy with a Red Triangle.
FIXED: Flashed CWM and then Installed the 3.1.3 Superuser you can download via CWM when normally booted.
Click to expand...
Click to collapse
You need to read more carefully. The first question has already been answered in this thread multiple times. Also the issue with the lost recovery should not have surprised you, because I told you about it before.

Help w/ Bricked tf700t

When I got my tf700t a few months ago it was on 4.04. I unlocked the bootloader using the asus tool, rooted it(can't rememberr what tool I used it was awhile ago) then installed the trwp recovery. When the jellybean update came out I downloaded it from the asus site, unzipped it, dropped it on my sdcard, updated. A couple weeks ago the os started getting buggy so I booted with the vol down and power button and selected wipe, it crashed, and wouldn't do anything but boot into recovery from there.
So my transformer infinity has been bricked for a couple weeks now. Every time I power on my tablet it goes right into twrp recovery. As far as I can tell the recovery can't access anything but the ram disc so I'm unable to flash anything. I also can't get into fastboot mode to flash anything from there. I never backed anything up w/ NVFlash either. I've tried everything I could find on these forums as well as a few other forums and I'm getting nowhere.
Here are a couple threads that relate to this problem:
http://forum.xda-developers.com/showthread.php?t=1917304&page=7
http://forum.xda-developers.com/showthread.php?p=35370971#post35370971
I would really appreciate any help that anyone could offer.
Thanks.

Anyone......
Sent from my SCH-I535 using xda premium

xda uni
http://forum.xda-developers.com/showthread.php?t=2059993
Brian2177 said:
Anyone......
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I just saw this ... maybe they can help?

Help......
Sent from my SCH-I535 using Xparent Blue Tapatalk 2

Brian2177 said:
Help......
Sent from my SCH-I535 using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
You are on JB and what version of twrp did you used when you bricked your device?

Twrp 2.2.1
Sent from my SCH-I535 using Xparent Blue Tapatalk 2

Brian2177 said:
Help......
Click to expand...
Click to collapse
Sorry, I can't help you - I can just summarize what we found out so far:
- JB bootloader
- TWRP 2.2
- no nvflash backups
- "wipe data" caused forced booting into recovery, no way to access fastboot
- TWRP has no access to internal eMMC (mmc0: error -110 whilst initialising MMC card)
- therefore no partitions appear in /dev/block and nothing can be flashed via recovery
- adb shell works, but it can only access the ramdisk
Someone in a CM thread said the incompatibility between JB bootloader and pre-JB kernels is related to TF (Trusted Foundations) - some security system to improve DRM, which was enabled with the JB update on the TF700. But I don't know if it TF has anything to do with the inability to access to the eMMC card in the recovery.
What we need to do: gain access to the eMMC.
What we have: a root shell.
A root shell can load kernel modules (if it has not been disabled in TWRP's kernel config), so it might be possible to load a kernel module that initializes the eMMC card.
The main question is: *Why* can't the kernel initialize the eMMC card?

Brian2177 said:
Twrp 2.2.1
Sent from my SCH-I535 using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
This's why you bricked your device, you have a twrp for ICS and you used it on JB bootloader. We need to figure out how to flash the new JB twrp on your device and hopefully we can recover, but the chance is slim.

_that said:
Sorry, I can't help you - I can just summarize what we found out so far:
- JB bootloader
- TWRP 2.2
- no nvflash backups
- "wipe data" caused forced booting into recovery, no way to access fastboot
- TWRP has no access to internal eMMC (mmc0: error -110 whilst initialising MMC card)
- therefore no partitions appear in /dev/block and nothing can be flashed via recovery
- adb shell works, but it can only access the ramdisk
Someone in a CM thread said the incompatibility between JB bootloader and pre-JB kernels is related to TF (Trusted Foundations) - some security system to improve DRM, which was enabled with the JB update on the TF700. But I don't know if it TF has anything to do with the inability to access to the eMMC card in the recovery.
What we need to do: gain access to the eMMC.
What we have: a root shell.
A root shell can load kernel modules (if it has not been disabled in TWRP's kernel config), so it might be possible to load a kernel module that initializes the eMMC card.
The main question is: *Why* can't the kernel initialize the eMMC card?
Click to expand...
Click to collapse
Yeah I'm getting really frustrated. No matter what I try I can't get anything besides the tmpfs to mount.

This type of problem can only be fixed via fastboot or nvflash. If you can't get to fastboot and you don't have nvflash then you will have to send it to Asus for repair. There's no other way. I have run across 2 or 3 others like this and there is no other solution. Sorry.

Dees_Troy said:
This type of problem can only be fixed via fastboot or nvflash. If youccan't get to fastboot and youddon't have nvflash then you will have to send it to Asus for repair. There's no other way. I have run across 2 or 3 others like this and there is no other solution. Sorry.
Click to expand...
Click to collapse
I'll contact asus tomorrow. Thanks for the reply.

Fresh eyes
Dees_Troy said:
This type of problem can only be fixed via fastboot or nvflash. If you can't get to fastboot and you don't have nvflash then you will have to send it to Asus for repair. There's no other way. I have run across 2 or 3 others like this and there is no other solution. Sorry.
Click to expand...
Click to collapse
I want to confirm something with someone who knows twrp inside and out, I got this tablet from Brian so you know his story about how it got this way but I want to make sure it isn't recoverable. its running twrp 2.2.1 and i can mount the micro sd card, but i get a code 7 error when trying to flash roms downloaded from asus website and someone told me that means that i need to update to the latest twrp or get cwm... my question is can twrp be updated from the twrp interface since thats all I can access right now?
P.S. I am a newb so to speak I've only ever used cwm in my early android days as it was the easiest to use and I have forgotten everything about unlocking, rooting, and flashing but don't be afraid to get technical because google is my best friend. I know you guys are humble but I wanna offer a lil something to anyone with strong responses that can help me get this fixed, asus wanted to replace his mobo for over $200 sad story cause Brians a really nice guy, guess they didn't think so, anyways thanks in advance.

[Q] KitKat Failed Unknown Error

I'm trying to upgrade my SCH-i535 to KitKat but every time I try,
I get an Unknown Error occurred when I try to install it. I've unrooted and even factory reset.
Last night I updated from ML1 to NC1. Now I'm tring to update to 4.4.2. I have no problem downloading it OTA.
Kies freezes when I tell it what device I have. (Thought about doing it manually.)
Has anyone had a similar problem with the new update? Any way to fix this and install KitKat?

Jackelope said:
I'm trying to upgrade my SCH-i535 to KitKat but every time I try,
I get an Unknown Error occurred when I try to install it. I've unrooted and even factory reset.
Last night I updated from ML1 to NC1. Now I'm tring to update to 4.4.2. I have no problem downloading it OTA.
Kies freezes when I tell it what device I have. (Thought about doing it manually.)
Has anyone had a similar problem with the new update? Any way to fix this and install KitKat?
Click to expand...
Click to collapse
Have you just tried downloading it in about phone then software upgrade and over WiFi? Sorry I can't be of complete help as I'm on an unlocked bootloader
Sent from my SCH-I535 using Xparent ICS Tapatalk 2

ShapesBlue said:
Have you just tried downloading it in about phone then software upgrade and over WiFi? Sorry I can't be of complete help as I'm on an unlocked bootloader
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
Yeah that's how I've been trying to update it. I'm wondering if it could be because I froze some apps with Titanium backup.
I unfroze everything and unrooted and even factory reset.
Here is a snippet of a log I got from the update process:
Code:
Verifying update package...
I:comment is 3317 bytes; signature 1778 bytes from end
signed len : 419569452
sha1 : 419569472
6166a2c2 e7e3004f 59c5b22a 3f0c3478 da627d54
61 66 a2 c2 e7 e3 00 4f 59 c5 b2 2a 3f 0c 34 78 da 62 7d 54
2e 52 53 41 50 4b 05 06 00 00 00 00 c8 06 c8 06 e8 31 02 00
30 ed ff 18 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c8 10 f9 60
I:whole-file signature verified against key 0
I:verify_file returned 0
Installing update...
Register_libbootloader_updater Qcom msm8960
Register_libbootloader_updater Qcom msm8960
open failed '/sys/fs/scfs/system_type' - No such file or directory
Verifying current system...
file "/system/bin/app_process" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
failed to stat "/data/.saved.file": No such file or directory
failed to load data file
script aborted: "/system/bin/app_process" has unexpected contents.
"/system/bin/app_process" has unexpected contents.
E :Error in /cache/fota/update.zip
(Status 7)
E:Error in /cache/fota/update.zip
(Status 7)
FOTA_update_success_log_result()
Update Fail. File is written. status = 7
Installation aborted.

I hear people saying you have to be 100% stock to update. I was wondering if maybe I still had
some files left over from SafeRoot\GeoHots Root, or Safestrap that is causing the error.
I just tried to install from update.zip manually using recovery mode and got the following:
error in sideload package.zip
I'll let you know what I find.
EDIT:
Tried downloading the update.zip from someone else but same error. I'm going to try and flash stock via
odin and then try updating.

Jackelope said:
I hear people saying you have to be 100% stock to update. I was wondering if maybe I still had
some files left over from SafeRoot\GeoHots Root, or Safestrap that is causing the error.
I just tried to install from update.zip manually using recovery mode and got the following:
error in sideload package.zip
I'll let you know what I find.
EDIT:
Tried downloading the update.zip from someone else but same error. I'm going to try and flash stock via
odin and then try updating.
Click to expand...
Click to collapse
Did you mess around with the .prop file??
For me I think it's going to be quicker if you do the following (instead of trying to find the root cause of the update failure)
1) Make a Tibu backup of all the USER apps (about 10-15min)
2) Odin back stock ML1 (10-15min)
3) Let the OTA update to 4.4 kitkat (20 min)
4) Use Tibu to restore all your apps (use batch mode - select all apps then hit the check mark).(10-15 min)
The whole process probable about 45min-1hrs).
This way you kill 2 birds with 1 stone - fresh clean install and you're now on 4.4.

buhohitr said:
Did you mess around with the .prop file??
Click to expand...
Click to collapse
Me personally no. But I don't know if Xposed, TowelRoot or others did.

buhohitr said:
Did you mess around with the .prop file??
For me I think it's going to be quicker if you do the following (instead of trying to find the root cause of the update failure)
1) Make a Tibu backup of all the USER apps (about 10-15min)
2) Odin back stock ML1 (10-15min)
3) Let the OTA update to 4.4 kitkat (20 min)
4) Use Tibu to restore all your apps (use batch mode - select all apps then hit the check mark).(10-15 min)
The whole process probable about 45min-1hrs).
This way you kill 2 birds with 1 stone - fresh clean install and you're now on 4.4.
Click to expand...
Click to collapse
Yeah I'm planning on it. I just had to wait for ML1 to download. Thanks everyone for your help.

Jackelope said:
I'm trying to upgrade my SCH-i535 to KitKat but every time I try,
I get an Unknown Error occurred when I try to install it. I've unrooted and even factory reset.
Last night I updated from ML1 to NC1. Now I'm tring to update to 4.4.2. I have no problem downloading it OTA.
Kies freezes when I tell it what device I have. (Thought about doing it manually.)
Has anyone had a similar problem with the new update? Any way to fix this and install KitKat?
Click to expand...
Click to collapse
I had similar issues and then I odin'd back to stock and then took the update....it worked good
Sent from my SCH-I535 using Tapatalk

My Galaxy S3 will not connect to my computer, or any computer (I tried 6) on different 4 different OS's (including Linux), with different cables, on every USB port, so clearly something is wrong. It used to, now it doesn't.
That said, I was 4.3 rooted, and I cleared everything up (I think) and factory reset and got the NC1 update to run. After that was KitKat but it fails with an error. Poor robot just falls over and an red exclamation triangle comes out of his chest.
My question:
Can I take an image from sammobile.com/firmwares/3/? download=31550 and install it via the built in recovery mode apply update from cache/sd card? I can at least run Towelroot to root without pc, so that's handy if I'm stuck on 4.3. It isn't so bad.
Thanks!

BobSmith8 said:
Can I take an image from sammobile.com/firmwares/3/? download=31550 and install it via the built in recovery mode apply update from cache/sd card? I can at least run Towelroot to root without pc, so that's handy if I'm stuck on 4.3. It isn't so bad.
Click to expand...
Click to collapse
I looked at the update.zip from the OTA update (before it failed) and it is a directory structure and commands. The images one would (if I could) restore via ODIN are a different format with boot/recovery images. So, to answer my own question..
No, you can not flash to recovery and install a disk image in lieu of ODIN/etc.

@BobSmith8 You can use Mobile Odin from the play store to flash an Odin file without a a computer (unlocked bootloader required)
Edit: just realized you r on 4.3 with a locked bootloader
Sent from my SCH-I535 using Tapatalk

Sandman-007 said:
@BobSmith8 You can use Mobile Odin from the play store to flash an Odin file without a a computer (unlocked bootloader required)
Edit: just realized you r on 4.3 with a locked bootloader
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
You do know the version from the play store isn't free correct? Chainfire actually has a mobile odin available for download directly here from xda
Sent from my SCH-I535 using Xparent ICS Tapatalk 2