Hi Guys
I wonder if there's anyway to access android root system folder on Windows PC? where the build.prop file is? well the reason is i pretty much screw my build.prop by editing it with a line to remove the soft button on screens. And now my tablet is showing nothing but i can still get it connected through USB.
how about use root explorer and copy the file u want to sd card..then connect sd card to pc..and change whatever u want there..:laugh:
dukesinclair said:
how about use root explorer and copy the file u want to sd card..then connect sd card to pc..and change whatever u want there..:laugh:
Click to expand...
Click to collapse
I think you don't understand what i am trying to say, I meant i can't access my Galaxy Tab now since it's all blank and it is not displaying anything. the reason why it's not displaying anything is because i wanted to remove those on screens buttons and i found out that people said here by adding this script at build.prop qemu.hw.mainkeys=1 and reboot it will remove them. But instead all i get is a blank screen
I wonder if there's a way to access Android root system dir on Windows PC you know the place where you can find the build.prop file.
Can someone help me with this?
Is it rooted??
If it is you could reflash ur Rom without wiping anything. Just flash the same Rom u are currently using and don't wipe anything. When done dix permissions and reboot.
Sent from my HTC Glacier using Tapatalk 2
mickeyasamoah said:
Is it rooted??
If it is you could reflash ur Rom without wiping anything. Just flash the same Rom u are currently using and don't wipe anything. When done dix permissions and reboot.
Sent from my HTC Glacier using Tapatalk 2
Click to expand...
Click to collapse
Yes my Galaxy Tab is rooted with a custom rom installed. i can still access my CWM. Ugh.. i really wonder if it's possible to access the android root system on a PC or not.
I'm not going to reflash it if i could just remove that line i added earlier at build.prop. which is qemu.hw.mainkeys=1 i am hoping that after removing that line might return everything to normal
dc2mx said:
Yes my Galaxy Tab is rooted with a custom rom installed. i can still access my CWM. Ugh.. i really wonder if it's possible to access the android root system on a PC or not.
I'm not going to reflash it if i could just remove that line i added earlier at build.prop. which is qemu.hw.mainkeys=1 i am hoping that after removing that line might return everything to normal
Click to expand...
Click to collapse
Hello bro ... you can access the android root files ( but not view directly as a file manager) and edit the build prop ..... but for this you need android sdk ( android development kit ) on pc through which you can type the adb shell commands for the build prop changes you made... but it still needs usb debugging to be activated...... If you can flash stock rom it is better ...
HIT THANKS IF I HELPED
Sent From My GT-I9082
asifcheer said:
Hello bro ... you can access the android root files ( but not view directly as a file manager) and edit the build prop ..... but for this you need android sdk ( android development kit ) on pc through which you can type the adb shell commands for the build prop changes you made... but it still needs usb debugging to be activated...... If you can flash stock rom it is better ...
HIT THANKS IF I HELPED
Sent From My GT-I9082
Click to expand...
Click to collapse
Hello
I can still access my Tablet through USB mode using CWM to set it on. I wonder if i can see the android root system dir when using android SDK? or i am screwed ? Does the Android SDK really need USB Debug Mode turn on to make changes to the build.prop file? If yes, i wonder is there a way to turn USB Debug mode on at SDK?
Since my tablet is not displaying anything so i can't manually turn it on there.
dc2mx said:
Hello
I can still access my Tablet through USB mode using CWM to set it on. I wonder if i can see the android root system dir when using android SDK? or i am screwed ? Does the Android SDK really need USB Debug Mode turn on to make changes to the build.prop file? If yes, i wonder is there a way to turn USB Debug mode on at SDK?
Since my tablet is not displaying anything so i can't manually turn it on there.
Click to expand...
Click to collapse
Hey... try this link ... it mentions about the kind of software you need ...
http://forum.xda-developers.com/showthread.php?t=1587717
But It would be useless if it asks for root permission on your phone ( as you can't access your screen)
HIT THANKS IF I HELPED
Sent From My GT-I9082
asifcheer said:
Hey... try this link ... it mentions about the kind of software you need ...
http://forum.xda-developers.com/showthread.php?t=1587717
But It would be useless if it asks for root permission on your phone ( as you can't access your screen)
HIT THANKS IF I HELPED
Sent From My GT-I9082
Click to expand...
Click to collapse
Flash the stock build prop back from recovery first..
and reboot.
or
connect the device flash the stock kernel..
You need spend some money to buy one software to slove this problem.
Ebmmki said:
Root android phone ,you will lost all data ,files,apps on android phone
Click to expand...
Click to collapse
Wrong. You don't lose anything rooting unless you use some nonsense.
It's unlocking the bootloader that wipes the phone.
Please learn what you are talking about before posting.
Related
I want to ask something to the teacher who has been adept at breaking into the android system. at some time ago I made a mistake editing build.prop phone models on the line, so I can not connect my phone to pc.
until now the android phone I can only start up in the display logo and can not get into the phone application. another mode can only be entered in fastboot mode.
so my question is:
1. Can I go on my mobile phone and access the system, change the files contained in the system / build.prop?
2. if you could, say, and help me because I was new in the world of android.
thanks for the help and advice ...
ycusoy said:
I want to ask something to the teacher who has been adept at breaking into the android system. at some time ago I made a mistake editing build.prop phone models on the line, so I can not connect my phone to pc.
until now the android phone I can only start up in the display logo and can not get into the phone application. another mode can only be entered in fastboot mode.
so my question is:
1. Can I go on my mobile phone and access the system, change the files contained in the system / build.prop?
2. if you could, say, and help me because I was new in the world of android.
thanks for the help and advice ...
Click to expand...
Click to collapse
Yes u can change build.prop in the phone. Root ur phone and get root explorer and navigate to /system/ . Open build.prop and change whichever values u want
Hit THANKS if I helped you
Sent from my Blade using xda premium
IceCream_Sandwich said:
Yes u can change build.prop in the phone. Root ur phone and get root explorer and navigate to /system/ . Open build.prop and change whichever values u want
Hit THANKS if I helped you
Sent from my Blade using xda premium
Click to expand...
Click to collapse
the problem is I lost the original application from my phone, which I accidentally deleted, so do not get to go to the normal display phone. so I am looking for a way without enabling usb debug I get root access.
anyone know how to get into the system and change any file in there with access to computers without enabling usb debug on android phone ??
ycusoy said:
anyone know how to get into the system and change any file in there with access to computers without enabling usb debug on android phone ??
Click to expand...
Click to collapse
Are you on stock rom or a rooted one? It is possible through recovery. In CWM and 4EXT recoveries, there's an option to mount system. Then you should be able to access it from a pc. In recovery you dont have the ADB option so I guess it'll work. If you're not rooted and do not have custom recovery installed, I don't know. You might also try QtADB program, is like a file explorer on your pc with which you can access phone files in a graphical manner, without need to know ADB commands. You need to have Android SDK installed on your pc for these methods to work
Sent from nowhere over the air...
Rapier said:
Are you on stock rom or a rooted one? It is possible through recovery. In CWM and 4EXT recoveries, there's an option to mount system. Then you should be able to access it from a pc. In recovery you dont have the ADB option so I guess it'll work. If you're not rooted and do not have custom recovery installed, I don't know. You might also try QtADB program, is like a file explorer on your pc with which you can access phone files in a graphical manner, without need to know ADB commands. You need to have Android SDK installed on your pc for these methods to work
Sent from nowhere over the air...
Click to expand...
Click to collapse
hmm .. that's my fault. I forgot to backup the data from the phone. There are two mistakes here that I made:
A. I tried upgrading my android phone to a higher level, but the one included with the correct phone model in the / system / build.prop.
2. I also already remove the formal application in the directory / sytem / app.
therefore, I want to ask if there are other ways that I can use to get to the root without interference adb.exe? for example with special commands in windows or ubuntu, or by flashing using a particular application, or the fastboot command which allows root can be accessed with ease ..
ycusoy said:
hmm .. that's my fault. I forgot to backup the data from the phone. There are two mistakes here that I made:
A. I tried upgrading my android phone to a higher level, but the one included with the correct phone model in the / system / build.prop.
2. I also already remove the formal application in the directory / sytem / app.
therefore, I want to ask if there are other ways that I can use to get to the root without interference adb.exe? for example with special commands in windows or ubuntu, or by flashing using a particular application, or the fastboot command which allows root can be accessed with ease ..
Click to expand...
Click to collapse
Ok... But you can still enter in recovery right? I mean, don't know exactly what phone model you have, but there's power on key combination that usualy allow to boot in recovery. For ex, on Desire S I keep pressed vol-down+ power then select recovery. And from there I can acces system or flash another ROM. You cannot do the same?
Sent from nowhere over the air...
Rapier said:
Ok... But you can still enter in recovery right? I mean, don't know exactly what phone model you have, but there's power on key combination that usualy allow to boot in recovery. For ex, on Desire S I keep pressed vol-down+ power then select recovery. And from there I can acces system or flash another ROM. You cannot do the same?
Sent from nowhere over the air...
Click to expand...
Click to collapse
yup ... It is true bro. I can still access the recovery mode. rom to install it but I always fail. My cell phone specs, Nexian nx-a892. congenital previous 2.2.1 version, then I tried upgrading to 2.2.2 from GSmart G1315 product. Here I make text editing the wrong file build.prop. I change only the G1315 model only, without including the GSmart. Then came the refusal every time I go in recovery mode.
Various tools have been tried, but all to no avail. One way that I think can be done only with fastboot. But until this moment I have not managed to solve the secret of accessing the android system, without the ADB and USB Debug ...
At other times, I had also tried the Linux operating system. Because Android applying the same thinking with linux. but just the same, I stopped in there a way to access the root ...
ycusoy said:
yup ... It is true bro. I can still access the recovery mode. rom to install it but I always fail. My cell phone specs, Nexian nx-a892. congenital previous 2.2.1 version, then I tried upgrading to 2.2.2 from GSmart G1315 product. Here I make text editing the wrong file build.prop. I change only the G1315 model only, without including the GSmart. Then came the refusal every time I go in recovery mode.
Various tools have been tried, but all to no avail. One way that I think can be done only with fastboot. But until this moment I have not managed to solve the secret of accessing the android system, without the ADB and USB Debug ...
At other times, I had also tried the Linux operating system. Because Android applying the same thinking with linux. but just the same, I stopped in there a way to access the root ...
Click to expand...
Click to collapse
anyone can help me ???????:crying::crying::crying::crying::crying::crying::crying::crying::crying:
I'm having the same problem. Can anyone help accessing files on a soft-brick with android stock rom, with USB debugging disabled?
MyTab brick
And what if I have also softbricked tab (Mytab 10 dual core) I have messed up with build.prop file probably but I don't have any bootloader mode or any option like that. Is there any way to get to the Android system files? I have now sent it for a warranty however I'm sure they won't accept it. Tab launches but hungs at boot screen (computer can see it). I have USB debugging off. Any help would be apreciated much
how to make a flashable rom/firmware from the images from romdump.
need it for my rk3188 tablet.
thanks
th3f33 said:
how to make a flashable rom/firmware from the images from romdump.
need it for my rk3188 tablet.
thanks
Click to expand...
Click to collapse
Depends
Whats The Main Device
Screen DPI
Kernel
Droid Version
Pranto Roy said:
Depends
Whats The Main Device
Screen DPI
Kernel
Droid Version
Click to expand...
Click to collapse
Device is:
Skyworth skypad x7010 , rk3188 quad, 2gb ram, 8gb storage
DPI - 160
Kernel - i dont know, still using the stock...
running on jellybean 4.1.1
th3f33 said:
Device is:
Skyworth skypad x7010 , rk3188 quad, 2gb ram, 8gb storage
DPI - 160
Kernel - i dont know, still using the stock...
running on jellybean 4.1.1
Click to expand...
Click to collapse
Is It The main device's or your's??
Pranto Roy said:
Is It The main device's or your's??
Click to expand...
Click to collapse
its mine,
i have stock images from rom dump
but it is soft bricked as of now.. due to some build.prop errors or maybe when i set the cpu minimum frequency state...
.
th3f33 said:
its mine,
i have stock images from rom dump
but it is soft bricked as of now.. due to some build.prop errors or maybe when i set the cpu minimum frequency state...
.
Click to expand...
Click to collapse
If Both Build.prop 's are of same droid version replace it with your phone's
cpu won't Matter
thanks for the replys
Pranto Roy said:
If Both Build.prop 's are of same droid version replace it with your phone's
cpu won't Matter
Click to expand...
Click to collapse
yeah i would really like to do that, to keep my save files in some rpgs i played, but i had this problem where i cant access the tablet thru adb, although i am rooted, usb debugging is on, and have installed the right / working/ correct adb drivers for my device although i was supposed to be able to do it before, i dunno what had happened to it,
maybe it happened somewhere during my initial setup of factory restore - root - clear bloat apps - clear cache - factory restore,
but i can access the tablet with adb when it is turned off, but even though i can access it with adb, cant seem to push any file anywhere, and cant use SU command, it just goes blank, and adb root / adb remount not working too, adb root says cannot run in production build and remount is not having permission.
i also checked the default.prop and it says
ro.secure=1
ro.debuggable= 1
when i check the adb devices when the tablet is off, it says
name - device
no access to recovery mode anymore, can only access the device in off state and flash state, (rkbatchtool flash state - green)
whenever i try to push the recovery button (Power + Volume Up, used to be working before i flashed the incorrect recovery) it ends up in the flash mode.
when the device is turned on and stuck in grey screen after logo, it can be detected in the windows as android adb interface but adb devices doesnt detect the tablet, even after i restart the adb thru adb kill-server adb start-srver
th3f33 said:
yeah i would really like to do that, to keep my save files in some rpgs i played, but i had this problem where i cant access the tablet thru adb, although i am rooted, usb debugging is on, and have installed the right / working/ correct adb drivers for my device although i was supposed to be able to do it before, i dunno what had happened to it,
maybe it happened somewhere during my initial setup of factory restore - root - clear bloat apps - clear cache - factory restore,
but i can access the tablet with adb when it is turned off, but even though i can access it with adb, cant seem to push any file anywhere, and cant use SU command, it just goes blank, and adb root / adb remount not working too, adb root says cannot run in production build and remount is not having permission.
i also checked the default.prop and it says
ro.secure=1
ro.debuggable= 1
when i check the adb devices when the tablet is off, it says
name - device
no access to recovery mode anymore, can only access the device in off state and flash state, (rkbatchtool flash state - green)
whenever i try to push the recovery button (Power + Volume Up, used to be working before i flashed the incorrect recovery) it ends up in the flash mode.
when the device is turned on and stuck in grey screen after logo, it can be detected in the windows as android adb interface but adb devices doesnt detect the tablet, even after i restart the adb thru adb kill-server adb start-srver
Click to expand...
Click to collapse
Complex Problems
Don't Think Can Be Solved At Home
Contact Customers Care
RE:
well i dont think i can do that because
skyworth is a chinese company, and they dont have a good support for the tablets they've released, i cant understand chinese/cantonese/mandarin too
in our local provider, i also have used the most of my warranty,
rooting/flashing the tablet voids the warranty
even though i had sucessfully made them replace my first tablet due to soft-bricking it, all i did is made the tablet bootable only to flashmode, and they didn't even understand/tracked what i had done, all they did was mark the device as faulty mobo then replaced it with a new one,
so right now i am asking for the online community in some help on how to restore it,
oh btw i have the stock romdump images of it. during the state where it is 100% working.
Pranto Roy said:
Complex Problems
Don't Think Can Be Solved At Home
Contact Customers Care
Click to expand...
Click to collapse
can you instruct me on how to make an update.zip that will replace the build.prop with my default build.prop from what ive learned, it is possible to make one right?
th3f33 said:
can you instruct me on how to make an update.zip that will replace the build.prop with my default build.prop from what ive learned, it is possible to make one right?
Click to expand...
Click to collapse
Possible But Can't Say If It Will Work.
Upload Your Build.prop
I'll Be Quite Late Though
Pranto Roy said:
Possible But Can't Say If It Will Work.
Upload Your Build.prop
I'll Be Quite Late Though
Click to expand...
Click to collapse
here it is.. oh i forgot to rename it to build.prop, it is a backup made weeks ago..
'well i've tried adding an update.zip and I dont think i can use it anyways, i think i need to find a way to flash the romdumps that i have.'
th3f33 said:
here it is.. oh i forgot to rename it to build.prop, it is a backup made weeks ago..
'well i've tried adding an update.zip and I dont think i can use it anyways, i think i need to find a way to flash the romdumps that i have.'
Click to expand...
Click to collapse
Allow Me 24 Hours
As Its Mid-Night In My Country I'll Do It Tomorrow
Pranto Roy said:
Allow Me 24 Hours
As Its Mid-Night In My Country I'll Do It Tomorrow
Click to expand...
Click to collapse
ok its already 2:51 am here, cant sleep without my tab running
still reading a lots of forum topics related to my problem...
RE:
I got my access back to the device thru adb
what i did was added the dev id of my device in the adb_usb.ini
now i can push files back to it
now i need to it to the working state
Hello good day,
I have read alot of tutorial but have found none that will help me. I saw a malware installed on my device which was eating up my ram and internet data. I tried to uninstall it most of the times but it keeps on installing itself anytime i enable my data or wifi. I later found out that there was this new files in my phone system storage, that wont allow me to delete it even if am root. i tried to change the permission and still cant . I tried to move all the files in that folder to a different folder leaving the suspicious ones. after moving the ones i know was not a malware to a different folder. my device froze and i couldn't do anything but to restart the device. i did so and that was it. My device always get stuck on the htc logo anytime that i turn it on. Please i really need help on how i can fix this issue and get my phone back to its normal state. I think is not booting because i move all files including the systemUi to a different folder.. the folder was located at (system/app) I created a new folder called appa in the same directory. thinking if i move all the legimate apps to the new folder. i will be able to delete the whole app folder which i left the malwares in. so i can rename the folder i created back to app. But after the moving was successful. my phone froze and thats it.. I need help( [email protected] ) thank you
farrelzamani said:
Hello good day,
I have read alot of tutorial but have found none that will help me. I saw a malware installed on my device which was eating up my ram and internet data. I tried to uninstall it most of the times but it keeps on installing itself anytime i enable my data or wifi. I later found out that there was this new files in my phone system storage, that wont allow me to delete it even if am root. i tried to change the permission and still cant . I tried to move all the files in that folder to a different folder leaving the suspicious ones. after moving the ones i know was not a malware to a different folder. my device froze and i couldn't do anything but to restart the device. i did so and that was it. My device always get stuck on the htc logo anytime that i turn it on. Please i really need help on how i can fix this issue and get my phone back to its normal state. I think is not booting because i move all files including the systemUi to a different folder.. the folder was located at (system/app) I created a new folder called appa in the same directory. thinking if i move all the legimate apps to the new folder. i will be able to delete the whole app folder which i left the malwares in. so i can rename the folder i created back to app. But after the moving was successful. my phone froze and thats it.. I need help( [email protected] ) thank you
Click to expand...
Click to collapse
unless you have some sort of backup, or can find the stock software to put back on, you will not be able to fix it.
next time before doing such a activity like this you should make a nandroid backup and store it to a safe storage that you can restore.....
Sent from my SM-G7102 using Tapatalk
I have the stock rom
bweN diorD said:
unless you have some sort of backup, or can find the stock software to put back on, you will not be able to fix it.
Click to expand...
Click to collapse
Hi ,Actually i found the stock rom from needrom. how can i flash it with it
farrelzamani said:
Hi ,Actually i found the stock rom from needrom. how can i flash it with it
Click to expand...
Click to collapse
I have no experience flashing HTC devices, but the process is usually the same, just the files used change.
There should be some program common for HTC devices to flash.
I would look on some more popular HTC device and see if you can find a guide, and just substitute your firmware instead of theirs.
Thanks
bweN diorD said:
I have no experience flashing HTC devices, but the process is usually the same, just the files used change.
There should be some program common for HTC devices to flash.
I would look on some more popular HTC device and see if you can find a guide, and just substitute your firmware instead of theirs.
Click to expand...
Click to collapse
Is there any way i can push files to my phone via adb. as it wont boot and get stuck on the htc logo. I mean i tried to copy the rom on my sd card so i can flash the phone with it. but my sd card does not show on recovery mode. rather my internal storage does. is there a way i can push file to it via adb./
farrelzamani said:
Is there any way i can push files to my phone via adb. as it wont boot and get stuck on the htc logo. I mean i tried to copy the rom on my sd card so i can flash the phone with it. but my sd card does not show on recovery mode. rather my internal storage does. is there a way i can push file to it via adb./
Click to expand...
Click to collapse
There is but I don't know the proper commands. I think it's something like adb push (push location) (file name)
You may be able to move the file with pc while in twrp by Normal means. I can do it on my phone like that. Internal shows up on pc just like it does when it's booted.
Thank you
bweN diorD said:
There is but I don't know the proper commands. I think it's something like adb push (push location) (file name)
You may be able to move the file with pc while in twrp by Normal means. I can do it on my phone like that. Internal shows up on pc just like it does when it's booted.
Click to expand...
Click to collapse
Thank you. But i have one problem here. I have download java and android sdk manager. but when i connect my phone. it doesnt get detected when i use the command < adb devices >. could it be that usb debugging is not enable? If so then how can i enable it as the boot wont boot but get stuck always on the htc logo
farrelzamani said:
Thank you. But i have one problem here. I have download java and android sdk manager. but when i connect my phone. it doesnt get detected when i use the command < adb devices >. could it be that usb debugging is not enable? If so then how can i enable it as the boot wont boot but get stuck always on the htc logo
Click to expand...
Click to collapse
USB debug is not needed for flashing. If your pic don't see the device in download mode, you will have to look around for some proper drivers. I don't know if adb works in download mode, so there may not be an issue. You need to get the proper flash tool and see if that can connect to your device. Trying to connect with anything else is a waste of time.
bweN diorD said:
USB debug is not needed for flashing. If your pic don't see the device in download mode, you will have to look around for some proper drivers. I don't know if adb works in download mode, so there may not be an issue. You need to get the proper flash tool and see if that can connect to your device. Trying to connect with anything else is a waste of time.
Click to expand...
Click to collapse
Thank you.
How can I get the best flashing tool. As am using htc k touch u9. Please can you give me some tools.
bweN diorD said:
I have no experience flashing HTC devices, but the process is usually the same, just the files used change.
There should be some program common for HTC devices to flash.
I would look on some more popular HTC device and see if you can find a guide, and just substitute your firmware instead of theirs.
Click to expand...
Click to collapse
farrelzamani said:
Thank you.
How can I get the best flashing tool. As am using htc k touch u9. Please can you give me some tools.
Click to expand...
Click to collapse
follow the advice that i gave before ^^^
there is no "best flashing tool" for these situations. there is usually 1 or 2 options of software provided by the manufacturer. one of these you must use, because there is no options, such as tools made by the community.
i have never owned a htc device, so you are going to have to do some searching and reading to help yourself out, unless someone else comes along who can provide specific help.
Hi everyone I just found out a way recently on how to unlock the bootloader without losing data and root Oppo A71 Cph1717 ,but just in case please i encourage you to backup your phone before doing this, i tested this with my own phone and it works so now lets start!!!
1) download and install latest python (ensure to tick the checkbox Add Python x.x to PATH) ------>https://www.python.org/downloads/
2) download and install preloader driver -----> https://drive.google.com/file/d/0B9...dUE/view?resourcekey=0-TN-5Ipeegh7SowX4sduz_g
3) download the latest MTK-client zip --------> https://github.com/bkerler/mtkclient
4) unzip the mtk-client and open the CMD or Powersell inside the extracted MTK-client folder
5) enter the first command -----> python setup.py install ,and wait until the process is done
6) after the installation is done enter the second command ----> pip3 install -r requirements.txt ,wait until the process is done.
7) Now this is the part to where you are going to unlock the bootloader of your Oppo A71
8) enter command -----> python mtk da seccfg unlock it will wait for the phone to be connected
9) Now power off your phone, connect the small part of the usb cable in your phone, hold both up and down volume button and connect the another end of the usb cable to the computer and you will see the process starting after the process is done boot up your phone and the VIOLA!!! you have unlocked your bootloader without losing any data!!,when you see a warning ( your device has been unlocked and cannot be trusted , your device will boot in 5 seconds....) dont worry its very normal , Now lets hop in on how to root your oppo a71 .
Second Rooting your Oppo A71 CPH1717
1) download latest magisk apk and install it on your phone
2) download your stock rom in your PC -----> https://oppostockrom.com/oppo-a71-cph1717
3) and extract the stock rom in your pc
4) now go to developers option of your phone and enable usb debugging and select the type of connection and select MTP while connected in pc
5) copy the extracted boot.img in your internal storage
5) now open magisk app and select install (you can select Preserve AVB option if you want ) then select next and press the Select img and select the boot.img that you copied fron the PC and then press lets go option
6) wait until the patching is done
7) after the process is done, now copy the magisk_patched.img in the pc ( you can find it in your internals download folder)
8) now create a folder in your pc name it Root flash
9) move the magisk_patched.img in the folder that you created and rename it boot (no extension and other things )
10) copy the scatter file,preloader.bin from the extracted stock rom in to the folder that you created (root flash folder)
11) download sp flash tool ------>https://spflashtool.com/download/ ,and unzip it in your pc
12) open the sp flash folder and open flash tool.exe
13) now see scatter-loading file option and click choose go to the created folder( root flash folder) and select the scatter file
14) now untick the preloader but not the boot
15) click the download button , power off your phone ,connect the small part of the usb cable to your phone ,hold the up and down volume button then connect the another end of the usb to the Pc
16) wait until the flashing is done you will receive a green check in the screen ,disconnect your phone from the pc and turn your phone on and VIOLA!!!! your Oppo a71 CPH1717 is now rooted you can check the magisk app if its installed or install root checker
if i did something wrong pls feel free to tell me
PS: only follow this instruction that i created on how to unlock bootloader if your phone is Oppo A71 CPH1717 because if you follow another tutorial for unlocking the bootloader of this phone TRUST me it will going to be fu*ked up!!!!
BTW if you didn't enable the (Allow OEM unlock, but to be sure please enable it) option don't worry its ok trust me ,you can see it too in my screenshot.
you can refer to the screenshots below from my phone for the evidence , i hope this helps others.
Credits to the tool Developer in github: https://github.com/bkerler
Want to try this, but i think its too risky i dont have backup phone. Btw thank you for this.
pullll said:
Want to try this, but i think its too risky i dont have backup phone. Btw thank you for this.
Click to expand...
Click to collapse
Your welcome, btw You can backup just your data because if something went wrong you can redownload the stockrom in the oppo website for free
Anonymous V said:
Your welcome, btw You can backup just your data because if something went wrong you can redownload the stockrom in the oppo website for free
Click to expand...
Click to collapse
Hello sir, what do you think about this tutorial? Do you think this is legit?
pullll said:
Hello sir, what do you think about this tutorial? Do you think this is legit?
Click to expand...
Click to collapse
as i can see in the video its legit he really unlocked,root and install twrp(which i have it too) in the oppo phone but the only thing thats difficult is he uses a test point and to do that you need to open the phone and some tools to do that which is hasle and hard while in my method i directly unlock it you can see in the vid he uses something to activate the test point but in my case i didnt, i just connect my phone and enter the commands and let the tool do the magic we both use the same tool but the only difference is he uses gui version and im using only command prompt version both version of tool is good but for me command prompt version is stable
Anonymous V said:
as i can see in the video its legit he really unlocked,root and install twrp(which i have it too) in the oppo phone but the only thing thats difficult is he uses a test point and to do that you need to open the phone and some tools to do that which is hasle and hard while in my method i directly unlock it you can see in the vid he uses something to activate the test point but in my case i didnt, i just connect my phone and enter the commands and let the tool do the magic we both use the same tool but the only difference is he uses gui version and im using only command prompt version both version of tool is good but for me command prompt version is stable
Click to expand...
Click to collapse
i will follow your tutorial and i'll update here if it's successful. Thanks!
UPDATE: Bootloader successfully unlocked! I will proceed with rooting the phone.
UPDATE: I successfully root the phone. Thank you so much for this tutorial, been waiting for this.
pullll said:
UPDATE: I successfully root the phone. Thank you so much for this tutorial, been waiting for this.
View attachment 5810051
Click to expand...
Click to collapse
wow thats nice congrats on unlocking your bootloader and rooting your phone without losing data glad to help you
Anonymous V said:
wow thats nice congrats on unlocking your bootloader and rooting your phone without losing data glad to help you
Click to expand...
Click to collapse
there's one problem . hmm not actually a problem but there's a red banner on status bar saying "rooting has been detected".
pullll said:
there's one problem . hmm not actually a problem but there's a red banner on status bar saying "rooting has been detected".
Click to expand...
Click to collapse
thats kinda normal ,well yeah im facing the same problem right now but apparently there is no way we can remove that thing i searched every where but no luck but there is a method to remove that but the requirment that it needs doesnt met by our phone, this method needs Edxposed with we cant use because we need our phone to run in android 8/8.1 or higher i tried it with xposed framework but no luck i cant open the app because its not meant for the phone for now im thinking to to build a custom rom to fix this problem i dont know if this is possible but i found something in internet that got my attention im thinking to build (Resurrection remix 7 android 9) because it has a source code but it might take a while because im still studying it for now my twrp is on stanby for flashing and trying any rom that would fit for my phone
Anonymous V said:
thats kinda normal ,well yeah im facing the same problem right now but apparently there is no way we can remove that thing i searched every where but no luck but there is a method to remove that but the requirment that it needs doesnt met by our phone, this method needs Edxposed with we cant use because we need our phone to run in android 8/8.1 or higher i tried it with xposed framework but no luck i cant open the app because its not meant for the phone for now im thinking to to build a custom rom to fix this problem i dont know if this is possible but i found something in internet that got my attention im thinking to build (Resurrection remix 7 android 9) because it has a source code but it might take a while because im still studying it for now my twrp is on stanby for flashing and trying any rom that would fit for my phone
Click to expand...
Click to collapse
hello sir, i know this is out of the topic, just want to ask if you have a working solution to fix null imei after flash?
pullll said:
hello sir, i know this is out of the topic, just want to ask if you have a working solution to fix null imei after flash?
Click to expand...
Click to collapse
can i fix it using a root tool?
pullll said:
hello sir, i know this is out of the topic, just want to ask if you have a working solution to fix null imei after flash?
Click to expand...
Click to collapse
does your baseband isnt working too? if only your imei you can fix it using modem meta or sn write tool i have the same problem null imei here you can try this tutorial
_---------> https://www.hovatek.com/forum/thread-11609.html
Anonymous V said:
does your baseband isnt working too? if only your imei you can fix it using modem meta or sn write tool i have the same problem null imei here you can try this tutorial
_---------> https://www.hovatek.com/forum/thread-11609.html
Click to expand...
Click to collapse
the baseband also unknown.
pullll said:
the baseband also unknown.
Click to expand...
Click to collapse
you can fix the unknown baseband easily using Zarchiver grant root access then go to ROOT/data/nvdata then delete all the files inside it then after reboot them check if it work because it works fine in me while in the case of the null imei you can only fix it using tools like SN writer or Modem meta
Anonymous V said:
you can fix the unknown baseband easily using Zarchiver grant root access then go to ROOT/data/nvdata then delete all the files inside it then after reboot them check if it work because it works fine in me while in the case of the null imei you can only fix it using tools like SN writer or Modem meta
Click to expand...
Click to collapse
will try this. thanks!
pullll said:
will try this. thanks!
Click to expand...
Click to collapse
ok
Anonymous V said:
you can fix the unknown baseband easily using Zarchiver grant root access then go to ROOT/data/nvdata then delete all the files inside it then after reboot them check if it work because it works fine in me while in the case of the null imei you can only fix it using tools like SN writer or Modem meta
Click to expand...
Click to collapse
is nvdata is a folder ? can't find it.
pullll said:
is nvdata is a folder ? can't find it.
Click to expand...
Click to collapse
yes its a folder justv go to root/data/nvdata then go inside it then delete all files inside it