Related
hi, i really hope someone could help me,
I just put twrp and a custom rom on my phone and i was annoyed by the stupid warning messages at bootup so i tried to relock the bootloader with fastboot and disabled the allow oem lock option from the phone, after this my phone doesnt boot up anymore.
i can still get into twrp but there is nothing to do with it. i dont have anything on the internal storage( custom roms or anything) as it was wiped, it doesnt recognise an otg cable-usb stick either to put a rom on it (tried FAT, NTFS, and exfat too- its a micro usb otg cable with an adapter that works otherwise)
when i try to install a stock rom it doesnt let me obviously as the bootloader is locked, i cant use the fastboot oem unlock option because thats disabled from the developer options so i have no idea what could i do..
anyone here have a solution for this?
Thnaks
rolkabolka said:
hi, i really hope someone could help me,
I just put twrp and a custom rom on my phone and i was annoyed by the stupid warning messages at bootup so i tried to relock the bootloader with fastboot and disabled the allow oem lock option from the phone, after this my phone doesnt boot up anymore.
i can still get into twrp but there is nothing to do with it. i dont have anything on the internal storage( custom roms or anything) as it was wiped, it doesnt recognise an otg cable-usb stick either to put a rom on it (tried FAT, NTFS, and exfat too- its a micro usb otg cable with an adapter that works otherwise)
when i try to install a stock rom it doesnt let me obviously as the bootloader is locked, i cant use the fastboot oem unlock option because thats disabled from the developer options so i have no idea what could i do..
anyone here have a solution for this?
Thnaks
Click to expand...
Click to collapse
Flash a custom rom in recovery, boot into it and enable OEM unlock.
Unlock the bootloader in fastboot.
And then never again lock the bootloader if you have a custom recovery.
Maker that: Never lock the bootloader.... Why would you????
Edit: Oh, and you should have adb access in TWRP. Push the rom file to the phone or adb sideload it while in recovery.
i can't help you with unbricking your phone. in case you get it working again just don't attempt to lock your bootloader again as long as you are not on stock. the message when booting the phon is something you have to get used to i'm afraid.
as for your micro-usb OTG cable: from what i could gather around the web is that in your configuration this will never work. the problem is the micro usb to usb c adapter. it's not a problem of it beeing low quality or something like that, but rather an incompatible pin-configuration.
good luck anyway.
rolkabolka said:
hi, i really hope someone could help me,
I just put twrp and a custom rom on my phone and i was annoyed by the stupid warning messages at bootup so i tried to relock the bootloader with fastboot and disabled the allow oem lock option from the phone, after this my phone doesnt boot up anymore.
i can still get into twrp but there is nothing to do with it. i dont have anything on the internal storage( custom roms or anything) as it was wiped, it doesnt recognise an otg cable-usb stick either to put a rom on it (tried FAT, NTFS, and exfat too- its a micro usb otg cable with an adapter that works otherwise)
when i try to install a stock rom it doesnt let me obviously as the bootloader is locked, i cant use the fastboot oem unlock option because thats disabled from the developer options so i have no idea what could i do..
anyone here have a solution for this?
Thnaks
Click to expand...
Click to collapse
Also, if you get back to the custom ROM working, you can use this thread to "remove" the annoying warning message at boot:
http://forum.xda-developers.com/showpost.php?p=63826602&postcount=7
Mark
Nexus 5X, Chroma ROM, Franco Kernel, no unlock warning.
---------- Post added at 09:52 PM ---------- Previous post was at 09:45 PM ----------
rolkabolka said:
hi, i really hope someone could help me,
I just put twrp and a custom rom on my phone and i was annoyed by the stupid warning messages at bootup so i tried to relock the bootloader with fastboot and disabled the allow oem lock option from the phone, after this my phone doesnt boot up anymore.
i can still get into twrp but there is nothing to do with it. i dont have anything on the internal storage( custom roms or anything) as it was wiped, it doesnt recognise an otg cable-usb stick either to put a rom on it (tried FAT, NTFS, and exfat too- its a micro usb otg cable with an adapter that works otherwise)
when i try to install a stock rom it doesnt let me obviously as the bootloader is locked, i cant use the fastboot oem unlock option because thats disabled from the developer options so i have no idea what could i do..
anyone here have a solution for this?
Thnaks
Click to expand...
Click to collapse
I think item 11 in this first post of this thread should guide you:
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Mark
Use adb sideload function to sideload a third-party ROM like CM13
berndblb said:
Flash a custom rom in recovery, boot into it and enable OEM unlock.
Unlock the bootloader in fastboot.
And then never again lock the bootloader if you have a custom recovery.
Maker that: Never lock the bootloader.... Why would you????
Edit: Oh, and you should have adb access in TWRP. Push the rom file to the phone or adb sideload it while in recovery.
Click to expand...
Click to collapse
can you put files to the internal memory while you are in the recovery? i was not able to copy anything on it thats why i couldnt flash a new rom on it..
I tried t wipe the userdata, cache and those stuff but didnt let me cos it didnt mount the internal storage, but somehow it let me to do a factory reset in twrp which solved my problem. it booted in to the custom rom so i could enable everything..
thanks anyway
rolkabolka said:
can you put files to the internal memory while you are in the recovery? i was not able to copy anything on it thats why i couldnt flash a new rom on it..
I tried t wipe the userdata, cache and those stuff but didnt let me cos it didnt mount the internal storage, but somehow it let me to do a factory reset in twrp which solved my problem. it booted in to the custom rom so i could enable everything..
thanks anyway
Click to expand...
Click to collapse
I think you can enable MTP mode while you are in TWRP, then you can connect device to computer and copy files to internal storage. I've never get MTP work on my Galaxy S4's TWRP as well as adb sideload, but sideloading is working on my Nexus 9's TWRP. Who knows... maybe it works.
rolkabolka said:
can you put files to the internal memory while you are in the recovery? i was not able to copy anything on it thats why i couldnt flash a new rom on it..
Click to expand...
Click to collapse
Yes, I have used ADB via the "ADB Push" command on OSX to do so.
Sent from my Nexus 5X using Tapatalk
rolkabolka said:
hi, i really hope someone could help me,
I just put twrp and a custom rom on my phone and i was annoyed by the stupid warning messages at bootup so i tried to relock the bootloader with fastboot and disabled the allow oem lock option from the phone, after this my phone doesnt boot up anymore.
i can still get into twrp but there is nothing to do with it. i dont have anything on the internal storage( custom roms or anything) as it was wiped, it doesnt recognise an otg cable-usb stick either to put a rom on it (tried FAT, NTFS, and exfat too- its a micro usb otg cable with an adapter that works otherwise)
when i try to install a stock rom it doesnt let me obviously as the bootloader is locked, i cant use the fastboot oem unlock option because thats disabled from the developer options so i have no idea what could i do..
anyone here have a solution for this?
Thnaks
Click to expand...
Click to collapse
I am in the same boat did you ever fix the problem?
Nebula666 said:
I am in the same boat did you ever fix the problem?
Click to expand...
Click to collapse
adb sideload the latest ota.
Sent from my Nexus 5X using Tapatalk
I could be mistaken but can't you go the route of flashing the latest factory image through fastboot? or can you not get to fastboot? - you would unlock the bootloader through fastboot, flash the files, relock and boot
https://developers.google.com/android/nexus/images#bullhead
that or try what PiousInquisitor said
PiousInquisitor said:
adb sideload the latest ota.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I am having trouble side loading the the files... I keep getting verification errors https://goo.gl/photos/RVBsL2NRqzAUpJKT7
berndblb said:
Flash a custom rom in recovery, boot into it and enable OEM unlock.
Unlock the bootloader in fastboot.
And then never again lock the bootloader if you have a custom recovery.
Maker that: Never lock the bootloader.... Why would you????
Edit: Oh, and you should have adb access in TWRP. Push the rom file to the phone or adb sideload it while in recovery.
Click to expand...
Click to collapse
Why don't stock roms work? I had this same incident and had to use a custom ROM because I kept getting Sig verification errors when flashing Google roms
I think the problem is you are on 6.0 MDA89E (from the picture of your error), so side loading the latest OTA won't work. But you definitely should I should be able to flash the latest TWRP and then boot into it and move a custom ROM into internal memory and flash, once booted in tick OEM unlock and unlock the bootloader in fastboot.
Nebula666 said:
I am having trouble side loading the the files... I keep getting verification errors https://goo.gl/photos/RVBsL2NRqzAUpJKT7
Click to expand...
Click to collapse
This is a confusing device to work on, but I can help if you like. My recommendation is to fast boot flash the factory marshmallow image and go from there. Once your device is rooted with recovery there is a tool to remove the warnings
Sent from my Nexus 5X using XDA-Developers mobile app
ebowen 747 said:
This is a confusing device to work on, but I can help if you like. My recommendation is to fast boot flash the factory marshmallow image and go from there. Once your device is rooted with recovery there is a tool to remove the warnings
Sent from my Nexus 5X using XDA-Developers mobile app
Click to expand...
Click to collapse
Hey thanks for your help, but I fixed it. I have a hole other thread dedicated to the issues I was having. Sigh thanks tho
rolkabolka said:
hi, i really hope someone could help me,
I just put twrp and a custom rom on my phone and i was annoyed by the stupid warning messages at bootup so i tried to relock the bootloader with fastboot and disabled the allow oem lock option from the phone, after this my phone doesnt boot up anymore.
i can still get into twrp but there is nothing to do with it. i dont have anything on the internal storage( custom roms or anything) as it was wiped, it doesnt recognise an otg cable-usb stick either to put a rom on it (tried FAT, NTFS, and exfat too- its a micro usb otg cable with an adapter that works otherwise)
when i try to install a stock rom it doesnt let me obviously as the bootloader is locked, i cant use the fastboot oem unlock option because thats disabled from the developer options so i have no idea what could i do..
anyone here have a solution for this?
Thnaks
Click to expand...
Click to collapse
i`m sorry for being not to learn english language
Please go to recovery
operations fullwipe
operations Mount (Mount system & data & ... )
then go to sideload and copy rom to phone ( my suggestion CM13 )
and joy....
i installed cm14.1 today from the cyanogenmod website i had everything running fine until i reboot into recovery. i got a black screen and it didnt bot into recovery at all so i held my power button and volume down and nothing happens. i cant even boot up into fast boot or anything. nothing is turning my phone on. when i connect it to my pc nothing happens. is there anything i can do?
There's a mega unbrick guide for the OnePlus 3, use that then install the correct firmware and install the custom TWRP and re flash the ROM
i tried that method but the device doesnt even show up on my pc
envious86 said:
i tried that method but the device doesnt even show up on my pc
Click to expand...
Click to collapse
Get this sorted yet? You'll need a modified TWRP recovery for the newest CM based builds. I went through the same thing yesterday or the day before. Try holding volume down and power for like 30 seconds until you feel it vibrate that it is rebooting. Then hold volume *UP* while it reboots or if you see the "your device is not safe..." flash screen hurry and press volume down and go into fastboot. From there you can fastboot flash a new recovery.
I had the same problem as well, in device manager go to ports (com & LPT) and it will show up there under qualcum device. Don't forget to go and turn off certificate verification
Thanks guys I'll try this after work. Hopefully it works. If not sure oneplus are hopefully releasing a new phone soon
No it didn't work. I have a feeling I deleted something I shouldn't have because I was clearing out my files before I restarted and that was that.
you gotta use special twrp recovery for cm14.1...
https://www.androidfilehost.com/?fid=385035244224394867
Just use the recovery rahditzz provided you with a link, if your phone is stuck on black screen with white led hold your power button until it turns off, then boot to fastboot and flash the recovery and you will boot...
rahditzz said:
you gotta use special twrp recovery for cm14.1...
https://www.androidfilehost.com/?fid=385035244224394867
Click to expand...
Click to collapse
thanks didnt work. when i fastboot flash recovery and boot again it just goes into a black screen again
Then use unbrick method 2..
rahditzz said:
Then use unbrick method 2..
Click to expand...
Click to collapse
neither method works. all i can do is get into fastboot mode thats it. it wont show up on my pc at all
Method 2 workshop 100%, unless its a hardware fault..
Are you pushing volume up while plugging in cable?
I am. To be honest its very complex too me. I'm new to android and all this is so hard. I follow steps but I'm not 100% sure what I doing. Also my computer isn't great. Do these methods work on vista? Is there a video tutorial or anything? Sorry for annoying you and you don't understand how thankful i am for your help.
I jeep getting the sahara communication failed error
envious86 said:
I am. To be honest its very complex too me. I'm new to android and all this is so hard. I follow steps but I'm not 100% sure what I doing. Also my computer isn't great. Do these methods work on vista? Is there a video tutorial or anything? Sorry for annoying you and you don't understand how thankful i am for your help.
Click to expand...
Click to collapse
Your running vista???? Good god update your OS!!
Maybe your fastboot drivers got updated? There were some reports around this. You could try reinstalling the drivers and following the unbrick guide without an internet connection.
Sent from my ONEPLUS A3003 using Tapatalk
Cool u can boot into Fastboot, what error do you get when you type Fastboot devices? Nothing shows up?
Hi,
My phone got a message about a virus which I assumed was a devious add, it wouldn't go away so I rebooted. It has gone into Mi-Recovery 3.0 and I cant get out. I've tried to connect to PC suite but it won't connect to my laptop
without debugging, which I can't do. I've wiped data but no good. Any ideas?
Flash full rom img via EDL mode and MiFlash software. Check out the official forums how to do it all.
For me the command fastboot oem edl works to get into edl mode.
pr0x2 said:
Flash full rom img via EDL mode and MiFlash software. Check out the official forums how to do it all.
For me the command fastboot oem edl works to get into edl mode.
Click to expand...
Click to collapse
Thank you for answering. I have downloaded a full rom and the MiFlash software. I have made an EDL cable but nothing happens. From what I read it says turn the phone off and connect the modified cable and it will enter EDL mode however it just stays on the Mi-Recovery 3.0 page. I've tried the command line you suggest but that can't find the phone. I've also tried the test point method and still can't get into edl mode. What am I doing wrong?
Sorry, I'm new to this so don't really know what I'm doing. Would you be able to give me some easy to follow advise or some links please.
Multi57 said:
Thank you for answering. I have downloaded a full rom and the MiFlash software. I have made an EDL cable but nothing happens. From what I read it says turn the phone off and connect the modified cable and it will enter EDL mode however it just stays on the Mi-Recovery 3.0 page. I've tried the command line you suggest but that can't find the phone. I've also tried the test point method and still can't get into edl mode. What am I doing wrong?
Sorry, I'm new to this so don't really know what I'm doing. Would you be able to give me some easy to follow advise or some links please.
Click to expand...
Click to collapse
You need your normal USB C cable. When you are in fastboot you need to type "fastboot oem edl" your screen will go to black and you are now in EDL mode. Now flash full img via miflash software.
pr0x2 said:
You need your normal USB C cable. When you are in fastboot you need to type "fastboot oem edl" your screen will go to black and you are now in EDL mode. Now flash full img via miflash software.
Click to expand...
Click to collapse
I cant get to fastboot as I'm stuck in Recovery. My only choices are Reboot to System and Back to Main Menu. When I'm in Main Menu my choices are Reboot, Wipe Data or Connect with MIAssistant.
Multi57 said:
I cant get to fastboot as I'm stuck in Recovery. My only choices are Reboot to System and Back to Main Menu. When I'm in Main Menu my choices are Reboot, Wipe Data or Connect with MIAssistant.
Click to expand...
Click to collapse
When you turn off the phone and press vol down + power what does that do?
It shows the Mi start screen then boots strait into recovery Main Menu. I can't turn the phone off without it rebooting.
Does anyone know how I can get around this? I've run out of things to try.
Did you try reflashing the recovery maybe that fixes it?
Sent from my MI 5s using Tapatalk
Can you explain how I do that? I can't connect to my computer so not sure what you mean. I'm new at this so unsure of the options.
Multi57 said:
Can you explain how I do that? I can't connect to my computer so not sure what you mean. I'm new at this so unsure of the options.
Click to expand...
Click to collapse
Oh hmm never mind. Ignore what I said above. I thought you had TWRP recovery but you've got the stock one.
Sent from my MI 5s using Tapatalk
templeka said:
Oh hmm never mind. Ignore what I said above. I thought you had TWRP recovery but you've got the stock one.
Sent from my MI 5s using Tapatalk
Click to expand...
Click to collapse
Is there no way of getting out of stock recovery?
Maybe your volume rocker buttons are faulty .
Happened with one of my friend his device was only booting into recovery mode on reboot because vol+ button was permanently stuck ?
Try to lift up the button if it is stuck or
press button repeatedly for sometime .
Ashish 289, you are right, it was a faulty volume rocker. Once disconnected it booted. Thanks.
Multi57 said:
Hi,
My phone got a message about a virus which I assumed was a devious add, it wouldn't go away so I rebooted. It has gone into Mi-Recovery 3.0 and I cant get out. I've tried to connect to PC suite but it won't connect to my laptop
without debugging, which I can't do. I've wiped data but no good. Any ideas?
Click to expand...
Click to collapse
now its my turn brother got my mi5 bricked in the same way .
it stays in mi recovery 3.0 always . if you tell me what you did after these steps not working ? could you do anything ?
need a solution man, please help .
thanks in advance.
Hi, I am new to custom ROMs install , recently got a Poco F3 and When installing I run into a problem, the pc doesnt recognize the device after I run the batch install for the device, when running the console, it gets stuck here (Ill add a picture), its been one hour like this, whta can I do? I am using the lastest version of Pixel Extended.
Also I can no longer get back into normal MIUI so IDK what to do.
Thanks for any help and sorry if this sounds like such a noob mistake but I am really lost right now
Edit:
SOLVED! IDK how, but It was a drivers issue, had to install It and uninstall it multiple times, sometimes the device manager would recognize it but the console script wouldn't, don't know really why it happened but hey I fixed it and managed to install custom ROMs, thanks for the help.
looks like a driver issue when its rebooting fastboot mode,check device manager,might just need to unplug cable and then plug back in to get it working again.
if that doesnt help try a different driver on the pc.
metalspider said:
looks like a driver issue when its rebooting fastboot mode,check device manager,might just need to unplug cable and then plug back in to get it working again.
if that doesnt help try a different driver on the pc.
Click to expand...
Click to collapse
And which kind of driver should I get because in the MIUI unlock app, it says that the latest drivers are installed. Where could I get other drivers?
Bruh124 said:
And which kind of driver should I get because in the MIUI unlock app, it says that the latest drivers are installed. Where could I get other drivers?
Click to expand...
Click to collapse
are u able to boot to recovery? at this step, your phone should boot to recovery, and enter fastboot from there
if able to enter recovery, select advanced > enter fastboot
the installation should continue. dont seem a like a driver issue to me
keyoke87 said:
are u able to boot to recovery? at this step, your phone should boot to recovery, and enter fastboot from there
if able to enter recovery, select advanced > enter fastboot
the installation should continue. dont seem a like a driver issue to me
Click to expand...
Click to collapse
It DID get into recovery mode with the pixel experience logo in it but the script wouldn't move past after waiting for device(one time for like 2 hours)
In the end IDK how, but It was a drivers issue, had to install It and uninstall it multiple times, sometimes the device manager would recognize it but the console script wouldn't even start saying waiting for device , don't know really why it happened but hey I fixed it with that trick and managed to install custom ROMs, thanks for the help!!
So I downloaded pixelos and wished to revert to stock miui, i was using the miflash tool and in the first few seconds my usb disconnected. Then i could not exit fastboot no matter what I pressed. I've tried to flash miui again but am getting the error "data transfer error" and "data transfer time unknown". I could really use the help. Thank you
This kind of crap happened to my Redmi K30 Pro as well. The only difference is that mine did not turn on anymore after I tried to restart it. Both Recovery Mode and Fastboot are unaccessible.
I think there's always a risk going from a custom rom back to miui, specially so when using fastboot.
If u can access EDL mode either via touch point or EDL Usb cable, do that and try flashing the MIUI again through Mi-Flash. Make sure you're using the same MiAccount and hope they will flag it as authorized, otherwise you'll be forced to take it to a service center and have the whole motherboard replaced.
You can also use QFIL but that's a unreliable tool and it always spouts out Sahara error messages.
iceman0826 said:
This kind of crap happened to my Redmi K30 Pro as well. The only difference is that mine did not turn on anymore after I tried to restart it. Both Recovery Mode and Fastboot are unaccessible.
I think there's always a risk going from a custom rom back to miui, specially so when using fastboot.
If u can access EDL mode either via touch point or EDL Usb cable, do that and try flashing the MIUI again through Mi-Flash. Make sure you're using the same MiAccount and hope they will flag it as authorized, otherwise you'll be forced to take it to a service center and have the whole motherboard replaced.
You can also use QFIL but that's a unreliable tool and it always spouts out Sahara error messages.
Click to expand...
Click to collapse
I am not familliar with EDL mode, any tutorials you know to get into that? I really appreciate it.
Google is your bestfriend. If ur going with touch point method, know that it will void the warranty as you'll have to open it and short the pins, to invoke EDL mode.
EDL cable is advisable so try that first and follow the instructions that came with the package. It's a cable with a button.
iceman0826 said:
Google is your bestfriend. If ur going with touch point method, know that it will void the warranty as you'll have to open it and short the pins, to invoke EDL mode.
EDL cable is advisable so try that first and follow the instructions that came with the package. It's a cable with a button.
Click to expand...
Click to collapse
And once im in EDL mode, do i just have to try the miflash tool again?
Also can i try get TWRP again and try boot a rom from there, could that be possible?
If u can access the recovery mode then try that first.
For EDL mode, yes you have to use MiFlash for this. Make sure you're using the same Mi Account that you've used when you unlocked the bootloader and do not remove the device from the Mi Account. This way, it will recognized it as authorized and it will flash successfully.
iceman0826 said:
If u can access the recovery mode then try that first.
For EDL mode, yes you have to use MiFlash for this. Make sure you're using the same Mi Account that you've used when you unlocked the bootloader and do not remove the device from the Mi Account. This way, it will recognized it as authorized and it will flash successfully.
Click to expand...
Click to collapse
Okay I've managed to get TWRP installed, any idea what to do from here?
I'm sure you're knowledgeable in flashing, and knows how to use google. I'm sure u also know that accessing TWRP is a good sign and u can now access fastboot or EDL via adb from there.
iceman0826 said:
I'm sure you're knowledgeable in flashing, and knows how to use google. I'm sure u also know that accessing TWRP is a good sign and u can now access fastboot or EDL via adb from there.
Click to expand...
Click to collapse
I've only flashed one custom rom so not too knowledgable, I would probably try to get a miui recovery file and transfer it to my phone and then install from twrp. I think that would work
Also i cant decrypt my data despite entering the only pin I have ever used