Database Info

Is it possible to convert a hero2lte into a dream2lte or star2lte by flashing BL&CP?

Is it possible to convert a hero2lte into a dream2lte or star2lte by flashing BL&CP?
Ok, this may seem like a silly question, but seeing how awesome developers are at tweaking devices to run passed the two next model releases, perhaps this isn't the dumbest inquirey. Ok, my question is CAN YOU CONVERT a hero2lte device into a dream2lte or even star2lte device? *All EXYNOS models* (which is basically Galaxy s7edge into S8+ or even to an S9) by flashing the BL Bootloader and CP Modem in TWRP, or will this BRICK the hero2lte, and if so, would I begin from the Android Marshmallow 6.0 BL Bootloader and CP Modem, or does it matter? The main reason I'm actually asking this, is because I love the BatMan S7edge sm-g935w8 S8+ ROM on Nougat, but I just want Oreo, even though SuperMan ROM comes in Oreo, and is pretty much just as awesome, especially since you can change the folder colours to literally any colour you want, via colour pallet, but for some reason, BatMan ROM was still my fave, and there is an Oreo 8.0 version released, but it is for dream2lte for the S8+ actually (the s8_rom was still listed as for the sm-g935w8, not sm-g955), so I'm wanting to flash the BL and CP and the rom to my Galaxy S7 edge, but I love it and don't want to BRICK IT! LOL not funny. But seriously, if anyone could help me in guiding me with if this is safe to do a conversion, since the hardware can probably handle the features is what im thinking, but if someone could clerify this for me, I would be much appreciative of you taking the time. :good:THANKS IN ADVANCE! R00+ (Joseph)

R00+ said:
Ok, this may seem like a silly question, but seeing how awesome developers are at tweaking devices to run passed the two next model releases, perhaps this isn't the dumbest inquirey. Ok, my question is CAN YOU CONVERT a hero2lte device into a dream2lte or even star2lte device? *All EXYNOS models* (which is basically Galaxy s7edge into S8+ or even to an S9) by flashing the BL Bootloader and CP Modem in TWRP, or will this BRICK the hero2lte, and if so, would I begin from the Android Marshmallow 6.0 BL Bootloader and CP Modem, or does it matter? The main reason I'm actually asking this, is because I love the BatMan S7edge sm-g935w8 S8+ ROM on Nougat, but I just want Oreo, even though SuperMan ROM comes in Oreo, and is pretty much just as awesome, especially since you can change the folder colours to literally any colour you want, via colour pallet, but for some reason, BatMan ROM was still my fave, and there is an Oreo 8.0 version released, but it is for dream2lte for the S8+ actually (the s8_rom was still listed as for the sm-g935w8, not sm-g955), so I'm wanting to flash the BL and CP and the rom to my Galaxy S7 edge, but I love it and don't want to BRICK IT! LOL not funny. But seriously, if anyone could help me in guiding me with if this is safe to do a conversion, since the hardware can probably handle the features is what im thinking, but if someone could clerify this for me, I would be much appreciative of you taking the time. :good:THANKS IN ADVANCE! R00+ (Joseph)
Click to expand...
Click to collapse
No, it doesn't work like that. S7 edge can only use S7 edge firmware, S8+ can only use S8+ firmware, S9 can only use S9 firmware and so on and so on.
Some of the apps and features can be "ported" or modified to work from one model to the next but you can't just flash firmware or firmware parts from one model on another model, it must be properly ported first.
Sent from my LGL84VL using Tapatalk

makes sense, thanks for the reply. One more thing to add or question rather, i was with a coder friend a few nights ago and asked him the same thing, and he said it could be possible using "Real Term" which he said was similar to Odin but way more advanced to go deeper into the coding to write to the BIOS to basically accomplish my question, as a first step before going to them flashing BL n' CP thru Odin. Any take on what I was told of this at all? (On REAL TERM being able to write to BIOS to change device to another model, that is) hopefully this shines some new light instead of asking the same question twice. lol
Thanks again,
R00+ (Joseph)

R00+ said:
makes sense, thanks for the reply. One more thing to add or question rather, i was with a coder friend a few nights ago and asked him the same thing, and he said it could be possible using "Real Term" which he said was similar to Odin but way more advanced to go deeper into the coding to write to the BIOS to basically accomplish my question, as a first step before going to them flashing BL n' CP thru Odin. Any take on what I was told of this at all? (On REAL TERM being able to write to BIOS to change device to another model, that is) hopefully this shines some new light instead of asking the same question twice. lol
Thanks again,
R00+ (Joseph)
Click to expand...
Click to collapse
Samsung android devices do not have a BIOS, android and PC are nothing alike. Virtually nothing that applies to PC applies to android. Whatever that guy was telling you is a load of crap and hasn't a clue what they are talking about
Intel atom based android tablets do have a BIOS, but it doesn't do the same thing on these tablets that it does on PC, it only comes into play when booting the device, but then the bootloader takes over and handles everything else as if the BIOS were never there. In android, the bootloader is everything and bootloaders can't be switched between devices, bootloaders are model number specific. Using a bootloader on a device that it wasn't specifically built for will result in a hard bricked device that can only be fixed by replacing the motherboard or by using a RIFF box or JTAG.
Stop looking for a way or trying to theorize, there is ABSOLUTELY no way to do what you are asking about, period, it isn't going to happen. You aren't the first person to have this idea.
As I already stated, you can port the system.img from one model to another but only if they have the same CPU/hardware architecture, you CANNOT use any other parts of a firmware from another device, only the system.img and it MUST be ported/modified to work on the new device, it can not be flashed or installed as-is. Porting the system.img is the only way you're going to get anything from the S10 to install on S9. Another option that "might" be possible is to build a custom ROM for S10 using the S10 stock source code and then porting that ROM to work on S9, but that requires an unlocked bootloader and also requires having TWRP custom recovery to flash the custom ROM.
Do some searching to learn how to port Samsung firmware from one device to work on another.
Sent from my LGL84VL using Tapatalk

Downgrading my (unrooted) carrier locked At&t Note 8.

