I'm on the latest version of android.
A little birdie gave me a neat set of files and I was able to successfully flash them, RES OK!
................But..............
When booting, android complains about the vbmeta file and says, "you have flashed custom firmware, the device is now locked. Please contact your service provider"
I was a bit worried at first but just flashed the stock image and I was up and running again.
The flash was supposed to enable the OEM Unlock option but the security put in place on the device prevents the system from even booting.
Can anyone shed light if I am close or if this is futile?
Thanks
**EDIT** - Without unlocked bootloader, flashing anything is useless, successfully or not.
Related
Hello,
received the Phone with the t-mobile branding (german version).
What i did is to use the official device unlock from Sony so be able to flash another Firmware.
Then i downloaded the generic DE from the FlashTool, and flashed it.
This failed because the rom was already on Android 7.
I did not manage to aquire the -9090 Rom in Android 6.0.1
So i flashed the central europe version.
First problem: this version does not (yet?) update to Android 7 - and actualy is NOT the version i wanted to have in the end.
Second problem: The camera app did not work anymore (already in use)
So i've read through this forum, and got the information, i need to re-unlock the device.
Did that, camera works.
However now i always get "this device is not trusted"
What i actualy want to have:
- A stock ROM in german, whcih gets OTA updates.
- Working Stock-Apps
- No warning when starting the Phone.
I do not care wether the warning is disabled, or simply not shown because of another bootloader. There should simply be no annoying warning.
I also have the exact same phone twice (mine, and the one for my girlfriend) in case this help somehow. In theory the best situation would be to hard-sync every single byte on the disk (i assume?)
I did not read anything about "do not flash currently, as this will make you loose your drm keys forever and the stock camera will no more work at all". But after watching this forum for some days now, it seems that exactly that has happened? So using a locked bootloader will not work anymore due to lost and unrecoverable drm keys? I cannot copy them from the other phone? So i need to replace the bootloader with another one to get rid of the message? And i also need to reflash the firmware as soon as FlashTool supports Android 7?
In the end a total piece of crap, because of a goddamn branding -.-
What would you guys recommend to do now? Just want to make it work without an error or unsecure warning displayed at every boot.
You did not need to unlock to flash another firmware.
Now you have unlocked you can't use the camera without keeping it unlocked and if it is unlocked you will get the warning message.
Just flash a 6.0 ftf from a region with the update then you will get the ota update
Ps, there are plenty of warnings on the Sony site about drm keys that you must have visited to get your unlock code...
And you cannot copy drm keys from another device
Had no idea the dev options needed to be left ON regardless after rooting, or it rejects the custom binary? Would have thought the FRP lock would have been bypassed with the rooting. Can't enter twrp recovery neither.
And to be 100% clear, phone is rooted. Dev option was unticked w/o realizing it'd retroactively lock the phone as it detects the non-oem firmware and refuses to boot, refuses recovery, refuses flashing.
Can I somehow flash a stock firmare via Odin and NOT get the wrath of FRP? I found the stock firmware for the phone from Samsung's site. For some reason, the firmware.zip is like 1.4gb? Do I need to strip out a file for the recovery image assuming it'll accept it? Or just select the entire thing in Odin?
OK, flashed the 2.5gb (unzipped it had THAT much bloat) factory Samsung firmware, which took about 2.5 minutes vs. like 4 sec for the root .img :silly: and phone boots back up w/o issue, all personal stuff is intact, and unsurprisingly it adds all the bloatware back that I just deleted earlier.
So, if you accidentally turn off the dev options or I'm assuming the OEM unlocker specifically on your J7, and the phone refuses to boot as it's retroactively detecting "custom binary", OR if you happen to accidentally truly delete an important app and/or it can't be brought back with 3rd party apps, going to Samsung's firmware section, finding your EXACT phone/model/software numbers including the most recent OS and security upgrade to it i.e. 7.1.1 in my case, flashing it with Odin (site said to use most recent, so used v3.13.1) will restore the phone, unrooted of course. But it's better than a paperweight.
Hi everybody,
I was recently trying to update my phone so I did this by wiping the partitions and flashing the latest OS using HWOTA. I kinda messed this up and tried to fix it and basically dug myself a massive hole trying to fix a minor mistake.
Eventually I made the mistake of factory resetting it. Now I am at a stage where I have no TWRP and my bootloader shows its unlocked (shows Phone unlocked and "oem get-bootinfo" shows unlocked) but does not allow me to run commands that I should. FRP shows as unlocked on fastboot and in developer settings.
I would simply try to unlock my bootloader again using oem unlock with my unlock code however I was silly enough to not save my code from DC Unlocker. I would get my code by setting my phone to manufactor mode etc, however its messed up so that most the default software is not included, including the ProjectMenu, and even a default keyboard (only includes Googles Voice keyboard).
Is it possible to get this menu back or is there anything I can do to restore my phone to have TWRP on it?
I tried installing the ProjectMenu APK but that fails and I don't know how to install the files in "update_data_full_public". I have messed with my phone a lot to try and fix it, including using the erecovery to try and flash many various updates, rolled it back, and flashing it after that to no avail.
There's a lot that I have done that is not included so if theres any questions, please ask.
Thanks
Phone is FRD-L09 C432
zacy5000 said:
Hi everybody,
I was recently trying to update my phone so I did this by wiping the partitions and flashing the latest OS using HWOTA. I kinda messed this up and tried to fix it and basically dug myself a massive hole trying to fix a minor mistake.
Eventually I made the mistake of factory resetting it. Now I am at a stage where I have no TWRP and my bootloader shows its unlocked (shows Phone unlocked and "oem get-bootinfo" shows unlocked) but does not allow me to run commands that I should. FRP shows as unlocked on fastboot and in developer settings.
I would simply try to unlock my bootloader again using oem unlock with my unlock code however I was silly enough to not save my code from DC Unlocker. I would get my code by setting my phone to manufactor mode etc, however its messed up so that most the default software is not included, including the ProjectMenu, and even a default keyboard (only includes Googles Voice keyboard).
Is it possible to get this menu back or is there anything I can do to restore my phone to have TWRP on it?
I tried installing the ProjectMenu APK but that fails and I don't know how to install the files in "update_data_full_public". I have messed with my phone a lot to try and fix it, including using the erecovery to try and flash many various updates, rolled it back, and flashing it after that to no avail.
There's a lot that I have done that is not included so if theres any questions, please ask.
Thanks
Phone is FRD-L09 C432
Click to expand...
Click to collapse
Have you simply tried to use eRecovery? Did you still have it?
ScardracS said:
Have you simply tried to use eRecovery? Did you still have it?
Click to expand...
Click to collapse
Yes, I have tried using the dload method multiple times with different firmwares, the "Download and install via wifi" method which fails as it says it cannot find anything for my phone, as well as trying through HiSuite when in fastboot. This also says it can't find any package for my phone. Very weird to be honest.
Also tried factory reset, settings reset (from advanced menu in settings), and wiping cache.
Also tried to go back to Android 6 using this method: https://www.stechguide.com/downgrade-honor-8-from-nougat-to-marshmallow/ and that failed ):
Ok, so I used this tutorial ( https://forum.xda-developers.com/honor-8/how-to/b399-flash-via-dload-mode-t3716885 which is yours) and it actually flashed and upgraded the phone. ProjectMenu still wasn't working so updated from the settings as one appeared. Phone is now on C432 B404.
Project menu still doesn't work along with some default apps not being installed such as Clock.
It seems like all the files I need is in the "update_data_full_public" update zip including the project menu apk. Does anyone know how to flash everything in this file as just installing the apk fails?
I tried putting it in to dload file but that just files as there is no update.app.
Any way to downgrade from Nougat to MM without losing FP Sensor,Haptic Feedack&Camera
I recently purchased a new S7 not realizing that it was equipped with a Nougat OS. I would like to restore my current phone to the new one, but my current phone runs on MarshMallow. After restoring the backup, my new phone has no haptic feedback, no fingerprint sensor with "an error has occurred with the fingerprint sensor. if this message appears repeatedly, restart your phone" message and the Camera doesn't work.
I'm sure it has something to do with bootloader N using MM. Even restoring Stock Marshmallow firmware (Including BL) on the new phone removes these functions. Does anyone have any ideas on how I can get these to operate?
My current phone has
Bootloader Version: G930W8OYA2APK3 (MM)
Baseband and PDA Version: G930W8OYA2API1 (MM)
When I restore my old phone to the new one, it ends up with
Bootloader Version: G930W8OYA2BQK4 (N)
Baseband and PDA Version: G930W8OYA2API1 (MM)
EDIT: Just tried the Nougat firmware with MM Bootloader. All of the functionality is present.
Bootloader Version: G930W8OYA2API1 (MM)
PDA Version: G930W8OYA2BQK4 (N)
Just restored old backup with MM bootloader (Boot, Data, System only).
No Fingerprint Sensor or Camera.
BTW, ignore the HAPTIC FEEDBACK portion of this post. I believe it is working.
Any help with this matter would be greatly appreciated.
Not possible to downgrade since the bootloader block you from flashing lower version of that. You may try to flash without BL, but your phone will be malfunction
Thank you for your reply. I don't think I'll be able to get the fingerprint wizard to work but having a functional camera would be a necessity. From the System/Priv-App folder I copied the SamsungCamera5 (from MM) and the SamsungCamera6 (from N) onto an SD Card. I guess I can try to play around with them to see if either will work, but I don't think they will since my restored backup should already have SamsungCamera5 and the SamsungCamera6 apk probably isn't compatible with MM. Kinda disappointing that I'll have to continue to use my old phone with a broken screen instead of the brand new one I purchased.
Sleaze0 said:
Thank you for your reply. I don't think I'll be able to get the fingerprint wizard to work but having a functional camera would be a necessity. From the System/Priv-App folder I copied the SamsungCamera5 (from MM) and the SamsungCamera6 (from N) onto an SD Card. I guess I can try to play around with them to see if either will work, but I don't think they will since my restored backup should already have SamsungCamera5 and the SamsungCamera6 apk probably isn't compatible with MM. Kinda disappointing that I'll have to continue to use my old phone with a broken screen instead of the brand new one I purchased.
Click to expand...
Click to collapse
do not flash AP from a firmware set made prior to the bootloader youre on, it will more than malfunction, itll probably brick
i went back and read all the tl : dr stuff and saw that you seem to have got it working, oddly enough. The camera issue is likely the kernel
Thanks for the info on the thanks button. I've just about given up trying to get Marshmallow to work properly on this phone. Looks like it'll take weeks to configure my new Nougat phone to be similar to the three years of tweaks I've made to my old MM one. Oh well, first world problems I guess.
As others have pointed out, you can't use Odin to successfully flash a ROM with a bootloader that is earlier (in version) than the bootloader you have installed. The "gatekeeper" is Odin, however, not the bootloader.
Though I haven't tried it, it is my understanding that there is a way around this. Install TWRP, and use it to install a custom ROM which uses the version of bootloader that you want/need. Once the bootloader has been rolled back, you can use Odin to reinstall Nougat (or whatever). I don't know whether this might require a particular build of Odin, but I doubt it
Droiderat said:
As others have pointed out, you can't use Odin to successfully flash a ROM with a bootloader that is earlier (in version) than the bootloader you have installed. The "gatekeeper" is Odin, however, not the bootloader.
Though I haven't tried it, it is my understanding that there is a way around this. Install TWRP, and use it to install a custom ROM which uses the version of bootloader that you want/need. Once the bootloader has been rolled back, you can use Odin to reinstall Nougat (or whatever). I don't know whether this might require a particular build of Odin, but I doubt it
Click to expand...
Click to collapse
i cant even begin to imagine how/why that would work. the bootloader doesnt really care what ROM you install, its the other way around. The ROM being installed has to be compatible with the bootloader. So, installing a ROM wouldnt really do anything to the bootloader and therefore wouldnt be able to bypass the lock in knox.
The procedure I outlined apparently works where the custom ROM includes a related bootloader. Thus, when it is installed via TWRP, it replaces both the existing ROM and the bootloader. I know that TWRP can be used to install a bootloader, as I have done it (on a SM-930F). And if the gatekeeper is Odin and not the bootloader itself, then this could work.
As I stated, I haven't tried this, nor have I extensively researched it. I've only read about it, and am passing it along as a possible solution.
This post can be closed since the phone was deemed Lost or Stolen by the carrier, therefore they couldn't unlock it for me to use my SIM card. I've since returned the phone. At least I learned a few lessons for my next one. Mainly, back up the phone when you first get it. Thanks again for all of the feedback.
Greetings. After trying Derpfest on my Redmi Note 7 Pro, I decided to switch back to MiUI. I wiped out the entire Custom ROM, then installed Indian version firmware, and then installed the latest MiUI ROM in recovery mode (I prefer Orange Fox). After that, I wanted to relock my bootloader so I got the latest MiUI 11 fastboot ROM and then used MiFlash and used the clean_all_and_lock option. My device relocked it's bootloader, however, it turned out that several things like sensors or Find Device service were not working correctly. It also showed a message "Find device storage corrupted, your device is now unsafe". Looking for solutions, I ended up unlocking the bootloader again, getting back OFox, and installing the persist.img file which I extracted from my fastboot ROM. This fixed the issue with the sensors. But now, I still can't get access to services like Find Device (both from Xiaomi and Google). If I have to avoid the 'Find Device Storage corrupted' error, I have to unlock bootloader. If I have to lock bootloader, I get the error message. What am I supposed to do?
I also have tried older Fastboot ROMs, although they were all MiUI 11. Should I try fastbooting into a MiUI 10 ROM and then get OTA to do everything else? If this is the case, which specific version of MiUI 10 ROM should I flash? I can't remember which version my phone came with. My model number M1901F7S. And also, I've never used Magisk. I didn't really care if I wanted to root or not. Derpfest passed Safetynet pretty nicely. But now I do not wish to root. I don't want Magisk or anything else, I want to secure the phone just as it was before.
EDIT : Turns out that Find Device (from both Google and Xiaomi) are actually working, just in a less effective scale than what I previously used to have (before getting the custom ROM). But yet, can I bring my phone back to the locked bootloader state? I want to secure it completely, just like how it was when it came out of the box. I also cannot install apps like Netflix. I would really like to know how to relock my bootloader.
EDIT 2: I've fixed it. Indeed, I had to flash a stock MiUI 10 ROM. Version 10.0.2 and whatever number ahead worked for me and gave me no problems, and then I simply updated to MiUI 11 using OTA Updates.
However, I do not recommend using MiFlash tool, and instead recommend pasting the ROM files into your platform_tools folder and then running flash_all_lock/flash_all. MiFlash may sometimes glitch and cause problems.