I've relocked my wileyfox swift 2 and now i can't boot my phone anymore - Wileyfox Swift 2 Questions & Answers

I had been flashing custom roms and other files like SuperSU which all went to plan and I decided I was happy with my rom so I decided to disable OEM unlocking to get rid of the startup message. It didn't work so I went into adb and entered
Code:
fastboot oem lock
but I forgot to enable oem unlocking in developer settings and now I have a hard-bricked phone without any recovery or system, only fastboot. I don't have enough money to get it fixed for me so I'll have to do it myself but I don't know how.

You are not alone, I'm in the same situation, no system, no recovery, only fastboot with locked bootloader and nobody is willing to repair it.

AxorPL said:
You are not alone, I'm in the same situation, no system, no recovery, only fastboot with locked bootloader and nobody is willing to repair it.
Click to expand...
Click to collapse
Well I've just sent it to a reparation centre and i'm gonna wait :fingers-crossed:

ALamX_14 said:
Well I've just sent it to a reparation centre and i'm gonna wait :fingers-crossed:
Click to expand...
Click to collapse
Did you have any joy?

Related

Nightmare, help please :)

Hi, I literally opened the nexus 9 out of the box, powered it on & after choosing a wifi network it began updating, the device crashed during this update and now it won't boot! I've tried & searched for everything, anyone have any ideas?
Booting to recovery with HW buttons, wiping cache/userdata/factory reset - Nada!
Can boot into fastboot, no permission to flash as oem unlock is disabled!
I cant get into the tablet to unlock fastboot oem unlock within devOpitons or usb debugging etc, (com.android.phone has stopped on boot) black screen indefinitely.
I can't flash any images while it is locked
surely there must be a simple method?
desperate here
Return it
I'd just return it. I'm no expert, but I'd seek a way to avoid the update during setup and try to postpone it until you unlock developer options and OEM unlock. I'm not sure how you'd bypass the update during setup, but you're in the right place if it's possible.
VermontKindBud said:
I'd just return it. I'm no expert, but I'd seek a way to avoid the update during setup and try to postpone it until you unlock developer options and OEM unlock. I'm not sure how you'd bypass the update during setup, but you're in the right place if it's possible.
Click to expand...
Click to collapse
Hmm, its one of works, just bought bulk amount of them. surely it can't be stuck in an unescapable cycle?
syko9 said:
Hmm, its one of works, just bought bulk amount of them. surely it can't be stuck in an unescapable cycle?
Click to expand...
Click to collapse
Certainly it can. If it started to install the 5.0.2 OTA, there have been a lot of bricks.
cam30era said:
Certainly it can. If it started to install the 5.0.2 OTA, there have been a lot of bricks.
Click to expand...
Click to collapse
Alright thanks for the info, guess it shall be replaced thanks.
syko9 said:
Alright thanks for the info, guess it shall be replaced thanks.
Click to expand...
Click to collapse
Welcome. And FWIW: there's a button for that.
If I remember correctly you can still flash the stock images even with the boot loader locked. Its only custom images that google will not accept unless you unlock boot loader.
Ripx88 said:
If I remember correctly you can still flash the stock images even with the boot loader locked. Its only custom images that google will not accept unless you unlock boot loader.
Click to expand...
Click to collapse
Bootloader has to be unlocked to "fastboot flash" anything.
You can sideload an OTA with a locked bootloader, but you have to be able to access recovery.
cam30era said:
Bootloader has to be unlocked to "fastboot flash" anything.
You can sideload an OTA with a locked bootloader, but you have to be able to access recovery.
Click to expand...
Click to collapse
Ah ok gotcha. My apologizes, I thought I heard somewhere you could. Thank you for the correction.
Ripx88 said:
Ah ok gotcha. My apologizes, I thought I heard somewhere you could. Thank you for the correction.
Click to expand...
Click to collapse
No problem. That's how we learn.
cam30era said:
No problem. That's how we learn.
Click to expand...
Click to collapse
Indeed I'm still new to nexus devices. I've been flashing on Samsung devices for years so I'm still stuck in my Odin ways. Just got the N9 less then a week ago. The whole fastboot thing was foreign at first but I'm getting there lol. Thank you again.

Bootloader

