Develop Bugs

Unrevoked3

Hey all. Need help as usual. I "rooted" using unrekoved3. I'm a mac user and that's the reason i chose unrevoked. But now I'm thinking i should have jusr rooted from a pc. I dont think i have full rooy. Heres what i did.
1. Download unrevoked3 for mac. Opened file, ran program, rooted phone.
2. Downloaded titanium backup. Performed a full user/data and app backup.
3. Downloaded busybox.
4. Downloaded rom manager. Clicked clockwork option.
5. Downloaded terminal emulator
Verified root by typing SU, got #.
6. Accessed superuser permission app.
7. Downloaded setcpu.
8. Downloaded root manager.
I never ran a pc36img file on the phone. When i go into bootloader and try to do a nand, the screen stays on htc evo 4g white screen. When i enter bootloader, some text flashes for a second that says pc36diag.zip and pc36nbh.zip... no Image! I think i missed a step.
I had 2.2 before root, thats why i chose unrevoked3. I am thinking about unrooting but i dont know how to on a mac. It seems i need to download htc sync which there are no links for a mac.
I dont know what to do. Should i unroot on a pc and reroot using a better method? Im driving to va, currently in TN. Ill be mobile so please reply and or msg me on gtalk: [email protected]. thanks guys
Sent from my Evo 4g from inside my Evo X.

I think once you go into the bootloader screen, there should be an option to go into recovery mode.
sent via HTC EVO

i tried doing that. the phone wont go into recovery mode. it just stays on the white htc evo 4g screen. the exact message i get when i go into bootloader is this...
sd checking...
loading... [pc36imgdiag.zip]
no image!
loading... [pc36diag.nbh.zip]
no image or wrong image!
loading... [pc36img.zip]
no image!
loading... [pc36img.nbh]
no image or wrong image!
then it goes back to the bootloader screen, if i select power down it will boot normal. if i select recovery, it freezes on white screen

I'm a total noob to EVO and I am getting the same result too...
Altough I rooted via PC. I was on 2.2 stock from the box and I used unrevoked3 as well. Everything seemed to be OK and I showed root and S-OFF but after downloading ROMManager and trying to do a nand backup, I keep getting this same message during bootup. If I let it do its thing, the phone seems to work OK... but I don't think I have root anymore. I tried to load wireless tether and it tells me that I need root, so I assume I am no longer rooted.
Could it be that I need to load a recovery onto SD? I'm gonna try and do unrevoked3 again and see if it will give me root again...
EDIT: when I try to go to recovery, I get the black screen with the red circle and ! and it doesn't do anything. I have to do a battery pull.

hah funny story, IT IS SUPPOSED TO FLASH THAT TEXT. this is the phone checking itself for a manual update. i have no idea why you cant go into recovery. try reflashing with rom manager again, but this time, i would reccomend the alternate recovery (amon ra)

thanks, I'll try that
what do I do, put amon ra on the sd?

http://forum.xda-developers.com/showthread.php?t=705026 recovery thread
im personally not a big fan of clockwork...
i prefer fastboot method, if you have a pc handy. need the tools folder of the android sdk and put the recovery file in the same directory as fastboot (should be /android sdk/tools unless you change install folders)
although you can flash recovery w/o pc using adb method. get astro or another file manager so you can move files around easily on /sdcard/ put the recovery file on the sd card and check if you have flash_image. if not, i have it attached and then just put it on the root of the sd card as well. then follow instructions on the recovery thread.
if you need the flash_image, go into the .zip and extract it to sd card root.

[problem] desire restarting after cyanogen flash

Heya,
I was using the LeeDroid ROM until today, when I desided I want Cyanogen.
I backed up the phone using ROM Manager, wipe and flashed Cyanogem 6.1 RC2. The phone restarted, turned on - but it cn't load the actual android OS - just keeps restarting on the blue wheel-thing animation.
I can boot my phone into recovery, but can't do much from there since its S-ON.
The recovery windows says:
bravo pvt1 ship s-on
hboot-0.80.0000
microp-031d
touch panel-synt0101
radio-5.10.05.23
fastboot
recovery
clear storage
simlock
what can I do to get my phone working again? Will a simple restore using HTC software do the trick (followed by root with unrevoked)?
Thanks

