Related
Hello!
So I tried to root my Verizon SM-900V using Root De La Vega, but Odin gave me a failed message and my phone was uhh.. soft bricked? I ultimately did the whole PIT thing with Odin and have got it back working, but I'd still like to get root. I was wondering where I went wrong/what I can do to try and get root? Here is a quick overview of what I did
AP/CSC - The *#1234* dialer didn't work for me. So ultimately tried Kies, which just showed me MJE.
ROM - Only found one ROM on SamMobile for the MJE, which was: N900VVRUBMJE_N900VVZWMJE_VZW
URDLV.sh - Processed this file with Universal Root De La Vega 0.5.
Odin - Ran the URDLV output through the AP input on Odin 3.09, which processed this just fine
Flashed ROM - Used Odin to flash, and got a 'Failed' at the end of the flash! (and a non working phone
I then ran the PIT function of Odin on a new file: ALL_N900VVRUBMJE_N900VVZWMJE_2106277_REV03_user_low_ship_MULTI_CERT
which got my phone back to a working state.
What did I do wrong? I'm wondering why I PIT'd with a different file than I used initially. Can I use the PIT file for a 2nd attempt at De La Vega/Odin? Was the initial failure just random and should I try with the original file again? Or can I not root my phone with this method, and should just wait?
Thanks for your time and insights!
-Nick
albrnick said:
Hello!
So I tried to root my Verizon SM-900V using Root De La Vega, but Odin gave me a failed message and my phone was uhh.. soft bricked? I ultimately did the whole PIT thing with Odin and have got it back working, but I'd still like to get root. I was wondering where I went wrong/what I can do to try and get root? Here is a quick overview of what I did
AP/CSC - The *#1234* dialer didn't work for me. So ultimately tried Kies, which just showed me MJE.
ROM - Only found one ROM on SamMobile for the MJE, which was: N900VVRUBMJE_N900VVZWMJE_VZW
URDLV.sh - Processed this file with Universal Root De La Vega 0.5.
Odin - Ran the URDLV output through the AP input on Odin 3.09, which processed this just fine
Flashed ROM - Used Odin to flash, and got a 'Failed' at the end of the flash! (and a non working phone
I then ran the PIT function of Odin on a new file: ALL_N900VVRUBMJE_N900VVZWMJE_2106277_REV03_user_low_ship_MULTI_CERT
which got my phone back to a working state.
What did I do wrong? I'm wondering why I PIT'd with a different file than I used initially. Can I use the PIT file for a 2nd attempt at De La Vega/Odin? Was the initial failure just random and should I try with the original file again? Or can I not root my phone with this method, and should just wait?
Thanks for your time and insights!
-Nick
Click to expand...
Click to collapse
You'd be better off asking over here at the Verizon Note 3 sub-forum, as Verizon notes are different to the N9005 (which is what we mainly have here)
Oh! Will do! Thanks!
Hello!
So I tried to root my Verizon SM-900V using Root De La Vega, but Odin gave me a failed message and my phone was uhh.. soft bricked? I ultimately did the whole PIT thing with Odin and have got it back working, but I'd still like to get root. I was wondering where I went wrong/what I can do to try and get root? Here is a quick overview of what I did
AP/CSC - The *#1234* dialer didn't work for me. So ultimately tried Kies, which just showed me MJE.
ROM - Only found one ROM on SamMobile for the MJE, which was: N900VVRUBMJE_N900VVZWMJE_VZW
URDLV.sh - Processed this file with Universal Root De La Vega 0.5.
Odin - Ran the URDLV output through the AP input on Odin 3.09, which processed this just fine
Flashed ROM - Used Odin to flash, and got a 'Failed' at the end of the flash! (and a non working phone
I then ran the PIT function of Odin on a new file: ALL_N900VVRUBMJE_N900VVZWMJE_2106277_REV03_user_low_ship_MULTI_CERT
which got my phone back to a working state.
What did I do wrong? I'm wondering why I PIT'd with a different file than I used initially. Can I use the PIT file for a 2nd attempt at De La Vega/Odin? Was the initial failure just random and should I try with the original file again? Or can I not root my phone with this method, and should just wait?
Thanks for your time and insights!
-Nick
P.S. I'm trying to stay away from Kingo for the reasons it is banned here.
albrnick said:
Hello!
So I tried to root my Verizon SM-900V using Root De La Vega, but Odin gave me a failed message and my phone was uhh.. soft bricked? I ultimately did the whole PIT thing with Odin and have got it back working, but I'd still like to get root. I was wondering where I went wrong/what I can do to try and get root? Here is a quick overview of what I did
AP/CSC - The *#1234* dialer didn't work for me. So ultimately tried Kies, which just showed me MJE.
ROM - Only found one ROM on SamMobile for the MJE, which was: N900VVRUBMJE_N900VVZWMJE_VZW
URDLV.sh - Processed this file with Universal Root De La Vega 0.5.
Odin - Ran the URDLV output through the AP input on Odin 3.09, which processed this just fine
Flashed ROM - Used Odin to flash, and got a 'Failed' at the end of the flash! (and a non working phone
I then ran the PIT function of Odin on a new file: ALL_N900VVRUBMJE_N900VVZWMJE_2106277_REV03_user_low_ship_MULTI_CERT
which got my phone back to a working state.
What did I do wrong? I'm wondering why I PIT'd with a different file than I used initially. Can I use the PIT file for a 2nd attempt at De La Vega/Odin? Was the initial failure just random and should I try with the original file again? Or can I not root my phone with this method, and should just wait?
Thanks for your time and insights!
-Nick
P.S. I'm trying to stay away from Kingo for the reasons it is banned here.
Click to expand...
Click to collapse
Root de la vega doesnt work on the newer builds. Kingo is your best bet.
Root De La Vega only works properly for the MI9 firmware. If you are on either MJ7 OR MJE you have to use Kingo.
shiftr182 said:
Root de la vega doesnt work on the newer builds. Kingo is your best bet.
Click to expand...
Click to collapse
Is that the complete truth, or is it more accurate to say "it will work, but will trip the Knox flag on recent factory releases"?
I see that @designgears is still recently updating his thread over in the N3 International forum.
I understand that for some, tripping the Knox flag would be undesirable - but the OP ( @albrnick ) didn't make it clear whether or not that was a concern. The OP did say that he/she wanted to avoid Kingo.
.
bftb0 said:
Is that the complete truth, or is it more accurate to say "it will work, but will trip the Knox flag on recent factory releases"?
I see that @designgears is still recently updating his thread over in the N3 International forum.
I understand that for some, tripping the Knox flag would be undesirable - but the OP ( @albrnick ) didn't make it clear whether or not that was a concern. The OP did say that he/she wanted to avoid Kingo.
.
Click to expand...
Click to collapse
It's more correct to say the posted RDLV tar file for the N900V is a rooted MI9 build and you cannot flash back to prior firmware. Repackaging RDLV with MJ7 and/or MJE may work and may trip Knox - that is probably why no one has done it since tripping Knox is generally undesirable.
And Kingo works, and its pretty simple to use...
Sent from my SM-N900V using Tapatalk
use this http://forum.xda-developers.com/showthread.php?t=2543386
niklasio said:
use this http://forum.xda-developers.com/showthread.php?t=2543386
Click to expand...
Click to collapse
Thanks for all the responses guys! I ended up going the route above, after first factory resetting and using a dummy google account. I could use Kingo up front, since it was replaced later/when I would enter my real google account.
Thanks again!
-Nick
albrnick said:
Hello!
So I tried to root my Verizon SM-900V using Root De La Vega, but Odin gave me a failed message and my phone was uhh.. soft bricked? I ultimately did the whole PIT thing with Odin and have got it back working, but I'd still like to get root. I was wondering where I went wrong/what I can do to try and get root? Here is a quick overview of what I did
AP/CSC - The *#1234* dialer didn't work for me. So ultimately tried Kies, which just showed me MJE.
ROM - Only found one ROM on SamMobile for the MJE, which was: N900VVRUBMJE_N900VVZWMJE_VZW
URDLV.sh - Processed this file with Universal Root De La Vega 0.5.
Odin - Ran the URDLV output through the AP input on Odin 3.09, which processed this just fine
Flashed ROM - Used Odin to flash, and got a 'Failed' at the end of the flash! (and a non working phone
I then ran the PIT function of Odin on a new file: ALL_N900VVRUBMJE_N900VVZWMJE_2106277_REV03_user_low_ship_MULTI_CERT
which got my phone back to a working state.
What did I do wrong? I'm wondering why I PIT'd with a different file than I used initially. Can I use the PIT file for a 2nd attempt at De La Vega/Odin? Was the initial failure just random and should I try with the original file again? Or can I not root my phone with this method, and should just wait?
Thanks for your time and insights!
-Nick
P.S. I'm trying to stay away from Kingo for the reasons it is banned here.
Click to expand...
Click to collapse
Glad you got it all worked out!
az_biker said:
Glad you got it all worked out!
Click to expand...
Click to collapse
Oh, *Thank You* For That Amazing Post!! Made it so easy to do! :good:
albrnick said:
Oh, *Thank You* For That Amazing Post!! Made it so easy to do! :good:
Click to expand...
Click to collapse
That's the exact reason I created the step by step. Just helping other users out...
And if you didn't already, there's a button for that "thank you"
hey everyone figured id write up a quick little guide on rooting your s5 mini model SM-g800f on android 4.4.2
lets crack on and I hope it helps you out
this is my first guide so feedback is greatly appreciated
Things you are going to need
before you begin you will need a few things
1. Your device ( for this guide I am focusing on the sm-g800f in particular)
2. a USB cable and access to a pc
3. files from this site https://autoroot.chainfire.eu/ (credit to : chainfire)
4. Samsung USB drivers (i recommend Kies for this)
Device Prep
ok so you have all that you need lets crack on
firstly you will need to download the files from the link above and extract the folder to your desktop
now on your device you need to put it into download mode after plugging it in
to do this simply plug your device into the USB port on your PC and turn it off
then hold volume down , home and power.
if done right you will see a warning screen just press volume up to confirm you know what you are doing
The Root
once your device is connected and in download mode (see above) you are ready to roll
simply right click odin and run as administrator you should see the box in the top right of Odin is blue and say Com 0 connected or similar.
check the box next to pda and click the PDA button.
from here select the auto root file and click start
that's all there is to it
let it work its magic and when your device reboots it should say updating android if you haven't rooted before just relax this is normal and it is simply installing superuser to your device
Post rooting tips&apps
so you are rooted eh?
well done the hard part is over from here i personally always do the following
tap on superSU and you will be prompted to disable Knox security ( Knox limits what you can do once rooted disabling it makes your life easier)
i also usually install x posed and busy box as well as lucky patcher
if this is too much to read I've made a quick video guide too this is me doing the entire rooting process from start to end and worth a look of anything stumps you
https://www.youtube.com/watch?v=jcggfrq-WzE
Will I lose the warranty?
Yes
Gesendet von meinem SM-G800F mit Tapatalk
there is a new G800FXXU1AOG2
will the root work on it?
Yes it works on AOG2 too.
Is it possible to select invisible rooting? In some of the Cyanogemod OSs you can toggle between visible/invisible rooting.
Reason being if it's visibly rooted, then I am not allowed to use it on the corporate email service (detected by Airwatch).
Worked perfectly for me, thank you
WIll this work on the brand new 5.1.1 ?
this worked om my aog2, thanks for the post
What Android version did u have installed?
firmware upgrade encountered an issue. please select recovery mode in kies & try agai
firmware upgrade encountered an issue. please select recovery mode in kies & try again . j'ai eu ce message apres avoir fait par odin ,comment réparer cela , kies ne reconnais pas le s5 !
avez vous une soluce ,grand merci a vous :confus::confus:
S5 SMG800F
Morthawt said:
WIll this work on the brand new 5.1.1 ?
Click to expand...
Click to collapse
Same question here.
Stock rom. Not tried it with that new one
tonemgub1 said:
Same question here.
Click to expand...
Click to collapse
did you find out if this works on 5.1.1?
No, on the website https://autoroot.chainfire.eu/ only files for 4.4.2 are listed and I finally got my device rooted with the app Kingroot. In a different thread some user announced to write an instruction for 5.1.1 g800f bit still nothing has happened.
H!
have a g800fxxu1bpc3 on 5.11 Can i use root method form post no.1 with cf autoroot ?
Just tried it today on my stock 5.1.1 S5 mini (G800FXXU1BPC3) and it worked like a charm with the latest files from ChainFire.
Thanks a lot for the tutorial.
jimmay12345 said:
tap on superSU and you will be prompted to disable Knox security ( Knox limits what you can do once rooted disabling it makes your life easier)
Click to expand...
Click to collapse
Hi,
Nice guide. My G800F is now rooted. Thanks much!
However, when I go into SuperSU it doesn't prompt me about Knox. I wish I could disable it from there.
thanks!
man i have a g800f with 5.1.1 can i root it with that procedure or not?
Will it wipe my Samsung S5 mini when using this method? Or will it just root and everything continues to work as installed?
Please help me. I am not familiar with any of this until now. I have learned a lot but also, I DO NOT WANT TO "BRICK" my device. I am unsure as to how it all works. Please read!!!! I want to be precise! More Information the better, right?
Problem:
I purchased a used Samsung Tab4 8GB SM-T230NU from a 3rd party. I got it home, connected it to the WiFi network, when I did that the browser + GooglePlay did not open, it would say "No Internet Connection" so I thought there might have been something that would not let it connect so I HARD RESET(once). Turn it back on, frozen at the Samsung Tab4 Logo Screen. If I press up it takes me to another screen "Team Win Recovery Project V2.8.0.1" I have tried EVERY OPTION from reset to recovery to restoring back to the last saved back-up. I have done what I can do without having to try "rooting" - "roms" - "firmware"(this is where I am a noob BUT WILLING TO LEARN)
My actions-
I called Samsung and they want me to send it in but they wanted to charge me money just to have it looked at. Next move I went to BestBuy, met with a Samsung Representative, he said he'd do it for me but I would have to leave my tablet overnight(he didn't have his own computer) I didn't think that would have been wise on my part so I had him write me instructions as to what I could do. He wrote: 1. Download ODIN(done) 2. Download SM-T230 Stock Rom. (downloaded+extracted files: StockRoms-Series_T230(NU)+V1.6.3)
This is as far as I have gotten, please get back to me. Thank you for taking the time in reading this.
Well, the solution is easier than you think, download this file
https://www.androidfilehost.com/?fid=24572369242687230
Put it in a micro sd you have, put that micro sd in the tablet and then reboot in recovery mode (power + home + up volume) then when you see that special menu go to where it says "wipe" then "advanced wipe" and select all The options minus external sd (which is your microsd where you have the zip, which I left) then, you give back and you give install (depending on your version of twrp can say up or down select storage) you choose that option and you go To sd, you choose the zip that I left and you give swipe to install, wait for it to install and then you reboot and ready, it would have to work, the tablet should be revived
in spanish/en español
bien, la solucion es mas facil de lo que crees, descarga este archivo
https://www.androidfilehost.com/?fid=24572369242687230
ponlo en alguna micro sd que tengas, pon esa micro sd en la tablet y despues, reiniciar en recovery mode (power+home+ subir volumen) entonces cuando veas ese menu especial ve a donde dice "wipe" despues "advanced wipe" y selecciona todas las opciones menos external sd (que es tu microsd donde tienes el zip, que te dejé) despues, le das a retroceder y le das a install (dependiendo de tu version de twrp puede decir arriba o abajo seleccionar almacenamiento) eliges esa opcion y vas a la sd, eliges el zip que te dejé y le das a swipe to install, esperas a que installe y despues le das a reboot y listo, tendria que funcionar, la tablet deberia de revivir
Here the post of the rom, it is not necessary that you read it as such, but anyway it is my obligation to leave it
https://forum.xda-developers.com/tab-4/development/rom-stock-t230-nu-acheron-rom-v1-0-2015-t3000107
I have 32gb SD card in my phone , I have 4gb of it used, and 28gb free. Would it matter if I have other files on SD card before inserting into tab4 with file?
Juzzzinlbs said:
I have 32gb SD card in my phone , I have 4gb of it used, and 28gb free. Would it matter if I have other files on SD card before inserting into tab4 with file?
Click to expand...
Click to collapse
No, it does not matter at all, as long as you have the zip on the SD, everything will work perfectly, LUCK
jimmy999x said:
Here the post of the rom, it is not necessary that you read it as such, but anyway it is my obligation to leave it
https://forum.xda-developers.com/tab-4/development/rom-stock-t230-nu-acheron-rom-v1-0-2015-t3000107
Click to expand...
Click to collapse
Is that because that is their program? What's your obligation?
I have managed to upload photos to an Album called Tab4. If you could teach me further, much appreciated.
(Deleted my post)
keikari said:
(Deleted my post)
Click to expand...
Click to collapse
Why would you do that?
Juzzzinlbs said:
Why would you do that?
Click to expand...
Click to collapse
I read your first post a bit carelessly, i just wrote about that you should use odin. And there are lot of tutorials how to use it. So my post was kind of unnecessary.
Would you agree with the method that jimmy just explained?
keikari said:
I read your first post a bit carelessly, i just wrote about that you should use odin. And there are lot of tutorials how to use it. So my post was kind of unnecessary.
Click to expand...
Click to collapse
Odin is not necessary, it would imply downloading many more files than you need, it already has twrp installed, so the only thing you need to revive the tablet is a custom rom
jimmy999x said:
Odin is not necessary, it would imply downloading many more files than you need, it already has twrp installed, so the only thing you need to revive the tablet is a custom rom
Click to expand...
Click to collapse
Not always, I once had wifi problem with samsung galxay ace and it didn't got fixed with changin rom, but after flashing stock firmware with odin it started to work. Of course TWRP flash is much faster, but with odin you can be almost 100% sure that it's a hardware issue if it doesn't work.
keikari said:
Not always, I once had wifi problem with samsung galxay ace and it didn't got fixed with changin rom, but after flashing stock firmware with odin it started to work. Of course TWRP flash is much faster, but with odin you can be almost 100% sure that it's a hardware issue if it doesn't work.
Click to expand...
Click to collapse
Sure, but that would be the plan b, for now just need to go the easy way, if it does not work, then we will proceed to use odin
jimmy999x said:
Sure, but that would be the plan b, for now just need to go the easy way, if it does not work, then we will proceed to use odin
Click to expand...
Click to collapse
If it doesn't work, is there a chance of bricking it?
Juzzzinlbs said:
If it doesn't work, is there a chance of bricking it?
Click to expand...
Click to collapse
Do not worry, if it does not work, the only thing that will not solve is the wi fi problem, the zip is functional to your device, the odin method will solve any problem, even wi fi, but it is that more time it takes, Try first with my method, if it does not work, we use odin
Okay so I did the steps you said, and it's not as easy as you put it.... Does anything like "SuperSU" mean anything?
Juzzzinlbs said:
Okay so I did the steps you said, and it's not as easy as you put it.... Does anything like "SuperSU" mean anything?
Click to expand...
Click to collapse
SuperSu is flashable .zip file which you flash in TWRP to get root access and root acceess is kind of similiar as being an administrator in windows(allows to do more stuff). I hope i understood your question correctly.
Yes. But when I go to do the wipe, it says wipe failed and in the terminal command screen it stops when it tries to update the partition details....
Juzzzinlbs said:
Yes. But when I go to do the wipe, it says wipe failed and in the terminal command screen it stops when it tries to update the partition details....
Click to expand...
Click to collapse
Thats weird. Well now you can try to install rom without wiping or do odin method.
keikari said:
Thats weird. Well now you can try to install rom without wiping or do odin method.
Click to expand...
Click to collapse
Could I possibly try adding the SuperSU root file?
Keep in mind it's still saying there is no OS installed
so i bought this Tab E (SM-T377V) off a site , and it was owned by a resturant that no longer used the service Doordash. it was locked down with FRP lock when i first got it i was able to by pass the FRP and i can flash any ROM to it now but it always loads the KNOX customization no matter what ROM i try and load .. now in 5.1.1 i can get root but when i try and remove the KNOX it freezes and wont boot. right now i can let knox load and use it normally for the most part just has the doordash logo wallpaper which is set with the KNOX. i would like to try and get rid of this KNOX customization , i assume there is a hidden partition or something like that makes it point too the KNOX loading no matter what i flash it with? in ODIN i've tried to do the erase nand and everything else i can but still no luck any help or advise would be useful, on another note i have the COMBONATION FILE ROM and when i load that i don't get the KNOX thing but its just alot of testing stuff is there anyway i can use that to remove this KNOX??? again any advise or pointers would be helpful. right now like i said i got it usable as a tablet just with annoying with the doordash customizations ..
Any luck?
cernorama said:
so i bought this Tab E (SM-T377V) off a site , and it was owned by a resturant that no longer used the service Doordash. it was locked down with FRP lock when i first got it i was able to by pass the FRP and i can flash any ROM to it now but it always loads the KNOX customization no matter what ROM i try and load .. now in 5.1.1 i can get root but when i try and remove the KNOX it freezes and wont boot. right now i can let knox load and use it normally for the most part just has the doordash logo wallpaper which is set with the KNOX. i would like to try and get rid of this KNOX customization , i assume there is a hidden partition or something like that makes it point too the KNOX loading no matter what i flash it with? in ODIN i've tried to do the erase nand and everything else i can but still no luck any help or advise would be useful, on another note i have the COMBONATION FILE ROM and when i load that i don't get the KNOX thing but its just alot of testing stuff is there anyway i can use that to remove this KNOX??? again any advise or pointers would be helpful. right now like i said i got it usable as a tablet just with annoying with the doordash customizations ..
Click to expand...
Click to collapse
Just factory reset with twrp and format the data partition.
Ensure oem unlock is enabled first.
cernorama said:
so i bought this Tab E (SM-T377V) off a site , and it was owned by a resturant that no longer used the service Doordash. it was locked down with FRP lock when i first got it i was able to by pass the FRP and i can flash any ROM to it now but it always loads the KNOX customization no matter what ROM i try and load .. now in 5.1.1 i can get root but when i try and remove the KNOX it freezes and wont boot. right now i can let knox load and use it normally for the most part just has the doordash logo wallpaper which is set with the KNOX. i would like to try and get rid of this KNOX customization , i assume there is a hidden partition or something like that makes it point too the KNOX loading no matter what i flash it with? in ODIN i've tried to do the erase nand and everything else i can but still no luck any help or advise would be useful, on another note i have the COMBONATION FILE ROM and when i load that i don't get the KNOX thing but its just alot of testing stuff is there anyway i can use that to remove this KNOX??? again any advise or pointers would be helpful. right now like i said i got it usable as a tablet just with annoying with the doordash customizations ..
Click to expand...
Click to collapse
Hola gracias a Google Translate eh podido entender tu pregunta.
Veras, yo tengo el mismo problema,.
Ya casi tengo lista la tablet, pero aun no puedo activar la WiFi del dispositivo.
Yo usé la Samsung tools + Hack file.
Ya puedo usar la tablet pero no me permite navegar por internet porque el WiFi esta bloqueado
Si tienes alguna idea me la comparte y yo te doy lo que tengo de investigacion.
Saludos
IDK if you figured this one out but here is how I did it:
>Extract PIT file from the BL tar.md5 of your stock firmware
>Nand erase all with Odin 3.07 with autoreboot UNCHECKED
>Set PIT file and check repartition, reboot download mode
>Flash stock firmware
If anyone needs links PM me. I have a Sammobile account.
hi just flash this combination and activ usb debug and oem unlock make hard reset
COMBINATION_VZW_FA51_T377VVRU1AQD1_VZWFAC_CL6507601_QB13278124_REV00_user_mid_noship
flash this rom ALL_VZW_T377VVRU1AOL7_T377VVZW1AOL7_5.1.1_USA
thats all
Lol just go to safe mode and then put the wrong password in 30 times
help!
Having trouble doing this. Would you be able to help me with the process? Got a practically new tablet preloaded with Doordash. Thank-you!
2 more tablets , reset and cleared
i got 2 more doordash tablets SM-T377v , i was able to odin flash the combonation file .. unlock oem and usb debugger in developers options, and then flash the latest 7.1 rom , both work like a charm now , from what i have read the OEM unlock disables the KNOX .
Where can I find this combination file?
HI, im having a very similar issue with my device i just got. Its a tab e (SM-T567V) i tried flashing a new rom and every time it connects to wifi Knox pops up and locks it out. What rom and steps should i be using to fix this? I have the ability to oem unlock and USB debug it. Thanks any info would be greatly appreciated
I have same tablet and same issue. How did you get it reset? Where can I find that combination file?
MarXilla said:
IDK if you figured this one out but here is how I did it:
>Extract PIT file from the BL tar.md5 of your stock firmware
>Nand erase all with Odin 3.07 with autoreboot UNCHECKED
>Set PIT file and check repartition, reboot download mode
>Flash stock firmware
If anyone needs links PM me. I have a Sammobile account.
Click to expand...
Click to collapse
Hey can I please get those links? I'm ready to conquer this damn thing... Lol
cernorama said:
2 more tablets , reset and cleared
i got 2 more doordash tablets SM-T377v , i was able to odin flash the combonation file .. unlock oem and usb debugger in developers options, and then flash the latest 7.1 rom , both work like a charm now , from what i have read the OEM unlock disables the KNOX .
Click to expand...
Click to collapse
Can you please tell me where that combination file is? And also how to own unlock...it's not in the settings
I am also having same issue with t387V, I was able to flash combination file and oem unlock; however when I flash the stock firmware with ODIN, the MDM (mobicontrol) is still present.
For above, you can try to find combination file here https://firmwarex.net/?s=t377v
neozengar said:
I am also having same issue with t387V, I was able to flash combination file and oem unlock; however when I flash the stock firmware with ODIN, the MDM (mobicontrol) is still present.
For above, you can try to find combination file here https://firmwarex.net/?s=t377v
Click to expand...
Click to collapse
I have the Samsung SM-T387v as well. Did you ever figure a fix for this?
8wrlobo said:
Lol just go to safe mode and then put the wrong password in 30 times
Click to expand...
Click to collapse
Unfortunately, that didn't work
MarXilla said:
IDK if you figured this one out but here is how I did it:
>Extract PIT file from the BL tar.md5 of your stock firmware
>Nand erase all with Odin 3.07 with autoreboot UNCHECKED
>Set PIT file and check repartition, reboot download mode
>Flash stock firmware
If anyone needs links PM me. I have a Sammobile account.
Click to expand...
Click to collapse
Hi, I'm having the same issue. Samsung Galaxy Tab A, SM-T387v.
I have no idea how to do what you just said. Can you or someone please explain so that I may perform the necessary actions to fix my tablet?
I have the T-378V also. You can get access to developer mode by interrupting Soti Mobicontrol during initial setup. You can do this by restarting in safe mode as soon as device setup has started following setting up your work device. Now, there are comments regarding several methods of proceeding: 1)Try to Nand erase all, flash pit from combo file ? and then flash stock fw? 2) Wait out the 7 days with sim inserted, wifi on and, in safe mode to unlock oem? What step proceeds at that point abd twrp? 3)There is a method involved of encrypting the device and incorrectly entering the password to factory reset, however without having encryption and oem unlock enabled this option hasn’t worked for me. 4) One of the fw I flashed with odin made an unlock symbol show up at the bottom of the android/samsung boot up logo I don’t know what the significance was or how to proceed.
If anyone figures something out please share it here.
MarXilla said:
IDK if you figured this one out but here is how I did it:
>Extract PIT file from the BL tar.md5 of your stock firmware
>Nand erase all with Odin 3.07 with autoreboot UNCHECKED
>Set PIT file and check repartition, reboot download mode
>Flash stock firmware
If anyone needs links PM me. I have a Sammobile account.
Click to expand...
Click to collapse
It didn't work for me.