Hi guys,
I have a few problems with my Motorola Milestone.
1. I can't get in to recovery. I only get an black screen (backlight is on)
2. I don't get any video in the bootloader. but RSD lite does recognizes it, and is able to flash it. When it's flashing I do get video only stating that there is software update busy.
3. When I boot up my phone I don’t get, a Motorola logo, but just a black screen (back light on) followed by the Android logo after a few minutes.
4. If I try to wake up the phone, the screen remains black, but the hardware keys to light up, I have to press the lock button multiple times to activate the screen. - Note when the screen remains black, it is responsive and I can unlock the phone, but it still remains black. And sometimes the colors are inverted, but when i make a screen of it with Screen Grabber (shoot me) it's in normal colors.
That kind of sums it up.
I have tried a few things to fix it. I have:
1. Cleared caches, and personal data
2. Flashed a different SBF en recovery
And since I can’t get in to recovery, I had to get Root via Z4 Root method and it works fine.
Afterwards I downloaden Rom-manger, and installed the ClockWork recovery, and tried to boot in Recovery via clockwork, but that didn’t work either. I also can’t get in to Recovery via a cold boot
I think the problems started when I was using CyanogenMod 7 RC4. It worked just fine, but after I installed it I couldn't get in to recovery.
Can I try something else to fix it? or should I flash it back to original state and RMA it?
Edit some additional information:
Frimware: 2.2.1
Frimware configuration: GAS_EMEA_UCAMS1FRYOQWRTEU_P005
Baseband version: 3GSMPU91A_U_91.09.00I
Baseband configuratuin version:UCALHLSMR2EMEAB1B806E.0R
Kernel Versuin: 2.6.32.9-ge635aa4 [email protected]#1
Build Number: SHOLS_U2_05.06.0
And is it possible to restore the orginal boot animation, without recovery?
TL.DR: Motorola Milestone --> CyanogenMod 7 RC4 --> no recovery & no video @ bootloader, plus additinal video problems --> back to orginal --> same problems.
BUMP: is there anyone with a possible soulution?
ClockWork recovery doesn't work on milestone.
So CM7 does boot up?
zeppelinrox said:
ClockWork recovery doesn't work on milestone.
So CM7 does boot up?
Click to expand...
Click to collapse
CM7 doesn't anymore as I removed it, and flashed a different SBF and recovery.
CyanogenMod 7 RC4 worked fine but I had a few video problems, and I could get in to recovery.
I will flash a different recovery tonight and try it out.
Only use androidiani open recovery
Sent from my Milestone using Tapatalk
zeppelinrox said:
Only use androidiani open recovery
Sent from my Milestone using Tapatalk
Click to expand...
Click to collapse
Flashed a different .sbf and placed the androidiani open recovery files on the Sd card root, but i still can't get in to recovery. I won't even get the /!\ screen. The phone does turn on, but will only get a black screen.
Which sbf?
Sent from my Milestone using Tapatalk
UK SHOLS_U2_02.36.0
I think I bricked it, I'm going to try to restore it or buy a new phone... >.<
BloemBlaster said:
UK SHOLS_U2_02.36.0
I think I bricked it, I'm going to try to restore it or buy a new phone... >.<
Click to expand...
Click to collapse
I don't think you bricked it... but damaged it in some way.
Could also be some hardware related stuff in the end.
Anyway try to wipe everything, that could be wiped.
Start into bootloader and try to install G.O.T. 2.2.1 using RSD again.
This one got the vulnerable recovery already integrated.
Then try to use the specific G.O.T. OpenRecovery on your sdcard to check system integrity.
Please try to take care of every single step and check out what happens....
If your hardware is doing fine, i'm pretty sure that you will get a working phone again.
P.S.: How about your bootloader version?
Good luck,
scholbert
scholbert said:
I don't think you bricked it... but damaged it in some way.
Could also be some hardware related stuff in the end.
Anyway try to wipe everything, that could be wiped.
Start into bootloader and try to install G.O.T. 2.2.1 using RSD again.
This one got the vulnerable recovery already integrated.
Then try to use the specific G.O.T. OpenRecovery on your sdcard to check system integrity.
Please try to take care of every single step and check out what happens....
If your hardware is doing fine, i'm pretty sure that you will get a working phone again.
P.S.: How about your bootloader version?
Good luck,
scholbert
Click to expand...
Click to collapse
I think my boatloader is 90.47 I'm not sure as I won't get any video in the boatloader.
I flashed the G.O.T 2.2.1but I can't get in to recovery, there is still no video only a blackscreen.
Is it posible the may have deleted the files for the logo?
BloemBlaster said:
I think my boatloader is 90.47 I'm not sure as I won't get any video in the boatloader.
I flashed the G.O.T 2.2.1but I can't get in to recovery, there is still no video only a blackscreen.
Is it posible the may have deleted the files for the logo?
Click to expand...
Click to collapse
You can try upgrading your bootloader to 90.78 from here.
Then try flashing GOT 2.2.1, then see if AOR boots up.
sileshn said:
You can try upgrading your bootloader to 90.78 from here.
Then try flashing GOT 2.2.1, then see if AOR boots up.
Click to expand...
Click to collapse
I flashed 90.78, and then reflashed GOT 2.2.1, but is still can't get into te recovery. I getting the same result, no motorola logo and a black screen with no /!\ logo
If your phone is recognised in adb, then you can use the link below to get into AOR directly. Just make sure you have AOR extracted to your sdcard.
http://forum.xda-developers.com/showthread.php?t=625950
Check the commands in the last post and enter them in order.
I was just looking at QtADB for somebody else's problem but it looks like you can use QtADB to boot recovery if the phone is recognized.
http://qtadb.wordpress.com/features/
Hi guys,
sorry for the late reply, but I'm also moving at the moment.
I have tired numerous things.
If I flash the 2.2.1 Firmware SHOLS_U2_05.26, I can get to the recovery selection screen, with the /!\ screen.
But if apply update.zip I will get an error message, stating "EOCD marker occurs after start of EOCD E:signature verification failed", something like that, I don't know the specific message out of my head
And if I flash a vurnable recovery only sbf, with the SHOLS_U2_05.26 I can't get the recovery screen, only a black screen.
zeppelinrox said:
I was just looking at QtADB for somebody else's problem but it looks like you can use QtADB to boot recovery if the phone is recognized.
http://qtadb.wordpress.com/features/
Click to expand...
Click to collapse
I will try thiss when I get home.
sileshn said:
If your phone is recognised in adb, then you can use the link below to get into AOR directly. Just make sure you have AOR extracted to your sdcard.
http://forum.xda-developers.com/showthread.php?t=625950
Check the commands in the last post and enter them in order.
Click to expand...
Click to collapse
I will try this if zepplelinrox method fails becaus I don't have any experince with adb. But the phone is recognised.
...........strange....
BloemBlaster said:
If I flash the 2.2.1 Firmware SHOLS_U2_05.26, I can get to the recovery selection screen, with the /!\ screen.
But if apply update.zip I will get an error message, stating "EOCD marker occurs after start of EOCD E:signature verification failed", something like that, I don't know the specific message out of my head
Click to expand...
Click to collapse
This is standard error, if vulnerable recovery is not installed and you try to start OpenRecovery.
BloemBlaster said:
And if I flash a vurnable recovery only sbf, with the SHOLS_U2_05.26 I can't get the recovery screen, only a black screen.
Click to expand...
Click to collapse
This is strange behaviour...
My last guess is, that something might be wrong with your vulnerable recovery sbf file (file corruption ???). There should have been some errors during flash...
Anyway, you might grab it here and try again:
http://gitorious.org/droid/openrecovery/blobs/master/zips/SHOLS/vulnerable_recovery.sbf
Good luck!
scholbert
sileshn said:
If your phone is recognised in adb, then you can use the link below to get into AOR directly. Just make sure you have AOR extracted to your sdcard.
http://forum.xda-developers.com/showthread.php?t=625950
Check the commands in the last post and enter them in order.
Click to expand...
Click to collapse
Still trying this, no luck yet. ADB isn't my strongest point
zeppelinrox said:
I was just looking at QtADB for somebody else's problem but it looks like you can use QtADB to boot recovery if the phone is recognized.
http://qtadb.wordpress.com/features/
Click to expand...
Click to collapse
The same goes for you, no luck yet. QtADB, work and it recognise my phone, but i can't any (re)boot commands.
scholbert said:
This is standard error, if vulnerable recovery is not installed and you try to start OpenRecovery.
This is strange behaviour...
My last guess is, that something might be wrong with your vulnerable recovery sbf file (file corruption ???). There should have been some errors during flash...
Anyway, you might grab it here and try again:
http://gitorious.org/droid/openrecovery/blobs/master/zips/SHOLS/vulnerable_recovery.sbf
Good luck!
scholbert
Click to expand...
Click to collapse
I actually have no idea how to download the sbf, form the site you have provided.
nevermind, I found it out . but now if my phone to connect to windows it doesn't recognizes it :S
BloemBlaster said:
but now if my phone to connect to windows it doesn't recognizes it :S
Click to expand...
Click to collapse
Before or after flashing the vulnerable recovery again?
Confusing...
scholbert
scholbert said:
Before or after flashing the vulnerable recovery again?
Confusing...
scholbert
Click to expand...
Click to collapse
Sorry for being confusing, it was after flashing vulnerable recovery, but my I'm flashing with a different system now and it working just fine.
If I try the .sbf you provided RSD gives a error "Failed flashing process. failed flashing process (0x17100);phone connected"
BloemBlaster said:
Sorry for being confusing, it was after flashing vulnerable recovery, but my I'm flashing with a different system now and it working just fine.
Click to expand...
Click to collapse
No problem...
BloemBlaster said:
If I try the .sbf you provided RSD gives a error "Failed flashing process. failed flashing process (0x17100);phone connected"
Click to expand...
Click to collapse
O.K. seems that something went wrong during download grab it here:
http://forum.xda-developers.com/showpost.php?p=13039348&postcount=17
BTW the link points to the OpenRecovery developers git rep... so this file is absolutely save.
Cheers,
scholbert
Ok, so I've flashed two different roms now: Serindipity VII and Mosiac IV. After following steps:
1. flash to stock via ODIN
2. Root phone applying root.zip--->update.zip
3. install clockwork using same method
====Right here something happens which I don't understand as well. Once I reboot to recovery again, after installing CWM, the native recovery module (android recovery) is still there. I have to press install from update again to goto clockwork.
4. install mosaic or seridipity using CWM
After install, the ROM works fine. But I can no longer reboot to recovery using the power button (adb reboot recovery didnt work either). When I startup the phone it shows ATT World Phone screen and the bunch of random colors lines and then the serindipity or mosaic start screen.
I realize this is some sort of bootloader issue, but isnt that what CWM is? Thanks for any help of pointing me in the right direction
axel4401 said:
Ok, so I've flashed two different roms now: Serindipity VII and Mosiac IV. After following steps:
1. flash to stock via ODIN
2. Root phone applying root.zip--->update.zip
3. install clockwork using same method
====Right here something happens which I don't understand as well. Once I reboot to recovery again, after installing CWM, the native recovery module (android recovery) is still there. I have to press install from update again to goto clockwork.
4. install mosaic or seridipity using CWM
After install, the ROM works fine. But I can no longer reboot to recovery using the power button (adb reboot recovery didnt work either). When I startup the phone it shows ATT World Phone screen and the bunch of random colors lines and then the serindipity or mosaic start screen.
I realize this is some sort of bootloader issue, but isnt that what CWM is? Thanks for any help of pointing me in the right direction
Click to expand...
Click to collapse
You have missed a complete step of flashing GB bootloaders, till u do that u will see those weird screens
yeah... thanks. didnt realize how silly I was being
Hi Guys,
I am facing similar kind of issue in my phone. I tried to flash cwm-6.0.1.9 recovery using Samsung Galaxy Note II toolkit. Whenever i try to boot in recovery mode i come across random color lines and complete blackout afterwards. Later i need to power on it manually. But yes i can operate the phone..
Help !!
hunk2008 said:
Hi Guys,
I am facing similar kind of issue in my phone. I tried to flash cwm-6.0.1.9 recovery using Samsung Galaxy Note II toolkit. Whenever i try to boot in recovery mode i come across random color lines and complete blackout afterwards. Later i need to power on it manually. But yes i can operate the phone..
Help !!
Click to expand...
Click to collapse
Well first off, don't flash anything that isn't made for you phone.
Now if you wanna get to flashing and such, you have lots of reading to do, starting with this: http://forum.xda-developers.com/showthread.php?t=1350266
Plz help i tried to remove yellow triangle from boot screen
i think it went sum thing wrong....d screen turn black and cant get it right....else boot sound runs wen i re boot my device....
plz help me devs....need assistance...
More information about the situation please...
How you managed to ACHIEVE this..
Can you go to Recovery /download mode?
no i cant able to....
i cant able c anything behind
You need come up with more words Sir! Help me isnt enough.
Where you using JIG method to remove triangle or TriangleAway app (from Playstore)?
Ok I think you flashed s2 bootloader to remove triangle and counter.So it is absolutely normal for the screen to go blank.But your devices isn't dead.Now flash a rom which contains the boot loader.Maybe LPF will suite you.Here is the link.
Now since you dont see anything on the screen,do this to enter download mode:
1.remove your battery
2.insert it after 5 secs.
3.Hold vol down+home+power button for 10 secs
4.count 10 and then press vol up again.
5.Now connect your phone to pc and odin will detect it and use the guide I link above to flash the rom.
And yeah you wont see anything in the screen during this process.
my phone (galaxy note) after root and when i go wipe data then my phone suddenly appear the yellow triangle and just hang there.i cant even go recovery mode and on my phone.can i use this method also?
weiverpool said:
.can i use this method also?
Click to expand...
Click to collapse
Didn’t you read the part about posting more info? How did you root? Did you root from GB or ICS, what else did you do? ROM and Kernal?
And of course, are you using the international GT N7000 Note??? Note the model.
Sent from my GT-N7000 using Xparent ICS Tapatalk 2
weiverpool said:
my phone (galaxy note) after root and when i go wipe data then my phone suddenly appear the yellow triangle and just hang there.i cant even go recovery mode and on my phone.can i use this method also?
Click to expand...
Click to collapse
no u can download apk link from below link :
http://forum.xda-developers.com/showthread.php?t=1494114
and follow the steps from youtube video link below:
http://www.youtube.com/watch?v=Aa-t-8ypcYs&feature=g-user-u...
Hi i have a samsung galaxy s gt i9000t and i was doing some changes to the device via odin and everything was fine until i try to flash via odin a clockworkmod image and now when i power up my device i get a black screen with a little phone two white dots a yellow triangle two white dots and a computer all of this is a little image on the center of the screen. Can you guys help me with this?? and can you please let me know if i brick my phone or not, i hope not cause this is my girlfriends phone :S i hope you guys can help me!!
daworship said:
Hi i have a samsung galaxy s gt i9000t and i was doing some changes to the device via odin and everything was fine until i try to flash via odin a clockworkmod image and now when i power up my device i get a black screen with a little phone two white dots a yellow triangle two white dots and a computer all of this is a little image on the center of the screen. Can you guys help me with this?? and can you please let me know if i brick my phone or not, i hope not cause this is my girlfriends phone :S i hope you guys can help me!!
Click to expand...
Click to collapse
Does the phone still have an accessible download mode???? Vol - / HOME /power? I am pretty sure a USB Jig will work on this problem if you cant access it via the 3 button combo.
I am one of the unlucky ones with no download mode, hopefully you aren't
Yup exactly what the guy above me said, also take the battery out for quite some time, but it back in, and check if you can access download mode.
daworship said:
flash via odin a clockworkmod image and now when i
Click to expand...
Click to collapse
You are still in download mode , so connect to odin and flash the correct bootloader , rom combination or use a rescue kit My Android Collections
Hi guys, I come to you as I'm truly desperate about the actual state of my phone.
Earlier today, I decided to go back to a stock rom. When I tried to use Odin, I realized that my phone wasn't recognized by my PC hile in download mode. To avoid this problem, I used Mobile Odin and successfully flashed a stock rom (S5830BUKT2_S5830SFRKT1_S5830XWKT8_HOME.tar). Then I wanted to re-install a custom recovery mode, and I went with version 6.0.4.6 (6.0.4.6-cooper_fix.zip was the actual file). After I did that I couldn't boot in recovery mode anymore : the screen goes black, the logo reappears, then the screen goes white, then gets stuck at a blue screen. At this point I have to remove the battery and boot normally. So I was like 'nevermind I'll flash again the stock rom with Mobile Odin'. But the app requires for me to root the phone. Which I can't do without using the recovery mode. And I still can't use Odin (download mode not recognized). (I don't know why, but I don't have to press Volume Up to actually enter download mode, so I guess it's some kind of custom download mode).
So here I am, asking you to help me because every solution I can think of seems unapplicable to my case.
Thanks in advance !
skrabz said:
Hi guys, I come to you as I'm truly desperate about the actual state of my phone.
Earlier today, I decided to go back to a stock rom. When I tried to use Odin, I realized that my phone wasn't recognized by my PC hile in download mode. To avoid this problem, I used Mobile Odin and successfully flashed a stock rom (S5830BUKT2_S5830SFRKT1_S5830XWKT8_HOME.tar). Then I wanted to re-install a custom recovery mode, and I went with version 6.0.4.6 (6.0.4.6-cooper_fix.zip was the actual file). After I did that I couldn't boot in recovery mode anymore : the screen goes black, the logo reappears, then the screen goes white, then gets stuck at a blue screen. At this point I have to remove the battery and boot normally. So I was like 'nevermind I'll flash again the stock rom with Mobile Odin'. But the app requires for me to root the phone. Which I can't do without using the recovery mode. And I still can't use Odin (download mode not recognized). (I don't know why, but I don't have to press Volume Up to actually enter download mode, so I guess it's some kind of custom download mode).
So here I am, asking you to help me because every solution I can think of seems unapplicable to my case.
Thanks in advance !
Click to expand...
Click to collapse
cwm6.0.4.6 had blue screen issue. use cwm 6.0.4.7. In windows 8 I faced difficulty flashing stock. make sure you are using windows 7. and download mode is sometime pain in @ss. sometimes it simply restarts phone. Be patient.