CoreOxide said:
Heya,
I was using the LeeDroid ROM until today, when I desided I want Cyanogen.
I backed up the phone using ROM Manager, wipe and flashed Cyanogem 6.1 RC2. The phone restarted, turned on - but it cn't load the actual android OS - just keeps restarting on the blue wheel-thing animation.
I can boot my phone into recovery, but can't do much from there since its S-ON.
The recovery windows says:
bravo pvt1 ship s-on
hboot-0.80.0000
microp-031d
touch panel-synt0101
radio-5.10.05.23
fastboot
recovery
clear storage
simlock
what can I do to get my phone working again? Will a simple restore using HTC software do the trick (followed by root with unrevoked)?
Thanks
Click to expand...
Click to collapse
Which version of Clockworkmod recovery did you fakeflash? There is an issue with the latest one that makes your SDcard unaccessible afterwards. It also mess up your USB.
Here is a thread that guides you how to fix it: http://forum.xda-developers.com/showthread.php?t=691639

I used the latest one, 2.5.1.7 I think.
Isn't there a way to restore the phone with the HTC software, sonething lite the iphone+itunes combo?

Is your sd card not being recognzed?
As you said you created a backup using rom manager before you flashed the new rom. So why dont you just enter hboot, go to recovery and the restore youre phone to the backup that you made using rom mabager before you flashed?

When I select "recovery" using the HBOOT I get a picture of a phone, and a red triangle with an exclamation mark. Does this mean I have to do the USB brick fix?

hmmm thats odd ... sounds like it could be a usb brick related issue, im not sure as i havnt had the same problem before or seen anyone else in the forum experiencing this problem.
I think you should read up more about the usb brick fix, hopefully there is something there that would be able to help you ... if its already known that the latest version of clockworkmod does give this problem then im sure its this and you would be able to find a solution to this problem.
Good luck

UPDATE:
My bad, I was supposed to press volumeup+power to see the recovery screen.
Now, when I do that I get "E:Can't open /cache/recovery/command", and get only 4 options:
reboot system now
apply sdcard:update.zip
wipe date
wipe cache
Is this related to the USB BRICK thing?

You need to wipe data when switching roms, this will fix the bootloop.
I would also suggest you flash a permanent recovery for ease of use. You need to use unrevoked to do this.

CoreOxide said:
UPDATE:
My bad, I was supposed to press volumeup+power to see the recovery screen.
Now, when I do that I get "E:Can't open /cache/recovery/command", and get only 4 options:
reboot system now
apply sdcard:update.zip
wipe date
wipe cache
Is this related to the USB BRICK thing?
Click to expand...
Click to collapse
This is the default android recovery screen. The error "E:Cant open...." is something I also get.
Do you have an update.zip on your SDcard? Like the clockworkmod recovery? http://forum.xda-developers.com/showthread.php?t=839640Use 2.5.0.7 and not 2.5.1.2 (has the fail you most likely see now). If correct update.zip on SDcard, try to press apply sdcard. If youre able to do so, you are accessing your sdcard. If youre getting problems applying this update file. I suggest following the thread I told you in my first post You then have to make your SDcard accessible with a fastboot command.
You are accessing fastboot by holding vol down while powering your phone on. Select fastboot. Plug your USB. Download the Android SDK or only fastboot.exe. Run this command from cmd: "fastboot oem enableqxdm 0". You should get a return command like "okay", and your SD card should be accessible again. Now you will need to follow the guide and fix your USB. However, you should be able to flash a new ROM now when your SDcard is accessible again, or just restore the nandroid backup that gave you this problem to begin with
Update: post #30, weee!

jmelhus said:
This is the default android recovery screen. The error "E:Cant open...." is something I also get.
Do you have an update.zip on your SDcard? If so try to press apply sdcard. If youre able to do so, you are accessing your sdcard. If youre getting problems applying this update file. I suggest following the thread I told you in my first post You then have to make your SDcard accessible with a fastboot command.
Click to expand...
Click to collapse
When i select that I get "E; failed to open sdcard\update.zip (no such file or directory)
E: signature verification failed"
Does this simply mean I don't have that file on my card?
If so, is there a way to access the card in mass storage mode while the phone is in HBOOT?

