Develop Bugs

[Q] Rom Manager - Failed to Seek

Anytime I try to do anything through Rom Manager (flash a ROM, nandroid backup, etc.) upon rebooting into recovery, I get a white triangle with an yellow exclamation point. After pressing the power button, the following text is revealed along with the Clockwork Recovery Menu.
Finding update package...
Opening update package...
Verifying update package...
E:failed to seek in /cache/update.zip (Invalid argument)
E:signature verification failed
Installation aborted.
If I select advanced->Reboot Recovery after receiving the error, the device reboots. After this second reboot, the process continues as it should have after the first reboot. I've tried downgrading the version of my Clockwork Recovery, but it seems to have no effect.
Any ideas?

...
I believe the standard array of initial questions would be:
1) Did you flash S-OFF?
2) Is your card FAT32 formatted
3) Try redownloading the file using a different browser (to ensure a cache doesn't deliver the same update.zip without trying)

jdmba said:
I believe the standard array of initial questions would be:
1) Did you flash S-OFF?
Click to expand...
Click to collapse
Yes.
jdmba said:
2) Is your card FAT32 formatted
Click to expand...
Click to collapse
Yes.
jdmba said:
3) Try redownloading the file using a different browser (to ensure a cache doesn't deliver the same update.zip without trying)
Click to expand...
Click to collapse
This failure isn't specific to any one file. Besides, I don't think it's a corruption of the file since it works when I select "reboot recovery" from the first failed attempt. In fact, this even happens when choosing "Backup ROM" from ROM Manager.
On a side note, I've tried wiping cache in ROM Manager as well.

Toggle Signature Verification and/or is d/l corrupt?
In CWM, have you tried toggling the on or off setting for the signature verification, as well as the other toggle?
Also, I read some superb advice here:http://http://forum.xda-developers.com/showthread.php?t=765930
check out the advice in post # 285 and see if that fixes you up.

Everyone seems to think my downloads are corrupt. That is definitely not the problem. If they were corrupt, they wouldn't function after the first reboot. They would continue to fail. Let me try explain my problem another way...
Here's my device setup...
Radio - 2.15.00.07.28
Kernel - King's BFS #4
ROM - SR Vanilla RC 2
CWM Version - 2.5.0.5
ROM Manager Version - 2.0.2.6
Here's a process I'm following...
1. Open ROM Manager
2. Clear Download Cache (Just to be sure!)
3. Select Backup Current ROM which causes reboot into recovery.
4. Receive the error which I outlined in my first post. *NOTE* I have not downloaded nor chosen to flash ANY update.zip files. *NOTE*
5. Open the advanced menu in CMW and choose "Reboot recovery" which causes the phone to reboot into recovery.
6. The backup progresses like it should have after the first reboot.
Again, the process above does not involve the use of any downloaded update.zip files. No ROMS, no Kernels, etc.
Does ROM Manager create it's own update.zip file stored in /cache to execute whatever function it needs to after reboot? It appears that might be the case.
I've attempted to reinstall ROM Manager and downgrade to an early version of CWM in ROM Manager. Neither seem to have helped.

I had the same problem trying to flash the latest leedroid
I entered recovery, de-selected signature verification and then flashed the rom through recovery mode.
Flashed normally and up to now it looks like it worked (waiting for first boot)
Hope this helped

Both signature verification and script asserts are toggled off. This is why the update.zip will flash after the second reboot into recovery and manually.

In recovery, is cache, data, or system mounted? If so, can you unmount any/ all, and reboot?
Sent from my ADR6300 using XDA App

I just started having this problem today, at least i noticed it today. It acts as if the signature verification is enabled the first try and disabled the second time. I can't find ANY way to fix this but reboot recovery and it works... If anyone finds a solution, please post.
*edit* I also noticed the "Fix Permissions" utility doesn't work in ROM Manager. Dont know if this is related or not.

PIYIRIO said:
I just started having this problem today, at least i noticed it today. It acts as if the signature verification is enabled the first try and disabled the second time. I can't find ANY way to fix this but reboot recovery and it works... If anyone finds a solution, please post.
Click to expand...
Click to collapse
Did you change anything today? I found someone in the SR ROM thread today that started having the same problem.

No, only an app and removed it. I dont know how long it has been broke since I haven't used it since SR 3.0rc1.. got tired of the reminder for rc3 and it wouldn't automagically run the install.zip.

Interesting.... Please post as this shakes out.
Sent from my ADR6300 using XDA App

I have this same issue, I think it's an issue with Rom Manager. No matter what I try to do from there (Reboot to Recovery, make backup, flash zip, etc.) I get that string of messages.
If I download a file from ROM manager to be flashed, I have to move the file to the root of the sd card before booting to recovery for it to flash correctly. I have just gotten used to doing it this way.

srt4mn said:
I have this same issue, I think it's an issue with Rom Manager. No matter what I try to do from there (Reboot to Recovery, make backup, flash zip, etc.) I get that string of messages.
If I download a file from ROM manager to be flashed, I have to move the file to the root of the sd card before booting to recovery for it to flash correctly. I have just gotten used to doing it this way.
Click to expand...
Click to collapse
Me as well

PIYIRIO said:
*edit* I also noticed the "Fix Permissions" utility doesn't work in ROM Manager. Dont know if this is related or not.
Click to expand...
Click to collapse
If you look in the OP for the SR ROMS, you'll see that a known issue. He includes a fix_permissions binary instead.

I've reached out to the developer. Hopefully we will hear from him soon.

Can you guys try clearing your download cache, and then reflashing recovery?

Possible workaround
Koush said:
Can you guys try clearing your download cache, and then reflashing recovery?
Click to expand...
Click to collapse
Cache wipe have been tried, see post #3.
I have some info that may be valuable:
This evening I rooted my Desire (SLCD) using Unrevoked 3.14 and recovery-clockwork-2.5.0.7-bravo.img I realize this is the incredible forum but hold on.. hear me out
I observed the _exact_ same behavior:
- Yellow eclamation + second reboot to recovery would run backup, also happened when selecting "Reboot Into recovery" in RomManager (RM)
- Tried DL cache wipe in RomManager,
- Tried reflash of recovery
This fixed it for me:
- Re-root via Unrevoked 3.14 using recovery-clockwork-2.5.0.1-bravo-slcd.img
- Re-flash CM (this may be optional, I don't know)
- Boot ROM and start RM just to have it tell me I need to install recovery (obviosly didn't detect my 2.5.0.1-bravo-slcd)
- Allow RM to flash 2.5.0.7-bravo via download
- Now "Backup ROM" and "Reboot to recovery" works as intended
- RM reports 2.5.0.7-bravo installed, recovery booted (via RM) is 2.5.0.7-bravo BUT recovery booted using HBOOT (back+power on Desire) is 2.5.0.1-bravo-slcd (!)
Note: Incredible users should _not_ use -bravo recovery images(!) just outlining how I made it work to help you find a solution

Koush said:
Can you guys try clearing your download cache, and then reflashing recovery?
Click to expand...
Click to collapse
Worked for me. Thanks Koush!
Sent from my ADR6300 using XDA App

Didn't work for me.. I've tried everything that I can think of. Different SD cards, i've formated /data/ /cache/ and reinstalled..
i'm using virtuous 2.7

[Q] problems with flashing ARHD, what's going wrong?

first time posting here, and it's my first time trying to root my phone.
i used the toolkit, and that went without any problems. the phone was rooted and unlocked, and I downloaded CWM.
After I dl'ed CWM, I downloaded the ROM Android Revolution HD. There were two files I downloaded, the actual rom itself, and the firmware that comes alongside with it. They are both zip files, and I placed them both into my phone's storage.
I booted CWM, and chose to flash the actual ROM first. That worked fine, and I thought I should flash the firmware as well. Some error came up, and it said it was aborted. No big deal, so I reboot, and it shows the screen of the phone trying to boot for at least 30 minutes.
I restart my phone, and then I flash the ROM again. Tried it again, and I'm going to leave it attempting to boot into the ROM over night.
If I wake up with this problem still, what is a method to work around this?

okay it seems that i can not restore my phone back to the factory settings, and I can't connect to a mobile network.
the phone does now boot into android revolution HD, but I just need to figure out why I can't get on a mobile network

Welcome kyro- okay usually ARHD has 2 files and one is the ROM itself and the other may be the Superwipe file, they are both .zip files but perhaps you are confusing the Superwipe file with a firmware file (I am going from memory here so bear with me)
If this is the case go into CWM again and flash the Superwipe FIRST then flash the Rom file.
I am hoping it's something simple like this.
Just a suggestion
LL13-

i wish it was that simple, but i seem to have messed my firmware up in some way. everything else works fine, except for the radio. Baseband version is unknown at the moment, after wiping data cache system battery and using the super wipe as well.
from the website, here are the three links to download from
Firmware package
Flash it in recovery by selecting "apply update.zip from /sdcard"
Firmware package contains newest radio and bootloader for 4.0.x ROMs
Android Revolution HD 4.0.0
MD5 Checksum: 8C5E76C0665E088F721780BF1391C040
Direct link to 6 fast server that will randomly use one of our sources ---
Thanks to Mavy170, Whiskey103, MarcoHD, Pili21181, Lizard & Denngie ---
Super Wipe Lite
This script will erase and format your system and cache partition using EXT4 file-system
It will also wipe /data partition, but /data/media (virtual SD card) will be untouched
Click to expand...
Click to collapse
when i flash it in recovery mode, this is the error
assert failed: getprop("ro.product.device") == "maguro" || getprop("ro.build.product") == "maguro"
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
so i can't connect to a mobile network until this is properly installed i'm assuming.

[Q] Help with CW Recovery please

Hello, I've got an S3 from Bell Canada earlier this week.
I followed a tutorial here: How to Root U.S. and Canada Galaxy S3 AT&T, T-Mobile, Sprint/US Ceullar! [Fail-Proof][Noob-Proof] to root it, all went great! (wont let me post the actual link yet, but that was the name of the article)
I'm trying to put task650's 4.2.2 build on but it failed, so i recovered from my backup.. worked great!
When i researched my error it indicated i may have an outdated CWRecovery in stalled. I've got 5.5.0.4.. When i check the clockworkmod website it says the latest version is 6.0.3.1.. awesome.
This is where i'm hitting a wall. I see the .img file there, but i cant find a .tar file to use to flash my phone with Odin.
I've installed ROM MANAGER (even bought the full version) but it's behaving as if i dont have a recovery mod installed.. even though i do. When i go through the 'install' options in ROM MANAGER it only lists the metroPCS version of the S3.. where I need the ATT version.
So that's where i'm at. i *think* i need to find 6.0.3.1 for an SGH-i747m in tar format. i've been googling and searching forums but i'm coming up empty. This is my first android device and it's a week old.. everything i've done i've learned this week so please forgive me if i'm missing the obvious here.
thanks in advance

If I was you, I'd just forget CWM and install TWRP. Install goomanager from the play store, open it up, hit the menu button and select to install an open recovery script. Voilà, you have TWRP recovery.

itrunner said:
Hello, I've got an S3 from Bell Canada earlier this week.
I followed a tutorial here: How to Root U.S. and Canada Galaxy S3 AT&T, T-Mobile, Sprint/US Ceullar! [Fail-Proof][Noob-Proof] to root it, all went great! (wont let me post the actual link yet, but that was the name of the article)
I'm trying to put task650's 4.2.2 build on but it failed, so i recovered from my backup.. worked great!
When i researched my error it indicated i may have an outdated CWRecovery in stalled. I've got 5.5.0.4.. When i check the clockworkmod website it says the latest version is 6.0.3.1.. awesome.
This is where i'm hitting a wall. I see the .img file there, but i cant find a .tar file to use to flash my phone with Odin.
I've installed ROM MANAGER (even bought the full version) but it's behaving as if i dont have a recovery mod installed.. even though i do. When i go through the 'install' options in ROM MANAGER it only lists the metroPCS version of the S3.. where I need the ATT version.
So that's where i'm at. i *think* i need to find 6.0.3.1 for an SGH-i747m in tar format. i've been googling and searching forums but i'm coming up empty. This is my first android device and it's a week old.. everything i've done i've learned this week so please forgive me if i'm missing the obvious here.
thanks in advance
Click to expand...
Click to collapse
Another choice is download andromizer from play store and then download the .img file. Next use andromizer to make a flashable recovery and now you have a flashable CWM....or use the goomanager method above. I prefer TWRP anyway but if you want CWM what I stated works well.

If you go with twrp, remember to make a backup as your cwm backup will no longer be of use to you anymore.
If you decide to remain on cwm, there is a recovery flashable touch version 6.0.3.1 in the link in my signature. At the bottom of post #2. Boot into recovery, flash zip, advanced > reboot recovery

xBeerdroiDx said:
If you go with twrp, remember to make a backup as your cwm backup will no longer be of use to you anymore.
If you decide to remain on cwm, there is a recovery flashable touch version 6.0.3.1 in the link in my signature. At the bottom of post #2. Boot into recovery, flash zip, advanced > reboot recovery
Click to expand...
Click to collapse
I just tried both, the TWM fails with an MD5 checksum error before it even reboots (right after the download)
When i try your 6.0.3.1 file i get the following:
"assert failed: getprop("ro.product.device") == "d2att" || getprop("ro.product.device") == "d2att" e:Error in /sdcard/CWMTouch-recovery_ATT-6.0.3.1.zip (Status 7) Installation Aborted
:silly:

By "both" do you mean both cwm flashable zips in that post or did you mean you tried flashing a cwm one AND a twrp one?

xBeerdroiDx said:
By "both" do you mean both cwm flashable zips in that post or did you mean you tried flashing a cwm one AND a twrp one?
Click to expand...
Click to collapse
Hey xBeerdroidDx,
My exact steps were:
1.) Tried TWRP (seen his reply before yours) it failed the checksum on the download.
2.) Seen your post, copied over the 6.0.3.1 zip file of yours, booted to recovery and tried to install. Got the error i posted above... rebooted.
3.) Tried TWRP again, went successful this time.
I think i still have something wonky.. ROM MANAGER still says i have no recovery installed, and if I go back into GOOMANAGER it's behaving as if i didnt install a recovery yet either.. even though it just did.
I did make a backup using TWRP as soon as it was installed.. i'm not brave enough to try the 4.2.2 yet as it seems something is still screwy. or i'm just being overly paranoid

