[Q] Unable to load Google Apps - G2 and Desire Z General

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)

Related

CM7 Nexus one install - no powerbutton - sdcard won't mount - what not to do

I just had some fun upgrading my phone to CM7 from CM6. This is my tale of woe. Of course any confirmation of exactly where I went wrong would be much appreciated.
My Nexus One is
FRG83D
CM 6.1.1-N1
ROM manager 2.5.0.9
security on
bootloader locked
Also, my n1's power button is dead so I use the battery pop with power/usb connected method to boot. During the last couple of all nighters, I found out that a Hong Kong company is selling said part on ebay and will send international, so will finally invest I think.
To begin:
I downloaded the update and using rom manager, did a backup and install - all OK. Had a quick look at CM7 and restored CM6.
Then:
Backed up everything again with TI and moved both ROM manager and TI backup to my laptop just in case.
Went back to ROM manager and did the upgrade. This time I didn't select backup (as I already had one) and - here's where I probably went wrong - didn't select clear cache. Perhaps a, "I wonder what this does" moment.
My phone wouldn't reboot past the coloured cross. Using the battery pop method and some help from xda and elsewhere, I found out the vol-down button would get me HBOOT recovery screen and the track ball would get me into fastboot recovery screen. Of course I couldn't do anything here as the power button doesn't work.
I could connect the usb and I'd installed the sdk and fastboot (I tried this on Linux but had too many hassles with the usb driver. Something for next time.) On windows, I remembered to delete the windows usb driver and re-install to one in the sdk directory.
adb devices returned nothing but fastboot devices worked. From fastboot recovery with usb, I tried to fastboot flash recovery, boot, and system using my ROM backup files. I could not - while nobody has stated this explicitly, my reading is that it is probably because my phone is locked (sorry, the error message alludes me at the moment). Could not unlock my phone with fastboot oem unlock to find out as I don't have a power button (welcome to yosarian's world).
I could delete cache, which I did as I thought that my failure to select this option in rom manager install was the cause of the problem.
I rebooted and exalted as the CM7 splash screen appeared...but the boot stopped there.
I found I could now use adb devices while it looped here, but the /scard wasn't mounted and would not using mount /sdcard. I got this error; mount: can't read /etc/fstab: No such file or directory
I this found this thread http://forum.xda-developers.com/showthread.php?t=984688&page=4
I followed jason's instructions and mounted the sdcard OK. I could now see the sdcard in XP Explorer. However, I noted that any .img files I copied to the sdcard using XP Explorer did not show up in an adb shell ls of the sdcard. Conversely, my copies of the system and recovery images using cat /dev/mtd/mtd1 > /sdcard/mtd1.img and cat /dev/mtd/mtd2 > /sdcard/mtd2.img weren't visible in XP Explorer.
I pushed the recovery image from my original rom manager backup. flash_image recovery failed with: header is the same, not flashing recovery. I pushed a copy of recovery-clockwork-2.5 (I remember reading something about 3.0 causing problems). This time it flashed OK.
adb reboot recovery got me back to the recovery screen and I restored CM6. I went to bed.
Will try the upgrade again soon.
It's the claockwork mod. I don't use 3.+ at all anymore. Doubt I'll be flashing any Roms for awhile as I too have a broken power button and don't want to haveto go through all that you went through just to get back to where I was!
Just out of curiousity. How are you flashing w/o using the power button? In recovery you have to use it. No?
you can use the trackball once in clockworkmod recovery. btw my phone froze at the splash screen a few days after i re-installed cm7.0.2.1. the keyboard had gone wonky and i did a rom manager reboot. this time i just did "adb reboot recovery" and restored my full backup. all ok. not sure what the reboot problem is. i'm using rom manager 4.2.0.0 and clockworkmod 2.5.1.0.
i like cm7, power button problems or not.
johnsopaul said:
you can use the trackball once in clockworkmod recovery. btw my phone froze at the splash screen a few days after i re-installed cm7.0.2.1. the keyboard had gone wonky and i did a rom manager reboot. this time i just did "adb reboot recovery" and restored my full backup. all ok. not sure what the reboot problem is. i'm using rom manager 4.2.0.0 and clockworkmod 2.5.1.0.
i like cm7, power button problems or not.
Click to expand...
Click to collapse
try amon ra recovery. Cm 7 requires cwm 3 and up which is causing a lot of problem right now. Good luck.
Sent from my Nexus One using XDA Premium App
will do that now. thanks
Amon RA need the power button to select thingsn
Sent from my Nexus One using XDA Premium App

