Hello
Here i would love to present the Dev-DB of Firehound ROM for Coolpad Note 3.
This is for the Unofficial builds
Link for the project : https://forum.xda-developers.com/android/development/unofficial-firehound-rom-t3636230
While flashing rom im getting error 7
...what should I do currently I am on 360OS
manishj976 said:
While flashing rom im getting error 7
...what should I do currently I am on 360OS
Click to expand...
Click to collapse
Use the recovery recommended. The recovery you might be having is 3.0.2-1, where as this ROM gets installed with recovery 3.0.2-0. The error is due the /dev/..../by-name/system path difference in the different versions of the recovery.
Flash the recommended recovery using SP FLash, or change the path of /dev/..../by-name/system in the update-script in the ROM.
original path in the script
block_image_update("/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat")
change to
block_image_update("/dev/block/platform/mtk-msdc.0/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat")
manishj976 said:
While flashing rom im getting error 7
...what should I do currently I am on 360OS
Click to expand...
Click to collapse
maybe an issue with the recovery...may have to get a new one... that is compatible with the Android version of the rom you are flashing
Related
I have an SGS2 (former running with Android 2.3.5 and SpeedmodKernel). I fullwiped it in order to install a Custom Rom. Then I tried to install the custom-roms .zip file in CWM (v5.0.2.3) with "install from sd-card", I chose the ROM I wished to install and then I get the following error:
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device")=="galaxys2" || getprop("ro.build.product")="galaxys2" || getprop("ro.product.device")=="i9100" || getprop("ro.build.product")="GT-I9100" [...]
E: Error in /emmc/CM/cm-10.1-20130204-NIGHTLY-i9100.zip (Status7)
Installation aborted
I wiped everything, so I can't do anything except entering DownloadMode or Recovery!
Can you help me? What can I do?
Indurus said:
I have an SGS2 (former running with Android 2.3.5 and SpeedmodKernel). I fullwiped it in order to install a Custom Rom. Then I tried to install the custom-roms .zip file in CWM (v5.0.2.3) with "install from sd-card", I chose the ROM I wished to install and then I get the following error:
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device")=="galaxys2" || getprop("ro.build.product")="galaxys2" || getprop("ro.product.device")=="i9100" || getprop("ro.build.product")="GT-I9100" [...]
E: Error in /emmc/CM/cm-10.1-20130204-NIGHTLY-i9100.zip (Status7)
Installation aborted
I wiped everything, so I can't do anything except entering DownloadMode or Recovery!
Can you help me? What can I do?
Click to expand...
Click to collapse
Hi. I think is because SpeedmodKernel doesn't support JB.
You can try flash a differnt kernel like this one or install some ICS based ROM.
_FreaK_ said:
Hi. I think is because SpeedmodKernel doesn't support JB.
You can try flash a differnt kernel like this one or install some ICS based ROM.
Click to expand...
Click to collapse
Thank you!
But this Error occurs even when I try to install CM7 (which isn't based on JB as far as I know). It simply occurs at every .zip I try to install!
Indurus said:
Thank you!
But this Error occurs even when I try to install CM7 (which isn't based on JB as far as I know). I don't think it's a problem with JB...
Click to expand...
Click to collapse
Try CM9. CM7 is based on gingerbread.
_FreaK_ said:
Try CM9. CM7 is based on gingerbread.
Click to expand...
Click to collapse
I tried 7,9 and 10. Same error with each of those!
Indurus said:
I tried 7,9 and 10. Same error with each of those!
Click to expand...
Click to collapse
I get the same errors with CM roms on my i9100p so i flash other rom. Try to flash some other kernel.
I'm usin siyah kernel 5.x with Sensation rom 4.1 and is work like a charm.
_FreaK_ said:
I get the same errors with CM roms on my i9100p so i flash other rom. Try to flash some other kernel.
I'm usin siyah kernel 5.x with Sensation rom 4.1 and is work lake a charm.
Click to expand...
Click to collapse
My Phone is completely blank (except of the cwm and download modus).
Is it possible to flash any SiyahKernel for my s2...what do I have to take care of?
Indurus said:
My Phone is completely blank (except of the cwm and download modus).
Is it possible to flash any SiyahKernel for my s2...what do I have to take care of?
Click to expand...
Click to collapse
Download siyah fom gokhanmoral' s homepage. Siyah v5.0.1 (v6beta 4 will boot only leaked lsj version).
CWM zip version and put it to external sd and flash it in cwm recovery.
I just flash it and have no issues at all.
_FreaK_ said:
Download siyah fom gokhanmoral' s homepage. Siyah v5.0.1 (v6beta 4 will boot only leaked lsj version).
CWM zip version and put it to external sd and flash it in cwm recovery.
I just flash it and have no issues at all.
Click to expand...
Click to collapse
It will also boot LS8 based roms. I'm using it with Disaster ROM v.8
Then it's better to flash Dorimanx.
It has ICS & JB support and from what I read on forum is very good kernel. Will try it in near future.
Indurus said:
My Phone is completely blank (except of the cwm and download modus).
Is it possible to flash any SiyahKernel for my s2...what do I have to take care of?
Click to expand...
Click to collapse
try flashing latest CWM Philz or dorimanx or siyah and then try flashing JB 4.1.2 based ROM.
Hi friend
googled but, looks something different to ..
Im getting installation aborted status 7 during installation of kitkat
ROMs like cm-11-20140101-INFECTED-i9100 and super nexus
The same above rom has been flashed before worked well and no problem, now not able flash
tried using recovery.. original CWM apolo kernal(CWM), Philz kernal(CWM) and even TWRP
and deleted asserts in rom update scrip file still error status 7
But the thing is i can flash NeatROM lite using above Recovery
Im little scared i think it has been bricked?
Please help regarding above error
thippesh said:
Hi friend
googled but, looks something different to ..
Im getting installation aborted status 7 during installation of kitkat
ROMs like cm-11-20140101-INFECTED-i9100 and super nexus
The same above rom has been flashed before worked well and no problem, now not able flash
tried using recovery.. original CWM apolo kernal(CWM), Philz kernal(CWM) and even TWRP
and deleted asserts in rom update scrip file still error status 7
But the thing is i can flash NeatROM lite using above Recovery
Im little scared i think it has been bricked?
Please help regarding above error
Click to expand...
Click to collapse
its not bricked, if it was bricked you can't even start the phone so no worries.
first make sure your phone is a gt9100, if it is try to flash something else (just for a test), or download a other rom, like slimsaber. Please give a report back :highfive:
You flash the CWM 6.0.4.5 (KK Compatible)?
Just use a up to to date CWM version. First, flash gustavo's Kitkat kernel, then flash a kitkat rom. For example, you cannot install a KK rom with 6.0.3.7 recovery. You need at least CWM 6.0.4.5 or TWRP 2.6.1, to be able to flash a KK rom. So, its not bricked or something.
Dampierre said:
Just use a up to to date CWM version. First, flash gustavo's Kitkat kernel, then flash a kitkat rom. For example, you cannot install a KK rom with 6.0.3.7 recovery. You need at least CWM 6.0.4.5 or TWRP 2.6.1, to be able to flash a KK rom. So, its not bricked or something.
Click to expand...
Click to collapse
Exatcly. I raccomanded flash a KK ROM from CM 10.2 / ROM based-on-10.2
COMMON PROBLEM !
1. if your in TWRP install blazing kernal to get the lower version of cwm
2. if your getting error on cwm flash an older version CM 10.2
3. that's it fixed
4. or if your in cm 10.2 and still getting error in the sense corrupted download
hope it helps :good:
Dampierre said:
Just use a up to to date CWM version. First, flash gustavo's Kitkat kernel, then flash a kitkat rom. For example, you cannot install a KK rom with 6.0.3.7 recovery. You need at least CWM 6.0.4.5 or TWRP 2.6.1, to be able to flash a KK rom. So, its not bricked or something.
Click to expand...
Click to collapse
Thank you all everyone to your kind replies and helping me out this problem,
has been solved by first flashing the gustavo's Kitkat kernel or kitkat Compatible Kernal
after that i can flash the KK rom
thanks thank you guys
-Marco said:
Exatcly. I raccomanded flash a KK ROM from CM 10.2 / ROM based-on-10.2
Click to expand...
Click to collapse
Does this mean I have to install ROM from CM 10.2?
This means I have to clean all my data n cache 1st. Thn install CM 10.2?
Thn clear data n cache again?
Thn install the Kit Kat ROM n GApps?
Yep
Can any one tell me when we flash a ROM on MI note 4 from
MIUI to any custom rom,i mean to flash a rom for first time
We need a file to flash before flashing any custom rom ,
By that file we dont able to stuck on that MI logo.
jatin.t.16 said:
Can any one tell me when we flash a ROM on MI note 4 from
MIUI to any custom rom,i mean to flash a rom for first time
We need a file to flash before flashing any custom rom ,
By that file we dont able to stuck on that MI logo.
Click to expand...
Click to collapse
If you are upgrading to a Lineage OS 7.1x ROM, then this is the file
https://www.androidfilehost.com/?fid=817550096634766008
DarthJabba9 said:
If you are upgrading to a Lineage OS 7.1x ROM, then this is the file
https://www.androidfilehost.com/?fid=817550096634766008
Click to expand...
Click to collapse
You need a lazyflasher zip file for first time
@jatin.t.16 you need lazyflasher if you rooted the phone and still stick with miui. This is to avoid bootloop.
If you want to flash custom rom, you need drivers (link provided by @DarthJabba9) ESPECIALLY when you migrated from Marshmallow base MIUI to any Nougat base custom rom.
I somehow uninstalled my OS tonight when I was trying to flash AOSP's Oreo ROM. The flashing was unsuccessful (Error: 7) but I've noticed that no ROMs will flash at all.
I'm getting the same error for all ROMs despite them being suitable for my device:
Updater Process ended with ERROR: 7 Error Installing Zip File "ROM xx.x.x..."
Click to expand...
Click to collapse
Things I've done:
I've tried wiping the cache before I flash ROMS
I am on the most updated version of TWRP available for my device (3.0.2)
I've tried changing the updater-script as someone pointed out in another thread but it did not help
At this point, I just want a stable OS that will run on the phone.... Can someone help me? I just want to understand the error and what's causing it and install a ROM that would work...
Look for Mega Unbrick Guide to install a OS.
Sent from my Pixel 2 XL using Tapatalk
That's odd, because Error 7 is usually related to Updater-Script. Have you modified your model name in Updater-Script or just removed the line from it?
jklh said:
[*]I am on the most updated version of TWRP available for my device (3.0.2)
.
Click to expand...
Click to collapse
TWRP version is 3.1.1-1 now so you're not on the last.
Beside that, the question is what was on your device before :
- Did you already installed OOS 3.1.4 at one point?
- Didi you use the BLUpdater method to update the bootloader (logic ) ?
If no to the 2 questions above, that is the problem. So , you'll have to use the mega unbrick guide !
Kéno40 said:
TWRP version is 3.1.1-1 now so you're not on the last.
Beside that, the question is what was on your device before :
- Did you already installed OOS 3.1.4 at one point?
- Didi you use the BLUpdater method to update the bootloader (logic ) ?
If no to the 2 questions above, that is the problem. So , you'll have to use the mega unbrick guide !
Click to expand...
Click to collapse
I actually haven't done both. I tried flashing the OOS 3.1.4 full ROM but it did not work. I will update my TWRP to 3.1.1-1 and I'll try it again. I do have an update though, I am able to flash an old version of Android M OOS using "OnePlusOxygen_14_OTA_003_all_201510241934". If I am able to install this, maybe this isn't a bricked device? Any advice would be super useful, thanks in advance.
jklh said:
I actually haven't done both. I tried flashing the OOS 3.1.4 full ROM but it did not work. I will update my TWRP to 3.1.1-1 and I'll try it again. I do have an update though, I am able to flash an old version of Android M OOS using "OnePlusOxygen_14_OTA_003_all_201510241934". If I am able to install this, maybe this isn't a bricked device? Any advice would be super useful, thanks in advance.
Click to expand...
Click to collapse
If you haven't done any of the 2 things listed, then you tried to flash a "new Bootloader rom", you have no choice :
=> MEGA UNBRICK GUIDE
Hi everyone, I want install a new custom ROM (I'm on CrDroid 7.6 on Android 11) but I can't boot into recovery. I tried to flash a new recovery but i get this message from fastboot "(remote: '(recovery_b) No such partition')".
I've always installed custom OS using a custom recovery but it seems that that there is no recovery partition on Android 11 ?
Do I have to flash the boot partition with the custom rom .zip directly ?
Myuan34 said:
Hi everyone, I want install a new custom ROM (I'm on CrDroid 7.6 on Android 11) but I can't boot into recovery. I tried to flash a new recovery but i get this message from fastboot "(remote: '(recovery_b) No such partition')".
I've always installed custom OS using a custom recovery but it seems that that there is no recovery partition on Android 11 ?
Do I have to flash the boot partition with the custom rom .zip directly ?
Click to expand...
Click to collapse
You need to:
1. root
2. flash custom recovery
3. flash rom
To flash the recovery you use "fastboot flash boot recovery.img" ?
Do I need to flash both partition ?
Myuan34 said:
Hi everyone, I want install a new custom ROM (I'm on CrDroid 7.6 on Android 11) but I can't boot into recovery. I tried to flash a new recovery but i get this message from fastboot "(remote: '(recovery_b) No such partition')".
I've always installed custom OS using a custom recovery but it seems that that there is no recovery partition on Android 11 ?
Do I have to flash the boot partition with the custom rom .zip directly ?
Click to expand...
Click to collapse
This phone have a/b partion system. The recovery partition is present or phone will not boot. Install a rom via fastboot is possible but it's not safe. In every custom rom thread you can find los recovery and how to install procedure. Read with accuracy. Open the section kernel and custom rom. I suggest you pixel experience
Thank you ! The PixelExperience thread got a nice procedure on how to flash it.
I'll try to flash this ROM tomorrow to test it.
If this is successful I'll try other ROM without Gapp included and with official release, any suggestion ?
Myuan34 said:
Thank you ! The PixelExperience thread got a nice procedure on how to flash it.
I'll try to flash this ROM tomorrow to test it.
If this is successful I'll try other ROM without Gapp included and with official release, any suggestion ?
Click to expand...
Click to collapse
i suggest rom with gapps... the best vanilla rom for me is los... but the system ui is very basical
Yeah but google's feature are useless for my daily usecase and it use more battery.
Great, I'll try it out.
Myuan34 said:
Yeah but google's feature are useless for my daily usecase and it use more battery.
Great, I'll try it out.
Click to expand...
Click to collapse
Ah ok! If you don't use Gapps... I suggest you try latest nezuko. The system UI is cool
wetito said:
Ah ok! If you don't use Gapps... I suggest you try latest nezuko. The system UI is cool
Click to expand...
Click to collapse
Yeah nezuko and corvus seems pretty good, I would rather use a popular ROM like lineage but those ROM looks very promising
Corvus is fantastic... With some optimization made with root... In my opinion is the best at now. For performance, stability and systemUI