Related
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.
FLASHING WRONG IMAGES CAN DAMAGE YOUR DEVICE SO USE THIS APP ON YOUR OWN RISK
fire flash is an App for flashing boot and recovery partitions on both versions of Kindle Fire HD. Optionally it also installs a simple Open Recovery Script which gets executed after entering recovery mode. In script only wiping system/data/cache and installing ROMs (.zip files) are supported.
Usage: download files you want to flash (boot image, recovery image, ROM .zip files). After downloading files, select them and check appropriate options. In attached image there is an example for flashing Hashcode's bootloader + TWRP + stock ROM v8.1.4 with installed stack override on a KFHD8.9. After all files are selected and options checked as shown on the image, first tap Flash,install script button and then Reboot into recovery button. All required files can be found in Hashcode's threads.
Tomsgt made a video http://youtu.be/a1bLCuQN0-U which shows how to use the fire flash. Thanks.
Note: more than one .zip file can be selected. To remove a file from the list, select the same file again.
Update v1.1
-added support for system version 7.3.0 / 8.3.0:
: if current bootloader is not 7.2.3 / 8.1.4 a red warning is displayed and check box for flashing 7.2.3 / 8.1.4 bootloader is enabled.
: unless you are sure your current bootloader is not 7.3.0 / 8.3.0 bootloader 7.2.3 / 8.1.4 should probably be flashed - check the checkbox.
-works on CM10.1
-every flashed partition is read back and verified
-shows progress when flashing
Update v1.01
-added some feedback after pressing Flash,install script button
-(hopefully) resolved problems with open recovery script
stanga72 said:
FLASHING WRONG IMAGES CAN DAMAGE YOUR DEVICE SO USE THIS APP ON YOUR OWN RISK
fire flash is an App for flashing boot and recovery partitions on both versions of Kindle Fire HD. Optionally it also installs a simple Open Recovery Script which gets executed after entering recovery mode. In script only wiping system/data/cache and installing ROMs (.zip files) are supported.
Usage: download files you want to flash (boot image, recovery image, ROM .zip files). After downloading files, select them and check appropriate options. In attached image there is an example for flashing Hashcode's bootloader + TWRP + stock ROM v8.1.3 with installed stack override on a KFHD8.9. After all files are selected and options checked as shown on the image, first tap Flash,install script button and then Reboot into recovery button. All required files can be found in Hashcode's threads.
Note: more than one .zip file can be selected. To remove a file from the list, select the same file again.
Click to expand...
Click to collapse
can flash for example tweaks and sound tweaks like acid audio engine that come in a zip?
persano said:
can flash for example tweaks and sound tweaks like acid audio engine that come in a zip?
Click to expand...
Click to collapse
fire flash generates a script which is then executed by TWRP. If tweaks can be flashed from TWRP then yes. Leave boot and recovery image 'Not flashed' and don't wipe anything in OpenRecoveryScript section. Select your .zip file(s), press Flash, then reboot into recovery. This app only simplifies (a few) tasks that can be done in TWRP and makes intalling boot and recovery partition realy easy.
stanga72 said:
fire flash generates a script which is then executed by TWRP. If tweaks can be flashed from TWRP then yes. Leave boot and recovery image 'Not flashed' and don't wipe anything in OpenRecoveryScript section. Select your .zip file(s), press Flash, then reboot into recovery. This app only simplifies (a few) tasks that can be done in TWRP and makes intalling boot and recovery partition realy easy.
Click to expand...
Click to collapse
you need twrp?
persano said:
you need twrp?
Click to expand...
Click to collapse
yes TWRP does the unzipping. If you only need to unzip some files into the /system dir this app perhaps isn't the best choice.
I downloaded it will it work on a unrooted Kindle fire hd since I have no way to root my kindle right now
sent from my unrooted kindle fire hd
Raymond199483 said:
I downloaded it will it work on a unrooted Kindle fire hd since I have no way to root my kindle right now
sent from my unrooted kindle fire hd
Click to expand...
Click to collapse
device must be rooted for this App to work.
Works good. A couple things to note:
1. It gives no indication when you click the "flash, install script" button that it's done flashing. I ended up clicking it twice...
2. Even though I selected to wipe the cache/data/system and install the new IS zip file, it did not work. I rebooted to TWRP ok, but had to wipe and flash manually...
But, I'm definitely not complaining about anything cuz it got my second boot loader installed without me having to buy a fast-food cable first!
Sent from my KFTT using Tapatalk 2
Good news I'm rooting my Kindle fire HD today for sure
sent from my unrooted kindle fire hd
Awesome work. My plan is to backup the current image before flashing any new ROMs. Using this script how can I just flash TWRP without changing anything else? If I just flash recovery partition alone, would it do the trick for my use case ?
Sent from my SAMSUNG-SGH-I727 using xda premium
---------- Post added at 11:43 AM ---------- Previous post was at 11:38 AM ----------
Also I think this thread deserves a place in kernel Dev section as I happened to find this by accident. I don't generally browse Apps Dev section but I did and was to happy to find this thread.
Sent from my SAMSUNG-SGH-I727 using xda premium
raj3366 said:
Awesome work. My plan is to backup the current image before flashing any new ROMs. Using this script how can I just flash TWRP without changing anything else? If I just flash recovery partition alone, would it do the trick for my use case ?
Click to expand...
Click to collapse
I was able to do it without flashing any other zip files(just boot and recover images). It takes a while to boot into recover though (after the "kindle fire" logo turns blue).
Thanks for the good work.
this is truly awesome, i have TWRP installed in like a minute!
hector333 said:
this is truly awesome, i have TWRP installed in like a minute!
Click to expand...
Click to collapse
Can you tell me what steps you did to have twrp install by this app?
Can you tell me what steps you did to have twrp install by this app?
Click to expand...
Click to collapse
First download the kfhd7-freedom-boot.img and the TWRP Recovery from this post:
http://forum.xda-developers.com/showthread.php?t=2128848
Now move those files to the storage on your KFHD7, install the fire flash APK and execute it, select the files and check the "Apply Stack override" box and the "disable recovery auto update" just like the picture on the OP.
now execute it by pushing the "flash install script" button and Wait! (it do not says its done so i wait like a full minute)
now do a reboot and the boot logo will turn blue and the you push volume up and then you will be in TWRP
hope it helps.
hector333 said:
First download the kfhd7-freedom-boot.img and the TWRP Recovery from this post:
http://forum.xda-developers.com/showthread.php?t=2128848
Now move those files to the storage on your KFHD7, install the fire flash APK and execute it, select the files and check the "Apply Stack override" box and the "disable recovery auto update" just like the picture on the OP.
now execute it by pushing the "flash install script" button and Wait! (it do not says its done so i wait like a full minute)
now do a reboot and the boot logo will turn blue and the you push volume up and then you will be in TWRP
hope it helps.
Click to expand...
Click to collapse
Thanks for the info, one more thing was this done on a kindle fire or kindle HD?
---------- Post added at 04:20 PM ---------- Previous post was at 03:56 PM ----------
[email protected] said:
Thanks for the info, one more thing was this done on a kindle fire or kindle HD?
Click to expand...
Click to collapse
please ignore found my answer.
hector333 said:
First download the kfhd7-freedom-boot.img and the TWRP Recovery from this post:
http://forum.xda-developers.com/showthread.php?t=2128848
Now move those files to the storage on your KFHD7, install the fire flash APK and execute it, select the files and check the "Apply Stack override" box and the "disable recovery auto update" just like the picture on the OP.
now execute it by pushing the "flash install script" button and Wait! (it do not says its done so i wait like a full minute)
now do a reboot and the boot logo will turn blue and the you push volume up and then you will be in TWRP
hope it helps.
Click to expand...
Click to collapse
Wow done in least then 2 minuets. :good:
Thanks, this work out perfect no nightmares to report, maybe next update for this app will let you know when its safe to reboot. :laugh:
[email protected] said:
Wow done in least then 2 minuets. :good:
Thanks, this work out perfect no nightmares to report, maybe next update for this app will let you know when its safe to reboot. :laugh:
Click to expand...
Click to collapse
flashing is done almost instantly, no need for waiting. In v1.01 there is some feedback after flashing is done.
stanga72 said:
flashing is done almost instantly, no need for waiting. In v1.01 there is some feedback after flashing is done.
Click to expand...
Click to collapse
I was wondering is it possible to update twrp to the latest version or are we stuck with this one?
[email protected] said:
I was wondering is it possible to update twrp to the latest version or are we stuck with this one?
Click to expand...
Click to collapse
I was also wondering the same thing. Can we upgrade to the newest version of twrp?
eclipsegt said:
i was also wondering the same thing. Can we upgrade to the newest version of twrp?
Click to expand...
Click to collapse
WARNING DO NOT-DO IT I tried it and it went into fastboot loop, i was lucky that i was able to fix back.
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.
I have seen that since the update notification for Jelly Bean has arrived, Many people (Including me) have been asking for a Tutorial to root the Jelly Bean updated HTC Desire X (HTC DX for short). In this tutorial I would like to mention the steps to root Android Jelly Bean (JB) on HTC DX.
UPDATE: Tutorial with Screenshots here : HTC Desire X Root
This was what had worked for me when I recently rooted by HTC Desire X with Jelly Bean Update, So I hope it works for you too. I am assuming you have just installed the OTA Update and are now sitting with a Stock Jelly Bean on your device.
Summary:
1. Unlock Bootloader (if not already unlocked).
2. Install Jelly Bean compatible Custom Recovery.
3. Flash Super User and Install Busy Box.
4. Enjoy.
Steps.
1. Unlocking Bootloader.
There is a fully explained thread on unlocking bootloader and rooting android ICS put up by user nlooooo, Follow that thread and unlock your bootloader.
http://forum.xda-developers.com/showthread.php?t=2076675
2. Install Jelly Bean compatible Custom Recovery.
Once you update via OTA for the JB Update, Your HBoot becomes JB Hboot instead of the old ICS Hboot so you need a JB Hboot compatible Custom Recovery to flash the Super User and Root.
Our fellow user atis112 fixed the recovery by neXus PRIME to make it work with JB. So you need to download the JB Custom Recovery from the attachment and put it in your C Drive, So the file location would be C:\recovery.img
2.1] Download JB Recovery.img from here : http://forum.xda-developers.com/showpost.php?p=39662992&postcount=66 OR You can use the TWRP Recovery Image made by Yasir. Download from here : http://d-h.st/tSc
2.2] Once you put it in C Drive you need to connect your HTC Mobile to PC and Install HTC JB Drivers, You can install the drivers from here : http://forum.xda-developers.com/showthread.php?t=2222501. Make sure you have installed the Drivers correctly.
2.3] Open your Android SDK (Download it from here if not already) and Go to the \sdk\platform-tools folder. If on Windows 7, Keep the Shift Key pressed + Right click on an empty place in the platform-tools folder > Open Command Window here.
2.4] Type in the following command and see if your device is detected.
adb devices
Click to expand...
Click to collapse
After it is detected, Type the following command.
adb reboot bootloader
Click to expand...
Click to collapse
Once you are in the bootloader, Type the following command.
fastboot flash recovery c:\recovery.img
Click to expand...
Click to collapse
followed by
fastboot reboot-bootloader
Click to expand...
Click to collapse
and
fastboot erase cache
Click to expand...
Click to collapse
2.5] Now you have installed your custom recovery. Now Reboot your Phone.
3. Install SuperUser and Busybox.
3.1] Once again connect your HTC to PC, Download the attached SuperUser.zip and copy it to your SD Card.
3.2] Open the command prompt again as said earlier by going to platform-tools folder and using the adb devices command to check if the phone is detected.
3.3] Once it is connected, Type the following command.
adb reboot recovery
Click to expand...
Click to collapse
3.4] Now you are in the recovery, Use the Volume Up and Down keys to navigate it (Use the power button to select an option).
Navigate to Install Flashable Zip. (This should be the first option and already selected.)
Press Power Button once.
Select "Choose Zip from internal SD-Card" or "external SD-Card" accordingly as to where you put the Superuser.zip.
Press Power Button once.
Scroll and select the Superuser.zip using the Volume Keys.
Press Power Button once.
Then you have flashed your Zip successfully and you are rooted.
Go back to the Main screen using the "Go back" option. Select the "Reboot System Now".
Once you are in the HTC Main screen > Go to App Drawer > Google Play Store > Search for Busy Box and Install it.
That is it, You are now on Jelly Bean and Successfully Rooted.
To Check If You Are Rooted.
1. Open Playstore and search for an app named "Terminal Emulator".
2. Install it.
3. Open it and type in su and execute it.
4. You will get a prompt from Superuser to allow or deny > Allow it.
If you get that prompt, You are successfully rooted.
I hope I have provided credits to all the users whose threads I have mentioned. If not please let me know.
Thanks for reading this.
Or you can refer to my TWRP for JB. Its much better than the fixed neXusRecovery.
Hey, I didn't check that.. Can you give a link to the recovery?
Droid.Anoop said:
Hey, I didn't check that.. Can you give a link to the recovery?
Click to expand...
Click to collapse
Here: http://d-h.st/tSc
xpirt
xpirt said:
Here: http://d-h.st/tSc
xpirt
Click to expand...
Click to collapse
Done. Added it to the post. Thanks Yasir and Xpirt
Droid.Anoop said:
Done. Added it to the post. Thanks Yasir and Xpirt
Click to expand...
Click to collapse
1 more little thing.
I think the instructions in recovery are using vol up down and power buttons. But if im not mistaken,, both my recoveries you mentioned are Touch enabled. So actually no need to bash the crappy volume buttons (i really hate these volume buttons due to bad tactile feedback)
neXus PRIME said:
1 more little thing.
I think the instructions in recovery are using vol up down and power buttons. But if im not mistaken,, both my recoveries you mentioned are Touch enabled. So actually no need to bash the crappy volume buttons (i really hate these volume buttons due to bad tactile feedback)
Click to expand...
Click to collapse
Actually I used the CWM Modded Recovery using Vol rockers only assuming it wasn't touch enabled due to its User Interface. The TWRP one is touch enabled. Are you sure the fixed recovery is touch enabled? As I don't want to flash the old recovery once again to test it.
Droid.Anoop said:
Actually I used the CWM Modded Recovery using Vol rockers only assuming it wasn't touch enabled due to its User Interface. The TWRP one is touch enabled. Are you sure the fixed recovery is touch enabled? As I don't want to flash the old recovery once again to test it.
Click to expand...
Click to collapse
Both my recoveries are touch enabled.
1. TWRP (JB)
2. neXusRecovery. (discontinued for updates)
I'm not really a fan of buttons.
Droid.Anoop said:
Actually I used the CWM Modded Recovery using Vol rockers only assuming it wasn't touch enabled due to its User Interface. The TWRP one is touch enabled. Are you sure the fixed recovery is touch enabled? As I don't want to flash the old recovery once again to test it.
Click to expand...
Click to collapse
Yes, also fixed recovery is touch enabled: you mean the nexus Recovery, right?
xpirt
xpirt said:
Yes, also fixed recovery is touch enabled: you mean the nexus Recovery, right?
xpirt
Click to expand...
Click to collapse
Yes, Thanks for letting me know. Also is there any method to unlock the write protection in JB? I think the JB Sources are not released yet but any workaround?
Droid.Anoop said:
Yes, Thanks for letting me know. Also is there any method to unlock the write protection in JB? I think the JB Sources are not released yet but any workaround?
Click to expand...
Click to collapse
I think ckpv5 found a way. Just think.
xpirt
xpirt said:
I think ckpv5 found a way. Just think.
xpirt
Click to expand...
Click to collapse
Wow that is cool! Wonder if he will share it soon. Or has he already shared it somewhere?
Droid.Anoop said:
Wow that is cool! Wonder if he will share it soon. Or has he already shared it somewhere?
Click to expand...
Click to collapse
Look at his ROMs: deodexed one and myOneDx+ have both hTC write permissions defeated.
xpirt
xpirt said:
Look at his ROMs: deodexed one and myOneDx+ have both hTC write permissions defeated.
xpirt
Click to expand...
Click to collapse
There is a wp_mod which has a Module file "wp_mod2.ko" and an init.d script, (credits to flar2) using which ckpv5 has made his roms.
neXus PRIME said:
There is a wp_mod which has a Module file "wp_mod2.ko" and an init.d script, (credits to flar2) using which ckpv5 has made his roms.
Click to expand...
Click to collapse
Can you explain how to implement it in stock ROM? Then we can integrate it in the tutorial with proper credits.
Droid.Anoop said:
Can you explain how to implement it in stock ROM? Then we can integrate it in the tutorial with proper credits.
Click to expand...
Click to collapse
Look at flar2's thread but use the files from ckpv5's ROM, but first ask him for permission.
xpirt
root JB without flashing custom recovery?
Hi!
I haven't flashed TWRP v2.5.0.0 but only boot the phone into this custom recovery, which is working perfectly. (I want to keep the stock recovery.)
I can install and use the Aroma File Manager (TWRP with Aroma File Manager did not work.)
I can mount the system partition and change / delete files.
However, with a reboot, all my changes will be undone.
Before installing Aroma File Manager for the first time, I installed SuperSu1.34.zip. No error. I installed Aroma File Manager right after it, and I think it said "rooted".
Using TWRP's SuperSu does not work (no error message, but system reboots, and it says it's not rooted.)
My question: can I root my phone while only booting into a non-stock recovery or do I have to flash TWRP and then root the phone?
Would I see the system apps e.g., after mounting /system, even if the phone was not rooted?
I am new to JB, I had 2.3.7 before, which I could root without flashing a custom recovery.
I am not sure if I have to flash the custom recovery because of the s-off problem with HTC devices?
If I flash a custom recovery and root the device, can I flash the stock recovery afterwards without loosing root again?
Would you recommend using SuperSu or Superuser? Which version?
I don't think I need busybox.
I only want to delete bloatware and change the battery symbol.
Thanks for your help!
I didn't try rooting using the stock recovery, but I think it won't be possible as it won't let us change system partition due to S-On. But after you rooted using a custom recovery you can flash the stock recovery again without loosing root. But keep in mind that you won't be able to change system partition. Also, you can't flash zips which aren't signed by HTC.
Sent from my HTC Desire X using xda premium
dansou901 said:
I didn't try rooting using the stock recovery, but I think it won't be possible as it won't let us change system partition due to S-On.
Click to expand...
Click to collapse
The question is if there is a difference if I just boot into the custom recovery vs. if it is flashed and I boot into it. Does ist need to be properly flashed to allow writing in /system?
mary-lou said:
The question is if there is a difference if I just boot into the custom recovery vs. if it is flashed and I boot into it. Does ist need to be properly flashed to allow writing in /system?
Click to expand...
Click to collapse
How do you boot into a custom recovery without flashing it first? It has to be on recovery partition to work correctly.