Database Develop

[Q] Bricked Milestone, stuck at Motorola logo

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

[Q] Stuck at the X, move on to a new phone?

I recently bought this Nexus off eBay and it worked fine.
Owner said it had problems with the SD card, but it seemed to be working, for they said it wouldnt read, when it does.
Anyway, it had cyanogen mod 6.1.1 on it, and I hate the setup...so i changed roms. That was a success, but when i flashed a sense rom thru clockwork(most updated) it said:
E:Error in /sdcard/N1Sensation_v0.4.zip
(Status 0)
Installation aborted.
Now, when i flash any roms, whether it says it installed correctly, it doesnt change anything. Now it's stuck at the 4 color x with the unlock icon. Any advice is good advice!
In my hboot, it says:
*** UNLOCKED ***
NEXUSONE PVT SHIP S-ON
HBOOT-0.35.0017
MICROP-0b15
TOUCH PANAL-SYNT0103
RADIO-5.00.00.04
Oct 12 2010, 14:33:16
HBOOT
Etc. Etc. Etc.
Thanks for any help!
Edit: I fixed the issue with why it failed, was my fault, didnt partition the card...but i was flashing a stock rom and it said complete and when i rebooted it stayed at the X and then powered off. Since then has never turned on. I don't know what to do. Nothing will turn it back on. I have a universal charger that charges the battery and it said the battery is full. I need help!

Ok lets see here try this plug in the charger then pull the battery place it back in wait a few seconds and repeat until you see the splash screen (the static X). This could get the phone to at least boot.
But just to check did you flash a radio in all that stuff??

Dude Random21 said:
Ok lets see here try this plug in the charger then pull the battery place it back in wait a few seconds and repeat until you see the splash screen (the static X). This could get the phone to at least boot.
But just to check did you flash a radio in all that stuff??
Click to expand...
Click to collapse
That did not work. I work at a cellphone repair store, but im yet to open it up. But i flashed a sensation rom...
http://forum.xda-developers.com/showthread.php?t=1083035
After then i got stuck on the X
Then i used... well i cant find the link, but it's PureGoogleMod.
From what I saw, there was no radio or kernal being flashed. I just know i flashed a rom, it said completed, then went to the X, rebooted, but never turned on. And ive tried other batteries.

matistight said:
That did not work. I work at a cellphone repair store, but im yet to open it up. But i flashed a sensation rom...
http://forum.xda-developers.com/showthread.php?t=1083035
After then i got stuck on the X
Then i used... well i cant find the link, but it's PureGoogleMod.
From what I saw, there was no radio or kernal being flashed. I just know i flashed a rom, it said completed, then went to the X, rebooted, but never turned on. And ive tried other batteries.
Click to expand...
Click to collapse
Try flashing CM7. Also...before you do...you may want to search for a format.zip from a member named temasek. It'll wipe your phone...clean. Real clean. Then flash CM7. try that.
also....those sense roms sometimes take at least 5 minutes to boot. Sometimes it'll stay on the X screen for 5 minutes or it'll stay on the bootanimation screen for 5 minutes. FYI.

SiNJiN76 said:
Try flashing CM7.
those sense roms sometimes take at least 5 minutes to boot. Sometimes it'll stay on the X screen for 5 minutes or it'll stay on the bootanimation screen for 5 minutes. FYI.
Click to expand...
Click to collapse
I can't flash anything. Phone wont react to anything anymore. Hoping one of my family members can fix it. But if I get it on I will try that.
I am pretty sure i waited long enough, but who knows. I didn't partition my card, which may have been the problem. And also it was S-On....which i thought was odd when it had a custom firmware.

Unlock bootloader. Flash recovery. Boot into recovery. Wipe everything. Flash rom.

Why do you guys keep suggesting software stuff when it's probably a hardware problem he can't get the phone to boot up so he can't do any of that.
Although there is one thing I want you to try before your family take a crack at it to take it apart and what not, it's a long shot but it's your last chance if it's software. Hold down trackball and press power keep holding trackball for another 5-10 seconds (better to long then to short) then connect it to the computer via USB you could see a popup notification saying that it's looking for driver software if you do then it's software and we need to reflash everything and might need to unlock the bootloader. Now if you don't see a popup notification I would still go check in the device manager and check for an unidentified device probably in other (it should be extracted so that you can see it).
If this doesn't work then sorry but I think it's a brick