If you booted into twrp and were able to perform a successful backup then you're all set.

Here's a copy of 6.0.3.1 touch i just made. Try it
http://d-h.st/HTi
---------- Post added at 04:01 PM ---------- Previous post was at 03:50 PM ----------
itrunner said:
Hey xBeerdroidDx,
My exact steps were:
1.) Tried TWRP (seen his reply before yours) it failed the checksum on the download.
2.) Seen your post, copied over the 6.0.3.1 zip file of yours, booted to recovery and tried to install. Got the error i posted above... rebooted.
3.) Tried TWRP again, went successful this time.
I think i still have something wonky.. ROM MANAGER still says i have no recovery installed, and if I go back into GOOMANAGER it's behaving as if i didnt install a recovery yet either.. even though it just did.
I did make a backup using TWRP as soon as it was installed.. i'm not brave enough to try the 4.2.2 yet as it seems something is still screwy. or i'm just being overly paranoid
Click to expand...
Click to collapse
Goomanager will always install recvoery if you try to....you are using ROM manager or Goo manager to actually install install the rom's are you ?

hednik said:
Here's a copy of 6.0.3.1 touch i just made. Try it
---------- Post added at 04:01 PM ---------- Previous post was at 03:50 PM ----------
[/COLOR]
Goomanager will always install recvoery if you try to....you are using ROM manager or Goo manager to actually install install the rom's are you ?
Click to expand...
Click to collapse
That was my plan, but before ROM MANAGER wouldn't let me do anything as it kept saying i didn't have a recovery installed (which it still does).
Am i pretty safe to try applying my 4.2.2 ROM on there at this point? I've done 2 backups just to be safe hah

