Related
My goal: Root my old skyrocket so that I can run apps from Google Play that require root. I do not want to flash a custom ROM.
These are the instructions I am following, I am currently trying to figure out step 5:
1. Start ODIN
2. Put phone into download mode
3. Download(USE FIREFOX!) CWM 5.5.0.4 OR TWRP 2.2.2.0 TAR FILE "recovery.tar.md5" , do not change the filename, and select it in PDA section of ODIN
4. Hit the START button in odin, wait until it finishes.
5. Udate CWM from HERE or TWRP from HERE or with the TWRP 2.4.1.0 Flashable Zip
6. You're done.
Click to expand...
Click to collapse
Since I have CWM installed, I clicked the 'HERE' link on step 5, which sends me here http://forum.xda-developers.com/showthread.php?t=1777970
This is what that link tells me to do:
- Download this file ----> updater.sh (updated to fix typo)
- Put it on your sdcard
- open adb and type:
Code:
su
sh /mnt/sdcard/updater.sh skyrocket
- it will reboot you into recovery
- starting in v14.2.1 it will automatically start installing and reboot when its done
Note: If your sdcard is not mounted on /mnt/sdcard then open the script and change the line that says path=/mnt/sdcard/sk8sUpdater to match your mount point. i.e. ICS users may have to change it to say path=/mnt/emmc/sk8sUpdater
Click to expand...
Click to collapse
-I have no ****ing clue what this is telling me to do.
-I have put updater.sh on my sdcard
-What the **** is adb. I don't even know if that's a phone or PC application, or some file manager, or what.
-What does completing step 5 accomplish? Will this have rooted me pursuant to my goal at the top of this post? I have literally no clue what these insturctions are trying to do nor when they have given me what I want.
Thanks.
Leave. Skyrocket is i727. Also don't cuss. People are more likely to help someone who doesn't seem *****y. And Google searches would have helped you. Adb. Is that hard to put in Google?
Sent from my GS4 running CM11 Kandy Kane
Moved to SkyRocket Q&A section
Make sure your phone is a i727 skyrocket
Download
http://d-h.st/KMT
And flash in recovery. This will update your recovery.
Reboot your phone
Download this http://d-h.st/fOD
Go back to recovery and flash the file you just downloaded. If it fails flash again.
Reboot your phone
Open the SuperSU app that will now be in your app drawer and update the binary when it prompts.
You are rooted.
You do not need to update your recovery but I highly recommend it
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
---------- Post added at 01:05 PM ---------- Previous post was at 12:57 PM ----------
Oh yeah and thank vincom
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Hi Hi.. friends.. its been 5 months since Coolpad Dazen 1 (8297L-I00) was launched in India and yet the stock rom for this phone is not available on net. Even at Coolpad's official service support site where firmware for all of their models are available, our beloved Dazen 1 seems to be an orphan.
There is no cwm available for our device either.
But if you are rooted and were searching for cwm and probably got one (wrong one which is for coolpad f1 plus) following some misguiding articles. and if you try to flash it to your phone, you will get stuck in bootloader mode. But don't worry it can be fixed easily..
NOTE: YOU WILL BE RESPONSIBLE FOR ANY TYPE OF DAMAGE THAT CAN HAPPEN TO YOUR PHONE. I HAVE TESTED THIS METHOD AND IT WORKED PERFECTLY FINE FOR ME. IT WILL WORK FOR YOU AS WELL IF YOU FOLLOW THE STEPS CAREFULLY.
Steps.
#1. Download the recovery.zip below, extract the files.
#2. Download and install the drivers if u haven't already.
#3. Power off your phone, connect it to pc, press and hold the Volume + and Power key for a few seconds to enter bootloader.
#4. Go to the folder where u extracted the files, Press Shift key then right click any where on the window and select open command window here.
#5. Press Volume+ key in phone.
#6. Type this command in command window.
Code:
fastboot devices
if your device is listed. then type
Code:
fastboot flash recovery recovery.img
If flash succeeds then you are done.
Code:
fastboot reboot
to reboot your device.
and if you don't see your device listed then make sure you have installed the drivers.
NOW.. if you mess up with your system u will brick your device OR try to apply OTA update on your rOOted phone, u will stuck on boot logo.
and these bricks will be pain in head to fix.. because there's no cwm backup or no stock rom.
but somehow @jaswant singh has managed to create fastboot flashable system.img which can restore our system but there are issues with it, wifi and bluetooth do not work after flashing.. but we hope that it will be fixed soon.
this is only way to fix this brick until stock rom becomes available.
oooooooohhhhhhhhhhh yeaaaah...........
Created my own system.img with help of @jaswant singh
and finally fixed my dazen 1 completely.. everything is working fine... wifi, bluetooth, sims are also working..
Fully functional Stock system.img is ready.
[Supports OTA Update]
Link below..
https://mega.nz/#!3gRkVLLB!MAUWgk_OjOCPrTI8qMeGfU30o8Ejq6NPw8T0qLglM8s
Flash system.img in fastboot.
#1. For windows.
copy system.img in your adb folder. put your phone in fastboot and give the command.
Code:
fastboot flash system system.img
it will take 2-3 minutes to complete. when its done, type
Code:
fastboot reboot
#2. For Ubuntu.
cd to the directory where you have put system.img. put your phone in fastboot and give the command.
Code:
fastboot flash system system.img -i 0x1ebf
when done.
Code:
fastboot reboot -i 0x1ebf
Voila.... :highfive::highfive:You just unbricked your coolpad dazen 1 and saved yourself some cash that you would have paid to service center.
So, Hit thanks button if I helped you.
OTA bricking the phone after root is really sad.. I don't think i will root my phone not until we find ways to counter this problem..
Anyways its good to finally see development work start on our Coolpad Dazen 1.. Better late than never..
This is the complete guide to unbrick coolpad dazen 1
---------- Post added at 07:28 AM ---------- Previous post was at 07:27 AM ----------
http://forum.xda-developers.com/showthread.php?p=63542971
---------- Post added at 07:31 AM ---------- Previous post was at 07:28 AM ----------
I need to upload all the stuff and will do it soon......
Not if any one have IMEI problem then please give the IMEI no I will solve it
Bugs are WiFi and Bluetooth not working
Will be fixed soon
Stock recovery and boot images link
https://www.dropbox.com/s/dfth7bs1601e7ni/boot and recovery.zip?dl=0
---------- Post added at 09:28 AM ---------- Previous post was at 09:13 AM ----------
System image link
Will recover the imei no also
https://www.dropbox.com/s/bay9cu8sbkn9oel/system.zip?dl=0
---------- Post added at 09:31 AM ---------- Previous post was at 09:28 AM ----------
Flash the files by fast boot
Commands
Fastboot flash boot boot.img
Fastboot flash recovery recovery.img
Fastboot flash system system.img
System image will take approx 10 minutes to flash
If any tell me will try to fix
@jaswant singh's guide
Requirements
1. Linux box or virtual machine
2. simg2img, make_ext4fs binaries which can be downloaded from here
web.djodjo.org/?a=download:an...inux:ext4tools
Procedure:
system stock files(u can get it by nandroid backup)
place you system files and the 2 binaries in one directory, and make sure the binaries have exec permission.
Code
mkdir sys
Place all the system stock files in sys folder
Part 2 - create a new flashable system image.
1. sudo ./make_ext4fs -s -l 2147483648 -a system system.img sys/
2. rm -fr sys
Now u I'll get system.img
Flash it by fastboot
fastboot flash system system.img
jaswant singh said:
Stock recovery and boot images link
https://www.dropbox.com/s/dfth7bs1601e7ni/boot and recovery.zip?dl=0
---------- Post added at 09:28 AM ---------- Previous post was at 09:13 AM ----------
System image link
Will recover the imei no also
https://www.dropbox.com/s/bay9cu8sbkn9oel/system.zip?dl=0
---------- Post added at 09:31 AM ---------- Previous post was at 09:28 AM ----------
Flash the files by fast boot
Commands
Fastboot flash boot boot.img
Fastboot flash recovery recovery.img
Fastboot flash system system.img
System image will take approx 10 minutes to flash
If any tell me will try to fix
Click to expand...
Click to collapse
@jaswant singh plz post md5 sum for system.zip so that we can check after download that the downloaded file is ok...
It's OK
jaswant singh said:
It's OK
Click to expand...
Click to collapse
have u checked your zip file after creating it?? i have downloaded it but its corrupted... don't know if got corrupted during download..
Yes it's okk
jaswant singh said:
Yes it's okk
Click to expand...
Click to collapse
well.. my data limit is exhausted.. can u give me nv file and where to put it?
OK I'm out of town will give you in night
jaswant singh said:
Yes it's okk
Click to expand...
Click to collapse
i think it wasn't uploaded successfully.. i have saved the file in google drive and google is unable to open the archive..
Alright I'll re-upload it
use 7zip
jaswant singh said:
Alright I'll re-upload it
Click to expand...
Click to collapse
use 7zip with ultra compression level and compression method: LZMA for best compression..
cm11 compressed 2.43 gb
http://forum.xda-developers.com/chef-central/android/aokp-aosp-cyanogenmod-miui-source-code-t2918515
for me also archive is showing corrupted. :crying: Still my phone is dead
Don't worry i will upload my system.img soon...
Sent from my Coolpad 8297L-I00 using XDA Free mobile app
How to root coolpad dazen 1
hey guys running lack of time will start work on dazen after 8/11/15 sorry guys just wait some more
........
sorry guys took along time
now I have a working link for system.img
after downloading hit thanks........
link:- https://mega.nz/#F!nJRyAT4R!kWFsSayc_WyLg128aASQaA
DISCLAIMER: I'm not responsible for anything that happens to your device. Use the steps below at your own risk . Be mindful of the facts unlocking bootloader voids your warranty and also hard resets your device - ALL YOUR DATA, SETTINGS, FILES AND APPS WILL BE DELETED. Rooting your device voids warranty as well. I own the Chinese SHT-AL09 8.4" LTE device and tested this root procedure ONLY WITH THIS MODEL. However, I believe there is a good chance the steps below will work for all other models of MediaPad M5, including WiFi only variants and 10" models. You MUST unlock your bootloader first. Do NOT use ramdisk image I provide in the steps below for any other model besides SHT-AL09 - doing so is guaranteed to render your device unusable. Ramdisk I provided is ONLY for SHT-AL09. You will need to extract your own ramdisk from stock firmware, specific to your device model
Credits:
@Wirmpolter - this root method largely based on his Magisk guide for Mate 9
@topjohnwu for creating the awesome Magisk Manager, which was used to patch ramdisk image with superuser binary
People, who created HuaweiUpdateExtractor
@magnumlove who pointed me in the right for developing root method in this post
This site, for hosting stock firmware for Huawei MediaPad M5
1. First, you will need to unlock the bootloader of your M5. Follow this guide
2. Transfer this patched ramdisk image to your device
Note for users with version of M5 other than SHT-AL09: Do NOT use the above ramdisk image. Download the full stock rom (update.zip) from the site I linked in the credits. Extract UPDATE.APP file from the zip. Then use HuaweiUpdateExtractor to extract ramdisk.img specific to your device. If you get errors in HuaweiUpdateExtractor - uncheck first 2 checkboxes for checksum verification on Settings tab and try again
3. Once bootloader is unlocked, install latest Magisk Manager from the official Magisk thread
4. Once Magisk Manager gives you a pop-up prompt to either download Magisk zip or patch the boot image file - chose to patch the boot image, but instead of boot.img select ramdisk.img from step 2. Magisk Manager should give you a message the image was successfully patched. It will be saved as patched_boot.img in MagiskManager folder on your sdcard. If it does not say success - do NOT proceed
5. Transfer the newly created patched_boot.img back to your PC
6. If you already have ADB and Fastboot tools installed on your PC you can just use what you've got. If not - get them from here
7. Connect your M5 to PC via USB cable
8. Run command prompt. If your ADB and Fastboot are installed as system app - you can do this from any path in CMD. If not - you need to switch in CMD to your ADB and Fastboot folder. Either way, the patched ramdisk patched_boot.img file must be in the same path, from which you will be running commands below in CMD window
9. Type "adb " in CMD window to start android debug bridge
10. Type "adb reboot-bootloader" and wait until your device restarts in Download mode
11. Once in Download mode, type "fastboot flash ramdisk patched_boot.img" - you should see some output from flash procedure, indicating successful flash
12. Once patched ramdisk is flashed, type "fastboot reboot"
That is it - you're done. Once your device reboots it will be rooted.
Note 1: Magisk Manager has it's own built-in superuser app and uses Systemless root, which works completely differently - you will not see external, standalone app like SuperSU or SU you might be familiar with in your App Drawer. The way to control the superuser app is from Magisk Manager itself: Settings->Superuser section
Note 2: I don't do tech support via PM, so don't PM me for help or with questions. Use the thread instead, and some other XDA members or myself will probably help you. Good luck!
Note 3: You may find some links to Huawei stock firmware in the 2nd post
UPDATE - August 6, 2018
Huawei officially approved 8.0.0.171 firmware with GPU Turbo for installation on SHT-AL09 devices. If you're doing first time root - just follow the original steps above. If you are already rooted and want to upgrade to 8.0.0.171 - follow the steps below:
1. Boot into download mode:
Code:
adb reboot-bootloader
from CMD window
2. Flash stock recovery from 8.0.0.171 to your device in fastboot:
Code:
fastboot flash recovery_ramdisk recovery_ramdis.img
3. Download and install the official OTA through Settings (full or just the update)
4. Boot into download mode again and flash patched ramdisk from 8.0.0.171
Code:
fastboot flash ramdisk patched_boot.img
5. OPTIONAL: If you were using TWRP or any custom recovery - you will need to reflash it back
Code:
fastboot flash recovery_ramdisk twrp.img
or whatever you named your custom recovery image
REMINDER: Do NOT use ramdisk image I provided for any other model besides SHT-AL09 - doing so is guaranteed to render your device unusable. This patched ramdisk is ONLY for SHT-AL09. You will need to extract your own ramdisk from stock firmware, specific to your device model
Needless to say, all the images you are going to flash must reside in the same directory, from which you are going to be running the CMD commands. If your ADB/Fastboot folder is not in your WIndows' PATH environmental variable - the images must be placed in the same folder where ADB/Fastboot binaries are, and CMD commands must be run from that folder.
C5Longhorn said:
Yes, they still work. I have the same model and build as you and I'm rooted.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
I'm considering buying an SHT-W09 with firmware version 8.0.0.200 (C567), but I'd like to know if I can root it first. I do not know if the bootloader has been unlocked. Since you have the same version, can you confirm that it's possible to unlock and root, and if so, sketch out how it's done? I'm confused about whether it's possible with this firmware.
samiller said:
I'm considering buying an SHT-W09 with firmware version 8.0.0.200 (C567), but I'd like to know if I can root it first. I do not know if the bootloader has been unlocked. Since you have the same version, can you confirm that it's possible to unlock and root, and if so, sketch out how it's done? I'm confused about whether it's possible with this firmware.
Click to expand...
Click to collapse
Unlocking is possible *only* if you've gotten already your unlock code. As this service was suspended about 2 years ago there is no easy way to get it unlocked.
Small request to developers, or people with access to reliable file hosting: I don't have a developer account, so all the files I linked or referenced in the OP are hosted on free hosting sites. That file hosting has expiration date and max downloads limit, so the files will become inaccessible sooner rather than later. Please upload these files to reliable hosting and create a post with the links. I will link your post in the OP as a mirror.
In the meantime, mirror for SHT-W09 firmware: https://mega.nz/#!asVjmZrR!bW2OmXgTjnyVN4pqb9fA7OzAJ4bzil7YZxNW14qoCmk
I can confirm that this works on the 10.8" wifi model using the devices relevant ramdisk.img.
Hello, can somebody test sixaxis controller tool with root and magisk? There is a Trial in Google Play Store, that is called sixaxis compatibility checker without purchise the App. Maybe i want to buy the Tablet, but only with Dualshock 4 Support...
Just a heads up, been following threads on this forum for flashing a GSI. Now that you guys can root, you can also make backups of your own stock system image if you can't find one from Firmware Finder. Then you can safely try flashing the GSI.
@MishaalRahman well it's bit like chicken egg dilemma. As we do not have a stock system image for e.g. SHT-W09 we cannot patch the ramdisk.img and so we cannot get the stock system image ...
Thanks Apo11on, great to have root so soon for the M5! Do you know if there's a way to get Xposed working? I tried the Xposed Framework SDK 26 from inside Magisk, but it put me in a boot loop.
Question is, for those of us with the Non Pro version, can this still be done.
@OHP Yes. The OP did it with the 8.4" version which has no pro option.
I'm looking to buy the Chinese 10" wifi version myself but need Google Play Store + Services on it which I'm guessing the Chinese version doesn't have. Is one of the firmwares at the website you link to a global version of the firmware that will work on this model?
OHP said:
Question is, for those of us with the Non Pro version, can this still be done.
Click to expand...
Click to collapse
Doesn't matter what version you have as long as you have access to your device firmware and the ramdisk.img. You really need to reread the guide.
magnumlove said:
Doesn't matter what version you have as long as you have access to your device firmware and the ramdisk.img. You really need to reread the guide.
Click to expand...
Click to collapse
Problem I have is :
CMR-W09C432B123 (8.0.0.123) from download headlines.
notice the Bold letter.
my Firmware on device:
CMR-W09C432123 (8.0.0.123)
obliviously it could be nothing but I wouldn't want to brick my tablet :fingers-crossed:
OHP said:
Problem I have is :
CMR-W09C432B123 (8.0.0.123) from download headlines.
notice the Bold letter.
my Firmware on device:
CMR-W09C432123 (8.0.0.123)
obliviously it could be nothing but I wouldn't want to brick my tablet :fingers-crossed:
Click to expand...
Click to collapse
I have exactly the same tablet/firmware as you and it was fine. The additional letter also threw me a little. But if you are unsure, download Huawei Firmware Finder from Google play and it will automatically detect your tablets firmware (which you can download if you wish).
magnumlove said:
I have exactly the same tablet/firmware as you and it was fine. The additional letter also threw me a little. But if you are unsure, download Huawei Firmware Finder from Google play and it will automatically detect your tablets firmware (which you can download if you wish).
Click to expand...
Click to collapse
I took the plunge, and I am sucessfully rooted now :silly:
struggling with this part
2. Transfer this patched ramdisk image to your device
Note for users with version of M5 other than SHT-AL09: Do NOT use the above ramdisk image. Download the full stock rom (update.zip) from the site I linked in the credits. Extract UPDATE.APP file from the zip. Then use HuaweiUpdateExtractor to extract ramdisk.img specific to your device. If you get errors in HuaweiUpdateExtractor - uncheck first 2 checkboxes for checksum verification on Settings tab and try again
I have a CMR-W09 :s i can got the files downloaded and the huwai software not sure how i make a img
The good news is I followed these instructions yesterday and they worked perfectly (SHT-AL09).
The bad news is, I seem to have lost root overnight.
---------- Post added at 06:41 AM ---------- Previous post was at 06:22 AM ----------
And I figured out why I lost root; I was playing around with Developer options and switched the default GPU renderer from 'default' to 'Skia.' Apparently, this disables root access until you switch back. I regained root access on a reboot, lost it again after switching back to Skia, and then regained it after switching back to default.
I got the right image file from the site and huwai extract. I have googled how to use this app but what files do I extract as there appears to be. Alot ? I extracted all of them ? I don't have a ramdisk.img
Also thanks for writting this up. Without it I would be lost
Thanks for the efforts making this thread. Unfortunately my device is SHT-W09 and I'm still waiting for the right firmware. Is there anything I can help, considering I have the device?
@dkk6 I am in the same boat as you. Unfortunately I installed the update to 8.0.0 123 without having the Firmware Finder installed on the device. Do you have installed already the update to 8.0.0 123?
If not, you could install Firmware Finder and provide us with the ota url ...
This works perfectly no issues. i had some how maanged to download the wrong rom first. AND thankfully it did not have a ramdisk in. it is important that your firmware matches the firmware present on the site as explained. This was easy guide to follow now to flash it with somthing other then andriod
AndDiSa said:
@dkk6 I am in the same boat as you. Unfortunately I installed the update to 8.0.0 123 without having the Firmware Finder installed on the device. Do you have installed already the update to 8.0.0 123?
If not, you could install Firmware Finder and provide us with the ota url ...
Click to expand...
Click to collapse
I'm on 8.0.0.101
Please someone should help me with custom recovery for Gionee A1 Plus, I can provide the stock recovery.. Or if anyone can provide general Stock with Root Access so I can flash my phone with it.. I just need help.. My Airtime keeps depleting for no reason..
https://forum.xda-developers.com/showthread.php?t=1943625
Please just help me out
Thanks but can you help me.. reading through this can cause headache.. I am not trying to be lazy, just too complicated. thank you
DSA said:
https://forum.xda-developers.com/showthread.php?t=1943625
Click to expand...
Click to collapse
First of all there is no stable custom recovery for this phone (due to its less popularity) so don't expect a support.
Secondly don't try to code it on your own because it's bit complicated and chances to make a suitable recovery are low.
Now I have a solution for you and it's not that complicated, it will provide root and a (partially working CWM recovery)
1st step : On your computer extract "BOOT.IMG" and scatter files from your rom (if you don't have so go download the same rom you're using and extract the specific file mentioned) and copy paste it in your phone directory. Then download & install Magisk manager on your phone.
2nd step : Open Magisk app, download patch [I believe its root files] or something like that then apply it on the "BOOT.IMG" file that you just transferred it on your phone [must remember the file directory you selected].
3rd step : go back to your computer and retrieve the patched or modded "BOOT.IMG" file, it must be in "Phone directory\Magisk" folder [it may not be the one you transferred earlier], now turn your phone off, flash your phones' "Boot partition" with the this patched file using SP FLASHTOOL and original scatter file so you can get the #ROOT privileges after you turn on your phone.
(Remember to leave other partitions unchecked Before start flashing).
And finally, on your phone download & install Flashify app and give it SU permission from Magisk and select The the custom recovery IMG file, the one which will provided in end of article, then of course flash it and reboot your phone.
~ This Philz CWM custom recovery is partially working or in other words it still on alpha stage.
Link : https://mega.nz/#!wSJ1nRbI!gWJ0wSi_AmxBx9Cj_Oa7XCsTR0hl3xJWAgDf5SyUYT8
Sent from my Condor M1 Plus using Tapatalk
Thanks! I am trying to check it out
Thanks bro, I will write you back soon, let me quickly get to work on this, hopefully, it will work.
The Mega link you sent, is it a custom recovery I could try out as well without going through the magicdsk steps?
Please advise
sonicswink said:
First of all there is no stable custom recovery for this phone (due to its less popularity) so don't expect a support.
Secondly don't try to code it on your own because it's bit complicated and chances to make a suitable recovery are low.
Now I have a solution for you and it's not that complicated, it will provide root and a (partially working CWM recovery)
1st step : On your computer extract "BOOT.IMG" and scatter files from your rom (if you don't have so go download the same rom you're using and extract the specific file mentioned) and copy paste it in your phone directory. Then download & install Magisk manager on your phone.
2nd step : Open Magisk app, download patch [I believe its root files] or something like that then apply it on the "BOOT.IMG" file that you just transferred it on your phone [must remember the file directory you selected].
3rd step : go back to your computer and retrieve the patched or modded "BOOT.IMG" file, it must be in "Phone directory\Magisk" folder [it may not be the one you transferred earlier], now turn your phone off, flash your phones' "Boot partition" with the this patched file using SP FLASHTOOL and original scatter file so you can get the #ROOT privileges after you turn on your phone.
(Remember to leave other partitions unchecked Before start flashing).
And finally, on your phone download & install Flashify app and give it SU permission from Magisk and select The the custom recovery IMG file, the one which will provided in end of article, then of course flash it and reboot your phone.
~ This Philz CWM custom recovery is partially working or in other words it still on alpha stage.
Link : https://mega.nz/#!wSJ1nRbI!gWJ0wSi_AmxBx9Cj_Oa7XCsTR0hl3xJWAgDf5SyUYT8
Sent from my Condor M1 Plus using Tapatalk
Click to expand...
Click to collapse
After installing Philz recovery, it keeps entering recovery.. Help!
I tried this link Link : https://mega.nz/#!wSJ1nRbI!gWJ0wSi_A...xJWAgDf5SyUYT8, it made my phone restart at the logo stage. I guess the custom recovery is not compatible. I have now done fresh installing of my rom twice now.
Meanwhile, I followed a download on how to create my Philz custom recovery, it installed but after installing supersu.zip, it keep loading to recovery without entering phone. Please help!
sonicswink said:
First of all there is no stable custom recovery for this phone (due to its less popularity) so don't expect a support.
Secondly don't try to code it on your own because it's bit complicated and chances to make a suitable recovery are low.
Now I have a solution for you and it's not that complicated, it will provide root and a (partially working CWM recovery)
1st step : On your computer extract "BOOT.IMG" and scatter files from your rom (if you don't have so go download the same rom you're using and extract the specific file mentioned) and copy paste it in your phone directory. Then download & install Magisk manager on your phone.
2nd step : Open Magisk app, download patch [I believe its root files] or something like that then apply it on the "BOOT.IMG" file that you just transferred it on your phone [must remember the file directory you selected].
3rd step : go back to your computer and retrieve the patched or modded "BOOT.IMG" file, it must be in "Phone directory\Magisk" folder [it may not be the one you transferred earlier], now turn your phone off, flash your phones' "Boot partition" with the this patched file using SP FLASHTOOL and original scatter file so you can get the #ROOT privileges after you turn on your phone.
(Remember to leave other partitions unchecked Before start flashing).
And finally, on your phone download & install Flashify app and give it SU permission from Magisk and select The the custom recovery IMG file, the one which will provided in end of article, then of course flash it and reboot your phone.
~ This Philz CWM custom recovery is partially working or in other words it still on alpha stage.
Link : https://mega.nz/#!wSJ1nRbI!gWJ0wSi_AmxBx9Cj_Oa7XCsTR0hl3xJWAgDf5SyUYT8
Sent from my Condor M1 Plus using Tapatalk
Click to expand...
Click to collapse
Yes me too I experienced bootloop but it's alright, sometimes it keep rebooting for 5 ~ 10 mins before initializing system.
And SuperSU never worked for me, I guess it's Android 7.0 Nougat Magisk should more compatible.
Sent from my Allure M1 Plus using Tapatalk
---------- Post added at 05:03 PM ---------- Previous post was at 04:59 PM ----------
Magisk steps are for patching BOOT.IMG to gain root, unlike The custom recovery has philz cwm recovery.img you should try flashing it as is.
Sent from my Allure M1 Plus using Tapatalk
Help
Wow! you mean I should allow it boot for close to 30 minutes? and what will happen after that is done? please let me know... I have decided not to root anymore as I am very tired already.
The option you gave for me to root using magisk through boot.img did not work.. I tried installing many times but nothing shows up neither did I see any patch as well..
Please let me know if I need to let it reboot for 10 minutes or more if thats the solution then I will wait..
sonicswink said:
Yes me too I experienced bootloop but it's alright, sometimes it keep rebooting for 5 ~ 10 mins before initializing system.
And SuperSU never worked for me, I guess it's Android 7.0 Nougat Magisk should more compatible.
Sent from my Allure M1 Plus using Tapatalk
---------- Post added at 05:03 PM ---------- Previous post was at 04:59 PM ----------
Magisk steps are for patching BOOT.IMG to gain root, unlike The custom recovery has philz cwm recovery.img you should try flashing it as is.
Sent from my Allure M1 Plus using Tapatalk
Click to expand...
Click to collapse
It's a bit challenging task huh ?
Okay did you extracted the file BOOT.IMG from your Rom and patched it in Magisk as I said ?
Because that's the most important step.
samosward said:
Wow! you mean I should allow it boot for close to 30 minutes? and what will happen after that is done? please let me know... I have decided not to root anymore as I am very tired already.
The option you gave for me to root using magisk through boot.img did not work.. I tried installing many times but nothing shows up neither did I see any patch as well..
Please let me know if I need to let it reboot for 10 minutes or more if thats the solution then I will wait..
Click to expand...
Click to collapse
Sent from my Allure M1 Plus using Tapatalk
---------- Post added at 06:37 PM ---------- Previous post was at 06:27 PM ----------
After that you should see the patched file on output folder. This file flash it using sp flashtool and once the flash finishes launch Magisk app and you will see the ROOT access enabled.
It's a piece of cake boy.
Sent from my Allure M1 Plus using Tapatalk
Please disregard in earlier message, I have finally done the boot patching with magisk. I tried flashing just the patch_boot.img which I renamed to boot.img but it shows error message C0030004 on SPtools.. Do you recommend I flash the whole phone while I used the new boot.img instead of the stock boot.img? If you can write me soon I will appreciate it.
sonicswink said:
It's a bit challenging task huh ?
Okay did you extracted the file BOOT.IMG from your Rom and patched it in Magisk as I said ?
Because that's the most important step.
Sent from my Allure M1 Plus using Tapatalk
---------- Post added at 06:37 PM ---------- Previous post was at 06:27 PM ----------
After that you should see the patched file on output folder. This file flash it using sp flashtool and once the flash finishes launch Magisk app and you will see the ROOT access enabled.
It's a piece of cake boy.
Sent from my Allure M1 Plus using Tapatalk
Click to expand...
Click to collapse
It's done!
I have rooted my phone! I truly can't say how I did it but I think your advise helped me out by using Magisk Boot patch... wow! I am the most happiest at this time.. Thanks for your support, I appreciate!
samosward said:
Please disregard in earlier message, I have finally done the boot patching with magisk. I tried flashing just the patch_boot.img which I renamed to boot.img but it shows error message C0030004 on SPtools.. Do you recommend I flash the whole phone while I used the new boot.img instead of the stock boot.img? If you can write me soon I will appreciate it.
Click to expand...
Click to collapse
Glad you did it.
I recommend you to make a backup If you're inexperienced with Root risks management.
Sent from my Allure M1 Plus using Tapatalk
Yeah, I have my firmware backup, if anything goes wrong, I would reflash my phone but for now, I would keep using it like this. Although, Fingerprint is presently not working.. I guess it hs something to do with magisk...
sonicswink said:
Glad you did it.
I recommend you to make a backup If you're inexperienced with Root risks management.
Sent from my Allure M1 Plus using Tapatalk
Click to expand...
Click to collapse
Honestly I don't advice you to depend on a firmware backup in case of loss of system or software disfonctionnement.
If you are an advanced or experienced user, go ahead, if not then read this immediately :
Your phone has not Snapdragon chip, your phone is powered by Mediatek chipset.
You don't want to end up using your phone as 6 inches mp4 player or WiFi tablet after flashing.
Every MediaTek phone has a unique data in a partition called "NVRAM" "MODEM" or "BASEBAND" name differs for every brand. If you my friend will perform a flash from a downloaded firmware backup, this flash is going format or erase system (the partition you want to flash) plus all other partitions that hold the unique data files, so you'll definitely lose your phone's IMEI, WiFi MAC address, Bluetooth address, and all radio drivers.
Consider this a friendly advice that saves you a 200$ phone.
Sent from my Allure M1 Plus using Tapatalk
sonicswink said:
Honestly I don't advice you to depend on a firmware backup in case of loss of system or software disfonctionnement.
If you are an advanced or experienced user, go ahead, if not then read this immediately :
Your phone has not Snapdragon chip, your phone is powered by Mediatek chipset.
You don't want to end up using your phone as 6 inches mp4 player or WiFi tablet after flashing.
Every MediaTek phone has a unique data in a partition called "NVRAM" "MODEM" or "BASEBAND" name differs for every brand. If you my friend will perform a flash from a downloaded firmware backup, this flash is going format or erase system (the partition you want to flash) plus all other partitions that hold the unique data files, so you'll definitely lose your phone's IMEI, WiFi MAC address, Bluetooth address, and all radio drivers.
Consider this a friendly advice that saves you a 200$ phone.
Click to expand...
Click to collapse
So how can one avoid that on an mtk device? I have had that happen to me before. All the other can be sorted but i failed to resolve meid to the way it was.
Thanks for the advise bro but I am not an outright novice, even if anything goes wrong,
I can always flash imei, mac or Bluetooth ID to the phone anytime.
Just my fingerprint that isn't working is my issue presently, secondly, how can I get or update my firmware to the latest update for Android 7.0, this particular one seems to load/open almost everything slowly compared to the stock firmware that came with it.
sonicswink said:
Honestly I don't advice you to depend on a firmware backup in case of loss of system or software disfonctionnement.
If you are an advanced or experienced user, go ahead, if not then read this immediately :
Your phone has not Snapdragon chip, your phone is powered by Mediatek chipset.
You don't want to end up using your phone as 6 inches mp4 player or WiFi tablet after flashing.
Every MediaTek phone has a unique data in a partition called "NVRAM" "MODEM" or "BASEBAND" name differs for every brand. If you my friend will perform a flash from a downloaded firmware backup, this flash is going format or erase system (the partition you want to flash) plus all other partitions that hold the unique data files, so you'll definitely lose your phone's IMEI, WiFi MAC address, Bluetooth address, and all radio drivers.
Consider this a friendly advice that saves you a 200$ phone.
Sent from my Allure M1 Plus using Tapatalk
Click to expand...
Click to collapse
tonde4jc said:
So how can one avoid that on an mtk device? I have had that happen to me before. All the other can be sorted but i failed to resolve meid to the way it was.
Click to expand...
Click to collapse
Just perform a Nandroid backup of indicated partitions and partitions you want yo keep, then restore Nand backup after flash, or if you're not in position to make a backup, simply restore your phone with flashing selected system and storage partitions and avoid (uncheck) indicated partitions.
Sent from my Allure M1 Plus using Tapatalk
---------- Post added at 05:09 PM ---------- Previous post was at 04:31 PM ----------
samosward said:
Thanks for the advise bro but I am not an outright novice, even if anything goes wrong,
I can always flash imei, mac or Bluetooth ID to the phone anytime.
Just my fingerprint that isn't working is my issue presently, secondly, how can I get or update my firmware to the latest update for Android 7.0, this particular one seems to load/open almost everything slowly compared to the stock firmware that came with it.
Click to expand...
Click to collapse
I didn't say you're novice, but you are writing like one bro.
First after Root installation process is finished, you can forget about updates for two reasons :
1- Updates kills Root and any system mods.
~After update process don't expect to find any Root.
2- updates makes Root installation harder by fixing system bugs and updates Android security patch.
~After updates expect a harder root setup process and less convenient Root usage, lags and bugs in your device usage because of security conflicts. Because some of Root apps are considered as threat or hostile by Google.
One of the bugs or conflicts are the fingerprint disfonctionnement, and I've done some researches so I found the easiest and only way to safely use root without any security conflicts is to downgrade the initial Nougat 7.0 update of your phone, I believe there are other methods to fix this issue without downgrading but they are not a permanent solutions.
My phone is rooted and works well in this version.
Sent from my Allure M1 Plus using Tapatalk
The version I use.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Allure M1 Plus using Tapatalk
Android Security patch level
April 5, 2017
Same Kernel 4.4.15
but my build is just too old
(SW Version)
A1 Plus_0301_V5242
(HW Version)
A1 Plus_Mainboard_P3
(hardware Vesion)
P3
My SW Version is just too old why my phone is moving too sluggishly, I am so so sure of that.
sonicswink said:
The version I use.View attachment 4589105
Sent from my Allure M1 Plus using Tapatalk
Click to expand...
Click to collapse
samosward said:
Android Security patch level
April 5, 2017
Same Kernel 4.4.15
but my build is just too old
(SW Version)
A1 Plus_0301_V5242
(HW Version)
A1 Plus_Mainboard_P3
(hardware Vesion)
P3
My SW Version is just too old why my phone is moving too sluggishly, I am so so sure of that.
Click to expand...
Click to collapse
Yes judging your device by the version infos you provided, it's very outdated, outdated Amigo UI firmwares are laggy and slow in response regardless to the hardware capacity.
Sent from my Allure M1 Plus using Tapatalk
This is a great rugged phone, perfect for the outdoors (I'm a keen mountaineer). I couldn't see a thread so I thought I would start one! A couple of posts re. rooting to follow....
Hey @dwastell, I know this thread is a couple months old, so I wanted to see if you have any root instructions?
Do you think the process for rooting the OUKITEL K13 here on the forum will work on the WP5?
Rooted!
Hi all,
I rooted my WP5. Sorry for not having time to write a full tutorial, only a concise story. Of course this is ONLY for experienced users...
My phone is 4GB version Android 10, build 10.0_V02_20200508.
1) download the firmware from oukitel website: https://oukitel.com/pages/download-center (1)
2) download and install SP Flash Tools https://spflashtool.com/download/
3) download and install Android Platform Tools https://developer.android.com/studio/releases/platform-tools
4) connect the phone to PC and verify that adb is working
5) WARNING: make a backup af your data!
6) unlock the bootloader:
- in Developer options enable the unlock
- adb reboot bootloader
- fastboot flashing unlock
- fastboot reboot
Now the phone restarts and is completely virgin!
7) shutdown the phone.
8) using SP Flash Tools readback the following partitions:
- boot
- recovery (2)
- vbmeta
9) download the attached patched_vbmeta.img
10) transfer the boot.img that you just readback to the phone download folder
11) install Magisk Manager (today 7.5.1)
12) Use Magisk Manager to patch the boot.img and copy back to PC
13) flash the images:
- fastboot flash --disable-verification vbmeta patched_vbmeta.img
- fastboot flash boot magisk_patched.img
- fastboot reboot
14) if the phone boots up run Magisk Manager to check if it's installed.
14b) if the phone goes in bootloop... flash back the original images you have read back (do not use the firmware you downloaded from Oukitel, it's necessary only to have the scatter file (the partition table).
Enjoy
Nicola
Notes:
(1) actually there are 2 firmware available and despite having different names are the same. This fw is Android 9.
(2) not used now but may be useful in the future
Rooting the WP5
totallybeachin said:
Hey @dwastell, I know this thread is a couple months old, so I wanted to see if you have any root instructions?
Do you think the process for rooting the OUKITEL K13 here on the forum will work on the WP5?
Click to expand...
Click to collapse
I eventually succeeded in rooting my WP5 with Magisk. For a while, the firmware was not available but once the official ROM was published, I managed to patch boot.img and install via fastboot. My phone is the 4 GB version -copies of the stock and patched boot image are available at: github.com/dwastell/Oukitel_WP5_magisk
I have experienced some complications as detailed in my next post...
Cheers, Dave
Rooting the WP5
Thanks for your post Nicola. You'll see that I did succeed in rooting my phone (Android 9) with Magisk, once I was able to get hold of the stock firmware. All is working though there are a couple of points worth noting.
The phones is SAR ("system-as-root") and the magisk instructions suggest that recovery.img is patched rather than boot.img. I proceeded by patching boot.img, as in your instructions, as this seemed a better solution - and it works fine.
One problem has occurred with updates. Magisk manager appears to assume that the recovery partition is the one that has been patched. When you do the direct install for the update, partition 2 is flashed (recovery) rather than partition 26 (boot). On rebooting the phone inevitably goes into boot loop.
To avoid this, I go for "select and patch a file" option, and then install again via fastboot as per the original installation. A bit of a hassle but better than the alternative!
Does this mean you were able to root the phone but revert to android 9? Both of you mention Android 9 in your posts.
vivekiny2k said:
Does this mean you were able to root the phone but revert to android 9? Both of you mention Android 9 in your posts.
Click to expand...
Click to collapse
No. No need to revert.
I rooted an Android 10. But cited the stock Android 9 only because the scatter file (ie. the partition table) is the same.
@dwastell rooted the Android 9.
Please read better my tutorial, if something is not clear... I'm here!
N
---------- Post added at 20:10 ---------- Previous post was at 19:59 ----------
dwastell said:
The phones is SAR ("system-as-root") and the magisk instructions suggest that recovery.img is patched rather than boot.img. I proceeded by patching boot.img, as in your instructions, as this seemed a better solution - and it works fine.
Click to expand...
Click to collapse
This phone is NOT a SAR. Neither Android 9 nor 10. The proof is that patching the boot.img worked!
One problem has occurred with updates.
Click to expand...
Click to collapse
Have you unrooted before applying the update?
Which kind of update? Not all are the same!
Android version
vivekiny2k said:
Does this mean you were able to root the phone but revert to android 9? Both of you mention Android 9 in your posts.
Click to expand...
Click to collapse
My phone was originally Android 9 so no reversion...
SAR
Both "Treble Check" and "Magisk Manager" confirm that the phone is SAR. I agree this is odd.... your thoughts?
The update I was referring to is the Magisk update, handled by Magisk Manager. Given that the phone is seen as SAR, it attempts to patch recovery.img, with an ensueing boot loop.
No, I don't unroot the phone
nicolap8 said:
No. No need to revert.
I rooted an Android 10. But cited the stock Android 9 only because the scatter file (ie. the partition table) is the same.
@dwastell rooted the Android 9.
Please read better my tutorial, if something is not clear... I'm here!
N
---------- Post added at 20:10 ---------- Previous post was at 19:59 ----------
This phone is NOT a SAR. Neither Android 9 nor 10. The proof is that patching the boot.img worked!
Have you unrooted before applying the update?
Which kind of update? Not all are the same!
Click to expand...
Click to collapse
Thanks Nicola for your tutorial. I'm eager to root my WP5 Pro with Magisk, but first I need a backup of boot vbmeta and recovery. I have made extensive use of SP Flash Tools but never to readback partitions so I'm having some problems here. Could you please detail your technique to extract such files? Thank you
Michele
Build number OUKITEL_WP5Pro_EEA_V01-20200624 CPU MT6762D, 8 cores,64 Gb ROM, 4 Gb RAM.
wallace108 said:
Thanks Nicola for your tutorial. I'm eager to root my WP5 Pro with Magisk, but first I need a backup of boot vbmeta and recovery. I have made extensive use of SP Flash Tools but never to readback partitions so I'm having some problems here. Could you please detail your technique to extract such files? Thank you
Michele
Build number OUKITEL_WP5Pro_EEA_V01-20200624 CPU MT6762D, 8 cores,64 Gb ROM, 4 Gb RAM.
Click to expand...
Click to collapse
Beware: your phone is different! So I don't know:
1) Android version.
2) which kind of booting are using, read here https://topjohnwu.github.io/Magisk/install.html#knowing-your-device
Before writing an image you MUST have a backup of it!
To read back a partition with SP Flash Tools you need to know the start address end the length of the partition. This information is available only (because your phone is not yet rooted) from the scatter file (from the SAME phone).
In the Readback page hit "Add" then input a name for the image file. Follows a new dialog "Readback block start address" where you have to write the values.
After this you can give the Read Back command. If it doesn't start shutdown the phone.
N
Thank you all for
the data to root! I just got a 4/32 android 10 version. Is there a custom recovery yet? Been a looooong time since I have dabbled but want to root it and customise. I have replaced most of google apps or disabled them already but want more room. I have never created a TWRP but have been reading about it and they already have many Oukitel versions, so should I wait? TIA
Thanks, it's clear.
I bought it for my son, don't have plans to root it yet. will probably wait till later.
nicolap8 said:
No. No need to revert.
I rooted an Android 10. But cited the stock Android 9 only because the scatter file (ie. the partition table) is the same.
@dwastell rooted the Android 9.
Please read better my tutorial, if something is not clear... I'm here!
Click to expand...
Click to collapse
No Joy with
Hardware : MT6761V/WE
Model : WP5
Build number : OUKITEL_WP5_NOEEA_V01_20200701
Build date UTC : 20200701-071441
Android v : 10
Baseband v: MOLY.LR12A.R3.MP.V114.9,MOLY.LR12A.R3.MP.V114.9
Kernel v : 4.9.190+ ([email protected]) (Android (5484270 based on r353983c) clang version 9.0.3 (based on LLVM 9.0.3svn)) #2 SMP Wed Jul 1 15:19:21 CST 2020
It seems locked down as I lose adb in fastboot and even patching the boot.img I create fails. MTKdroid tools can't create scatter.
vivekiny2k said:
I bought it for my son, don't have plans to root it yet. will probably wait till later.
Click to expand...
Click to collapse
Remember that you will lose ALL YOUR DATA! Usually it's better to root before start using the phone...
oncouch1 said:
No Joy with
Build number : OUKITEL_WP5_NOEEA_V01_20200701
It seems locked down as I lose adb in fastboot and even patching the boot.img I create fails. MTKdroid tools can't create scatter.
Click to expand...
Click to collapse
You have to describe well what you have done and error messages.
Note also that your firmware is never... maybe there is some difference.
N
As of today the firmware for the WP5 PRO has not been posted yet. I'll wait. Meanwhile I want to ask Nicolap8: what does the vbmeta file do? Why is it important to patch it. Isn't patching the boot enough? Thanks
TWRP for WP5 (Pie, 4GB)
If anyone wants to install TWRP, I've built and tested it for my WP5 (Android 9.0, 4GB). A copy of the image may be found in the MISC folder at: https://github.com/dwastell/TWRP_Oukitel_WP5
Note that the data partitiion is not accessible due to encryption (not a major limitation), and that the null version of vbmeta (thanks Nicola) does need to be flashed. Also, I have had problems flashing some versions of Magisk - please read the README.md.
nicolap8 said:
Remember that you will lose ALL YOUR DATA! Usually it's better to root before start using the phone...
You have to describe well what you have done and error messages.
Note also that your firmware is never... maybe there is some difference.
N
Click to expand...
Click to collapse
Sorry it has been a while I HAD WRONG USB DRIVERS! I got bootloader unlocked and will try again.
---------- Post added at 07:13 PM ---------- Previous post was at 07:09 PM ----------
A WP5 (android 10) .zip file is now on the site. It contains less files though?
For some reason the images taken in windows are corrupt. Magical fails to run on them. The one taken in llinux patches fine. One question though the original image is 32 meg the magical patches is only 10 meg is that correct? Also the vbmeta is 8 meg off the phone but the patches 256 k?
oncouch1 said:
For some reason the images taken in windows are corrupt. Magical fails to run on them. The one taken in llinux patches fine.
Click to expand...
Click to collapse
Strange but... with W all is possible!
One question though the original image is 32 meg the magical patches is only 10 meg is that correct? Also the vbmeta is 8 meg off the phone but the patches 256 k?
Click to expand...
Click to collapse
Both are correct.
The Magisk patched image is not "filled" to the partition size.
The vbmeta also is smaller because it's empty (is present only the "index").
N