Ok, i only write here the method/Infos we have used for the guys who hazzle with the thread from here
Phone must be rooted. I have done this with 20A official ADEUWH (262-000)
Open a terminal on your device (Play Sore app that i have used)
type the following:
su root
cat /sys/firmware/fuse/odm_reserved >/data/local/tmp/odm_reserved
after that edit the file odm_reserved loctated here: /data/local/tmp/
change the line that it reflects this one: 0x00000000000000000000000000000000000000000000000000000040000000c8
save the changes, back to the terminal enter:
echo /data/local/tmp/odm_reserved >/sys/firmware/fuse/odm_reserved
than i used my PC (Phone connected via USB, USB-Debugging enabled) and entered
adb reboot bootloader
fastboot oem unlock
in a comand prompt
Press Vol Down, then Power Button from the Phone to unlock, screen went#s back, i waited 30Sec and rebootet
the phone, after that i rebootet back to the bootloader and installed the unsecure boot img and CWM.
And don't thank me - thx to Derjan23 for finding this out for us all!!!!!!!!!!!!!!
here is a script from exFAT, this script will do the job for you
fire3d said:
here is a script from exFAT, this script will do the job for you
Click to expand...
Click to collapse
I didn't need to issue the fastboot oem unlock command
Fantastic!
Absolutely brilliant, Worked fist time. Im now running CWM 6.0.3.1 touch recovery and just looking to install Cyanogenmod 10.1.
UK 234-000 V20A UNLOCKED. :good:
---------- Post added at 05:10 PM ---------- Previous post was at 04:51 PM ----------
cupidstunt said:
I didn't need to issue the fastboot oem unlock command
Click to expand...
Click to collapse
+1 Just a sweet and simple Fastboot command to push CWM to recovery.
works on 232-10 *_*
Omgf omgf it work it works!!!!!
fire3d said:
Ok, i only write here the method/Infos we have used for the guys who hazzle with the thread from here
Phone must be rooted. I have done this with 20A official ADEUWH (262-000)
Open a terminal on your device (Play Sore app that i have used)
type the following:
su root
cat /sys/firmware/fuse/odm_reserved >/data/local/tmp/odm_reserved
after that edit the file odm_reserved loctated here: /data/local/tmp/
change the line that it reflects this one: 0x00000000000000000000000000000000000000000000000000000040000000c8
save the changes, back to the terminal enter:
echo /data/local/tmp/odm_reserved >/sys/firmware/fuse/odm_reserved!
Click to expand...
Click to collapse
Here I get permission denied
Emin3ms said:
Here I get permission denied
Click to expand...
Click to collapse
Terminal must run at root now I'm on cm10.1
Sent from my rooted P880
Emin3ms said:
Here I get permission denied
Click to expand...
Click to collapse
Remember the to type su root and click enter/return first.
Done with 268-01!
Thanks a LOT!
@non4 said:
Terminal must run at root now I'm on cm10.1
Sent from my rooted P880
Click to expand...
Click to collapse
It runs at root
It returns "/system/bin/sh: can't create /sys/firmware/fuse/odm_reserved: Permission denied"
device rooted?
Which Rom is installed?
No sorry i closed the window when I edited odm_reserved, i try after enter su root now
---------- Post added at 07:11 PM ---------- Previous post was at 07:05 PM ----------
C:\root>adb reboot bootloader
C:\root>fastboot oem unlock
...
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) Bootloader is unlocked now.
FAILED (status read failed (Too many links))
finished. total time: 45.707s
But the hidden menu says Unlock. It's ok I can flash CM 10.1 ?
Thanks you guys for every tuto ^^ great community on xda
Emin3ms said:
No sorry i closed the window when I edited odm_reserved, i try after enter su root now
---------- Post added at 07:11 PM ---------- Previous post was at 07:05 PM ----------
C:\root>adb reboot bootloader
C:\root>fastboot oem unlock
...
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) Bootloader is unlocked now.
FAILED (status read failed (Too many links))
finished. total time: 45.707s
But the hidden menu says Unlock. It's ok I can flash CM 10.1 ?
Thanks you guys for every tuto ^^ great community on xda
Click to expand...
Click to collapse
There's no need to do any unlock command, once you have modified the file it's already unlocked, yes just install CWM with ROM manager and flash away!
Sent from my rooted P880
Can someone just confirm, the string of zeros that replace the original:
0x000000000000000000000000000000000000000000000000 00000040000000c8
Are you saying there is a space or is that a carriage return?
I cut and past it onto a rooted version of the 20A Rom that was leaked originally, no issue with replacing the file itself, but after a adb oem reboot it hangs at the LG screen.
Any advice please?
@lbert said:
Can someone just confirm, the string of zeros that replace the original:
0x000000000000000000000000000000000000000000000000 00000040000000c8
Are you saying there is a space or is that a carriage return?
I cut and past it onto a rooted version of the 20A Rom that was leaked originally, no issue with replacing the file itself, but after a adb oem reboot it hangs at the LG screen.
Any advice please?
Click to expand...
Click to collapse
You don't need to do this! Changing this file already unlocked it! But the screen you refer to is the boot loader, your command should have been adb reboot oem-unlock
Sent from my rooted P880
WORKS!!!! THX!!!
lol rofl xd!!!111 It worked. 262-000 Germany. Finally unlocked.
@non4 said:
You don't need to do this! Changing this file already unlocked it! But the screen you refer to is the boot loader, your command should have been adb reboot oem-unlock
Sent from my rooted P880
Click to expand...
Click to collapse
Yes I see, I only noticed the post above after I posted my question, I'm unlocked, with no warning or disclaimer, no erase or factory reset, in fact legally, LG mustn't have a leg to stand on here in terms of warranty because they never even got a chance to put the agree or disagree warning up.
Thank you for this. :crying:this is an emotional moment!
Emin3ms said:
No sorry i closed the window when I edited odm_reserved, i try after enter su root now
---------- Post added at 07:11 PM ---------- Previous post was at 07:05 PM ----------
C:\root>adb reboot bootloader
C:\root>fastboot oem unlock
...
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) Bootloader is unlocked now.
FAILED (status read failed (Too many links))
finished. total time: 45.707s
But the hidden menu says Unlock. It's ok I can flash CM 10.1 ?
Thanks you guys for every tuto ^^ great community on xda
Click to expand...
Click to collapse
Try "C:\root>adb reboot oem-unlock"...
Related
Hello xda community, I'd like to start with saying all the work done on this forum for open-source, freeware, and general android tweaks is awesome! Thank you.
So awesome in fact that I got a little bit ahead of myself with my new "Sprint HTC One". I followed this guide http://forum.xda-developers.com/showthread.php?t=2244060 to Unlock the bootloader, and root my phone. I then went a step further and wanted to flash a custom Rom. I followed this video, but strayed a little bit (whoops!). I went into twrp recovery, and flashed the "Beanstalk" super custom 4.3 (9/24/2013), along with smw6180_superwipe, and 4.3 gapps.
This actually was working for about 4 days, but now it won't connect to the mobile network even when toggling on and off airplane mode (A temp fix for the ROM). I went ahead and looked for solutions, namely to just get back to stock to see if the problem is bigger than just custom ROM. I relocked my bootloader, following http://www.youtube.com/watch?v=0WWNZpaQBh8&list=PLE395F615E026133D&index=11 Thus running into my current issue of Error 140 when trying to flash the RUU.
I'm asking anyone that could help, to offer suggestions on getting my phone back to stock. I would also like a couple suggestions for more stable ROM's (again, i knew what i getting into; ie disclaimers) that offer cool customization!
did you put the stock recovery back on before you locked the bootloader? Also are you super cid?
olorolo said:
did you put the stock recovery back on before you locked the bootloader? Also are you super cid?
Click to expand...
Click to collapse
No i don't believe so, Well now its not even going into twrp recovery. It displays tampered relocked security warning, s-on, hboot 1.44.0000 and This is the only screen i have for fastboot and the bootloader
I've seen this issue before let me take a quick look I think your ok
Sent from my HTCONE using Tapatalk 4
---------- Post added at 06:58 PM ---------- Previous post was at 06:57 PM ----------
You caught me in the middle of flashing the s-off firmware myself
Sent from my HTCONE using Tapatalk 4
Good to hear! Thank you for your time sir
get the newest twrp and rename it to recovery.zip put it in your cmd folder in bootloader type reboot bootloader fastboot flash flash recovery fastboot reboot
---------- Post added at 07:28 PM ---------- Previous post was at 07:18 PM ----------
once you have twrp back flash the s-off firmware http://forum.xda-developers.com/showthread.php?t=2467607 then the 4.3 rom of your choice
olorolo said:
get the newest twrp and rename it to recovery.zip put it in your cmd folder in bootloader type reboot bootloader fastboot flash flash recovery fastboot reboot
Click to expand...
Click to collapse
Either i don't understand fully or its failing. I have fastboot usb selected on my phone connected to usb on pc. I open my folder with cmd in it, and i typed what you said but error is "reboot" is not recognizable.
edit: I also have the trwp 2.6.3 image in the folder along with cmd.
Pug4567 said:
Either i don't understand fully or its failing. I have fastboot usb selected on my phone connected to usb on pc. I open my folder with cmd in it, and i typed what you said but error is "reboot" is not recognizable.
edit: I also have the trwp 2.6.3 image in the folder along with cmd.
Click to expand...
Click to collapse
twrp has to be renamed to recovery.zip try fastboot flash then type flash recovery then the name of the zip which is recovery.zip then fastboot reboot
I did that am getting error:cannot load recovery.
Also tried fastboot flash recovery openrecovery-twrp-2.6.3.0-m7wls.img
that resulted in this
sending 'recovery' (8608 KB)...
OKAY [ 1.120s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.880s
Or should i try http://forum.xda-developers.com/showthread.php?t=2314582
Pug4567 said:
I did that am getting error:cannot load recovery.
Also tried fastboot flash recovery openrecovery-twrp-2.6.3.0-m7wls.img
that resulted in this
sending 'recovery' (8608 KB)...
OKAY [ 1.120s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.880s
Or should i try http://forum.xda-developers.com/showthread.php?t=2314582
Click to expand...
Click to collapse
try hassoons all in one toolbox
I got twrp back by unlocking my phone again. Should i proceed with the 3.04.651.2 firmwre? beanstalk is now hanging on splash screen.
The phone isn't being recognized on my computer it seems, it shows as m7wls under device manager, when in twrp 2.6.3. When in bootloader it shows as One device, but neither is accessible.
Also tried flashing the s-off firmware, but got 'error cannot load firmware.zip'
Any more help would be appreciated, almost thinking of taking it back to sprint, i have a protection plan. But i would like to avoid that, im currently going to buy an otg-usb cable as well.
Hello everybody.
My brother bricked his xt1097 recently and, unable to fix it or find someone that could do it, he brought a new phone for him and gave me his old one.
The phone goes directly to fastboot mode, it says "Device is LOCKED" and "Software Status: Modified". I failed in finding an stock rom that I could successfully flash. Current flashed image fails to boot with "failed to validate system image". I cannot flash zip roms as the current recovery doesn't boot.
Bootloader reports version 61.00 (sha-130760b, 2016-08-24).
Cannot unlock also:
Code:
> fastboot oem get_unlock_data
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Could not get unlock data!
OKAY [ 0.016s]
finished. total time: 0.016s
I am with a very cheap phone right now (Nokia Lumia 525) I would get a really nicer phone if I resurect this Moto X.
Thanks :good:
Have you read this:
https://forum.xda-developers.com/moto-x-2014/general/guide-return-to-stock-official-status-t3274121
---------- Post added at 05:11 PM ---------- Previous post was at 05:03 PM ----------
HTML:
https://forum.xda-developers.com/moto-x-2014/general/warning-downgrade-bootloader-partition-t3105147
MAAZAHMEDSIDDIQEE said:
Have you read this:
https://forum.xda-developers.com/moto-x-2014/general/guide-return-to-stock-official-status-t3274121
---------- Post added at 05:11 PM ---------- Previous post was at 05:03 PM ----------
HTML:
https://forum.xda-developers.com/moto-x-2014/general/warning-downgrade-bootloader-partition-t3105147
Click to expand...
Click to collapse
Yes, I did read. I still could not flash anything. Always fails with "hab check failed" when flashing boot, system or recovery.
I am not trying to flash anything other than boot, system or recovery to avoid further bricking.
Tried all three firmwares starting with VICTARA_RETBR_XT1097 that are in firmware.center
Now I am downloading RETBR_XT1097_4.4.4_KXE21.187-30.3_cid12_CFC to try again
Thanks for your help
mrachid said:
Yes, I did read. I still could not flash anything. Always fails with "hab check failed" when flashing boot, system or recovery.
I am not trying to flash anything other than boot, system or recovery to avoid further bricking.
Tried all three firmwares starting with VICTARA_RETBR_XT1097 that are in firmware.center
Now I am downloading RETBR_XT1097_4.4.4_KXE21.187-30.3_cid12_CFC to try again
Thanks for your help
Click to expand...
Click to collapse
Try this:
https://forum.xda-developers.com/showthread.php?t=1487788
MAAZAHMEDSIDDIQEE said:
Try this:
https://forum.xda-developers.com/showthread.php?t=1487788
Click to expand...
Click to collapse
Did not get what to do, exactly. The solution doesn't apply for this phone, I think.
---
I tried one more RETBR firmware without success. I am afraid that the bootloader currently installed is expecting a ROM other than the original one for this phone, checking for a ROM of another region or a ROM that I would not find.
Also status code of lock is 0. The phone bricked overnight, which makes me think an OTA did it.
MAAZAHMEDSIDDIQEE said:
Try this:
https://forum.xda-developers.com/showthread.php?t=1487788
Click to expand...
Click to collapse
https://forum.xda-developers.com/droid-turbo/help/relocked-bootloader-bricked-t3306081
Hello everyone, I'm new in the Android world.
I have been trying to unlock my bootloader with the sticky guide, but it doesnt work for some reason.
In the cmd (after i got into the "Device locked" screen) it gives me an error and i dont know how to fix it.
I would like to see a full working 2k17 guide for how to unlock bootloader for a Huawei P7 running android 5.1.1 with Emui 3.1
Hope someone can help me.
What error do you get?
Does it appear right after entering fastboot mode?
RangerP7 said:
What error do you get?
Does it appear right after entering fastboot mode?
Click to expand...
Click to collapse
Im getting into fastboot without problem, but when i try to unlock it gives me the (Failed to write) error? Maybe its the guide that doesnt work
What guide do you use?
Did you install your driver (HiSuite)
---------- Post added at 02:00 PM ---------- Previous post was at 01:57 PM ----------
Before you are flashing try the command "fastboot devices". Is your devices listed?
RangerP7 said:
What guide do you use?
Did you install your driver (HiSuite)
---------- Post added at 02:00 PM ---------- Previous post was at 01:57 PM ----------
Before you are flashing try the command "fastboot devices". Is your devices listed?
Click to expand...
Click to collapse
I used this guide: https://forum.xda-developers.com/ascend-p7/general/rooted-p7-l10-609-t3003605
I got HiSuite installed and updated.
It is listed as "0123456789ABCDEF fastboot" ?
F:\Overførsler\ADB Flash Tools>fastboot flash boot BOOT_EMUI3.0_619_UNLOCKED.img
target reported max download size of 536870912 bytes
sending 'boot' (8038 KB)...
OKAY [ 0.309s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.309s
So you are trying to flash a KitKat boot image on a lollipop device?
But the guid works, I rooted my device the same way
CalloDK said:
I used this guide: https://forum.xda-developers.com/ascend-p7/general/rooted-p7-l10-609-t3003605
I got HiSuite installed and updated.
It is listed as "0123456789ABCDEF fastboot" ?
F:\Overførsler\ADB Flash Tools>fastboot flash boot BOOT_EMUI3.0_619_UNLOCKED.img
target reported max download size of 536870912 bytes
sending 'boot' (8038 KB)...
OKAY [ 0.309s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.309s
Click to expand...
Click to collapse
if you have emui 3.1 you can't flash a kernel for emui 3.0
a question: is your bootloader unlocked? (in fastmode under the green robot there is written in red letters phone unlocked)
EDIT: in your first post you write that the phone is locked...so you need an unlock code from huawei site in order to unlock bootloader, otherwise you will never be able to flash kernel or recovery
use this guide https://forum.xda-developers.com/ascend-p7/general/guide-root-huawei-p7-t3311424
and at point 8-9-10 use this https://forum.xda-developers.com/ascend-p7/orig-development/recovery-t3314665
usb2 said:
if you have emui 3.1 you can't flash a kernel for emui 3.0
a question: is your bootloader unlocked? (in fastmode under the green robot there is written in red letters phone unlocked)
EDIT: in your first post you write that the phone is locked...so you need an unlock code from huawei site in order to unlock bootloader, otherwise you will never be able to flash kernel or recovery
use this guide https://forum.xda-developers.com/ascend-p7/general/guide-root-huawei-p7-t3311424
and at point 8-9-10 use this https://forum.xda-developers.com/ascend-p7/orig-development/recovery-t3314665
Click to expand...
Click to collapse
I tried to install it on 2 computers, but i dont get any desktop shortcut?
What shortcut do you mean adb/fastboot?
RangerP7 said:
What shortcut do you mean adb/fastboot?
Click to expand...
Click to collapse
It says in the guide that it will create a shortcut on the desktop, otherwise i dont know how to continue
You don't need any shortcut
Just go to the path, you installed it via cmd
How did you get it work in your first post?
RangerP7 said:
You don't need any shortcut
Just go to the path, you installed it via cmd
How did you get it work in your first post?
Click to expand...
Click to collapse
I didnt set a path, it just got installed.
I used another cmd, where i was just going to open it and run it
CalloDK said:
I didnt set a path, it just got installed.
I used another cmd, where i was just going to open it and run it
Click to expand...
Click to collapse
There schoulkd be a folder calld "adb" at C:
So open cmd "cd C:/adb"
RangerP7 said:
There schoulkd be a folder calld "adb" at C:
So open cmd "cd C:/adb"
Click to expand...
Click to collapse
I got a folder called ADB Flash Tool? Can i use that?
Yes of course
RangerP7 said:
Yes of course
Click to expand...
Click to collapse
It worked and now im rooted, thanks. But I cant find the cyanogenmod which works with P7
Because there is no one for Android L.
Or look at the developer channel, there you will find another custom roms
I realize that our device have the source code on Asus website and the unlock tool haven't been released by Asus. That's maybe a chance for unlocking bootloader and play guessing that our device is just using similarly same method with nexus or other legacy bootloader locking mechanism. Thanks, and blame Asus for that! But, I could stop thinking and doing this and (BAM!) the bootloader unlocked and I'm able to boot patched boot.img with Magisk Manager app.
READ THIS FIRST!
Before you all do this, it's recommended to do factory reset before unlocking bootloader because our device is using force encryption by default. If you didn't reset your device, you will get locked from the start and cannot doing anything even you type password or pin correctly.
PLEASE READ CAREFULLY!
1. Reboot to Bootloader by pressing power + vol up
2. Type fastboot command below:
echo > key.txt
fastboot oem get_unlock_key key.txt
fastboot reboot-bootloader
Click to expand...
Click to collapse
3. Enjoy the freedom of Android experience with annoying verifiedboot caution on the start ( Blame Google for that) but it's not a big problem.
To relock bootloader type this in fastboot (Thanks to @shakalaca for telling that in this thread)
echo > key.txt
fastboot oem reset_unlock_key key.txt
fastboot erase config
fastboot flashing lock
fastboot reboot-bootloader
Click to expand...
Click to collapse
REMEMBER! DO WITH YOUR OWN RISK! I'M NOT RESPONSIBLE FOR WHAT HAPPENS TO YOUR DEVICE AND YOUR LIFE FOR DOING THIS! GOOD LUCK!
PS: I dont have any device to take a shot from my device because this Zenfone was my only device that I have.
To do list:
- Get rid of the caution at startup that reminds our bootloader state
NOTE: This method works only for version below 215. If you're updated to latest firmware. It won't work since Asus update the bootloader. And the bootloader just temporarily unlocked with this method. If device restarted, the bootloader get locked automatically
Не работает
Here's what happens:
C:\adb>fastboot oem get_unlock_key
...
(bootloader) @!
OKAY [ 0.004s]
finished. total time: 0.005s
C:\adb>fastboot oem unlock-go
...
FAILED (remote: unknown command)
finished. total time: 0.004s
aaaaaaziskurnia said:
i realize that our device have the source code on asus website and the unlock tool haven't been released by asus. That's maybe a chance for unlocking bootloader and play guessing that our device is just using similarly same method with nexus or other legacy bootloader locking mechanism. Thanks, and blame asus for that! But, i could stop thinking and doing this and (bam!) the bootloader unlocked and i'm able to boot patched boot.img with magisk manager app.
Read this first!
Before you all do this, it's recommended to do factory reset before unlocking bootloader because our device is using force encryption by default. If you didn't reset your device, you will get locked from the start and cannot doing anything even you type password or pin correctly.
Please read carefully!
1. Reboot to bootloader by pressing power + vol up
2. Type fastboot command "fastboot oem get_unlock_key" then press enter key
3. After that type "fastboot oem unlock-go"then hit enter again
4. Check the bootloader status by rebooting to bootloader back using command "fastboot reboot-bootloader"
5. Enjoy the freedom of android experience with annoying verifiedboot caution on the start ( blame google for that) but it's not a big problem.
Remember! Do with your own risk! I'm not responsible for what happens to your device and your life for doing this! Good luck!
Ps: I dont have any device to take a shot from my device because this zenfone was my only device that i have.
To do list:
- find a hack to relock again the bootloader
- get rid of the caution at startup that reminds our bootloader state
Click to expand...
Click to collapse
you have 2/16 or 3/32 ???
Johann Richter said:
you have 2/16 or 3/32 ???
Click to expand...
Click to collapse
Actually not the size of the rom and ram. But the SOC, I have the msm8937. Check yours pls
aaaaaaziskurnia said:
Actually not the size of the rom and ram. But the SOC, I have the msm8937. Check yours pls
Click to expand...
Click to collapse
I have 8917, no options with this?
Johann Richter said:
I have 8917, no options with this?
Click to expand...
Click to collapse
Try this methods. Because asus share same project named ZC554KL in the source code I've inspected, It's worth to try.
aaaaaaziskurnia said:
Try this methods. Because asus share same project named ZC554KL in the source code I've inspected, It's worth to try.
Click to expand...
Click to collapse
After much suffering, 15 times to unlock the bootloader. Thank you!!!
Johann Richter said:
After much suffering, 15 times to unlock the bootloader. Thank you!!!
Click to expand...
Click to collapse
I've suffering same thing as you in the first but it's unlocked. Good luck and enjoy development
Phone should be unlocked once you've done "fastboot oem get_unlock_key" , you can then verify after "fastboot reboot-bootloader" with on-screen-message.
To lock the phone again:
Code:
echo > key.txt
fastboot oem reset_unlock_key key.txt
fastboot erase config
fastboot flashing lock
fastboot reboot-bootloader
It works on my TW sku ..
shakalaca said:
Phone should be unlocked once you've done "fastboot oem get_unlock_key" , you can then verify after "fastboot reboot-bootloader" with on-screen-message.
To lock the phone again:
It works on my TW sku ..
Click to expand...
Click to collapse
Thanks shalaca, I'll include it to the first Page :good::laugh:
shakalaca said:
Phone should be unlocked once you've done "fastboot oem get_unlock_key" , you can then verify after "fastboot reboot-bootloader" with on-screen-message.
To lock the phone again:
Code:
echo > key.txt
fastboot oem reset_unlock_key key.txt
fastboot erase config
fastboot flashing lock
fastboot reboot-bootloader
It works on my TW sku ..
Click to expand...
Click to collapse
thanks a lot, very useful information
---------- Post added at 09:52 AM ---------- Previous post was at 09:49 AM ----------
On our device there is TWRP?
Johann Richter said:
Phone should be unlocked once you've done "fastboot oem get_unlock_key" , you can then verify after "fastboot reboot-bootloader" with on-screen-message.
To lock the phone again:
thanks a lot, very useful information
---------- Post added at 09:52 AM ---------- Previous post was at 09:49 AM ----------
On our device there is TWRP?
Click to expand...
Click to collapse
Just wait for TWRP. I've got built TWRP but still messed up. Stil investigating.
tks for your guide
can you root with supersu?? or can you send a custom recovery to flash zip file?
Mr Foot said:
can you root with supersu?? or can you send a custom recovery to flash zip file?
Click to expand...
Click to collapse
I suggest using Magisk. Since the stock rom protected /system by selinux. If you doing any modifications in /system , it will result hangs or unbootable device and you should clean flash again.
If someone is interested in building TWRP here's the source: https://github.com/shakalaca/android_device_asus_X00I
I've already built one https://www.androidfilehost.com/?fid=673791459329051335
And currently I don't have the phone on my hand so feel tree to fork/build/test/fix/release TWRP ..
shakalaca said:
If someone is interested in building TWRP here's the source: https://github.com/shakalaca/android_device_asus_X00I
I've already built one https://www.androidfilehost.com/?fid=673791459329051335
And currently I don't have the phone on my hand so feel tree to fork/build/test/fix/release TWRP ..
Click to expand...
Click to collapse
so is he a worker?
Johann Richter said:
so is he a worker?
Click to expand...
Click to collapse
who ? me ?
shakalaca said:
who ? me ?
Click to expand...
Click to collapse
Thanks, it works
shakalaca said:
If someone is interested in building TWRP here's the source: https://github.com/shakalaca/android_device_asus_X00I
I've already built one https://www.androidfilehost.com/?fid=673791459329051335
And currently I don't have the phone on my hand so feel tree to fork/build/test/fix/release TWRP ..
Click to expand...
Click to collapse
I'm already have a device tree written two weeks ago.
https://github.cm/aaaaaaziskurnia/twrp_device_asus_X00ID
But messed up many times so I freshly uploads all the device tree.
I'm still new but I can sure that I'm fast learner. Should we collab?
shakalaca said:
who ? me ?
Click to expand...
Click to collapse
Good day, which firmware do you use?
How to root moto x4 android 9?I failed with magisk 18.0
I've gotten root with Magisk on most versions. My general steps:
Download TWRP .img (not the zip unless you want to flash it as the recovery)
Download the magisk .zip
Place the magisk.zip on the phone (sd card or internal)
Enter the following commands in the console window:
adb reboot bootloader
fastboot boot C:\Path\To\twrp.img
Wait for TWRP to load, then flash the magisk.zip file (and twrp.zip if you want to keep it as the recovery. I'm not sure what order, probably magisk THEN twrp)
Reboot. It should prompt you to install magisk manager.
tjololo12 said:
I've gotten root with Magisk on most versions. My general steps:
Download TWRP .img (not the zip unless you want to flash it as the recovery)
Download the magisk .zip
Place the magisk.zip on the phone (sd card or internal)
Enter the following commands in the console window:
adb reboot bootloader
fastboot boot C:\Path\To\twrp.img
Wait for TWRP to load, then flash the magisk.zip file (and twrp.zip if you want to keep it as the recovery. I'm not sure what order, probably magisk THEN twrp)
Reboot. It should prompt you to install magisk manager.
Click to expand...
Click to collapse
I tried unlocking my moto x4 (indian variant). the error I got seem to be new - when I hit "fastboot oem get_unlock_data", instead of 4 strings below, it showed only digits with 1 strings. how come it showed up like this ?
any help anyone ?
SiddharthHarishkumar said:
I tried unlocking my moto x4 (indian variant). the error I got seem to be new - when I hit "fastboot oem get_unlock_data", instead of 4 strings below, it showed only digits with 1 strings. how come it showed up like this ?
any help anyone ?
Click to expand...
Click to collapse
Did you remember to turn on" OEM unlocking" from "developer options"?
When I did a normal unlock, no website needed, for a different device, this was needed.
dougo007 said:
Did you remember to turn on" OEM unlocking" from "developer options"?
When I did a normal unlock, no website needed, for a different device, this was needed.
Click to expand...
Click to collapse
Yes the "oem unlocking" was turned on.
By using powershell, it showed up "Bootloader : <number>" - just only one line instead of 5 lines of number.
And by using CMD prompt : it said "failed : unknown command" - but the commands I followed were correct.
---------- Post added at 02:51 PM ---------- Previous post was at 02:50 PM ----------
SiddharthHarishkumar said:
Yes the "oem unlocking" was turned on.
By using powershell, it showed up "Bootloader : <number>" - just only one line instead of 5 lines of number.
And by using CMD prompt : it said "failed : unknown command" - but the commands I followed were correct.
Click to expand...
Click to collapse
This showed up :
this ---> "E:\Motorola\ADB>fastboot oem get_unlock_data
(bootloader) slot-countta: not found
(bootloader) slot-suffi: not found
...
FAILED (remote: unknown command)
finished. total time: 0.002s"
SiddharthHarishkumar said:
Yes the "oem unlocking" was turned on.
By using powershell, it showed up "Bootloader : <number>" - just only one line instead of 5 lines of number.
And by using CMD prompt : it said "failed : unknown command" - but the commands I followed were correct.
---------- Post added at 02:51 PM ---------- Previous post was at 02:50 PM ----------
This showed up :
this ---> "E:\Motorola\ADB>fastboot oem get_unlock_data
(bootloader) slot-countta: not found
(bootloader) slot-suffi: not found
...
FAILED (remote: unknown command)
finished. total time: 0.002s"
Click to expand...
Click to collapse
you find a fix? getting the same error lol
Warranty
Does unlocking bootloader void the warranty or is there any other way to ensure the warranty is retained
vaidhy2007 said:
Does unlocking bootloader void the warranty or is there any other way to ensure the warranty is retained
Click to expand...
Click to collapse
Yes according to moto TOS
drago10029 said:
Yes according to moto TOS
Click to expand...
Click to collapse
Is there any way to bypass this?
vaidhy2007 said:
Is there any way to bypass this?
Click to expand...
Click to collapse
Short answer: No.
Besides unlocking bootloader and rooting the device via recovery, no other root method had been found to work on the X4. Getting the unlock code from the Moto site will void your warranty as they update their records at that time. This is the only way to unlock the bootloader. Even if you could unlock it by other means, a flag is permanently flipped on the device that will show that the bootloader has been unlocked. There is no way to undo that on-device flag at this time.
jhedfors said:
Short answer: No.
.
Click to expand...
Click to collapse
Thanks for the prompt response. Do you have any links for the official firmware of Android 8.1, 9.0 for retin software update channel (XT1900-2, India). I am trying to use VoLTE, unable to use in 9.0 (firmware from lolinet).
vaidhy2007 said:
Thanks for the prompt response. Do you have any links for the official firmware of Android 8.1, 9.0 for retin software update channel (XT1900-2, India). I am trying to use VoLTE, unable to use in 9.0 (firmware from lolinet).
Click to expand...
Click to collapse
Not sure as I am using the XT1900-1 (FI). Hopefully someone familiar with your model will respond.
vaidhy2007 said:
Thanks for the prompt response. Do you have any links for the official firmware of Android 8.1, 9.0 for retin software update channel (XT1900-2, India). I am trying to use VoLTE, unable to use in 9.0 (firmware from lolinet).
Click to expand...
Click to collapse
I only know where to find 9.0 retin: https://mirrors.lolinet.com/firmware/moto/payton/official/RETIN/
tjololo12 said:
I only know where to find 9.0 retin: https://mirrors.lolinet.com/firmware/moto/payton/official/RETIN/
Click to expand...
Click to collapse
I already have this. Want to go back to oreo to check something.
Is there any issue if i flash the retail version on the retin version?
Rooting Moto X4
while unlocking bootloader with command
fastboot oem get_unlock_data
only one string comes up and sometimes no string at all.
I have switched on OEM Unlocking.
all drivers are installed.
I think everything is proper
then why I'm facing this problem