Code:
PID: Null
IMEI: Null
Model :
DLL: LS990
BIN: LS990ZV4_04.51101.TOT
SWV:
SWOV:
Model Information Check Fail
000000000
Please help I've been troubleshooting for days, tried redownloaded huge TOT files, tried different cables different systems etc.
Does this mean I have a special version of the LS990 that can't be downgraded?
what does this mean?
Only similar issue I found is this: http://forum.xda-developers.com/showthread.php?t=2729056&page=2
The [email protected]$$ says "NM, I got it too work!!"
And doesn't share the solution :crying:
EDIT; I guess implicitly, the solution in is in the return the to stock guide for LG G2 Verizon mentioned in the earlier reply, but that won't help my Sprint LG G3. Different ballgame alltogether.
DOUBLE EDIT: Just re-read hyelton's Return to Stock thread for the 10th time in the G2 general section, nothing seems to jump out aside from the warning not to use 16GB files for 32GB phone. AFAIK, G3 only comes in 32GB so I don't think even that would apply.
Again, I'm left to wonder if I have some odd engineering sample or a tampered (previously rooted maybe) phone.
And yes, I've tried the generic LGUP_8974.dll from AutoPrime
Nobody encourtered this?
Is this really such a unique issue that no one has encountered this on the G3?
It has to be something simple right?
Why is the generic dll not working either, does anyone have an alternate dll I could try?
Can you maybe post some screen shots? This can help us to really help. Why are trying to to "Tot" back? Is it because of some sort of recovery problem or something? The reason I aak is because this maybe able to tell me/us how we can help you. Can you tell us what os(s) you have used? This maybe because the usb port(s) you are using maybe "dead" this could end up causing the phone to not be able to "talk" to the computer correctly.
screenshot
A screenshot would simple have the FAIL status on a red backround and the code from the OP:
Code:
PID: Null
IMEI: Null
Model :
DLL: LS990
BIN: LS990ZV4_04.51101.TOT
SWV:
SWOV:
Model Information Check Fail
000000000
This is on VirtualBox on a Macbook, USB ports are fine I'm able to copy to and from the phone, adb works, etc
Tried it on my Windows machine and get FailedPreviousLoad() BIN CRC (attached screen)
And my reason for downgrading is I'm on ZV6 and would like to root
Is the device bricked? This code cause many problems. You might end up having to go to sprint and getting a replacment device. I have never herd of this before. You may need to stop using any VM(s) it might have some sort of problem with your phone.
Yes but the tot not passing usually indicates a bad download
This is my downloaded file's md5 hash
ed593facd25e16597ebf3834f435b820
The problem is I have nothing to compare it to... the source at codefi.re doesn't have an MD5!
http://downloads.codefi.re/wolfgart/LG_G3/LS990/ZV4/LS990ZV4_04.51101.tot
As far as what happens in the VM that's a different problem and the one that I'm focused on since the TOT passes there, I get further
Could this phone have been tampered with? That's what it's starting to look like.... it's as if it thinks it's another device.
Do you have another DLL I could try? I'm at my wits end here
Have you looked in this thread http://forum.xda-developers.com/showthread.php?p=54912191 or asked for help there?
Edfunkycold
Have a great day!
Thanks, I'll scour it again
Thanks, but I have been reading that thread, it's where I got the TOT file link from in the first place, and yeah, I think I might post there too.
Just wanted my own thread for more exposure.
EDIT: There is a user on page 26 of that thread, but they are pretty much at the point of giving up.
It's starting to look like this mystery will go unsolved
TechShui said:
Thanks, but I have been reading that thread, it's where I got the TOT file link from in the first place, and yeah, I think I might post there too.
Just wanted my own thread for more exposure.
EDIT: There is a user on page 26 of that thread, but they are pretty much at the point of giving up.
It's starting to look like this mystery will go unsolved
Click to expand...
Click to collapse
Did you backup your EFS? It looks like it got cleared. I'm not sure how you can restore it now without TWRP..
Isn't EFS just for data? @engine95
---------- Post added at 10:50 PM ---------- Previous post was at 10:49 PM ----------
Can you post a screenshot of the settings for the flash tool? I just want to see something
1619415 said:
Isn't EFS just for data? @engine95
---------- Post added at 10:50 PM ---------- Previous post was at 10:49 PM ----------
Can you post a screenshot of the settings for the flash tool? I just want to see something
Click to expand...
Click to collapse
In the screenshots, everything is either null or zeros. That usually means the EFS got wiped. If it's not backed up it usually means a brick. And it'll be very lucky to save it.
I could be wrong. And I can't remember if Flashtool shows it that way? Or if he's cleared them for posting. But in the past, and if I'm seeing/remembering right. That's not a good sign.
I think in the International forum, autoprime might have posted a possible way to save it. Or it might have been in the irc.
EFS is what gives us all functionality of cell and data. Along with our personal Id to the phone. In a nutshell.
Edit: heres a post about EFS. http://forum.xda-developers.com/showthread.php?p=56058409&postcount=1 There's also a lot of links in the FAQ
that's a good guess, but I the IMEI is not missing from within About Phone, Model information
The phone boots and runs fine, just want it rooted. Tried PurpleDrake too and it said to downgrade
Tried stump, it says "Device has been patched"
I don't want to give up but I'm running out of ideas.
New root method posted in general seems to be working for a lot of people
I am having the exact same issue with "Model Information Check Fail" on an LG990
TechShui said:
that's a good guess, but I the IMEI is not missing from within About Phone, Model information
The phone boots and runs fine, just want it rooted. Tried PurpleDrake too and it said to downgrade
Tried stump, it says "Device has been patched"
I don't want to give up but I'm running out of ideas.
Click to expand...
Click to collapse
I get the same error message that my phone has been patched, which is why I have gone down this path. I also get model information failed, and I've tried tot's 4,6, and 8 and get the same result. Also, just like you I can reboot the phone and it works fine. So if you have found or happen to find something that will help this issue, please be sure and post what you did to fix it.
Thanks!!1
no situation? can u help me fix my phone? i flashed the wrong rom. no download screen. no recovery. pc recognizes the port though. LG FlashTool says this: PID: Null
IMEI: Null
Model :
DLL: LS990
BIN: LS990ZV4_04.51101.TOT
SWV:
SWOV:
Model Information Check Fail
000000000
i fix this error by flashing cloudi rom and selecting correct model bot you will need a custom recovery
Related
Well I made a mess out of this situation... I was trying to do the OTA update for MJ7 but it was failing.. I seemed to be one of a very select few that got this issue but from researching, I found that I should be able to update via the USB cable on my PC and let the verizon update utility that installed on my PC find the update and install it. Fair enough, it came up and showed an update ready. After download it started installing, after about 5 minutes, it times out and gave me some error that I needed to connected to kies and do a recovery as the update failed. No matter what I did, restarting my phone and recovery mode, everything, it kept taking me to that message, unless I went into ODIN mode, that showed as it was supposed to...
to try and wrap this long story short, I tried many methods of recovering my phone and/or finish the update WITHOUT losing data. Everything I found led to a dead end and I found the only way was to run the recovery through the verizon utility app on the PC. It stated it would not keep data and basically do a factory reset in a nutshell.. No problem I thought, I was thinking it would put me back on my original OS version like MI7 or even ME7 and I could root and recover a lot of my data through Titanium Backup... i found there was no way to root MJ7 (yet) although after the fact I saw the article of attempting to keep it after update, but we know how that went... nonetheless.. the repair did reset my phone and it put the MJ7 (latest version) on the phone... great, no root method there... now i read and from what I understand if I try to flash back to a previous version it permanently logs it and marks this new KNOX marker that its been changed and "voids" the warranty and thus far there is no found way to keep that from happening nor reverse it after it does..
Question is... IS all my research correct as stated in above paragraph? OR is there a way I can safely flash back to a previous STOCK OS such as ME7 or MI7, be able to root the phone again, then go back on my merry way (with or without updating to MJ7 this time after I get my data back, hopefully?) If possible, I want to MAKE SURE I have the correct files or a link supplied to a existing post with download links with the right downloads I need to get. Hate to brick the phone again and go through all this waiting all over again. Any help appreciated!
Thanks,
David
Sorry, your correct, there is no way back and no way to root.
Ryno77 said:
Sorry, your correct, there is no way back and no way to root.
Click to expand...
Click to collapse
So to confirm, even if I were to ODIN my way back to a older stock image like ME7 or MI7, what exactly would occur then? Would it work but tick that KNOX 0x0 to 0x1 thus "voiding" warranty but still take me back to previous version where I may root once again...?? Or...??
This has been said hundreds of times:
You can not move backwards. Once you're on a release, you can only install the same or later software.
---------- Post added at 07:08 PM ---------- Previous post was at 07:03 PM ----------
dpiffy said:
So to confirm, even if I were to ODIN my way back to a older stock image like ME7 or MI7, what exactly would occur then? Would it work but tick that KNOX 0x0 to 0x1 thus "voiding" warranty but still take me back to previous version where I may root once again...?? Or...??
Click to expand...
Click to collapse
If you try to flash older software, it'll fail and softbrick your device. This will only allow download mode, requiring you to flash what's expected to recover your phone.
You'll only trip the Knox warranty flag if you try to flash an un-signed bootloader (and, I think, an unsigned recovery.)
k1mu said:
This has been said hundreds of times:
You can not move backwards. Once you're on a release, you can only install the same or later software.
Click to expand...
Click to collapse
Well then please excuse me. As I said I researched this for a lengthy amount of time, I found mixed answers on this issue found some saying it is not possible but doesn't say why (much like you just did, not explain what happens as I asked, all due respect). I found places saying it is possible but this new "KNOX" thing on the latest version which I know VERY little about, that it would add a "count" or change the value but would work, of course many people don't want to do that with there not being a way to revert it back, from my understanding. Then some articles are handing out download links to restore/downgrade left and right. So again, excuse my confusion. Even after starting to write this article and the subject line I used produced possible matches to what I was about to post about, NONE and I repeat NONE of those options fit my question, so I don't need this "it has been said 'hundreds of times" when I just spend the greater part of my afternoon getting my phone updated then it failing and trying to do anything to get it back up and running one way or another. Not in the best of moods as I lost some precious data on my internal storage that otherwise would be safe and able to be restored from the titanium backup, which is proving useless right now. Nope, that is not your fault, but show a LITTLE more respect to this open community instead of being Mr. Moderator over there correcting me on things that aren't exactly made clear from all the other posts I have read today!
k1mu said:
This has been said hundreds of times:
You can not move backwards. Once you're on a release, you can only install the same or later software.
---------- Post added at 07:08 PM ---------- Previous post was at 07:03 PM ----------
If you try to flash older software, it'll fail and softbrick your device. This will only allow download mode, requiring you to flash what's expected to recover your phone.
You'll only trip the Knox warranty flag if you try to flash an un-signed bootloader (and, I think, an unsigned recovery.)
Click to expand...
Click to collapse
Now that I see you evidently edited your last response, I saw after the fact your response you ended up making. Thank you for explaining as I only asked for in the first place.
dpiffy said:
Now that I see you evidently edited your last response, I saw after the fact your response you ended up making. Thank you for explaining as I only asked for in the first place.
Click to expand...
Click to collapse
No editing, but there's been two of us replying. JFTR.
Hopefully we've saved you from a trip to softbrick city. :good:
(Edit: I see - the "post edited" - well, what happens is if you post more than once to a thread, the posts get combined where the subsequent posts are marked as edits. That's a bit misleading. THIS is an edit after-the-fact.)
Bummer
Got it. Well thanks...
It's not a question of if but when someone will figure all this out again... especially for a phone as the S4... i'd be more than happy to put forth a donation to further encourage someone to get things rooted AND unlocked again... I have a lot of stuff I'd pay decent money towards getting my data back through my Titanium Backup files... there is still some things I lost and can't even get back through the TB but anything is better than nothing... Where do you give donations through? I've always heard of the "bounty" -- do you have to be in any specific standing on these forums to give to this?
So, its been a rough time with this phone. I received it rooted and im really a noob to any of this, its a verizon phone, its labeled outside, and when you remove the battery it says model VS985. But in the settings it says otherwise. I placed an att sim card in it, and it worked fine, i just had some errors on the rom that i have no idea how to fix, it all just seems like a hassle to me, so i decided to unroot it to the best of my ability. I managed to download everything and when i ran the lg flash tool, i selected the firmware i downloaded, the verizon one, but when i tried to run it, it would say "Device Model is different" "factory model check error" or something like that, it would identify the phone has D850, which is at&t version.
So i went ahead and said **** it, i downloaded that version and went with that, something messed up and it ended with factory reset status 2 instead of 3.
So i had to select BOARD instead of UPGRADE in the flash tool. and it reset everything, booted with att logo and everything, now the only problem is i don't get any signal, at all. Any help?
cedric182 said:
So, its been a rough time with this phone. I received it rooted and im really a noob to any of this, its a verizon phone, its labeled outside, and when you remove the battery it says model VS985. But in the settings it says otherwise. I placed an att sim card in it, and it worked fine, i just had some errors on the rom that i have no idea how to fix, it all just seems like a hassle to me, so i decided to unroot it to the best of my ability. I managed to download everything and when i ran the lg flash tool, i selected the firmware i downloaded, the verizon one, but when i tried to run it, it would say "Device Model is different" "factory model check error" or something like that, it would identify the phone has D850, which is at&t version.
So i went ahead and said **** it, i downloaded that version and went with that, something messed up and it ended with factory reset status 2 instead of 3.
So i had to select BOARD instead of UPGRADE in the flash tool. and it reset everything, booted with att logo and everything, now the only problem is i don't get any signal, at all. Any help?
Click to expand...
Click to collapse
Somewhere in the g3 forums is an unbranded DLL file. It is my understanding from reading about it previously, you need to use that to allow you to flash the proper firmware. The DLL file was made to fix this exact issue from what I read before.
bweN diorD said:
Somewhere in the g3 forums is an unbranded DLL file. It is my understanding from reading about it previously, you need to use that to allow you to flash the proper firmware. The DLL file was made to fix this exact issue from what I read before.
Click to expand...
Click to collapse
Really? any more info on how to find it?
cedric182 said:
Really? any more info on how to find it?
Click to expand...
Click to collapse
I wish I could point you right to it, unfortunately you may have to browse similar help threads to yours until you find it.
I have the exact same problem but mine is seen as a d855 when it is a vs985 if you can find that .dll file please tell me as well! I am going to search for it now
cedric182 said:
So, its been a rough time with this phone. I received it rooted and im really a noob to any of this, its a verizon phone, its labeled outside, and when you remove the battery it says model VS985. But in the settings it says otherwise. I placed an att sim card in it, and it worked fine, i just had some errors on the rom that i have no idea how to fix, it all just seems like a hassle to me, so i decided to unroot it to the best of my ability. I managed to download everything and when i ran the lg flash tool, i selected the firmware i downloaded, the verizon one, but when i tried to run it, it would say "Device Model is different" "factory model check error" or something like that, it would identify the phone has D850, which is at&t version.
So i went ahead and said **** it, i downloaded that version and went with that, something messed up and it ended with factory reset status 2 instead of 3.
So i had to select BOARD instead of UPGRADE in the flash tool. and it reset everything, booted with att logo and everything, now the only problem is i don't get any signal, at all. Any help?
Click to expand...
Click to collapse
If you are 100% sure you do in fact have the Verizon LG G3 (VS985), replace the Verizon DLL file with the Generic LG G3 DLL below. This error is most common if you have changed the Product Name, Product Model, Display ID, and/or Build ID entries in the build.prop
The generic dll file is on autoprime's site. It's named LGUP_8974.dll and can be found here- http://downloads.codefi.re/autoprime/LG/LG_G3 Use that along with the Verizon firmware Instead of the Verizon dll
Hawkswind thank you so much!! that worked for me now i am going to flash back the verizon .dll file
Thank you.
Hi guys,
Just wondering if I can get root without unlocking the bootloader. Seems that I;m hearing that this isn't possible, which makes no sense. I know Verizon is Verizon when it comes to locking things down(They were even blocking free games on dumbphones back in the day so that you would have to buy them, even when the manufacturer included them for free), but it seems that gaining root access is completely different than flashing a new ROM. Am I correct here?
Also, would towelroot work for this phone? I know it's a nice simple solution, but I believe their claim is for phones manufactured before Jun '14.
Lastly, would a solution like Safestrap work here? It's what I used on my last phone (S3), when Verizon locked THAT down.
I know it is a battle fighting Verizon on this, and I know it takes time, I was just wondering if I am reading this right, or if I could root, but run the standard ROM, just with the extra access... Really, the phone is working so well that I just want better control for things like deleting/disabling/freezing stock apps and such.
Thanks for any help!! Sorry if this is in the wrong thread, seemed appropriate.
I am a user of H961N and it is also cannot be rooted.
I think root injection may be the answer.
http://forum.xda-developers.com/g4/general/lg-g4-100-root-success-directives-root-t3180586
This is the related thread in G4 forum. I have tried this method. However, I have encountered a problem shown below during the process:
Code:
D:\V10\LG_Root>Send_Command.exe \\.\COM8
Author : blog.lvu.kr
SPECIAL COMMAND : ENTER, LEAVE
#dd if=/dev/block/mmcblk0p51 of=/data/media/0/system.img
FAIL
#ls
FAIL
#
It keeps returning "FAIL" to me no matter what command i enter. I have asked about this in the thread in G4 forum but no one answer me, sad
I think that you may try it and it may work, as the above problem may not due to the phone but my computer.
Where did you get you system.img file? if you are using the one from the g4 it will not work. The file needs to be rooted for your device and then injected.
ivangundampc said:
I am a user of H961N and it is also cannot be rooted.
I think root injection may be the answer.
http://forum.xda-developers.com/g4/general/lg-g4-100-root-success-directives-root-t3180586
This is the related thread in G4 forum. I have tried this method. However, I have encountered a problem shown below during the process:
Code:
D:\V10\LG_Root>Send_Command.exe \\.\COM8
Author : blog.lvu.kr
SPECIAL COMMAND : ENTER, LEAVE
#dd if=/dev/block/mmcblk0p51 of=/data/media/0/system.img
FAIL
#ls
FAIL
#
It keeps returning "FAIL" to me no matter what command i enter. I have asked about this in the thread in G4 forum but no one answer me, sad
I think that you may try it and it may work, as the above problem may not due to the phone but my computer.
Click to expand...
Click to collapse
ivangundampc said:
I am a user of H961N and it is also cannot be rooted.
I think root injection may be the answer.
http://forum.xda-developers.com/g4/general/lg-g4-100-root-success-directives-root-t3180586
This is the related thread in G4 forum. I have tried this method. However, I have encountered a problem shown below during the process:
It keeps returning "FAIL" to me no matter what command i enter. I have asked about this in the thread in G4 forum but no one answer me, sad
I think that you may try it and it may work, as the above problem may not due to the phone but my computer.
Click to expand...
Click to collapse
I'm curious, the 'Fail' just means that it fails to work, right? Phone works fine after that and all? No bricking or need to restore? If so, that's a safe risk. Thanks for the suggestion.
Mikey1969 said:
I'm curious, the 'Fail' just means that it fails to work, right? Phone works fine after that and all? No bricking or need to restore? If so, that's a safe risk. Thanks for the suggestion.
Click to expand...
Click to collapse
Yes, the phone is working fine after I have tried this. So it is a safe risk.
---------- Post added at 12:08 PM ---------- Previous post was at 12:06 PM ----------
spidey44 said:
Where did you get you system.img file? if you are using the one from the g4 it will not work. The file needs to be rooted for your device and then injected.
Click to expand...
Click to collapse
That's why I am trying to clone the system partition but it shows fail
Good luck with this but I have a feeling that unless someone has an exploit laying around, you'll need an unlocked bootloader.
Sent from my LG-H901 using Tapatalk
Should this be in the Q and A sections as this is not development?
Don't have an LG v10 yet, but found this:
www.droidviews.com/how-to-root-lg-v10-with-supersu-v2-56/
Thought I'll share if someone would like to give this a shot.
(try at your own risk, that's all I can write to that, since i can't try myself.)
Thanks for this.....but i was reading that article...it says you root it by flashing the superuser zip in TWRP recovery....um....you cannot flash custom recovery without root....or am i missing something. Im not bashing you for posting the article. I thank you very much for posting it! More like questioning the articles validity.
in99flames said:
Thanks for this.....but i was reading that article...it says you root it by flashing the superuser zip in TWRP recovery....um....you cannot flash custom recovery without root....or am i missing something. Im not bashing you for posting the article. I thank you very much for posting it! More like questioning the articles validity.
Click to expand...
Click to collapse
you need an unlocked bootloader
http://www.droidviews.com/how-to-unlock-bootloader-on-lg-v10/
and adb & fastboot tool, not root
To install a custom recovery
http://www.droidviews.com/how-to-install-twrp-recovery-on-lg-v10-h901/
That's how I usually would do it, the way it's described in the articles, since I still have to get my v10 from Far East can't test it.
And don't worry, I don't feel like you are bashing.
Life's too short to take anything too personal.
Awesome thank you for clearing that up!! I was totally confused for a second there.
GerManiac said:
you need an unlocked bootloader
http://www.droidviews.com/how-to-unlock-bootloader-on-lg-v10/
and adb & fastboot tool, not root
To install a custom recovery
http://www.droidviews.com/how-to-install-twrp-recovery-on-lg-v10-h901/
That's how I usually would do it, the way it's described in the articles, since I still have to get my v10 from Far East can't test it.
And don't worry, I don't feel like you are bashing.
Life's too short to take anything too personal.
Click to expand...
Click to collapse
What you've mention is only working for tmobile V10, since it's bootloader can be easily unlocked while the other are not.
ivangundampc said:
What you've mention is only working for tmobile V10, since it's bootloader can be easily unlocked while the other are not.
Click to expand...
Click to collapse
Thanks for clearing that up. Didn't know that and didn't see that on the article.
Cheers
I think if LG release a genuine ROM file, we could replace recovery parition with rooted one and flash it to our phone, that the only way open but LG hasn't released any ROM file yet.
phillymade said:
Should this be in the Q and A sections as this is not development?
Click to expand...
Click to collapse
Sorry, wasn't sure, as I was asking about development.... Sometimes this is like a scene form the movie Big Trouble... At the airport, "Arrivals or Departures"? "Well, we're arriving at the airport, but then we're going to be departing.".
good nights and days that have this problem I want to go back to Stock 4.4.2 48a but I get this error can be?
model information check fail
00000000
factory model check error
that injection can lead this?
black listed?
Raymerg3v2 said:
good nights and days that have this problem I want to go back to Stock 4.4.2 48a but I get this error can be?
model information check fail
00000000
factory model check error
that injection can lead this?
Click to expand...
Click to collapse
48A is 6.0.
4.4.2 is KitKat
Try searching threads on here. It took me a LOT of digging, but I found the answers. Every way that something went wrong for someone on here, minus bricking my device, happened every time I tried to root. the .kdz method absolutely would not work for me. the .tot method, however, worked with lg flash tool but the .dll file being lgup8975 from the .zip of the same name as stated in the previous stately statement, but then again, what state is your phone in. is it happy?
http://forum.xda-developers.com/verizon-lg-g3/general/verizon-lg-g3-one-toolkit-vs985-root-t3124846
Why-Fi said:
48A is 6.0.
4.4.2 is KitKat
Try searching threads on here. It took me a LOT of digging, but I found the answers. Every way that something went wrong for someone on here, minus bricking my device, happened every time I tried to root. the .kdz method absolutely would not work for me. the .tot method, however, worked with lg flash tool but the .dll file being lgup8975 from the .zip of the same name as stated in the previous stately statement, but then again, what state is your phone in. is it happy?
Click to expand...
Click to collapse
I'm also trying to downgrade from 48A.
Did you mean lgup8974.dll? I can't seem to find lgup8975 anywhere, and I get the same error with lgup8974. I've tried following every guide I could find, as well as improvising, all to no avail. I'm about ready to offer of $50 to anyone who can successfuly downgrade my phone...
Edit: Nevermind, I figured it out. Phone is VS985WK... Guess I'll just have to sell/trade it...
Raymerg3v2 said:
good nights and days that have this problem I want to go back to Stock 4.4.2 48a but I get this error can be?
model information check fail
00000000
factory model check error
that injection can lead this?
Click to expand...
Click to collapse
You can use the 31B dll file to restore or as in my case i flashed 24B KDZ that worked for me
UPDATED 3-30-2018:
Offical TWRP has been released for this device.
https://twrp.me/motorola/motorolamotox4.html
It seems to have a couple active maintainers.
TWRP builds linked from here are no longer active, but the bootable may remain important to use.
---
Update 05/31/2018:
Step 1: install or boot TWRP
Step 2: flash your desired root package (magisk, SuperSU, etc)
That's all.
Screenshot
mightysween said:
Screenshot
Click to expand...
Click to collapse
Now... on to building the device tree and vendor
UPDATE: Geez, this is VERY different than anything I have done before. There is no recovery image at all!? I need to get up to speed on these new filesystems, I guess.
Great news - thank you!
Any chance you could post a checksum for the modified boot.img? I'm just paranoid given our issues with corrupt downloads from the Moto server and Mega as of late!
caain said:
Great news - thank you!
Any chance you could post a checksum for the modified boot.img? I'm just paranoid given our issues with corrupt downloads from the Moto server and Mega as of late!
Click to expand...
Click to collapse
Done, check OP.
Also, have been trying to get it uploaded directly to XDA but not working... gives no errors, but maybe too big?
I did not realize I could not unlock the bootloader on the Amazon version of this phone.
I will probably have to return it and get a different phone.
Sucks.
EDIT: I specifically bought the device because it said unlocked. I didn't know it just meant carrier unlocked.
johnjingle said:
I did not realize I could not unlock the bootloader on the Amazon version of this phone.
I will probably have to return it and get a different phone.
Sucks.
Click to expand...
Click to collapse
Bummer... I suspect most of the variants other than the XT1900-1 may be in the same boat.
mightysween said:
Bummer... I suspect most of the variants other than the XT1900-1 may be in the same boat.
Click to expand...
Click to collapse
The phone is labeled on the box and the SKU in about phone as XT1900-1. Just can't get an unlock code from Motorola, I believe because I bought it through Amazon.
I'm willing to try anything to unlock. Don't want to have to return the phone, just won't deal with a locked bootloader.
It was a pain to get my old phone (Droid Turbo) unlocked and will not deal with the pain it was to do that again.
If anyone has advice PM me.
EDIT: Half the reason I buy stuff is to tinker with it as a hobby.
johnjingle said:
The phone is labeled on the box and the SKU in about phone as XT1900-1. Just can't get an unlock code from Motorola, I believe because I bought it through Amazon.
I'm willing to try anything to unlock. Don't want to have to return the phone, just won't deal with a locked bootloader.
It was a pain to get my old phone (Droid Turbo) unlocked and will not deal with the pain it was to do that again.
If anyone has advice PM me.
Click to expand...
Click to collapse
Ah, so restricted by IMEI. They did that with Moto Gs back a few years.
mightysween said:
Ah, so restricted by IMEI. They did that with Moto Gs back a few years.
Click to expand...
Click to collapse
So... If I return this phone and buy one from Best Buy do you think that bootloader would be unlockable?
I got one from best buy and yes i unlocked it
running on verizon. I just did this and waiting for the phone to finish booting up. Taking a while here.
---------- Post added at 03:22 AM ---------- Previous post was at 03:07 AM ----------
has anyone tried to flash recovery yet? Or is this way to much in infancy for that?
\
hotpl8 said:
I got one from best buy and yes i unlocked it
running on verizon. I just did this and waiting for the phone to finish booting up. Taking a while here.
---------- Post added at 03:22 AM ---------- Previous post was at 03:07 AM ----------
has anyone tried to flash recovery yet? Or is this way to much in infancy for that?
Click to expand...
Click to collapse
There is no recovery to flash Hopefully we can get device tree and vendor built... not going so hot on that front at the moment.
Something happened
I did as described above. And I got stuck on a boot loop left it for 15 min. or more I got back into fastboot and booted the boot.img again and it just kept reseting. I got into create an account and when I was done google play services wasnt working causing more issue. Is there a stock img that I can flash to get this back to stock>?
Is it the oem.img or am I into something worse here?
hotpl8 said:
I did as described above. And I got stuck on a boot loop left it for 15 min. or more I got back into fastboot and booted the boot.img again and it just kept reseting. I got into create an account and when I was done google play services wasnt working causing more issue. Is there a stock img that I can flash to get this back to stock>?
Is it the oem.img or am I into something worse here?
Click to expand...
Click to collapse
I'd wait for mightysween to weigh in on this. I haven't flashed his modified boot.img myself yet, though I did unlock the device in preparation for it. I forgot unlocking erases all userdata so I'm setting the thing up again.
We think what we downloaded from the Moto server in the other thread is a complete firmware package for the current X4 Fi build. It is untested apart from the boot.img, to my knowledge. Did you by chance look at your 'About Phone' screen before this? I would specifically be interested in what was under "Software Variant", "Software Channel", and "build number". You mentioned previously that you purchased your X4 from Best Buy, so we may be working with different animals as there are several X4 variants. I am no developer, but it's possible that the stock boot.img files differ between variants.
---------- Post added at 12:19 AM ---------- Previous post was at 12:11 AM ----------
mightysween said:
ONLY VERIFIED ON XT-1900-1 (payton_sprout/Project Fi) running NPW26.83-34-0-1 firmware
Click to expand...
Click to collapse
So my "Motorola version" under the "About Phone" heading does report NPW26.83-34-0-1. However, my build number reports NPW26.4. Is this what yours is reading? Software variant reads google_fi, software channel reads retus. I wonder if it wouldn't be a good idea to get a cross comparison on these figures from those with Amazon and Best Buy devices.
I've got cold feet on flashing the boot.img after hotpl8 ran into issues, but I'm wondering if it's due to the variant differences. The firmware we got from the Moto server is NPW26.83-34-0-1, baseband M660_7020.05.01.52.01R. It ought to work as a backup for Fi variants, but I'd hate to be the first one that flashes it. Just mailed my N6 back to Google yesterday, so I've got no backup.
For everybody worrying about the modified boot.img, I was able to flash it without issue and everything is running fine. Got Titanium BU and Root Explorer (and Busybox) running w/root privileges. Android Pay is borked, but unlocking the bootloader did that.
Bootloader Info:
AP fastboot Flash Mode (Secure)
BL: MBM-3.0-uefi-f02712d-171004
Baseband: M660_7020.05.01.052.01R PAYTON_NA_CUST
Product/Variant: payton XT1900-1 32GB P4
Serial Number: **********
CPU: SDM630 1.0 (2)
eMMC: 32GB SAMSUNG DD68MB RV=08 PV=02 FV=0000000000000002
DRAM: 3GB SAMSUNGLP4x DIE=12Gb M5=01 M6=06 M7=00 M8=0E
Console[NULL]: null
Tools Mode Config: DISABLED
Power OK
oem_locked (before unlock)
flashing_unlocked (after unlock)
Software status: Official
Connect USB Data Cable (cable uncconected)
Transfer Mode: USB Connected (cable connected)
caain said:
I'd wait for mightysween to weigh in on this. I haven't flashed his modified boot.img myself yet, though I did unlock the device in preparation for it. I forgot unlocking erases all userdata so I'm setting the thing up again.
We think what we downloaded from the Moto server in the other thread is a complete firmware package for the current X4 Fi build. It is untested apart from the boot.img, to my knowledge. Did you by chance look at your 'About Phone' screen before this? I would specifically be interested in what was under "Software Variant", "Software Channel", and "build number". You mentioned previously that you purchased your X4 from Best Buy, so we may be working with different animals as there are several X4 variants. I am no developer, but it's possible that the stock boot.img files differ between variants.
---------- Post added at 12:19 AM ---------- Previous post was at 12:11 AM ----------
So my "Motorola version" under the "About Phone" heading does report NPW26.83-34-0-1. However, my build number reports NPW26.4. Is this what yours is reading? Software variant reads google_fi, software channel reads retus. I wonder if it wouldn't be a good idea to get a cross comparison on these figures from those with Amazon and Best Buy devices.
I've got cold feet on flashing the boot.img after hotpl8 ran into issues, but I'm wondering if it's due to the variant differences. The firmware we got from the Moto server is NPW26.83-34-0-1, baseband M660_7020.05.01.52.01R. It ought to work as a backup for Fi variants, but I'd hate to be the first one that flashes it. Just mailed my N6 back to Google yesterday, so I've got no backup.
Click to expand...
Click to collapse
build number: NPW26.4
MOTO Version: NPW26.83-34-0-1
Software channel: retus
Baseband Version: M660_7020.05.01.52.01 R PAYTON_NA_CUST
of course this is after I tried the method above. Not sure if this changed anything?
hotpl8 said:
build number: NPW26.4
MOTO Version: NPW26.83-34-0-1
Software channel: retus
Baseband Version: M660_7020.05.01.52.01 R PAYTON_NA_CUST
of course this is after I tried the method above. Not sure if this changed anything?
Click to expand...
Click to collapse
Probably not. But what does your "software variant" tag read?
Your moto version, baseband, and software channel are all identical to the Fi variant, it seems.
---------- Post added at 12:51 AM ---------- Previous post was at 12:48 AM ----------
DiDGR8 said:
For everybody worrying about the modified boot.img, I was able to flash it without issue and everything is running fine. Got Titanium BU and Root Explorer (and Busybox) running w/root privileges. Android Pay is borked, but unlocking the bootloader did that.
Click to expand...
Click to collapse
I gave it a whirl after setting up my phone again from the bootloader unlock. All went well after 2 or 3 reboots. My bootloader info looks the same as yours as well. I never used Android Pay anyway!
I posted on r/MotoX4 and r/Project Fi asking for "About Phone" info from the other variants. From hotpl8's comment it seems like the Best Buy variant is on the same build and baseband.
Has anyone seen anything in the firmware from the Moto server that suggests it is 100% Fi-specific? All I see is build and baseband references. I wonder if it could safely be used as a backup for all variants (assuming it is in fact intact).
caain said:
Probably not. But what does your "software variant" tag read?
Your moto version, baseband, and software channel are all identical to the Fi variant, it seems.
---------- Post added at 12:51 AM ---------- Previous post was at 12:48 AM ----------
I gave it a whirl after setting up my phone again from the bootloader unlock. All went well after 2 or 3 reboots. My bootloader info looks the same as yours as well. I never used Android Pay anyway!
I posted on r/MotoX4 and r/Project Fi asking for "About Phone" info from the other variants. From hotpl8's comment it seems like the Best Buy variant is on the same build and baseband.
Has anyone seen anything in the firmware from the Moto server that suggests it is 100% Fi-specific? All I see is build and baseband references. I wonder if it could safely be used as a backup for all variants (assuming it is in fact intact).
Click to expand...
Click to collapse
payton XT1900-1
Now I do not have much command on the SDK. My command prompt was letting me input and reboot but now I says its having an unknown error.
Where did you get the factory image for the Fi? Wonder if I can find the factory image for the non-fi variant
hotpl8 said:
I did as described above. And I got stuck on a boot loop left it for 15 min. or more I got back into fastboot and booted the boot.img again and it just kept reseting. I got into create an account and when I was done google play services wasnt working causing more issue. Is there a stock img that I can flash to get this back to stock>?
Is it the oem.img or am I into something worse here?
Click to expand...
Click to collapse
Just reading back through... I am not sure what the version from Best Buy is. This image was from the Project Fi version (which it says, in bold, at the top and bottom of the OP, where it also says not to flash it if you aren't familiar with the risks and getting yourself out of trouble)
If your firmware is the same as what is described in the OP, then just flash the stock boot.img from here:
https://drive.google.com/file/d/0ByZWXbOZqmVqbUV5T3ZvZEFBZ2M/view?usp=drivesdk
If not, then you will need to find yourself a factory image for whatever variant of the device you have.
hotpl8 said:
payton XT1900-1
Now I do not have much command on the SDK. My command prompt was letting me input and reboot but now I says its having an unknown error.
Where did you get the factory image for the Fi? Wonder if I can find the factory image for the non-fi variant
Click to expand...
Click to collapse
There is a 4+ page thread in this very forum about our struggles in trying to download the Project Fi variant factory image! I am not aware of any other factory images available at this time.