Database Develop

Stuck at X logo

I'm stuck at X logo, I already tried to flash recovery.img thru fastboot but no luck. I can go to bootloader though. Anyone can help me please?

http://files.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=recovery-RA-passion-v2.2.1.img
download this, rename it to recovery.img (if your using windows be careful how you name it as it may hide file extensions from you ie dont name it recover.img.img)
boot into fastboot mode on phone, have connected to computer via usb, open cmd/terminal in location of image
fastboot flash recovery recovery.img
so long as you dont get an errors
fastboot reboot-bootloader
now scroll to recovery and select it
if you got errors, let me know and ill help

demkantor said:
http://files.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=recovery-RA-passion-v2.2.1.img
download this, rename it to recovery.img (if your using windows be careful how you name it as it may hide file extensions from you ie dont name it recover.img.img)
boot into fastboot mode on phone, have connected to computer via usb, open cmd/terminal in location of image
fastboot flash recovery recovery.img
so long as you dont get an errors
fastboot reboot-bootloader
now scroll to recovery and select it
if you got errors, let me know and ill help
Click to expand...
Click to collapse
This is really strange. I arleady flash 4ext and amon_ra. And when I boot to recovery Im stuck at X logo. I already followed this http://forum.xda-developers.com/showthread.php?t=1576102. After following that guide I have STOCK hboot now..

first off, write down everything it says on hboot screen

demkantor said:
first off, write down everything it says on hboot screen
Click to expand...
Click to collapse
blackrose -by lecahel(dla5244)
stock-145/95/196
nexusone pvt eng s-off
hboot-7.35..5017 (pb9911000)
microp-0b15
touch panel-synt0103
radio-5.08.00.04
apr 21 2012

https://www.box.com/s/f74848b2c5ee61e952c6
flash this through fastboot
fastboot flash hboot hboot.img
(change file names as needed)
then do what i said before about flashing recovery
if you get stuck or it wont work, copy and past your input/output from cmd/terminal
(use code wraps or pastepin to post)

demkantor said:
https://www.box.com/s/f74848b2c5ee61e952c6
flash this through fastboot
fastboot flash hboot hboot.img
(change file names as needed)
then do what i said before about flashing recovery
if you get stuck or it wont work, copy and past your input/output from cmd/terminal
(use code wraps or pastepin to post)
Click to expand...
Click to collapse
Only hboot.img inside the zip file that I gonna flash in hboot? OR the whole .zip file?
Edit: Im stuck.
C:\android-sdk\platform-tools>fastboot flash hboot hboot.img
sending 'hboot' (512 KB)...
OKAY [ 0.087s]
writing 'hboot'...
OKAY [ 0.187s]
finished. total time: 0.275s
C:\android-sdk\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' (3366 KB)...
OKAY [ 0.478s]
writing 'recovery'...
OKAY [ 1.187s]
finished. total time: 1.666s
C:\android-sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.029s]
finished. total time: 0.030s
C:\android-sdk\platform-tools>
Click to expand...
Click to collapse

yes just flash the .img (extract from .zip)
do it again, this time skip the fastboot reboot-bootloader
just flash the hboot
then flash the recovery
then right after you get the okay use volume rocker to choose recovery

demkantor said:
yes just flash the .img (extract from .zip)
do it again, this time skip the fastboot reboot-bootloader
just flash the hboot
then flash the recovery
then right after you get the okay use volume rocker to choose recovery
Click to expand...
Click to collapse
Still at stuck X logo.. :crying::crying:

fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash hboot hboot.img
fastboot flash recovery recovery.img
Use the recovery and hboot I linked you, or go to amonras thread and download there and check md5sum, if this dosent work consider replacing blackrose with a stock engineering bootloader
Sent from my HTC Vision using xda premium

demkantor said:
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash hboot hboot.img
fastboot flash recovery recovery.img
Use the recovery and hboot I linked you, or go to amonras thread and download there and check md5sum, if this dosent work consider replacing blackrose with a stock engineering bootloader
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Thanks for the effort man. I fixed it using PASSIMG.ZIP, back to stock ROM. Thank you..