[REF] related to CM7 of WILDFIRE BUZZ

Hi everyone.
I'm just creating this thread to share any issues everyone is facing with cm7. And maybe getting issues fixed. Just trying so that everyone will share their issues + known solutions if any. Please specify the CM version on what you are talking about... PLS SHARE THE THINGS..
NOTE : The below things doesn't mean that they should be present in your device. It is always better if you don't have those. Just they are the common issues faced by many people.
FAQ's
1. My GPS / Wifi is not working.
A: This is the issue which most of the people are facing. Re-flashing the radio will solve this (cannot assure this since it didn't solve for some people) . If you are going with re-flashing the radio, please make sure that you have enough battery and using recovery 2.x (the one from rom manager is also enough). And flashing the hboot and radio has the potential to brick the phone, suppose if anything goes wrong. So, better to avoid doing these things frequently.
ALTERNATE METHOD (SAFE) : This is working. First install cm7 and then make a nandroid backup of it. Then wipe everything and restore the previous nandroid backup of stock froyo rom (or any rom with working gps) and use gps to capture your location. Then again wipe everything and restore the cm7 backup. Now gps will be working. And once gps on cm7 works, then even after a hard reset it still works. This seems to be an issue only when freshly installing cm7. This is definitely a safe method.
2. USB tethering not working + I can't see usb tethering option on status bar.
A: The status bar of cm7 doesn't has the option for selecting usb tethering (like stock rom). Instead the option is present in Settings/Wireless & Networks/Tethering & Portable hotspot/usb tethering. So, access the option from here. And make sure that your pc has necessary drivers (HTCDriver_2.0.7.17.exe is enough). No need of drivers for linux.
And another important thing is, You should disable USB DEBUGGING to access usb tethering. For doing that go to Settings/Applications/Development/ . The stock htc rom will disable usb debugging automatically when tethering is selected. But on cm7 presently u need to manually disable the debugging option (for usb tethering to work).
3. I can't access MOBILE INTERNET DATA
A: Check whether you have the correct access point or not. Go to Settings/Wireless & Networks/Mobile Networks/Access Point Names/ . If this is the issue make sure to manually add APN by clicking menu and select "New APN". The settings to be told by your service provider. Or if you have the previous working nandroid backups, then u can note the settings from them to be entered in CM7 apn. The APN will be generally configured automatically, and in case if they are not, you need to manually add apn.
4. I can't see the market application.
A: Google apps package is not included in CM7 rom. Make sure u have flashed the "universal google apps package for CM7" from the recovery. It is better to flash the google apps just after flashing the rom (without a reboot gap). The process of flashing google apps is same as the process of flashing a custom rom. And login to your gmail account to access the market.
--Google apps link: gapps-gb-20110613-signed.zip
5. I can't add facebook / twitter account through settings.
A: You need to have those applications installed to add those accounts. Just after opening the market for first time, you will see a MARKET INSTALLER screen to "Choose the apps to install". This includes facebook, gmail, google goggles, google maps, google voice, twitter, youtube and some others. Either install them from this screen or install them later from market to integrate those accounts. And u can synchronize the facebook contacts on doing this.
6. Problem related to Wifi connection
A: Try to change the number of channels under Wifi Advanced settings/Regulatory domain/ .
7. I can't enable BLUETOOTH FTP
Maybe there is no option by default. But you can always enable it with third party apps like "Bluetooth file transfer"(by medieval software) .
8. I can't access root permissions
A: in 99% cases, the su binary will be there in the rom. Incase if you can't access the root permissions due to the absence of su binary, then flash this file from recovery just like flashing any other rom.
su-2.3.6.1-ef-signed.zip
9. Font issue of Google Maps
A: The newer version of google maps is somewhat laggy and has blurred fonts. Try the older version (gmm-android-google version:5.0.0) which has clear font and is more responsive.
**********************Thanks to Cyanogen Mod team for the awesome rom**********************
Nice Post. Haven't had any of those issues myself so far. Good to see some useful information though.
Yep. Not everyone has all the issues. But depends. Thank u
I don't have had any of those issues yet. All of the things you mentioned are working just fine.
mine working great so far..just my youtube videos are black screen..sound is there tho.
Random reboot, wifi dying on full signal.
Openfire ftw lol, no problems what so ever.
Sent from my wildfire using Tapatalk
I have the GPS problem too. I tried reflashing both radios, 19.25 and 20.10 but neither of them worked. Did the backup and restore method you mentioned work properly?
Sent from my HTC Wildfire using XDA App
waywardlistener said:
I have the GPS problem too. I tried reflashing both radios, 19.25 and 20.10 but neither of them worked. Did the backup and restore method you mentioned work properly?
Sent from my HTC Wildfire using XDA App
Click to expand...
Click to collapse
yes. Worked with me really.
If it works when u restore the stock rom, it will also work then on cm7 i think.
Pls post your results if u check
hi guys
i've a problem, i did the s-off method from alpha, i'd install the recovery mode clockwork-3.2.0.0, did the backup, wipe out all, instal from sd card and..........still got my stock version froyo 2.2. what hell???
plus add all the stock apps, the only thing left was the others one that i had installed. so i dont quite get it?
please help me
p.s. foret to tell im trying to install CyanogenMod 7 Nightly Builds
alexctk said:
hi guys
i've a problem, i did the s-off method from alpha, i'd install the recovery mode clockwork-3.2.0.0, did the backup, wipe out all, instal from sd card and..........still got my stock version froyo 2.2. what hell???
plus add all the stock apps, the only thing left was the others one that i had installed. so i dont quite get it?
please help me
p.s. foret to tell im trying to install CyanogenMod 7 Nightly Builds
Click to expand...
Click to collapse
Don't know, but check again ...
You are using recovery 3.x and it is correct one for cm7.
Download link for nightly version here http://download.cyanogenmod.com/?type=nightly&device=buzz
Then boot into custom recovery and select wipe data, wipe cache, wipe dalvik cache, factory reset . Then select "install zip from sdcard". Then "choose zip from sdcard". Then add the downloaded file. Takes around 5min to install. Then install the google apps package linked above. After that, reboot. Will solve i think.
I have a problem with the phone. I am on CM 7 stable. Whenever I receive a phone call, and answer, it first activates speakerphone for a second or two and then goes back to normal. Anybody else have this problem?
Sent from my HTC Wildfire using XDA App
bharatgaddameedi said:
yes. Worked with me really.
If it works when u restore the stock rom, it will also work then on cm7 i think.
Pls post your results if u check
Click to expand...
Click to collapse
For some reason my nandroid backup of the stock rom failed to restore.
Any other ideas?
Sent from my HTC Wildfire using XDA App
good job ! man
how to reflash radio my gps dont work. using clockwork recovery
What cwm you have used for your nandroid back up?
send with my wf s-off thank Alpharevx
waywardlistener said:
For some reason my nandroid backup of the stock rom failed to restore.
Any other ideas?
Click to expand...
Click to collapse
Have had something similar, and in trying to restore it, I tought I almost broke my phone :-o it would only boot up in recovery, very painfull for a moment.
I solved it by flashing the nandroid backup immages manualy with the use of fastboot.
1. Open the nandroid backup folder on your computer and you can see a boot.img, data.img and system.img
2. Copy (only) those three in the same folder where fastboot.exe is stored.
3. Reboot phone into bootloader. Select fastboot and plug the phone in your computer.
4. Open the command line on your computer and browse to the folder where fastboot is. Type "fastboot devices" and hit enter. You should see your device listed now.
5. Type
"fastboot flash system system.img" and hit enter
"fastboot flash userdata data.img" and hit enter
"fastboot flash boot boot.img" and hit enter
Note that every time you time you hit enter, you can follow the proces in the bootloader itself.
6. Type "fastboot reboot" and hit enter
It should work. Make sure you have enough battery and wathever you do, do not interupt the flashing proces.
Good luck with it,
Erwin
waywardlistener said:
For some reason my nandroid backup of the stock rom failed to restore.
Any other ideas?
Click to expand...
Click to collapse
I guess u have changed the folder name of backup folder (which will be normally in date and time). I have also once changed the folder name of that and it said md5 checksum error. But this can be flashed from fastboot flash method.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
While restoring nandroid backup through fastboot process make sure u first delete the things (you can also do these from recovery menu). The commands will be
fastboot erase boot
fastboot erase userdata
fastboot erase cache
fastboot erase dalvik-cache
fastboot erase system
Then use the commands said above by erwinP (can also include cache.img). Keep your img files in the fastboot.exe folder ( = command prompt CD folder).
And recovery version shouldn't be giving issues related to nandroid restore AFAIK.
Sent from my HTC Wildfire using XDA App
i solved my problems by myself, thanks anyway, back to cm7 - best
Fulfen said:
how to reflash radio my gps dont work. using clockwork recovery
Click to expand...
Click to collapse
Go to this thread [REF] [22/06] [MAJOR UPDATE] The Complete Wildfire Index
and download the radio from section 4. Put the zip file on sdcard.
Then you should have clockworkmod 2.x recovery for flashing this. This is because amend scripting is not supported by recovery 3.x and +. So, if you are using CWM 3.x , then you can open rom manager and select "flash recovery" which flashes 2.5.0.7 recovery as a secondary thing on the memory card. Then if you select "Reboot to Recovery" from the rom manager itself, your phone reboots into 2.x recovery for that one time only [Let us call this as secondary recovery]. Now you can flash the Radio file you downloaded. Make sure your battery is enough so as not to interrupt the process. And once you are in 2.x recovery, then select "install zip from sdcard" and then "choose zip from sdcard". Then add your zip file. (NOTE : Donot wipe the data for radio installations, not necessary)
note: For secondary recovery to work, the memory card should be mounted (Although u need it for every recovery flashing).
for me radio re-flashing dont work, or should i flash older 1? thank you.

Going from CWM 2.5.1.2 to 5.0.2 (ClockworkMod)

I notice that the old standard, ClockworkMod 2.5.1.2, is now old news.
I went to install CWM 5.0.2, attempting both methods (flashing directly from CWM 2.5.1.2, also by booting into the PB31IMG.zip). Neither works, when I reboot, I'm back in 2.5.1.2
I searched here, but I don't see anyone having this issue.
Thank you in advance,
RKM
In rom manager, make sure erase recovery is selected. Then try to flash it twice.
Thank you for the reply.
I had found the posts that suggested that prior to my posting, however, I'm *not* using ROM Manager, I'm using both methods of installing correctly, at boot/recovery.
If it does not work from boot/recovery, no amount of settings in ROM manager will help me, unfortunately.
rkmFL said:
Thank you for the reply.
I had found the posts that suggested that prior to my posting, however, I'm *not* using ROM Manager, I'm using both methods of installing correctly, at boot/recovery.
If it does not work from boot/recovery, no amount of settings in ROM manager will help me, unfortunately.
Click to expand...
Click to collapse
Boot to recovery, go to mounts and storage and format recovery. Reboot the phone.
Download this http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip, and put it on your sdcard in no folders. Then boot to hboot, hboot will find the file and prompt to press vol up to install, and then vol up again to reboot.
Or you could do as sugested earlier and download rom manager, go to its settings and check erase recovery before flashing. Then from the main screen select the top option install cwm recovery.
If that dosent work i would flash back to thr stock recovery, and then back to cwm again, or try amon ra recovery then back to cwm.
If that dosent work, ruu and then flash cwm. Note that cwm 2 backups are not compatible with version 5.
@cmlusco - that's the same file I'm using now and it won't take, on *either* HDR6300 Incredible that I've tested it on. I'm still on 0.92 HBOOT and 2.15.00.07.28 RADIO.
During the HBOOT process, it does recognize the PB31IMG.zip, but it rejects it.
It reminds of of the way the phone reacts when it's S-ON. You know, how it rejects custom PB31IMG's until removing the security flag. Despite that, this is a fully S-OFF phone.
The one thing I had not yet done that you mentioned .. I haven't yet tried to "mounts and storage and format recovery" as you suggested. However, there is no option for "Format Recovery". In CWM 2.5.1.2, the Format options include:
Format Boot
Format System
Format Data
Format Cache
Format SDCard
Format SD-Ext
After reading your post, I tried "Format Boot" and "Format System". Neither one of those helped either.
The thing is, I don't think this is a one-off issue, because the exact same thing is happening on both of my DInc's.
rkmFL said:
@cmlusco - that's the same file I'm using now and it won't take, on *either* HDR6300 Incredible that I've tested it on. I'm still on 0.92 HBOOT and 2.15.00.07.28 RADIO.
During the HBOOT process, it does recognize the PB31IMG.zip, but it rejects it.
It reminds of of the way the phone reacts when it's S-ON. You know, how it rejects custom PB31IMG's until removing the security flag. Despite that, this is a fully S-OFF phone.
The one thing I had not yet done that you mentioned .. I haven't yet tried to "mounts and storage and format recovery" as you suggested. However, there is no option for "Format Recovery". In CWM 2.5.1.2, the Format options include:
Format Boot
Format System
Format Data
Format Cache
Format SDCard
Format SD-Ext
After reading your post, I tried "Format Boot" and "Format System". Neither one of those helped either.
The thing is, I don't think this is a one-off issue, because the exact same thing is happening on both of my DInc's.
Click to expand...
Click to collapse
Have you tried reformating your sdcard fat32? The only 2 reasons a PB31IMG.zip wont get recognized or install is if there is a problem with the sdcard, or its a bad download. Try downloading from a different source http://pvillecomp.com/?page_id=28.
You could run unrevoked with the 5.0.2.0 cmw img (custom recovery) set in unrevoked's menu. You can pull the .img file out of the PB31IMG.zip
I've tested three different SD cards, two different phones, about six different downloads (I've lost count).
I can flash ROM's without any problem. But if I try to flash a radio or recovery (including the stock recovery), it will not work, and this is on both phones. I've tried Stock, RA, CWM 3 and CWM 5. Yet I've tried three different ROM's and they all work fine.
That's a good idea on using Unrevoked and pushing an image. I'm not sure where to specify a custom .img file on Unrevoked, but will try to get through that now.
Thanks again for the ideas!
I pushed the custom recovery by using the CWM v5 .img file as you suggested, but that didn't work either.
The strange thing is how I can install any ROM I like, but CWM or Radios, won't flash. And weirder, is that it's not just a fluke on one phone.
I'm searching everything I can find with no luck. I suppose an RUU is probably the next logical step. I'm just worried because the last I remember, the newer RUU's will cause me to lose S-OFF. I can't remember if that's still the case and the posts don't say definitively.
Why not flash in ROM Manager? Just because it doesn't work in recovery/hboot doesn't mean it won't work in ROM manager. Also what happens if you do
flash_image recovery recovery.img
From either ROM or recovery? Your ROM might not have flash_image but clockwork does.
Sent from my GT-P7510 using Tapatalk
Hi Tiny,
Thank you for the suggestion.
I was previously led to believe that ROM Manager would not work if a straight CWM/Recovery upgrade did not work.
However, you're correct, using ROM manager worked. As a side note: to be safe, I selected "Erase Recovery" and flashed twice, as suggested.
I'm now on our third phone, and not a single one has been able to upgrade CWM coming from 2.5.1.2, but ROM Manager has worked for all of them!
Thanks again!
RKM
I feel compelled to say "Called it."
it'd be good to have hboot able to flash as a safety net but I don't like to bother flashing recovery and finding an hboot compatible zip so I use ROM manager to update. Glad to hear its working.
Sent from my Galaxy Nexus using Tapatalk

