Ive noticed many people with older TWRP versions having problems with the updater script when installing 4.4 roms you need to be on the latest version of twrp (CWM may also need to be on a recent version). This tutorial will cover TWRP. Goo manager will not work for installing the latest TWRP recovery version on grouper. The following will give you the basics on how to use fastboot to flash a recovery.img (In this case twrp)
Things you will need:
A PC
Android SDK http://developer.android.com/sdk/index.html
TWRP recovery.img for grouper http://techerrata.com/browse/twrp2/grouper
A basic understanding of terminal/command prompt
You will need a PC and the android SDK (SDK http://developer.android.com/sdk/index.html) for fastboot to push the recovery file. TWRP can be found here (http://techerrata.com/browse/twrp2/grouper) you need the 2.6.3.0 version. Extract your android sdk and move your twrp image file (openrecovery-twrp-2.6.3.0-grouper.img) to the platform-tools folder in the sdk (This is where fastboot/adb are). For simplicity's sake rename your twrp file to recovery.img Enter command prompt or terminal depending on what OS you are using (windows/linux) and navigate to to your platform-tools folder in the SDK folder (where you should have moved your recovery.img) using the cd command. (plug device in) Once there check to see if you device is connected and seen with the adb devices command hopefully you will see a wonky alpha numeric code with "device" after it. If you dont you need to enter developer setting to enable adb. You do that by going into settings/about tablet and tapping build number 7 times. That should give you a developer options in settings check to make sure USB debugging is enabled. If all is well reboot your device into the boot loader with the adb reboot bootloader command once your device is at the bootloader check fastboot with fastboot devices you should see another wonky output with "fastboot" after it. The final command to push your new twrp image will be fastboot flash recovery recovery.img You should see some output saying how long it took to push the file it should not take that long. That should cover it! Now you should be good to go with the 4.4 rom's floating around.
There are many tutorials online explaining this process I just thought customizing it to the grouper would help those less comfortable with adb/fastboot. It's always a good idea to know how to use these tools you never know when you might need to use them. Anyone with question's feel free to ask.
Or just install flashify and it basically does all of this for you. I did it and it worked.
Sent from my Nexus 7 using XDA Premium 4 mobile app
blankit said:
Or just install flashify and it basically does all of this for you. I did it and it worked.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That will work. But knowing your way around adb/fastboot can't hurt. There won't always be a GUI to do everything for you.
blankit said:
Or just install flashify and it basically does all of this for you. I did it and it worked.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Didn't know of flashify, awesome. Thx, really fast and easy method. Best thing is I didn't even need my pc for it
Thanks for the tutorial but surely this belongs in q&a, help etc not android development ;p
Sent from my Nexus 4 using XDA Premium 4 mobile app
Actually it's suited to the General section (guides and all). I appreciate you advising the fastboot method (I use it too), but it can b a pain for people who don't have their devices configured (configuring it can be a pain sometimes too). Flashify, as one member said, is a great alternative. BUT you *may* brick your device if you flash something to the wrong block device (possibility of that happening to an expert user: 0.0001%; possibility of that happening to a new user: 1%). Just my two cents.
I agree guys this should be in general. I've never posted anything but a build and didn't even think about it. Do I need to get a mod to move it? As for flashify sounds like a great tool. I've never had the pleasure of using it but if it works and people are comfortable with it more power to it. Personally fastboot is what I'm comfortable with it might seem a little in depth but really its quite simple especially if you use adb for logcats and are setup.
OP No worries, moved and thank you.
To flash 4.4 ROMs one could follow this tutorial, or one could simply flash this .zip of the latest version of CWM:
http://forum.xda-developers.com/showpost.php?p=46053223
So, i've bricked it already.
Hello experts and knowledgeable persons!
First, i'm a noob.
I decided to flash KitKat as I play a WebView based game and thought the WebView Chromium of KitKat might make it run faster as it ran pretty slow. On the Paranoid Google+ page it says you need TWP 2.6 later and other sites say 2.6.x. I had 2.6.0.0, so did a backup of boot, data, system and recovery, copied to PC and then tried installing KitKat, it failed. So I updated to TWRP 2.6.3.0 and it failed again, tried a second time and it updated.
The game didn't work well on KitKat, so I restored my original version. I then decided to take screenshot of game not working on KitKat to complain, so tried installing KitKat again forgetting to update to 2.6.3.0 as the restoration of the backup restored the prevous 2.6.0.0 recovery, was a noob and tried again and i'm now left with a Nexus 7 in a boot logo loop.
Restoring the backup fails, as does installing the KitKat Zip or Opensensation . If I try flashing TWRP 2.6.3.0 via fastboot, it says success, but when I reboot the recovery i'm still in 2.6.0.0. I can boot into 2.6.3.0 using "fastboot boot", but it still won't restore the backup or flash. I also have a backup of the OpenSensation rom (wanted to try PDroid and it was the only rom I could find prepatched) which I made on 2.6.3.0, that won't restore either.
So now what do I do, as I don't want to make things worse. I am doing a factory reset before installing. The error i'm getting is "symlink: some failed"", "can't open destination log file: '/cache/recovery/log'" and "E:Unable to open '/cache/recovery/log'"
ziffius said:
Hello experts and knowledgeable persons!
First, i'm a noob.
I decided to flash KitKat as I play a WebView based game and thought the WebView Chromium of KitKat might make it run faster as it ran pretty slow. On the Paranoid Google+ page it says you need TWP 2.6 later and other sites say 2.6.x. I had 2.6.0.0, so did a backup of boot, data, system and recovery, copied to PC and then tried installing KitKat, it failed. So I updated to TWRP 2.6.3.0 and it failed again, tried a second time and it updated.
The game didn't work well on KitKat, so I restored my original version. I then decided to take screenshot of game not working on KitKat to complain, so tried installing KitKat again forgetting to update to 2.6.3.0 as the restoration of the backup restored the prevous 2.6.0.0 recovery, was a noob and tried again and i'm now left with a Nexus 7 in a boot logo loop.
Restoring the backup fails, as does installing the KitKat Zip or Opensensation . If I try flashing TWRP 2.6.3.0 via fastboot, it says success, but when I reboot the recovery i'm still in 2.6.0.0. I can boot into 2.6.3.0 using "fastboot boot", but it still won't restore the backup or flash. I also have a backup of the OpenSensation rom (wanted to try PDroid and it was the only rom I could find prepatched) which I made on 2.6.3.0, that won't restore either.
So now what do I do, as I don't want to make things worse. I am doing a factory reset before installing. The error i'm getting is "symlink: some failed"", "can't open destination log file: '/cache/recovery/log'" and "E:Unable to open '/cache/recovery/log'"
Click to expand...
Click to collapse
I'm sure this is not what you want to hear but if all else fails push the factory.IMG you will be starting from square one. You can try pulling your backups off but might as well start over for 4.4
blankit said:
Or just install flashify and it basically does all of this for you. I did it and it worked.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you very much for this recommendation. Really nice. Simple and took out all the nervousness of using the computer to push these files etc.
REally truly best for flashaholics.
question
Won't it work too if you just flash the zip from twrp itself? I'm running 2.6.3.2 and I read somewhere that i can simply install the new version (2.7.0.0.) zip from the recovery itself..Is it right??
Ergina95 said:
Won't it work too if you just flash the zip from twrp itself? I'm running 2.6.3.2 and I read somewhere that i can simply install the new version (2.7.0.0.) zip from the recovery itself..Is it right??
Click to expand...
Click to collapse
Did you ever try just flashing it and if so, did it work?
for some reason i cannot download the twrp ..it stuck at 99%
tried 2 version of twrp..hurm
Mookie2014 said:
Did you ever try just flashing it and if so, did it work?
Click to expand...
Click to collapse
yeap! did it! worked perfectly :good: just flash zip updates through the recovery
Related
The last time I flashed a custom rom to my phone was CyanogenMod-7.1.0-RC1-N1.
I'd really like to get ICS on it, but the process seems just so much more confusing this time around. If anyone give me a breakdown of what I'd need to do, or even if they could just point me in the right direction, I'd be grateful.
i never messed with that as they are always a lil buggy i like sense better ^_^ try asking people in that thread im sure they be happy to help you bro
sorry i couldn't help
Mintyass said:
The last time I flashed a custom rom to my phone was CyanogenMod-7.1.0-RC1-N1.
I'd really like to get ICS on it, but the process seems just so much more confusing this time around. If anyone give me a breakdown of what I'd need to do, or even if they could just point me in the right direction, I'd be grateful.
Click to expand...
Click to collapse
There are at least 3 ICS ROMs with 2 are in the working progress and the other we don't know what is the status of it. Spend some time to read first to gain some knowledge and procedures. They are in the Development section of Nexus One. And, remember, once you have Ice Cream Sandwich you don't want to have Gingerbread
u can flash this miui ics as like anyother roms before
http://forum.xda-developers.com/showthread.php?t=1479348
but for other ics roms u need to partition /system. for that first u need to know abt blackrose.
http://forum.xda-developers.com/showthread.php?t=1270589
Sent from my Nexus One using Tapatalk
The process is actually easier than the process you went through to root your phone and install CM7.
First, download the ICS firmware zip file to your phone's sdcard.
Next, make your backup using TitaniumBackup.
For most ICS firmware, you'll need to repartition your hboot. Google for blackrose-manual_120216.zip, download to your computer, unzip and look for the hboot_brcust-220-10-206.nb0 file. This one is pre-configured with the right partition sizes. Follow the instructions in the README file, which are basically:
Update your recovery firmware, by downloading to your computer and then using fastboot from your computer. I used the Amon-RA recovery for CM and stayed with it for ICS.
On the phone, enable USB Debugging in the CM Developer settings menu.
Boot the phone into the bootloader and go to FastBoot mode. It'll tell you what HBOOT you currently have. Read the instructions in the blackrose README to see which (if any) of the goXX.lol files you need. Then, on the computer:
Code:
fastboot flash recovery goXX.lol
fastboot flash recovery recovery-RA-passion-v2.2.1.img
Next, flash the new hboot:
Code:
fastboot flash hboot hboot_brcust-220-10-206.nb0
The blackrose-manual zip contains fastboot binaries for Linux, Mac and Windows. If you need a fastboot for FreeBSD, send me a PM.
Then boot into recovery, do a Nandroid backup, then a full wipe, then install the ICS firmware zip you put on the sdcard earlier.
That should be all. Once the new system is booted, you'll use Titanium again to restore your apps.
For what it's worth, the BCM firmware is based on CM with all the CM additions you're used to, so things will be pretty familiar. It's running well for me.
Jaiy said:
The process is actually easier than the process you went through to root your phone and install CM7.
First, download the ICS firmware zip file to your phone's sdcard.
Next, make your backup using TitaniumBackup.
For most ICS firmware, you'll need to repartition your hboot. Google for blackrose-manual_120216.zip, download to your computer, unzip and look for the hboot_brcust-220-10-206.nb0 file. This one is pre-configured with the right partition sizes. Follow the instructions in the README file, which are basically:
Update your recovery firmware, by downloading to your computer and then using fastboot from your computer. I used the Amon-RA recovery for CM and stayed with it for ICS.
On the phone, enable USB Debugging in the CM Developer settings menu.
Boot the phone into the bootloader and go to FastBoot mode. It'll tell you what HBOOT you currently have. Read the instructions in the blackrose README to see which (if any) of the goXX.lol files you need. Then, on the computer:
Code:
fastboot flash recovery goXX.lol
fastboot flash recovery recovery-RA-passion-v2.2.1.img
Next, flash the new hboot:
Code:
fastboot flash hboot hboot_brcust-220-10-206.nb0
The blackrose-manual zip contains fastboot binaries for Linux, Mac and Windows. If you need a fastboot for FreeBSD, send me a PM.
Then boot into recovery, do a Nandroid backup, then a full wipe, then install the ICS firmware zip you put on the sdcard earlier.
That should be all. Once the new system is booted, you'll use Titanium again to restore your apps.
For what it's worth, the BCM firmware is based on CM with all the CM additions you're used to, so things will be pretty familiar. It's running well for me.
Click to expand...
Click to collapse
Restore apps from GB backup might bring FC. It is better to download them from the Google Play
taodan said:
Restore apps from GB backup might bring FC. It is better to download them from the Google Play
Click to expand...
Click to collapse
While, in theory, you are correct, I restored my GB apps using TB because it is very fast to do so. In practice, they all appear to be working just fine. I believe I have run every one of them to make sure.
But I agree that a better general procedure would be to restore the apps themselves from the Play Store then restore your former app data using TB.
Jaiy said:
The process is actually easier than the process you went through to root your phone and install CM7.
First, download the ICS firmware zip file to your phone's sdcard.
Next, make your backup using TitaniumBackup.
For most ICS firmware, you'll need to repartition your hboot. Google for blackrose-manual_120216.zip, download to your computer, unzip and look for the hboot_brcust-220-10-206.nb0 file. This one is pre-configured with the right partition sizes. Follow the instructions in the README file, which are basically:
Update your recovery firmware, by downloading to your computer and then using fastboot from your computer. I used the Amon-RA recovery for CM and stayed with it for ICS.
On the phone, enable USB Debugging in the CM Developer settings menu.
Boot the phone into the bootloader and go to FastBoot mode. It'll tell you what HBOOT you currently have. Read the instructions in the blackrose README to see which (if any) of the goXX.lol files you need. Then, on the computer:
Code:
fastboot flash recovery goXX.lol
fastboot flash recovery recovery-RA-passion-v2.2.1.img
Next, flash the new hboot:
Code:
fastboot flash hboot hboot_brcust-220-10-206.nb0
The blackrose-manual zip contains fastboot binaries for Linux, Mac and Windows. If you need a fastboot for FreeBSD, send me a PM.
Then boot into recovery, do a Nandroid backup, then a full wipe, then install the ICS firmware zip you put on the sdcard earlier.
That should be all. Once the new system is booted, you'll use Titanium again to restore your apps.
For what it's worth, the BCM firmware is based on CM with all the CM additions you're used to, so things will be pretty familiar. It's running well for me.
Click to expand...
Click to collapse
This is great! I found blackrose_manual_120216.zip, but the only .nb0 file in it was hboot_blackrose.nb0. Will this work, or do I need to keep looking?
Mintyass said:
This is great! I found blackrose_manual_120216.zip, but the only .nb0 file in it was hboot_blackrose.nb0. Will this work, or do I need to keep looking?
Click to expand...
Click to collapse
The instructions are in the Blackrose thread in the Development section, you don't need to use the manual if you're using Windows.
I would read the blackrose thread so you understand what you are doing and why. Easier to get out of trouble and harder to get into it. You probably did same for CM7. The blackrose hboot is not easy to work with without knowing what you are doing. The backrose thread has pre requisites in OP, like install of drivers if you don't have them.
You guys sure the fastboot command for the exploit has the word "recovery" in it or should be:
fastboot boot go.lol
where go.lol is exact name of exploit from the actual blackrose binary folder depending what version of blackrose you are fastbooting. could be "fastboot boot go2.lol" etc
just a suggestion--
So I was able to use blackrose to repartition my system cache, but now I've got a problem. In the bootloader, when I select "Recovery" the phone hangs on the Nexus "X" logo, and I'm unable to get my phone to reboot into anything but the bootloader.
you probably lost recovery and need to re fastboot it
i once had to fastboot erase system before the recovery would flash
all these issues are in the thread
Would this be the correct thing to do? http://forum.xda-developers.com/wiki/HTC_Nexus_One/Recovery_Images
good info but if you have sdk and know fastboot do this
Copy recovery-RA-passion-v2.2.1.img to a location where fastboot can find it. Usually tools folder.
Boot your phone into fastboot mode (power on while holding the trackball)
Connect your phone via usb to your pc
type fastboot devices (to make sure that fastboot "sees" your phone)
type fastboot flash recovery recovery-RA-passion-v2.2.1.img or whatever exact name your recovery is
I was able to get into recovery, but now when I select "Flash zip from sdcard", I get an error saying that there was No Signature and that the Verification Failed.
Mintyass said:
I was able to get into recovery, but now when I select "Flash zip from sdcard", I get an error saying that there was No Signature and that the Verification Failed.
Click to expand...
Click to collapse
You need to disable the signature verification in the recovery and then flash the ROM
Thanks so much for everyone's help! I've got ICS up and running now thanks to you.
Since this forum account is too new to post in the BCM thread, I guess I'll try asking a question here instead.
So far there's two problems I've encountered that would be dealbreakers for BCM. I saw on the BCM thread that voice search is currently broken, but it seems like it's kind of unexpected and will likely be fixed. The other issue I have, that I can't find anyone else complaining about, is that I don't seem to have the Car Home app anymore. Has anybody else run into this issue, or know a fix? I use my phone in my car pretty much every day in my car dock, and make extensive use of both the car home app and the voice search feature for getting navigation directions.
If there's a better place to post these questions, feel free to let me know!
Thanks
audio has been ab issue for me and others on ics and sense roms lately, don't know why. i am back on CM7 Kangs atm bc of it. hope it is found and fixed. the current remedies don't work for me
glad you are up and running, all these roms have issues of some type for a few at least. goes with the territory--
someone should be able to get you a car home apk you can install or push thru adb--i always delete mine as i don't use--sorry. might be able to find it thru search/google
posting here is perfectly fine--it a couple general threads for a "meaningful" post and you will be to ten real quick
enjoy rom
ken
Mintyass said:
This is great! I found blackrose_manual_120216.zip, but the only .nb0 file in it was hboot_blackrose.nb0. Will this work, or do I need to keep looking?
Click to expand...
Click to collapse
Sorry, I wasn't watching this thread over the weekend and I see you have already moved past this. But to answer the question...
I thought the pre-partitioned blackrose-220-10-206 was in that zip, but I see now that I found it on the Evervolv ROM thread in the Nexus One development forum. Sorry for not remembering to mention that.
---------- Post added at 12:08 PM ---------- Previous post was at 11:58 AM ----------
Mintyass said:
Thanks so much for everyone's help! I've got ICS up and running now thanks to you.
Click to expand...
Click to collapse
You're welcome.
So far there's two problems I've encountered that would be dealbreakers for BCM. I saw on the BCM thread that voice search is currently broken, but it seems like it's kind of unexpected and will likely be fixed. The other issue I have, that I can't find anyone else complaining about, is that I don't seem to have the Car Home app anymore. Has anybody else run into this issue, or know a fix? I use my phone in my car pretty much every day in my car dock, and make extensive use of both the car home app and the voice search feature for getting navigation directions.
Click to expand...
Click to collapse
BCM Version RC3.3Ux has very broken voice input. Many folk (including me) have commented that no VoIP apps work with it. Hopefully this will be fixed soon. BCM3.2U2 works fine, so I have reverted to that version for now.
You can install the CarHome app from the Play Store; it doesn't seem to be included in the BCM zip file.
Rom Manager was just updated to version 5.0.2.4 and allows you to flash to CWM 6.0.1.6 recovery. Booting to recovery just gives me the Android with a red flag though. Just a FYI till it gets sorted.
Pressing and holding the pwr button will boot you back to the OS. Not a huge deal as we don't have anything to flash at the moment.
If you need to get back to the stock recovery in the meantime which can be found in this thread
http://forum.xda-developers.com/showthread.php?t=1993331
Edit:
Don't Flash this yet, you'll have to re-install the stock recovery or wait for a fix and could possibly brick your phone if you don't know what you're doing.
Is there like an easy way to root other than manually adb pushing? Flashable zip maybe?
I get the same thing as you, says flash successful then the red flag.
F4M0U569 said:
Is there like an easy way to root other than manually adb pushing? Flashable zip maybe?
Click to expand...
Click to collapse
You can use the temporary "boot" method as opposed to "flash" when using the current CWM recovery which is posted here http://forum.xda-developers.com/showthread.php?t=1993331
Don't flash the recovery yet though, it's obviously not sorted. I used the adb method to root which worked fine. I got excited when I saw the new Rom Manager which allowed me to flash recovery because Koush's G+ messages earlier today.
kchino said:
You can use the temporary "boot" method as opposed to "flash" when using the current CWM recovery which is posted here http://forum.xda-developers.com/showthread.php?t=1993331
Don't flash the recovery yet though, it's obviously not sorted. I used the adb method to root which worked fine. I got excited when I saw the new Rom Manager which allowed me to flash recovery because Koush's G+ messages earlier today.
Click to expand...
Click to collapse
I tried using the adb boot method but it doesn't work for me. After booting the insecure boot and taking me to the Android screen, I tried using the codes listed there but it says no device found.
F4M0U569 said:
I tried using the adb boot method but it doesn't work for me. After booting the insecure boot and taking me to the Android screen, I tried using the codes listed there but it says no device found.
Click to expand...
Click to collapse
i did it last night and it was quite late, but if i remember correctly i had the same problem but just had to reselect USB debugging
Sent from my Nexus 7 using xda app-developers app
Hey guys, long time lurker and now first time poster. Shame it has to be something very stupid.
So anyways, I wanted to flash the latest CM10.2 Unofficial build so I did the usual and downloaded the zip & gapps to my phone. But upon wiping my phone via TWRP I accidentally left the wipe userdata part checked and ... well now I have no OS installed as well as no zip's :/
I have TWRP installed so I thought why not sideload it, however when I go to advanced -> adb sideload it never starts up. This is the log:
Updating partition details...
Starting ADB sideload feature...
Click to expand...
Click to collapse
And it just stays there
I know that my ADB works as I have S-OFF & unlocked the bootloader and flashed the latest 1.54.0000 hboot so I can definitely use it, I just don't understand why it doesn't let me sideload for some reason.
Either way, I have full access to fastboot & TWRP recovery so i'm hoping this is a pretty simple thing to fix ... right?
Can anybody point me to the right direction?
Details:
No OS installed.
Access to TWRP & fastboot.
S-OFF, Modified Hboot 1.54.0000 (SuperCID) & Unlocked bootloader.
Windows 8 64-bit, drivers all work.
Latest SDK with all the binaries installed.
P.S. when I connect and try and use adb devices it doesn't recognise my device, and the cmd window gives the following when I try the sideload command:
Error: device not found.
Click to expand...
Click to collapse
Sounds like a driver issue to me but it doesn't make sense that the drivers would suddenly stop working ???
Here are screenshots of odd device behaviour when switching from fastboot to recovery (please copy & paste, I don't have enough posts to post images yet):
i.imgur.com/V79DFFA.jpg
i.imgur.com/MKD5C9U.jpg
Bump for help
I can't seem to get sideload to work in TWRP at the moment either. CWM works fine though, try flashing that and use the sideload feature.
Sent from my HTC One using xda premium
redbull123 said:
I can't seem to get sideload to work in TWRP at the moment either. CWM works fine though, try flashing that and use the sideload feature.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Tried that already, same issue in not detecting the device. I'm downloading these drivers in a hope to fix something.
Thanks for the reply
EDIT:
Finally got sideloading in TWRP to work, it turns out it was a driver issue :/
Anyways, these are the drivers that worked:
androidfiles.org/hasoon2000/getdownload.php?file=HTC%20Drivers/HTCDriver.exe
why is everyone always wiping their storage these days? just use CWM next time and you wont accidentally do this again..
IINexusII said:
why is everyone always wiping their storage these days? just use CWM next time and you wont accidentally do this again..
Click to expand...
Click to collapse
TWRP is much better for people who know what they are doing. There are more options and also a built in file manager. Also, the wipe button in TWRP wipes the 3 main partitions at once (data/cache/dalvik), so he must have actually selected internal sdcard from the advanced menu, and I have no idea why he would do that...
Doing the slider is all anyone needs to do in twrp to wipe yet I read more posts about people wiping with twrp than any other problem in these forums
Hi Guys,
I have a Samsung Note for Tmobile, the t879 model. I had it rooted and the person installed cwm version 5.5.0.4. I would like to update it to the latest version for my device which seems to be 6.0.4.3 (according to cwm website).
The reason i want to update is because I want to, at some point, install custom jelly bean/kitkat/other rom. I've had some issues attempting to install custom jelly bean rom already.
I tried Rom Manager and my device is not supported, plus i've read several threads that suggest not using rom manager anyway.
I think from what I think i've gathered so far, i have to flash a custom cwm kernel?
Is that correct?
Is there a tutorial somewhere that caters to my device.
Where might I find this kernel, if that's what i need to do.
Can my existing cwm install newer cwm (doubt it but it's worth a shot asking)
Any advice, comments, or general counsel you can offer is appreciated, i'm going on 3 days of searching
You guys are great, I've enjoyed reading your threads and look forward to any help you can offer.
The updated cwm is on the cwm web site, but it is in img format, which means you have to use adb on the command line to overwite your current recovery with the new one.
I took a flashable zip from another phone and replaced the img file inside with the tmobile one and that is what I use. Here it is if you want to use it: https://drive.google.com/file/d/0Bx_IbXnhPXBJRlFxR0VlSXVhRTQ/edit?usp=sharing
Make sure you know and pay attention to what you are doing, screwing up the recovery will be a bad day.
Jellybean roms use TWRP recovery. http://teamw.in/project/twrp2/113
Some have had better luck with 2.5.0.0, but the latest version should work also.
You need to have a copy of twrp and a copy of cwm on your sdcard so that you can go back and forth between jellybean and kitkat, if that is what you want.
Do your system wipe/factory reset in the recovery that you will use to flash. So going to Kitkat, first reboot into recovery, do a full backup of everything, then flash the cwm zip, then reboot into cwm recovery, then do factory reset, then flash your rom zip, then flash THE CORRECT GAPPS, then you can reboot.
Going back, same thing. Recovery, backup, flash twrp, reboot, recover your backup.
Gapps are important, there are 2 different jellybean gapps one for 4.3 and one for 4.4 Kitkat, be sure you flash the right ones or, you will just get an error, or you will get errors when starting up, either way it won't work. http://wiki.rootzwiki.com/Google_Apps
This thread is where you get the 4.4 Kitkat gapps, full package is fine, just be sure it is the 4.4 one. http://forum.xda-developers.com/showthread.php?t=2397942
Read the ATT forum also as the device is the same, but don't flash ATT roms unless you are using the patch. http://forum.xda-developers.com/showthread.php?t=2573315
Lot to read and understand and lots of files to get on your sdcard before you proceed. Good luck.
I can tell your post will be a super helpful resource, thank you for that.
I took a flashable zip from another phone and replaced the img file inside with the tmobile one and that is what I use. Here it is if you want to use it
are these my options, basically I can either override cwm with an adb command or flash the rom you shared above? I'm just a little unclear on that?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
dje0624 said:
I can tell your post will be a super helpful resource, thank you for that.
I took a flashable zip from another phone and replaced the img file inside with the tmobile one and that is what I use. Here it is if you want to use it
Click to expand...
Click to collapse
are these my options, basically I can either override cwm with an adb command or flash the rom you shared above? I'm just a little unclear on that?
Click to expand...
Click to collapse
Yes. Here is the clockworkmod download page. Scroll down for the tmobile note: http://www.clockworkmod.com/rommanager
Look in the "recovery" column, click on the one for tmobile and you get a recovery.img file.
To get the adb instructions to install it, you have to go to the TWRP page for this device: http://teamw.in/project/twrp2/113
"You can use adb or terminal emulator to install the following image:
adb push openrecovery-twrp-2.3.1.1-sgh-879.img /sdcard
adb shell dd if=/sdcard/openrecovery-twrp-2.5.x.x of=/dev/block/mmcblk0p22"
So you can do the same thing with the recovery.img from the clockworkmod page.
Now download the zip I gave you, verify that the recovery.img inside is the same as the one on the clockworkmod page. Do an md5 on it to check, pretty sure its the same version. Check the updater script, it is the same command as above. Also, I believe the original post in the "patch" thread that I linked you to has a flashable zip file for clockworkmod as well.
Either of the zips you just flash in your current recovery. Much easier and less room for making a really unfortunate mistake.
srpanadero said:
"You can use adb or terminal emulator to install the following image:
adb push openrecovery-twrp-2.3.1.1-sgh-879.img /sdcard
adb shell dd if=/sdcard/openrecovery-twrp-2.5.x.x of=/dev/block/mmcblk0p22"
So you can do the same thing with the recovery.img from the clockworkmod page.
Now download the zip I gave you, verify that the recovery.img inside is the same as the one on the clockworkmod page. Do an md5 on it to check, pretty sure its the same version. Check the updater script, it is the same command as above. Also, I believe the original post in the "patch" thread that I linked you to has a flashable zip file for clockworkmod as well.
Either of the zips you just flash in your current recovery. Much easier and less room for making a really unfortunate mistake.
Click to expand...
Click to collapse
I think the adb method is a bit to advanced for me at the moment. I'd be happy if I could just get Jelly Bean going, I'm on ics at the moment.
I will put updating cwm on hold for now. Can you install twrp with odin or goomanager when cwm is installed? Are there any special considerations?
Thanks man
Of course the adb stuff is not the best way to go about it. Just use the flashable zip. Or install goo manager and allow it to install it. Check the twrp link that I gave to you. Instructions are there. I can upload a twrp zip a little later.
Sent from my ASUS Transformer Pad TF300T using Tapatalk
srpanadero said:
Of course the adb stuff is not the best way to go about it. Just use the flashable zip. Or install goo manager and allow it to install it. Check the twrp link that I gave to you. Instructions are there. I can upload a twrp zip a little later.
Sent from my ASUS Transformer Pad TF300T using Tapatalk
Click to expand...
Click to collapse
I ended up just flashing twrp with cwm and it worked it flawlessly. Now I just have to find my perfect rom
Thanks again for your help
i have been downloading CM nightlys to my pc, copying them to my phone's internal storage, then flashing the zip using recovery (twerp v2.6.3.0) successfully for 3 or 4 months. I found CM Downloader app on the app store and down loaded that. I set the setting to automatically check for a new build, and download it. it did download the new builds although they failed to flash. 3 days after this started happening, CM came out with a 'snapshot' version. that one flashed ok. but the 'nighly' builds no longer flash. I have uninstalled CM downloader, and tried downloading them to the PC and copying them to the phone, that no longer works either. I have reinstalled CM downloader no change. so I think there is something changed on the phone that needs to be fixed, or reset or something. I appreciate any ideas here, I am still entry level skill level, so be gentle
blairman
TWERP failed flash message
blairan said:
i have been downloading CM nightlys to my pc, copying them to my phone's internal storage, then flashing the zip using recovery (twerp v2.6.3.0) successfully for 3 or 4 months. I found CM Downloader app on the app store and down loaded that. I set the setting to automatically check for a new build, and download it. it did download the new builds although they failed to flash. 3 days after this started happening, CM came out with a 'snapshot' version. that one flashed ok. but the 'nighly' builds no longer flash. I have uninstalled CM downloader, and tried downloading them to the PC and copying them to the phone, that no longer works either. I have reinstalled CM downloader no change. so I think there is something changed on the phone that needs to be fixed, or reset or something. I appreciate any ideas here, I am still entry level skill level, so be gentle
blairman
Click to expand...
Click to collapse
Updating partition details
Processing OpenRecoveryScript file
unable to locate zip file "/CyanogenRob_Downloa
E:Error installing zip file "/CyanogenRob_Downloa
Don processing script file
Installing ' /sdcar/CyanogenRob_Downloader/cm1
skipping MD5 check: no MD5 file found
E:Error executiong updater binary in ' /sdcar/CyanogenRob_Downloader/cm1
Error flashing zip ' /sdcar/CyanogenRob_Downloader/cm1
updating partition details
then under that in red letters "Failed'
blairan said:
Updating partition details
Processing OpenRecoveryScript file
unable to locate zip file "/CyanogenRob_Downloa
E:Error installing zip file "/CyanogenRob_Downloa
Don processing script file
Installing ' /sdcar/CyanogenRob_Downloader/cm1
skipping MD5 check: no MD5 file found
E:Error executiong updater binary in ' /sdcar/CyanogenRob_Downloader/cm1
Error flashing zip ' /sdcar/CyanogenRob_Downloader/cm1
updating partition details
then under that in red letters "Failed'
Click to expand...
Click to collapse
TWRP that works:
http://forum.xda-developers.com/showpost.php?p=50383573&postcount=3
Why (changelog):
http://forum.xda-developers.com/showpost.php?p=50383578&postcount=4
i'm part way there...
tdhite said:
TWRP that works:
http://forum.xda-developers.com/showpost.php?p=50383573&postcount=3
Why (changelog):
http://forum.xda-developers.com/showpost.php?p=50383578&postcount=4
Click to expand...
Click to collapse
OK, I have downloaded the 2 files. placed them in a directory near my root directory on my pc. placed the phone in fastboot usb, opened a command prompt window from that directory. typed in fastboot flash recovery openrecovery-m7wls-2.7.0.9-05-01-2014
and I get error: cannot load 'fastboot flash recovery openrecovery-m7wls-2.7.0.9-05-01-2014'
per a video showing how to flash recovery, I also tried the command adb reboot bootloader I get error : device not found
back to my pc, I open device manager, and I show a device labeled android device that is working properly.
stumped at this point.
is updating recovery the same as the initial install of a custom recovery?
do I need updated drivers for win 7? where are the latest? all videos say they are the latest, but that was when they were recorted.
thanks for help!
Yes u need updated drivers....any easy solution however is go and get the app flashify u will need root of course...it allows u to flash recovery that is on ur sd card. Just choose the img and flash recovery in the app then reboot into recovery and u will be good to go.
Sent from my HTCONE using Tapatalk
Thank you!
Thanks to both of you, updated TWERP did the trick and Flashify allowed me to install it without the fastboot, and PC hookup which was not working. Latest nightly installed, I am a happy camper!
Ok, let me get this straight, snag this Flashify, then snag TWRP 2.7.1.1, flash it with Flashify and I am golden????
(I am unlocked and S-Off running CM-11)
Slagathor01 said:
Ok, let me get this straight, snag this Flashify, then snag TWRP 2.7.1.1, flash it with Flashify and I am golden????
(I am unlocked and S-Off running CM-11)
Click to expand...
Click to collapse
All u have to do is update your recovery. So u can grab the latest TWRP and flash it any method u wish. Fastboot is best but flashify is the most convenient. After u flash your recovery the CM Rom should flash perfectly. Note: If u experience any failures in flashing any Rom that u know is good just downgrade your recovery via which ever method u prefer and that should flash fine now. You can always use the recovery zip floating around on the android development thread I'll see if I can find it for u.
Here u go bud http://forum.xda-developers.com/showthread.php?t=2656065
Note if the flash fails try a older zip until it works and flash the twrp by TD. Don't forget to thanks rootlinux for the zips. Might also want to keep the zips in handy on the phone storage incase the Note situation appears.
Sent from my HTCONE using Tapatalk
luigi311 said:
All u have to do is update your recovery. So u can grab the latest TWRP and flash it any method u wish. Fastboot is best but flashify is the most convenient. After u flash your recovery the CM Rom should flash perfectly. Note: If u experience any failures in flashing any Rom that u know is good just downgrade your recovery via which ever method u prefer and that should flash fine now. You can always use the recovery zip floating around on the android development thread I'll see if I can find it for u.
Here u go bud http://forum.xda-developers.com/showthread.php?t=2656065
Note if the flash fails try a older zip until it works and flash the twrp by TD. Don't forget to thanks rootlinux for the zips. Might also want to keep the zips in handy on the phone storage incase the Note situation appears.
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
I got it with fastboot, I forgot I re installed windows since I did it initially, so I was pulling my hair out wondering why fastboot wouldnt see it, and I couldnt even get files to or from it till I installed HTC sync.....heh
thanks for the info.....