I flashed clockworkmod and rooted a few days ago and all has gone well. I'm a bit concerned as I don't have the problem described when rebooting and losing the custom recovery - it doesn't get overwritten as it should do (I have rebooted many times now). Also I don't appear to have the file "install-recovery.sh" on my system (I have searched/browsed using root explorer).
Obviously this has been no problem to me but I would like get get an idea as to why I seem to be immune from what most others experience and is there any potential problem that anyone can forsee (like if i ever need to restore the default recovery). Any suggestions would be appreciated.
Related
I hope I am not wasting anyones time by posting something that may be and I hope is a simple fix, but I have a problem with my Verizon Xoom, a 602 (without the 4g upgrade- don't even have verizon service) that I can't figure out- and it's not for lack of searching. I have been rooting my devices and running custom Roms since my HTC Touch, (a big thank you to all of you here at xda for all the knowledge and instruction I have been able to leach) but I am very much still a noob with only the vaguest since of how Linux, android or the devices themselves actually work- and that is especially true of my xoom with all its post release changes in storage and whatnot since I bought mine, so please don't flame me to hard if this is just my ignorance- I promise you I'm not just being lazy, I just can't figure this one out. I have been running EOS for a while now without a hitch, and recently installed 150 when it became available. everything was fine until a couple of days ago when it started freezing on unlock which just took turning the screen off and back on to fix, but every app started crashing, some periodically and some such as android.process.acore, browser, and google play that won't open at all. I use Team Win's recovery and tried a wipe and reinstall, but same thing. When I try to fix permissions I get a failure with the message "E: Unable to chown '/data/app/com.google.android.youtube-2.apk' 1000 1000". Also when I try to wipe internal storage I noticed everything was still there even though my recovery was saying I had a successful wipe. I switched to clockworkmod recovery and tried to use eraseData file in the folder to wipe the old way but that didn't seem to work either (which I'm not even sure I did right but figured I better get some advice first anyway), and when I tried to flash EOS 3 stable it won't get past the EOS boot animation at all. If anybody out there knows whats up and has the time to point me in the right direction it would greatly appreciated... Thanks
Wowzers! When all else fails ... unroot / re-root. That will wipe everything.
Well hi folks...
from today on - made no changes to my rooted nexus5 with graviton n5 1.1, which worked without any problems from the day I got it - it keeps changing the WiFi-mac-address after rebooting. (first 3 octets stay the same, last 3 octets change randomly, see attachment)
The issue seems to be well known on some other devices, but obviously I´m the first one experiencing this on the Nexus5.
Anyone else having this problem and maybe got a solution for ? It´s pretty annoying to have lots of entries on my wlan-router, also persistent ip assingning is not possible any more.
Things I tried already to fix the problem:
- installed different custom (bricked and franco) and stock kernels
- wiping dalvic/cache
- restored EFS-Backup made on the second day I got the phone
- reverted back to full stock without root / unlocked bootloader
Any help / tips / tricks to get things fixed would be highly appreciated ...
This seems to be a nexus thing, but not everyone's phone does this. There is a fix for it (I applied it to my galaxy nexus) but I'll have to get hone before I can find the instructions...it requires some hex editing
Sent from my Nexus 5 using Tapatalk
Nobody any useable information regarding this problem?
Experiencing the same. Except for when I restore stock it returns to its original. So weird, maybe has something to with restoring a twrp backup checking Vendor partition?
Apologize if I am posting in the wrong spot, but I have pretty much defined insanity by trying the same over and over and expecting a different result. I have accepted that I can't get it to work, but I am hoping someone can shed some light... and yes I have scoured XDA and the entire net for a solution. Here is my situation:
Received a replacement d2vzw with 4.1.2 because I bricked mine trying to downgrade from 4.3 - in the early days of release before it was known this was a very bad idea.
I am able to root and install custom recovery just fine, but TWRP and CWM cannot see/mount internal or external storage. Philz can see the storage but any attempt to apply a custom ROM fails and increments the binary counter.
I have tried editing the ROM script file to remove the model check but it still fails.
It seems that others have had the mounting problems per http://forum.xda-developers.com/showthread.php?t=2391616, but these are for Sprint and do not work for d2vzw.
From what I can tell it appears Sammy and/or Vzw made an undocumented change in the newer S3's that added additional security to prevent flashing custom ROM's. My question is has anyone been able to solve this for the d2vzw?
Thanks in advance.
Solved
So thanks to the post by ohlin5 here, many hours of frustration have been solved.
Again, my issues were that I could not mount internal or SD storage after apparently successfully achieving root and unlocking via CASUAL. Neither TWRP or CwM would work. Philz would mount the storage, but anything other than stock ROM would not install and would increment the binary counter. Based on other posts I was under the impression that there had been a hardware change (this is a newer S3), that was causing this behavior. However, it occurred to me that the bootloader was not actually fully unlocked (even tho it appeared that way and recovery was able to be installed). Per the posting above, it was suggested to run EZ-Unlock and then install recovery and this WORKED! I am not sure what the issue is and why CASUAL is not working in some cases, but I can confirm the behavior and fix.
Hopefully ohlin5's post can save some others the time/hassle as it seems many have the same problem.
I've been doing research on this for a while, and I decided to sign up and ask about this question. Majority of the topics here dealing with bricking either have solved it because of access to fastboot, or some users have given up and either retired their devices or sent them in to ASUS.
Long story short, I installed Clockwork Recovery Mod and Cyanogen mod with no issues. After a couple of weeks, I decided I wanted to go back to stock. I did some research and found a topic which said I needed TWRP in order to flash back the stock ROM. I installed TWRP, but some things seemed to have gone awry with that install and I no longer have access to the fastboot menu and the tablet keeps booting straight into recovery.
I can load new roms by pushing them with adb, but when I try to reload the stock mod it just reboots and nothing gets installed. I tried to sideload a rom, but my version of TWRP doesn't have that feature (I have 2.2). So far, I think I can get it back on track if I could somehow install a new recovery, or start my device from scratch somehow.
Also whenever I transfer to device memory, if I reboot the tablet, everything gets erased and the log is littered with errors about not being able to find and mount /data. From what I've read, it should be solved with a simple format of the file system. However, all of my attempts to use the recovery's built in wiping/formatting tools have ended with no success. If I put in a microSD, that gets wiped as well so in order to load a ROM, I have to push it using adb.
I thought I had fully bricked it, but it seems that since it's accessible through adb, it's still somewhat fixable. I know about backing up everything with nvflash, now, I guess I just didn't do enough research before getting into this. Any ideas, feedback, is appreciated, so far I'm learning a lot about android devices from this experience.
lino4 said:
I can load new roms by pushing them with adb, but when I try to reload the stock mod it just reboots and nothing gets installed. I tried to sideload a rom, but my version of TWRP doesn't have that feature (I have 2.2).
Click to expand...
Click to collapse
Where did you dig out this ancient TWRP version? It is not compatible with the current bootloaders and cannot access the internal storage at all - that's why all your installation attempts are failing.
Read this thread, it deals with a similar problem: http://forum.xda-developers.com/showthread.php?t=2291974
_that said:
Where did you dig out this ancient TWRP version? It is not compatible with the current bootloaders and cannot access the internal storage at all - that's why all your installation attempts are failing.
Read this thread, it deals with a similar problem: http://forum.xda-developers.com/showthread.php?t=2291974
Click to expand...
Click to collapse
Yeah I found that thread not too long ago, I pushed the bootloader and was able to load the stock rom and get everything going.
Hey guys,
I've used XDA for quite a while now as a resource for rooting and flashing my phones. After some trial and error, I finally got a custom rom and root onto my previous phone, the Samsung Galaxy Light (SGH-T399). However, I booted the T-MOBILE kernel, not MetroPCS, and got locked out. So I bought a Galaxy Core Prime, and after a bit decided to root that as well. But when I did some sort of permission modification and tried to make my extSD writeable, the phone crapped out. It would not load the kernel past the bootloader. I tried flashing everything and anything. It just would not allow it to write or mount properly.
So I went back and tried restoring the T399 until I sorted that out, and the same thing is happening. I even flashed ShabbyPenguins stock rom which never failed me before, to no avail . I was able however to successfully install TWRP again. Someone please help me out, I can't afford another phone at the moment. Im still a novice, but I know enough to know it's more than just a mistake in Odin or a file I didn't upload. I've tried searching for an answer to no avail.
P.S. -I'm 90% sure it's a partition issue of some sort, where the filesystem isn't being communicated with properly.