I recently installed CM7 following this guide (http://forum.xda-developers.com/showthread.php?t=1337105) and had no troubles at all. I soon got bored of CM7 and went to try a CM9 ROM but when I went to install it via Clockwork it failed. I tried a few others and they all failed also. I even tried to re install the stock ROM and restore from my backup but nothing worked. I'm still stuck on CM7. Anyone got any ideas of what's going wrong?
Edit 1: For example when I attempt to re install the stock ROM I get an error message saying "E:can't open /sdcard/PG32IMG.zip (bad) Installation aborted"
Bobtehblob said:
I recently installed CM7 following this guide (http://forum.xda-developers.com/showthread.php?t=1337105) and had no troubles at all. I soon got bored of CM7 and went to try a CM9 ROM but when I went to install it via Clockwork it failed. I tried a few others and they all failed also. I even tried to re install the stock ROM and restore from my backup but nothing worked. I'm still stuck on CM7. Anyone got any ideas of what's going wrong?
Edit 1: For example when I attempt to re install the stock ROM I get an error message saying "E:can't open /sdcard/PG32IMG.zip (bad) Installation aborted"
Click to expand...
Click to collapse
install Roms from inc s development section following their instructions and you should be fine. Roms are usually not in pg32img format and are not made to be installed using that method. The guide you're following also does not mention using this filename to install Roms.
In fairness, at least you're stuck on a stable Rom.
Sent from my Incredible S using Tapatalk 2
Take pg32img.zip out of the root of your SD card.
Sent from my Incredible S using xda premium
Yup, delete the PG32IMG file from your SD card or try a new radio(for better performance). You can find it in the development forum thread.
Sent from my Incredible S using xda app-developers app
Just make sure it's not a froyo rom! You don't want to brick your phone.
Sent from my Incredible S using xda app-developers app
Froyo roms wont brick your phone, however there will be no radio support unless you flash a froyo radio which will brick your phone. After saying that I doubt in any case that there are no active links to any froyo anything for the incs any more.
Sent from my Incredible S using xda premium
Related
Hi guys, I'm new to Android, swaped my 3Gs for a N1, I manually updated the phone to FW 2.3.3 (GRI40), the phone is stock, no root, no custom firmware.
The phone randomly loses network connectivity, (no network available message on display) I can't connect using 3G but I can with Wi-Fi, can't make phone calls, only way to fix this is to reboot the phone or switch airplane mode on/off.
I have radio version 5.08.00.04, kernel 2.6.35.7-59423-g08607d4.
I like this phone and don't want to swap it for an iPhone 4, but this issue is starting to get on my nerves, please let me know if there is a fix for this.
Root and flash cm7.2. Has more goodness than others. Then flash Inexus theme to make it eyecandy when look at and google apps package.
Sent from my Xoom using XDA App
Can you give me a link to CM7.2?
sandman_rave said:
Can you give me a link to CM7.2?
Click to expand...
Click to collapse
BTW - this is one of many options.
Theres a lot of eager people who (perhaps incorrectly) think CM is the answer to everything...
http://download.cyanogenmod.com/?device=passion
Sent from my Nexus One using XDA Premium App
Ok, I tried everything and nothing seems to work, I reverted back to FRG33, but I can't root the device, everything fails, I can't go back to EPE76 or something else, I get the old version error.
I can't update to 2.2.1 or anything higher than that (including moded GRI40 versions) because I get the signature error.
Basically I can only install FRG33 or GRI40 (stock FW), the phone works fine on FRG33 but I would like to be able to install 2.2.2 (FRG83G i think), cause the 2.3.3 is just crap, reminds me of some older iPhone firmwares.
So, what should I do, cause i'm out of ideeas, please keep in mind that this is my first android phone when you explain something.
Thanks.
You can either root, or flash the updates one at a time:
FRG33> FRG83> FRG83D> FRG83G> GRI40...
Sent from my Nexus One using XDA Premium App
I tried that but it doesn't work, I receive the no signature error.
I got the fw from the wiki.
Strange...
Just for a sanity check, make sure that the files you downloaded aren't a zip within a zip, and MD5 check for integrity...
Sent from my Nexus One using XDA Premium App
I checked the archives, everithing is fine, I done a factory reset and tried again with the same result.
I am on FRG33 now (I flashed the rom using passimg.zip copied on the SD), trying to update to FRG83, I got the ROM's from here. I receive this error:
E:signature verification failed
Installation aborted
This sh**t is driving me mad.
I got bootloader 0.35.0017 and it's unlocked.
You're unlocked?
Are you running a custom recovery (Ra)?
Have you turned signature verification off?
Sent from my Nexus One using XDA Premium App
I bought this phone from a guy, and I don't know exactly what he has done with it before but when I go into bootloader (trackball+power) I get a line that says unlocked, I don't know exactly what it means, it's like the one in the attachment.
It means your bootloader is unlocked. Basically, you now have the ability to install images to the phone through fastboot on the PC.
Sent from my Nexus One using XDA Premium App
After a few hours of reading and rom download I managed to update 2.2 to 2.2.1 using this rom "766a101ae02c.signed-passion-ota-60505.766a101a.zip" not sure where I downloaded it from but worked like a charm and then I applied the the updates to get to 2.2.2 (FRG83G).
And now, how do I root? I tried SuperOneClick, I installed the USB drivers etc, the software runs, it installs superuser on my phone, the SOC SU test is OK but I installed Terminal on the phone and the SU command returns access denied, also I installed Root Manager and it doesn't start because it doesn't have sufficient permissions, I have no pop-up when opening to grant root access to Root Manager.
Any ideas?
I finally managed to root my phone thanks to Danger-Rat's super easy tutorial you can find here
Thanks for all the help.
There are a few problems i'm having. Have done multiple roots (z4, super one click) and have super user access but doesn't show any where. If that matters our could be the reason to my problem. I have rom manager and multiple roms but everytime I try to install them I get some error message saying the certificates could not be verified. Does any one have a suggestion about what is wrong?
Sent from my SAMSUNG-SGH-I897 using XDA App
s.7 said:
There are a few problems i'm having. Have done multiple roots (z4, super one click) and have super user access but doesn't show any where. If that matters our could be the reason to my problem. I have rom manager and multiple roms but everytime I try to install them I get some error message saying the certificates could not be verified. Does any one have a suggestion about what is wrong?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
rom manager is poop...use clockwork i created a roms folder on my sd where all my roms go its easier to use clockwork mod. update for it is attached copy to internal sd and boot recovery with 3 button combo and select reinstall packages might have to do it twice till you see it then select rom and and install reboot and success
Tried it 3 times still had the same problem.
Sent from my SAMSUNG-SGH-I897 using XDA App
But this time it erased all of my pictures
Sent from my SAMSUNG-SGH-I897 using XDA App
What rom are you on? Sounds like you don't have root. If super user is not there then that is your problem. The root didn't take, you need super user
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
I have super user access but it doesn't show up in amy of the info as rooted. When i troed to unroot and reroot using super one it said i had a temporary abd root and to restart my device to remove it. I did that but it still says the same thing. I'm trying to get cognition v4
Sent from my SAMSUNG-SGH-I897 using XDA App
s.7 said:
I have super user access but it doesn't show up in amy of the info as rooted. When i troed to unroot and reroot using super one it said i had a temporary abd root and to restart my device to remove it. I did that but it still says the same thing. I'm trying to get cognition v4
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
BACKUP
1.Flash stock
2. Master Clear
3. Grab a CW mod recovery update zip from on of the threads.
4.Copy said zip and rom zip to phone
5. Follow directions to flash rom. Lots of FAQ on how to do it
What do you mean by flash stock?
Sent from my SAMSUNG-SGH-I897 using XDA App
I've done it the way this website, theunlockr.com and numerous youtube videos have said to do out. I keep getting the ertor (E: failed tp verify whole-file sinature. Followed by E: signature verification failed installation aborted)
Sent from my SAMSUNG-SGH-I897 using XDA App
This is how you "flash back to stock": http://www.megaupload.com/?d=SBSMALFJ
Instructions can be found on http://forum.xda-developers.com/showthread.php?t=884364
It's crucial you read most of it, and then ask if you don't understand any of the steps there.
guys I have a problem I would like to install the cm7, I do the download. room, I put the SD card without problems when it turns on the milestone in recovery mode, then carcica. by sd. zip file party controls cn ke then after a while I started out: failed to verify whole-file signature
and I abort the installation that I do? ? ah thanks I forgot Froyo official and the Phone is rooted
Milestone A853 italy
Sent from my Milestone using XDA Premium App
If I understood, you are running official froyo. To flash CM7, you need to flash vulnerable recovery first to run Androidiani Open Recovery needed to flash CM7.
Sent from my Milestone using Tapatalk
I just downloaded cm7 following these steps here today:
http://forum.xda-developers.com/showthread.php?t=932196
and used this rom:
http://androidforums.com/motorola-m...date-milestone-android-2-3-3-instruction.html
there is also a different set of instructions in the 2nd link.
thanks a lot S2556
, successful trials as the second link ke I had written was a show and had all the correct files that I used. if
you ever walk away from Italy and Modena have offered coffee hello thanks again
Sent from my Milestone using XDA Premium App
Hello guys, as a friend was having trouble with her sgs+, i had to install a custom rom, and i had a samsung phone before and i know the procedure, so i first installed the official CWM for sgs+ and tried to install blazr rom battery edition.. it got installed, and when i press reboot, it was rebooting to recovery only... then i was a bit tensed as it was not my phone, and thought of installing other recovery and try other rom afterwards, i installed feamod recovery and the rom was booting normally, and it was fine, but the rom isnt good and she wanted some other rom, and then i downloaded ehndroix rom and when i try to install it, i get a code 7 error ( 'assert' some error) and i know that this problem is because the phone isnt being detected as sgs+, i tried installing different roms, with different recoveries but the same code 7 error, then i installed brood rom rc5 via odin and its doing well, but she really wanted enhdroix rom and i still get code 7 error while installing roms, please can someone tell me how to fix the code 7 error? or are there any other custom roms for sgs+ which can be installed though odin?
your help would be greatful, please :crying:
read here, same error 7
http://forum.xda-developers.com/showthread.php?t=2303815
Sent from my GT-I9000 using xda premium
If you are absolutely sure the rom is for your device you can remove the assert lines from the updater script. These are usually the first couple of lines in the script. But if the rom is not for your device and you bypass the assert.....well then you could have a nice brick.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
compacity said:
read here, same error 7
http://forum.xda-developers.com/showthread.php?t=2303815
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
i tried even that, i am still getting the same error.. are there any custom roms which can be installed via odin?
jd1639 said:
If you are absolutely sure the rom is for your device you can remove the assert lines from the updater script. These are usually the first couple of lines in the script. But if the rom is not for your device and you bypass the assert.....well then you could have a nice brick.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Yeah i know that, and wanted to try that but didnt know exactly how many lines to delete, if you could give an example i would try it out.. and yeah, the rom is 100% for that phone only.
roh756 said:
Yeah i know that, and wanted to try that but didnt know exactly how many lines to delete, if you could give an example i would try it out.. and yeah, the rom is 100% for that phone only.
Click to expand...
Click to collapse
Before you do that, make sure you have the latest version of cwm. You can get the error 7 with an older cwm and the newer roms. The assert lines are pretty obvious. Just delete the lines that start with assert. Extra the rom zip and with your way down to the updater script and open it with notepad ++
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
jd1639 said:
Before you do that, make sure you have the latest version of cwm. You can get the error 7 with an older cwm and the newer roms. The assert lines are pretty obvious. Just delete the lines that start with assert. Extra the rom zip and with your way down to the updater script and open it with notepad ++
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
okay, thanks
OTA [UNTESTED] [NAKASI-wifi only!]
NO GUARANTEE IF IT WILL WORK BUT NO HARM IN CHECKING THE FILES!:laugh::victory:
I WILL NOT BE RESPONSIBLE IF IT BRICKS YOUR DEVICE!!!
One Person reports it to be working.... thats good news
http://android.clients.google.com/p....signed-nakasi-JWR66V-from-JDQ39.ab67ca07.zip
LINK CREDITS-StannyG
Downloading. Wish me luck
CheCorchete said:
Downloading. Wish me luck
Click to expand...
Click to collapse
Best of Luck!! Be Really careful!! IT may not work~!
CheCorchete said:
Downloading. Wish me luck
Click to expand...
Click to collapse
How was your luck??
Seems like my pc is missing a driver, lol. But android police make a wonderfull guide with link to the ota http://www.androidpolice.com/2013/0...-to-android-4-3-jwr66v-and-root-it-right-now/
It works, got the link this am from the original post, rebooted in cmw, flashed it, over my stock rooted nexus 7. At first lost root, but found a beta of superuser flashed that with cwm and all of back to normal. Now I am running 4.3 rooted stock Rom...
Sent from my Nexus 7 using XDA Premium HD app
mk69 said:
It works, got the link this am from the original post, rebooted in cmw, flashed it, over my stock rooted nexus 7. At first lost root, but found a beta of superuser flashed that with cwm and all of back to normal. Now I am running 4.3 rooted stock Rom...
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I try to flash the zip through cwm and keep getting an error...
assert failed: apply_patch_check
instalation aborted...status 7 ...
E: error in (filename.zip)
anyone knows what´s going on? already downloaded the zip many times
i´m on stock rooted 4.2.2 LOCKED bootloader (motochopper root method)...maybe something about the bootloader?
mtdelnero said:
I try to flash the zip through cwm and keep getting an error...
assert failed: apply_patch_check
instalation aborted...status 7 ...
E: error in (filename.zip)
anyone knows what´s going on? already downloaded the zip many times
i´m on stock rooted 4.2.2 LOCKED bootloader (motochopper root method)...maybe something about the bootloader?
Click to expand...
Click to collapse
I used nrt to root my n7, I am not sure about the method you used. Also if you changed any build prop parameters, or any stock system apps, you must revert back to the original files before this ota update will work. The update will check your n7 to see if there were any mods to the original stock files. If you can't revert back to know what was changed then you may have to do a full flash of 4.2.2 then flash the update...
Try to write down the error message when you try to flash the update, that may give you some clues...
Sent from my Nexus 7 using XDA Premium HD app