Problem with oopof1 phone - Oppo F1

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.

Related

[Q] is my desire s dead ?

i just wanted reset my phone
the in Phone Button "Reset ..." hasnt work
so i did it at the recovery boot
but after that, the phone dont wona start
it hangs after " HTC..."
after:
Code:
adb reload boatloader
it said:
NO Device coudnt be found
is my phone dead ?
Boot into recovery and flash a new rom?
What did you chose in the recovery?
My first guess is that you wiped your system partition. (That WOULD mean you don't have a ROM installed) Try flashing a new one.
Power down your phone
Press the volume down and the power button together until you are in the bootloader
Choose recovery (use the volume buttons to navigate and the power button to confirm)
Now flash a new ROM or restore a backup. Don't forget to flash the boot.img, if you are HTC Dev unlocked.
does yor recovery show errors like "E:Cant mount cache" ?
Thanks !
I realy wiped the phone, and there was no rom
c:\Android>fastboot flash boot boot.img
sending 'boot' (5624 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.016s
Click to expand...
Click to collapse
???

[q] cant enable usb debugging

My Nexus 5 will not boot it gets stuck on the 4 circles spinning loading screen, when i go into recovery mode it says E: failed to mount /cache (Invalid Argument), i have tried wipe data/factory reset but it still does the same thing, now i want to flash it to a factory image but USB debugging isn't enabled and i cant turn on the phone to enable it, is there any other way to enable it? I'm new to this so i don't know much about it, any help would be great, thanks.
First try to wipe cache. This may take up to 15 minutes.
If it doesn't work: You don't need USB debugging enabled to flash a factory image.
experience7 said:
First try to wipe cache. This may take up to 15 minutes.
If it doesn't work: You don't need USB debugging enabled to flash a factory image.
Click to expand...
Click to collapse
I have tried wiping cache, still does the same thing, and the tutorial i was on to unlock the boot loader said i needed USB debugging enabled.
You don't need USB debugging on to flash factory image .
Sent from my Nexus 5 using Tapatalk
You are getting mixed up. Adb is for when android is up and running. If it's crashed you boot to the bootloader and use fastboot
fastboot flash boot boot.img
fastboot flash system system.img
Ben36 said:
You are getting mixed up. Adb is for when android is up and running. If it's crashed you boot to the bootloader and use fastboot
fastboot flash boot boot.img
fastboot flash system system.img
Click to expand...
Click to collapse
when i try to fastboot flash boot boot.img it says
target reported max download size of 1073741824 bytes
sending 'boot' (8852 KB)...
OKAY [ 0.153s]
writing 'boot'...
FAILED < remote: not supported in locked device>
finished. total time: 0.619s
and nothing happens on the phone, am i doing something wrong ? i am new to doing this so any help would be appreciated, thanks.
Chris2073 said:
when i try to fastboot flash boot boot.img it says
target reported max download size of 1073741824 bytes
sending 'boot' (8852 KB)...
OKAY [ 0.153s]
writing 'boot'...
FAILED < remote: not supported in locked device>
finished. total time: 0.619s
and nothing happens on the phone, am i doing something wrong ? i am new to doing this so any help would be appreciated, thanks.
Click to expand...
Click to collapse
First, unlock your bootloader.
fastboot oem unlock
Then you use the fastboot flash commands.
By the way where is this guide which tells you need usb debuging enabled to unlock bootloader? I see this nonsense everytime.
Sent from my Nexus 5 using XDA Free mobile app
bitdomo said:
First, unlock your bootloader.
fastboot oem unlock
Then you use the fastboot flash commands.
By the way where is this guide which tells you need usb debuging enabled to unlock bootloader? I see this nonsense everytime.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I tried that, now when i try to flash system i get
FAILED (remote: flash write failure)is there anything i can do about this? or is it the end of my Nexus 5? Thanks for all your help.
Chris2073 said:
I tried that, now when i try to flash system i get
FAILED (remote: flash write failure)is there anything i can do about this? or is it the end of my Nexus 5? Thanks for all your help.
Click to expand...
Click to collapse
I am sorry to tell you but flash chip of the device is gone bad. You have to buy a new motherboard

OTA caused a boot loop?

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.

Root: Stuck at "Your device is booting now"

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).

Help, going back to stock EMUI 5 and bricked

Guys, I wanted to go back to EMUI 5 stock (BLN-L24C567B366) but I got stock flashing the BOOT, RECOVERY, and SYSTEM images, fastboot shows
Code:
PS C:\adb> fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (15508 KB)...
OKAY [ 0.594s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.620s
I looked up for that and seems because the PC is not communicating with fastboot maybe due to drivers or disabled USB Debugging, what can I do to recover my phone? My bootloader is still unlocked and shows
Code:
PHONE Unlocked
FRP Lock
I still have access to TWRP if that helps... Help please :crying:
Jessooca said:
Seeing as you have twrp still working, why not reflash any of the other custom roms so you have a working phone again? I'm assuming you still have whichever rom you been using, on your phone again? If not, put one on an SD card then put the sd card into the phone, reboot twrp back into recovery so it can find the rom on the sd card and flash that rom.
Click to expand...
Click to collapse
Thank you very much, I will download a ROM now bcz I just had root.
Jessooca said:
Then instead of going back to stock via cmd and fastboot just copy over the update file in the dload folder and do the 3 button restart so it can detect the update file and restore your phone.
Click to expand...
Click to collapse
With this you mean getting all the files out of update.zip(Full-OTA) and putting them in dload folder in the sdcard right? I tried that(just without any system installed ) and it failed at 5%, is there a difference?
Again, thanks a lot for your help

Categories

Resources