[ROM][May 13][JB 4.2.1] AndroWook Prime Hairy Bean v2.2 **Unleash The Beast!**

[ArghMonkey]

Now reinstall the rom and reboot

how do I do that?

from TWRP?

Do I put the latest AndroWook on my external microSD card then find the install function in TWRP?

How do I know if I am running the right TWRP? I hear it changed?

I am a noob at this and i need step by step like I am 3 years old

 

[ArghMonkey]

Anyone ?

 

[sbdags]

how do I do that?

from TWRP?

Do I put the latest AndroWook on my external microSD card then find the install function in TWRP?

How do I know if I am running the right TWRP? I hear it changed?

I am a noob at this and i need step by step like I am 3 years old

Which TWRP do you have installed - just make sure you have flashed the bootloader and twrp in the first post - all the instructions are there for for you.

 

[ArghMonkey]

Which TWRP do you have installed - just make sure you have flashed the bootloader and twrp in the first post - all the instructions are there for for you.

How do I find out what version of TWRP and bootloader that I am using?

 

[sbdags]

How do I find out what version of TWRP and bootloader that I am using?

Start the tab with power and vol down held down - the bootloader version will be int he top left corner.

Then hit vol up on the RCK icon which will take you into recovery which should be obvious what its version is

 

[ArghMonkey]

Start the tab with power and vol down held down - the bootloader version will be int he top left corner.

Then hit vol up on the RCK icon which will take you into recovery which should be obvious what its version is

When in TWRP if I hit "settings" then in the top left it says v2.4.4.0 is that the version of TWRP I have?

When I restarted it says bootloader (1.00 e) is that my bootloader version?!

Can I copy over the latest AndroWook on my microSD card with these TWRP and bootloader versions? ...

 

[sbdags]

When in TWRP if I hit "settings" then in the top left it says v2.4.4.0 is that the version of TWRP I have?

When I restarted it says bootloader (1.00 e) is that my bootloader version?!

Can I copy over the latest AndroWook on my microSD card with these TWRP and bootloader versions? ...

Bootloader will be something like 10.6.1.27.1. I think 2.4.4.0 is OLD!
OK YOU ARE IN THE WRONG THREAD - GO HERE

http://forum.xda-developers.com/showthread.php?t=2407248

If you installed the file (bootloader and recovery package) from the first post in that thread for 2.3.1 then you have everything ready to install this rom......

 

[flumpster]

Bootloader will be something like 10.6.1.27.1. I think 2.4.4.0 is OLD!
OK YOU ARE IN THE WRONG THREAD - GO HERE

http://forum.xda-developers.com/showthread.php?t=2407248

If you installed the file (bootloader and recovery package) from the first post in that thread for 2.3.1 then you have everything ready to install this rom......

Noooo.. Don't give up now, you was doing so well.

You ok mate? long time no speak.

 

[sbdags]

Noooo.. Don't give up now, you was doing so well.

You ok mate? long time no speak.

Yeah good mate! What you been up to?

 

[ArghMonkey]

Maybe someone, Flumpster too, can tell me whether I should be upgrading or what

