I just currently opened my box fresh out and installed z4root to root it... Sucess!
Now im trying to downgrade as i am "supposed" to according to this thread.
http://forum.xda-developers.com/showthread.php?t=1036956
This is what is in my about screen under settings so you know what version ect i have http://img546.imageshack.us/img546/1476/20110427032325.jpg
from the aforementioned thread i downloaded the 4349_Downgrade.zip and placed it on my sd card... Renamed it update.zip and closed usb connection, and then powered off and powered up first pressing and holding the "+" on the volume rocker on the top of the tab. and then pressing power.. When i say "+" i mean Volume + witch is on the top left of the tab closest to the right in the direction of the search home menu and back keys...
When im holding this combo of buttons the screen boots up after a second or two says recovery key detected or whatever in the top left for a few seconds and then goes to the g tablet white screen... THen it shows a box with a downarrow on it and a progress bar for a few moments and then shuts off and reboots into the homescreen.......
I read in this forum a topic how the guy experienced the same results but turned out he was holding the Volume - key... I made certian i wasent doing what he did and literally just held the Volume + key on the right edge with the tip of my nail and held power... Same results..
I have tried with the program root explorer going into the file manager... (Why is there a file called sdcard2?? never seen that before) i go into /sdcard find the update.zip i put from the renamed 4349 file and then back up to the "/" dir and mount as r/w and paste the update.zip in there then mount as r/o back out to home power off.. i repeate the aforementioned process and still the excat same thing...
The origonal update that was put on there when i first put in my newly formated fat32 sd card i deleted.. i have searched and search and have no idea what is wrong or how to fix this... Certianly i couldnt be the only one with this issue?
Please help, im just killing time sitting here waiting for help lol.... Thanks..
My end result is im trying to get CWM 08 on there and a great and stable rom witch i choose that RC1 of vegan.. Unless u know of a better one. And once this is all done is there a good kernal i should be flashing? Why and how do i do it.?
Thank you in advance..
1) The downgrade is only necessary if you were on 4349 to begin with.
2) what you described is exactly what should happen in stock recovery for 3588 and older.
3) No... it is not exactly what others have said about holding the wrong volume key because when you do hold the wrong one the screen goes black after a few seconds.
4) SDCARD is your internal storage. SDCARD2 is the mount point for your external (MicroSD Card) storage.
5) It sounds like nothing is wrong...
6) Install CWM... http://forum.xda-developers.com/showthread.php?t=865245
Ooook
The thread i mentioned in my first post the first link if u click it the title of tje topic reads
[STICKY] [ATTENTION] - 3991 and 4349+ VIEWSONIC-LOCKED BOOTLOADER INFO here
Also it has a link to a pic of my about phone so cant u tell from that?
I am lost i did excatly to a T as described in the tutorial in step 6 in your reply and im getting the same thing i hold down volume + it says recovery key detected for a few secs in goes to gtablet screen and flashes to that down with a down arrow.....
What am i missing? Surely i dont have the only tablet with this problem..
Yes, I can... Your TAP UI version is 3391... LOWER than what you are trying to downgrade to. So you don't need to. You are seeing exactly what is supposed to happen with the version you have. This is the normal behavior for that version.
The only thing you are missing is the knowledge that nothing is wrong...
http://forum.xda-developers.com/showthread.php?t=892090
There is nothing wrong with your tablet.....[mod edit]
K J Rad said:
Yes, I can... Your TAP UI version is 3391... LOWER than what you are trying to downgrade to. So you don't need to. You are seeing exactly what is supposed to happen with the version you have. This is the normal behavior for that version.
The only thing you are missing is the knowledge that nothing is wrong...
Click to expand...
Click to collapse
Then why can i not flash CWM? I went to your link tried both internal and sd files mounting on "/" and on "/sdcard" /update.zip or /recovery.zip in either folder and im still getting the same issue when i hold Volume + and power...
I cannot get CWM and a Rom on there.
thebadfrog said:
http://forum.xda-developers.com/showthread.php?t=892090
There is nothing wrong with your tablet.....just your knowledge
Click to expand...
Click to collapse
From what i gather from that link is that i am to take the files insides cwmod_microsd.zip witch are update.zip and recovery folder that houses command and physically take the microsd card out and mount on my computer witch is technicly SDCARD2 and place those files in that root directly... and then the power down insert card and vol up and power.....
I am getting the same issue same box and same nothing.
Most likely because you aren't following the directions. Take some time to learn at least the basics about your tablet. Then read the instructions again.
you can do it on either the internal or external. It depends on what the line in the command file says. Once you boot once whether sucessful or not the command file is deleted. Your making this harder than it is
Then what am i missing? I got this tablet yesterday at 2 pm and stayed up till 3 am trying to get CWM on it!
I cant imagine what im missing, ive read dozens of posts tried atleast 15 times putting either the downgrade or cwm sdcard update files in the internet "/" or "/sdcard" or "/sdcard2"
And yes i noticed that it deletes the update and recovery folder if i drop it in /sdcard2 or "/", ill put the files there either directly to sd card from the computer or thru root explorer and when i hit vol + and power it does the same thing.
This has to be the most frustrating tablet/ android device ever!
The last time i had something this hard was when i bricked my iphone in early 09 and figured out i had to reload the ipw file via a brand new install of itunes from a virgin computer (that computer turned out to be me using the librarys lol)
so i just got both the internal and external cwm files from this post
http://forum.xda-developers.com/showthread.php?t=865245
and put them in both /sdcard and /sdcard 2 for some reason when i used root explorer i noticed that for somereason in /sdcard2 there was a recovery/recovery/command so i pulles recovery to /sdcard2/recovery and pasted it there and deleted the other recovery folder.. re did the whole process and low and behold i was lookin at a CWMN screen! so... i have no idea, but if i ever meet the man who created the Vewsonic g tab ill kick him in the nuts.
Now i followed this guide
http://forum.xda-developers.com/showthread.php?t=865245
and i mounted the usb put the Vegan Rc1 rom in the ROMS folder and choose zip from sd and installed... and im just stuck at the view sonic screen, so i powered off did a wipe data factory reset and wipe cache and then went to advanced and fix permissions... Then to choose install from sd card choose my vegan rom and installed then backed out to home and hit restart and again its been ten mins or so and im still staring at a viewsoniv screen still..... Is this normal or any more suggestions?
There is a fix but as much trouble as you had installing clockwork I'm suggesting you avoid that fix so I'm not even saying the name. Stick with froyo roms
Thats not very helpfull... Just please tell me what it is i can ifgure it out on my own, i obviously did with the CWM now i just cant get the rom installed for some reason i have a tablet that just boots to the view sonic screen at the moment
Just to update...
I fixed it. THanks for your help and no thanks for your sarcasim.
Was stuck at the viewsonic birds screen
So i did so more, searching... its now 5 am and figured out what nvflash is and
via this thread http://forum.xda-developers.com/showthread.php?t=861950
and making sure u extract EVERYTHING in all the zip files with the exception to the USB folder u drop in the nvflash folder as directed, because if u dont u will get a error when u run nvflash_gtablet.bat
Once that is complete follow this thread
http://forum.xda-developers.com/showthread.php?t=865245
Word for word to install Vegan from stock... It may save a lot of confusion to just nvflash from stock and then drop the CWM recovery and update on the sd card and go that route..
Hope this helps and newbs...
See...the search function does work
I'm looking for some help, I've been searching and there's just so much information out there, I can't seem to make much headway.
My tab is boot looping. I monekeyed around with the /system directory and mucked thigns up. doh!
I would like to reflash with this rom here - http://forum.xda-developers.com/showthread.php?t=1162302.
The problem is, I can't figure out how to get the rom on my sdcard. Since the sdcard it's not removable, how do I get it on there? Usb debugging is turned off so I can't use adb to move it over since I can't actually start the tablet to set it usb debugging on.
So, I'm not sure what to do. I can get into fastboot mode and launch CWM, but not much it seems I can do without actually having the update.zip on my sdcard. Can I use fastboot to flash a stock image? If so, I can't find any .img file to be flashed.
Arrrghh... If anybody can point me in the right direction, that would be awesome.
Launch CWM, and mount USB storage from there. Use that to move the rom zip over, and then flash.
It says it can't mount it for some reason....
keeps saying
ClockworkMod Recovery v3.1.0.1
E:Unable to open ums lunfile (no such file or directory)
thanks... I actually just got it back to working. I will post a follow up later to explain all that I did and all that I learned from this experience. I think it will be of great help to others. It's actually quite simple once you Bundestag how things work. Of course only after I asked a question did I finally "get" it.
More to come.
did you figure this out? im in the same boat as you. HElp please!
Hello all.
I'm not from this section of the forum, I'm trolling around. Go to Samfirmware.com Your answer is there.
Sent from my GT-I9100 using xda premium
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!
You have never seen me here, though I have been lurking for quite a while. I don't know that much about how Android works and usually leave everything up the pros. Recently, as in 1 1/2 hours ago, I tried to flash CM 11 through 4EXT. Well... it failed. I was stuck at the HTC loading screen and couldn't access the internal storage. I dug around the internet for a while and, while I did find some work arounds to fix it, they were lengthy and didn't work on Windows 8.1. So, being the impulsive person I am, I attempted something extremely stupid to hopefully solve my issue... and it worked! So, here goes:
1) Boot in 4EXT (not sure if it works on other recoveries)
2) Press the USB storage button
3) On your computer, open up explorer and find where the device is connected (there should be two partitions, D: and E:\)
4) One of the two will have files while the other one just shows a device (for me, it was E:\). Right click, hit properties, then format it. Yes, your read that right: Format it.
5) Reboot your phone into recovery. You should now have access to the internal SD card.
Nice helpful first post. Next time I get stuck like that I'll have to try. It beats the heck out of reinstalling.
I TAKE NO CREDIT OTHER THAN GATHERING AND CLARIFYING THE PROCESS
Seems as though there isn't any device specific directions do this at your own risk if you wake up in the middle of the night and your android is walking around you can blame that on me
Ok start by downloading this http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
This will get you a temp clock work recovery
Also you need su UPDATE zip. To your external sd card http://download.chainfire.eu/supersu
you need the Asus drivers from att http://dlcdnet.asus.com/pub/ASUS/Mo..._Android_USB_drivers_for_Windows_20131202.zip
Ok now to get the phone ready pull the handset loose from tablet
Go to settings/ about/ software information
Tap build number 7 times. Your now a developer
push back once go to developer options
Tick USB debugging
go back go to storage
top right corner tap USB symbol
Select camera ptp
Now plug phone into PC install the drivers you downloaded
when that's done your pc should see phone and ask you what you want to do close all that open the Intel android file you downloaded just unzip to desktop open file and double click launcher look at phone it should be asking you to trust computer click ok
Cap locks on type accept the option t3 and just wait
when your phone is done and in clock work install zip from sd card then go back wipe cache go to backup backup to external SD card you can back up internal but it takes a bit of space now reboot and enjoy root
I want to thank you profoundly for taking the time to do this, truly. Before reading your guide I was going absolutely nuts! I had stumbled through all the relevant guides but for some reason I wasn't piecing it together. Thank you.
evolvedmod said:
I TAKE NO CREDIT OTHER THAN GATHERING AND CLARIFYING THE PROCESS
Seems as though there isn't any device specific directions do this at your own risk if you wake up in the middle of the night and your android is walking around you can blame that on me
Ok start by downloading this http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
This will get you a temp clock work recovery
Also you need su UPDATE zip. To your external sd card http://download.chainfire.eu/supersu
you need the Asus drivers from att http://dlcdnet.asus.com/pub/ASUS/Mo..._Android_USB_drivers_for_Windows_20131202.zip
Ok now to get the phone ready pull the handset loose from tablet
Go to settings/ about/ software information
Tap build number 7 times. Your now a developer
push back once go to developer options
Tick USB debugging
go back go to storage
top right corner tap USB symbol
Select camera ptp
Now plug phone into PC install the drivers you downloaded
when that's done your pc should see phone and ask you what you want to do close all that open the Intel android file you downloaded just unzip to desktop open file and double click launcher look at phone it should be asking you to trust computer click ok
Cap locks on type accept the option t3 and just wait
when your phone is done and in clock work install zip from sd card then go back wipe cache go to backup backup to external SD card you can back up internal but it takes a bit of space now reboot and enjoy root
Click to expand...
Click to collapse
problem rooting
Hey, thanks for posting the step by step guide.
unfortunately haven't get mine to work yet.
I noticed that the "UPDATE-SuperSU-v2.46.zip" in external drive doesnt seem to be visible in the CWM session :/ I do see an Update.zip, however nothing happens when I choose to install from zip.
One question about
the step where we have to "select camera ptp"
why do we have to do that?
I noticed that under "Intel Android Devices Root / Temp CWM Session" the phone had problem accessing the external SD card.
Not sure if it is because the SD card was from my previous android device, will try again after it is reformatted.
When I boot the phone whit de .bat into CWM mode
only shows me a quarter of the image, to be exact the upper left ,
not let me run any commands by usb or touch nowhere.
if I put the phone to the tablet does not work in that state. any suggestions?
frankerebus said:
When I boot the phone whit de .bat into CWM mode
only shows me a quarter of the image, to be exact the upper left ,
not let me run any commands by usb or touch nowhere.
if I put the phone to the tablet does not work in that state. any suggestions?
Click to expand...
Click to collapse
That's because you're using twrp, use option 5. cwm.zip it should work fine... use volume up and down to navigate and power to confirm.