Related
hi everyone,
i have no idea why, but ever since last week i can't seem to see any internal\external storage in recovery (while in android it's fine). needless to say i can't flash new roms, backup\restore etc.
can any one help me?
i'm using CWM 5.8.3.1 (without team rogues, i want to flash that one, but i'm not sure whether or not i can use fastboot to flash ontop of an existing recovery... if so, could you please post the instructions to this?)
the 20120419 snapshot of cm9 wingray.
thanks for your help
xdave72 said:
hi everyone,
i have no idea why, but ever since last week i can't seem to see any internal\external storage in recovery (while in android it's fine). needless to say i can't flash new roms, backup\restore etc.
can any one help me?
i'm using CWM 5.8.3.1 (without team rogues, i want to flash that one, but i'm not sure whether or not i can use fastboot to flash ontop of an existing recovery... if so, could you please post the instructions to this?)
the 20120419 snapshot of cm9 wingray.
thanks for your help
Click to expand...
Click to collapse
Well, try to flash another recovery image. If you are running eos team build, you can flash their recovery and it reads internal and external sd card.
Let me know if you need the link...
wesamothman said:
Well, try to flash another recovery image. If you are running eos team build, you can flash their recovery and it reads internal and external sd card.
Let me know if you need the link...
Click to expand...
Click to collapse
i'm not sure... i'm running CM9 (so team rogue?) and my recovery isn't branded (it's original, no teams there...).
so you're saying it's ok to reflash ontop of the existing one with other recoveries?
please send me the links
thank you so much
xdave72 said:
i'm not sure... i'm running CM9 (so team rogue?) and my recovery isn't branded (it's original, no teams there...).
so you're saying it's ok to reflash ontop of the existing one with other recoveries?
please send me the links
thank you so much
Click to expand...
Click to collapse
Yup, it is ok to flash another recovery.
This is the link: http://forum.xda-developers.com/showthread.php?t=1604014
Also, I would suggest you to go to another ROM, which has been found to be the best as of now. Thanks to Team EOS for this ROM.
What is your xoom model? 3G or WIFI?
wesamothman said:
Yup, it is ok to flash another recovery.
This is the link: http://forum.xda-developers.com/showthread.php?t=1604014
Also, I would suggest you to go to another ROM, which has been found to be the best as of now. Thanks to Team EOS for this ROM.
What is your xoom model? 3G or WIFI?
Click to expand...
Click to collapse
i have the wifi version
one more thing - i have to boot the xoom into a certain mode right? and then do the flashing...
how do i get to that mode?
EDIT: sorry for that, i could find the answer easily online. thanks so much, everything is now working perfectly
xdave72 said:
i have the wifi version
one more thing - i have to boot the xoom into a certain mode right? and then do the flashing...
how do i get to that mode?
Click to expand...
Click to collapse
Hold on please. I am writing the procedure for you (how to flash the new recovery and to flash the latest ROM of Team OS for xoom wifi. You choose whatever suites you by then
---------- Post added at 10:21 AM ---------- Previous post was at 09:34 AM ----------
xdave72 said:
i have the wifi version
one more thing - i have to boot the xoom into a certain mode right? and then do the flashing...
how do i get to that mode?
EDIT: sorry for that, i could find the answer easily online. thanks so much, everything is now working perfectly
Click to expand...
Click to collapse
Yes, Let me clarify should you need to:
Definitely root your xoom and upgrade to custom ROM of ICS from Nightlites EOS team. Rooting and upgrading to this custom ROM, wingray for your device MZ604 is pretty fast and easy. will help you if you need to.
• Your custom ROM will be: Eos-wingray-102.zip. This is the latest ROM released on May 3rd. Very stable and everything works with it. No issues found.
http://goo.im/devs/teameos/roms/nightlies/wingray/
• Your GOOGLE APPs (GAPPs) would be: gapps-ics-20120429-signed.zip
http://goo.im/gapps
Full thread in details is here: http://forum.xda-developers.com/showthread.php?t=1400958
To summarize:
First, download the above ROM and GAPPs and put them onto your xoom internal and external SD card.
To download:
• Get the Motorola USB drivers: http://developer.motorola.com/docstools/USB_Drivers/
• Get the Android SDK: http://developer.android.com/sdk/index.html
• Recovery Image: http://goo.im/devs/teameos/recoveries/wingray/eos-recovery-r6.img
• GAPPS: http://goo.im/gapps, your GAPPs would be: gapps-ics-20120429-signed.zip
• ROM: Your custom ROM will be: Eos-wingray-102.zip. This is the latest ROM released on May 3rd. Very stable and everything works with it.
http://goo.im/devs/teameos/roms/nightlies/wingray/
Steps:
1. Power off your XOOM device.
2. Press and hold the volume down button while pressing the power button at the same time. Note: Even if your xoom starts again, just keep the button pressed until you see "Starting fastboot protocol" on the screen.
3. Connect Xoom to your computer via USB.
4. Open a ‘Command Prompt’ or ‘Terminal’ window on your computer in your sdk/tools folder.
5. If your device is not already unlocked, type:
i. “adb reboot bootloader”
ii. “fastboot oem unlock”
iii. “fastboot reboot”
6. If your device is already unlocked, and to flash another recovery, type:
i. “adb reboot bootloader”
ii. “fastboot flash recovery eos-recovery-r6.img”
iii. “fastboot reboot”
Now, you have your device unlocked and recovery installed.
Reboot your xoom, you will still have your old ROM.
To flash the other ROM downloaded above,
1. Boot into recovery by:
i. As soon as you hit the reboot command, you should see a Motorola logo appear. Wait 3 seconds and tap the Volume down button and the words Android Recovery should appear on the screen. When you see that, tap the Volume up button and you’ll boot into recovery.
2. From within Recovery, perform wipe data, wipe cache, and go to advanced, wipe dalvik cache and battery stats. Don't worry, if the ROM and GAPPs are deleted, which should not be the case, you will have them on your external sd card
3. In recovery, navigate to install zip from sdcard > choose zip from sd card and select the EOS ROM you copied to the root of the SD card. Once the files are flashed, DO NOT reboot afterwards. Hold on.
4. Again, from Recovery, choose install zip from sdcard > choose zip from sd card and select the GAPPs you copied to the root of the SD card.
Then hit reboot system now. It will take 2 - 3 minutes for the first reboot. Setup your google account. and you are good to go.
Later reboots will be much faster (around 40 - 50 seconds).
Advice: purchase Startup Manager from the market. Remove unwanted user programs from the startup. That will boost the boot time of your xoom. and don't remove superuser or superSU.
To have better battery life, from the market buy JuiceDefender ultimate. configure it as aggressive. don't worry, it is ok. This will give you around 2 hours of extra battery life than the promised 10 hours. Keep that in the startup.
You may need after that to install terminal emulator from the market if not already installed by the ROM to check if you have root permissions. Just type "su -"
you will be prompted with superuser check. Click allow. and then type "id"
You will see your id is root.
Should you require further details or assistance, please let me know. And enjoy the best rom customized ever for your device
Best Thanks to TEAM EOS for the great ROMs they provide.
After you are done with all that, let me know and will explain to you how to work with the pre-installed gooManager in the new ROM. It will make your life much easier to upgrade to future releases of your ROM.
NOTE: don't forget to hit the thanks button if you feel kind to
Regads,
you've done more then enough thanks so much again!
done with the stuff you posted (although i already had a root so just re-flashed the recovery)
i don't use gapps (i have problems with google stuff) so i use F-droid and aptoid. if you have any others, i'll thank you even more
I would love to help you with that but honestly I don't know know any other alternative to gapps besides that the latest gapps pack is fully issue-free
Sent from my MZ601 using Tapatalk 2
Hi all.
I have an Spanish wifi-only Xoom (MZ604) and I'm tired of waiting for motorola's updates (still in Honeycomb 3.2!!!).
I want to test either EOS3 (Android 4.1.1) or EOS2 (Android 4.0.4) custom roms. I've read almost all tutoriales but I still have some doubts about the procedures... could anybody check this message and warn me if I'm going to do something wrong?
DOUBT 1.- Key shortcuts in Xoom
Can anybody tell me the existing key combinations in Xoom? I only know about POWER+VOL_UP key to enter bootloader mode.
DOUBT 2.- How to install CWM.
If I understand it correctly, both EOS2 and EOS3 should be installed from CWM recovery...
Is the following procedure OK?
- Some tutorials say that you have to be root first to install CWM ... is it really needed? Can't be done directly with ADB?
- Install Android SDK in the PC.
- Download eos-recovery-r6.img or eos-recovery-r6-softkeys.img
- Connect XOOM to PC with the original USB cable.
- Reboot XOOM in bootloader mode (Power + VolUp)
- Exec adb and then:
fastboot oem unlock <---- is this a requirement?
fastboot flash recovery eos-recovery-r6.img
fastboot reboot
DOUBT 3.- How to install or upgrade EOS 2 or 3 ROM?
Is the following procedure OK?
- Download ROM and gapps zip files.
- Start XOOM in recovery mode (CWM) -> How to do this?
- Do a nandroid backup.
- Wipe everything (data, cache, dalvik, etc)
- Install ROM zip.
- Install gapps zip.
- No need to do anything to root it, the rom is already rooted <-- is that right?
- Reboot
Is everything OK? Did I miss anything? Do I need to root my 3.2 install before any other step? Do I have to do the "oen unlock"?
Thanks.
All you need to do is unlock your boot loader and get into flashing eos3. Will give you details how to soon
Sent from my MZ601 using Tapatalk 2
wesamothman said:
All you need to do is unlock your boot loader and get into flashing eos3. Will give you details how to soon
Click to expand...
Click to collapse
Thanks for answering. If I'm understanding you correctly, you say that I don't need CWM and I can just flash the EOS ROM directly to my xoom without "applying" it as a zip in CWM...
I would really like to install CWM, I appreciate a lot the possibility to do "nandroid" backups to be able to go back before installing kernels, updates or so ...
NoP_Compiler said:
Thanks for answering. If I'm understanding you correctly, you say that I don't need CWM and I can just flash the EOS ROM directly to my xoom without "applying" it as a zip in CWM...
I would really like to install CWM, I appreciate a lot the possibility to do "nandroid" backups to be able to go back before installing kernels, updates or so ...
Click to expand...
Click to collapse
Since you are going to install EOS Jellybean, I don't advise you with CWM. A different recovery made by EOS team is better through which you can do nandroid backup and other stuff...
Here is what you need to do step by step...
Note: please read this procedure carefully more than once until you are fully aware of it. If you have any doubts or concerns, just ask to avoid confusion before you apply. This should be followed step by step.
To summarize:
First, download the above ROM and GAPPs and put them onto your xoom internal and external SD card. Put them under /mnt/sdcard for internal sd or somewhere accessible, and under the root of your external sd card.
To download:
• Get the Motorola USB drivers to your laptop: http://developer.motorola.com/docstools/USB_Drivers/
• Get the Android SDK to your laptop: http://developer.android.com/sdk/index.html
• Recovery Image: http://goo.im/devs/teameos/recoveries/wingray/eos-recovery-r6.img
• GAPPS: http://goo.im/devs/teameos/roms/eos3/gapps/gapps-jb-20120726-eos-signed.zip
• ROM: http://goo.im/devs/teameos/roms/eos3/nightlies/wingray/ ; get the latest one...
Steps:
1. Power off your XOOM device.
2. Press and hold the volume down button while pressing the power button at the same time. Note: Even if your xoom starts again, just keep the button pressed until you see "Starting fastboot protocol" on the screen.
3. Connect Xoom to your computer via USB.
4. Open a ‘Command Prompt’ or ‘Terminal’ window on your computer in your sdk/tools folder. This is the sdk you downloaded above.
5. unlock your xoom and flash the recovery image. The recovery image should be in your current working directory where you have command line navigated to: Type:
adb reboot bootloader
fastboot oem unlock
fastboot flash recovery eos-recovery-r6.img
fastboot reboot
adb reboot recovery
Now, you have your device unlocked and recovery installed.
Reboot your xoom by selecting the option "reboot system now" from recovery. you can navigate up and down using the volume buttons. Once an option is highlighted, press the power button to select, you will still have your old ROM.
To flash the other ROM downloaded above,
1. Boot into recovery by:
i. As soon as you hit the reboot command above, you should see a Motorola logo appear. Wait 3 seconds and tap the Volume down button and the words Android Recovery should appear on the screen. When you see that, tap the Volume up button and you’ll boot into recovery.
2. From within Recovery, perform wipe data, wipe cache, and go to advanced, wipe dalvik cache and battery stats. Don't worry, if the ROM and GAPPs are deleted, which should not be the case, you will have them on your external sd card
Note: wipe data will delete your stuff on the xoom. It would be great if you backup your files that you need to your external sd card before you start any of this procedure.
3. In recovery, navigate to install zip from sdcard > choose zip from sd card and select the EOS ROM you copied to the root of the SD card. Once the files are flashed, DO NOT reboot afterwards. Hold on.
4. Again, from Recovery, choose install zip from sdcard > choose zip from sd card and select the GAPPs you copied to the root of the SD card.
Then hit reboot system now. It will take 2 - 3 minutes for the first reboot. Setup your google account. and you are good to go.
Later reboots will be much faster (around 30 - 45 seconds). The more apps you install, the slower it boots...
That is pretty much it. Enjoy, I hope this helps you
Of course it helps! In fact, a lot.
When I was talking about CRW I really meant EOS recovery (which is based in CRW itself IIRC).
The only that I can't understand is why some tutorials ask me to root the tablet before doing all this process...
Anyway, I think I'm finally going with EOS3 + EOS recovery if nobody here advices me to flash EOS 2 instead...
Sent from my Samsung Galaxy S2 using Tapatalk Pro.
So, before flashing:
- Do you think EOS3 (JB in Xoom) is mature enough to use it, or I should go with EOS2 final (ICS)?
- Do you know of anything not working in a wifi xoom with EOS3 rel.127?
- I've downloaded eos6-recovery.img ... do you think I should flash the "soft-keys" or the rogue-recovery instead?
- I don't have Microsoft Windows in my laptop: I work under Linux, so I haven't downloaded Motorola's USB drivers... I imagine that they are not needed under Linux, and It will work just with SDK's "adb" and "fastboot", right?
- Can the device be bricked with this procedure, or there is always a "Power+VolKey" way to flash a stock image? (like galaxys2 that its almost unbrickable).
PS: Thanks for informing me in the other thread that the EOS rom comes already rooted
I will be away for couple of hours, will answer your questions all as soon as I get back...
Sent from my MZ601 using Tapatalk 2
NoP_Compiler said:
So, before flashing:
- Do you think EOS3 (JB in Xoom) is mature enough to use it, or I should go with EOS2 final (ICS)?
- Do you know of anything not working in a wifi xoom with EOS3 rel.127?
- I've downloaded eos6-recovery.img ... do you think I should flash the "soft-keys" or the rogue-recovery instead?
- I don't have Microsoft Windows in my laptop: I work under Linux, so I haven't downloaded Motorola's USB drivers... I imagine that they are not needed under Linux, and It will work just with SDK's "adb" and "fastboot", right?
- Can the device be bricked with this procedure, or there is always a "Power+VolKey" way to flash a stock image? (like galaxys2 that its almost unbrickable).
PS: Thanks for informing me in the other thread that the EOS rom comes already rooted
Click to expand...
Click to collapse
Alright, eos jelly bean is fully stable, ,such faster and smoother than ICS. You want feel the difference until you try it... however, eos ICS is stable too and has more features and addons by eos because it has been there under dev for longer time, jellybean is new, one month old only... I recommend you to go for jellybean, and try and see for yourself. At anytime you can flash ICS since your Xoom booloader is already unlooked and recovery installed, you can do that by just wiping data and flash ICS zip. That is as simple as that...
For Motorola drivers on Linux, I think it is not needed, adb is built in with Linux, but I am not sure as I haven't tried that yet.
For eos recovery, don't use the soft key version, use the normal one...
with this recovery, you will be safe, because at all times, your external SD is accessible in emergencies...
Hope that helps...
Sent from my MZ601 using Tapatalk 2
You have it down perfectly. Just to recap.
1. Set up android sdk. Download recovery image and store in sdk folder. Download rom/gapps and store on tablet.
2. Boot into fastboot (power + volume up).
3. fastboot oem unlock (required). This will wipe all data.
4. fastboot flash recovery recovery.img (whatever recovery you decide to go with, I recommend eos soft key).
5. boot into recovery, make nandroid backup, flash rom of your choice + gapps if necessary.
People tie rooting to flashing custom roms because many people have become so reliant on apps like rom manager that flash the recovery for you, an app that requires root access. I never rooted my galaxy nexus or xoom. I simply flashed recoveries in fastboot and proceeded to flash roms in recovery.
It actually bothers me how some have become so reliant on root access to flash roms. It has gotten to a point where many people genuinely don't know the difference and that, to me, says they don't really understand what it is they're doing, which will lead to issues should they ever need to troubleshoot.
You seem to have it down well though. Good luck.
Thanks a lot to both.
I'm still waiting for JDK to download for Android SDK to work (I'm on hollydays in a small house in the middle of the forest and Im connecting with GPRS via tethering...).
I'll inform about the results...
Sent from my Samsung Galaxy S2 using Tapatalk Pro.
Good luck...
Sent from my MZ601 using Tapatalk 2
Ok. EOS6-RECOVERY installed correctly. There are a couple of mistakes and some missing info in the "tutorial", so I'm going to change it to help future users:
I finally did it under Windows because almost all tutorials in Internet explain all the possible problems that you can find in Windows, and it's a "too risky" task for me to "experiment" by myself.
PART 1 .- HOW TO INSTALL EOS6 RECOVERY:
Originally quoted from wesamothman:
First, download the above ROM and GAPPs and put them onto your xoom external SD card. Put them in a folder called /sources/ of your external sd card.
- Get the Motorola USB drivers to your laptop: http://developer.motorola.com/docstools/USB_Drivers/
- Get the Android SDK to your laptop: http://developer.android.com/sdk/index.html
- GAPPS: http://goo.im/devs/teameos/roms/eos3/gapps/gapps-jb-20120726-eos-signed.zip
- ROM: http://goo.im/devs/teameos/roms/eos3/nightlies/wingray/ ; get the latest one...
And the most important:
- Recovery Image: http://goo.im/devs/teameos/recoveries/wingray/eos-recovery-r6.img
Check that the md5sum of this file is correct and matches with the one provided in the download page. This is the most important file because it will allow to install the CWM recovery system and it's CRITICAL that the file is not corrupted.
Steps:
a.- Install in your PC the lastest JavaSE JDK from Oracle's website.
b.- Install in yout PC Android SDK, open Windows' cmd, enter the android-sdk folder and run:
Code:
tools\android.bat update sdk
Now select "Android SDK Tools", "Android SDK platform-tools", and Extras/"Google USB Driver". Click on "Install packages".
c.- Enable USB debugging in the XOOM (in settings, development).
d.- Install the Motorola USB drivers for your laptop (32 or 64 bits, check it in the Windows system properties).
e.- Plug the Xoom to your laptop.
f.- Execute cmd and enter the android-sdk/platform-tools folder.
Run "adb devices", if you get an empty "List of devices attached", then you must enter the control-panel -> devices and "Fix problem with device" over the MZ60x device. After a While, Windows will fix it and "adb devices" will show a message like:
Code:
List of devices attached
037887sda897xz device
(the digits string will vary according to your device)
NO NEED TO DO THIS:
NO -> 1. Power off your XOOM device.
NO -> 2. Press and hold the volume down button while pressing the power button at the same time. Note: Even if your xoom starts again, just keep the button pressed until you see "Starting fastboot protocol" on the screen.
Because the first command show after this lines: (adb reboot bootloader) won't work while in fastboot. Only "fastboot" commands work in fastboot mode. If you try that command in fastboot mode, it will say "Error: device not found".
So just, with your xoom working under the Android OS, do:
Code:
adb reboot bootloader
With the above, you'll enter fastboot mode without needing to press any key in the startup.
Now your Xoom will show the Motorola logo and the words "Fastboot protocol...". If you need to stop now for any reason, you can abandon this mode safely and reboot the tablet with "Power+VolUP+VolDown" for a few seconds.
But let's continue.... If you now do:
Code:
fastboot devices
You should get a string like
Code:
List of devices attached
037887sda897xz fastboot
If you don't see that string (and you see and error about device not found), you have to "fix/repair" the usb drivers again in the Windows ControlPanel / Devices. Now you'll see a "FASTBOOT" device instead of the MZ60x you repaired before (that's why we have to repair/fix again the device, because WIndows see it as a different device while in fastboot mode).
After repairing it, unplug and plug the USB cable (still in fastboot mode) and repeat the command:
Code:
fastboot devices
Now it will work and you'll see the device recognized by "fastboot"
Issue the following command to unlock the Xoom (you'll void the warranty):
Code:
fastboot oem unlock
Follow the Xoom's onscreen instructions to unlock the bootloader. You have to use VolDown to move through options and VolUP to accept an option.
The xoom will reboot and your old android OS will show, but now with a factory reset. Select language, time, etc and enable again USB debugging and execute in the PC:
Code:
adb reboot bootloader
(to start again the tablet in fastboot mode)
Now copy the file eos-recovery-r6.img to the android-sdk/platform-tools/ folder and execute:
Code:
fastboot flash recovery eos-recovery-r6.img
You will see something like:
Code:
C:\Users\sromero\Desktop\android-sdk-windows\platform-tools>
fastboot flash recovery eos-recovery-r6.img
sending 'recovery' (4114 KB)...
OKAY [ 0.499s]
writing 'recovery'...
OKAY [ 1.014s]
finished. total time: 1.529s
Check in the xoom's screen that the file was correctly written and execute:
Code:
fastboot reboot
You xoom will start again in Android OS mode. Execute:
Code:
adb reboot recovery
And you'll start the nice EOS Recovery (based on Clockworld Mod) recovery system.
You can also do it manually by powering on the Xoom and when the motorola logo appears, wait 3 seconds and press VolUp.
Now, you have your device unlocked and recovery installed. Now, you are SAFE because you can do nandroid backups and restores and can put any ROM in your system and go back with a backup or flash another different rom.
PART 2 .- HOW TO USE CWM / EOS RECOVERY
Code:
Up -> VolumeUp button
Down -> VolumeDown button
Select -> POWER button
PART 3 .- HOW TO INSTALL EOS3 ROM:
Under recovery mode (abd reboot recovery), do:
- Backup/restore -> backup to external SD.
- Wipe data/factory reset
- Wipe cache
- Advanced -> Wipe Dalvik Cache
- Advanced -> Wipe Battery Stats
- Install ZIP from SDCARD -> /sources/ -> the eos3 rom .zip file.
- Install ZIP from SDCARD -> /sources/ -> the gapps .zip file.
- Reboot
- Enjoy your new rom!
Very well detailed... great...thx.
Sent from my MZ601 using Tapatalk 2
wesamothman said:
Very well detailed... great...thx.
Click to expand...
Click to collapse
No... thank you for the initial info
After restarting, I have a notification about a ROM update (128). The ROM-management app allows me to download it or apply a incremental update...
Do you know if that second option (incremental update) is safe?
Anyway, I can just always do a Nandroid and test it ... having CWM I can't loose never anything, right?
Of course it is safe, I use it a lot. Just boot into recovery now by long press on power menu, select reboot, recovery,
First download build128. It will be under /storage/sdcard0/goo manager.
From recovery, wipe cache, dalvik, flash build 128, and reboot,
FYI, this latest build has theme engine now
Sent from my MZ601 using Tapatalk 2
wesamothman said:
First download build128. It will be under /storage/sdcard0/goo manager.
From recovery, wipe cache, dalvik, flash build 128, and reboot,
FYI, this latest build has theme engine now
Click to expand...
Click to collapse
So, the incremental update has to be flashed from recovery too?
I'll try it after a few days, when people confirms that it has not any major bug...
Thanks.
NoP_Compiler said:
Thanks a lot to both.
I'm still waiting for JDK to download for Android SDK to work (I'm on hollydays in a small house in the middle of the forest and Im connecting with GPRS via tethering...).
I'll inform about the results...
Sent from my Samsung Galaxy S2 using Tapatalk Pro.
Click to expand...
Click to collapse
Worth noting that to use fastboot and stuff, you only really need to install the Android SDK Platform-tools, maybe the regular SDK tools as well, I can't remember.
You don't need to install all the other stuff.
---------- Post added at 08:02 AM ---------- Previous post was at 08:01 AM ----------
NoP_Compiler said:
So, the incremental update has to be flashed from recovery too?
I'll try it after a few days, when people confirms that it has not any major bug...
Thanks.
Click to expand...
Click to collapse
Yes, any updates/mods/gapps updates need to be flashed in recovery.
Unless specified that its necessary by devs though, you don't need to wipe anything. I've been on JB nightlies from day 1 and I haven't wiped cache or anything since the initial wipe.
Is it possible to...
a.- change the system font (too 'light' in my xoom).
b.- disable jellybean UI animations...
?
I don't know about question a, though I'm sure its possible.
As for question b, try a different launcher. Apex launcher and nova launcher are both popular Android 4.0+ launchers (check play store for them).
Eos ROM,m settings, developer options, disable animations and transitions
Sent from my MZ601 using Tapatalk 2
For my fellow Stingray users (and possibly Everest users as well, if they're having similar issues), I was one of the group of people who couldn't get data on any 4.4 roms after going through the BigPart process. After a bunch of trial and error (and some excellent suggestions from fellow community members, I was able to get data working again and I'm happily enjoying KitKat on my three-year-old Xoom. If you've got a bit of patience and an hour or so, I believe I've got the solution to help you restore your data as well.
IMPORTANT: This entire process should be completely harmless to your Xoom, and the goal here is to help the group of Stingray users who lost all data functionality to repair that issue so that they can enjoy the full benefits of Android 4.4 (and potential future updates). That said, you do this at your own risk, and in doing so, you agree not to hold me accountable if you brick your Xoom, or if it dies, loses data (you’re going to lose everything but what’s on your SD Card, so think about that before you start the process), or any other unforeseen circumstances.
STAGE 1: Reverting to Stock Partitions
1.) DISCLAIMER: Any and all data on anything but your external SD Card will be completely wiped. If there are any back-ups you value, move them to your SD Card, your computer, or a cloud storage account. There’s no getting them back once you start this process.
2.) First off, you need to make sure you have everything you need downloaded and ready. You will need the following on your SD Card:
-TWRP 2.6.3.0 touch recovery from @runandhide05
-TWRP 2.6.3.0 BigPart touch recovery from @runandhide05
-a standard partition Stingray rom (I used CM 10.1 from @Steady Hawkin, 10/28 build, which you can find here)
-(optional) GApps package for standard partition rom (I used the 02.20.2013 Unified GApps found here, but you seriously don’t need them for anything.
-your BigPart rom of choice (I went with CM 11, which you can find in this thread, but there’s also OmniRom, which you can find in this thread, both of which were kindly ported by @Schischu. If you opt for Omni, you’ll also need a flashable zip file of the Superuser app of your choice.)
-your 4.4 GApps of choice (I use the PA Modular Full GApps, but any 4.4 GApps will be fine once you’ve repartitioned)
-Universal Xoom root .zip file, created by @solarnz (which you can find here)
As well as the following on your computer:
-The Android SDK, specifically ADB and Fastboot (if you don’t have this set up yet, start at the very beginning: http://developer.android.com/sdk/index.html)
-a stock android rom for the Stingray (I used HRI66, which you can find here)
-TWRP 2.6.3.0 touch recovery from @runandhide05
And one last thing:
-A good wifi connection (either through a wireless router or using your phone or other device with a data plan)
3.) Reboot your tablet into recovery and flash the non-BigPart TWRP 2.6.3.0 touch recovery. DO NOT REBOOT YET!
4.) Tap the Home icon, tap the Wipe tab, tap the Advanced Wipe tab, and wipe everything but sdcard (that means Dalvik Cache, System, Cache, Data, and Internal Storage)
5.) Tap the Home icon, tap the Reboot tab, tap the Recovery tab. You will get a “No OS” warning, tap “Reboot Anyway”. You will be prompted to install SuperSU – ignore this and reboot into recovery.
6.) Once you’re back into recovery (CAUTION: THIS MAY TAKE SOME TIME. BE PATIENT AND LET YOUR TABLET DO ITS THING!) You may get a warning about data being encrypted, but just tap the Home icon, then tap the Wipe tab. Tap the Format Data tab, type “yes” when prompted, and wait for your data to format. Go back to the main wipe menu, tap the Advanced Wipe tab, and select System and Cache and proceed to wipe them.
7.) Tap the Home icon, tap the Reboot tab, tap the Recovery tab. Again, you will get the “No OS” warning and the prompt to install SuperSU – ignore both of them and allow your tablet to reboot into recovery, which, again, may take some time. (I’ve done this process multiple times and each time, the amount of time that it needed on various reboots was different, so be patient if you don’t want to brick your Xoom.)
8.) Tap the Mount tab. Sdcard, Cache, and Data should be checked; System should be unchecked. Tap the box next to System, make sure that it mounts without any errors, and then uncheck it again. If you’ve made it this far, you’re back to the standard partitions.
9.) Tap the Install tab. Your external sdcard should be showing by default. Flash your standard partition rom (in my case, CM 10.1) and your GApps, if you so choose (though again, they serve no purpose).
10.) Tap the Home icon, tap the Reboot tab, and tap the System tab to reboot into your chosen standard partition rom. Ensure that everything loads (again: this may take some time) and go through the setup process.
11.) Go into Settings and enable developer options (Settings --->About Tablet--->tap Build Number several times until Developer options are enabled.
12.) Go into Developer options and make sure that Android debugging is checked. Now you’re ready for Stage 2.
STAGE 2: Returning to stock Honeycomb
1.) Find your stock Honeycomb rom (as mentioned earlier, I used HRI66) and unzip it into a folder of its own.
2.) Inside the folder you unzipped, you may find another folder designated MZ600_HRI66. Inside that folder, there will be four files, boot.img, recovery.img, system.img, and userdata.img
3.) Copy those files into the folder that has adb.exe and fastboot.exe (if you simply installed the Android SDK as instructed, it’ll be inside the platform-tools folder, which is itself inside the sdk folder).
4.) Connect your Xoom to your computer using a USB data cable (preferably a Motorola one if you have one available) and ensure that there is a notification that says “Android debugging enabled” (if you don’t see this notification, go back into Settings --> Developer options, and make sure that “USB debugging notify” has a check in the box next to it).
5.) Open a command prompt in the directory that contains adb.exe and fastboot.exe (Windows 7 and up, click the File tab and choose “Open Command Prompt”; if you’re on Vista or older, I can’t help you, but I’m sure Google can).
6.) Enter the following command:
Code:
adb reboot bootloader
7.) Your tablet will reboot to the red “M” logo and it should say “Fastboot protocol initiated” at the top in white letters. If so, proceed to step 8; if not, and assuming your tablet has rebooted normally, try step 6 again.
8.) Enter the following commands into your command prompt, one at a time, and let each one compete. You’ll get a series of status updates in both your command window and on your tablet as each process completes. Wait for it to say “Done!” before entering the next command.
Code:
fastboot flash boot boot.img
Code:
fastboot flash system system.img
Code:
fastboot flash recovery recovery.img
Code:
fastboot flash userdata userdata.img
Code:
fastboot erase cache
9.) Once all those steps have completed, enter one last Fastboot command:
Code:
fastboot reboot
10.) Your tablet should now reboot into factory Honeycomb and you can disconnect from the USB cable. As mentioned before, this is one of those reboots that could take a few seconds up to several minutes, so just be patient!
NOTE: These next several steps are much easier to complete if you have a high-speed wifi connection. At this point, if you don’t have a data connection, don’t panic, at least not yet. I tried multiple times to activate my device on the Verizon network, and while it said it was successful each time, I never managed to get a 3G connection back. Your best bet is to connect to Wifi and continue the process.
11.) On your tablet, go to Settings --> About tablet --> System Updates. More than likely, your tablet has already started downloading the next update, so you can just sit back and wait for it to download. You’ll get a notification when the download is complete. While you’re waiting, on your computer, move boot.img, system.img, recovery.img, and userdata.img from your ADB folder back into a folder where you’ll have them on-hand if you need them again.
12.) Once you get the notification that the update is downloaded, you’ll have the option to reboot and install or install later. Choose to reboot and install. Your tablet will reboot into the stock Android recovery and install the update, then go to the “M” logo screen and more white text will appear. Wait for this to complete and your tablet to reboot again.
13.) Repeats steps 11 and 12 until you receive and install the IMM76L build (I believe that’s the one) – it’ll be Ice Cream Sandwich and your data should be working. If it’s not, then I’m not sure what to suggest. Your tablet will attempt to download the stock 4.1.2 build (JZO45M) and if it completes, it’s not a big deal, but MAKE SURE YOU DON’T INSTALL IT!
14.) Go to Settings --> Developer options and turn on USB debugging again. (If everything is grayed out, tap the On/Off slider in the upper righthand corner to make the checkbox clickable). At this point, you’re ready for Stage 3.
STAGE 3: Re-rooting
1.) On your computer, find the copy of TWRP 2.6.3.0 touch recovery from @runandhide05 (the standard one, not the BigPart one, yet), and unzip it into its own folder. Copy the recovery.img file from the unzipped folder into the same directory that contains adb.exe and fastboot.exe. IT IS CRUCIAL THAT YOU REMOVED THE RECOVERY.IMG FILE THAT YOU USED TO GET BACK TO STOCK EARLIER!
2.) Connect your Xoom to your computer via USB data cable and ensure that the USB debugging notification appears and that your computer recognizes your Xoom.
3.) Open a command prompt in the directory with adb.exe and fastboot.exe and enter the following command:
Code:
adb reboot bootloader
4.) Your tablet will reboot to the “M” logo screen and it will again say “Fastboot protocol initiated”. When it’s ready, enter the following command into your command prompt:
Code:
fastboot flash recovery recovery.img
5.) Once you get the “Done” notification in the command prompt and on your tablet, enter the following command:
Code:
fastboot reboot
6.) Your tablet will reboot, and when you see the “M” logo screen, wait three seconds and press the Volume Down key. “Android recovery” will appear, press the Volume Up key.
7.) Your tablet will now boot into TWRP 2.6.3.0 and it may “hang” at the TWRP splash screen for some time – that’s normal, wait it out, and when TWRP loads, tap the Install tab. Navigate to the root of your external sdcard (if it’s not showing by default), choose the Xoom Universal root.zip file, and install it.
8.) Tap the Home icon, tap the Reboot tab, and tap System from the reboot menu. Your tablet should boot back into ICS, but you should now have a superuser app installed (ChainsDD’s, I believe). If that’s the case, and you’ve still got data functionality, then it’s time to move to Stage 4.
STAGE 4: BigPart and KitKat
1.) Reboot your tablet into recovery (you have two options – either shut down your tablet, power it back on, wait three seconds at the “M” logo screen and then press Volume Down, followed by Volume Up when it says “Android Recovery”, or reconnect your tablet to your computer with a USB data cable, open a command prompt in your adb directory, and enter the following command: adb reboot bootloader)
2.) Reboot your tablet into recovery and flash the TWRP 2.6.3.0 BigPart touch recovery. DO NOT REBOOT YET!
3.) Tap the Home icon, tap the Wipe tab, tap the Advanced Wipe tab, and wipe everything but sdcard (that means Dalvik Cache, System, Cache, Data, and Internal Storage)
4.) Tap the Home icon, tap the Reboot tab, tap the Recovery tab. You will get a “No OS” warning, tap “Reboot Anyway”. You will be prompted to install SuperSU – ignore this and reboot into recovery.
5.) Once you’re back into recovery (CAUTION: THIS MAY TAKE SOME TIME. BE PATIENT AND LET YOUR TABLET DO ITS THING!) You may get a warning about data being encrypted, but just tap the Home icon, then tap the Wipe tab. Tap the Format Data tab, type “yes” when prompted, and wait for your data to format. Go back to the main wipe menu, tap the Advanced Wipe tab, and select System and Cache and proceed to wipe them.
6.) Tap the Home icon, tap the Reboot tab, tap the Recovery tab. Again, you will get the “No OS” warning and the prompt to install SuperSU – ignore both of them and allow your tablet to reboot into recovery, which, again, may take some time.
7.) Tap the Mount tab. Sdcard, Cache, and Data should be checked; System should be unchecked. Tap the box next to System, make sure that it mounts without any errors, and then uncheck it again. If you’ve made it this far, you’ve successfully repartitioned your tablet back to BigPart.
8.) Tap the Install tab. Your external sdcard should be showing by default. Flash your BigPart rom (and, if you’re installing Omni, your superuser zip file, or, if you’re not flashing one of Schischu’s KitKat roms, the corresponding BigPart boot img or the ElementalX kernel). NOTE: BECAUSE THIS WASN'T SUCCESSFUL FOR EVERYONE, FOR THIS STEP, PLEASE FLASH SCHISCHU'S JANUARY 4TH VERSION OF CM 11 FOR THE STINGRAY, WHICH YOU CAN FIND HERE.
NOTE: You probably can flash your GApps at this point as well; however, I’m detailing the process as I had success with it.
9.) Tap the Home icon, tap the Reboot tab, and tap the System tab to reboot into your chosen BigPart rom. Go through the setup process, ensure you have data, and if you do (and you didn’t do so already), reboot and install your GApps.
NOTE: You may get com.android.phone force close errors when going through setup – if this happens, it’s a good thing – pull your SIM card and reboot, complete setup, re-insert SIM card and reboot again.
If this post helped you, then give thanks to the following people (because they did all the hard work):
@bigrushdog (for the hard work on BigPart) @realjumy (for the hard work on BigPart)
@Schischu (for the excellent KitKat roms)
@xyrcncp (for clarifications that led to a minor breakthrough) @rapson2000 (for thinking outside the box and leading to my breakthrough)
There are probably a bunch of other people who contributed that I missed, but I wanted to get this up there in case other people were still having issues.
Reserved to answer any questions that may arise.
LTE data still not working
All your instructions were good and working, up until I reinstalled Cyanogenmod 11 (cm-11-20140203-UNOFFICIAL-2235+0100-stingray.zip). Then I lost data again. I'm guessing from your instructions and how things stopped working that there's something about the re-partitioning process that makes the LTE APKs just stop working.
The Xoom is detecting the LTE network, just as before, there are no bars and no data connection. Looks like I'll have to repartition again and use a ROM that sticks with the old partitions and wait for a possible fix to this issue.
variatbg said:
All your instructions were good and working, up until I reinstalled Cyanogenmod 11 (cm-11-20140203-UNOFFICIAL-2235+0100-stingray.zip). Then I lost data again. I'm guessing from your instructions and how things stopped working that there's something about the re-partitioning process that makes the LTE APKs just stop working.
The Xoom is detecting the LTE network, just as before, there are no bars and no data connection. Looks like I'll have to repartition again and use a ROM that sticks with the old partitions and wait for a possible fix to this issue.
Click to expand...
Click to collapse
I've repartitioned multiple times now - once from stock, rooted Jelly Bean, and got no data, then back to standard partition and CM 10.1 with only 3G, back to BigPart with no data, then I followed the steps that I wrote up here and now I'm BigParted on CM 11 with data. So it's not the repartitioning process. I'm a testament to that. What were you on when you did the BigPart process for the first time?
Edit: if you're willing to do the whole process again, would you try installing the very first CM 11 that Schischu released? I should've specified that that's the rom I installed first after repartitioning this time. One I had working data, I updated to the latest version.
Sent from my HTC6435LVW using xda app-developers app
Help with MZ605 (Everest) stock (step 10 of stage 2)
Thank you very much for your work on the data problem.
I have a Brazilian MZ605 (WIFI + 3G) and the problem I'm facing is that after flashing the stock rom it don't allow me to proceed to the configuration menu if I don't put a valid SIM card, and that is my dead end, it isn't recognizing my SIM card so I cannot follow the rest of your guide...
Do you have any idea on how I could force the stock to ignore the first SIM verification?
Thank you in advance!
LTE data still not working
webeougher said:
What were you on when you did the BigPart process for the first time?
Click to expand...
Click to collapse
I was first using OmniROM of January 12, though I can't quite recall. Then I also tried CM 11 and no dice there. Following your process, when I first reverted to CM 10.1 on original partitions, data was immediately present again.
It was there through all the reversions to stock 3.2.2, and through every OTA update Motorola sent to the device. In fact, some of the updates wouldn't even show up except over Mobile Data.
One thing that might make a difference is that this Xoom is on a business account through Verizon. It's not part of a shared data plan, but there might be a different categorization perhaps?
Anyways, I'm not going through all that partitioning and flashing again just now. I will though, eventually do a Nandroid backup and try again, once I see here or elsewhere that something might have changed for me. I have spent just too much time on this, and data is more important in this case than KitKat.
Thiago Delatorre said:
Thank you very much for your work on the data problem.
I have a Brazilian MZ605 (WIFI + 3G) and the problem I'm facing is that after flashing the stock rom it don't allow me to proceed to the configuration menu if I don't put a valid SIM card, and that is my dead end, it isn't recognizing my SIM card so I cannot follow the rest of your guide...
Do you have any idea on how I could force the stock to ignore the first SIM verification?
Thank you in advance!
Click to expand...
Click to collapse
This is a stupid question, but did you flash the stock rom I linked in this thread, or a stock Everest rom?
Sent from my HTC6435LVW using xda app-developers app
webeougher said:
This is a stupid question, but did you flash the stock rom I linked in this thread, or a stock Everest rom?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Not stupid at all, it could make all the difference!
I flashed the MZ605 Brazilian, MZ601 International and the one you linked. The formers booted and asked for the SIM card and the last just didn't boot. I put two different SIM cards and it didn't work, I was wondering it there were a way to circumvent the first check. I also read somewhere that the MZ601/MZ605 US Retail version didn't check for a SIM card on the first boot, but I didn't find an official stock rom for such a device (I don't even know if these devices exist).
The next trial would be with the MZ600 Verizon 3G, but I'm not that confident that it is gonna work...
Another problem is that I stopped using the 3G data on Xoom for more than one year, so I can't even tell if the SIM card would be recognized nowadays...
Beside that, what choices do we have? Is it possible to avoid the first boot SIM card verification? Is it possible to extract the baseband files from another MZ605 and put them in mine?
Do you know what kind of file/library is the baseband?
Another thing, how the modem stays working if we completely clean the internal storage of Xoom going from the official to the CM11 (on your procedure)? What I'm missing...?
Thank you very much for your guide, I didn't know how to revert the bigPart
Regards,
Thiago
So @webeougher ...I FINALLY had some time to sit down with my Xoom and try this. In the interest of verifying that this process works, I went through your guide step by step without deviation and... SUCCESS! I'm back to BigPart CM11 w/ full 4G LTE!!! Thanks for taking the time to write out such a detailed guide! It was just about perfect.
I have just two things to mention... First, the link to the stock image HRI66 didn't work. I had to look elsewhere (http://rootzwiki.com/topic/1586-stock-images/). Also, in step one of stage 4, the adb command should be "adb reboot recovery", not "adb reboot bootloader"... correct?
One last thing, at this point should we start recommending people not attempt BigPart / CM11 if they start from stock Jelly Bean?
Again, I can't tell you how stoked I am to be back up and running. This... all of it... BigPart, CM11 for Xoom, and the fix for the no data situation... it's all awesome.
Awesome! It's amazing that somebody was able to figure out the process with all of
it's steps, and have it actually work.
I am back on my feet now, have my CM 11 Bigpart, as well as 4G LTE. Woo!
Thank you!
About the only thing I did differently was to do the "fastboot oem lock" after reflashing the
baseline honeycomb partition images. I always thought you had to have the thing locked before
it would allow you to do OTA updates. Whatever.
I then let the OTA updates go by(except for that final one), then did a "fastboot oem unlock"
before applying the universal root. Other than the locking & unlocking, I followed your instructions
exactly. Perfecto!
rmkenney12 said:
Awesome! It's amazing that somebody was able to figure out the process with all of
it's steps, and have it actually work.
I am back on my feet now, have my CM 11 Bigpart, as well as 4G LTE. Woo!
Thank you!
About the only thing I did differently was to do the "fastboot oem lock" after reflashing the
baseline honeycomb partition images. I always thought you had to have the thing locked before
it would allow you to do OTA updates. Whatever.
I then let the OTA updates go by(except for that final one), then did a "fastboot oem unlock"
before applying the universal root. Other than the locking & unlocking, I followed your instructions
exactly. Perfecto!
Click to expand...
Click to collapse
It's not necessary to relock to get OTAs, so long as you're running a pure stock rom.
Sent from my Galaxy Nexus using xda app-developers app
webeougher said:
4.) Tap the Home icon, tap the Wipe tab, tap the Advanced Wipe tab, and wipe everything but sdcard (that means Dalvik Cache, System, Cache, Data, and Internal Storage)
...
8.) Tap the Mount tab. Sdcard, Cache, and Data should be checked;
Click to expand...
Click to collapse
There was aleady a problem with Step 4... unable to mont /cache - therefore Failed to wipe /data and /cache.
Step 8 also showed NO /data-partition.
I downloaded the original Xoom stock boot,system,recovery (MZ601) MZ601_H.6.1-38-5_TMO_Germany...
Code:
fastboot flash boot boot.img
Code:
fastboot flash system system.img
Code:
fastboot flash recovery recovery.img
Code:
fastboot flash userdata userdata.img
Code:
fastboot erase cache
Click to expand...
Click to collapse
boot status - done!
system status - done!
recovery status - done!
userdata status | | | | | | | | | | | | | | | | | | | | | | - done! (there have been such weird lines)
formatting cache: CAC status: -done!
Rebooting - after 60 min of M-logo I quit.
Is there a way to TOTALLY MANUALLY repartition the xoom and recover everything from scratch?
EDIT: New development: not even in fastboot mode I'm able to flash anything anymore... CWM recovery (recovery-clockwork-touch-6.0.3.2-everest.img and recovery-Tiamat-R4c-100611-1150-cwm.img) for example: status done! Still TWRP
Thank you and Question
First off thank you this worked perfectly for me, everything worked like it was supposed to! Now the question is; After I have followed these steps, can I update to the newer version of CM 11, because there are a couple things that are buggy in the first couple version?
semp3rfi said:
First off thank you this worked perfectly for me, everything worked like it was supposed to! Now the question is; After I have followed these steps, can I update to the newer version of CM 11, because there are a couple things that are buggy in the first couple version?
Click to expand...
Click to collapse
Absolutely. I flashed to whatever the latest nightly was when I completed the process, and I've updated several times through the CM updater as well and data still works as intended.
Sent from my HTC6435LVW using xda app-developers app
Thank you
webeougher said:
Absolutely. I flashed to whatever the latest nightly was when I completed the process, and I've updated several times through the CM updater as well and data still works as intended.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Awesome thanks for the reply!
What does this whole sequence actually accomplish? Is the problem that we have the wrong radios installed, and this is a way to get the right ones installed? If so is there a way to extract the new radios so that they can be installed directly?
I am just trying to understand the process, and see if it can be simplified.
Thanks much for coming up with a solution. I will try it soon.
I'm no developer, but my best theory is that these BigPart roms and kernels use proprietary files from ICS. By taking the OTA to JB, something changed. I tried flashing other radio files and nothing worked, so when it was suggested that only people who had taken the OTA were losing data, I went through this process just on a whim to see if it worked. When it did, I didn't really think much else about it.
Sent from my HTC6435LVW using xda app-developers app
thx
The for this topic really informative
Wow
Talk about a long process but it worked for me! Thank you so very much!
I did have an issue with the google keyboard fc on me after going through the whole process but I ended up downloading the go keyboard (not selecting it) and for some reason that took care of the Google keyboard fcing.
I also used the omnirom instead of cm.
Again, thanks for your hard work!
Wanted to thank you. I pulled out the ole Xoom and flashed Omni and the data wasn't working... But you're instructions got me back on track. Thanks again bro! :good:
Hi All, new to this forum... what brought me here is trying to figure out if I can upgrade the TF101 to android higher than 4.0.3 that seems to be the "normal" latest version you can get.
Issues I have are: lockup, freeze, twitter post (crash twitter), screen weird colors (need reboot) etc... Maybe I have some hardware issue... planing to open the case and verify all connectors are ok and well seated.
I just spent 4 hours looking around this forum and saw the KatKiss 4.4.4 thing... I say thing because I have no clue (and did not find how) to install this thing.
So! Is it worth it that I spent hours more on understanding how to upgrade, debug and all... or I just go buy a new tablet?
I saw some post around the twitter issue that did not work either after KatKiss upgrade, so not sure if it's worth it ?
I was looking at the Samsung Pro tablets with 8 cores... seems amazing! But pricy!
Anyhow, recommendations?
If you say... sure try to upgrade to 4.4.4 with KatKiss... ok, I can try that, but from the last 4 hours of reading/looking around, I did not find instructions steps I could understand.
Most of those steps I have not clue what they are!
These builds are designed to be installed from your favorite recovery. MAKE SURE TO INSTALL A COMPATIBLE ANDROID 4.2/4.3 RECOVERY!
TWRP >= 2.3.2.3 is recommended, new TWRP available here
Backup everything !
Go to recovery
Make a full wipe / factory reset (you can skip this step if you're already on KatKiss-4.4, if ever you encounter a problem do the full wipe and try again before reporting )
Format /system (only if Version<026)
Flash the rom
Flash KatKiss gapps
Wipe cache/dalvik
Reboot
Click to expand...
Click to collapse
Thanks for any feedback
Cheers!
Simon
I have the tab pro and i like it a lot.
I also have the tf101 running katkiss.
The katkiss is running smooth for me.
All is well and no issues this far.
So I would say try katkiss.
Verstuurd vanaf mijn SM-G900F met Tapatalk
r2go said:
I have the tab pro and i like it a lot.
I also have the tf101 running katkiss.
The katkiss is running smooth for me.
All is well and no issues this far.
So I would say try katkiss.
Verstuurd vanaf mijn SM-G900F met Tapatalk
Click to expand...
Click to collapse
Would love to try katkiss.... but I did not find a how-to steps I can understand.... Any help would be nice.
:laugh:
Simon
SimonFiliatrault said:
Would love to try katkiss.... but I did not find a how-to steps I can understand.... Any help would be nice.
:laugh:
Simon
Click to expand...
Click to collapse
Hi Simon.
Is your device already rooted?
You need to root your device first.
What android version are you running?
Verstuurd vanaf mijn SM-G900F met Tapatalk
r2go said:
Hi Simon.
Is your device already rooted?
You need to root your device first.
What android version are you running?
Verstuurd vanaf mijn SM-G900F met Tapatalk
Click to expand...
Click to collapse
Device not rooted... Android 4.0.3.
I am looking for step-by-step instructions... if they exist?
Never did that type of mod before.
Thanks,
Simon
SimonFiliatrault said:
Device not rooted... Android 4.0.3.
I am looking for step-by-step instructions... if they exist?
Never did that type of mod before.
Thanks,
Simon
Click to expand...
Click to collapse
Easiest way, use Easyflasher (If your TF101 has a serial number B6O or eariler (Some B7O), it is an SBK1, most B7O and all higher are SBK2) choosing the wrong one in Easyflasher will not do any harm, it just won't work
http://forum.xda-developers.com/showthread.php?t=1688012
1: Flash TWRP recovery with Easyflasher
2. Download KatKiss ROM #33 & Latest Gapps and copy to your MicroSD, stick MicroSD Card into TF101
3: Boot to TWRP Recovery by powering off the TF, then pressing and holding Power & Volume Down until the white text appears at the top of the screen, then quickly hit Volume Up once
4: Goto the WIPE menu, and wipe everything apart from External Storage (This will 100% wipe your TF, so if you have anything you want to keep, back it up, you can also make a Nandroid backup inside of TWRP, so make sure your MicroSD Card has enough room if you choose that)
5: Once everything is wiped, goto the INSTALL menu and install KatKiss ROM you copied to the MicroSD Card (Might have to select External from the INSTALL menu to navigate to the MicroSD Card)
6: When the ROM says it is completed the install, go back to the INSTALL menu and install the GAPPS you also copied to the MicroSD Card
7: Once GAPPS have completed installing (Ignore any messages about failing to mount partitions etc) WIPE Cache and Dalvik Cache (Might ask you immediately after flashing Gapps, if not, do it from the WIPE menu
8: Choose REBOOT > SYSTEM or POWER OFF > REBOOT
9: All being well, you are now running the KatKiss ROM
---
TIPS:
When using Easyflasher, you're gonna need to install the "Universal Naked Drivers" from the Easyflasher thread - use a 32bit Windows 7 for least chance of any problems, 64bit windows requires driver signing, and so do all versions of Windows 8.x, you can use 8.x but you'll need to disable driver signing mode before installing them
---
Any problems, reply here and I`ll check every now and then
ok here's the detail steps I did...
1) I have a TF101, B60... S/N, thus SBK1 (what ever that means!)
2) Using this thread: http://forum.xda-developers.com/showthread.php?t=1688012
- Need APX Drivers: http://forum.xda-developers.com/showthread.php?t=1514942
Found those instructions that partially work:
http://forum.xda-developers.com/showthread.php?t=1514942&page=4
Search in the start menu for Device Manager and open it.
Plug in your tablet via USB while in APX mode (hold power button and volume (+) until the screen turns off).
The driver should try to automatically install off the tablet upon plugging it in to your computer.
If it fails to install, you will have an "Unknown Devices" section in Device Manager.
Right click on Unknown Devices and hit update driver.
Then hit manually install driver. Point the file browser to the root folder of the extracted package that you downloaded.
For clarification: You downloaded the zip in the OP called Universal_Naked_Driver_0.72.zip.
When you extract it, you should get something like Universal Naked Driver 0.72 or something like that.
Point that file browser to the newly extracted folder, NOT the subfolders.
If you point it to the amd64 or the i386 subfolders it will not work. Hope this helps you out!
That is partly true... here's what I did:
1. power button + volume up
2. device manager showed "other devices" - APX
3. right-click APX and update driver
4. point to extracted naked driver folder
5. Cannot install - hash not present issue!
6. Found this how-to on installing unsigned drivers: http://dhakshinamoorthy.wordpress.com/2012/05/14/installing-an-unsigned-driver-in-windows-8-x64/
- Cannot find the control panel advanced startup menu!!!
Found those that work! http://pcsupport.about.com/od/windows-8/a/open-advanced-startup-options-windows-8.htm
Method 2: PC Settings
Swipe from the right to open the charms bar.
Tip: If you have a keyboard, use WIN+I and then skip to Step 3.
Tap or click on Settings.
Tap or click on Change PC settings at the bottom of the charms bar.
Choose Update and recovery from the list of options on the left of the PC settings window.
Note: Prior to Windows 8.1, choose General instead and then skip to Step 6.
Choose Recovery.
Locate Advanced startup, at the bottom of the list of options on your right.
Tap or click on Restart now.
Wait through the Please wait message until Advanced Startup Options opens.
After reboot, I could install the Asus Transformer APX interface.
downloaded easy flasher: http://yarr.ntg.cx/pub/EasyFlasher-0.8.3b-STABLE.zip
extracted and started with SBK1
Choose TWRP 2.2.1 and clicked flash
Tablet need to be in APX mode (power + volume up)
click flash and ok
Saw this on easy flash:
Running Wheelie..
>Tablet is now ready for Nvflash
Flashing twrp.SOS
>Finished, now reboot into recovery!
Saw this on tablet:
Entering NvFlash recovery mode / Nv3p Server
Chip Uid: xxxx
!!! phone update success !!!
!!! phone update success !!!
Copying those file to root of flash drive
- KatKiss-4.4.4_032b.zip
- gapps-KatKiss-4.4.4_20140720.zip
- fsync_on.zip
3) Booted to TWRP Recovery
1. Pressing and holding Power & Volume Down
2. when white text appears at the top of the screen, then quickly hit Volume Up once
Now we see the TWRP!
4) Goto the WIPE menu, and wipe everything apart from External Storage (This will 100% wipe your TF, so if you have anything you want to keep, back it up, you can also make a Nandroid backup inside of TWRP, so make sure your MicroSD Card has enough room if you choose that)
- cache
- Dalvik cache
- Factory reset
- System
- Internal storage
- Format data
FAILED!
Unable to format data
5) Once everything is wiped, goto the INSTALL menu and install KatKiss ROM you copied to the MicroSD Card (Might have to select External from the INSTALL menu to navigate to the MicroSD Card)
- Choose katkiss rom
KatKiss-4.4.4_032b.zip
- clicked home
6) When the ROM says it is completed the install, go back to the INSTALL menu and install the GAPPS you also copied to the MicroSD Card
- gapps-KatKiss-4.4.4_20140720.zip
- Home
7) Also installed fsync_on.zip
- This is optional to have more speed, but can cause data loss if tablet reboot
8) WIPE Cache and Dalvik Cache
9) Reboot - System
- Should see the new OS start - with the dog and colored circles!
10) After a short minute... you will get the welcome and setup screen
- Do standard setup!
Tablet is up and running... NICE!
Thanks a LOT!
Will now re-install my stuff and test... will keep you posted.
Do this detailed how-to exist somewhere?
CRAP!!! The main reason I updated this tablet was in the hopes to fix the twitter issue... that is, when trying to post a new tweet, the app crash and restart...
SAME issue!
Any tips on this one would be wonderful.
It's easy.
First root it. Rooting has a few basic common steps. just get the files right.
Then install the rom in recovery!
Voila!
SimonFiliatrault said:
ok here's the detail steps I did...
1) I have a TF101, B60... S/N, thus SBK1 (what ever that means!)
2) Using this thread: http://forum.xda-developers.com/showthread.php?t=1688012
- Need APX Drivers: http://forum.xda-developers.com/showthread.php?t=1514942
Found those instructions that partially work:
http://forum.xda-developers.com/showthread.php?t=1514942&page=4
Search in the start menu for Device Manager and open it.
Plug in your tablet via USB while in APX mode (hold power button and volume (+) until the screen turns off).
The driver should try to automatically install off the tablet upon plugging it in to your computer.
If it fails to install, you will have an "Unknown Devices" section in Device Manager.
Right click on Unknown Devices and hit update driver.
Then hit manually install driver. Point the file browser to the root folder of the extracted package that you downloaded.
For clarification: You downloaded the zip in the OP called Universal_Naked_Driver_0.72.zip.
When you extract it, you should get something like Universal Naked Driver 0.72 or something like that.
Point that file browser to the newly extracted folder, NOT the subfolders.
If you point it to the amd64 or the i386 subfolders it will not work. Hope this helps you out!
That is partly true... here's what I did:
1. power button + volume up
2. device manager showed "other devices" - APX
3. right-click APX and update driver
4. point to extracted naked driver folder
5. Cannot install - hash not present issue!
6. Found this how-to on installing unsigned drivers: http://dhakshinamoorthy.wordpress.com/2012/05/14/installing-an-unsigned-driver-in-windows-8-x64/
- Cannot find the control panel advanced startup menu!!!
Found those that work! http://pcsupport.about.com/od/windows-8/a/open-advanced-startup-options-windows-8.htm
Method 2: PC Settings
Swipe from the right to open the charms bar.
Tip: If you have a keyboard, use WIN+I and then skip to Step 3.
Tap or click on Settings.
Tap or click on Change PC settings at the bottom of the charms bar.
Choose Update and recovery from the list of options on the left of the PC settings window.
Note: Prior to Windows 8.1, choose General instead and then skip to Step 6.
Choose Recovery.
Locate Advanced startup, at the bottom of the list of options on your right.
Tap or click on Restart now.
Wait through the Please wait message until Advanced Startup Options opens.
After reboot, I could install the Asus Transformer APX interface.
downloaded easy flasher: http://yarr.ntg.cx/pub/EasyFlasher-0.8.3b-STABLE.zip
extracted and started with SBK1
Choose TWRP 2.2.1 and clicked flash
Tablet need to be in APX mode (power + volume up)
click flash and ok
Saw this on easy flash:
Running Wheelie..
>Tablet is now ready for Nvflash
Flashing twrp.SOS
>Finished, now reboot into recovery!
Saw this on tablet:
Entering NvFlash recovery mode / Nv3p Server
Chip Uid: xxxx
!!! phone update success !!!
!!! phone update success !!!
Copying those file to root of flash drive
- KatKiss-4.4.4_032b.zip
- gapps-KatKiss-4.4.4_20140720.zip
- fsync_on.zip
3) Booted to TWRP Recovery
1. Pressing and holding Power & Volume Down
2. when white text appears at the top of the screen, then quickly hit Volume Up once
Now we see the TWRP!
4) Goto the WIPE menu, and wipe everything apart from External Storage (This will 100% wipe your TF, so if you have anything you want to keep, back it up, you can also make a Nandroid backup inside of TWRP, so make sure your MicroSD Card has enough room if you choose that)
- cache
- Dalvik cache
- Factory reset
- System
- Internal storage
- Format data
FAILED!
Unable to format data
5) Once everything is wiped, goto the INSTALL menu and install KatKiss ROM you copied to the MicroSD Card (Might have to select External from the INSTALL menu to navigate to the MicroSD Card)
- Choose katkiss rom
KatKiss-4.4.4_032b.zip
- clicked home
6) When the ROM says it is completed the install, go back to the INSTALL menu and install the GAPPS you also copied to the MicroSD Card
- gapps-KatKiss-4.4.4_20140720.zip
- Home
7) Also installed fsync_on.zip
- This is optional to have more speed, but can cause data loss if tablet reboot
8) WIPE Cache and Dalvik Cache
9) Reboot - System
- Should see the new OS start - with the dog and colored circles!
10) After a short minute... you will get the welcome and setup screen
- Do standard setup!
Tablet is up and running... NICE!
Thanks a LOT!
Will now re-install my stuff and test... will keep you posted.
Do this detailed how-to exist somewhere?
Click to expand...
Click to collapse
I am essentially trying to do this although I have a C20 so I use SBK2 in Easy Flash. However, after I do my wipes, then go to flash my rom, I get an error message that it can't open the zip file What is strange is that I have done this before and have had KK installed on my tablet.
706
Razor64 said:
It's easy.
First root it. Rooting has a few basic common steps. just get the files right.
Then install the rom in recovery!
Voila!
Click to expand...
Click to collapse
Unsure what you are referring to?
1) Rooting the TF101
2) Fixing Twitter issue
As you see in the thread, I have successfully installed 4.4.4 KatKiss.
barkeater said:
I am essentially trying to do this although I have a C20 so I use SBK2 in Easy Flash. However, after I do my wipes, then go to flash my rom, I get an error message that it can't open the zip file What is strange is that I have done this before and have had KK installed on my tablet.
Click to expand...
Click to collapse
Did you make sure the zip on the flash drive are ok? Did you try to open them on a PC?
Found a solution for twitter! Simply installed which is better! TWEEDLE
Razor64 said:
It's easy.
First root it. Rooting has a few basic common steps. just get the files right.
Then install the rom in recovery!
Voila!
Click to expand...
Click to collapse
KatKiss is already rooted!
SimonFiliatrault said:
Found a solution for twitter! Simply installed which is better! TWEEDLE
Click to expand...
Click to collapse
Great pleased you managed to get it working in the end, you can now update TWRP to either the latest official 2.3.2.3 or the unofficial which has been taken over by another member, that's possibly why you ended up with the DATA failing to wipe
Twitter works ok for me, but there are 2 different types of KatKiss, there is the normal one which has a speed increase, and the NonLinaro version which has much better compatibility with apps
Its possible twitter is not liking the Linaro version (Normal one)
Anyway, you are set to flash whichever ROMs you like now you have TWRP, but Id advise updating to 2.3.2.3 to avoid issues, that's the version Ive been running since it was released
Oh and SBK1 and 2 mean, Secure Boot Key, SBK1 was leaked and therefore very easy to flash recovery and other stuff to that required the key, SBK2 did not leak, so devs had to find workarounds in order to flash recovery
Wow Simon.
Already so much.
By the way you sound like a pro already
Now just follow what *detection* says.
That Rom is fast and smooth.
Verstuurd vanaf mijn SM-G900F met Tapatalk
I now want to update again since I have some issue with wifi disconnecting and would like to have original Twitter app working.
So here's a couple of questions:
1. TWRP... before I used EasyFlasher that have TWRP 2.2.1
- I did not find easy flasher with TWRP 2.3.2.3 what do you recommend to use to update TWRP? Link please.
2. You said Twitter work for you and you installed the NonLinaro... right?
- I would be using this link: http://forum.xda-developers.com/showthread.php?t=2592890
That's good?
Any other tips, new version since you last post?
Thanks,
Simon
SimonFiliatrault said:
I now want to update again since I have some issue with wifi disconnecting and would like to have original Twitter app working.
So here's a couple of questions:
1. TWRP... before I used EasyFlasher that have TWRP 2.2.1
- I did not find easy flasher with TWRP 2.3.2.3 what do you recommend to use to update TWRP? Link please.
2. You said Twitter work for you and you installed the NonLinaro... right?
- I would be using this link: http://forum.xda-developers.com/showthread.php?t=2592890
That's good?
Any other tips, new version since you last post?
Thanks,
Simon
Click to expand...
Click to collapse
I can help you with 2.3.2.3 TWRP
Code:
https://mega.co.nz/#!0MFjWR5L!Xsf2b83h54I97z5Zsp_1PUn6mDHi6itZIc2GGoFkAeI
This Easyflasher has 2.3.2.3 updated inside (Credit to Frederuco)
*Detection* said:
I can help you with 2.3.2.3 TWRP
Code:
https://mega.co.nz/#!0MFjWR5L!Xsf2b83h54I97z5Zsp_1PUn6mDHi6itZIc2GGoFkAeI
This Easyflasher has 2.3.2.3 updated inside (Credit to Frederuco)
Click to expand...
Click to collapse
Ok... Downloaded this new version and ran it:
Running Wheelie..
>Tablet is now ready for Nvflash
Flashing twrp.SOS
>Finished, now reboot into recovery!
on the tablet, I see the !!!!! phone update success!!!! 2 time
Trying now to get in "recovery mode"...
Tried simple reboot in recovery from KatKiss, does not work.
Ideas?
SimonFiliatrault said:
Ok... Downloaded this new version and ran it:
Running Wheelie..
>Tablet is now ready for Nvflash
Flashing twrp.SOS
>Finished, now reboot into recovery!
on the tablet, I see the !!!!! phone update success!!!! 2 time
Trying now to get in "recovery mode"...
Tried simple reboot in recovery from KatKiss, does not work.
Ideas?
Click to expand...
Click to collapse
Did you reboot fully into KK before trying to get into recovery after flashing 2.3.2.3?
You need flash 2.3.2.3 > reboot fully into KK to complete the install > then reboot into recovery
Also you can try powering off the TF, then hold Vol down and Power until you see the white text at the top of the screen, then release all buttons and quickly tap Vol up to enter recovery
*Detection* said:
Did you reboot fully into KK before trying to get into recovery after flashing 2.3.2.3?
You need flash 2.3.2.3 > reboot fully into KK to complete the install > then reboot into recovery
Also you can try powering off the TF, then hold Vol down and Power until you see the white text at the top of the screen, then release all buttons and quickly tap Vol up to enter recovery
Click to expand...
Click to collapse
After first attempt, yes I entered KK then did reboot in recovery and did not work.
I have tried many time to do power with vol down and vol up... I see "cold-booting linux"... then KK, not recovery mode
I started another thread for this, not sure where the best place to discuss this is?
I recently bought a second hand TF700T that has been rooted with Katkiss 6.0 but it has numerous problems that I need to know which is the best way to resolve. This is what I have:
Model: TF700T
Android Version: 6.0.1
Kernel Version: 3.1.10 katkernel-tf700
Build: Katkiss-024.6.0.1
ClockworkMod Recovery v6.0.4.7
The problems I have are:-
1. It has no Play Store and I am able to download the apk file but 'can't read/open' so it won't install from download (yes I have allowed apps from unknown sources). I managed to pull the apk file using ADB but the Play Store simply opens and closes a white page.
2. If I go to settings there is a SuperSU – clicking on it I get 'Unfortunately, settings has stopped'. I don't think this should happen. I don't know how to check if Super SU Beta 2.52 is installed.
3. If I go to Accounts I have Personal (IMAP) and + Add Account where I only have Exchange and Personal (IMAP). So I can't seem to be able to select a Google Account.
Presently I have nothing on the tablet I need (i.e. no data I need to keep) so if I have to start again I am happy to do that but I'm just learning so saying 'flash the rom' or such is too vague for me at this stage. I'm also not sure what or how to get 'data as f2fs' if that is important.
If someone could assist with a clear step by step of how I might resolve these issues I'd be very grateful. Happy to provide any other info sought. Not sure if this was caused when the seller wiped his personal data before selling or what, he says Play Store was working, so don't know if he bungled the rooting or what.
I got your PM and first of all, congrats you did a good amount of reading and you are on the right track.
Your problems with Google account and Play Store are probably due to either the wrong gapps (Google apps) version or the previous owner did a wipe of /data and did not reflash properly. Yep, arm 6.0 is right, but it has to be the pico edition. Since you did buy the tablet used, it probably would be a good idea to start from scratch. At least you would then know that if something won't work, it's because of something you did.
And yes, I agree with the advice to flash the Kang TWRP recovery. I have no idea if CWM supports f2fs but I don't think so. Most people use TWRP as recovery - it's the right way to go.
So let's get you prepped:
Download the rom, gapps and SuperSU from the links in Tim's thread (first post) and put them on a microSD. http://forum.xda-developers.com/transformer-tf700/development/rom-t3282166
Then head here and download the flashable zip of the Kang TWRP recovery: http://forum.xda-developers.com/showpost.php?p=59299365&postcount=2
Also copy that to the microSD
Boot into CWM recovery, go to Install and navigate to the Kang TWRP zip.
To tell the truth I can't even remember if CWM supports the microSD but I think it does. If it doesn't you have to use adb to push the zip to internal memory and then flash it from there.
Anyway, flash the Kang TWRP and then reboot. Let it boot up, then turn the tablet off and boot via buttons (Power and Vol Down to get into bootloader, VolUp on flashing RCK) into recovery which should be TWRP at this time.
Go to Wipe > Format data > type "Yes" and go have a beer (did I mention the battery needs to be full before you start?). This will take 60 minutes plus and may look as if nothing happens but it does, don't mess with it!
Once that is done follow this guide to convert internal data to f2fs: http://forum.xda-developers.com/tra.../guide-convert-data-to-f2fs-twrp-2-8-t3073471
Start at step 4 and ignore any instructions related to data2sd/rom2sd.
Alright, now you got a squeaky clean tablet itching for a rom.
In TWRP go to Install > navigate to the microSD and select the rom zip. If you like, you can line up the other two files to be flashed right after the rom zip:
Touch: Add another zip, and repeat this for both the gapps and the supersu zips.
Or you flash them one by one - doesn't matter. But all 3 have to be flashed without rebooting in between and the rom has to be first!
Make sure "verify zip signature" is not checked, then swipe the button.
Have another beer
Once it's done, reboot to system and set up your new rom.
You definitely want to install the SuperSU app from the Play Store. You gain root by flashing the SuperSU zip, but you need the app to manage root.
If anything is unclear: Ask!
Have fun!
I'm up to the part where I get to have a beer...haaa. Wasn't all plain sailing. Having TWRP as an img file wasn't recognised on the sd card so I was unable to flash twrp that way. I managed to push twrp using ADB. (The small issue I had here originally was when I renamed the img file from say twrp-2.8.x.x-xxx.img to twrp.img (for ease of typing in adb) it was really twrp.img.img as it appears with a zip icon on my XP. After realising this it was straightforward after putting twrp.img into the adb folder and connecting the device and accessing the command prompt:
C:\adb>adb devices (to check I'm connected)
response:
List of devices attached
(numbers&letters here) device
C:/adb>adb reboot bootloader
This reboots the device into the bootloader and you hear the device buzz
C:/adb>fastboot flash recovery twrp.img
response
sending 'recovery' (7038kb)
Okay
writing 'recovery'
Okay
finished total time etc
then
c:/adb>fastboot reboot
rebooting....
I then used the power vol down buttons and yahoo I'm in TWRP and currently at the wipe data phase.
Can't tell you how much I appreciate this help and I'll repost a report after I get further along. Hope this helps others also.
Unexpected Clean Android waiting for a ROM
Beers were great. I finished the bit of 'convert internal data to f2fs' and thought when I rebooted, well don't know what I expected but 'squeaky clean tablet itching for a rom' wasn't a still present KatKiss rom logo start but that's what happened. Then I went to 'Install > navigate to the microSD and select the rom zip' and nothing on the SD card seemed to be recognised other than a self created 'LOST.DIR' directory so I copied the files into this directory ( Heh, at least it can see this directory). So I'm now in the process of installing KatKiss, Gapp 6 pico and SU User Beta.
If I'm on the wrong track here please let me know. Cheers
Paul;
No, you're doing good. You formatted /data, so did not touch /system where the rom lives. That's why your old room still boots. /system gets formatted during installation of the new rom = squeaky clean.
Sent from my Nexus 5X using Tapatalk
berndblb said:
No, you're doing good. You formatted /data, so did not touch /system where the rom lives. That's why your old room still boots. /system gets formatted during installation of the new rom = squeaky clean.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I've completed all the instructions - changed data to f2fs and then starting with the Katkiss, then Gapp pico and SuperSU (adding one zip after the other) and rebooted. Rebooted and device installed 73 apps and took me to a welcome screen with a language dropdown and a swipe button. I can access and change the language but the swipe button won't work so I'm locked on this screen. I went back to TWRP and pressed 'reboot' but what happened was the reboot button(located bottom right), settings button above it and the two bottom buttons on the left disappeared... so from there it wouldn't reboot. I had to hold the power button down to reboot and back in the flash screen but still can't get past that.
plato2 said:
I've completed all the instructions - changed data to f2fs and then starting with the Katkiss, then Gapp pico and SuperSU (adding one zip after the other) and rebooted. Rebooted and device installed 73 apps and took me to a welcome screen with a language dropdown and a swipe button. I can access and change the language but the swipe button won't work so I'm locked on this screen. I went back to TWRP and pressed 'reboot' but what happened was the reboot button(located bottom right), settings button above it and the two bottom buttons on the left disappeared... so from there it wouldn't reboot. I had to hold the power button down to reboot and back in the flash screen but still can't get past that.
Click to expand...
Click to collapse
Heck! I did not think we needed to check your bootloader if it had Katkiss on it, but now I think we do:
Boot into fastboot and read the tiny text top left. The part with 10.6.1...... is what we need
Bootloader problem now! More beer required....
berndblb said:
Heck! I did not think we needed to check your bootloader if it had Katkiss on it, but now I think we do:
Boot into fastboot and read the tiny text top left. The part with 10.6.1...... is what we need
Click to expand...
Click to collapse
OK, I went back to the wipe data bit and did it all again.... I noted that when installing the Katkiss, Gapps and SuperU zips I saw 2 lines:
checking for md5 file
skipping md5 check: No md5 file found
Have no idea if it matters or not....
OK the tiny writing at top on fastboot (why does this have to be so small....really).
Anyway it says:
Key Driver not found.. booting as
Android CardHU-User Bootloader <2.0 e> released by "ww_epad-10.6.1.14.10-2013601" A?3
It is hard to be exact with it that small so hope that helps, but the 10.6.1.14.10 is correct can't be as sure with the last numbers though.
Thinking about a solution
plato2 said:
OK, I went back to the wipe data bit and did it all again.... I noted that when installing the Katkiss, Gapps and SuperU zips I saw 2 lines:
checking for md5 file
skipping md5 check: No md5 file found
Have no idea if it matters or not....
OK the tiny writing at top on fastboot (why does this have to be so small....really).
Anyway it says:
Key Driver not found.. booting as
Android CardHU-User Bootloader <2.0 e> released by "ww_epad-10.6.1.14.10-2013601" A?3
It is hard to be exact with it that small so hope that helps, but the 10.6.1.14.10 is correct can't be as sure with the last numbers though.
Click to expand...
Click to collapse
I've done a bit of reading and I'm currently downloading ww_10_6_1_18_SDupdate.zip
I think my next step will be to unzip this file and find the T4_SDupdate file and put it on the sdmicro in root and boot into recovery. I'm guessing it will be located and the update begin. After that I'm not sure of what to expect. Will I have to go and flash twrp, wipe date, change to f2fs and install Katkiss,Gapps and SuperSU again? Will it matter if other files (TWRP, Katkiss, Gapps,SuperSU) are also on the microsd while this happens. If you could let me know if I'm on the right track that would be great.
plato2 said:
I've done a bit of reading and I'm currently downloading ww_10_6_1_18_SDupdate.zip
I think my next step will be to unzip this file and find the T4_SDupdate file and put it on the sdmicro in root and boot into recovery. I'm guessing it will be located and the update begin. After that I'm not sure of what to expect. Will I have to go and flash twrp, wipe date, change to f2fs and install Katkiss,Gapps and SuperSU again? Will it matter if other files (TWRP, Katkiss, Gapps,SuperSU) are also on the microsd while this happens. If you could let me know if I'm on the right track that would be great.
Click to expand...
Click to collapse
Sorry, that should be 22_10_26_1_18_SDupdate.zip
plato2 said:
Sorry, that should be 22_10_26_1_18_SDupdate.zip
Click to expand...
Click to collapse
Third time luck...(should be) ww_10_26_1_18_SDupdate.zip
plato2 said:
Third time luck...(should be) ww_10_26_1_18_SDupdate.zip
Click to expand...
Click to collapse
Don't do that!!
Whatever it is that is not firmware for the TF700!
You are on the latest bootloader, no reason to mess with it!!
---------- Post added at 09:29 AM ---------- Previous post was at 09:28 AM ----------
Give me some time, I'll get back to you
Sent from my Nexus 5X using Tapatalk
That was TF701 firmware you were thinking to flash. It is totally incompatible with your tablet and the T4 SD Update method works only with stock recovery. But all that aside....
Ok, what you experience is quite weird and I have no idea what caused it. Maybe a bad download maybe something went wrong during the flash - I have no idea...
So what is your situation now? Can you reboot from TWRP? Does the recovery work normally?
Because if not, that is the first thing you need to fix.
You may want to reflash TWRP anyway - just to be sure it did not get corrupted. You know how to flash in fastboot - excellent! Then let's do it that way.
Download from the first link for Kang TWRP 2.8.7.4. https://www.androidfilehost.com/?fid=24352994023705509
Look at the info under "Download information" on that page: You'll see the md5 checksum for that file. That is control value to make sure the file you downloaded is complete and not corrupted.
You'll need a small program like Hashtab on your PC to check the md5. Install it, then right click on a zip, go to Properties and there you'll see a new tab: FileHashes. Copy the string from the download page into the "Compare" box and it instantly tells you if the file you have on your PC matches the one on the server. TWRP has a feature that it will compare the md5 if you have it along with the zip in form of a small text file on your microSD. If it doesn't find a md5 it just skips the integrity check.
Your microSD - something else to check. That TWRP doesn't see the downloaded files unless they are in the LOST directory is totally crazy. How is that microSD formatted? You got another one you can use? One that actually works and does not add another question mark to this situation? If not, at least format the microSD to fat32 on your PC, load your files and then check if TWRP sees them. Also check the md5 AFTER copying the files to the card.....
Do that with all the files you downloaded.
So, first thing is to flash TWRP again. Then make sure it works, you can reboot from it etc.
Then just perform a quick wipe in TWRP. From Home select Wipe > swipe the button > done
Then reflash the rom zip, gapps and supersu on which you checked the md5.
Let me know how that goes.....
Thanks for that info. No I wasn't going to do anything stupid without you OKing it first.
I redownloaded Kang TWRP 2.8.7.4 and pushed it again successfully with adb no problem. I am still unable to reboot from bootloader using adb or pressing reboot... these problems weren't present prior to installing Katkiss, Gapps and SuperSU. Still frozen on front screen of rom. I put the twrp.img file onto the micro SD Card and tried to flash. It gives me an option to select staging which I didn't tick so it tells me no partitions selected for flashing. Didn't want to tick something and stuff it up. I think TWRP is OK as it did work fine before I installed the other 3 programs.
The micro SD is fine it's FAT32 formatted. The issue with the recovery program not seeing the zip files in the root dir was when I was using CWM - no longer a problem.
plato2 said:
Thanks for that info. No I wasn't going to do anything stupid without you OKing it first.
I redownloaded Kang TWRP 2.8.7.4 and pushed it again successfully with adb no problem. I am still unable to reboot from bootloader using adb or pressing reboot... these problems weren't present prior to installing Katkiss, Gapps and SuperSU. Still frozen on front screen of rom. I put the twrp.img file onto the micro SD Card and tried to flash. It gives me an option to select staging which I didn't tick so it tells me no partitions selected for flashing. Didn't want to tick something and stuff it up. I think TWRP is OK as it did work fine before I installed the other 3 programs.
The micro SD is fine it's FAT32 formatted. The issue with the recovery program not seeing the zip files in the root dir was when I was using CWM - no longer a problem.
Click to expand...
Click to collapse
There's some fundamental flaw in your thinking: You cannot flash the .img file in TWRP.
twrp_tf700t_kang_2.8.7.4.img - this file you have to flash in fastboot (fastboot flash recovery twrp_tf700t_kang_2.8.7.4.img)
twrp_tf700t_kang_2.8.7.4-signed.zip - this is the same recovery packaged into a flashable zip. This you can flash in recovery
I am still unable to reboot from bootloader using adb or pressing reboot... these problems weren't present prior to installing Katkiss, Gapps and SuperSU
Click to expand...
Click to collapse
You mean rebooting from recovery??? That sentence does not make sense. And something else is going on. Flashing a rom, gapps, supersu cannot have anything to do with your recovery not working properly. The recovery lives on it's own partition and boots from there.
Maybe time to take a break and retrace your steps. I cannot put my finger on it but somewhere you are doing something wrong.
Edit: Ha! Interesting! Just remembered that something changed in TWRP and yes, this latest version lets you flash an .img file to staging (from where it will get installed to it's proper partition during the next boot). I have no idea how solid this new feature is, so I'd still recommend falshing TWRP in fastboot.
But 2.8.7.4 works fine flashing Katkiss and associated files. Tried it myself this afternoon. All the components work. So the problem is most likely in the "how", not the "what".....
Sorry for the confusion. Really can't see what I may be doing wrong here. I followed exactly the same procedure as I did when I installed TWRP over CWM initially. I re-downloaded twrp_tf700t_kang_2.8.7.4.img , placed it in the adb folder and renamed it twrp.img. I then followed the same procedure I did originally:
C:\adb>adb devices (to check I'm connected)
response:
List of devices attached
(numbers&letters here) device
C:/adb>adb reboot bootloader
This reboots the device into the bootloader and you hear the device buzz
C:/adb>fastboot flash recovery twrp.img
response
sending 'recovery' (7038kb)
Okay
writing 'recovery'
Okay
finished total time etc
then
c:/adb>fastboot reboot
rebooting....
However, this time the response to the last command:
c:/adb>fastboot reboot
(waiting for device) and it hangs and the device doesn't reboot from recovery. However, all the other stuff before it is the same. Not sure what to try next.
plato2 said:
However, this time the response to the last command:
c:/adb>fastboot reboot
(waiting for device) and it hangs and the device doesn't reboot from recovery. However, all the other stuff before it is the same. Not sure what to try next.
Click to expand...
Click to collapse
Elaborate on this please.
You are in fastboot.
The command fastboot reboot does nothing?
Then what? Did you reboot manually?
You are not in recovery here, so i do not understand "the device does not reboot from recovery".....
Sorry, my lack of understanding. I suppose I mean I am in the bootloader which is where adb>reboot>bootloader puts me so that I can flash twrp.img. Then to get out of there and go back to the rom fastboot>reboot would put me back into the rom and I would get the response >rebooting. Now that doesn't happen it simply says (waiting for device)....So I have to reboot manually.
Just got home and playing around with it. I went into the bootloader and installed just the katkiss rom. It installed fine and then I clicked reboot and it rebooted no problem. But of course that doesn't give me any Play Store or SuperSU.... so there's still hope. So now I'm back in the bootloader and going to try the 3 together again and see what happens.Let you know shortly
Setup wizerd stopped - google play services stopped
plato2 said:
Just got home and playing around with it. I went into the bootloader and installed just the katkiss rom. It installed fine and then I clicked reboot and it rebooted no problem. But of course that doesn't give me any Play Store or SuperSU.... so there's still hope. So now I'm back in the bootloader and going to try the 3 together again and see what happens.Let you know shortly
Click to expand...
Click to collapse
So now when I install the katkiss, Gapps and SuperSU from TWRP and reboot I get 2 repeating messages Setup wizerd has stopped' and Google Play Services has stopped. It just goes from one to the other when I press OK....