Root Onda Obook 10 Se V5 : Remix OS 2.0 - Supported Devices

Rooting voids your warranty and the process may brick your tablet. Common sense dictates that rooting will also kick you out of OEM updates. I take no responsibility. Problem is when it comes to gadgets/ android I am neither common nor sensible and I follow grand benefits. Please continue at your own risk!
…
Couple of months ago I bought this tablet to take advantage of the amazing “Remix OS” only to realize just like the normal android I needed to root to get the juicy benefits of the rom. In any case the gadget comes with loads of Chinese stuff which I don’t follow.
I couldn’t get anything regarding rooting the Remix on Obook 10 SE and unfortunately TWRP method which seems to work with majority of Onda tablets doesn’t click with this one. Here is my method:
Requirements:
1. PC with Intel drivers installed
2. Onda Obook 10 SE V1 stock android boot.img (facilitates the rooting). download
3. Onda Obook 10 SE V5 Remix OS rooted boot.img. download
4. Root-tablette-chinoise tool. download
5. Debugging on the tablet is enabled
6. Human brain, cats patience
(I take no credit in any of the tools used here. Follow the specific links to thank the respective developers. The v3boot.img mod thanks goes to @digital0 here. If however you want to get into the crazy bit where I rooted the Obook 10 SE V5 Remix boot.img be my guest at the bottom of this thread. It might be helpful if the attached doesn’t work with your tablet)
STEP 0: Back up your data including apps and anything else important to you in the internal memory. YOU WILL LOSE IT IF YOU DON’T!
STEP 1:
i. Download all the attached tool, boot images and extract the “ Root-tablette-chinoise.net ”. copy the boot images in the root directory of the extracted folder
ii. Open the command prompt from inside the extracted folder and connect the tablet.
iii. Type ‘
Code:
adb reboot bootloader
‘ without quotes and hit Enter. The tablet will reboot to bootloader screen. If the DEVICE STATE is locked / verified hit next step (iv) else if it is unlocked skip (iv)
STEP 2: Type
iv.
Code:
fastboot oem unlock
v.
Code:
fastboot flash boot v1boot.img
vi.
Code:
fastboot reboot
NB:
If prompted during reboot hit the “Volume up” to continue
STEP 3:
vii. Once the tablet boots up, head over to settings and enable USB Debugging
viii. Double click on “3 Root-tablette-chinoise.net.bat” file and follow the screen prompts. If all went well once the tablet reboots, you will have “SUPERSU” installed. Just cancel the Binary update prompt!
ix. Once again from the command prompt reboot the tablet into bootloader ‘adb reboot bootloader’
x. Flash the rooted Obook V5 remix boot image. Type without quotes ‘fastboot flash boot v5remixboot.img’
xi. Reboot the tablet and you are good to go. With ROOT !
ROOTING Onda Obook 10 SE Remix OS boot.img
Like you have noticed, the stock android V3boot.img seems a good fit for the V5 remix OS. It facilitates the rooting, boots up … EXCEPT… WIFI, BLUETOOTH, ROTATION & SOUND don’t work. Courtesy of @... and “RKwinTools_v133” (Search the web and thank the creator) I was able to tear open the stock android v3boot.img, change a few lines to get the WIFI, BLUETOOTH up and working again but ROTATION & SOUND proved tough.
When you flash the stock v5 remix OS boot.img even after editing with RKwinTools to add root you boot up only to realize the root you got with v1boot.img is lost. As such you only have root as long as the V1boot.img is inside the tablet.
This got me thinking: If I could flash the stock V5 Remix OS boot.img in another tablet/Phone with a custom recovery, then flash SuperSU in the recovery, then extract the rooted boot.img in the recovery using CMD prompts, won’t that give me an easily rooted boot.img? It worked for me. And that’s the attached V5Remixboot.img!
STEPS:
1. Connect a phone/tablet with a custom recovery to the PC and reboot into bootloader (Make sure you have a full back up). In my case I used a Doogee X5 Max phone
2. Flash the Remix OS boot.img into the gadget using fastboot
3. Reboot the gadget and long press the volume up key to boot into recovery
4. Flash the latest SuperSu.zip
5. Extract the boot.img by using the dd command to dump the system partition containing the boot image. More details here

Hello, my PC is not reading my ONDA Obook10 SE when I connect it via USB. So I can't do the steps here. Any help? I already enabled USB Debugging mode but still doesn't appear on my PC.

Hi,
Confirm the intel drivers for the obook are well installed from the Device manager and that the usb cable is in good working condition. You can also reinstall the drivers and boot the pc. You can boot into fastboot by shutting down the tablet and pressing down the VOLUME DOWN button and POWER button at the same time

Related

[RECOVERIES & ROOT] Yureka custom recoveries & Root without Changing Stock Recovery

