Develop Bugs

[Q] Problem upgrading ClockworkMod.

I dowloaded ROM Manager from the market and used the Flash ClockworkMod Recovery option to upgrade to the latest verion of CWM.
From the ROM Manager application it says the current verion is 3.0.0.8 but when I reboot into recovery the phone still says v2.5.1.2. Am I doing something wrong?
Thanks

EKhatch1 said:
I dowloaded ROM Manager from the market and used the Flash ClockworkMod Recovery option to upgrade to the latest verion of CWM.
From the ROM Manager application it says the current verion is 3.0.0.8 but when I reboot into recovery the phone still says v2.5.1.2. Am I doing something wrong?
Thanks
Click to expand...
Click to collapse
in ROM manager hit Menu >> Settings and check the box for Erase Recovery. This will erase your current recovery before flashing the new one to give you a clean flash.
Then just hit Flash ClockworkMod Recovery. It should attempt to flash it again.

Okay I did that and it didn't work so I cleared the download cache from the menu setting and tried again. It appeard to work but when I reboot into recovery my phone still says it is on v.2.5.1.2
Maybe this is a sign I should just leave my phone alone for a while. lol

Just manually flash it. ROM Manager was doing that to me too. I hate using ROM Manager... lol. I flash stuff manually myself because then I know is going on.
http://dougpiston.com/?page_id=85
For AMOLED: use 3.0.0.7 (some have reported problems with 3.0.0.8 on AMOLED).
For SLCD: use 3.0.0.8
Rename the zip you download to "PB31IMG" (without quotes) and put it on the root of your SD card. Boot to HBoot and flash the update when prompted (by pressing Vol Up).

Don't forget to delete the zip after it successfully updates. To add onto CarngeX, the zip should be named: PB31IMG.zip

Okay thanks. I had never even tried ROM Manager for anything else. I always load ROM's manually but I thought it would be way more complicated to update than you showed me. It's all good now. Thanks again.

SlimSnoopOS said:
Don't forget to delete the zip after it successfully updates. To add onto CarngeX, the zip should be named: PB31IMG.zip
Click to expand...
Click to collapse
Reason I just said "name it to PB31IMG" is because a lot of times people have file extensions hidden, and they end up naming it to "PB31IMG.zip.zip" and it causes more problems lol.
EKhatch1 said:
Okay thanks. I had never even tried ROM Manager for anything else. I always load ROM's manually but I thought it would be way more complicated to update than you showed me. It's all good now. Thanks again.
Click to expand...
Click to collapse
Glad you got it running.

carngeX said:
Just manually flash it. ROM Manager was doing that to me too. I hate using ROM Manager... lol. I flash stuff manually myself because then I know is going on.
For AMOLED: use 3.0.0.7 (some have reported problems with 3.0.0.8 on AMOLED).
For SLCD: use 3.0.0.8
Rename the zip you download to "PB31IMG" (without quotes) and put it on the root of your SD card. Boot to HBoot and flash the update when prompted (by pressing Vol Up).
Click to expand...
Click to collapse
I'm just curious, I've updated my cwm to 3.0.0.7 already through rom manager, but I had previous tried doing it like this through recovery using a .zip. When it prompts for the update, is it just passive? Like you enter hboot and then wait until it asks if you want to upgrade?

soft pillowcase said:
I'm just curious, I've updated my cwm to 3.0.0.7 already through rom manager, but I had previous tried doing it like this through recovery using a .zip. When it prompts for the update, is it just passive? Like you enter hboot and then wait until it asks if you want to upgrade?
Click to expand...
Click to collapse
When you boot to HBoot, it should check for a PB31IMG.zip file on your card. If it finds one, it'll ask if you would like to update or not.

carngeX said:
When you boot to HBoot, it should check for a PB31IMG.zip file on your card. If it finds one, it'll ask if you would like to update or not.
Click to expand...
Click to collapse
I guess I didn't package it right since I would see it scan for it (quickly, so I couldn't see what it was saying exactly), but it didn't offer me any option to update afterwards. Thanks.

