[Q] Root Issue for Xolo q800 - Android Q&A, Help & Troubleshooting

I earlier rooted my cell and it was working fine till yesterday. I reinstalled the DogeMod Rom but now my Xposed Module is not working. I installed root checker from the playstore but it's showing that I am not rooted. I can go into the recovery and have tried flashing supersu files, xposed modules, twrp recovery but still I am unable get it rooted again. I believe that this is a rooting issue only.
Kindly troubleshoot my problem.
Thanking in anticipation.

Manipal said:
I earlier rooted my cell and it was working fine till yesterday. I reinstalled the DogeMod Rom but now my Xposed Module is not working. I installed root checker from the playstore but it's showing that I am not rooted. I can go into the recovery and have tried flashing supersu files, xposed modules, twrp recovery but still I am unable get it rooted again. I believe that this is a rooting issue only.
Kindly troubleshoot my problem.
Thanking in anticipation.
Click to expand...
Click to collapse
Do you have a custom recovery?

christi9503 said:
Do you have a custom recovery?
Click to expand...
Click to collapse
Yes Sir, I can go in the recovery, I tried flashing SuperSu files and other files to get my device rooted but to no effect.
I also tried to root it via SP Flash but still it is showing not rooted

Manipal said:
Yes Sir, I can go in the recovery, I tried flashing SuperSu files and other files to get my device rooted but to no effect.
I also tried to root it via SP Flash but still it is showing not rooted
Click to expand...
Click to collapse
@Manipal
Try flashing this guy.
Also format cache partition and dalvik cache.

christi9503 said:
@Manipal
Try flashing this guy.
Also format cache partition and dalvik cache.
Click to expand...
Click to collapse
Encryption Unsuccessful
Encryption was interrupted and the data on your phone is no longer accessible. Reset your phone now. -_-

Manipal said:
Encryption Unsuccessful
Encryption was interrupted and the data on your phone is no longer accessible. Reset your phone now. -_-
Click to expand...
Click to collapse
When did you get this after clearing cache or after flashing the su update?

christi9503 said:
When did you get this after clearing cache or after flashing the su update?
Click to expand...
Click to collapse
When I rebooted my device after the given instructions were completed.

Manipal said:
When I rebooted my device after the given instructions were completed.
Click to expand...
Click to collapse
Well I have never seen that error before. It is strange because it is just Su binary and SuperSu in the zip i gave you. Did you manage to boot it?

Yes, I have to reinstall all my software's afresh.
Sent from my Nexus 4 using XDA Free mobile app

Manipal said:
Yes, I have to reinstall all my software's afresh.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
Is root working now at least?

christi9503 said:
Is root working now at least?
Click to expand...
Click to collapse
Yes, thanks god, it's working now.
Between thanks for the assistance.
Sent from my Nexus 4 using XDA Free mobile app

Manipal said:
Yes, thanks god, it's working now.
Between thanks for the assistance.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
Sorry for the inconvenience with that error. I don't know what caused it never seen that ever before hope all your data is ok.

christi9503 said:
Sorry for the inconvenience with that error. I don't know what caused it never seen that ever before hope all your data is ok.
Click to expand...
Click to collapse
I reinstalled my rom last night and when I was to reboot again it remained struck there. So first thing in the morning I formatted and installed the rom fresh. It took me about 3 hours to get everything installed and now I am facing the same trouble again.
I am struck at my bootscreen. I rebooted the device when I tried to install a font of Chocooky from Fonter Xposed Module. I am in a big fix now. Please help me now as it is not bypassing the bootscreen :crying:

I am not home and i don t have your device. I just gave a universal root solution. I will try to help when i get home to make some research for your device.
Sent from my LG-P710 using XDA Free mobile app

Related

[Q] What did I do.

