I download this rom on the internet for my sch-i800 verizon and i want to know how to install it without a computer.
Sent from my SCH-I800 using xda app-developers app
copy ur rom .zip file into sd card of ur fon....then go into recovery and choose .zip install from sd card.....
Use ROM MANAGER
mohit378 said:
copy ur rom .zip file into sd card of ur fon....then go into recovery and choose .zip install from sd card.....
Click to expand...
Click to collapse
use rom manager app install it and select "flash from sd card" select ur recovery file and install it .. easiest way to install recovery. "AM NOT RESPONSIBLE FOR ANY DAMAGE TO UR PHONE"
Rom manager doesnt support my device, it asks me to install clockworkmod bu my device in not supported
Sent from my SCH-I800 using xda app-developers app
Panzer15 said:
I download this rom on the internet for my sch-i800 verizon and i want to know how to install it without a computer.
Sent from my SCH-I800 using xda app-developers app
Click to expand...
Click to collapse
If you want to flash the rom without a pc, just google "how to flash rom without a computer" and look at the first link...the guide might help.
Otherwise, after you have rooted just install a custom recovery (like twrp or cwm) and flash the rom from your sd card. And make sure you wipe cache/data etc before flashing the new rom. (make a backup first)
This is my first time trying to install a ROM. When i try to install after wiping i get this error
- Installing: /sdcard/download/cm-10-20131006-NIGHTLY-p1c.zip Finding update package... I:Update location: /sdcard/download/cm-10-20131006-NIGHTLY-p1c.zip Opening update package... Installing update... script aborted: assert failed: getprop("ro.product.device") == "galaxytab7c" || getprop("ro.build.product") == "galaxytab7c" || getprop("ro.product.device") == "p1c" || getprop("ro.build.product") == "p1c" || getprop("ro.product.device") == "SCH-I800" || getprop("ro.build.product") == "SCH-I800" || getprop("ro.product.device") == "SPH-P100" || getprop("ro.build.product") == "SPH-P100" || getprop("ro.product.device") == "vzwtab" || getprop("ro.build.product") == "vzwtab" assert failed: getprop("ro.product.device") == "galaxytab7c" || getprop("ro.build.product") == "galaxytab7c" || getprop("ro.product.device") == "p1c" || getprop("ro.build.product") == "p1c" || getprop("ro.product.device") == "SCH-I800" || getprop("ro.build.product") == "SCH-I800" || getprop("ro.product.device") == "SPH-P100" || getprop("ro.build.product") == "SPH-P100" || getprop("ro.product.device") == "vzwtab" || getprop("ro.build.product") == "vzwtab" E:Error in /sdcard/download/cm-10-20131006-NIGHTLY-p1c.zip (Status 7) Installation aborted. result was NULL, message is: assert failed: install_zip("/sdcard/download/cm-10-20131006-NIGHTLY-p1c.zip")
I know that its possible installing rom by using heimdall but there is a gapps file. Do i flash gapps file after flashing rom?
Sent from my SCH-I800 using xda app-developers app
I'm not sure why you're getting that error. You're best bet would be to make sure you follow the instructions from whoever posted the rom and ask questions on the roms thread if you still are stuck...sorry I couldn't help directly
Sent from my DROID Pro using xda app-developers app
---------- Post added at 12:22 AM ---------- Previous post was at 12:19 AM ----------
And yes, you flash the rom and then the gapps...this should also be in the OP directions wherever the rom was posted...(I would advise you to flash roms from xda forums because they have clear instructions and support)
Sent from my DROID Pro using xda app-developers app
So if i use heimdall to flash rom, how do i flash the gapps file?
Sent from my SCH-I800 using xda app-developers app
Panzer15 said:
So if i use heimdall to flash rom, how do i flash the gapps file?
Sent from my SCH-I800 using xda app-developers app
Click to expand...
Click to collapse
just update ur recovery......
Related
I rooted the phone and installed the super user file, but I've been having issues installing the latest stable version. I ended up installing the latest nightly version but I think it has been affecting the mic somehow. I was just wondering if anyone could clarify why I may be having issues. I placed both the latest and the second latest zip files on my SD card, but when I run the Clockwork mod, it says for both the installation is aborted.
I'm not sure why your installs would abort but if you're running cm7 and having mic issues go to Settings - Device Settings - Sound Settings and disable hi-fi recording.
Sent from my Nexus S 4G
Thanks, that seemed to have fixed the problem. I'm still not sure why the stable version isn't working but this nightly version I have seems to be working well so maybe I'll just stick with it for now.
You should flash another ROM and check whether the issue still exists steer clear or CM7 based ROMS
What would you suggest? I'm not phone illiterate or anything, but this is my first experience rooting & installing ROMs.
HurtMeSole said:
What would you suggest? I'm not phone illiterate or anything, but this is my first experience rooting & installing ROMs.
Click to expand...
Click to collapse
Heres the link to one of my fav ROMS Oxygen http://download.oxygen.im/roms/update-oxygen-2.3.2-NS-signed.zip
Instructions:
Boot into recovery
do factory reset wipe cache/dalvik/
install the ROM
For whatever reason I'm getting the same error when I tried to install the stable CM7 ROM. I also tried using the ROM Manager as well and didn't have any luck either. Could there be a problem with my ClockWork Mod?
HurtMeSole said:
For whatever reason I'm getting the same error when I tried to install the stable CM7 ROM. I also tried using the ROM Manager as well and didn't have any luck either. Could there be a problem with my ClockWork Mod?
Click to expand...
Click to collapse
Which version are you using. Try to have the latest version.
-- Installing: /sdcard/update-oxygen-2.3.2-NS-signed.zip
mtd: successfully wrote block at 0
I:Set boot command "boot-recovery"
Finding update package...
I:Update location: /sdcard/update-oxygen-2.3.2-NS-signed.zip
Opening update package...
Installing update...
script aborted: assert failed: getprop("ro.product.device") == "crespo" || getprop("ro.build.product") == "crespo" || getprop("ro.product.board") == "crespo"
assert failed: getprop("ro.product.device") == "crespo" || getprop("ro.build.product") == "crespo" || getprop("ro.product.board") == "crespo"
E:Error in /sdcard/update-oxygen-2.3.2-NS-signed.zip
(Status 7)
Installation aborted.
result was NULL, message is: assert failed: install_zip("/sdcard/update-oxygen-2.3.2-NS-signed.zip")
There is the error message.
HurtMeSole said:
For whatever reason I'm getting the same error when I tried to install the stable CM7 ROM. I also tried using the ROM Manager as well and didn't have any luck either. Could there be a problem with my ClockWork Mod?
Click to expand...
Click to collapse
You can reinstall CWM within ROM-manager
Yeah I did. Still no luck.
Are you on nexus s or nexus s 4G? I am not sure if there's different recovery but yours would seem to be for nexus s I believe.
Sent from my Nexus S 4G running CM7/franco.Kernel
I have the 4G. I went to the CyanogenMod site and downloaded the latest version for the 4G but I get that exact same error message I posted earlier.
Now I can't even get it to boot into recovery. It just freezes.
HurtMeSole said:
-- Installing: /sdcard/update-oxygen-2.3.2-NS-signed.zip
mtd: successfully wrote block at 0
I:Set boot command "boot-recovery"
Finding update package...
I:Update location: /sdcard/update-oxygen-2.3.2-NS-signed.zip
Opening update package...
Installing update...
script aborted: assert failed: getprop("ro.product.device") == "crespo" || getprop("ro.build.product") == "crespo" || getprop("ro.product.board") == "crespo"
assert failed: getprop("ro.product.device") == "crespo" || getprop("ro.build.product") == "crespo" || getprop("ro.product.board") == "crespo"
E:Error in /sdcard/update-oxygen-2.3.2-NS-signed.zip
(Status 7)
Installation aborted.
result was NULL, message is: assert failed: install_zip("/sdcard/update-oxygen-2.3.2-NS-signed.zip")
There is the error message.
Click to expand...
Click to collapse
This is for the NEXUS S, You should install the NS4G version. You try to install a NS rom to a 4G, It wont install.
Yeah I see that now. But the CyanogenMod still wouldn't install and I'm sure I was using the 4G version for that. & now I am having an issue even getting into the Clockwork recovery.
Use fastboot to flash recovery again to your phone. Then Redownload the CM7 rom from here
http://forum.cyanogenmod.com/topic/32476-cyanogenmod-7-for-the-nexus-s-4g-v7101-11-oct-2011/
and try flashing. Check whether the MD5 sum of the ROM on the site matches with the file you downloaded.
Can you get into bootloader and then you select recovery but it doesn't load? If so you could try flashing recovery from your computer using fastboot.
Sent from my Nexus S 4G running CM7/franco.Kernel
Yeah what he said! My thoughts exactly.
Sent from my Nexus S 4G running CM7/franco.Kernel
I just kept flashing the Clockwork until it allowed me to get into the recovery mode. I installed the CM7 for the 4G and it worked but there was no Market app so no way to get my backup on to the phone.
I need some help rooting my Samsung Galaxy Ace. It's running Gingerbread 2.3.5 XWKS9
I tried rooting it before, and it worked like a charm, selecting zip, installing and done.
But I had to send it in for warranty, and when I got it back, they did a total wipe.
But when I try rooting it now I get:
Code:
Opening Update Package...
Installing Update...
assert failed: getprop("ro.product.device") == "GT-S5830" || getprop("ro.build.product") == "GT-S5830" || getprop("ro.product.device") == "GT-S5570" || getprop("ro.build.product") == "GT-S5570" || getprop("ro.product.device") == "GT-S5670" || getprop("ro.product.product") == "GT-S5670" || getprop("ro.product.device") == "GT-B7510" || getprop("ro.product.product") == "GT-B7510"
E:Error in /sdcard/upd_1.zip
(status 7)
Installation aborted.
I tried everything I could think of (wiping cache, other CWM etc.) but it wouldn't matter.
I already searched google for hours. Tried everything in this topic (seemed to be an exact case like mine):
forum.xda-developers.com/showthread.php?t=1537505
I hope anyone can help me
Please help me, I can't seem to figure it out by myself. I even tried editing some of the tried zip files.
The one who fixes it, will recieve a great present! A free Smily throug a private message!
Try flashing a stock ROM (2.3.4 f.ex) using ODIN and then try to root it.
HeXmit said:
Try flashing a stock ROM (2.3.4 f.ex) using ODIN and then try to root it.
Click to expand...
Click to collapse
I can't even seem to flash it using ODIN. Downloaded the OPS file, and a stock firmware. Followed a guide, but couldn't get it working.
Anyone got another idea?
EDIT:
It seems fixed. Tried again using ODIN, and it worked this time!
Whenever I find some spare time I use to switch rom. Flashollic Me!
Increment CM digits are always no task at all because developers are taking good care so that flash process is done right.
But when try to decrements cm digits - do not have options. Back to DDLF2 via mighty odin is the only way to start. No flash-able zip files to step back! There should exist some easy way to do the job. This is a way to do this but I believe more easier way exists.
From cm11 rebboot to recovery
Flash cm-Ker-10.2over11-BuildBox.zip from cwm
Reboot to recovery again
Clean user data, etc, etc
Flash any cm10 (I tried cm10.2) rom
If that well known error "status 7" appears go ahead and flash again.
Flash gapps accordingly (gapps for 4.1, 4.2, 4.3)
Reboot.
Yes, not caught by mighty odin. Bye bye odin. See you later in deep needs.
This is not my work. I moved things from here to there. No Dev thing.
The zip structure is taken from the work of David Rodero
The boot.img is from BuildBox
All credit goes to @rodero95 and @buildBox
Finally, good luck to all flashers.
another method:
open cm10(10.1 or 10,2).zip\META-INF\com\google\android
edit the updater-script
delete the device assert script
Code:
assert(getprop("ro.product.device") == "galaxysl" || getprop("ro.build.product") == "galaxysl" ||
getprop("ro.product.device") == "GT-I9003" || getprop("ro.build.product") == "GT-I9003" ||
getprop("ro.product.device") == "GT-I9003L" || getprop("ro.build.product") == "GT-I9003L");
then mount sdcard0 ,sdcard1 in cwm recovery and then chose the zip and flash. work for me
Hello friends,
I followed a tutorial to install CM11 on my tablet Samsung Galaxy tab 2 7.0 (P3110), and as part of the process I flashed the Clockworkmod recovery via Odin. The problem is that I selected the wrong CWM version, I chose the P3100 model instead of P3110. Despite CWM is running, now I cannot install any ROM via CWM. The installation process results on error code 7.
The best part is that I'm not being able to connect the tablet to the PC - it seems that this wrong CWM is preventing the tablet to be recognized by Windows
Do you guys have any suggestions or hints on how to solve this? I was wondering if it is possible to re-flash CWM via SD card or something which could be done without USB connection.
Thanks in advance for your attention!
Download odinflashable CWM, TWRP or PhilZ Touch for p3110 and flash it from Download mode.
Find latest one here: https://www.androidfilehost.com/?w=files&flid=14076
Send from OnePlus One using Tapatalk
No USB connection
Hello Andi!
Thanks for the quick response. My problem is that the tablet is not being detected by the PC, so I cannot flash anything using Download Mode.
Do you see any alternative?
Regards.
Rom booting?
Edit: or access to microSD card?
Send from OnePlus One using Tapatalk
Please flash attached CWM for p3110, reboot your recovery once after that.
I removed the device check from the updater-script:
Code:
assert(getprop("ro.product.device") == "p3110" || getprop("ro.build.product") == "p3110" ||
getprop("ro.product.device") == "GT-P3110" || getprop("ro.build.product") == "GT-P3110" ||
getprop("ro.product.device") == "espressowifi" || getprop("ro.build.product") == "espressowifi" ||
getprop("ro.product.device") == "espressowifixx" || getprop("ro.build.product") == "espressowifixx");
DO NOT FLASH THIS ZIP ON A DIFFERENT DEVICE!
Yes
Android-Andi said:
Rom booting?
Edit: or access to microSD card?
Send from OnePlus One using Tapatalk
Click to expand...
Click to collapse
Yes I do have access to SD card via the current CWM.
Many thanks
Android-Andi said:
Please flash attached CWM for p3110, reboot your recovery once after that.
I removed the device check from the updater-script:
Code:
assert(getprop("ro.product.device") == "p3110" || getprop("ro.build.product") == "p3110" ||
getprop("ro.product.device") == "GT-P3110" || getprop("ro.build.product") == "GT-P3110" ||
getprop("ro.product.device") == "espressowifi" || getprop("ro.build.product") == "espressowifi" ||
getprop("ro.product.device") == "espressowifixx" || getprop("ro.build.product") == "espressowifixx");
DO NOT FLASH THIS ZIP ON A DIFFERENT DEVICE!
Click to expand...
Click to collapse
Thank you my friend I'll try this at night (Brazilian time). Probably will post the answer tomorrow.
CMW successfully instaled
Hello Andi,
Last friday I installed successfully the CWM package you prepared. But just after CWM installation and reboot the battery died. As the tablet is not charging nor connecting to the PC, I could not try the CM11 installation from the new CWM.
I'll try to turn it on with another battery, in order to find out if the USB connection problem is related to the custom CWM or ROM. It seems that I have actually a hardware problem.
Thank you anyway for the support. Will let you know as soon as I have news.
Alexandre.
Hi guys,
Can you help me please?, I having problems to upgrade my xt925 to CM12.1. The error log says that I have a xt926 and the update process abort.
Please see the attached image. Thanks in advance for your support.
xt925 to cm12.1
rodrigo_ruiz_rr said:
Hi guys,
Can you help me please?, I having problems to upgrade my xt925 to CM12.1. The error log says that I have a xt926 and the update process abort.
Please see the attached image. Thanks in advance for your support.
Click to expand...
Click to collapse
I had a similar problem, but in my case the log said that my device was not a xt925 because i had cm11 for msm8960, the solution was to delete this line:
Code:
[I][B]assert(getprop("ro.product.device") == "xt925" || getprop("ro.build.product") == "xt925" || getprop("ro.product.device") == "vanquish_u" || getprop("ro.build.product") == "vanquish_u" || abort("This package is for device: xt925,vanquish_u; this device is " + getprop("ro.product.device") + "."););
ifelse(is_mounted("/system"), unmount("/system"));
assert(getprop("ro.boot.secure_hardware") == "1" || abort("This package is for devices with 4.4 bootloader"););[/B][/I]
in the updater-script file inside the folder cm-12.1-20150810-NIGHTLY-xt925.zip\META-INF\com\google\android of your zip file, so it won't try to verify your device name and instead will install it as it is
REMEMBER USE THIS UNDER YOUR OWN RISK, DON'T BLAME ME FOR A NICE PAPER WEIGHT
I ALREADY HAD A KITKAT BOOTLOADER FROM A STOCK FIRMWARE and i tried this on a old device, so no harm if bricked, also i was sure that i downloaded the correct cm12.1 version for my mobile and, at last but not least, i knew how to unbrick it in case something went wrong