Sorry for the noobish question, I've looked for an answer but I haven't been able to find one thus far.
To the best of my knowledge, I have successfully unlocked the the booter and flashed a custom recovery. I also believe I have superuser installed (this was accomplished through TWRP).
The problem I run into is with flashing a custom rom. The first step always includes places the zip of the rom onto the sd card (or virtual sd card as I believe it is in this case) of my HTC One. I don't know how to accomplish this. I cannot browse the internal memory of the HTC One through my computer- whether it is in boot mode, recovery mode, or just booted regularly with USB debugging on or off. How do I get the actual zip ONTO the device?
The main thing I want to accomplish is to remove blinkfeed and change the theme of my device to be more minimalistic. I'm sure I can find a rom out there that does this, I'm just running into problems with this particular step. Should I be able to browse the memory of my device via the PC, or is there a different method of getting the zip onto my device entirely?
Thank you for the help
Either download it on to the phone directly or move it on to your phone from your pc via usb
Sent from my HTC One using Tapatalk 4 Beta
Btonic said:
Sorry for the noobish question, I've looked for an answer but I haven't been able to find one thus far.
To the best of my knowledge, I have successfully unlocked the the booter and flashed a custom recovery. I also believe I have superuser installed (this was accomplished through TWRP).
The problem I run into is with flashing a custom rom. The first step always includes places the zip of the rom onto the sd card (or virtual sd card as I believe it is in this case) of my HTC One. I don't know how to accomplish this. I cannot browse the internal memory of the HTC One through my computer- whether it is in boot mode, recovery mode, or just booted regularly with USB debugging on or off. How do I get the actual zip ONTO the device?
The main thing I want to accomplish is to remove blinkfeed and change the theme of my device to be more minimalistic. I'm sure I can find a rom out there that does this, I'm just running into problems with this particular step. Should I be able to browse the memory of my device via the PC, or is there a different method of getting the zip onto my device entirely?
Thank you for the help
Click to expand...
Click to collapse
you don't need to flash a rom to remove Blinkfeed. Download Nova launcher or Go EX launcher from Google play and that will solve your Blinkfeed issue.
do you have the proper drivers installed on your pc? Normally when I plug my phone in, HTC SYnc starts up and shortly after a small window pops up with my Ones internal storage.. I click on that and it takes me right to the root of my sdcard (internal storage).
Btonic said:
Sorry for the noobish question, I've looked for an answer but I haven't been able to find one thus far.
To the best of my knowledge, I have successfully unlocked the the booter and flashed a custom recovery. I also believe I have superuser installed (this was accomplished through TWRP).
The problem I run into is with flashing a custom rom. The first step always includes places the zip of the rom onto the sd card (or virtual sd card as I believe it is in this case) of my HTC One. I don't know how to accomplish this. I cannot browse the internal memory of the HTC One through my computer- whether it is in boot mode, recovery mode, or just booted regularly with USB debugging on or off. How do I get the actual zip ONTO the device?
The main thing I want to accomplish is to remove blinkfeed and change the theme of my device to be more minimalistic. I'm sure I can find a rom out there that does this, I'm just running into problems with this particular step. Should I be able to browse the memory of my device via the PC, or is there a different method of getting the zip onto my device entirely?
Thank you for the help
Click to expand...
Click to collapse
Although I suggest using the cable you could also put the rom in googledrive, or any other cloud storage site. Then download to /sdcard/downloads folder using an app like EZ File Manager. Now the rom is on your phone. Just might take a little while depending on the size of the file.
Btonic said:
Sorry for the noobish question, I've looked for an answer but I haven't been able to find one thus far.
To the best of my knowledge, I have successfully unlocked the the booter and flashed a custom recovery. I also believe I have superuser installed (this was accomplished through TWRP).
The problem I run into is with flashing a custom rom. The first step always includes places the zip of the rom onto the sd card (or virtual sd card as I believe it is in this case) of my HTC One. I don't know how to accomplish this. I cannot browse the internal memory of the HTC One through my computer- whether it is in boot mode, recovery mode, or just booted regularly with USB debugging on or off. How do I get the actual zip ONTO the device?
The main thing I want to accomplish is to remove blinkfeed and change the theme of my device to be more minimalistic. I'm sure I can find a rom out there that does this, I'm just running into problems with this particular step. Should I be able to browse the memory of my device via the PC, or is there a different method of getting the zip onto my device entirely?
Thank you for the help
Click to expand...
Click to collapse
You've done the hard parts unlocking the bootloader and rooting the device. Assuming you have custom recovery installed like TWRP or CWM, flashing new roms is easy in comparison.
You can download these rom zip files directly to your phone off a browser link or FTP or google drive and all those downloads should default to your downloads directory on your storage. You can store them basically anywhere but I created a folder in the main directory to store all my custom rom and kernel zip files and gave it a name I remember. Then when you flash the rom you have to enter custom recovery first, and from there find that directory, pick whatever zip you want to flash and do it. The exact step by step process is more detailed but thats what the online instructions and tutorials are for, i found youtube really helpful because you get to see exactly what they are doing step by step and then after that, its easier to following the vague sounding text-only instructions in the threads here, which can sound a little cryptic for noobies
Sent from my Nexus 7 using Tapatalk 2
getting rom onto phone
Assuming you already downloaded the ROM zip onto your computer and are connected to your phone via USB cable
...go to the ROM zip on the computer,
R click on the ROM zip that should bring up a box with multiple options
somewhere in that box should be option to Send To and find HTC One,
click on it and you will be good to go,
it may also bring up an options box about "...this file contains media files, should media files be sent to media section of phone" choose No
Boot into recovery follow dev's reco for flashing ROM
Hope this helps
Related
I've seen a number of requests for this functionality and recently it became necessary for one user who had a disabled Home Key to clear cache and data without the use of ClockworkMod. I have reserached two methods to address this issue. These instructions require some familiarity of android, computer and tablet terminology and usage. Feel free to ask for clarifications in comments. Here we go...
Method I - Stock Recovery Command File
Technical: Stock Recovery command file can be used to perform a few additional functions as well as to alter the path to update files. These commands will execute with all privileges available to recovery mode.
Advantages: Very easy to use. Very little technical knowledge required. No third party software is required for use.
Prerequisites: You will need a MicroSD card formatted FAT32 and a method for transferring files from your computer to the MicroSD.
Usage:
1) Prepare a text file named "command" (no file extension) with one of the following commands on a single line. The wipe data command will wipe both data and cache. Wipe cache will wipe cache only.
--wipe_data
--wipe_cache
2) Place the file in a folder named "recovery" in the root directory of your MicroSD card.
3) From a powered down state, insert the MicroSD card into your tablet and boot into recovery by powering it on while holding down the Volume Up key.
4) Allow the command to execute completely then the tablet should reboot (this may not occur automatically depending on firmware installed).
Method II - Updater Script
Technical: The attached "Updater Scripts" perform delete commands (recursively if necessary) on the named directory or file(s). The directories are mounted automatically by the system before the script executes but it could be easily revised to include that step if necessary. The partitioning, formatting and directory structure are left untouched. Only files are deleted.
Advantages: No third party software is necessary for execution. Relatively easy to modify for more surgical precision (i.e. leaving installed apps but clearing possibly corrupted system data). Included example: "Clear Battery Stats"
Prerequisites: You will need a MicroSD card formatted FAT32 and a method for transferring files from your computer to the MicroSD.
Usage:
1) Download the attached archive (ClearData.zip) to your computer.
2) Extract the files to your computer. You should then have a folder named "recovery" (which contains a file named "command") and an additional archive named "update.zip"
3) Place the recovery folder and the update.zip in the root directory of the MicroSD card.
4) From a powered down state, insert the MicroSD card into your tablet and boot into recovery by powering it on while holding down the Volume Up key.
5) Allow the script to execute completely then reboot the tablet (this may occur automatically depending on firmware installed).
This will become handy someday.
Thanks for sharing your knowledge.
You're welcome. One quick note... the new stock recovery adds a menu simiilar to ClockworkMod. These methods will still work since the recovery folder/command file are checked first but it really isn't as necessary any more.
Need Help
Tried both methods above but either way I get to the viewsonic splash with the message "Booting recovery kernel image" in the upper left and it just stays there, stuck there, I left it for a long time to see and it never leaves that screen.
Any ideas?
Me too
I can't get into clockworkmod either. My machine is running faster. I almost hate to mess it more.
lrgche said:
Tried both methods above but either way I get to the viewsonic splash with the message "Booting recovery kernel image" in the upper left and it just stays there, stuck there, I left it for a long time to see and it never leaves that screen.
Any ideas?
Click to expand...
Click to collapse
That's an indication that you may have more serious problems. nvflash will be required. http://forum.xda-developers.com/showthread.php?t=861950
Once done you will likely need to install ClockworkMod and repartition your internal storage.
Loukoebel said:
I can't get into clockworkmod either. My machine is running faster. I almost hate to mess it more.
Click to expand...
Click to collapse
If your tablet boots properly but you can't get into CWM then it probably isn't installed properly (or at all). http://forum.xda-developers.com/showthread.php?t=865245
Keep in mind that CWM is NOT compatible with all ROMs. Make sure the developer for your chosen ROM recommends it before installing it.
Does your method in opening post have to be run from external micro sdcard?
Both methods are performed with an external MicroSD card. They will work from internal also but it is a little more difficult to get the files in place if your tablet is not booting properly.
K J Rad said:
Both methods are performed with an external MicroSD card. They will work from internal also but it is a little more difficult to get the files in place if your tablet is not booting properly.
Click to expand...
Click to collapse
so your method is a simple way to replace one of the main uses of Clockword MOD?--Plus you stay stock more or less.
That is correct. Method II can also be modified to be less intrusive (leave user apps installed) or embedded into update scripts to perform a wipe during new ROM installs.
K J Rad said:
That is correct. Method II can also be modified to be less intrusive (leave user apps installed) or embedded into update scripts to perform a wipe during new ROM installs.
Click to expand...
Click to collapse
Wipe data does what--remove the apps installed?
And the partitions?
Your post is very interesting. It implies that you have a knowledge of the g-tabs partition structure. I have played with Linux off and on for the last 10+ years. When I began, I used Slackware and when you set it up you had to manually create partition tables using fdisk. You were only required to create two - the data partition and a swap partition but it was often recommended that you create several others - one to contain the home directory to prevent users from using all the disk space (in the days of small disks) for example. It appears that there are a lot of partition on the g-tab. Up to now, I have used various wiping tools like clockwork or calkulins wipe all on faith. I would really like to know what all the partitions are and what is in them. I have used terminal to get to the root folder and tried to do an fdisk to display the partitions but try as I might everything remains hidden. It would seem that a script like yours could be adapted to do many things but I would certainly want to understand the structure a little better before I did anything. I have searched and been unable to find that information. Can you point a way for the curious to learn more about the partition structure on the g-tab?
Wish I had a direction I could point you in. What I've found so far has mostly been stumbled upon while looking for something else. What I can tell you is this...
1) When using fdisk in Android you must specify the device to look at. Try something like: fdisk /dev/block/mccblk3 That should list the current partitions as defined by CWM or whatever was used originally.
2) Within one of those partitions in the list generated above are sub-partitions holding the bootloader, system, data, etc partitions. You can see how they're described in the .cfg files in the nvflash restores that are lying about.
lsu205 said:
Wipe data does what--remove the apps installed?
Click to expand...
Click to collapse
Removes user apps and their associated data as well as system related data and settings.
K J Rad - any idea if the partition size can be set with these methods (2048 & 0) in case I can't get clockwork installed?
CodeNamePapa said:
K J Rad - any idea if the partition size can be set with these methods (2048 & 0) in case I can't get clockwork installed?
Click to expand...
Click to collapse
I'm looking for a solution to that problem. Unfortunately these methods still require the ability to get into recovery mode which likely won't work if you're having trouble getting CWM installed.
If, however, you can get into recovery... then it is theoretically possible to create a script that would accomplish that. As soon as I have one I'll be adding it to the mix ;-)
Edit: I've found something I think will work. Will do some testing tonight. It will still require access to recovery.
I wasn't sure if you saw my other post but I am seeing no partition 0 when I NVFlash with a verifypartition.
http://forum.xda-developers.com/showpost.php?p=13059520&postcount=57
I haven't yet but I will. Let's try to keep this thread on topic. Thanks.
More thoughts:
because I went w/ cyan7 is it possible i have a "bad" kernel and that the stock bekit-1105 or the roebeet-3588 files are crashing w/ the kernel in place already?
I know custom ROMs can have a custom kernel applied separately, but I have no idea whether cyan7 loads it's own kernel...
I have yet to try the nvflash_gtablet_46 version, as I see the img files w/in are different from the original 1105 .zip
Also:
read on another thread that part 2 and part 3 aren't loading for other users when doing nvflash - I did notice that it pauses, runs some stuff, then starts loading part 4 through to the last part, then success. - do part 2 and 3 run for you?
edit: I see a 4349 downgrade.zip in another thread for those who got the OTA update but want to go back to stock 3588 prior to jumping off somewhere else - I can't expect that would help me as I can't do squat w/ recovery yet, but could that possibly "reset" any bad kernel problems? - again, I'm just thinking out loud.
This is well outside the scope of this thread but I find some of what you mention interesting so I'll address it and then end any further off topic discussions.
I did not build nor have I ever used Cyan7 so I have no basis for an opinion on the matter other than this... Each ROM comes with a kernel installed so if properly done an nvflash should overwrite any "bad" kernel.
Part2 and Part3 do indeed load, they are just displayed differently than the other Parts. Just minutes ago I flashed down from Mountain Laurel (4349 based with the new bootloader and recovery) with absolutely no trouble. I can, and have, read back those partitions after an nvflash to prove that point.
The 4349 downgrade will only work for you if recovery is working. Having never used it I don't know that it would "reset" the kernel but any subsequent flashing of a new ROM image would.
I am working on a stock recovery solution for partitioning but it isn't likely to help anyone who is stuck in an APX loop. I do have some ideas on what might help for that condition but I haven't been able to get my hands on one for testing and trying to help people here is like being a consulting mechanic for a car repair that's in someone else's shop having work done on it that you're not being told about.
I'll be happy to address any further comments or questions regarding your specific issue in an appropriate thread or via PM. Thanks.
To someone who has not worked with tablets before, but has good computer knowledge. I sure would like to see (even pay for) a step by step from the beginning of a stock updated gtab, rooting to loading roms. Are we supposed to z4root, clockwork, backup, just load a rom. The guides are great that are here, but none of them are consistant. I could eventually after several months make heads or tales, sure would like some opinions and how will this effect the fact that we know honeycomb is coming I assume, What is the stable rom to use?
Thanks for your consideration.
I feel your pain. I recently received my $279 gtab. I needed to put it to use right away and was afraid to flash it until I had more time to study the issues involved.
It took me a few days to figure out what to do. I ended up installing the Vegan 7 ROM using Clockworkmod 8.
This post was the most helpful:
http://forum.xda-developers.com/showthread.php?t=865245
There is another one I cannot find now, but author also has a blog with some instructions (google search fugatech)
Some more info to install CM8:
http://forum.xda-developers.com/showthread.php?t=865017
I installed clockworkmod on my external sdcard (sdcard2). I used the sdcard slot on my computer to transfer files to sdcard2 of my gtab -- just like you would a thumb drive -- by unzipping the downloaded file directly to the sdcard
I partitioned as explained and deleted caches that mentioned in cwm menu items
I used cwm to connect my gtab to my pc via usb. I used my pc to create a folder on gtab intermal storage (sdcard) named "ROM." I then copied the whole vegan zip file to the ROM folder
There is a menu item in cwm that will flash your rom. All I needed to do was to browse to the zip file I copied to the rom folder and let it do its work
I didn't have to do the market fix
Went to Market and downloaded latest flash player.
The whole thing takes only a few minutes once you are ready. Once you hace CWM installed and see the menus things will be come clearer. I suggest you forget about the ROMs and just install Clockworkmod and take a look at it. Then go get Vegan 7.
It seems a lot of time is spent, and threads created, by people just trying to figure out where to start.....especially considering that the process itself is very simple.
Well, I am new to this forum because I recently bought a Galaxy Player. This is my first Android device and I have rooted it using SOC. I have installed clockworkmod but there is no option for the Galaxy Player. I have downloaded the ICS rom for the 5.0 USA version and I am just a complete noob to custom roms. Can anyone direct me to a goods tutorial on this or just a quick rundown on how to do it, I am just a really confused 14 year old... Thanks
mrjaredbeta said:
Well, I am new to this forum because I recently bought a Galaxy Player. This is my first Android device and I have rooted it using SOC. I have installed clockworkmod but there is no option for the Galaxy Player. I have downloaded the ICS rom for the 5.0 USA version and I am just a complete noob to custom roms. Can anyone direct me to a goods tutorial on this or just a quick rundown on how to do it, I am just a really confused 14 year old... Thanks
Click to expand...
Click to collapse
just pretend you didn't do any of that and...
1. download odin3 v1.3 (windows application)
2. download the samsung usb drivers and install them, i can't remember where i got them
3. plug phone into usb, turn off while plugged in, turn back on while holding volume down (maybe it was up?)
4. go into odin and click the pda button and select...
5. this file and press "start" (i think that's what it's labeled)
6. the phone will reboot itself back to normal
7. copy this zip onto your sd.
8. turn the phone off, and turn back on while holding volume up
9. back that **** up, i dunno what the hell it's labeled
10. wipe data/cache/dalvik (dalik is under advanced)
11. choose to install zip from sd, choose the "this zip" from step 7
12. choose install from zip again -> ICS ROM you downloaded
13. reboot, try out ICS for 2 seconds
14. turn off, boot into recovery (the volume up + power **** we keep doing)
15. install from zip -> Google Apps zip
16. reboot and enjoy ICS and google apps and all the other cool stuff the internet has to offer
Thanks! Very well written, I'll try it out later tonight.
I have installed it successfully, however I don't think it detects my internal SD card. Do you know why that is?
mrjaredbeta said:
I have installed it successfully, however I don't think it detects my internal SD card. Do you know why that is?
Click to expand...
Click to collapse
idk what you mean by "it" nor do i pay attention to my internal at all since i have 32gb external
I meant the device doesn't detect it, and I do not have an external at the moment.
mrjaredbeta said:
I meant the device doesn't detect it, and I do not have an external at the moment.
Click to expand...
Click to collapse
yeah, idk i haven't even noticed so i'm not the person to ask i guess.
mrjaredbeta said:
I have installed it successfully, however I don't think it detects my internal SD card. Do you know why that is?
Click to expand...
Click to collapse
This is why you should always read the entire post when you download a ROM. That issue is mentioned several times through the thread, and it has yet to have been resolved to the best of my knowledge. But always look into what your flashing, otherwise you'll probably end up with a really shiny paperweight on your hands.
Yes, I should've looked at the whole thread but I f'd it up badly now... So, I read what you said about the "SD card problem in the thread" and I took a look and saw that you had to switch around /emmc (I think?) and /sdcard around in the vold.fstab file in the /etc directory. SO, I was stupid and extracted the whole .zip of the ROM, changed the contents in the vold.fstab file, re-zipped it up, and tried to flash it again. Unfortunately, I tried to flash but this is what CWM Recovery said:
-- Installing: /emmc/ICS/3-31.zip
Finding update package...
Opening update package...
Installing update...
Installation aborted.
... It's probably because the signature verification failed (because of no signature). And I was also being so stupid as to deleting the original ROM off of my SD card... I also note that I am doing this all from an internal, I do not have an external... This is what I am going to:
Get an external microSD and microSD reader for the PC
Put the original ROM on it
Flash it from the external
I am guessing that it would work from that way, as I probably f's up the internal. Can someone clear this up? Will this method work?
Disregard my last post, I am all set back to the stock ROM with no problems. Anyways, thanks for the support, and I will always try to look at the whole thread before flashing a new ROM.
Here
Check here this forum has a lot of custom roms for the SGP player and a lot of smart people who explain it as good as M.I.T.
http://forum.xda-developers.com/forumdisplay.php?f=1423
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 and thanks for reading / helping if you can.
In brief, I have a Samsung Tab 2 GT-P3110 tablet which was running android 4.2.2. It's main use was as a controller for my sonos sound system which no longer supports my device. I thought I'd try and update it rather than simply chuck it into landfill for no good reason other than it was old like me! I know almost nothing about what I am doing, sorry!
So far I have I think 'rooted' the device using something called odin, and installed the clockwork recovery mod. I have also installed the Samsung drivers onto my PC and I have on my pc a zipped file which I believe will install a newer version of android (perhaps some guidance might be required for best file to go for). Unfortunately I am unable to see my tablet's sd card (or anything to do with the tablet) when connected to my pc via USB in order to copy it. Moreover I have copied the same file to a micro sd card but when I put this directly into the tablet and try and boot off the external card I get an access error and the card is not read.
I am out of ideas now and wonder if one of you clever people might be able to help me? I think I read somewhere about having to switch on USB debugging and USB sharing or the like BEFORE rooting. The instructions I used only mentioned the former and so that's all I did. Maybe I've locked myself out for good.
Thanks again, Pezos
Blimey, I really must have killed it! Surely someone out there can help me fix it?