Is there any way to boot into Fastboot without booting into OS and using ADB?
E.g. when in bootloop Cox of MAGISK?
Fastboot would at least allow for stock kernel.
Maybe it's stupid question but I can't not into it at all from turned off device.
No problem with recovery tho...
I'm stupid or it wasn't there before. I tried both Vol- and + on OotB firmware (don't remember version) as well as .38 and all I could do is booting into OS and recovery.
Now, .40, Vol+ does nothing, but - boots into bootloader mode,
I love it, as it gives me access to all things - fastboot, "fast" power off, recovery, etc. Similar to how Moto has and as I moved from Moto Z3 Play to X3 I'm in love
Can you tell me how did you go to the fastboot mode?
Hi there https://youtube.com/c/TRICKSTER11 this yt channel about realme x3 and x3 sz
Related
Hello there,
i need help with unbricking my Bq Aquaris X5 Cm Edition (codenname: paella).
I flashed Twrp, was not able to flash SU.zip. And flahsing LineageOs failed with "error7"
after i was unable to flash lineage and doing other stuff i had no system installed any more so i flashed cm unnofical gohan version with the flashall.bat.
And then i rebooted and had the mess. The phone does not want to turn on. Only thing that the phones give me as a "sign of life" is the red LED when i plug in the charging cable and give him power.
Im not able to get into fastboot or recovery mode. So my questions is: Is there ANY way to get that phone back to life?
Istn the normal way flahsing old bootloader and then original firmware?
But for that i need to get to fastboot mode which im not reaching.
LaCereb said:
Hello there,
i need help with unbricking my Bq Aquaris X5 Cm Edition (codenname: paella).
I flashed Twrp, was not able to flash SU.zip. And flahsing LineageOs failed with "error7"
after i was unable to flash lineage and doing other stuff i had no system installed any more so i flashed cm unnofical gohan version with the flashall.bat.
And then i rebooted and had the mess. The phone does not want to turn on. Only thing that the phones give me as a "sign of life" is the red LED when i plug in the charging cable and give him power.
Im not able to get into fastboot or recovery mode. So my questions is: Is there ANY way to get that phone back to life?
Istn the normal way flahsing old bootloader and then original firmware?
But for that i need to get to fastboot mode which im not reaching.
Click to expand...
Click to collapse
I'm in the same situation with a BQ X5 plus, I think the only way is to get the phone to the BQ service center
Did you get the phone working again ?
Nope i handed it over to the support and got a New one because guarentee was still valid
LaCereb said:
Hello there,
i need help with unbricking my Bq Aquaris X5 Cm Edition (codenname: paella).
I flashed Twrp, was not able to flash SU.zip. And flahsing LineageOs failed with "error7"
after i was unable to flash lineage and doing other stuff i had no system installed any more so i flashed cm unnofical gohan version with the flashall.bat.
And then i rebooted and had the mess. The phone does not want to turn on. Only thing that the phones give me as a "sign of life" is the red LED when i plug in the charging cable and give him power.
Im not able to get into fastboot or recovery mode. So my questions is: Is there ANY way to get that phone back to life?
Istn the normal way flahsing old bootloader and then original firmware?
But for that i need to get to fastboot mode which im not reaching.
Click to expand...
Click to collapse
yes you have to install qualcomm drivers and see in what mode the phone are.
9006, 900E or 9008
solved
I HAD the same problem with my BQ Aquaris X Pro.
Running the lineage OS 15.1, rooted with AddonSu installed.
This is how I was able to wake it up again.
1) I unplugged the phone from the USB loading cable
(don't know if this step is needed - the battery was definitely not totally empty, when this red flashing LED thing occurred. However, i don't think the phone charges when the LED red light flashes.).
2) I took the sim card out (don't know if this step is needed).
3) I pressed for about 2 [minute] power and volume (don't know if up or down) button together. And then it woke up again.
Maybe this is the special boot recovery mode option mentioned here?
What ever it is, it worked for me.
+ https : / / wiki.lineageos.org/devices/bardockpro
Good luck!
ElmBeech
R3 Pro (3GB/32GB, 2015817 version) came with some chinese/sellers custom ROM (and locked bootloader). It was heavy and bloated, so I decided to update it. Tried latest global stable (fastboot) ROM via miflash, flash was successful but that's was a lie - it stuck on mi logo...
Then I tried various other ROMs, global and developers, latest and older, some xiaomi.eu, manhit, etc. (for locked bootloader) and all I've got was either just a mi logo or mi logo with "powered by android" animation beneth. I left it for hours after flash and still nothing.
Then I found some ways to flash twrp, did that successfully, booted into it, wonder around in terminal and file manager, tried some recovery ROMs - but the result is the same - just logo or logo + animation.
I can get into fastboot (but it doesn't realy matters since bootloader is locked), download (EDL) mode, that Xiaomi menu (with Power and Vol+, with "shortcuts" to all the modes, hardware tests - btw. everything works there, etc.), twrp, charge battery (with some ROMs phone just gets warm and I know it's charging, there are no LED and/or animation, but in some everything works just like it should), but just can't boot into OS.
And I'm going nuts!
Here are some logs from the last ROM (i don't even know anymore which one is it) - pastebin.com/qaKVzxue and pastebin.com/dM3nEVj0
I'm not so experienced in looking at that but seems like every other thing in there, like cpu, i2c (touch/sensor), sound, battery, etc. is broken/faulty which is not true - everything was fine before update, and everything IS still fine according to inbuilt (xiaomi) hardware tests.
So somehow it seems that all the ido ROMs I tried are wrong for this device? Or am I missing something (quite possibly, I'm tired and pissed off)
Last night I did a backup of efs/nvram and then wiped internal memory/partitions, flashed latest global ROM, restored efs/nvram - phone stuck, but this time not on MI logo but freakin' penguin logo (like here en.miui.com/thread-377870-1-1.html). Same logo is for fastboot mode, no more bunny. Then flashed twrp and phone now shows mi logo with "powered by android" animation beneath, like before...
I don't know how this works with Xiaomi phones, but looks like it worked with some factory/seller special combination of ROM and bootloader. Then I did update and something stuck, maybe differences between ROM and bootloader, or some inside/hidden security mechanism that stops boot process? And because I can't find original firmware and/or bootloader is locked (maybe even updated?) it's now stuck...
Either that or some HW fault, but it would be insane that official ROM update with official tools and in factory download mode with full battery can cause such problem!
Can you go to twrp recovery?
Yes, like I said in the first post. I can do anything but boot android/MIUI. It's either because of locked bootloader or somehow official ROM installed officialy (via MiFlash in EDL mode) bricked phone, which is catastrophic bug i.e. epic design/implementation fail by Xiaomi.
Try this
https://forum.xda-developers.com/redmi-3/help/bootloop-bootloader-locked-options-t3331139
Sorry to intrude, I have pretty much the same problem.
Phone is stuck in bootloop and I can only access fastboot mode and EDL mode (but in EDL the phone does not connect to pc) and when I try to flash a stock ROM (since I know it is a software issue due to an unfortunate update) it says "locked device". So I tried to unlock it via MiUnlock... but phone cannot be verified 'cause "account not bound to this device" and obviously I cannot change any options since I cannot use my phone.
Please, help
it was happened to me about 3 days ago when i play around with the twrp & rooting thingy... tried everything from youtube to various forum solutions... just one link really works when you only have fastboot options and your phone bootloader is still unlocked. just follow the steps in the OP... key things here is downloading the tool to read your phone as mentioned in the OP i.e [TOOL]Minimal ADB and Fastboot [1-6-17]
1) Download Tool -> https://forum.xda-developers.com/showthread.php?t=2317790
2) Follow all the steps in the OP -> http://en.miui.com/thread-277276-1-1.html
3) Enjoy your phone from back from the dead.. LOL!
4) Remember here, the key is NEVER GIVE UP and PATIENT!
NOTE : The Device will start, wait till completion , it can take up to 10 Minutes. -> for me around 15-20 minutes for I have flashed the current beta rom of MIUI8 7.6.8
cheers, guys!
blx-
I had a similar situation.
Officially unlocked boot loader. Flashed TWRP using fastboot. Only got the mi logo and a boot loop on start up.
Could not turn on. Could not boot into TWRP.
When the phone was boot looping I could still get into fastboot mode by holding power+volume down.
I booted from fastboot mode into TWRP by opening the command prompts and using
"fastboot boot twrp2.img"
That got the phone available from windows explorer. I was able to move a new ROM image to the SD card and install from TWRP.
Currently running lineage 14.1 -20190112.
I lost a bunch of **** but my phone seems to turn on for the moment.
Note, I still cannot boot into TWRP using the phone only. I can only boot in from fast boot as above.
Hi!
I have a OnePlus X and the year after I bought it, I flashed TWRP and installed Lineage OS. Since then, I've flashed many custom roms on my phone. A few weeks back, I decided to flash Resurrection Remix. The battery life on my phone with resurrection was pathetic so I assumed it could be fixed by flashing a custom kernel (franco kernel). I downloaded franco kernel, copied it to my SD card and powered off my phone.
Instead of pressing the VOLUME DOWN and POWER button simultaneously to enter TWRP, I pressed the VOLUME UP and POWER button by accident and went into Fastboot mode. When in Fastboot mode, I pressed the VOLUME DOWN and POWER button thinking my phone would boot into recovery, but it got stuck in a bootloop.
Now my phone can boot only into fastboot mode by pressing the volume up+power button. Any other combination of buttons and it goes into a bootloop.
All this is completely my fault and I would do anything to try and fix it.
Is my phone soft bricked or hard bricked? ( I have a feeling that it is soft bricked).
I've downloaded the android SDK and Minimal adb and fastboot on my pc. I'm able to run fastboot commands, but when I type 'fastboot oem unlock', I get an error saying
"FAILED (remote: oem unlock is disabled)". I've tried 'fastboot flashing unlock' too, but the screen just says "...". Hence, I'm not able to flash TWRP. I tried flashing even the stock recovery but it wouldn't work.
Is there any other way to unlock the bootloader?
I haven't tried the Mega unbrick guide for a hard bricked OnePlus X yet, since I'm able to boot into fastboot mode. Should I give it a shot?
And lastly, can I recover my phone from this mess or is it permanently bricked?
I would appreciate any help.
Thank you!
Sounds very similar to my situation. I did end up following that guide to get mine going again. The link is broken to get the recovery tool, the 2nd one below is the "minimal" version which isn't supposed to wipe data. That is the one that worked for me. I would backup any data if you can first, no guarantee it wont wipe it. Mine wouldn't boot into the stock rom after, but at least it would get to the stock bootloader (VolDOWN + PWR). From there I was able to adb sideload the stock rom (Install from USB). This completely restored it to stock.
23santosh24 said:
Hi!
I have a OnePlus X and the year after I bought it, I flashed TWRP and installed Lineage OS. Since then, I've flashed many custom roms on my phone. A few weeks back, I decided to flash Resurrection Remix. The battery life on my phone with resurrection was pathetic so I assumed it could be fixed by flashing a custom kernel (franco kernel). I downloaded franco kernel, copied it to my SD card and powered off my phone.
Instead of pressing the VOLUME DOWN and POWER button simultaneously to enter TWRP, I pressed the VOLUME UP and POWER button by accident and went into Fastboot mode. When in Fastboot mode, I pressed the VOLUME DOWN and POWER button thinking my phone would boot into recovery, but it got stuck in a bootloop.
Now my phone can boot only into fastboot mode by pressing the volume up+power button. Any other combination of buttons and it goes into a bootloop.
All this is completely my fault and I would do anything to try and fix it.
Is my phone soft bricked or hard bricked? ( I have a feeling that it is soft bricked).
I've downloaded the android SDK and Minimal adb and fastboot on my pc. I'm able to run fastboot commands, but when I type 'fastboot oem unlock', I get an error saying
"FAILED (remote: oem unlock is disabled)". I've tried 'fastboot flashing unlock' too, but the screen just says "...". Hence, I'm not able to flash TWRP. I tried flashing even the stock recovery but it wouldn't work.
Is there any other way to unlock the bootloader?
I haven't tried the Mega unbrick guide for a hard bricked OnePlus X yet, since I'm able to boot into fastboot mode. Should I give it a shot?
And lastly, can I recover my phone from this mess or is it permanently bricked?
I would appreciate any help.
Thank you!
Click to expand...
Click to collapse
Surely your bootloader is already unlocked isn't it?
You don't actually say what happens when you try to reboot into recovery using fastboot commands. Does that fail too? What happens when you try to flash twrp again? You don't actually say.
That's what I thought too. It would just say 'recovery.img' not found or something like that. But, I followed the Mega unbrick guide and was able to install the stock ROM through the stock recovery. My OPX is alive again!
i'm stuck here. the phone does not go into recovery at all .. stuck on oneplus logo .. I don't know what to do .. any ideas?
---------- Post added at 09:20 AM ---------- Previous post was at 08:24 AM ----------
I managed to get it alive again with this guide
HI,
I inherited this phone. ( D6503 )
Fixed a few hardware problems, now looking at software improvements.
I have unlocked the bootloader , but for the life of me I cannot get a recovery on this phone??
I have previoiusly done flashing on nokia, motorola and Nexus, but I am having no luck with this sony
I am able to connect using ADB, and can get to fastboot, but it stops there.
Issuing '' fastboot boot twrp.img'' ( to try and boot temporarily to twrp ) gives me a blank screen.
issuing ''fastboot flash recovery twrp.img'' does the same.
I cannot get a bootloader screen at all, even using the key combinations.
I cannot boot any recovery at all.
Is there someone here who can put me out of my misery
I am not looking to perform anything fancy, I just want to flash the latest lineage to see how it performs
Many Thanks in advance.
pootler.
Anybody???
I have rooted the z2 by dropping down to 5.11, installed the twrp app, then flashed recommended version of twrpl
Then when I power off the phone, and press the power and volume down buttons, instead of booting into twrp after 7 or so seconds, it just reboots after abour 2-3 seconds???
Can anybody help?-------please
I have even tried rooting , then installing twrp by either 1) fastboot or 2) twrp app.
I then installed NDR utils, to reboot to recovery - it still reboots to main system??
HEEELLPP !
I also tried flashing TWRP with 1) fastboot and 2)the twrp app,
I then installed NDR utils ( i have root ) , and it still wont boot into recovery, just straight into system???
HEELLPP!!
Thread closed on request of OP @pootler
Hi Community,
I read some posts how to fix my Problem, but i cant go to a service Point.
So I was using the Evolution X for a long Time (Installed with TWRP 3.1.0).
And now i wanted to change to the Nusantara Project (Vanilla), I did a clean Flash, everything worked i could access the System.
Than i had problems installing Play Store, so i rebooted into Recovery via the System. But now im Stuck in the Loop.
Can i Somehow connect my Phone to the PC and Reset?
Can someone tell me if i Hard/soft bricked my phone ?
Just a little advice, would be really appreciated.
Thanks a lot
Go to TWRP, wipe system, cache, data and dalvik. Now flash nusantra and whichever GApps are recommended for it (if there are no recommendations then use OpenGApps, make sure the architecture is correct). Now wipe dalvik and restart. Sometimes, certain roms begin to bootloop if you boot into the rom first, then try to install gapps later.
If you still have issues, just reflash the stock rom.
I cant access the TWRP anymore, im just stuck on the Bootloader, no matter how i turn on The Phone (Volume Up + Power ON ), (Volume Down + Power), (All 3 Buttons)
Nothing works anymore i dont understand ....
Im searching the net but i cant go to fastboot or something else, its just keeps on rebooting ...
So it's bootlooping, but you cant access recovery?
When the screen turns off, press the key combo and it should go to recovery.
Your best bet is to take it to a service centre, but if that really isn't possible for you, then wait for its battery to drain completely, then when you plug in the charger, instead of turning the phone on, press the key combo to enter the recovery. From there, wipe and flash some other OS.
I've also heard that certain versions of TWRP don't support some roms, leading to a bootloop. In that case, you'll have to use orangefox recovery to flash the rom (orangefox is flashable via twrp)
Yes its Bootlooping.
When i turn it on, on the Left Corner "Recovery Mode" blinks for one second. Than the usual Text appears:
"Orange State
Your Device has been unlocked and cant be trusted
Your Device will boot in 5 Seconds".
So after a couple of seconds (around 10-20 sec)
It turns off and immediately on again. I Just can turn it OFF when i hold all 3 Buttons.
Than i try starting it with Volume up + Power / Volume down + Power, But i cant access Recovery or TWRP.
So i should wait til the battery gets low and try it again ?
Like i said, my custom Rom (Evolutionx) and TWRP just worked fine. I dont know man ...
Well since your bootloader is unlocked, try flashing the stock rom again. Look for a tutorial and follow it.
Hi I managed to unbrick my device with this guide, and im back on a stock rom
Unbrick
i ran following commands to get to my custom rom:
I run adb reboot bootloader,
add executed following commands.
(Pitch Black recovery 3.1)
- adb reboot bootloader
- fastboot flash recovery recovery.img
-fasboot reboot recovery
It just hang up and booted after a while into the normal system.
But im not able to get to the recovery menu ?
When I restart and hold Volume up + Power, i go in a loop and the phone keeps restarting over and over again.
what have i Fu**ed up ?
Do i need another recovery tool ?
sorry guys, i appreciate your help a lot tho !
EDIT: Is my bootloader unlocked ?
I can access via "adb reboot bootloader" the phone
and on the blackscreen on the phone it is written:
oppo verfiy pass
fastboot_unlock_verify ok
Update:
So i tried some Stuff and i got Red State. No Problem i Unbricked it once again and now im on Stock Android 10.
Now im Trying to enable the bootloader again.
I downloaded the In Depth Test_Realme_6.apk but i keep getting the Error that i should update the system.
So should i update the system ?
I cant find a CURRENT Tutorial to make this work, please help...
If you cant find a tutorial for your version, why not downgrade back to a previous one if possible.