Hello,
I cannot make sense of either the written directions or the Youtube video. They assume knowledge that I do not possess. Speaking of which...
In the "flash a recovery" step, is this supposed create a recovery image of some sort, or flash an already existing one onto the phone. If the latter, where does this recovery image come from?
In the kernel step, it says to place your kernel in the /Data/Kernel directory. How am I supposed to obtain the kernel image?
Thank you in advance.
(I posted this here because I do not have the necessary permissions to reply to Hansoon2000's thread)
psterrett said:
Hello,
I cannot make sense of either the written directions or the Youtube video. They assume knowledge that I do not possess. Speaking of which...
In the "flash a recovery" step, is this supposed create a recovery image of some sort, or flash an already existing one onto the phone. If the latter, where does this recovery image come from?
In the kernel step, it says to place your kernel in the /Data/Kernel directory. How am I supposed to obtain the kernel image?
Thank you in advance.
(I posted this here because I do not have the necessary permissions to reply to Hansoon2000's thread)
Click to expand...
Click to collapse
Assuming you are S-on you dont have to flash a kernel if you are just rooting it
Root your phone, S-off it(If you want to... I recommend it), and just flash a rom via recovery
I believe the recovery is in the folders already? Can anyone confirm?
bilibox said:
Assuming you are S-on you dont have to flash a kernel if you are just rooting it
Root your phone, S-off it(If you want to... I recommend it), and just flash a rom via recovery
I believe the recovery is in the folders already? Can anyone confirm?
Click to expand...
Click to collapse
Correct CW or WCX just have to choose which you want
It's pretty straight forward and noob friendly...follow instructions to unlock bootloader, choose cwm or wcx recovery then press button to flash...kernel is optional, if you want one download one from here and put it in the kernels subfolder...
Everything comes from/is located in the data folder and its sub-directories you also extracted
Sent from my HTC PH39100 using xda app-developers app
Thank you
Thanks for the replies. I found a simpler to follow method, using fastboot.exe and an included recovery image, and successfully rooted the phone.
Now, I'm going to do some RTFMing, so this won't be an issue again.
One piece of information that might help you is understanding that the term "recovery" can mean two things. In the context of "flashing a recovery" in the process of rooting your phone, what this means is flashing a recovery tool to the recovery partition of your phone. Your phone has a special place set aside for a backup OS (or recovery tool) in case things go south for your actual OS. The recovery you can flash with the all-in-one tool will install CWM (ClockWorkMod), or WCX. Personally, I use CWM. By holding the power key and volume down when you start your phone, you gain access to the boot menu, where you can load the recovery tool. This allows you to do all sorts of powerful things, from flashing kernels and ROMS, to preforming backups and restores, to clearing caches, and all sorts of other power-user type functions.
Hope that helps, and glad you got your phone rooted. These things are a lot of fun once you open them up a little
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.
My question is similar to 'nikpmr's troubles but different enough I think they deserve a separate post.
The Problem as UnderstoodI was trying to root my device following the guide at this website. It's so simple it's a wonder I messed up. I think my failure was that I thought the drivers installed when I connected the phone were enough so I skipped that step. Then when running fastboot flash recovery.img the install failed. So I saw on some forum that it was supposed to be fastboot flash boot recovery.img of course now I know if anything it ought to have been "recovery" not "boot".
What I've Tried & Partial SolutionAt first I was just stuck in a boot loop and selecting "sideload" from the CWM recovery failed to allow me to connect with ADB or fastboot. i.e. Running "fastboot devices" and "adb devices" both returned as having no devices connected to my computer. So I installed the HTC Sync and promptly uninstalled the non driver parts of the app. Then I installed USBdeview and used it to uninstall all the USB devices associated with my HTC First. After doing that I learned booting into HBOOT allowed me to connect to the computer using fastboot and after then booting to the CWM Recovery I was able to connect using ADB to do a sideload. So I guess I'm about halfway there. Unfortunately after looking up the newest RUU and attempting to sideload it using "adb sideload OTA_MYST_UL_1.08.502.1-1.08.502.4.zip" the sideload failed. After selecting "- install zip from sideload" I get a message twice of "failed to open driver control: No such file or directory". It also failed when I attempted it with a similar fastboot command. So from all that I surmise my ROM is ruined and just needs to be replaced.
QuestionSo how do I go about replacing this ROM and boot partition? And, which ROM should I use? Is the one I got from the RUU site suitable? And what about the radio? I just need my phone to work. I can worry about rooting later. At this point I think I know what's happened but I don't know where to begin reading to figure out how to fix it myself.
Thanks for reading,
Relevant HBOOT text:
Code:
*** TAMPERED ***
*** UNLOCKED ***
MYSTUL PVT SHIP S-ON RL
HBOOT-2.00.0000
RADIO-1.15.40.00.13_2
OpenDSP-v9.2.0268.1214
eMMC-boot
Mar 22 2013,21:29:50:1682
1. you had to type in fastboot flash recovery recovery.img NOT fastboot flash boot recovery.img
Well there was an actual all in 1 tool to get cwm/twrp & root with a click for this specific device somewhere around these threads.
1) what exactly is the problem? (Sorry it was just so many words)
I don't think side loading the RUU would work bc I haven't heard its possible to flash it in the phone itself.
2) why don't you just sideload an existing pre-rooted ROM instead of the RUU file?
3) I see you're s-on, did you try flashing just the boot.IMG from the ROM you've got on it?
BTW I've only had luck with twrp on having it successfully detected when wanting to sideload
abrahammmmmmm_ said:
Well there was an actual all in 1 tool to get cwm/twrp & root with a click for this specific device somewhere around these threads.
1) what exactly is the problem? (Sorry it was just so many words)
I don't think side loading the RUU would work bc I haven't heard its possible to flash it in the phone itself.
2) why don't you just sideload an existing pre-rooted ROM instead of the RUU file?
3) I see you're s-on, did you try flashing just the boot.IMG from the ROM you've got on it?
BTW I've only had luck with twrp on having it successfully detected when wanting to sideload
Click to expand...
Click to collapse
1) The issue is I did "fastboot flash boot recovery.img" rather than "fastboot flash recovery.img" now I don't seem to have a boot mount point.
2) That sounds best. I didn't realize the RUU want a flashable ROM. More I just have to find the updated stable stock ROM.
3) I didn't have a ROM on it. I was just trying to root stock. Seems like I'm pretty close once I find that ROM.
Thanks y'all! Between your answers I think I have enough to go on. Feel free to point me to your preferred stable ROM. I'm content with stock but it would be nice to have Tiranium BU.
bnjo said:
1) The issue is I did "fastboot flash boot recovery.img" rather than "fastboot flash recovery.img" now I don't seem to have a boot mount point.
2) That sounds best. I didn't realize the RUU want a flashable ROM. More I just have to find the updated stable stock ROM.
3) I didn't have a ROM on it. I was just trying to root stock. Seems like I'm pretty close once I find that ROM.
Thanks y'all! Between your answers I think I have enough to go on. Feel free to point me to your preferred stable ROM. I'm content with stock but it would be nice to have Tiranium BU.
Click to expand...
Click to collapse
Right now our most stable stock ROM is our rooted stock ROM
http://forum.xda-developers.com/showthread.php?t=2287811
We currently have 2 very able recognized devs working on CyanogenMod. You can expect something new in the near future but until then what I've showed you is the best.
Have any problems just come back to the thread
Success!
abrahammmmmmm_ said:
Right now our most stable stock ROM is our rooted stock ROM
http://forum.xda-developers.com/showthread.php?t=2287811
We currently have 2 very able recognized devs working on CyanogenMod. You can expect something new in the near future but until then what I've showed you is the best.
Have any problems just come back to the thread
Click to expand...
Click to collapse
Thanks guys I know I always like to know when something I said was successful in helping someone. I just wanted yall to know after sideloading the most recent Odexed ROM then pushing it to memory after it wouldn't boot I succeeded after taking abrahammmmmm's advice of flashing the boot.img from HBOOT. After a longer boot than I'm used to I was able to get into my phone again. I wasn't able to use my TitaniumBU to restore but that just meant I had to spend a few minutes selecting apps to install.. And restoring a data backup for the only important app that doesn't keep the primary data off the phone.
Thanks again!
tl;dr Flashing the Odexed ROM boot.img fixed my issues. Thx!
bnjo said:
Thanks guys I know I always like to know when something I said was successful in helping someone. I just wanted yall to know after sideloading the most recent Odexed ROM then pushing it to memory after it wouldn't boot I succeeded after taking abrahammmmmm's advice of flashing the boot.img from HBOOT. After a longer boot than I'm used to I was able to get into my phone again. I wasn't able to use my TitaniumBU to restore but that just meant I had to spend a few minutes selecting apps to install.. And restoring a data backup for the only important app that doesn't keep the primary data off the phone.
Thanks again!
tl;dr Flashing the Odexed ROM boot.img fixed my issues. Thx!
Click to expand...
Click to collapse
Great! glad to hear I could help. Yes it's always nice knowing when something I've said has helped someone in any way
bnjo said:
Thanks guys I know I always like to know when something I said was successful in helping someone. I just wanted yall to know after sideloading the most recent Odexed ROM then pushing it to memory after it wouldn't boot I succeeded after taking abrahammmmmm's advice of flashing the boot.img from HBOOT. After a longer boot than I'm used to I was able to get into my phone again. I wasn't able to use my TitaniumBU to restore but that just meant I had to spend a few minutes selecting apps to install.. And restoring a data backup for the only important app that doesn't keep the primary data off the phone.
Thanks again!
tl;dr Flashing the Odexed ROM boot.img fixed my issues. Thx!
Click to expand...
Click to collapse
i think what happened, when you typed in "fastboot flash boot recovery.img" is this
boot, is also known as kernel in aosp and rom building terms, because if you look inside a rom.zip, you will see that the kernel is the boot.img
so what happened is you flashed a recovery as kernel, and duh it wont boot cause if the kernel doesnt work, the os doesnt either
so what YOU did is you simply reflashed the stock kernel, usually after changing a kernel, it takes a while to boot cause...well you get it right?
the kernel is what android is based off of, kind of like ubuntu, its a linux os based on the original linux kernel.
russian392 said:
usually after changing a kernel, it takes a while to boot cause...well you get it right?
Click to expand...
Click to collapse
Yes I get it.
russian392 said:
i think what happened, when you typed in "fastboot flash boot recovery.img" is this
boot, is also known as kernel in aosp and rom building terms, because if you look inside a rom.zip, you will see that the kernel is the boot.img
so what happened is you flashed a recovery as kernel, and duh it wont boot cause if the kernel doesnt work, the os doesnt either
so what YOU did is you simply reflashed the stock kernel, usually after changing a kernel, it takes a while to boot cause...well you get it right?
the kernel is what android is based off of, kind of like ubuntu, its a linux os based on the original linux kernel.
Click to expand...
Click to collapse
That's what I thought happened. If I had stopped to read the help on fastboot before running "fastboot flash boot recovery.img" I wouldn't have made that mistake because I would have seen I wanted to flash recovery. One thing I *did not* know, which I'm glad to know, was that the boot.img contains the kernal. I was thinking Android was more similar to IBM style PCs than it is and therefore the boot.img was analogous to a bootloader like grub or lilo.
So the one thing I don't get is how is partitioning done? I take it Androids have some reserved partition for boot and the boot.img takes care of all system partitioning and mounts /sdcard/ for everything else. i.e. userland; appdata, media, and files. Am I guessing correctly?
bnjo said:
So the one thing I don't get is how is partitioning done? I take it Androids have some reserved partition for boot and the boot.img takes care of all system partitioning and mounts /sdcard/ for everything else. i.e. userland; appdata, media, and files. Am I guessing correctly?
Click to expand...
Click to collapse
in a nutshell yes, the boot.img uses the fstab
btw 10 posts you'll be "verified"
So the one thing I don't get is how is partitioning done? I take it Androids have some reserved partition for boot and the boot.img takes care of all system partitioning and mounts /sdcard/ for everything else. i.e. userland; appdata, media, and files. Am I guessing correctly?
Click to expand...
Click to collapse
Yep that's correct.
The name correlation is booting up requires kernel there for kernel is called beet.IMG
Thing about custom kernels, they aren't like that and simply contain modded files and pretty much an in packaged kernel.
Sent from my HTC first using xda app-developers app
stock recovery
please can anyone send me the stock recovery.img
when i try to get it from RUU it says archive is corrupted
astrit1995 said:
please can anyone send me the stock recovery.img
when i try to get it from RUU it says archive is corrupted
Click to expand...
Click to collapse
here:
http://androidfiles.org/getdownload.php?file=MystUL/Stock_Roms/stockrecovery.img
if you help, press thanks!!
Serupo said:
here:
http://androidfiles.org/getdownload.php?file=MystUL/Stock_Roms/stockrecovery.img
if you help, press thanks!!
Click to expand...
Click to collapse
Thank you for your help,i solved my problem yesterday but i think im gona need this sometime...
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
hi guys! I'm new at this forum, so if i'm doing something wrong about rules and regulation, even if i've read them, correct me please! However, i just bough an At&T Atrix HD with stock 4.1.1 and i wanted to install a CM11; i obtained root privileges and unlocked the bootloader, and when i try to flash the clockwork recovery, apparently everything goes fine in fact i get no errors, but when i turn off the device and try to reboot in recovery it displays the "dead" droid with a red explanation mark. I've read in the cyanogen wiki that some firmwares during the reboot overwrite the custom recovery, is this the case? Which is the command or the procedure to reboot the cell in recovery then?
PS: I flash it through the command line by the PC, i got OSx and i tried with the clockwork posted in cyanogen wiki and the one posted here http://forum.xda-developers.com/showthread.php?t=2421418
Hi, first of all, did you installed the recovery with: fastboot flash recovery recovery.img right??
If you did so, you just need to turn off your phone, hold volume up button and power button and wait until it enters to recovery mode. From there you can flash a new ROM if you have it on your SD card or internal storage.
sliker90 said:
hi guys! I'm new at this forum, so if i'm doing something wrong about rules and regulation, even if i've read them, correct me please! However, i just bough an At&T Atrix HD with stock 4.1.1 and i wanted to install a CM11; i obtained root privileges and unlocked the bootloader, and when i try to flash the clockwork recovery, apparently everything goes fine in fact i get no errors, but when i turn off the device and try to reboot in recovery it displays the "dead" droid with a red explanation mark. I've read in the cyanogen wiki that some firmwares during the reboot overwrite the custom recovery, is this the case? Which is the command or the procedure to reboot the cell in recovery then?
PS: I flash it through the command line by the PC, i got OSx and i tried with the clockwork posted in cyanogen wiki and the one posted here http://forum.xda-developers.com/showthread.php?t=2421418
Click to expand...
Click to collapse
1. You're rooted so go to /system/etc and rename "install-recovery.sh" to "install-recovery.sh.bak"
2. Use Myth Tools to flash recovery (CWM or PhizTouch is included in the tool)
3. Check and Test
thanks to both of you guys!! i've solved with the solution in the second post, just deleting the "install-recovery.sh" script, i was going crazy!! i hope this post will help someone else!
PS: i don't understand why they do not put these solutions in the first posts in important threads like that one i've linked....
devilsking said:
1. You're rooted so go to /system/etc and rename "install-recovery.sh" to "install-recovery.sh.bak"
2. Use Myth Tools to flash recovery (CWM or PhizTouch is included in the tool)
3. Check and Test
Click to expand...
Click to collapse
I thought mythtools removed the .sh file by itself?
jaweinre said:
I thought mythtools removed the .sh file by itself?
Click to expand...
Click to collapse
Nope. You need to do it manually.
I tried to put that function into Myth Tools but it's impossible to do it via adb commands if the kernel is not enabled "insecure".
That's why I put a guide line in Myth Tools to remind user rename that file manually before flashing recovery.
devilsking said:
Nope. You need to do it manually.
I tried to put that function into Myth Tools but it's impossible to do it via adb commands if the kernel is not enabled "insecure".
That's why I put a guide line in Myth Tools to remind user rename that file manually before flashing recovery.
Click to expand...
Click to collapse
Not necessarily. You don't HAVE to rename that file before flashing. The newer CWM's detect that file and will fix it for you. All you gotta do is enter recovery and exit it through the menu, it'll prompt about the file, and say yes to it. Problem solved. It's what I do along with flashing a root zip with every stock flash I do; haven't had a problem yet.
"Enter and exit CWM" is a lot easier to describe than renaming or deleting a file on the /system partition...less error prone too.
skeevydude said:
Not necessarily. You don't HAVE to rename that file before flashing. The newer CWM's detect that file and will fix it for you. All you gotta do is enter recovery and exit it through the menu, it'll prompt about the file, and say yes to it. Problem solved. It's what I do along with flashing a root zip with every stock flash I do; haven't had a problem yet.
"Enter and exit CWM" is a lot easier to describe than renaming or deleting a file on the /system partition...less error prone too.
Click to expand...
Click to collapse
We are 2, never had problems
Im not an expert but have tried almost everything i could find on the web relating to my issue.
Sucessefully rooted with motochopper
Bootloader unlocked by motopocalypse
Now when it comes to entering recovery mode through Rom Manager or GooManager i always end up with the dead android.
Even device update also failed and ends up the same way.
I have already deleted install-recovery.sh but to no avail.
I want to install SlimKat on my device, only thing in my way is a Dead Android whenever i try to enter recover mod. PLEASE HELP.
Motorola Atrix HD
98.4.20.MB886.ATT.en.US
Android 4.1.1
andrewyp said:
Im not an expert but have tried almost everything i could find on the web relating to my issue.
Sucessefully rooted with motochopper
Bootloader unlocked by motopocalypse
Now when it comes to entering recovery mode through Rom Manager or GooManager i always end up with the dead android.
Even device update also failed and ends up the same way.
I have already deleted install-recovery.sh but to no avail.
I want to install SlimKat on my device, only thing in my way is a Dead Android whenever i try to enter recover mod. PLEASE HELP.
Motorola Atrix HD
98.4.20.MB886.ATT.en.US
Android 4.1.1
Click to expand...
Click to collapse
Do you have a custom recovery already installed? Which one? If you don't, remember that in order to flash a new ROM, you need to install a custom recovery.
mauchito said:
Do you have a custom recovery already installed? Which one? If you don't, remember that in order to flash a new ROM, you need to install a custom recovery.
Click to expand...
Click to collapse
Guess i missed this. I will try to do that and update you. Incase you have any guide to direct me too please do so, otherwise i will try to figure it out. Thanks.
andrewyp said:
Guess i missed this. I will try to do that and update you. Incase you have any guide to direct me too please do so, otherwise i will try to figure it out. Thanks.
Click to expand...
Click to collapse
Sure, buddy.
You need to download a custom recovery, this is the option in Android that lets you erase all content in the device and do other things. With a custom recovery you can do even more things, like install .zip archives or ROMs, erase partitions, dalvik cache, etc, etc, a lot of things.
I personally use this one: http://forum.xda-developers.com/showthread.php?t=2552622
Since you are already rooted, I think that you are familiar with fastboot. In order to flash a custom recovery, you need to do this:
1. Download the custom recovery
2. If it's in a .zip, extract the archive so you have one *.img archive.
3. Then, copy that file to the folder where you have the fastboot.exe archive.
4. Open Windows command console and change the directory to the one where you have the files.
5. Turn off your device, then press volume down key and power key. Hold until you see a black screen with white letters. Connect via USB to your computer.
6. Run the following command in the command console of Windows:
fastboot flash recovery recovery.img
Where "recovery.img" is the name of your custom recovery archive, for example, "philz_touch_6.22.7.img"
7. Wait about 6 seconds and in the console you should see something like "done", I don't remember exactly what does it says.
8. You are good to go. Turn off your device. Then press the volume up key and power button. Hold until you see the custom recovery interface.
After this point, you can flash the custom ROM of your preference.
In the Philz link above, it goes to our thread that links to the main one, from there, download the unified moto-msm8960 one labeled for xt925/xt926. Last time I checked it was more up to date than the native mb886 one (not surprising since our CM repo is gone).