Because in order to find out if its truly a hardware problem you need to try every software fix first.
Op mentioned nothing of trying fastboot as well. Software fix is free hw is not. That is why we suggest software fixes.
Sent from my Nexus S using XDA App

Let me remind you guys, THE PHONE WONT TURN ON AT ALL REGARDLESS OF WHAT I DO. I can post a YouTube video to show everything. It'd be very random for it to be hardware because it just turned off and will not turn back on. If there is any software like an RUU out there, that would help, if not, ill have to buy a bottom piece and warranty it out. But I'd feel bad because that isn't the right thing to do.
I don't expect you guys to fix it and I and very thankful of your help! But the phone won't turn on at all. So telling me to flash roms doesn't work. Imagine it as flashing a rom with the battery out of your phone. I am wondering if there's an adb way or something to get it to turn on and restore to stock?
With all that said, any help is amazing help and I am very grateful that this isn't a post I have to bump! Thank you so much, when I go on the PC, ill thank the helpful posts
Sent from my (finally) permanent root Sensation 4G

Then it is a brick if it won't turn on at all. The entire getting stuck at the x thing confused me to think it was powering on.

You have me confused sir, I'm not quite sure what good it is your looking for a RUU for. If the phone truly won't turn on/go past the X screen and you have it on a charger with no LED notification, then the phone is bricked. When you said you flashed a Sensation rom, I truly hope you just meant a Sense rom. If you can still get to the bootloader screen then you are not bricked and should retry everything from scratch.

Thread Closed
xsnipuhx said:
When you said you flashed a Sensation rom, I truly hope you just meant a Sense rom.
Click to expand...
Click to collapse
Sensation based, but it was a Sense rom
Confirmed it is bricked.
Sold on eBay for $100
Bought for $77
Semi-Winning.
Thread Closed

[Q] Galaxy S stuck in boot-loop

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...

[Q] WiFi not turning on, not working.

After the forced AT&T software update, my WiFi will not turn on. I will go into WiFi settings, press the toggle button, and it will grey out and get stuck on "Turning on WiFi". I have tried wiping both caches, and I have replaced the bcmdcm.ko under system\lib\modules with bcm4330.ko, which was the one from the stock ROM. Nothing has worked and this problem persists. I am rooted and my bootloader is unlocked. Is there anything short of doing a full factory reset that can fix this problem?

Please post in the appropriate section.
Thread moved to Q&A
Sent from my Nocturnalized One XL using Forum Runner

Bigluc said:
After the forced AT&T software update, my WiFi will not turn on. I will go into WiFi settings, press the toggle button, and it will grey out and get stuck on "Turning on WiFi". I have tried wiping both caches, and I have replaced the bcmdcm.ko under system\lib\modules with bcm4330.ko, which was the one from the stock ROM. Nothing has worked and this problem persists. I am rooted and my bootloader is unlocked. Is there anything short of doing a full factory reset that can fix this problem?
Click to expand...
Click to collapse
Have you tried flashing the boot.img via fastboot? That seems to help a lot of people.

ronnie498 said:
Have you tried flashing the boot.img via fastboot? That seems to help a lot of people.
Click to expand...
Click to collapse
Ok I've googled around alot and looked on this forum but I can't find a boot.img anywhere that isn't modified. Can you point me to the stock boot.img?

My mom has a Vivid and her phone has been doing this ever since the update was pushed down by AT&T. Since she lives 1000 miles from me, I didn't root her phone, and leaving it stock, the only thing that ended up working was a factory reset. The other thing that was happening after the update was every boot would go through the "Optimizing application 1 of x..." message like it does after the update. I get the impression that whenever she performed the mandatory AT&T update, something didn't go correctly, which is why her Wi-Fi was permanently stuck in this "Turning on Wi-Fi" state. It seems to be working perfectly now, and we no longer see the "Optimizing..." message either when the phone reboots. Now I won't have to do remote tech support when she flies back home next week

