So recently i unlocked my bootloader so i could root my XT1092. But without knowing, i booted a file for an older android version while i was on 6.0. So then i was stuck at the end of the boot. Somebody told me to flash original stock files from motorola site. Did that but now i'm stuck at the 'bootloader unlocked' warning, and when i trie to charge it stays at battery low and it doesn't charge. Also when i trie to lock the bootloader again it says:
C:\android-sdk\platform-tools>fastboot oem lock
...
(bootloader) FAIL: Please run fastboot oem lock begin first!
(bootloader) sst lock failure!
OKAY [ 0.057s]
finished. total time: 0.063s
What should i do? PLEASE SOMEBODY HELP!!!
Sorry can't help..... But will you pls tell me what wrong step did you go through so that I can avoid them ( I need to unlock my X2)... Thanks!
had no problems with unlocking the bootloader. I flashed a twrp on the device and when i tried to get into recovery it said: no command
So i used another method that said i needed to boot a file but i forgot to read the comments and it was only for the moto x 2014 that are running on KITKAT. I was running on 6.0 and i saw that right after i booted the file. So always read the comments! That's the advice i can give. If you find a proper method please tell me too pls so i know what to do if i find a solution.
Ok, i fixed it i had some problems flashing the system img. but its solved.
OK i got the phone back working but it doesn't recognize my sim-card anymore and my internet speed is slow af. I got 101 kb/s for downloading and 22kb/s uploading speed. Sometimes i see a toast that says that it was unable to download the appendix?! What do i have to do to fix it?
benjg_ said:
OK i got the phone back working but it doesn't recognize my sim-card anymore and my internet speed is slow af. I got 101 kb/s for downloading and 22kb/s uploading speed. Sometimes i see a toast that says that it was unable to download the appendix?! What do i have to do to fix it?
Click to expand...
Click to collapse
You might have flashed an image for other variant. Now, flash the modems for your variant, you can find them in the threads! :fingers-crossed:
Could be true. Maybe it would work again if i install cyanogenmod 13?
Related
New to rooting and playing around with the flashboot.
I have a pure edition Moto X lollipop. I decided to unlock (successful) and root (unsuccessful). Also, not sure if I enabled USB debugging before I started messing with fastboot. Now that I'm in loop, I cannot enable it.
My phone is now in constant loop, more specifically stuck on the blue world screen. It will not go any further. Here are the different solutions I've tried that have come up short:
- Fastboot menu cannot access "Recovery mode" it simply says "boot up failed."
- Tried flashing "openrecovery-twrp-2.8.3.0-ghost.img" file but I believe something must be incompatible and have now screwed up my system.
I just simply want to put it back to stock. Any help would be greatly appreciated. Please tell me I didn't stupidly brick my phone.
I have fixed this issue. This thread can be deleted/closed. Thank you for the search button!
how you solved this problem???
DocDroid said:
I have fixed this issue. This thread can be deleted/closed. Thank you for the search button!
Click to expand...
Click to collapse
HOW YOU recovered from problem??? i am having same one..
Neelesh16 said:
HOW YOU recovered from problem??? i am having same one..
Click to expand...
Click to collapse
Im having the same issue, Havent found a soluttion yet. gotta keep looking
I rest my Moto X Pure to Stock via CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml_SHAWN5162
- I believe Im locked out my phone now
Device is LOCKED Status Code: 0
Software Status: Modified
Any Fastboot(or mfastboot) code I try does this:
(bootloader) Permission denied
FAILED (Remote Failure)
So far its not looking good. Anyone have any ideas?
Hi guys! Its my first time posting a problem, i usually manage to fix it by reading and looking for info, but this time im really stuck
My cousins phone turned off one day and it never booted right again, got stuck in Moto logo... He tried to fix it (Not sure what he did, but my guess is that he somehow deleted a partition or someting), and now, it wont flash anything, just keep getting this error in every line:
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
Click to expand...
Click to collapse
I was able to unlock the bootloader (Device is UNLOCKED. Status: 3) but still cant flash anything, i tried almost every single post i could find in the web but no luck at all...
It boot directly into fastboot mode and when i press the power up button the logo image was replaced by this http://imgur.com/JH4CAq1
Bootloader version is 48.86 and when connected to the PC it is recognized as "Fastboot Titan S"
If anyone can help me i'll be really greatful!
Thanks for reading and sorry for my pooooor englando :laugh:
Hello Guys,
My R1 HD Amazon prime version got 8.4 update, since them WiFi and Bluetooth connectivity is broken/unstable. Their 8.3 has also the same issue.BLU support is also not that great.
I want to roll back the my phone to 7.4, with 8.4 on I cannot root or unlock the boot loader with tools and procedures posted earlier in the forum.
Can any one help me?
Appreciate your help.
Thanks
Gags
gags_bd said:
Hello Guys,
My R1 HD Amazon prime version got 8.4 update, since them WiFi and Bluetooth connectivity is broken/unstable. Their 8.3 has also the same issue.BLU support is also not that great.
I want to roll back the my phone to 7.4, with 8.4 on I cannot root or unlock the boot loader with tools and procedures posted earlier in the forum.
Can any one help me?
Appreciate your help.
Thanks
Gags
Click to expand...
Click to collapse
I have an Idea that I wanted to try but I cannot, because I cannot re-lock my boot loader.
It gives me lock failed error..
So the idea is as follows if you are willing and able to try it out.
I believe with a locked bootloader you are supposed to be able to boot "official" images.
So if you "fastboot boot v6.1-boot.img" android will not exactly boot into visual interface but will give adb access. And from there will be kernel before they patched dirty cow. So maybe the unlock tool will work.
UPDATE
I did complete my test and dirty-cow did work on 8.4 when I "fastboot boot 6.1-boot.img" even though the screen stayed on the frozen boot animation the whole time.
That leaves the last part of the idea needing testing , and that is the fact that fastboot supposed to allow official images to boot. And if the copy of boot.img is accepted as official.
mrmazak said:
I have an Idea that I wanted to try but I cannot, because I cannot re-lock my boot loader.
It gives me lock failed error..
So the idea is as follows if you are willing and able to try it out.
I believe with a locked bootloader you are supposed to be able to boot "official" images.
So if you "fastboot boot v6.1-boot.img" android will not exactly boot into visual interface but will give adb access. And from there will be kernel before they patched dirty cow. So maybe the unlock tool will work.
UPDATE
I did complete my test and dirty-cow did work on 8.4 when I "fastboot boot 6.1-boot.img" even though the screen stayed on the frozen boot animation the whole time.
That leaves the last part of the idea needing testing , and that is the fact that fastboot supposed to allow official images to boot. And if the copy of boot.img is accepted as official.
Click to expand...
Click to collapse
Thanks mrmazak, for your response. I am relatively new to fast boot and adb. I am happy to test if you can post the steps to follow. I have adb and fastboot utilities on my machine and can communicate to my R1 HD from my machine.
Thanks
Gags
gags_bd said:
Thanks mrmazak, for your response. I am relatively new to fast boot and adb. I am happy to test if you can post the steps to follow. I have adb and fastboot utilities on my machine and can communicate to my R1 HD from my machine.
Thanks
Gags
Click to expand...
Click to collapse
the test i propose is only to see if the image of 6.1 boot i have willl boot on locked bootloader.
If test works out good, then some type of update to the unlock tool will follow
1. open terminal
2. type "adb reboot bootloader"
3. type "fastboot boot v6.1_stock_boot.img"
I have made batch file that does those steps.
1. unzip files to location of your choice
2. connect usb cable to phone, make sure adb is enabled
3, click the "test_boot-6.1.bat"
I get the below error : -(
C:\Gags\Other\R1HD\R1-HD-Tool-V11\Tool-V11>fastboot boot v6.1-stock-boot.img
downloading 'boot.img'...
OKAY [ 1.589s]
booting...
FAILED (remote: oem unlock is false)
finished. total time: 1.589s
Note: I do not have "OEM Unlock" option in developers options.
-Gags
gags_bd said:
I get the below error : -(
C:\Gags\Other\R1HD\R1-HD-Tool-V11\Tool-V11>fastboot boot v6.1-stock-boot.img
downloading 'boot.img'...
OKAY [ 1.589s]
booting...
FAILED (remote: oem unlock is false)
finished. total time: 1.589s
Note: I do not have "OEM Unlock" option in developers options.
-Gags
Click to expand...
Click to collapse
was afraid of that. the image I have is untouched, and original, but because it was read back from device it is missing the signature.
or because the signature is below v8.4 it is rejected.
Wonder if there is a way to apply the signature file from the 8.4 update to that older boot.img.
so for now there is still no way to roll you back to older version rom.
Is it even possible to ... make it a bare metal and install everything from scratch? Similar to how we would install OS on a PC.
The situation I am in w.r.t BLU R1 HD, is something like BIOS is locked and hence I cannot boot PC from other media , in PC world?
gags_bd said:
Is it even possible to ... make it a bare metal and install everything from scratch? Similar to how we would install OS on a PC.
The situation I am in w.r.t BLU R1 HD, is something like BIOS is locked and hence I cannot boot PC from other media , in PC world?
Click to expand...
Click to collapse
The system app "settings" is what is missing the OEM unlock switch. A while ago @vampirefo patched the settings app for v17. The patched app returns the toggle. That settings app still works in v8.4 to give back the toggle. Problem is , as with most of rooting methods, stock recovery will not install unsigned packages.
It's the standard "catch 22" of rooting (if I could only.......)
Same issue as OP
I have the same issue, does anyone have a solution? I am stuck on 8.4 with slow wifi, I want to revert the update
brandex07 said:
I have the same issue, does anyone have a solution? I am stuck on 8.4 with slow wifi, I want to revert the update
Click to expand...
Click to collapse
Factory reset seems to have worked for me , I would give couple of more days to conclude.
gags_bd said:
Factory reset seems to have worked for me , I would give couple of more days to conclude.
Click to expand...
Click to collapse
Since the day I did factory reset it is working for me.
Hi everybody, I have a little question regarding my P10.
The model of my phone is VTR-L09C521B101
Is there a way to flash this phone with VTR-L09C432 version?
or i need to flash with same model version (VTR-L09C521)?
Thnks
Yes, it is possible to 'rebrand'. The procedure is explained in the Mate 9 forum. It is not so easy and involves unlocking the bootloader.
Updating can be done with the Firmware Finder (Playstore).
M1chiel said:
Yes, it is possible to 'rebrand'. The procedure is explained in the Mate 9 forum. It is not so easy and involves unlocking the bootloader.
Updating can be done with the Firmware Finder (Playstore).
Click to expand...
Click to collapse
thanks for the answer!!
regarding bootloader, the phone shows this:
PHONE RELOCKED
FRP LOCK
ADB shows me that the phone is unlocked, the problem is when I try to send something to phone it shows:
Error Remote command not allowed.
any ideas?
thanks!
I've tried to reword the mate 9 instructions for the p10 here: https://forum.xda-developers.com/p10/help/rebrand-firmware-finder-t3685951
As for adb, what command are you trying? Do you see your phone if you type ADB Devices?
Quintman said:
I've tried to reword the mate 9 instructions for the p10 here: https://forum.xda-developers.com/p10/help/rebrand-firmware-finder-t3685951
As for adb, what command are you trying? Do you see your phone if you type ADB Devices?
Click to expand...
Click to collapse
Quintman, no the phone is not listed with adb devices command. I can only enter with fastboot.
Let me paste the commands that I have tried:
C:\adb>fastboot devices
WPG7N17320000978 fastboot
C:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.001s]
finished. total time: 0.001s
C:\adb>fastbot oem lock <my_unlock_code>
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\adb>fastboot oem unlock <my_unlock_code>
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\adb>fastboot oem relock <my_unlock_code>
...
FAILED (remote: stat not match)
finished. total time: 0.016s
The Strange thing is that in the phone shows PHONE RELOCKED, not unlocked as ADB shows.
Since I uploaded boot img of another version (C432) full OTA, could this be the problem? in this case what can I do?
thanks for your help!!
Could this be happening because of FRP Lock?, none of the software I have tried (DC-phoenix, chimera and Unlocker v2) worked. Im this close to throw this f*ckin phone to trash u.u
fmm1977 said:
Could this be happening because of FRP Lock?, none of the software I have tried (DC-phoenix, chimera and Unlocker v2) worked. Im this close to throw this f*ckin phone to trash u.u
Click to expand...
Click to collapse
edit: just found this in another thread "FRP Lock occurs when the phone has a firmware mismatch and or oem unlocking is not on in developer options"
Hmm, i've just checked my phone and in fastboot it says PHONE Locked, and FRP Unlock. I think that may be your issue. What exactly did you do to flash your phone with the other version? put an UPDATE.APP into a \Dload folder and 3 button update?
is your phone booting (guessing not). my guess is that you need to get a hold of your stock firmware file an flash that first.
Quintman said:
edit: just found this in another thread "FRP Lock occurs when the phone has a firmware mismatch and or oem unlocking is not on in developer options"
Hmm, i've just checked my phone and in fastboot it says PHONE Locked, and FRP Unlock. I think that may be your issue. What exactly did you do to flash your phone with the other version? put an UPDATE.APP into a \Dload folder and 3 button update?
is your phone booting (guessing not). my guess is that you need to get a hold of your stock firmware file an flash that first.
Click to expand...
Click to collapse
Ok, this is what I've done step by step:
1.- With the unlock code provided by huawei, I have unlocked my phone (my version is VTR-L09C521B101 stock)
2.- Once unlocked, I have downloaded another ROM version (VTR-L29C605B151) in the web page says this rom is for latin america), so with the Huawei Update Extractor, I have extracted all files.
3.- Via ADB/FASTBOOT, I sent the files to my phone, boot.img first and then the others. (big big mistake!)
4.- Rebooted the phone, and then keeps restarting at huawei logo.
5.- Seeing that it did´t worked, what I did was to lock the phone again thinking to send it to Huawei (at this point the phone shows as "unlocked" via fastboot commands, however when I start the phone in fastboot mode, in the screen shows "PHONE RELOCKED, FRP LOCK"
6.- Sent to huawei's service, they said that they cannot fix my phone because it was tampered/rooted.
7.- Right now all I need to fix my phone is to LOCK/UNLOCK again in order to rebrand it to L29 version, since the original stock rom dont exist (not as FULL OTA).
And that´s what I did so far my friend.
Questions:
1.- Is there a way to connect to my phone and change the oem info file? or something?
2.- Do I need to wait the stock rom to be released in order to reflash via Dload method?
3.- What if the stock ROM version of my phone is never released?
thank you for your answer my friend!!
Hmm ok. I am just not sure on your step 3, I've never heard of a method that involves a boot.img... what I would suggest, is to try and download the stock firmware files (need the larger full ota files), extract the update.app file and put on sd card in \dload.
Then hold down both volume up and down and power (3 button method)
It will try and flash the stock image back to the phone.
I just tried the Dload method and nothing happened (always stuck in 5%), now im going to try to use a smaller memory card (mine is 64 Gb). lood
U have disconnected the USB cable when u try 3 button update
berka38 said:
U have disconnected the USB cable when u try 3 button update
Click to expand...
Click to collapse
Yes sr!!
ok... i was just browsing the web on my phone then i sat it down for a bit... then, when i came back, it was in bootloader... i tried to start it and it said "Boot Failed: Failed to initialize partition table" so, what can i do to fix it... it is a motorola g6, XT1925-6 and i tried flashing it and it still didnt work... dont have an unlocked bootloader because i cant unlock it because the device is bricked. can someone please help?
DerpyPlayz71 said:
ok... i was just browsing the web on my phone then i sat it down for a bit... then, when i came back, it was in bootloader... i tried to start it and it said "Boot Failed: Failed to initialize partition table" so, what can i do to fix it... it is a motorola g6, XT1925-6 and i tried flashing it and it still didnt work... dont have an unlocked bootloader because i cant unlock it because the device is bricked. can someone please help?
Click to expand...
Click to collapse
If you download the latest stock firmware I believe it ends with -92 you should be able to reflash the stock firmware. I would try just flashing the GPT.bin file per the restore stock instructions, and then attempt to boot. They're official files so they should flash regardless of bootloader status