Related
Ok I'm kinda a newbie...I've searched the forums and can't find my solution.
So I installed CM 7 on my nexus one from Rom manager. Everything is ok...so I decide to put google add ons ( froyo). This is what happens now... I get the Cyan logo animation , then the green google sign up logo then the phone reloops to the cyan logo and then the google sign in logo...I cant access nothing on my phone.
I boot into recovery ( power +trackball) , go to recovery option click on power and then I see the X (phone vibrates ) then I get a black screen...and nothing happens.
I did do 2 working rom recoveries from clockwork...I just cannot access them to recover my old working images....Can someone help or did I brick a new phone...
Thanks
just like basketball.......... brick
Maybe try to push a new recovery through ADB?
ok how to do that ADB?
What is ADB ...can someone please help
Thanks
You shouldn't be flashing pre-beta firmwares if you don't know how to use adb.
Use Google or the forum search to find out all about adb.
Also, if the phone is booting as far as the Cyanogen logo, then it's not even remotely "bricked", it does sound like you've managed to stuff up the recovery though, probably ROM Manager's fault, it has a habit of breaking things horribly.
Boot into fastboot and flash the latest Amon Ra recovery, then boot into recovery, do a full data wipe and flash a standard firmware back on.
Yep it's dead, send it to me because I'm building a house.
OK so I fastboot with sdk ...
Because the recovery option just send me to the dreaded X and then nothing
Not bricked. The best people to help you through it the fastest are on the Cyanogen Mod IRC Chat. Make a screenname and one of our amazing Devs will help you though the crisis. Been there, and you'll love them for it.
When I was a newbie in xda, I made sure to research thoroughly before blindly doing weird kinky stuff to my phone.
The xda wiki was one place that helped me in my dark noobish times.
Do yourself a favor and read up the wiki, you might find your answer there.
http://forum.xda-developers.com/wiki/index.php?title=File:Nexus_One.png
get yourself the android SDK, run a cmd window, while your phone is bootlooping;
type adb remount
you should get a message "remount successful"
now type; adb shell rm /system/app/NetworkLocation.apk
and also; adb shell rm /system/app/OneTimeInitializer.apk
your phone should now boot normally
thanks
I.ll try it when i come back from work
But it isn't bootlooping persay...I get the cyan guy and the cm7 logo screen (the arrow turns for awhile...then I get the Green Android guy and it says click to start...I can't even click ...the blue cyan screen starts ...then the green guy ...this loops for ever.
In bootloader mode ( power+trackball) when I try to recover...the the google X logo appears the phone shakes then black screen....nothing happens.
I think that either clockwork recovery is broken (because I saved 3 back-ups from rom manager)...or it works but I cant see screen (SLCD)...Anyway, is there a way to just flash en existing image on my sd card.....
Also my phone was soft rooted (androot) I don't have the big unlocked under the x...will this prevent me from using fast boot to flash???
Thanks guys I know I'm a newbie...Ive read alot...I'm sorry if I offend some of you guys...Thanks for the help....
Sounds like your bootloader is still locked... in that case, fastboot will not work for your phone.
Still read the section on flashing recovery in the xda wiki. There's a section on how to flash a recovery without fastboot but adb.
adB
Ok isn't ADB a driver for usb ...
Anyone know a step by step for morons ( like me)
That have a locked phone, a corrupted bootloader ( or recovery not working) and modified roms on the sd card...
Can i just erase the sd ( put stock image on it)
I will try this at 2pm I must go to work....thanks for the help
Yes.
Download: http://shipped-roms.com/shipped/Pas...le_WWE_2.16.1700.1_FRG33_MFG_Shipment_ROM.zip
Unzip it, and rename the extracted file passimg.zip
Place it on the root of your SD card and power the phone on holding Vol-
It will find the file and ask if you want to install, pick yes.
Ok
Ok heres what I did so far:
I used an empty sd card ( formated it and put followed what you said: put renamed image oanto sd card)
I power with the volume, here is what happens:
I click on bootloader
I get : recovery option , click the X comes back on shaked and then I get a black screen
Ive waited for 10 minutes nothing
Also: when I click on boot loader, I see ( in green) it saying wrong image, wrong something else.....
Can someone telle what I did wrong
Thanks
Did you extract the zip from within the zip, as instructed?
Sent from my Nexus One using XDA App
ok heres something else I tried:
Went to the original sd card with everything on it) went to the clockwork folder) went to an old back up folder ( copy pasted everything onto the empty sd card) put the sd card into the phone , press power + volume - , get the green guys with skateboards , click onto boot loader ( see the same errors that roll down quickly, funny why they fly down so fast...but I think it says bad image or wrong image or time ) . Anyway, still same thing when I press recover ( with power button) the X shows up , the phones vibrates and then the black screen.
I i do a normal power on ....still get the CM7 boot guy , the arrow that turns around him a few times , then the green guy that ask you to click on him, then you can't even click on him...the CM7 boot guy starts all over (this loops til infinity)
Just so you guys know, the phone was rooted with androot...so I don't know it its still rooted since the software dowsn't work....
Any ideas guys...thanks...
I will try the adb method late tonight...but Im not sure its works if the phone is soft rooted...
Thanks
Did you really rename the passimg.zip correctly? The bootloader should automatically detect the file and prompt you if u want to update. If it did not detect it, it could be the wrong file u renamed.
Remember that once you boot into bootloader using the vol down button, you have to wait for it to detect the passimg.zip before doing anything else.
And fastboot will not work on your phone. You need the roundabout method to flash recovery using cmd.
Ok heres what I did:
1-I download the link Rusty! supplied
2-I extract using winrar to the empty sd card ( a 2 gig card that has been formated using windows format tool to fat 32)..not the one that came with the phone)
3-Once the file in on the sd card, I rename is ( copy paste) exactly passimg.zip
4-I ask windows to eject
5-I insert the card
6-I press the power and volume down
7-I wait , so that fastboot is read.
8-I select fastboot wait a few seconds , select Fastboot ( is green letters) with the power button, it changes to bootloader( green letters), I see green text roll down( says ' i try to see, wrong....something)
9- nothing happens
10-I click recovery, the phone vibrates, get the X, phone goes black
****I tried reading that roll down message : wrong image is there with some other stuff
These are the steps...nothing
Thanks for the help
More info (when I boot in skateboard mode):
nexusone PVT SHIP S-ON
HBOOT-0.35.0017
MICROP-0c15
TOUCH PANEL-SYNT0103
my radio is : 5.12.00.08
June 14 2010,12:02:27
HBOOT
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
Its also a videotron phone....I did modify the radio from original stock
Dunno if this can help
Thanks
I'm having an irritating problem.
I've rooted my wife's Gen 1 Orange SF with Androot, even repeated it when I started having problems to make sure the root had worked. SuperUser is installed and working so I know it has gone OK.
I've installed Recovery Manager v0.36, which has root access.
The current recovery is listed as "unrecognised"
I flashed the following CWM - recovery-clockwork-3.1.0.1-blade-gen1.img (MD5 checksum correct)
I get an "installing" message, then back to the Recovery screen and the recovery is still listed as "unrecognised".
One of the guides I found on Modaco is quite specific about using Recovery Manager v0.34 (though I suspect it just hasn't been updated with the latest release) so I've also tried this using that version and no joy.
So... I thought I'd try the FASTBOOT method. I turn the phone off, remove and replace the battery. Turn the phone on whilst holding the up volume button, and the phone just boots up normally. I've tried this repeatedly, I don't get the big grey square that people report when FASTBOOT fails, I just get no response at all.
Grrrrr!
Any thoughts?
Hmm, when you power up holding volume up key (held for a couple of seconds) does you phone show a static green android logo, or does it boot up fully to the lockscreen?
If only to the android logo, means you're in fastboot.
Edit: you can replace the green android logo with Orange's logo in the above comment if you haven't flashed an alternate ROM on the phone as yet.
I also had the same while trying to flash a recovery to my friend's Blade. I understood that i have been flashing the wrong recovery all this time (though it showed for gen1 and i had a gen1). I used the given recovery(link provided below), and it worked for me like a charm. Use the link download on root of sd card. Use recovery manager to install it. If the recovery manager shows that it has identified the cwmod version then its done or else if it again says unrecognised try different versions of cwmod.
Preferably after getting cwmod to working convert your gen1 to gen2 (wbaw method). Then you can flash a custom rom and use ROM manager to upgrade your cwmod recovery.
http://android.podtwo.com/recovery/archived/recovery-clockwork-3.0.2.8-v9-gen1.img
To Convert gen1 to gen2:
http://forum.xda-developers.com/showthread.php?t=1103096
harmohn said:
Hmm, when you power up holding volume up key (held for a couple of seconds) does you phone show a static green android logo, or does it boot up fully to the lockscreen?
If only to the android logo, means you're in fastboot.
Edit: you can replace the green android logo with Orange's logo in the above comment if you haven't flashed an alternate ROM on the phone as yet.
Click to expand...
Click to collapse
He hasnt been able to install CWmod yet so no green logo will appear. Due to unrecognised version only DELL logo appears and hangs or it reboots normally. And yes FASTBOOT is not enabled in gen1 devices so thats why i say to convert to gen2 as soon as possible.
Hi Be4con,
I flashed a batch of 10 blades the other day, and wrote my own little guide for it. I had exactly the same problem as you with the first two i tried to flash.
The guide on modaco does work, but i found i had to use a much older version of clockwork mod. I used 2.5.0.8 (if i remember correctly) not at work just now so cant see my notes. This was picked up by the recovery no problems and i was able to move on from there.
Hope that helps
Hi
You have try to flash directly to your device with a terminal emulator
type SU
accept SuperUser autorisation
type flash_image recovery /sdcard/recovery_xx_xx.img (you find the good version on the recovery on internet)
reboot your phone with volume + down
if you have any problem to find the fine recovery or to flash the recovery contact me on pv . this method work with my zte gen1
Well somehow i bricked my phone,I'm stuck on the Motorola logo,i try using sbf but it does not recognize my phone, oh yeah i had install cm7 diet rom witch really would not let me get into recovery cuz it kept saying that my phone was a htc bravo? So i try a droid bootstrap to see if that work and that's when my phone got bricked, can someone please help,and yes i tried going into recovery by pressing the volume and power button and it takes me into recovery and brings me to the Android and exclamation but that's it, even if i pressed the lower right corner nothing happens
ssfirme said:
Well somehow i bricked my phone,I'm stuck on the Motorola logo,i try using sbf but it does not recognize my phone, oh yeah i had install cm7 diet rom witch really would not let me get into recovery cuz it kept saying that my phone was a htc bravo? So i try a droid bootstrap to see if that work and that's when my phone got bricked, can someone please help,and yes i tried going into recovery by pressing the volume and power button and it takes me into recovery and brings me to the Android and exclamation but that's it, even if i pressed the lower right corner nothing happens
Click to expand...
Click to collapse
Press both volume buttons on the screen with the android and exclamation mark. That'll take you to stock recovery where you need to wipe data and factory reset.
If you have to flash the sbf again, try using sbf_flash on Linux. It'll flash in times where RSD won't recognize your phone.
Linux Live\sbf_flash tut
sbf_flash binary is in attachments
Only use Defy 2nd-init for recovery
(and once its installed, steal /system/bootmenu/* and /system/bin/bootmenu from Defy CM9 from June 5th on up -- touch bootmenu is pretty awesome; replacing the bootmenu isn’t for the feint of heart.)
the only problem is i dont have linux i have windows 7
Use rsdlite sri I don't have a link on me
Sent from my Galaxy Nexus using XDA
Had same type of problem on Friday. Followed this post http://forum.xda-developers.com/showthread.php?t=1559109 now I'm back up and running.
ssfirme said:
the only problem is i dont have linux i have windows 7
Click to expand...
Click to collapse
I dual boot between the two
If you have a blank cd and a usb drive\sdcard you can just use a Linux Live environment -- you never install Linux at all -- and you can use sbf_flash from there.
RSD Lite version that works and tutorial
And since it hasn't been mentioned yet, holding volume up + power on boot access the boot recovery to flash sbf's. Just make sure you have at least 50% battery before flashing or you might get an actual brick.
What your dealing with is nothing more than a recovery screw up. I had the same problem last night installing touch recovery -- it wiped /bootmenu/ instead of installing to it. Solution is to flash sbf, reboot, wipe data/factory reset from stock recovery, reboot, eebluroffee at first screen, root, enable non market apps, Defy 2nd init flash something that's better than stock.
ok i install the motorola usb drivers and start up rsd lite but it does not regocogize my phone
yes i have it in bootloader mode
Did you install everything before plugging phone in?
Try uninstalling everything motorola related and reinstalling just the drivers....On a previous Win7 install nothing was recognized, but on a reinstall of the entire system it worked fine and still does. I still recommend the Linux way over RSD because it will flash your phone regardless, provided you can access the loader.
I still haven't gotten native tethering to work with Windows, but then again, I quit trying sometime around December or January.
ssfirme said:
ok i install the motorola usb drivers and start up rsd lite but it does not regocogize my phone
Click to expand...
Click to collapse
This is for all those people who are having trouble flashing with RSDlite in Vista & WIndows 7.
If I am right, RSD lite does not seem to recognize the sbf file after you select it and instead the "start" button remains grayed out.
If that's the case, here the solution:
I had a similar problem and sucessfully used the command line parameters for RSDlite to force a flash. I managed to get a signed/unsigned firmware installed.
You need to copy the firmware you want to flash into the RSDlite directory in your program files folder.
Make sure you are in bootloader mode first.
Then, open command prompt and "cd" to the RSDlite directory
eg:
> cd C:\
> cd Program Files
> cd motorola
> cd RSDlite
>
now for the flashing type:
> SDL.exe -f xxxx.sbf -t 2
where xxxx.sbf is the firmware you are flashing to the phone.
flashing will begin shortly afterwards.
It worked for me, but in the end, show FAIL STATUS.
skeevy420 said:
I dual boot between the two
If you have a blank cd and a usb drive\sdcard you can just use a Linux Live environment -- you never install Linux at all -- and you can use sbf_flash from there.
RSD Lite version that works and tutorial
And since it hasn't been mentioned yet, holding volume up + power on boot access the boot recovery to flash sbf's. Just make sure you have at least 50% battery before flashing or you might get an actual brick.
What your dealing with is nothing more than a recovery screw up. I had the same problem last night installing touch recovery -- it wiped /bootmenu/ instead of installing to it. Solution is to flash sbf, reboot, wipe data/factory reset from stock recovery, reboot, eebluroffee at first screen, root, enable non market apps, Defy 2nd init flash something that's better than stock.
Click to expand...
Click to collapse
Thank you sooooooooooooooooo much!
After several hours of messing with my brothers Bravo, I finally got it working by following your instructions.
Really: I'm speechlees man.
hard bricked my phone
hello. i'm looking for any help to this issue: i believe i hard bricked my bravo somehow. it was running one of the first MIUI rom for two or more years. but became slow and laggy thru last months. and the other day it just freezed while i was browsing the call log. no reaction to the pover button at all, had to take out the battery. now it gives no reaction to any combination of button presses ( power; vol up + power ; vol down + power), the only signal what see is white LED light when į connect the phone to the PC. When phone is connected to the pc freshly, and when i press Vol down + Power, Windows 7 releases "clink" sound and device manager tries to show that "Motorola USB Device" is connected, but quickly disapears with another Windows sound. RDS lite 5,0 doesnt recognize phone too.
Is there any chance to bring this phone alive? any advise will be appreciated.
p.s. english isn't my native. sorry for the mistakes
dzdonce said:
hello. i'm looking for any help to this issue: i believe i hard bricked my bravo somehow. it was running one of the first MIUI rom for two or more years. but became slow and laggy thru last months. and the other day it just freezed while i was browsing the call log. no reaction to the pover button at all, had to take out the battery. now it gives no reaction to any combination of button presses ( power; vol up + power ; vol down + power), the only signal what see is white LED light when į connect the phone to the PC. When phone is connected to the pc freshly, and when i press Vol down + Power, Windows 7 releases "clink" sound and device manager tries to show that "Motorola USB Device" is connected, but quickly disapears with another Windows sound. RDS lite 5,0 doesnt recognize phone too.
Is there any chance to bring this phone alive? any advise will be appreciated.
p.s. english isn't my native. sorry for the mistakes
Click to expand...
Click to collapse
Not sure if this will help since I did not watch the video myself, but a quick Google search gave me a video describing how to take a Motorola USB cable and modify it to unbrick a phone. I did not watch the video yet so I don't know how relevant it is to your problem. But just by looking at the video preview it looks like the difficulty level may be pretty high... Here is the link:
http://m.youtube.com/watch?v=XwwI_6doBWk
Sent from my LG-D415 using XDA Free mobile app
EDIT:
UPDATED POST AT THE BOTTOM!
Hey guys,
flashed czechops CM 10.2 a while ago everything was running fine.
On Saturday i decided to let the battery drain completely to do a full recharge. That`s when the Problems started.
After booting the Phone up i was stuck in a Bootloop with the Cyanogenmod Logo turning around and around and around and so on.
Okay i thought let`s reboot and see what happens.
Still the same.
I then booted into recovery by holding the x button on the keyboard and power and then when the androind in the triangle showed up using vol + and vol - to get into recovery.
I then deleted the cache and rebooted again (No full wipe to factory default trying to avoid that).
After that the phone turned on saying Android is getting updated Updating Package x of y.
After its done its now stuck in Apps getting started.
After i found out to get to the Bootmenu i decided to check the Recovery Menu there.
I can choose between Motorola Stock Recovery (the normal one i already was on)
and Team Win Recovery.
So i choose Team Win Recovery and thought okay since its not working im gonna install the Update of czechops 10.2
Installing itself worked fine. But now im stuck in the same loops.
Currently im goind a Backup of the System with the Team Win Recovery in the hope i wont loose the data even if what im trying to avoid a full factory wipe.
What kinda poped in my eyes when i started the recovery was that it said E: Unable to locate '/boot' partition for backup.
Could this be the problem which is stopping the phone from booting correctly?
And if so how can i fix it?
Hope anyone can help me,
Kind Regards,
Invi
I had te same problem before doing a clean install.
I don't know why but, if you install the android 10.0 tezet and from there start the gapps, creating a account and installing your apps, you do not have problems to install the 10.2.
Good luck.
Sent from my A953 using xda app-developers app
jonasgitz said:
I had te same problem before doing a clean install.
I don't know why but, if you install the android 10.0 tezet and from there start the gapps, creating a account and installing your apps, you do not have problems to install the 10.2.
Good luck.
Sent from my A953 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the heads up jonas.
Unfortunately its too late its seems. My Milestone is just a stone now it seems.
After trying to install 10.2 12.03.14 and that not working correct after doing a full factory wipe i decided to install cm 11 from czechop.
Unfortunately it seems it failed.
My milestone just boots up and stops at the First Logo. No lights. No chance to get in any recovery mode except the normal one.
Bootloader was working some time but stopped cause the Battery is almost empty.
The Problem is i cant even load the Phone anymore cause as soon as i put it on a charger it boots up and wont get enough battery power to live for a few minutes.
So the only thing left working is the normal Android 3e Recovery. Hope i can do anything from there.
Don't give up.
Your problem it's normal, you fisrt need a global battery charger to recharge your battery.
After it, go to boot recovery, you must turn on the milestone holding " volume down + camera" or "volume up + camera", than you need to uses the RSD Lite to reflash your milestone 2.
Normaly, when do you came from another room, you stay in boot loop, so you need to entery in Miestone recovery, "x + volume down" than after it you do a factory reset. It will boot normaly after that.
To go to boot recovery, you must turn on.
Try harder.
(Guys, lets try to help a little)
Sorry about my poor english
I wont. Already ordered an global battery charger yesterday. In the mail from the store delivery is 7-10 Weekdays.
Good thing i have a second cellphone which i can use in the meantime.
i had a similar scenario
Invisan said:
Thanks for the heads up jonas.
Unfortunately its too late its seems. My Milestone is just a stone now it seems.
After trying to install 10.2 12.03.14 and that not working correct after doing a full factory wipe i decided to install cm 11 from czechop.
Unfortunately it seems it failed.
My milestone just boots up and stops at the First Logo. No lights. No chance to get in any recovery mode except the normal one.
Bootloader was working some time but stopped cause the Battery is almost empty.
The Problem is i cant even load the Phone anymore cause as soon as i put it on a charger it boots up and wont get enough battery power to live for a few minutes.
So the only thing left working is the normal Android 3e Recovery. Hope i can do anything from there.
Click to expand...
Click to collapse
hi, I had a similar situation to that earlier today, in that I got to the situation where on boot up I got the Motorola logo then nothing else (I was trying to install C.M. 11 from 10.2 but when it went to install got a message E;// error - verification signature installation aborted), after major panic thinking I'd bricked my milestone, I tried starting the phone in bootloader mode (press camera, volume up and power buttons at the same time) which gives a black screen saying boot loader 70.13 and towards the bottom says boot menu, connect USB, then on your pc find program MOTOROLA SOFTWARE UPDATER (hope you've got it) open the program, it'll say connect a device plug your phone in and let it do it's stuff, takes about an hour (charge your battery using a desktop battery charger beforehand) and your phone will be returned to the stock Motorola rom but at least your phone isn't a brick and you can always start again trying cyanogenmod.
hope this helps
mark13_2001 said:
hi, I had a similar situation to that earlier today, in that I got to the situation where on boot up I got the Motorola logo then nothing else (I was trying to install C.M. 11 from 10.2 but when it went to install got a message E;// error - verification signature installation aborted), after major panic thinking I'd bricked my milestone, I tried starting the phone in bootloader mode (press camera, volume up and power buttons at the same time) which gives a black screen saying boot loader 70.13 and towards the bottom says boot menu, connect USB, then on your pc find program MOTOROLA SOFTWARE UPDATER (hope you've got it) open the program, it'll say connect a device plug your phone in and let it do it's stuff, takes about an hour (charge your battery using a desktop battery charger beforehand) and your phone will be returned to the stock Motorola rom but at least your phone isn't a brick and you can always start again trying cyanogenmod.
hope this helps
Click to expand...
Click to collapse
So i downloaded Motorola Software Updater and RSD Lite + Motorola Device Manager newest Version
Unfortunately my Milestone seems not to be recognized by either Software updater nor RSD Lite.
In the Device Manager S Flash OMAP3630 shows up and is recognized.
Im running Windows 8.1 x64 and on a second Computer Windows 7 x64
What tool can i use ander Linux? Maybe the Phone will be recognized there.
EDIT:
K found it. Doing it with Linux at the Moment. Its working.
Only need to Root it then and after that flash my old Files and hope they are working.
At least i have an old Backup i made from Tezet before going up to 10.2 which i made with Clockworkmod
Hope it will work and not be broken like the one i made with Team Win Recovery.
Anyone knows how i can change stuff in a Team Win Backup?
Invisan said:
So i downloaded Motorola Software Updater and RSD Lite + Motorola Device Manager newest Version
Unfortunately my Milestone seems not to be recognized by either Software updater nor RSD Lite.
In the Device Manager S Flash OMAP3630 shows up and is recognized.
Im running Windows 8.1 x64 and on a second Computer Windows 7 x64
What tool can i use ander Linux? Maybe the Phone will be recognized there.
EDIT:
K found it. Doing it with Linux at the Moment. Its working.
Only need to Root it then and after that flash my old Files and hope they are working.
At least i have an old Backup i made from Tezet before going up to 10.2 which i made with Clockworkmod
Hope it will work and not be broken like the one i made with Team Win Recovery.
Anyone knows how i can change stuff in a Team Win Backup?
Click to expand...
Click to collapse
I did find it took a long time for the Motorola software updater (about 20 mins) to detect my milestone 2 (I'm using windows7 x64), I'm thinking the mistake I made when trying to upgrade to CM 11 was I didn't wipe data/cache before trying to install it
mark13_2001 said:
I did find it took a long time for the Motorola software updater (about 20 mins) to detect my milestone 2 (I'm using windows7 x64), I'm thinking the mistake I made when trying to upgrade to CM 11 was I didn't wipe data/cache before trying to install it
Click to expand...
Click to collapse
Hi mark,
well Windows popped up saying N/A
when it should show new Software.
It also couldnt recognize my Cellphone correctly it seemed.
But i flashed it with Linux anyways.
Flashing to tezet`s 10 worked also like a charm
and i could install my Backup i made in december before
updating to czechops 10.2.
Guess after i know what to do now i will try to update to cm11 now.
Invisan said:
Hi mark,
well Windows popped up saying N/A
when it should show new Software.
It also couldnt recognize my Cellphone correctly it seemed.
But i flashed it with Linux anyways.
Flashing to tezet`s 10 worked also like a charm
and i could install my Backup i made in december before
updating to czechops 10.2.
Guess after i know what to do now i will try to update to cm11 now.
Click to expand...
Click to collapse
let us know how you get on as I'm tempted to try again (I do like how CM10 gets rid of all the un-necessary apps but gives you control of all the system parameters) but want to step up to CM11 without having the same problem as before.
A year or two so ago I updated my Motorola Milestone 2 to CyanogenMod, Android 4.1 I think, with no trouble.
I though that I'd take advantage of the CM11 (cm-11-20141003-UNOFFICIAL-milestone2.zip) and I attempted to upgrade to this.
I found that, after booting to the recovery utility, that would not accept this zip file. I noticed that czechop says:
Install my CM10.2 version >= 07.11.2013 first
So I installed cm-10.2-20140312-UNOFFICIAL-milestone2.zip and that went like a breeze. The phone booted up with the new version of Android. I then booted this into the recovery utility and found a new style of this ('Teamworks', I think) with a graphical interface. I found that this liked the cm11 zip file and it installed it without any apparent problem - it reported success and gave me two options - 'clear cache dalvik' (or something very similar), and 'reboot'. I opted for the clear cache, and that seemed to go OK, then I opted for 'reboot'.
This is where my heart sank, because the phone started to boot with the Motorola 'M' logo, then that faded out, then back in, then out. I see no little coloured LED light, and the phone seems to cycle around with the 'M' display, never getting anywhere.
What should I do now? I tried to boot the phone into the original Motorola recovery, holding down the keyboard 'X' key whilst switching on, but that just brings up a little picture of an orange triangle with a '!' in it.
Regards,
David
Hi,
Your best option is to ask for help in the thread you downloaded the rom from.
Good luck!
Thanks
Darth said:
Hi,
Your best option is to ask for help in the thread you downloaded the rom from.
Good luck!
Click to expand...
Click to collapse
Thanks. Unfortunately the site won't let me post there. I'm a new member.
Ah, There's no Q&A section. Normally now if you post in a development thread it automatically creates or posts in a thread in your device section Q&A.... But this won't work cause your section has no Q&A.
I will have your thread moved to your devices General section.
Good luck!
More on 'bricked' Milestone 2
datatone said:
A year or two so ago I updated my Motorola Milestone 2 to CyanogenMod, Android 4.1 I think, with no trouble.
I though that I'd take advantage of the CM11 (cm-11-20141003-UNOFFICIAL-milestone2.zip) and I attempted to upgrade to this.
I found that, after booting to the recovery utility, that would not accept this zip file. I noticed that czechop says:
Install my CM10.2 version >= 07.11.2013 first
So I installed cm-10.2-20140312-UNOFFICIAL-milestone2.zip and that went like a breeze. The phone booted up with the new version of Android. I then booted this into the recovery utility and found a new style of this ('Teamworks', I think) with a graphical interface. I found that this liked the cm11 zip file and it installed it without any apparent problem - it reported success and gave me two options - 'clear cache dalvik' (or something very similar), and 'reboot'. I opted for the clear cache, and that seemed to go OK, then I opted for 'reboot'.
This is where my heart sank, because the phone started to boot with the Motorola 'M' logo, then that faded out, then back in, then out. I see no little coloured LED light, and the phone seems to cycle around with the 'M' display, never getting anywhere.
What should I do now? I tried to boot the phone into the original Motorola recovery, holding down the keyboard 'X' key whilst switching on, but that just brings up a little picture of an orange triangle with a '!' in it.
Regards,
David
Click to expand...
Click to collapse
I am going to journal my experiences with this, in the hope that it will be useful to someone else.
Possibly the mistake that I made when flashing the CM11 (see above) is that I didn't put the md5 sum file onto the SD card with the archive. Note that all downloads have a .zip and a .zip.md5sum file. The phone output a message to say that it couldn't find a checksum, but that it was going ahead anyway. Possibly, had I put the md5sum file in, a fault with the zip file would have been detected and I may have been saved from this issue.
I have found references to a 'Motorola factory cable' which is a cable that is wired to persuade the phone not to worry about battery state and to operate the flashing utility from the usb cable power. this is obviously useful in the factory for programming the phone without a battery. See this link for information:
[unfortunately the site didn't allow me to attach a url to 'www dot droidforums dot net' where you might find a posting 'how-why-to-make-your-own-motorola-factory-cable', which is a well-writen and informative article]
My phone is in a state that the charger will operate to charge the battery as normal when the charger is plugged in with the phone off. It still shows the image of a battery filling up. Therefore I can keep my battery in good condition between recovery attempts, and I don't think I'll need any special cables.
My technique for putting the archives onto the SD card is to take the card out of the phone and put it into my laptop, so that I can simply manage the files on it with standard Windows file browser.
I can get to a very promising recovery utility by holding down the 'X' key on the keyboard whilst switching the phone on. The Motorola 'M' logo comes up and the screen then displays a 3D orange triangle with an exclamation mark and a little green Android man. If I press the keyboard '@' at this point, I jump into a recovery menu.
The recovery menu has options:
* 'reboot system now'
* 'apply sdcard:update.zip'
* 'wipe data/factory reset'
* 'wipe cache partition'
The 'apply sdcard:update.zip' seems to offer the promise of recovery.
I have tried placing both:
* cm-10.2-20140312-UNOFFICIAL-milestone2 (.zip and .zip.md5sum)
and
* cm-11-20141003-UNOFFICIAL-milestone2 (.zip and .zip.md5sum)
onto the sdcard (renamed as 'update.zip' and 'update.zip.md5sum').
In both cases the recovery utility says:
---
E:Can't open /cache/recovery/command
E:Can't open /cache/recovery/caller
-- Install from sdcard...
Finding update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
---
If I remove the update.zip.md5sum file, the result is identical. Therefore I don't think that this utility is using the md5sum for archive file verification. The problem that I seem to have at the moment is that I need an archive in the right format for the factory recovery utility.
I will be researching this and will add to this thread when I find an answer.
As a little bit of extra information, whilst fiddling about with the buttons during power up, I did manage to get a screen that said:
---
Bootloader
70.12
Battery OK
OK to Program
Connect USB
Data Cable
---
I guess that this is a lower stage in the bootloader chain, and suggests that there is hope if your phone is screwed up to the extent that you can't get the factory recovery utility. Thankfully, I don't seem to need to investigate what is required at the PC end to make use of this low level programming aid. (If anyone knows, it would be good to hear the details, for future reference and help to others).
Alas, I'm not sure what I did to bring this screen up - I fiddled with the volume, camera, and power buttons whilst the phone was starting up.
Regards,
David
Hello.
1. You don't need no 'factory cable'. All you need to come back to stock ROM is PC, RSDlite software, generic USB<->micro USB cable, and a stock ROM sbf file. The question what to do with a bricked phone was answered here plenty of times. Almost always the best way to bring a dead phone back to life is to flash a stock ROM (with bootloader version >= of version of current one).
2. You seem to have an older bootloader (the latest is 70.13 included in Ginger Bread ROMs), but you don't have to flash a newer one. Just remember, that bootloader is locked and cannot bet downgraded, so if you flash a newer one, you will never be able to flash generic ROMs with an older version. For example after I flashed 70.13 GB, a was unable to flash Froyo ROM over it (but you'll still be able to flash Froyo based CM7 with some tricks).
3. If you can access TeamWinRecovery (the graphicac one), you can simply clear system/cache partitions, and flash any custom ROM zip (for example Czechop's 10.2).
4. The stock recovery (with an exclamation mark, then you press both vol up and down to access menu) doesn't allow to flash unsigned zip images (and none of custom ROMs is signed with Motorola key). What you can do there is try to clear cache/data (factory reset). Sometimes some information in /data is preventing ROM from booting, if you changed ROM.
5. What You described is called a 'bootloop' - rebooting endlessly.
Progress
rabinhood said:
Hello.
1. You don't need no 'factory cable'. All you need to come back to stock ROM is PC, RSDlite software, generic USB<->micro USB cable, and a stock ROM sbf file. The question what to do with a bricked phone was answered here plenty of times. Almost always the best way to bring a dead phone back to life is to flash a stock ROM (with bootloader version >= of version of current one).
2. You seem to have an older bootloader (the latest is 70.13 included in Ginger Bread ROMs), but you don't have to flash a newer one. Just remember, that bootloader is locked and cannot bet downgraded, so if you flash a newer one, you will never be able to flash generic ROMs with an older version. For example after I flashed 70.13 GB, a was unable to flash Froyo ROM over it (but you'll still be able to flash Froyo based CM7 with some tricks).
3. If you can access TeamWinRecovery (the graphicac one), you can simply clear system/cache partitions, and flash any custom ROM zip (for example Czechop's 10.2).
4. The stock recovery (with an exclamation mark, then you press both vol up and down to access menu) doesn't allow to flash unsigned zip images (and none of custom ROMs is signed with Motorola key). What you can do there is try to clear cache/data (factory reset). Sometimes some information in /data is preventing ROM from booting, if you changed ROM.
5. What You described is called a 'bootloop' - rebooting endlessly.
Click to expand...
Click to collapse
Thank you very much. I have spent all day researching this.
I have discovered 'RSD Lite' and the ability to get the phone into the bootloader mode that I described by starting the phone and keeping the camera and volume buttons pressed.
I can boot to the stock recovery mode by powering up with the 'X' key pressed and then pressing '@'
I don't think that I can access TeamWinRecovery. There may be some way to do this that I don't know.
I did do a complete 'Nandroid?' backup of the system before I started this, so I guess that if I can get TeamWinRecovery or clockworkmod recovery back, I can restore to my previous working state.
What I have tried is 'G.O.T.’s OpenRecovery' to get a recovery installed. I put the OpenRecovery folder and the update.zip onto the SDcard and tried to flash it with the stock recovery utility. I got the "E:EOCD marker occurs after start of EOCD E:signature verification failed" error. I read that this means that I am not properly rooted (I thought I was) and I need to install 'vulnerable recovery' using an sbf file and RSD Lite. I have tried 'vulnerable_recovery_only_RAMDLD90_78.sbf' but the process errors, and what I read suggests that this might be due to the older bootloader version.
I tried to find an old stock android sbf for the phone, but all the links to such things seem to be dead.
I did try the factory reset from the stock recovery as a means to fix the bootloop. It didn't work.
You clearly know a lot about this. I would appreciate help to get back to something that works, maybe the last backup that I did.
I am also puzzled by why the upgrade to the CM11 from the CM10.2 failed. Did I do something wrong, or is there some compatibility issue with my phone? I never had a problem updating from the original motorola software to the cyanogenmod, then to the CM10.2.
I think I became a little over-confident.
Thank you in anticipation,
David
---------- Post added at 06:20 PM ---------- Previous post was at 05:59 PM ----------
rabinhood said:
Hello.
4. The stock recovery (with an exclamation mark, then you press both vol up and down to access menu) doesn't allow to flash unsigned zip images (and none of custom ROMs is signed with Motorola key).
Click to expand...
Click to collapse
Ah! the penny drops. The stock recovery that I can access will only install archives signed by Motorola. Hence the signature errors that I get when I try anything else. So I understand that if I can only get to the stock recovery, I can only use it to reinstall a stock android.
So the problem is where to find a stock sbf file to reinstall Motorola android as a first step to getting back to CM.
I guess that this is the only way to get back to clockworkmod recovery or teamwin recovery?
If I can get one of these recoverys running, I can simply restore to the last working system, I guess?
Regards,
David
---------- Post added at 07:07 PM ---------- Previous post was at 06:20 PM ----------
david.datatone said:
My phone is in a state that the charger will operate to charge the battery as normal when the charger is plugged in with the phone off. It still shows the image of a battery filling up. Therefore I can keep my battery in good condition between recovery attempts, and I don't think I'll need any special cables.
Click to expand...
Click to collapse
I realise that I was mistaken about this. There is no image of a battery filling up. The white LED by the USB socket lights when the charger is plugged in, but I can't be sure that the battery is charging.
Are you sure you're trying to flash a proper recovery? I remember there was a 'vulnerable recovery' for milestone 1, but no such thing for MS2. As you wrote, signature errors while trying to flash zips from stock recovery are due to lack of Motorola signature, not to problems with root. Root access has nothing to do with recovery, it is something much later/higher in system.
So again, what to do to unbrick the MS2:
1. Get a stock ROM - I suggest lates European one with 70.13 bootloader. There are also later Latin America ROMs, but they lead to more problems with custom ROMs. SBF's were published somewhere in these forums. If you cannot find them, write, and I'll upload one to some file sharing servers if I have time (I'll be staying at work for next 30 hours or so).
2. Get RSD lite and latest Motorola USB drivers (they're on the web), install. Before flashing remember you cannot use an USB 3 port - the best way is to turn USB 3 support off in computer BIOS.
3. Enter the flash mode in MS2. Connect is with generic USB cable to PC.
4. Run RSD lite, flash SBF, wait until phone reboots - it can take several minutes. If it freezes - try to enter stock recovery and wipe data/cache.
After these steps you should have a clear installation of stock ROM. Then you have to root, install Droid2 Bootstrap, install CM 10 or 10.1 -> 10.2 -> 11. If you have problems with these, write, and I'll write more detailed instructions.
PS. By the way, to enter TWR or CWM recovery you have to press vol down while a blue led is lit for a short time during reboot.
1000 Thanks
rabinhood said:
Are you sure you're trying to flash a proper recovery? I remember there was a 'vulnerable recovery' for milestone 1, but no such thing for MS2. As you wrote, signature errors while trying to flash zips from stock recovery are due to lack of Motorola signature, not to problems with root. Root access has nothing to do with recovery, it is something much later/higher in system.
So again, what to do to unbrick the MS2:
1. Get a stock ROM - I suggest lates European one with 70.13 bootloader. There are also later Latin America ROMs, but they lead to more problems with custom ROMs. SBF's were published somewhere in these forums. If you cannot find them, write, and I'll upload one to some file sharing servers if I have time (I'll be staying at work for next 30 hours or so).
2. Get RSD lite and latest Motorola USB drivers (they're on the web), install. Before flashing remember you cannot use an USB 3 port - the best way is to turn USB 3 support off in computer BIOS.
3. Enter the flash mode in MS2. Connect is with generic USB cable to PC.
4. Run RSD lite, flash SBF, wait until phone reboots - it can take several minutes. If it freezes - try to enter stock recovery and wipe data/cache.
After these steps you should have a clear installation of stock ROM. Then you have to root, install Droid2 Bootstrap, install CM 10 or 10.1 -> 10.2 -> 11. If you have problems with these, write, and I'll write more detailed instructions.
PS. By the way, to enter TWR or CWM recovery you have to press vol down while a blue led is lit for a short time during reboot.
Click to expand...
Click to collapse
I can't thank you enough. I'm currently downloading your stock ROM. I already have what I think is the latest verion of RSD Lite (6.1.6) installed on my Windows 8.1 laptop (I've read about problems with more contemporary versions of Windows, but I have successfully connected to the phone before now, just haven't had joy with flashing the file that I tried). I am fingers crossed that all will go well, and I'll certainly note that here. Otherwise I very much appreciate your offer of further help.
Bets regards,
David
david.datatone said:
I can't thank you enough. I'm currently downloading your stock ROM. I already have what I think is the latest verion of RSD Lite (6.1.6) installed on my Windows 8.1 laptop (I've read about problems with more contemporary versions of Windows, but I have successfully connected to the phone before now, just haven't had joy with flashing the file that I tried). I am fingers crossed that all will go well, and I'll certainly note that here. Otherwise I very much appreciate your offer of further help.
Bets regards,
David
Click to expand...
Click to collapse
recommend you return the original rom using RSDlite and start doing it all over again putting the rom CM10 and then cm11