Hello Guys,
First of all i want to indicate that i'm a junior on this forum, i'm not used to forums and i'm French, so i apologize for my English...
Then i want to say that i read a lot on this forum, and you're job is amazing. It is why i have to post my request to you. There is my first post, thanks a lot by advance :
So, i recently acquired a Crosscall Core X4 because i used to broke all my smartphones. The thing is : i dont really need a smartphone... The only thing that maked me the idea to buy a smartphone, is to use it for my training with Kali Linux. I want to install it by termux, but all programs i needs needs roots access.
I already figure it out how can i do it but my problem is here : I cant unlock my bootloader... Fastboot systematically respond : FAILED (remote: Command not allowed) to "fastboot oem unlock" and "fastboot flashing unlock"
Before you ask, "fastboot devices" works well and yes i activate "OEM unlock" in dev options on android.
I have already ask Crosscall for help (perhaps they have a KEY : "fastboot oem unlock "key" ", or a specific command for fastboot) but they dont want to ear "root" and "unlock"... They laugh on me and says to me that i don't need a rooted smartphone -_-
Here is why i need help from reals devellopers like XDA-Devellopers to know what can i do with this issue.
Thank you a lot to anyone who keep the time to help me.
Arcalienator said:
Hello Guys,
First of all i want to indicate that i'm a junior on this forum, i'm not used to forums and i'm French, so i apologize for my English...
Then i want to say that i read a lot on this forum, and you're job is amazing. It is why i have to post my request to you. There is my first post, thanks a lot by advance :
So, i recently acquired a Crosscall Core X4 because i used to broke all my smartphones. The thing is : i dont really need a smartphone... The only thing that maked me the idea to buy a smartphone, is to use it for my training with Kali Linux. I want to install it by termux, but all programs i needs needs roots access.
I already figure it out how can i do it but my problem is here : I cant unlock my bootloader... Fastboot systematically respond : FAILED (remote: Command not allowed) to "fastboot oem unlock" and "fastboot flashing unlock"
Before you ask, "fastboot devices" works well and yes i activate "OEM unlock" in dev options on android.
I have already ask Crosscall for help (perhaps they have a KEY : "fastboot oem unlock "key" ", or a specific command for fastboot) but they dont want to ear "root" and "unlock"... They laugh on me and says to me that i don't need a rooted smartphone -_-
Here is why i need help from reals devellopers like XDA-Devellopers to know what can i do with this issue.
Thank you a lot to anyone who keep the time to help me.
Click to expand...
Click to collapse
Hi,
i think i can fix this but can you send me copy of the firmware you are running?
Like i need the modem/aboot etc...
Best Regards!
Thargorsson said:
Hi,
i think i can fix this but can you send me copy of the firmware you are running?
Like i need the modem/aboot etc...
Best Regards!
Click to expand...
Click to collapse
Tanks you for your help, but i cant find the firmware on the web and i cant extract it because my bootloader is locked... Maybe have you an other idea?
Any one ever rooted any Crosscall ?
Hello, got a CrossCall Core M4, and after some searchs, I could not find any public witness about successfull root for any device from this brand. # fastboot oem unlock ... FAILED (remote: unknown command) finished. total time: 0.001s And...
forum.xda-developers.com
I have dug very deep in Google for rooting my Crosscall Core M4 and X4, and I have found no success story about it. I have found fake forums, and fake tutos that, in short say "this command should do the job"; bot nobody ever stated "I have done it".
Arcalienator said:
I have already ask Crosscall for help (perhaps they have a KEY : "fastboot oem unlock "key" ", or a specific command for fastboot) but they dont want to ear "root" and "unlock"... They laugh on me and says to me that i don't need a rooted smartphone -_-
Click to expand...
Click to collapse
I can understand some brands refuse to help rooting, as long as they say they just refuse. HTC changed their minds in a fair way: "we help you rooting your phone, but you will loose waranty". This is a critical point for Crosscall, because they provide a 3y complete waranty, including battery; and from experience with HTC Sensation, a bad rooting can not only kill your battery, but also transform your phone in a literal bomb (or at least, if no literal explosion, produce heavy toxic fumes). I was luccky to know how to fix my Sensation without damaging my phone, but on the week that bad rooting kit was released, we counted over 12 phones that exploded over internet, and several undred dead batts.
But I agree, rooting a phone makes it soo much easier to use, flexible, and usefull.
For this reason, I will probably never bug Crosscall again. They have very good hardware features, but not having root is a huge issue.
Keep in mind that many brands that help rooting request you to wait 15 days after purchase before unlocking (xaomi IIRC).
Also spent a few hours searching for pre-rooted devices, and could not find any. My issue is that rooting takes time, and requires heavy tools I don't always have access to (I don't have Windows laptop; when rooting requires Windows, I need to wait a few days or weeks before I meet & borrow some Windows machine, and install softwares on it).
About crosscall, I had to send my M4 twice to repair; on the paper, it's quiet easy: put your IMEI on their website, and UPS comes to collect your phone. In practice, after I received it the second time, 4 screws were missing ... and, they refuse to send them to me over the post; I have to send them my phone a 3rd time ... what inclued a complete user data wipe, and several days to reinstall/reconfigure when I get it back. 4 srews implies spending 1 more week on software reconf because of lack of root.
I have found those screws on Ali.
Thargorsson said:
Hi,
i think i can fix this but can you send me copy of the firmware you are running?
Like i need the modem/aboot etc...
Best Regards!
Click to expand...
Click to collapse
hey...
i have trekker-x3 and i checked the aboot and found the code which normal code ( fastboot oem unlock-go) but didnt work.. if u need aboot or modem i can send u..
boot info;
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.008s]
finished. total time: 0.009s
t-mobile_mda said:
hey...
i have trekker-x3 and i checked the aboot and found the code which normal code ( fastboot oem unlock-go) but didnt work.. if u need aboot or modem i can send u..
boot info;
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.008s]
finished. total time: 0.009s
Click to expand...
Click to collapse
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
as we see this info it may accept;
fastboot flashing unlock
fastboot flashing unlock_critical
but didnt accept it.. maybe it can unlock with unlock.app..? like asus bootlaoder.?
Related
Delete
Warning! All your data will be lost.
It clears your data partition for security purposes
are u guys able to access stock recovery? wht key combination?
worked like a charme....
Ta.... used your fastboot package as the one in my android dir kept saying waiting for device..
all done!!!
That was simple cheers we have success : )
Sent from my HTC Hero using Tapatalk
Worked without any problem for me....
Is it just me, or does the USB driver refuse to work in Windows 7 64bit? It worked fine in 32bit, though.
I use Win7 x64 and tried on my Desire HD before uploading the .rar. The phone was detected successfully.
anyone know if this will work for Rogers SE ARC?
Try . If step 9 doesn't work then try debranding with Customized FW from here: http://forum.xda-developers.com/showthread.php?t=1033193
kyods said:
Is it just me, or does the USB driver refuse to work in Windows 7 64bit? It worked fine in 32bit, though.
Click to expand...
Click to collapse
yes my windows 7 64 bit having hard time. using my vista 32 bit works perfectly
Sent from my Xperia Arc
lollylost100 said:
Try . If step 9 doesn't work then try debranding with Customized FW from here: http://forum.xda-developers.com/showthread.php?t=1033193
Click to expand...
Click to collapse
Cant get past step 8, no go on the blue led so no fast boot. on orange branded piece of **** software lol
Try debranding, then post results.
punkmonkey1984 said:
Cant get past step 8, no go on the blue led so no fast boot. on orange branded piece of **** software lol
Click to expand...
Click to collapse
I'm surprised you can get past step 4 to be honest...
IMEIs are not registered for specific operators. Only part is the start which is used for SEUS detection. Branded devices will be able to receive their key, just won't be able to go into fastboot. I need someone to debrand their phone and check if fastboot is enabled after debranding.
lollylost100 said:
IMEIs are not registered for specific operators.
Click to expand...
Click to collapse
I'm not convinced of that but fair enough.
Personally, I'm having issues with the fastboot drivers for Win7 x64...
I'm sure that's how it is . Too much hassle + service centres can change phone's customization rendering such methods useless.
Try these drivers and report back: http://www.multiupload.com/0XZV1LXRVA
I can't quite bring myself believe that SE don't keep a record of which handsets are sold to whom and what network they're locked to.
Obviously, they're not cross-referencing against those records when issuing the unlocking keys but I'm sure they know.
Thank you for the drivers, I think they've done it...
Here's what it said on the command prompt:
Code:
C:\Users\[username]\Desktop\SE Unlock\fastboot>fastboot.exe -i 0x0fce getvar version
version: 0.3
finished. total time: 0.001s
C:\Users\[username]\Desktop\SE Unlock\fastboot>fastboot.exe -i 0x0fce oem unlock 0x[my key]
...
(bootloader) Unlock phone requested
(bootloader) Erasing block 0x00000d00
(bootloader) Erasing block 0x00000e00
(bootloader) Erasing block 0x00000f00
(bootloader) Erasing block 0x00001000
(bootloader) Erasing block 0x00001100
(bootloader) Erasing block 0x00001200
(bootloader) Erasing block 0x00001300
(bootloader) Erasing block 0x00001400
(bootloader) Erasing block 0x00001500
(bootloader) Erasing block 0x00001600
(bootloader) Erasing block 0x00001700
(bootloader) Erasing block 0x00001800
OKAY [ 4.170s]
finished. total time: 4.170s
C:\Users\[username]\Desktop\SE Unlock\fastboot>
That's it . I'll update first post with x64 drivers.
Hello
Due to an issue of loss of storage on my HTC LEGEND, I decided to switch to root and supporting the solution DATA2EXT. That's how I followed this tutorial ( can't post the link, so it's the tutorial from FRAndroid, sticked on the HTC LEGEND part for root). I'm stuck at 2. ROOT, when I start the step1-windows.bat, my phone displays an HTC logo on black and ... nothing happens.
thank you in advance for your help
Meanwhile, my phone is in a very old version, which is not very pleasant to quotidient: /
thanks
what does it show on your pc... i mean the commands on terminal window...
what's your software version?
if it's 1.31 or lower it's ok... maybe u haven't made gold card properly
On my comp :
Legend Root Step 1
Erasing cache and rebooting in RUU mode...
erasing 'cache'... OKAY
... OKAY
About to start flash...
< waiting for device >
sending 'zip' (121756 KB)... OKAY
writing 'zip'...
on my phone :
a htc logo with a black background
i'm on a 1.31 & i check my gold card few mins ago
thanks for help me
Ok, so i pass the step1-windows.bat
now... another problem, when i go to recovery mode, adb didn't find my device ... : /
adb devices return nothing
when i kill & start adb, it's the same .
Make sure you have the right version of HTC sync installed.
http://forum.xda-developers.com/showthread.php?t=894465
Has a link to the corect version
I reply to french forum.
Good luck
Thanks all for your answer
yes i'm sure i got the good htc Sync.
When i'm in recovery mode, nothing is recognize as ADB or something like that. I think the problem is here ..
do you know how run it ?
thanks for all your answer
no idea ?
plz help me, this gonna take my head
Maybe this helps. Sounds like USB brick.
You must be rooted to try the following, it seems you can't write to mtd0 without root.
Click to expand...
Click to collapse
i'm not rooted : /
i'm still trying this. thanks for the info
[edit] i can follow this tutorial cause i haven't permission
I have the same problem.. No solution found yet...
Hi
I get the chinese version of oneplus 2 and it is running HydrogenOS. I don't like all the chinese bloatware so I decided to install oxygenOS, the one linked here :http://forum.xda-developers.com/one...s-oneplus-files-drivers-roms-toolbox-t3178267
But I try to unlock the bootloader, I get this message :
FAILED (remote : oem unlock is disabled)
Any clue on how unlock the boot loader.
Thanks a lot.
Nabolito.
I find out, I have to enable oem unlock in developpers options. Sorry for that. I google it.
So I am continuing the adventure. next step
Hi have you found anny solution?
Yes, as I said I enable it in developpers options menu. There is an option for that.
hi,
you know why in my chinese OnePlus 2 doesnt exist the "OEM unlock" option?
thank so much
Dear,
a few days after OnePlus started selling the 2, I rooted it successfully. But I was unable to update to new versions, so I flashed stock recovery and the update manually.
Now, I tried to install an OTA update, but no chance. The device reboots without any update screen.
I decided, that then I can also go back to root again, because there is no big disadvantage more.
I set checkmark in developers settings, that fastboot can unlock bootloader.
But by trying to unlock it (I worked EXACTLY after instructions from OP forums) it firstly shows me:
Code:
fastboot oem unlock
...
OKAY [ 0.006s]
finished. total time: 0.006s
But now it's restarting in a loop. Looks like bootloop... Shows the startup screen with Android logo at the lower edge for < 1 sec, then it vibrates and shows the startup screen another time.
I still can go into bootloader, but I cannot start system anymore. Also trying to boot into recovery shows no effect. Only bootloader is working.
Code:
fastboot oem device-info
< waiting for device >
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Device is_verified: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_locked: 1
(bootloader) exec_console_unconsole: 0
OKAY [ 0.075s]
finished. total time: 0.075s
Normally, after sending "fastboot oem unlock" to device, he will ask me, if I really want to unlock bootloader, but directly after sending command, bootloop starts :crying:
Can anyone help me?
I guess you missed to check the 'OEM bootloader unlock' option within the developer settings. That's what I missed some days ago, when beeing in the same situation.
This thread helped me to get out of this trouble:
Oneplus Two - Solution for Hard Bricked Device
JayVee said:
I guess you missed to check the 'OEM bootloader unlock' option within the developer settings
Click to expand...
Click to collapse
Hab ich ganz sicher nicht vergessen
JayVee said:
This thread helped me to get out of this trouble:
Oneplus Two - Solution for Hard Bricked Device
Click to expand...
Click to collapse
Danke
But problem is still the same, after exactly following of instructions :'(
greetz
~Confringo
https://forums.oneplus.net/threads/mega-unbrick-guide-for-a-hard-bricked-oneplus-2.347607/ < follow step 3 . Worked for another user with the same problem.
You can read his way of suffering here:
https://forums.oneplus.net/threads/relocked-bootloader-bricked.369165/page-6#post-13326550
Hope, you will get lucky .
P.S.: Grüße aus Österreich .
MickyFoley said:
https://forums.oneplus.net/threads/mega-unbrick-guide-for-a-hard-bricked-oneplus-2.347607/ < follow step 3 . Worked for another user with the same problem.
Click to expand...
Click to collapse
Du bist supergeil :highfive::laugh::good::silly::victory:
MickyFoley said:
P.S.: Grüße aus Österreich .
Click to expand...
Click to collapse
Grüße zurück
Mann mann mann ein knappes Gbit im Speedtest.
Grund nach Linz zu ziehen :angel:
JayVee said:
I guess you missed to check the 'OEM bootloader unlock' option within the developer settings. That's what I missed some days ago, when beeing in the same situation.
This thread helped me to get out of this trouble:
Oneplus Two - Solution for Hard Bricked Device
Click to expand...
Click to collapse
HELP PLEASE
i dont have ‘OEM Unlocking’ option in ‘Developer options’.
Help Please
Oxygen V 2.0.0
Right, I tried everything but my bootloader just won't unlock using "fastboot oem nubia_unlock NUBIA_NX563J" I keep getting FAILED (remote: password is error!!)
I've searched for other means but found nothing. What is this password and does somebody know how I can bypass that?
Originally was on 4.16, then updated to 5.15 (8.1 Oreo) with a hope that it will somehow work but it doesn't.
Any help is appreciated, fellas.
tkstevefox62 said:
Right, I tried everything but my bootloader just won't unlock using "fastboot oem nubia_unlock NUBIA_NX563J" I keep getting FAILED (remote: password is error!!)
I've searched for other means but found nothing. What is this password and does somebody know how I can bypass that?
Originally was on 4.16, then updated to 5.15 (8.1 Oreo) with a hope that it will somehow work but it doesn't.
Any help is appreciated, fellas.
Click to expand...
Click to collapse
Try: fastboot flash nubia_unlock NUBIA_NX563J
tkstevefox62 said:
Right, I tried everything but my bootloader just won't unlock using "fastboot oem nubia_unlock NUBIA_NX563J" I keep getting FAILED (remote: password is error!!)
I've searched for other means but found nothing. What is this password and does somebody know how I can bypass that?
Originally was on 4.16, then updated to 5.15 (8.1 Oreo) with a hope that it will somehow work but it doesn't.
Any help is appreciated, fellas.
Click to expand...
Click to collapse
Same **** here. I flashed 4.16 with 5.15 update and i got this error. I tried to fix it in many ways but I got an hard brick (blank screen without any functions); I flashed succesfully the geek buying rom by miflash, but my bootloader still locked and I'm stucked on 2.44 CnCommon.
Are u using AMD Ryzen chipset? I get same result with my pc. I just use my other intel chipset pc to slove it
blindffish said:
Are u using AMD Ryzen chipset? I get same result with my pc. I just use my other intel chipset pc to slove it
Click to expand...
Click to collapse
I am actually using Ryzen, yeah. Will try it on my Intel laptop tonight and let you know if it worked since before that I had a 3770 i7 and I think I tried it there with the same effect.
Thanks for the tip.
WonderingDane said:
Try: fastboot flash nubia_unlock NUBIA_NX563J
Click to expand...
Click to collapse
The command didn't work. Will try with my Intel PC tomorrow.
No way for me.
You have to enable OEM_Unlocking from developer settings
Nof13 said:
You have to enable OEM_Unlocking from developer settings
Click to expand...
Click to collapse
done
°Washy said:
done
Click to expand...
Click to collapse
I had the same problem. I've downloaded abd tools again but not from Nubia Z17 Unlocking Guide, i;'ve downloaded these : https://forum.xda-developers.com/showthread.php?t=2588979 . Put green recovery into adb folder and follow the instructions for Nubia Z17.
News?
tkstevefox62 said:
Right, I tried everything but my bootloader just won't unlock using "fastboot oem nubia_unlock NUBIA_NX563J" I keep getting FAILED (remote: password is error!!)
I've searched for other means but found nothing. What is this password and does somebody know how I can bypass that?
Originally was on 4.16, then updated to 5.15 (8.1 Oreo) with a hope that it will somehow work but it doesn't.
Any help is appreciated, fellas.
Click to expand...
Click to collapse
Same for me guys.
I tried everything that I found on internet but nothing is working
All that it says is password error
@arceoxis are u able to help us,pls. I dont know what I would try to fix this; I'm actually on geekrom bit it's so buggy and I'm not able to flash another one.
°Washy said:
@arceoxis are u able to help us,pls. I dont know what I would try to fix this; I'm actually on geekrom bit it's so buggy and I'm not able to flash another one.
Click to expand...
Click to collapse
I'm going through the same problem. <WAITING DEVICE> in FASTBOOT. in the ROM NUBIA UI 5.18.3. with OEM unlocking and USB debugging enabled.
jurarj said:
I'm going through the same problem. <WAITING DEVICE> in FASTBOOT. in the ROM NUBIA UI 5.18.3. with OEM unlocking and USB debugging enabled.
Click to expand...
Click to collapse
Check the guide about hardbricking. Good luck, man .
SOLUTION
I got it. You have to use: fastboot OEM nubia_unlock
your-version-device
This solve the problems with password error. In my case I have a Nubia z17 NX591J and it works when I use:
fastboot OEM nubia_unlock NX591J
Hope it works for you too
nadiolo said:
Same for me guys.
I tried everything that I found on internet but nothing is working
All that it says is password error
Click to expand...
Click to collapse
tkstevefox62 said:
Right, I tried everything but my bootloader just won't unlock using "fastboot oem nubia_unlock NUBIA_NX563J" I keep getting FAILED (remote: password is error!!)
I've searched for other means but found nothing. What is this password and does somebody know how I can bypass that?
Originally was on 4.16, then updated to 5.15 (8.1 Oreo) with a hope that it will somehow work but it doesn't.
Any help is appreciated, fellas.
Click to expand...
Click to collapse
Mate, do you solve the issue?
nadiolo said:
I got it. You have to use: fastboot OEM nubia_unlock
your-version-device
This solve the problems with password error. In my case I have a Nubia z17 NX591J and it works when I use:
fastboot OEM nubia_unlock NX591J
Hope it works for you too
Click to expand...
Click to collapse
This got me on the right track, i just had to add NUBIA_your-version-device.
And also to anyone else having this issue: Double check if your bootloader unlocking is really enabled in the developer options. I enabled it, and as soon as i left the developer options menu, the OEM unlocking was disabled again. Fix for this issue: activate unlocking, then deactivate it, then activate it again. You should get a popup asking you if you really want to enable OEM unlocking