Related
Hi guys,
does anyone know how to root the ZTE blade V7?
I mean, root is a necessity and i just dont seem to find a way to do it.
And fo course i dont wanna ruin the new device.
Thanks in advance
Same probl
im in the same situation!! did you manage to find something out???
i havent, hope somebody does...
drakal10 said:
i havent, hope somebody does...
Click to expand...
Click to collapse
There is some Recoverys and Su files to find with Google search but...
... There is no meta mode/bootloader (fastboot) drivers for the Blade v7.
If everybody has manage to root or unlock the bootloader share the drivers plz )
:fingers-crossed:
The bootloader can be unlocked in the Settings. Enable "Developer Options" by going to "Settings > About" and then click on the "Build Number" until you see a message "You are now a developer". From the General Settings a new menu option "Developer Settings" is now available. In "Developer Settings" there is a setting called "OEM Unlocking". Set it to true, then use fastboot to unlock the bootloader with "fastboot oem unlock"
Fastboot doesn't work (I'm on ArchLinux). It just doesn't detect the device at all, so after typing "fastboot oem unlock", it just says "< waiting for any device >"
ADB works, but I can't get fastboot to work (even as root)
I am experiencing the same issue on OSX. ADB works but fastboot doesn't ever connect. I wrote a script to run lsusb every second while switching the phone between recovery, bootloader, and normal boot. Here are the vendor ids with my notes in parentheses:
Code:
ID 0e8d:2000 MediaTek Inc. MT65xx Preloader (for 3 seconds pre boot)
ID 0e8d:2000 MediaTek Inc. MT65xx Android Phone (Bootloader)
ID 0e8d:2008 MediaTek Inc. MT65xx Android Phone Serial: 0123456789ABCDEF (OFF "charge screen")
ID 19d2:0307 19d2 BLADE Serial: 10063399 (During boot before decrypt volume screen [pin])
ID 19d2:0306 19d2 BLADE Serial: 10063399 (After entering in password to decrypt volume)
I wrote a script that ran
Code:
fastboot -i 0x0e82 devices
and
Code:
fastboot -i 0x19d2 devices
every second and it never returned anything during these different boot cycles. Recovery mode doesn't seem to produce any usb devices even after initiating an adb sideload. These tests were conducted with the Developer Option "OEM Unlocking" enabled in Marshmallow 6.0. The device is branded for the Telcel operator located in Mexico.
Are there really "drivers" that need to be installed above and beyond the android platform tools? It seems to me as if the fastboot interface to the bootloader was intentionally disabled by the manufacturer.
did anybody figure anything out? I tried using spft and flashing a recovery for a device which was basically identical however i seem to have bricked my device, (won't switch on, doesn't even light up when charging) if anybody figured anything out that'd be great
Fastboot
fastboot is only avaible when youre out of Metamode , you will still stuck there because you got no Serialnr .
Thats ok you dont need any to get root .
If someone wants to get root access pm me i´ve done it already.
I need an EU Stock ROM too so someone with an untouched EU ZTE BLADE V7 have to contact me pls :fingers-crossed::good:
Germany image maybe
ckrypt0r said:
fastboot is only avaible when youre out of Metamode , you will still stuck there because you got no Serialnr .
Thats ok you dont need any to get root .
If someone wants to get root access pm me i´ve done it already.
I need an EU Stock ROM too so someone with an untouched EU ZTE BLADE V7 have to contact me pls :fingers-crossed::good:
Germany image maybe
Click to expand...
Click to collapse
Hi ckrypt0r, can you explain how to get the device into fastboot mode? I have unlocked the bootloader in the Android Settings -> Developer menu. I would like to flash a custom recovery and ROM.
Thank you
what you can try to root this zte version might work with how i rooted my zte blade l5 with supersu no flashing, no pc needed
download kingroot apk
https://forum.xda-developers.com/devdb/project/dl/?id=23776
go to this page
https://forum.xda-developers.com/a310/general/how-to-remove-replace-kingroot-kinguser-t3308989
it will show you what to download and how to do it
https://forum.xda-developers.com/zte-blade/general/unbrick-root-jaqrom-xposed-t3575488
Could somebody backup the NVRAM partition with spflashtool and upload it please
you should have to recover your NVRAM by https://mega.nz/#F!iUIAgRyS!p9Mj-VlDUlNVlSpr8ZS9vw
turn off your phone start the program and plug it in , now you´re able to write IMEI and Serial to your device.
if someone want to develope on this devices here some other tools that bring you forward https://mega.nz/#F!mEpAxR5B!7nPoBKbLRpoOU8eYxt3NLA
hope you will enjoy it and maybe give an feedback or maybe a thanks !
thanks alot for reading
ckrypt0r said:
fastboot is only avaible when youre out of Metamode , you will still stuck there because you got no Serialnr .
Thats ok you dont need any to get root .
If someone wants to get root access pm me i´ve done it already.
I need an EU Stock ROM too so someone with an untouched EU ZTE BLADE V7 have to contact me pls :fingers-crossed::good:
Germany image maybe
Click to expand...
Click to collapse
I have untouched zte blade v7 lite, can you help me root please thank you?
Hi im from germany and i have a german zte blade v7
ckrypt0r said:
fastboot is only avaible when youre out of Metamode , you will still stuck there because you got no Serialnr .
Thats ok you dont need any to get root .
If someone wants to get root access pm me i´ve done it already.
I need an EU Stock ROM too so someone with an untouched EU ZTE BLADE V7 have to contact me pls :fingers-crossed::good:
Germany image maybe
Click to expand...
Click to collapse
hi can u help me with rooting my phone?
help rooting for ZTE blades6 too..
terbeaux said:
Hi ckrypt0r, can you explain how to get the device into fastboot mode? I have unlocked the bootloader in the Android Settings -> Developer menu. I would like to flash a custom recovery and ROM.
Thank you
Click to expand...
Click to collapse
There is more easiest method with SPFlashTool, custom recovery and scatter file to get TWRP and root for Blade V7
It seems that unlocking the BootLoader on the WileyFox Swift2+ is even easier.
To unlock the boot loader (WARNING!!! This wipes your user data!!!)
Go To 'Settings - About Phone' Tap 'Build Number' seven times to enable 'Developer Options'.
Go To 'Developer Options' Enable 'Advanced Reboot', Enable 'OEM Unlocking'
...## not sure if these next few steps are even needed!!
Connect to computer running "Minimal ADB and Fastboot"
Open command window as administrator (To prevent Win10 messing around).
Enter command "fastboot oem unlock"
...##
Press the phone 'Power Off - Reboot - FastBoot'
PC detects device and states "Follow instructions on device screen"
Phone screen issues dire warnings about unlocking Bootloader.
Proceed and job done Bootloader is Unlocked (device at this point not rooted).
The stock Swift2+ Cyanogen Rom is no longer available - seek out the LineageOS rom instead
I unlocked my bootloader the other day and those are the same steps I did so I can confirm this works.
I then proceeded to root the phone with SuperSU 2.78. Worked a treat.
Swift 2 Plus and SuperSU
FelixPiers said:
I unlocked my bootloader the other day and those are the same steps I did so I can confirm this works.
I then proceeded to root the phone with SuperSU 2.78. Worked a treat.
Click to expand...
Click to collapse
Yes initially the only version of SuperSU I could find was v2.46, which kept failing.
Any help? My reboot menu doesn't have a fastboot option. Yes I have advanced reboot and oem unlocking enabled.
Edit: Sorted it. Turns out you have to reboot into the bootloader.
thejackle123 said:
Any help? My reboot menu doesn't have a fastboot option. Yes I have advanced reboot and oem unlocking enabled.
Edit: Sorted it. Turns out you have to reboot into the bootloader.
Click to expand...
Click to collapse
Is it too hard to google your question?
Works on most devices:
1) Turn off device
2) Hold VOLUME UP button
3) Connect device to PC via usb-cable
I installed SuperSU, before that I installed TWRP. Now I am unable to install the latest update "cm-marmite-a1478a0ee9-to-7aa1c797975e-signed"
When I download this update and perform the actual install, it gives an error. Restarting the phone via TWRP recovery gives the same error. I am getting "Error 7"
So no I want to revert back, to get rid off SuperSU and TWRP to install all updates and then later root the device with TWRP and SuperSU. How do I get the original state of the phone back?
Or do you have any advice how to get the latest update installed?
Thx.
SMessy said:
It seems that unlocking the BootLoader on the WileyFox Swift2+ is even easier.
To unlock the boot loader (WARNING!!! This wipes your user data!!!)
Go To 'Settings - About Phone' Tap 'Build Number' seven times to enable 'Developer Options'.
Go To 'Developer Options' Enable 'Advanced Reboot', Enable 'OEM Unlocking'
...## not sure if these next few steps are even needed!!
Connect to computer running "Minimal ADB and Fastboot"
Open command window as administrator (To prevent Win10 messing around).
Enter command "fastboot oem unlock"
...##
Press the phone 'Power Off - Reboot - FastBoot'
PC detects device and states "Follow instructions on device screen"
Phone screen issues dire warnings about unlocking Bootloader.
Proceed and job done Bootloader is Unlocked (device at this point not rooted).
The stock Swift2+ Cyanogen Rom is here
http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
Click to expand...
Click to collapse
Hi, mate
unfortunately teh link to the stock rom is not working.
Can u provide me with another working link?
I deleted my rom and i can't find the stock to reanimate my phone.....
EDIT!!!!
All done, device is restored
THy @ll
Rom location
RayfG said:
Hi, mate
unfortunately teh link to the stock rom is not working.
Can u provide me with another working link?
I deleted my rom and i can't find the stock to reanimate my phone.....
EDIT!!!!
All done, device is restored
THy @ll
Click to expand...
Click to collapse
Just to confirm the stock room is still at this location as at 2nd march 2017
http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
"Just to confirm the stock ROM is still at this location as at 2nd march 2017 :"
Link above does not work now, however below one does.
https://androidfilehost.com/?w=files&flid=126553
Hmmm. I'm going to try again. Before I got fastboot in red and Dvice Status: Locked. But I'll try again, see where I get.
Image of issue: https://ibb.co/jfLPye
edit: Updating to the latest Oreo update (8.1 I think)
---------- Post added at 08:34 AM ---------- Previous post was at 08:14 AM ----------
ohhhhhhh, I had to turn the phone off while connected, already running "adb & fastboot" (not just adb) then (phone connected in USB debugging mode) turn off the phone and hold volume up (no need to hole the power key as connected and I got the option to unlock with a warning that I may void the warranty. Then my phone encrypted/re-encrypted itself (I think it was already encrypted).
Now to flash TWRP (3.2 I think) and flash a custom ROM (Lineage 15.1 / 8.1 Oreo) Not sure if I should root or not. And if I do, should I root before installing 8.1?
got damit i never understand how to flash twrp i followed what google said.
fastboot flash recovery XXX.img it does its thing i reboot still no recovery im on stock cm12 ? i think or cm13 android 6.0)
Hi, trying to unlock my S2+ bootloader with Ubuntu MATE. Have completed all the steps listed, entered fastboot oem unlock into the terminal which now just sits there displaying < waiting for any device >
Any idea where I go from here?
bl91 said:
Hi, trying to unlock my S2+ bootloader with Ubuntu MATE. Have completed all the steps listed, entered fastboot oem unlock into the terminal which now just sits there displaying < waiting for any device >
Any idea where I go from here?
Click to expand...
Click to collapse
your device isn't picked up by fastboot ...first of all install the very latest version of adb ...using the usual Ubuntu story
sudo apt-get install adb
sudo apt-get upgrade
sudo apt-get update
sudo reboot
then switch on your device
go to /settings/about/buildnumber
click until developer settings are enabled
go to developer settings
toggle oem unlock to on
toggle adb to on
WITHOUT SWITCHING OFF
connect device to pc/laptop with original orange wileyfox cable
now your Ubuntu machine
must install drivers and Mount the phone so it should appear as a mounted volume on desktop
now open a terminal
now run the following :
sudo adb
sudo adb devices
now look on your phone and pull down the notification shadse ..make sure you have adb connected and file transfer mode ..if not change from charge to file transfer ...
there should be a pop up window on phone screen asking for permission for adb ..select allways allow and give pernission / authorization ..
now in terminal run adb devices and it should return some value as connected device
run:
adb reboot bootloader
phone will reboot to bootloader
run:
fastboot oem unlock
*use volume up to select yes
**beware will erase DATA ...
***if it doesn't work and adb and fastboot doesn't detect your device it is a driver problem but i haven't used Ubuntu in ages so can't remember steps to update your drivers other than updating the whole adb package
****some ubuntu instructions might be a little off as I've explained previously it's been a while
*****your waiting for device means
-adb service didn't start
+try "sudo adb"
-adb drivers out of date
+try sudo apt-get update
-adb on device not toggled to on
+toggle adb in dev settings
*adb authorization not given **should still see unauthorized device
-bad usb cable
+try another usb cable
-bad usb port
+try a different usb port
_____for clarity double check Ubuntu adb instructions and commands but this should put you on the right track____
---------- Post added at 08:30 AM ---------- Previous post was at 08:19 AM ----------
reggiexp said:
got damit i never understand how to flash twrp i followed what google said.
fastboot flash recovery XXX.img it does its thing i reboot still no recovery im on stock cm12 ? i think or cm13 android 6.0)
Click to expand...
Click to collapse
don't reboot immediately ..stock recovery will be flashed back over twrp
*i assume you know how to get to fastboot
adb reboot bootloader
fastboot oem unlock
*volume up for yes
fastboot flash recovery recovery.img
*make sure you have a copy of twrp called recovery.img in adb folder
when it says sending...
then is says writing ...
then it says done
DON'T REBOOT
UNPLUG USB
***MANUALLY BOOT TO BOOTLOADER USING VOLUME UP AND POWER
**** IN BOOTLOADER SELECT "RECOVERY"
you should then just wait on wileyfox first time it takes a minute or two don't know why then
it should boot to twrp
***you can take stock boot.img and patch it with magisk
-use: fastboot flash boot boot.img
-then you will have magisk and rooted
-using twrp apk or something like root rasher or flasher ..give apk root permission
-download twrp ..flash with apk from inside system ..after flashing select yes to reboot directly to recovery
Thanks very much, I've unlocked my bootloader now! Onto the TWRP, Magisk and LineageOS business now
bl91 said:
Thanks very much, I've unlocked my bootloader now! Onto the TWRP, Magisk and LineageOS business now
Click to expand...
Click to collapse
okay no problem
*i know everybody likes lineage and its usually more stable and the base for many custom roms
however just my 2cents worth ...i tried all the roms for our device ..but the by far the best for me was following the tutorial on how to make our device treble compatible ..
Then ...after 3-4 months of trying different treble GSI's i have stopped on Viper Official Pie 64bit A-only treble system.img ... at least give it a try after trying out lineageOs ..
you might thank me .
I can't get my device to show up usb debugging is on, Advanced Reboot', 'OEM Unlocking' etc. I've been trying for hours and hours. It shows up to transfer files if I want that mode so my PC is recognising it, but it doesn't seem to have drivers for adb. I've tried installing google usb drivers and also this: https://afterthoughtsoftware.com/posts/using-adb-with-wileyfox-swift
sorry if I haven't explained clearly, I'm just so sleepy from going around in circles. :|
I've rooted phones before and never had this issue. please can anybody help?
edit: have fixed I think! did two things at once so not sure which. I revoked usb devices so that my computer would have to ask permission again to connect (or something like this) and also clicked a thing on my PC to allow it to update what I think said driver icons automatically, which I wouldn't have thought would help, but it seemed to find the adb driver this time. I'd probably make more sense if it weren't 1am. :|
When i got my Swift 2 X, it came updated with 8.1 Oreo out of the box and the issue I had was unlocking the bootloader.
Sure fastboot oem unlock unlocked so I could flash recovery and roms but whenever I tried flashing a bootloader via fastboot, it gave me "FAILED (remote: Critical partition flashing is not allowed)". So that part was still locked.
This I fixed way back after searching around on my own about it but since the solution to this aint mentioned around here and I can't be the only one who have encountered this I think, I am just gonna add it in here.
There are now other commands to unlock your device, fastboot flashing unlock that does the exact same thing that fastboot oem unlock does and fastboot flashing unlock_critical is the command that unlocks the bootloader.
Both commands prompts you with the usual to confirm unlock and wipes your data.
It doesn't matter if you already unlocked the device with the oem command or flashing command, fastboot flashing unlock_critical should be able to unlock the bootloader either way.
My swift was also at 8.1 I had no problem unlocking the bootloader.
DH
RavZ75 said:
When i got my Swift 2 X, it came updated with 8.1 Oreo out of the box and the issue I had was unlocking the bootloader.
Sure fastboot oem unlock unlocked so I could flash recovery and roms but whenever I tried flashing a bootloader via fastboot, it gave me "FAILED (remote: Critical partition flashing is not allowed)". So that part was still locked.
This I fixed way back after searching around on my own about it but since the solution to this aint mentioned around here and I can't be the only one who have encountered this I think, I am just gonna add it in here.
There are now other commands to unlock your device, fastboot flashing unlock that does the exact same thing that fastboot oem unlock does and fastboot flashing unlock_critical is the command that unlocks the bootloader.
Both commands prompts you with the usual to confirm unlock and wipes your data.
It doesn't matter if you already unlocked the device with the oem command or flashing command, fastboot flashing unlock_critical should be able to unlock the bootloader either way.
Click to expand...
Click to collapse
bubba_66 said:
My swift was also at 8.1 I had no problem unlocking the bootloader.
DH
Click to expand...
Click to collapse
Doesn't seem that many who have this lock on their bootloaders, the only ones I could find here who had locked bootloaders the same way as I had are in the LineageOS 14.1 thread.
So at least I am not alone with that but sure makes me wonder how it is so for some while others not.
After unlock bootloader Everytime reboot always like this https://ibb.co/NSZR818
Hello,
I am trying to unlock my HTC U Ultra in order to get root and to install custom recovery. The computer I use has Ubuntu 14.04 installed on it.
What I have done:
- enabled Developer options
- enabled OEM unlocking and USB debugging
- I have Android Debug Bridge version 1.0.31 and fastboot installed
- I can see the device when running the
Code:
adb devices
List of devices attached
FA7371702310 device
- I can reboot to bootloader
Code:
adb reboot bootloader
After getting to the bootloader change into DOWNLOAD mode manually using volume Up and Down, select with Power
Code:
sudo fastboot oem get_identifier_token
[sudo] password for acer:
...
...GET THE TOKEN
use the steps from https://www.htcdev.com/bootloader/unlock-instructions/page-4/
Remaining steps to do: root and recovery
Hi
Could anyone help me
How to root my p10 lite?
And any way to unlock my bootloder
After huawei closed the link for code?
MoNabil said:
Hi
Could anyone help me
How to root my p10 lite?
And any way to unlock my bootloder
After huawei closed the link for code?
Click to expand...
Click to collapse
Only way to unlock your bootloader is to pay for dc phoenix...
nemanjsb said:
Only way to unlock your bootloader is to pay for dc phoenix...
Click to expand...
Click to collapse
And how much for that?
MoNabil said:
And how much for that?
Click to expand...
Click to collapse
I don't know, register on dc phoenix and u will see.
EDIT: I found in a forum where they say that the price is 5$ for code.
Files you need (P10 Lite): https://mega.nz/#F!TNQiFDrS!LeWgM5bukSz66UEL5zE1Tg
Part 1 - Unlock Bootloader:
Full guide how to unlock your Bootloader via DC-Unlocker or HCU Client - https://forum.xda-developers.com/honor-7x/how-to/how-to-unlock-huawei-bootloader-removal-t3780903
* If you use HCU Client then TURN OFF your Antivirus because it detects parts of the program as a Trojan! But don't worry, it's safe!
Also see this tutorial here - http://hcu-client.com/read-bootloader-code-huawei-phone/
Install ADB drivers (adb-setup-1.4.3.exe)
Once you get the unlock code turn OFF the phone, press and hold only VOL DONW and connect it to PC via USB cable.
The phone will boot in to Bootloader mode.
Open PowerShell or CMD window and use this command:
fastboot oem unlock <your_unlock_code>
On the phone choose YES with the buttons and bootloader will unlock.
The phone will be factory reseted!!!
Part 2 - Root the phone:
Go to Settings -> System -> About Phone -> Click 7-8 times on the Build Number (until you see a message that you're developer)
Go to Settings -> System -> Developer options -> Enable USB Debugging
Turn OFF your Phone, press and hold VOL Down and connect it to the PC via USB cable.
The phone will boot in to Bootloader mode, but this time you will see this:
Bootloader: Unlocked
FRP: Unlocked
Open PowerShell or CMD window and use this command:
fastboot flash ramdisk patched_boot.img
fastboot reboot
That's all. Your phone is rooted with Magisk!
If you need just install latest Magisk Manager.
patched_boot.img is patched stock RAMDISK.img (boot file)
REMEMBER:
1. You CAN NOT install OTA update if you phone is rooted (during instalation gives error)
2. You CAN install only FullOTA update but you will lose the root
3. After every system update (FullOTA) you should run the phone to Bootloader mode and flash patched_boot.img again if you want root
nemanjsb said:
Only way to unlock your bootloader is to pay for dc phoenix...
Click to expand...
Click to collapse
Aalesund said:
Files you need (P10 Lite): https://mega.nz/#F!TNQiFDrS!LeWgM5bukSz66UEL5zE1Tg
Part 1 - Unlock Bootloader:
Full guide how to unlock your Bootloader via DC-Unlocker or HCU Client - https://forum.xda-developers.com/honor-7x/how-to/how-to-unlock-huawei-bootloader-removal-t3780903
* If you use HCU Client then TURN OFF your Antivirus because it detects parts of the program as a Trojan! But don't worry, it's safe!
Also see this tutorial here - http://hcu-client.com/read-bootloader-code-huawei-phone/
Install ADB drivers (adb-setup-1.4.3.exe)
Once you get the unlock code turn OFF the phone, press and hold only VOL DONW and connect it to PC via USB cable.
The phone will boot in to Bootloader mode.
Open PowerShell or CMD window and use this command:
fastboot oem unlock <your_unlock_code>
On the phone choose YES with the buttons and bootloader will unlock.
The phone will be factory reseted!!!
Part 2 - Root the phone:
Go to Settings -> System -> About Phone -> Click 7-8 times on the Build Number (until you see a message that you're developer)
Go to Settings -> System -> Developer options -> Enable USB Debugging
Turn OFF your Phone, press and hold VOL Down and connect it to the PC via USB cable.
The phone will boot in to Bootloader mode, but this time you will see this:
Bootloader: Unlocked
FRP: Unlocked
Open PowerShell or CMD window and use this command:
fastboot flash ramdisk patched_boot.img
fastboot reboot
That's all. Your phone is rooted with Magisk!
If you need just install latest Magisk Manager.
patched_boot.img is patched stock RAMDISK.img (boot file)
REMEMBER:
1. You CAN NOT install OTA update if you phone is rooted (during instalation gives error)
2. You CAN install only FullOTA update but you will lose the root
3. After every system update (FullOTA) you should run the phone to Bootloader mode and flash patched_boot.img again if you want root
Click to expand...
Click to collapse
This is for root or for unlock bootloder?
Can i unlock bootloder with out pay for that?
And what is the way to install rooted roms for my device..
MoNabil said:
This is for root or for unlock bootloder?
Can i unlock bootloder with out pay for that?
And what is the way to install rooted roms for my device..
Click to expand...
Click to collapse
This is unlock bootloader + root.
If you want rooted stock rom, then root is just one simple step: fastboot flash ramdisk patched_boot.img
There is no free way to unlock bootloader.
If you want to install custom roms then flash TWRP:
fastboot flash recovery_ramdisk TWRP.img
But DO NOT flash Pretoriano80's TWRP because it's for stock rom only and isn't support custom roms!!!
Maybe try this:
Haky86's TWRP - https://www.haky86.com/hi6250/twrp-emui-8-hi6250/
Haky86's Android 9.0 - https://www.haky86.com/hi6250/emui-8-hi6250/
ArrowOS and AOSP are stable.
Aalesund said:
This is unlock bootloader + root.
If you want rooted stock rom, then root is just one simple step: fastboot flash ramdisk patched_boot.img
There is no free way to unlock bootloader.
If you want to install custom roms then flash TWRP:
fastboot flash recovery_ramdisk TWRP.img
But DO NOT flash Pretoriano80's TWRP because it's for stock rom only and isn't support custom roms!!!
Maybe try this:
Haky86's TWRP - https://www.haky86.com/hi6250/twrp-emui-8-hi6250/
Haky86's Android 9.0 - https://www.haky86.com/hi6250/twrp-emui-8-hi6250/
ArrowOS and AOSP are stable.
Click to expand...
Click to collapse
Thanks
If i want to install root on my device
It is nessesary to unlock bootloder? or it is just separated step and helps to install roms
With new options and different features... Etc
MoNabil said:
Thanks
If i want to install root on my device
It is nessesary to unlock bootloder? or it is just separated step and helps to install roms
With new options and different features... Etc
Click to expand...
Click to collapse
U must unlock bootloader or u can't flash nothing. Free way to unlock bootloader was with huawei code but now u must pay for dc phoenix...
MoNabil said:
Thanks
If i want to install root on my device
It is nessesary to unlock bootloder? or it is just separated step and helps to install roms
With new options and different features... Etc
Click to expand...
Click to collapse
You are going to screw up your phone in this learning process .Unless you have another phone and this p10 is your 2nd phone then you can try & error .No matter what you must open yr bootloader to proceed next step .Means additional cost for sure .
Good luck
Well, I asked for huawei support for unlock code. I had to send them details and I got the code in almost a month
Hey there guys! Is it still available to get the code directly from huawei? How could I request them the code? I recently received this phone as present and it is as it came from factory but i want to install custom roms in my P10 lite is it still possible?
Thanks in advance for your help, I really wouldn't like to screw up my new phone! Cheers!
Aalesund said:
Files you need (P10 Lite): https://mega.nz/#F!TNQiFDrS!LeWgM5bukSz66UEL5zE1Tg
Part 1 - Unlock Bootloader:
Full guide how to unlock your Bootloader via DC-Unlocker or HCU Client - https://forum.xda-developers.com/honor-7x/how-to/how-to-unlock-huawei-bootloader-removal-t3780903
* If you use HCU Client then TURN OFF your Antivirus because it detects parts of the program as a Trojan! But don't worry, it's safe!
Also see this tutorial here - http://hcu-client.com/read-bootloader-code-huawei-phone/
Install ADB drivers (adb-setup-1.4.3.exe)
Once you get the unlock code turn OFF the phone, press and hold only VOL DONW and connect it to PC via USB cable.
The phone will boot in to Bootloader mode.
Open PowerShell or CMD window and use this command:
fastboot oem unlock <your_unlock_code>
On the phone choose YES with the buttons and bootloader will unlock.
The phone will be factory reseted!!!
Part 2 - Root the phone:
Go to Settings -> System -> About Phone -> Click 7-8 times on the Build Number (until you see a message that you're developer)
Go to Settings -> System -> Developer options -> Enable USB Debugging
Turn OFF your Phone, press and hold VOL Down and connect it to the PC via USB cable.
The phone will boot in to Bootloader mode, but this time you will see this:
Bootloader: Unlocked
FRP: Unlocked
Open PowerShell or CMD window and use this command:
fastboot flash ramdisk patched_boot.img
fastboot reboot
That's all. Your phone is rooted with Magisk!
If you need just install latest Magisk Manager.
patched_boot.img is patched stock RAMDISK.img (boot file)
REMEMBER:
1. You CAN NOT install OTA update if you phone is rooted (during instalation gives error)
2. You CAN install only FullOTA update but you will lose the root
3. After every system update (FullOTA) you should run the phone to Bootloader mode and flash patched_boot.img again if you want root
Click to expand...
Click to collapse
I followed all your steps. It seems all done but the root is not completed at the end. I guess I do something wrong in Part 2...
Hi,
I have had a MotoG6 plus from a friend, but after upgrade it from 8.0 to 9.0 begans problems. The phone goes on crash and restart many time during usage of lots of Apps. I Tried a factory reset + reinstall alot of app, but nothing changed. The phone crash as well with same frequency. I decide to broke it and i tried to install a LineageOS16_9Pie. Unfortunatly during the Custom install, even if i followed a guide, unloking the bootloader, i really broke it, the bootloader and recovery partition. I have started the image of TWRP via fastboot to obtained a motoG6plus working (even without a proper bootloader) with LineageOS16_9Pie. To do it i've got the code from motorola site, to unlock the G6plus, after eneable USB debug + OEM Unlock from OS. With theLineageOS i have unlocked and locked oem many times using the OS without any problems . I have used the LineageOS for a week, after that, It started agan the same crashs i had with the stock rom 9.
I decided to reinstall the 8.0 version Evert , to remove the boot errors and because with the 8.0 was stable. After i installed the stock rom 8.0 evert i cant' unlock oem again . Into the developer option, the option "OEM unclock" is gray , disabeld not switchable . Even if i tried to unclock again from fastboot command , it say that i have to switch and anable "OEM Unlock" from the OS but i can't.
Is there a way to unclock byassing the OS or re-enable that option?
Try this command in terminal app:
Code:
:/ $ su
:/ # service call oem_lock 1 s16 allowed
The output should be:
Code:
Result: Parcel(00000000 '....')
WoKoschekk said:
Try this command in terminal app:
Code:
:/ $ su
:/ # service call oem_lock 1 s16 allowed
The output should be:
Code:
Result: Parcel(00000000 '....')
Click to expand...
Click to collapse
Thanks WoKoschekk, but i surely ' loaded a wrong rom, because the Moto G6plus don't have Wifi and connectivity via SIMs working, so I can't download any app. I am going to try to copy an app via apk on the SD. The good news is that the bootloader initial stop has disapeared, (but i still do not have any recovery)
Nothing to do with "install app unknown" o similar (sorry, my phone is in Italian). Even if i do have the apk terminal emulator, i Can't install because of the few app in list that i can unable to install unknown sources. In this list there isn't "File manager" .. i still have the error of parsing the package
If you downgrade from Pie to Oreo you will lost all connections. To get them back you must flash a Pie version of any Rom.
First of all flash the right and latest firmware.
I Would like to reburn another rom, but i can't because the option "Unlock OEM" is in "gray" not switchable, so for be is a bit hard. I am stuck..
Thanks anyway for your interest. I appreciated it.
Reggians said:
I Would like to reburn another rom, but i can't because the option "Unlock OEM" is in "gray" not switchable, so for be is a bit hard. I am stuck..
Thanks anyway for your interest. I appreciated it.
Click to expand...
Click to collapse
Flash the latest Magisk.zip to enable OEM unlock option.
WoKoschekk said:
Try this command in terminal app:
Code:
:/ $ su
:/ # service call oem_lock 1 s16 allowed
The output should be:
Code:
Result: Parcel(00000000 '....')
Click to expand...
Click to collapse
Hi
I finally copy a term.apk and installed with success ! (i have no root permissions on the device)
when i give
Code:
evert_n:/ $ su
the answer is:
Code:
/system/bin/sh: su: not found
127|evert_n:/
if send the command with #
Code:
:/ $ # service call oem_lock 1 s16 allowed
i get null
Code:
127|evert_n:/
if i send the command without # (probably it is the cli after su level) like this
Code:
:/ $ service call oem_lock 1 s16 allowed
the answer is
Code:
service: Service oem_lock does not exist
WoKoschekk said:
Flash the latest Magisk.zip to enable OEM unlock option.
Click to expand...
Click to collapse
I have installed Magistik7.3.4.apk via filesystem but, i don't have connectivity and i can't install it via TWRP because i have the device locked so i can't even try to load TWRP via fastboot , so Magistik is not fully working unfortunatly..
Are you able to start the device in fastboot mode?
What is the error message when booting in TWRP?
For the "service oem_lock" command you need super user rights...
if you haven't solved it yet, use this to enable internet connection to your phone and you will be able to unlock the bootloader
https://github.com/Genymobile/gnirehtet
Has anyone solved this? Do I need to wait the 7 days to unlock it again?
I saw a thread where someone said they skipped the 7 days by changing the date of the device and rebooting, but that didn't work for me.