Related
This is a new ipad2 imitation, i'm interested but need community support please:
it is on HSN, these are the specs :
Specs
Model #:
i10-h
Operating System:
Google Android 2.2
Processor:
Samsung A8 Cortex 1GHz
Display:
9.7"; 1024 x 768 resolution; 4:3 aspect ratio
Dynamic RAM:
512MB DDR
Memory Storage:
4GB built-in
Memory Expansion:
microSD card slot
Wireless Networking:
802.11b/g/n
Bluetooth 2.1
Ports:
(1) HDMI output
(2) USB 2.0
(1) 3.5mm earphone jack
Battery:
Lithium-ion 6800 mAh
Measurements:
Approx. 9.64"L x 7.55"W x 0.47"H
Weight:
Approx. 0.8 lb.
Listing:
UL
Country of Origin:
China
I can not vouch for other methods but I have rooted this tablet with SuperOneClick ver. 2.1.1. If you leave "Exploit" on "auto" and click "root" you will be pleasantly surprised. Took me two tries, but if you turn on usb debugging in settings and leave the screen timeout on 30min your golden. Happy rooting.... I'm also uploading a google apps zip file. I unzipped it and installed all the files in the corresponding places to get a working Android Market. I used Android Commander to move the files & install apk's. *NOTE* You need to install the apps in the "/sysem/app" folder in this order...
1. GoogleServicesFramework.apk
2. OneTimeInitializer.apk
3. SetupWizard.apk
4. Talk.apk
5. Vending.apk
6. Gmail.apk
7. Maps.apk
After... Restart, Connect to wifi, and launch Market. You will be prompted to sign in to google. Then you will see Market License blah blah blah...
*Use the attached zip not the one at the following link* But use this link as a guide if you need it... http://forum.xda-developers.com/showthread.php?t=827209
Have fun.
*Zip File Link*
http://www.mediafire.com/download/d85zjeb9b43j9do/gapps-hdpi-20100817-Impression_10.zip
****THIS METHOD WORKED FOR MY IMPRESSION 10 MODEL # i10-50, but UNTESTED by me on other models****
***EDIT*** Sorry guys... you were unlucky because I forgot something crucial.... THE DARN ADB DRIVER.... You will need to go into the device manager and right click the "Android" device with exclamation mark & click update driver. Search for the driver and point the installer to this folder should work on 32 & 64 bit if my edits are correct... Tested on 64 bit Windows 7.
DRIVER
http://www.mediafire.com/?lzrwj65da0c5c63
Also when you install those "/system/app" files above use Android Commanders "Installer" and install them one at a time in the order above. AND AFTER YOU RESTART USE LAUNCHER AND NOT SETUP OR YOU CAN'T ACTIVATE YOUR WIFI.
I tried both methods,
SuperOneClick and Gingerbreak both did not work.
The table is running android 2.3.1.
wonkastocks said:
I tried both methods,
SuperOneClick and Gingerbreak both did not work.
The table is running android 2.3.1.
Click to expand...
Click to collapse
Do you have usb debugging turned on, and did you use the latest version of SuperOneClick. For me it stalled when my screen timeout was to short and locked me out of my tablet when the screen cut off. Second time around it looked like it was going to fail, stalled and then prompted me to ok the install of busybox... etc etc. I am also running android 2.3.1 and it worked for me. Just have to keep trying till you get it.
PIC's...
http://img148.imageshack.us/img148/5624/44983779.jpg
http://img225.imageshack.us/img225/3019/68779107.jpg
http://img32.imageshack.us/img32/7827/42856323.jpg
http://img198.imageshack.us/img198/3149/44013908.jpg
Remember i'm running a i10-50, but the pictures speak for themselves. SU, Market...
Fails
I've also tried this on my husband's Impression 10 - same model i10-50. Can you give some details of how you rooted? What programs did you use besides Android Commander and SuperOneClick 2.2.1? Any help would be appreciated.
i just got an impression 10 as well. i10-50 model with android 2.3.1. im interested in more in depth info on rooting it as well. i tried updating firmware from the page it gives from the box. instructions to download the system.img file from the impression site. but i am not sure how long it takes? when i loaded the file on sd card and restarted (power+vol-) one time it stayed on the blue screen with the white status bar for like over a half hour. i thought it froze and restarted. when i tried it another few times the blue screen disapeared and i got a screen full of multi colored lines all down it. when i reseted.you could still faintly see those lines even when its running normaly. its faintly in background and you can see it more on certain pages or folders u open. my first tablet and i wish there was more info on it. any clue what im doing wrong?
dude i do customer suport forthis tablet, as u may know by now............it sux
leader Impression I10-50 firmware update
In order for the firmware update to be completed successfully, u need to first format your sd card via sd card reader or your tablet as follows:
Plug in the tablet via usb to your PC or load your card reader with sd card
Then select and left click whatever removable disk drive your tablet shows up
Select format and make sure the file system is set at FAT32
Select start, your sd card should begin formating.
Once complete, then u follow the 13 steps, but since you have already started step 1-13, just press your -volume and power buttons at the same time (steps 11 and 12 again) and it should update your tab. Be sure to do it twice as far as the volume and power button go so the update completes successfully.
I cannot seem to get this thing to root....tried the above with the external sd unmounted and then removed. Followed the instruction on the gtab post. All I can see is the external sd card. It did install superuser. Without the sd it gets stuck at Step 6.
It took awhile....but switched to EZ File Explorer. And I was able to see the internal sd and copy the files Then was able to install the market! Life is good!
edit: nevermind
StephenMC said:
It took awhile....but switched to EZ File Explorer. And I was able to see the internal sd and copy the files Then was able to install the market! Life is good!
Click to expand...
Click to collapse
Do you know if the root is reversible in case you need to put it back to the factory default? Would installing the image file on the Impression website reset the tablet back to stock firmware?
TC93 said:
Do you know if the root is reversible in case you need to put it back to the factory default? Would installing the image file on the Impression website reset the tablet back to stock firmware?
Click to expand...
Click to collapse
Yes, SuperOneClick has a unroot option as well.
StephenMC said:
Yes, SuperOneClick has a unroot option as well.
Click to expand...
Click to collapse
Thanks for the reply. About that file program you used, the only one I can find with a similar name is "ES File explorer". Is that the one you used?
I can't get it to copy the files over in the system directory, it acts like its write protected and fails the copy. I must be doing something wrong.
Oops yes ES File Explorer...
Need go to settings.... Open menu, choose Settings Check Root explorer and mount file system...
I'll probably just give up on this. This still isn't wanting to write/copy the files. This is the whole reason I returned my Nook Color before because of the hassle it takes to do this.
edit: it copies a few files, but then some files it says it failed.. like the "maps.apk" file.
Had a few apk's not move as well. I think map was one of them. Just followed the install order and did those from the external sd.....all worked out.
StephenMC said:
Had a few apk's not move as well. I think map was one of them. Just followed the install order and did those from the external sd.....all worked out.
Click to expand...
Click to collapse
Thank you for your help. I finally got it working, I spent hours on this.
But I decided to try that original posts recommendation of using the program "Android Commander". I had to search to find it, but its a Windows program that makes it much easier to copy files over to the root directory. (although I had to change a setting it in so that it auto closes the log window after it copies, otherwise you can't close the log window, or do anything else until its closed).
I wasn't able to copy the maps with that either though, it gave the error that there wasn't enough space. But it seems to be working fine now.
Impression i10-50
I bought the i10-50 and actually love the tablet. With google market installed (update firmware first), I have full access to the market and no problems installing apps. The only con about the tab is no gps. To install the market, I only downloaded the google apps file and installed the apks in the correct order and that was it. No need to root. I am truly enjoying this tab now.
Below,I will list the steps I do to setup my webtop,I am using webtop2sd on a 32GB PNY Class 10 card, and used a 2GB Transcend (not sure on class,im sure its old) card to test with, same results with both pretty much,so I think something im doing is causing it to stop working.
What happends when it stops, is it just wont come up anymore. When I plug the phone into my lapdock, I either get a bluebox with an HDMI not found error (I'm assuming from the dock itself), or the red moto logo that just moves around. I would try resetting the phone, and reinstalling the executable through the webtop2sd app, and it still wont launch. This has happened about 5 times so far, I would get it setup how I would want it to be,then it stops working.
So here is what I would do (there is a phone reboot between each step pretty much)
1. Use my PC to partiton the SD card, ~22 GB FAT32 followed by an ~8GB ext3
2. Use webtop2sd to create the webtop, default settings, aside from the missing dock fix, which I only used 2-3 out of the 5 times I ran it
3. Once I am in the new webtop, I would install terminal and synaptic,then reboot.
4. Then I would run the webtop scripts, version 1.4, hitting yes to everything, then a reboot
5. I would check to see if synaptic is installed, the last time i did this, I had to use aptitude to install it.
6. Once I got synaptic up,I would use it to install the xfce4 package. Just about everytime I would go to install it,I would get an error on the "tzdata" package, the only way I could get past it,would be to uninstall tzdata, then most of the time,whatever I would go to install would reinstall it anyway. This does concern me, because when I remove tzdata, it appears to be tied to a critical package, which may be the source of my problem,but I am not sure.
7. Once I would get xfce4 installed,I would add xfdesktop and xfce-panel to the startup list (those may not be the exact package names,there is another thread I reference for that, can't remember atm, nor can I remember the exact name of that startup file, but its on this forum somewhere). I would also comment out the awmdock one and the webtop desktop one as well.
8. I would reboot,and it would actually boot up xfce4 just fine, the only gripe I have,is that I would usually get an error on the trash service needing thunar, when it is already installed. The one time,I was able to install open office, and test out some youtube videos.
9. At about this time, I would reboot my phone to see if it still works, then I would get the "bouncing moto logo of death" on my lapdock screen, and would have to start over.
One other unrelated note,about every other time I would reboot my phone, it would come up saying SIM card not installed, so I would reboot it again to fix the problem. So there were normally 2 reboots when a reboot is required.
So,I guess I would ask a few direct questions about my problem
1. Has anyone else had a problem with the tzdata package? Is there a way around it without uninstalling it?
2. Could the full xfce4 package be breaking the webtop? Do I only need certain packages out of it?
3. Even though I tested this on 2 different SD cards, could my problem be that the files are just getting corrupted on the card? Its pretty consistant though, I canpretty much say "Look,my awesome webtop is now setup how I want it to be, now watch me reboot my phone to see it not work anymore" everytime I go to set it up.
Info on my phone:
Stock firmware, unlocked bootloader, cwm installed (I thought I needed it,but not for webtop2sd) and rooted running latest webtop2sd. I havent messed with the stock webtop on the phone itself, i rather not since I like having it as a backup.
Btw, I am a bit of a linux n00b, I've pretty much just been reading what other people have been doing. Any help would be appreciated, thanx
You sure like to mod the webtop. Lol jk.
I have no issues and I have webtop with the Lapdock with the Ninja ROM. My phone is bootloader unlocked and rooted. I personally think you modded too much if that's possible. If I were you, I would start over and try webtop with stock firmware or a ROM with a fresh sd card. That way you can know if your phone has a hardware issue or if you modded too much. Hope this helps.
Sent from my Atrix XDA Premium App
I can assure you that your phone is more modded than mine is, since im running stock firmware. What I'm doing is really not that much modding, I'm just trying to get a better interface running on the webtop, which people have posted saying they have the same one working on theirs. Its also not that I can't get it working, its really not hard, just time consuming, I just need to know why it keeps breaking on phone reboots...
teeth_03 said:
I can assure you that your phone is more modded than mine is, since im running stock firmware. What I'm doing is really not that much modding, I'm just trying to get a better interface running on the webtop, which people have posted saying they have the same one working on theirs. Its also not that I can't get it working, its really not hard, just time consuming, I just need to know why it keeps breaking on phone reboots...
Click to expand...
Click to collapse
I honestly think you should try some of my suggestions. I think starting fresh is your best option. When something doesn't wok right or something goes wrong. Starting fresh can fix your issues.
Sent from my Atrix XDA Premium App
I've formatted the SD card about 6-8 times nowsince I got my lapdock 3 days ago
teeth_03 said:
I've formatted the SD card about 6-8 times nowsince I got my lapdock 3 days ago
Click to expand...
Click to collapse
Have you tried reflashing the phone yet with new firmwares or ROMS?
Sent from my Atrix XDA Premium App
why would I do that when the issue has something to do with the files on the SD card?
webtop2sd copies the webtop files from the phone, to the SD card,so the files on the phone are basically out of the equation at that point. So its not a problem with android,but with the other linux files from webtop on the SD card
Oh ok. Well have you tried an all new sd card yet?
Sent from my Atrix XDA Premium App
teeth_03 said:
Below,I will list the steps I do to setup my webtop,I am using webtop2sd on a 32GB PNY Class 10 card, and used a 2GB Transcend (not sure on class,im sure its old) card to test with, same results with both pretty much,so I think something im doing is causing it to stop working.
Click to expand...
Click to collapse
yeah......
I think I fixed it. by finding this little piece of info
http://forum.xda-developers.com/showpost.php?p=18465066&postcount=3
I believe tzdata has been my problem for he past like 3 days I've been messing with this
It has been running great for the past day. XFCE4 is a large improvement over the standard webtop.
Of course, I ran into another snag, I need to access windows network shares, and Samba doesn't seem to be functioning, specifically, the samba-common package wont install correctly.
This user was able to fix it:
http://forum.xda-developers.com/showpost.php?p=19132707&postcount=19
But I have no idea how to fix the read/sym links. Can any linux gurus here explain how that is fixed? Thanx guys!
teeth_03 said:
It has been running great for the past day. XFCE4 is a large improvement over the standard webtop.
Of course, I ran into another snag, I need to access windows network shares, and Samba doesn't seem to be functioning, specifically, the samba-common package wont install correctly.
This user was able to fix it:
http://forum.xda-developers.com/showpost.php?p=19132707&postcount=19
Click to expand...
Click to collapse
Yeah his post was kind of light on the details.
What it looks like is that when the /var/lib/dpkg/samba-common.postinst script is run by dpkg --configure -a it calls a program named ucf that in turn wants to run the symbolic link of "readlink" located in /usr/bin.
This is where i got stuck. I am by no means a linux guru.
I tried deleting the symlink to force ucf to use the "readlink" in the path, tried setting the symlink to point to the "readlink" located in /system/bin and in /system/xbin, and set the symlink to the busybox in /system/bin and to the custom busybox webtop2sd uses in /system/etc/webtop2sd but it did not help.
The output of dpkg changed slightly depending on which "readlink" ucf used but still the same error, "readlink: invalid option", and no samba-common.
Btw my busybox is 1.19.3
2.3.5 webtop on sdcard with fixed dependencies
A little help would be appreciated.
I was told on IRC that the actual problem is that the stock kernel does not include CIPs support, which is what is required for connectivity
but I still dont like the fact that samba package is still broken...
I'm using faux123's 0.2.3 kernel though, which might have CIPs support. Its hard to tell from the changelog and features listed in his kernel thread. Btw the 0.2.3 kernel fixes the broken top panel.
I have a GTab that was running Calkulin + Clemsyn Combo Overclock at 1.5 ghz V8 on the 1.2 branch fine for a couple months now, then something happened today. Woke up to find there was no sound coming from it (I'd left an Anti-mosquito app running all night), so I tried to play a couple music files. Seemed to get frozen instead of playing, so I restarted. That's when it went into a boot loop from 3 birds to the first splash screen of the loaded ROM.
Attempted to do a backup via CWM, and it failed on /data. Tried a data wipe/reset, then reflashing the ROM and finally NVFlash. Still goes into a bootloop. Repartitioning and mounting doesn't do anything; ADB doesn't see the device at all in CWM or APX; /data cannot be mounted and /sdcard mounts only when a card is inserted (doesn't see the internal space) but still doesn't mount USB storage and says: "E:Unable to write to ums lunfile (No such file or directory)"; drive shows in Win7, but is inaccessible;
As mentioned, APX mode and NVFlash along with CWM works fine. And I can mount /cache and /system fine. I've gotten to Code Double Red here and now I'm draining the battery for the next step (really don't want to pull any screws). Also tried the fix here, but it seems that's just for CM7, which I'll probably try flashing some time.
I'm going to return to the 1.1 branch and try a couple ROMs there, but I have a really slow connection and it's taking a while to get nvflash 1.1.
Did a quick search of the forum and didn't find anything quite similar. Obvious question is, has anyone ever experienced this before? What are some other steps I can take to fix this? Is there a way to backup the internal SD before I probably have to wipe it?
Connect the USB cable to the tablet, then boot it into CWM, and run this command on your PC:
Code:
C:\SOME\PATH> [B]adb shell dmesg > dmesg.txt[/B]
Post that dmesg.txt file here. We'll see what's wrong.
Connected the charger long enough to run the command, but all I get is "error: device not found". As I'd said, ADB doesn't detect the tablet, even though Windows knows when it's connected and disconnected. Is there anything that I can flash to get me a terminal? That's the only way I can think of to get that command run and hopefully direct the output to my SD. Thanks.
I now have a completely dead battery. Wondering what to do next since it's supposed to have been hard reset now. Not seeing anything different after booting; same boot loop even though I just flashed a ROM again.
rajeevvp said:
Connect the USB cable to the tablet, then boot it into CWM, and run this command on your PC:
Code:
C:\SOME\PATH> [B]adb shell dmesg > dmesg.txt[/B]
Post that dmesg.txt file here. We'll see what's wrong.
Click to expand...
Click to collapse
I had seen this thread before where you were helping someone last year. Wish I'd read further to see that he eventually got the same problem I now have. I'm currently working my way through everything. First I need to get ADB running though, so I'm working on that now. Think I may be needing that partition swap trick, but we'll see...
Having issues getting the right USB drivers installed for ADB on Windows 7 64 bit. Using instructions here. But each time I uninstall the device, as soon as I plug in the tablet, it installs the default drivers. Using both Device manager and USBDeview. Updating and other options are also disabled when there is nothing installed. Considering to do a direct registry hack of the device info if I can, and hopefully not break anything important.
Try using Linux.
I finally got ADB working on my system and did some experimenting. Seems there's definitely something wrong with my internal SD according to the dmesg output. Luckily I have a SD which I used in my SG3, and it is already properly partitioned, so I'll try using that. Tried making a fstab file in /etc (mtdblock3) but I got "Magic Value Mismatch" error, so I NVFlashed to return it to how it was. I'm currently researching how to create update files, because it seems that's the only way I can get the SDs swapped. Any guidance is still welcomed. Thanks alot.
Skele Drew said:
Seems there's definitely something wrong with my internal SD according to the dmesg output.
Click to expand...
Click to collapse
Yeah. There are clear error messages relating to the internal SD card. You can either return the tablet and get a replacement, or, use my SD card device swapping technique to use the external SD in place of the non-working internal one.
Tried making a fstab file in /etc (mtdblock3) but I got "Magic Value Mismatch" error, so I NVFlashed to return it to how it was. I'm currently researching how to create update files, because it seems that's the only way I can get the SDs swapped.
Click to expand...
Click to collapse
If you use my files, you don't need to modify anything manually. What're you trying to change, BTW?
I can definitely use some help there. Where are the files? I tried modifying the custom ROM I use by adding a custom fstab and vold.fstab to /etc, an init script to init.d and replacing the /data mounting command with:
Code:
ui_print("Copying Data Files");
run_program("/sbin/mount", "-t", "ext3", "/dev/block/mmcblk2p2", "/data");
ui_print("Mount information:");
ui_print(run_program("/sbin/mount"));
Not sure what you're attempting to do here...
If you just want to use an external SD card in place of your non-working internal one, then all you have to do is a) flash either one of the CWM zip files and then b) flash the SD card swapping zip file right after you install the ROM of your choice. And, if you tell me which ROM you plan to install, I can look inside it and tell you if my scripts will work with that ROM.
If you can read shell/awk scripts, you can look inside the zip files to see what they do and how they do it.
rajeevvp said:
Not sure what you're attempting to do here...
If you just want to use an external SD card in place of your non-working internal one, then all you have to do is a) flash either one of the CWM zip files and then b) flash the SD card swapping zip file right after you install the ROM of your choice. And, if you tell me which ROM you plan to install, I can look inside it and tell you if my scripts will work with that ROM.
If you can read shell/awk scripts, you can look inside the zip files to see what they do and how they do it.
Click to expand...
Click to collapse
I was trying to make a swap script myself, but it's not working. /system dir gets corrupted. I'm using Clemsyn_Caulkinver8final2, a Froyo ROM.
Look at my scripts. If you have any questions, just ask.
Where are the scripts? That's what I've been asking...
EDIT: If this is what you use, then all should be ok. Let you know the result when I'm again online. Thanks alot for your help!
That's what I was talking about. I modified the device-swapping script today to fix-up an additional shell script, /system/etc/inandop.sh, on the various Clemsyn/Beasty ROMs (incl. yours), so use the newer zip file.
rajeevvp said:
That's what I was talking about. I modified the device-swapping script today to fix-up an additional shell script, /system/etc/inandop.sh, on the various Clemsyn/Beasty ROMs (incl. yours), so use the newer zip file.
Click to expand...
Click to collapse
Appears it still doesn't work. However, now instead of having a boot loop, it's just stuck at the splash screen after the 3 birds. I'm going to try combining your script and the ROM to see if I can get better results. I'm also going to try inserting some log/debug messages where I can.
Skele Drew said:
Appears it still doesn't work. However, now instead of having a boot loop, it's just stuck at the splash screen after the 3 birds. I'm going to try combining your script and the ROM to see if I can get better results. I'm also going to try inserting some log/debug messages where I can.
Click to expand...
Click to collapse
THANK YOU RAJEEV!!!!!!!
Today I got the time to work on my tablet again, since I just restarted college and it's been a bit hectic. Decided to try CM7 since when I looked into your script I saw direct management for it, so I NV'd back to 1.1 (I didn't know what branch CM7 was on, but flashing CM7 on 1.2 gave an error and aborted). The first time I tried the CM7, it got to the CM7 logo, then was there for a while until I only had a black screen. The only way I knew the tablet was still on was because ADB was still connected. Then I flashed your script and VOILA! everything started great. So now I have my tablet again for my classes .
I am planning to still run a few tests to see if I can somehow recover/fix the internal SD, so I downloaded your set of e2fsprogs. Think I'll make a flashable file for the entire package.
Again, thanks for all your assistance. It's much appreciated. I really didn't have that much time anymore to work on it myself too. I will continue to learn more as time goes on though, and I hope one day I'll become a guru like you .
Skele Drew said:
Decided to try CM7 since when I looked into your script I saw direct management for it, so I NV'd back to 1.1 (I didn't know what branch CM7 was on, but flashing CM7 on 1.2 gave an error and aborted).
Click to expand...
Click to collapse
The official CM7 is, right now, only for 1.1. However, since you can replace just the kernel and instantly make a 1.2 ROM, you'll have to look at the kernel messages to tell which bootloader version you have (Note: this is only for pershoot kernels).
The first time I tried the CM7, it got to the CM7 logo, then was there for a while until I only had a black screen. The only way I knew the tablet was still on was because ADB was still connected.
Click to expand...
Click to collapse
This is to be expected. When a ROM first runs, it writes a whole bunch of stuff into /data; but, your internal SD card is messed up, so every write would've ended up with the kernel retrying for quite a bit and then failing.
You should've flashed the ROM and immediately afterwards my script to fix-up the mount points on the ROM--ie. before the first boot.
I am planning to still run a few tests to see if I can somehow recover/fix the internal SD, so I downloaded your set of e2fsprogs. Think I'll make a flashable file for the entire package.
Click to expand...
Click to collapse
I doubt if you can "fix" your internal SD card error using any of the e2fsprogs--it looks like a card-controller error rather than a media error. You have one of the non-standard internal SD cards which has caused problems for some other users as well.
Ok. I do have a few issues I hope I can get some help on. For one, flash player doesn't work, and that's something very important. All my browsers direct me to get flashplayer. It worked pretty well in my previous ROM, so it may be an issue with CM7, but I haven't seen any similar issues on their site.
Also, the tablet is less responsive now, though I think this has to do with the /data partition being on external SD, though it's a class 6 card.
Sent from my GTablet using Tapatalk
Did you partition the external SD card correctly into 2 partitions (the first as VFAT and the second as ext3) before you installed CM7? I'm not sure what steps from my post you followed and what steps you skipped: you mentioned you were planning to modify the scripts/ROM, right?
It is also possible that my script is not doing the right thing on CM7 since it doesn't touch the vold.fstab on it. Get me the output of a mount command in CM7, and these files:
Code:
/system/etc/vold.fstab
/system/build.prop
Also make sure that you, or the ROM provider, haven't enabled the SD card switching in Settings > Cyanogenmod settings.
The SD I'm using was in a SG3 using this ROM, so I think it's correctly partitioned. I've accessed the partitions before and the correct names are associated with the contents. I only followed steps 1 & 4. The option to use removable for apps and media is disabled.
build.prop
mount.txt
vold.fstab
Wifi and OTA updates were working fine before I rooted my kids' Nabi 2. I never tried an OTA update until after I rooted them, which doesn't work (I tried 2.1 since it said it was available). I followed the directions at http://forum.xda-developers.com/showthread.php?t=2041224 and it worked great to restore to stock 1.9.12, but wifi doesn't work now (mine could have been 1.9.37 originally). I tried the "wifi fix" mentioned, but there are still no wifi networks displayed like there were earlier today. I do not have a micro SD card to install the updates from, as mentioned in the replies. If I were to buy one, can I just put the OTA updates from http://forum.xda-developers.com/wiki/Fuhu_nabi_2 on it, and install from it somehow?
I tried to copy fuhu_nabi2_138139_1937_ota.zip to the device and install through the recovery kernel, but got an "assert failed" error. Any ideas as to what can be done to at least update this to 1.9.37, or maybe do a "stock install" of 1.9.37 instead of 1.9.12 so I have a better chance of wifi working? Please be specific as to what I need to try and in what order...some of the tools I tried seem to be inconsistent in results (Nabi Lab was latest I used). I am comfortable using what t499user has to go back to 1.9.12, I just wish I could use the same method to go to something newer...
I had the wifi problem this past spring. I backed up all my apps and data then flashed back to stock with NabiLab. Re-rooted and all was fine again.
You should also be able to use TWRP to flash back to stock. See TWRP thread http://forum.xda-developers.com/showthread.php?t=2074501
Some more info that may help http://forum.xda-developers.com/showthread.php?t=2248495
This experience is only my second time with TWRP and updating the Nabi. I've previously tried reverting to the backup in the "stockunrooted" folder, which is where I think the original was. I now recall that this had been updated to 2.0 using OTA before it was rooted.
Using TWRP, I tried reverting back to stockunrooted just now. Wifi works again, but OTA still does not (2.1 downloaded and seemed to install quicker, but upon reboot all I saw was "an error installing" message and it went directly to TWRP (where I just rebooted and it went to the Nabi screen). I am not sure what else to try. There is also an "oem" folder available for restore in TWRP, but that is the one created using t499user's process to go to 1.9.12. I initially used t499user's tutorial because I thought maybe something was wrong with the stockunrooted backup.
I have a few questions. Is updating TWRP to the latest version important? If yes, how do I do that (I've seen http://forum.xda-developers.com/showthread.php?t=2074501 before, but still not sure how to download/install 2.6.1.0)? If this has been reverted to "stock" and OTA updates still don't work, how do I apply them manually (from http://forum.xda-developers.com/wiki/Fuhu_nabi_2)?
I just noticed that the "stockunrooted" backup has things that aren't stock. Internal Storage has an Android folder with com.google.apps subfolders, etc. I am back to the original problem, and that is going to "stock" (something other than 1.9.12).
Cool, I figured out how to install 205to210.zip (TWRP 2.3.3.0)...For anyone interested, I copied the zip to Nabi/Internal Storage/TWRP, booted while holding +, pressed - to 'recovery kernel,' pressed + to choose it, then chose install. There is one more update I tried (2127stock.zip), but I get a flash error and it did not install. Considering (so far) I cannot get back to "stock unrooted" and use OTA updates, does anyone know how I can install this?
Wait...maybe there isn't another update. http://forum.xda-developers.com/wiki/Fuhu_nabi_2 has "Update 2.0.5 to 2.1.27" as the latest. I think it is working OK. Back to my original question(s), what is the process to install an updated version of TWRP and a "stock version" of something other than 1.9.12? Just trying to get the whole process understood...If I can simply use t499user's tutorial with different images, that would be rad to the max.
brentford said:
Wait...maybe there isn't another update. http://forum.xda-developers.com/wiki/Fuhu_nabi_2 has "Update 2.0.5 to 2.1.27" as the latest. I think it is working OK. Back to my original question(s), what is the process to install an updated version of TWRP and a "stock version" of something other than 1.9.12? Just trying to get the whole process understood...If I can simply use t499user's tutorial with different images, that would be rad to the max.
Click to expand...
Click to collapse
Yes its probably wise to update to TWRP 2.6.1.0. Get the file
Download
Follow "Method 3" here
http://forum.xda-developers.com/showthread.php?t=2074501&highlight=nabi
As for getting a stock image. You were using the zips here http://forum.xda-developers.com/wiki/Fuhu_nabi_2
You dont "Install" those zips. You need to extract the contents. boot.win, system.win, etc. and put them in the TWRP folder.(TWRP/BACKUPS/XXXXXX/folder)
Make a folder called 2127 put the filed in there. Then "Restore in TWRP. Then you should have a stock system. Same goes for 1937stock.zip 205stock.zip
If you have questions ask away.
Thank you all! I think I am getting it. Since I am reading (and had first hand experience) that Google Play isn't working very well with 2.1.27, I will go back to 2.05. That should keep the kids happy. I will let you know if I have more questions.
Oops...I broke something. I have two Nabis. I accidentally restored one using the device ID path of the other. I used "adb push c:\nabi\fuhu_nabi2_v1912_system.ext4.win /sdcard/TWRP/BACKUPS/015d2bc264340217/oem/system.ext4.win" for both. The incorrect one booted, but I noticed that the apps aren't the same. I tried to use TWRP again, but it is not recognized by cmd "adb devices" and I get "error: device not found" when trying "adb reboot-bootloader." I also tried whatever restore option there was in the settings, but it is the same result...Any options?
brentford said:
Oops...I broke something. I have two Nabis. I accidentally restored one using the device ID path of the other. I used "adb push c:\nabi\fuhu_nabi2_v1912_system.ext4.win /sdcard/TWRP/BACKUPS/015d2bc264340217/oem/system.ext4.win" for both. The incorrect one booted, but I noticed that the apps aren't the same. I tried to use TWRP again, but it is not recognized by cmd "adb devices" and I get "error: device not found" when trying "adb reboot-bootloader." I also tried whatever restore option there was in the settings, but it is the same result...Any options?
Click to expand...
Click to collapse
Google play won't work with 2.1.27 unless you delete some apps from /system/vendor/apps before installing gapps
As long as you have the bootloader(with the 4 options boot normal, fastboot, recovery kernel, forced recovery) and working USB port there are always options.
So is ADB not working in TWRP or in Android or both? It's probably best to copy boot.emmc.win, data.ext4.win and restore those too since you have done so much stuff. Boot contains you kernel, and data the apps. You will be back to a stock tablet with no game saves or anything so make sure you got off the tablet what you needed
I don't see a /system/vendor folder using TWRP file manager now...is that only when 2.1 is installed? How much do I need to remove, and are there any known problems with gapps in this case?
I fixed whatever problems I had. (Yes, I still have the bootloader.)
I am not that familiar with this, but let me explain what I have done. As before, I was using ADB/fastboot instructions from http://forum.xda-developers.com/showthread.php?t=2041224 (Windows 7). Both tablets' Internal Storage were recognized by Windows, but only the other one (with correct device ID 015d2bc264340217) was recognized when using ADB. That is how I was updating between Nabi 2 versions before.
Tablet 1:
C:\adb>adb devices
List of devices attached
015d2bc264340217 device
Tablet 2 (normally 015d24a7f41c1c15):
C:\adb>adb devices
List of devices attached
At one point, both devices started an endless loop when booting (shows the "Please wait while Nabi initializes" message for a split second and boots again). It may have been something with the way I installed the OTA updates, but I figured that it had to be something wrong with System so I wiped absolutely everything from within TWRP and I followed t499user's instructions for Windows cmd line (for going back to 1.9.12). Everything is good now, but I don't want to upgrade to 2.1 if gapps has any problems...
brentford said:
I don't see a /system/vendor folder using TWRP file manager now...is that only when 2.1 is installed? How much do I need to remove, and are there any known problems with gapps in this case?
I fixed whatever problems I had. (Yes, I still have the bootloader.)
I am not that familiar with this, but let me explain what I have done. As before, I was using ADB/fastboot instructions from http://forum.xda-developers.com/showthread.php?t=2041224 (Windows 7). Both tablets' Internal Storage were recognized by Windows, but only the other one (with correct device ID 015d2bc264340217) was recognized when using ADB. That is how I was updating between Nabi 2 versions before.
Tablet 1:
C:\adb>adb devices
List of devices attached
015d2bc264340217 device
Tablet 2 (normally 015d24a7f41c1c15):
C:\adb>adb devices
List of devices attached
At one point, both devices started an endless loop when booting (shows the "Please wait while Nabi initializes" message for a split second and boots again). It may have been something with the way I installed the OTA updates, but I figured that it had to be something wrong with System so I wiped absolutely everything from within TWRP and I followed t499user's instructions for Windows cmd line (for going back to 1.9.12). Everything is good now, but I don't want to upgrade to 2.1 if gapps has any problems...
Click to expand...
Click to collapse
Before browsing with TWRP file manager you need to go to the "Mount" tab, put an X in system. Then go to file manager.
Probably have to remove around ~50MB, maybe a bit less. Lots of people choose Wings, but obviously Wings is something some kids love. Really depends on the user.
When you flash stock, it often reset USB debugging to off in Android settings, if you flashed data too.
USB debugging is still on. Do you know anything about whether or not gapps has any problems with rooted Nabi 2.1? You have been a great help!
I didn't realize what would happen until it broke, but what I tried to do was remove apk files prior to upgrading to 2.1. I have copies of them on Internal Storage and locally, but I don't see a way to copy them back to /system/vendor/app using TWRP (tried mounting everything except external storage, which isn't selectable; internal storage isn't selectable, located to the right). Is there a way to do it, or do I have to go back to 1.9.12 and start over?
brentford said:
I didn't realize what would happen until it broke, but what I tried to do was remove apk files prior to upgrading to 2.1. I have copies of them on Internal Storage and locally, but I don't see a way to copy them back to /system/vendor/app using TWRP (tried mounting everything except external storage, which isn't selectable; internal storage isn't selectable, located to the right). Is there a way to do it, or do I have to go back to 1.9.12 and start over?
Click to expand...
Click to collapse
The only problem gapps has is there isn't enough room for it with a stock 2.1. You have to remove something.
Mount everything in TWRP. Go to file manager. /data/media is internal storage. You will find your files. Copy them back to /system/vendor/apps. Might have to set permissions.
Thanks! I copied from Windows using adb, but I got the same asset error (two of the files no longer had their original icon, it was default Android icon). That might have been the permissions issue you mentioned. In the future, how do I change the permissions, and what should they be set to? After this, I am done messing with it. Thank you for everything!
brentford said:
Thanks! I copied from Windows using adb, but I got the same asset error (two of the files no longer had their original icon, it was default Android icon). That might have been the permissions issue you mentioned. In the future, how do I change the permissions, and what should they be set to? After this, I am done messing with it. Thank you for everything!
Click to expand...
Click to collapse
You might be out of space again depending on what you copied back and why the icons are blank. Check with
adb shell df (in Android)
Look at system and see how much space you have free.
Or it could be permissions. You can use a file manager in Android such as ES File Explorer or Astro. You need to go to the setting in the app and enable whatever option they have to browse and remount "system" as read/write that will require root and should prompt you to accept. Then you can browse to the directory. You could also use TWRP File manager the same as when you copied files. There is a permissions tab.
I think the permission you want is 0644(for TWRP), or wr-r--r--(for ES). Same thing just different nomenclature.
Similar issue as OP
Hi guys, I have done pretty much the same thing as the OP. The wireless will not turn on or find any networks. I have tried reverse tethering, but have lost root and pretty much any other way to get internet to the nabi 2, so I can update from version 1.9.12. The big problem is I cannot use TWRP because when I boot into recovery and try to get there I get the dead green android guy with the exclamation point error and it hangs there until a hard restart. Any ideas on how to fix this. Is there a way to push an update through the SD card? Any ideas and suggestions would be greatly appreciated. I have already spent more time than I would have liked trying to fix this.
Dead android is stock recovery. You need to reflash TWRP.
Also to get out of the stock recovery just press vol + and - together. Should be am option to reboot. No need to hard power off.
aicjofs said:
Dead android is stock recovery. You need to reflash TWRP.
Also to get out of the stock recovery just press vol + and - together. Should be am option to reboot. No need to hard power off.
Click to expand...
Click to collapse
Well I swear I have tired this, but decided to give it another go and it worked! Got TWRP up and running then ran NabiLab to return to stock 1.9.37. Wireless is working and updating to 2.1 and then will give root a shot and GApps. Thanks for getting back on track!
Hello,
I have bought an Acer E380 about two months ago, and I rooted it two days later.
It was (afair*) always on 4.4.2, and I never had problems with it.
But about a week ago, I installed the popcorntime app from the official said website (Horrible app, torrent downloader is slow and often breaks, if you restart your phone the 'checking files...' goes on forever,...) and said app, that was downloading a file, crashed and would not let me restart a download because of "insufficient space".
I tried deleting said file, unusable but full size, thanks to that useless torrent client, and it kept coming back.
I could not edit the SD card files from another computer with linux, and windows would straight out not recognize it.
After wiping it with gParted, it worked fine on both windows and linux, but android started screwing with my root.
Some apps like linux deploy would not be able to write, impossible to copy a file from the phone's memory to the card, and much more...
But it strangely worked fine with "normal" apps without root access!
After opening a terminal, I made a quick dummy file and tried to copy it to sdcard0, worked fine.
I then tried to proceed the exact same way with superuser rights, and it threw some Endpoint errors as well as just "Read-Only Filesystem"
Does anyone knows what's going on, and how can I fix this mess?