Related
I tried to root again even though I have root. I dont see the ninja but I do see the Superuser Permission icon in the app drawer and have granted a few apps su priveleges. I tried to reflash clockwork it in rom mananger and nothing. How can I get clockwork back?
I just got it back, these are the steps I took although I have no idea which order is correct or why this happened to me.
1. Rom manager - fixed permissions(first I had to force stop, clear data in manage applications as I was getting an error)
2. Rom manager - web connected
3. Rom manager - flashed clockwork recovery like 3 times in a row
4. DroidxBootstrapper - bootstrap recovery
5. DroidxBootstrapper - reboot recovery
Had to do this after I installed a different rom. Is this normal to do after every rom?
I don't think this is normal, what ROM was it?
Sent from my DROIDX using XDA App
Happened after zapx and then after rubix. First time I experienced this with rubix, so I'm thinking its zapx related or even ota 2.2 sbf related(Since I had to use this last night.) Not sure.
all you had to do was open the bootstrapper app and bootstrap recovery. these ROMs format system thus ridding of everything that was in there prior. so you have to bootstrap every time you flash a ROM.
Hello all,
I recently attempted to go from my stock ROM (HTC-Sense 2.2, stock) to something a little more modern (CM7.0.3).
I attempted to do this after rooting my phone (confirmed it worked) and doing the S-OFF stuff.
Originally I attempted to flash via ROM Manager, however this resulted in a boot-loop and upon restoring back to my pre-MOD image I had a broken version of SENSE (believe this is due to improper "wiping" of the various data/cache areas).
I had to manually flash CM7 via hBoot into CWM (hboot>recovery, CWM update.zip).
This resulted in what appears to be a full install of CM7 (7.0.3), however I am now left without any gApps (including Market).
I understand that due to legal requirements, CM does not bundle the gApps but they are available via download/flashing.
I expected this would mean simply downloading the gApp*.zip, uploading to the root of my SD card, and then re-doing the hBoot>CWM update.
This does not appear to function however as hBoot > Recovery does not load CWM (counter to what I recall happening previously).
I can get into hBoot (either via PWR+Vol Down, or PWR + reboot into Recovery within CM7), but get no further then the Recovery menu (inside of hBoot).
Specifically, I see the following (within hBoot > Recovery):
Bootloader
Reboot
Reboot Bootloader
Power Down
Selecting "Bootloader" takes me back to the main hBoot screen (detailed below).
Selecting "Reboot" takes me back into CM7.
Selecting "Reboot Bootloader" reloads the above detailed hBoot selections.
Selecting "Power Down" shuts the device off.
Here is what I have available on the primary hBoot screen:
Fastboot
Recovery
Factory Reset
Simlock
Image CRC
Selecting "Fastboot" attempts to locate and do something with "PC10IMG.*" (including .zip).
Selecting "Recovery" leads to further selections described above.
Selecting "Factory Reset" returns me to the same hBoot screen (seemingly without doing anything).
I have not attempted "Simlock" or "Image CRC".
Here is some further output from hBoot (Fastboot > Bootloader):
SD Checking...
Loading...[PC10DIAG.zip]
No image!
Loading...[PC10DIAG.nbh]
No image or wrong image!
Loading...[PC10IMG.zip]
No image!
Loading...[PC10IMG.nbh]
No image or wrong image!
Then it returns to the hBoot menus.
I understand from past research on this topic, that some users observe a terminal option somewhere within hBoot (which is not present in my case).
# Speculation on the root cause of this issue
I believe the issue is that hBoot does not know where/how to load CWM (wrong version, missing link, etc).
Thus why it keeps looping back instead of doing "something useful" like loading CWM.
I offer the following observed behavior to support this.
When I load ROM Manager (4.2.0.2) within CM7, I "Flash ClockworkMOD Recovery" (despite the "latest" and "current" versions matching (3.0.2.4)), which results in no change in version.
When I attempt to "Download ROM", I get prompted to "upgrade ROM Manager to the latest version", which then leads to a Force Close error.
I would really like to "close the loop" on this ROM upgrade for my phone, as I like the look and feel of CM7.
Without the gApps however, I am unable to access the Market and reload the APPs I had prior to the upgrade (EG: Gmail, Blizzard Mobile Authenticator, ROM Manager, etc.)
Any (constructive) tips or suggestions would be greatly appreciated.
# Phone info (let me know if you require more then the below)
Phone: HTC Desire Z (Vision) (*not* G2)
Rooted: Yes
S-off: Yes
MOD: Cyanogenmod 7.0.3
ROM Manager: 4.2.0.2
CWM Recovery: 3.0.2.4
hBOOT: 0.85.0005
gApps: 20110307 (attempted), 20110613 (attempted)
Thank you.
Download the gapps from rom manager and flash it. You don't flash from bootloader if doing it manually, you "install zip from sd card" after you boot into recovery.
Sent from my HTC Vision using XDA Premium App
Spastic909 said:
Download the gapps from rom manager and flash it. You don't flash from bootloader if doing it manually, you "install zip from sd card" after you boot into recovery.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Hello Spastic909,
Thank you for the above response to the thread.
Understood regarding your suggestion, however it is not an option for me at this time.
I have attempted to re-flash CWM with the latest version within ROM Manager.
This did not result in a version change (v3.0.4.2) even though the device "appeared" to check and did not report any errors.
I say "appeared" as I am unconvinced the software actually is making a full connection (using my home wifi, which is confirmed to work).
I also note further unusual behavior within ROM Manager when I attempt to "Download ROM".
I get a prompt indicating I need to upgrade the ROM Manager application (You must upgrade your ROM Manager to the latest version!)
When I click on OK, I recieve a force close error (proces com.koushikdutta.rommanager has stopped unexpectedly).
This is coming from the version of ROM Manager (v4.2.0.2) that comes packaged with CM7 (7.0.3).
I do recall observing reports of this sort of behaviour elsewhere from CM7 users post installation.
With regards to rebooting into recovery mode, I have attempted this previously, which dumps me into the hBoot menu system.
I do note a "Recovery" option within hBoot, but the association with CWM appears to have been severed.
As a result of selecting "Recovery", I get dumped back to the hBoot menus with the only option seeming to work is "Reboot" which takes me back into CM7.
I have observed some users reporting a "terminal" option within hBoot, but this is not present in my case.
In summary, I appear to be in a difficult position.
I am unable to enter CWM via ROM Manager or hBoot.
I do not have the ability to flash the gApps which would give me the Android Market.
Without this, I am unaware of a method to upgrade ROM Manager & CWM to the latest release.
In addition, I am un-aware of a method to revert back to my last restore point, given the "Recovery loop" I described above.
Have you tried to uninstall and then reinstall rom manager? Have you tried to adb into recovery?
Sent from my HTC Vision using XDA Premium App
Spastic909 said:
Have you tried to uninstall and then reinstall rom manager? Have you tried to adb into recovery?
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Hello Spastic909,
Thank you for the above response to this thread.
I have not attempted to un-install/re-install ROM Manager at this time.
Specifically as I am unaware as to how I might source this APP to perform the re-install phase.
Upon examining the instance of CM7 installed on my device, I do note the ability to manipulate aspects of ROM Manager (Settings > Applications > Manage applications > All > ROM Manager).
However, I do not observe an option to "Remove" or "Uninstall".
What I do observe are as follows:
Force Stop
Cancel (greyed out)
Clear data
Move to SD card
Clear cache (greyed out)
Clear defaults (greyed out)
I am option to suggested options on this point.
With regards to leverage adb to access recovery, I have attempted this, however I only get as far as hBoot.
hBoot does offer a "Recovery" option, however it does not actually lead to CWM (or anywhere other then back into the hBoot menu system).
I have attempted to load some versions of recovery.img I found online, but these did not prove useful (hBoot association with Recovery corrupt?)
Thank you for your assistance thus far.
So with adb you ran "adb reboot recovery"? Install titanium backup, remove rom manager, reinstall from market. See if that fixes it
Sent from my HTC Vision using XDA Premium App
Or download the new market in the apps&themes section. Then install all the google apps u want
Sent from my HTC Vision using XDA Premium App
Spastic909 said:
So with adb you ran "adb reboot recovery"? Install titanium backup, remove rom manager, reinstall from market. See if that fixes it
Or download the new market in the apps&themes section. Then install all the google apps u want
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Hello Spastic909,
First off, thank you for your continued suggestions regarding these issues.
I did indeed use 'adb reboot recovery', however this also leads to the hBoot menus described above (and no further).
On your suggestion, I sourced/installed Ti-Backup and this has permitted some progress on the matter.
Specifically I was able to force un-install ROM Manager via the Ti-Backup APP.
Once this was done I attempted to boot into recovery via adb (which lead to hBoot issue).
I sourced the latest ROM Manager APK from the dev website, and loaded this via adb (adb install $BLAH) and this also seemed to make some progress.
My new install of ROM Manager is at an increased version (4.3.3.0).
I do not note a version change for CWM (3.0.2.4).
I do note more ROM manager features are functional (ability to list/download new ROMs including the gApps & make selections within "All CWM Recoveries", both of which was not accessable before).
I am unclear on where you indicated to check for the Market APP to install with (apps & themes is located where?)
I did find a Market APK here in the forums, and was able to load to my phone via adb.
However, this version (2.2.6) failed to start (displays "loading" very briefly as in 1 second, and then returns to home screen).
As such, I was unable to leverage this APP to source additional pieces.
http://forum.xda-developers.com/showthread.php?t=869964
It strikes me that the large issue (and perhaps the final one) is this hBoot menu looping problem.
For some reason unknown to myself, the "Recovery" option is failing to associate with CWM (or anything else that I can tell).
If this part of the problem can be resolved, I feel confident the rest of the pieces will fall into place.
Is this perhaps a case of a partially corrupted hBoot?
I did not personally make any changes to hBoot since when I rooted my device.
I ran the unit for some time post-rooting using the stock HTC Sense (Froyo 2.2) ROM with out issue.
I also was able to flash CM7 using the hBoot Recovery to access the instance of ROM Manager / CWM (current) I had in the Sense install (pre-CM7).
Now that you have ROM Manager installed you should be able to download and install the google apps through it. This will give the Android Market. Within ROM Manager go to Download ROM -> Google Apps -> 20110613 Universal -> Download. ROM Manager should automatically start downloading the apps and then it'll reboot and install it through recovery. Once the phone has rebooted, you should have the Market installed.
But, if your phone is having issues booting into recovery then the Google Apps may not install at all. Just a matter of curiosity, which/who's steps did you use to root your phone and put ClockWorkMod on it? If you think your HBOOT has become corrupted, then I think you need to flash the RUU for your phone. By doing that it should return your phone to complete stock. Mind you this is a suggestion by basically a noob so if someone who is more seasoned agrees with me then start researching. You can start with the link below.
[GUIDE] Downgrade your Desire-Z from 1.72 to 1.34 (and get root and S-OFF)
Hi
I am currently running the latest CM 7 nightly build. However, I have issues with GPS which doesn't find any satellites.
In order to re-flash the radio (which I have tried previously), I need to use ClockWorkMod Recovery 2.5.x. Currently I have 3.2.0.0.
I have previously used ROM Manager to do this, but now when I install 2.5.0.7 through ROM manager and select Reboot to recovery it simply reboots into 3.2.0.0.
I have tried reinstalling ROM Manager from Android Market after complete uninstall. But the same things keeps happening.
Any suggestions?
BR, Martin / mhca
Is a small "bump" allowed...?
I haven't found a solution yet. I have even played around with different ROMs without success. Is it a bug in ROM Manager?
Do I have to first upgrade CWM to 5.0.0.2 and then afterwards try to use ROM Manager to hopefully reboot into CWM 2.5.0.7 ?
Flash this ZIP in your existing CWM3/4/5 setup. Then you can get temporary 2.5.0.7 without touching the ROM Manager app:
http://forum.xda-developers.com/attachment.php?attachmentid=662193&d=1311319218
(It's the same temp 2.5.0.7 which ROM Manager downloads.)
Thanks a ton!
I just realised that this was even written with small text in The Complete Wildfire index, right next to the links to the radio. But somehow I missed that.
Really glad that you gave me a fail-safe method which doesn't require Rom Manager.
Radio didn't flash with CWM - used Android Flasher
Although I got a working CWM 2.5.0.7 with the above-mentioned method, I couldn't properly flash the radio.
I got error message "no space left on device", must likely due to custom partition sizes.
I found out that I could use the Windows app Android Flasher to flash the radio. And now my GPS works
PLEASE USE THE CWM UPDATE BY KOUSH ONLY.. ALSO, PLEASE BE ADVISED THAT CWM VERSION 5.5.0.4 has been reported to have some freeze issues, contact Koush and forward a logcat or provide information so he can resolve. Until then, use an earlier version until all the bugs are gone..... thank you--- oka1 moderator
Today I noticed That Koush Has released CWM 5.5.04 for Our device. So simply You can Download Rom manager from Market and then just install the CWM.
AllCredits go to KOUSH.
Here IS the .img file.
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.5.0.4-tf101.img
Installed fine. Reboot to recovery still doesn't work for me. Still works fine when using the app from the market though. Thanks for the heads up.
Reboot to recovery messed up my tab, so it would only boot into recovery (booting to Android was done manually).
works either manually or via market app reboot to recovery, via ClockworkMod restart the system, is not in recovery
"reboot system now" does not work, reboot into recovery again.
Same to me on my tab. Don't install it yet.
Unable to install either through rom manager
or
Terminal method
Rom manger says it installed it but when I reboot to revocery (via another app)
it's still the old one
Terminal emulator says image not found no matter where I store it or what directory I point to
Seems like I'm missing something.
The linked .img file is a blob file with the SOS partition. It can be flashed through the staging partition. If you extract it or strip out the header, it will be a regular .img file that can be flashed through cwm (with a little work).
I haven't flashed it yet.
Same here, unable to boot android again (recovery loop), is there any way to flash the old one from adb?
Thanks
bug
since i have instal it i can't go out of the recovery when i do restart and it reboot in recovery again
go out by pressing power button + volume down , wait a moment and you can select recovery or boot android os
If you go into advanced there's no option to return.
Wasn't there a bug about installing recovery with Rom Manager that causes constant boots into recovery?
let me look...
EDIT: This may or may not apply, but ...
http://forum.xda-developers.com/showthread.php?t=151963
Official, yes, see here the 5.5.0.4 for tf101, the .img and .zip:
http://download.clockworkmod.com/recoveries/
I should have read more of this thread before flashing. Because now mine does what everyone else is doing. Goes back into the recovery in a loop..
If You have problems return to the older:
http://forum.xda-developers.com/showthread.php?t=1346180
=================
mine flashed fine from rom manager pro on Eos-tf101-5 All menu's seem to work fine, but there is no external SD access only internal. Still can't access recovery from rom manager but that's the same standard issue with the rom.
it support tf101g or not ?
Cant flash a new recovery either.
Tried reflashing rogue and still boot loops into cwm.
Downloaded current cwm from web link above and flashed. Still boot loops into recovery.
Sent from my Transformer TF101 using Tapatalk
I would love to go back to the older one...But my Tab doesnt show the sdcard at all. Only internal memory...weird
Flashing the IMG via NVFLASH broke recovery for me. Installing it through ROM Managers works fine.
I've been running the 10-20130303-Nightly-encore for a while now with no problems. Yesterday I decided to try to use the CyanogenMod update to upgrade to 10.1.2. Did both Ti and CWM backups, then went ahead with the 10.1.2 update. This mostly worked, but several things broke right off the bat.
First, some of my apps either got erased or uninstalled. The icons were there, but tapping on them would bring up a message saying the app was not installed.
Second, as my Nook booted up, it reported several apps have stopped. (Such as gmail, Trillian, etc.) Worse yet, some of my apps wouldn't even run. (RomManager for one!) I attempted to restore some of those apps via Ti. Some of them restored but still didn't run. On a few of them, Ti just got stuck on the "Restoring..." popup.
Third, although my WiFi was connected and apparently working for some apps, other apps reported no network connection. (Namely the Play store!) I did notice that the WiFi icon at the top was always gray, not the normal blue.
After fiddling with it for several hours, I managed to get RomManager back up and reverted back to my previous backup.
So my questions are:
1. What is the correct way to update/upgrade using CyanogenMod's updater?
2. Should I have updated to 10.1.0 first, then 10.1.1, then 10.1.2?
Thanks!
You need to factory reset/clear data (probably need to wipe/format system as well) and install the correct gapps for 10.1 (20130301)
So, are you saying that I should go to the "CyanogenMod updates" settings, select the cm-10.1.2, download it (by taping the button to download), then not install it using the button to install it, but instead download (manually) the correct gapps, move both files to the sdcard root, reboot into recovery, totally wipe/reset the whole tablet, then install cm-10.1.2 and the gapps, and then begin to re-install all of my apps and data?
If so, then I think I fail to see the purpose of the "CyanogenMod updates" settings page.
software_samurai said:
So, are you saying that I should go to the "CyanogenMod updates" settings, select the cm-10.1.2, download it (by taping the button to download), then not install it using the button to install it, but instead download (manually) the correct gapps, move both files to the sdcard root, reboot into recovery, totally wipe/reset the whole tablet, then install cm-10.1.2 and the gapps, and then begin to re-install all of my apps and data?
If so, then I think I fail to see the purpose of the "CyanogenMod updates" settings page.
Click to expand...
Click to collapse
If you have a "CWM based recovery" on internal memory, you should be able to download and install the CWM 10.1.2 using cmupdater. But you may have to manually install the right version of gapps the first time. After that just use the updater. No need to wipe anything if just updating CM10.1 to another CM10.1.
Obviously something when wrong last time and that is why dizzy recommended wiping. Usually that is not necessary.
Sent from my Galaxy Tab 2 using XDA Premium
leapinlar said:
If you have a "CWM based recovery" on internal memory, you should be able to download and install the CWM 10.1.2 using cmupdater. But you may have to manually install the right version of gapps the first time. After that just use the updater. No need to wipe anything if just updating CM10.1 to another CM10.1.
Click to expand...
Click to collapse
Personally I have found the TWRP recovery to work more reliably than CWM. At some point I was having similar issues with the first updates after fresh-flashing my first CM10 nightly, and after switching to TWRP there has been no problems so far. As a bonus, ROMs which use GooManager for updates would also be able to install updates from GooManager automatically. If you only plan to use CM, what leapinlear says should work, too.
Thread targets me exactly, so thank you, thank you all.
Requesting further clarification ; I wish to use cmupdate to latest stable version for my Nook. Regardless of which flavor recovery I use, should I, first flash the appropriate gapps, then run the updater?
This seems to be the logical order if there is a chance that the recovery might get hosed during the update process. But will it work?
If I'm off track here please set me straight!
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Chipsy Chopsy said:
Requesting further clarification ; I wish to use cmupdate to latest stable version for my Nook. Regardless of which flavor recovery I use, should I, first flash the appropriate gapps, then run the updater?
This seems to be the logical order if there is a chance that the recovery might get hosed during the update process. But will it work?
Click to expand...
Click to collapse
The CM Updater should work regardless whether gapps are installed or not — the updater does not need gapps to work.
The first time you install CM, the usual thing is to flash both CM and gapps (some people may decide to not use the Google stuff, so they choose to not flash gapps, but in general almost everybody would/should flash them). If gapps are installed, the CM updater will then preserve the gapps when doing an update, so it is not needed to flash gapps with each update.
I hope the explanation makes things a bit clearer for you