Database Develop

*HELP!!* locked bootloader with no OS

So here's my problem...
I've accidentally wiped out entire phone (including OS)...
I still have access to TWRP, but the bootloader is locked, meaning I cannot flash stock rom (or any roms) to my phone...
I've tried to use following command:
fastboot oem unlock​but it gives me this:
<bootloader> Check 'Allow OEM Unlock' in Developer Options.​FAILED <remote failure>​
How can I check 'Allow OEM unlock' if I can't even get to the setting..?
I see others have similar issue like me but there's no solution to be found... Anyone know how to fix this problem??

prestigiousboi said:
So here's my problem...
I've accidentally wiped out entire phone (including OS)...
I still have access to TWRP, but the bootloader is locked, meaning I cannot flash stock rom (or any roms) to my phone...
I've tried to use following command:
fastboot oem unlock​but it gives me this:
<bootloader> Check 'Allow OEM Unlock' in Developer Options.​FAILED <remote failure>​
How can I check 'Allow OEM unlock' if I can't even get to the setting..?
I see others have similar issue like me but there's no solution to be found... Anyone know how to fix this problem??
Click to expand...
Click to collapse
Boot into TWRP. Connect to PC. Download a ROM to your PC. Drag and drop the ROM into your internal storage. Flash ROM with TWRP. Enable oem unlock via developer options. Boot to bootloader. Fastboot oem unlock.

Evolution_Tech said:
Boot into TWRP. Connect to PC. Download a ROM to your PC. Drag and drop the ROM into your internal storage. Flash ROM with TWRP. Enable oem unlock via developer options. Boot to bootloader. Fastboot oem unlock.
Click to expand...
Click to collapse
Thanks for the comment,
I've tried it and it gave me following error:
Skipping MD5 check: no MD5 file found​Error flashing zip 'sdcard/image-shamu-lmy47d.zip'​

Evolution_Tech said:
Boot into TWRP. Connect to PC. Download a ROM to your PC. Drag and drop the ROM into your internal storage. Flash ROM with TWRP. Enable oem unlock via developer options. Boot to bootloader. Fastboot oem unlock.
Click to expand...
Click to collapse
^ this. You'll still be able to flash a rom because you have twrp.

prestigiousboi said:
Thanks for the comment,
I've tried it and it gave me following error:
Skipping MD5 check: no MD5 file found​Error flashing zip 'sdcard/image-shamu-lmy47d.zip'​
Click to expand...
Click to collapse
Are you trying to flash a factory image through TWRP? That won't work. Download a ROM (other than M preview) from the Android development section. Any custom ROM other than M.
---------- Post added at 07:42 PM ---------- Previous post was at 07:40 PM ----------
Something like this:
http://forum.xda-developers.com/showthread.php?t=3061595

Evolution_Tech said:
Are you trying to flash a factory image through TWRP? That won't work. Download a ROM (other than M preview) from the Android development section. Any custom ROM other than M.
---------- Post added at 07:42 PM ---------- Previous post was at 07:40 PM ----------
Something like this:
http://forum.xda-developers.com/showthread.php?t=3061595
Click to expand...
Click to collapse
why not m? it booted fine for me via twrp, the twrp flashable version at least.

simms22 said:
why not m? it booted fine for me via twrp, the twrp flashable version at least.
Click to expand...
Click to collapse
To get him up and running with a locked bootloader, I chose to keep it simple. M would require the bootloader and radio flash and that's not happening with a locked bootloader.

Evolution_Tech said:
Are you trying to flash a factory image through TWRP? That won't work. Download a ROM (other than M preview) from the Android development section. Any custom ROM other than M.
---------- Post added at 07:42 PM ---------- Previous post was at 07:40 PM ----------
Something like this:
http://forum.xda-developers.com/showthread.php?t=3061595
Click to expand...
Click to collapse
I love you man. Thank you for helping me (a noob)

prestigiousboi said:
I love you man. Thank you for helping me (a noob)
Click to expand...
Click to collapse
I guess that means you got it working. :victory: :good:

