I'm reviving an old VZW S5 that's rooted on 5.0. Can it be updated to 6.0 without losing root? Or, being greedy, 7.0?
If I need to wipe the phone, that's OK.
RBEmerson said:
I'm reviving an old VZW S5 that's rooted on 5.0. Can it be updated to 6.0 without losing root? Or, being greedy, 7.0? If I need to wipe the phone, that's OK.
Click to expand...
Click to collapse
Your best bet is to post this question within the following Q&A thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=2700073
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Ibuprophen said:
Your best bet is to post this question within the following Q&A thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=2700073
Good Luck!
[/...]
Click to expand...
Click to collapse
Thanks!
RBEmerson said:
Thanks!
Click to expand...
Click to collapse
Not a problem at all!
Just keep in mind that, even though the following area of the forum is specific to the Verizon GS5 (kltevzw)...
https://forum.xda-developers.com/verizon-galaxy-s5
... the following area of the forum is specific to the Galaxy S5 (klte...) variants because of the "Unified Developments" that also include the Verizon GS5 (kltevzw) device.
https://forum.xda-developers.com/galaxy-s5
Also (in case you may have wondered about it) the Verizon GS5 (kltevzw) device has the "Snapdragon" processor. Be sure NOT to use anything that falls under the "Exynos" category or similar.
I wish you the best of luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Quick question before I follow your suggested links - is there a quick way to determine what processor is in the phone? I distinctly remember the issue of the processors when rooting. AFAIK the only hardware info is G900V.05. When I booted into recovery with TI, no TWRP, etc., just the stock recovery screen.
RBEmerson said:
I'm reviving an old VZW S5 that's rooted on 5.0. Can it be updated to 6.0 without losing root? Or, being greedy, 7.0?
If I need to wipe the phone, that's OK.
Click to expand...
Click to collapse
1. It's impossible to update from 5.0 to 6.0 witout losing root. You will have to gain it again if possible.
2. Root is possible on 6.0 for G900V with Samsung EMMC chips.
3. You can check which chip your phone has with EMMC Brickbug Test app from the Market. Just run it and look at the first two figures in CID line on the info screen.
They will be 15 or 11.
15 - Samsung memory, root is possible on 6.0.
11 - Toshiba memory, root is impossible on 6.0.
For both variants root is possible on 5.0.
RBEmerson said:
Quick question before I follow your suggested links - is there a quick way to determine what processor is in the phone? I distinctly remember the issue of the processors when rooting. AFAIK the only hardware info is G900V.05. When I booted into recovery with TI, no TWRP, etc., just the stock recovery screen.
Click to expand...
Click to collapse
I had stated on the last statement that the G900V has a Snapdragon Processor.
I can't state that what your looking to do is possible since I've never performed this but, the threads i had provided are where you can, at least, get some additional member guidance.
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Ibuprophen said:
I had stated on the last statement that the G900V has a Snapdragon Processor.
I can't state that what your looking to do is possible since I've never performed this but, the threads i had provided are where you can, at least, get some additional member guidance.
Good Luck!
[/...]
Click to expand...
Click to collapse
I think bbsc pretty much nailed down the go-nogo for me. Thanks again, guys. Good on ya!
CID begins 15... woohoo!
RBEmerson said:
CID begins 15... woohoo!
Click to expand...
Click to collapse
Glad to see it makes you happy.
Now you have to look around and decide what ROM you want.
Should it be a stock ROM or something other?
There're several good guides on flashing and rooting in Verizon Galaxy S 5 General section.
A) where is a good place to continue this discussion? I don't want to be OT B) I've managed to screw myself into the ground and somehow lost the basic ability to load anything via Odin. The problem's in the phone. I somehow landed in what seems to be an engineering version of 4.4.2. Which would be annoying but OK IF... Power/Home/Vol Down brought me to push Vol Up letting Odin do the rest. Instead, all I get is "Power Reset or Unknown Upload Mode". The only way out is the same three buttons (Pwr is ignored). Booting up, I get a generic Samsung background, across the bottom, four Andy's with 15 on one, possibly numeric keypad on the next, app drawer, HW on the next Andy, and FAIL on the last (oh how so true!).
Apps on the screen include CPUStress, Waterproof, SEMI, Factory IME, RX_AGC_LE and MIC2 Echo.
Where am I? How do I get back normal uploading? Odin has utterly no idea about how to do anything useful with the phone, although it acknowledges it's there. Ditto for file explorer on Win10.
Oh yeah, and I have a black window filled with yellow info describing the phone, memory, cameras, etc. The first two lines might help (or not):
PDA: FA44_G900VVRU2APA1
Phone: G900VVRU2AOI1
The window doesn't appear to close, move, or go away. Attempts to open the app drawer are covered by a not totally opaque black foreground.
"Toto, I don't think we're in Kansas anymore."
The ugly wreckage:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
RBEmerson said:
Where am I? How do I get back normal uploading?
Click to expand...
Click to collapse
The ugly wreckage:
Click to expand...
Click to collapse
What do you want to achieve?
Just practice in flashing or something else?
bbsc said:
What do you want to achieve?
Just practice in flashing or something else?
Click to expand...
Click to collapse
I want to be back to a sane loader and 6.0.1. The instructions I followed clearly were brainless in recommending, after, G900VVRU2DQF2_G900VVZW2DQF2_G900VVRU2DQF2_HOME.tar.md5, using COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_2572656_REV00_user_mid_noship_MULTI_CERT.tar.md5. If I can flash the first file, I'll be back to 6.0.1 and then I can spend a lot more time planning rooting that.
As a side question, I assume that VZW's seriously locked code is still present on my S5, right?
RBEmerson said:
I want to be back to a sane loader and 6.0.1. The instructions I followed clearly were brainless in recommending, after, G900VVRU2DQF2_G900VVZW2DQF2_G900VVRU2DQF2_HOME.tar.md5, using COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_2572656_REV00_user_mid_noship_MULTI_CERT.tar.md5. If I can flash the first file, I'll be back to 6.0.1 and then I can spend a lot more time planning rooting that.
As a side question, I assume that VZW's seriously locked code is still present on my S5, right?
Click to expand...
Click to collapse
Yes, "VZW's seriously locked code" is there forever.
But we're trained to live with it at present time.
Try to take the battery off for 10-20 sec, insert it back and boot to Odin mode.
But don't flash anything more, just tell me if there is any success.
No change. BTW, there's some text in the UL corner:
Wait...
Done
UDC Start
And then a standing Andy with a little speech balloon and then "POWER RESET or UNKNOWN UPLOAD MODE" as before. IIRC there may have been an error code in the UL but that's not there. Maybe the battery pull changed that, maybe not. Meanwhile, I'm going to try some other button "gestures" to see if the produce something else. Probably not... "Insanity is doing the same thing over and over again and expecting different results." - - ≠ Einstein
The situation is definitely abnormal. This shouldn't happen.
A USB jig can help to get to Odin mode but I don't think you have one.
I'd try these variants:
1. Boot the phone into this abnormal boot mode, run Odin and connect the phone to the PC. Then press and hold Power, Vol- and Home till the phone reboots (more than 10 sec) and see if it reboots to Odin mode.
The second variant will be later.
No change. BTW, there's some text in the UL corner:
Wait...
Done
UDC Start
And then a standing Andy with a little speech balloon and then "POWER RESET or UNKNOWN UPLOAD MODE" as before. IIRC there may have been an error code in the UL but that's not there. Maybe the battery pull changed that, maybe not. Meanwhile, I'm going to try some other button "gestures" to see if the produce something else. Probably not... "Insanity is doing the same thing over and over again and expecting different results." - - ≠ Einstein
And this is about the only result:
Vol Up + Pwr
Ok, here's the second variant:
- Boot to system.
- Press "Andy" with black dialpad and dial *#9900#
- You should see a menu. Press "Debub Level ..." button and select High.
- Power off the phone and try to boot to Odin mode.
Related
I've been thinking about it for a while but decided to give it a try today . The step that tells me to hold up I get but then how so I power down to activate fastboot ?
Sent from my Atrix-4G, stock 2.3.4 (rooted)
DopeHack said:
I've been thinking about it for a while but decided to give it a try today . The step that tells me to hold up I get but then how so I power down to activate fastboot ?
Sent from my Atrix-4G, stock 2.3.4 (rooted)
Click to expand...
Click to collapse
hold volume down button while booting up, then hold volume up after fastboot is selected to activate it.
after that, you use fastboot commands on your computer.
But I was using the automatic unlocker . I still need to put in commands myself?
Sent from my Atrix-4G, stock 2.3.4 (rooted)
DopeHack said:
But I was using the automatic unlocker . I still need to put in commands myself?
Sent from my Atrix-4G, stock 2.3.4 (rooted)
Click to expand...
Click to collapse
Did you ask in that thread?
Sent from my MB860 using xda premium
DopeHack said:
But I was using the automatic unlocker . I still need to put in commands myself?
Click to expand...
Click to collapse
I believe the automatic unlocker will pause and should give clear instructions ask you to do specific things that have to be done by a human (power down and reboot into certain mode, etc), you just need to follow these instructions. After that, you just hit enter to continue.
If you are unable to follow these instructions, probably it's too much for you...
To reboot into fastboot, for example: press the power button, to turn off the phone; then hold the volume down button, press the power button again, you'll see "Fastboot", then release volume down, press volume up, you enter the "fastboot" mode
Too much for me lol I know how to get to all the menus that its telling me to go to but nothing else happens. the guide said nothing about typing in anything which is why I choose it. Especially since the automatic root worked easy as pie ...
Sent from my Atrix-4G, stock 2.3.4 (rooted)
You want help, laugh when people who are trying to help say it might be too much for you, yet you provide us close to absolute no information.
What guide are you following? We might know, but it still is your job to provide a link.
What is the step you are stuck at?
Why, what isn't going according to plan? What do you see happening in your sceen / phone?
If you can't explain properly, provide some screenshots.
You say you can get to all the menus it tells you to, yet in the first step you can't seem to get into fastboot. Your speech is unclear and what you want is hard to understand.
My opinion is you aren't ready to unlock your bootloader. You know very little about your phone or how it works. That's the community's fault really, with all these automatic scripts, which are really nice if you know what you're doing, but end up promoting easy ignorance in people like you.
I just hope in a month or two you are not one of those writing "OMG, please, I arrempted to downgrade by SBF and know my phone won't boot, what gives???"
Read up on some information a learn how these things work. It is the best you can do. Owning an android device and modding it can be great fun, but it does require some effort on your part. If I were you, I would learn how to unlock my bootloader with pudding, just to understand what is actuallly going on.
Either that, or you can learn how to ask for help properly and politely. Your choice.
Also, wrong section, This is not Q&A.
My girlfriend was rushing me so I tried to type up something quick but I used this
http://forum.xda-developers.com/showthread.php?t=1182871
As you can see like I can see it does not say I need to type anything in the cmd (which I have seen in YouTube videos and isn't that hard) but thought hey automatic sounds good so I gave it a try I don't have any problems getting the phone to fast boot or rsd as I've used the stock recovery to clear cache in an attempt to fix something. The part I'm stuck at is step 6
You are right I don't know alot about android which is why I didn't start messing with my phone the day I got it but I've been all over this site (well the atrix at least) and YouTube.
I appreciate any help and sorry for the misplaced thread
Sent from my Atrix-4G, stock 2.3.4 (rooted)
DopeHack said:
My girlfriend was rushing me so I tried to type up something quick but I used this
http://forum.xda-developers.com/showthread.php?t=1182871
Click to expand...
Click to collapse
this one is better
http://forum.xda-developers.com/showthread.php?t=1302423
doesnt give you the soft brick i think
So, let's see if I got this, you are having trouble at the part it says it should restart? Or before that? After you choose the number and press enter, what happens?
This could be a driver problem... If windows is not recognizing a device, it's common... Which windows are you using? I used to have some problems on XP and vista...
Newbleeto said:
So, let's see if I got this, you are having trouble at the part it says it should restart? Or before that? After you choose the number and press enter, what happens?
This could be a driver problem... If windows is not recognizing a device, it's common... Which windows are you using? I used to have some problems on XP and vista...
Click to expand...
Click to collapse
Right where it says it should restart and go into fastboot nothing happens I could hold that power button all day. I knew vista would bring an issue into the mix cause it never made the sound for connecting the phone but the SD cards show up
Sent from my Atrix-4G, stock 2.3.4 (rooted)
sanriver12 said:
this one is better
http://forum.xda-developers.com/showthread.php?t=1302423
doesnt give you the soft brick i think
Click to expand...
Click to collapse
This is the one I read before thanks hopefully my girlfriend will disappear for a hour or two (she doesn't want me to ruin my phone) so I can work on it .
so with this one I can use fauxs 1.3 or 1.45Ghz kernal with cm7 I've been craving that ice cream sandwich ..
Sent from my Atrix-4G, stock 2.3.4 (rooted)
Computer is down for a while seems like it wasn't meant to be but Im still going to get it done
Sent from my Atrix-4G, stock 2.3.4 (rooted)
I actually had to use a Vista system to get this to work.
Now, when the instructions say it should "Restart", at that point, have you been in "Fastboot" yet? Have you been to the part where you have to enter your "Unique ID"?
This is important to know because throughout the bootloader-unlocking process the phone should be restarted a couple of times. It sounds like you have at least gotten through the part where it flashes "Pudding" but it sounds like you haven't done the "fastboot" part yet.
Are you referring to "Step 6" in the actual post or within the script? If the power button does not work then just pull the battery. As long as it is not in the process of doing something you should be fine.
I also want to point out that the program you are using only requires that you type in your Unique ID, everything else is automated, not to mention the file contains everything you need including adb, fastboot, RSDlite, Superuser, Pudding, and a working recovery so it makes it very easy for the end user to not have to find everything on their own. The script unlocks the bootloader, roots your phone, and flashes CWM recovery.
Either way, please provide more details if you are still having issues. Good luck.
DopeHack said:
Right where it says it should restart and go into fastboot nothing happens I could hold that power button all day. I knew vista would bring an issue into the mix cause it never made the sound for connecting the phone but the SD cards show up
Sent from my Atrix-4G, stock 2.3.4 (rooted)
Click to expand...
Click to collapse
live4nyy said:
I actually had to use a Vista system to get this to work.
Now, when the instructions say it should "Restart", at that point, have you been in "Fastboot" yet? Have you been to the part where you have to enter your "Unique ID"?
This is important to know because throughout the bootloader-unlocking process the phone should be restarted a couple of times. It sounds like you have at least gotten through the part where it flashes "Pudding" but it sounds like you haven't done the "fastboot" part yet.
Are you referring to "Step 6" in the actual post or within the script? If the power button does not work then just pull the battery. As long as it is not in the process of doing something you should be fine.
I also want to point out that the program you are using only requires that you type in your Unique ID, everything else is automated, not to mention the file contains everything you need including adb, fastboot, RSDlite, Superuser, Pudding, and a working recovery so it makes it very easy for the end user to not have to find everything on their own. The script unlocks the bootloader, roots your phone, and flashes CWM recovery.
Either way, please provide more details if you are still having issues. Good luck.
Click to expand...
Click to collapse
I wasn't blaming vista I was just saying cause I've had problem with that is in the past.
I've basically done nothing haven't flashed or wiped my phone yet I was basically stuck at or around the first step cause it first asks for RSD protocol and then it says restart phone but the power button has no effect why in that mode nd when I pull the battery to manually put it in fast boot nothing happens nd I get some kind of batch error when it trays to get my unique id...
But got the computer back today so I'm gonna work on it again
Thanx for help ... will update you guys when I can
sanriver12 said:
this one is better
http://forum.xda-developers.com/showthread.php?t=1302423
doesnt give you the soft brick i think
Click to expand...
Click to collapse
Actually, I followed the method you linked (old netbook running XP) and got a softbrick on the automatic reboot after flashing pudding. I was so busy watching RSD Lite do its thing that I didn't catch that my phone had actually rebooted; it selected fastboot mode on its own so I was able to issue the unlock command. It took.
"7.Plug your device into your computer. RSD Lite should recognize your device and say “Model: NS Flash Olympus” and “Connected…” The acronym 'NS' may be different for your device people!!"
its not doing this(i have rsdlite 4.5.5 because i cant find 5.5)
edit: got on to next problem
Thanks everyone
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from Atrix 4G running CM7 ICS Final @ 1.2Ghz
If cpu not recognizing ur device in fastboot try restarting ur cpu. If u updated drivers u have to restart the cpu before it will see ur device.
Sent from my MB860 using xda premium
I have a Att galaxy s4 i337 and I'm running black box ROM I don't know what happen but every time I try to go into recovery it brings up a yellow icon and its says Att found unsupported soft wear. Can some please help me fix this issue I tried flashing the stock tar file in Odin but it won't pass.I need some serious help. Can some assist me!
That sounds more like download mode. There are a bunch of quick boot/recovery apps in the play store. Those would be easiest.
Sent from my TARDIS
0p3nsrc said:
That sounds more like download mode. There are a bunch of quick boot/recovery apps in the play store. Those would be easiest.
Sent from my TARDIS
Click to expand...
Click to collapse
But the thing is I can get into download mode but not my recovery
swaggsexy said:
But the thing is I can get into download mode but not my recovery
Click to expand...
Click to collapse
0p3nsrc actually answers this.
Two steps: #1. Download an app like Quickboot and then #2. start that app and use it to reboot either recovery or download mode (your choice). It should work.
I have had the same problem of the "unauthorized software" in the past and got around it by doing the manual process to get into recovery.
That is #1. turn off phone
#2. hold Volume up and keep holding it while pressing power button to start the phone
#3. Keep holding power+Volume UP button until you see the recovery indications (small print on top left part of screen).
#4. RElease the power button but DONT let go of the volume up button until you're actually in recovery. . .
you may have to try it a few times in a row to get it going, but it eventually WILL get you into recovery!
markbc01 said:
0p3nsrc actually answers this.
Two steps: #1. Download an app like Quickboot and then #2. start that app and use it to reboot either recovery or download mode (your choice). It should work.
I have had the same problem of the "unauthorized software" in the past and got around it by doing the manual process to get into recovery.
That is #1. turn off phone
#2. hold Volume up and keep holding it while pressing power button to start the phone
#3. Keep holding power+Volume UP button until you see the recovery indications (small print on top left part of screen).
#4. RElease the power button but DONT let go of the volume up button until you're actually in recovery. . .
you may have to try it a few times in a row to get it going, but it eventually WILL get you into recovery!
Click to expand...
Click to collapse
It won't work its saying. In Lil orange writting on top left kernel fail don't know what to do!
swaggsexy said:
I have a Att galaxy s4 i337 and I'm running black box ROM I don't know what happen but every time I try to go into recovery it brings up a yellow icon and its says Att found unsupported soft wear. Can some please help me fix this issue I tried flashing the stock tar file in Odin but it won't pass.I need some serious help. Can some assist me!
Click to expand...
Click to collapse
Hay "sexy" what base are you?
MDL or MF3
your profile lacks your phone and its base
Sent from my SAMSUNG-SGH-1337 using xda app-developers app
No matter which galaxy I had (s i9000, s2 i777, or my current s4), I've always has issues with the button combo for recovery. The safest/easiest had always been the quickboot app.
To the OP: black box ROM is ONLY meant for the international s4 (i9500). Major difference in hardware from the att s4 is the octocore processor. You are most likely getting kernel failure due to the ROM/kernel combo. Not 100% sure, though. Aside from kernel fail, any other parts to the error message? Post a screenshot of your "about device" under system settings > more..
For example, mine:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my TARDIS
that is what im getting is kernel fail on the top left hand corner
andriod system erased
if i accidentally erased my system on my phone how can i get tht back on a att galaxy s4
swaggsexy said:
if i accidentally erased my system on my phone how can i get tht back on a att galaxy s4
Click to expand...
Click to collapse
Explain.... How did you erase your system? Furthermore, are you talking about: your whole phone, the /system directory, or your internal sdcard? I've seen some people on the xda forums using 'system' a little too open-endedly.
If you mean /system, you're only option is flashing a ROM, unless you had a nandroid backup, in which case, depending on your recovery, you'd be able to do an advanced restore of the backup.
The same holds true if the whole phone has been wiped.
Sent from my TARDIS
swaggsexy said:
that is what im getting is kernel fail on the top left hand corner
Click to expand...
Click to collapse
swaggsexy said:
if i accidentally erased my system on my phone how can i get tht back on a att galaxy s4
Click to expand...
Click to collapse
swaggsexy said:
It won't work its saying. In Lil orange writting on top left kernel fail don't know what to do!
Click to expand...
Click to collapse
swaggsexy said:
But the thing is I can get into download mode but not my recovery
Click to expand...
Click to collapse
swaggsexy said:
I have a Att galaxy s4 i337 and I'm running black box ROM I don't know what happen but every time I try to go into recovery it brings up a yellow icon and its says Att found unsupported soft wear. Can some please help me fix this issue I tried flashing the stock tar file in Odin but it won't pass.I need some serious help. Can some assist me!
Click to expand...
Click to collapse
Since you can't get into recovery, based on what you've described, this means that you 1) flashed a recovery that was NOT loki'd 2) flashed a boot.img that was NOT loki'd.
This is most definitely something that can be fixed, depending on what Firmware your device is on.
If you know FOR A FACT that you have the MF3 bootloader, then I can walk you through how to use Heimdall to flash the phone back to an "out-of-the-box" state with MF3 firmware on it.
Is the Heiman method good to bring bacc to stock
jakew02 said:
Since you can't get into recovery, based on what you've described, this means that you 1) flashed a recovery that was NOT loki'd 2) flashed a boot.img that was NOT loki'd.
This is most definitely something that can be fixed, depending on what Firmware your device is on.
If you know FOR A FACT that you have the MF3 bootloader, then I can walk you through how to use Heimdall to flash the phone back to an "out-of-the-box" state with MF3 firmware on it.
Click to expand...
Click to collapse
If u can that would be appreciated. And the only thing I did was out a new room black box rom and root nothing going else done to the phone
swaggsexy said:
If u can that would be appreciated. And the only thing I did was out a new room black box rom and root nothing going else done to the phone
Click to expand...
Click to collapse
are you 100% positive that you were on MDL firmware? as in, you DID NOT take the OTA update for MF3? if you are on the wrong bootloader then this will brick your device.
honestly it's safer, you could just take it to BestBuy and tell them it "turned off during an update" or that you just want it reset
jakew02 said:
are you 100% positive that you were on MDL firmware? as in, you DID NOT take the OTA update for MF3? if you are on the wrong bootloader then this will brick your device.
honestly it's safer, you could just take it to BestBuy and tell them it "turned off during an update" or that you just want it reset
Click to expand...
Click to collapse
I fixed everything I just took of the Md5 off the tar file and put into Odin and it flashed just fine. Thanks for the input guys
swaggsexy said:
I fixed everything I just took of the MF3 or the tar file and put into Odin and it flashed just fine. Thanks for the input guys
Click to expand...
Click to collapse
awesome, sounds good.
as long as you have a bootloader from any firmware PRIOR to MF3, then you can just flash loki-doki as a precaution, otherwise you'll need to use SafeStrap, and I have not looked into that as I personally have no need to
I created a spot on my website for the stock Odin Tar's that I use for the P600.
I posted the US / XAR Region Stock Odin. I also posted the ML1 Asian base I used as well.
As I gather newer ones I will put them up and updated this thread.
Although this guide is written for the p600 it would, in theory work on any P60x device so long as you have the proper Odin files!
Note: This will not "untrip knox"!!!!!!!!
Here is the download page on my site:
MOD EDIT: Link removed as domain has expired. Thread closed until new links can be installed
Enjoy!
Currently Hosted:
P600UEUBMK1_P600XARBMK1_XAR (Shipped US ROM / XAR Region)
P600ZTUBML1_P600ZZTBML1_BRI (Asian Based ROM / BRI Region)
Other Odin Tar resources: Sammobile. Must be a member but they have tons of them.
How to Return to stock
This mini guide assumes the following...
You were able to root and or install a custom recovery or ROM therefore the drivers are installed on your PC for the tablet. So here we go...
Download Odin from the links in the OP
Extract the the .md5 file from the zip file you downloaded above.
Boot tablet into "Download" mode. You can do this by holding Power and Volume - (down) when the device is shut off. I note on this device it can be a little trickier so you may have to try a couple times. You should now see this on your tablet
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Connect Tablet to PC using known good USB Cable
Start Odin and Press the "AP" button to load the tar.md5 file. This may take a minute as it is also calculating the MD5 to ensure you have a good file. A bad file means bad issues and it wont let you flash it (good fail safe).
Once Odin sees the Tar and loads it completely AND Odin sees the tablet press the Start button to begin. Can takes about 5 to 10 minutes so be patient. Do NOT check or uncheck mark ANY other Options in Odin unless you know what you are doing!
Once it complete you will have a factory image on your tablet. Yay!
But we are not done. You may also want to, at this point, reboot to recovery and do a full data wipe. This method of Odin leaves the SD card and user data intact. To get into recovery hold Power and Volume + until you see the stock Android recovery. Select format Data, reboot. Boom, your tablet is like brand new!
Guided added!
I am not the best technical writer so if you need help understanding what I am saying dont hesitate to ask!
Bumped so people can find this...
Mods moved it so no one looking will actually see it...
scrosler said:
Bumped so people can find this...
Mods moved it so no one looking will actually see it...
Click to expand...
Click to collapse
I'm glad you bumped it. I still haven't tried to install any custom ROM in this tablet, but this post will sure come in handy soon!
Vexelius said:
I'm glad you bumped it. I still haven't tried to install any custom ROM in this tablet, but this post will sure come in handy soon!
Click to expand...
Click to collapse
Indeed!
What happens if I failed to root (according to TWRP) and am stuck in the Samsung splash screen? I was obviously able to install TWRP so hopefully that is enough for Odin to get me back to stock
Will this work?
kaneelias said:
What happens if I failed to root (according to TWRP) and am stuck in the Samsung splash screen? I was obviously able to install TWRP so hopefully that is enough for Odin to get me back to stock
Will this work?
Click to expand...
Click to collapse
If you can see samsung screen you can odin back to stock.
The directions I posted should hold true about getting to Odin / Download Mode
Thanks for this guide, I agree, it should definitely be in the development section.
Hello
So will I get the OTA updates after this? How do I untrip knox?
thanks
Thanks for this Scott and a great ROM!!!!
Sent from my SAMSUNG-SGH-I317 using Tapatalk
tahrang said:
Hello
So will I get the OTA updates after this? How do I untrip knox?
thanks
Click to expand...
Click to collapse
Yes, this is returning you to stock like when you turned it on for the very first time.
No one knows how to untrip knox.
Is it Knox that blocks the ota updates, or is it the rooting itself?
starfall42 said:
Is it Knox that blocks the ota updates, or is it the rooting itself?
Click to expand...
Click to collapse
Not sure. Never tried to Ota with KNOX.
Maybe ask in the Q/A forums.
Just to be safe, and If I do this the tablet will be as if it was completely new, right? I'm going to exchange it for another one and I want to be sure it's as new. Are there any flash counters or stuff like that I should be worried about?
Sent from my Nexus 5
So when a system update comes out we could use these directions to flash the stock rom with out loosing data, apps, settings, etc? Then be able to get the stock OTA?
Coming from the Nexus world, This is a bit different. Google seems to have no interest in the 10 inch sector though, so here we are.
Never have we had a tablet so heavily defended with so many issues. 6 tablets and this one stands out.
Via my Note 3
Tripping out?
scrosler said:
Note: This will not "untrip knox"!!!!!!!!
Click to expand...
Click to collapse
I think I understand what you are saying, but I'm new to Android, and would appreciate a sanity check::cyclops:
1. Knox "trips" (i.e. opens a fusible link in the hardware) if you root the tab and (or?) boot with a non-factory ROM. Once it trips, it cannot ever be "untripped", even if you return to a factory ROM image. (Hence the emphatic statement in the quote.)
2. Question: If a tablet is currently, and has always been, unrooted and stock, will using Odin and these instructions with a factory ROM trip knox? For example, to upgrade to the factory KitKat image
3. Follow-up question: If I flash KitKat as above, can I return to the original release by following your guide, again without tripping knox?
Thanks for the guide and software, and for your help.
iTelegraph said:
I think I understand what you are saying, but I'm new to Android, and would appreciate a sanity check::cyclops:
1. Knox "trips" (i.e. opens a fusible link in the hardware) if you root the tab and (or?) boot with a non-factory ROM. Once it trips, it cannot ever be "untripped", even if you return to a factory ROM image. (Hence the emphatic statement in the quote.)
2. Question: If a tablet is currently, and has always been, unrooted and stock, will using Odin and these instructions with a factory ROM trip knox? For example, to upgrade to the factory KitKat image
3. Follow-up question: If I flash KitKat as above, can I return to the original release by following your guide, again without tripping knox?
Thanks for the guide and software, and for your help.
Click to expand...
Click to collapse
1. As far as anyone knows, Knox cannot be untripped.
2. If you Odin a FACTORY IMAGE it WILL NOT trip Knox. Only custom roms/rooting trips AFAIK.
3. I'm not 100% sure as I haven't tried, but I think I've seen discussions where the bootloader wasn't changed so you could go back. Again, I'm not 100% sure. Maybe we could get clarification from someone who tried.
Sent from my SM-P600 using Tapatalk
Okay, so I've had this issue for a few months now where no matter what I tried, I could not update my Baseband. I tried everything I could think of - flashed the full stock Rom, used mobile ODIN, flashed twice, etc. but no matter what, the baseband would stick to the old one. I tried googling and looking around but the same tricks as above were posted again and again to no avail.
I eventually found the answer, it was a single post buried in a thread on here. As I keep seeing posts from other users with the same issue, I figured I'd write a quick guide so that hopefully those searching for the problem will find it.
So to reiterate - you've just updated to a new firmware (custom or otherwise) but your radio (aka baseband) has not changed. You then try to flash the radio directly but it still won't change. What gives?
Well to fix it, you're going to need the following:
Odin 3.07
Triangle Away (Thanks to Chainfire, as always)
A Method of rooting your device (I'm leaving this up to you as it's a warranty voiding experience and I presume you know how to do that by this point).
An official Samsung firmware containing the radio you want to update to
If you're currently on an AOSP based ROM, then I have bad news - you'll need to flash back to touchwiz to do this. Once you're done, you can flash back though.
Remember to make a backup of all your data, as you will be doing a lot of flashing here.
Note: You may be able to fix your stuck radio problem without flashing back to a completely stock firmware and cutting corners elsewhere, however I wanted this guide to be bulletproof, deviating slightly may produce different results. If all else fails, follow each step below exactly!
Remember: This guide is specifically for those of you who have tried other methods and are still stuck on an old baseband. If you're just looking how to flash your radio, there are easier and less involved methods that don't require any wiping - I strongly advise you to try those first.
Okay, by this point I'm going to assume you've done all your backups and are ready to start flashing.
Step 1: Reboot your phone into DOWNLOAD mode (aka Odin). To do this, hold down POWER, VOL-DOWN and HOME at the same time until you see the following screens:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Remember to let go of the above buttons and press "volume up" to continue.
Step 2: Open up Odin 3.07, click on the "PDA" button and select the stock firmware file you have downloaded (file should have a ".tar.md5" extension, if you downloaded a .zip file you'll need to extract it but DO NOT EXTRACT MORE THAN THIS, you want a single .tar.md5 file).
Step 3: With your phone connected to your PC running ODIN, click "start". This will take a few mins, so be patient.
Step 4: Root. Now your phone should be rebooting into some pretty awful stock Samsung firmware. Boo. However this is a necessary evil. Here you need to root your phone. CF-Auto-Root is my preferred method but this trips Knox so do what you feel is best.
Step 5: Install and run Triangle Away. Triangle Away requires a Stock samsung kernel, which is why you've just flashed a full Samsung firmware. Triangle away requires root, which is why you've just performed Step 4.
Step 6: Install the Stock Firmware. Again.
That's right, repeat steps 2 and 3 once more to flash that stock Samsung firmware all over again. Except this time, your system is reporting that it's "official" and TriangleAway has cleared some flags that were preventing the updated radio from installing. When your phone reboots, your radio should have updated.
You're done! From here, you can do whatever you like - flash another custom ROM (you're still rooted at this point), wipe and restore a backup you made earlier, switch to AOSP or whatever. Personally, I would go buy Chainfire a beer as TriangleAway is what makes this all possible.
Nice....it helped me :good:
Thanks :highfive:
neoKushan said:
Okay, so I've had this issue for a few months now where no matter what I tried, I could not update my Baseband. I tried everything I could think of - flashed the full stock Rom, used mobile ODIN, flashed twice, etc. but no matter what, the baseband would stick to the old one. I tried googling and looking around but the same tricks as above were posted again and again to no avail.
I eventually found the answer, it was a single post buried in a thread on here. As I keep seeing posts from other users with the same issue, I figured I'd write a quick guide so that hopefully those searching for the problem will find it.
So to reiterate - you've just updated to a new firmware (custom or otherwise) but your radio (aka baseband) has not changed. You then try to flash the radio directly but it still won't change. What gives?
Well to fix it, you're going to need the following:
Odin 3.07
Triangle Away (Thanks to Chainfire, as always)
A Method of rooting your device (I'm leaving this up to you as it's a warranty voiding experience and I presume you know how to do that by this point).
An official Samsung firmware containing the radio you want to update to
If you're currently on an AOSP based ROM, then I have bad news - you'll need to flash back to touchwiz to do this. Once you're done, you can flash back though.
Remember to make a backup of all your data, as you will be doing a lot of flashing here.
Note: You may be able to fix your stuck radio problem without flashing back to a completely stock firmware and cutting corners elsewhere, however I wanted this guide to be bulletproof, deviating slightly may produce different results. If all else fails, follow each step below exactly!
Okay, by this point I'm going to assume you've done all your backups and are ready to start flashing.
Step 1: Reboot your phone into DOWNLOAD mode (aka Odin). To do this, hold down POWER, VOL-DOWN and HOME at the same time until you see the following screens:
Remember to let go of the above buttons and press "volume up" to continue.
Step 2: Open up Odin 3.07, click on the "PDA" button and select the stock firmware file you have downloaded (file should have a ".tar.md5" extension, if you downloaded a .zip file you'll need to extract it but DO NOT EXTRACT MORE THAN THIS, you want a single .tar.md5 file).
Step 3: With your phone connected to your PC running ODIN, click "start". This will take a few mins, so be patient.
Step 4: Root. Now your phone should be rebooting into some pretty awful stock Samsung firmware. Boo. However this is a necessary evil. Here you need to root your phone. CF-Auto-Root is my preferred method but this trips Knox so do what you feel is best.
Step 5: Install and run Triangle Away. Triangle Away requires a Stock samsung kernel, which is why you've just flashed a full Samsung firmware. Triangle away requires root, which is why you've just performed Step 4.
Step 6: Install the Stock Firmware. Again.
That's right, repeat steps 2 and 3 once more to flash that stock Samsung firmware all over again. Except this time, your system is reporting that it's "official" and TriangleAway has cleared some flags that were preventing the updated radio from installing. When your phone reboots, your radio should have updated.
You're done! From here, you can do whatever you like - flash another custom ROM (you're still rooted at this point), wipe and restore a backup you made earlier, switch to AOSP or whatever. Personally, I would go buy Chainfire a beer as TriangleAway is what makes this all possible.
Click to expand...
Click to collapse
No need this,too complicated。
Only turn off the phone, then remove the battery ,
install it
and get into download model ,
Flash the radio.
that you can update the baseband
nforce4 said:
No need this,too complicated。
Only turn off the phone, then remove the battery ,
install it
and get into download model ,
Flash the radio.
that you can update the baseband
Click to expand...
Click to collapse
Thanks, but unfortunately that didn't work for me.
neoKushan said:
Thanks, but unfortunately that didn't work for me.
Click to expand...
Click to collapse
Turn off your phone manually. Leave it for 10 sec, dont need to remove battery, Put the modem on Phone, NOT PDA connect your phone and flash it. It is simple.
IzArsha said:
Turn off your phone manually. Leave it for 10 sec, dont need to remove battery, Put the modem on Phone, NOT PDA connect your phone and flash it. It is simple.
Click to expand...
Click to collapse
Believe me when I say that I tried that, I tried just about everything before it would finally stick. Removing battery, leaving it off for 10s+ (I did this numerous times as TriangleAway demands it due to the risk if bricking your phone and one time left it off/unplugged for a good 20mins to no avail). There was some kind of write protection in place, Mobile ODIN (yeah tried that as well) mentioned it when trying to flash the Radio - hence why TriangleAway is needed.
Before it got "Stuck", I had manually updated my Modem a few times without issue. I've had the Note 3 since launch and voided Knox within about 2 days of getting it - believe me, I've been there and done that
Nothing worked for me also until I tried this method...
Sent from my SM-N9005 using XDA Premium 4 mobile app
Here's what I don't like, and what I "Do" Like...
Like....
1) A post in the proper forum that seems to help a few people fix their issue when other methods didn't seem to work.
Dislike...
1) Somebody coming in touting their own method (which may or may not work for a particular user). This, believe it or not, only adds to confusion when a person looks for an answer. Now there are different methods in the same thread topic.
2) 2 pages of back and forth arguing as a result of the above ^^^
So, I'll delete all posts concerning this debate on procedures.
Folks, don't go poaching other users threads please. If they provide a solution that helps a few users, then that is GREAT!!! Not all normal solutions work for all users. Stick around long and you will discover this on your own one day.
Cleaned thread, please don't make me come back and do it again.
MD
Thanks Moscow. I apologise for what happened, I didn't mean to cause a fuss.
To show there's no hard feelings, I've updated the OP with a warning that this is specifically for those who are still stuck after trying out other methods. Hopefully that's enough to keep everyone happy.
neoKushan said:
Thanks Moscow. I apologise for what happened, I didn't mean to cause a fuss.
To show there's no hard feelings, I've updated the OP with a warning that this is specifically for those who are still stuck after trying out other methods. Hopefully that's enough to keep everyone happy.
Click to expand...
Click to collapse
Much better. I didn't mean to start an argument... But it happened somehow.
Good detailed guide however. See you around XDA.
I'm having Baseband: Unknown issue, and flashing different modems are not changing it.
Can this method help ?
thanks
MuhammadZeeshan7 said:
I'm having Baseband: Unknown issue, and flashing different modems are not changing it.
Can this method help ?
thanks
Click to expand...
Click to collapse
Hmm, I really don't know man. I've not seen that error before so I can't comment. Perhaps this can help?
neoKushan said:
Hmm, I really don't know man. I've not seen that error before so I can't comment. Perhaps this can help?
Click to expand...
Click to collapse
I've done almost every method, but not yours. BTW I don't have any other triangle icon except the yellow triangle at the start of Download mode.
MuhammadZeeshan7 said:
I'm having Baseband: Unknown issue, and flashing different modems are not changing it.
Can this method help ?
thanks
Click to expand...
Click to collapse
Unpack the tar file, and flash just the modem.bin into phone (not pda) in Odin.
not working on SM-N900w8
Didn't work on my note 3 sm-n900w8, modem still previous version :crying:
any other suggestion please?
jsecruzvalencia said:
Didn't work on my note 3 sm-n900w8, modem still previous version :crying:
any other suggestion please?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=53632129&postcount=1
In the first box.
EDIT 2022-06-30: FOUND A RELIABLE SOLUTION FOR MY NEW T307U TABLET! May work for other models! https://forum.xda-developers.com/t/...e-it-as-a-normal-tablet.4316969/post-87091297
Original post from 2021-08-09 below:
Following this thread to no avail: https://forum.xda-developers.com/t/doordash-knox-customized-tablet-unable-to-remove.3890522/
Setup requires an internet connection, at which point it sets up MobiControl:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My friend's an IT so he set up Meraki for me which I can enroll in instead of MobiControl, but a minute later this pops up:
I still have access to the settings but cannot enable USB Debugging.
I flashed a combination file which got me to the "factory binary" where I can unlock OEM and enable USB Debugging, but I don't know where to go from here:
I flashed a stock ROM, but that doesn't get rid of doordash and MobiControl during setup.
Please help!
Which Android version did you flash? Did you finally get rid of MobiControl?
XDA.Samsung said:
Which Android version didn't you flash? Did you finally get rid of MobiControl?
Click to expand...
Click to collapse
I solved this. Basically, I accidentally bricked the tablet, which I assume is what caused Samsung Knox to fail and thus Mobi Control didn't try installing on a fresh flash of Android 8.1. Fuller story below:
After 3 days straight of trying to reset the tablet, including flashing the combo file, trying anything I can think of, re-flashing the stock rom and seeing if the problem is gone, I finally fixed it.
What ended up happening was, while re-flashing the stock rom on my 4th attempt, I flashed the AP but not one of the other things (I guess CP?) which resulted in the tablet getting bricked.
Long story short, I held both volume buttons and power to boot into a blue download mode (as opposed to a black one via holding power down + volume and selecting download mode, since the volume down + power nor the volume up + power combos weren't working) and flashed the stock rom to it properly.
Upon setup, I was still required to set up wi-fi, but it didn't attempt to install mobicontrol! I've been using the tablet normally since. Who would have known accidentally bricking the tablet was all I needed to do!
genesisboy4 said:
I solved this. Basically, I accidentally bricked the tablet, which I assume is what caused Samsung Knox to fail and thus Mobi Control didn't try installing on a fresh flash of Android 8.1. Fuller story below:
After 3 days straight of trying to reset the tablet, including flashing the combo file, trying anything I can think of, re-flashing the stock rom and seeing if the problem is gone, I finally fixed it.
What ended up happening was, while re-flashing the stock rom on my 4th attempt, I flashed the AP but not one of the other things (I guess CP?) which resulted in the tablet getting bricked.
Long story short, I held both volume buttons and power to boot into a blue download mode (as opposed to a black one via holding power down + volume and selecting download mode, since the volume down + power nor the volume up + power combos weren't working) and flashed the stock rom to it properly.
Upon setup, I was still required to set up wi-fi, but it didn't attempt to install mobicontrol! I've been using the tablet normally since. Who would have known accidentally bricking the tablet was all I needed to do!
Click to expand...
Click to collapse
Good to know. Congratulation. Does it still show secured by knox on boot screen?
I had no luck. I can't flash anything, got error "MDM mode, can't download ".
XDA.Samsung said:
Good to know. Congratulation. Does it still show secured by knox on boot screen?
Click to expand...
Click to collapse
Yes, it does.
XDA.Samsung said:
I had no luck. I can't flash anything, got error "MDM mode, can't download ".
Click to expand...
Click to collapse
Make sure you're using the right version of odin for your tablet and you're flashing the right version of android.
genesisboy4 said:
Yes, it does.
Make sure you're using the right version of odin for your tablet and you're flashing the right version of android.
Click to expand...
Click to collapse
Which version of Odin did you use?
XDA.Samsung said:
Which version of Odin did you use?
Click to expand...
Click to collapse
Odin3_v3.13.3
genesisboy4 said:
Odin3_v3.13.3
Click to expand...
Click to collapse
After tried 5 versions of Odin, include 2 different v3.13.3, finally got a good news. I can flash T387v firmware Andriod 8.1 and 9. But the bad news is I cannot brick it, no matter flashed only AP or BL. I tried to flash with T387W or T387T firmware, I got PIT error messages.
Which version of firmware were you using?
XDA.Samsung said:
After tried 5 versions of Odin, include 2 different v3.13.3, finally got a good news. I can flash T387v firmware Andriod 8.1 and 9. But the bad news is I cannot brick it, no matter flashed only AP or BL. I tried to flash with T387W or T387T firmware, I got PIT error messages.
Which version of firmware were you using?
Click to expand...
Click to collapse
I think I installed android version SM-T387V_1_20200520121029_yelpqjg66y_fac.
genesisboy4 said:
I think I installed android version SM-T387V_1_20200520121029_yelpqjg66y_fac.
Click to expand...
Click to collapse
Thank you. It looks like it's Android 9. Did you update it to Android 10?
XDA.Samsung said:
Thank you. It looks like it's Android 9. Did you update it to Android 10?
Click to expand...
Click to collapse
It's Android 8.1. If that file I mentioned is 9, then it's not the one I flashed, but was instead on my to-do list of troubleshooting steps. I was going to try flashing Android 9 and 10 but I got it working with 8.1 so I'm keeping it on that. Plus, the newer the android, the more secure Samsung Knox will be, so it will be harder breaking it.
Any idea where you downloaded it from? I cant seem to find a link.
quiqsilverr said:
Any idea where you downloaded it from? I cant seem to find a link.
Click to expand...
Click to collapse
Android 10: https://samfrew.com/download/Galaxy__Tab__A__/1hjk/VZW/T387VVRU3CUI2/T387VVZW3CUI2/
"The fact that it has MobiControl installed suggests it's a company device, and is therefore administered by that company's IT department. It's probably going to be difficult to remove MobiControl unless you talk to that IT department about it."
The above is a quote I found regarding Knox and the MobiControl app. Which tells me that this thread, although likely unintentional, is violating XDA Forum Rule #9:
9. Don't get us into trouble.
Don't post copyrighted materials or do other things which will obviously lead to legal trouble. If you wouldn't do it on your own homepage, you probably shouldn't do it here either. This does not mean that we agree with everything that the software piracy lobby try to impose on us. It simply means that you cannot break any laws here, since we'll end up dealing with the legal hassle caused by you. Please use common sense: respect the forum, its users and those that write great code.
Click to expand...
Click to collapse
XDA does not wish to be held liable for circumventing device security regardless of intent of the user, which is why I'm closing this thread.
-Regards: Badger50