I've been trying to install a custom rom to my htc hero (gsm) but it seemes like i can't root it properly.. i've used androot to root with, and tjecked if the mobile was rooted through busybox and various apps, and it all tjecks out, it gives su permission to the android terminal, and i can delete obligatory apps that i dont need from the phone without a problem, but when i try to setup another recovery to install custom roms im stuck, the terminal can't go that far.. just trying to reboot from the terminal isn't allowed..
So have anybody experienced the same issue?
and idea what to try next?
There was the same thing with my phone
Then I found a thread which said there are several different ways to apply recovery.zip. some of them difn't work for me either. Now I can't remember which method worked for me, but I'll share tgat thread as soon as I get to my notebook just wait for it
Sent from my HTC Hero using XDA App
ok, this is how I have done.
put the recovery.zip in SD card
run Androot and do ROOT.
run Terminal Emulator.
execute the following commands
su (wait for superuser request and accept it)
flash_image recovery /sdcard/recovery.img
the reboot command won't work, so just turn off the phone and boot into recovery (Home+Power)
that's it.
If this method doesn't work, try this one
do Androot
run ROM Manager
press "Flash clockwork recovery"
grant superuser permissions
wait
boot into recovery
And another way to apply recovery via Droid Explorer
download and install Droid Explorer on your PC
USB Debugging must be turned on in the phone
connect via usb and run the program
coose Flash Recovery Image plugin and fill th path to recovery.img
It should do the job...
you sir. are awesome!
i've tried the two first methods before, they didn't work
but the last one did
another question now:
im in the system recovery and i've done everything i need to install a custom rom (cyanogenmod) but it stops installing:
E: No signature (775 files)
E: Verification failed
Installation aborted.
what to do now?
first of all, I'm not a Sir. I'm a Miss
and I'm glad I helped you
and third. Personally I haven't tryed cyanogenmod, so I'm not sure why the install package couldn't be verified. Try redownloading the zip. Maybe it is corrupt. If not, did you follow ALL these steps? I found it in this thread with the same question as yours. And he solved it this way.
Hope this will help...
hmh didn't expect that, and your quite smart too ^^
it's way my own fault, i repacked the zip that was the problem
cyanogenmod is damn nice
though it's the first rom ever to try out, it seems stable enough..
it's just good to fully control your own device
thanks
And yeah, cyanogen is nice
Sent from my HTC Hero using XDA App
FIX ::D
LMFAO was about to post that same thing arvan had (in my own words) till i actually read the whole threat.
THanks to Arvan its exactly how u fix this issue
]Verification issue
flash clockworkmod recovery 2.5.0.7 by installing rom manager and pressing on the option
to fix the signature issue press on install zip from sd, then on toggle signature verification on your clockworkmod recovery if u have this. if not try flashing this recovery image its very complete and useful
then choose form sd and as it says choose your rom and flash and reboot
there u go
have a good day
Wishhes the best for your hero
~Jseb
HEro deV
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.
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.
So I got the 5.12.10 update for the weekly developer ROM and it installed stock recovery over TWRP and unrooted my phone. The first time I rooted I managed to flash TWRP with stock recovery, but it isn't working this time. I've had a lot of trouble trying to install via ADB drivers. Help please?
PytSkee said:
So I got the 5.12.10 update for the weekly developer ROM and it installed stock recovery over TWRP and unrooted my phone. The first time I rooted I managed to flash TWRP with stock recovery, but it isn't working this time. I've had a lot of trouble trying to install via ADB drivers. Help please?
Click to expand...
Click to collapse
Did you rename TWRP to update.zip and put it on the root of the internal storage before flashing? If yes and it still failed, you'll have to give us a bit more info as to why it failed to flash (any error messages f.e.?). Should be fairly trivial to flash TWRP and SuperSU
elaurens said:
Did you rename TWRP to update.zip and put it on the root of the internal storage before flashing? If yes and it still failed, you'll have to give us a bit more info as to why it failed to flash (any error messages f.e.?). Should be fairly trivial to flash TWRP and SuperSU
Click to expand...
Click to collapse
It wasn't too difficult the first time, but the recovery seems to be using some sort of signature on the ROM's. All it tells me is that "Install update.zip failed! update.zip signature verification failed." It is named update.zip on the root of internal storage.
PytSkee said:
It wasn't too difficult the first time, but the recovery seems to be using some sort of signature on the ROM's. All it tells me is that "Install update.zip failed! update.zip signature verification failed." It is named update.zip on the root of internal storage.
Click to expand...
Click to collapse
Hm, from what I've found on the miui forum, you're not the first one having this issue. These are the "possible" solutions I've gathered from a couple of threads.
1) Flash TWRP using fastboot (rename twrpxxxx.zip to recovery.zip and place it in the same folder as the fastboot executable):
Code:
fastboot oem unlock
fastboot flash recovery recovery.img
2) Update your current ROM (stable/developer) to the latest version if that isn't the case yet and try flashing TWRP again trough the update app
3) Flash TWRP using Flashify
1. download flashify app from playstore and give root acces
2. download img of twrp for redmi 2 note and put in your sd card (I prefer sdext root folder)
3. Open flashify, select "recovery image", find the img file you've downloaded
4. confirm flash, wait until it's done
4) Re-download a copy of TWRP or use a different one (like this one for example)
Let me know how it went..
So I tried Flashify and every time I tried to use it, the app froze right before/after selecting the recovery image. I did, however, manage to make the ADB and fastboot methods work on my desktop PC. I have no idea what I did wrong before, maybe the wrong ADB drivers? Anyway, I did get it working, so thank you
PytSkee said:
So I tried Flashify and every time I tried to use it, the app froze right before/after selecting the recovery image. I did, however, manage to make the ADB and fastboot methods work on my desktop PC. I have no idea what I did wrong before, maybe the wrong ADB drivers? Anyway, I did get it working, so thank you
Click to expand...
Click to collapse
Used windroid to do all these: http://en.miui.com/forum.php?mod=viewthread&tid=167882&extra=pag
Sent from my Redmi Note 2 using Tapatalk
timberwolf60 said:
Used windroid to do all these: http://en.miui.com/forum.php?mod=viewthread&tid=167882&extra=pag
Sent from my Redmi Note 2 using Tapatalk
Click to expand...
Click to collapse
I remember seeing this right after I ordered my phone. I had totally forgotten about it by the time I got it though, as it was more than a month later But thanks for reminding me, I already have it installed on my home PC!
Just got a uhappy up580 mtk6580 5.1LP phone.
All sorts of problems with it if I try to do anything with it, as stock it works great, no issues. Install kingroot as thats the only way to root it, Ive tried them all... Cannot remove kingroot for super SU using ANY way including superSUme, all things on here and needrom etc... cant do it.
I cant unlock the bootloader using everything I've found on here, from simply selecting it in settings to ADB on the PC and terminal in root shell, says 'not permitted' or 'not allowed' or rewboots to a selection screen and the volume up button to select it wont work.
Cannot remove install.recovery.sh using an old esfile explore, root explore, adb root shell on PC and terminal etc... all say, not permitted or 'system is r/o' Used commands to r/w system but again, this isnt allowed/permitted.
Installed chainfires 'secureADB' I think it was called to allow ADB to to be used root in system, does nothing.
MTKdroidTools doesnt work on MTK6580 so cant get CWM recovery flashed that way.
Have downloaded numerous CWM/PhilzTouch/TWRP and tried to flash them with SPtools, and removing battery before rebooting recovery and that also, doesnt work.
MTKunpacktools cant unpack the recovery.img of stock rom....
Am really at the end of my tether now.
I have the full stock rom installed, and a full SPFlashTools stock back-up if anyone has any ideas? All I'm really wanting is Xposed installed, thats it, and know with another chainfire app I can flash a zip without a recovery, but needs super SU which I cant get installed....
Dont worry, sorted it.