can't change TWRP 2.1.1 settings to stop official recovery from reinstalling

Hi all,
I have a Nexus 7, rooted, running stock 4.1.1 rom, and just installed TWRP 2.1.1
I have been reading this thread, http://forum.xda-developers.com/showthread.php?t=1779092 , however I cannot post on the thread due to being a new/low post count member.
I read that, and it does happen, that each time I reboot, the stock recovery reinstalls itself.
I attempted to follow this....
NOTE: The stock ROM may automatically replace TWRP with the stock recovery. To prevent the stock ROM from replacing TWRP, boot TWRP, go to the mount menu and mount system, press the home button, then press Advanced -> File Manager. Browse to /system and select the file named recovery-from-boot.p then choose to rename the file to recovery-from-boot.bak
Click to expand...
Click to collapse
but it doesn't seem to work.
Firstly, when I go to the "Mount" menu, there is only 3 entries.....1 large button which says "Mount USB Storage", and 2 boxes which are selected with a cross in the box, "Unmount Data", and "Unmount Cache". If I do press Mount USB Storage I can only Unmount it to return to menu.
So regardless of that part, if I then go to the file manager, and browse to the system folder, the folder shows up empty, and the only thing showing is a Bin subfolder (also empty)
any ideas whats wrong?
Use the one-click root tool. Install TWRP via GooManager. Profit.
Sent from my Nexus 7
TheBiles said:
Use the one-click root tool. Install TWRP via GooManager. Profit.
Sent from my Nexus 7
Click to expand...
Click to collapse
hi,
yeah I did use the tool, all is rooted fine. If you install TWRP from GooManager, and then press to reset to recovery, TWRP loads fine. Once you reboot again however, the stock roms overwriting the TWRP so it no longer works each time. The steps there were supposedly to stop this from happening, from within TWRP, however the options aren't even there. Sadly, I can't post in the TWRP thread due to having less than 10 posts
How r u booting into recovery? Do u power off then use button combo? I use quickboot from market. Its free and boots u into recovery without having to manually turn off the device. I had the same exact issue u drescribe when attempting to follow op instructions. I couldn't do it so I said what the hell, let me see if I boot into recovery using quickboot it overwrites. I was happy to discover that it didn't.
Sent from my EVO using Tapatalk 2
Hi.
I booted into recovery directly from the GooManager option which restarts it into it for me. After a reboot though choosing the same option gives the official recovery I presume (android robot with chest open and exclamation mark)....until I tell it to install the OpenRecoveryScript again
I'm not familiar with Quickboot - take it its just a button to press to get it into recovery the same way as the GooManager option of "Reboot Recovery"?
I'm looking at this TeamEOS nightly build at the moment, toying with the idea of whether to stick with stock rom or flash their custom rom over it.....hard call as its still early days for the roms I think, but if spend ages again installing my apps, will have to do it again afresh when do eventually change the rom
Midnight Tboy said:
Hi.
I booted into recovery directly from the GooManager option which restarts it into it for me. After a reboot though choosing the same option gives the official recovery I presume (android robot with chest open and exclamation mark)....until I tell it to install the OpenRecoveryScript again
I'm not familiar with Quickboot - take it its just a button to press to get it into recovery the same way as the GooManager option of "Reboot Recovery"?
I'm looking at this TeamEOS nightly build at the moment, toying with the idea of whether to stick with stock rom or flash their custom rom over it.....hard call as its still early days for the roms I think, but if spend ages again installing my apps, will have to do it again afresh when do eventually change the rom
Click to expand...
Click to collapse
Yes quickboot is as u describe. I know what u mean about starting to flash. It's a bit early for me considering conditions of the roms ( early stages). I am getting tempted tho...lol. won't be long I'm sure.
Sent from my EVO using Tapatalk 2
pathtologos said:
Yes quickboot is as u describe. I know what u mean about starting to flash. It's a bit early for me considering conditions of the roms ( early stages). I am getting tempted tho...lol. won't be long I'm sure.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
yup....just installed Quick Boot (Reboot),
chose Recovery, and again its rebooting back to the original recovery instead of the TWRP.
Guess I'll have to flash to a custom rom to get around it if want it sorting now....or wait till I have the minimum post count to post on the main TWRP thread
Not end of the world to reinstall apps and games I guess when the custom roms are more mature, so long as I remember to use Titanium Backup to save my games progress
you need to rename the recovery-restore.sh file in /system/etc/ (I forget the name offhand - if you look at the filenames there you'll figure it out). It restores the stock recovery at every reboot unless deleted or renamed. Then flash your 3rd party recovery.
Hi,
thats the trouble.....I use the file manager in TWRP, and I can't see that file anywhere.
The TWRP page says to go to /system......but when I go there its empty, only one subfolder, /system/bin, which also shows up empty

[Q] nook color CM10.2 update problems CyanogenROM_Downloader/TWRP

Hi all. I have a Nook Color running CM 10.2 and am trying to upgrade it without success.
I have Superuser, CyanogenmodRom_Download, and TWRP downloaded.
Using CyanogenmodROM_Downloader configured to use TWRP I can successfully download a new Nightly. When I select Flash it takes me to Cyanboot. I select Internal eMMC Recovery and it brings up a notice saying that the Install Failed.
I tried using TWRP->Install->CyanogenROM_Downloader->cm-10.2-20131009-NIGHTLY-encore.zip. I'm not Wiping anything. Cyanboot into Internal eMMC recovery and the existing release instead of the update is installed.
Also, the only way I can tell which build is installed is with the CyanogenROM_Downloader. I looked around the web for something that would tell me where to look and didn't find anything. I also looked around /etc and didn't find anything obvious. Is there an easy way to tell what nightly build is installed?
I've been beating on this step for a couple of days now and looking around this site and the web and haven't found anything that helps although I'm sure it's out there somewhere. Any suggestions would be appreciated.
Thanks
Steve S.
Finding installed ROM
sjs_bebop said:
Hi all. I have a Nook Color running CM 10.2 and am trying to upgrade it without success.
I have Superuser, CyanogenmodRom_Download, and TWRP downloaded.
Using CyanogenmodROM_Downloader configured to use TWRP I can successfully download a new Nightly. When I select Flash it takes me to Cyanboot. I select Internal eMMC Recovery and it brings up a notice saying that the Install Failed.
I tried using TWRP->Install->CyanogenROM_Downloader->cm-10.2-20131009-NIGHTLY-encore.zip. I'm not Wiping anything. Cyanboot into Internal eMMC recovery and the existing release instead of the update is installed.
Also, the only way I can tell which build is installed is with the CyanogenROM_Downloader. I looked around the web for something that would tell me where to look and didn't find anything. I also looked around /etc and didn't find anything obvious. Is there an easy way to tell what nightly build is installed?
I've been beating on this step for a couple of days now and looking around this site and the web and haven't found anything that helps although I'm sure it's out there somewhere. Any suggestions would be appreciated.
Thanks
Steve S.
Click to expand...
Click to collapse
Go into system settings / about tablet (at bottom of settings)
About 3/4 down list you'll see the ROM installed. Also kernel info plus other info.
For updates ;
I go to this link and download directly.
http://download.cyanogenmod.org/?type=nightly&device=encore
Also I copy and paste the md5 sum into MD5 checker (free in play store), run the check.
Reboot into recovery using power button menu and install in TWRP there. I had too many problems using cm downloader, goo manager, etc.
nook color cm10.2 update problems
Thanks. That helps. I can determine the version now.
But I still can't get update to work. I downloaded from the location you gave using the browser and can see the file using TWRP and selecting install. This boots into the cyanoboot loader, there are two options enabled: 'Internal eMMC Normal' and 'Internal eMMC Recovery.' Normal seems to reboot -- which makes sense. Recovery re-installs the currently installed version. Also, using ADB I can see the new cm-nightly zip file in /storage/sdcard1/Download.
I don't see TWRP during the reboot. Should I??
I also don't get an option to select a new image to install. Should I?
I also tried copying the cm-nightly zip file to the /emmc directory and that doesn't seem to make any difference.
Sounds like a problem I had a while back
sjs_bebop said:
Thanks. That helps. I can determine the version now.
But I still can't get update to work. I downloaded from the location you gave using the browser and can see the file using TWRP and selecting install. This boots into the cyanoboot loader, there are two options enabled: 'Internal eMMC Normal' and 'Internal eMMC Recovery.' Normal seems to reboot -- which makes sense. Recovery re-installs the currently installed version. Also, using ADB I can see the new cm-nightly zip file in /storage/sdcard1/Download.
I don't see TWRP during the reboot. Should I??
I also don't get an option to select a new image to install. Should I?
I also tried copying the cm-nightly zip file to the /emmc directory and that doesn't seem to make any difference.
Click to expand...
Click to collapse
You may be having partition problems. I have had either lost the ability to install new nightlies or the ability to backup. Read the instructions through completely first. Get the info together and then start.
If you have a backup App like titanium backup, backup all files and data before anything else. Also if you can, do a backup in recovery before doing the following.
Check this link: http://forum.xda-developers.com/showthread.php?p=28457126#post28457126 by Leapinlar
I set up a 2Gb sd bootable card to run these from using the CWM recovery (If you need help check eyeballer's link below).
I put the partition repair files on it. Also the 1.4.3 Stock rom, the TWRP open recovery. zip 2.4.1.0 (http://forum.xda-developers.com/showpost.php?p=37554712&postcount=129), and the latest Rom you want to install and Gapps.
After following leapinlar's instructions including installing the 1.4.3 Stock rom (fixes other possible problems), then follow eyeballer's install for the Rom, Gapps and recovery here (http://forum.xda-developers.com/showthread.php?t=1030227&highlight=install+cm7+to+nook+color).
After booting and doing the initial CM setup return to recovery and VERY IMPORTANT ***restore only the data*** Not boot or system from your latest backup. This should get you back up and running. If you have a backup like Titanium restore "newer versions of apps" if you had to use an older recovery backup. Once you have everything set reboot into recovery and do another backup for safeties sake.
Including my wife's Nook I have four units and have needed to do this 4 or 5 times. Takes a little time but has always worked great. I keep the card available and update the Rom, Gapps or whatever else needs changing.
This link also contains a lot of helpful info. I have all these bookmarked on both my PC and Nook.
User Tips http://forum.xda-developers.com/showthread.php?p=25354258#post25354258

Categories

Resources