Stuck in bootloader and getvar all empty - HTC 10 Questions & Answers

Hello everyone,
I've got some trouble with my phone.
The battery was empty I plugged it with the official charger, I heard some crackling. Then it's hard to boot into bootloader, it wo'nt charge.
When I plug it it show the "charging icon" with 0% but without the green progression bar.
I can't relock the bootloader to flash a stock firmware. I'm S-ON.
You can see below my "fastboot getvar all" it's pretty empty so weird :
e_Kit_v1.0\Data>fastboot getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:Surf eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0xe000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x61e000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xef000000
(bootloader) serialno:FA66TBNXXXX
all:
Click to expand...
Click to collapse
Anyone can help me ?
Thanks

That's the way the fastboot getvar all info is gonna look if you're in bootloader. It'll show when you're in download mode.

OK but I can't enter download mode.
I try to flash the *.img directly into bootloader but only hosd_signed.img work but I'm still at the same point.

GaTeRy86 said:
OK but I can't enter download mode.
I try to flash the *.img directly into bootloader but only hosd_signed.img work but I'm still at the same point.
Click to expand...
Click to collapse
If you're in bootloader mode you should be able to boot to download mode from there. It's the third entry from the top. Just navigate to it with the Vol- and confirm with the power button. If there post the getvar all without IMEI and serial number.
And please elaborate a little bit more which image are you trying to flash? Is the only problem that your device doesn't seem to charge or are there more problems you encounter. Did you previously flash a custom recovery or ROM?
Sent from my htc_pmeuhl using XDA Labs

I can't enter into download mode. The screen goes dark and the computer sees the device with "fastboot devices" but no other command works.
I had TWRP and last Venom rom on it. Everything was working fine.
I tried to flash every single img file in the firmware.zip from the last official release.
fastboot flash aboot aboot_signed.img
fastboot flash adsp adsp.img
fastboot flash apdp apdp-8996-1.img
fastboot flash cache cache.img
fastboot flash cmnlib32 cmnlib32.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash cota cota.img
fastboot flash devcfg devcfg-8996-1.img
fastboot flash dsp dsp.img
fastboot flash fsc fsc.img
fastboot flash hosd hosd_signed.img
fastboot flash hyp hyp-8996-1.img
fastboot flash keymaster keymaster.img
fastboot flash lksecapp lksecapp.img
fastboot flash modemst1 modemst1.img
fastboot flash modemst2 modemst2.img
fastboot flash pg2fs pg2fs_ship_signkey.img
fastboot flash pmic pmic-8996-1.img
fastboot flash rcdata rcdata.img
fastboot flash recovery recovery.img
fastboot flash rfg rfg_3.img
fastboot flash rpm rpm-8996-1.img
fastboot flash slpi slpi.img
fastboot flash tz tz-8996-1.img
fastboot flash venus venus.img
fastboot flash xbl xbl-8996-1.img
fastboot flash radio radio.img
Click to expand...
Click to collapse
I read that for some people that fix the problem.
It won't charge and it's also hard to enter bootloader, It goes often directly to black screen with htc written on it.

OK what if you try to boot into download mode even though the screen stays black. After issuing the command fastboot devices, to make sure it is properly recognized and comes back with its serial number in cmd, you could either try to flash the firmware.zip twice using fastboot - as long as it is the proper ZIP for your device. Another possibility would be to flash it from SDCard using the 2PS6IMG.zip method.
Last and least, you could try to run all full official RUU, in case something else git messed up. I assume this is the case, and fear that your try to flash partitions manually maybe just got it worse.
Without the getvar all from download mode I can't help any further, as there aren't enough informations to do so.
Sent from my htc_pmeuhl using XDA Labs

5m4r7ph0n36uru said:
OK what if you try to boot into download mode even though the screen stays black. After issuing the command fastboot devices, to make sure it is properly recognized and comes back with its serial number in cmd, you could either try to flash the firmware.zip twice using fastboot - as long as it is the proper ZIP for your device. Another possibility would be to flash it from SDCard using the 2PS6IMG.zip method.
Last and least, you could try to run all full official RUU, in case something else git messed up. I assume this is the case, and fear that your try to flash partitions manually maybe just got it worse.
Without the getvar all from download mode I can't help any further, as there aren't enough informations to do so.
Sent from my htc_pmeuhl using XDA Labs
Click to expand...
Click to collapse
Thanks for your help,
I can't flash the firmware in downloadmod, the only command which works is fastboot devices.
Flash the entire rom with RUU don't work because I don't have 30% battery and the last solution with SD card don't work too.

GaTeRy86 said:
Thanks for your help,
I can't flash the firmware in downloadmod, the only command which works is fastboot devices.
Flash the entire rom with RUU don't work because I don't have 30% battery and the last solution with SD card don't work too.
Click to expand...
Click to collapse
Try fastboot oem rebootRUU then try flashing the firmware after

xunholyx said:
Try fastboot oem rebootRUU then try flashing the firmware after
Click to expand...
Click to collapse
The phone just reboot and stay at the beginning with the battery logo with the lightning and without charging

GaTeRy86 said:
The phone just reboot and stay at the beginning with the battery logo with the lightning and without charging
Click to expand...
Click to collapse
Sadly welcome to the club , my phone is s-off with exactly the same issue, it's almost two months as a paperweight
It seems that it is difficult to understand even for the most illustrious of this forum that theres is no way to enter to recovery, download mode, RUU mode or whatever other mode in which you can do something more than flashing img in the broken bootloader.
https://forum.xda-developers.com/htc-10/help/htc-10-brick-usa-mex-wall-t3574704

You can't brick it from S-ON. It's just not possible.

tabp0le said:
You can't brick it from S-ON. It's just not possible.
Click to expand...
Click to collapse
That's not true.
Two examples are disconnecting your phone from your PC in the middle of an RUU, or having your phone die or power off during an OTA update.
Those two examples don't apply here, but I'm just pointing out that it is in fact possible.
The OP mentioned that there was a "crackling" noise when he plugged his phone in. Could be a loose wire or connection (which could happen by dropping the phone onto a hard surface) that fried a part of the mother board. That may not be the case here, but it is another way to get a hard brick.
---------- Post added at 11:14 AM ---------- Previous post was at 11:03 AM ----------
GaTeRy86 said:
I can't enter into download mode. The screen goes dark and the computer sees the device with "fastboot devices" but no other command works.
I had TWRP and last Venom rom on it. Everything was working fine.
I tried to flash every single img file in the firmware.zip from the last official release.
Quote:
fastboot flash aboot aboot_signed.img
fastboot flash adsp adsp.img
fastboot flash apdp apdp-8996-1.img
fastboot flash cache cache.img
fastboot flash cmnlib32 cmnlib32.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash cota cota.img
fastboot flash devcfg devcfg-8996-1.img
fastboot flash dsp dsp.img
fastboot flash fsc fsc.img
fastboot flash hosd hosd_signed.img
fastboot flash hyp hyp-8996-1.img
fastboot flash keymaster keymaster.img
fastboot flash lksecapp lksecapp.img
fastboot flash modemst1 modemst1.img
fastboot flash modemst2 modemst2.img
fastboot flash pg2fs pg2fs_ship_signkey.img
fastboot flash pmic pmic-8996-1.img
fastboot flash rcdata rcdata.img
fastboot flash recovery recovery.img
fastboot flash rfg rfg_3.img
fastboot flash rpm rpm-8996-1.img
fastboot flash slpi slpi.img
fastboot flash tz tz-8996-1.img
fastboot flash venus venus.img
fastboot flash xbl xbl-8996-1.img
fastboot flash radio radio.img
I read that for some people that fix the problem.
It won't charge and it's also hard to enter bootloader, It goes often directly to black screen with htc written on it.
Click to expand...
Click to collapse
You shouldn't have flashed the aboot.img
https://forum.xda-developers.com/showpost.php?p=69856732&postcount=972

