Database Info

[Q] Can't receive update to 8.4.4.11

I rooted my transformer using the pure root method in the development transformer forums for devices that already received 3.1. People have said that they receive their update and unroots their device, but I haven't even received the FOTA. I only rooted my device; without clockwork or a custom rom. I did delete some pre installed programs (bloatware) with titanium backup but I re installed them. Not sure if the damage has been done but I want someone to confirm if that can be the issue and how do I go about to properly reinstall the bloatware.

I know .11 will not install on a rooted device. I even unrooted several different ways installing the normal software from the asus site and never could get ota working... I am wondering if any others have got updates working after unrooting... (ended up exchanging at Best Buy for a new one....

Danny80y said:
I know .11 will not install on a rooted device. I even unrooted several different ways installing the normal software from the asus site and never could get ota working... I am wondering if any others have got updates working after unrooting... (ended up exchanging at Best Buy for a new one....
Click to expand...
Click to collapse
I am having the exact same problem and a lot of people will. Once you root and try to unroot it appears you cannot receive anymore OTA or make them work for that matter. I have found how to get the notification telling me that the .11 update is available for me. (Place the update file in sdcard/asus/update/) and then rename it US_epad-user-8.4.4.11.zip and rebooting. After this you can choose to make the update but it will not work. It will just go to the stock recovery with the android and the exclamation after a one second loading appearing that it will work. After you turn it off and back on it will tell you (System Update Failed Error (12) )Still trying to figure out why it is not accepting the update.

You can get the update in the "Just got an OTA update" thread.

Thank you for that valuable information. It worked like a charm. Now I just need the original update for the dock.
Sent from my Nexus S 4G using Tapatalk

...................

martijua said:
You can get the update in the "Just got an OTA update" thread.
Click to expand...
Click to collapse
I guess I'll have to manually install. Let's see how it turns out...

for just patiently wait for FOTA or rooted repack... The improvements are not HUGE.

TheIneffable said:
I guess I'll have to manually install. Let's see how it turns out...
Click to expand...
Click to collapse
Didn't even work. I guess my device is not recognizing the file or something. I guess I'll have to wait or probably get use to installing roms

TheIneffable said:
Didn't even work. I guess my device is not recognizing the file or something. I guess I'll have to wait or probably get use to installing roms
Click to expand...
Click to collapse
Did you tried the explanation give in the thread that the guy on top of my post suggested? It helped me out.
Sent from my Transformer TF101 using Tapatalk

Meh I am givin up for today. Flashed back to stock recovery, plopped the update package on a card in the format of EP101_SDUPDATE.zip, reboot to stock recovery, just kept getting the exlamation point. Can't flash the thing any other way either.
Guess I'll wait for a rooted 3.2 to come out.

You are not suppose to rename the file. Extract the contents of the ZIP file to the ROOT DIRECTORY of the MicroSD card.
Works everytime for me....while the renaming of the file never worked for me.

It's weird because, I downloaded the txt, and rename it, placed it on the root of the so card and the update passed flawlessly.
Sent from my Transformer TF101 using Tapatalk

Fixter said:
Did you tried the explanation give in the thread that the guy on top of my post suggested? It helped me out.
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
"Then press volume up when you see the text on the top left of the screen"
I did it just how the instructions stated but I never saw the text on the top left of my screen. It just boots up normally with stock boot animations. The update notification is not present either. I guess I'll try and see if not renaming it might help. Even though I don't think leaving the file extension to just "file" will help. I'll try...

Digiguest said:
You are not suppose to rename the file. Extract the contents of the ZIP file to the ROOT DIRECTORY of the MicroSD card.
Works everytime for me....while the renaming of the file never worked for me.
Click to expand...
Click to collapse
hmm...Probably because you extracted the .zip to the SD card. It just stated to move the .zip to the sd card. Maybe extracting might work.

None of the methods worked. Guess I'll be installing roms. I guess when I deleted some of the preinstalled apps, my device became disqualified for any sort of updates.

I don't understand most of you. You buy this stuff as early adopters, complain about the price, then ***** about how it "doesn't work", then hack/break it and then complain i doesn't update properly or whatever. Then come on here and piss all over the vendor.
Really?

superevilllama said:
Meh I am givin up for today. Flashed back to stock recovery, plopped the update package on a card in the format of EP101_SDUPDATE.zip, reboot to stock recovery, just kept getting the exlamation point. Can't flash the thing any other way either.
Click to expand...
Click to collapse
Read the first post of this thread to properly flash the update when renamed to ep101_sdupdate.zip:
http://forum.xda-developers.com/showthread.php?t=1171116

Carl LaFong said:
I don't understand most of you. You buy this stuff as early adopters, complain about the price, then ***** about how it "doesn't work", then hack/break it and then complain i doesn't update properly or whatever. Then come on here and piss all over the vendor.
Really?
Click to expand...
Click to collapse
haha. Who's *****ing? My transformer still works great. Just wanted to diagnose why I wasn't getting an update so I can be more informed about it and see if I should just stick to installing roms or unroot.

Right. That says exactly what I just said, and did. Anyway.. I eventually got it to work. I had to go compeletly back to stock as apparently deleting stuff from the stock rom altered it enough that the update didn't see it as the same rom.
Tried to root after and got froze up at the boot screen like everyone else. Been playing with this too long. Understanding that we risk messing up our devices by rooting and such.. other issues that are in complete control of Asus such as build quality... IE light bleed, bezel issues, freezing, touch screen not sensing touch are making me rethink this product. Sigh. Sucks too because the idea is awesome. Just wish the build quality was there.

Major problem - tf101 bricked

I rooted my tablet and it worked fine. I then proceded to modify my build.prop file. My friend sent me his to work from but i mistakenly copied it over directly. Now the tablet will not boot. How can i restore to factory or whatever i need to do?
(please spare me from the "you shouldn't have done that" speech, trust me i know lol)

need more info
what model number do you have, what can you get into, what cant you get into etc

lowgoz said:
need more info
what model number do you have, what can you get into, what cant you get into etc
Click to expand...
Click to collapse
sorry, late night, not really with it lol
its model tf101 US version and it has the latest ICS firmware, stock recovery. i can get it to load the recovery screen with the wipe data option. sorry for my poor terminology im new to the whole android rooting stuff.

You can download the latest firmware from Asus website.
Unzip it to get the zip file from inside and put it on your external sd card. Boot into recovery and let it flash the ROM again.
Plenty of thread to show step by step if needed.
You could also try to adb push the original file to your tf

baseballfanz said:
You can download the latest firmware from Asus website.
Unzip it to get the zip file from inside and put it on your external sd card. Boot into recovery and let it flash the ROM again.
Plenty of thread to show step by step if needed.
You could also try to adb push the original file to your tf
Click to expand...
Click to collapse
i've already tried this. it just gives me the dead android with a red exclamation point. also for some reason my windows pc says "the device cannot start" and im unable to use adb.

What is the serial number of your tf?
Hopefully it's one that's nvflash compatible

baseballfanz said:
What is the serial number of your tf?
Hopefully it's one that's nvflash compatible
Click to expand...
Click to collapse
dont think it is, starts with B90

i think the mods rudely removed my post in general forum where i was actually getting some help, but whatever. still need help here if anyone has any ideas.

I think you have several options-
1) use adb to fix your build.prop file. This can be done in the rom or recovery. There are adb guides coming out of the woodworks on here. If windows doesn't recognize your device, then get linux or a mac and kick windows to the curb. Nothing but grief.
2) install the correct build.prop via a flashable zip. You can extract the build.prop from the system dump I have in the dev section. Yeah, it's a slow download, but I'm working on something to move it to a faster server.
There's no easy fix... yet. adb will be the "easiest" fix.