[Q] Help? Softbrick, stuck in AP Fastboot: Security Version Downgraded / Boot Failure

Hey guys, I did something really stupid.
I acquired an Atrix HD through a third party, network/sim unlocked it to work on T-Mobile, and tried to flash 4.1.2 Mexican Retail (MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX) through RSD Lite 6.1.5 after removing the getvar command and.. it failed half way. I forgot to unlock the bootloader before flashing.
Now I'm stuck and I've tried almost everything to fix it. I've searched Google and XDA, in the process I have downloaded Myth Tools, sirhoover_atrixhd_utility, motochopper, motopocalypse, and moto-fastboot, tried them all to the best of my knowledge and nothing is working. I've even edited the XML file to exclude the files it fails on.
Common errors I encounter:
Fastboot reason: Boot failure
Fastboot reason: Flash failure
Partition (boot) Security Version Downgraded
Preflash Validation Failed for boot
Partition (system) Security Version Downgraded
PIV black validation for system failed
Invalid PIV image: system
Worst part is, I can't unlock my bootloader because I need ADB to do so! Recovery will give me ADB but only to sideload (available on certain recoveries I've managed to flash). If you have any ideas or information that could assist me in getting my phone back to normal, whether that's unlocking the bootloader through fastboot or flashing a stock rom sucessfully, I would greatly appreciate it! :good:

You don't need a unlocked bootloader to flash firmware through rsd.. Try flashing the stock att back.
Sent from my PACMAN MATRIX HD MAXX

deeje00 said:
You don't need a unlocked bootloader to flash firmware through rsd.. Try flashing the stock att back.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
Thanks for your reply
I've tried flashing several stock firmwares already, I get preflash validation failed errors every time on boot.img and system.img
Here's the firmwares I have downloaded:
MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX
MB886_bell-user-4.1.2-9.8.2Q-8_MB886_FFW-11-4-release-keys-BellMobility-CA
MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA
7.7.1Q-144_MB886_MR1-22_SIGNED_CFC
7.7.1Q-115_MB886_FFW-14_SIGNED_CFC
I wish I knew exactly the version I had before I started flashing, but unfortunately I do not..

DaveTheRave said:
Thanks for your reply
I've tried flashing several stock firmwares already, I get preflash validation failed errors every time on boot.img and system.img
Here's the firmwares I have downloaded:
MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX
MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA
7.7.1Q-144_MB886_MR1-22_SIGNED_CFC
7.7.1Q-115_MB886_FFW-14_SIGNED_CFC
I wish I knew exactly the version I had before I started flashing, but unfortunately I do not..
Click to expand...
Click to collapse
Once your phone's OS has been upgraded, I don't think you can flash to an older firmware unless you have an unlocked bootloader. I'm not sure but that maybe the reason you're getting validation errors.
Did you try re-downloading the firmware?

audit13 said:
Once your phone's OS has been upgraded, I don't think you can flash to an older firmware unless you have an unlocked bootloader. I'm not sure but that maybe the reason you're getting validation errors.
Did you try re-downloading the firmware?
Click to expand...
Click to collapse
Just tried re-downloading everything on a brand new Windows install on a different computer, still having problems.
No matter how hard I try, I cannot get boot.img or system.img to flash from any Stock firmware, whether it's AT&T, Mex, or Bell
Using snap-fastboot:
snap-fastboot flash boot boot.img
sending 'boot' (10240 KB)...
OKAY [ 0.788s]
writing 'boot'...
Preflash validation failed
FAILED (remote failure)
snap-fastboot flash system system.img
sending 'system' (30720 KB)...
OKAY [ 2.343s]
writing 'system'...
Preflash validation failed
FAILED (remote failure)
I'm going to try making a Motorola Factory cable in the meantime. Any other suggestions?
EDIT: Factory cable didn't help.. is there a way to generate a higher security version? No matter what, the bootloader always displays Partition (boot/system) Security Version Downgraded
I really don't want this to end up being a paperweight