xunholyx said:
That's not true.
Two examples are disconnecting your phone from your PC in the middle of an RUU, or having your phone die or power off during an OTA update.
Those two examples don't apply here, but I'm just pointing out that it is in fact possible.
The OP mentioned that there was a "crackling" noise when he plugged his phone in. Could be a loose wire or connection (which could happen by dropping the phone onto a hard surface) that fried a part of the mother board. That may not be the case here, but it is another way to get a hard brick.
---------- Post added at 11:14 AM ---------- Previous post was at 11:03 AM ----------
You shouldn't have flashed the aboot.img
https://forum.xda-developers.com/showpost.php?p=69856732&postcount=972
Click to expand...
Click to collapse
Good point! You're absolutely right. I wasn't even thinking about that!

Related

Stock Recovery Issue

Everytime i try and flash the stock image in fastboot it fails when it gets to anything pertaining to the bootloader
FAILED (remote: Do not allow to flash Bootloader image on Unlock device)
My device is unlocked but to try and compat this i even try to re-lock the device which also fails:
FAILED (remote: oem lock back is forbidden)
Im stuck, i cant use the flashall because it fails, i cant individually flash files because the bootloader items fail,
im at a loss as to what to do.
Im able to flash a custom recovery but i cant do anything with it, except try and flash modem items with twrp which also did nothing.
brother, i am sorry for your condition , i dont have much knowledge on such things, but i once had MotoG, i used to flash Stock files with this method..
https://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
if you are flashing Stock files, then Bootloader need not to be stayed UNLOCKED..
hope you get any idea from there.. all the best
---------- Post added at 11:25 AM ---------- Previous post was at 11:23 AM ----------
look in to this also :
https://forum.xda-developers.com/mo...e-restore-moto-e-2015-stock-firmware-t3054303
this might give u anyidea
Did you have TWRP installed before you tried to flash stock Rom ? I'm guessing thats why its failing , but i dont know how to fix
maybe you're trying to flash older version of bootloader than the one you've already got? besides you don't need to flash bootloader to lash the rest, like system, modem or kernel
Okay so i know what my problem is i just dont know how to solve it:
I have a partially unlocked bootloader. is i do the fastboot oem device-info command, it tells me that my bootloader is unlocked but im unable to flash bootloader images (Device critical unlocked: false)
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Device Secure boot: yes
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.080s]
finished. total time: 0.081s
Does anyone know how to get Device critical unlocked: true?
I stuck in the bootanimation and i cant flash a stock rom because there is no such thing. I found one, but this is no flashable zip. And the "flashall.bat" doesnt work. CM also doesnt work. I dont know what to do now.
Edit: Now i dont get into twrp recovery. With adb and with the hardware its not possible to enter twrp.
Did anyone found any solution? I am in same situation...
Found
flash only boot and system, not bootloader
finally while Flashing stock, i am stuck at Bootlogo looop
any suggestions??
i tried unrooting my RR 7.1.1 but with the zip provided , i think it failed..
any way to clean flash / freshly load stock again !!
nandakis4 said:
finally while Flashing stock, i am stuck at Bootlogo looop
any suggestions??
i tried unrooting my RR 7.1.1 but with the zip provided , i think it failed..
any way to clean flash / freshly load stock again !!
Click to expand...
Click to collapse
if you have the stock rom just follow the trouble shooting guide at the start of this thread , should work
Hi, thanks for replying..
flashed the files again,
Boot, recovery, then systemchunk files, REBOOT..
its still bootlooping, i think i am missing any file that needs to be put, but i am not putting .. !!
any more suggestions ??
nandakis4 said:
Hi, thanks for replying..
flashed the files again,
Boot, recovery, then systemchunk files, REBOOT..
its still bootlooping, i think i am missing any file that needs to be put, but i am not putting .. !!
any more suggestions ??
Click to expand...
Click to collapse
I am having the same issues:
I cannot flash anything pertaining to the bootloader, this is the official flash list, open fastboot and paste this entire list, when its finished you will see "failed" next to anything pertaining to the bootloader. And therein lies the issue, i havent found a soloution and ive been searching for 2 months now
fastboot flash partition gpt_both0.bin
fastboot flash sec sec.dat
fastboot flash apdp dp_AP_signed.mbn
fastboot flash msadp dp_MSA_signed.mbn
fastboot flash prov prov32.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl1bak sbl1.mbn
fastboot flash rpm rpm.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash devcfg devcfg.mbn
fastboot flash devcfgbak devcfg.mbn
fastboot flash lksecapp lksecapp.mbn
fastboot flash lksecappbak lksecapp.mbn
fastboot flash tz tz.mbn
fastboot flash tzbak tz.mbn
fastboot flash keymaster keymaster.mbn
fastboot flash cmnlib cmnlib.mbn
fastboot flash cmnlibbak cmnlib.mbn
fastboot flash cmnlib64 cmnlib64.mbn
fastboot flash cmnlib64bak cmnlib64.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot flash logo logo.bin
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system systemchunk0.img
fastboot flash system systemchunk1.img
fastboot flash system systemchunk2.img
fastboot flash system systemchunk3.img
fastboot flash system systemchunk4.img
fastboot flash system systemchunk5.img
fastboot flash system systemchunk6.img
fastboot flash system systemchunk7.img
fastboot flash system systemchunk8.img
fastboot flash system systemchunk9.img
fastboot flash system systemchunk10.img
fastboot flash system systemchunk11.img
fastboot flash system systemchunk12.img
fastboot flash cache cache.img
fastboot erase userdata
FYI i have unlocked my bootloader, and it wont let me lock it again
@nandakis4 Did you manage to solve your issue?
@itsjustbilly Why are you flashing the bootloader? It will fail if it's unlocked.
I'd want to go back to stock to start off fresh, but these are some discouraging stories.
cyrrrinda said:
Found
flash only boot and system, not bootloader
Click to expand...
Click to collapse
Please confirm if you were able to revert to MM without losing your signal.
Edit: It crossed my mind just now. TWRP has the ability to backup the modem so surely you could use it if you were to have problems with the signal later? Provided you can access the recovery of course, but that doesn't seem to be a problem in most cases.
qcn backup
Hi here is qcn backup from working phone. To go to engeneering mode you have to press ####8899#. Smaller is from qfil tool, bigger is from qpst tool (software download). When I restored, I am back on internet 4G, can make or receive calls, BUT NO SOUND from speaker and MIC not working so. Any idea?
cyrrrinda said:
Hi here is qcn backup from working phone. To go to engeneering mode you have to press ####8899#. Smaller is from qfil tool, bigger is from qpst tool (software download). When I restored, I am back on internet 4G, can make or receive calls, BUT NO SOUND from speaker and MIC not working so. Any idea?
Click to expand...
Click to collapse
Do 2G and 3G work? My phone can detect 4G, but not 2G and 3G.
You've probably solved the sound issue by now, otherwise have a look at this thread.