gee one said:
I think you have several options-
1) use adb to fix your build.prop file. This can be done in the rom or recovery. There are adb guides coming out of the woodworks on here. If windows doesn't recognize your device, then get linux or a mac and kick windows to the curb. Nothing but grief.
2) install the correct build.prop via a flashable zip. You can extract the build.prop from the system dump I have in the dev section. Yeah, it's a slow download, but I'm working on something to move it to a faster server.
There's no easy fix... yet. adb will be the "easiest" fix.
Click to expand...
Click to collapse
ok well heres the issue. earlier way early this morning when this first started i was able to adb in, saw it was going in an infinite loop in logcat. now for some reason windows, and i've tried 3 installations of it, says the device cannot start. to me it sounds like something weird with the device. any ideas?

The exact same thing happened to me. I booted into recovery and restored from a nandroid backup. Maybe their is a way you can still install recovery and you someone can lend you their nandroid?

roflcopterofl said:
The exact same thing happened to me. I booted into recovery and restored from a nandroid backup. Maybe their is a way you can still install recovery and you someone can lend you their nandroid?
Click to expand...
Click to collapse
i think its too late for that now, adb wont work. im guessing now maybe the recovery isnt working because i had a newer version of the os than i can get a copy of right now. anyone have/know where i can get 9.2.1.17 fw?

If he is getting the dead android, it sounds like he has a stock recovery.
regarding adb, if windows won't start, then get a linux live cd. I think rebound128 has a minimal one in the dev section for nvflash rooting, but it will probably work. Or you can download a ubuntu live cd and boot from there.
one other option would be to wait until asus releases the 9.2.1.17 firmware on their site and download that. You should be able to flash it without the dead android. the 8.6.5.21 won't work because it won't let you install to a previous version. You can only install your current version or later. In your case, that would be 9.2.1.17.
At this point, I would say that windows is holding you back. I wish I had a $1 for every person that gets screwed over by windows- I would be as rich as Bill Gates used to be.

gee one said:
If he is getting the dead android, it sounds like he has a stock recovery.
regarding adb, if windows won't start, then get a linux live cd. I think rebound128 has a minimal one in the dev section for nvflash rooting, but it will probably work. Or you can download a ubuntu live cd and boot from there.
one other option would be to wait until asus releases the 9.2.1.17 firmware on their site and download that. You should be able to flash it without the dead android. the 8.6.5.21 won't work because it won't let you install to a previous version. You can only install your current version or later. In your case, that would be 9.2.1.17.
At this point, I would say that windows is holding you back. I wish I had a $1 for every person that gets screwed over by windows- I would be as rich as Bill Gates used to be.
Click to expand...
Click to collapse
im hearing that from everyone i talk to but in this case i dont think its windows thats causing the problem. like i said, i've tried THREE different installations of windows, and none of them pick up the tablet properly, they see "ASUS Android MTP Device" for some reason, and then it says that device isnt working properly. im probably just gonna wait till asus releases the new firmware. that will definately work....right?

joshcrumley100 said:
im hearing that from everyone i talk to but in this case i dont think its windows thats causing the problem. like i said, i've tried THREE different installations of windows, and none of them pick up the tablet properly, they see "ASUS Android MTP Device" for some reason, and then it says that device isnt working properly. im probably just gonna wait till asus releases the new firmware. that will definately work....right?
Click to expand...
Click to collapse
just tried it on linux, adb wont detect the device, so no luck there. im just hoping the .17 firmware will work on it, if not idk what to do.

In linux, with the TF plugged into the USB, what do you get when you type "lsusb" ??

gee one said:
In linux, with the TF plugged into the USB, what do you get when you type "lsusb" ??
Click to expand...
Click to collapse
it had Asus Transformer or something like that, it had it listed, but thats all. couldnt interact with the device.

Perhaps adb/debugging is not activated in the rom?
I think you'll have to wait until Asus releases a new update, although the last update checked the md5 sum of the build.prop file, so if you made any changes it won't flash.

gee one said:
Perhaps adb/debugging is not activated in the rom?
I think you'll have to wait until Asus releases a new update, although the last update checked the md5 sum of the build.prop file, so if you made any changes it won't flash.
Click to expand...
Click to collapse
Wait so you're saying even after i get the new firmware it still may not work? What a load of BS...

Originally Posted by gee one
Perhaps adb/debugging is not activated in the rom?
I think you'll have to wait until Asus releases a new update, although the last update checked the md5 sum of the build.prop file, so if you made any changes it won't flash.
Click to expand...
Click to collapse
Wait so you're saying even after i get the new firmware it still may not work? What a load of BS...
Click to expand...
Click to collapse
Sorry for the confusion- I think the full 9.2.1.17 rom that asus posts on their website will work, as long as it checks the rom version in recovery default.prop. It's not clear to me how it checks the "rule" that prevents downgrading. It's a maybe, but there's still a chance.
sent from my cyanogen(mod) vision

Unbricked TF101, but no Updates?

