So here's what happened : I flashed the SlimKat 4.4.2 on this phone (SGS4G) using CWM, everything worked, and CWM changed to TWRP. But I didn't like the performance so I decided to go back to CM 10.1 which I have backed up. To restore it I had to re-install CWM, so what I did is installing AntonX Basic with a twist BML/Stock Rom, using the Heimdall one-click package, and I was presented with a red CWM -Vodoo lag fix- 5.0-. and some commands that says cannot read -I can't remember exactly but it has to do with the SD card-. So I went to restore, restored the CM 10.1, and then every time I boot, I get the Galaxy S 4G screen, then Google, then it loops back again from the Galaxy screen. I tried booting up to recovery, but all that happens is I get the orange (6.0.-) CWM with it's logo in the center, and before it loads it starts looping again.
Please help guys !
EDIT :
The things that appear on CWM are :
E:Can't mount /cache/recovery/log
E:Can't mount /cache/recovery/last_log
hope this helps !
red cwm? you need Blue CWM to restore.
Oh right. I've just fixed it, flashed the stock KJ6 Rom via Odin, then flashed AntonX kernel with the heimdall one-click to get CWM, flashed the Beanstalk ROM, and things are going great so far !
But the FFC is screwed up (see the attachment)
Tried flashing a different kernel but no luck. Any ideas on how to fix that ?
Related
I recently noticed a problem in the red cwm I am running. I flashed the gtg community kernel over stock to get access to cwm and be able to flash a custom rom like I normally do. I have flashed a few custom roms recently and noticed that when i boot into cwm recovery I cant mount / unmount the system. I always get Error mounting system. What can be the problem. I have tried different roms and kernels and keep getting this error. Thanks for the help.
Does any one have any suggestions as it does this with everyrom I try. I cant unmount/mount the system in cwm . I like to try things from uot kitchen but with out doing this some things go unthemed.
Hi, i'm a relative noob to rooting and rom flashing but i know the basics and have successfully installed cyanogen on other phones and devices in the past. So essentially I am trying to install jellybean on my infuse 4g (on rogers). I begun with this guide (http://forum.xda-developers.com/showthread.php?t=1776129) but and gotten stuck trying to install entropy's cm9 (http://forum.xda-developers.com/showthread.php?t=1601844). i flashed the rom and then formatted the data, system and cache, but then realized forgot to put the ICS gapps bundle on the sd card before i started. So i flashed once, did the formatting of data, system, cache, then attempted to boot and now im stuck at the samsung screen. It just hangs at that screen every time i try to boot. I have the red CWM screen and can get to CWM, but whenever i try to mount the SD it does not show up on my PC (Mac too) so i can't put any thing on it to flash and fix it.. when i attempt to flash the cm9 rom again it says [bad] and aborts. If anyone could help me out in where to go from here. I have done some reading about setting up ADB to push a rom to it, but will that work if i cant even mount the sd in the first place. CWM allows me to mount and say it should be active but i get nothing on the pc. Also which rom should i use to fix it.. also i follwoed the instructions and have Qksters IMEI backup script run (I'm not exactly sure what this does).
Thanks
phillyjevs said:
Hi, i'm a relative noob to rooting and rom flashing but i know the basics and have successfully installed cyanogen on other phones and devices in the past. So essentially I am trying to install jellybean on my infuse 4g (on rogers). I begun with this guide (http://forum.xda-developers.com/showthread.php?t=1776129) but and gotten stuck trying to install entropy's cm9 (http://forum.xda-developers.com/showthread.php?t=1601844). i flashed the rom and then formatted the data, system and cache, but then realized forgot to put the ICS gapps bundle on the sd card before i started. So i flashed once, did the formatting of data, system, cache, then attempted to boot and now im stuck at the samsung screen. It just hangs at that screen every time i try to boot. I have the red CWM screen and can get to CWM, but whenever i try to mount the SD it does not show up on my PC (Mac too) so i can't put any thing on it to flash and fix it.. when i attempt to flash the cm9 rom again it says [bad] and aborts. If anyone could help me out in where to go from here. I have done some reading about setting up ADB to push a rom to it, but will that work if i cant even mount the sd in the first place. CWM allows me to mount and say it should be active but i get nothing on the pc. Also which rom should i use to fix it.. also i follwoed the instructions and have Qksters IMEI backup script run (I'm not exactly sure what this does).
Thanks
Click to expand...
Click to collapse
the samsung boot loop is to be expected when flashing cm9. If CM9 is not your target Rom, then having GApps on your SD card or not doesnt matter. Carefully refollow the step in CM9 then continue onto cm10. After you do the three finger salute, your cwm will be blue. if all else fails, odin back to stock and start over..just make sure you have GApps when you reach the time to flash cm10.
You need to go to mount then unmount the first set. Then re flashee infinitum.
Sent from my SGH-I997 using xda premium
Hello, I know I am an idiot for this.
But I tried to create my own rom, following a guide carefully.
It was a miui rom and I skipped only one thing, because I couldn't find it. I don't think it was anything important that could have caused my dilemma.
To get to the point.
I have the Nexus S 4G
Using TWRP Recovery
I made a backup of my stock rom
I flashed the Rom(I created) and it failed to flash.
So I tried to restore my Stock rom. Once it said it completed.
I tried to reboot and it just brought me back to bootloader screen.
I'm panicking now.
So I use my root toolkit to flash CWM recovery and tried to install a
new rom on my phone, but it's not working
when I try to boot up into a new rom, all I get is a black screen.
HELP PLEASE. ((
edit: when I went back into TWRP to check the log, it said "can't mount SD"
and I went to MOUNT and Sdcard was mounted..
Hello all,
Last night I was trying to install the latest Gummy release on my Verizon Galaxy S3. This was the first time I have tried to flash a rom on this phone. It failed, and I rebooted my phone, and now it will only boot into the clockwork recovery.
I thought it may have been damaged as i was transferring the file to the device. I had an SD card in my droid X, So I put it in my Galaxy and formatted it with clockwork. Then I transferred the gummy release (that I also re-downloaded) from my computer to the SD card via a memory card reader. I put it in my Galaxy and tried to install the release, and it gave me a different error
Code:
E: Can't Open /external_sd/Gummy-2.1-01-09-14-NIGHTLY-d2vzw.zip
(bad)
Installation aborted.
Edit: Tried a few other roms and they had the same issue, but Cyanogen Mod 10.2 worked. Anybody have any guesses why?
Edit2: Further developments, Trying to do the latest nightly fir the CM yields the same issue that Gummy's release gave me initially. It reports as follows:
Code:
E: Error in /external_sd/cm-11-20140110NIGHTLY-d2vzw.zip
(Status 7)
Installation aborted
Is there possibly a firmware issue at play?
Did u unlocked ur recovery. And if ur trying to flash a KITKAT rom u need the latest clockwork recovery
I'm having this exact issue except I currently have TWRP 2.6.3. I wiped data, cache and internal and it actually booted the below ROM (the first boot) but once I got everything setup and rebooted the device it will not boot beyond recovery. It hangs on the Samsung boot logo. I've tried to restore to a 4.1.2 ROM as well as install 4.3 and 4.1.2 again multiple times but they will not boot. Any direction would be appreciated.
http://forum.xda-developers.com/showthread.php?t=2601536
twistedillutions said:
Did u unlocked ur recovery. And if ur trying to flash a KITKAT rom u need the latest clockwork recovery
Click to expand...
Click to collapse
Sorry, forgot to mention, I did unlock with EZunlock. Would the clockwork on the play store be the latest one, or is there another place with more up to date versions?
Cappurnikus said:
I'm having this exact issue except I currently have TWRP 2.6.3. I wiped data, cache and internal and it actually booted the below ROM (the first boot) but once I got everything setup and rebooted the device it will not boot beyond recovery. It hangs on the Samsung boot logo. I've tried to restore to a 4.1.2 ROM as well as install 4.3 and 4.1.2 again multiple times but they will not boot. Any direction would be appreciated.
http://forum.xda-developers.com/showthread.php?t=2601536
Click to expand...
Click to collapse
Do you get the same error on install that I'm getting, ro are the installs finishing, but not booting?
Try goo manager or ez-recovery to install the latest recovery
right now i can think of
factory reset format data. Make sure u backup ur internal
Wen changing from rom to rom is a good thing to do a clean install
get the right gapps.
The 1st boot always takes time at least on me.
Sorry i cant think of more helpful things.. Been drinking
Looks like my recovery just needed an update. Thanks everyone.
Sent from my Nexus 7 using Tapatalk
Confirmed also an old recovery for me as well. Thank you very much!
My P5100 is acting strange. Short after booting it gives errors about gapps and other apps being stopped. Those messages keep popping up, so nothing else except rebooting/shutting down is possible.
Everything I try to change (in the short time before the errors pop up) is gone after a reboot.
I tried flashing several new roms with the recovery. They all where flashed succesfully according the recovery, but still after reboot the old omni rom is back.
I tried flashing stock roms with odin, they flashed succesfull according ODIN, but still, after a reboot the old omni rom is back
I tried flashing Andi's latest TWRP build with ODIN and my current recovery. ODIN and recovery said it was succesfull but after reboot there is still the old recovery.
So basically it seems this damn thing is insome kind of read-only mode......
Any idea howto fix this ?
This is what is currently installed on the tablet :
TWRP 2.8.7.2
omnirom 5.1.1-20151116-2332-p5100-HOMEMADE
kernel 3.0.101-Omni [email protected] #1
zorka said:
My P5100 is acting strange. Short after booting it gives errors about gapps and other apps being stopped. Those messages keep popping up, so nothing else except rebooting/shutting down is possible.
Everything I try to change (in the short time before the errors pop up) is gone after a reboot.
I tried flashing several new roms with the recovery. They all where flashed succesfully according the recovery, but still after reboot the old omni rom is back.
I tried flashing stock roms with odin, they flashed succesfull according ODIN, but still, after a reboot the old omni rom is back
I tried flashing Andi's latest TWRP build with ODIN and my current recovery. ODIN and recovery said it was succesfull but after reboot there is still the old recovery.
So basically it seems this damn thing is insome kind of read-only mode......
Any idea howto fix this ?
This is what is currently installed on the tablet :
TWRP 2.8.7.2
omnirom 5.1.1-20151116-2332-p5100-HOMEMADE
kernel 3.0.101-Omni [email protected] #1
Click to expand...
Click to collapse
Something strange I just noticed.... In download mode it says "downlaod" instead of "download". Is this normal ? see screenshot
probably the same as this.......
http://forum.xda-developers.com/galaxy-tab-2/help/gt-p3100-boot-loop-recovery-information-t3307456
zorka said:
probably the same as this.......
http://forum.xda-developers.com/galaxy-tab-2/help/gt-p3100-boot-loop-recovery-information-t3307456
Click to expand...
Click to collapse
Find the 4 firmware files for tab 2 series, I tried but can't find working links anywhere. That may recover some cases of bricks and errors. I requested on other forums but, still found none available.
The emmc bug, has only one solution until now, replacement.