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.
Related
DJ Steve ported CWM 4.0.1.4 with the release of 507.
Requirements:
Stock 5xx based rom [Honeystreak is not supported!]
Ability to enter fastboot mode: Fastboot+ADB.zip
Battery with 60% or greater charge
Basic understanding of the command line
Install Instructions:
Download recovery.img
flash the recovery with "fastboot flash recovery recovery.img"
Finished
Credits:
DJ_Steve for porting it
Koush for creating clockwork mod
I take no credit beyond this basic guide
Notice:
The Streak 7 with HC might now detect the driver properly, if it doesnt you must force install it using the "Android ADB Interface" from the list of available drivers
Will not work on 2.2.x, you must use CWM 3.0 for that.
Do not attempt to wipe data from within CWM, it will likely case a boot loop afterwards.
Thank you!!
Can I just push this recovery to my recovery partition within 3.2?
Im having issues having my PC at work recognize the fastboot device, and installing the drivers.
I am on xp..
TIA!
'error: cannot load 'recovery.img'
I got fastboot going fine, commands like 'fastboot reboot' are working.
However just above when I use your line to flash recovery, any ideas on what it might be!?
Uploaded new version of fastboot+adb.zip hopefully it has the correct IDs so you dont have to force install it.
Are you sure you downloaded the image correctly, and did you name it correctly when using fastboot
Yeah I was making a repeated typo when pointing fastboot to the recovery but its all working now, thanks a lot.
Clockwork mod (cool blue writing) and rooted all within a few days, good work and thanks to all involved.
FWIW I tried this on the T-MO stock 2.2.2 ROM. The install went fine, I copied S7-4.0.1.4.img to recovery.img and ran the fastboot command with no problems.
I power up the Dell Streak 7 while holding power and the up volume key, and get the menu as expected. I Select "Software Upgrade via update.pkg on SD Card", and the message "Booting recovery kernel image" is displayed.
At this point the machine seems to be frozen. I can reset with a paper clip, and reboot the machine into 2.2.2 just fine, but if I cannot resolve why it does not show the clockwordmod menu, then I guess it is back to NVFLASH.
So what am I doing wrong? do I need an SD card in the device with an update.pkg on the card? Or is there something else?
Oh that was a strong possibility.
CWM 4.0 uses the 507 kernel as a base. 507 will not boot without updating the bootloaders.
So that means CWM 4.0 wouldnt be able to boot unless you had 50x installed.
TheManii said:
Oh that was a strong possibility.
CWM 4.0 uses the 507 kernel as a base. 507 will not boot without updating the bootloaders.
So that means CWM 4.0 wouldnt be able to boot unless you had 50x installed.
Click to expand...
Click to collapse
Probably a good idea then to remove that "Assumed to work on 2.2.2" phrase then from your first append.
So I guess it is NVFLASH time ... Or could I somehow flash back only the original recovery.img using fastboot somehow?
Post updated, i needed someone to actually confirm that it didnt work as i dont have access to a s7
dblml320 said:
Probably a good idea then to remove that "Assumed to work on 2.2.2" phrase then from your first append.
So I guess it is NVFLASH time ... Or could I somehow flash back only the original recovery.img using fastboot somehow?
Click to expand...
Click to collapse
I posted over at TabletRoms yesterday that the new recovery did not work with Froyo 2.2.2.
To answer your question, all you have to do is fastboot flash the old CWM recovery, version 3xx something I think it is.
"waiting for device " and nothing happen !!! what should i do? i can not install driver using files in : Fastboot+ADB\Win32\Streak 5+Streak 7+Venue\Win7 !
cdzo72 said:
I posted over at TabletRoms yesterday that the new recovery did not work with Froyo 2.2.2.
To answer your question, all you have to do is fastboot flash the old CWM recovery, version 3xx something I think it is.
Click to expand...
Click to collapse
Like he said if you flashed it on a s7 that's still on 2.2.x just reflash with the CWM 3.0 one and that one will work fine on 2.2.x
Is there another way to root stock 3.2?
I am getting this error in fastboot...
"Flashing StorMgr partition recovery
Read after write verify partition recovery"
Not the stock one, as no other rooting tools work on it.
Ways to get around it include: using a pre-rooted rom or using a custom rom (which are normally pre-rooted)
Something may be wrong with your device/install if that is coming up. Or possibly your download was bad, try re-downloading it.
I tried re-downloading didn't work, I have stock rom, I don't think I can install a custom or pre-rooted rom without installing CWM?
You can with nvflash, as honeystreak is ment to be installed with nvflash then updated with the bundled CWM, which is prerooted
Whichever method you decide is up to you, as I cannot formally recommend that one method is better then the other.
thesmacker11 said:
Is there another way to root stock 3.2?
I am getting this error in fastboot...
"Flashing StorMgr partition recovery
Read after write verify partition recovery"
Click to expand...
Click to collapse
Well just as an update I tried this on a windows xp, windows 7 32bit, windows 7 64bit computer, and redownloaded that file each time and it still does the same thing on my device.
It's likely your device itself that's the issue then, I cant be more specific as I dont own a S7
I'm not sure if I should be asking questions here or over in another forum. Figure I'll start here...
I was sorely missing app2sd in honeycomb so went to use and install Link2SD figuring I'd use that. But it doesn't seem to see the second partition I've made on my SDHC card. I can mount the card on Mac OS and Linux and both mount the two partitions on the card so I feel pretty sure I formatted the card correctly. I saw some comment about a change in the way CW mounts things and it causing troubles in the Link2SD thread but I don't understand enough about the magic of Android and how it mounts discs, although I know it had Linux roots, so the comments in that thread weren't clear to me what I can do to get Link2SD working or for that matter even start to gather info to try to figure out what's wrong. Can anyone help me out or point me to a thread that can get me started in figuring out what's going wrong?
Sent from my HTC Flyer P512 using Tapatalk
ok so i installed the drivers for fastboot and i can enter fast boot , but how can i push the file? soory im a newb with the streak.
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
im wanting to flash the Eclipse 1.0 ROM that is out but im currently still on the initial version that was on the phone at release. i have heard that taking the OTA when rooted can cause boot loops and that i need to OTA fist before flashing Eclipse. what are the steps i need to take in order to safky take the OTA?
also, are titanium backups working so i can load all my apps and data once i get onto eclipse? i thought i saw something about them not working a while back and have not been keeping up with if this has been sorted out?
yamaha83 said:
im wanting to flash the Eclipse 1.0 ROM that is out but im currently still on the initial version that was on the phone at release. i have heard that taking the OTA when rooted can cause boot loops and that i need to OTA fist before flashing Eclipse. what are the steps i need to take in order to safky take the OTA?
also, are titanium backups working so i can load all my apps and data once i get onto eclipse? i thought i saw something about them not working a while back and have not been keeping up with if this has been sorted out?
Click to expand...
Click to collapse
download and install the newest SS that was just released. then go to your stock slot. uninstall SS from the SS app. Then flash stock recovery and system (assuming you didn't flash your baseband as well, if you did then flash the old baseband back on there). then either install pwnmymoto without running, take ota, then check to confirm you have root. OR take ota then root with rockmymoto. then follow instructions to instlal SS on rootzwiki. then follow instructions for the rom.
TIBU works. (not sure for the eclipse rom, just post over there on that thread that question, i haven't run it yet so idk but i would presume that it will since it is based off of the original FW for the phone and not source.) I typically install the apps i had myself from the play store then just reinstall data with TiBu. This is ebcause I have ran into problems installing apps from tibu personally but it was most likely my own error. I never have a problem otherwise, so i just install my own apps. Sometimes google or something does it for me as well so i only instlal a few root apps taht i already saved the apks for so i just move the folder to my phone and install them. Once done with all of that i go and put my data back in with tibu.
jayboyyyy said:
download and install the newest SS that was just released. then go to your stock slot. uninstall SS from the SS app. Then flash stock recovery and system (assuming you didn't flash your baseband as well, if you did then flash the old baseband back on there). then either install pwnmymoto without running, take ota, then check to confirm you have root. OR take ota then root with rockmymoto. then follow instructions to instlal SS on rootzwiki. then follow instructions for the rom.
TIBU works. (not sure for the eclipse rom, just post over there on that thread that question, i haven't run it yet so idk but i would presume that it will since it is based off of the original FW for the phone and not source.) I typically install the apps i had myself from the play store then just reinstall data with TiBu. This is ebcause I have ran into problems installing apps from tibu personally but it was most likely my own error. I never have a problem otherwise, so i just install my own apps. Sometimes google or something does it for me as well so i only instlal a few root apps taht i already saved the apks for so i just move the folder to my phone and install them. Once done with all of that i go and put my data back in with tibu.
Click to expand...
Click to collapse
ok so within the safestrap app i click uninstall recovery, i assume thats what you mean by uninstall safestrap from within the app? after that how do i install the stock recovery and system?
yamaha83 said:
ok so within the safestrap app i click uninstall recovery, i assume thats what you mean by uninstall safestrap from within the app? after that how do i install the stock recovery and system?
Click to expand...
Click to collapse
hmmmm. you go and learn how to use fastboot is how you do it lol. you can also just rsd lite if you don't care about keeping your data. i just posted some general instructions that will help you with fastboot.
http://forum.xda-developers.com/showthread.php?t=2525495&page=6
also , if you don't want to install the sdk tools you can just go download the motofastboot file from here, and run that
http://forum.xda-developers.com/showthread.php?t=2489249
jayboyyyy said:
hmmmm. you go and learn how to use fastboot is how you do it lol. you can also just rsd lite if you don't care about keeping your data. i just posted some general instructions that will help you with fastboot.
http://forum.xda-developers.com/showthread.php?t=2525495&page=6
also , if you don't want to install the sdk tools you can just go download the motofastboot file from here, and run that
http://forum.xda-developers.com/showthread.php?t=2489249
Click to expand...
Click to collapse
i may just use RSDLITE... its been a long time since I had to use fastboot dont really have the time to mess around with it. hmmmmmm
yamaha83 said:
i may just use RSDLITE... its been a long time since I had to use fastboot dont really have the time to mess around with it. hmmmmmm
Click to expand...
Click to collapse
its extremely simple in reality. download that fastboot file from that link. put it in a a folder on your c drive (for instance "fastboot") download the FW for your hone. unzip. put the system and recovery img in the fastboot file you created. then open cmd. type "cd c:/fastboot" THEn plug phone into computer, the reboot phone into fastboot mode with power button and volume down button held for like 3 secs. then run commands in fastboot, fastboot flash recovery recovery.img
fastboot flasht system system.img
fastboot reboot
and your done.
or go use rsd light and remove all of the code from the fastboot commands except for the flash system and flash recovery (the code in the xml file).
jayboyyyy said:
its extremely simple in reality. download that fastboot file from that link. put it in a a folder on your c drive (for instance "fastboot") download the FW for your hone. unzip. put the system and recovery img in the fastboot file you created. then open cmd. type "cd c:/fastboot" THEn plug phone into computer, the reboot phone into fastboot mode with power button and volume down button held for like 3 secs. then run commands in fastboot, fastboot flash recovery recovery.img
fastboot flasht system system.img
fastboot reboot
and your done.
or go use rsd light and remove all of the code from the fastboot commands except for the flash system and flash recovery (the code in the xml file).
Click to expand...
Click to collapse
ah thank you!! that was enough of a refresher to get me going! thanks a lot!
yamaha83 said:
ah thank you!! that was enough of a refresher to get me going! thanks a lot!
Click to expand...
Click to collapse
np. i had to go refresh on my fastboot stuff when i first got the phone because i hadn't touched phone stuff for over a year.
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...
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).