First of all, I apologise if I have posted this in the wrong section. Secondly, please be aware right now that the device in question is the S3 4G VERSION. Very different to the vanilla S3. I have dabled in rooting/flashing and general messing around with android firmwares before so I have a mild understanding but please be patient
Now the problem: Rooting. It shouldn't be hard. Should it? Not with tools like chainfires auto rooting kit these days... Alas, CF's auto root isn't doing it for me. At first I was having dramas with KNOX (congrats on loosing a long time customer there samsung). After i got rid of that with the de-samsungizer kit flashed through CWM it stopped showing the stupid "an application has attempted to gain root access and was blocked" crap. However SuperSu continued to crash, I'm assuming because the root was not properly completed. NO error codes or anything are ever returned from Odin, or CWM, everything looks like its happy but just not rooting. Confirmed with rootchecker.
Now a couple of other things I should mention: CWM keeps getting erased or something aswell? Like I'll turn the phone off to go into recovery mode, and im sitting at the bone stock one again, with the little red exclamation mark over my poor android corpse D:
I even tried disabling auto-reboot in ODIN when flashing CF's auto root, droppping the battery and manually starting recovery mode. I get excited when I see the red pirate-droid executing instructions, all goes well, everything is happy, still no root -_-
EDIT: In download mode, knox still exists and has logged EVERY attempt i've made. so everything is definitely executing just fine...
This is also my first time rooting in the presence of KNOX
I don't know what else to do... Am I missing something? is there a glaringly obvious thread or bit of information I've missed?
Thank you in advance for any help provided.
Ok so I took a break from this for a while cos i got really busy and didn't fancy doing MORE work on my phone when i finally got a spare tic. However, I came back to it today and managed to find a magic combination.
I AM NOT RESPONSIBLE FOR BRICKING YOUR DEVICE, PLEASE FEEL FREE TO CRY IN A PM ABOUT IT THOUGH I COULD DO WITH A LAUGH.
The following is a guide for anyone having issues making the root stick on their GT-i9305 samsung galaxy s3 4G/LTE on android 4.3. DO NOT ATTEMPT THIS ON ANY OTHER OS VERSION, VARIANT OR DEVICE.
I noticed a particularly important piece of information in the following link: How to Fix Android 4.3 Jelly Bean Rooting Problem for Galaxy S3/S4/Note 2/3 - W0lfDroid
A superSu update. So i went there grabbed that package ( SuperSU Download for update package ) and started my grand master plan. If you would like to actually read what hte user said yourself, its in a quote bubble naer the bottom, just before the comments.
now. Using an important piece of information in a thread I cannot, for the life of me, find through my browser history (apologies) I grabbed a copy of pihlz touch which you can find in the following thread: [CWM][PhilZ Touch][GT-I9305] 4.00-b21 Touch … | Samsung Galaxy S III I9300, I9305 | XDA Forums
Now. grab yo-self a copy of busybox's supersu root How to root Galaxy S3 I9305 with SuperSU 1.02 - Samsung Update located on that page. Make a folder on both your phone's internal storage and external, name them both the same thing and something you will remember. For instanceI called mine Root stuff. I only do folders on each of them in case I can't extract from external for whatever reason, its not necessary. Put both the supersu update you downloaded earlier and the one you just downloaded from above, busyboxes root, into both of these folders if you did it my way.
To avoid having to reboot your phone an extra time, make sure you did the above step BEFORE moving on
First up, I flashed philz touch with Odin (ensure you have the latest version, use your PDA checkbox and be sure that auto reboot and F. reset time are checked). Next up, turn your phone off and boot into your magnificent (no seriously, this is amazing. Its like a GUI in todays BIOS's...) new CWM recovery mode. Go into advanced and hit reset permissions or something like that... My phone is downstairs atm and I CBF in going and getting it and rebooting. Note that I am unsure if this is actually an essential part of the process, this is something I did because I worried about the permissions on the phone after my, by KNOX's count, 15 attempted flash operations -_- More like freaking 20 thousand....
Now once you have done that, go back to the main menu and tap install zips. FIRST you select the actual root, supersu1.02 busybox. Next, select the extra zip file option and que the UPDATE supersu-v2.02 after the actual root package. Once you have done this, swipe to install. THESE TWO PACKAGES MUST BE IN ORDER!!!!
Thats all I did. My phone rebooted and I was able to use Root checker to conform the root, allowed access to supersu and no crashing. Finally. THat was way too hard.
Thank you for hosting the website gentlemen/ladies where we can all come and share knowledge.
all credits go to anyone/webpage I linked people to and the brilliant programmers that made the packages. And finally, a HUGE thanks to Google and Linux (from which android is based) for freeing us from the shackles of iOS.
Related
so i have the i777 and i rooted using a guide on the android central forum
basically i downloaded kies, odin, cwm, and superoneclick
i put the cwm.tar file through odin, and than ran superoneclick, and i was rooted pretty easily
i than downloaded rom manager and through there i flashed CWM. I tried to make a back up using rom manager but that failed, no biggie i hear other people have the same problem. I boot up into CWM using rom manager and it says stuff like "failed to verify whole file signature"
im not sure if this means i rooted incorrectly?
i made a back up just fine using CWM. However i found out this stuff about flash increments and how i flashed a custom CWM kernal or something (sorry my definitions in this subject are still noob)
i decided i want to get rid of the yellow triangle + i9100 message every boot, no biggie but i am here to learn and i figure might as well if i can. I read a couple threads here and im not sure if this is my answer but i think it is please advise
my plan is to go back completely as if i never rooted and than root by using a stock rom/kernal so i dont get the error triangle message as well as the incorrect international i9100 display
i think this is my solution
"2b.) How to root by flashing Entropy512's Return/Unbrick to Stock, Kernel + Rooted System Package from the command line using Heimdall (Linux and Mac OS)
* Tested on Linux, should work on Mac OS
* Download and install the latest version of Heimdall Command Line for your operating system from here. (Latest version 1.3.1 at this writing.)
* Download Entropy512's Return/Unbrick to Stock, Kernel + Rooted System Package from here. Extract the PDA.tar file from this package to a directory on your hard disk drive, then extract the two component files from the tar - zImage and factoryfs.img.
* Place zImage and factoryfs.img both in the directory where you have the Heimdall command line executable, and enter the following at the command prompt:
Code:
heimdall flash --kernel zImage --factoryfs factoryfs.img
* Reboot the phone. Success. You're Rooted.
"
i am under the impression that if i flash the .tar file that is 200+mb (why so big) that i will be RE ROOTED and COMPLETELY stock, therefore no error message and no international thing popping up
also, no more flash counter increments ? << this one is also important as this is one major reason i want to re root
im not really sure but i think that by flashing this new .tar it will over ride my custom.tar file that i do not want any more, i dont know how to get rid of it so this is the only thing i can think of
im worried because i dont know if i have to UNROOT before i install entropys thing or if it will just over ride
thanks so much to any one who can give me advice
Really the best instructions are in creepncrawly's write up on how to return to stock. It covers any question you could have:
http://forum.xda-developers.com/showthread.php?t=1313659
And for doing it right:
http://forum.xda-developers.com/showthread.php?t=1311081
Plus new tools:
http://forum.xda-developers.com/showthread.php?t=1367319
The write ups he does are top notch and should be mandatory reading for first time visitors.
The file is so big because it contains the entire android os.
The issues you're having in cwm sound like clockworkmod needs to be reflashed.
The triangle will be removed simply by the stock kernel being replaced. The flash counter as of now can only be reset by a usb jig ~ less than $10.
Though a few have reported returning the phone for warranty issues and they did not check the flash counter.
The only way the flash counter is tripped is by using pc Odin to flash a non stock kernel.
Sent from my páhhōniē
ok thanks for the help, tomorow im gona read the links you posted thoroughly but i was wondering
if i flash a stock kernal, than how am i rooted
i am not even really sure what "roots" my phone but i thought that it was installing CWM because its a recovery tool which allows more options "superuser"
thanks again! cant wait to waste all day tom reading more about rooting
DroidBehavior said:
ok thanks for the help, tomorow im gona read the links you posted thoroughly but i was wondering
if i flash a stock kernal, than how am i rooted
i am not even really sure what "roots" my phone but i thought that it was installing CWM because its a recovery tool which allows more options "superuser"
thanks again! cant wait to waste all day tom reading more about rooting
Click to expand...
Click to collapse
There's a stock plus root package. One of the best ways to root in my opinion.
Root means installing SuperUser.apk, su, and busybox. That's it. The stock + root package has those already included, but also gives you the bone stock kernel.
You install a custom kernel to, among other things, get ClockworkMod Recovery.
DroidBehavior said:
ok thanks for the help, tomorow im gona read the links you posted thoroughly but i was wondering
if i flash a stock kernal, than how am i rooted
i am not even really sure what "roots" my phone but i thought that it was installing CWM because its a recovery tool which allows more options "superuser"
thanks again! cant wait to waste all day tom reading more about rooting
Click to expand...
Click to collapse
in reality, 'rooting' your phone is nothing more than placing 2 files on the /system (only one is really needed, since you can download Superuser from the market)
what happens is this:
android version release (say 2.3.5)
extremely smart people find way to exploit a memory hole in the OS, and create a 'rooting' method. what this method does is exploit that hole, which allows for a 'temp root' while it injects the needed files for root
needed files for root:
/system/bin/su <- this is the binary that allows you to retain root access
/system/app/Superuser.apk
without root access, /system is a read-only partition. utilizing the exploit, it will create temp root, then remount the /system partition as read/write, allowing your rooting tool to inject the required files into /system
rooting actually has nothing to do with the device at a true hardware level. it is all within the OS itself. anything outside the OS (recovery, boot, bootloaders, etc) dont get 'rooted' because root is only access to the /system within the OS
samsungs have this awesome ability to be easily rooted via CWM. its extremely easy with ODIN or heimdall to flash recovery/new kernel with recovery built in, and use a cwm zip file to inject the needed files into /system rather than relying on an exploit to do it for you.
its a common misconception that i hate to see when people associate rooting with access to anything outside the OS itself.
'i am having problems flashing this rom/kernel/mod in cwm'
'are you sure you are rooted? try re-rooting'
asinine logic...to say the least
^^
That needs to be stickied in every android forum on xda.
Sent from my páhhōniē
ok im back, i read a lot of the guides n a lot of pages and i successfully rooted using entropys 2a method return to stock + root
now i have a 2-3 second delay in my home button, and an additional 1 second delay when i turn my phone ion with the power button to show my display
i also added CWM by using the android terminal and that worked
but im regretting all this because of the delay, my error message is gone so thats good but now i have a delay
what could be the problem? i dont remember any one mentioning this issue and if im the only one than i dont know what to do, also i noticed the flash counter is still at 1 so i know i did everything right
DroidBehavior said:
ok im back, i read a lot of the guides n a lot of pages and i successfully rooted using entropys 2a method return to stock + root
now i have a 2-3 second delay in my home button, and an additional 1 second delay when i turn my phone ion with the power button to show my display
i also added CWM by using the android terminal and that worked
but im regretting all this because of the delay, my error message is gone so thats good but now i have a delay
what could be the problem? i dont remember any one mentioning this issue and if im the only one than i dont know what to do, also i noticed the flash counter is still at 1 so i know i did everything right
Click to expand...
Click to collapse
Sounds like you still have reading to do. And kudos to you for taking what they said as constructive criticism.
The flash counter can only be reset by a usb jig. Mobile Tech videos make some very good quality ones.
The delay from the home button is due to the vlingo app shortcut being tied to the home button (double tap home button) so it's waiting to see if you hit it twice before it takes you to the home screen. Cusom roms remove the vlingo app from being there which helps cut down on the delay.
But you may notice it more since what you did. And you should. By adding cwm you likely flashed Entropy512's kernel. Which is an awesome kernel. One of the ways that kernel helps battery life is by setting the cpu govener to conservative. It slows the cpu from jumping too high too quick. That explains why you may have not noticed the delay before you did anything. As well as the delay from unlocking the phone.
For me the extra battery life is worth it. If you don't like the delay one of the easier ways to set it back to ondemand (stock) is to use the app SetCpu:
https://market.android.com/details?id=com.mhuang.overclocking&hl=en
Hope that explains everything.
Sent from my páhhōniē
yeah that makes perfect sense thanks for the explanation
right now i installed miui and i ****ing love it! the interface is so smooth and sexy its like iphone spliced with android
minimalistic ftw
the interface was so much smoother i ran quadrant but the score was the same heh, but still its impressively smooth
I have solved this problem I think last night by updating to XXEMB1 on Kies last night - I have of course lost root for the moment but will get back to that later when I have more time
I have an international galaxy gt19300
It had begun to restart itself a few times a day and then would run for days with no issues
I eventually decided to root it when I found the new toolkit on here which seemed to work a treat
I now had superuser installaed titanium back up and ROM Toolboxand paid for pro versions of this and toolkit
to be honest apart from doing one back up using the toolkit the only other thing I did was to disable the auto scanning on start up to speed up booting the phone. A day or two after this the problems started again but this time with it no rebooting but just freezing. Eventually I took out the sd card as I remembered I had an sd card problem with my old S2 - though this is a new samsung sd card. At first I thought that was it but then a bit later it froze while i was browsing the app store and has done so periodically, though today it ran all day without freezing onvce. Then suddenly it froze again for no reason - I was just swithcing screens and it froze part way through the process
As far as I can see I have three options
1) Flash a new ROM (for the moment I am still using the stock rom having only just rooted it using Toolkit.exe from here) but not sure which one I should use so need reccommendations
2) Use the toolkit to download a stock odin flashable rom (but dont I have this already?) and then 3 reset the flash counter using triangle away (seems risky to me) install the stock rom , undo root (if necessary) and then return the phone to Samsung
3) go to Kies and install the latest update in the hope that the problem will go away - though if S User pro doesnt manage to keep root I wiill presumably have to re-root all over again.
What attracted me to S3 Toolkit was that it packaged up all sorts of options into one easy package - on the other hand this may have made me a little over confident with rooting. If I hadnt rooted it the earlier problem, though not as bad, would still have been there but I could easily have sent it back to Amazon UK or Samsung UK for repair and replacement.
My biggest worry at the moment is that whichever process I go for - or even a third option suggested here - there must be a risk that the phone might lock up during flashing or upgrade - probably not likely as it didnt when I restored the back up I had done (didnt help either) and the touch wiz ui wont be running
Anyway would really appreciate some help guys - even if it is only what you would do in the same circumstances. I guess I should have tried to have the problem fixed but earlier I put that down to maybe having too many apps and crapware and thougth rooting would help me solve it. I have unintstalled every app that I dont regularly use but it is still happening
gbswales said:
...
Click to expand...
Click to collapse
First of all you have to be aware of the fact that rooting & flashing ROMs is always a risk, toolkit or not.
The safest way is to stay un-rooted stock if you do not know why you need root in the first place. If you know you need root, and actually also before, read the guides & information in the stickies under the General section as they explain you in detail how to root, un-root, use triangle away etc.
As for your situation, I would try to 1) flash another kernel than the stock one, if this does not work, 2) flash the most up-to-date stock ROM (you can get it here on XDA or sammobile.com) via Odin or Mobile Odin, not the toolkit (Odin is as simple as the toolkit if you follow the how-to), if this also does not work 3) try a custom rom, and if it also does not work 4) return back to stock and give it to Samsung service centre.
I wish you good luck!
Thanks for your advice
chrismast said:
First of all you have to be aware of the fact that rooting & flashing ROMs is always a risk, toolkit or not.
The safest way is to stay un-rooted stock if you do not know why you need root in the first place. If you know you need root, and actually also before, read the guides & information in the stickies under the General section as they explain you in detail how to root, un-root, use triangle away etc.
As for your situation, I would try to 1) flash another kernel than the stock one, if this does not work, 2) flash the most up-to-date stock ROM (you can get it here on XDA or sammobile.com) via Odin or Mobile Odin, not the toolkit (Odin is as simple as the toolkit if you follow the how-to), if this also does not work 3) try a custom rom, and if it also does not work 4) return back to stock and give it to Samsung service centre.
I wish you good luck!
Click to expand...
Click to collapse
Firstly the good news is that it turned out to be a problem with the last XXELLA upgrade - I found a new one on KIES ran the update and it is fine
Of course I lost root access but expected that anyway.
I do enjoy tinkering with Systems and although I know my way around Windows I have not tried with Android until now - this is my second Galaxy so was naturally wary of bricking it if I rooted. Christmas time I bought myself a galaxy tab 2 10.1 with the express aim of rooting it and was prepared to take the risk - after a few false starts I got it rooted fine - was still wary of the phone but once the kit came out the benefit that has for me is the way you have to check things step by step systematically as you do things - my problem with doing stuff from instructions on line is that I find it is all to easy to skip a step (which I did with the tab first time around) Also with it being a system I haven't explored before I like having a step by step approach which is the same way that I learned DOS way back in time.
I do want to try some different ROMs on it to see what they offer and I would really have liked to have got some apps running from my external SD card and I also like having a complete image back up (as I have for Windows 8) so that in the event of a serious issue it is easy to wipe all and restore from new (I keep several images which I make on a weekly basis so that I don't have to re-install everything.
I confess to playing with computers and devices as a hobby - evidence of this was the 350 apps I had installed before I started purging them in case that was the cause of the problem. I pretty nearly try every new app I find just to see what it does and so there being a whole range of apps that I couldn't install without root access upset me. I am not going to rush to root again and will at least wait until the current version has been on the phone a while - just to make sure the XXEMB1 version is stable now - it has a lot of new admin features to keep me amused for a while!
Two things that disappointed me about root were that it looked as if I couldn't overclock the device to improve speed - the main CPU bar was already on max (though I didn't have time to explore more than that) and that it still seemed pretty hard , if possible at all on the hardware, to run apps from the external SD card -- as I do now with windows (using a smaller SSD ) I will have to be a bit more prudent about uninstalling the apps I find I don't really use.
I guess deep down the main reason why I want root is I don't like any manufacturer telling me what I can and cannot do with the device I paid for - one thing I did try was installing Linux but that didn't quite get finished before I lost root access.
Your advice however is very sound for people who don't like or enjoy tinkering or taking risks and I don't think I would recommend any normal phone user to root their device.
Thanks again
Just to add quickly....to overclock you need to flash a kernel that supports it.....And know what you are doing before doing it
How can I update to the latest 2.1.27 update on my Nabi 2? The Nabi is rooted and has TWRP as the recovery. Any help would be good! I have tried to flash a couple different Nabi 2 roms and they all fail. Thanks
toby1978 said:
How can I update to the latest 2.1.27 update on my Nabi 2? The Nabi is rooted and has TWRP as the recovery. Any help would be good! I have tried to flash a couple different Nabi 2 roms and they all fail. Thanks
Click to expand...
Click to collapse
I've got the same question. I know I'm an idiot that shouldn't have installed Gapps without having a clue, but unfortunately I did. I used the Victoria Antonio youtube video that says it does not root but does install Gapps about 4 months ago--May 2013. I'm now trying to figure out how to get the OTA update to 2.1, but I'm just lost, since it's been a while. I tried fooling around in TWRP, but again, didn't have any luck. Then idiotic me touched the square button in the upper right hand side of TWRP, and it is now stuck after saying:
*Verifying filesystem. . .
*Verifying partition sizes. . .
I know this is my own fault and I apologize, but I would really appreciate some help! Thanks so very much!
abbienormal said:
Then idiotic me touched the square button in the upper right hand side of TWRP, and it is now stuck after saying:
*Verifying filesystem. . .
*Verifying partition sizes. . .
I know this is my own fault and I apologize, but I would really appreciate some help! Thanks so very much!
Click to expand...
Click to collapse
That's just the log. You didn't do anything bad. Next time just press the button again and it will hide the log.
For both of you we need some more info, what have you tried so far? What methods and files are you trying to use to get to 2.1.27?
Thanks and sorry!
aicjofs said:
That's just the log. You didn't do anything bad. Next time just press the button again and it will hide the log.
For both of you we need some more info, what have you tried so far? What methods and files are you trying to use to get to 2.1.27?
Click to expand...
Click to collapse
Thanks so much for the reassurance. I did actually try to push the button aagin, but it wouldn't do anything, and after thinking I had bricked it for about a hour, I finally held down the volume -/+ and power buttons and got back to familiar territory. Sorry, again, for the completely idiotic question.
I haven't tried anything besides the standard order of operations suggested by Nabi. I downloaded the Nabi OTA software update (which took forever with our pokey internet), then clicked okay as it verified things, then it automatically rebooted with the little green Android guy with his chest open, then, unexpectedly, he's on his back dead with a red triangle sign above his chest. The tablet reboots by itself normally, and there are no changes from what I had before--none of the OTA update has taken effect. And, as a matter of fact, when I check for an update, again, (because it's still at the 2.0 release keys), low-and-behold, it detects an update and wants to download again.
I went through the process 4 times before giving up and checking with the Nabi support on FB. After troubleshooting a couple of things, they wanted to know if my Nabi 2 had ever been rooted. I shut-up then because I didn't want to be scolded, and because, of course, it's no longer under warranty if it's been rooted.
However, I got it second-hand, so I've got no warranty anyway, plus, according to the Victoria Antonio youtube video I followed, I didn't actually root it. With the teensy bit of knowledge I've got now, I'm kinda skeptical of that particular claim, but nevertheless, I still can't get it to update with the fancy new Nabi software, which I've been lusting after.
Any ideas? Obviously I'm clueless about tech lingo, so I would greatly appreciate a very simple explanation. Thanks so much for your time!!
abbienormal said:
Thanks so much for the reassurance. I did actually try to push the button aagin, but it wouldn't do anything, and after thinking I had bricked it for about a hour, I finally held down the volume -/+ and power buttons and got back to familiar territory. Sorry, again, for the completely idiotic question.
I haven't tried anything besides the standard order of operations suggested by Nabi. I downloaded the Nabi OTA software update (which took forever with our pokey internet), then clicked okay as it verified things, then it automatically rebooted with the little green Android guy with his chest open, then, unexpectedly, he's on his back dead with a red triangle sign above his chest. The tablet reboots by itself normally, and there are no changes from what I had before--none of the OTA update has taken effect. And, as a matter of fact, when I check for an update, again, (because it's still at the 2.0 release keys), low-and-behold, it detects an update and wants to download again.
I went through the process 4 times before giving up and checking with the Nabi support on FB. After troubleshooting a couple of things, they wanted to know if my Nabi 2 had ever been rooted. I shut-up then because I didn't want to be scolded, and because, of course, it's no longer under warranty if it's been rooted.
However, I got it second-hand, so I've got no warranty anyway, plus, according to the Victoria Antonio youtube video I followed, I didn't actually root it. With the teensy bit of knowledge I've got now, I'm kinda skeptical of that particular claim, but nevertheless, I still can't get it to update with the fancy new Nabi software, which I've been lusting after.
Any ideas? Obviously I'm clueless about tech lingo, so I would greatly appreciate a very simple explanation. Thanks so much for your time!!
Click to expand...
Click to collapse
If you followed any of the guides out there then you likely have gapps on your tablet(Google Play Store). If that is the case then it has modified/removed some system files. When the Nabi OTA does its thing in the "Android guy" screen(aka stock recovery) it finds files missing or modified and halts the OTA.
You have 2 options. 1) Use a modified OTA(that ignores those files), or
2) restore your backup you made during the Victoria video that has unmodified/removed files then do the OTA.
There is a caveat. The new 2.1.27 OTA uses up almost all the room on the system partition. Without removing something you cannot have a tablet with full gapps package and full Nabi 2.1.27 something will have to be deleted.
Start reading from post #1597 http://forum.xda-developers.com/showthread.php?t=1905674&highlight=nabi&page=160 it will make some more sense.
Update Nabi 2
I have no idea how I rooted the Nabi 2 tablet originally, but I know I did it because I wanted the Google Play store. I am now unable to get the update and the people at Nabi are asking if I have the Play store - I'm pretty sure they are asking this because there is some sort of issue with the update and rooted tablet. If anyone is willing to explain and work with me on this, I would greatly appreciate it!
rozibaby84 said:
I have no idea how I rooted the Nabi 2 tablet originally, but I know I did it because I wanted the Google Play store. I am now unable to get the update and the people at Nabi are asking if I have the Play store - I'm pretty sure they are asking this because there is some sort of issue with the update and rooted tablet. If anyone is willing to explain and work with me on this, I would greatly appreciate it!
Click to expand...
Click to collapse
Assuming you are on 2.0 right now?(2.0.5)? I'm going to base my description on that, if it's 1.9.37 or less there would be other steps.
If so you have a couple of options. I don't know which method you used to get playstore so it's a bit harder. There are 2 questions that you need to answer for yourself. Do you want Wings or the Playstore? Because as of right now it's difficult to fit them both on, and while we kind of have a method using symlinks it's not perfect yet.
So if you want to update and keep the playstore the first thing you need to do is figure out if you have TWRP installed(probably best to have version 2.6.1.0). WIth tablet powered off press and hold the vol+ and power key, navigate with the vol- key to recovery kernel and vol+ to select. If it boots to TWRP you can go on, if it boots to an Android guy you need to install TWRP. Once you have TWRP. MAKE A BACKUP! You can delete it later if you choose but make one now so you can get back to where you are if something goes wrong. I would use external SD for all of this because these are some big files.
After you have done that you can try to do this:
Download these
https://docs.google.com/file/d/0B024tOntNFbbaFJHcFRBRjVMUXc/edit?usp=sharing
http://home.comcast.net/~aicjofs/205to210libfix.zip
Copy them to the Nabi.
Boot in to TWRP and "install" both of these. You should be at 2.1 with Playstore and no Wings(You will still have one Wings app)
OR
You can restore a stock 2.1 if the above doesn't work
Download this:
https://docs.google.com/file/d/0B024tOntNFbbX1liUGN5eVU4UU0/edit?usp=sharing
Extract boot.emmc.win, system.ext4.win from the zip in to the TWRP folder on the device to internal storage(may not have room)
TWRP/BACKUPS/%serial%/2127
Or external SDcard
TWRP/BACKUPS/%serial%/2127
you will have to create the 2127 folder, and possibly the others(if you made a backup some of this will exist already) %serial% = whatever your device serial number is it's different for everyone.
Then boot to TWRP and "restore" checking boot and system only. Don't select data(it shouldn't be an option if you didn't copy data.ext4.win from the zip anyway)
This would leave you at 2.1.27 with Wings but no playstore. You can root it at that point but not install the Playstore unless you then deleted Wings.
The Product Version on the Nabi 2 tablet is 1.9.37. I am assuming that is what you were referring to when you asked if I was on 2.0 right now. I don't really care if I have the Play store or not anymore. At this point, I just want to be able to get the Nabi update and see if it addresses some of the other issues that I am having. I think that I made a huge mistake in doing all of this since I do not actually know what I am doing. I think the only reason why I got the Play store was for one specific game and I don't even remember what that game was anymore, so she will be ok without it.
I do not really understand what TWRP or anything like that is. Is there an easy way to just get rid of everything and pretty much start from scratch so that I can get the updates like normal? I know that the factory reset doesn't get rid of the rooting, unfortunately.
I am really grateful for your help! Thank you!
Error in /external_sdcard/...
I am not sure why I am getting his but I have tried every version of the Nabi2 ROM stock and custom 2.0.5 and above. It seems that I can only install previous versions to 2.0.5.
I have TWRP v2.3.3.0 installed and I am trying to get the latest 2127OTA build installed. If I revert back to stock ROM it boots fine but there a few odd going ons. One it always defaults to Mommy Mode even though I select Daddy Mode. WiFi never works even with WiFi fix. Tap sound does not turn off even though I selected to turn it off.
At this point I am fine going back to a full working stock mode as long as I will be able to get the latest OTA of the web or a working 2127OTA build.
Please advise,
Niles
Hi, I have a similar upgrading problem with the Fuhu Nabi .
I am on version "1.9.37-release-keys" with TWRP 2.6 installed.
I am happy with the process of booting into TWRP, adb push etc
I just cannot get any of the updates to succeed, at the moment they all fail at the start of installation with a "assert failed: apply_patch_check("/system/app/ApplicationsProvider.apk", [and then what I'm guessing is a checksum]").
I guess this means I'm trying to apply the patch to the wrong version of current system.
I wonder if someone would be able to spell out a recommended upgrade path from 19.37 to 2.10 (possibly this would require upgrading to 2.05 as a an intermediate step)
Marcus
marcusbaw said:
Hi, I have a similar upgrading problem with the Fuhu Nabi .
I am on version "1.9.37-release-keys" with TWRP 2.6 installed.
I am happy with the process of booting into TWRP, adb push etc
I just cannot get any of the updates to succeed, at the moment they all fail at the start of installation with a "assert failed: apply_patch_check("/system/app/ApplicationsProvider.apk", [and then what I'm guessing is a checksum]").
I guess this means I'm trying to apply the patch to the wrong version of current system.
I wonder if someone would be able to spell out a recommended upgrade path from 19.37 to 2.10 (possibly this would require upgrading to 2.05 as a an intermediate step)
Marcus
Click to expand...
Click to collapse
I have upgraded to the latest TWRP, 2.7, on my Nabi2 and was able to upgrade to 2.05, but I am still not able to upgrade to 2.10. Same error. Obviously some one was successful or they would not post the 2.10 file. Please advise.
Not sure if it will work for everyone, but....
Not sure if it will work for everyone, but after much fooling around with TWRP and the OTA update not working, I restored the backup I had made when I first rooted the nabi earlier this year, once it was done it booted into the standard nabi mode, when I logged into Daddy mode the Play store and all my root apps were gone, but I was able to install the 2.1 update that brings Wings university, and once that was installed, I then searched for updates again and it showed nabi 2 Over-the-Air Update v.2.3 (Part 1) which officially adds the Play store to the nabi 2, after that installed, I again went into Daddy mode and searched once more for updates and found nabi 2 Over-The-Air Update v.2.3 (Part 2) (which add Google Services (bloatware, honestly) and upgrades the OS to 4.1 Jelly Bean), and installed that as well. I haven't decided whether or not to re-root it, but I don't think I will, simply because there's really no need to root it anymore, since the Google Apps are there officially now. I hope this helps alot of people, since I wasn't able to find any info myself on the process, and discovered it through trial-and-error:highfive:.
How to Restore Backup?
78cherokeechief said:
Not sure if it will work for everyone, but after much fooling around with TWRP and the OTA update not working, I restored the backup I had made when I first rooted the nabi earlier this year, once it was done it booted into the standard nabi mode, when I logged into Daddy mode the Play store and all my root apps were gone, but I was able to install the 2.1 update that brings Wings university, and once that was installed, I then searched for updates again and it showed nabi 2 Over-the-Air Update v.2.3 (Part 1) which officially adds the Play store to the nabi 2, after that installed, I again went into Daddy mode and searched once more for updates and found nabi 2 Over-The-Air Update v.2.3 (Part 2) (which add Google Services (bloatware, honestly) and upgrades the OS to 4.1 Jelly Bean), and installed that as well. I haven't decided whether or not to re-root it, but I don't think I will, simply because there's really no need to root it anymore, since the Google Apps are there officially now. I hope this helps alot of people, since I wasn't able to find any info myself on the process, and discovered it through trial-and-error:highfive:.
Click to expand...
Click to collapse
How do I locate the backup file to restore it? I am hoping that I saved everything on my computer at home. I really just want to get rid of everything that I did to get access to the Google Play Store. I regret ever messing with it to begin with. I am trying to update my daughter's tablet, but it won't let me bc of whatever I did to get the Google Play Store about a year ago. I am almost 100% sure that I used the video by Victoria Antonio to root the tablet originally. If you are able to explain this process to me to fix it, I would greatly appreciate it. I like to think of myself as being pretty computer intelligent, but this was a big mistake!
ok guys gonna be honest here. its been a long time since I have done any rooting but remember the basics. and will have no problems but I need some verification before I proceed.
I am wanting to root because I just cannot stand this bloat crap that is embedded into my stock note 3. especially this flipboard crap! I mean what the hell. cant even turn it off! I wonder how much they had to pay Samsung to have this embedded where you can even turn it off!!!!! and when you force stop it is updates the next day and is on again! ohh it burns me up makes me boil. I have already called and chewed Samsung a new a**hole. but doesn't matter they don't care. so it is time for me to take matters into my own hands.
anyway. I am going to paste the procedure I found and make sure this is the correct way up to date or point me to a better way if one is available.
what I want is just to be able to remove this bloat and get rid of the knox crap that is an invasion of my privacy anyway! I really don't care about roms at all. just want to have control of my phone..
here is the procedure I am going to follow
So i am going to root my sisters phone, as she has not been previously rooted and she is already on the stock kit-kat ota. Im looking at this method and I hear good things, though I believe that things are a little bit easier for those who are already on stock ota. So to help clear up some confusion im listing the simplified steps for those already on stock kit-kat so could someone please confirm if this is accurate?
1. Download odin/CF-root from op (file name-CF-Auto-Root-hlte-hltexx-smn9005)
2. Download 4.4 bl compatible twrp from OP-(file name hltespr-recovery-4.4.img)
3. Since you are already on 4.4 Bl simply put phone in dl mode and flash the included CF-root 9005.tar (placed in PDA of course)
4. Allow phone to reboot (no data will be wiped, and phone will be rooted correct??)
5. Boot back into dl mode and odin the hltespr-recovery-4.4.img (placed in in PDA)
6. Reboot.. now phone will be rooted with Twrp recovery and you are free to flash any rom 4.4 only of course (freeza's 4.4 stockish rom)
7. Done!
so please someone confirm if this is correct, and clarify whether data will be wiped?
Thanks!
is this safe and are the files up to date?
thanks
Before I begin, I wish to apologize for my naivete, as I am just starting to scratch the surface.
Well, I'm stuck with my wife's old stupid verizon bootloader OF1 stuck junk. I have managed (with help from other posts on this forum) to root my phone using kingroot, switch root to supersu, and load all the necessary files for flashing step for step from http://forum.xda-developers.com/gal...ort-albe95-s6-port-4-5-updt-23-09-15-t3234009. I also tried using rom from http://galaxys4root.com/t-mobile-galaxy-s4-roms/android-6-0-root-for-galaxy-s4-jdc-team/2/, to no avail. For whatever reason, the device wipes properly, installs the software, gives no error messages, and then just reboots into startup just like factory reset with the stock firmware (still rooted thank goodness). I made sure that I verified the root before proceeding, that it was supersu binary, and that all the files were stored and backed up on my external sd card. Flashfire was loaded in the order specified on the tutorial and I followed them to the letter. I'm just very lost at this, since I have rooted many devices, but never tried to flash a rom and it just factory reset.... very odd. On the plus side it didn't brick it so there's that glimmer of hope. Anyways, I really hope that someone could help me out on this one, or just tell me I'm crazy and there's no way it can be done on this firmware.
wstefan20 said:
Before I begin, I wish to apologize for my naivete, as I am just starting to scratch the surface.
Well, I'm stuck with my wife's old stupid verizon bootloader OF1 stuck junk. I have managed (with help from other posts on this forum) to root my phone using kingroot, switch root to supersu, and load all the necessary files for flashing step for step from http://forum.xda-developers.com/gal...ort-albe95-s6-port-4-5-updt-23-09-15-t3234009. I also tried using rom from http://galaxys4root.com/t-mobile-galaxy-s4-roms/android-6-0-root-for-galaxy-s4-jdc-team/2/, to no avail. For whatever reason, the device wipes properly, installs the software, gives no error messages, and then just reboots into startup just like factory reset with the stock firmware (still rooted thank goodness). I made sure that I verified the root before proceeding, that it was supersu binary, and that all the files were stored and backed up on my external sd card. Flashfire was loaded in the order specified on the tutorial and I followed them to the letter. I'm just very lost at this, since I have rooted many devices, but never tried to flash a rom and it just factory reset.... very odd. On the plus side it didn't brick it so there's that glimmer of hope. Anyways, I really hope that someone could help me out on this one, or just tell me I'm crazy and there's no way it can be done on this firmware.
Click to expand...
Click to collapse
*UPDATE* for anyone experiencing the aforementioned issue, I found a solution. Not quite sure which one of these actually fixed it, but my bet is on disabling Samsung's locked and found. Anyways, here's what I did:
1. Disabled Samsung locked and found.
2. Factory reset and cleared dalvik and all cache and the sdcard (internal and external).
3. Re-set up phone making sure not to enable Samsung locked and found.
4. Rooted with Kingroot
5. Switched root from kingroot to supersu
6. Enabled default in supersu to allow vs prompt
7. Downloaded required files to ext sdcard
8. Used flashfire to load rom in EXACT order as first post specifies with wipe first
9. Let it do it's thing (for whatever reason, my load took hours not minutes to complete so be patient)
10. Laugh at everyone on every other forum who says this can't be done
Again, this is on Samsung Galaxy S4 Verizon running 5.0.1 OF1 Firmware originally unrooted. IT IS POSSIBLE!!!
All files must be on device storage if u planning to use flash fire. for example in a download folder. Do not use SD card. I used Albe95 rom 4.7 port. Works very good and smooth. All u need is of1 wifi fix.zip
Thanks Sashaua04, but I have to disagree, as I tried it multiple times and that is the only way I got it to work. Again, not sure which of those steps worked for me, but I most certainly DID use my external sd card to store and flash the zip and that is the only way I got it to work. I tried using downloads folder on internal storage and it did not work. It did however work on ext. I say do whatever works for you. I'd love to hear from a pro why this is the case and why this happened like it did. I was thinking my binary was unofficial, but I checked in download mode each time and it was official, but it said something about Samsung lock active, and after disabling and making aforementioned changes, it worked. Maybe that had something to do with it. Strange... maybe I had a bad download or
something...