My boot loader is unlocked and am rooted with the stock recovery. My model is XT1550 (dual sim variant in India). I received the OTA updates today.. I downloaded them and installed.. The installation looked like it went fine.. after the installation the phone restarted.. but it kind of went to a boot loop after that.. I can power off the phone pressing the power button for some time.. bu the phone powers off and restarts automatically... it does not progress beyond the few initial screens after which it just displays a blank display...
I am able to get into flashmode.. however, my pc does not recognize the device.. adb terminal shows no devices when I give "adb devices" command.. can someone help? Can I do a factory reset from the flashboot menu? what does the factory mode do? what else can be done to salvage the situation? Thanks.
Update: I went into the stock recovery and did a factory reset. It wiped the user data and did a factory reset. After this I tried rebooting the system. But again the same problem. The phone starts and after the first two -three screens of a boot animation it simply gives me a blank screen display. Really worried now.. Any help?
Flash STOCK FIRMWARE
coolmalayalee said:
My boot loader is unlocked and am rooted with the stock recovery. My model is XT1550 (dual sim variant in India). I received the OTA updates today.. I downloaded them and installed.. The installation looked like it went fine.. after the installation the phone restarted.. but it kind of went to a boot loop after that.. I can power off the phone pressing the power button for some time.. bu the phone powers off and restarts automatically... it does not progress beyond the few initial screens after which it just displays a blank display...
I am able to get into flashmode.. however, my pc does not recognize the device.. adb terminal shows no devices when I give "adb devices" command.. can someone help? Can I do a factory reset from the flashboot menu? what does the factory mode do? what else can be done to salvage the situation? Thanks.
Update: I went into the stock recovery and did a factory reset. It wiped the user data and did a factory reset. After this I tried rebooting the system. But again the same problem. The phone starts and after the first two -three screens of a boot animation it simply gives me a blank screen display. Really worried now.. Any help?
Click to expand...
Click to collapse
Hi, I have faced the same issue that you have faced. I will be resorting to flashing original STOCK ROM using the ADB commands.
There are other threads in this forum explaining the procedure.
Don't worry. If you follow the procedure correctly you will be able to reinstall the system and use your phone again.
After flashing STOCK ROM and before installing OTA update, please ensure that your phone has stock recovery and is not rooted. Other wise you will face similar issue.
To go to fastboot mode from the blank screen mode you may follow the steps below:
1. Keep the power key pressed for a few seconds till you can see that the screen has gone completely black (otherwise you will see the screen dimly lit)
2. Immediately after this step press the volume down button first followed by power button and hold for a second or two and release the buttons, you would be in the fastboot mode
3. You can connect your phone to the PC in this mode to flash the STOCK ROM using the flash boot commands
4. You will find the STOCK ROM in the following link
http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
5. For installation procedure and fastboot commands refer this link:
http://www.gammerson.com/2015/08/how-to-flash-stock-firmware-of-Moto-g-3rd-gen.html
Hope this helps
arunhebbare; said:
Hi, I have faced the same issue that you have faced. I will be resorting to flashing original STOCK ROM using the ADB commands.
There are other threads in this forum explaining the procedure.
Don't worry. If you follow the procedure correctly you will be able to reinstall the system and use your phone again.
After flashing STOCK ROM and before installing OTA update, please ensure that your phone has stock recovery and is not rooted. Other wise you will face similar issue.
To go to fastboot mode from the blank screen mode you may follow the steps below:
1. Keep the power key pressed for a few seconds till you can see that the screen has gone completely black (otherwise you will see the screen dimly lit)
2. Immediately after this step press the volume down button first followed by power button and hold for a second or two and release the buttons, you would be in the fastboot mode
3. You can connect your phone to the PC in this mode to flash the STOCK ROM using the flash boot commands
4. You will find the STOCK ROM in the following link
http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
5. For installation procedure and fastboot commands refer this link:
http://www.gammerson.com/2015/08/how-to-flash-stock-firmware-of-Moto-g-3rd-gen.html
Hope this helps
Click to expand...
Click to collapse
Thanks a lot. I can get into fastbot mod. However, when I type adb devices from the command prompt it doesnt list any devices. Will I be able to flash anything in such a situation? I already have the stock firmware extracted to my adb folder.
Update: I have flashed the stock firmware successfully. The device is back up and running now.. thanks a lot..
coolmalayalee said:
Thanks a lot. I can get into fastbot mod. However, when I type adb devices from the command prompt it doesnt list any devices. Will I be able to flash anything in such a situation? I already have the stock firmware extracted to my adb folder.
Update: I have flashed the stock firmware successfully. The device is back up and running now.. thanks a lot..
Click to expand...
Click to collapse
Can you please let us know what you did to over come the problem of your device not being able to be recognized by ADB fastboot?
Also which STOCK firmware did you use (there are two in the link)?
Could you download and update via the OTA?
Your reply would help others. Thanks
arunhebbare said:
Can you please let us know what you did to over come the problem of your device not being able to be recognized by ADB fastboot?
Also which STOCK firmware did you use (there are two in the link)?
Could you download and update via the OTA?
Your reply would help others. Thanks
Click to expand...
Click to collapse
Well, after getting into fastboot when I use the command "adb devices" it did not show anything under the list of devices. However, when I started giving the commands for flashing the stock firmware it was accepting the adb commands. I followed the commands here.
http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
and I used the stock firmware XT1550_OSPREY_RETASIA-INDIA_DS_2GB_5.1.1_LPI23.72-47_cid7 for this purpose downloaded from
http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639 things were alright. But I need to say that the first command "fastboot flash partition gpt.bin" did fail in fastboot. But I went ahead and gave all the subsequent commands all of which were successful and in the end I was able to restart with the new factory image.
However, all my data lost, root lost, and my boot loader is still in unlocked status.
About OTAs, I don't know. I went to the system updates to see if there is an OTA.. it says my software is up to date.
Thanks
That was a fast reply. Thanks for elaborating.
Don't know what the consequences of not being able to flash the gpt.bin are...
I will post update after flashing stock rom after reaching home. Stuck in office still...
Hello,
A little info about adb/fastboot :
adb works only after boot.
fastboot works in fastboot mode.
When you boot to fastboot mode and try commands such as "adb devices" you won't see any output or may get an error as the device is connected in fastboot mode.
So using "fastboot devices" will return all device ids connected in fastboot mode.
Hope this helps other new users.
arunhebbare said:
That was a fast reply. Thanks for elaborating.
Don't know what the consequences of not being able to flash the gpt.bin are...
I will post update after flashing stock rom after reaching home. Stuck in office still...
Click to expand...
Click to collapse
This is the message I get after gpt.bin flashing.
sending 'partition' (32 KB)...
OKAY [ 0.059s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
Click to expand...
Click to collapse
Below is a response I saw in reddit on this error. Looks like it should be fine.
That normally happens when you try to downgrade. GPT.bin and motoboot should fail to flash if you're trying to downgrade; prevent a hardbrick. As long as all the other commands are flashing successfully you'll be fine.
Click to expand...
Click to collapse
https://www.reddit.com/r/MotoG/comments/3dxmso/xt_1032_mfastboot_preflash_validation_failed/
Edit: Deleted
Flashed Stock rom. up and about
I flashed the stock 23.72.47 version using fastboot commands.
The flashing of gpt.bin failed but all the other commands were successful.
I had unlocked my bootloader previously which is still showing as unlocked.
Yes, I made a mistake of using adb commands in fastboot. In bootloader we got to use fastboot commands and adb does not work.
I respect this forum for these exact reasons that things are no nonsense here and this is the place for really knowledgeable people.
Thanks for bearing noobs like me.
Lastly my beloved moto g3 is up and about and doing fine.
Oh BTW I too checked for updates and found that the the stock rom 23.72.47 seems to be the updated version with the Ota incorporated. Earlier I was on the 23.72.33 rom.
Thank you members.
boot loupe due to an update
i was used all commands in cmd prompt but in in cmd prompt it was saying like that
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
error: cannot load 'gpt.bin': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash motoboot motoboot.img
target reported max download size of 268435456 bytes
error: cannot load 'motoboot.img': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash logo logo.bin
target reported max download size of 268435456 bytes
error: cannot load 'logo.bin': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
error: cannot load 'boot.img': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
error: cannot load 'recovery.img': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash system system.img_spar
sechunk1
target reported max download size of 268435456 bytes
error: cannot load 'system.img_sparsechunk1': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash system system.img_spar
echunk2
target reported max download size of 268435456 bytes
error: cannot load 'system.img_sparechunk2': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash system system.img_spar
sechunk3
target reported max download size of 268435456 bytes
error: cannot load 'system.img_sparsechunk3': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash modem NON-HLOS.bin
target reported max download size of 268435456 bytes
error: cannot load 'NON-HLOS.bin': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.062s]
finished. total time: 0.085s
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.021s]
finished. total time: 0.022s
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash fsg fsg.mbn
target reported max download size of 268435456 bytes
error: cannot load 'fsg.mbn': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot erase cache
erasing 'cache'...
OKAY [ 0.119s]
finished. total time: 0.120s
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.975s]
finished. total time: 0.976s
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot reboot
< waiting for device >
rebooting...
finished. total time: 0.007s
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>
i was tried a lot in my motog3 device after rebooting also it was showing blank dimly light it was not turning on my device had got a ota update so i was updated after that update i was installed then restarted the mobile after that it was no starting at all showing blank in that case also i was factory data reset my phone in recovery mode but still also it was restating with moto logo and then showing blank please help
Out of curiosity I flashed the 23.72.33 and updated via ota. The version it shows is 23.72-47.4.
Observing the ota results.
pranaykumar3318 said:
i was used all commands in cmd prompt but in in cmd prompt it was saying like that
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
error: cannot load 'gpt.bin': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash motoboot motoboot.img
target reported max download size of 268435456 bytes
error: cannot load 'motoboot.img': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash logo logo.bin
target reported max download size of 268435456 bytes
error: cannot load 'logo.bin': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
error: cannot load 'boot.img': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
error: cannot load 'recovery.img': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash system system.img_spar
sechunk1
target reported max download size of 268435456 bytes
error: cannot load 'system.img_sparsechunk1': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash system system.img_spar
echunk2
target reported max download size of 268435456 bytes
error: cannot load 'system.img_sparechunk2': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash system system.img_spar
sechunk3
target reported max download size of 268435456 bytes
error: cannot load 'system.img_sparsechunk3': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash modem NON-HLOS.bin
target reported max download size of 268435456 bytes
error: cannot load 'NON-HLOS.bin': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.062s]
finished. total time: 0.085s
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.021s]
finished. total time: 0.022s
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash fsg fsg.mbn
target reported max download size of 268435456 bytes
error: cannot load 'fsg.mbn': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot erase cache
erasing 'cache'...
OKAY [ 0.119s]
finished. total time: 0.120s
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.975s]
finished. total time: 0.976s
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot reboot
< waiting for device >
rebooting...
finished. total time: 0.007s
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>
i was tried a lot in my motog3 device after rebooting also it was showing blank dimly light it was not turning on my device had got a ota update so i was updated after that update i was installed then restarted the mobile after that it was no starting at all showing blank in that case also i was factory data reset my phone in recovery mode but still also it was restating with moto logo and then showing blank please help
Click to expand...
Click to collapse
Try it again using fastboot not mfastboot
i was done
thanks friend i was done finally i was installed stock firmwere thanks to xda developers
---------- Post added at 02:14 PM ---------- Previous post was at 02:00 PM ----------
arunhebbare said:
Hi, I have faced the same issue that you have faced. I will be resorting to flashing original STOCK ROM using the ADB commands.
There are other threads in this forum explaining the procedure.
Don't worry. If you follow After flashthe procedure correctly you will be able to reinstall the system and use your phone again.
after installing STOCK ROM and before installing OTA update, please ensure that your phone has stock recovery and is not rooted. Other wise you will face similar issue.
To go to fastboot mode from the blank screen mode you may follow the steps below:
1. Keep the power key pressed for a few seconds till you can see that the screen has gone completely black (otherwise you will see the screen dimly lit)
2. Immediately after this step press the volume down button first followed by power button and hold for a second or two and release the buttons, you would be in the fastboot mode
3. You can connect your phone to the PC in this mode to flash the STOCK ROM using the flash boot commands
4. You will find the STOCK ROM in the following link
http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
5. For installation procedure and fastboot commands refer this link:
http://www.gammerson.com/2015/08/how-to-flash-stock-firmware-of-Moto-g-3rd-gen.html
Hope this helps
Click to expand...
Click to collapse
i was successfully installed stockfirmwere in my motog3 but still the bootloader is unlocked will you please say that if i unlock the bootloader and then update my device without root will i face the bootloupe problem?? and again i dont want to face bootloupe problems after an otp update will you please say that what type of rules i have to follow to not face this type of problem
and you said that the after installing STOCK ROM and before installing OTA update, please ensure that your phone has stock recovery and is not rooted. will you please say that how to ensure that my phone has stock recovery
my thought
coolmalayalee said:
My boot loader is unlocked and am rooted with the stock recovery. My model is XT1550 (dual sim variant in India). I received the OTA updates today.. I downloaded them and installed.. The installation looked like it went fine.. after the installation the phone restarted.. but it kind of went to a boot loop after that.. I can power off the phone pressing the power button for some time.. bu the phone powers off and restarts automatically... it does not progress beyond the few initial screens after which it just displays a blank display...
I am able to get into flashmode.. however, my pc does not recognize the device.. adb terminal shows no devices when I give "adb devices" command.. can someone help? Can I do a factory reset from the flashboot menu? what does the factory mode do? what else can be done to salvage the situation? Thanks.
Update: I went into the stock recovery and did a factory reset. It wiped the user data and did a factory reset. After this I tried rebooting the system. But again the same problem. The phone starts and after the first two -three screens of a boot animation it simply gives me a blank screen display. Really worried now.. Any help?
Click to expand...
Click to collapse
so far i have learned that before applying official ota one must have bootloader relock and everything official like recovery etc etc and may be no root (do not remember no root thing well)
i may be wrong but sharing is caring right?
umo4u said:
so far i have learned that before applying official ota one must have bootloader relock and everything official like recovery etc etc and may be no root (do not remember no root thing well)
i may be wrong but sharing is caring right?
Click to expand...
Click to collapse
It doesn't need bootloader relocked but you need stock rom(no Mods or root) and stock recovery to do ota
---------- Post added at 15:56 ---------- Previous post was at 15:53 ----------
pranaykumar3318 said:
thanks friend i was done finally i was installed stock firmwere thanks to xda developers
---------- Post added at 02:14 PM ---------- Previous post was at 02:00 PM ----------
i was successfully installed stockfirmwere in my motog3 but still the bootloader is unlocked will you please say that if i unlock the bootloader and then update my device without root will i face the bootloupe problem?? and again i dont want to face bootloupe problems after an otp update will you please say that what type of rules i have to follow to not face this type of problem
and you said that the after installing STOCK ROM and before installing OTA update, please ensure that your phone has stock recovery and is not rooted. will you please say that how to ensure that my phone has stock recovery
Click to expand...
Click to collapse
If you reflashed stock firmware then you will have stock recovery and not twrp to find out reboot into your bootloader then use arrow keys until get to option saying recovery then select if its stock it will look abit like cwm but call android 3e recovery or something close to that if not it will boot into twrp
minidude2012 said:
It doesn't need bootloader relocked but you need stock rom(no Mods or root) and stock recovery to do ota
---------- Post added at 15:56 ---------- Previous post was at 15:53 ----------
If you reflashed stock firmware then you will have stock recovery and not twrp to find out reboot into your bootloader then use arrow keys until get to option saying recovery then select if its stock it will look abit like cwm but call android 3e recovery or something close to that if not it will boot into twrp
Click to expand...
Click to collapse
once upon a time I used to have HTC phone and I landed in same problem and learned things from there so what I shared is half true though
minidude2012 said:
It doesn't need bootloader relocked but you need stock rom(no Mods or root) and stock recovery to do ota
---------- Post added at 15:56 ---------- Previous post was at 15:53 ----------
If you reflashed stock firmware then you will have stock recovery and not twrp to find out reboot into your bootloader then use arrow keys until get to option saying recovery then select if its stock it will look abit like cwm but call android 3e recovery or something close to that if not it will boot into twrp
Click to expand...
Click to collapse
thanks for your fast replay
Thanks
arunhebbare said:
Hi, I have faced the same issue that you have faced. I will be resorting to flashing original STOCK ROM using the ADB commands.
There are other threads in this forum explaining the procedure.
Don't worry. If you follow the procedure correctly you will be able to reinstall the system and use your phone again.
After flashing STOCK ROM and before installing OTA update, please ensure that your phone has stock recovery and is not rooted. Other wise you will face similar issue.
To go to fastboot mode from the blank screen mode you may follow the steps below:
1. Keep the power key pressed for a few seconds till you can see that the screen has gone completely black (otherwise you will see the screen dimly lit)
2. Immediately after this step press the volume down button first followed by power button and hold for a second or two and release the buttons, you would be in the fastboot mode
3. You can connect your phone to the PC in this mode to flash the STOCK ROM using the flash boot commands
4. You will find the STOCK ROM in the following link
http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
5. For installation procedure and fastboot commands refer this link:
http://www.gammerson.com/2015/08/how-to-flash-stock-firmware-of-Moto-g-3rd-gen.html
Hope this helps
Click to expand...
Click to collapse
Thanks bro.
Related
I wanted to flash the latest update of RR7 but when i tried to get into the recovery the phone would reboot and show the twrp starting screen and then it would reboot again and start normally. I figured something must have gone wrong and reflashed twrp from my pc, however the issue persists. Flashify doesn't work either. So aside from a clean install, is there a workaround?
BoredDude said:
I wanted to flash the latest update of RR7 but when i tried to get into the recovery the phone would reboot and show the twrp starting screen and then it would reboot again and start normally. I figured something must have gone wrong and reflashed twrp from my pc, however the issue persists. Flashify doesn't work either. So aside from a clean install, is there a workaround?
Click to expand...
Click to collapse
You can try to boot directly into twrp with "fastboot boot TWRP.img"
zys52712 said:
You can try to boot directly into twrp with "fastboot boot TWRP.img"
Click to expand...
Click to collapse
Just tried it, same thing happens i can see the twrp starting screen but i can get to the main menu.
EDIT.
Changed the twrp version to an older one. No results, tried both flashing and booting from fastboot.
i get the following message:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp2.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (14796 KB)...
OKAY [ 0.479s]
writing 'recovery'...
OKAY [ 1.566s]
finished. total time: 2.049s
zys52712 said:
You can try to boot directly into twrp with "fastboot boot TWRP.img"
Click to expand...
Click to collapse
BoredDude said:
Just tried it, same thing happens i can see the twrp starting screen but i can get to the main menu.
EDIT.
Changed the twrp version to an older one. No results, tried both flashing and booting from fastboot.
i get the following message:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp2.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (14796 KB)...
OKAY [ 0.479s]
writing 'recovery'...
OKAY [ 1.566s]
finished. total time: 2.049s
Click to expand...
Click to collapse
Then something is really wrong with your internal memory. Because that boot command in the post above does not use TWRP installed on your phone, it's a "temporary" TWRP booted from your PC folder.
Even if you've never installed TWRP on your phone (still have stock recovery) you can still boot to TWRP for a one-time/one-off session by using those commands. Do whatever you want, like install SuperSu, and when you reboot, you'll still have stock recovery!
ChazzMatt said:
Then something is really wrong with your internal memory. Because that boot command in the post above does not use TWRP installed on your phone, it's a "temporary" TWRP booted from your PC folder.
Even if you've never installed TWRP on your phone (still have stock recovery) you can still boot to TWRP for a one-time/one-off session by using those commands. Do whatever you want, like install SuperSu, and when you reboot, you'll still have stock recovery!
Click to expand...
Click to collapse
I fixed it erasing the TWRP folder in my internal storage
Problem with oopof1 phone
I have made Rom for the wrong phone oppof1f and the phone has stopped on this logo
I do not move I have stood on this and I can not enter the recovery permanently, what is the solution?
And sorry if the subject is not in place
Picture of the problem
store6.up-00.com/2017-05/149603505807811.png
So it looks like its trying to install the rom.
if you cant enter recovery.
extract the recovery.img for the stock rom in the link below
boot into fastboot (power and volume up) then,
fastboot flash recovery recovery.img
if you can enter recovery do this.
Turn off the phone and put this rom for the f1f on the micro sd card.
http://community.oppo.com/en/forum.php?mod=viewthread&tid=46153
then hold the power button and volume down and it should come up with a langauge to pick.
then press install from sd card.
select the rom.
if it fails keep trying. u can also try wiping data and cache
Jamie_oppo said:
So it looks like its trying to install the rom.
if you cant enter recovery.
extract the recovery.img for the stock rom in the link below
boot into fastboot (power and volume up) then,
fastboot flash recovery recovery.img
if you can enter recovery do this.
Turn off the phone and put this rom for the f1f on the micro sd card.
http://community.oppo.com/en/forum.php?mod=viewthread&tid=46153
then hold the power button and volume down and it should come up with a langauge to pick.
then press install from sd card.
select the rom.
if it fails keep trying. u can also try wiping data and cache
Click to expand...
Click to collapse
When you press the power button and the volume down, this message appears
Store6.up-00.com/2017-05/149603505807811.png
And unable to enter into recovery
Unable to access your phone
up up up up
If fastboot mode is working, you can try to boot another recovery (twrp, with fastboot boot twrp.img) and wipe the cache partition (that might have update information on it).
If it's not enough, I'd try to wipe data. But before that, try to backup things while TWRP is working.
tarek.eid said:
up up up up
Click to expand...
Click to collapse
Can you boot unto fast boot using power and volume up?
kdd998 said:
If fastboot mode is working, you can try to boot another recovery (twrp, with fastboot boot twrp.img) and wipe the cache partition (that might have update information on it).
If it's not enough, I'd try to wipe data. But before that, try to backup things while TWRP is working.
Click to expand...
Click to collapse
Yes FastBoot mode works
And when working twrp.img recovery
Of this site
Https://twrp.me/devices/oppof1.html
But there is a problem with the message
Target reported max download size of 268435456 bytes
Sending 'recovery' (25858 KB) ...
OKAY [1.142s]
Writing 'recovery' ...
FAILED (remote: Partition flashing is not allowed)
Finished. Total time: 1.157s
Can you explain
Clear the cache section
Jamie_oppo said:
Can you boot unto fast boot using power and volume up?
Click to expand...
Click to collapse
Yes I know how to login to FastBoot mode
But this message appears after the steps are executed
Target reported max download size of 268435456 bytes
Sending 'recovery' (25858 KB) ...
OKAY [1.142s]
Writing 'recovery' ...
FAILED (remote: Partition flashing is not allowed)
Finished. Total time: 1.157s
tarek.eid said:
Yes I know how to login to FastBoot mode
But this message appears after the steps are executed
Target reported max download size of 268435456 bytes
Sending 'recovery' (25858 KB) ...
OKAY [1.142s]
Writing 'recovery' ...
FAILED (remote: Partition flashing is not allowed)
Finished. Total time: 1.157s
Click to expand...
Click to collapse
Type fastboot oem unlock then repeat
Jamie_oppo said:
Type fastboot oem unlock then repeat
Click to expand...
Click to collapse
This message has not been opened
FAILED (remote: oem unlock is not allowed)
Finished. Total time: 0.009s
tarek.eid said:
This message has not been opened
FAILED (remote: oem unlock is not allowed)
Finished. Total time: 0.009s
Click to expand...
Click to collapse
Looks like you have a locked bootloader with unlocking disabled via developer options. With bootloader locked,no recovery and cant boot to rom to enable bootloader unlocking you only real option is to follow instuctions in this post to flash back to original stock firmware using low level QDloader to flash entire phone in factory mode.
PS This is only for f1f not f1s. You do have a f1f, right?
MiniBlu said:
Looks like you have a locked bootloader with unlocking disabled via developer options. With bootloader locked,no recovery and cant boot to rom to enable bootloader unlocking you only real option is to follow instuctions in this post to flash back to original stock firmware using low level QDloader to flash entire phone in factory mode.
PS This is only for f1f not f1s. You do have a f1f, right?
Click to expand...
Click to collapse
Yes my phone is f1f
I will carry
Https://drive.google.com/file/d/0B3vGskcdFbBcVThPS3FIb2dkdGs/view?usp=drivesdk
I will try
Take you
There is a problem with these definitions
Qualcomm HS-USB QDLoader 9008 (COM5
A triangle sign appears that needs to be defined
Does this affect
Even if it has a possible impact on its definition
tarek.eid said:
There is a problem with these definitions
Qualcomm HS-USB QDLoader 9008 (COM5
A triangle sign appears that needs to be defined
Does this affect
Even if it has a possible impact on its definition
Click to expand...
Click to collapse
You need to follow the instruction in the post I linked and "Install the QDLoader driver found in the DRIVER directory of the extracted archive". If its using the correct drivers the triangle should not be there. (you mean in contol panel?)
If you have problems PM the quy who posted the link. He said he would help.
Hello! I tried to root my Honor 6x (BLN-L21, EMUI 5.0) following the instructions there:
cyberkey.in/how-to-root-honor-6x-100-working/
The bootloader was successfully unlocked.
But when I tried to flash TWRP the process failed and now my phone is stuck on boot :
"Your device has been unlocked and can't be trusted [...] Your device is booting now."
I can get access to recovery and fastboot. I wiped the cache and tried a factory reset but nothing changed, my system won't start and I don't know what to do.
Please help!
if you have the boot backup then restore it.
venugopalu007 said:
if you have the boot backup then restore it.
Click to expand...
Click to collapse
I don't have any backup. Is there a way to just reset everything? Also I don't know how to connect to the phone anymore since adb won't find the device.
if you cannot find the boot.img
just do a rollback bro
here is the link
first dload this
http://download-c.huawei.com/download/downloadCenter?downloadId=94070&version=376169&siteCode=de-h
and this now
if your device is BLN-L21C432B151 http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1277/g104/v84712/f1/full/update.zip
or BLN-L21C185B131 http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1277/g104/v75593/f1/full/update.zip
I think that I flashed the wrong files in "boot" and "recovery". Please tell me which files I should flash there.
I used the commands:
.\fastboot flash boot twrp.img
.\fastboot flash recovery twrp.img
Stinks said:
I think that I flashed the wrong files in "boot" and "recovery". Please tell me which files I should flash there.
I used the commands:
.\fastboot flash boot twrp.img
.\fastboot flash recovery twrp.img
Click to expand...
Click to collapse
The guide from "cyberkey.in/how-to-root-honor-6x-100-working/" is simply wrong when it comes to flashing the twrp recovery. If you really followed this guide completely then you flashed the recovery to the boot partition.
Use "fastboot flash recovery twrp.img" to flash the recovery.
You will still have to flash the boot image to your boot partition then (fastboot flash boot boot.img).
Stinks said:
I don't have any backup. Is there a way to just reset everything? Also I don't know how to connect to the phone anymore since adb won't find the device.
Click to expand...
Click to collapse
Use fastboot flash recovery twrpname.img to flash the recovery
Ok so basically I need to flash the boot image. However I don't know where to find the stock boot image. I downloaded the so-called "full version" of the stock firmware that I found here: boycracked.com/2017/07/20/official-huawei-honor-6x-bln-l21-berlin-l21-stock-rom-firmware/
However there was no boot.img file inside.
If you could direct me to the proper stock boot.img or send me one, that would greatly help. I had EMUI 5.0 with Nougat 7.0 I believe, phone version BLN-L21.
V
Stinks said:
Ok so basically I need to flash the boot image. However I don't know where to find the stock boot image. I downloaded the so-called "full version" of the stock firmware that I found here: boycracked.com/2017/07/20/official-huawei-honor-6x-bln-l21-berlin-l21-stock-rom-firmware/
However there was no boot.img file inside.
If you could direct me to the proper stock boot.img or send me one, that would greatly help. I had EMUI 5.0 with Nougat 7.0 I believe, phone version BLN-L21.
Click to expand...
Click to collapse
Bro there is update.app open it with huawei update extractor then you will see the the boot image.but remember the emui 4.1 boot wont help you in emui 5 .the boot.img must be emui 5 once.
venugopalu007 said:
V
Bro there is update.app open it with huawei update extractor then you will see the the boot image.but remember the emui 4.1 boot wont help you in emui 5 .the boot.img must be emui 5 once.
Click to expand...
Click to collapse
Thanks. I successfully updated boot.img and and recovery.img, but system won't load, so I might have imported from the wrong STOCK version.
I tried to reinstall a stock ROM using:
fastboot flash system system.img
But I got this error message:
target reported max download size of 471859200 bytes
sending sparse 'system' (444686 KB)...
OKAY [ 12.901s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 12.929s
Then I tried to erase the system file with "erase system" and got this error:
erasing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 0.013s
I guess that the only option now is to install the files on an external SD card?
Stinks said:
Thanks. I successfully updated boot.img and and recovery.img, but system won't load, so I might have imported from the wrong STOCK version.
I tried to reinstall a stock ROM using:
fastboot flash system system.img
But I got this error message:
target reported max download size of 471859200 bytes
sending sparse 'system' (444686 KB)...
OKAY [ 12.901s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 12.929s
Then I tried to erase the system file with "erase system" and got this error:
erasing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 0.013s
I guess that the only option now is to install the files on an external SD card?
Click to expand...
Click to collapse
Bro y this ,just do a rollback .
Stinks said:
Thanks. I successfully updated boot.img and and recovery.img, but system won't load, so I might have imported from the wrong STOCK version.
I tried to reinstall a stock ROM using:
fastboot flash system system.img
But I got this error message:
target reported max download size of 471859200 bytes
sending sparse 'system' (444686 KB)...
OKAY [ 12.901s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 12.929s
Then I tried to erase the system file with "erase system" and got this error:
erasing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 0.013s
I guess that the only option now is to install the files on an external SD card?
Click to expand...
Click to collapse
I recommend you to download firmware files only from the official honor website or by using the huawei firmware finder(https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146)
In this case try to use huawei firmware finder to get the right stock version for your phone. Download these two files: e.g. update.zip & update_full_BLN-L21_hw_eu.zip.
Export the following image files: recovery, system, boot and cust.
The try to flash them:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cust cust.img
fastboot flash recovery recovery.img
If flashing a partition via fastboot fails then it is usually because it's the wrong image or just not made for your phone.
Thank you guys, you saved my phone! I eventually managed to flash the files from Nougat update for European Honor 6X BLN-L21C432B360 that I found there: stechguide.com/honor-6x-b360-nougat-update/
Now the phone is working fine.
Stinks said:
Thank you guys, you saved my phone! I eventually managed to flash the files from Nougat update for European Honor 6X BLN-L21C432B360 that I found there: stechguide.com/honor-6x-b360-nougat-update/
Now the phone is working fine.
Click to expand...
Click to collapse
Glad you revived your phone
question
Stinks said:
Hello! I tried to root my Honor 6x (BLN-L21, EMUI 5.0) following the instructions there:
cyberkey.in/how-to-root-honor-6x-100-working/
The bootloader was successfully unlocked.
But when I tried to flash TWRP the process failed and now my phone is stuck on boot :
"Your device has been unlocked and can't be trusted [...] Your device is booting now."
I can get access to recovery and fastboot. I wiped the cache and tried a factory reset but nothing changed, my system won't start and I don't know what to do.
Please help!
Click to expand...
Click to collapse
my phone is stuck at your device is booting now i cant get to any of other functions such as fastboot or recovry i can only acces it after full charge is gone and after charging.how did you get to acces fastboot or recover.
[email protected] said:
question
my phone is stuck at your device is booting now i cant get to any of other functions such as fastboot or recovry i can only acces it after full charge is gone and after charging.how did you get to acces fastboot or recover.
Click to expand...
Click to collapse
did you solve your issue.....I have same problem now
nokiasatyam said:
did you solve your issue.....I have same problem now
Click to expand...
Click to collapse
Hello, could you be more specific about your problem? I'll be able to help you.
Brief Explanation:
From the screen on which you're stuck, press and hold power button for about 10 seconds to forcibly restart your device. when you see the same screen again, immediately press and hold volume up button(for about 3 seconds) to boot to eRecovery.
> Choose shut down option on eRecovery. press and hold vol down button and insert the charging cable to boot to fastboot.
> Press and hold power and volume up button to boot to recovery. (You could do this even from fastboot screen and the screen you're stuck at).
I am currently running android 9.0 on htc dual sim model. i have unlocked my bootloader but whenever i tried to flash twrp or any other fastboot command after sending it says not allowed on production device.
target reported max download size of 536870912 bytes
sending 'recovery' (46340 KB)...
OKAY [ 1.320s]
writing 'recovery'...
FAILED (remote: Not allowed on PRODUCTION device)
finished. total time: 1.355s
i have tried both commands
fastboot flash recovery
htc_fastboot flash recovery (through different folder heaving related files)
Help me Solve that issue.
hassanulhaq said:
I am currently running android 9.0 on htc dual sim model. i have unlocked my bootloader but whenever i tried to flash twrp or any other fastboot command after sending it says not allowed on production device.
target reported max download size of 536870912 bytes
sending 'recovery' (46340 KB)...
OKAY [ 1.320s]
writing 'recovery'...
FAILED (remote: Not allowed on PRODUCTION device)
finished. total time: 1.355s
i have tried both commands
fastboot flash recovery
htc_fastboot flash recovery (through different folder heaving related files)
Help me Solve that issue.
Click to expand...
Click to collapse
I recently unlocked bootloader to flash Magisk so I could have root access. I was getting the same error and found out that you must do the flashing in "download mode", not in fastboot or bootloader mode.
---------- Post added at 01:32 AM ---------- Previous post was at 01:31 AM ----------
hassanulhaq said:
I am currently running android 9.0 on htc dual sim model. i have unlocked my bootloader but whenever i tried to flash twrp or any other fastboot command after sending it says not allowed on production device.
target reported max download size of 536870912 bytes
sending 'recovery' (46340 KB)...
OKAY [ 1.320s]
writing 'recovery'...
FAILED (remote: Not allowed on PRODUCTION device)
finished. total time: 1.355s
i have tried both commands
fastboot flash recovery
htc_fastboot flash recovery (through different folder heaving related files)
Help me Solve that issue.
Click to expand...
Click to collapse
I recently unlocked bootloader on my HTC U11 to flash Magisk so I could have root access. I was getting the same error and found out that you must do the flashing in "download mode", not in fastboot or bootloader mode.
Download mode
CiroConsentino said:
I recently unlocked bootloader to flash Magisk so I could have root access. I was getting the same error and found out that you must do the flashing in "download mode", not in fastboot or bootloader mode.
---------- Post added at 01:32 AM ---------- Previous post was at 01:31 AM ----------
I recently unlocked bootloader on my HTC U11 to flash Magisk so I could have root access. I was getting the same error and found out that you must do the flashing in "download mode", not in fastboot or bootloader mode.
Click to expand...
Click to collapse
How to do that in download mode?
hassanulhaq said:
How to do that in download mode?
Click to expand...
Click to collapse
hi, sorry for the late reply, my brother "borrowed" my phone for a couple weeks and he did a factory reset. I don't have my phone yet, hopefully I won't have to unlock the phone again or flash Magisk into the bootloader again either...
To unlock the bootloader, I followed this nice and detailed tutorial here:
https://www.getdroidtips.com/unlock-bootloader-htc-u11/
Click to expand...
Click to collapse
.
Then I followed Magisk's official tutorial on how to flash it without a custom recovery... here
https://savegyd.com/magisk-root-tutorial/
Click to expand...
Click to collapse
... just go to the "How to install Magisk with ADB and Fastboot (without custom recovery)" section and read it carefully, but instead of rebooting the phone into fastboot mode, I had to do it all in download mode.
I I did not install TWRP custom recovery, I manually patched the stock "boot.img" file with Magisk and then flashed the patched boot with this command with the ADB tool in Windows (phone in download mode):
fastboot flash boot patched_boot.img. I wanted to keep HTC's stock recovery.
Then I rebooted the phone into Android, and opened "Magisk" app in Android to make sure the root was working...
I didn't have internet connection in my phone (data connection or wifi), I did it all offline.
If you don't have the locked "boot.img" you must check the exact version of your installed Android OS and download the correct RUU file. Then you can extract the boot.img from it, patch it with Magisk, then flash it into the phone.
I did it in download mode as it was failing in fastboot mode. Make sure to enter download mode when you restart your phone, not fastboot mode. I'm not responsible if you brick your phone. My phone is the "Global" version from India (6GB RAM, 128GB internal storage).
issue resolved
CiroConsentino said:
hi, sorry for the late reply, my brother "borrowed" my phone for a couple weeks and he did a factory reset. I don't have my phone yet, hopefully I won't have to unlock the phone again or flash Magisk into the bootloader again either...
To unlock the bootloader, I followed this nice and detailed tutorial here: .
Then I followed Magisk's official tutorial on how to flash it without a custom recovery... here
... just go to the "How to install Magisk with ADB and Fastboot (without custom recovery)" section and read it carefully, but instead of rebooting the phone into fastboot mode, I had to do it all in download mode.
I I did not install TWRP custom recovery, I manually patched the stock "boot.img" file with Magisk and then flashed the patched boot with this command with the ADB tool in Windows (phone in download mode):
fastboot flash boot patched_boot.img. I wanted to keep HTC's stock recovery.
Then I rebooted the phone into Android, and opened "Magisk" app in Android to make sure the root was working...
I didn't have internet connection in my phone (data connection or wifi), I did it all offline.
If you don't have the locked "boot.img" you must check the exact version of your installed Android OS and download the correct RUU file. Then you can extract the boot.img from it, patch it with Magisk, then flash it into the phone.
I did it in download mode as it was failing in fastboot mode. Make sure to enter download mode when you restart your phone, not fastboot mode. I'm not responsible if you brick your phone. My phone is the "Global" version from India (6GB RAM, 128GB internal storage).
Click to expand...
Click to collapse
Issue was resolved. My phone's bootloader was unlocked and and top of all it got pie update on unlocked bootloader with rooted phone and updated to android pie, then it started creating random issues like phone booting time was around 10 to 15 mins and i was getting above mentioned error. whenever i was booting to download mode my system was not detecting my phone but in fastboot mode it was detecting (kind of strange issue)... which turns out to be a cable issue. Once i changed my cable my phone was detected in download mode. So i re-locked the bootloader and then again flashed the firmware everything came to normal. Phone is up and working fine and thanks for help again.
Hello,
I followed the steps on these two links:
https://forum.xda-developers.com/pixel-3a-xl/how-to/how-to-root-pixel-3a-3a-xl-twrp-t3928868
https://www.**********.com/unlock-pixel-3a-bootloader-and-root-pixel-3a-3a-xl/
To root my Pixel 3A. I unlocked it successfully, and then I did the final step of this command:
fastboot flash boot magisk_patched.img
But now my device is stuck on the bootloader screen. The bottom lines say:
Device state: unlocked
Boot slot: b
Enter reason: error boot prepare
I tried the options on the boot loader (rescue mode, recover mode, restart bootloader, powering off and restarting) but it only takes me back to the bootloader screen with same error.
From my MAC, I can still do the commands:
fastboot reboot (which does reboot the phone)
and
fastboot flash boot magisk_patched.img, which shows this:
Sending 'boot_b' (29136 KB) OKAY [ 0.760s]
Writing 'boot_b' OKAY [ 0.189s]
Finished. Total time: 1.219s
But not sure what else I can do to get out of the bootloader screen
Any help would be appreciated, as the phone is effectively bricked
DarthLuch said:
Hello,
I followed the steps on these two links:
https://forum.xda-developers.com/pixel-3a-xl/how-to/how-to-root-pixel-3a-3a-xl-twrp-t3928868
https://www.**********.com/unlock-pixel-3a-bootloader-and-root-pixel-3a-3a-xl/
To root my Pixel 3A. I unlocked it successfully, and then I did the final step of this command:
fastboot flash boot magisk_patched.img
But now my device is stuck on the bootloader screen. The bottom lines say:
Device state: unlocked
Boot slot: b
Enter reason: error boot prepare
I tried the options on the boot loader (rescue mode, recover mode, restart bootloader, powering off and restarting) but it only takes me back to the bootloader screen with same error.
From my MAC, I can still do the commands:
fastboot reboot (which does reboot the phone)
and
fastboot flash boot magisk_patched.img, which shows this:
Sending 'boot_b' (29136 KB) OKAY [ 0.760s]
Writing 'boot_b' OKAY [ 0.189s]
Finished. Total time: 1.219s
But not sure what else I can do to get out of the bootloader screen
Any help would be appreciated, as the phone is effectively bricked
Click to expand...
Click to collapse
Sounds like your magisk file is either the wrong version or corrupted. Download the full Google image, extract the boot.img from that and ash that image file using the fastboot flash boot boot.img command. Alternatively you could download the mvk kernel from here on xda and flash that. It's pre-rooted.
adm1jtg said:
Sounds like your magisk file is either the wrong version or corrupted. Download the full Google image, extract the boot.img from that and ash that image file using the fastboot flash boot boot.img command. Alternatively you could download the mvk kernel from here on xda and flash that. It's pre-rooted.
Click to expand...
Click to collapse
Thanks for that.. For whatever reason the MVK_Sargo_v10.22_magisk_patched.img version did not work, but the MVK_Sargo_v10.21_magisk_patched.img one did!
DarthLuch said:
Thanks for that.. For whatever reason the MVK_Sargo_v10.22_magisk_patched.img version did not work, but the MVK_Sargo_v10.21_magisk_patched.img one did!
Click to expand...
Click to collapse
If 21 worked but 22 didn't... Going from my faltering memory that means your not on March security, your on feb or earlier. 22 only worked on March, i am running it myself.
I got stuck here, too... I used the flash tool (flash.android.com) and it put me back to stock after about a 20 minute progress bar crawl
I have the same problem can someone help me?
YYa solucionaste ?