Evolution_Tech said:
To get him up and running with a locked bootloader, I chose to keep it simple. M would require the bootloader and radio flash and that's not happening with a locked bootloader.
Click to expand...
Click to collapse
doesnt require the radio flash, but does require the bootloader flash. I did forget though, you're right. I updated that via twrp as well. but you are very right about keeping it simple

i got excited when i found this thread. then I realized I have no recovery. this phone is seriously screwed it isn't showing any screens or anything

Stuck in boot up screen

ok, i am stuck on my boot up screen. i flashed a zip file xposed arm zip. after the reboot it will not pass the boot animation screen. now on my old Motorola phone, i would do the pwr + vol keys to boot back in to recovery. well this does no work on my X. any one have any ideas. I am rooted, unlocked, twrp was installed from play store, & i did do a back up. thanks

JWACK72 said:
ok, i am stuck on my boot up screen. i flashed a zip file xposed arm zip. after the reboot it will not pass the boot animation screen. now on my old Motorola phone, i would do the pwr + vol keys to boot back in to recovery. well this does no work on my X. any one have any ideas. I am rooted, unlocked, twrp was installed from play store, & i did do a back up. thanks
Click to expand...
Click to collapse
What device do you have, XT1095, XT1097, etc? And you are not able to boot into the bootloader using vol down + power correct?

It was a 1096, now its trash. it would go into fastboot, but could not get into twrp recovery. its done. RIP

JWACK72 said:
It was a 1096, now its trash. it would go into fastboot, but could not get into twrp recovery. its done. RIP
Click to expand...
Click to collapse
If it boots to fastboot, it's not dead. Just reflash the recovery and you're good to go.
Sent from my XT1095 using Tapatalk

Was there a resolution for this? I'm having a similar problem. I'm not sure how I got to this status, but here's what I'm dealing with:
Device: XT1095
Bootloader: Unlocked
Rooted, ROM - Resurrection Remix, TWRP
Turning on the phone reaches the RR bootsplash and proceeds to bootloop.
When holding down the power and volume down, it will enter fastboot.
When I try to open TWRP recovery, it'll show the blue TWRP screen and just sit there.
I have tried to reinstall TWRP, but that has no effect. I didn't want to manually flash another ROM or go back to stock because at least now it seems USB debugging is on and if I flashed a ROM I cant be sure I'd be able to turn it on. Do any of you pros have some ideas hove I can get back into my phone? Thanks

bibbin said:
I have tried to reinstall TWRP, but that has no effect. I didn't want to manually flash another ROM or go back to stock because at least now it seems USB debugging is on and if I flashed a ROM I cant be sure I'd be able to turn it on. Do any of you pros have some ideas hove I can get back into my phone? Thanks
Click to expand...
Click to collapse
Do you have a USB-OTG device plugged in while trying to start TWRP? If so remove it, you can mount it after TWRP starts if this helps.
Have you tried a different build of TWRP? I'm currently using the one built by invisiblek, one of the CM devs for the victara. It was built and posted on December 8th and is here: http://www.invisiblek.org/twrp/twrp_2.8.7.0-0624b8bd_victara.img
Have you tried flashing the stock recovery to see if that will start? If it does, you could use the factory reset option there and then try reinstalling TWRP. (TWRP has a settings directory in /sdcard and maybe that is corrupted.)
There have been a few people posting with this problem but I've not seen a definitive fix for it.

Thank for the quick response. No, I don't have USB-OTG inserted. It is using TWRP 2.8.7.1. No, I haven't tried installing the version you mentioned. What I did do was attempt to flash the pre-installed TWRP 2.8.1.0 via MOTO X TOOLKIT. It failed. I'm not very experienced at using ADB manually. As I mentioned, I've been reluctant to flash another ROM (custom or stock) because I don't want to get stuck with USB debugging inactive with no way to get in far enough to reactivate it.
---------- Post added at 04:32 PM ---------- Previous post was at 03:40 PM ----------
If I manage to install the invisiblek TWRP and it opens properly will I then be able to restore the backups created with TWRP 2.8.7.1?
If that's the case, I need to find a tutorial on installing TWRP manually via ADB, right? I usually install TWRP via TWRP Manager.

