Hi!
I wanted to flash cloudyfa today, so first I wiped everything and flashed the KK bootloader using this:
http://forum.xda-developers.com/lg-g2/general/d802-bootloader-changer-1-1-jb-kk-lp-t3104380
Then after reboot I see only "Fastboot mode started". On PC after "fastboot devices" I don't see letters and numbers as usualy, only "?" symbol there. Commands like "fastboot reboot" and "fastboot flash recovery recovery.img" works flawlessly, but even after this and reboot, nothing happens. Download mode is working, but isn't there any easly way to flash twrp than doing whole operation with going back to stock via download mode? :crying:
EDIT: "One click" won't work - it doesn't see device.
EDIT2: Nevermind. Done it with KDZ files... ^^.
Related
Hello everyone!
Okay, so I'll try to keep it as short as possible but with the most information I can give ofc.
So here's what I did with my Oneplus 2:
- unlocked bootloader
- flashed custom recovery (twrp)
- flashed superSU.zip
- flashed xposed.zip
- used it for about half a year if not even longer
everything on Lollipop 5.1 stock rom so xposed would work.
Everything was fine but some day when I wanted to enter twrp recovery it didn't work. (I swear, this is the most illogical thing ever but I DID NOT CHANGE A THING!)
I tried to enter recovery via fastboot but that didn't work either.
So I reflashed latest TWRP recovery.img for OP2 via fastboot.
When I pressed power + vol. down to see if it'd work nothing happened.
When I tried to enter recovery when my system was booted via power button->restart->recovery my phone got stuck in a bootloop.
I had to go in fastboot mode to enter "fastboot continue" in order to get my phone booting normal again.
Then, one night when my phone was in my pocket it vibrated and got stuck in the bootloop again, even though it was booted into system and locked last time I used it (minutes before that).
I had no access to a computer at that moment so I had to wait for a few days.
Now when I boot my phone in fastboot mode and try to enter "fastboot continue" on my cmd nothing happens with my phone and cmd says "(command write failed (Unknown error))" even though "fastboot devices" shows that my device is connected properly.
I also tried:
- the FirstAidKit, copied the Win Files in my fastboot directory and started the firstaid.bat but it stops on "fastboot flash boot boot.img" (I waited for like two hours).
- a different USB port (USB 3 and USB 2)
I am kinda depending on my phone so yeah..
If someone knows how to fix this I would be very grateful.
Have a good day/night
SoulSnatcher
Do you have a backup??
If yes, download the latest official OS from Oneplus and the stock recovery. Flash the stock recovery. Try rebooting into stock recovery. If it succeeds, wipe everything and flash OS via adb sideload.
Honestly, I can't guess what went wrong with your device. Maybe it could've been some app which crashed the entire system.
AJay27 said:
Flash the stock recovery.
Click to expand...
Click to collapse
Same problem as with the FirstAidKit:
"fastboot devices" does display the device but "fastboot flash recovery recovery.img" doesn't do anything (I waited for 1h just to make sure).
I'll try this Mega Unbrick Guide for A Hard Bricked OnePlus 2 next, even though I can get into fastboot but since it doesn't do s**t I'll have to give it a try. I mean, what's the worst thing that could happen? That my phone gets bricked?!
Haha.... hmm.
I'll keep the person(s) updated who care to know what's happening.
Cheers
fml
I had previously flashed twrp recovery onto my phone via adb. And also flashed a few ROMs.
I recently flashed a stock KitKat ROM and everything is working fine. Except I can't boot into twrp recovery.
I have enabled USB debugging and as MTP.
The phone is being detected on my PC and I can transfer files between the two.
Typing 'adb devices' also shows that my phone is authorized.
I ran command 'adb reboot bootloader' and it works.
'Fastboot devices' also shows my device.
I tried 'fastboot OEM device-info' & also 'fastboot OEM unlock' after running 'adb reboot bootloader'.
I can also flash recovery on my android and it displays an 'okay' message.
However, the phone boots in stock recovery.
I tried flashing various twrp images ranging from KitKat to Marshmallow, from various sites.
None work.
I also booted into twrp manually but that does not work either.
If somebody has a KitKat twrp image will you please share it with me?
Also I do not want to update my phone because I had previously flashed twrp on stock kitkat and it worked then.
Command 'fastboot flash recovery recovery.img' works but 'fastboot boot recovery recovery.img' doesn't.
The command is 'fastboot boot recovery.img'. Also, if that doesn't work, try flashing CWM recovery.
Thank You.
Command "fastboot boot recovery.img' worked. :victory:
I don't understand why flashing recovery didn't work though.
Nevertheless, Thanks a lot!
Hello guys
I have a problem, yesterday I was putting the twrp to my one plus 6t via fastboot and as soon as I entered the bootloader I put the command "fastboot boot twrp.img" and it said "fastboot unknow command".
So I searched on google for the commands to start the twrp via the PC terminal and I found this command "fastboot flash recovery twrp.img".
Everything ok, it restarts the screen, 3 minutes then it is turned off and remains in the initial screen where it says that the bootloader is unlocked, it does not go in fastboot mode not in recovery
Tips?
Use the Msm tool to recover if your phone is bricked.
https://forum.xda-developers.com/on...-msmdownloadtool-v4-0-oos-9-0-5-t3867448/amp/
FrancescoPtr said:
Hello guys
I have a problem, yesterday I was putting the twrp to my one plus 6t via fastboot and as soon as I entered the bootloader I put the command "fastboot boot twrp.img" and it said "fastboot unknow command".
So I searched on google for the commands to start the twrp via the PC terminal and I found this command "fastboot flash recovery twrp.img".
Everything ok, it restarts the screen, 3 minutes then it is turned off and remains in the initial screen where it says that the bootloader is unlocked, it does not go in fastboot mode not in recovery
Tips?
Click to expand...
Click to collapse
When it comes to A/B slot phones (Like the OnePlus 6T), you're not suppose to use the fastboot flash recovery twrp.img command. The reason why is because that command doesn't apply to A/B slotted phones, you need to use the fastboot boot twrp.img command to boot into TWRP and then flash the TWRP flasher for OnePlus 6T which can be found here:
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
Make sure to download the flasher zip and the latest img for TWRP.
Drag the .img into the fastboot folder and use fastboot boot twrp-3.3.1-8-fajita.img. Then once it boots into TWRP, drag and drop the installer zip onto your phone's storage and flash it. Reboot into recovery and you should have TWRP on your phone.
ImmorTaLGiLL said:
Use the Msm tool to recover if your phone is bricked.
https://forum.xda-developers.com/on...-msmdownloadtool-v4-0-oos-9-0-5-t3867448/amp/
Click to expand...
Click to collapse
I tried but didn't see it
Sadistic_Loser said:
When it comes to A/B slot phones (Like the OnePlus 6T), you're not suppose to use the fastboot flash recovery twrp.img command. The reason why is because that command doesn't apply to A/B slotted phones, you need to use the fastboot boot twrp.img command to boot into TWRP and then flash the TWRP flasher for OnePlus 6T which can be found here:
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
Make sure to download the flasher zip and the latest img for TWRP.
Drag the .img into the fastboot folder and use fastboot boot twrp-3.3.1-8-fajita.img. Then once it boots into TWRP, drag and drop the installer zip onto your phone's storage and flash it. Reboot into recovery and you should have TWRP on your phone.
Click to expand...
Click to collapse
ok but it does not go into fastboot mode or in recovery mode
FrancescoPtr said:
I tried but didn't see it
Click to expand...
Click to collapse
Make sure the device is off,Press volume up + volume down button then connect it to the computer.
If your device still doesn't show up,try pressing volume up+volume down+power button and then connect it.
This worked for me in many cases.
When I connect my phone via USB it shows up in the device manager as Qualcomm HS-USB.... But when I try using MSM it shows the phone connected on port 16 and I hit start and it fails after 16 seconds because it can't do a download. My question is is the download external via internet or is it a file in the MSM folder? I might be blocked by firewall at work if external.
EDIT: Looks like I found my issue. I couldn't tell if my phone was on or off since I had no display after trying about 20 more times I guess I got it ON.
Hi,
i used Miflash in edl mode to get back to stock rom. after flash and reboot I used the recovery mode to do a factory reset.
It seems to work. It shows Android Recovery, but the bootloader is still unlocked.
What mode do I need to enter to use the "fastboot oem lock" command? I always see "waiting for device" and nothing happens
When I type "adb devices" I can see the phone. I saw there is a command "fastboot devices", too. but it shows me no result.
Stevie123 said:
Hi,
i used Miflash in edl mode to get back to stock rom. after flash and reboot I used the recovery mode to do a factory reset.
It seems to work. It shows Android Recovery, but the bootloader is still unlocked.
What mode do I need to enter to use the "fastboot oem lock" command? I always see "waiting for device" and nothing happens
When I type "adb devices" I can see the phone. I saw there is a command "fastboot devices", too. but it shows me no result.
Click to expand...
Click to collapse
Reboot to fastboot using
adb reboot fastboot
Click to expand...
Click to collapse
Then, try to use fastboot cmd
Thanks, before I can try that I have to solve another problem.
That doesn't work. The phone isn't entering a special mode. I can choose fastboot from the bootmenu, too. But nothing happens. The phone does a restart, shows the bootmenu again and boots android after 5 seconds.
@Stevie123
You need to enable fastboot (bootloader) mode since it is disabled by ZTE, so that the selection from menu to be effective (after enabling it, in fastboot mode, your command "fastboot devices" (to check) and "fastboot oem lock" (to lock bootloader) will be accepted).
You can use Axon 7 EDL tool to unlock the bootloader.
It's already unlocked. I have to make another unlock procedure again to get access to fastboot? The EDL Tool tells me that I have to wipe and reset the phone after it. So it seems I can't keep my data and just lock the bootloader.
Either Lock or Unlock will wipe your data. And yes, the unlock procedure by Axon 7 EDL tool includes the enabling of fastboot. So you have to re-unlock if you want to relock.
I think this EDL tool doesn't work very good. It flashed something to make fastboot available, but I had a green ZTE Logo screen and this screen also had errors like white spots. The original ZTE logo is in cyan. But the fastboot worked and I could lock the phone. But I couldn't do anything else anymore. I couldn't reach Android and reflashing also didn't work. So I tried to use the EDL Tool to unlock my bootloader again. It said success, but it didn't work. It was still locked.
Well, I had to wait until the phone was empty. Luckily I could reach EDL Mode again. I used the MiFlash again to Downgrade to Android Nougat B12. I read somewhere that the fastboot is included there. So I had the right ZTE Logo back and it worked. I could leave the Bootloader locked. The final update I did with a SD Card to the lastest Android Software for Axon 7. Luckily without a brick. It's a pity that they don't offer any Updates anymore.
Weird: I was just using it normally, it switched off and now it stays stuck on the Google logo; when entering recovery mode, I get TWRP"s splash screen and it stays there, so I cannot even recover.
Suggestions please??
Note 1: I'm pretty bad with this kind of stuff, need step-by-step instructions.
Note 2: rom is AOSP 7.1.2 but I guess is irrelevant, as even TWRP does not load.
Thanks in advance!!
Can you fastboot boot the TWRP recovery?
Hmmm dont know exactly what that means sorry; I mean I havent tried connecting it to the laptop and using thr ADB toolkit, but I can reset via Power+VolDown to the bootloader menu (? the android layind down and giving the option to StartSystem/ SwitchOff/ Restart/ RecoveryMode), and choosing RecoveyMode it tries to launch TWRP (it even shows the logo) but stays there on the splashscreen, doesn't quite manage to give me the TWRP menus
Someone?
AndDiSa said:
Can you fastboot boot the TWRP recovery?
Click to expand...
Click to collapse
let's see... I set in recovery mode, connect to the PC (does not recognise it), and with "fastboot boot twrp.img" it just sends/writes the file, the tab shows the Google logo with open lock, and then tries to launch Twrp, but as before, it just get stuck in the splashscreen "TeamWin Recovery Project 3.3.1.0" , so just the same.
Command "fastboot flash boot twrp.img" the same
Command "fastboot flash recovery twrp.img" the same
Command "adb devices" returns the list empty
Command "adb reboot recovery" returns "error: no devices / emulators found"
Command "fastboot oem unlock" returns "(bootloader) bootloader is already unlocked"
I tried running a tool called FirstAid (https://forum.xda-developers.com/devdb/project/dl/?id=16684) but does nothing for me
I'm lost, please help
Video and photos of the issue (device, not adb)
video: https://photos.app.goo.gl/GrFrmQhbyQeHVFZN7
Well, looking at your video it seems that there is no bootable ROM installed and also the recovery (for what ever reason) has some issues to start.
The fact, that you are able to boot into bootloader shows that at least it's not completely bricked ... but there's still the chance that the flash memory has some issues.
I would connect the device via usb with a PC and try to do a
fastboot boot <twrp-3.3.1-grouper.img>
to whether in that case the recovery is booting.
If this is successful, the next step would be re-flashing the recovery into the recovery partition and booing into recovery mode from the bootloader.
If this is successful, too, wiping and flashing a new ROM would be the last step.