A unique set of problems - Sprint HTC EVO 4G LTE

I have come to what seems to be the end of a very unique set of misfortunes. I was keeping my phone stock for as long as possible, to avoid running into these issues (I don't have any "backup" phones), but being sent on travel for work and staying in a hotel with no Internet forced my hand. I needed to be able to tether my phone.
I went about unlocking the bootloader and after booting into TWRP, I immediately made a backup. I then flashed the necessary zip file to acquire root access. After successfully rooting it, I was able to achieve wireless tethering via Wireless Tether for Root. However, I did not want to deal with the power drain and possible latency/bandwidth degradation of a wireless connection, so I began the process of flashing a custom ROM (MeanROM).
After laboriously acquiring the ROM zip via Panera Bread wifi and placing it in my external SD card, I booted into TWRP to attempt to flash it. While trying to flash a ROM, I ran into some problems and was able to successfully restore from the backup I had made. I attempted to flash MeanROM, however, and received a failure message. The zip program was unable to open the file.
After reading up a bit more, I decided to wipe cache, dalvik cache, and perform a factory reset and system wipe. These operations did not enable me to successfully flash my ROM. They did, however, result in corrupting my internal SD card partition, resulting in the loss of my backup. What I mean by this is that there are several messages about "failed to mount /sdcard (Invalid argument)" in the log. The next step was to try to reformat the internal SD card.
I discovered that the busybox install provided did not have the ability to do what I needed, so I went about pushing a newer version onto my phone using adb push. The exact command I ran (copied and pasted from my terminal) was this:
Code:
sudo ./adb-linux push busybox /sbin
This had the unfortunate result of assuming /sbin was the new name of the busybox file on my phone, thus overwriting my /sbin folder with a file. Now, when I try to run adb shell, I get the nasty message
Code:
- exec '/sbin/sh' failed: Permission denied (13) -
So! Does anyone want to undertake the task of trying to help me?

After another Factory Reset and reboot, I was able to get past that last error message and can now adb shell in again. Hopefully I'll just be able to re-download the (or another) ROM and get that flashed.

Aaaaaaaaaaand I just learned about this: Enable WiFi Hotspot and USB / Bluetooth Tethering on the EVO 4G LTE
Note to self, do more reading.

elead1 said:
After another Factory Reset and reboot, I was able to get past that last error message and can now adb shell in again. Hopefully I'll just be able to re-download the (or another) ROM and get that flashed.
Click to expand...
Click to collapse
That would be my suggestion. Make sure to check the md5 on the rom download, especially on questionable wifi networks.
Sent from my EVO LTE

Definitely a bad download. Also, you must be on twrp 2.2.1 to install the latest MeanRom. With the addition of GoogleNow to the rom it has grown to over 600mb and the older versions of twrp seem to fail more often than succeed during install. If you want to use usb tether, you probably should bite the bullet and buy PDAnet. It is by far the best and most reliable method of USB tether. You won't be able to get it in the market though, you will have to get it directly from their website: http://junefabrics.com/android/
I've been using PDAnet for 3 years now and you don't have to be rooted to use it. PDAnet's latest version offers wifi and bluetooth tether now, but unfortunately it doesn't work on HTC phones because it uses FoxFi for its wireless tether which doesn't work on HTC phones.

Related

[HOW-TO] Wifi Fix for CM6 [1/2/2011]

DISCLAIMER: Nobody -- and I do mean nobody -- is responsible for a bricked device except for the person attempting this modification. Do not contact me to complain that you borked your Slide by not following instructions.​
All credit for this discovery goes to knowmercymod​
Certain Espresso owners running CM6 (or CM6 derivatives) may have discovered that their wifi functionality doesn't work as expected. The issue is well-documented on the CM6 issue tracker [issue 2153] and the cause of the problem is known, but there is no source-based solution at the moment. As such, there's no easy way to distribute a fix for working wifi within a packaged CM6 zip.
The issue relates to missing GPL'd drivers for the MSM7227 chipset from Qualcomm that is used in several devices, most notably the HTC Espresso, Legend and Aria. But due to small versioning differences in certain aspects of this chipset, some devices have functioning wifi using the generic open-source SDIO modules and others do not. The permanent solution for this issue is cajoling HTC into releasing this code -- this process is already underway -- but, in the meantime, this thread will serve to provide a temporary solution that is 100% effective.
So let's get started...
Step 1: Downloading the necessary files​
Attached to this post are the two files necessary to fix this issue:
sdio.ko
tiwlan_drv.ko
They both come from *stock* Espresso -- the code currently in use in the CM6 repository does not generate fully-functional versions of these modules.
Download the "modules.zip" file to your PC and extract the two files to an easily accessible location.
Step 2: Backing up the corresponding files on your device [optional]​
This optional step will walk you through backing up the existing files on your device. This is completely unnecessary as those files can simply be restored by re-flashing a CM6 zip, but I figured that people should get in the habit of backing up stock files before modifying their device.
To do so, execute the following two commands -- both can be done while the phone is booted up or in recovery (if you're in ClockworkMod recovery, just make sure your system partition is mounted -- partitions->mount /system):
Code:
ADB PULL /system/lib/modules/tiwlan_drv.ko [DESTINATION]
ADB PULL /system/lib/modules/sdio.ko [DESTINATION]
To use my PC as an example, I would connect my Slide via USB and enter the following commands on the command line:
Code:
ADB PULL /system/lib/modules/tiwlan_drv.ko ~/Documents/Android/Backup
ADB PULL /system/lib/modules/sdio.ko ~/Documents/Android/Backup
Step 3: Replacing the files on your device​
So now we're ready to make the actual modification. First step: boot into recovery. My preferred method is to use the ADB REBOOT RECOVERY command.
Once you're in ClockworkMod Recovery, please make sure system is mounted -- partitions->mount /system
Then you would simply execute these two commands:
Code:
ADB PUSH [SOURCE]/tiwlan_drv.ko /system/lib/modules/tiwlan_drv.ko
ADB PUSH [SOURCE]/sdio.ko /system/lib/modules/sdio.ko
To use my PC as an example, I would enter the following commands on the command line:
Code:
ADB PUSH ~/Downloads/modules/tiwlan_drv.ko /system/lib/modules/tiwlan_drv.ko
ADB PUSH ~/Downloads/modules/sdio.ko /system/lib/modules/sdio.ko
Once you've pushed these files, simply reboot your device and you're done! You should no longer have any issues with your wifi connectivity, including (but not limited to) full wifi tether functionality when using the Wireless Tether 2.0.5 application.
And, again, all credit for this temporary fix goes to knowmercymod (who is far too humble to post this himself).
Saving this space for future updates...
I hope this fixes my frequent disconnects, but on the legend section they fixed the problem by changing the channels to 14 instead of 11, not sure if that will work for espresso.
UPDATE: Works great! Thanks for posting this.
Very exciting news! I'll fully charge and try this fix. Looking forward to using CM instead of stock.
Just pushed the files to cyanoginger 1.1.. wifi and wifi tether both appear to work perfectly now
Cool, thanks for posting!
I did it, not sure if it did anything. Weird thing is, after pushing the 2 files I noticed I forgot to mount the system folder but it said it transfered successfully.. *shrugs*
I think tethering was working before, either way though, it works now
Awesome! Thanks so much for the hard work. I know you guys will manage a perm fix via a regular rom soon. HTC will cough up that source code for ya
Just chiming in to say this works for me. Takes a little longer now to connect to an access point than it used to, but rock solid after that. With s-off, didn't even have to be in recovery, just mounted system rw, pushed files, and rebooted.
Sent from my MyTouch 3G Slide running CM6.1.1
Did it right off my phone with sufbs file manager. Great job hopefully its integrated in next cm build.
I keep getting a "out of space" error when I go to copy the files.
Please help.
poormanq45 said:
I keep getting a "out of space" error when I go to copy the files.
Please help.
Click to expand...
Click to collapse
If you have not applied s-off patch by alpharev, then you have to push the files while in clockwork recovery, after going to the partitions menu and selecting mount /system. If you are in fact s-off, you have to use a terminal emulator and type [code}mount -o rw,remount /system[/code] and then push the files
Sent from my T-Mobile myTouch 3G Slide
CM6 wifi works fine for me, but would these drivers work better with my phone anyways since they're specifically made for this phone?
Applied this on Arayaray revamped which seemed to have spotty wifi for me especially when accessing the market. After applying this the wifi is perfect not a single problem at all now, thanks so much!!
I refuse to connect my phone to my pc. Is there any way to get these files pushed onto my phone? Terminal Emulator work? If not, it's cool. Wifi seems to be working for the most part under CM6.
xaodxkevin said:
CM6 wifi works fine for me, but would these drivers work better with my phone anyways since they're specifically made for this phone?
Click to expand...
Click to collapse
It depends. These files are taken *directly* from the stock espresso rom and are known-good. If you're not having any issues with wifi running CM6 I don't feel comfortable telling you this will "improve" anything -- but I don't think it would hurt. In any case, if you follow my instructions you will have backed up the original files and can restore them at any time.
Hayzie said:
I refuse to connect my phone to my pc. Is there any way to get these files pushed onto my phone? Terminal Emulator work? If not, it's cool. Wifi seems to be working for the most part under CM6.
Click to expand...
Click to collapse
Uhhhh -- why? That seems incredibly myopic and weird. You know what -- never mind -- I don't want to know. You can use a terminal emulator on the device to move the two files from your sdcard to their rightful place on /system. I'll leave it as an exercise to the user to figure out the correct commands to do so.
Well I'll tell you anyways... MyTouch Slide always acts funny when plugged via USB to my pc, more-or-less so Windows 7. I could say this is an uncommon issue, but it's not. So it's not weird.
Mine works just fine, whats funny about it when u plug it in? Sorry to bring this up here herbrewtoyou but im curious lol
Sent from my T-Mobile myTouch 3G Slide using XDA App
Hey guys I just pushed the 2 files to my phone, I'm running CM 6.1.1-Slide - since I flashed to 6.1 and then reflashed to 6.1.1 I have had 0 Wifi capability. So I push these files and followed the instructions, and well I still have no wifi. I will enable it and it will scan, try to authenticate and then disconnect and repeat.......any ideas???
ApeMan911 said:
Hey guys I just pushed the 2 files to my phone, I'm running CM 6.1.1-Slide - since I flashed to 6.1 and then reflashed to 6.1.1 I have had 0 Wifi capability. So I push these files and followed the instructions, and well I still have no wifi. I will enable it and it will scan, try to authenticate and then disconnect and repeat.......any ideas???
Click to expand...
Click to collapse
Sounds like an issue with your router...
No its def not the router, phone would connect all day long before switching to CM.

Partially functional Atrix - Need Assistance or SBF File

So I as working on theming the Adeo ROM and must have messed something up. I didn't think it had to do with the framework files I had pushed so I did a factory reset to clear off all the 3rd party apps from the phone.
Well, since that reset, I can't access the phone in ADB, settings FC's, Market FC's, and I can't download/install an APK because of the security restrictions.
The phone is "functional", I can place/receive calls/sms and use the browser. USB to the PC works for everything except getting ADB access. I verified I can get it to recognize for RSDLite and for Fastbook so I figure using one of those methods should (eventually) provide me an avenue to get my phone 100% functional again.
Does anyone happen to have or know where I could find signed files for Fastboot to replace the entire /system partition or an SBF file to flash the phone back to stock? Or possibly any other solutions?
Also, before I get flamed as a n00b who broke a phone, I've worked on over a dozen different Android handsets and I was well aware I was working without a safety net. This is NOT my primary phone so if I need to I can patiently wait for an SBF to leak. I'm just checking to see if anyone knows any solutions already so I can get back to theming.
Sounds to me like a permissions issue. I had that after I fiddled with the contacts database to unrestrict pictures from third party apps. I would double check any files you modified and make sure they got chmod'ed back to what they should be.
You will have to somehow access the Settings to re-enable adb. When you did a factory reset, you disabled USB Development (aka adb).
For now the only known way to recover is through adb. No fastboot or signed update.zip for now.
navalynt said:
So I as working on theming the Adeo ROM and must have messed something up. I didn't think it had to do with the framework files I had pushed so I did a factory reset to clear off all the 3rd party apps from the phone.
Well, since that reset, I can't access the phone in ADB, settings FC's, Market FC's, and I can't download/install an APK because of the security restrictions.
The phone is "functional", I can place/receive calls/sms and use the browser. USB to the PC works for everything except getting ADB access. I verified I can get it to recognize for RSDLite and for Fastbook so I figure using one of those methods should (eventually) provide me an avenue to get my phone 100% functional again.
Does anyone happen to have or know where I could find signed files for Fastboot to replace the entire /system partition or an SBF file to flash the phone back to stock? Or possibly any other solutions?
Also, before I get flamed as a n00b who broke a phone, I've worked on over a dozen different Android handsets and I was well aware I was working without a safety net. This is NOT my primary phone so if I need to I can patiently wait for an SBF to leak. I'm just checking to see if anyone knows any solutions already so I can get back to theming.
Click to expand...
Click to collapse
When I lost ADB access because of a hard reset (I think), this is what I did to fix my issue: http://forum.xda-developers.com/showthread.php?t=974824
I never lost root after a hard reset so I went to the market and bought root explorer and sqlite editor and copied the adbd to the /sbin folder to fix adb. I then bought sqlite editor and followed this: http://forum.xda-developers.com/showthread.php?t=972760 to re-enable side loading of apps. To install apps that I had the apk's for.
I still lose adb after a reset, but I can copy the adbd file to the /sbin folder and adb works again until I reset the phone.
I made a post about losing adb access on the motorola support forums: https://supportforums.motorola.com/message/332307#332307 to see if there were any solutions, but Mark said he would get back to me after trying to reproduce my problem.
I hope this helps.
I think I'm just up **** creek without a paddle for the moment because I can't connect via ADB, the Market force closes, and the security restrictions won't let me side-load any applications via download from the browser. I can't manually add ADB because I have no way to move the files to where they need to be.
Thanks for the replies! airbillion, I'm following your thread at the Motorola Owners' Forum to!
navalynt said:
I think I'm just up **** creek without a paddle for the moment because I can't connect via ADB, the Market force closes, and the security restrictions won't let me side-load any applications via download from the browser. I can't manually add ADB because I have no way to move the files to where they need to be.
Thanks for the replies! airbillion, I'm following your thread at the Motorola Owners' Forum to!
Click to expand...
Click to collapse
No problem. That sucks, I'm not sure what you can do. Hopefully motorola or someone here will get a sbf soon so we can mess with our phones and have a way to fully recover. I hope you get it working again. Good luck!
navalynt said:
I think I'm just up **** creek without a paddle for the moment because I can't connect via ADB, the Market force closes, and the security restrictions won't let me side-load any applications via download from the browser. I can't manually add ADB because I have no way to move the files to where they need to be.
Thanks for the replies! airbillion, I'm following your thread at the Motorola Owners' Forum to!
Click to expand...
Click to collapse
Have u not tried sideload wonder machine love that thing used it alot when my wife had her backflip
Sent from my MB860 using XDA App
shadowscreation said:
Have u not tried sideload wonder machine love that thing used it alot when my wife had her backflip
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Requires USB Debugging to be enabled, but I have no access to enabled it due to Settings force closing and no ADB access in pre-boot.
Could you download Android Terminal Emulator 's apk to your sdcard, then install it using a apk install you may already have that work.
If you can get any terminal access from your phone, do a su, then launch /sbin/adbd. This should hopefully give you adb shell access. Without needing to enable USB debugging.
adlx.xda said:
Could you download Android Terminal Emulator 's apk to your sdcard, then install it using a apk install you may already have that work.
If you can get any terminal access from your phone, do a su, then launch /sbin/adbd. This should hopefully give you adb shell access. Without needing to enable USB debugging.
Click to expand...
Click to collapse
It won't let me install a downloaded APK because of the security restriction.
If you have an SD card, try booting into recovery with an update.zip on the file.
I can get into the recovery, but the update.zip file needs to be signed. I created one that will push the original copies of the framework files I was working with but it won't install because it's signed with test keys. The stock recovery 3e needs update.zip files signed with the manufacturer release-keys which only Motorola has.
https://supportforums.motorola.com/thread/46051?tstart=30
I started a thread on the official Motorola Owner's Forum in hopes I can find a full factory restore method for the OS. It's unfortunate that unlike HTC and other manufacturers who release full wipe RUU files Motorola has chosen to keep their restore files internally.
http://www.4shared.com/file/7YXo_gmO/update.html
That's the link to the update.zip file I was trying to use that fails because it's only signed with test-keys.
Retracteddd

[SOLVED] Upgrade Fujitsu Arrows F-01D to ICS

Firstly a big thank you macexplorer who again found the relevant links amongst much Japanese.
See the original thread on rooting the F-01D:
http://forum.xda-developers.com/showthread.php?t=1611484
Following are quick instructions on how to upgrade the device to ICS. All your data will remain intact, but the /system partition is completely wiped.
NB: YOU WILL LOSE ROOT IF YOU FOLLOW THESE INSTRUCTIONS. YOU WILL NOT GET ROOT BACK.
To be clear, at the present moment in time, you need to CHOOSE BETWEEN ICS OR ROOT, you can't have both. The official upgrade below completely reflashes the system partition, so tools like OTA RootKeeper will not help you. The new release is more secure than ever and at current we don't know a new way to get root. If anyone finds any new information, please speak up
DISCLAIMER: Following these instructions might brick your device, void your warranty, etc. This is unlikely since you're basically installing an official update, but to be clear, I disclaim any and all responsibility for any (permanent) damage that might be caused by these instructions. DO AT YOUR OWN RISK.
The original instructions are here (or see in Google Translate)
http://spf.fmworld.net/fujitsu/c/update/nttdocomo/f-01d/update1/top/index.html
My instructions are slightly different, aimed at more advanced users, and serves the file direct from my server (I found the original server quite picky in terms of refer and user agent, and also slow. I'm also serving the unzipped version, since compression was 0% anyways).
PRE-REQUISITES
At least 50% battery (ideally more in case things go wrong...).
Settings -> About, make sure Android version is 3.2, and Build number is either V28R43A (as recommended on the official page) or V19R36D (what I had; it worked for me but YMMV).
Settings -> Storage, at least 1.5 GB free in "Built in storage" (try installing first to external SD card and let me know if it works.. it's a lot safer).
ICS UPGRADE FOR F-01D
Download F01D_TO_SP_ICS1.enc and put it in /sdcard (md5sum: 2014d0254568a4ef955b21476012a9b5)
Boot into recovery (power off, hold down both volume keys and power up), select "update firmware" and press the power button agin.
Pay attention... the first time I tried this, it rebooted back in to recovery part way.... if this happens, just repeat step 2 above and make sure the progress bar completes all the way.
After this, it will reboot a few times, don't worry. Boot 1 will do the "optimizing android apps" screen, Boot 2 will be "upgrading calendar, contacts, etc..." and Boot 3 will say "finishing upgrade" and let you use the system.
If anyone has any leads on re-rooting the device, speak up. From my initial observations security is tighter than ever, so this might be a problem... but there are clever people out there
Regarding root
No leads for now. We can create /data/local.prop using the ICS/JB restore technique, but unfortunately the new firmware is completely ignoring either this file or the ro.kernel.qemu property.
If I understood the google translated Japanese correctly, this guy got to the same conclusion, and is now looking for other solutions. I wish him luck because after spending the day on this I have to get back to my real work
http://blog.huhka.com/2012/09/arrows-tab-lte-f-01d-icsshell-root.html
Temporary Root
This link in xda works to get a temporary root:
http://forum.xda-developers.com/showthread.php?t=1886310
i think to get permanent root, need the lsm_disabler.ko for ICS kernel.
Update:
ICS kernel has blocked loading kernel modules; so cannot insmod a custom kernel.
so cannot remount /system, and cannot get permanent root..
shame on the dandroids..
Post upgrade restart errors?
Hi, slightly off-topic but related - has anyone had issues after upgrading with google maps? Whenever I start google maps it will hang and then restart my tablet.
Essentially google maps is now unusable which is very annoying. Please let me know if anyone has experienced this too and if so if they have a solution to the problem.
Many thanks in advance!
I lost boot after upgrade the device to ICS :crying:
anyone help me repaid boot
Thanks:laugh:
longdau12 said:
I lost boot after upgrade the device to ICS :crying:
anyone help me repaid boot
Thanks:laugh:
Click to expand...
Click to collapse
Help me :crying:
macexplorer said:
This link in xda works to get a temporary root:
http://forum.xda-developers.com/showthread.php?t=1886310
i think to get permanent root, need the lsm_disabler.ko for ICS kernel.
Update:
ICS kernel has blocked loading kernel modules; so cannot insmod a custom kernel.
so cannot remount /system, and cannot get permanent root..
Click to expand...
Click to collapse
FINALLY..ROOT on F-01D for V08R31A
I hope someone is still using the F-01D. So here's to you diehards.
After many many failed attempts, i finally managed to get a more permanent root.
Probably others have got this to root, but I havent seen anything come up via searches.
Main stumbling block has been in getting the address of 'ptmx_fops'. Finally got it thro, rootkitXperia_20131207.zip (get_root..this prints but fails in ptrace; ptrace is blocked in f01d)
I have just managed to get a permanent root. The steps maybe little approx. Do verify and let me know. Its non-destructive, so no harm done.
but do at your own risk..and other standard disclaimers apply
Steps:
1. do the temp root as per : http://forum.xda-developers.com/showpost.php?p=33071441&postcount=3
2. get the exploit source from https://github.com/fi01/unlock_security_module
(recursive download)
3. compile the source. this will generate a libs/armeabi/unlock_security_module binary
4. add the following recs to the device_database/device.db
these are kallsyms kern func addresses; most are avail direct from kallsyms, except for ptms_fops.
Code:
sqlite3 device_database/device.db
insert into supported_devices values(187,'F-01D','V08R31A');
insert into device_address values(187,'commit_creds',3221986012);
insert into device_address values(187,'prepare_kernel_cred',3221985196);
insert into device_address values(187,'ptmx_fops',3229222484);
insert into device_address values(187,'remap_pfn_range',3222251308);
insert into device_address values(187,'vmalloc_exec',3222293708);
5. push device.db and unlock_security_module to /data/local/tmp/
6. simply run from /data/local/tmp: ./unlock_security_module as the root obtained temp earlier.
7. after sometime, this will say LSM disabled!!
8. now remount /system as rw. carefully copy su binary to /system/xbin/ (pref use the latest version from SuperSu).
Also copy Superuser.apk to /system/app
>>carefully copy means: chown/chgrp /system/xbin/su to "0"; set perms: chmod 06755 /system/xbin/su.
9. copy busybox from /data/local/tmp to /system/xbin; and install (./busybox --install -s /system/xbin/
10. At this stage, su doesnt seem to work for newer shell connections (must do _su and then su). probably due to the exploit messing up the kernel.
11. reboot. and enjoy your newly permanent rooted status.
12. after reboot, still cannot do system remount as lsm is back to original. rerun the unlock_security_module should disable this.
maybe even move this to /system/xbin/;
But this seems to destabilise the system.
Its not possible to use a lsm disabler ko insmod. the kernel sec mech validates the module with path and hash.
So it has to be: unlock security; do your thing with /system etc., reboot.
(not sure yet if any changes to /system/buid.prop will help)
Do let me know how this works out and point out errors in the steps.
And as luck would have it there is a new ICS release out on 5-Feb.
https://www.nttdocomo.co.jp/support/utilization/product_update/list/f01d/index.html
http://spf.fmworld.net/fujitsu/c/update/nttdocomo/f-01d/update1/top/data/download.html
(F01D_TO_SP_ICS2.zip)
This moves the version to V12R33B.
Do not hazard to update to this, if you want to keep this root. this release probably fixes many of the exploits.
the wifi model seems to have got 4.1..wonder is something will trickle down to f01d.

[Q] I think I killed it.

Alright, so this is going to take a bit of explaining, please bear with me.
I got this phone a couple of weeks ago, subsequently rooted it, and shortly thereafter decided upon Viper for my ROM. After playing around for a bit, I took a look at Beastmode kernel yesterday. I backed up my phone, installed the new kernel, and everything went to hell shortly thereafter. Upon rebooting, my phone no longer detected a mounted SD card. Along with this, it also doesn't have working audio. I tried rolling back to my restoration point, but I cannot find it now. While digging through directories in recovery, I've found two things out.
1: There is now a storage/emulation/legacy folder with (almost) every folder that was in mnt/sdcard.
2: My restore point is gone, and I don't have the original kernel on my phone
I figured this wouldn't be THAT big of a problem, connect my phone to my PC, go into ADB and try to push the stock s-off kernel. Next set of problems.
1: /mnt/sdcard is showing as a non-directory, insists it doesn't exist.
2: storage/emulation/ shows as read only, and all lower subdirectories are coming up as not existing (I believe it to be an issue with folder naming, legacy is actually 0 on my file explorer on the phone, I think?).
Where I stand now::
At this moment, I have the HTC Droid DNA Toolkit running, the stock s-off Kernel, and a phone that doesn't cooperate with anything.
Also; I tried downloading the .zip directly on my phone, but because it doesn't think there's an SD card, it's refusing to let me download it. It lets me download apps from the market, though.
Any ideas?
PS! Forgot the biggest SNAFU in all of this. On my phone are about 200 pictures from my vacation which I hadn't put onto my computer yet because I am an imbecile. This is keeping me from wiping the phone down to brass tacks and starting all over. If someone can find a way for me to pull said pictures from my device, I can wipe it and see if that helps.
Killerkendolls said:
Alright, so this is going to take a bit of explaining, please bear with me.
I got this phone a couple of weeks ago, subsequently rooted it, and shortly thereafter decided upon Viper for my ROM. After playing around for a bit, I took a look at Beastmode kernel yesterday. I backed up my phone, installed the new kernel, and everything went to hell shortly thereafter. Upon rebooting, my phone no longer detected a mounted SD card. Along with this, it also doesn't have working audio. I tried rolling back to my restoration point, but I cannot find it now. While digging through directories in recovery, I've found two things out.
1: There is now a storage/emulation/legacy folder with (almost) every folder that was in mnt/sdcard.
2: My restore point is gone, and I don't have the original kernel on my phone
I figured this wouldn't be THAT big of a problem, connect my phone to my PC, go into ADB and try to push the stock s-off kernel. Next set of problems.
1: /mnt/sdcard is showing as a non-directory, insists it doesn't exist.
2: storage/emulation/ shows as read only, and all lower subdirectories are coming up as not existing (I believe it to be an issue with folder naming, legacy is actually 0 on my file explorer on the phone, I think?).
Where I stand now::
At this moment, I have the HTC Droid DNA Toolkit running, the stock s-off Kernel, and a phone that doesn't cooperate with anything.
Also; I tried downloading the .zip directly on my phone, but because it doesn't think there's an SD card, it's refusing to let me download it. It lets me download apps from the market, though.
Any ideas?
PS! Forgot the biggest SNAFU in all of this. On my phone are about 200 pictures from my vacation which I hadn't put onto my computer yet because I am an imbecile. This is keeping me from wiping the phone down to brass tacks and starting all over. If someone can find a way for me to pull said pictures from my device, I can wipe it and see if that helps.
Click to expand...
Click to collapse
Have you tried using an OTG cable to mount a flash drive? That's what I do when I backup/flash anything, I keep all my roms, kernels, backups, basically anything flashable on a flash drive, and use an OTG cable in CWM.
For the pictures:
Step 1; adb reboot recovery
Step 2; adb devices (to make sure it's detected)
Step 2.1: If your phone isn't detected, open sideload in recovery, adb devices again, then close sideload
Step 3: adb pull /sdcard/ C:\<username>\Desktop\sdcardbackup\
To fix everything else you'll probably need to wipe everything and flash a new rom.
EDIT: For future "snafus" the sdcard is on /sdcard/ not /mnt/sdcard/ because it's on internal memory, not mounted memory.
walther1337 said:
For the pictures:
Step 1; adb reboot recovery
Step 2; adb devices (to make sure it's detected)
Step 2.1: If your phone isn't detected, open sideload in recovery, adb devices again, then close sideload
Step 3: adb pull /sdcard/ C:\<username>\Desktop\sdcardbackup\
To fix everything else you'll probably need to wipe everything and flash a new rom.
EDIT: For future "snafus" the sdcard is on /sdcard/ not /mnt/sdcard/ because it's on internal memory, not mounted memory.
Click to expand...
Click to collapse
Well, I feel silly for that confusion. I've pulled everything from the sdcard, which honestly mattered more to me than fixing the phone. I'll putter around with getting the ROM and kernel operating correctly in the next couple of hours.
UPDATE!
Once I had the adb pull command corrected for me, pushing the new ZIP on there was an instant success in recovery. SD card exists correctly once again, installed Viper ROM over, full functionality once more.
Killerkendolls said:
Well, I feel silly for that confusion. I've pulled everything from the sdcard, which honestly mattered more to me than fixing the phone. I'll putter around with getting the ROM and kernel operating correctly in the next couple of hours.
UPDATE!
Once I had the adb pull command corrected for me, pushing the new ZIP on there was an instant success in recovery. SD card exists correctly once again, installed Viper ROM over, full functionality once more.
Click to expand...
Click to collapse
you can always do this too as long as the device is recognized by adb
Code:
adb shell
this will get you into the actual device where you can navigate around by using the " cd /dir_name " command and to go back up a dir use " cd .. " (a space and 2 "."s are needed) or just " cd " to get back to the starting point... if you know how to navigate through a unix terminal then you will know what to do here...
some other useful commands
Code:
ls, ls -a, ls -l, cd, cp, mv
ls = list (lists files/folders) "-a" means all, "-l" just makes it look neat and laid out better.
cd = change directory aka "dir"
cp = copy /path/to/file.ext /path/to/where/you/want/to/save/it/file.ext
mv = move (same as ^ ) except it just moves it and doesn't copy
oh and to exit adb shell just type "exit"
Honestly, just grab a working kernel. And use fastboot. Especially since you're s-off
fastboot flash boot boot.img should get you back in working order.
Sent from my HTC6435LVW using XDA Premium 4 mobile app

Nabi 2 1.9.12 wifi issue

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!

Categories

Resources