itrunner said:
That was my plan, but before ROM MANAGER wouldn't let me do anything as it kept saying i didn't have a recovery installed (which it still does).
Am i pretty safe to try applying my 4.2.2 ROM on there at this point? I've done 2 backups just to be safe hah
Click to expand...
Click to collapse
Do not use an app to flash a ROM. Always boot into recovery to flash them.
Make sure you do a complete wipe and flash in the recovery as well.
Sent from my SAMSUNG-SGH-I747 using xda premium

xBeerdroiDx said:
If you booted into twrp and were able to perform a successful backup then you're all set.
Click to expand...
Click to collapse
It bombed again in TWRP. Did my 3rd recovery of the day
Here's the error, looks the same as when i was doing it via CWRecovery
-- Dalvik Cache Wipe Complete!
I:command is: 'install' and I:value is: '/sdcard/aokp_JB_4.2.2_d2att-ota-eng.task650-4.23.2013.zip'
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
Installing zip file '/sdcard/aokp_JB_4.2.2_d2att-ota-eng.task650-4.23.2013.zip'
Installing '/sdcard/aokp_JB_4.2.2_d2att-ota-eng.task650-4.23.2013.zip'...
Checking for MD5 file...
I:Cannot find file /sdcard/aokp_JB_4.2.2_d2att-ota-eng.task650-4.23.2013.zip.md5
Skipping MD5 check: no MD5 file found.
Warning: No file_contexts
script aborted: assert failed: getprop("ro.product.device") == "d2att" || getprop("ro.build.product") == "d2att"
assert failed: getprop("ro.product.device") == "d2att" || getprop("ro.build.product") == "d2att"
E:Error executing updater binary in zip '/sdcard/aokp_JB_4.2.2_d2att-ota-eng.task650-4.23.2013.zip'
E:Error installing zip file '/sdcard/aokp_JB_4.2.2_d2att-ota-eng.task650-4.23.2013.zip'
Done processing script file

