Key Features:
Ability to save custom recovery settings
Default partitions to back up
Default zip folder location
Default color theme (lots to choose from) (Thanks to ffolkes!)
Default Time Zone (for more accurate time stamps)
Zip Signature Verification
Zip md5 Verification (looks for file with zipname.zip.md5)
Ability to flash multiple zips in one go
Ability to select which individual partitions to backup, and restore.
Ability to choose compression or no compression backups.
Compression takes longer of course, but you save roughly half the space. EVO3D's stock system uncompressed is ~800mb, 380mb compressed. You choose.
Ability to auto restore GAPPS on zip flash (for CM based ROMS)
Ability to auto reboot after successful flashes (for the lazy)
Some devices utilize their capacitive buttons in recovery.
Home - Main Menu
Menu - Advanced Menu
Back - Up a Menu Level
Search - Select Current Selection
Battery Level and Timestamp (Better safe than sorry)
HTC Dumlock Instructions:
Install the build of TWRP using your method of choice, but you must actually flash TWRP to recovery. No fastboot booting it. We need it in recovery so that this build of TWRP will be flashed to your boot. This new build of TWRP has features in it to easily restore your original boot.
Reboot into recovery.
Make a backup of your phone.
Tap Advanced.
Tap HTC Dumlock. (If you don't see HTC Dumlock then you need to remove any custom TWRP theme that you might be using.)
Tap Install HTC Dumlock. This will install the app and binaries needed to make everything work nicely.
Reboot your device.
Find and open the HTC Dumlock app.
If/when prompted, give the app root (SuperUser) permissions.
Tap the Execute HTC Dumlock button.
Wait patiently for a couple of minutes. It takes a little while.
If your device doesn't reboot automatically, reboot it manually. Reboot it normally. DO NOT reboot it to recovery.
You should now be in your recovery, but your recovery is flashed into boot.
Tap Advanced.
Tap HTC Dumlock.
Tap Restore Original Boot.
Use your recovery like normal. Flash a new kernel. Restore a backup with a different kernel. Do whatever you please!
Consider donating!
Note, you must repeat steps 8 through 17 EVERY TIME you need to flash boot.
Installation:
Unlock bootloader at http://www.htcdev.com/bootloader/
Make sure fastboot is unchecked in power options and turn phone completely off
Boot into HBOOT then Fastboot
From fastboot. Use command "fastboot erase cache"
From fastboot. Use command "fastboot flash recovery recovery.img"
Video Tutorials:
How To Unlock The Bootloader EASIEST Method - https://www.youtube.com/watch?v=r0gzJdwCxX0
How To ROOT EASIEST METHOD - https://www.youtube.com/watch?v=S1KmsxO84UU
PC USB Mass Storage:
You can't! http://teamw.in/DataMedia
Downloads:
If rooted. You can flash using GooManager in the Play Store
http://techerrata.com/browse/twrp2/m7/
Thanks..
I have a buddy who is picking one up this week.. We all have the "one" from sprint and it works great.
Just ordered mine
Sent from my HTC One S
and you continue to pop up everywhere! lol. I can see it's the same recovery for the int'l/at&t models. I'll just mirror my toolkit here as well!
hasoon2000 said:
and you continue to pop up everywhere! lol. I can see it's the same recovery for the int'l/at&t models. I'll just mirror my toolkit here as well!
Click to expand...
Click to collapse
hahahaha I'll try to pop up on every new HTC device. :laugh:
hasoon2000 said:
and you continue to pop up everywhere! lol. I can see it's the same recovery for the int'l/at&t models. I'll just mirror my toolkit here as well!
Click to expand...
Click to collapse
Great! I used your Toolkit for my girlfriends One S! Keep up the great work. I should be going to the Tmo Store soon to decide if I want it or not.
Weird I am unable to have any zips show up here so I can flash them.. any idea why nothing shows up in TWRP?
Sent from my HTC One
I just tried using adb sideload and it transferred the rom zip, and the rom looked like it was installing, it even said it was installed. However, when I went to reboot, TWRP says 'are you sure no OS installed?' sure enough, i got stuck at the HTC One screen for a long time afterwards. The rom installed fine with adb push, then installing it. Just wondering if this is me or other people experience it.
Billyvnilly said:
I just tried using adb sideload and it transferred the rom zip, and the rom looked like it was installing, it even said it was installed. However, when I went to reboot, TWRP says 'are you sure no OS installed?' sure enough, i got stuck at the HTC One screen for a long time afterwards. The rom installed fine with adb push, then installing it. Just wondering if this is me or other people experience it.
Click to expand...
Click to collapse
Idk about this phone but did you make sure the boot.img was installed. Try flashing manually the boot.img.
Can anyone help please.I flashed twrp v 2.5.0.0 but I think I checked fast boot in power for some reason . Now twrp is giving me some problems like it doesn't recognise my internal storage and can't flash supersu or superu ,so my device is still unrooted. Could anybody tell me what should I do now? Thanks in advance and sorry guys if I'm using the wrong thread.
Sent from my HTC One using xda app-developers app
Delete.
Hello everyone... I really like the way TWRP works even though the backup files seem to be proprietary. I especially like the way the wipe area allows you to select other specific items under "advanced." One question I have though is this... is the "fix permissions" option working for everyone? Would this not work on certain ROMs? I am just curious. Thanks for your insight!
cant flash the recovery. it says out of memory :/
help pls
Could someone please link me to a flashable zip? No OS installed. outdated TWRP >_<
i want to ask that if i can flash that recovery then rooted my phone then back to stock recovery my HTC GPE works or not ??
sadeg111 said:
i want to ask that if i can flash that recovery then rooted my phone then back to stock recovery my HTC GPE works or not ??
Click to expand...
Click to collapse
It should work as long your bootloader is unlock.
Related
Hi,
I traded a phone with someone and the rom they had was acting up.. the Infected Rom (cdma verizon)... When I got the phone, I told him he could keep his SD card and I could keep mine.. i guess the P something image file was on there and now Im just rooted with Teamwin recovery and not able to flash any rom or restore the Infected rom i nandroid backed up.
I have fastboot 1.50 S On but unlocked
Now imma be at work and not have a working phone. This isn't cool. PLEASE GET BACK TO ME IF YOU CAN HELP peeps. I would really appreciate it.
I also tried the unlocking method all over again but the Java SDK wont install.. it tells me to disable my virus protection (I did) and then it says unable to install it. This is just a mess man.
stepinmyworld said:
Hi,
I traded a phone with someone and the rom they had was acting up.. the Infected Rom (cdma verizon)... When I got the phone, I told him he could keep his SD card and I could keep mine.. i guess the P something image file was on there and now Im just rooted with Teamwin recovery and not able to flash any rom or restore the Infected rom i nandroid backed up.
I have fastboot 1.50 S On but unlocked
Now imma be at work and not have a working phone. This isn't cool. PLEASE GET BACK TO ME IF YOU CAN HELP peeps. I would really appreciate it.
I also tried the unlocking method all over again but the Java SDK wont install.. it tells me to disable my virus protection (I did) and then it says unable to install it. This is just a mess man.
Click to expand...
Click to collapse
If you're interested in reverting back to completely stock, the RUU files are available at http://www.goo-inside.me/shooter/ruu . Both the PG86IMG.zip and the .exe files are available there.
Interesting the device is flashed to verizon, at least you mention the device is on CDMA verizon. The only issues I can forsee here will be 3G data/MMS might not work via Verizon if using a stock Sprint ROM.
Of course, these *might* work and they can also be *tweaked* but I doubt, out of the box, they will work. Phone calls and SMS should work over verizon using the stock sprint ROM.
Here is my usual lecture, reading this will save you a lot of time and headache, regarding flashing a ROM and kernels on the EVO 3D with hboot 1.5 and htc's unlock method:
Essentially, if you're looking to flash a kernel or ROM (which many times also include a kernel), there are three basic methods (two seem the easier) with hboot 1.50 and htc's unlock method:
1) For Kernel Flashing: From Android mode, using my application, Flash Image GUI. Put the kernel .zip file on your sdcard, select from inside the application and flash.
For ROM Flashing: Pull out the kernel file (usually named boot.img) out of the ROM .zip and push to sdcard. Flash using Flash Image GUI.
If you're away from a computer and want to flash any kernel, this is a great tool!
2) Load the custom recovery, NOT using the traditional method (reboot recovery, bootloader -> recovery, etc), but a specific method for Hboot 1.5. From the prompt use: fastboot boot c:\downloads\cwm-recovery.img.
This will temporarily boot the custom recovery image and the HTC unlock method will grant it write access to the boot partition while in this mode.
In this temporarily booted recovery mode, when a full ROM (with kernel included) is flashed, the kernel will flash correctly.
3) Boot into recovery using the traditional methods, reboot recovery, bootloader -> recovery, etc, and after the custom recovery has loaded, flash the ROM. Reboot into fastboot mode and then separately flash the kernel from the computer: fastboot flash boot c:\boot.img.
Downside to this method would be if a zImage is included instead of the boot.img for the kernel, won't flash correctly.
Being without a phone is rough now a days! Hope that helps and points in the right direction!
so sorry.. i meant to say CDMA Sprint.. i probably was so frustrated and typed verizon. I am about to read what you post completly.
Thank you so much for the reply! I purchased the GUI App from the market a few days ago and I wasnt sure if it would work on my phone because that PG86IMG.zip wasn't on the root of my SD card (it's on the other guy's sd card) I will try your method to flash a ROM.
I was able to get the Rom restored from the nandroid backup someone last night.. I still need a new rom because this one has touch screen problems. Thanks again
Phone Details
Motorola Atrix 4G AT&T (bought around June 2011 Time frame)
System Version
4.5.91.MB860.ATT.en.US
Model Number
MB860
Android Version
2.34
Baseband Version
N_01.77.30P
Webtop Version
WT-1.2.0-110
Kernel Version
[email protected] #2
Build Number
4.5.91
I am absolutely new to this Android ROM installs on the phones. Though I decided to install this ROM I absolutely didn’t’ have any idea how to proceed. As a beginner I started doing the following in order.
Download and Keep the CM7 ROM
1. Downloaded Ba2F.zip to my laptop
2. Downloaded and Installed the Motorola USB drivers MotoHelper_2.0.53_Driver_5.2.0.EXE
3. Connect the Atrix and set the USB option on the phone to “USB Mass Storage”
4. Copy both BaTF.zip as well as the Extracted one to Phone internal storage as well as the Ext-SDcard on the phone
Download ROM Manager and Titanium Backup
1. Downloaded both from Android Market (ROM Manager Pro and Titanium Backup Free Version)
2. Both Apps won’t open because I had not ROOTED the phone
Root the Phone
1. I used “Pete's Motorola Root Tools.EXE” file to ROOT the phone
2. Followed step by step as mentioned here http://www.androidauthority.com/how-to-root-motorola-atrix-4g-35233/
Flash ClockworkMod Recovery
1. I used ROM Manager to do this as when you try to do anything in ROM manager it prompts to do this. The version of this is 5.0.2.0 ( I am not sure what is this for why we have to do this)
Unlocking the Bootloader
1. What I learned is, to unlock the bootloader, we have to first flash the phone with the SBF file
a. Installed RSDLite5.3.1.msi
b. Loaded the file 4547-fix-try2.sbf (Downloaded from http://forum.xda-developers.com/showthread.php?t=1136261)
c. Boot the phone with Power+volume UPPER key pressed till "Starting RSD protocol support" comes up
d. Connect to the Laptop and Hit Start button in RSD Lite Program
e. It Did Throw an error saying “FAIL” after showing the following message
i. Failed to boot: error 0x1000'( not word for word). There will also be a list of boot options like Fastboot, RSD, Recovery, etc. And it says Starting Fastboot Protocol
2. Then comes unlocking the phone
a. Though I had the previous error message, it still had the Fastboot Protocol loaded
b. I went to the FASTBOOT folder in command prompt of my laptop executed the following to unlock the phone which worked perfectly as I see the “Unlock” on the left hand corner when phone boots
c. fastboot oem unlock (it gave me the code) then I used the code to unlock
d. fastboot oem unlock #######
e. fastboot reboot
3. Installing the recovery IMG
a. I had downloaded the Recovery IMG file (recovery-atrix5.img) from http://forum.xda-developers.com/showthread.php?t=1204500
b. Booted the phone into Fastboot mode (turn off phone, hold power and volume down key until 'fastboot' appears then use volume up to select so it says 'starting fastboot protocol support').
c. From the CMD promnt and FASTBOOT directory I used fastboot erase recovery
d. Then I executed fastboot flash recovery recovery-atrix5.img (Note: I didn’t rename the file to recovery as suggested by some people)
e. Then gave fastboot reboot to restart.
4. Booting into Recovery mode (This is where I have the problem)
a. The phone is not booting into recovery it’s not going past the Android and yellow Triangle screen
b. I re-flashed the phone same SBF file (this time it was a success showed in the RSD Lite Program), re-installed the same IMG file after renaming to recovery.img
c. Also tried with a different IMG from the same link (recovery-blue-atrix5.img) but no luck
d. Also deleted the file install-recovery.sh from ./etc/ folder (bought the app root manager to delete the file) and then push the recovery.img, no luck
e. Some people said to TAP the bottom right corner while on that screen, did that but nothing is happening
f. Then I saw a note to press both the Volume Keys at the same time, this works but in this mode the cursor (I mean the selection) on the phone doesn’t go to the First TWO (i and iii) shown below, it allows me to select any of the last FOUR (v, vi, vii, viii).
i. Android System Recovery <3e>
ii. <EMPTY LINE >
iii. Android System Recovery utility
iv. <EMPTY LINE >
v. Reboot System now
vi. Apply update from sdcard
vii. Wipe data/factory reset
viii. Wipe cache partition
g. Using the above option I did factory reset but sill no results.
5. Current condition of the phone
a. It boots in unlock mode and I can do all the daily tasks. But I want to install the CM7 ROM that’s my requirement
PLEASE HELP HELP HELP
First of all, I applaud your effort in giving the a very comprehensive description of your issue.
Second, it seems you are having issues with installing a custom recovery because the recovery you're describing is still the stock recovery. I'll look around and see if I can find something that might help.
jhakash said:
4. Booting into Recovery mode (This is where I have the problem)
a. It boots in unlock mode and I can do all the daily tasks. But I want to install the CM7 ROM that’s my requirement
PLEASE HELP HELP HELP
Click to expand...
Click to collapse
---------- Post added at 11:31 AM ---------- Previous post was at 11:28 AM ----------
Have you tried re-installing the CWM from RomManager through RomManager? And then boot into recovery from within the app?
---------- Post added at 11:40 AM ---------- Previous post was at 11:31 AM ----------
EDIT: This might seem trivial, but is "USB Debugging" turned on?
You are the Man, I just flashed the same CWM 5.0.2.0 and i am in the recovery mode. This gave me an error when i did last time hence i didn't try again.
Thanks a bunch
Glad I can help, also, I think it's recommended to use the RomManager recovery for CM7 so good thing it worked.
jhakash said:
You are the Man, I just flashed the same CWM 5.0.2.0 and i am in the recovery mode. This gave me an error when i did last time hence i didn't try again.
Thanks a bunch
Click to expand...
Click to collapse
Oops.. started again, Can i use the recovery-atrix5.img and ROM manager flash it? if yes, then how?
I copy this file (after renaming to recovery.img) to both internal storage and SD card then what option should i choose in ROM Manager?
If you downloaded the CWM zip file for the romracer recovery and as long as RomManager's recovery is working then, yes, you can.
jhakash said:
Oops.. started again, Can i use the recovery-atrix5.img and ROM manager flash it? if yes, then how?
I copy this file (after renaming to recovery.img) to both internal storage and SD card then what option should i choose in ROM Manager?
Click to expand...
Click to collapse
jhakash said:
Oops.. started again, Can i use the recovery-atrix5.img and ROM manager flash it? if yes, then how?
I copy this file (after renaming to recovery.img) to both internal storage and SD card then what option should i choose in ROM Manager?
Click to expand...
Click to collapse
See post#2 from romracer's thread. Read the Miscellaneous part. Probably need to get rid of, or backup, install-recovery.sh.
He has mentioned he already did that. In his OP, under the steps he took look at "Booting into Recovery Mode" - 4.d, he says he removed it.
Maybe he's not doing it in the right order? Do you happen to know which should be done first as far as installing recovery and removing said file?
ghost_og said:
See post#2 from romracer's thread. Read the Miscellaneous part. Probably need to get rid of, or backup, install-recovery.sh.
Click to expand...
Click to collapse
live4nyy said:
He has mentioned he already did that. In his OP, under the steps he took look at "Booting into Recovery Mode" - 4.d, he says he removed it.
Maybe he's not doing it in the right order? Do you happen to know which should be done first as far as installing recovery and removing said file?
Click to expand...
Click to collapse
Woops, I should have read more carefully. It's best to remove the file first and then flash the recovery.img, or else the script will install the stock recovery on boot. That would make stock recovery the current one on the phone at the time of the script getting deleted.
I would double check and make sure /system/etc does not have install-recovery.sh. If it is not there, then proceed to the fastboot steps and reflash the recovery.img again. It should stick this time.
@Ghost, yes i deleted the file multiple times however i didn't find the /system/etc folder on the Internal Storage. however I found the install-recovery.sh file under /etc folder. The thing i observed that whether i flash it with a new CWM or not if i reboot the phone then it was created by itself.
@Live4nyy, Thanks for your suggestion, I could able to install CM7 now and it looks awesome good so far, but looks like i need to install Google Apps separately to access the APP market, am I right?
The only thing that happens to me is, it allowed me to go to Recovery only ONCE after i Flashed it thru ROM Manager, if i exit out of recovery without doing anything then next time tried to go to Recovery, it will struck at the same old Android screen and i had to flash it again. But Many thanks for suggesting to flash it thru ROM Manager.
Now with CM7, under ROM Manager (I guess this comes default with CM7) I see there is no version listed under "Flash Clockworkmod Recovery" and it says i must have to install it in-order to Flash and restore ROMs, do i need to do that? I can go to Recovery mode after reboot without any issues. Please Advise.
------
Jhakash
jhakash said:
@Ghost, yes i deleted the file multiple times however i didn't find the /system/etc folder on the Internal Storage. however I found the install-recovery.sh file under /etc folder. The thing i observed that whether i flash it with a new CWM or not if i reboot the phone then it was created by itself.
Click to expand...
Click to collapse
I just checked out my girlfriend's stock, locked, unrooted Atrix and she actually has install-recovery.sh in both /etc and /system/etc. Her file manager does not alphabetize anything in either folder, so I almost overlooked the second one.
If you're already on CM7, then you probably won't need to worry anymore. They have an entirely different set of start up scripts in that folder. Welcome to the community!
At this point I do not know enough to help you any further with this issue. All I knew about is the file that needs to be removed that @ghost_og has mentioned. But if you can flash it from RomManager and access CWM from there as well then I guess that's a good enough workaround for now.
Does anyone else have any idea why the stock recovery cannot be removed?
jhakash said:
@Live4nyy, Thanks for your suggestion, I could able to install CM7 now and it looks awesome good so far, but looks like i need to install Google Apps separately to access the APP market, am I right?
The only thing that happens to me is, it allowed me to go to Recovery only ONCE after i Flashed it thru ROM Manager, if i exit out of recovery without doing anything then next time tried to go to Recovery, it will struck at the same old Android screen and i had to flash it again. But Many thanks for suggesting to flash it thru ROM Manager.
Now with CM7, under ROM Manager (I guess this comes default with CM7) I see there is no version listed under "Flash Clockworkmod Recovery" and it says i must have to install it in-order to Flash and restore ROMs, do i need to do that? I can go to Recovery mode after reboot without any issues. Please Advise.
------
Jhakash
Click to expand...
Click to collapse
I am good to go now, everything seems to be functioning well after flashing CM7 ROM, no more recovery issues, and the Stock recovery is gone now.
Appreciate for all the info you guys provided, it helped a lot. Have a great day and Merry Christmas.
Regards
Jhakash
Do I have root?
First you install the unlock APK, unlock it...Install goo beta, Install Open-Script Recovery, reboot and ill have TRWP? and be able to install custom roms?
IM READY TO JUMP SHIP!
You have your recovery to install everything.....
Inviato dal mio Transformer Prime TF201 con Tapatalk 2
It has its own recovery? or do i need to install one...
David522d said:
It has its own recovery? or do i need to install one...
Click to expand...
Click to collapse
install one. get goo manager from market place. then go in goo manager, go to settings I believe. then tell it flash open script recovery. It will flash the TWRP recovery for prime. all touch screen based. then with goo manager, you can find all the great toms for prime in there and flash directly from there. plus it'll let you know when there is updates for your custom rom. check it out. IMO, has alot more features and more straight forward that CWM recovery.
actually there a sticky thread in developement section that has video guides for the prime. one of them shows you how to install this recovery I mentioned if you unsure.
also a video showing you how to flash a custom rom, with TWRP and goo manager, is there also
demandarin said:
install one. get goo manager from market place. then go in goo manager, go to settings I believe. then tell it flash open script recovery. It will flash the TWRP recovery for prime. all touch screen based. then with goo manager, you can find all the great toms for prime in there and flash directly from there. plus it'll let you know when there is updates for your custom rom. check it out. IMO, has alot more features and more straight forward that CWM recovery.
actually there a sticky thread in developement section that has video guides for the prime. one of them shows you how to install this recovery I mentioned if you unsure.
Click to expand...
Click to collapse
1. Install Unlock APK. Unlock.
2. Reboot, Install Goo Manger, Install Open script recovery. Reboot into TWRP recovery
3. Install ROMS?!?!!?!
As in I don't have to root after I unlock it already does?
I don't have root on this tablet, its on .21. I don't want to brick it, so will these steps be perfect?!
THANKS!!!
Anyone ?
I don't know about goo manager but I flashed cwm touch with fastboot (normal cwm didn't work and twrp wasn't out)
Sent from my sgs2 running cm9
David522d said:
1. Install Unlock APK. Unlock.
2. Reboot, Install Goo Manger, Install Open script recovery. Reboot into TWRP recovery
3. Install ROMS?!?!!?!
As in I don't have to root after I unlock it already does?
I don't have root on this tablet, its on .21. I don't want to brick it, so will these steps be perfect?!
THANKS!!!
Click to expand...
Click to collapse
Yeah steps sound good. you could always flash a ROM that has root. I dont think you need root to install twrp. Double check though. post in twrp thread to make sure.
Hate to be a pain the butt
But does anyone know if that method will work 100%
Sorry fellas dont want to end up with a 500$ paprr weight
David522d said:
1. Install Unlock APK. Unlock.
2. Reboot, Install Goo Manger, Install Open script recovery. Reboot into TWRP recovery
3. Install ROMS?!?!!?!
As in I don't have to root after I unlock it already does?
I don't have root on this tablet, its on .21. I don't want to brick it, so will these steps be perfect?!
THANKS!!!
Click to expand...
Click to collapse
Unlocking will not root your prime. I think Goomanager needs superuser rights so you will need to be rooted to flash TWRP (at least it asks for SU when I check for rom updates).
I use CWM since there have been a few stories floating around of people bricking their primes when trying to restore using TWRP. I am sure it is fine but it just makes me a little nervous...
If you're unlocked, not rooted and want to install CWM follow method 1 here:
http://forum.xda-developers.com/showthread.php?t=1576937
David522d said:
Hate to be a pain the butt
But does anyone know if that method will work 100%
Sorry fellas dont want to end up with a 500$ paprr weight
Click to expand...
Click to collapse
There is nothing that will work 100%, but its pretty close, maybe 98%? Anytime someone does anything with the bootloader, recovery rom, or OS rom, there is a chance for bricking: interuption in the write process, loss of power, corrupted dl (crc check should catch most of those). If your worried about bricking it, leave your TFP stock and await the OTA's - that way if it gets bricked by Asus then they are responsible and you havent nullified your warranty.
Unlocking the bootloader allows the use of non stock bootloaders/recoveries to be installed and used. From the new bootloader/recovery, you can install a rom that either has root, or not. You don't even have to change roms after unlocking. The 2 are independent.
Right -
Unlocking with the APK does not root or in any other way modify or prep the prime for what you're about to do. Depending on your stock ROM revision this is either very easy or a complete pain in the ass, I'll provide both versions:
For Stock ROM ending .15 or earlier -
* DO NOT RUN THE GOO IM.MANAGER FIRST. Follow these steps below.
* Download Sparky's APK to root - it's in the development forum for the TF Prime. Run it. This will get you root access on the system. It's automated and practically idiot proof, just follow the on screen instructions.
* If you're going the Team Win route, once rooted, load up the Goo.im manager, then follow the instructions as per a rooted installation for getting TW Recovery into place. This is pretty painless really and works automatically, approve the Superuser permissions as required. Once the recovery is in, you can reboot into it and then get with the flashy.
-----
If you're on the Stock ROM ending .21, you're going to have to do what I did. As you're already unlocked using the BLOB files to downgrade -will- result in a hard brick. SO!
* Install ADB and Fastboot onto your system, as well as the universal USB naked driver which you can find on this forum.
* Search for DotTech install ADB and Fastboot - follow this guide, it's probably the easiest way to get a working fastboot and ADB environment up and running.
* Enable USB debugging on the tablet under developer options.
* Set up the universal driver, you'll need to reboot your TF201 and hold the POWER and VOLUME DOWN buttons until you see some text in the top corner. Do NOT press volume up to go into Recovery Image mode or you'll just walk into a dead end.
* Shortly after you'll see three icons, press volume down ONCE and then volume UP once, the USB icon in the middle should be highlighted and you should see text saying "Entering Fastboot Protocol" or similar.
* Plug the USB cable into the tab and the PC, test whether you have a working fastboot install by typing fastboot -i 0x0b05 reboot, if your tablet reboots without you touching it, then you've got working fastboot access. Remove the cable, reboot to fastboot mode as described above.
* Meantime, download openrecovery-twrp-2.1.3-tf201.blob from the team win site, and stuff it in the same directory that you set up Fastboot/ADB, rename it to twrp.blob. Plug your tablet back in and then issue the command fastboot -i 0x0b05 flash recovery twrp.blob , if this goes to plan you'll see a couple of lines of text on the command window which will tell you that it's been successfully flashed in. YOU STILL DO NOT HAVE ROOT THOUGH, SO NO SILLY STUFF
* Finally, download the ROM of your choice, place it in the base /sdcard directory, then reboot the tab and hold POWER and VOLUME DOWN, when you see the text, this time hit VOLUME UP, and you'll be sent into the team win recovery suite, at this point you can wipe and flash the newly prepared ROM as per normal.
* For the first occasion I -strongly- recommend you use Virtuous Prime-S as you can generate a solid backup environment out of it, as well as the fact it's not too departed from Stock, so it's a good way to break yourself in.
Hope this helps.
This whole blob thing is new for me since i have always insta-rooted, and CWM'ed any android device i get; but from what I've gathered, it is used by ASUS to lowlevel write the os on locked systems, similar to the way nvflash dumps img's directly to the memory. Once your unlocked with the CWM or twrp, then you can no longer use blobs, just the rom zips. The recovery rom handles the unpacking and dumping of the kernel and OS into the appropriate partitions. Some roms are zipped with install scripts that wipe your cache, user space and dalvik - but its always a safe bet to do that anyways.
Nice writeup Hobbesian
Well, some blobs are fine, but generally they're strictly either Team Win Recovery or Clockwork mod recovery suites, and they need to be slipped in using fastboot (I believe ROM manager and GOO managers use their own scripts to handle installation) as a rough rule. The "big" BLOB files which Asus puts out are a guarantee to hardbrick an unlocked device (some days I wonder if it would kill Asus to offer a route to re-lock and re-stock a device on the proviso that if you brick it doing so you're still out of warranty).
That said - Virtuous Prime is definitely an excellent first step into Custom ROM tinkering, it gives you root and all the associated useful features, as well as the ability to start experimenting with more feature heavy ROM builds such as Cyanogen and AOKP Cornerstone. They're even nice enough to include a partially tweaked build.prop which saves you a lot of the work in modifying that.
I should point out my guide is relevant only if you already applied the unlock APK to your system, if you haven't done so, there's alternative routes including the downgrade blob option to get root without unlocking your device.
paddycr said:
Unlocking will not root your prime. I think Goomanager needs superuser rights so you will need to be rooted to flash TWRP (at least it asks for SU when I check for rom updates).
I use CWM since there have been a few stories floating around of people bricking their primes when trying to restore using TWRP. I am sure it is fine but it just makes me a little nervous...
If you're unlocked, not rooted and want to install CWM follow method 1 here:
http://forum.xda-developers.com/showthread.php?t=1576937
Click to expand...
Click to collapse
1. Unlock Prime...
2. Do method 1
3. Then goo manger, install script. Reboot in team win recovery
4. Install AKOP =) !??!?!
yes?
David522d said:
1. Unlock Prime...
2. Do method 1
3. Then goo manger, install script. Reboot in team win recovery
4. Install AKOP =) !??!?!
yes?
Click to expand...
Click to collapse
The method 1 in the link will install ClockWorkMod which I use as my recovery. You can completly miss step 3. If you really want to use TWRP then do the goomanager thing.
However, before you do a wipe and install AOKP (ethher from CWM or TWRP) MAKE A BACKUP OF YOUR CURRENT ROM!! That's important (hence caps ) - people are always on here complaining that they are soft bricked because of a bad download and not making a backup.
EDIT: if you're in fastboot and you cannot get adb to recognize your prime you need to install the correct drivers for your pc/mac. Hobbesian describes how to do this a few posts above this. In his nice write up he also describes how to flash TWRP directly from fastboot. If you want TWRP, follow his instructions since you'll have less messing around to do.
paddycr said:
The method 1 in the link will install ClockWorkMod which I use as my recovery. You can completly miss step 3. If you really want to use TWRP then do the goomanager thing.
However, before you do a wipe and install AOKP (ethher from CWM or TWRP) MAKE A BACKUP OF YOUR CURRENT ROM!! That's important (hence caps ) - people are always on here complaining that they are soft bricked because of a bad download and not making a backup.
Click to expand...
Click to collapse
And flashing a rom with root therefor should give me root correct?
I sound like an idiot, but just to make sure
David522d said:
And flashing a rom with root therefor should give me root correct?
I sound like an idiot, but just to make sure
Click to expand...
Click to collapse
Yes, all of the roms will have root. Hit my thanks button if it works for you
paddycr said:
Yes, all of the roms will have root. Hit my thanks button if it works for you
Click to expand...
Click to collapse
Would it be easier to install CWM, then install TWR
David522d said:
Would it be easier to install CWM, then install TWR
Click to expand...
Click to collapse
I think both ways are the same. There's no correct answer to that. It depends on whether you would prefer to use CWM or TWRP.
i followed the instructions on the CyanogenMod wiki (http://wiki.cyanogenmod.org/w/Install_CM_for_jewel) to install CM 10.2 on my EVO 4G LTE.
i am able to launch TWRP 2.7.0.8 and receive a notice that CM 10.2 flashes successfully but when i try to reboot into the system, i see the white htc screen, the screen goes black and the whole thing just repeats itself until the battery dies or i get back into recovery and shut down.
there is a note at the bottom that says " if unlocked with HTCDev Unlock, must have its kernel flashed via fastboot." since i used the instructions on that page, i assumed this didn't apply to me, otherwise it would have been included within the instructions.
i have installed CM on my old captivate and my Nexus 7 successfully, so i have done this before by following instructions, but am at a loss as to what happened this time. any tips would be greatly appreciated!
If you're S-on you have to flash the kernel separately from the ROM. Hit the top link in my sig and scroll down to the section on S-on kernel flashing for more info.
Sent from my HTC M8
Magnum_Enforcer said:
If you're S-on you have to flash the kernel separately from the ROM. Hit the top link in my sig and scroll down to the section on S-on kernel flashing for more info.
Sent from my HTC M8
Click to expand...
Click to collapse
thanks for your quick reply. can i use TWRP to flash the kernel? i can copy the boot.img to my external sd card and then flash from there. i am unable to push files using adb.(not sure where the problem is. i installed sync but do not have media player 11 installed so maybe that's the problem)
barthie said:
thanks for your quick reply. can i use TWRP to flash the kernel? i can copy the boot.img to my external sd card and then flash from there. i am unable to push files using adb.(not sure where the problem is. i installed sync but do not have media player 11 installed so maybe that's the problem)
Click to expand...
Click to collapse
No, you can't use TWRP, at least not for flashing in recovery. You do have a few options, though. You can use the paid app Flash Image GUI from the Play Store, use the TWRP Dumlock feature (link can be found in my guide), or get S-off (your best bet). There is a link in my guide on how to set up ADB on your computer, so maybe that will get you headed in the right direction.
Magnum_Enforcer said:
No, you can't use TWRP, at least not for flashing in recovery. You do have a few options, though. You can use the paid app Flash Image GUI from the Play Store, use the TWRP Dumlock feature (link can be found in my guide), or get S-off (your best bet). There is a link in my guide on how to set up ADB on your computer, so maybe that will get you headed in the right direction.
Click to expand...
Click to collapse
flashed boot.img to the phone. still was unable to push the modified zip via adb but was able to mount the phone in recovery so i copied the zip, reflashed and all works!
thanks!!!!
So I got my shiny new device today, and it feels really nice. I worked with the launcher it came with, tried another one, and realized that yep, I gotta root and install a new rom. The notification bar just annoys me too much as I'm used to having quick actions and other things in there.
So, I followed a few guides, and finally worked my way through to having my command line find my device and can successfully reboot it into fastboot mode.
At that point, I realized that I can boot into recoveries without flashing them first (essentially trying them out to see how it works). However, I tried the 4 official version on the twrp site, and one made by a user here (cuoco92). They all successfully boot into the recover using the command "fastboot boot nameOfFileHere.img". At this point, every single recovery failed to respond to touch and volume presses. I can press the power button to turn off the screen, and pressing power to turn the screen back on shows a locked recovery screen, but I can't slide the screen to unlock it.
This is quite concerning to me. I don't want to flash a recovery for good if it's not working properly. I hope this makes sense. Or, is it normal to just flash a recovery and hope for the best? Do recoveries work with just booting to them without being flashed?
I haven't rooted and/or flashed any devices in about 5+ years, the last being a phone from virgin mobile that supported sd cards. When installing new roms, do we store the zips in the root of the phone, or does this get cleared out/deleted when doing the wipe cache/dalvik/etc?
Personally, I just want to make sure I don't rush into this, as there seems to be fragmented results when searching around for twrp not working with touch. I know these things have been asked before plenty of times, and I hope I don't come across as another "ugh, this again" post. I really appreciate any responses!
you never did, then just leave it as it is...its a nice phone eui is not bad... take it easy
Try booting the official TWRP recovery. As far as I remember, some of the versions tweaked by Cuoco92 had issues with the touch panel.
Anyway, EUI is not that bad, as your were told. While I used it, I also used an app called "Notification Toggles", which lets you get Quick Settings like toggles on notification area. It's nice and easy to set up, and the results, although not the same as having the AOSP toggles, is quite nice and convenient.
BTW, which stock ROM did your phone come with?
I have tried 4 different official twrp files (all from the twrp site). My phone is an x820 6gb/64gb and came with EUI version: 5.8.019S (Stable). EUI is nice, very fast and sleek. Maybe I do just need to get used to it, or maybe it's just me itching to try out the different options available since I finally have a phone is not carrier/manufacturer locked down.
Heyyo, hmm that's very odd indeed! I wonder if maybe by temporary booting Cuoco92's TWRP it could have messed up your recovery hmm...
I'd recommend first to flash the stock recovery over your current one and then reboot to fastboot and then flash TWRP. Hopefully this will erase any problem that Cuoco92's recovery could have caused.
This was the guide I followed and it worked flawlessly for me
https://forum.xda-developers.com/le-max-2/how-to/protocol-backup-stock-rom-flash-stock-t3517151
I never actually flashed any of them. I have only ever just tried booting into them using "fastboot boot recovery name.img". I have not used the fastboot flash command for any of the files.
The only thing I can do after booting the recoveries is hold the power button and eventually the phone will boot up normally.
Remember that I just wanted to boot them to make sure they worked before flashing them. I'll be checking out the guide you linked shortly.
Haven't flashed any of them eh? Hmm should work just fine then... Have you tried TWRP 3.0.2-0 ? I know that one was built with Marshmallow sources
As for which ROM to try? I'd recommend OmniROM if you want to try a custom Nougat ROM.
If you want to see why I think so? I made a massive post or two about it here heh
https://forum.xda-developers.com/le-max-2/help/party-rom-best-help-t3691165/
Thank you so much for the guide you linked. I'm making a little bit of progress here.
I found a twrp recover by cuocos92 that is labeled V3 (apparently from what I read in other threads, V3 seems to be good with the 6gb/64gb models). This recovery allows the use of the touchscreen . Remember that I am only using the "fastboot boot" command so no flashing yet.
Now that I am in a working recovery, I kept hitting "keep read only" so that the stock recovery would not be replaced. I set out to make a backup. Well that kept failing with attempts of trying to mount /system and such. Off to more reading, found out that using the Wipe->Swipe to Factory Reset inside twrp fixes this. I did that. I successfully created a backup.
Now to try to flash the SuperSU zip I have, which was previously copied to the root of the phone from my pc. Can't see any zip files on the internal storage. Reboot the phone (forgetting that it takes a long time after the wipe). Copy the backup to my pc. Copy the SuperSU back to root of phone. Restart the process of adb and fastboot -> back into the cuocos92 V3 recovery. Still no zip to be found. Couldn't mount system again...
Did some more reading. I just attempted the Wipe->Format data. I am currently rebooting back into the phone to set it up again. Apparently, a lot of people say this needs to be done if we did not reboot after unlocking the bootloader. Since twrp has been asking for a password each time I entered it, the format data is supposed to solve this.
I'll edit/post again with more steps or results.
I apologize for the second post here, but this seems more than should go into an appended edit:
After doing the Wipe->Format data, it's advised to reboot back into the recovery. Without flashing the twrp cuocos92 recovery, my thoughts are it would just be back into the stock recovery. At least the twrp version works, so I have no problems with flashing it. And then I'll have to Wipe->Format data again, reboot back into recovery, and then I can flash my SuperSU zip. But how can I get my SuperSU zip on the phone?
Doesn't Wipe->Format data remove it? Everytime I reboot my phone after that the SuperSU on the root of the phone is gone. I can't seem to mount to my pc from the recovery either, clicking the usb storage just unchecks itself right away, and clicking the enable MTP doesn't seem to do anything. So, even if I flash the recovery, Wipe-Format data again, reboot back into the recovery, I still don't see a way of getting the SuperSU zip onto the phone anyways.
I know it probably sounds like I'm whining by now about how things aren't as easy as it seems. I'm trying to be descriptive in what I am doing and what's happening.
Hmm by chance are you using Windows 10? At least I've noticed for me it fails to properly mount the correct drivers for ADB and MTP for TWRP. I'd recommend checking device manager.
If I remember correctly here's what mine looked like at first
https://photos.app.goo.gl/wXaqbi3OeH3bKEf62
Select MTP > update driver > browse my computer > let me pick > (standard MTP Device) > MTP USB Device
Sorry I'm not in front of my PC but I'm sure it's something like that to solve it
If that doesn't work? You can always use...
Code:
adb push ROM.zip /sdcard
Which will copy the zip file to the root of your data storage (on the Le Max 2 much like the One Plus 3 they use /Sdcard as a shortcut since we don't have external Sdcard hardware).
As for system read only? Swipe to allow modifications. Can't flash a ROM properly if the system is read only eh? Hence the failed to mount system.
It's really just there as a disclaimer to cover their ass in case people use TWRP improperly and brick their device. Following green man gaming's guide is safe as I've used it plus many other people as you'll see in his replies
I'd also recommend following the guide and flashing TWRP to your recovery. I only did boot recovery image for backup and then booted to EUI and copied that backup to my PC.
Format data is handy to get rid of encryption and also give you full access to your storage capacity because when I didn't before I didn't get 54.43GB of data storage only something like 40GB.
Tbh I haven't used any custom EUI ROMs but if you're fighting with TWRP? I know Cuoco92's eui has a fastboot installable version
Hope this helps
Well thank you so much for the information. I am running windows 10, but never saw mtp under portable devices, only the phone name Le Max 2. That's ok, as I booted (still not flashed) into recovery and this time I swiped to allow modifications. I still couldn't mount /system but I was able to use the adb push command and the SuperSU file appeared inside the /sdcard directory when looking under Install inside twrp. I swiped to flash the zip, then hit reboot system. Looking in the SuperSU app, I noticed that the setting "Install SuperSU into /system" is greyed out. Well, at least I think it worked.
At this point in time, since things appear to be working, I'll be flashing the recovery and installing OmniRom (it was either this or Resurrection Remix). I think if the play store just works on OmniRom like people mention, it'll be worth it.
So, my steps will be to:
adb -> fastboot -> fastboot flash recovery fileName.img
recovery -> wipe -> factory wipe (using factory to get rid of system encryption) -> reboot back into recovery
recovery -> wipe -> dalvik/cache (do i still need to do this after factory wipe?)
adb -> adb push romFileName.zip /sdcard
adb -> adb push gapps.zip /sdcard
recovery -> install -> /sdcard -> romFileName.zip
recover -> install -> /sdcard -> gapps.zip
At any point do I need to flash SuperSU again? I guess I should after flashing the rom/gapps because, afterall, SuperSU is an app.
Once again, thank you so much for all the information that you have already provided!
Heyyo, it's always recommended to do a full wipe when installing a different ROM so you should format data, wipe system, data, dalvik and cache and then install the ROM of choice with Gapps of choice
Wiping system is OK when flashing a ROM as it'll write into system.. plus there's always the risk of instability if system is not wiped if a Gremlin setting is left over from previous ROM
I'd recommend using Magisk v14.3 over SuperSU as SuperSU doesn't have the same functionality as Magisk for passing SafetyNet...
Plus Magisk is full open source software (FOSS) where as SuperSU is closed source so gotta love that open source (this part is more personal preference since Android is built upon open source and people working together).
Plus there's really cool Magisk modules you can do like ART Optimizer and so fourth if you check the XDA forum section for it
Also, you're welcome! We all had our start on XDA at different points and passing on the knowledge I find is just as important as the ROMs we love
Don't use SuperSU. Magisk is the way to go for rooting nowadays. Easy, systemless, updated frequently to pass safetynet. It's a no brainer.