Related
I always get an error saying E:/ cannot open file /cache/update.zip (bad), no matter what ROM it is. theres not even an update.zip anywhere on my phone or sd card, and i cant manage to get to this so called /cache. please help.
Mrblackroot said:
I always get an error saying E:/ cannot open file /cache/update.zip (bad), no matter what ROM it is. theres not even an update.zip anywhere on my phone or sd card, and i cant manage to get to this so called /cache. please help.
Click to expand...
Click to collapse
Since this isn't development related, you should post it in the general board.
You didn't install clockwork correctly, or you didn't follow all of the directions when you did install it. Did you follow the instructions and press "flash clockworkmod recovery", which downloads the latest version and puts the update file on your phone?
i did, i have the latest recovery version. and i uninstalled and then reinstalled it before trying again.
Wrong section and you have to use the option that says choose zip from sdcard not the one that says install update.zip
Sent from my GT-I9000 using XDA App
Mrblackroot said:
I always get an error saying E:/ cannot open file /cache/update.zip (bad), no matter what ROM it is. theres not even an update.zip anywhere on my phone or sd card, and i cant manage to get to this so called /cache. please help.
Click to expand...
Click to collapse
If there is no update.zip then in Rom Manager you need to select the first option that reads Flash ClockworkMod Recovery. That will bring up a screen asking which phone. If you are installing an i9000 rom choose i9000. If not choose the Captivate. That will install an update.zip on your sd card
Then select install rom from sd card and it will probably take you to stock recovery so select install packages (or whatever the 2nd choice is). That will get you into CWM. Install whatever rom from there
First off, this is the right section, as this thread is *somewhat* development related.
I had a similar problem a while back, and never did figure out exactly what was causing it. Might have been because I often just use the Clockwork update.zip (bootstrapped from stock recovery) to flash ROMs without always "installing" it from Android itself. Though, even when I got that error, I could still flash new ROMs without problems.
Either way, flash to stock w/ oneclick, then do a master clear, fixes the problem right up.
If there is no update.zip then in Rom Manager you need to select the first option that reads Flash ClockworkMod Recovery. That will bring up a screen asking which phone. If you are installing an i9000 rom choose i9000. If not choose the Captivate. That will install an update.zip on your sd card
Then select install rom from sd card and it will probably take you to stock recovery so select install packages (or whatever the 2nd choice is). That will get you into CWM. Install whatever rom from there
Click to expand...
Click to collapse
Thanks a lot, this worked. is there anyway i can just move this thread to the general forum, or would that require a moderator?
Shammyh said:
First off, this is the right section, as this thread is *somewhat* development related.
I had a similar problem a while back, and never did figure out exactly what was causing it. Might have been because I often just use the Clockwork update.zip (bootstrapped from stock recovery) to flash ROMs without always "installing" it from Android itself. Though, even when I got that error, I could still flash new ROMs without problems.
Either way, flash to stock w/ oneclick, then do a master clear, fixes the problem right up.
Click to expand...
Click to collapse
Mmmm.. last time I checked the development forums was for developers to start topics on things they have developed or are working on... not for Q & A. There's another board for that..
I get this error all the time.
Open ROM Manager, hit Menu, hit Clear Download Cache.
Then hit Flash Clockwork Mod Recovery, choose Captivate, and let it go. Then hit Reboot Into Recovery and it should work fine. You may have to select Reinstall Packages if you end up in the stock 2e recovery.
Hey fellow G2x's. I rooted my phone today and attempted to install CM7 nightly #56. FIrst of all...
I tried just downloading the rom via rom manaer, clicked wipe data and wipe cache. When I did it tried to install and asid "Could not open cm7nightlyetc..." And then it proceeded to reboot itself as if it was a new phone.
I then tried to do it via recovery. First whenever I click install from zip card then choose zip from sdcard, the only file I can see is LOST.DIR/ even though I deliberately moved the rom into the sdcard/. I was met with the same problem.
During both the encounters. a triangle with an ! appears, with a little android dude next to it. WHat does this mean? What do I need to do to fix this?
GManLynx said:
Hey fellow G2x's. I rooted my phone today and attempted to install CM7 nightly #56. FIrst of all...
I tried just downloading the rom via rom manaer, clicked wipe data and wipe cache. When I did it tried to install and asid "Could not open cm7nightlyetc..." And then it proceeded to reboot itself as if it was a new phone.
I then tried to do it via recovery. First whenever I click install from zip card then choose zip from sdcard, the only file I can see is LOST.DIR/ even though I deliberately moved the rom into the sdcard/. I was met with the same problem.
During both the encounters. a triangle with an ! appears, with a little android dude next to it. WHat does this mean? What do I need to do to fix this?
Click to expand...
Click to collapse
First rule of G2X/Tegra2 club... don't use Rom Manager. Use CWR for all your flashing needs. *Install CWR via NVFlash only.
Alright, I'm sorry but I came the G2.... And I was wondering what NVFlash is? I'm gonna google it, but it will be nice if you answer it too.
Setting up NVFlash
Here's the guide to setting up NVFlash. It's a moderately challenging process, but it's seamless after getting it put on your G2x. This is the only way to get CWM without issues. http://forum.xda-developers.com/showthread.php?t=1054492
Oh, and remember to go into C: on your computer and make the folder "G2x". This is where you put the files from NVFlash.
darbear5610 said:
Here's the guide to setting up NVFlash. It's a moderately challenging process, but it's seamless after getting it put on your G2x. This is the only way to get CWM without issues. http://forum.xda-developers.com/showthread.php?t=1054492
Oh, and remember to go into C: on your computer and make the folder "G2x". This is where you put the files from NVFlash.
Click to expand...
Click to collapse
yup and when u get ready for commands u can copy and paste them
techboydino said:
First rule of G2X/Tegra2 club... don't use Rom Manager. Use CWR for all your flashing needs. *Install CWR via NVFlash only.
Click to expand...
Click to collapse
First - the above is the truth - learned the hard way by many.
From the "triangle" comment, I would have thought you were not able to get into recovery anymore, but you said you had tried flashing in recovery - are you still able to get into recovery? Also, when you said you moved the file to the SD - internal or external?
You could re-download the ROM on you computer and/or move the one you downloaded when in USB connect mode if you can connect through USB. and then try flashing it again.
Otherwise - did you do an nandroid back-up first (add that to the G2X Club rules). If so, and you can get into recovery, you can restore it through recovery. If not, you are truly back to square one (except for rooted).
At some point, you need to NVflash a real recovery. The one-click method in the Dev section is the easier way to go. If you can't get into recovery (you only see the triangle and it only does a factory reset), then you HAVE to start there.
Yeah I am still able to get to recovery mode. And external sdcard.
I think i'm just gonna go staright to the NVFlash way. I have a history class today so I have a hour and a half to burn.
And thanks guys for all the inputs.
I'm loving my G2x so far. So fast and sleek
All you need to do is NVFlash once, just so you can get into recovery on a bootloop (Power+VolDown)
After you install NVFlash once, you can use RomManager all you want (I do).
Rom Manager will install a temp recovery initially, but it won't affect your permanent NVFlash recovery. So just do both. Rom Manager will work perfectly fine without doing a NVFlash, but an NVFlash just enables the option to get into recovery on a cold boot.
Every day, I launch Rom Manager and it will find the latest Nightly and download it plus Google Apps, prompts for Full Wipe, Backup, or Cache options, then it will reboot, flash the items, and reboot back into Android.
So, again, NVFlash just enables Power+VolDown to get into recovery but Rom Manager works great without it. You SHOULD do BOTH initially and just get it out of the way.
Alright thanks. I just installed via NVFlash and now I will try again to install CM7
player911 said:
All you need to do is NVFlash once, just so you can get into recovery on a bootloop (Power+VolDown)
After you install NVFlash once, you can use RomManager all you want (I do).
Rom Manager will install a temp recovery initially, but it won't affect your permanent NVFlash recovery. So just do both. Rom Manager will work perfectly fine without doing a NVFlash, but an NVFlash just enables the option to get into recovery on a cold boot.
Every day, I launch Rom Manager and it will find the latest Nightly and download it plus Google Apps, prompts for Full Wipe, Backup, or Cache options, then it will reboot, flash the items, and reboot back into Android.
So, again, NVFlash just enables Power+VolDown to get into recovery but Rom Manager works great without it. You SHOULD do BOTH initially and just get it out of the way.
Click to expand...
Click to collapse
Agree with all the above (I have and use both), except for making nandroids, which was not mentioned above. The only ones where I have had a check-sum issue with trying to restore are nandroids I did with ROM Manager. I would stick with doing them straight from recovery.
Others have had issues with flashing nightlies also, but I have not noticed that as I always head straight to recovery to flash.
Question - I had flashed real recoveries with ROM manager on MT4G - why the "false" recovery issue on G2X?
So player, once I have NVFLASH and CWM, I can download ROM manager to backup/restore/flash any ROM from the list without worrying about anything?
Hey, I installed the 4.0.0.3 and I still have the same problem. I can't see any roms I put on the SD card, and when I try to install it by naming it update.zip it gives me the same error. Any ideas?
OKay so here is what happens
Installing: /sdcard/update.zip
Finding update package...
Opening update package...
E:Can't open /sdcard/update.zip
(No such file or directoy)
Installation aborted
THere is definately a file there. I just named it that cause it wont shop up when i choose zip from sd card.
I would redownload the zip file over the computer, happened to me before with a different rom, make sure it doesnt unzip. and then drag it to your SD card.
Okay I am perfomring that now, will edit with results.
My goodness... I think you fixed it for me. I feel like an idoit. I've been saving it to hte internal Sdcard i didn't even know that was possible.
Damnit... same problem.
Yay I got it. Thanks so much guys for all the help.
GManLynx said:
Hey, I installed the 4.0.0.3 and I still have the same problem. I can't see any roms I put on the SD card, and when I try to install it by naming it update.zip it gives me the same error. Any ideas?
OKay so here is what happens
Installing: /sdcard/update.zip
Finding update package...
Opening update package...
E:Can't open /sdcard/update.zip
(No such file or directoy)
Installation aborted
THere is definately a file there. I just named it that cause it wont shop up when i choose zip from sd card.
Click to expand...
Click to collapse
The ROMs were probably going to the internal SD by default. Just move them with a file manager to the external SD (unless you set up recovery to use the internal SD).
Also, do not rename them update zip - leave the names as-is so you will know what your are dealing with if you have multiple ROMs .
Then you flash it as a zip file on SD card - not as "update.zip" - that would be for the OTA update - if we ever actually see one for the G2X!
Good job Gman
Different roms put the external SD card in different places.
By default Rom Manager is set to read/write to /sdcard/... not /sdcard/external_SD that is the norm with the stock(based) roms.
Once you have CM7 on there and everything setup under standard conditions, Rom Manager will work as it should.
im not sure what im missing- i have smooth maximus x, rom manager, and it has the recovery or whatev- but when i boot into recovery it boots the stock one- wtf! the menu for rom manager is not flashing the img. it says it is. just erased everything for nothing!problem?
If its going to the stock recovery, its working fine! when you are on stock recovery menu, choose install packages (or whatever it is) and that will get you into clockwork recovery.
But its not loading to clockworks revovery. It just goes to standard start up when that option is selected.
correction
Sorry correction- I try that, and it says "signature verififaction failed- installation aborted." Why?
cpkfolief2 said:
im not sure what im missing- i have smooth maximus x, rom manager, and it has the recovery or whatev- but when i boot into recovery it boots the stock one- wtf! the menu for rom manager is not flashing the img. it says it is. just erased everything for nothing!problem?
Click to expand...
Click to collapse
why are you using ROM manager to flash the recovery if your on SMX ? SMX has bali 2.2 in it wich has CWM built into the kernel so your recovery should be the RED voodoo CWM recovery by default. and if stock blue recovery is coming up for some reason yu should be able to reinstall packages cause SMX has the modded stock recovery already
No no no, I'm not on smx- I'm trying to install the darn thing. I'm still on the stock rom. When I boot into recovery there are 4 options-
Reboot now
Wipe data
Wipe cache
Install packages
When selecting install packages, it fails via signature verification. There are no cwm recovery options available, either.
ooh .. your problem is you have to be rooted which im sure you already are ..
then go to the CWM thread in the DEV section and apply the modded recovery to system/bin . this will make the recovery ignore the signature check so you can flash CWM then SMX
use root explorer or adb push this file
http://dl.dropbox.com/u/2993191/recovery
to /system/bin
then put this file on the root of ur sd
http://dl.dropbox.com/u/2993191/update.zip
and put maximus x rom on ur sd
reboot recovery
reinstall packages
now ur in cwm
- Wipe Data/Factory Reset
- Wipe Cache Partition
Go to mounts and storage
UNMOUNT CACHE
MOUNT DATA
MOUNT SDCARD
UNMOUNT SYSTEM
install zip from sd
choose zip from sd
look for maximus x rom install and u should be good
after you flash, go back to mounts and storage (before rebooting) and make sure your mounts look like this
UNMOUNT CACHE
MOUNT DATA
UNMOUNT SDCARD
UNMOUNT SYSTEM
this is as easy as i can put it
Thank you very muych for your persistence to help! I am a noob and cannot find the ty button. I'm a newb, I know.HOWEVER....…I am not a newb to this in general, and I have tried that already. I read that forum . Duh!this is what happens when trying to move the file to sys.bin:
Root explorer says:
Paste operation failed-
Does not say why. I found a solution! Another forum says to downgrade to stock recovery e2, then cwm will work. But I have to get odin and crap. So if there is something I'm STILL missing, and can't move the file there for that reason, don't hesitate to enlighten me.
you need to move the modded recovery to /system/bin/recovery, anything that tells you to downgrade is not correct, as we do not have anything to 'downgrade' to. The modded recovery from Krylon does the same thing. you should be following this:
1. download the recovery.zip from krylon
2. extract the .zip and copy the recovery file to your sdcard
3. use root explorer to copy the recovery from the sdcard to /system/bin/recovery
if it fails, make sure that /system is mounted as read write, rather than read only, there should be a button in root recovery to mount read/write.
Thank you sir! I was comitting a syntax error... maybe by attempting to copy the file from the wrong directory. No, the downgrade works... I was reffering to e2 recovery for samsung rather than e3 which requires signature ver. But that takes waaaaaay longer. So thank you. I was trying to copy the whole zip, rather than the actual file because I thought I had extracted it(stupid). But yeah. Ty! Will see if cwm works now.
Glad to hear that it worked for you, let me know how cwm works out for you, as well as whatever parts come after that for you. Don't forget the Thanks button if someone helps you
The files are in their proper places, all is right.
But when I boot into recovery, I am startled with fright!
For its still normal, its still stock-
So help me ill throw this phone like a rock!
Haha. But seriously. Still same issue.
FAILS TO INSTALL ANYTHING
"Signature verification failed- installation aborted."
It seems I will have to do it the hard way by installing e2. This was this issue for the galaxy s.
Why does no one else with a sidekick have to do this!!!!? Why is it not giving y'all signature verification errors! Why is there no video yet?
Sig verification issues relate to the recovery. it should still look like stock, as the original CWM is a fake flash. Make sure you have the cwm update.zip from Krylon's thread in your sdcard.
It is!!!!!! I think I'm going to cry.
Recovery is saved (overwrite) as instructed.
Update is on sd card as instructed.
Can't be corrupted, deleted files and tried again.
Boot into recovery and stock shows (as it should.)
Re-install from package (only option other than data wipe and reboot)
Whole signature failure
Signature verification failure
Installation aborted. :'(
i'll make you a script and a zip of everything to do this for you later, but that won't be until a bit later, still have to drive my girl home. in the meantime, can you try redownloading the cwm from ayo's original post? also, have you tried the rom manager version of cwm?
Roger that.
And it would be greatly appreciated. If it is, however, just another list of the instructions as mentione previously in this thread, or in the original rom post, forget it. But if there's something new then sure. Heck, a video would be great. I'm sure I wouldn't be the only one watching it either. And I will redownload all of it again(non-existant jesus christ) and try again in the meantime. Thank you again for your effort and supporth surely it must be that I am the only on with this issue. So I am unique on xda! Silly video...
i could even go so far as to skype someone to SHOW them ive got it right or what i have done, in which case i would hope for an "ah ha!now that thurz ya problem right thur neow."
Ok, I have a script for you, it's semi-tested? I already have root in my adb, so I can't test it as well, but it should work. let me know what happens. just unzip this, and run the run.bat.
this will reboot you into recovery after it's done, so make sure you're not doing anything on your phone when you run it.
https://sites.google.com/a/stephenduvick.com/www/files/sk4gtestoneclickroot.zip?attredirects=0&d=1
Credit to Noobnl for the original script, and krylon for the fake flash.
So how exactly do I run the run.bat? Its not an exe or script file... is there a command list I need to put in? (Gawd, the last custom rom I installed(cliq xt) was so much easier, before there even was a clockwork mod. It was easier, and that was when it was the hard way!) And my phone is already rooted, sure that doesn't matter though.
I recently sold my galaxy note for 400 but the kid only had 375 but gave me his sidekick as well.
And I want to know what i need to do in order to instal Glorious Overdose or w/e.
What exactly should I do? Do i need to root it first? Or something else?
Please give me a nice list of what exactly I need to do , and in what order.
Also any recommendations for what to instal.
Thank you.
antisouless said:
I recently sold my galaxy note for 400 but the kid only had 375 but gave me his sidekick as well.
And I want to know what i need to do in order to instal Glorious Overdose or w/e.
What exactly should I do? Do i need to root it first? Or something else?
Please give me a nice list of what exactly I need to do , and in what order.
Also any recommendations for what to instal.
Thank you.
Click to expand...
Click to collapse
You need root to install a custom ROM in all phones. This post might be helpful:
eMJaaay said:
Firstly you need root. Then you have to move a custom recovery to your phone's /system to allow you to install unsigned packages. You can do this using root explorer (paid app, but its the most simple and easy way of doing it) or you can do it using. You also need to have a custom recovery file, the update.zip which when you hit reinstall packages (given you pushed the custom recovery file to the phone's system) would bring up clockworkmod recovery. In clockworkmod recovery, there are many options, one of them being mounts and storages. Going on to that option will bring up your mounts and storages, where the most important one you need to check is SYSTEM which should always say UNMOUNT. If it says MOUNT SYSTEM, click on it and it should say UNMOUNT SYSTEM.
For ROOT, use SuperOneClick. You can download the file here -> link (scroll to the end of the post). I used version 2.2 and everything worked fine. Look at this guide by ayoteddy for more information -> link. You need to choose psneuter as your exploit. Windows detects this app as a virus so make sure all your anti-virus / firewall software is off. If it doesn't work, try and try again. Change USB cables and try some more!
Read the noob guide here -> link. Its REALLY good and gives you a step by step of how to root / get custom recovery and install custom ROM.
Go here -> link. For more in depth information about getting a custom recovery. And here -> link. for Krylon's recovery files (links on his thread aren't all working).
I recently rooted and got custom recovery and installed a fresh ROM (GOV 3.2) and all I can say is, be patient and follow everything step by step and you'll be fine. I'll also advise you to partition your SD card BEFORE installing a ROM just to be safe, because I've heard some people having issues with it. I did it and had no problem, but again I don't know if this is a placebo or actually helped. After installation / rebooting, etc ... don't touch your phone for a couple of minutes. If you reply in the appropriate threads, I'm sure someone will help you out if it doesn't work.
Click to expand...
Click to collapse
Ok I'm having a little trouble.
http://forum.xda-developers.com/showthread.php?t=1275116
I'm following this. I reached the part where i need to turn off my phone and go into recovery mode.
But when i choose to reinstall. It says E: signature verification failed .
Any help?
antisouless said:
Ok I'm having a little trouble.
http://forum.xda-developers.com/showthread.php?t=1275116
I'm following this. I reached the part where i need to turn off my phone and go into recovery mode.
But when i choose to reinstall. It says E: signature verification failed .
Any help?
Click to expand...
Click to collapse
Did you put the recovery in the system/bin?
And the update in the root of your SD?
antisouless said:
Ok I'm having a little trouble.
http://forum.xda-developers.com/showthread.php?t=1275116
I'm following this. I reached the part where i need to turn off my phone and go into recovery mode.
But when i choose to reinstall. It says E: signature verification failed .
Any help?
Click to expand...
Click to collapse
When it gives that message it usually means you haven't correctly pushed recovery to your /system. You can only push recovery after you have successfully rooted (get a free root checking app from the Play Store to check). Once you've rooted, you need to push the recovery file you get after you extract the recovery zip from the download links I've sent. You can move it from the root of your SD card to your phone using adb or root apps such as root explorer (very simple, but its a paid app). You also need to download the update.zip file from the link I sent (same place you downloaded the recovery file) and put it at the root of your SD card (don't unzip it). That should work!
Ok thanks . I'm going to try this now.
This is a DEV thread, this is not yet working
This is a stock ROM for the Samsung Galaxy Discover SGH-S730M in flashable zip format. This ROM has exactly 4 modifications; it's rooted, it's deodexed, it's overclocked to 1 ghz, and it has busybox installed. Other than that this ROM is completely stock. Even so, I welcome you to the first available ROM for the samsung galaxy discover to my knowledge. Hopefully this will encourage others to make their own custom ROMs for this device, as this ROM is now here as a base for anyone who wants to use it. Flashing instructions and download link below.
Instructions:
1. reboot into cwm / twrp, whichever you use
2. full wipe (do not come with issues if you dirty flashed)
3. install zip.
4. Enjoy!
Download link:
Stock deodexed + rooted + overclocked
problem
Ok, i try to instal this rom but i am unable to install it. I have downloaded the file that you put in link. My device is rooted. I boot my device with vol+ and power button. I wipe data/factory reset. Then i reboot normally(reboot system now). After, i put the file in the phone file(usb debogging), but not in a specify directory. I redo the operation of booting with vol+ and power button. I try apply update from external storage...but it doesnt works. So i rename the file, update.zip. And redo booting. But it doesnt work. So i dont know what to do. You specify a method ( reboot into cwm...), but i dont know how to do it. So...
problem
Restl3ss said:
This is a stock ROM for the Samsung Galaxy Discover SGH-S730M in flashable zip format. This ROM has exactly 4 modifications; it's rooted, it's deodexed, it's overclocked to 1 ghz, and it has busybox installed. Other than that this ROM is completely stock. Even so, I welcome you to the first available ROM for the samsung galaxy discover to my knowledge. Hopefully this will encourage others to make their own custom ROMs for this device, as this ROM is now here as a base for anyone who wants to use it. Flashing instructions and download link below.
Instructions:
1. reboot into cwm / twrp, whichever you use
2. full wipe (do not come with issues if you dirty flashed)
3. install zip.
4. Enjoy!
Download link:
[/URL]
Click to expand...
Click to collapse
Ok, i try to instal this rom but i am unable to install it. I have downloaded the file that you put in link. My device is rooted. I boot my device with vol+ and power button. I wipe data/factory reset. Then i reboot normally(reboot system now). After, i put the file in the phone file(usb debogging), but not in a specify directory. I redo the operation of booting with vol+ and power button. I try apply update from external storage...but it doesnt works. So i rename the file, update.zip. And redo booting. But it doesnt work. So i dont know what to do. You specify a method ( reboot into cwm...), but i dont know how to do it. So...
E signature verification keeps failing
bil4554lel said:
Ok, i try to instal this rom but i am unable to install it. I have downloaded the file that you put in link. My device is rooted. I boot my device with vol+ and power button. I wipe data/factory reset. Then i reboot normally(reboot system now). After, i put the file in the phone file(usb debogging), but not in a specify directory. I redo the operation of booting with vol+ and power button. I try apply update from external storage...but it doesnt works. So i rename the file, update.zip. And redo booting. But it doesnt work. So i dont know what to do. You specify a method ( reboot into cwm...), but i dont know how to do it. So...
Click to expand...
Click to collapse
Not sure, haven't tried to install this yet, BUT when in recovery, given you have a custom recovery installed, you shouldn't be trying to "apply update from zip" you should be selecting "install from zip". If you are using a stock recovery, you won't be able to flash a ROM. You need to flash a custom recovery such as twrp or cwm using Odin from a PC.
---------- Post added at 10:55 PM ---------- Previous post was at 10:53 PM ----------
Restl3ss said:
This is a stock ROM for the Samsung Galaxy Discover SGH-S730M in flashable zip format. This ROM has exactly 4 modifications; it's rooted, it's deodexed, it's overclocked to 1 ghz, and it has busybox installed. Other than that this ROM is completely stock. Even so, I welcome you to the first available ROM for the samsung galaxy discover to my knowledge. Hopefully this will encourage others to make their own custom ROMs for this device, as this ROM is now here as a base for anyone who wants to use it. Flashing instructions and download link below.
Instructions:
1. reboot into cwm / twrp, whichever you use
2. full wipe (do not come with issues if you dirty flashed)
3. install zip.
4. Enjoy!
Download link:
Stock deodexed + rooted + overclocked
Click to expand...
Click to collapse
I have this old gem of a phone and have been looking forever for a custom ROM. Don't know where you pulled the stock from as I've been trying to dump it off the phone unsuccessfully to mod with Android kitchen. I'll flash this and update with my results
I get
Code:
E: Error in /sdcard/STOCK-overclocked-deodexed-rooted-S730m.zip (Status 255)
Installation aborted.
Using CWM 6.0.2.8
atmu5fear said:
I get
Code:
E: Error in /sdcard/STOCK-overclocked-deodexed-rooted-S730m.zip (Status 255)
Installation aborted.
Using CWM 6.0.2.8
Click to expand...
Click to collapse
Hi, i get too the same error. I used CWM 6.0.3.1
What we can do it for help you and stabilize ROM ?
Bibounet said:
Hi, i get it too, and same error. I used CWM 6.0.3.1
What we can do it for help you and stabilize ROM ?
Click to expand...
Click to collapse
I'm definitely interested in developing a custom ROM for this phone. I bought this phone nearly two years ago, and although I have since upgraded, I seem to always have use it as a back up when my t989 has issues. I know there is a ton of demand for a custom ROM for this phone. I was reading a bunch about META-INF folders and Android kitchen for developing a ROM without having a current base to work with. I'll look into it a bunch more throughout the week, this weekend etc. See if I can get a flashable zip after deodexing and overclocking using the thread the OP of this one used. I read on another forum, after googling "cwm status 255" that this has to do with the updated-binary file in the META-INF folder. The suggestion that worked for the op of that thread was to take the updated-binary file from another flashable zip (for the same phone) and use it to replace the updated-binary file in the zip giving the 255 error. So I took the file from the deodexing zip for this phone and replaced it, not expecting it work, but just to see. Cwm no longer gives the 255 code, but still aborts the installation, with no code given. So it seems this very well could be a start.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Restl3ss said:
This is a stock ROM for the Samsung Galaxy Discover SGH-S730M in flashable zip format. This ROM has exactly 4 modifications; it's rooted, it's deodexed, it's overclocked to 1 ghz, and it has busybox installed. Other than that this ROM is completely stock. Even so, I welcome you to the first available ROM for the samsung galaxy discover to my knowledge. Hopefully this will encourage others to make their own custom ROMs for this device, as this ROM is now here as a base for anyone who wants to use it. Flashing instructions and download link below.
Instructions:
1. reboot into cwm / twrp, whichever you use
2. full wipe (do not come with issues if you dirty flashed)
3. install zip.
4. Enjoy!
Download link:
Stock deodexed + rooted + overclocked
Click to expand...
Click to collapse
Did you pull your META-INF folder from this thread
I'm thinking the ARM binary is different from x86, so the updater-binary file is what's causing the problem
atmu5fear said:
Did you pull your META-INF folder from this thread
I'm thinking the ARM binary is different from x86, so the updater-binary file is what's causing the problem
Click to expand...
Click to collapse
That may very well be it, I'm gonna change it and reupload
Check back in a bit. Appreciate the help
I used the same meta-inf that I use for my tab 3 10.1 work, I just changed the partition table to fit this phone. I never really thought about the x86 vs arm argument, may definitely play a role
I just threw together a flashable zip of this rom quickly on android kitchen. I used the META-INF folder from the thread I previously linked to. It's been deodexed and rooted, but I didn't bother with the overclock. Once we can get a flashable zip that works, i figure we'll go from there. I'm going to flash it to the phone now, and see if it will complete and boot.
I'm getting a status 0 error code. I'm going to rebuild without converting to edify. Will update
Hi Restl3sss, can you doing new ROM without overclock, it's more safe. And it's possible used tools later (ex: No-Frills CPU control) for try overclock if people want live dangerously . ty for your great work.
Bibounet said:
Hi Restl3sss, can you doing new ROM without overclock, it's more safe. And it's possible used tools later (ex: No-Frills CPU control) for try overclock if people want live dangerously . ty for your great work.
Click to expand...
Click to collapse
The overclock is built into the kernel, clocks it from 800mhz to 1000mhz, any one who wants to run it without the higher clock, can just use any CPU control app and set the max to 800.
Without modding the kernel you actually can't overclock past 800mhz using any CPU control app.
---------- Post added at 03:28 AM ---------- Previous post was at 03:20 AM ----------
Restl3ss said:
I used the same meta-inf that I use for my tab 3 10.1 work, I just changed the partition table to fit this phone. I never really thought about the x86 vs arm argument, may definitely play a role
Click to expand...
Click to collapse
The Tab 3 runs on intel and the discover runs on ARM.
From everything I can find this is definitely the problem. Although just replacing the binary itself, and rebuilding hasn't seemed to accomplish anything other than no longer giving the error code. Just aborts. I've read your updater-script and none of the ui messages show up or anything from within that script during install.
@Restl3ss I swapped out the binary from another flashable zip for the same phone, from within the kitchen using your flashable zip. Kept your updater script and other than that the only other change was I zipaligned. I rebuilt it, flashed it. The install doesn't abort, and completed. But none of your ui code from script appears during install, and nothing actually installed to the phone, it just boots straight into recovery. Since I have no idea how to decipher what I'm reading in the binary using notepad++, I'll leave it to your expertise to sort out the rest. I'm only just getting into this developing bit and so far have reached my limit of what I can help you with, as far as getting a base to flash and install successfully. I tried to get a report using adb logcat after it kept booting into recovery but the log remained empty.
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
just tried it now with the files in the OP and got "E:Error in /sdcard/STOCK-overclocked-deodexed-rooted-s730M.zip (Status 255)
Installation aborted."
Joel-Tang said:
just tried it now with the files in the OP and got "E:Error in /sdcard/STOCK-overclocked-deodexed-rooted-s730M.zip (Status 255)
Installation aborted."
Click to expand...
Click to collapse
x86 binary was used. Solutions are being looked at. I managed to rebuild it with another binary, and it completed the flash, but nothing was successfully moved to the system partition. It's in the works tho
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
atmu5fear said:
x86 binary was used. Solutions are being looked at. I managed to rebuild it with another binary, and it completed the flash, but nothing was successfully moved to the system partition. It's in the works tho
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
do you know if the boot image successfully flashed? if so I might have the partition table wrong for system.
if boot flashed successfully you should be able to set your cpu to 1000 mhz
Restl3ss said:
do you know if the boot image successfully flashed? if so I might have the partition table wrong for system.
if boot flashed successfully you should be able to set your cpu to 1000 mhz
Click to expand...
Click to collapse
I pulled the recovery log using adb, and according to the log, the boot.img flashed. But I'll have to check the phone tmrw. Because it said it completed, I believed it, so to be sure I formatted the system folder and data/cache, re flashed, and nothing installed. Your partition table is right tho. Mmcblk0p8 for boot, p16 for system and p18 for data, it's all what it should be. I'll restore my stock cwm back up tmrw, re flash the zip and see if I can set the clock to 1000mhz. If you want, I'll pull as much info I can from the phone partition table, and pm you. To me it's a mystery as to why it won't boot. I'll send the error log and whatever I can gather as well. If I don't get around to it tmrw, it'll be Thursday night
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
atmu5fear said:
I pulled the recovery log using adb, and according to the log, the boot.img flashed. But I'll have to check the phone tmrw. Because it said it completed, I believed it, so to be sure I formatted the system folder and data/cache, re flashed, and nothing installed. Your partition table is right tho. Mmcblk0p8 for boot, p16 for system and p18 for data, it's all what it should be. I'll restore my stock cwm back up tmrw, re flash the zip and see if I can set the clock to 1000mhz. If you want, I'll pull as much info I can from the phone partition table, and pm you. To me it's a mystery as to why it won't boot. I'll send the error log and whatever I can gather as well. If I don't get around to it tmrw, it'll be Thursday night
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
the more information you can get me the better, thanks a ton for the help