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
Related
Hi guys,
I'm having trouble getting into CWM recovery. When I try to boot into if from Rom Manager it gives me an error that says, "System software not authorized by verizon wireless". After filling my pants I figured out how to get past that and boot up my phone, but I don't know what to do from here. Any thoughts?
I'm running stock 4.4.2 Rooted
Thanks!
Retail devices can only use safestrap. Developer editions can use custom recoveries. Sounds like youre on a retail device.
waxcatharsis said:
Hi guys,
I'm having trouble getting into CWM recovery. When I try to boot into if from Rom Manager it gives me an error that says, "System software not authorized by verizon wireless". After filling my pants I figured out how to get past that and boot up my phone, but I don't know what to do from here. Any thoughts?
I'm running stock 4.4.2 Rooted
Thanks!
Click to expand...
Click to collapse
bmwh0r3 said:
Retail devices can only use safestrap. Developer editions can use custom recoveries. Sounds like youre on a retail device.
Click to expand...
Click to collapse
Like my buddy @bmwh0r3 stated, sounds like you're on a Retail device.
Check out this thread by @az_biker that walks you through all the things you need to know.
Shaggy Kobain said:
Like my buddy @bmwh0r3 stated, sounds like you're on a Retail device.
Check out this thread by @az_biker that walks you through all the things you need to know.
Click to expand...
Click to collapse
Yes I have a retail version rooted using the towelroot method. So I can just install Safestrap and move on from there?
waxcatharsis said:
Yes I have a retail version rooted using the towelroot method. So I can just install Safestrap and move on from there?
Click to expand...
Click to collapse
Correct. Make sure you grab SafeStrap 3.75B04 and you will be good to go :good:
Shaggy Kobain said:
Correct. Make sure you grab SafeStrap 3.75B04 and you will be good to go :good:
Click to expand...
Click to collapse
Great, I'll try that! Thanks guys!
Success! Only thing is I still need to do the workaround to boot up my phone(hold down home, volume down and power). Once I do that I'm able to boot into recovery or system. Do I need to remove CWM through some further process or is something else causing that?
I would start over. Odin the stock tar and pit files. Root again and follow the instructions in the safestrap thread. Be re device you can only use the touchwiz roms
{
"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"
}
bmwh0r3 said:
I would start over. Odin the stock tar and pit files. Root again and follow the instructions in the safestrap thread. Be re device you can only use the touchwiz roms
Click to expand...
Click to collapse
I was afraid of that...
bmwh0r3 said:
I would start over. Odin the stock tar and pit files. Root again and follow the instructions in the safestrap thread. Be re device you can only use the touchwiz roms
Click to expand...
Click to collapse
100% agree. Nothing like taking the chance that all is ok, just to get everything set up, issues show their ugly heads, and you end up starting from scratch anyway.
At this point, you're basically at square one, just do it right and save a ton of headaches down the road
az_biker said:
100% agree. Nothing like taking the chance that all is ok, just to get everything set up, issues show their ugly heads, and you end up starting from scratch anyway.
At this point, you're basically at square one, just do it right and save a ton of headaches down the road
Click to expand...
Click to collapse
As I mentioned earlier, I used the towelroot method to get root originally. Can you point me towards a thread that has the most current method to gain root on the Note 3?
waxcatharsis said:
As I mentioned earlier, I used the towelroot method to get root originally. Can you point me towards a thread that has the most current method to gain root on the Note 3?
Click to expand...
Click to collapse
If you're on NC4, towelroot is the most current.
thegamerdarkseid said:
If you're on NC4, towelroot is the most current.
Click to expand...
Click to collapse
Great, so to be clear you recommend unrooting and rooting again?
waxcatharsis said:
Great, so to be clear you recommend unrooting and rooting again?
Click to expand...
Click to collapse
Are you already rooted? Explain fully, are you still trying to use clockwork mod or have you gotten rid of that and trying safestrap?
thegamerdarkseid said:
Are you already rooted? Explain fully, are you still trying to use clockwork mod or have you gotten rid of that and trying safestrap?
Click to expand...
Click to collapse
I have root and safestrap now. I didn't remove CWM I just installed safestrap. It works fine but I am getting an error message that says "system software not authorized" on boot that I have to bypass by pressing volume down, home and power at the same time. It's really a minor inconvenience so I'm not too worried about it but if there's a simple fix I'd like to do that.
waxcatharsis said:
I have root and safestrap now. I didn't remove CWM I just installed safestrap. It works fine but I am getting an error message that says "system software not authorized" on boot that I have to bypass by pressing volume down, home and power at the same time. It's really a minor inconvenience so I'm not too worried about it but if there's a simple fix I'd like to do that.
Click to expand...
Click to collapse
You really may not want to but it'll be best to start over as there's no telling what kind of problems having clockwork mod on a phone with a locked bootloader might bring down the line. Things may seem okay now with a minor inconvenience but you just never know.
thegamerdarkseid said:
You really may not want to but it'll be best to start over as there's no telling what kind of problems having clockwork mod on a phone with a locked bootloader might bring down the line. Things may seem okay now with a minor inconvenience but you just never know.
Click to expand...
Click to collapse
Alright. I can wipe my phone from safestrap but do you know if that will get rid of CWM also?
waxcatharsis said:
Alright. I can wipe my phone from safestrap but do you know if that will get rid of CWM also?
Click to expand...
Click to collapse
You SHOULD be able to perform a FACTORY RESET / WIPE from Android download, that will return your phone to OEM, unrooted (should remove CWM) and all your peronal files.
Then start the process from scratch, the NC4 Root link in my sig has links to the files you need to get back up and running.
This will give you peace of mind that no 'unknowns' are hanging around waiting to surface...
az_biker said:
You SHOULD be able to perform a FACTORY RESET / WIPE from Android download, that will return your phone to OEM, unrooted (should remove CWM) and all your peronal files.
Then start the process from scratch, the NC4 Root link in my sig has links to the files you need to get back up and running.
This will give you peace of mind that no 'unknowns' are hanging around waiting to surface...
Click to expand...
Click to collapse
Thanks Biker, I was at a function last night and couldn't get back to him.
Here you go.
https://www.dropbox.com/s/9mqfr656nugnzvp/OF5baseband.tar?dl=0
Steps:
-Power down phone completely.
-Boot into download mode (vol+down,power,home)
-Uncheck 'auto reboot' in Odin & flash.
-Remove battery, wait 5 sec, re-insert battery and boot into download mode.
-Re-check 'auto reboot' in Odin & flash.
Done
freeza said:
Here you go.
https://www.dropbox.com/s/9mqfr656nugnzvp/OF5baseband.tar?dl=0
Steps:
-Power down phone completely.
-Boot into download mode (vol+down,power,home)
-Uncheck 'auto reboot' in Odin & flash.
-Remove battery, wait 5 sec, re-insert battery and boot into download mode.
-Re-check 'auto reboot' in Odin & flash.
Done
Click to expand...
Click to collapse
Thanks freeza!
OK dumb question... If I Odin the baseband, will I be OK or I have to Odin the tar to update bootloader and firmware.. trying the shortcut if I can.?...I know when I was with tmobile note 2 i can do with baseband. Don't know if the same with CDMA. Tia
Sorry for the noob question here but is this similar to flashing a modem to possibly get better reception? I've done that before and no issues. I'm using Notarzed Stable 2 ROM (OB7) and don't want to screw anything up.
Yes it may make it unusable
@BB said:
Sorry for the noob question here but is this similar to flashing a modem to possibly get better reception? I've done that before and no issues. I'm using Notarzed Stable 2 ROM (OB7) and don't want to screw anything up.
Click to expand...
Click to collapse
Based on the file size, I think this is the of5 bootlader/firmware and modem not just the modem. A modem only tar shouldn't cause any issues. Ive also done that before. I could be wrong tho.
arrogant437 said:
Based on the file size, I think this is the of5 bootlader/firmware and modem not just the modem. A modem only tar shouldn't cause any issues. Ive also done that before. I could be wrong tho.
Click to expand...
Click to collapse
Nah, it's just the baseband (modem and apnhlos)
freeza said:
Nah, it's just the baseband (modem and apnhlos)
Click to expand...
Click to collapse
Cool...going to Odin this puppy over my noterized2 then. Thanks
---------- Post added at 09:35 PM ---------- Previous post was at 08:57 PM ----------
Of5 modem successfully odin'd over noterized2
{
"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"
}
Can you use mobile odin or flashify to flash this on vacation in Orlando and i really want to try this service sucks down here
Sent from my SM-N910P using Tapatalk
tanderson164 said:
Can you use mobile odin or flashify to flash this on vacation in Orlando and i really want to try this service sucks down here
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Got your MSL? Band priority set to 41, 26, 25? Did you do the PRL and Profile updates? Got my MSL directly from Sprint for... you guessed it; slow data.
I was Orlando twice this past Spring and data was great just about everywhere I went. Disney World even has complimentary Wi-Fi which I didn't use for days until I realized it worked in some indoor areas where Sprint was weak or dead. I had LTE at the resort, indoors.
Disneyland in Anaheim, CA? Not so good there but I've got LTE at the resort that's faster than AT&T and TWC Wi-Fi.
I'm on OB7 modem. Can't recall who but I've been told Mobile Odin isn't compatible with Note 4 when I asked about it.
Sent from my SM-N910P using Tapatalk
I have tried to get my msl from sprint twice i guess I will have to keep trying because right now I feel like I am using my HTC evo it takes forever to load maps or anything
Sent from my SM-N910P using Tapatalk
freeza said:
Here you go.
https://www.dropbox.com/s/9mqfr656nugnzvp/OF5baseband.tar?dl=0
Steps:
-Power down phone completely.
-Boot into download mode (vol+down,power,home)
-Uncheck 'auto reboot' in Odin & flash.
-Remove battery, wait 5 sec, re-insert battery and boot into download mode.
-Re-check 'auto reboot' in Odin & flash.
Done
Click to expand...
Click to collapse
Hey freeza! So you flash the same file twice? Just wanna make sure get it rigjt cause i know modems can brick phones if done wrong. Thanx!!
Awesome, I was wondering why we could do this with the HTC phones and not the Samsungs. Guess we just needed the right people here. Before you got here freeza we were having to Odin a new update, didn't make sense to me to take a whole update, just to move on to the updated custom roms instead of just updating the baseband than you can move on or not if you want. Thanks
tanderson164 said:
I have tried to get my msl from sprint twice i guess I will have to keep trying because right now I feel like I am using my HTC evo it takes forever to load maps or anything
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I called Sprint customer service yesterday and when the lady answered I asked her with some authority, I need the MSL for one of the phones on my account. she said no problem I'll get that for you, I grabbed the pen and wrote the number down. if she asked why I needed the number I would have said I'm a developer and I need to access certain features of the phone to test an app I'm developing. I didn't have to go that far. Oh yeah and I was feeling lucky....
xyojimbox said:
Hey freeza! So you flash the same file twice? Just wanna make sure get it rigjt cause i know modems can brick phones if done wrong. Thanx!!
Click to expand...
Click to collapse
Yes indeed you need to flash it twice for a safety precaution and to ensure the file properly flashes and sticks.
I was a victim once, didn't know about needing to flash twice so I flashed it just once and it didn't stick.
Nickitt said:
Yes indeed you need to flash it twice for a safety precaution and to ensure the file properly flashes and sticks.
I was a victim once, didn't know about needing to flash twice so I flashed it just once and it didn't stick.
Click to expand...
Click to collapse
Ok cool thank you
Worked like a charm thank you freeza!!!!!
I finally got my msl had to go on chat when I got home it took a whole 2 minutes but I never got anything from calling customer care thanks for all the help
Sent from my SM-N910P using Tapatalk
I am having a heck of a time getting this to flash in Odin 3.07 . After it flashes the phone reboots to the Samsung Galaxy Note 4...powered by Android screen then goes black, vibrates twice then continuously repeats the same process of booting up going black then vibrating twice.
Any ideas? Should I use a newer version of Odin? I'm on stock rooted OB7.
Thanks guys!
ianmb said:
I am having a heck of a time getting this to flash in Odin 3.07 . After it flashes the phone reboots to the Samsung Galaxy Note 4...powered by Android screen then goes black, vibrates twice then continuously repeats the same process of booting up going black then vibrating twice.
Any ideas? Should I use a newer version of Odin? I'm on stock rooted OB7.
Thanks guys!
Click to expand...
Click to collapse
You need to flash a OF5 rom after you flash the OF5 baseband. Or you can use Notarized Rom with OF5 baseband.
January 1 Security update. Everything else seems to have stayed the same.
{
"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"
}
Another update! Cool.
These security updates are coming very frequently. I would be careful updating if you value an unlocked bootloader. I wouldn't bet that Samsung wouldn't pull a fast one and lock it down even at this stage of the N4's life span. So be careful just incase.
Could anyone installed this update, confirms that the bootloader still unlocked, plz?
Sent from my SM-N910P using Tapatalk
tx_dbs_tx said:
These security updates are coming very frequently. I would be careful updating if you value an unlocked bootloader. I wouldn't bet that Samsung wouldn't pull a fast one and lock it down even at this stage of the N4's life span. So be careful just incase.
Click to expand...
Click to collapse
I agree. I never update until i have an Odin file!
aaron74 said:
I agree. I never update until i have an Odin file!
Click to expand...
Click to collapse
When you get the full tar file which files you remove from the tar before flashing to make sure that your bootloader still the old unlocked one?
anees02 said:
When you get the full tar file which files you remove from the tar before flashing to make sure that your bootloader still the old unlocked one?
Click to expand...
Click to collapse
I dont remove anything. But just use the name to verify the bootloader is same version. I cant verify this but I read somewhere that as long as the version number doesnt change, then its backwards flashable. Heres an example of what I mean.
Heres current firmware on sammobile N910PVPS4DPK1
and following so on like these N910PVPS4DPJ1, N910PVPU4DPH4, etc.
After the PVP is the bootloader version # as "S4" and "U4". Now what I read is as long as that # is same, that determines what firmware you can use.
So if you go back to firmware that we cant go back to like N910PVPU3BOF5. You can see its a 3. This is why we can only go back to N910PVPU4COG5
So in other words, as long as that stays a "4" , we should be able to downgrade to any firmware that is a "4".
As I already stated, I dont know this first hand, but have read it somewhere here!!
Hope this was helpful!!
aaron74 said:
I dont remove anything. But just use the name to verify the bootloader is same version. I cant verify this but I read somewhere that as long as the version number doesnt change, then its backwards flashable. Heres an example of what I mean.
Heres current firmware on sammobile N910PVPS4DPK1
and following so on like these N910PVPS4DPJ1, N910PVPU4DPH4, etc.
After the PVP is the bootloader version # as "S4" and "U4". Now what I read is as long as that # is same, that determines what firmware you can use.
So if you go back to firmware that we cant go back to like N910PVPU3BOF5. You can see its a 3. This is why we can only go back to N910PVPU4COG5
So in other words, as long as that stays a "4" , we should be able to downgrade to any firmware that is a "4".
As I already stated, I dont know this first hand, but have read it somewhere here!!
Hope this was helpful!!
Click to expand...
Click to collapse
Thank you very much.
I knew something new today because of you... Thanks again.
When I see to the latest OTA QA1 there are two things T4 and S4 what does that mean?
Maybe different CSC versions?
anees02 said:
Thank you very much.
I knew something new today because of you... Thanks again.
When I see to the latest OTA QA1 there are two things T4 and S4 what does that mean?
Maybe different CSC versions?
Click to expand...
Click to collapse
On all firmwares. The middle listing is the csc version, and its always got a different numbering than the others.
There's 3 version numbers here. 1st is the PDA (which is the actual rom firmware) 2nd is CSC (which is region) 3rd is the PHONE (which is the modem)
So this one is still #4 so it should be alright to still downgrade.
Now the last 3 digits just rep the date. Q=2017 A=January 1= 1st revision.
https://forum.xda-developers.com/showthread.php?t=1356325
wow. learning new things. thank guys.
just a little too late, after taking the update myself.
Has anyone been able to twrp/root? or odin backwards is the only way right now?
linhnd2000 said:
wow. learning new things. thank guys.
just a little too late, after taking the update myself.
Has anyone been able to twrp/root? or odin backwards is the only way right now?
Click to expand...
Click to collapse
You can Odin back as far as OG5 which is Android Lollipop 5.1
You can Odin TWRP on any of those updates. But Odin the desired update first if that's your goal.
What gets overlooked with TWRP flash is that you should boot directly into recovery after flashing. If you boot system first, immediately after TWRP flash, stock recovery gets restored.
That pattern and timing is tricky so it's recommended to uncheck auto reboot in Odin options when flashing TWRP. Once you get the success, 0 failed in Odin status, pull the USB cable and battery and wait at least 30 seconds (some suggest waiting at least a minute while discharging power circuit by holding power button down *Don't go Beastmode on that power button*). Reinstall battery and pattern boot into recovery (Vol+, Power and Home simultaneously until phone vibrates).
If you're rooting stock with stock kernel, you need systemless superuser. Flash SuperSU zip by Chainfire in recovery.
If flashing a custom ROM, you only need TWRP. No pre-root required for that.
Sent from my SM-N920P using Tapatalk
samep said:
You can Odin back as far as OG5 which is Android Lollipop 5.1
You can Odin TWRP on any of those updates. But Odin the desired update first if that's your goal.
What gets overlooked with TWRP flash is that you should boot directly into recovery after flashing. If you boot system first, immediately after TWRP flash, stock recovery gets restored.
That pattern and timing is tricky so it's recommended to uncheck auto reboot in Odin options when flashing TWRP. Once you get the success, 0 failed in Odin status, pull the USB cable and battery and wait at least 30 seconds (some suggest waiting at least a minute while discharging power circuit by holding power button down *Don't go Beastmode on that power button*). Reinstall battery and pattern boot into recovery (Vol+, Power and Home simultaneously until phone vibrates).
If you're rooting stock with stock kernel, you need systemless superuser. Flash SuperSU zip by Chainfire in recovery.
If flashing a custom ROM, you only need TWRP. No pre-root required for that.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
works perfectly. thanks. I went back to PK1 so I can use the debloated rom.
I have Galaxy s8 on Verizon SM-G950U, a standard update notice kept appearing past few days, finally installed it. The minute it finished, it is now in an endless restarting loop. Does not stay on. Tried cache wipe and safe mode, no luck. I am trying to salvage some picture and files in it. I'm 3 days into researching this stuff and watching endless videos, I still dont know what or how to do this.
1) Would ADB allow backup of files if the phone wont stay on? It does stay on when in Android Recovery mode (Volume down and Power button press), but would recovery mode allow access to internal files such as backing up pictures?
2) I was considering trying to flash my phone. But would that even work without it being on the normal homescreen? If so, would I just download whatever the latest ODIN is, 3.13.1? And then whatever the latest Firmware software is for my phone (see below)?
{
"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"
}
halfhumble said:
I have Galaxy s8 on Verizon SM-G950U, a standard update notice kept appearing past few days, finally installed it. The minute it finished, it is now in an endless restarting loop. Does not stay on. Tried cache wipe and safe mode, no luck. I am trying to salvage some picture and files in it. I'm 3 days into researching this stuff and watching endless videos, I still dont know what or how to do this.
1) Would ADB allow backup of files if the phone wont stay on? It does stay on when in Android Recovery mode (Volume down and Power button press), but would recovery mode allow access to internal files such as backing up pictures?
2) I was considering trying to flash my phone. But would that even work without it being on the normal homescreen? If so, would I just download whatever the latest ODIN is, 3.13.1? And then whatever the latest Firmware software is for my phone (see below)?
Click to expand...
Click to collapse
Yes the firmware below is the latest. You put your device in download mode and flash using the latest Odin as for your data. Do not use the home csc. Will wipe. Other than most of the time your data should be safe. Not always but most of the time. Uncheck nand erase
TheMadScientist said:
Yes the firmware below is the latest. You put your device in download mode and flash using the latest Odin as for your data. Do not use the home csc. Will wipe. Other than most of the time your data should be safe. Not always but most of the time. Uncheck nand erase
Click to expand...
Click to collapse
Wow, good I saw your reply. Because an article I was reading said Make sure you choose the HOME_CSC, and not CSC file.
So would I just leave the CSC file section blank? Or use the CSC file?
halfhumble said:
Wow, good I saw your reply. Because an article I was reading said Make sure you choose the HOME_CSC, and not CSC file.
So would I just leave the CSC file section blank? Or use the CSC file?
Click to expand...
Click to collapse
You could leave it blank
userdata
TheMadScientist said:
You could leave it blank
Click to expand...
Click to collapse
Sorry, one more thing, the UserData button, some tutorials say leave it blank, other say to use it.
What should I do? As I know the Tiniest mistake could mess this up, so Im crossing my T's and dotting my I's......
halfhumble said:
Sorry, one more thing, the UserData button, some tutorials say leave it blank, other say to use it.i
What should I do? As I know the Tiniest mistake could mess this up, so Im crossing my T's and dotting my I's......
Click to expand...
Click to collapse
Blank
halfhumble said:
Sorry, one more thing, the UserData button, some tutorials say leave it blank, other say to use it.
What should I do? As I know the Tiniest mistake could mess this up, so Im crossing my T's and dotting my I's......
Click to expand...
Click to collapse
Bassicly system and bootloader are the most important.
TheMadScientist said:
Bassicly system and bootloader are the most important.
Click to expand...
Click to collapse
So no luck, here's what I get, Failed (1):
halfhumble said:
I have Galaxy s8 on Verizon SM-G950U, a standard update notice kept appearing past few days, finally installed it. The minute it finished, it is now in an endless restarting loop. Does not stay on. Tried cache wipe and safe mode, no luck. I am trying to salvage some picture and files in it. I'm 3 days into researching this stuff and watching endless videos, I still dont know what or how to do this.
1) Would ADB allow backup of files if the phone wont stay on? It does stay on when in Android Recovery mode (Volume down and Power button press), but would recovery mode allow access to internal files such as backing up pictures?
2) I was considering trying to flash my phone. But would that even work without it being on the normal homescreen? If so, would I just download whatever the latest ODIN is, 3.13.1? And then whatever the latest Firmware software is for my phone (see below)?
Click to expand...
Click to collapse
Welcome to XDA halfhumble, good to have with us
halfhumble said:
So no luck, here's what I get, Failed (1):
Click to expand...
Click to collapse
sorry mate it was late. What the error on the device. Does it show a fused binary
halfhumble said:
I have Galaxy s8 on Verizon SM-G950U, a standard update notice kept appearing past few days, finally installed it. The minute it finished, it is now in an endless restarting loop. Does not stay on. Tried cache wipe and safe mode, no luck. I am trying to salvage some picture and files in it. I'm 3 days into researching this stuff and watching endless videos, I still dont know what or how to do this.
1) Would ADB allow backup of files if the phone wont stay on? It does stay on when in Android Recovery mode (Volume down and Power button press), but would recovery mode allow access to internal files such as backing up pictures?
2) I was considering trying to flash my phone. But would that even work without it being on the normal homescreen? If so, would I just download whatever the latest ODIN is, 3.13.1? And then whatever the latest Firmware software is for my phone (see below)?
Click to expand...
Click to collapse
Welcome to XDA halfhumble
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