Then it's probably not named correctly (needs to be exactly PB31IMG.zip, check for hidden extensions), or your SD card isn't formatted to fat32.

k_nivesout said:
Then it's probably not named correctly (needs to be exactly PB31IMG.zip, check for hidden extensions), or your SD card isn't formatted to fat32.
Click to expand...
Click to collapse
Thanks, I think it's the formatting issue; I'll try again soon.

Trying to install a custom ROM

Hey,
Basically, I've got a HTC Wildfire with HBoot 1.0.0.2 - s-off was already disabled by stock.
I first of all tried to root with revolutionary, this attempt failed and it booted back up into a red triangle with an exclamation mark - pulled the battery out and all was fine again, booting into android. Realised later that this was due to being on 2.2.1
Then I tried rooting with Gingerbreak, it gave me a failed message and say it might just be the fact that it failed to restart - rebooted the phone and superuser was installed so it appears to have worked
ok so, installed custom rom manager and tried to install clockworkmod, it appears to have installed but when I click boot from clockworkmod it reboots and goes back into the red triangle?
any ideas to what might be going wrong, i think theres a problem with the clockworkmod installation
THANKS

Get a PC49IMG.Zip of a CWM Recovery version you want from here: (Point #6), place on SDCard, and reboot into HBoot. It will install CWM, then try selecting Recovery again in HBoot
http://forum.xda-developers.com/showpost.php?p=12782368&postcount=2
I am assuming by "s-off was already disabled by stock" you mean you ARE S-OFF.

It says S-OFF on the top of HBoot, so I would presume that it was disabled from factory
I put the .zip on the SD card, and booted HBoot - it did it's scan for files at startup but did not find the zip on the sd card? does it have to be in a particular place on the SD (PC49IMG.ZIP)
It's saying not found or wrong image - Im trying to use ClockWorkMod v5.0.2.0 - Click here for PC49IMG ZIP and its on the root of the sd card

I hope you clicked the right part of the link. Clockworkmod v5.0.2.0 and Click here for PC49IMG ZIP link to two different files. Try downloading the right hand side file (Which is a file named PC49IMG.zip), place that on your sd card and try again.
It should not be in any folder / sub-folder on your sd. Just place it as it is.

3xeno said:
I hope you clicked the right part of the link. Clockworkmod v5.0.2.0 and Click here for PC49IMG ZIP link to two different files. Try downloading the right hand side file (Which is a file named PC49IMG.zip), place that on your sd card and try again.
It should not be in any folder / sub-folder on your sd. Just place it as it is.
Click to expand...
Click to collapse
nope :/*I used the PC49IMG file, I also tried the one from the earlier release and no joy - this is strange, everything i try to do with this phone results in problems haha
(this is billy, just in my friends house)

*.*Bump*.*
still stuck in the same situation, any help or suggestions would be greatly appreciated.

[Q] clockworkmod recovery

hello,
last night i tried to flash an update from cm7 nightly and after trying it, decided to return to the previous build i was using. i did a nan restore and encountered an error "md5 mismatch". i asked for 3xeno help as to what could have possibly caused the error and suggested some possible causes and solution to my problem which I am still trying to figure out till now. but in the meantime i have just decided to reflash the nightly i was using and reinstalled all the apps i was using.
i read quite a few articles and threads here and if i understood it right there are some cwm version that encounter nandroid restore problems. i am currently using cwm 3.0.0.6 and i was wondering if there is a cwm version that i can use which is more stable and will not create any problems if i would make nan restores in the future.
thanks.

Switch to 5.0.2.0. No issues with Nandroid Backups / Restores. I have done tons of restores with this version.

3xeno said:
Switch to 5.0.2.0. No issues with Nandroid Backups / Restores. I have done tons of restores with this version.
Click to expand...
Click to collapse
will give it a try and see how it goes.
edit: i found the link from your guide you posted before sir. the zip for cwm 5.0.2.0 with the PC49IMG zip. sorry for the stupid question, should i flash both zip?

[email protected] said:
will give it a try and see how it goes.
edit: i found the link from your guide you posted before sir. the zip for cwm 5.0.2.0 with the PC49IMG zip. sorry for the stupid question, should i flash both zip?
Click to expand...
Click to collapse
The two zips are different ways of installing it.
Download PC49IMG.zip only and place on SD card root, go into hboot and press volume up when it asks you to update
Sent from my HTC Wildfire using XDA App

jacktyler1807 said:
The two zips are different ways of installing it.
Download PC49IMG.zip only and place on SD card root, go into hboot and press volume up when it asks you to update
Sent from my HTC Wildfire using XDA App
Click to expand...
Click to collapse
Manage to flash it as per 3xeno guide and suggestions. Im now on cwm 5.0.2.0. Thought i had it figured out at first but it was only temporary recovery. Flashed PC4IMG zip and now everything is good.
Thanks.

3xeno said:
Switch to 5.0.2.0. No issues with Nandroid Backups / Restores. I have done tons of restores with this version.
Click to expand...
Click to collapse
I get lots of MD5SUM errors with this version of CWM, 4 out of 5 nands fail on me. I think my card may be to blame but i really dont trust my backups now. I'm sketchy about any mods I do now because i cant be sure if my backups will restore.

If you are ready to use fastboot, you can use it to push all the IMG files directly to your Wildfire without bothering about MD5 checksums. (I had loads of MD5 errors on versions 4.x, but not a single one yet, as I said before, on 5.0.2.0)

3xeno said:
If you are ready to use fastboot, you can use it to push all the IMG files directly to your Wildfire without bothering about MD5 checksums. (I had loads of MD5 errors on versions 4.x, but not a single one yet, as I said before, on 5.0.2.0)
Click to expand...
Click to collapse
Will probably try to learn that method over the weekend. I tried a nandroid backup and restore with cwm 5.0.2.0 and it went well so far. Thank you for the suggestion sir.
If my previous backups including my stock rom gets really messed up, I guess Im just gonna stick with cm7. I'm loving it anyway.

Quoting myself from a previous post:
2) Use Fastboot
- Download this attachment and extract it to any folder (eg: C:\fastboot)
http://forum.xda-developers.com/atta...1&d=1308537074
- Download CWM IMG Image for Wildfire (Buzz) from here:
http://download.clockworkmod.com/rec...0.2.0-buzz.img
- Place that IMG file along with the 4 files from the attachment in the same folder you created
- Now, turn off your Wildfire, connect to PC, and turn on in HBoot
- Navigate to Fastboot and Select it
- Open a Command Prompt Window (Start > Run > cmd)
- Type the following one by one and press Enter (It is assumed you created the folder in C Drive and have named it fastboot)
- cd\
- cd fastboot
- fastboot flash recovery recovery-clockwork-5.0.2.0-buzz.img
- This should produce 2 lines of code - SENDING RECOVERY and WRITING RECOVERY. If both states OK at the end, you should have CWM installed successfully after this.
Click to expand...
Click to collapse
The above Quote was for installing a Recovery Image like CWM. Fastboot commands use the following syntax:
fastboot flash <partition name> <name of IMG file to be flashed>
So, the other command names will change according to the files from your previous Nandroid Backup. Examples:
fastboot flash cache cache.img
fastboot flash system system.img
fastboot flash data data.img
... and so on

will give this a try sir. thanks

[Q] Help! Edited settings.db now phone won't boot?

I am running a T-Mobile Note 3, stock rom, rooted. I wanted to get unrestricted wifi tethering by following a thread that has you edit the settings.db. Before editing it I not only made a backup copy but I also renamed the settings.db in the original location to .bk. I edited the settings.db with SQLite, saved it and overwrote the original. After rebooting I'm just stuck at a t-mobile logo.
So my question is how can I now erase that and rename the backup?
First try:
I'm in recovery but no devices are listed. Bummer.
Second try:
In recovery I pick "apply update from ADB". Now my device is listed but you cannot 'adb shell' from that mode.
What else can I try? Is there a way to make a sideload.zip that will restore my settings.db so I don't have to restore the entire phone?
Update:
Now I'm trying to create my own update.zip to sideload. So far I have been unable to get the file signed.

Where is the thread you are following
TWEAKED N3

This thread in this forum: http://forum.xda-developers.com/showthread.php?t=2467193 which links you over to this thread (another forum) http://forum.xda-developers.com/google-nexus-5/help/nexus-5-tethering-block-t2512674/page8.
The next thing I tried was to flash CWM using Odin. I thought CWM would let me use adb shell in recovery since the stock recovery doesn't. I flashed with Odin and then I could't get into recovery at all, awesome.
Finally I downloaded TWRP and flashed it with Odin. This time it worked and I could boot into recovery. In recovery I used adb to go to my settings.db file and I saw that the permissions were root:root instead of system:system. I chowned it and now I am back up and running!

pcm2a said:
This thread in this forum: http://forum.xda-developers.com/showthread.php?t=2467193 which links you over to this thread (another forum) http://forum.xda-developers.com/google-nexus-5/help/nexus-5-tethering-block-t2512674/page8.
The next thing I tried was to flash CWM using Odin. I thought CWM would let me use adb shell in recovery since the stock recovery doesn't. I flashed with Odin and then I could't get into recovery at all, awesome.
Finally I downloaded TWRP and flashed it with Odin. This time it worked and I could boot into recovery. In recovery I used adb to go to my settings.db file and I saw that the permissions were root:root instead of system:system. I chowned it and now I am back up and running!
Click to expand...
Click to collapse
glad you got it working. that thing sent you all over the place. not a good thread.

[Q] Help -- CWM not working

Can't install any ROMs on G2.
Had CWM 5.0.27, I think. Couldn't install any of several ROMs. Installed CWM 6.0.4.5. Same outcome.
Aroma installer always stops at "Symlinking..." after extracting files.
Says "set_perm: some changes failed" and Status 7.
What am I doing wrong?

O's said:
Can't install any ROMs on G2.
Had CWM 5.0.27, I think. Couldn't install any of several ROMs. Installed CWM 6.0.4.5. Same outcome.
Aroma installer always stops at "Symlinking..." after extracting files.
Says "set_perm: some changes failed" and Status 7.
What am I doing wrong?
Click to expand...
Click to collapse
Well as far as I remember, the new roms were better to be installed with 4ext Recovery, because the CWM had some problems working with ext4 filesystem. Try the one I have on the web site below, that should fix it for you.

a.s.j said:
Well as far as I remember, the new roms were better to be installed with 4ext Recovery, because the CWM had some problems working with ext4 filesystem. Try the one I have on the web site below, that should fix it for you.
Click to expand...
Click to collapse
Thanks, but the zip didn't work. Put it in sdcard root and tried several times with CWM Touch 5.8.1.0 -- installation failed, every time.
I've since gotten CM10.1 and Mimicry to work with CWM, but I'm struggling with one ROM in particular no matter the recovery: coolIOS, a 4.0.4.
Tried to install it with CWM 5.0.2.7 and got the error described at top.
Tried with CWM 6.0.4.5.
Tried with CWM Touch 5.8.1.0.
Tried with TWRP 2.6.3.0.
Same error, every time. Redownloaded the ROM, but same. I'm really at a loss with that one. It worked fine on a previous G2.

O's said:
Thanks, but the zip didn't work. Put it in sdcard root and tried several times with CWM Touch 5.8.1.0 -
Click to expand...
Click to collapse
Just try to install 4EXT recovery !
http://4ext.net/

Kéno40 said:
Just try to install 4EXT recovery !
http://4ext.net/
Click to expand...
Click to collapse
I meant the only 4ext install zip I could find didn't work.
Downloaded the apk from the site and got "Cannot open file".
Yes, Unknown Sources is checked.
Thanks, anyway.
EDIT: Got 4ext working, but still no help. Had to extract the .img from the install zip, install Mimicry ROM, and use the Terminal Emulator to flash the .img. That got it working, but it only boots in safe mode. Says it can't read the cache partition, and also says this:
"If you changed hboot you should choose to format all partitions (except sdcard)".
Formatted all partitions, rebooted recovery -- still safe mode. Still says it can't read cache.
Starting to think some of the physical memory is corrupt.
But if that's the case, why do other ROMs work? Or does someone else see another plan/fix/anything here? Thanks.

O's said:
I meant the only 4ext install zip I could find didn't work.
Downloaded the apk from the site and got "Cannot open file".
Yes, Unknown Sources is checked.
Thanks, anyway.
EDIT: Got 4ext working, but still no help. Had to extract the .img from the install zip, install Mimicry ROM, and use the Terminal Emulator to flash the .img. That got it working, but it only boots in safe mode. Says it can't read the cache partition, and also says this:
"If you changed hboot you should choose to format all partitions (except sdcard)".
Formatted all partitions, rebooted recovery -- still safe mode. Still says it can't read cache.
Starting to think some of the physical memory is corrupt.
But if that's the case, why do other ROMs work? Or does someone else see another plan/fix/anything here? Thanks.
Click to expand...
Click to collapse
There is no install zip on my pages, just zipped image which should be pushed in via Fastboot. You are perhaps doing something terribly wrong my friend.
What you need to do can be achieved by several ways:
- Rename recovery.zip to PC10IMG.zip put it into your /sdcard root and start your phone to recovery (hold Vol-Down and Power to start recovery system)
- use adb to push the image to the recovery partition
- or the easiest could be to check this one: http://www.4ext.net/install.pdf

a.s.j said:
There is no install zip on my pages, just zipped image which should be pushed in via Fastboot. You are perhaps doing something terribly wrong my friend.
What you need to do can be achieved by several ways:
- Rename recovery.zip to PC10IMG.zip put it into your /sdcard root and start your phone to recovery (hold Vol-Down and Power to start recovery system)
- use adb to push the image to the recovery partition
- or the easiest could be to check this one: http://www.4ext.net/install.pdf
Click to expand...
Click to collapse
Perhaps I was unclear. I downloaded your zip and renamed it PC10IMG.zip and put it in sdcard root and started to recovery, but that did not work. I thought it would work, since the phone showed the "vertical progress bar" as if it was about to change recovery, but I didn't get the prompt to "Update recovery?" that I usually see there. So nothing happened.
I also tried to download the 4ext apk directly from the site onto my phone, but after downloading the apk, phone said "Cannot open file."
Instead, I got 4ext working by downloading the zip in the 4ext forum zip. It contains an .img that I flashed in Terminal Emulator, which got 4ext working.
Once I booted to 4ext, it said it could only load in safe mode because it couldn't read the cache. It advised to wipe the cache, so I wiped everything several times, but it still only loads in safe mode.
I'll try your zip method again, and I thank you for the assistance. I just don't get why five different recoveries work on some ROMs but not one that worked fine on a past G2.

O's said:
Perhaps I was unclear. I downloaded your zip and renamed it PC10IMG.zip and put it in sdcard root and started to recovery, but that did not work. I thought it would work, since the phone showed the "vertical progress bar" as if it was about to change recovery, but I didn't get the prompt to "Update recovery?" that I usually see there. So nothing happened.
I also tried to download the 4ext apk directly from the site onto my phone, but after downloading the apk, phone said "Cannot open file."
Instead, I got 4ext working by downloading the zip in the 4ext forum zip. It contains an .img that I flashed in Terminal Emulator, which got 4ext working.
Once I booted to 4ext, it said it could only load in safe mode because it couldn't read the cache. It advised to wipe the cache, so I wiped everything several times, but it still only loads in safe mode.
I'll try your zip method again, and I thank you for the assistance. I just don't get why five different recoveries work on some ROMs but not one that worked fine on a past G2.
Click to expand...
Click to collapse
SOLVED: Helps if I read the instructions. Thread for that ROM clearly says to have Desire Z hboot; I had G2 hboot. In all the years of using a G2, I've never had to switch hboot and was unfamiliar with it. If anyone else has same issues as this post, might try installing the Virtuous Team's PC10IMG.zip and read up on it at the Hboot thread. Thanks to all who beared with my lack of knowledge.