I've recently unlocked my bootloader and I wanted to re lock it. Well, I couldn't find any thread about this and I thought it would be good to open one. My question is obviously how to re lock the bootloader in Xiaomi Redmi Note 3 Snapdragon.
Xristomania said:
I've recently unlocked my bootloader and I wanted to re lock it. Well, I couldn't find any thread about this and I thought it would be good to open one. My question is obviously how to re lock the bootloader in Xiaomi Redmi Note 3 Snapdragon.
Click to expand...
Click to collapse
simply flash any official fastboot ROM using miflash.
sanjib734 said:
simply flash any official fastboot ROM using miflash.
Click to expand...
Click to collapse
With edl right?
sanjib734 said:
simply flash any official fastboot ROM using miflash.
Click to expand...
Click to collapse
Did it with the EDL and now i got hard brick. Now I am stuck at mi logo not even bootlooping and i can access fastboot mode but have no permision to do anything in there and cant flash from recovery. Any solution about this?
Xristomania said:
Did it with the EDL and now i got hard brick. Now I am stuck at mi logo not even bootlooping and i can access fastboot mode but have no permision to do anything in there and cant flash from recovery. Any solution about this?
Click to expand...
Click to collapse
Did you use unofficial bootloader unlock? If you did, you're really really f***ed right now. The only way to fix this is to physically open the device, unscrew the motherboard, plug in the usb and use a metal object to connect the two "testpoints", which will force the phone into edl mode.
justinxfan said:
Did you use unofficial bootloader unlock? If you did, you're really really f***ed right now. The only way to fix this is to physically open the device, unscrew the motherboard, plug in the usb and use a metal object to connect the two "testpoints", which will force the phone into edl mode.
Click to expand...
Click to collapse
I know about the testpoint but thank god i did wait for the unlock aproval.
Xristomania said:
I know about the testpoint but thank god i did wait for the unlock aproval.
Click to expand...
Click to collapse
In that case of official unlock, guess you can take to service center and get it repaired?
For unofficial unlock, there is simple way to lock bootloader by putting back original "emmc_appsboot.mbn" from fastboot rom.
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
Xristomania said:
I know about the testpoint but thank god i did wait for the unlock aproval.
Click to expand...
Click to collapse
You used official unlocked and the phone still bricked?
mGforCe said:
In that case of official unlock, guess you can take to service center and get it repaired?
For unofficial unlock, there is simple way to lock bootloader by putting back original "emmc_appsboot.mbn" from fastboot rom.
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
Click to expand...
Click to collapse
Greece doesn't have a service center for xiaomi phones. Yeap, this sucks.
justinxfan said:
You used official unlocked and the phone still bricked?
Click to expand...
Click to collapse
Yep, still bricked. Hard Bricked. I have used tespoint again but it was actually hard to trigger it because it caused phone to restart normally instead of going to edl.
When I tried to EDL Flash my phone normally when i had access to android, I got and max memory something problem in Mi Flash and when i tried again it sent a hello package to my phone and then it said catastrophic failure. So, don't know what that actually means and I hope not what it actually says. However i still have access to fastboot mode and recovery mode but i found out that I actually have locked bootloader after flashing this "emmc_appsboot.mbn" and had the phone alive in chinese dev rom and then i wanted to roll back to global stable via edl and got brick. Sadly I do not have access to this test mode where you test your phone's sensors, display and more.
Xristomania said:
When I tried to EDL Flash my phone normally when i had access to android, I got and max memory something problem in Mi Flash and when i tried again it sent a hello package to my phone and then it said catastrophic failure. So, don't know what that actually means and I hope not what it actually says. However i still have access to fastboot mode and recovery mode but i found out that I actually have locked bootloader after flashing this "emmc_appsboot.mbn" and had the phone alive in chinese dev rom and then i wanted to roll back to global stable via edl and got brick. Sadly I do not have access to this test mode where you test your phone's sensors, display and more.
Click to expand...
Click to collapse
Hey, you can go into EDL mode?
If yes, why don't you flash the Fastboot ROM - Global one if you don't want CHinese one
Refer this post for basic steps.
http://forum.xda-developers.com/showpost.php?p=66962198&postcount=7
mGforCe said:
Hey, you can go into EDL mode?
If yes, why don't you flash the Fastboot ROM - Global one if you don't want CHinese one
Refer this post for basic steps.
http://forum.xda-developers.com/showpost.php?p=66962198&postcount=7
Click to expand...
Click to collapse
I might can with the testpoint method. Although I can not boot into android.
Xristomania said:
I might can with the testpoint method. Although I can not boot into android.
Click to expand...
Click to collapse
Suggest trying @Rajdip's thread here
http://forum.xda-developers.com/redmi-note-3/how-to/unbricking-redmi-note3-hardbrickhs-usb-t3351325
EDL
mGforCe said:
Suggest trying @Rajdip's thread here
http://forum.xda-developers.com/redmi-note-3/how-to/unbricking-redmi-note3-hardbrickhs-usb-t3351325
Click to expand...
Click to collapse
Just got into edl mode with testpoint and flashed successfully global firm. I'll charge it fully and the find out if it actually works.
Xristomania said:
Just got into edl mode with testpoint and flashed successfully global firm. I'll charge it fully and the find out if it actually works.
Click to expand...
Click to collapse
Great! Happy to note that your phone is back.. If flash has been successful then it will work.
testpoint is risky and requires expertise right?
mGforCe said:
Great! Happy to note that your phone is back.. If flash has been successful then it will work.
testpoint is risky and requires expertise right?
Click to expand...
Click to collapse
Actually it is not that difficult but it is extremely tricky since if you press only the left one test point it will just reboot. You need to touch them at the same time. Although you'll need to be accommodated with electronics since they are sensitive.
mGforCe said:
Great! Happy to note that your phone is back.. If flash has been successful then it will work.
testpoint is risky and requires expertise right?
Click to expand...
Click to collapse
Weirdly enough, it shows battery sign when charging but button do not seem to respond for a weird reason. I'll check cables.
Oh god yes
Xristomania said:
Weirdly enough, it shows battery sign when charging but button do not seem to respond for a weird reason. I'll check cables.
Click to expand...
Click to collapse
I had a little heart attack because I thought That i had cut the Button Cable during the flash process but THANK GOD it was right underneath the motherboard and IT NOW WORKS. YES I AM IN MIUI GLOBAL. THANK GOD. Just for you to know, every failed bootloader unlock on any smartphone is equal to several heart attacks.

