So I did a big mistake,I tried too many custom roms and I think I messed up my phone. My current custom rom is Resurrection Remix.
Few days ago my phone was having a weird problem,my recovery was gone,and the phone's screen turned black after 2 mins of booting up.However this issue solved automatically,I reinstalled recovery. ( I should have reflashed the custom rom,but I didn't:crying The settings was still missing,but I ignored it as there was not much use of settings.
Fast forward to today's morning , the phone was at 7% I don't know what I thought but I decided to give it a reboot.AND now my phone is not starting(It's not bootloop ,the phone is not even starting up).The battery is not charging up(It's very difficult to get new battery for Nokia X2,that would be the last thing I'd want to do,that or either buying a new phone)
.There is no light,no vibration whenever I connect my charger.I got my charging socket changed but nothing is working.I think it's a software issue.
Please is there anything I can do to recover my phone? Anything?:crying:
make sure your battery is ok and charged.
then try to flash the phone using pc with "nokia x2 tools" and a custom ROM and recovery
Related
Hello
I had some trouble with a bricked SGS for about 3 weeks ago but got it on the run again with some flashing help.
Now i have this strange problem. If i turn it off or if it just goes black out, which it has begun to do after i flashed it, then it can't turn on, it just show the sun looking loading icon and then a empty battery icon and then turns off.
I can't load recovery mode with the combo, but i can make the download mode combo work.
But if i connect the phone with the charger/usb i recognize it and show that it charging up. Now it boot and shows the Galaxy I9000 model no. image.
Had tried flashing newer versions From XXJPO -> XXJPY -> XWJS3 and both with and without pre-partition and it still occur.
Now the question: Does any of you experienced people know this problem and can it be fixed somehow ?
Thank you in advance
First i would liik to charge phone for 24 hours and also check with another battery .
jje
JJEgan said:
First i would liik to charge phone for 24 hours and also check with another battery .
jje
Click to expand...
Click to collapse
The battery don't seem to be defected. Once the phone is booted with a cable connected, it goes without problems. It just will not boot without a charging signal.
Bump - Still actual
Try using Block 2 Odin method here to go back first to Eclair and if that works test phone then upgrade to Froyo .
jje
JJEgan said:
Try using Block 2 Odin method here to go back first to Eclair and if that works test phone then upgrade to Froyo .
jje
Click to expand...
Click to collapse
That happened to me a while back and I couldn't find a fix for it. Ended up doing the above and it resolved it.
Z3icon said:
Hello
I had some trouble with a bricked SGS for about 3 weeks ago but got it on the run again with some flashing help.
Now i have this strange problem. If i turn it off or if it just goes black out, which it has begun to do after i flashed it, then it can't turn on, it just show the sun looking loading icon and then a empty battery icon and then turns off.
I can't load recovery mode with the combo, but i can make the download mode combo work.
But if i connect the phone with the charger/usb i recognize it and show that it charging up. Now it boot and shows the Galaxy I9000 model no. image.
Had tried flashing newer versions From XXJPO -> XXJPY -> XWJS3 and both with and without pre-partition and it still occur.
Now the question: Does any of you experienced people know this problem and can it be fixed somehow ?
Thank you in advance
Click to expand...
Click to collapse
i agree wiv the suggetions frnds given.galaxy is hard to brick.i did all sort of unusual things an even uptodate lol.don worri m8 jus flash to older stock and hard reset.check the connectivity pins,to b clean even the battri pins.somtimes its best u format ur eternal xd on pc an format.and giving another hard rest makes things better.i had once formated my int sd on pc and the phone had emptied,then i flashed and things worked fine.personally sticking to stock rom is better if u dont wan troubles,cause every custom rom has som drawback an needs a lil knownledge to tweak it up.check kies if ur on it,i recomend download the recovery driver in it.hope u get some help.cheeeerzzzz
Same here...
Hello everyone,
I too have the same issue as stated in the first post.
I even had issue sometimes that when boot up.
The USB notification icon wouldnt turn off even if i wasn't connected.
Some threads suggested that I clean the USB port, which i did and nothing changed, even if it looked a little bit dirty in there (Hard to say since it is really small).
Now the USB port looks just as new but same issue: I cant power on the unit witout having it connected with a power cord.
Also, when offline in download mode, Odin detect the unit and I can flash my device (Which I did yesterday by flashing UGJH2 re-partition and UGJL2 not re-partition) but when boot up, I can't make it to sync up with the computer. No sync possible (Also now I'm not rooted anymore).
The unit is under warranty but since it is unlocked with a tool that needed rooting to lock back, abviously I would need to be rooted again but to do it, I need to be able to sync it with my PC (No cant do here).
I have some engineer at work that offered me to check it out for me, they think it is related with the USB port, but I'm worried about the warranty seal. I found how to disasemble it but does anybody knows where it could be located on the I9000M from bell (Vibrant)? Does it have one?
Anybody have any better suggestion or a second opinion, please?
Its my 3rd Galaxy S from Bell and Samsung is now the last company I would think when buying a new mobile.
EDIT: Did the Block 2 Method and now it doesnt even want to boot at all (Did the JPY_JPY_JPY.tar part), now it shows the loading sign even faster and the battery doesnt even show it self at all.
Hello again people!
Got my friend engineers to open the phone and they didnt find anything that would cause my issue (Also no warranty label...).
Does anybody knows how to root a Galaxy S with Froyo without a PC?
I want to return my phone to Bell Canada under warranty but my phone is unlocked and I want to lock it back before sending it back and I need to be rooted to do so...
Thanks for your help!
I got the same problem here. Could someone tell me more on this. What is this Block 2 ODIN method?
this problem can be caused by water or sweat that got inside the case of your sgs.
the biggest hole in the case is micro-usb port) i think condensation accumulated there and locked some contacts.
try to disassemble the phone and carefully clean and dry it.
this helped me.
Hi,
I managed to brick my Milestone, terminally I'm afraid, but the symptoms are different than what I see around the forum so they might interest someone else.
So, I first backed up everything with GOT Nandroid and Titanium Backup then modded CyanogenMod 7 RC4 0.08-11.04.05 (Android 2.3.3) successfully, except that the SIM was locked and would not unlock, although it works in another phone. This was a bug supposedly fixed in version 6 of Cyanogen...
Browsing the forums, the only thing that made a bit of sense was that maybe the GSM frequency was set to the wrong value. There is a Nandroid mod (but not GOT) that allows you to change that so I entered GOT Nandroid again. Since it had no such option, I Rebooted. Then, the fun begun.
The phone got stuck on the Motorola logo and no button, not even Power, worked anymore. After waiting for many minutes with no progress, I took out the battery - that made a change , the phone shut down. I then put it back - the phone immediatelly, no, instantly, cause there's no delay as when you were powering it up, lights up with the same Motorola logo. Tried several times, always the same behavior.
I left it booting (but also connected to the charger) for a whole night, no change.
The phone is not seen by the PC when connected to USB. It won't reboot, normally or to recovery. Buttons won't work at all. Yeah, tried with or without the SIM and the sdcard, no change. Tried to start without battery, just the charger, doesn't work.
Useless to say, I am getting bored of that Motorola logo
I suspect that the bootloader in the internal memory got corrupted. Can this be flashed even if the device is not seen by the PC (I mean by the RDSLite installed on it)?
Cheers
When the charger is connected to the phone try at the same timeull out and pull in the battery while holding the buttons who will get you in the OR
Yup, it worked. So first I got the battery with a question mark. Then I put in the battery and I got a battery at 60%. Since I was holding Power+Camera, it continued to the Recovery mode and now I have a working Milestone with Cyanogen mod!!
Thank you a lot, Mikicishte.
I still have to see about the initial locked SIM problem... but that will be mostly fun.
florinadrian said:
I still have to see about the initial locked SIM problem... but that will be mostly fun.
Click to expand...
Click to collapse
Have you tried to factory reset the Milestone, to see if after that the SIM is accessible again ?
http://forum.cyanogenmod.com/topic/14099-sim-card-not-detected-after-factory-reset/
You could try also to install a logger application catlog for example (https://market.android.com/details?id=com.nolanlawson.logcat&feature=search_result ) to see in the logs if you can find out more details to help you with the investigations...
I did the factory reset as part of installing the mod.
Even if the post quoted reports the wipe as the source of the problem and not as a solution, I just wiped again with no good result.
Will try catlog.
florinadrian said:
I did the factory reset as part of installing the mod.
Even if the post quoted reports the wipe as the source of the problem and not as a solution, I just wiped again with no good result.
Will try catlog.
Click to expand...
Click to collapse
or maybe you could try to use an unlock tool to see what error is reporting
https://market.android.com/details?id=com.droidgram.bladeunlock&feature=search_result
Hi guys,
Gone through about 100 threads these last couple of days, but nothing helps, so have to start a new one.
What happened was that the other day my phone started ringing.
The screen however was black, so I could neither see who was calling nor answer the call.
I let it ring out, then I held the power button so it would shutdown.
Tried to restart it, and that's when the fun started.
The phone got stuck in a boot-loop, only showing the Galaxy S logo (not getting to the animated one).
Left it in this loop for several hours, since I've had problems recently with the phone needing to do this cycle 5-10 times before booting up.
This time it wouldn't boot, however.
I've tried putting the phone in a bag of rice for 18 hours, in case of any moisture inside, not helping.
Then I tried recovery-mode, formatting the whole thing, but I got the following error:
"E:format_volume: rfs format failed on /dev/block/mmcblk0p2"
Found this thread to try to fix the format error.
Got into download mode, but Odin does not recognize the phone, and I started believing all hope for fixing it without sending it in was gone.
I've also tried applying a couple of update.zip's from the SD-card, just to have tried it, but every package got Signature verifcation-error.
Anyway, when I headed to bed last night I left the phone in the boot-loop, and to my surprice, 8 hours later it had booted into first-time configuration.
YES!!!
Configured the phone with language etc., then all of a sudden the animated Galaxy S logo appeared...
And it appeared again, and again, and again for about 15 min., until I unplugged the battery.
And now I'm back at square one, stuck in the boot-loop (not getting to the animated logo)...
I have the latest versjon of KIES, not that it probably matters.
Does anyone have an idea of what the problem might be?
What rom were you using? stock or custom? Maybe it has something to do with lagfix if it was activated... im guesing, im not dev just normal user... Maybe try to reinstal usb drivers.
Just use odin 1.3 reflash official rom , everything would be OK.
Not sure about the ROM, bought the phone used... But pretty sure it's stock..
Since Odin didn't recognize the phone, reflashing it with official ROM would be hard...
However, as for the Odin problem, that was caused by a faulty USB-cable...
Used another one, and Odin worked like a charm.
The phone won't start after running through the steps in the thread I mentioned before, but I will try to reflash it with offical ROM now and see how that works.
mortenlm said:
Not sure about the ROM, bought the phone used... But pretty sure it's stock..
Since Odin didn't recognize the phone, reflashing it with official ROM would be hard...
However, as for the Odin problem, that was caused by a faulty USB-cable...
Used another one, and Odin worked like a charm.
The phone won't start after running through the steps in the thread I mentioned before, but I will try to reflash it with offical ROM now and see how that works.
Click to expand...
Click to collapse
Not sure about used phone, But if I bought the phone used, I would reflash rom first. Because I do not even know what they done before , reflash offical rom would be fix some problem.
porkapple said:
Not sure about used phone, But if I bought the phone used, I would reflash rom first. Because I do not even know what they done before , reflash offical rom would be fix some problem.
Click to expand...
Click to collapse
Well, I would have if I knew... But stupid me thought that a phone was a phone.
How wrong was I?
Anyway, a little update here (the problem is kind of solved now):
Flashed the phone with 2.3.3 Gingerbread I found on dkszone, after running the steps in the previous mentioned thread.
And the phone started like a charm.
But after a few hours of configuring etc, I managed to insert the SD-card again, and all hell broke loose again...
Come to think about it, thats what I did yesterday too, so I've come to the conclusion that the SD-card is the main problem...
However, now the phone is slow... REAL slow... Kind of like my 1.5 year old HTC Touch Diamond 2 with WP6.5...
It takes up to 2 seconds to open menu items, keyboard etc.
Is there any way to fix that?
Or should I flash it with another ROM?
You mean the external sdcard? Maybe try to format it...
OK, so this is what I've now figured out:
The phone is damaged...
It seems that the internal SD has gone AWAL, and internal storage has somehow created itself on the external SD-card, thus the phone crashed when I switched cards...
When trying to format the USB-storage, I receive error: SD-card has been removed
So I guess I have to ship the phone off to Samsung ASAP...
Hey guys, I just got a htc one m7 at a good price because of its problem with charging. there is still no fix for the no charging problem on the htc One m7?
On the stock rom i needed to reboot , go in safe mode, reboot again and then it was charging untill i got a phone call and it stoped ..
Then I have installed a costum rom and every time I want to charge it i need to reboot my phone and if i close the screen or recieve a phone call it cancels the charging and i need to reboot again..to charge it..and charging is very very slow eaven though it is on AC mode , i am currently running Slim rom 4.4.4 ( first time i tried withouth installing a costum ketnel, still no fix ) now I have installed a costum kernel and still the same thing..please guys help me!
STILL NO FIX/HELP?? PLEASE GUYS IT IS DRIVING ME CRAZY!!!!
alexandru.j91 said:
STILL NO FIX/HELP?? PLEASE GUYS IT IS DRIVING ME CRAZY!!!!
Click to expand...
Click to collapse
You have tried with both stock and custom roms with the same results. It is a hardware issue most likely a loose connection. Send it to a repair center.
If it were a hardware issue why it chsrges after reboot only?
I'm using mi3 with Euphoria-OS 0509 version. My phone will suddenly shutdown itself even the battery is full.
I tried re-flash this ROM, but no help.
It happens every time when I use the phone in no time. But It won't happen when charging.
Maybe there's a problem on your phone's battery. Try to bring it on a service center.
error01671 said:
I'm using mi3 with Euphoria-OS 0509 version. My phone will suddenly shutdown itself even the battery is full.
I tried re-flash this ROM, but no help.
It happens every time when I use the phone in no time. But It won't happen when charging.
Click to expand...
Click to collapse
What do you mean by "suddenly shutdown itself"?
Do you see 1) the closing down routine? Or 2) does the phone simply not respond to pressing the power button?
If it's 2), plenty of ROMs exhibit the "screen OFF death", where the phone is actually still active but you can't get the screen to light up. try flashing another ROM. Paranoid Android is the most stable ROM for me.
If it's 1), still try flashing another ROM, and it it is still closing down, it's a hardware issue (hopefully battery), so service centre time.
paul c said:
What do you mean by "suddenly shutdown itself"?
Do you see 1) the closing down routine? Or 2) does the phone simply not respond to pressing the power button?
If it's 2), plenty of ROMs exhibit the "screen OFF death", where the phone is actually still active but you can't get the screen to light up. try flashing another ROM. Paranoid Android is the most stable ROM for me.
If it's 1), still try flashing another ROM, and it it is still closing down, it's a hardware issue (hopefully battery), so service centre time.
Click to expand...
Click to collapse
In my case, my phone's screen will suddenly frozen while I'm using, and turn off itself. I need to hard reboot the phone. I used flashed this rom few months ago and change to PAC rom, no such problem until I flash this rom again, all roms were clean flash and the battery was calibrated. So I think it might be the hardware problem.
error01671 said:
In my case, my phone's screen will suddenly frozen while I'm using, and turn off itself. I need to hard reboot the phone. I used flashed this rom few months ago and change to PAC rom, no such problem until I flash this rom again, all roms were clean flash and the battery was calibrated. So I think it might be the hardware problem.
Click to expand...
Click to collapse
Well, if the phone was OK with a different ROM, that implies your current ROM is the problem - try another one.
I recall having had the same behaviour in the past, when I was trying a lot of ROMs in quick succession - so I don't know which one(s) it was.
All the same, it doesn't sound like hardware/battery. Make a Nandroid backup in recovery, then flash eg PAC ROM or Paranoid Android - wait a day before adding all your apps etc - and see if you get that issue again.
paul c said:
Well, if the phone was OK with a different ROM, that implies your current ROM is the problem - try another one.
I recall having had the same behaviour in the past, when I was trying a lot of ROMs in quick succession - so I don't know which one(s) it was.
All the same, it doesn't sound like hardware/battery. Make a Nandroid backup in recovery, then flash eg PAC ROM or Paranoid Android - wait a day before adding all your apps etc - and see if you get that issue again.
Click to expand...
Click to collapse
OK, I got some conclusions, and it might be a hardware problem.
First, I replaced the battery with same ROM, it still got SOD.
Then I flash Omni, PAC, Euphoria-OS, all got SOD like before.
So I return to MIUI, no SOD, but I got random reboots and sometimes Wi-Fi will disconnect itself even in its range.
Now I'm using Ivan's AOSP, still got random reboots and Wi-Fi problem.
And now I need this phone to work because I don't have a backup, waiting for new Nexus!!