Hey,
My TF101 got bricked by a simple reboot - "encryption unsuccessful" splash screen.
I used the nvflash-package from the devel-section "[Tool] Nvflash unbricking released!" for getting back a fresh, clean install of 3.2.1, which seems to work well.
Sadly, no OTA-Update to ICS is found and no microSD-Update is recognized.
Wipe, another cold-boot tried.
Q:
nvflash repartition and format - thus there couldn't be hassle with my old "broken" Android, right?
Q2:Anyone has an idea why updates dont work? Within the thread mentioned above I found some posts about updates which where recognized.
Searched a lot but nothing specific to the nvflash image solution...
BR / Adarof

NvFlash the RougeXM touch recovery CWM and use that to flash a new ICS firmmware/ROM. That's probably the easiest route to take. You can flash total stock that overwrites the custom recovery if you'd like too. Should fix your ota problem too.

removed

Okay, I have flashed ww-9.2.1.11-CWM-full-rooted.zip.
Wipeing everything tried.
But still no updates...
I found http://forum.xda-developers.com/showthread.php?t=1655976, which are the same log-entries like I found
But no luck on googling further on

If you have anything but a stock recovery, you will not get an OTA. You need to here to get the stock recovery and flash it through CWR. Then when you boot to recovery, using the power+vol down wait to see the text at top right corner and then hit volume up, method, you'll see an android laying on his back with a ! above him. This is stock recovery. Should be able to push OTA through settings after this.

Wohu - Thanks, thats one of the very gernal infos I missed :-/
I tried your mentioned tutorial. The process itself seems to be fine.
But...still no updates (it takes ages for the 1st update-check and is very fast for the 2nd and ongoing checks)
I'm from Germany, thus I would expect to require a firmware and recoveryimage for DE but the tutorial just links a WW for firmware and just US for reecovery?
Well ... DE has gone to WW since .21, thus I tried ... but the process uses a repacked Android3, thus I should care about DE ?
Might this be the reason? Is there a repacked-CWM-enabled firmware-image with recovery for DE?
Thanks again so far!
BR / Adarof

adarof said:
Wohu - Thanks, thats one of the very gernal infos I missed :-/
I tried your mentioned tutorial. The process itself seems to be fine.
But...still no updates (it takes ages for the 1st update-check and is very fast for the 2nd and ongoing checks)
Click to expand...
Click to collapse
When the file goes to update, it will fail if there are any apps missing from /system/app that ASUS put in there. There is a checker that looks for these app. If you deleted any of these or any were deleted in the CWR version you flashed earlier, you'll have to replace them before the update will install.
adarof said:
I'm from Germany, thus I would expect to require a firmware and recoveryimage for DE but the tutorial just links a WW for firmware and just US for reecovery?
Click to expand...
Click to collapse
All you need from that link I posted above is the SURecovery image and nothing else. You can get the firmware.zips from Asus directly. The SURecovery is universal, meaning it will work no matter what region you are in. It is the ROM/Blobs that are region specific. Don't forget that if you download one from the Asus site, that you need to extract it first and then push the zip that was inside the original file you downloaded.
So it would look like this WW.zip->extract->firmware.zip<<<---This is your ROM
adarof said:
Well ... DE has gone to WW since .21, thus I tried ... but the process uses a repacked Android3, thus I should care about DE ?
Might this be the reason? Is there a repacked-CWM-enabled firmware-image with recovery for DE?
Click to expand...
Click to collapse
Not sure about these questions.

Woodrube said:
When the file goes to update, it will fail if there are any apps missing from /system/app that ASUS put in there. There is a checker that looks for these app. If you deleted any of these or any were deleted in the CWR version you flashed earlier, you'll have to replace them before the update will install.
Click to expand...
Click to collapse
Okay, I havent known this either...
Is there a list of asus-default installed apps? I havent found :/
Woodrube said:
All you need from that link I posted above is the SURecovery image and nothing else.
You can get the firmware.zips from Asus directly.
Click to expand...
Click to collapse
SURecoverty means the USRecovery.zip, right?
So, in summarize
1) Rogue XM Touch recovery via nvflash from http://forum.xda-developers.com/showthread.php?t=1446019
2) Use RogueXM to flash original asus-firmware (decompressed download archive)
3) Use RogueXM to flash USRecovery.zip from http://theunlockr.com/2011/11/28/how-to-unroot-and-remove-cwm-recovery-on-asus-transformer/
Am I right?
...on 2) I get
Code:
assert failed: write_raw_image("/tmp/blob","staging")
E: Error in /sdcard/WW_epad-user-9.2.1.24.zip
(Status 7)
Installation aborted.
...but I could install the repacked-8.2.3.13_WW+root-CWR-update(su_removed).zip.
I assume the RogueXM requires a blob-File within the zip, which is not provided by asus-original-downloads?
A bit confused ;-)
BR / Adarof

adarof said:
Okay, I havent known this either...
Is there a list of asus-default installed apps? I havent found :/
Click to expand...
Click to collapse
That is a tough one. i would suggest looking at the OP's for the custom ROMs and see if the have an Add-on pack that will put them in their custom ROMs. That way you'll be able to extract the apps from them and push to /system/app on your own (don't forget to set permissions also on the ones you push). If not, I will see if I can pull them from mine, zip them up and them send a link to you, but that won't be until I 1 get home and 2 get some time which unfortunately won't be tonight.
adarof said:
SURecoverty means the USRecovery.zip, right?
Click to expand...
Click to collapse
Yes sorry about that. I was typing too fast. :/
adarof said:
Am I right?
...on 2) I get
Code:
assert failed: write_raw_image("/tmp/blob","staging")
E: Error in /sdcard/WW_epad-user-9.2.1.24.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
This is the 3rd Status 7 I have seen today from someone. The other two were in my phone forums and it is bc of a mismatched CWR version. In my phone forum, they just needed to flash a different kernel. Not sure what is going on with it here, but see below...
adarof said:
...but I could install the repacked-8.2.3.13_WW+root-CWR-update(su_removed).zip.
Click to expand...
Click to collapse
If you can get this far, then NVflash this and get it to boot up completely. That way you shoudl have all the /system/apps anyways. You can root it (if you lose it somehow) with Razerclaw since it is HC.13 (if you accidentally update all the way to ICS .11 without rooting, you can use ViperMod or any of the other root tools out there) Remember that once you root it, you can use OTA Rootkeeper to preserve your Root status, accept the OTA and then restore Root (this is what I have done since HC). Then install this app and flash the USRecovery.zip and you should be good to go. Reboot to full boot up and then try to reboot into recovery using Key Combo. It should throw the Android on his back with ! above him.
I would then uninstall the Recovery Installer to make sure you don't accidentally hit it and you are back where you started. But you'll have the APK to reinstall whenever you want later on.
Sorry for the long post, just trying to cover everything bc I have log out for a bit and won't be on until later on. Maybe Thing O Doom will swing through, though.
Edit::: Check this out too.