So i was going to flash a rom I made a back up, I hit fixed permissions. and now all I have is Samsung Galaxy S4 logo and is just stuck there. I can get into twrp and have tried wiping and starting from a clean slate and restoring the back up but still get the galaxy logo? any suggestions ?
**have just tried to use odin and fails also*** How do I get back to stock please? Anyone please help
bump
Imprezive13 said:
bump
Click to expand...
Click to collapse
Have you tried flashing a stock ROM from TWRP?
-------edit----------
I just remembered. This used to happen on the Note 2 at times. If you're booting and get the Samsung splash screen, try going to TWRP and doing a Factory Reset a couple times. No idea if it will work, but with the Note that would usually clear whatever block existed and allow the ROM to boot past the splash screen. Good luck.
eakeller said:
Have you tried flashing a stock ROM from TWRP?
Click to expand...
Click to collapse
what do you mean ? first time ever having a problem with this. are you talking about the SCH-I545_MDK_562219_Stock_Restore.tar file ?
Imprezive13 said:
what do you mean ? first time ever having a problem with this. are you talking about the SCH-I545_MDK_562219_Stock_Restore.tar file ?
Click to expand...
Click to collapse
If it exists, it would basically be that ROM stuck into a .zip file which could be flashed from TWRP. I'm not sure it exists, was just browsing the Dev thread for you to see if anyone posted it. There is a version here http://forum.xda-developers.com/showthread.php?t=2292707 , but I'm not familiar with Loki enough to say whether or not you have it.
eakeller said:
If it exists, it would basically be that ROM stuck into a .zip file which could be flashed from TWRP. I'm not sure it exists, was just browsing the Dev thread for you to see if anyone posted it. There is a version here http://forum.xda-developers.com/showthread.php?t=2292707 , but I'm not familiar with Loki enough to say whether or not you have it.
Click to expand...
Click to collapse
Well for right now im trying to just get the phone back to its working condition. trying to using odin, but fails every time. and not sure what i should do.
Imprezive13 said:
Well for right now im trying to just get the phone back to its working condition. trying to using odin, but fails every time. and not sure what i should do.
Click to expand...
Click to collapse
If Odin isn't working for you, a solution might be had via TWRP since you can still get into the recovery. If you flash your ROM or try your backup, does the install complete or does it crash? Have you wiped cache, dalvik, system, and data before the flash?
-edit-
Sorry, just saw your OP where you said you wiped and tried. If I were you my next step would be trying a different ROM just to see if you can get something booting.
eakeller said:
If Odin isn't working for you, a solution might be had via TWRP since you can still get into the recovery. If you flash your ROM or try your backup, does the install complete or does it crash? Have you wiped cache, dalvik, system, and data before the flash?
Click to expand...
Click to collapse
Trying again. First wiping wiped cache, dalvik, system, and data , then restoring back up. I've tried this multiple times before hopefully it works this time. But generally when i hit reboot system afterward it just hangs at the Samsung Galaxy IV boot screen and does nothing.
Imprezive13 said:
Trying again. First wiping wiped cache, dalvik, system, and data , then restoring back up. I've tried this multiple times before hopefully it works this time. But generally when i hit reboot system afterward it just hangs at the Samsung Galaxy IV boot screen and does nothing.
Click to expand...
Click to collapse
After your backup restores, try using TWRP to do a Factory Reset a couple times before rebooting. Also wipe cache/dalvik again before the boot.
Failed again stuck at Samsung Galaxy S4 boot screen
eakeller said:
After your backup restores, try using TWRP to do a Factory Reset a couple times before rebooting. Also wipe cache/dalvik again before the boot.
Click to expand...
Click to collapse
Stuck again
Imprezive13 said:
Stuck again
Click to expand...
Click to collapse
Sorry to hear that, man. I'm out of ideas and hopefully someone with more know-how can give the solution.
Sent from my SCH-I545 using Tapatalk 2
I would try downloading a ROM to your computer then copying it to a microsd, put the card in your phone and then try to flash the fresh ROM from TWRP. (After wiping everything again.)
Sent from my SCH-I545 using Tapatalk 2
slim6596 said:
I would try downloading a ROM to your computer then copying it to a microsd, put the card in your phone and then try to flash the fresh ROM from TWRP. (After wiping everything again.)
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Ive been looking for the stock rom files no luck at the moment.
Maybe this one?
http://forum.xda-developers.com/showthread.php?t=2292707
Sent from my SCH-I545 using Tapatalk 2
slim6596 said:
Maybe this one?
http://forum.xda-developers.com/showthread.php?t=2292707
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
downloading now wish me luck
Good luck to you.
Sent from my SCH-I545 using Tapatalk 2
slim6596 said:
Good luck to you.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
got it working. on a deoxed rom. but is there a way to go completely back to stock using odin ?
http://forum.xda-developers.com/showthread.php?t=2289325
Sent from my SCH-I545 using Tapatalk 2
slim6596 said:
http://forum.xda-developers.com/showthread.php?t=2289325
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Well went to restart the phone and now its stuck on a Samsung logo with a unlocked icon thats says custom underneath it and just sits there.