bibbin said:
Thank for the quick response. No, I don't have USB-OTG inserted. It is using TWRP 2.8.7.1. No, I haven't tried installing the version you mentioned. What I did do was attempt to flash the pre-installed TWRP 2.8.1.0 via MOTO X TOOLKIT. It failed. I'm not very experienced at using ADB manually. As I mentioned, I've been reluctant to flash another ROM (custom or stock) because I don't want to get stuck with USB debugging inactive with no way to get in far enough to reactivate it.
---------- Post added at 04:32 PM ---------- Previous post was at 03:40 PM ----------
If I manage to install the invisiblek TWRP and it opens properly will I then be able to restore the backups created with TWRP 2.8.7.1?
If that's the case, I need to find a tutorial on installing TWRP manually via ADB, right? I usually install TWRP via TWRP Manager.
Click to expand...
Click to collapse
That's interesting, the TWRP Manager has never worked correctly for me although it's been a long time since I've tried it.
To flash manually, you actually need fastboot which is usually installed along with adb. If you open a command window, and type in fastboot and it runs, the rest is pretty easy. If it doesn't run, this thread has the 15 second ADB/Fastboot installer, select to install it system-wide: http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Download the recovery image, rename the file to twrp.img, then open a command window in the folder where you downloaded it (type cmd then Enter in the address line at the top of the folder window.)
When the command window is open and the phone is in bootloader mode and connected to the computer with the USB cable, enter the command "fastboot device" (without the quotes) If everything is working it will list the serial number of your phone.
Then enter "fastboot flash recovery twrp.img" (without the quotes) to start the flashing process, ignore the size mismatch message. It will only take a few seconds to complete.
Use the volume down key to highlight recovery, then volume up to select it. Hopefully TWRP will boot up and you'll be good to go!

Well, reinstalling TWRP didn't fix it. Thoughts? Anyone?

bibbin said:
Well, reinstalling TWRP didn't fix it. Thoughts? Anyone?
Click to expand...
Click to collapse
Reflash stock rom from fastboot.
Sent from my XT1095 using Tapatalk

UPDATE: Thanks all. Well, after fiddling around with various methods of reinstalling TWRP, I managed to get it reinstalled and all is back to normal now.

[6.0.1][STOCK][ROOT] Android one boot img for root

Files are in this link http://forum.turkdevs.com/konu-root-android-6-0-6-0-1-calisan-root-yontemi.html?pid=62642#pid62642
This method will work on 6.0 and 6.0.1
Extract files in adb folder
Enable usb debugging and oem lock
Open adb on your PC and execute "adb reboot bootloader"
Execute "fastboot flash boot newboot.img"
Execute "fastboot boot recovery-twrp.img"
Flash supersu via twrp and reboot system.
Thanks t_sasak for editing boot.img in TurkDevs Forums

nhmanas said:
Files are in this link http://forum.turkdevs.com/konu-root-android-6-0-6-0-1-calisan-root-yontemi.html?pid=62642#pid62642
This method will work on 6.0 and 6.0.1
Extract files in adb folder
Enable usb debugging and oem lock
Open adb on your PC and execute "adb reboot bootloader"
Execute "fastboot flash boot newboot.img"
Execute "fastboot boot recovery-twrp.img"
Flash supersu via twrp and reboot system.
Thanks t_sasak for editing boot.img in TurkDevs Forums
Click to expand...
Click to collapse
I thought i was able to successfully root my phone but after flashing SuperSU using TWRP i get a bootloop. HELP please!
Phone: Cherry Mobile One G1
OS: Android 6.0 Marshmallow
Build No: MRA58Y

Its working. THANKS!

PineappleOwl said:
Its working. THANKS!
Click to expand...
Click to collapse
what's your mobile phone?

kiksilog said:
what's your mobile phone?
Click to expand...
Click to collapse
Cherry Mobile G1 of Philippines

