New too this whole phone, but I've rooted & ROM'd the Kindle Fire (Gen 1.) Samsung Galaxy S3, LG Vortex, and a few other devices so I'm not stupid when it comes too this stuff.
I've never been a fan of CWM, but anyways I used the AIO Vibrant Toolbox too root it, then I added a recovery with the Custom ROM Button, selected the zip and it *Eventually* got me int CWMR v2.5.0.4, I downloaded c-Rom, and http://forum.xda-developers.com/showthread.php?t=2535547, I tried both but they each fail with
"Installing Update...
E: Error in /sdcard/ROM.zip
(Status 0)
Installation Aborted"
I wiped Dalvik, Factory Reset, Wiped Cache, eevrything. But nothing seems too have worked.
Same problem
Hi I'm currently having the same problem and I also have experience rooting other devices with no problem. I even re rooted the device from the beginning and still a no go. If anyone has any solution to our problems please reply thanks.
Bumping, any help available?
depends on what version of android your'e running, i'm assuming 2.2 since you just rooted it. so grab a cm7, cm 10.2, cm11 or any 4.4.2 rom and a 4.4.2 kernel as well. first flash cm7 and let it fully boot into the os, afterwards boot back into recovery and flash cm 10.2 same as before let it boot, now flash that 4.4.2 kernel and while in same recovery session choose "reboot recovery" option now go ahead and flash what ever kitkat rom you like...
Actually I rooted mine to stock eclair from 2.2. I wasn't sure if I needed to stay because all the guides showed to go to 2.1. It is currently rooted with stock rom and I haven't been able to get further than that.
v4vamp said:
Actually I rooted mine to stock eclair from 2.2. I wasn't sure if I needed to stay because all the guides showed to go to 2.1. It is currently rooted with stock rom and I haven't been able to get further than that.
Click to expand...
Click to collapse
try what i mentioned in my previous comment, it should get your device up to date.
Related
I have a rooted Galaxy Tab 10.1 wifi GT-P7510 with CWM
I flashed ROM Starburst ROM and the 1.4Ghz Overclocking kernel for Touchwiz UX.
Shortly after this I started have erratic battery behavior. I was not able to resolve this after trying many of the fixes I founds here. I decided to go back to the stock ROM and kernel.
I download hc-3.1_ota-full_sam_tab_10.1.zip and hc-3.1_touchwiz_ux-full_sam_tab_10.1.zip.
I first tried to install hc-3.1_touchwiz_ux-full_sam_tab_10.1.zip.
and received the following error:
ASSERT FAILED
getprop("ro.bootloader")=="P7100BUKB7"||getprop("ro.bootloader")=="P7100BUKC8"
I then tried hc-3.1_ota-full_sam_tab_10.1.zip and received a similar error:
getprop("ro.bootloader")=="P7100BUKB7" E:error in /sdcard/hc-3.1_ota-full_sam_tab_10.1.zip
I did Factory Reset/Wipe, wipe cache and then wipe dalvick cache.
Navigated to install zip from sdcard > choose zip from sdcard
How can I get back to the stock ROM?
Right now I have it working on the starburst ROM without the overclocking kernel. I still have excessive drain ion the battery.
I want to get back to stock in case I have to send this off to samsung for repair.
Thank you for any assistance you can offer.
I have the same error on a Galaxy Tab 10.1 WiFi I just purchased. Is a wipe absolutely needed? The error seems to be with the ZIP file.
im getting that error and another error. i can reflash the overcome rom. but i jst want to get back to stock. i hear re-rooting works. going to try thattonight. if i come across a fixill post.
Have you reverted the kernel ?
If not, I would start there first.
revert the kernel? how do you do that?
I have had the same errors come up. I reflashed clockwork recovery with odin and after that, problems went away. This has only happened to me if i use rom manager to go into recovery, happens a couple of times.
happyhourtx said:
revert the kernel? how do you do that?
Click to expand...
Click to collapse
Personally I haven't messed with flashing kernels. I would recommend that you head back to the thread where you got the kernel from and start from there. I would imagine that there are instructions, or someone could help you.
OK, I reccomend never using ROM manager it's wonky on our tabs, just boot into recovery with the button combo or the power menu if your ROM has it.
The steps you should take to get back to stock.
I you made a nandroid backup of your stock ROM flash that.
Try re-downloading the stock ROM zips (you may have gotten a bad download)
If those fail.
Flash the new version of Clockwork Mod found in this thread: http://forum.xda-developers.com/showthread.php?t=1090289
(sorry the link button was giving me grief.)
It's an ODIN flash should be pretty simple. Then try again to flash the stock .zip
Unfortunately this may not resolve your battery issue. For help with that go here: http://forum.xda-developers.com/showthread.php?t=1215182
Good Luck!
I know it's been adressed many times in different ways, but the info I found yet is not clear so I need a little help! I am trying to install the latest stable Cyanogen mod, using Gingerbread 2.3.7.
I have a Galaxy SII from Bell that I rooted and unlocked when I got it last november. It came on 2.3.3 and I flashed an official 2.3.4 on it, mainly to improve the battery life (and it worked). I did that using Odin and it went well.
Now I try to install Cyanogen mod through ClockworkMod ROM manager, I download and launch the install from ROM manager but on restart the install fails because of the classic 3E recovery message that says the whole signature cannot be verified.
I was having doubts if my phone was even rooted, but since it is still unlocked and software like Titanium backup runs fine, I guess that confirms it!! I am not sure what route to take from here...
Right now here are the phone details...
GT-i9100 on 2.3.4, FW I9100XXKG2, Kernet 2.6.35.7-I9100XXKG2-CL375027 [email protected] #2
I'll appreciate any help!!!!!!
JFChamp said:
Now I try to install Cyanogen mod through ClockworkMod ROM manager, I download and launch the install from ROM manager but on restart the install fails because of the classic 3E recovery message that says the whole signature cannot be verified.
|Question = Q&A
Looks like you are yet another that has not followed the instructions and flashed a cwm and root kernel .
Root + CWM .
http://forum.xda-developers.com/showthread.php?t=1103399
OR are not following the instructions posted .
First time flashing CyanogenMod 7 to the Samsung Galaxy S II, or coming from another ROM?
Root the device and install ClockworkMod Recovery. Instructions are available here.
Perform a NANDroid backup of your current ROM.
Format the system, data & cache partitions of your device.
Perform a factory reset.
Flash CyanogenMod.
Clockwork mod recovery see
NEW HERE
http://forum.xda-developers.com/showthread.php?t=1134290
The instructions work as i have just installed by following the instructions in reply to an exact same post .
jje
Click to expand...
Click to collapse
Thanks jje... The instructions did work! Tough I tought I had bricked my phone at one point, on the final restart it would get stuck at the Samsung logon screen, but I forced it back in recovery, re-flashed from the zip and then it booted in CyanogenMod!!!
I really appreciate your reply
Hi All, I rooted my Verizon GS4 with this method "[GUIDE] Root for Verizon Galaxy S4 ***VRUAMDK Build Only!***" back before the first update so I have Root with Baseband I545VRUAMDK, Build JDQ39.I545VRUAMDKand Kernal 3.4.0-562219. I haven't tried to install any ROMs since then but started to get the itch so I started refreshing myself on the process and found that when I try to reboot into CWM Recovery it boots to Android System Recovery 3e. I'm looking for guidance on how to get CWM working properly. ROM Manager says I am using CWM 6.0.4.7. Any help will be appreciated.
Thanks
jpp2109 said:
Hi All, I rooted my Verizon GS4 with this method "[GUIDE] Root for Verizon Galaxy S4 ***VRUAMDK Build Only!***" back before the first update so I have Root with Baseband I545VRUAMDK, Build JDQ39.I545VRUAMDKand Kernal 3.4.0-562219. I haven't tried to install any ROMs since then but started to get the itch so I started refreshing myself on the process and found that when I try to reboot into CWM Recovery it boots to Android System Recovery 3e. I'm looking for guidance on how to get CWM working properly. ROM Manager says I am using CWM 6.0.4.7. Any help will be appreciated.
Thanks
Click to expand...
Click to collapse
From what I've read about that issue is people have had to Odin back to stock then start over. Now maybe you could try installing another recovery like Philz maybe using Odin or try Goo for TWRP before you Odin back to mdk and go through all that.
Sent from my SCH-I545 using Tapatalk
I had a similar thing a few years ago, with what I know now I think the recovery is temporarily flashed with CWM to gain root and stock recovery is replaced after, I'd look for an actual CWM recovery to flash in.
Same applied to me using a ROM Manager, said it was v.xxx made a backup, flashed a ROM, turns out was left without a backup..... noob-old days
Bashing away at my HTC Desire C
Thank you for the solid replies, I'm interested in getting experience with the other recovery methods anyway so I'll try those and worse case I start from scratch.
I have pretty much this same issue. I was happily running 6.0.44 CWM, installed via CWM.
Then I happened to check and see there's an update to 6.0.47. I installed via ROM manager which reported success. Except that it isnt. I basically have 2 recoveries as far as ROM manager is concerned. It thinks I'm on 6.0.47, but 6.0.44 is what boots. I'm betting it's the same issue you have.
I re-flashed Twrp trying to fix it. Now twrp is what recovery always boots; but Rom manager still thinks 6.0.47 is installed. Rom manager shows BOTH recoveries in the "Recovery already installed" menu.
Seems the issue here is the 6.0.47 when flashed via Rom manager. It bugs the crap out of me that it seems like I have 2 recoveries installed somehow. Not sure how that's possible, but everything seems like it's functioning for me.
Compare the sizes of the recoveries, one thing I've come across is when you flash a new .img in because of the NAND chip process for writing/erasing I have had 'remnants' from previous files.
In one respect it is unlikely but I wouldn't rule it out until you check yourself. It could just be left on the list as a marker that it has previously been installed.
Personally I don't use ROM Managers now, it's into TWRP Recovery and backup from there
Bashing away at my HTC Desire C
Look Like I'll Have to Start From Scratch
I'm just getting back to this because work was crazy. No Matter what recovery I try always comes up with Android System Recovery 3e. Stock MDK and re-root it is.
Maybe try using GooManager to install TWRP after you've gone back to stock.
Hey Guys,
I'm having a bit of an issue. Currently I was running STOCK Android 4.3 JB, have been for a while, it started to get a bit slow & I was wanting to fresh install, but also try out a 5.0 lollipop ROM. I've rooted my phone in the past and installed custom ROMs before without a problem (Revolution Remix + Cyanogenmod 11), however, I decided to try Liquidsmooth 5.0 lollipop. i followed this video,
https://www.youtube.com/watch?v=QquFDFEEKlI
http://forum.xda-developers.com/galaxy-s3/development/rom-liquidsmooth-lollipop-4-0-b1-t2980477
I downloaded both files and copied them onto my MicroSD card.
I backed up my data (contacts, images, files etc..)
Booted into "Recovery Mode", wiping Cache & factory Reset
When to install from SD, located file and it started reading/installing (sorry can't remember exactly what it did), but during process it failed. I went back into Android (had to setup again), Went and made sure Developer Mode and USB Debugging was on, still didn't work.
Went to make sure CWM was installed/update, which it said it was (possibly from previous custom installs?), tried updating, failed. It said
Went and installed 'SuperSU' from Play store, but got this error.
Decided to try re-install STOCk 4.3 JB, I
made sure USB Debugging was on
loaded Odin 3.07 (or was it 3.09) and loaded 4.3 Firmware under PDA (left everything else as is)
Started and let it do its thing. It finished/PASSED and phone restarted.
i went back into the phone, installed ROM manager & SuperSU again to give it another shot... but same problem again, getting the error above.
I'm not sure what's happened and I'm not sure what "solutions" to search for... anyone have any suggestions?
At this stage I'm thinking of just going back to STOCK 4.3, then maybe try again (either with Liquidsmooth lollipop, or, Slimkat 4.4)
Thanks guys, any help would be super appreciated,
Regards,
~ Dave
Le Widget said:
Hey Guys,
I'm having a bit of an issue. Currently I was running STOCK Android 4.3 JB, have been for a while, it started to get a bit slow & I was wanting to fresh install, but also try out a 5.0 lollipop ROM. I've rooted my phone in the past and installed custom ROMs before without a problem (Revolution Remix + Cyanogenmod 11), however, I decided to try Liquidsmooth 5.0 lollipop. i followed this video,
https://www.youtube.com/watch?v=QquFDFEEKlI
http://forum.xda-developers.com/galaxy-s3/development/rom-liquidsmooth-lollipop-4-0-b1-t2980477
I downloaded both files and copied them onto my MicroSD card.
I backed up my data (contacts, images, files etc..)
Booted into "Recovery Mode", wiping Cache & factory Reset
When to install from SD, located file and it started reading/installing (sorry can't remember exactly what it did), but during process it failed. I went back into Android (had to setup again), Went and made sure Developer Mode and USB Debugging was on, still didn't work.
Went to make sure CWM was installed/update, which it said it was (possibly from previous custom installs?), tried updating, failed. It said
Went and installed 'SuperSU' from Play store, but got this error.
Decided to try re-install STOCk 4.3 JB, I
made sure USB Debugging was on
loaded Odin 3.07 (or was it 3.09) and loaded 4.3 Firmware under PDA (left everything else as is)
Started and let it do its thing. It finished/PASSED and phone restarted.
i went back into the phone, installed ROM manager & SuperSU again to give it another shot... but same problem again, getting the error above.
I'm not sure what's happened and I'm not sure what "solutions" to search for... anyone have any suggestions?
At this stage I'm thinking of just going back to STOCK 4.3, then maybe try again (either with Liquidsmooth lollipop, or, Slimkat 4.4)
Thanks guys, any help would be super appreciated,
Regards,
~ Dave
Click to expand...
Click to collapse
First of all and most important don't use rom manager! it causes more problems than anything else.The best way to install custom roms is to use Cwm,PhilZ or Twrp to install anything!
Flash superSU zip in recovery from here >> http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1 << SuperSU forum here >> http://forum.xda-developers.com/showthread.php?t=1538053 << Technically you should not need to flash SuperSU because nearly all custom roms come with root built in so you could flash a custom recovery then wipe and flash your rom (but I can see you have been having problems doing that)
What you should do is
(1) Flash a custom recovery with Odin (Recommend PhilZ)
(2) Reboot to custom recovery
(3) Wipe phone
(4) Install custom rom (which is already rooted) from Ext SD card
(5) Reboot (If you get bootloop factory reset/ wipe cache
Also to note PhilZ recovery (which I think is better as more options and is based on Cwm) as a option to fix root in settings.
tallman43 said:
First of all and most important don't use rom manager! it causes more problems than anything else.The best way to install custom roms is to use Cwm,PhilZ or Twrp to install anything!
Flash superSU zip in recovery from here >> http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1 << SuperSU forum here >> http://forum.xda-developers.com/showthread.php?t=1538053 << Technically you should not need to flash SuperSU because nearly all custom roms come with root built in so you could flash a custom recovery then wipe and flash your rom (but I can see you have been having problems doing that)
What you should do is
(1) Flash a custom recovery with Odin (Recommend PhilZ)
(2) Reboot to custom recovery
(3) Wipe phone
(4) Install custom rom (which is already rooted) from Ext SD card
(5) Reboot (If you get bootloop factory reset/ wipe cache
Also to note PhilZ recovery (which I think is better as more options and is based on Cwm) as a option to fix root in settings.
Click to expand...
Click to collapse
hi tallman, much appreciated for the reply
For some reason I couldnt get Philz Custom Recovery to work with odin, kept getting an error :/ . So I ended up trying TWRP, which worked, I booted into it then installed Liquidsmooth + gapps, all installed ok, but all up it was the same process you mentioned, which I greatly appreciate.
So running Liquidsmooth 5 now with TWRP recovery, though will likely give Philz recovery a shot down the track
Le Widget said:
hi tallman, much appreciated for the reply
For some reason I couldnt get Philz Custom Recovery to work with odin, kept getting an error :/ . So I ended up trying TWRP, which worked, I booted into it then installed Liquidsmooth + gapps, all installed ok, but all up it was the same process you mentioned, which I greatly appreciate.
So running Liquidsmooth 5 now with TWRP recovery, though will likely give Philz recovery a shot down the track
Click to expand...
Click to collapse
Good to hear it's working Yes it's worth persevering with PhilZ it's a good recovery although Twrp is not bad either:good:
Hi, recently I just rooted my phone, everything going fine back there. Then I try to download cwm touch recovery and everything fine.Then I download "http://forum.xda-developers.com/galaxy-s3/development/i9300-to-n00t-bring-lte-fun-to-3g-t2886574/page333" this rom and wipe data/factory reset >>> flash it with cwm, it said Installation Abort Stage 7 something like that, I found something that said my cwm version is not compatible with the rom. So I now stuck at cwm, I tried to flash to stock rom and the big PROBLEM is, I dont know my software version. here http://samsung-updates.com/device/?id=GT-I9300
Then can anyone help me get out of this cwm, flash to stock rom, and get my s3 back?
It's 3am and I still didn't sleep.