Hey everyone,
I apologize if this has already been asked; did some searching but didn't really find much.
So I updated my samsung galaxy tab 8.9 wifi to ICS via Kies when the update was released sometime back, not thinking that it would prevent me from being able to root (I know, stupid of me). I always figured Samsung devices were developer friendly, and always had easy ways to root them.
I tried the root instructions posted in all the tutorial posts, and unfortunately they does not work for me (and I presume others). I get a "E:unknown volume for path [/sdcard]" error when trying to access "apply update from external storage" from recovery. I assume this is a change to the bootloader/recovery that Samsung made to prevent unauthorized access (aka, rooting), which is kind of a bummer if you ask me.
When googling for that I found a lot of stuff, but nothing that really told me the best course of action to take for this tablet. Should I hold out for someone to come up with a solution, or would it be best to revert back to 3.2 (if that is even possible), and then "install" the package I saw on the XDA developers front page that gets ICS on the tab with root access. Or is there something else I should do? I've found articles explaining some courses of action, but none explicitly related to the new ICS update that was just released (these were mostly articles referencing the prior 3.2 version).
I realize it was only recently since the update was provided, but any ideas/suggestions would be appreciated. I would like to have root again on ICS if possible!
Thanks.
Was answered several times, e.g. here
http://forum.xda-developers.com/showthread.php?p=31196953
zemoffm said:
Hey everyone,
I apologize if this has already been asked; did some searching but didn't really find much.
So I updated my samsung galaxy tab 8.9 wifi to ICS via Kies when the update was released sometime back, not thinking that it would prevent me from being able to root (I know, stupid of me). I always figured Samsung devices were developer friendly, and always had easy ways to root them.
I tried the root instructions posted in all the tutorial posts, and unfortunately they does not work for me (and I presume others). I get a "E:unknown volume for path [/sdcard]" error when trying to access "apply update from external storage" from recovery. I assume this is a change to the bootloader/recovery that Samsung made to prevent unauthorized access (aka, rooting), which is kind of a bummer if you ask me.
When googling for that I found a lot of stuff, but nothing that really told me the best course of action to take for this tablet. Should I hold out for someone to come up with a solution, or would it be best to revert back to 3.2 (if that is even possible), and then "install" the package I saw on the XDA developers front page that gets ICS on the tab with root access. Or is there something else I should do? I've found articles explaining some courses of action, but none explicitly related to the new ICS update that was just released (these were mostly articles referencing the prior 3.2 version).
I realize it was only recently since the update was provided, but any ideas/suggestions would be appreciated. I would like to have root again on ICS if possible!
Thanks.
Click to expand...
Click to collapse
Check this thread: http://forum.xda-developers.com/showthread.php?t=1406137
I just got mine rooted and I had the exact same issues as you. It's basically a broken root, as laid out in the OP of that thread I linked. See the How To section, subcategory Fixing Root.
Thanks,
I swear I did search, but apparently didn't know what key words to search for. I apologize for the duplicate post.
I have same issue and have thoroughly trawled the referenced threads. Can't access a root zip from recovery and can't flash a recovery from Odin. As a relative newb would really appreciate a step by step idiot's guide
alexbush said:
can't flash a recovery from Odin.
Click to expand...
Click to collapse
Why not? What goes wrong? What recovery file did you try this with?
Tried various versions of cwm. Odin simply freezes although it has a connection to com6. Stock recovery same issue.
Okay let me preface this post by saying, I did a good deal of research before I began this process, and was confident that I knew the steps sufficiently, and also the "plan B" recovery options.
Every video I watched on YouTube, every guide I found on various forums, and everyone I talked to made this process seem like cake. I have grown to disagree.
I am not a moron, nor am I incapable of following instructions. Every time I had a problem, I consulted with Google/YouTube/Forums, and researched how to fix it. I generally consider myself tech literate, but this is new to me. As such, I find it quite astonishing that, after so many years of development/home projects/general interest, there is NOT A SINGLE valuable 'getting started' guide. Granted, this is probably considered an advanced process, but even *nix development has more information than this FFS.
Anyway.
My task was simple; I wanted to update My GF's HTC One (m7spr) from 4.06xx to 4.4x. (Way overdue)
First things first; Settings -> About Phone -> Update -> Download it -> Install
Somehow this process got botched??? And the phone refused to accept 4.4, despite it being officially supported for several months.
Phone stuck at 4.06. Google had no information on failing to update, nothing relevant/useful anyway.
After dealing with that for 2 weeks, with zero progress, I decided to try the Root+Custom ROM process. That was, I believe, my only mistake.
The steps I followed, not necessarily in order*** :
-Install TWRP (so many problems with this, can't even find the words)
-Root phone (didn't work after multiple attempts, despite following directions perfectly, finally got it to work, and it didn't accomplish anything?!)
-Attempted to install SLIMkat ROM (took several attempts, finally got it running) This ROM was --no offense to the developer(s)--, for my purposes, disfunctional/broken, decided to attempt to rid myself of it
-Followed guides on YouTube to remove a ROM // flash stock
-Found several RUU's (all claimed to be valid, functioning and "simple solutions". None of which worked, and in every case, my device would 'lock' at the white screen/fastboot menu, and rebooting was a serious problem. During one failed attempt, my device would not reboot, causing me to be forced to let the battery drain before attempting again. (Hence the significance of removable batteries, but that's a whole other matter)
This is where it gets interesting
-SOMEHOW(???) "Chameleon OS" was attempting to be installed on the device. I had never heard of it, I had never seen it, I had no prior knowledge of it, I had not intentionally or even unintentionally collected this ROM, and surely did not have any intention of installing it. I wish to warn the community of potential maliciousness on the part of Chameleon OS. I did not give it permission to install, I was not even aware of its existance until the animated Chameleon came up, upon boot. I could not exit the install process, and it never finished booting. I had to simply let the battery die before I could re-enter the boot console/white screen. To be clear, I am not accusing the developers of anything malicious, I am simply pointing it out that this happened and the community should be aware of it.
Moving on.
-Using TWRP, I reset data, then factory reset the phone, then used the backup function, to boot into stock 4.06x Official.
-At this point, every time I restart the device, trying to enter TWRP, I can only access the white screen/fastboot menu -- I consider this to be progress, although it created a new problem; I am able to see the 4.4x update, and after it downloads, it asks me to restart the device so it can install. In doing so, it does NOT apply the update, however it stalls at the white screen/fastboot menu. I can reboot device and get back into Android, and the process repeats.
-
Allow me to sum up my current state;
-Device is fully functional within 4.06x, but for intents and purposes this is unacceptable
-Device can not be updated to newer version of Android, stuck at 4.06x
This process has been so long and drawn out, I am completely turned around with what problem requires what solution, and frankly I am exausted of trying to figure it out.
The real problem at hand is that the people who create guides/tutorials expect you to know certain things, and if you don't know certain things, they expect you to pause the video you're watching, go watch another video they made (irritating way to make your channel look like it has more traffic), and then resume what you were watching. As a first-time ROOTer, you're expected to pick up a ton of information that is not properly laid out in chronological order. Terms are not defined, and you're expected to just go with it.
This is why I did so much research beforehand. I was under the impression that the process was as simple as follows:
-ROOT device
-Install recovery option
-Create backup
-Install ROM
-Enjoy
Guides/forums/videos make it seem like a 10 minute proceedure. Lolnope. Going on several days of dealing with the current state. I waited so long to post because I was sure I was missing something, or messing it up. But I'm out of ideas now. :/
*** = Please understand that the process became frustratingly convoluted with various "I have B* problem, so I have to google the answer, which led me to learn about Y* treatment/process, and to complete Y* steps I needed Z* program, and to get Z* program I had to find Q* obscure information about my device, which requires me to go into BLUE* menu...and so on" ... it's irritating, to say the least.
I am frustrated, stuck and confused. The process is way more complex than the guides led on, and I have no idea what my next move should be. I'm humbly asking for help.
I would be more than glad to offer any non-personal information about my device's current state, in order to help you help me. Although as it stands I don't know what you need. Just ask. All I want to do is make the device COMPLETELY STOCK/FACTORY 4.4
Please forgive me if this post sounded ranty/salty. I'm honestly just tired of dealing with it, and I'm hoping to find some help from the people who know what they're doing.
Please and thank you.
Super_Annoyed said:
Okay let me preface this post by saying, I did a good deal of research before I began this process, and was confident that I knew the steps sufficiently, and also the "plan B" recovery options.
Every video I watched on YouTube, every guide I found on various forums, and everyone I talked to made this process seem like cake. I have grown to disagree.
I am not a moron, nor am I incapable of following instructions. Every time I had a problem, I consulted with Google/YouTube/Forums, and researched how to fix it. I generally consider myself tech literate, but this is new to me. As such, I find it quite astonishing that, after so many years of development/home projects/general interest, there is NOT A SINGLE valuable 'getting started' guide. Granted, this is probably considered an advanced process, but even *nix development has more information than this FFS.
Anyway.
My task was simple; I wanted to update My GF's HTC One (m7spr) from 4.06xx to 4.4x. (Way overdue)
First things first; Settings -> About Phone -> Update -> Download it -> Install
Somehow this process got botched??? And the phone refused to accept 4.4, despite it being officially supported for several months.
Phone stuck at 4.06. Google had no information on failing to update, nothing relevant/useful anyway.
After dealing with that for 2 weeks, with zero progress, I decided to try the Root+Custom ROM process. That was, I believe, my only mistake.
The steps I followed, not necessarily in order*** :
-Install TWRP (so many problems with this, can't even find the words)
-Root phone (didn't work after multiple attempts, despite following directions perfectly, finally got it to work, and it didn't accomplish anything?!)
-Attempted to install SLIMkat ROM (took several attempts, finally got it running) This ROM was --no offense to the developer(s)--, for my purposes, disfunctional/broken, decided to attempt to rid myself of it
-Followed guides on YouTube to remove a ROM // flash stock
-Found several RUU's (all claimed to be valid, functioning and "simple solutions". None of which worked, and in every case, my device would 'lock' at the white screen/fastboot menu, and rebooting was a serious problem. During one failed attempt, my device would not reboot, causing me to be forced to let the battery drain before attempting again. (Hence the significance of removable batteries, but that's a whole other matter)
This is where it gets interesting
-SOMEHOW(???) "Chameleon OS" was attempting to be installed on the device. I had never heard of it, I had never seen it, I had no prior knowledge of it, I had not intentionally or even unintentionally collected this ROM, and surely did not have any intention of installing it. I wish to warn the community of potential maliciousness on the part of Chameleon OS. I did not give it permission to install, I was not even aware of its existance until the animated Chameleon came up, upon boot. I could not exit the install process, and it never finished booting. I had to simply let the battery die before I could re-enter the boot console/white screen. To be clear, I am not accusing the developers of anything malicious, I am simply pointing it out that this happened and the community should be aware of it.
Moving on.
-Using TWRP, I reset data, then factory reset the phone, then used the backup function, to boot into stock 4.06x Official.
-At this point, every time I restart the device, trying to enter TWRP, I can only access the white screen/fastboot menu -- I consider this to be progress, although it created a new problem; I am able to see the 4.4x update, and after it downloads, it asks me to restart the device so it can install. In doing so, it does NOT apply the update, however it stalls at the white screen/fastboot menu. I can reboot device and get back into Android, and the process repeats.
-
Allow me to sum up my current state;
-Device is fully functional within 4.06x, but for intents and purposes this is unacceptable
-Device can not be updated to newer version of Android, stuck at 4.06x
This process has been so long and drawn out, I am completely turned around with what problem requires what solution, and frankly I am exausted of trying to figure it out.
The real problem at hand is that the people who create guides/tutorials expect you to know certain things, and if you don't know certain things, they expect you to pause the video you're watching, go watch another video they made (irritating way to make your channel look like it has more traffic), and then resume what you were watching. As a first-time ROOTer, you're expected to pick up a ton of information that is not properly laid out in chronological order. Terms are not defined, and you're expected to just go with it.
This is why I did so much research beforehand. I was under the impression that the process was as simple as follows:
-ROOT device
-Install recovery option
-Create backup
-Install ROM
-Enjoy
Guides/forums/videos make it seem like a 10 minute proceedure. Lolnope. Going on several days of dealing with the current state. I waited so long to post because I was sure I was missing something, or messing it up. But I'm out of ideas now. :/
*** = Please understand that the process became frustratingly convoluted with various "I have B* problem, so I have to google the answer, which led me to learn about Y* treatment/process, and to complete Y* steps I needed Z* program, and to get Z* program I had to find Q* obscure information about my device, which requires me to go into BLUE* menu...and so on" ... it's irritating, to say the least.
I am frustrated, stuck and confused. The process is way more complex than the guides led on, and I have no idea what my next move should be. I'm humbly asking for help.
I would be more than glad to offer any non-personal information about my device's current state, in order to help you help me. Although as it stands I don't know what you need. Just ask. All I want to do is make the device COMPLETELY STOCK/FACTORY 4.4
Please forgive me if this post sounded ranty/salty. I'm honestly just tired of dealing with it, and I'm hoping to find some help from the people who know what they're doing.
Please and thank you.
Click to expand...
Click to collapse
Did you try the latest RUU? No need to root etc...Just download the file, run the setup and you're good to go!
http://forum.xda-developers.com/showthread.php?t=2658910
Super_Annoyed said:
Okay let me preface this post by saying, I did a good deal of research before I began this process, and was confident that I knew the steps sufficiently, and also the "plan B" recovery options.
Every video I watched on YouTube, every guide I found on various forums, and everyone I talked to made this process seem like cake. I have grown to disagree.
I am not a moron, nor am I incapable of following instructions. Every time I had a problem, I consulted with Google/YouTube/Forums, and researched how to fix it. I generally consider myself tech literate, but this is new to me. As such, I find it quite astonishing that, after so many years of development/home projects/general interest, there is NOT A SINGLE valuable 'getting started' guide. Granted, this is probably considered an advanced process, but even *nix development has more information than this FFS.
Anyway.
My task was simple; I wanted to update My GF's HTC One (m7spr) from 4.06xx to 4.4x. (Way overdue)
First things first; Settings -> About Phone -> Update -> Download it -> Install
Somehow this process got botched??? And the phone refused to accept 4.4, despite it being officially supported for several months.
Phone stuck at 4.06. Google had no information on failing to update, nothing relevant/useful anyway.
After dealing with that for 2 weeks, with zero progress, I decided to try the Root+Custom ROM process. That was, I believe, my only mistake.
The steps I followed, not necessarily in order*** :
-Install TWRP (so many problems with this, can't even find the words)
-Root phone (didn't work after multiple attempts, despite following directions perfectly, finally got it to work, and it didn't accomplish anything?!)
-Attempted to install SLIMkat ROM (took several attempts, finally got it running) This ROM was --no offense to the developer(s)--, for my purposes, disfunctional/broken, decided to attempt to rid myself of it
-Followed guides on YouTube to remove a ROM // flash stock
-Found several RUU's (all claimed to be valid, functioning and "simple solutions". None of which worked, and in every case, my device would 'lock' at the white screen/fastboot menu, and rebooting was a serious problem. During one failed attempt, my device would not reboot, causing me to be forced to let the battery drain before attempting again. (Hence the significance of removable batteries, but that's a whole other matter)
This is where it gets interesting
-SOMEHOW(???) "Chameleon OS" was attempting to be installed on the device. I had never heard of it, I had never seen it, I had no prior knowledge of it, I had not intentionally or even unintentionally collected this ROM, and surely did not have any intention of installing it. I wish to warn the community of potential maliciousness on the part of Chameleon OS. I did not give it permission to install, I was not even aware of its existance until the animated Chameleon came up, upon boot. I could not exit the install process, and it never finished booting. I had to simply let the battery die before I could re-enter the boot console/white screen. To be clear, I am not accusing the developers of anything malicious, I am simply pointing it out that this happened and the community should be aware of it.
Moving on.
-Using TWRP, I reset data, then factory reset the phone, then used the backup function, to boot into stock 4.06x Official.
-At this point, every time I restart the device, trying to enter TWRP, I can only access the white screen/fastboot menu -- I consider this to be progress, although it created a new problem; I am able to see the 4.4x update, and after it downloads, it asks me to restart the device so it can install. In doing so, it does NOT apply the update, however it stalls at the white screen/fastboot menu. I can reboot device and get back into Android, and the process repeats.
-
Allow me to sum up my current state;
-Device is fully functional within 4.06x, but for intents and purposes this is unacceptable
-Device can not be updated to newer version of Android, stuck at 4.06x
This process has been so long and drawn out, I am completely turned around with what problem requires what solution, and frankly I am exausted of trying to figure it out.
The real problem at hand is that the people who create guides/tutorials expect you to know certain things, and if you don't know certain things, they expect you to pause the video you're watching, go watch another video they made (irritating way to make your channel look like it has more traffic), and then resume what you were watching. As a first-time ROOTer, you're expected to pick up a ton of information that is not properly laid out in chronological order. Terms are not defined, and you're expected to just go with it.
This is why I did so much research beforehand. I was under the impression that the process was as simple as follows:
-ROOT device
-Install recovery option
-Create backup
-Install ROM
-Enjoy
Guides/forums/videos make it seem like a 10 minute proceedure. Lolnope. Going on several days of dealing with the current state. I waited so long to post because I was sure I was missing something, or messing it up. But I'm out of ideas now. :/
*** = Please understand that the process became frustratingly convoluted with various "I have B* problem, so I have to google the answer, which led me to learn about Y* treatment/process, and to complete Y* steps I needed Z* program, and to get Z* program I had to find Q* obscure information about my device, which requires me to go into BLUE* menu...and so on" ... it's irritating, to say the least.
I am frustrated, stuck and confused. The process is way more complex than the guides led on, and I have no idea what my next move should be. I'm humbly asking for help.
I would be more than glad to offer any non-personal information about my device's current state, in order to help you help me. Although as it stands I don't know what you need. Just ask. All I want to do is make the device COMPLETELY STOCK/FACTORY 4.4
Please forgive me if this post sounded ranty/salty. I'm honestly just tired of dealing with it, and I'm hoping to find some help from the people who know what they're doing.
Please and thank you.
Click to expand...
Click to collapse
if you are s-on you need to relock your bootloader, you also need to flash stock recovery for the ruu you are using, also if ypu are s-on you'll need the latest ruu, will not let you downgrade,
Muchas gracias amigos
indy1811 said:
Did you try the latest RUU? No need to root etc...Just download the file, run the setup and you're good to go!
http://forum.xda-developers.com/showthread.php?t=2658910
Click to expand...
Click to collapse
Aldo101t said:
if you are s-on you need to relock your bootloader, you also need to flash stock recovery for the ruu you are using, also if ypu are s-on you'll need the latest ruu, will not let you downgrade,
Click to expand...
Click to collapse
I greatly appreciate the responses.
I will try both and report back.
Super_Annoyed said:
I greatly appreciate the responses.
I will try both and report back.
Click to expand...
Click to collapse
LOG:
-RUU listed above was successful, booted into 4.06.651.4
-Attempting to update to 4.06.651.9
-Update unsuccessful, upon reboot, still 4.06.651.4, no error message
-Attempting to update to 4.06.651.9 again
-Update successful
-Attempting to update to 5.03.651.3
-Update successful (THANK YOU!)
Oh wow, such a huge relief. I feel a bit dumb having been so close to the actual solution, lol.
I would like to extend a huge helping of gratitude to both users indy181 AND Aldo101t.
Yall really knew what my problem was and how to fix it, so yall both have my gratitude.
I guess in my frustration I misunderstood the purpose of the RUU files, and ignored the version labels.
To a frustrated noob, the filename "1_29_651_10" has no real meaning. I suppose my research failed at this critical point.
It doesn't explain why the device failed to update in the first place, but since it's all set now it makes no difference.
Thanks so much, fellas!
worked like a charm)
Just a quick comment:
I didn't see any mention of HTC Dev unlock. Did you do that?
Did u ever get any offers from any publishers? Haha holy cow that was a long post! Glad u got straightened out!
Sent from my Nexus 7 using Tapatalk
Note: Relevant device info will be provided below.
Dear techwizards and wannabe,
I've been trying to root my phone for a while, I've done it before: both my S II and S III were international variants, and rooting those devices was very simple. But after getting an S IV from America and consensually downloading a samsung issued update -- I had yet to read up on the disadvantages of knox -- my rooting and android experience took a turn for the worse.
Long story short -- I know developers are a proud bunch who value their time -- I tried rooting my phone yesterday after almost smashing my phone on a coffee table. They say it's a well known side effect of Touchwiz, but I'll leave that to you.
I used a towelroot.com root -- a wonderful tool, if I may say so. After that, I visited the CM website and picked out the compatible CM11. I never got to flashing it though, as my problems arose while installing a recovery.
I had downloaded an app, a something recovery or another. They had an option to flash recoveries on there--it would download your recovery for you and do all the work, which seemed plausible as most video tutorials demonstrated. To my astonishment, doing so bricked my phone.
I tracked back, looked for the samsung stock rom, downloaded all 2.2 gb's of it and flashed it. It worked. My phone was functional but I suspect something within it stinks. My device, apparently for security reasons, wont let my wifi or 4g to establish a connection. It's making it impossible for me to fix this problem as I can't root my device or flash a custom rom.
About Device:
Pre problem I was running a:
SGH-I337UCUFNC1 baseband. Build Number ending with: NC1.
Android version: 4.2.2
Post problem:
Baseband: I337UCUFNC1
Build Number: JSS15J.I337UCUEMK2
Android version 4.3.
If I could find my original stock 4.2.2 NC1 version and get simple instructions on how to re-install it back to stock version, I'd be very grateful.
If you know how I could fix the internet issue on the MK2 one, and provide some simple instructions of how to root it, I'd be grateful too.
If you think neither would work, and have something else in mind, Im open to your suggestions.
Much Regards,
Y
androidshmandroid said:
Note: Relevant device info will be provided below.
Dear techwizards and wannabe,
I've been trying to root my phone for a while, I've done it before: both my S II and S III were international variants, and rooting those devices was very simple. But after getting an S IV from America and consensually downloading a samsung issued update -- I had yet to read up on the disadvantages of knox -- my rooting and android experience took a turn for the worse.
Long story short -- I know developers are a proud bunch who value their time -- I tried rooting my phone yesterday after almost smashing my phone on a coffee table. They say it's a well known side effect of Touchwiz, but I'll leave that to you.
I used a towelroot.com root -- a wonderful tool, if I may say so. After that, I visited the CM website and picked out the compatible CM11. I never got to flashing it though, as my problems arose while installing a recovery.
I had downloaded an app, a something recovery or another. They had an option to flash recoveries on there--it would download your recovery for you and do all the work, which seemed plausible as most video tutorials demonstrated. To my astonishment, doing so bricked my phone.
I tracked back, looked for the samsung stock rom, downloaded all 2.2 gb's of it and flashed it. It worked. My phone was functional but I suspect something within it stinks. My device, apparently for security reasons, wont let my wifi or 4g to establish a connection. It's making it impossible for me to fix this problem as I can't root my device or flash a custom rom.
About Device:
Pre problem I was running a:
SGH-I337UCUFNC1 baseband. Build Number ending with: NC1.
Android version: 4.2.2
Post problem:
Baseband: I337UCUFNC1
Build Number: JSS15J.I337UCUEMK2
Android version 4.3.
If I could find my original stock 4.2.2 NC1 version and get simple instructions on how to re-install it back to stock version, I'd be very grateful.
If you know how I could fix the internet issue on the MK2 one, and provide some simple instructions of how to root it, I'd be grateful too.
If you think neither would work, and have something else in mind, Im open to your suggestions.
Much Regards,
Y
Click to expand...
Click to collapse
Two things:
1. You're posting in the wrong forum, this is the forum for the S4 Active i537, a different phone than the regular S4 i337.
2. The i337 had a locked bootloader that cannot be unlocked. Therefore it is impossible to install a custom recovery other than SafeStrap and it is impossible to install ROMs that are not TouchWiz-based ROMs.
Good luck.
Hi all,
I have been hammering away at this one, and putting it on the back-burner, but now, it is really getting to me. Samsung Galaxy Tab Pro 10.1 SM-T520
It has been rooted with ODIN, and shows no problem, (things seem much easier now, as I have re-jigged lots of my old phones using so many more tools, I am not an expert, but can read and search without too much problems) I was very careful to choose the correct file, CF-Auto-Root-picassowifi-picassowifixx-smt520.zip, I have rechecked this step several times, as most of the instructions I found ODIN device ID:COM box should become yellow, when on newer versions it is blue I think, I wondered if I was going mad,
Root Checker Root access granted, all fine. I have Root access. n.
Installed CWM ,latest recovery for a Pro 10.1 wifi, recovery 6.0.3.1 Titanium backup-ed, all ready to go and Reboot and flash a new ROM.. No joy. .. Installed TWRP , same.
When it re-starts it ,shows the galaxy logo, flashes off, then back on, and then fails. Android dead with a red warning , standard recovery KOT49H.T520XXUANAE, all I can do is the usual options:apply update. The only thing I haven't tried is to just wipe all the data. I have a backup of my apps with Titanium Backup on the SD card,I am not that bothered really about much other data if its a pain. I just want control of my device and to try a new ,cleaner ROM(SMT520_GraveD_V3.0)
This has been bothering me for ages, I have read so many posts so am now getting really frustrated I have bought triangle away app. today although I think I sorted that issue early on anyway , but just in case...
Super SU seemed to have vanished so that is back installed
I think I searched and found the Mount/system issue and looked into an issue that lead me to the .system folder, but it is hidden, so I could not find the file it related to. I dont have the specifics to hand as I checked it out at work. I wondered if it is because I have ES file manager, not ASTRO as it said in some of the posts I found.but sure this is a red herring.
I have tried everything..I have a Mac at home and PC at work, I have tried ADB and can see &restart the device etc... so I am connected, first I got the error that it didn't recognise the sideload command. Read up on ADB , looked at the help etc. sideload isn't there as a command, very confusing. But I think I got there one I figured out paths, as of course they are different on a Mac, and possibly more so as I have 2 drives in it, which often confuses me ..grr.
I can of course get into the bootloader, with ON+VOL -, it tells me so far the system is : Official and Knox Warranty Void: 1 which I think is fine, but a chap at work suspected this, but after lots of threads I gather this is normal..
Sorry if long, just thought I should be as clear as possible. I have not really come across such an awkward issue as this , my HTC One was a breeze:crying:
*edit* Just worked out through trial and error, that to use the sideboot command I had to select send via ADB and now with the path /Desktop/SMT520_GraveD_V3.0.zip I was able to send the file but with the following messgae : E:footer is wrong and E:signature verification failed, twice.. So some progress
Thanks !
Just to say after being up waay too long on this, I discovered there is a newer firmware T520XXUANI1_T520BTUANI1_BTU which I may aswell upgrade to first, but of course I cannot do this OTA now As it recognises the device is 'tampered with' *sigh* so gun and games with Odin for Mac tonight, or JODIN3 , just to get the firmware upgrade(which seems to be a jungle of fake download links). before a Rom without bloatware..
I am also not completely clear why, as from another thread about KNOX, as I am basically running stock , without custom recovery.. According to this thread , but I am getting a bit confused now
http://forum.xda-developers.com/gal...neral/knox-warranty-void1-otas-t2996067/page2
Click to expand...
Click to collapse
however this is another story from the ROM install. Apologies
Well. No replies, but I did eventually solve this. Hopefully this can help someone. I am a tinkerer, but I really nearly gave up on this..But this was a cheap second hand tablet ( my first) and I want to see what it can do before I test drive one on my mother who is having nightmares with every Windows laptop I give her!
Once I got to a PC , I had access to Odin3, although it is not available online (apparently to Mac) I could not get it to work due to Java issues (JOdin3 online - brilliant idea but no joy for me so far)
I had the Rom I wanted ( GraveDigger- SMT520_GraveD_V3.0.zip ), the firmware update (T520XXUAOD2_T520BTUAOB1_BTU.zip(i think)) and the unlock file (CF-Auto-Root-picassowifi-picassowifixx-smt520.zip) , non of which I could install in any way , due to being locked out of using a custom Rom bootloader!
At this point I factory reset and cleared the cache( as that is the only options in the basic bootloader!) I also has ADB on the PC so attempted to install the files this way (after messing about using some software to produce the .tar and .md5 files needed for Odin. I tried everything to get this into proper 'bootloader mode' all from scrach again, including trying the adb oem unlockbootloader command, which I would never get to work as I could not get there!
With Odin, I was also again able to flash the firmware update, eventually, and of course had to unlock again. I was curious if I could now use the OTA update, and could not. At some point, in repeating this process( as I think it hung up several times and needed a hard reboot) I had at this point fully wiped the device as I know that is another reason to have glitches and an unstable ROM later.
I think I then tried to check and although T520XXUAOD2 seems to still be the firmware, at some point I managed to get online ( I think some superuser app which I have had to try several may have notified me that KNOX was reset:laugh:When I go to About>Software update it said I had the latest update! Good news!
At this point I had installed both CWM and TWRP again , and thought I would try TWRP.I had tried CWM and the same problem, like a double flash of the Samsung Logo , so I know it had reset !!
THIS TIME I used TWRP ( I thought of trying CWM touch, but its either paid, or I would have to find and ABD the file over I guess) , I managed to re-apply the Root file, Root checker confirmed this , as it had throughout this ordeal!, although apart from ACCESS GRANTED I dont really know what the rest means..Anyway although picassowifi , was still in Device name on TWRP I chose an earlier recovery version to install.- twp-2.7.0.0-picassowifi.img. When I re-booted, I was able to get the TWRP recover image, and install the ROM, I cannot remember if I re-rooted as I was so elated.
I had a few , freezing moments, reinstalling most of my apps through Titanium Backup, I think I just tried to reinstall everything which of was unnecessary, after a hard reset, all seems fine. I checked and the TWRP recovery seems to have stuck. I am not entirely sure how to check about the firmware , but for now I feel this is progress.
Good Luck if anyone found this any use.
Just to add, when you search this ( and probably many other models) you seem to get so many sites, offering exactly the same unlock information, in exactly the same way, many of the downloads seem to take you to many weird and wonderful places. So I tended to look here for downloads if possible. But I had to join SamMobile (which seems a useful site for the firmware upgrade) and trawl all over and assume similarities between other Samsung devices to fully check I was not being an idiot. But this was very odd and I could not find any posts or other workarounds that I did not try. But this new ROM feels lovely and smooth so far, and I now want to look into this tablet further