hednik said:
Do not use an app to flash a ROM. Always boot into recovery to flash them.
Make sure you do a complete wipe and flash in the recovery as well.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
We just replied at the same time, my error is posted in my previous reply. If nothing else, recovering from backup 3 times today has built my confidence a bit hah:good:

i get the impression from this error: script aborted: assert failed: getprop("ro.product.device") == "d2att" || getprop("ro.build.product") == "d2att"
that the script is calling my device name and d2att is not being returned. how can i figure out what it really is?

itrunner said:
i get the impression from this error: script aborted: assert failed: getprop("ro.product.device") == "d2att" || getprop("ro.build.product") == "d2att"
that the script is calling my device name and d2att is not being returned. how can i figure out what it really is?
Click to expand...
Click to collapse
Looked in the build.prop file, mine is ro.product.device=d2can
so i guess that's why it's failing.

used root toolbox, changed the d2can to d2att, tried again.
failed with getprop("ro.product.device") == ""
this time nothing, i think i'm getting closer. will keep updating this thread in case anyone has a suggestion

I've Solved this!!
1.) Root Toolbox to change build.prop's ro.device from d2can to d2att
2.) Rom Manager, download and apply Clockwork Recover , downloaded and applied 6.0.3.1
3.) Boot to recovery.. BACKUP to internal memory, BACKUP #2 to external SD (paranoid)
4.) Wipe system, Wipe Cache, Wipe Davlink
5.) Applied my custom Rom with success

