I ordered a Redmi note 4 through Amazon India, came out alright, all properly sealed and everything but one thing caught my attention is that on developer settings the phone unlock status says it's already unlocked! How can this be possible?
That's weird. Did you call a customer service centre? If I'd receive such product my first though would be to confirm if the Mido I got is a refurbished one or 1st hand. And even if it's one, then the Xiaomi guys should have relocked it... Maybe it's a software bug, try restarting. And the ultimate way to confirm is to use your PC, and you know the rest I hope.
Well, if you feel you can replace it (maybe) talk to amazon guys and confirm if they cover such thing in their replacement policy. Good luck.
MayankMathur said:
That's weird. Did you call a customer service centre? If I'd receive such product my first though would be to confirm if the Mido I got is a refurbished one or 1st hand. And even if it's one, then the Xiaomi guys should have relocked it... Maybe it's a software bug, try restarting. And the ultimate way to confirm is to use your PC, and you know the rest I hope.
Well, if you feel you can replace it (maybe) talk to amazon guys and confirm if they cover such thing in their replacement policy. Good luck.
Click to expand...
Click to collapse
How to check if it's refurbished via PC?
Maybe you have RN4x, it is default unlocked... You can check your box, if it is with chinese language you have 4x, if you have with english lang. it is RN4 Global version and it is locked default...
Edit: also check if it is Snapdragon 625 version or maybe it is MTK?
Sent from my Redmi Note 4x
kurogami95 said:
How to check if it's refurbished via PC?
Click to expand...
Click to collapse
You have to check if the bootloader is really unlocked or not. For this download this zip - https://drive.google.com/open?id=13Sjej5zIJPm_yiJQOVR4rEocwbhDc9oh
Unzip in pc and inside the platfrom-tools folder hold shift and right click.
In the menu it should say, open command prompt here or open powershell here.
click on the provided item (whatever of both it shows)
now, boot your device in fastboot by switching it off and holding down the power and volume down. Once the fastboot mode is open, connect your device via cable to your pc.
Now if you opened a command prompt window then type in -
Code:
fastboot devices
This command will show the connected fastboot devices. If nothing is printed on screen on executing command, then try reconnecting.
then type -
Code:
fasboot oem device-info
But if you have powershell then type in
Code:
.\fastboot devices
and
Code:
.\fastboot oem device-info
This will return some data and now you have to check the first two parameters saying "device tampered" and "device unlocked".
If device unlocked says true, then that means someone had actually used the device before. and if device tampered says true, then definetly someone has tested out your device, by doing all kinds of stuff like installing roms etc.
Use the mi flasher and flash the most current xiaomi rom. Your rom is probably a vendor rom, which is bad.
MyNameIsRage said:
You have to check if the bootloader is really unlocked or not. For this download this zip - https://drive.google.com/open?id=13Sjej5zIJPm_yiJQOVR4rEocwbhDc9oh
Unzip in pc and inside the platfrom-tools folder hold shift and right click.
In the menu it should say, open command prompt here or open powershell here.
click on the provided item (whatever of both it shows)
now, boot your device in fastboot by switching it off and holding down the power and volume down. Once the fastboot mode is open, connect your device via cable to your pc.
Now if you opened a command prompt window then type in -
This command will show the connected fastboot devices. If nothing is printed on screen on executing command, then try reconnecting.
then type -
fasboot oem device-info
But if you have powershell then type in
But if you have powershell then type in
.\fastboot devices
and
This will return some data and now you have to check the first two parameters saying "device tampered" and "device unlocked".
If device unlocked says true, then that means someone had actually used the device before. and if device tampered says true, then definetly someone has tested out your device, by doing all kinds of stuff like installing roms etc.
Click to expand...
Click to collapse
Thanks for making it easy for me. ?
Sometimes sellers unlock bootloader to flash other roms version. It's usually on online selling where there is Chinese roms on devices and buyers want global version.
As allready ppl stated, check by adb fastboot to see if its really unlocked.
Sent from my Redmi Note 4 using Tapatalk
MyNameIsRage said:
You have to check if the bootloader is really unlocked or not. For this download this zip - https://drive.google.com/open?id=13Sjej5zIJPm_yiJQOVR4rEocwbhDc9oh
Unzip in pc and inside the platfrom-tools folder hold shift and right click.
In the menu it should say, open command prompt here or open powershell here.
click on the provided item (whatever of both it shows)
now, boot your device in fastboot by switching it off and holding down the power and volume down. Once the fastboot mode is open, connect your device via cable to your pc.
Now if you opened a command prompt window then type in -
Code:
fastboot devices
This command will show the connected fastboot devices. If nothing is printed on screen on executing command, then try reconnecting.
then type -
Code:
fasboot oem device-info
But if you have powershell then type in
Code:
.\fastboot devices
and
Code:
.\fastboot oem device-info
This will return some data and now you have to check the first two parameters saying "device tampered" and "device unlocked".
If device unlocked says true, then that means someone had actually used the device before. and if device tampered says true, then definetly someone has tested out your device, by doing all kinds of stuff like installing roms etc.
Click to expand...
Click to collapse
Please can you help me? I got a Xiaomi Mi A1 and I noticed the bootloader was already unlocked, when I relock it the phone refuses to come on because I found out that "device tampered" is saying true. Please how can I get it back to false? Thank you
chuckychux said:
Please can you help me? I got a Xiaomi Mi A1 and I noticed the bootloader was already unlocked, when I relock it the phone refuses to come on because I found out that "device tampered" is saying true. Please how can I get it back to false? Thank you
Click to expand...
Click to collapse
You should contact xiaomi for this. And the seller from which you bought it. Because 98% of companies aren't allowed to sell phones with unlocked bootloader. Just leave it as it is. Tampering it by yourself would mean that you yourself did something to phone, which u haven't (not much, what u did is ok) . So getting in touch with the company and the provider would be a better option.
---------- Post added at 07:42 AM ---------- Previous post was at 07:41 AM ----------
chuckychux said:
Please can you help me? I got a Xiaomi Mi A1 and I noticed the bootloader was already unlocked, when I relock it the phone refuses to come on because I found out that "device tampered" is saying true. Please how can I get it back to false? Thank you
Click to expand...
Click to collapse
Or you can just unlock the bootloader once again to possibly make the phone functional
MyNameIsRage said:
You should contact xiaomi for this. And the seller from which you bought it. Because 98% of companies aren't allowed to sell phones with unlocked bootloader. Just leave it as it is. Tampering it by yourself would mean that you yourself did something to phone, which u haven't (not much, what u did is ok) . So getting in touch with the company and the provider would be a better option.
---------- Post added at 07:42 AM ---------- Previous post was at 07:41 AM ----------
Or you can just unlock the bootloader once again to possibly make the phone functional
Click to expand...
Click to collapse
I have unlocked it again and it's working again, but my problem now is that I can't get Ota updates on my phone and is there a way I can change "Device tampered" from true to false? Thank u
chuckychux said:
I have unlocked it again and it's working again, but my problem now is that I can't get Ota updates on my phone and is there a way I can change "Device tampered" from true to false? Thank u
Click to expand...
Click to collapse
Did u install twrp? If no then flash fastboot rom
MyNameIsRage said:
Did u install twrp? If no then flash fastboot rom
Click to expand...
Click to collapse
I didn't install twrp, if I flash with fastboot will it be locked? And how will I do it
chuckychux said:
I didn't install twrp, if I flash with fastboot will it be locked? And how will I do it
Click to expand...
Click to collapse
Most probably yea. Also you should report this in mi a1 forums as well. And you can google to find instructions for flashing update via fastboot.
Related
It looks like Huawei has made available an official method to unlock the bootloader.
http://www.huaweidevice.com/worldwide/servicePolicy.do?method=preUnlock
But i haven't tried it yet. Maybe it could lead to something useful.
both way to obtain product ID doesn't work on cm10 rom, maybe I need to use stock rom.
borisxiao said:
both way to obtain product ID doesn't work on cm10 rom, maybe I need to use stock rom.
Click to expand...
Click to collapse
tested on hwmod's c232B005 rom with bart's kernel, doesn't work either.
Rumbi said:
It looks like Huawei has made available an official method to unlock the bootloader.
http://www.huaweidevice.com/worldwide/servicePolicy.do?method=preUnlock
But i haven't tried it yet. Maybe it could lead to something useful.
Click to expand...
Click to collapse
The form doesn't work correctly. Poor Huawei, they need to get some help from WEB professionals ...
If I select "Tablet" then "Huawei Mediapad" form the two select boxes then it is impossible to fill the IMEI/MEID field.
However if you press the "SUBMIT" button the system says "The IMEI/MEID can contain numbers and letters only.".
The procedure to find the "Product ID" is wrong, or it is not for the MediaPad tablet and doesn't work.
The string they suggest to type in the phone *#*#1357946#*#* or in the calculator ()()1357946()()
doesn't bring up any "Product ID" on my tablet. Probably this number is for other devices.
I just unlocked my MediaPad device by typing:
Code:
fastboot oem unlock
So I believe this device was not really LOCKED.
hwmod said:
The form doesn't work correctly. Poor Huawei, they need to get some help from WEB professionals ...
If I select "Tablet" then "Huawei Mediapad" form the two select boxes then it is impossible to fill the IMEI/MEID field.
However if you press the "SUBMIT" button the system says "The IMEI/MEID can contain numbers and letters only.".
The procedure to find the "Product ID" is wrong, or it is not for the MediaPad tablet and doesn't work.
The string they suggest to type in the phone *#*#1357946#*#* or in the calculator ()()1357946()()
doesn't bring up any "Product ID" on my tablet. Probably this number is for other devices.
I just unlocked my MediaPad device by typing:
Code:
fastboot oem unlock
So I believe this device was not really LOCKED.
Click to expand...
Click to collapse
wow, that looks easy...
hwmod said:
...
So I believe this device was not really LOCKED.
Click to expand...
Click to collapse
I also don't see in what aspect the device should have been locked, fastboot flashing stuff worked right out of the box. Not even fastboot oem unlock was needed.
mblaster said:
I also don't see in what aspect the device should have been locked, fastboot flashing stuff worked right out of the box. Not even fastboot oem unlock was needed.
Click to expand...
Click to collapse
Correct ...
However I tried "fastboot oem unlock" as soon as I bought back in December.
Now with the following "fastboot" command my device shows:
Code:
fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
OKAY [ 0.004s]
finished. total time: 0.004s
while we have tested that for some others users it is:
Code:
fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
OKAY [ 0.004s]
finished. total time: 0.004s
You can try with your and see what you get.
I had a problem,.
I install Mediapad_2.06.26_OsiMood - Light gets Lighter on my Pad.
Now, I can not test CyanogenMod, because it is not come in "fastboot"
How can I do, thank you
anyone has any alternative to unlock the fastbooot Huawei Mediapad 7 v302u
If you have locked bootloader just flash older fw version. This or something older http://download-c.huawei.com/tcpsdownload/downLoadCenter?category=&flay=software&downloadID=NDYyNDc=
Rumbi said:
It looks like Huawei has made available an official method to unlock the bootloader.
http://www.huaweidevice.com/worldwide/servicePolicy.do?method=preUnlock
But i haven't tried it yet. Maybe it could lead to something useful.
Click to expand...
Click to collapse
This website doesn't work, there is not even a way to select MediaPad as of 7/28/2013
hwmod said:
The string they suggest to type in the phone *#*#1357946#*#* or in the calculator ()()1357946()()
doesn't bring up any "Product ID" on my tablet. Probably this number is for other devices.
I just unlocked my MediaPad device by typing:
Code:
fastboot oem unlock
So I believe this device was not really LOCKED.
Click to expand...
Click to collapse
the correct string in the calculator is ()()1357946()()=
you forgot the '=' sign...
but when I type your code in adb I get " FAILED <remote: please input key>
So then I tried to type*
Code:
fastboot oem unlock <product key I obtained from above mentioned method>
then it says: Unlocking...
OKAY [0.038 sec]
Finished. Total Time..
But the MediaPad reboots and goes into "Failed" wrong key or something of that sort, and still cannot get over the fastboot lock. Can anyone please help?
Corn Flake said:
Everything what was said there about unlocked bootloader for hws73xx. I am not sure if there is fw with unlocked bootloader for lite. Try to send email to [email protected] with your S/N number, IMEI and product id and request for bootloader unlocking code.
Click to expand...
Click to collapse
I sent an email to that address and I got the following reply from HuaWei:
From: [email protected]
Sent: Sunday, July 28, 2013 5:17 PM
Subject: 答复: i need bootloader unlock code for my mediapad
Dear Customer,
Thank you for contacting Huawei device.
Sorry that there have no bootloader unlock code for the MediaPad items.
Once again thank you for contacting Huawei device.
Best Regards.
Huawei Device Customer Care Team.
Please someone HELP ME unlock the fastboot, because this is the only firmware <<<HUAWEI MediaPad Firmware(S7-302u, Android 4.0, C235B001, EN, Network Function)>>> that I find perfectly working the way I need it, except I cannot install SU and CWM to root it because of this fastboot lock thing... I REALLY NEED HELP! PLEASE!!!
I have the TMobile Springboard 303u version, still waiting on network unlock code from tmobile... wonder if that code is going to work to unlock the bootloader too?
of only superuser you can try this way. inject su binary & superuser.apk to the official rom with linux command. set permission. then reflash it to your mediapad. but this can't fix the unlocked bootloader problem. this just add a superuser to official rom.
danisukses said:
of only superuser you can try this way. inject su binary & superuser.apk to the official rom with linux command. set permission. then reflash it to your mediapad. but this can't fix the unlocked bootloader problem. this just add a superuser to official rom.
Click to expand...
Click to collapse
i did the unthinkable! (I am so stupid) In the effort to get a working unlocked bootloader, I stubbornly flashed the wrong bootloader by using the attached application [NOTE to everyone - do NOT use this attachment for anything! you will brick your device! i am only attaching it in hopes that somebody will fully understand what i've done & troubleshoot and help/guide me in the process of unbricking my device]
So can somebody please help me unbrick my device? I am a noob and I have Windows 7 Ultimate. I don't even know how to use Linux. The sad part is that I got SU and root right before I did this stupidity. I got root and SU with the software from this website: http://www.unlockroot.com/unlockroot.html
so officially now I am really begging for HELP with step-by-step instructions on how to unbrick my device? (again - I flashed the wrong bootloader from the attached file).
can you enter to bootloader (fastboot) mode?
danisukses said:
can you enter to bootloader (fastboot) mode?
Click to expand...
Click to collapse
No. Dead. Device doesn't even look like it is turning on, which is expected when one flashes the wrong bootloader. this is brick-brick dead. it doesn't get any worse than this...
maybe the JTAG method can fix it. but JTAG method is only for professional who really2 know how to use the tools.
danisukses said:
maybe the JTAG method can fix it. but JTAG method is only for professional who really2 know how to use the tools.
Click to expand...
Click to collapse
what is JTAG method? are their detailed instructions for the T-Mobile Springboard? If there are detailed instructions for this specific device, then I can definitely do it. I've been pretty good so far at following all the instructions here. I've flashed many ROMs here, etc. The only time I get in trouble is when I go off and do stupid things like flashing the wrong bootloader... I'll never do that again! So yeah - any step-by-step instructions for Windows 7 user?
you can find it on google. it use some toolkit to flashing the board directly from PC.
Unlock code recived from Huawei support about 3 hours ago
try to install "twrp recovery for mediapad" - done
try to find people, who can build CM mod
hwmod said:
The form doesn't work correctly. Poor Huawei, they need to get some help from WEB professionals ...
If I select "Tablet" then "Huawei Mediapad" form the two select boxes then it is impossible to fill the IMEI/MEID field.
However if you press the "SUBMIT" button the system says "The IMEI/MEID can contain numbers and letters only.".
The procedure to find the "Product ID" is wrong, or it is not for the MediaPad tablet and doesn't work.
The string they suggest to type in the phone *#*#1357946#*#* or in the calculator ()()1357946()()
doesn't bring up any "Product ID" on my tablet. Probably this number is for other devices.
I just unlocked my MediaPad device by typing:
Code:
fastboot oem unlock
So I believe this device was not really LOCKED.
Click to expand...
Click to collapse
where to write this? and how to get the adb file for media pad 7 youth (S7-701u)
---------- Post added at 03:18 PM ---------- Previous post was at 02:47 PM ----------
danisukses said:
can you enter to bootloader (fastboot) mode?
Click to expand...
Click to collapse
where to get the ADB file?
I bought a Mediapad X1 3G version. It is a nice machine, albeit a bit too large as a phone - picture a large brick near your head,
Well, I emailed [email protected] to obtain the bootloader unlock code. I got the code so I would like to go ahead. But I ran into a very strange fastboot issue. When I issue the command "fastboot devices" -
? fastboot
That question mark is supposed to be some number. So this means the device is not recognized. Hence the unlock code does not work. Weirdly, commands such as "fastboot oem get-bootinfo" works, it shows the bootloader is locked. "Fastboot reboot" also works.
Anyone has any idea how I can solve this problem? Some driver issue? Thanks.
wxppro said:
I bought a Mediapad X1 3G version. It is a nice machine, albeit a bit too large as a phone - picture a large brick near your head,
Well, I emailed [email protected] to obtain the bootloader unlock code. I got the code so I would like to go ahead. But I ran into a very strange fastboot issue. When I issue the command "fastboot devices" -
? fastboot
That question mark is supposed to be some number. So this means the device is not recognized. Hence the unlock code does not work. Weirdly, commands such as "fastboot oem get-bootinfo" works, it shows the bootloader is locked. "Fastboot reboot" also works.
Anyone has any idea how I can solve this problem? Some driver issue? Thanks.
Click to expand...
Click to collapse
You just emailed them asking for bootloader unlock code? What information did you have to provide them?
Update: bootloader on my device was already unlocked
acuratlsfan said:
You just emailed them asking for bootloader unlock code? What information did you have to provide them?
Update: bootloader on my device was already unlocked
Click to expand...
Click to collapse
I just gave them the serial number, IMEI, MAC address, and model (7D-501U). They reply pretty quickly, a few hours.
Good that you have an unlocked bootloader - When you run the fastboot command, does it show a number for your device but not a question mark?
wxppro said:
I just gave them the serial number, IMEI, MAC address, and model (7D-501U). They reply pretty quickly, a few hours.
Good that you have an unlocked bootloader - When you run the fastboot command, does it show a number for your device but not a question mark?
Click to expand...
Click to collapse
i
I can't remember i it displayed a number or a " ? " . I updated to 4.4.2 earlier... and 4.4.2 has an updated fastboot.img. The way i know if because when I enter fastboot now it displays in green letters " DEVICE UNLOCKED " under the"...hold power down 10 sec...."
Dear all,
I bought Mi Pad 4 and it was running well, and I want to update the ROM. The device is comes with Locked bootloader.
I unlocked my Mi Pad 4 using MI Unlock. And when I try to relock it using "fastboot oem lock" command, it become suddenly comes with black screen with written: "The system has been destroyed. Press power button to shutdown".
So I entered the fastboot mode and try some command/solutions:
- My device status is locked:
E:\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.006s]
finished. total time: 0.006s
- I can't unlock it using Mi Unlock:
- Flashing using MiFlashalso not allowed since it is still locked:
- I tried to unlock using fastboot, also failed:
E:\adb>fastboot oem unlock
...
FAILED (remote: Token Verify Failed, Reboot the device
)
finished. total time: 0.003s
- The faastboot screen in my mi pad is only for around 10 Second. After that it goes to "The System has been Destroyed" stage...
Any help is appreciated, because I cant use it anymore...
Why did you even want to close the BL again?!? I dont understand anyone who does that.
And AFAIK you can flash an original Image from Xiaomi even with locked BL. But I have never done it and the guide shows a working phone..
http://en.miui.com/thread-835254-1-1.html
You need the Mi-Flash Tool. And these damn Indian people with their fake titles on youtube.. The title is english and the freaking video is hindi or whatever.. SO ANNOYING!!!
Hi, the tutorial you gave is for 'normal' xiaomi phone, where it boot normally (even its BL is locked).
In my case, I cant load the BL (It said: Destroyed). The only thing I can do is restart to fastboot state, and after 20 seconds it goes again to Destroyed state.
Ok, so I have read some other threads and what seems the "only" solution is to unlock the bootloader again.. But the other people had no problem running "oem unlock".. And you get an error, what is kinda strange.
What happens in MiUnlock? Error?
Hi, I think the main problem is current status is "The System has been Destroyed", therefore it cannot load the BL.
Meanwhile, the BL is in Locked status. So it need to be un-locked first, so I can load the new ROM.
MIUnlock is error, it said: "Current account is not bound to this device", which is strange, because previously I unlocked using it before.
I assume MIUnlock said this because the status of "System destroyed"...
Never lock if there is not 100% Xiaomi official rom inside, and better use MiFlash with "clean all and lock" option for locking.
Thanks for your suggestion. Will do that after I fix this problem..
I think you have a bricked device.. Some devices have this "test-pins", where you can enable some debug-bridge and there you could flash it (mi5 or redmi5 was that in that thread). I dont know if the Pad4 has such Pins and you would have to open the whole device.. (its not something you can access from the outside).
But I dont know if the Pad has these test-pins, just because another Xiaomi device had it..
Noted on that, but too risky for me to open the case..
Any other solution would be really appreciated.
thE_29 said:
But I dont know if the Pad has these test-pins, just because another Xiaomi device had it..
Click to expand...
Click to collapse
On some devices you have to login your Mi Account with MiFlash when flashing in EDL mode and account needs special permissions.
P.Kosunen said:
On some devices you have to login your Mi Account with MiFlash when flashing in EDL mode and account needs special permissions.
Click to expand...
Click to collapse
Yup, and I cant do that since cannot load the BL, because it's "Destroyed" right now..
Up.
Does anyone have the solution on this?
Thanks.
Seemed "bricked" to me, welcome to the bricked world dude, I have had 2 beautiful paper holder on my desk.
mac_erot said:
Up.
Does anyone have the solution on this?
Thanks.
Click to expand...
Click to collapse
The only solution was already posted several times -> open device, find test-pins, use them and flash ROM. And yet, you still ignore it everytime. THERE is no other solution for bricked devices.
And: NEVER close the bootloader again on NON official ROMs.
2 ways to try out...
1st run
"fastboot flashing unlock"
2nd
"fastboot oem reboot EDL"
Or this link if the command doesn't work
https://www.google.com/amp/s/forum....e-how-to-reboot-to-edl-fastboot-t3394292/amp/
go to service centre they will be able to restore the device using edl i hope
I tried also all solutions, but nothing helped. EDL, fastboot, etc.
If there is a way to unlock the BL again I can go on. Otherwise there will be no chance for me to get it running.
Has anyone got a solution how I can unlock the BL again? Or flash with locked BL?
Thanks!
maluc said:
I tried also all solutions, but nothing helped. EDL, fastboot, etc.
If there is a way to unlock the BL again I can go on. Otherwise there will be no chance for me to get it running.
Has anyone got a solution how I can unlock the BL again? Or flash with locked BL?
Thanks!
Click to expand...
Click to collapse
Looks like it is straightforward to remove the back cover. Perhaps you can find the EDL test points on the motherboard?
https://www.youtube.com/watch?v=RZpj0k9HKTQ
Is there no possibility to enable USB Debugging without entering the miui surface?
maluc said:
I tried also all solutions, but nothing helped. EDL, fastboot, etc.
If there is a way to unlock the BL again I can go on. Otherwise there will be no chance for me to get it running.
Has anyone got a solution how I can unlock the BL again? Or flash with locked BL?
Thanks!
Click to expand...
Click to collapse
Edl with test points should work, try some different ones, maybe the ones you are trying are wrong
---------- Post added at 06:47 AM ---------- Previous post was at 06:47 AM ----------
Also, try to run fastboot erase vbmeta
ahsvanz
try
C:\ADB >fastboot devices
C:\ADB >fastboot OEM device-info
etc
replacing
C:\ADB with where ever you fastboot file is located
I too am having the same issue.
I recently wanted to try Android 12, I took a chinnese version of it and my phone is unusable, literally all chinnese.
I want to downgrade, I enabled Debugging and Oeam Unlock in Dev options but I get the ''remote: 'Flashing Unlock is not allowed"" when I try to fastboot oem unlock, I tried different USB ports, I keep updating all my drivers for ADB but nothing is working. I'm panicking a bit cause I don't have a phone to use, and not many people work with ONEPLUS in my country.
If someone has an answer, please save me lol
slimmynine said:
I too am having the same issue.
I recently wanted to try Android 12, I took a chinnese version of it and my phone is unusable, literally all chinnese.
I want to downgrade, I enabled Debugging and Oeam Unlock in Dev options but I get the ''remote: 'Flashing Unlock is not allowed"" when I try to fastboot oem unlock, I tried different USB ports, I keep updating all my drivers for ADB but nothing is working. I'm panicking a bit cause I don't have a phone to use, and not many people work with ONEPLUS in my country.
If someone has an answer, please save me lol
Click to expand...
Click to collapse
have you tried the code above ??
cant you just download the official original firmware and flash that ? im not familiar with the oneplus flashing techniques, ive always had samsungs except for the htc evo 3d back in the day
I tried them all, nothing seems to work
I'm stuck at 'Flashing unlock is not allowed'. I've set up everything I need to in Developer Options, I made sure they're all enabled.
It's really weird, could it potentially be a software issue? The software itself will not allow me to unlock OEM even though the check is turned on?
slimmynine said:
I tried them all, nothing seems to work
I'm stuck at 'Flashing unlock is not allowed'. I've set up everything I need to in Developer Options, I made sure they're all enabled.
It's really weird, could it potentially be a software issue? The software itself will not allow me to unlock OEM even though the check is turned on?
Click to expand...
Click to collapse
how does the one plus flash firmware ? for samsung we use a tool called odin, do you not have a similar tool for your device ?
I don't recall having any toolkit like that, but in order for the toolkit to work.. do you need to have an unlocked bootloader?
Cause the main issue is that I can't unlock it.
i dont think so, if your flashing an official firmware, but for your device i cant be sure of that
?
did you try running your commands as an su , is your device rooted ? you could try sideloading an update.zip maybe
what does it say when you flash this command ? true, true false ?
C:\ADB>fastboot OEM device-info
maybe this will help https://forum.xda-developers.com/t/...us-2-back-to-stock-100.3269543/#post-64279667
slimmynine said:
I too am having the same issue.
I recently wanted to try Android 12, I took a chinnese version of it and my phone is unusable, literally all chinnese.
I want to downgrade, I enabled Debugging and Oeam Unlock in Dev options but I get the ''remote: 'Flashing Unlock is not allowed"" when I try to fastboot oem unlock, I tried different USB ports, I keep updating all my drivers for ADB but nothing is working. I'm panicking a bit cause I don't have a phone to use, and not many people work with ONEPLUS in my country.
If someone has an answer, please save me lol
Click to expand...
Click to collapse
yeah i think some phone makers lock down the bootloader, like its unlocked but when i try to flash a gsi it says device locked state
jamsandpeabug said:
alcatel has a program to download and install firmware but the device is not listed, cannot find fw on the net
Click to expand...
Click to collapse
OK try
c:\adb
Adb fastboot oem device-info
Replacing
C:\adb
With where ever your fastboot is located
Just to check if your device is showing is oem locked or unlocked, it will display with a true or false option. I can't really advise to much as I don't have experience with that device
You could also try
fastboot oem unlock_critical
Not sure if that will work for your device though
Idk what else to recommend, are you stuck at boot ? Can u boot into recovery mode ? Do u have an ext sd card slot
OT-6025D | GSMSERVERPRO
gsmserverpro.com
Is that your firmware
Alcatel 1s Flash File Download [Stock ROM or Firmware
You can Download latest flash file and flash tools for Alcatel 1s phone here. Original stock ROM or Firmware available for free.
mobilereset99.com
Have youlooked at that
if you can confirm your phone has a mtk chipset use mtkclient to bootloader unlock it https://github.com/bkerler/mtkclient
otherwise youre out of luck
But
jamsandpeabug said:
im not stuck at boot, i want to flash gsi but it says device is in locked state even with oem unlocked in dev options, adb debugging enabled etc , and just wont let me flash.. its starts flashing and then fails due to locked state
Click to expand...
Click to collapse
If the flashing starts, and fails, the os would be overwritten and you wouldn't be able to boot. So what you mean is the process trys to start but fails, right yh then I don't know what else I can say to try and help, let's hope mtkclient is an avenue you can pursue
MOD ACTION:
Thread closed since OP has no content.
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