Woodrube said:
That is a tough one. i would suggest looking at the OP's for the custom ROMs and see if the have an Add-on pack that will put them in their custom ROMs.
Click to expand...
Click to collapse
Well, Ok...since I "just" would like to have back a real stock system, with OTA - there should be another way ;-)
Woodrube said:
This is the 3rd Status 7 I have seen today from someone. The other two were in my phone forums and it is bc of a mismatched CWR version. In my phone forum, they just needed to flash a different kernel. Not sure what is going on with it here, but see below...
Click to expand...
Click to collapse
Okay! This explains why I cant find any 1000000 hits on google related to my prop, which seems to me rather "simple" in principle ;-)
Woodrube said:
If you can get this far, then NVflash this and get it to boot up completely. That way you shoudl have all the /system/apps anyways.
Click to expand...
Click to collapse
Agreed...apps should be there. But even the Asus storage app was missing? Thus no stock-apps included?
Its an old Andoroid 3.0.1 and it wouldn't find OTA updates - thats correct?
Woodrube said:
Then install this app and flash the USRecovery.zip and you should be good to go. Reboot to full boot up and then try to reboot into recovery using Key Combo. It should throw the Android on his back with ! above him.
Click to expand...
Click to collapse
Okay, while Power-VolDown -> VolUp (this gave me Rogue XM before but since I installed USRecovery it was overwritten, right?) -> a Droid on its back with a "!" comes up.
...and now?
The .24 update on SDCard is recognized but when I try to install the knocked-out droid with "!" comes on reboot again and next reboot yields to a popup "failed update, reverted to old system" or so.
Woodrube said:
Sorry for the long post, just trying to cover everything bc I have log out for a bit and won't be on until later on. Maybe Thing O Doom will swing through, though.
Click to expand...
Click to collapse
THANKS for your time so far and dont stress anything
I really appriciate it! Im feeling lost on android...even I work with Linux/Unices since a decade or so :-/
Woodrube said:
Edit::: Check this out too.
Click to expand...
Click to collapse
Thats a Win-solution :-/
Most propably I need a stock DE .21 or WW .24 , repacked for flashing with CWM ... right? But that doesnt exists?!?! Cant imagine...
BR - Adarof!

Im still on this problem and have no idea - searched a lot, but havent found any real howtos for DE-tf101 for unbricking.
So my main thoughts are about this Error7, which is really ...strange.
I could flash the repacked, which is available for .11. But I dont have a change to get anz further...
I SHOULD be able to flash a original asus stock Firmware with the Rogue XM Touch recovery, right?
Since Im not able to ... should I try an older version of Rogue XM?
BTW: Is the region info somewhat hard-wired thus it couldnt be changed?
BR - Adarof

There's a WW .24 available for tf101 and I'm making a 9.2.2.6 for the Tf101G,
so there is the latest FW available.

If you are flashing, then that means you have a custom recovery. That is why no OTA.
I'm mobile now but IIRC from before, you flash a working CWR version of the ROM. Thne boot up. Then flash the stock recovery. Then you should be able to OTA after that.
Just make sure whatever ROM you flash is full. If you can nvflash that would be better and then put stock recovery in after your first boot.

Thanks to both of you!
@Woodrube: Flashing means using RogueXM...
Summary:
1) Rogue could flash me either CWR/rooted images or the repacked one - both without OTA.
Just RogueXM is left as bootloader, which shouldnt prevent OTA?!
2) Rogue gives Error7 on flashing the asus-downloaded-onetime-depacked-firmwares, doesnt matter if the DE.21 or current WW.24. :-/
Trying to make the long story short:
For comming back to a "known" system I would like to really go back to a stock system.
I conclude that using nvflash would be the best for this, right?
But where do I get the img-Files for flashing using nvflash?
I just found one package which included a download.sh: It repartitioned, formated and installed a WW android3 (3.2.1) version and deleted the RogueXM. It mentioned its a stock firmware (thus should have all apps).
Sadly no updates afterwards...
I think it could be since its the WW version and I would need a WW .21/.24 (since 21/24 dont distinguish DE and WW anymore) or an older DE-version. But for nvflash I need the img files of these firmwares, which I dont find. ...
Maybe you could simply point me to such img files for nvflash, please?
BR / Adarof

Finally I managed to borrow a win pc and thus could give EasyTool of your posting #8 a try: http://forum.xda-developers.com/showthread.php?t=1688012
After some hassle with the driver I managed to flash asus stock download DE_epad-user-9.2.1.21, which is "DE_Special" for coming to WW of german tf101s. the tf was wiped and boots just fine - it states that it has
IML74L.WW_epad9.2.1.21-20120413 - as I think is fine.
Sadly no update again:
The OTA doesnt find any.
The microSD recognizes WW_epad-user-9.2.1.24.zip, but during rebooting I get the Droid with ! and after another reboot a popup with something like "update failed (12)" (in german Systemaktuallisierung fehlgeschlagen (12)). It mentiones that the new version in not compatible ...but ....the .24 is for the DE_special .21 the next ... ?!
I could flash the .24 using Easytool, but this would mean to loose always all data for an update ....
Installing rogue still gives error7 on flashing stock (once decompressed) .zip

I've been reading and Rouge gives errors with stock otas X.x
You can manually install the stock blobs with adb shell, but they will overwrite recovery and etc..
If you want total stock you need to NvFlash, and for whatever reason your tf does NOT like updates.
Rouge V1.3 will take otas, if you don't mind the downgrade.

Thanks for the hint - but I was to lazs to install the rogue 1.3.
I found a .zip, which I tried to install by Rogue 1.5 hoping for a downgrade overall, but during installation it stated "Returning to recovery" and still 1.5 was installed .
What I finally found is a ww-9.2.1.21-to-9.2.1.24-CWM-v1.0.zip image.
I installed this using rogue 1.5 and got a clean .24 installation.
So I'm using this installation hopeing either
1) OTA will work, if asus releases .24++ or
2) I find an ww-9.2.1.24-to-9.2.1.24++
Still I dont get why the EasyTool .21 installation yields to a non-OTA state ... but ...
So, THANKS all of you for your support and hints!
I'll come back here and report further on, if .24++ is out
BR / Adarof