My note 8 had OneUI pushed to it about a week ago even though I kept refusing not wanting to while I was sleeping. It says my bootloader is v5. This is actually what it says (N950USQU5DSD3). My problem is that when I search for the firmware I'm wanting to downgrade to (the last oreo update possible for this particular phone) on Sammobile I can't find the one for At&t. I see ones for Verizon, sprint, etc. But nothing for at&t, which one am I supposed to use and where can I get it? This is going to be my very first downgrade/upgrade, really my first time doing anything like it on android. And I CAN do this right? There's nothing I should be aware of that makes what I'm trying to do not able to be done is there? The biggest reason I'm asking is because I have very limited tools to work with, I have a little 12" Acer aspire one (no disk drive) running windows 7 home basic, mobile hotspot from my wife's phone(the last software I tried to download and use came from xda out of a thread I found titled, "Stock Oreo N950USQS5CRF6 Odin*files*for AT&T*NOTE*8" it failed halfway through 2 nights ago during the beginning of storm, and the whole time it would only download around 32kbs so it literally to FOREVER! Only for it to fail halfway through. Was I wasting my time or was this in fact the firmware I'm looking for? If not, as I asked before, where could I find it?? Thanks a bunch for any help.

https://forum.xda-developers.com/at...n950u-stock-n950usqs5crf6-odin-files-t3821222
^^^^^^^Is this all I need? Do I need to follow this tutorial or a different one?? What version of odin, do I need anything else
Sorry for so much all at once, I really hate this update and want Oreo back.

https://forum.xda-developers.com/ga...m-n950u-u1-t3685884/post74087340#post74087340
Follow the steps from the above-linked post, and follow them very carefully. I did, and I was able to successfully downgrade from Pie to Oreo on my AT&T NOTE8.
I actually flashed the unlocked firmware, which has zero AT&T bloat. It works just fine for my needs. I don't think AT&T WiFi calling works on this unlocked firmware (I haven't tried - I don't use it).
Caveat emptor: whichever version of Oreo you choose (either the AT&T stock, or the unlocked firmware), we are stuck on the February 2019 Android security patch.
Only Pie gets the latest security patches. As long as you are ok with this, then proceed with the downgrade to Oreo!

pyrolad said:
Caveat emptor: whichever version of Oreo you choose (either the AT&T stock, or the unlocked firmware), we are stuck on the February 2019 Android security patch.
Only Pie gets the latest security patches. As long as you are ok with this, then proceed with the downgrade to Oreo!
Click to expand...
Click to collapse
A little off topic, but has anyone seen an AT&T security update for May yet? I'm still on April security, and it's basically mid June?

Tha k you I'll check it out when I get off work, I didn't know you could flash the unlocked firmware on a carrier locked phone

Let me get this straight. Can a locked bootloader AT&T SM-N9500U on Android 9, N9500USQU5DSD3 downgrade to Oreo? I thought this bootloader whould not let you go back.
I LOATH Pie and wan to go back to Oreo so bad, please tell me there is a for sure way. This is my first permanently locked bootloader phone and it's killing me not to flash an software I prefer.

I dont know I wish someone could tell me forsure whether it will work or not because now my phone is getting another software update notification so it's getting ready to force another update on me and I doubt after that I will still have bootloader v5. Can someone please verify whether my current bootloader (N9500USQU5DSD3) will downgrade successfully to back to oreo or not? I have the oreo firmware I want to use downloaded and ready to go which is (SM-N950USQU5CRL1). Can I downgrade to this without messing anything up?? Please I need a fast reply I dont want this new update forced to my phone and updating my bootloader to v5 where I can ever go back to oreo.

marhodges said:
Let me get this straight. Can a locked bootloader AT&T SM-N9500U on Android 9, N9500USQU5DSD3 downgrade to Oreo? I thought this bootloader whould not let you go back.
I LOATH Pie and wan to go back to Oreo so bad, please tell me there is a for sure way. This is my first permanently locked bootloader phone and it's killing me not to flash an software I prefer.
Click to expand...
Click to collapse
Yes you CAN downgrade back to Oreo. BUT you MUST go to a bootloader 5 firmware.
---------- Post added at 07:55 AM ---------- Previous post was at 07:54 AM ----------
Superloud024 said:
I dont know I wish someone could tell me forsure whether it will work or not because now my phone is getting another software update notification so it's getting ready to force another update on me and I doubt after that I will still have bootloader v5. Can someone please verify whether my current bootloader (N9500USQU5DSD3) will downgrade successfully to back to oreo or not? I have the oreo firmware I want to use downloaded and ready to go which is (SM-N950USQU5CRL1). Can I downgrade to this without messing anything up?? Please I need a fast reply I dont want this new update forced to my phone and updating my bootloader to v5 where I can ever go back to oreo.
Click to expand...
Click to collapse
Yes you can go to that firmware. You will want to back up and allow it to factory reset. Be sure to use the modified version of Odin. Go HERE, post #2

KG state prenormal after 7 days no reboots

I have an SM-A530F and had no issues flashing roms and TWRP. I eventually tried Saboor OneUI from and my phone got completely encrypted and would only allow official binaries to be flashed. I flashed Binary 7 (Pie) to my device and tried to flash TWRP but had come across the error and after researching realised I'd have to wait 7 days with the phone continuously booted up. I have waited 7 days with nothing changed. I'm now on my 25th day and still have a prenormal KG state. But in developer options my OEM states that it is already unlocked and I can switch the toggle. I cannot flash TWRP or magisk though.

The same thing happens to me and I used the chimera program and nothing works. 12 euros in the trash.
they have returned my money

almeria53 said:
The same thing happens to me and I used the chimera program and nothing works. 12 euros in the trash
Click to expand...
Click to collapse
I've tried multiple binaries and nothing. Bootloader says its unlocked and even with adb commands I get an unlocked status but the RMM/KG remains prenormal. I'm wondering if anyone can repack TWRP for jackpotlte so the device and Odin THINKS it's an official recovery binary?

Zefpoes23 said:
I've tried multiple binaries and nothing. Bootloader says its unlocked and even with adb commands I get an unlocked status but the RMM/KG remains prenormal. I'm wondering if anyone can repack TWRP for jackpotlte so the device and Odin THINKS it's an official recovery binary?
Click to expand...
Click to collapse
i see you started another thread about this, so take my previous reply in that thread with a grain of salt. I still dont think its the TWRP file thats the culprit. Try reflashing stock firmware and do the 168 hour method again.

almeria53 said:
The same thing happens to me and I used the chimera program and nothing works. 12 euros in the trash.
they have returned my money
Click to expand...
Click to collapse
youdoofus said:
i see you started another thread about this, so take my previous reply in that thread with a grain of salt. I still dont think its the TWRP file thats the culprit. Try reflashing stock firmware and do the 168 hour method again.
Click to expand...
Click to collapse
I know TWRP isn't the culprit. But because of my predicament having waited well over 168 hours without a reboot (oem unlock toggle is available but still shows KG/RMM prenormal) I'm wondering if anyone can change TWRP to make the device think its an official recovery. That way I could flash it with a prenormal state as I can flash stock recovery no problem. If the device thought TWRP was official then that way I could still root and flash zip roms with a locked KG. I hope I'm making sense?

Zefpoes23 said:
I know TWRP isn't the culprit. But because of my predicament having waited well over 168 hours without a reboot (oem unlock toggle is available but still shows KG/RMM prenormal) I'm wondering if anyone can change TWRP to make the device think its an official recovery. That way I could flash it with a prenormal state as I can flash stock recovery no problem. If the device thought TWRP was official then that way I could still root and flash zip roms with a locked KG. I hope I'm making sense?
Click to expand...
Click to collapse
youre not going to get the phone to think that TWRP is official. If that was possible, we would all have root and without so much as unlocking the bootloader for that matter

manifesto- posted on another thread-sorry for the dupe
A bit of history gives a bit more depth/ Just when you thought it was okay to go back in the water. I'm Canadian you can probably tell by my accent. My journey with phones has always been Samsung simply due to availability s6 s7 s8 s8+ most recently the a530w.
In order for you to understand my joy finding the A8 and my horror is that the S8 series. in North America S8 uses a Qualcomm Snapdragon chip. g950u is SD g950f is the rest of the world (exnyos) This is probably due to some kind of World Trade Organization antitrust treaty {although qualcom makes great chips} or whatnot I don't care.
i do care about is their bootloader lock policy (g950u and up) so it is impossible to unlock an encrypted Snapdragon bootloader. When I ran into the a530w exnyos, I was like a three-year-old at Christmas now you have to understand I'm not a coder I'm more of a mason I'm familiar with bricks. I'm sure we've all watch the AP file upload and Odin like we watch paint dry. So when I first got the a530w pi version April patch I was able to TWRP install I believe at the time was Pixel project or something else added magisk, xposed you get the idea.
Eventually a file got corrupt (much like @Zefpoes23) and I had to common sense restock it. I think my mistake what is going with the most current pie version (hadn't read this thread yet from @corsicanu) which is binary 7 knowing what I know now I would have probably had the ability to go a binary 4 or so. I haven't done the 7 day challenge simply not to waste my sanity. my bootloader unlock never vanished, it like it's a light switch with no bulb. I've tried to backdated front dated. I refuse to wait 7 days to find out that I'm still at the same place. . The problem is all the fixes are zip files which you need TWRP to flash. I agree, it's not @BlackMesa123 version. it's the prenormal. No I'm certainly not a developer and some of them are mobile gods. My questions maybe Elementary logical. Is it possible to replace a recovery image in a stock AP and Odin flash it? Repack. Also is there any way to combo a stockfirm in order to downgrade from the B7. Alter it somehow so it's thinks it's a 7 but it's actually a 4 of some sort. think we're all about to become in the same boat. we could start a movement lie "#meprenormal2" In Time will tell. As or now "prenormal" is the new "normal" All I can to the devs: help me odin 3 canmodme. your my only hope

i have no idea what youre on about for half of this post, so ill chime in with what i could decipher and know the answer to
jthibault27 said:
Is it possible to replace a recovery image in a stock AP and Odin flash it? Repack. Also is there any way to combo a stockfirm in order to downgrade from the B7. Alter it somehow so it's thinks it's a 7 but it's actually a 4 of some sort.
Click to expand...
Click to collapse
nope, sorry man. you cant go backwards in bootloader revisions. if you have B7, youre stuck with revision 7
jthibault27 said:
I refuse to wait 7 days to find out that I'm still at the same place.
Click to expand...
Click to collapse
you wont have much say in this refusal as the 168 hour thing is quite normal. Every A8 owner ive seen come into these forums has had to do the 168 hour thing.

Youdoofus said:
i have no idea what youre on about for half of this post, so ill chime in with what i could decipher and know the answer to
nope, sorry man. you cant go backwards in bootloader revisions. if you have B7, youre stuck with revision 7
you wont have much say in this refusal as the 168 hour thing is quite normal. Every A8 owner ive seen come into these forums has had to do the 168 hour thing.
Click to expand...
Click to collapse
If I'm violating XDA rules please let me know. You are obviously higher up on the rank that I am. Since my post on November 10th my findings on other threads have led me to believe that this is not just an A8 problem but an entire Samsung Fleet. A summer security patch upgraded knox guard to disable any attempts to flash TWRP. If you are lucky enough to get through that stay on it. My bootloader is like a light switch I can on and off it at anytime. 168 hours is a solution for an old problem that I don't have. I'm in permanent prenormal state with the sole ability to only flash official stock firmware and in one direction v7 or higher.. Which is what Samsung wants. i'm on V7, security patch July 1st 2019. I cannot flash anything else through Odin 13.3.1. I'm simply voicing the fact 168 hours fix is to have the ability to unlock the bootloader. I have the bootloader unlocked. My kg is tripped and I believe my fix will come in Time through a modified Odin or combo firmware emerges. i will also recluse myself from posting on this thread and open my own
---------- Post added at 19:35 ---------- Previous post was at 19:20 ----------
Youdoofus said:
i have no idea what youre on about for half of this post, so ill chime in with what i could decipher and know the answer to
nope, sorry man. you cant go backwards in bootloader revisions. if you have B7, youre stuck with revision 7
you wont have much say in this refusal as the 168 hour thing is quite normal. Every A8 owner ive seen come into these forums has had to do the 168 hour thing.
Click to expand...
Click to collapse
And to clarify what I meant as to replace the recovery file in the AP stock firmware specifically unpacking the lz4 format using 7-Zip 19 ZS v144, replacing the recovery image with the TWRP Recovery image and repacking it (the AP) and flashing it hoping the phone with think it's official. I've consulted a developer who tried it several times without any luck since he shares the same problem on a50.

jthibault27 said:
If I'm violating XDA rules please let me know. You are obviously higher up on the rank that I am. Since my post on November 10th my findings on other threads have led me to believe that this is not just an A8 problem but an entire Samsung Fleet. A summer security patch upgraded knox guard to disable any attempts to flash TWRP. If you are lucky enough to get through that stay on it. My bootloader is like a light switch I can on and off it at anytime. 168 hours is a solution for an old problem that I don't have. I'm in permanent prenormal state with the sole ability to only flash official stock firmware and in one direction v7 or higher.. Which is what Samsung wants. i'm on V7, security patch July 1st 2019. I cannot flash anything else through Odin 13.3.1. I'm simply voicing the fact 168 hours fix is to have the ability to unlock the bootloader. I have the bootloader unlocked. My kg is tripped and I believe my fix will come in Time through a modified Odin or combo firmware emerges. i will also recluse myself from posting on this thread and open my own
---------- Post added at 19:35 ---------- Previous post was at 19:20 ----------
And to clarify what I meant as to replace the recovery file in the AP stock firmware specifically unpacking the lz4 format using 7-Zip 19 ZS v144, replacing the recovery image with the TWRP Recovery image and repacking it (the AP) and flashing it hoping the phone with think it's official. I've consulted a developer who tried it several times without any luck since he shares the same problem on a50.
Click to expand...
Click to collapse
naw man, youre good. i had an A8 for about a year and now the older kiddo has it and it seems to be working well as i havent heard any complaints as of yet.
I, by no means, am an expert on this device and i admittedly have not kept current on the 168 hour fix no longer being relevant.
There is a fellow who had this forum on point about a year ago, cant recall his alias. Ill tag him if i can find him. Hopefully he has kept current on this device more than I.

@mchlbenner if you have a moment, could you lend a hand?

Youdoofus said:
naw man, youre good. i had an A8 for about a year and now the older kiddo has it and it seems to be working well as i havent heard any complaints as of yet.
I, by no means, am an expert on this device and i admittedly have not kept current on the 168 hour fix no longer being relevant.
There is a fellow who had this forum on point about a year ago, cant recall his alias. Ill tag him if i can find him. Hopefully he has kept current on this device more than I.
Click to expand...
Click to collapse
I started in this thread because I had a8 after researching through a bunch of different search engines I found this link
https://forum.xda-developers.com/galaxy-note-9/help/rmm-prenormal-oem-unlock-android-9-0-t3952959
it ended to be a note link. The moderator is convinced that it's all in our heads but people have been flocking to this thread because the title is so specific that it brings in people from different Samsung devices. It's like Field of Dreams, if you can't mod it they will come. Anyway, there are interesting comments. I apologize if my redirect or hyperlink is off. I'm no expert in this web forum platforms.

jthibault27 said:
I started in this thread because I had a8 after researching through a bunch of different search engines I found this link
https://forum.xda-developers.com/galaxy-note-9/help/rmm-prenormal-oem-unlock-android-9-0-t3952959
it ended to be a note link. The moderator is convinced that it's all in our heads but people have been flocking to this thread because the title is so specific that it brings in people from different Samsung devices. It's like Field of Dreams, if you can't mod it they will come. Anyway, there are interesting comments. I apologize if my redirect or hyperlink is off. I'm no expert in this web forum platforms.
Click to expand...
Click to collapse
This issue is true I have seen this on other a8 plus.
It part of Samsung security and no mod can fix this.

mchlbenner said:
This issue is true I have seen this on other a8 plus.
It part of Samsung security and no mod can fix this.
Click to expand...
Click to collapse
there you are!! so, the A8 is now not rootable?

Youdoofus said:
there you are!! so, the A8 is now not rootable?
Click to expand...
Click to collapse
It's very rootable provided that you don't do what 99% of the world do before selling it on Kijiji (Canadian version of Craig's list) is upgrade the latest OTA to impress the buyer. if you have an Oreo built Axxx or Sxxx (basically an Exynos chip) you are golden. not going to get into the whole North American snapdragon-Qualcomm thing. If you have a (guessing) Pre-June 2019 security patch however 9.0 I believe you can flash TWRP (all things being equal) you have a chance. however, if you have (I'm guessing most recent models) 9.0 security patch July 1 2019+ stock (previously tripped KG on a custom ROM-which say got corrupt), you are in the non-mod world. you are stuck with 9.0 official Samsung. you can't flash oreo (until someone develops a matching binary). since through my sammobile travels, I've yet to encounter a baseband/BL Oreo higher than 4. my phone (a8 9.0) is B7

jthibault27 said:
It's very rootable provided that you don't do what 99% of the world do before selling it on Kijiji (Canadian version of Craig's list) is upgrade the latest OTA to impress the buyer. if you have an Oreo built Axxx or Sxxx (basically an Exynos chip) you are golden. not going to get into the whole North American snapdragon-Qualcomm thing. If you have a (guessing) Pre-June 2019 security patch however 9.0 I believe you can flash TWRP (all things being equal) you have a chance. however, if you have (I'm guessing most recent models) 9.0 security patch July 1 2019+ stock (previously tripped KG on a custom ROM-which say got corrupt), you are in the non-mod world. you are stuck with 9.0 official Samsung. you can't flash oreo (until someone develops a matching binary). since through my sammobile travels, I've yet to encounter a baseband/BL Oreo higher than 4. my phone (a8 9.0) is B7
Click to expand...
Click to collapse
Well I'm on gsi ROMs this will never see a Samsung rom ever again.
Also slot of don't follow rooting directions I have been lock out once on Oreo never had a problem with Android 9.

mchlbenner said:
Well I'm on gsi ROMs this will never see a Samsung rom ever again.
Also slot of don't follow rooting directions I have been lock out once on Oreo never had a problem with Android 9.
Click to expand...
Click to collapse
so, between what you and the other fella are saying, the newest factory OTA prevents folks from rooting this thing now, correct? That would be a shame, locking down even the F devices? Come on Samsung!!

Youdoofus said:
so, between what you and the other fella are saying, the newest factory OTA prevents folks from rooting this thing now, correct? That would be a shame, locking down even the F devices? Come on Samsung!!
Click to expand...
Click to collapse
note: This doesn't necessarily apply to everyone since my situation was that I had a custom ROM corrupt and I restock firmware to V7 on the A8. My original custom install using TWRP had triggered kg Knox. I should have not flashed the latest stock version of 9.0. This was simply just a bridge to a new custom firmware anyway. I did not realize that I was installing a security patch that Samsung would deploy. So the question is if you go and buy the latest a, n, s 9.0 (F) can you still TWRP? Or does it say pre normal as soon as you attempt to TWRP. Rooting is not even in the realm of possibilities if you can't install TWRP. Magisk now has a feature where it modifies the AP system file which you can Odin. I thought it would pass as official. Of course, it didn't. Those dam Samsung MIT grad security engineers probably think they're better than us. LOL. All I can tell you is the toggle for the unlock Bootloader is as effective as the close door button on an elevator, you're not sure if it's connected to anything. This has been an Android War since Jelly Bean.

jthibault27 said:
note: This doesn't necessarily apply to everyone since my situation was that I had a custom ROM corrupt and I restock firmware to V7 on the A8. My original custom install using TWRP had triggered kg Knox. I should have not flashed the latest stock version of 9.0. This was simply just a bridge to a new custom firmware anyway. I did not realize that I was installing a security patch that Samsung would deploy. So the question is if you go and buy the latest a, n, s 9.0 (F) can you still TWRP? Or does it say pre normal as soon as you attempt to TWRP. Rooting is not even in the realm of possibilities if you can't install TWRP. Magisk now has a feature where it modifies the AP system file which you can Odin. I thought it would pass as official. Of course, it didn't. Those dam Samsung MIT grad security engineers probably think they're better than us. LOL. All I can tell you is the toggle for the unlock Bootloader is as effective as the close door button on an elevator, you're not sure if it's connected to anything. This has been an Android War since Jelly Bean.
Click to expand...
Click to collapse
yes, from what ive gathered from mchelbenner, the party is over. I trust his input as he is very well versed in the A8. More than I as he has had this forum on lockdown even before i got my A8 to begin with. If he said its no longer possible, thats what i will go with also

Youdoofus said:
yes, from what I've gathered from mchelbenner, the party is over. I trust his input as he is very well versed in the A8. More than I as he has had this forum on lockdown even before I got my A8 to begin with. If he said its no longer possible, thats what i will go with also
Click to expand...
Click to collapse
If you ever come across a forum specific to this issue ({completely extrapolating the date by guess} July 1, 2019 9.0) but not necessarily specific to the A8, please share. as it stands now, my findings indicate isolated conversations in different forums on various models, sharing the same problem. We must unite! lol. truth be told, it's challenging searching for such a specific problem relating to a patch on many models.

Samsung S7 edge sm-G930V android version 8.0 Unlock Bootloader

Hello Guys i have been searching all over the internet for a few month, where do i find the boot unlock for this particular phone? I need this in order to root and install lineage OS custom rom
I really appreciate if someone has the information.

CAN ANYONE HELP PLEASE? I need to unlock bootloader for Verizon SM-G930V

ibex333 said:
CAN ANYONE HELP PLEASE? I need to unlock bootloader for Verizon SM-G930V
Click to expand...
Click to collapse
I just picked up this model myself and find myself in the same boat. My developer options do list an "OEM unlock" option. Does yours?

ibex333 said:
CAN ANYONE HELP PLEASE? I need to unlock bootloader for Verizon SM-G930V
Click to expand...
Click to collapse
Emmalfal said:
I just picked up this model myself and find myself in the same boat. My developer options do list an "OEM unlock" option. Does yours?
Click to expand...
Click to collapse
It doesn't matter, Verizon devices have locked bootloaders that can't be unlocked, don't waste your time trying, it isn't going to happen. Verizon devices have been this way for years now, I don't forsee that changing at any time in the future.

Droidriven said:
It doesn't matter, Verizon devices have locked bootloaders that can't be unlocked, don't waste your time trying, it isn't going to happen. Verizon devices have been this way for years now, I don't forsee that changing at any time in the future.
Click to expand...
Click to collapse
My device has the "oem unlock" button. Does that not matter? I was surprised as hell to find that.

Emmalfal said:
My device has the "oem unlock" button. Does that not matter? I was surprised as hell to find that.
Click to expand...
Click to collapse
You can try it but I'm pretty certain that Verizon has it locked down. There is a root method for Verizon S7 and S7 edge but no TWRP or custom ROMs that I know of.
Verizon S7 / S7 Edge [Root Guide] SM-G930V SM-G935V [NO KNOX TRIP]
Hi, I am compiling this guide for rooting the verizon variant. I also hope to fill in some gaps in the other guides. I AM NOT RESPONSIBLE FOR ANY PROBLEMS YOU MAY CAUSE OR ENCOUNTER I did not develop this, I'm only telling you how to do it...
forum.xda-developers.com

Droidriven said:
You can try it but I'm pretty certain that Verizon has it locked down. There is a root method for Verizon S7 and S7 edge but no TWRP or custom ROMs that I know of.
Verizon S7 / S7 Edge [Root Guide] SM-G930V SM-G935V [NO KNOX TRIP]
Hi, I am compiling this guide for rooting the verizon variant. I also hope to fill in some gaps in the other guides. I AM NOT RESPONSIBLE FOR ANY PROBLEMS YOU MAY CAUSE OR ENCOUNTER I did not develop this, I'm only telling you how to do it...
forum.xda-developers.com
Click to expand...
Click to collapse
Figured I'd give it the old college try. Got Odin to recognize the phone and went through the root process. All looked well until the very end. "Complete (write) operation failed."

Emmalfal said:
Figured I'd give it the old college try. Got Odin to recognize the phone and went through the root process. All looked well until the very end. "Complete (write) operation failed."
Click to expand...
Click to collapse
And now, using the latest version of Odin (I somehow downloaded an older one the first time around) it got to recovery.img and just stuck there. An exercise in frustration as you had warned. I need a Verizon phone that can 100 percent be rooted. I'm using a rooted original Pixel now but that sucker is getting worn out.

Emmalfal said:
Figured I'd give it the old college try. Got Odin to recognize the phone and went through the root process. All looked well until the very end. "Complete (write) operation failed."
Click to expand...
Click to collapse
It might depend on what version/build number of stock firmware is installed on the device. That guide might be for an older version of a specific version. If what you have is newer than what the guide was written for, that might be why it failed.
Does it say anything in the guide thread about it requiring a specific stock firmware or specific bootloader version?

Emmalfal said:
And now, using the latest version of Odin (I somehow downloaded an older one the first time around) it got to recovery.img and just stuck there. An exercise in frustration as you had warned. I need a Verizon phone that can 100 percent be rooted. I'm using a rooted original Pixel now but that sucker is getting worn out.
Click to expand...
Click to collapse
How about an unlocked device that can be used on Verizon's network?

Droidriven said:
It might depend on what version/build number of stock firmware is installed on the device. That guide might be for an older version of a specific version. If what you have is newer than what the guide was written for, that might be why it failed.
Does it say anything in the guide thread about it requiring a specific stock firmware or specific bootloader version?
Click to expand...
Click to collapse
I've gone through a couple different tutorials and they all seem to link to the same files that I need to download. It's been frustrating because looking for proper files for a phone this old leads to a lot of dead links. I'm probably going to give it up soon, but you know how it is. There's always "one more thing" to try. I tell you, I'm going to research like hell before I buy another phone. I need to know for sure that it can be rooted. In this case, I inherited my wife's old phone and a quick search revealed that it ought to be a piece of cake to root. There's always some little detail that trips me up. I appreciate your help with this.

Emmalfal said:
And now, using the latest version of Odin (I somehow downloaded an older one the first time around) it got to recovery.img and just stuck there. An exercise in frustration as you had warned. I need a Verizon phone that can 100 percent be rooted. I'm using a rooted original Pixel now but that sucker is getting worn out.
Click to expand...
Click to collapse
Try a version of Odin from around the same time the S7/S7 edge was released onto the market. Some versions work better with certain devices, as android evolved and as Odin gets updated to newer versions for newer devices, there are slight differences along the way that can effect how it works on older devices.
If the stock firmware that you are trying to flash is older than what was already installed on the device, it will probably fail due to not allowing the device to be degraded to an older version, it's a "security" measure put there to prevent you from installing a less "secure" operating system.

Droidriven said:
How about an unlocked device that can be used on Verizon's network?
Click to expand...
Click to collapse
Yeah, that would work. It's been so long since I messed around with this stuff -- I've had the pixel for six or seven years I think -- that I've forgotten everything I once knew.
Droidriven said:
Try a version of Odin from around the same time the S7/S7 edge was released onto the market. Some versions work better with certain devices, as android evolved and as Odin gets updated to newer versions for newer devices, there are slight differences along the way that can effect how it works on older devices.
If the stock firmware that you are trying to flash is older than what was already installed on the device, it will probably fail due to not allowing the device to be degraded to an older version, it's a "security" measure put there to prevent you from installing a less "secure" operating system.
Click to expand...
Click to collapse
I'll look that up and try it out. Nothing to lose at this point. All I'm trying to flash at this point is the CF Auto Root Tar.md5, as per the instructions.

Emmalfal said:
I've gone through a couple different tutorials and they all seem to link to the same files that I need to download. It's been frustrating because looking for proper files for a phone this old leads to a lot of dead links. I'm probably going to give it up soon, but you know how it is. There's always "one more thing" to try. I tell you, I'm going to research like hell before I buy another phone. I need to know for sure that it can be rooted. In this case, I inherited my wife's old phone and a quick search revealed that it ought to be a piece of cake to root. There's always some little detail that trips me up. I appreciate your help with this.
Click to expand...
Click to collapse
No, I mean does it say anything about it requiring a specific version of stock firmware or specific version of bootloader to be already installed on the device "before" you do the rooting process described in the guide?
Sometimes these kinds of things require your device to have a certain stock software version as a starting point before the device is modified. Most of the time, if the device is ever updated to a newer version, the specific exploit that was being used to root gets patched in the update, killing the effectiveness of the exploit used to root. From that point on, chances of rooting are nil.

Emmalfal said:
Yeah, that would work. It's been so long since I messed around with this stuff -- I've had the pixel for six or seven years I think -- that I've forgotten everything I once knew.
I'll look that up and try it out. Nothing to lose at this point. All I'm trying to flash at this point is the CF Auto Root Tar.md5, as per the instructions.
Click to expand...
Click to collapse
The vulnerability that CF autoroot takes advantage of may have been patched in newer versions of firmware.
I haven't been able to root any of my devices for last 4-5 years.

Droidriven said:
No, I mean does it say anything about it requiring a specific version of stock firmware or specific version of bootloader to be already installed on the device "before" you do the rooting process described in the guide?
Sometimes these kinds of things require your device to have a certain stock software version as a starting point before the device is modified. Most of the time, if the device is ever updated to a newer version, the specific exploit that was being used to root gets patched in the update, killing the effectiveness of the exploit used to root. From that point on, chances of rooting are nil.
Click to expand...
Click to collapse
Yeah, I've been careful to download files in keeping with my specific phone, not just the G930V but the longer version of that model number, which seems super specific. Nothing works. I've tried three or four different versions of Odin at this point, but they all either fail or get stuck somewhere in the process. Probably time to start searching for a new phone. I looked around for other ways to root this s7 but i'm not finding much. I rooted the PIxel with Magisk.

Emmalfal said:
Yeah, I've been careful to download files in keeping with my specific phone, not just the G930V but the longer version of that model number, which seems super specific. Nothing works. I've tried three or four different versions of Odin at this point, but they all either fail or get stuck somewhere in the process. Probably time to start searching for a new phone. I looked around for other ways to root this s7 but i'm not finding much. I rooted the PIxel with Magisk.
Click to expand...
Click to collapse
I'm not talking about model number version, I mean the specific build number of the firmware that is installed on the device. Some guides/methods only work on specific build numbers of stock firmware or only work if a specific version of bootloader is installed on the device.

Droidriven said:
I'm not talking about model number version, I mean the specific build number of the firmware that is installed on the device.
Click to expand...
Click to collapse
Ah. I'll check that.

Emmalfal said:
And now, using the latest version of Odin (I somehow downloaded an older one the first time around) it got to recovery.img and just stuck there. An exercise in frustration as you had warned. I need a Verizon phone that can 100 percent be rooted. I'm using a rooted original Pixel now but that sucker is getting worn out.
Click to expand...
Click to collapse
The S7 *can* be rooted, with lots of limitations afterwards. It just can't be BL unlocked

It could be failing due to the usb port or cable. I have an S8 that i can no longer flash only because I don't have a usb port in my pc old enough to flash it. I assume the S7 is the same way

Question Removing Retail Mode from S21+

Hi XDA, first time poster and I could not find a similar thread with the answers I was looking for, if that thread exists I apologize!
So basically I started a job in a retail phone shop a few months back. We have a drawer in store that has a bunch of old demo units in there that, once they have been removed from display, just sit there unused. There is phones in there from almost 10 years ago. They are never given back or requested back, nor are they logged in any way.
Well I noticed there was an almost perfect condition S21+ in there so I asked my manager if we could use it as a sales incentive and he replied saying the phones are useless because of the software on them. I said I was pretty sure you could remove the retail software and use it as a normal phone and he said if I can do that and get it working, I can take the phone for myself.
Well, I took it home and did some digging / experimenting. The phone has a proper IMEI already, you can put a SIM into the phone and it registers to the network. The problem is, the phone has security restrictions on data sharing and it does not have the playstore on it and there is no factory data reset option in the settings, nor in recovery mode.
I have tried flashing a stock firmware on using Odin which I thought worked, however when the phone restarts and you go through set up, Samsung Knox pops up and installs settings which forces the phone to set up in retail mode again with the same restrictions as previous (no play store, factory reset etc).
Any idea how to get around this issue? I would have thought flashing stock software would be the obvious work around but something on the phone forces it to install on retail mode every time.
Any advice on this is much appreciated.

Frostyb said:
Hi XDA, first time poster and I could not find a similar thread with the answers I was looking for, if that thread exists I apologize!
So basically I started a job in a retail phone shop a few months back. We have a drawer in store that has a bunch of old demo units in there that, once they have been removed from display, just sit there unused. There is phones in there from almost 10 years ago. They are never given back or requested back, nor are they logged in any way.
Well I noticed there was an almost perfect condition S21+ in there so I asked my manager if we could use it as a sales incentive and he replied saying the phones are useless because of the software on them. I said I was pretty sure you could remove the retail software and use it as a normal phone and he said if I can do that and get it working, I can take the phone for myself.
Well, I took it home and did some digging / experimenting. The phone has a proper IMEI already, you can put a SIM into the phone and it registers to the network. The problem is, the phone has security restrictions on data sharing and it does not have the playstore on it and there is no factory data reset option in the settings, nor in recovery mode.
I have tried flashing a stock firmware on using Odin which I thought worked, however when the phone restarts and you go through set up, Samsung Knox pops up and installs settings which forces the phone to set up in retail mode again with the same restrictions as previous (no play store, factory reset etc).
Any idea how to get around this issue? I would have thought flashing stock software would be the obvious work around but something on the phone forces it to install on retail mode every time.
Any advice on this is much appreciated.
Click to expand...
Click to collapse
Have you tried following the steps in a video such as this?
DO THIS COMPLETELY AT YOUR OWN RISK! I AM NOT RESPONSIBLE IF ANYTHING GOES WRONG, INCLUDING BUT NOT LIMITED TO BRICKING YOUR DEVICE, GETTING A VIRUS OR STARTING A LITERAL WAR.
Everything i was able find on the subject was kind of sketchy-looking (probably because doing this without permission would probably be illegal) so I included a warning.

BloodyFruitDestroyer said:
Have you tried following the steps in a video such as this?
DO THIS COMPLETELY AT YOUR OWN RISK! I AM NOT RESPONSIBLE IF ANYTHING GOES WRONG, INCLUDING BUT NOT LIMITED TO BRICKING YOUR DEVICE, GETTING A VIRUS OR STARTING A LITERAL WAR.
Everything i was able find on the subject was kind of sketchy-looking (probably because doing this without permission would probably be illegal) so I included a warning.
Click to expand...
Click to collapse
Thanks for the reply!
So I also came across this same video on the subject last night, it seems to be a workaround for bypassing Knox but I couldnt find any further info on what kind of state that leaves the phone in after, if it can still get official updates and such or if it triggered to eFuse that causes you to lose access to Samsung Pay and other official apps.
I'm aware this is at my own risk, the phone will sit in a drawer if I cant figure it out any way so no harm no foul as far as I can see. I've thought about rooting the device (I know this will trigger the eFuse) but I cant find any info on if that would get around the specific issue I'm having of Knox forcing the phone to install in retail settings or not so do not want to go down that road just yet.

Frostyb said:
Thanks for the reply!
So I also came across this same video on the subject last night, it seems to be a workaround for bypassing Knox but I couldnt find any further info on what kind of state that leaves the phone in after, if it can still get official updates and such or if it triggered to eFuse that causes you to lose access to Samsung Pay and other official apps.
I'm aware this is at my own risk, the phone will sit in a drawer if I cant figure it out any way so no harm no foul as far as I can see. I've thought about rooting the device (I know this will trigger the eFuse) but I cant find any info on if that would get around the specific issue I'm having of Knox forcing the phone to install in retail settings or not so do not want to go down that road just yet.
Click to expand...
Click to collapse
I'd say that the Knox workaround would probably (do not quote me on that) leave you with un-tripped Knox (=e-fuse intact) if it even still is. Even if Knox would be tripped, you would still most likely be able to get software updates. But because you said that you have already used Odin successfully on the device, that would lead me to believe that OEM unlocking might already be on in which case there probably isn't any more to lose by rooting the device. On a rooted device there are instructions o WikiHow on how to remove the Knox , but I haven't personally tested them. If I were you, I'd check with a Knox warranty checker app or through recovery mode, etc
whether the e-fuse is already triggered before continuing with anything.
And if I confused you, feel free to ask anything!

With the root approach you would also have to worry about passing Safety Net, but that'll only be relevant if you decide to go with that path.

BloodyFruitDestroyer said:
I'd say that the Knox workaround would probably (do not quote me on that) leave you with un-tripped Knox (=e-fuse intact) if it even still is. Even if Knox would be tripped, you would still most likely be able to get software updates. But because you said that you have already used Odin successfully on the device, that would lead me to believe that OEM unlocking might already be on in which case there probably isn't any more to lose by rooting the device. On a rooted device there are instructions o WikiHow on how to remove the Knox , but I haven't personally tested them. If I were you, I'd check with a Knox warranty checker app whether the e-fuse is already triggered before continuing with anything.
And if I confused you, feel free to ask anything!
Click to expand...
Click to collapse
Interesting, I may give the workaround a shot when I get home later then.
So I have used Odin but it was with official firmware obtained through Frija and, according to reading, that does NOT trip the eFuse. I did turn on OHD in dev options but from what I can tell, the fuse is only tripped when you load an unofficial image onto the device which I havent done yet. I can check when I get home by booting into recovery mode and checking the warranty line AFAIK it will say either 1 or 0 indicating if it's been tripped or not.
So my issue with rooting is I dont know if I root, will the phone still install in the retail setup that it does currently. I know I can run apps or code to remove Knox once rooted, but I dont know if then just reinstall firmware and it will be back to default like I want, or if I'll then need to figure out how to get the playstore loaded, if the security issues persist etc. Also as far as I can tell to root, I need to install Magisk on the device first to alter one of the image files, then move that file back to the PC to flash with Odin, and I'm not sure I can do that with the retail settings enabled.

Frostyb said:
Interesting, I may give the workaround a shot when I get home later then.
So I have used Odin but it was with official firmware obtained through Frija and, according to reading, that does NOT trip the eFuse. I did turn on OHD in dev options but from what I can tell, the fuse is only tripped when you load an unofficial image onto the device which I havent done yet. I can check when I get home by booting into recovery mode and checking the warranty line AFAIK it will say either 1 or 0 indicating if it's been tripped or not.
So my issue with rooting is I dont know if I root, will the phone still install in the retail setup that it does currently. I know I can run apps or code to remove Knox once rooted, but I dont know if then just reinstall firmware and it will be back to default like I want, or if I'll then need to figure out how to get the playstore loaded, if the security issues persist etc. Also as far as I can tell to root, I need to install Magisk on the device first to alter one of the image files, then move that file back to the PC to flash with Odin, and I'm not sure I can do that with the retail settings enabled.
Click to expand...
Click to collapse
I am interested in how this develops. Please keep me updated with the warranty byte status and whether the workaround is successful!

BloodyFruitDestroyer said:
I am interested in how this develops. Please keep me updated with the warranty byte status and whether the workaround is successful!
Click to expand...
Click to collapse
So quick update on this: none of the workaround videos on youtube seem to be capable of doing anything. They all rely on being able to connect to Wifi then get around the device before Knox settings apply, however on my build as SOON as you connect to wifi, it immediately starts applying knox settings and cannot be skipped.
I am wondering if this is because the version of software I flashed on using Odin was the most recent firmware, being android 12, and most of these workarounds are for android 11? Is it safe to locate the original firmware for the S21+ somewhere and flash that on to the device instead do you think?
Also the eFuse is still currently in tact.

Frostyb said:
So quick update on this: none of the workaround videos on youtube seem to be capable of doing anything. They all rely on being able to connect to Wifi then get around the device before Knox settings apply, however on my build as SOON as you connect to wifi, it immediately starts applying knox settings and cannot be skipped.
I am wondering if this is because the version of software I flashed on using Odin was the most recent firmware, being android 12, and most of these workarounds are for android 11? Is it safe to locate the original firmware for the S21+ somewhere and flash that on to the device instead do you think?
Also the eFuse is still currently in tact.
Click to expand...
Click to collapse
You could flash an older Android version, but if and only if it has the same bootloader version as the current one, otherwise it won't work and might even brick your device. I am unsure though if the downgrade would help but if the bootloader versions match, you can try!
On SamMobile.com you can see older versions of firmware. Just check the bootloader version before flashing!

BloodyFruitDestroyer said:
You could flash an older Android version, but if and only if it has the same bootloader version as the current one, otherwise it won't work and might even brick your device. I am unsure though if the downgrade would help but if the bootloader versions match, you can try!
On SamMobile.com you can see older versions of firmware. Just check the bootloader version before flashing!
Click to expand...
Click to collapse
So this may seem like a dumb question but how do I check to make sure the bootloader version matches?

Frostyb said:
So this may seem like a dumb question but how do I check to make sure the bootloader version matches?
Click to expand...
Click to collapse
It's most likely as simple as comparing the bootloader filenames between the Odin flashable files for the old and new software. I could verify whether that's the case if you send the filenames for both bootloader files here. (The file that goes into the BL slot in Odin)

BloodyFruitDestroyer said:
It's most likely as simple as comparing the bootloader filenames between the Odin flashable files for the old and new software. I could verify whether that's the case if you send the filenames for both bootloader files here. (The file that goes into the BL slot in Odin)
Click to expand...
Click to collapse
So the first image is of the current firmware that successfully flashed to my device via Odin.
The second is firmware from August 2021 that is on a build of Android 11. You can also see by the file modification dates.

What were your exact model and region again? Probably won't matter, please wait a minute

BloodyFruitDestroyer said:
What were your exact model and region again?
Click to expand...
Click to collapse
BloodyFruitDestroyer said:
What were your exact model and region again? Probably won't matter, please wait a minute
Click to expand...
Click to collapse
SM-G996B
Region is Ireland (CSC is MET)

Yeah, it seems like the current bootloader is version 4 while the Android 11 one is version 3 so these versions seem, unfortunately, incompatible.

Frostyb said:
SM-G996B
Region is Ireland (CSC is MET)
Click to expand...
Click to collapse
Hi there, I can help you out! I have some experience with Samsung.
So first off, I take it this is an Exynos model? Snapdragons require the use of a paid service to get an unlock.
It seems you've flashed stock firmware before but it didn't work out due to Knox. Did you flash all the files including the CSC (wipe all data) file? Also, you could try flashing TWRP and that would trip Knox, at which point Knox is disabled due to detecting system modifications or it will try to rollback your modifications.

So the only thing I personally can think of to get rid of the problem is going the TWRP route, but this will trip the Knox warranty byte to 0x1, so think about it. There might be someone more experienced than me that might be able to help without tripping Knox, but this is right now the only thing I can personally suggest to fix the problem.
Edit: It seems like someone more experienced appeared while I was writing this! Sweet!

BloodyFruitDestroyer said:
So the only thing I personally can think of to get rid of the problem is going the TWRP route, but this will trip the Knox warranty byte to 0x1, so think about it. There might be someone more experienced than me that might be able to help without tripping Knox, but this is right now the only thing I can personally suggest to fix the problem.
Frostyb said:
SM-G996B
Region is Ireland (CSC is MET)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Are you able to enable developer options? If so, you might be able to use ADB commands to disable the Retail Mode app. I doubt they're enabled though.

BloodyFruitDestroyer said:
Yeah, it seems like the current bootloader is version 4 while the Android 11 one is version 3 so these versions seem, unfortunately, incompatible.
Click to expand...
Click to collapse
Dammit, so it seems I'm stuck on Android 12 and there is no way to get back to a previous version then I take it?

Frostyb said:
Dammit, so it seems I'm stuck on Android 12 and there is no way to get back to a previous version then I take it?
Click to expand...
Click to collapse
With official firmware, I'd be pretty certain that you can't. By the way, please look at the latest messages as there is someone else with fresh ideas here, too.