Related
I have been searching all morning for the answer to my issue, but evidently I am not using the correct words in my search. Either that or I am the first person to need to do this:
In an effort to try to get Netflix working on my Gtab running Vegan 5.1.1, I have been trying differing edits of the build.prop file. Since Netflix is working on my original version Droid, I have been using it as a model. All to no avail. So, last evening, fully aware that I might brick the gtab and willing to pay the price of a reflash if necessary, I copied the entire build.prop file from my Droid to my gtab and rebooted. Sure enough, won't boot.
I have backups of the original working build.prop but cannot access it by connecting my gtab to my pc through usb. I can access the files on the sdcard but cannot figure out how to get into the system folder so that I can replace the offending file with a good one. I thought that nvflash might be my friend, but after reading everything I can find on that tool it seems that it will just reflash to stock.
I can reflash my Vegan install, and may have to do so....but is it possible to just access the files in the system folder? If so, all I would have to do is to delete the current build.prop file and rename my backup file back to build.prop.
Anyone know how I can do this?
Joe
You can us ADB to push (or pull) files as well as accessing the command line on your gTab. ADB is a development tool, and is part of the Android development kit. You need to install the driver that comes with it, but first you need to edit the .INF file with a couple lines referencing the gTab. You can find additional information about ADB in other posts.
If recovery is working ok then you could reflash your ROM or craft a custom update to replace build.prop.
You could also nvflash just the system partition if you have an image for your ROM.
Lots of options.
Edit: Just looked at the Vegan 5.1.1 supplement update and it has a build.prop file in it. Reinstalling it would likely get you running again as long as you haven't made any other significant changes to the system files. It might revert a few system applications to older versions.
If you have adb set up and working, restoring your backed up build.prop would be trivial job. Let us know if you have adb working and then we can give you the commands you need to use.
As of right now, I do not have adb setup and working. Well, that's not quite true....I did set it up quite some time ago and used it on my Droid. Guess I need to reconfigure it for the gtab and then proceed from there?
Joe
Well, I resolved my issue by reflashing the VegaN rom, all is good now.
Joe
Mine is a froyo 2.2.1 device (ViewSonice VB730), I tried z4root, instant root, DPRoot, and many many many rooting apk but it is not working, some of them are FC or some of them are stucking in "attempting to apply root"
I tried to use SuperOneClick but since I can't find a suitable driver for it, so when I use "adb devices", the list is empty.
I also checked out about some article about how to manually root a devices with PC, seems I have to copy the necessary file first to /data then run the exploit. Since I dont have the driver, I tried to do it with Terminal Emulator and tried to grand access right of /data but failed.
cd /data/
$ ls
ls: can't open '.' : Permission denied
$ chmod 777/data
chmod: /data. Operation not permitted
What should I do
Still no one answer this..
Sorry, I cant help you. Just interested in the right answers.
Not sure but if you can find a copy of Z4Root it might work on Froyo
Sent from my Transformer TF101 using Tapatalk
baseballfanz said:
Not sure but if you can find a copy of Z4Root it might work on Froyo
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
I have tried it before but it keep stucking at "attempting to apply root"
I am here and still waiting for the answer..........
Another 12 hours has just passed...
Another 12 hours just passed......again
Don't be so sad. I am here with you.
Mr.Wrong said:
Don't be so sad. I am here with you.
Click to expand...
Click to collapse
Thanks
I just wonder if I post this in wrong section so no one is here
Nooope, maybe just the ones who can answer it are happened to be falling in love with their ladies and cant spare time here. Why don't you try some ways of rooting the similar phones. There are so many people out there talking about rooting their devices everywhere, maybe you can try some. Next time I will copy for you.
Mr.Wrong said:
Nooope, maybe just the ones who can answer it are happened to be falling in love with their ladies and cant spare time here. Why don't you try some ways of rooting the similar phones. There are so many people out there talking about rooting their devices everywhere, maybe you can try some. Next time I will copy for you.
Click to expand...
Click to collapse
I tried almost any method before opening this thread.. like Superoneclikc, z4root or some similar ways or apps, but if you still have any recommendation for me, I will still try it and thanks
few days passed, still try to pump this for hope
still try to pump this for hope
I wonder ViewSonic vb730 is same as Creative ZiiO 7" tablet in view of their features and CPU. The guide at http://forum.xda-developers.com/showthread.php?t=1010402 may also apply for ViewSonic vb730
aleunghk said:
I wonder ViewSonic vb730 is same as Creative ZiiO 7" tablet in view of their features and CPU. The guide at http://forum.xda-developers.com/showthread.php?t=1010402 may also apply for ViewSonic vb730
Click to expand...
Click to collapse
(pump thread and reply )
I heard about this method before, but the main problem is I can't find the suitable driver for the device so I am not able to perform any action related to the adb.. can you tell me which one you have choosen which one for your Creative ZiiO 7"? Thanks a lot!
few days a pump
I'm going to say I have the same problem with the VB730. I wish to root this thing but can't seem to make it work (in spite of hours and hours of work). Programs I've tried:
Z4 Root
Universal Androot
Instant Root
SuperOneClick
I've also attempted to do it by hand. No dice. I have installed File Expert which allows me to see all the files including the system files, however, I cannot write to these files nor change them without at least temporary root access.
After looking around though, I think the problem seems to be the same as the Creative ZiiO tablet in that there is no driver available for the USB debugging and even once you get those files, the Android system files aren't in normal places so you'd have to figure out a workaround for it.
I tried following the guide here and I believe this would work but for the problem of the USB driver. I wrote to ViewSonic asking for a solution to get my USB Debugging to work but they have no idea what to do it seems. Or they just don't care enough to figure it out.
I tried using the PID, VID and MI for the ZiiO as per the guide (despite it being for a different vendor and product) which got the driver to install and recognize the VB730 as an Android device (when first installed, it came up with a bad parameter but I restarted the device, reinstalled the driver and the problem disappeared) but I am unsure where to make and put the adb_usb.ini file as there isn't a ".android" file located on the VB730 (there IS a ".android_secure" folder on the write-able portion though). So, when checking for devices through ADB I get a readout that says no devices are connected.
Anyone have any ideas on what else I (we) could try? Thanks both for the help already given and any still to come!
Try superoneclick 2.1.1 ,It may help you.
cuplzz said:
Try superoneclick 2.1.1 ,It may help you.
Click to expand...
Click to collapse
Nope! That's the version I tried. Not going to work.
I was trying to modify build.prop to get Play Store to work which bricked the device. Tried factory reset and now it's totally not being recognized by the computer and ADB not working. Any solution or help.
Android Cowboy said:
I was trying to modify build.prop to get Play Store to work which bricked the device. Tried factory reset and now it's totally not being recognized by the computer and ADB not working. Any solution or help.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2491057 Try this. It might at least get recognized in adb and then you can try factory reset in fastboot.
johnnydowngrief said:
http://forum.xda-developers.com/showthread.php?t=2491057 Try this. It might at least get recognized in adb and then you can try factory reset in fastboot.
Click to expand...
Click to collapse
I can't get into the safe mode either. I can get into recovery mode to factory reset but that's it. ADB still not recognized.
Android Cowboy said:
I can't get into the safe mode either. I can get into recovery mode to factory reset but that's it. ADB still not recognized.
Click to expand...
Click to collapse
Then maybe this. http://forum.xda-developers.com/showthread.php?t=1379875 But I'm just guessing here. I dont want to spam this thread. Maybe someone more experienced can help you.
I did same thing. Strange but I COULD finally use adb, but only from the Android SDK base folder & only after uninstalling all devices & using USB deview to remove all adb, mtp & other android related USB devices.
So far, it looks like Amz actually keeps a partial firmware backup on the device, which they can use via mayday when things get really messed up. I would bet, they can also see system mods. It may even function automatically in some instances, I goofed mine pretty bad restore HD system files with TB & after a couple resets, it seemed it restored the system files.
Sent from my Nexus 7 using XDA Premium HD app
GSLEON3 said:
I did same thing. Strange but I COULD finally use adb, but only from the Android SDK base folder & only after uninstalling all devices & using USB deview to remove all adb, mtp & other android related USB devices.
So far, it looks like Amz actually keeps a partial firmware backup on the device, which they can use via mayday when things get really messed up. I would bet, they can also see system mods. It may even function automatically in some instances, I goofed mine pretty bad restore HD system files with TB & after a couple resets, it seemed it restored the system files.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I will try that. If I could just push a new build.prop to overwrite the old one I put probably be okay. How did restore system files using ADB.
GSLEON3 said:
I did same thing. Strange but I COULD finally use adb, but only from the Android SDK base folder & only after uninstalling all devices & using USB deview to remove all adb, mtp & other android related USB devices.
So far, it looks like Amz actually keeps a partial firmware backup on the device, which they can use via mayday when things get really messed up. I would bet, they can also see system mods. It may even function automatically in some instances, I goofed mine pretty bad restore HD system files with TB & after a couple resets, it seemed it restored the system files.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Do you think you can pull a system.img for me in case I can get ADB working then I can try and flash. Lots of other people are bricking as well after root so it might be useful to many people. Thanks.
GSLEON3 said:
I did same thing. Strange but I COULD finally use adb, but only from the Android SDK base folder & only after uninstalling all devices & using USB deview to remove all adb, mtp & other android related USB devices.
So far, it looks like Amz actually keeps a partial firmware backup on the device, which they can use via mayday when things get really messed up. I would bet, they can also see system mods. It may even function automatically in some instances, I goofed mine pretty bad restore HD system files with TB & after a couple resets, it seemed it restored the system files.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
That didn't work for me, I've also trying factory resetting again multiple times through recovery, but no dice.
I got my fastboot cable working, and was able to get the device recognized as "Qualcomm USB modem converter"
I opened a thread about it, any help is appreciated!
Android Cowboy said:
Do you think you can pull a system.img for me in case I can get ADB working then I can try and flash. Lots of other people are bricking as well after root so it might be useful to many people. Thanks.
Click to expand...
Click to collapse
I am on the road right now, but I will see what I can do when I get home. You could try DL the firmware bin from Amazon. It is on their site & if you have ADB, pushing a file may be easiest, particularly since nobody has has any luck with flash or boot commands yet. At any rate, I'll do it as soon as I can, but seriously, start with just trying to push the build.prop so you still have SU & root level shell access.
GSLEON3 said:
I am on the road right now, but I will see what I can do when I get home. You could try DL the firmware bin from Amazon. It is on their site & if you have ADB, pushing a file may be easiest, particularly since nobody has has any luck with flash or boot commands yet. At any rate, I'll do it as soon as I can, but seriously, start with just trying to push the build.prop so you still have SU & root level shell access.
Click to expand...
Click to collapse
Even with the fastboot cable ADB/fastboot is not working. The Kindle finally gets recognized but as a Qualacomm device and can't find the right drivers that can make it recognize ADB. I actually have a replacement coming today so I might just let this one go. I was hoping to figure it out so I could help others in the same situation. But the factory rest really messed this thing up and Amazon is not making it easy.
Android Cowboy said:
Even with the fastboot cable ADB/fastboot is not working. The Kindle finally gets recognized but as a Qualacomm device and can't find the right drivers that can make it recognize ADB. I actually have a replacement coming today so I might just let this one go. I was hoping to figure it out so I could help others in the same situation. But the factory rest really messed this thing up and Amazon is not making it easy.
Click to expand...
Click to collapse
Did you try either of these drivers:
http://www.4shared.com/rar/kRIFBtGe/qualcomm_hsusb_device_drivers.html
http://drivers.softpedia.com/progDo...dows-7-x64-Windows-8-x64-Download-179130.html
So I actually had a similar thing happen today. build.prop mod caused my 7" to boot loop. It makes it to the first kindle screen and then the screen goes black. Based on what I've read I shouldn't try to factory reset it, because that will make it worse. I ordered a fastboot cable that should be in on Monday. Only issue is, I don't have much experience with fastboot. Would I be able to adb push a stock build.prop file to fix it if it's recognized by my computer?
S_transform said:
So I actually had a similar thing happen today. build.prop mod caused my 7" to boot loop. It makes it to the first kindle screen and then the screen goes black. Based on what I've read I shouldn't try to factory reset it, because that will make it worse. I ordered a fastboot cable that should be in on Monday. Only issue is, I don't have much experience with fastboot. Would I be able to adb push a stock build.prop file to fix it if it's recognized by my computer?
Click to expand...
Click to collapse
Since you didn't factory reset, does it show up on adb devices at all while it's trying to boot ?
S_transform said:
So I actually had a similar thing happen today. build.prop mod caused my 7" to boot loop. It makes it to the first kindle screen and then the screen goes black. Based on what I've read I shouldn't try to factory reset it, because that will make it worse. I ordered a fastboot cable that should be in on Monday. Only issue is, I don't have much experience with fastboot. Would I be able to adb push a stock build.prop file to fix it if it's recognized by my computer?
Click to expand...
Click to collapse
Try to use adb with root to push a new build.prop file. That's your best bet for recovery.
Sent from my Nexus 5 using Tapatalk
So currently its not showing up on adb while its booting, but that's probably because I haven't updated adb in a while. I'm going to update when I get home from work and report back.
EDIT: So I update ADB, which isn't recognizing it, but oddly enough, my computer can see it even after the screen shuts off as an android device. My only guess then is I'm missing a driver or something. Any suggestions?
Android Cowboy said:
Try to use adb with root to push a new build.prop file. That's your best bet for recovery.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
So I finally got ADB to recognize the device, and I can adb shell and everything, but its saying I don't have permission to adb push /system/build.prop. Also I thought that was where build.prop was located but I can't find it in adb shell. I have tried su and it hangs up, like its asking supersu for permission and I can't respond. What can I do?
S_transform said:
So I finally got ADB to recognize the device, and I can adb shell and everything, but its saying I don't have permission to adb push /system/build.prop. Also I thought that was where build.prop was located but I can't find it in adb shell. I have tried su and it hangs up, like its asking supersu for permission and I can't respond. What can I do?
Click to expand...
Click to collapse
Try adb root to reload it with root permission. Otherwise you'll need to chmod to make the system RW so you can push the build.prop file. And yes it's in the system folder. If you have the Android SDK then you can use the file manager in Monitor.bat file under "tool" folder to see to see all the files.
Android Cowboy said:
Try adb root to reload it with root permission. Otherwise you'll need to chmod to make the system RW so you can push the build.prop file. And yes it's in the system folder. If you have the Android SDK then you can use the file manager in Monitor.bat file under "tool" folder to see to see all the files.
Click to expand...
Click to collapse
When I try adb root it tells me I can't do that on consumer devices or something like that. what would the chmod command be? I dont think I've used it before. Also thank you so much for helping me.
S_transform said:
When I try adb root it tells me I can't do that on consumer devices or something like that. what would the chmod command be? I dont think I've used it before. Also thank you so much for helping me.
Click to expand...
Click to collapse
When you ADB shell, are you seeing a "#" which means you are rooted. I'm not the world's expert on ADB but this should help. Once you are shell and rooted you can just chmod 644 or 777 on /system and see if that works. http://gizbeat.com/2103/how-to-change-file-permissions-through-adb/
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.
So i got the new G8X and have been trying desperatey to just access the system files to remove some bloatware.
Problem is it only gives me access from \User\0 and on. I tried to delete them through adb on windows but everytime i try and run adb shell the phone automatically disconnects.
I know i have all the updated drivers cause it recognizes the phone through windows and adb when i type adb devices
but as soon as i execute adb shell it disconnects. Does anyone have a solution for this?
Any sort of feedback would be greatly appreciated. i Have a 30 day return policy in effect if i cant gain access to any of that i plan on returning the phone.
Thanks for reading
Edit: Im dumb switching ports and usb cable resolved issue.
If anyone hears anything about root access please advise. Thanks all
I have had my phone on ADB and sending and reading data from it two nights in a row, I have not seen this problem at all. I can run adb shell no problem. Sorry! I know it's a stupid suggestion, but can you try a different USB cable/port on your PC?
SirataXero said:
I have had my phone on ADB and sending and reading data from it two nights in a row, I have not seen this problem at all. I can run adb shell no problem. Sorry! I know it's a stupid suggestion, but can you try a different USB cable/port on your PC?
Click to expand...
Click to collapse
Its not dumb, i appreciate the input i hve not tried a diff port or cable. I'm going to do that right now.
What provider are you using?
abraham3991 said:
Its not dumb, i appreciate the input i hve not tried a diff port or cable. I'm going to do that right now.
What provider are you using?
Click to expand...
Click to collapse
The problem might be that if you run from power shell command, first type cmd and press enter.
abraham3991 said:
Its not dumb, i appreciate the input i hve not tried a diff port or cable. I'm going to do that right now.
What provider are you using?
Click to expand...
Click to collapse
I bought unlocked but i'm using it with T-Mobile and its getting WiFi calling and HD Voice and everything. Works really well and am getting good service/signal with it on T-Mobile.
Yeah, as suggested, I also used it in CMD and not in powershell…
SirataXero said:
I bought unlocked but i'm using it with T-Mobile and its getting WiFi calling and HD Voice and everything. Works really well and am getting good service/signal with it on T-Mobile.
Yeah, as suggested, I also used it in CMD and not in powershell…
Click to expand...
Click to collapse
As simple as your suggestion was it lets me command it through cmd now., switching the cable worked.
Still through the phone itself i cant access system directories. and its not like i cant change things it just flat out wont let me view them at all.
The end goal is to get root/custom recoveries so i can install magisk and xposed, if you hear anything let me know.And thanks again!
abraham3991 said:
As simple as your suggestion was it lets me command it through cmd now., switching the cable worked.
Still through the phone itself i cant access system directories. and its not like i cant change things it just flat out wont let me view them at all.
The end goal is to get root/custom recoveries so i can install magisk and xposed, if you hear anything let me know.And thanks again!
Click to expand...
Click to collapse
No problem! Glad that worked.
I can view system directories, and I read them as well. However, I definitely can't change anything and don't have write access either.
Will be open to suggestions/attempts in the future!
SirataXero said:
No problem! Glad that worked.
I can view system directories, and I read them as well. However, I definitely can't change anything and don't have write access either.
Will be open to suggestions/attempts in the future!
Click to expand...
Click to collapse
Sorry or the constant questions I downloaded a file explorer and im able to see more than before but i still have some files telling me i lack access.
What file explorer are you using?
abraham3991 said:
Sorry or the constant questions I downloaded a file explorer and im able to see more than before but i still have some files telling me i lack access.
What file explorer are you using?
Click to expand...
Click to collapse
I use Solid Explorer. So, some of the files you can physically see in the explorer, but if you try to open it, the text is garbled. It was only after I started doing adb pull that I could actually see/read the files themselves.