[RECOVERIES & ROOT] Yureka custom recoveries & Root without Changing Stock Recovery
Note : This tutorial is for YU Yureka based on CM11 (KK 4.4.4) 32bit architecture
and
do it on your own risk, I will not be responsible if you brick your phone
Here is the detailed guide and collection of stock and all custom recoveries for YU Yureka and detailed guide to Root YU Yureka without changing Stock Recovery
Requirements
1. YU Yureka (obviously) with USB Data cable
2. PC / Laptop (Having Windows installed at least Windows 7 or above)
3. Drivers (Windows Automatically detect and install the required drivers)
4. ADB & Fastboot binary package that can be downloaded from XDA 15 seconds ADB Installer v1.4.2']http://forum.xda-developers.com/showthread.php?t=2588979
5. Custom Recovery (Anyone in which you are interested CWM, PhiZ, TWRP)
6. Latest SuperSU.zip file to root your phone
Warning: This process may delete all data stored in internal storage so better backup all the files stored in internal storage.
Step One
Enable USB Debugging on your device you can just follow these steps:
Go to Settings> About phone and keep taping on build number at least 7 times or till it appears "You are a developer now",
Now again go to settings>developer option (only after the previous step it will be enabled)> check/select USB debugging.
Step Two
Unlock your bootloader to flash custom recovery and root.
Here is the process
1. Download the adb & fastboot binary package and install it.
2. Put your phone into FASTBOOT mode by following anyone from below methods :
Method 1 (easiest)
-------------------
a. Power down phone
b. Plug USB cable to your PC
c. Press and hold Vol Up button and plug other end of USB to your device, soon you will see the fastboot screen.
(or without plugging USB Cable, Press and Hold Power and Vol Up buttons simultaneously, until you see the screen
"FASTBOOT MODE"
Method 2
---------
a. While your phone is Power On, plug USB Data Cable with PC and Phone (USB Debuging must be Enable)
b. Open Command Prompt on your PC (with Administartor rights) and type the following command
adb -s 0x1ebf devices
You will get results something like that :
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
3a289c2 device
*Note : If you get "authorization message" then look on your mobile screen and authorize your PC and run the command again.
c. Now note down the device no. (for e.g. in above "3a289c2") and type the following command
adb -s 3a289c2 reboot bootloader
[*Note replace the device id with your id (here 3a289c2), that you got in last command]
Now your phone must be booted into fastboot mode. A screen with "Fastboot Mode" should be appear on your phone.
3. Device drivers will get installed by windows (please wait for the driver installation to complete)
4. After driver installation is done go to the folder where you have extracted the package
5. Now open elevated DOS command prompt (terminal) on your PC and go into the same folder where you saved the recovery file
(*Note : to start command prompt directly from desired folder, while holding the Shift Key Right Click on folder and select start "open command window here")
6. Type the following command to check if the device was detected in fastboot mode
fastboot -i 0x1ebf devices
you should get output like : 2a25d00 fastboot
if you don't get similar output it means that the drivers weren't correctly installed or the device wasn't connected properly
7. If the output is similar to above then run the following command:
fastboot -i 0x1ebf oem unlock
you should get output something like :
.....
OKAY [ 0.003s]
finished. total time: 0.004s
8. Now your bootloader is now unlocked.
*Note : if you want to re-lock your bootloader again (for warranty on any other reason), again boot into fastboot mode and this time type the following command and enter
fastboot -i 0x1ebf oem lock
Step Three
Boot your phone into recovery (temporarily or permanently) and root your phone
1. Download SuperSU.zip and put it on root of your internal or external SD card
2. To load custom recovery (CWM / TWRP / PhiZ) temporarily, now type this command in terminal :
fastboot -i 0x1ebf boot CWM_6.0.5.1_recovery-yu.img
*Note 1 : if you want to flash the custom recovery permanently then us the following command
fastboot -i 0x1ebf flash CWM_6.0.5.1_recovery-yu.img
*Note 2 : if your download custom recovery is named differently (here CWM_6.0.5.1_recovery-yu.img) then while writing the above commands you need to put the name of the recovery same as as your saved file name (anyone CWM / Phiz / TWRP)
3. Done ! You loaded custom recovery temporarily, if command used with "boot" hence to root your phone, proceed to next section (step 5).
or
If you flashed recovery permanently, using command with "flash" then boot your phone into recovery. To do so, you have Two options
i) type the following command and press enter : adb -s 3a289c2 reboot recovery
or
ii) power off your phone, after then press and hold "Vol up+ Vol down + Power" buttons simultaneously to boot into custom recovery.
Now to root your phone proceed with next section (step 5).
Root your phone
5. To gain root access, flash SuperSu.zip that is stored on your internal or external SD card (in step 1)
6. Choose reboot phone and enjoy rooted phone with stock or custom recovery !
Special Note 1
I didn't tested, but came to know that root doesn't effect OTA update on Yureka.
You can get OTA updates with root but after the OTA update is flashed you will loose root access. To keep it or to avoid this please go to System Settings -> Developer Options -> UNTICK -"Update CM Recovery" (update recovery while installing system updates)
Even though if someone want to go back to Stock recovery, then download the official stock recovery (link no. 6 above) and flash it using command in fastboot mode (second command in step 2 under head "STEP THREE")
Downloads
1. 15 seconds ADB Installer v1.4.2 http://forum.xda-developers.com/showthread.php?t=2588979
2. Super SU latest v2.46 http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
3. CWM 6.0.5.1 https://s.basketbuild.com/devs/vishal_android_freak/yu/yureka
OR http://d-h.st/ElAe
4. PhilZTouch 6.59 based on CWM v6.0.5.1 http://www.androiddevs.net/downloads/
OR http://d-h.st/UqWK
5. TWRP 2.8.5.0 http://techerrata.com/browse/twrp2/tomato
OR https://www.androidfilehost.com/?fid=95916177934528156
OR http://d-h.st/5wDD
6. YU Yureka Official Stock Recovery http://d-h.st/tQ1k
Special Note 2
Without the vendor id, phone will not get detected in fastboot mode.
Like if you want to check fastboot type this :
fastboot -i 0x1ebf devices
therefore, always add "i -0x1ebf" after fastboot and then write your command
aabidhashmi said:
Here is is collection of all custom recoveries for YU Yureka and detailed guide to Root YU Yureka without changing Stock Recovery
Requirements
1. YU Yureka (obviously) with USB Data cable
2. PC / Laptop (Having Windows installed at least Windows 7 or above)
3. Drivers (Windows Automatically detect and install the required drivers)
4. ADB & Fastboot binary package that can be downloaded from XDA 15 seconds ADB Installer v1.4.2']http://forum.xda-developers.com/showthread.php?t=2588979
5. Custom Recovery (Anyone in which you are interested CWM, PhiZ, TWRP)
6. Latest SuperSU.zip file to root your phone
Warning: This process may delete all data stored in internal storage so better backup all the files stored in internal storage.
Step One
Enable USB Debugging on your device you can just follow these steps:
Go to Settings> About phone and keep taping on build number at least 7 times or till it appears "You are a developer now",
Now again go to settings>developer option (only after the previous step it will be enabled)> check/select USB debugging.
Step Two
Unlock your bootloader to flash custom recovery and root.
Here is the process
1. Download the adb & fastboot binary package and install it.
2. Power down phone
3. Plug USB cable to your PC
4. Press and hold Vol Up button and plug other end of USB to your device, soon you will see the fastboot screen.
(or without plugging USB Cable, Press and Hold Power and Vol Up buttons simultaneously, until you see the screen
"FASTBOOT MODE"
5. Device drivers will get installed by windows (please wait for the driver installation to complete)
6. After driver installation is done go to the folder where you have extracted the package
7. Now open elevated DOS command prompt (terminal) on your PC and go into the same folder where you saved the recovery file
* to start command prompt directly from desired folder, while holding the Shift Key Right Click on folder and select start "open command window here"
8. Type the following command to check if the device was detected in fastboot mode
fastboot -i 0x1ebf devices
you should get output like : 2a25d00 fastboot
if you don't get similar output it means that the drivers weren't correctly installed or the device wasn't connected properly
9. If the output is similar to above then run the following command:
fastboot -i 0x1ebf oem unlock
you should get output something like :
.....
OKAY [ 0.003s]
finished. total time: 0.004s
10. Now your bootloader is now unlocked.
Step Three
Root your phone without changing your stock recovery
1. Download SuperSU.zip and put it on root of your internal or external SD card
2. To load custom recovery (CWM / TWRP / PhiZ) temporarily, now type this command in terminal :
fastboot -i 0x1ebf boot recovery CWM_6.0.5.1_recovery-yu.img
*Note : if your download custom recovery is named differently (here CWM_6.0.5.1_recovery-yu.img) then while writing the above command you need to put the name of the recovery same as as your saved file name (anyone CWM / Phiz / TWRP)
Done ! You flashed custom recovery temporarily.
3. Now press and hold "Vol up+ Vol down + Power" buttons simultaneously to boot into custom recovery.
4. To gain root access flash SuperSu.zip that is stored on your internal or external SD card (in step 1)
5. Choose reboot phone and enjoy rooted phone without changing stock recovery !
Downloads
1. 15 seconds ADB Installer v1.4.2 http://forum.xda-developers.com/showthread.php?t=2588979
2. Super SU latest v2.46 http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
3. CWM 6.0.5.1 https://s.basketbuild.com/devs/vishal_android_freak/yu/yureka
OR http://d-h.st/ElAe
4. PhilZTouch 6.59 based on CWM v6.0.5.1 http://www.androiddevs.net/downloads/
OR http://d-h.st/UqWK
5. TWRP 2.8.5.0 http://techerrata.com/browse/twrp2/tomato
OR https://www.androidfilehost.com/?fid=95916177934528156
OR http://d-h.st/5wDD
Special Note
Without the vendor id, phone will not get detected in fastboot mode.
Like if you want to check fastboot type this :
fastboot -i 0x1ebf devices
therefore, always add "i -0x1ebf" after fastboot and then write your command
Click to expand...
Click to collapse
Few errors noted:
1. You can't say flashing recovery when you are booting it.
2. In step 3 point 3 is not valid because when your command is to boot it will automatically boot into recovery you need not use combination keys.
3. Last point vender id is wrong !!!
Few suggestions:
1. It feels like you have not tested this by yourself
2. There is already a guide for "rooting without flashing recovery". Search before posting.
Regards
aashking
aashking said:
Few errors noted:
1. You can't say flashing recovery when you are booting it.
2. In step 3 point 3 is not valid because when your command is to boot it will automatically boot into recovery you need not use combination keys.
3. Last point vender id is wrong !!!
Few suggestions:
1. It feels like you have not tested this by yourself
2. There is already a guide for "rooting without flashing recovery". Search before posting.
Regards
aashking
Click to expand...
Click to collapse
Dear aaskking
Thanks to inform. Here is the corrections
1 & 2 - Tutorial updated with "boot" and "flash" commands separately.
3 + Vendor ID is correct nothing wrong in it.
4 - I already tested all those procedures and commands. I never post anything without testing.
5 - Yes, I also seen that available guide, but that is not so much detailed and also required files links are not provided.
Anyway, thanks for your suggestions.
aabidhashmi said:
Dear aaskking
Thanks to inform. Here is the corrections
1 & 2 - Tutorial updated with "boot" and "flash" commands separately.
3 + Vendor ID is correct nothing wrong in it.
4 - I already tested all those procedures and commands. I never post anything without testing.
5 - Yes, I also seen that available guide, but that is not so much detailed and also required files links are not provided.
Anyway, thanks for your suggestions.
Click to expand...
Click to collapse
EDIT : You can get OTA updates with root..
After the update is flashed you will loose root access ..
To keep it or to avoid this please write the following step
STEP) In Developer Option UNTICK -"Update CM Recovery".
That's it.. Cheers mate wonderful thread.. @aabidhashmi @aashking
arjunsingh1000 said:
EDIT : You can get OTA updates with root..
After the update is flashed you will loose root access ..
To keep it or to avoid this please write the following step
STEP) In Developer Option UNTICK -"Update CM Recovery".
That's it.. Cheers mate wonderful thread.. @aabidhashmi @aashking
Click to expand...
Click to collapse
Thanks Arjun Singh @arjunsingh1000 for suggestion and appreciation
Post updated ...
aabidhashmi said:
Thanks Arjun Singh @arjunsingh1000 for suggestion and appreciation
Post updated ...
Click to expand...
Click to collapse
Great mate cheers just checked and tried that ota updates are available and work.. On stock recovery... Locked bootloader and with root..
Achieved this by downgrading to the very first cm11 firmware and got then rooted it and locked the bootloader then I just booted it and got the incremental update .. Downloaded and flashed .. Works perfectly.. Root not lost due to the untick in dev options..
Thanks again Arjun Singh, for confirming OTA updates are working.
I am already on Stock ROM & recovery {rooted} and tried the same procedure {locked the bootloader}, but no updates for me.
Is updates are really there, or something wrong with me ?
Sent from my AO5510 using Tapatalk
I am simply unable to get the device listed in command prompt after fastboot mode is enabled. my phone has option to boot into fastboot mode in power options. i tried that option, i tried using command to boot into fastboot. But somehow, when phone is in fastboot mode, it does not get detected by fastboot application (even though windows installs drivers successfully).
I have tried 3 different laptops. All had same problem. No idea how to solve this.
aabidhashmi said:
Thanks again Arjun Singh, for confirming OTA updates are working.
I am already on Stock ROM & recovery {rooted} and tried the same procedure {locked the bootloader}, but no updates for me.
Is updates are really there, or something wrong with me ?
Sent from my AO5510 using Tapatalk
Click to expand...
Click to collapse
Well I guess you are on the latest build XN0PHQ I guess? Another beta update was made but not rolled out it is um XNPH08P I know its a little late but just in case you don't know..
---------- Post added at 05:30 PM ---------- Previous post was at 05:28 PM ----------
jitendragarg said:
I am simply unable to get the device listed in command prompt after fastboot mode is enabled. my phone has option to boot into fastboot mode in power options. i tried that option, i tried using command to boot into fastboot. But somehow, when phone is in fastboot mode, it does not get detected by fastboot application (even though windows installs drivers successfully).
I have tried 3 different laptops. All had same problem. No idea how to solve this.
Click to expand...
Click to collapse
Ahahahaah... I know just the way... Do not reboot via adb ...
Switch off your phone remove your battery and put it back in do not turn it on.. But connect your USB cable and at the same time hold the power up or maybe down button .. Voila your in fastboot which will get detected .. Don't forget to use the vendor id.
arjunsingh1000 said:
Ahahahaah... I know just the way... Do not reboot via adb ...
Switch off your phone remove your battery and put it back in do not turn it on.. But connect your USB cable and at the same time hold the power up or maybe down button .. Voila your in fastboot which will get detected .. Don't forget to use the vendor id.
Click to expand...
Click to collapse
I tried this method but phone does not get detected in fastboot mode at all. I have drivers installed for all different modes I connect my phone as. No luck at all.
Also, weird thing is, I have an option to directly go to fastboot mode from the power menu.
Jitendra Garg
Your driver's are not installed
As there is no special drivers setup, so connect your PC with Internet then plug your phone and let Windows install drivers automatically.
Sent from my AO5510 using Tapatalk

