Unlock Bootloader/change rom on an unknown china device - General Questions and Answers

Hi, my uncle bought for him an android device from a china shop ( joom ), 2 days ago it arrived.
immediately I noticed some oddities, at the first start it was all pre-installed, random ads popping up while using the device and doing a hard reset the result was the same (I didn't have the android setup screen).
In the settings, the Android version is 9.1, but both from the UI and from the recovery you can see that the real version is Android 6, from the recovery I also noticed that the build is MRA58K.
I then tried to unlock the bootloader by selecting "OEM unlock" in the settings, entering the fastboot mode, and writing "fastboot oem unlock" in the terminal, I selected "yes" on the device, as the output of the terminal I received an ok after about 7 seconds but going to reboot the phone nothing happened, and checking the details with "fastboot getvar all" known that the bootloader is still locked.
the device has the name "mata30 pro"
not being an expert in this area I ask you if it is possible to do something or I should simply throw this device, thank you

Related

[Q] Nexus S Stuck!

Hi,
today I woke up and my Nexus S was off. I turned it on and it just stucks while showing the google logo..
I tried pulling the battery, turning on.. still stucks!
so I tried do boot in Fastboot, ok.
Installed the SDK, the USB Drivers. The Nexus was recognized as "Android ADB Interface", ok.
Tried to list the device by "adb device", but I only said: list of devices attached. No device!
Then I tried "fastboot device". There it is! Trying "adb device" again, no device. mh.
So I tried to unlock the phone by typing "fastboot oem unlock".
I get the message on my phone, check "YES" and execute by pressing POWER, but no success. The phones stucks again. The cmd just says "...".
I spend 30min by watching on the cmd and the Nexus S, but no result.
What can I do?
Nexus S, locked Bootloader, 2.3.3, 2 days old
*push..*..
Can you get into the bootloader on the device? (Power and Volume Up)
Has it been rooted, and do you have CWM installed?
I can enter the the bootloader. Firmware is stock, unrooted!
I think the main problem is, that usb debug is not enabled in the device. Thats the reason why adb doesnt recognize it. But fastboot does ...
You can only use adb when the phone is booted up. Fastboot is for when the phone is in the bootloader.
Try going into recovery and doing a factory reset?
I don't know which phone you have, I'm on NS4G, got phone unlocked using GSM codes, so erased everything - a mess. When I got to backup using 2 finger method, there was nothing to reboot to
I went to Samsung site - found program called Samsung Simple DL for my phone, downloaded, executed and ran - back to stock. Kept it unlocked, but was back up and running.
I was paniced, so this might help

[Q][RUU] Heat issues got - Error 131; Customer ID Error when reverting to Stock?

Dear XDA members,
I've purchased the HTC Sensation (non-4G) in July 2011 from eBay UK. After receiving the phone, it was branded with an Taiwanese stock factory firmware. The phone is from the UK, but I think the UK eBay seller bought it from the HTC factory(?) because it's Taiwanese branded.
After the devs achieved S-OFF and custom recovery I started flashing ROMs and everything went perfect.
Just 1 week ago, I was listening and recording some internet radio to my SD card using TuneIn Radio Player. I started recording radio in the evening, with my goal to record it the whole night to listen in the public transportation the next day. After the whole night recording, I woke up in the morning, tried to grab my Sensation, but it was so freaking hot that I said OUCH! within 2 seconds of holding the Sensation. The glass from the screen, the rubber back and aluminium back was so so hot! Also the battery should've been fully charged, but it was stuck at 65% with the notification LED blinking green and red like:
Green 0,2 seconds
Nothing 0,4 seconds
Red 0,2 seconds
Nothing 0,4 seconds
Green 0,2 seconds
Nothing 0,4 seconds
etc etc etc..
I pulled out the battery inmediately let it cool of for about 20 minutes and put the battery back in, and booted up. Everything seemed fine, it started recharging without problems. Also the strange LED lights were gone.
But that same day, the phone lost WIFI, was greyed out on status: Turning on Wi-Fi, but keeps greyed out. 3G mobile network was lost (no 3G/H icon, just nothing), returned after rebooting, but got lost with many other roms after the heat issue. - Phone randomly turns off, hard-poweroff. Just the whole phone power off from sec to sec, like pulling out the battery...
So all and all many issues, which in my eyes is caused by the extreme heated phone from that night. I want to revert it to Stock by removing ROOT, removing ClockWorkMod Recovery and restoring S-ON, to return it back to HTC for warranty. Followed the tutorial here in the DEV section, but got stuck at running the RUU.
I've downloaded the Taiwanese RUU again, ran it, said: 1) Removing user data (or something), Sending......... but gives me a Error 131 - Customer ID Error. I've readed a lot about making a goldcard, but in my eyes this isn't needed because my phone is unlocked, not carrier branded.. correct me if I'm wrong.. Also I can't find how to make a goldcard from an Sensation.
You can send me a message on WhatsApp for any question, which I preffer for the fastest reply: +31 6 41 73 11 58 Phone works correctly.
Best regards and thanks a lot in advance.
Max
Anyone ? #Bump
Do you make SuperCID to your phone?
CID = Customer ID
If not, better do it.
WRITE SUPER CID (allows you to flash ANY ROM to the device regardless of the carrier).
1. Install HTC Sync (install all drivers from HTC Sync for YOUR phone)
2. Activate "USB debugging" on your phone, from "Settings -> Applications -> Development".
3. On "C" drive from your computer create a new folder called "adb" and extract the files from adb.zip into it.
4. Open command prompt and type "c:" enter, then the path to your adb folder "cd adb" enter.
5. Ensure your phone is switched on (regular home screen) and connect it to USB in charging mode.
6. Enter the command "adb devices". (will show "List of devices attached" and YOUR serial number)
7. Enter the command "adb reboot-bootloader". (device WILL reboot in bootloader)
8. Enter the command "fastboot getvar cid" (it should show your actual CID - write down YOUR CID in case you need to go back)
9. Enter the command "fastboot oem writecid 11111111" (write as CID 11111111 - this mean SuperCID)
10. Enter the command "fastboot reboot-bootloader (reboot the bootloader)
11. Enter the command "fastboot getvar cid" (it should confirm your new CID is 11111111)
12. Enter the command "fastboot reboot"
13. Now you can now flash any ROM you like.
Note:
To return to your original CID, repeat steps 6 to 11. On step 8 use YOUR ORIGINAL CID instead "11111111"
[ERR] Command error
> 9. Enter the command "fastboot oem writecid 11111111"
On a MARVEL PVT SHIP S-ON RL I'm getting the following error when executing step 9:
(bootloader) [ERR] Command error !!!
Is this to be expected? Any workaround? Thx

[Q] Nexus 5 died in the night. Fastboot works, but recovery is a black screen.

Hi all, first time posting here.
Last night my Nexus 5 turned itself off while charging. Today it won't boot past the white Google logo. I had an unlocked bootloader, but was stock with no root and no custom rom, 5.1.1. I've had the phone for over a year, and bought it from a high street UK phone chain on contract, not from the Play Store.
I've spent the last 6 hours learning, trying, reading, trying again, watching videos, trying not to punch things, but nothing works.
Here's what I know:
I can boot into fastboot mode
bootloader is unlocked
recovery mode is a permanent black screen
"adb devices" cmd in platform-tools does not find the device
I've tried tweaking Windows 7 drivers (driver for fastboot etc.) but to no avail (including using clockwork)
"fastboot devices" returns the serial code for my phone
flashing using fastboot commands gives me "flash write failure" on bootloader-hammerhead xxx .img
even "fastboot erase boot" does not work ("failed to erase partition")
"fastboot reboot-bootloader" simply turns the phone off (does not attempt even a normal reboot)
Unless I'm in some weird driver quandary, I fear my phone may be beyond help as even simple commands do not work. Any help is much appreciated.
I should mention that "flash-all" doesn't work within platform-tools.
The reboot doesn't actually work. When it says "waiting for device" I manually restart the phone into fastboot myself. And then I get write errors, when it's starts pushing the radio file.
imgur . com / eBk4KnX.png
Pete.D said:
Hi all, first time posting here.
Last night my Nexus 5 turned itself off while charging. Today it won't boot past the white Google logo. I had an unlocked bootloader, but was stock with no root and no custom rom, 5.1.1. I've had the phone for over a year, and bought it from a high street UK phone chain on contract, not from the Play Store.
I've spent the last 6 hours learning, trying, reading, trying again, watching videos, trying not to punch things, but nothing works.
Here's what I know:
I can boot into fastboot mode
bootloader is unlocked
recovery mode is a permanent black screen
"adb devices" cmd in platform-tools does not find the device
I've tried tweaking Windows 7 drivers (driver for fastboot etc.) but to no avail (including using clockwork)
"fastboot devices" returns the serial code for my phone
flashing using fastboot commands gives me "flash write failure" on bootloader-hammerhead xxx .img
even "fastboot erase boot" does not work ("failed to erase partition")
"fastboot reboot-bootloader" simply turns the phone off (does not attempt even a normal reboot)
Unless I'm in some weird driver quandary, I fear my phone may be beyond help as even simple commands do not work. Any help is much appreciated.
Click to expand...
Click to collapse
Did you try locking the bootloader, and then unlocking it again?
Oh god , I think you have a hard bricked nexus .
Schoat333 said:
Did you try locking the bootloader, and then unlocking it again?
Click to expand...
Click to collapse
Good idea! Just tried it (which it let me do) but still getting write errors running flash-all.
Given the sudden shutdown and corruption on your phone along with failure to write and to erase sounds like your internal memory has gone bad.
If that's the case you won't be able to to anything. I had the same occur with a Galaxy S3 last year and the nand memory went bad. Unfortunately it does happen, but not often. My guess is you now have a paperweight

{Q} {ASAP} Completely Bricked HTC One M4. Help!

My friend has recently given me his old phone and ask me if i could fix it for him, i took up the chance and said yeah sure, but now i am stuck and i have no clue what to do!
This phone has no operating system on it and when i got to boot it up, it goes straight to the bootloader screen with the corresponding options; "BOOTLOADER", "REBOOT", "REBOOT BOOTLOADER", "POWER DOWN".
Although i feel that it has no operating system, the bootloader says otherwise. It says that it has "OS-4.15.61.2". It is completely locked and has never been tampered with before, and using "HBOOT-2.22.000".
I have tried putting it into fastboot and then downloading the fastboot terminal, but when i type "fastboot devices" nothing shows up then when i type in something like "fastboot oem unlock" it just says "Waiting for devices". I have been searching for the last 2-3 hours and have been looking at the phone for around 4 hours. I have completely lost my sanity with this phone and it is really bugging me.
Please Help Me!
Yours Sincerely,
Mitch
SkylineUK said:
My friend has recently given me his old phone and ask me if i could fix it for him, i took up the chance and said yeah sure, but now i am stuck and i have no clue what to do!
This phone has no operating system on it and when i got to boot it up, it goes straight to the bootloader screen with the corresponding options; "BOOTLOADER", "REBOOT", "REBOOT BOOTLOADER", "POWER DOWN".
Although i feel that it has no operating system, the bootloader says otherwise. It says that it has "OS-4.15.61.2". It is completely locked and has never been tampered with before, and using "HBOOT-2.22.000".
I have tried putting it into fastboot and then downloading the fastboot terminal, but when i type "fastboot devices" nothing shows up then when i type in something like "fastboot oem unlock" it just says "Waiting for devices". I have been searching for the last 2-3 hours and have been looking at the phone for around 4 hours. I have completely lost my sanity with this phone and it is really bugging me.
Please Help Me!
Yours Sincerely,
Mitch
Click to expand...
Click to collapse
Do you have ADB installed and working on your PC?
Sent from my OnePlus 2 using Tapatalk

Problem with installing a custom recovery (custom binary blocked by OEM lock)

I have bought a used Samsung S10e (SM-G970F/DS) it came with Android 12 and it was reseted.
My goal is to install iodeOS. Even if the iodeOS website says "Update the stock firmware to the latest" I considered the instructions from LineageOS and installed the latest Android 11 version, following this (https://iode.tech/en/iodeos-installation/#1629185391421-4cf1f5c8-d900) uninstall instructions.
After Android 11 was installed I enabled the developer options. OEM-Unlock was not available. Therefore I followed these instructions (https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/) and the OEM-Unlock was available again.
Now it seemed that everything is ready to install iodeOS or LineageOS. Therefore I followed this instructions (https://wiki.lineageos.org/devices/beyond0lte/install). It worked fine until "Installing a cutom recovery using heimdall"
after the "heimdall flash --RECOVERY <recovery_filename>.img --no-reboot" command the S10e shows a bar which is filled from the left to the right and then it shows "Custom Binary (RECOVERY) Blocked By OEM Lock"
Now I have no clue what to do :-(
I would be glad for any help.
​
You need to unlock the bootloader. You've toggled the OEM Unlocking switch, so unlocking the bootloader is the next step.
Make sure you have the Samsung USB drivers installed on your PC.
Turn off your device.
While holding the Bixby and Volume Down buttons, connect your phone to your PC.
The device should start in Download Mode. Hold down Volume Up until you get a warning about unlocking the bootloader. Unlocking the bootloader will wipe your data. Click Volume Up to confirm.
Your device will wipe data, then reboot. At this point, you can reboot to download mode and flash a custom recovery using Odin or Heimdall.
Thanks a lot for all your help!
The problem was I entered the download mode by the adb command "adb reboot-bootloader" and this mode seems to be different to the one which can be accessed by pressing the keys.
Now everything worked fine
I have exactly the same problem here:
SM-A205G with OEM Unlock enabled
There is no unlock bootloader in the bootloader no option anymore
at least in the bootloder of this edition
And I suppose that if it is the bootloader that flashes everything, it is COMPLETELLY LOCKED, could be jailbroken by some new method, but until them... no option :sad:
V0latyle said:
You need to unlock the bootloader. You've toggled the OEM Unlocking switch, so unlocking the bootloader is the next step.
Make sure you have the Samsung USB drivers installed on your PC.
Turn off your device.
While holding the Bixby and Volume Down buttons, connect your phone to your PC.
The device should start in Download Mode. Hold down Volume Up until you get a warning about unlocking the bootloader. Unlocking the bootloader will wipe your data. Click Volume Up to confirm.
Your device will wipe data, then reboot. At this point, you can reboot to download mode and flash a custom recovery using Odin or Heimdall.
Click to expand...
Click to collapse
It seems that this <confirm> option in the bootloader is being removed by samsung, so... even if unlock oem is enabled... it will not work...
I can only reach the bootloader by going to recovery mode them selecting reboot bootloader, or by adb reboot bootloader, but it boots directly in download mode without the option to long-press volume up key
A flasher that doesn't flashes doesn't makes sense. Maybe samsung have hidden something new in there?...
Ok. I've found the solution
1 - Power the phone off
2 - Hold both volume up and down
3 - PLUG THE USB BUTTON WHILE YOU HOLD BOTH these buttons
4 - NO NEED TO PRESS POWER BUTTON
I guess this will work for all phones that don't have the option to start with power+down
Yes. A flasher that does not flash don't exists.
Good luck ! \o/
source:
HELP!!! Custom Binary (BOOT) Blocked By OEM Lock
Hi there, I've been having trouble rooting my Samsung Galaxy A20 - SM-A205GN for awhile now. I'm officially on Android Version 10 with One UI Version 2.0, I've followed the provided guide to root my device but it fails on Odin "all versions" when...
forum.xda-developers.com
wavedevice said:
Ok. I've found the solution
1 - Power the phone off
2 - Hold both volume up and down
3 - PLUG THE USB BUTTON WHILE YOU HOLD BOTH these buttons
4 - NO NEED TO PRESS POWER BUTTON
I guess this will work for all phones that don't have the option to start with power+down
Yes. A flasher that does not flash don't exists.
Good luck ! \o/
source:
HELP!!! Custom Binary (BOOT) Blocked By OEM Lock
Hi there, I've been having trouble rooting my Samsung Galaxy A20 - SM-A205GN for awhile now. I'm officially on Android Version 10 with One UI Version 2.0, I've followed the provided guide to root my device but it fails on Odin "all versions" when...
forum.xda-developers.com
Click to expand...
Click to collapse
Yes, you don't unlock the bootloader VIA the bootloader in Samsung phones.
so you know what happened? I accidentaly reset my phone! I have gone into download mode and there was additional choices: to unlock bootloader holt volup, so I did, then again to confirm unlocking press volup. I did so and then there was for a brief moment android logo and "erasing" and then after about 2 minutes of just Samsung logo phone restarted and asked me to perform setup as it was new! WTH? There was nothing mentioned about deletion
DaHansi said:
I have bought a used Samsung S10e (SM-G970F/DS) it came with Android 12 and it was reseted.
My goal is to install iodeOS. Even if the iodeOS website says "Update the stock firmware to the latest" I considered the instructions from LineageOS and installed the latest Android 11 version, following this (https://iode.tech/en/iodeos-installation/#1629185391421-4cf1f5c8-d900) uninstall instructions.
After Android 11 was installed I enabled the developer options. OEM-Unlock was not available. Therefore I followed these instructions (https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/) and the OEM-Unlock was available again.
Now it seemed that everything is ready to install iodeOS or LineageOS. Therefore I followed this instructions (https://wiki.lineageos.org/devices/beyond0lte/install). It worked fine until "Installing a cutom recovery using heimdall"
after the "heimdall flash --RECOVERY <recovery_filename>.img --no-reboot" command the S10e shows a bar which is filled from the left to the right and then it shows "Custom Binary (RECOVERY) Blocked By OEM Lock"
Now I have no clue what to do :-(
I would be glad for any help.
​
Click to expand...
Click to collapse
I had the same problem on my samsung tab a10.1. That's why I had to flash the stock firmware 3 times. Every time I flashed twrp with odin, I got the error (custom binary blocked by oem lock).
I write what they should do in order.
1. Turn on the phone.
2. Open Developer mode
3. USB debugging mode - on
4. oem unlocking - on
5. then turn off the phone and disconnect from usb
6. Connect the phone to the PC with USB by holding down the volume up and volume down buttons at the same time. WITHOUT PRESSING THE POWER BUTTON
7. Press and hold the volume up button according to the instructions in the pop-up window.
oem unlocked
Sorry that, I had another problem. May I know how to unlock the OEM if my S10e phone can't turn on.
My device always on "samsung" display page, can't open to index. Do you know this issue? Expecting your reply.
Hi! I have the same issue on my Xiaomi Mi 11 Pro (It was Chinese) but it came unlocked with xiaomi.eu rom.
After i installed a global rom, and google wallet nfc pay did not work, so i thought okay i will lock it then so maybe wallet would accept it, (with the eu rom it worked before) so i put the device in fastboot and used fastboot oem lock on cmd...
And from then it stucks on miui recovery 5.0 screen, and says, this miui version can't be installed on this device...
I might not enabled oem unlocking before i shut if off, but i added it to my mi account so i dont know if after a week i can maybe unlock it. But i think the other possible solution would be to sideload the original chinese stock rom, which is for M2102K1AC, Mi 11 pro, codename mars, but i couldn't find it anywhere... If someone can upload a link to it, that would be a huge help! Or any idea! thx!
geraldmany said:
HI! i got a mi 11 pro 1 year ago, and it was offically chinese, but it came unlocked with Xiaomi.eu firmware, but i could't update it via the updater app, so i searched and found the global star version and just flashed it, everything worked, only now google pay nfc didnt work, it said that its probably because of the unlocked bootloader, so i got to fastboot and in cmd i sent fastboot oem lock, and since then my phone is stuck in miui recovery 5.0 screen and says that i cannot run this firmware on the device, i tried to unlock it but failed, maybe after a week, but i think that i didnt turn on oem unlocking on the phone itself before this... So im just hoping that after a week unlocking could be done... Or my other idea is, that i could install the original chinese rom with sideload, because i managed to install another global version on it since, but the result is still the same, the only problem is that i cannot find literally anywhere a mars codenamed firmware...
Click to expand...
Click to collapse
Anyone who might have the same situation, i found a simple, but effective solution, not sure if it works on every xiaomi device, but i will write down the steps here:
You need to use XiaomiADB, here is the download link and the description for how to use it -> https://xiaomiui.net/how-to-use-xiaomiadb-8044/ (if the page is not available, then feel free to msg me!)
For xiaomi adb, you need to go to 3rd option on the miui recovery screen, NOT THE FASTBOOT
So basically i went through the steps to “xiaomiadb sideload_miui <filename>”
And I tried to install a rom, BUT IT DIDNT ACCEPT IT!
The message was:
ERROR: This rom cannot be installed, server code -> 2001, server message -> Can't install unofficial rom
after trying 4 times all the same and: Installation of this rom via stock recovery is not allowed by Xiaomi
Says Installation failed, and then i just decided to download another rom so i PLUGGED OUT THE PHONE right after this, and went to another room to connect to wired network, to download and try a different rom... when i came back, to all my surprise, the phone was turned on, so i went to the setting dev ops and enabled bootloader unlocking, linked it to my account enabled adb and everything that is needed to flash another rom later, so then i rebooted and again, miui recovery 5.0 screen, but now i enabled unlocking, so i put the phone in fastboot, and tried MI UNLOCKER TOOL again, now it says: Please unlock 168 hours later. And do not add your account in MIUI again, otherwise you will wait from scratch.
So that means, after 7 days i wll be able to unlock it, until then, i can turn it on with the above method, in short try to sideload (copy and install) a rom to it, and then after it failed, plug it out and just wait like 10-20 maybe 30 seconds and bam your device is normally booted... I hope it helps to some of you, (i have been searching for the solution for almost a week, my other option was to pay someone who can MAYBE do it or send the phone back to china and pay the repairs, so im really happy with this method! If it helps to you, please reply so i and the others will know that it worked! Have a nice day!

Categories

Resources