This is for 201 user running KatKiss android 5.0 !!!!!
DEV THREAD
KatKiss-5.0_TF201T_014b_signed.zip
The original thread this spinoffed from: http://forum.xda-developers.com/transformer-tf300t/development/rom-t2932783
Couple of issues I've had as a newbie to flashing Androids, I hope I get these right. I already wrote about these in the Q&A, but I think we could start the thread with these:
1) You must upgrade you're bootloader. The last OTA was 4.1.1 (?), you need 4.2.1. Without upgrading, the device will try to boot but after a minute or two, it will reboot over and over again. I used instructions from CROMBi-kk http://forum.xda-developers.com/showthread.php?t=2773812#4. EDIT: or just follow lj50036's instructions below in #3
2) Do not install K.A.T apps. Or if you had it in your KatKiss 4.4, do not restore it from the backups. I had lagginess, short and permanent freezes, reboots. After removing it, TF201 has worked like a charm. EDIT: May have been a coincidence...
The boost in stock OTA Android from Asus is huge. The device responds immediately to touch and is way faster than I could have ever hoped. Thank you timduru and others involved!
lj50036 said:
UPGRADE INSTRUCTIONS, STEP BY STEP
This may help
Starting from a stock bootloader V 10.4.2.18
What you will need
Woking fastboot & adb / SDcard optional
TWRP for a 201 = twrp_tf201t.blob
@ne0zone75 TWRP for the 300 = ne0zone75_tf300t.blob
HairyBean BL & TWRP: This is effectively turn your 201 into a 300 <---- which is a flashable zip inside the zip that you downloasd
All 3 of the above file are in a zip in the Download section @ the top of every page of the thread ...... THIS ZIP IS NOT FLASHABLE...Your must unzip it to get to the real files !!! The name of this zip is
upgrade_tf201_to_tf300t.zip
foo 201 ROM zip
A fully charged tablet
All the above files in the same directory as your fastboot.exe (if using windows) In your home folder on linux....
The process
Lets start with the TWRP recovery for the 201, let flash it with fastboot...
Power your tablet off and with the [ VOL DOWN & POWER ] buttons boot the tablet into the bootloader
Once there [ VOL DOWN ] untill the green box is on the USB ICON then [ VOL UP ] to select fastboot
Let make sure your PC can see your tablet with this command.
Code:
fastboot devices
Code:
fastboot -i 0x0b05 flash recovery twrp_tf201t.blob
Then
Code:
fastboot -i 0x0b05 reboot-bootloader
[ VOL UP ] ON RCK to enter recovery
Once in TWRP check to see if adb is working...
Code:
adb devices
Ok now that we know that is working let go ahead and push the HairyBean BL onto the tablet
Code:
adb push HairyBean_Bootloader_TWRP2.5.zip /sdcard
Now under the install tab in TWRP fine the folder and flash it....
reboot once it has fishined..If ask to install SuperUser say NO..........
LET THE BLUE BAR FILL !!!!!!!!! Once it has finished it will reboot into Hairybean TWRP....
Once booted into recovery, run this command to boot into fastboot
Code:
adb reboot-bootloader
You will see that the USB icon is missing now, this is good... If you still see the USB icon DON'T go to the next step
Now lets flash @ne0zone75 TWRP recovery
Code:
fastboot -i 0x0b05 flash recovery ne0zone75_tf300t.blob
Once that has finished let reboot into bootloader
Code:
fastboot -i 0x0b05 reboot-bootloader
Now enter recovery....
Make sure its verison 2.7.1.0
Go to Wipe////Format Data////Type yes
This can take up to 90 mins to format
DO NOT INTERRUPT THE FORMAT !!!!!!!
Now lets push foo.zip onto your tab
Code:
adb push foo.zip /sdcard
Find it under the install tab and flash it..
REBOOT into android, first boot can take up to 15 minutes
Click to expand...
Click to collapse
Thx Josh
apartypooper said:
2) Do not install K.A.T apps. Or if you had it in your KatKiss 4.4, do not restore it from the backups. I had lagginess, short and permanent freezes, reboots. After removing it, TF201 has worked like a charm.
Click to expand...
Click to collapse
I doubt that it was the app causing that,
but Lollipop is only supported since the version 2.0.1 of the K.A.T app,
so if you want it to work that's definitely the one you need to use, and not restore an older version.
For the freezes that were discussed in the previous thread, I've noticed it happens alot when using the browser .
random reboots
Big fan of all the developers keeping the prime alive, thankyou very much.
Very glad this Q&A has been opened, not got many posts so cant post on developer parts.
Usually find answers by reading, but realized thats just not enough any more, got to help the developers, if they are still willing to help us.
As it is written everywhere that most of the developers no longer have a tf201.
So ive been reading up on getting logcats, kmsg etc.
If their is anything i can post here, please let me know.
Been getting a few random reboots myself.
Thanks again
goosebickel said:
Big fan of all the developers keeping the prime alive, thankyou very much.
Very glad this Q&A has been opened, not got many posts so cant post on developer parts.
Usually find answers by reading, but realized thats just not enough any more, got to help the developers, if they are still willing to help us.
As it is written everywhere that most of the developers no longer have a tf201.
So ive been reading up on getting logcats, kmsg etc.
If their is anything i can post here, please let me know.
Been getting a few random reboots myself.
Thanks again
Click to expand...
Click to collapse
After one of these random reboot can you post a last_kmsg plz...
Let the tab boot after said random reboot and run this command from terminal ....
Code:
adb pull /proc/last_kmsg
Thx Josh
lj50036 said:
After one of these random reboot can you post a last_kmsg plz...
Let the tab boot after said random reboot and run this command from terminal ....
Code:
adb pull /proc/last_kmsg
Thx Josh
Click to expand...
Click to collapse
It wouldn't let me upload as txt file, so i stuck it in a zip
Hope it helps
timduru said:
I doubt that it was the app causing that,
but Lollipop is only supported since the version 2.0.1 of the K.A.T app,
so if you want it to work that's definitely the one you need to use, and not restore an older version.
Click to expand...
Click to collapse
You're probably right. I installed KatKiss a week ago and it had been unstable and laggy until I froze K.A.T with link2sd. I unfroze it now and everything seems fine. *knock knock*
The device froze twice a moment ago (before unfreezing K.A.T). According to logcat, the device registered pushing power buttons on both the tablet and keyboard, but the screen stayed frozen. I was able to restart the launcher (nova) from adb shell, but it froze again soon after. I now switched back to launcher3, lets see if works better
goosebickel said:
It wouldn't let me upload as txt file, so i stuck it in a zip
Hope it helps
Click to expand...
Click to collapse
The first thing that needs to happen is I need to work on a zImage + ramdisk ......
I am working on this as we speak ..... :good:
Thx Josh
camera logcat
Camera boots up fine but crashes when photo is taken.
Got a logcat if it helps
Thanks again for all the help
goosebickel said:
Camera boots up fine but crashes when photo is taken.
Got a logcat if it helps
Thanks again for all the help
Click to expand...
Click to collapse
Well I found this ....
The service starting ......
Code:
I/CameraService( 8115): CameraService started (pid=8115)
I/CameraService( 8115): Loaded "NVIDIA Development Platform Camera HAL" camera module
And the cam not liking this ....
Code:
E/NvOmxCamera( 8115): Could not get config for CONFIG_LENS_PHYSICAL_ATTR (80001001)
Lets see where this goes ..... :good:
Thx Josh
Bootlooping at this point.. Sometimes I don't get the last message but anyways it would not boot.
Maybe I don't have a compatible bootloader? I'm coming from PA 4.5, I'll give this a look tomorrow and see if I can get what's wrong
Enviado desde mi XT1068
zodiark said:
Bootlooping at this point.. Sometimes I don't get the last message but anyways it would not boot.
Maybe I don't have a compatible bootloader? I'm coming from PA 4.5, I'll give this a look tomorrow and see if I can get what's wrong
Enviado desde mi XT1068
Click to expand...
Click to collapse
Well what is your bootloader version ?
That pic looks like the preinit from crombi ?
I am working on things as fast as I can .....
Let me put something together ...
Thx Josh
Yes, it's because of my bootloader, I need to update it to the 4.2 version.
I'll try to update it this afternoon, thanks for your help and your work!
Enviado desde mi XT1068
Will twrp 2.7 work in flashing this ROM, comparability pack, and gapps
Itzamistry said:
Will twrp 2.7 work in flashing this ROM, comparability pack, and gapps
Click to expand...
Click to collapse
Yep that will do it for now ...
I am working on somethings ....
Should know more a bit later today ...
Thx Josh
Upgraded bootloader and reinstalled.. WOW! That's all I can say. It's fast, feels snappy, just amazing! It's like a new tablet.
Again thanks to everyone who made this ROM, very good job!
Has anyone tried using the ROM's encryption feature? I've had issues where the password/pin is not recognized in the past. Wondering if its a result of the custom 201/301 bootloader and recovery. Right now on tf201 with Twrp geass 2.7, geass v7 kernel and katkiss v36. Had PW issue with twrp 2.8.2
Sent from my Nexus 4 using Tapatalk
lj50036 said:
Yep that will do it for now ...
I am working on somethings ....
Should know more a bit later today ...
Thx Josh
Click to expand...
Click to collapse
Im up for testing if you need a guinnie pig.
Related
I have been running hariybean 2.31 for quite some time but saw some kitkat based roms are now available so I thought I would try on out. As a precursor, I had to upgrade my TWRP to the 2.6.3 version that supports KK. I did the upgrade using the terminal emulator method and it seems to have installed correctly but now, when I start recovery, it asks for a password to contiue. If you cancel out of it, then you do not have access to the partitions and I assume they are encrypted.
I cannot find a password listed anywhere, nor did i set one on my machine. I am rooted currently and unlocked. I also tried to downgrade TWRP back to the 2.5.0.0 version but i cant seem to do that either, it seems to instal, but when I go back into recovery, it is still the 2.6.3.0 version.
Can anybody help me? want to either get the password, disable the password (without loosing my data) or downgrade back to a version that will not request a password.
Detailed steps to accomplish any of the above would be greatly appriceiated!
jismail said:
I have been running hariybean 2.31 for quite some time but saw some kitkat based roms are now available so I thought I would try on out. As a precursor, I had to upgrade my TWRP to the 2.6.3 version that supports KK. I did the upgrade using the terminal emulator method and it seems to have installed correctly but now, when I start recovery, it asks for a password to contiue. If you cancel out of it, then you do not have access to the partitions and I assume they are encrypted.
I cannot find a password listed anywhere, nor did i set one on my machine. I am rooted currently and unlocked. I also tried to downgrade TWRP back to the 2.5.0.0 version but i cant seem to do that either, it seems to instal, but when I go back into recovery, it is still the 2.6.3.0 version.
Can anybody help me? want to either get the password, disable the password (without loosing my data) or downgrade back to a version that will not request a password.
Detailed steps to accomplish any of the above would be greatly appriceiated!
Click to expand...
Click to collapse
This is all down to a lack of reading mate. What does the disclaimer say in the hairybean thread under the big red writing saying "read everything carefully"
flumpster said:
This is all down to a lack of reading mate. What does the disclaimer say in the hairybean thread under the big red writing saying "read everything carefully"
Click to expand...
Click to collapse
Couldn't he use the NVFlash Guide and put the Flatline_TF300.img back onto the device?
feyerbrand said:
Couldn't he use the NVFlash Guide and put the Flatline_TF300.img back onto the device?
Click to expand...
Click to collapse
Does he have his nvflash backups? I didn't notice him post that.
He needs to try the following and try to get back on the correct TWRP for that bootloader before downgrading.
http://forum.xda-developers.com/showpost.php?p=40149294&postcount=8
If neither of them work for him then he can still be fixed but I'm gonna need to wipe the machine.
flumpster said:
Does he have his nvflash backups? I didn't notice him post that.
He needs to try the following and try to get back on the correct TWRP for that bootloader before downgrading.
http://forum.xda-developers.com/showpost.php?p=40149294&postcount=8
If neither of them work for him then he can still be fixed but I'm gonna need to wipe the machine.
Click to expand...
Click to collapse
I'm going to be honest with you, the reason I was interested is I made the bonehead mistake of not downgrading to 4.1 before attempting to flash the KK twrp. Looks like the link you sent fixed the recovery just fine without needing NVFlash (At least in my case) if only I knew how to actually develop roms better. I want a 4.4.2 Linaro AOSP ROM with ART optimization (Or Vanir) for the Prime on the 4.2 bootloader... that would be pretty awesome.
feyerbrand said:
I'm going to be honest with you, the reason I was interested is I made the bonehead mistake of not downgrading to 4.1 before attempting to flash the KK twrp. Looks like the link you sent fixed the recovery just fine without needing NVFlash (At least in my case) if only I knew how to actually develop roms better. I want a 4.4.2 Linaro AOSP ROM with ART optimization (Or Vanir) for the Prime on the 4.2 bootloader... that would be pretty awesome.
Click to expand...
Click to collapse
It really isn't as hard as everyone thinks if you know your way around linux a little bit. Glad you're fixed anyway and bloody read next time
Thanks for the replies so far. I now have made things even worse by using wipe in TWRP and now the OS is gone I have tried using the fastboot -I 0x0b05 flash recovery twrp.blob as suggested and it says it is writing it, but when it is done, it restarts into the same TWRP 2.6.3.0 version everytime. I have no data on the tablet that isn't already backed up (but I don't have NVflash) so I don't care how deep It needs to be formatted to get it back online again.
Any further suggestions or steps to take? I have ADB and Fastboot access but that seems to be all......
sheesh... all I wanted to do was try out KK
jismail said:
Thanks for the replies so far. I now have made things even worse by using wipe in TWRP and now the OS is gone I have tried using the fastboot -I 0x0b05 flash recovery twrp.blob as suggested and it says it is writing it, but when it is done, it restarts into the same TWRP 2.6.3.0 version everytime. I have no data on the tablet that isn't already backed up (but I don't have NVflash) so I don't care how deep It needs to be formatted to get it back online again.
Any further suggestions or steps to take? I have ADB and Fastboot access but that seems to be all......
sheesh... all I wanted to do was try out KK
Click to expand...
Click to collapse
Follow this http://forum.xda-developers.com/showthread.php?t=2409602
Where is says to use the TF300 stock blob just use the prime stock blob instead.
flumpster said:
Follow this http://forum.xda-developers.com/showthread.php?t=2409602
Where is says to use the TF300 stock blob just use the prime stock blob instead.
Click to expand...
Click to collapse
I finally got it back.
Did this list of commands:
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\blob
fastboot -i 0x0B05 reboot
and that allowed me to overwrite the TWRP 2.6.3.0 and thus unencrypt the storage finally and then I just reinstalled the Harirybean zip again.
Thanks so much for all the help!
flumpster said:
It really isn't as hard as everyone thinks if you know your way around linux a little bit. Glad you're fixed anyway and bloody read next time
Click to expand...
Click to collapse
I do know a bit around linux, I have been using Ubuntu for about 3 years but not super familiar with things. I know basic commands in terminal and I know how to Google really well haha. Any chance you could PM me a list of starter guides because I really am interested in doing new development for the Prime. I am not getting a tablet anytime soon... due to money concerns and the fact that I just like the transformer series.
feyerbrand said:
I do know a bit around linux, I have been using Ubuntu for about 3 years but not super familiar with things. I know basic commands in terminal and I know how to Google really well haha. Any chance you could PM me a list of starter guides because I really am interested in doing new development for the Prime. I am not getting a tablet anytime soon... due to money concerns and the fact that I just like the transformer series.
Click to expand...
Click to collapse
I would advise not starting with a rom but starting with an app to get yourself used to using toolchains etc.
Take a look at compiling your own version of Gotham XBMC to get you started, the instructions on that are pretty good and straight forward.
https://github.com/xbmc/xbmc/blob/master/docs/README.android
flumpster said:
I would advise not starting with a rom but starting with an app to get yourself used to using toolchains etc.
Take a look at compiling your own version of Gotham XBMC to get you started, the instructions on that are pretty good and straight forward.
https://github.com/xbmc/xbmc/blob/master/docs/README.android
Click to expand...
Click to collapse
Awesome I will get cracking on that over the weekend. I will see how that treats me and if it goes well I will let you know and see if I could be your padawan learner and hopefully build a vanilla Linaro AOSP Rom for the 4.2 bootloader some day.
The blob file helped a lot and I'm back with a working TWRP! Great work - thanks again!
But I'm kind of scared and confused right now, regarding KitKat ROMs. Do I really need NVFlash?
I guess the right road 2 kitkat would be:
1. downgrade my bootloader
2. install flatline & nvflash
3. install cw recovery?
4. install kitkat roms?
There is also KitKat TWRP - is this the right way?
Like I said - I'm super confused. ^^
wolwe said:
The blob file helped a lot and I'm back with a working TWRP! Great work - thanks again!
But I'm kind of scared and confused right now, regarding KitKat ROMs. Do I really need NVFlash?
I guess the right road 2 kitkat would be:
1. downgrade my bootloader
2. install flatline & nvflash
3. install cw recovery?
4. install kitkat roms?
There is also KitKat TWRP - is this the right way?
Like I said - I'm super confused. ^^
Click to expand...
Click to collapse
You are on Hairybean 2.31 at the moment? If so there are instructions somewhere in the hairybean thread on how to do nvflash backups while on there. Search is down at the moment so I can't find it for you.
flumpster said:
You are on Hairybean 2.31 at the moment? If so there are instructions somewhere in the hairybean thread on how to do nvflash backups while on there. Search is down at the moment so I can't find it for you.
Click to expand...
Click to collapse
AndroWook Hairybean 2.31 yessir!
I think I found the tutorial: http://forum.xda-developers.com/showthread.php?t=2407248&page=102
flumpster said:
You are on Hairybean 2.31 at the moment? If so there are instructions somewhere in the hairybean thread on how to do nvflash backups while on there. Search is down at the moment so I can't find it for you.
Click to expand...
Click to collapse
eh, ok is there a guide how to unbrick my device with these files? ^^
this one seems to be very near but I'm not so sure:
http://forum.xda-developers.com/showthread.php?p=48948717&highlight=bricksafe+img#post48948717
wolwe said:
eh, ok is there a guide how to unbrick my device with these files? ^^
this one seems to be very near but I'm not so sure:
http://forum.xda-developers.com/showthread.php?p=48948717&highlight=bricksafe+img#post48948717
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1927818&highlight=nvflash
flumpster said:
http://forum.xda-developers.com/showthread.php?t=1927818&highlight=nvflash
Click to expand...
Click to collapse
Allright, thanks a lot.
I'm now on ParanoidAndroid KitKat Rom via Voyagers TWRP Recovery. I'm curios how KitKat will perform on my TF201 over time.
Thanks for your help flumpster!
I have a TF201 and have loved it. Earlier this year after cracking the screen I decided to unlock, root and play around a bit. Installed CM11. I liked it and didn't have an issues with it. I went back to a stock version 2 days ago. I have quickly seen how much better performance was on CM11. But now there are some other KK roms out there, and I read on a thread you can actually install TF300 roms on a TF201 as well. What ROM do you suggest I try next? Crombi-X, Crombi-kk, CM11 (newer build) or another.
JoanneDisFan said:
I have a TF201 and have loved it. Earlier this year after cracking the screen I decided to unlock, root and play around a bit. Installed CM11. I liked it and didn't have an issues with it. I went back to a stock version 2 days ago. I have quickly seen how much better performance was on CM11. But now there are some other KK roms out there, and I read on a thread you can actually install TF300 roms on a TF201 as well. What ROM do you suggest I try next? Crombi-X, Crombi-kk, CM11 (newer build) or another.
Click to expand...
Click to collapse
If you head over to the Crombi-kk thread there is a step by step to upgrade to be able to run a 4.4.x rom ....
We do have some small issue like the CAM not working for the last 2 releases, BUT we got it fixed and the next
release will have it working ...
I dont think that you would be unhappy with any of the tf300 ROMs available for your 201 after you follow the steps
in post number 4 here on this thread http://forum.xda-developers.com/showthread.php?t=2773812
It would open up a whole new set of roms for your flashing pleasure..
Thx Josh & Team CROMBI-kk
Thanks Josh.
I'm learning towards either the Cromi-X or Crombi-KK. Are both still being developed? Is there a benefit to sticking with the TF201 version rather than the tf300 version?
I like several of the asus apps. Can I install those on any of the KK versions?
Hubby was also wondering which kernel would give the best wifi and speed?
JoanneDisFan said:
Thanks Josh.
I'm learning towards either the Cromi-X or Crombi-KK. Are both still being developed? Is there a benefit to sticking with the TF201 version rather than the tf300 version?
I like several of the asus apps. Can I install those on any of the KK versions?
Hubby was also wondering which kernel would give the best wifi and speed?
Click to expand...
Click to collapse
I would say that Cromi-X is close to the end of is development life, but having said that if there are bugs I know @sbdags would take care of them
WIth this ROM everything would be just like it is now fully supported dock all the asus apps.. etc .....
With Crombi-kk is still very much under development. But things are not quite as refined in this one, the dock has some small bugs
and there is an Asus app zip that can be flashed and will give you the stock Asus back
If you decide to go with Cromi-X i would choose _that's kernel for sure ...
If going with Crombi-kk I think that Grimlocks kernel is a very good one ...
I think that answers all your questions , nice post thx for that :good:
and always Thx Josh
So I've decided to go with Crombi-KK for the 201. I'm following the install instructions on the link you posted but running into a problem. I have the BL installed at TWRP 2.7 but when I try and do ads push of the crombi I get an error: device not found but if I do fastboot devices I do find my device.
JoanneDisFan said:
So I've decided to go with Crombi-KK for the 201. I'm following the install instructions on the link you posted but running into a problem. I have the BL installed at TWRP 2.7 but when I try and do ads push of the crombi I get an error: device not found but if I do fastboot devices I do find my device.
Click to expand...
Click to collapse
are you running the adb command from recovery ?
lj50036 said:
are you running the adb command from recovery ?
Click to expand...
Click to collapse
Not sure. I try to do it at the screen that gives me recovery as well at android to boot into. How would I get into adb in twrp?
JoanneDisFan said:
Not sure. I try to do it at the screen that gives me recovery as well at android to boot into. How would I get into adb in twrp?
Click to expand...
Click to collapse
Can you boot into twrp ?
lj50036 said:
Can you boot into twrp ?
Click to expand...
Click to collapse
Yes I can get TWRP up.
JoanneDisFan said:
Yes I can get TWRP up.
Click to expand...
Click to collapse
Found ADB sideload under advanced. Used sideload rather than push and it's now moving
JoanneDisFan said:
Found ADB sideload under advanced. Used sideload rather than push and it's now moving
Click to expand...
Click to collapse
Okay I take that back. It load 2-3% then I get the error: failed to write data ' protocol fault <No status>'
JoanneDisFan said:
Found ADB sideload under advanced. Used sideload rather than push and it's now moving
Click to expand...
Click to collapse
Well we need to get adb and fastboot working ....
Have you ever used G+ to do screenshare ?
Let me know
Thx Josh
No never have done a screen share. I'm starting with making sure I have the current version of adb. Downlaoding SDK at the moment. Fastboot worked fine.
JoanneDisFan said:
No never have done a screen share. I'm starting with making sure I have the current version of adb. Downlaoding SDK at the moment. Fastboot worked fine.
Click to expand...
Click to collapse
If you would like any help with getting adb working shoot me a hangouts at
[email protected]
thx Josh
EDIT
Hey XDA, This one has me doing some reading, The driver would install and the adb devices would show the device, but when we tried to push it would give us a "failed protocol"
I am sure this is a windows issue and I am just not the best with windows. Yes we had the CMD opened as admin, and everything looks good ....
I am doing some more reading myself....
Thx Josh
A quick update whats been happening. Tried to install via sdcard only to have that not mount. So went to fastboot and loaded my stock boot loader. Went back into TWRP and it could find my sdcard. Installed from the SDcard the HB BL, then installed TWRP 2.7, then install crombi-kk. I'm still doing the install, but it's working.
The current recovery version is TWRP 2.7.0.0 by Voyager.
It happened after failure of installing ParanoidAndroid 4.5-BETA2 ROM.
Now My tf210 always skips the fastboot mode and goes into recovery directly.
And I lost all my partition information except /system.
It also can't read external sdcard.
I tried "adb sideload" command in my PC, but installations always show failure because of no partitions.
I spent a whole morning to search any related threads, but............. :crying:
Please help! Thanks!!
Thanks lj50036.
I follow your post http://forum.xda-developers.com/transformer-prime/help/guide-t2864946
Although some commands I couldn't run as your example, me tf201 now survived.
I am struggling to install a proper ROM in which the camera could work, but it is a good start.
Thanks again!!
Hsu said:
Thanks lj50036.
I follow your post http://forum.xda-developers.com/transformer-prime/help/guide-t2864946
Although some commands I couldn't run as your example, me tf201 now survived.
I am struggling to install a proper ROM in which the camera could work, but it is a good start.
Thanks again!!
Click to expand...
Click to collapse
Great to see you are on the right path..
Let me know if you need any help along the way ...
Thx Josh
Q&A for [ROM][STOCK][JB 4.2.2] ASUS MeMO Pad 8 (ME180A-WW-3.1.0.42)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][STOCK][JB 4.2.2] ASUS MeMO Pad 8 (ME180A-WW-3.1.0.42). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
My asus memo pad 8 not booting and not reach to check usb debuging...
When conecct usb fastboot mode device not found in win 8.1
Help me please
Sorry my bad english
hhzznn said:
My asus memo pad 8 not booting and not reach to check usb debuging...
When conecct usb fastboot mode device not found in win 8.1
Help me please
Sorry my bad english
Click to expand...
Click to collapse
Hello there,
If not using the "adbsetup" drivers or the ones off the ASUS website (sorry, couldn't find the ASUS drivers when I looked ), use one of the above. If using one and still not connecting, try the other option.
Also, check your USB ports to make sure you are not connecting via a USB 3.x standard. Android (or at least some Android devices) don't like those.
If all else fails, you may need a Linux build
Hope this provides a head start.
Sent from my LG-D520 using XDA Free mobile app
help me please
hello
my asus memo pad 8 not booting becuse im delete odex file in system/app after rooting..now device not booting any way!wipe data and wipe cash dont answer and not booting yet!!
in fast boot mode unlock oem not answering...
please help me ...
email :[email protected]
hhzznn said:
hello
my asus memo pad 8 not booting becuse im delete odex file in system/app after rooting..now device not booting any way!wipe data and wipe cash dont answer and not booting yet!!
in fast boot mode unlock oem not answering...
please help me ...
email :[email protected]
Click to expand...
Click to collapse
Looks you got a little further... :good:
From what I remember when I followed the guide, there was no feedback (nothing on the screen, and tablet remains black) on when you issue the unlock commands - which by the way, are:
Code:
fastboot oem unlock61646
fastboot oem unlockD696E
Then, reboot the bootloader and install CWM (first line may be substituted with rebooting into fastboot by hand):
Code:
fastboot reboot-bootloader
fastboot flash recovery recovery_cwm.img
fastboot flash misc misc_reboot-recovery.img
fastboot reboot
You shouldn't get a write-protect error this time around. Hope this helps.
By the way, your SKU is WW version, right? If not, my ROM may not help you (without going the long way around of instead of flashing the ROM, copying the odex files back into /system/app using CWM's ADB push command). Just a warning. If you are not WW, and insist on flashing anyway, I would highly recommend a nandroid backup (and probably copied) to MicroSD to protect your original (broken) ROM.
help me
my pad is sku = ww
in the fastboot mode i type fastboot oem unlock61646 and i get asnwer okey and finish but when type fastboot oem unlockD696E i get answer oem admunlock not request
help me please
hhzznn said:
my pad is sku = ww
in the fastboot mode i type fastboot oem unlock61646 and i get asnwer okey and finish but when type fastboot oem unlockD696E i get answer oem admunlock not request
help me please
Click to expand...
Click to collapse
The latter may have been for the 10" model - cannot remember. Try rebooting into fastboot now and see if CWM install takes.
Sent from my LG-D520 using XDA Free mobile app
joel.maxuel said:
The latter may have been for the 10" model - cannot remember. Try rebooting into fastboot now and see if CWM install takes.
Sent from my LG-D520 using XDA Free mobile app
Click to expand...
Click to collapse
the code:fastboot unlock oem61646 worked but fastboot oemD696E not working
in stock recovery i cant install rom.zip
and in fastboot when install recovery cwm answer bootloader lock
any offer for me?
---------- Post added at 09:14 AM ---------- Previous post was at 09:07 AM ----------
**you may need a Linux build **
i have a linux base ,, may you help me??
hhzznn said:
**you may need a Linux build **
i have a linux base ,, may you help me??
Click to expand...
Click to collapse
May not be as important now (if you got fastboot working in windows), but what distro do you have? I am familiar with Debian, Ubuntu, and their derivates.
Sent from my LG-D520 using XDA Free mobile app
joel.maxuel said:
May not be as important now (if you got fastboot working in windows), but what distro do you have? I am familiar with Debian, Ubuntu, and their derivates.
Sent from my LG-D520 using XDA Free mobile app
Click to expand...
Click to collapse
i have ubuntu....what should i do?
hhzznn said:
i have ubuntu....what should i do?
Click to expand...
Click to collapse
In a terminal...
apt-get install android-tools-fastboot
...would be a good start. You may need to register the device vendor in your configuration, which I can research later if...
fastboot devices
...lists nothing. Hope this helps.
Sent from my LG-D520 using XDA Free mobile app
Hi...I was having issues with my ME180A (WW variant) where the OTA update would never take (I had the tablet rooted) so when I finally found this thread and the associated stock ROM install instructions I thought I would give it a go to see if I could clean up the mess that I must have made rooting and de-bloating my tablet. I got adb and fastboot install on my win 8.1 machine with no problems, got CWM (from your link) installed on my tablet with no issues but when I tried to flash your original rom onto my tablet it would get partially through the install and then I would get
set_metadata_recursive; some changes failed
error in /data/media/0/K00L_Back_To_Stock_Untouched_Orig.zip
status 7
and the install would fail. I think this has somehow screwed up my bootloader because now my tablet constantly reboots into CWM no matter what I do. When the tablet is connected to my Windows machine, the drivers don't get loaded so ADB and fastboot just sit at "waiting for device" after I try some of the different commands. I'm familiar with flashing ROMs onto my phones and have never had an issue but I have had a lot of difficulties with this tablet. Do you have any advice to solve the bootloader and ROM flashing issues?
Thanks in advance for any assistance that can be provided.
Syncline said:
Hi...I was having issues with my ME180A (WW variant) where the OTA update would never take (I had the tablet rooted) so when I finally found this thread and the associated stock ROM install instructions I thought I would give it a go to see if I could clean up the mess that I must have made rooting and de-bloating my tablet. I got adb and fastboot install on my win 8.1 machine with no problems, got CWM (from your link) installed on my tablet with no issues but when I tried to flash your original rom onto my tablet it would get partially through the install and then I would get
set_metadata_recursive; some changes failed
error in /data/media/0/K00L_Back_To_Stock_Untouched_Orig.zip
status 7
and the install would fail. I think this has somehow screwed up my bootloader because now my tablet constantly reboots into CWM no matter what I do. When the tablet is connected to my Windows machine, the drivers don't get loaded so ADB and fastboot just sit at "waiting for device" after I try some of the different commands. I'm familiar with flashing ROMs onto my phones and have never had an issue but I have had a lot of difficulties with this tablet. Do you have any advice to solve the bootloader and ROM flashing issues?
Thanks in advance for any assistance that can be provided.
Click to expand...
Click to collapse
Hmmmm, I guess this is why I made two files, but the other may have similar problems because of this issue.
I will see if I can change the updater program. In the meantime, pop the other back-to-stock file onto MicroSD, reload CWM, and try that one. Report back to me in any case.
UPDATE:
If the above fails, try this one as well.
joel.maxuel said:
Hmmmm, I guess this is why I made two files, but the other may have similar problems because of this issue.
I will see if I can change the updater program. In the meantime, pop the other back-to-stock file onto MicroSD, reload CWM, and try that one. Report back to me in any case.
UPDATE:
If the above fails, try this one as well.
Click to expand...
Click to collapse
Joel,
I tried to flash the other back-to-stock file as you recommended however the end result was the same.
set_metadata_recursive: some changes failed
E:Error in /external_sd/K00L_Back_To_Stock_Re-Perm-Linked.zip
(Status 7)
Installation aborted.
Are there any other things that you can think of that I can try to get this issue fixed? And thanks for all your assistance, it is appreciated.
Syncline said:
Joel,
I tried to flash the other back-to-stock file as you recommended however the end result was the same.
set_metadata_recursive: some changes failed
E:Error in /external_sd/K00L_Back_To_Stock_Re-Perm-Linked.zip
(Status 7)
Installation aborted.
Are there any other things that you can think of that I can try to get this issue fixed? And thanks for all your assistance, it is appreciated.
Click to expand...
Click to collapse
So the third file I created (in my post update) replaces the updater-binary that would be causing issues with that particular CWM.
Third times the charm... :fingers-crossed:
joel.maxuel said:
So the third file I created (in my post update) replaces the updater-binary that would be causing issues with that particular CWM.
Third times the charm... :fingers-crossed:
Click to expand...
Click to collapse
Things worked great that time with the flash working and the tablet rebooting properly however now it is asking for a password to decrypt storage and this is the first time I've ever seen this. Any thoughts?
Syncline said:
Things worked great that time with the flash working and the tablet rebooting properly however now it is asking for a password to decrypt storage and this is the first time I've ever seen this. Any thoughts?
Click to expand...
Click to collapse
Were you encrypted before?
Could do is a nandroid of the data partition and then factory reset. You will have to set your apps up by hand again, but it is better than that message.
Sent from my MeMO Pad 8"
joel.maxuel said:
Were you encrypted before?
Could do is a nandroid of the data partition and then factory reset. You will have to set your apps up by hand again, but it is better than that message.
Sent from my MeMO Pad 8"
Click to expand...
Click to collapse
No I wasn't encrypted before but from what I read it seems to involve a failure to mount the DATA partition correctly, and the Android OS erroneously assumes it's encrypted. I'm not overly concerned about setting up apps by hand, I do have a titanium backup of my apps and data. As I'm still at work, I can't do too much playing around on my tablet. I don't have access to my personal computer that has all my tools like adb, fastboot, etc. until the work day is done. I've said it a couple of times, but I truly appreciate the assistance that you've provided.
UPDATE: After booting back into CWM, doing a factory reset and a format of the /data partition seems to have done the trick. I'm back into my tablet and currently updating all the pre-installed apps that require it. One more quick question Joel, you mention that the ROM is rooted and I do have SuperSU installed, however when I run the app it tells me there is no SU binary installed and SuperSU cannot install it, can I just install the latest version of a flashable SuperSU zip with CWM to fix this?
Syncline said:
UPDATE: After booting back into CWM, doing a factory reset and a format of the /data partition seems to have done the trick. I'm back into my tablet and currently updating all the pre-installed apps that require it. One more quick question Joel, you mention that the ROM is rooted and I do have SuperSU installed, however when I run the app it tells me there is no SU binary installed and SuperSU cannot install it, can I just install the latest version of a flashable SuperSU zip with CWM to fix this?
Click to expand...
Click to collapse
That's an interesting side effect...never had that happen before.
You can try it, and let me know. Hopefully your CWM is still kicking around, or else you will have to reinstall via fastboot. Or alternatively, just re-root normally (like with Kingo).
By the way, before you do that, does /system/xbin/su exist? Or what you could answer, is you could download Voodoo OTA RootKeeper and report back which values are not checked off. I think SuperSU update.zip places the su binary, nothing else. But we shall see.
Sorry Joel, I didn't see your reply before I flashed the SuperSU zip but it did work, my tablet is rooted again.
Welcome to Twrp 3.0.0.0 for our Zenwatch 2's
This release I was able to flash the recovery, flash the supersu zip, and flash some others, so far I have not encountered our wild soft brick madness.
Thanks to @acbka for showing me how to get into log files, essentially helping me figure out why the partitions were not mounting correctly when I compiled and recompiled.
Here is TWRP 3.0.0.0
Directions:
Get into fastboot, either by enabling adb by enabling developer options going into settings, about, and taping the Build number 8 times, and going back, down to developer options and enable ADB Debugging.
Then you can type into your CMD or terminal adb reboot-bootloader or by powering down by holding the button or power down in settings, when the screen goes black, repress and hold the button and swipe the screen from the upper left down to the lower right and that should bring up the ASUS logo with CSC Fastboot Mode! on the screen
continue to boot the recovery by typing fastboot flash recovery twrp3.img
OR load up your tethered twrp and flash the image under that.
Hope you guys enjoy! So far I have not encountered soft bricks so it should be safe and sound
thank you, will test now
---------- Post added at 09:21 PM ---------- Previous post was at 09:01 PM ----------
Works perfectly, my zenwatch 2 is now rooted
thank you, you`re amazing
Thank you very much! I hope this will be one of the first steps into advanced development for our watches! Does this work for WI502Q? But what's a benefit of rooting this watch?
okaay3D said:
Thank you very much! I hope this will be one of the first steps into advanced development for our watches! Does this work for WI502Q? But what's a benefit of rooting this watch?
Click to expand...
Click to collapse
That im not sure, it might, wouldnt hurt to fastboot boot it and see if itll start twrp. I have the 501
Root will go with modifying the Momentum kernel so you wont have much lag on the watch, and any other root modifications that can go with it, like maybe xposed?
Next step in development is fixing twrp so it can be flashed, then maybe modifying the wear os? Or maybe porting some stuff
T10NAZ said:
As far as I understand people are able to get backups of their watch in order to preserve OTA's before rooting
Click to expand...
Click to collapse
I want to test it. But how do I backup my watch and restore it to get updates? And is there something like a KNOX-counter to tell whether the device was modified?
matze19999 said:
Works perfectly, my zenwatch 2 is now rooted
thank you, you`re amazing
Click to expand...
Click to collapse
what did u flash to get root? the one twrp offers (if this one does)? the one xda tv featured for 5.0.1 wear http://www.xda-developers.com/root-android-wear-5-0-1-xdatv/ ? or just the newest non-systemless supersu.zip used for phones? with a phone i would just flash away anything. but im a bit hestitant on the watch yet. couldnt find clear info yet.
Awesome! Got supersu flashed and was able to use Advanced Settings to disable some of the built-in bloatware apps. I'll have to try out the kernel but I'm currently at work and don't want to spend all day messing around with my watch (well... I want to, but I like not getting fired).
4RK4N said:
what did u flash to get root? the one twrp offers (if this one does)? the one xda tv featured for 5.0.1 wear http://www.xda-developers.com/root-android-wear-5-0-1-xdatv/ ? or just the newest non-systemless supersu.zip used for phones? with a phone i would just flash away anything. but im a bit hestitant on the watch yet. couldnt find clear info yet.
Click to expand...
Click to collapse
I do have the 5.0.1 wear downloaded and installed! And as far as i know, Its working ok
okaay3D said:
I want to test it. But how do I backup my watch and restore it to get updates? And is there something like a KNOX-counter to tell whether the device was modified?
Click to expand...
Click to collapse
You can tell twrp to preserve the system protection, back every single thing up that you can in the twrp option, push that backup to your computer, and then you can disable system protection. twrp itself wont do anything, however playing with options will modify the watch.
OR you can fastboot pull things off the watch, the system.img and boot.img yourself, in case the ones uploaded in my general thread didnt have the protection enabled.
If you want to hang tight until 1.4 comes out, that can be a good thing too
And im not sure if there is something like that on the watch. I have not seen anything about it before
My attempt was a failure on my WI502Q. I got the following messages. And, OP, how do you pull system.img from a device through fastboot? I thought you needed root permission to do that through adb.
"
C:\adb\zw2>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.381s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.834s
"
Thanks for this! I was losing hope on any development for this watch but now we have the most crucial component to modifying anything on android, a custom recovery. Going to perform a backup, root and flash your custom kernel you kindly released as well!
T10NAZ said:
Hello everyone, I have been working hard last night to make twrp run on our watches, and this I think is a good representation on what itll be like with actual development going on
As far as I understand people are able to get backups of their watch in order to preserve OTA's before rooting, and I was able to flash some zips and kernels successfully, and I fixed the UI to look better and actually usable on the watch
Also, I was able to flash this puppy, and I got android wear to boot with it flashed, however most of the time, it goes haywire and only boots into recovery. Same thing applies, this shall be a Tethered recovery only until I know why its going crazy.
As always, problems can arise on your watch, so be careful!
read the entire instructions, This is a known way to get system protection off, and to flash zips/kernels when need be. Do not flash please.
Here is the link to the updated twrp
Get into fastboot, either by enabling adb by enabling developer options going into settings, about, and taping the Build number 8 times, and going back, down to developer options and enable ADB Debugging.
Then you can type into your CMD or terminal adb reboot-bootloader or by powering down by holding the button or power down in settings, when the screen goes black, repress and hold the button and swipe the screen from the upper left down to the lower right and that should bring up the ASUS logo with CSC Fastboot Mode! on the screen
continue to boot the recovery by typing fastboot boot recovery.img like the other one.
I also have a kernel underway if people would like to try it out and test it in the next couple days
Click to expand...
Click to collapse
What are the Advantages of installing TWRP in Zenwatch 2 WI501Q..???
does it allow to uninstall stock apps..!!
yash92duster said:
What are the Advantages of installing TWRP in Zenwatch 2 WI501Q..???
does it allow to uninstall stock apps..!!
Click to expand...
Click to collapse
it could lead to that, yea, since this is the only root method basically, it adds a few extra steps to do it
can we root with regular supersu .zip, or do we need a special build for wear devices?
slothdabski said:
can we root with regular supersu .zip, or do we need a special build for wear devices?
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B3zB2zRyWlLBNmhwSmNBUEp1SVU/view?usp=sharing there ya go. dunno if the regular supersu works. havent tried that out. this one does. and alrdy has a busybox installer wear app included which u need anyway sooner or later.
there is no supersu manager app in it though like on phones. apps requiring root just have it. tested advanced settings so far for disabling built-in stuff and a reboot option. but maybe there is a supersu-wear.apk somewhere?
not my link. taken from here: http://forum.xda-developers.com/showpost.php?p=65759835&postcount=14 he took it from the G watch R forums iirc.
zenwatch2
hi dear freind
after the flash twrp recovery
after the wipe
my watch was brick and hang on asus logo
help me plase
mehdi.ahmadi said:
hi dear freind
after the flash twrp recovery
after the wipe
my watch was brick and hang on asus logo
help me plase
Click to expand...
Click to collapse
Let me know the steps you took from when you downloaded it, to when it sits on the asus logo, and do you have the 502 or the 501 watch?
mehdi.ahmadi said:
after the flash twrp recovery
Click to expand...
Click to collapse
guess that means he flashed it. now his watch is bricked. not that it hasent been mentioned NOT to flash it just fastboot boot ...
flash the stock images via fastboot or tethered (NOT flashed) twrp and you should get your watch working again.
4RK4N said:
what did u flash to get root? the one twrp offers (if this one does)? the one xda tv featured for 5.0.1 wear http://www.xda-developers.com/root-android-wear-5-0-1-xdatv/ ? or just the newest non-systemless supersu.zip used for phones? with a phone i would just flash away anything. but im a bit hestitant on the watch yet. couldnt find clear info yet.
Click to expand...
Click to collapse
I flashed this zip file
https://drive.google.com/file/d/0B3zB2zRyWlLBNmhwSmNBUEp1SVU/view
matze19999 said:
I flashed this zip file
https://drive.google.com/file/d/0B3zB2zRyWlLBNmhwSmNBUEp1SVU/view
Click to expand...
Click to collapse
found it about 2 weeks ago somewhere here on xda and alrdy linked it to several ppl here in the thread.
but thx