Related
I started discouraging its use on TNT Lite after the TNT Lite 5 fiasco, but I didn't realize that my opinions carried so much weight. So I want to set the record clear for everyone.
First off, if the developer / modder requires clockworkmod for their ROM, then that's the tool you need to use. I've had more than a few PM's on this question, but the answer is simple. Use what the developer asks you to use -- but also understand the risks. I would guess that most of the devs here mod with clockworkmod in mind.
For my own two active mods (TNT Lite 4 and gADAM) -- for the gADAM, it requires clockworkmod to install, right now. The reason why is because you HAVE to do a data wipe post-install, which standard recovery does not have. I have this written clearly in the instructions. As for TNT Lite, I discourage it for flashing, but I have instructions for clockworkmod users regardless. gADAM 1.3.0+ and TNT Lite 4.3.0+ have something called "Recovery Pack" built into them. This allows the user to toggle between clockworkmod and standard recovery.
Flashing is my concern, btw. For nandroid backups, data wipes and SD repartitions, the cwm tool is an absolute must. And if you are flashing between 1.1-based mods, clockworkmod should still be a low risk. HOWEVER, if Viewsonic releases a 1.2-based mod with a new bootloader, then cwm becomes a much higher risk. My point with discouraging clockworkmod for flashing on TNT Lite is just to get people used to the idea that cwm has caveats that might become a problem, later on.
When that new firmware is released, we will pick it apart and tell everyone the results of what we find. Hopefully my concerns are for nothing and the new firmware will be safe for clockworkmod users.
Also, for reference: I've been throwing around the term "1.1-based ROM" for about 2 weeks, now. Viewsonic's stock firmware has come in three flavors, so far: 1.0.1 and 1.1, which seem to be on the same dev branch and compatible (from a clockworkmod standpoint). Most, if not all, of the mods here are 1.1-based. 1.2 is a new dev branch that was introduced with build 3991, which was never officially released. This build has a bootloader that, if not flashed with standard recovery, will soft-brick your device. This is the dev branch that concerns me and that we should be watching out for, when that new firmware is released. As I mentioned, we will test it when the time comes.
when the time comes...
Somewhat quicker.
Thanks for detailed explanations!
absorbers said:
when the time comes...
Somewhat quicker.
Thanks for detailed explanations!
Click to expand...
Click to collapse
Quicker is not always better, imo. If users here use cwm, they should understand the risks. I would argue that anyone using a mod here should also understand how to install and use nvflash - devices like the Advent VEGA, Notion Ink Adam and even Viewsonic's own Viewpad10s have nvflash-only firmware updates. I personally find it to be a critical tool for anyone modding their device.
Thanks for the explanation. As a n00b (Wooter) to all of this, I have to say that I have used the built in bootloader to flash both Vegan 5.1.1 and TNT Lite 4.4 without any issues. I did not install CWM based on your previous warnings about it and so far I haven't had any issues. I needed to do a factory data reset after changing ROMs to fix some FC issues, but so far I haven't seen a need to repartition the SD card or any other features that CWM has.
severusx said:
Thanks for the explanation. As a n00b (Wooter) to all of this, I have to say that I have used the built in bootloader to flash both Vegan 5.1.1 and TNT Lite 4.4 without any issues. I did not install CWM based on your previous warnings about it and so far I haven't had any issues. I needed to do a factory data reset after changing ROMs to fix some FC issues, but so far I haven't seen a need to repartition the SD card or any other features that CWM has.
Click to expand...
Click to collapse
And you have cwm ready for use, with TNT Lite 4.4.0 - it's in the Recovery Pack. So, if you find the need to do an SD repartition later, it's there for you to use. I find it to be a good balance and I toggle back and forth a lot. Actually, for day-to-day I leave it on clockworkmod and then flip it to standard if I plan to flash.
There have been some discussions in the partition thread regarding the 'fix permissions' portion of CWM making the repartition suggestion obsolete. I don't have access to standard recovery to check if that option is in there too but the permissions thing may also be a feature of CWM that will be difficult to let go.
roebeet said:
And you have cwm ready for use, with TNT Lite 4.4.0 - it's in the Recovery Pack. So, if you find the need to do an SD repartition later, it's there for you to use. I find it to be a good balance and I toggle back and forth a lot. Actually, for day-to-day I leave it on clockworkmod and then flip it to standard if I plan to flash.
Click to expand...
Click to collapse
First, thanks for your work here. You guys rock! I am using TnT Lite 4.4, where do I locate the recovery toggle? Is it an app?
I wanna say Thanks for the 'Recovery Pack', I actually didn't find it until after I had
gone over the scripts in TnT Lite 4.4 and copied all the files to SDCard.
I then flashed back to Stock 3855 and gave Terminal Emulator SU, mounted system rw and copied them back in.
I ran the 'cwmrecovery.sh' and booted into ClockWorkMod and successfully did a backup (and later a restore).
I ran the 'fixrecovery.sh' and booted into Standard recovery and got the downloading animation and it proceeded to a normal startup (no exclamation!).
Is this normal?
I think there was an update.zip @ root but no command file.
Thanks again for all your work, looking forward to more modding.
Peace!
brown14you said:
First, thanks for your work here. You guys rock! I am using TnT Lite 4.4, where do I locate the recovery toggle? Is it an app?
Click to expand...
Click to collapse
It's a set of scripts - just read my first post, and the Recovery Pack reference link, at the bottom.
jazzruby said:
I wanna say Thanks for the 'Recovery Pack', I actually didn't find it until after I had
gone over the scripts in TnT Lite 4.4 and copied all the files to SDCard.
I then flashed back to Stock 3855 and gave Terminal Emulator SU, mounted system rw and copied them back in.
I ran the 'cwmrecovery.sh' and booted into ClockWorkMod and successfully did a backup (and later a restore).
I ran the 'fixrecovery.sh' and booted into Standard recovery and got the downloading animation and it proceeded to a normal startup (no exclamation!).
Is this normal?
I think there was an update.zip @ root but no command file.
Thanks again for all your work, looking forward to more modding.
Peace!
Click to expand...
Click to collapse
If memory serves, you should get the "!" and then a reboot. But it might not do anything if there's no command file (just hang there for a moment, and then reboot).
Thanks. Got it!
Thanks, I just booted again to recovery, no command or update.zip and same thing.
jazzruby said:
Thanks, I just booted again to recovery, no command or update.zip and same thing.
Click to expand...
Click to collapse
To verify 100% that it's working, you might want to run an update.zip. ie. use the Recovery Pack standalone, it will just overwrite what's already there. Always good to know before you actually need it.
I'm not so sure I'd feel 100% just flashing the 'Recovery Pack'.
I was getting ready to flash Pershoot's Kernel so I think first I'll flash 3588 with stock recovery and be sure all's good.
Then I'll flash the RP and boot into ClockWorkMod and Restore 4.4 from backup.
Thanks for the Heads Up!
jazzruby said:
I'm not so sure I'd feel 100% just flashing the 'Recovery Pack'.
I was getting ready to flash Pershoot's Kernel so I think first I'll flash 3588 with stock recovery and be sure all's good.
Then I'll flash the RP and boot into ClockWorkMod and Restore 4.4 from backup.
Thanks for the Heads Up!
Click to expand...
Click to collapse
Pershoot's kernel may not work with standard recovery, just a heads up. But you can certainly give it a go.....
Pershoot's kernel is nested in a subfolder and I need/want to wipe first.
I just flashed 3588 with Stock recovery and all's good.
I got root and flashed 'RP' and CWM restored my backup.
I ran TE 'fixrecovery.sh', rebooted into Stock recovery and I don't see the (!).
Aside from the downloading animation it seems like a normal boot.
This was with no update.zip @ root or command file in recovery subfolder.
So I guess it's safe to say that no (!) is nothing to worry about.
Just to be sure I dropped an update.zip @ root and same results.
I did the OTA update today, and attempted an install of CWM. I'm not sure if it went all the way through.
The tablet was still working fine.
When attempting to load an update of 4349 with market, the gtab gets stuck at "booting recovery kernal image".
Now the g-tab will not load at all. I attempted the NV Flash procedure but it failed at the final step during the batch where it could not find the file.
Any tips on what I should do next?
which method? Linux, windows?
windows version.
if you can, give us a list of files in your nvflash directory.
thank you, you got me in the right direction. i did not extract the gtablet file.
yea, with all these tools available, it's really hard (is it possible?) to brick g-tab . ..
210danielz,
Unless I misunderstood your first post, it sounds like you have a CWM problem.
Running CWM with 4349 will cause semi-bricks -- and several of us have tried
to post warnings to that effect all over the forum.
IMO, you probably should NVFlash back to stock and let the OTA update take
you back to 3588. Then you will be stock with a solid rom and can do what you
want.
http://forum.xda-developers.com/showthread.php?t=861950
Good Luck,
Rev
210danielz said:
I did the OTA update today, and attempted an install of CWM. I'm not sure if it went all the way through.
The tablet was still working fine.
When attempting to load an update of 4349 with market, the gtab gets stuck at "booting recovery kernal image".
Now the g-tab will not load at all. I attempted the NV Flash procedure but it failed at the final step during the batch where it could not find the file.
Any tips on what I should do next?
Click to expand...
Click to collapse
Here is more info on 4349.
http://forum.xda-developers.com/showthread.php?t=1035983
Roebeet ran a lot of tests and found that 4349 is not compatible with CWM.
210danielz,
When someone gets a bad NVFlash like that I always tell them to:
Take the procedure and go through and check everything. Make sure right
.zip files used. Check every little detail.
Re-run the NVFlash.
If previous step fails again, try nvflashing CWM only:
http://forum.xda-developers.com/showthread.php?t=1030042
If you get a good flash on CWM and get it up, the go to the
Advanced Menu and Partition (2048/0), Fix Permissions, Wipe
Dalvic Cache. Then Return to Main Menu and Wipe Cache
and Wipe/Reset Factory Data.
Having done the above, shut down and go back and NVFlash
to stock again (having cleaned out and repartitioned to
hopefully make it work right this time!)
Hopefully this will give you a working G-Tablet with Bekit 1105
or stock Version 2638 on it. If you set up wifi it will pretty
quickly offer you an OTA to 3588.
From there you can go where you want.
Hope this helps,
Rev
I've updated my 3.1 to 3.1.1 and then to 3.2 using the following methods and I just realized that my bluetooth wont turn on. I've tried restarting / setting to airplane mode and clearing bluetooth share data and nothing works. Can anyone with the same experience help ?
Symtom :
When i Go Into Settings > Wireless & Networks > Bluetooth , and I hit the Bluetooth to power it on it says Powering On then it goes back to the Off Settings
From rooted 3.1 to 3.1.1 ( 8.4.4.11 ) I've flashed using this thread
http://forum.xda-developers.com/showthread.php?t=1178607
and to 3.2 using this thread
http://forum.xda-developers.com/showthread.php?t=1190877
I do use the bluetooth alot for tether so it would be nice if I can regain it's functionality.
may be due to corrupt file
flash the last file after checking md5
I am almost sure thatit is the flash fro 3.1 to 3.1.1 that did it s there anything that i can do now ?
I have the exact same problem and hoping I don't have to wipe everything again. I spent some time getting everything working. I flashed the .11 cwm full in the dev section then the 3.2 cwm zip. I might backup my data and flash again.
jetway1122 said:
I have the exact same problem and hoping I don't have to wipe everything again. I spent some time getting everything working. I flashed the .11 cwm full in the dev section then the 3.2 cwm zip. I might backup my data and flash again.
Click to expand...
Click to collapse
I am already on 3.2 what should i do and what do you mean by reflash ? Do you just redo the 3.1.11 and then 3.2 via CWM ? Won't that brick the TF ?
desilva79 said:
I am already on 3.2 what should i do and what do you mean by reflash ? Do you just redo the 3.1.11 and then 3.2 via CWM ? Won't that brick the TF ?
Click to expand...
Click to collapse
I believe it will, I mean nvflash to stock and try the whole process again. I'm in the process of backing up and attempting. I did try 3.2 cwm zip again but bluetooth still wont turn on so it must be the flash to .11 that messed things up.
Okay I'm not that smart.....can you be so kind to provide steps/forum thread on how to nvflash ? I know it's a process to flash back to stock / unrooted / without CWM ( just like out of the box ) ?
Had to step out but I'm back now and will try to reflash with nvflash and post the steps for you if it works.
Thanks a lot Jetway. That would be awesome.
I figure it would be something like use nvflash to 3.1
Asus Transformer NVFlash Stock 3.1 Recovery Roms
upgrade to 3.1.1 OTA
root it using the thread below ?
Batch script Pure Root Method for 8.4.4.11 & 8.6.5.6US - v5 beta update
use the CWM to flash to 3.2 ( there's also post on the thread above stating that you can just do OTA to 3.2 and then root it using the available script )
Sounds about right ? If you can still post your steps it would be awesome. Sorry I'm total noob in this.
desilva79 said:
Thanks a lot Jetway. That would be awesome.
I figure it would be something like use nvflash to 3.1
Asus Transformer NVFlash Stock 3.1 Recovery Roms
upgrade to 3.1.1 OTA
root it using the thread below ?
Batch script Pure Root Method for 8.4.4.11 & 8.6.5.6US - v5 beta update
use the CWM to flash to 3.2 ( there's also post on the thread above stating that you can just do OTA to 3.2 and then root it using the available script )
Sounds about right ? If you can still post your steps it would be awesome. Sorry I'm total noob in this.
Click to expand...
Click to collapse
You got it right, that's what I wanted to do and skip the Full 8.4.4.11 CWR ZIP but for some reason on .11 I cannot install any version of cwm not even the failsafe one and my tablet won't see the OTA either even with the stock flash and manual update from asus website.
So flashing with nvflash from link tabletroms brought back bluetooth and when I flashed Full 8.4.4.11 CWR ZIP I still have bluetooth! I rooted with the script in the dev thread and used the failsafe cwm. About to update to 3.2 and see if it still works.
Update: So when flashing the cmw 3.2 file this is where the bluetooth is lost. If only my device would see the OTA this could be solved. Im trying to redownload the zip file.
I got to grab another microSD card so I haven't started yet , but from the sound of it I should try to upgrade all the way to 3.2 ( if possible ) and then only try to root/cwm ( using the batch script v. 5 ) it by then ? What a pain in the bottom...... thanks for your help , at least I have someone with the same scenario that knows way much more than I do and can offer help...
Jetway , will this 3.2 OTA firmware be useful to you since you cant get the 3.2 from 3.1.1 ?
http://forum.xda-developers.com/showthread.php?t=1190868
I tried everything I could with the cwm files but once going to 3.2 I always lost bluetooth. So I looked at the thread you posted which I saw before but didn't read the whole thread and now that I did I was able to update to 3.2 (no root) + bluetooth working.
I nvflashed to 3.1 (.45 not .11) then I downloaded the ota ([the one from multiupload 60+meg one] )
imtiyazee:
I followed these instructions to flash:Instructions copied from gee one post
I had trouble applying the OTA manually. It was a pain.
If you are stock and NOT rooted, it's not too bad.
Download the US version of the update. There's a thread in the dev section I think.
Rename it to EP101_SDUPDATE.zip and save it to the root directory of the external micro SD.
Put the sdcard in the slot and reboot into recovery. You should see an android guy with a gear belly for 5-10 mins. Wait and be patient until you see your homescreen again.
To get into recovery, turn off the TF. Hold the volume down button and press the power button. As soon as the screen come on, you see some text at the top. Press volume up to boot recovery. If you wait too long, it will wipe your data, so back up anything important.
If you are rooted and/or you have a custom recovery, this probably won't work.
After all this I had 3.2 with working bluetooth, I will use the script to root but follow the above and you should be good as well
Update : I used the script v5 and rooted just fine, finally I'm done!!!!
Jetway, I'm confused , how did you update from 3.1.11 to 3.2 ?
Update: What a pain in the butt. I finally managed to finish installing everything. I did the same thing you did ( I should learn to read slower) . Thanks a lot Jetway
desilva79 said:
Jetway, I'm confused , how did you update from 3.1.11 to 3.2 ?
Click to expand...
Click to collapse
I didnt, i went from 3.1.45 not the .11. I went to tabletroms and grabbed the nvflash for us transformer. So i skipped the update you see, and i grabbed the 3.2 update from OTA thread as you posted. Get the 60meg one as its for updating from 3.1 (.45) version andfollowed the steps i posted about renaming the update file and putting it on an micro sdcard.
Awesome, I'm back to 3.2 Rooted /CWMed and Bluetooth freaking works ! Thanks Jetway112
Here's what we did , in case anyone needs help
Backup Apps using Titanium
Flash back to stock
Asus Transformer NVFlash Stock 3.1 Recovery Roms
upgrade to 3.2 OTA from ( 3.1 stock to 3.2 ) using the OTA file from this post
[OTA] STOCK 3.2 zip file.
root it using the thread below
Batch script Pure Root Method for 8.4.4.11 & 8.6.5.6US - v5 beta update
Restore Apps Using Titanium
Update CWM from this thread
[Recovery] ClockworkMod 3.1.0.1-solarnz-R3 Modded for Internal media
Np we helped each other out on this one for sure. Just glad that our bluetooth is working agian.
Someone needs to sticky this so that no one else goes from 8.4.4.5 to 8.4.4.11 then 3.2 like we did and lose bluetooth.
I've lost my Bluetooth too. I'm trying to find out how I can return to what I had before without losing everything. I did a android and a titanium backup so I'm hopeful.
Second that
Yeah I agree... it was a pain in the bottom to get the bluetooth back up. I'm going to post this thread over at the other 8.4.4.11 thread
Thanks a lot! Followed everything as u said and got BT back!
Hey, this would be my first attempt at doing rooting and firmware installation on an android device (I have jailbroken iOS devices several times in the past, which seems much easier lol). I just wanted to double check things before I end up making a mistake.
EDIT: I have a UK 8010 WiFi only Note10.1 ... Realised I should probably have added that somewhere.
Basically, I havent managed to find a decent step-by-step guide on how to do this, especially not with the current JB updates (probably because they have only been out for a couple of days) so I was hoping someone would help me out, or point me in the right direction.
From what I understand....
1. I root the Note (with help from this thread: http://forum.xda-developers.com/showthread.php?t=1831152)
Using method 2, I guess... though I did want to check that it is possible to reset the binary counter on the Note??
2. I do a backup of my device with nandroid?
3. I download the Nordic Countries JB 4.1 file from here : http://forum.xda-developers.com/showthread.php?t=2016792
I'm in the UK, so I figured this was the one to use.
4. I install the firmware using Odin... http://www.tsar3000.com/Joomla/inde...es-by-odin-program&catid=57:how-to&Itemid=104
5. Use the links in the thread to fix the rom for my 8010 - http://forum.xda-developers.com/showthread.php?t=1982821
6. Profit.
Does this seem about right?
And if so:
A) Can the binary counter for Note10.1 be reset fairly straightforwardly?
B) When the actual official firmware gets released, how difficult is it to reset the device back to factory settings?
Thanks for the help
If I were you I would install the update from step three. This would get you to a JB stock base.
Then I would work on root. Same as you have in step 1.
Then step 5 .
I will say tha myself I installed Root and then loaded my recovery (you can use CWM or TWRP). Then I installed a custom ROM and after on good boot any fixes or updater I wanted or needed
Hope this helps.
Sent from my GT-N8013 using xda premium
alperin1 said:
If I were you I would install the update from step three. This would get you to a JB stock base.
Then I would work on root. Same as you have in step 1.
Then step 5 .
I will say tha myself I installed Root and then loaded my recovery (you can use CWM or TWRP). Then I installed a custom ROM and after on good boot any fixes or updater I wanted or needed
Hope this helps.
Sent from my GT-N8013 using xda premium
Click to expand...
Click to collapse
Ahh ok thankyou, for some reason I assumed that to install a non-standard ROM, I would need to be rooted (as in, installing the 8000 ROM onto my 8010).
Thanks for the tip though
I think you need cwm for the zip fix from step 5. If you want to do a nandroid backup, doit right after flashing cwm, before flashing superuser, in order to have a untouched backup of your stock unrooted Rom. You need root to use triangleaway. Here is how I did it:
1. Flash cwm and use it for backup
2. Flash a deodexed Rom, it is the German one by darkman in dev forum here, reboot and let it load.
3. Boot in cwm again and flash the fix
4. Install triangle away and use it.
Sent from my GT-N8010 using Tapatalk HD
Hello community,
I was given the device last year and had been fairly satisfied with the performance of it. However, it has gotten laggy over the past couple weeks and a friend suggested to root and flash a rom on it. So, without any prior knowledge, I have been doing some research and browsing through the threads on this forum. I can see that there are guides but was very unsure if the methods would still work because I have noticed that most of them were last updated/edit a while ago. I know I shouldn't use the word 'latest' for doing this to a tablet that is fairly old in the market. However, it would be very helpful if someone can point me to some 'proven to work' or 'trust-worthy' guides of rooting, flashing recovery, and rom.
Also, just out of curiosity, please recommend which recovery and rom a first-timer should use if possible
try these roms.
rocketfans14 said:
Hello community,
I was given the device last year and had been fairly satisfied with the performance of it. However, it has gotten laggy over the past couple weeks and a friend suggested to root and flash a rom on it. So, without any prior knowledge, I have been doing some research and browsing through the threads on this forum. I can see that there are guides but was very unsure if the methods would still work because I have noticed that most of them were last updated/edit a while ago. I know I shouldn't use the word 'latest' for doing this to a tablet that is fairly old in the market. However, it would be very helpful if someone can point me to some 'proven to work' or 'trust-worthy' guides of rooting, flashing recovery, and rom.
Also, just out of curiosity, please recommend which recovery and rom a first-timer should use if possible
Click to expand...
Click to collapse
hello ,
these are the things you need to do before flashing a ROM.
note: -the following things may void your warranty.
-do this on your own risk.
1. HOW TO ROOT
-First install kingo root on your windows PC. Then check USB debugging .
( settings. < about device < touch build number 7times < go back and select developer options < check USB debugging.)
-Open kingo root on the PC and connect your device and connect your device to the PC. Start root and do not remove the USB cable until it says finish.
-Now you have successfully rooted your device.
2.HOW TO INSTALL A CUSTOM RECOVERY
- Go to the following link and download CLOCK WORK MOD(CWM)
LINK: https://www.clockworkmod.com/rommanager
Select your device and install the recovery.
go into the app and install recovery .
3.BACK UP
download rom manager from playstore and do a backup( do a backup using this ap only if you are using CWM recovery.
link for ROM manager: https://play.google.com/store/apps/d...mmanager&hl=en
Now the first thing you need to do is download this rom.
https://www.androidfilehost.com/?fid=95916177934533333
(note: you can flash the rom of p5110 for p5113)
now to flash the rom follow the following steps.
1. Go to recovery mode
2. (have the rom in your sd card)flash it there .
use this link to know how to flash a rom.
https://www.youtube.com/watch?v=tJfPwWjnWGY
now you can reboot after flashing.
to get inbuilt google apps and play store you need to install something called GAPPS (Google apps) download from this link.
http://opengapps.org/?api=5.1&variant=nano
now you flash this zip the same way you flashed the rom.
any problems plz notoce me.
Zte blade l said:
hello ,
these are the things you need to do before flashing a ROM.
note: -the following things may void your warranty.
-do this on your own risk.
1. HOW TO ROOT
-First install kingo root on your windows PC. Then check USB debugging .
( settings. < about device < touch build number 7times < go back and select developer options < check USB debugging.)
-Open kingo root on the PC and connect your device and connect your device to the PC. Start root and do not remove the USB cable until it says finish.
-Now you have successfully rooted your device.
2.HOW TO INSTALL A CUSTOM RECOVERY
- Go to the following link and download CLOCK WORK MOD(CWM)
LINK: https://www.clockworkmod.com/rommanager
Select your device and install the recovery.
go into the app and install recovery .
3.BACK UP
download rom manager from playstore and do a backup( do a backup using this ap only if you are using CWM recovery.
link for ROM manager: https://play.google.com/store/apps/d...mmanager&hl=en
Now the first thing you need to do is download this rom.
https://www.androidfilehost.com/?fid=95916177934533333
(note: you can flash the rom of p5110 for p5113)
now to flash the rom follow the following steps.
1. Go to recovery mode
2. (have the rom in your sd card)flash it there .
use this link to know how to flash a rom.
https://www.youtube.com/watch?v=tJfPwWjnWGY
now you can reboot after flashing.
to get inbuilt google apps and play store you need to install something called GAPPS (Google apps) download from this link.
http://opengapps.org/?api=5.1&variant=nano
now you flash this zip the same way you flashed the rom.
any problems plz notoce me.
Click to expand...
Click to collapse
I was looking in the forum and someone said that I would also need to unlock the bootloader? If so, how do I do that?
Also, is there a difference between kingroot and towelroot? I saw a post in the forum here saying towelroot is fast and easy to root the tablet.
Not much difference.
Actually there is not much difference between kings root and towel root....towel root doesn't need a PC...but I have never used it so I can't assure you that it is safe.
And coming to the boot loader I don't know much about it but I didn't do anything like that before flashing a rom or rooting my tab2....
If you want further assistance about the boot loader I can help you with that..
rocketfans14 said:
I was looking in the forum and someone said that I would also need to unlock the bootloader? If so, how do I do that?
Also, is there a difference between kingroot and towelroot? I saw a post in the forum here saying towelroot is fast and easy to root the tablet.
Click to expand...
Click to collapse
it is not necessary to unloack bootloader for tab 2 as it comes with a unlocked bootloader from stock.
Zte blade l said:
Actually there is not much difference between kings root and towel root....towel root doesn't need a PC...but I have never used it so I can't assure you that it is safe.
And coming to the boot loader I don't know much about it but I didn't do anything like that before flashing a rom or rooting my tab2....
If you want further assistance about the boot loader I can help you with that..
Click to expand...
Click to collapse
Hey, it's been a while. Honestly speaking, when I first posted this thread, I didn't really have enough time to do the things so now I am finally back and trying to do it. So far, I know what recovery and rom I'm going to use with all the files downloaded and ready. Though, currently, I am still at the pre-root stage. I have read up things about kingoroot and not sure if I wanted to use it. So I looked around on the forum and wonder if Odin is still a working solution. Reading on the steps and guides, I was wondering if I need to have Kies installed?
rocketfans14 said:
Hey, it's been a while. Honestly speaking, when I first posted this thread, I didn't really have enough time to do the things so now I am finally back and trying to do it. So far, I know what recovery and rom I'm going to use with all the files downloaded and ready. Though, currently, I am still at the pre-root stage. I have read up things about kingoroot and not sure if I wanted to use it. So I looked around on the forum and wonder if Odin is still a working solution. Reading on the steps and guides, I was wondering if I need to have Kies installed?
Click to expand...
Click to collapse
Kies is not needed as it never helped.
You can depend on odin it is your only saviour when you are in trouble.
I think rooting with kingroot is easy as it is just connecting to your PC and cick the start button.
So just notice me when your ready.
And there is also one good news...?
Tab 2 has got marshmallow.
Zte blade l said:
Kies is not needed as it never helped.
You can depend on odin it is your only saviour when you are in trouble.
I think rooting with kingroot is easy as it is just connecting to your PC and cick the start button.
So just notice me when your ready.
And there is also one good news...��
Tab 2 has got marshmallow.
Click to expand...
Click to collapse
I have rooted the tablet. I did it with odin and twrp with flashing the updatedSuperSU zip folder.
I have tried flashing the CM12.1 rom yesterday but resulted in a boot loop. So for now, I'm just rooted and on stock rom until I or someone can find out what was the problem. I have read about the discussion with marshmallow but it seems to me that the project isn't really stable yet. From what I have researched lately, can I assume there's issue with the p51xx line of tablets? Because I saw many people having problems with p51xx and most people with the other tablets aren't having any.
rocketfans14 said:
I have rooted the tablet. I did it with odin and twrp with flashing the updatedSuperSU zip folder.
I have tried flashing the CM12.1 rom yesterday but resulted in a boot loop. So for now, I'm just rooted and on stock rom until I or someone can find out what was the problem. I have read about the discussion with marshmallow but it seems to me that the project isn't really stable yet. From what I have researched lately, can I assume there's issue with the p51xx line of tablets? Because I saw many people having problems with p51xx and most people with the other tablets aren't having any.
Click to expand...
Click to collapse
You first must update your tab to jelly bean bootloader, before trying out newer roms.
Or perhaps flash stock jb firmware with odin
Whatever you choose, both is ok.
http://forum.xda-developers.com/showthread.php?t=2642005
Read here
The first thing you do, is take a nandroid backup, it's very important at every step, unless you are really ready to risk. It's better to have it.
Next Read through the rom threads, clear your mind and your tab too. You must format data.
Stay on twrp 2.8.7.2. Don't go to the latest one yet.
Flash rom, wait, it will boot up.
Every tab behave differently with every rom, sure you are going to face soft reboots, on some roms it will be a lot, on some it will be less. I would suggest you try both LP and kk first.
Remember, it's better to keep this tab updated than to stay on stock. This tab 2 series has a emmc bug and staying on stock or jumping back is a risk too. I have been on kk and lp. They both have kept this tab running great and away from that bug.
billysam said:
You first must update your tab to jelly bean bootloader, before trying out newer roms.
Or perhaps flash stock jb firmware with odin
Whatever you choose, both is ok.
http://forum.xda-developers.com/showthread.php?t=2642005
Read here
The first thing you do, is take a nandroid backup, it's very important at every step, unless you are really ready to risk. It's better to have it.
Next Read through the rom threads, clear your mind and your tab too. You must format data.
Stay on twrp 2.8.7.2. Don't go to the latest one yet.
Flash rom, wait, it will boot up.
Every tab behave differently with every rom, sure you are going to face soft reboots, on some roms it will be a lot, on some it will be less. I would suggest you try both LP and kk first.
Remember, it's better to keep this tab updated than to stay on stock. This tab 2 series has a emmc bug and staying on stock or jumping back is a risk too. I have been on kk and lp. They both have kept this tab running great and away from that bug.
Click to expand...
Click to collapse
Do I have to unroot first? Do you have a link to making a nandroid backup?
Edit: Oh, I looked at the link you included and it said that if I am on stock jb (4.2.2), I can skip the update bootloader part..
When you flashed the new rom, did you do a factory reset (wipe data)?
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app
rocketfans14 said:
Do I have to unroot first? Do you have a link to making a nandroid backup?
Edit: Oh, I looked at the link you included and it said that if I am on stock jb (4.2.2), I can skip the update bootloader part..
Click to expand...
Click to collapse
Yes, that's what I meant too, if you're on jb already, you are fine. You don't have to unroot. For making a nandroid backup, use twrp recovery, there is an option for backup, select and backup all from there, if you get into bootloop or any other problem, as long as you can get back to recovery, you can restore from there. Most rom comes pre rooted.
rocketfans14 said:
I have rooted the tablet. I did it with odin and twrp with flashing the updatedSuperSU zip folder.
I have tried flashing the CM12.1 rom yesterday but resulted in a boot loop. So for now, I'm just rooted and on stock rom until I or someone can find out what was the problem. I have read about the discussion with marshmallow but it seems to me that the project isn't really stable yet. From what I have researched lately, can I assume there's issue with the p51xx line of tablets? Because I saw many people having problems with p51xx and most people with the other tablets aren't having any.
Click to expand...
Click to collapse
Did you clear dalvik cache in recovery before flashing rom?
Zte blade l said:
Did you clear dalvik cache in recovery before flashing rom?
Click to expand...
Click to collapse
Yes, I cleared the top four options in recovery, and formatted data before flashing.
billysam said:
Yes, that's what I meant too, if you're on jb already, you are fine. You don't have to unroot. For making a nandroid backup, use twrp recovery, there is an option for backup, select and backup all from there, if you get into bootloop or any other problem, as long as you can get back to recovery, you can restore from there. Most rom comes pre rooted.
Click to expand...
Click to collapse
That's what I did. Let me just briefly summarize what I have done:
used odin with twrp
booted into recovery and made back up
cleared dalvik, cache, system, and data, formatted data
flashed update supersu, booted into system and checked root with root checker
rebooted into recovery, cleared dalvik, cache, system, and data, formatted data again
flashed cm12.1 and gapps, rebooted but ran into bootloop at splash screen
rebooted into recovery and restored back up
So I'm rooted and on stock 4.2.2 currently.
champ1919 said:
When you flashed the new rom, did you do a factory reset (wipe data)?
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app
Click to expand...
Click to collapse
I did.
Try flashing blisspop or slimLP.