Database Users

Root Explorer problem with permissions

ummmm...hello xda devs and members. i am a noob on these forums regarding development of the android OS. i managed to installed racht's floyo v0.30 after a lot of difficulties.
i have root explorer v2.15 installed on the custom rom. before yesterday everything was alright, i could browse and change the permissions of files easily. how ever yesterday in the evening i found out that my gallery wasnt displaying any of my cam pics. so via root explorer i browsed to the DCIM folder and saw that Owner r/w/e permission wasnt enabled. i tried to enable but i got a message saying that permission change was unsuccessful as sd card does not allow it, or something similar. so i updated and installed the official android 2.1 eclair via SEUS. the problem still persists. please help me

um, did you wipe the userdata in xrec/cwm ?
if not, try that.
if you did, all i can suggest is back up the content and format the card.
(that said i'm no expert so maybe someone else will have better solutions.)

before installing rom i performed factory reset through xrecovery and i also tried formatting the sd card. but no use. are u saying that i should try factory reset in phone settings. please reply ASAP

oh, no, just in recovery , but if you've done that, and you've tried formatting the sdcard, idk, perhaps try reinstalling the rom now that you've formatted the sdcard?
if that doesn't do it, y'need someone with more experience than me, heh.

hmmmm...maybe i should try again. and i was wondering if i can use a different sd card(not the one that came with my phone) but if i do so on my custom rom will i brick my phone or something

no, switching sd card won't brick the phone.
also, you could try a more recent version of root explorer and see if that helps.

thanks for the replies. i will try root explorer v2.17 and give updates. please subscribe to this thread so if i face any further problems with this you can help me out.

If can help....
you should explorer more on the forum
anyway, get latest flash tool, adb shell, baseband 015, unlock bootloader, custom kernel, custom Rom which is compatible with your custom Rom.
NOTE: USE THE SEARCH BUTTON ON TOP RIGHT OF THIS PAGE.
flash 015 baseband using flash tool, reboot, install busybox, xrecovery, #unlock bootloader (CAREFUL), reboot, flash custom kernel#, install custom rom. done.
NOTE: CAN SKIP STEP WITH ## QUOTE IF YOU ARE UNEASY WHAT YOU ARE DOING, PHONE WILL NOT BE SMOOTH AS PHONE WITH UNLOCKED BOOTLOADER AND WITH CUSTOM KERNEL, SAFETY FIRST .
IF GOT PROBLEM, REFLASH/UPDATE USING SEUS(GOOGLE), USING FLASHTOOL INSTALL BUSYBOX, XRECOVERY. REBOOT INTO RECOVERY, MOUNT SYSTEM, PLUG IN ADB CABLE TO PC (ENABLE USE DEBUG FIRST ADB AND INSTALL DRIVER), CMD, ADB SHELL, TYPE IN:
1. SU
2. BUSYBOX
3. DMESG
(SEARCH FORUM FIRST IF DON'T UNDERSTAND)
1. FLASHTOOL, SU IMPROPER INSTALLED
2. FLASHTOOL, BUSYBOX IMPROPER INSTALLED
3. KERNEL, SEUS AGAIN
IF ANY IF THE COMMAND YOU HAVE ENTERED SHOW ERROR, BLANKS(ENABLE USB DEBUG OR DRIVER ERROR) PLEASE CHECK INSTRUCTION CAREFULLY AND TRY AGAIN. THIS IS ULTIMATE FIX THAT I KNOW TO ME, OUT THERE MAYBE SOME PEOPLE WHOSE ARE MORE ADVANCE THAN ME CAN COMMENT/POINT OUT ERROR ABOUT MY POST AND WORK TOGETHER TO TEACH NEWBI A BETTER UNDERSTANDING
Thanks button are there ====>

ok guys thanks for all your replies (though i did not get many). i think i fixed the problem. you see with racht's floyo v0.30 comes a file manager. what i did was browse to the sd card directory. then i first excluded it from media scan and then reverted the process. i checked to see if my pictures were still in the gallery. i rebooted the phone and to my relief they were there...thank god. anyways thanks for your prompt replies. if you need any help be sure that i will help you

CKKnot said:
you should explorer more on the forum
anyway, get latest flash tool, adb shell, baseband 015, unlock bootloader, custom kernel, custom Rom which is compatible with your custom Rom.
NOTE: USE THE SEARCH BUTTON ON TOP RIGHT OF THIS PAGE.
flash 015 baseband using flash tool, reboot, install busybox, xrecovery, #unlock bootloader (CAREFUL), reboot, flash custom kernel#, install custom rom. done.
NOTE: CAN SKIP STEP WITH ## QUOTE IF YOU ARE UNEASY WHAT YOU ARE DOING, PHONE WILL NOT BE SMOOTH AS PHONE WITH UNLOCKED BOOTLOADER AND WITH CUSTOM KERNEL, SAFETY FIRST .
IF GOT PROBLEM, REFLASH/UPDATE USING SEUS(GOOGLE), USING FLASHTOOL INSTALL BUSYBOX, XRECOVERY. REBOOT INTO RECOVERY, MOUNT SYSTEM, PLUG IN ADB CABLE TO PC (ENABLE USE DEBUG FIRST ADB AND INSTALL DRIVER), CMD, ADB SHELL, TYPE IN:
1. SU
2. BUSYBOX
3. DMESG
(SEARCH FORUM FIRST IF DON'T UNDERSTAND)
1. FLASHTOOL, SU IMPROPER INSTALLED
2. FLASHTOOL, BUSYBOX IMPROPER INSTALLED
3. KERNEL, SEUS AGAIN
IF ANY IF THE COMMAND YOU HAVE ENTERED SHOW ERROR, BLANKS(ENABLE USB DEBUG OR DRIVER ERROR) PLEASE CHECK INSTRUCTION CAREFULLY AND TRY AGAIN. THIS IS ULTIMATE FIX THAT I KNOW TO ME, OUT THERE MAYBE SOME PEOPLE WHOSE ARE MORE ADVANCE THAN ME CAN COMMENT/POINT OUT ERROR ABOUT MY POST AND WORK TOGETHER TO TEACH NEWBI A BETTER UNDERSTANDING
Thanks button are there ====>
Click to expand...
Click to collapse
ummmm...you just taught how to install a custom rom which is already in my knowledge but anyways you tried to help so i appreciate it and thanks.

Flashing on 935F

Hi all.
I have the 935F International on it's way to me, delivering in the next day or so
By all accounts the 935F is already unlocked. To prepare, I have already downloaded Odin 3.11.1, CF's root file, TWRP twrp-3.0.2-2-hero2lte tar, and a custom ROM and bootloader/modem files.
I'm not a noob to flashing, just newish to Samsung.
What is the best way to start? Boot into stock, enable bootloader unlock on developer options, run Odin and flash TWRP, then CF's root file? Also, I want to run unencrypted - format data using advanced wipe 'yes' method?
The ROM states it sets root on installation. Do I then need to flash CF's root file?
Further, how are bootloader/modem tar files flashed? Is it as simple as selecting BL for bootloader, although I don't see anything for the modem??
Finally, what is the actual order of all this? I'm thinking: TWRP first, Format internal data second, CF root third, ROM flash from TWRP fourth, reboot to download mode from TWRP and then flash modem/bootloader last. Then reboot all together to set the phone up?
Thanks and any help is appreciated

1. Update to latest firmware
2. CF-Autoroot
3. TWRP
4. Flash no-verity-opt-encrypt.zip, wipe data.
5. Reboot recovery, mount system.
6. Wipe all except internal and external sd.
7. Flash your ROM

dynospectrum said:
1. Update to latest firmware
2. CF-Autoroot
3. TWRP
4. Flash no-verity-opt-encrypt.zip, wipe data.
5. Reboot recovery, mount system.
6. Wipe all except internal and external sd.
7. Flash your ROM
Click to expand...
Click to collapse
Thanks for the info :good:
When you say update to latest firmware this is Bootloader and Modem yes?
Steps 2 & 4 - just having done a little more research, are these outdated now?; as TWRP (latest) now fixes encryption and the ROM will inject (for a better term ) SuperSU when installing it? Or will this still need to be done irrespective of using the latest version of TWRP and ROM?
Cheers and thanks :good:

If you're not new to rooting and custom roms, pretty much all you need is to unlock OEM in Dev Options in Settings, Restart the device and hold Vol Down+Home+Power to get into Download Mode and press Up at the blue screen. Plug in your USB to your phone and run the tool on your PC.
Once Rooted, its business as usual. You don't need a guide to install TWRP, just install the Flashify app and let it do it for you, and then have no-verity-opt-encrypt.zip handy to flash. I know no-verity-opt-encrypt.zip is essential if you flash TWRP through ODIN, but not 100% sure if you should if you flashed TWRP through Flashify, I always flash no-verity-opt-encrypt.zip regardless so I unno.
Also if you find yourself in a semi-bricked situation where you can't figure out your problem, as long as you have Download Mode, you'll always have a way to get back to a working device. Samsung Smart Switch for Windows has an Emergency Mode that will revert your device back to Factory Conditions.

peteri8706 said:
Thanks for the info :good:
When you say update to latest firmware this is Bootloader and Modem yes?
Steps 2 & 4 - just having done a little more research, are these outdated now?; as TWRP (latest) now fixes encryption and the ROM will inject (for a better term ) SuperSU when installing it? Or will this still need to be done irrespective of using the latest version of TWRP and ROM?
Cheers and thanks :good:
Click to expand...
Click to collapse
I've been doing things this way since day 1 with no problems. My advice would be to do it the same way. I can assure you a solid install ;]
Yes, firmware is bootloader & modem. Great thread for this is here http://forum.xda-developers.com/s7-edge/how-to/official-stock-firmware-update-odin-t3335065

How do I backup my IMEI?

I was told to backup my IMEI before fashing CM14.1. I looked at this guide and because I don't want to go through the hassle rooting my phone I decided to go with the twrp backup way because I was going to backup with twrp anyway. But when I go to backup it doesn't show the EFS partitition like in the guide. I have Boot, System, Data and Cache. Will I need to root my phone or is there an easy fix to this? Also my phone is a moto G4 and not a G4 plus but I thought I'd ask here because the non-plus forum is kinda dead.

Florensie said:
I was told to backup my IMEI before fashing CM14.1. I looked at this guide and because I don't want to go through the hassle rooting my phone I decided to go with the twrp backup way because I was going to backup with twrp anyway. But when I go to backup it doesn't show the EFS partitition like in the guide. I have Boot, System, Data and Cache. Will I need to root my phone or is there an easy fix to this? Also my phone is a moto G4 and not a G4 plus but I thought I'd ask here because the non-plus forum is kinda dead.
Click to expand...
Click to collapse
In my lg g3 i have this option in twrp, it was nice if we had also in our moto g4.But for now we do not have.
Sent from my Moto G4 using XDA Labs

1. Backup all available in twrp
2. Follow this for root -> http://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772
3. Download Flashfire -> https://play.google.com/store/apps/details?id=eu.chainfire.flash&hl=en_GB
4. Set selinux to permissive temporary:
Code:
su
setenforce permissive
5. Open Flashfire and select RAW partition backup.
(I would backup all, but for IMEI you only need modem partitions)

velosa said:
In my lg g3 i have this option in twrp, it was nice if we had also in our moto g4.But for now we do not have.
Sent from my Moto G4 using XDA Labs
Click to expand...
Click to collapse
So do I need to root my phone or is the IMEI stored in any of the other partitions TWRP backs up? Also, can't I just write down my number from the about tab in Android?
Sent from my Moto G (4) using XDA-Developers mobile app

gabriwinter said:
1. Backup all available in twrp
2. Follow this for root -> http://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772
3. Download Flashfire -> https://play.google.com/store/apps/details?id=eu.chainfire.flash&hl=en_GB
4. Set selinux to permissive temporary:
Code:
su
setenforce permissive
5. Open Flashfire and select RAW partition backup.
(I would backup all, but for IMEI you only need modem partitions)
Click to expand...
Click to collapse
Thanks I'll take a look at that.

gabriwinter said:
1. Backup all available in twrp
2. Follow this for root -> http://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772
3. Download Flashfire -> https://play.google.com/store/apps/details?id=eu.chainfire.flash&hl=en_GB
4. Set selinux to permissive temporary:
Code:
su
setenforce permissive
5. Open Flashfire and select RAW partition backup.
(I would backup all, but for IMEI you only need modem partitions)
Click to expand...
Click to collapse
EDIT: I restored my backup and it's fine now. But I sure did almost have a heart attack. I am on nougat soak test which was causing issues.
I did the second step but now my IMEI doesn't show up anymore, my SIM isn't found, I can't find any networks, my IP address is gone, my mac address is reset. Do I restore the backup?
tl;dr: topic in the second step barely points out the fact it only works on marshmellow (small, non bold, normal size letters at the top of the topic), flashed it anyway, almost lost my IMEI while trying to backup... my IMEI
EDIT 2: sorry for being such a noob, but wouldn't it be better to go straight to CM, root it with CM's built-in rooting functionality and then do the backup? Would there be a higher chance of losing an IMEI number in the process of that than in the process of your instructions because for your instructions I need to go back to marshmellow, root, backup IMEI, flash nougat (people say CM has less issues if you flash nougat first), flash CM? How do you even 'lose' your IMEI?

I'm sorry I didn't realise you where using nougat.
Yes flashing CM and then using flashfire will work just fine.
You will be taking a backup of the soak version of your modem partitions.
You won't loose your IMEI flashing CM because it doesn't change the modem partitions.
The only way you can loose your IMEI is by using fastboot (or flashfire) and flashing the wrong version.
So you don't need to worry about losing your IMEI at this stage.

gabriwinter said:
I'm sorry I didn't realise you where using nougat.
Yes flashing CM and then using flashfire will work just fine.
You will be taking a backup of the soak version of your modem partitions.
You won't loose your IMEI flashing CM because it doesn't change the modem partitions.
The only way you can loose your IMEI is by using fastboot (or flashfire) and flashing the wrong version.
So you don't need to worry about losing your IMEI at this stage.
Click to expand...
Click to collapse
No problem, you couldn't have possibly known that. I should have mentioned it. Thanks for the help yet again.
Sent from my Moto G (4) using XDA-Developers mobile app

I may be asking a stupid question but how do you "lose" your imei? Isn't that the serial number to the device. I mean it's stamped on the back of the battery. I wouldn't think that is possible, isn't that how your phone gets blacklisted?

daverobinson88 said:
I may be asking a stupid question but how do you "lose" your imei? Isn't that the serial number to the device. I mean it's stamped on the back of the battery. I wouldn't think that is possible, isn't that how your phone gets blacklisted?
Click to expand...
Click to collapse
The phone cannot read what's stamped on the back of the battery. It needs something to tell it that the IMEI number is so-and-so. The IMEI number thus is stored in a particular partition of your phone, one that is usually never touched by the average user.

Rooted, Custom Rom a huge fail

Hello dear Community!
It is depressing that my first appearance here is to ask for help, but I am going crazy.
So, I tried to Root my phone via Odin + CF Autoroot klte and it seemed to have been a success.
The root checker also said, that my device was rooted so I went on and installed TWRP to be able to install Lineage OS.
After getting Lineage to work I got a few error messages suddenly popping up, telling me that either "Music had stopped" or other android operation were closed because they didn't work properly.
I tried to install Gapps, it seemed to have worked but I was only able to open and enter the store once, afterwards the store never managed to load and then the app closed itself after starting it.
So I checked again with Root Checker, but this time it gave me an error message, too. It said, that my device was not rooted properly.
I guess this is were I made it worse by deciding to just root the phone again. Obviously, it didn't work either.
Afterwards I thought that maybe installing The Original Android OS and then unrooting the phone would be the best solution to be able to start anew.
First I tried to flah Lineage again and that made it impossible for me to boot the phone. The farthest I got was the setup page, were it tells you Hello and were you can choose a Language, but clicking the arrow key didn't do anything at all.
The recovery mode was also not the TWRP one anymore, but the original Android one and that was a huge problem for me.
Then I tried to flash the 6.1 OS for the S5 (I made sure it was the correct version), but now it is stuck at the "Samsung" screen while it boots.
It never boots though.
I don't know what to do anymore.
Please, I beg you, could anyone help me out?

Don't flash the latest Lineage OS ROM
Hello AsylumAlice u shouldn't have flashed the latest Lineage OS ROM because now u will need a new motherboard for your S5 since the ROM corrupts the MMC chip now u will need to get a new MMC chip or a new Motherboard sorry that your s5 is now hard bricked but when u get it fixed flash the DreamUX S8 Rom it works flawless on my S5 SM-G900i
Yours Sincely
Matty Bourke

mattybourke1994 said:
Hello AsylumAlice u shouldn't have flashed the latest Lineage OS ROM because now u will need a new motherboard for your S5 since the ROM corrupts the MMC chip now u will need to get a new MMC chip or a new Motherboard sorry that your s5 is now hard bricked but when u get it fixed flash the DreamUX S8 Rom it works flawless on my S5 SM-G900i
Yours Sincely
Matty Bourke
Click to expand...
Click to collapse
What are the grounds for your claims?
You needn't root via CF-autoroot if your end goal was to flash lineage. CF autoroot was intended to root stock roms with ease and less effort.
Flash The LATEST, official TWRP via odin then do a FULL WIPE. Wipe system, data, cache and dalvik cache.
From here on, you have two options:
1.) Sideload the LineageOS rom via ADB
2.) Transfer it to the phone's storage via MTP and flash it from TWRP.
As for how to accomplish this, the forum search bar and Google has your back. You need only choose one procedure.
If you need the Play Store, flash gapps AFTER flashing LINEAGE AND BEFORE REBOOTING.
Since you were under the idea that utilizing CF-autoroot was a necessity, I suggest that you re-read this post thoroughly before actually putting it into practice.

Kinloch said:
What are the grounds for your claims?
You needn't root via CF-autoroot if your end goal was to flash lineage. CF autoroot was intended to root stock roms with ease and less effort.
Flash The LATEST, official TWRP via odin then do a FULL WIPE. Wipe system, data, cache and dalvik cache.
From here on, you have two options:
1.) Sideload the LineageOS rom via ADB
2.) Transfer it to the phone's storage via MTP and flash it from TWRP.
As for how to accomplish this, the forum search bar and Google has your back. You need only choose one procedure.
If you need the Play Store, flash gapps AFTER flashing LINEAGE AND BEFORE REBOOTING.
Since you were under the idea that utilizing CF-autoroot was a necessity, I suggest that you re-read this post thoroughly before actually putting it into practice.
Click to expand...
Click to collapse
Thank you so much for your fast reply!
-> I flashed the newest Version for klte via Odin, but I can't get into the boot mode.
I only am able to enter the download mode. What can I do now?

