Hello Everybody!
Here is just a simple little script that roots your Flyer. You need an exploit address, so they are listed down below. You should also make sure you have the HTC Sync Drivers for the Flyer/View Download Also, there is now a Perma-Root method, which root access doesn't expire, so it is definitely better than mine. Since there is one now, I won't develop any more releases of the script, unless it is utilizing the new method, but they already have a script.
Exploit Addresses:
HTC EVO View 4G: Use the EVO View root.bat, it is automatic. Sorry Flyer users, there are too many exploits that work and don't work. If you want, you could try using the EVO View Root.bat with a Flyer. If it works, tell me!
HTC Flyer WiFi 16GB: exploit at adress 38126600:a00 or 38125600:1a00 (this works with mine.)
HTC Flyer 3G 32GB: exploit at address 38125e00:1200
Your root may expire, so please run Superuser.bat every time. Sorry for the trouble, I might make one that will run directly on your device that runs every ten minutes or whatever. Also remember this is only a temp root, so you will have to run the rooting script every time you reboot.
Also, a script that you don't have to enter an exploit address is in development.
Thanks,
pndo1
PS - A Mac version is in development.
Credits:
agrabren and teamwin for fre3vo
Elim for the exploit addresses
dalada for his root script (which I modified) and his superuser, su and busy box binaries.
And finally, all of XDA for being the best mobile device forum I have ever seen.
thank you very much but i think you forgot the attachment
Updates
Updates:
0.2 Added support for the Sprint EVO View
0.1 Released.
i can confirm that is it working on my htc flyer 3g thanks alot
Thanks for getting the scripts. Let us know when you get the one for the View.
pndo1,
thanks, really easy.
New we can hope for a root that sticks.
There is one that roots the EVO View!
pndo1 said:
Hello Everybody!
Hi pndo1,
Sorry, I not very familar with rooting, can you help explain further on this script? Can you help confirm my below understanding.
1) Connet Flyer to PC with sync connect
2) run the Flyer root bat file and enter the code
Question: Do i have to install the adb and adb shell sw in PC prior running this script?
Click to expand...
Click to collapse
Will you please help me understand what I do wrong. I run the script from the Windows folder. Successfully get to the point where I should enter the address. Do that. Then once I was successfull in getting to the "exploiting device" step and further. But that resulted in no actual root. Then I tried again after a reboot. But now it only gets to the address stage and no further. I connect in the charge only mode. USB debugging on. What did I do wrong?
@yongck7
No, connect the Flyer/View in Charge Only mode, with debugging enabled, and then run the root script for your device (Flyer or View).
@romanas2007
You can try and try again, as it appears you are not rooted. If it says exploiting, and there is no superuser, than run Superuser.bat
I ran the root script again from a freshly unzipped folder and it went ok. But when the script is trying to install the SU, I get the error messages all the time, like this:
Unable to chmod /data/local/tmp/busybox: no such file or directory
Unable to chmod /system/bin/su: no such file or directory
What can be wrong? Sorry, for noob questions.
Your Flyer/View is most likely one that has trouble mounting /system. Some guys were reporting it in the general section. You could try going into a command prompt, and type in cd, and a space, and drag the folder with the root files in it into the window, and press enter. Then type adb shell. If there is a # sign, you are ok. Try typing in "mount -o re,remount /dev/block/mmcblk0p5" without the quotes, and see what it says. But, if there is a $ sign, rerun the rooting script after a reboot, it can only be run once or twice, if you run it too many times, /system can't mount as write properly. Oh, and if the output from the mount command says "mount -o re,remount /dev/block/mmcblk0p5" then it mounted properly and you can run superuser.bat. If it says "mount: filesystem read only" or "mount: filesystem r/o" then reboot and run root.bat again.
Sorry for the long instructions, the script is kind of fussy as of now.
thank you. working very well.
pndo1 said:
@yongck7
No, connect the Flyer/View in Charge Only mode, with debugging enabled, and then run the root script for your device (Flyer or View).
@romanas2007
You can try and try again, as it appears you are not rooted. If it says exploiting, and there is no superuser, than run Superuser.bat
Click to expand...
Click to collapse
Dear
pndo1
I tried to execute the flyer root.bat I got a message "Device not found"
My device is flyer 32G 3G
connected in charge only and debugging enabled
any help
You may have to install the drivers for the flyer, aka HTC Sync, which is on the HTC website. Google is your friend. Also you do not have to sync or even open HTC Sync once installed. I will update the OP.
Doesn't work properly with my 32 gb flyer ...
Installs SU but when opening SU i get a FC
.. Also any apps that require SU fail
Kris
i00 said:
Doesn't work properly with my 32 gb flyer ...
Installs SU but when opening SU i get a FC
.. Also any apps that require SU fail
Kris
Click to expand...
Click to collapse
Works well here on 32GB Flyer.
When running the code, I let the Flyer connect in sync, rather than charge only. No problem whatsoever.
You should try running superuser.bat again. Thats what I had to do, sometimes it doesn't copy and have the right permissions. Also in development is a version with no user input, if it is a good day it should be released tomorrow.
Works with my 32 3G Flyer
update: Noob question - I tried to perform run superuser.bat but no idea how :-(
You should just be able to double click.
Related
Hello everyone!
You may or may not know me, however I have secretly been working behind the scenes with ChiefzReloaded to learn how Android works. Together we have been trying to develop new ways to root the Slide, primarily because we both landed in a sticky situation that left us both without root and without a way to revert to root.
After many long hours of trying to restore my phone, I have now ported the exploid exploit to the MyTouch Slide! This means that you can gain root on any version of the Slide, INCLUDING the latest OTA! However, this isn't necessarily "easy" as in the One-Click Root program, but there are reasons for this. While Android is running we cannot write to /system and even if we force Linux to let us, the NAND protection will prevent Linux from completing the write!
To get started, please see the bottom of this post for the link and download it. You will want to download it to your computer and not your phone's SD card. Also, you will need the tools from the Android SDK. I would suggest extracting the file from my zip at the bottom of this page into the Android SDK's tools directory.
Extract the zip
Make sure your phone is in USB debugging mode AND you are in "Charge Only" mode.
Connect your phone to your computer.
Make sure you're in the same directory as where exploid is extracted before continuing to the next step.
Issue the following command: adb push exploid /sqlite_stmt_journals. Note: It MUST be in that directory - NO exceptions.
Run: adb shell
Run: cd /sqlite_stmt_journals
Run: chmod 0755 exploid
Run: ./exploid
Toggle your phone's Wifi (on or off, however you wish to do that).
Now (again) run: ./exploid (if prompted for a password enter: secretlol)
The next line should now begin with a pound (#) - if not, then something isn't setup right. Make sure to follow the directions verbatim. If you suspect you did follow them correctly, please reply to this post letting me know.
You should now be root! At this point you can do many things, but if you're looking to flash a custom ROM, continue to these instructions:
[NEW 10/18/2010:]
Steps 1-12 are intended to get you the ability to flash mtd0.img (which previously required using the SimpleRoot method) by gaining root inside of Android. By following the instructions in the rest of this section, it will allow you to flash a ROM or S-OFF your device:
The files you need are at: http://forum.xda-developers.com/showthread.php?t=703076- download both files linked in there (ESPRIMG.zip and SlideEng-package.zip)
Extract the contents of SlideEng-package.zip to a place of your choosing on your computer.
Place the entire (unextracted) ESPRIMG.zip on your SDcard.
Now push the files 'flash_image' and 'mtd0.img' that you just extracted from SlideEng-package.zip to /data/local using 'adb push'. (Noob? Instead of using 'adb push', install Droid Explorer and, using that utility, copy the 'flash_image' and 'mtd0.img' files to /data/local on your Slide)
Now I'm going to assume your phone is at root prompt (#) using steps 1-12. So now do (without typing the '#' symbols in front of both lines - they're just there to remind you that you need to be at a '#' prompt):
Code:
# cd /data/local
# chmod 04755 flash_image
# ./flash_image misc mtd0.img
Before you reboot make sure that the ESPRIMG.zip is on your SDcard!
Now turn off the phone.
Then press Volume-Down + Power.
The phone will power on and after about 5 minutes of verifying ESPRIMG.zip it will ask you if you want to flash it.
Press Volume-Up for 'YES' and wait until it finishes (ABSOLUTELY DO NOT POWER DOWN WHILE IT'S STILL FLASHING!!!).
Now when you go into recovery it should allow you to 'Apply update.zip from sdcard' (booting into Clockwork). If you don't have the Clockwork update.zip, here it is: http://www.4shared.com/file/OTRU7T3y/update_2.html (rename to update.zip after downloading since it's currently update_2.zip, then place it on your sdcard).
[/NEW 10/18/2010]
[NEW 12/30/2010]
Optional: Now that you're rooted you might want to disable all flash memory protections so you can permanently flash Clockworkmod (recovery - no more using an update.zip!) as well as other random things. Check here for details: http://forum.xda-developers.com/showthread.php?t=798168
[/NEW 12/30/2010]
CREDIT GOES TO:
[*] ChiefzReloaded! (For helping me learn the intricacies of Android and patiently answering all of my questions)
[*] 743C (For developing the original exploit)
Source code: (Yes, it's hackish. I was just trying to figure out why the system kept rebooting and haven't cleaned up the code since) download
DOWNLOAD:
http://www.4shared.com/file/CZsxSq-f/exploid.html
DONATE:
(Anything helps!)
(Some people may wonder why this is special compared to the One Click Root application. What's important is that One Click Root doesn't work on Slides running production/retail software, likely the same problem I had to fix to get exploid to work in my version.)
Thats whats up!!
If you be trollin then YOU BES TRAWLLIN
But if not then good job nb!
Sent from my T-Mobile myTouch 3G Slide using XDA App
Can you provide the source? No offense, but I tend not to run homebrew C programs that I didn't compile myself.
Thanks for all the work!
falken98 said:
Can you provide the source? No offense, but I tend not to run homebrew C programs that I didn't compile myself.
Thanks for all the work!
Click to expand...
Click to collapse
Sure, I was getting around to that - and I understand your concern. I'll post it in a second.
falken98 said:
Can you provide the source? No offense, but I tend not to run homebrew C programs that I didn't compile myself.
Thanks for all the work!
Click to expand...
Click to collapse
You think nb is distributing a virus disguised as a root method?
Waaaaaat
Sent from my T-Mobile myTouch 3G Slide using XDA App
r0man said:
You think nb is distributing a virus disguised as a root method?
Waaaaaat
Click to expand...
Click to collapse
It is a bit funny, but I do understand his concern. I've posted the source code into the original post. Compiling it should result in the same hash as the binary I posted.
Good to see this I suggested this in another thread glad to see it in use thanks a bunch
nbetcher said:
It is a bit funny, but I do understand his concern. I've posted the source code into the original post. Compiling it should result in the same hash as the binary I posted.
Click to expand...
Click to collapse
Ill take a look at it when I get home.
ilostchild said:
Good to see this I suggested this in another thread glad to see it in use thanks a bunch
Click to expand...
Click to collapse
I actually had to do a lot of work on it. It doesn't quite work the same as the original exploid simply because the original exploid crashes the entire system and reboots. This causes the rootshell to never be committed to NAND and thus you get no where. I had to keep playing with things until I found a different method that works. It took several hours of me being upset with it, but watched the latest Burn Notice, came back to it, and BAM I had a stroke of genius.
where is rootshell? i can't exicute rootshell nor can i "cp" any files from sdcard however i do have a # instead of a $
Armyjon88 said:
where is rootshell? i can't exicute rootshell nor can i "cp" any files from sdcard however i do have a # instead of a $
Click to expand...
Click to collapse
Ignore that portion of the instructions provided by the program. As I stated, this is not intended for non-developers at this point. The # is your indication that you're running as root.
I am headed to work, but I don't usually have much going on there - I will be setting up a much cleaner system/environment for non-developers to work with and perma-root their phones with over the next few hours. Stay tuned!
Sweet
Sent from my T-Mobile myTouch 3G Slide using XDA App
having # and running as root as stated before u can actually follow with eng and then custom recovery and ur choice's rom..pls correct me if im wrong..thanx
statuzz said:
having # and running as root as stated before u can actually follow with eng and then custom recovery and ur choice's rom..pls correct me if im wrong..thanx
Click to expand...
Click to collapse
i'm also wondering the same thing, because i got the exploid working, and i have the # in the shell, but when i go to follow the instructions to flash the eng-release, i can't cd to any different dirs, nor can i push any files to the phone. i have the ESPRIMG.zip copied to my sdcard, so could i just reboot into recovery and flash the nbh from there? any help is appreciated.
nbetcher said:
Ignore that portion of the instructions provided by the program. As I stated, this is not intended for non-developers at this point. The # is your indication that you're running as root.
I am headed to work, but I don't usually have much going on there - I will be setting up a much cleaner system/environment for non-developers to work with and perma-root their phones with over the next few hours. Stay tuned!
Click to expand...
Click to collapse
Let me know if you want to work together on some kind of one-click root app for the Slide. If the commands work through the terminal on the phone itself rather than via adb, I could probably make this into an app already, but since you're working on a more non-developer-friendly version, I'll just wait until that's out
televate said:
i'm also wondering the same thing, because i got the exploid working, and i have the # in the shell, but when i go to follow the instructions to flash the eng-release, i can't cd to any different dirs, nor can i push any files to the phone. i have the ESPRIMG.zip copied to my sdcard, so could i just reboot into recovery and flash the nbh from there? any help is appreciated.
Click to expand...
Click to collapse
I'm delaying the release of my non-developer program for another couple hours.
As far as what you said above, all you need to do after gaining the # prompt is (in a separate window):
adb push flash_image /data/local
adb push mtd0.img /data/local
(switch back to your # adb shell, then type
cd /data/local
chmod 04755 flash_image
./flash_image misc mtd0.img
Then reboot and apply the ESPRIMG.zip. All of these files are found on the same post that I referenced in my OP. These instructions are all in that same page.
televate said:
i'm also wondering the same thing, because i got the exploid working, and i have the # in the shell, but when i go to follow the instructions to flash the eng-release, i can't cd to any different dirs, nor can i push any files to the phone. i have the ESPRIMG.zip copied to my sdcard, so could i just reboot into recovery and flash the nbh from there? any help is appreciated.
Click to expand...
Click to collapse
Im also stuck since im not sure if you can update to eng from the ota..But first i want to personally thank the OP & CR for providing this.
This would be great for a One Click method
this would be nice to work into a one click root!
And This did work for me!
Does this root method gets /system moumted when android running?In short do we finaly get metamorph and root explorer working?
When will it arrive?for 101 i mean
It won't happen until we get permanant root. No telling when that will happen.
a better question is, when will root be available, doesn't seem we have people with the right skills interested on the 101
Does the rageagainstthemachine root patch not work? Are you able to get to the /data/local directory and place something there that will allow for a flash_image command to be run? Do we know if they have the same type of hardware-level protection like HTC does?
EDIT: Can someone do the following:
1. download the rage zip enclosed, and unzip to it's own directory
2. run the following from your command prompt, assuming you have the Android SDK installed and in the path
adb push root/rageagainstthecage /data/local/tmp
adb shell
chmod 0755 /data/local/tmp/rageagainstthecage
./data/local/tmp/rageagainstthecage
Click to expand...
Click to collapse
It should kick you out and display some messages on the screen...just not errors. Then type:
adb shell
Click to expand...
Click to collapse
You Should see a "#".
If so, then we have temp root and then we should be able to perform some other functions like flash a recovery, etc....
Sent with my fingertips and voice on my Evo
jerdog said:
Does the rageagainstthemachine root patch not work? Are you able to get to the /data/local directory and place something there that will allow for a flash_image command to be run? Do we know if they have the same type of hardware-level protection like HTC does?
EDIT: Can someone do the following:
1. download the rage zip enclosed, and unzip to it's own directory
2. run the following from your command prompt, assuming you have the Android SDK installed and in the path
It should kick you out and display some messages on the screen...just not errors. Then type:
You Should see a "#".
If so, then we have temp root and then we should be able to perform some other functions like flash a recovery, etc....
Sent with my fingertips and voice on my Evo
Click to expand...
Click to collapse
It does not work as of the latest Archos firmware. All the previous firmwares/z4root work fine for temp root. The ADB device part of the Archos just never comes back (doesn't show in device manager for instance). I do not know if this helps, but Archos also has a crippled busybox and it seems furthered crippled as of the last firmware upgrade.
Tsusai said:
It does not work as of the latest Archos firmware. All the previous firmwares/z4root work fine for temp root. The ADB device part of the Archos just never comes back (doesn't show in device manager for instance). I do not know if this helps, but Archos also has a crippled busybox and it seems furthered crippled as of the last firmware upgrade.
Click to expand...
Click to collapse
Maybe have something to do with newer ARM architecture?
Sent with my fingertips and voice on my Evo
Why do you need permanent root?
Archos kindly released SDE which provides a way to install your own builds in dual boot.
Some links for more info:
http://forum.xda-developers.com/showthread.php?t=871335
http://www.openaos.org/
IRC #openaos on freenode
Maurice
The SDE require booting in recovery mode, and people said that it's often not perfect.
A permanent root for main OS would still be very useful, and still allow us to dual boot when we need to..
I think so too. PermaRoot would be very usefull.
Hey all,
I would just like to say I am new to this whole thing, and HAVE searched the forums, and found this link to be most helpful:
http://forum.xda-developers.com/showpost.php?p=12029729&postcount=12
I am merely trying to install the new swype beta, I am currently trying to uninstall my current version of swype, now I have done the majority of the steps the only thing I am having trouble doing is giving the phone read/write access
as when I try: mkdir /mnt/sdcard/swype_backup I get an error because it's a read-only file system.
I am using ADB; the first line of the post I linked to says to enable R/W access if you're using Root Explorer... but I am not, so how can I accomplish this through adb?
Am I missing something glaringly obvious?
Thanks for your time and patience
Edit: I believe adb is working to the extent it should... after I type in adb shell I do infact get a '#' before each line.
It's all fixed, re-did gladroot and now everything worked perfectly, not sure exactly why it wasn't before
thanks anyways!
Important Update on Dec 2, 2011: Please do not update to Vizio Update 1.5. This will remove the root as well as disable this hack. According to user felixand in this Post.
I decided to start a new thread.
For those who would like to root, please see the instructions in the first post of this thread. This works for me.
http://forum.xda-developers.com/showthread.php?p=18805532
### Please use V3 version: DooMLoRD_v3_ROOT-zergRush-busybox-su.zip ###
Edited to add: If the above DooMLoRD method does not work you can use SuperOneClick. SuperOneClick can be found here: SuperOneClick. Download it and expand it. You will also need to download DooMLoRD_v3_ROOT-zergRush-busybox-su.zip. Expand it as well. Copy the new zergRush binary from the files directory of DooMLord into the exploits directory of the SuperOneClick folder. Then run SuperOneClick to root. Thanks to those who tried this method. See post by marvin02 below.
ACKNOWLEDGEMENTS:
I am not the original developer. I just helped test it. Please thank the developer of zergRush who fixed this code on the Vizio. Post by Ch4lky here.
http://forum.xda-developers.com/showthread.php?p=19396835
For those interested in the original source code of this exploit it is here.
Source code: https://github.com/revolutionary/zergRush
Binary: https://github.com/revolutionary/zergRush/downloads
Edited: Info about Vizio update 1.5 on Dec 2, 2011.
so to read into what you are posting - we need to follow directions and use the http://forum.xda-developers.com/attachment.php?attachmentid=784296&stc=1&d=1321435888
which is "DooMLoRD_v3_ROOT-zergRush-busybox-su.zip"
again, I am at work and can't download, but does above file contain the additional files called out in the script - namely busybox, su, and superuser.apk - if I were to guess from the filename, I would say yes...
to sum up:
place the 4 fileset(s) into a common directory under your adb setup - for consistency - we'll call this "files"
so we end up with
./files/zergRush
./files/busybox
./files/su
./files/Superuser.apk
is this about right?
Rich
Yes, that is correct.
okay - so the next step is the rewriting of the vold.fstab file to properly map the internal mount point and the external microSDHD card.
I remember seeing something on the Pandigital Novel forums that had suggestions on this topic...
Any ideas as to what the Vizio needs?
1) first so as not to break the current OS settings
2) then, to remap the mount point as needed so that software like APP2SD will behave correctly.
(looking forward to getting home tonight)
Rich
Wow, I was about ready to get rid of this thing. Will be giving this a go today and seeing about some dev support for roms and what not.
Kudos!
For me the doomlord script stuck waiting for the device.
I put the zergrush exploit into the exploits folder of SOC 2.2 (replace the one that is there) and it worked liked a charm.
Edit: SD Card mount point mod
If you are having issues rooting here is some troubleshooting:
To test your connection with adb:
After installing the drivers open a command prompt in the folder where the adb.exe is located at, make sure USB debugging is on and connect your VTAB to your computer.
Now type "adb devices" without the quotes and you should see:
D:\Android\tools>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
Your serial number here device
If this does not work then adb is not connecting to your VTAB.
For me the version of adb that is packaged with the doom script does not connect, but the version packaged with SOC 2.2 does. I copied the zergRush exploit from doom's script to the exploit folder on SOC 2.2 and used SOC. I am on WinXP Pro.
If you are using 64 bit windows make sure you install the drivers as an admin and run the doom script or SOC 2.2 as an admin.
Now...
Who feels like making a custom recovery?
I guess I'll start on CWM porting...
Maybe now that it has root, XDA should create a subforum for it?
blackcog said:
Who feels like making a custom recovery?
I guess I'll start on CWM porting...
Click to expand...
Click to collapse
This is great. Please post your progress. That will be very helpful.
majorpay said:
Maybe now that it has root, XDA should create a subforum for it?
Click to expand...
Click to collapse
We have to request it here.
http://forum.xda-developers.com/showthread.php?t=1301121
rprr said:
This is great. Please post your progress. That will be very helpful.
Click to expand...
Click to collapse
As embarrassing as it is, I'm actually having a terrible time getting a proper dump of the boot img. It seems to be corrupt every time I pull it
Once I get that much, the rest is a breeze. Probably 20 minutes, tops.
blackcog said:
As embarrassing as it is, I'm actually having a terrible time getting a proper dump of the boot img. It seems to be corrupt every time I pull it
Once I get that much, the rest is a breeze. Probably 20 minutes, tops.
Click to expand...
Click to collapse
May I ask how you are trying to dump the boot img?
Hey rprr, I just wanted to say I love you and offer you any females in my family for inpregnation.
sigeltek said:
Hey rprr, I just wanted to say I love you and offer you any females in my family for inpregnation.
Click to expand...
Click to collapse
Thanks, I showed that to my DW and she burst out laughing But, the real credit should go to the devs of zergRush and Ch4lky in particular. Please see my OP for the link to Ch4lky's post if you wish to "Thank" his post.
Same problem here.
The doomlord rooting kit did not work for me either. However, the superoneclick 2.2 with zergrush exploit copied into the exploit folder did work.
---------- Post added at 09:13 PM ---------- Previous post was at 08:52 PM ----------
Do get my device rooted runnning ADB under Vista (32-bit) I did the following:
1) First the Vizio provided ADB driver would not install. I instead did the following.
2) After making sure that any previous drivers were uninstalled from Device Manager including the Android Composite ADB driver. This driver would install for my VTAB successully but I was unable to communicate to the tablet using ADB. I deleted this driver and clicked on "delete the driver software". I also deleted the USB mass storage device and USB composit device.
3) I did a clean boot of the VTAB and then enabled the USB debugging.
4) I connected the VTAB to the USB port and this enabled "installing new hardware"
5) On my machine, I allowed it to search for the device driver and the key was to ensure that it would fail and close.
6) Go into control panel, device manager and you should now have other device named VTAB1008 with yellow highlight.
7) Right mouse click and select "update driver software"
8) then select "browse my computer for driver software"
9) then select "let me pick from a list of device drivers"
10) Select "ADB interface" and then select "Android Sooner ADB testing interface".
11) Once this driver was installed, I was successful in seeing the VTAB through ADB.
12) Install SuperOneClick version 2.2
13) Download the doomlord V3 toolkit and copy the zergrush file under the /files directory to the exploit directory under SuperOneClick (replacing the existing zergrush file)
14) Once this was done, SuperOneClick was successful
rprr said:
May I ask how you are trying to dump the boot img?
Click to expand...
Click to collapse
Actually, after several hours and a chat with a vizio tech, I've finally been able to diagnose it as a hardware malfunction.
On that note, my vtab has died. This is number two. I don't think I'll invest in a third. Sorry, guys.
blackcog said:
As embarrassing as it is, I'm actually having a terrible time getting a proper dump of the boot img. It seems to be corrupt every time I pull it
Once I get that much, the rest is a breeze. Probably 20 minutes, tops.
Click to expand...
Click to collapse
I do not now how to do what you are doing, but I found this guide. Don't know if it is helpful.
blackcog said:
Actually, after several hours and a chat with a vizio tech, I've finally been able to diagnose it as a hardware malfunction.
On that note, my vtab has died. This is number two. I don't think I'll invest in a third. Sorry, guys.
Click to expand...
Click to collapse
Sorry about your VTAB. May I ask again how you were trying to extract the boot.img?
marvin02 said:
I do not now how to do what you are doing, but I found this guide. Don't know if it is helpful.
Click to expand...
Click to collapse
Thanks. I did try that but still cannot get to the boot.img.
hey everyone long story short i rooted my tablet a while back and started having problems so i flashed a new rom and the wifi isnt working.
I went to androidfiles.org and clicked nabi 2 and download wifi-fix, ota update and stock zip rom and flashed those three zip files ( i compressed them) in twrp.. its booting up and everything but wifi isnt working. ive read a lot of peeps are having wifi probs. I have a xda link for my exact device and you guys tell me wut the hell im supposed to do. its got all kinds of stock roms and ota updats and stuff,... which one do i use wtf do i do. should i go one at a time from lowest to biggest, do i even need ota updates or w./e that is?!?!?!? please help guys my chirstmas is becoming a nightmare... its my only internet source.. i had to come all the way to the dang library for this crap.. please help!!!!! heres the link that might give u guys an idea on how to help.. heres the stock roms and stuff
http://forum.xda-developers.com/wiki/Fuhu_nabi_2 thank you!!!!!
duuude im baked said:
hey everyone long story short i rooted my tablet a while back and started having problems so i flashed a new rom and the wifi isnt working.
I went to androidfiles.org and clicked nabi 2 and download wifi-fix, ota update and stock zip rom and flashed those three zip files ( i compressed them) in twrp.. its booting up and everything but wifi isnt working. ive read a lot of peeps are having wifi probs. I have a xda link for my exact device and you guys tell me wut the hell im supposed to do. its got all kinds of stock roms and ota updats and stuff,... which one do i use wtf do i do. should i go one at a time from lowest to biggest, do i even need ota updates or w./e that is?!?!?!? please help guys my chirstmas is becoming a nightmare... its my only internet source.. i had to come all the way to the dang library for this crap.. please help!!!!! heres the link that might give u guys an idea on how to help.. heres the stock roms and stuff
http://forum.xda-developers.com/wiki/Fuhu_nabi_2 thank you!!!!!
Click to expand...
Click to collapse
Thought I would share some info I found when I ran into the wifi problem on my daughter's nabi. I did some searches on the internet and the typical answer I found for solving the wifi issue was "reset the device" or "unroot and return to stock rom - flash all updates and reroot". Being a glutton for punishment, and the fact I didn't want to reset the device, I searched and searched and was able to fix my daughter's wifi without doing a reset or unroot/reroot. Before I get into it I wanted to mention that wifi failures can happen for a number of reasons so while this worked for myself, it may not work for you.
Some prerequisites:
Most importantly; you need a rooted device. If you do not have root access you will not be able to write files or access the commands to fix the issue I am about to outline.
Some knowledge of linux would be helpful, but not necessarily required.
Lets get started:
Warning! It goes without saying but I will say it anyways - you can mess up your nabi by rooting it. Some of the commands below could mess up your nabi bad. If this scares you then you probably should not proceed any further. I am not responsible for any damage you do to your nabi.
Commands are listed between ' and ' - do not use the ' when inputing the commands.
Note: The first two/three steps are not necessary but they do give you insight as to how I was able to determine my problem. If following this doesn't fix the problem for you the logcat output may give you some important info that you can google that may help you fix your particular problem.
Note: Steps 5 and on can be skipped if you have a text editor (vi or nano) on your device. If you have a text editor loaded simply edit the conf file directly.
1. You will need to run the command 'adb logcat' in a command-line window and in your appropriate directory. Adb is available as part of the android sdk but can also be found stand alone since most people do not need the sdk.
2. Try to turn on the wifi. You should see the output of your adb logcat window scroll some data. If the wifi is not attempting to turn on at all sometimes you can move between the settings options then go back to the wifi settings and move the slider. If you cannot get your wifi to turn on you can scroll the window up and attmept to find the data from when the device started up. In the output you should see lines that talk about wlan0 and probably something that says "failed" somewhere. In my case I could see where the wlan0 enabled but then a few lines down it said something about "Line: 25 failed" and "failed to parse file".
3. The file is actually a configuration file used by the wifi kernal module/driver. In my case this file had become corrupted.
4. Set adb in root mode (won't work if the device does not have root access) by running 'adb root' at the command-line. You may need to click on an "allow root permission" window on the actual device after running this command.
5. Run 'adb pull /data/misc/wifi/wpa_supplicant.conf' from command-line. If this does not work then do the following:
a. Run 'adb shell' from command line.
b. 'su'
c. 'cat /data/misc/wifi/wpa_supplicant.conf' - copy the output from the command and paste into a text editor (see note in step 6 on why NOT to use notepad).
d. Save the file as wpa_supplicant.conf, preferrably in the same diretory as adb.
e. 'exit' twice should exit you from the adb shell and return you to your command-line. If all else failes a "ctrl-c" should drop you out of adb.
6. Use a text editor to open wpa_supplicant.conf. The file should be located int he same directory as adb. If you are using Windows I would strongly suggest you NOT use notepad. Notepad will typically change all the EOLs (End Of Line) from \n to \r\n which will really mess things up worse.
7. In the file you should see "network={" entries. There maybe one entry, there maybe many entries. You can remove all lines between "network={" and "}" including the latter themselves. If you see your 'home' network listed you can leave it as the only entry and make sure its priority is set to 1 but it maybe better to remove it as well just in case it contains part of the corrupted data.
8. Save the file.
9. Do 'adb push wpa_supplicant.conf /data/misc/wifi/wpa_supplicant.conf' from command-line. If this does not work then do the following:
a. Run 'adb push wpa_supplicant.conf /sdcard/wpa_supplicant.conf' from command-line.
b. Run 'adb shell'
c. 'su'
d. 'dd if=/sdcard/wpa_supplicant.conf of=/data/misc/wifi/wpa_supplicant.conf'
e. Do 'exit' twice to exit the adb shell. If all else fails then a "ctrl-c" should drop you ot of adb.
10. If the wpa_supplicant file was corrupted then the wifi should now be able to enable and you should now be able to connect to a network.
I hope this is helpful to at least a few people.