First post, and already I'm confused and lost. Off to a good start, yes?
Firstly, greetings all. Nice to meet you.
Secondly, I today managed to acquire a very special and so far beloved Asus EEE Transformer TF101, so, tell me, what can make this Transformer even better?
Why, gaining root access, of course!
I've had a HTC sensation for about seven-ish months now, installed many things on it, and avoided bricking it (somehow), so I'm not entirely new to this process. However, the entire process of rooting the Transformer is getting a bit confusing.
After using Google (yay!) to my advantage, I eventually came across this thread:
http://forum.xda-developers.com/showthread.php?t=1366743
"EASY!" I thought.
...until I discovered my current build number is "8.6.5.21".
So, using the above thread, I got redirected to this thread:
http://forum.xda-developers.com/showthread.php?t=1417006
At this point, things started going downhill.
I read through the steps of the latter thread, which were:
" Get Razorclaw and install it, no root needed."
Done.
"- Get the recovery installer and do the same."
"The Recovery"? My first question comes here, what recovery do I want? Do I go for the straightforward CWM?
My second question is, how am I meant to install a recovery without first rooting my device?
"- Check your version info. You'll see a pair of letter which are like the "WW"[...]"
My version says "WW_epad-etc" so I assume that's sorted.
"- Follow the instructions regarding downloading the .13 update (WW version and/or whatever letter pair your tablet uses, in case the WW doesn't work)."
To this, I assume "pjfriend" refers to the first thread. So I go to it, and open this link. This link works fine, however...
image
How am I meant to downgrade(upgrade?) to Version 8.6.5.13 when it's only designed for a JP "SKU", and I have a WW "SKU"?
"Unzip, slap on external SD, power off, power on with down volume, volume up to go to recovery, bang. Done."
Again, if I have no recovery installed due to being unable to root due to being unable to update my build number, how am I supposed to boot into recovery?
"- Do the same thing with the megaupload file (.19)."
No root :<
"The second option did fix the problem I had, which was trying to update to a WW.19 firmware from a US.13 - DO THE DOUBLE FILE/RENAME TRICK. It works perfectly."
I'm unsure as to what the "second option" he refers to is, and what the "double file/rename trick" is. Any ideas?
"- Run razorclaw, run recovery installer, and gloat."
Wait... so... NOW I run the recovery installer? :/
Darn my build version, it could be as easy as installing an APK and finishing!
My final aim is to install AOKP, and use that, which of course I need root for.
So, for my last trick, do I need to install any firmware for AOKP?
For my really last trick, anything else I should know?
Thanks in advance, apologies for the wall of text.
All best,
Valky.
1- Vipermod
2- Gnufabio's Recovery Installer
3- Factory Reset
4- Flash AOPK
mrevankyle said:
1- Vipermod
Click to expand...
Click to collapse
Thanks very much, however, from what I understand Vipermod is built for the Transformer Prime. Does it work on the non-prime variant?
It will work for rooting only and not installing cwm. Use Recovery Installer for that. Worked fantastic for me on 9.2.1.17.
Sent from my GT-I9100 using XDA
Yes, I used vipermod option 1 to root my tf101.
Valkorian said:
Thanks very much, however, from what I understand Vipermod is built for the Transformer Prime. Does it work on the non-prime variant?
Click to expand...
Click to collapse
ViperMod, use option 3 since you're still on HC firmware.
Thanks a lot, all of the above, looks a lot less difficult than I was making it.
Last question:
"Plug in your Transformer"
Check.
"and make sure to install the drivers located in the included .zip"
How would I do this? After plugging in the Tablet, Windows automatically installed the driver software successfully. Is that it already done, or do I need to do anything in particular before running Vipermod?
Valkorian said:
Thanks a lot, all of the above, looks a lot less difficult than I was making it.
Last question:
"Plug in your Transformer"
Check.
"and make sure to install the drivers located in the included .zip"
How would I do this? After plugging in the Tablet, Windows automatically installed the driver software successfully. Is that it already done, or do I need to do anything in particular before running Vipermod?
Click to expand...
Click to collapse
If your PC recognized you TF, you're good to go.
In case the ViperMod process doesn't work for some reason, update the driver to
the one in the folder.
Thanks a bunch, super easy, sorted, rooted, everything's going fantastically.
Hopefully, I shall be able to help someone else in return. Thank you all once again!
Valkorian said:
Thanks a bunch, super easy, sorted, rooted, everything's going fantastically.
Click to expand...
Click to collapse
Great. I highly recommend using Recovery Installer to install Rogue XM CWM Recovery. Its the only version that supports the external micro SD card. There are far to many posts about problems with others especially ROM Manager.
Sent from my GT-I9100 using XDA
I'm afraid that "one last thing" isn't coming around as quickly.
After sucessfully rooting my device (thanks all!), I've installed titanium backup, backed up the few apps I installed, enabled root access on ES File Explorer, given super user permissions, all that...
Unfortunately, it seems the recovery installer insists I'm not rooted. It just flashes for a second, and then I get a message saying "Sorry, you are not rooted!"
Have I done something wrong?
Also, I have no external SD card in the device currently, but I have the 8 gig one from the old Sensation. Is that required?
Tried various things, but it seems that Recovery Installer just doesn't want to listen. Is there any other way to install a recovery, either manually or automatically, and other than ROM manager? I used 4ext/TWR on my Sensation, so I'm unused to using other things.
And now I'm being asked to update my firmware, I have two more postpone chances. Should I accept?
Valkorian said:
I'm afraid that "one last thing" isn't coming around as quickly.
After sucessfully rooting my device (thanks all!), I've installed titanium backup, backed up the few apps I installed, enabled root access on ES File Explorer, given super user permissions, all that...
Unfortunately, it seems the recovery installer insists I'm not rooted. It just flashes for a second, and then I get a message saying "Sorry, you are not rooted!"
Have I done something wrong?
Also, I have no external SD card in the device currently, but I have the 8 gig one from the old Sensation. Is that required?
Tried various things, but it seems that Recovery Installer just doesn't want to listen. Is there any other way to install a recovery, either manually or automatically, and other than ROM manager? I used 4ext/TWR on my Sensation, so I'm unused to using other things.
Click to expand...
Click to collapse
Look in system/bin and copy the su to system/xbin
Valkorian said:
And now I'm being asked to update my firmware, I have two more postpone chances. Should I accept?
Click to expand...
Click to collapse
clear data for DMClient app
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks a lot guys. I wouldn't have been able to done it without you, hopefully I shall, in turn, be able to help others.
Thanks a plenty. You've made one happy person, all of you.
Related
I put together a diagram image showing how the file structure for how to take the various update.zip files to flash your rom or add functionality not obtainable via apk files or market. It was suggested we have a faq using this image to describe this process. I have only done this 3 times so I hope this is correct!
The basic thing it needs to explain is:
1. how to load up the filesystem with the update zip file and command file
Here is a diagram that shows either of the 2 methods to make this work, you can download zip files from Viewsonic's TNT page and just rename them to update.zip (then you have to create the recovery folder and command file), or you can download files here, some are rar'd which means the actual zip has been zipped/rar'd again, just extract it out, and if there are no recovery/command, you have to create them. A trick I use is to have this structure already defined on my laptop as a staging area, then I can just copy over a zip and a folder over to my device or sdcard.
I personally don't know how all this works, I believe the device first looks to the microSD card first for the recovery command file, then over to the internal storage for the same, but I could be wrong.
NOTE 1: Just make sure that if you use the external sd card, you have the correct command file notation (SDCARD2 not SDCARD).
NOTE 2: There are TWO dashes at the start of the command file contents, the image doesn't show it well (--update_package=SDCARD:/update.zip) or (--update_package=SDCARD2:/update.zip)
NOTE 3: This command file has NO file suffix, it is a text file, but make sure it is named command
NOTE 4: After a recovery is invoked, the process will have removed your command file (whether it was successful or not), and you will have to replace it when you are ready to flash again. A trick you might like is to copy the command file to command.bak, and each time you want to flash, just copy the bak file to command so you don't have to upload it each time. It is safest just to recopy the update.zip and command files back into their respective places each time you plan on reattempting recovery, just to make sure both files have the appropriate content.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. how to boot into recovery
Power down the unit. Once it has gone blank, press and hold the Vol +, then press and hold the power button
3. how do you know recovery is booting up (Text at the top of the screen)
You should see tiny text in the upper left that says "Detect a Recovery Key Pressed", and then a 2nd line that reads "Recovery Image Detected", or something to that effect.
4. how do you know recovery did not see either the update.zip or command file or both (exclamation mark, plus no changes after reboot)
I have not personally hit this yet, but if you don't see a cardboard box logo in the middle of your screen with a progress bar at this point, chances are you have something incorrect. If you don't see any changes or see an exclamation point, then you don't have the filesystem exactly as described in the diagram in #1. Or your update.zip file isn't really the proper file, maybe you took a RAR file and just renamed it, etc. If you open the zip file, you should not see any zip files, but IMG files or BIN files or SYSTEM folders, etc.
Now, if you identify the issue and resolve it and are about to run another recovery cycle, take a look at #1 NOTE #4 above...
Hope this helps!
Thanks so much, this will be a time saver for us devs. A great reference for getting clockwork installed, or for people who don't want to use clockwork.
Stuck because it's worth it
Yeah, thanks.. Might keep me from answering the same question 52 bazillion times.....
you should add a note that the command file will be deleted after it has been run, regardless if the update occurred or not - always double check that the (correct) command file is there or you will get the exclamation point
brian_h_kim said:
you should add a note that the command file will be deleted after it has been run, regardless if the update occurred or not - always double check that the (correct) command file is there or you will get the exclamation point
Click to expand...
Click to collapse
Good point, I will add it. What folks could do (I have done this) is to make a file called command.bak, and you can just copy that to command every time you want to flash.
TeamSpeed said:
Good point, I will add it. What folks could do (I have done this) is to make a file called command.bak, and you can just copy that to command every time you want to flash.
Click to expand...
Click to collapse
Or just install Clockwork 0.8 and be done with the recovery folder/command file all together.
Sprdtyf350 said:
Or just install Clockwork 0.8 and be done with the recovery folder/command file all together.
Click to expand...
Click to collapse
some people may not want to use CWM as it breaks OTA updating
brian_h_kim said:
some people may not want to use CWM as it breaks OTA updating
Click to expand...
Click to collapse
I understand and also know that some people like driving without tires too. Doing an update via OTA is way overrated. All I am saying is the benefits that can be gained by installing clockwork outweigh the negatives of not.
As soon as the OTA update comes out someone here will have the download location in seconds. That download can be installed from clockwork just like any other update file. Why Viewsonic doesn't just supply the file on there site is beyond me.
So... not running clockwork so you can wait for an update that comes every other month, or maybe never again versus having the security of easy to perform backups, the ability to easily install updates, fix the inevitable boot loop, mount storage, etc just doesn't make sense to me...
Sprdtyf350 said:
I understand and also know that some people like driving without tires too. Doing an update via OTA is way overrated. All I am saying is the benefits that can be gained by installing clockwork outweigh the negatives of not.
As soon as the OTA update comes out someone here will have the download location in seconds. That download can be installed from clockwork just like any other update file. Why Viewsonic doesn't just supply the file on there site is beyond me.
So... not running clockwork so you can wait for an update that comes every other month, or maybe never again versus having the security of easy to perform backups, the ability to easily install updates, fix the inevitable boot loop, mount storage, etc just doesn't make sense to me...
Click to expand...
Click to collapse
having a choice is better than not having a choice
I keep a complete library of files on a separate storage, and I only copy over what I want on the tablet. Just because you may like cwm,doesn't mean everybody does or will. This works just fine for me, and I am sticking with the stock OS until viewsonic stops supporting it, which means I wait for the ota updates.
TeamSpeed said:
I keep a complete library of files on a separate storage, and I only copy over what I want on the tablet. Just because you may like cwm,doesn't mean everybody does or will. This works just fine for me, and I am sticking with the stock OS until viewsonic stops supporting it, which means I wait for the ota updates.
Click to expand...
Click to collapse
And like the post above says.. Choice is good. If what you are doing works for you that's great.
It is not so much whether I like, or dislike clockwork. It is just a tool. For someone that buys a tablet, has no intention of doing anything but using it as it came, no clockwork is fine. But for those that want to keep the stock firmware but play around and add all the little updates, fixes, apps, or even play with all the other roms then I think you do yourself a disservice by not using clockwork. One of those things you do to your tablet will eventually end up in a bootloop. Or something you installed will not work and you will want to revert back to what you had before. You can't fix that with the stock recovery, but you can do it with clockwork.
Not trying to start an argument. I just see many advantages to using it versus not.
I think a lot of people don't want to use it because they are afraid of breaking there tablet. Installing a lot of different things available here, and other places is much more scary... And without a viable backup, or recovery method can be a real pain to fix.
Wanting to keep your tablet stock is fine. But if you bought a car that came stock with no brakes, I guess you could drive it. But if there was a really simple method to add brakes to augment your feet wouldn't you want them? Maybe not.. But I do...
I am glad you took the time to write this guide. Even though it is listed all over these forums how to do what you wrote it seems people don't read much anymore. So hopefully it will help some folks...
Sprdtyf350 said:
Wanting to keep your tablet stock is fine. But if you bought a car that came stock with no brakes, I guess you could drive it. But if there was a really simple method to add brakes to augment your feet wouldn't you want them? Maybe not.. But I do...
Click to expand...
Click to collapse
I like this point so much!
TeamSpeed said:
Good point, I will add it. What folks could do (I have done this) is to make a file called command.bak, and you can just copy that to command every time you want to flash.
Click to expand...
Click to collapse
I've only used the latest version, but have noticed a behavior not covered here:
rather than deleting the /recovery/command file, it deletes the contents of the file. This seems to happen whether or not the update actually happens.
mwmeyer said:
I've only used the latest version, but have noticed a behavior not covered here:
rather than deleting the /recovery/command file, it deletes the contents of the file. This seems to happen whether or not the update actually happens.
Click to expand...
Click to collapse
I can't remember on whether or not it happens when it doesn't actually run the update. However, it has always deleted the command file for me.
/recovery/command
ends up
/recovery/
Can't root into gtablet
Ok fellas I must be super retarded. For sOme dumb reason I can not add colckwork or TNT or root into my g. I've tried everything and the stock g sucks bad. I am used to the apple firmwares. This is my first droid product so bare with me. I've used winscp to hack into my root folder but I can't into my gtablet. Please help I need to hack my tab. Any suggestions?
scopes44 said:
Ok fellas I must be super retarded. For sOme dumb reason I can not add colckwork or TNT or root into my g. I've tried everything and the stock g sucks bad. I am used to the apple firmwares. This is my first droid product so bare with me. I've used winscp to hack into my root folder but I can't into my gtablet. Please help I need to hack my tab. Any suggestions?
Click to expand...
Click to collapse
Some of this may be outdated now but it will get you started. Read Read Read....
http://forum.xda-developers.com/showthread.php?t=874258
http://forum.xda-developers.com/showthread.php?t=865245
http://gtabfans.com/
scopes44 said:
Ok fellas I must be super retarded. For sOme dumb reason I can not add colckwork or TNT or root into my g. I've tried everything and the stock g sucks bad. I am used to the apple firmwares. This is my first droid product so bare with me. I've used winscp to hack into my root folder but I can't into my gtablet. Please help I need to hack my tab. Any suggestions?
Click to expand...
Click to collapse
Read this thread
http://forum.xda-developers.com/showthread.php?t=865245
The first post
Upgrade malata Zpad to Viewsonic Gtab
Thank you for your instruction.
Now, I can upgrade Malata Zpad to Gtab
upgrade Malata Zpad to Gtab
Thank you for your instruction.
Now, I can upgrade Malata Zpad to Gtab (gtab.VEGAn.1.00.beta5.1.user.final.zip).
And it's work find.
Alright... i keep reading about this KIES deal... since its windows native, i cant install that.
So i need some help...
Im wanting to know how to load a flashing system... and which one...
then wanting to load Infused v1.
Im doing this all from Ubuntu 10.10
__________
Im already rooted, along with the current (stable) BusyBox loaded... so i got that far.
i just wanna know what i gotta do, cause everything seems to rely on this KIES deal, and i dont have that.
I guess im asking for a walk-through... if anyone is willing to help?
re: Ubuntu
Ph0z3 said:
Alright... i keep reading about this KIES deal... since its windows native, i cant install that.
So i need some help...
Im wanting to know how to load a flashing system... and which one...
then wanting to load Infused v1.
Im doing this all from Ubuntu 10.10
__________
Im already rooted, along with the current (stable) BusyBox loaded... so i got that far.
i just wanna know what i gotta do, cause everything seems to rely on this KIES deal, and i dont have that.
I guess im asking for a walk-through... if anyone is willing to help?
Click to expand...
Click to collapse
Kies is not required for what you want to do, but without knowing
if your Ubuntu OS can reconize your phone as an external USB
flash drive device and or if you have a microUSB card reader and a
microUSB memory card in your phone its difficult to tell you the
exact step by step way to flash roms to your phone.
I can help, but I do need to know these things first.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Have a great day,
Enjoy!
Please don't forget to give me a big THANKS if this was worthwhile reading!
Ph0z3 said:
Alright... i keep reading about this KIES deal... since its windows native, i cant install that.
So i need some help...
Im wanting to know how to load a flashing system... and which one...
then wanting to load Infused v1.
Im doing this all from Ubuntu 10.10
__________
Im already rooted, along with the current (stable) BusyBox loaded... so i got that far.
i just wanna know what i gotta do, cause everything seems to rely on this KIES deal, and i dont have that.
I guess im asking for a walk-through... if anyone is willing to help?
Click to expand...
Click to collapse
If you have all that just download the rom zip, place on SD, reboot into recovery, install zip from SD, choose the zip you desire and then select yes and wait .
Sent from my SAMSUNG-SGH-I997R using XDA Premium App
Ph0z3 said:
Alright... i keep reading about this KIES deal... since its windows native, i cant install that.
So i need some help...
Im wanting to know how to load a flashing system... and which one...
then wanting to load Infused v1.
Im doing this all from Ubuntu 10.10
__________
Im already rooted, along with the current (stable) BusyBox loaded... so i got that far.
i just wanna know what i gotta do, cause everything seems to rely on this KIES deal, and i dont have that.
I guess im asking for a walk-through... if anyone is willing to help?
Click to expand...
Click to collapse
first dont ask questions in dev
next kies does nothing but install drivers for the infuse. you.have ubuntu. you.dont need drivers.
what you need is cwm to flash roms and heimdall to return to stock.
google heimdall download. get the frontend package and the backend package and install. you may need to set permissions.as executable.
for.cwm the easiest way is to use heimdall to push a kernel to the.phone. download the comunity kernel. extract the .zip and place the zimage in the kernel slot in heimdall
the phone needs to be in download mode look it up.
alternatively yu can use sgs kernel flasher. get it in android market. that app is self explainatory.
there is another way we used before we had these cool custom kernels but i wont get into that.
re: flashing rom
VtHondaGuy08 said:
If you have all that just download the rom zip, place on SD, reboot into recovery, install zip from SD, choose the zip you desire and then select yes and wait .
Sent from my SAMSUNG-SGH-I997R using XDA Premium App
Click to expand...
Click to collapse
My, the way you explain things so fast, complete and with
such few words....... I never seen anything like it!
For me to explain the same thing you have just now would
take me well over a hundred words for sure
Have a great day,
Enjoy!
VtHondaGuy08 said:
If you have all that just download the rom zip, place on SD, reboot into recovery, install zip from SD, choose the zip you desire and then select yes and wait .
Sent from my SAMSUNG-SGH-I997R using XDA Premium App
Click to expand...
Click to collapse
lol, he never said he has clockwork mod.
op pm me if you have trouble. i run mint 10kde. its basdically identical to ubuntu kde edition. i havent run gnome in a while but i think i can still help.
I've used heimdall on my install of ubuntu and it works fairly well. 1.3.0 should be compatible with 10.10
Misterjunky said:
My, the way you explain things so fast, complete and with
such few words....... I never seen anything like it!
For me to explain the same thing you have just now would
take me well over a hundred words for sure
Have a great day,
Enjoy!
Click to expand...
Click to collapse
LOL I'm a chef so I do everything at light speed! Id go more into depth but its 4:56am and I have to be at work in 6 hours.
Sent from my SAMSUNG-SGH-I997R using XDA Premium App
hmm,. i just updated to heimdall 1.3.0 im not sure i like it.
i prefer 1.1.0. it was very strait forward.
edit: after further use i definately prefer v1.1.0, 1.3 isnt as friendly for flashing kernels. it wants a firwamre.xml file in the .tar or something, i need to read up on the new heimdal, the old one let you flash the different partitions individually. and the files were not .tar achives, you just extracted the images from the odin packages.
im sure the new version has its purpose but for simplicity id say get 1.1.1. the 1.1.1 frontend package seems to work over the 1.2 comandline package.
v1.3 seems to be for compatability with future devices(or current ones) that have a different partition table, the firmware.xml file can specify what device the files get flashed to. this is more advanced and not for everyone.
Dani, just go to the "Flash" tab. The old style of doing things is still there.
LinuxBozo said:
Dani, just go to the "Flash" tab. The old style of doing things is still there.
Click to expand...
Click to collapse
thanks linux, but i couldnt see how to insert the files. it lets me search for a pit but nothing else.
does the phone need to be connected first?
does it now require a pit before the other files?(i cant get the unbrick ackage to download at this time to test that)
should it be in a .tar file or still extracted like it was before?
Misterjunky said:
I can help, but I do need to know these things first.
Click to expand...
Click to collapse
Like i said... i have NOTHING as far as recovery, flash software, ect... Im rooted and thats it.
When i plug my phone in, and enable USB, it sees my internal & external memory separately, so im good to go.
So if you could help me though this, that would be spectacular.
Hell... i might even be cool and donate you a few bucks on PayPal
What you might want to look into are the "Odin" flashable ROM packages - these will at least get you root and CWM recovery.
The Ubuntu equivalen of Odin is Heimdall, as mentioned previously. There are a few tricks to flashing a complete Odin firmware package with heimdall, next time I'm at my Ubuntu box I'll go into more detail.
To use Odin/Heimdall, once you've got them set up and have something to flash - turn off your phone, and then hold VolUp and VolDn at the same time while plugging in the USB cable to the phone. A yellow screen with an Android doing construction work will appear.
Edit: And Heimdall 1.3.0 is just as easy to flash kernels with as 1.1.0... 'heimdall flash --kernel zImage' (I don't use the GUI frontend ever)
Ph0z3 said:
Like i said... i have NOTHING as far as recovery, flash software, ect... Im rooted and thats it.
When i plug my phone in, and enable USB, it sees my internal & external memory separately, so im good to go.
So if you could help me though this, that would be spectacular.
Hell... i might even be cool and donate you a few bucks on PayPal
Click to expand...
Click to collapse
no donation needed.
Ubuntu doesn't need any special packages or drivers on these phones at all.
actually a heimdall install on ubuntu iis a lot easier than an Odin install in windows, there are never driver issues. infact Ubuntu is eaiser to install than windows so all these Mac users doing the vm thing with windows and Odin are making life hard for themselves.
you can get cwm recovery by flashing a voodoo kernel. this can be done in heimdall (1.1.1 is self explanitory, 1.3.0 might need some explaining but I figured it out so feel free to ask if you need to.) the kernel can also be flashed in a market app called sgs kernel flasher.
Entropy512 said:
Edit: And Heimdall 1.3.0 is just as easy to flash kernels with as 1.1.0... 'heimdall flash --kernel zImage' (I don't use the GUI frontend ever)
Click to expand...
Click to collapse
but us linux newbs like the gui, it reminds us of windows.
but yeah, you're right that is easy.
the new gui requires a pit to flash individual partitions. I found it odd. but its not too difficult.
re: flash custom rom
Ph0z3 said:
Like i said... i have NOTHING as far as recovery, flash software, ect... Im rooted and thats it.
When i plug my phone in, and enable USB, it sees my internal & external memory separately, so im good to go.
So if you could help me though this, that would be spectacular.
Hell... i might even be cool and donate you a few bucks on PayPal
Click to expand...
Click to collapse
First download this cwm recovery kernel here:
http://www.mediafire.com/?srhipjqvy7mpdde
Then rename the downloaded zip file to "update.zip"
and copy it to root of your INTERNAL SD card.
Now boot to the blue text recovery screen of your phone
pressing the up/down and power keys at the same time
then after 10-15 seconds letting go.
If you have trouble getting into the stock blue recovery
menu you can go to the market and download a free
app called "reboot recovery" that way you can go to
the recovery menu with one click.
After you are in the blue recovery menu select "reinstall packages"
You may have to do this twice the first time, then you will see the
clockworkmod recovery menu and you will be ready to flash a
custom rom.
I do now know which custom rom you want to download, so go
ahead and download a custom rom of your choice (must be a zipfile)
and then copy the custom rom zipfile to the root of your internal
sdcard.
After that reboot the phone into recovery using the "reboot recovery"
app or by pressing vol up/down and power keys after the phone is off.
Then you get to the cwm recovery menu and select
"install zip from sd card" then you will see the files in sdcard.
Select the custom rom zipfile from the the menu by going up/down
on list using vol up and vol down buttons. When you highlight the
file you want press the power button and let it start flashing
the custom rom.
On first bootup on custom rom it usually takes twice as long
to complete the boot process.
If you have any questions, let me know.
Good luck, and yes a donation is always welcome
Have a great day,
Enjoy!
alright... got it loaded...
-phone didnt catch fire.
-the sketchy beaner down the road hasnt stolen my car yet
-i still have 1/2 a pot of tea left...
:: UPDATE ::
STEP 9) Press OK and hold your breath. When 3e recovery comes up, just select reinstall packages.
yeah... i never got that... is that an issue?
2nd thing, was kinda hoping it would be a bit louder... since it has voodoo sound. I DLed the FREE manager, but it doesn't seem any different...
3rd thing, how do i change the lock screen back to the default? (just the large pane, instead of the sliders)
That aside... now that ive had it up and running for a few hours and able to play online and play games to really test it. I really like it. nice and smooth, quick as hell too!
@MisterJunky - It appears my PayPal was attacked, so once i get it sorted and un-frozen, ill send ya a few bucks for helping me.
help on my previous.... anyone?
.....?
voodoo sound is mainly for recording and headphones( headphones more so than recording) . it had no effect on the external speaker.
First and foremost I take no responsibility to what this update package will do to your device. That being said I have tried this successfully on multiple rooted tablets running US 8.6.5.6.
Long story short if your rooted this will update you to 8.6.5.9 and update your CWM to 3.2.0.1 provided by Roach2010. Simply download to root of sdcard and flash through CWM.
All credit goes to Roach2010 and the package he provided for the 3.2 upgrade.
UPDATE: This is for Rooted stock firmware only, if you applied Netflix patch or any other mod's this will fail. Revert your changes and then give this a shot.
UPDATE2: Added the WW package but I can't test this. Please let me know how it goes.
Nice, waiting for WW version also
Sent from my Transformer TF101 using Tapatalk
Remember !!!!
If you already apply Netflix patch You cant update. (MD5 error) Using root explorer go to system/lib and rename
libnvomx.so file to libnvomx.so.tmp
and
original libnvomx.so.bak file to libnvomx.so.
After Update using CW mode ( Remember to mount all before)
*** [when you update nexflix patch last time this file replace to XOOM's libnvomx.so file. Thats why you need to do this.]***
rufik said:
Nice, waiting for WW version also
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
If someone can get me the WW package I can cobble something together. I won't be able to test however since I am on US.
Let me know.
Backing up now to try. I tried the unroot and update method but it kept failing, im betting some file I modified (like the Xoom SystemUI) or something I deleted is pissing it off. Hopefully this resolves it.
I never did the netflix patch so I should be good right? I should be able to run this, sideload netflix and party all the time?
I un-rooted, trying to get the update ... will this still work ?
nolf3 said:
I un-rooted, trying to get the update ... will this still work ?
Click to expand...
Click to collapse
If you unroot that why you did'n update original one. I saw some one upload in another thread. I think this is only for rooted one and this is modified version.
I was able to install this, it appears to have updated my build. I did run into some issues where it got mad because I had uninstalled the ASUS programs that it wanted to update but once I pasted those back in it ran fine (i of course then deleted them again).
Now I just need to clear this firmware thing. It keeps asking me to update
Ryan, did you install this while un-rooted ? since you mention you tried the unroot and update method - which is what i tried too
ryan stewart said:
I was able to install this, it appears to have updated my build. I did run into some issues where it got mad because I had uninstalled the ASUS programs that it wanted to update but once I pasted those back in it ran fine (i of course then deleted them again).
Now I just need to clear this firmware thing. It keeps asking me to update
Click to expand...
Click to collapse
Just run the firmware and it will fail. Reboot and the notice will go away. How I did it on mine.
Can I use this if I'm running Prime 1.7 ?
ajamils said:
Can I use this if I'm running Prime 1.7 ?
Click to expand...
Click to collapse
No. This is only for people with rooted stock ROM version 8.6.5.6 who want to update to stock rooted 8.5.6.9
nolf3 said:
Ryan, did you install this while un-rooted ? since you mention you tried the unroot and update method - which is what i tried too
Click to expand...
Click to collapse
Rooted and with clock workmod
A couple of bugs I see, not sure if its because of my Xoom systemUI but when I mount a disk it says its mounted as read only but I can modify it and when I click on the SD card icon the pop up says "mobiledock firmware updating" instead of "sd card inserted."
Also, the auto and slider look wierd under the brightness options, white icons that dont match.
chuy08 said:
If someone can get me the WW package I can cobble something together. I won't be able to test however since I am on US.
Let me know.
Click to expand...
Click to collapse
http://dl.dropbox.com/u/39328504/dlpkgfile.zip
CrazyPeter said:
http://dl.dropbox.com/u/39328504/dlpkgfile.zip
Click to expand...
Click to collapse
Bump, give that a shot. Let me know.
chuy08 said:
Bump, give that a shot. Let me know.
Click to expand...
Click to collapse
No Go...
Failed on CRC Checking of ApplicationsProvidor.apk
(running HTJ85B.WW_epad-8.6.5.7-20110730)
CrazyPeter said:
No Go...
Failed on CRC Checking of ApplicationsProvidor.apk
(running HTJ85B.WW_epad-8.6.5.7-20110730)
Click to expand...
Click to collapse
I see what I did wrong try that. Sorry bout this I am new at this Android stuff.
chuy08 said:
I see what I did wrong try that. Sorry bout this I am new at this Android stuff.
Click to expand...
Click to collapse
Just did a BeyondCompare diff between the original dpkgzip and the modded one, so I can understand what you did. Most of it makes sense (the stuff in the script).
But why is the binary blob file half the size?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Bump...
Anyone know what the blob file is, what it does and why it's smaller? I don't want to screw up my working tablet, but I do want to try this out.....
CrazyPeter said:
Bump...
Anyone know what the blob file is, what it does and why it's smaller? I don't want to screw up my working tablet, but I do want to try this out.....
Click to expand...
Click to collapse
The blob is half the size cause its CWM.
I've searched everywhere and can't find anything on the sprint SPH-P500.
Does anyone know of any guides out there? I don't want to risk bricking it with a root from another model number. Thanks for all your hard work guys.much appreciated!
Do you have your stock rom? If you do, try rom for GT-5100 but you will not have 4G capability...
And if it don't work, you go in download mode and then restore your old stock rom thank to odin!
I guess everyone has forgotten about our tablet
I've never done anything on the coding side. But if someone could give me some guidance, I'd be willing to attempt to port some of the greatness that all of the other tablets are getting.
Its a great undertaking. I do website development and have linux experience and would rater not touch rom development. I have been interested though.
As far as the gt builds, i can give that a try. I dont have 4g in my area anyways,. Ill just have to become comfortable with odin before i do anything. Thanks!
Has there been any update on this? Looked around and doesn't look like there is even a developer working on it.
I can't even find the stock firmware for the SPH-P500.05 to download. I'm about to see if a sprint store will give me the file so I can start experimenting. If someone has a link to the stock firmware for this device it would be great. Maybe I'll get my hands dirty and make a few attempts and maybe get a guide going.
FluffyMittens said:
Has there been any update on this? Looked around and doesn't look like there is even a developer working on it.
I can't even find the stock firmware for the SPH-P500.05 to download. I'm about to see if a sprint store will give me the file so I can start experimenting. If someone has a link to the stock firmware for this device it would be great. Maybe I'll get my hands dirty and make a few attempts and maybe get a guide going.
Click to expand...
Click to collapse
Any luck? I'm dying to root this thing.
FluffyMittens said:
Has there been any update on this? Looked around and doesn't look like there is even a developer working on it.
I can't even find the stock firmware for the SPH-P500.05 to download. I'm about to see if a sprint store will give me the file so I can start experimenting. If someone has a link to the stock firmware for this device it would be great. Maybe I'll get my hands dirty and make a few attempts and maybe get a guide going.
Click to expand...
Click to collapse
I understand that CVE-2013-2094 has been ported to work (escalate to r00t) on Android devices. I don't know if this model has "performance events" turned on but, if so, could this be an opportunity to get # on our tablets?
Also, I have a way to kick off processes as system. Could that help us?
buford said:
I understand that CVE-2013-2094 has been ported to work (escalate to r00t) on Android devices. I don't know if this model has "performance events" turned on but, if so, could this be an opportunity to get # on our tablets?
Also, I have a way to kick off processes as system. Could that help us?
Click to expand...
Click to collapse
I need to subscribe to this thread. Sorry about the delay. I have been playing with the idea of flashing the GT-5100 firmware, but there is no way back to stock if things go bad. I think I'm going to be more proactive and talk with the local Sprint store to see if I can get that firmware / bin from them. The fact that the development community for this device is so dead is a bit eerie.
FluffyMittens said:
I need to subscribe to this thread. Sorry about the delay. I have been playing with the idea of flashing the GT-5100 firmware, but there is no way back to stock if things go bad. I think I'm going to be more proactive and talk with the local Sprint store to see if I can get that firmware / bin from them. The fact that the development community for this device is so dead is a bit eerie.
Click to expand...
Click to collapse
I sent you a couple PMs with more information. Not sure if they actually got to you.
Long search but - Cydia Impactor will take care of root for that Tab 2! Just follow that up adding busybox and all of the other root goodness!
Thanks Jay!!!
Instructions: Just Run it!
MrDavis
MrDavis said:
Long search but - Cydia Impactor will take care of root for that Tab 2! Just follow that up adding busybox and all of the other root goodness!
Thanks Jay!!!
Instructions: Just Run it!
MrDavis
Click to expand...
Click to collapse
Great. Any more information on this? Links?
More info
Sure! Google search 'cydia impactor' and pick the first link. That is just about as technical has I can make it
MrDavis said:
Sure! Google search 'cydia impactor' and pick the first link. That is just about as technical has I can make it
Click to expand...
Click to collapse
Haha, sorry about that. I will test it tonight. Maybe write up a script to automate this. Thank you so much for sharing this information.
FluffyMittens said:
Haha, sorry about that. I will test it tonight. Maybe write up a script to automate this. Thank you so much for sharing this information.
Click to expand...
Click to collapse
Use cydia installer to root then use http://forum.xda-developers.com/showthread.php?t=2101044&highlight=sprint to get cwm
sph-p500 Rooted!
MrDavis said:
Sure! Google search 'cydia impactor' and pick the first link. That is just about as technical has I can make it
Click to expand...
Click to collapse
I can also confirm cydia impactor works and is really as easy as downloading to pc run impactor hit startband it installsnsuper su right to the root of the tablet after that I have been able to successfully install (titanium, busybox, , link2sd, rom manager) and they all have root access
I have also been able to download mobile terminal and at $ prompt put in (su) and # should show letting you know you now have root access
after that I have also been able to change the default storage to ext2 by using. pm set-install-location 2, from # prompt and using link2sd to move apps 2 extsdcard for those of you that have an 8 gigger like I do I hope this helps im still alittle new to android
Any custom roms found for this tablet? I googled and I could only find rooting method but no custom roms (e.g. kitkat) for this tablet. Can the P5100 ones be used instead? I don't need the 4G service.
cydia impactor isnt recognizing the device. usb drivers fully installed and all that... kinda weird
nevermind. it worked!!! now i just need to install recovery and find a darn ROM LoL
I just received my Sprint SPH-500, and wouldn't have known it's a nonstandard Galaxy Tab 2 variant without this thread. I rooted mine with Towelroot, so I still have a locked bootloader, but full root access. AFAIK, my flash counter hasn't been triggered.
Here;s a screen capture of my downloading screen. It shows I haven't done a custom binary download (what triggers the flash counter), and I'm not running a custom binary, as I'm running the Samsung Official binary. But it does show my system status is custom..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I should have progress to report on moving apps to my external sdcard and second partition soon.
After experimenting with Link2SD for more than a week, I gave up on it. It's just too unstable to be a daily driver. I only have the 8 GB model, and run several large data astronomy and birding apps, They left me with 800 MB free RAM on my internal SD storage, and I still had other apps to install.
Link2SD put apks, Dalvik-cache, and lib files on the second partition of my external SDCard, but lost the links a reboot or two later. It claimed to move 1.8 GB of files, but showed 14 GB of RAM used on my second partition. It lost user and system apps that were linked, unlinked, and lost, for instance, the Google Play Store Services.
I ended up using a symlinking app called Foldermount, similar to the old (unsupported) Directory Bind app. It stores data folders on my external SDCard, and symlinks them so my astronomy and birding apps think they're still stored on the internal SDCard. I've got all my apps installed, and still have nearly 3 GB internal SDCard RAM free.
Post 1 - Information
Post 2 - Downloads and Release / Change Information
Post 3 - Bugs, Future Additions to the GUI, FAQ
I would like to add for those that like my toolkit, PLEASE DO NOT POST IT ELSEWHERE WITHOUT MY PERMISSION!
I have seen multiple sites who copy and paste my work to their site! If I do not approve of it, then do not do it! it will discourage me from adding updates since it is being used for their own benefits!
tl;dr.
If you post my work without permission, don't expect updates!
I created an easy to use GUI program for the HTC Amaze and I decided to make one for the Nexus 7 2013 Model. I spent a good over 10+ hours to learn how to script, watch videos on how to do it, working on it during school when I should have been listening lol and all that fun stuff. I am going to fix it and up and add more updates to it. You CAN place requests and I will try to fulfill it!
If this helped you out, Please press the thanks button and if you want, you can always donate!
FEATURES
- Install ADB Drivers
- Enter Bootloader (after it enters into bootloader, press the power button to enter Fastboot) REMOVED. No longer necessary.
- Unlock Bootloader (Must place Unlock_code.bin in the folder)
- Install Recoveries
User Provided Recoveries
TWRP WiFi
TWRP LTE
Kernels
User provided kernels
- Link to this thread
- Link to PM me if you need a phone unlocked
- Link to the Nexus 7 2013 Development thread
- Boot Into Recovery/Bootloader/Phone
- Flash kernel/recovery/RUU zip
- APK Batch Installer (Credits to hamsteyr)
- Donate to me (Hasoon2000) -> Donating to yours truly for putting time into this!
Here is a screenshot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How To Use. THIS IS FOR THE PC ONLY. No plans ever for Mac or Linux. Sorry.
1. Download the toolkit DO NOT RENAME THE FOLDER
2. Download Winrar from here. Install it after you download it
3. Extract the folder anywhere.
4. Run the program.
Credits
- The guys at the AutoIT help forum that helped me learn how to make the script!
- Devs for making us ROMS!
- The community for being awesome!
- To everyone else I may have forgotten!
*DISCLAIMER*
I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given.
DONATIONS
Downloads
Mod edit: Download links removed
Changes
V1.0 Released! 7-30-2013
- Initial Release
v1.0.1 Released! 7-31-2013
- Updated ADB/Fastboot so the toolkit should now work with the device.
- Added more info to the message box. If you don't flash a ROM, you MUST do a factory reset within the custom recovery, or else the device will be soft bricked!
Bugs
- Directory has to have one word.
Ex:
Will Work. This will solve any issues if the buttons don't work when you press them.
C:\Users\John\Dropbox\Phones\Amaze_All-In-One_Kit_V2.4
C:\Users\John_Smith\Dropbox\Phones\Amaze_All-In-One_Kit_V2.4
Will NOT work. Your directory will look something like this and buttons won't work when you press it.
C:\Users\John Smith\Dropbox\Phones\Amaze_All-In-One_Kit_V2.4
If you have 2 words, put the folder in Drive C:
Ex. This will solve any issues if the buttons don't work when you press them.
C:\Amaze_All-In-One_Kit_V2.4
Click to expand...
Click to collapse
Looking to add in the future
- Kernels
- More recoveries
- Makes Requests!!!
FAQs
Q - Why Did you make this?
A - To make life easier
Q - You are limited on features. Why?
A- You can always make a request!
Q - Will this work on other devices?
A - Only the fastboot commands, HTC Dev unlock (device specific) and the HTC drivers. Toolkit is made for the specific device.
Q - Will you support more devices in the future?
A - If people REALLY want, I can make it happen. I just don't want to make anything that nobody would use.
Q - Awesome! Can I make a donation?
A - Of course! Do not feel obligated though. If you would like to make a donation, you can click the button on my toolkit or under my username.
This is my first time supporting a non-HTC device. This should work perfectly fine, but let me know. I never owned a Nexus and I will do my best to make this compatible!
You are a gentleman and a scholar.
I'll give this a shot since the other Guide isn't working for me.
Edit: Yeah I cannot, no matter what I try, get my Nexus 7 drivers installed correctly. Odd.
Maroon Mushroom said:
You are a gentleman and a scholar.
Click to expand...
Click to collapse
Thank you sir
Chadneu said:
I'll give this a shot since the other Guide isn't working for me.
Edit: Yeah I cannot, no matter what I try, get my Nexus 7 drivers installed correctly. Odd.
Click to expand...
Click to collapse
Go to control panel -> Device Manager. Find your Nexus 7. Right click it and press uninstall drivers and delete the drivers with it (it will give you the option to delete them). Then, on top of device manager, press scan for hardware changes and it will find it and install the correct drivers.
hasoon2000 said:
Thank you sir
Go to control panel -> Device Manager. Find your Nexus 7. Right click it and press uninstall drivers and delete the drivers with it (it will give you the option to delete them). Then, on top of device manager, press scan for hardware changes and it will find it and install the correct drivers.
Click to expand...
Click to collapse
Nah, done that. I've uninstalled, restarted, installed the universal abd. It still doesn't see my Nexus 7 when I go to use your toolkit. At this point it installs fine, I have ABD interface in my device list, but it cannot be seen by the scripts.
No idea why. I'm gonna delete all the abd/toolkit stuff and start over.
What's really great about it is even when Windows fails to install any drivers and I point it to the correct ones it still fails and says it cant find the drivers, lol.
Something isn't right, especially since I've done this with about a dozen nexus devices on this computer.
Chadneu said:
Nah, done that. I've uninstalled, restarted, installed the universal abd. It still doesn't see my Nexus 7 when I go to use your toolkit. At this point it installs fine, I have ABD interface in my device list, but it cannot be seen by the scripts.
No idea why. I'm gonna delete all the abd/toolkit stuff and start over.
What's really great about it is even when Windows fails to install any drivers and I point it to the correct ones it still fails and says it cant find the drivers, lol.
Something isn't right, especially since I've done this with about a dozen nexus devices on this computer.
Click to expand...
Click to collapse
I bet you have done this, but did you turn on USB Debugging?
hasoon2000 said:
I bet you have done this, but did you turn on USB Debugging?
Click to expand...
Click to collapse
Haha yeah.
This has happened once before and I can't remember exactly what I did to get it fixed.
Dont worry, I know it isnt your toolkit.
Chadneu said:
Haha yeah.
This has happened once before and I can't remember exactly what I did to get it fixed.
Dont worry, I know it isnt your toolkit.
Click to expand...
Click to collapse
Trying to help you out. I never had a Nexus so at least I can learn it as well. Uninstall the drivers. Download the Google Drivers from here.
https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
Point the device from Device Manager to that. Hopefully it works. If it doesn't, just manually boot into bootloader and run the unlock bootloader command.
Chadneu said:
Haha yeah.
This has happened once before and I can't remember exactly what I did to get it fixed.
Dont worry, I know it isnt your toolkit.
Click to expand...
Click to collapse
You probably have done this also. Try rebooting PC after removing drivers and then reinstall drivers.
Sent from my Galaxy Nexus using xda premium
hasoon2000 said:
Trying to help you out. I never had a Nexus so at least I can learn it as well. Uninstall the drivers. Download the Google Drivers from here.
https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
Point the device from Device Manager to that. Hopefully it works. If it doesn't, just manually boot into bootloader and run the unlock bootloader command.
Click to expand...
Click to collapse
Yep, already tried using those.
Hmm, idk. Maybe I'll just say fug it and install windows 8, lol.
\/\/\/\No dice on that even, DroidIt!.
Took me awhile to figure it out but what worked for me was plug in nexus in booted up state, open device manager, hit update drivers (not uninstall), hit browse for drivers, navigate to where you have your adb/fastboot folder at and point it to there. Sorry at work and can't remember the folder it's in off the top of my head, but in adb/fastboot folder the one you want to pick is i386. That worked for me.
from my Viped out one x
While I find this tool to be overkill since the N7 is fairly easy to root, I can say from past experience that it was invaluable in getting my Droid DNA rooted; especially if you aren't too familiar with command prompt adb commands.
Alright! Got it all working. No idea what made it work. I basically kept installing/uninstalling with restarts in between, switched USB ports a few times, uninstalled some other stuff, restarted, and somehow it worked. Idk, I'll chalk it up to windows 7 driver management being absolute ****.
I wound up having to use the other tool to install TWRP. Apparently your ADB server is out of date? I replaced your /data/adb.exe with a newer one, worked fine after that.
Got my bootloader unlocked, recovery flashed, and it's rooted.
Thanks!
I did all the steps to root but I can't get pass the boot screen, can someone help?
Sent from my Nexus 4 using Tapatalk HD
sabinblitz said:
While I find this tool to be overkill since the N7 is fairly easy to root, I can say from past experience that it was invaluable in getting my Droid DNA rooted; especially if you aren't too familiar with command prompt adb commands.
Click to expand...
Click to collapse
It's always nice to have options and remember, this is all-in-one for a reason. Extra commands, features, everything.
Chadneu said:
Alright! Got it all working. No idea what made it work. I basically kept installing/uninstalling with restarts in between, switched USB ports a few times, uninstalled some other stuff, restarted, and somehow it worked. Idk, I'll chalk it up to windows 7 driver management being absolute ****.
I wound up having to use the other tool to install TWRP. Apparently your ADB server is out of date? I replaced your /data/adb.exe with a newer one, worked fine after that.
Got my bootloader unlocked, recovery flashed, and it's rooted.
Thanks!
Click to expand...
Click to collapse
Can you upload those ADB files so I can put it in my toolkit?
bmakk2055 said:
I did all the steps to root but I can't get pass the boot screen, can someone help?
Sent from my Nexus 4 using Tapatalk HD
Click to expand...
Click to collapse
I don't have the device so I can't actually say. Hopefully somebody else can help.
bmakk2055 said:
I did all the steps to root but I can't get pass the boot screen, can someone help?
Sent from my Nexus 4 using Tapatalk HD
Click to expand...
Click to collapse
If you didn't flash a custom ROM yet, go back into recovery and do a factory reset. Should boot up then.
Getting my N7 tomorrow. Will this work on Win8 64? Thanks in advance.
Sent from my SCH-I605 using xda app-developers app