bad luck
....meanwhile my tf101 has started to ignored the dock battery, while the keyboard still works. I tried cleaning ....no luck, the dock battery does not come up within the menues ...
Thus it was returned and I'm waiting for repairing or refunding ...
BR / Adarof

Something just not right in my attempt to flash roms.

About to tear my hair out at its roots trying to get this thing up to Jellybean. I bought it being told it was Jellybean capable but it had not been upgraded yet and all I had to do was go to the Asus site and get the files.
Well I go to the asus site and sure enough I download the file but thenit does not mention how to do the upgrade process. So I then go to - http://forums.androidcentral.com/an...-jelly-bean-asus-infinity-tf700t-minutes.html and this tells me to get the file needed to make it a specific file name and then do the reboot into the regular bootloader.
Well this worked like a hill of beans. I kept getting an error about the signature being invalid though I downloaded it off the ASUS site and I tried downloading the file three different ways (at work) on my phone and off my home Cablemodem) so if its a file problem its a file problem on the hosted site Asus is using.
I then used the unlocker and I unlocked my Asus it even shows it is unlocked every time it unboots so this part I know I did right.
I then ran DebugfsRoot_Generic_v2.3.zip from the link here - http://dottech.org/78441/how-to-root-asus-transformer-pad-infinity-tf700-debugfs-method-guide/ - and it said that it gave me root access on the OS installed. I however downloaded SU and RootChecker both which indicated I did not have root.
So then I decided if I was going to do this I would go full gusto. So I got a CWM GUI from http://forum.xda-developers.com/showthread.php?t=2094746 because I use CWM on my phones and figured if I stuck with the gui version of this I would be fairly competent on doing a rom replacement.
So then I downloaded a couple of roms from here - http://forum.xda-developers.com/showthread.php?t=1834521
as well as the SU that can be flashed. before boot up but I seem to still not to be able to get root (though the tool I used indicated I have it) on the current system.
The problem I have right now is rigt now anything I try and load from my sd card that is a zip shows -
E: Can't Open /sdcard/filename.zip
(bad)
Installation aborted.
For Filename.zip I have tried CWM-SuperSU-v0.99.zip from http://download.chainfire.eu/310/SuperSU/UPDATE-SuperSU-v1.04.zip as well as multiple ROM files from http://forum.xda-developers.com/showthread.php?t=1834521 as well as a couple from Asus
Things i know 1) I have correct USB from the Tablet to the PC this is evident because I was able to update the bootloader to the CWM GUI. 2) The MicroSD card is a 4 gb card and it works just fine. I have used it in my computer many times and I can open and copy and move files just fine on it any which way. 3) I am unsure as to why DebugfsRoot_Generic_v2.3.zip indicated it was all Rooted but then rootchecker is not showing it as rooted.
Is the fact I don't have Root the main reason for the files not being able to be opened? If so is there a better TF700T root program out there?

So for my clarification you want Jelly Bean rooted?
Is this correct?

Although it could be risky, you can actually toggle file system hashing verifications off in CWM. Make absolutely sure that the file downloaded correctly by verifying the MD5 yourself, other wise you could end up with a brick of the same value but even less practical use than the one you currently have.
Sent from a comfortable chair from the outer ring of Purgatory. The red guy asked me to say 'hi'.
---------- Post added at 12:50 PM ---------- Previous post was at 12:42 PM ----------
StumpedTechy said:
About to tear my hair out at its roots trying to get this thing up to Jellybean. I bought it being told it was Jellybean capable but it had not been upgraded yet and all I had to do was go to the Asus site and get the files.
Click to expand...
Click to collapse
To answer Thats_OK's question: I read this to mean that the 700 is still ICS, and he wants to get JB on there.
1) I have correct USB from the Tablet to the PC this is evident because I was able to update the bootloader to the CWM GUI.
Click to expand...
Click to collapse
Just to correct a minor error in terminology, just to get it straight: CWM is a recovery, and not a bootloader nor a "GUI" to the bootloader.
2) The MicroSD card is a 4 gb card and it works just fine. I have used it in my computer many times and I can open and copy and move files just fine on it any which way.
Click to expand...
Click to collapse
Not thT IT SEEMS TO BE THE ROOT Cuse here, but what filesystem is it formatted to?
3) I am unsure as to why DebugfsRoot_Generic_v2.3.zip indicated it was all Rooted but then rootchecker is not showing it as rooted.
Click to expand...
Click to collapse
I do not have a clue either -- the script should do everything for you and you should not have to undertake any action afterwards.
Is the fact I don't have Root the main reason for the files not being able to be opened?
Click to expand...
Click to collapse
Nope, an unlocked bootloader and a suitable recovery is all you need. Once those two are in place and working correctly, you should be able to flash anything. Rooting pertains to the access granted to the filesystem once you're 'inside', i.e. with the tablet running the ROM installed.
If so is there a better TF700T root program out there?
Click to expand...
Click to collapse
Nah, this works for pretty much anyone. I've had the error of "bad installation" a few times as well, and I toggled the hashing. Worked like a charm, although, as said, there is a minor risk involved if you do not keep your head cool and forget to verify manually. I haven't had this on the latest version of CWM, though.
Sent from a comfortable chair from the outer ring of Purgatory. The red guy asked me to say 'hi'.

Go to settings--> about tablet and provide the full build number for your device.

Thats OK said:
So for my clarification you want Jelly Bean rooted?
Is this correct?
Click to expand...
Click to collapse
I want Jellybean, roooted isn't so much a need but would be a plus.
Go to settings--> about tablet and provide the full build number for your device.
Click to expand...
Click to collapse
Build number is IML74K.US_epad-9.4.5.30-20120907
Not thT IT SEEMS TO BE THE ROOT Cuse here, but what filesystem is it formatted to?
Click to expand...
Click to collapse
The card is formatted to fat32
I've had the error of "bad installation" a few times as well, and I toggled the hashing.
Click to expand...
Click to collapse
I am not seeing anythign for hashing i am seeing signiture varification but with this enabled or disabled it is not changing the error I am getting.

If you just want JellyBean have you tried looking here? >>> http://forum.xda-developers.com/showpost.php?p=28374043&postcount=1

