I've been trying to reflash OrangeFox without success (ofoxginna2). I assume it's not reflashed because i had deleted the magisk addon folder while trying to solve the "missing magisk. quitting! " error when trying to install it (see orangefox thread post ) and after i "fastboot flash recovery2.img i get the same magisk manager error described here:
the install addon manager says "File Doesn't exist! Please reflash recovery using the installation zip"). If i then go to /sdcard and pick ofoxginna2.zip, i run into the same "magisk is missing error".
At this point, i'm trying to get back to the original issue (after first time flash) of the magisk manager install giving an error due to corrupt zip (somethng deeper about missing keys).
Should i try to:
1) fastboot flash the ofoxginna.zip (without touchscreen support) and then flash ofoxginna2,zip again?
2) blank flash the recovery ( haven't found the steps to do this)
3) flash the recovery from the stock rom (here again not sure how to do this).
thanks.
Wow, that's hard to follow.
If the recovery zip is giving you trouble, don't use it. Take ofoxginna2.img and boot it with fastboot. You can try flashing it as well, but it's really a waste of time bothering.
If your having trouble flashing the magisk recovery installer, don't use it either. Dump your boot image, patch it in Magisk Manager, and flash it in fastboot.
You seem to be getting caught up on little steps. Can you give me a better idea of where your at and what works and what doesn't? Your still trying to boot the nogapps build, and you just have no idea how to place that file, or what?
For your question on how to get back, boot recovery
Code:
fastboot boot ofoxginna2.img
Then format data, reflash lineage, and reboot.
If you wanted to get touch working through Magisk, you'd need an OTG cable and mouse to do it easily. You'd install Magisk Manager, patch that image I shared, and then flash it.
Code:
fastboot flash boot magisk_patched.img
Then you'd install the module I shared and reboot.
But if you don't have have an OTG cable, flash the boot image, Magisk is optional. Boot ofoxginna2, press the button on the bottom right, choose mount, and check the box for vendor. Then you pull up a root shell on your computer with "adb shell".
Code:
mount -o rw,remount /vendor
Then you can extract the module and push the firmware to the phone.
Code:
adb push chiptone-tianma-ICNL9911C-0288-0000-ginna.bin /vendor/firmware/
And reboot.
Please don't make any more threads. Ask questions or for help instead.
Related
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...
Tried to flash flash ob 10, but twrp said the zip was corrupted. I could not boot into the system anymore.
The problem is the system partition is ok ( verified from twrp file manager), but every time I choose reboot system, it will go back to twrp. I tried to re-flash ob 9, but twrp again reported another error. Log is attached. How should I solve the problem?
By the way, I wipe all data, including storage in twrp by mistake. Is there any way to recover the data? I am traveling now, just got several hundred pictures.:crying::crying: It seems to be impossible to do it on a computer in MTP mode, but I could not boot into the system neither.
Download the modded twrp from here and install it. Use it to flash community builds and all other roms from now on.
About the file recovering part, I wouldn't know.
You need to flash stock recovery, ADB sideload the official Open Beta, and boot into ROM.
By any chance, did you trigger an OTA update with TWRP installed?
zTweaked said:
Download the modded twrp from here and install it. Use it to flash community builds and all other roms from now on.
About the file recovering part, I wouldn't know.
Click to expand...
Click to collapse
I am always using the modified one. I am encountering a weird error.
The message is like
'E: unknown command [log]
........
script succeeded: result was [1.000000]'.
Update: flashing stock recovery seems to be effective ( of course, twrp does not exist anymore ).
SoybeanYoung said:
I am always using the modified one. I am encountering a weird error.
The message is like
'E: unknown command [log]
........
script succeeded: result was [1.000000]'.
Click to expand...
Click to collapse
Unknown command is a known and harmless issue on all 7.x.x roms. Just ignore it and go ahead.
And I think I saw 3.0.2-1 twrp version in your log.
---------- Post added at 09:20 AM ---------- Previous post was at 09:18 AM ----------
pmbabu said:
You need to flash stock recovery, ADB sideload the official Open Beta, and boot into ROM.
By any chance, did you trigger an OTA update with TWRP installed?
Click to expand...
Click to collapse
Open Beta builds can be flashed via modded twrp, no need to use stock recovery and adb sideloading. Plus even if he installed an OTA update, it won't get installed on twrp ~ and no harm will be done.
After you flash any rom, reflash recovery. Reboot to RECOVERY & then to system.
The red message it's on almoust every Nugat rom. And it's about some log .
zTweaked said:
Open Beta builds can be flashed via modded twrp, no need to use stock recovery and adb sideloading. Plus even if he installed an OTA update, it won't get installed on twrp ~ and no harm will be done.
Click to expand...
Click to collapse
He said he could only boot into twrp. That occurs (reboot to system will take it back to twrp over and over) only if someone tried an OTA update with twrp.
I don't think this is the case for you, but if you tried the other suggestions don't work try the below. I had a similar issue and found that my recovery partition was corrupted. However, an additional symptom I had was that my TWRP would hang completely when selecting reboot after any successful flash. I think modded TWRP does not like internal storage wipe from within TWRP (rather than through fastboot format userdata).
Boot to fastboot
Fastboot erase recovery
Fastboot flash recovery filename.img
Boot to recovery and flash your desired ROM+supersu which you can sideload via MTP (drag and drop from Windows) or adb push C:\SourceLocation\filename.zip /sdcard
I recommend ADB push over MTP.
Had the exact same problem as op, after some issues i was forced to use the unbrick method to get phone back as it wasn't even booting. Now im using beta 10 perfectly.
Did you manage to fix it? I have the same probem.
I have attempted to flash Magisk in the past to see if it will work. It never did. The FireTV would just bootloop. I have always been able to boot back into recovery and flash the original boot image and then SuperSU to get back to normal. The latest Magisk 16.3 renders the FireTV unbootable. Luckily I had a USB A-A cable to fix it. AFAIK, Magisk can only work on Fire TVs with fully unlocked bootloaders, so I suggest only Fire TV 1 users attempt this.
In case you want to experiment:
Prepare:
Extract the bootloader_unlocked.img from the latest rom, assuming that's the one you have installed.
Send it to your FireTV using adb push boot_unlocked.img /sdcard/.
Put Magisk ZIP on the sdcard folder, too.
Put the latest working SuperSU ZIP on /sdcard too.
To install Magisk:
Reboot to recovery.
Install the boot_unlocked.img to the boot partition using TWRP.
Hit the escape key to back out and install the Magisk ZIP file.
Reboot the system.
To restore SuperSU, follow the directions for installing Magisk, but use the SuperSU zip file.
To recover from a brick:
Attach the FireTV to your computer with a USB A-A cable.
Go to the directory where the boot_unlocked.img file is located.
Run the following command: fastboot flash boot boot_unlocked.img
When it's done, reboot the FireTV.
Just tried Magisk 18.1 since it supports older versions of Android but it also bricks the device.
tried to replace SuperSU with Magisk via TWRP.
Magisk won't take by itself.
Removed SuperSU. Tried again. Still NG.
"adb reboot recovery" back to TWRP and flashed SuperSU. I have root back, though I don't see SuperSU in the app drawer.
The info to install Magisk leave a bit to be desired.
"install manually" what does that mean?
Remove root (SuperSU) seems to prevent one from installing Magisk, though I did "adb reboot recovery" to get the re-install of SuperSU done.
In the long run, I want to update our other H811 to 20x from 20q. Thats' what started me down this track.
Any input?
Did Magusk Zip Got Trough without any issues in TWRP?
Did you have the magisk App in drawer after flashing Magisk?
Magisk manager is sometimes an older version, so you have to go to magisk manager (app) open ist and click on upgrade or install upgrade.
sometimes my device needed 2installations. one in twrp an another in MAgisk app. but both were v16.0 zip.
no & no. "updater process ended with ERROR: 1
Error installing zip file '/external_sd/Magisk-v16.0.zip'
Tried installing Magisk Manager, which went ok. And then Magisk from that. Error.
"Boot image patched by other programs (SuperSU, perhaps?)
Please restore stock boot image."
So I ran the script that removes SuperSU.
Tried install again from MM.
"Select stock boot image dump in .img or .img.tar format."
No idea where to find that.
Tried this method.
NG. SuperSU doesn't show in app drawer, though it appears to be working as I can reboot recovery from the phone without going into Terminal and adb.
metropical said:
no & no. "updater process ended with ERROR: 1
Error installing zip file '/external_sd/Magisk-v16.0.zip'
Tried installing Magisk Manager, which went ok. And then Magisk from that. Error.
"Boot image patched by other programs (SuperSU, perhaps?)
Please restore stock boot image."
So I ran the script that removes SuperSU.
Tried install again from MM.
"Select stock boot image dump in .img or .img.tar format."
No idea where to find that.
Tried this method.
NG. SuperSU doesn't show in app drawer, though it appears to be working as I can reboot recovery from the phone without going into Terminal and adb.
Click to expand...
Click to collapse
You should Always search the TWRP errors you have, that gives you more info.
Error 1 means on your system partition is not enough space anymore, so delete or Freeze some bloatware/apps and it should go trough.
boot.IMG files are containt in KDZ (firmware files).
Maybe you should visit https://******************/
and read trouh installation (with pictures) for better understanding.
uweork said:
Maybe you should visit https://******************/
and read trouh installation (with pictures) for better understanding.
Click to expand...
Click to collapse
went and posted in digeridoohan original thread.
https://forum.xda-developers.com/showpost.php?p=76980632&postcount=25580
all is well.. thanks very for the help. and I installed the Xposed module that works with TextAid and MM.
also your link won't doesn't seem to work. I've found that a I've had to use shortened links of late or they don't fire on XDA.
Guys I can't run Magisk on my LG G4 H815 with Nougat v29a. After removing Supersu and flashing magisk 17.1 with twrp, the phone doesn't boot normally. It reboots recovery when I click reboot system. It always reboot recovery. I don't know why.
Do you have any Idea?
software status modified i wand to use linieageos with gapps and recovery TWRP somone to help me stap by step and save my life!!!!
love you all
You need to download the latest twrp for the Z2F/Nash from the TWRP site. One of the files is the twrp installer, which should be moved to your z2's sdcard. The img file stays on a PC.
Before you do anything, the Android platform tools should be present. Or you can instead install minimal adb/fastboot from XDA. Once you boot twrp you have to format data and type yes, so the rom and other files should be on an SD card. Alternatively, one may opt for adb sideload.
1.Flash LOS. Without rebooting, flash the twrp installer otherwise it won't stick.
2.Reboot recovery and flash gapps, then reboot recovery again
3. Reboot system