Evening all,
Hoping someone can help me with the following please? Please be as technical as you like, I'm fairly tech-savvy (I have CFW on my PSP, I build my own computers and have flashed/cfw various devices in the past) if I don't understand I can google it, but I need to know WHAT to google first and I'm a bit lost...! :good:
I have stock TF201 which is getting pretty painful despite a recent re-install. I've noticed that there is still no real idea as to if/when KitKat will be rolled out for it and was rather p!ssed off to see my missus's Nexus 7 (2012 version!) get 4.4.3 today!
I've done a lot of googling and forum reading but I'm a little confused as to the best route to go...
Having come across the "one-click method to root" using motochopper (and/or other methods) would it then be possible to install 4.4.2 for example using CM11 and a guide such as this (google "Install Android 4.4.2 KitKat on Asus Transformer Prime TF201" as I can't post URLs) - or will this only work for OFW release like 4.2?
In summary, am I missing the point (I get the feeling I may need to be unlocked as well to have a custom recovery?), THEN root etc...
Long and short is I'm not after doing anything crazy other than getting my TF201 to the latest STABLE(ish) version of Android. I understand the risks of bricking, CFW/OFW & OTA etc. I guess I'm basically after a simple list of steps (or pointing at the relevant thread) to achieve this - from the guides I've seen I have to unlock, root and then go down the CM11 route but I want to know if I can get there more easily/safely using one-click root or another method for example?
All advice gratefully received!
Mark
mistral_blue said:
Evening all,
Hoping someone can help me with the following please? Please be as technical as you like, I'm fairly tech-savvy (I have CFW on my PSP, I build my own computers and have flashed/cfw various devices in the past) if I don't understand I can google it, but I need to know WHAT to google first and I'm a bit lost...! :good:
I have stock TF201 which is getting pretty painful despite a recent re-install. I've noticed that there is still no real idea as to if/when KitKat will be rolled out for it and was rather p!ssed off to see my missus's Nexus 7 (2012 version!) get 4.4.3 today!
I've done a lot of googling and forum reading but I'm a little confused as to the best route to go...
Having come across the "one-click method to root" using motochopper (and/or other methods) would it then be possible to install 4.4.2 for example using CM11 and a guide such as this (google "Install Android 4.4.2 KitKat on Asus Transformer Prime TF201" as I can't post URLs) - or will this only work for OFW release like 4.2?
In summary, am I missing the point (I get the feeling I may need to be unlocked as well to have a custom recovery?), THEN root etc...
Long and short is I'm not after doing anything crazy other than getting my TF201 to the latest STABLE(ish) version of Android. I understand the risks of bricking, CFW/OFW & OTA etc. I guess I'm basically after a simple list of steps (or pointing at the relevant thread) to achieve this - from the guides I've seen I have to unlock, root and then go down the CM11 route but I want to know if I can get there more easily/safely using one-click root or another method for example?
All advice gratefully received!
Mark
Click to expand...
Click to collapse
Man your asking for alot
Shoot me a PM lets see if we can point you in the right direction.....
Thx Josh
mistral_blue said:
(I get the feeling I may need to be unlocked as well to have a custom recovery?), THEN root etc...
Click to expand...
Click to collapse
Yep, that's the only route to custom ROM and vital you make NVFlash backups:
1. Unlock device using the official tool from Asus website - its says "for ICS" but works fine on JB.
2. Assuming you are on the latest official stock JellyBean (Asus v 10.4.2.18) then go get the latest TWRP 2.6 for TF201 JB from the bottom of this page: http://techerrata.com/browse/twrp2/tf201 Flash that blob using fastboot following the instructions in the section titled "Download - Recovery Image / Fastboot Method (using ICS or JB Asus bootloader)" on this page: http://teamw.in/project/twrp2/93.
3. Follow the instructions in the tutorial here for making NVFlash backups: http://matthill.eu/android/transform...ybean-nvflash/
4. You are now ready flash a custom ROM of your choice. If you really want to go straight to KK then my advice would be to look no further than CROMBi-kk: http://forum.xda-developers.com/showthread.php?t=2773812. You will get plenty of help here from people who know about the tf201. Read the whole thread but pay particular attention to post #4 where Josh has written a step by step guide for people starting from scratch.
Finally, though you are pretty safe now with your NVFlash backups and even though you are well experiences at flashing, follow all the instructions to the letter and avoid the sadly well tested routes to brick. I don't believe there is another android device in current use that is so easy to brick as the prime.
1. Use only TWRP recoveries. Steer completely clear of CWM and ROM Manager. They never did produce an official recovery for JB on the prime and installing the last one from their site onto the JB bootloader will most certainly land you with a brick. The flatline process leaves behind its own version of CWM but has been made compatible. However, you probably won't be able to see your external SD card with it and it is based on a clunky non-touch version so best advice would be to ditch it straight away for TWRP 2.6 even though you will be upgrading that shortly anyway,
2. Always check you are flashing the correct version of TWRP for your current bootloader and ROM
3. Never, ever press that Wipe Data button on the fastboot screen - that too will kill your tablet.
Oh, and have fun!
EDIT: just seen Josh has offered to hold your hand - don't let go and you'll be fine
Thanks for the quick replies gents... Restorer, I'll read up on the methods you suggest (thanks for the detailed list with links, exactly what I was after) and then Josh I'll be in touch to check I've not missed anything before I start following the Yellow BRICK road:laugh:
Taking The Plunge!
Restorer said:
Yep, that's the only route to custom ROM and vital you make NVFlash backups:
1. Unlock device using the official tool from Asus website - its says "for ICS" but works fine on JB.
2. Assuming you are on the latest official stock JellyBean (Asus v 10.4.2.18) then go get the latest TWRP 2.6 for TF201 JB from the bottom of this page: http://techerrata.com/browse/twrp2/tf201 Flash that blob using fastboot following the instructions in the section titled "Download - Recovery Image / Fastboot Method (using ICS or JB Asus bootloader)" on this page: http://teamw.in/project/twrp2/93.
3. Follow the instructions in the tutorial here for making NVFlash backups: http://matthill.eu/android/transform...ybean-nvflash/
4. You are now ready flash a custom ROM of your choice. If you really want to go straight to KK then my advice would be to look no further than CROMBi-kk: http://forum.xda-developers.com/showthread.php?t=2773812. You will get plenty of help here from people who know about the tf201. Read the whole thread but pay particular attention to post #4 where Josh has written a step by step guide for people starting from scratch.
Finally, though you are pretty safe now with your NVFlash backups and even though you are well experiences at flashing, follow all the instructions to the letter and avoid the sadly well tested routes to brick. I don't believe there is another android device in current use that is so easy to brick as the prime.
1. Use only TWRP recoveries. Steer completely clear of CWM and ROM Manager. They never did produce an official recovery for JB on the prime and installing the last one from their site onto the JB bootloader will most certainly land you with a brick. The flatline process leaves behind its own version of CWM but has been made compatible. However, you probably won't be able to see your external SD card with it and it is based on a clunky non-touch version so best advice would be to ditch it straight away for TWRP 2.6 even though you will be upgrading that shortly anyway,
2. Always check you are flashing the correct version of TWRP for your current bootloader and ROM
3. Never, ever press that Wipe Data button on the fastboot screen - that too will kill your tablet.
Oh, and have fun!
EDIT: just seen Josh has offered to hold your hand - don't let go and you'll be fine
Click to expand...
Click to collapse
Restorer thanks for the instructions...like the title I am about to take the "plunge" and flash this Prime and I want to got to KK. Just one thing.. below you state: "4. You are now ready flash a custom ROM of your choice. If you really want to go straight to KK then my advice would be to look no further than CROMBi-kk: http://forum.xda-developers.com/show....php?t=2773812. " but when I go to the link it says that I must be on Hairybean and the bootloader 4.2.1. I am currently on the stock 10.4.2.18 and downloaded the unlock v6 .apk file from Asus to do the bootloader "unlocking" Just for the sake of clarity...I am new to this...should I still unlock using the Asus util and once done then do the Hairybean update? which will in turn upgrade the bootloader (10.6.1.27.1)?
Tim
tim2min said:
Restorer thanks for the instructions...like the title I am about to take the "plunge" and flash this Prime and I want to got to KK. Just one thing.. below you state: "4. You are now ready flash a custom ROM of your choice. If you really want to go straight to KK then my advice would be to look no further than CROMBi-kk: http://forum.xda-developers.com/show....php?t=2773812. " but when I go to the link it says that I must be on Hairybean and the bootloader 4.2.1. I am currently on the stock 10.4.2.18 and downloaded the unlock v6 .apk file from Asus to do the bootloader "unlocking" Just for the sake of clarity...I am new to this...should I still unlock using the Asus util and once done then do the Hairybean update? which will in turn upgrade the bootloader (10.6.1.27.1)?
Tim
Click to expand...
Click to collapse
Yes, you can't flash anything until the device is unlocked and you have installed a TWRP recovery.
But make sure to then make your NVFlash backups and once you have those files safely stored go straight on to follow Josh's step-by-step guide for in post #4 of the ROM thread. His guide was written specifically for TF201 people coming from stock. Follow it to the letter but be sure to ask if there is something you don't understand.
Good Luck!
Taking The Plunge!
Restorer said:
Yep, that's the only route to custom ROM and vital you make NVFlash backups:
1. Unlock device using the official tool from Asus website - its says "for ICS" but works fine on JB.
2. Assuming you are on the latest official stock JellyBean (Asus v 10.4.2.18) then go get the latest TWRP 2.6 for TF201 JB from the bottom of this page: http://techerrata.com/browse/twrp2/tf201 Flash that blob using fastboot following the instructions in the section titled "Download - Recovery Image / Fastboot Method (using ICS or JB Asus bootloader)" on this page: http://teamw.in/project/twrp2/93.
3. Follow the instructions in the tutorial here for making NVFlash backups: http://matthill.eu/android/transform...ybean-nvflash/
4. You are now ready flash a custom ROM of your choice. If you really want to go straight to KK then my advice would be to look no further than CROMBi-kk: http://forum.xda-developers.com/showthread.php?t=2773812. You will get plenty of help here from people who know about the tf201. Read the whole thread but pay particular attention to post #4 where Josh has written a step by step guide for people starting from scratch.
Finally, though you are pretty safe now with your NVFlash backups and even though you are well experiences at flashing, follow all the instructions to the letter and avoid the sadly well tested routes to brick. I don't believe there is another android device in current use that is so easy to brick as the prime.
1. Use only TWRP recoveries. Steer completely clear of CWM and ROM Manager. They never did produce an official recovery for JB on the prime and installing the last one from their site onto the JB bootloader will most certainly land you with a brick. The flatline process leaves behind its own version of CWM but has been made compatible. However, you probably won't be able to see your external SD card with it and it is based on a clunky non-touch version so best advice would be to ditch it straight away for TWRP 2.6 even though you will be upgrading that shortly anyway,
2. Always check you are flashing the correct version of TWRP for your current bootloader and ROM
3. Never, ever press that Wipe Data button on the fastboot screen - that too will kill your tablet.
Oh, and have fun!
EDIT: just seen Josh has offered to hold your hand - don't let go and you'll be fine
Click to expand...
Click to collapse
Restorer said:
Yes, you can't flash anything until the device is unlocked and you have installed a TWRP recovery.
But make sure to then make your NVFlash backups and once you have those files safely stored go straight on to follow Josh's step-by-step guide for in post #4 of the ROM thread. His guide was written specifically for TF201 people coming from stock. Follow it to the letter but be sure to ask if there is something you don't understand.
Good Luck!
Click to expand...
Click to collapse
Sorry just one more question, since I have a TF201 and and want to use this ROM, it seems I am essentially turning my Prime into aTF300, which is ok, now right after unlocking the boot loader and then running TWRP (2.7 TF300) it is at this point I flash the hairybean update or do the creation & backing up for NVFlash first then the hairybean?...sorry for the elemental question...just want to be sure!
Tim
tim2min said:
now right after unlocking the boot loader and then running TWRP (2.7 TF300)
Click to expand...
Click to collapse
No you're not a TF300 yet! Unlock then flash the latest TWRP version for TF201 from the page I linked to (still 2.6). Then do your NVFlash backups. Then you can pick up Josh's guide again where you flash "Upgrade Hairybean 2.31 (4.2.1) Bootloader & TWRP (2.5).zip". It's just the guide assumes you already have your backups .
Taking The Plunge!
Restorer said:
No you're not a TF300 yet! Unlock then flash the latest TWRP version for TF201 from the page I linked to (still 2.6). Then do your NVFlash backups. Then you can pick up Josh's guide again where you flash "Upgrade Hairybean 2.31 (4.2.1) Bootloader & TWRP (2.5).zip". It's just the guide assumes you already have your backups .
Click to expand...
Click to collapse
Hey restorer this can all be done on a non-root device correct? Should root first if so what is the best way you suggest ...read a little something about motochopper.?
Taking The Plunge!
tim2min said:
Hey restorer this can all be done on a non-root device correct? Should root first if so what is the best way you suggest ...read a little something about motochopper.?
Click to expand...
Click to collapse
Have a possible issue when trying to after renaming the original file flat_tf201 (image file) to twrp.blob it looks like on the windows 7 side it sent it fine but on the tablet I did not see the "blue bar". So worried it did not send I tried it again and got the "error cannot open twrp.blob" when I did a dir of the fastboot directory it is there but noticed is the command prompt after renaming (per instructions from TWRP) the full file name was twrp.blob.img should not matter but renamed it (from command prompt) w/o the .img extension still would not send.
I am thinking eventhough it initially looked like it did send (based on output in command prompt initially) is it possible I missed the blue bar on the tablet?... Should I have seen it? Does it take awhile?
The tablet shows "starting Fastboot USB download protocol"
any help what be appreciated
tim2min said:
Have a possible issue when trying to after renaming the original file flat_tf201 (image file) to twrp.blob it looks like on the windows 7 side it sent it fine but on the tablet I did not see the "blue bar". So worried it did not send I tried it again and got the "error cannot open twrp.blob" when I did a dir of the fastboot directory it is there but noticed is the command prompt after renaming (per instructions from TWRP) the full file name was twrp.blob.img should not matter but renamed it (from command prompt) w/o the .img extension still would not send.
I am thinking eventhough it initially looked like it did send (based on output in command prompt initially) is it possible I missed the blue bar on the tablet?... Should I have seen it? Does it take awhile?
The tablet shows "starting Fastboot USB download protocol"
any help what be appreciated
Click to expand...
Click to collapse
Why rename the the .img file to a .blob file ?
Not really the best thing you could do .....
Just boot to fastboot and run the command
Code:
fastboot flash recovery flatline_tf201.img
The blue bar will show up and fill on the write part of the command ...
Once that is done do this command .....
Code:
fastboot reboot-bootloader
Let the tablet reboot into bootloader and VOL up on RCK
Now your golden ......
Make sure you understand what need to be done in flatline ...
Thx Josh
tim2min said:
Hey restorer this can all be done on a non-root device correct? Should root first if so what is the best way you suggest ...read a little something about motochopper.?
Click to expand...
Click to collapse
No need to root first - the custom ROM you will be installing will be rooted.
---------- Post added at 08:09 AM ---------- Previous post was at 07:59 AM ----------
tim2min said:
Have a possible issue when trying to after renaming the original file flat_tf201 (image file) to twrp.blob it looks like on the windows 7 side it sent it fine but on the tablet I did not see the "blue bar". So worried it did not send I tried it again and got the "error cannot open twrp.blob" when I did a dir of the fastboot directory it is there but noticed is the command prompt after renaming (per instructions from TWRP) the full file name was twrp.blob.img should not matter but renamed it (from command prompt) w/o the .img extension still would not send.
I am thinking eventhough it initially looked like it did send (based on output in command prompt initially) is it possible I missed the blue bar on the tablet?... Should I have seen it? Does it take awhile?
The tablet shows "starting Fastboot USB download protocol"
any help what be appreciated
Click to expand...
Click to collapse
Sounds like you have downloaded (and renamed) the .img file and not the .blob file! "openrecovery-twrp-2.6.3.0-tf201-JB.blob" is the one you want if you are follwoing the instructions on the TWRP page I linked you too. The blob file Josh refers to is the one in this zip file and has a shorter name. You can either use Josh's instructions or TWRP's but not a mixture of the two
@lj50036 I think he referring to the instructions from TWRP on the downloads page which say to rename the file to a shorter form.
@tim2min don't let this renaming stuff confuse you - TWRP are only suggesting it because their full names are so long and prone to error when you are typing them out!
EDIT: Sorry, I hadn't realised Josh had already prepared and renamed the files for you. Just use all 3 of his files contained in his zip and not from my links or you may get further confused.
Restorer said:
No need to root first - the custom ROM you will be installing will be rooted.
---------- Post added at 08:09 AM ---------- Previous post was at 07:59 AM ----------
Sounds like you have downloaded (and renamed) the .img file and not the .blob file! "openrecovery-twrp-2.6.3.0-tf201-JB.blob" is the one you want if you are follwoing the instructions on the TWRP page I linked you too. The blob file Josh refers to is the one in this zip file and has a shorter name. You can either use Josh's instructions or TWRP's but not a mixture of the two
@lj50036 I think he referring to the instructions from TWRP on the downloads page which say to rename the file to a shorter form.
@tim2min don't let this renaming stuff confuse you - TWRP are only suggesting it because their full names are so long and prone to error when you are typing them out!
EDIT: Sorry, I hadn't realised Josh had already prepared and renamed the files for you. Just use all 3 of his files contained in his zip and not from my links or you may get further confused.
Click to expand...
Click to collapse
Does no one use auto-complete any more ......
Thx Josh
lj50036 said:
Does no one use auto-complete any more ......
Thx Josh
Click to expand...
Click to collapse
Haha, yes. Why do command windows have to be so primitive .
Restorer said:
No you're not a TF300 yet! Unlock then flash the latest TWRP version for TF201 from the page I linked to (still 2.6). Then do your NVFlash backups. Then you can pick up Josh's guide again where you flash "Upgrade Hairybean 2.31 (4.2.1) Bootloader & TWRP (2.5).zip". It's just the guide assumes you already have your backups .
Click to expand...
Click to collapse
Just an observation Restorer I note that you said never to select "Wipe Data" in the boot menu but in Josh step by step he suggested to do that which can take a while. In this case it ok to do it since we are putting on a new ROM. I have my backups (blob files) as well as the NVFlash file
Tim
tim2min said:
Just an observation Restorer I note that you said never to select "Wipe Data" in the boot menu but in Josh step by step he suggested to do that which can take a while. In this case it ok to do it since we are putting on a new ROM. I have my backups (blob files) as well as the NVFlash file
Tim
Click to expand...
Click to collapse
How is this saying anything about wiping from bootloader ?
I am sure it say NOW ENTER RECOVERY ....
But maybe I missed something or maybe you did ....
lj50036 said:
Now enter recovery....
Make sure its verison 2.7.1.0
Go to Wipe////Format Data////Type yes
This can take up to 90 mins to format
DO NOT INTERRUPT THE FORMAT !!!!!!!
Click to expand...
Click to collapse
Thx Josh
Taking The Plunge!
lj50036 said:
How is this saying anything about wiping from bootloader ?
I am sure it say NOW ENTER RECOVERY ....
But maybe I missed something or maybe you did ....
Thx Josh
Click to expand...
Click to collapse
Man it was going so well until my computer could no longer see my tablet via USB! so I can now longer use FASTBOOT because the device is not found. This happen right after flashing Hariybean and I was about to run"
Interesting my Win7 computer says that it sees the Asus device:but fastboot does not see it. Also initially the it saw it as an APX device but no longer so I can not do the next step which is to adb reboot-bootloader and then do flash @ne0zone75 TWRP recovery per the instuctions. I have tried re-pointing to the Universal Naked drivers trying to select a diffrent drvier but to no avail. looks like the tablet can no longer communicate to the computer. I will copy the contents of the fastboot directory to another computer and see if that will work
any ideas?
Tim
tim2min said:
Man it was going so well until my computer could no longer see my tablet via USB! so I can now longer use FASTBOOT because the device is not found. This happen right after flashing Hariybean and I was about to run"
Interesting my Win7 computer says that it sees the Asus device:but fastboot does not see it. Also initially the it saw it as an APX device but no longer so I can not do the next step which is to adb reboot-bootloader and then do flash @ne0zone75 TWRP recovery per the instuctions. I have tried re-pointing to the Universal Naked drivers trying to select a diffrent drvier but to no avail. looks like the tablet can no longer communicate to the computer. I will copy the contents of the fastboot directory to another computer and see if that will work
any ideas?
Tim
Click to expand...
Click to collapse
Sounds like another windows driver issue .....
I really cant help much here as I dont use windows ...
But there is a short term solution at least to get you booted up ....
@ne0zone75's flashable zip twrp
Download this and move it into your folder that contains the fastboot.exe ... Then rename it to twrp.zip
Then boot into the recovery and run this command from CMD window
Code:
adb push twrp.zip /sdcard
Let that happen should not take long, find the zip file under install and flash it .....
YOU MUST DO A REBOOT AFTER THIS NOT JUST A REBOOT INTO BOOTLOADER ...
So lets run this command ....
Code:
adb reboot
Let it fully boot into a bootloop then with the buttons get back to the bootloader screen and enter RCK ...
then once you have done that continue on your way ....
Let me know this works for you ....
Thx Josh
tim2min said:
Just an observation Restorer I note that you said never to select "Wipe Data" in the boot menu but in Josh step by step he suggested to do that which can take a while. In this case it ok to do it since we are putting on a new ROM. I have my backups (blob files) as well as the NVFlash file
Tim
Click to expand...
Click to collapse
Josh has answered you. But this is another fine example of why people here keep banging on about reading things carefully and then following instructions to the letter .
Taking the Plunge
Well, after some "trying" moments I got this ROM on the Prime!...must say extremely excited seems like my TF201 has more than just a "heartbeat" left in her, shoot she may be able to run hard a little longer!. I must admit some EXTREME anxiety occured and I really got scared when after flashing hairybean/bootloader my computer could not find/see my tablet AT ALL!!. This lost of connection was madddding especially when Windows would add the tablet in device manager and you would hear the computer chime every time I connected/disconnect the USB cable from the computer while the other end was in the tablet. I had to fuss around with Android APD Interface/Android APX drivers until my computer settled on one that actually worked after running c:\fastboot>fastboot devices 50x's and if finally saw my tablet I literally shedded a tear, this is definetely not for the faint of heart...lol Needless to say I hurried up and finished going down the instructions just for fear my computer might "inexplicably " loose connection again!....lol
Many thanks to Restorer for chiming in with my question also Josh (especially for the step by step instructions) also to the whole team that made this ROM!
Just a question though: If you wanted to change the color theme on boot up (which now shows in blue "CROMBi-KK") how would I go about that?
Tim
Related
Sorry about pulling the old post because of some problems.
Here is the latest update, I have modified the root.zip which may solve the flash_image problem.
Let's start!
What we need:
1. Nexus One with FRF72
2. The files I provide
3. Android SDK
4. Transcend Class 6 4gig(High recommend but not a must)
5. A brain!!!
Click to expand...
Click to collapse
YOU MUST FOLLOW ALL STEPS, OTHERWISE YOU LOSE!
Step 0:
- Install the SDK
- Make sure there is no "update.zip" in SD card
- Connect your phone with the USB
- Extract all files I provided to your <SDK>/tools
Step 1:
Enable Debugging in Setting->Development
Then, shut down your phone
Step 2:
Booting into bootloader by holding vol- and press Power
Use vol- button to highlight "Recovery"
Step 3:
Open CMD, and cd to the <SDK>/tools
Run "loop"
Step 4:
Press Power to enter Recovery now, you will see the triangle and <!>
Hold Power and vol+ to show the menu
Step 4a:
If your CMD shows you the devices is in recovery, press control + c to stop the "loop"
Step 4b:
If there is nothing, reboot your phone and repeat step 2-4 until it shows up.
(This is 99% caused by the sd card, faster card make it easier to show up)
Step 5:
Select "Apply update.zip", and it will show failed(IMPORTANT!!!!)
Step 6:
Run "adb push ota.zip /sdcard/update.zip"
Run "adb push busybox /sdcard/busybox"
Step 7:
Type but not run "adb push root.zip /sdcard/update.zip"
Step 8:
Select "Apply update.zip" again and run the step-7-code half a second later.
IF IT SHOWS ERROR STATUS 6, DOWNLOAD THE NEW ZIP I UPLOADED
Step 8a:
If it works, it will print ""Nexus One Rooting modified by Booker from Hong Kong"
Step 8b:
If it failed, repeat step 6-8
Step 9:
Finished the process, you can now immediately flash_image.
Step 10:
If you do flash a new recovery image, you may need to remove "/system/etc/install-recovery.sh" and "/system/recovery-from-boot.p"
This prevent the system automatically re-flash your recovery image to the stock one.
Click to expand...
Click to collapse
Have fun to flash great roms from devs.
Hope you can buy me some candies if you do like my work.
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=3CDK8GTKMZGWJ
requirements. for this method
Hey..your post says you require frf72 for this to work
But that requires me to root my n1...(epe54b)...which means bootloader unlocking.
Will your method then remove the padlock?
There is not much reason to root the t-mo n1 since they can flash frf50 anyway (tethering included )
So based on the last statement, I'm assuming after doing this I'm not able to flash the stock updates without loosing my root? Just wanted to make sure I understood you correctly. Also the flash_image file. After it's uploaded to the phone I have to run this using a terminal or from a adb shell, correct?
actuallly you can get the official version, put it on your sd card and install it without being rooted. That is what they want you to do.
You see those of us who were rooted had to wait for a repacked version of the FRF72 update or we had to revert to stock with a stock recovery to get it to install. So sir, this is a valid method and you will keep your warranty intact!
O_O this is a really big deal NO?
anangphatak said:
Hey..your post says you require frf72 for this to work
But that requires me to root my n1...(epe54b)...which means bootloader unlocking.
Will your method then remove the padlock?
There is not much reason to root the t-mo n1 since they can flash frf50 anyway (tethering included )
Click to expand...
Click to collapse
you can flash the stock frf72 and don't need to root. just grab an official non-root build, place on sdcard and flash via any recovery u have installed
Looks interesting to say the least!
Just curious, why no frf83? Is it too new or just not possible?
madj42 said:
So based on the last statement, I'm assuming after doing this I'm not able to flash the stock updates without loosing my root? Just wanted to make sure I understood you correctly. Also the flash_image file. After it's uploaded to the phone I have to run this using a terminal or from a adb shell, correct?
Click to expand...
Click to collapse
No it will not remove the padlock. There is no way to relock the phone as of now.
I really wish this was a week ago..I had gotten a new phone, and decided not to wait to root it.
artcarney said:
Looks interesting to say the least!
Just curious, why no frf83? Is it too new or just not possible?
Click to expand...
Click to collapse
I was asking myself the same thing. The other thing is, wouldn't we have to flash a new radio too? Coming from 2.1 update1 this is a must afair.
jroid said:
you can flash the stock frf72 and don't need to root. just grab an official non-root build, place on sdcard and flash via any recovery u have installed
Click to expand...
Click to collapse
Really? I have been looking for this file for EPE54B for days!
all i have found was FRF50 from EPE27, FRF72 from FRF50, FRF83 from FRF50...
can you please advise us where we could find the one for EPE54B please?
Zapo said:
I was asking myself the same thing. The other thing is, wouldn't we have to flash a new radio too? Coming from 2.1 update1 this is a must afair.
Click to expand...
Click to collapse
i still haven't got a confirmation from anyone that updating radio requires unlocked bootloader....
but i understand everyone's concern as flashing radio is pretty much the only way to brick you phone therefore no one has the guts to be the 1st one flashing Froyo and the new radio with a rooted phone w/o an unlocked bootloader, right?
Rayman0625 said:
No it will not remove the padlock. There is no way to relock the phone as of now.
I really wish this was a week ago..I had gotten a new phone, and decided not to wait to root it.
Click to expand...
Click to collapse
Let me rephrase my statement above. I have not rooted my phone using the fastboot method. No padlock is shown on the boot screen. I'm asking if after doing this, am I stuck to using the modified builds (one's with root) or can I still use the official builds directly from Google? I'm assuming based on what has been said that if I use the official builds after using this process, that I'll loose the root access. Correct me if I'm wrong.
Thanks in advance. I apologize for being such a newb with all these questions.
kaiser_tytnii said:
can you please advise us where we could find the one for EPE54B please?
Click to expand...
Click to collapse
Have a look here brother: http://forum.xda-developers.com/showthread.php?t=654869
Second thread in this forum.
christiankk said:
Have a look here brother: http://forum.xda-developers.com/showthread.php?t=654869
Second thread in this forum.
Click to expand...
Click to collapse
my apologizes, i did not see any Froyo ROM there.
madj42 said:
Let me rephrase my statement above. I have not rooted my phone using the fastboot method. No padlock is shown on the boot screen. I'm asking if after doing this, am I stuck to using the modified builds (one's with root) or can I still use the official builds directly from Google? I'm assuming based on what has been said that if I use the official builds after using this process, that I'll loose the root access. Correct me if I'm wrong.
Thanks in advance. I apologize for being such a newb with all these questions.
Click to expand...
Click to collapse
if you stay with stock recovery and ROM, you will receive OTA from Google.
You can still flash Stock ROM with Custom Recovery but will not be able to install OTA from Google.
hope this help.
Booker-T said:
Sorry about pulling the old post because of some problems.
Here is the latest update, I have modified the root.zip which may solve the flash_image problem.
Let's start!
Have fun to flash great roms from devs.
Hope you can buy me some candies if you do like my work.
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=3CDK8GTKMZGWJ
Click to expand...
Click to collapse
proud of you Konger!
Is there any way this can work on FRF83?
or
Is there a way to revert back to FRF72?
You can revert. Just need to grab the passimg.zip for the phone and flash from bootloader. Good job with tut a little clearer then mine. Didn't check files to see if the same but worked for me. Not reading the memory card was the obstacle which putting card in after detected in recovery was the only way I was able to get it to work.
M9x3mos said:
You can revert. Just need to grab the passimg.zip for the phone and flash from bootloader. Good job with tut a little clearer then mine. Didn't check files to see if the same but worked for me. Not reading the memory card was the obstacle which putting card in after detected in recovery was the only way I was able to get it to work.
Click to expand...
Click to collapse
Do you think you could give me a link to the passimg.zip that I can use without having to unlock the bootloader? I've been searching for hours.
PS: there is no busybox in the "Nexus_One_Full_Root.zip" from the original post.
Just a quick advice for everybody.... If someone (like me) is still stuck with the 2.1 Update 1, before update to 2.2 FRF52 test on your phone the point between 2 and 4.b. Once you will have your phone recognized by ADB then you can update to 2.2 FRF52.
For now my 4 microSD (1 * Class 6 Sandisk / 1 * Class 4 Kingston / 1 * Class 6 Transcend and 1 * Class 2 Samsung) doesn't work at all....
Hope this help
Hey guys,
apart from my Un-Bricking-Thread I wanted to start a Thread dealing with how to prevent a brick in the first place.
--- Already bricked your Prime? Read on here, maybe you can recover it ---
In the last days I learned quite a few things about the TFP, its CWM and how to work with it. I also hard bricked my Prime so I certainly know what I am talking about
Unfortunately ASUS didn't fully unlock our Bootloader. We still can't use NVFLASH for low level flashs.
This also means that we can't recover some things we could with NVFLASH access (like a broken bootloader).
So lets start with the things you better not do:
DON'T
Once you unlocked the prime and installed CWM, do NOT try to install a super blob from ASUS (that is a blob file from one of the 'full' updates from their site)
It seems that doing so totally bricks your Prime with no chance of recovery... (happened at least twice so far)
Don't flash kernels like you used to flash (with write_raw_image to /boot). This does not work on the Prime. More on how to do it later.
Don't rely on your newly created ROM to work, ALWAYS have a backup of a working ROM on your sdcard (or a zip of a working ROM)
Currently we can't mount the USB-Storage from inside CWM, so transferring files to the Prime while being in recovery is not as easy for many not so advanced users.
Always make sure you have all files you need before rebooting to recovery.
DO
Kernel flashing: There seem to be two methods on how to flash a new kernel. One is safer but needs a bit more work, and the other is rather unsafe but okay when you (or the ROM dev) know what needs to be done.
Flash your boot.img via fastboot. This is usually rather safe (as safe as fastboot can be) but needs you to have a working fastboot environment. Update: It seems kernel flashing via fastboot does not work at all. Fastboot doesn't give you an error but it doesn't update the kernel either...
Flash your kernel via the /staging partition. In order to use this method you first need to pack your boot.img into a blob file.
Then you need put the data from the blob file to the /staging partition.
Once you reboot the kernel gets automatically installed.
Please be aware that you can flash almost everything like this, even the bootloader.
So if you screw up packing the blob file, you could easily brick your Prime.
The advantage of this method is that the user doesn't need to do anything, but you really need to take care of what you are doing.
Also make sure that the /staging partition is ALWAYS unmounted before flashing anything to it. Otherwise this will result in a Brick 3.
Always make a backup of your current ROM before flashing anything else. As stated earlier, we currently have no access to the sdcard in recovery, so transferring files to Prime is not as easy in recovery mode.
So I hope I can find some more topics in the future, but for now that's it
Diamondback said:
DON'T
Once you unlocked the prime and installed CWM, do NOT try to install a super blob from ASUS (that is a blob file from one of the 'full' updates from their site) It seems that doing so totally bricks your Prime with no chance of recovery... (happened at least twice so far)
Click to expand...
Click to collapse
But but but how can I has update?! I want Update! RWAR!
Thanks, thanks, bump, and thanks again! Due to the current state of our device's development (especially with an early build of CWM), misinformation floating around, etc. this is invaluable! Now I know what "staging" is and what its use is. Well done - keep up the great work
Sent from my Transformer Prime TF201 using xda premium
mtotho said:
But but but how can I has update?! I want Update!
Click to expand...
Click to collapse
Use custom ROMs. We currently don't really know if it ALWAYS bricks your Prime. We just know that two updates bricked two primes
I think nobody wants to try
Diamondback said:
Use custom ROMs. We currently don't really know if it ALWAYS bricks your Prime. We just know that two updated bricked two primes
I think nobody wants to try
Click to expand...
Click to collapse
Yea I am just kidding. I knoweth better plus I like custom roms (and I am very flash happy)
I won't be happy until we get some sort of nightly rom that I can flash daily
thanks diamondback this prob saved me lots of time and the almost $700 i have in my device+dock
Sent from my Transformer Prime TF201 using xda premium
Will be possible to use NVFLASH anytime? Have we to look for a dev or is Asus that must upgrade its apk?
Thanks Diamondback for making this. This needs to become a sticky immediately. To many people are blindly unlocking then get mad when they find out they can't do OTA updates. Or people installing CMW without even unlocking and blaming others issues on that when they found out device should've been unlocked first..lmfao
Unlock tool release=operation sabotage for those who don't know any better or ignorant or lazy to research first. QnA section had several people with semi or hard bricked primes. Primes are dying off left n right..lol
Diamondback said:
Unfortunately ASUS didn't fully unlock our Bootloader.
Click to expand...
Click to collapse
So you download their software, run it to completely void your warranty (they've already denied support on one unrelated hardware issues that I know of), and you STILL don't have full access?
WTF!?!?!!?
Not being able to use NVFlash has completely put me off, for me NVFlash was the ultimate aim for unlocking the bootloader ... pretty **** !
(unhappy smiley)
Diamondback, I'm so sorry to hear that you bricked your Prime! Any luck getting unbricked yet?
Thank you so much for posting this invaluable guide. You are generous beyond words, to go to this effort to save other users from the lessons you had to learn the hard way. There aren't enough thanks in the world.
If we can at least ATM use fastboot that's a good thing. A good thing for fastboot is you can first do-
fastboot boot boot.img and it will boot the kernel the first time, basically so you can test it before it writes the .img
then you can fastboot flash boot.img to write the image. It'll work for now, sucks that any non-dev who just wants to flash a kernel has to set up fastboot
Edit- girluvsdroid- just saw you were in wilmington- me too.
This was very helpful.
BUMP!
Reading is fundamental! Lol I don't know how many times I've just glanced over post, just to get the newest firmware, and kernals, just to end up on the verg of a bricked device. Thanks.
What ?
So If I UnlockBootLoader
I cant OTA Anymore ? Seriously
AndyMclamb said:
What ?
So If I UnlockBootLoader
I cant OTA Anymore ? Seriously
Click to expand...
Click to collapse
But why would you unlock if you were not going to install custom roms (that have the latest OTA built in) anyway?
Diamondback said:
Flash your boot.img via fastboot. This is usually rather safe (as safe as fastboot can be) but needs you to have a working fastboot environment.
Click to expand...
Click to collapse
Hmm.. Does not seem to work for me. Built a kernel, switched in fastboot mode. Then:
Code:
$ sudo ./fastboot -i 0x0b05 boot zImage blob.LNX-ramdisk.cpio.gz
creating boot image...
creating boot image - 4214784 bytes
downloading 'boot.img'...
OKAY [ 0.748s]
booting...
FAILED (remote: ()
finished. total time: 0.749s
Prime displays: Failed to process command boot error(0x120000)
Any advice?
saturn_de said:
Hmm.. Does not seem to work for me. Built a kernel, switched in fastboot mode. Then:
Code:
$ sudo ./fastboot -i 0x0b05 boot zImage blob.LNX-ramdisk.cpio.gz
creating boot image...
creating boot image - 4214784 bytes
downloading 'boot.img'...
OKAY [ 0.748s]
booting...
FAILED (remote: ()
finished. total time: 0.749s
Prime displays: Failed to process command boot error(0x120000)
Any advice?
Click to expand...
Click to collapse
Yes. fastboot boot does not work at all.And we also found out that kernel flashing via fastboot does not work either.
You have to flash your kernels via a custom made blob ;-)
Gesendet von meinem Desire HD mit Tapatalk
Prime Stuck in CWM boot loop hell.
I have a Prime that is stuck in a CWM Recovery boot loop.
Brick 1a
All thanks (sincerely) to Viperboy and his ViperMOD PrimeTime 4.5, I had my Prime rooted, boot loader unlocked and loaded with ClockworkMOD Recovery 5.5.0.4.
I used CWM to create a backup, wipe the data/factory, cache partition and Dalvik cache, rebooted the system (from CWM menu) just to verify that the unit was really wiped back to setup, powered down the unit, rebooted into CWM Recovery (using Power while holding Vol.Down, wait for small/white text, Vol.Up) and Restored using the previously created Backup.
I rebooted Android from CWM menu and my Prime was restored.
Everything was great, but not for long.
The next time that I booted into CWM recovery I selected “Reboot System Now”.
It went dark, displayed the ASUS splash screen, went dark and went back into CWM.
I am stuck in that loop.
I have tried all the suggested fixes I can find but all methods are useless because:
1. I can’t acquire an ADB connection because Windows doesn’t identify the bricked Prime correctly and won’t install the USB drivers. Device Manager sees “Full Android as Emulator”.
2. I can’t boot into the boot loader to use Fastboot because I never see the option to choose it. It boots or reboots directly into CWM after “Booting Recovery Kernel Image”, ever while holding the Vol.Down button.
I have repeatedly tried installing and uninstalling the drivers by installing and uninstalling the Asus Sync and Asus Android USB Drivers. I have repeatedly tried to install the drivers via the Device Manager. No good. I’ve installed and uninstalled Android SDK Tools repeatedly.
Is there a way out of this? I hope I'm not efed.
Thank you in advance for any help.
Temporalmind said:
I have a Prime that is stuck in a CWM Recovery boot loop.
Brick 1a
[..]
I apologize for the length of this post. I hope I’m not efed.
Click to expand...
Click to collapse
Please try to manually installing these drivers here
http://forum.xda-developers.com/showthread.php?t=1426502
Adb should be working afterwards
Universal Naked Driver works great!
Ok, you saved me and my precious.
Your drivers were exactly what I needed.
After installing them in Device manager I was able to achieve a “ASUS Android Composite ADB Interface” connection.
Following the “How to Unbrick your Transformer Prime (or not)”, Option 1a and restoring I’m up and running.
Thank you!
Then, I deliberately caused the boot looping condition again to see if I could figure out how I got there.
There is an app that I think comes preinstalled on the Prime called ”Transformer Recovery Boot”. The icon is labeled "Recovery". This is the app that took me into the Brick 1a the first time and I duplicated it the next time I used it.
Then I was able to ADB my way back to civilization, again.
Thought I’d pass that on incase it helps to determine why the unlocked Prime seems to be so susceptible to bricking.
Again, Thank You!
Hey XDA, can we talk? cause im about to cry man tears.
First off you are much better at android then I am, this isn't me trying to sound humble, I suck and the threat of bricking my toys scares me.
Today I found a way to get root access without unlocking my bootloader and I was thrilled, it was easy and it worked! I had root access and then decided I was going to try to install CyanogenMod 10 (latest nightly) and so I installed ROM Manager and downloaded CyanogenMod, when I tried to boot to recovery mode (hold down volume and power, then up volume) I would get the dead android with an exclamation point, every time.
So I decided to unlock my bootloader, I went searching and came across the ASUS official bootloader unlocker and it said the unlocker was for ICS and I have already upgraded the ASUS rom to jellybean, I decided to try the unlock device app anyway and now when I restart the words "this device is unlocked" show in the top left corner, I thought that meant the bootloader is unlocked but when I restart into recovery mode I still get the dead android.
I cant find any information anywhere about how to unlock an ASUS jellybean bootloader and I am only guessing that why I keep getting the dead android.
Anyway, if you can help thats awesome, I am usually the kind of guy that can read and find the answers but **** me if I cant find them anywhere, I was never good at the world of bootloaders, whether PC or Android and I am hoping to find a hand and learn something more here
Thanks
I know its my first time here to post but I have read loads of stuff off this site.
78 people read this already, one of you must be able to point my dumbass in the right direction?
bueller, bueller ...:crying:
Once I get an idea of what I am doing wrong and why I keep getting the dead android, I think I will try to install AndroWook 2.2
ArghMonkey said:
Once I get an idea of what I am doing wrong and why I keep getting the dead android, I think I will try to install AndroWook 2.2
Click to expand...
Click to collapse
You are unlocked but you do not have a custom recovery installed yet.
Go to the TWRP thread and follow the instructions for installing TWRP for the JB bootloader. Do not install CWM.
Make sure you get the correct TWRP for the JB bootloader.
flumpster said:
You are unlocked but you do not have a custom recovery installed yet.
Go to the TWRP thread and follow the instructions for installing TWRP for the JB bootloader. Do not install CWM.
Make sure you get the correct TWRP for the JB bootloader.
Click to expand...
Click to collapse
Sweet, im on it right now
Wow, there are TWRP threads everywhere, several downloads, I even did a search within the transformer prime subthread and cant find one version mentioned for the JB bootloader.
Ill keep looking ...
Lost again.
So I found this
http://teamw.in/project/twrp2/93
But then I read this
"We STRONGLY recommend users enable and backup your device before flashing custom roms/recoveries with nvflash courtesy of AndroidRoot.mobi (this also makes your device essentially "brick-proof") - you need to be on the ICS bootloader to do this, if you have taken the JB OTA from Asus you cannot get nvflash access.
If you have updated to the JB OTA bootloader then you must use the -JB version of the recovery, flashing the non -JB version could potentially permanently brick your device (unless you have nvflash as noted above)."
And have no idea which way I should proceed, should I downgrade? no idea how to do that, I think I read somewhere if I have the official formware updates from ASUS that I can stick it on my microSD and the asus recovery will see it and install the downgrade.
Or should I just go for it, that bricking is a risk but low?
I know I am running jellybean but I still dont have a clue exactly what bootloader I have, I assume there are several versions under jellybean but I cant find any guides to tell me exactly where to find what bootloader version I have.
1: Can anyone tell me how I find exactly which bootloader I am running? I have JB installed (4.1.1)
2: So what version of TWRP do I need to download?
3: How would I install TWRP?
and yes, I am unlocked and rooted, help!
Download TWRP 2.5.0.0 for JB blob from here: http://teamw.in/project/twrp2/93
Rename to twrp.blob
Use command prompt on your computer to flash recovery to tablet using this command: fastboot -i 0x0b05 flash recovery twrp.blob
....................
Follow this thread: http://forum.xda-developers.com/showthread.php?t=2038464
---------- Post added at 12:37 PM ---------- Previous post was at 12:35 PM ----------
ArghMonkey said:
Lost again.
So I found this
http://teamw.in/project/twrp2/93
But then I read this
"We STRONGLY recommend users enable and backup your device before flashing custom roms/recoveries with nvflash courtesy of AndroidRoot.mobi (this also makes your device essentially "brick-proof") - you need to be on the ICS bootloader to do this, if you have taken the JB OTA from Asus you cannot get nvflash access.
If you have updated to the JB OTA bootloader then you must use the -JB version of the recovery, flashing the non -JB version could potentially permanently brick your device (unless you have nvflash as noted above)."
And have no idea which way I should proceed, should I downgrade? no idea how to do that, I think I read somewhere if I have the official formware updates from ASUS that I can stick it on my microSD and the asus recovery will see it and install the downgrade.
Or should I just go for it, that bricking is a risk but low?
I know I am running jellybean but I still dont have a clue exactly what bootloader I have, I assume there are several versions under jellybean but I cant find any guides to tell me exactly where to find what bootloader version I have.
Click to expand...
Click to collapse
You can't use NVFlash because you are on the JB bootloader. You can't downgrade to ICS.
Great links!
Thanks for your help, I will report back once I try this
ArghMonkey said:
Great links!
Thanks for your help, I will report back once I try this
Click to expand...
Click to collapse
Any update? I've had my Prime for over a year. Rooted tonight, looking to unlock the bootloader and flash a custom ROM. Interested to hear the results.
Flash TWRP:
Once unlocked, power it off. Once off power it on by holding BOTH volume down and power buttons. When you see the menu appear the first option is RCK. press Volume Down to change the cursor to be over the USB logo (two presses of the button) and press volume up. This puts your device in fastboot mode
Back on your computer you should hopefully see a successfull driver install for fastboot. I got all my drivers from downloading and installing the Android SDK so you may or may not need to do that. Android SDK
If all is prepared and you are in fastboot with drivers loaded:
On your computer hold shift and right click on the folder where fastboot and the twrp.blob file are and you will see a context menu. Click on "Open Command Window Here" (Vista + only or if you installed powertools on 2000/XP)
Click to expand...
Click to collapse
Ok, so I followed your link, I downloaded the Android SDK and when I opened it I see a million things, the Google USB Driver was highlighted so I installed it, are there other drivers im supposed to install before I go to the next step?!
Lavman72 said:
Any update? I've had my Prime for over a year. Rooted tonight, looking to unlock the bootloader and flash a custom ROM. Interested to hear the results.
Click to expand...
Click to collapse
Working on it right now, flashed twrp over, prime is starting up right now *fingers crossed*
and yes! it booted to stock, now to transfer over supersu ...
Awesome TWRP is alive and in charge, now to flash with Androwook!
It aint over but its getting close
ArghMonkey said:
Awesome TWRP is alive and in charge, now to flash with Androwook!
It aint over but its getting close
Click to expand...
Click to collapse
That's great news. Did you follow the steps on this thread?
http://forum.xda-developers.com/showthread.php?t=2038464
Any suggestions or pointers? I've rooted/installed custom roms on many phones, but this one seems to be the most complicated/risky.
Lavman72 said:
That's great news. Did you follow the steps on this thread?
http://forum.xda-developers.com/showthread.php?t=2038464
Any suggestions or pointers? I've rooted/installed custom roms on many phones, but this one seems to be the most complicated/risky.
Click to expand...
Click to collapse
Yup, thats how i did it.
The biggest obstacle is unclear instructions or instructions that assume the reader is not a noob *L*
ArghMonkey said:
Yup, thats how i did it.
The biggest obstacle is unclear instructions or instructions that assume the reader is not a noob *L*
Click to expand...
Click to collapse
Excellent. I'll probably give it a go in the next couple of days. Strange that the Unlock tool works. I've read other posts that state if you are already on JB (which I am) the unlook tool won't work.
Lavman72 said:
Excellent. I'll probably give it a go in the next couple of days. Strange that the Unlock tool works. I've read other posts that state if you are already on JB (which I am) the unlook tool won't work.
Click to expand...
Click to collapse
Everything is totally installed and working great now, Whew, what a relief!
Thanks folks!
ArghMonkey said:
Everything is totally installed and working great now, Whew, what a relief!
Thanks folks!
Click to expand...
Click to collapse
Rooted: Check
Unlocked bootloader: Check
Tired though, and it's late. So I'm going to hold off on the final steps.
Okay, I bought this Transformer Prime from my brother. I tried getting a custom recovery on it once, and I hard bricked it. I got a super lucky fix ($40), and it's back to being new again. Now, I really want Cyanogenmod on it, along with a good custom recovery (I'm partial to Clockword Mod, but open to suggestions). It currently has Android 4.1.1 on it, and I've looked up step by step instructions online on how to install CWM and CM9.1 and CM10 on it, but every description is way different than the various screens my Prime gives me. There is no Eee Pad screen, it just says Asus. When I hold down the Volume Down and Power, it gives me a screen with four different icons to choose from. This is where I died last time. Currently it has Root and the bootloader is unlocked, but that's as far as I've been willing to go. Anyone able to point me in the direction of more recent updates/directions so that I can be sure to get something that suits my tablet? And I'm pretty familiar with Android for phones, been rooting, hacking, what have you those for a few years now. Thanks!
Get your NVFlash blobs first, that will help prevent a brick again. Here is the thread in the development forum http://forum.xda-developers.com/showthread.php?t=2455920
jjubenv said:
Get your NVFlash blobs first, that will help prevent a brick again. Here is the thread in the development forum http://forum.xda-developers.com/showthread.php?t=2455920
Click to expand...
Click to collapse
I've seen a couple things on nvflash, and been to that tutorial page before. What I'm confused on and haven't seen a clear answer to is, how in the world do I download it? Is it something that can even be downloaded, or is it embedded into the bootloader and I just need to access it?
*Edit* Nevermind, found what my brain was missing all this time. This is why I don't like attempting stuff after getting home from work, I usually wait till a day off.
Anyone know a good tutorial for my other two questions?
Once I figured out the NVFlash thing, I read around about ROMS (It seems like you already have some familiarity with these). I picked a ROM that is really well supported on this site (HairyBean http://forum.xda-developers.com/showthread.php?t=2407248 ) and I read the whole devel thread. It's recently released and so the instructions are relevant and current. There is a good video link by wwjoshdew in the first post which showed me what I should expect and what a normal install should look like (the forum thread shows brief "Works for me, this is great!" posts and bunch of "I have this problem" or "that problem" posts which could be off putting). So I installed TWRP from HairyBean instead of CWM (I like the GUI touch stuff) and HairyBean after that and had great success. I don't have any affiliation with the Androwook team, or HairyBean, but I they have a stable ROM and it is very well supported (Thanks to flumpster and the team). Now I like my Prime even more.
How do you install TWRP from HairyBean, then install HairyBean? I'll work on NVFlash this weekend.
It's in the first install step in the first post of the HairyBean thread. Just watch the video in that first post and he shows you step by step. The HairyBean bootloader and TWRP are installed in the first step. The video (also in the first post of the HairyBean devel thread) shows you how to get into recovery, he goes into TWRP, which he had installed before. You will have a new recovery partition (CWM I believe) once you make your NVFlash blobs. You can use that to flash the HairyBean bootloader and TWRP at the same time (It's one ZIP file) from a MicroSD card. No need to unzip it, just put it on the root of the MicroSD card and select that to install. (I can't remember the exact steps to do this from the CWM install left over by the NVFlash process).
jjubenv said:
It's in the first install step in the first post of the HairyBean thread. Just watch the video in that first post and he shows you step by step. The HairyBean bootloader and TWRP are installed in the first step. The video (also in the first post of the HairyBean devel thread) shows you how to get into recovery, he goes into TWRP, which he had installed before. You will have a new recovery partition (CWM I believe) once you make your NVFlash blobs. You can use that to flash the HairyBean bootloader and TWRP at the same time (It's one ZIP file) from a MicroSD card. No need to unzip it, just put it on the root of the MicroSD card and select that to install. (I can't remember the exact steps to do this from the CWM install left over by the NVFlash process).
Click to expand...
Click to collapse
I got pretty far in the NVflash process, but when I try to direction that says to run "wheelie --blob blob.bin" while the tablet is in APX mode, I get "Error 3 receiving response from command". Google has been fruitless. Any ideas?
You may want to try asking for help in the flatline NVFlash thread in the Development forum, I didn't have any problems and I don't know the components well enough to help you you out. Sorry.
Yeah, I did that. There was one other guy on there having the same problem and I never saw a resolution posted. Here goes though.
Ugh, this always happens to me! I have a problem, I post about it on topics started by the developers that people had been posting on all day every day since it was started, and suddenly the posts dry up.
I am on rooted Thor with 13.3.2.4, with the Nexus Rom installed via safestrap. I have been reading all the threads on unlocking the bootloader and find all of the steps to be very scary. I would like to wait until there was some kind of "toolkit" for this rather than having to first downgrade and then use python through adb etc which I am somewhat uncomfortable with. Will there ever be such a simpler solution?
The bootloader unlock procedure is a no brainer, can't mess up anything there. Downgrading is a little risky, but you're on 3.2.4, thus you can even use the rollback images for Safestrap, take a look at this thread (page 1 is about 3.2.5/3.2.6 users who can NOT use the downgrade images). I'm afraid it won't get any easier than that.
If you don't want to use Python, just execute the adb commands to get your ID and serial (post them here, or PM me if you don't want anyone to see them), I'll create the .unlock file for you then. Downgrading and (actual) unlocking are tasks you have to do yourself though.
I think I might try it this weekend. Thanks for the help.
Cl4ncy said:
The bootloader unlock procedure is a no brainer, can't mess up anything there. Downgrading is a little risky, but you're on 3.2.4, thus you can even use the rollback images for Safestrap, take a look at this thread (page 1 is about 3.2.5/3.2.6 users who can NOT use the downgrade images). I'm afraid it won't get any easier than that.
If you don't want to use Python, just execute the adb commands to get your ID and serial (post them here, or PM me if you don't want anyone to see them), I'll create the .unlock file for you then. Downgrading and (actual) unlocking are tasks you have to do yourself though.
Click to expand...
Click to collapse
I have successfully downgraded to 13.3.1.0, but I am confused about how to install TWRP. Since I have not enabled wifi and registered, I can't install flashify or cwm, or even install a file explorer apk to access my storage, and I don't know how to get the twrp.img file (which I guess I can only install via adb?) Where do I get the correct twrp.img file? I'm kind of stuck....
kbs24 said:
I have successfully downgraded to 13.3.1.0, but I am confused about how to install TWRP. Since I have not enabled wifi and registered, I can't install flashify or cwm, or even install a file explorer apk to access my storage, and I don't know how to get the twrp.img file (which I guess I can only install via adb?) Where do I get the correct twrp.img file? I'm kind of stuck....
Click to expand...
Click to collapse
I am by no means an expert but I just went through this process myself yesterday and it was relatively simple. Check this thread. It has a number of helpful posts in it, including my questions from yesterday.
The correct TWRP image is here. Just follow the instructions in that thread. It's super simple if you use the minimal adb and fastboot linked by Cl4ncy in the first thread I linked. If you have any other questions I'll do my best to help you.
kbs24 said:
I have successfully downgraded to 13.3.1.0, but I am confused about how to install TWRP. Since I have not enabled wifi and registered, I can't install flashify or cwm, or even install a file explorer apk to access my storage, and I don't know how to get the twrp.img file (which I guess I can only install via adb?) Where do I get the correct twrp.img file? I'm kind of stuck....
Click to expand...
Click to collapse
Sorry for the late reply, @muunkin pointed you in the right direction already.
Be sure to (re-)root 3.1.0 and disable OTA via HDX ToolKit, and enable USB debugging in Fire OS, hope you installed minimal adb and fastboot, then copy the TWRP image for your HDX (Thor = 7", Apollo = 8.9") to the root of the sdcard (which is the directory you'll see in Explorer after connecting the HDX to your PC, i.e. don't open another directory), open a DOS box, change dir to the adb directory (enter cd\adb) and enter the commands mentioned in the TWRP thread. This will flash the TWRP image to the recovery parition.
Do a backup of your Fire OS in TWRP before you flash any custom ROM, and copy it to your PC, also look for the TWRP backup of the stock recovery (I think TWRP does a backup somewhere), and move that to your PC as well.
In case you don't know how to access TWRP: with the HDX powered off, you press and hold volume up, then press and hold the power button, release both when the grey Kindle Fire logo appears on screen. Some ROMs (e.g. CM12) offer the advanced reboot in developer options, this will add options to reboot into recovery, bootloader or a soft (quick) reboot to the power menu.
Cl4ncy said:
Sorry for the late reply, @muunkin pointed you in the right direction already.
Be sure to (re-)root 3.1.0 and disable OTA via HDX ToolKit, and enable USB debugging in Fire OS, hope you installed minimal adb and fastboot, then copy the TWRP image for your HDX (Thor = 7", Apollo = 8.9") to the root of the sdcard (which is the directory you'll see in Explorer after connecting the HDX to your PC, i.e. don't open another directory), open a DOS box, change dir to the adb directory (enter cd\adb) and enter the commands mentioned in the TWRP thread. This will flash the TWRP image to the recovery parition.
Do a backup of your Fire OS in TWRP before you flash any custom ROM, and copy it to your PC, also look for the TWRP backup of the stock recovery (I think TWRP does a backup somewhere), and move that to your PC as well.
In case you don't know how to access TWRP: with the HDX powered off, you press and hold volume up, then press and hold the power button, release both when the grey Kindle Fire logo appears on screen. Some ROMs (e.g. CM12) offer the advanced reboot in developer options, this will add options to reboot into recovery, bootloader or a soft (quick) reboot to the power menu.
Click to expand...
Click to collapse
Thank you both @muunkin and @Cl4ncy for guiding me through this. It is clear now that I have to flash TWRP via adb. Unfortunately I did, however, last night briefly turn on wifi in order to get es file explorer, and very quickly the OS ugraded itself to 13.3.2.3. Then, stupidly, I decided to go back to Nexus rom 2.0.2, which I did by reinstalling safestrap. And, Nexus rom is installed on the Stock Rom slot, and I did NOT backup the 13.3.2.3 stock rom. SO, since I am on Nexus rom, do I understand correctly that I need to begin again by downgrading to 13.3.1.0? Right? (After printing out all of these threads and printing out a lot of it and carefully reading, it looks to me like if I had stayed on stock 13.3.2.3 I would not have had to downgrade.....but too late now anyway.) I do have the minimal adb and fastboot installed, and my device is recognized, so eventually this will work I'm pretty sure. I appreciate the help!
kbs24 said:
Thank you both @muunkin and @Cl4ncy for guiding me through this. It is clear now that I have to flash TWRP via adb. Unfortunately I did, however, last night briefly turn on wifi in order to get es file explorer, and very quickly the OS ugraded itself to 13.3.2.3. Then, stupidly, I decided to go back to Nexus rom 2.0.2, which I did by reinstalling safestrap. And, Nexus rom is installed on the Stock Rom slot, and I did NOT backup the 13.3.2.3 stock rom. SO, since I am on Nexus rom, do I understand correctly that I need to begin again by downgrading to 13.3.1.0? Right? (After printing out all of these threads and printing out a lot of it and carefully reading, it looks to me like if I had stayed on stock 13.3.2.3 I would not have had to downgrade.....but too late now anyway.) I do have the minimal adb and fastboot installed, and my device is recognized, so eventually this will work I'm pretty sure. I appreciate the help!
Click to expand...
Click to collapse
No, 13.3.2.3 is ok for both TWRP and unlocking the bootloader, i.e. no need to flash 3.1.0 again - a firmware below 3.2.4 is enough.
Cl4ncy said:
No, 13.3.2.3 is ok for both TWRP and unlocking the bootloader, i.e. no need to flash 3.1.0 again - a firmware below 3.2.4 is enough.
Click to expand...
Click to collapse
Even if I am not running on the stock rom? I can adb install TWRP while on Nexus rom?
kbs24 said:
Even if I am not running on the stock rom? I can adb install TWRP while on Nexus rom?
Click to expand...
Click to collapse
Hm, I'm not exactly sure about this - @ggow's answer here seems to point out that you really have to do it all over again.
Why did you install Safestrap again anyway? ADB-flashing TWRP and unlocking the bootloader before you install a custom ROM would've been the next steps. Also I told you to create a backup of your stock slot before you flash any custom ROM, didn't I?
Cl4ncy said:
Hm, I'm not exactly sure about this - @ggow's answer here seems to point out that you really have to do it all over again.
Why did you install Safestrap again anyway? ADB-flashing TWRP and unlocking the bootloader before you install a custom ROM would've been the next steps. Also I told you to create a backup of your stock slot before you flash any custom ROM, didn't I?
Click to expand...
Click to collapse
Yes you sure did, and that's why I said "stupidly" about me putting safestrap back and nexus rom. I was overanxious and acted impulsively, not having a recovery installed was freaking me out. Bad habit. About doing the backup, there did not appear to be enough room on the internal storage. Sorry. We'll start over no problem. Again thanks.
kbs24 said:
Yes you sure did, and that's why I said "stupidly" about me putting safestrap back and nexus rom. I was overanxious and acted impulsively, not having a recovery installed was freaking me out. Bad habit. About doing the backup, there did not appear to be enough room on the internal storage. Sorry. We'll start over no problem. Again thanks.
Click to expand...
Click to collapse
I'm also not sure how to do this now. You don't have any Safestrap 3.2.3 Fire OS backup to restore, you shouldn't use the 3.2.4 rollback image, as you're not on 3.2.4, so what do you want to flash to the stock slot now? Or did I miss anything?
Cl4ncy said:
I'm also not sure how to do this now. You don't have any Safestrap 3.2.3 Fire OS backup to restore, you shouldn't use the 3.2.4 rollback image, as you're not on 3.2.4, so what do you want to flash to the stock slot now? Or did I miss anything?
Click to expand...
Click to collapse
I was going to look for a stock 3.2.3 to flash. If can't find, I do have a backup of stock 3.2.4 on the card which I would flash, thus requiring the downgrade.
kbs24 said:
I was going to look for a stock 3.2.3 to flash. If can't find, I do have a backup of stock 3.2.4 on the card which I would flash, thus requiring the downgrade.
Click to expand...
Click to collapse
I haven't seen a 3.2.3 Safestrap flashable Image, good luck. Regarding the 3.2.4 backup I'm not sure whether it works with the 3.2.3 bootloader.
Cl4ncy said:
I haven't seen a 3.2.3 Safestrap flashable Image, good luck. Regarding the 3.2.4 backup I'm not sure whether it works with the 3.2.3 bootloader.
Click to expand...
Click to collapse
Yeah, I am probably screwed. But we'll see. I'm pretty sure I understand what the process should be at least.
kbs24 said:
Yeah, I am probably screwed. But we'll see. I'm pretty sure I understand what the process should be at least.
Click to expand...
Click to collapse
Not sure how far you got with this but you *should* be able to flash TWRP from Nexus provided the version of FireOS was 3.2.3.2 or lower prior to the installation of Safestrap v3. The customized version of twrp leverages a vulnerability in the HDX bootloader that is installed with FireOS. Neither Safestrap nor Nexus mess with the bootloader so the prerequisites should remain intact. I say should as interactions are complex - further complicated by a fussy device with limited recovery capability should something go wrong. To the best of my knowledge no one has attempted a twrp flash from Nexus while Safestrap v3 is installed.
Thoughts:
- grab flashify from the play store or here; make a backup of your current recovery environment (this step will also help to familiarize you with flashify)
- download the HDX customized version of twrp (here); use ES File Explorer to verify MD5
- use flashify to install twrp (can also be done via adb commands as shown in the twrp op)
Options:
- unlock the bootloader before attempting other remedial steps. Unlocking is a frustrating but low/no risk activity that yields substantially improved recovery capabilities once completed. Yep - you can do this without twrp (unlocking before flashing twrp is the recommended path according to several devs - although I prefer the opposite).
[-or-]
- flash 3.1.0 from here to the stock slot and then attempt to remove Safestrap v3. If successful you can proceed with flashing twrp unlocking, etc in the normal manner. As with any flash there is a risk something will go wrong or FireOS will not start up properly. To help mitigate the latter suggest installing a fallback version of Nexus v2 in a secondary slot. Don't forget to remove this slot before uninstalling SS.
The above is only an outline. Give it some thought and post any questions BEFORE taking action. I also suggest you let this post sit for a few days in case some of the rational is fatally flawed. Lots of smart people in the community who will jump in if my guidance is misdirected (which it has been shown to be on occasion). Don't risk a brick by acting too quickly. Proper preparation is essential for a successful outcome.
Sorry for sounding like your mum ... :angel:
Davey126 said:
Not sure how far you got with this but you *should* be able to flash TWRP from Nexus provided the version of FireOS was 3.2.3.2 or lower prior to the installation of Safestrap v3. The customized version of twrp leverages a vulnerability in the HDX bootloader that is installed with FireOS. Neither Safestrap nor Nexus mess with the bootloader so the prerequisites should remain intact. I say should as interactions are complex - further complicated by a fussy device with limited recovery capability should something go wrong. To the best of my knowledge no one has attempted a twrp flash from Nexus while Safestrap v3 is installed.
Thoughts:
- grab flashify from the play store or here; make a backup of your current recovery environment (this step will also help to familiarize you with flashify)
- download the HDX customized version of twrp (here); use ES File Explorer to verify MD5
- use flashify to install twrp (can also be done via adb commands as shown in the twrp op)
Options:
- unlock the bootloader before attempting other remedial steps. Unlocking is a frustrating but low/no risk activity that yields substantially improved recovery capabilities once completed. Yep - you can do this without twrp (unlocking before flashing twrp is the recommended path according to several devs - although I prefer the opposite).
[-or-]
- flash 3.1.0 from here to the stock slot and then attempt to remove Safestrap v3. If successful you can proceed with flashing twrp unlocking, etc in the normal manner. As with any flash there is a risk something will go wrong or FireOS will not start up properly. To help mitigate the latter suggest installing a fallback version of Nexus v2 in a secondary slot. Don't forget to remove this slot before uninstalling SS.
The above is only an outline. Give it some thought and post any questions BEFORE taking action. I also suggest you let this post sit for a few days in case some of the rational is fatally flawed. Lots of smart people in the community who will jump in if my guidance is misdirected (which it has been shown to be on occasion). Don't risk a brick by acting too quickly. Proper preparation is essential for a successful outcome.
Sorry for sounding like your mum ... :angel:
Click to expand...
Click to collapse
Thanks for your input. I am still on the nexus rom, but I am fairly sure that Safestrap was installed while on 13.3.2.4. Is there a way to tell? It is safestrap 3.75, based on twrp 2.7.
I had some time today to work on this, and after looking over the ideas from all of you (thank you very much!) it seemed that my only option is to restore my backup which will get me back to the Nexus 2.0.2 rom. So I did this successfully. Being on Nexus rom, I was then able to use the 13.3.2.4 rollback file to get back to 13.3.0.9. Then ran into trouble......the system update to 13.3.1.0 was not successful. the .bin file was located, but all that happened was a "validating update file" followed by forced reboot. I remain stuck on 13.3.0.9. There are threads discussing editing build.prop but I know I did not have to do this when I first did a rollback a few days ago. Not sure whether to give up or maybe someone has another idea how to get the system to use that .bin file? Should I turn on wifi and wait for an ota or is that too risky, will it jump me all the way up to the most current build? Will it maybe go incrementally?
kbs24 said:
Thanks for your input. I am still on the nexus rom, but I am fairly sure that Safestrap was installed while on 13.3.2.4. Is there a way to tell? It is safestrap 3.75, based on twrp 2.7.
Click to expand...
Click to collapse
(Also as you suggested, I did try flashing the zip 3.1.0 and it did not work, never rebooted successfully. So went back again to 3.0.9.)
kbs24 said:
I had some time today to work on this, and after looking over the ideas from all of you (thank you very much!) it seemed that my only option is to restore my backup which will get me back to the Nexus 2.0.2 rom. So I did this successfully. Being on Nexus rom, I was then able to use the 13.3.2.4 rollback file to get back to 13.3.0.9. Then ran into trouble......the system update to 13.3.1.0 was not successful. the .bin file was located, but all that happened was a "validating update file" followed by forced reboot. I remain stuck on 13.3.0.9. There are threads discussing editing build.prop but I know I did not have to do this when I first did a rollback a few days ago. Not sure whether to give up or maybe someone has another idea how to get the system to use that .bin file? Should I turn on wifi and wait for an ota or is that too risky, will it jump me all the way up to the most current build? Will it maybe go incrementally?
Click to expand...
Click to collapse
Glad you were able to make some progress. I believe you could have flashed twrp from Nexus as I believe you successfully downgraded/upgraded to 13.3.2.3 which would then be the base version when you reininstalled Safestrap. But you found another path which is just fine.
It is possible the 13.3.1.0 is invalid (possibly corrupt). You can use ES File Explorer to validate the MD5 (c49c0363de4d8dfa5c87c1bdb88aa2ba) or download a fresh copy here. You can also upgrade directly to 13.3.2.3 instead of hopscotching through 13.3.1.0 and then applying the 13.2.3.3 bootloader update.
I strongly suggest you NOT connect to WiFi as it is unpredictable if/when you will receive at OTA and what version will be downloaded. Options for getting files onto you device:
- use HDX toolkit to root and block OTA on 13.3.0.9; you can then enable WiFi
- tether your device and drop files into "Internal Storage"
- use 'adb push' to transfer files
You should not need to mess with build.prop as the 3.2.4->3.0.9 rollback should have handed that. It's quite easy to brick your device if you get any of the edits or permissions wrong.