Related
Hi Evryone.
Because I didn't found CWM or TWRP Recovery or any root method for the galaxy J5 J5108 and the J7 J7108, I made a pre-rooted firmwares for those models.
This firmware base on the hong kong firmware which include the Google apps, this a full firmware exactly like the original, except the root.
After flash you will see the SuperSU app in the app drawer.
Also, this firmware contains the bootloader from the china firmware which doesn't have frp lock.
The root include the binary files in the system, and a pathed boot. (from Android 6.0 or samsung 5.1.1 pathing the boot is necessary for the root work properly)
Flashing this firmware will not wipe data automaticly. you should not lose anything.
This file will work on any firmware/baseband/csc. you can always flash it like a stock firmware.
J5 - base on - J5108ZHU1APD2.
Android version: 5.1.1
J7 - base on - J7108ZHU1APD1.
Android version: 5.1.1
Downloads
J5
http://www.mediafire.com/download/o8hfu81j3j4irjt/J5108ZHU1APD2_Rooted_by_avicohh.exe
J7
http://www.mediafire.com/download/z7bh4sdmzqer6nb/J7108ZHU1APD1_rooted_by_avicohh_v2.exe
Installation instructions
Before flashing check the CROM Service status in Download mode, if it locked you will need to unlock the bootloader first with the app attached.
Install samsung usb drivers from here.
Download the self extracting 7z file above and extract it (just double tap) to some folder, you should receive a tar.md5 file.
Open odin 3 (attached in the zip)
Put the tar.md5 file in AP.
Put the device in download mode. (vol down + home + power button, and then click on vol up)
Connect your phone to usb and wait for odin detect the device.
Click start.
After it finish choose reboot system now in recovery.
Enjoy.
If you want to thank me for this work, you can do this by donating.. :good:
Thanks a lot avicohh. This was simple and painless. I now have google services on my mainland China phone. And root too! And like you said - I did not loose anything.
well now i am stuck. I enabled my google account, installed and updated my apps through google play, shutdown and now I can't boot. The message in red on the top of the boot screen is:
"KERNEL IS NOT SEANDROID ENFORCING
Custom Binary blocked by FRP lock."
I also cannot reflash the same HK rooted firmware using Odin
apparently I should have enabled developer options then enabled OEM unlocking before rebooting. But I didn't know that so for now I am bricked
Also apparently, the fix for it is to reflash the original firmware using Odin. I am now downloading the firmware from http://updato.com/firmware-archive-select-model?record=1F170CA05E5611E6B055FA163EE8F90B but it is still another 2-3 hours to complete the download (yes, poor internet connection here.)... So I'll see how that goes...
OK, that didn't work. Now the message on the download mode screen says:
SW REV. Invalid type.
FRP is enabled, not allow download non FRP bootloader binary
Well..
I just recently had the same problem in another device.
I don't think the "Oem unlock" has nothing to do with this. the problem is that when you're adding Google account the frp (factroy reset protection) is automaticly enabled, and then it blocks the pathed boot.
The reason reflash the original firmware didn't work for you is because you tried to flash the china version, that doesn't have google service and also doesn't have frp in the bootloader. (apparently once frp is enabled this kind of operation is not allowed because you are actually trying to remove the frp lock by flashing bootloader..)
I think the solution will be to flash the original hong kong firmware with the frp bootloader and original boot. (or just the original boot)
http://updato.com/firmware-archive-select-model?record=5C13445B54D811E6B055FA163EE8F90B
Then, try to enable the "Oem unlock" option and finally flash the rooted firmware again.
maybe it will work, I'm not sure about it but I would like to know.
If this won't work, I'll try to combine the rooted hong kong firmware with the non-frp bootloader from the china firmware.
Thanks so much for replying avicohh
avicohh said:
Well..
The reason reflash the original firmware didn't work for you is because you tried to flash the china version, that doesn't have google service and also doesn't have frp in the bootloader. (apparently once frp is enabled this kind of operation is not allowed because you are actually trying to remove the frp lock by flashing bootloader..)
Click to expand...
Click to collapse
This makes sense. I was actually suspecting this and was considering trying the 6.01 HK version since that is the only one I could find: http://updato.com/firmware-archive-select-model?record=5C13445B54D811E6B055FA163EE8F90B
Now that you've posted a link to your original 5.1 HK firmware I'll try what you suggest. I'll wait to get home before I start the download.
But I still wonder if the 6.01 would work on my phone?
It's a mistake.
This link above is 5.1.1, not 6.0.1.
There is no 6.0.1 fro this model for now.
yes, I see, the website says its 6.01, but its actually 5.1.1. How do I know? BECAUSE IT WORKED!!! It took 7 hours to download but when I got up this morning it was done, I flashed and it worked!!!
I'm going to read up some more on this FRP business before flashing the rooted version again. My old phone (very old) had no such thing. I'd never heard of it till this unpleasant way of learning about it.
downloading
Same problem downloading the stock firmware from http://forum.xda-developers.com/gal...108-how-to-root-galaxy-j7-2016-model-t3426967
I hope this works....
---------- Post added at 12:27 AM ---------- Previous post was at 12:26 AM ----------
Tukuvai said:
Same problem downloading the stock firmware from http://forum.xda-developers.com/gal...108-how-to-root-galaxy-j7-2016-model-t3426967
I hope this works....
Click to expand...
Click to collapse
I meant http://updato.com/firmware-archive-s...55FA163EE8F90B
Hi guys.
Thanks for your replies.
I've just checked it now on another device.
As it turn out after a several tests, this "custom binary blocked by frp lock" problem occurs only if the oem unlock option is disabled.
Here is what I did, step by step:
First, I enabled the oem unlock option and then I added Google account - nothing happened. frp lock in Download mode is still off and everything working fine.
I removed the google account, turned off the oem unlock option and finally added the google account again - frp lock in download mode immediately switch to on, and when I tried to restart, the device has stuck on the boot. (custom binary..)
I flashed stock firmware (from the link above), the device now bootup normally but the frp lock in download mode is still on. (I didn't remove the google account yet)
Final check - I enabled the oem unlock again, and the frp lock in download mode switch to off.
So..
I can safely say that all you need to do is just enable oem unlock in developer options, and then flash the rooted firmware.
Anyway, to be even more sure, I made a new firmware with the china bootloader, frp now is not even exist in download mode.
You can download the new firmware from here
http://www.mediafire.com/download/z7bh4sdmzqer6nb/J7108ZHU1APD1_rooted_by_avicohh_v2.exe
Good luck!
avicohh said:
Hi guys.
Thanks for your replies.
I've just checked it now on another device.
As it turn out after a several tests, this "custom binary blocked by frp lock" problem occurs only if the oem unlock option is disabled.
Here is what I did, step by step:
First, I enabled the oem unlock option and then I added Google account - nothing happened. frp lock in Download mode is still off and everything working fine.
I removed the google account, turned off the oem unlock option and finally added the google account again - frp lock in download mode immediately switch to on, and when I tried to restart, the device has stuck on the boot. (custom binary..)
I flashed stock firmware (from the link above), the device now bootup normally but the frp lock in download mode is still on. (I didn't remove the google account yet)
Final check - I enabled the oem unlock again, and the frp lock in download mode switch to off.
So..
I can safely say that all you need to do is just enable oem unlock in developer options, and then flash the rooted firmware.
Anyway, to be even more sure, I made a new firmware with the china bootloader, frp now is not even exist in download mode.
You can download the new firmware from here
http://www.mediafire.com/download/z7bh4sdmzqer6nb/J7108ZHU1APD1_rooted_by_avicohh_v2.exe
Good luck!
Click to expand...
Click to collapse
Hey, How do I enable OEM unlock when I can't even boot my device. it simply refuses to boot.
Hi
First flash the original HK firmware from here. the device should boot up normally.
http://updato.com/firmware-archive-select-model?record=5C13445B54D811E6B055FA163EE8F90B
Then, enable oem unlock.
Thanks for making the root version of mainland firmware. I'm going to stick with the HK version as I want to have google services. and thanks for testing the oem unlock
I informed myself some more about FRP and OEM unlock and I am now feel safe to use the rooted HK firmware. Except, I came across one note for which I want further clarification before proceeding. The note is from http://www.androidcentral.com/factory-reset-protection-what-you-need-know and it says:
"A couple notes need added here. This doesn't undo Samsung's (or anyone else's) version of Reactivation Lock. If you've enabled data reset protection through your Samsung account, you'll need to turn that off in your Security settings. You can find the switch under the "Find My Mobile" section."
So, I want to be sure I don't have this samsung Reactivation Lock enabled. and that I am in no danger of it auto-enabling. I believe I am safe but I would like to know if anyone has more clear information.
What I do know is before I flashed to HK ROM, when I went into download mode, there displayed a setting:
"REACTIVATION LOCK: OFF"
now, using the HK ROM, it is gone, but in that exact same location is the setting:
"FRP LOCK: OFF"
I think, that means the mainland version of the FRP lock (Samsung Reactivation Lock), is now replaced with the google FRP lock and as I don't have to worry about the samsung reactivation lock anymore. Is that so?
even so, as the article says, I look in "Settings" >> "Lock screen and security" >> "Find my mobile" >> log into Samsung Account when prompted, then it does not display the "Reactivation Lock" option that is shown in at least one guide that I found. I really think this is further proof I don't have to worry about Samsung Reactivation Lock. Can anyone confirm?
Yes I can confirm.
But pay attention that because of the FRP, is not possible to make a pre-rooted firmware for Android 6.0 and above or 5.1.1 Samsung devices, from firmware contains FRP protection like the HK one.
From those android versions (and above), a pre-rooted firmware (or any root method) must include a patched kernel.
Due to the FRP protection, once it turn on, it detect the custom kernel (boot) and not allow the device to boot. (custom binary blocked by FRP lock)
That's the reason I had to replace the HK bootloader which contain FRP protection, with the China bootloader which contain the Samsung reactivation lock. (instead of FRP, because china firmwares doesn't include any google services)
I don't know what the policy of the Samsung reactivation lock, about custom kernels.
And also I don't know if the Samsung reactivation lock turns on automaticly if you are adding Samsung account. (Like the FRP lock)
And one more thing, I beleive most people don't use Samsung account at all.
So after all this,
If it come to decision what to use, the FRP lock or the Samsung one (depends only in the bootloader), I'm pretty sure that in this case (custom boot), the best is to use the Samsung lock, and just dont add Samsung account, or add Samsung account if needed but turn off the Reactivation lock in the Find my mobile settings.
I hope it help you a bit.
Good luck.
btw, If you can check the Samsung lock after root and report here, it would be great.
avicohh said:
Anyway, to be even more sure, I made a new firmware with the china bootloader, frp now is not even exist in download mode.
You can download the new firmware from here
http://www.mediafire.com/download/z7bh4sdmzqer6nb/J7108ZHU1APD1_rooted_by_avicohh_v2.exe
Good luck!
Click to expand...
Click to collapse
Oh, at first I thought you meant you rooted the mainland firmware. Now, based on your later post, I believe what you did was to put the mainland bootloader in the rooted HK firmware. Is this the case? If so, that means I can still have google services, and root, and no possibility of FRP issues because its a mainland bootloader. OK, I will try tonight. The Samsung reactivation lock is off by default. Even adding a Samsung account does not turn it on, you have to go into "find my phone" to turn it on. So it should be safe. I will confirm tonight after I download your new firmware.
Yes, this is exactly what i did.
Thanks for testing the samsung account. so it is pretty safe.
yes, this new version with mainland bootloader is good. It seems almost impossible to lock.
Now when I go to download mode, there is no more "FRP LOCK: OFF". in its place is "REACTIVATION LOCK: OFF".
Just for fun I tested by going inter developer options and turned off OEM unlock - then I tried to reboot = success. Enter download mode = still "REACTIVATION LOCK: OFF". Of course I turned it back on again after the test.
and in settings, find my mobile, there is still not a setting for "REACTIVATION LOCK". I have seen an example on the web that this reactivation lock setting should be at the bottom of the options under find my mobile. So, actually now I cannot find any way to turn on the reactivation lock - this is good, its what we want.
Of course to even enter the "find my mobile" section I can do nothing at all (in fact it does not even show me what the options are) untill I give my samsung account credentials. Once I give credentials I can see the options but there is no option to turn on reactivation lock. There is just one thing, maybe, is that in "find my mobile", there a place that says: for more information go to findmymobile.samsung.com. When I go there I have 2 options:
-1) FIND - Find, Lock, Wipe my device
-2) PREPARE - Ready device for Find my Mobile
this "prepare" option I am afraid to try, I am afraid it may be the one to enable reactivation lock. Clearly it is not required to actually find my mobile because I just click the "Find" button and it it finds it for me. So, what would be the use of "prepare"?
At any rate, we know that just creating a samsung account does not activate the lock. I never had a Samsung account before. When I set up this new phone I never did enter developer mode to turn on oem unlock but i did create the samsung account. It was after that I flashed version 1 of avicohh's rooted firmware and when I went into download mode, it said REACTIVATION LOCK: OFF, so creating the Samsung account does not turn it on.
avicohh said:
Hi Evryone.
Because I didn't found CWM or TWRP Recovery or any root method for the galaxy J5 J5108 and the J7 J7108, I made a pre-rooted firmwares for those models.
This firmware base on the hong kong firmware which include the Google apps, this a full firmware exactly like the original, except the root.
After flash you will see the SuperSU app in the app drawer.
Also, this firmware contains the bootloader from the china firmware which doesn't have frp lock.
The root include the binary files in the system, and a pathed boot. (from Android 6.0 or samsung 5.1.1 pathing the boot is necessary for the root work properly)
Flashing this firmware will not wipe data automaticly. you should not lose anything.
This file will work on any firmware/baseband/csc. you can always flash it like a stock firmware.
J5 - base on - J5108ZHU1APD2.
Android version: 5.1.1
J7 - base on - J7108ZHU1APD1.
Android version: 5.1.1
Downloads
J5
http://www.mediafire.com/download/o8hfu81j3j4irjt/J5108ZHU1APD2_Rooted_by_avicohh.exe
J7
http://www.mediafire.com/download/z7bh4sdmzqer6nb/J7108ZHU1APD1_rooted_by_avicohh_v2.exe
Installation instructions
Before flashing check the CROM Service status in Download mode, if it locked you will need to unlock the bootloader first with the app attached.
Install samsung usb drivers from here.
Download the self extracting 7z file above and extract it (just double tap) to some folder, you should receive a tar.md5 file.
Open odin 3 (attached in the zip)
Put the tar.md5 file in AP.
Put the device in download mode. (vol down + home + power button, and then click on vol up)
Connect your phone to usb and wait for odin detect the device.
Click start.
After it finish choose reboot system now in recovery.
Enjoy.
If you want to thank me for this work, you can do this by donating.. :good:
Click to expand...
Click to collapse
sir, you are awesome!!
I'll try to install in my J5108. I will give to my daughter. Is there a form to unroot the phone? Thanks!
Yes.
Just install stock rom.
http://updato.com/firmware-archive-select-model?record=A097D215549D11E6B055FA163EE8F90B
Hello guys,
I'm not a noob when we speak about flashing ROMs and unlocking bootloaders. I've been doing that for some years. Yesterday I flashed the new stock ROM for LG G4 - v29a, android 7.0. Everything went fine. Later this day, I've seen a post claiming that it was possible to relock your bootloader with this specific ROM using the fastboot oem lock. And it worked indeed. The problem now is that when I turn on the phone the following message shows up on RED: "Your device is corrupt. It cannot be trusted and may not work properly".
So, here's the problem:
1 - Can't access recovery;
2- Can't access download mode;
3 - Can't boot normally;
4 - Can't re-unlock since (i guess) the IMEI is now 0;
5 - Can't flash stock ROM using LGUP;
6- Can't erase any partition via adb since the bootloader is now locked;
So, basically all my ways are locked. Any fix you know and want to share?
Hello friends of XDA, I have a big problem between hands, I have a MOTO Z and I had it in android 7.0 since last year the update to andorid 7.1.1 did not arrive and I felt that with android 7 the battery was consumed very quickly, so I tried to find the update to flash it and just about 3 days ago I found it, I proceeded to download it and flash it in fastboot and adb.
The thing is that a few months ago, browsing through my phone (I had already rotated it, and unlocked the bottloader, I decided to re-block the bootloader, and remove the root, which never worked at 100) I got into the developer options, and I saw an option that until then I didn't know about its "OEM Unlock"function, as it was turned on and deactivated because I thought it didn't work.
Returning to the update flashing I proceeded as usual, with the commands, I proceed to restart the device and show the image of the boot of motrola but then it shows me a message in red letters.
"Startup Failed"
"failed to pass validation, backup to fastboot.
I thought it was a compatibility problem with the downloaded version of 7.1.1 so again I decided to flash the stock rom 7.0 but when I finished and restart the same message appeared.
I started to investigate and it seems that the OEM blockade is responsible for not being able to install any Stock Rom, or anything, and now I have a nice brick with Moto mods and I can't use it.
I wanted to unlock OEM in fastboot but nothing. sends message from "ALLOW OEM UNLOCK IN SETTINGS"
There is way to unlock the OEM from pc or fastboot without needing to be unlocked from the android settings, as in my case it is impossible for me,
I'd be very grateful for your help friends, I know it's a bit tedious to read but it's the only phone I have and I feel weird without it on the street.:bueno::bueno::llorando:
I'm with same problem here!
Suckmymfdick17 said:
Hello friends of XDA, I have a big problem between hands, I have a MOTO Z and I had it in android 7.0 since last year the update to andorid 7.1.1 did not arrive and I felt that with android 7 the battery was consumed very quickly, so I tried to find the update to flash it and just about 3 days ago I found it, I proceeded to download it and flash it in fastboot and adb.
The thing is that a few months ago, browsing through my phone (I had already rotated it, and unlocked the bottloader, I decided to re-block the bootloader, and remove the root, which never worked at 100) I got into the developer options, and I saw an option that until then I didn't know about its "OEM Unlock"function, as it was turned on and deactivated because I thought it didn't work.
Returning to the update flashing I proceeded as usual, with the commands, I proceed to restart the device and show the image of the boot of motrola but then it shows me a message in red letters.
"Startup Failed"
"failed to pass validation, backup to fastboot.
I thought it was a compatibility problem with the downloaded version of 7.1.1 so again I decided to flash the stock rom 7.0 but when I finished and restart the same message appeared.
I started to investigate and it seems that the OEM blockade is responsible for not being able to install any Stock Rom, or anything, and now I have a nice brick with Moto mods and I can't use it.
I wanted to unlock OEM in fastboot but nothing. sends message from "ALLOW OEM UNLOCK IN SETTINGS"
There is way to unlock the OEM from pc or fastboot without needing to be unlocked from the android settings, as in my case it is impossible for me,
I'd be very grateful for your help friends, I know it's a bit tedious to read but it's the only phone I have and I feel weird without it on the street.:bueno::bueno::llorando:
Click to expand...
Click to collapse
Try to boot in Fastboot flash twrp and flash ressurection remix rom. It's great rom. Forget about locking. I had the same problem like you as I was trying to flash stock ROM and lock bootloader.
I gave up on this.
knjigo said:
Try to boot in Fastboot flash twrp and flash ressurection remix rom. It's great rom. Forget about locking. I had the same problem like you as I was trying to flash stock ROM and lock bootloader.
I gave up on this.
Click to expand...
Click to collapse
Well, when the root didn't work properly, I flashed the phone again and blocked the bootloader. Will I still be able to install TWPR or should I lose my phone?
Suckmymfdick17 said:
Well, when the root didn't work properly, I flashed the phone again and blocked the bootloader. Will I still be able to install TWPR or should I lose my phone?
Click to expand...
Click to collapse
What do you mean with "I blocked my bootloader"?
Twrp is easy to flash. Root is integrated in ressurection remix rom. And this rom is great. Just try to flash twrp in Fastboot and than ressurection remix with twrp.
Can you boot in Fastboot?
Do you remember what build of 7.1.1 you had on your device before downgrading to 7.0?
If so, I would suggest finding that firmware (the full stock firmware, not OTA updates) or newer if you can, and try to flash that. Since your bootloader is still likely from the 7.1.1 build, a locked bootloader will only permit files matching the same patch level (i.e. from the exact same stock ROM as that bootloader patch) to boot.
If not, then unfortunately there's not a lot we can do. You could wait for a newer firmware to get leaked, but as your device is unable to boot (due to failing the bootloader checks) and you cannot toggle OEM unlocking because you cannot boot, it's a nasty vicious circle that is difficult to get out of. You may have to consider sending your device for service and pay for an expensive motherboard replacement otherwise, since Motorola have a record of your device being unlocked. Your service centre experience may vary.
Only lock a bootloader after ensuring you've flashed all the stock firmware and it is all the same patch level as your bootloader. Hopefully you'll find newer firmware that you can repair with.
tjgibri said:
I'm with same problem here!
Click to expand...
Click to collapse
I solved it, I finally flashed the stock rom to my phone and it works.
Apparently my pc was not flashing the stock rom in adb, and the phone turned off when loading the software. I did it 3 times until I load correctly and start well.
if you have the same problem apparently then OEM Blocking is not responsible. You have to flash the most current rom or the one that you had by default when the brick happened to you, you flash it in a normal way with commands of adb and ready, I would have to come back to life.
download from firmware center MotoZ Griffin the most current rom stock at 7.1.1
echo92 said:
Do you remember what build of 7.1.1 you had on your device before downgrading to 7.0?
If so, I would suggest finding that firmware (the full stock firmware, not OTA updates) or newer if you can, and try to flash that. Since your bootloader is still likely from the 7.1.1 build, a locked bootloader will only permit files matching the same patch level (i.e. from the exact same stock ROM as that bootloader patch) to boot.
If not, then unfortunately there's not a lot we can do. You could wait for a newer firmware to get leaked, but as your device is unable to boot (due to failing the bootloader checks) and you cannot toggle OEM unlocking because you cannot boot, it's a nasty vicious circle that is difficult to get out of. You may have to consider sending your device for service and pay for an expensive motherboard replacement otherwise, since Motorola have a record of your device being unlocked. Your service centre experience may vary.
Only lock a bootloader after ensuring you've flashed all the stock firmware and it is all the same patch level as your bootloader. Hopefully you'll find newer firmware that you can repair with.
Click to expand...
Click to collapse
Thanks for your help friend, I finally flashed it with a recent android 7.1.1 update. Apparently the OEM lockout was not the culprit, but it was an interrupted flash of android 7.1.1 at some point when loading the software to the phone, it would shut down on its own and not complete the installation, which showed me the mentioned message. I didn't realize that and thought it was the OEM blockade.
I finally did it on another pc and it worked. the phone came back to life.
I have one Moto Z2 Force (XT1789-05), bought from coolicool.com, I didn't know device came Unlocked Bootloader, Device rom had problem with many apps, I googled and found one topic in XDA developer to Install Stock Rom, I downloaded and Installed India Rom, it's worked somehow fine, but still had problem, I downloaded Verizon Rom, Android 8, after Installed Android 8 Verizon Rom, Locked device bootloader immediately, now device stuck at Welcome Wizard in Android 8, after select language I got this message: (Please wait, this may take a few minutes) this is proof video (http://ahmn.co/Upload/IMG_0161.MOV), after this issue, device already locked, I can't unlock, because need to go to the Developer Option in Setting, I stucked in Welcome Wizard, there isn't any bypass, So, I start to search in Google, XDA-Forum, Android Central and more, I created many threads, many requests, no one can't help me, I tried to reach google developer support to the tell to me how can I bypass Android 8 Welcome Wizard, there is must be a way, but I can't find it, now I can access to Android Recovery and Bootloader
1. if you help me to FORCE UNLOCK device without need Developer Option in setting my problem will solve
2. If you help me to Bypass Android Welcome Wizard, access setting and enable OEM Unlock
3. If you help me to update the device from Android 8 to Android 9 Verizon ROM via ADB Sideload or Update from SD card in Recovery mode
4. If you have any idea to how can I fix it
Extra Information: I bought Belkin and Uni USB-C to Ethernet Adaptor to help me bypass Android 8 Welcome Wizard, I bought WSKY WIFI Adaptor because device Wifi can't find any network (I found QR setup by tap several times in Language Selection), after this section need to download google device policy apk, my device can't find any Wifi Network and my Ethernet Adaptor can't help me either, So, I just remained with my phone, and I can't do anything,
Please, someone, help me
My Device SKU: XT1789-05
Hi.
I have a Doogee X6 S.
It is currently flashed with stock ROM¹, which runs Android 6.0 with a 3.4.5 kernel and contains OEM adware, and maybe worse.
I'd like to be able to flash a more trustworthy rom of android.
I was unable to root the device with kingoroot app. The bootloader is locked, I can't flash TWRP.
I tried to unlock the bootloader:
- I unlocked and enabled developer options,
- I checked the "oem unlocking" option ("allow the bootloader to be unlocked"),
- "adb reboot bootloader" rebooted the phone in fastboot mode
- "fastboot oem unlock" asked me confirmation for unlock, VOL_UP for "Yes", VOL_DWN for "No", but none of the keys have any effect when pressed.
I tried flashing older versions of the stock ROM with SP Flash Tool, but this resulted in a softbick (solved by flashing back last stock ROM).
I tried contacting Doogee support, to no avail.
I don't know what to try next, so here I am!
While I'm not an Android hacker, I know my Linux, and I'm not affraid of complex solutions.
¹ available from official support page: community.doogee.cc/forum.php?mod=viewthread&tid=4872
Since I didn't get any answer here in one week, I opened a thread on the official support forum :
community.doogee.cc/forum.php?mod=viewthread&tid=7544&page=1&extra=#pid50966
If I get a solution there, I'll relay it here.
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.