Related
I'm trying to backup my phone before making any substantial changes to it. I've done the de la Vega root and made the AT&T APN changes and that's about it. I wanted to use the ADB fastboot commands to load CWM temporarily to do a backup. So I've installed the sdk and downloaded the CWM 6.0.4.5 to the platform tools folder. I found an article on androidcentral which explains how to do this on a GN (which looks a lot like an S3) which instructs on how to use the fastboot boot xxxxxx.img command. I'm stuck before that trying to download the CWM to the phone.
Not sure what I'm doing wrong. the instructions suggest booting into the bootloader by using the ADB reboot bootloader command. That puts it in a "downloading... Do not turn off target" screen which is captioned Odin Mode and on the bottom of the text it says Write Protection Enabled. Did I miss a step with Sudo?
the next step is described as running fastboot devices to see if the computer sees it. This gets no response but the prior reboot command would still work. Finally it ignore the fastboot boot command as it did the fastboot devices command.
Can anyone tell me where I've dropped the ball and what to do?
bump
You can't use fastboot with Note 3. It's not supported. But you can run adb backup I guess. Also you can image partitions with dd but not familiar with it. Just search the forum...
YOURE LOOKING UP DIRECTIONS FOR THE WRONG PHONE!!! STOP NOW! Never...ever use directions meant for another phone unless it's been confirmed by others that it works; or unless you like being a pioneer.
What exactly are you trying to backup? Your EFS, FSG, modemst1 and modemst2 should be the only backups you need. Everything else is "rebuildable" yourself. If you killed the bootloader msmercy42 started a N900T hard brick unbrick thread. If you have a soft brick you can always Odin the stock firmware.
CAREFUL when playing around in adb. One wrong number means a hard brick. Meaning if you meant to type mmcblk0p3 in a "dd if" command and instead typed mmcblk0p2 you might end up with a device upon reboot shows a completely black screen (hard brick).
Sent from my SPH-L900. Please hit the thanks button if I helped you out!
Help! Please
I have rooted my phone thru odin mode, downloaded a rom to install and it wont let me it says on my screen downloading do not turn off target, what can i do? nothings happening to the phone its been stuck on this screen for an hour.
As far as I know, you install a ROM through a custom recovery, not through Odin.
Sent from my SPH-L900. Please hit the thanks button if I helped you out!
Hi,
I am stuck with a LG G3 US990 on download mode. Following is the history:
1. Restored a LG G3 LS990 Nandroid Backup to device.
2. Flashed Cloudy 1.3 in hopes of getting a sim unlock(sim unlock failed - network was still grayed out)
3. Tried to restore phone back to LS990ZV4 stock using fastboot.
4. Accidentally flashed laf and stock recovery.
5. Stock recovery was accessible for a while and the phone showed "Security Error" when trying to do a normal boot.
6. Above later changed to Download Mode. Now, the phone goes to Download Mode if a normal boot is performed. When tried to get to recovery, it shows "Recovery Mode" but still goes to Download Mode.
When I try to restore phone to LS990ZV4 stock using Flash Tool 1.8, I get an Error: Partition Table change 00000064. When I try to flash it back to US99010a stock using LG Flash Tools 2014(I have to do this as US99010a only has kdz), the phone is never detected. I have tried multiple reboots of my PC, changed com ports and everything possible else than using another PC.
I also tried to extract dll and .dz from the kdz to use on Flash Tool 1.8 but that failed with error: Failed in Previous Load ().
On LG Flash Tool 1.8, the phone is detected and progress goes up to 6% before partition table... error is displayed. Phone Model shows as LGLS990 and IMEI,PID info is unknown.
Any help on this would be greatly appreciated and I would recommend anyone trying to get a sim unlock on US990 should definitely refrain at this moment as I have apparently lost a device in this pursuit.
Thanks to @Abu Siona for all his help so far!
texan_mirage said:
Hi,
I am stuck with a LG G3 US990 on download mode. Following is the history:
1. Restored a LG G3 LS990 Nandroid Backup to device.
2. Flashed Cloudy 1.3 in hopes of getting a sim unlock(sim unlock failed - network was still grayed out)
3. Tried to restore phone back to LS990ZV4 stock using fastboot.
4. Accidentally flashed laf and stock recovery.
5. Stock recovery was accessible for a while and the phone showed "Security Error" when trying to do a normal boot.
6. Above later changed to Download Mode. Now, the phone goes to Download Mode if a normal boot is performed. When tried to get to recovery, it shows "Recovery Mode" but still goes to Download Mode.
When I try to restore phone to LS990ZV4 stock using Flash Tool 1.8, I get an Error: Partition Table change 00000064. When I try to flash it back to US99010a stock using LG Flash Tools 2014(I have to do this as US99010a only has kdz), the phone is never detected. I have tried multiple reboots of my PC, changed com ports and everything possible else than using another PC.
I also tried to extract dll and .dz from the kdz to use on Flash Tool 1.8 but that failed with error: Failed in Previous Load ().
On LG Flash Tool 1.8, the phone is detected and progress goes up to 6% before partition table... error is displayed. Phone Model shows as LGLS990 and IMEI,PID info is unknown.
Any help on this would be greatly appreciated and I would recommend anyone trying to get a sim unlock on US990 should definitely refrain at this moment as I have apparently lost a device in this pursuit.
Thanks to @Abu Siona for all his help so far!
Click to expand...
Click to collapse
try this:
note: that what you are trying to achieve is take the phone into fastboot mode so you can then fastboot flash us990 partition data (laf.bin or laf.img from us990)
plug in the phone thats in download mode
download and extract the attached, change into the extracted folder.
start command prompt in that folder ie
execute ports.bat ( this shows your lg diag amd mdm ports) your diag port i want to assume is com41 (flashtool port)
when in download mode, check your flashtool com port (want to assume is com 41) if not replace appropriately with the right download mode comport. default here is com41
so copy and send this as below (be sure you have the right com port specified):
Send_Command.exe \\.\COM41
this takes you to su (root) and you should have the # sign
then delete the laf file thats causing all the stress by sending the command below:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
with the right port selected after this command it should return #
then reboot phone battery out and in, then power , if all went well you should be back in fastboot mode, then grab the us990 Z4 partition and fastboot flash into phone. you should be good.
link to us990 partition files:
https://mega.co.nz/#!dk9FHbpS!xTI3kWI3BWcp27eoi0GYz-GIzUfRaCucHWZ6KhJnDNE
essojay said:
try this:
note: that what you are trying to achieve is take the phone into fastboot mode so you can then fastboot flash us990 partition data (laf.bin or laf.img from us990)
plug in the phone thats in download mode
download and extract the attached, change into the extracted folder.
start command prompt in that folder ie
execute ports.bat ( this shows your lg diag amd mdm ports) your diag port i want to assume is com41 (flashtool port)
when in download mode, check your flashtool com port (want to assume is com 41) if not replace appropriately with the right download mode comport. default here is com41
so copy and send this as below (be sure you have the right com port specified):
Send_Command.exe \\.\COM41
this takes you to su (root) and you should have the # sign
then delete the laf file thats causing all the stress by sending the command below:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
with the right port selected after this command it should return #
then reboot phone battery out and in, then power , if all went well you should be back in fastboot mode, then grab the us990 Z4 partition and fastboot flash into phone. you should be good.
link to us990 partition files:
https://mega.co.nz/#!dk9FHbpS!xTI3kWI3BWcp27eoi0GYz-GIzUfRaCucHWZ6KhJnDNE
Click to expand...
Click to collapse
Hey,
Thanks a lot for this helpful post! Device now boots in to fastboot mode and though I am able to write most of the files, I am not able to write following files: BackupGPT, rct, PrimaryGPT . The error which I get is "remoteartition table does not exist"
I tried flashing TWRP recovery but instead of going in to recovery the phone goes in to download mode.
Thanks!
texan_mirage said:
Hey,
Thanks a lot for this helpful post! Device now boots in to fastboot mode and though I am able to write most of the files, I am not able to write following files: BackupGPT, rct, PrimaryGPT . The error which I get is "remoteartition table does not exist"
I tried flashing TWRP recovery but instead of going in to recovery the phone goes in to download mode.
Thanks!
Click to expand...
Click to collapse
You ll need to fastboot flash laf.bin if you open / edit the flash.bat laf.bin was not included I think .. just get back to fastboot mode and fastboot flash laf.bin like:
fastboot flash laf laf.bin
reboot and phone should boot normally and all modes should work.
Thanks
essojay said:
You ll need to fastboot flash laf.bin if you open / edit the flash.bat laf.bin was not included I think .. just get back to fastboot mode and fastboot flash laf.bin like:
fastboot flash laf laf.bin
reboot and phone should boot normally and all modes should work.
Thanks
Click to expand...
Click to collapse
Hey,
Thanks much for your reply. I followed your instructions and was able to boot successfully in to fastboot mode.
I proceeded to flash the partitions including laf.bin but the phone still goes in to download mode. I tried flashing partitions of both US990 and LS990 with same results.
Also, I was not able to flash following partitions from either of US990 or LS990:
rct.bin - Error in fastboot while flashing- remote: size too large
PrimaryGPT.bin - Error in fastboot while flashing- remote: Partition table doesn't exists
BackupGPT.bin - Error in fastboot while flashing- remote: Partition table doesn't exists
From my understanding the Partition Table is broken or actually does not exist at all and hence I can not write the OS, I might be incorrect though. I need to figure out how to re-build partition table or broken partition on LG G3.
Any help would be greatly appreciated.
texan_mirage said:
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Sometimes the solution is simple and the brain just won't think in the right direction. I was finally able to restore my US990 back to US990(it got converted in to LS990). The solution is to flash TWRP in fastboot and restore the nandroid backup. MAKE SURE YOU HAVE A NANDROID BACKUP before you get in to the conversion business.
Thanks a ton to @essojay
texan_mirage said:
Sometimes the solution is simple and the brain just won't think in the right direction. I was finally able to restore my US990 back to US990(it got converted in to LS990). The solution is to flash TWRP in fastboot and restore the nandroid backup. MAKE SURE YOU HAVE A NANDROID BACKUP before you get in to the conversion business.
Thanks a ton to @essojay
Click to expand...
Click to collapse
happy you were able to get it back on,, do you know if
us990 is Quad band ie bands 850, 900, 1800 and 1900 .. it doesnt seem to have europe GSM band .. any opinion regading this will be appreciated.
thanks
essojay said:
happy you were able to get it back on,, do you know if
us990 is Quad band ie bands 850, 900, 1800 and 1900 .. it doesnt seem to have europe GSM band .. any opinion regading this will be appreciated.
thanks
Click to expand...
Click to collapse
I can only confirm once I'm able to achieve the unlock. I have now flashed Cloudy 1.3 on the phone again and it's a LS990 now. The Bluetooth and MAC addresses are unavailable and there is no network. I'm thinking what to do next.
essojay said:
happy you were able to get it back on,, do you know if
us990 is Quad band ie bands 850, 900, 1800 and 1900 .. it doesnt seem to have europe GSM band .. any opinion regading this will be appreciated.
thanks
Click to expand...
Click to collapse
@essojay
US990 Bands: LTE B1/B3/B17/B18/B26/B41, WCDMA B1/B2/B5, GSM 900/1800/1900, CDMA BC0/BC6
@Abu Siona
I cannot register on Rogers in Canada apparently because it operates on 850but the phone reads my sim card and also is displaying the phone number.
My device is converted to a LG G3 LS990 and is running Cloudy G3 1.2 . I used shortcut master lite to change the bands. No luck with GSM, can't confirm CDMA functionality. Will be back down south in a few weeks and will then test if this phone works with T-Mobil or any other operator in States.
No download no fastboot
I'm getting emojis and a black screen.. no download mode and no fastboot.. Any ideas would be greatly appreciated, possibly a command to write the new laf.bin , img or boot/recovery img files?
"#dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
0 ☻ ☻ #"
texan_mirage said:
@essojay
US990 Bands: LTE B1/B3/B17/B18/B26/B41, WCDMA B1/B2/B5, GSM 900/1800/1900, CDMA BC0/BC6
@Abu Siona
I cannot register on Rogers in Canada apparently because it operates on 850but the phone reads my sim card and also is displaying the phone number.
My device is converted to a LG G3 LS990 and is running Cloudy G3 1.2 . I used shortcut master lite to change the bands. No luck with GSM, can't confirm CDMA functionality. Will be back down south in a few weeks and will then test if this phone works with T-Mobil or any other operator in States.
Click to expand...
Click to collapse
So whats the conclusion..CAN the US990 work in europe if converted to the LS990? Really wish it could work,love my G3 but cant use it ?
Please help mE my Phone Lg g3 Stuck In Download Moad i Trying To flash But Laf Read Gpt ProbLem Faced Help Me Please How To solve this Problem
As the title says my phone is hard bricked on fastboot:
i was flashing a kdz file via flash tool and i took out the cable before it ends(lolipop kdz) after that i plugged the cable again and a realized that ive lost download mode(laf.img).
i had this problem when i was on kitkat firmware and i solved using the propers commands on fastboot,the thing is fastboot does not respond to any command and theres no way to get out this situation. i know its related with the bootloader and after reading alot and trying a few methods the problem still remais.
i dont know if i have any chance on this or to i have to send the phone to lg
i kindly aprecciate any help on this concern
thanks in advance
same things for me, my lg d855 is stocked in fastboot mode and non accept any things, help please
this problem never happened to anyone? its strange that on fastboot it doesnt respond to the commands erase or flash it kept saying erasing for ever and nothing happen. im no expert thats why i asked for help. i dont know if its soft bricked or hard bricked either way it has to have a solution.ive seen many tutorials and videos but nothing specific to this problem so im wondering if its a new kind of brick.
once again im asking for help,please.
thank all of u
mido3adhalet said:
same things for me, my lg d855 is stocked in fastboot mode and non accept any things, help please
Click to expand...
Click to collapse
windo34 said:
this problem never happened to anyone? its strange that on fastboot it doesnt respond to the commands erase or flash it kept saying erasing for ever and nothing happen. im no expert thats why i asked for help. i dont know if its soft bricked or hard bricked either way it has to have a solution.ive seen many tutorials and videos but nothing specific to this problem so im wondering if its a new kind of brick.
once again im asking for help,please.
thank all of u
Click to expand...
Click to collapse
If you guys cant boot into the os normally the only way you can fix this is through twrp. If you don't have that then im afraid the only way you can fix it is to kick it into Qualcomm USB Loader 9008 mode and reflash from there. I vaguely remember the only variant that fastboot commands work on is VS985 (which ships with a unlocked bootloader), the fastboot commands dont work for any other variants (Someone correct me if im wrong)
How to fix using TWRP shell:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/twrp-2.8.0.0_CHANGEME-signed.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
itsbighead said:
If you guys cant boot into the os normally the only way you can fix this is through twrp. If you don't have that then im afraid the only way you can fix it is to kick it into Qualcomm USB Loader 9008 mode and reflash from there. I vaguely remember the only variant that fastboot commands work on is VS985 (which ships with a unlocked bootloader), the fastboot commands dont work for any other variants (Someone correct me if im wrong)
How to fix using TWRP shell:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/twrp-2.8.0.0_CHANGEME-signed.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Click to expand...
Click to collapse
thanks for the tip:good:
tell me one thing i have to write those commands one fastboot rigth?its like a bypass to enter recovery?cause if i have to write that and on fastboot it passes i think im good to go
windo34 said:
thanks for the tip:good:
tell me one thing i have to write those commands one fastboot rigth?its like a bypass to enter recovery?cause if i have to write that and on fastboot it passes i think im good to go
Click to expand...
Click to collapse
You cant write it in fastboot
you can only write it using adb or twrp terminal shell
itsbighead said:
You cant write it in fastboot
you can only write it using adb or twrp terminal shell
Click to expand...
Click to collapse
can u kindly post a link to the tool?using adb or the terminal shell i have to put the recovery.img on sdcard and then write the commands.
thanks in advance
Alright here's the story. I was trying to put CM on this rooted LP 5.0.1 tmobile d851 (20e i think). I backed up and removed the LAF in order to access fastboot so i could flash the custom recovery. fastboot would send the recovery, but the phone would never actually flash the img to the device and report done. Even "fastboot reboot" did nothing. "fastboot devices" reported the serial as "?" and no driver or Arch/CentOS/other windows installs would get fastboot working. fastboot showed up as Marshal london bootloader in device manager.
So then i tried using flash_image from inside of rooted LP to flash the recovery however i ran into PIE errors that could be fixed by replacing /usr/bin/linker. So I found a patched version, rm -rf the old one and tried to cp in the new one. This seemed like a totally valid idea from my linux experience. Buuuut crap. Nothing works. No commands are accepted because I deleted linker. I rebooted cause I had no better alternative and i get a dead android "no command".... Looks like I found the single best way to kill an android installation.
Now im really stuck because i cant use download mode (LAF) to restore because it has been deleted to access fastboot and fastboot wont actually do anything so I can't restore the laf. There is no custom recovery. The stock recovery adb sideload will only let me install OTAs and far as i know there isn't a FULL OTA that will restore the entire system. I even tried the qualcomm 9008 hard brick method with boardDiag, but that doesnt work on tmobile.
I see a few options:
Somehow get fastboot and then download mode working
Wait for a 6.0 OTA and hope it updates the linker bin
advise?
also, the LG logo appears on screen and the LG serial port (the one used for the LG flasher tool) is present in my device manager for a good 15secs before the no command android shows up. I tried lg flasher tool with this time window but it always cut out before the tool could get anywhere.
Edit: This is what the fastboot process would look like:
Screen right after fastboot boot:
[500] Fastboot mode started
[600] -- reset --
[610] -- portchange --
[710] fastboot: processing commands
fastboot erase aboot brings:
erasing 'aboot' ... on command prompt
and
[346290] fastboot: getvarartition-type:aboot
[346350] fastboot: erase:aboot
after those appear it just hangs like that
unplugging it after that command gives me:
FAILED (status read failed (Too many links))
finished. total time: 164.350s
on cmd
and
[514820] -- reset --
[514820] EP1/out FAIL nfo=40 p0=f90bao0
[514830] -- portchange --
[514840] usb_read(0) transaction failed
[514890] fastboot: oops!
[514940] fastboot: processing commands
Click to expand...
Click to collapse
Did you ever find a fix for this?
No, its either professional jtag, or maybe the MM stock ota update zip will fix it if it includes the linker. i havent found this ota on the Internets yet though.
i just had the same problem. any fixes?
flash laf via fastboot
sirbow2 said:
Alright here's the story. I was trying to put CM on this rooted LP 5.0.1 tmobile d851 (20e i think). I backed up and removed the LAF in order to access fastboot so i could flash the custom recovery. fastboot would send the recovery, but the phone would never actually flash the img to the device and report done. Even "fastboot reboot" did nothing. "fastboot devices" reported the serial as "?" and no driver or Arch/CentOS/other windows installs would get fastboot working. fastboot showed up as Marshal london bootloader in device manager.
So then i tried using flash_image from inside of rooted LP to flash the recovery however i ran into PIE errors that could be fixed by replacing /usr/bin/linker. So I found a patched version, rm -rf the old one and tried to cp in the new one. This seemed like a totally valid idea from my linux experience. Buuuut crap. Nothing works. No commands are accepted because I deleted linker. I rebooted cause I had no better alternative and i get a dead android "no command".... Looks like I found the single best way to kill an android installation.
Now im really stuck because i cant use download mode (LAF) to restore because it has been deleted to access fastboot and fastboot wont actually do anything so I can't restore the laf. There is no custom recovery. The stock recovery adb sideload will only let me install OTAs and far as i know there isn't a FULL OTA that will restore the entire system. I even tried the qualcomm 9008 hard brick method with boardDiag, but that doesnt work on tmobile.
I see a few options:
Somehow get fastboot and then download mode working
Wait for a 6.0 OTA and hope it updates the linker bin
advise?
also, the LG logo appears on screen and the LG serial port (the one used for the LG flasher tool) is present in my device manager for a good 15secs before the no command android shows up. I tried lg flasher tool with this time window but it always cut out before the tool could get anywhere.
Edit: This is what the fastboot process would look like:
Click to expand...
Click to collapse
download laf file for your model and flash it....
"fastboot erase laf" then
"fastboot flash laf laf.img"
"fastboot reboot"
Then try to put your phone into download mode.
nibedankaran said:
download laf file for your model and flash it....
"fastboot erase laf" then
"fastboot flash laf laf.img"
"fastboot reboot"
Then try to put your phone into download mode.
Click to expand...
Click to collapse
thanks for the reply, but as i mentioned in my post, fastboot commands don't work. i wish it was that easy.
nibedankaran said:
download laf file for your model and flash it....
"fastboot erase laf" then
"fastboot flash laf laf.img"
"fastboot reboot"
Then try to put your phone into download mode.
Click to expand...
Click to collapse
I think you have a serious problem
You have to see google fix lg g3 on Qualcomm mode...I mean hard brick fix....
Download as instructed
I think it will be fixed
Recently I fixed lg g3 from only led blink no signal to pc and only vibrate and others
That doesn't work on tmobile G3s, thanks though. I did try it anyways btw.
Getting the update.zip from a friend. its in the SD card but its not showing up in MTP so were trying to figure that out. once i have the zip ill try flashing it. if it doesnt work, itll get a octoplus jtag flash.
Well the update did not like the fact that this phone was missing the linker bin or the previous root because it fails when checking the current system. Looks like octoplus is the only way cause i'm an idiot.
Anyone know where i can send this to get it done? i thought some people on ebay did it but i cant find them.
I have same problem, no download mode, system corrupted and recovery is useless.
mysteryjeans said:
I have same problem, no download mode, system corrupted and recovery is useless.
Click to expand...
Click to collapse
If it's a tmobile G3 (d851) you have no choice but send it to someone for an octoplus jtag service because the DIY jtag method doesn't work. Got mine done for $42 after shipping from an ebay service.
sirbow2 said:
If it's a tmobile G3 (d851) you have no choice but send it to someone for an octoplus jtag service because the DIY jtag method doesn't work. Got mine done for $42 after shipping from an ebay service.
Click to expand...
Click to collapse
Finally I recovered it, I have to short testpoint then connect cable to PC, my device is dual sim therefore different logic board, see this http://forum.xda-developers.com/lg-g3/help/lg-d858-qualcomm-test-location-t3293440 for D856/7/8 testpoint to get device into Qualcomm 9008 mode, then I had flash F400K (yes korean rom) tot from thread http://forum.xda-developers.com/showthread.php?t=2785089 using BoardDiagv2.99 http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359 to get it live and get into download mode.
Now finally flashed stock KDZ using this post http://forum.xda-developers.com/showpost.php?p=64624353&postcount=3
If I knew there is new tool to flash MM stock, I wouldn't brick my device. :silly:
Thats exactly what i tried but didn't work because D851
After a couple weeks of on and off searching the internet, I finally got a couple GSI ROMs from the treble forum to boot up; so I'm posting this guide in hopes it saves somebody else all the searching
A couple things to note:
You and only yourself are doing this at your own risk. Unlocking your bootloader voids warranty
Have your stock images ready to flash in case of a brick
You must have an unmodified boot.img installed, the Moto REALLY doesn't like clean booting with a modified boot.img. I've tried every combination in magisk when patching a boot.img (keep & remove DM-Verity/Encryption) with no success on Stock and a GSI
Most things should work fine, text are reported to not work unless you change your network mode to 3G
Android 10 brought two fastboot modes to the game. Bootloader and Fastbootd. Since the Moto uses dynamic partitions we have to use fastbootd for this.
The Moto is 64-bit and uses A/B partitions so use arm64 A/B images
Lastly, BACK UP YOUR DATA, you will lose your data
Requirements
Install ADB & Fastboot from here
https://developer.android.com/studio/releases/platform-tools
You must have an unlocked bootloader. You can follow these instructions here
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Download this vbmeta.img from here
https://dl.google.com/developers/android/qt/images/gsi/vbmeta.img
A GSI ROM you want to flash
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
Instructions:
Boot into fastbootd
Code:
adb reboot fastboot
Install the vbmeta.img
Code:
fastboot --disable-verification flash vbmeta vbmeta.img
Erase the system partition
Code:
fastboot erase system
Install the GSI of your choice
Code:
fastboot -w flash system GSI.img
If you get an error about resizing the partition run this command and try again
Code:
fastboot delete-logical-partition product_#
Replace # with a or b depending on what slot you're flashing toReboot and finish
Code:
fastboot reboot
You might boot into a screen that says to factory reset, do it and it should boot fine. It might happen another time or two (if it keeps happening, you've bootlooped, flash your stock images)
Recover/Back to Stock:
If your device bricked or you just want to go back to 100% stock, you can download the smart recover tool from here:
https://support.lenovo.com/us/en/downloads/ds101291
Recover Tool not working?
You can download the firmware from here:
Retail:
https://forum.xda-developers.com/mo...t/stock-rom-motorola-g-stylus-retail-t4104451
Metro:
https://forum.xda-developers.com/mo...30-80-64-3-t4138681/post83146807#post83146807
- Bricked devices are usually recoverable if they can still get into fastboot
Advanced Tips:
(Anytime you see # in a code box, replace with a or b depending on what slot you want)
- Since the Moto uses a A/B layout it's possible to have two different ROMs installed, but with no decryption it's not possible to share data between them, you have to factory reset every time you want to switch
- I personally like to have slot_a as a stock backup and slot_b set as active for flashing, make sure you flashed the bootloader to slot_b before switching slots
- You can flash or erase a specific slot if desired
Just put the slot after the partition name
Code:
fastboot erase system_#
Code:
fastboot --disable-verification flash vbmeta_# vbmeta.img
- You can change your current active slot with
Code:
fastboot --set-active=#
- Its helpful to use adb to dd some partitions on stock ROM like system and vendor, to make it easier going back to stock/fixing bricks:
Full Instructions here: https://forum.xda-developers.com/pr...si-porting-tools-android-auto-script-t4089193
- Requires Root
System:
Code:
dd if=/dev/block/mapper/system_# of=/storage/emulated/0/Download/system.img
Vendor:
Code:
dd if=/dev/block/mapper/vendor_# of=/storage/emulated/0/Download/vendor.img
Product:
Code:
dd if=/dev/block/mapper/product_# of=/storage/emulated/0/Download/product.img
VBmeta:
Code:
dd if=/dev/block/by-name/vbmeta_# of=/storage/emulated/0/Download/vbmeta.img
Boot:
Code:
dd if=/dev/block/by-name/boot_# of=/storage/emulated/0/Download/boot.img
Thank you for this guide. I was just able to install Phh's latest AOSP FLOSS (v221) GSI using your guide. Also, my data, SMS, and phone calls all worked. My device is on t-mobile.
The only issue I see so far is that the overlay for the punch hole camera is not correct. The time is currently behind the punch hole camera.
SnowStruk said:
Thank you for this guide. I was just able to install Phh's latest AOSP FLOSS (v221) GSI using your guide. Also, my data, SMS, and phone calls all worked. My device is on t-mobile.
The only issue I see so far is that the overlay for the punch hole camera is not correct. The time is currently behind the punch hole camera.
Click to expand...
Click to collapse
Hmm I'm on T-Mobile/Metro too. Maybe I was just doing something wrong, glad you found it helpful though! ?
DMedina559 said:
Hmm I'm on T-Mobile/Metro too. Maybe I was just doing something wrong, glad you found it helpful though!
Click to expand...
Click to collapse
Upon further testing, receiving text messages is not working correctly. I am not receiving new text messages, until a reboot of the device then they all come in at once. Then to receive more text messages I need to do another reboot.
Inbound and outbound calling works. LTE data works as well.
SnowStruk said:
Upon further testing, receiving text messages is not working correctly. I am not receiving new text messages, until a reboot of the device then they all come in at once. Then to receive more text messages I need to do another reboot.
Inbound and outbound calling works. LTE data works as well.
Click to expand...
Click to collapse
Did you capture logs of your SMS app/rcs service?
mrbubs3 said:
Did you capture logs of your SMS app/rcs service?
Click to expand...
Click to collapse
So the issue appears to be more intermittent. It seems if I wait long enough the text messages may come in on their own. I usually have to wait 2-4 hours, however I just did another test this morning where I sent two test text messages, and I received one after about 5 minutes, and it has now been 30+ minutes and I still have not received my second text message.
Here are the logs from the Silence app.
https://1drv.ms/t/s!AjI_xrwAxdGkqOla3nr6b7WvVDqzcg?e=RTSIvw
Right around 9:45 I received one of the two text messages that I sent around 9:40.
Also, here are the adb logs in case they help.
https://1drv.ms/t/s!AjI_xrwAxdGkqOlb6CkRMzgSucZAvg?e=n8Bf5j
Every time I try to flash a system omg it fails at the 3rd portion. Am I doing something wrong?
JimmyJurner said:
Every time I try to flash a system omg it fails at the 3rd portion. Am I doing something wrong?
Click to expand...
Click to collapse
Gapps and Floss version flashed fine for me, try this:
Code:
fastboot flash system GSI.img
fastboot -w
DMedina559 said:
Gapps and Floss version flashed fine for me, try this:
Click to expand...
Click to collapse
I'm getting the same thing. It won't pass the 3rd portion of the flash. I'm supposed to be in fastbootd right?
JimmyJurner said:
I'm getting the same thing. It won't pass the 3rd portion of the flash. I'm supposed to be in fastbootd right?
Click to expand...
Click to collapse
Yess you want to use fastbootd
You're using an Android 10 image right? I can't think of anything else unless it's a driver or a fastboot install issue, but I doubt it is
DMedina559 said:
Yess you want to use fastbootd
You're using an Android 10 image right? I can't think of anything else unless it's a driver or a fastboot install issue, but I doubt it is
Click to expand...
Click to collapse
Yes. I've tried almost every one of these. They all work on my other phones but this one keeps getting the same error. I'll try a different computer and let ya know the results.
JimmyJurner said:
I'm getting the same thing. It won't pass the 3rd portion of the flash. I'm supposed to be in fastbootd right?
Click to expand...
Click to collapse
Yes in fastbootd.
Did you try running the command to delete the partition? I had to do that step for it to work for me.
Code:
fastboot delete-logical-partition product_#
SnowStruk said:
Yes in fastbootd.
Did you try running the command to delete the partition? I had to do that step for it to work for me.
Code:
fastboot delete-logical-partition product_#
Click to expand...
Click to collapse
so run that 1st?
fastboot delete-logical-partition product_a
fastboot: usage: unknown command delete-logical-partition
Thats whats coming up.
JimmyJurner said:
Yes in fastbootd.
Did you try running the command to delete the partition? I had to do that step for it to work for me.
so run that 1st?
fastboot delete-logical-partition product_a
fastboot: usage: unknown command delete-logical-partition
Thats whats coming up.
Click to expand...
Click to collapse
Update your ADB. I just realized minimal adb hasn't been updated since 2018. Use the one I linked in the first post. It's a minimal adb & fastboot directly from google
DMedina559 said:
Update your ADB. I just realized minimal adb hasn't been updated since 2018. Use the one I linked in the first post. It's a minimal adb & fastboot directly from google
Click to expand...
Click to collapse
You sir are a gentleman and a scholar! I haven't updated my adb in awhile lol!
Worked like a charm.
Thank you all for the help!
So far I've gotten lineage os and havoc os to boot. Havocs face unlock crashes on setup. Keep ya guys posted...
SnowStruk said:
So the issue appears to be more intermittent. It seems if I wait long enough the text messages may come in on their own. I usually have to wait 2-4 hours, however I just did another test this morning where I sent two test text messages, and I received one after about 5 minutes, and it has now been 30+ minutes and I still have not received my second text message.
Here are the logs from the Silence app.
https://1drv.ms/t/s!AjI_xrwAxdGkqOla3nr6b7WvVDqzcg?e=RTSIvw
Right around 9:45 I received one of the two text messages that I sent around 9:40.
Also, here are the adb logs in case they help.
https://1drv.ms/t/s!AjI_xrwAxdGkqOlb6CkRMzgSucZAvg?e=n8Bf5j
Click to expand...
Click to collapse
I was able to find a reliable workaround to the SMS issue for now. I went into Settings -> Network & Internet -> Mobile Network and changed my Preferred network type from LTE to 3G and now all my text messages come in right away.
Is anyone else with a GSI having SMS issues? I am wondering if I can change some APN settings to get it work reliably with LTE being the preferred network.
SnowStruk said:
I was able to find a reliable workaround to the SMS issue for now. I went into Settings -> Network & Internet -> Mobile Network and changed my Preferred network type from LTE to 3G and now all my text messages come in right away.
Is anyone else with a GSI having SMS issues? I am wondering if I can change some APN settings to get it work reliably with LTE being the preferred network.
Click to expand...
Click to collapse
I changed the apn to T-Mobile and was no change. Had to switch to hspa to get it working
Fyi don't change slots and try anything. It super bricks. No response what so ever...