i just updated my at&t Samsung SGH-I897 captivate to firmware version to 2.3.5. which unrooted my phone, so i re rooted it and now i got everything working, But when I go into wifi i can enable it and then it says that it's searching for wifi connections and then shuts off. can anyone give me any ideas on whats wrong? thanks!
Stock rom??
what did you flash to root it??
a little more details would be helpful
your device access point names may need tweakin...I had the same problem on my cappy...ur in prime position to flash cyanogen...guarantee that will fix the problem whatever it is.
My phone got messed up! it just keeps restarting and showing the at&t then reboots. it will not do a recovery either. So I got a new one today and it has 2.2 firmware. can someon post me the stuff to re root it to be sure i done mess this one up? thanks
mikeyw8187 said:
My phone got messed up! it just keeps restarting and showing the at&t then reboots. it will not do a recovery either. So I got a new one today and it has 2.2 firmware. can someon post me the stuff to re root it to be sure i done mess this one up? thanks
Click to expand...
Click to collapse
SuperOneClick by CLShortfuse. I've always been partial to v1.9 or lower for 2.2 ROMS.
thanks alot! i re rooted my phone using super1click. Just wanted to make sure it was still safe to use.
Hi everyone.
I have an Optimus 2x, and when i updated it to 2.3.4 i could not use superoneclick to root my phone instead i found an answer on how to root it.
I needed to install cwm 5 and after that busybox and so on, and it worked, it was rooted.
Now i have a other problem, i have an update on my phone and when i click on installing it starts to reebot then it comes to cwm screen, there i'm stuck.
I have tryed everything there trying to update it but nothing works.
So now i am wondering if any of you can help me?
Got any idea what i can do to update or what i am doing wrong?
//Szander.
Ok, so now i did a recover so i get back my phone as it was before i installed cwm and tryed to update, it did work fine.
Until the update was done, then it stopped, and nothing i did worked the little android just stand there and looked at me.
So what now, i removed the battery and hoped for the best, now the phone would not bot at all.
After a few tears and a few swear words, i thougt about something, maybe i could use nvflash to get it all back as it was ???
I tryed closed my eyes and after a few minutes i could restart my phone and it loaded as useall, but the update was gone, ofcourse.
So now back to square one again.
Sigh (
Hi Szander,
So just to be completely clear, you're back at a perfectly stock 2.3.4 unrooted ROM and you want to root it, right?
Why not trying to follow cyanogen wiki to root it?
LarsPT said:
Hi Szander,
So just to be completely clear, you're back at a perfectly stock 2.3.4 unrooted ROM and you want to root it, right?
Why not trying to follow cyanogen wiki to root it?
Click to expand...
Click to collapse
No.
I have cwm, and its still rooted.
What i want is to get rid of cwm so i can update to the latest update wich is v20q.
I have tryed this with recover but its only working on froyo, i belive i read it somewhere.
And when i recovered my phone then the problem really started, but thats fine now.
And as an plus is that now when i run LGMobileupdate tool its saying that i have v20q but in the phone it says that i still have v20I.
Weird.
I have read alittle more and (if i got it right) found out that i might just need to use smartflash on the phone via my computer to get rid of cwm and get a perfectly stocked phone again.
So can you help me please, hoping that you understand my problem.
Yup, as far as I know you are correct. To get your phone back to stock you need to flash a stock ROM using either smartflash or nvflash. I haven't done it so I can't guide you through it personally, but search this forum you should find the relevant threads easily enough.
If you have trouble finding it let me know I'll help you searching.
EDIT: By the way, thanks for Meshuggah, one of the best bands ever I should visit Sweden sometime
Hey guys,
First of all, I'm new to this, so please bear with me. To cut a long story short, I attempted to install the CyanogenMod RC on my Galaxy Note N7000 today. I followed the instructions I found on the web somewhere (can't remember of it was XDA) and after attempting to wipe my device from the ClockwordMod, I appear to have bricked it.
My Note no longer gets passed the startup screen. I've tried everything I can to revive it, and I've been searching XDA all day for a solution, with little success. I've tried flashing a number of kernels, and a number of ROMs, including stock GB and stock ICS. I can still get into both Download and Recovery mode (which I'm hoping is a good sign) but when I try to flash a ROM with Odin, it gets stuck on the "factoryfs" stage.
I've tried flashing the PIT repartition file at least four or five times, but that doesn't seem to be helping at all.
Does anyone have any other ideas? I'd really just like to get back to stock ICS. I just fancied playing around with CyanogenMod for a bit, but I wish I hadn't tried. Thanks in advance for any help!
Were you on stock ICS when you did the wipe ?
Akiainavas said:
Were you on stock ICS when you did the wipe ?
Click to expand...
Click to collapse
Yes, downloaded via Kies.
I think you have fallen victim to the infamous eMMC "superbrick". Contact Samsung, they are well aware of this problem and will surely replace it for you as it's plaguing devices running their stock ICS. The problem is with their kernel and the eMMC chip to it doesnt even matter what were you trying to do.
When they do replace it - first, flash a GB rom via Odin, and then install CM9. CM9 kernel is safe and superbrick bug free. Whatever you do - never try doing a wipe/factory reset on stock Samsung ICS rom.
Akiainavas said:
I think you have fallen victim to the infamous eMMC "superbrick". Contact Samsung, they are well aware of this problem and will surely replace it for you as it's plaguing stock ICS devices. The problem is with their kernel and the eMMC chip to it doesnt even matter what were you trying to do.
When they do replace it - first, flash a GB rom via Odin, and then install CM9. CM9 kernel is safe and superbrick bug free. Whatever you do - never try doing a wipe/factory reset on stock Samsung ICS rom.
Click to expand...
Click to collapse
Yeah, I feared that was the case. The problem is, I now have the yellow warning triangle on bootup, and my "binary count" has increased to 9. Does this mean Samsung won't replace it?
if that's the case, is there any way to reset the binary count and remove the triangle in its current state?
You might try resetting the counter with a jig. I don't know if it will work in its state, but you may not have much to lose.
Sent from a guy on a buffalOOooo.
Generally - USB Jig is the only way to reset it on a bricked device.
There is one way other way though:
http://www.mediafire.com/?5bmrc6cf81w5mya
This kernel is supposed to reset binary counter, and many users reported that it actually did the trick - mind that this kernel also causes hard brick. It's a last effort for people whose devices are already bricked.
You nees to flash it via Odin, disconnect and go into recovery. At first boot you will still see the triangle - in the recovery, select reboot. Now the triangle should disappead, and binary counter should be set to "no".
Remember that this kernel causes a hard brick. Use it only if your device is already bricked and you intend to send it to Samsung. It will work only on ICS devices.
Akiainavas said:
Generally - USB Jig is the only way to reset it.
There is one way other way though:
http://www.mediafire.com/?5bmrc6cf81w5mya
This kernel is supposed to reset binary counter, and many users reported that it actually did the trick - mind that this kernel also causes hard brick. It's a last effort for people whose devices are already bricked.
You nees to flash it via Odin, disconnect and go into recovery. At first boot you will still see the triangle - in the recovery, select reboot. Now the triangle should disappead, and binary counter should be set to "no".
Remember that this kernel causes a hard brick. Use it only if your device is already bricked and you intend to send it to Samsung.
Click to expand...
Click to collapse
Thanks very much for your help. I really appreciate it.
So do you think it's worth contacting Samsung first - before trying to reset the binary - or do you think they'll refuse to replace it once they know I tried flashing an unsupported ROM?
Thanks again!
I think you might try contacting them first, just ask all the info you need without giving them the serial numbers - before you send the phone in. They might replace it anyway - they know very well it happens because of their defective kernel/emmc chip. Although i'm afraid they might find out and refuse to fix it for free.
If they turn you down, then flash the kernel and contact them again. If you're going to do it in person and they refuse cause they "remembered you" ( shocking, but it happens... ) then simply get a friend or family to bring them your phone.
Just say that Kies messed up your phone - they'll know what the problem is
Hope they'll get it fixed for you. Let us know how it went.
Akiainavas said:
I think you might try contacting them first, just ask all the info you need without giving them the serial numbers. They might replace it anyway - they know very well it happens because of their defective kernel/emmc chip.
If they turn you down, then flash the kernel and contact them again. If you're going to do it in person and they refuse cause they "remembered you" ( shocking, but it happens... ) then simply get a friend or family to bring them your phone.
Just say that Kies messed up your phone - they'll know what the problem is
Hope they'll get it fixed for you. Let us know how it went.
Click to expand...
Click to collapse
Okay, I'll do that. Thanks again for all the info! I'll let you know how I get on.
kill.i.an said:
Hey guys,
First of all, I'm new to this, so please bear with me. To cut a long story short, I attempted to install the CyanogenMod RC on my Galaxy Note N7000 today. I followed the instructions I found on the web somewhere (can't remember of it was XDA) and after attempting to wipe my device from the ClockwordMod, I appear to have bricked it.
My Note no longer gets passed the startup screen. I've tried everything I can to revive it, and I've been searching XDA all day for a solution, with little success. I've tried flashing a number of kernels, and a number of ROMs, including stock GB and stock ICS. I can still get into both Download and Recovery mode (which I'm hoping is a good sign) but when I try to flash a ROM with Odin, it gets stuck on the "factoryfs" stage.
I've tried flashing the PIT repartition file at least four or five times, but that doesn't seem to be helping at all.
Does anyone have any other ideas? I'd really just like to get back to stock ICS. I just fancied playing around with CyanogenMod for a bit, but I wish I hadn't tried. Thanks in advance for any help!
Click to expand...
Click to collapse
You may also try manual/adb repartition method described in here to revise your phone. cheers.
kill.i.an said:
Hey guys,
First of all, I'm new to this, so please bear with me. To cut a long story short, I attempted to install the CyanogenMod RC on my Galaxy Note N7000 today. I followed the instructions I found on the web somewhere (can't remember of it was XDA) and after attempting to wipe my device from the ClockwordMod, I appear to have bricked it.
My Note no longer gets passed the startup screen. I've tried everything I can to revive it, and I've been searching XDA all day for a solution, with little success. I've tried flashing a number of kernels, and a number of ROMs, including stock GB and stock ICS. I can still get into both Download and Recovery mode (which I'm hoping is a good sign) but when I try to flash a ROM with Odin, it gets stuck on the "factoryfs" stage.
I've tried flashing the PIT repartition file at least four or five times, but that doesn't seem to be helping at all.
Does anyone have any other ideas? I'd really just like to get back to stock ICS. I just fancied playing around with CyanogenMod for a bit, but I wish I hadn't tried. Thanks in advance for any help!
Click to expand...
Click to collapse
IF U CAN GET INTO RECOVERY UR NOT BRICKED OR SUPER BRICK TRUST ME I HAVE A NOTE HERE THATS BRICKED...IF INDEED ITS BRICKED U CANT GET IN ****!!! u just soft bricked it...flash stock recovery b4 tar or what ever it is
Sent from my SAMSUNG-SGH-I717 using xda premium
forest1971 said:
You may also try manual/adb repartition method described in here to revise your phone. cheers.
Click to expand...
Click to collapse
Thanks!
JB calhoun said:
IF U CAN GET INTO RECOVERY UR NOT BRICKED OR SUPER BRICK TRUST ME I HAVE A NOTE HERE THATS BRICKED...IF INDEED ITS BRICKED U CANT GET IN ****!!! u just soft bricked it...flash stock recovery b4 tar or what ever it is
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Stock recovery? Where would I find that?
The problem is, I cannot flash any ROM. It just hangs during the "factoryfs" process in Odin. When I try to install stuff via ClockworkMod recovery, it fails. Sometimes I get an error like "cannot mount (or access) /system."
JB calhoun said:
IF U CAN GET INTO RECOVERY UR NOT BRICKED OR SUPER BRICK TRUST ME I HAVE A NOTE HERE THATS BRICKED...IF INDEED ITS BRICKED U CANT GET IN ****!!! u just soft bricked it...flash stock recovery b4 tar or what ever it is
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Not true I'm afraid...
If you've damaged the eMMC chip:
- You can still get into recovery.
- You can still get into download mode.
If you did a factory reset on stock ICS kernel and can't flash "factoryfs" data because Odin gets stuck at this point, and repartitioning does not help - that's the "superbrick".
It happens because using data wipe on stock ICS kernel runs a format procedure which damages Note's defective eMMC chip. If it happened, repartitioning won't help as parts of the storage are corrupted and Odin simply cannot put data there. I seriosusly don't know how could Samsung not see that the format command introduced in ICS ( it was not present in GB, that's why GB kernels are safe ) damages the chip... didn't they test the software at all ?
Take a look here:
http://forum.xda-developers.com/showthread.php?p=28048062
This guy managed to recover his device, but what he's left with is Note with 3-4GB less storage, and remember that once the eMMC chip is damaged, it will never be completely reliable again.
Here's a guide on how to revive superbricked Note. Bear in mind it might not work though:
http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
It's still best to try and get it replaced though. If Samsung won't replace it for free - then try reviving it.
Akiainavas said:
Not true.
If you've damaged the eMMC chip:
You can still get into recovery.
You can still get into download mode.
If you did a factory reset on stock ICS kernel and can't flash "factoryfs" data because Odin gets stuck at this point, and repartitioning does not help - that's the "superbrick".
It happens because using data wipe on stock ICS kernel runs a format procedure which damages Note's defective eMMC chip. If it happened, repartitioning won't help as parts of the storage are corrupted and Odin simply cannot put data there.
Take a look here:
http://forum.xda-developers.com/showthread.php?p=28048062
This guy managed to recover his device, but what he's left with is Note with 3-4GB less storage, and remember that once the eMMC chip is damaged, it will never be completely reliable again.
Here's a guide on how to revive superbricked Note. Bear in mind it might not work though:
http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
It's still best to try and get it replaced though. If Samsung won't replace it for free - then try reviving it.
Click to expand...
Click to collapse
Yeah, I'm certainly going to speak to Samsung over the next few days. I'm going to wait a little while for my JIG to arrive and try to remove the binary count, then I'll give them a call. I don't see how they can refuse to replace it really —*it is their software that caused this (I think).
Keeping my fingers crossed.
Thanks for all the advice, guys.
kill.i.an said:
Yeah, I'm certainly going to speak to Samsung over the next few days. I'm going to wait a little while for my JIG to arrive and try to remove the binary count, then I'll give them a call. I don't see how they can refuse to replace it really —*it is their software that caused this (I think).
Keeping my fingers crossed.
Thanks for all the advice, guys.
Click to expand...
Click to collapse
JIG is probably the best thing to do. Clear the counter, get rid of triangle and send it in. As you said - it's Samsung's kernel that causes this, and they know it.
Good luck mate.
Okay, here's a surprise: Because I can still enter download and recovery mode, I decided I would try to reset the binary counter before my JIG gets here. So I downloaded the kernel from another thread, and it worked perfect. I then tried to flash the stock ICS ROM so that there was no evidence of another one, and this time it didn't get stuck on "factoryfm" in Odin.
So I now have a working Galaxy Note. I have no idea how that happened (maybe the PIT I flashed earlier kicked in), but it's working.
Now the question is, do I attempt to install CyanogenMod again, or should I just stick to a working Galaxy Note and be happy?
Stay with what you have.
Sent from my GT-N7000 using xda app-developers app
kill.i.an said:
Okay, here's a surprise: Because I can still enter download and recovery mode, I decided I would try to reset the binary counter before my JIG gets here. So I downloaded the kernel from another thread, and it worked perfect. I then tried to flash the stock ICS ROM so that there was no evidence of another one, and this time it didn't get stuck on "factoryfm" in Odin.
So I now have a working Galaxy Note. I have no idea how that happened (maybe the PIT I flashed earlier kicked in), but it's working.
Now the question is, do I attempt to install CyanogenMod again, or should I just stick to a working Galaxy Note and be happy?
Click to expand...
Click to collapse
How much capacity do you have on your internal storage? If it is less than 11GB you may have a damaged chip and just managed to unbrick it.
I think if you can flash GB with Odin you should be fine, and once you get to GB everything is (relatively) safe.
I had a similar problem when I was trying to flash GB from stock ICS using odin, it stuck at FactoryFS and I thought I had superbricked it, but it turns out I was using a dodgy USB cable and using a good USB cable I managed to flash GB again and recover it, and now I am using CM9 - Never going back to stock ICS after this.
Ok,
Telus Galaxy Ace
did the root thing - no problem worked
then I did hte CWM thing - no problem worked
try to install file cm_ace-ota-eng.maclaw.beta1 it says it installs successfully but when the phone boots the screen just goes black,
restored with Odin tried again...same result.
This is not my main phone and I just bought it as something to learn with so no urgency but any thoughts input etc would be appreciated.
Which firmware did you flash from Odin?
Thanks for quick response
TJ_Ahluwalia said:
Which firmware did you flash from Odin?
Click to expand...
Click to collapse
I flashed this file
S5830DTLKI4_S5830DTLSKI4_S5830DTLKI4_HOME.tar
this brought me back to the default telus install device is working ok boots as per normal etc.
I have restored twice now, I am not really worried about pooching the device as snooping around here I learned enough about making backups etc
But I would like to try this jellybean business
GOT IT!!!!!!!!!!!!
Ok I got it to go
I install clockworkmodace.zip from one of the threads here, then upgraded to 5.0.2.6 CWM then did the install of cm_ace-ota-eng.maclaw.beta1
then cleared the c ache and user data reboot and tada works
mods feel free to close this thread I am going to go play with my new toy