Today I tried to flash the CyanogenMod 9 Nightly 06-30-12, coming from Build 35 of AOKP and after factory resetting and clearing Dalvik I went to install the zip and while flashing it I got a build-prop related error!
All of my NANDROIDS gave me a data error when flashing and now I am pretty f'd! I /really/ need to fix this ASAP but have no idea how.
-Samsung Galaxy Tab 10.1 Wifi-
-CWM 4-
On a second note, does anywhere know where I can get my screen replaced for cheap? I dropped my tab a few months back and the screen got MAJOR cracked, though it still does technically work (I still use the screen, it works but it's cracked is all...) and after calling Samsung and waiting for over 1 and a half hours they told me they wanted $150 to fix it, which if I recall is about half of what I payed for it anyway...
To be honest, I'd be lying if I said I was happy with Samsung over all.
I mean, bad customer support, the proprietary connection cable, and lack of official updates (along with the ugly TouchWiz that I'm not sure /who/ likes ) don't make me that happy...
Anyway, can anyone help me please?
Thanks in advance!
Update your recovery: http://droidbasement.com/db-blog/?p=2655
If you have a GT-P7510 (p4wifi), in this post are flashable zips (with your current recovery) of CWM and TWRP, in case you prefer this method: http://forum.xda-developers.com/showpost.php?p=28051448&postcount=29
After that, flash your ROM like always.
Yeah, thanks, were it so easy. I fired up ODIN multiple times, no matter what, unsuccessful. Like always, my computer would not recognize my tablet. Yes, I have the bloody Samsung drivers, yes I've tried reinstalling them (several times in the last few months), yes I've tried using different USB ports! And what? Nothing. Nothing at all. For the last few months I have not been able to transfer movies/music to my tablet via file transfer and I can't even get the stupid odin download thing to work. To be honest, I really am pissed off with this broken pile of trash. Would trade it in for a similar tablet any time.
Did you try any of the flashable zips for a new recovery?
About the USB, it sounds like a different problem, but for the file transfers, are you sure you have MTP selected? (answer #5 --> http://forum.xda-developers.com/showthread.php?t=1642009 )
If you haven't tried it yet, you could use a different computer, another OS (some Linux distro and check that adb works), change the USB cable.
I can't use a flashable zip since I can't copy files onto the tablet >.>
Also, yes, for file transfers I /do/ have MTP selected always and it doesn't work eitherway.
Essentially, I am stuck with a $300+ ugly and broken thing that I can only use as a paperweight for the huge mess I call my desk. Yay.
>Rage sidenote; Samsung, go take the money I payed for **** and shove it.
And I guess you don't have your old ROM (AOKP build 35) in your tab.
Try with adb (in recovery), but if you can't get a working USB connection (using other computers or OS), maybe there's something physically wrong with your tablet.
No, I don't. I'm stupid enough to delete the ROM zip after flashing it to save space on the tablet...
How do I do this ADB thing? I've heard of it before alot but never used it or looked into it...
Read this: for windows -> http://forum.xda-developers.com/showthread.php?t=1387527 , for Ubuntu -> http://forum.xda-developers.com/showthread.php?t=921169
After everything is installed, boot your tablet into recovery and try running in your command line application (CMD for windows):
adb devices
If it shows that a device (and ID number and the actual state, e.g. recovery) is connected, your golden!
If you have another android device, try it too, to be sure that is working.
To transfer a file the command is
adb push /path/to/file /path/in/tablet
In windows I guess is something like this:
adb push C:\path\to\file /path/in/tablet
so I'd do something like
adb push C:\ADB\CWM-5.5.0.4-p4wifi.zip mnt/sdcard/ ?
Im dling the ADB files right now
adb push C:\ADB\CWM-5.5.0.4-p4wifi.zip /mnt/sdcard/
You need the slash at the star and end of the path of the tablet.
While installing PdaNet it failed, said it couldnt connect through to the device or w/e
Also,I don't recall having ADB on when I had the tablet. I might've but I don't think I kept debugging on for the general time...
This is so frustrating >.>
I'm not sure about that error in PdaNet, I can help you with adb but I don't use Windows, so there's things I can't test.
If you didn't select ADB debugging in your ROM it doesn't matter, you're doing this from recovery.
BTW, do you have other android device?
adb seems to be working and copying, but I can't find the file in Recovery while doing choose a zip to apply!
Yes, I have an LG Optimus V on Virgin Mobile running tdm's AMAZING Quattrimus Alpha 10 on Ice Cream Sandwich/ Android 4.0.4
this is what I get
C:\Users\Mikoyan Gurevich\Desktop\LG Drivers>adb devices
List of devices attached
43C800340009517 recovery
C:\Users\Mikoyan Gurevich\Desktop\LG Drivers>adb push C:\CWM-5.5.0.4-p4wifi.zip
43C800340009517\sdcard\download
1328 KB/s (4147569 bytes in 3.048s)
C:\Users\Mikoyan Gurevich\Desktop\LG Drivers>
If you connect your phone and execute
adb devices
What's the output?
If you do the same with your tablet, what's the output?
with the tablet it's
C:\Users\Mikoyan Gurevich\Desktop\LG Drivers>adb devices
List of devices attached
43C800340009517 recovery
with my phone it doesn't wanna show up in Recovery or not.... Hmm.
Well, it shows fine, then you should be able to transfer the files
First, in your recovery, go through the steps to install some zip file, but just go as far as selecting the directory, then go back
Now in your PC try running something like this, change your path in windows:
adb push C:\CWM-5.5.0.4-p4wifi.zip /sdcard/
The in your recovery, select install and should show there. The thing is that most likely the sdcard wasn't mounted in your tab
Edit, to mount your sdcard in recovery do: mounts and storage > mount /sdcard > Go back
The do the transfer in your PC.
Hmm
While I was holding it to my gut, pushing the end of the cable into my stomach (It was the only way to get it to be recognized) I fooled around and went into download mode, hoping that on the contrary I could do that, turn it off, and when I went back into Recovery it would be there when it finally said the cable WAS connected and then I rushed to open Odin and wrote it through, and it frickin' wrote CWM v5 right on and it worked, I'll be damned!
Maple, I can not thank you enough for helping me with this, I am in great debt.
You're welcome, I'm glad it worked. Knowing how to use adb is really useful. And now you know that something is wrong with your cable.
Or in the connector pins or w/e of the tablet... The cable works fine for charging though....
You are my savior, bro.
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.
Recently I decided to try Slim Bean on my phone, seeing they released a new version a few days ago. I had been running Cyanogenmod 7 but decided it was time for a change. Initially, everything worked great, I was able to reinstall all my old apps, send texts, and things functioned well.
About 12-14 hours after doing this however, my phone stopped having signal. I didn't reboot it or anything, just no longer would it pick up a signal. Checking the about phone revealed it saying it had an unknown baseband and IMEI, I wasn't too concerned, I had backups of the EFS files, so I turned on USB debugging, plugged my computer in, and used an adb shell to move the backup to the main system. However, this still didn't work for my phone.
According to the Slimrom's FAQ, there are two solutions to this: delete the 00check and 98tweaks files in the system/etc/init.d folder, or just reinstall the ROM. However, using an adb shell or a terminal emulator on my phone, both with superuser powers, I can't remove those files. chmod spits back that they are read-only files. lsattr shows only the A tag active, which shouldn't be standing in my way. I seem powerless to get rid of these, and I can't find any guide as to how to do so. I've tried restoring to factory defaults and reinstalling the ROM, and this time I don't have signal right from the start. Can anyone help me figure out what to do about this? I've searched around and can't find any answers, which is making me think I'm just missing something really stupid. Any help would be appreciated!
Update: Figured it out. The system partition was mounted as read-only, and I thought I had tried remounting it but must have tried a higher level directory or botched the command. mount -o remount,rw /system gave me the ability to delete those files. Sorry for the trouble!
I'm not a smart man don't know where to go from here with soft bricked HTC One (AT&T)
Was experimenting with different stuff on my phone and currently on S-Off HBoot 1.44. I was tried to flash a new 4.4 ROM over and somewhere in there something went wrong. Went to backup file and everything was fine, decided to just try and wipe everything on phone (made backup files of everything and have the files in a folder on desktop) and that's where my troubles began. Taking advice from a friend of mine I ended up relocking the bootloader (mistake #1), so of course everything on phone was wiped. I was trying to do adb sideload to push a new rom after unlocking the bootloader again. The computer sees my device in adb on the cmd window. Says:
HT359W917890 recovery
but in sideload in TWRP it says:
E: Unable to mount
I'm guessing its because I no longer have the files on the phone or a stock anything on it. Please help me out here been messing around with it for about 3 hours now running in circles. I'm sure I'm missing an easy step in here but I've been reading all over and am starting to think this **** is pretty hopeless at this point.
Put the rom you are wanting to flash in the folder you are using to open the cmd window and type
adb push nameofrom.zip /sdcard/
I wake up from a nap, see your reply and try it out....now computer isn't seeing my device in adb again. This is so frustrating, back to square one I suppose
okay rebooted the phone and device is showing in adb again (yay) pushed the file through but I'm still getting the
E: Unable to mount '/data'
E: Unable to mount internal storage
any suggestions here?
SOLVED
All solved solved the E: Unable to mount issue by going into TWRP settings and doing a format data wipe. The pushed the file from the computer and voila all solved, I really appreciate the help man!
Brodrick said:
All solved solved the E: Unable to mount issue by going into TWRP settings and doing a format data wipe. The pushed the file from the computer and voila all solved, I really appreciate the help man!
Click to expand...
Click to collapse
Lol I was gonna suggest that but most people freak out when you ask them to format their sdcard
Glad you got it
I recently rooted my device. ( my first time, go figure) After many errors and even a bricked device, I finally managed to root the device and unbrick it. I believe the opperating system was deleted in the process along the way and I had to flash a stock ROM onto the device, resulting in a downgrade from 6.0 to 5.1.1. I still had TWRP on the device and was able to put the needed superuser zip files on the SD card when in TWRP mode because that's the only time the pc recognized the phone. After install in the Superuser files in Twrp the device rebooted up and I ran a root checker and it says that superuser was installed correctly and I have root access. Now here's the issue, I went to go and turn on unknown sources and when I click on fingerprints and securiry, I'm met with an error message saying com.android.settings has stopped . this happens In a few other areas of the settings but not all. I also had downloaded another app (NT Hidden Settings) that I was hoping would allow for me to turn on unknown sources and when I click on the option to turn on unknown sources, I get anmessage saying system/bin/su missing. I now am lost and have no idea what to do. I tried copying a file named su from the xbin folder thinking that may fix the issue but it didnt. Any tips or ideas? If I have to unroot the device and reroot I have no problem doing so (although I'd probably need a concise tutorial because I had very poor luck getting as far as I did..)