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!
so, I've had my SG2 for like a month now, rooted and all, but the problem is , i can't flash any other ROMs(but stock ROMs) or kernels (except for CF root,stock and siyah kernels ) on it via CMW... each time i tried to flash anything, i end up stuck at "galaxy s2 GT-I9100" boot-up logo.... I've tried flashing CM7 then i got the boot-loop ( even with double flash, or triple didn't work for me) and i can't get into CWM when i got the boot-loop....
someone please help me.. i read alotta threads and none of them got similar issue like mine...
i guess its true what they say : every galaxy s2 is different from the rest.
Hmm....must be something you're doing wrong. Nothing to do with Galaxy S2 being different.
Have you always followed the dev's instructions while flashing roms?
Wiping data, cache? Matching up the kernels and roms?
As far as I know, there hasn't been a single person who completely failed to install VillainROM on their SGS2.
I would advise you to give it a go.
Transmitted from a Galaxy far far away via XDA lightspeed telepathy.
What ROMs have you tried to flash?
If you're tring to flash AOSP ROms like CM7 or MIUI it's normal if you're not doing it with a comatible version of CWM. For example, cf root kernel installs a modified version of CWM on your device, which is not compatible with CM7. IF you want to flash CM7 first you have to flash codeworkx kernel http://forum.xda-developers.com/showthread.php?t=1118693, and then enter recovery (the new CWM installed with this kernel) to flash CM7.
Now if you can't flash samsung firmware based ROMs (villainROM, Leomar Revolution, Batista...), I don't know what it could be. I never had a problem flashing samsung firmware custom ROMs with the cf root CWM recovery.
tomascunill said:
What ROMs have you tried to flash?
If you're tring to flash AOSP ROms like CM7 or MIUI it's normal if you're not doing it with a comatible version of CWM. For example, cf root kernel installs a modified version of CWM on your device, which is not compatible with CM7. IF you want to flash CM7 first you have to flash codeworkx kernel http://forum.xda-developers.com/showthread.php?t=1118693, and then enter recovery (the new CWM installed with this kernel) to flash CM7.
Now if you can't flash samsung firmware based ROMs (villainROM, Leomar Revolution, Batista...), I don't know what it could be. I never had a problem flashing samsung firmware custom ROMs with the cf root CWM recovery.
Click to expand...
Click to collapse
If your phone has cf-root/kernal and cf cwm can you just flash over top codeworkx's kernel and do you have to re-root?
InFa_ReD_1 said:
If your phone has cf-root/kernal and cf cwm can you just flash over top codeworkx's kernel and do you have to re-root?
Click to expand...
Click to collapse
If you already have root then you won't loose it.
geko95gek said:
Hmm....must be something you're doing wrong. Nothing to do with Galaxy S2 being different.
Have you always followed the dev's instructions while flashing roms?
Wiping data, cache? Matching up the kernels and roms?
As far as I know, there hasn't been a single person who completely failed to install VillainROM on their SGS2.
I would advise you to give it a go.
Transmitted from a Galaxy far far away via XDA lightspeed telepathy.
Click to expand...
Click to collapse
I used to use VR 3.0 but could only work with stock kernel or cf root kernel has never booted with the ROM's kernel..
tomascunill said:
What ROMs have you tried to flash?
If you're tring to flash AOSP ROms like CM7 or MIUI it's normal if you're not doing it with a comatible version of CWM. For example, cf root kernel installs a modified version of CWM on your device, which is not compatible with CM7. IF you want to flash CM7 first you have to flash codeworkx kernel http://forum.xda-developers.com/showthread.php?t=1118693, and then enter recovery (the new CWM installed with this kernel) to flash CM7.
Now if you can't flash samsung firmware based ROMs (villainROM, Leomar Revolution, Batista...), I don't know what it could be. I never had a problem flashing samsung firmware custom ROMs with the cf root CWM recovery.
Click to expand...
Click to collapse
My phone came with CM7, but i flashed it with rooted stock coz i wanted to have a feel of it... but now i'm done with it but i can't get any roms to work... so frustrating.
i literally have tried flashing ALL Roms (ligtnung, gingerbread,vr, cm7), during the 1st few days that i got my phone it worked with VR 2.5 and 3.0, even MIUI.. but after i flashed with some Asian stock ROM via odin... nothing would work through cmw anymore...
i seriously don't know what i did wrong...
btw, right now im using basebad ver: I9100XXXKI4, kernel: 2.6.35.7-siyah [email protected]#20, build number GINGERBREAD.ZSKI3.
I really don't know. YOu should try to go the closest possible to stock and try from there. DO a full wipe, wipe data, wipe system, everything and flash a stock ROM from your country and carrier (there is a thread from infratech where you can get carrier specific ROMS). THen connect your phone to kies (maybe yo get an oficial update) and then do everything from scratch, root, install CWM, etc...
That's what I'd do but I really don't now if it's the best option.
i have almost the same problem,but me i can flash any rom,but the problem is with the kernel my phone refuse to boot on any other kernel else than cf-root and the speedmod,it freezes in the kernel loading so i must turn it off and reflash via odin cf-root or speedmod to get it works again.
tomascunill said:
I really don't know. YOu should try to go the closest possible to stock and try from there. DO a full wipe, wipe data, wipe system, everything and flash a stock ROM from your country and carrier (there is a thread from infratech where you can get carrier specific ROMS). THen connect your phone to kies (maybe yo get an oficial update) and then do everything from scratch, root, install CWM, etc...
That's what I'd do but I really don't now if it's the best option.
Click to expand...
Click to collapse
well, i'm gonna try that and see if it works, am also goin' try to see if downgrading to 2.3.4 or something would work too...
but please if you got any more ideas, just keep it coming..
thanks
Phew! NOW I HAVE CM7 RUNNING ON MY PHONE!!
I'm gonna try to explain how i fixed my issue, as clear and explanatory as i can..
lucky i didn't brick my phone during all this, because I tried so many things and none worked.I unsuccessfully tried downgrading to XWkI4, ZCKI4, and alot others via Odin... after flashing all i get is tons of error messages(on 3e recorvery) E: can't open/cache or E:failed blah bla bla to load /efs... i thought OMG! my phone is bricked! then i recalled reading somewhere that flashing the 3 tar (PDA,MODEM,CSC) files usually should work(maybe better than flashing a 1 tar file), so i found a 3 files xxKI3 rom, flashed it and BAM! it booted up this time without any error. so now i went ahead and rooted it since the tar files came unrooted, then went into CWM to flash cm7 ROM, flashed it twice and ofc i got stuck on boot logo.....i didn't panic much, i pulled out the battery, and restarted to CWM where i cleared cache/ dalvik/ and did wipe/factory reset, then i reflashed CM7 again (twice) and it worked!!!! YES, CM7 is fiannly working on my SG2!
thanks for everyone for helping, and i hope this can help others on the same boat as me..
I am using CM9 on my SGS2. I have been flashing the nightlies for months. But I wanted to give CM7.2 a shot so I tried flashing that. But it gave me a boot loop. So I reloaded CM9 using Odin, re-downloaded CM7.2, checked the md5 and tried flashing again... same result. So I tried a couple of other GB ROMs and I got the same result. So I thought maybe the problem is CWM and I tried flashing a stock Samsung GB firmware but I got a boot loop again... but I have successfully flashed an ICS firmware, CM9 and MIUI4 since then. I can only use ICS ROMs.
So the problem must be my phone. Can anybody suggest what the problem might be or suggest a way to fix this? My phone works perfectly otherwise.
are you trying these with full wipe before and after the installation
+1 @ zacq
simple answer format system partition and will not bootloop for sure
deleted
ZACQ8 said:
are you trying these with full wipe before and after the installation
Click to expand...
Click to collapse
Yes. When I wipe afterwards I get kernel panic upload mode.
I'm new to this forum and find the i717 a wee bit more complicated than my old phone. (a Galaxy S 4g.)
I've managed to get CWM touch 5.5.0.4 on the phone and have successfully flashed the deodexed stock jelly bean rom. However when I try to flash any of the "quincy.att" based rom, CWM gives me an error, which I imagine means that I need a more recent CWM. Before I flashed stock jelly bean, I was able to get the 6.0.3.6 quincy.att CWM on the phone using the terminal but when I tried using it, it did not see the external sdcard and I could not get there to flash any rom. I tried using ODIN to flash CWM 5.8.4.3 but ODIN just sat there and nothing got loaded onto the phone at all.
So it is kind of a chicken and egg situation here. What is the minimum version of CWM I need to flash any of the quincy.att roms and how do I get it on there and working? Or am I supposed to use TWRP? I haven't tried that. I remember it from the 4g and it was a pain to use on that phone. I have tried to flash the 10.1 quincy.att plain Cyanogen and the chameleon rom and I just get error messages from CWM,
Just use twrp.....your probably getting error 7 ...install twrp
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
TWRP is piece of cake here. you will never look back
I'm having issues getting cwm 6.0.4.4 to work.... 6.0.4.3 touch or regular work just fine, but the few times I've tried flashing 6.0.4.4 in order to flash the latest Kit Kat I get stuck in a bootloop. The only way to fix it is to remove my battery, flash twrp with Odin, wipe everything, flash cwm (earlier than 6.0.4.4) and reflash a ROM. I've tried: updating through ROM manager, flashing 6.0.4.4 in recovery, converting a zip to a tar (thinking maybe the file was corrupted). I'm beginning to think my phone just doesn't like Kit Kat.... Now I'm back on Padawan because it's like literally the most stable ROM for my phone. Any ideas?
longhairdaddy said:
I'm having issues getting cwm 6.0.4.4 to work.... 6.0.4.3 touch or regular work just fine, but the few times I've tried flashing 6.0.4.4 in order to flash the latest Kit Kat I get stuck in a bootloop. The only way to fix it is to remove my battery, flash twrp with Odin, wipe everything, flash cwm (earlier than 6.0.4.4) and reflash a ROM. I've tried: updating through ROM manager, flashing 6.0.4.4 in recovery, converting a zip to a tar (thinking maybe the file was corrupted). I'm beginning to think my phone just doesn't like Kit Kat.... Now I'm back on Padawan because it's like literally the most stable ROM for my phone. Any ideas?
Click to expand...
Click to collapse
If 6.0.4.3 touch works "fine", why don't you just use that?
veningTrMarchal
tube517 said:
If 6.0.4.3 touch works "fine", why don't you just use that?
Click to expand...
Click to collapse
cwm 6.0.4.4 is recommended for the Unofficial AOKP 4.4.2 flash and I couldn't get it to install with 6.0.4.3. It installs with 6.0.4.4 but ends up in a bootloop.
longhairdaddy said:
cwm 6.0.4.4 is recommended for the Unofficial AOKP 4.4.2 flash and I couldn't get it to install with 6.0.4.3. It installs with 6.0.4.4 but ends up in a bootloop.
Click to expand...
Click to collapse
Try CM11 for KitKat. It's very stable.
tube517 said:
Try CM11 for KitKat. It's very stable.
Click to expand...
Click to collapse
I actually did try CM11 Kit Kat and liked it but about ten minutes after everything boots up it will force close and go into a boot loop. I've tried the various gapps packages, installing without gapps then flashing them, wiping dalvic before and after and in between, I dunno.
4.3 ROMs run like a diesel, it just seems I can't get 4.4s to be stable. I just now flashed the Beanstalk 4.4.2 along with the updated gapps and can't get past the beanstalk animation. Sat there for an hour.
I appreciate the input though.
longhairdaddy said:
I actually did try CM11 Kit Kat and liked it but about ten minutes after everything boots up it will force close and go into a boot loop. I've tried the various gapps packages, installing without gapps then flashing them, wiping dalvic before and after and in between, I dunno.
4.3 ROMs run like a diesel, it just seems I can't get 4.4s to be stable. I just now flashed the Beanstalk 4.4.2 along with the updated gapps and can't get past the beanstalk animation. Sat there for an hour.
I appreciate the input though.
Click to expand...
Click to collapse
I had the same issues with 4.4 kitkat roms. Did you format system in CWM when wiping? This solved my bootloop issues. Also, make sure you have a clean download of the ROM. Flash the ROM twice back to back when flashing a new kitkat rom
Hey folks,
I'm desperately trying to get a CustomRom working on my GP4.
I'm relatively new to the device, but not to CustomRom's, since I was using a Motorola Defy untill last summer, running CM7.2 and CM9, MIUI and a couple of others.
So here's my issue:
I flashed the Terrasilent Kernel in order to get CWM so I could flash the .zip's from there, as some weren't available for odin.
The kernel works fine, but as soon as I try to flash any CustomRom (I tried CM9, CM10.2, Hydrogen and the PACMAN Rom), I'm just getting infinite bootloops.
I also tried flashing with SD card removed, SD card back in....doesn't help. No matter whether it's done with odin or CWM.
Mostly I get stuck at the Samsung screen , the PACMAN insert coin or the Terrasilent phonebooth .
Does anyone have suggestions how I could make it work?
Cheers!
basti_b24 said:
Hey folks,
I'm desperately trying to get a CustomRom working on my GP4.
I'm relatively new to the device, but not to CustomRom's, since I was using a Motorola Defy untill last summer, running CM7.2 and CM9, MIUI and a couple of others.
So here's my issue:
I flashed the Terrasilent Kernel in order to get CWM so I could flash the .zip's from there, as some weren't available for odin.
The kernel works fine, but as soon as I try to flash any CustomRom (I tried CM9, CM10.2, Hydrogen and the PACMAN Rom), I'm just getting infinite bootloops.
I also tried flashing with SD card removed, SD card back in....doesn't help. No matter whether it's done with odin or CWM.
Mostly I get stuck at the Samsung screen , the PACMAN insert coin or the Terrasilent phonebooth .
Does anyone have suggestions how I could make it work?
Cheers!
Click to expand...
Click to collapse
Did you wipe the data/cache? Also, I believe you're supposed to flash then ROM first, THEN you flash the kernel.
TheKryptonite said:
Did you wipe the data/cache? Also, I believe you're supposed to flash then ROM first, THEN you flash the kernel.
Click to expand...
Click to collapse
Forgot to mention that: I tried various ways: first wipe data/cache, then flash ROM; first flash ROM, then wipe cache; wipe cache, flash ROM, wipe again...
In order to get CWM recovery and being able to flash a zip I flashed the Kernel first. For CM9 I followed this http://forum.xda-developers.com/showthread.php?t=2213152
As I couldn't flash any of the pre-flash zip from stock, I thought it's necessary to flash a kernel including CWM first. It was done in the same way in some youtube tutorial I watched, where the guy already had the terrasilent kernel on his device.
For odin, I will check if it works with first flashin the ROM and afterwards the kernel.
Cheers for your fast reply!