Is my HTC 10 another Brick for the USA-MEX wall?

Hi Guys! I appreciate any help or orientation to find out how should I proceed,
I don't know why my phone just got Brick yesterday, it was running fine for two months since the last Room's flash, suddenly I notice an estrange behavior of the system, then the capacitive buttons were not responding nor its backlit appear when I touch them, the home button and the fingerprint and everything else was working fine, so I think that with a simple Reboot it will be back to normality. For my disgrace, it enter in a Bootloop in the HTC logo screen and for my surprise when I manage to get to the Bootloader and try to enter to the Download and Recovery mode get me to the same HTC logo Bootloop!!
The principal suspect for me is that like 15 days ago a installed the TotallyFreeVPN app to see some Japanese Netflix
To complicate the things I want to make my phone thefts proof, so I disable usb debugging and OEM unlocking and installed Cerberus with the option of block usb debugging and also in security I enable the encrypted data option for every reboot or when enter in recovery.
My only hope is that you know if something can be done from the Bootloader to unbricked?
I attach the only two screens I have access right now
HTC 10
Firmware 2.41.401.4
Leedroid V3.6.1
Unlocked Bootloader
S-OFF
TWRP 2.8.4
I manage to run some fastboot commands from Bootloader, getvar all give me the following:
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:Surf eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0xe000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x61e000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xef000000
(bootloader) serialno:HT64EBN02616
flash a stock ruu
If your phone will still power on, it's not bricked.
BrianKuo1853 said:
flash a stock ruu
Click to expand...
Click to collapse
I wish I could, but I can´t enter in download mode, recovery or oem rebootRUU, all send me to the bootloop, after looking around I find this post that manage to solve a similar brick
https://forum.xda-developers.com/showpost.php?p=69874694&postcount=18
But in the last step when I put the micro sd card with the RUU file, nothing happens in my case, I thinks is because I didn't have USB debugging before the brick happen, but meaby the solution works for others.
I´ll keep trying
Thanks for any other ideas :good:
ALOMAJEMO said:
I wish I could, but I can´t enter in download mode, recovery or oem rebootRUU, all send me to the bootloop, after looking around I find this post that manage to solve a similar brick
https://forum.xda-developers.com/showpost.php?p=69874694&postcount=18
But in the last step when I put the micro sd card with the RUU file, nothing happens in my case, I thinks is because I didn't have USB debugging before the brick happen, but meaby the solution works for others.
I´ll keep trying
Thanks for any other ideas :good:
Click to expand...
Click to collapse
with s-off you can flash all images in bootloader of a firmware.
Flash the images in that order:
Code:
fastboot flash aboot aboot_signed.img
fastboot flash adsp adsp.img
fastboot flash apdp apdp-8996-1.img
fastboot flash cache cache.img
fastboot flash cmnlib32 cmnlib32.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash cota cota.img
fastboot flash devcfg devcfg-8996-1.img
fastboot flash dsp dsp.img
fastboot flash fsc fsc.img
fastboot flash hosd hosd_signed.img
fastboot flash hyp hyp-8996-1.img
fastboot flash keymaster keymaster.img
fastboot flash lksecapp lksecapp.img
fastboot flash modemst1 modemst1.img
fastboot flash modemst2 modemst2.img
fastboot flash pg2fs pg2fs_ship_signkey.img
fastboot flash pmic pmic-8996-1.img
fastboot flash rcdata rcdata.img
fastboot flash recovery recovery.img
fastboot flash rfg rfg_3.img
fastboot flash rpm rpm-8996-1.img
fastboot flash slpi slpi.img
fastboot flash tz tz-8996-1.img
fastboot flash venus venus.img
fastboot flash xbl xbl-8996-1.img
fastboot flash radio radio.img
Grab the firmware.zip from @Sneakyghost Thread..ensure you take the one you were on
Yeah and use the full version, not the NoWipe...
I am wondering if you were able to solve it... I am having the same issue. Tried the same you tried (although as I am s-on I could only flash hosd like the guy on the other post) but no luck at all. The funniest thing is that I've never tocuhed this phone (no s-off, no unlock, no custom recovery, just updated via OTA to get Nougat), it just ran out of battery during the night and got the boot loop the morning after when I plugged it in to charge. Cant believe it could turn into a f''ing brick by itself.
j to the 4n said:
with s-off you can flash all images in bootloader of a firmware.
Flash the images in that order:
Code:
fastboot flash aboot aboot_signed.img
fastboot flash adsp adsp.img
fastboot flash apdp apdp-8996-1.img
fastboot flash cache cache.img
fastboot flash cmnlib32 cmnlib32.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash cota cota.img
fastboot flash devcfg devcfg-8996-1.img
fastboot flash dsp dsp.img
fastboot flash fsc fsc.img
fastboot flash hosd hosd_signed.img
fastboot flash hyp hyp-8996-1.img
fastboot flash keymaster keymaster.img
fastboot flash lksecapp lksecapp.img
fastboot flash modemst1 modemst1.img
fastboot flash modemst2 modemst2.img
fastboot flash pg2fs pg2fs_ship_signkey.img
fastboot flash pmic pmic-8996-1.img
fastboot flash rcdata rcdata.img
fastboot flash recovery recovery.img
fastboot flash rfg rfg_3.img
fastboot flash rpm rpm-8996-1.img
fastboot flash slpi slpi.img
fastboot flash tz tz-8996-1.img
fastboot flash venus venus.img
fastboot flash xbl xbl-8996-1.img
fastboot flash radio radio.img
Grab the firmware.zip from @Sneakyghost Thread..ensure you take the one you were on
Click to expand...
Click to collapse
Sneakyghost said:
Yeah and use the full version, not the NoWipe...
Click to expand...
Click to collapse
Thank for your tips guys,
I follow exactly the order you suggest my good j to the 4n, and I download the firmware from your useful thread Sneakyghost, but still, I can not get it out of the Bootloop my friends
Dont you think my case is very strange?
If it serves for any other suggestion, I I add the following details
-The only image that is not flashing is rcdata, everything else is flashing OK
-I buy a microsd card class 10 of 32GB only to discard that the old microsd card of 3GB was not reading the RUU zip file.
-I optained the zip file, from the RUU.exe with the same version of the firmware 2.41.401.4 (the full version) and I copying it from the Temp files in Windows.
-With the microSD in FAT32 format I put the RUU zip file with the 2PS6IMG.zip name
-After flashing all the img files and rebooting to bootloader, then I inserted the card and select Download mode, where is supposed should appear the screen that jichuan89 mention to flash the RUU, but again nothing happen.
-Also I should say that I try also with the firmware and RUU version 2.41.617.3 (the corresponding for my model 2PS6500 in the back) but the last I have was the 2.41.401.4 with superCID and cidnum change it to HTC-001.
-And also among the hundreds of attempts I have executed fastboot erase userdata, erase cache, erase system, to try to clean any corrupt file.
Do you think there is any hope yet?
Once again thank you for your support guys!:good::good:
singlemalt said:
I am wondering if you were able to solve it... I am having the same issue. Tried the same you tried (although as I am s-on I could only flash hosd like the guy on the other post) but no luck at all. The funniest thing is that I've never tocuhed this phone (no s-off, no unlock, no custom recovery, just updated via OTA to get Nougat), it just ran out of battery during the night and got the boot loop the morning after when I plugged it in to charge. Cant believe it could turn into a f''ing brick by itself.
Click to expand...
Click to collapse
Not yet, but I start to think that having s-off or s-on makes no difference in the weight of our bricks If humor is any good LOL
ALOMAJEMO said:
Not yet, but I start to think that having s-off or s-on makes no difference in the weight of our bricks If humor is any good LOL
Click to expand...
Click to collapse
Haha...we have two bricks for the wall now...do you know if Donald would cover shipping costs from Argentina?
curious if anyone know how to view the firmware if cannout access downlad mode
venom55521 said:
curious if anyone know how to view the firmware if cannout access downlad mode
Click to expand...
Click to collapse
Dude, I'm answering your questions as we speak and still making new threads. Didn't you get the total picture about cross posting. If you never posted anywhere you should open a Q&A, I'm on it and i see this.
I'm pretty much done i guess........
Mr Hofs said:
Dude, I'm answering your questions as we speak and still making new threads. Didn't you get the total picture about cross posting. If you never posted anywhere you should open a Q&A, I'm on it and i see this.
I'm pretty much done i guess........
Click to expand...
Click to collapse
my bad,i was looking around for info and ideas and just had a question when i was reading it
venom55521 said:
my bad,i was looking around for info and ideas and just had a question when i was reading it
Click to expand...
Click to collapse
Please pick up a sledgehammer and smash your device....... it's the best for all of us.
Mr Hofs said:
Please pick up a sledgehammer and smash your device....... it's the best for all of us.
Click to expand...
Click to collapse
i realize you help a lot people out which is appreciated ,but being rude is pointless
venom55521 said:
i realize you help a lot people out which is appreciated ,but being rude is pointless
Click to expand...
Click to collapse
Your interpretation of the situation. I'm honest, not rude.