Flash TWRP via odin again, untick the Auto-Reset option of Odin first. Then try booting to recovery via long holding the power, home and volume up button simultaneously without releasing any of the buttons until you successfully see the TWRP splash screen.
If that still doesn't work, reboot to recovery via adb from download mode. You need the adb and the usb drivers for your device.
If that still doesn't work, you might have flashed an incompatible version of TWRP.

Kinloch said:
Flash TWRP via odin again, untick the Auto-Reset option of Odin first. Then try booting to recovery via long holding the power, home and volume up button simultaneously without releasing any of the buttons until you successfully see the TWRP splash screen.
If that still doesn't work, reboot to recovery via adb from download mode. You need the adb and the usb drivers for your device.
If that still doesn't work, you might have flashed an incompatible version of TWRP.
Click to expand...
Click to collapse
Thank you so much, it worked perfectly!
I can now start my phone and use it normally.
But the Root Checker still says:
"Sorry! Root access is not properly installed on this device.
Device: SM-G900M
Android version: 7.1.2"
What should I do from now on?
Thank you so much for your help (agaiN).
And as for why I used the auto-root, well I just followed a guide that I found, it only had positive reviews so I assumed it was a correct tutorial.

AsylumAlice said:
Thank you so much, it worked perfectly!
I can now start my phone and use it normally.
But the Root Checker still says:
"Sorry! Root access is not properly installed on this device.
Device: SM-G900M
Android version: 7.1.2"
What should I do from now on?
Thank you so much for your help (agaiN).
And as for why I used the auto-root, well I just followed a guide that I found, it only had positive reviews so I assumed it was a correct tutorial.
Click to expand...
Click to collapse
just flash supersu in twrp