Can I brick my phone using Xposed?

I have a mtk6572 will installing modules brick my device
Sent from my GT-S5830L using xda app-developers app
no it will not brick your phone but it will do hang or force stop your system ui sometimes
divyamg28 said:
no it will not brick your phone but it will do hang or force stop your system ui sometimes
Click to expand...
Click to collapse
Never had that problem
BenDroid1 said:
I have a mtk6572 will installing modules brick my device
Sent from my GT-S5830L using xda app-developers app
Click to expand...
Click to collapse
keep this on the root of your sd card...
https://www.dropbox.com/s/h0u496vl6vwp79x/Xposed-Disabler-Recovery.zip
havent ran into brick yet but definitely an endless bootloop...flash this zip and it doesnt delete your xposed modules, just switched it off so you can boot
spiral777 said:
keep this on the root of your sd card...
https://www.dropbox.com/s/h0u496vl6vwp79x/Xposed-Disabler-Recovery.zip
havent ran into brick yet but definitely an endless bootloop...flash this zip and it doesnt delete your xposed modules, just switched it off so you can boot
Click to expand...
Click to collapse
The Xposed installer creates that zip on install. So no need to share it. Isn't it device/rom specific too? (it flashes back some original files from before install)
GriffinSauce said:
The Xposed installer creates that zip on install. So no need to share it. Isn't it device/rom specific too? (it flashes back some original files from before install)
Click to expand...
Click to collapse
Never realized that... Thnx
For anyone that thinks it can't brick your phone it can. I had a Note 4 t;mobile, had a custom recovery twrp 2.8.7, had a backup to. I somehow messed it up so bad I couldn't even get to recovery, Odin original rom, recovery, everything even tried baseband/bootloader. Flashed 4 different original roms, tried flashing philz recovery also. Even restored it via Kies3 said it completed but on boot my phone says recovery...booting and then shuts off. It was worth the risk imo.
Please help me ... After I flash the framework from xposed installer i had the problem of the system force stopping how can I fix it without losing my data
How can I flash the uninstaller , I tried by entering the recovery and apply update from my sd card but it does not work can you tell me if there is another way and thanks

[Q]All Roms failing during flashingon Note 3 - PROBLEM SOLVED!