Thats OK said:
If you just want JellyBean have you tried looking here? >>> http://forum.xda-developers.com/showpost.php?p=28374043&postcount=1
Click to expand...
Click to collapse
I appreciate the link but did you read this part of my post?
Well I go to the asus site and sure enough I download the file but thenit does not mention how to do the upgrade process. So I then go to - http://forums.androidcentral.com/and...t-minutes.html and this tells me to get the file needed to make it a specific file name and then do the reboot into the regular bootloader.
Click to expand...
Click to collapse
I have already followed these instructions multiple times and each time it is giving me errors about the files being invalid or something of the sort.
I have tried about 4 different roms to load and each time I get bad file indicators even after comparing md5s and verifying the files are okay.
Is there any way to wipe this thing 100% and just load something on fresh?

StumpedTechy said:
I appreciate the link but did you read this part of my post?
I have already followed these instructions multiple times and each time it is giving me errors about the files being invalid or something of the sort.
I have tried about 4 different roms to load and each time I get bad file indicators even after comparing md5s and verifying the files are okay.
Is there any way to wipe this thing 100% and just load something on fresh?
Click to expand...
Click to collapse
Hmmm..Guess I'm not catching what you have done.
When you downloaded from the Asus website did you rename the file inside the zip to: EP201_768_SDUPDATE.zip then place this on your microSD?
Also I don't see any mention of ADB to push files to the tablet.
Sorry for my confusion.
Just not understanding where your at.
It is possible to wipe the internal SD card (eMMC) memory using TWRP...yet I'd wait until we get things sorted.

Let me go over what I did and what didn't work and let me go over what I finally did that did work now that I have mine all upgraded.
Didn't work -Scenario 1 -
Go into Settings->About Tablet-> System update this did absolutely nothing for getting me jellybean it just sat at a connecting screen that gave me nothing.
Didn't work -Scenario 2 -
Straight from the last link you provided -
1. Decompress downloaded .zip file (it will be another .zip)
2. Rename it to EP201_768_SDUPDATE.zip
3. Format FAT32 the MicroSD card that you will be using for the update process
4. Copy the file to (the root directory of) your MicroSD
5. Insert it into the tablet
6. Shutdown (power off) the tablet
7. Power it on by pressing and holding VOLUME DOWN and POWER buttons simultaneously
8. When you see white text in the top left corner of the screen, release the buttons ^^ and press VOLUME UP button until you see Android logo and process bar
9. Wait patiently for 10 minutes or so
(when I reached number 8 nothing happened automatically and I had to use the blue screened system recovery and when I pointed it to the SD file it told me it was a bad file.)
Didn't work -Scenario 3 -
Loaded
Transformer ADB Tool v6 and then loaded CWM GUI and then tried loading different rom from all over the place Asus main site, and all over the Index site here for different roms. http://forum.xda-developers.com/showthread.php?t=1834521
Finally however I finally made it work -
I am not sure why ALL the other ways did not work but on mine this is what I had to do.
1) From my first post I got the program from Asus that did the Unlocker I ran that from the Asus site.
2) From the first post I installed CWM GUI and I installed that.
3) From the index site I downloaded Stock Rooted Odex 10.4.4.23 to a USB stick - mainly because it says its rooted and I don't have to worry about rooting it AND I don't mind being .02 revisions behind.
4) I did an MD5 check vrs the download verified all was correct.
5) Tried to install from the MicroSD card and it failed yet again same errors as before.
6) On a whim I rebooted the TF700T and I copied the Stock Rooted Odex 10.4.4.23 to the device directly.
7) I booted to CWM GUI again and this time it installed when I selected to load from the internal SD.
8) I reloaded all my apps on the top.
9) I then loaded the apk of flash that "isn't supported" but works well enough on JB even on my phone.
So basically it would not install from my MicroSD though everything said it should but it would work fine from the internal memory.
This is with me using 2 different MicroSD cards and both are known working ones out of current phones I use all the time.
So I am now up to Jellybean and I am sporting all I needed to be upgraded for. Thanks for the attempts but it was just my constant tenacity that got me through this process.

Sounds like you have loaded my stock rooted rom. Which means you will still be on the old ice cream sandwich bootloader. Recommend you flash the JellyBean bootloaderfrom one of my threads in the ddevelopment section.
The reason your ota Asus updates failed is because you were already unlocked.

sbdags said:
The reason your ota Asus updates failed is because you were already unlocked.
Click to expand...
Click to collapse
Good point. Any idea why the other ROMs were failing as well?
@OP: now you have found a way that works, I suggest to try CROMI.

sbdags said:
Sounds like you have loaded my stock rooted rom. Which means you will still be on the old ice cream sandwich bootloader. Recommend you flash the JellyBean bootloaderfrom one of my threads in the ddevelopment section.
The reason your ota Asus updates failed is because you were already unlocked.
Click to expand...
Click to collapse
Ugh so I actually just made this worse? Basically since I did Stock Rooted Odex 10.4.4.23 over the version 9 ICS I am still running version 9ICSwith files over the top that are from 10.4.4.23 making it now some mixture of the two? So confused because I thought when I did a rom upgrade it wiped out the old and put in the new? it is showing the right version in Settings and it is acting right with what Jellybean should be doing so I am a lot confused right now.

StumpedTechy said:
Ugh so I actually just made this worse? Basically since I did Stock Rooted Odex 10.4.4.23 over the version 9 ICS I am still running version 9ICSwith files over the top that are from 10.4.4.23 making it now some mixture of the two? So confused because I thought when I did a rom upgrade it wiped out the old and put in the new? it is showing the right version in Settings and it is acting right with what Jellybean should be doing so I am a lot confused right now.
Click to expand...
Click to collapse
boot into recovery, when you see 4 icons, take a look at the second line (white text), it should say the version of your bootloader (1.00e is JB bootloader and 2.00e is ICS), then next to it is your JB or ICS version.
What sdbags said is when you flash a premade rom from XDA, it only included the ROM/kernel, but no bootloader. The only way is to flash the full firmware download from Asus site which included everything and bootloader is one of them.

buhohitr said:
boot into recovery, when you see 4 icons, take a look at the second line (white text), it should say the version of your bootloader (1.00e is JB bootloader and 2.00e is ICS), then next to it is your JB or ICS version.
What sdbags said is when you flash a premade rom from XDA, it only included the ROM/kernel, but no bootloader. The only way is to flash the full firmware download from Asus site which included everything and bootloader is one of them.
Click to expand...
Click to collapse
Ahhh gotcha. So I have really only done it halfway and have to get the bootloader flashed up as well. Will work on this next then. Right now I only have three options in my bootloader android, USB and the wipe data when all the others I read about indicate 4 icons should be there so I thought something was off there.

