Used dsixdas Rom kitchen.
Built my own Rom using rogers stock RUU
starts to flash, then I get, error in sd card installation aborted
(status 0)
the last thing it was doing
minzip: extracted file "system/cuE:Error in /sdcard/marksrom
any takers??!!
Thanks guys
markdexter said:
Used dsixdas Rom kitchen.
Built my own Rom using rogers stock RUU
starts to flash, then I get, error in sd card installation aborted
(status 0)
the last thing it was doing
minzip: extracted file "system/cuE:Error in /sdcard/marksrom
any takers??!!
Thanks guys
Click to expand...
Click to collapse
What type of zip file is it?
its just the one that dsxidas tool spits out, although I did notice some differences.
If i click on the Rom.zip file, go to properties, then security. The only 2 that where check-marked was "modify" and "read & execute" So i compared that to a Rom that works on my device and noticed that in that same box they where all checked. - full control
modify
Read & execute
Read
Write
Special permissions
I changed those in my Rom so there all checked,however cant flash till tonight.
Just wondering if that could possibly be an, or the, issue
Not sure how to check what type of .zip file it is??
markdexter said:
Used dsixdas Rom kitchen.
Built my own Rom using rogers stock RUU
starts to flash, then I get, error in sd card installation aborted
(status 0)
the last thing it was doing
minzip: extracted file "system/cuE:Error in /sdcard/marksrom
any takers??!!
Thanks guys
Click to expand...
Click to collapse
markdexter said:
its just the one that dsxidas tool spits out, although I did notice some differences.
If i click on the Rom.zip file, go to properties, then security. The only 2 that where check-marked was "modify" and "read & execute" So i compared that to a Rom that works on my device and noticed that in that same box they where all checked. - full control
modify
Read & execute
Read
Write
Special permissions
I changed those in my Rom so there all checked,however cant flash till tonight.
Just wondering if that could possibly be an, or the, issue
Not sure how to check what type of .zip file it is??
Click to expand...
Click to collapse
Lol .. the "check boxes" you're referring to only indicate the access permissions for the specific .zip file. When in recovery mode, everything runs as root. If there is any read permission on the file, recovery should be able to acces it without any issues. Further, you mentioned above the recovery was in the process of flashing the file indicating the recovery has no issues accessing the file.
If the recovery has no issues accessing the file, there shouldn't be any issues with the specific permissions of the ROM .zip file on that specific file system in recovery mode.
As a ROM developer, the next step to troubleshooting and understanding errors when flashing a ROM is by becoming familiar with the custom recovery error log.
The custom recovery shows very limited information on the display, but in the log shows much more detail. The logs are generally kept at /tmp/recovery.log and /cache/recovery.log.
The best process is to process the .zip file and when the recovery errors, open up the recovery log. If you can paste back here the few lines before the error occurred including the error we can start working on the issue.
We might need a copy of the .zip file to match up with the recovery log to understand how much progress was made in order before the error occured.
The only other common place for ROM flashing errors when developing a ROM will be in the updater-script file. Might need a copy of this posted also.
In summary, the two most common places for issues occur either in the file name/structure of the .zip or in the updater-script.
Hope that helps! Good luck!
joeykrim said:
Lol .. the "check boxes" you're referring to only indicate the access permissions for the specific .zip file. When in recovery mode, everything runs as root. If there is any read permission on the file, recovery should be able to acces it without any issues. Further, you mentioned above the recovery was in the process of flashing the file indicating the recovery has no issues accessing the file.
If the recovery has no issues accessing the file, there shouldn't be any issues with the specific permissions of the ROM .zip file on that specific file system in recovery mode.
As a ROM developer, the next step to troubleshooting and understanding errors when flashing a ROM is by becoming familiar with the custom recovery error log.
The custom recovery shows very limited information on the display, but in the log shows much more detail. The logs are generally kept at /tmp/recovery.log and /cache/recovery.log.
The best process is to process the .zip file and when the recovery errors, open up the recovery log. If you can paste back here the few lines before the error occurred including the error we can start working on the issue.
We might need a copy of the .zip file to match up with the recovery log to understand how much progress was made in order before the error occured.
The only common place for ROM flashing errors when developing a ROM will be in the updater-script file. Might need a copy of this posted also.
In summary, the two most common places for issues occur either in the file name/structure of the .zip or in the updater-script.
Hope that helps! Good luck!
Click to expand...
Click to collapse
Amazing answer, thank you so much for taking your time with me, appreciate it, I'll try the recovery log, see what I get, as you can tell I'm pretty new to this, everyone has to start somewhere!
Thanks again buddy
Sent from my HTC EVO 3D X515a using xda premium
Related
Hey everybody,
I apologize in advance if this post is a duplicate but I have tried searching for a solution and still lost. Here is what I did: I used the Odin to restore stock rom, then re-rooted using the one click method, then downloaded a rom from theunlockr.com, then used rommanger to install it. My rom has gave me no problems but now when I try to reboot into recovery to install something else(Like the 2.3 keyboard or a lagfix) i get this error:
E:Can't open /sdcard/update.zip
(No such file or directory)
Installation aborted
Can someone please help me? Thank you, BTW I have a Samsung Vibrant running axura-froyo-rom
I had the same problem too.
When I put update.zip at the root directory of internal memory... once I restart the phone (not get into the recovery mode), this file is missing / dissapear. So... I always got this message too :
E:Can't open /sdcard/update.zip
(No such file or directory)
Installation aborted
anybody can help us pleaseeeeee
I got my phone to factory settings using odin then i rerooted my phone and flashed the same custom rom back on and it worked. Try reflashing your phone, backup first, might work.
CarlosCruz15 said:
I got my phone to factory settings using odin then i rerooted my phone and flashed the same custom rom back on and it worked. Try reflashing your phone, backup first, might work.
Click to expand...
Click to collapse
thanks for reply.
how to use factory setting using odin ? tick the "re-partition" box ?
can you explain to us step by step please ?
I'm so frustated
Did you guys delete the update.zip after rooting?
If you do not see
sdcard/update.zip using a file manager, download the update.zip from my noob guide, move it to internal memory and then try to flash CWR.
Also, look in the bottom of the noob guide (last few posts) for a solution to a RECENT issue with CWR... I assume whatever Koush did in the last update is causing this problem? BUT, there is a fix posted by another XDA user... just a matte of downloading the file and putting it in the right place.
mikomikos said:
thanks for reply.
how to use factory setting using odin ? tick the "re-partition" box ?
can you explain to us step by step please ?
I'm so frustated
Click to expand...
Click to collapse
check out this link...its what i used
http://forum.xda-developers.com/showthread.php?t=734475
listen to s15's post....he knows what he is talking about. i followed his noob guide in his sticky and everythign worked perfectly! his vids are also very helpful. one thing i have found that works a lot as well is if you download ROM Manager from the market and then click on "fix permissions"... don't know if this would help in this situation but i have had that fix weird stuff.
s15274n said:
Did you guys delete the update.zip after rooting?
If you do not see
sdcard/update.zip using a file manager, download the update.zip from my noob guide, move it to internal memory and then try to flash CWR.
Also, look in the bottom of the noob guide (last few posts) for a solution to a RECENT issue with CWR... I assume whatever Koush did in the last update is causing this problem? BUT, there is a fix posted by another XDA user... just a matte of downloading the file and putting it in the right place.
Click to expand...
Click to collapse
yeah this, the update.zip is ESSENTIAL for your phone to run the clockwork recovery, it stores all the things needed, and when you click "reinstall packages" your system goes in update.zip and looks for what to boot up and finds CWR and boots that so you see that screen.
Don't delete it if you did.
i have tried numerous times to root,but cant seem to get update.zip file in right place,can anyone help? thanks. challenged noob!!
Rayn1328 said:
i have tried numerous times to root,but cant seem to get update.zip file in right place,can anyone help? thanks. challenged noob!!
Click to expand...
Click to collapse
When you usb into your phone it needs to be in the initial area of your sdcard.
You might have a bad update.zip file. Two things, verify the md5(if possible) from where you got it and check the properties and make sure it's not names update.zip.zip. The later is very common.
Try this method too btw, when I Odin back to stock I always use this one to root again. Follow the 'Automated Method' area.
http://forum.xda-developers.com/showthread.php?t=786877
you will need these drivers AND set your phone to debugging mode (settings/applications/development check USB debugging).
http://forum.xda-developers.com/showthread.php?t=728929
hey all,
Newbie here trying to flash a ROM, i am running into this same error, i have tried everything here and i have one question (might be a stupid question) but my root sd folder is called SD/, not SDCard/ ...is this a path error?
Please note it file must be in the internal card, not the SD card.
This step drove me nuts.
"2. Copy the update.zip (and the ROM) to the INTERNAL SD (not the external SD Card). sdcard/ " (http://forum.xda-developers.com/showthread.php?t=732458)
i ran into the same problem...how do i get from 3e to CWR?
here's what's shown in my vibrant directory: Android, DCIM, external_sd, LOST.DIR
i dont have an internal sd (the card) so it's not shown?
the path i got error on: /mnt/internal_sd/update.zip
1. when i tried to "reinstall packages" i keep getting the error that the update.zip file cant be found. should i create a folder for it or something? i think it's a matter of pathing but i cant find out the right place to put the file...(to get from 3e to CWR)
2. i see people suggesting boot with odin or sth like that...does that solve my problem and how do i do that?
janthe6th said:
i ran into the same problem...how do i get from 3e to CWR?
here's what's shown in my vibrant directory: Android, DCIM, external_sd, LOST.DIR
i dont have an internal sd (the card) so it's not shown?
the path i got error on: /mnt/internal_sd/update.zip
1. when i tried to "reinstall packages" i keep getting the error that the update.zip file cant be found. should i create a folder for it or something? i think it's a matter of pathing but i cant find out the right place to put the file...(to get from 3e to CWR)
2. i see people suggesting boot with odin or sth like that...does that solve my problem and how do i do that?
Click to expand...
Click to collapse
You definitely have an internal sd card. Use Astro file manager or something similar and put update.zip on the root of internal sd card, meaning not in a folder. It should look like sdcard/update.zip. If you are having the 3e mismatch recovery issue read this http://forum.xda-developers.com/showthread.php?t=833423
Sent from my SGH-T959 using Tapatalk 2
i go to the link that you linked and ran the script. then i download the update.zip file at the noob guide with a slimbean 4.2.2 rom and addons. this time i would just put it in the root folder (technically not in any folder). when i try to reinstall packages, the screen shows that it is "replacing stock recovery with clock work recovery"... but then it would go back to the 3e.
so...i guess putting the files in the root folder is correct. but someone it still wont let me get tot CWR...
janthe6th said:
i go to the link that you linked and ran the script. then i download the update.zip file at the noob guide with a slimbean 4.2.2 rom and addons. this time i would just put it in the root folder (technically not in any folder). when i try to reinstall packages, the screen shows that it is "replacing stock recovery with clock work recovery"... but then it would go back to the 3e.
so...i guess putting the files in the root folder is correct. but someone it still wont let me get tot CWR...
Click to expand...
Click to collapse
You have to reinstall packages twice for it to work properly. It is normal to not work the first time, just reinstall packages again and you should be good to go. If you keep having issues you should just flash back to stock 2.1 with Odin and go from there.
Sent from my SGH-T959 using Tapatalk 2
Keep getting the following message for every ROM I attempt to install:
-- Install /sdcard/download...
Finding update package...
Opening update package...
E: Can't open /tmp/sideload/package.zip
(bad)
Please anyone, whats my resolution to this matter. Thanks in advance!
HackDPlanet said:
Keep getting the following message for every ROM I attempt to install:
-- Install /sdcard/download...
Finding update package...
Opening update package...
E: Can't open /tmp/sideload/package.zip
(bad)
Please anyone, whats my resolution to this matter. Thanks in advance!
Click to expand...
Click to collapse
What version of TWRP are you on?
My only other thought would be that the roms aren't downloading correctly for some reason or another, check the size of the file downloaded to the actual size its supposed to be.
Im using the latest version of TWRP. I flashed the following .img:
recovery-twrp-shooter-1.0.2.img
HackDPlanet said:
Im using the latest version of TWRP. I flashed the following .img:
recovery-twrp-shooter-1.0.2.img
Click to expand...
Click to collapse
My guess is a bad download then, possibly you aren't getting the whole file when you download it?
I'm redownloading see if thats the fix. I initially downloaded directly to phone. I am downloading to computer now and will drop into SD card and see what happens from there. Cross your fingers!!!!!
HackDPlanet said:
I'm redownloading see if thats the fix. I initially downloaded directly to phone. I am downloading to computer now and will drop into SD card and see what happens from there. Cross your fingers!!!!!
Click to expand...
Click to collapse
With the size of the roms for the 3D I would highly recommend always just doing it on your computer. I almost guarantee that is your issue, not 100% sure but not just a shot in the dark.
HackDPlanet said:
I'm redownloading see if thats the fix. I initially downloaded directly to phone. I am downloading to computer now and will drop into SD card and see what happens from there. Cross your fingers!!!!!
Click to expand...
Click to collapse
NO GO!?!?! I wiped and attempted again and nothing. SAME ERROR MESSAGE. Quick question: The background image when choosing to zip to flash, is it a box with question marks? Just wondering maybe something is wrong with my tmrp.
I dont get it and dont know what to do. Should I push the root .zip again to see what happens, if anything?
Please HELP! SOS SOS SOS SOS SOS
All XDA gurus, I call for your powers! I have read the in and outs of the EVO 3D pages and have not found one single person running into the same issue.
HackDPlanet said:
NO GO!?!?! I wiped and attempted again and nothing. SAME ERROR MESSAGE. Quick question: The background image when choosing to zip to flash, is it a box with question marks? Just wondering maybe something is wrong with my tmrp.
I dont get it and dont know what to do. Should I push the root .zip again to see what happens, if anything?
Please HELP! SOS SOS SOS SOS SOS
All XDA gurus, I call for your powers! I have read the in and outs of the EVO 3D pages and have not found one single person running into the same issue.
Click to expand...
Click to collapse
Try running the PC86IMG.zip from your bootloader instead of pushing the img file for TWRP. My only guess is that for some reason or another it is something to do with the recovery.
Could you provide me some directions really quick, detailed? Just want to make sure i get this right. Ya dig lol. Man I am so discouraged right now. Im missing my Hero lol. Ouch no, i didnt just say that. nevermind
I have the following directions:
Install as a Flashable Zip? [RECOMMENDED]
1.Download flashable zip from the OP and rename it "PG86IMG.zip" (without the quotes)
2.Place in the root of the sdcard
3.Power off phone (make sure you turn off hot boot or pull the battery when it's off)
4.Power on the phone holding power and volume down
5.Follow the prompts to flash it
6.Delete .zip (PG86IMG.zip) after booting
7.Enjoy
I have read over and over that you will be "prompted" to flash as update or whatever, but I never get this option. I basically just load into hboot. Am I missing a step here or what?
HackDPlanet said:
Could you provide me some directions really quick, detailed? Just want to make sure i get this right. Ya dig lol. Man I am so discouraged right now. Im missing my Hero lol. Ouch no, i didnt just say that. nevermind
Click to expand...
Click to collapse
Alright, I am just gonna copy the how to from the TeamWin thread but this should be alot easier than doing the push of the .img file.
Install as a Flashable Zip? [RECOMMENDED]
Download flashable zip from the OP and rename it "PG86IMG.zip" (without the quotes)
Place in the root of the sdcard
Power off phone (make sure you turn off hot boot or pull the battery when it's off)
Power on the phone holding power and volume down
Follow the prompts to flash it
Delete .zip (PG86IMG.zip) after booting
Enjoy
Click to expand...
Click to collapse
Here is the zip: http://api.viglink.com/api/click?fo...er-1.0.2.zip&jsonp=vglnk_jsonp_13125241678211
Just read what you posted before I posted that. If you are not being prompted for an update then the file isn't renamed properly. You don't need to add .zip when you rename it because it is already a zip file.
Ok, I made sure the file name was correct. When loading, it slowed up on that .zip but never prompted me to do anything?
Oh and still getting the same message when trying to install ROM. It was different this time around with the slowing up when booting like it did something but it never prompted me to do any action. I really dont know man, I am clueless.
HackDPlanet said:
Oh and still getting the same message when trying to install ROM. It was different this time around with the slowing up when booting like it did something but it never prompted me to do any action. I really dont know man, I am clueless.
Click to expand...
Click to collapse
Hmmm so you did update the recovery or still not able to?
Second guessing myself now, root of the SDcard is just anywhere in the SDcard not within a folder, correct? Just want to make sure, trying to over all my bases. Jeeeze, I did not have this type of trouble with my Hero. I am feeling like a Noob but this is challenging me.
It did not prompt me to update the recovery. It simply slowed down during the .zip verification process when it was booting and than it kept going. Nothing more, no prompt for my action to update.
HackDPlanet said:
It did not prompt me to update the recovery. It simply slowed down during the .zip verification process when it was booting and than it kept going. Nothing more, no prompt for my action to update.
Click to expand...
Click to collapse
The file just needs to be placed on the SD plain and simple no folders etc.
I still think this is a naming issue because it should prompt you to press the volume up to update. Rename the file to just PC86IMG and see if that works.
Oh and the renaming part is case sensitive.
Ok, I read what it said "wrong zipped image" when the process slowwed down during the boot up
And I named it only "PC86IMG". and than when i look at the file through AstoZip than the it shows as "PC86IMG.zip" The ending (.zip) automatically is added.
Does anyone know how to fix a e:/tmp/sideload has perms 40755 issue?
I was flashing a rom and got stuck there.
Any help will be appreciated.
Thank you!
Whenever I used to get that I'd pull battery do a full wipe and try again. Later I flashed my recovery again and the problem has stopped entirely. I flash ROMs as much as 5 times a day (on a good day).
proxhack said:
Does anyone know how to fix a e:/tmp/sideload has perms 40755 issue?
I was flashing a rom and got stuck there.
Any help will be appreciated.
Thank you!
Click to expand...
Click to collapse
I haven't seen this error come up before on the q&a board, but I very well could have missed it.
The recovery outputs the details around the error in a /tmp/recovery.log file. Once the error occurs, its best to check this file, /tmp/recovery.log for the details around the error. In order to really troubleshot the specific issue, we'd need a copy of the /tmp/recovery.log and the .zip file being loaded.
Sorry that doesn't directly answer the question, but it will lead to the best technical solution possible! Hope that helps provide some light around recovery .zip flashing troubleshooting!
I just got this trying to install sick sense rom. There is no log file in tmp/
MikeC84 said:
I just got this trying to install sick sense rom. There is no log file in tmp/
Click to expand...
Click to collapse
whenever the recovery first boots, it will create a log file in /tmp/recovery.log. this file will get wiped on reboot. the best time to pull and examine the /tmp/recovery.log file is right after the recovery throws the installing error.
if, for some odd reason, there is a recovery.log in /tmp, you can also try checking /cache/recovery.log.
if you can post the file contents up we can help troubleshoot!
i know i've seen people post back, after attempting to flash 2-3 times the error would disappear. i also know i've seen people post that re-flashing the custom recovery, or flashing an updated version helps clear the issue.
hope that helps!
I had this problem too after trying to flash Viper-Rom RC2 version 4. The problem did not occur during the first installation, but after realizing I forgot to format the data partition, and going back and formatting everything and trying the install again, I had the perms 40755 issue. It appears that having a rom that tweaks the file system and permissions will cause this issue on occasion. After pulling the battery like triscuit suggested, it worked just fine. Unfortunately I scoured the entire phone for a recovery.log file and it was nowhere to be found. We may not have a technical reasoning for this issue exactly, but triscuit's workaround appears to take care of the problem.
So I was trying to package a rom and let the kitchen create the meta-inf folder along with the updater-script but the problem is that it's not using the specified mount points.
My phone isn't supported in the kitchen so I had to make a file in the edify_defs folder for my phone. I did all the right steps, I renamed the file to that of the ro.produc.device, used the template and made the necessary edits using notepad ++, and checked the file for any incorrect syntax yet after all that, the kitchen isn't using the mount points I put but instead uses the default value "mount("MTD", "system", "/system")".
Any help?
bump
Don't rely on kitchen's mount. Instead, use the update binary of a working zip for your device and edit the updater-script manually to make it work.
iZLeeP said:
Don't rely on kitchen's mount. Instead, use the update binary of a working zip for your device and edit the updater-script manually to make it work.
Click to expand...
Click to collapse
Yah, the thing is there are no roms for my device not even a stock rom. This is the reason why I'm trying to learn how to build a rom.
Anyways, I got the kitchen to detect the mount points. Turns out i had put the kitchen in the wrong directory. Made the zip flash correctly but now i encountered a new problem. After flashing the zip, the interface on my phone becomes really small. It's like my display went into tablet mode. Any idea on this?
black_fire21 said:
Yah, the thing is there are no roms for my device not even a stock rom. This is the reason why I'm trying to learn how to build a rom.
Anyways, I got the kitchen to detect the mount points. Turns out i had put the kitchen in the wrong directory. Made the zip flash correctly but now i encountered a new problem. After flashing the zip, the interface on my phone becomes really small. It's like my display went into tablet mode. Any idea on this?
Click to expand...
Click to collapse
What's your device and android version? Much better if you could post on your device's specific thread.
It's a local phone called starmobile quest, running jellybean. Sadly, there is absolutely no support for the device not even from the manufacturers. There are no developers either. The only thing we have is root and cwm.
I have followed every step of this turtorial: http://forum.xda-developers.com/showthread.php?t=2746044
Not sure what is going on. When I try to flash i get this message: Skipping MD5 check: no MD5 file found (next line in red) Failed to map file '/externel_sd/Root Stuff/TestRom.zip (next line in red) Error installing zip file '/externel_sd/Root Stuff/TestRom.zip
Just out of curiosity I unzipped a known working ROM and rezipped it with winrar and get the same error with a known working rom. So it is something in the zipping process that is making it no work, I just dont know what. Any help is appreciated.
Note I have also tried Z-zip to zip my rom and get the same for my custom rom and also a known working rom that I extract and repack.
Josh