Database Develop

[Q] Can't get into CWM - MIUI RC8vC

Hi!
Im having trouble getting into CWM. I have been running MIUI on my Galaxy S i9000 for over a month now without any problems with CWM. Im running MIUI RC8vC right now and decided to update it to the latest release MGv2, but here comes the problem. I can't get into the Clockwork Mod Recovery mode.
What i have been trying is the standard 3-button-combination, where i end up on the splash screen for the Galaxy S i9000 and than nothing more happens (left it on for 10 minutes just to be sure). So i then tried rebooting into CWM using the ROM Manager from Market, ending up with the same result.
My question is, what is the most simple way of fixing this annoying problem?
Thanks!

how long are you holding the 3 button combo for ? you only need to do it until the GT-I9000 screen comes on, then let go.
anyway if you cant get it working its probably kernel related, did you flash they CM7 initial kernel before you came to MIUI,
do this again in ODIN and start the process again

Yepp that's what im doing, I have been using CWM quite a lot so im 100% sure im doing the combo correct, it seems like the CWM just wont boot up.
Yes i did, and after that i have been upgrading MIUI like 10 times for every new version without any problems at all, up until now with this release.
So the solution is to Flash the initial kernel again, then use the 3 button combo and install the latest release and all will be fine again hopefully?

RobertRoos_ said:
Yepp that's what im doing, I have been using CWM quite a lot so im 100% sure im doing the combo correct, it seems like the CWM just wont boot up.
Yes i did, and after that i have been upgrading MIUI like 10 times for every new version without any problems at all, up until now with this release.
So the solution is to Flash the initial kernel again, then use the 3 button combo and install the latest release and all will be fine again hopefully?
Click to expand...
Click to collapse
yes, that should work
weird problem and i have never heard of it before lol..

Thanks for the quick answer!
I did what you said and it worked fine, im now running the latest release of MIUI for Galaxy S.
But now i can't get into CWM again! This is really strange, and annoying, if i have to go back to the initial kernel all the time for upgrading MIUI, i do wonder what could be causing this problem. If it was the kernel that comes with the later releases av MIUI i suppose others would have similar problems, but i can't find anyone else having these kinds of problems.
Seems like im beeing followed by bad luck today.

so download mode IS working ??? Hmmm.... not a 3 button combo issue then..
How long have you been on MIUI, did you come from a gingerbread ROM ?
can i just ask how are you doing the 3 button combo..... (i feel stupid asking this, but this problem is so strange)

Yes, works like a charm- so as I said im on the MGv2 right now but with the same problem as before lol.
I've been on MIUI for about a month now, perhaps a little longer. No i came from Darkys v9.5, than did the standard update procedure going to a stock froyo rom and so on as described in the main MIUI thread.
Well im doing it the same way both when on the kernel for CM7 where i can get in, and when on the kernel for MGv2. Menu+Volume Up+POWER, Releasing Power directly when the "Galaxy S i9000 Samsung" splash screen turns up. So im 100% im doing the combination right. I can't get into CWM using the ROM Manager either that donät require the 3-button combination, so there must be something else.
Thanks for trying to help me with this!

no need for thanks we havent got it sorted yet lol
make a post in the MIUI thread in development, there is a lot of cleverer people in there and im hoping that they can shed some light on this bizzare situation

I wanted to do that in the first place, however i must reach 10 posts or so before i can post in there. You could not post my question in there for me you think? So i don't hace to just spam this forum with another 5 posts.

thats very respectful of you not wanting to spam the thread, but yes i will post your question now for you,
you can keep your eye on the post and watch the results, i will also post the results here when someone kindly answers it
EDIT: have you done a factory reset ? when in recovery did you format /system /cache / dalvik cache and then install MIUI

hey mate had a reply, dont know if you have been checking but here is what was said
I had a similar problem when first installing CM7, I believe it is a problem with having come from the original JVK. The solution was to flash an older Froyo version (JS3 in my case) and repartitioning with 512-pit, then installing MIUI again from scratch. Hope that helps.
Click to expand...
Click to collapse
hope this helps
Ill reply when more solutions come up

