Hi everyone, I think I've done a bad damage on my TF201. I was an happy user of [ROM]BAKED TF201 bb-8 (3-16-2013) with TWRP 2.5.0 as recovery, when today I decide to flash the [ROM][Apr 4][JB 4.2.1] AndroWook Prime Hairy Bean v2.11. Doing that I did flash before this file JB.4.2.1.Bootloader.and.partitions.zip. ROM was doing ok, so I decide than to flash via Terminal the TWRP 2.5.0, as the previous one was push me back with the 2.4.4.0. Unfortunately after booting into recovery is asking me the password that I don't remember, and now I am not able anymore to flash any ROM or restore any backup as the TWRP won't show me anything as is keep me asking for a password and when I ask to reboot is telling me that nor OS or SuperUser is available.... Is any solution for this mess that I've done?
Many thanks for the support, I am really desperate now!
EDIT: ok I did manage to resume the ROM, but is any way to recover the passwordto TWRP 2.5.0 recovery?
paura01 said:
Hi everyone, I think I've done a bad damage on my TF201. I was an happy user of [ROM]BAKED TF201 bb-8 (3-16-2013) with TWRP 2.5.0 as recovery, when today I decide to flash the [ROM][Apr 4][JB 4.2.1] AndroWook Prime Hairy Bean v2.11. Doing that I did flash before this file JB.4.2.1.Bootloader.and.partitions.zip. ROM was doing ok, so I decide than to flash via Terminal the TWRP 2.5.0, as the previous one was push me back with the 2.4.4.0. Unfortunately after booting into recovery is asking me the password that I don't remember, and now I am not able anymore to flash any ROM or restore any backup as the TWRP won't show me anything as is keep me asking for a password and when I ask to reboot is telling me that nor OS or SuperUser is available.... Is any solution for this mess that I've done?
Many thanks for the support, I am really desperate now!
EDIT: ok I did manage to resume the ROM, but is any way to recover the passwordto TWRP 2.5.0 recovery?
Click to expand...
Click to collapse
Go and read the disclaimer that is in big writing at the beginning of the hairy bean thread and then come back here and say what you have done wrong
not sure where you're talking about....
EDIT:
I am facing with this issue you posted here http://forum.xda-developers.com/showpost.php?p=40149294&postcount=8
after rebooting the tablet goes straight into recovery, still 2.5.0. The only way to load the rom is reboot the device via adb then with Volume - selecting androd icon and load it.
Quick note: after rebooting via adb I've got a message on top left position of the tablet as follow:
Key driver not found..Booting OS
Android cardhu-user boot loader <1.00 e> released by "WW_epad-10.6.1.2.8-20130225" A03
paura01 said:
not sure where you're talking about....
EDIT:
I am facing with this issue you posted here http://forum.xda-developers.com/showpost.php?p=40149294&postcount=8
after rebooting the tablet goes straight into recovery, still 2.5.0. The only way to load the rom is reboot the device via adb then with Volume - selecting androd icon and load it.
Quick note: after rebooting via adb I've got a message on top left position of the tablet as follow:
Key driver not found..Booting OS
Android cardhu-user boot loader <1.00 e> released by "WW_epad-10.6.1.2.8-20130225" A03
Click to expand...
Click to collapse
I'm talking about reading this section.
"READ EVERYTHING CAREFULLY. THIS IS NOT JUST FLASHING ANOTHER ROM
This Rom has been tested by many people but if you do not follow the instructions correctly or then go on to flash an incompatible TWRP you can brick yourself.
DO NOT INSTALL ANY OTHER RECOVERY WHILE USING THE NEW 4.2.1 BOOTLOADER, THEY ARE NOT COMPATIBLE AT THE MOMENT, THE ONE BUILT IN IS MODDED. USE THE DOWNGRADE ZIP TO TAKE YOU BACK TO 4.1.1 BOOTLOADER AND RECOVERY IF YOU NEED IT."
You ignored it and installed 2.5.0 even tho I had posted not to and now you are half bricked.
The post you just linked to is your only chance to recover. If one of the ways does not fix you in that post or you do not have nvflash backups there is nothing I can do sorry.
ok so if flashing either via Terminal or fastboot, would not replace the current TWRP 2.5.0, I am half screw then....
No I never manage to have the nvflash backups, the only backup I have is the one related to the previous ROM with TWRP 2.5.0 image, but of course I am not able to see it now.
Stupid question as I am not aware about it: is the nvflash backups related to a specific hardware or can it be use to any TF201 tablets?
Thanks for your tips
paura01 said:
ok so if flashing either via Terminal or fastboot, would not replace the current TWRP 2.5.0, I am half screw then....
No I never manage to have the nvflash backups, the only backup I have is the one related to the previous ROM with TWRP 2.5.0 image, but of course I am not able to see it now.
Stupid question as I am not aware about it: is the nvflash backups related to a specific hardware or can it be use to any TF201 tablets?
Thanks for your tips
Click to expand...
Click to collapse
Nvflash backups can only be used on the machine they were created on.
and of course do it now wouldn't be possible....
appreciate your help anyway, if you have maybe another idea is more than welcome!
would be possible in recovery with adb copy the ROM into the tablet and flash it?
paura01 said:
would be possible in recovery with adb copy the ROM into the tablet and flash it?
Click to expand...
Click to collapse
That isn't possible because you have the wrong TWRP on there for the bootloader and it can't mount any of the partitions it needs.
flumpster said:
That isn't possible because you have the wrong TWRP on there for the bootloader and it can't mount any of the partitions it needs.
Click to expand...
Click to collapse
... Too good to be true. I think I have to hope for a new TWRP or Hair release which may fix this half brick.
Thank you
Inviato dal mio Transformer Prime TF201 con Tapatalk 2
flumpster said:
That isn't possible because you have the wrong TWRP on there for the bootloader and it can't mount any of the partitions it needs.
Click to expand...
Click to collapse
... Too good to be true. I think I have to hope for a new TWRP or Hair release which may fix this half brick.
Thank you
Inviato dal mio Transformer Prime TF201 con Tapatalk 2
apparently you and I have the same problem: http://forum.xda-developers.com/showthread.php?t=2245136
any more idea for us?
I think we just need to hope for a new TWRP release and see if it would be flashable, otherwise stay in this half brick condition till new update
Related
My system directory seems to be missing. I've installed teamwin Recovery but am unable to mount the system drive. When I install the latest Cyanogen Mod nightly it appears to install but won't boot. All I've got is Recovery and Fastboot. Help!
So, I had it booting momentarily. Once I had it going I figured I would attempt to load Clockwork Mod Recovery and give it another go. Now I can't even get to the bootloader. Please tell me this isn't bricked!
DustL82 said:
So, I had it booting momentarily. Once I had it going I figured I would attempt to load Clockwork Mod Recovery and give it another go. Now I can't even get to the bootloader. Please tell me this isn't bricked!
Click to expand...
Click to collapse
We don't have enough information. What rom was you on? When you say you had it booting momentarily to where? What Cwm did you flash and how? What happens when you hold down volume down and power together from being off?
flumpster said:
We don't have enough information. What rom was you on? When you say you had it booting momentarily to where? What Cwm did you flash and how? What happens when you hold down volume down and power together from being off?
Click to expand...
Click to collapse
Here is the whole sequence of events...
1) I was on complete stock updated to the latest Asus OTA
2) I used the Asus unlock tool to unlock the bootloader
3) I wanted to gain root access so I tried the freshroot method here http://forum.xda-developers.com/showthread.php?t=1929189. This didn't work and it made my system directory not be found via fastboot.
4) I attempted to load CW Recovery 5.8.3.4 for the TF201 but it wouldn't open so I went with TWRP 2.3.1.0 (both were loaded via fastboot)
5) Once TWRP was working I flashed stock Asus version 10.4.2.17(US) and was able to boot into the welcome screen
6) I still wanted root and I noticed that my recovery image was no longer loading so I attempted to once again push CW Recovery via fastboot.
7) At this point the tablet turns on to the Asus splash screen and in the top left says "The Device is Unlocked". Holding Power + Volume Down lands me in the same spot.
Thank you again for the help!
DustL82 said:
Here is the whole sequence of events...
1) I was on complete stock updated to the latest Asus OTA
2) I used the Asus unlock tool to unlock the bootloader
3) I wanted to gain root access so I tried the freshroot method here http://forum.xda-developers.com/showthread.php?t=1929189. This didn't work and it made my system directory not be found via fastboot.
4) I attempted to load CW Recovery 5.8.3.4 for the TF201 but it wouldn't open so I went with TWRP 2.3.1.0 (both were loaded via fastboot)
5) Once TWRP was working I flashed stock Asus version 10.4.2.17(US) and was able to boot into the welcome screen
6) I still wanted root and I noticed that my recovery image was no longer loading so I attempted to once again push CW Recovery via fastboot.
7) At this point the tablet turns on to the Asus splash screen and in the top left says "The Device is Unlocked". Holding Power + Volume Down lands me in the same spot.
Thank you again for the help!
Click to expand...
Click to collapse
I have a really bad feeling about this. Can you show me where you got that Cwm from please?
flumpster said:
I have a really bad feeling about this. Can you show me where you got that Cwm from please?
Click to expand...
Click to collapse
Yes, I downloaded the Asus Transformer Prime Recovery image from clockworkmod.com/rommanager.
DustL82 said:
Yes, I downloaded the Asus Transformer Prime Recovery image from clockworkmod.com/rommanager.
Click to expand...
Click to collapse
I really have a bad feeling about this mate. The version you mentioned earlier came out at the end of may. Jellybean didn't come out until July. I don't think they released a version since then that supports the Jellybean bootloader and if you flash an ICS recovery onto a Jellybean bootloader you will hard brick your device.
If you cannot access the icons by holding down power and volume down for about 5 seconds while you are powered off then I am afraid it is hard bricked and will have to be returned to asus and have motherboard replaced.
I know it's no conciliation but there are posts everywhere saying not to use CWM on prime
flumpster said:
I really have a bad feeling about this mate. The version you mentioned earlier came out at the end of may. Jellybean didn't come out until July. I don't think they released a version since then that supports the Jellybean bootloader and if you flash an ICS recovery onto a Jellybean bootloader you will hard brick your device.
If you cannot access the icons by holding down power and volume down for about 5 seconds while you are powered off then I am afraid it is hard bricked and will have to be returned to asus and have motherboard replaced.
I know it's no conciliation but there are posts everywhere saying not to use CWM on prime
Click to expand...
Click to collapse
Unfortunately there is at least one post out there saying it will work. On that note, know of anyone who needs some spare parts?
DustL82 said:
Unfortunately there is at least one post out there saying it will work. On that note, know of anyone who needs some spare parts?
Click to expand...
Click to collapse
It can be repaired by asus. Ask them how much to fix. If it's too much these will sell on eBay as people want them for the screen etc.
Hello guys. First of all I want to apologize for my English , and the second thing is that I need your help. A couple days ago I tried to flash a custom rom with data2sd to my prime and I've made a mistake that bricked my tablet. I have updated the bootloader to 4.2.1 and I've installed an incompatible TWRP by mistake Now my tablet does not boot OS...only TWRP. The major problem that whatever I try to it gives me that E: unable to mount data(also cache, internal storage, staging) looks like my internal memory failed..and my sdcard is recognized as "system" folder in TWRP file manager. I can access bootloader but there are only 3 icons( recovery, Cold boot, wipe) but no fastboot. Can somebody help me solve this problem?:crying:
motorom said:
Hello guys. First of all I want to apologize for my English , and the second thing is that I need your help. A couple days ago I tried to flash a custom rom with data2sd to my prime and I've made a mistake that bricked my tablet. I have updated the bootloader to 4.2.1 and I've installed an incompatible TWRP by mistake Now my tablet does not boot OS...only TWRP. The major problem that whatever I try to it gives me that E: unable to mount data(also cache, internal storage, staging) looks like my internal memory failed..and my sdcard is recognized as "system" folder in TWRP file manager. I can access bootloader but there are only 3 icons( recovery, Cold boot, wipe) but no fastboot. Can somebody help me solve this problem?:crying:
Click to expand...
Click to collapse
With the 4.2.1 bootloader you are in fastboot as soon as those icons appear. You do not need to select anything.
Most people who have done what you have done are hard bricked but try and fastboot the correct twrp back onto the device.
It normally says sending and then writing but freezes straight after and you can't continue.
flumpster said:
With the 4.2.1 bootloader you are in fastboot as soon as those icons appear. You do not need to select anything.
Most people who have done what you have done are hard bricked but try and fastboot the correct twrp back onto the device.
It normally says sending and then writing but freezes straight after and you can't continue.
Click to expand...
Click to collapse
I've founded a tool WSG_UnBricker_V1.0.3 and I tried to use it. The result is not good at all. Power+ vol.down gives me the menu with the 3 icons but when I'm pushing one of them I'm getting a error "unrecoverable bootloader error(0x00000000)" this is it you think? Garbage is the best place for my Prime now?
motorom said:
I've founded a tool WSG_UnBricker_V1.0.3 and I tried to use it. The result is not good at all. Power+ vol.down gives me the menu with the 3 icons but when I'm pushing one of them I'm getting a error "unrecoverable bootloader error(0x00000000)" this is it you think? Garbage is the best place for my Prime now?
Click to expand...
Click to collapse
You have now killed it completely. I said to try and fastboot the correct twrp as that was your only chance.
Don't thow it in the garbage!
I have the same issue. First, did you enable nvflash? And if so do you still have your backup files? If you said yes to both of these questions you can still save your prime using Craig gomez's nvflash unbrick tutorial. I recommend you use the linux version's automated restore.
http://rootzwiki.com/topic/35086-guide-nvflash-general-users-guide-unbrickrecoverdowngradeupgrade-tf201/
Good luck!
blade2k11 said:
I have the same issue. First, did you enable nvflash? And if so do you still have your backup files? If you said yes to both of these questions you can still save your prime using Craig gomez's nvflash unbrick tutorial. I recommend you use the linux version's automated restore.
Good luck!
Click to expand...
Click to collapse
thank you for trying to help me but it looks like my Prime is bricked forever...I'm new in this things and I didn't enable nvFlash before messing up my device, and of course I don't have the required files to unbrick it. I will wait a little bit maybe a solution will appear after a while...if not then my Prime will be sold for parts on ebay(( I still can't believe that I killed it by making a stupid little mistake...
I thought I was installing an old rooted stock ROM that I had. Turns out it was an actual stock ROM. Now it won't boot after I tried doing a restore. I can get to the fastboot and TWRP recovery, but not sure what to do from here.
holmern said:
I thought I was installing an old rooted stock ROM that I had. Turns out it was an actual stock ROM. Now it won't boot after I tried doing a restore. I can get to the fastboot and TWRP recovery, but not sure what to do from here.
Click to expand...
Click to collapse
First things first. When you get into the bootloader what number do you see along the top left of the screen? It will start with a 9 or 10.
Then go into TWRP and tell me what the TWRP version number is along the top of the screen.
Then wait to get shouted at by someone who has nothing better to do because you have posted this in the wrong section
edit.. I only need answers to the first 2
flumpster said:
First things first. When you get into the bootloader what number do you see along the top left of the screen? It will start with a 9 or 10.
Then go into TWRP and tell me what the TWRP version number is along the top of the screen.
Then wait to get shouted at by someone who has nothing better to do because you have posted this in the wrong section
edit.. I only need answers to the first 2
Click to expand...
Click to collapse
Guess I should continue the post in Developer forum eh?
It says Android cardhu-user bootloader <1.00 e> released by "us_epad-10.4.2.15-20120917" A03. (I'm thinking im screwed if it tried flasing stock bootloader?
TWRP version is 2.2.2.1. I know its an old one. Haven't used the tablet in a while and was trying to get it back to stock type ROM before selling it. Any help would be greatly appreciated!
holmern said:
Guess I should continue the post in Developer forum eh?
It says Android cardhu-user bootloader <1.00 e> released by "us_epad-10.4.2.15-20120917" A03. (I'm thinking im screwed if it tried flasing stock bootloader?
TWRP version is 2.2.2.1. I know its an old one. Haven't used the tablet in a while and was trying to get it back to stock type ROM before selling it. Any help would be greatly appreciated!
Click to expand...
Click to collapse
You are on JB bootloader.
Grab the rom from here http://forum.xda-developers.com/showthread.php?t=1911024 and place it on your microsd card.
Go into twrp and wipe system, data, cache and dalvik.
Flash the rom linked above and see if that works.
flumpster said:
You are on JB bootloader.
Grab the rom from here http://forum.xda-developers.com/showthread.php?t=1911024 and place it on your microsd card.
Go into twrp and wipe system, data, cache and dalvik.
Flash the rom linked above and see if that works.
Click to expand...
Click to collapse
I tried downloading a new Rom, but for some reason it seems like it won't mount the SD card. It just shows it as empty. Is there anything I have to do to mount it? I was going to try to install ADB and go the push route to get access to the storage.
flumpster said:
You are on JB bootloader.
Grab the rom from here http://forum.xda-developers.com/showthread.php?t=1911024 and place it on your microsd card.
Go into twrp and wipe system, data, cache and dalvik.
Flash the rom linked above and see if that works.
Click to expand...
Click to collapse
Woohoo! Got the new Rom and managed to get adb so work from a Mac so I could push the file over. All good now. Thank you so much for your help!
Sent from my GS4
holmern said:
Woohoo! Got the new Rom and managed to get adb so work from a Mac so I could push the file over. All good now. Thank you so much for your help!
Sent from my GS4
Click to expand...
Click to collapse
Please teach me how to do it ?
I have same situation with you.
Thanks.
I had to install ADB on Mac since my PC wouldn't recognise the prime when I was in recovery. One I installed it on the Mac.. I booted to recovery, pushed the Rom that was linked here to the prime and did a wipe/install.
Sent from my SGH-M919 using Tapatalk 4
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!
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.