Related
Can any developer please please help me out quickly? i'm out of time seriously I need help but quick.
I'm trying to unlock my device Redmi Note 3 Snapdragon varient. All the other commands like
* adb devices
* adb reboot edl
* fastboot devices
* fastboot oem device-info
everyone of it is working fine but when I write
* fastboot oem unlock-go
I get the above mentioned error.
Does anybody know the solution to it? Before answering please consider that other commands are working except this one, I didn't found any proper solution that's why posted the problem here and I already did revoke USB debugging permissions and turned it on again but that didn't helped.
So please give me a working solution as quick as possible or else any help is appreciable.
enable oem unlock in developer options
Enable OEM Unlock option in Developer Options.
caesar13th said:
enable oem unlock in developer options
Click to expand...
Click to collapse
It's already enabled, I don't know what's causing the problem. Please help me with another solution. Ask everything at once, I will answer. But I really need a solution.
superboy123 said:
Enable OEM Unlock option in Developer Options.
Click to expand...
Click to collapse
It's already enabled, I don't know what's causing the problem. Please help me with another solution. Ask everything at once, I will answer. But I really need a solution.
Gurkirat_Singh said:
It's already enabled, I don't know what's causing the problem. Please help me with another solution. Ask everything at once, I will answer. But I really need a solution.
Click to expand...
Click to collapse
That fastboot oem unlock-go command won't work.
OK, follow these steps:-
a) Reboot to Fastboot mode by pressing Power and Vol down buttons for 10 seconds.
b) Download the MiUnlock tool and enter your credentials first. It will check whether your Mi account has permission to unlock (you must have permission from Xiaomi to unlock).
c) It will detect your phone as Mi Phone and proceed to unlock.
d) It will verify whether the Mi account in your phone and the credentials of the Mi account you entered on the PC are the same.
e) It will unlock your device for sure!
If it says some sort of verification error aka. the famous stuck at 50%, wait for some days like for a week and try again, it may work even in 2 days! Keep trying!
Good Luck!:good::highfive:
Thank you!
superboy123 said:
That fastboot oem unlock-go command won't work.
OK, follow these steps:-
a) Reboot to Fastboot mode by pressing Power and Vol down buttons for 10 seconds.
b) Download the MiUnlock tool and enter your credentials first. It will check whether your Mi account has permission to unlock (you must have permission from Xiaomi to unlock).
c) It will detect your phone as Mi Phone and proceed to unlock.
d) It will verify whether the Mi account in your phone and the credentials of the Mi account you entered on the PC are the same.
e) It will unlock your device for sure!
If it says some sort of verification error aka. the famous stuck at 50%, wait for some days like for a week and try again, it may work even in 2 days! Keep trying!
Good Luck!:good::highfive:
Thank you!
Click to expand...
Click to collapse
Thanks for the help but I don't even want to try that method first it's very problematic, it takes a lot of time and it's not even sure if it works. So if you can help me with the problem I'm having that would very very very appreciable :good:.
And why the command will not work, can you please tell me? Also this command gives the same error "fastboot OEM unlock bootloader". Hope you can help .
Gurkirat_Singh said:
Thanks for the help but I don't even want to try that method first it's very problematic, it takes a lot of time and it's not even sure if it works. So if you can help me with the problem I'm having that would very very very appreciable :good:.
And why the command will not work, can you please tell me? Also this command gives the same error "fastboot OEM unlock bootloader". Hope you can help .
Click to expand...
Click to collapse
It's not that problematic, actually it is the easiest way to unlock bootloader!
Unofficial bootloader is the very "problematic" method.
Anyhow, Are you looking for unofficial bootloader unlock? Then go here and follow the steps correctly, dont skip any step.
And for your second question, Xiaomi has complicated the bootloader unlock process by heavy encryption. That's why you couldn't unlock Redmi Note 3 as any Moto device!
superboy123 said:
It's not that problematic, actually it is the easiest way to unlock bootloader!
Unofficial bootloader is the very "problematic" method.
Anyhow, Are you looking for unofficial bootloader unlock? Then go here and follow the steps correctly, dont skip any step.
And for your second question, Xiaomi has complicated the bootloader unlock process by heavy encryption. That's why you couldn't unlock Redmi Note 3 as any Moto device!
Click to expand...
Click to collapse
OK that's why I'm having so much problem to unlock it. I just want to ask do you know any other way to fix the problem I'm having with this error. Cause the post you gave me tells how to unlock the RN3 temporary :crying: but the thread I followed helps to unlock it permanently :good: (how I know cause I used similar commands on my Canvas A1) and I followed almost every step properly.
I don't understand why companies emerged as custom ROMs stops supporting customisation, at least don't make it hard. I just wanted to flash my RN3 with a Custom ROM like CM13 cause MIUI is not supporting 4G networks properly of multiple operators that's why, for which I needed a custom recovery and for which I needed unlocked bootloader.
I just don't understand , all this so that no one could copy their ROM or I don't know for what . It's just makes things difficult for normal people and no one else. Locks can't keep a thief away. If anyone wants to break into their system than one will, if he/she uses right tools properly. Why make normal people lives' difficult?
ALSO I WANT TO ASK MORE THING, if in first case, I get into fastboot mode just after the ROM flash & before very first ROM boot and run this command and if in second case, the room gets booted and then I go into fastboot mode & run the command, DOES IT CREATES ANY CHANCE OF NON-OCCURRENCE OF THAT ERROR IN FIRST CASE?.
Gurkirat_Singh said:
OK that's why I'm having so much problem to unlock it. I just want to ask do you know any other way to fix the problem I'm having with this error. Cause the post you gave me tells how to unlock the RN3 temporary :crying: but the thread I followed helps to unlock it permanently :good: (how I know cause I used similar commands on my Canvas A1) and I followed almost every step properly.
I don't understand why companies emerged as custom ROMs stops supporting customisation, at least don't make it hard. I just wanted to flash my RN3 with a Custom ROM like CM13 cause MIUI is not supporting 4G networks properly of multiple operators that's why, for which I needed a custom recovery and for which I needed unlocked bootloader.
I just don't understand , all this so that no one could copy their ROM or I don't know for what . It's just makes things difficult for normal people and no one else. Locks can't keep a thief away. If anyone wants to break into their system than one will, if he/she uses right tools properly. Why make normal people lives' difficult?
ALSO I WANT TO ASK MORE THING, if in first case, I get into fastboot mode just after the ROM flash & before very first ROM boot and run this command and if in second case, the room gets booted and then I go into fastboot mode & run the command, DOES IT CREATES ANY CHANCE OF NON-OCCURRENCE OF THAT ERROR IN FIRST CASE?.
Click to expand...
Click to collapse
The thread I gave you was not temporary, it is permanent and it is temporary till you get the official unlock permission. Actually it's a permanent 'safe' solution.
Xiaomi did it for security of data, not to stop customising. If it had to stop users from customising, xiaomi wouldn't have given you warranty even if you root or it may not even have given you an option to unlock bootloader!
superboy123 said:
The thread I gave you was not temporary, it is permanent and it is temporary till you get the official unlock permission. Actually it's a permanent 'safe' solution.
Xiaomi did it for security of data, not to stop customising. If it had to stop users from customising, xiaomi wouldn't have given you warranty even if you root or it may not even have given you an option to unlock bootloader!
Click to expand...
Click to collapse
Thanks for all the support and help you gave me.
I got this error too but i forgot how to fix it.
Something about the 'disable driver signature' or the modified rom that you flash before you trying to unlock.
caesar13th said:
I got this error too but i forgot how to fix it.
Something about the 'disable driver signature' or the modified rom that you flash before you trying to unlock.
Click to expand...
Click to collapse
I unlocked the bootloader and also flashed the ROM successfully but still I'm not able to use the 4g service.
superboy123 said:
The thread I gave you was not temporary, it is permanent and it is temporary till you get the official unlock permission. Actually it's a permanent 'safe' solution.
Xiaomi did it for security of data, not to stop customising. If it had to stop users from customising, xiaomi wouldn't have given you warranty even if you root or it may not even have given you an option to unlock bootloader!
Click to expand...
Click to collapse
I unlocked the bootloader and also flashed the ROM successfully but still I'm not able to use the 4g service.
Gurkirat_Singh said:
I unlocked the bootloader and also flashed the ROM successfully but still I'm not able to use the 4g service.
Click to expand...
Click to collapse
By your name, I think you are an Indian, so which Sim you are using? You need to do a 4G pack recharge first to use LTE, VoLTE won't work in custom ROMs right now.
Edit: you could see this thread but this is a bit complicated: http://en.miui.com/thread-335643-1-1.html
superboy123 said:
By your name, I think you are an Indian, so which Sim you are using? You need to do a 4G pack recharge first to use LTE, VoLTE won't work in custom ROMs right now.
Edit: you could see this thread but this is a bit complicated: http://en.miui.com/thread-335643-1-1.html
Click to expand...
Click to collapse
I appreciate your help but the post you gave me is for non-asian countries so it will not work for me. As you already know I'm an Indian so that's why. Are you an Indian, only asking cause in that way you may already faced the problems i'm having.
I'm only familiar with only 2 4G networks for now. One is Airtel 4G, what they say have FDD LTE network, I don't what that is, but that's why it's not working on my phone, I contacted them and they said that my phone doesn't support it, I don't know why cause it support much more LTE Bands other than any smartphone in that price range. Second is Jio 4G, my sim gets detected, shows network in manual selection but doesn't get registered on them. I see only the message of 'No Service' or 'Emergency calls only' when I insert it.
@Gurkirat_Singh
It worked for me.
I had the same problem!
superboy123 said:
@Gurkirat_Singh
It worked for me.
I had the same problem!
Click to expand...
Click to collapse
What worked for you and how? Can you please answer/clarify my questions/doubts please also?
I tried that fix that I gave you and 4G started working for me. You cannot use jio on second sim slot. 2nd sim only connects to 2g.
superboy123 said:
I tried that fix that I gave you and 4G started working for me. You cannot use jio on second sim slot. 2nd sim only connects to 2g.
Click to expand...
Click to collapse
OK I'll try when got time and will update you with the result.
hi everybody.
i need help with finding the stock rom for NOA E1. it`s not its real name, it is a clone of some chinese phone which is sold by a company hangar 18 in croatia under a brand NOA. i cant seem to find the real name of the phone hence i cant find the stock rom.
i found one here but it`s some kind of demo version. it works but it`s filled with bugs and it lags and crashes a lot.
i think the name is hidden in the name of the file "full_n320b-eng 5.1 LMY47D – mt6735m_n320b_l2qhdbs01_kangjia_cc-kewei_64gbitp8d3_lp1_lte_3m-fdd-cs_mul". specifically this part "l2qhdbs01_kangjia_cc-kewei" but all searches led to nothing.
please if anyone knows the name of the phone or where to find the stock rom, it would help me and all the people from my part of the world a lot. any help is appreciated.
tnx.
closest i got is sumvier l22, but the volume buttons are on the other side compared to noa. nevertheless cant seem to find rom for it eather :/
I have it and upload it soon.
tnx a lot m8
i started learning how to port a custom recovery so if it works ill post it
https://mega.nz/#!Zodn3LKZ!OYKU5k6JSmIxRg8nI5xF3GoDzDjda1K56JSULgsCX2g
cant thank you enough.. seriously, tnx
ill upload the recovery if it works
i cant root the device :/
OEM unlocking is on.. none of the apps work.. MTK droid tools is for 65xx, space MTK tools doesn't have the same functionality.
without root i cant port.. so if anyone have a working method for porting 67xx or how to root it ill gladly use it to make a recovery for this device.
https://mega.nz/#!NlNV3ABY!M8PH39oVaYv-X0jYp9PP2f12Fd_zzFKW6TdeV5KeFXI
Use this boot.img file instead stock one, unlock bootloader like this:
a) Type "adb reboot bootloader"
b) After it reboots
c) Type "fastboot oem unlock"
d) Let the process complete
- Check if bootloader is unlocked using the below commands
a) Type "fastboot oem get-bootinfo"
b) If it says your bootloader is unlocked you can proceed
After that you will be able to root the device in standard way
Lost rom
Hi there... does anyone happen to have the rom for this phone? Thank you in advance
Help! lol
lemsip2007 said:
Hi there... does anyone happen to have the rom for this phone? Thank you in advance
Click to expand...
Click to collapse
Does no one have a rom for this handset anymore???
Thank you.
Is it possible to crack the miflash_unlock.exe? Or anyone is familiar with reverse engineering?
sign is local or must by internet? Anyone who can unlock Bootloader with no waiting time can tell me something?
MarsZhang said:
Is it possible to crack the miflash_unlock.exe? Or anyone is familiar with reverse engineering?
sign is local or must by internet? Anyone who can unlock Bootloader with no waiting time can tell me something?
Click to expand...
Click to collapse
You cant crack it because its server based.. you need internet for it to check if you are allowed to unlock. Just wait
Plekst said:
You cant crack it because its server based.. you need internet for it to check if you are allowed to unlock. Just wait
Click to expand...
Click to collapse
if only check you can just jump the instruction. if we know the correct information. maybe we can crack the exe and unlock any device.
MarsZhang said:
if only check you can just jump the instruction. if we know the correct information. maybe we can crack the exe and unlock any device.
Click to expand...
Click to collapse
Lol. Go and crack it then. You think no one else thought of that before?
Plekst said:
Lol. Go and crack it then. You think no one else thought of that before?
Click to expand...
Click to collapse
That's a good news that someone else thought of that. what's the problem?or where is the difficulty? I have tried to modify the exe, ( I changed the flow and give the sign result 0, of course that's not enough) but I do not know if it is possible. maybe we can try.
good
MarsZhang said:
That's a good news that someone else thought of that. what's the problem?or where is the difficulty? I have tried to modify the exe, ( I changed the flow and give the sign result 0, of course that's not enough) but I do not know if it is possible. maybe we can try.
Click to expand...
Click to collapse
I also thought of that but my dissembler skills are weak, any game unlocckers sure can test... but i think to ser base of this phone is very high and some might have tried it too.
MarsZhang said:
Is it possible to crack the miflash_unlock.exe? Or anyone is familiar with reverse engineering?
sign is local or must by internet? Anyone who can unlock Bootloader with no waiting time can tell me something?
Click to expand...
Click to collapse
Not possible at all, even though I've heard there are unauthorised unlocking softwares available online but I highly suggest u stick to MiFlash and go through he waiting period
It will not unlock at all. You need the unlock key, which comes from the server. The server first checks whether the particular account with this device has completed, required no of days. If yes, then it will send the unlock key. You might think, I can skip the checking, but even the checking happens online.
Vishal P said:
You might think, I can skip the checking, but even the checking happens online.
Click to expand...
Click to collapse
Well yes, to unlock the phone fastboot needs a oem bootloader unlock code which only mi knows and probably is a function of imei / serial of the phones.
Cracking a exe may let you land into instruction to try unlocking ( without contacting srver) but then you wont have the code to pass as parameter to oem unlock
So i wanna root my phone with magisk, i have the boot.img prepared. But i cant unlock the bootloader. fastboot oem unlock and fastboot flashing unlock does not work.
Code:
fastboot flashing unlock
...
FAILED (remote: Not implemet.)
finished. total time: 0.004s
Please help, im desperate.
bump
I have the same issue.
I know mostly everyone should know this but ...........I have to say it I am sure some new people don't know or someone just forgot but ...
Have you enabled OEM Unlock ? Have you enabled USB Debugging ?
If you have not then of course your commands will not work or will return with error and ect.....
Have you done adb devices and see what comes back?
Dose it come back with your devices ID or is it come back blank for device info?
One reason you Run that command is to know the state of your phone or USB Debugging ect...
Even if you have enabled the OEM and or USB in developers options before you must check it every time always...now if you haven't for one or both then several things will happen....
Your adb or fastboot commands will not work or or will return with errors.Don't be fooled or confused that some adb and fastboot commands do and will work even if you didn't enable the two options or just one option.
I won't explain that you can Google why you may learn something when doing so if you have t already ... ......
Now if your reading this then. You fit in one of 4 catergories In my Opion .
1.Newbie ( Team entire post it will explain a lot you need to know)
2 Lazy and try to cut corners
( Don't know what to tell you.... ..do it right and quit being lazy)
3 Soft Bricked , Hard Bricked , Bootloop ect.
( Something happens by acident or whatever reason maybe sideloading firmware,recovery,bootloader,ect... ** If not a newbie Skip to
*?*?*?* Section
To advoid a lesson on what to do and what not to do as a newbie.
4 Your using incorrect OEM or ADB and Fastboot commands not for your devices .....
Now I won't beat you up to bad about your post or question or whatever you call that what you did I don't know just looked lazy as hell I won't get to worked up over it no one is perfect and we all been a Newbie or rookie in something but you need to know the importance of what is missing or why your post is crappy as hell ok. So you can learn and or not do it aging. The solution or helping is faster for everybody .
Further reference put as much info as possible . Just most will not ask you 100 questions about . What have you done or not done. Ect...
You should let us know how you ended up in the position what did you do before remember it's not my job to ask you 100 questions to find out what's going one with your device its not our phone that is the problem it's yours
So do us the favor and youraelf and everyone else that comes into contact with the same or similar issue and provide as much info as possible.
So I don't know what you have done other that run 2 fastboot commands and honestly I don't even know think they are correct for That device.
Most phones. Use the same or simar adb or fastboot Commands but there are OEM specific commands for certain android versions or devices and that don't work on other devices .
I will let you. Google more about that also maybe you learn something...
*?*?*?*?*?*?*?*?*?*
to restart your phone into fastboot mode or bootloader mode:
adb devices
adb reboot bootloader
fastboot devices ( just like earlier it's important that device info returns after command )
Now when your bootloader / fastboot mode
fastboot oem unlock
This will Unlock the bootloader and delete all user data present on the phone.
If you still having issue then USB Debugging and OEM unlock was not the issue then your problem is not just the bootloader and needs more detailed approach to fix specific to your device.
I have the same issue impossible to unlock the bootoader on this device and i am not a newbie !
On android 9, device branded orange neva play, 2gb and 32 gb ,Unisoc SC9863A , usb debug on and oem unlock on, all commands not work, i try with your phone tool , the same issue. Nothing on google that can work with this device, seems to be a specific command for this device,
Devildog0351 said:
I know mostly everyone should know this but ...........I have to say it I am sure some new people don't know or someone just forgot but ...
Have you enabled OEM Unlock ? Have you enabled USB Debugging ?
If you have not then of course your commands will not work or will return with error and ect.....
Have you done adb devices and see what comes back?
Dose it come back with your devices ID or is it come back blank for device info?
One reason you Run that command is to know the state of your phone or USB Debugging ect...
Even if you have enabled the OEM and or USB in developers options before you must check it every time always...now if you haven't for one or both then several things will happen....
Your adb or fastboot commands will not work or or will return with errors.Don't be fooled or confused that some adb and fastboot commands do and will work even if you didn't enable the two options or just one option.
I won't explain that you can Google why you may learn something when doing so if you have t already ... ......
Now if your reading this then. You fit in one of 4 catergories In my Opion .
1.Newbie ( Team entire post it will explain a lot you need to know)
2 Lazy and try to cut corners
( Don't know what to tell you.... ..do it right and quit being lazy)
3 Soft Bricked , Hard Bricked , Bootloop ect.
( Something happens by acident or whatever reason maybe sideloading firmware,recovery,bootloader,ect... ** If not a newbie Skip to
*?*?*?* Section
To advoid a lesson on what to do and what not to do as a newbie.
4 Your using incorrect OEM or ADB and Fastboot commands not for your devices .....
Now I won't beat you up to bad about your post or question or whatever you call that what you did I don't know just looked lazy as hell I won't get to worked up over it no one is perfect and we all been a Newbie or rookie in something but you need to know the importance of what is missing or why your post is crappy as hell ok. So you can learn and or not do it aging. The solution or helping is faster for everybody .
Further reference put as much info as possible . Just most will not ask you 100 questions about . What have you done or not done. Ect...
You should let us know how you ended up in the position what did you do before remember it's not my job to ask you 100 questions to find out what's going one with your device its not our phone that is the problem it's yours
So do us the favor and youraelf and everyone else that comes into contact with the same or similar issue and provide as much info as possible.
So I don't know what you have done other that run 2 fastboot commands and honestly I don't even know think they are correct for That device.
Most phones. Use the same or simar adb or fastboot Commands but there are OEM specific commands for certain android versions or devices and that don't work on other devices .
I will let you. Google more about that also maybe you learn something...
*?*?*?*?*?*?*?*?*?*
to restart your phone into fastboot mode or bootloader mode:
adb devices
adb reboot bootloader
fastboot devices ( just like earlier it's important that device info returns after command )
Now when your bootloader / fastboot mode
fastboot oem unlock
This will Unlock the bootloader and delete all user data present on the phone.
If you still having issue then USB Debugging and OEM unlock was not the issue then your problem is not just the bootloader and needs more detailed approach to fix specific to your device.
Marc530 said:
I have the same issue.
Click to expand...
Click to collapse
Oi! When was the last time you unlocked a bootloader? 2014? "FAST OEM UNLOCK" LOL, Any question is a valid help people don't get angry the
The greatest flaw that any intelligent person has is
to think they're smarter than everyone else,
Click to expand...
Click to collapse
Just a quick heads-up.
unlock token - OnePlus (United States)
www.oneplus.com
By the way, to root without readily available stock firmware, first unlock bootloader, then boot a pre-rooted GSI with DSU Sideloader, pull stock boot partition from there, and finally patch/flash it. This applies to the Open variant as well.
AndyYan said:
Just a quick heads-up.
unlock token - OnePlus (United States)
www.oneplus.com
By the way, to root without readily available stock firmware, first unlock bootloader, then boot a pre-rooted GSI with DSU Sideloader, pull stock boot partition from there, and finally patch/flash it. This applies to the Open variant as well.
Click to expand...
Click to collapse
Tried to unlock but apparentpy my device only has 7 digits in the serial number which keeps me from being able to use the website to request the unlock code.
I used the debloat script I found on n200 threads to get oem unlock on option. T-Mobile variant
PsYk0n4uT said:
Tried to unlock but apparentpy my device only has 7 digits in the serial number which keeps me from being able to use the website to request the unlock code.
I used the debloat script I found on n200 threads to get oem unlock on option. T-Mobile variant
Click to expand...
Click to collapse
Try prepending 0s?
Well. I was thinking that doing that would make the unlock token they give me different from what the phone would be expecting
PsYk0n4uT said:
Well. I was thinking that doing that would make the unlock token they give me different from what the phone would be expecting
Click to expand...
Click to collapse
Tried adding zero on front and back of serial it just tells me invalid serial
PsYk0n4uT said:
Tried adding zero on front and back of serial it just tells me invalid serial
Click to expand...
Click to collapse
Chatting with OnePlus hasn't yielded anything so far
Just a tip, because in my infinite forgetfulness I wasted an hour last night trying to figure out why I was getting the error, fastboot could not open target HAL.
Remember that you must request the unlock code from fastboot, not fastbootd. Which is what you will boot into if you issue adb reboot fastboot.
So here's a quick step by step.
1.Enable usb debugging. 2. Connect your device and allow access for the computer. My device asks if I want it to charge or transfer files. Select transfer files/Android auto and then use adb start-server. May have to unplug the USB cable and reconnect. Select "always allow this device/PC".
3. Issue "adb devices" to make sure your connected.it should list your device by it's serial number. If not then try unplugging the device and revoke adb authorizations in dev options and toggle USB debugging off and back on, may even need to reboot the device to get it to connect after doing this.
4. If your device is listed under devices go ahead and issue "adb reboot fastboot"
5. Once rebooted issue "fastboot devices" and make sure the device is listed again.(If not listed make sure you have your driver's installed correctly and fastboot is installed correctly, may need to install Android SDK into same folder as fastboot)
6.You can select English or whatever language if you want but it doesn't seem necessary.You are in fastbootd mode you will see if you DO select a language.
So from here issue"fastboot reboot bootloader" device will reboot and you will have scrollable option at the top beginning with a big green START at the top. This is regular fastboot And where you wanna be to get your unlock code for submitting to Oppo for your unlock token.
7. Issue "fastboot oem get_unlock_code"
8. It should return the info you need, you will also need your IMEI number when submitting so be sure to copy that down.
you can copy and paste the unlock code into notepad or Word and delete out the extra stuff so your left with just the two lines of your unlock code as one single contiguous string of numbers.
8. Go to the link listed by OP and submit the required info. And wait for what seems like forever.
ADB/Fastboot commands-quick recap.
1. adb reboot fastboot
2. fastboot reboot bootloader
3. fastboot oem get_unlock_code
PsYk0n4uT said:
ADB/Fastboot commands-quick recap.
1. adb reboot fastboot
2. fastboot reboot bootloader
3. fastboot oem get_unlock_code
Click to expand...
Click to collapse
Simply "adb reboot bootloader". You won't need fastbootd until GSIs (which I already did ofc).
Thanks, definitely a quicker way to get to fastboot. I guess I wasn't sure if you could reboot directly. Seems maybe I was confusing an older device where you had to reboot to fastboot then "fastboot reboot fastboot" to get to fastbootd for a whole different reason.
This one goes directly to fastbootd when you "adb reboot fastboot"
Nice catch.
with this particular model in scope, what do either of you guys suggest I do if I have gottne the age old bricked message "destroyed boot/recovery image"".. I've tried the MSMTool route and cna't get it to register under Device Manager with the Qualcomm drivers.. It's highly upsetting..
I'm not really sure to be honest, this is my first OnePlus device and just trying to contribute anything I can to get the N20 section up and going as I make progress with the device.
Just a quick search though turns up this and maybe it could be of use if you can still access the bootloader.
the current image(boot/recovery) have been destroyed
I updated my oneplus 8t to KB2005_11.C.11 (OOS 12 ) by first booting to twrp-3.6.1_11-0-kebab.img and then flashed the KB2005_11_C_OTA_1100_all_362b9b_10100001.zip. After the upgrade I had no mobile data on t-mobile and had Volte instead of 5g...
forum.xda-developers.com
Someone mentions extracting the boot.img from stock image and flashing it. I would imagine it should work for you if the stock firmware can be found and circumstances are similar. Maybe at least a start. Wish I could be of more help, maybe someone else can chime in that knows more.
Try Linux, maybe a live dist. if your on a windows machine that won't recognize it just to get it into a state that you can work with it again.
Just an idea, I don't want to steer you wrong as i still have a lot to learn
DrScrad said:
with this particular model in scope, what do either of you guys suggest I do if I have gottne the age old bricked message "destroyed boot/recovery image"".. I've tried the MSMTool route and cna't get it to register under Device Manager with the Qualcomm drivers.. It's highly upsettinghav
Click to expand...
Click to collapse
DrScrad said:
with this particular model in scope, what do either of you guys suggest I do if I have gottne the age old bricked message "destroyed boot/recovery image"".. I've tried the MSMTool route and cna't get it to register under Device Manager with the Qualcomm drivers.. It's highly upsetting..
Click to expand...
Click to collapse
I want to try and help but I'm so new it's sketchy I don't want to say something and get bashed
Please feel free to comment. Don't worry about the trolls. We would love to have you to be part of this conversation. If you have suggestions just post them, and if your unsure about anything just mention that you are. It's a great way to learn. Don't worry about negative feedback, take it as constructive criticism. You may find that the feedback can clear up many questions and/or misconceptions. You never know how your dialogue with other members could help someone else in the future. These forums are here to document all of it just for that purpose. We are all here to learn or help others who want to learn. Though this account is only a year old I have been around these forums on and off for many years and I learn something each and every time I come in search of wisdom. I'm by no means an expert but I find that others benefit from my questions and answer just as much as I have over the years.
Fyi according to a recently made friend who also had the 7 digit serial issue, they were told by OnePlus their dev team is working on an OTA update that will resolve the serial number issues. I'm not sure how that's going to work but I saw the email between them and Oppo support
I guess this must be a widespread issue that they feel is cheaper to invest the amount of money it takes for r&d to come up with a fix than it was to replace a few devices or attempt to do remote repairs.
But this also makes me wonder what avenue they will take to correct the issue.
Also I wonder if someone with the right skillset could gather enough bootloader unlock codes along with the unlock tokens, serial, IMEI, pcba etc.. maybe the algorithm their using to generate the codes could be broken. I'm no crypto expert or math genius either, but if we have the variables to the equation minus one but have the answer, isn't this pretty simple almost pre-algebra?
I mean I guess their not worried about enough people being brave enough to give out sensitive info like that. But maybe Im just ignorant of the complexity of these algorithms.
64 digit key on one end
T-Mobile bought sprint and they have T-Mobile sims no. But I understand that sprint is still a somewhat seperate company (tried to buy a T-Mobile phone and it would not activate on my sprint account. So I bought this from the sprint side of the T-Mobile site so I knew it would work but I assume this is a sprint phone and not a T-Mobile phone so this method would not work.
Can anyone confirm this?
PsYk0n4uT said:
Please feel free to comment. Don't worry about the trolls. We would love to have you to be part of this conversation. If you have suggestions just post them, and if your unsure about anything just mention that you are. It's a great way to learn. Don't worry about negative feedback, take it as constructive criticism. You may find that the feedback can clear up many questions and/or misconceptions. You never know how your dialogue with other members could help someone else in the future. These forums are here to document all of it just for that purpose. We are all here to learn or help others who want to learn. Though this account is only a year old I have been around these forums on and off for many years and I learn something each and every time I come in search of wisdom. I'm by no means an expert but I find that others benefit from my questions and answer just as much as I have over the years.
Click to expand...
Click to collapse
okay peep theres a way i put my oneplus into efu mode, hold both vol up and down then put usb c in continue to hold u should hear PC recognize it
So, before i do it, would deleting the modemst1/modemst2 partitions still let me bypass the t-mobile sim lock and let me unlock the phone like it did on the old oneplus phones?
Flashed a patched boot.img and lost modems. Anyone willing to post the modems? Are they device specific like a device partition?
Sim locked and trying to recover. No radios are working