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.
Related
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
So far, fit and finish is outstanding. Better than a number of units that have gone through our hands in testing. (I'm keeping this one) Very, very little bloatware. But, not having root and the ability to write to SD etc is a PITA
Root was achieved using the method developed by social-design-concepts You will want to use the T4 trigger option. His thread is here. You will want to be sure that you use the download he mentions that are what he calls the public trial release, it's here
Glad to answer any questions about the device and follow up questions as well. I'm conversant with adp, etc.
Thanks!
Sent from my Venue 10 7040 using Tapatalk
Does this work on the latest Lollipop 5.1 firmware update?
Yes, it does.
How did you get the adb fastboot to work? I've installed the universal adb driver from http://androidxda.com/download-dell-usb-drivers but I still haven't gotten it to work.
I checked the Device Manager and the only unknown device is MTP.
Thanks!
I generally switch connection types to mass storage VS MTP and that makes it happen. Do remember that on occasion you have to specify the exact driver in device manager, Windows necessarily get it right. (Not being condescending mind you, just not sure where your skill level is at.)
I could use some help... After the T4 selection Fastboot Mode starts doing it's thing and attempting to copy over files but in the end it says Result: Fail (command now allowed in this device state) and I noticed the device state is Locked...
That's pretty straight forward. In short, your bootloader is still locked. Social design concept covers this well in his post. It's the first link in my original post. My apologies for the late reply. Been bringing up my Nexus devices to Marshmallow and dealing with all that.
Fearcher said:
That's pretty straight forward. In short, your bootloader is still locked. Social design concept covers this well in his post. It's the first link in my original post. My apologies for the late reply. Been bringing up my Nexus devices to Marshmallow and dealing with all that.
Click to expand...
Click to collapse
Hello Fearcher Congrats on rooting your 7040! Im in desperate need of your expertise. Trying to root my 7040 on L5.1
-installed drivers
-bootloader unlocked but text is in red?
-adb devices attached successfully
-fastboot devices found successfully
-have tried t4 on both tools with remote flashing to this partion error?
-tablets encryption is "encrypted"
Please help me root this tablet what am I missing?!
Is there anything about rooting 5.1 on a venue 10 that would prohibit future updates? I have read of rooted venue 8 users being unable to update to 5.1 after root but there was speculation that it was due to it being a 5.1 based root to begin with. I don't know enough about the details to know if this is plausible. This is the post I am reffering to: http://forum.xda-developers.com/showpost.php?p=64196214&postcount=15
I'd like to root but if it means no future updates that would be a deal breaker. Fearcher, you say this root method works on 5.1. Does this mean you had updated your tablet from 5.01 (rooted) to 5.1? If so did it require any special procedure or was it an OTA update? Thanks for you help
what driver do i need
Hello.
I've tried the ADB fastboot driver found in this thread and the stickied one. I've gone into device manager and selected several different drivers including the one named "dell adb fastboot" something which required me to turn off driver signature enforcement. Driver installed fine every time. When I launch the program I get the correct status message. Everything is right according to the instructions. I'm still getting the fail when it tries to install its files (command not allowed in this state).
What am i missing exactly? I've followed everything i can find in both this thread and the linked thread.
I have the latest 5.1 update from dell/google. I just bought the device from dell. My PC is Windows 10 64 bit if that matters. Driver signing is off.
Hey bro he hasn't been replying to any questions. Your bootloader is locked. I unlocked mine and it still don't work. From what I can gather you have to downgrade to kitkat then run Intel flash tool. We need a droidboot.zip file for flash tool but no one has helped. We need a package made from this site
---------- Post added at 07:06 PM ---------- Previous post was at 07:05 PM ----------
http://opensource.dell.com/releases/Venue_10_7040_Moorefield/developer-edition/
r_nation said:
Hey bro he hasn't been replying to any questions. Your bootloader is locked. I unlocked mine and it still don't work. From what I can gather you have to downgrade to kitkat then run Intel flash tool. We need a droidboot.zip file for flash tool but no one has helped. We need a package made from this site
---------- Post added at 07:06 PM ---------- Previous post was at 07:05 PM ----------
http://opensource.dell.com/releases/Venue_10_7040_Moorefield/developer-edition/
Click to expand...
Click to collapse
That's what I was thinking. is this because the 10 has a different chip than the smaller versions or something? It seems like they're having fun with their root and stuff. I thought moving to a device without a carrier would be easier. I have no idea why these are locked. it's nuts.
both models have same processor. It has to do with android 5.1 , they were able to root because there was kitkat firmware they could flash. Actually I don't even think my above method will work. We have to wait for an Intel based custom recovery for lollipop 5.1 but don't unlock your bootloader til there is one available.
whosloosin92 said:
I...
I'd like to root but if it means no future updates that would be a deal breaker. ...
Click to expand...
Click to collapse
Don't worry about future updates because they aren't coming. Dell killed off the Android dev team last year, so these are amazing but orphaned devices.
Are you sure?
bcjackson said:
Don't worry about future updates because they aren't coming. Dell killed off the Android dev team last year, so these are amazing but orphaned devices.
Click to expand...
Click to collapse
bc are you sure, who told you this? I am also a corporate customer of Dell, I am going to go to my SE and see what he saids. I am not doubting you, really hate to hear this actually. But I just find it hard to believe. But you and I know, it's all about the money. If they are not moving the 7040, then...bye, bye.
r_nation said:
Hey bro he hasn't been replying to any questions. Your bootloader is locked. I unlocked mine and it still don't work. From what I can gather you have to downgrade to kitkat then run Intel flash tool. We need a droidboot.zip file for flash tool but no one has helped. We need a package made from this site
---------- Post added at 07:06 PM ---------- Previous post was at 07:05 PM ----------
http://opensource.dell.com/releases/Venue_10_7040_Moorefield/developer-edition/
Click to expand...
Click to collapse
Do tell if u are able to root it in 5.1
They have enabled encryption by default so it would be tough
I don't want to go back to 4.4 :c
That opensource firmware is lollipop. There is literally no development for venue 10 7000 root is still impossible.
Just wanted to report in that I successfully rooted my 7040 today using the social-designs-concepts method mentioned in the first post of this thread with IntelAndroid-FBRL-07-24-2015.7z (had attempted to use the recommended IntelAndroid-FBRL 05-16-2015 Public Trail Release but Windows 10 AV kept quarantining it due to detected trojan malware). SuperSU Free v2.76 is installed successfully.
FWIW, I did this on a refurb 32GB 7040 that I purchased online for US$216 (as my 16GB one has become to precious to experiment with). I did not allow the system to connect to networks before rooting, and it is on Android 5.0.2. I'm not sure if that affected the success of rooting; I just wanted to report clearly what I did. Please note that after rooting automatic firmware updates to 5.1 failed. Will undo the rooting and try again after 5.1 update.
The expanded memory will be useful, as well as the ability to extend "internal" to include the external SD card.
Now if I could just figure out how to put Nougat on this thing I would be ecstatic.
rcbarr said:
bc are you sure, who told you this? I am also a corporate customer of Dell, I am going to go to my SE and see what he saids. I am not doubting you, really hate to hear this actually. But I just find it hard to believe. But you and I know, it's all about the money. If they are not moving the 7040, then...bye, bye.
Click to expand...
Click to collapse
Dell now confirming that they are discontinuing Android lines and will not provide further updates.
http://www.pcworld.com/article/3090466/android/dell-stops-selling-android-devices.html
bcjackson said:
Just wanted to report in that I successfully rooted my 7040 today using the social-designs-concepts method mentioned in the first post of this thread with IntelAndroid-FBRL-07-24-2015.7z (had attempted to use the recommended IntelAndroid-FBRL 05-16-2015 Public Trail Release but Windows 10 AV kept quarantining it due to detected trojan malware). SuperSU Free v2.76 is installed successfully.
FWIW, I did this on a refurb 32GB 7040 that I purchased online for US$216 (as my 16GB one has become to precious to experiment with). I did not allow the system to connect to networks before rooting, and it is on Android 5.0.2. I'm not sure if that affected the success of rooting; I just wanted to report clearly what I did. Please note that after rooting automatic firmware updates to 5.1 failed. Will undo the rooting and try again after 5.1 update.
The expanded memory will be useful, as well as the ability to extend "internal" to include the external SD card.
Now if I could just figure out how to put Nougat on this thing I would be ecstatic.
Click to expand...
Click to collapse
So the baseline is that u cannot root once you upgrade to 5.1?
---------- Post added at 02:15 PM ---------- Previous post was at 02:09 PM ----------
bcjackson said:
Just wanted to report in that I successfully rooted my 7040 today using the social-designs-concepts method mentioned in the first post of this thread with IntelAndroid-FBRL-07-24-2015.7z (had attempted to use the recommended IntelAndroid-FBRL 05-16-2015 Public Trail Release but Windows 10 AV kept quarantining it due to detected trojan malware). SuperSU Free v2.76 is installed successfully.
FWIW, I did this on a refurb 32GB 7040 that I purchased online for US$216 (as my 16GB one has become to precious to experiment with). I did not allow the system to connect to networks before rooting, and it is on Android 5.0.2. I'm not sure if that affected the success of rooting; I just wanted to report clearly what I did. Please note that after rooting automatic firmware updates to 5.1 failed. Will undo the rooting and try again after 5.1 update.
The expanded memory will be useful, as well as the ability to extend "internal" to include the external SD card.
Now if I could just figure out how to put Nougat on this thing I would be ecstatic.
Click to expand...
Click to collapse
So the baseline is that u cannot root once you upgrade to 5.1?
well now that they have abandoned android maybe they will release the open source?:crying:
FOR MOTO G7 PLUS ONLY!!!
Hello, everyone.
I created a .bat file "executable " For those who want to flash the stock rom on your Moto G7 Plus.
Just put it in the stock Rom folder along with the fastboot files and run the file.
For those who want the file, just download it by the following link or download the file that is on the thread.
http://www.mediafire.com/file/q836uaerr17pn0f/Flash_ROM_G7%252B.zip/file
Could you share where to get the Stock ROM fein?
---------- Post added at 11:13 PM ---------- Previous post was at 10:25 PM ----------
Tried the same sequence with a Stock ROM last week, but didn't achieve to get back to original ROM. I always get the prompt in the initial boot, that a different OS is installed than the original. This has the consequence that I cannot upgrade wit OTA anymore. And there is an upgrade already available (Jan security patch)
moto g7 G7........
any one have a flash rom.bat stock rom for moto g7.......
Which stock rom did you flash on your Moto g7 plus?
Where can I find the stock rom?
Nes.
NesNol said:
Where can I find the stock rom?
Nes.
Click to expand...
Click to collapse
Didn't you just find it yesterday on the telegram group?
What was the problem that you asked again here today?
Latest Stock ROM RETAIL at that link is the one we have all been using.
You'll need to download it to a computer, unzip it in a folder with the fastboot/ADB files, then fastboot flash it with phone attached in bootloader mode.
NesNol said:
Where can I find the stock rom?
Nes.
Click to expand...
Click to collapse
You have a model of the XT1965-3 smartphone and region of the software is reteu? Then this your last firmware.
"Your device has loaded a different operating system."
baikal0912 said:
You have a model of the XT1965-3 smartphone and region of the software is reteu? Then this your … .
Click to expand...
Click to collapse
Thank you very much!
I guess that the software channel was reteu.
A second moto g7 phone I bought - and is unmodified - says "software channel: reteu".
The information on the package of my phone says XT1965-3.
I flashed this image already, the result is a 'working' system except for the message at the start "Your device has loaded a different operating system." .
NesNol said:
Thank you very much!
I guess that the software channel was reteu.
A second moto g7 phone I bought - and is unmodified - says "software channel: reteu".
The information on the package of my phone says XT1965-3.
I flashed this image already, the result is a 'working' system except for the message at the start "Your device has loaded a different operating system." .
Click to expand...
Click to collapse
This will get rid of that message we all got too:
[Bootlogo] Modded Bootlogo from unlocked bootloader
The new RETEU stock version was just updated in last few days, before that not available and you could have used the RETAIL channel that I mentioned above, it worked fine for several users on RETEU channel.
Dahenjo said:
This will get rid of that message we all got too:
The new RETEU stock version was just updated in last few days, before that not available and you could have used the RETAIL channel that I mentioned above, it worked fine for several users on RETEU channel.
Click to expand...
Click to collapse
Get rid of the message?
Does that also mean that OTAs will work? That banking apps will not complain about the integrity of the system?
Thanks!
NesNol said:
Get rid of the message?
Click to expand...
Click to collapse
Yes, you said: except for the message at the start "Your device has loaded a different operating system."
After unlocking bootloader there is some message like this on starting device, keep in mind we all got these too and everything is fine but we like to cover it up with a different bootlogo, just looks better that is its only purpose. This message is because you also upgraded the firmware, meaning it's not really a different OS but only a different version of your correct OS.
Does that also mean that OTAs will work? That banking apps will not complain about the integrity of the system?
Click to expand...
Click to collapse
For G7 Plus we are not getting the OTAs properly after unlocking or rooting, I was originally rooted on PPW29.98-28 and repeatedly got the notifications of upgrading to 29.98-66-2 but it kept failing, the only way to stop it was freezing the Moto Update Process using Titanium Backup. So my only remaining option to upgrade was to fastboot flash the full firmware, as you just did, it wipes your data but gets you to the same place.
With future updates we may be able to capture them and then a dev can make them into a TWRP flashable zip with no wiping of internal data. We had that on G5 Plus which was a nice thing and they are still doing that. But until that might happen the best we can do is the same for now - when your channel has an update just get it from lolinet (these are all official stock firmwares there) and fastboot flash after backing up your data.
Usually it is more from the rooting (if you did that too) that may mess up your banking or other apps, but in Magisk there are settings that may work on that, you'll just have to try and see but there are mixed results. My choice is to not use banking apps on my devices anyway even if not unlocked or rooted, I just do it from home on a computer that I won't forget and leave out in public somewhere. :crying:
Dahenjo said:
Yes, you said: except for the message at the start "Your device has loaded a different operating system."
…
…
Click to expand...
Click to collapse
Hi,
thank you very much for your elaborate answer!
I will come back on it soon.
Nes
Dahenjo said:
Yes, you said: except for the message at the start "Your device has loaded a different operating system."
After unlocking bootloader there is some message like this on starting device, keep in mind we all got these too and everything is fine but we like to cover it up with a different bootlogo, just looks better that is its only purpose. This message is because you also upgraded the firmware, meaning it's not really a different OS but only a different version of your correct OS.
For G7 Plus we are not getting the OTAs properly after unlocking or rooting, I was originally rooted on PPW29.98-28 and repeatedly got the notifications of upgrading to 29.98-66-2 but it kept failing, the only way to stop it was freezing the Moto Update Process using Titanium Backup. So my only remaining option to upgrade was to fastboot flash the full firmware, as you just did, it wipes your data but gets you to the same place.
With future updates we may be able to capture them and then a dev can make them into a TWRP flashable zip with no wiping of internal data. We had that on G5 Plus which was a nice thing and they are still doing that. But until that might happen the best we can do is the same for now - when your channel has an update just get it from lolinet (these are all official stock firmwares there) and fastboot flash after backing up your data.
Usually it is more from the rooting (if you did that too) that may mess up your banking or other apps, but in Magisk there are settings that may work on that, you'll just have to try and see but there are mixed results. My choice is to not use banking apps on my devices anyway even if not unlocked or rooted, I just do it from home on a computer that I won't forget and leave out in public somewhere. :crying:
Click to expand...
Click to collapse
So you expect that in future my phone will be OK again? And receive OTAs while having Magisk installed.
I tried indeed to Magisk my phone, as I did with my old OnePlus One.
Which leads to TWRP, but then I discovered that the recovery has disappeared on this Moto!?
Then I was lost, and read about A/B and treble(?).
Concerning the banking applications: Even if I handle the banking transactions on my Mac, I still need the banking app on my phone for authentication.
Which is also true for accessing my medical data (GP, hospitals, etc), insurance companies, taxes, etc.
Last question: Is there a full description of how to magisk my phone?
Dahenjo said:
Yes, you said: except for the message at the start "Your device has loaded a different operating system."
…
…
…
…
Click to expand...
Click to collapse
I have replied to this messages twice.
None has arrived?!
Nes
---------- Post added at 01:34 PM ---------- Previous post was at 01:33 PM ----------
Dahenjo said:
Yes, you said: except for the message at the start "Your device has loaded a different operating system."
…
…
…
…
Click to expand...
Click to collapse
I have replied to this message twice.
None has arrived?!
Nes
NesNol said:
So you expect that in future my phone will be OK again? And receive OTAs while having Magisk installed.
I tried indeed to Magisk my phone, as I did with my old OnePlus One.
Which leads to TWRP, but then I discovered that the recovery has disappeared on this Moto!?
Then I was lost, and read about A/B and treble(?).
Concerning the banking applications: Even if I handle the banking transactions on my Mac, I still need the banking app on my phone for authentication.
Which is also true for accessing my medical data (GP, hospitals, etc), insurance companies, taxes, etc.
Last question: Is there a full description of how to magisk my phone?
Click to expand...
Click to collapse
Sorry not to reply yet, I sometimes have other things going on besides my phone. Also I thought I gave you a good answer on the situation, based on what I know as just another user (not a dev, not with Moto).
Yes, there have been changes since your last phone, it was the same for me. So it's good to find out as much as possible before deciding to unlock & root again, because the results may not be like before. We used to unlock and flash TWRP directly but we can't do that now or maybe brick the phone. It is always the risk when choosing not to remain fully stock/locked/etc as when you bought it, and with that is a responsibility to do the research first and not just expect other users to tell you every step.
So I don't know if things will change, but for now we can't get OTAs anymore after unlocking. For me I didn't mind and I am willing to upgrade manually if that let's me work with the device the way I like with root & using custom ROMs etc. I didn't plan to ever go back to how I bought it and don't need banking apps or other types that rooting might mess up. For others that may not be the case so they must learn the situation then decide for themselves.
As for installing Magisk, now we have TWRP working enough to just put the Magisk zip on your SD card and install it in TWRP. Before we had a functional TWRP we had another method by installing Magisk Manager and using it to patch the boot.img then fastboot flash that, but it's not needed anymore since TWRP, just do it the old way now.
Flashing the roms from lolinet, in my case ( RETEU[/URL) is a complete reset of the phone, I assume.
To flash, these steps should be right:
Copying the firmware to sdcard.
Boot in TWRP
Flashing the lolinet firmware.
Delete Dalvik Cache.
Should TWRP and Magisk be reinstalled immedeately after this procedure? Or renew the developer mode, reinstall twrp and magisk?
Woif said:
Flashing the roms from lolinet, in my case RETEU is a complete reset of the phone, I assume.
To flash, these steps should be right:
Copying the firmware to sdcard.
Boot in TWRP
Flashing the lolinet firmware.
Delete Dalvik Cache.
Should TWRP and Magisk be reinstalled immedeately after this procedure? Or renew the developer mode, reinstall twrp and magisk?
Click to expand...
Click to collapse
It won't work to flash full firmware in TWRP, so far the only way is using fastboot with phone connected to a computer in bootloader (unlocked) mode. Unzip firmware into your fastboot/ADB folder and also the batch file available in this thread, then run the batch file.
Yes this will reset/wipe your phone (except for SD) so backup your data first, and it will be like when you first bought it. You can reinstall TWRP and then Magisk, but boot to system first and set things up including enabling USB debugging setting in developer options again.
I am going to try and update now as the notifications are much too annoying.
Moto G7 Plus - lake Stock rom / firmware download here
NesNol said:
Where can I find the stock rom?
Nes.
Click to expand...
Click to collapse
Moto G7 Plus - lake
Download the Moto G7 Plus - lake stock firmware according to the Country/region/retail/carrier for example US Retail > T-Mobile, Verizon or Amazon, and everything is flashed through fastboot mode
XT1965-2 > https://boycracked.com/2019/02/11/official-motorola-moto-g7-plus-xt1965-2-stock-rom/
XT1965-3 > https://boycracked.com/2019/02/11/official-motorola-moto-g7-plus-xt1965-3-stock-rom/
XT1965-4 > https://boycracked.com/2019/02/11/official-motorola-moto-g7-plus-xt1965-4-stock-rom/
XT1965-6 > https://boycracked.com/2019/07/26/official-motorola-moto-g7-plus-xt1965-6-lake_retcn-stock-rom/
XT1965-9 > https://boycracked.com/2019/07/26/official-motorola-moto-g7-plus-xt1965-9-lake-stock-rom/
XT1965-T > https://boycracked.com/2019/07/26/o...-g7-plus-xt1965-t-lake-us-t-mobile-stock-rom/
Remove the line
'fastboot erase userdata'
from the flashROM.bat file and it won't factory reset. It will act like an upgrade.
Sent from my Moto Z (2) using XDA Labs
vickbuitenzorg said:
Moto G7 Plus - lake
Download the Moto G7 Plus - lake stock firmware according to the Country/region/retail/carrier for example US Retail > T-Mobile, Verizon or Amazon, and everything is flashed through fastboot mode
Click to expand...
Click to collapse
Can I use a different retail code than current stock? My phone is XT1965-2, PPW29.98-28, RETLA. The system reminders are all in Spanish. Could I update to PPW29.98-66, EEGB (UK English) without a problem?
Also, if this is possible, could I update by removing the 'fastboot erase userdata' line from the BAT file, or, due to the language change, would I need to leave that line and do a factory reset?
This is a long-shot but essential if we're going to mess around with this phone with any degree of confidence or YOLO. Without this, there is no experimenting with global non-5G 7T Pro roms and partitions. The MSM for the OP7 Pro 5G for EE and Sprint never leaked, but that was a low-key phone. Let's do better with the T-Mobile McLaren.
Your mission is simple: Obtain the MSMDownloadTool and ops file (usually packaged together in a password-protected rar). You need that package and the password. These are device specific. Don't really care how the files are ultimately delivered as long as there's no encryption. Any info about the file or URL (e.g. https://s3.amazonaws.com/oneplussupport/...) is welcome.
I hate bounties or the thought of enforcing one, but expect donations if you succeed and avail yourself. Anonymity is also acceptable.
If you happen to find something we don't expect like global firmware for this phone, there's a separate bounty thread for that. I doubt it exists.
Relevant codenames and identifiers for our device:
HD1925
hotdogg
oneplus7tpronroxygen
HD61CB
I think @ddggttff3 asked them for this and they wouldn't send it to him for some reason. Maybe they misunderstood what he was asking for? A stock MSM image is just stock, so it doesn't make sense to not release it on XDA. It seems wasteful for a company to have to do extra remote recovery sessions when simply releasing a stock MSM image on XDA could save a company extra time and money.
I also asked OnePlus https://www.oneplus.com/support/contact for a MSM image for the OnePlus 7T Pro 5G McLaren, since it's critical for safe development. In my case, they did not say no, they just gave me a boilerplate response of, "About your concern we would like to inform you that we will take this as feedback and pass it along to our developer team so that this update can be rectified in the upcoming updates in the near future." They emailed me again asking for a further response and I haven't replied yet, because that second email was more obviously automated and did not have a name like the first one did. I think they could possibly let a tech post it to XDA, etc., if convinced by someone with experience like a XDA Recognized Developer.
jhofseth said:
I also asked OnePlus https://www.oneplus.com/support/contact for a MSM image for the OnePlus 7T Pro 5G McLaren, since it's critical for safe development. In my case, they did not say no, they just gave me a boilerplate response of, "About your concern we would like to inform you that we will take this as feedback and pass it along to our developer team so that this update can be rectified in the upcoming updates in the near future." They emailed me again asking for a further response and I haven't replied yet, because that second email was more obviously automated and did not have a name like the first one did. I think they could possibly let a tech post it to XDA, etc., if convinced by someone with experience like a XDA Recognized Developer.
Click to expand...
Click to collapse
I just got off a chat with an agent and they tell me I'll get a remote session with their technical team in 24-48 hours I'm gonna do my best to get the image/ password for you guys
tserv95 said:
I just got off a chat with an agent and they tell me I'll get a remote session with their technical team in 24-48 hours I'm gonna do my best to get the image/ password for you guys
Click to expand...
Click to collapse
Did it work out?
Still waiting from then
They never follow up. I'm still waiting a week later
LLStarks said:
They never follow up. I'm still waiting a week later
Click to expand...
Click to collapse
Same here, been about four days!
Unlucky. OnePlus is being pretty crappy with their service.
https://www.oneplus.com/support/contact has 3 contact options: phone (Call us +1 (833) 777-3633 7x24 hours), live chat and email. I really think a XDA Recognized Developer might have some luck getting a MSM image for the OnePlus 7T Pro 5G McLaren. There is a legitimate safe development need for this and providing it only benefits OnePlus and T-Mobile. The squeaky wheel gets the grease!
Barring actually getting the MSM I may have a method of recovery using fastboot and friends. However, I need the help of
a hotdogg owner with stock firmware & unlocked bootloader. The method is non-destructive (aside from the unlocking nuking
your data); just requires you to use fastboot to boot a twrp image and use adb to pull a partition (its 15gb, so to make it faster
you may want to use a real usb-c 3.0 cable; I don't think the orange one that comes with it is) and unpack it with a tool
called 'lpunpack' (unfortunately I don't know how to build it outside of an aosp/lineageos/grapheneos tree yet).
bad news, after waiting for days for a response from Oneplus, I decided to phone them. They state that after speaking to the remote support team, they cannot even help us. As they apparently don't have the images for the T-Mobile firmware either/ firmware for the Mclaren edition. This is a big bummer as until they (if they for that matter) release the firmware on support site we have no way of really recovering a bricked device and any firmware flashing is gonna be very dangerous to attempt. So yeah.. really regretting buying a T-Mobile variant Oneplus phone atm.
tserv95 said:
bad news, after waiting for days for a response from Oneplus, I decided to phone them. They state that after speaking to the remote support team, they cannot even help us. As they apparently don't have the images for the T-Mobile firmware either/ firmware for the Mclaren edition. This is a big bummer as until they (if they for that matter) release the firmware on support site we have no way of really recovering a bricked device and any firmware flashing is gonna be very dangerous to attempt. So yeah.. really regretting buying a T-Mobile variant Oneplus phone atm.
Click to expand...
Click to collapse
So, does T-Mobile flash the final firmware after OnePlus ships it to the US or something? If the firmware isn't finally flashed until it gets to the US, then that might make sense; but, if not, someone there could either be mistaken or less than truthful.
---------- Post added at 11:24 AM ---------- Previous post was at 10:54 AM ----------
Maybe this will be a good avenue for us? https://twitter.com/tmobilehelp
tserv95 said:
bad news, after waiting for days for a response from Oneplus, I decided to phone them. They state that after speaking to the remote support team, they cannot even help us. As they apparently don't have the images for the T-Mobile firmware either/ firmware for the Mclaren edition. This is a big bummer as until they (if they for that matter) release the firmware on support site we have no way of really recovering a bricked device and any firmware flashing is gonna be very dangerous to attempt. So yeah.. really regretting buying a T-Mobile variant Oneplus phone atm.
Click to expand...
Click to collapse
Do you currently have one in an unflashed (to anything other than stock), unlocked state? If so I can probably guide you through how we can get a sort of
flashable stock image (flashed over fastboot). Hit me up if you are in that situation (sim unlocked, bootloader unlocked, and otherwise stock firmware).
---------- Post added at 11:50 AM ---------- Previous post was at 11:27 AM ----------
jhofseth said:
So, does T-Mobile flash the final firmware after OnePlus ships it to the US or something? If the firmware isn't finally flashed until it gets to the US, then that might make sense; but, if not, someone there could either be mistaken or less than truthful.
---------- Post added at 11:24 AM ---------- Previous post was at 10:54 AM ----------
Maybe this will be a good avenue for us? https://twitter.com/tmobilehelp
Click to expand...
Click to collapse
Quite possible. I don't recall offhand but I believe mine came to me with version 10.0.14, and after 'recovering' from
flashing an experimental lineageos build on mine I ended up on version 10.0.13, which may be sort of the last common
ancestor for all the variants, and its now unable to OTA (it wants to go to 10.0.16, but as an incremental update it
can only jump versions 'in the correct order').
ntzrmtthihu777 said:
Barring actually getting the MSM I may have a method of recovery using fastboot and friends. However, I need the help of
a hotdogg owner with stock firmware & unlocked bootloader. The method is non-destructive (aside from the unlocking nuking
your data); just requires you to use fastboot to boot a twrp image and use adb to pull a partition (its 15gb, so to make it faster
you may want to use a real usb-c 3.0 cable; I don't think the orange one that comes with it is) and unpack it with a tool
called 'lpunpack' (unfortunately I don't know how to build it outside of an aosp/lineageos/grapheneos tree yet).
Click to expand...
Click to collapse
Getting my device tomorrow, but will obviously have to get it sim unlocked first, then wait the week for the OnePlus token to unlock the bootloader. But once I am at that point, I would happily do this if it could possibly lead to an alternate fastboot recovery method if no one is able to get the MSM tool. Obviously if anyone else can do this before I am able to, please do
ntzrmtthihu777 said:
Do you currently have one in an unflashed (to anything other than stock), unlocked state? If so I can probably guide you through how we can get a sort of
flashable stock image (flashed over fastboot). Hit me up if you are in that situation (sim unlocked, bootloader unlocked, and otherwise stock firmware).
Click to expand...
Click to collapse
I was wondering what particular device was mounted root, so I did: cat /proc/mounts
Apparently, / is /dev/block/dm-8
This is why TWRP is taking so long for Android 10: https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
"Android 10 also introduces a new dynamic partitioning system. Instead of having a dedicated system partition and a dedicated vendor partition, etc. Android 10 uses a super partition. I like to think of the super partition as a partition that contains a bunch of smaller partitions. One of the side effects of this dynamic partition system is that Google has chosen to use a form of the ext4 file system that is for all intents and purposes, read-only. This choice means that even if you wanted to, you can't easily mount and modify the system partition. We haven't really discussed this with other developers yet, but it may impact your ability to do things like install Gapps. In addition, the dynamic partition model means that eventually, we should probably provide you, the user, some GUI driven tools in TWRP to allow you to manage the dynamic partitions that are on the super partition." @Dees_Troy
jhofseth said:
I was wondering what particular device was mounted root, so I did: cat /proc/mounts
Apparently, / is /dev/block/dm-8
Click to expand...
Click to collapse
Yeah, but / is not terribly important compared to /system, /vendor, and /product (it is important tho)
jhofseth said:
This is why TWRP is taking so long for Android 10: https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
Click to expand...
Click to collapse
Yeah, but twrp is not incredibly essential to the backup/restore process I've theorized about (still not sure about how it would work
in practice), just needed to get something to boot with root available without actually changing the stock firmware (by installing
magisk and such) in order to be able to pull the stock data.
---------- Post added at 12:38 PM ---------- Previous post was at 12:35 PM ----------
jhofseth said:
"Android 10 also introduces a new dynamic partitioning system. Instead of having a dedicated system partition and a dedicated vendor partition, etc. Android 10 uses a super partition. I like to think of the super partition as a partition that contains a bunch of smaller partitions. One of the side effects of this dynamic partition system is that Google has chosen to use a form of the ext4 file system that is for all intents and purposes, read-only. This choice means that even if you wanted to, you can't easily mount and modify the system partition. We haven't really discussed this with other developers yet, but it may impact your ability to do things like install Gapps. In addition, the dynamic partition model means that eventually, we should probably provide you, the user, some GUI driven tools in TWRP to allow you to manage the dynamic partitions that are on the super partition." @Dees_Troy
Click to expand...
Click to collapse
Yeah. This super partition is what I'm interested in. Once you copy it from the device (using adb pull /dev/block/.../super super.img)
you can extract it into its subpartitions using lpunpack. I believe one would be able to flash its subpartitions using fastboot in order
to recover from either a bad flash or a bad restore (like I and another user have, which left us on 10.0.13).
/dev/block/bootdevice/by-name/super
I made an image of super and file info reads 14.0 GiB (15,032,385,536).
That super.img compresses down to about 4.6 GiB in a regular zip file.
https://source.android.com/devices/tech/ota/dynamic_partitions/implement
jhofseth said:
/dev/block/bootdevice/by-name/super
I made an image of super and file info reads 14.0 GiB (15,032,385,536).
That super.img compresses down to about 4.6 GiB in a regular zip file.
https://source.android.com/devices/tech/ota/dynamic_partitions/implement
Click to expand...
Click to collapse
Nice, nice. Yeah. that's to be expected. I think with that file I and dandroid would be able to restore our phones, assuming
that's stock firmware. Potentially others. Do you have a reliable means to share the file, if you're willing to? Per the link you
posted it contains no userdata so it should be safe to share.
Are we expecting the global version to have the ability to be bootloader unlocked? Looking at the recent Motorola devices, they seem that most can be unlocked and kernel sources are published.
My Motorola edge plus from Verizon actually has the toggle for bootloader unlocking. I am kind of shocked!
droidnew said:
My Motorola edge plus from Verizon actually has the toggle for bootloader unlocking. I am kind of shocked!
Click to expand...
Click to collapse
It's not unusual for Moto phones on Verizon to show but it doesn't mean it actually works.
Hey this is just a question. Has anybody tried Google there is a ton of information about unlocking the bootloader.. I'm reading some of the info now. I'm debating on getting this phone or the OnePlus 8 pro. I'm kinda stuck with Verizon right now that's why the 8 pro from OnePlus looked real good. But reading about edge + and getting the unlock code from motorola it looks good too.
droidnew said:
My Motorola edge plus from Verizon actually has the toggle for bootloader unlocking. I am kind of shocked!
Click to expand...
Click to collapse
Were you able to confirm that the toggle functions?
rodken said:
Were you able to confirm that the toggle functions?
Click to expand...
Click to collapse
The toggle does function. But I haven't tried to unlock the bootloader. But if I toggle it on it does give me a warning about unlocking. I actually returned the phone as I was not satisfied with the camera. I have 2 grand kids and I found enough situations where the camera took pictures that were a little blurry that I didn't feel like I needed to keep the phone. I hated to do it, I really liked the phone, but the camera was a deal breaker.
droidnew said:
The toggle does function. But I haven't tried to unlock the bootloader. But if I toggle it on it does give me a warning about unlocking. I actually returned the phone as I was not satisfied with the camera. I have 2 grand kids and I found enough situations where the camera took pictures that were a little blurry that I didn't feel like I needed to keep the phone. I hated to do it, I really liked the phone, but the camera was a deal breaker.
Click to expand...
Click to collapse
I think that you just gave me hope in that if I decide to purchase one shortly, that the toggle will still be available to unlock the bootloader.
Question: Assuming that the toggle will still unlock the bootloader, I would not have a need for any fastboot mode command lines?
Hey Guy I just picked this device up straight from Verizon , it came today and I already checked off OEM UNLOCK. I wanted to even see if it depended on sim so...I am coming from an LG V60 and when I got the new phone I just simply activated with the sim it came with went straight to developer options to see if it was greyed out. It wasn't I checked it off and I went to the Motorola page and checked to see if my device could be unlocked which it could and I got my unique key and submitted it. It said I should be getting the email with the unlock key for Fastboot. However it doesn't look like there is factory images but I am willing to test stuff while I have a backup phone and also since I am in my return period.
daillcyruz said:
Hey Guy I just picked this device up straight from Verizon , it came today and I already checked off OEM UNLOCK. I wanted to even see if it depended on sim so...I am coming from an LG V60 and when I got the new phone I just simply activated with the sim it came with went straight to developer options to see if it was greyed out. It wasn't I checked it off and I went to the Motorola page and checked to see if my device could be unlocked which it could and I got my unique key and submitted it. It said I should be getting the email with the unlock key for Fastboot. However it doesn't look like there is factory images but I am willing to test stuff while I have a backup phone and also since I am in my return period.
Click to expand...
Click to collapse
Please keep me posted on whether the email with the fastboot commands holds true and are you looking for factory images for testing purposes or couldn't you just run with the device as-is until the images materialize?
rodken said:
Please keep me posted on whether the email with the fastboot commands holds true and are you looking for factory images for testing purposes or couldn't you just run with the device as-is until the images materialize?
Click to expand...
Click to collapse
I will keep posted, yes I wouldn't try anything until factory images are available. I wanted to see if it was really going to let me go through with requesting the lock... I thought the email would be fast but its been 30 min no email yet.
daillcyruz said:
I will keep posted, yes I wouldn't try anything until factory images are available. I wanted to see if it was really going to let me go through with requesting the lock... I thought the email would be fast but its been 30 min no email yet.
Click to expand...
Click to collapse
Unlocking the bootloader should not interfere with the overall operability of the device, e.g., text, calls, data, etc. Is there a reason as to why you are waiting for factory images before unlocking?
rodken said:
Unlocking the bootloader should not interfere with the overall operability of the device, e.g., text, calls, data, etc. Is there a reason as to why you are waiting for factory images before unlocking?
Click to expand...
Click to collapse
No no not not waiting to unlock, yes I am going to that as soon as I get the Code I mean roms if any devs put something out there...However I will be willing to try some stuff lol...
---------- Post added at 05:39 PM ---------- Previous post was at 04:42 PM ----------
For kicks and giggles I downloaded Lenovos Mobile program for backup and recovery to see if it would have a rescue function that would pull down a full image..And Wa La looks like it did. You have to connect your phone first and then go to rescue and it pulled down a 2.5GB Imaged named...
Burton_VZW_QPB30.188_43_subsidy_VZW_RSU_QCOM_regulatory_default_CFc.XML.ZIP
edgeplus by Chaz Chamberlain, on Flickr
Full download for the 2.5GB File here..
https://drive.google.com/drive/folders/11YXi-3arbpDbPy8Rjz6Ub1GShqMzibx3?usp=sharing
daillcyruz said:
No no not not waiting to unlock, yes I am going to that as soon as I get the Code I mean roms if any devs put something out there...However I will be willing to try some stuff lol...
---------- Post added at 05:39 PM ---------- Previous post was at 04:42 PM ----------
For kicks and giggles I downloaded Lenovos Mobile program for backup and recovery to see if it would have a rescue function that would pull down a full image..And Wa La looks like it did. You have to connect your phone first and then go to rescue and it pulled down a 2.5GB Imaged named...
Burton_VZW_QPB30.188_43_subsidy_VZW_RSU_QCOM_regulatory_default_CFc.XML.ZIP
edgeplus by Chaz Chamberlain, on Flickr
Full download for the 2.5GB File here..
https://drive.google.com/drive/folders/11YXi-3arbpDbPy8Rjz6Ub1GShqMzibx3?usp=sharing
Click to expand...
Click to collapse
Wait..... are you still waiting for the code by email or did you receive the code and now waiting for a ROM to be developed?
Still waiting on code
Here's a magisk patched boot img.
Boot it with fastboot when you have unlocked the bootloader:
Code:
fastboot boot magisk_patched.img
nilezon said:
Here's a magisk patched boot img.
Boot it with fastboot when you have unlocked the bootloader:
Code:
fastboot boot magisk_patched.img
Click to expand...
Click to collapse
Do I still need to obtain a copy of the stock boot/recovery image as required or do I simply flash the patched boot img you have supplied?
---------- Post added at 09:44 AM ---------- Previous post was at 09:21 AM ----------
daillcyruz said:
Still waiting on code
Click to expand...
Click to collapse
I read an article that the unlock code is obtained from the supplier within a maximum period of 24 business hours, although there are cases where this could take anywhere from one hour up to three business days. Other times, the code is provided in less than 15 minutes. It depends on the make and model of the phone and the original network provider. What - 3 days?
I don't have the phone myself, so I can't say for sure what works or not. But usually, when bootloader is unlocked, you can boot or flash a patched boot.img to obtain root.
I patched the boot.img from the rom dump supplied by @daillcyruz
You should start with the "fastboot boot" command i wrote, as that command won't modify anything permanently.
EDIT:
Any news on that unlock code from Motorola yet?
nilezon said:
I don't have the phone myself, so I can't say for sure what works or not. But usually, when bootloader is unlocked, you can boot or flash a patched boot.img to obtain root.
I patched the boot.img from the rom dump supplied by @daillcyruz
You should start with the "fastboot boot" command i wrote, as that command won't modify anything permanently.
EDIT:
Any news on that unlock code from Motorola yet?
Click to expand...
Click to collapse
Thanks for supplying the patched img. I guess we'll have to wait on the response from @daillcyruz regarding receipt of the code.
Hey still waiting for the code.
daillcyruz said:
Hey still waiting for the code.
Click to expand...
Click to collapse
I imagine you'll be waiting a long time but I may be surprised. Toggling a switch means nothing when it comes to Verizon.