tonemand said:
My mom has a Vivid and her phone has been doing this ever since the update was pushed down by AT&T. Since she lives 1000 miles from me, I didn't root her phone, and leaving it stock, the only thing that ended up working was a factory reset. The other thing that was happening after the update was every boot would go through the "Optimizing application 1 of x..." message like it does after the update. I get the impression that whenever she performed the mandatory AT&T update, something didn't go correctly, which is why her Wi-Fi was permanently stuck in this "Turning on Wi-Fi" state. It seems to be working perfectly now, and we no longer see the "Optimizing..." message either when the phone reboots. Now I won't have to do remote tech support when she flies back home next week
Click to expand...
Click to collapse
I think this is my next step. I tried flashing boot.img, but that didn't work. Does anyone have any other solutions short of this?

Bigluc said:
Ok I've googled around alot and looked on this forum but I can't find a boot.img anywhere that isn't modified. Can you point me to the stock boot.img?
Click to expand...
Click to collapse
There's a link to one in the thread for Kozmik Kernel.

Bigluc said:
After the forced AT&T software update, my WiFi will not turn on. I will go into WiFi settings, press the toggle button, and it will grey out and get stuck on "Turning on WiFi". I have tried wiping both caches, and I have replaced the bcmdcm.ko under system\lib\modules with bcm4330.ko, which was the one from the stock ROM. Nothing has worked and this problem persists. I am rooted and my bootloader is unlocked. Is there anything short of doing a full factory reset that can fix this problem?
Click to expand...
Click to collapse
it could just be a problem with the kernels, i was experiencing this even before the update.
Are you on a cusotm rom and/or custom kernel?

wifi will not turn on
y Rogers HTC Raider is unlocked and S-ON. I flashed MIUI 2.8.17 and now I can't turn on wifi, google play won't connect and I cannot boot into recovery mode, it just stays at he HTC screen. How do I fix this?

AshleyPem28 said:
y Rogers HTC Raider is unlocked and S-ON. I flashed MIUI 2.8.17 and now I can't turn on wifi, google play won't connect and I cannot boot into recovery mode, it just stays at he HTC screen. How do I fix this?
Click to expand...
Click to collapse
Did you install the kernel? If you're s-on you need to fastboot flash the kernel image.
Sent from my HTC Raider using xda premium

[Q] White HTC Screen and Triangle! During Recovery

I apologize in advance if this has been discussed in the past, but my searching here hasn't helped so I gotta ask for help.
Having a problem with me wife's HTC Vivid. It's bone stock. Nothing has been messed with other than whatever updates may have been installed automatically over the air. She wouldn't let me touch it to root it, mod it, nothing.....
Anyway. Problem happened Saturday night. Phone shut down due to dead battery. Put it on charger overnight. Tried to boot it up Sunday morning and it stops at the white HTC screen. Period. Just sits there. Forever.
I did some reading, learned how to hold power and vol down buttons to get to HBOOT. Tried navigating to recovery. It goes to white HTC screen, then to a black screen with a green circle arrow icon, then to a red triangle with an exclamation point.
I downloaded drivers and the HTC RUU and was going to try fastboot usb, but when it said all data will be lost I stopped.
My wife has tons of pics and stuff on her phone (that she has failed to back up ) and really doesn't want to loose them.
Before I wipe the phone and try to reinstall the stock rom do any of you have any suggestions on a way to get it back up and running and recover her pics and stuff?
Or are we screwed? :crying:

Ginther said:
I apologize in advance if this has been discussed in the past, but my searching here hasn't helped so I gotta ask for help.
Having a problem with me wife's HTC Vivid. It's bone stock. Nothing has been messed with other than whatever updates may have been installed automatically over the air. She wouldn't let me touch it to root it, mod it, nothing.....
Anyway. Problem happened Saturday night. Phone shut down due to dead battery. Put it on charger overnight. Tried to boot it up Sunday morning and it stops at the white HTC screen. Period. Just sits there. Forever.
I did some reading, learned how to hold power and vol down buttons to get to HBOOT. Tried navigating to recovery. It goes to white HTC screen, then to a black screen with a green circle arrow icon, then to a red triangle with an exclamation point.
I downloaded drivers and the HTC RUU and was going to try fastboot usb, but when it said all data will be lost I stopped.
My wife has tons of pics and stuff on her phone (that she has failed to back up ) and really doesn't want to loose them.
Before I wipe the phone and try to reinstall the stock rom do any of you have any suggestions on a way to get it back up and running and recover her pics and stuff?
Or are we screwed? :crying:
Click to expand...
Click to collapse
You get the red triangle/exclamation point because you dont have a custom recovery installed if Im correct. Using the all in one here is the most user friendly way of installing -
http://forum.xda-developers.com/showthread.php?t=1498003
Install twrp and you should be able to recover your pics/vids by selecting "mount/mount sdcard" in the twrp ui with your phone plugged in to your pc. Then opening the storage located under computer. Navigating to the appropriate folder & cut/pastting to a folder on your pc.
I dont know how technology savvy you are but it sounds like flashing the stock kernel will repair your phone hanging on the htc logo. This is the stock ICS kernel - http://d-h.st/rHX
You can flash it through the all in one. Or follow up here -
http://forum.xda-developers.com/showthread.php?t=1416836
Hope this helps. Good luck!
Sent from my HTC Raider X710e using xda premium

