I want to unlock the bootloader of my device.
my device is samsung galaxy tab e (sm-t375s) using android Marshmallow. This is an old device.
Cellular service provider is SKT (in korea)
I installed twrp and did routing using magisk, but it became a brick, so I covered the stock ROM.
Once I unlock the bootloader, I'll root it again.
i am downloading Adb, I succeeded in making my device recognized in adb.
For example, entering [ ADB devices ] recognizes my device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
However, if I enter [ADB bootloader], reboots. But it's a normal boot - such as pressing the power button to restart -. I cannot enter the bootloader.
if I enter [fastboot flashing unlock], prompt <waitng for any device >, we couldn't find the device, so i had to shut down the powershell.
And when I type [fastboot devices], adb doesn't return any response.
So I tried.
1.Update USB Drivers
It didn't work.
2.Power Button & Home Button & Volume+ Button -> Enter Recovery Mode -> Select reboot to bootloader
This method also becomes normal boot and cannot enter fast boot mode.
3.Power Button & Home Button & Volume - Button -> Enter Download Mode
Recent Galaxy devices can unlock in download mode. But my device is too old to do.
Running adb in download mode does not recognize my device. I mean, even the [adb devices] command is impossible.
How can I unlock the bootloader?
Samsung devices don’t have a traditional bootloader, but something the company calls “Download mode.” To access it, press and hold the volume down, power, and home buttons until the Samsung logo shows up, then release. In order to flash anything in downloader mode, you might need a patched version of odin. Try using the search bar on XDA or search the internet for a way for you to do it.
Have a look at THIS page which will tell you all about it. I wouldn't go downloading a bunch of stuff from there as I am not sure if it is any good but, it's a great read and it'll be very informative to you.
Also, be very careful what you do to your phone without ever having done it before or without reading things in their entirety. You could Brick your device. (render it useless)
I'm sure it's likely similar to this post. The search bar is your friend!
BookCase said:
Samsung devices don’t have a traditional bootloader, but something the company calls “Download mode.” To access it, press and hold the volume down, power, and home buttons until the Samsung logo shows up, then release. In order to flash anything in downloader mode, you might need a patched version of odin. Try using the search bar on XDA or search the internet for a way for you to do it.
Have a look at THIS page which will tell you all about it. I wouldn't go downloading a bunch of stuff from there as I am not sure if it is any good but, it's a great read and it'll be very informative to you.
Also, be very careful what you do to your phone without ever having done it before or without reading things in their entirety. You could Brick your device. (render it useless)
I'm sure it's likely similar to this post. The search bar is your friend!
Click to expand...
Click to collapse
First of all, thank you for your kind reply.
But did you read my question well? I'm sorry if I didn't write the question properly.
I read all the tutorials I could see.
I tried to enter the download mode that you linked first.
In my question, please look at the numbers one to three.
As a result, I can enter download mode, but adb does not recognize my device. Updating the driver is the same.
I can enter download mode, but then adb doesn't recognize my device.
Normally(system booting), it becomes adb devices, but when i enter download mode, i can't do it at all.
Secondly, is bootloader unlock only available in custom ROM?
I tried all the previous attempts in stock rom. If it's only possible in custom ROM, it's my mistake.
I downloaded the file from the site you mentioned (second). However, if I try to send it to my device by odin, it fails.
Is it because SM-t377p is global version and my SM-t375s is Korean local version?
It is the same device and the same screen size, but the model names of the two devices are different.
If you say unlock is possible only in custom ROM, I will find my own custom ROM.
Thank you.
I'm sorry, I know that is not your device but, it is similar. Those were just examples. I am trying to help you but, I'm not completely sure if I can. I believe your tablet is Wi-fi only. You should see a toggle in "Developer Options" on the device that says "OEM Unlocking". You should toggle that on as well as USB Debugging. When you connect the device to the PC you should switch it to "Transfer Files" instead of just charging and when you do that, you should get a popup to allow the PC to control it. Approve that. Then try rebooting into "Download Mode" and see if there's an option to unlock the bootloader on the device. If not, I don't know. I have done this before with other Galaxy tablets. I know it's not difficult. Are you sure the bootloader is even locked?
BookCase said:
I'm sorry, I know that is not your device but, it is similar. Those were just examples. I am trying to help you but, I'm not completely sure if I can. I believe your tablet is Wi-fi only. You should see a toggle in "Developer Options" on the device that says "OEM Unlocking". You should toggle that on as well as USB Debugging. When you connect the device to the PC you should switch it to "Transfer Files" instead of just charging and when you do that, you should get a popup to allow the PC to control it. Approve that. Then try rebooting into "Download Mode" and see if there's an option to unlock the bootloader on the device. If not, I don't know. I have done this before with other Galaxy tablets. I know it's not difficult. Are you sure the bootloader is even locked?
Click to expand...
Click to collapse
Thank you for your advice.
My device is a cellular model. But I didn't register with the carrier.
I toggled the options "OEM Unlocking" and "USB Debugging". And I connected it to my computer, and I switched it to "Transfer Files."
Could you tell me the device and version that you succeeded in?
There is no bootloader unlock option in my download mode.
Maybe you saw this screen.
But I look at this screen.
(This picture is not my device.)
Can you see the difference between the two pictures?
First, there are three menus. It has the option of unlocking the boot loader (Long press volum +, device unlock mode.)
The second is two menus. and there is no such option.
Pressing and holding the Volume+Key on this screen does not enter bootloader.
Has anyone found a solution? I am having the exact problem with my Samsung Galaxy Tab S8 5G (UK model, not locked with a specific mobile carrier, should be bootloader un-lockable). I can go to download mode, but don't have the option for unlocking bootloader with long pressing vol+ on the warning screen. If I press Vol, I am taken to the 'downloading' page and I can only get out of it to reboot. I've been trying to find a solution with no avail.
Related
This is the first time it happens to me. I'm not an expert with cellphones, but i think this is a very weird situation.
This is the history. My cousin gave me his Moto X Play as a gift after he went to a local to repair the phone's broken display. It looked good well when i used it at the first time. But, when i tried to root that phone i have noticed a very weird issue....
The phone can't enter to a Fastboot mode when i press the buttons, and when i turn it on, it doesn't seem to have a boot logo. Im not sure about this situation, but im afraid that this phone doesn't have a boot logo, or fastboot menu.
-The phone doesn't seems to be rooted before, or have an another recovery, but i'm not sure about this.
-Everyting in the phone's system seems ok.
-The phone turns on with order (The right time and right boot), there's also the boot animation except that there's no logo.
-I have a little trouble with the phone's speaker, but, thats an another situation.
What can i do about? What do you think this is about? I can't talk with my cousin because his not living in my town, and he doesn't know about this.
Are you sure all the buttons are working ?
Are you saying that the phone manages to boot to the OS (Android)
It also sounds like you've deleted or corrupted some files e.g. the boot logo file (which contains a load of images not just the unlocked one)
Once its booted and you connect via ADB?
Have you rooted the phone, and does ADB have root.
Have you tried installing a replacement boot img file ? (not sure if this is possible from ADB)
RogerClark said:
Are you sure all the buttons are working ?
Are you saying that the phone manages to boot to the OS (Android)
It also sounds like you've deleted or corrupted some files e.g. the boot logo file (which contains a load of images not just the unlocked one)
Once its booted and you connect via ADB?
Have you rooted the phone, and does ADB have root.
Have you tried installing a replacement boot img file ? (not sure if this is possible from ADB)
Click to expand...
Click to collapse
.....
1. Yes! Pretty sure
2. Yes, the OS runs perfectly
3. I'm not sure about that, it may be
4. Nope
5. Not me, maybe another guy, but the phone doesn't seem to be rooted right now
6. Nope
Anny sugest?
Try entering fastboot with no power cable connected (not connected to the PC or charger)
Hold the power and volume down for at least 15 secs (needs longer than you expect)
(I see that on some Motorola G's if it is connected to a PC or power it doesn't seem to enter fastboot)
RogerClark said:
Try entering fastboot with no power cable connected (not connected to the PC or charger)
Hold the power and volume down for at least 15 secs (needs longer than you expect)
(I see that on some Motorola G's if it is connected to a PC or power it doesn't seem to enter fastboot)
Click to expand...
Click to collapse
I tried those before and nothing. Anything else you can think for me?
Have you tied this
https://forum.xda-developers.com/showthread.php?t=1853159
RogerClark said:
Have you tied this
https://forum.xda-developers.com/showthread.php?t=1853159
Click to expand...
Click to collapse
I have tried, but console says my ADB Device is Offline. What can i do? My ADB Tools are up to date
I presume you followed the instructions in the linked thread and enabled the developer options etc
One thing I've noticed about Marshmallow and Nougat is that ADB doesnt seem to work unless you select File Transfer instead of Charging in the "Using USB to " notification popup.
Otherwise if you do
adb devices
there is nothing in the list
RogerClark said:
I presume you followed the instructions in the linked thread and enabled the developer options etc
One thing I've noticed about Marshmallow and Nougat is that ADB doesnt seem to work unless you select File Transfer instead of Charging in the "Using USB to " notification popup.
Otherwise if you do
adb devices
there is nothing in the list
Click to expand...
Click to collapse
I'll keep that in mind, thanks a lot for those sugestions.
RogerClark said:
I presume you followed the instructions in the linked thread and enabled the developer options etc
One thing I've noticed about Marshmallow and Nougat is that ADB doesnt seem to work unless you select File Transfer instead of Charging in the "Using USB to " notification popup.
Otherwise if you do
adb devices
there is nothing in the list
Click to expand...
Click to collapse
UPDATE: It seems i can access to bootloader from the computer, but screen is black when that happens. When i finaly entered to fastboot mode screen was all black and nothing happened. I noticed about this 'cause when i pushed the "+" button phone has restarted with normaly. What do you think about this?
As an extra, these messages apear when i write an ADB comand...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
UPDATE: I've already unlocked the phone's bootloader, but can't flash the TWRP Recovery. When i try it says it was flashed sucessfuly, but, when i enter to recovery mode, it haves the stock recovery.
I've not personally experienced this, but I think you are supposed to make sure you reboot back onto recovery after flashing TWRP because some systems will overwrite TWRP the next time you boot.
If you can get hold of the original ROMs for the phone, (search this forum). I'd recommend perhaps you flash them first, using mfastboot, and get the phone back into a factory configuration.
And make sure you erase the existing files first, on my Moto G I normally erase all of these
mfastboot erase boot
mfastboot erase system
mfastboot erase userdata
mfastboot erase cache
mfastboot erase webtop
mfastboot erase preinstall
But moto X is probably different
RogerClark said:
I've not personally experienced this, but I think you are supposed to make sure you reboot back onto recovery after flashing TWRP because some systems will overwrite TWRP the next time you boot.
If you can get hold of the original ROMs for the phone, (search this forum). I'd recommend perhaps you flash them first, using mfastboot, and get the phone back into a factory configuration.
And make sure you erase the existing files first, on my Moto G I normally erase all of these
mfastboot erase boot
mfastboot erase system
mfastboot erase userdata
mfastboot erase cache
mfastboot erase webtop
mfastboot erase preinstall
But moto X is probably different
Click to expand...
Click to collapse
What do you refer with factory configuration? Actualy the phone are supposed to be on Stock. The phone has never unlocked by bootloader, i'm almost sure of that. So, for that reason i suppose the phone had never another rom.
Maybe i can be wrong, but. Why do you thing there are missing files?
Hi,
I search the recovery.img of Oukitel K10.
I have make OEM Unlock, and I can get fastboot.
I have find many fake websites to hot to do this, but realy don't trust (last time I have brick my K10000 Pro).
The better way is now to "fastboot boot test.img" and see if my phone boot before flash anything.
But I dont find a recvery.img who boot my phone
I have the "fake" ROM (I search inside, and it's seem match as mine)
The other problem is SP flash tools don't want to get me my NVRAM ...
Anyone have root is K10 ? (I have a brick until my device is not root, I don't use it in stock ROM !)
So I finaly test the "normal" way, whit the SP Flash tool method, and it's works.
I don't know why, when I fastboot the image, the phone won't boot, but whith flashtools, it's works.
I have now My Oukitel K10 rooted, and cleaned
So, what did you use to root it?
Yea can u tell us how you did it atep by step. My flashlight its not working andi cant hear a thing on Bluetooth... Need to root this.. or someone else knows how to fix it?
I actually found a step-by-step guide here:
https://www.getdroidtips.com/twrp-recovery-oukitel-k10/
But, i got stuck at downloading the image over my phone,.... i never get green light after flashing....
The phone functions normal, after... because nothing flashed i guess...
And that guide is incomplete, you need to first disable digitally signed drivers check, otherwise the preloader won't work at all...
Did anyone else try it?
What do you guys get?
Mind to share your knowledge? How you obtain your Oukitel K10 rooted cleaned?
I've got this phone today. Here is my quick root procedure.
1. Prepare a magnifiying glass for reading messages on your phone.
2. Download SuperSU (ZIP) and TWRP for oukitel k10.
This one works for me (OKITEL_K10_V121_20180112).
3. Reboot to bootloader.
VOL-DOWN+POWER
4. Unlock bootloader. It will destroy /data now.
fastboot oem unlock
# VOL-UP confirm
5. Reboot to system, then reboot to bootloader again.
6. Flash recovery
fastboot flash recovery recovery.img
7. Reboot to recovery
# Hold VOL-UP
fastboot reboot
8. Format /data again
because no one knows password
9. Install SuoperSU.zip
Advanced - sideload -swipe # <-- on phone
adb sideload SuperSU-v2.82-201705271822.zip # <-- on computer
10. Reboot to system, setup and install SuperSU from market.
Now you should have root.
sergey1369 said:
I've got this phone today. Here is my quick root procedure.
1. Prepare a magnifiying glass for reading messages on your phone.
2. Download SuperSU (ZIP) and TWRP for oukitel k10.
This one works for me (OKITEL_K10_V121_20180112).
3. Reboot to bootloader.
VOL-DOWN+POWER
4. Unlock bootloader. It will destroy /data now.
fastboot oem unlock
# VOL-UP confirm
5. Reboot to system, then reboot to bootloader again.
6. Flash recovery
fastboot flash recovery recovery.img
7. Reboot to recovery
# Hold VOL-UP
fastboot reboot
8. Format /data again
because no one knows password
9. Install SuoperSU.zip
Advanced - sideload -swipe # <-- on phone
adb sideload SuperSU-v2.82-201705271822.zip # <-- on computer
10. Reboot to system, setup and install SuperSU from market.
Now you should have root.
Click to expand...
Click to collapse
I am not able to get to bootloader how to do that? voldown and power button does nothing but restarting phone everytime.
Hello. Turn off your phone first. Then hold button and turn it on. Be carefull - font is too small in menus.
sergey1369 said:
Hello. Turn off your phone first. Then hold button and turn it on. Be carefull - font is too small in menus.
Click to expand...
Click to collapse
I did turn off the phone then pressed power button and volume down button at a time then kept pressing it till logo came. as soon as I release them .. Phone just get started, instead of going to bootloader
Can anyone share recovery img file? I cant find anywhere.
Hi, you need Vol-up+Power.
It takes about 11 seconds on my phone.
Choose Fastboot mode with Vol-up and
confirm selection with Vol-down.
sergey1369 said:
Hi, you need Vol-up+Power.
It takes about 11 seconds on my phone.
Choose Fastboot mode with Vol-up and
confirm selection with Vol-down.
Click to expand...
Click to collapse
Thanks a lot for reply .. yes it gives me recovery propmpt
Have you got K10 Recovery? Cant find anywhere. The one link given here. Takes me to other website which need to paid membership and I tried to pay but Cant pay via paypal and developer inbox is full so cant contact him too.
Oh, that's weird, it was free. Here is a copy
Anyone know how install cleaned rom?
I keep getting bootloops as soon as I try to flash Magisk. I have no trouble flashing and starting up TWRP, but after flashing I can´t reboot to system. I also get the warning from my Pc when I connect my phone that it doesn´t recognize it. It reboots fine if I don´t flash anything. Any help? I also tried the steps on page 1 (Bootloader is successfully unlocked).
SuperSu works, but fails Safety Net, that´s why I want Magisk.
k10 ROOT
Hello Friend,
I have a K10 but I have not been able to do the ROOT, can you help me ??
What is the procedure?
FukTheRegister said:
So I finaly test the "normal" way, whit the SP Flash tool method, and it's works.
I don't know why, when I fastboot the image, the phone won't boot, but whith flashtools, it's works.
I have now My Oukitel K10 rooted, and cleaned
Click to expand...
Click to collapse
Hey there and sorry for the late response. What steps did you do so far? Is your bootloader unlocked already? Or are you at the start and this is your first try? If it is your first try, here is a step by step guide on what to do and what you will need.
What you need:
1. The SP Flash Tool and its drivers. You can find them on the Oukitel website or in the internet. Search for SP Flash Tool and download the latest. For the drivers it´s best to get them from Oukitel. Lower right side of their website and then click Latest software Rom and choose the K10.
2. The adb and fastboot drivers. Search them on the internet.
3. Your Smartphone.
4. A computer and the data cable.
5. The SuperSU 2.82 S3 files from chainfire. Again, search them on the internet.
6. The TWRP Image from this thread.
If you have everything, you do the following:
1. If you have used your phone already, safe everything you want to keep on your computer! You will have to erase your data at least once in the process!
2. Turn your phone on and go to settings.
3. Then tap on About your phone and scroll all the way down to see its build number.
4. Tap on that 7 times in a row to get the message: Congratulations you are now a developer. Go back to the settings to see a new option, the developer options.
5. Go to the developer options and tap on allow oem unlock and also tap on enable debugging options.
6. Leave the settings and connect your phone to your computer. Push the SuperSU file to your sd card (Magisk unfortunately does not seem to work and results in a bootloop at least for me).
7. On your computer, go to the folder where you saved the adb.exe and fastboot.exe. Hold shift and open a power shell or command window in there (don´t actually know the steps for a Mac or Linux computer, sry).
8. Now type adb devices and confirm the access on your phone. If your phone doesn´t show up or there is no confirmation message on your phone, type adb kill-server and then adb devices.
9. Once your phone is confirmed, you type adb reboot-bootloader.
10. Now type fastboot oem unlock and press the volume up button on your phone to confirm the bootloader unlock.
11. Your phone will now erase your data (internal storage only, your sd card will not be touched, but may need to be set up and formatted again if it was used to extend the internal storage).
12. On your computer, type fastboot reboot and set up your phone again (just the basics, because you will have to erase it again). Don´t forget to turn on the debugging mode again.
13. Open up the SP Flash Tool on your computer and choose the scatter file from the twrp image (custom recovery). Only recovery should be ticked. Hit the download all button, connect your phone to computer and turn off the phone. Now wait till there is a green hook on your computer. This means, the download has been successfull.
14. Get to recovery mode on your phone by holding the volume up and power button at the same time and choose the first option, then hit the volume down button to enter recovery mode.
15. From here, go to the settings in the upper right corner and choose your language (ignore the message of the password and hit back).
16. Now go to Wipe and format your data.
17. Hit the restart button and press Recovery. Allow it to modify the system and pull the slider.
18. Now go to Install, choose your sd card and press SuperSU. Let it run through the process. Then restart and press system. First time the boot may take a while, so be patient.
19. Set up the phone and enjoy your root.
Magisk 17.1
Magisk 17.1 install AS IS, no warranty, no testing (yet).
!!! You can lose your data or brick your phone !!!
0. Don't try default install or upgrade via MagiskManager - you'll get bootloop.
1. You can try this boot-magisk.img (AIK repacked with force encryption and dm-verity enabled).
It works for me, but I did factory reset before trying.
- boot.img comes from OUKITEL_K10_V12_20180112.rar (I'm not sure about file's source)
fastboot flash boot boot-magisk.img
2. If your phone freeze on Oukitel logo, don't touch it. Wait.
If you stop phone here, you'll lose your data.
There is no way back - it starts data encryption.
3. If it fails, try flashing stock boot back and factory reset your phone.
fastboot flash boot boot.img
That modified boot.img did the trick. What did you modify to make it work?
The forced encryption, however, is annoying. Is there a possibility to undo that?
help ... Oukitel K10
I flash firmware Oukitel K10 by SP_MDT_v3.1828 (Format and Download All). now : looked picture(red font). Phone call ok. please help me. I from Vietnam. Thankyou!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hey,
I had read in a few posts on xda that oppo had locked/disabled fastboot mode on their devices. I was wondering if somebody could test if adb reboot bootloader or adb reboot fastboot are working on the Find X and if so fastboot oem unlock is working?
Thanks in advance
i can confirm that Fastboot mode here it seems to be factory disabled.
adb reboot bootloader it only reboot device on normal OS and "Enable OEM Unlocking" switch it seems to be dead
Disabled mode:
fastboot mode
Avaiable mode:
Recovery Mode :
(adb reboot recovery)
Turn off your device.
Press and hold the Volume down and Power buttons simultaneously until the device turns on.
Qualcomm EDL Mode
(adb reboot edl)
Turn off your device.
Press the Volume Up and Power buttons and connect the USB Cable to the phone.
EDL => Emergency Download Mode
snowwolf725 said:
Disabled mode:
fastboot mode
Avaiable mode:
Recovery Mode :
(adb reboot recovery)
Turn off your device.
Press and hold the Volume down and Power buttons simultaneously until the device turns on.
Qualcomm EDL Mode
(adb reboot edl)
Turn off your device.
Press the Volume Up and Power buttons and connect the USB Cable to the phone.
Click to expand...
Click to collapse
Theoretically it's possible to unlock the bootloader and backup the device partitions through EDL right? Can it be used to emulate the functionalities of fastboot?
rezesius said:
Theoretically it's possible to unlock the bootloader and backup the device partitions through EDL right? Can it be used to emulate the functionalities of fastboot?
Click to expand...
Click to collapse
No, you also need OEM-signed programmer.
In addition, it's very hard to unlock bootloader through EDL mode.
Ref:
https://alephsecurity.com/2018/01/22/qualcomm-edl-1/
EDL = Emergency Download Mode
EDL mode is power than fastboot mode, but it's too hard to use.
You can flash specified partition, or resize partition size in EDL mode.
snowwolf725 said:
No, you also need OEM-signed programmer.
In addition, it's very hard to unlock bootloader through EDL mode.
Ref:
https://alephsecurity.com/2018/01/22/qualcomm-edl-1/
EDL = Emergency Download Mode
EDL mode is power than fastboot mode, but it's too hard to use.
You can flash specified partition, or resize partition size in EDL mode.
Click to expand...
Click to collapse
So literally this phone have no future??*
I don't think so. We just have to use what we can. Maybe get twrp installed through recovery mode
I'll recheck how it had to be done on the axon7. But if I remember, it was a similar issue.
We don't yet know what will or will not be unlocked in the international variant. Even if they just give it the OEM slider without an unlocked bootloader you can sometimes get root through magisk. In theory we should soon get owners in India and the Philippines with an international phone and we should have a better idea then as to what we're up against.
Adding insult to injury, when I asked Oppo India if they'll release the kernel source of the Find X, they immediately send a message back point blank refusing to that
rezesius said:
Adding insult to injury, when I asked Oppo India if they'll release the kernel source of the Find X, they immediately send a message back point blank refusing to that
Click to expand...
Click to collapse
Lmao.... killing it bro. Im not surprised from them..
avetny said:
Lmao.... killing it bro. Im not surprised from them..
Click to expand...
Click to collapse
Haha, knowing Oppo's track record it was kinda expected. I was just hoping they'd change their stance. This is truly a beautiful phone screwed over by their stupid policies
rezesius said:
Haha, knowing Oppo's track record it was kinda expected. I was just hoping they'd change their stance. This is truly a beautiful phone screwed over by their stupid policies
Click to expand...
Click to collapse
Absolutely agree sir.
As long as I can get root I can make it do what I want and that is where the line in the sand lies; no root is my deal-breaker.
krabman said:
As long as I can get root I can make it do what I want and that is where the line in the sand lies; no root is my deal-breaker.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
wolfgart said:
i can confirm that Fastboot mode here it seems to be factory disabled.
adb reboot bootloader it only reboot device on normal OS and "Enable OEM Unlocking" switch it seems to be dead
Click to expand...
Click to collapse
Just bought mine in Thailand so I assume it's the global variant. The "Enable OEM Unlocking" works and so does the USB debugging switch. I haven't tried to use fastboot yet.
farang4u said:
Just bought mine in Thailand so I assume it's the global variant. The "Enable OEM Unlocking" works and so does the USB debugging switch. I haven't tried to use fastboot yet.
Click to expand...
Click to collapse
Just bought mine in India and can confirm Bootloader Unlock is availableand should be a piece of cake with OEM Unlock available in the developer options. Oppo Find X is not a mediatek device hence rooting should be easy with kingoroot. I am not rooting risking the security Oppo provides. I am not a developer who can undo it. Hence waiting ...
You have no clue, fastboot is disabled, even in new ColorOS 5.2 beta
yeah no idea we are all bricked with.this.device ?
Bring me in
InspectMyGadget said:
yeah no idea we are all bricked with.this.device
Click to expand...
Click to collapse
If you guys can send me that phone, I'll be able to do some tricks & tries, I've done that before with vivo devices, Oppo is also owned by BBK Electronics, So...
Oppo: Fastboot Disabled
Any update on this issue?
Ive got here an Oppo A7 , purchased for about $280 in the Philippines last December 2018.
"Allow OEM Unlock" can be activated in Developer Options.
But unfortunately "ADB reboot bootloader" seems only to restart the device. Key combinations for fastboot doesnt work either.
Damn stupid brand this is. Goin crazy these past few days untill I saw this thread. never thought of it to be this enthusiast-unfriendly
I flash SAMSUNG GALAXY J3 ORBIT SM-S367VL with Combination File and able to load Factory Binary Mode. Now I revert back to it's original Firmware. In the Factory Binary mode I enable Developer mode(enable OEM unlocking, USB Debugging), Reset Factory Data, and change USB Settings to ACM+DM+UTS+ADB. Now I want to boot the device in downloading mode. But when I pressed Volume Down + Power + Home key the downloading key is not appearing. Instead it shows a screen like below. Can any body help me to resolve the issue. And is there any tutorial available to disable Network Carrier Lock for the device?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
dassoubarna said:
I flash SAMSUNG GALAXY J3 ORBIT SM-S367VL with Combination File and able to load Factory Binary Mode. Now I revert back to it's original Firmware. In the Factory Binary mode I enable Developer mode(enable OEM unlocking, USB Debugging), Reset Factory Data, and change USB Settings to ACM+DM+UTS+ADB. Now I want to boot the device in downloading mode. But when I pressed Volume Down + Power + Home key the downloading key is not appearing. Instead it shows a screen like below. Can any body help me to resolve the issue. And is there any tutorial available to disable Network Carrier Lock for the device?
Click to expand...
Click to collapse
:laugh:
I am able to solve it by using Samsung 300K Tools posted by Speechless
https://forum.xda-developers.com/galaxy-note-8/how-to/samsung-300k-tool-t3847487
dassoubarna said:
:laugh:
I am able to solve it by using Samsung 300K Tools posted by Speechless
https://forum.xda-developers.com/galaxy-note-8/how-to/samsung-300k-tool-t3847487
Click to expand...
Click to collapse
I have the exact same phone, I even have the exact same screen. I tried to 300K tools posted by speechless. It recognizes the phone says it's in download mode but nothing changes on the screen, still reads: power reset or unknown upload mode. It's recognized by Odin the com turns blue,but never moves past 'SetupConnection'. Im not sure if I missed something or its my luck of the draw. Ive triple check everything list you had done. No idea at this point. Ordered a jig. Last ditch effort.
you will have to use an adb fastboot folder and enter the "adb reboot download" command and you will be able to install the firmware by odin.
Pollo367 said:
you will have to use an adb fastboot folder and enter the "adb reboot download" command and you will be able to install the firmware by odin.
Click to expand...
Click to collapse
This was my first thought when I first gave it a go. I have no adb connection with computer (device not detected. Recovery sideloading isn't possible, no USB connection read by computer. Drivers are installed, Dev options all correct (oem unlock checked, USB debug checked. Nothing has been overlooked, just completely stumped. I noticed I have permission thru Bluetooth to possibly install apps, but all attempts have proven faulty. I know it's not the USB port itself, I do get Samsung Modem detected if I force it into Power Reset/Unknown upload mode . USB jig didn't work, phone seems to ignore it's presents. I'm absolutely dumbfounded on this one.
Bump!
I have the same exact phone and am facing the same exact issue.
A friend gave me the phone. They had factory reset it before giving it to me. I could not proceed with the setup because of google verification. Asked the friend about it but they do not know the credentials, so I'm guessing they got the phone from someone else. Who knows?
After doing some research, I found combination roms to get rid of the google verification.
I was able to get the phone into download mode and used odin to flash the factory binary rom.
I then used the phone to enable USB debugging and OEM unlocking.
That is as far as I have gotten and I've spent two days searching for answers.
I can no longer get the phone into download mode and I've tried every supposed solution under the sun. A myriad of button combinations, both with and without the USB cable plugged into the phone. I've tried taking the battery out and holding down the buttons just after replacing the battery. I've tried holding down the VOL buttons just before plugging in the USB cable. Nothing works.
This is where my issue is a bit different from the OP's problem. I can get into recovery mode and I have the option to apply update through ADB.
In the CMD prompt on my PC, I use the command adb devices and it shows the phone connected and sideloaded, however no commands work for the phone itself. I can't apply any sort of rom. I can't push or pull files. I can't reboot or reboot download. It just says error: closed.
The phone in the ADB update mode says E:Failed to set driver control. No such device.
Installation Aborted.#1
E:Failed to set driver control. No such device.
I have literally tried everything. I don't need the phone, mind you. I have a google pixel and another Samsung galaxy that I had before the google phone. I just really want that feeling I get when I breathe life back into an otherwise useless device
That being said, I know that the Samsung Galaxy J3 Orbit (SM-S367VL) isn't a great phone but it could still serve a purpose if I could just get it to work.
If anyone can shed any light on the situation, I would be quite thankful.
with the mobile shown dial * # 0808 # and mark where it says adb and restart. then with the mobile on again open an adb fastboot folder and insert the command "adb reboot downloader" with the normal taught mobile (do not put power + button -). He will send them directly to downloader mode.
Do not try to put the phone in download mode with power button + volume button -. the command will send them with the mobile taught normal to downloader
With the j3 orbit sm-s367vl i flashed the factory binary then kept haveing the same issue about getting it to actually go into download mode best way i have found is by useing miracle box 2.27 an up to get it to go into download mode. Just have the phone powered on connect to computer open miracle box go to samsung tab scan ports select thr comport for your samsung an switch the auestion mark to where it says download mode an click go then it sends your j3 orbit into thr correct download mode you need to be able to flash the firmware
Hello,
Thanks for decently compiled guide to the OP. The steps are easy to follow and one can achieve this.
Tip: Incase you're stuck at the last step of trying to flash the CSC and your phone is booting into Factory Binary again, follow below steps -
1. Enter the Factory Binary Mode
2. Enable USB debugging on your device if needed.
3. Run adb on your computer (assuming you have it installed)
4. Connect your device to PC by USB cable
5. Verify device is recognized by adb devices
5. To boot into download mode for Samsung devices type in cmd window :
adb reboot download
6. Voila! Phone boots into download mode and you can install the firmware using Odin now.
dassoubarna said:
I flash SAMSUNG GALAXY J3 ORBIT SM-S367VL with Combination File
Click to expand...
Click to collapse
Can you provide link to the S367VL Combination File please? Also, what exactly is the combination file? Is it a custom ROM? I have not been able to find any for this specific phone yet. Stock Tracfone/Samsung configuration is loaded with bloatware and I can't find accurate information on how to root it.
amy91 said:
Hello,
Thanks for decently compiled guide to the OP. The steps are easy to follow and one can achieve this.
Tip: Incase you're stuck at the last step of trying to flash the CSC and your phone is booting into Factory Binary again, follow below steps -
1. Enter the Factory Binary Mode
2. Enable USB debugging on your device if needed.
3. Run adb on your computer (assuming you have it installed)
4. Connect your device to PC by USB cable
5. Verify device is recognized by adb devices
5. To boot into download mode for Samsung devices type in cmd window :
adb reboot download
6. Voila! Phone boots into download mode and you can install the firmware using Odin now.
Click to expand...
Click to collapse
Thank-you so much!!! This worked for me on my J3 Orbit. I had thrown it in a drawer back in September thinking it was a lost cause after trying seemingly everything to put it into download mode. I dug it back out last night because my son needed a phone. Thank-you for the easy to follow instructions and your time.
dassoubarna said:
I flash SAMSUNG GALAXY J3 ORBIT SM-S367VL with Combination File and able to load Factory Binary Mode. Now I revert back to it's original Firmware. In the Factory Binary mode I enable Developer mode(enable OEM unlocking, USB Debugging), Reset Factory Data, and change USB Settings to ACM+DM+UTS+ADB. Now I want to boot the device in downloading mode. But when I pressed Volume Down + Power + Home key the downloading key is not appearing. Instead it shows a screen like below. Can any body help me to resolve the issue. And is there any tutorial available to disable Network Carrier Lock for the device?
Click to expand...
Click to collapse
Samsung download jig is what you need. It will force the phone into download mode. I had this same problem and it worked. They are only a few bucks to order online. But if you're like me and don't want to wait there are instructions online that tell you how to make one. Which was easy enough. I was able to do it without having any prior knowledge on that stuff. Hope this helps
So am I understanding correctly, that once the SM-S367VL Tracfone has ODIN on it, the stock ROM on the phone is then opened up and rooted and can be put on any compatible CDMA network like Verizon as long as you have a SIM card to use on Verizon for it?
Thanks so much for the information. Very much appreciate all the hard work done here.
Lip Lip Lip
Errrr Wait.....flashing SAMSUNG's Stock ROM for the phone (A Tracfone purchased at Walmart and never activated), VS the Tracfone ROM that is on it, is all that is necessary to do because then the phone is carrier unlocked as it is no longer running the Tracfone ROM but the Samsung Stock ROM......is this correct, please?
Thanks.
Lip Lip Lip
P.S. I know I sound Ultra NEWB here asking this, but I am totally unfamiliar with this particular phone.
I have hacked TONS of phones using TWRP.....Galaxy Nexus....and my new Moto G5s+ SE's and used Tiny's hack for the 2007 Droid INC Version 1 to get Android 4.4.4 on it (RUNS GREAT!) and Clockwork MOD initially and then TWRP 2.6.3.0 after a bit, so I know what's up, but am hoping someone can point me in the right direction so I don't brick the phone.
Need to know if I am flashing the combo package mentioned in this thread earlier (and where to get that) or if the goal is to just root the ROM via ODIN once it is in Downloader mode.
Or do you actually install ODIN to it as a recovery?
Never used ODIN either before.
Always been using ADB and flashing Clockwork mod or TWRP and then off to the races from there.
A LITTLE HELP PLEASE?!?!?!?!
8)
Lip Lip Lip
S367vldu1arg2
need help finding the combination file for Samsung j3 orbit tracfone net10 - no OEM unlock- I want to unlock boatloader then flash
thanks
i think downloading mode you use the volume up button
Once the combination is flashed, to reboot into Download mode, hold Home + Vol Down while plugging in the usb cord. Figured THAT out, now if only I could figure out how to flash stock firmware back, ANY of them! Either get a version error about the bootloader, or Odin flies through the flash, says PASS! but has absolutely no effect on the phone... Crap.
Any ideas??
Entering Download mode on factory firmware & flashing with ODIN
grasshoppa420 said:
Once the combination is flashed, to reboot into Download mode, hold Home + Vol Down while plugging in the usb cord. Figured THAT out, now if only I could figure out how to flash stock firmware back, ANY of them! Either get a version error about the bootloader, or Odin flies through the flash, says PASS! but has absolutely no effect on the phone... Crap.
Any ideas??
Click to expand...
Click to collapse
sammobile doesn't carry the tracfone ROM for this model unfortunately. You can get the stock firmware from hardreset.info but you need to reboot into reovery and check the binary revision... the Ux number in the PDA version, that has to match on whatever you're flashing the phone with until you have the bootloader unlocked, then you can flash it or backflash it with whatever you want.
As for carrier unlocking it, you'll have to pay for that one, just flashing the stock binary for the J3 from Samsung won't remove that. Although I am curious as to whether the TMO J3 Orbit firmware will flash onto the TracFone version... You should be able to change the CSC with the factory firmware and ODIN.
the adb reboot download worked for me when stuck on factory binary mode
Hello all, I've been trying to install /e/ os GSI on my Redmi Note 11S. I already unlocked the bootloader.
Whenever i tried flashing system.img, (with boot.img patched manually via fastboot, not via a custom recovery), the phone would only boot fastboot. So I tried installing this custom recovery, and patch boot.img from there, but that still wouldn't work (though the recovery at least worked). So I tried installing the stock ROM, and try something else.
I went with latest fastboot EEA image and ran flash_all.sh (worked last time I tried), but this time I got an error (something about partition preloader not found). So I restarted the phone after which it got stuck in this bootloop. Can't boot into fastboot, nor recovery. Instead, the phone keeps flashing the mi logo on and off every 5 seconds. fastboot on my Linux install can't detect the phone. My Windows 10 install can't find it either, though it plays the "device connected" sound followed by the "device disconnected" sound shortly after. I can't turn the phone off either. Windows 10 USB drivers worked, or at least when I was unlocking the bootloader, so I don't think the issue is there. Any idea how to fix this?
Thank you in advance
Edit: Typos. Also I noticed that it only plays the "device connected" and "disconnected" sounds on Windows 10 only when i hold down the power and vol- buttons.
UPDATE: This tool can at least detect the phone, though I do get this error afterwards:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
UPDATE: Managed to get FASTBOOT back, thanks to this kind stranger (system is still unbootable).
UPDATE: IT'S ALIVE! Did a quick install_all.sh on the stock ROM, and it's working again! Thank you all for helping me resolve this problem
no idea
Normally you use flashall.bat and not .sh, try using flashall.bat and hopefully you'll get out of the bootloop.
Try following my "how to fix bootloop" guide again, atleast till step 4 when you get the fastboot mode back up again.
warhead1721972 said:
Normally you use flashall.bat and not .sh, try using flashall.bat and hopefully you'll get out of the bootloop.
Try following my "how to fix bootloop" guide again, atleast till step 4 when you get the fastboot mode back up again.
Click to expand...
Click to collapse
Could you send a link to the guide please? The only guide I could find on your profile is the one with the rooting, which is among the first guides I tried and it was the one to get me into this situation. Note that in your guide, it appears that you can at least get to the FASTBOOT screen, which I can't. My phone just stays on the logo for 5 seconds before rebooting, and no matter which buttons I press or hold, I can't get it to go to the FASTBOOT screen.
Also, what's the difference between flash_all.bat, and flash_all.sh, aside of one being for Linux and the other for Windows?
UPDATE: This tool can at least detect the phone, though I do get this error afterwards:
kritomas said:
Could you send a link to the guide please? The only guide I could find on your profile is the one with the rooting, which is among the first guides I tried and it was the one to get me into this situation. Note that in your guide, it appears that you can at least get to the FASTBOOT screen, which I can't. My phone just stays on the logo for 5 seconds before rebooting, and no matter which buttons I press or hold, I can't get it to go to the FASTBOOT screen.
Also, what's the difference between flash_all.bat, and flash_all.sh, aside of one being for Linux and the other for Windows?
Click to expand...
Click to collapse
Press and hold all the 3 buttons, vol +, vol - and power button at the same time, till you see the phone switched off for a few seconds.
Then press the power and vol - button to get to the fastboot mode.
About the flashall.bat, I completely forgot that you were using Linux my bad.
Also sometimes some drivers don't work well in Linux try using windows.
Did you follow the guide which was at the end of this?
warhead1721972 said:
Press and hold all the 3 buttons, vol +, vol - and power button at the same time, till you see the phone switched off for a few seconds.
Then press the power and vol - button to get to the fastboot mode.
About the flashall.bat, I completely forgot that you were using Linux my bad.
Also sometimes some drivers don't work well in Linux try using windows.
Did you follow the guide which was at the end of this?
Click to expand...
Click to collapse
Yes, that's the one, and it won't go into fastboot.
Isn't /e/ Murena GSI just android 10? I am pretty sure it won't work. I had the same problem, but I fixed it by installing stock ROM..
And that /e/ GSI is not actively developed and not even in beta stage (not usable at most cases)
Don't use SP Flash tool for full flash this phone seriously, Sp flash tool will make your phone stuck in recovery miui and show Nvdata Corrupted even you choose download only mode.
for now try to use mtkclient to flash boot.img only to both side A&B.
move your boot.img to mtk client folder
open cmd on that folder
type this command:
Code:
python mtk w boot_a,boot_b boot.img,boot.img
and try turn on your phone.
if still can't boot try to flash one by one img from your firmware
I has your same problem. Just hold the vol- for more than your usually Need and should boot into fastboot and than you flash with flashall.bat
I've sucessfully restore my phone and work as normal.
soutaminori said:
Don't use SP Flash tool for full flash this phone seriously, Sp flash tool will make your phone stuck in recovery miui and show Nvdata Corrupted even you choose download only mode.
for now try to use mtkclient to flash boot.img only to both side A&B.
move your boot.img to mtk client folder
open cmd on that folder
type this command:
Code:
python mtk w boot_a,boot_b boot.img,boot.img
and try turn on your phone.
if still can't boot try to flash one by one img from your firmware
Click to expand...
Click to collapse
Thank you so much, it worked!!!
I think. It's now at least on the FASTBOOT screen, which is progress. And the MIUI recovery is now back as well. While the system is still unbootable, I think I can take it from here. Thank you
Hypeka said:
I has your same problem. Just hold the vol- for more than your usually Need and should boot into fastboot and than you flash with flashall.bat
I've sucessfully restore my phone and work as normal.
Click to expand...
Click to collapse
That's the first thing I tried, and no luck. But I fixed it now (I think).
Very welcome, Glad to hear that
Note for everyone:
Backup this partition it's very important.
nvcfg.img, nvdata.img, nvram.img, persist.img, proinfo.img, protect1.img, protect2.img, md1img.img
Thats all partition about imei, security and network configuration for ur device. CMIW.
mtkclient also can do that,
and it's the clue:
Code:
python mtk r nvcfg,nvdata,nvram,persist,proinfo,protect1,protect2,md1img nvcfg.img,nvdata.img,nvram.img,persist.img,proinfo.img,protect1.img,protect2.img,md1img.img
Check ur mtk client folder, now you got the back up.
u can also use this Partitions Backup & Restore this tool don,t need PC for backup and restore, but i'm not really sure can be work perfectly. i just try for boot partition and its worked.
cheeerrss
Hi. Could you help me to unbrick my Note 11S 4g? I faced with bootloop after trying rooting phone by twrp. And now i can`t enter to fastboot.
When i try to - python mtk w boot_a,boot_b boot.img,boot.img
Or when I try to disable auth brom i have another one issue.
alzhuks said:
Hi. Could you help me to unbrick my Note 11S 4g? I faced with bootloop after trying rooting phone by twrp. And now i can`t enter to fastboot.
When i try to - python mtk w boot_a,boot_b boot.img,boot.img
Or when I try to disable auth brom i have another one issue.
Click to expand...
Click to collapse
i can't see mtk client log. but maybe driver problem or try to unlock BL again with THIS TOOL
alzhuks said:
Hi. Could you help me to unbrick my Note 11S 4g? I faced with bootloop after trying rooting phone by twrp. And now i can`t enter to fastboot.
When i try to - python mtk w boot_a,boot_b boot.img,boot.img
Or when I try to disable auth brom i have another one issue.
Click to expand...
Click to collapse
I myself did it with the terminal and on Linux. I didn't use the GUI, so I can't help with that. Could you send a higher res picture of the terminal please? We can't really see anything.
If you're doing this on Windows, then my guess is a driver issue (I did have to install a special driver for Windows to work with Fastboot, could be that mtk needs it too).
Hi All,
I unbricked my phone by using fresh release of mtkclient (https://github.com/bkerler/mtkclient).