AronFerr said:
just flash supersu in twrp
Click to expand...
Click to collapse
I thought about doing that, but wasn't sure how exactly to proceed and what Version to install.
I downloaded SuperSU v.2.82 and put it on my internal storage.
Just install over TWRP the same way that I Installed Lineage and Gapps I suppose?
I guess if it doesn't work out, I just follow the steps from above again and retry?
Thank you so much. I feel like in idiot in this situation.

AsylumAlice said:
I thought about doing that, but wasn't sure how exactly to proceed and what Version to install.
I downloaded SuperSU v.2.82 and put it on my internal storage.
Just install over TWRP the same way that I Installed Lineage and Gapps I suppose?
I guess if it doesn't work out, I just follow the steps from above again and retry?
Thank you so much. I feel like in idiot in this situation.
Click to expand...
Click to collapse
yes just flash it but no wipes

How to unbrick my ZTE Axon 7 mini b2017g

Dear Seniors.
I am facing great hardship because my phone is stuck at boot logo.
No booting in recovery mode to flash another rom.
I did unlock bootloader of it by using tuliptool with success. After that i flashed custom rom in it. after reboot it is happening that.
Please suggest to recover it.

Did you flash twrp after unlocking? Did you make backup of stock ROM? Perhaps find a version of the factory firmware and flash that.