yosoywilson78 said:
You get the red triangle/exclamation point because you dont have a custom recovery installed if Im correct. Using the all in one here is the most user friendly way of installing -
http://forum.xda-developers.com/showthread.php?t=1498003
Install twrp and you should be able to recover your pics/vids by selecting "mount/mount sdcard" in the twrp ui with your phone plugged in to your pc. Then opening the storage located under computer. Navigating to the appropriate folder & cut/pastting to a folder on your pc.
I dont know how technology savvy you are but it sounds like flashing the stock kernel will repair your phone hanging on the htc logo. This is the stock ICS kernel - http://d-h.st/rHX
You can flash it through the all in one. Or follow up here -
http://forum.xda-developers.com/showthread.php?t=1416836
Hope this helps. Good luck!
Sent from my HTC Raider X710e using xda premium
Click to expand...
Click to collapse
Thanks for the help. I was able to get the bootloder unlocked with the all-in-one but when I tried to install the kernel it kept failing. I tried several different things over and over again but no luck.
I finally got frustrated and tried the HTC RUU from their website to see what would happen. I had to relock the bootloader before it would work though. It finally ran successfully and the phone is back up and running now.
Only bad news is that I wasn't able to recover any of her files.
Now she understands the importance of backing up files and getting stuff OFF the phone to another form of long term storage. :good:
Thanks again for the help.

Ginther said:
Thanks for the help. I was able to get the bootloder unlocked with the all-in-one but when I tried to install the kernel it kept failing. I tried several different things over and over again but no luck.
I finally got frustrated and tried the HTC RUU from their website to see what would happen. I had to relock the bootloader before it would work though. It finally ran successfully and the phone is back up and running now.
Only bad news is that I wasn't able to recover any of her files.
Now she understands the importance of backing up files and getting stuff OFF the phone to another form of long term storage. :good:
Thanks again for the help.
Click to expand...
Click to collapse
You probably could have recovered your media. Just by mounting the internal memory like I said in my original post. You really should invest in an SD card that way no matter what happens your stuff is accessible. You can use up to 32GB. People also say 64GB SDXC cards work too. But glad its up and running again.
HTC VIVID ICS 4.0.4 SENSE 4.1

yosoywilson78 said:
You probably could have recovered your media. Just by mounting the internal memory like I said in my original post. You really should invest in an SD card that way no matter what happens your stuff is accessible. You can use up to 32GB. People also say 64GB SDXC cards work too. But glad its up and running again.
HTC VIVID ICS 4.0.4 SENSE 4.1
Click to expand...
Click to collapse
I got into CWM recovery and tried mounting the sdcard but kept getting "error mounting sdcard"
No mater what I did I could not get it to mount and become visible on my pc. I could see the disk drive(s) for the phone, but they were shaded and when I'd try to access them it would say insert disk into drive. When using the all-in-one it would try to push the kernel to the phone, but it got errors too. I tried putting the kernel on a micro sdcard and installing it from cwm with no luck. Couldn't get that to show/mount/work either.
I've done modding to my Samsung phones and build my own pc's so I'm not too technologically challenged.... but, Something was just wrong with this phone and it didn't want to cooperate.
And/or I didn't have the time and patience to keep jacking with it.

Switch to twrp
Sent from my Vivid 4G using Tapatalk 2