i was trying to install cm7 after seeing it everywhere,i was on gingerbread. tried to install it it didn't work just went to recovery screen every time, then i read i had to be using froyo so i downgraded to froyo , successfully downgraded, i noticed i didnt have recovery nor download, so i installed rom manager so i can install recovery, didnt work so installed cm7 from the app, phone powered on then vibrated,went to random repair shop(Somalian) they said he can fix it, then he said i damaged the boot sector so he said he can do it, left it to him, couldnt do it, after he tried fixing it, phone didn't power on (worse) he did say samsung will fix it because he repaired the boot sector and they will fix it. phone was rooted with froyo software.
WILL SAMSUNG FIX THIS ISSUE, TOLD THEM IT WAS AN ISSUE AFTER UPDATING THROUGH THE KIES SOFTWARE . HAS ANYONE ELSE HAD THIS ISSUE
(IN THE UK) URGENT SENT IT TO THEM WAITING FOR IT
whlzibos said:
i was trying to install cm7 after seeing it everywhere,i was on gingerbread. tried to install it it didn't work just went to recovery screen every time, then i read i had to be using froyo so i downgraded to froyo , successfully downgraded, i noticed i didnt have recovery nor download, so i installed rom manager so i can install recovery, didnt work so installed cm7 from the app, phone powered on then vibrated,went to random repair shop(Somalian) they said he can fix it, then he said i damaged the boot sector so he said he can do it, left it to him, couldnt do it, after he tried fixing it, phone didn't power on (worse) he did say samsung will fix it because he repaired the boot sector and they will fix it. phone was rooted with froyo software.
WILL SAMSUNG FIX THIS ISSUE, TOLD THEM IT WAS AN ISSUE AFTER UPDATING THROUGH THE KIES SOFTWARE . HAS ANYONE ELSE HAD THIS ISSUE
(IN THE UK) URGENT SENT IT TO THEM WAITING FOR IT
Click to expand...
Click to collapse
I think, therefore fail to understand, that might even fix it yourself. Could enter download mode?
You should have bought the USB jig to force boot into download mode. Less hassle.
Nevertheless Samsung will fix it for you.
no download mode
i wasn't able to go into download mode i tried many things, i thought of getting the jig but its for semi bricked i think mine was fully bricked.
you said they will fix it, have you tried it before and how do you know (no offence)
Hi,
Yes samsung will fix it, i did it once !
It's when i tried to flash my first ROM, i used ODIN and during the flashing, it failed, and i did not have the 3-button-combo to go back into download mode...
Result : Phone bricked...
I sent it back to samsung saying that my computer turned off during an upgrade using Samsung Kies.
They gave it back to me after 2 weeks!
if you're newly flashing the CM7, then after the installation, it goes bootloop then go to recovery, over and over. remove the battery, then go to recovery(volume up+homebutton+powerkey) then flash it again. try that.
price
Skiess said:
Hi,
Yes samsung will fix it, i did it once !
It's when i tried to flash my first ROM, i used ODIN and during the flashing, it failed, and i did not have the 3-button-combo to go back into download mode...
Result : Phone bricked...
I sent it back to samsung saying that my computer turned off during an upgrade using Samsung Kies.
They gave it back to me after 2 weeks!
Click to expand...
Click to collapse
how much was it for samsung to fix it ?
not trying cm7 again
nieohl said:
if you're newly flashing the CM7, then after the installation, it goes bootloop then go to recovery, over and over. remove the battery, then go to recovery(volume up+homebutton+powerkey) then flash it again. try that.
Click to expand...
Click to collapse
never trying cm7 again
whlzibos said:
i wasn't able to go into download mode i tried many things, i thought of getting the jig but its for semi bricked i think mine was fully bricked.
you said they will fix it, have you tried it before and how do you know (no offence)
Click to expand...
Click to collapse
That it can be repaired there is no doubt because it is a software problem and not hardware. I've seen in forums that if you can not enter the download mode, you can force hardware, you put a resistor in the USB cable, but in the end for a normal user is a bit complicated, my advice would carry it to the Service Center. And the price can be from free to relatively inexpensive because it does not have to replace any parts.
phone is back
they fixed the phone free of charge and the bonus is my phone was 8gb now is 16gb for some reason
thanks for the replies
whlzibos said:
they fixed the phone free of charge and the bonus is my phone was 8gb now is 16gb for some reason
Click to expand...
Click to collapse
Then they didn't bother fixing it and just sent you another handset...
[CONSPIRACYMODE] Or Samasung only made 16gb versions and crippled some to only 8gb... [/CONSPIRACYMODE]
Some people have all the luck. Glad for you whizibos your small mishap had fringe benefits.
Related
Hi everyone,
This morning I upgraded to froyo via Kies on my Bell i900m. It was running stock JH2 without any rooting or lagfix etc.
The upgrade process went smoothly however after booting into froyo i began to get force closures and then the phone froze (within ten mins of running froyo).
Then I did a battery pull to reboot and now i'm stuck in a boot loop.
The phone only goes to the "Galaxy S GT-i9000m" screen then reboots constantly. I can't get into recovery mode (phone reboots too quickly) but I can get into download mode.
Is my internal sd fried? any advice how i can try to do a factory reset ? Can i even do this if i can't get into recovery?
any help is greatly appreciated
Internal SD issues,
you can try one thing,
download Odin 1.7 and i9000UGJH2 then flash ONLY the PDA.
Once booted open the recovery and if you have errors mounting you have the internal sd problem..
Since it was an official froyo upgrade though I would just take it in.
Edit:
Btw, you didnt have a lagfix installed right?
brendonsled said:
Internal SD issues,
you can try one thing,
download Odin 1.7 and i9000UGJH2 then flash ONLY the PDA.
Once booted open the recovery and if you have errors mounting you have the internal sd problem..
Since it was an official froyo upgrade though I would just take it in.
Edit:
Btw, you didnt have a lagfix installed right?
Click to expand...
Click to collapse
No I didn't have lagfix, or root - it's purely stock. The only modification done was that I unlocked it (but i'm running it on Bell)
kaiser__sose said:
No I didn't have lagfix, or root - it's purely stock. The only modification done was that I unlocked it (but i'm running it on Bell)
Click to expand...
Click to collapse
its hooped.
take it back,
sorry for the bad news
BlackDino said:
its hooped.
take it back,
sorry for the bad news
Click to expand...
Click to collapse
sux.. but thanks for the help
argh i hv this problem too, hopefully they won't know i unlocked the phone lol...also no recepit ...but i heard they still honour warranty as long as they check the imei number n stuff
This is what happened.
I used for a few hours its fine and now I finally got time to sit down and do some settings. Then suddenly applications started to crash and in the notification bar I read something like internal sd couldn't be loaded or something.
Edit: i can get into recovery mode and download mode! any suggestions?
miniflight said:
argh i hv this problem too, hopefully they won't know i unlocked the phone lol...also no recepit ...but i heard they still honour warranty as long as they check the imei number n stuff
This is what happened.
I used for a few hours its fine and now I finally got time to sit down and do some settings. Then suddenly applications started to crash and in the notification bar I read something like internal sd couldn't be loaded or something.
Edit: i can get into recovery mode and download mode! any suggestions?
Click to expand...
Click to collapse
I took mine back to bell this evening. I have the bill but they didn't ask to see it they just took the phone and sent it in for repairs.
If you can get into recovery mode I would see if the internal SD is working. If it is you can flash with Odin and see if that fixes things. If the internal is fried then you have to send it in but no worries like i said they didn't ask me for the bill (but I was using a bell sim).
I was on Stunner ICS Rom and then decided to try out CM9 so i did the following
1.backed up everything using CWM Backup
2.Copied the main cwm rom and google apps zips onto internal zip card
3.Booted into recovery using CWN menu option.
4.Navigated to install zip from internal sd card and selected the zip
5.Then nothing. no progress bar,no movement etc.
6.Waited for about 10mins, still nothing.
7.Powered off the phone and removed battery.
8.PHONE WONT POWER ON AT ALL.
Anyone had a similar issue and is it resolvable?
Thanks.
I think not!, Sorry, mate - it looks like you've bricked your phone.
Haven't you read this in CyanogenMod 9 Discussion Thread:
- I STRONGLY RECOMMEND TO FLASH FROM A CF-ROOTED STOCK GINGERBREAD ROM, JUST TO AVOID YOU HARD BRICKS.
and
- DON'T flash FROM i9220 LEAKED REPACK!
all found here!!!
Well is wrong way because you miss return to gingerbread before flash cm9 first.
Overall,try to flash rooted gingerbread indownload mode with pc odin bro
Good luck
xovox said:
Overall,try to flash rooted gingerbread indownload mode with pc odin bro
Click to expand...
Click to collapse
No harm in trying, but I think it's too late for that now.
Motherboard replacement is in order, I fear....
Can you get into download mode? I had a similar problem and fixed it by getting into download mode, connecting to pc, then run Odin and load CF-Root-SGN_XX_SER_LA6-v5.0-CWM5.tar, this reloaded my CWM recovery and then wipe cache etc and install anything. But by using Odin you will be stuck with that yellow triangle
As you said it would not turn on try the following.
Remove the batteyr for about 1hr or so when plug it back in and try to go directly yo downalod mode.
If you can flash a GB Rom and you "should" be OK. If you still can't start it you most likely need to send it in to replace the motherboard.
if its still on warranty, tell them this happened because of kies update fail.
sometimes, its inevitable to lie...
kuriandungu said:
I was on Stunner ICS Rom and then decided to try out CM9 so i did the following
1.backed up everything using CWM Backup
2.Copied the main cwm rom and google apps zips onto internal zip card
3.Booted into recovery using CWN menu option.
4.Navigated to install zip from internal sd card and selected the zip
5.Then nothing. no progress bar,no movement etc.
6.Waited for about 10mins, still nothing.
7.Powered off the phone and removed battery.
8.PHONE WONT POWER ON AT ALL.
Anyone had a similar issue and is it resolvable?
Thanks.
Click to expand...
Click to collapse
try a usb jig... if it is able to force ur mobile into download mode use pc odin to flash a gb rom... otherwise the only alternative is motherboard replacement
Thank you guys for your Responses. i appreciate them.
I returned the phone to Samsung Repair office and they said it looked repairable. (fingers crossed). They'll get back to me in a couple of days.
[user_99] said:
I think not!, Sorry, mate - it looks like you've bricked your phone.
Haven't you read this in CyanogenMod 9 Discussion Thread:
- I STRONGLY RECOMMEND TO FLASH FROM A CF-ROOTED STOCK GINGERBREAD ROM, JUST TO AVOID YOU HARD BRICKS.
and
- DON'T flash FROM i9220 LEAKED REPACK!
all found here!!!
Click to expand...
Click to collapse
No i didnt read that! i got instructions from theandroidsoul.com page called cm9-galaxy-note Which doesnt talk about coming from a Gingerbread rom etc. I should have come straight to XDA and i'm paying the price!
Hope the samsung repair shop can restore it. One representative said they have quite a number of such cases but somehow they get the phone to work again. So i'm hoping mine will work out.
musashiro said:
if its still on warranty, tell them this happened because of kies update fail.
sometimes, its inevitable to lie...
Click to expand...
Click to collapse
i told them it failed during an update....didnt say which update (economy with truth
belveder69 said:
Can you get into download mode? I had a similar problem and fixed it by getting into download mode, connecting to pc, then run Odin and load CF-Root-SGN_XX_SER_LA6-v5.0-CWM5.tar, this reloaded my CWM recovery and then wipe cache etc and install anything. But by using Odin you will be stuck with that yellow triangle
Click to expand...
Click to collapse
Thanks for the reply. Already took it to Samsung.
Really Bricked note
Just got news from Samsung local repair office that its beyond repair. Hard to believe that the software is so deeply intwined with the hardware that a software process can kill the phone.
Will try get the usb jig and see if it will work.
Thanks to everyone who had a suggestion or comment.
I swear I did the same a few weeks ago and flashed a N7000 STOCK Rom PC Odin and I was ok.
Really Bricked note - had to get new motherboard
Guys...read this before attempting to flash ... I had to buy a new motherboard after trying to flash CM9 on Stunner Rom.
http://forum.xda-developers.com/showthread.php?t=1633943
Hi guys,
I'm in a problem with my GNote... I am (or was) running Android 4.0.4 stock from Samsung, then today completely out of the blue the phone froze and I had to reset, then it was stuck in the Samsung Galaxy Note logo screen. I tried removing the SIM and SD card, etc but nothing. Then I tried reinstalling the ROM via Odin but it got stuck in "Writing NAND...". Then I read in a forum that I could try a repartitioning with the PIT for my memory size (16 GB). I tried this but it got disconnected in the middle (the cable connector is a bit unstable) and now I can't get it to boot ANYTHING. The screen is completely black and Odin doesn't recognize the phone, can't get into recovery mode, etc.
Any idea? My tel company told me that it has a little marking that looks like the phone was hit and so they can't accept it for warranty tech service. I will try Samsung Service Center directly but before that, is there anything I can do???
Thanks!!
Chaostar said:
Hi guys,
I'm in a problem with my GNote... I am (or was) running Android 4.0.4 stock from Samsung, then today completely out of the blue the phone froze and I had to reset, then it was stuck in the Samsung Galaxy Note logo screen. I tried removing the SIM and SD card, etc but nothing. Then I tried reinstalling the ROM via Odin but it got stuck in "Writing NAND...". Then I read in a forum that I could try a repartitioning with the PIT for my memory size (16 GB). I tried this but it got disconnected in the middle (the cable connector is a bit unstable) and now I can't get it to boot ANYTHING. The screen is completely black and Odin doesn't recognize the phone, can't get into recovery mode, etc.
Any idea? My tel company told me that it has a little marking that looks like the phone was hit and so they can't accept it for warranty tech service. I will try Samsung Service Center directly but before that, is there anything I can do???
Thanks!!
Click to expand...
Click to collapse
Is it starting up? If note just remove ur battery for around 10 mnts, then insert that try pressing vol down + power + home for 20 seconds and then press vol +, just check if ur pc could detect the device and also if the battery is enough charged.
If this detects ur device, u have chances or else only jig is the option.
Hope 4 the best
Press THANKS if this helped u :fingers-crossed:
I don't think even jig is an option now... the phone screen is completely black, it doesn't even get into the logo screen... going to Samsung right now.
jig mite help you.. cuz even when the phone doesnt boot up .. the jig mite force it to download mode.. check with that.. if not then get it to the samsung service.. how did u reset... were u rooted? stuck on NAND write is not a good sign
Chaostar said:
I don't think even jig is an option now... the phone screen is completely black, it doesn't even get into the logo screen... going to Samsung right now.
Click to expand...
Click to collapse
Why not?
The Jig costs 2-3 US$ from Ebay, China...
Give it a try, its simple:
- remove battery
- put the Jig in
- wait a bit and put the battery back
- wait, pull battery out, pull Jig out
- connect the phone via USB to your PC, put battery back and start Odin
And if you are a lucky man you can flash a new firmware via Odin.
If you have an corrupt bootloader, Jig helps.
If there is a hardware problem you need a new maniboard.
How you described your Note there is possible only a corrupted bootloader ( Jig ) or a dead mainboard ( Samsung repair ).
Hmmm I'd say there is some serious problem. Originally (yesterday) my Note was working OK and then spontaneously (I didn't do anything or bump it or anything like that, I was just writing an email) it froze and so I used the reset combination (power+home buttons), then it entered into boot loop, it started and when it got to the Galaxy Note logo it rebooted, it did this 2 or 3 times and then it was stuck in Note logo. I took out the battery, put it back in, the same. I waited 10 minutes with the battery out, again the same results.
But I could get into recovery mode, so I tried re-flashing my ROM (LRQ Samsung stock from Germany, this was the only flash I did in my Note since last year when I bought it, I had 2.3.6 and then last month I updated to 4.0.4 via Kies official download and then using Odin I flashed the LRQ Samsung 4.0.4 stock because it has new features like the 3D gallery) but it got to "Writing NAND..." or something like that. I tried this several times and it was always the same.
So I read somewhere that I could try repartitioning the memory using Odin and the PIT file for my memory size (16GB), I tried this but just when I was in the process, the USB connector (which is a bit loose in my Note) disconnected for a second and reconnected and it was all. Phone dead. I'm guessing there's nothing there in the memory to boot from or to... so I'm taking it to Samsung.
Chaostar said:
But I could get into recovery mode, so I tried re-flashing my ROM (LRQ Samsung stock from Germany, this was the only flash I did in my Note since last year when I bought it, I had 2.3.6 and then last month I updated to 4.0.4 via Kies official download and then using Odin I flashed the LRQ Samsung 4.0.4 stock because it has new features like the 3D gallery) but it got to "Writing NAND..." or something like that. I tried this several times and it was always the same..
Click to expand...
Click to collapse
bro Chaostar
your Gnote is totally got a called ( brick ) same my gnote but it is revive via repartition.. with 2GB loss
first you do is make sure your battery is full charge and forced your Gnote into DOWNLOAD MODE.....
how to forced to download mode?
1 press home button + volume down then press power button,, if result is not lucky...... go to second way
2 use jig for download mode
(a) remove batt,,
(b) then attach the jig to usb port
(c) then put back the batt,,, then wait almost 60second
(d) after 60sec, remove jig then press volume up,..... one press only.... it shown black screen but the system status is download mode.
(e) open odin pc, connect your Gnote,,, see and wait.. if you see your gnote is detected,,,, your welcome you have a chance.. then flash kernel only ( safe_CM9_kernel.tar) then reboot to recovery then flash the JB:CM10:HYBRD] PARANOIDANDROID [2.20 or follow the repartition procedure,,
( f) what if not detected?.......... don't worry..:highfive: i have last option for you... this is revive your Gnote via (JTAG)..
GUDLUCK and see you..
Well I already left my Note in my cell company, it is within warranty period and I hope they can fix it. The only problem is that it has a slight marking that looks like a bump on the side and they said that this could void the warranty, but they will give me a budget if it has to be paid for, I hope they don't have to change the whole mainboard, and if they want to charge me I'll take it to Samsung directly as a last chance. After that, I guess it's jig.
What really gets to me is that this started as a sort of spontaneous error, I didn't do anything to the phone before the initial freezing and unability to boot. The problem is that then I tried the PIT stuff. Well, let's see what happens.
Thanks for your suggestions!!
Chaostar said:
After that, I guess it's jig.
Thanks for your suggestions!!
Click to expand...
Click to collapse
ABOUT JIG''... HERE THE INFO...http://droidangel.blogspot.com/2011/05/how-to-make-samsung-galaxy-s-download.html
about JTAG .. here the info,,http://www.youtube.com/watch?v=d0SX3iDuIZc&feature=youtube
So I, (like apparently many other 5830D users) was having the bug where it would randomly restart for no apparent reason.
i read that froyo did not have this issue, and figured id give it a shot. i downloaded the ZSKC2 2.2.1 files and loaded them into odin with cooper_v1.0.ops, connected my phone and hit start.
it said it installed everything just fine, but when my phone went to reboot, it didnt.
it flashed a black, blank screen for maybe a second and that was it.
so i tried to go back into download mode on it so i could reinstall the firmware it had before, and i couldnt get it to work.
it would turn on the screen, flash the "downloading..." text for a second, and then turn off the screen. it was weird, because the text was white, not the yellow it always seemed to be. odin recognized my phone for that second, but that was it. once the display turned off, the connection went away. i've tried other usb ports, but no luck
is there any way i can fix this? or is my ace bricked for good? i have no warranty with it because i bought it used.
ive read about a USB jig, will that help?
please, any help at all would mean a lot!
1) You should have taken the bill & the warranty card from the owner you bought this phone.
Coming to the point, it appears to me that there might be a problem with your battery, but I ain't sure about this. Try using a different battery with your phone. Also, are you sure to have used the odin & stock rom for S5830D & not S5830 ? Check these aspects first. If you've got them right, then there'll be either a multi-package or a single package filed stock rom for your device. You can google for the exact odin flashing, try again to boot into download mode again & flash. If your phone fails again to go into the download mode, use the search option here on xda to find out the issue with your phone or the best thing to do would be go to the service centre & tell them that donno what went wrong & this happened.
Sent from my GT-S5830 using xda premium
Venomous Viper 119 said:
1) You should have taken the bill & the warranty card from the owner you bought this phone.
Coming to the point, it appears to me that there might be a problem with your battery, but I ain't sure about this. Try using a different battery with your phone. Also, are you sure to have used the odin & stock rom for S5830D & not S5830 ? Check these aspects first. If you've got them right, then there'll be either a multi-package or a single package filed stock rom for your device. You can google for the exact odin flashing, try again to boot into download mode again & flash. If your phone fails again to go into the download mode, use the search option here on xda to find out the issue with your phone or the best thing to do would be go to the service centre & tell them that donno what went wrong & this happened.
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
okay, i tried the battery from my other phone and got it into download mode, i installed the stock rom and it is working again, but the reboot problem is still there!
is there any way to fix that? i have a feeling it might have something to do with the kernel, other roms still reboot and apparently froyo doesnt, the only thing common between all the gingerbread roms that i can think of is the kernel.
i have flashed S5830,T,L,B roms with no issues, but the reboot still occurs. cyanogen hasnt helped either, do you have any clues?
racer_25 said:
okay, i tried the battery from my other phone and got it into download mode, i installed the stock rom and it is working again, but the reboot problem is still there!
is there any way to fix that? i have a feeling it might have something to do with the kernel, other roms still reboot and apparently froyo doesnt, the only thing common between all the gingerbread roms that i can think of is the kernel.
i have flashed S5830,T,L,B roms with no issues, but the reboot still occurs. cyanogen hasnt helped either, do you have any clues?
Click to expand...
Click to collapse
After flashing via odin, if you face a bootloop, reboot into stock recovery & do a factory reset & reboot now. It should work.
Sent from my GT-S5830 using xda premium
Venomous Viper 119 said:
After flashing via odin, if you face a bootloop, reboot into stock recovery & do a factory reset & reboot now. It should work.
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
..but it is not tuck in a boot loop. its doing what the stock roms did; it'll boot into the rom fine, and you can use it, but once it goes to sleep the phone restarts itself.
rayman121985 said:
Thats a great idea...hopefully they won't go over $500 in price.
Click to expand...
Click to collapse
If you are having this issue with the froyo, try it out with GB. If the issue prevails, go to service centre. Sorry for repeating the same thing again & again but that's the best I could say of it...
Sent from my GT-S5830 using xda premium
Hi there! Now, firstly, ive always used Windows Phones but, would like to join Android and discover what it is really like to use... It really does look like fun to use
Anyway, last night i got my mums old Samsung Galaxy S1(G-I9000) and tried to root it and put CyanogenMod on it so i could get arid of the broken TouchWiz(I don't know what the new versions of it are like, but this one was broken and horrible to use) and get updated to Android 4+. Now, the root was successful and i am very happy with myself for doing that.... But here is where it all fell apart....
So, i jumped on their guide on their cyanogenmod wiki and it turns out that doing that first step(The "Installing a custom recovery on Galaxy S") was not needed because i already had ClockWork on my phone and that doing it would apparently break my phone.... I did not realise that till afterwards.
When i tried to reboot into recovery mode to install CM it got stuck on the boot screen. I think to myself maybe its stuffed and ill just reboot it again and see if it work... Nope. Now i try to reboot normally and leave it alone.... Nope. Turns out, all i can do is get into download mode. Now, from what ive found online, using Odin to reflash my phone with the stock ROM is how to fix my phone, problem is, Odin is not finding the phone and Hard Resetting the phone by holding down Lower Volume button and power is not working.... How can i fix this?
I think you can still recover it. However, the reason Odin might not recognize it it's probably because you haven't installed the Samsung USB drivers
If you install them and try to go into Download mode again you might be able to flash the stock ROM back onto your Samsung phone