Just a quick heads up to everyone, I was able to fix my issue by SWITCHING TO A NEW SDCARD, I had been using a 64GB SDCARD and I switched to a 2GB SDCARD and I guess that my recovery or my phone couldn't handle such a large card.
It took me about two days to come to this conclusion but after lots of ODIN and reflashing just about everything possible I've decided this was the issue. Also I ran up my flash count a hell of a lot. I hope this helps someone out who may have issues like mine!
Hey all,
Today I decided I would try out a new ROM on my SGS3 so I decided to install the MIUIv5 ROM here: http://forum.xda-developers.com/showthread.php?t=2232800
Normally ROM installations go quite smooth for me so I opened up TWRP v2.5.0.0 and I did as I usually do by making a backup and wiping my system and then going to install my ROM. Instead today I got tons of errors saying:
Code:
Finding update package...
Opening update package...
E: Can't open /external_sd/MIUI5_d2vzw_3.4.12.420-signed (1).zip
(bad)
Installation aborted
So, I downloaded the ROM again, but this time from the mirror just in case I had a bad .zip or it didn't transfer to my SDCARD correctly, but then I started getting more and more errors.
Instead of getting a bad zip error I got the following:
Code:
E:Mount: Unable to find partition for path '/'
I guess this means it can't find my root partition?
Now all of a sudden I can't find my backups and I am just stuck without a ROM and I only have a recovery... quite inconvenient, also I can't flash any ROMS as I tried flashing some others but they didn't work at all no matter what I did and I am just running in circles... any help is GREAT APPRECIATED as I would love to have a functional phone by tomorrow.
I am fairly fluent with android and linux systems as well as computers in general so I should be able to provide any helpers with almost all information needed relative to my device, but sadly this whole issue has really stumped me.
Thanks so much!
ljbaumer
Click to expand...
Click to collapse
Have you tried flashing with Odin?
I know a lot of people swear by twrp but for me I always seemed to have issues. I had a similar issue you are having when I finally flashed cwm again. I was able to fix my issue by odin.
Sent from my GT-P5113 using xda premium
Thanks for both of your replies, I decided just to revert back to stock and I am in the process of re-obtaining root and such and then I am going to try to flash again just using recovery... by flashing by odin do you mean flashing a ROM or flashing back to stock?
FIXED! Read OP
Related
Hey guys,
I have a problem, which i couldn't solve using the search. Sorry if i was too stupid to search at all
The thing is this:
I have a Nexus S I9020T which i bought as "broken"
It is stuck at the Google logo with the open lock. I thought i could save that device easily but i can't get that thing to work again.
At first: I still have my first android phone here: a Milestone. I had it for a year now and i would say that i flashed pretty much everything to that device. So i know a thing or two about android and flashing. But i have never had a nexus s in my hands before.
So i did this:
I Opened the Bootloader -> success
I flashed a few different CWM recovery -> also no problem here
I flashed a SU_2.3.6.1 which was already on the sdcard and it flashed without an error
I tried to delete all the files of the previous uswer -> at first I could delete all but as soon as i unmount and mount the usb storage, everything is back to the way it was. Means I can't delete or write anything onto the sdcard
Sometimes i have luck and i can write a .zip file to the card but as soon as I try to flash the ROM CWM says : e:can't open /sdcard/***.zip (bad)
so i know, that sometimes the zip files is just... bad. So i downloaded at least 10 different roms. Always the same problem.
I can'T format the SDcard, at every new mount, everything is back to how it was when i got the phone.
I tried to flash with Odin. But the only thing that changed was that i lost the recovery. So i flashed it new and here i am still stuck with that thing
Odin gets stuck while flashing with som PK[][][] thing -> screenshot. Doesn't seem to get further.. so flashin failed... any ideas?
So my question is:
Is there a problem with the SD card?
Is there just a problem with drivers?
Can My Phone be repaired?
Please you guys help me with your knowledge.
I am living in germany and the nexus is bought in the USW at bestbuy in december 2010. Does someone know how the warranty thing is handled for such a scenario?
Thanks a lot guys for even reading my problem.
My Tab has been collecting dust for most of the year, so I figured I'd dust it off and update it to a shiny 4.3 rom. I wiped everything (no nandroid, stupid I know) and tried to flash, but I got a "status 7" error. It wasn't tied to the device, but to symlinks (I did try to remove the assert lines in the updater script first, just to make sure). According to some of the error lines in TWRP, it was the permissions (set_perm some changes failed). This result was the same from CWM, to TWRP, and finally to Philz recoveries.
I just couldn't flash anything. I tried a few 4.3 roms, and then assumed that perhaps something changed with 4.3 firmware-wise that I didn't have, tried something 4.2 like what was on before. Nothing. Same status 7 errors. I've been doing some research and can't find anything that will work for me. I've noticed, however, that I can't unmount the data partition. I'm wondering if this is my problem, and I can't find the solution for this either. Help the noob?
EDIT: I managed to flash a stock ICS image via Odin, then attempted to install TWRP and try again. Same errors. Not sure what could be going on.
Anybody? I'm not sure how often the second page gets glanced at around here. Even an inkling of an idea might put things in motion.
I believe Status 7 usually indicates the wrong update file.
You might try...
androidforums.com/nexus-s/588179-jelly-bean-update-status-7-error.html
highonandroid.com/android-roms/how-to-fix-status-7-error-with-cwm-recovery-on-rooted-android
ibtimes.co.uk/articles/499093/20130814/galaxytab2-p3100-p3110-p3113-android43-jellybean-cyanogenmod102. htm
Best of luck.
Bennyboy371 said:
My Tab has been collecting dust for most of the year, so I figured I'd dust it off and update it to a shiny 4.3 rom. I wiped everything (no nandroid, stupid I know) and tried to flash, but I got a "status 7" error. It wasn't tied to the device, but to symlinks (I did try to remove the assert lines in the updater script first, just to make sure). According to some of the error lines in TWRP, it was the permissions (set_perm some changes failed). This result was the same from CWM, to TWRP, and finally to Philz recoveries.
I just couldn't flash anything. I tried a few 4.3 roms, and then assumed that perhaps something changed with 4.3 firmware-wise that I didn't have, tried something 4.2 like what was on before. Nothing. Same status 7 errors. I've been doing some research and can't find anything that will work for me. I've noticed, however, that I can't unmount the data partition. I'm wondering if this is my problem, and I can't find the solution for this either. Help the noob?
EDIT: I managed to flash a stock ICS image via Odin, then attempted to install TWRP and try again. Same errors. Not sure what could be going on.
Click to expand...
Click to collapse
True, this is usually the case, but not this time. I tried all these, but the root of this issue is with the symbolic links and setting permissions. I am starting to really think it's all about getting data to unmount, but I haven't been able to get this to happen.
back to the stock rom
---------- Post added at 04:20 PM ---------- Previous post was at 04:17 PM ----------
[/COLOR]
Bennyboy371 said:
My Tab has been collecting dust for most of the year, so I figured I'd dust it off and update it to a shiny 4.3 rom. I wiped everything (no nandroid, stupid I know) and tried to flash, but I got a "status 7" error. It wasn't tied to the device, but to symlinks (I did try to remove the assert lines in the updater script first, just to make sure). According to some of the error lines in TWRP, it was the permissions (set_perm some changes failed). This result was the same from CWM, to TWRP, and finally to Philz recoveries.
I just couldn't flash anything. I tried a few 4.3 roms, and then assumed that perhaps something changed with 4.3 firmware-wise that I didn't have, tried something 4.2 like what was on before. Nothing. Same status 7 errors. I've been doing some research and can't find anything that will work for me. I've noticed, however, that I can't unmount the data partition. I'm wondering if this is my problem, and I can't find the solution for this either. Help the noob?
EDIT: I managed to flash a stock ICS image via Odin, then attempted to install TWRP and try again. Same errors. Not sure what could be going on.
Click to expand...
Click to collapse
try to get back to the stock rom firmware, I have the same
problem few days ago, cant flash any rom
n I think the problem b'cause wrog flash when rooting or
flashing the image cwm/bootloader
that's all I know,
Well it's good to know that I'm not the only person who has had this problem. I managed to get back to stock. I'm not sure what I can do from here, though. I don't want to try anything because I don't want to break it.
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 folks. I am trying to get the hang of messing around with my android device. I am quite good with Windows/Linux, so this is the next frontier. So here is my problem: I am trying to update my TF101 to 5.1 and the installation failed. I installed Clockwork Recovery v3.2.0.1 and it worked well, I can get into recovery no prob. I installed the kitkass 5.1 on the SD card, the Update-Super-v2.46, and Katkiss_5.1_030c.
When I trying to install from zip the Katkiss I get this error:
set_metadata_recursive: Some changes failed.
E:error in sdcard/Kitkass/Katkiss-5.1_030c.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
I am a bit stumped. Did I download a bad copy? I can't get into the TF101 at this point except for recovery. When I try, it just stays on the ASUS splash page.
I am sure this has been asked before, but I couldn't find any threads with this issue. Any help is appreciated.
xa3phod said:
Hey folks. I am trying to get the hang of messing around with my android device. I am quite good with Windows/Linux, so this is the next frontier. So here is my problem: I am trying to update my TF101 to 5.1 and the installation failed. I installed Clockwork Recovery v3.2.0.1 and it worked well, I can get into recovery no prob. I installed the kitkass 5.1 on the SD card, the Update-Super-v2.46, and Katkiss_5.1_030c.
When I trying to install from zip the Katkiss I get this error:
I am a bit stumped. Did I download a bad copy? I can't get into the TF101 at this point except for recovery. When I try, it just stays on the ASUS splash page.
I am sure this has been asked before, but I couldn't find any threads with this issue. Any help is appreciated.
Click to expand...
Click to collapse
I have this devices some were in a drawer lol anyways sounds like u mave have downloaded a bad copy try redownloading and get a md5 checker and check it. Also did you make a back up in twrp? If so could restore that in time being. Have a read trew kitkass thread agin and see if you missed any thing i know i had that rom running at one point but went back to kitkat cuz it was more stable.
Thanks for the help. I think I had a bad copy and a redownload fixed the issue. Android 5.1 is on the device and it sort of works. Well, not really. It runs poorly, reboots a lot and now it actually reboots before I can log in. I think I should hit a lower version of Android. Any suggestions on which version works best on the TF101? As of now its not usable.
Also, if I go to say, 4.4, can I use the same gapps-Katkiss-5.1 or do I need a correct version for 4.4? Can I just install it over 5.1 or do I need to wipe the device and start from scratch?
Again, thanks for the help.:good:
I tried to install 4.0.3, the official TF101 image from Asus but it wouldn't install. How do I go back to stock?
Here's to hoping someone can help me out. My phone details before I messed up: LG G3 D850, rooted, TWRP 3.0, running Fulmics 5.2 for about 1 1/2 weeks
I noticed that I was not seeing the LTE indicator on my phone. I checked the HUB and saw the BootD850-30012016 data patch and figured that I just needed to install. So I flashed it and my phone wouldn't start. I was able to boot into recovery, so I figured I would do a clean install of the ROM so I did a full wipe, accidentally wiping EVERYTHING except for my external SD.
Result was that I can access TWRP but am unable to flash any of my backups or zips from my external SD, or OTG. I can see the files, but don't have the option to "swipe". I also am unable to 'mount' or 'install'.
At this point, I noticed that AT&T has finally released the OTA for Marshmallow, so I figured I would just use LG FlashTool and totally un-root and give the update a try. (BTW, I have used the flash tool many times with no problems/issues on both my phone and my son's D855).
Unfortunately, I am getting the dreaded "unable to change to download mode" after 15 seconds. I have uninstalled and re-installed Flash Tool, the LG Drivers and all files and used every port on both of my computers (Windows 10 btw) but can't get past the download error.
So...after many hours of digging, I took a leap of faith and was able to sideload Fulmics 5.1 successfully and install the 5.2 update from the HUB. I made backup of the ROM but TWRP still won't allow me to "swipe" and install/restore. I reinstalled TWRP using Flashify and it installed version 2.8 but still no go on flashing from recovery.
I realize that I'm lucky to have been able to figure out how to get the phone back using the sideload function in TWRP, but I really do want to go back to stock and it bugs me that I am unable to use my backups.
Sorry for the novel, but I wanted to be sure to include everything I did....if anyone can help me out I would be much obliged. My 11 year old is anxiously waiting on me to figure this out before she gets this phone (I'm moving up to the HTC 10 in a couple of weeks!). She still thinks I'm 'SuperMommy' so if I can fix this I get to keep my swagger!
I was also running fulmics 5.1 and updated to 5.2 in my phone but now i was having pretty good laggs and i finally realised that the update provided by the phone was corruped so i went on the official site and downloaded the same 5.2 OTAs from there and flashed it into TWRP recovery to finally get the latest version 5.3..know that is it always advisable to flash zip file when in recovery mode using TWRP recovery...The big mistake was cleaning also the internal memory of your phone.this caused the malfunction of twrp.
The issue is that most often i have seen cases of lagg in those updating to fulmics 5.2 from the Hub .sometimes in twrp recovery the update files will not successfully wipe and then reboot system with 5.2 installed but with many lagg the file downloaded there may be corrupted and not give you permission to swipe..if you really like fulmics and still update to the latest..Try this it may help you solve your problem:1 reinstall the fulmics 5.1 go to xdadevelopers.com/fulmics follow the link given by xpirit to www.fulmics.com and download the OTA 5.2(file size maybe 46 mb).. 2.reboot your phone now in twrp recovery it should now be able swipe and install..(if not then install Twrp 3.0 and try) 3-search the files in your internal memory or wherever you have downloaded it and flash it ..4.reboot system.That should be done!! In case you want to come back to stock and cant install from Twrp then the problem is with Twrp just download the latest version that goes with your phone.
Thanks guys for the suggestions. I finally figured it out after a couple days of sweating and swearing. Yaneddik, you were spot on about updating from the Hub. I ended up installing TWRP 2.8.6 and re-installed 5.1 from the Fulmics website along with the updates. Everything has been working great (except for losing LTE connectivity, but that's for another thread!). I'm not inclined to update TWRP to 3.0 unless absolutely necessary, 2.8.6 works just fine for me.
dcli23 said:
Thanks guys for the suggestions. I finally figured it out after a couple days of sweating and swearing. Yaneddik, you were spot on about updating from the Hub. I ended up installing TWRP 2.8.6 and re-installed 5.1 from the Fulmics website along with the updates. Everything has been working great (except for losing LTE connectivity, but that's for another thread!). I'm not inclined to update TWRP to 3.0 unless absolutely necessary, 2.8.6 works just fine for me.
Click to expand...
Click to collapse
Am a newbie here but a long time rooter on my older phones. This is the first time that I've seen the Hub mentioned. Can you kindly post a link?
TIA
Sent from my LG-H810 using Tapatalk
SofaSpud said:
Am a newbie here but a long time rooter on my older phones. This is the first time that I've seen the Hub mentioned. Can you kindly post a link?
TIA
Sent from my LG-H810 using Tapatalk
Click to expand...
Click to collapse
Hey there....you can access the Hub after you flash the Fulmics ROM. It's where you can get your tweaks, downloads, mods, etc. You'll find it in your app drawer.