Related
So a while ago I rooted my phone but messed it up because I uninstalled a few too many system apps. I just dealt with it for a few months since I could still make calls (but not much else). I finally bit the bullet to look into flashing the stock rom again, but to do so it looked like I had to install a custom recovery, but to do that, unlock the bootloader. So I first unlocked the bootloader using motopocalypse (batch file didn't work but apk did), and got the expected BOOTLOADER UNLOCKED message at bootup, with fastboot saying unlocked, code 3. I then tried flashing CWM recovery via Rom Manager, and it seemed successful, but I was unable to boot to it either from the UI of ROM manager or from holding the buttons during bootup, it would just hang for a few more minutes than normal at the BOOTLOADER UNLOCKED screen, then boot up like normal. So I kept reading, found RSDlite, and was able to flash the stock rom, which I downloaded from the internet and the phone boots up fine, but now fastboot says locked, status code 2, and motopocalypse does not unlock it again (either the batch file or the apk), but I still get the BOOTLOADER UNLOCKED message at bootup. So I'm not sure if my bootloader is unlocked or not and if I can proceed with installing CWM recovery again, so i can make a full backup in case I mess something up again.
So how do I reunlock the bootloader, or verify if it's locked or not?
First, CWM and TWRP aren't official for this phone, so you can't use their apps to flash. You'll need to use fastboot, Flashify, or Rashr. Second, you're still unlocked, we've seen this error come from bad flashes. What is the complete text on your FB screen. You should be able to clear this by re-flashing with RSD. What firmware did you attempt to flash?
Sent from my HTC6525LVW using Tapatalk
RikRong said:
First, CWM and TWRP aren't official for this phone, so you can't use their apps to flash. You'll need to use fastboot, Flashify, or Rashr. Second, you're still unlocked, we've seen this error come from bad flashes. What is the complete text on your FB screen. You should be able to clear this by re-flashing with RSD. What firmware did you attempt to flash?
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
FB screen:
Code:
AP Fastboot Flash Mode (S)
10.9B(*) (sha-61146a2, 2014-05-02 00:54:39)
eMMC Info: Size 8GB
Device is LOCKED. Status code: 2
Battery OK
Transfer Mode:
USB connected
Fastboot reason: Reboot to bootloader
usb connected
I've tried reflashing with RSD previously but no change. I could try it once more if you want.
Not entirely sure what you're asking for with the firmware version, but the image I used was for android 4.4.2, version 183.46.10.XT907Verizon.en.US.
modemman11 said:
Device is LOCKED. Status code: 2
Click to expand...
Click to collapse
I think your boot loader is still LOCKED. Mine is showing UNLOCKED. Status code: 3. You cannot flash a custom recovery on a phone with a locked BL. You need to motocalypse again!
To trace the issue from the ground up, if you're just trying to reinstall stock ROM, you should be relying on RSD instead of trying to mess with custom recoveries and BL unlocking. Just flash .10 (not .15) via RSD, root via Towelroot and you can start fresh.
Unlocking your BL is still highly recommended, though, 'cuz it's now or never.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
Code 3 as well.
Sent from my XT907 using XDA Free mobile app
rahimali said:
I think your boot loader is still LOCKED. Mine is showing UNLOCKED. Status code: 3. You cannot flash a custom recovery on a phone with a locked BL. You need to motocalypse again!
Click to expand...
Click to collapse
Yes, that's why I'm asking. So I've got one vote for unlocked, one for locked. As I said though, motopocalypse isn't working a 2nd time.
AndyYan said:
To trace the issue from the ground up, if you're just trying to reinstall stock ROM, you should be relying on RSD instead of trying to mess with custom recoveries and BL unlocking. Just flash .10 (not .15) via RSD, root via Towelroot and you can start fresh.
Unlocking your BL is still highly recommended, though, 'cuz it's now or never.
Click to expand...
Click to collapse
I would like to flash custom ROMs later down the road, but for now I just want to get the stock stuff going.
On a side note, the version of the image I downloaded was 183.x.x, but my mother, who has the same phone, purchased at the same time, and has never rooted it or anything, has version 182.something, and that is also the version I had before I started messing with the bootloader/recovery stuff. The two versions were released at the same time, but I don't know what determines which version you got if you just did OTA updates, or if it even matters. Speaking of OTA updates, the version I downloaded is prompting me to do an OTA update now to another 183.x.x version. I wonder if I'd be able to grab the 182.x.x ROM from my mom's phone without rooting it via fastboot or something.
The 182/183 does not matter regarding root/boot loader unlock its the .10/.15 that matters do not take the .15 without unlocking your boot loader....
We cannot teach people anything; we can only help them discover it within themselves.
So no other thoughts? What would happen if I flashed a custom rom/recovery with a locked bootloader? I tried flashing the ROM again and fb still says locked, code 2, and motopocalypse still doesn't do anything like it did the first time.
modemman11 said:
What would happen if I flashed a custom rom/recovery with a locked bootloader?
Click to expand...
Click to collapse
It won't let you flash a custom recovery. This is the difference between locked and unlocked.
modemman11 said:
So how do I reunlock the bootloader, or verify if it's locked or not?
Click to expand...
Click to collapse
If your bootloader is relocked for some reasons, try unlocking it again with
Code:
fastboot oem unlock
lem22 said:
It won't let you flash a custom recovery. This is the difference between locked and unlocked.
Click to expand...
Click to collapse
I guess what I'm asking is, will it let me flash it but then the phone won't work or will give an error on boot, or perhaps brick my phone? Or will it just not flash in the first place? Because if it's the latter, then I can just try to flash a custom ROM/recovery and if it works then I know it's unlocked.
If your bootloader is relocked for some reasons, try unlocking it again with
Code:
fastboot oem unlock
Click to expand...
Click to collapse
Code:
D:\adt-bundle-windows-x86-20140702\sdk\platform-tools>fastboot oem unlock
...
(bootloader) fastboot oem unlock [ unlock code ]
OKAY [ 0.031s]
finished. total time: 0.031s
Still locked code 2 though. Looks like it wants an unlock code from Motorola's website, I tried following the steps to get the code but it says I'm not eligible for bootloader unlock. So unless there's another way to get the unlock code...
modemman11 said:
I guess what I'm asking is, will it let me flash it but then the phone won't work or will give an error on boot, or perhaps brick my phone? Or will it just not flash in the first place? Because if it's the latter, then I can just try to flash a custom ROM/recovery and if it works then I know it's unlocked.
Click to expand...
Click to collapse
A "Code 0" locked device would refuse flashing an unofficial or older recovery. I have no idea about Code 2 though.
From what I was able to locate status code 2 indicates that the bootloader has been unlocked and relocked like by doing the whole "fastboot oem unlock unlock code" then the "fastboot oem lock" ... I'll look more into it but from what little I read it looks like it can not be unlocked again with out the Motorola unlock code...
We cannot teach people anything; we can only help them discover it within themselves.
ezknives said:
From what I was able to locate status code 2 indicates that the bootloader has been unlocked and relocked like by doing the whole "fastboot oem unlock unlock code" then the "fastboot oem lock" ... I'll look more into it but from what little I read it looks like it can not be unlocked again with out the Motorola unlock code...
We cannot teach people anything; we can only help them discover it within themselves.
Click to expand...
Click to collapse
Same here, I can see what it means but cannot find any way to get back to code 3 other than using the unlock code from Motorola, which I am unable to obtain because it says I am not eligible. Surprising that someone hasn't cracked the unlock code yet or made a keygen, people are so eager to do it with pirated computer software before the software is even released.
I've read of someone getting locked status code 2 b4 from flashing an older gpt with rsd (if I remember correctly) I think all that was required to fix it and get unlocked again was to flash the latest gpt. Very important..... Are you sure when you were unlocked you didn't ota update to .15? Because flashing .10 gpt while on .15 may be what caused your false relock
Nope, no OTA update to .15. The ZIP I have of the rom does include the gpt.bin file with the same timestamp as all the other files. I suppose I could try reflashing the whole rom once again later...
Hmm strange, I went to find the old thread I read about the gpt relock issue but it's not exactly the same as your situation.
http://forum.xda-developers.com/showthread.php?p=51436123
Until now I didn't think relock was possible due to the way unlocking works. It's a physical change, a qfuse was blown when the motopocalypse apk was run the first time. It can't be unblown lol. Wish I knew what went wrong here.
hi all motorola users
1st you must have Unlocked your motorola XT925
see this thread : http://forum.xda-developers.com/showthread.php?t=2797116
2nd you need custom recovery for example CWM for kitkat bootloader
you can download the stable kitkat cwm for XT925
from there : http://www.mediafire.com/download/uxyrv1b17ctu5rv/CWM6049-RAZR-HD_M-KITKAT.img
3rd you need root package
download from there : http://www.mediafire.com/download/v8sptt6oy9m1xd6/UPDATE-SuperSU-v2.16.zip
let's start :laugh:
put everything in adb folder and connected you XT925
adb wait-for-device
adb reboot bootloader
fastboot flash recovery CWM6049-RAZR-HD_M-KITKAT.img
----------
disconnected you phone power off and go to bootloader again and then go CWM recovery and install the UPDATE-SuperSU-v2.16.zip
you can use the sideload options
good luck
Has anyone tried/verified this yet or should I be the first?
matt121188 said:
Has anyone tried/verified this yet or should I be the first?
Click to expand...
Click to collapse
back when i flashed kk, it worked to get root. no other root exploits have been found unfortunately.. this is the normal and easiest way to get root just need an unlocked bootloader and flash chainfire's super su through a custom recovery.
A little help please
s27moto said:
hi all motorola users
1st you must have Unlocked your motorola XT925
see this thread : http://forum.xda-developers.com/showthread.php?t=2797116
2nd you need custom recovery for example CWM for kitkat bootloader
you can download the stable kitkat cwm for XT925
from there : http://www.mediafire.com/download/uxyrv1b17ctu5rv/CWM6049-RAZR-HD_M-KITKAT.img
3rd you need root package
download from there : http://www.mediafire.com/download/v8sptt6oy9m1xd6/UPDATE-SuperSU-v2.16.zip
let's start :laugh:
put everything in adb folder and connected you XT925
adb wait-for-device
adb reboot bootloader
fastboot flash recovery CWM6049-RAZR-HD_M-KITKAT.img
----------
disconnected you phone power off and go to bootloader again and then go CWM recovery and install the UPDATE-SuperSU-v2.16.zip
you can use the sideload options
good luck
Click to expand...
Click to collapse
I apologize for my stupidity.
But, is there any chance for more advance step by step tutorial on this topic.
I have a filing that i'm going to miss something. My bootloader is unlocked now im trying to root my phone and install custom recovery on it. Currently on 4.4.2 kitkat motorola tx925.
hassoman_64 said:
I apologize for my stupidity.
But, is there any chance for more advance step by step tutorial on this topic.
I have a filing that i'm going to miss something. My bootloader is unlocked now im trying to root my phone and install custom recovery on it. Currently on 4.4.2 kitkat motorola tx925.
Click to expand...
Click to collapse
it's so simple
1- unlocked bootloade
2- root you device
3-install recovery
4-install custom roms
5-install google apps
Confusing with first step...
s27moto said:
it's so simple
1- unlocked bootloade
2- root you device
3-install recovery
4-install custom roms
5-install google apps
Click to expand...
Click to collapse
Hi s27moto,
Thanks for your very clear guide. Btw, In 1 step (unlock bootloader) could you tell me more about this step:
0. My phone is RAZR HD Kitkat offical update, no root, bootloader locked.
1. Can I unlock it by using fastboot command with motopolycase that provided in following link in step 1 (4.4.2 kitkat) ?
2. I tried to unlock my phone using Motorolar website but It's say that my phone is not qualify. What can I do ?
Thanks you.
Quang Hung said:
Hi s27moto,
Thanks for your very clear guide. Btw, In 1 step (unlock bootloader) could you tell me more about this step:
0. My phone is RAZR HD Kitkat offical update, no root, bootloader locked.
1. Can I unlock it by using fastboot command with motopolycase that provided in following link in step 1 (4.4.2 kitkat) ?
2. I tried to unlock my phone using Motorolar website but It's say that my phone is not qualify. What can I do ?
Thanks you.
Click to expand...
Click to collapse
If you have a 926 and are on the latest FW, you can't unlock. If you have a 925, you should be able to unlock via Moto.
Sent from my HTC6525LVW using Tapatalk
xt926 4.4.2 unlocked........
how do I get my root back after 4.4.2 update. all instruction lead to needing custom rom and or rooted. I have stock kk and my device is unlocked what would be the next step for installing a custom rom. hope I asked the question right
kadesxys said:
how do I get my root back after 4.4.2 update. all instruction lead to needing custom rom and or rooted. I have stock kk and my device is unlocked what would be the next step for installing a custom rom. hope I asked the question right
Click to expand...
Click to collapse
no need for custom rom just install a recovery like twrp then flash root and then you are rooted
Fastboot Success??
billycar11 said:
no need for custom rom just install a recovery like twrp then flash root and then you are rooted
Click to expand...
Click to collapse
Has anyone actually flashed a custom recovery on an xt925 4.4.2 OTA? I have had no luck trying any kind of fastboot, mfastboot, Olympian-fastboot... Nothing. If anyone has, perhaps point us to the resource you used. Thanks.
gtan2589 said:
Has anyone actually flashed a custom recovery on an xt925 4.4.2 OTA? I have had no luck trying any kind of fastboot, mfastboot, Olympian-fastboot... Nothing. If anyone has, perhaps point us to the resource you used. Thanks.
Click to expand...
Click to collapse
i use fastboot from the android sdk also make sure you have moto drivers installed
billycar11 said:
i use fastboot from the android sdk also make sure you have moto drivers installed
Click to expand...
Click to collapse
And you did this after the OTA update to 4.4.2? I'll double check the drivers, since I use multiple phone types on my PC. Thanks.
gtan2589 said:
And you did this after the OTA update to 4.4.2? I'll double check the drivers, since I use multiple phone types on my PC. Thanks.
Click to expand...
Click to collapse
yes i did this on 4.4.2
---------- Post added at 03:35 PM ---------- Previous post was at 03:28 PM ----------
gtan2589 said:
And you did this after the OTA update to 4.4.2? I'll double check the drivers, since I use multiple phone types on my PC. Thanks.
Click to expand...
Click to collapse
also here is updated recovery https://twitter.com/dhacker29/status/557054829357707264
edit: i hate the sites he uploads to but you can figure out the right button
Ok. I tried what you said (checked the drivers) and I'm getting this...
(bootloader) Variable bot supported!
Then it looks like it worked, but no joy. Ideas?
--Update--
Just tried with 'mfastboot' and it gave me no error this time and didn't freeze after 'writing recovery', i.e. actually finished the process. Still no TWRP recovery on the phone though.
gtan2589 said:
Ok. I tried what you said (checked the drivers) and I'm getting this...
(bootloader) Variable bot supported!
Then it looks like it worked, but no joy. Ideas?
--Update--
Just tried with 'mfastboot' and it gave me no error this time and didn't freeze after 'writing recovery', i.e. actually finished the process. Still no TWRP recovery on the phone though.
Click to expand...
Click to collapse
Are you booting directly back into recovery after flashing? If you don't, stock recovery will override it. After flashing, immediately power off the phone and boot straight into recovery.
Sent from my HTC6525LVW using Tapatalk
RikRong said:
Are you booting directly back into recovery after flashing? If you don't, stock recovery will override it. After flashing, immediately power off the phone and boot straight into recovery.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
I can't get that far. Whenever I try to flash the recovery, I get...
(bootloader) Variable not supported!
target reported max download size of 31457280
C:\Users\Gaetano\AppData\Local\Android\android-sdk\platform-tools>fastboot getvar all
(bootloader) version-bootloader: 109B(*)
(bootloader) product: vanquish_u
(bootloader) secure: yes
(bootloader) mid: 0056
(bootloader) version: 0.5
(bootloader) serialno: TA24001ST4
(bootloader) qe: qe 0/1
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 31457280
(bootloader) emmc-size: 16GB
(bootloader) reason: Reboot to bootloader
(bootloader) revision-hardware: 0x8300
(bootloader) cpu: MSM8960 CS
(bootloader) uid: 93ABD20802000100000000000000
(bootloader) cid: 0x0e
all:
finished. total time: 0.031s
--UPDATE--
Got it!! I had to...
mfastboot erase cache
Then everything work perfectly!! Thanks, all.
Hello! I'm trying to root it, but it seems like I can't! Is it beacause my version is unable to do so? I have already unlocked the bootloader, flashed the CWM even tryed the TWRP, but I'm unable to do it from the PC and even by the ROM Manager App.
As I enter the recovery mode, there is always a opened up android robot with the !triangle
sistem vers: 180.46.117.XT925.Brasil.en.BR
running 4.4.2
where am I missing?
Thanks!
euricko said:
Hello! I'm trying to root it, but it seems like I can't! Is it beacause my version is unable to do so? I have already unlocked the bootloader, flashed the CWM even tryed the TWRP, but I'm unable to do it from the PC and even by the ROM Manager App.
As I enter the recovery mode, there is always a opened up android robot with the !triangle
sistem vers: 180.46.117.XT925.Brasil.en.BR
running 4.4.2
where am I missing?
Thanks!
Click to expand...
Click to collapse
Looks the same issue I had. When you are in bootloader (fastboot) did you try erasing the cache, then flash recovery?
gtan2589 said:
Looks the same issue I had. When you are in bootloader (fastboot) did you try erasing the cache, then flash recovery?
Click to expand...
Click to collapse
sorry it took too long to answer you. now it won't be online on the adb. i think i've tried everything, new drivers, sdk update, debuggin on/off, delete certifieds pcs, reboot. I'm about to give up hahahah
I couldn't try to do "mfastboot erase cache"
euricko said:
sorry it took too long to answer you. now it won't be online on the adb. i think i've tried everything, new drivers, sdk update, debuggin on/off, delete certifieds pcs, reboot. I'm about to give up hahahah
I couldn't try to do "mfastboot erase cache"
Click to expand...
Click to collapse
Try it without the "m" (fastboot). "mfastboot" command only works if it's in the directory. If that doesn't do it, do a search for "mfastboot" (Motorola version of "fastboot"), put it in the same folder as "fastboot", and try again.
It took me almost 3 weeks of research and experimentation to find something that worked. Don't know how some people got it done so easily.
Hi everyone,
I would like to know if is possible to dowgrande to a different country firmware (I'm not interested in the dual sim option). Anyone know if this is possible? I have a locked and non rooted moto x play. I've tried to follow this thread REMINDER HOW TO DOWNGRADE from 6.0 to 5.1.1, but the installation fail with this error:
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
Click to expand...
Click to collapse
lollo64 said:
Hi everyone,
I would like to know if is possible to dowgrande to a different country firmware (I'm not interested in the dual sim option). Anyone know if this is possible? I have an unlocked and non rooted moto x play. I've tried to follow this thread REMINDER HOW TO DOWNGRADE from 6.0 to 5.1.1, but the installation fail with this error:
Click to expand...
Click to collapse
Yes, downgrading is possible with unlocked bootloader (locked bootloader doesn't allow downgrading). The first 2 commands ("fastboot flash partition gpt.bin" and "fastboot flash bootloader bootloader.img") always fail when downgrading, and can be skipped without any issues, so if the error you got was for one of the first 2 commands just continue with the rest of the commands.
panart said:
Yes, downgrading is possible with unlocked bootloader (locked bootloader doesn't allow downgrading). The first 2 commands ("fastboot flash partition gpt.bin" and "fastboot flash bootloader bootloader.img") always fail when downgrading, and can be skipped without any issues, so if the error you got was for one of the first 2 commands just continue with the rest of the commands.
Click to expand...
Click to collapse
Thanks, I was start to supposing that the locked bootloader was the problem and you just confirmed. Unluckily right now I can't unlock the bootloader so I think I must wait for the release of the complete EU 6.0 Firmware.
lollo64 said:
Thanks, I was start to supposing that the locked bootloader was the problem and you just confirmed. Unluckily right now I can't unlock the bootloader so I think I must wait for the release of the complete EU 6.0 Firmware.
Click to expand...
Click to collapse
In your post you mentioned "unlocked" so i assumed you had unlocked the bootloader already. I'm afraid that downgrading is only possible if you unlock the bootloader, or you can wait for EU 6.0 full stock ROM to become available and try installing that (it might work as you'll be going from 6.0 ROM to 6.0 ROM).
panart said:
In your post you mentioned "unlocked" so i assumed you had unlocked the bootloader already. I'm afraid that downgrading is only possible if you unlock the bootloader, or you can wait for EU 6.0 full stock ROM to become available and try installing that (it might work as you'll be going from 6.0 ROM to 6.0 ROM).
Click to expand...
Click to collapse
Ooops, sorry. It was a typo, I've just fixed it. Yes, right now I'm waiting for the release of EU 6.0 full stock rom and then I'm going to retry to flash it!
lollo64 said:
Ooops, sorry. It was a typo, I've just fixed it. Yes, right now I'm waiting for the release of EU 6.0 full stock rom and then I'm going to retry to flash it!
Click to expand...
Click to collapse
Have you tried what panart said, about skipping the first 2 fastboot commands ?
I also downgraded to 5.1 skipping the first 2 lines and it was working fine.Only I had an unlocked bootloader at that moment ,but maybe it wil also works with a locked bootloader, not sure.
Sickaxis79 said:
Have you tried what panart said, about skipping the first 2 fastboot commands ?
I also downgraded to 5.1 skipping the first 2 lines and it was working fine.Only I had an unlocked bootloader at that moment ,but maybe it wil also works with a locked bootloader, not sure.
Click to expand...
Click to collapse
Yes, I've tried both. With and without the first two commands (fastboot flash partition gpt.bin / fastboot flash bootloader bootloader.img), but it fails in every case. Purposely I get the errors when I launch this commands:
Code:
- fastboot flash boot boot.img
- fastboot flash system system.img_sparsechunk.*
All the other instructions work fine.
http://forum.xda-developers.com/showpost.php?p=65423306&postcount=475
24.65-33 Full EU
You can flash it directly On any XT1562
Update V20E 6.0 T - Mobile
H901 - T Mobile
V20e (6.0)
https://drive.google.com/open?id=0B3R77elw9JjNSmVsVjhjbWdLcEU
V20j (6.0)
http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW1FRFU652MMA4P3503B0ON/H90120j_00_0712.kdz
V20l (6.0)
http://pkg03.lime.gdms.lge.com/dn/d...1478794859&h=59e2525cdab042c7ac78e39941ad3362
Woww. Thánks for sharing
reachedxyz said:
Woww. Thánks for sharing
Click to expand...
Click to collapse
Bày đặt nói tiếng anh
My question you have this here as ROM we are happy is here as promised. But is it rooted or is it just the official download untouched ?
Sent from my LG-H901 using XDA-Developers mobile app
diamantericos said:
My question you have this here as ROM we are happy is here as promised. But is it rooted or is it just the official download untouched ?[/URL]
Click to expand...
Click to collapse
KDZs are factory firmware files, untouched.
Is it possible to root? Bootloader remains unlocked?
jonsat said:
Is it possible to root? Bootloader remains unlocked?
Click to expand...
Click to collapse
Bootloader can be unlocked. No word on root yet
Do you have to have stock recovery to used the kdz file
I'll wait for the rooted stock version, but I'm sure we'll be seeing it this week!
shawn1 said:
Do you have to have stock recovery to used the kdz file
Click to expand...
Click to collapse
I nand back to a stock build thru twrp. Booted to Android ran LG bridge and it worked fine
Sent from my LG-H901 using XDA-Developers mobile app
shawn1 said:
Do you have to have stock recovery to used the kdz file
Click to expand...
Click to collapse
You need to use LGUP for flashing KDZ:
http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
First of all, flashing this KDZ will re-lock the bootloader. It is important to know because if you want unlocked bootloader, you need to execute "fastboot oem unlock" which will wipe all user data.
Secondly, I am surprised to see that TWRP is no longer working after MM update:
Code:
O:\LG\H901>fastboot boot twrp-2.8.7.1-h901.img
downloading 'boot.img'...
OKAY [ 0.732s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.749s
Same error if I try to flash TWRP as well. Did somebody successfully manage to root this version?
Edit: I've also tried with latest TWRP available from this thread:
http://forum.xda-developers.com/tmobile-lg-v10/development/recovery-updated-twrp-v3-0-1-0-t3350825
Maybe we need a newer build of TWRP based on MM sources?
sikander3786 said:
First of all, flashing this KDZ will re-lock the bootloader. It is important to know because if you want unlocked bootloader, you need to execute "fastboot oem unlock" which will wipe all user data.
Secondly, I am surprised to see that TWRP is no longer working after MM update:
Code:
O:\LG\H901>fastboot boot twrp-2.8.7.1-h901.img
downloading 'boot.img'...
OKAY [ 0.732s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.749s
Same error if I try to flash TWRP as well. Did somebody successfully manage to root this version?
Edit: I've also tried with latest TWRP available from this thread:
http://forum.xda-developers.com/tmobile-lg-v10/development/recovery-updated-twrp-v3-0-1-0-t3350825
Maybe we need a newer build of TWRP based on MM sources?
Click to expand...
Click to collapse
i got that same error when trying to fastboot boot TWRP. however, i then realized that my bootloader had been relocked. i assume you re-unlocked yours tho. i have tons of Google Play music downloaded for offline listening, so i'm trying to see if i can back that up before unlocking.
edit: moving google music to sdcard, will unlock and give it a try later on
YrrchSebor said:
i got that same error when trying to fastboot boot TWRP. however, i then realized that my bootloader had been relocked. i assume you re-unlocked yours tho. i have tons of Google Play music downloaded for offline listening, so i'm trying to see if i can back that up before unlocking.
edit: moving google music to sdcard, will unlock and give it a try later on
Click to expand...
Click to collapse
Yes, I unlocked the bootloader again. As per siraltus' post in the thread linked below, we need a new MM compatible TWRP:
http://forum.xda-developers.com/tmo...recovery-updated-twrp-v3-0-1-0-t3350825/page2
Means no rooting for now.
sikander3786 said:
You need to use LGUP for flashing KDZ:
http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
Click to expand...
Click to collapse
LG Flash tool won't work?
Sent from my LG-H901 using XDA-Developers mobile app
SmileBigNow said:
LG Flash tool won't work?
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
No I don't think so. Not with MM KDZ.
sikander3786 said:
First of all, flashing this KDZ will re-lock the bootloader. It is important to know because if you want unlocked bootloader, you need to execute "fastboot oem unlock" which will wipe all user data.
Secondly, I am surprised to see that TWRP is no longer working after MM update:
Code:
O:\LG\H901>fastboot boot twrp-2.8.7.1-h901.img
downloading 'boot.img'...
OKAY [ 0.732s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.749s
Same error if I try to flash TWRP as well. Did somebody successfully manage to root this version?
Edit: I've also tried with latest TWRP available from this thread:
http://forum.xda-developers.com/tmobile-lg-v10/development/recovery-updated-twrp-v3-0-1-0-t3350825
Maybe we need a newer build of TWRP based on MM sources?
Click to expand...
Click to collapse
YrrchSebor said:
i got that same error when trying to fastboot boot TWRP. however, i then realized that my bootloader had been relocked. i assume you re-unlocked yours tho. i have tons of Google Play music downloaded for offline listening, so i'm trying to see if i can back that up before unlocking.
edit: moving google music to sdcard, will unlock and give it a try later on
Click to expand...
Click to collapse
sikander3786 said:
Yes, I unlocked the bootloader again. As per siraltus' post in the thread linked below, we need a new MM compatible TWRP:
http://forum.xda-developers.com/tmo...recovery-updated-twrp-v3-0-1-0-t3350825/page2
Means no rooting for now.
Click to expand...
Click to collapse
BadNews: I hate to be the one to tell you all this, But LG locked some of the fastboot commands... It has nothing to do with TWRP..
you all gota understand that twrp has its own kernel regrdless of what rom you run............. So ROM and Recovery dont tie into eather other..
Nexus 7 did this same thing some time ago.. the fastboot commands are locked up.. LG did the same on the G3 when we figured out how to get around the download mode.........
anyhow, if you even use< fastboot continue >
you will get same error:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot continue
resuming boot...
FAILED (remote: unknown command)
finished. total time: 0.018s
So now, we are all should I say, F----d Up............. I even use my G3 rooting knowledge to gain root... But that method failed tooo, and it uses the download mode come port way..
seems LG though of everything this time around........ But you can count on one thing,, WE WILL HAVE ROOT again.................
We have something the other devices dont have.,. We can unlock our bootloaders.. So, we just gota wait a bit.....................
Eliminater74 said:
BadNews: I hate to be the one to tell you all this, But LG locked some of the fastboot commands... It has nothing to do with TWRP..
you all gota understand that twrp has its own kernel regrdless of what rom you run............. So ROM and Recovery dont tie into eather other..
Nexus 7 did this same thing some time ago.. the fastboot commands are locked up.. LG did the same on the G3 when we figured out how to get around the download mode.........
anyhow, if you even use< fastboot continue >
you will get same error:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot continue
resuming boot...
FAILED (remote: unknown command)
finished. total time: 0.018s
So now, we are all should I say, F----d Up............. I even use my G3 rooting knowledge to gain root... But that method failed tooo, and it uses the download mode come port way..
seems LG though of everything this time around........ But you can count on one thing,, WE WILL HAVE ROOT again.................
We have something the other devices dont have.,. We can unlock our bootloaders.. So, we just gota wait a bit.....................
Click to expand...
Click to collapse
That's bad, real bad.
The first thing most of us will want to know here is if downgrade to 5.1.1 is safe? If yes, which build? I don't think we have many options there.
For rooting, can we try opening the LG Com port using the old 9% method? Maybe then we can try flashing a root injected system image? I am away from PC so can't try this right now. Won't be asking otherwise.
I will wait for a flashable zip. And hope it will have root. Or maybe stick with the Korean Mm port
Sent from my LG-H901 using XDA-Developers mobile app
Yep. Flashable zip is the way to go for now (if it somehow becomes available). I am not sure how to read system dump from a locked-down device and create a Flashable zip.
I will try downgrading to 5.1.1 in the morning.
Just wondering, why allow bootloader unlock if LG and T-Mobile want to lock down everything else?
hi now I no you prob see this title and think oh another 1 but hear me out as I cant find any thing the same as the issue I'm having.
so I followed a rooting guide unlocked bootloader installed twrp all good installed supersu phone wont boot reinstalled twrp systemless installed supersu still nothing I have followed every guide I can find phone will only boot into twrp or bootloader I have flashed custom and stock roms however I do keep getting
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.004s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.071s
PS C:\Program Files (x86)\Minimal ADB and Fastboot>
I have tried every way I can find still nothing when I try to boot it freezes on the screen saying my phone is unlocked and cant be trusted I'm now lost don't no were to go from here I did not back any thing up as the first thread I read don't say bout it and iv neva had any problems with any of my other phones or games consoles I no games consoles are different any help would be amazing
Most likely the flashing wasn’t complete or corrupted or the stock ROM wasn’t the correct one (Remember to be safe you’d have to flash the original ROM when you bought the phone) that being said. My suggestion you should try flashing TWRP again and boot into TWRP. Then flash stock ROM which will overwrite the current config. Not guaranteed, but it’s worth a shot.
Good luck.
Sent from my iPhone 7 Plus from Tapatalk
Sorry to sound dumb flash it through twrps? I can get twrps to boot but thats it iv flashed through bootloader putting all commands in separate but when i tried to boot it came up with no command with the andriod dude with a red triangle above him but i can flash and boot twrps after this
1) If you're rooting on stock Motorola Nougat ROMs, you need a custom kernel - attempting to root on the stock Motorola hudsoncm kernel usually results in a boot failure or bootloop as you've found. https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918 for a useful guide, you can root with either magisk or SuperSU.
2)That security downgrade error suggests you're attempting to flash stock firmware older than the firmware matching your device's bootloader. If you need newer firmware, you could look into this thread: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 You'll need to flash this firmware via fastboot/the bootloader.
3) Try first of all booting into TWRP, copy a custom kernel to your device via a computer and USB cable, and then flash the custom kernel. See if that gets your device booting. If not, you may have to re-flash the stock firmware to get your device booting again (or use a backup, if you had one).
echo92 said:
1) If you're rooting on stock Motorola Nougat ROMs, you need a custom kernel - attempting to root on the stock Motorola hudsoncm kernel usually results in a boot failure or bootloop as you've found. https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918 for a useful guide, you can root with either magisk or SuperSU.
2)That security downgrade error suggests you're attempting to flash stock firmware older than the firmware matching your device's bootloader. If you need newer firmware, you could look into this thread: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 You'll need to flash this firmware via fastboot/the bootloader.
3) Try first of all booting into TWRP, copy a custom kernel to your device via a computer and USB cable, and then flash the custom kernel. See if that gets your device booting. If not, you may have to re-flash the stock firmware to get your device booting again (or use a backup, if you had one).
Click to expand...
Click to collapse
If xt1625 amazon not having understood flash RSD firmware ATHENE_NPJS25.93-14-13 (instead ATHENE_AMZ_NPJ25.93-14.7) is there any way to restore the phone's load ?
bootloder lock, oem lock, "we have detected an attempt to flash unauthorized sw on your device"
hlpain said:
If xt1625 amazon not having understood flash RSD firmware ATHENE_NPJS25.93-14-13 (instead ATHENE_AMZ_NPJ25.93-14.7) is there any way to restore the phone's load ?
bootloder lock, oem lock, "we have detected an attempt to flash unauthorized sw on your device"
Click to expand...
Click to collapse
Have you tried to flash this firmware: https://androidfilehost.com/?fid=817906626617956922 That should be the AMZ NPJ25.93-14.7 US firmware (for XT1625 and XT1644)
tried, error gpt bootloader, all firmware below 14-13 not installed, AMZ NPJ25.93-14-13 I did not find it or it does not exist.
hlpain said:
tried, error gpt bootloader, all firmware below 14-13 not installed, AMZ NPJ25.93-14-13 I did not find it or it does not exist.
Click to expand...
Click to collapse
Unfortunately you'd have to wait for a newer firmware, the NPJS25.93-14-13, NPJS25.93-14-15 and NPJS25.93-14-18 firmwares are for retail devices. Amazon devices are on a different firmware and as you've partially flashed the Dec 2017 firmware, you'd likely need AMZ NPJ25.93-14.7-3 or NPJ25.93-14.7-5 (Feb 2018 update), however neither AMZ build appears to be available at the moment.
If you're desperate for a working device, your best bet may be to talk to Amazon or Motorola support, or if your bootloader was previously unlocked, you could try to unlock your bootloader and flash a custom ROM.
I will wait for a new firmware amz