StumpedTechy said:
Ahhh gotcha. So I have really only done it halfway and have to get the bootloader flashed up as well. Will work on this next then. Right now I only have three options in my bootloader android, USB and the wipe data when all the others I read about indicate 4 icons should be there so I thought something was off there.
Click to expand...
Click to collapse
You could flash just JB bootloader with custom recovery from here: http://forum.xda-developers.com/showthread.php?t=2049274

StumpedTechy said:
Ahhh gotcha. So I have really only done it halfway and have to get the bootloader flashed up as well. Will work on this next then. Right now I only have three options in my bootloader android, USB and the wipe data when all the others I read about indicate 4 icons should be there so I thought something was off there.
Click to expand...
Click to collapse
I uploaded sbdags' version I used to DropBox for you: https://www.dropbox.com/s/js0m8nas00ts95h/tf700t-WW-JB-bootloader-only.zip
It's just a matter of flashing this (and update your recovery, if applicable), and then reflash any ROM you'd like.
https://www.dropbox.com/s/js0m8nas00ts95h/tf700t-WW-JB-bootloader-only.zip

Thanks guys I went ahead I went ahead and downloaded it from the link right on the website that sbdags was talking about just did a quick forum search and found the proper JB bootloader. So now I have a CWM GUI recover, JB bootloader and the sdbags stock rooted JB rom on it.
Now I know this is a loaded question and someone has already mentioned CleanROM Inheritance 3.2
But are there any clear cut "great" JB roms that run pretty much flawlessly on the TF700T that are prerooted? Just checking because as I mentioned I have tried quite a few roms on my Samsung S2 and used AOKP, SuperNexus, and am now on ShoStock3. Are the roms on the TF700Ts about the same in "feel" to their galaxy s counterparts? E.G. AOSP TF700T like a AOKP Galaxy S2? (assuming AOSP and AOKP are the same developer?
Thanks for everyone sticking with me through this. This has been such a learning curve over my phone which was simply install CWM (non gui) and download the rom and then flash. Didn't have to worry about unlocking anything, didn't have to worry about where I was installing the rom from and all that.

StumpedTechy said:
Thanks guys I went ahead I went ahead and downloaded it from the link right on the website that sbdags was talking about just did a quick forum search and found the proper JB bootloader. So now I have a CWM GUI recover, JB bootloader and the sdbags stock rooted JB rom on it.
Click to expand...
Click to collapse
Good job -- wherever you got it from, it served you well. I'll keep the JB bootloader on that DropBox link for a while so others can benefit from it too.
Now I know this is a loaded question and someone has already mentioned CleanROM Inheritance 3.2
Click to expand...
Click to collapse
Yup.
But are there any clear cut "great" JB roms that run pretty much flawlessly on the TF700T that are prerooted?
Click to expand...
Click to collapse
Pretty much all of them are preooted, but in my opinion, none of them is as smooth as CROMI. BBB7 has been quite a bufggy experience for most of the people that tried it (or so I gather from the thread), and although the CM team is making nice progress on their 10.x version, some minor niggles remain (and sometimes resurface, such as shortcut keys on the dock being broken every once in a while). Also, CROMI is developed actively in the meantime as well, and you can take the mods with it that disable those annoying notifications.
Just checking because as I mentioned I have tried quite a few roms on my Samsung S2 and used AOKP, SuperNexus, and am now on ShoStock3.
Click to expand...
Click to collapse
I agree that the SGS2 was a breeze to flash compared to the TF700 -- I was in the same boat as you. Flashed away without a care, then had to learn how to do it anew with the Infinity.
Are the roms on the TF700Ts about the same in "feel" to their galaxy s counterparts? E.G. AOSP TF700T like a AOKP Galaxy S2? (assuming AOSP and AOKP are the same developer?)
Click to expand...
Click to collapse
The differences are greater, because the TF700 has a lot of pixels to push and therefore its hardware is more hard-pressed than the SGS2's. The Exynos in the SGS2 is a VERY good chip, so it handles itself quite nicely in lots of scenarios. The Tegra3, I am pained to say, has impressed me less in everyday use than the numbers on paper did. With CROMI, it's pretty good, so I'm happy as it is now, but it should have been better out-of-the-box.
Thanks for everyone sticking with me through this. This has been such a learning curve over my phone which was simply install CWM (non gui) and download the rom and then flash. Didn't have to worry about unlocking anything, didn't have to worry about where I was installing the rom from and all that.
Click to expand...
Click to collapse
All I worried about was that darned yellow triangle. Thanks to Chainfire we could disable that too, so I was a happy camper.

[Q] Deleted my OS!!!!!!

So I sell my Infinity on ebay tonight. Went to wipe my data via TWRP and managed to delete my OS. The device shows the ASUS bootup screen but goes nowhere.
I'm a near illiterate in terms of understanding root level work on the tablet, and my other handicap is that I am a Mac user which means that I am not familiar with some of the "lingo" people use when describing connections to their Windows OS (things like ADB, bootloader, that sort of stuff).
Can someone help me with a step by step fix, using basic language?
i was hoping to ship tomorrow. OTOH, if I've bricked the thing, give me the bad news and I'll refund the money.

gmermel said:
So I sell my Infinity on ebay tonight. Went to wipe my data via TWRP and managed to delete my OS. The device shows the ASUS bootup screen but goes nowhere.
I'm a near illiterate in terms of understanding root level work on the tablet, and my other handicap is that I am a Mac user which means that I am not familiar with some of the "lingo" people use when describing connections to their Windows OS (things like ADB, bootloader, that sort of stuff).
Can someone help me with a step by step fix, using basic language?
i was hoping to ship tomorrow. OTOH, if I've bricked the thing, give me the bad news and I'll refund the money.
Click to expand...
Click to collapse
You should be alright... Can you try this for me? Holding the power button and volume down at the same time.. You should see your bootloader menu whih has 3 icons... Please let me know if you can get there..:fingers-crossed:

gmermel said:
So I sell my Infinity on ebay tonight. Went to wipe my data via TWRP and managed to delete my OS. The device shows the ASUS bootup screen but goes nowhere.
I'm a near illiterate in terms of understanding root level work on the tablet, and my other handicap is that I am a Mac user which means that I am not familiar with some of the "lingo" people use when describing connections to their Windows OS (things like ADB, bootloader, that sort of stuff).
Can someone help me with a step by step fix, using basic language?
i was hoping to ship tomorrow. OTOH, if I've bricked the thing, give me the bad news and I'll refund the money.
Click to expand...
Click to collapse
No - you're probably ok.
Just boot up with Power and Volume Down, hold both buttons until you feel the tablet vibrate twice. Let go when you see the tiny script and you'll see the bootloader menu with three icons and RCK flashing. Push Volume up and you should boot into TWRP.
From here you can just re-flash the rom you wiped or the stock rom (although flashing the stock firmware would wipe out TWRP). You need to have the zip of your chosen rom on your internal storage already (but maybe you wiped it???) or on your microSD.
Ask if I was not clear enough.
Edit: LMK beat me to it - again... LOL
Sorry mate, didn't see your post

berndblb said:
No - you're probably ok.
Just boot up with Power and Volume Down, hold both buttons until you feel the tablet vibrate twice. Let go when you see the tiny script and you'll see the bootloader menu with three icons and RCK flashing. Push Volume up and you should boot into TWRP.
From here you can just re-flash the rom you wiped or the stock rom (although flashing the stock firmware would wipe out TWRP). You need to have the zip of your chosen rom on your internal storage already (but maybe you wiped it???) or on your microSD.
Ask if I was not clear enough.
Edit: LMK beat me to it - again... LOL
Sorry mate, didn't see your post
Click to expand...
Click to collapse
Wow. 2 minutes and I'm getting help already.
I'm in TWRP. Where do I get the stock rom? I presume I'll download it my computer, but how do I tell the tablet to load it from there?

berndblb said:
No - you're probably ok.
Just boot up with Power and Volume Down, hold both buttons until you feel the tablet vibrate twice. Let go when you see the tiny script and you'll see the bootloader menu with three icons and RCK flashing. Push Volume up and you should boot into TWRP.
From here you can just re-flash the rom you wiped or the stock rom (although flashing the stock firmware would wipe out TWRP). You need to have the zip of your chosen rom on your internal storage already (but maybe you wiped it???) or on your microSD.
Ask if I was not clear enough.
Edit: LMK beat me to it - again... LOL
Sorry mate, didn't see your post
Click to expand...
Click to collapse
It is not a problem... I think that my device is running the ET so it is a little faster...:silly: Just kidding...
It would be better that you can help him/her.. I am a little busy testing new stuffs.. Thanks for the helps and talk more with you later...

LetMeKnow said:
It is not a problem... I think that my device is running the ET so it is a little faster...:silly: Just kidding...
It would be better that you can help him/her.. I am a little busy testing new stuffs.. Thanks for the helps and talk more with you later...
Click to expand...
Click to collapse
A LITTLE busy testing new stuff??? Haha! Are you doing anything but...?
---------- Post added at 10:48 PM ---------- Previous post was at 10:38 PM ----------
gmermel said:
Wow. 2 minutes and I'm getting help already.
I'm in TWRP. Where do I get the stock rom? I presume I'll download it my computer, but how do I tell the tablet to load it from there?
Click to expand...
Click to collapse
You don't. You have to copy the rom or firmware to your microSD.
Insert the card, boot into TWRP as described earlier.
Choose 'Install" and then navigate to your microSD and the zip you parked there.
Select it, swipe to flash it.
Now: I cringe, when someone on a perfectly fine and unlocked TF700 wants to flash back the Asus firmware. Ouch!
But I understand you only want to sell it and the buyer may not know how much better this tablet is on a custom ROM like CROMi-X. Sigh!
So, if you insist on flashing the latest firmware, go to the Asus support website, the download section, enter Transformer in the search box, select the TF700 and look for the 10.6.1.14.10 firmware. Make sure you select the one for your SKU, meaning US if you're on this continent (and I assume you are since you're awake at this time ), or WW or where ever you are.
Download the firmware and and on your computer, extract that zip file once - the result being another zip file.
It's that once extracted zip you want to copy to your SD, insert in your tab and flash in TWRP.
Ask if I left anything out.