Jade Remix OS ROM for NEXUS 10

Hi all,
i haven't a Nexus 10 but I want to let you know that Jade Remix OS ROM is now available for flashing on the Nexus 10:
Here is the link to download the ROM: https://drive.google.com/open?id=0B6QbFTXmsda3VDhCMUU3OVg1S2s
Here you'll find screenshots and videos: http://www.jide.com/en/remixos - https://www.youtube.com/channel/UC0U64-AHqJfeAnFJ5vQnM8w/feed
Here is the JIDE forum: https://forum.jide.com/index.php?p=/discussion/601/nexus-10-rom-available-here#Head
This is the greatest "fork" Android base ROM!!
P.S.: I don't want anything, just a Thank You
ROM Installation Instructions
Want to try to flash a Remix OS ROM to other android devices? Yes! We will soon put the Remix OS ROM on the Internet for users to download and flash onto their own device. To start, we will provide the guideline and support to flash the Remix OS ROM on Google Nexus 10.
Disclaimer
Flashing Remix OS ROM on Nexus 10 requires strong android knowledge. Flashing this ROM on Nexus 10 will be at your own risk. You will have to bear responsibility for all the resulting consequences. Jide will NOT be responsible for any damage caused.
Further Note:
Unfortunately, as a startup, we lack the resources to support installation Remix OS ROM on other android devices, thus, we will ONLY provide support for the Nexus 10 device. The Nexus 10 is a touchscreen tablet manufactured by Samsung with direct support from Google. It is the second Nexus tablet. Of course, we will look forward to the support of Remix fans to share with the world about their experience on flashing the ROM on other Android devices.
Installation Instructions
The followings are the steps to install Remix OS ROM: Unlocking the device & Installing image files using fastboot
Unlocking the device
1. Make sure your computer has working fastboot and adb.
2. Enable USB debugging on the device.
3. Connect the device to the computer through USB.
4. From a terminal on a computer, type the following to boot the device into fastboot mode:
- adb reboot bootloader
5. Once the device is in fastboot mode, verify your PC sees the device by typing
- fastboot devices
- If you don't see your device serial number, and instead see "", fastboot is not configured properly on your machine. See fastboot documentation for more info.
- If you see "no permissions fastboot", try running fastboot as root.
6. From the same terminal, type the following command to unlock the bootloader:
fastboot oem unlock
7. A disclaimer will display on the device that must be accepted. Use the volume keys to cycle through the options. Pressing the power button should confirm your selection.
8. If the device doesn't automatically reboot, reboot it from the menu. It should now be unlocked. You can confirm this is the case if you see an unlocked icon at the bottom of the Google boot screen during reboots.
9. Since the device resets completely, you will need to re-enable USB debugging on the device to continue.
Installing image files using fastboot
1. Make sure your computer has working fastboot and adb.
2. Download images
- you should have a download link from us in the email. The information of the image zip file:
- Images Zip File Name: images_Nexus_10-5.0.2-B2015070105-signed.zip
- md5: bdb08b6a0508dd1088f177a9e19c2875
- sha1: 9d6df824ef8c32af1a3a9d89e5f870133bcdebf6
3. Unzip the downloaded zip file ( images_Nexus_10-5.0.2-B2015070105-signed.zip ) and go to the folder
4. Connect the Nexus 10 to the computer via USB.
5. Make sure the fastboot binary is in your PATH or that you place the recovery image in the same directory as fastboot.
6. Open a terminal on your PC and reboot the device into fastboot mode by typing
adb reboot bootloader
or by using the hardware key combination for your device while it is powered off.
7. Once the device is in fastboot mode, verify your PC sees the device by typing
fastboot devices
- If you don't see your device serial number, and instead see "", fastboot is not configured properly on your machine. See fastboot documentation for more info.
- If you see "no permissions fastboot", make sure your UDEV rules are setup correctly.
8. Clean the existing data by entering the following command:
- fastboot -w
9. Flash images onto your device by entering the following three commands:
- fastboot flash system system.img
- fastboot flash recovery recovery.img
- fastboot flash boot boot.img
10. Once the flash completes successfully, run the following command to reboot the device into recovery to verify the installation.
- fastboot reboot
Some of the external link of this documents will link to CM website. The installation process is referenced by http://wiki.cyanogenmod.org/w/Install_CM_for_manta
You are the man!
Yea that didn't work for me, no recovery on boot to recovery just blank screen. Also stuck on remix boot logo.
Works for me. You have to fastboot -w to wipe your device, then flash at least the system and boot image through fastboot.
I didn't wipe my device ,didn't wanna lose the sdcard content. I simply did a factory reset from twrp. Question, can it be rooted with cfautoroot like normal android 5.0?
its totally a new dev rom! the best out there! Love this rom!
How to add other languages, for example, russian?
So far I'm loving this rom. The only thing is that I wish there was a way to add widgets.
For some reason i can't hear any media volume whether it be youtube videos, music, or netflix. Any ideas on what might be wrong?
For some odd reason Tapatalk doesn't work on this ROM for me.
How do we root? Anyone know?
I've found this YOUTUBE link, but didn't test yet
EddyTeddy01 said:
For some reason i can't hear any media volume whether it be youtube videos, music, or netflix. Any ideas on what might be wrong?
Click to expand...
Click to collapse
I'm having the same problem, did you ever figure this out?
Corvidd said:
I'm having the same problem, did you ever figure this out?
Click to expand...
Click to collapse
Why is this always a problem with N10 roms?
Sent from my Nexus 5 using Tapatalk
I'm trying to get this ROM off my nexus 10, but I don't have ADB connection for some reason. I don't have TWRP recovery anymore either. Anyone have any tips?
blkhrt13 said:
I'm trying to get this ROM off my nexus 10, but I don't have ADB connection for some reason. I don't have TWRP recovery anymore either. Anyone have any tips?
Click to expand...
Click to collapse
ADB - do you have USB debugging on? is Fastboot not working either? may need to re-install drivers on your PC
TWRP - are you saying it was installed, but you can't access it? unclear on your exact issue.
drewski_1 said:
ADB - do you have USB debugging on? is Fastboot not working either? may need to re-install drivers on your PC
TWRP - are you saying it was installed, but you can't access it? unclear on your exact issue.
Click to expand...
Click to collapse
Okay, I'll power off the tablet, then hold volume up AND down + power and that boots it into.... Recovery I think. When it boots to that, adb and fastboot are connected. I have a Nexus toolkit installed on my pc for flashing etc. Whenever I click flash recovery to reinstall twrp, it reboots the tablet into the OS and that's it. And when it's booted into the OS, there's no adb connection. And USB debugging is on. I finally just gave up.
blkhrt13 said:
Okay, I'll power off the tablet, then hold volume up AND down + power and that boots it into.... Recovery I think. When it boots to that, adb and fastboot are connected. I have a Nexus toolkit installed on my pc for flashing etc. Whenever I click flash recovery to reinstall twrp, it reboots the tablet into the OS and that's it. And when it's booted into the OS, there's no adb connection. And USB debugging is on. I finally just gave up.
Click to expand...
Click to collapse
Power + Vol Up/Down boots to bootloader.
If you have fastboot, then download the TWRP img file to your computer and issue the following command in the bootloader (forget the toolkit)
Code:
fastboot flash recovery <recovery img file name>
then you should be able to get into TWRP by using the Power Up/Down buttons until you see "Recovery" aligned with the Power Button.
press Power and you should be good to go.
blkhrt13 said:
I'm trying to get this ROM off my nexus 10, but I don't have ADB connection for some reason. I don't have TWRP recovery anymore either. Anyone have any tips?
Click to expand...
Click to collapse
I'm in the EXACT same situation. Fastboot and adb not working for this, but all my other android devices are working fine. Luckily I have twrp installed so I'll just flash something else then start over on a diff rom.
Edit: and of course, just like that, I restart one more time and it actually works. very temperamental i guess.
This is a great ROM with fast clean I interface. I used official manta 5.1 from Jide. Unfortunately google device manager now sees my N10 as a Linux device, and google play services will not load properly so I cannot play cloud connected games which is really sad, I will have to back to an android custom ROM..... If you don't need play services give jide a try.. Its a pretty cool concept.

