hi, name's Josh, i was trying to downgrade my moto g8 plus, but i had this issue with "please lock bootloader" loop so i tried locking it, but now i cannot even pass from bootloader:
"no booteable A/B slot
failed to boot linux, falling back to fastboot
fastboot reason: Fall-through from normal boot mode"
i've tried to fix it with the rescue and smart assistant but it keeps failing, i also tried flashing it with fastboot but i get the message "failed to identify current slot", when i try to "--set-active=a" it shows (either for b):
Setting current slot to 'a'...
FAILED (remote failure)
finished. total time: 0.172s
And when i type "fastboot getvar current-slot" i get this:
current-slot:
finished. total time: 0.064s
I don't really know what to do now, even recovery mode won't prompt, it just restarts bootloader, does anyone have a solution for this? i never had this kind of issue with samsung devices, this is my first motorola and since i bought it i had problems with touch being laggy so i was trying to downgrade android 10 to 9 but i was unable, and now i can't even use it at all, i would really apreciate if somebody could help me, in advance thanks for your time and attention
Can you unlock the bootloader again?
gfrank227 said:
Can you unlock the bootloader again?
Click to expand...
Click to collapse
when i try "fastboot oem unlock" it just says:
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
FAILED (remote failure)
finished. total time: 0.190s
darkhonor said:
when i try "fastboot oem unlock" it just says:
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
FAILED (remote failure)
finished. total time: 0.190s
Click to expand...
Click to collapse
If you're really desperate, you can try this. I can't vouch for its success rate. Be careful.
Moto G8+ Fix/Repair Hard Brick Tutorial
hello everyone i hard bricked my moto g8 plus the other day it was totally dead it couldnt power on there was no sound no vibration my pc couldnt recognise it when connected with usb cable, But i managed to fix it and get it working again the...
forum.xda-developers.com
gfrank227 said:
If you're really desperate, you can try this. I can't vouch for its success rate. Be careful.
Moto G8+ Fix/Repair Hard Brick Tutorial
hello everyone i hard bricked my moto g8 plus the other day it was totally dead it couldnt power on there was no sound no vibration my pc couldnt recognise it when connected with usb cable, But i managed to fix it and get it working again the...
forum.xda-developers.com
Click to expand...
Click to collapse
Since you are able to get into fastboot, perhaps you should start with a blankflash from lolinet and do not take your phone apart quite yet.
When you say you tried to downgrade did you flash the previous version bootloader and partition table? You should never do that, but it sounds like you need to try and flash a blankflash like mentioned above.
One other thing you can try to do, although I doubt it would work since it can't determine the active slot is download the firmware from lolinet then fastboot boot boot.img to try and boot the kernel, which will boot the system. If that does work then you can go into dev settings and check the allow bootloader unlock option.
gfrank227 said:
Since you are able to get into fastboot, perhaps you should start with a blankflash from lolinet and do not take your phone apart quite yet.
Click to expand...
Click to collapse
ok so i tried to blankflash it but i got this error i guess is time to say goodbye jajaj
Motorola qboot utility version 3.86
[ -0.000] Opening device: \\.\COM7
[ 0.005] Detecting device
[ 34.666] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 34.666] Check qboot_log.txt for more details
[ 34.666] Total time: 34.668s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()
->IO error
CodyF86 said:
When you say you tried to downgrade did you flash the previous version bootloader and partition table? You should never do that, but it sounds like you need to try and flash a blankflash like mentioned above.
One other thing you can try to do, although I doubt it would work since it can't determine the active slot is download the firmware from lolinet then fastboot boot boot.img to try and boot the kernel, which will boot the system. If that does work then you can go into dev settings and check the allow bootloader unlock option.
Click to expand...
Click to collapse
well im uncertain of how that is made, i just followed up a tutorial , downloaded official firmware and flashed it with fastboot comands:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor vendor.img
fastboot erase carrier
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
and yeah i tried flashing the newest official firmware that rescue and smart assistant showed, but since i cannot determine slot it says "failed to identify current slot"
Yeah it looks like that would have flashed the previous version of androids parttition table for that device from the commands you ran and that's usually a rip.
CodyF86 said:
Yeah it looks like that would have flashed the previous version of androids parttition table for that device from the commands you ran and that's usually a rip.
Click to expand...
Click to collapse
So there's no other way to fix it?
Related
After tried to root my device without the assist of PC (only using apk), my device only starts on AP Fastboot Flash Mode (Secure).
I downloaded the brazilian firmware, tried to flash it but I can't.
Was getting this ERROR: "(bootloader) Preflash validation failed".
My bootloader is locked, so I tried to unlock it following the Motorola's guide. Got my device ID via fastboot, copy and paste on their site and requested the unlock key.
Then again, when I use "fastboot oem unlock CODE"
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.016s
The problem is that I can't pass trough flash mode screen.
I've been reading some threads over here, and one guy which had his bootloader locked on XT1563 tried to flash the Canadian firmware and didn't get any error, then he was able to fully unlock his bootloader and after this he was able to flash the Brazilian firmware.
I didn't try to flash the Canadian firmware yet. How risky is this? There is another way to unlock the bootloader?
If you flash the right firmware for a locked phone (model and version), it won't give the prevalidation error. Then it can boot again and you can turn on the OEM unlock, and unlock the bootloader.
Try to use the right firmware for your phone.
TImMaia said:
After tried to root my device without the assist of PC (only using apk), my device only starts on AP Fastboot Flash Mode (Secure).
I downloaded the brazilian firmware, tried to flash it but I can't.
Was getting this ERROR: "(bootloader) Preflash validation failed".
Click to expand...
Click to collapse
I don't believe it is possible to root without first unlocking your bootloader (which will factory reset your device). What apk were you attempting to install?
MrTooPhone said:
I don't believe it is possible to root without first unlocking your bootloader (which will factory reset your device). What apk were you attempting to install?
Click to expand...
Click to collapse
I'm a real noob at this issue. I tried to root with Kingroot. I took the device to the Motorola Tech Support in my city yesterday afternoon and it is ready to pick up.
Thank you guys for helping me :good::good::good:
TImMaia said:
I'm a real noob at this issue. I tried to root with Kingroot. I took the device to the Motorola Tech Support in my city yesterday afternoon and it is ready to pick up.
Thank you guys for helping me :good::good::good:
Click to expand...
Click to collapse
If you really want to root, you need to follow these instructions. Although you can use the latest version of TWRP, do not use any other version of Supersu except v2.62-3. Any other methods will most likely soft brick your phone.
Boys, is not difficult, not just fiddling around to fix it.
Motorola install drivers
Install ADB and fastboot
Looking for your stock rom here: " github dot com dash motoxplay dash stock dash releases " for example.
Saddled with fastboot Tooda the rom (eye, if downloaded from out there commands, you may be wanting to them upload any image rom, this drove me crazy to me all one day until I realized I was missing two sparsechunk).
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 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 system system.img_sparsechunk.9
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
On the subject battery, the XT1563 charge the batt when it is in this mode, we just have to leave it connected to the charger and is loading very slowly.
On the bootloader issue, I have LOCK, and may do so without problems because they look the same version of rom that he had.
About not having DEPURACION USB, I did not have it on, and yet I could do it.
My stay in Fastboot mode I when installing the app Kingroot, and turned off the phone and start no more.
In this way it is solved, 100% sure I did not do myself. Do not try other methods like TWRP or things like that because with locked bootloader will hit the wall every time.
Anyone who needs a hand, ask or send mail.
Sorry if he had been resolved, but it was a big achievement for me, so I leave the info. I cost a lot to buy the cell phone and had ****ed the other day.
Regards!
(Sorry, its googletranslated, im from argentina)
Yeah, what ever @jonatandirocca1 said is right
i also once faced the problem of missing sparse file but after flashing every file you can make your Phone revoke
if you want to install STOCK FIRMWARE , you dont need to unlock bootloader, you just need your phone detected in ADB
This started happening since today morning. The phone doesn't charge or get detected when connecting to a computer.
I tried wiping everything and clean installing different roms and kernels, but nothing helped.
For some reason, the phone is charging when in the Bootloader screen though. What should I do?
Windows 10? Install this
Huh?
Let me clarify, it was working properly until last night, and I have Windows 10.
I'm currently forced to charge using the bootloader screen as the phone refuses to charge otherwise - not while fully switched off, and also not when switched on.
The computer and the phone don't even detect that anything is connected when I plug in the USB. (The cable is okay, I'm using the same cable to charge my phone on the bootloader screen)
Wait... It charges in the bootloader (or while off I assume) but not when booted into the OS? Is this device stock? What have you tried, wipe cache, factory reset, etc?
Sent from my MotoG3 using Tapatalk
acejavelin said:
Wait... It charges in the bootloader (or while off I assume) but not when booted into the OS? Is this device stock? What have you tried, wipe cache, factory reset, etc?
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
No it's not stock.
I've tried everything. Full wipe and flashed various roms and kernels. No avail. :/
Check for lint build up in the plug on the phone and try a different cable... I know it sounds wrong but once the phone is booted it does some simple communication to the source, that may not be working.
Sent from my MotoG3 using Tapatalk
I forgot to mention something.
The battery icon in the notification bar is permanently stuck showing charging even though the phone actually isn't being charged (and the battery screen in Settings also show 'Not charging').
acejavelin said:
Check for lint build up in the plug on the phone and try a different cable... I know it sounds wrong but once the phone is booted it does some simple communication to the source, that may not be working.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
This didn't work, sorry.
So, it only seems to charge when connected the PC in bootloader mode. It doesn't charge otherwise - not with any charger, and not while being switched on. wth.
Nvm, I'll try removing the lint.
FalKoopa said:
No it's not stock.
I've tried everything. Full wipe and flashed various roms and kernels. No avail. :/
Click to expand...
Click to collapse
Did you try to install stock rom or only custom roms?
Acetyloaceton said:
Did you try to install stock rom or only custom roms?
Click to expand...
Click to collapse
Only custom roms. I'm admittedly a bit scared to try installing the stock rom as it might get bricked.
EDIT: Btw, cleaning it didn't work. I suppose I have no option but to give it for repairs.
If I were you, I would try to do this. Dont be scared. If you have the newest marshmallow partition and bootloader then flash factory images without these two. You can also skip logo if you want to keep disabled unlocked bootloader information.
fastboot oem fb_mode_set
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 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
Wait 5-10 minutes and done
Acetyloaceton said:
If I were you, I would try to do this. Dont be scared. If you have the newest marshmallow partition and bootloader then flash factory images without these two. You can also skip logo if you want to keep disabled unlocked bootloader information.
fastboot oem fb_mode_set
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 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
Wait 5-10 minutes and done
Click to expand...
Click to collapse
Where will I get these files?
Here you go
And if I remember correctly you have an xt1550 right? I have flashed factory image of 6.0.1 with no problems on my xt1550, just to assure.
Check in device manager & devices and printers, if something pops up when phone is connected in bootloader mode. If a device with yellow triangle shows up, you can install drivers (pointing to driver inf file) to and subsequently fastboot flash stock.
Broadcasted from Zeta Reticuli
I think if you flash partition and bootloader then it also should work. Brick issue only appears when you are trying to do downgrade from marshmallow to lollipop and you flash older partition (you should always have the newest one).
Gravemind2015 said:
And if I remember correctly you have an xt1550 right? I have flashed factory image of 6.0.1 with no problems on my xt1550, just to assure.
Check in device manager & devices and printers, if something pops up when phone is connected in bootloader mode. If a device with yellow triangle shows up, you can install drivers (pointing to driver inf file) to and subsequently fastboot flash stock.
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
Alright. I'm going to flash it then. Downloading it will take a while...
I don't remember ever updating the bootloader though..
@Acetyloaceton
So, I tried to flash the stock recovery.img
I got this.....
target reported max download size of 268435456 bytes
sending 'stock' (16484 KB)...
OKAY [ 0.571s]
writing 'stock'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.598s
Nevermind, I managed to flash everything and all went well, but now the phone is in a bootloop between bootloader unlocked screen and the Erasing screen.
FalKoopa said:
Nevermind, I managed to flash everything and all went well, but now the phone is in a bootloop between bootloader unlocked screen and the Erasing screen.
Click to expand...
Click to collapse
Have you tried factory resetting via stock recovery? I mean power off>power+vol. Down>bootloader>recovery. If still can't boot then after factory resetting try flashing firmware again.
Broadcasted from Zeta Reticuli
Hi,
I followed Motorola procedure to unlock my G3, but I missed I should have first set "Allow OEM unlock" with a working phone:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
Then my phone was unbootable. I tried "Factory reset" as here:
http://forum.xda-developers.com/showpost.php?p=66521508&postcount=590
Then I ended in a endless animation of Android robot working to erase data at every boot.
The I tried to reflash stock rom (my bootloadre is still locked), using this method:
http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
but this line always timed out:
fastboot flash system system.img_sparsechunk.0
I was on 6.0 via OTA.
How can I fix my phone? Only sending it to Motorola will solve?
Thanks
So you didn't have OEM Unlocking enabled and you tried to unlock? It should have just said "Nuh uh, not gonna do it" and you could reboot and go.
You probably didn't need to flash anything, just factory reset and WAIT... a factory reset on the Moto G3 can take 10-20 minutes to complete, then the first boot can be 10, 15, even 20 minutes of panic... you just have to be patient.
Problem is now you have started a flash process, but it sounds like you not in oem fb_mode because your sparcechunks are not taking... You need to slow down and start over, and make sure you have a complete firmware image and are following these instructions EXACTLY.
It is somewhat difficult to brick a Moto G, although not impossible, chances are in all this there wasn't enough patience... some things this phone does takes a scary amount of time.
Dear acejavelin, thank you for answering.
I tried a factory reset and waited, mainly because I didn't know what to do next...the reset didn't complete in 30 minutes.
Now (and when factory reset didn't complete), I follow exactly the instructions at http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750, including the lines for partition and bootloader:
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 system system.img_sparsechunk.0 <- This always times out after 7200sec, 5000sec, ...
This last step never completed. Then I start again from beginning (from "oem fb_mode_set") with no success.
Also this step:
fastboot erase userdata
times out (once I tried to skip system.img_sparsechunk.0 and go ahead)
Flashing the bootloader works, I tried 1st with bootloader of Android 6.0 and it showed correct version at reboot, and with version 6.0.1.
Now I cannot dowgrade from this level (when flashing boot.img, recovery.img) but always stuck at system.
I think I have lost my phone.
ziko111 said:
Dear acejavelin, thank you for answering.
I tried a factory reset and waited, mainly because I didn't know what to do next...the reset didn't complete in 30 minutes.
Now (and when factory reset didn't complete), I follow exactly the instructions at http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750, including the lines for partition and bootloader:
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 system system.img_sparsechunk.0 <- This always times out after 7200sec, 5000sec, ...
This last step never completed. Then I start again from beginning (from "oem fb_mode_set") with no success.
Also this step:
fastboot erase userdata
times out (once I tried to skip system.img_sparsechunk.0 and go ahead)
Flashing the bootloader works, I tried 1st with bootloader of Android 6.0 and it showed correct version at reboot, and with version 6.0.1.
Now I cannot dowgrade from this level (when flashing boot.img, recovery.img) but always stuck at system.
I think I have lost my phone.
Click to expand...
Click to collapse
Unfortunately, I have to agree... You could try manually erasing and formatting the main partitions before starting.
fastboot erase userdata
fastboot erase cache
fastboot erase system
fastboot erase boot
fastboot flash partition gpt.bin
fastboot format userdata
fastboot format cache
fastboot format system
fastboot format boot
Then attempt the factory flash again, at this point it can't hurt anything... Under no circumstances do a fastboot erase all though, if you do might as well throw it in the trash.
Since this problem occurred while attempting to unlock the device, might be worth a shot to post in the official Motorola forums.
ziko111 said:
Dear acejavelin, thank you for answering.
I tried a factory reset and waited, mainly because I didn't know what to do next...the reset didn't complete in 30 minutes.
Now (and when factory reset didn't complete), I follow exactly the instructions at http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750, including the lines for partition and bootloader:
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 system system.img_sparsechunk.0 <- This always times out after 7200sec, 5000sec, ...
This last step never completed. Then I start again from beginning (from "oem fb_mode_set") with no success.
Also this step:
fastboot erase userdata
times out (once I tried to skip system.img_sparsechunk.0 and go ahead)
Flashing the bootloader works, I tried 1st with bootloader of Android 6.0 and it showed correct version at reboot, and with version 6.0.1.
Now I cannot dowgrade from this level (when flashing boot.img, recovery.img) but always stuck at system.
I think I have lost my phone.
Click to expand...
Click to collapse
Which stock rom have you downloaded? What variant of Moto G 2015 do you have?
EvilHowl said:
Which stock rom have you downloaded? What variant of Moto G 2015 do you have?
Click to expand...
Click to collapse
Hi, thank you
I have a moto XT1541 with 1GB RAM/8GB emmc.
I only used rom from xda-developers (http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639).
I first tried with this:
v6.0 - XT1541_OSPREY_RETEU_6.0_MPI24.65-33_cid7
Then I thought v6.0.1 could have been better so,
v.6.0.1 - XT1541_OSPREY_RETEU_6.0.1_MPI24.107-55_cid7
then, since I had a Vodafone EU phone, this one:
v.6.0.1 - XT1541_OSPREY_VFEU_6.0.1_MPI24.107-55-2_cid7
From fastboot getvar all, I still have v 6.0 (flash system always failed):
(bootloader) ro.build.fingerprint[0]: motorola/osprey_vfeu/osprey_umts:6
(bootloader) ro.build.fingerprint[1]: .0/MPI24.65-33/36:user/release-key
(bootloader) ro.build.fingerprint[2]: s
(bootloader) ro.build.version.full[0]: Blur_Version.24.41.33.osprey_vfeu
(bootloader) ro.build.version.full[1]: .vfeu.en.EU
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LA.BR.1.1.3_RB1.
(bootloader) ro.build.version.qcom[1]: 05.01.00.032.015
At any point in the process are you getting a "Pre-flash validation error" or any response other than OK up until the sparcechunk timeout?
acejavelin said:
At any point in the process are you getting a "Pre-flash validation error" or any response other than OK up until the sparcechunk timeout?
Click to expand...
Click to collapse
I get "Pre-flash validation error" only if I try v6.0.
With v.6.0.1 I arrive with all OKs till system.img which hangs.
When I boot, I get "failed to validate system image", also for recovery
ziko111 said:
I get "Pre-flash validation error" only if I try v6.0.
With v.6.0.1 I arrive with all OKs till system.img which hangs.
When I boot, I get "failed to validate system image", also for recovery
Click to expand...
Click to collapse
OK... Next time try
fastboot erase system
fastboot format system
Right before starting the sparcechunks. If that fails, probably bricked.
acejavelin said:
OK... Next time try
fastboot erase system
fastboot format system
Right before starting the sparcechunks. If that fails, probably bricked.
Click to expand...
Click to collapse
#fastboot oem fb_mode_set
OKAY
#fastboot flash partition gpt.bin
OKAY
#fastboot flash bootloader bootloader.img
OKAY
#fastboot flash logo logo.bin
OKAY
#fastboot flash boot boot.img
OKAY
#fastboot flash recovery recovery.img
OKAY
#fastboot erase system
erasing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.104s
# fastboot format system
Formatting is not supported for filesystem with type 'raw'.
Thank you for trying.
Will Motorola be able to recover the phone? Or will they propose to change motherboard for a fool price?
ziko111 said:
#fastboot oem fb_mode_set
OKAY
#fastboot flash partition gpt.bin
OKAY
#fastboot flash bootloader bootloader.img
OKAY
#fastboot flash logo logo.bin
OKAY
#fastboot flash boot boot.img
OKAY
#fastboot flash recovery recovery.img
OKAY
#fastboot erase system
erasing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.104s
# fastboot format system
Formatting is not supported for filesystem with type 'raw'.
Thank you for trying.
Will Motorola be able to recover the phone? Or will they propose to change motherboard for a fool price?
Click to expand...
Click to collapse
Hmm... /system should be ext4, not raw... Since your locked I guess you're kind of screwed. Sorry.
Can you try flashing TWRP again? There is a repair file system option in TWRP>Wipe>Advanced Wipe. You can try that and then start fastboot flashing the stock firmware again, hoping for the best.
BTW, what does it say in the bootloader menu- locked or unlocked? Is the device status official, unofficial or engineering (<- not good)?
Broadcasted from Zeta Reticuli
Gravemind2015 said:
Can you try flashing TWRP again? There is a repair file system option in TWRP>Wipe>Advanced Wipe. You can try that and then start fastboot flashing the stock firmware again, hoping for the best.
BTW, what does it say in the bootloader menu- locked or unlocked? Is the device status official, unofficial or engineering (<- not good)?
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
He messed up while unlocking his bootloader. I doubt there's anyway to install TRWP. He's better off sending it to Motorola, they'll fix it since it isn't unlocked yet
firuzmaster said:
He messed up while unlocking his bootloader. I doubt there's anyway to install TRWP. He's better off sending it to Motorola, they'll fix it since it isn't unlocked yet
Click to expand...
Click to collapse
Yes, they will fix it but not under warranty... Once the unlock code is issued the warranty is done.
Recently I rooted my phone and flash the resurrection remix naught in moto g3 xt1550....
For some reason I start to flash firmware ROM .....but it is not flashing.... Shows " preflash validation failed " and on system image " invalid image" .......... I tried many times but it didn't flash......when I skip the partition gpt file then every image file start flashing and phone start..,..
But their is no network......
After that whenever I switch off or reboot or go to recovery rather than that it start boot loader....
Then I flashed the resurrection remix again..... When I press reboot after flashing then it goes to boot loader......
At boot loader I press power on then it start booting and there is no network in this ROM too......
What can I do now ...... Please help.........
To clear the Fastboot mode, in fastboot enter "fastboot oem fb_mode_clear" and after that it should start the OS without going into fastboot each time.
The fact this is happening leads me to believe your other problem is related... meaning you didn't flash the stock images properly. If you have no network then you need to reflash the radio stack and boot.img file, they must match and you have to erase the modemstX partitions for the radios to work properly.
yes U will get the error of "preflash validation failed" cause of the security update which motorola released for the month of October, January and recent April.... Do one thing again flash the appropriate stock rom according to ur mobile But skip these two steps/Files >>> 1) fastboot flash partition gpt.bin and 2) fastboot flash bootloader bootloader.img and enter the remaining command/or follow the whole procedure but skip these two file mentioned above U will succed:fingers-crossed::good:
For ur simplicity im providing u commands and plz CHECK UR SPARSECHUNK Files it varies according to mobile I have 7 thats y 7 sparsechunk files DO CHECK URs ok>>>>
fastboot oem fb_mode_set
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 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
Do it ur own risk Im not responsible for any damage :laugh:
everything went well except my network .........i checked in about phone < status < imei no is " 0 ".......how to restore that...........i think thats why the network isn't showing.......................
acejavelin said:
To clear the Fastboot mode, in fastboot enter "fastboot oem fb_mode_clear" and after that it should start the OS without going into fastboot each time.
The fact this is happening leads me to believe your other problem is related... meaning you didn't flash the stock images properly. If you have no network then you need to reflash the radio stack and boot.img file, they must match and you have to erase the modemstX partitions for the radios to work properly.
Click to expand...
Click to collapse
where I find radio stack...... I don't know........and I didn't flash the stock images correctly because I have to skip the partition gpt and bootloader......
give me something else to solve it......
btw thanks sir......:good:
heisenberg1546 said:
where I find radio stack...... I don't know........and I didn't flash the stock images correctly because I have to skip the partition gpt and bootloader......
give me something else to solve it......
btw thanks sir......:good:
Click to expand...
Click to collapse
The "radio stack" is the relevant radio portions of the firmware image...
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
It is not uncommon that they don't take the first time, repeat it and the boot.img command. Verify EVERY command returns an OKAY response, if not, repeat it.
And do not copy and paste the commands all at once, type them out and look at the response, or at least copy and paste each command individually.
acejavelin said:
The "radio stack" is the relevant radio portions of the firmware image...
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
It is not uncommon that they don't take the first time, repeat it and the boot.img command. Verify EVERY command returns an OKAY response, if not, repeat it.
And do not copy and paste the commands all at once, type them out and look at the response, or at least copy and paste each command individually.
Click to expand...
Click to collapse
isn't working sir........
I did without copy paste.........
boot img command gives preflash validation failed....
heisenberg1546 said:
It is not uncommon that they don't take the first time, repeat it and the boot.img command. Verify EVERY command returns an OKAY response, if not, repeat it.
And do not copy and paste the commands all at once, type them out and look at the response, or at least copy and paste each command individually.
isn't working sir........
I did without copy paste.........
boot img command gives preflash validation failed....
Click to expand...
Click to collapse
You didn't do the boot.img... but Might want to look at the IMEI 0 recovery thread... I don't have any more ideas.
acejavelin said:
You didn't do the boot.img... but Might want to look at the IMEI 0 recovery thread... I don't have any more ideas.
Click to expand...
Click to collapse
After those commands ...... I flash again all img's including the boot.img......
How to restore the imei file ..... Like in mediatek device ,,, we can write by sn tools .....
heisenberg1546 said:
After those commands ...... I flash again all img's including the boot.img......
How to restore the imei file ..... Like in mediatek device ,,, we can write by sn tools .....
Click to expand...
Click to collapse
I don't know... There is a thread here specifically about it, you will have to look there.
I want to keep the custom rom (RR-O-v6.0.0-20180511-ospreyl) with all networks
acejavelin said:
To clear the Fastboot mode, in fastboot enter "fastboot oem fb_mode_clear" and after that it should start the OS without going into fastboot each time.
The fact this is happening leads me to believe your other problem is related... meaning you didn't flash the stock images properly. If you have no network then you need to reflash the radio stack and boot.img file, they must match and you have to erase the modemstX partitions for the radios to work properly.
Click to expand...
Click to collapse
Hey, I have installed RR-O-v6.0.0-20180511-osprey on Moto G(3rd Generation), and now the error is: "No sim Detected ", IMEI number is fine. I want to flash radio firmware in this custom Rom. Will flashing radio stack of stock rom 6.0.1 (Moto G3 x1550) work?
adb reboot bootloader
fastboot flash modem NON-HLOS.bin (That must of Moto G3?)
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash boot boot.img (Is it to be of RR or of Moto?)
fastboot reboot
Is there any other option or solution then please mention.
You need to flash stock firmware first then your network problem solved then you can install custom roms?
Good Luck!
i have the official firmware downloaded using Lenovo Moto Smart Assistant: OCEAN_PPOS29.114_134_7_1_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml
running a batch file with the following
Code:
fastboot set_active a
fastboot reboot-bootloader
sleep 5
fastboot oem lock begin
fastboot oem lock begin
fastboot getvar max-sparse-size
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.exe erase modemst1
fastboot.exe erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.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 system system.img_sparsechunk.9
fastboot flash system_b system.img_sparsechunk.0
fastboot flash system_b system.img_sparsechunk.1
fastboot flash system_b system.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot.exe erase carrier
fastboot.exe erase userdata
fastboot.exe erase ddr
fastboot oem fb_mode_clear
fastboot oem lock
pause
when i run
Code:
fastboot oem lock
the final time it tells me "Still Requires Signed Boot.Img"
flashing the boot.image results in "(bootloader) Still require signed boot.img"
any ideas where i can get a working boot.img?
MadMan29729 said:
i have the official firmware downloaded using Lenovo Moto Smart Assistant: OCEAN_PPOS29.114_134_7_1_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml
running a batch file with the following
when i run the final time it tells me "Still Requires Signed Boot.Img"
flashing the boot.image results in "(bootloader) Still require signed boot.img"
any ideas where i can get a working boot.img?
Click to expand...
Click to collapse
(coming from flashing stock)
fastboot oem lock begin
fastboot oem lock begin
fastboot oem lock
fastboot oem lock
fastboot oem lock
fastboot flash boot boot.img
fastboot oem lock
vinoxflame said:
(coming from flashing stock)
fastboot oem lock begin
fastboot oem lock begin
fastboot oem lock
fastboot oem lock
fastboot oem lock
fastboot flash boot boot.img
fastboot oem lock
Click to expand...
Click to collapse
that worked! Thanks!
that didn't lock mine
C:\ADB>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (32768 KB)...
OKAY [ 0.993s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.763s]
finished. total time: 1.760s
C:\ADB>fastboot oem lock
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.012s]
finished. total time: 0.014s
your going to have to root it with magisk or the option will be greyed out and say "bootloader already unlocked".. once you have a booted rooted rom, goto developer options and check enable Allow OEM Unlock..
MadMan29729 said:
your going to have to root it with magisk or the option will be greyed out and say "bootloader already unlocked".. once you have a booted rooted rom, goto developer options and check enable Allow OEM Unlock..
Click to expand...
Click to collapse
So have to to root it first, then lock the bootloader?
endleesss said:
So have to to root it first, then lock the bootloader?
Click to expand...
Click to collapse
Yeah that doesn't sound like a good idea.
Sent from my mata using XDA Labs
---------- Post added at 05:58 AM ---------- Previous post was at 05:56 AM ----------
Make sure you have the correct software channel
Sent from my mata using XDA Labs
yes cause that's what I had to do cause motorola won't let you relock it unless you flash the factory firmware along with the lock command but you can't lock it without checking allow oem unlock
endleesss said:
So have to to root it first, then lock the bootloader?
Click to expand...
Click to collapse
its the only way to get rid of the bootloader error that says you need to enable Allow OEM Unlock.. rooting with magisk just forces the allow oem unlock to be enabled.. so you can check it..
as far as locking.. once you run the lock commands you have to flash the factory images then run the lock command again.. therefore you won't be rooted in the end!
Question for anyone who may know ..
So if we're already rooted and we would like to lock our bootloader we have to flash our factory image and type in the bootloader lock command as well?
Anyone successfully locked there bootloader?
If we have an unlocked bootloader and we lock it can we return back to unlocked bootloader immediately afterwards? Has anyone done this? Do we use same method as we initially did to unlock our bootloader? I only say that because I do not have my original code for my bootloader unlock that I used. If we go about it same way will Motorola give us the code again or do we need to still have those #s that we originally used?
I'm on a mission now. Soon as I comment this I'll search my butt off for a while and see what all I can figure out. If I get any good solid information I shall return here and share it for sure. Good day to everyone.
---------- Post added at 07:21 PM ---------- Previous post was at 07:08 PM ----------
Credit to @smokinu from motp G7 River forum. I'm pasting the comment here below.
I saw the same thing on my end at first. Found this to work repeatedly....
fastboot oem lock (enter this a few times until i says something to the effect of...."you still need to flash a signed boot.img")
fastboot flash boot boot.img (this will now flash fine without saying the image is not signed)
fastboot oem lock (if you prefer to re-lock. You'll need the unlock key again if you plan to unlock).
Above is from post #34 here: https://forum.xda-developers.com/mo...are-29-114-t3913673/post79305396#post79305396 And I'm quite sure the same method will work for Power although I have not tested this. Pretty sure it will though.
In order to relock my bootloader, I had to root my phone using the magisk method.
After I was rooted I was able to go into develope options and turn on allow oem unlocking.
Then, I was able to flash the signed bootloader from an oem firmware and relock the bootloader.
You must use the same bootloader version that is currently on your phone. You can not downgrade the bootloader.
And yes, you can unlock it at a later time.
Sent from my moto g(7) power using Tapatalk
MrCamby said:
In order to relock my bootloader, I had to root my phone using the magisk method.
After I was rooted I was able to go into develope options and turn on allow oem unlocking.
Then, I was able to flash the signed bootloader from an oem firmware and relock the bootloader.
You must use the same bootloader version that is currently on your phone. You can not downgrade the bootloader.
And yes, you can unlock it at a later time.
Click to expand...
Click to collapse
Thanks for the info! I always just assume on any device that bootloader can't be downgraded. When I first get the device anyway.. thanks!
can you help me relock bootloader of motorola one p30 play? i am having same issue even after typing
fastboot oem lock begin
fastboot oem lock begin
fastboot oem lock
fastboot oem lock
fastboot oem lock
fastboot flash boot boot.img
fastboot oem lock
it still says "still require signed boot.img"
also i have a dual slot partition slot phone