azzledazzle said:
thats very respectful of you not wanting to spam the thread, but yes i will post your question now for you,
you can keep your eye on the post and watch the results, i will also post the results here when someone kindly answers it
EDIT: have you done a factory reset ? when in recovery did you format /system /cache / dalvik cache and then install MIUI
Click to expand...
Click to collapse
azzledazzle said:
hey mate had a reply, dont know if you have been checking but here is what was said
hope this helps
Ill reply when more solutions come up
Click to expand...
Click to collapse
Thanks again azzledazzle!
Yes a did a complete wipe since I as well thought that might could solve the problem, however it did not.
Okay I will have a go at it tomorrow- I guess i need to find a ROM with a bootloader and all though when downgrading from 2.3.4?

yes, im not sure which firmware contains the bootloader or if you have to check 'update bootloader' in odin, i have never had to do this, so you will have to search.
but let me know how you get on and we can go from there.
Im off to bed now its late, if you get it fixed PM me, if not il be back to check on the thread tomo

Problem is now solved!
I was thinking that MIUI gets updates all the time, and switches between kernels quite often as well, so I decided to wait for the next update with a kernel-switch.
MGv4 was released today and had the kernel-switch I had been waiting for, so I just flashed over the initial kernel for CM7 again using ODIN. Than went into CWM and updated MIUI to MGv4.
Than with my fingers crossed i tried entering CWM again and it worked like a charm.
So I did not have to go back to FroYo and all that again, just had to wait for the next update.
Thanks for your help!

[Q] Problem installing Cyanogen on Optimus 2X

Hey Guys,
Yes it is my first post on this Forum but I've been looking many thread and no one awnser correctly...(I wish im the good section for this)
So i'm trying to install Cyanogenmod on my Optimus 2X and I can't install the Clockwordmod Recovery for some reason.
Here's what I did :
1. Install LG Drivers
2. Root Phone with SuperOneClickRoot
3. Download Rom Manager
4. Flash ClockWordMod Recovery
After that it restore and BootLoop until death
The only thing I can do is remove the battery, push Volume Down and Power and the Android Recovery Manager Wipe all my data.
I also made a Video of all the steps
watch?v=vMRcYgjtf7o (I can't post Direct link since i'm a new member..)