[HELP] Help with fastboot and RSD Lite

The phone doesn't show up in RSD Lite
But in my ADB ( $- Fastboot devices) it's showing up.
Can someone help me?
Downloaded and installed:
Device Manager
Moto USB Drivers
Moto Service (doesn't appear here too)
My brother give me this phone, and doesn't know the Gmail account he use (yeah i'm furious, he created a account just to "test" the phone, now i'm stuck in the google login screen because he wipes the phone in bootloader)
Windows 10
Motorola USB Cable
Print:
http://prntscr.com/gcrqab
What are you attempting to do?
If you are trying to flash firmware you do it through fastboot
If you are trying to log into google just create and sign in with a different account
Commands to flash via fastboot once you have downloaded the firmware are
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Note if you have more sparsechunks flash them as well in number order
If you want to play it safe and only really flash what should get the phone booting again just flash
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot erase cache
fastboot erase userdata
fastboot reboot
Again if you have more sparsechunks flash them as well in number order
I don't know what that tool you are using is but it's not required
TheFixItMan said:
What are you attempting to do?
If you are trying to flash firmware you do it through fastboot
If you are trying to log into google just create and sign in with a different account
Commands to flash via fastboot once you have downloaded the firmware are
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Note if you have more sparsechunks flash them as well in number order
If you want to play it safe and only really flash what should get the phone booting again just flash
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot erase cache
fastboot erase userdata
fastboot reboot
Again if you have more sparsechunks flash them as well in number order
I don't know what that tool you are using is but it's not required
Click to expand...
Click to collapse
I can do it with bootloader locked?
i"m with FRP (Factory Reset Protection) i can't pass without the gmail that he created and doesn't even remember the email.
TeuzHd said:
I can do it with bootloader locked?
Click to expand...
Click to collapse
Yes if it's original Motorola firmware
You only need to unlock bootloader for custom firmware/roms
TheFixItMan said:
What are you attempting to do?
If you are trying to flash firmware you do it through fastboot
If you are trying to log into google just create and sign in with a different account
Commands to flash via fastboot once you have downloaded the firmware are
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Note if you have more sparsechunks flash them as well in number order
If you want to play it safe and only really flash what should get the phone booting again just flash
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot erase cache
fastboot erase userdata
fastboot reboot
Again if you have more sparsechunks flash them as well in number order
I don't know what that tool you are using is but it's not required
Click to expand...
Click to collapse
TheFixItMan said:
Yes if it's original Motorola firmware
You only need to unlock bootloader for custom firmware/roms
Click to expand...
Click to collapse
I'm getting this with everything:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk3
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
That's my ADB root folder: http://prntscr.com/gcz5ld
TeuzHd said:
I'm getting this with everything:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk3
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
That's my ADB root folder: http://prntscr.com/gcz5ld
Click to expand...
Click to collapse
from that you should be typing the following
Code:
fastboot flash partition gpt.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk0
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
The errors you are getting is because of your adb version - it should still flash
long as you get an output that looks like this at the end
Code:
sending 'logo' (460 KB)...
OKAY [ 0.099s]
writing 'logo'...
OKAY [ 0.154s]
finished. total time: 0.256s
I have encluded my adb and fastboot folder for you to use (excludes any firmware just adb and fastboot) for use on windows
Download from link below
Platform-tools
TheFixItMan said:
from that you should be typing the following
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.520s]
writing 'boot'...
(bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.722s[/HTML]
i can try with another PC, should work?
Click to expand...
Click to collapse
TeuzHd said:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.520s]
writing 'boot'...
(bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.722s[/HTML]
i can try with another PC, should work?
Click to expand...
Click to collapse
The firmware you are trying to flash is a lower version than what is installed - You must get firmware that is equal to or newer than the firmware on the device already else it will fail
eg you cant flash android 7.0 on a device that has a bootloader that is for 7.1
you will have to find the correct firmware for your device
note there is no harm trying the firmware because as you can see - if its wrong it will just fail the validation test and not flash
TheFixItMan said:
The firmware you are trying to flash is a lower version than what is installed - You must get firmware that is equal to or newer than the firmware on the device already else it will fail
eg you cant flash android 7.0 on a device that has a bootloader that is for 7.1
you will have to find the correct firmware for your device
note there is no harm trying the firmware because as you can see - if its wrong it will just fail the validation test and not flash
Click to expand...
Click to collapse
Reflashing the 7.1.2 version i can pass FRP? i'm trying to bypas FRP.
In the authorized warranty, they told me that they can not do any software repairs on the device until I remove the FRP, but as I said we do not know the account he used to "test" the device
try adding this to the list of fastboot commands
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
---------- Post added at 06:24 PM ---------- Previous post was at 06:21 PM ----------
TeuzHd said:
Reflashing the 7.1.2 version i can pass FRP? i'm trying to bypas FRP.
In the authorized warranty, they told me that they can not do any software repairs on the device until I remove the FRP, but as I said we do not know the account he used to "test" the device
Click to expand...
Click to collapse
best thing is to google
eg
https://www.progeeksblog.com/frp-bypass-apk/
Iv never had do anything with frp so no idea how to do it on this device
TheFixItMan said:
try adding this to the list of fastboot commands
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
---------- Post added at 06:24 PM ---------- Previous post was at 06:21 PM ----------
best thing is to google
eg
https://www.progeeksblog.com/frp-bypass-apk/
Iv never had do anything with frp so no idea how to do it on this device
Click to expand...
Click to collapse
I did this, but the APK and Share exploit's doesn't work anymore
do you mean there is a password on the device because you can bypass that easy
just goto twrp
advanced
file manager
data
system
click on each of the following files and delete
gatekeeper-password.key
gatekeeper-patten.key
locksettings.db-shm
locksettings.db-wal
other than that I can't help anymore
TheFixItMan said:
do you mean there is a password on the device because you can bypass that easy
just goto twrp
advanced
file manager
data
system
click on each of the following files and delete
gatekeeper-password.key
gatekeeper-patten.key
locksettings.db-shm
locksettings.db-wal
other than that I can't help anymore
Click to expand...
Click to collapse
can't start TWRP
1- bootload locked with ADB options OFF
to put adb options on i need to pass FRP
TeuzHd said:
can't start TWRP
1- bootload locked with ADB options OFF
to put adb options on i need to pass FRP
Click to expand...
Click to collapse
have you tried
https://www.youtube.com/watch?v=xhf9egv8-ys
uses this app
https://play.google.com/store/apps/details?id=com.wUnlockiOfficial
TheFixItMan said:
have you tried
https://www.youtube.com/watch?v=xhf9egv8-ys
uses this app
https://play.google.com/store/apps/details?id=com.wUnlockiOfficial
Click to expand...
Click to collapse
How can i install a app without pass FRP?
TeuzHd said:
How can i install a app without pass FRP?
Click to expand...
Click to collapse
Do some googling
https://youtu.be/GkmL5tUtyB0
With this tool
http://www.mediafire.com/file/yif2m8j11dx1ur8/Moto+G4+Plus+Google+Account.rar
Watch videos and Google - don't rely on me to search for thing for you
TheFixItMan said:
Do some googling
https://youtu.be/GkmL5tUtyB0
With this tool
http://www.mediafire.com/file/yif2m8j11dx1ur8/Moto+G4+Plus+Google+Account.rar
Watch videos and Google - don't rely on me to search for thing for you
Click to expand...
Click to collapse
i alredy do this, look in the thread
Hi,
Where I can download the last firmware for Moto G5 XT1676 ?

Moto E4 Qualcomm (Owens) completely back to stock

WARNING: if the gpt.bin flash did not work, please stop and do not continue with the rest of the commands. It has been brought to my attention that software upgrades to the phone has changed the gpt and may not allow you to go back to the original stock firmware.
For all of you who DID NOT do a System image backup in TWRP and then found out your backup doesn't work.
First get your stock firmware here, the only place to get Moto stock firmware!
https://firmware.center/firmware/Motorola/Moto E4 Plus/Stock/
Then get fastboot. Google fastboot or grab the one from here: This one still works:
https://forum.xda-developers.com/showthread.php?t=2317790
If your fastboot directory isn't in your $PATH or you don't know how to do that, then copy fastboot into the same folder where you unzipped your stock firmware.
Got to the folder where you put everythig, open up a command or powershell prompt. Hold down shift, right click, "open command window here".
Now for the fun. You veterans can just look at the flashfile.xml to see the order. Those of you who are new, here are the commands you need to do. You could probably copy the entire thing and past it in your command window at one time. But I like to type it out.... line by line. You know, old school.
Commands:
Code:
fastboot oem fb_mode_set
fastboot flash gpt gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem hlos.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
the command to erase ddr will probably fail, but that shouldn't affect anything. I have tested by bringing my Moto E4 Plus that was running Lineage OS back to 100% stock. Of course, then I went right back to Lineage
Outstanding. Thank you for the post. I'm sure this will get used quite a bit. I did do a backup but it's always nice to have contingencies at the ready.
Sent from my Nexus 10 using XDA Premium HD app
I know this may sound like a stupid question, but which firmware package should I download and use for the Device purchased straight from Motorola? There are quite a few there and I don't want to flash the wrong one. This device was supposed too work on any US carrier and I would like to keep it that way, but my carrier is Verizon. All I had to do, when I got the device was install my Verizon Sim out of my Nexus 6 and it worked great. I do test for Cricket network too and that is a GSM radio so as I said, I would like it to have the firmware that would have come right from Motorola for this specific device. Thank you in advance.
glockman4519 said:
I know this may sound like a stupid question, but which firmware package should I download and use for the Device purchased straight from Motorola? There are quite a few there and I don't want to flash the wrong one. This device was supposed too work on any US carrier and I would like to keep it that way, but my carrier is Verizon. All I had to do, when I got the device was install my Verizon Sim out of my Nexus 6 and it worked great. I do test for Cricket network too and that is a GSM radio so as I said, I would like it to have the firmware that would have come right from Motorola for this specific device. Thank you in advance.
Click to expand...
Click to collapse
https://firmware.center/firmware/Mo...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
aj2333 said:
https://firmware.center/firmware/Mo...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Thank you very much. You sir are an awesome person.
I have another question and forgive me for being a pain but all steps went ok but at the end where the re-boot takes place it just keeps flashing back and forth from a black screen with "Bad Key" in the upper left corner and then to a screen with a colorful circle that says "erasing". I figured it was just doing a factory reset but it just keeps flashing back and forth between the 2 screens. Any idea what to try ? I tryed to boot to recovery and get the same thing. Thank you for any help.
glockman4519 said:
I have another question and forgive me for being a pain but all steps went ok but at the end where the re-boot takes place it just keeps flashing back and forth from a black screen with "Bad Key" in the upper left corner and then to a screen with a colorful circle that says "erasing". I figured it was just doing a factory reset but it just keeps flashing back and forth between the 2 screens. Any idea what to try ? I tryed to boot to recovery and get the same thing. Thank you for any help.
Click to expand...
Click to collapse
Did you remember to do an fastboot OEM fb_mode_clear?
no I didn't do that. I will go back over your instructions and re-do it. Thank you again for your assistance. I usually don't bug people for help and try to fix things on my own so I really appreciate you help.
Sent from my G3223 using XDA Premium HD app
Actually that is the command input right before the reboot command so I guess I did do that command. I will research this more and thank you for your help once again.
glockman4519 said:
Actually that is the command input right before the reboot command so I guess I did do that command. I will research this more and thank you for your help once again.
Click to expand...
Click to collapse
The cmd commands above aren't written correctly for carrier unlocked E4 Plus's. Hlos.bin isn't in the unlocked stock ROM, NON-HLOS.bin is. Also, "flasty" should be flash. Here is the correct commands. This worked on my unlocked phone.
Code:
fastboot oem fb_mode_set
fastboot flash gpt gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
doodalydoo said:
The cmd commands above aren't written correctly for carrier unlocked E4 Plus's. Hlos.bin isn't in the unlocked stock ROM, NON-HLOS.bin is. Also, "flasty" should be flash. Here is the correct commands. This worked on my unlocked phone.
Click to expand...
Click to collapse
You Sir are the man. I can't thank you enough for your help.
Update: Awesome.... It worked like a charm. I have everything copied now in case I hit the wall again. Thank you once again.
So I have used this and it worked great. However does anyone know when the firmware in that download will be updated to the latest version?
XT1775 rom's is possible install on XT1776 ?
almao11 said:
XT1775 rom's is possible install on XT1776 ?
Click to expand...
Click to collapse
Not Stock ROM, no. Custom ROMs should work fine tho
---------- Post added at 11:41 AM ---------- Previous post was at 11:32 AM ----------
For OP @zerogun & those of you wondering which stock ROM Firmware to grab for Boost Mobile's XT1776 (owens), I used this one and it worked 100%. The Fastboot cmd list in the 10th post or so i nears perfect, (all the rest is Golden) except that for the Boost Mobile FW's:
fastboot flash oem.img
..needs to actually be:
fastboot flash oem.img_sparsechunk.0
fastboot flash oem.img_sparsechunk.1
Cool miner malware that pops up on firmware.center.
mattleft said:
Cool miner malware that pops up on firmware.center.
Click to expand...
Click to collapse
I haven't had that problem. Have you scanned your PC for virus/malware?
I would like to relock my bootloader but on this firmware it says the boot is not signed. Can I relock it after I do the ota as they should be signed then right?
bcrichster said:
Not Stock ROM, no. Custom ROMs should work fine tho
---------- Post added at 11:41 AM ---------- Previous post was at 11:32 AM ----------
For OP @zerogun & those of you wondering which stock ROM Firmware to grab for Boost Mobile's XT1776 (owens), I used this one and it worked 100%. The Fastboot cmd list in the 10th post or so i nears perfect, (all the rest is Golden) except that for the Boost Mobile FW's:
fastboot flash oem.img
..needs to actually be:
fastboot flash oem.img_sparsechunk.0
fastboot flash oem.img_sparsechunk.1
Click to expand...
Click to collapse
Did this allow you to use a non Boost/Sprint sim card?
Thanks,
Victor
mindstream98 said:
Did this allow you to use a non Boost/Sprint sim card?
Thanks,
Victor
Click to expand...
Click to collapse
I read in another thread that it was possible by using a Custom ROM but haven't tried it myself..
Although the Custom ROMs should work on several Carriers, this is a "Completely Back to Stock" thread..
Running an Xp3r!meπt with my XT1776
zerogun said:
For all of you who DID NOT do a System image backup in TWRP and then found out your backup doesn't work.
First get your stock firmware here, the only place to get Moto stock firmware!
https://firmware.center/firmware/Motorola/Moto E4 Plus/Stock/
Then get fastboot. Google fastboot or grab the one from here: This one still works:
https://forum.xda-developers.com/showthread.php?t=2317790
If your fastboot directory isn't in your $PATH or you don't know how to do that, then copy fastboot into the same folder where you unzipped your stock firmware.
Got to the folder where you put everythig, open up a command or powershell prompt. Hold down shift, right click, "open command window here".
Now for the fun. You veterans can just look at the flashfile.xml to see the order. Those of you who are new, here are the commands you need to do. You could probably copy the entire thing and past it in your command window at one time. But I like to type it out.... line by line. You know, old school.
Commands:
Code:
fastboot oem fb_mode_set
fastboot flash gpt gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem hlos.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
the command to erase ddr will probably fail, but that shouldn't affect anything. I have tested by bringing my Moto E4 Plus that was running Lineage OS back to 100% stock. Of course, then I went right back to Lineage
Click to expand...
Click to collapse
I used this to go back to stock, now my phone wont even turn on, at all.

[GUIDE] Moto G5 Plus: Flashing Stock Firmware & Rooting [2021]

Flashing signed stock firmware:
You need:
Latest signed stock firmware:
Europe (RETEU):
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors-obs-2.lolinet.com
India (RETIN):
https://mirrors-obs-2.lolinet.com/f...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
US (RETUS):
https://mirrors-obs-2.lolinet.com/f...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
All other firmwares and locations:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors-obs-2.lolinet.com
Also:
flashallO.bat:
https://drive.google.com/file/d/1Ne7Kps25heUO7wsJ0Z4_X43eKQYRegoa/view?usp=sharing
Motorola drivers (Device Manager - former LMSA):
Motorola Device Manager
Motorola Device Manager, free download for Windows. Program to transfer data between Motorola devices and computers, update software and backup files.
motorola-device-manager.en.lo4d.com
Tiny ADB & Fastboot v1.4.0 signed;
Tiny_ADB_&_Fastboot_v1.4.0-signed.exe | Tool by K3V1991 for Misc. Software & Hardware Resources
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
1) Download the 8.1.0_OPS28.85-17-6-2 firmware for your region (it's the last one for the Moto G5+ (potter), there won't be any updates anymore, so no risk of bootloader downgrading)
2) Install Tiny ADB & Fastboot (best place is the root directory of C: or wherever your OS resides).
3) Extract the firmware to that ADB & Fastboot folder.
4) Download my "flashallO.bat" and move it to that folder too.It removes the need for you to manually flash all partitions, just double-click it and it'll run all the commands for you.
5) Download and install Motorola device drivers.The program is called "Motorola Device Manager".
6) Reboot your phone to the bootloader. To do this, turn it off, then hold down the power and volume down buttons until you see a bugdroid undergoing open-heart surgery.
7) Connect the phone to your PC with your USB cable. Type
Code:
fastboot devices
to check if your device is connected. A serial number should be shown.
8) Run the flashallO.bat script. (Caution: This will wipe your device completely!) It will take some time to flash, just be patient and don't worry.
If the command window appears for a brief moment and then disappears, the device drivers may not be installed correctly. You can ask me in that case, there are some special drivers that may solve that.
9) Once the command window closes, it should have completed the flashing process and you are safe to press the power key on the phone to start Android. Just make sure that the text near the buttons reads "START".
That's it.
You can save your (internal) data when you open the flashallO.bat and delete the command
Code:
fastboot erase userdata
so that it will be omitted.
I won't recommend it but it's possible.
Rooting:
You need:
Magisk 24.1:
https://github.com/topjohnwu/Magisk/releases/download/v24.1/Magisk-v24.1.apk
If you have problems with the newer Magisk builds (since v24) you may try
Magisk 23:
https://github.com/topjohnwu/Magisk/releases/tag/v23.0
or
Magisk 20.4: https://github.com/topjohnwu/Magisk/releases/tag/v20.4
TWRP 3.5.2_9-0:
https://eu.dl.twrp.me/potter/twrp-3.5.2_9-0-potter.img
Maybe you'll need:
Disable_Dm-Verity_ForceEncrypt.zip:
https://yadi.sk/d/HLr5vjnkA8gaqw
- Download TWRP from the above link and place it in your ADB & Fastboot folder.
- Download magisk.zip (and Magisk Manager APK if you use version 20.4) and place it in your internal storage.
- Turn the phone off again and reboot to bootloader using previously mentioned key combination.
- Navigate to the folder where you placed the TWRP image.
- Hold down the "shift" key and right-click anywhere in the Explorer window,it should give you an option to "Open command window here."
- Now input the command:
Code:
fastboot flash recovery [filename].img
, where [filename] is the name of your TWRP image file. Tap Enter and it will take a few seconds to flash the new recovery.
- Alternatively, you can use "fastboot boot [filename].img" to temporarily boot TWRP for the purpose of flashing Magisk. This retains the stock recovery.
- Now that TWRP has been flashed, press the volume down key until you see the label on the side change to read "RECOVERY." At that point you can press the power button and you will boot right into TWRP.
- If you decide to decrypt your device:
In that case go to "Wipe" in TWRP and use "format data" (the option where you have to confirm with "yes"). Just wipe data is not enough!
- If you want your device to stay encrypted skip that step.
- Now press the "Install' button in TWRP and navigate to the location where the magisk.zip is located. Simply tap it and "Swipe to install."
- If you decided to decrypt your device normally magisk should take care that it doesn't get encrypted again.
Magisk only disables the enforced encryption flag, the device will still be encrypted and that's why a wipe of data is necessary to remove the encryption.
If that's not the case and you get problems to reboot flash Disable_Dm-Verity_ForceEncrypt.zip after magisk.zip.
More information about decryption/encryption:
https://didgeridoohan.com/magisk/Magisk#hn_Disabling_dm-verity_and_forced_encryption
- Reboot your device, if the Magisk Manager isn't installed already (it should) install the Magisk Manager APK.
Thanks to @Jrhotrod for parts of the rooting tutorial.
Edit: Updated Links again.(1-2022)
My 3 year old Moto G5 Plus running android 8 suddenly restarted a few days ago and went into Start up failure. It no longer shows My product or IMEI number. It just shows potter 000000000000000 32GB P3B
Bootloader logs read " Start up failure. Your device didn't start up successfully. Use the Software Repair Assistant on computer to repair your device. Connect your device to your computer to get the Software Repair Assistant" written in red.
I have my IMEI and product numbers saved on my pc in a notepad file, but the LMSA software does not recognise my device to even try to rescue it. I want to retrieve files from my phone before attempting a factory reset.
On using the LMSA, it says "lmsa doesn't match appropriate firmware. you can try to select a firmware manually" but then it has no option to select anything manually. I have my phone previously registered on the software on my PC.
I have not rooted my phone, nor used anything other than stock android. My bootloader is locked. I cannot remember if I had Developer options selected or not, most probably not.
On trying to go to recovery mode it says the same message " Start up failure. Your device didn't start up successfully. Use the Software Repair Assistant on computer to repair your device. Connect your device to your computer to get the Software Repair Assistant"
When I connect the phone to the computer, it recognises it (I hear a notification sound) and under Devices it shows under Unrecognised as "Fastboot potter s"
I've never flashed my phone but would it be possible to recover the files in the internal storage of the phone by installing TWRP (in a non rooted, bootloader locked phone) without data loss?
How does it work?
Please help! I really need to recover my photos and notepad notes. Is there any way? Any software?
Is there any way to flash stock ROM without losing data? I haven't attempted anything in the off chance that there is a way to recover internal storage data. It's absolutely essential to me. I don't care about the phone, I'm gonna replace it anyway.
If I can even switch on the phone for long enough to backup data from the phone, it will be enough.
I read in another thread that downgrading a Moto with a locked bootloader will hard brick the device. This thread. My bootloader/oem is locked. I've attached a screenshot from when I once connected my phone to LMSA a few weeks before it crashed, it showed my current version I was running at the time. I never got around to taking a backup of the phone, then.
These are the screens I get. I try to charge the phone in fastboot every day to keep it from dying completely.
I'm desperate.
Also Lolinet seems to be down. I tried to download RETIN firmware from the link you provided, but I only get
404 Not Found
nginx
What to do now?
I downloaded the firmware from Motorola Stock Room. Will that do?
I downloaded the firmware from Motorola Stock Room. Will that do?
[/QUOTE]
DwightKBrute said:
Also Lolinet seems to be down. I tried to download RETIN firmware from the link you provided, but I only get
404 Not Found
nginx
What to do now?
I downloaded the firmware from Motorola Stock Room. Will that do?
Click to expand...
Click to collapse
I also recognised that lolinet.mirrors has some problems but it seems it's been working on it (see attached screenshot).
The firmware from Motorola Stock ROM should work, it's the same build and also the last firmware for the Moto G5+ so no risk of bootloader downgrading.
Let me know if you were successful.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Edit: No way to save your data from an unroofed device with locked bootloader, I'm sorry.
You can omit the "fastboot erase userdata" command (see above thread) to save your internal storage when flashing the firmware but as you have problems with your device a complete clean start may be the only solution. But you can give it a try.
Wolfcity said:
I downloaded the firmware from Motorola Stock Room. Will that do?
Click to expand...
Click to collapse
I also recognised that lolinet.mirrors has some problems but it seems it's been working on it (see attached screenshot).
The firmware from Motorola Stock ROM should work, it's the same build and also the last firmware for the Moto G5+ so no risk of bootloader downgrading.
Let me know if you were successful.
View attachment 5162915
[/QUOTE]
I will follow your instructions on this post.
The download from the Motorola stock room has adb, flashboot and everything else (including a .bat file) in its folder.
How can I use your .bat file (from the link you provided) instead of the one from Motorola Stock Room?
Also I want to preserve the internal storage, so I can erase the fastboot erase userdata command. But how do I open the .bat file? There is no open with option.
Also since I'm missing my IMEI and SKU, should I keep the erase modemst1 and fastboot erase modemst2 commands in the file?
DwightKBrute said:
I also recognised that lolinet.mirrors has some problems but it seems it's been working on it (see attached screenshot).
The firmware from Motorola Stock ROM should work, it's the same build and also the last firmware for the Moto G5+ so no risk of bootloader downgrading.
Let me know if you were successful.
View attachment 5162915
Click to expand...
Click to collapse
I will follow your instructions on this post.
The download from the Motorola stock room has adb, flashboot and everything else (including a .bat file) in its folder.
View attachment 5162925
View attachment 5162923
How can I use your .bat file (from the link you provided) instead of the one from Motorola Stock Room?
Also I want to preserve the internal storage, so I can erase the fastboot erase userdata command. But how do I open the .bat file? There is no open with option.
View attachment 5162927
[/QUOTE]
Copy this content and put it into a notepad:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Delete the fastboot erase userdata line and save it as .bat file (if your notepad has no option to save it as .bat save it as .txt and change the ending from .txt to .bat by hand).
And deactivate your Windows Defender when doing that and also when using the .bat file.
Wolfcity said:
I will follow your instructions on this post.
The download from the Motorola stock room has adb, flashboot and everything else (including a .bat file) in its folder.
View attachment 5162925
View attachment 5162923
How can I use your .bat file (from the link you provided) instead of the one from Motorola Stock Room?
Also I want to preserve the internal storage, so I can erase the fastboot erase userdata command. But how do I open the .bat file? There is no open with option.
View attachment 5162927
Click to expand...
Click to collapse
Copy this content and put it into a notepad:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Delete the fastboot erase userdata line and save it as .bat file (if your notepad has no option to save it as .bat save it as .txt and change the ending from .txt to .bat by hand).
And deactivate your Windows Defender when doing that and also when using the .bat file.
[/QUOTE]
So let me just recheck the steps.
1. Downloaded the firmware from Motorola Stock Room
2. Downloaded and installed Mini Adb.
3. Extracted the firmware to the same folder as the mini adb
4. Deleted the .bat file already present in the extracted firmware folder from MSR. Replaced that with the .bat file you have provided.
5. Erase userdata command removed.
6. Run the .bat file.
7. Wait for flashing to complete
Yes?
DwightKBrute said:
I also recognised that lolinet.mirrors has some problems but it seems it's been working on it (see attached screenshot).
The firmware from Motorola Stock ROM should work, it's the same build and also the last firmware for the Moto G5+ so no risk of bootloader downgrading.
Let me know if you were successful.
View attachment 5162915
Click to expand...
Click to collapse
I will follow your instructions on this post.
The download from the Motorola stock room has adb, flashboot and everything else (including a .bat file) in its folder.
View attachment 5162925
View attachment 5162923
How can I use your .bat file (from the link you provided) instead of the one from Motorola Stock Room?
Also I want to preserve the internal storage, so I can erase the fastboot erase userdata command. But how do I open the .bat file? There is no open with option.
View attachment 5162927
[/QUOTE]
Download (or copy) my flashallO.bat file delete,the erase userdata line
DwightKBrute said:
Copy this content and put it into a notepad:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Delete the fastboot erase userdata line and save it as .bat file (if your notepad has no option to save it as .bat save it as .txt and change the ending from .txt to .bat by hand).
And deactivate your Windows Defender when doing that and also when using the .bat file.
Click to expand...
Click to collapse
So let me just recheck the steps.
1. Downloaded the firmware from Motorola Stock Room
2. Downloaded and installed Mini Adb.
3. Extracted the firmware to the same folder as the mini adb
4. Deleted the .bat file already present in the extracted firmware folder from MSR. Replaced that with the .bat file you have provided.
5. Erase userdata command removed.
6. Run the .bat file.
7. Wait for flashing to complete
Yes?
[/QUOTE]
Sounds ok. The bat file has to be copied into the ADB & Fastboot folder (mini ADB) too.
Deactivate Defender and start the bat file.
Be patient.
And collect as many data from the flashing process as possible (screenshots etc.)
Well. I wasn't able to get many screenshots, it happened too quickly. But the phone is still stuck on fastboot, but this time the fastboot reason is given as: Last time flashing failed.
Oh well. I'll try again without removing the flashboot erase userdata?
failed to validate recovery image
DwightKBrute said:
Well. I wasn't able to get many screenshots, it happened too quickly. But the phone is still stuck on fastboot, but this time the fastboot reason is given as: Last time flashing failed.
Oh well. I'll try again without removing the flashboot erase userdata?
failed to validate recovery image
Click to expand...
Click to collapse
Seems your device has problems to erase partitions before flashing new stuff to them. Maybe search for blankflash files.
Where to find the blankflash file?
DwightKBrute said:
Where to find the blankflash file?
Click to expand...
Click to collapse
https://mirrors.lolinet.com/firmware/moto/potter/
Hello. I have a rooted Moto G5 Plus (Magisk) and I have also installed a Custom ROM with TWRP. I want to unroot the device and return it to absolute stock. Will this guide work in that case? If no, can anyone direct me to the correct guide?
DEJAVU54 said:
Hello. I have a rooted Moto G5 Plus (Magisk) and I have also installed a Custom ROM with TWRP. I want to unroot the device and return it to absolute stock. Will this guide work in that case? If no, can anyone direct me to the correct guide?
Click to expand...
Click to collapse
The above guide https://forum.xda-developers.com/t/guide-moto-g5-plus-flashing-stock-firmware-rooting-2021.4205293/ should be helpful for you. Flashing the latest signed stock firmware as described in the first part will take you to absolute stock.
A few points to take care of:
- Make sure that you chose the correct firmware for your location.
- Don´t delete the fastboot erase userdata command from the flashallO.bat so that it will be omitted because some parts of Magisk or other root apps may reside at that location.
- You have to erase everything to be on the safe side.
- So save your internal userdata like pictures, documents, music etc. to a PC or a SD card before you start the
process!
- Flashing stock will overwrite the recovery.img (TWRP) and the boot.img (Magisk) so you don´t have to unroot or reflash stock recovery.
If you want to relock your bootloader too (remember that you won´t get to the "nerver unlocked" state again, the device will flag the bootloader as "has been unlocked" even when you lock it):
-After flashing stock firmware open a command prompt in the ADB & Fastboot folder again and give the following commands one by one or use the attached relockO.bat file. the same way you did it with the flashallO.bat:
relockO.bat:
relockO.bat
drive.google.com
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash boot boot.img
fastboot oem lock
You can do that anytime, it hasn´t to be right after the firmware flash.
I flashed the ROM today and everything went well, except the IMEI is 0 and I cannot use VoLTE. What can I do?
DEJAVU54 said:
I flashed the ROM today and everything went well, except the IMEI is 0 and I cannot use VoLTE. What can I do?
Click to expand...
Click to collapse
What does getvar all say?
post it here after you remove imei line.
Code:
fastboot getvar all
sd_shadow said:
What does getvar all say?
post it here after you remove imei line.
Code:
fastboot getvar all
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.92
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 6
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX14MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY2244FVLG
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: 10E5EE5600000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: Volume down key pressed
(bootloader) meid:
(bootloader) date: 05-23-2017
(bootloader) sku: XT1686
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Aug 30 2:39:28 UTC 1973"
(bootloader) ro.build.fingerprint[0]: motorola/potter_n/potter_n:8.1.0/O
(bootloader) ro.build.fingerprint[1]: PSS28.85-13-3/72e4:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.201.4.potter.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: M8953_41.50.07.82u POTTER_INDIADSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g70fa69f (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Wed Oct 10 11:58:58 CDT 2018
(bootloader) sbl1.git: git=MBM-NG-VC0.92-0-gd009c3b
(bootloader) rpm.git: git=92e5e21-dirty
(bootloader) tz.git: git=26cc248-dirty
(bootloader) devcfg.git: git=26cc248-dirty
(bootloader) keymaster.git: git=26cc248-dirty
(bootloader) cmnlib.git: git=26cc248-dirty
(bootloader) cmnlib64.git: git=26cc248-dirty
(bootloader) prov.git: git=26cc248-dirty
(bootloader) aboot.git: git=MBM-NG-VC0.92-0-g3ea8df0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retin
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
Finished. Total time: 0.062s
DEJAVU54 said:
I flashed the ROM today and everything went well, except the IMEI is 0 and I cannot use VoLTE. What can I do?
Click to expand...
Click to collapse
Have you ever flashed someone else's persist file?
Wolfcity said:
Have you ever flashed someone else's persist file?
Click to expand...
Click to collapse
No I have not. Only the PixelExp zip and now, the stock rom.
Anyways, after panicking a bit yesterday, I flashed the custom rom again and my IMEI and LTE returned, but I cannot place/receive calls. What can be done if I wanted to stay on the ROM but gain calling capabilities?
EDIT: I'd prefer to have everything working on the stock ROM if possible.

Categories

Resources