Hey Guys
I'm a experienced flasher but I have ran into a issue with flashing roms on my Note 3. I had recently just been running stock rooted rom (basically I rooted my phone the day it came out with Sprint and never have update anything). So when I noticed that ny son's note 3 (note rooted) got an update recently, I decided to look for an updated base and broadband for my phone, which I thought I had found. So after so help with figuring out which update I needed to do, I figured NH7 was the latest. Finally got my phone updated or so it appeared.
So this week I've been trying desperately to update to MOAR S5 PORT (NE5 based I believe) I followed the instructions carefully and tried all 3 versions. All failed. So I restored my phone. Tonight I tried flashing flashing Pac-man rom. Same thing happened. Failed during install.
Can you guys take a look at my setup and tell me what may be wrong? Doing a clean install each time.
Sent from my SM-N900P using XDA Premium 4 mobile app
UPDATED 10/24/2014:
I had to reflash all the Note 3 stock tar's in order. Then root with Chainfire Auto Root. Then install Clockwork MOD Recovery. Now I can flash roms.
shaun0207 said:
Hey Guys
I'm a experienced flasher but I have ran into a issue with flashing roms on my Note 3. I had recently just been running stock rooted rom (basically I rooted my phone the day it came out with Sprint and never have update anything). So when I noticed that ny son's note 3 (note rooted) got an update recently, I decided to look for an updated base and broadband for my phone, which I thought I had found. So after so help with figuring out which update I needed to do, I figured NH7 was the latest. Finally got my phone updated or so it appeared.
So this week I've been trying desperately to update to MOAR S5 PORT (NE5 based I believe) I followed the instructions carefully and tried all 3 versions. All failed. So I restored my phone. Tonight I tried flashing flashing Pac-man rom. Same thing happened. Failed during install.
Can you guys take a look at my setup and tell me what may be wrong? Doing a clean install each time.
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Wipe wipe Wipe and when it fails to flash then restart recovery And it will flash then ....
So wipe 3 times. Then when it fails. Reboot to recovery and flash again? Do I need to wipe again before flashing?
Sent from my LGLS990 using XDA Free mobile app
shaun0207 said:
So wipe 3 times. Then when it fails. Reboot to recovery and flash again? Do I need to wipe again before flashing?
Sent from my LGLS990 using XDA Free mobile app
Click to expand...
Click to collapse
Any time you wipe the system partition, you MUST restart TWRP recovery before flashing the rom of your choice,.. or it'll fail every time.
Ok. I will try that noq
Sent from my SM-N900P using XDA Premium 4 mobile app
shaun0207 said:
Ok. I will try that now
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sent from my SM-N900P using XDA Premium 4 mobile app
shaun0207 said:
Ok. I will try that noq
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Let us know how it goes. Happy flashing.
So I wiped everything. Tried to install and it failed. So i go to reboot to recovery and it ask me about superuser. But it doesnt install because their is no OS. REBOOT to recovery and it fails again
Do I need to format data?
Actually I dont even see a option in TWRP to format data
I wonder if I should try a dirty flash?
I would odin flash a full stock nh7. To get you all the way to nh7. I see you are still at nab on one. I had problems when they weren't all the same. I could be wrong.... I'm a noob. lol
Then, root with chanfires autoroot. Install your recovery. Then, flash your rom of choice.
NOTE: I said nh7.... but, if the rom you want to use isn't, then odin to nab or whatever the rom you want to run is. I don't know about downgrading, could make a brick.... lol
Research everything I said before you do anything! Or wait for someone to correct what's wrong with what I said! I take no responsibility for what you do to your phone!
one of your issues is you updated wrong! unless you were on nc5 you shouldnt jump right to nh7. you have to update in order to insure no issues. so if oyu were nqb or ever mi3 you need to go in order mi3>nab>nc5>nh7
Chainfires auto root.....http://download.chainfire.eu/362/CF-Root/CF-Auto-Root/CF-Auto-Root-hltespr-hltespr-smn900p.zip
Here is Supersu download.....so when you check to see if you have root.....it will all be good.......http://download.chainfire.eu/578/SuperSU/UPDATE-SuperSU-v2.14.zip
Odin v3.07.......http://forum.xda-developers.com/showthread.php?t=1738841
now you can try to go back to stock and flash whichever you are going to flash........or you can do a reflash of whatever you want....I have notice a losss of root also too.
also make sure to look into all those fixes for security patches xda has for our phone......download and scan with bluebox security and search for any open links that have a fix here on xda........
this happened to me the other weekend and it took an afternoon to dig all resources to figure out why and what i needed to do........I started rooting with a samsung moment......
I am back to stock.....no complaints.....but only did to get home before i go back to a rom.......hope we have helped....
Thanks guys. I will try all of these
shaun0207 said:
Thanks guys. I will try all of these
Click to expand...
Click to collapse
to get updates to stick via odin. remove sd card too. and when you update each version. boot to stock recovery wipe phone. flash again. what i do on each update. never had a single issue.
shaun0207 said:
Do I need to format data?
Click to expand...
Click to collapse
Yes you have to do that.. Also I believe you have to be in twrp 2.8 for kitkat I was having problems too until I installed the new Twrp!
bigkev904 said:
Yes you have to do that.. Also I believe you have to be in twrp 2.8 for kitkat I was having problems too until I installed the new Twrp!
Click to expand...
Click to collapse
I dont see a new TWRP. All I see is version 2,8
I installed all the updates back to back. I have TWRP installed and I'm on NH7 now. But I cant get root. Chainfire Auto took me back to stock recovery and I'm not rooted. So I flashed TWRP via Odin and flashed ChainFire Superuser v.2.14 and I'm still not rooted. All thought it say it worked. So WHen I reboot, what do I need to do then? I have SU installed
Ok guys. After flashing all the Roms in order via ODIN. I finally have NH7 working and rooted.
I just tried wiping system, data,dalvik and cache. Then I immediately rebooted to recovery and tried to flash MOAR V1. and Pac-man rom. Both failed.
One thing Im noticing in recovery is that the system is not mounted in when wiping. So I tried wiping with and without system being mounted and got the same result. One thing Im not sure about with flashing for the note is if the Data should be formatted before installing? However I dont see that option in TWRP.
This is the only phone Ive had this much trouble with when it came to flashing.
Any ideas?
Sent from my SM-N900P using XDA Premium 4 mobile app