Hello!
Can you get in the recovery system?
Did you place a copy of a downloaded CM7-ROM on your external SD card?
If yes - just go to choose .zip from SD and flash it - after that you should be good to go.
BTW: I can recommend the KANG build by koboltzz(http://bit.ly/sbUogR) - works for me and is compatible with the ironkrnL.
And don't forget you may need LG-Ril from the market since the RIL included in the CM-ROMs is always 0218 and you almost probably come from 0725 or something else - and the RIL should match your baseband - LG-Ril Version will take care of this...
Greetings
Medizinmann

No actually I can't access to the Recovery, that's the problem...
I Updated my first post with my video.
Also : What I'm suppose to do with the LG-Ril, I can see and change my Ril but everytime it say : The Ril dosent match with you Baseband...

Is your phone an Optimus 2x Wind?
Don't quote me on this but isn't that a g2x if it's a wind? Like the American one? So it needs the g2x recovery and ROMs? Or am I just talking out of my arse?
Sorry if I'm going down to the wrong road.

I finnaly made it work,
To Flash the CWM Recovery I used the NvFlasher (Work Great) : http://forum.xda-developers.com/showthread.php?t=1056847
Then I had some problems installing CM7 I looked up a bit and you were right @Fulwood Sedge I have the P999 version not the P990 wich is slighly different -_-".
Now I have CM7 Nightly running.
Thank You guys for the Help.
Last question : What Rom you guys recommend for best performance and everyday use ?

I'm using miui ATM and I totally love it. The UI changes on it are quality IMO. It's completely different look and feel and that's what I really like. And that's what I wanted from a custom rom.
Check this out: http://forum.xda-developers.com/showthread.php?t=1350761&highlight=Best+rom
It's been going for quite a while now so it gives up a good idea. But those are p990 ROMs and those won't work on your phone. So might be best to see if there is similar thread in p999 forum.

I use my phone 3-4 hours a day and I would not use anything other than Cm7 with vorkkernal. Love it, battery life is good, phone is stupid fast and basically everything works.
accelerometer calibration is a bit off though? Trials 2x doesn't really work as the acceleormeter isn't sensitive enough to tilt left/right. But rotating in web browsing etc works fine.
Sent from my Optimus 2X using Tapatalk

guy, i have problem installing and running CM7 / kang.
i was using miui rom 1.12.2. everythg works fine expect the network drop few times a day. then i tried flashing other baseband for it and same thing happened. network dropped frequently. last night i've downloaded CM-7 and kang rom. tried flash both of it but i thing i dun understand. it flashed successfully but can't boot up. waited like 5-7mins booting time after flashed each of the rom but success.
can anyone help me?
actually i like the miui rom very much. totally different from other custom rom i've been using and battery is good originally. but network keep dropping.

Just one question limkoksoon,
do you have an Optimus 2X? this is the O2X forum and i noticed in your signiture that you have a galaxy s2...?

Fulwood Sedge said:
Just one question limkoksoon,
do you have an Optimus 2X? this is the O2X forum and i noticed in your signiture that you have a galaxy s2...?
Click to expand...
Click to collapse
hi bro, sorry, i havent update my siggy for quite sometime. sold my s2 and using o2x now.
anyway, can anyone help?

What is happening..
I followed the directions exactly,
Rooted with superuser and SuperOneClick
Used ROM Manager to backup and chose Cyanogen 7.1 from the download section
Flashed ROM,
Now...its just shows the boot screen over and over for 15-20 min then everything goes black.
Did I just break my new phone?
UPDATE: Access ClockworkMod and tried to reflash .zip and clear cache, same result. As well I cannot mount my InternalSD to put on nightly CM instead of stable. Serious help needed!!!
UPDATE 2: My wife has the same phone as me, from the provider..could I copy her stock LG Optimus 2X from fido ROM and use it as a recovery for me??

ShwayJames said:
I followed the directions exactly,
Rooted with superuser and SuperOneClick
Used ROM Manager to backup and chose Cyanogen 7.1 from the download section
Flashed ROM,
Now...its just shows the boot screen over and over for 15-20 min then everything goes black.
Did I just break my new phone?
UPDATE: Access ClockworkMod and tried to reflash .zip and clear cache, same result. As well I cannot mount my InternalSD to put on nightly CM instead of stable. Serious help needed!!!
UPDATE 2: My wife has the same phone as me, from the provider..could I copy her stock LG Optimus 2X from fido ROM and use it as a recovery for me??
Click to expand...
Click to collapse
i think your phone is p999 not p990. so that's why boot loop. i don't know if there's nvflasher for p999. i hope there's one so you can restore your phone to original.
guy, i have problem installing and running CM7 / kang.
i was using miui rom 1.12.2. everythg works fine expect the network drop few times a day. then i tried flashing other baseband for it and same thing happened. network dropped frequently. last night i've downloaded CM-7 and kang rom. tried flash both of it but i thing i dun understand. it flashed successfully but can't boot up. waited like 5-7mins booting time after flashed each of the rom but success.
can anyone help me?
actually i like the miui rom very much. totally different from other custom rom i've been using and battery is good originally. but network keep dropping.
Click to expand...
Click to collapse
i don't use the kang version. flash only with cm 7.1 nightly built 204

antec123 said:
i think your phone is p999 not p990. so that's why boot loop. i don't know if there's nvflasher for p999. i hope there's one so you can restore your phone to original.
Click to expand...
Click to collapse
I have the P990-hn, should I be trying to use the Nighly Build, I can only find the -stable version. As well I found CANADA FIDO BIN_LGP990hNAT-01-V21b-302-370-AUG-23-2011+0
I am going to use that to get my phone back using the ClockworkMod Recovery.

ShwayJames said:
I have the P990-hn, should I be trying to use the Nighly Build, I can only find the -stable version. As well I found CANADA FIDO BIN_LGP990hNAT-01-V21b-302-370-AUG-23-2011+0
I am going to use that to get my phone back using the ClockworkMod Recovery.
Click to expand...
Click to collapse
Did you wiped/format all partitions before flashing cm7 ? It's mandatory when you change totally of ROM type.
You'd better use nightly, links are on the cm7 nightly download page.
In cm7 internal sdcard is mounted as /mnt/emmc. External is mounted as /mnt/sdcard.
Last thing: the file you grabbed is not a cwm file but a smartflash one I guess....

no way you can use CWM with that version. it only can use with smartflash

Striatum_bdr said:
Did you wiped/format all partitions before flashing cm7 ? It's mandatory when you change totally of ROM type.
You'd better use nightly, links are on the cm7 nightly download page.
In cm7 internal sdcard is mounted as /mnt/emmc. External is mounted as /mnt/sdcard.
Last thing: the file you grabbed is not a cwm file but a smartflash one I guess....
Click to expand...
Click to collapse
Yes your right I see that now, would I be able to use that with smartflash to get my phone unbricked? What would someone suggest?
---------- Post added at 01:51 AM ---------- Previous post was at 01:44 AM ----------
I used the nightly to no success, same old and yes I wiped the data, cache's. I am looking at using smartflash and stock ROM I found here on XDA
---------- Post added at 02:34 AM ---------- Previous post was at 01:51 AM ----------
antec123 said:
i think your phone is p999 not p990. so that's why boot loop. i don't know if there's nvflasher for p999. i hope there's one so you can restore your phone to original.
i don't use the kang version. flash only with cm 7.1 nightly built 204
Click to expand...
Click to collapse
I GOT IT!!! CLEARED BOTH CACHE'S and DATA then re added the nightly!!!!!

ShwayJames said:
Yes your right I see that now, would I be able to use that with smartflash to get my phone unbricked? What would someone suggest?
---------- Post added at 01:51 AM ---------- Previous post was at 01:44 AM ----------
I used the nightly to no success, same old and yes I wiped the data, cache's. I am looking at using smartflash and stock ROM I found here on XDA
Click to expand...
Click to collapse
yes your phone will be unbricked if using smartflash like new again.

[Q] FASTY III problem/question

HI!
Just recently signed up so I can't seem to post this question in the FASTY III forum....I kind of understand why xda has this policy about new members not being able to post int he developmental forums...but still...
I recently moved from FASTY II to III...ran into a bunch of issues but I managed to resolve most of them by going through the forums. What I am having trouble with is my inability to get to the Recovery menu. I have tried to go there thru the shutdown menu, by doing the button holding trick, and even from ROM Manager... none of those seem to work for me. Very frustrating... All those mentioned attempts only bring up an ATT screen which wont go away until I reboot the phone into a normal start....
So why am I unable to enter Recovery mode?
Any help would be much appreciated. Thank you!

nycmon said:
HI!
Just recently signed up so I can't seem to post this question in the FASTY III forum....I kind of understand why xda has this policy about new members not being able to post int he developmental forums...but still...
I recently moved from FASTY II to III...ran into a bunch of issues but I managed to resolve most of them by going through the forums. What I am having trouble with is my inability to get to the Recovery menu. I have tried to go there thru the shutdown menu, by doing the button holding trick, and even from ROM Manager... none of those seem to work for me. Very frustrating... All those mentioned attempts only bring up an ATT screen which wont go away until I reboot the phone into a normal start....
So why am I unable to enter Recovery mode?
Any help would be much appreciated. Thank you!
Click to expand...
Click to collapse
in terminal emulator type su and then reboot recovery maybe it work
or may be you just flashed unsupported recovery

nycmon said:
HI!
Just recently signed up so I can't seem to post this question in the FASTY III forum....I kind of understand why xda has this policy about new members not being able to post int he developmental forums...but still...
I recently moved from FASTY II to III...ran into a bunch of issues but I managed to resolve most of them by going through the forums. What I am having trouble with is my inability to get to the Recovery menu. I have tried to go there thru the shutdown menu, by doing the button holding trick, and even from ROM Manager... none of those seem to work for me. Very frustrating... All those mentioned attempts only bring up an ATT screen which wont go away until I reboot the phone into a normal start....
So why am I unable to enter Recovery mode?
Any help would be much appreciated. Thank you!
Click to expand...
Click to collapse
I have been having the same problem recently, but not just with this rom. I have flashed many roms to my device, but it appears that almost everytime i try to flash something now, the same exact thing happens as the OP. any information on what is wrong or how to fix this would be greatly appreciated.

When you boot up...do you guys get a scrambled screen that looks like white noise?
that's caused by froyo bootloaders on a gingerbread ROM.
Not all That familiar with fasty though...dunno of the jump from 2 to 3 was froyo to ginger, just a guess.

studacris said:
When you boot up...do you guys get a scrambled screen that looks like white noise?
that's caused by froyo bootloaders on a gingerbread ROM.
Not all That familiar with fasty though...dunno of the jump from 2 to 3 was froyo to ginger, just a guess.
Click to expand...
Click to collapse
Sometimes this happens, but i am usually still able to use the rom after i wait for awhile. Recently it just gets stuck at the ATT logo screen and does nothing else.

HERE is a package containing JUST the ginger boots.
MAKE SURE YOU HAVE A GOOD PHONE/PC CONNECTION, FLASHING BOOTLOADERS IS THE ONLY WAY TO TRULY HARD BRICK

studacris said:
HERE is a package containing JUST the ginger boots.
MAKE SURE YOU HAVE A GOOD PHONE/PC CONNECTION, FLASHING BOOTLOADERS IS THE ONLY WAY TO TRULY HARD BRICK
Click to expand...
Click to collapse
i just tried it with a solid connection and it almost instantly said failed in the red box. now i cant turn it on or get to download mode so im pretty sure it is hard bricked. is there any way you can help me with this?
EDIT: False alarm, i can still get to download mode so i can ODIN back to stock, but i do not know if i should risk it again

Whew that was close.
You can flash to stock using a bootloader less package, that way if it fails it can't hard brick.
Then if that works, find an entire stock gingerbread package with bootloaders included, and flash that instead of just the bootloader one click. this again, will involve risk, but full Odin package seem to work better on some phones than one clicks do.

I tried to flash the bootloader again and it succeeded. i then proceeded to try and flash Fasty KK4 v1.1 and once again i was stuck at the ATT logo. For some reason with every rom i flash, when the logo pops up, it starts dim and then get bright. After it gets bright, it stays that way and it is a real pain not being able to use custom roms anymore.

If you have the GB bls just make sure you follow LL's instructions in the OP for Fasty. I had the same issue, but it was me mistake for not following the istructions properly

studacris said:
When you boot up...do you guys get a scrambled screen that looks like white noise?
that's caused by froyo bootloaders on a gingerbread ROM.
Not all That familiar with fasty though...dunno of the jump from 2 to 3 was froyo to ginger, just a guess.
Click to expand...
Click to collapse
i DO get a very colorful white noise screen whenever it boots up ...the screen goes away once it fully reboots....I wondered about it but just assumed it was a quirk of the FASTY III package...
Is Rom Manager a froyo based app?

No, ROM manager is poop. Not implemented on galaxy devices properly, and won't work past eclair, and even them it was severely limited to just downloading an update.zip to your sdcard...which you could put there manually with out having to root...
FORGET ROM MANAGER EXISTS

studacris said:
No, ROM manager is poop. Not implemented on galaxy devices properly, and won't work past eclair, and even them it was severely limited to just downloading an update.zip to your sdcard...which you could put there manually with out having to root...
FORGET ROM MANAGER EXISTS
Click to expand...
Click to collapse
Really? Rom Manager helped me a lot until this Fasty III installation....even in my previous rom Fasty II it worked fine and did great for backing up and restoring backups....saved my asss a few times with those restores lol....But if this program doesn't work for fasty III what comparable program can I use?
Also I still can't intorecovery mode...nothing works...I even tried using ADB and Droid Explorer....nothing seems to get it into recovery mode...
Am I going to have to flash back to stock ROM and try reinstalling fasty iii again? This seems all so tedious lol...
OR is there a way for me to flash back to Fasty II without having to go back to stock rom? or without having to access the recovery screen?
Thank you^

All that backing up and restoring you did with ROM manager can be done in cwm recovery and that's what you should use from now on. No app needed at all.
Follow the instructions I've already provided in this thread. You'll either need Odin to flash the gingerbread bootloaders,
or to go back to a froyo firmware, first flash a froyo kernel with Odin and THEN the froyo ROM. stock isn't needed.
Recovery in a gingerbread kernel is completely inaccessible with froyo bootloaders.

studacris said:
All that backing up and restoring you did with ROM manager can be done in cwm recovery and that's what you should use from now on. No app needed at all.
Follow the instructions I've already provided in this thread. You'll either need Odin to flash the gingerbread bootloaders,
or to go back to a froyo firmware, first flash a froyo kernel with Odin and THEN the froyo ROM. stock isn't needed.
Recovery in a gingerbread kernel is completely inaccessible with froyo bootloaders.
Click to expand...
Click to collapse
Thank you for the info!
Looks like fasty III is a GB based mod after all...I guess I should read up more on the rom before installing lol....I did not expect the dev to go from froyo to gb -_-
I was thinking of using your previous post for the one click gb bootloaders only....but it seems a little iffy and I can't afford to hardware brick the phone lol...
Makes me wonder tho...is it really THAT risky to flash bootloaders? It would make things simpler if i could just flash the gb bootloaders and go from there....

the whole flash should take less than a minute, where the actual writing takes only a few seconds...but if you were to lose communication in that awful window then it would be bad day.
But that is a small window, and if you have never had connection issues you should be ok if Odin tends to be iffy, you van try heimdall I've heard that works better for some.

Still haven't tried flashing the bootloaders because i'm scared of the possibility of hard bricking my phone... If worst case scenario was to happen and it gets hard bricked....are there any options to restore that phone? or is it just paper weight after?
Also until I flash those bootloaders there is no way to back up my phone or anything?
Thanks for all ur help btw!

another issue i am having is that the phone seems pretty laggy after installing this rom...even with tegra overclock premium and tweaking it up to 1252mhz 1275mv 1100mv setting...it still seems laggy when opening sms etc....is this just the results of a bad rom install? also battery life seems crappy....even after doing the battery recalibration...of course i couldn't wipe the battery stats since i cant get into recovery...

Hard bricks are recoverable by a hardware modification known as unbrickable mod, search for user Adam outler, or go to mobiletechvideos.com they both offer this service if you're not a soldering expert.
Battery recalibration does NOTHING the stats are reset everytime you charge to 100, and besides that they don't calculate your current battery level, just what's been using it, its what's used in settings> about phone> battery use. It has nothing to do with extending battery life.

oh lol...i have been reading all these threads where people are talking about how much their battery life improved after they did the recalibration and stat wipe ....well anyways I am going to attempt the bootloader flashing...I hope everything goes well! after that I want to try reflashing the fasty III ROM...
Do you have any recommendations as far as a good ROM for teh captivate? One that doesn't lag and has good gps & battery life? I would appreciate any help you can give.
Thanks!

[Q] Random Freezing on Galaxy Tab

Hi everyone, first post on this forum.
I have a used Uk Tab, P1000. It came with Stock Gingerbread.
I keep getting freezing on it with different Roms e.g Overcome, Boca, Miui.
this could be in any apparently or even scrolling between screen. A quick press of the power button back to the lock screen will wake it up but it's annoying.
However Cyanogen Mod 7 is stable. No frezzing
I have cleared down all caches and factory reset on installs.
Any thoughts or anyone had similar with a fix?
Thanks

Hi, same thing was happening to me A LOT with standard Gingerbread rom from Kies.
Complete freeze of the screen(touch and capacitive buttons) until new lock+unlock.
So I guess it's not a custom rom problem.
However I do not know what could be the issue.
I 'fixed' it (by that I mean it happens much less frequently now) with Dolphin Companion.
Maybe it is some process in the background?
While i was researching the issue online I found many people complaining about this on forums and whatnot.

Hi
Thanks for the reply.
I wanted to try another ROM (ICS) but when I tried to go back to CM7, the restore failed confused, so I've restocked and back to Overcome 4.01 using the standard instructions. Still still hangs with Dolphin Companion.
Annoying as I don't want to keep restocking. Any ideas how I can identify what the issue is anyone? Seems to hang on anything Internet related e.g Hotmail App and Browsers.
My model of device is GT-P1000. When I got the device it was already rooted on GB. Is it worth restocking with Froyo then GB again?
Where did u see other people complaining - got the URL's?
Thanks

i think it is normal for most phone to 'freeze' that need to reboot. mine too sometimes it freeze when i play game. but if it is too frequent (like my x10 mini pro) then it is somewhat related to hardware. but some believe that by flashing to other rom the problem can be fix for a while.

EdwardCheong said:
Hi
Thanks for the reply.
I wanted to try another ROM (ICS) but when I tried to go back to CM7, the restore failed confused, so I've restocked and back to Overcome 4.01 using the standard instructions. Still still hangs with Dolphin Companion.
Annoying as I don't want to keep restocking. Any ideas how I can identify what the issue is anyone? Seems to hang on anything Internet related e.g Hotmail App and Browsers.
My model of device is GT-P1000. When I got the device it was already rooted on GB. Is it worth restocking with Froyo then GB again?
Where did u see other people complaining - got the URL's?
Thanks
Click to expand...
Click to collapse
hi edward. I have a suggestion for you. Try to flash your firmware to the latest build.. you can view it by clicking at this link http://www.youtube.com/watch?v=4K75QwV4aDw. This is the best build so far ever i have tried. so smooth + no laggy.
---------- Post added at 12:28 AM ---------- Previous post was at 12:24 AM ----------
Hi again. U always can help your self by opening this great link websites to solve all your problems
http://www.youtube.com/watch?v=RtWdNqwAETs
http://www.youtube.com/watch?v=CAK9i_ISeqM
http://www.humberos.com.br/p/android-ics.html
cheers

[Q] How can i fix DATAFS particion?''

Hi all.
i´ve flash the last ics firmware with bootloader pit repartition an all the file. all that thing go wonderfull. i whant to go back to my kingdroid rom doing fullwipe. i reboot into recovery and i flash a cwm temporary. i go to wipe cache dalvik but data got stuck. i pull out the battery and i´ll see that the phone its stuck into bootloop. i tryed to flash a stock gingerbread, a stock ics a custom rom and avery thing go stuck in odin pc on DATAFS. can i fix it??

Dr.Taly said:
Hi all.
i´ve flash the last ics firmware with bootloader pit repartition an all the file. all that thing go wonderfull. i whant to go back to my kingdroid rom doing fullwipe. i reboot into recovery and i flash a cwm temporary. i go to wipe cache dalvik but data got stuck. i pull out the battery and i´ll see that the phone its stuck into bootloop. i tryed to flash a stock gingerbread, a stock ics a custom rom and avery thing go stuck in odin pc on DATAFS. can i fix it??
Click to expand...
Click to collapse
Why don't you ask Entropy512 in a PM? He's best qualified to give you an answer to your question.
Everything else you're likely to get here would be pure conjecture.

It would be nice to know however, was it LPF of LPY.
and while, yes, entropy knows a lot of things, not all samsung flashers are dumbots that can not systematically analyze such information.

If he has bootloader on this, cant i sound like its LPF ?
If so its sounds like the same problems Ficeto from darky team had on LPY ?

opsakas said:
It would be nice to know however, was it LPF of LPY.
and while, yes, entropy knows a lot of things, not all samsung flashers are dumbots that can not systematically analyze such information.
Click to expand...
Click to collapse
Why don't you systematically analyze the information and offer us a viable way of getting out of the superbrick situations?
I freely admit that I am a dumbot when it comes to that, and could use some help.

Well, statement about bootloader does not mean anything. It is an assumption and thus not reliable in such situation. People do mix files, intentionally, unintentionally, and by chance.
But then again, we all know what is in common with 99.9% of hardbricks.
And the 'reported' few cases of bricking on stock fw - is it sure that these phones were never-ever flashed with anything else than stock?
But as for devs, i have to stress one thing. The higher the price of failure, the more we tend to find culprits outside of our own circles. And it is human. One of the toughest things to admit is always admitting one's own part in unwanted results.

In other words, you don't know squat, but are offering general philosophical musings instead.

What i am thinking... Is it that in Germany the service centers are really overcrowded these days? I do not have information, but if that would have been the case, some information would be even here in XDA.
And with the stock fw brick - with every flash there is risk for small percentage of failure. Perhaps that was the one.
It seems that there may be almost identical functions for handling file system. Perhaps in raw level and perhaps there is only one function but it depends of the parameters.
What it seems to me is that custom roms are working just abit too fast. Perhaps with stock ther is no chance for the error show out.
And going into dark side, i personally have met with several serious computer and related malfunctions during last week. The sun activity or something else similar may cause undesired effects where tolerances are too tight. The 32 k of zeroes might be written not by random but by some input that may depend on things that creators of the chip could not foresee - but nevertheless exists.
For practical considerations i assume the custom roms allow the note to execute some functions too fast.
---------- Post added at 11:31 AM ---------- Previous post was at 11:29 AM ----------
There is one word and that is responsibility. You might want to think about it.
---------- Post added at 11:32 AM ---------- Previous post was at 11:31 AM ----------
Well, statement about bootloader does not mean anything. It is an assumption and thus not reliable in such situation. People do mix files, intentionally, unintentionally, and by chance.
But then again, we all know what is in common with 99.9% of hardbricks.
And the 'reported' few cases of bricking on stock fw - is it sure that these phones were never-ever flashed with anything else than stock?
But as for devs, i have to stress one thing. The higher the price of failure, the more we tend to find culprits outside of our own circles. And it is human. One of the toughest things to admit is always admitting one's own part in unwanted results.