Related
my Xperia Play R800i will not turn on anymore after i tried to flash a rom... i dont exactly remember which one it was... i hope its not important
what my phone does is showing the Sony Ericsson logo and just stays there... i had it on the entire day just be sure that i wasnt doing something in the background or anything ...
but i never did it on my phone yet... (maybe better if never did this now i think of it)
but anyway pc companion says "null" and thats all it will say further it cannot detect my phone or do anything with it
i hope flashtool works if anyone is willing to lead me through it.
i dont have warranty anymore.
MausHaxxi said:
my Xperia Play R800i will not turn on anymore after i tried to flash a rom... i dont exactly remember which one it was... i hope its not important
what my phone does is showing the Sony Ericsson logo and just stays there... i had it on the entire day just be sure that i wasnt doing something in the background or anything ...
but i never did it on my phone yet... (maybe better if never did this now i think of it)
but anyway pc companion says "null" and thats all it will say further it cannot detect my phone or do anything with it
i hope flashtool works if anyone is willing to lead me through it.
i dont have warranty anymore.
Click to expand...
Click to collapse
Would you happen to have a custom kernel? Which Sony Ericsson logo is it, the non-moving one or the animated one?
Now, you wouldn't have happened to install a CyanogenMod, Ice Cream Sandwich or Jelly Bean rom, would you? I know you don't remember which rom you installed, just trying to spark a memory. Anyway, if you did so, then all you need to do is flash a compatible kernel. You see, if the Sony Ericsson logo you are seeing is the non-moving one, then you have the stock kernel, the one that's incompatible with the aforementioned roms.
If you don't want to get involved with this kernel business, then I've provided a Flashtool guide, so you can at least get your phone to a working, albeit factory reset, state:
First, install Flashtool.
Go here and find what you think your stock firmware was, download it.
Place the .ftf file in your Flashtool/firmwares directory.
Open Flashtool (as administrator if necessary) and click on the lightning bolt in the Flashtool window. Highlight Flashmode and select OK. A new window shall pop-up.
Select your downloaded firmware. I should read "R800i" in the first box and "4.0.2.A.0.XX" (with the "XX" being the number of the version you downloaded) in the second, the contents of the third box varies, so disregard it. There are many options for what to keep/replace during flashing, but I'd recommend leaving them as they are. Select OK. The window will now close and a new window will pop-up shortly after.
This window will detail the proceeding steps: With your turned-off phone (make sure its battery is intact), hold the back key (the leftmost one) while inserting the usb from your computer to your phone, continue holding the key until the window closes, DO NOT REMOVE THE USB.
The Flashtool window will now begin streaming various lines detailing its progress, all you need to look for is the line detailing a successful flash which with then tell you to disconnect your phone, now you can remove the USB.
Go ahead and close the remaining Flashtool window, your phone should now be back to default, factory reset, everything except your phone's bootloader and SIM unlocked statuses, they should be how you left them before.
thanks!
Toasty Clown said:
Would you happen to have a custom kernel? Which Sony Ericsson logo is it, the non-moving one or the animated one?
Now, you wouldn't have happened to install a CyanogenMod, Ice Cream Sandwich or Jelly Bean rom, would you? I know you don't remember which rom you installed, just trying to spark a memory. Anyway, if you did so, then all you need to do is flash a compatible kernel. You see, if the Sony Ericsson logo you are seeing is the non-moving one, then you have the stock kernel, the one that's incompatible with the aforementioned roms.
If you don't want to get involved with this kernel business, then I've provided a Flashtool guide, so you can at least get your phone to a working, albeit factory reset, state:
First, install Flashtool.
Go here and find what you think your stock firmware was, download it.
Place the .ftf file in your Flashtool/firmwares directory.
Open Flashtool (as administrator if necessary) and click on the lightning bolt in the Flashtool window. Highlight Flashmode and select OK. A new window shall pop-up.
Select your downloaded firmware. I should read "R800i" in the first box and "4.0.2.A.0.XX" (with the "XX" being the number of the version you downloaded) in the second, the contents of the third box varies, so disregard it. There are many options for what to keep/replace during flashing, but I'd recommend leaving them as they are. Select OK. The window will now close and a new window will pop-up shortly after.
This window will detail how the preceding steps: With your turned-off phone (make sure its battery is intact), hold the back key (the leftmost one) while inserting the usb from your computer to your phone, continue holding the key until the window closes, DO NOT REMOVE THE USB.
The Flashtool window will now begin streaming various lines detailing its progress, all you need to look for is the line detailing a successful flash which with then tell you to disconnect your phone, now you can remove the USB.
Go ahead and close the remaining Flashtool window, your phone should now be back to default, factory reset, everything except your phone's bootloader and SIM unlocked statuses, they should be how you left them before.
Click to expand...
Click to collapse
Thanks, i will try this when im home tonight
i will tell you if i got it working again lol (ps. i aint a noob... i never got freezings before... i was just being cautious so i wont break it behond repair LOL)
ALMOST fixed
ok it works again now. but now it asks me to download settings ... which it fails in... my phone tells me that it failed and asks me to retry downloading them.... which eventually will fail again... i got wifi on ofcourse (duh...)
anyway... i dont get it why i am having so much trouble with my phone.... my tablet i can hack without hassle... i just never used flashtool XD
always cmd and such...
anyway im almost there to have it completely fixed
thanks so far
MausHaxxi said:
ok it works again now. but now it asks me to download settings ... which it fails in... my phone tells me that it failed and asks me to retry downloading them.... which eventually will fail again... i got wifi on ofcourse (duh...)
anyway... i dont get it why i am having so much trouble with my phone.... my tablet i can hack without hassle... i just never used flashtool XD
always cmd and such...
anyway im almost there to have it completely fixed
thanks so far
Click to expand...
Click to collapse
Okay, having not used stock in a long time, I've reverted my rom and kernel! Upon doing so, I noticed little wrong. Though I do remember an annoying prompt when I opened the browser, it'd say "Please insert SIM card" and "downloading settings" would pop-up following it.
Aside from that, I can't recreate the problem you're having. Could you go into more detail?
screen photo
Toasty Clown said:
Okay, having not used stock in a long time, I've reverted my rom and kernel! Upon doing so, I noticed little wrong. Though I do remember an annoying prompt when I opened the browser, it'd say "Please insert SIM card" and "downloading settings" would pop-up following it.
Aside from that, I can't recreate the problem you're having. Could you go into more detail?
Click to expand...
Click to collapse
here is the popup that i get all the time.... while i CAN call people and receive calls... my phone refuses to use 3G which i do need...
MausHaxxi said:
here is the popup that i get all the time.... while i CAN call people and receive calls... my phone refuses to use 3G which i do need...
Click to expand...
Click to collapse
Well... That's something I have never seen before...
Searched the Q&A and troubleshooting section, and I'd found a thread detailing such an error upon switching firmware. No offence but perhaps I didn't give you enough detail on which firmware to download, and for that I apologise.
Would you happen to know what branding your phone is, and post what it is and which firmware you installed (you can find said information in that third box I told you to ignore in Flashtool)? AT&T, Verizon, unbranded/no SIM/unlocked? I ask this as you may have installed incompatible firmware.
As an example, my phone was unbranded and came with no SIM, the pre-installed installed firmware (and the only one that I find to be fully compatible) was the R800i 4.0.2.A.0.42 UK Generic. In the context of stock roms, I find that it's best not to stray.
Anyway, you've probably already figured out what to do: find the intended firmware and flash it, using the instructions above. I'd recommend gathering some more outside help, changing the thread's title to reflect the current conundrum should be a good starting point.
will do
Toasty Clown said:
Well... That's something I have never seen before...
Searched the Q&A and troubleshooting section, and I'd found a thread detailing such an error upon switching firmware. No offence but perhaps I didn't give you enough detail on which firmware to download, and for that I apologise.
Would you happen to know what branding your phone is, and post what it is and which firmware you installed (you can find said information in that third box I told you to ignore in Flashtool)? AT&T, Verizon, unbranded/no SIM/unlocked? I ask this as you may have installed incompatible firmware.
As an example, my phone was unbranded and came with no SIM, the pre-installed installed firmware (and the only one that I find to be fully compatible) was the R800i 4.0.2.A.0.42 UK Generic. In the context of stock roms, I find that it's best not to stray.
Anyway, you've probably already figured out what to do: find the intended firmware and flash it, using the instructions above. I'd recommend gathering some more outside help, changing the thread's title to reflect the current conundrum should be a good starting point.
Click to expand...
Click to collapse
if i cant obtain the required info i need i will make a new post regarding this issue...
but thanks to you for getting my phone to a working state
ps. i will post here if i got the 3G back to work or not using the thread you supplied.
fixed
MausHaxxi said:
if i cant obtain the required info i need i will make a new post regarding this issue...
but thanks to you for getting my phone to a working state
ps. i will post here if i got the 3G back to work or not using the thread you supplied.
Click to expand...
Click to collapse
it was simply the APN settings....
how could i know xD never had this error before... anyway it works fine now 3G works smoothly
MausHaxxi said:
it was simply the APN settings....
how could i know xD never had this error before... anyway it works fine now 3G works smoothly
Click to expand...
Click to collapse
Oh, sorry about that. I'd only ever experienced an APN problem when one of the roms I had installed had a broken settings app.
Anyway, it's nice to see that you've fixed your phone yourself, congrats!
I recently picked up a D851 (TMobile). I rooted it, but did not replace the ROM or install a custom bootloader.
Last weekend, the phone started randomly rebooting. Watching logcat via adb showed me several random apps throwing sig11s, after which the phone would give up and reboot. Cycle repeats.
This looks like a hardware issue, as the apps that crash change on each boot cycle.
I arranged with TMobile to swap the device, but they cautioned me that the phone must be returned to an unrooted state.
I've had a hell of a time with it from here. My first try was to install the LG drivers and the PC Suite under a Windows VM, as I do not run Windows at home. Enabling USB passthrough for the phone to the VM let Windows see the phone, but the LG drivers would invariably fail with 'Device cannot start. Code 10.'. Likewise, the PC Suite couldn't find the phone.
Next step was to throw together some spare hw and install Windows 7 on that (a desparate move, to be certain. ). The LG drivers can now recognize the phone, so that's a definite plus. The LG PC Suite, though, claimed that my phone could not be upgraded. Wonderful.
Next step was to try this tutorial: http://www.androidrootz.com/2014/07/how-to-unroot-lg-g3-all-variants.html . I was able to get further with this method, but as it begins to flash SYSTEM, it pauses, and then dies with 'We can't communicate with Phone'. End result - I now have a soft bricked phone. On the phone, I see the port - COM41 - appear, and the usb animation starts to spin ... and after a few seconds, stops. It's at this point that Flashtool throws the Can't Connect error.
I next tried following this tutorial: http://forum.xda-developers.com/showthread.php?t=2785089 to flash a KDZ. The newer LG Flash tool used here can't create a connection to my phone for flashing.
I've run into a wall here. Any ideas on where to go next? I need to reset this phone back to a working stock state so that I can send it back.
http://lgg3root.com/lg-g3-root/how-to-unrootunbrick-lg-g3/
Use this and follow video carefully. Has worked many times. Use all his links not what you have downloaded.
NOTE 4
BACARDILIMON said:
http://lgg3root.com/lg-g3-root/how-to-unrootunbrick-lg-g3/
Use this and follow video carefully. Has worked many times. Use all his links not what you have downloaded.
NOTE 4
Click to expand...
Click to collapse
Also - as silly as it sounds, make certain you're using the USB cable that came with the phone. This has solved problems for a lot of people when trying to revert to stock.
etawful said:
Also - as silly as it sounds, make certain you're using the USB cable that came with the phone. This has solved problems for a lot of people when trying to revert to stock.
Click to expand...
Click to collapse
I wasn't initially, but I did switch to it last night. Still no go.
I suspect it's either the phone itself (see above: re suspected hw failure), or the PC in question (nVidia chipset on this old motherboard, and I've had more than a few problems with adb talking to phones on nVidia motherboards). I'm going to try Bacardilimon's suggestion tonight, on a PC that has *nothing* nVidia-related in it, before I throw in the towel. As it is, the failing phone needs to be back to TMO by the middle of next week, so I'm all but out of time to resolve this.
Drake Maijstral said:
I recently picked up a D851 (TMobile). I rooted it, but did not replace the ROM or install a custom bootloader.
Last weekend, the phone started randomly rebooting. Watching logcat via adb showed me several random apps throwing sig11s, after which the phone would give up and reboot. Cycle repeats.
This looks like a hardware issue, as the apps that crash change on each boot cycle.
I arranged with TMobile to swap the device, but they cautioned me that the phone must be returned to an unrooted state.
I've had a hell of a time with it from here. My first try was to install the LG drivers and the PC Suite under a Windows VM, as I do not run Windows at home. Enabling USB passthrough for the phone to the VM let Windows see the phone, but the LG drivers would invariably fail with 'Device cannot start. Code 10.'. Likewise, the PC Suite couldn't find the phone.
Next step was to throw together some spare hw and install Windows 7 on that (a desparate move, to be certain. ). The LG drivers can now recognize the phone, so that's a definite plus. The LG PC Suite, though, claimed that my phone could not be upgraded. Wonderful.
Next step was to try this tutorial: http://www.androidrootz.com/2014/07/how-to-unroot-lg-g3-all-variants.html . I was able to get further with this method, but as it begins to flash SYSTEM, it pauses, and then dies with 'We can't communicate with Phone'. End result - I now have a soft bricked phone. On the phone, I see the port - COM41 - appear, and the usb animation starts to spin ... and after a few seconds, stops. It's at this point that Flashtool throws the Can't Connect error.
I next tried following this tutorial: http://forum.xda-developers.com/showthread.php?t=2785089 to flash a KDZ. The newer LG Flash tool used here can't create a connection to my phone for flashing.
I've run into a wall here. Any ideas on where to go next? I need to reset this phone back to a working stock state so that I can send it back.
Click to expand...
Click to collapse
There is a link in the general thread on how to return to stock including a method using twrp. It's a sticky thread at the top I've never done the twrp method myself but it can more than likely be done without a computer. Twrp can be installed via Playstore if you don't already have it
BACARDILIMON said:
httx://lgg3root.com/lg-g3-root/how-to-unrootunbrick-lg-g3/
Use this and follow video carefully. Has worked many times. Use all his links not what you have downloaded.
NOTE 4
Click to expand...
Click to collapse
Holy hell. That site's links are absolutely infuriating. Anyone who puts each and every download link for software referenced by a howto behind separate timed appearance links that you have to ALSO enter an annoying captcha to enable should be shot out of a cannon - or, at the very least, have their howto ignored by the rest of the world.
Suffice it to say, the quality of that page doesn't give me much confidence that this will work any better than what I've tried already. Since I've already wasted a crapload of time on this project, and more on following those damned links, I'll give it a try tonight, but I'm not going to hold my breath.
Is the author of that page an XDA member? If so, please let me know who he is, so I can berate him personally. Thanks.
Toneman07 said:
There is a link in the general thread on how to return to stock including a method using twrp. It's a sticky thread at the top I've never done the twrp method myself but it can more than likely be done without a computer. Twrp can be installed via Playstore if you don't already have it
Click to expand...
Click to collapse
I'd consider doing that, except as I mentioned, the G3 in question disconnected during a run of Flashtool, rendering it without a working OS to boot to. The phone now boots straight to download mode. The good news is, it's now officially unrooted. The bad news is, it's also officially bricked until I can get an OS flash to work.
Drake Maijstral said:
Holy hell. That site's links are absolutely infuriating. Anyone who puts each and every download link for software referenced by a howto behind separate timed appearance links that you have to ALSO enter an annoying captcha to enable should be shot out of a cannon - or, at the very least, have their howto ignored by the rest of the world.
Suffice it to say, the quality of that page doesn't give me much confidence that this will work any better than what I've tried already. Since I've already wasted a crapload of time on this project, and more on following those damned links, I'll give it a try tonight, but I'm not going to hold my breath.
Is the author of that page an XDA member? If so, please let me know who he is, so I can berate him personally. Thanks.
Click to expand...
Click to collapse
OK I gonna keep it real with you. You can either enter the captcha and fix the issue or throw the phone away. Yes he is a member and for every phone that is out their he has its own page doing this for us. If you can't fix your phone with his method then it not the method but you. I have used this for many bricks. It works and it works great. Sorry if he making you do a little typing but like I said u can use his method or keep trying the other methods. Good luck
NOTE 4
BACARDILIMON said:
OK I gonna keep it real with you. You can either enter the captcha and fix the issue or throw the phone away. Yes he is a member and for every phone that is out their he has its own page doing this for us. If you can't fix your phone with his method then it not the method but you. I have used this for many bricks. It works and it works great. Sorry if he making you do a little typing but like I said u can use his method or keep trying the other methods. Good luck
NOTE 4
Click to expand...
Click to collapse
After going through the painful process of clicking his links, I found that everything I downloaded is the same thing I already had, except for Flashtool - lgg3root's is actually older. Even the TMO firmware for my phone and the dll are both exactly the same, and I checked by running md5sum on them.
But hey, it must be me. There's clearly no other technology-related cause for this issue. I obviously don't know how to follow a howto, right?
Thanks for 'keeping it real'.
Drake Maijstral said:
After going through the painful process of clicking his links, I found that everything I downloaded is the same thing I already had, except for Flashtool - lgg3root's is actually older. Even the TMO firmware for my phone and the dll are both exactly the same, and I checked by running md5sum on them.
But hey, it must be me. There's clearly no other technology-related cause for this issue. I obviously don't know how to follow a howto, right?
Thanks for 'keeping it real'.
Click to expand...
Click to collapse
See we agree.
NOTE 4
BACARDILIMON said:
See we agree.
NOTE 4
Click to expand...
Click to collapse
Not likely.
In any case, it failed again. The video he did gave me the exact same steps I followed elsewhere, and unsurprisingly, it failed with 'We can't communicate with Phone', after beginning the flash process. There is something else wrong here, though I'm not certain if the failing phone is at fault or the PC in question is causing the issue. To be crystal clear, the flash process starts, and then, at a random point during the flash, it completely stops, and Flashtool eventually gives up and throws the aforementioned error.
Any other ideas? If not, I'm going to have to try another PC to rule that out as the culprit. Sigh.
Mine gave the same error as well as couldn't communicate with server but the flash process continued running and the phone rebooted took about 3 minutes u learned not to touch any of the popups on the screen during flash and sorry I missed the part about no OS I thought you were booting to recovery... Driving while reading not the best idea
Toneman07 said:
Mine gave the same error as well as couldn't communicate with server but the flash process continued running and the phone rebooted took about 3 minutes u learned not to touch any of the popups on the screen during flash and sorry I missed the part about no OS I thought you were booting to recovery... Driving while reading not the best idea
Click to expand...
Click to collapse
Nope, the phone is definitely not doing anything - the usb animation on the G3 completely stops before Flashtool throws the error.
And damnit, quit reading while driving. You can do that later.
Moved the hdd Windows is installed on to another PC with a different chipset. After it updated drivers, I tried again. Flash proceeded partway, then died. Reset phone, Flashtool reststarted flash from scratch, flash died at 15%.
15% is interesting. While I've seen the flash die at various points, 15% is the one that was most often repeated. This tells me the failure follows the phone, not the PC - which makes sense, as the phone has a suspected RAM failure.
At this point, it appears that flashing this phone is impossible due to faulty hw. Hopefully TMO (and eventually, LG) will accept the faulty phone back with no OS, because there's no way an OS is being written to this device ever again.
Thank you for answering
yanowman said:
Thank you for answering
Click to expand...
Click to collapse
No problem. There's nothing I hate more than stumbling across a thread where the OP has the same problem I have, only to find it was never updated with the solution.
Good luck man let us know what tmobile says
Ok, first of all, new to rooting and all that follows. However, I'm not new to forums and if this is in the wrong category, or if I overlooked a similar post, I am sorry. Feel free to redirect me to wherever you see fit. I know just too well how similar posts can be annoying, but I feel like I've exhausted Googlesearching and looked everywhere I can think of.
So, I have a Note II. N7100, Android 4.4.2 and I want to root it. Googlesearching has found me a lot of nice looking ROMs, and besides looks the added functions tempt me. Wont be long until I upgrade to a Note 4 or 5 anyway, figure I might as well. For what its worth, I live in Norway, and AT&T does not exist over here, nor does any other major american carrier. USB debugging was on the entire time.
I got the Odin V3.10, and appropriate clockworksmod files, and thought everything was peaches. Into download mode (after backing up ofc), Odin finds it, I upload everything and Odin says "PASS" in nice, green letters. When it reboots, it looks the same as before, but.. "Unfortunately, SuperUser has stopped", Titanium backup does not work since it apparently isnt rooted. Root Checker says the same. However, when checking for updates my phone displays "The operating system on your device has been modified in an unautorized way. Try downloading software updates using Samsung KIES on your PC, or visit a customer service center."
Read alot about devices having to be unlocked from carrier, however all google searches on "how to check for carrier lock on Note 2" yields numbersequences I have to input into the dialler and dial. None of the sequences give anything other than "Connection problem or invalid MMI code". I honestly dont remember if its carrier locked or not.
I came across an article here on XDA saying that with the later versions of android, KNOX has become an issue when trying to root, but someone had found a way around it. I downloaded MJ5BLPatch.tar.md5, uploaded to my phone via Odin, and here it fails, looses connection with the device and cant reconnect. Phone displays something alon the lines of "Invalid magic code" or the similar in red text.
I am the newb here, looking for help, and if I screwed up big somewhere I am cool with a little flaming. I just want to squeeze this for what use I can before upgrading, and probably rooting that too.
Any help as to how I can root it and load custom ROMs? I appreciate any and all help, sincerely.
Forget that MJ5 bootloader related stuff.
Reflash CWM using Odin and untick auto reboot, run through and reboot manually.
After reboot into recovery flash SuperSu.zip, start supersu after reboot system and disable knox by following the advices from app.
Thank you very much. i feel exceedingly stupid, I had been using the guide found on Note2root.com, when I applied step by step from this guide (http://forum.xda-developers.com/showthread.php?t=2143479) everything worked out. hope this may be of help to anyone having the same issues.
Again, thank you very much for your help.
Hello, first timer here. I have never tried rooting or anything, but today I finally decided to... and messed it up.
Verizon Samsung Note 2 SCH-i605 (yes, still.)
Got it on July 2nd, 2013, so I believe it was build 4.1.1 kernel 3.1? Not too sure on the legalities
Completely unrooted and unmodded
I was using kingo root and everything was fine until it hit about 52% on the rooting process when my computer lost connection with my phone. Since, it gave me the "Firmware upgrade encountered an issue" problem. So then I google-fu'd and followed directions of:
http://forum.xda-developers.com/showthread.php?t=2040264
http://forum.xda-developers.com/showthread.php?t=2120726
http://forum.xda-developers.com/showthread.php?t=2582290
http://forum.xda-developers.com/showthread.php?t=2024207
etc.
and used Odin 3.10.7 (and 3.10.0 just in case, both on and off admin mode cause why not) on every single md5 available in all those links and the one from sammobile.com for sch-i605.
And each time, I would either received failure on "sboot.bin" or receive the "System Software Not Authorized" error if succeeded (it was stuck in bootload? too, kept flashing the logo then the error message). The VERY first time, however, it actually brought me to that page where I'm allowed to press things like erase cache, factory reset, or reboot my phone. There, I chose all those options in the order I've listed them. And ever since I haven't seen that screen again.
My issue seems to be every problem I can find put together, and can't seem to resolve it with my skills alone. I honestly don't care about recovering my data (which I believe is impossible now anyway) or rooting my phone. I just want it to turn on again.
Thanks in advance.
p.s. getting a new phone isn't an option currently
-edit-
Checked my verizon wireless software upgrade assistant for some info, and it says "Up to date" and "Version ND3" if that means anything to you pros out there.
jk1982 said:
Hello, first timer here. I have never tried rooting or anything, but today I finally decided to... and messed it up.
Verizon Samsung Note 2 SCH-i605 (yes, still.)
Got it on July 2nd, 2013, so I believe it was build 4.1.1 kernel 3.1? Not too sure on the legalities
Completely unrooted and unmodded
I was using kingo root and everything was fine until it hit about 52% on the rooting process when my computer lost connection with my phone. Since, it gave me the "Firmware upgrade encountered an issue" problem. So then I google-fu'd and followed directions of:
http://forum.xda-developers.com/showthread.php?t=2040264
http://forum.xda-developers.com/showthread.php?t=2120726
http://forum.xda-developers.com/showthread.php?t=2582290
http://forum.xda-developers.com/showthread.php?t=2024207
etc.
and used Odin 3.10.7 (and 3.10.0 just in case, both on and off admin mode cause why not) on every single md5 available in all those links and the one from sammobile.com for sch-i605.
And each time, I would either received failure on "sboot.bin" or receive the "System Software Not Authorized" error if succeeded (it was stuck in bootload? too, kept flashing the logo then the error message). The VERY first time, however, it actually brought me to that page where I'm allowed to press things like erase cache, factory reset, or reboot my phone. There, I chose all those options in the order I've listed them. And ever since I haven't seen that screen again.
My issue seems to be every problem I can find put together, and can't seem to resolve it with my skills alone. I honestly don't care about recovering my data (which I believe is impossible now anyway) or rooting my phone. I just want it to turn on again.
Thanks in advance.
p.s. getting a new phone isn't an option currently
-edit-
Checked my verizon wireless software upgrade assistant for some info, and it says "Up to date" and "Version ND3" if that means anything to you pros out there.
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist. To get you the best possible assistance, I'm going to move this thread to your device's Q&A forum. Good luck!
install kies and try flashing rom. do you have rom from i.e. sammobile? use different odin versions and do not mark repartition
yaro666 said:
install kies and try flashing rom. do you have rom from i.e. sammobile? use different odin versions and do not mark repartition
Click to expand...
Click to collapse
KIES is unable to read my phone (tried the bottom 3 versions of it), and I've tried running Odin 3.07 and unchecked repartition for every stock and restore md5s I had for my phone... the ones that didn't fail sboot.bin are still giving me unauthorized error.
I'll keep trying all the combinations, but it seems moot at this point.
Edit 3: USIC, after further investigation, has confirmed the tablet was actually one lost in shipment and compensated for by insurance, the sale was legitimate (not a stolen device) and they unenrolled it from KNOX before I could ask if they would do so. So, overall a satisfactory outcome, even if the tech part of me wanted to find a way to defeat a technical challenge.
EDIT 2: The device may not be stolen after all, seller has given a plausible explanation. Withholding further judgement until more information comes in.
EDIT: I was originally thinking of 'USIC' as a subsystem of Android or KNOX. A user on Reddit suggested I reach out to the company USIC and see if the tablet was stolen from them. I did. It was. Will be getting the tablet back into their hands and pursuing a refund from the eBay seller. Will leave this post up in case anyone has a use for the technical rabbit hole I went down.
Backstory: Found a good deal on a new Galaxy Tab Active Pro from an IT liquidator company on eBay, it was listed as locked and price reduced because of that. I thought along the lines of 'hardware access is total access' and figured I would be able to wipe / reset it.
Device arrived today, the crippleware (MDM or administration software actually, but I'm feeling ornery at it) installed is Soti Mobicontrol. I can boot into the OS but a bunch of stuff is disabled. First I initiated a factory reset from Settings - it resets and during setup lists "This tablet is protected by Knox Cloud Service. To continue setup, connect to a Wi-Fi or mobile network." From there it states "Your admin can monitor and manage settings".... a bunch of stuff ending with "USIC will manage and monitor this device using the following app: MobiControl" with the only option being 'Accept & continue'.
Tried another factory reset through the boot menu (hold down vol down and power to reboot followed by hold down vol up) - same result.
Found and downloaded the same version firmware the tablet currently has: SM-T540_XAR_T540XXU2BTG5_fac.zip where XAR appears to be the US/Canada region code and T540XXU2BTG5 is the exact version of firmware the tablet currently has installed (verified by going to 'Software information' in settings).
Downloaded latest version of Odin (3.13), booted the tablet into the correct mode and flashed clean firmware (just the AP firmware) to the device. Went through first install sequence to no change in behavior, still installs Soti Mobicontrol as a device admin.
I've looked into maybe getting TWRP installed (so I can delete KNOX from TWRP file browser perhaps as demonstrated here:
) but as far as I can tell there isn't a build for this version of the tablet - closest I can get is for the SM-T547 XDA forum post on it here: https://forum.xda-developers.com/t/...alaxy-tab-active-pro-10-1-snapdragon.4284347/. Also not sure how I would get it installed since I can't enter dev options in the tablet (tapping on Build number, even in safe mode, results in a popup: Action not allowed This action is disabled by MobiControl. Contact your organization's administrator to learn more.)
I've found someone on YouTube (
) who removed the software just by intentionally entering a wrong password until a factory reset tripped - but I am already able to use the factory reset option and the software comes back. I'm thinking Soti Mobicontrol and the KNOX service are separate issues and in this person's example he was only dealing with Soti and not KNOX Enrollment.
Next I found this gentleman on Youtube:
who specifically mentions using the 'Nand erase' option in Odin along with flashing all files in the stock firmware to remove management software. Tried that, no luck. Same as each install I get the message 'Updating... Updating Knox Enrollment Service... X%' after being required to connect to wifi to continue setup with the 'Skip' option greyed out.
So, that's where I am right now with it, and I refuse to give up. Ideas?
@studentoflife don't know this device but might be a chance to flash the multiple part stock ROM you can get via Samfirm_reborn.
bmwdroid said:
@studentoflife don't know this device but might be a chance to flash the multiple part stock ROM you can get via Samfirm_reborn.
Click to expand...
Click to collapse
I am unfamiliar with Samfirm_reborn. What is this project? I can't seem to find much in the way of descriptive notes.
Edit: apologies, did some googling and now know what Samfirm_reborn is. I'm pretty sure I've already flashed all parts of the stock ROM - downloaded the T540XXU2BTG5 version firmware and flashed the BL, AP and CSC images. No CP image given this version of the device does not have a cellular modem.
Hm. I suddenly wonder what will happen if I reflash with the earliest version instead of the current one. I know I don't want to update it to the latest firmware in case that applies some security patch that can't be downgraded and locks out some workaround I haven't found yet, but downgrading... maybe.
I have a similar tablet with mobicontrol. I can't unlock OEM so all the methods of flashing new firmware I tried, failed. Have you had any luck since your last post?