Is this where you got the firmware: http://sbf.droid-developers.org/dinara/list.php ?
Did you reboot each time you loaded a different set of fastboot files? Did you remove the previous fastboot files before installing a new set of fastboot files? Are you able to try this on a different computer?

I just got a new Atrix HD replacement and its showing firmware of 9.8.0Q-97_MB886_FFW-20 . Its not the same as the firmware available here: http://sbf.droid-developers.org/ .... I get the same error even after modifying the XML file in the SBF. Wonder if the last update caused an issue. Running into some similar issue with the replacement. Its not wanting to bootloader unlock.

Did you mount the system before installing?
Sent from my SAMSUNG-SGH-I537 using xda app-developers app

Found a fix for the AP Fastboot loop
List of commands to type in. ( in order)
1. adb reboot bootloader
2.fastboot oem fb_mode_set
3.fastboot oem fb_mode_clear
3.fastboot erase userdata
4.fastboot erase cache
5.fastboot reboot
Source:http://www.droidrzr.com/index.php/topic/17320-sticky-bit-fastboot/

Sorry I've been MIA, been busy with work.
TabascoTX said:
Found a fix for the AP Fastboot loop
List of commands to type in. ( in order)
1. adb reboot bootloader
2.fastboot oem fb_mode_set
3.fastboot oem fb_mode_clear
3.fastboot erase userdata
4.fastboot erase cache
5.fastboot reboot
Source:http://www.droidrzr.com/index.php/topic/17320-sticky-bit-fastboot/
Click to expand...
Click to collapse
Thanks for the reply! I wished this worked for me. After completing the steps successfully, I get:
Partition (boot) Security Version Downgraded
Fastboot Reason: Boot Failure
Code:
adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
fastboot oem fb_mode_set
...
OKAY [ 0.006s]
finished. total time: 0.006s
fastboot oem fb_mode_clear
...
OKAY [ 0.005s]
finished. total time: 0.005s
fastboot erase userdata
erasing 'userdata'...
OKAY [ 3.095s]
finished. total time: 3.095s
fastboot erase cache
erasing 'cache'...
OKAY [ 1.669s]
finished. total time: 1.669s
fastboot reboot
rebooting...
finished. total time: 0.005s
audit13 said:
Is this where you got the firmware: http://sbf.droid-developers.org/dinara/list.php ?
Did you reboot each time you loaded a different set of fastboot files? Did you remove the previous fastboot files before installing a new set of fastboot files? Are you able to try this on a different computer?
Click to expand...
Click to collapse
That's exactly where I got my firmwares from. And to answer your question, I have tried this on different computers but I wasn't doing much rebooting when changing fastboot files.

DaveTheRave said:
...I have tried this on different computers but I wasn't doing much rebooting when changing fastboot files.
Click to expand...
Click to collapse
Try logging off and back on to see what happens. For me, using fastboot/adb commands on an x86 Win7 machine works more consistently than using an x64 Win7 machine.

TabascoTX said:
Found a fix for the AP Fastboot loop
List of commands to type in. ( in order)
1. adb reboot bootloader
2.fastboot oem fb_mode_set
3.fastboot oem fb_mode_clear
3.fastboot erase userdata
4.fastboot erase cache
5.fastboot reboot
Source:http://www.droidrzr.com/index.php/topic/17320-sticky-bit-fastboot/
Click to expand...
Click to collapse
When I run fastboot oem fb_mode_set, it just says "< waiting for any device >"

Sorry for the late reply. make sure you have adb installed and the drivers for the Atrix. Also,if possible and not in a boot loop or stuck in fastboot, device debugging should be enabled.

Boot problem
Hello here I have a problem and I made everything from my knowledge but It's not fixed.
I have a Motorola Droid Maxx X8 verison XI1080, version 4.4.4, built number SU4.21,
If I install or do something and I switch off and I turn on my phone it disappears as if it is never done and if I try to reinitialize the phone I have a error Fastboot Reason: Boot Failure
If I get the fastboot and I take recovery its said Boot up failed.
I did everything I flashed with RSD and I update it with Motorola update but still nothing we see that the flashing and the update works but on reboot Its has no effect on the phone its stays as if you did nothing.
Please help me! I look forward to a solution, I thank you more.