CanĀ“t unlock Bootloader

Hello,
situation ist this:
Cyanogen Recovery is installed and there is no rom on the phone. But it won't install a new one through apply update. So I tried installing twrp through fast boot. But it failed with:
FAILED (remote: Device not unlocked cannot flash or erase)
So i tried to unlock it which gave me:
FAILED (remote: oem unlock is disabled)
oem devices gave me tampered = false and unlocked = false
What can I do.
Would appreciate help
Morishno
Flash stock recovery and try unlock again.
Dumb Question but how exactly do I do that?
Just flash it via fast boot? And where do i get it?
Morishno said:
Dumb Question but how exactly do I do that?
Just flash it via fast boot? And where do i get it?
Click to expand...
Click to collapse
You can get it from oneplus downloads section, if you cant find it ask me... Yes you have to flash official stock recovery through fastboot
Exodusche said:
Flash stock recovery and try unlock again.
Click to expand...
Click to collapse
cva_kabil said:
You can get it from oneplus downloads section, if you cant find it ask me... Yes you have to flash official stock recovery through fastboot
Click to expand...
Click to collapse
Not really, OP reports that the unlock command gave him FAILED (remote: oem unlock is disabled)
Hey OP, did you enable OEM Unlocking from Developer options ?
Joshwin Aranha said:
Not really, OP reports that the unlock command gave him FAILED (remote: oem unlock is disabled)
Hey OP, did you enable OEM Unlocking from Developer options ?
Click to expand...
Click to collapse
If not is there any other way?
cva_kabil said:
If not is there any other way?
Click to expand...
Click to collapse
I'm sorry but i do not know any other method that works without flipping that switch in Developer Options.
Joshwin Aranha said:
I'm sorry but i do not know any other method that works without flipping that switch in Developer Options.
Click to expand...
Click to collapse
You dont need to be sorry, thats okay i jus asked... Maybe OP didnt enable oem unlocking.
I didnt enable oem unlocking because it wasnt necessary. The device was unlocked and twrp and cyanogenmod were installed. But somehow cyanogen recovery was installed. Super user was away and I tried to reinstall it. Not knowing the recovery had changed I chose twrp/cwm to install it what resulted in a boot loop. No problem I thought just flash a ROM which didn't worked. No problem just flash a proper recovery it didn't worked. And somehow the device is locked again..
Sorry I was little brief when I said flash stock recovery. I believe if you revert back completely stock you can start the process from the beginning again. That would mean fastboot flash stock recovery then any firmware of OnePlus X. I'm not sure how a bootloader can relock itself.
Exodusche said:
Sorry I was little brief when I said flash stock recovery. I believe if you revert back completely stock you can start the process from the beginning again. That would mean fastboot flash stock recovery then any firmware of OnePlus X. I'm not sure how a bootloader can relock itself.
Click to expand...
Click to collapse
But I couldn't flash twrp.. Is it possible to flash the stock recovery with a locked boot loader? I don't have access to the phone at the moment and i want to gather as much information possible thats why i'm asking
Morishno said:
But I couldn't flash twrp.. Is it possible to flash the stock recovery with a locked boot loader? I don't have access to the phone at the moment and i want to gather as much information possible thats why i'm asking
Click to expand...
Click to collapse
I'm not sure but this has been addressed many times. Comb the threads you will find the information you need.
Exodusche said:
I'm not sure but this has been addressed many times. Comb the threads you will find the information you need.
Click to expand...
Click to collapse
Found a hard brick guide. You mean that?
So I just remembered something was able to help someone else with a similar issue. If you can boot Into something and your rooted download the app Rashr. With it you can flash stock recovery and be back in business.
The problem is i dont have anything to Boot
//UPDATE: So I tried booting with fastboot boot but it said cannot boot device isn't unlocked.
Edited
So i managed to save the Phone using the Hard Brick Guide. Thanks everyone!
Thank goodness for the hard brick guide. ?
Exodusche said:
I think your gonna have to go through the hard bricked guide.
Click to expand...
Click to collapse
Yeah i did that and it worked thank you

