Related
Sorry if it is a silly question. I am new to installing new ROM and flashing stuff. I have come across the thread on TWRP recovery where it says that to install it, we have to flash it from other recoveries(i.e. CWM or AmonRA). What if I have none of these? Should I install one of them at first place and then proceed to flash TWRP or, there is some other way out? Thanks.
flash_image, Flash Image GUI, fastboot, another recovery, LGMDP.exe for unrooted phones. Read the sticky threads.
Sent from my LG-P500 using XDA App
dr.notor said:
flash_image, Flash Image GUI, fastboot, another recovery, LGMDP.exe for unrooted phones. Read the sticky threads.
Sent from my LG-P500 using XDA App
Click to expand...
Click to collapse
Thanks Sir for your quick response. Will go through it.....
developer++ said:
Sorry if it is a silly question. I am new to installing new ROM and flashing stuff. I have come across the thread on TWRP recovery where it says that to install it, we have to flash it from other recoveries(i.e. CWM or AmonRA). What if I have none of these? Should I install one of them at first place and then proceed to flash TWRP or, there is some other way out? Thanks.
Click to expand...
Click to collapse
root using gingerbreak,download latest rom manger and install clockwork recovery from there - if want to change reovery to twrp just flash from clockowrk recovery after it gets installed
this may help u http://forum.xda-developers.com/showthread.php?t=1038338
make sure usb debugging is enabled while installing custom recovery from rom manger ,make sure u download the latest rom manger from market
welcome to world of custom rom
shhbz said:
root using gingerbreak,download latest rom manger and install clockwork recovery from there - if want to change reovery to twrp just flash from clockowrk recovery after it gets installed
this may help u http://forum.xda-developers.com/showthread.php?t=1038338
make sure usb debugging is enabled while installing custom recovery from rom manger ,make sure u download the latest rom manger from market
welcome to world of custom rom
Click to expand...
Click to collapse
Thanks for the info. Was really a nice descriptive guide for newbies.
One more question. I am on stock froyo 2.2.2 and have flashed TWRP recovery which creates partition in ext4 only. Now I have also flashed Darktremor A2SD which fails to move dalvik to sd card which I assume is because of the ext4 partition that is not recognised by the stock rom. Am I correct with my assumption?
Is flashing another rom is the only way out? If yes, how should I move the existing apps from my stock rom to the new row. Thanks.
Code:
cat /proc/filesystems
will tell you what your kernel supports.
shhbz said:
root using gingerbreak,download latest rom manger and install clockwork recovery from there - if want to change reovery to twrp just flash from clockowrk recovery after it gets installed
this may help u http://forum.xda-developers.com/showthread.php?t=1038338
make sure usb debugging is enabled while installing custom recovery from rom manger ,make sure u download the latest rom manger from market
welcome to world of custom rom
Click to expand...
Click to collapse
This method is not quite OK for me. Did anyone try to actually install that recovery using "Phone Terminal Emulator method"?
I mean this.
adb shell
su (it will ask for root permission in your phone screen just allow)
mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 755 /system/bin/flash_image
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak (you will get an error just proceed)
mount -o remount,ro -t yaffs2 /dev/block/mtdblock1 /system
flash_image recovery /sdcard/LGp500-recovery-v12.img (note just name the blue marked as the same as your custom recovery name and should end with .img)
Click to expand...
Click to collapse
Martin "skunk" Rotter said:
This method is not quite OK for me. Did anyone try to actually install that recovery using "Phone Terminal Emulator method"?
I mean this.
Click to expand...
Click to collapse
Click the link in my signature. There are 3 perfectly working methods to flash recovery. Dunno what the problem really is.
Well, if course i know these methods and i used it many times. Maybe author of this (extremely interesting and incredibly looking) recovery could mention these methods in his thread. I think that only "flash this ZIP via your CWM"-like tutorial is not enough for some users and then they are confused -> and then new threads like this are created.
Martin "skunk" Rotter said:
Well, if course i know these methods and i used it many times. Maybe author of this (extremely interesting and incredibly looking) recovery could mention these methods in his thread. I think that only "flash this ZIP via your CWM"-like tutorial is not enough for some users and then they are confused -> and then new threads like this are created.
Click to expand...
Click to collapse
That thread is a development thread for that particular recovery. There is absolutely no difference when flashing this or another recovery (like AmonRa or CWM.) So, there are enough howtos here (mentioned in the sticky thread that noone reads) to cover flashing recovery.
Development section is for development, not for repeating redundant stuff over and over again.
I get it, but obvíously developer++ doesn't.
Martin "skunk" Rotter said:
This method is not quite OK for me. Did anyone try to actually install that recovery using "Phone Terminal Emulator method"?
I mean this.
Click to expand...
Click to collapse
well that an outdated mwthod and a lengthy procedure so why not use rom manger and get the latest clockwork recovery and easily shift to whichever recovery u are wiling to use
shhbz said:
well that an outdated mwthod and a lengthy procedure so why not use rom manger and get the latest clockwork recovery and easily shift to whichever recovery u are wiling to use
Click to expand...
Click to collapse
There is nothing outdated about the method. And why not use ROM Manager? Because ROM Manager absolutely lacks any sanity checks when flashing recovery. It will happily download incomplete *.img (happens a LOT esp. on 2G/3G) and flash it, making your phone stuck with fastboot.
I have mentioned numerous times that they should distribute a signed ZIP with recovery contained and check the ZIP before flashing. (Even the ZIP format itself has a CRC checks built in if you are too lazy to bother with manifests.)
There are tons of complaints from people all over the board about ROM Manager half-bricking their phones, I am really stunned by the bad design of the feature and lack of action to fix it.
shhbz said:
well that an outdated mwthod and a lengthy procedure so why not use rom manger and get the latest clockwork recovery and easily shift to whichever recovery u are wiling to use
Click to expand...
Click to collapse
Well, but don't you see that problem?
get the latest clockwork recovery and easily shift to whichever recovery u are wiling to use
Click to expand...
Click to collapse
Why this? Some say usual recovery installation methods will work and you say to use this (weird) method. Then you can't wonder, why creator of this thread is confused.
dr.notor said:
There is nothing outdated about the method. And why not use ROM Manager? Because ROM Manager absolutely lacks any sanity checks when flashing recovery. It will happily download incomplete *.img (happens a LOT esp. on 2G/3G) and flash it, making your phone stuck with fastboot.
I have mentioned numerous times that they should distribute a signed ZIP with recovery contained and check the ZIP before flashing. (Even the ZIP format itself has a CRC checks built in if you are too lazy to bother with manifests.)
There are tons of complaints from people all over the board about ROM Manager half-bricking their phones, I am really stunned by the bad design of the feature and lack of action to fix it.
Click to expand...
Click to collapse
yes the problem was there of phone getting into fastboot mode ,but i beieve the problem was later solved and then it worked fine as many users dont follow instruction carefully which land them into probs.yes i do agree on ur internet connection part if that lacks than they need to use adb to get it done.
since,many users are not able to use adb and stuff just bcoz they cannot configure it properly.
so they have these option to do it the easiest way if they are not able to configure adb to work properly.
shhbz said:
yes the problem was there of phone getting into fastboot mode ,but i beieve the problem was later solved and then it worked fine as many users dont follow instruction carefully which land them into probs.yes i do agree on ur internet connection part if that lacks than they need to use adb to get it done.
Click to expand...
Click to collapse
I do not believe they ever changed the ROM Manager design in the way suggested. The problem is with lack of sanity checks, do not blame users for their sucky internet connection.
Martin "skunk" Rotter said:
Well, but don't you see that problem?
Why this? Some say usual recovery installation methods will work and you say to use this (weird) method. Then you can't wonder, why creator of this thread is confused.
Click to expand...
Click to collapse
It depends on the users choice what they choose as we started with thunderg recovery than came the clockwork method and now the twrp method.
there are various threads and discussion on the first two method .
go and read threads as i said is a matter of choice which way u want it to get it done.
so make ur choice in which u are comfortable and confident.
dr.notor said:
Code:
cat /proc/filesystems
will tell you what your kernel supports.
Click to expand...
Click to collapse
the above command gives me the following output:
Code:
cat /proc/filesystems
nodev sysfs
nodev rootfs
nodev bdev
nodev proc
nodev tmpfs
nodev debugfs
nodev sockfs
nodev pipefs
nodev anon_inodefs
nodev rpc_pipefs
nodev inotifyfs
nodev devpts
ext3
ext2
nodev ramfs
vfat
nodev nfs
yaffs
yaffs2
as seen my kernel does not support ext4.
dr.notor said:
Click the link in my signature. There are 3 perfectly working methods to flash recovery. Dunno what the problem really is.
Click to expand...
Click to collapse
Yes, I have been following links from your signature. They are perfectly ok. But the situation I got into was that I flashed TWRP recovery and created a ext4 partition which was the only format supported by TWRP. Then I flashed Darktremor A2SD but it was unable to mount the ext4 partition as such was unable to move dalvik to sd.
Martin "skunk" Rotter said:
Well, if course i know these methods and i used it many times. Maybe author of this (extremely interesting and incredibly looking) recovery could mention these methods in his thread. I think that only "flash this ZIP via your CWM"-like tutorial is not enough for some users and then they are confused -> and then new threads like this are created.
Click to expand...
Click to collapse
Yes, I too think an additional info about the other ways to install recovery as stated by dr.notor would be very much helpful.
And as for creating new threads I sincerely apologize if I have a made a mistake here.
Flash the correct franco kernel, it supports ext4 just fine. (v1 versions are for CM7 6.6.x and stock(-based) GB ROMs only!)
Guys i just start update center on my NEO V and i found that the update to 4.0.4 is there!!
Only for Neo V, Arc S and Ray with 4.0.3 firmware. If somebody have GB, OTA is not update to ICS.
SI 1254-8478_R6D OTA downloaded, but can't install update message after reboot.
Wysyłane z mojego MT11i za pomocą Tapatalk 2
Yes indeed over the air but not with supercharger and modified widgets and music players, i know it because i had that so i must repair with pc companion to clean and original 562 and root again and then do the OTA
and that was... Working !!
upgraded will post comments soon
Cwm recovery should be uninstalled ota update don't give error
Sent from my MT11i using XDA
Really love the new 4 0 4 update, the phone is snappier than the 4 0 3.
how can we obtain FTF file for 4.0.4
yacloo said:
Cwm recovery should be uninstalled ota update don't give error
Sent from my MT11i using XDA
Click to expand...
Click to collapse
How can I uninstall recovery?
http://forum.xda-developers.com/showthread.php?t=1345741
zakk87 said:
How can I uninstall recovery?
http://forum.xda-developers.com/showthread.php?t=1345741
Click to expand...
Click to collapse
total uninstall not neccesary just one file we need
remove that file /system/bin/chargemon
change name of /system/bin/charger to /system/bin/chargemon
be sure file permissions should be rwx-rx-rx- for new /system/bin/chargemon
or can do that via command line such as adb or a terminal emulator
here is to cli commands
mount -o remount rw /system
rm /system/bin/chargemon
mv /system/bin/charger /system/bin/chargemon
chmod 755 /system/bin/chargemon
mount -o remount ro /system
Click to expand...
Click to collapse
Please can someone with unlocked and relocked bootloader tell me that has succesfully done the update?
Sent from my MT11i using XDA
Has anyone tried update phone with rooted ICS 4.0.3 using OTA?
Is root available on 4.0.4 after OTA update?
CJ Grass said:
I am afraid only by installing the whole ROM again.
Or maybe someone know any way to remove CWM?
Click to expand...
Click to collapse
didn't you see my post
it's easy do removing cwm http://forum.xda-developers.com/showpost.php?p=26771166&postcount=10
so we can after that install cwm again on 4.0.4?
yacloo said:
didn't you see my post
it's easy do removing cwm http://forum.xda-developers.com/showpost.php?p=26771166&postcount=10
Click to expand...
Click to collapse
after I write my post i saw your post so i edit my message...
plesan said:
Please can someone with unlocked and relocked bootloader tell me that has succesfully done the update?
Sent from my MT11i using XDA
Click to expand...
Click to collapse
Sent from my MT11i using XDA
yacloo said:
total uninstall not neccesary just one file we need
remove that file /system/bin/chargemon
change name of /system/bin/charger to /system/bin/chargemon
be sure file permissions should be rwx-rx-rx- for new /system/bin/chargemon
or can do that via command line such as adb or a terminal emulator
here is to cli commands
Click to expand...
Click to collapse
unfortunately it does not work.
I'll make a backup
I'll repair my phone,
root,
OTA
CWM
restore data & android.secure :-D
maybe it will work. Or before that i restore phone settings without losing data < not work - it's time to repair .562
yacloo said:
total uninstall not neccesary just one file we need
remove that file /system/bin/chargemon
change name of /system/bin/charger to /system/bin/chargemon
be sure file permissions should be rwx-rx-rx- for new /system/bin/chargemon
Click to expand...
Click to collapse
It's work for me and i can upgrade my phone to 4.0.4 via OTA... Thanks...
Sent from my MT11i using xda premium
I asked something to mates.
If we can install cwm again on rooted 4.0.4 ?
yacloo said:
Cwm recovery should be uninstalled ota update don't give error
Click to expand...
Click to collapse
You mean it does give error? What kind of error?
Pandemic said:
If we can install cwm again on rooted 4.0.4 ?
Click to expand...
Click to collapse
Yes you can.
You also had error for cwm while doing ota?
Hi,
some days ago i brought a new Prestigio Tablet. There was no Root Tool available for this tablet and i did a lot of searching to find a way to achieve root rights.
Today I found a way and want to share my results with you.
The solution is similar to the one described in this Post.
The main difference is the file system of the system image.
In the PMP5080B Rom the system.img is in cramfs and the wendal script unpacks this image onto disk.
The system.img in the PMP5097C is ext3 so you can mount the image directly on a Linux system and copy the Superuser binaries and set the rights with chmod.
copy /B su system\bin\
copy /B Superuser.apk system\app\
chmod -R 0777 system/*
chmod 6755 system/bin/su
chmod 6755 system/app/Superuser.apk
Click to expand...
Click to collapse
after you did this and copied the modified image back into the Temp/Image folder you can use the script to pack the ROM back together.
Now you can flash the new ROM on the usual way like described in the manual.
Hope this helps
Please can you upload the patched image file ..
THX a lot
Here you are:
https://www.dropbox.com/s/lwa1d0v6lotuhwi/rootrom.zip
teddybt said:
Here you are:
https://www.dropbox.com/s/lwa1d0v6lotuhwi/rootrom.zip
Click to expand...
Click to collapse
thx .. i have install the rom but i have no root .....
I checked the uploaded Rom.
The owner of the Superuser files was not root.
Hope this will fix the issue.
Link: https://www.dropbox.com/s/lwa1d0v6lotuhwi/rootrom.zip
Thx Thx Thx... Rooted pmp 5097 now... Your the Best... 1000 Thx
OMG thank you so much for this! I have been waiting a long time for this. You are awesome!
You don't happen to know how to install clockworkmod if its possible do u? Cheers.
Sent from CrazyD's Galaxy II via XDA Android App
Is there any link for this?
I have 1.06 on my tablet and I would like to root it.
I have 1.06 also.
Is there a way to root it?
I found 1.06 root version on a RU site.
This version has 512 MB for apps and later on 1GB for apps ver. should be available.
iJohnny said:
I found 1.06 root version[/URL] on a RU site.
This version has 512 MB for apps and later on 1GB for apps ver. should be available.
Click to expand...
Click to collapse
I installed this onto my 5097 and it hasn't seemed to give me root access at all have i missed something?
smithaz1212 said:
I installed this onto my 5097 and it hasn't seemed to give me root access at all have i missed something?
Click to expand...
Click to collapse
Same problem here
I dont suppose anyone has had any progress with the russian firmware which was posted earlier, still cant seem to gain root access through it for some reason. It might possibly be the same problem as was detailed before in that the owner of the superuser is not root? although i have noticed that there is no superuser app on this firmware, any ideas anyone?
Ok found a firmware that seems to be rooted and is working 100% on my device only small issue is that it is for another tablet (eFun M1005) which seems to be the exact same tablet just rebranded for sale in asia possibly. Anyway:
h t t p ://narod.ru/disk/48873776001.bacdb0ce2f72ba9a6bd089bf055f247a/M1005HN_20120419_V1.0.3_OS4.0_mod_v2.7z.html
As i said is working fine on my tablet and seems to have no problems but i have only tested it for ~1 hour
1.06 root
I found 1.06 root version on a RU site.
This version has 512 MB for apps and later on 1GB for apps ver. should be available.
Click to expand...
Click to collapse
Its no root
I made rooted version of latest v.1.0.6 firmware. But as a new user, I cannot post link
Thanks to daddycruel for posting my link in next post.
Here is the link for download, thank's to gregyk!
http://www.sendspace.com/file/ignk4l
mount
Hi,
I've just downloaded official and rooted 1.0.6 img and I wanted to look into it before flashing. For some reason
Code:
mount -t ext3 -o loop ASBSM1005HN_20120802_V1.0.6.img /mnt
on my box doesn't work (wrong superblock). Did they changed fs or I'm doing something wrong?
BTW thanks for sharing the rom.
Ficik said:
Hi,
I've just downloaded official and rooted 1.0.6 img and I wanted to look into it before flashing. For some reason
Code:
mount -t ext3 -o loop ASBSM1005HN_20120802_V1.0.6.img /mnt
on my box doesn't work (wrong superblock). Did they changed fs or I'm doing something wrong?
BTW thanks for sharing the rom.
Click to expand...
Click to collapse
You must extract firmware file with Wendal RK29xx Image Tools and then you get images (.img) that you can mount in linux (system.img, etc ..).
I rooted like this: extracted firmware with wendal, than mounted system.img in linux - copied "su" and "superuser.apk" and set right permissions to this files. Than packed firmware back together also with wendal tools.
Today I had to send my 5097 for repair ... it won't turn on no more normally. I had to press few times reset, then power and if that didn't work - sometimes it started when I connected it to PC. I tried several different firmwares, but same situation with all.
Anyone heard of or had similar problems?
Finally, I deodex my .290 rom myself.
Here is a CWM zip to DEODEX
IT ISN'T A ROM, JUST DEODEX APP AND FRAMEWORK FOLDER
Require:
1.ROOT
2.Recovery
3.C6833 or C6802
How to use:
Use CWM to flash it.
Download
deodex_290
Special Thanks: dx9901mk5 (Make a TUT for ROOT 4.3 with locked bootloader)
----------------------------------------------------------------------------------------------------------------------------
Finally, I deodex my .532 rom myself.
Here is a CWM zip to DEODEX
IT ISN'T A ROM, JUST DEODEX APP AND FRAMEWORK FOLDER
1. Use CWM to flash it (For Unlocked Bootloader)
or
2. Extract the zip and use ADB pull the file to your device: (For Locked Bootloader)
a. Delete the folder : /app in your internel storage if you have it. (NOT the system/app)
b. Put the folder "app" and "framework" to your internel storage.
c. Use Root explorer to edit system/build.prop
d. Add "ro.secure=0" without the quotes below "ro.build.host"
e. Save and exit.
f. Copy the build.prop from /system to /
g. Connect the phone and follow the step below.
Code:
[COLOR="Blue"]adb shell
su
stop ric
busybox pkill -f /sbin/ric
mount -ro remount,rw /
chmod 0440 /sbin/ric
stop ric
busybox pkill -f /sbin/ric
mount -ro remount,rw /system[/COLOR] ←after you do this, please continue to other steps as fast you can.
[COLOR="blue"]busybox cp -af /build.prop /system/build.prop
rm /build.prop[/COLOR]
mount -o rw,remount /system/ /system/
cp /sdcard/app/* /system/app/
rm /system/app/*.odex ←If your device reboot after this step, Don't worry, wait the device start and redo the blue step to continue.
cp /sdcard/framework/* /system/framework/
rm /system/framework/*.odex
mount -o ro,remount /system/ /system/
reboot
After Deodex, You can use root explorer to edit system apps or framework to theme your rom.
Download Link: http://d-h.st/hJ7
Special thanks: sigma9988(deodex TUT) , juanyunis(fix adb reboot issue)
Nice Work
Just out of curiosity,
How long time did it take?
3lastic said:
Just out of curiosity,
How long time did it take?
Click to expand...
Click to collapse
You mean deodex time or flash the zip's time?
Sent from my C6833 using XDA Premium 4 mobile app
bkk99213 said:
You mean deodex time or flash the zip's time?
Sent from my C6833 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
From start to end ..
3lastic said:
From start to end ..
Click to expand...
Click to collapse
Total: ten hours.
For download the files I need : eight hours
That's because my internet is too cheap.
Sent from my C6833 using XDA Premium 4 mobile app
Thanks for share
Update the method for locked bootloader
Works like a charm in my unlocked device
Thx.....
Sent from my C6833 using XDA Premium HD app
mw1kaduxx said:
Works like a charm in my unlocked device
Thx.....
Sent from my C6833 using XDA Premium HD app
Click to expand...
Click to collapse
So I have an unlocked bootloader.. I just flash this zip and it deodexes my Rom automatically?
I want to try the lenovo Camera App but I know you have to be deodexed first
baileyjr said:
So I have an unlocked bootloader.. I just flash this zip and it deodexes my Rom automatically?
I want to try the lenovo Camera App but I know you have to be deodexed first
Click to expand...
Click to collapse
Yes, just flash in CWM. But the lenovo Camera app is no need deodex, just install like normal apk.
bkk99213 said:
Yes, just flash in CWM. But the lenovo Camera app is no need deodex, just install like normal apk.
Click to expand...
Click to collapse
Cool, I though it was deodex only... At least I know there was something I wanted that was deodex only...... Actually I think it was the Z1 camera app lol
baileyjr said:
Cool, I though it was deodex only... At least I know there was something I wanted that was deodex only...... Actually I think it was the Z1 camera app lol
Click to expand...
Click to collapse
You right. Z1 camera app need deodex and that can take a better photo. But this mod also get more fc when take photo, and cannot restore the stock camera by CWM restore. If you install it and don't like it, you must use flashtool to restore it normal.
So, I wait krabappel2548 update and fix.
bkk99213 said:
You right. Z1 camera app need deodex and that can take a better photo. But this mod also get more fc when take photo, and cannot restore the stock camera by CWM restore. If you install it and don't like it, you must use flashtool to restore it normal.
So, I wait krabappel2548 update and fix.
Click to expand...
Click to collapse
OK thats good to know I'll hold off for now
can this been done on ZU +HSDPA devices - c6802 ?
curiouso9 said:
can this been done on ZU +HSDPA devices - c6802 ?
Click to expand...
Click to collapse
EDIT
may I know can it use for C6833 hk version (4G lte)
or do I need to backup baseband
thanks
toystory said:
may I know can it use for C6833 hk version (4G lte)
or do I need to backup baseband
thanks
Click to expand...
Click to collapse
I'm use HK C6833 in HK. It's not include baseband, so you no need make a backup for baseband.
bkk99213 said:
Cannot. I think the system app is different. You can make the cwm zip youself if you can read Chinese.
Click to expand...
Click to collapse
There is no problem swapping any /system/app between 6833 and 6802 /system/framework ok too.
Sent from my C6833 using Tapatalk
Because I get locked bootloader Root in .290
So, I make a zip to deodex my rom
Update in first post.
^^ thx mate, my deodexing always failed on settings.apk (sort of important app lol)
Update: flashed and all good :thumbup:
Sent from my C6833 using Tapatalk
Hello, im having a couple of problems regarding my filesystem as well as the app supersu and its binary file.
To start, i rooted with kingroot and switched to supersu using terminal emulator commands. There are still kingroot files in my xbin which i will attatch a picture showing the contents of my xbin folder in attatchments (i also have .tmpsu in xbin) please ask if you need more pictures or information of files located in my directories.
The problems i need help with is:
1. I cannot mount /system or any foler in that directory as r/w, i feel that there is a file located somewhere that is preventing me from mounting /system as r/w.
2. I cannot update the su binary, i have tried normal and twrp modes neither work. Ive also tried flashing the UPDATE-supersu-2.78.zip in twrp and that doesnt work either. It says that it installed but nothing changes once i boot back into system, i feel that me not being able to mount /system as r/w is preventing me from updating the su binary.
I need help on how to regain conrtol of my /system and how to update the su binary. Any help? Thank you
Some specs of phone:
Android 5.1
Cpu model - AArch64 processor rev 4
Kernel version - 3.10.65+
Model - blu vivo xl
icy201 said:
Hello, im having a couple of problems regarding my filesystem as well as the app supersu and its binary file.
To start, i rooted with kingroot and switched to supersu using terminal emulator commands. There are still kingroot files in my xbin which i will attatch a picture showing the contents of my xbin folder in attatchments (i also have .tmpsu in xbin) please ask if you need more pictures or information of files located in my directories.
The problems i need help with is:
1. I cannot mount /system or any foler in that directory as r/w, i feel that there is a file located somewhere that is preventing me from mounting /system as r/w.
2. I cannot update the su binary, i have tried normal and twrp modes neither work. Ive also tried flashing the UPDATE-supersu-2.78.zip in twrp and that doesnt work either. It says that it installed but nothing changes once i boot back into system, i feel that me not being able to mount /system as r/w is preventing me from updating the su binary.
I need help on how to regain conrtol of my /system and how to update the su binary. Any help? Thank you
Some specs of phone:
Android 5.1
Cpu model - AArch64 processor rev 4
Kernel version - 3.10.65+
Model - blu vivo xl
Click to expand...
Click to collapse
download root checker from the play store and make sure that u have root access on your device
messi2050 said:
download root checker from the play store and make sure that u have root access on your device
Click to expand...
Click to collapse
It says i have properly installed root access. Something fishy is going on with my root and my system.
icy201 said:
It says i have properly installed root access. Something fishy is going on with my root and my system.
Click to expand...
Click to collapse
then u can try to completely uninstall root from inside super su/king root apps and then reinstall it
messi2050 said:
then u can try to completely uninstall root from inside super su/king root apps and then reinstall it
Click to expand...
Click to collapse
I did try that too, it took around 15-20 minutes to uninstall then when i rebooted the app was gone but my device still had root. I did get it to uninstall root 1 time then i went and flashed the zip file and the same problem occured again. Maybe kingroot just f-ed up my device so root will never work properly again? Maybe a virus? Idk whats going on with it.
icy201 said:
I did try that too, it took around 15-20 minutes to uninstall then when i rebooted the app was gone but my device still had root. I did get it to uninstall root 1 time then i went and flashed the zip file and the same problem occured again. Maybe kingroot just f-ed up my device so root will never work properly again? Maybe a virus? Idk whats going on with it.
Click to expand...
Click to collapse
Your device does not have twrp/cwm port ?
It does, i have twrp(touch) 3.0 for blu vivo xl. Thats the only way i got my device unrooted one time. What i had to do i had to boot into recovery, mount /system, reboot into system then root explorer would allow me to mount /system as r/w but i believe theres a script or something somewhere that is locking the /system into read only mode cause after a short period of time (around 5 minutes or so) i can no longer modify or delete anything in that folder even though it still says its in r/w and if i close root explorer and reopen it it shows that its back in read only mode even though i didnt change it back to that.
Edit: if i mount /system in twrp and boot into system when i boot back into twrp system is not mounted anymore, idk if its supposed to do that or not.
These are the only possible solutions ive been able to find that do kinda make sense.
"It's because you need a boot.img with r.o secure=0 in the build prop" i went and looked and my file says r.o secure=1 that would explain why my system will not mount as r/w.
Another post i found said -
"I've found the source of the problem asking in the MIUI forums, the boot image will not accept a modified /system.
You have to use the adb interface: adb devices then adb disable-verity.
Disclaimer: I'm not responsible for any damage caused by these operations."
The second solution seems more reasonable and alot easier to do. My question now is: will one or both of these solutions possibly fix both my problems? And the second solution disabling verify should that be okay to do without messing up my device? I do have that recovery i could flash but dont wanna do anything that might make the phone not boot into recovery.
icy201 said:
It does, i have twrp(touch) 3.0 for blu vivo xl. Thats the only way i got my device unrooted one time. What i had to do i had to boot into recovery, mount /system, reboot into system then root explorer would allow me to mount /system as r/w but i believe theres a script or something somewhere that is locking the /system into read only mode cause after a short period of time (around 5 minutes or so) i can no longer modify or delete anything in that folder even though it still says its in r/w and if i close root explorer and reopen it it shows that its back in read only mode even though i didnt change it back to that.
Edit: if i mount /system in twrp and boot into system when i boot back into twrp system is not mounted anymore, idk if its supposed to do that or not.
Click to expand...
Click to collapse
Yes that's normal , your problem is because of a buggy root
messi2050 said:
Yes that's normal , your problem is because of a buggy root
Click to expand...
Click to collapse
I just remembered something. I think i know what bugged it. I was trying to do an ota update for my device and it wouldnt let me. I found another app by chainfire called flashfire. I tried to flash the ota update and i had the option "inject supersu" enabled even though i already had supersu installed and everything else i needed for root. I guess doing that messed up all my su files ect.. But how do i fix it? I cant uninstall root cause my /system folder is locked into r/o. If i press full unroot in supersu it will remove the app (although it takes a while!) but all the files needed for root stay.
Guess there just no fixing this phone. Someone really hacked it good i guess, problem is still there and nothing can fix it...
Update - thread can be closed
Problem fixed, to fix the problems i was having i had to download the stock system files for my device and flash them, after that just installed the latest supersu 2.78 zip and remount problem is fixed.