Related
When I'm trying to turn on my Nexus 5 i get an error (in the title) and phone starts to reboot! Many people say : "clear app data", but how do i clear cache when i can't run the phone. It happened when my Nexus started to update system by itself without my touches to 4.4.3. I tried to do Wipe, but it doesn't make sense on phone's system and my TWRP asking for password (http://forum.xda-developers.com/google-nexus-5/help/twrp-password-t2511049) this helps to wipe, but doesn't solve problem with "Unfortunely bla-bla......" and inf.rebooting.
Phone's Description:
Android 4.4.2 before phone started to update by itself
Rooted
TWRP - custom recovery
Just flash 4.4.4 stock with fastboot. You'll be on the latest and issue should be gone.
KJ said:
Just flash 4.4.4 stock with fastboot. You'll be on the latest and issue should be gone.
Click to expand...
Click to collapse
now i have bootlop and message box with "Android is updating....Start apps" and reboot again and again. What should i do?
cwclasses said:
now i have bootlop and message box with "Android is updating....Start apps" and reboot again and again. What should i do?
Click to expand...
Click to collapse
tried to reflash img instead existing.
Output:
Userdata - Failed
Boot - OK
System - Failed
Recovery - Failed
Maybe i have to use adb commands and push something into the phone's memory, something like new ROM, Recovery or something else?
This is a guide for flashing stock.....has all the info you need. Make sure to follow it step by step.
http://forum.xda-developers.com/showthread.php?t=2513701
KJ said:
This is a guide for flashing stock.....has all the info you need. Make sure to follow it step by step.
http://forum.xda-developers.com/showthread.php?t=2513701
Click to expand...
Click to collapse
it doesn't work, OMG my new nexus5......seems to be completely soft brocken:crying:
cwclasses said:
it doesn't work, OMG my new nexus5......seems to be completely soft brocken:crying:
Click to expand...
Click to collapse
Which part doesn't work?
by the issues , your emmc is bad, replace it
PsychDrummer said:
Which part doesn't work?
Click to expand...
Click to collapse
When i try to flash it messages me:
sending 'system' (209158 KB)...
OKAY [ 27.414s]
writing 'system'...
FAILED (remote: image update error)
finished. total time: 51.147s
Hi,
I've posted on this topic on transformerforums website but have not had any success (despite valiant attempts from the guys on the forums).
I am unable to post the link here, please PM me for a link to my original post.
Basically my TF700T got stuck in a bootloop. I have unlocked the bootloader but have not flashed it so it's on stock ROM. I have not been able to flash a recovery ROM and am at a dead end as to what to do.
I am able to get to bootloader and I when I run
Code:
fastboot devices
I get the following output
Code:
015d2a506733f618 fastboot
Which all seems correct. I have access to the tablet when connected to my pc.
When I try to flash the recovery rom, it takes a very short amount of time and on my tablet the device hangs (i.e the RCK icon is no longer flashing). I have checked the blob, it is the correct one and the MD5 hash is correct.
Code:
C:\androidsdk\platform-tools>fastboot -i 0x0B05 flash recovery twrp-2.7.1.1-tf700t.blob
sending 'recovery' (6894 KB)...
OKAY [ 0.868s]
writing 'recovery'...
OKAY [ 0.089s]
finished. total time: 0.958s
I can get back into the bootloader if I restart again but attempting to flash it results in a hang.
I have tried to insert an sd with the stock ROM and boot in RCK mode but this has not worked either.
Has anyone any suggestions as to what to do?
The tablet is 2 years old now so not under warranty.
thanks in advance.
anyone have any suggestions?
I'm going on holidays on Thursday and would really love to get this resolved before I go.
deleted
Shameless bump .... are my only options to return this to the manufacturer?
Anyone any suggestions, do you need more info from me?
What you did looks correct, only the short time for "writing" looks suspicious. Try the fastboot command again, but replace "recovery" with "staging", maybe that works better. At the next reboot you should see a blue progress bar on the boot screen for a few seconds and it should reboot again.
Hi,
Thanks for the reply.
I tried as you suggested and looks like the same results. I'm doing this in windows 7 and have opened the command prompt as Administrator.
Code:
C:\adb>fastboot -i 0x0B05 flash staging twrp-2.7.1.1-tf700t.blob
sending 'staging' (6894 KB)...
OKAY [ 0.869s]
writing 'staging'...
OKAY [ 0.084s]
finished. total time: 0.955s
Is there any way I get get logs from the tablet itself?
I had been thinking was this a permissions thing although I am able to run
Code:
fastboot boot
Code:
fastboot boot-bootloader
and they work correctly. So I do have access but for some reason the partition is not getting flashed correctly.
Does anyone know what the partitions are used for?
I assume the system partition is used for the actual system image but what is the staging partition used for?
knoxor said:
I had been thinking was this a permissions thing although I am able to run
Code:
fastboot boot
Code:
fastboot boot-bootloader
and they work correctly. So I do have access but for some reason the partition is not getting flashed correctly.
Does anyone know what the partitions are used for?
I assume the system partition is used for the actual system image but what is the staging partition used for?
Click to expand...
Click to collapse
When blobs are written to the staging partition, on next boot. the bootloader flashes the contents to the relevant partitions (i.e., kernel, system, bootloader)
knoxor said:
Hi,
Thanks for the reply.
I tried as you suggested and looks like the same results. I'm doing this in windows 7 and have opened the command prompt as Administrator.
Code:
C:\adb>fastboot -i 0x0B05 flash staging twrp-2.7.1.1-tf700t.blob
sending 'staging' (6894 KB)...
OKAY [ 0.869s]
writing 'staging'...
OKAY [ 0.084s]
finished. total time: 0.955s
Is there any way I get get logs from the tablet itself?
Click to expand...
Click to collapse
Hi sbdags,
So it looks like I'm stuck at this point. The above command seems to work but the time for flashing the recovery blob to staging seems very short which probably indicates that this has not happened correctly. After the above command, on next boot when selecting RCK from the bootloader menu the tablet attempts to perform the update but then I get the android error screen (android dude on his back and error message).
Any suggestions as to what I can do next?
thanks
Paul
knoxor said:
Hi sbdags,
So it looks like I'm stuck at this point. The above command seems to work but the time for flashing the recovery blob to staging seems very short which probably indicates that this has not happened correctly. After the above command, on next boot when selecting RCK from the bootloader menu the tablet attempts to perform the update but then I get the android error screen (android dude on his back and error message).
Any suggestions as to what I can do next?
thanks
Paul
Click to expand...
Click to collapse
Well shoot me a PM, Lets see if we can find a solution to your issue ...
Thx Josh
bump again.
Is there anyone there who can help me on this please ?
knoxor said:
Is there anyone there who can help me on this please ?
Click to expand...
Click to collapse
I don't think I can help you, but can you post the build number of your bootloader? I remember someone had a bootloader for the TF300 on his TF700 and was then unable to flash blobs.
_that said:
I don't think I can help you, but can you post the build number of your bootloader? I remember someone had a bootloader for the TF300 on his TF700 and was then unable to flash blobs.
Click to expand...
Click to collapse
Hi, I fairly sure I have the correct bootloader (WW_epad-10.6.1.14.10-20130801 A03).
Just to clarify, this is a stock rom I have on the tab. I have it unlocked but not rooted.
thanks
knoxor said:
Hi, I fairly sure I have the correct bootloader (WW_epad-10.6.1.14.10-20130801 A03).
Just to clarify, this is a stock rom I have on the tab. I have it unlocked but not rooted.
thanks
Click to expand...
Click to collapse
Your bootloader is ok.
Did you PM Josh? What did you guys try?
If he couldn't help you, I doubt I can...
Aside from the suggestions I gave you on the Transformer Forum, I'm stumped...
So again:
Do not use USB 3.0 ports
Uninstall the fastboot drivers and use the one from here: http://forum.xda-developers.com/showthread.php?t=2646279
Check the fastboot.exe version and see if you can find a later one.
That's all I can think of right now....
berndblb said:
Your bootloader is ok.
Did you PM Josh? What did you guys try?
If he couldn't help you, I doubt I can...
Aside from the suggestions I gave you on the Transformer Forum, I'm stumped...
So again:
Do not use USB 3.0 ports
Uninstall the fastboot drivers and use the one from here: http://forum.xda-developers.com/showthread.php?t=2646279
Check the fastboot.exe version and see if you can find a later one.
That's all I can think of right now....
Click to expand...
Click to collapse
Yes I contacted Josh and shared my desktop with him one evening. We didn't resolve it. I've tried the flashing on 3 different computers.
One of them is an old laptop running ubuntu that I know only has USB2 ports on it.
The only thing I can think of is that I lost my original charger/cable but I spent the extra money to get an OEM one again so I hope that is not
the issue.
Could the cable be the issue??
knoxor said:
Yes I contacted Josh and shared my desktop with him one evening. We didn't resolve it. I've tried the flashing on 3 different computers.
One of them is an old laptop running ubuntu that I know only has USB2 ports on it.
The only thing I can think of is that I lost my original charger/cable but I spent the extra money to get an OEM one again so I hope that is not
the issue.
Could the cable be the issue??
Click to expand...
Click to collapse
If you got the charger from anywhere else but Asus - yes, that could be the issue. And the only one left I can think of....
Hi all, first post here.
I have a bricked XT925 which I'm trying to recover.
It will go into fastboot and I can access it with ADB/Fastboot/mFastbootv2/RazorHDToolkit5.0/RSD lite etc, but none of these will write a new recovery to flash.
I was able to unlock the bootloader using the Motorola website and the phone will talk to the PC software, but it's as though the internal flash memory is trashed.
In fact lots of commands to the flash result in a "fastboot max download size 30mb" error.
Can anyone help?
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-2.8.6.0-xt925.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (9154 KB)...
OKAY [ 0.730s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.871s
Click to expand...
Click to collapse
I would start with obtaining a clean working flash of the official ROM, before trying to flash anything custom.
Just a guess, but if you went to the unlock website after the phone was soft-bricked, the bootloader may still be locked. I assume that the phone needs a full working OS to receive and implement the unlock signal from Motorola. Since it hasn't booted the OS since it was bricked, it hasn't had a chance to do so.
I would start with obtaining a clean working flash of the official ROM, before trying to flash anything custom.
Click to expand...
Click to collapse
Would that I could. All the links I've found so far are dead.
I have another XT925 in working order, anyone know how to extract the image from it?
Just a guess, but if you went to the unlock website after the phone was soft-bricked, the bootloader may still be locked. I assume that the phone needs a full working OS to receive and implement the unlock signal from Motorola. Since it hasn't booted the OS since it was bricked, it hasn't had a chance to do so.
Click to expand...
Click to collapse
I think the Bootloader error messages are to be expected, everything I've since read suggests I should ignore them.
ddichiera said:
Would that I could. All the links I've found so far are dead.
I have another XT925 in working order, anyone know how to extract the image from it?
I think the Bootloader error messages are to be expected, everything I've since read suggests I should ignore them.
Click to expand...
Click to collapse
I have one of the old Canadian leaked KK stock sbf (I was using it to see if I could bring anything to my AHD). I can post it to my GDrive and post the link this afternoon.
palmbeach05 said:
I have one of the old Canadian leaked KK stock sbf (I was using it to see if I could bring anything to my AHD). I can post it to my GDrive and post the link this afternoon.
Click to expand...
Click to collapse
Any image would be welcome, GDrive is fine.
ddichiera said:
Any image would be welcome, GDrive is fine.
Click to expand...
Click to collapse
https://drive.google.com/open?id=0B52pkPIFU2dRWFRXOU9UQlhHZ3c
Thanks for that, unfortunately my situation has become worse.
Whilst the phone was connected and in fastboot mode, I deleted the ADB driver in Device Manager and now the PC, or more specifically ADB and Fastboot wont talk to the phone. Grrrrr.
Oh, and the other handset has decided to die as well.
One thing at a time. Anyone know how to restore the driver/get-the-phone-talking-to-ADB/Fastboot again?
I have OPO 64GB and unlocked via fastboot. Every fastboot command related to flash or erase or format gave same error, unable to erase or write the partition.
I was able to fastboot boot <custom_recovery.img> into TWRP 2.7 I believe but TWRP gives errors, unable to mount <partition>, etc. Any command in TWRP results into a failure to mount or write.
I tried ADB Sideload <zip> and at 12% it rebooted back into Cyanogen Mod ready logo.
TWRP only runs if I boot to it via fastboot, it can't write to the bootloader via fastboot. One strange thing under TWRP storage it shows Internal Storage 0MB and USB-OTG 0MB, the partitions also show 0MB excep for system, but can't format anything or resize.
I feels like there is no storage in this device, is this something that can be fixed or is this a DOA device? It was working fine and a Cyanogen update ran and bricked it!
When I try to fastboot flash I get this error, fail to write. I even tried the OnePlusRestoreTool and it fails to write to the phone.
fastboot flash recovery twrp3.img
target reported max download size of 1073741824 bytes
sending 'recovery' (13326 KB)...
OKAY [ 0.422s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 5.479s
Thoughts?
Thank You
It seems that your partitions are corrupt.
I had the same issue and solved it by restoreing completley to stock Rom. There must be a thread for this anywhere out, if not download a fastboot image from cyanogen support site extract it and try to flash it.
That is what I was leaning towards, but in every solution to restore the stock ROM I have to use fastboot and fastboot just fails to write anything. I can't even get TWRP to stick, fails to write every time. I tried the OnePlusRestoreTool but the driver installs ok but the tool can't find the phone, tried 2 different PCs. I was hoping for another solution other than fastboot or the OnePlusRestoreTool, I searched but could not find another method, I was hoping someone could point me in the right direction.
Thanks
newpop1_android said:
I have OPO 64GB and unlocked via fastboot. Every fastboot command related to flash or erase or format gave same error, unable to erase or write the partition.
I was able to fastboot boot <custom_recovery.img> into TWRP 2.7 I believe but TWRP gives errors, unable to mount <partition>, etc. Any command in TWRP results into a failure to mount or write.
I tried ADB Sideload <zip> and at 12% it rebooted back into Cyanogen Mod ready logo.
TWRP only runs if I boot to it via fastboot, it can't write to the bootloader via fastboot. One strange thing under TWRP storage it shows Internal Storage 0MB and USB-OTG 0MB, the partitions also show 0MB excep for system, but can't format anything or resize.
I feels like there is no storage in this device, is this something that can be fixed or is this a DOA device? It was working fine and a Cyanogen update ran and bricked it!
When I try to fastboot flash I get this error, fail to write. I even tried the OnePlusRestoreTool and it fails to write to the phone.
fastboot flash recovery twrp3.img
target reported max download size of 1073741824 bytes
sending 'recovery' (13326 KB)...
OKAY [ 0.422s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 5.479s
Thoughts?
Thank You
Click to expand...
Click to collapse
Try this
geowolf1000 said:
Try this
Click to expand...
Click to collapse
So I tried the link but also their method uses FastBoot and FastBoot fails to write to the OPO every time no matter what, see below. I can put TWRP in memory but can't write to the SD I guess. Any tool that can reformat the storage and put it back together since FastBoot and ADB can't write to it?
Thx
target reported max download size of 1073741824 bytes
sending 'persist' (4244 KB)...
OKAY [ 0.137s]
writing 'persist'...
FAILED (remote: flash write failure)
finished. total time: 5.208s
Has a second method from terminal
Run command from twrp rerminal
Στάλθηκε από το A0001 μου χρησιμοποιώντας Tapatalk
Try this http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 , it will rewrite all the partition and then change the rom and recovery you want, it should work
Chinaroad said:
Try this http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 , it will rewrite all the partition and then change the rom and recovery you want, it should work
Click to expand...
Click to collapse
He tried that one, but as the PC doesn't detect his phone that ain't gonna work...
@newpop1_android could you sent me a PM, I'll try to resolve your issue in a teamviewer session.
Chinaroad said:
Try this http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 , it will rewrite all the partition and then change the rom and recovery you want, it should work
Click to expand...
Click to collapse
Hello, so I managed to get an older PC to do all this in as well and tried another PC anyway. I ran the color.zip install, drivers installed OK and phone is detected, I ran the Msm8974DownloadTool.exe and it found the phone in COM3, I see a progress bar in one file, the image file and then it reboots the phone but it comes back to the Cyanogen splash screen and it does not go anywhere, so I reboot it again manually power+VUp and the tool finds it again and tries to send the *same* file again, and then I tried this loop at least 10 times.
I conclude that it is unable to write the image to the cell, same symptom I encountered with Fastboot flash boot img. Does this mean that the cell is bricked since nothing can write to the SD?
Do the progressbars you see in Msm8974DownloadTool.exe become green?
Maybe see there:
http://www.technobuzz.net/guide-to-recover-from-hard-bricked-oneplus-one/
It is nearly the same like the one posted before, but has some screenshots.
After doing this color OS should boot up, not cyanogen os.
If only one image file is "flashed", check if your color.zip is downloaded correctly
Hope this helps
Flo9818 said:
Do the progressbars you see in Msm8974DownloadTool.exe become green?
Maybe see there:
http://www.technobuzz.net/guide-to-recover-from-hard-bricked-oneplus-one/
It is nearly the same like the one posted before, but has some screenshots.
After doing this color OS should boot up, not cyanogen os.
Hope this helps
Click to expand...
Click to collapse
Hello, not really, it does one file and then I see progress bar move on the first file, progress bar finished and then the phone boots to the cyanogen screen again, then i tried again, it still shows the same file again. It does not save the file, fails to write pretty much, same thing as fastboot.
There should be serveral progressbars. One for each image in color.zip. Try to reinstall the qualcomm 2012 drivers.
Have you restarted your PC?
Flo9818 said:
There should be serveral progressbars. One for each image in color.zip. Try to reinstall the qualcomm 2012 drivers.
Click to expand...
Click to collapse
I actually did that and tried one plus one as well, I also tried the other unbrick toll as well with other drivers. The phone is recognized no problem, but nothing can write to it, just like fastbook flash , write denied every time.
Restarted your PC after qualcomm driver install?
Maybe there be driver problems related to win10.
Also check
fastboot oem device-info if your bootloader is really unlocked
Flo9818 said:
Restarted your PC after qualcomm driver install?
Maybe there be driver problems related to win10.
Also check
fastboot oem device-info if your bootloader is really unlocked
Click to expand...
Click to collapse
It won't work, his device is not recognized by adb or fastboot.
My device is in the same state, I rebooted it and it hard bricked, I tried using the ColorOS flash tool but, when I start it, it is stuck in a loop trying to flash "8974_msimage.mbn", any solution would be appreciated, because I hard bricked it in the first day after receiving my OPO (I bought an used one).
I already tried on two different computers, the same issue happens, I also tried to find a fix, but everyone that had this issue never replied, so I think this state is really THE hard brick, with no ways to go back to the original state.
@newpop1_android did you find a solution for your problem?
MrPowerGamerBR said:
It won't work, his device is not recognized by adb or fastboot.
My device is in the same state, I rebooted it and it hard bricked, I tried using the ColorOS flash tool but, when I start it, it is stuck in a loop trying to flash "8974_msimage.mbn", any solution would be appreciated, because I hard bricked it in the first day after receiving my OPO (I bought an used one).
I already tried on two different computers, the same issue happens, I also tried to find a fix, but everyone that had this issue never replied, so I think this state is really THE hard brick, with no ways to go back to the original state.
@newpop1_android did you find a solution for your problem?
Click to expand...
Click to collapse
Did you run the programm as administrator?
Someone in the oneplus forum had the same problem with loop flashing the 8974_msiimage.mbn and solved it with
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Maybe a try?
Flo9818 said:
Did you run the programm as administrator?
Someone in the oneplus forum had the same problem with loop flashing the 8974_msiimage.mbn and solved it with
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Maybe a try?
Click to expand...
Click to collapse
Yes, I did.
I also tried that tool before, same issue.
Flo9818 said:
Did you run the programm as administrator?
Someone in the oneplus forum had the same problem with loop flashing the 8974_msiimage.mbn and solved it with
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Maybe a try?
Click to expand...
Click to collapse
The problem is that the device gets disconnected when flashing for some reason. I tried two different drivers, both didn't work.
I'm willing to pay 5$ to someone who can fix this issue for me.
MrPowerGamerBR said:
The problem is that the device gets disconnected when flashing for some reason. I tried two different drivers, both didn't work.
I'm willing to pay 5$ to someone who can fix this issue for me.
Click to expand...
Click to collapse
Which Windows Version do you use? I would try with win7. With win 8.1 and 10 you have to disable driver verification.
Have you disabled your antivirus?
Have you disabled UAC?
Maybe another USB cable?
If all this does not work see here:
https://forums.oneplus.net/threads/solution-bricked-oneplus-one-recovery.306306/
Flo9818 said:
Did you run the programm as administrator?
Someone in the oneplus forum had the same problem with loop flashing the 8974_msiimage.mbn and solved it with
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Maybe a try?
Click to expand...
Click to collapse
Flo9818 said:
Which Windows Version do you use? I would try with win7. With win 8.1 and 10 you have to disable driver verification.
Have you disabled your antivirus?
Have you disabled UAC?
Maybe another USB cable?
If all this does not work see here:
https://forums.oneplus.net/threads/solution-bricked-oneplus-one-recovery.306306/
Click to expand...
Click to collapse
Windows 7, but Windows 7 also needs to disable driver verification.
I don't use any antivirus.
No, but I ran the tool as administrator.
I already tried that, I tried with the original cable that came with the device and my Moto G 2014 cable, same issue on both.
It isn't a missing driver issue tho, Qualcomm drivers are installed and working because the ColorOS flash tool detects the device.
Anyway, thanks for helping
Hello,
My honor 8 is hard bricked, yesterday I wished to install custom Rom and it was encrypted so I decided to return to EMUI, I installed stock recovery I installed rollback package to emui 4.1 and emui 4.1 now i'm stuck on boot screen. I already do a format data and wipe cache but nothing.
Please help me.
EDIT : I can go to ADB but I have this message when I try to flash anything... "FAILED (remote: Command not allowed)" FRP is locked
Please help me I'm so bored about this problem
There are some guides on how to unbrick phone with FRP locked... You could try to watch on them.
That's mine guide
ScardracS said:
There are some guides on how to unbrick phone with FRP locked... You could try to watch on them.
That's mine guide
Click to expand...
Click to collapse
The problem is when i use ADB command it wrongs me
"target reported max download size of 471859200 bytes
sending 'recovery' (36996 KB)...
OKAY [ 0.894s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.903s"
If you can't find any solution with ADB, as a last resort you could use DC Phoenix to fix it. But it costs 15 Euros to use it. That's what I had to do fix the same problem you have.
BnK1986 said:
The problem is when i use ADB command it wrongs me
"target reported max download size of 471859200 bytes
sending 'recovery' (36996 KB)...
OKAY [ 0.894s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.903s"
Click to expand...
Click to collapse
Go with dload method. Try downloading the full firmware for your model and use the 3 combination to flash. There is quick guide in my signature if you are not aware of the exact method for dload.
shashank1320 said:
Go with dload method. Try downloading the full firmware for your model and use the 3 combination to flash. There is quick guide in my signature if you are not aware of the exact method for dload.
Click to expand...
Click to collapse
I can't do dload method it shows me boot screen.
BnK1986 said:
I can't do dload method it shows me boot screen.
Click to expand...
Click to collapse
You may not be doing it right. Assuming.
Keep trying couple of times, remember to press power up+powet down 1st and then power key and keep pressing all together
shashank1320 said:
You may not be doing it right. Assuming.
Keep trying couple of times, remember to press power up+powet down 1st and then power key and keep pressing all together
Click to expand...
Click to collapse
Yes I know i was doing this before and it worked but now it's not possible I will try several times like 5-10 times in a row
BnK1986 said:
Yes I know i was doing this before and it worked but now it's not possible I will try several times like 5-10 times in a row
Click to expand...
Click to collapse
are you able to get into fastboot or recovery?
shashank1320 said:
are you able to get into fastboot or recovery?
Click to expand...
Click to collapse
No I hold the 3 buttons it shows me boot screen, black screen for 1 second and again boot screen
shashank1320 said:
are you able to get into fastboot or recovery?
Click to expand...
Click to collapse
Any solutions?
BnK1986 said:
Any solutions?
Click to expand...
Click to collapse
You can enter in fastboot, by pressing volume down when the phone is powering on and holding the button, immediately insert the usb cable (already plugged in the pc) and you will enter in fastboot.
Video
Sent from my FRD-L09 using XDA Labs
grilla99 said:
You can enter in fastboot, by pressing volume down when the phone is powering on and holding the button, immediately insert the usb cable (already plugged in the pc) and you will enter in fastboot.
Video
Sent from my FRD-L09 using XDA Labs
Click to expand...
Click to collapse
I can do this but ADB commands not working
BnK1986 said:
I can do this but ADB commands not working
Click to expand...
Click to collapse
When you enter in this shell, you are not allowed to use ADB commands, but only fastboot commands, previously you typed adb devices, now you can't. But if you type fastboot device it will shown you your id number plus device, just try if what i sad is true
Sent from my FRD-L09 using XDA Labs
tnks !!!! friend save _me !!!!!
hey i have the same problem
what did you exactly do in fastboot mode? no commands works on my phone