I just formatted my AndroWook transformer prime, I dont know how to find the bootloader (the top left tells me I have bootloader 1.00 e when I startup with power + down volume.

When I go to settings in TWRP it tells me I have v2.4.4.0. which sdbags was nice enough to tell me is the old version, is that too old to upgrade from?! How do I find the bootloader version exactly?!

Thanks ahead of time for this guys

 

[ArghMonkey]

Hey Flumpster, you helped me before when I first installed AndroWook, without you I never would have got it working.

Any help you can give my dumb brain on this one?

 

[flumpster]

Hey Flumpster, you helped me before when I first installed AndroWook, without you I never would have got it working.

Any help you can give my dumb brain on this one?

Just go to the 2.31 where you have posted also and follow the instructions in the first post that includes flashing the bootloader and twrp combo.

What you are reading about flashing wrong versions is between bootloader and twrp.. If you have a certain version bootloader and flash the wrong twrp for it it can brick you. This doesn't apply here because the file I give in the 2.31 thread flashes the bootloader and the correct compatible twrp the same time. Then you flash the rom.

So, to paraphrase. Follow instructions on 2.31 1st post.

 

[ArghMonkey]

Just go to the 2.31 where you have posted also and follow the instructions in the first post that includes flashing the bootloader and twrp combo.

What you are reading about flashing wrong versions is between bootloader and twrp.. If you have a certain version bootloader and flash the wrong twrp for it it can brick you. This doesn't apply here because the file I give in the 2.31 thread flashes the bootloader and the correct compatible twrp the same time. Then you flash the rom.

So, to paraphrase. Follow instructions on 2.31 1st post.

You rock Flumpster!

I might have AndroWook installed on my transformer prime but we both know, its the Flump-mobile!

 

[hitch77]

So I think I've screwed up a bit. I was running Androwook and I read someone say that SlimKat is looking good. I flashed androwook ages ago, so forgot about the whole "If you want to install anything else you've got to use the "downgrade" zip". and therefore I didn't.

I tried to install SlimKat using TWRP, and it failed. So I thought it might be my TWRP version, so I upgraded - I'm now on v2.6.3.0. However when I boot up the device it goes straight into TWRP and prompts for password - which I didn't set. I've read a bunch of threads, suggesting:
- to wipe (I can't, the partitions aren't mounted)
- to format a partition as ext3 (or 4 - whatever) - I can't no partitions are mounted.

When I check in adb or TWRP file manager, I can see /dev/block/mmcblk0 and mmcblk0p1 - which I assume is my external sd card, however it doesn't let me mount my external SD card.

When I'm in windows, my windows won't recognise my device to allow me to use adb - it says "Transformer - device not recognised". I can use adb in ubuntu, but then I can't access any on device partitions.

Would love any advice here that might get me back on the right path. Right now the device is looking like a big paperweight... cheer.

 

[Restorer]

So I think I've screwed up a bit. I was running Androwook and I read someone say that SlimKat is looking good. I flashed androwook ages ago, so forgot about the whole "If you want to install anything else you've got to use the "downgrade" zip". and therefore I didn't.

I tried to install SlimKat using TWRP, and it failed. So I thought it might be my TWRP version, so I upgraded - I'm now on v2.6.3.0. However when I boot up the device it goes straight into TWRP and prompts for password - which I didn't set. I've read a bunch of threads, suggesting:
- to wipe (I can't, the partitions aren't mounted)
- to format a partition as ext3 (or 4 - whatever) - I can't no partitions are mounted.

When I check in adb or TWRP file manager, I can see /dev/block/mmcblk0 and mmcblk0p1 - which I assume is my external sd card, however it doesn't let me mount my external SD card.

When I'm in windows, my windows won't recognise my device to allow me to use adb - it says "Transformer - device not recognised". I can use adb in ubuntu, but then I can't access any on device partitions.

Would love any advice here that might get me back on the right path. Right now the device is looking like a big paperweight... cheer.

Wonder how flumspter knew people would be doing this :laugh:. He made a special blob for you to flash :good:. Follow the instructions in this post and you should get back to the correct TWRP so you can start over again:

http://forum.xda-developers.com/showpost.php?p=40149294&postcount=8

 

[hitch77]

Wonder how flumspter knew people would be doing this :laugh:. He made a special blob for you to flash :good:. Follow the instructions in this post and you should get back to the correct TWRP so you can start over again:

http://forum.xda-developers.com/showpost.php?p=40149294&postcount=8

Thanks for the tips here - I've had a go, but unfortunately I'm not having much luck. It appears I'm unable to get into fastboot any more - holding volume down during power on appears to do nothing.

I tried adb shell, but it reports "insufficient permissions for device". Also, as mentioned previously, I can only see mmcblk0 and mmcblk0p1 when using the twrp file manager, so don't know if the adb command on the thread you reference is any use to me.

I'll keep trying. Any more tips welcome!

 

[ChungWingKeung]

cannot detect memory card

my prime cannot detect memory card
and now i cannot boot into the system after upgrading the bootloader

what can i do now thx D:

 

[SmilinGuy]

Thanks for the tips here - I've had a go, but unfortunately I'm not having much luck. It appears I'm unable to get into fastboot any more - holding volume down during power on appears to do nothing.

I tried adb shell, but it reports "insufficient permissions for device". Also, as mentioned previously, I can only see mmcblk0 and mmcblk0p1 when using the twrp file manager, so don't know if the adb command on the thread you reference is any use to me.

I'll keep trying. Any more tips welcome!

It sounds like I'm in the same boat.

Can't get into fastboot, just goes directly to TWRP 2.6.3.0 and prompts for password.

Can't wipe /data as it give the error "unable to format to remove encryption" which is preceded by "Unable to find partition size for '/misc' and again for '/staging', '/data', '/boot' and '/recovery'.

I'm unable to use the dd command suggested as the /dev/block directory contains only 2 mmcblk files: mmcblk0 and mmcblk0p1. So, I don't have an mmcblk0p4 to write to. TWRP is running though, so I guess I should be able to access it's device and overwrite it with dd.

When I boot without the external sdcard, I have no devices other than loop0..loop7 in the /dev/block folder. Where are the partitions? I wonder if I should I be trying to overwrite the bootloader as it's ignoring my VOL-Down and just going directly into TWRP? If so, how would I do that with adb? I can transfer files and adb seems to be okay.

So, confused. Any help would be greatly appreciated.

NEW INFO
I cant get to fastboot using adb reboot-bootloader. I can flash with fastboot -i 0x0B05 flash recovery twrp.blob and it finishes on the command line but no blue line appears on the device and it just hangs there.

 

[sbdags]

It sounds like I'm in the same boat.

Can't get into fastboot, just goes directly to TWRP 2.6.3.0 and prompts for password.

Can't wipe /data as it give the error "unable to format to remove encryption" which is preceded by "Unable to find partition size for '/misc' and again for '/staging', '/data', '/boot' and '/recovery'.

I'm unable to use the dd command suggested as the /dev/block directory contains only 2 mmcblk files: mmcblk0 and mmcblk0p1. So, I don't have an mmcblk0p4 to write to. TWRP is running though, so I guess I should be able to access it's device and overwrite it with dd.

When I boot without the external sdcard, I have no devices other than loop0..loop7 in the /dev/block folder. Where are the partitions? I wonder if I should I be trying to overwrite the bootloader as it's ignoring my VOL-Down and just going directly into TWRP? If so, how would I do that with adb? I can transfer files and adb seems to be okay.

So, confused. Any help would be greatly appreciated.

NEW INFO
I cant get to fastboot using adb reboot-bootloader. I can flash with fastboot -i 0x0B05 flash recovery twrp.blob and it finishes on the command line but no blue line appears on the device and it just hangs there.

Even after fastboot reboot-bootloader?

 

[flumpster]

All these posts are in the wrong thread. If you have messed up your device by flashing a different version of TWRP to the one needed by the bootloader you are on then please make a new thread. This thread is for the Hairybean rom and it tells you in the instructions that you are not to use different recoveries while using it.

It seems most people are getting into trouble while trying to move to a different rom so you could ask in their threads also