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
Related
Hi,
I have lost the ability to use my internal and external storage memory. Is there anyone that can tell me how to fix this. I am at a loss.
Thanks
Zack Cadieux
I have the same problem after flashing JPH firmware. (I know how to flash FW, I've been flashing every FW as it was released)
It says that there is an I/O error in mmcblk0p1.
I think i'm screwed as well.
Not one person knows what is going on
Hi,
Im supprised that even the dev's know nothing about this issue. I have read almost every thread and nothing to show how to respolve this issue. Is there anyone???
I had the same problem. I have a Bell Vibrant which I flashed to JPH using the Kies method, rooted, then One Click Lag Fix. Things worked for about a day then I lost my storage. Luckily I did the samsung 3 button fix first.
I downloaded the Tmobile Stock Rom, and used the following instructions to flash.
http://forum.xda-developers.com/showthread.php?t=734475
It booted up to the Tmobile Rom, and everything worked. I then used Odin to flash back to JPH.. rooted.. and now am contemplating the Lag Fix.
Not sure if it was related to the problem but I had my phone connected to my computer transferring files before all hell broke loose. I may have yanked the USB without unmounting... Just a thought.
Good Luck..
Dawgplg said:
I had the same problem. I have a Bell Vibrant which I flashed to JPH using the Kies method, rooted, then One Click Lag Fix. Things worked for about a day then I lost my storage. Luckily I did the samsung 3 button fix first.
I downloaded the Tmobile Stock Rom, and used the following instructions to flash.
It booted up to the Tmobile Rom, and everything worked. I then used Odin to flash back to JPH.. rooted.. and now am contemplating the Lag Fix.
Not sure if it was related to the problem but I had my phone connected to my computer transferring files before all hell broke loose. I may have yanked the USB without unmounting... Just a thought.
Good Luck..
Click to expand...
Click to collapse
My situation is about the same. I did the update and applied the root and lag fix. Phone worked fine for a day or so and then it just locked up and couldn't detect the sd cards anymore. I rebooted and it was stuck on the S for over 30 minutes...I flashed HJ2 and when it rebooted all that happens is I get a gray blinking battery if it's attached via USB and if on battery it boots up to the I9000 initial screen and shuts down. Lucky for me the shop will do a swap when they restock in about a week. Back to the HTC for now.
LordSoth said:
My situation is about the same. I did the update and applied the root and lag fix. Phone worked fine for a day or so and then it just locked up and couldn't detect the sd cards anymore. I rebooted and it was stuck on the S for over 30 minutes...I flashed HJ2 and when it rebooted all that happens is I get a gray blinking battery if it's attached via USB and if on battery it boots up to the I9000 initial screen and shuts down. Lucky for me the shop will do a swap when they restock in about a week. Back to the HTC for now.
Click to expand...
Click to collapse
Dont recall if I did any of the Recovery options, but I remember the big Grey Battery... You could even try flashing back to JPH through Odin... It may wake it up. But good to hear they will replace it, at least you have something to fall back on.
Dawgplg said:
Dont recall if I did any of the Recovery options, but I remember the big Grey Battery... You could even try flashing back to JPH through Odin... It may wake it up. But good to hear they will replace it, at least you have something to fall back on.
Click to expand...
Click to collapse
There was another thread I read about this exact same issue happening and the guys had to return the phones in the end. Yea I was lucky I was under the 30 days limit. By the time I get a new one hopefully a proper Froyo build will be out.
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...
I was attempting to flash the ICS4 ROM. I had formatted /system and was done with installing the from from zip. Before I could do anything else, the phone just stopped being responsive. I pulled and restored the battery but the phone will not boot up. What to do now, short of going to my VZW store?
When you say it doesnt boot.. what exactly do you mean? Does anything come up on the screen?
nothing comes when you press the power button, screen remains blank.
ronaldheld said:
nothing comes when you press the power button, screen remains blank.
Click to expand...
Click to collapse
Did you try booting up into recovery and then going to fastboot and reinstalling the stock fxz file to see if that fixed it?
Sure the battery didn't die also?
The phone does not boot into recovery. Pressing the power button does nothing at all, as far as I can see.
I found out that the phone is literally fried. Whether the ICS4 ROM contributed is unknown.
You are most likely covered under manufacturer warranty - seems like a hardware failure. Never known of a ROM flash to fry a phone's board.
They also most likely won't know you even tried to flash a custom ROM.
That part is very good to know.
I will have restart again with rooting, and proceed with flashing Eclipse 2.2.
Is the place you live in very statically charged? When you touch metal do you get shocked alot?
If you touched the battery ports it could have discharged into the phones board and killed it.
Let us know what they do for you.
ronaldheld said:
That part is very good to know.
I will have restart again with rooting, and proceed with flashing Eclipse 2.2.
Click to expand...
Click to collapse
Compared to everything else we do here at XDA, the process to get rooted and flash a ROM is very basic. Getting the phone back up and running is the more difficult part.
What I can say to try is attempt to use a different battery. I had a problem once where both of my batteries functioned properly because I was able to test them in other phones. But when I placed that specific battery into my phone, it wouldn't boot up. I ended up using a different battery and was then able to boot into AP Fastboot and fxz to fix it. Then my "dysfunctional" battery worked properly again.
I got a Sprint HTC One last week, rooted it, s-offed it and flashed several ROMs on it.
My problem is that in every ROM I've tested, the phone reboots after a couple of minutes.
Here are the ROMs I've tried so far:
- CLEAN ROM SPR 2.5
- CM-10.1-20130714-NIGHTLY-m7spr
- MIUI_m7wls_signed_07042013
- Slim-m7spr-4.2.2.build.7-OFFICIAL
- Sprint_HTC_One_1.29.651.10_Stock_Deodexed
- Sprint_HTC_One_1.29.651.10_Stock_Odexed_05.17.13
- Stock_w_Goodies_One_1.06
- viperROM_One_v1.1.0
I'm using TWRP 2.5, advanced wiping: dalvik, cache, data, system before flashing the ROM.
Does anyone have sugestions?
Hi bro...
There's another thread talking about that:
http://forum.xda-developers.com/showthread.php?t=2344478
alexyomar said:
Hi bro...
There's another thread talking about that:
http://forum.xda-developers.com/showthread.php?t=2344478
Click to expand...
Click to collapse
I guess that's a slightly different problem then mine.
My phone is S-OFF already and I've wiped and flashed almost every single ROM out there and the phone reboots (doesn't shutdown) every 2 minutes...
After I read some other similar issues, I'm guessing I'll have to use a RUU tool to fix the problem. The other problem is that I only have Mac and Linux...
I've read a post advising to copy the ROM file to the root of the phone's internal storage in order to do a proper flash.
Since I was always flashing the roms directly from an external usb thumb drive, I thougt it was a good idea.
I copied Android Revolution 2.5 to the phone's memory, wiped everything and flashed it. Installation whas OK so I rebooted. When selecting the wi-fi network on the initial setup I received a message saying "avoiding poor signal network" even thoug my router was about 10ft from me. After finishing the initial setup I rebooted the phone and then it got stuck hard.
Even when pressing the power button for over 20 second it didn't shut down. Now I'm waiting for the battery to die so I can see what happens on the next boot.
Again, if someone can help me on this situation, I'll appreciate it...
1alemao said:
I've read a post advising to copy the ROM file to the root of the phone's internal storage in order to do a proper flash.
Since I was always flashing the roms directly from an external usb thumb drive, I thougt it was a good idea.
I copied Android Revolution 2.5 to the phone's memory, wiped everything and flashed it. Installation whas OK so I rebooted. When selecting the wi-fi network on the initial setup I received a message saying "avoiding poor signal network" even thoug my router was about 10ft from me. After finishing the initial setup I rebooted the phone and then it got stuck hard.
Even when pressing the power button for over 20 second it didn't shut down. Now I'm waiting for the battery to die so I can see what happens on the next boot.
Again, if someone can help me on this situation, I'll appreciate it...
Click to expand...
Click to collapse
press the buttons while holding phone under a bright light and it will reboot, if that rom was a 4.2.2 rom from the intl. forum you're going to have to ruu it.
Aldo101t said:
press the buttons while holding phone under a bright light and it will reboot, if that rom was a 4.2.2 rom from the intl. forum you're going to have to ruu it.
Click to expand...
Click to collapse
This!
Sent from my HTCONE using xda app-developers app
I've only used Sprint ROMs but still got those freaking reboots. Only by using RUU (provided by viperboy) I managed to solve the reboot issue.
Now I'm waiting for a software SIM Unlock solution, since I'm in Brazil an cannot unlock it OTA.
I'll post an update here as soon as I have a solution...
Hello,
I'd like to preface this to say I've searched through this and other sites but have not found quite the same problem. I also apologise for the small wall of text. I just want to post everything that seems relevant.
Several weeks ago I unlocked my phone and flashed the latest stable Cyanogenmod. This has all gone fine. I decided today I wanted to try something else and settled on TeamAsylum's 4.4 rom.
Downloaded a whole bunch of stuff and was a little confused as the flashing process seemed a bit different and I didn't fully understand it. I booted into Clockwork Recovery and inadvertently flashed the raw kernel from here, which I downloaded in my searches earlier thinking I needed it. I rebooted the recovery but now I get nothing from the phone. No lights, no display, no vibrations.
I have tried a reset (Power+Volume UP). I have tried using SUS and Flashtool but both get to the same point and stop (hole Volume DOWN and plug USB in). Nothing happens after this. The only thing telling me the phone is alive is when I plug it in, Windows makes the detected sound. If it's plugged in when I hold power+Volume UP it repeats the detection sound as if the phone is trying to boot over and over.
I realise I have ****ed up by flashing the kernal of a different phone. I'm hoping someone can help me or guide me in the right direction.
Thank you.
Nightstaar said:
Hello,
I'd like to preface this to say I've searched through this and other sites but have not found quite the same problem. I also apologise for the small wall of text. I just want to post everything that seems relevant.
Several weeks ago I unlocked my phone and flashed the latest stable Cyanogenmod. This has all gone fine. I decided today I wanted to try something else and settled on TeamAsylum's 4.4 rom.
Downloaded a whole bunch of stuff and was a little confused as the flashing process seemed a bit different and I didn't fully understand it. I booted into Clockwork Recovery and inadvertently flashed the raw kernel from here, which I downloaded in my searches earlier thinking I needed it. I rebooted the recovery but now I get nothing from the phone. No lights, no display, no vibrations.
I have tried a reset (Power+Volume UP). I have tried using SUS and Flashtool but both get to the same point and stop (hole Volume DOWN and plug USB in). Nothing happens after this. The only thing telling me the phone is alive is when I plug it in, Windows makes the detected sound. If it's plugged in when I hold power+Volume UP it repeats the detection sound as if the phone is trying to boot over and over.
I realise I have ****ed up by flashing the kernal of a different phone. I'm hoping someone can help me or guide me in the right direction.
Thank you.
Click to expand...
Click to collapse
Try this:
Open flashtool
Hold volume up and insert usb cable( you will enter fastboot )
then select fastboot and flash a good kernel for CM.
let me know it this works
RaZieLRaH said:
Try this:
Open flashtool
Hold volume up and insert usb cable( you will enter fastboot )
then select fastboot and flash a good kernel for CM.
let me know it this works
Click to expand...
Click to collapse
Hi,
I tried what you said. When holding Volume UP and inserting cable, literally nothing happens. I don't even get a sound from Windows detecting it.
Whilst trying this several times though I did notice if I press Power the phone seems to stay on for 30-60 seconds. If I press Power and plug it in, Windows will make a sound. It will then make another sound after 30-60 seconds as if the device has been removed or turned off.
no clue then sorry can't help
Nightstaar said:
Hi,
I tried what you said. When holding Volume UP and inserting cable, literally nothing happens. I don't even get a sound from Windows detecting it.
Whilst trying this several times though I did notice if I press Power the phone seems to stay on for 30-60 seconds. If I press Power and plug it in, Windows will make a sound. It will then make another sound after 30-60 seconds as if the device has been removed or turned off.
Click to expand...
Click to collapse
Just for giggles, check your device manager to see if you have an unknown device... (you may need to install the fastboot drivers...) I've bootlooped my phone a couple of times while putzing with my phone... And can normally get back into flash mode and fast boot mode...
Sent from my Xperia ZL using Tapatalk
scifan said:
Just for giggles, check your device manager to see if you have an unknown device... (you may need to install the fastboot drivers...) I've bootlooped my phone a couple of times while putzing with my phone... And can normally get back into flash mode and fast boot mode...
Sent from my Xperia ZL using Tapatalk
Click to expand...
Click to collapse
I did check this. There are no unknown devices. I did install the Xperia Z/fastbot/flashboot drivers from the flashtool folder. When it does make the detection sound Device Manager does 'reset' as if something has connected as well, although I can't find the device.
Most other similar issues have an LED or some type of display and generally are responsive to flashmode.
Note1 boot partition is the XZ's SBL3 (bootloader) partition. So you have effectively flashed a Note1 boot.img to your bootloader. Phone will never boot again once bootloader is hosed. Sorry about your loss
Sent from my C6603 using xda app-developers app
Shoey is right, your Z is toast now, sorry; the only solution here is to replace the MoBo, and that costs a pretty penny.
But why did you download stuff from the n7000 forum? Didn't everything said there sound unfamiliar and therefore suspicious enough for you
to double-check which forum you were in exactly?
I thought as much. I dun goof'd
Thanks for your help.
@chasmodo: Well I started in the N7000 thread and downloaded all the stuff and copied it to my SD card. I then realised I was in the wrong forum and switched to the relevant thread. All the stuff for the N7000 and the Z were both on my SD card, so it was just a stupid mistake really. Everything on both forums sounded a little unfamiliar. As I mentioned I was a bit cofused on the TWRP section. I should done more research before proceeding.
Do you think there is any use for the phone now? Do you know of anywhere/anyone I can donate it to for spare parts or something?
Nightstaar said:
Do you think there is any use for the phone now? Do you know of anywhere/anyone I can donate it to for spare parts or something?
Click to expand...
Click to collapse
As I said, you can get it fixed by replacing the MoBo, but I don't know how much that costs in your country. Google a little, contact someone, get the info and then decide what to do.
chasmodo said:
As I said, you can get it fixed by replacing the MoBo, but I don't know how much that costs in your country. Google a little, contact someone, get the info and then decide what to do.
Click to expand...
Click to collapse
I did have a look around and had trouble finding a main board in particular. I contacted Sony as well and they said it was quite expensive to replace.
I contacted my carrier and it appears getting a new phone is a lot cheaper than anything I've looked into so far.
Thanks for your help.
The next time you decide to flash your phone , make sure your in the correct forum. Lesson learned
Sent from my C6603 using XDA Premium 4 mobile app