Database Info

[Q] Help please, can't use any Kernel on SGS2 except for CF-Root

Hi to everyone, first of all I'm Marco, 29 years old from Italy, nice to meet you
Now my problem:
I can't use any Kernel on Galaxy S2 except for CF-Root (essentially is the stock Kernel rooted).
I did a deep clean but the phone is stuck on the start Galaxy SII image.
I tried Abyss, Siyah and Ninphetamine.
Actually I'm using VillainROM 3.0 but I also tried other roms and had the same problem.
If I enter in recovery it gives me these errors:
E:can't mount / cache/recovery/command
E:can't mount / cache/recovery/log
E:can't open / cache/recovery/log
E:can't mount / cache/recovery/last_log
E:can't open / cache/recovery/last_log
I can't even flash anything in recovery and had to re-flash Cf-Root with Odin.
Maybe someone can help me?
Thanks in advance

i dont now much about the gs2 but i suggest finding a .pit file and flash that via odin witch will remove any partitions and restore memory back to normal then find a stock odin image flash that and start over. as for your kernal issues you need to make sure the rom supports it before flashing it.

Hi, thank you, so are you suggesting to install directly the rom with Odin without using recovery? The Kernels were made for the roms I tried, actually they were inside the roms

Ok. I got it!!
I never heard of PIT files but once I discovered what they are, i flashed it with Odin and now I have Ninphetamine 2.1.3 up and running on VillainROM 3.0.
Thank you so much, you've been really helpfulf!

Xoom MZ601 - ICS need Urgent help, please.

Hi,
My Problem, xoom MZ601 with 3G [Europe] rooted,
The update ICS came last night so I agreed it downloaded
and now I can only get into:
ClockworkMod Recovery v3.2
I also get a an error
E:Can't open /dev/block/mmcb1k1p3
E:Can't mount /chache/recovery/command
E:Can't mount /chache/recovery/log
E:Can't open /chache/recovery/log
E:Can't mount /chache/recovery/last_log
E:Can't open /chache/recovery/last_log
I feel pretty sick, seeing I use my Xoom for work as well.
I could hardly sleep & I have been searching the web for hours,
I hope here is were I'll get hellllppp
In advance Thank you.

You cannot update over OTA if you are rooted. If you are able to go to recovery then flash the custom ROM again and everything will be back to normal
Sent from my MZ601 using xda app-developers app

iamanoopmk said:
You cannot update over OTA if you are rooted. If you are able to go to recovery then flash the custom ROM again and everything will be back to normal
Sent from my MZ601 using xda app-developers app
Click to expand...
Click to collapse
If you mean
-wipe data/factory reset
then I still get this:
ClockworkMod Recovery v3.2
E:Can't mount /chache/recovery/command
E:Can't mount /chache/recovery/log
E:Can't open /chache/recovery/log
E:Can't mount /chache/recovery/last_log
E:Can't open /chache/recovery/last_log
If I could stop the rebooting process
is there anyway to access my xoom from the pc?
ClockworkMod Recovery reminds me of DOS.

Re Flash the rom u where using, hopefully if you can get it on a pc and put into your root drive youll be ok,
Reflash the rom in clockwork, and it will be back to normal
OTA Upates when rooted = Worst idea.

rezkon said:
Re Flash the rom u where using, hopefully if you can get it on a pc and put into your root drive youll be ok,
Reflash the rom in clockwork, and it will be back to normal
OTA Upates when rooted = Worst idea.
Click to expand...
Click to collapse
I can't get access to my xoom via PC
the minute i start my xoom up it shuts down into
Clockwork.
and then the error mount starts.
Is there no guides for a noob like me ?
I am freaking out, i have to work tomorrow,
my job is on the line :crying:

If you have rooted then you must have used fastboot. Try to flash the stock image obtained from motodev using fastboot.. have you tried it before? Just search the forum about the procedure
Sent from my MZ601 using xda app-developers app