Dear I have no backup and i flashed TWRP recovery.......
It is to aware you that i did relock bootloader now my phone is working properly. but i am unable to enter recovery mode. !!!
Now my phone is running android 6.0.1 B02
But i am failed to root this rom uptill now due above mentioned problem.

modorate said:
Dear I have no backup and i flashed TWRP recovery.......
It is to aware you that i did relock bootloader now my phone is working properly. but i am unable to enter recovery mode. !!!
Now my phone is running android 6.0.1 B02
But i am failed to root this rom uptill now due above mentioned problem.
Click to expand...
Click to collapse
I found software update notification but when i update an error accruing while update. (This update not compatible with this device"
In easy words......... my recovery.img has been corrupted. I have no idea to get rid of this situation.

I planned to unlock my Mini's bootloader this weekend. After reading this post, I decided to act later until the root cause has been figured out.

bao_gg said:
I planned to unlock my Mini's bootloader this weekend. After reading this post, I decided to act later until the root cause has been figured out.
Click to expand...
Click to collapse
Several people myself included have been able to use tuliptool to successfully unlock and root the device.

mine is hard bricked too. but I think it is worse than the case listed on the op.
if you want to hard bricked these are the steps:
follow the procedure to install the Spanish ROM 6.1, than another android m b12, than finally the android seven......use tulip tool and install twpr fine, root ect. amazing ROM.......buuuuut......I lost my IMEI somewhere in this process, and the original FTM which had a small menu changes to another static one, without the menu.
I needed this menu to open the com port to fix the IMEI. than I had the brilliant idea to re-flash android M via twrp (without modifying the zip file to remove the recovery, something I knew so well from the older axon mini).
results:
-lost twpr because the stock ROM wrote over it,
-cannot boot the OS because I flashed android m but the phone had the aboot 7.
-i now have a brick
I need a genious to sujest something to bring it back to life........sh....t...sh...t.....sh...t
any chances I could inject aboot7 via ADB through my dead recovery which somehow the phone recognises? ADB shell still seems to be working
thanks