Related
Hi everybody!
On our 4pda.ru forum we are struggling with this phone in two ways- rootin it and unlocking in order to update manually to 2.0 and even 2.2; and other way- working android (already have beta rom which is exact copy of rom from another alcatel 6014x which runs android and similar to our Fire E 6015x).
if there are any enthusiasts about android, i can translate the guide for you and share the needed files and programs. Almost everything works except sim-card(when there is no one- phone asks to insert it, when there is one- phone says its not registered) but we are working on it
i came over a https://www.soeren-hentzschel.at/mo...ch-verteilt-firefox-os-2-0-und-firefox-hello/ that states that in Germany some people already received 2.0 update on their Fire E. Here arises my question- are here people who own updated Fire E? I mean update to 2.0.
If there are ones, would you be so kind to make a copy of your rom for our little development? I can provide you with guides and software on how to do it.
I can post guides for making this an android phone.
Hi my dear russian brother - greetings from Germany.
I do have an updated 6015x device to FFOS2.0 and I could dump the rom for U. Just gimme links to the needed info. My russian is not one of my strength, but I think I can manage it - I'm a bulgarian after all.
hej, i also have a 6015X (fire e) with firefox os 2.0 running
tell me how to make a rom which i can send to you
root
After few months of waiting my phone get the forefoxos2.0 update
01008d yes it is fine but how to root it?
cybervitexud said:
After few months of waiting my phone get the forefoxos2.0 update
01008d yes it is fine but how to root it?
Click to expand...
Click to collapse
Look, please, do you have in System settings parameters of russian language on your FFOS 2.0.
HOWTO ROOT ALCATEL OT 6015X:
1. Download CWM recovery image made for 6014x.
https:// yadi.sk/d/BIdXndcbfR2Gm
2. Download Install-SuperSU.
download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
3. Turn your phone to bootloader mode anyway.
4. Run modrecovery:
Code:
fastboot boot my_recovery.img
5. In CWM menu follow "install zip" -> "install zip from sideload"
6. On pc:
Code:
adb sideload UPDATE-SuperSU-v2.46.zip
7. reboot phone
I am sure lowlevel utilities from android's SuperSU are working fine on any FFOS (because FFOS based on Android now).
WBR
Alcatel's stock ROM for the Fire E has been published at sourceforge.net in the Alcatel project.
dermartinac said:
Alcatel's stock ROM for the Fire E has been published at sourceforge.net in the Alcatel project.
Click to expand...
Click to collapse
I wonder how do you use it though, can you build it on its own? The B2G by Mozilla still hasn't got an option for this device.
Svinka said:
Look, please, do you have in System settings parameters of russian language on your FFOS 2.0.
HOWTO ROOT ALCATEL OT 6015X:
1. Download CWM recovery image made for 6014x.
https:// yadi.sk/d/BIdXndcbfR2Gm
2. Download Install-SuperSU.
download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
3. Turn your phone to bootloader mode anyway.
4. Run modrecovery:
Code:
fastboot boot my_recovery.img
5. In CWM menu follow "install zip" -> "install zip from sideload"
6. On pc:
Code:
adb sideload UPDATE-SuperSU-v2.46.zip
7. reboot phone
I am sure lowlevel utilities from android's SuperSU are working fine on any FFOS (because FFOS based on Android now).
WBR
Click to expand...
Click to collapse
I tried your recovery image but it doesn't seem to work. There is no error but after booting the image, the device isn't visible in fastboot or adb. For that reason, I'm unable to sideload the Su zip update.
sybiam said:
I tried your recovery image but it doesn't seem to work. There is no error but after booting the image, the device isn't visible in fastboot or adb. For that reason, I'm unable to sideload the Su zip update.
Click to expand...
Click to collapse
Flashing the recovery image works though, then sideloading the SU image works from clock work mode recovery.
Ok, here's some news. I built a boot image that enables adb as root. All you need is to flash it on the boot partition and reboot the phone. I made a few changes to the boot image.
default.prop
Code:
ro.secure = 0
ro.debuggable = 1
To flash:
Code:
fastboot flash boot boot3.img
and replaced /sbin/adbd by an adbd built with "ALLOW_ADBD_ROOT". (I used the sources fetched using b2g repo).
Cool thing..wish I am able
Sent from my SM-G7102 using XDA Free mobile app
Hi. Update firefox os 3.0?
lirondeespaña said:
Hi. Update firefox os 3.0?
Click to expand...
Click to collapse
As far as i know even Firefox OS 2.2 is not officially released yet.
There are only pre Versions.
Has anybody else troubles with FFOS 2.0 on the Alcatel Fire E?
The phone sometimes hangs completely while it was sleeping. (Can´t wake up or even call the phone)
Only if i press the start button for some seconds the phone starts again.
I hope someone builds a FFOS 2.2 Rom for the Fire E --> Copy and paste :good:
How can I switch this piece of **** called smartphone to bootloader mode?
Softbricked 6015x
Hey guys,
I got stuck with creating the boot.img and figured out that the backed up one doesn't work.
Does anybody have a working boot.img for the 6015x, NOT the 6014x?
I tried also getting the venezuelian one, but those TLDs are not reachable anymore - all gone.
The custom boot images from the russian 4pda forum are also not working.
I currently have only access to ADB, the TWRP recovery mod (temporarily) and fastboot, so I need a fastboot working image.
The Mobile Upgrade Q / TCL Updater / QDST distribution updater is Windows only - and crawling the binaries for URLs is a dead-end. The tool also requires
a fully booted OS, so it's pretty much the dumbest update tool out there and not practical to use. As I don't have Windows, the imgc files for the eMMC flashing tool are also a dead-end.
I really need only the boot.img file.
I really need only the boot.img file.
Click to expand...
Click to collapse
Did you try my boot img?
sybiam said:
Did you try my boot img?
Click to expand...
Click to collapse
Yes, my device constantly reboots and fails to initialize the display (seems like an Xorg alike error to me) when trying to figure out what logcat shows.
Due to the constant reboots I can't debug it using adb, because of constantly lost connections. That's why I'm asking for an OEM boot.img file.
I started to collect the working stuff over at github.com/martensms/alcatel-6015x (cant post links -_-)
cmartensms said:
Yes, my device constantly reboots and fails to initialize the display (seems like an Xorg alike error to me) when trying to figure out what logcat shows.
Due to the constant reboots I can't debug it using adb, because of constantly lost connections. That's why I'm asking for an OEM boot.img file.
I started to collect the working stuff over at github.com/martensms/alcatel-6015x (cant post links -_-)
Click to expand...
Click to collapse
Did you try to boot with fastboot or did you flash it to the boot partition. I had no success booting with fastboot but flashing works. That said, you have to install a custom recovery image.
Also, I'm working on building FFOS from sources but as won't be home for a month, it's kind of slow.
sybiam said:
Did you try to boot with fastboot or did you flash it to the boot partition. I had no success booting with fastboot but flashing works. That said, you have to install a custom recovery image.
Also, I'm working on building FFOS from sources but as won't be home for a month, it's kind of slow.
Click to expand...
Click to collapse
Both. Didn't work. As I said, I have no functioning boot image available. All boot images, from everywhere including your one, don't work.
I don't know what's so hard to understand. NO custom boot.img works. Seriously. None. Simple as that. I tried 9 different boot.img out, I even tried extracting the eMMC boot.img which obviously failed.
Again, third time, I just need an OEM boot.img in order to get further debugging my device because I can't debug my device in 3 second disconnect intervals from ADB.
edit: I unbricked my device now and made backup images of all OEM partitions - github.com/martensms/alcatel-6015x
cmartensms said:
Both. Didn't work. As I said, I have no functioning boot image available. All boot images, from everywhere including your one, don't work.
I don't know what's so hard to understand. NO custom boot.img works. Seriously. None. Simple as that. I tried 9 different boot.img out, I even tried extracting the eMMC boot.img which obviously failed.
Again, third time, I just need an OEM boot.img in order to get further debugging my device because I can't debug my device in 3 second disconnect intervals from ADB.
edit: I unbricked my device now and made backup images of all OEM partitions - github.com/martensms/alcatel-6015x
Click to expand...
Click to collapse
That's weird, my custom boot works on my own phone. 6015x, it's a russian phone. Firmware revision: 01005, hardware revision 01, platform version: 28. Firefox OS 1.3.0.0 .
I guess, if you had a newer version of Firefox, there could be something wrong with the boot image.
This thread applies to Huawei Mate 9 Pro only (model LON*, as M9Pro below). For Mate 9 (model MAH*) please go to the corresponding forum.
-----
Disclaimer:
I won't be responsible for bricked phone. Proceed with your own risk, make sure you know what you are doing.
This thread can be seen as a guide if your phone has exactly the same model and build version as mine. Otherwise please consider it as a description of my experiences for unlocking, flashing and rooting the phone.
SUPPORTED DEVICES:
LON-L29
LON-AL00
-----
As a start, this phone is great and I feel that it doesn’t need to be unlocked and rooted for a stable and long lasting daily use. However, unlock and root is almost a religion if you use Android phones
As a piece of info, big thanks to @raimondomartire, there is a thread for unlock, flash TWRP and root in the Mate 9 forum https://forum.xda-developers.com/mate-9/development/recovery-huawei-mate-9-pro-unofficial-t3546976, which is however according to my experience not totally applicable for the M9Pro anymore. There are also several other threads on the Mate 9 forum. Many things can be shared between both phones, but not always. Be careful about what you are doing!
-----
General info and attentions:
- My phone is M9Pro LON-AL00 (All net version from Chinese Mainland); LON-L29 (International version) should also work.
- This thread applies for build LON-AL00C00B213. Can be also applicable for similar builds, but I couldn’t test. Please report.
- None of the current builds of TWRP (up to 3.1.0) can decrypt data partition by default, which means you could only format the data partition in TWRP in order to access it in recovery (for backup to and install from internal storage etc.). But after formatting, you have to flash Huawei’s special stock data back to data partition (/data/hw_init), otherwise several functions of Huawei ROM won’t work. Refer to this (https://forum.xda-developers.com/showpost.php?p=71302827&postcount=627) or this (https://forum.xda-developers.com/showpost.php?p=72497328&postcount=204). Thanks to @gm007 and @ante0
- There are several root methods which handles encrypted or decrypted data partition. I didn’t format the data partition, i.e. data is still encrypted. If you want to format the data partition, please refer to this thread: https://forum.xda-developers.com/mate-9/how-to/guide-how-to-root-mate-9-decrypt-data-t3569986. Thanks to @eddmecha
- If you need stock ROM, refer to useful links below. Use Huawei Update Extractor to extract the individual partitions from the ROM: https://forum.xda-developers.com/showthread.php?t=2433454
-----
Unlock bootloader:
There is enough info in the internet about unlocking M9Pro’s bootloader. Just a few points to mention:
- Generally, you can follow the steps in @raimondomartire thread (https://forum.xda-developers.com/mate-9/development/recovery-huawei-mate-9-pro-unofficial-t3546976). But unlike he describes in his thread, there is no OEM Unlock options in the developer options anymore. Just use ADB to unlock.
- FRP unlock is not required!
- Huawei enables now a 14-day limitation, where you can officially get the bootloader unlock code 14 days after you first activate your Huawei ID on your phone and have logged in using your Huawei ID 14 CONSECUTIVE days.
- To go around this limitation, you can use dc-unlocker to get the bootloader code immediately. Google yourself
-----
Flash TWRP:
- Still, you can follow the steps in @raimondomartire thread (https://forum.xda-developers.com/mate-9/development/recovery-huawei-mate-9-pro-unofficial-t3546976).
- The image from this thread is 3.0.3, which has some bugs built in, especially when flashing SuperSU.
- You could use TWRP 3.1.0-1 from https://forum.xda-developers.com/mate-9/development/recovery-unofficial-twrp-huawei-mate-9-t3515617, but this one seems to have problem to be recognized as ADB device in recovery.
- There is a version 3.0.2 for Mate 9, which seems to have problem mounting USB-OTG.
- If your data partition is encrypted, you can only use ADB sideload or USB-OTG to install anything.
- If you want to do data wipe in TWRP, you have to flash Huawei’s special stock data back to data partition. See above general info and attentions.
-----
Root:
Firstly, thanks to @ante0 for explaining different flags in the root methods: https://forum.xda-developers.com/showpost.php?p=72504501&postcount=210. Some more discussions between us are also around this post.
I also tried several other root tools on the market (mobilego, vroot, YoRoot, OneClickRoot, iRoot etc.), NONE of them works.
As mentioned, there are different root methods around for unlocking M9Pro, depending on if you want to format your data partition. For me, I didn’t format, and SuperSU works for me. And the mate_9_pro_root.zip from @raimondomartire thread didn’t work for me.
I followed the steps below:
1. Get TWRP 3.1.0-1 (https://forum.xda-developers.com/mate-9/development/recovery-unofficial-twrp-huawei-mate-9-t3515617)
2. Disable fingerprint ID (I think it’s probably optional, but have read somewhere that fingerprint stops working after flashing root).
3. Flash stock boot image for B213D (in download section). I think it’s optional too, but if you have tried other methods before, you can do this step to make sure your boot is stock and clean
4. Flash TWRP 3.1.0-1
5. Flash SuperSU-v2.79-MATE9-init.d_support_no_decrypt-signed.zip (in download section) via USB-OTG (in TWRP the device is not recognized as an ADB device, hence no “ADB sideload”). Thanks to @ante0 for building this zip!
6. Reboot – phone will reboot itself twice and SuperSU.apk will be installed automatically
7. You could flash back to 3.0.3, if you want the ADB sideload function.
-----
Download:
- TWRP 3.0.3-1: https://forum.xda-developers.com/mate-9/development/recovery-huawei-mate-9-pro-unofficial-t3546976
- TWRP 3.1.0-1: https://forum.xda-developers.com/mate-9/development/recovery-unofficial-twrp-huawei-mate-9-t3515617
- SuperSU modified for M9Pro (thanks to @ante0): https://mega.nz/#!bR8D2Bab!bIgMLVmoll9R0GFqoFgkLxULrXlQ2710INt3TNbuI0c
- Boot image from B213D: https://mega.nz/#!LFlGTTZY!AaFq-_quM44YlK_Qdh9PgOjBE3Wtepmyz5OAuo_mabw
-----
Useful links:
- Stock firmware: http://hwmt.ru/oth/HWFF/info/view.php?find_model=lon
- Huawei Update (ROM) Extractor: https://forum.xda-developers.com/showthread.php?t=2433454
Enjoy your Mate!
Just some clarification: (eventhough you wrote it's for AL00C00B213, which I missed xD)
Flashing stock boot is only needed if you're already rooted.
Boot image B213D is only for AL00C00. If you have a different model/build, use the boot image for that specific build:
Download your stock firmware from hwmt.ru and Huawei Update Extractor. Extract update.app from your firmware zip.
Open update.app in Huawei Update Extractor. Rightclick on BOOT and click on Extract selected.
Flash the extracted boot.img using fastboot in download mode (fastboot flash boot boot.img).
OEM Unlocking is required to be enabled. It's just not there in the chinese version (AL00). So check if it's there first and enable if it is.
Hi guys. Not sure if this is the right place to ask but how do I get rid of that annoying "your device is unlocked and can't be trusted....etc " msg?
I have a mate 9 pro and I want to flash twrp and to root it. I did it for some one plus, xiaomi, samsung so I have some experience. reading xda posts about the case of M9pro I understood that is not a simple path and I dont want to hard brick the phone. what precautions should I take?
attached phone config
thank you in advance
ante0 said:
Just some clarification: (eventhough you wrote it's for AL00C00B213, which I missed xD)
Flashing stock boot is only needed if you're already rooted.
Boot image B213D is only for AL00C00. If you have a different model/build, use the boot image for that specific build:
Download your stock firmware from hwmt.ru and Huawei Update Extractor. Extract update.app from your firmware zip.
Open update.app in Huawei Update Extractor. Rightclick on BOOT and click on Extract selected.
Flash the extracted boot.img using fastboot in download mode (fastboot flash boot boot.img).
OEM Unlocking is required to be enabled. It's just not there in the chinese version (AL00). So check if it's there first and enable if it is.
Click to expand...
Click to collapse
hwmt. ru is unavailable
mcn1970 said:
hwmt. ru is unavailable
Click to expand...
Click to collapse
http://hwmt.ru/hwmtsite/firmware-database/
working fine for me.
Edit: I should probably have posted the full link in my previous post. Sorry.
ante0 said:
http://hwmt.ru/hwmtsite/firmware-database/
working fine for me.
Edit: I should probably have posted the full link in my previous post. Sorry.
Click to expand...
Click to collapse
is it all procedures safe? no risk of hard brick?
ante0 said:
Just some clarification: (eventhough you wrote it's for AL00C00B213, which I missed xD)
Flashing stock boot is only needed if you're already rooted.
Boot image B213D is only for AL00C00. If you have a different model/build, use the boot image for that specific build:
Download your stock firmware from hwmt.ru and Huawei Update Extractor. Extract update.app from your firmware zip.
Open update.app in Huawei Update Extractor. Rightclick on BOOT and click on Extract selected.
Flash the extracted boot.img using fastboot in download mode (fastboot flash boot boot.img).
OEM Unlocking is required to be enabled. It's just not there in the chinese version (AL00). So check if it's there first and enable if it is.
Click to expand...
Click to collapse
i unlocked the bootloader and flashed recovery but my OTG stick is not recognized and cannot be mounted. also while in recovery the phone is not seen on PC.
i tried with both recoveries above.
ADB sideload doesnt work...keeps saying starting ADB sideloading features...in TWRP sdcard content is a bunch of files with weird names...
therefore how can I root the phone?
someone please help me!!
mcn1970 said:
i unlocked the bootloader and flashed recovery but my OTG stick is not recognized and cannot be mounted. also while in recovery the phone is not seen on PC.
i tried with both recoveries above.
ADB sideload doesnt work...keeps saying starting ADB sideloading features...in TWRP sdcard content is a bunch of files with weird names...
therefore how can I root the phone?
someone please help me!!
Click to expand...
Click to collapse
edit: solved it
any OTA after?
hi guys. You may or may not find this interesting. I certainly did. I'll post this in the mate 9 pro forum as well but i just thought i could get some ideas from as many of guys as possible seeying that theres a lot more posts here for mate 9 in general.
I have chinese version mate 9 pro that has been rebranded from AL00 to LON Spcseas and rooted. Build number b228. Anyway i recently saw in FF the new b229 so i downloaded all three files which had longer file names than usuall by the way. In twrp, the only file that was visable was the update.zip. So i renamed the hw and public zip files to what they would usually be named. Wiped data, and flashed all three files. Then reflashed supersu.
This is the interesting bit ( i think ). My imei numbers have changed, before flashing, the first imei number ended in 7 - now it ends with 4, the second imei number ended in 9 and now it ends with 7. Also, i now have a MEID number visable which was not there before and a section called android security patch level. Oddly enough im not getting any issues out of play store, im on play store right now and not a single problem regarding authentication. The build number is the same as well. As far as functionality goes, everything seems to be tip top, in fact everything seems to be working better, even unofficial exposed is working well. Only one thing isn't working properly. In phone manager there was a feature in the battery section that darkens the interface for everything to save power and prolong battery. That doesn't seem to be working anymore. In App - Permissions, the permissions is greyed out and it says no permissions requested.. Any thoughts or explenations guys??
Trying to flash another orginal stock rom
I bought a Mate 9 Pro, China Version (LON-AL00C00) want to install Mate 9 Pro, Asia Version (LON-L29C636) software on it. All explanations about Mate 9 Pro is for models which have SD Card. My Mate 9 Pro with dual sims and not containing a SD Card enrty.
I succesfully unlocked the bootloader, installed TWRP but couldn't flash LON-L29C636 stock software. Because TWRP don't see update.zip file. Not only update.zip, any files I downloaded or copied before. When I put a OGT TWRP suddenly exits and phone restarts.:crying:
As you see I can't flash a zip file and ofcourse superuser zip file to root as well. I'm stuck in this triangle. Please give me a hand guys.
I can't root my phone. Because I can't view and locate any file of my phone. When I plug a ogt cable twrp exits and phone restarts. 6GB-128GB Dual Sim version
---------- Post added at 11:48 AM ---------- Previous post was at 11:47 AM ----------
Seems I am the only one who is looking for something about Mate 9 Pro
CrisperNeO said:
This thread applies to Huawei Mate 9 Pro only (model LON*, as M9Pro below). For Mate 9 (model MAH*) please go to the corresponding forum.
-----
Disclaimer:
I won't be responsible for bricked phone. Proceed with your own risk, make sure you know what you are doing.
This thread can be seen as a guide if your phone has exactly the same model and build version as mine. Otherwise please consider it as a description of my experiences for unlocking, flashing and rooting the phone.
SUPPORTED DEVICES:
LON-L29
LON-AL00
-----
As a start, this phone is great and I feel that it doesn’t need to be unlocked and rooted for a stable and long lasting daily use. However, unlock and root is almost a religion if you use Android phones
As a piece of info, big thanks to @raimondomartire, there is a thread for unlock, flash TWRP and root in the Mate 9 forum https://forum.xda-developers.com/mate-9/development/recovery-huawei-mate-9-pro-unofficial-t3546976, which is however according to my experience not totally applicable for the M9Pro anymore. There are also several other threads on the Mate 9 forum. Many things can be shared between both phones, but not always. Be careful about what you are doing!
-----
General info and attentions:
-My phone is M9Pro LON-AL00 (All net version from Chinese Mainland); LON-L29 (International version) should also work.
-This thread applies for build LON-AL00C00B213. Can be also applicable for similar builds, but I couldn’t test. Please report.
-None of the current builds of TWRP (up to 3.1.0) can decrypt data partition by default, which means you could only format the data partition in TWRP in order to access it in recovery (for backup to and install from internal storage etc.). But after formatting, you have to flash Huawei’s special stock data back to data partition (/data/hw_init), otherwise several functions of Huawei ROM won’t work. Refer to this (https://forum.xda-developers.com/showpost.php?p=71302827&postcount=627) or this (https://forum.xda-developers.com/showpost.php?p=72497328&postcount=204). Thanks to @gm007 and @ante0
-There are several root methods which handles encrypted or decrypted data partition. I didn’t format the data partition, i.e. data is still encrypted. If you want to format the data partition, please refer to this thread: https://forum.xda-developers.com/mate-9/how-to/guide-how-to-root-mate-9-decrypt-data-t3569986. Thanks to @eddmecha
-If you need stock ROM, refer to useful links below. Use Huawei Update Extractor to extract the individual partitions from the ROM: https://forum.xda-developers.com/showthread.php?t=2433454
-----
Unlock bootloader:
There is enough info in the internet about unlocking M9Pro’s bootloader. Just a few points to mention:
-Generally, you can follow the steps in @raimondomartire thread (https://forum.xda-developers.com/mate-9/development/recovery-huawei-mate-9-pro-unofficial-t3546976). But unlike he describes in his thread, there is no OEM Unlock options in the developer options anymore. Just use ADB to unlock.
-FRP unlock is not required!
-Huawei enables now a 14-day limitation, where you can officially get the bootloader unlock code 14 days after you first activate your Huawei ID on your phone and have logged in using your Huawei ID 14 CONSECUTIVE days.
-To go around this limitation, you can use dc-unlocker to get the bootloader code immediately. Google yourself
-----
Flash TWRP:
-Still, you can follow the steps in @raimondomartire thread (https://forum.xda-developers.com/mate-9/development/recovery-huawei-mate-9-pro-unofficial-t3546976).
-The image from this thread is 3.0.3, which has some bugs built in, especially when flashing SuperSU.
-You could use TWRP 3.1.0-1 from https://forum.xda-developers.com/mate-9/development/recovery-unofficial-twrp-huawei-mate-9-t3515617, but this one seems to have problem to be recognized as ADB device in recovery.
-There is a version 3.0.2 for Mate 9, which seems to have problem mounting USB-OTG.
-If your data partition is encrypted, you can only use ADB sideload or USB-OTG to install anything.
-If you want to do data wipe in TWRP, you have to flash Huawei’s special stock data back to data partition. See above general info and attentions.
-----
Root:
Firstly, thanks to @ante0 for explaining different flags in the root methods: https://forum.xda-developers.com/showpost.php?p=72504501&postcount=210. Some more discussions between us are also around this post.
I also tried several other root tools on the market (mobilego, vroot, YoRoot, OneClickRoot, iRoot etc.), NONE of them works.
As mentioned, there are different root methods around for unlocking M9Pro, depending on if you want to format your data partition. For me, I didn’t format, and SuperSU works for me. And the mate_9_pro_root.zip from @raimondomartire thread didn’t work for me.
I followed the steps below:
1.Get TWRP 3.1.0-1 (https://forum.xda-developers.com/mate-9/development/recovery-unofficial-twrp-huawei-mate-9-t3515617)
2.Disable fingerprint ID (I think it’s probably optional, but have read somewhere that fingerprint stops working after flashing root).
3.Flash stock boot image for B213D (in download section). I think it’s optional too, but if you have tried other methods before, you can do this step to make sure your boot is stock and clean
4.Flash TWRP 3.1.0-1
5.Flash SuperSU-v2.79-MATE9-init.d_support_no_decrypt-signed.zip (in download section) via USB-OTG (in TWRP the device is not recognized as an ADB device, hence no “ADB sideload”). Thanks to @ante0 for building this zip!
6.Reboot – phone will reboot itself twice and SuperSU.apk will be installed automatically
7.You could flash back to 3.0.3, if you want the ADB sideload function.
-----
Download:
-TWRP 3.0.3-1: https://forum.xda-developers.com/mate-9/development/recovery-huawei-mate-9-pro-unofficial-t3546976
-TWRP 3.1.0-1: https://forum.xda-developers.com/mate-9/development/recovery-unofficial-twrp-huawei-mate-9-t3515617
-SuperSU modified for M9Pro (thanks to @ante0): https://mega.nz/#!bR8D2Bab!bIgMLVmoll9R0GFqoFgkLxULrXlQ2710INt3TNbuI0c
-Boot image from B213D: https://mega.nz/#!LFlGTTZY!AaFq-_quM44YlK_Qdh9PgOjBE3Wtepmyz5OAuo_mabw
-----
Useful links:
-Stock firmware: http://hwmt.ru/oth/HWFF/info/view.php?find_model=lon
-Huawei Update (ROM) Extractor: https://forum.xda-developers.com/showthread.php?t=2433454
Enjoy your Mate!
Click to expand...
Click to collapse
I unlocked bootloader but couldn't root. Anyway I wanted to rebrand my phone to Asia version. Now I'm done but not successful because there is no Google,frp locked, and version is test one.
I can't install twrp because frp lock don't allow it. Also twrp can't read 128 GB internal memory, so I needed to install from pc.
Is there anyway to resolve and install stock Oreo version to my Mate 9 Pro or do you suggest me to resolve it via paid services?
PRA-LX1 cihazımdan Tapatalk kullanılarak gönderildi
livevalue said:
I unlocked bootloader but couldn't root. Anyway I wanted to rebrand my phone to Asia version. Now I'm done but not successful because there is no Google,frp locked, and version is test one.
I can't install twrp because frp lock don't allow it. Also twrp can't read 128 GB internal memory, so I needed to install from pc.
Is there anyway to resolve and install stock Oreo version to my Mate 9 Pro or do you suggest me to resolve it via paid services?
PRA-LX1 cihazımdan Tapatalk kullanılarak gönderildi
Click to expand...
Click to collapse
I've installed Oreo to Mate 9 Pro. If you have 128GB edition don't try to install anything from internal storage. That's it.
PRA-LX1 cihazımdan Tapatalk kullanılarak gönderildi
Hi guys, for re-branding there are threads in general Mate 9 forum. I didnt do it and am not planning to do it either...
CrisperNeO said:
Hi guys, for re-branding there are threads in general Mate 9 forum. I didnt do it and am not planning to do it either...
Click to expand...
Click to collapse
Rebranding is easy with HWOTA system if you will keep your phone EMUI 5.0 Nougat. And there is no risk if you make everything clearly.
PRA-LX1 cihazımdan Tapatalk kullanılarak gönderildi
never used Huawei before have a couple of questions
1. Is there anyway to get back to full stock with relock bootaloder in case the device need to go to service center?
(assume unlock bootloader with dc-unlocker not huawei id one)
2. From question 1 what do i need to do or backup before root?
thnak you so much!
44alphabeT said:
never used Huawei before have a couple of questions
1. Is there anyway to get back to full stock with relock bootaloder in case the device need to go to service center?
(assume unlock bootloader with dc-unlocker not huawei id one)
2. From question 1 what do i need to do or backup before root?
thnak you so much!
Click to expand...
Click to collapse
Yes you can always flash stock ROM as factory out, if you are not in Oreo.
And you can root it. It's your own protection to have a backup. I suggest you have, anyway it's up to you. You can loose all your data after root.
Hi, yersterday I used TWRP trying to install a newer firmware and I wiped system partition and now it does not boot because it doesn't have an OS. I was on EMUI 8 (636) trying to update the firmware.
Is there any way to flash a firmware via TWRP or Fastboot on EMUI 8 (i know partition names change on Oreo).
Thanks!
I just bought a Nuu R1 Rugged Phone. It has Oreo 8.1.0 on it.
It is an "unlocked" phone. But I don't know if unlocked refers to the phone carrier or to the boot loader. (I'm thinking phone carrier.)
The last I rooted my tablets was Android 5, which required using a custom script that a dev here wrote that temporarily ran CW via fast boot.
I would like to root my R1. I hear now that Magisk is the way to go. (Instead of SU.)
Most every Guide says that I have to have TWRP installed before installing Magisk. But there's no TWRP for the R1. And I am incapable of compiling my own.
I learned, from Nuu Tech Support, that I can get into the phone's Recovery mode with some hidden button pushes. Here's a screen shot:
My first question is, could I simply install Magisk by selecting "Update from SD card"?
If it's not that easy, then, second: I can also get to a fastboot screen. (Not shown here.) Could I install Magisk from ADB on my computer?
I suppose a third question: Is there a version of TWRP that's compatible with this phone? And if so, how do I find it? It would be nice to have a Nandroid backup.
I am willing to show various screens that come up from various button pushes if that would help a dev here.
More data for TWRP'ing
So, I see that one needs an image of the OEM ROM to compile TWRP. I found two sites on the web that claim to have the ROM. (Before the R1 was officially released.) Sounds sketchy. Will try to get an image from Tech Support.
In the meantime, I found that the bootloader can be unlocked (or allowed to be unlocked) via a setting under Developer Options.
I contacted Nuu Mobile Support and they were kind to send me the MediaTek USB drivers for the R1.
It was a two step process to get the driver installed for ADB. But now I have access to the R1 via ADB.
I read here on the forums that I can boot TWRP via fastboot, and not risk ruining/corrupting the R1's Recovery Partition.
Anyone know of a TWRP model version that's close enough to work on the R1? (I presume a TWRP for another MediaTek device might work?)
I would hate to try KingRoot to get root.
I found a website called unofficialtwrp.com. It has a TWRP for the MediaTek 6739, running Oreo 8.1, with 16/2 GB. That's exactly what the Nuu Mobile R1 has.
So, hopeful that this would allow me to root my R1, I tried it. (Short version: Didn't work.)
I already had ADB installed and could talk to my R1 via ADB.
But once the R1 had booted into fastboot mode via ADB, I got a message from fastbood devices that it was "waiting."
I learned that that message means that I didn't have drivers for fastboot.
I ended up installing a fresh version of Win8.1 and using the Windows' updater to find the needed drivers. I had to have the R1 plugged in to the USB in fastboot mode for this to work. After that, I could talk to the device via the fastboot command.
So I unlocked the boot loader (which wiped my data - not every Guide warns you about that) and I did "fastboot boot recovery.img."
I got the message that the recovery file had transferred. After abotu 15 seconds, the phone rebooted. But no TWRP.
Rats.
I didn't want to try the fastboot flash command in case this unoffiical twrp from an unofficial site bricked my phone. If I understand things correctly, booting in fastboot to the recovery.img should give me a temporary instance of TWRP.
Presumably, after copying Magisk into memory, I would be able to get root that way.
PMikeP said:
I found a website called unofficialtwrp.com. It has a TWRP
Click to expand...
Click to collapse
Whoa you have been busy you must've heard XDA helps those who help themselves.. :highfive:
I just dropped by to say, 1st rule of modding is taking a pristine stock backup..
For MTK devices, there is a tool called SP Flash Tools, a quick search will help you take a full backup using this tool.
Afterward, you can even try using SP Flash Tools to flash a Magisk patched boot image to your device for ROOT!
Hope this helps!
Thanks. I did see SP Flash Tools mentioned and I did take a look at it. While I've rooted before, I'm trying to get my head around a Scatter File.
Everything I've read so far - well, almost everything - says that I need TWRP to get Magisk installed. But if you think it can be done via SP Flash Tools, I'll start playing with it.
Root nuu r1
Did u ever manage to figure out how to do this & get TWRP to install? :fingers-crossed:
No, I haven't had time to play with rooting lately. I still would like to root it tho.
Anyone know how to root the nuu phones?
someone has the boot.img i need the image
I will port TWRP for you in case you have stock recovery.img
jjgvv said:
I will port TWRP for you in case you have stock recovery.img
Click to expand...
Click to collapse
plis
do you have stock rom?
Hi all,
I put my hands on a Philips 10BDL4151T, an Android 7.1.2 tablet powered by a RockChip rk3368.
My goal is to root it, and these are my findings/what I tried so far:
-AIO root tools (KingRoot et al.) don't work
-Bootloader unlock works fine
-RockChip AndroidTools for flash dump works fine
-fastboot can boot images only up to 16MB
-Dumped recovery.img doesn't boot (it's 32MB)
-No official sources/updates/OTA images are available.
-None of the available TWRPs for rk3368 devices found in the wild boot: the ones in AOSP format are too large and the others in KRNL format seems not compatible (nothing on screen and usb stops working)
The last thing that came to my mind was dumping boot.img and patching it with Magisk Manager, but i haven't flashed it back yet because I'm too afraid of bricking it (and I don't know if AndroidTool can be used to restore a bricked device)
What should i do? Is writing back patched boot.img safe? Can I eventually recover from it?
Or are there other ways?
Thank you
Any news on this one? I also have the same device and what to have google play store...
Hi all,
I'm new here and was wondering if I could get some help.
I recently purchased an Oukitel C15 Pro, which I am now trying to root but without any success.
From my own research, there are 2 versions of the Oukitel C15 Pro, one that is 2 gb ram and another one which is 3gb ram. Mine is the updated version 3gb with V14 build number.
Here is some info:
Build number - OUKITEL_C15 Pro_V14.0_20191121
Baseband - E557_61_P0_LWTG_V0.3.0_S191028
OS - Android 9.0
Processor - MT6761V/WBB - ARMv7 Processor rev 4, 4 cores at 2ghz arm cortex a53
So far I have managed to find the stock rom file and twrp recovery file for Oukitel C15 Pro.
I seem to be having issues with booting into recovery. I have literally tried everything.
I've tried flashing it via adb, trying to boot from adb into recovery etc. I've also tried using the SP flash tool. It does the flashing perfectly fine without any errors as I have already unlocked the bootloader and debugging is on, but the phone just seems to always load into its stock recovery and not twrp.
I've also tried patching the boot file with majisk, again no errors whatsoever, however when trying to boot, it boots into the normal system without any changes being made. I have all drivers installed etc and I honestly have no idea what I'm doing wrong.
I know that on some phones you have to boot directly into recovery after flashing otherwise the stock recovery will overwrite the twrp but again no luck, it just boots into the stock file.
I have also tried booting it via adb directly into recovery once flashed but no luck, normal recovery loads. When I try to do adb sideload I get error E 21 verification failed.
Does anybody have any advice on what I need to do to root my device? Maybe the files I have downloaded are wrong? I have no idea. I'd literally appreciate any help/links etc.
Thank you
You are not alone
zxckxx said:
Hi all,
Does anybody have any advice on what I need to do to root my device? Maybe the files I have downloaded are wrong? I have no idea. I'd literally appreciate any help/links etc.
Click to expand...
Click to collapse
Hi there,
I have one of these phones too and am going to start hacking it shortly. Did you make any further progress in the last few weeks? My phone is virgin at this stage. I will report back if I get anywhere.
Cheers
B
nessesitetem_gearallnews.com/how-to-install-lineage-os-17-gsi-for-oukitel-c15-pro-android-10/
@zxckxx
Disable dm-verity/AVB if it's enabled, otherwise you wont have any luck flashing a Custom Recovery, a Custom ROM or patched boot
Code:
adb devices
adb disable dm-verity
adb reboot
Help to root
Pls how did u unlock bootloader
tvroman said:
You are not alone
Hi there,
I have one of these phones too and am going to start hacking it shortly. Did you make any further progress in the last few weeks? My phone is virgin at this stage. I will report back if I get anywhere.
Cheers
Were you able to root it successful?
Click to expand...
Click to collapse