Related
Well, I'm not much of a guide person, but there's a great tool that's been out for a long time that has proven to be quite useful to me. THIS IS NOT A REPLACEMENT FOR FREEZA'S GUIDE. That's an excellent guide, and he deserves full credit for it. This guide is for those of you who want to trim/debloat after you flash. It also serves many other handy uses, which I shall explain in a few.
Also keep in mind, this will work on damn near ANY rooted Android phone. In fact, I used to use it QUITE a lot on my old Sprint Hero. This is essentially ADB without the need to know how to use the command line.
~~ This guide is a constant WIP ~~
What is Android Commander?
It's an all-in-one tool that was designed using adb. It provides the following:
[*]Complete root-based file manager
[*]Applications Manager
[*]Rebooting/Powerdown Abilities
[*]Storage Monitor
[*]All around awesome tool
It's completely free to use and is written by a talented XDA developer.
Requirements:
Windows XP or higher: As if I'm going to give you link to this
My little ADB Package: http://dl.dropbox.com/u/345001/Images/AC Guide/ADB.rar (For anyone wondering why I'm giving this seperate, it's to save you the trouble of having to download the entire android sdk and going through the convoluted method of using the SDK manager to grab adb)
Android Commander written by our very own XDA user PanPiotr: http://androidcommander.com/
1. Download my ADB package, and extract is somewhere. Inside is a folder called ADB, with two dlls and the adb executable. Remember where you put it.
2. Download and install Android Commander.
3. Right click and run Android Commander as administrator. It will ask you to set the ADB path near the bottom. Select the ADB folder that contains the 3 files above, which you downloaded already.
4. If it doesn't automatically start the app after selecting the folder, simply press exit, and run it again as administrator. This time, the app will start up
And this is what you see!
{
"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"
}
Now for starters, you'll notice a plethora of information. Try not to get overwhelemd. Android Commander is a ridiculously comprehensive utility. And the best part is that it's based entirely on ADB. Now, by default, you'll see your Windows files on the left pane, and the Android files on the right.
Let's begin with the debloating. Start by finding the "System" folder first.
From here, head on over to the "app" folder.
So this should be pretty self explanatory. Start selecting checkboxes for apps and bloatware that you don't want/need. Then, just click the "delete" button. It will delete them all in one shot.
I know this seems a bit anticlimactic, but that's more or less it for the debloating guide, because that's only one of the many uses AC has. Read on to the next few posts for a few scenarios/possibilities that you may encounter while using custom ROMs.
Basic Scenarios/Uses
This post covers basic scenarios and uses for Android Commander.
[If you've been directly linked to this post, please see the post above for information on installing and getting Android Commander up and running]
Remember, AC can start functioning as quickly as just moments after you see the white HTC screen. It doesn't have to be fully on for you to use AC and all its features. Android Commander can also be used from recovery as well.
Help! I used SetCPU, checked "Set On Boot", overclocked too high, and now my device is in a boot loop
Not a problem! I've done this too many damn times to count. The solution comes down to two options; one, be super fast when booting up and try and clock down SetCPU when you get in (very frustrating), or use AC! Remember, Android Commander can be used either in recovery or even during boot! So what we're going to do is start it up, and uninstall SetCPU. Let's open up Android Commander, and select "Applications Manager". It will ask you if you would like to update the list of applications, click yes.
From this point on, you can now see all of your applications. Simply click on one of the applications, and either uninstall it using the buttons above, choosing to delete its data or not.
By the time your device finishes rebooting, or when you boot out of recovery, you'll find SetCPU gone and your device no longer locking up and bootlooping! Easy, huh?
Did you know you can reboot the device from Android Commander?
Yes, you can . Simply click on the "Phone" menu up top:
Pick what you want to boot in. Also, yes, you see "screenshot" in there, but it currently doesn't work for the EVO 3D. It should for older devices though.
Did you know you can flash a recovery image through AC?
Indeed, you can.
More to come!
Advanced Uses - For Devs/Themers
This section is intended for both budding and veteran ROM cooks, modders, and themers.
Did you know that you can set file permissions with Android Commander? You can do what root explorer does, just fine. If you choose to use the 7.9.9.9 beta and up, you can easily set file permissions of any file, as shown below
MORE TO COME
First part of the guide is up
Thanks for this, I look forwards to seeing what more comes to this guide. Well done man.
empiire said:
Thanks for this, I look forwards to seeing what more comes to this guide. Well done man.
Click to expand...
Click to collapse
Glad you find it useful. It's got a ton of potential for devs such as yourself, I'd highly recommend you experiment with it, there's stuff I still don't even know about yet.
It even has it's own pre-"su"'d command line built into it.
Updated the "basic use" post to include more awesome little details
This is a nice tool! im definitively gonna be using this! thanks!!
steal25 said:
This is a nice tool! im definitively gonna be using this! thanks!!
Click to expand...
Click to collapse
Let me know what other cool features you end up finding, I'm sure you'll run into plenty of stuff I haven't found yet.
This will be loaded before the sun sets. Thanks for sharing - great utility.
Sent from here using this. Black. Slab.
Thats a pretty slick app.
I did everything stated in the first post, and for some reason it doesn't say I am rooted. so I don't have the application manager. to be clear I don't need the SDK installed, just your file? I extracted it into a new directory and then set that as the path when I started up AC, it starts up, finds my phone, can explore it, reboot it, but it still says I am not rooted in the lower left corner of AC. I am not a noob when it comes to doing stuff with android, but am noobish with adb, never used it before, so i thought this would be a great tool for me to learn...if I can get it to work.
jbermi said:
I did everything stated in the first post, and for some reason it doesn't say I am rooted. so I don't have the application manager. to be clear I don't need the SDK installed, just your file? I extracted it into a new directory and then set that as the path when I started up AC, it starts up, finds my phone, can explore it, reboot it, but it still says I am not rooted in the lower left corner of AC. I am not a noob when it comes to doing stuff with android, but am noobish with adb, never used it before, so i thought this would be a great tool for me to learn...if I can get it to work.
Click to expand...
Click to collapse
Hmm. Did you run AC as admin?
LiquidSolstice said:
Hmm. Did you run AC as admin?
Click to expand...
Click to collapse
yep, followed everything in the first post...and yes, the phone is rooted. LOL. I am going to uninstall AC and try again, and see if that works...
problem - phones rooted - viper rom 1.2.1 stock kernal - downloaded the two files you have, installed your AC, and unzipped the ADB - start up, point it to that folder, then it has the little window that says DEVICE: NOT FOUND. have debug on, charge, i am the admin on the pc.
-----sorry------ now it runs only after i posted.... sometimes thats all it takes - now to test it out, looks very useful, and easy.... thank you
Thanks, Liquid. Way faster then using Root Explorer or manual adb. Wish I'd known about this ages ago.
Very usefull...but We realy need a UI manager to change icons ect....
Thanks Liquid - I used your LiquidSense ROMs over on the Hero side, and now that I've got my E3D, it's great to see you devving over here. I used Android Commander a lot on the Hero, so good to see it will still work for the E3D! Thanks for the Guide!
-mb
when i use the sign .zip file tool, i put a file on my desktop, then run the tool and cannot figure out where is put the new signed file at? Any help?
i changed the output folder to desktop, and nothing, it doesn't sign the file and ouput it....hmm...
Great guide! I use Android Commander for just about everything. Nice point on using it to get out of a boot loop. I discovered that when I had my Hero, and it saved me many times.
Sent from my s-off Shooter!
The aim of this guide is to enable you to install a custom firmware on your Optimus G while being as clear, accurate and succinct as possible. This guide is intended for use by Windows users with an AT&T Optimus G (AKA LGE970).
I've presented the following sections in a specific order for a reason: you need to root to unlock, and you need to unlock to install a custom firmware. If you're currently running what the manufacturer gave you, you need to start with rooting, then unlocking, then trying other firmwares. Be careful, good luck, and have fun!
How to "root" your Optimus G
(Optional if you have another means of un-RARing) Download and install 7-zip from here. You need this to open certain types of archives (specifically .rar, but you might also want to open .tar, .bz2, or other types of archives in the future). This program is supremely awesome in its ability to open almost any archive you throw at it. It's also unobtrusive and efficient.
Download and install LG USB Drivers from here. Without these drivers, your computer won't be able to effectively communicate with your phone. This is vital for the steps we will be taking.
Enable USB debugging by going to Settings->(General)->Developer options" and checking the box next to "USB debugging." You will get warnings. You can probably ignore them. This setting will allow you to run commands on your phone from your computer (via USB). For more info on the Android Debug Bridge, click here.
Download and extract (using 7-zip (or whatever)) the root exploit from here.
Connect your phone to the computer with your USB cable.
Put the phone into "Charge Only" mode at Settings->General->PC connection->USB connection type
Open CurrentRoot.bat and follow its prompts. You will need to change from "Charge Only" to "Media sync (MTP)" mode. The setting is in the same place.
Run SuperSU (now in your apps drawer) it and make sure it works. This program allows others to gain access to superuser privileges. For more info on rooting and what kind of stuff it lets you do, click here and/or use Google.
If that didn't work for you, try following instructions from the thread where this root method came from.
How to unlock the bootloader
The bootloader is the first program your phone runs and its main job is to load the operating system. The stock bootloader is locked and will only run versions of Android that LG and AT&T want it to. Since our goal is to install and run custom firmwares, we must circumvent this locked bootloader. Luckily, thecubed and Shellnut2 have found a way to do this for us. What you want to do is buy Shelnutt's app. There are several reasons you should throw down some cash on this:
It's way easy to use
It'll make backups of your stock recovery/bootloader for you, it'll also make restoring these backups easy
The money is for a good cause
If you're still confused, visit thecubed's thread. He is the man, thank him a billion times. Then thank him again for being a nice guy.
For the convenience of those interested, here is the more laborious/error prone/manual way to unlock (NOTE: this method does NOT work if you've updated to Jelly Bean, you need to use the app):
If you haven't already, download and install 7-Zip and the LG USB drivers, and make sure you have USB Debugging turned on (see above).
Download the latest version of the bootloader unlock here (latest version has the highest version number).
Ensure that your screen is on and unlocked (I'd go to "Settings->Display->Screen timeout" and set the timeout to never to make sure the screen doesn't go off during this process). Your screen must remain on because SuperSU will ask you to grant superuser privileges to the unlock script and you want to be able to tap "Yes" when the time comes.
Connect your phone to the computer with your USB cable, and run the freegee.bat script in extracted files on your computer. Do NOT run this script as administrator. The install will fail if you do. Follow the prompts. You can ignore "No space left on the device" errors, but "adb.exe not found" or "tar: invalid magic" errors are not negligible and indicate either you skipping a step, a funky download, or something very bad.
Once the script finishes, make sure you have a populated "backups" folder in the folder where freegee.bat lives. The backups folder contains your original stock/locked bootloader, which you might want if you ever want to revert to stock.
If you're sure the script ran successfully, power off the phone. Next, hold down the power and volume up keys simultaneously to enter fastboot mode. You should see a screen that looks like this:
{
"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"
}
In fastboot mode, there is a menu, but it's hidden. To navigate it, remember that volume up moves the cursor up, volume down moves it down, and power selects the currently highlighted option. The options are, in order:
Start - boot the phone normally [highlighted by default]
Restart Bootloader - reboot into bootloader
Recovery Mode - enter ClockworkMod recovery (more on this later)
Power Off - (duh)
Here is a video of thecubed showing you how to get to ClockworkMod from the bootloader (like a boss):
Using Team Win Recovery Project
Team Win Recovery Project (AKA TWRP) is a recovery, which basically allows you to install new firmwares and apply updates/modifications to already-installed firmwares (and a bunch of other things, like mounting and formatting portions of your phone's memory). It is the default recovery option when you use the Freegee app to unlock your phone (the other is Clockworkmod, which is so similar I won't be writing a separate guide on how to use it). Navigating TWRP is fairly self explanatory. Many great guides on how to use TWRP have been written and can be found via Google. Here is the first search result that came up for me. It's a pretty good guide.
One thing I will vehemently recommend is that you make a backup every time you install a new firmware. Personally, I backup apps and texts with Titanium Backup and my current firmware via TWRP (the linked guide explains how to make a backup in TWRP). Backups are a good idea and people should always make them. ALWAYS.
Installing custom firmwares
Follow the firmware author's instructions EXACTLY. These guys know what they are doing, certainly more than you or I. Check out the development threads for ROMs to try out.
Note: Be sure that if you are installing ROMs that require the Jelly Bean OTA update that you have taken that update.
There are two ways to do this: receive the update as intended (Over The Air) or use LGNPST (guide on using that under FAQ 3.a of this post) or autoprime's awesome tool, TeenyBin.
FAQs
How do I upgrade FreeGee? The easiest thing to do is simply install the new version of FreeGee the way you did the old one. It will work. Make sure you keep your original locked bootloader in a different, safe place though, just in case you ever want to revert to stock (if you try to return your phone, for example).
How do I disable that pesky OTA update notification? This comes courtesy of shawnchalfant and adfurgerson (visit ad's thread for more details): go into Titanium Backup and freeze the following programs: com.lge.lgfota.permission 4.0.4-91f513f88d AND com.lge.omadmclient 3.2.21
How can I re-lock and un-root my phone?
How to LGNPST to restore a factory image.
Obtain the following files: AutoLGNPST-tSilenzio.zip (available on IRC), and the firmware. Unzip AutoLGNPST-tSilenzio.zip and follow the instructions in "READ ME FIRST.txt" (mad props to tSilenzio for automating this process).
Here's the laborious/error prone/manual method for LGNPST-ing back to stock.
You need to obtain the following files: LGNPST-PhantomPhreak53.zip, LGNPST_ACG_2.2.3_Lab.zip, and the firmware. Follow the following steps (please note: I am less experienced with this process and find it much more tedious. Also, IMHO, I don't think the people you're returning the phone to will care if you leave some minor traces of your unlocking shenanigans. I think the process above this is more than sufficient and simpler). Credits go to Jhoopes517 for this process, he showed me how to do it in his thread.
(Install LG USB drivers)
Extract LGNPST_ACG_2.2.3_Lab.zip, run the installer. Open file explorer to C:\Program Files\LG Electronics\LGNPST and replace the current LGNPST_ACG.exe with the one in the extracted folder (if you are on a 64-bit version of windows, go to C:\Program Files (x86)\LG Electronics\LGNPST)
Extract LGNPST-PhantomPhreak53.zip and run LGNPST_GenericModels_Ver_5_0_12_0.exe and then run LGNPST_Components_Ver_5_0_20_0.exe
In file exlorer, navigate to C:\LG Electronics\LGNPST and copy over the "Models" folder from the extracted Phantom zip folder
Run cmd as administrator and execute the following
Code:
regsvr32 "C:\LG Electronics\LGNPST\Models\LGNPST_LS970.dll"
Extract LGE970AT-01-V20j-310-410-MAR-08-2013.zip and change the extension of the .tot file to .bin
Connect phone to computer, power off, and then power on, holding down the power button and both volume buttons
Run the newly replaced LGNPST_ACG.exe from step 2. Select the DLL from step 5 and the .bin from step 6.
Press Start
If LGNPST errors out at 85%, turn your phone off and hold the power button until the phone powers on, then release. DO NOT disconnect the cable before LGNPST is done doing its thing. Your phone may reboot. This is OK.
(If you are using Shelnutt's app, simply use the button in the app to re-lock and install the stock stuff).
Here's the laborious/error prone/manual method for re-locking the phone and installing the stock recovery/bootloader/kernel.
Remember the backups of the locked bootloader that you kept? You're going to need them. Obviously, you'll need USB Debugging enabled and LG USB drivers installed. Copy them to your phone's "Internal Storage" in a folder, in this example it's called "backups." Connect the phone to your computer via USB, open a command line (cmd) and type the following:
Code:
cd C:/some/folder/where/you/have/adb.exe/eg/your/freegee/download
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/boot
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/aboot
dd if=/sdcard/backups/aboot-att-backup.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
dd if=/sdcard/recovery-att-backup of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/boot-att-backup.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
dd basically copies from the if= location and writes to the of= location. The first three dd steps write a bunch of zeros to the recovery, boot, and aboot partitons, the last three write the backups to aboot, recovery, and boot. If you want to know more, read all about dd here and/or Google. If you lost your backups, you can try writing mine.
Now you've restored the stock bootloader and recovery, but your phone is still rooted. To unroot it, open SuperSU, go to its settings, and tap "Full unroot." Do a factory reset (Settings->General->Backup & reset->Factory data reset) and you should be good to return the phone to AT&T (or whatever).
Be careful with these last two methods if you have removed any bloatware or installed a custom firmware, you may prefer to LGNPST back to stock (LGNPST is almost always a safe way to return to stock).
blenkows said:
Haha I wish I had seen this earlier. I had screenshots before and after so I could see exactly what was removed but I had just deleted them. From memory, it doesn't seem like too much was removed. All the AT&T apps are gone but it appears LG's apps are still here.
Click to expand...
Click to collapse
Here is a list of apps I had shortly after factory reset on stock for people to compare with theirs. I have struck out the ones I was able to remove without my phone blowing up. Let me know if you safely removed one and I'll strike it out. Also let me know if I missed any or included an app which isn't part of stock. Thanks!
AAT
Adobe Flash Player 11.1
Adobe Reader
Amazon Kindle
Android keyboard
Android live wallpapers
Android system
Aspect ratio correction
AT&T address book
AT&T code scanner
AT&T family map
AT&T hot spots
AT&T locker
AT&T messages
AT&T navigator
AT&T ready2go
AT&T smart wi-fi
Bluetooth share
Browser
Bt/wifi test
Bubbles
Calculator
Calendar
Calendar storage
Calendar widget
Camera
Car home
Certificate installer
City ID
Clock
com.android.backupconfirm
com.android.providers.partnerbookmarks
com.android.providers.settings
com.android.sharedstoragebackup
com.lge.lgdrm.permission
com.lge.lgfota.permission
com.lge.lockscreen
com.lge.omadmclient
Contacts
Contacts storage
DeviceHelp
Download manager
Downloads
DRM protected content storage
DRM service
Email
Email widget
EmailServices
Face unlock
Facebook
Favorite contacts widget
File manager
File networking
FileShare
Finance
Gallery
GestureOverlayService
Gmail
Google account manager
Google backup transport
Google calendar sync
Google contacts sync
Google partner setup
Google play books
Google play magazines
Google play movies & tv
Google play music
Google play services
Google play store
Google search
Google services framework
Google text-to-speech engine
Google+
Home
Home selector
Home theme - Biz
Home theme - cozywall
Home theme - marshmallow
HTML viewer
Key chain
Lg keyboard
Lg tag+
Lg voicecommand speechpack
Lgapduservice
Lgatcmd service
Lgsmartcard service
Lgsystemserver
Live tv
Live wallpaper picker
Local search
Lock screen settings
Maps
Marionette
Market feedback agent
Media home
Media storage
Messaging
Multi-photo live wallpaper
Music
Music
Musicfx
My uploads
MyAT&T
Network location
News
NFC service
Nfsservicemanager
Note pad
Note pad widget
On-screen phone
Package access helper
Package installer
Phone
Phone/messaging storage
Photo frame
Playready cert test
Polaris office 4.0
Power control widget
Quickmemo
Search applications provider
Settings
Setup wizard
Shutdown monitor
Sim toolkit
Smartshare
Social+
Streaming player
System ui
Talk
Task manager
Today+ widget
Tom's diner
Twitter
User dictionary
Usermode
Vidclip
Video wiz
Videos
Voice command
Voice search
Voicemail
VPN client
Vpndialogs
Wap service
Weather
Widevine keybox test
Wiper app
Wise screen
World clock widget
YouTube
Yp mobile
I can't root. What do I do?
Double check that you have followed all the steps in this guide (USB drivers, correct settings, etc.) If your software version ends in "c," you need to LGNPST to the version that ends in "o" (see the section on LGNPST in this post).
Why shouldn't I run the Nexus 4 conversion?
See this post by thecubed. Don't be impatient, a legit, safe ROM is forthcoming here. Messing with partition tables is needlessly risky.
My shiny new firmware has no APNs and I don't get mobile data! What do I do?
Use the APN settings in this post. They have always worked for me. If they don't try setting the "APN" variable to "pta" instead of "Phone."
... (ask me more questions!)
I hope you found this useful. Obviously this is a work in progress. I am way open to suggestion, please leave a comment below! If you liked this post, hit the thanks button and/or rate this thread so that others know this guide is legit. Thanks!
Very nice, man. This is great for people who don't want to have to hop between threads for all the different information.
I recommend we sticky it.
this is definitely appreciated. i was looking for a guide when i first rooted and unlocked, just to read along with making sure i was doing it right. more just to double check my process than actually needing it.
This is the best root/ROM guide I've ever seen. Excellent job.
Sent from my LG Optimus G
anyone try this on E97110d
should it work?
cpus456 said:
anyone try this on E97110d
should it work?
Click to expand...
Click to collapse
I haven't so I can't recommend trying it.
Awesome work! someone please sticky
all worked great!
can you please also post a guide on how to lock back the device and unroot.
and also how to update to a new version of freegee if it comes out.
Please
?
Thank you.
karelson said:
can you please also post a guide on how to lock back the device and unroot.
and also how to update to a new version of freegee if it comes out.
Please
?
Thank you.
Click to expand...
Click to collapse
Both of those requests are covered in the OP. Specifically, look at FAQ #2...If you can't understand that, I can't help you.
Carrett can u do a guide for going back to stock? Flashing a stock Rom....got the files I need just have no clue what to do. .need to return my phone.thanx
Sent from my LG-E970 using xda premium
martyotaku said:
Carrett can u do a guide for going back to stock? Flashing a stock Rom....got the files I need just have no clue what to do. .need to return my phone.thanx
Sent from my LG-E970 using xda premium
Click to expand...
Click to collapse
What files do you have exactly? The easiest way to do it, in my opinion, is to follow the steps in FAQ #2.
i have the stock rom(i deleted some bloat) and i went on thecubed's irc and got some dlls and and a lg program but no clue what to do
Is there a way to restore? I totally messed up. My phone won't turn on at all. Help would be appreciated thanks.
i need a step by step for LGNPST back to stock if possible please
martyotaku said:
i need a step by step for LGNPST back to stock if possible please
Click to expand...
Click to collapse
I have never LGNPST-d my way back to stock, nor do I plan on doing it. If you are already unlocked, my advice to you is to obtain APKs of any bloat you removed, reinstall them, and follow my method for relocking and unrooting. That being said, you may be able to find someone willing to walk you through LGNPST-ing in IRC. I will try to figure out how to do it and if I feel confident I'll write a how-to. If someone wants to supply me with a howto, I'd be happy to include it in the OP and credit them (assuming their how-to makes sense and I can easily follow it).
Honestly though, it seems like a pointless exercise when you have CWM and su.
Sorry I can't be more accommodating.
carrett said:
I have never LGNPST-d my way back to stock, nor do I plan on doing it. If you are already unlocked, my advice to you is to obtain APKs of any bloat you removed, reinstall them, and follow my method for relocking and unrooting. That being said, you may be able to find someone willing to walk you through LGNPST-ing in IRC. I will try to figure out how to do it and if I feel confident I'll write a how-to. If someone wants to supply me with a howto, I'd be happy to include it in the OP and credit them (assuming their how-to makes sense and I can easily follow it).
Honestly though, it seems like a pointless exercise when you have CWM and su.
Sorry I can't be more accommodating.
Click to expand...
Click to collapse
I kinda need LGNPST. Somewhere during rooting, my phone just wouldn't turn back on. It did that screen flicker thing and the buttons flicker, but it stayed there for about 10+ minutes. So i figured, i wanted to start fresh with factory settings again. When i try to run LGNPST, it goes to 67% then the phone leaves download mode and then LGNPST says it's been disconnected and that i should restart my phone and then it can continue. Problem is that the phone can't even boot up at all.
I even tried the unbrick guide from the other optimus g forum but i can't get ahold of the .KDZ file. I'm not even sure if that process can work on an AT&T optimus g. Spoke to people on IRC and said that it sounds like a hardware issue. If i can't get this thing to boot, i'm going back to BestBuy to exchange for another one.
aznracer62 said:
I kinda need LGNPST. Somewhere during rooting, my phone just wouldn't turn back on. It did that screen flicker thing and the buttons flicker, but it stayed there for about 10+ minutes. So i figured, i wanted to start fresh with factory settings again. When i try to run LGNPST, it goes to 67% then the phone leaves download mode and then LGNPST says it's been disconnected and that i should restart my phone and then it can continue. Problem is that the phone can't even boot up at all.
I even tried the unbrick guide from the other optimus g forum but i can't get ahold of the .KDZ file. I'm not even sure if that process can work on an AT&T optimus g. Spoke to people on IRC and said that it sounds like a hardware issue. If i can't get this thing to boot, i'm going back to BestBuy to exchange for another one.
Click to expand...
Click to collapse
The folks in IRC know much more about lgnpst than I do. There's no secret that's being withheld, and unfortunately my best guess is that the lgnpst experts in IRC are right and it is a hardware issue. The good news is that you don't have to tell Best Buy the events leading up to your phone's demise and they probably won't be able to tell what they were either (we're talking about Best Buy employees here; most don't give two craps about their job).
Found a how to for a different lg phone here. Not certain that it will work for ours but it's worth a try. If it works for you, let me know and I'll add it the OP for others.
carrett said:
Found a how to for a different lg phone here. Not certain that it will work for ours but it's worth a try. If it works for you, let me know and I'll add it the OP for others.
Click to expand...
Click to collapse
I've tried something similar to that. Basically that's just an older version of LGNPST but when you use it, it says verizon wireless on it, well the one i downloaded at least. And you're right, took it to best buy and they didn't ask about it. I have up to January 24 to exchange it again in case it happens again. If the guys on IRC say it's hardware after explaining exactly what i did, it's the hardware. Gotta admit, i'm new to LG. I came from a line of Samsungs. Usually if anything goes wrong id just reflash with Odin or Heimedall and everything's back to normal again. LGNPST does the same function? From what i've read it serves the same purpose.
Anyway, take 2 on this guide. Deleting everything LG from my computer and starting fresh. One thing that i did notice when rooting, cmd gave me an error saying i'm missing backup_restore.apk (or something of similar name).
NABI LAB v2
{
"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"
}
NOTE: The program is becoming long in the tooth and not as useful with Jellybean on Nabi. For Jellybean TWRP installs check this repackaged version of Nabilab http://forum.xda-developers.com/showpost.php?p=48987089&postcount=2088
This is a tool for performing various automated tasks on the Nabi 2. It's written as a windows command line batch file, and v1 has been tested by a few members of the forum with positive results. Hopefully this means all the bugs are worked out, most issues have been typos on my part. It's an attempt to include all recent developments in Nabi 2 rooting, Gapps install, recovery methods, and modding and provide and all in one experience. Alot of this is my own original work, and other parts are creations of others intact or modded for Nabi use. Using the latest known working methods, it hopefully prevents users from having to install, break things, uninstall, recover, try new method, ask forum questions, try another method, and all the while for those with kids having them ask why you broke their toy.
Currently you cannot install Gapps on 2.1.27 see here http://forum.xda-developers.com/showpost.php?p=45866724&postcount=1647
A test version of NabiLabGUI is here: http://forum.xda-developers.com/showthread.php?t=2391449
Overview
Video Overview of Nabi Lab v1 mostly the same as v2
-Install ADB/Fastboot digitally self-signed drivers.
-Root the Nabi 2
-Install Gapps(Play Store, etc)
-Fix Android is upgrading message
-Make a stock backup of unrooted device
-Install a stock 1.9.37 in the event of loss of backup.
-Install stock, or TWRP recoveries
-Tablet Information
-Lockscreen modding tool
-NabiLab patching system to install updates to this program
-Fix TWRP touchscreen issues
-While not a built in function using the tools to fix broken Wifi
Download
Read the installation section below to determine which version you want.
File names:
NabiLabFull.zip 1.1GB
Download
NabiLabLite.zip 97MB
Download
Download Mirror
NabiLabv2Update.zip 10.1MB(upgrade patch for v1 users)
Download
Download Mirror
Installation
There are 2 versions of Nabi Lab: Full and Lite. The full edition is 1.1GB and includes a stock 1.9.37 backup of the system, data, and boot partition. It's usefulness is really only of interest to those that need to restore to a stock backup. It should be a rather limited group of people as you should have a backup of your system already that you could use in lieu of this. However in the event you have lost your backup, or have mangled the system to the point you aren't sure what to do, the option to restore to stock 1.9.37 is in the full edition. The likely download of choice is the Lite edition at a more manageable download size of 97MB. It has all the tools of NabiLab just without the ability to restore a stock backup(which of course you have one of your own). The upgrade patch zip is for v1 users.
NEW INSTALLS
1) Download Nabi Lab
NabiLabFull.zip 1.1GB
NabiLabLite.zip 97MB
2) Extract the zip files to a location of your choosing. Run the NabiLab.bat file.
PATCH INSTALLS(For version 1 users)
1) Download NabiLabv2Update.zip 10.1MB
2) Extract the zip IN to the directory NabiLab is in not FROM the directory. What ever your unzip program it should be extracting to X:\somefolder\somefolder\yourNabiFolder\ If you do it right there will be a file RunOncePatch.bat in the same folder as NabiLab.bat, and a NabiPatch.zip in a new folder called patch in your NabiLab folder.
3) Run RunOncePatch.bat
note: This is only necessary this time, any future patches will be applied by downloading a NabiPatch.zip, and installing inside the NabiLab program.
Prerequisites
1) ADB enabled in Android. Enter Mommy/Daddy mode. Open settings->developer options->put a check mark in USB debugging.
2) Unsure you are on version 1.9.37. Enter Mommy/Daddy mode. Open settings->About Tablet->Product Version. If it's at something less then 1.9.37 go up to the "Update" selector and check update and install. You may have to do this more then once.
Notes: At this point it is believed that the Madagascar Nabi 2, and UK version have product versions of 1.9.34, and 1.9.35/6 respectively. You can attempt to use NabiLab at those versions but I cannot guarantee results. Most things should work however.
Usage
Obviously using this product on your Nabi 2 voids the warranty and I take no responsibility for the damage you cause.
MENU 1 - Installing drivers
The provided drivers are for Windows XP,Vista, 7 and 8 32bit and 64bit. They are modded version of the drivers by 1wayjonny found in this thread. The mod to those drivers are adding the Nabi, and the HP Touchpad Tenderloin(only because I have one). The are digitally self signed by "NabiLab".
Menu Option 1 - Auto Install
Check in the top left corner under Detected OS to see if it matches your configuration. The most important part is if it says "x86"(32bit) or "AMD64"(64bit) this is what the auto installer is going to install. If you don't know right click "my computer" and look under system type. If everything looks right proceed. An installer will launch and guide you through install.
Menu Option 2 - Manual Install
If you want to manually install, an explorer window will launch allowing you to pick the NabiDriver32.exe or NabiDriver64.exe. In case it needs stating the NabiDriver32 is for 32bit OS, and NabiDriver64 is for 64bit.
Notes: The driver can be uninstalled by going into control panel and add/remove programs, select Nabi Driver and click uninstall. The digital certificate for Nabi lab is installed in Trusted Root Certification Authorities. Probably the easiest way to view is internet explorer. Go to tools->internet options->content->certificates. It can be removed from here should you feel it's a security risk. I don't think it installs properly on XP, so if you want to add it go to your program files folder->NabiLab->driver and find the NabiLab.cer, right click and select install. When you come to option of where to install manually select Trusted Root Certification Authorities.
MENU 2 - Root, Gapps, Recovery
Menu Option 1 - Install Root, Recovery and Gapps
This option is best used if you have a brand new Nabi. At this point you should have met the prerequisites of enabling ADB in Android and upgrading to 1.9.37. Follow directions, most sticking points are pressing the volume + and then pressing the volume - button twice and making sure recovery kernel is the one highlighted. After its complete you should have a rooted Nabi, with Gapps and a backup of your unmodified Nabi in the folder TWRP/BACKUPS/YOURSERIAL/stockunrooted on your device. Not a bad idea to copy this off the Nabi to your computer if you need to free space or have it in a second location.
Menu Option 2 - Install Root and Recovery
Same as above but doesn't install Gapps. Some people have trouble with option 1 taking the Gapps install, I personally have never experienced it but the option is this one, or I guess if you are an elite hacker that just wants root.
Menu Option 3 - Install Gapps
Same Gapps installed in the Option 1. Useful for re-installing Gapps, and/or getting rid of the Android is Upgrading message. It is the immensely popular t499user Gapps with the 2 stray .odex removed. No sense in reinventing the wheel. This makes NO backup of you Nabi. You will have to already have installed TWRP.
Menu Option 4 - Install Root
Installs root. Nothing fancy here, and likely unneeded but here for completeness if you find yourself in a strange situation. One that comes to mind is that you have a stock backup which you restored and don't want to do another backup so you would just run this and the gapps install. It makes NO backup. You will have to already have installed TWRP.
Note: The layout of this is based on the original work by jmztaylor, modified for what we currently know about the Nabi and tweaked accordingly.
MENU 3 - Return Nabi to Stock Condition
The menu options will only be available if you have downloaded Nabi Lab full. If you have a stock unrooted backup you should try that first.
Menu Option 1 - Return Nabi to Stock 1.9.37. Android can boot.
This is useful if you just want to return your Nabi to stock for regular use, sale, or warranty(morals aside). This is the mode to use if you can boot Android. This operation will take some time to run, so let it. Upon completion TWRP is still installed, to entirely restore to stock you will need to install the stock recovery(see Menu 4). You have the option to put on external or internal storage. Although I don't think I compiled TWRP to use "in place" install, which would mean it still copies to internal. I'm not sure on this one, so internal is probably the best bet, but I have performed it on external and it works fine. You will need space on internal storage to do it.
Menu Option 2 - Return Nabi to Stock 1.9.37. Android not booting.
This is useful if you are in a situation that has left Android unbootable and you have no backup. Otherwise it's the same as Option 1. You will boot to TWRP and then perform the restore. Again TWRP will still be installed afterward, no be completely at stock you will have to remove it by Main Menu 4. I have it this way in the event you plan to immediately reroot it.
Notes: If you want to view this menu in the lite version, you need to open the file havefiles.txt, it is located in the stockimage folder. Change the line backup=false, to backup=true. You can then view the menu. You can then copy files you wanted to the stockimage folder and restore. Since the restore portion is manual I'm not sure why you would ever use it this way but if you want to play around that's how to enable it.
MENU 4 - Install Recoveries
Menu Option 1 - Install TWRP 2.3.3.0 for Nabi Version 1.9.37
Installs TWRP 2.3.3.0. This is the version that everyone should be trying to use first before trying other versions. This is the version that has symlinked paritions since it is thought currently their might be different partition structures for various Nabi's. Newer Nabi kernel and fixes touchscreen issues for some people that were using 2.2.2.1.
Menu Option 2 - Install TWRP 2.3.3.0 for Nabi Versions prior to 1.9.37
Use this option if Option 1 didn't work for you. Older Nabi kernel, otherwise same as Option 1.
Menu Option 3 - Install TWRP 2.2.2.1
This is the original TWRP from the first Nabi rooting thread. Use this if the other 2 don't suit you, or you just trust my compile skills, which may be prudent... :silly:
Menu Option 4 - Install Stock Recovery
Installs stock recovery. This is useful for taking an OTA, or completely returning Nabi to stock.
Menu Option 5 - About Recovery Installer
A leftover from my initial recovery installer, I was too lazy to remove it.
Notes: TWRP installs are based off my work in this thread if you want to read more.
MENU 5 - Tablet Information
Nabi Information, serial, version, build date, device mode, internal/external size, detected backups.
Note: This only detects if a backup folder is present, not if there are backups actually inside the folder. The only way this would be the case is if you manually deleted them or just made a empty folder in there, so be aware. Also if you have made a ramdisk modifying init.rc, used creative symlinking to swap internal and external SD, or used a prebuilt app to swap this screen may be incorrect.
MENU 6 - Lockscreen Mod Tool
Don't use this if you have updated to v2.0.5, I haven't tested but the framework-res.apk was updated in the 2.0.5 update and if you are using the old one you could throw yourself in to a bootloop
Menu Option 1 - Install custom lockscreen
Use this to install a custom lockscreen. You will need a picture that is in .png format and is 1440 x 903. A explorer window will open up showing you the location to put the picture. The file MUST be name lockscreen.png, there is one there that is black, you can overwrite it be there MUST ALWAYS be a lockscreen.png file in that folder if you use the tool. Bad things could possibly happen if it doesn't. You have the option to manually install the lockscreen, or automatically install it after the zip is built. In either case it copies whatever you named the zip(you are prompted for a name) to the internal SD, along with a file called lockorig.zip. The lockorig.zip is there if you mess up and Android won't boot you can manually install the lockorig.zip in TWRP to put it back to stock.
Menu Option 2 - Install stock lockscreen
Use this to return to stock. Remember if you used Option 1 there will already be the stock lockorig.zip on your internal storage.
Notes: If you make a custom lockscreen, while it copies the installable zip to your device it also copies it to your picture folder so you can share with others. Make sure you visit in share your creation over in this thread.
MENU 7 - Patch NabiLab
Menu Option 1 - Install Patch
For any updates to Nabi Lab this is where you can automatically load them. Basically you will download NabiPatch.zip and place the entire zip in the patch folder. No unzipping just the single file. Then run this option.
Note: Since this option wasn't in NabiLab v1, we have to do some trickery when coming from version 1 to install, so the procedure is different, all subsequent patches will be the above method however. Coming from version 1 you will need to download NabiLabv2update.zip and extract it into the NabiLab directory such that RunOncePatch.bat is in same directory as NabiLab.bat, and the other file NabiPatch.zip is in the folder "patch", then run the RunOncePatch.bat If you extract into your NabiLab directory it won't be a problem, the hint you didn't do it right will be if the RunOncePatch.bat isn't right there with NabiLab.bat
Credits
jzmtaylor - Original Nabi root. Nabi device code from which to build newer TWRP
t499user - Gapps fix
Dees_Troy - TWRP build tutorial
Eric Karz - Lockscreen Modding, NabiLab scripting
1wayjonny - Universal Driver base code
TeamWin - They are the guys that make TWRP possible
In all honesty everyone that has participated in the main Gapps thread has indirectly made the program what it is from testing, to information, to troubleshooting and everything else Nabi.
Hmmm just for giggles I installed Nabi Lab on my Computer to change the Lock Screen and it does not want to read my Tablet.
Thanks for this! Driver install didn't work for me on any of my computers...well it did install a driver but didn't read my nabi. Uninstalled nabilab driver and used PDA.net and all was good. Nabilab worked great installing recovery root n gapps! Thanks agn.
Sent from my EVO using xda app-developers app
DarkAngel said:
Hmmm just for giggles I installed Nabi Lab on my Computer to change the Lock Screen and it does not want to read my Tablet.
Click to expand...
Click to collapse
So it's saying error Nabi not detected or no driver? Is the device seen in Device Manger? Really can be only 2 thing, adb conflict or device driver.
strive53 said:
Thanks for this! Driver install didn't work for me on any of my computers...well it did install a driver but didn't read my nabi. Uninstalled nabilab driver and used PDA.net and all was good. Nabilab worked great installing recovery root n gapps! Thanks agn.
Click to expand...
Click to collapse
What operating systems and did you have any previous Android devices connected to the computer? Sometimes I noticed it will conflict with any previous driver installs, and while installing the driver is successful it won't use it. I guess it doesnt matter if it's working for you with PDAnet. If you are on vista or later you can try running pnputil -e from command prompt and look through all the oemxx.inf's and see how many google,inc android drivers there are.
aicjofs said:
So it's saying error Nabi not detected or no driver? Is the device seen in Device Manger? Really can be only 2 thing, adb conflict or device driver.
What operating systems and did you have any previous Android devices connected to the computer? Sometimes I noticed it will conflict with any previous driver installs, and not while installing the driver is successful it won't use it. I guess it doesnt matter if it's working for you with PDAnet. If you are on vista or later you can try running pnputil -e from command prompt and look through all the oemxx.inf's and see how many google,inc android drivers there are.
Click to expand...
Click to collapse
Sorry should have been more specific. It detects it via Device Manager but not via Nabi Lab. I am running Windows 7 x64
DarkAngel said:
Sorry should have been more specific. It detects it via Device Manager but not via Nabi Lab. I am running Windows 7 x64
Click to expand...
Click to collapse
Is it detecting 2 Nabi interfaces in Device Manager? I can see it's detecting the MTP interface, but what about the ADB interface. Usually ADB appears under Android Device and MTP under Portable Devices. Is there anything under "Other Devices"? NABI2-NV7A something or other? Only other thing I could think is that there is a hung up ADB process running, kill it in task manager or reboot.
sorry knew i should have stated my operating system. my main computer is a macbook and i have a old xp laptop n xp netbook that i use for flashing. i also tried it on my moms win7 desktop and a friends win8 desktop without luck. never changed in device manager from NABI2-NV7A with yellow exclamation point. ive flashed a bunch of phones from my laptop and probably do have drivers installed from who knows what.. it did install the driver but nabi wasnt detected as adb interface. rebooted computers n nabi after installs. i didnt have any other device attached at the time.
aicjofs said:
Is it detecting 2 Nabi interfaces in Device Manager? I can see it's detecting the MTP interface, but what about the ADB interface. Usually ADB appears under Android Device and MTP under Portable Devices. Is there anything under "Other Devices"? NABI2-NV7A something or other? Only other thing I could think is that there is a hung up ADB process running, kill it in task manager or reboot.
Click to expand...
Click to collapse
Yes it's detecting on both. The only thing that has been baffling me for some time is back when I had a Windows phone and after I switched to android, what appears to show in "Other" looks like my old TouchPro2. I can not delete that.
strive53 said:
sorry knew i should have stated my operating system. my main computer is a macbook and i have a old xp laptop n xp netbook that i use for flashing. i also tried it on my moms win7 desktop and a friends win8 desktop without luck. never changed in device manager from NABI2-NV7A with yellow exclamation point. ive flashed a bunch of phones from my laptop and probably do have drivers installed from who knows what.. it did install the driver but nabi wasnt detected as adb interface. rebooted computers n nabi after installs. i didnt have any other device attached at the time.
Click to expand...
Click to collapse
I had trouble with computers that has previous drivers installed sometimes, other times not. I tested fresh installs on XP 32, 7 32, 7 64, 8 64 and everything went fine, but it was much more hit and miss with computers that already had a slew of drivers. I'm more concerned that NONE of yours would work, although I guess it's offset by the fact that PDAnet driver worked and that NabiLab itself worked fine.
Yes it's detecting on both. The only thing that has been baffling me for some time is back when I had a Windows phone and after I switched to android, what appears to show in "Other" looks like my old TouchPro2. I can not delete that.
Click to expand...
Click to collapse
Well you have me baffled too! haha. If you run "adb devices" from cmd prompt what is the output? You have a modified cmd processor, that opens batch files? Seems like everything is in place. It case it's something with the program did you come from v1 NabiLab and patch or just v2?
f you want to play with the lockmod while we figure it out, the pic zip you made will still be in "pictures" folder, just let that portion of the program run until it errors when it tries to adb transfer. You can manually transfer to SD and flash TWRP.
aicjofs said:
I had trouble with computers that has previous drivers installed sometimes, other times not. I tested fresh installs on XP 32, 7 32, 7 64, 8 64 and everything went fine, but it was much more hit and miss with computers that already had a slew of drivers. I'm more concerned that NONE of yours would work, although I guess it's offset by the fact that PDAnet driver worked and that NabiLab itself worked fine.
Well you have me baffled too! haha. If you run "adb devices" from cmd prompt what is the output? You have a modified cmd processor, that opens batch files? Seems like everything is in place. It case it's something with the program did you come from v1 NabiLab and patch or just v2?
f you want to play with the lockmod while we figure it out, the pic zip you made will still be in "pictures" folder, just let that portion of the program run until it errors when it tries to adb transfer. You can manually transfer to SD and flash TWRP.
Click to expand...
Click to collapse
This is the first time installing it actually since I Rooted and installed GApps through Ubuntu. I just wanted to try it so I can try and change the lockscreen image and update TWRP while I was there also. I downloaded v2 with the backup. I was going to try v1 to see if that made a difference or try the PDAnet driver.
Sent from my NABI2-NV7A using Tapatalk HD
Worked fine as soon I realised I wasnt waiting for the files to transfer :banghead:
Sent from my GT-I9100 using xda premium
kieronw3 said:
Worked fine as soon I realised I wasnt waiting for the files to transfer :banghead:
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
I could add a line that says, go check the mail, run to 7-11, trim the dogs toe nails. Hehe. Glad it worked eventually. 58 or so downloads and not many complaints, I can live with that, better then a brickfest. :laugh:
Nice job on lab update. Good use of the colors
i have a Request
could you add 'upgrade Twrp to the latest version'
maybe under Advanced User tool.
then if for some reason there is changes in the future you could just put the image file down load in that folder and update by click of a button ?
Win 8 64bit... Never had other android drivers installed on this machine. I dont see it listed in device manager at all. But the machine definitely sees it in my computer, and I also see it go into debug mode on the tablet. Confused,,,
Eric Karz said:
Nice job on lab update. Good use of the colors
i have a Request
could you add 'upgrade Twrp to the latest version'
maybe under Advanced User tool.
then if for some reason there is changes in the future you could just put the image file down load in that folder and update by click of a button ?
Click to expand...
Click to collapse
I need something for a version 3, so why not?
delio77 said:
Win 8 64bit... Never had other android drivers installed on this machine. I dont see it listed in device manager at all. But the machine definitely sees it in my computer, and I also see it go into debug mode on the tablet. Confused,,,
Click to expand...
Click to collapse
Are you using NabiLab or just the drivers I linked in another post? Is it detecting it in NabiLab? If it is the drivers have to be there under Android Device.
When I try to install recovery, root, gapps, I get stuck on waiting for device. My device detects just fine. I think it may be an issue with fastboot drivers, not ADB drivers? Because ADB reboots the device into fastboot just fine. But once it's there, it just sits on "waiting for device". Any thoughts?
bradleyw801 said:
When I try to install recovery, root, gapps, I get stuck on waiting for device. My device detects just fine. I think it may be an issue with fastboot drivers, not ADB drivers? Because ADB reboots the device into fastboot just fine. But once it's there, it just sits on "waiting for device". Any thoughts?
Click to expand...
Click to collapse
Have you verified that your fastboot drivers are working? If you navigate to the folder where adb.exe and fastboot.exe are you can just iddues the command fastboot devices to see if the device is connected while in fastboot.
1. How would you update a Nabi that has been originally rooted on .23 with jmz's work. I'd also like to clean up the optimizing android apps issue?
2. Would it be possible for you to add a "Clone Nabi" option to the Lab. Many people have more than one Nabi to tend to and it would be nice if you could duplicate the setup across multiple devices. I did it by hand for a dozen and let's just say it's a bit painful.
Mostly, though I wanted to thank you and all of the other developers for their work. There is a classroom full of 1st graders that use the Nabis everyday. They used to be stuck with nine-year-old Dell computers that would take 15 minutes just to boot...now things are easy and fun. You guys have really made my donation of the Nabis a great project. Thanks!
aicjofs said:
I need something for a version 3, so why not?
Are you using NabiLab or just the drivers I linked in another post? Is it detecting it in NabiLab? If it is the drivers have to be there under Android Device.
Click to expand...
Click to collapse
I am using NabiLab and it said not detected. I eventually got it to work with PDAnet
Ken Esq said:
1. How would you update a Nabi that has been originally rooted on .23 with jmz's work. I'd also like to clean up the optimizing android apps issue?
2. Would it be possible for you to add a "Clone Nabi" option to the Lab. Many people have more than one Nabi to tend to and it would be nice if you could duplicate the setup across multiple devices. I did it by hand for a dozen and let's just say it's a bit painful.
Mostly, though I wanted to thank you and all of the other developers for their work. There is a classroom full of 1st graders that use the Nabis everyday. They used to be stuck with nine-year-old Dell computers that would take 15 minutes just to boot...now things are easy and fun. You guys have really made my donation of the Nabis a great project. Thanks!
Click to expand...
Click to collapse
So is the device still on .23? Probably 3 ways to go about it if that's the case,
1) backup apps with something like Titanium backup, restore the original backup "stockunrooted" of Nabi, reinstall stock recovery, update to 1.9.37, reapply root and gapps, restore app backups, or
2) backup apps, restore a stock 1.9.37 from NabiLab, reapply root, gapps, restore app backup. or
3) you can try updating the safe OTA's people have posted, I came late to the game so I didn't study those, I know there is the wifi issue between kernel and modules if you don't do it right. If you already are on .37 but just rooted back on .23 the only thing to do is gapps to fix android upgrading. The optimizing android is fixed by flashing the fixed gapps.(Gapps only, option 2 then option 3 in NabiLab)
How would you like to see cloning? It just loops through the procedure and you just keep plugging Nabi? Or a restoring image to all of them. Help me visualize what you think would be best.
I'm not sure how you are doing it. How I would do it currenlty for Nabilab if I had 20 brand new Nabi's is like this. Once all Nabi's are at version you want (1.9.37)
Take one Nabi and do a recovery, root, gapps, backup(Option 2, Option 1)
Grab the backup it made and move it to computer.
Take remaining Nabi's
Install TWRP 2.3.3.0(Option 4, Option 1)
Install Root Only(Option 2, Option 4)
Install Gapps Only.(Option 2, Option 3)
What you accomplish here is making the backup only once. So first Nabi takes 15 min, the remaining maybe 3 min.
No thank you for popping in with some feedback.
HOX+ Tutorial for Unlocking, Rooting & installing a custom ROM [BEGINNERS FRIENDLY ]
[SIZE="+2"]-- Step-by-Step Tutorial for Unlocking, Rooting and Installing a Custom Rom for your HTC ONE X+ --[/SIZE]
Here is my beginner friendly manual method for Unlocking, installing an alternative Recovery, Rooting and installing a custom ROM for HTC ONE X+
Why should you do it manually?
At first glance, an all in one tool to do the work for us seems a good idea, but what happens if a step fails? Do you know how to use the right tools to recover? Does your computer have the basics prerequisites installed to allow you to recover your device? In performing this task manually all the basic tools will be installed and in the event that some bugs occurs, at least you will have the certainty of having all the tools in hand to fix it. It is an easy task to obtain if you follow this step-by-step tutorial rigorously. All you need is in this thread, no need to search to find that file or that app, all you need is 30-60 minutes of attentive reading and performing the described procedure. If something goes wrong, read again and simply perform the procedure another time. Remember, you decided to root and customize your phone, no one can be held responsible for your action. If something goes wrong we are here to help, but if you have the ability to read, you should be able to perform this without a swear.
Be aware that the HTC ONE X+ comes in two versions, one version called INTERNATIONAL (ENRC2B) that come WHITOUT the so-called LTE technology.
Then the North American version for AT&T and TELUS (EVITARE_UL) version that comes WITH so-called LTE technology.
LTE is an initialism of Long-Term Evolution. To determine which version your phone is you can simply download an application called CID Getter from the Google Play store available HERE Simply open the program once installed and navigate to the line named [ro.aa.project]:[your version model]
ENRC2B is INTERNATIONAL
EVITARE_UL is AT&T / TELUS
Now that you know which version is your phone lets start with the installation of your SDK tool folder. ADB is a versatile command line tool that lets you communicate with your Android device. This tool is MANDATORY and will serve you very often. Let's do this.
-- Screenshots for the visual ones --
{
"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"
}
____________________________________________
[SIZE="+1"]-- Enabling USB debugging mode --[/SIZE]
On your phone simply follow this path : Settings -> Developer options -> Turn the option ON -> under Debugging -> tick USB debugging option Debug mode when USB is connected
That's it, done!
-- Screenshots for the visual ones --
____________________________________________
[SIZE="+1"]-- Java Installation --[/SIZE]
This is a prerequisite to have a flawlessly working SDK tool installation.
Click on the following link to download it on Java's website : Free Java Download
On the next page, do not click on Agree and Start Download, instead click on See all Java downloads.
Which should you choose? If you have a 64-bit Windows OS you MUST install the two versions (both 32-bit and 64-bit), otherwise the 32-bit is sufficient for a 32-bit Windows OS.
Before installing the latest version of Java, it is recommended to uninstall all previous Java's installation. (How to -> Remove Older Versions)
Complete the required installation depending of the type of Windows installation.
You are all done for Java.
-- Screenshots for the visual ones --
____________________________________________
[SIZE="+1"]-- SDK Tools Installation --[/SIZE]
First step is to download the SDK Manager, to do so click on this link -> Download the SDK
Next locate on the bottom of your screen the USE AN EXISTING IDE, click on it.
On the Get the Android SDK page, tick the I have read and agree with the above terms and conditions box and click on the Download the SDK Tools for Windows button.
Navigate to your Download folder, and locate a file named like this: installer_r21.1-windows.exe (N.B. The r21.1 version was available when I did this how to, your version could be different.)
Double click on the installer_r21.1-windows.exe file to start the installation. Take good note where the file will be installed, generally the default SDK path is : C:\Users\your_session's_name\AppData\Local\Android\android-sdk.
Now, navigate to the path of the SDK installation folder.
Select all (CTRL + A) in this folder and Copy (CTRL +C) them for the next step.
Now you need to create a new folder at the root of your C:\ drive named : AndroidSDK
Open up the newly created folder and Paste (CTRL + V) the previously copied files.
Stay in this folder and double click on the SDK Manager icon.
The SDK Manager will open a new window, click on Deselect All, then tick the following line in Tools : AndroidSDK Platform-tools
Click on Install 1 Package..., accept the license agreement and click on Install let the manager do it's thing.
Click on Done and close the manager's window.
Congrats! You have created successfully your SDK tool!
Wait! Let's clean your computer a bit....
Go back to the previous folder, the one located in this path : C:\Users\your_session's_name\AppData\Local\Android\android-sdk
Click on the Uninstaller, we don't need this one anymore. Don't worry the other AndroidSDK folder won't be deleted.
Voilà! You are done with this part.
-- Screenshots for the visual ones --
____________________________________________
[SIZE="+1"]-- Creating of script file for a fast access --[/SIZE]
Locate the Platform-tools sub-folder in the AndroidSDK folder.
Right click in a empty space of the folder and select in the contextual menu New -> Text Document
Open this new Text Document and Copy/Paste this : c:\windows\system32\cmd.exe
Save this file as : Start SDK.bat
Acknowledge the : If you change file extension... warning.
Right click your new created Start SDK and send a shortcut on your Desktop.
Done! If you try to double click on your Start SDK shortcut, a command window should open with something like these lines :
Code:
C:\AndroidSDK\platform-tools>c:\windows\system32\cmd.exe
Microsoft Windows [version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\AndroidSDK\platform-tools>
Success!
____________________________________________
[SIZE="+1"]-- Installing HTC's Drivers --[/SIZE]
This one is very easy, simply download and run the installer and let Windows do the rest. Drivers compatbile 32-bit or 64-bit
Download the Self-install HTCDriver_4.0.1.001.exe/
Make sure your phone is not plugged on your computer via the USB cable.
Simply run the installer of the driver you've just downloaded.
Once the installation is completed, simply plug your phone via your USB cable and Windows "wizard manager" will now detect your phone.
If it doesn't work, unplug your phone and reboot your computer. Then plug back your phone once rebooted.
Done!
-- Screenshots for the visual ones --
____________________________________________
[SIZE="+1"]-- Let's try all this! --[/SIZE]
With your phone plugged on your USB cable...
From your Desktop, double click on your Start SDK shortcut.
In the command window, at the command line : C:\AndroidSDK\platform-tools> type this -> adb devices (Enter)
The serial number of your phone should appear in the command window. If it is the case, then try this again : C:\AndroidSDK\platform-tools> type this -> adb reboot (Enter)
Your phone will now Reboot
If all this worked, you have a successful SDK Tools installation!
-- Screenshots for the visual ones --
____________________________________________
[SIZE="+1"]-- Unlocking your Bootloader --[/SIZE]
This step is mandatory since there is no other solution yet to unlock the bootloader on the ONE X+. !! PLEASE BE ADVISED TO BACKUP ALL YOUR DATA FROM YOUR PHONE'S USB MEDIA, THIS PROCEDURE WILL TOTALLY AND FULLY WIPE YOUR PHONE. ALSO, BE ADVISED THAT YOUR WARRANTY IS MOSTLY VOID !!
Before doing this you can visualize what is an unlocking procedure HERE. Or you can watch this video HERE
Ready?
To unlock your bootloader go to HTCDev create your account with a valid email address, then select on the right field : All Others Supported Devices and click on Begin Unlock Bootloader (If you followed this tutorial to the letter, your SDK tool/adb command should work flawlessly for this procedure.)
Follow the on screen instructions to get your Token ID.
To submit your Token ID you need to highlight everything between the two spades ♠< < < < <Identifier Token Start> > > > > ....token ID string.... < < < < <Identifier Token End > > > > >♠
Now simply right click and Copy/Paste in the correspondent field to submit.
You will received your unlocking code in your email account (almost instantly, check in your SPAM folder if it take more than 5 minutes) you registered with on HTCDev.
Complete the unlocking procedure and wait for your phone to reboot.
Congrats! The Unlocking process is successful!
____________________________________________
[SIZE="+1"]-- Recovery installation --[/SIZE]
Let's install your new recovery now. !! Be advised that installing CWM Recovery on this device is NOT RECOMMENDED, this recovery is untested, unreliable, unsupported and outdated. The ONLY recovery you should use on your HTC ONE X+ is TWRP Recovery !!
Download this TWRP Recovery for the International version (ENRC2B) : HERE MD5:0a708f4c27d69d2d1505ce7832d4b3be
Download this TWRP Recovery for the AT&T/TELUS version (EVITARE_UL) : HERE MD5:6e24a6686bc4840043a57cb61b63f22c
Once downloaded to simplify the operation rename your file like this : TWRPrecovery.img
Take this TWRPrecovery.img file and Copy/Paste it in the platform-tool of your SDK folder.
TIP : Since your are in the platform-tool folder you can create a batch file to open a command window right from your Desktop.
Do this directly into the platform-tools folder.
Right click on an empty space and select Create New text document
In the new text paste this : c:\windows\system32\cmd.exe
Save it with this name StartADB.bat (important to save it with .bat extension and overwrite the warning)
Now right click again on your new .bat file, and create a shortcut to your Desktop.
Now try to : adb devices your phone via your new Start ADB batch file directly form your Desktop shortcut with your phone plugged on your USB cable.
If you have a serial number as confimation you have done it right!
This a ONE TIME OPERATION TO DO, IT WILL WORK AS LONG AS THE SHORTCUT WILL BE ON YOUR DESKTOP.
Time to plug your phone on your USB cable if it is not already plugged.
Click on Start SDK, in the command window type at the prompt > adb devices (Enter)
Confirmation of the serial.
At the prompt type >adb reboot-bootloader (Enter)
The phone will reboot in bootloader mode.
Make sure the FASTBOOT USB is highlighted.
At the prompt type >fastboot flash recovery TWRPrecovery.img (Enter)
If Success is achieved, type again at the prompt >fastboot erase cache (Enter)
You now have TWRP Recovery installed.
Unplug your USB cable and hit Power button one time.
Select Recovery with your Volume rocker.
Hit Power button one time.
Your phone should reboot in Recovery
Familiarize yourself with it.
Click on BACKUP and perform a full backup of your actual ROM.
Once done REBOOT System.
-- Screenshots for the visual ones --
____________________________________________
[SIZE="+1"]-- Time to install the root --[/SIZE]
This is fast to obtain, simply download this SuperSU.zip file and transfer this at the root of your USB media (SD card).
You can now click on your Start SDK batch file from your Desktop to start a command window while your phone is still plug on the USB cable.
Type at the prompt > adb devices (Enter)
Then again at the prompt (if serial confirmation is positive) >adb reboot-bootloader (Enter)
Phone will reboot in Bootloader
Unplugged the USB cable
Hit Power button once
Select Recovery in the menu with the Volume rocker
Hit Power once to reboot in Recovery
Select Install
In the Select Zip to Install menu located your SuperSU.zip file
Click on it and in the new menu simply Swipe to Confirm Flash
Reboot system
You are done rooting your phone.
____________________________________________
[SIZE="+1"]-- Custom ROM installation --[/SIZE]
So far all is good and the above instructions were all successful as we expected now you want that wonderful ROM from that thread, right? This procedure is very simple, but one rule applied here : ALWAYS BACKUP YOUR ACTUAL ROM BEFORE FLASHING ANYTHING! Do transfer it on your computer and keep this file in a safe place follow this path to locate the TWRP folder. At the root of your SD card locate TWRP -> Backups -> your_One X+_serial_number -> You should have one file stamped with date and time. This is your backup you can rename it. Copy/Paste it and put it in a safe place in your computer.
Now the fun part begin!
Once you have selected the ROM for your model version INTERNATIONAL OR AT&T/TELUS, simply download it.
Take also the correspondent boot.img that need to be flashed just before or just after (doesn't really matter) the ROM installation.
Transfer your ROM.zip at the root of your internal storage of the HTC ONE X+ via your USB cable.
While the ROM is transferring on your phone, simply extract the boot.img that match your ROM, rename it for an easier recognition (i.e. Viperboot.img, Eleganciaboot.img, ARHDboot.img, etc) Copy/Paste it in your platform-tool folder (SDK)
Leave your phone plugged to your USB cable
Click on Start SDK, in the command window type at the prompt > adb devices (Enter)
Confirmation of the serial.
At the prompt type >adb reboot-bootloader (Enter)
The phone will reboot in bootloader mode.
Make sure the FASTBOOT USB is highlighted.
At the prompt type >fastboot flash boot insert_your_boot_image_name_here.img (Enter)
If Success is achieved, type again at the prompt >fastboot erase cache (Enter)
You now have a customized boot.img installed.
Unplug your USB cable and hit Power button one time.
Select Recovery with your Volume rocker.
Hit Power button one time.
Your phone should reboot in Recovery
(!! The following instruction are with TWRP Recovery installed !!)
Select Wipe menu, then select Factory reset (swipe), select System (swipe)
Go back to the Install menu and select it.
Locate your ROM.zip and select it.
Swipe to confirm.
Probably Aroma installer will start, simply follow the on-screen instructions and complete the installation.
!! Confirm the Rebooting option ONLY IF YOU FLASHED THE BOOT.IMG BEFORE ROM INSTALLATION !!
Otherwise select the Reboot Bootloader and perform the 4 to 8 steps
Reboot the phone.
-- Screenshots for the visual ones --
Your phone should Reboot with your new ROM, put your phone aside for ~10 minutes to let the new installation performing all it's task. Then you can customize your phone at your desire. Don't forget to reboot your phone when done.
Enjoy!
If you found something hard to understand, let me know, I will do my best to rearrange this tutorial.
Also let me know by PM all the orthographic errors you found, I will fix this ASAP.
If this helped you in anyway please take the time to rate this thread.
Happy flashing!
Lucky Thirteen said:
you should be able to perform this without a swear.
Click to expand...
Click to collapse
I don't do anything without swearing, but thanks for a great, thorough tutorial. Mods - please sticky this!
sup, i have been using your guide to root and i have been getting trouble getting through the "adb device" part, no matter how many htc drivers i download i end up with the same error, it says devices but mine is never shown. but i guess its all good now as is followed it through the htcdev site...... but anyways would like to know how i can add these roms cause i am really confused about there kernels and stuff would be appreciated if you could explain how it works and whats a good rom to start with.
Hi decoy,
Can you specified at which portion of the tutorial you are stuck at?
i was getting stuck at lets try all this---> AndroidSDK\platform-tools> type this -> adb devices. over here when i type this my device does not show up i have tried updating my drivers several times still no success.
Are you with stock OS on your phone?
Have you tried another USB port? USB 3.0 ports are known to create issues. Also make sure your USB cable is not on a USB hub. If you have Enable USB debugging and you have followed the procedure to the letter, obviously there is a little thing missing.
Please try to describe your computer type and Windows version, where your USB cable is plugged in your computer, is Java installed correctly. Do describe at the most of your knowledge your situation. If it's really not working we can try to arrange a TeamViewer session to have a deeper look at it.
Yo its cool now cause I already rooted it, I guess the problem was the device connection on adb, as it was not being shown even though my computer recognized it, but when I went through the steps on Htcdev it worked cause I was able to unlock and install the recovery..... And I was using it on a usb 3 hub on windows 7. And yes at the moment I am running the stock Rom. I have An other question if you don't mind.... When you install the international recovey how does the back up work and how can you use it?
Sent from my HTC One X+ using xda app-developers app
You simply reboot in recovery and you will see menus, from there it is easy simply pick your choice and swipe to confirm.
Once you will be in Recovery you will see how simple it is, it is very intuitive.
New to android and new to rooting, thanks so much for this guide, unlocked, rooted and custom rom installed. I had no issues with this guide and it was a clean and new experience
Thanks! Successful completion with a few questions
First off, thank you very much for the thorough and easy to follow guide. This was my first attempt at installing a custom ROM on my phone and it went without a hitch.
I do have a few questions for you. First, I decided to install the Elagancia rom. It was a somewhat arbitrary decision, but is there any place that lists the pros and cons about various roms so it can be easier to decide which is right for my phone?
I was hoping to find a 4.2.2 based rom that was pretty much stock without sense, but I couldn't find one for the AT&T HTC One X+, is there one out there that I'm missing?
When I went through the install, it asked me various questions about install options. I didn't know what many of the options did, so I was wondering if there was a guide somewhere about the rom which describes the tweaks I could install. And I also wanted to know if there's a way to go back and change my options without wiping the phone clean and doing a fresh install again.
And again, thanks!
BlueWRXPride said:
First off, thank you very much for the thorough and easy to follow guide. This was my first attempt at installing a custom ROM on my phone and it went without a hitch.
Click to expand...
Click to collapse
Glad if it helped you! Please take the time to rate this thread, it will help to reference it. Take the time also to read this FAQ, you will probably learn a trick or two about your phone.
BlueWRXPride said:
I do have a few questions for you. First, I decided to install the Elagancia rom. It was a somewhat arbitrary decision, but is there any place that lists the pros and cons about various roms so it can be easier to decide which is right for my phone?
Click to expand...
Click to collapse
No, there's not a specific thread for that usage, but in each ROM thread there are Changelog and Screenshots that describing what you should expect from that specific ROM. It's not perfect but generally it's a good... appetizer!
BlueWRXPride said:
I was hoping to find a 4.2.2 based rom that was pretty much stock without sense, but I couldn't find one for the AT&T HTC One X+, is there one out there that I'm missing?
Click to expand...
Click to collapse
Unfortunately, not yet, at least, not that I know of.
BlueWRXPride said:
When I went through the install, it asked me various questions about install options. I didn't know what many of the options did, so I was wondering if there was a guide somewhere about the rom which describes the tweaks I could install. And I also wanted to know if there's a way to go back and change my options without wiping the phone clean and doing a fresh install again.
Click to expand...
Click to collapse
Again, in each Changelog and Add-on section of the intend ROM should have a brief description of tweaks and options available in Aroma Installer, but you can perform a search or ask for a description if you don't find an satisfying answer about a given option.
If you flash over the same ROM, all your settings, apps and data will be preserved, only the system will be updated, so simply flash over to change some options. The vital thing is to have a perfect backup done and saved just in case something goes bad with one flash or update.
BlueWRXPride said:
And again, thanks!
Click to expand...
Click to collapse
You are welcome!
I have a more general question about different roms. First, I'm assuming while it's easy to load a different ROM on the phone, there's no way to put it on there and try it out without wiping your phone clean. That makes the process of trying our different roms to find what you like pretty lengthy. Am I missing anything there?
Second, am I right to assume that most roms that are based of Sense 4+ will more or less look the same, and that the variations from rom to rom will mostly be behind the scenes?
BlueWRXPride said:
I have a more general question about different roms. First, I'm assuming while it's easy to load a different ROM on the phone, there's no way to put it on there and try it out without wiping your phone clean. That makes the process of trying our different roms to find what you like pretty lengthy. Am I missing anything there?
Click to expand...
Click to collapse
Well there is some way to migrate your apps & DATA from one ROM to another with applications like Titanium Backup or My Backup Pro. What I usually do is a full backup of my everyday ROM just before trying another ROM, than I can full wipe (this mean a factory reset and system format) and install the intend ROM I wanna try on my phone without setting everything at the first boot, I play with it and check for options, fluidity, speed, customization,etc. If I find the ROM worth installing my thing, I go on and start the processus to migrate my personal preferences, apps and DATA. This process can take two,three,four days to set the ROM like I want. I simply full backup the unready installed ROM and simply restore my everyday ROM until the other will be completely up and running. Then I suddenly have two perfect ROM to play with only by restoring them at my desire.
BlueWRXPride said:
Second, am I right to assume that most roms that are based of Sense 4+ will more or less look the same, and that the variations from rom to rom will mostly be behind the scenes?
Click to expand...
Click to collapse
Even if the base is the same, the developers do magnificent work to customize, personalize them very differently. Options and tweaks are very different from one dev to another. They all have their personal strength and usually the ROM reflects that talent.
Again, you have to try some at first, then you will see the personality of each ROM. You will learn also if you like a strongly customized ROM or maybe you will prefer a more Vanilla ROM (close as stock as possible) it is all yours to discover.
Lucky Thirteen said:
Well there is some way to migrate your apps & DATA from one ROM to another with applications like Titanium Backup or My Backup Pro. What I usually do is a full backup of my everyday ROM just before trying another ROM, than I can full wipe (this mean a factory reset and system format) and install the intend ROM I wanna try on my phone without setting everything at the first boot, I play with it and check for options, fluidity, speed, customization,etc. If I find the ROM worth installing my thing, I go on and start the processus to migrate my personal preferences, apps and DATA. This process can take two,three,four days to set the ROM like I want. I simply full backup the unready installed ROM and simply restore my everyday ROM until the other will be completely up and running. Then I suddenly have two perfect ROM to play with only by restoring them at my desire.
Click to expand...
Click to collapse
Thanks, that makes sense. Are you able to change between roms without hooking up to the computer and using adb? In your instructions you talk about how you have to flash the boot.ini file that is specifically for the rom you want so is there a way to take care of that without your computer?
I am having trouble here:
•While the ROM is transferring on your phone, simply extract the boot.img that match your ROM, rename it for an easier recognition (i.e. Viperboot.img, Eleganciaboot.img, ARHDboot.img, etc) Copy/Paste it in your platform-tool folder (SDK)
•Leave your phone plugged to your USB cable
1.Click on Start SDK, in the command window type at the prompt > adb devices (Enter)
2.Confirmation of the serial.
3.At the prompt type >adb reboot-bootloader (Enter)
Where do I click on start sdk?
golmar88 said:
I am having trouble here:
•While the ROM is transferring on your phone, simply extract the boot.img that match your ROM, rename it for an easier recognition (i.e. Viperboot.img, Eleganciaboot.img, ARHDboot.img, etc) Copy/Paste it in your platform-tool folder (SDK)
•Leave your phone plugged to your USB cable
1.Click on Start SDK, in the command window type at the prompt > adb devices (Enter)
2.Confirmation of the serial.
3.At the prompt type >adb reboot-bootloader (Enter)
Where do I click on start sdk?
Click to expand...
Click to collapse
Start SDK refers to the cmd file you created on your desktop in the -- Creating of script file for a fast access -- section
Mr. Thirteen, do you think you could offer me a little more help? Please refer to the post below.
http://forum.xda-developers.com/showthread.php?t=2226031
golmar88 said:
I am having trouble here:
•While the ROM is transferring on your phone, simply extract the boot.img that match your ROM, rename it for an easier recognition (i.e. Viperboot.img, Eleganciaboot.img, ARHDboot.img, etc) Copy/Paste it in your platform-tool folder (SDK)
•Leave your phone plugged to your USB cable
1.Click on Start SDK, in the command window type at the prompt > adb devices (Enter)
2.Confirmation of the serial.
3.At the prompt type >adb reboot-bootloader (Enter)
Where do I click on start sdk?
Click to expand...
Click to collapse
BlueWRXPride said:
Start SDK refers to the cmd file you created on your desktop in the -- Creating of script file for a fast access -- section
Click to expand...
Click to collapse
Probably you just missed a section like BlueWRXPride told you.
trouble with file Start SDK.bat
Lucky Thirteen said:
If you found something hard to understand, let me know, I will do my best to rearrange this tutorial.
Also let me know by PM all the orthographic errors you found, I will fix this ASAP.
If this helped you in anyway please take the time to rate this thread.
Happy flashing!
Click to expand...
Click to collapse
Hey lucky thriteen ive been doing everything step by step but im having trouble making the note and copying and pasting c:\windows\system32\cmd.exe once i create the shortcut and open it its nothing like how you show it in the example any idea what it could be?? thanks
---------- Post added at 04:47 PM ---------- Previous post was at 04:41 PM ----------
Lucky Thirteen said:
If you found something hard to understand, let me know, I will do my best to rearrange this tutorial.
Also let me know by PM all the orthographic errors you found, I will fix this ASAP.
If this helped you in anyway please take the time to rate this thread.
Happy flashing!
Click to expand...
Click to collapse
hey lucky thirteen ive been having trouble with the step where you have to create a note in the platform-tools file once i save the note and create the shortcut its not like the example that you post it only shows c:\windows\system32\cmd.exe any idea on what i did wrong?? thanks
How to for n00bs:
Beaups Moonshine S-OFF for the Droid DNA
(Note: This guide will assume that you are complete noob with android and linux, BUT that you are not too dense to google basic things and infer basic differences between PC setups)
YOU WILL NEED:
1 Laptop or Desktop with internet access
1 32bit Linux (Ubuntu or Mint preferred, Mint to be used in this guide) liveUSB or liveCD (liveCD preferred, and what will be covered in this guide)
1 Stock Droid DNA with the 2.06 firmware update (2.04 is reported to work, but more success seems to be had with the updated firmware) WITH AT LEAST 80% BATTERY LIFE
1 Factory HTC/Droid micro-usb (Or any cable you know will work with ADB)
{
"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"
}
Prepping your computer:
1: Burn a liveCD of your linux distro of choice. Mint is my choice due to having great out of the box compatibility with hardware.
2: Insert liveCD into your PC, turn it on (or reboot), and enter boot menu (typically esc, f8, or f12 pressed during start up) and select “Boot from CD Drive”.
3: Allow liveCD to boot, it may take some time depending on the speed of your hardware. This is good time to prepare your phone for shining.
Prepping your phone:
1: Update to the 2.06 firmware update, if you have not already. If you cannot OTA, you can find guides to flash said firmware update elsewhere on XDA
a: If you are unsure what firmware you are on, go to “Settings”, “About”, and “Software Information” and it will have your firmware listed.
2: Disable any sort of screen lock. Image lock, facelock, pin lock, doesn't matter, it MUST BE DISABLED FOR THIS TO WORK
3: Disable “Fastboot”. “Settings”, “Battery”, UNCHECK “Fastboot”
4: Enable USB Debugging. “Settings”, “Developer Options”, “USB Debugging”
5: Boot into fastboot (turn off phone, reboot holding down POWER button and VOLUME DOWN button simultaneously). Select “Factory reset”. Allow phone to reset and reboot. Go back into settings, repeat sets 2 and 3 if necessary.
Downloading, unpacking, and excecuting moonshine.
1: On your live linux session, that is connected to the internet, go to www.moonshine.io
2: READ EVERYTHING
3: READ EVERYTHING AGAIN
4: Download the .tgz file relevant to your device (for most of us this will be the Verizon DNA file “moonshine_dlx_2.06.605.1.tgz”
5: Go to the folder your .tgz was just downloaded to. This should be your “downloads directory”
6: Right click anywhere in your download directory and select “Open in Terminal”
7: Extract the moonshine .tgz by typing out the following command into terminal “tar -zxf moonshine_<device>_<version>.tgz” For the Verizon DNA this will be “tar -zxf moonshine_dlx_2.06.605.1.tgz”
Your download directory should look like this when done
(Unfortunately, after this, the iPhone I was using to take pictures died, so there are no more pictures after this, but everything is very straightforward)
At this time plug your phone (which has been factory reset, rebooted, and all things listed in the “phone prep section” have been double checked) into your PC via your HTC/Android USB cable.
8: Execute the “Distiller” by typing the following command into terminal “sudo ./distiller”
9: Agree to the onscreen prompts, sit back, relax, DO NOT F**K WITH YOUR PHONE, and let the shine do its magic. This should take five to fifteen minutes and your phone will reboot several times.
10: Enjoy S-OFF and root.
ALL CREDIT GOES TO BEAUPS AND THE MOONSHINE DEV TEAM, this is simply a shoddy step by step guide by a n00b for n00bs to (hopefully) get more comfortable with the idea. This may be reproduced, altered, or edited in anyway as long as credit is given to me (DWC2134) for the original text and pictures and to the DEVS who brought us this awesome utility. In fact, PLEASE edit, improve, and revise this as you see fit for use by new android and linux users. Any changes suggested in this thread will be taken into account and incorporated into the OP.
Toubleshooting:
1: If you are experiencing the "temproot failed" problem, first try a hard reboot, then a factory reset + hard reboot if the reboot alone does not solve the problem.
2: There is some chatter of questionable validity that VZW is trying to push an update to stop SOFF. If you are having trouble, turn off your radios and/or put your phone in airplane mode while attempting moonshine. While most, myself included, doubt the validity of this claim it is better safe then sorry.
Beaups original moonshine thread
Moderators, if this is in the wrong section, or out of line, etc etc, please move, edit, delete, or do as needed.
Does it have to be the 32 bit version? If so I just have to redo my live usb.
sent from my droid DNA with xda premium
DaPitt84 said:
Does it have to be the 32 bit version? If so I just have to redo my live usb.
sent from my droid DNA with xda premium
Click to expand...
Click to collapse
Yes or the exploit will give an error saying there aren't enough 32 bit libraries. I tried on a 64 bit and got that error. I re did my live cd to use 32 bit ran the exploit and it worked flawlessly.
Sent from my HTC6435LVW using xda premium
Nice howto I did the s-off yesterday worked great. I'm on windows 7 64 bit and installed 32 bit mint.
For people doing this like op said install and use 32 bit just easier and if you're on a 64 bit system doesn't matter 32 bit installs fine.
Sent from my HTC6435LVW using xda premium
Very nice "How To' for us Windows PC peeps dwc2134...thank you.
I have a couple of questions if anyone can answer:
1) I haven't seen any other procedure where "Factory Reset" is called upon. Is there a specific reason?
2) I have a burned image of "Ubuntu-13.04-desktop-i386.iso" on USB Stick that runs v/smoothly on my laptop w/Vista Ultimate, but I can't seem to get to terminal screen. I do however see all of the Moonshine flies in download folder when in Ubuntu and "moonshine_dlx_2.06.605.1.tgz"
Please forgive the noobish Q's
Thx in advance
First of all, thank you dwc2134 for providing this guide! I am very new to this scene (Android rooting) and this guide helps out TREMENDOUSLY since I have no knowledge about terminal/command prompts.
However, after re-reading this guide and the instructions at moonshine.io, I have some questions in my head that are preventing me from going further (If anyone here can answer any of my questions, it would be most appreciated!)
1. At the Instructions page on moonshine.io, Step 8 says "Use the matchingStockRUU..", I have no idea what this, is this something I should worry about? I have not modified my Droid DNA in anyway whatsoever ever since I got the device. I only did the 2 OTA updates (2.04 and 2.06) and that's it.
2. In this guide (dwc2134's) on Step 8 where it says to execute the "Distiller", do I type it into the same terminal window I extracted the Moonshine.tgz file?
3. Once the whole process finishes, and I go back to the fastboot screen to see the glorious text that reads: "S-Off", does this mean my phone is rooted and I can install apps like SetCPU off the bat? Or do I have to flash a custom ROM and if so, can anyone recommend a "tried-and-true" ROM?
Once again, if anyone can answer my queries, it would be very helpful. Thank you in advance!
dfa7 said:
Very nice "How To' for us Windows PC peeps dwc2134...thank you.
I have a couple of questions if anyone can answer:
1) I haven't seen any other procedure where "Factory Reset" is called upon. Is there a specific reason?
2) I have a burned image of "Ubuntu-13.04-desktop-i386.iso" on USB Stick that runs v/smoothly on my laptop w/Vista Ultimate, but I can't seem to get to terminal screen. I do however see all of the Moonshine flies in download folder when in Ubuntu and "moonshine_dlx_2.06.605.1.tgz"
Please forgive the noobish Q's
Thx in advance
Click to expand...
Click to collapse
OK, fingered it out. This may just be of some help to others here. ubuntu-13.04-desktop-i386.iso wouldn't get into "terminal" BUT, linuxmint-15-cinnamon-dvd-32bit.iso does.
Does anyone know if it absolutely necessary to "Factory Reset" DNA with this Mooshine S-OFF method?
dfa7 said:
Very nice "How To' for us Windows PC peeps dwc2134...thank you.
I have a couple of questions if anyone can answer:
1) I haven't seen any other procedure where "Factory Reset" is called upon. Is there a specific reason?
2) I have a burned image of "Ubuntu-13.04-desktop-i386.iso" on USB Stick that runs v/smoothly on my laptop w/Vista Ultimate, but I can't seem to get to terminal screen. I do however see all of the Moonshine flies in download folder when in Ubuntu and "moonshine_dlx_2.06.605.1.tgz"
Please forgive the noobish Q's
Thx in advance
Click to expand...
Click to collapse
1: While not ENTIRELY necessary for a successful moonshining, performing the factory reset and hard reboot seems to solve the "temproot failed" problem several users (myself included) have expierenced.
2: Mint is my go to, so it may be slightly different in ubuntu. You can also open terminal by pressing ctrl-alt-T or by going to your applications menu (or the search in the dash) and searching for "Terminal" and then inputting "cd ~/downloads". This will, for lack of better words, open your download directory in terminal so that the commands you input specifically look for, and effect, the files there. You may have to alter the "~/downloads" portion slightly to get you to the correct directory, but looking at the filepath on your computer it should be pretty obvious.
AndroM31 said:
First of all, thank you dwc2134 for providing this guide! I am very new to this scene (Android rooting) and this guide helps out TREMENDOUSLY since I have no knowledge about terminal/command prompts.
However, after re-reading this guide and the instructions at moonshine.io, I have some questions in my head that are preventing me from going further (If anyone here can answer any of my questions, it would be most appreciated!)
1. At the Instructions page on moonshine.io, Step 8 says "Use the matchingStockRUU..", I have no idea what this, is this something I should worry about? I have not modified my Droid DNA in anyway whatsoever ever since I got the device. I only did the 2 OTA updates (2.04 and 2.06) and that's it.
2. In this guide (dwc2134's) on Step 8 where it says to execute the "Distiller", do I type it into the same terminal window I extracted the Moonshine.tgz file?
3. Once the whole process finishes, and I go back to the fastboot screen to see the glorious text that reads: "S-Off", does this mean my phone is rooted and I can install apps like SetCPU off the bat? Or do I have to flash a custom ROM and if so, can anyone recommend a "tried-and-true" ROM?
Once again, if anyone can answer my queries, it would be very helpful. Thank you in advance!
Click to expand...
Click to collapse
1: If you have not modified your phone in anyway, and have received the OTAs, then that is irrelevant to you.
2: Yes. Or in another terminal window opened in your "downloads" directory, though opening a second window seems kind of pointless.
3: Moonshine installs superuser to your device, so YES YOU CAN install custom apps like SetCPU right off the bat. I would recommend first installing a custom recovery (I am using CWMs new touch version) and making a nandroid backup before doing anything else, personally. I would also highly recommend installing a custom rom instead of putting in too much time with the stock sense rom. There are so many fantastic roms out for this phone, it would almost be a waste not to. A lot of folks swear by the ViperROM. I'm currently using it and love it.
dwc2134 said:
1: While not ENTIRELY necessary for a successful moonshining, performing the factory reset and hard reboot seems to solve the "temproot failed" problem several users (myself included) have expierenced.
2: Mint is my go to, so it may be slightly different in ubuntu. You can also open terminal by pressing ctrl-alt-T or by going to your applications menu (or the search in the dash) and searching for "Terminal" and then inputting "cd ~/downloads". This will, for lack of better words, open your download directory in terminal so that the commands you input specifically look for, and effect, the files there. You may have to alter the "~/downloads" portion slightly to get you to the correct directory, but looking at the filepath on your computer it should be pretty obvious
Click to expand...
Click to collapse
Thanks for clarrification. I decided to Mint and all is perfect! Ubuntu was a challenge considering I'm not an Apple guy and Linux is greek to me. As for the "Factory Reset", I'll gamble only 'cause I'm configured to my liking and not in mood yet to spend a day getting everything back. Thx again!
All's well that ends well. If you end up having the temp root problem, try a hard reboot first and then a factory reset.
Sent from my HTC6435LVW using xda app-developers app
dwc2134 said:
1: If you have not modified your phone in anyway, and have received the OTAs, then that is irrelevant to you.
2: Yes. Or in another terminal window opened in your "downloads" directory, though opening a second window seems kind of pointless.
3: Moonshine installs superuser to your device, so YES YOU CAN install custom apps like SetCPU right off the bat. I would recommend first installing a custom recovery (I am using CWMs new touch version) and making a nandroid backup before doing anything else, personally. I would also highly recommend installing a custom rom instead of putting in too much time with the stock sense rom. There are so many fantastic roms out for this phone, it would almost be a waste not to. A lot of folks swear by the ViperROM. I'm currently using it and love it.
Click to expand...
Click to collapse
Thank you so much for clearing away my doubts! Once I get the "S-Off" message, I'll look into your suggestions mentioned here.
dwc2134 said:
All's well that ends well. If you end up having the temp root problem, try a hard reboot first and then a factory reset.
Click to expand...
Click to collapse
dwc2134 - thanks for your help, patience and interset with some of us and this project! It does seem easier than revone.
Where do I find the Linux file to put on usb? I don't have any blank cd's either...will it work from usb stick?
HellRayzer said:
Where do I find the Linux file to put on usb? I don't have any blank cd's either...will it work from usb stick?
Click to expand...
Click to collapse
You can find the .iso image for any distro you want online. I prefer Linux Mint, though Ubuntu is another crowd favorite. You can make a bootable USB, but I find it easier to make and use liveCD/DVDs. A pack of burnable DVDs is $2.89 at CVS. Google is your friend for the rest of this, it is all VERY self explanatory and most distro sites put step by step instructions right on their website.
http://www.linuxmint.com/download.php
http://www.linuxmint.com/documentation/user-guide/english_15.0.pdf
Error When Trying To Download - 'This file reached max downloads limit"
Followed the guide...booted from USB Ubuntu. No problems. Connected to moonshine.io, clicked next, next, but when I selected the DNA version, I get the error:
"This file reached max downloads limit"
...and no download.
Any ideas? I see another person has posted this in the developers section. Is there a link problem?
Thanks.
dwc2134 said:
You can find the .iso image for any distro you want online. I prefer Linux Mint, though Ubuntu is another crowd favorite. You can make a bootable USB, but I find it easier to make and use liveCD/DVDs. A pack of burnable DVDs is $2.89 at CVS. Google is your friend for the rest of this, it is all VERY self explanatory and most distro sites put step by step instructions right on their website.
http://www.linuxmint.com/download.php
http://www.linuxmint.com/documentation/user-guide/english_15.0.pdf
Click to expand...
Click to collapse
This is spot on. I did my first live cd related to rescuing crucial data on a government computer with a corrupt OS a few weeks ago. I googled "How to make a bootable live cd USB drive" and literally in five minutes I was booted into my Ubuntu distro.
One thing I did learn is with Ubuntu there's a lot of alternative distros on their main site with all the links. After not having the option to boot without making any changes I went to my google-found guide again and realized only ubuntu distros with "desktop" in the filename would give me the live boot option I needed for the task at hand.
One of those small details I overlooked, that was solved by a quick recheck with google.
EXCELLENT GUIDE, I'm really impressed.
Max download limit reached.
I am having the same issue it says that the maxium download limit has been reached.:crying:
I can't donate if I can't download!
FUBAR'd
UntamedDarkness said:
I am having the same issue it says that the maxium download limit has been reached.:crying:
I can't donate if I can't download!
Click to expand...
Click to collapse
Link looks to be FUBAR'd. Maybe Verizon got pizzzed and did a bit of hacking themselves...
Several people now reporting the issues in multiple threads. I just rechecked...same error.
Out of curiosity, are you using Verizon Mobile Hotspot on your phone to connect to the internet via computer? I am.
CharliesTheMan said:
This is spot on. I did my first live cd related to rescuing crucial data on a government computer with a corrupt OS a few weeks ago. I googled "How to make a bootable live cd USB drive" and literally in five minutes I was booted into my Ubuntu distro.
One thing I did learn is with Ubuntu there's a lot of alternative distros on their main site with all the links. After not having the option to boot without making any changes I went to my google-found guide again and realized only ubuntu distros with "desktop" in the filename would give me the live boot option I needed for the task at hand.
One of those small details I overlooked, that was solved by a quick recheck with google.
EXCELLENT GUIDE, I'm really impressed.
Click to expand...
Click to collapse
Yep, google has most any answer you could ever need if you search enough. The only reason I promote liveCDs over liveUSBs is that I think they are a touch easier to make and use. For some reason I have always had a hard time getting liveUSBs to work.
Thank you! I'm really glad it seems to have helped some folks out!
UntamedDarkness said:
I am having the same issue it says that the maxium download limit has been reached.:crying:
I can't donate if I can't download!
Click to expand...
Click to collapse
ejohanss said:
Link looks to be FUBAR'd. Maybe Verizon got pizzzed and did a bit of hacking themselves...
Several people now reporting the issues in multiple threads. I just rechecked...same error.
Out of curiosity, are you using Verizon Mobile Hotspot on your phone to connect to the internet via computer? I am.
Click to expand...
Click to collapse
I doubt it is Verizon, most likely a bandwidth issue or hosting service issue. Seems to be common with everyone trying to download moonshine right now. Sounds like there is trouble with the download limit counter. I knew I should have kept a backup copy of the .tgz
No, when I tether I use one of the free solutions. I got bumped off of unlimited, so I tend to use more wifi then phone data. You NEED an internet connection that is not reliant on your phone for this to work. Moonshine actively connects to the internet during the ./distiller program.
dwc2134 said:
Yep, google has most any answer you could ever need if you search enough. The only reason I promote liveCDs over liveUSBs is that I think they are a touch easier to make and use. For some reason I have always had a hard time getting liveUSBs to work.
Thank you! I'm really glad it seems to have helped some folks out!
I doubt it is Verizon, most likely a bandwidth issue or hosting service issue. Seems to be common with everyone trying to download moonshine right now. Hopefully beaups will be able to set up some new downloads or someone else will be willing to host the files for him. I knew I should have kept a backup copy of the .tgz
No, when I tether I use one of the free solutions. I got bumped off of unlimited, so I tend to use more wifi then phone data. You NEED an internet connection that is not reliant on your phone for this to work. Moonshine actively connects to the internet during the ./distiller program.
Click to expand...
Click to collapse
I just checked it's a host download limit it's ABSOLUTELY not related to verizon.