[root g900tuvs1fol] !!!!!

I just rooted my 900T S5 that i accidentally let T-mobile update install like a wee ago. I said **** it, so I trie CF-autoroot for the FOJ, and it worked. who woulda thunk..heh.
Ya but can you flash custom Roms???
You can also root by flashing twrp in download mode from Odin & then flashing supersu in reocvery
Sent from my SM-G900T using Tapatalk
Well everything was good than around noon today out of nowhere I got 'Sim not inserted' error. I flashed stock already, tried another working sim, so it's obviously my phone.. any suggestions
caspuh said:
Well everything was good than around noon today out of nowhere I got 'Sim not inserted' error. I flashed stock already, tried another working sim, so it's obviously my phone.. any suggestions
Click to expand...
Click to collapse
I would odin back to stock and if that didn't fix it, back to TMO.
caspuh said:
Well everything was good than around noon today out of nowhere I got 'Sim not inserted' error. I flashed stock already, tried another working sim, so it's obviously my phone.. any suggestions
Click to expand...
Click to collapse
I'd recommend wiping the phone and then flashing the stock rom ( or cyanogenmod for fun ). Make a backup though since this will delete everything. This helped my issues, just factory reset and then find the newest rom on sammobile. Good luck bud☺
This guy needs help said:
I'd recommend wiping the phone and then flashing the stock rom ( or cyanogenmod for fun ). Make a backup though since this will delete everything. This helped my issues, just factory reset and then find the newest rom on sammobile. Good luck bud
Click to expand...
Click to collapse
I legit did EVERYTHING, wouldn't come back, sent the phone for warranty and got a brand new replacement.. now I wonder if I should try the just flashing twrp way...
caspuh said:
now I wonder if I should try the just flashing twrp way...
Click to expand...
Click to collapse
you should
caspuh said:
I legit did EVERYTHING, wouldn't come back, sent the phone for warranty and got a brand new replacement.. now I wonder if I should try the just flashing twrp way...
Click to expand...
Click to collapse
That way worked for me.
gspears said:
That way worked for me.
Click to expand...
Click to collapse
Did you have any issue when installing SuperSU from TWRP on this firmware? I've tried it twice on my girlfriends phone and it gets stuck on the Samsung logo screen. Tried doing a factory reset to clear everything and still no luck.
soul_vice said:
Did you have any issue when installing SuperSU from TWRP on this firmware? I've tried it twice on my girlfriends phone and it gets stuck on the Samsung logo screen. Tried doing a factory reset to clear everything and still no luck.
Click to expand...
Click to collapse
What version of TWRP, and more importantly, what version of SuperSU? I would recommend this version of supersu: https://download.chainfire.eu/932/SuperSU/BETA-SuperSU-v2.71-20160331103524.zip and instead of factory resetting, after you install supersu in TWRP, just clear cache and dalvik
soul_vice said:
Did you have any issue when installing SuperSU from TWRP on this firmware? I've tried it twice on my girlfriends phone and it gets stuck on the Samsung logo screen. Tried doing a factory reset to clear everything and still no luck.
Click to expand...
Click to collapse
I installed the version listed in the post above. Use it.
thisisapoorusernamechoice said:
What version of TWRP, and more importantly, what version of SuperSU? I would recommend this version of supersu: <link> and instead of factory resetting, after you install supersu in TWRP, just clear cache and dalvik
Click to expand...
Click to collapse
gspears said:
I installed the version listed in the post above. Use it.
Click to expand...
Click to collapse
I tried with both versions 3.0.1 and 3.0.2 of TWRP. I tried with whatever version of SuperSU is included in TWRP. I tried to install it when TWRP detects that SuperSU is not installed and it asks you if you would like to install it. Perhaps this is a known issue and I am just not aware of it? I will try downloading the recommended version above and flashing the .zip in TWRP manually this weekend.
Thanks all for your input!
Hit " Do Not Install ".Thats most likely your problem.
Sent from my SM-G900T using XDA Free mobile app