have u solved the problem
Please explain how u have solved the problem ,my moto g4 plus in same problems

Bootloop - Recovery not working

Hi Everyone,
Don't know what I did wrong but at the moment i stucked with a bootloop. I was trying to flash a 4.4 Rom on a Cyanogenmod 4.2.2
Now I can enter in bootloader but not into the recovery. When I try to boot into recovery it simply tries to boot the phone.
Bootloader i unlocked (it says tampered) but S-ON.
Tried to fastboot the recovery of clockworkmod but still can't enter in it.
How I can restore the phone to its original factory image?
Thnaks

It's seems you are not the only one.
Enter bootloader and choose fastboot.
Then run a command prompt in your PC, cd to the fastboot folder and write fastboot flash recovery filename.img
I suggest you download and flash twrp 2.6.3.0
Then check if the recovery has been installed successfully.If yes, go into recovery and type in the command prompt in your PC the following:
Adb push filename.Rom /data/media/0
Filename.zip stands for the Rom you wanna flash. After its done you can flash that file with twrp
Sent from my HTC One using Tapatalk

I think the cache just needs wiping with the command:
fastboot erase cache
Worked for me once or twice
Sent from my HTC One using XDA Premium 4 mobile app

thanks guys,
as i said i already tried to flash the recovery with the fastboot flash command.
I tried CMW and TWRP... but still can't enter into the recovery.
I have to try the erase cache command....
will let you know!

Did you find a solution? I am in the same boat and it is actually quite annoying.
gerazzo said:
thanks guys,
as i said i already tried to flash the recovery with the fastboot flash command.
I tried CMW and TWRP... but still can't enter into the recovery.
I have to try the erase cache command....
will let you know!
Click to expand...
Click to collapse

The_Doctor_Who said:
Did you find a solution? I am in the same boat and it is actually quite annoying.
Click to expand...
Click to collapse
Yes solved for me with the erase cache command and fastboot recovery the latest TRWP
Than i flashed the AR ROM...
bye

gerazzo said:
Yes solved for me with the erase cache command and fastboot recovery the latest TRWP
Than i flashed the AR ROM...
bye
Click to expand...
Click to collapse
Thanks. Unfortunately I cannot boot in to the custom recovery. It skips the recovery and jumps directly to the google screen.

The_Doctor_Who said:
Thanks. Unfortunately I cannot boot in to the custom recovery. It skips the recovery and jumps directly to the google screen.
Click to expand...
Click to collapse
^^^^ fastboot erase cache will solve that

nkk71 said:
^^^^ fastboot erase cache will solve that
Click to expand...
Click to collapse
Unfortunately I've typed fastboot erase cache until I'm blue in the face and it still will not boot into the custom recovery. Trust me, I wish I could get it to work for me.

The_Doctor_Who said:
Unfortunately I've typed fastboot erase cache until I'm blue in the face and it still will not boot into the custom recovery. Trust me, I wish I could get it to work for me.
Click to expand...
Click to collapse
okay, i trust you, can i have a little info on your state:
hboot version
which recovery are you using (name and version please )
and you are unlocked right?

nkk71 said:
okay, i trust you, can i have a little info on your state:
hboot version
which recovery are you using (name and version please )
and you are unlocked right?
Click to expand...
Click to collapse
Sure! H-boot 1.54, s -On, I have tried both locked and unlocked (via fasboot oem lock and unlock). I originally tried CWM touch, then gave TWRP a try. No luck booting to either. I get success on the cmd with loading, but cannot get it into recovery. I select recovery from the fastboot menu and the phone vibrates, then a second later "Google" appears.
Version of recovery:
CWM 6.0.3.1 and and 6.0.4.3
TWRP: 2.6.6.3 m7

