I am trying to install the ozzey ROM on my incredible I just got it and rooted it. I have Rom managr, astro file viewer and titanium backup installed. I know I can do it via update.zip or Rom manager but it always fails and says signature verification failed. I triple checked the file to see that it was in .zip not .zip.zip I had windows show the hidden file extensions. In Rom manager it says whole file verification failed along with signature file. Astro file viewer shows it as update and on the root of the SD card but still get the error. I haven't done nand unlock or backup, and I don't care about looking any apps its a new phone with nothing on it. Any suggestions or method instructions? Does the SD card have to be fat32? My SD card is the 2gb pny card. Thanks!
You should just be able to use the .zip, put it anywhere on your sd card. Boot into Clockwork Recovery (If you flashed the new recovery using reflash.exe from unrevoked), DO A NANDROID BACKUP (this is a full system backup), format the user data and cache partition (both options), select update with a .zip and select your preferred .zip file (in your case ozzeh's)
See here for more information and any questions: http://forum.xda-developers.com/showthread.php?t=709220
Any thoughts as to why I am getting those errors? Can I use the re flash tool and go into clockmode recovery and install througt that?
If you do not have clockwork recovery you're not going to be able to flash a ROM. You need to use the reflash tool before you can flash any ROMS.
i have clockwork recovery its on my phone but it still won't flash. Also I tried the reflash but it keeps saying that its interrupted, I uninstalled HTC Sync and it still doesn't work. I also tried to format the sd card to fat32 and ran clockwork recovery but it didnt work same error
It's not clear from your posts exactly what your error is. You say you have Clockworkmod Recovery installed but you keep referencing trying to flash from ROM Manager.
What happens when you boot into Recovery and try to flash the zip file from there?
I instaleld Clockworkmod from ROM Manager, 2.0.1.3 is the verison of clockworkmod I have installed on the phone. I then use ROM Manager to install ROM SD card and it fails, it says signature verification failed and whole-file verification failed. I booted into it and it says it can't find the file in /cache/ and it says verification failed so it aborts and reboots.
kingdavid216 said:
I instaleld Clockworkmod from ROM Manager, 2.0.1.3 is the verison of clockworkmod I have installed on the phone. I then use ROM Manager to install ROM SD card and it fails, it says signature verification failed and whole-file verification failed
Click to expand...
Click to collapse
You might want to try a different rom and see how it goes.
That makes no sense. You can't flash CWM Recovery from ROM Manager on the Incredible (although you can update a prior install, sort of); you have to use unrevoked's tool.
kingdavid216 said:
I instaleld Clockworkmod from ROM Manager, 2.0.1.3 is the verison of clockworkmod I have installed on the phone. I then use ROM Manager to install ROM SD card and it fails, it says signature verification failed and whole-file verification failed
Click to expand...
Click to collapse
I thought I remember reading in some thread that ROM Manager going to clockworkmod will not work because there is no write access.
You will have to use recovery reflash tool to install the clockworkmod recovery and boot into it.
You can find that information in this thread:
http://forum.xda-developers.com/showthread.php?t=706270
supagene said:
I thought I remember reading in some thread that ROM Manager going to clockworkmod will not work because there is no write access.
You will have to use recovery reflash tool to install the clockworkmod recovery and boot into it.
You can find that information in this thread:
http://forum.xda-developers.com/showthread.php?t=706270
Click to expand...
Click to collapse
I instaleld Clockworkmod from ROM Manager, 2.0.1.3 is the verison of clockworkmod I have installed on the phone. I then use ROM Manager to install ROM SD card and it fails, it says signature verification failed and whole-file verification failed
Click to expand...
Click to collapse
You can use Rom manager to boot into clockwork recovery and install the zip from there however, you can't use the feature "Install rom from sd card" within rom manager itself.
Well I tried using just ROM manager to boot into clockwork and I was able to but it still gives me the same errors. I can't do the unevoked flash it reboots then says the communications were intruputed. I deleted HTC synch and had the usb on both disk drive connection and HTC synch but it doesn't go through
kingdavid216 said:
Well I tried using just ROM manager to boot into clockwork and I was able to but it still gives me the same errors. I can't do the unevoked flash it reboots then says the communications were intruputed. I deleted HTC synch and had the usb on both disk drive connection and HTC synch but it doesn't go through
Click to expand...
Click to collapse
Did you ever successfully use unrevoked's flash utility? If you just downloaded rom manager and booted in to recovery without successfully flashing, that won't work.
If you're having problems using the reflash tool then I suggest you get that working and then try again installing a rom.
Use terminal emulator to verify u have su.. Just type su and click accept, if u can do that follow word for word unrevoked reflash method, including installing the correct drivers for adb.
Sent from my ADR6300 using Tapatalk
i just did terminal emulator and i get root acess, #, superuser comes up and allows me to access it, so I will try again but for some reason I get that communication was interuppted.
hey, thanks to all you guys I finally got the custom ROM to work. I did the revoked flash, i had to delete the old htc driver and start again, and once it finally flashed just mounted the sd card and installed, worked perfectly, thanks again!!
kingdavid216 said:
hey, thanks to all you guys I finally got the custom ROM to work. I did the revoked flash, i had to delete the old htc driver and start again, and once it finally flashed just mounted the sd card and installed, worked perfectly, thanks again!!
Click to expand...
Click to collapse
glad you got it working!
Congrats man, good to hear you finally got it working.
Related
Anytime I try to do anything through Rom Manager (flash a ROM, nandroid backup, etc.) upon rebooting into recovery, I get a white triangle with an yellow exclamation point. After pressing the power button, the following text is revealed along with the Clockwork Recovery Menu.
Finding update package...
Opening update package...
Verifying update package...
E:failed to seek in /cache/update.zip (Invalid argument)
E:signature verification failed
Installation aborted.
If I select advanced->Reboot Recovery after receiving the error, the device reboots. After this second reboot, the process continues as it should have after the first reboot. I've tried downgrading the version of my Clockwork Recovery, but it seems to have no effect.
Any ideas?
...
I believe the standard array of initial questions would be:
1) Did you flash S-OFF?
2) Is your card FAT32 formatted
3) Try redownloading the file using a different browser (to ensure a cache doesn't deliver the same update.zip without trying)
jdmba said:
I believe the standard array of initial questions would be:
1) Did you flash S-OFF?
Click to expand...
Click to collapse
Yes.
jdmba said:
2) Is your card FAT32 formatted
Click to expand...
Click to collapse
Yes.
jdmba said:
3) Try redownloading the file using a different browser (to ensure a cache doesn't deliver the same update.zip without trying)
Click to expand...
Click to collapse
This failure isn't specific to any one file. Besides, I don't think it's a corruption of the file since it works when I select "reboot recovery" from the first failed attempt. In fact, this even happens when choosing "Backup ROM" from ROM Manager.
On a side note, I've tried wiping cache in ROM Manager as well.
Toggle Signature Verification and/or is d/l corrupt?
In CWM, have you tried toggling the on or off setting for the signature verification, as well as the other toggle?
Also, I read some superb advice here:http://http://forum.xda-developers.com/showthread.php?t=765930
check out the advice in post # 285 and see if that fixes you up.
Everyone seems to think my downloads are corrupt. That is definitely not the problem. If they were corrupt, they wouldn't function after the first reboot. They would continue to fail. Let me try explain my problem another way...
Here's my device setup...
Radio - 2.15.00.07.28
Kernel - King's BFS #4
ROM - SR Vanilla RC 2
CWM Version - 2.5.0.5
ROM Manager Version - 2.0.2.6
Here's a process I'm following...
1. Open ROM Manager
2. Clear Download Cache (Just to be sure!)
3. Select Backup Current ROM which causes reboot into recovery.
4. Receive the error which I outlined in my first post. *NOTE* I have not downloaded nor chosen to flash ANY update.zip files. *NOTE*
5. Open the advanced menu in CMW and choose "Reboot recovery" which causes the phone to reboot into recovery.
6. The backup progresses like it should have after the first reboot.
Again, the process above does not involve the use of any downloaded update.zip files. No ROMS, no Kernels, etc.
Does ROM Manager create it's own update.zip file stored in /cache to execute whatever function it needs to after reboot? It appears that might be the case.
I've attempted to reinstall ROM Manager and downgrade to an early version of CWM in ROM Manager. Neither seem to have helped.
I had the same problem trying to flash the latest leedroid
I entered recovery, de-selected signature verification and then flashed the rom through recovery mode.
Flashed normally and up to now it looks like it worked (waiting for first boot)
Hope this helped
Both signature verification and script asserts are toggled off. This is why the update.zip will flash after the second reboot into recovery and manually.
In recovery, is cache, data, or system mounted? If so, can you unmount any/ all, and reboot?
Sent from my ADR6300 using XDA App
I just started having this problem today, at least i noticed it today. It acts as if the signature verification is enabled the first try and disabled the second time. I can't find ANY way to fix this but reboot recovery and it works... If anyone finds a solution, please post.
*edit* I also noticed the "Fix Permissions" utility doesn't work in ROM Manager. Dont know if this is related or not.
PIYIRIO said:
I just started having this problem today, at least i noticed it today. It acts as if the signature verification is enabled the first try and disabled the second time. I can't find ANY way to fix this but reboot recovery and it works... If anyone finds a solution, please post.
Click to expand...
Click to collapse
Did you change anything today? I found someone in the SR ROM thread today that started having the same problem.
No, only an app and removed it. I dont know how long it has been broke since I haven't used it since SR 3.0rc1.. got tired of the reminder for rc3 and it wouldn't automagically run the install.zip.
Interesting.... Please post as this shakes out.
Sent from my ADR6300 using XDA App
I have this same issue, I think it's an issue with Rom Manager. No matter what I try to do from there (Reboot to Recovery, make backup, flash zip, etc.) I get that string of messages.
If I download a file from ROM manager to be flashed, I have to move the file to the root of the sd card before booting to recovery for it to flash correctly. I have just gotten used to doing it this way.
srt4mn said:
I have this same issue, I think it's an issue with Rom Manager. No matter what I try to do from there (Reboot to Recovery, make backup, flash zip, etc.) I get that string of messages.
If I download a file from ROM manager to be flashed, I have to move the file to the root of the sd card before booting to recovery for it to flash correctly. I have just gotten used to doing it this way.
Click to expand...
Click to collapse
Me as well
PIYIRIO said:
*edit* I also noticed the "Fix Permissions" utility doesn't work in ROM Manager. Dont know if this is related or not.
Click to expand...
Click to collapse
If you look in the OP for the SR ROMS, you'll see that a known issue. He includes a fix_permissions binary instead.
I've reached out to the developer. Hopefully we will hear from him soon.
Can you guys try clearing your download cache, and then reflashing recovery?
Possible workaround
Koush said:
Can you guys try clearing your download cache, and then reflashing recovery?
Click to expand...
Click to collapse
Cache wipe have been tried, see post #3.
I have some info that may be valuable:
This evening I rooted my Desire (SLCD) using Unrevoked 3.14 and recovery-clockwork-2.5.0.7-bravo.img I realize this is the incredible forum but hold on.. hear me out
I observed the _exact_ same behavior:
- Yellow eclamation + second reboot to recovery would run backup, also happened when selecting "Reboot Into recovery" in RomManager (RM)
- Tried DL cache wipe in RomManager,
- Tried reflash of recovery
This fixed it for me:
- Re-root via Unrevoked 3.14 using recovery-clockwork-2.5.0.1-bravo-slcd.img
- Re-flash CM (this may be optional, I don't know)
- Boot ROM and start RM just to have it tell me I need to install recovery (obviosly didn't detect my 2.5.0.1-bravo-slcd)
- Allow RM to flash 2.5.0.7-bravo via download
- Now "Backup ROM" and "Reboot to recovery" works as intended
- RM reports 2.5.0.7-bravo installed, recovery booted (via RM) is 2.5.0.7-bravo BUT recovery booted using HBOOT (back+power on Desire) is 2.5.0.1-bravo-slcd (!)
Note: Incredible users should _not_ use -bravo recovery images(!) just outlining how I made it work to help you find a solution
Koush said:
Can you guys try clearing your download cache, and then reflashing recovery?
Click to expand...
Click to collapse
Worked for me. Thanks Koush!
Sent from my ADR6300 using XDA App
Didn't work for me.. I've tried everything that I can think of. Different SD cards, i've formated /data/ /cache/ and reinstalled..
i'm using virtuous 2.7
Hi, I have a S-Off'd Wildfire (done with XTC-Clip) in version 2.2.1 and I asked a user from this forum how could I root. He answered me with this message:
Code:
hi poinu glad you managed S-off now you can put on any rom you want.
first you must get a custom recovery on your machine I use ClockworkMod 3.0.0.6
this should be fine to flash cyanogenmod7.
here is the file to it (http ://www . mediafire . com /?i09yp4r7odhlzws)
put this PC49IMG.zip on the root of your sd card. (not in a folder)
put the cyanogenmod update zip also on your sd card.
Reboot your phone into Hboot Mode by pressing Volume Down and Power.
It will now ask if you want to update the firmware select Volume Up for Yes.
wenn its done remove thePC49IMG.zip from your sd card.
Reboot your phone into Hboot Mode again.
it will look for the PC49IMG.zip again let that finish and ignore.
Then go with volume down to recovery and push power button, clockwordmod will start.
Do a wipe cache partition, wipe data/factory reset and under advanced wipe Dalvik cache.
go to install zip from sdcard / choose zip from sd card and choose your cyanogen mod update zip and install.
reboot wen finished don't worry if it takes some time first reboot always is slower.
hope i helped you enjoy your mod.
kind regards ab65
I've downloaded the PC49IMG.zip file and copied at the root next to the cm7.zip file (picture: http : //i55 . tinypic . com/ egai5s. png) but when I enter the HBOOT and looks for the PC49IMG.zip file, it finds nothing (and yes, the file is PC49IMG.zip not PC49IMG.zip.zip, I've already checked this )
I don`t know what I have done wrong (I have done nearly anything!) any ideas?
Thank you very much for having a look on the threat
here is what i suggest simply,
***** Ur memory card must be formatted with fat32 partition before doing this.......
go to this link and download the attached file at the bottom PC49IMG.ZIP
http://forum.xda-developers.com/showpost.php?p=12188132&postcount=15
Since security flag is turned of (by xtc clip) , the recovery partition is no longer protected. U can install custom recovery without any exploits. That downloaded PC49IMG.ZIP file is nothing but "ClockworkMod Custom Recovery". Put it in the root of the memory card (fat32). Then go to hboot menu. It definately finds the file and prompts u to install. Go with it. At the end u will have custom recovery.
then u can install custom roms. Custom roms will be packed in zip files and can be installed from recovery menu. Its not needed to put the custom rom zip file only in the root of memory card. And the most important thing is, remember to clear data/factory reset and clear cache (both done frm recovery menu) before installing a custom rom. Thats all
Oh god, i didn`t know that.... succesfully done
but now... there's another problem, I installed the CyanogenMod7 and there are some things that I pretty dislike and I would like to install another ROM I have (it's a 2.2.1 rooted ROM) and I tried to do what I did to install the CM7 but when I installed it from the recovery this error message appeared:
"Installing update...
Amend scripting (update-script) is no longer supported.
Amend scripting was deprecated by Google in Android 1.5. It was necessary to remove it when upgrading to the ClockworkMod 3.0 Gingerbread based recovery.
Please switch to Edify scripting (updater-script and update-binary) to create working update zip packages.
Installation aborted."
Is it really possible to root this ROM or do I have to stay in the CM7? :S
Any suggestion? Thank you very much for the support
poinu said:
Oh god, i didn`t know that.... succesfully done
but now... there's another problem, I installed the CyanogenMod7 and there are some things that I pretty dislike and I would like to install another ROM I have (it's a 2.2.1 rooted ROM) and I tried to do what I did to install the CM7 but when I installed it from the recovery this error message appeared:
"Installing update...
Amend scripting (update-script) is no longer supported.
Amend scripting was deprecated by Google in Android 1.5. It was necessary to remove it when upgrading to the ClockworkMod 3.0 Gingerbread based recovery.
Please switch to Edify scripting (updater-script and update-binary) to create working update zip packages.
Installation aborted."
Is it really possible to root this ROM or do I have to stay in the CM7? :S
Any suggestion? Thank you very much for the support
Click to expand...
Click to collapse
CLockworkmod 3 is a must for the gingerbread CM7 roms.
And clockworkmod3 recovery will not support "amend - scripting"
What u need to do is, to install the CM7 custom rom. Then install "Rom Manager" from market. Then use a different version of clockworkmod (downgrade to 2.5 version or try different versions). Then reboot to recovery from Rom manager itself. Then try to install the 2.2.1 rooted rom. It should work. If u have any issues with installing custom roms, then try different version of clockworkmod recovery (from Rom Manager). That's all.
explanation: http://forum.xda-developers.com/showthread.php?t=897026
it surely worked, thank you very much
I done the Alpharev s-off method but now when I try to install CM7 from CWM 3.0.0.6 it get stuck on "Installing update"
Any ideas?
diarmaid said:
I done the Alpharev s-off method but now when I try to install CM7 from CWM 3.0.0.6 it get stuck on "Installing update"
Any ideas?
Click to expand...
Click to collapse
what recovery do you use? did you dowloaded the zip correctly?
I upgraded to cwm4 and it worked perfectly.
That was a close one, it was a birthday present for the missus and i finally got it working on the morning of the birthday
Sent from my HTC Desire S using XDA App
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.
stock recovery gives me error "E:signature verification failed"
In stock recovery, I can see my sdcard and select which zip file i want to install.. but when i do, i get the signature verification error.
CW recovery cannot see my sdcard (tried 3 different cards so far) and gives me error: files not found. Mounting SDcard does not do anything.
reformatted the 3 SDcards many times. , wiped the phone cache and tried disabling signature verification in CW recovery.
Phone is bricked now and has no ROM installed. Access to download and recovery mode are my 2 options only.
bid1 said:
stock recovery gives me error "E:signature verification failed"
In stock recovery, I can see my sdcard and select which zip file i want to install.. but when i do, i get the signature verification error.
CW recovery cannot see my sdcard (tried 3 different cards so far) and gives me error: files not found. Mounting SDcard does not do anything.
reformatted the 3 SDcards many times. , wiped the phone cache and tried disabling signature verification in CW recovery.
Phone is bricked now and has no ROM installed. Access to download and recovery mode are my 2 options only.
Click to expand...
Click to collapse
You're getting the signature error.because you are trying to flash an unofficial zip. With stock recovery the zip has to have a signature for it to flash.(this is why we need custom recovery)
What version of cwm are you flashing? If its the one that doesn't support the external SD card you have to put whatever zip you want to flash on the internal SD card, not the external. I think newer versions of cwm released have support for the external card. If you can get into download mode I would suggest flashing the stock rom and kernel through odin
Sent from my Samsung Galaxy S II Epic 4G Touch
Double post
Had this happen to my brother's phone last night where sd cards won't read and he couldn't flash a ROM. Your phone is not bricked if you can get into CWM or Odin mode. Take a look at this thread:
http://forum.xda-developers.com/showthread.php?t=1282420
Use Odin to flash to the stock eg30.tar and start from scratch. I'm new so I hope I didn't lead you into the wrong path or tell you something you already knew. Good luck!
bid1 said:
stock recovery gives me error "E:signature verification failed"
In stock recovery, I can see my sdcard and select which zip file i want to install.. but when i do, i get the signature verification error.
CW recovery cannot see my sdcard (tried 3 different cards so far) and gives me error: files not found. Mounting SDcard does not do anything.
reformatted the 3 SDcards many times. , wiped the phone cache and tried disabling signature verification in CW recovery.
Phone is bricked now and has no ROM installed. Access to download and recovery mode are my 2 options only.
Click to expand...
Click to collapse
Can you give a bit more explanation?
Which kernel do you have installed right now? Which ROM do you have installed?
Here is how i fixed this:
1- File (SPH-D710_Zedomax_EpicTouchKernel-v3 (SPH-D710_Zedomax_EpicTouchKernel-v3.tar) allowed me back into SDCard since it has CWM5. CW5 was able to do what CWM4 was not : give me access to sdcard. It also eliminated signature verification error.
2- Loaded Starburst ROM.
One common misconceptions here.
Very few people here understand the difference between firmware, kernel and ROM. You search for stock ROM and you will get stock kernel, stock firmware but NEVER stock ROM.
Also, ODIN DOES NOT allow ROM flashing. Odin does not recognize zip format. All ROMs are in zip format.
bid1 said:
Here is how i fixed this:
1- File (SPH-D710_Zedomax_EpicTouchKernel-v3 (SPH-D710_Zedomax_EpicTouchKernel-v3.tar) allowed me back into SDCard since it has CWM5. CW5 was able to do what CWM4 was not : give me access to sdcard. It also eliminated signature verification error.
2- Loaded Starburst ROM.
One common misconceptions here.
Very few people here understand the difference between firmware, kernel and ROM. You search for stock ROM and you will get stock kernel, stock firmware but NEVER stock ROM.
Also, ODIN DOES NOT allow ROM flashing. Odin does not recognize zip format. All ROMs are in zip format.
Click to expand...
Click to collapse
There is a stock rom on here to flash with odin ..... I have done it search and you will find it
http://forum.xda-developers.com/showthread.php?t=1282418
Sent from my SPH-D710 using xda premium
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.