Here is what happends when I try diffent starts:
Starting with a SD Card inserted
Shows a
Triangle with a Droid.
Starting without SD
brings me to
ClockworkMod Recovery v3.2.0.0 (solarnz--R4c-100611-1150)
- reboot system now
- apply update from sdcard
- wipe data/factory reset
- wipe cache partition
- install zip from sdcard
- backup and restore
- mount and storage
- advanced
- power off
- +++++Go Back+++++
____________________________________________________________________________
ClockworkMod Recovery v3.2
E:Can't open /dev/block/mmcb1k1p3
(No such file or directory)
E:Can't mount /chache/recovery/command
E:Can't mount /chache/recovery/log
E:Can't open /chache/recovery/log
E:Can't mount /chache/recovery/last_log
E:Can't open /chache/recovery/last_log
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Rebooting Start Vol+ then Vol-
Start Fastboot Protocol support.
Hangs, waited for 20mins nothing.
Start or Power On & Vol+
I get to the start screen then it says
Restarting as if it tring to do the update.

Ok after hours of :cursing: & getting very angry & cursing motorola nonstop,
feeling sick to the stomack
My xoom has been set back to 3.... now at 3.2
and here is the BAD JOKE
System updates:
Your device is up todate.
No update is necessary at this time.
I could "vommit" ! <-- where is the smilely for that ?
My xoom downloaded ICS then got hung up because of Root,
Now there is no root & NO Update
BAnGinG my Head!
Anyone have a clue what is going wrong here ? ? ?
Have a smile about me it is Free & Healthy. :silly:

If I were you, I would do the whole thing from scratch, thru adb, I will install another recovery after I unlock the boot loader, and install a pre rooted ROM.
Use this http://forum.xda-developers.com/showthread.php?p=29733454
However, the rom is for mz604, get the one for mz601.
Sent from my MZ601 using Tapatalk 2

Mizpah said:
Ok after hours of :cursing: & getting very angry & cursing motorola nonstop,
feeling sick to the stomack
My xoom has been set back to 3.... now at 3.2
and here is the BAD JOKE
System updates:
Your device is up todate.
No update is necessary at this time.
I could "vommit" ! <-- where is the smilely for that ?
My xoom downloaded ICS then got hung up because of Root,
Now there is no root & NO Update
BAnGinG my Head!
Anyone have a clue what is going wrong here ? ? ?
Have a smile about me it is Free & Healthy. :silly:
Click to expand...
Click to collapse
exactly the same as me i have tried update while rooted and unlocked but it stucked in recovery with errors..
after that i tried to download official rom and flashed it europe rom to my mz601
i get all updates up to 3.2 but now it says dont need update system is up to date omg are they kidding?
did you solve it by the way?

I have that same problem. I back to stock 3.0 then a update to 3.2 I wait 9 days and nothing.

rtncy said:
exactly the same as me i have tried update while rooted and unlocked but it stucked in recovery with errors..
after that i tried to download official rom and flashed it europe rom to my mz601
i get all updates up to 3.2 but now it says dont need update system is up to date omg are they kidding?
did you solve it by the way?
Click to expand...
Click to collapse
Same here. Was running custom ics and jb but wanted stock ics. Got to 3.2 and nothing. Seen on another thread that you get moved to back of update window ... but I am geting impatient now

gellofish said:
Same here. Was running custom ics and jb but wanted stock ics. Got to 3.2 and nothing. Seen on another thread that you get moved to back of update window ... but I am geting impatient now
Click to expand...
Click to collapse
i solved the problem.. i flashed the fw "spain telefonica" version and after first update it offered me to install ics update and i updated now its ok everything is working fine

[Q] Trying to Install CM10.1 (unofficial), Only Boots into CWM Recovery

