Hi all,
First of all be carefull, Nobody will be responsible for bricking your device but yourself.
I compiled twrp 3.0 for blu advance 4.0 l2 (A030U) https://drive.google.com/open?id=0Bw48RaTkRMm_eTRXVk84aWJTUjA here the sources https://github.com/contrerasojuanc/device_blu_advance_l2_A030U, thanks to @Dees_Troy and its guide on https://forum.xda-developers.com/showthread.php?t=1943625. So, in order to install it on this device, we will need to unlock bootloader (Factory reset needed), and flash TWRP recovery on recovery partition.
Settings -> About device -> Compilation number click multiple times to get new developer options menu.
Enable Unlock OEM.
On terminal:
Code:
adb reboot bootloader
On terminal:
Code:
fastboot oem unlock
On terminal:
Code:
fastboot flash recovery twrp_a030u.img
On terminal:
Code:
fastboot reboot
(Immediately press and hold Volumen + on device until custome recovery shows up.)
In order to achieve root on this device, we need to install from TWRP a Supersu system-mode, available thanks to @mauam, it can be get at https://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120 (I used SR3-SuperSU-v2.79-SYSTEMMODE.zip).
Note that maybe /system need to be mounted as writeable, so first mount System and then, on TRWP's terminal:
Code:
/system/bin/mount -o remount,rw /system
Hope, it can be useful somehow. Any questions, please let me know.
I did everything right but I can not get root
Could you give more detail on how you installed supersu in system mode? I used the command mount -o remount,rw /system (replacing /system with the actual system folder path I found using the mount command in twrp temrinal) BUT discovered system remained read-only and everywhere I searched says you need to have root access to mount it as re-writeable.
I installed the zip you used anyways but am now stuck at the BLU logo screen. What should I do now?
talesgs said:
I did everything right but I can not get root
Click to expand...
Click to collapse
Please give me more details of what was done, in order to try to help
4mand said:
Could you give more detail on how you installed supersu in system mode? I used the command mount -o remount,rw /system (replacing /system with the actual system folder path I found using the mount command in twrp temrinal) BUT discovered system remained read-only and everywhere I searched says you need to have root access to mount it as re-writeable.
I installed the zip you used anyways but am now stuck at the BLU logo screen. What should I do now?
Click to expand...
Click to collapse
The command I used for get writable /system was
Code:
/system/bin/mount -o remount,rw /system
exactly that one, remember that if you are in TWRP you have root access in recovery partition, so /system can be set as writeable from there. Probably you need to flash recovery and system partition again. I have those partitions from my stock device, let me know if want to give it a try.
Did you type any commands before that? I get the error "sh: /system/bin/mount: not found".
It would be great if you could link the stock partitions.
4mand said:
Did you type any commands before that? I get the error "sh: /system/bin/mount: not found".
It would be great if you could link the stock partitions.
Click to expand...
Click to collapse
No command before, this is what I did:
1. In TWRP tap Mount menu, then check "Mount system partition read-only" then check "System", then middle bottom button (Home). (So now we have /system partition mount but as RO)
2. Tap Advance menu, Terminal and type
Code:
/system/bin/mount -o remount,rw /system
3. Now if all goes alright, we should have /system writeable.
4. With /system writeable, tap on Install menu, select the Supersu file (Only this worked for me SR3-SuperSU-v2.79-SYSTEMMODE.zip).
5. Deviced rooted.
Ok, I'll try to upload the partitions tonight, while you could search the rom in web.
contrerasojuanc said:
No command before, this is what I did:
1. In TWRP tap Mount menu, then check "Mount system partition read-only" then check "System", then middle bottom button (Home). (So now we have /system partition mount but as RO)
2. Tap Advance menu, Terminal and type
Code:
/system/bin/mount -o remount,rw /system
3. Now if all goes alright, we should have /system writeable.
4. With /system writeable, tap on Install menu, select the Supersu file (Only this worked for me SR3-SuperSU-v2.79-SYSTEMMODE.zip).
5. Deviced rooted.
Ok, I'll try to upload the partitions tonight, while you could search the rom in web.
Click to expand...
Click to collapse
Yes, what you describe is exactly what I did on a previously stock device, but with the same issue on terminal I posted before. After ignoring that, and sideloading the supersu .zip you used, the device gets stuck on the second BLU logo screen on boot, no hope getting back to system. Hopefully it works the second time around with stock partitions...
4mand said:
Yes, what you describe is exactly what I did on a previously stock device, but with the same issue on terminal I posted before. After ignoring that, and sideloading the supersu .zip you used, the device gets stuck on the second BLU logo screen on boot, no hope getting back to system. Hopefully it works the second time around with stock partitions...
Click to expand...
Click to collapse
Also here
;-;
Blu Advance 4.0 L2 (A030U) rom partitions
Blu Advance 4.0 L2 (A030U) stock rom partitions
HTML:
https://ufile.io/j6925
Inside there is a scatter file to use with flashtools
contrerasojuanc said:
Blu Advance 4.0 L2 (A030U) rom partitions
HTML:
https://ufile.io/j6925
Inside there is a scatter file to use with flashtools
Click to expand...
Click to collapse
rooted? or stock?
talesgs said:
rooted? or stock?
Click to expand...
Click to collapse
Stock
I have a Blu Advance 4.0 L2 (A030L) device, I know it is different, but I dared, now I have a bricking device with this twrp 3.0. Anybody knows somethings about reverse it or if it is possible??
I already gave up doing root does not work
doni.zeti said:
I have a Blu Advance 4.0 L2 (A030L) device, I know it is different, but I dared, now I have a bricking device with this twrp 3.0. Anybody knows somethings about reverse it or if it is possible??
Click to expand...
Click to collapse
Hi, the only way I know would be to flash stock partitions of that device. If you manage to find them in the web, I could tell you how to flash it.
contrerasojuanc said:
Hi, the only way I know would be to flash stock partitions of that device. If you manage to find them in the web, I could tell you how to flash it.
Click to expand...
Click to collapse
thank you for your attention, I'm already trying your recommend, but no success yet. I have the stock, sp-flash and drivers (for win). I think it is any problem with drivers or sp-flash (v5.1712)...
Not working
Hi, I have a BLU Advance 4.0 L2 (A030U) and the TWRP doesn't work in my phone, it boots but the touchscreen isn't working, any suggestion?
UPDATE: I was booting twrp from fastboot because I wasn't able to flash it like is explained here, I think that is why my touchscreen wasn't working, anyways I managed to flash it through SP Flash Tools and It worked but now the root doesn't work, it softbrick the phone everytime I try, I'm able to mount system and all that stuff, everything is successfull but the phone does not boot.
Thank you
.It successfully helped root my Advance 4.0 L 2 A030L in yesterday.
I bad English.
I tried flash superuser.zip(superuser.phh.me_2016-09-23), Magisk-v14.0.zip, SR3-SuperSU-v2.79-SYSTEMMODE.zip, they could root my A030L(stock-V05_GENERIC）
if not fastboot reboot"(Immediately press and hold Volumen + on device until custome recovery shows up.)" , devices will replace your custom recovery automatically during first boot.
Other unimportant: Recovery in A030L also need remount / system, there is not read SDcard (update.zip can be imported in TWRP or OS to internal storage),can't backup userdate.can't input password to read userdate after Encrypted.
update:2017-1007 22:16
SR3-SuperSU-v2.79-SYSTEMMODE.zip looks not work...try next time
2017-1012
SuperSU. ---- Both of these are need: SuperSU-v2.76(or2..79).zip and SuperSU-v2.76(or2.79)-SYSTEMMODE.zip
BLU_A030L_V05_GENERIC i find it in
HTML:
https://plus.google.com/collection/cnwFTB
Ver-V05 can root both ok. Ver-V12 look like something wrong in boot.img,it can only root by Magisk. Maybe you should flash boot.img from ver-V05 if you want use V12.
i have a030u v12 rom. v5generic not work, after install result crash bootlogo loop same make option format... recovery not work! same press up button! after all process not enter in twrp. i test magisk not work customize boot.img flash to sp flash result crash boot! mtk droid not detect my phone too please help me.... very hard root this device!
TianNian said:
Thank you
.It successfully helped root my Advance 4.0 L 2 A030L in yesterday.
I bad English.
I tried flash superuser.zip(superuser.phh.me_2016-09-23), Magisk-v14.0.zip, SR3-SuperSU-v2.79-SYSTEMMODE.zip, they could root my A030L(stock-V05_GENERIC）
if not fastboot reboot"(Immediately press and hold Volumen + on device until custome recovery shows up.)" , devices will replace your custom recovery automatically during first boot.
Other unimportant: Recovery in A030L also need remount / system, there is not read SDcard (update.zip can be imported in TWRP or OS to internal storage),can't backup userdate.can't input password to read userdate after Encrypted.
update:2017-1007 22:16
SR3-SuperSU-v2.79-SYSTEMMODE.zip looks not work...try next time
2017-1012
SuperSU. ---- Both of these are need: SuperSU-v2.76(or2..79).zip and SuperSU-v2.76(or2.79)-SYSTEMMODE.zip
BLU_A030L_V05_GENERIC i find it in
HTML:
https://plus.google.com/collection/cnwFTB
Ver-V05 can root both ok. Ver-V12 look like something wrong in boot.img,it can only root by Magisk. Maybe you should flash boot.img from ver-V05 if you want use V12.
Click to expand...
Click to collapse
[/COLOR]
TianNian said:
Thank you
.It successfully helped root my Advance 4.0 L 2 A030L in yesterday.
I bad English.
I tried flash superuser.zip(superuser.phh.me_2016-09-23), Magisk-v14.0.zip, SR3-SuperSU-v2.79-SYSTEMMODE.zip, they could root my A030L(stock-V05_GENERIC）
if not fastboot reboot"(Immediately press and hold Volumen + on device until custome recovery shows up.)" , devices will replace your custom recovery automatically during first boot.
Other unimportant: Recovery in A030L also need remount / system, there is not read SDcard (update.zip can be imported in TWRP or OS to internal storage),can't backup userdate.can't input password to read userdate after Encrypted.
update:2017-1007 22:16
SR3-SuperSU-v2.79-SYSTEMMODE.zip looks not work...try next time
2017-1012
SuperSU. ---- Both of these are need: SuperSU-v2.76(or2..79).zip and SuperSU-v2.76(or2.79)-SYSTEMMODE.zip
BLU_A030L_V05_GENERIC i find it in
HTML:
https://plus.google.com/collection/cnwFTB
Ver-V05 can root both ok. Ver-V12 look like something wrong in boot.img,it can only root by Magisk. Maybe you should flash boot.img from ver-V05 if you want use V12.
Click to expand...
Click to collapse
---------- Post added at 07:13 AM ---------- Previous post was at 07:13 AM ----------
[/COLOR]
TianNian said:
Thank you
.It successfully helped root my Advance 4.0 L 2 A030L in yesterday.
I bad English.
I tried flash superuser.zip(superuser.phh.me_2016-09-23), Magisk-v14.0.zip, SR3-SuperSU-v2.79-SYSTEMMODE.zip, they could root my A030L(stock-V05_GENERIC）
if not fastboot reboot"(Immediately press and hold Volumen + on device until custome recovery shows up.)" , devices will replace your custom recovery automatically during first boot.
Other unimportant: Recovery in A030L also need remount / system, there is not read SDcard (update.zip can be imported in TWRP or OS to internal storage),can't backup userdate.can't input password to read userdate after Encrypted.
update:2017-1007 22:16
SR3-SuperSU-v2.79-SYSTEMMODE.zip looks not work...try next time
2017-1012
SuperSU. ---- Both of these are need: SuperSU-v2.76(or2..79).zip and SuperSU-v2.76(or2.79)-SYSTEMMODE.zip
BLU_A030L_V05_GENERIC i find it in
HTML:
https://plus.google.com/collection/cnwFTB
Ver-V05 can root both ok. Ver-V12 look like something wrong in boot.img,it can only root by Magisk. Maybe you should flash boot.img from ver-V05 if you want use V12.
Click to expand...
Click to collapse
Hi, in order to know what can be happening, first let's try to flash recovery partition, for that, please follow these steps:
Settings -> About device -> Compilation number click multiple times to get new developer options menu.
Enable Unlock OEM.
On terminal:
Code:
adb reboot bootloader
On terminal:
Code:
fastboot oem unlock
On terminal:
Code:
fastboot flash recovery twrp_a030u.img
On terminal: After write the next command, press enter on your computer and immediately press and hold Volumen + on device until custom recovery shows up.
Code:
fastboot reboot
Related
I tried to change my build.prop file with ROOT EXPLORER to this:
ro.product.model=Desire HD
ro.product.brand=htc_wwe
ro.product.name=htc_ace
ro.product.device=ace
ro.product.board=spade
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.board.platform=qsd8k
ro.build.product=ace
Click to expand...
Click to collapse
in order to able to run apps no compt with desire, but desire HD.
unfortunately, as I saved the file the device rebooted itself and is now stuck in bootloop. (edit: I also can't access recovery for some reason, it's stuck on E:Can't open /cache/recovery/command and doesn't let me flash the update.zip)
I saved a copy of the unedited build.prop file on the SD card.
How is it possible to restore the file into the /system directory (adb maybe)?
Thanks!
*I'm not currently S-OFFed
*I think that a full wipe and reflashing the ROM will solve it, but I prefer not to, unless it is necessary.
edit:
Now that I think of it, is it even possible to edit files in /system while device is booted and not S-OFFed?
Was that the cause of it?
You can restore your old build.prop via ADB while in recovery.
Here it is:
Connect the USB cable while in recovery and use the commands (from command prompt):
1) adb shell
2) su
3) mount -o remount rw /system
4) adb push build.prop /system
And reboot.
b1gdrag0n said:
I tried to change my build.prop file with ROOT EXPLORER to this:
in order to able to run apps no compt with desire, but desire HD.
unfortunately, as I saved the file the device rebooted itself and is now stuck in bootloop.
I saved a copy of the unedited build.prop file on the SD card.
How is it possible to restore the file into the /system directory (adb maybe)?
Thanks!
*I'm not currently S-OFFed
*I think that a full wipe and reflashing the ROM will solve it, but I prefer not to, unless it is necessary.
edit:
Now that I think of it, is it even possible to edit files in /system while device is booted and not S-OFFed?
Was that the cause of it?
Click to expand...
Click to collapse
Just reflash the ROM without wiping
Okay, this one never happened to me, but I can't access my recovery...
I press vol down + power button, and when the /!\ appears, and I press vol up + power button, it's stuck on the:
E:Can't open /cache/recovery/command
and doesn't let me flash the update.zip...
For the same reason, I can't reflash the rom.
Thanks you guys.
What recovery do you have (or had) ?
You tried from the bootloader?
I have CWM 2.5.0.7.
Tried what from the bootloader?
the abd commands?
It says:
adb server out of date. killing...
* daemon started successfully *
- exec 'system/bin/sh' failed: no such file or directory <2> -
Click to expand...
Click to collapse
or did u mean something else?
Well just boot into recovery (the main menu) and then execute the commands.
Oh and also go to the Mount options and mount /system.
Maybe I'm getting something wrong or I don't understand you well, but I can't access the recovery...
I rooted my phone in a pretty old method, and not using UNREVOKED, and in order to get into recovery I used fakeflash.
now, when I try to access recovery, in the bootloader, I press VOL UP + POWER, and now I get stuck on
E:Can't open /cache/recovery/command
Click to expand...
Click to collapse
and it doesn't let me flash the update.zip.
thanks for your help!
Even simpler root than Invisiblek's method for the older versions: If you have already tried that method and now have broken wireless, see Post #2.
Note: A more detailed and user-friendly version of these instructions can be found at: http://www.oppoforums.com/threads/n5206-international-root-instructions.24159
Download http://lum.uk/n3/files/recmodn3.img and http://lum.uk/n3/files/Root_ColorOS_by_tantrums_v2.zip
Copy the rooter onto your SD card.
Boot into fastboot by holding volume up while powering on the phone.
fastboot oem unlock
fastboot flash recovery recmodn3.img
fastboot boot recmodn3.img
Flash the root coloros zip file, reboot and you're rooted.
Note: This is a modified stock recovery that can flash OTAs as well as zips not signed by Oppo. If you prefer TWRP then that is available here: https://dl.twrp.me/n3/. Note that at the time of writing TWRP is unable to flash OTAs.
Thanks to [email protected] for the original root method, Arvin A. [email protected] for the fixing SuperSU to work on ColorOS, and [email protected] for providing the modified N3 recovery.
Restoring stock firmware
Download your chosen firmware and recovery from this thread
Copy the firmware to the root of the internal storage
Take a nandroid backup using TWRP
Reboot to bootloader from within TWRP
Code:
fastboot flash recovery recovery_N3.img
fastboot reboot
adb reboot recovery
Use the stock recovery to flash your chosen firmware
If you are downgrading then wipe data and cache (you did remember to take a nandroid, right?)
Reboot
You are now on stock fimware. Follow the rooting instructions in post #1, and if you wiped you may optionally restore only the data partition from your nandroid backup.
Will memory be erased?
Hi,
So i'm looking forward to root my beautiful Oppo N3.
On my last Phones memory (data and so on) was erased alongside with unlocking the phone.
Will it be the same on this phone so that I have to backup all my data?
Your data will not be erased when rooting or unlocking. Also your warranty will not be invalidated like it is with other manufacturers.
It is, however, always wise to take a backup before anything like this, just in case something does go wrong.
Hi,
I tried rooting my N3 now but i made a mistake by not executing the commands after falshing SuperSU.
That's why my phone is always booting into TWRP. There i tried executing your commands, but apparently the shell refuses to su by throwing exception: "command not found"
Going on with mount-command, it is also giving back an error: "can't find /system in /proc/mounts"
Hope sb could help me now...
EDIT: Solved by installing stock recovery, booting system, and the reflash twrp.
Lum_UK said:
Even simpler root than Invisiblek's method for the older versions: If you have already tried that method and now have broken wireless, see Post #2
Download http://teamw.in/project/twrp2/282 and http://download.chainfire.eu/supersu
adb reboot bootloader
fastboot oem unlock
fastboot flash recovery openrecovery-twrp-2.8.4.0-n3.img
fastboot reboot
adb reboot recovery
Flash Super SU from within TWRP. Then boot the OS
adb shell
su
mount -o remount,rw /system
echo "/system/xbin/su --daemon &" >> /system/etc/init.qcom.post_boot.sh
Reboot and you're rooted.
By default ColorOS doesn't let apps auto-start themselves, so go into security centre and allow SuperSU to auto-start, otherwise you won't get prompts for root when other apps need it.
Thanks to invisiblek for the original root method and babelmonk for the fix. I have shamelessly copied these and adapted them for the new firmware.
Click to expand...
Click to collapse
Quoted from your post in oppo forum
Wait for the phone to boot:
adb reboot recovery
It should boot into TWRP recovery flash the SuperSU zip you downloaded but do not reboot as we need to fix a small bug in SuperSU due to Oppo not using the expected startup scripts.
adb shell
su
mount -o remount,rw /system
echo "/system/xbin/su --daemon &" >> /system/etc/init.qcom.post_boot.sh
Reboot and congratulations. You are now rooted.
Sorry , quite new in fastboot command so i apologize if I misunderstood you but I'm running on N5206_EX_23_150208 , which should i follow ? to boot up after flashing SuperSU or not to boot up ?
It doesn't matter which way around you do it, just that root won't work outside of ADB until it's done.
I assume that XDA folk are more familiar with ADB etc. than on the Oppo forums so the instructions skip over more detail here.
Updated the method to use fastboot boot instead of fastboot flash.
This should work around the issue with phones that can't flash twrp, and also leave the stock recovery in place which is more useful to have until we get some custom roms.
Lum_UK said:
Updated the method to use fastboot boot instead of fastboot flash.
This should work around the issue with phones that can't flash twrp, and also leave the stock recovery in place which is more useful to have until we get some custom roms.
Click to expand...
Click to collapse
I was using modified boot.img to get root and then edit init.qcom.post_boot.sh. Now my wi-fi is broken. Can I fix it without wiping? Maybe flash some other boot img?
Anilexis said:
I was using modified boot.img to get root and then edit init.qcom.post_boot.sh. Now my wi-fi is broken. Can I fix it without wiping? Maybe flash some other boot img?
Click to expand...
Click to collapse
Fixed it by flashing boot.img from 150208, root still there due to script edit.
Updated the OP to use the modified stock recovery (Wmjan's recovery for the N5207) as this will be friendlier to noobs and also make it easier to install OTAs.
Anyone know where to get the root coloros file? Link doesn't seem to work for me...
http://www.oppoforums.com/attachment..._v2-zip.31142/
cowabunga said:
Anyone know where to get the root coloros file? Link doesn't seem to work for me...
http://www.oppoforums.com/attachment..._v2-zip.31142/
Click to expand...
Click to collapse
Sorry for the delay in replying. I've re-hosted the file for you.
http://lum.uk/n3/files/Root_ColorOS_by_tantrums_v2.zip
You could also try this. It worked on my girlfriend's R5 running a similar version of ColorOS. Didn't need modified recovery or anything, install it, run, click the root button, and it'll reboot to recovery and root for you.
http://lum.uk/n3/files/ForceRoot.apk
can this root work with Chines n5207
Hello,
I'm from Malaysia,
I got problem with my N3 / N5206 after update the newest version of software...now it cannot detect any line signal and open a wifi...what the problem,can u help me...
I can't make the WiFi to work again. Installed all versions of firmware and no luck....
Update: I was using the wrong tool to flash the firmware.
Don't update the phone with Msm8974DownloadTool !!!!
You have to download and install QPST_2.7.460 and place the phone in download mode by pressing volume + and power button and then in QPST load the firmware N5206EX_11_A.11_150528_SVN6225 or Oppo_N3_N5206_EX_11_A.13_151230 or N5206EX_11_A.10_150519_SVN6196
After flashing the wifi is working but you gonna loose the NV ram backup for the IMEI numbers..
Then you have to open dealpad with *#801# and anable Full-port ON
In QFIL(QPST) click on Tools then click QCN Backup Restore
Choose the qcn file and press restore.
Everything will work again after reboot the phone...
I accidentally permitted ota update to 18s. Now the phone is stuck on twrp screen and does not boot any system. Tried to install back rusch rom from twrp but still get to twrp only... any help would be very appreciated..
vladkon1 said:
I accidentally permitted ota update to 18s. Now the phone is stuck on twrp screen and does not boot any system. Tried to install back rusch rom from twrp but still get to twrp only... any help would be very appreciated..
Click to expand...
Click to collapse
Maybe you could fix this by using TWRP terminal commands, and enter the following:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
Click to expand...
Click to collapse
Reboot.
Good luck
Thank you for your reply!
tried to do it but after
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota i got error :
can't open /dev/block/platform/msm_sdcc.1/by-name/fota no such file or directory
any ideas?
Checked in file manager - under /dev/block/platform i have only /f9824900.sdhci and not /msm_sdcc.1 . Also under mount - system partition is not checked, when I check it and reboot it is still get unchecked. Any advise?
vladkon1 said:
Checked in file manager - under /dev/block/platform i have only /f9824900.sdhci and not /msm_sdcc.1 . Also under mount - system partition is not checked, when I check it and reboot it is still get unchecked. Any advise?
Click to expand...
Click to collapse
Copy Stock Rom (older release is better)to the phone's root, then Wipe Dalvik/Cache. Return to Stock recovery and try to flash it, maybe it will fix the boot issue.
nsmsdz said:
Copy Stock Rom (older release is better)to the phone's root, then Wipe Dalvik/Cache. Return to Stock recovery and try to flash it, maybe it will fix the boot issue.
Click to expand...
Click to collapse
Already tried 13s official. Also tried to restore from system backup... still twrp bootloops...
I get my mobile back from lg repair service with a new mainboard.
I unlock the bootloader, flash twrp and reboot into recovery.
But twrp only shows erroros..i test du flash magisk but dont work...i test flash SuperSu, the installer shows install but after boot no root and twrp replace with stock recovery.
/system /data (& int.Sd) /externalSD and /cache are not mountable...adb sideload dont work too.
But i can push files over adb push to /cache an flash them
ElRongMcBong said:
I get my mobile back from lg repair service with a new mainboard.
I unlock the bootloader, flash twrp and reboot into recovery.
But twrp only shows erroros..i test du flash magisk but dont work...i test flash SuperSu, the installer shows install but after boot no root and twrp replace with stock recovery.
/system /data (& int.Sd) /externalSD and /cache are not mountable...adb sideload dont work too.
But i can push files over adb push to /cache an flash them
Click to expand...
Click to collapse
How much they asked to repair that phone?
Janis2017 said:
How much they asked to repair that phone?
Click to expand...
Click to collapse
Nothing..bring it back coz usb-plugin was damaged and cant charge my phone..
I get a new board with new s/n imei, and between the stepes wipe&restore aboot for unlocking boatloader by laptop goes power off so i brick it.
Take it back to shop say after repair it makes nothing anymore aand after a few days my phones comes back again with a new board with new s/n and imei..so now we are here
Finaly i found on weekend a soloution how i can root my device without twrp and it may work on other versions without working twrp.
Steps i do...(with linux (on raspberry pi) coz LGLAF dont regnotize my device after unlocking bootloader, reboot and come back to download modus)
1. Unlocking bootloader from this tutorial:
https://forum.xda-developers.com/lg-k10/how-to/guide-unlock-bt-install-twrp-download-t3574701
2. Making backup from boot:
"python partitions.py --dump boot.img boot"
and reboot my phone
3. Pushing the boot backup to my phone
"adb push boot.img /sdcard"
4. Install the the MagiskManger from this thread (very great tool)
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
and open it
5.After downloading magisk into MagiskManager and patch my boot.img from internal SD i get a patched boot.img
"/sdcard/MagiskManager/boot_patched.img"
6.Copy the patched Image to the PC
"adb pull /sdcard/MagiskManager/boot_patched.img /boot_patched.img"
and goes to download mode.
7. I restore the boot_patched.img to boot
"python partitions.py --wipe boot && python partitions.py --restore boot"
and YEAH...after reboot my phone is rooted
When I was in operator shop, where I purchased it, they said nobody will fix that for free. not my problem that they make low-quality devices even if its water or screen.
Phones value is now half less than when I get it. Now I will be happy living whit no mobile phone.
https://photos.app.goo.gl/orW6KGp3kTer14rq1
Hello mates.
I Did this exactly like the tutorial says:
NUBIA RED MAGIC 5G UNLOCK BOOTLOADER
1. Connect your Nubia in laptop, in your laptop, open Minimal ADB and Fastboot and type the following:
a. adb reboot bootloader
b. fastboot oem nubia_unlock NUBIA_NX659J
c. fastboot flash recovery recovery-TWRP-3.4.1B-0324-NUBIA_REDMAGIC_5G-CN-wzsx150.img
d. fastboot flash vbmeta vbmeta_BL_skip.img
e. fastboot flash modem NON-HLOS.bin
f. fastboot flash parameter parameter.img
2. Go to your RM5G, select reboot to recovery
3. It will reboot in TWRP twice, in the 2nd reboot it will stay in TWRP, change the language to English and select the keep read only.
4. Go to WIPE option, then select FORMAT DATA, type yes
5. Press home button, then go to REBOOT, select REBOOT to RECOVERY
NUBIA RED MAGIC 5G ROOTING PROCEDURE
6. Go to ADVANCED, below there are list, select INSTALL ROOT.
7. Reboot your RM5G.
-----------------------------------------------------------------------------------------------------
Everything went fine, it booted, magisk says it has root, root checker also says i have Root.
However...
When i go to a Root Explorer, i can't delete anything, i can't change permissions, can't mount read/write, can't change mixer_paths.xml or replace it because it says it's Read Only "and can't mout read/write option".
And, when i go to the Fastboot of the phone, the counts are:
Boot Root - 1, Device Root - 1, but System Root - 0.
This means, i have root in my device, but not on the System partition. It's like having no Root at All.
What Can i Do?,
Must be Something Wrong :-S.
I'm on version 4.11 of European Rom, the same happened on the 4.09 version.
Thanks
Crazy Seed said:
Hello mates.
I Did this exactly like the tutorial says:
NUBIA RED MAGIC 5G UNLOCK BOOTLOADER
1. Connect your Nubia in laptop, in your laptop, open Minimal ADB and Fastboot and type the following:
a. adb reboot bootloader
b. fastboot oem nubia_unlock NUBIA_NX659J
c. fastboot flash recovery recovery-TWRP-3.4.1B-0324-NUBIA_REDMAGIC_5G-CN-wzsx150.img
d. fastboot flash vbmeta vbmeta_BL_skip.img
e. fastboot flash modem NON-HLOS.bin
f. fastboot flash parameter parameter.img
2. Go to your RM5G, select reboot to recovery
3. It will reboot in TWRP twice, in the 2nd reboot it will stay in TWRP, change the language to English and select the keep read only.
4. Go to WIPE option, then select FORMAT DATA, type yes
5. Press home button, then go to REBOOT, select REBOOT to RECOVERY
NUBIA RED MAGIC 5G ROOTING PROCEDURE
6. Go to ADVANCED, below there are list, select INSTALL ROOT.
7. Reboot your RM5G.
-----------------------------------------------------------------------------------------------------
Everything went fine, it booted, magisk says it has root, root checker also says i have Root.
However...
When i go to a Root Explorer, i can't delete anything, i can't change permissions, can't mount read/write, can't change mixer_paths.xml or replace it because it says it's Read Only "and can't mout read/write option".
And, when i go to the Fastboot of the phone, the counts are:
Boot Root - 1, Device Root - 1, but System Root - 0.
This means, i have root in my device, but not on the System partition. It's like having no Root at All.
What Can i Do?,
Must be Something Wrong :-S.
I'm on version 4.11 of European Rom, the same happened on the 4.09 version.
Thanks
Click to expand...
Click to collapse
[emoji23][emoji23] the time you took to explain us the issue.. you could have researched a bit more about magisk. Magisk is a systemless root which doesnt let you modify system. Thats how magisk is safer than other roots.
Sent from my NX659J using Tapatalk
raumyasarkar said:
[emoji23][emoji23] the time you took to explain us the issue.. you could have researched a bit more about magisk. Magisk is a systemless root which doesnt let you modify system. Thats how magisk is safer than other roots.
Sent from my NX659J using Tapatalk
Click to expand...
Click to collapse
Lol, always like to explain the issue with all details so that i dont have answers questioning me "did you do this?, Try doing this... Etc" instead of giving direct answer to the problem.
Not everyone is developer or expert in the subject, so things like searching for magisk would not occur to me xD.
But, i still didnt get the answer i was hoping for, still dont know how to root system or if it is even possible to do it in this phone.
Tried supersu also, didnt work either, will try again.
Any tips?
I'll hit thanks if answer is helpful yes xD.
Crazy Seed said:
Lol, always like to explain the issue with all details so that i dont have answers questioning me "did you do this?, Try doing this... Etc" instead of giving direct answer to the problem.
Not everyone is developer or expert in the subject, so things like searching for magisk would not occur to me xD.
But, i still didnt get the answer i was hoping for, still dont know how to root system or if it is even possible to do it in this phone.
Tried supersu also, didnt work either, will try again.
Any tips?
I'll hit thanks if answer is helpful yes xD.
Click to expand...
Click to collapse
Nope if you tried supersu and didnt work then the only option is change folder read write access through adb command i think, with codes being 777(please search google i dont remember those) for all access but that thing is risky. Also i think these permissions can be edited with root explorer app to get access. Also i really dont have any idea what thanks button does [emoji51][emoji51]
Sent from my NX659J using Tapatalk
raumyasarkar said:
Nope if you tried supersu and didnt work then the only option is change folder read write access through adb command i think, with codes being 777(please search google i dont remember those) for all access but that thing is risky. Also i think these permissions can be edited with root explorer app to get access. Also i really dont have any idea what thanks button does [emoji51][emoji51]
Sent from my NX659J using Tapatalk
Click to expand...
Click to collapse
I tried flashing supersu.zip instead of doing the "Install Root" option of the Twrp that installs Magisk, it flashes yes but when i boot phone there's no root or superuser app available. So i think there's no SuperSu for this phone unfortunatly :-S.
Chmod -R 777 code didn't work, after i input the code it shows everything still as Read Only on the terminal, so there was no effect.
On Root Explorer, i also tried to click the "R/W" button on top, but it doesn't do anything, tried to change the Permissions and was also denied.
So now, i think the only solution possible is, by a Magisk Module.
But... i think there's no module available to change permissions, mount r/w, edit files on /system or just Replace Files.
In my case, I just wanted to edit the file "Mixer_Paths.xml" for boosting the volume of Calls and Headphones, not Speaker because that is already too Loud.
I copied the Mixer_Paths.xml to my computer and was able to edit the values there, but i can't replace these edited file for the one on the Phone because it always shows the Read Only error so i can't Copy/Paste anything on the Root folder
I was able to Adb Push and Pull that file into the phone while being on Recovery "Twrp", but, after i reboot... everything was back to normal like i it didn't changed anything at all
This is confusing
Is there any way or MOD just to boost volume on Magisk?
I think i'll question that on another thread xD.
Thanks anyway