Hi,
I have an issue with my Desire 610, because it didn't want to start, i clicked by mistake fix permissions in twrp.
What can I do?
Tried installing new rom via zip ... failed. Any ideas?
Bump!
There's two permission fixes dialogues. Did you fix symlinks (which is what normally would brick you) or the actual permission fix?
If it was the latter, the only reason you'd brick is if the ROM archive contained improper files for your device.
So, is there a way to fix this?
Related
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, 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!
Hello XDA can somebody help this bloody fool?
I was following the directions of this thread trying to install notifications toggles to my phone. Used root explorer. However, l changed the permissions on the wrong file or folder, it seems, as the phone just displays the logo and reboots, caught in a loop.
What files and folders has to have which permissions? How can I change them if I can't boot my phone? I don't have any mod other than Root, as this was the first I was trying to use, as I have to have better access to the toggles.
Any ideas? Some command prompt commands? Guide?
Sorry, I think I got it now.
Flashed the phone with Flashtool. Wised everything, but it's working now.
Hi guys!
I was hoping one of you could help me.
Yesterday i modified a build.prop file on my NextBook EBM8000ND (Next800T) tablet, causing it to get stuck in a bootloop every time it's turned on. I've been searching the Internet all day long but it's hard to find support when you have a device which no one in the world uses . It was rooted but I did a factory reset hoping that it would fix it. It didn't and now it's also unrooted. I tried to make a custom update.zip with the backup of the original build.prop file but the stock recovery simply refuses to load any update file. It always stops at verification. I used 7zip with store option. I tried signing the zip, I even edited the updater script to only print some text on the screen but the recovery still wouldn't load it. I tried to find a way to install CWM using sdcard but with no luck. When i tried to use ADB in recovery the device says: "failed to open driver control: No such file or directory". It might be worth mentioning that I found my device's ROM online with boot.img and recovery.img files and a .tar file which contains the original system folder.
Is there any way to make the stock recovery (since installing CWM or TWRP seems impossible) read my update file? Or is there another way to fix this? I only need to replace that single file.
Hoping to get help soon.
Cheers!
Dear fellas,
I replaced my build.prop file to an another one and my phone is not booting up anymore.
I have a rooted Xiaomi Mi 5s Plus, with custom recovery.
Can anyone advise what to do without wiping the phone completely and flashing a new ROM?
What I've tried doing:
- I had the original build.prop that the phone had before it got stuck.
- I used the file explorer in custom recovery, copied that file to the system folder in root.
- Rebooted the device, still no luck!
- After rebooting, when I reopen the recovery, and navigate to the system folder again, I don't find the file I copied to the system folder!
Any thoughts on the matter please? Thanks in advance!
Have you tried writing original Rom to the phone. Don't have much experience with that kind best I can suggest
Sent from my SM-G930V using Tapatalk
black_hawk1990 said:
Dear fellas,
I replaced my build.prop file to an another one and my phone is not booting up anymore.
I have a rooted Xiaomi Mi 5s Plus, with custom recovery.
Can anyone advise what to do without wiping the phone completely and flashing a new ROM?
What I've tried doing:
- I had the original build.prop that the phone had before it got stuck.
- I used the file explorer in custom recovery, copied that file to the system folder in root.
- Rebooted the device, still no luck!
- After rebooting, when I reopen the recovery, and navigate to the system folder again, I don't find the file I copied to the system folder!
Any thoughts on the matter please? Thanks in advance!
Click to expand...
Click to collapse
Try mount system read/write first then copy og build prop file in system partition and reboot or use aroma file manager.