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!
Related
Okay so I received an Asus Transformer Prime tf201 yesterday. This morning I was able to unlock it, root it, and then I wanted to install the latest nightly of CM10 (24th). After I saw that it was indeed rooted I booted into twrp and in Wipe I did Factory Reset, System, Internal Storage (wanted to get rid of the pictures, etc. from previous owner). I had CM10 latest nightly and gapps both on my External SD Card so I knew I wasn't removing those.
Anyway after clicking on Install and then Using external SD I selected the zip of CM10 and swiped to confirm flash. It does well for about 2 or 3 minutes (the blue bar even shows progress) and then it comes up with the message E:Unable to mount '/staging'.
Please please tell me I did not mess up my Prime when I just got it???!!! Anyone that can help please help as soon as possible as I am really wanting to play with this after all the fantastic reviews I have heard. You would have my eternal gratitude and if it is not wrong to do this I will even donate via PayPal to the person that can help me "fix" my Prime.
Please KNOW I have been looking for answers to this for HOURS today and still haven't found anything to help me. I am really hoping some genius on XDA can help me.
alias4ever said:
Okay so I received an Asus Transformer Prime tf201 yesterday. This morning I was able to unlock it, root it, and then I wanted to install the latest nightly of CM10 (24th). After I saw that it was indeed rooted I booted into twrp and in Wipe I did Factory Reset, System, Internal Storage (wanted to get rid of the pictures, etc. from previous owner). I had CM10 latest nightly and gapps both on my External SD Card so I knew I wasn't removing those.
Anyway after clicking on Install and then Using external SD I selected the zip of CM10 and swiped to confirm flash. It does well for about 2 or 3 minutes (the blue bar even shows progress) and then it comes up with the message E:Unable to mount '/staging'.
Please please tell me I did not mess up my Prime when I just got it???!!! Anyone that can help please help as soon as possible as I am really wanting to play with this after all the fantastic reviews I have heard. You would have my eternal gratitude and if it is not wrong to do this I will even donate via PayPal to the person that can help me "fix" my Prime.
Please KNOW I have been looking for answers to this for HOURS today and still haven't found anything to help me. I am really hoping some genius on XDA can help me.
Click to expand...
Click to collapse
Did you check in twrp under the mounts button? I don't have my prime with me atm but I know there is a mounts section either on the first screen or under advanced may be....
Gage_Hero said:
Did you check in twrp under the mounts button? I don't have my prime with me atm but I know there is a mounts section either on the first screen or under advanced may be....
Click to expand...
Click to collapse
Yeahup I tried mounting everything and then unmounting everything to try and get it to work. What should be mounted/unmounted and selected on either SD Card or Internal? THANKS!
alias4ever said:
Yeahup I tried mounting everything and then unmounting everything to try and get it to work. What should be mounted/unmounted and selected on either SD Card or Internal? THANKS!
Click to expand...
Click to collapse
Mine, the radio button for external is on, you could try the terminal under advanced button...command would be something like su then enter and then mount /staging or something like that.... you may want to check the command exactly, my terminal skills are limited...
alias4ever said:
Yeahup I tried mounting everything and then unmounting everything to try and get it to work. What should be mounted/unmounted and selected on either SD Card or Internal? THANKS!
Click to expand...
Click to collapse
Probably running TRWP 2.3.x.x, right? Some others had this same problem with the TF300 and switched back to TWRP 2.2.2.1 and their ROM flashed just fine. Might be worth a shot.
tedr108 said:
Probably running TRWP 2.3.x.x, right? Some others had this same problem with the TF300 and switched back to TWRP 2.2.2.1 and their ROM flashed just fine. Might be worth a shot.
Click to expand...
Click to collapse
Isn't 2.3 for the JB bootloader and 2.2 for ics though?
Gage_Hero said:
Isn't 2.3 for the JB bootloader and 2.2 for ics though?
Click to expand...
Click to collapse
No, there is a 2.3 for both ics and jb bootloaders ... I THINK that 2.2 was ics only (can't remember for sure). If he was loading the CM10 nightly, he should have had an ics bootloader, or it would not have run.
---------- Post added at 04:16 PM ---------- Previous post was at 04:12 PM ----------
Gage_Hero said:
Isn't 2.3 for the JB bootloader and 2.2 for ics though?
Click to expand...
Click to collapse
You do bring up a good point, though ... if his TFP had a JB OTA, he could have the jb bootloader! Alias, you need to check these types of things out before moving forward.
tedr108 said:
No, there is a 2.3 for both ics and jb bootloaders ... I THINK that 2.2 was ics only (can't remember for sure). If he was loading the CM10 nightly, he should have had an ics bootloader, or it would not have run.
---------- Post added at 04:16 PM ---------- Previous post was at 04:12 PM ----------
You do bring up a good point, though ... if his TFP had a JB OTA, he could have the jb bootloader! Alias, you need to check these types of things out before moving forward.
Click to expand...
Click to collapse
I had the JB OTA before starting I do know that. Would have kept it if I didn't love CM so much! So would I just install twrp 2.2 through fastboot then like I did the 2.3.1.0 that I have now? Or is there another way I can do this? Thank you BOTH for your help! It is much appreciated! :good:
alias4ever said:
I had the JB OTA before starting I do know that. Would have kept it if I didn't love CM so much! So would I just install twrp 2.2 through fastboot then like I did the 2.3.1.0 that I have now? Or is there another way I can do this? Thank you BOTH for your help! It is much appreciated! :good:
Click to expand...
Click to collapse
If you had the JB bootloader before, then you surely still have it. You would not change your bootloader by flashing a CM10 nightly ROM. The only way that I know of for you to go back to an ICS bootloader is with nvflash. If nvflash was not on your TFP when you got it, you won't be getting it anytime soon, because it cannot be installed with a JB bootloader on your TFP.
Which TWRP 2.3.1 did you load? The JB version?
The CM10 nightlies are not currently compatible with a JB bootloader, so you had no hope of running it. That may very well have caused your staging error, but I am not sure. Since you apparently have a JB bootloader, you would have to flash an appropriate ROM, like Craig Gomez' (here). But, only the JB version of TWRP 2.3.1 will work for you, as far as I know. So, I'm thinking you must have loaded the correct one.
I cannot be 100% sure that you have the JB bootloader. I hope you are sure that your TFP was updated to JB by an Asus update (OTA).
If I were you, I'd make a plan of action and post it here. Be patient and wait for a response, before moving forward. Good luck with this.
alias4ever said:
I had the JB OTA before starting I do know that. Would have kept it if I didn't love CM so much! So would I just install twrp 2.2 through fastboot then like I did the 2.3.1.0 that I have now? Or is there another way I can do this? Thank you BOTH for your help! It is much appreciated! :good:
Click to expand...
Click to collapse
the only way back to an ics bootloader it through nvflash... if you didn't do nvflash before you started with JB then you are stuck using jb roms only I think.....you could try hairy bean .....
tedr108 said:
If you had the JB bootloader before, then you surely still have it. You would not change your bootloader by flashing a CM10 nightly ROM. The only way that I know of for you to go back to an ICS bootloader is with nvflash. If nvflash was not on your TFP when you got it, you won't be getting it anytime soon, because it cannot be installed with a JB bootloader on your TFP.
Which TWRP 2.3.1 did you load? The JB version?
The CM10 nightlies are not currently compatible with a JB bootloader, so you had no hope of running it. That may very well have caused your staging error, but I am not sure. Since you apparently have a JB bootloader, you would have to flash an appropriate ROM, like Craig Gomez' (here). But, only the JB version of TWRP 2.3.1 will work for you, as far as I know. So, I'm thinking you must have loaded the correct one.
I cannot be 100% sure that you have the JB bootloader. I hope you are sure that your TFP was updated to JB by an Asus update (OTA).
If I were you, I'd make a plan of action and post it here. Be patient and wait for a response, before moving forward. Good luck with this.
Click to expand...
Click to collapse
Okay let's see if I can get this is all right. I have The JB version of TWRP 2.3.1. As for running a different ROM I tried the Unofficial one you listed and it still gives me the Unable to mount 'staging/' error. It first says it is verifying the signature then update package, then it says Updating partition details and that is when it comes to the staging error. :crying:
I am 110% positive that my TFP was updated to JB by the Asus update (OTA). Thanks again for the suggestions hopefully someone out there will suggest something.
What about doing the PRIME FULL WIPE that someone suggests here: http://forum.xda-developers.com/showthread.php?t=1670824 Then trying to install the Unofficial CM10 with the JB Bootloader? Anyone know if this would work?
alias4ever said:
Okay let's see if I can get this is all right. I have The JB version of TWRP 2.3.1. As for running a different ROM I tried the Unofficial one you listed and it still gives me the Unable to mount 'staging/' error. It first says it is verifying the signature then update package, then it says Updating partition details and that is when it comes to the staging error. :crying:
I am 110% positive that my TFP was updated to JB by the Asus update (OTA). Thanks again for the suggestions hopefully someone out there will suggest something.
What about doing the PRIME FULL WIPE that someone suggests here: http://forum.xda-developers.com/showthread.php?t=1670824 Anyone know if this would work?
Click to expand...
Click to collapse
I wouldn't try the full wipe... what I would try is the fix permissions button under advanced.... failing that... I would try fastboot install of twrp 2.3 again (instructions on the twrp OP).... it is like you don't have rights to write to the staging partition...
Read this thread... this guy was in the same boat... page 2 post 19 is where he fixed it....
http://forum.xda-developers.com/showthread.php?t=1942927&highlight=unable+to+mount+staging&page=2
@Alias -- I was really hoping the JB bootloader ROMs would do it for you.
This right here is excellent advice from Gage_Hero:
Gage_Hero said:
I wouldn't try the full wipe... what I would try is the fix permissions button under advanced.... failing that... I would try fastboot install of twrp 2.3 again (instructions on the twrp OP).... it is like you don't have rights to write to the staging partition...
Click to expand...
Click to collapse
If this does not work, I am at a loss of how to recreate the Staging partition (and perhaps others), but there is probably a way.
Gage_Hero said:
I wouldn't try the full wipe... what I would try is the fix permissions button under advanced.... failing that... I would try fastboot install of twrp 2.3 again (instructions on the twrp OP).... it is like you don't have rights to write to the staging partition...
Read this thread... this guy was in the same boat... page 2 post 19 is where he fixed it....
http://forum.xda-developers.com/showthread.php?t=1942927&highlight=unable+to+mount+staging&page=2
Click to expand...
Click to collapse
You are an ABSOLUTE GENIUS! I remember reading that post of the guy in the same boat and honestly did not think it would work for me because I kept trying to install the different ROM's but it WORKED! Thank you, thank you, THANK YOU to you and everyone else for their suggestions! @Gage, can I send you a little thank you on PayPal??? Thank you so MUCH AGAIN! I can't thank you enough...
Now do I dare flash the CM10 Unofficial with the JB Boatloader through GooManager??? :silly:
alias4ever said:
You are an ABSOLUTE GENIUS! I remember reading that post of the guy in the same boat and honestly did not think it would work for me because I kept trying to install the different ROM's but it WORKED! Thank you, thank you, THANK YOU to you and everyone else for their suggestions! @Gage, can I send you a little thank you on PayPal??? Thank you so MUCH AGAIN! I can't thank you enough...
Now do I dare flash the CM10 Unofficial with the JB Boatloader through GooManager??? :silly:
Click to expand...
Click to collapse
Glad to get you up and running again just do yourself a favor before you try cm10.... make a backup... or 2 I never used cm on my tab but did it on my phone.... when I restored... I had to do it twice... not sure if that is the case with the prime or not ... but if it is a JB bootloader then you should be okay... I like flashing through twrp though .. never did a rom through goo... but I am sure it works...
I need a little more help now. I went to boot into TWRP last night and I just got the dead Andy. Does that mean that putting this stock JB back on my TFP I have lost my TWRP recovery?
My TFP is rooted though as I have SU in my app drawer and I installed Titanium Backup just fine. I just wanted to make a couple of backups of my TFP (one to save on my PC and one to save on my TFP's External SD. So my question is can I reinstall my TWRP through Fastboot like I did before even with it rooted? First time I did it I followed these instructions:
http://www.youtube.com/watch?v=-pW05Jf87dg&feature=plcp
But upon further reading it states that people have had problems installing JB ROMs with using the 2.3 or 2.3.1 version so should I install the 2.2 version? Please someone help me yet again possibly??? THANKS!
alias4ever said:
I need a little more help now. I went to boot into TWRP last night and I just got the dead Andy. Does that mean that putting this stock JB back on my TFP I have lost my TWRP recovery?
My TFP is rooted though as I have SU in my app drawer and I installed Titanium Backup just fine. I just wanted to make a couple of backups of my TFP (one to save on my PC and one to save on my TFP's External SD. So my question is can I reinstall my TWRP through Fastboot like I did before even with it rooted? First time I did it I followed these instructions:
http://www.youtube.com/watch?v=-pW05Jf87dg&feature=plcp
But upon further reading it states that people have had problems installing JB ROMs with using the 2.3 or 2.3.1 version so should I install the 2.2 version? Please someone help me yet again possibly??? THANKS!
Click to expand...
Click to collapse
I think people have had issues installing 2.2 on the JB bootloader I would fastboot install 2.3.1 there is no reason it shouldn't work..... I think there is some disconnect between twrp and some of the jb roms as some devs are including twrp in their install like Mr.Wookie over at team wookie.....
Gage_Hero said:
I think people have had issues installing 2.2 on the JB bootloader I would fastboot install 2.3.1 there is no reason it shouldn't work..... I think there is some disconnect between twrp and some of the jb roms as some devs are including twrp in their install like Mr.Wookie over at team wookie.....
Click to expand...
Click to collapse
Okay so I went ahead and have redone TWRP 2.3.1 via Fastboot. I then did a backup of my ROM twice onto my External SD card. After that I did a a Factory Reset through TWRP of course and then installed the Unofficial CM10 with JB Bootloader. I still got the E:can not mount '/staging' but I went ahead and installed the Gapps that was listed on the thread as well and then wiped davlik cache and regular cache. Rebooted and I am VERY HAPPY to say it FINALLY worked this time!
I was ecstatic to see that CyanogenMod symbol come up. I made sure to wait 10 minutes to let the ROM settle before doing anything and it looks very nice!
I am confused as to why it worked the second time or even worked with the staging error as well when it didn't last time. Maybe because I didn't do the wipe Internal in TWRP? Who knows all I know is my Asus is working wonderfully and I am SO HAPPY to have it back! Thank you again everyone for all your help, I LOVE THIS FORUM! :laugh: :good:
alias4ever said:
Okay so I went ahead and have redone TWRP 2.3.1 via Fastboot. I then did a backup of my ROM twice onto my External SD card. After that I did a a Factory Reset through TWRP of course and then installed the Unofficial CM10 with JB Bootloader. I still got the E:can not mount '/staging' but I went ahead and installed the Gapps that was listed on the thread as well and then wiped davlik cache and regular cache. Rebooted and I am VERY HAPPY to say it FINALLY worked this time!
I was ecstatic to see that CyanogenMod symbol come up. I made sure to wait 10 minutes to let the ROM settle before doing anything and it looks very nice!
I am confused as to why it worked the second time or even worked with the staging error as well when it didn't last time. Maybe because I didn't do the wipe Internal in TWRP? Who knows all I know is my Asus is working wonderfully and I am SO HAPPY to have it back! Thank you again everyone for all your help, I LOVE THIS FORUM! :laugh: :good:
Click to expand...
Click to collapse
Good to hear.... not sure if your aware or not but with a decent backup ( I do one everytime I think I am going to try something foolish) even if you do a wipe, as long as you can reach twrp you can restore the prime to it's state before you started messing with it....
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
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
So my friend decided to try to update my tablet and i was on Hariybean 2.31 and he installed twrp that wasn't compatible and now i cannot mount anything in the recovery and it only boots to the recovery i can still get adb from the remove menu and i can adb restart bootloader and access fast boot but every time i try to flsh anything it locks up fastboot says that i am on 10.6.1.27. anyone with any knoloege please help.
Edit:
Follow Flumpsters method below ...
the isc or the jelly bean on also i have gotten the hairbeany recover back on but i dont have permission to do anything. keeps asking for password.?
SAJdroid said:
Goto twrp download 2.5.0.0 version n flash from fast boot. Install hairy bean again by following the instructions.
Once u are able to successfully load the rom. Goto recovery n flash the downgrade bootloader which can be found at the bottom of hairy bean thread. Now you can flash any rom compatible on 4.1 bootloader.
Click to expand...
Click to collapse
Mate you have to stop telling people this. This is the second thread I have seen you say it In. Hairy bean uses the 4.2 bootloader, flashing 2.5 twrp from their site for the prime is just asking to hard brick the device.
Official twrp will not work on a 4.2 bootloader, he would not be able to do anything in it. It would have all partitions locked and he would be completely stuck and it would ask for a password.
http://forum.xda-developers.com/showpost.php?p=40149294&postcount=8
http://forum.xda-developers.com/showthread.php?t=2409602
edit.. Just in case that sounded a bit harsh it wasn't meant to. I am just trying to stop people getting in worse situations.
flumpster said:
Mate you have to stop telling people this. This is the second thread I have seen you say it In. Hairy bean uses the 4.2 bootloader, flashing 2.5 twrp from their site for the prime is just asking to hard brick the device.
Official twrp will not work on a 4.2 bootloader, he would not be able to do anything in it. It would have all partitions locked and he would be completely stuck and it would ask for a password.
http://forum.xda-developers.com/showpost.php?p=40149294&postcount=8
http://forum.xda-developers.com/showthread.php?t=2409602
edit.. Just in case that sounded a bit harsh it wasn't meant to. I am just trying to stop people getting in worse situations.
Click to expand...
Click to collapse
Flumpster you are correct mate .. sorry for the confusion .. I am editing the previous threads ...
SAJdroid said:
Flumpster you are correct mate .. sorry for the confusion .. I am editing the previous threads ...
Click to expand...
Click to collapse
Cheers. Don't stop helping over this, They need all the people they can over here helping out. Just make sure you know you are 100 percent before giving advise, I always used to test it myself first as wrong information is far worse than no information.
Keep up the good work mate. :good:
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.