[Guide] Unlock/Root/Update/Relock for BQ Aquaris X2 pro (zangyapro)

Introduction
I'm writing this thread to summarize useful information about the BQ Aquaris X2 pro such as:
preliminary actions (adb and fastboot configuration)
unlocking the bootloader
flash a factory image
root the device (currently without TWRP)
updating the device without losing root
relocking the bootloader
I own this phone since July 2018. I started writing my notes in August 2018 in the form of a Google document (link here). I shared this document with some telegram groups and some people I know.
Now I that I think it can be more useful to summarize all my notes here on XDA so that all interested people can access it.
DISCLAIMER:
By attempting any of the processes listed in this thread you accept full responsibility for your actions. I have no responsibility about your actions.​
1) Preliminary actions
1.1) Developer options, USB debugging and Unlock OEM
The first thing you need to do is to enable Developer options, USB debugging and Unlock OEM. Hence:
enable “Developer options” by hitting 7 times on the build number (Got to settings --> about phone)
enter the new menu “Developer options” and,
enable “USB debugging”
enable “Unlock OEM”
1.2) Download and configure abd and fastboot
All steps listed in this guide will require the use of Google Platform tools. I suggest the use of the one provided by Google here: https://developer.android.com/studio/releases/platform-tools.
Download the one for your operating system:
View attachment 4655394
Be sure that your terminal can access adb and fastboot from every position by configuring the PATH. I'm use to configure the PATH on the fly when I need it. As I said before, I work on Linux/macOS where you can set the PATH by:
opening a terminal and running:
Code:
export PATH=$PATH:path_to_platform_tools
2) Unlock the bootloader
Unlocking the booloader will wipe your phone. So backup your data first.
The good news here is that this phone can be handled like a Nexus/Pixel phone. Therefore, the procedure to unlock the bootloader is straightforward:
do all stuff at point 1.1 and 1.2
open a terminal
plug your phone to the PC
reboot into the bootloader
Code:
adb reboot bootloader
run the code:
Code:
fastboot flashing unlock
now you have to wait until your phone reboots. It takes a while, don't panic!!! When the phone is on the initial screen turn it off and reboot into the bottloader again by holing 'power + volume down'.
run the code:
Code:
fastboot flashing unlock_critical
it's done. Your bootloader is completely unlocked. Now, you only have to wait again for the reboot.
3) Flash a factory image
As you probably know, BQ releases a factory image at each update at this link factory images. Factory images are very useful to perform a very clean install. Are you experiencing some issues with your phone and none of the trick you tried solved it? If it is a software issue a clean flash with a factory image will likely remove the issue.
Keep in mind that by flashing a factory image you will wipe also the userdata partition. So backup your data first. Now let's see how to flash the factory image:
you need an unlocked bootloader (see previous sections)
download the factory image from this link
unzip the archive
open a terminal at this folder
be sure to have abd and fastboot properly configured (see previous sections)
run the script to flash all (*):
Code:
./sdm660_fastboot_all_images.sh
wait the end of the process. The phone will reboot.
(*) on Windows you have to deal with the file sdm660_fastboot_all_images.bat. I suppose it's similar but I've never done it on Windows.
4) Obtain ROOT privileges
Nowadays, the most common tool to obtain root privileges is Magisk. Many people here know very well what Magisk is and how to install it with TWRP. However, TWRP is not yet ready for BQ Aquaris X2 pro, hence, we must follow the procedure for installing it without the custom recovery.
When I wrote the document in August I find very informative this guide by @nathanchance. It's for the pixel 2XL but, as I told you before, it works perfectly also for the BQ Aquaris X2 pro (zangyapro). So here I summarize what @nathanchance already posted. All credits must go to him.
Here you have the steps:
Download the Magisk zip from the official thread and install the manager from the zip.
Grab a boot image to patch (either the one from the latest factory image or a custom kernel one) and push it to your device:
Code:
adb push <path_to_file> /sdcard/Download
Open Magisk Manager and click the Install button.
Click "Install" at the first prompt then choose "Patch Boot Image File". A file manager will pop up.
Select the boot image you want to patch and let Magisk Manager patch it.
Pull it off your device:
Code:
adb pull /sdcard/MagiskManager/patched_boot.img
Reboot into the bootloader:
Code:
adb reboot bootloader
Flash the boot image and reboot.
Code:
fastboot flash boot patched_boot.img
fastboot reboot
Open Magisk Manager and you should be rooted!
Please note that it exists also a specific thread where the author also provides the patched boot.img files for download. Hence, you can start from point 6 without patching the boot.img by yourself. Take care of selecting the right one. Here you have the thread link.
5) Update the ROM without loosing root
To the best of my knowledge, the only way to update keeping root is by using the factory images provided by BQ.
Download the factory image of the latest firmware (link)
Extract the file zip and upload the file boot.img on your phone
Code:
adb push <path_to_file> /sdcard/Download
Open Magisk Manager and click the Install button.
Click "Install" at the first prompt and then choose "Patch Boot Image File". A file manager will pop up.
Select the boot image you want to patch and let Magisk Manager patch it.
Pull it off your device:
Code:
adb pull /sdcard/MagiskManager/patched_boot.img
Place the file patched_boot.img in the folder of the BQ firmware unzipped at point 2
Make a copy of the file sdm660_fastboot_all_images (.sh in Mac/Liux and .bat on Windows).
Rename the file, I called it sdm660_fastboot_upgrade.sh
Change the following lines (this will preserve root privileges on your phone):
Code:
fastboot flash boot_a boot.img # <-- delete this line
fastboot flash boot_a patched_boot.img # <-- add this line
Delete the following line (this will prevent your data to be wiped):
Code:
fastboot flash userdata userdata.img # <-- delete this line
Run from your terminal
Code:
./sdm660_fastboot_upgrade.sh (or bat)
I think that one can also update using the OTA. This will make you lose the root privileges and therefore, you will have to repeat the procedure at section 4. I've never tested this so, if you decide to do it, you are on your own.
6) Relock the Bootloader
By relocking the bootloader you will lose all your data, hence, backup them first.
To relock the bootloader you only need the following commands:
Code:
fastboot flashing lock_critical
fastboot flashing lock
Each command will wipe your data and will reboot the phone. Be patient waiting for the reboot and do not panic.
Reserved.
(work in progress)
First: Thanks for this really nice and comprehensive thread!
I have an important addition to point:
3. Open Magisk Manager and click the Install button.
Click to expand...
Click to collapse
Install Button will only appear if the phone has internet connection (Wifi or Mobile Data)
with this I can patch the boot image successfully
But unfortunately I can not run the "sdm660_fastboot_upgrade.sh.bat" it does not recognize my device.
When checking the commands in the batch I found that my device is acting really strange, sometimes giving different errors for the same command like:
Code:
C:\Android\X2proRoot\1.7.1_WithRoot>fastboot set_active _a
error: Device does not support slots.
C:\Android\X2proRoot\1.7.1_WithRoot>fastboot set_active _a
Setting current slot to 'a'...
FAILED (remote: Invalid Slot)
finished. total time: 0.004s
C:\Android\X2proRoot\1.7.1_WithRoot>fastboot set_active _a
error: Device does not support slots.
also strange:
Code:
C:\Android\X2proRoot\1.7.1_WithRoot>fastboot flash boot patched_boot.img
target didn't report max-download-size
sending 'boot' (50749 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.004s
Probably some windows crap not working or an incompatibility of the installed platform tools / drivers and the ones from BQ...
raudidroid said:
First: Thanks for this really nice and comprehensive thread!
I have an important addition to point:
Install Button will only appear if the phone has internet connection (Wifi or Mobile Data)
Click to expand...
Click to collapse
Thanks. I was not aware of this. And now I can't check this on my device because I started using GPay and I prefer to stay with no root and locked bootloader.
Maybe I will play again with the bootloader when TWRP for this device will be released. If it will
got it running!
raudidroid said:
Probably some windows crap not working or an incompatibility of the installed platform tools / drivers and the ones from BQ...
Click to expand...
Click to collapse
Probably it was just that. I Installed Ubuntu 16.04 LTS in a Vmware machine and followed the tutorial (important note here: do everything in a Terminal running under root).
Short moments of panic due to boot-loop included (I flashed a defective boot image [vmware drag and drop files obviously did not copy the whole file] )
for everybody who ends in a bootloop: just keep calm, switch off phone (>10s press power button) an very quickly when it is of press power and volume down to get into flashmode again (I had to try several times)
Hey @raudidroid, when I answered to you the first time I did not read all the message or you edited it later. Only now I'm reading the issues you faced.
On Windows, what shell did you use? PowerShell?
I'm not sure about this because I banned Windows from my personal and working life several years ago, however, recently I read some posts of people having issues with PowerShell. If this is also your case next time try to use classic cmd.
Probably it was just that. I Installed Ubuntu 16.04 LTS in a Vmware machine and followed the tutorial (important note here: do everything in a Terminal running under root).
Click to expand...
Click to collapse
Regarding this the above quote, I'm quite sure that you do not need to be super user to apply any of the procedure listed in the guide.
for everybody who ends in a bootloop: just keep calm, switch off phone (>10s press power button) an very quickly when it is of press power and volume down to get into flashmode again (I had to try several times)
Click to expand...
Click to collapse
Since your are suggesting "... very quickly when it is of press power and volume down ... " I can imagine that you did this procedure while your phone was connected to the laptop/PC with the USB cable. In this condition, when you force the shutdown by pressing power for 10s, the phone reboots automatically. So my suggestion is to unplug it first, in this way the phone turn off without rebooting and you can comfortably enter in the bootloader with no hurry.
luk.giak said:
On Windows, what shell did you use? PowerShell?
I'm not sure about this because I banned Windows from my personal and working life several years ago, however, recently I read some posts of people having issues with PowerShell. If this is also your case next time try to use classic cmd.
Click to expand...
Click to collapse
I was using CMD / Command Prompt on win10, but maybe I have to many ADBs/Drivers/... installed. got a really weird behavior...
Regarding this the above quote, I'm quite sure that you do not need to be super user to apply any of the procedure listed in the guide.
Click to expand...
Click to collapse
without root it wouldn't work, i got "no permissions (user in plugdev group; are your udev rules wrong?)"
with root everything ran smoothly
Since your are suggesting "... very quickly when it is of press power and volume down ... " I can imagine that you did this procedure while your phone was connected to the laptop/PC with the USB cable. In this condition, when you force the shutdown by pressing power for 10s, the phone reboots automatically. So my suggestion is to unplug it first, in this way the phone turn off without rebooting and you can comfortably enter in the bootloader with no hurry.
Click to expand...
Click to collapse
Oh! Yep, that sounds like it would have been the better way to do it
Thanks for your post and your answers.
BTW: half-OT do you know any way to get netflix running after the rooting?
For your information.
I follow part 5 and updated my firmware to version 1.7.3 successfully. Thanks for this guide.
AndroidenKalle said:
For your information.
I follow part 5 and updated my firmware to version 1.7.3 successfully. Thanks for this guide.
Click to expand...
Click to collapse
Your welcome!
For your information.
I follow part 5 and updated my firmware to version 2.0.0 (Android Pie 9) successfully.
AndroidenKalle said:
For your information.
I follow part 5 and updated my firmware to version 2.0.0 (Android Pie 9) successfully.
Click to expand...
Click to collapse
Thanks for sharing.
I'm on PIE as well. Today I flashed the factory image to make a clean install.
Hello, maybe someone can be of help to my situation.
I had my phone rooted in the last firmware version (1.7.3), and I was getting notifications to update to Android 9 pie for some time, however I was waiting to have some time to spare and first backup my files and do a factory update to pie and then root.
However, last nigh without warning my phone just rebooted and updated to pie, (firmware ver 2.0.2) and I lost root obviously. However, all my files, apps, etc were intact.
So today I decided to root my phone again. I download the firmware zip from BQ's site and then used Magisk (ver. 19.2) to patch the boot.img.
I rebooted to fastboot and did "sudo fastboot flash magisk_patched.img", and rebooted but the phone got stuck in the logo screen.
Then I used method 5 of this tutorial and ran ./sdm660_fastboot_upgrade.sh (with the mentioned modifications), however it bootlooped again. Then I flashed the original boot img and my phone booted just fine again, I tried to patch the img again, did again step 4 and it bootlooped again.
Any clues on how to successfully root ? Never had any problems updating and rooting from firmware 1.4.0 to 1.7.3.
Thank you for your time

Simple LG K8 x240dsf Rooting guide

Preface​
We're following this guide https://topjohnwu.github.io/Magisk/install.html, specifically the Boot Image Patching section.
This guide is different because i'm not using berkantkz recovery, there are uses for it i know but i just needed root real quick, not ****ing around with the recovery partition.
Process works for EVERY phone out there but this guide is made for the one i'm using, here you can jump over a few steps as i'm giving you the patched boot image for the K8 x240dsf variant.
I'm giving instructions even if i shouldn't, mostly for me in case i forget but also for you so you can speed up the rooting process. That being said i know jack **** don't ask me stuff, also i'll get a stroke if you write like a robot that barfed random words into google translate.
Instructions:​Preparations:
1) PC: install LG drivers
2) PC: Install universal ADB (Thank you Clockworkmod team!)(https://adb.clockworkmod.com/)
3) download Magisk Manager (Thank you Magisk team!) https://github.com/topjohnwu/Magisk/releases
4) download Lg k8 x240dsf patched boot.img for magisk i made for you (Thank you...you!)
First stage:
1) Backup your ****
2) enable OEM unlock
3) enable USB debugging
4) plug the little ****er in your PC
5) pull up a console
6)
Code:
adb devices
HOLY F*CK WE'RE HACKING (no we f*cking aren't)
7) check your phone, authorize that sh*t
8)
Code:
adb reboot bootloader
Second stage:
1)
Code:
fastboot oem unlock
2) Mash that Volume UP key, motherf*cker (YOU WILL LOSE YOUR STUFF)
3) After it's done take the battery out and restart
4) Install Magisk Manager
5) enable USB debugging
6)
Code:
adb reboot bootloader
Unpack the zip file you just downloaded and flash it like your life depends on it
7)
Code:
fastboot flash boot /path/to/magisk_patched.img
Restart and you're done.