I haven't tried yet. I'm going to flash this today. People in TurkDevs developed and they're successful
Tengri biz menen

ricosuavehhh said:
I thought i was able to successfully root my phone but after flashing SuperSU using TWRP i get a bootloop. HELP please!
Phone: Cherry Mobile One G1
OS: Android 6.0 Marshmallow
Build No: MRA58Y
Click to expand...
Click to collapse
Did you unlock bootloader ? It has to be unlocked.

Yes i did enable OEM unlock bootloader in Developer Options

Choose correct boot file
ricosuavehhh said:
Yes i did enable OEM unlock bootloader in Developer Options
Click to expand...
Click to collapse
enable OEM unlock bootloader in Developer Options
enable USB Debugging Mode in Developer Options
unlock bootloder with "fastboot oem unlock-go" command
choose correct boot file (6.0.1 MMB29K or 6.0.0 MRA58Y)
you can find that files on first post link
---------- Post added at 08:17 PM ---------- Previous post was at 07:50 PM ----------
ricosuavehhh said:
Yes i did enable OEM unlock bootloader in Developer Options
Click to expand...
Click to collapse
what happend ?

cgtylpr said:
enable OEM unlock bootloader in Developer Options
enable USB Debugging Mode in Developer Options
unlock bootloder with "fastboot oem unlock-go" command
choose correct boot file (6.0.1 MMB29K or 6.0.0 MRA58Y)
you can find that files on first post link
---------- Post added at 08:17 PM ---------- Previous post was at 07:50 PM ----------
what happend ?
Click to expand...
Click to collapse
Thanks! i'll check if i did download the correct boot file

ricosuavehhh said:
Thanks! i'll check if i did download the correct boot file
Click to expand...
Click to collapse
Careful! Oem-unlock go command will wipe everything on your device including internal sd
Tengri biz menen

nhmanas said:
Careful! Oem-unlock go command will wipe everything on your device including internal sd
Tengri biz menen
Click to expand...
Click to collapse
You're right.

ricosuavehhh said:
You're right.
Click to expand...
Click to collapse
Problem solved ?

cgtylpr said:
Problem solved ?
Click to expand...
Click to collapse
I'm currently flashing boot.img, recovery.img... will update you later.

I flashed yesterday. It works like charm. And Xposed is working flawless
Tengri biz menen

nhmanas said:
I flashed yesterday. It works like charm. And Xposed is working flawless
Tengri biz menen
Click to expand...
Click to collapse
Nice

Thanks. Successfully flashed boot and superSU, running Xposed too, trying out modules. Thank you very much, OP.
Cherry Mobile One G1
MM 6.0.1

Just out of interest, what do your guys do, when the next OTA-Updates arrive...?

Xposed on mm causes random reboot.. Maybe because of modules I don't know
Tengri biz menen

vel_tins said:
Just out of interest, what do your guys do, when the next OTA-Updates arrive...?
Click to expand...
Click to collapse
Nothing these people who flashed twrp and rooted the phone can do when a new OTA arrives, except whine and hope that somebody is able to capture the OTA file and transform it to a twrp-flashable zip. :crying:

Help - forgot to install ota after downloading

I have a oneplus 6. I messed up today and downloaded the OTA but FORGOT to install it before flashing magisk to the backup slot and rebooted. Is there any way i can go back to the original partition? Am I screwed?

Nexus311 said:
I have a oneplus 6. I messed up today and downloaded the OTA but FORGOT to install it before flashing magisk to the backup slot and rebooted. Is there any way i can go back to the original partition? Am I screwed?
Click to expand...
Click to collapse
Dirty flash the ROM zip via TWRP. It should get you booting up into OOS.
Sent from my MotoG3-TE using Tapatalk

I dont have twrp. can i boot to the first partition with fastboot?

