Hello all,
I'll try to be brief, but descriptive.
Months ago I tested out a used S4A in sink... it got wet. I dried it out and it was working mostly fine. Changed the charging port/ribbon cable and worked fine except for the menu button was dead.
Rooted device with Towelroot and was getting ready to try and install custom ROM, why for some reason I deleted Towelroot app and restarted. Phone has since been stuck in Safe mode. I can install apps like safestrap, but can't get to them, being in safe mode.
I've tried flashing a custom recovery, and many factory resets after attempting "try this" and try that's" from forums. Nothing has worked.
I used to have an HTC that had a ROM mounted onto an SD card that I could run from RAM (at least I think thats how it worked), is that possible on this device? or is there any other solution to this?
Thanks in advance for any suggestions.
Solved
Apparently, I didn't clean it enough. I cleaned the contacts a couple times, but is seems that it was not enough. Unit is now operating normally. In addition, through testing everything, I noticed that the menu button on the board wasn't pressing forward towards the face button quite enough. I stuffed something in there to press it forward and now it is working perfectly!
Related
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...
Hello All,
I'm fairly certain there isn't another thread asking this question, if I overlooked it I apologize in advance. Now to the point, I have a dell streak 7 and I have been having some stability issues with it for about the last week. What was happening is I was running Android 2.2.2 and my system would crash randomly eventually it wouldn't start back up. I tried doing a factory restore several times this didn't work so I re-flashed to restore the original file system and I installed the T-mobile system by mistake. I played around with this for a little bit and every thing seemed fine. So I decided to upgrade to 3.2 honeycomb, I flashed the DS7 did all of the set up steps and started reading about rooting the device (I didn't start any of the steps). While it was sitting next to me in sleep mode I noticed it just randomly reset itself and started booting up. I looked around in it and nothing seemed to be changed, so I powered it off and powered it back on to see if it would freeze up and crash again. it didn't so I put it back in sleep mode and kept reading. then the side lights came on and it froze up. I was able to get it to boot by going into recovery mode and then selecting boot normally. So my question is, is this some sort of hardware issue or something that I am doing wrong? I don't think it's hardware but I could be mistaken. Also, has anyone else had an issue like this and if so is there a known fix? I am going to try re-flashing to the original file system again and replace the restore .img and see if this helps. Also, I'm not sure if my DS7 is the mobile version or wifi only version. I entered the service tag at DELL's website and it said I had the mobile version, however it didn't have the t-mobile start up animation before I flashed it the first time and in the sim card slot there is a black piece of plastic or card (IDK which) lodged in there and it wont come out. Any help or advice on this would be greatly appreciated .
Thanks in advance-Woulfenstien
OK I'm pretty sure i got it solved. what I did was I re-flashed everything. I re-flashed the boot.img, the system.img, and the recovery.img using fastboot and then i re-flashed whole system with nvflash. It's been a couple of hrs. and this has seemed to work so far. I upgraded back to 3.2 honeycomb and rooted the device with no problems so far. If any other issues arise I will post them here along with what i did to fix it. I would also like to thank everyone on this forum who has posted the tutorials, it was a huge help I wouldn't have been able to fix my DS7 with out all of your help.
Thanks again-Woulfenstien
Hey guys, hope you could help me with my problem.
So I've been trying to install many custom roms in my samsung to try it out, and then I decided to return to my stock rom, then I rooted it. After I rooted it, my power button/lock button started to malfunction, it won't lock my screen after the first press, then after pressing a couple of times, it reboots without any warning. Any solution? I don't think it is a hardware problem because when turning it on, it works fine. Also, it doesn't always happen, but it is really getting annoying when my phone starts to reboot again. I've found a similar problem here and tried the solution, but it didn't work. I also tried to format, return to my stock rom again, but no luck
up
I am running Infected's CM12.1 ROM on my Yuga, and it's been working great, but just yesterday, my phone restarted without warning and optimised all the apps (200 of them), right when it says "starting apps", it restarts again and did this until the battery drained out.
I cannot enter recovery at all. I have TWRP installed on the FOTA partition, but I cannot access that. When I'm holding the volume down key on the reboot, it just skips straight to the CM logo.
While it's optimising apps, I can see the phone in adb, but it's unauthorised, so I cannot run any commands to it.
I can reboot the phone into fastboot, but apart from reflashing the boot.img (which I already did) I don't know what else to try.
I think all the buttons are working, but I saw that the water pads are red underneath two of them. I think there may be water damage, but am not sure.
I'm out of ideas and would very much appreciated if anyone can help me bring my beloved phone back.
Lohot said:
I am running Infected's CM12.1 ROM on my Yuga, and it's been working great, but just yesterday, my phone restarted without warning and optimised all the apps (200 of them), right when it says "starting apps", it restarts again and did this until the battery drained out.
I cannot enter recovery at all. I have TWRP installed on the FOTA partition, but I cannot access that. When I'm holding the volume down key on the reboot, it just skips straight to the CM logo.
While it's optimising apps, I can see the phone in adb, but it's unauthorised, so I cannot run any commands to it.
I can reboot the phone into fastboot, but apart from reflashing the boot.img (which I already did) I don't know what else to try.
I think all the buttons are working, but I saw that the water pads are red underneath two of them. I think there may be water damage, but am not sure.
I'm out of ideas and would very much appreciated if anyone can help me bring my beloved phone back.
Click to expand...
Click to collapse
Have you tried flashing stock FTF ?
You would need FTF from general section and also flashtool which you can get from here. Make sure the FTF is device specific or your would end up bricking up your phone
http://www.flashtool.net/index.php
You can search xda for how to use it. If you still have questions, quote me and I would be glad to help
Hi,
Thanks for helping me out. I tried reflashing a few different ROMs using flashtool, including stock, but nothing helped.
In the end, I bit the bullet and gave it up for dead. The good news was, since the cause seemed to be water ingress, it was covered by my insurance, and so I was given a replacement!
Thanks again for your help.
Hnk1 said:
Have you tried flashing stock FTF ?
You would need FTF from general section and also flashtool which you can get from here. Make sure the FTF is device specific or your would end up bricking up your phone
Click to expand...
Click to collapse
Lohot said:
Hi,
Thanks for helping me out. I tried reflashing a few different ROMs using flashtool, including stock, but nothing helped.
In the end, I bit the bullet and gave it up for dead. The good news was, since the cause seemed to be water ingress, it was covered by my insurance, and so I was given a replacement!
Thanks again for your help.
Click to expand...
Click to collapse
There's nothing sweeter than using a phone for a long time and getting a brand new !
Enjoy mate. No trouble. Just quote me again in case you have any query for me.