Database Info

[ROM] ASUS rooted firmwares repackaged for ClockworkMod recovery

NOTICE
The method described is now obsolete.
Thread closed.
The only suggestion I would have is to make ClockWorkMod compatible directly with ASUS ROMs (previous and new format: patches + BLOB), as the previous idea is both inadequate or extremely inefficient.
Original first post:
Hi fellow Transformer adopters
After writing an Asus firmwares repacking tool for personal/dev usage, I repacked some official Asus ROMs in ClockWorkMod recovery update.zip formats.
Uploaded here on my server:
http://dl.project-voodoo.org/transformer-roms/
Those are unmodified but rooting is automatically applied in the flashing process without requiring manual intervention.
What's flashed:
- Everything (Kernel, system, additional stuff)...
- except of course the recovery, this way you keep your previously installed custom recovery.
What's needed:
- Only requirement: any custom recovery capable of flashing unsigned standard update.zips, like this one
- As long as the custom recovery is here, there is no prior-rooting requirement.
Requests to repack missing ROMS are welcome if accompanied by download links.
Happy flashing ^^

Hi, I'm new to Asus Transformer, but these are 3.0 ROMS? Do you have 3.1?
And am I correct in saying, that if I flash old 3.0, I can then get clockwork mod on there, and then flash one of these to get a stock ROM but rooted? (I'm guessing I would need SuperUser.APK to install).

CrazyPeter said:
Hi, I'm new to Asus Transformer, but these are 3.0 ROMS? Do you have 3.1?
And am I correct in saying, that if I flash old 3.0, I can then get clockwork mod on there, and then flash one of these to get a stock ROM but rooted? (I'm guessing I would need SuperUser.APK to install).
Click to expand...
Click to collapse
repacked-8.4.4.5_US+root-CWR-update.zip is a 3.1 ROM.
May I rename the files for faster recognition?
And yep that's the idea. Once you get the custom recovery, you can flash any ROM this way.
The lack of proper flashing tool is really annoying but those ROMs are here to make the whole rooting+flashing process a bit easier in the end for most people.

i'm slightly confused by what this does.
i see that these are stock roms with root, however does that mean that, if you are on pure stock 3.1 and you flash your rooted 3.1 rom over it. we then get a 3.1 rooted rom without wiping everything?
or is it a case of it will root the rom but wipe everything? or will it just not flash over a stock 3.1 rom?
thanks for all the help!

I would like to understand this more too. I want to root my 3.1 install and add custom recovery. Well the recovery first then root!

As long as the custom recovery is here, there is no prior-rooting requirement.
Click to expand...
Click to collapse
How does one install CWM without prior root?
Putting on CWM and then flashing a prerooted room seems like a very easy way to get root if there is a way to just install the CWM apk.
--dyst

drdystopia said:
How does one install CWM without prior root?
Click to expand...
Click to collapse
That's what I'd like to know. I'm on 3.1 now, and I understand how to downgrade, root, install CWM and re-upgrade, but that's a lot of effort if this really requires no previous root.

I believe these packages make it easier for you to go from rooted 8.x.y.z to rooted 8.x.z.z, without having to worry about CWM getting overwritten. It doesn't help you root.

drdystopia said:
How does one install CWM without prior root?
Putting on CWM and then flashing a prerooted room seems like a very easy way to get root if there is a way to just install the CWM apk.
--dyst
Click to expand...
Click to collapse
You have to be rooted previously.
What you're waiting for is someone to release the SBK, so we can use NVflash.

10ks Supercurio
just wait for your developing skills implement in TF

So I'm running 3.1 and dont want to downgrade to root and I have heaps of stuff on my tf,dies these mean 3.1 Rom is rooted ?
LEEDROID GB3.0.1DESIRE HD using XDA PREMIUM

I have a quick question:
I downgraded from 3.1 to 3.0, rooted, and installed CWM. When I rebooted I was rooted with the superuser app. I then installed the repacked 8.4.4.5 rom linked in the first post and rebooted. After the reboot, I no longer have the superuser app. How can I tell if I'm still rooted?
**EDIT**
I confirmed the ROM linked above for 8.4.4.5 is indeed rooted. I was trying to use titanium backup but it kept failing to gain superuser permissions. You'll need to manually install superuser (and busy box) from the market after flashing this rom.

combat goofwing said:
So I'm running 3.1 and dont want to downgrade to root and I have heaps of stuff on my tf,dies these mean 3.1 Rom is rooted ?
LEEDROID GB3.0.1DESIRE HD using XDA PREMIUM
Click to expand...
Click to collapse
There are rooted 3.1 roms avaiable yes. To use them you need custom recovery which can only be
install if you're rooted. So you have to downgrade first to gain root then upgrade bck to 3.1 rooted rom.
Sent from my Transformer TF101 using Tapatalk

supercurio said:
repacked-8.4.4.5_US+root-CWR-update.zip is a 3.1 ROM.
May I rename the files for faster recognition?
Click to expand...
Click to collapse
That may help, or put them in Android 3.0, Android 3.1 sub directories.
Any chance of a WW 3.1 ? Then i'm gonna give it a go.....

kingwp1 said:
I have a quick question:
I downgraded from 3.1 to 3.0, rooted, and installed CWM. When I rebooted I was rooted with the superuser app. I then installed the repacked 8.4.4.5 rom linked in the first post and rebooted. After the reboot, I no longer have the superuser app. How can I tell if I'm still rooted?
**EDIT**
I confirmed the ROM linked above for 8.4.4.5 is indeed rooted. I was trying to use titanium backup but it kept failing to gain superuser permissions. You'll need to manually install superuser (and busy box) from the market after flashing this rom.
Click to expand...
Click to collapse
Does Titanium backup require su binary be located in /system/bin instead of being in PATH? (I install the su binary in /system/xbin)

CrazyPeter said:
That may help, or put them in Android 3.0, Android 3.1 sub directories.
Any chance of a WW 3.1 ? Then i'm gonna give it a go.....
Click to expand...
Click to collapse
If you tell me where to download WW 3.1, sure I just don't where to find it

supercurio said:
Does Titanium backup require su binary be located in /system/bin instead of being in PATH? (I install the su binary in /system/xbin)
Click to expand...
Click to collapse
I don't honestly know. I just searched for superuser app in the market and downloaded and installed it normally. After you install it, you actually have to open the SU app first in order for Titanium Backup to work. Here's the app I installed:
https://market.android.com/details?id=com.noshufou.android.su
This is the version that came installed in all the roms I've ever used on my Captivate, so I figured I'd give it a try. It worked for me!
Before installing SU, Titanium Backup was unable to gain superuser permissions. Everything I've mentioned is what I've done after installing your repackaged stock rom for 3.1 and nothing else.

Oh that's right, I don't install Superuser apk correctly, I'll fix that.
So far the most important is that su binary is there already, this is the hard part

Does that mean you're going to repackage the repackaged firmware?
If so, would you recommend I reflash your new version over your previous version?

kingwp1 said:
Does that mean you're going to repackage the repackaged firmware?
If so, would you recommend I reflash your new version over your previous version?
Click to expand...
Click to collapse
Lol yeah I will
No need to reinstall anything though, you can have the exact same by installing Superuser from market like you di

Rooting Nexus S [Help]

A while back, I always rooted and unrooted my Nexus S with no problems at all. Now whenever I try to root it, it just goes wrong. I've tried TWRP & CWM, CWM used to always work but now it just messes up. Both TWRP and CWM both give me an error that say Installation Aborted when I try to install a custom rom. I've redownloaded the rom from different browsers and even different PCs but nothing working, still that same error. Does anyone have a guide that is 100% to work without any errors during the process?

What guide are you using?

paul96 said:
What guide are you using?
Click to expand...
Click to collapse
I used this one: http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/

1. Make sure you're running one the more recent versions of the custom recovery. You probably are but there are issues with older versions so just make sure.
2. Boot into what ever recovery you pick and do a full wipe. That is everything gets wiped but your SD card. Factory reset. Format /system etc.
3. Flash your ROM and gapps if they are seperate.
You should not get any errors. If your recovery is current and your flashing a new rom onto a fully wiped system and you still get a error either you're screwing something up or you may have a hardware problem.
To rule out a hw problem flash the factory images with fastboot. If those flash normally and everything works it is almost certainly user error.

albundy2010 said:
1. Make sure you're running one the more recent versions of the custom recovery. You probably are but there are issues with older versions so just make sure.
2. Boot into what ever recovery you pick and do a full wipe. That is everything gets wiped but your SD card. Factory reset. Format /system etc.
3. Flash your ROM and gapps if they are seperate.
You should not get any errors. If your recovery is current and your flashing a new rom onto a fully wiped system and you still get a error either you're screwing something up or you may have a hardware problem.
To rule out a hw problem flash the factory images with fastboot. If those flash normally and everything works it is almost certainly user error.
Click to expand...
Click to collapse
Alright, thanks Do you recommend that I root my Nexus S or should I wait for the Jelly Bean update? I've rooted before and I enjoyed it but now I don't see that many reasons to root, do you have any good reasons?

I have many. My reasons for root don't matter. If you don't have a reason for root then don't root. Its that simple really.
Make sure you're on a stock 4.0.4 rom. When the ota is out install it.
If you want just root on either os at any time just flash su.zip from custom recovery. Its that simple. Having root on a stock rom does not affect the ota process.

albundy2010 said:
I have many. My reasons for root don't matter. If you don't have a reason for root then don't root. Its that simple really.
Make sure you're on a stock 4.0.4 rom. When the ota is out install it.
If you want just root on either os at any time just flash su.zip from custom recovery. Its that simple. Having root on a stock rom does not affect the ota process.
Click to expand...
Click to collapse
What are your reasons for root? Please share?

Getting rid of stuff I don't want in a ROM.
Apps that do things that require root.Titanium backup/autoruns adaway ( ad blocker app alone could be its one point) etc
Changing kernel settings. Bid/bin clocks volts etc.
Being able to have a replacement launcher use the ICS style widget drawer.
Lastly , I simply just can't see having a computer that I don't have root/admin rights to. Its my damn device and I do what I want.

albundy2010 said:
Getting rid of stuff I don't want in a ROM.
Apps that do things that require root.Titanium backup/autoruns adaway ( ad blocker app alone could be its one point) etc
Changing kernel settings. Bid/bin clocks volts etc.
Being able to have a replacement launcher use the ICS style widget drawer.
Lastly , I simply just can't see having a computer that I don't have root/admin rights to. Its my damn device and I do what I want.
Click to expand...
Click to collapse
Oh cool. There is this project that some members from XDA are working on called Sense4All and they are porting Sense to many devices. Im probably going to wait until a fully functionable release is available for the Nexus S. I do like AOKP a lot, so that might be a reason for why I'll root.

You seem to be a little confused with some terms. Root is simply being able to grant superuser permission.
You don't need to root to flash a custom rom on a nexus. Just a unblocked bootloader. You could run aokp or any other rom without root if you wanted to.

albundy2010 said:
You seem to be a little confused with some terms. Root is simply being able to grant superuser permission.
You don't need to root to flash a custom rom on a nexus. Just a unblocked bootloader. You could run aokp or any other rom without root if you wanted to.
Click to expand...
Click to collapse
Oh, I never knew that, haha. Is it possible to flash a custom kernel with an unlocked bootloader or does that require root access?

m1l4droid said:
No you just need a custom recovery. But using that kernel's mods, like BLN, OC, UV, touchwake, etc, requires apps that need root, like NSTools, SetCPU, etc.
Click to expand...
Click to collapse
Oh alright. Now I really wanna root + install a custom rom. Do any of you have a full 100% fully working guide for rooting Nexus S and which rom should I flash first? I already know what kernel I want.

http://forums.acsyndicate.net/showthread.php?2024-ACS-Nexus-S-One-Click-Root-V4-0

leap_ahead said:
http://forums.acsyndicate.net/showthread.php?2024-ACS-Nexus-S-One-Click-Root-V4-0
Click to expand...
Click to collapse
Thank you so much! I rooted my phone with CWM recovery installed and Paranoid Android + gapps installed

[Q] Help with Rom Manager

Sorry for the noob questions but I can't seem to find a specific answer to my problem.
I am trying to create a backup of my stock Touchwiz ICS 4.0.4 using Rom manager premium v.5.0.2.1 so that I can flash CM10 to my Verizon S3. I have flashed the "ClockworkMod Recovery".
Current Recovery: ClockworkMod 6.0.1.2
Latest Recovery: ClockworkMod 6.0.1.2
Now when I try to "Backup Current ROM" my phone boots into a menu. I was under the impression that it should begin creating a Nandroid backup when I did this. It boots into Android system recovery <3e>
Word for word this is what I get
Volume up/down to move highlight:
Power button to select.
Reboot system now
apply update from external storage
wipe data/factory reset
wipe cache partition apply update from cache
_______________________________________________
# MANUAL MODE #
--Applying Multi-CSC...
Applied the CSC-code : VZW
Succesfully applied multi-CSC
From there I didn't see an obvious Create backup type of option so I chose "Reboot system now" which then booted up normally. In Rom manger there is no file under Manage and Restore backups. Do I need to choose a different option in the boot menu. I could manually make a nandroid backup I think, but I'm not sure if it would work properly since I flashed the ClockworkMod Recovery.
Sorry, I am very new to this!

How did you flash your recovery? Was it through rom manager or through ez recovery?
Sent from my VZW GS3 running Synergy/LeanKernel/Dark Horse Rises

Yeah you have the stock android recovery. (3e) Try using the "EZ-recovery for VZW Galaxy S3" app from the play store. I have always heard ROM manager can be kind of buggy.

JBO1018 said:
Yeah you have the stock android recovery. (3e) Try using the "EZ-recovery for VZW Galaxy S3" app from the play store. I have always heard ROM manager can be kind of buggy.
Click to expand...
Click to collapse
No, not at all, Rom manager works fine, but only if you flashed your recovery through it. If you used ez recovery, rom manager does not know that it has cwm recovery on it and will not operate correctly. Flash recovery through rom manager and it will work correctly. EZ is a foundation app intended to simplify recovery without rom manager. Not good if you know what your doing.
Sent from my VZW GS3 running Synergy/LeanKernel/Dark Horse Rises

annoyingduck said:
No, not at all, Rom manager works fine, but only if you flashed your recovery through it. If you used ez recovery, rom manager does not know that it has cwm recovery on it and will not operate correctly. Flash recovery through rom manager and it will work correctly. EZ is a foundation app intended to simplify recovery without rom manager. Not good if you know what your doing.
Sent from my VZW GS3 running Synergy/LeanKernel/Dark Horse Rises
Click to expand...
Click to collapse
He said he did use ROM manager to flash recovery and that it says he has CWM installed. Yet from his descripton when his phone reboots into recovery he is getting Android recovery 3e. (stock recovery) So something isnt working right. That's why I suggested ez recovery and mentioned ROM manager has been notoriously unreliable in the past for me and many other I know. It may work fine for this phone. I just, out of habit, tend to stay away from it.

JBO1018 said:
He said he did use ROM manager to flash recovery and that it says he has CWM installed. Yet from his descripton when his phone reboots into recovery he is getting Android recovery 3e. (stock recovery) So something isnt working right. That's why I suggested ez recovery and mentioned ROM manager has been notoriously unreliable in the past for me and many other I know. It may work fine for this phone. I just, out of habit, tend to stay away from it.
Click to expand...
Click to collapse
Good call!

I didn't see any mention of how he flashed his recovery, just assumed it was not through rom manager due to the issues he's having.
My experience with ez recovery made rom manager (an app I like alot) not work correctly. As soon as I re flashed through rom manager, all was well. Not knocking ez, just trying to get his rom manager app working for him.
Sent from my VZW GS3 running Synergy/LeanKernel/Dark Horse Rises

I am having the same problem. I flashed mine through Rom Manager also. It worked on the first reboot in recovery and has worked one other time in touch. Here's my thread. - http://forum.xda-developers.com/showthread.php?p=32795611#post32795611
Solutions?
If I install ez Recovery, how will that effect CWM?

I'm running the premium version of rom manager. Are you guys running the free version? I can't imagine why your having these issues, could it be related?
I originally used ez to install cwm 6.0.1.2, then used rom manager to flash the touch version of 6.0.1.2. Have not had these issues.
Sent from my VZW GS3 running Synergy/LeanKernel/Dark Horse Rises

annoyingduck said:
I'm running the premium version of rom manager. Are you guys running the free version? I can't imagine why your having these issues, could it be related?
I originally used ez to install cwm 6.0.1.2, then used rom manager to flash the touch version of 6.0.1.2. Have not had these issues.
Sent from my VZW GS3 running Synergy/LeanKernel/Dark Horse Rises
Click to expand...
Click to collapse
I got premium, I thought the same cause mine wont let me download roms either. It tells me to upgrade to the latest version.
Should we maybe uninstall and try a different install method, such as yours. Would there be any consequences?

I don't see any issues with that. To get touch through RM, there are 2 ways. One is in app purchase (don't do this, it's a one time, one use add on. Does not stay if you install a different recovery. Kind of a scam). The other is in RM you can link directly to cwm site and dl the apk for free. Just be sure you get the one for our phone, the site page is a little weird to navigate. Then you have it forever.
Sent from my VZW GS3 running Synergy/LeanKernel/Dark Horse Rises

This might be your problem, see if you gave the file mentioned in the last post and delete it.
http://forum.xda-developers.com/showthread.php?p=32346811
Sent from my S3 running Eclipse 2.1

kintwofan said:
This might be your problem, see if you gave the file mentioned in the last post and delete it.
http://forum.xda-developers.com/showthread.php?p=32346811
Sent from my S3 running Eclipse 2.1
Click to expand...
Click to collapse
What file? Im still noob confused about all of this. S-P-E-L-L it out. Can I just go ahead and do ez now or do I need to do anything to RM
Thanks for your help, its greatly appreciated.

travis.bridges10 said:
What file? Im still noob confused about all of this. S-P-E-L-L it out. Can I just go ahead and do ez now or do I need to do anything to RM
Thanks for your help, its greatly appreciated.
Click to expand...
Click to collapse
Just try ez recovery first and see if it works, its in the play store. If it doesn't I'll try to find the exact path of the file. I'm not stock so its hard I'll have to search for it
Sent from my S3 running Eclipse 2.1

kintwofan said:
Just try ez recovery first and see if it works, its in the play store. If it doesn't I'll try to find the exact path of the file. I'm not stock so its hard I'll have to search for it
Sent from my S3 running Eclipse 2.1
Click to expand...
Click to collapse
It worked the first time I rebooted from RM, then I tried to enter manual recovery and it went to android recovery, then I tried RM reboot to recovery and it went into android recovery. Do I need to back it up before I reboot? It seems like the reboot in recovery right after a flash works, but then looses it after reboot.
I still have the problem also of it not allowing me to download roms, says I need to upgrade to latest version.

travis.bridges10 said:
It worked the first time I rebooted from RM, then I tried to enter manual recovery and it went to android recovery, then I tried RM reboot to recovery and it went into android recovery. Do I need to back it up before I reboot? It seems like the reboot in recovery right after a flash works, but then looses it after reboot.
I still have the problem also of it not allowing me to download roms, says I need to upgrade to latest version.
Click to expand...
Click to collapse
Then that file needs deleted. I'll try to find it.
But the easiest fix would be to download whatever ROM you want directly from the forum. Use Ez recovery and in that first boot into recovery flash the ROM you downloaded following the instructions in the ROMs post.
Sent from my S3 running Eclipse 2.1

kintwofan said:
Then that file needs deleted. I'll try to find it.
But the easiest fix would be to download whatever ROM you want directly from the forum. Use Ez recovery and in that first boot into recovery flash the ROM you downloaded following the instructions in the ROMs post.
Sent from my S3 running Eclipse 2.1
Click to expand...
Click to collapse
ok... Thats probably what ill do then. I have to do some more reading on flashing roms... I dont want anymore problems. I got three more questions for you since youve been so helpful.
1. Any idea why its not letting me get into the download ROMS in RM. Saying I need to upgrade to the latest version of RM
2. Im sure I could find the answer to this but Ill ask since I got you here. I just went through over the last few days adding a lot of customizations, like nova, widgets, widgetlocker, tasker, etc. When I do flash a new rom whats the most efficient way to transfer apps, settings, designs, etc
3. If I was to keep the stock ROM what happens with VZW OTA updates. Doesnt it mess things up. This last update has messed everything up for GS3's and I bet the next will have even more "restrictions"
Thanks again

travis.bridges10 said:
ok... Thats probably what ill do then. I have to do some more reading on flashing roms... I dont want anymore problems. I got two more questions for you since youve been so helpful.
1. Any idea why its not letting me get into the download ROMS in RM. Saying I need to upgrade to the latest version of RM
2. Im sure I could find the answer to this but Ill ask since I got you here. I just went through over the last few days adding a lot of customizations, like nova, widgets, widgetlocker, tasker, etc. When I do flash a new rom whats the most efficient way to transfer apps, settings, designs, etc
Thanks again
Click to expand...
Click to collapse
1. I don't use RM so can't be much help there.
2. I personally use titanium backup to back up and restore user apps. I don't recommend restoring system settings.
Sent from my S3 running Eclipse 2.1
---------- Post added at 09:02 PM ---------- Previous post was at 08:52 PM ----------
One either thing make sure you backup your imie...there's a guide in the development section.
Sent from my S3 running Eclipse 2.1

I figured it out earlier. When you do the first reboot the recovery menu gives you the option to disable stock recovery from flashing. Select it and it's been working fine since.
Sent from my SCH-I535 using xda app-developers app

travis.bridges10 said:
I figured it out earlier. When you do the first reboot the recovery menu gives you the option to disable stock recovery from flashing. Select it and it's been working fine since.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Good. I don't remember seeing that option, but I've been rooted for a while.
Sent from my S3 running Eclipse 2.1

[Q] Superuser not installing

I have one problem. When I try to install new ROM, the recovery (TWRP) says that my device isn't rooted (I tried it on few ROMs, always the same...). Also, in the things that are shown when the ROM is installing (like mounting data, system, installing system files etc.) ins't installing superuser (I think that should be there)
Is there somebody to help me? Thank you...

XTheMike said:
I have one problem. When I try to install new ROM, the recovery (TWRP) says that my device isn't rooted (I tried it on few ROMs, always the same...). Also, in the things that are shown when the ROM is installing (like mounting data, system, installing system files etc.) ins't installing superuser (I think that should be there)
Is there somebody to help me? Thank you...
Click to expand...
Click to collapse
TWRP search whether the superuser app is install in your phone or not,and roms like cyanogenmod have a inbuilt superuser ,so you should ignore that. :highfive:

But it seems to be.happening only on sense based roms... And it won't boot either I install it or not...

XTheMike said:
But it seems to be.happening only on sense based roms... And it won't boot either I install it or not...
Click to expand...
Click to collapse
Search for super su apk in xda you will find it..
flash the rom.. after completing flash the super su reboot..

XTheMike said:
But it seems to be.happening only on sense based roms... And it won't boot either I install it or not...
Click to expand...
Click to collapse
and here comes a superuser zip out of nowhere

Thanks for your help It works now...

If you flash a custom rom on your phone, will it wipe the root?

Hey, im pretty new to rooting and stuff, and i've already rooted my phone. But if I flash a custom ROM on my phone, will it wipe the root? (I have an HTC One M8)

ViperVenom2000 said:
Hey, im pretty new to rooting and stuff, and i've already rooted my phone. But if I flash a custom ROM on my phone, will it wipe the root? (I have an HTC One M8)
Click to expand...
Click to collapse
Yes, it will wipe the root! I suggest you flash a CM based ROM since its got root toggle inbuilt in its developer settings. Cheers ?

sw1tchback said:
Yes, it will wipe the root! I suggest you flash a CM based ROM since its got root toggle inbuilt in its developer settings. Cheers
Click to expand...
Click to collapse
Thanks!

sw1tchback said:
Yes, it will wipe the root! I suggest you flash a CM based ROM since its got root toggle inbuilt in its developer settings. Cheers
Click to expand...
Click to collapse
So, something like this http://forum.xda-developers.com/showthread.php?t=2753248? WIll that have root? And, can you install superuser (Any version of Superuser) on any android version safely?

Well I'm very new at this as well and I see now that the road from sitting on your couch googling what is rooting to becoming a super hacker is a long one, I think I can help. With that being said I could be wrong too so research everything and double check. If you have root access before you do anything else install a custom recovery. I suggest TWRP. Then you want to focus on learning to create nandroid backups and Titanium backups. That way when things go awry all is not lost. THEN you can go for the ROMs. Research how to wipe your device properly with each flash. This is pretty important. TWRP recovery automatically tells you when your wipe has unrooted your device and gives you root again. May I ask is your bootloader already unlocked?

ViperVenom2000 said:
Thanks!
Click to expand...
Click to collapse
I'm always there to help?
---------- Post added at 07:15 AM ---------- Previous post was at 07:09 AM ----------
ViperVenom2000 said:
So, something like this http://forum.xda-developers.com/showthread.php?t=2753248? WIll that have root? And, can you install superuser (Any version of Superuser) on any android version safely?
Click to expand...
Click to collapse
Yeah the ROM you mentioned should work fine for your device. Just follow the instructions in the guide step by step and all should go well. And yes, you'd have root inbuilt since its a CM based ROM, just enable Developer Options in settings and toggle Root Access in it to 'Apps only' or 'Apps and ADB'. I prefer using Chainfire's SuperSU, it should work well with your ROM. Good Luck Flashing ??
EDIT: I just noticed, the ROM you mentioned is a pretty old one. I suggest you flash CM 13 running Android 6.x Marshmallow, there is an official build for your device here: http://forum.xda-developers.com/showthread.php?t=3256696
Check it out!

Thanks all! I found it out. I've unlocked my bootloader, and installed TWRP. Then, made a complete ROM Backup in case everything screws up. (I stored the backups and a stock ROM on a micro-SD card) Then, I installed a custom ROM running a CM based android Marshmallow (http://forum.xda-developers.com/showthread.php?t=2753248), along with the Google Play apps .zip. Then, made a backup again, and now I'm all set! I think I will still delve into finding the best ROM for me! And all without bricking my phone. I also was successfully able to root my LG G Pad 7.0 LTE using Purple Drake with a special version of TWRP. Again, thanks for all the help! (The next thing I need to do is figure out how to Dual-Boot custom ROMs...)