CoreOxide said:
When i select that I get "E; failed to open sdcard\update.zip (no such file or directory)
E: signature verification failed"
Does this simply mean I don't have that file on my card?
If so, is there a way to access the card in mass storage mode while the phone is in HBOOT?
Click to expand...
Click to collapse
Do you have a mem reader for windows/linux? Look if you have the file or not. If you don't have it, copy it there. If it's there, you have a problem with accessing the SDCard.
I would say, If I were you, I would try to "repair" the SDcard with the fastboot command first. Most likely, your ROM will boot again when it can read from your SDcard.
Other options would be to try to push the update file with ADB in Android Recovery. Most likely you can't push it either since your SDcard most likely is inaccessible. Try fastboot
Download Android SDK for Windows here: http://dl.google.com/android/android-sdk_r07-windows.zip
MD5: 69c40c2d2e408b623156934f9ae574f0
Unzip the file. Open CMD, navigate to the tools folder in SDK. Issue the command.
Source: http://developer.android.com/sdk/index.html

I ran the SDcard fix on CMD, it said "OKAY", but nothing changed in the phone's condition.
I put the SDcard on a card reader and saw there are backup files (.img) in the clockworkmod directory. how do i get the phone to recover from them?
The "update.zip" file, where can i get that one?

CoreOxide said:
I ran the SDcard fix on CMD, it said "OKAY", but nothing changed in the phone's condition.
I put the SDcard on a card reader and saw there are backup files (.img) in the clockworkmod directory. how do i get the phone to recover from them?
The "update.zip" file, where can i get that one?
Click to expand...
Click to collapse
You can get your update.zip file from here: http://forum.xda-developers.com/showthread.php?t=839640
Download the 2.5.0.7 zip file and rename to update.zip. Put on root of SDcard and apply sdcard: update.zip in android recovery. From here, go to nandroid, restore, and select your backup.

Doesn't the Update.zip file suppose to be a zipped ROM?

Not necessarily. A zip can flash a lot of different things. I'm not that much into it. But it all depends on the content of the zip file.

How do I " go to nandroid"?

CoreOxide said:
How do I " go to nandroid"?
Click to expand...
Click to collapse
Don't remember what it's called exactly. But when running update.zip (clockworkmod), you should have a restore menu somewhere...

Thanks a lot man! recovering right now.. will update when done.
About that S-ON thing, will the Unrevoked reflash option "Remove phone security" take care of this? Is there a risk in re-rooting?
I want to add some notifications sounds and the "system" folder is write protected
EDIT:
The restore works just fine!

[Q] another bricked phone thread; help needed