its good to see users figuring things out for themselves through research and trial/error. the best way to learn.
congrats, buddy.

[Q] Boot Hangup Error After Attemption Internal Memory Increase

Completed the following successfully on my Wildfire S 510c:
Unlocked
Installed CWM v5.0.2.6
Rooted
I wanted to find a way to either move the whole system to the SD card or to increase the Internal memory using the SD card.
I found a guide here explaining how to increase the internal memory using SD card, but after following the instructions to the T my phone hangs up on the white screen with HTC logo every time.
To make matters worse, the partitioned portion of the SD card cannot be seen in windows explorer when I try to access the SD via CWM, only the portion that was left over. I fear that since this problem occurred right after I installed cm-7-20120717-UNOFFICIAL-marvel recovery over the previous CWM I had and the Data2SDInstallerNXE2 I'm speculating 1 of 2 things have occurred: Either the Unofficial CWM is corrupted (All functions work properly inside recovery) or an error occurred where the system files were not properly copied into the newly created partition and so it tries to boot system from empty space.
I'm at a total loss where to go from here. I don't know of any free programs that can see all the partitions of the SD card where Windows cannot, let alone unpartition it, and even then how to set it back up to where it boots up where it needs to. I've tried to reinstall the previous CWM I had via zip installer but it give an "Installation Aborted".
Someone plz halp! lol
Ok, I found that under SD partition in CWM if you select different partition size it will remove the old partition, this still doesn't fix the hangup though.
Now it doesn't hang up, but keeps going back to bootloader screen. I think I should stop before it get worse and wait for a response. XD
Tried flashy method in an attempt to set phone back to locked and unrooted status. Only thing it did was set phone in relocked status. I'm taking a break for awhile, spent too many hours on this ><

LyleVertigo said:
Completed the following successfully on my Wildfire S 510c:
Unlocked
Installed CWM v5.0.2.6
Rooted
I wanted to find a way to either move the whole system to the SD card or to increase the Internal memory using the SD card.
I found a guide here explaining how to increase the internal memory using SD card, but after following the instructions to the T my phone hangs up on the white screen with HTC logo every time.
To make matters worse, the partitioned portion of the SD card cannot be seen in windows explorer when I try to access the SD via CWM, only the portion that was left over. I fear that since this problem occurred right after I installed cm-7-20120717-UNOFFICIAL-marvel recovery over the previous CWM I had and the Data2SDInstallerNXE2 I'm speculating 1 of 2 things have occurred: Either the Unofficial CWM is corrupted (All functions work properly inside recovery) or an error occurred where the system files were not properly copied into the newly created partition and so it tries to boot system from empty space.
I'm at a total loss where to go from here. I don't know of any free programs that can see all the partitions of the SD card where Windows cannot, let alone unpartition it, and even then how to set it back up to where it boots up where it needs to. I've tried to reinstall the previous CWM I had via zip installer but it give an "Installation Aborted".
Someone plz halp! lol
Ok, I found that under SD partition in CWM if you select different partition size it will remove the old partition, this still doesn't fix the hangup though.
Now it doesn't hang up, but keeps going back to bootloader screen. I think I should stop before it get worse and wait for a response. XD
Tried flashy method in an attempt to set phone back to locked and unrooted status. Only thing it did was set phone in relocked status. I'm taking a break for awhile, spent too many hours on this ><
Click to expand...
Click to collapse
Instead of the Data2sd provided in the tutorial, try using INT2EXTV2+(You can easily find it using the search function).....Do remember to flash it after the flashed rom has booted once
Also, you can not see the second partition of the SDCard on Windows...........Windows doesn't support it(EXT partitions)

