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.
Related
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.
I'm trying to get my own ROM working, and it currently locks up in the middle of booting. Here's logcat (had to use pastebin):
http://pastebin.com/SwFCJzDH
dementio said:
I'm trying to get my own ROM working, and it currently locks up in the middle of booting. Here's logcat (had to use pastebin):
http://pastebin.com/SwFCJzDH
Click to expand...
Click to collapse
there are a few things which fail during your boot up process. the only major issue I see is the signature mismatch. this seems to prevent the system from loading a required apk file which later on is the source of the crash .. at least that is my guess.
once you wipe the settings file in the /data partition which stores the signatures of each .apk file, they should process correctly. i think the exact file is /data/system/packages.xml which stores signatures for .apk files.
it is really hard to say with 100% confidence no information is provided as to what you've changed to get your "own ROM", but I would start by working on the signature mismatch issues.
hope that helps!
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
So, like an idiot I wiped/data/system to install a new Rom and didn't double check to make sure the file was good. I can get into ClockworkMod no problem but I have my nandroid and various other downloaded Roms on my microsd card. I'm trying to adb push a Rom while in Clockwork but it keeps failing. What am I doing wrong? Tips please? Thanks much!
Bump, Bump
What I'm getting is "Protocol Failure" every time I try to push a Rom zip to my sdcard. Thoughts?
Is it the size of the file? I just successfully pushed a smaller image file.
After much frustration and trial and error, I got this fixed and back up and running. Ended up having a driver issue with ADB. Master Zen's flash script came in real handy and I highly recommend it if any of you run into a similar problem!
So a quick catch up is needed: I accidentally wiped my system in TWRP recovery. I have now been able to push the ROM back to TFP via ADB. All seems to be ok.
Issues:
1) When flashing the rom zip I got a failed message after TWRP checked partitions, anyone know what to do with this?
2) TWRP only will allow me to install from /data directory, is this normal and will this hinder rom flash?
Any insights or knowledge of existing threads with answers would be really appreciated. Thanks for reading this too btw, I'm new so anything will be helpful.
Thanks again.
tstern0112 said:
So a quick catch up is needed: I accidentally wiped my system in TWRP recovery. I have now been able to push the ROM back to TFP via ADB. All seems to be ok.
Issues:
1) When flashing the rom zip I got a failed message after TWRP checked partitions, anyone know what to do with this?
2) TWRP only will allow me to install from /data directory, is this normal and will this hinder rom flash?
Any insights or knowledge of existing threads with answers would be really appreciated. Thanks for reading this too btw, I'm new so anything will be helpful.
Thanks again.
Click to expand...
Click to collapse
I haven't personally used TWRP but I've seen in the buglist that sometimes it could mess up with particularly large ROM files. However, I have not tested this firsthand because I know my prime is sort of like a moribund insect; you touch it, it dies.
Sent from my tf9001 with XDA XD.
tstern0112 said:
So a quick catch up is needed: I accidentally wiped my system in TWRP recovery. I have now been able to push the ROM back to TFP via ADB. All seems to be ok.
Issues:
1) When flashing the rom zip I got a failed message after TWRP checked partitions, anyone know what to do with this?
2) TWRP only will allow me to install from /data directory, is this normal and will this hinder rom flash?
Any insights or knowledge of existing threads with answers would be really appreciated. Thanks for reading this too btw, I'm new so anything will be helpful.
Thanks again.
Click to expand...
Click to collapse
The /data directory is the only partition I have ever flashed a ROM from. /data is just internal memory Where does ADB push put the file by default, at the root?
It sounds like you may need to re-partition your device. I guess when you wipe /system in twrp, it doesn't create a new /system partition? Or maybe it wiped everything? The TWRP thread can probably answer these questions, but my guess is that you just need to create a new partition(s) or if the partitions are okay just adb push the file to the right spot. I've never done that before in ADB, hopefully it isn't complicated? Good luck man, ask the Team Win thread if you have questions, I bet they can help!
Komodo Rogue said:
The /data directory is the only partition I have ever flashed a ROM from. /data is just internal memory Where does ADB push put the file by default, at the root?
It sounds like you may need to re-partition your device. I guess when you wipe /system in twrp, it doesn't create a new /system partition? Or maybe it wiped everything? The TWRP thread can probably answer these questions, but my guess is that you just need to create a new partition(s) or if the partitions are okay just adb push the file to the right spot. I've never done that before in ADB, hopefully it isn't complicated? Good luck man, ask the Team Win thread if you have questions, I bet they can help!
Click to expand...
Click to collapse
Thanks so much.. Yeah I've been reading up on this and of course there's always more to the story haha I talked to an old linux engineer and he agrees with you that there is probably something going on with partitions. I'll head over to TWRP and see if they have any ideas. Thanks for your help.