Flash factory images over a locked bootloader? HTC and Google both say it's possible.

So, long story short, I recently bought a Nexus 9 from ebay which arrived with factory reset protection.
I have spoken to both Google and HTC about the situation and both were of no real help except for saying a few things outright between them to give me good enough reason to believe one of two things.
That 1 - it is possible to flash factory images over a device with a locked bootloader
or 2 - it is possible to unlock the bootloader without having access to developer settings
Anyone have any experience with either of these possibilities?
https://developers.google.com/android/ota
Full OTA Images can be flashed onto devices with locked boot loaders.
You need to boot into recovery and select sideload update.
Yeah, I know how to do that, but that only goes for updates, doesn't it? I tried to sideload a previous build onto the tablet but it failed the procedure, so it doesn't really solve the issue and if I flash a more recent update I still get FRP :/ If I wanted to revert back to the 7.0, or even marshmallow, would that be possible? Or does that require an unlocked bootloader?
enriquejones666 said:
https://developers.google.com/android/ota
Full OTA Images can be flashed onto devices with locked boot loaders.
You need to boot into recovery and select sideload update.
Click to expand...
Click to collapse
Yeah, I know how to do that, but that only goes for updates, doesn't it? I tried to sideload a previous build onto the tablet but it failed the procedure, so it doesn't really solve the issue and if I flash a more recent update I still get FRP :/ If I wanted to revert back to the 7.0, or even marshmallow, would that be possible? Or does that require an unlocked bootloader?
BigDomTheFirst said:
Yeah, I know how to do that, but that only goes for updates, doesn't it? I tried to sideload a previous build onto the tablet but it failed the procedure, so it doesn't really solve the issue and if I flash a more recent update I still get FRP :/ If I wanted to revert back to the 7.0, or even marshmallow, would that be possible? Or does that require an unlocked bootloader?
Click to expand...
Click to collapse
Those are full ota images, same as factory image. Meaning full package.
BigDomTheFirst said:
Yeah, I know how to do that, but that only goes for updates, doesn't it? I tried to sideload a previous build onto the tablet but it failed the procedure, so it doesn't really solve the issue and if I flash a more recent update I still get FRP :/ If I wanted to revert back to the 7.0, or even marshmallow, would that be possible? Or does that require an unlocked bootloader?
Click to expand...
Click to collapse
Ah yes, now I see your predicament. Unfortunately, there is no "there" there. You do need an unlocked bootloader to wipe the system clean with a factory image, and as you noted, the Full OTA Image will recover you from a system that won't boot, but it won't get rid of FRP.
enriquejones666 said:
Ah yes, now I see your predicament. Unfortunately, there is no "there" there. You do need an unlocked bootloader to wipe the system clean with a factory image, and as you noted, the Full OTA Image will recover you from a system that won't boot, but it won't get rid of FRP.
Click to expand...
Click to collapse
Exactly Hence my questions as to how do the manufacturers wipe everything and flash the new image without unlocking the bootloader? Or will it always be a trade secret?...... Hmmmm
BigDomTheFirst said:
Exactly Hence my questions as to how do the manufacturers wipe everything and flash the new image without unlocking the bootloader? Or will it always be a trade secret?...... Hmmmm
Click to expand...
Click to collapse
did we ever fix this? my bootloader is locked and no os installed. Was trying to return to factory and went thru all the flashing steps successfully then at the end locked the bootloader. Now tablet says "for development purposes only not for production use" and boots back to fastboot. It will not reboot at all
Uncleheff said:
did we ever fix this? my bootloader is locked and no os installed. Was trying to return to factory and went thru all the flashing steps successfully then at the end locked the bootloader. Now tablet says "for development purposes only not for production use" and boots back to fastboot. It will not reboot at all
Click to expand...
Click to collapse
Never found out how they do this.... are you able to boot in to recovery? if you can do that you may be able to flash a recovery OTA through 'apply update from ADB'. Worth a shot
Uncleheff said:
did we ever fix this? my bootloader is locked and no os installed. Was trying to return to factory and went thru all the flashing steps successfully then at the end locked the bootloader. Now tablet says "for development purposes only not for production use" and boots back to fastboot. It will not reboot at all
Click to expand...
Click to collapse
If up dont mind my asking how did it get that way by just locking the bootloader? I was just about to flash stock and lock on my volantis, then read this...?
Bryanx86 said:
If up dont mind my asking how did it get that way by just locking the bootloader? I was just about to flash stock and lock on my volantis, then read this...?
Click to expand...
Click to collapse
definitely don't lock your bootloader. That is a horrible move and serves no purpose
madbat99 said:
definitely don't lock your bootloader. That is a horrible move and serves no purpose
Click to expand...
Click to collapse
I actually reflashed last factory stock image and relocked without issue. It is a horrible move, I agree...I already miss root, but it suits the purpose. Thanks for your reply.
Bryanx86 said:
I actually reflashed last factory stock image and relocked without issue. It is a horrible move, I agree...I already miss root, but it suits the purpose. Thanks for your reply.
Click to expand...
Click to collapse
it's only a bad move if you make a mistake and can't repair it because your bootloader is now locked. But if it goes well then you're all set.