csoulr666 said:
Instead of the Data2sd provided in the tutorial, try using INT2EXTV2+(You can easily find it using the search function).....Do remember to flash it after the flashed rom has booted once
Also, you can not see the second partition of the SDCard on Windows...........Windows doesn't support it(EXT partitions)
Click to expand...
Click to collapse
Ok, so as the current state of the phone, do I just wipe everything and then run CWM, reboot it then when it comes up again install Int2extv2+ from zip, that's it? Does the relock prevent me from taking the steps neccessary from getting back into the phone? and if so what would I need to do to unlock it again when I only have access to fastboot/bootloader/CWM?

LyleVertigo said:
Ok, so as the current state of the phone, do I just wipe everything and then run CWM, reboot it then when it comes up again install Int2extv2+ from zip, that's it? Does the relock prevent me from taking the steps neccessary from getting back into the phone? and if so what would I need to do to unlock it again when I only have access to fastboot/bootloader/CWM?
Click to expand...
Click to collapse
Unlock the Bootloader, get into CWM, wipe, flash the rom of your choosing, let it boot once, then go back to CWM and flash INT2EXTV2+

csoulr666 said:
Unlock the Bootloader, get into CWM, wipe, flash the rom of your choosing, let it boot once, then go back to CWM and flash INT2EXTV2+
Click to expand...
Click to collapse
Ok, so here is what I've done:
Re-unlocked √
Wipe date/Factory Reset √
Wipe Cache Partition √
Flashed cm-10.1-20130703-4.3-F-NIGHTLY-marvel √
Reboot System Now (Hangs on HTC white screen) - pulled battery out to turn off
Went back into bootloader -> CWM and installed INT2EXTV2+ via zip installer (selected no for SWAP2INT) √
Reboot - Hangs on HTC white screen. X
Here is a question, would S-ON affect this in any way? I've done the partial S-off procedure (which was recommended to me) but the bootloader still says S-On. If it needs to be completely off and shown as S-off would you show me a proper procedure link for me get that taken care of (but only if absolutely necessary)?
I really appreciate your help so far.

LyleVertigo said:
Ok, so here is what I've done:
Re-unlocked √
Wipe date/Factory Reset √
Wipe Cache Partition √
Flashed cm-10.1-20130703-4.3-F-NIGHTLY-marvel √
Reboot System Now (Hangs on HTC white screen) - pulled battery out to turn off
Went back into bootloader -> CWM and installed INT2EXTV2+ via zip installer (selected no for SWAP2INT) √
Reboot - Hangs on HTC white screen. X
Here is a question, would S-ON affect this in any way? I've done the partial S-off procedure (which was recommended to me) but the bootloader still says S-On. If it needs to be completely off and shown as S-off would you show me a proper procedure link for me get that taken care of (but only if absolutely necessary)?
I really appreciate your help so far.
Click to expand...
Click to collapse
Is there a chance you have a 2012 model of the WFS??? If so, see if the rom is compatible with the 2012 WFS.......some roms, like the OWL project(CM10.1) is compatible

csoulr666 said:
Is there a chance you have a 2012 model of the WFS??? If so, see if the rom is compatible with the 2012 WFS.......some roms, like the OWL project(CM10.1) is compatible
Click to expand...
Click to collapse
No go, Owl project roms are for GSM only. Mine does not have SIM card.

LyleVertigo said:
No go, Owl project roms are for GSM only. Mine does not have SIM card.
Click to expand...
Click to collapse
Why didn't you tell that before!! Look for roms with "marvelc" in them........ That's why it doesn't go past the HTC screen

