Related
My phone (GT-I9020T) was not rooted or unlocked and was running on stock 2.3.4
after some app updates, it got frozen on Google logo
I flashed a stock rom using odin and the process was successfully completed but it didn't work
I wiped all data and cache many times.
I unlocked the bootloader and flashed CWM 3.0.2.4
When trying to flash a rom from CWM (without rooting), it stops and says "E: couldn't open rom.zip (bad) installation aborted."
When I try to mount /system, it says "error mounting /system!"
and that happens to data as well
I don't wish to root the phone so it won't be easily brickable as I'm not an expert in this, but I'll try to root it if you guys say that I have to
Please help
Try to re-download the ROM package (I'd suggest the OTA for your model.) It looks like the package was not downloaded properly.
Flashing a ROM doesn't require root anyway.
suksit said:
Try to re-download the ROM package (I'd suggest the OTA for your model.) It looks like the package was not downloaded properly.
Flashing a ROM doesn't require root anyway.
Click to expand...
Click to collapse
I tried that. Didn't work either
any help guys?
at least, how can I format my sdcard before sending it to maintenance? when trying to format through CWM, it says it is formatted but it is not
even mounting it and formatting it through my computer didn't work
Last night, I decided to try out the Trinity kernel. I downloaded and flashed, and everything went without error. After that, I pushed a custom boot animation over ADB. The first one didn't work, and after the splash screen disappeared it was simply a black screen, but then I pushed one I downloaded from XDA and it was fine.
Now, though, I want to make a nandroid, but CWM is running into some issues. I started the ROM manager app, entered a name for the nandroid as usual, and hit OK, but when it rebooted into nandroid, it gave me an error saying "Error mounting /system" and rebooted back into CM7. That's odd, I thought, I never had any problems like that before. So I rebooted into CWM myself by holding down power+vol down and tried making a nandroid there. No luck. Then I went to mounts and storage and tried to manually mount /system. CWM gave me the error again.
I'm not really sure what's causing this. I thought it might be because now I'm using an ext4 filesystem because of Trinity (right? haha I'm new to kernels and such) and CWM might not support reading it, but if that's the case, I think I would not be the first to have this issue. Yet I searched, on that thread, on Google, on XDA general search, and didn't see anything. I also doubt it's the boot animation.
My last nandroid was yesterday. The only changes to the system I remember right now is that I flashed CM7 nightly 101, then flashed Trinity, rebooted, and flashed the boot animation mentioned. I installed apps since then but none of them had root so I doubt that's it. I would reflash CM7 to overwrite Trinity, but I read on the Trinity thread that if I did that without restoring an old CM7 kernel nandroid first, I'd be stuck in a bootloop because of ext4...?
So, what should I do? I don't want to make anything worse than it already is by tinkering with this myself, I no longer have a current nandroid, that's why I'm asking XDA. Does anyone have an idea why this might be happening? I'm sorry if a thread like this already exists or if this is in the wrong forum (if so mods please move it), this is my first time posting and my search skills could suck (although I looked in all the places I could think of)
Thanks for your help! My G2x is running CM7 nightly 101. Both the nvflashed CWM in recovery and the CWM started by the rom manager app are version 3.0.2.7.
I got the same problem as you bro right after flashing trinity
Sent from my LG-P999 using XDA App
ritthyhang said:
I got the same problem as you bro right after flashing trinity
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Good, so I'm not the only one! I thought that was too odd to be true.
Here's what I've done. I reflashed cm7 nightly 101 to get my CM kernel back and rebooted. Sure enough, bootloop. Or it never got past the splash screen to the CM7 android skateboard boot animation. I went back in recovery, though, and was able to mount /system. Odd. So I flashed trinity again and tried mounting /system again and no go. So this definitely has something to do with Trinity... I restored my nandroid, reflashed 101,and that's where I am now. Tomorrow, I will make an up-to-date nandroid and do some tinkering to try to figure out what's going on. Maybe it has something to do with the boot animation, maybe not, exactly what's going on is what I am going to try to figure out if no dev shows up here.
Could you give me a few details about your case? Were you coming from cm7 too? Did you do any boot animation tinkering like me?
Sent from my LG-P999 using XDA App
Okay so I was eaglesblood 1.6 and flashed trinity the other day. Before trinity I was on miui and made plenty of nandroid backup. So today and 1.7 got released so before update I try to backup then behold Our Problem. So after I confirm that I can flash 1.7 over 1.6 I decided to take that risk and flashed anyways. On 1.7 the Superuser was updated I notice, so I decided to make a backup and it Work. So I think the problem was had to do with the outdated Superuser. I think I might be wrong that's just my experience.
Sent from my LG-P999 using XDA App
ritthyhang said:
Okay so I was eaglesblood 1.6 and flashed trinity the other day. Before trinity I was on miui and made plenty of nandroid backup. So today and 1.7 got released so before update I try to backup then behold Our Problem. So after I confirm that I can flash 1.7 over 1.6 I decided to take that risk and flashed anyways. On 1.7 the Superuser was updated I notice, so I decided to make a backup and it Work. So I think the problem was had to do with the outdated Superuser. I think I might be wrong that's just my experience.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Hmm. So to clarify: You were running MIUI, then you flashed eb followed by trinity. Then, eb 1.7 was released and you went to nandroid, but you couldn't mount /system, so you took the risk and upgraded anyways. The new be came with a new version of superuser, and you were able to make nandroids once again. Is this correct?
One very important question if it is. Did you flash trinity again after flashing the eb 1.7 update?
Also, could I ask what version of superuser came in this update? I am using version 2.3.6.3, which is the latest according to Superuser check for updates, but ROM Manager lists a 3.0 beta version and I'm wondering if you're using that. To check, open Superuser, go to the settings tab, and scroll all the way down. It's the second to last option for me. It's unlikely that superuser is making the difference, since it works as a part of Android and our problem is in recovery, before Android loads, but I can see how it might be possible. If you're using the 3.0 beta, I will flash to that and see if it fixes.
I will look into this some more tomorrow, specifically right now I want to know what filesystem eb's kernel recommends.
Sent from my LG-P999 using XDA App
G2X here same problem.
I think they key here is MIUI. I tried to load MIUI image and it didnt go well. I formatted and CWR to restore and its been giving me issues same cant mount system errors.
Right now I downloaded CM7 and installed it from scratch and I can use the phone but it wont backup my ROMs anymore.
Have you guys found anything new ?
lithivm said:
I think they key here is MIUI. I tried to load MIUI image and it didnt go well. I formatted and CWR to restore and its been giving me issues same cant mount system errors.
Right now I downloaded CM7 and installed it from scratch and I can use the phone but it wont backup my ROMs anymore.
Have you guys found anything new ?
Click to expand...
Click to collapse
Update cwm to latest recovery 5.0.2.0 i believe.
fcisco13 said:
Update cwm to latest recovery 5.0.2.0 i believe.
Click to expand...
Click to collapse
+1 cwmr 5.0.2 is the first to officially support ext4 partitions
Sent from my LG-P999 using xda premium
lithivm said:
I think they key here is MIUI. I tried to load MIUI image and it didnt go well. I formatted and CWR to restore and its been giving me issues same cant mount system errors.
Right now I downloaded CM7 and installed it from scratch and I can use the phone but it wont backup my ROMs anymore.
Have you guys found anything new ?
Click to expand...
Click to collapse
I just stopped using Trinity and went back to the stock CM kernel. I don't think it's just miui, I never used that. But...
fcisco13 said:
Update cwm to latest recovery 5.0.2.0 i believe.
Click to expand...
Click to collapse
squish099 said:
+1 cwmr 5.0.2 is the first to officially support ext4 partitions
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
YESS! Looks good. I did hear about that. Looks like it's time to give Trinity another try
Error mount/system!
I can't restore my stock rom,i've tried to fully wipe but got:
-- Wiping data...
Formatting /data...
Error mounting /data!
Skipping format...
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
Data wipe complete.
and cant restore
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Restoring system...
Error mounting /system!
Skipping format
Can't mount /system!
and cm7 doesnt boot,now im just stuck in ClockworkMod Recovery v4.0.0.5
is there any ways to flash stock rom in clockworkmod??
asn_86 said:
I can't restore my stock rom,i've tried to fully wipe but got:
-- Wiping data...
Formatting /data...
Error mounting /data!
Skipping format...
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
Data wipe complete.
and cant restore
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Restoring system...
Error mounting /system!
Skipping format
Can't mount /system!
and cm7 doesnt boot,now im just stuck in ClockworkMod Recovery v4.0.0.5
is there any ways to flash stock rom in clockworkmod??
Click to expand...
Click to collapse
Update your recovery, both, fake and nvflash.
i was also having the can't load system issue. upgrading to latest clockwork mod via rom manager to v5.0.2.0 resolved the issue and i was able to take a backup of my current system.
jblah said:
i was also having the can't load system issue. upgrading to latest clockwork mod via rom manager to v5.0.2.0 resolved the issue and i was able to take a backup of my current system.
Click to expand...
Click to collapse
Where do I find the latest clockwork mod and how do I install it? I currently have a soft bricked phone, and I can't seem to get it unbricked. I tried using the pit files with the stock rom, the dbdata stuff and everything else. What happened was the the system was in ICS, but something happened and I couldn't load into CWM 4 and the system wouldn't boot. So to fix, I used odin to install the stock rom (v2.3.3), but the stock rom came with CWM 3.0, so now I'm at 3.0 and can't mount the file system and it's not booting. I'm assuming that if I upgraded the CWM back to a newer version, I'll be able to restore the system and gain access to the file system again.
reboot problem
i jus flashed ext4 converter for kernel update every think went fine but i couldnt mount system coz it was showing error i neglected dat nd flashed every thing was done nd when i rebooted it gt stuck in d samsung galaxy y logo...plzzz help meee wat to do..plzzz help
Abizer98 said:
i jus flashed ext4 converter for kernel update every think went fine but i couldnt mount system coz it was showing error i neglected dat nd flashed every thing was done nd when i rebooted it gt stuck in d samsung galaxy y logo...plzzz help meee wat to do..plzzz help
Click to expand...
Click to collapse
I'd ask in the samung galaxy forums bud.
"my mind draws lots of blanks actually"
Solution
asn_86 said:
I can't restore my stock rom,i've tried to fully wipe but got:
-- Wiping data...
Formatting /data...
Error mounting /data!
Skipping format...
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
Data wipe complete.
and cant restore
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Restoring system...
Error mounting /system!
Skipping format
Can't mount /system!
and cm7 doesnt boot,now im just stuck in ClockworkMod Recovery v4.0.0.5
is there any ways to flash stock rom in clockworkmod??
Click to expand...
Click to collapse
actually yes. the /system folder is corrupt and it need to be formatted. so all you need to do is format / system then it will work as it should
hope that helps
I posted this in Q&A, but no replies led me to post here as well.
Hi. I've been using this Xoom for a couple weeks now, and just started having this problem yesterday.
Before I noticed the promblem I was on EOS 3 Wingman. I had TWRP 2.2.2.0 as recovery.
I wanted to give CM10 nightlies a shot. Downloaded the ROM and GAPPS through Goo. I tried to flash the CM10 ROM and GApps zip through the Goo interface. Xoom rebooted and instead of installing, I just got a contantly repeating error saying the install failed.
Eventually I rebooted the xoom and went into recovery. I tried to wipe data and it said it couldn't be mounted. Same error for wiping system, cache, etc...
Rebooted xoom and the EOS 3 rom was still working fine, I downloaded [Recovery] ClockworkMod 3.2.0.0 (R4c) Modded for Internal media [UPDATED 10/6]" and flash via adb. rebooted to recovery and tried wipe. same issue. nothing could be wiped. everything said "failure mounting <applicable partition>".
I tried flahing rogue recovery and got the same thing. I said screw it and rebooted back into EOS and it's been working fine. EOS was updated last night to 143, so i downloaded and tried to install through goo. I got the repeating errors again. Rebooted into recovery and still got the errors where it seems like none of the partitions are writeable.
I WAS able to install the EOS update directly through recovery.
Has anyone ever seen this behavior before and know how to fix it? I can't even export logs in the 2 CWM recoveries because they fail when trying to write the log file.
If I try to install an update through goo, it reboots to recover and just keeps scrolling "An Update Error has occured".
I can reboot to recovery and install the zip from there directly with no issue.
Here is the log for the failed data wipe...
I:mke2fs command: mke2fs -t ext4 -m 0 /dev/block/mmcblk0p10
mke2fs 1.41.12 (17-May-2010)
/dev/block/mmcblk0p10 is apparently in use by the system; will not make a filesystem here!
E:Unable to format data.
* Verifying filesystems...
I:=> Let's update filesystem types via verifyFst aka blkid, command: 'blkid'.
* Verifying partition sizes...
Ievice has /data/media
I:Total used space on /data is: 5122715648
I:Total in /data/media is: 3962468352
I:Actual data used: 1160247296
du: /data/media/.android_secure: No such file or directory|
once in recovery, if I try to format data, it says "Unable to format data". Log
Well I can't help, I'm in the same boat...hoping to get some insight from any responses you might get.
grey.ghost said:
Well I can't help, I'm in the same boat...hoping to get some insight from any responses you might get.
Click to expand...
Click to collapse
It's extremely unusual to get no responses to an issue like these here at XDA. leads me to believe it might be a very uncommon problem. The folks here are usually on the ball about any issue that has even arisen before.
That being said, I am going to try to flash the stock RUU back on from this link...
http://developer.motorola.com/produ...utm_source=supportforums&utm_term=unlockboard
After I finish, I re-root/unlock.
I'll let you know how it goes.
I'll let you know if I come up with something as well. So far I've managed to erase the sd card and maintain a constant boot loop.
Flashing all of the stock img, relocking, and unlocking again didn't do ****.
Found an original MZ600 SBF, which is what I need for verizon 3g xoom, I'm installing this via RSD Lite to see if it blows away whatever is causing the issue.
I was able to wipe the entire system and use adb to repeat the unlock and root steps. So far so good. I'm using the CWM 3.2.0.0 recovery image right now though. I have at least been able to get into a clean copy of a ROM and no bootloops yet. Can't restore data off old Nandroids, so I'm about to update to the newer CWM based recovery image and see if that will help.
I think I'm OK now.
I installed the SBF. Let all of the OTA updates come in including the ICS update where my 3g stops.
flashed the ROGUE recovery from fastboot.
I was able to format all partitions and install and boot CM9 nightly.
Me too, i was sweating hard for a bit, but was able to go through the entire process from stock, unlock, root, rogue recovery and then flashed CNA. Got that working without boot loops or fc and then advance restored data from a previous nandroid through rogue to get it back. A couple of apps had to be redownloaded from the market, but it looks as if I'm back in business. I want to try TWRP, but every time I do something screws up, so I think I'll stop trying.
Thanks for the help.
grey.ghost said:
Me too, i was sweating hard for a bit, but was able to go through the entire process from stock, unlock, root, rogue recovery and then flashed CNA. Got that working without boot loops or fc and then advance restored data from a previous nandroid through rogue to get it back. A couple of apps had to be redownloaded from the market, but it looks as if I'm back in business. I want to try TWRP, but every time I do something screws up, so I think I'll stop trying.
Thanks for the help.
Click to expand...
Click to collapse
Are you installing Twrp from goo manager. Cause I have not had any issues with the goo manager download. But did have issues with the zip file here on xda. I dont kknow if it is worth a try but that is how I did it.
Sent from my Xoom using xda app-developers app
Well sense this is a twrp related issue I would think u would have asked in my thread where I released the port for twrp to Xoom,
Having said that, at one point n time there was a note n the open about open script recovery. But its is also buried in the thread too. So I will answer your question and also presume a few things... and please correct me if I am wrong anywhere.
Once u set the download path in goo app to /data/media/goomanager/ and downloaded a ROM, clicked flash ROM, and entered recovery once u saw all the E/ update error u manually rebooted the Xoom and did not let the script finish installing the ROM? If I am correct that so far. That's what cause your additional problems. You basically rebooted recover while mid install of a ROM.
Now as stated it the twrp thread for Xoom, these errors are false errors and should be ignored. To add it the reassurance that they are intact false errors, from goo app select to flash a ROM again and simple allow the script to finish and then the tablet will reboot on its own when it is finished with the script. And you will be greeted with your new ROM you just successfully flashed.
Again let me know if I am wrong on assuming you forced a reboot mid install ( aka while u saw all the errors)
Sent from my Nexus 7 using Tapatalk 2
runandhide05 said:
Well sense this is a twrp related issue I would think u would have asked in my thread where I released the port for twrp to Xoom,
Having said that, at one point n time there was a note n the open about open script recovery. But its is also buried in the thread too. So I will answer your question and also presume a few things... and please correct me if I am wrong anywhere.
Once u set the download path in goo app to /data/media/goomanager/ and downloaded a ROM, clicked flash ROM, and entered recovery once u saw all the E/ update error u manually rebooted the Xoom and did not let the script finish installing the ROM? If I am correct that so far. That's what cause your additional problems. You basically rebooted recover while mid install of a ROM.
Now as stated it the twrp thread for Xoom, these errors are false errors and should be ignored. To add it the reassurance that they are intact false errors, from goo app select to flash a ROM again and simple allow the script to finish and then the tablet will reboot on its own when it is finished with the script. And you will be greeted with your new ROM you just successfully flashed.
Again let me know if I am wrong on assuming you forced a reboot mid install ( aka while u saw all the errors)
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
No, after pushing the TWRP recovery to the Xoom using adp, I would clean install a ROM and get one of two results....1) the ROM would run for a few seconds and then reboot, or 2) the ROM would run, but everything would fc. Fixing permissions, wiping everything, etc., wouldn't help the issue. No matter what I tried under TWRP, those were the results. I ended up having to start from scratch to negate whatever it was that was making the xoom go funky. Once I pushed rogue and followed the same process, I was back in business.
Sent from my Xoom using Tapatalk 2
Oke, so I'm at the stage that I want to backup the Asus stock ROM and install a custom rom.
When starting the backup from TWRP, it shows 2 errors:
E: Unable to find partition size for '/boot''
E: Unable to find partition size for '/recovery'
The backup does backup the other partitions, such as system, data, etc. and ends with the error:
E:Backup File size for '/.........//boot.emmc.win' is 0 bytes
So, did it backup the boot files? If not, i will not install a custom rom, which will probably overwrite the boot partifion files and leaves me with an unrestorable backup of the Stock ROM.
Any info or advise about these errors would be welcome.
TWRP version 2.6.0.0
Stock ROM 4.2.1
------
EDIT: installing TWRP 2.5.0.0 does not have this problem. Seems like a bug in 2.6.0.0, so don't use this version with 4.2.1 stock Asus Rom
remonv76 said:
Oke, so I'm at the stage that I want to backup the Asus stock ROM and install a custom rom.
When starting the backup from TWRP, it shows 2 errors:
E: Unable to find partition size for '/boot''
E: Unable to find partition size for '/recovery'
The backup does backup the other partitions, such as system, data, etc. and ends with the error:
E:Backup File size for '/.........//boot.emmc.win' is 0 bytes
So, did it backup the boot files? If not, i will not install a custom rom, which will probably overwrite the boot partifion files and leaves me with an unrestorable backup of the Stock ROM.
Any info or advise about these errors would be welcome.
TWRP version 2.6.0.0
Stock ROM 4.2.1
------
EDIT: installing TWRP 2.5.0.0 does not have this problem. Seems like a bug in 2.6.0.0, so don't use this version with 4.2.1 stock Asus Rom
Click to expand...
Click to collapse
2.6.0.0 has other bugs too so you did right in going with 2.5.0.0.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
2.5 didnt fix my issue completely
remonv76 said:
Oke, so I'm at the stage that I want to backup the Asus stock ROM and install a custom rom.
When starting the backup from TWRP, it shows 2 errors:
E: Unable to find partition size for '/boot''
E: Unable to find partition size for '/recovery'
The backup does backup the other partitions, such as system, data, etc. and ends with the error:
E:Backup File size for '/.........//boot.emmc.win' is 0 bytes
So, did it backup the boot files? If not, i will not install a custom rom, which will probably overwrite the boot partifion files and leaves me with an unrestorable backup of the Stock ROM.
Any info or advise about these errors would be welcome.
TWRP version 2.6.0.0
Stock ROM 4.2.1
------
EDIT: installing TWRP 2.5.0.0 does not have this problem. Seems like a bug in 2.6.0.0, so don't use this version with 4.2.1 stock Asus Rom
Click to expand...
Click to collapse
first time posting, xda has been my bible and guide for all of my unlocked adventures.
I had very similar symptoms and questions. I flashed the CM 10.2 and it worked fine (i had previously backed up my working PACrom and my CM10.1 before that)
I backed up my 10.2 and did a wipe and cache d.cache wipe. But couldn't restore (/boot & /recovery issues as well) so I then fastboot flashed twrp 2.5 back on and tried to restore from there and it wouldn't restore data, so I then wiped wiped and tried to flash the pacrom and gapps that had worked in the past with 2.5 and it worked! ( i thought ) until i realized it wouldn't get past the boot animation...I wiped and tried a CM10.1 restore and it worked again, but not really...it would get as far as the lockscreen and reboot. I was about to break my tab...and still am tempted to do so. This went on for a while until I gave up and went to bed.
After class, I did some more crawling through support and searching, and I read that flashing the original 10.1.6.15 back might help, so I did. It went through the motions, but got stuck on the boot animation, again. so I tried to get into twrp, but it was gone..
I fastboot twrp 2.5 on again, and twrp loads (hooray) and so I proceeded to wipe, cache/d.cache wipe, and install pacrom/gapps and it worked again again, but really didnt as it rebooted right after the "starting apps" screen appeared.
I know 10.2 runs 4.3, but I don't know enough about android OS to know exactly what flashing it may have changed. also I don't know why it is hanging at the startup of the os.
I tried searching but this is the closest post to what my issues are.
I don't know the ins and outs of droid partitioning/filesystems to feel comfortable just freely wiping parts, like I would a PC.
I just wish I knew a way to go back in time 36 hours and tell myself, DONT FLASH THOSE YET.
I am sorry this is such a long post, but I can't risk hard bricking this tablet like I did my old SG3 and since fastboot and twrp still load/function I have a great deal of hope someone will be kind enough to help me out.
Thank you.
EDIT/ADDENDUM:
- used "format data" on twrp, and wiped dalvik cache, cache, andsystem w.twrp 2.5, flashed new stock .27 firmware with 2.6, since the last one didnt work.
hope new firmware is twrp 2.5-friendly...2.6 lacks alot of utility features that 2.5 had
Last weekend, I successfully achieved Unlock and S-Off on my M8 with 5.0.1 thanks to Kingroot and Sunshine. I'd like to switch to Santod's stock debloated ROM (★ ☆ [ROM|RADIO|FIRMWARE][5.0.1] Stock-Rooted | Sense 6 | m8vzw | 09-09-15). Can I dirty-flash that over my current setup or will I need to wipe stuff?
I ALWAYS dirty flash first *B*U*T* I'm aware it may cause problems so I make a backup first, then dirty flash, if problems arise I wipe and do a clean install.
I get away with the dirty flash most of the time so it's worth a try, just know it's a gamble.
xs11e said:
I ALWAYS dirty flash first *B*U*T* I'm aware it may cause problems so I make a backup first, then dirty flash, if problems arise I wipe and do a clean install.
I get away with the dirty flash most of the time so it's worth a try, just know it's a gamble.
Click to expand...
Click to collapse
Thanks. I'll give dirty flashing a try and see how it goes.
For those that want a reference, in post 48 of the ROM's thread, Santod said a dirty flash should work if you're already on a 5.0.1 stock ROM.
http://forum.xda-developers.com/showpost.php?p=62782182&postcount=48
I'm getting an error flashing this ROM. The log shows this when flashing:
Code:
-- Installing busybox
[COLOR="Red"]E: Error executing updater binary in zip '/external_sd/ROMmy/4.17.605.9_M8_WL_L50_SENSE60_MR_Debloated.zip'[/COLOR]
Error flashing zip '/external_sd/ROMmy/4.17.605.9_M8_WL_L50_SENSE60_MR_Debloated.zip'
Updating partition details...
...done
Rebooting system automatically reboots into TWRP recovery.
Help?
I wish I knew of a way to bring this to santod040's attention without having to PM him.
Desert Dwarf said:
I'm getting an error flashing this ROM. The log shows this when flashing:
Code:
-- Installing busybox
[COLOR="Red"]E: Error executing updater binary in zip '/external_sd/ROMmy/4.17.605.9_M8_WL_L50_SENSE60_MR_Debloated.zip'[/COLOR]
Error flashing zip '/external_sd/ROMmy/4.17.605.9_M8_WL_L50_SENSE60_MR_Debloated.zip'
Updating partition details...
...done
Rebooting system automatically reboots into TWRP recovery.
Help?
I wish I knew of a way to bring this to santod040's attention without having to PM him.
Click to expand...
Click to collapse
Either you need to update your twrp, your sd card is not formatted to Fat32, or you have a corrupt download of the file.
Try it from internal...
Sent from my HTC6525LVW using Tapatalk
Or, I'm a doofus and I forgot to install the new kernel in the first place. Oy!
Once I installed the new kernel, all was well.
Desert "Too Easily Distracted by Shiny New ROMs" Dwarf