Thanks. You're right, I'm in the US. But I am going to sleep. Will get on this in the AM.
You are correct to cringe. I rooted/C-romix'd a few months ago because I was frustrated by the constant lag on the tab. Figured if I bricked it, well, I wasn't happy with it anyway. I cringed when I went and did it because I knew I was taking a risk what with my capabilities. I've moved on to the Nexus 7 and just love it. Not just the performance. The small platform is just right....
Thanks for the rapid replies and the sophisticated yet understandable directions. Mostly, thanks for not calling me a knucklebrain even though I deserve it.

gmermel said:
Thanks. You're right, I'm in the US. But I am going to sleep. Will get on this in the AM.
You are correct to cringe. I rooted/C-romix'd a few months ago because I was frustrated by the constant lag on the tab. Figured if I bricked it, well, I wasn't happy with it anyway. I cringed when I went and did it because I knew I was taking a risk what with my capabilities. I've moved on to the Nexus 7 and just love it. Not just the performance. The small platform is just right....
Thanks for the rapid replies and the sophisticated yet understandable directions. Mostly, thanks for not calling me a knucklebrain even though I deserve it.
Click to expand...
Click to collapse
Not that long ago, I was exactly where you are now....:silly:

berndblb said:
Not that long ago, I was exactly where you are now....:silly:
Click to expand...
Click to collapse
Problem #1: When I opened the ROM.zip, I didn't get another zip, I got a folder with no zips in it (a blob.exe, several other .exe). When I moved that over to the SD and chose to install it TWRP returned a "failure" notification.
I'd like to get the stock ROM on for the buyer. What should I do
Problem #2: I still have CROM-X on the external card. It is installing, but which kernel should I use?
I'm going to use sbdags stock, and if you think that's a mistake I'll reflash.

gmermel said:
Problem #1: When I opened the ROM.zip, I didn't get another zip, I got a folder with no zips in it (a blob.exe, several other .exe). When I moved that over to the SD and chose to install it TWRP returned a "failure" notification.
I'd like to get the stock ROM on for the buyer. What should I do
Problem #2: I still have CROM-X on the external card. It is installing, but which kernel should I use?
I'm going to use sbdags stock, and if you think that's a mistake I'll reflash.
Click to expand...
Click to collapse
If you get the blob file you extracted once too often. The firmware is a zip inside a zip. You extract the downloaded file ONCE.
Stock kernel is fine.
Sent from my DROID4 using Tapatalk