csoulr666 said:
Why didn't you tell that before!! Look for roms with "marvelc" in them........ That's why it doesn't go past the HTC screen
Click to expand...
Click to collapse
The only one I was able to find that specifically called for CDMA that had a working dl link so far is cm-9.1.0-CRYPTOMILK-ALPHA9-marvelc.zip .
I tried to flash it but got this:
Installing update...
assert failed: getprop("ro.produ
ct.device") == "marvelc" || getp
rop("ro.build.product") == "marv
elc"
E:Error in /sdcard/cm-9.1.0-CRYP
TOMILK-ALPHA9-marvelc.zip
(Status 7)
Installation Aborted.
I did all the clearing and formatting required prior.

LyleVertigo said:
The only one I was able to find that specifically called for CDMA that had a working dl link so far is cm-9.1.0-CRYPTOMILK-ALPHA9-marvelc.zip .
I tried to flash it but got this:
Installing update...
assert failed: getprop("ro.produ
ct.device") == "marvelc" || getp
rop("ro.build.product") == "marv
elc"
E:Error in /sdcard/cm-9.1.0-CRYP
TOMILK-ALPHA9-marvelc.zip
(Status 7)
Installation Aborted.
I did all the clearing and formatting required prior.
Click to expand...
Click to collapse
Look for the ones with CDMA written in the thread, here are some CDMA roms I found
http://forum.xda-developers.com/showthread.php?t=2245617
http://forum.xda-developers.com/showthread.php?t=1861623
http://forum.xda-developers.com/showthread.php?t=2274173
Click to expand...
Click to collapse

csoulr666 said:
Look for the ones with CDMA written in the thread, here are some CDMA roms I found
Click to expand...
Click to collapse
I tried all those roms and same error, which leads me to believe that the rom isn't the problem.
However, all of that is irrelevant now, as I gave it to someone who said they knew how to fix it and they bricked it completely, so I just told him to keep it. lol

LyleVertigo said:
I tried all those roms and same error, which leads me to believe that the rom isn't the problem.
However, all of that is irrelevant now, as I gave it to someone who said they knew how to fix it and they bricked it completely, so I just told him to keep it. lol
Click to expand...
Click to collapse
U have marvelc no marvel mobile
Try with fastboot flash custom rom (boot.img,system.img, and recovery.img)
But dont forgot before factory reset.
U will have custom rom mobile, and worked mobile
If u can change rom, u must find marvelc roms, and first try cm7 rom
I too start with this rom (cm7)

Can't update firmware through TWRP

Hey all,
I'm having some trouble trying to update firmware packages through TWRP (and any ROM other than xiaomi.eu). I'm trying to flash this rom and I've downloaded both the ROM and the firmware as linked on the page. When I try to flash both through TWRP, the script succeeds but returns a value of 1. I'm assuming that means it failed, shouldn't it return 0 on success?
After flashing I've tried to boot to system, but it loops through the boot animation and a TWRP "Open Recovery Script" screen. Not too sure what that means. I'm running TWRP version 3.2.0-0.
I didn't have any of these problems with my Mi 5. Not too sure what I'm doing wrong. Can anyone guide me in the right direction?
Thanks

JaredG_ said:
Hey all,
I'm having some trouble trying to update firmware packages through TWRP (and any ROM other than xiaomi.eu). I'm trying to flash this rom and I've downloaded both the ROM and the firmware as linked on the page. When I try to flash both through TWRP, the script succeeds but returns a value of 1. I'm assuming that means it failed, shouldn't it return 0 on success?
After flashing I've tried to boot to system, but it loops through the boot animation and a TWRP "Open Recovery Script" screen. Not too sure what that means. I'm running TWRP version 3.2.0-0.
I didn't have any of these problems with my Mi 5. Not too sure what I'm doing wrong. Can anyone guide me in the right direction?
Thanks
Click to expand...
Click to collapse
Did you format data and type yes in TWRP?
For a lot of ROM changes you need to format the whole data partition not just wipe it.

Dobsgw said:
Did you format data and type yes in TWRP?
For a lot of ROM changes you need to format the whole data partition not just wipe it.
Click to expand...
Click to collapse
Yes I have.
I'm not too sure if I'm supposed to be rebooting to system afterwards. It's rebooting into MIUI 9 which sets up the internal storage and lets me copy the firmware updates onto the device through TWRP, but I'm still getting that 'return 1' and boot loop issue.

JaredG_ said:
Yes I have.
I'm not too sure if I'm supposed to be rebooting to system afterwards. It's rebooting into MIUI 9 which sets up the internal storage and lets me copy the firmware updates onto the device through TWRP, but I'm still getting that 'return 1' and boot loop issue.
Click to expand...
Click to collapse
Flash the firmware, then the ROM, then gapps if you use it.
Then format data and reboot.
That should get things working for you.
Then after that if you're flashing the same ROM you wont need to do a format of data you can just wipe it and keep internal storage

Dobsgw said:
Flash the firmware, then the ROM, then gapps if you use it.
Then format data and reboot.
That should get things working for you.
Then after that if you're flashing the same ROM you wont need to do a format of data you can just wipe it and keep internal storage
Click to expand...
Click to collapse
I can't seem to update the firmware. I'm definitely doing something wrong it's never taken me this long on any of my devices.
Trying to flash the Mi 6 Global 7.11.2 firmware gives this log in TWRP:
package_extract_file took 00s
...
SetMetadataFn took 00s
RunProgramFn took 00s
script succeeded: result was [1.000000]
Updating partition details...
...done
Click to expand...
Click to collapse
Then trying to flash the ROM afterwards gives me error 7. Where am I going wrong with the firmware update?
I bet at the end of all this it's going to be just a simple mistake haha :/

JaredG_ said:
I can't seem to update the firmware. I'm definitely doing something wrong it's never taken me this long on any of my devices.
Trying to flash the Mi 6 Global 7.11.2 firmware gives this log in TWRP:
Then trying to flash the ROM afterwards gives me error 7. Where am I going wrong with the firmware update?
I bet at the end of all this it's going to be just a simple mistake haha :/
Click to expand...
Click to collapse
Its not your fault.
Error 7 is common. It means the zip is looking for the device name and getting the wrong one. Probably looking for "Sagit" or something and TWRP is saying "this is a Mi 6"
Scripts follow exact logic haha.
So my recommendation is to copy the RR zip to PC.
Use 7zip to extract just the updater script from the meta-inf file.
Then use notepad++ to delete the very top few lines which are about checking device type.
Then copy it back to the zip and flash it.
It won't check what device it is flashing on and will flash regardless.
That's fine as you know its the correct device.
Seems like the firmware package is flashing fine.
You can also go to the LineageOS 15 thread and download the firmware package I made from the latest miui firmware. Its on the OP by NisseCool.

Dobsgw said:
Its not your fault.
Error 7 is common. It means the zip is looking for the device name and getting the wrong one. Probably looking for "Sagit" or something and TWRP is saying "this is a Mi 6"
Scripts follow exact logic haha.
So my recommendation is to copy the RR zip to PC.
Use 7zip to extract just the updater script from the meta-inf file.
Then use notepad++ to delete the very top few lines which are about checking device type.
Then copy it back to the zip and flash it.
It won't check what device it is flashing on and will flash regardless.
That's fine as you know its the correct device.
Seems like the firmware package is flashing fine.
You can also go to the LineageOS 15 thread and download the firmware package I made from the latest miui firmware. Its on the OP by NisseCool.
Click to expand...
Click to collapse
I'm not convinced that the firmware is flashing correctly. This is the error message from trying to flash the ROM:
Can't install this package on top of incompatible data. Pleas try another package or run a factory reset
Updater process ended with ERROR: 7
Click to expand...
Click to collapse
This was after I flashed the firmware package that you put together from the LineageOS 15.0 thread and after formatting data and rebooting into MIUI. Flashing the firmware gave the same log output as my previous post.
I had a look at the updater script, and it's definitely passing the first assert statements. This is the line with the error message:
HTML:
run_program("/tmp/install/bin/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
This is killing me
EDIT: Disregard my comment about the firmware not updating. I had a look at the firmware update script and from the TWRP log it seems like it is flashing fine.

Fixed.
Firmware was flashing fine. I need to learn to properly read instructions.
I had formatted data through the interface where you need to type 'yes', but I didn't do an advanced wipe and tick data (I swear I had done it already)
Silly mistakes. Learn to read instructions, kids haha
Thank you for your help

JaredG_ said:
Fixed.
Firmware was flashing fine. I need to learn to properly read instructions.
I had formatted data through the interface where you need to type 'yes', but I didn't do an advanced wipe and tick data (I swear I had done it already)
Silly mistakes. Learn to read instructions, kids haha
Thank you for your help
Click to expand...
Click to collapse
That's really strange. Format should do the same as wipe just more effective.
Glad it's all working!