The_Doctor_Who said:
Sure! H-boot 1.54, s -On, I have tried both locked and unlocked (via fasboot oem lock and unlock). I originally tried CWM touch, then gave TWRP a try. No luck booting to either. I get success on the cmd with loading, but cannot get it into recovery. I select recovery from the fastboot menu and the phone vibrates, then a second later "Google" appears.
Click to expand...
Click to collapse
make sure bootloader is unlocked, reboot to booloader/FASTBOOT USB (again make sure the top line or 2nd says UNLOCKED), then get latest CWM (just for this exercise) from here: http://forum.xda-developers.com/showthread.php?t=2173863
fastboot erase cache
fastboot flash recovery recovery-clockwork-touch-6.0.4.5-m7ul.img
fastboot erase cache
fastboot reboot-bootloader
copy/paste command prompt output (all of it pls)
---> and try to enter recovery.
let me know what happens.

nkk71 said:
make sure bootloader is unlocked, reboot to booloader/FASTBOOT USB (again make sure the top line or 2nd says UNLOCKED), then get latest CWM (just for this exercise) from here: http://forum.xda-developers.com/showthread.php?t=2173863
fastboot erase cache
fastboot flash recovery recovery-clockwork-touch-6.0.4.5-m7ul.img
fastboot erase cache
fastboot reboot-bootloader
copy/paste command prompt output (all of it pls)
---> and try to enter recovery.
let me know what happens.
Click to expand...
Click to collapse
Sure. Thank you!
Here is my output:
c:\And>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.055s]
finished. total time: 0.056s
c:\And>fastboot flash recovery recovery-clockwork-touch-6.0.4.5-m7ul.img
target reported max download size of 1526722560 bytes
sending 'recovery' (8746 KB)...
OKAY [ 1.175s]
writing 'recovery'...
OKAY [ 0.675s]
finished. total time: 1.852s
c:\And>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.051s]
finished. total time: 0.051s
c:\And>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.042s]
finished. total time: 0.042s
Tried entering recovery. Black screen for a moment, vibration and then "Google"

The_Doctor_Who said:
Sure. Thank you!
Here is my output:
c:\And>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.055s]
finished. total time: 0.056s
c:\And>fastboot flash recovery recovery-clockwork-touch-6.0.4.5-m7ul.img
target reported max download size of 1526722560 bytes
sending 'recovery' (8746 KB)...
OKAY [ 1.175s]
writing 'recovery'...
OKAY [ 0.675s]
finished. total time: 1.852s
c:\And>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.051s]
finished. total time: 0.051s
c:\And>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.042s]
finished. total time: 0.042s
Tried entering recovery. Black screen for a moment, vibration and then "Google"
Click to expand...
Click to collapse
what is "******** Did you mean to fastboot format this partition?" how come I never get that
is your adb sdk newer or older than mine? I'm still using:
Code:
C:\ADB2>adb
Android Debug Bridge version 1.0.29
Question, are you on GPE hboot (the black one) or normal (the white one)?

nkk71 said:
what is "******** Did you mean to fastboot format this partition?" how come I never get that
is your adb sdk newer or older than mine? I'm still using:
Code:
C:\ADB2>adb
Android Debug Bridge version 1.0.29
Question, are you on GPE hboot (the black one) or normal (the white one)?
Click to expand...
Click to collapse
That's interesting. Here is mine:
c:\adb>adb
Android Debug Bridge version 1.0.26
I'm on the GPE black screen.

The_Doctor_Who said:
That's interesting. Here is mine:
c:\adb>adb
Android Debug Bridge version 1.0.26
I'm on the GPE black screen.
Click to expand...
Click to collapse
1- recommend updating adb sdk, mine isnt even the latest, i think latest is something like 1.0.3xx
2- don't know if this will work in GPE hboot, but try "fastboot boot <recovery>.img", it used to work on 1.44, but stopped on 1.54+, maybe on GPE it still works.