"This is a development device not intended for production use"?

anybody seen this error? I was trying to revert back to stock. Once it rebooted, this happen. I found an old thread but only resolution was to warranty it. Of course this device is old so no more warranty. wanted to see if theres other solutions before i dump it on ebay for parts..
thanks
NJ_RAMS_FAN said:
anybody seen this error? I was trying to revert back to stock. Once it rebooted, this happen. I found an old thread but only resolution was to warranty it. Of course this device is old so no more warranty. wanted to see if theres other solutions before i dump it on ebay for parts..
thanks
Click to expand...
Click to collapse
You tried to relock the bootloader didn't you? Usually not a good idea. Is it not booting anymore? If it boots go in developer options and tick the allow OEM unlocking back to on. And then see if unlocking the bootloader changes it.
madbat99 said:
You tried to relock the bootloader didn't you? Usually not a good idea. Is it not booting anymore? If it boots go in developer options and tick the allow OEM unlocking back to on. And then see if unlocking the bootloader changes it.
Click to expand...
Click to collapse
yea.. smh... i actually got it out of that bootloop but i can't unlock bootloader. ill let it be. its running lineageos... i tried these steps and it actually worked if anybody has this issue...
https://forum.xda-developers.com/showpost.php?p=77355001&postcount=6

Categories

Resources