Related
Hello fellas,
After a long time I've decided to be back on Nexus, can't enjoy without nexus phones, ZF2 developement is stagnant as ASUS is not releasing src, a great HW stuck by OEM limtations.
So I've got my N6 today, I've learnt a few things before like not downgrading bootloader, had a post saying which versions are safe and ones that are not iirc <71.08 shouldn't be flashed onto 71.08 existing BL right or was it 71.10 ?? (idk why will anyone want to downgrade unless they want OTAs based on Fi, root is superior to all. Heard a few CM roms had BL packed into ROMs and the updte to 5.1.x + lower BL caused hardbrick, a.k.a bootloop + noTWRP with Fastboot lockedout ).
So here's my to-do list sorry to post this long but seems like this is start for me....Please correct me If I understood anthing wrong....as It's been a long time since I used a nexus (Maguro was my first nexus and things rapidly changed these days..)
1 - mFastboot for flashing
2 - OEM unlock check prior to unlock the phone (shipped with 5.1 LMY47D so I may need to do this before proceeding)
A few questions -
3 - Does NRT has mFastboot ? I have it in my computer tho.
4 - Can any one give me crash course for SuperSU + MultiROM with 5.1.1 (Need Xposed:silly, 6.x & Nexus 6 information....
a- Like If I OEM unlock my n6 now and use 5.1.1 CM based it has pre-root right ? So I shouldn't bother with SuperSU BETA 2.6x right, next is the systemless root is because of M's warning messages ? why all this hassle of
**root** as of lately with L and M, Is it because of SELinux policies + M's changes with System related messages ?
b - MultiROM working guide on 5.1.1 plus M latest release anyone, will try the official thread tho, any info on whre to start would be awesome !!
5- I should be good if I unlock the nexus and use an EX / Lean / Despair / Blu-Spark / or any kernels - these do have modified system so how about the M's warning msgs? are the custom ROMs on M are modded to avoid any nagging messages like that?
6- Please link me any useful posts/threads that are updated to reflect latest changes like SU or any old information that is essential !! thanks !!
Ashtrix said:
Hello fellas,
After a long time I've decided to be back on Nexus, can't enjoy without nexus phones, ZF2 developement is stagnant as ASUS is not releasing src, a great HW stuck by OEM limtations.
So I've got my N6 today, I've learnt a few things before like not downgrading bootloader, had a post saying which versions are safe and ones that are not(idk why will anyone want to downgrade unless they want OTAs based on Fi, root is superior to all). So here's my to-do list sorry to post this here but seems like this is start for me.Please correct me If I understood anthing wrong....as It's been a long time since I used a nexus (Maguro was my first nexus and things rapidly changed these days..)
1 - mFastboot for flashing
2 - OEM unlock check prior to unlock the phone (shipped with 5.1 LMY47D so I may need to do this before proceeding)
A few questions -
3 - Does NRT has mFastboot ? I have it in my computer tho.
4 - Can any one give me crash course for SuperSU + MultiROM with 5.1.1 (Need Xposed:silly, 6.x & a few Nexus 6 information, any useful links would do the job.
a- Like If I OEM unlock my n6 now and use 5.1.1 CM based it has pre-root right ? So I shouldn't bother with SuperSU BETA 2.6x right, next is the systemless root is because of M's warning messages ? why all this hassle of
**root** as of lately with L and M, Is it because of SELinux policies + M's changes with System related messages ?
b - Does MultiROM work on 5.1.1 plus M latest release ?
5- I should be good if I unlock the nexus and use an EX / Lean / Despair / Blu-Spark / or any kernels - these do have modified system so how about the M's warning msgs? are the custom ROMs on M are modded to avoid any nagging messages like that?
6- Please link me any useful links that are updated to reflect latest changes like SU or any old information that is essential !! thanks !!
Click to expand...
Click to collapse
1.) I don't think you need mFastboot. I think you just want standard fastboot with Nexus phones
2.) I'm not sure what this means, but just follow the beginner guide in the General section to unlock the device
2a.) Follow the advice in answer 2 for fastboot information as well
3.) NRT installs standard fastboot and adb into C:\Program Files(x86)\WugFresh Development\NRT\Data\ folder
4.) Can't do it, I don't use multi-rom.
5.) There are special instructions for installing custom kernels. Follow the directions mentioned within the threads
6.) This information will be available in the custom ROM or kernel threads you choose to use
AlkaliV2 said:
1.) I don't think you need mFastboot. I think you just want standard fastboot with Nexus phones
2.) I'm not sure what this means, but just follow the beginner guide in the General section to unlock the device
2a.) Follow the advice in answer 2 for fastboot information as well
3.) NRT installs standard fastboot and adb into C:\Program Files(x86)\WugFresh Development\NRT\Data\ folder
4.) Can't do it, I don't use multi-rom.
5.) There are special instructions for installing custom kernels. Follow the directions mentioned within the threads
6.) This information will be available in the custom ROM or kernel threads you choose to use
Click to expand...
Click to collapse
Thanks,
Last time I had a nexus 6 just for a couple of days which I returned for various reasons, I had the firmware error upon flashing the imgs from 5.0.x to 5.1.1, after googling a bit I used that mFastboot, but wanna confirm it..
Ashtrix said:
Thanks,
Last time I had a nexus 6 just for a couple of days which I returned for various reasons, I had the firmware error upon flashing the imgs from 5.0.x to 5.1.1, after googling a bit I used that mFastboot, but wanna confirm it..
Click to expand...
Click to collapse
I'm pretty sure mFastboot is made directly for a Verizon variant, but since the Nexus 6 is unlocked and your Verizon SIM card dictates the network you are on, I would say stick with normal Fastboot for your flashing endeavors. Good luck and read twice, flash once :good:
Edit: Quick side note, love the avatar. Good choice.
Thankyou :highfive:
Just did an OEM unlock and wierdly after that, the bugdroid loading doesn't end at all. Did an factory img flash of 5.1.1 Shamu-LMY48Y and booted in less than a min Lol.
And yes the fastboot is working, wow things are definitely wierd with Shamu (volume normalization, mFastboot previous xperience, bootloader bricks...seems like Qcom fixed that after CM brickbug and no one can help the manual bricking) but I'm ok with all these , just love this device, massive, powerful and sexy looking piece
EDIT :
Well everything's going fine but this bugdroid loading doesn't seem to be fixed at all, after bootup 23Gb was there so I did a format and again stuck, this time around I tried using TWRP to flash (CM12.1)after doing fastboot commands - fastboot format userdata, cache. Now it says unable to flash on so&so data partition, So formatted from the OS and now MTP says generical heirarchial. I don't remember any device with that format...
EDIT 2 : Device won't boot with that bugdroid formatting the Data partition. Needs to be fastboot flashed else stuck there forever again same 23Gb bootissue if I do that & Using fastboot format userdata command it formats into the 64GB - 54Gb available space but with TWRP It fails to flash - the same error, can't flash on data parition. So repeat fastboot and it's a damn cycle. Will try to flash MM if it won't then. I may have to return again...OMG
EDIT 3 : http://forums.androidcentral.com/go...ys-formatting-data-yellow-text-any-ideas.html
http://forum.xda-developers.com/google-nexus-5/help/help-stuck-formatting-data-t2737793
EDIT : Tried MM and after 10 mins formatted succesfully now gotta try a ROM or any, hope its fine !!
Again the GH FS is back with MTP and doesn't flash at all with TWRP. If I go for a re-lock and it it fails to boot with formatting properly...then bam nothing but a bricked Nexus !!
TWRP did the format but the device is messed up, sliptscreen issue..
I'm going to return this, enough of the hassle had me messed up totally :crying:
Seems like 6P seems better than having all these issues. Or wait for the 2016 device...
EDIT : Sorry for the GH format seems like it's normal, but the flashing issue is too wierd..
I dont know what the **** a bugdroid is.... But just use fastboot to flash things. Post up console messages and we can help.
If you flash userdata.img, its for the 32 gig model... But you can use TWRP to expand the partition to give your space back.
http://forum.xda-developers.com/nexus-6/general/phone-gb-storage-to-factory-reset-t3225492
Just read, its really really easy.
scryan said:
I dont know what the **** a bugdroid is.... But just use fastboot to flash things. Post up console messages and we can help.
If you flash userdata.img, its for the 32 gig model... But you can use TWRP to expand the partition to give your space back.
http://forum.xda-developers.com/nexus-6/general/phone-gb-storage-to-factory-reset-t3225492
Just read, its really really easy.
Click to expand...
Click to collapse
I know this issue, just a factory reset fixed this thing on my old N6 that I had for 2 days, but this takes too much of time to format....Just had TWRP do the job and flashed the Temasek but ALAS !! Splitscreen issue.
Because having my old reliable daily driver gathering dust really bothered me for too long...
This is a plain build of LineageOS 13.0 with the xt926 target. Pretty much everything necessary to build it is already in git, it just doesn't have any official builds or any official LineageOS maintainers. It's an opportunity for someone who still loves this device... I'm going to try to get 14.1 working and hopefully turn this over to someone who has the time to become a LineageOS maintainer for the device.
It requires KitKat bootloader. Your bootloader should also be unlocked (e.g. with Motopocalypse).
This is also my first time building Android and actually using it, so if you think I should have done something differently, feel free to let me know! I've been lurking on XDA for many years and I've learned a lot. This is the first chance I've had to start giving something back.
How I built it
I built this using LineageOS build instructions, just substituted xt926 as the build target and cm-13.0 as the branch. I had to replace external/tinycompress/ because it wouldn't compile; I used upstream Google sources, then it compiled properly.
I pulled missing proprietary blobs from https://github.com/TheMuppets/proprietary_vendor_motorola from the cm-13.0 branch.
Questions
What about LineageOS 14.1?
I plan to attempt to build 14.1 next. But unlike 13.0 it doesn't already have an xt926 build target defined so it's going to take some extra work. If all goes well, I'll be able to post builds in the next few days. If not...
Why don't you support JBBL?
Because it would be a lot of extra work. And from the preliminary look I've taken, it seems that 14.1 will probably require KKBL anyway, and not work at all with JBBL.
Does it work on xt907/xt925?
It should do. I don't have either of these devices so I can't test it and I can't guarantee it. But you can always try it!
Does it work on other phones?
If it's msm8960, then maybe. Otherwise, probably not. But feel free to brick your phone if you really want.
Download
System: lineage-13.0-20170706-UNOFFICIAL-xt926.zip
Recovery: lineage-13.0-20170706-UNOFFICIAL-xt926-recovery.img
Instructions:
Flash recovery from fastboot (optional). You can use the included recovery or some other recovery you already have.
Flash system ZIP from recovery. Flash gapps at the same time before rebooting out of recovery.
Wipe data/cache.
Reboot system and Enjoy!
I'm really interested in flashing lineageOS to my Droid RAZR HD devices. Unfortunately, I think these specs are incompatible:
* System Version: 182.46.15 XT926 Verizon.en.US
* Model Number: DROID RAZR HD
* Android Version: 4.4.2
* Baseband Version: VANQUINSH_BP_100731_020.64.21P
* Kernel Version: 3.4.42-gbd361ac
* Build Number: KDA20.62-15
* Build Date: Tue Jul 29 02:51:09 PDT 2014
Without going through all the tr.apk/motopacalypse.apk stuff, do you know of any way to make this happen? thanks.
I'm really interested in flashing lineageOS to my Droid RAZR HD . Any bugs? thx
Thanks for posting this! I tried installing it on my unlocked Verizon XT926, and got stuck at the animated logo in the boot sequence. I had the same problem with the CM11 M2 snapshot, but CM 12.1 works.
In both cases, I tried wiping data, cache, Dalvik cache, and system multiple times; I reinstalled and re-wiped in different sequences and combinations. (All operations were in TWRP.) I also tried cold booting and booting with and without SIM and SD card. I did not attempt to install GApps.
Bootloader version: 10.9B
Baseband version: VANQUINSH_BP_100731_020.64.21P
pentaflox said:
Thanks for posting this! I tried installing it on my unlocked Verizon XT926, and got stuck at the animated logo in the boot sequence. I had the same problem with the CM11 M2 snapshot, but CM 12.1 works.
In both cases, I tried wiping data, cache, Dalvik cache, and system multiple times; I reinstalled and re-wiped in different sequences and combinations. (All operations were in TWRP.) I also tried cold booting and booting with and without SIM and SD card. I did not attempt to install GApps.
Bootloader version: 10.9B
Baseband version: VANQUINSH_BP_100731_020.64.21P
Click to expand...
Click to collapse
I've had this issue in the past. First wipe your system, I usually do a format data as well (you will lose everything on your internal SD if you do this, external SD should be fine). Install CM 11, reboot to recovery, don't wipe and dirty flash whatever CM/LOS rom you want.
Ok, so I said all of that, and then got stuck for forever. I couldn't use my copy of TWRP 2.8.6.0, I had to use the recovery posted in this thread. I then did a factory reset (full wipe) and was able to install this build and get it to load.
I'd love to see an updated TWRP for KBBL, but I don't think we'll ever get that.
---------- Post added at 01:38 PM ---------- Previous post was at 12:58 PM ----------
Triple posting here:
I got into the system and things ran...ok. I rebooted to recovery and installed the latest opengapps pico package and everything went wrong. The device is now running very slowly and I can't log in to Google. It looks like it's going to work, but sits at "Checking info" for a long time before saying I can't log in. Comparatively, running the JBBL, Photon Q recovery, and latest official Lineage build for the Photon Q works much faster and without issue. I don't like running JBBL, and would rather have a build for my device and not a similar one, but that may be what I need to go back to.
I just tried another flash without rebooting between rom and Gapps and I'm getting stuck at the same point.
Another update:
Just tried opengapps nano package, I was able to get through the sign-in process with this one, but it's running slower with this package than with the pico. I'll give it a try for a couple of days and will try to remember to stop back to leave more feedback. I still need to test voice calls, since they don't work with the photon q (speakerphone works but not the built-in mic)
Well, no audio works. I can't play back local audio, both mic and earpiece are dead, no loudspeaker or speaker phone mic either. Back to 12.1 for now. I'll keep an eye on this thread too. Thanks!
why dont use the LOS13 for de xt 907? that rom runs very well in xt925 with jbbl. All is functional.
@error28, can you submit your work to a LOS branch so that others can commit changes, too? I retried installing this build today using the recovery you linked. Even though some things don't work, this seems like a great start and it would be terrific if it attracted more contributions.
My experience with this build: Since I didn't install GApps, I didn't reproduce the chronic slowdown that @thunder2132 mentioned. Any ideas for fixing audio? Trying to play an MP3 or M4A file in any app hangs the app; pressing the record button in Sound Recorder does not start recording. Also, LOS did not detect the SIM card.
Some notes for others thinking of trying this build: The recovery image linked in the original post is a version of CyanogenMod Recovery, which lacks many of the capabilities of TWRP. (It even failed when I tried to install SuperSU.) However, LOS continued to load successfully after I reflashed TWRP 2.8.5. I also tried installing the Photon Q (asanti) version of TWRP 3.0.2, since that's what TWRP Manager suggests for the XT296, but this TWRP version failed to load for me.
Related thread: https://forum.xda-developers.com/droid-razr-hd/help/xt926-4-1-1-to-lineageos-14-1-t3636103
pentaflox said:
@error28, can you submit your work to a LOS branch so that others can commit changes, too? I retried installing this build today using the recovery you linked. Even though some things don't work, this seems like a great start and it would be terrific if it attracted more contributions.
My experience with this build: Since I didn't install GApps, I didn't reproduce the chronic slowdown that @thunder2132 mentioned. Any ideas for fixing audio? Trying to play an MP3 or M4A file in any app hangs the app; pressing the record button in Sound Recorder does not start recording. Also, LOS did not detect the SIM card.
Some notes for others thinking of trying this build: The recovery image linked in the original post is a version of CyanogenMod Recovery, which lacks many of the capabilities of TWRP. (It even failed when I tried to install SuperSU.) However, LOS continued to load successfully after I reflashed TWRP 2.8.5. I also tried installing the Photon Q (asanti) version of TWRP 3.0.2, since that's what TWRP Manager suggests for the XT296, but this TWRP version failed to load for me.
Related thread: https://forum.xda-developers.com/droid-razr-hd/help/xt926-4-1-1-to-lineageos-14-1-t3636103
Click to expand...
Click to collapse
Maybe someone will try one of this two ROM´S -> https://forum.xda-developers.com/dr...resurrectionremix-nougat-xt907-xt905-t3697567
-> https://forum.xda-developers.com/dr.../crdroid-3-8-nougat-xt907-xt905-jbbl-t3697571
And yes it´s for the RazR-M, but it´s mostly the theme...
I have tested both...on my RazR-HD XT925...and can say ...very smooth...stable no big Problems so far...:good:
The only conditions: you must have JBBL and you must format DATA-Partition in F2FS !
WfG Konrat
|Konrat| said:
Maybe someone will try one of this two ROM´S -> https://forum.xda-developers.com/dr...resurrectionremix-nougat-xt907-xt905-t3697567
-> https://forum.xda-developers.com/dr.../crdroid-3-8-nougat-xt907-xt905-jbbl-t3697571
And yes it´s for the RazR-M, but it´s mostly the theme...
I have tested both...on my RazR-HD XT925...and can say ...very smooth...stable no big Problems so far...:good:
The only conditions: you must have JBBL and you must format DATA-Partition in F2FS !
WfG Konrat
Click to expand...
Click to collapse
I'm willing to try this if I can ever get it working. Is there a published method for downgrading the bootloader without reinstalling stock? I assume there's no CDMA support in the XT907 blob.
pentaflox said:
I'm willing to try this if I can ever get it working. Is there a published method for downgrading the bootloader without reinstalling stock? I assume there's no CDMA support in the XT907 blob.
Click to expand...
Click to collapse
I don´t now another method to downgrade...only with install stock...
But i think it´s relative simple...
In the original JB-Rom edit the "XML" and remove the 2 Lines with "partition_signed" and "tz_signed"...
And flash with RSD
Maybe you should then turn on Wlan, GPS, NFC and Bluetooth before flashing the Nougat-Rom...in the past there were problems when flashing with turn off...especially with Wlan....go´s after that never on
Because of CDMA...I don´t now ...must you test...in the build.prob are lines with CDMA config...but i don´t now the meaning...
konrat
error28 said:
What about LineageOS 14.1?
I plan to attempt to build 14.1 next. But unlike 13.0 it doesn't already have an xt926 build target defined so it's going to take some extra work. If all goes well, I'll be able to post builds in the next few days. If not...
Click to expand...
Click to collapse
Have you had the time and opportunity to try a LOS 14.1 build? I am interested in this as I have an XT905 (basically an xt907 with a different radio) and my build for the KKBL for LOS 14.1 does not successfully boot. I think that maybe/possibly when we go to Oreo that only the KKBL version will work.
error28 said:
Why don't you support JBBL?
Because it would be a lot of extra work. And from the preliminary look I've taken, it seems that 14.1 will probably require KKBL anyway, and not work at all with JBBL.
Click to expand...
Click to collapse
FYI: The fact that people are using my JBBL builds for an XT907/XT905 I think proves LOS 14.1 can run on the JBBL. Its actually one of the most stable ROMs I have personally used.
error28 said:
Does it work on xt907/xt925?
It should do. I don't have either of these devices so I can't test it and I can't guarantee it. But you can always try it!
Click to expand...
Click to collapse
Can someone document the steps they take to convert an XT907 ROM to that of an XT925/XT926?
error28 said:
Recovery: lineage-13.0-20170706-UNOFFICIAL-xt926-recovery.img
Click to expand...
Click to collapse
If someone documents the conversion of an XT907 ROM, maybe I could try and compile TWRP 3.1.1 for the xt925/xt926. Maybe.
error28 said:
Instructions:
Flash recovery from fastboot (optional). You can use the included recovery or some other recovery you already have.
Flash system ZIP from recovery. Flash gapps at the same time before rebooting out of recovery.
Wipe data/cache.
Reboot system and Enjoy!
Click to expand...
Click to collapse
thunder2132 said:
I've had this issue in the past. First wipe your system, I usually do a format data as well (you will lose everything on your internal SD if you do this, external SD should be fine). Install CM 11, reboot to recovery, don't wipe and dirty flash whatever CM/LOS rom you want.
Click to expand...
Click to collapse
FYI: Although its a different phone with a different Kernel, for the XT907 JBBL Nougat ROM's (not Marshmallow) we also had to reformat the Data partition as F2FS.
pentaflox said:
can you submit your work to a LOS branch so that others can commit changes, too? I retried installing this build today using the recovery you linked. Even though some things don't work, this seems like a great start and it would be terrific if it attracted more contributions.
Click to expand...
Click to collapse
And thats the problem, contributors for our aging phones are hard to find, and extending beyond your own computer takes extra work & time. I know I have not placed my work onto GITHUB. I built personally just to get Nougat ResurrectionRemix for me personally, not for the betterment of the world
pentaflox said:
My experience with this build: Since I didn't install GApps, I didn't reproduce the chronic slowdown that thunder2132 mentioned. Any ideas for fixing audio? Trying to play an MP3 or M4A file in any app hangs the app; pressing the record button in Sound Recorder does not start recording. Also, LOS did not detect the SIM card.
Click to expand...
Click to collapse
Have you tried taking a Logcat and lookiung at the results? or maybe even posting them on www.hastebin.com in case someone is interested enough to look for you?
pentaflox said:
Some notes for others thinking of trying this build: The recovery image linked in the original post is a version of CyanogenMod Recovery, which lacks many of the capabilities of TWRP. (It even failed when I tried to install SuperSU.) However, LOS continued to load successfully after I reflashed TWRP 2.8.5. I also tried installing the Photon Q (asanti) version of TWRP 3.0.2, since that's what TWRP Manager suggests for the XT296, but this TWRP version failed to load for me.
Click to expand...
Click to collapse
My brief look at the source code shows that the xt897 and the XT925/XT926 use different touch/display drivers.
---------- Post added at 10:43 AM ---------- Previous post was at 10:42 AM ----------
|Konrat| said:
Maybe someone will try one of this two ROM´S -> https://forum.xda-developers.com/dr...resurrectionremix-nougat-xt907-xt905-t3697567
-> https://forum.xda-developers.com/dr.../crdroid-3-8-nougat-xt907-xt905-jbbl-t3697571
And yes it´s for the RazR-M, but it´s mostly the theme...
I have tested both...on my RazR-HD XT925...and can say ...very smooth...stable no big Problems so far...:good:
The only conditions: you must have JBBL and you must format DATA-Partition in F2FS !
Click to expand...
Click to collapse
Again, any chance you could document what you change to get it to run?
pentaflox said:
I'm willing to try this if I can ever get it working. Is there a published method for downgrading the bootloader without reinstalling stock? I assume there's no CDMA support in the XT907 blob.
Click to expand...
Click to collapse
|Konrat| said:
I don´t now another method to downgrade...only with install stock...
But i think it´s relative simple...
In the original JB-Rom edit the "XML" and remove the 2 Lines with "partition_signed" and "tz_signed"...
And flash with RSD
Maybe you should then turn on Wlan, GPS, NFC and Bluetooth before flashing the Nougat-Rom...in the past there were problems when flashing with turn off
Click to expand...
Click to collapse
I personally never use RSD, I explicitly use fastboot to manually upgrade/downgrade my bootloader and recovery etc. The below is expoicitly for an xt905, but should be pretty easy to convert for your device
Code:
mfastboot flash partition "H:\My Documents\MobilePhone\2014 Motorolla XT905\RSD_IMAGES\JB\XT905 RETAIL Firmware\partition_signed"
mfastboot flash sbl1 "H:\My Documents\MobilePhone\2014 Motorolla XT905\RSD_IMAGES\JB\XT905 RETAIL Firmware\sbl1_signed"
mfastboot flash sbl2 "H:\My Documents\MobilePhone\2014 Motorolla XT905\RSD_IMAGES\JB\XT905 RETAIL Firmware\sbl2_signed"
mfastboot flash sbl3 "H:\My Documents\MobilePhone\2014 Motorolla XT905\RSD_IMAGES\JB\XT905 RETAIL Firmware\sbl3_signed"
mfastboot flash rpm "H:\My Documents\MobilePhone\2014 Motorolla XT905\RSD_IMAGES\JB\XT905 RETAIL Firmware\rpm_signed"
mfastboot flash tz "H:\My Documents\MobilePhone\2014 Motorolla XT905\RSD_IMAGES\JB\XT905 RETAIL Firmware\tz_signed"
mfastboot flash aboot "H:\My Documents\MobilePhone\2014 Motorolla XT905\RSD_IMAGES\JB\XT905 RETAIL Firmware\aboot_signed"
mfastboot reboot-bootloader
mfastboot flash modem "H:\My Documents\MobilePhone\2014 Motorolla XT905\RSD_IMAGES\JB\XT905 RETAIL Firmware\modem_signed"
mfastboot flash fsg "H:\My Documents\MobilePhone\2014 Motorolla XT905\RSD_IMAGES\JB\XT905 RETAIL Firmware\fsg_signed"
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash logo "H:\My Documents\MobilePhone\2014 Motorolla XT905\RSD_IMAGES\JB\XT905 RETAIL Firmware\logo"
mfastboot flash devtree "H:\My Documents\MobilePhone\2014 Motorolla XT905\RSD_IMAGES\JB\XT905 RETAIL Firmware\devtree_signed"
mfastboot flash boot "H:\My Documents\MobilePhone\2014 Motorolla XT905\RSD_IMAGES\JB\XT905 RETAIL Firmware\boot_signed"
mfastboot flash recovery "H:\My Documents\MobilePhone\2014 Motorolla XT905\RSD_IMAGES\JB\XT905 RETAIL Firmware\recovery_signed"
mfastboot flash system "H:\My Documents\MobilePhone\2014 Motorolla XT905\RSD_IMAGES\JB\XT905 RETAIL Firmware\system_signed"
mfastboot flash cdrom "H:\My Documents\MobilePhone\2014 Motorolla XT905\RSD_IMAGES\JB\XT905 RETAIL Firmware\cdrom_signed"
mfastboot erase tombstones
mfastboot erase userdata
mfastboot erase cache
mfastboot reboot-recovery
Your partitions may be different, and your files and locations will definitely! be different
|Konrat| said:
Because of CDMA...I don´t now ...must you test...in the build.prob are lines with CDMA config...but i don´t now the meaning...
Click to expand...
Click to collapse
Yeah, hmmm.. we dont have CDMA in Aus either, so I didnt test it. However, I did not remove any explicit CDMA code, but did change the "labelling" of CDMA stuff to remove company names/branding, so maybe that would of broke something
Again, any chance you could document what you change to get it to run?
Click to expand...
Click to collapse
I have nothing changed.
I was on kitkat and flashback to JB with an "JB-O2DE-ROM"..."O2" Is an Provider in Germany
(changed before the xml).
And flash with RSD-light.(it´s btw. only a Gui for Fastboot)
Than i flash your TWRP with Fastboot and than wiped all and reformat DATA and CACHE Partition to F2FS
After that i flash your ROM and Open GApps...booting...
Than i tweak a little bit the build.prob...Display Density to 320... Model Name...Country Code
And Viola... ready
WfG Konrat
|Konrat| said:
I have nothing changed.
I was on kitkat and flashback to JB with an "JB-O2DE-ROM"..."O2" Is an Provider in Germany
(changed before the xml).
And flash with RSD-light.(it´s btw. only a Gui for Fastboot)
Than i flash your TWRP with Fastboot and than wiped all and reformat DATA and CACHE Partition to F2FS
After that i flash your ROM and Open GApps...booting...
Than i tweak a little bit the build.prob...Display Density to 320... Model Name...Country Code
Click to expand...
Click to collapse
I am suprised that TWRP works, as there is explicit code for the screen resolution. The xt907 being 540x960 while yours is 720x1280
As for the ROM, the zip file explicitly checks for specific model no's. Admittedly I do have a couple in there I wasn't too sure of, but I wouldn't of expected them to have worked on your phone.
From whaqt you are saying above, there is no definitive need to actually compile a ROM or TWRP if you stay on JBBL. Its only maybe a KKBL ROM that is "missing"? as the KKBL TWRP works as-is.
PS: No-one as yet has actually given me a good reason to upgrade to KKBL. The only reason I have heard is that it removes the random flash of
the screen when turning on.
Thanks for the help, @DiamondJohn. I still don't know how anyone is cross-flashing these images—modifying build.prop doesn't seem to be enough. Although I haven't gotten the XT907 builds to work, at least now I've had the experience reverting to JBBL and restoring KKBL, and I've learned a lot more about AOSP. I'm running Mokee OS 5.1 at the moment.
pentaflox said:
Thanks for the help, @DiamondJohn. I still don't know how anyone is cross-flashing these images—modifying build.prop doesn't seem to be enough. Although I haven't gotten the XT907 builds to work, at least now I've had the experience reverting to JBBL and restoring KKBL, and I've learned a lot more about AOSP. I'm running Mokee OS 5.1 at the moment.
Click to expand...
Click to collapse
I would really question @|Konrat|, he appears pretty confident in what he does.
As for simply changing the build.prop, I know there are a number of items that cannot be changed except through the source code at compile time. build.prop mainly does visual things in renaming a device. What is really suprising is that the xt907 has different touch/display drivers
As for 5.1, I personally found Lollipop very problematic on my phone. With random reboots and not being able to run my custom live wallpaper.
DiamondJohn said:
As for 5.1, I personally found Lollipop very problematic on my phone. With random reboots and not being able to run my custom live wallpaper.
Click to expand...
Click to collapse
Thanks for the advice. Did you have those issues with Mokee specifically? It's only been two days but Mokee had serious enough problems that I went back to CM.
pentaflox said:
Thanks for the advice. Did you have those issues with Mokee specifically? It's only been two days but Mokee had serious enough problems that I went back to CM.
Click to expand...
Click to collapse
No, from memory, I used to run BlissPop, Carbon and maybe RR. Mokee seemed too close to CM at the time to really get into it.
---------- Post added at 10:00 AM ---------- Previous post was at 09:55 AM ----------
pentaflox said:
I still don't know how anyone is cross-flashing these images—modifying build.prop doesn't seem to be enough. Although I haven't gotten the XT907 builds to work, at least now I've had the experience reverting to JBBL and restoring KKBL
Click to expand...
Click to collapse
One of the surprises I had with people cross flashing my XT907/XT905 buiulds onto other phones is that the first line of the install script/zip checks that the device is an XT907/XT905, It occurred to me if they flash the XT907 TWRP, then it will probably report itself as an XT907, and thereby pass that test/check.
But I am still surprised that the XT907 TWRP works:silly:
|Konrat| said:
Maybe someone will try one of this two ROM´S -> https://forum.xda-developers.com/dr...resurrectionremix-nougat-xt907-xt905-t3697567
-> https://forum.xda-developers.com/dr.../crdroid-3-8-nougat-xt907-xt905-jbbl-t3697571
And yes it´s for the RazR-M, but it´s mostly the theme...
I have tested both...on my RazR-HD XT925...and can say ...very smooth...stable no big Problems so far...:good:
The only conditions: you must have JBBL and you must format DATA-Partition in F2FS !
WfG Konrat
Click to expand...
Click to collapse
Can second and confirm this. Both ROM's run great on my RAZR HD MAXX XT926.
RR was too laggy for me personally, it kept rebooting so i decided on crDroid as my daily which so far has been the best ROM i've ever used on this ageing device.
So if anyone is out there still using the RAZR HD as their daily phone give the above a try. They've really given my device a new lease of life and i feel like i'll get another year or two out of it as a result.
Oh and a big thanks for DiamondJohn and the creators behind these ROMs. Thanks!
AS OF RIGHT NOW THIS IS ONLY FOR T-MOBILE AND NOW SPRINT!
This is a stock rom for the retail brazil MotoZ(2) force ported over to our phone.
This is stock with only encryption and dm verity removed for support with twrp. (No more boot image including.)
Flashing instructions.
NOTE: CLEAN FLASH! This is a rom from another phone. I cant help you if you write me and say system fc's or any other fc's and you didnt clean flash.
1. Download rom and place it on sd card or internal.
2. Download oem.img and flash it (fastboot flash oem oem.img)
3. Reboot to recovery
2. Wipe system data cache.
3 Flash rom.
4. Reflash whatever root you had. (Magisk)
5. Profit.
As far as I know this does have all the latest fixings (KRACK,Bluebourne, ECT)
Includes VOLTE
Includes WIFI Calling
Usually all roms are pretty stable. IF there is any bugs post below and ill get to working on it.
Sprint install guide
Guide for Sprint users:
Go into Bootloader
Flash This oem.img (courtesy @joemossjr) "fastboot flash oem oem.img
Go into recovery
wipe system and data.
Flash rom
Tested this on my Sprint phone and everything works just fine and with Pantheon, you will pass Safetynet if you flash the image in bootloader.
note: for Sprint users, we NEED to flash the oem.img to not have dialer issues, so I will stress, flash that oem image and if you don't want the bloat, you can delete everything but oem.prop from /oem folder through root or recovery's file manager after you mount OEM.
FLASH ALL
Flash all has been made this includes T-Mobiles Modem with stock everything else. you wont be able to take otas on it due to modified Modem. But updates for thes roms come a lot faster then ours so when one comes out ill update it. Please flash the latest twrp. This is going to encrypt you so your gonna have to format data in twrp and flash this Unencrypt Zip
This will format data. Treat it as a flash all to get back to stock also if you dont want tmobile bloat. This rom in it self with twrp will pass safetynet without magisk as long as you dont modify oem partition. Other then that happy flashing. Download for flash all is below
Downloads: November
oem.img
November Flash all
CREDITS
Motorola Firmware Team
@SuperR. for providing a bad ass platform for Rom making.
@Uzephi for testing the Sprint side of things lol
First! ?
Pantheon works on this rom.
Edit: kernel upstream has KRACK and blueborne fixes in it ?
Edit: tried same install instructions. Works for Sprint phones and activates them
Edit 3: well had to do some dialer stuff, but everything else worked. Will give guide in the morning to get the rom 100%
Sprint install guide
Guide for Sprint users:
Go into Bootloader
Flash This oem.img (courtesy @joemossjr) "fastboot flash oem oem.img
Go into recovery
mount oem. (you can delete everything using file manager in /oem besides oem.prop)
wipe system and data.
Flash rom
Tested this on my Sprint phone and everything works just fine and with Pantheon, you will pass Safetynet if you flash the image in bootloader.
Edit: for Sprint users, we NEED to flash the oem.img to not have dialer issues, so I will stress, flash that oem image and if you don't want the bloat, you can delete everything but oem.prop from /oem folder through root or recovery's file manager after you mount OEM.
Edit 2: Wifi Calling will not work, that file is in sprint's OEM partition and it FC's when adding it or using sprint's oem.img, so if you want this rom, I advise WiFi calling will not work until further notice.
updated thread
ADDED Stock oem image
ADDED Sprint support per @Uzephi
joemossjr said:
updated thread
ADDED Stock oem image
ADDED Sprint support per @Uzephi
Click to expand...
Click to collapse
WiFi calling currently doesn't work for Sprint. Technical details: Sprint uses a different WiFi calling setup where a special Google dialer is in /oem to work. If you use this dialer or the included wifi dialer.jar file, it will just continuously FC and you can't do anything. To get Sprint models working we have to use the stock dialer which doesn't work with Sprint's WiFi calling. We will put a poll up to see interest in WiFi calling since this will take a bit of hackery to get working. I want to gauge interest before I take on this task.
My new T mobile Moto Z2 Force still has stock August image on it. I am waiting for my screen protector and case to arrive before I transfer my account to this phone. I am also waiting to unlock the bootloader and root the device. Now, should I flash your new Nov image since I want KRACK and blueborne fixes OR should I first flash the August image first, then upgrade to Nov image.
kendallgreen said:
My new T mobile Moto Z2 Force still has stock August image on it. I am waiting for my screen protector and case to arrive before I transfer my account to this phone. I am also waiting to unlock the bootloader and root the device. Now, should I flash your new Nov image since I want KRACK and blueborne fixes OR should I first flash the August image first, then upgrade to Nov image.
Click to expand...
Click to collapse
Either or honestly lol you can go to August for the updated firmware
So going from a brand new device on NCX26.7, how do we go about getting our phones ready to flash this? Unlock bootloader, root, then flash this and reroot? Then follow the instructions for TWRP in your other post?
swidger said:
So going from a brand new device on NCX26.7, how do we go about getting our phones ready to flash this? Unlock bootloader, root, then flash this and reroot? Then follow the instructions for TWRP in your other post?
Click to expand...
Click to collapse
Unlock bootloader, install TWRP, follow instructions in OP.
Moto Z2 Force Edition - T-Mobile
Unlocked Bootloader
TWRP 3.2.0-0
I keep trying to flash this ROM, and have succeed in the flashing process. However, whenever I boot up, I get "TMOConfig has stopped" and then I can close it. I notice, that cellular data is not active. I continue through setup as normal until the Moto Permissions screen. When I try to go through this screen, whether I accept or decline, "com.motorola.tmo.setupext has stopped" comes up. The only option is to open app again and it takes me to the prior screen for Google setup and gets stuck in this loop until I restart the phone.
I've followed the instructions exactly MULTIPLE times just to verify I got it right. I'm clean flashing as well, so no it's not cuz of that. I've even redownload the files three times just to ensure it wasn't the result of possible file issues. Anyone else having this issue? I'd greatly appreciate a second pair of eyes on this!
champ784 said:
Moto Z2 Force Edition - T-Mobile
Unlocked Bootloader
TWRP 3.2.0-0
I keep trying to flash this ROM, and have succeed in the flashing process. However, whenever I boot up, I get "TMOConfig has stopped" and then I can close it. I notice, that cellular data is not active. I continue through setup as normal until the Moto Permissions screen. When I try to go through this screen, whether I accept or decline, "com.motorola.tmo.setupext has stopped" comes up. The only option is to open app again and it takes me to the prior screen for Google setup and gets stuck in this loop until I restart the phone.
I've followed the instructions exactly MULTIPLE times just to verify I got it right. I'm clean flashing as well, so no it's not cuz of that. I've even redownload the files three times just to ensure it wasn't the result of possible file issues. Anyone else having this issue? I'd greatly appreciate a second pair of eyes on this!
Click to expand...
Click to collapse
you still have OEM stuff - you need to wipe oem partition and then flash.
byt3b0mb said:
you still have OEM stuff - you need to wipe oem partition and then flash.
Click to expand...
Click to collapse
Does formatting help wipe that? I've done wipes and formatting just to be safe
Gotta flash the oem.img then reflash
joemossjr said:
Gotta flash the oem.img then reflash
Click to expand...
Click to collapse
Just tried redoing everything again. I get cellular now, and it boots. But now the phone will randomly freeze after a few minutes and restart
Sorry for being such a noob... This is my first dual partition device I've worked with... I've gotten spoiled with OnePlus and Nexus devices lol
champ784 said:
Just tried redoing everything again. I get cellular now, and it boots. But now the phone will randomly freeze after a few minutes and restart
Sorry for being such a noob... This is my first dual partition device I've worked with... I've gotten spoiled with OnePlus and Nexus devices lol
Click to expand...
Click to collapse
Sorry I meant which slot/ota are you on
joemossjr said:
Sorry I meant which slot/ota are you on
Click to expand...
Click to collapse
To check this, go to TWRP and in the reboot menu it will tell you which slot you're on like the below screenshot of me on slot B
For sprint users, there is a poll to end on dec 8th asking if WiFi calling is a must for your rom. please answer it. I have tried a few methods but all fail. any further would require editing the framework.jar file in oem and some trickery that needs some serious coding done to work correctly. So I will take on the task if enough vote for it. (I do this in my free time for free and if not enough interest is given, I'd rather not waste the time as another update might break it, and it also takes me away from my EAS project which has a lot of interest.)
joemossjr said:
Sorry I meant which slot/ota are you on
Click to expand...
Click to collapse
Mine shows Slot A. Am I correct in assuming that should be Slot B?
champ784 said:
Mine shows Slot A. Am I correct in assuming that should be Slot B?
Click to expand...
Click to collapse
Slot A has less bugs than Slot B. I would stay slot A if you can. I would suggest wiping oem in TWRP, mount oem, wipe oem, then reboot to bootloader and flash the oem img in OP.
Ok, so here goes...
I'm currently running latest stock Motorola Android Q (reteu2) with unlocked bootloader, TWRP and Magisk installed and verity message showing up during boot.
According to "fastboot getvar all" my current slot is _a.
Although I'm pretty happy with this setup, I'm curious to try out LineageOS. From what I've read so far, flashing LineageOS from TWRP would flash it it to slot _b. So if I'm unhappy with LOS would "fastboot --set-active=a" just throw me back to stock?
Sorry, if this has been answered before. I just can't seem to find it. I'd appreciate all input.
Thanks!!!
Sure would be nice to be able to do that... but no. I believe the main reason for this is due to the fact that both slots share the same userdata partition. So say you installed lineage to slot B, it would overwrite the existing userdata partition where your stock install (slot a) has nicely kept its app data, system data etc (probably) rendering it (stock install) ubootable. I'm sure someone else could elaborate more, or correct me if i'm wrong, but this is how I understand it.
Here is a good guide on A/B done by xda.
Can I flash two different ROMs on each partition and dual boot?
In theory, yes. Problems arise because of the shared data partition though, so it’s not recommended.
Click to expand...
Click to collapse
....from above guide
christian963 said:
Ok, so here goes...
I'm currently running latest stock Motorola Android Q (reteu2) with unlocked bootloader, TWRP and Magisk installed and verity message showing up during boot.
According to "fastboot getvar all" my current slot is _a.
Although I'm pretty happy with this setup, I'm curious to try out LineageOS. From what I've read so far, flashing LineageOS from TWRP would flash it it to slot _b. So if I'm unhappy with LOS would "fastboot --set-active=a" just throw me back to stock?
Sorry, if this has been answered before. I just can't seem to find it. I'd appreciate all input.
Thanks!!!
Click to expand...
Click to collapse
It's very simple. A dual boot would merge the data of both ROMs. As long as both ROMs could use the same apps (user and system!) you won't get any problems. But Lineage and Stock don't use the same apps.
Maybe Pixel or EvoX would work beside a stock ROM.
Does anyone have any ideas on how to flash a GSI to the Dynamic Super Partition? I've been trying for a month to flash DotOS and nothing. I can get it to flash using "fastboot flash super" but flashing to system it fails. Still doesn't boot regardless, even if I flash vbmeta and stock boot. I have no idea what I'm doing wrong.
phenomenalblaze said:
Does anyone have any ideas on how to flash a GSI to the Dynamic Super Partition? I've been trying for a month to flash DotOS and nothing. I can get it to flash using "fastboot flash super" but flashing to system it fails. Still doesn't boot regardless, even if I flash vbmeta and stock boot. I have no idea what I'm doing wrong.
Click to expand...
Click to collapse
When I was testing out GSI I used this method:
I would just change the rom name in .bat(?) File. Everything flashed and booted fine. The only issue I had with GSI roms & AT&T was that I couldn't get mobile service.
Better to stick with one of the many custom roms made for Pixel 4/XL. I mean I'd rather use something made for my device than something universal. Cool to try out new things though I get it. DotOS is not too much different than anything else.. DotOS has a different look, a different theme/ui.. I'm referring to DotOS Android 11. I used DOT on my OnePlus 6t, before I got my Pixel 4XL. I'll see what I can find about what you are talking about here and if and when I do find some good reads I'll return and link to them in this same post. I would definitely search high and low and look around in PHH's GSI notes and see what all is in them about this sort of thing. How are you doing your install? What is your installation process step by step?
I haven't used a GSI since my Motorola phones a few years ago but I remember depending on what device installation varies. I'll see if I can locate anything and link it here and tag you if I do. Cheers.
Edit added: Turns out DotOS devs revamped the new Android 12 theme engine and plan on releasing it once they drop v5 2 of their DotOS rom!! Maybe someone will compile DotOS. I plan on getting another better laptop in six months. If it's not available for us then I'll take a few cracks at it and if I'm successful I'll first get permission from DotOS and show them what I have and if they okay it I'll post some Pixel 4XL coral builds. But that will be six to nine months away from now. Times are hard. May happen sooner..
@phenomenalblaze I found a tool thats supposedly made for this sort of thing here:
I'm usually not HUGE on using toolkits on Android because you don't learn anything that way you know. .But figured I'd share.