nkk71 said:
1- recommend updating adb sdk, mine isnt even the latest, i think latest is something like 1.0.3xx
2- don't know if this will work in GPE hboot, but try "fastboot boot <recovery>.img", it used to work on 1.44, but stopped on 1.54+, maybe on GPE it still works.[/QUOT
I'm updating now. I tried fastboot boot recovery yesterday and it froze the phone.
Click to expand...
Click to collapse

The_Doctor_Who said:
I'm updating now. I tried fastboot boot recovery yesterday and it froze the phone.
Click to expand...
Click to collapse
yeah, it was crapped in 1.54
i'm gonna have to sign off soon, but will check back tomorrow....
BTW: i wouldn't mind if you hit the thanks button on my posts (the useful ones!)
Cheers.

nkk71 said:
yeah, it was crapped in 1.54
i'm gonna have to sign off soon, but will check back tomorrow....
BTW: i wouldn't mind if you hit the thanks button on my posts (the useful ones!)
Cheers.
Click to expand...
Click to collapse
Of course! I appreciate your time today!

nkk71 said:
1- recommend updating adb sdk, mine isnt even the latest, i think latest is something like 1.0.3xx
2- don't know if this will work in GPE hboot, but try "fastboot boot <recovery>.img", it used to work on 1.44, but stopped on 1.54+, maybe on GPE it still works.
Click to expand...
Click to collapse
I think his recovery partition might be corrupt.. @mike1986. wrote an article about corrupt data partitions(http://android-revolution-hd.blogspot.ch/2013/10/fix-data-htc-one.html) I think it was you who sent me that link.. well.. do you know if it is possible to use some of this commands? But we'd have to get into a state where we can use adb..

[Q] [39a bootstack] Stuck on Secure Booting error, fastboot does not flash images

My VS980, I had updated to 39A through the manual OTA method, rooted with the new LG root method, everything worked fine, until I flashed a wrong boot.img file using the dd command. Now the boot screen says Secure booting error, and it doesnot boot. I tried getting into the fastboot mode (I erased the laf partition after rooting), but fastboot won't execute any commands
Code:
sh-3.2# fastboot flash recovery recovery.img
target reported max download size of 1862270976 bytes
sending 'recovery' (9712 KB)...
OKAY [ 0.356s]
writing 'recovery'...
^C
sh-3.2#
and it waits for ever at writing recovery, I waited close to an hour before doing ^C.
I didnot install custom recovery yet, and I could get only to factory reset on the recovery screen (using Vol Down + power)
Can someone help me out to get out of this brick?

rishie said:
My VS980, I had updated to 39A through the manual OTA method, rooted with the new LG root method, everything worked fine, until I flashed a wrong boot.img file using the dd command. Now the boot screen says Secure booting error, and it doesnot boot. I tried getting into the fastboot mode (I erased the laf partition after rooting), but fastboot won't execute any commands
Code:
sh-3.2# fastboot flash recovery recovery.img
target reported max download size of 1862270976 bytes
sending 'recovery' (9712 KB)...
OKAY [ 0.356s]
writing 'recovery'...
^C
sh-3.2#
and it waits for ever at writing recovery.
I didnot install custom recovery yet, and I could get only to factory reset on the recovery screen (using Vol Down + power)
Can someone help me out to get out of this brick?
Click to expand...
Click to collapse
http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW8BCUME0231ASHA4A40RQX/VS98027A_05.kdz
install LG drivers to windows 7 PC, download mode, LG Flash tool, KDZ link above, reroot at 27A, Autorec to install TWRP recovery 2.7.0.0, update to Blastagator's latest BUMPED recovery 2.8.5.1, flash 39A XDABBEB's bootstack, flash 39A stock rom made by XDABBEB's (already rooted).

Hi HueyT, Thanks for the reply, but currently I don't have download mode, as I erased laf partition. Now my g2 boots to fastboot mode, with Vol Up + USB Cable. If I can enter the stock recovery menu, then I can try sideloading any files but that too is not working.

rishie said:
Hi HueyT, Thanks for the reply, but currently I don't have download mode, as I erased laf partition. Now my g2 boots to fastboot mode, with Vol Up + USB Cable. If I can enter the stock recovery menu, then I can try sideloading any files but that too is not working.
Click to expand...
Click to collapse
http://forums.androidcentral.com/t-...-installing-custom-recovery-via-fastboot.html

HueyT said:
http://forums.androidcentral.com/t-...-installing-custom-recovery-via-fastboot.html
Click to expand...
Click to collapse
The same command I was trying to execute, but is not working, fastboot doesnot go past writing 'recovery'... step, I waited for almost 1 hour to see if the command completes, but it never completes.

rishie said:
Hi HueyT, Thanks for the reply, but currently I don't have download mode, as I erased laf partition. Now my g2 boots to fastboot mode, with Vol Up + USB Cable. If I can enter the stock recovery menu, then I can try sideloading any files but that too is not working.
Click to expand...
Click to collapse
You need to restore your laf partition. I personally don't have experience doing this, but it looks like there are a couple threads detailing how to do it in fastboot:
http://forum.xda-developers.com/showthread.php?t=2477595
http://forum.xda-developers.com/showthread.php?t=2779007
Instead of using the files included in those threads, downloaded the 39A bootstack zip from the resource thread and extract out the relevant files needed

Thanks for the reply.
I tried all of the following fastboot commands, using the 39a bootstack (ofc, one by one, waited for almost 15-20 min before cancelling the command):
Code:
fastboot erase laf
fastboot flash laf laf.img
fastboot erase boot
fastboot flash boot boot.img
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot -w
All the above commands stop at writing "****" ... section.
Basically the problem is that, the partitions are not getting modified by the fastboot in any way, something like a locked bootloader preventing fastboot from writing anything to the partitions.

G7 plus bricked with relocked bootloader is there a way to fix?

I managed to brick a moto G7 plus to the point of not being able to recover from it (locked bootloader, no twrp, boots to fastboot)
I wanted to go back to 100% stock but failed badly.
My device is odd one. RETLA stream with XT1965-T hardware. Lenovo Rescue apparently don't work on these devices.
1) I flashed stock RETLA latest rom from Lolinet using a flash.bat I made
2) worked and booted fine.....twrp was still intact
3) I did factory reset when booted in.
4) To relock I flashed boot.img and sent lock command a few times
5) Bootloader is now locked but only boots to fastboot and get (YOUR DEVICE HAS LOADED A DIFFERENT OPERATING SYSTEM.
6) I cannot unlock with code because adb says says I need developer option etc.
To repeat: this is BOOTLOADER LOCKED, JUST BOOTS TO FASTBOOT and gives "your device loaded a different operating system) which is not the issue and I expected that.
Bankflash didn't do anything. I mostly get oermission denied with mostly flashing anythiine else.
Any suggestions on how to just get this thing at least bootable again to use?
Thanks.

I have the same problem, but I found a way to at least start the device.
I gave "fastboot boot file.img" with a boot.img patched via Magisk.
But then it stopped working, so I changed the boot.img file to LineageOS.

Anrito Kun said:
I have the same problem, but I found a way to at least start the device.
I gave "fastboot boot file.img" with a boot.img patched via Magisk.
But then it stopped working, so I changed the boot.img file to LineageOS.
Click to expand...
Click to collapse
------------------
I was only able to do what is here: https://forum.xda-developers.com/t/...oem-at-developer-option-moto-g7-plus.4201169/

Anrito Kun said:
------------------
I was only able to do what is here: https://forum.xda-developers.com/t/...oem-at-developer-option-moto-g7-plus.4201169/
Click to expand...
Click to collapse
Thanks for replying to my post. I tried your patched boot.img but when I try to flash it I get " (bootloader) fllash permission denied "
renamed it to boot.img and then....
C:\adb>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (21845 KB)...
OKAY [ 0.465s]
writing 'boot'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.479s

PROBLEM SOLVED. See my post.
https://forum.xda-developers.com/t/moto-g7-plus-no-service.4201229/post-84335207