(Discontinued) Custom rom for R1HD (Zen UI) (Discontinued)

I am not responsible for any damage that may occur, you assume all responsibility for what you install on your phone.
This is a custom rom for R1HD, (Zen UI).
This is a rom I ported to my R1HD, I like the rom, thought I would share with community.
Rom is rooted, but doesn't prop per app, if you want prop per app after install go to playstore and install SuperSu https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en
The rom works well for me, it's intended for people who want something other than stock rom.
The rom includes gapps, so playstore works correctly. The rom is fast and smooth, nice to look at as well.
You need to have bootloader unlocked, and have twrp recovery.
e1a3216d83e18f99c5f2f5c1b8e415b4 /home/vampirefo/Desktop/R1HD_Roms/zen/R1HD_ZenUi.zip
To install download
https://www.androidfilehost.com/?fid=385035244224382387
place R1HD_ZenUi.zip and sdcard reboot to twrp
factory reset
install R1HD_ZenUi.zip
reboot to system.
this rom will take a while on first boot.
Kernel Source
https://github.com/vampirefo/android_kernel_mediatek_mt6735
Only tested via my twrp.
https://www.androidfilehost.com/?fid=24713784966774807
credits
Lexan
Vampirefo
XDA Developers.
Looks gorgeous vamp. Glad you got all the blob stuff sorted out.
"Updater process ended with ERROR: 7"
Does not flash.
bullet25 said:
"Updater process ended with ERROR: 7"
Does not flash.
Click to expand...
Click to collapse
What recovery you using? I only tested on my twrp recovery.
Sent from my R1 HD using Tapatalk
vampirefo said:
What recovery you using? I only tested on my twrp recovery.
Sent from my R1 HD using Tapatalk
Click to expand...
Click to collapse
TWRP.
bullet25 said:
TWRP.
Click to expand...
Click to collapse
You using my twrp?
Sent from my R1 HD using Tapatalk
vampirefo said:
You using my twrp?
Sent from my R1 HD using Tapatalk
Click to expand...
Click to collapse
No, lopestone's. You don't have a TWRP linked in the OP. Why should there be a difference?
bullet25 said:
No, lopestone's. You don't have a TWRP linked in the OP. Why should there be a difference?
Click to expand...
Click to collapse
I don't use his twrp only tested on my twrp.
Sent from my R1 HD using Tapatalk
vampirefo said:
I don't use his twrp only tested on my twrp.
Sent from my R1 HD using Tapatalk
Click to expand...
Click to collapse
Okay, can you please link to your TWRP?
bullet25 said:
Okay, can you please link to your TWRP?
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=24713784966774807
Sent from my R1 HD using Tapatalk
Can this port be used as base for others?
Same error even with your TWRP.
bullet25 said:
Same error even with your TWRP.
Click to expand...
Click to collapse
Works perfectly for me.
Sent from my BLU ENERGY X PLUS using Tapatalk
got it to install with lopestorms recovery. needed to mount the /system as writeable first
but it still had an error message during the flash. I t didnt stop the install. It said failed to mount /system (resource busy) then it continued anyway.
mrmazak said:
got it to install with lopestorms recovery. needed to mount the /system as writeable first
but it still had an error message during the flash. I t didnt stop the install. It said failed to mount /system (resource busy) then it continued anyway.
Click to expand...
Click to collapse
Well yes, cause you shouldn't be mounting system at all, mounting system causes the busy error.
You should just wipe data and cache, not mess with system.
That explains why you all have problems, system should never be touched.
All you should be doing is click wipe, slide one time this is factory reset. Do nothing else then click back and install ROM.
Sent from my BLU ENERGY X PLUS using Tapatalk
vampirefo said:
Well yes, cause you shouldn't be mounting system at all, mounting system causes the busy error.
You should just wipe data and cache, not mess with system.
That explains why you all have problems, system should never be touched.
All you should be doing is click wipe, slide one time this is factory reset. Do nothing else then click back and install ROM.
Sent from my BLU ENERGY X PLUS using Tapatalk
Click to expand...
Click to collapse
iknow system being mounted cause the busy message, but recovery was set with system not writeable before and that caused error 7
to get past error 7 needed to take check mark off "mount system read-only"
mrmazak said:
iknow system being mounted cause the busy message, but recovery was set with system not writeable before and that caused error 7
to get past error 7 needed to take check mark off "mount system read-only"
Click to expand...
Click to collapse
Recovery should never be set ro on system.
Anyway you have it figured out.
Sent from my BLU ENERGY X PLUS using Tapatalk
Flashed it and it works sdly oukitel 10000 does not have a Nougat or a cm13 from what i can see or even an MIUI 8(that would of been a sweet rom to this devices)
PS Also avoid using xposed , some xposed modules will crash the system.ui thus forces you to have to boot back to rec. to start over with the rom. Just a heads-up.(specially for Android N-Ify xposed module lovers like me)....but version 615 worked without crashing the systemUI but bugs in icons(quicksettings) some work some crashes the system but it bring you back to the lockscreen without crashing the hole thing. In other words best to avoid xposed with this rom.
Even though we can't get source compiling to work, it's good to see some sort of ROM for this thing anyway. Good job vamp! Downloading now, can't wait to flash it.
EDIT: Hey would you look at that, FM works!!!
EDIT 2: After fairly extensive use, I've found that both LTE and video recording (with the built in app anyway) don't work. I had an issue with Assistive Touch (I think it was called that) repeatedly crashing, but that can be solved by getting a root uninstaller and outright uninstalling it.
jasonmerc said:
EDIT: Hey would you look at that, FM works!!!
Click to expand...
Click to collapse
You mean like FM radio? If so, then I will have to switch: ).

Categories

Resources