Nexus311 said:
I have a oneplus 6. I messed up today and downloaded the OTA but FORGOT to install it before flashing magisk to the backup slot and rebooted. Is there any way i can go back to the original partition? Am I screwed?
Click to expand...
Click to collapse
BTW, how did you "forget" to install it? I have a 6T & all I get is a "Download & Install" option. It doesn't ask me when to install it. I'm new to Seamless Updates thing. Is there a toggle to disable the immediate installation after downloading?
Sent from my MotoG3-TE using Tapatalk
---------- Post added at 09:45 PM ---------- Previous post was at 09:44 PM ----------
Nexus311 said:
I dont have twrp. can i boot to the first partition with fastboot?
Click to expand...
Click to collapse
Ugh I'm not sure regarding it. You can just hotboot TWRP via fastboot & flash it. Or maybe, try sideloading the ROM zip via adb sideload to Stock Recovery.
Sent from my MotoG3-TE using Tapatalk

it downloaded the damn ota in the background in its own on wifi, i usually download then install it, it showed as already downloaded but didnt think to install it. it looked different and totally forgot.

i cant even get adb or fastboot to see the phone

Nexus311 said:
i cant even get adb or fastboot to see the phone
Click to expand...
Click to collapse
Have you installed the device drivers? Fastboot mode should be easily detected.
Sent from my #FlagshipKiller6T using Tapatalk

yeah, this powershell nonsense i dont know anything about, it told me i had to type .\fastboot. then i was able to see my device and ran fastboot --set-active=a
all good now. thanks so much

Nexus311 said:
yeah, this powershell nonsense i dont know anything about, it told me i had to type .\fastboot. then i was able to see my device and ran fastboot --set-active=a
all good now. thanks so much
Click to expand...
Click to collapse
If you're on a Mac, then it should be "." AFAIK. On Windows, there's no need for it. But Powershell is a Windows thing
Sent from my #FlagshipKiller6T using Tapatalk

TWRP with encryption support

Is there some TWRP version with encryption support? Mine shows just random empty folders, doesn't ask for encryption key.

kokesh said:
Is there some TWRP version with encryption support? Mine shows just random empty folders, doesn't ask for encryption key.
Click to expand...
Click to collapse
Yes maunofrio

Like said above, always use the most recent mauronofrio's TWRP.

Thanks! Got the latest version, but now I am facing an issue with Fastboot. I'm in fastboot mode, with drivers installed, but it just keeps saying Waiting for the device. I have all drivers installed and ADB works fine when the phone is on. I didn't find the fastboot device in Device manager, when connected on any USB port.

kokesh said:
Thanks! Got the latest version, but now I am facing an issue with Fastboot. I'm in fastboot mode, with drivers installed, but it just keeps saying Waiting for the device. I have all drivers installed and ADB works fine when the phone is on. I didn't find the fastboot device in Device manager, when connected on any USB port.
Click to expand...
Click to collapse
On adb debugging
---------- Post added at 10:19 AM ---------- Previous post was at 10:17 AM ----------
Or you can install new twrp in old

EpickBroVlad said:
On adb debugging
---------- Post added at 10:19 AM ---------- Previous post was at 10:17 AM ----------
Or you can install new twrp in old
Click to expand...
Click to collapse
What I've done:
Booted old TWRP
Pushed new twrp.img into /tmp
Flashed image via old twrp
Flashed new OTA
Couldn't install magisk (system read only)
After reboot twrp overwritten by stock recovery
Fastboot works only with original xiaomi cable for some reason
Flashed twrp via fastboot. Didn't stick, stock recovery comes up all the time.
Fastboot boot twrp.img starts new twrp, flashed magisk via that one.
Now all is fine.

kokesh said:
What I've done:
Booted old TWRP
Pushed new twrp.img into /tmp
Flashed image via old twrp
Flashed new OTA
Couldn't install magisk (system read only)
After reboot twrp overwritten by stock recovery
Fastboot works only with original xiaomi cable for some reason
Flashed twrp via fastboot. Didn't stick, stock recovery comes up all the time.
Fastboot boot twrp.img starts new twrp, flashed magisk via that one.
Now all is fine.
Click to expand...
Click to collapse
Install it twice

EpickBroVlad said:
Install it twice
Click to expand...
Click to collapse
I did flash it twice in a row. And after that thrice. Didn't stick.