Related
My question is regarding flash stock + unroot using the Nexus Root Toolkit v 1.6.3
I have already unlocked and rooted my phone using the tool.
I am now trying to flash stock + unroot using the Nexus Root Toolkit.
I downloaded the build from Google's Factory Image Download page.
I get passed Which Factory Image? by clicking Other/Browse
Choice: I downloaded a factory image myself that I would like to use instead.
Choose a google facotry image: mysidspr-ga02-factory.tar
Analyzing factory image; please be patient
Hascheck Verification
Enter the md5 has given for: mysidspr-ga02-factory.tar
I enter: c93156606b39a6b61d371ef935a6a6ba from googles website.
Message pops up: Your file is good to extract and flash! Press OK to continue.
Please be patient...Checking ADB Status
Device Connected Rebooting your device into bootloader mode
Chekcing Fastboot Status
Device Connected
Checking Fastboot Status
Device Connected
CMD window opens
Booting up your freshly flashed stock device
Wait for your device to finish booting up...
- It will appear to be boot looping; just wait...
-It could take 5-10 minutes; please be patient...
When its finally booted back up, please remember to re-enable USB debugging if you plan on using the toolkit to perform other operations
Press any key to exit...
My phone remains on the Bootloader screen with the robot laying down with its hatch open.
Bootloader is on Start
below robot:
FASTBOOT MODE
PRODUCT NAME - tuna
VARIANT - toro 32GB
HW VERSION - 14
BOOTLOADER VERSION - PRIMELC03
BASEBAND VERSION - L700, FC12 COMA - L700, FC12
CARRIER INFOR - NONE
SERIAL NUMBER - 0A3C2C620401C009
SIGNING - production
LOCK STATE - UNLOCKED.
I have gone through this over and over and have waited anywhere from 15 minutes to 3 hours. Nothing else occurs.
So I click Press any key to exit from the command window and restart my phone and it is still on Android 4.1.1
Any suggestions/help would be greatly appreciated.
Hi, I noticed that if you choose the option where you have already downloaded the image (from google) it wont work. You have to select the option where the program downloads the image from that site goo.xxx.
Google's stock image is .tar and the image downloaded from the other site is .tgz ( supposedly the same thing, but the toolkit would only extract the second) To be honest, I would have rather use the image downloaded from google's...
Doesn't work for me too..
tessorodesoto said:
Hi, I noticed that if you choose the option where you have already downloaded the image (from google) it wont work. You have to select the option where the program downloads the image from that site goo.xxx.
Google's stock image is .tar and the image downloaded from the other site is .tgz ( supposedly the same thing, but the toolkit would only extract the second) To be honest, I would have rather use the image downloaded from google's...
Click to expand...
Click to collapse
I tried to do both ways but it doesn't work for me either..
I have Galaxy Nexus with Android 4.2.1. I have managed to unlock and root my phone easily using Nexus Root Toolkit 1.7.1. However when it comes to flash rom+unroot process, it is not working.. I tried to flash Android 4.2.2 and Android 4.3 by choosing both options but the process always stopped in the beginnig of CMD prompt window..
same problem
I rooted my newly aquaried nex which was a fully stock 4.1 in anticipation of flashing to boost and custom roms and all that fun stuff. NOW I cant flash I CANT change os. I CANT FACTORY RESTORE I CANT DO CRAP I HAVE A FREAKING PAPER WEIGHTT because I don't want sprint and there is no way ill put this back on ebay and give the head ache to someone else. HAS ANYONE FIGURED ANYTHING OUT YET? I can really use a hand. Ive spent over 15 hours researching downloading flashing fast booting etc. and I've gotten nowhere ANY HELP would be GREATLY APPRECIATED.
Link provided is the firmware and unlocking script for the Warp 7. N9519
You can use QPST to flash the files, no cracked software is necessary for that (nor is it included).
I use NCK or UAT to go from ADB/FTM > EDL mode, but you should be able to do it with a modified ADB.
Getting to EDL mode (qualcomm 9008) is the only part of the process I cannot provide a surefire method to. I use paid programs that can do this.
Youll have to figure that part out.
This didnt work for me on any other firmware. B10, nor B07. I tried. It gives the 3g error.
1) Flash the B09 firmware if you arent already on that firmware. (provided in link)
2) Flash the unlock boot.img. (provided in link)
3) Enable USB debugging.
4)Make sure there are no pattern locks or passwords on the phone.
5) Run the 0b09.bat script. (provided in link)
The script will root the phone, unlock it, then apparently unroot it.
Phone will reboot several times. You will see some weird popups and autoclicks. Dont worry about it, its normal.
The script will also seem to reset itself/hang a few times. Be patient. It is just proceeding to the next steps.
Dont unplug the phone or touch it during the process except to swipe the screen lock off when it reboots (probably not necessary, but I did it anyway).
If you do the process with an invalid sim in the phone itll be obvious when the process is done. Itll have signal =P
Link:
https://mega.nz/#F!V1ZUQIxQ!6y3PxXDthqozVfG4UGKyRg
What are you talking about? There's nothing except a text file provided via the link?
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!
Anyone have this problem and solved it? I have an ASUS Zenfone Max Plus M1 (ZB570TL ) - (X018D) and i have tried every Rom you can think of from WW to CTC to CN, also tried dump firmware but nothing will stick and let this device actually fully boot up after flashing it, it just goes to the POWERED BY ANDROID screen and after 30 secs it will reboot itself back to the POWERED BY ANDROID screen and then reboot again and so on..
HOLDING VOL+ and POWER buttons in gets me to the:
- RECOVERY MODE - Just reboots back to Powered by Android screen and back to bootloop, no android guy recovery...
- FASTBOOT - Lets me have Fastboot but i cant flash anything or unlock bootloader as it errors and shows its Locked...
- NORMAL BOOT - Just reboots back to the Powered by Android and then reboots after 30 secs right back there....
There is no RECOVERY MODE that i can Factory Reset, Update.zip, clear cache...
I Flashed with SP Flashtool over 20 Firmwares and all finish with the popup Finished and green checkmark and i watch the flash process all the way without error, unplug the device and turn it on and back to Powered by Android screen and reboots itself after 30 secs... THIS IS CRAZY its like its a GAG Phone or something just messing with me like ( Jokes on you big guy ) ive never seen anything like it, its like the locked bootloader is telling the device not to allow any Firmware to install by tricking the SP Flashtool that yes it did install but didnt allow it to write to the actual system or let you get into recovery mode to factory reset the device or update from sdcard... im just wondering if its a waste of time to bother finding a UFI Box flasher that doesnt need the dongle so i could try flashing the EMMC files if that would help or not... its not a hardware problem or it wouldnt accept flashing or let it power on and enter fastboot mode....
Is this a GAG Device or has anyone actually had this exact problem and has solved it? If i could just get it to boot up into the system i could use Magisk and make a patched-boot.img thats unlocked bootloader and root but theres no ZenUI or anything but the Powered by Android screen....
Any Help would be awesome as i just put new screen, battery, back cover and buttons on this device thinking it would be a good little phone for my daughter... i cant even get any info on the device as theres no box or sticker with IMEI or Serial Number or info on the last working Firmware its all a shot in the dark... Anyways if anyone has the way to get this device working or has backup rom or links to an actual way thats not ASUS as they are just waste of time for 30 mins then you need to take it in to our service center and pay more money and im done putting money in this and could have bought her a new phone for what ive got into this Gag Phone....
Thankz...... Kixx
Judging from the whole situation, you screwed up several things honestly.
The fact it goes stuck on the splash screen and refuses to neither boot on recovery nor the system itself seems to tell 2 things:
the boot.img and recovery.img got screwed up way too much- or literally got flashed for the wrong device, hence the whole rejection to boot;
i assume SP Flashtool, even if got tricked, got a bit of a mess on the internal partitions to be flashed thru. Sounds like a big red flag because ADB can be highly of help (i don't own an X01BD but an X00HD- still an asus device- but i used simple ADB instead of things like QFIL or SP Flashtool to get things going);
On second point, if you wanna try to unlock the bootloader (since fastboot is the only one to be alive and usable- this means your device will be salvageable...atleast by a significant chunk):
you can give it an attempt by checking over my own collection post.
There you will find at the bottom some tiny guide on how to unlock the bootloader-
if you don't have a secondary rooted device, you can always rely using a laptop or pc.
What really matters is that you'll have ADB downloaded on your machine, because it could be of help to progress thru with the stuff.
After unlocked the bootloader, you can slowly approach to flash TWRP for your own device- even tho, it seems nobody so far has done anything for this specific model...
Atleast, on the bright side, unlocking the bootloader will give you the chance to flash manually the partitions via ADB, and maybe the official zendesk site for it can help if unpacking one of the update zips and see the contents inside- or generally pushing the following .zip update file via ADB and wait for the magic to happen.
I'm not sure on how to help with the region tho.
I guess, if you have the box of the device, it could give you a clue if it is a WW (WorldWide), CN (China), JP (Japan), etc. model- afterall, these letters do not lay around without a reason.
Of course, if you flash the wrong region to the wrong regional model:
then the recovery and system partitions get to screw up big time, just like the scenario you're having right now.
As a last thing, the patched boot.img file only gets to work after you got android to work-
otherwise, patching the pre-rooted boot.img file will be of no use since a functioning ROM isn't there at all.
Sadly, i don't own the device nor never had such screw-ups of this kind, but i hope it will help you up.
Ya i can flash the firmware correctly in SP Flashtool it comes back with green checkmark, all the firmware is for the correct device, its just when i had it given to me it had broken screen and bad battery, so i buy new screen, battery, backcover for it and when i booted it up it just sticks on the first screen shown ( Powered by Android ) then after like 30 secs it reboots back to that screen.. I can hold the vol + and power and get the menu to pick RECOVERY or FASTBOOT or REBOOT, recovery just reboots to powered by android screen then reboots after 30 secs, fastboot lets me use adb and fastboot but cant flash it says failed locked, and fastboot oen unlock or any of the commands to do with unlocking or flashing just gets me failed locked, but fastboot does work. Only way to root or unlock bootloader the device needs full boot into system so i can enable adb debugging or usb debug in developer settings so the computer will let the device get past the failed error locked part....
Do you know how to get the usb debugging turned on so the computer can grant full access to the device then il be able to actually crack into it and flash through fastboot..
Or where the usb debugging file is in the system.img if i extract it, use text editor and give the bool a yes that its been accepted then repack the system,img and flash it usinh sp flashtools, then i might ge able yo get it up and running....
After flashing all kinds of firmware for this device they all pass the flashing except for a few of them, ones that dont work wont even let the device boot to show system thing, then flashing correct firmware it allows the first screen again and the menu to pick fastboot but wont fully boot up..
Im thinking there must be somekind of lock the device put on from letting you oem unlock bootloader or booting into recovery mode because the firmware is working or it wouldnt take it using SP Flash Tools or even let it boot up as it would either reboot instantly or not even turn on, if the boot partition or recovery partition was courupt or broken or damaged it wouldnt take it during the flashing process it would fail....
If you know how i can activate the usb in developer settings from a file in system.img file after ectracting it then thats prob my BEST OPTION OR BUY A USED MOTHERBOATD OFF EBAY...
Lol
KixxTheManz said:
Ya i can flash the firmware correctly in SP Flashtool it comes back with green checkmark, all the firmware is for the correct device, its just when i had it given to me it had broken screen and bad battery, so i buy new screen, battery, backcover for it and when i booted it up it just sticks on the first screen shown ( Powered by Android ) then after like 30 secs it reboots back to that screen.. I can hold the vol + and power and get the menu to pick RECOVERY or FASTBOOT or REBOOT, recovery just reboots to powered by android screen then reboots after 30 secs, fastboot lets me use adb and fastboot but cant flash it says failed locked, and fastboot oen unlock or any of the commands to do with unlocking or flashing just gets me failed locked, but fastboot does work. Only way to root or unlock bootloader the device needs full boot into system so i can enable adb debugging or usb debug in developer settings so the computer will let the device get past the failed error locked part....
Do you know how to get the usb debugging turned on so the computer can grant full access to the device then il be able to actually crack into it and flash through fastboot..
Or where the usb debugging file is in the system.img if i extract it, use text editor and give the bool a yes that its been accepted then repack the system,img and flash it usinh sp flashtools, then i might ge able yo get it up and running....
After flashing all kinds of firmware for this device they all pass the flashing except for a few of them, ones that dont work wont even let the device boot to show system thing, then flashing correct firmware it allows the first screen again and the menu to pick fastboot but wont fully boot up..
Im thinking there must be somekind of lock the device put on from letting you oem unlock bootloader or booting into recovery mode because the firmware is working or it wouldnt take it using SP Flash Tools or even let it boot up as it would either reboot instantly or not even turn on, if the boot partition or recovery partition was courupt or broken or damaged it wouldnt take it during the flashing process it would fail....
If you know how i can activate the usb in developer settings from a file in system.img file after ectracting it then thats prob my BEST OPTION OR BUY A USED MOTHERBOATD OFF EBAY...
Lol
Click to expand...
Click to collapse
Well, as far as i can tell and did unlock 2 asus devices of the same model (still, X00HD):
i didn't needed to go thru android, since Asus never had an "OEM Unlock" thing to enable once unlocked dev settings-
yet, i'm speaking about the X00HD since, again, i never owned an X01BD, but i am trying to apply the same reasoning even if it is an entire different model but still same brand.
Dunno, in my case i was able to get the bootloader unlocked by going getvar all and got the secret key to unlock it just as easily by experimenting and finding cmds to use over this device's forum in here while being in Fastboot mode.
Before stepping my feet to Fastboot, tho, i even tried to get my hands at an OEM Unlocker apk made by Asus:
but to no avail it only worked on devices with really old firmware and since my device was updated to the latest Oreo FW, it was impossible to perform since things got patched overtime.
Sadly, i really don't know how to modify values over system.img files myself and tick up variables by inspecting over hex editors and such.
Least i know is getting the Brotli binaries and some other specific tool on GitHub to extract stuff from Android .img files, but that's all my skills really get limited to since i'm no dev myself nor either someone who can reverse engineer things just as well.
I think you could be out of luck on that regard.
Only thing that remains is going to a particular mode where it is required putting the phone apart and touch 2 specific pins on the board to enter it.
I currently forgot the name of this mode, but i do know by fact it's a common thing between Huawei devices.
If even this thingie won't help, then i really dunno myself.
Maybe someone else could be of help instead of me lol.
Ya ill try touching the two pins but what two oins and touch them with whst? Give me a roll out on what to do, i just dont understand why it accepts firmware but wont let me boot up into it or recovery mode or flash anything because at first it flashes then when it completes it fails and says remote unknown locked
Also im going to try find a way to format or partition the main system partitions maybe the system.img is landing on a different section of the harddrive... just need tge partitions for thus device
KixxTheManz said:
Ya ill try touching the two pins but what two oins and touch them with whst? Give me a roll out on what to do, i just dont understand why it accepts firmware but wont let me boot up into it or recovery mode or flash anything because at first it flashes then when it completes it fails and says remote unknown locked
Click to expand...
Click to collapse
Aight, to start with: i'll share out a couple of links.
First, here's a picture on where the testpoints of the device are.
As of second, you need some tweezers or something that is able to touch such testpoints inside the board (unrelated, but the GH page to PotatoNV has a guide what to do with the testpoints- even tho, the page redirects you to a tool that only works with Huawei devices. Don't test it on that asus device.).
Not sure about the flashing tool, honestly, but i do know for a fact i couldn't share software in here due to rules of this forum.
Since this is, i suppose, a device with a Qualcomm SoC:
maybe you could use stuff like QFIL Flash Tool for the job (dunno about partitions, for that you should get some linux knowledge- since android uses the linux kernel to communicate with everything inside the device).
Also, i've got something intriguing right now:
apparently the forum for the X01BD effectively exists over XDA lol (turns out the X01BD is a Zenfone Max Plus M2 and not an M1).
Maybe you can check out here for further custom ROMs and recoveries, plus more proper help on the matter- as of firmware dumps, you could try hopping over Android FileHost, firmware.mobi, or steep your feet into some unknown forum that has the firmware dumps of this specific device and restore it logically (or simply doing a google search by doing [insert model number here] firmware dump - if google only gets you to shady sites, stick to the XDA forum on the device).
Goodnight all,
I unlocked the OEM bootloader and Rooted my Samsung Galaxy Z Flip 4 using Magisk. It is a European model.
Now each time I start it I get warning messages that the security has changed as a result.
I reset my phone completely and I still have these warning messages on startup.
Is it possible to remove these warning messages because I will most certainly resell the phone???Is there a solution to lock the OEM bootloader again or is it irreversible???
Thank you in advance for your help and good evening to all.
This is by design. An unlocked bootloader should display the ORANGE state on boot to notify the user. This is normal, and no action is needed.
It is not possible to remove these warning messages as this is a result of the bootloader functioning as intended.
You can re-lock your bootloader if you want but make sure you have performed a clean flash with the factory firmware first. You would then follow the same process you used to unlock the bootloader (device off, hold both Volume buttons, plug in USB cable).
It's just a minor inconvenience though and does not affect device operation.
Good evening,
@V0latyle
if I understood your explanation , I download the latest firmware which is installed on my phone with the help of SamFirm or other software.
Then I use Odin in administrator mode and I select the file in the BL box, the file in the AP box, the file in the CP box and especially in the CSC box I put the CSC file (and not Home_CSC) in order to a hard reset of my Samsung Galaxy Z Flip 4 phone. Once the flash is done, the phone reboots to factory state, I click the build number 7 times then I go to developer options and there I could finally lock my OEM development loader again??? Once I've done all of this
,will the bootloader security warning message go away???
Please tell me if I understood correctly please and above all thank you again for your help.
nicoco19 said:
Good evening,
@V0latyle
if I understood your explanation , I download the latest firmware which is installed on my phone with the help of SamFirm or other software.
Then I use Odin in administrator mode and I select the file in the BL box, the file in the AP box, the file in the CP box and especially in the CSC box I put the CSC file (and not Home_CSC) in order to a hard reset of my Samsung Galaxy Z Flip 4 phone. Once the flash is done, the phone reboots to factory state, I click the build number 7 times then I go to developer options and there I could finally lock my OEM development loader again??? Once I've done all of this
,will the bootloader security warning message go away???
Please tell me if I understood correctly please and above all thank you again for your help.
Click to expand...
Click to collapse
You don't have to do anything with Developer Options or the OEM Unlock toggle. OEM Unlocking only functions as a "safety" to permit you to unlock your bootloader.
If it is already unlocked, simply follow the instructions you used to unlock it after you enabled OEM Unlocking the first time - with the device powered off, use the key combo to boot into Download Mode, then hold Volume Up until you see the device lock warning. When you relock the bootloader, it will wipe data. Once done, no further steps are needed.
If you want to tinker with your device and enjoy the benefits of root, why not leave it unlocked? Sure the bootloader warnning is slightly annoying but again that's by design.
@V0latyle
ah ok, I understand better, I'm doing the reverse step of what I did the very first time I unlocked the OEM bootloader.
I put my phone in download mode by connecting it to my computer and then I hold the volume up key for a long time to lock the OEM bootloader. And if I understood correctly, once this is done, my phone will be factory reset and no more warning message on startup. That's right ???
In fact, I'm asking you all this because I want to sell my phone to switch to the S23 Ultra.
thank you for your help and your feedback
nicoco19 said:
@V0latyle
ah ok, I understand better, I'm doing the reverse step of what I did the very first time I unlocked the OEM bootloader.
I put my phone in download mode by connecting it to my computer and then I hold the volume up key for a long time to lock the OEM bootloader. And if I understood correctly, once this is done, my phone will be factory reset and no more warning message on startup. That's right ???
Click to expand...
Click to collapse
Yes, if the bootloader is locked and the firmware is original OEM, there should be no warning.
@V0latyle I'm testing all this to the letter tomorrow evening and in the process I'll come back for other people that it could help.
thank you for your help and keep you posted
Hello,
I did what you said and problem solved, the warning messages at startup disappeared.
Thank you again for your help @V0latyle
But u know that KNOX is triggered and u loose some of functions anyway even if you relock bootloader ?