I've spent a good 50 hours trying to install scott.hart.bti's unofficial CyanogenMod 10.1 (JellyBean 4.2.1) on my Samsung Infuse 4G (SGH-I997), and have come up against nearly every conceivable problem. Today's problem is the fact that, after going through the scores of steps to finally get to the point to install CM10.1, my phone only boots into ClockworkMod Recovery whenever I turn it on. I've scoured these and other forums for hours trying to solve this, and I've had no luck. Any help would be greeeeatly appreciated.
Here's what I've done so far, if I remember correctly. I started out with stock Froyo on the Infuse.
I successfully rooted my phone with SuperOneClick.
I found out I have to install Gingerbread first. After having no luck with Heimdall (not exactly "one click"), I installed jscott30's UCLB3, option D using ODIN. It comes with Entropy's Daily Driver kernel and red CWM Recovery. I installed the corresponding gapps too.
Before I could install a JellyBean ROM, I had to install an ICS one. Entropy512's unofficial CM9 was recommended, so I installed the latest build of that, following the instructions for installing from Gingerbread with red CWM. I installed the recommended gapps along with it. I also did the recommended wipes before this installation.
I ended up with the scrambled rainbow start screen or whatever people call it. Apparently I have to have Gingerbread bootloaders and those didn't come with the GB ROM, so I installed those via ODIN.
I got CM9 to work.
I transferred over the zip files for the CM10.1 ROM and put them in /sdcard/.
Lots of wipes: wipe data/factory reset, wipe cache partition, format /system, wipe dalvik.
I installed the CM10.1 ROM, and then scott.hart.bti's modified gapps, using CWM.
I tried to reboot the phone. It rebooted into CWM, the same CWM I used to supposedly install CM10.1. Now, whenever I reboot or turn the phone on (by whatever method - removing battery, USB cord, holding power button, selecting "reboot system now" in CWM), it goes directly to CWM.
One, of many, points of confusion is the different CWMs. How do I tell what's a red CWM and a blue CWM? When I Google that, all that comes up is posts from this and other forums of people yelling at the poster to Google it. See the problem here? The CWM Recovery that I used to install CM10.1, is titled "CWM-based Recovery v6.0.2.7". It has a blue menu with a grey background.
Where did I go wrong? Anything remotely applicable that I read seems to be for a different phone, so I'm unsure what to believe. Here are some of the explanations / solutions recommended for similar problems on other phones.
Install a different type of recovery (recommended here, as well as several other places). But everything I find about installing different recovery software involves using ROM Manager (which I can't access and which doesn't work anyway), using Heimdall (which I couldn't get to work), or installing one of the ROMs I already installed. TWRP was recommended, but not for my phone specifically, plus I read here that it doesn't work with MTD JellyBean, which I think is what CM10.1 is. Everything seems to require going back to stock Gingerbread, which is where I started, so I'd still end up having to then install CM9 and run into the same problems. Is it this? Which recovery should I install, and how?
Someone else said here that "The ICS ROMS were built for safestrap now bootstrap (CWM). It does that because it was flashed using CWM." Is this just referring to some other ROM? Everything/everyone else says to do everything with CWM.
A couple posts (here and here) recommend some shell commands involving /dev/block/mmcblk0p3 and /dev/block/mmcblk0p4, respectively. I'm hesitant to try these because they're for different phones, they themselves refer to different blocks, and it seems like the type of thing that could really mess up my phone.
I just flashed with a Heimdall One-Click ICS Recovery found here. My phone is still only booting into recovery, but this time it's "CWM-based Recovery v5.5.0.4" with a blue menu and a black background. At the bottom of the screen, it shows the following errors, which I suspect are just because I cleared the cache before, but I'll include for completeness:
Code:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I'm clearly quite the noob, especially in comparison to all of you, so please save me with your endless expertise! Do I install a new recovery? If so, how? I have a new recovery now (just a different version of CWM). Is there some problem with a boot file or bootloader? Is it a kernel issue? Insert other clueless jargon-filled question here? Endless thanks in advance.

Before you flash 10.1, flash CM 10. Sometimes the phones can be finicky. I solved a similar problem by using this method.
Sent from my SGH-I997 using xda app-developers app

What CM10?
trej3k said:
Before you flash 10.1, flash CM 10. Sometimes the phones can be finicky. I solved a similar problem by using this method.
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
Okay, so I've started again from stock Gingerbread. What CM 10 are you talking about, though? I was only able to find CM 10.1 for Infuse. What CM 10 did you install? Are you referring to scott.hart.bti's BeanStalk build?

Fixed, I think
I think I have it working now. I have no idea what the problem was. I just started over again from the beginning. Jesus Christ was this complicated. I don't know how you guys make this stuff; it's hard enough to just install! Thanks for your help.

Glad you got it working. I try to always flash
In order ( stock, cm9, cm10, cm10.1) cm10 is right under the cm10.1 link in the 10.1 thread. Again, glad you got it up & running! :thumbup:
Sent from my SGH-I997 using xda app-developers app

booting to CM7.2 whit CWM Recovery v6.0.4.6

1 - i apologies in edvense for my multi post, i cant post in the relevant tread until i have 10 posts
2 - and for my poor English and horrendous spelling errors
i have a p500h (OldBB)
using "arnab321-Tasssadar-MultiROMMgr-v5.1" i dual boot
wen the story start i have CWM Recovery v5.0.2.0 CM10.2 on internal and CM7.2 on sd-ext
first i flashed mukulsoni`s flashable CWM Recovery v6.0.4.6
booted to CM10.2, works fine
booted to CM7.2, works too :laugh:
No, this recovery for KitKat only, as you must be aware that KitKat ROM flash on "Set_Metadata_Recursive" and all previous JB and others were using SET_PERM_RECURSIVE.
The update can take backup and restoration of sdext, which was disabled in previous one. Enjoy....
Click to expand...
Click to collapse

stage 2 installing CM11
i installed CM11
installed arnab321-Tasssadar multi rom
i had to restore my sd-ext partition, it was formatted during the CM11 install
and rebooted to CM7.2
still working
next test will be installing CM7.2 on the internal and see if its somting speceal in the rom i use or the arnab321-Tasssadar multi rom

road block
i cant flase the cm7.2 rom i get an error
format() expects 5 args got 3
and wen i try to flash CWM Recovery 5.0.2.0 i get install abortend
from log
I:Cant`t partition non-vfat: /storage/sdcard0 (vfat)
ill try using an app

end
i used an app to get back to 5.0.2.0
flashed my CM7.2 rom
flashed 6.0.4.6
boot
and CM7.2 runs
next try: slimrom v1.3-oldBB (an old rom from rec v4 days)
cant flash inn 6.0.4.6 "format() expects 5 args got 3" error
using an app to got back to recovery 5.0.2.0
flasing the slimrom
flasing 6.0.4.6
boot
slimrom runs whit no problem
my congloson: ther is no problem booting to old android like 2.3.7 (didnt test ICS and JB but i think thy will boot to)
the only problem is in the install scrips
the old probably wont get an updated scrips but ther is still work on 2.3.7 roms that mite get install scripts that can work in 6.0.4.6
that 4 postes 6 more to go
p.s.
i use a 2.3.7 rom called nexusme-kitkat
i understand it has some paid apps in it
can any on tell me wat thy are id like to pay for them
and id like to know what camera is in ther
thank for any help

[Q] i cant flash any rom

I have a samsung galaxy ace. I have CyanogenMod 10.1 flashed on my phone. But im having a lot of trouble with it. So i decided to fladh another rom. But i cant flash it. I even tried to go to stock rom. Whenever i try to install a rom this error shows
E:can't open/ sd card/ new folder/ stock rom.zip
(Bad)
Installation aborted.
Plz help.. What should i do and whats th problem