How to root a OnePlus 7T Pro with Magisk, For Noobs!

In this guide, ill be showing you how to root your device using Magisk. This is done at your own risk, i am not responsible for corrupted images, bricked devices etc.
*NOTE: This guide is for the OnePlus 7T Pro only*
What you will need:
A windows PC - idk buy one lol?
Platform tools SDK - https://developer.android.com/studio/releases/platform-tools
USB cable that came with the phone
Magisk Manager APK - https://magiskapp.com/apk/
Your phones current software boot.img! You can either get this from the vendors website, or if you are running a custom OS, you should already have the file.
*Ill be assuming you are familiar with cmd, fastboot commands, and that your bootloader is already unlocked, and you are running a custom recovery! For a guide on how to do the last two things, part of my last guide can help you - https://forum.xda-developers.com/t/how-to-install-android-12-derpfest-for-noobs.4385171/ *
Step 1: Download the magisk apk from the website and install it to your device. After this, copy over the boot.img file that is from your current rom into the downloads folder of your phone! Now, open up magisk manager, and press install beside the 'Magisk' Section on the home screen. Then press 'Select and Patch a FIle'. Now you can select the boot.img file and let Magisk do its thing.
Step 2: Once that process has been completed, you should have a file beginning with 'magisk_patched....img' in your downloads folder. Copy that file over to the platform tools folder in your computer. Now boot your phone into fastboot mode and connect it to your computer. Then on your computer, go to where you placed the magisk_patched file and in the search bar in file explorer type cmd. This should open a cmd window. Then type 'fastboot reboot fastboot' in order to enter your phone into fastbootd mode.
Step 3: Type 'fastboot flash boot 'PATH TO MAGISK_PATCHED FILE'
Let this run and once its done, reboot your phone.
Go to Magisk and Voila you should be rooted!
If you have any questions please dont hesitate to ask!
If i have made any mistakes in this guide, or you guys think i should make any changes, let me know, im new to this!
Thnx for the post , and confirming that this worked perfectly with OP7T PRO Android 11 official ROM
Do I assume correctly that I would wipe everything?
astroarchcraft said:
In this guide, ill be showing you how to root your device using Magisk. This is done at your own risk, i am not responsible for corrupted images, bricked devices etc.
*NOTE: This guide is for the OnePlus 7T Pro only*
What you will need:
A windows PC - idk buy one lol?
Platform tools SDK - https://developer.android.com/studio/releases/platform-tools
USB cable that came with the phone
Magisk Manager APK - https://magiskapp.com/apk/
Your phones current software boot.img! You can either get this from the vendors website, or if you are running a custom OS, you should already have the file.
*Ill be assuming you are familiar with cmd, fastboot commands, and that your bootloader is already unlocked, and you are running a custom recovery! For a guide on how to do the last two things, part of my last guide can help you - https://forum.xda-developers.com/t/how-to-install-android-12-derpfest-for-noobs.4385171/ *
Step 1: Download the magisk apk from the website and install it to your device. After this, copy over the boot.img file that is from your current rom into the downloads folder of your phone! Now, open up magisk manager, and press install beside the 'Magisk' Section on the home screen. Then press 'Select and Patch a FIle'. Now you can select the boot.img file and let Magisk do its thing.
Step 2: Once that process has been completed, you should have a file beginning with 'magisk_patched....img' in your downloads folder. Copy that file over to the platform tools folder in your computer. Now boot your phone into fastboot mode and connect it to your computer. Then on your computer, go to where you placed the magisk_patched file and in the search bar in file explorer type cmd. This should open a cmd window. Then type 'fastboot reboot fastboot' in order to enter your phone into fastbootd mode.
Step 3: Type 'fastboot flash boot 'PATH TO MAGISK_PATCHED FILE'
Let this run and once its done, reboot your phone.
Go to Magisk and Voila you should be rooted!
If you have any questions please dont hesitate to ask!
If i have made any mistakes in this guide, or you guys think i should make any changes, let me know, im new to this!
Click to expand...
Click to collapse
Hello, up to step 3 everything was fine. I let it run its thing, and reboot, BUT it became stuck in fastboot, forever. What can I do? I tried to wipe data and everything, but it's still stuck. Is there anything I can do?
Okay, so I manage to get my phone unbricked and is now running TWRP, which it was not before doing this. Am I correct to assume that doing all this without TWRP breaks the phone?
powerfulnacho said:
roidHello, up to step 3 everything was fine. I let it run its thing, and reboot, BUT it became stuck in fastboot, forever. What can I do? I tried to wipe data and everything, but it's still stuck. Is there anything I can do?
Okay, so I manage to get my phone unbricked and is now running TWRP, which it was not before doing this. Am I correct to assume that doing all this without TWRP breaks the phone?
Click to expand...
Click to collapse
Same here, not work too.
For OxygenOS latest, in Android 12.
--- EDIT ---
Personally I install TWRP to do mostly backups, if needed.
But you have to use this twrp for Android 12 :
OnePlus 7T Android 12 TWRP?
Hello! I'm very new to building custom recoveries, and haven't even completed a successful build yet. I have a OnePlus 7T model HD1905 (aka North American model/Global) running OOS 12. I've tried to find guides on how to make a TWRP recovery, but...
forum.xda-developers.com
For the moment, after flash boot.img builded by Magisk is not work. But i dont try with this twrp. I dont now if this have a link...

Categories

Resources