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
Hi guys, i have a galaxy s7 of a customer that doesn't absolutely remember email and password for his google account connected to the phone(and so it's OEM Locked).
i tried to follow many guides on the forum but this happened:
i can't root the phone (because the FRP is locking the Flash),
nor install 6.0.1 (because of the error "sw rev check fail device 2 binary 1")
i can't use bluetooth method to skip setup guide (it was fixed in 6.0.1)
i can't use RealTerm because it can't make me save the number to proceed the guide(also fixed in 6.0.1)
what can i do? how do i bypass the FRP? or how do I downgrade to 6.0.1?
Downgrading can be a problem caused by the bootloader, make sure you try to flash a stock ROM with the same version bootloader as shown with this number
G930FXXU2ERD5
The customer would have had to enter a secondary / recovery email while making that Google account, tell them to check their other email addresses for confirmation emails around the time they set up the phone, then they can find the email address of the google account and reset the password to that email address
You have to downgrade to 6.0 and then there are plenty of ways to unlock.
Download 6.0 and latest firmware.
In Odin
1st and 3rd field from old firmware
2nd and 4th field from new firmware
If You need guide how to unlock from 6.0 let me know
LaHunnid said:
You have to downgrade to 6.0 and then there are plenty of ways to unlock.
Download 6.0 and latest firmware.
In Odin
1st and 3rd field from old firmware
2nd and 4th field from new firmware
If You need guide how to unlock from 6.0 let me know
Click to expand...
Click to collapse
1st and 3rd field in ODIN is Bootloader & Modem
If you flash new firmware to 2nd and 4th you'll end up with new firmware flashed with old bootloader and it won't boot most likely / brick
*Detection* said:
1st and 3rd field in ODIN is Bootloader & Modem
If you flash new firmware to 2nd and 4th you'll end up with new firmware flashed with old bootloader and it won't boot most likely / brick
Click to expand...
Click to collapse
I did that and it didn't brick
LaHunnid said:
I did that and it didn't brick
Click to expand...
Click to collapse
AP is the system / OS, you're telling OP to flash a new version of Android (AP) with an old bootloader, in order to downgrade to 6.0.1, your method would not downgrade anything other than bootloader & modem and old bootloader with new OS will almost certainly brick
To downgrade you need to flash old bootloader (BL) & old Android 6.0.1 (AP), and probably old modem (CP), CSC is the only thing left
And as already stated, downgrading the BL is the problem that prevents most people from downgrading in the first place
check out my tutorial https://forum.xda-developers.com/galaxy-s7/how-to/g930f-frp-unlock-helps-99-g930f-t3791424
Massive thanks
S6unbricker said:
check out my tutorial https://forum.xda-developers.com/galaxy-s7/how-to/g930f-frp-unlock-helps-99-g930f-t3791424
Click to expand...
Click to collapse
I've been absolutely stuck for days trying to sort out the bloody FRP lock on an S7 (SM-G930F) that had been gifted to my wife by my father-in-law where he hadn't removed the accounts before passing it over.
My wife then did an update that the phone requested when it started up and that went wrong at which point I get involved and factory reset it...oh BIG mistake... and that's where my problems started made worse by the fact my father-in-law couldn't remember which account he had setup on the phone....or even the password to possible accounts!! I consider myself to be well versed in all things tech but I had absolutely no idea FRP existed and was absolutely baffled when i saw the message on the screen after flashing the stock firmware (G930FXXU2DRB6) that was on there according to the recovery mode. I've been trying so many different things over the past week all current methods failed...then I came across this one...which had seemed to be blocked by admins but I was able to click on the link in the 2nd post and grab the password from the readme in the first, which i must admit made it a bit dubious and not sure why @S6unbricker felt the need to do that but there's no issues it doesn't go to a stupid survey site or anything it just goes to a text file on mega which has one line and that's the password!
I followed the method to the letter and, to my surprise and joy, it's actually worked a treat...the S7 is no longer a paper weight!!!
Massive thanks to @S6unbricker :good: ...any chance of re-posting but without the password on the file or putting the password in the post?
Frp doesn't block eng bootloader...after u flash eng boot u can simply use Abd command to remove. Or the longer method flash factory binaries. Enable oem unlock (most important part). Then flash stock rom make sure to remove userdata.img ....on a side note wondering if adding the Samsung retail app and activating it, then using the login data to remove the app via factory data reset might work.
deshaney said:
Frp doesn't block eng bootloader...after u flash eng boot u can simply use Abd command to remove. Or the longer method flash factory binaries. Enable oem unlock (most important part). Then flash stock rom make sure to remove userdata.img ....on a side note wondering if adding the Samsung retail app and activating it, then using the login data to remove the app via factory data reset might work.
Click to expand...
Click to collapse
From my experience the combination roms (which I presume you are referring to when you say eng bootloader) didn't solve my issue. Yes I could get them on the phone and boot into them, change the settings or use adb but obviously I don't want the factory binary to stay on there so as soon as I flashed it back to the current firmware, back to square one!
Most poeple advised to use HOME CSC instead of CSC when flashing from combination rom back to stock but I couldn't get odin to flash with HOME CSC.
No I'm referring to the boot.img file. Combination ROMs don't enable su access via she'll.
Samsung s7
Ok I know this is an old Post but I'm brand new to Odin and all the unlock lingo.. can anyone explain to me how to downgrade to bypass the frp on my Galaxy I just bought , I'm very tech savvy just need a walkthrough any help would be greatly appreciated
Id like to downgrade my S7 from nougat to marshmallow. My current lowest factory reset option is nougat on bootloader version 3. Id like to downgrade to a downloaded stock firmware that uses version 1 of the bootloader.
my device is currently rooted and carrier unlocked
ive made a full backup of the nougat system, before ive done anything to it other than the rooting.
ive been reading around that some people were able to bypass the downgrade bootloader lock error in odin by first going into their desired downgraded firmware tar files and deleting any file that ends in .bin , and then successfully been able to flash the older firmware. what I want to know is if i decide to try this, and it still doesnt work in odin, or something still doesnt work properly - am i still able to fully restore from that backup ive just made? has anyone done this without issues? i hate the look and feel of nougat and oreo looks and feels the exact same...
i did make another thread about downgrading, but i didnt know nearly as much at the time. Been told downgrading is impossible and thats true, officially speaking. Id just like to know if anyone has been successful with this workaround.
What model, SM-G930F? Is OEM Unlocking turned on?
If it's a G930U/V/T/A/P then you won't be able to.
For the G930F so long as you don't have the latest Nougat version it shouldn't prevent downgrading. Otherwise upgrading up to Oreo then back down just by flashing in Odin should work, as Oreo doesn't have the downgrade lock that the newest Nougat has.
Beanvee7 said:
What model, SM-G930F? Is OEM Unlocking turned on?
If it's a G930U/V/T/A/P then you won't be able to.
For the G930F so long as you don't have the latest Nougat version it shouldn't prevent downgrading. Otherwise upgrading up to Oreo then back down just by flashing in Odin should work, as Oreo doesn't have the downgrade lock that the newest Nougat has.
Click to expand...
Click to collapse
model is sm-g930w8 but yes OEM unlocking is on, and so is usb debugging just to be on the safe side. It is running the very first version of nougat right now, 7.0. But the security patch is from feb 2018. Ive read that the bootloader itself is unlocked on this version of the phone though, its just that downgrade protection in the software that could get in the way, if what i read was correct? in the same place was where i read that deleting those bin files from the firmware i want to install would be a good workaround, it would make the bootloader not check it at all if i read it correctly.
i havent tried anything yet, ive been doing my research first to stay on the safe side. it might work without issues, but I want to be prepared for if issues do arise, what the correct next step should be to keep the device itself not bricked
Yea not 100% sure for the G930W8, it's the same SoC as the G930F but the firmware restrictions could be different since it's the Canada specific version
so, i decided to brave it and try it, since to read around you find alot of conflicting information... i was suspecting that odin would fail shortly after starting at sboot.bin if it was the bootloader thats the issue. but it didnt. it failed the very next step after that at param.bin.
anyone happen to know what param.bin means?
What files are you trying to flash? I have had the same problem, even though the bootloader is unlocked the device has efuses that prevent downgrade to older binary. I was using U2 binary and only managed to downgrade to nougat u2 binary version. Even when I skipped bootloader files, marshmallow would still give an error that system.img is version 0 where as device is v1
Good morning
So I've a xiaoxin pad 11 pro:
Model: tb-j706f
android version: 10
software version: tb-_706f_rf01_201229
ROM: TB-J706F_S240073_201229_ROW
kernel: 4.14.117 from 2020
Widevine: L1
And I whant to update to TB-J706F_S620150_211226_ROW. So my questions are many
-Can i use lenovo sofware to update?
-Do i need to lock or unlock oem bootloader from settings?
-Can only be done using QFIL or other softwares?
-Do i need to find out if it's region lock?
-How to backup this img, if everything goes wrong?
-Do i have to install the original chinese version, or can i just update the international one?
I see alot of threats talking about going from international to chinese, but I like to have play store and keepping widevine lv.1. Without having to do a lot of "work".
I've tried to use the OTA function, but downloads the update (just after my current version) it restart's and gets to the lenovo logo on the screen and reboots. Like a boot loop. I've to manually shutdown the tablet and it's back to normal.
After readding this forum, i still dont see a uniform way to update this device, and more importantly a easy way to do it. Can all of you help me?
- yes
- no
- yes
- even CN versions can be flashed with global rom
- you could still flash an img you download online if something wrongs happen
- it's on your own, if you have L1 with global unless you want latest updates no need to go CN, stay global.
if OTA update doesn't work maybe reset the device or even flash the newest rom available from lolinet then update with OTA.
@melones22 Thanks for the aswers.
Do you know if i download the newest global rom from lolinet, and force install, if i keep my lv1?
if you relock bootloader, likely. personally with natsafety patch + hde etc still l3
be absolute sure that you didn’t modified anything else than flashing before relocking
front3 said:
Good morning
So I've a xiaoxin pad 11 pro:
Model: tb-j706f
android version: 10
software version: tb-_706f_rf01_201229
ROM: TB-J706F_S240073_201229_ROW
kernel: 4.14.117 from 2020
Widevine: L1
And I whant to update to TB-J706F_S620150_211226_ROW. So my questions are many
-Can i use lenovo sofware to update?
Click to expand...
Click to collapse
Yes, but I nver used it
front3 said:
-Do i need to lock or unlock oem bootloader from settings?
Click to expand...
Click to collapse
If you flash stock ROMs CN or Global you do NOT need to unlock bootloader
front3 said:
-Can only be done using QFIL or other softwares?
Click to expand...
Click to collapse
To flash a ROM you can use QFIL, I never used Lenovo softwaare so I am not sure if you can flash form there only last version or if you have a choice.
Normally you should not be required to use QFIL and you should be able to update with OTA updates.
front3 said:
-Do i need to find out if it's region lock?
Click to expand...
Click to collapse
If you are having problems updating I guess it doesn't hurt finding that out.
front3 said:
-How to backup this img, if everything goes wrong?
Click to expand...
Click to collapse
You should backup QCN with QFIL and all partitions (you can probably exclude vendor and userdata) with QFIL or edl, there is a guide for both methods (I use edl) https://forum.xda-developers.com/t/two-ways-to-backup-tb-j706f-without-unlocking-bootloader.4402799/
front3 said:
-Do i have to install the original chinese version, or can i just update the international one?
Click to expand...
Click to collapse
You should be able to update your global ROM but since you are having problems I don't exclude you might need to go back to CN ROM before flashing again the Global ROM.
front3 said:
I see alot of threats talking about going from international to chinese, but I like to have play store and keepping widevine lv.1. Without having to do a lot of "work".
I've tried to use the OTA function, but downloads the update (just after my current version) it restart's and gets to the lenovo logo on the screen and reboots. Like a boot loop. I've to manually shutdown the tablet and it's back to normal.
After readding this forum, i still dont see a uniform way to update this device, and more importantly a easy way to do it. Can all of you help me?
Click to expand...
Click to collapse
I am not sure what's the problem with your OTA update.
I would suggest to:
Backup your QCN and all partitions first
Open your QCN with QCNView and check the region in NV Item 6858
If your region is 02 is Global and OTA update should work, so maybe try a factory reset and see if after OTA update works.
If it's 00 (region unlocked) or 01 (China) that might be the reason OTA updates are not working.
Edit
I read again the version you have now and it's quite old, that probably does not have any region lock.
In the one tablet I had from the shop with Chinese ROM I flashed TB-J706F_S250260_210804_ROW, that set it as global region and then from that I run OTA updates.
So I think you should backup as I said before and then flash TB-J706F_S250260_210804_ROW, make sure to select the right settings in QFIL and NEVER check "Reset state machine".
MrCrayon said:
Yes, but I nver used it
If you flash stock ROMs CN or Global you do NOT need to unlock bootloader
To flash a ROM you can use QFIL, I never used Lenovo softwaare so I am not sure if you can flash form there only last version or if you have a choice.
Normally you should not be required to use QFIL and you should be able to update with OTA updates.
If you are having problems updating I guess it doesn't hurt finding that out.
You should backup QCN with QFIL and all partitions (you can probably exclude vendor and userdata) with QFIL or edl, there is a guide for both methods (I use edl) https://forum.xda-developers.com/t/two-ways-to-backup-tb-j706f-without-unlocking-bootloader.4402799/
You should be able to update your global ROM but since you are having problems I don't exclude you might need to go back to CN ROM before flashing again the Global ROM.
I am not sure what's the problem with your OTA update.
I would suggest to:
Backup your QCN and all partitions first
Open your QCN with QCNView and check the region in NV Item 6858
If your region is 02 is Global and OTA update should work, so maybe try a factory reset and see if after OTA update works.
If it's 00 (region unlocked) or 01 (China) that might be the reason OTA updates are not working.
Edit
I read again the version you have now and it's quite old, that probably does not have any region lock.
In the one tablet I had from the shop with Chinese ROM I flashed TB-J706F_S250260_210804_ROW, that set it as global region and then from that I run OTA updates.
So I think you should backup as I said before and then flash TB-J706F_S250260_210804_ROW, make sure to select the right settings in QFIL and NEVER check "Reset state machine".
Click to expand...
Click to collapse
Hi Mr. Crayon,
Is there any guide in how to do as what you mentioned above ? I'm quite new to this 'manual update' and still learning. Would really appreciate your help on this. My Xiaoxin Pad Pro 2020 (TB-J706F_S268018_210731_ROW) is still running on android 10 and my device is not certified by play protect. T.T
Hello.
Thanks @MrCrayon, but i never has able to use qfil to backup my device. To complicated for me. But thanks for the help.
So what i did to update my tablet. After feeling the same way @shaoki92 , i just tried to use lenovo tools. And... puff... update done.
No problems what so ever,
Did not lose L1
And did not have to mess with bootloader or region lock.
But i understand that i took a big risk. The tablet could've become just a paper weight. But until now working fine. With new android and everything.
front3 said:
Hello.
Thanks @MrCrayon, but i never has able to use qfil to backup my device. To complicated for me. But thanks for the help.
So what i did to update my tablet. After feeling the same way @shaoki92 , i just tried to use lenovo tools. And... puff... update done.
No problems what so ever,
Did not lose L1
And did not have to mess with bootloader or region lock.
But i understand that i took a big risk. The tablet could've become just a paper weight. But until now working fine. With new android and everything.
Click to expand...
Click to collapse
Hi front3,
May i ask how do you update using lenovo tools ? Thanks
Im no expert that so ever. But i can tell you that i did.
Install lenovo assistance, on windows.
Used the charging cable of the tablet to connect to pc.
Launch the app
Connect to the device via app
(And i dont remember now, but i think its recue my device, and update, inside the app)
The app gives you a warning about using the tool on CH devices, and i took the risk.
Check the firmware version that the app gives you, and what it the lastest that has been deploid. Just to be sure. And do it if you dont mind taking the risk, do it.
In my case, the version that the app recomended has not on lolinet at that time. It only show up there, weeks later. But because the app connects to lenovo servers directly, i think it was safe.
Be careful because you can brick the device. And like @MrCrayon explained, i had one very old firmware, so xiaoxin didnt have the same "security" feactures has the newer devices. So maybe that is why it worked.
So, I rooted my device couple of month ago.
Long story short I had a problem and don t have magisk on my phone anymore
I want to unroot my device. But what i have read is that i need the original firmware with the boot.img that came with my phone when I rooted it.
Ihave search my device and the magisk folder got deleted and so I don t have the backup of boot.img that magisk did for me.
If I download the firmware with frija (the baseband is that the version number) can I restore the phone to his original state ?
And is there a way to have the original bootloader back and enable knox again ?
Thanks
When i input the baseband in frija the software let me download the latest version of the software on android 12.
Is it possible to find the original version of the software that came it was android 11
Everything is included in the firmware for reverting back, although not necessarily needed, i would advise for a reset as well. You can do that in one go by flashing CSC instead of HOME_CSC.
About KNOX, forget it, you're done. I haven't rooted a Samsung phone since the 2019, and don't see any reason to anymore, but if you do, i don't see a reason to revert back either since KNOX is out of the question.