I've looked around for solutions as much as I could before posting
I've outlined everything I've done so far, not sure how much is relevant
Was running LeeDrOiD HD V3.3.1 before the phone became bricked
I rebooted the phone at one point, and the battery fell out during a reboot
Next time I rebooted it got to the ascii art android logo, onto a part with text on, and got stuck in a boot loop, the text had a progress part "so&so out of 2703kb" or something to that effect
(can't remember the text exactly)
After a few tries at rebooting it went to the home screen, however nothing loaded onto the home screen for 20 minutes, and the only function that worked was locking the screen, I couldn't turn it off or anything.
After this, everytime I booted it got stuck in a boot-loop on a splash screen of
"ANDROID" in silver writing
This is what I currently get when I boot my phone
When booted into recovery mode (hboot) I first get the message;
SD Checking...
Loading...[PC36DIAG.zip]
No image!
Loading...[PC36DIAG.nbh]
No image or wrong image!
Loading...[PC36IMG.zip]
No image!
Loading...[PC36.IMG.nbh]
No image or wrong image!
Click to expand...
Click to collapse
After I get this message I am free to go into fastboot and recovery menu
The PC recognises the phone in fastboot (I'm running windows 7)
I tried reflashing the leedroid rom straight from the recovery menu, didn't affect anything at all.
Went on to reformat sd card entirely.
Tried updating to the latest ruu, as there was no ruu that was exactly the same as mine, my phone was originally on virgin mobile and there were no ruu's with the same baseband
RUU used; RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.exe
But the update fails part way through (after it reboots the phone) and gives
ERROR 131: CID ERROR
Rom update utility cannot update your phone at this time
Please get the correct rom update utility and try again
Click to expand...
Click to collapse
Current information that hboot gives me;
Bravo PVT1 SHIP S-ON
HBOOT-0.80.0000
TOUCH PANEL-SYNT0101
RADIO-5.11.05.14
Click to expand...
Click to collapse
Can anyone help?

if you can go into recovery, try reflash the zip file again and let it do its job. your hboot is not screwed so it shall restart with a new flash. recommending you download oxygen and save it on your sdcard. due to its fastest to load and most stable.

Just FYI: bootloop is not any kind of brick, and you're not bricked either.
Just do full wipe and reflash the ROM.
If you want to go back stock, you will need goldcard when running RUU.
SD Checking...
Loading...[PC36DIAG.zip]
No image!
Loading...[PC36DIAG.nbh]
No image or wrong image!
Loading...[PC36IMG.zip]
No image!
Loading...[PC36.IMG.nbh]
No image or wrong image!
Click to expand...
Click to collapse
Everyone is getting this upon entering bootloader...

Flashed oxygen, rebooted, left for 5 minutes
I'm still stuck in a boot loop, however the 'ANDROID' text splashscreen is now the 'OXYGEN' splashscreen

Did you do Full Wipe/Factory reset & dalvik cache wipe before flashing new ROM?
Do you have any partitions on SD card?

k3lcior said:
Did you do Full Wipe/Factory reset & dalvik cache wipe before flashing new ROM?
Do you have any partitions on SD card?
Click to expand...
Click to collapse
I wiped both
Yes, I partitioned it as instructed in the stickied noob guide
4GB partioned to 1GB of Ext3, the rest is FAT32. The partition is still there.

Probably something went wrong when you was creating ext partition, what i suggest is downloading this recovery:
http://forum.xda-developers.com/attachment.php?attachmentid=661317&stc=1&d=1311251519 (md5sum zip: 170785457774834c7ae58e331d6f4ab4)
Put it onto your sdcard (root of SD, not in any folders), rename it to "PB99IMG.zip" and boot into bootloader.
It should ask if you want to update, choose yes.
Partition your SD in new recovery, it will also perfectly align it, try to flash with this should be good.

k3lcior said:
Probably something went wrong when you was creating ext partition, what i suggest is downloading this recovery:
http://forum.xda-developers.com/attachment.php?attachmentid=661317&stc=1&d=1311251519 (md5sum zip: 170785457774834c7ae58e331d6f4ab4)
Put it onto your sdcard (root of SD, not in any folders), rename it to "PB99IMG.zip" and boot into bootloader.
It should ask if you want to update, choose yes.
Partition your SD in new recovery, it will also perfectly align it, try to flash with this should be good.
Click to expand...
Click to collapse
Didn't ask if it wanted to update
Text said loading image, A progress bar automatically appeared on the right, after it was done loading, it said 'checking image' then just went straight back into the bootloader

Are you sure you renamed file to PB99IMG.zip ? You can also try to rename it to PB99IMG (without extension)

k3lcior said:
Are you sure you renamed file to PB99IMG.zip ? You can also try to rename it to PB99IMG (without extension)
Click to expand...
Click to collapse
Yep, just double checked and tried a few more times, redownloaded and tried again just to be sure.
When renamed without extension the phone didn't find it, renamed with .zip extension the phone seemed to recognise it, but stopped after saying "checking image"

If you are branded try to put in you gold card and then try...
btw.
What did you used to partition your SD card?

k3lcior said:
If you are branded try to put in you gold card and then try...
btw.
What did you used to partition your SD card?
Click to expand...
Click to collapse
I'm just trying to create a gold card now (didn't know about them until after I flashed)
I used Gparted

You can also try to repartition in the recovery you have right now, might help who knows.

I'm crossing my fingers for the repartitioning from current recovery mode to work
because I'm not entirely sure on how to create a goldcard without being able to boot my phone normally
*edit*
Yes, that did indeed work
seems the file structure got fudged up when the battery fell out for a reboot
such a simple solution that I overlooked at the beginning sorry
Thanks for all your help

Create goldcard and bring your phone back to stock with the ruu you already wanted to use. With three goldcard you won't get the cid error.
Run unrevoked again, but this time you use a custom recovery:
http://downloads.unrevoked.com/recovery/3.21/reflash_package.exe
I can highly recommend rmd recovery:
http://forum.xda-developers.com/showthread.php?t=1137763
Download the zip, extract it and check the md5 of the image.
Standard amonra recovery:
www.android-hilfe.de/attachments/ro...-0-0-14-11-2010-recovery-ra-desire-v2.0.1.zip
Configure your phone correctly for using unrevoked.
Start unrevoked>file>custom recovery>choose the downloaded recovery image.
Run unrevoked.
If successfully done, go into recovery and flash custom rom.
The one k3lcior provided cannot be used as long as one is not s-on. So you cannot use it.
@k3lcior: Take care of this when you tell people to flash this recovery.
Swyped from Oxygen with Transparent XDA App

[Q] HBOOT Image and Update Script Errors

What I did:
Rooted Evo 4G Gingerbread using Revolutionary
Flahsed su-2.3.6.3-efgh-signed.exe and PC36IMG.EXE
Worked great, got excited flashed:
SOS_v1.9.0.2-swag.exe, navbar_rednblack.exe, remap_camera.exe, and ChopSuey-v.9.2.6-UNIVERSAL-signed.exe
Whats going on:
SOS, navbar, and remap flash fine; all other flash attempts give the error, E: Can’t Find Update Script
At HBoot
SD Checking
Loading (PC36IMG.img)
No Image
Loading (PC36IMG.img)
No Image or Wrong Image
Loading (PC36IMG.img)
No Image
Loading (PC36IMG.img)
No Image or Wrong Image
(With PC36IMG.EXE on the SD root) Also
Parsing (SD ZIP)
(1) Recovery
So how do I get rid of the errors so I can flash another ROM or whatever? Thanks for helping a noob

If you're already rooted, you need to boot into recovery. Then navigate to where the .zip (ROM) is located. The instructions to flash should be provided on the first page of the dev's post.

Thank you but, I don't undeerstand. I can find the zip files that I put on the SD card, and go into the recovery screen but when I try and flash any ROM/add on/bootanimation/ I get the eror, E: Can’t Find Update Script" so where is the script? Also, any ieas on the no/wrong image issue?

What recovery r u using? R u flashing chopsuey thru hboot or recovery?
Sent From My Pocket

I flashed the Kernal throu recovery.

HBoot> scroll to Recovery>hit power key> Brings up android systems recovery screen> scroll to "Flash sip from SDcard> Select the zip file. That is when I get the E: Can not find update script error.
I am not running the PC36IMG ROM, I am running the SOS_v1.9.0.2-swag but in HBOOT, its looking for the PC36IMG image, are't these issues related?

Google "evo amon-ra xda forums".
Download the PC36IMG.zip.
Copy and paste it in the root of your SD card.
Press volume up to install in hboot.
Once complete, boot into recovery and try to flash the ROM zip file.
Be sure to delete the amon-ra zip file or else it'll just ask if you want to flash when hboot loads.
Sent from my PC36100

Thanks, trie your suggestion but the file still aborted with the can find update script error.

Sounds like you got a bad zip file
Sent From My Pocket

i also have this problem now (different phone tho). but now it keeps telling me "No image!" "loading....[pj75diag.zip] No image!"

alltoEZ said:
i also have this problem now (different phone tho). but now it keeps telling me "No image!" "loading....[pj75diag.zip] No image!"
Click to expand...
Click to collapse
Go to the correct forum for your device. I'm sure someone over there will be able to help you do whatever it is you're trying to do.
If you're looking for a bootloader-flashable recovery file, I posted one in the TWRP thread for the LTE.

[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.