I recently changed from pauls recovery to twrp and tried to wipe and flash new rom however now im stuck. twrp seems to have wiped some stuff but not all and the rom just boot loops. any help is welcome asap.
I get this message. E:error opening '/data/data/com.google.android.g and E:error: I/O error
patrickliebl said:
I recently changed from pauls recovery to twrp and tried to wipe and flash new rom however now im stuck. twrp seems to have wiped some stuff but not all and the rom just boot loops. any help is welcome asap.
I get this message. E:error opening '/data/data/com.google.android.g and E:error: I/O error
Click to expand...
Click to collapse
I was having problems with TWRP recently (and periodically in the past). It would give errors and not flash/wipe/etc. I switched to the latest CWM and it's been working great so far. Just a thought it you cannot find a solution. I couldn't.
Good luck.
I got this from trying to use TB, and it corrupted a file. I switched recoveries a couple of time wiping internal, and data, switched back to twrp, and been solid ever since. It is the way TB messes up. I don't blame twrp for my mistake. Even posted in nebula about it.
Sent from my SCH-I605 using Tapatalk
Related
Hi,
First time it happened. tried everything but still cant fix it.
after a month or two on MIUI, I wanted to move to AOKP JB.
As I always do when switching ROMs, I backed up everything (efs, pictures, apps with titanium, etc) and format the internal sd card within the os to get rid of all the junk.
Then went into CWM (siyah) and wiped data and cache.
And now for my mistake, I foramt the /system instead of / cache.
So now, when Im trying to install the ROM as a zip file threw CWM I got an error 7.
When trying to do it on ODIN, it stuck on 'factory fs', 'cache', or 'boot'.
After some time, I got the "Firmware upgrade encountered an issue" message.
Then got rid of it after somehow succeeding installing a different cwm (the stock one) but nothing worked there either, exept installing the Siyah kernel zip from there.
What can I do now to get my phone back alive?
THANKS :crying:
pedel said:
Hi,
First time it happened. tried everything but still cant fix it.
after a month or two on MIUI, I wanted to move to AOKP JB.
As I always do when switching ROMs, I backed up everything (efs, pictures, apps with titanium, etc) and format the internal sd card within the os to get rid of all the junk.
Then went into CWM (siyah) and wiped data and cache.
And now for my mistake, I foramt the /system instead of / cache.
So now, when Im trying to install the ROM as a zip file threw CWM I got an error 7.
When trying to do it on ODIN, it stuck on 'factory fs', 'cache', or 'boot'.
After some time, I got the "Firmware upgrade encountered an issue" message.
Then got rid of it after somehow succeeding installing a different cwm (the stock one) but nothing worked there either, exept installing the Siyah kernel zip from there.
What can I do now to get my phone back alive?
THANKS :crying:
Click to expand...
Click to collapse
I jumped from S1 to S3, but I'm sure it's applicable. You need to flash via odin stock rom that originally came with your phone. Then root then flash custom rom. Odd tho in past I've done the 5 formats, boot, cache, data, system, sdcard then while still in recovery flash rom. Good luck
Sent from my GT-I9300 using xda premium
jj92942000 said:
I jumped from S1 to S3, but I'm sure it's applicable. You need to flash via odin stock rom that originally came with your phone. Then root then flash custom rom. Odd tho in past I've done the 5 formats, boot, cache, data, system, sdcard then while still in recovery flash rom. Good luck
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
thanks
The problem is, I really cant remember what was the original ROM version. I bought it end of june 2011.
I cant even remember if it was a UK ROM, or an open europe one, or anything else.
****
So i've posted pieces of this in other threads assuming i knew what the problem was, but nobody has been able to help me so far so i'm posting the whole saga anew.
First off, my phone:
LazyPanda S-OFF
HBOOT:1.12.111
RADIO-1.12.11.0809
I was running MeanRom 4.8 with TWRP 2.3.0.1
Like so many others i tried to OTA update just to get stuck at the recovery screen on reboot. I then found out that i had no ROM installed. I tried to wipe (cache, dalvik, system, etc) and flash a new ROM but i kept getting FAIL messages in TWRP.
"Formatting and mounting partition...
e:error in /sdcard/meanrom-ics-v49-jewel-ltevo.zip
(status 1)
error flashing zip '/sdcard/meanrom-ics-v49-jewel-ltevo.zip'
updating partition details"
I figured it might be a botched DL so i did it manually, MD5 checked out after copying to the mounted device. Attempted to flash the clean DL and i got the same error message. I nandroid restored an old stock rooted ROM I had and it installed just fine. After booting up to the system ROM for the first time I immediately got an "Internal storage is low" error. Checked and after a clean restore (no apps installed, fresh out of the box...) i only have ~200MB free in the app storage section (out of 1.92GB). I can't fathom what's taking up all the other space, nothing seems to be there. Because of this i can't install Titanium, Rom Toolbox, or anything else that may be remotely useful. I tried fixing permissions and re-wiping, re-restoring and i got the same thing.
I tried to flash the TWRP 2.2.2.0 image from recovery thinking this was the problem and got this message:
"updating partition details
E:unable to open ums lunfile 'sys/class/android_usb/android/f_mass_sto.....
Formatting cache...done
Formatting Data... done
Using rm -rf on .android_secure
Updating partition details
E:unable to open ums lunfile 'sys/class/android_usb/android/f_mass_sto.....
E:unable to open zip file."
And THEN i tried to ABD flash the TWRP image through fastboot with "fastboot flash recovery openrecovery-twrp-2.2.2.0-jewel.img" then 'fastboot flash boot openrecovery-twrp-2.2.2.0-jewel.img' and got this error:
"FAILED (remote partition is not allowed to be flushed!)"
So, i'm stuck with a device that loads a stock ROM, cant flash a new recovery or ROM, and cant' install anything useful because it's full after a restore. Does anyone have any suggestions how to clean/resore my partitions through ADB or a script? Your advice is much appreciated.
I can't help, but I suspect you'd have better luck posting this in the TWRP thread.
I'm wondering if fastboot erase cache would help here. I've seen that command used I think to clean a partition, but it may have been for something else. Sorry, this is a bit over my head. Hope you get help.
hurled from my AOKP'd Evo LTE. Enjoy.
You might have to re lock and run the RUU and then unlock and flash twrp, 2.3 has issues with the partitions for some reason so stick to 2.2
Try updating to the latest twrp. The latest is 2.3.1.0 not 2.3.0.1.
2.3.0.1 had issues which you can read about here
http://www.pocketables.com/2012/10/...for-htc-evo-4g-lte-fixes-rom-flash-death.html
It's been updated already? Cool
om4 said:
It's been updated already? Cool
Click to expand...
Click to collapse
Yeah, it fixes the mounting of the sdcards and the flashing rom problem
You may also want to get the 1.12.2222 hboot from the unlimited site. It has fastboot commands enabled.
I noticed you tried flashing TWRP to both the recovery and boot partitions...Do you get the same error when you flash to just recovery? TWRP should not be on boot.
Sent from my EVO LTE
I got my S3 a while ago and only recently decided to install a custom rom. I installed the CM10.1 nightly build and I've been happy with it and all, but upon seeing MIUI on my friend's phone I decided to flash MIUI. Now, when I tried flashing through recovery it hung for a min or so at "opening update package" and then gave me an error saying "E: Can't open /external_sd/miuiandroid_m0_jb-3.1.25.zip (bad) Installation aborted". I have tried re-downloading the rom and all, I've tried wiping cache/dalvik cache and even a factory reset and nothing's worked so far.
This happens no matter what rom I try to flash over CM. Has anyone had this happen and does anyone know how to fix it?
b0sanac said:
I got my S3 a while ago and only recently decided to install a custom rom. I installed the CM10.1 nightly build and I've been happy with it and all, but upon seeing MIUI on my friend's phone I decided to flash MIUI. Now, when I tried flashing through recovery it hung for a min or so at "opening update package" and then gave me an error saying "E: Can't open /external_sd/miuiandroid_m0_jb-3.1.25.zip (bad) Installation aborted". I have tried re-downloading the rom and all, I've tried wiping cache/dalvik cache and even a factory reset and nothing's worked so far.
This happens no matter what rom I try to flash over CM. Has anyone had this happen and does anyone know how to fix it?
Click to expand...
Click to collapse
Never happened to me. I can suggest a method that's not been tested, although theoretically there should be no problem implementing.
Although, have you tried flashing some AOSP mods? I'm getting a feeling something might be wrong with your recovery. If that is the case, try flashing siyah and hijack the recovery using stweaks. Then try installing roms again.
Are you installing from the internal or external sd? try the internal, and check the md5
Glebun said:
Are you installing from the internal or external sd? try the internal, and check the md5
Click to expand...
Click to collapse
Tried both internal and external, I get the same thing. I'm pretty sure that it's not corrupted since this is the same file that my friend used to flash his s3 to miui.
xcly said:
Never happened to me. I can suggest a method that's not been tested, although theoretically there should be no problem implementing.
Although, have you tried flashing some AOSP mods? I'm getting a feeling something might be wrong with your recovery. If that is the case, try flashing siyah and hijack the recovery using stweaks. Then try installing roms again.
Click to expand...
Click to collapse
I have not, will try it.
Edit: Flashed an AOSP rom and it worked fine, then MIUI, the install worked but now MIUI is just hanging on the boot screen.
Edit 2: Okay I got it working, I had to do a factory reset and it just started working.
Thanks for your help guys
Hello.
I have only been able to install ViperX+ 1.08 ROM successfully. I wanted to experience other ROMs in comparison and have found ROMs specifically for this model, HTC One X Plus International, only to have them fail to fully install successfully. I have read up here on how to go about it and followed the steps dutifully but to no avail.
Does it make a difference on which Recovery you have installed for it to be successful or not? I currently have the latest TWRP 2.5.0.0 for my model. I have tried installing CyanogenMod and AOKP. CyanogenMod never makes it pass the installation because it fails right after attempting to install. AOKP installs but hang at the opening picture, and yes, I tried flashing the boot.img in Fastboot thinking that would solve it but it continued hanging anyway. Anyone have any help they can offer me? Thanks.
Jussi31 said:
Hello.
I have only been able to install ViperX+ 1.08 ROM successfully. I wanted to experience other ROMs in comparison and have found ROMs specifically for this model, HTC One X Plus International, only to have them fail to fully install successfully. I have read up here on how to go about it and followed the steps dutifully but to no avail.
Does it make a difference on which Recovery you have installed for it to be successful or not? I currently have the latest TWRP 2.5.0.0 for my model. I have tried installing CyanogenMod and AOKP. CyanogenMod never makes it pass the installation because it fails right after attempting to install. AOKP installs but hang at the opening picture, and yes, I tried flashing the boot.img in Fastboot thinking that would solve it but it continued hanging anyway. Anyone have any help they can offer me? Thanks.
Click to expand...
Click to collapse
The aokp uses the 4.2 kernal so you will have to instal that. But I'm not sure on the recovery .. maybe it might be worth trying clockwork as if the twrp you are useing is especially for the viper Rom? Have a go at installing the different recovery maybe that will help and double check what you have to do to install on the thread hope this helps
Ilike the viper Rom... But if I get time tomorrow I will try for myself ... If no one else helps you out by the time I do it I will update you on how I done it and any problems I faced maybe I will end up in the same situation.
Sent from my HTC One X+ using xda premium
Appreciate it. Insofar as the Recovery is concerned, the initial Recovery that I installed from the All-In-One kit when installing ViperX+ is different from the one I have now. Unless it is just a newer version, I now have Venom TWRP 2.5.0.0., just FTR. Thanks again, I will be interested to hear what happens for you.
Jussi31 said:
Appreciate it. Insofar as the Recovery is concerned, the initial Recovery that I installed from the All-In-One kit when installing ViperX+ is different from the one I have now. Unless it is just a newer version, I now have Venom TWRP 2.5.0.0., just FTR. Thanks again, I will be interested to hear what happens for you.
Click to expand...
Click to collapse
TWRP is the ideal solution for our HOX+ - at least as of now.
I hope you are doing the following:
1. Wiping Data & System.
2. Installing boot.img.
The Venom customized TWRP does not have any issues because I also used it for some time (as of now I am back on the official TWRP).
You can download the lastes verison from here:
http://techerrata.com/browse/twrp2/enrc2b
And install it using Hox+ All in one toolkit by hasoon.
Make sure you wipe data & system before you install the ROM.
I also changed from ViperX 1.08 to ARHD, InsertCoin & Elegancia.. no issues
Hmmm. I'll have to putz around with it some more and see what happens. Thanks.
Here's a brief summary of what I attempted to do.
I wiped Delvik Cache; I wiped Cache; I did Factory Reset; I wiped System.
Next I tried installing CyanogenMod and received the following error messages:
assert failed: getprop
E: error executing updater binary in zip
Error flashing zip
So I wiped everything again and tried installing AOKP. It successfully installs. I try rebooting prior to flashing boot.img. It hangs on horse picture opening screen. So I flash the boot.img in Fastboot and reboot after erasing cache. When rebooting it hangs on opening white screen.
I'm baffled. What am I doing wrong?
Jussi31 said:
Here's a brief summary of what I attempted to do.
I wiped Delvik Cache; I wiped Cache; I did Factory Reset; I wiped System.
Next I tried installing CyanogenMod and received the following error messages:
assert failed: getprop
E: error executing updater binary in zip
Error flashing zip
So I wiped everything again and tried installing AOKP. It successfully installs. I try rebooting prior to flashing boot.img. It hangs on horse picture opening screen. So I flash the boot.img in Fastboot and reboot after erasing cache. When rebooting it hangs on opening white screen.
I'm baffled. What am I doing wrong?
Click to expand...
Click to collapse
I guess your recovery is not able to detect that your phone is one x+.. that's why assert failed error.. try changing the recovery( maybe CWM) and try again
Through trial-and-error, and reading hard, I figured out I had to install a compatible Kernel. I then was able to install, successfully, AOKP and it seems to work very smoothly. I'm just learning the ins-and-outs of everything. Thanks for your help.
Jussi31 said:
Through trial-and-error, and reading hard, I figured out I had to install a compatible Kernel. I then was able to install, successfully, AOKP and it seems to work very smoothly. I'm just learning the ins-and-outs of everything. Thanks for your help.
Click to expand...
Click to collapse
:good::good::good:
that is cool!
Hey all, so I decided to go from stock rooted to a custom rom, and see the progress since I last tried it and I encountered the following problem:
I formatted data and factory reset, and then I installed the custom rom, followed by the GAPPS.
Twrp rebooted every time I tried installing Gapps, so I was confused.
The following error occurred when before Aroma started:
"E:Legacy environment property did not initialize successfully. Properties may not be detected"
The next thing I did was I rebooted recovery, no cigar. I tried reinstalling the recovery, no cigar.
I tried formatting data again, and got the error that /data can't be mounted now. This started to worry me lol.
So I tried repairing it and then rebooting, and I tried updating to a newer TWRP but even there, the twrp version won't update. Its still the same number.
I'm too afraid to reboot and see if the rom boots or not, but when trying to flash even a stock rom ZIP it tells me the following:
"This package is for "Joan,h932" devices; this is a ""."
so twrp doesn't know what phone I have?
I am trying right now to restore my TWRP backup but it doesn't want to restore the data, so I'm trying without.
If you can help I would appreciate it very much!!
Here are the screenshots https://imgur.com/a/SLCPdIQ
EDIT: I finally figured it out. Hitting the reboot menu did nothing, because it was for some reason stuck and just rebooted into the same recovery version with the glitch.
I had to do a hard reset, and the finger dance again, and now everything is fixed.