first post, yes, i'm new to this... (forum, not flashing, not entirely anyway, i did fiddle with Sony Ericssons and stuff, kindergarden compared to androids)... but not an idiot, to the point:
firmware config. version seems to be RTGB, great britain, right? wrong, a RTUK is not it. I am sort of lost, i bought the phone with 2.1-update1, the 2.2.1 update has not yet been rolled out in my backwards country, so i did an official update over the internet with motorola app etc etc. I have no idea what was the 2.1 fw config. ver., but it strikes me as weird that i have a RTGB one now, the packaging/box/manuals all were German or something that looks like German. And now, i got myself RTUK sbf file, and RDS lite fails to do anything. I require assistance, and an explanation if possible as to why this didnt work? if i chose the wrong sbf, why does it show me having RTGB? and finally which sbf to take and from where (two german one's are available on this forum), but i've seen only one RTGB and it was only 2.1. For comparison, the friend bought the same phone on the same day, but she got one with a qwertz keyboard, mine is normal qwerty, fw config. ver. shows VFDE, did not update hers, it's still 2.1-update1. I can only assume that VF is german for RT and that her phone did not come from an unknows source. The phone company selling these obviously imports them, possibly even from random countries or EU countries at least...
however something did happen, my battery in the notification seems to be not present, there's just a question mark inside what appears to be an empty battery... apps that show battery levels work fine... although, scratch this last one, a reboot fixed it, even though i have not seen it before.
also, help me rack up some posts ^^ ask for info or whatever, i'd like to give a shot at improving my android...
Check the link below. You will get both service and non-service versions of 2.2.1 sbf's.
http://and-developers.com/sbf:milestone221
VF would be vodafone ( service version) while RT would be retail version.
Sent from my Milestone using Tapatalk
Thanks, gonna try asap, will come crying if it explodes in my face...
SuicideTree said:
Thanks, gonna try asap, will come crying if it explodes in my face...
Click to expand...
Click to collapse
It wont. I have done it many times and my face is still intact, as you can see from my avatar.
Sent from my Milestone using Tapatalk
now add a laptop that sometimes, actually recently starts bsoding not when you're gaming but when you're picking your nose... and now a serious question, how screwed am i if the laptop crashes WHILE doing something with RDS Lite or something similar ;]]
SuicideTree said:
now add a laptop that sometimes, actually recently starts bsoding not when you're gaming but when you're picking your nose... and now a serious question, how screwed am i if the laptop crashes WHILE doing something with RDS Lite or something similar ;]]
Click to expand...
Click to collapse
which version of rsdlite and what OS? rsdlite should not cause your OS to crash.
oh no, it's not rsd lite related, it's just laptop hardware being faulty, that's my assumption anyway, this laptop is going to the warranty next monday, it bsods randomly and i mean really randomly... atm i have win7ult x64 and rsd is 4.9... however this is unrelated, i had a linux here and on it was screwing me over from day one.
SuicideTree said:
oh no, it's not rsd lite related, it's just laptop hardware being faulty, that's my assumption anyway, this laptop is going to the warranty next monday, it bsods randomly and i mean really randomly... atm i have win7ult x64 and rsd is 4.9... however this is unrelated, i had a linux here and on it was screwing me over from day one.
Click to expand...
Click to collapse
Try it and see if it works.
Just finished. Seems to be good. Gonna Continue with the guide then ^^ Many thanks.
instead starting a new topic IDIOT QUESTION but... can someone give me a detailed dumbed down version of this instruction bellow:
If you applied an OTA update before, there is a script run at every system boot that checks and re-flashes the recovery when its checksum doesn't match. In such case, you have to avoid booting to android after the vulnerable recovery flash. Boot directly to recovery when RSD Lite restarts the phone (hold camera button) and from there remove the /system/etc/install-recovery.sh file.
rm -f /system/etc/install-recovery.sh
i am getting this
E:Cant open /cache/recovery/command
just upon entering AOR (power+x)
trying to apply the update regardless i get this
- install from sdcard
finding update package
opening update package
verifying update package
E:EOCD marker occurs after start of EOCD
E:signature verification failed
Instalation aborted
what is the meaning of this?
possible solutions:
"It seems that the key to successful recovery flash in some cases is to not let the phone to boot to android or recovery until the RSD Lite will signal PASS. When the RSD Lite is restarting the phone during flash, hold the D-Pad Up, so the phone enters the bootloader again immediately."
does this work? DIDNT WORK, so i still need help
i'm still combing through many threads mentioning this... either please tell me this works or point me in the right direction -_- thanks
Once you flash the official sbf, you need to flash the vulnerable recovery to enable you to run openrecovery which is used to flash custom roms and much more.
There is a script which checks your recovery image everytime it boots and replaces it with the original if it finds any changes. So you need to remove that script.
Procedure would be as follows.
1. Download and extract androidiani openrecovery to the root if your sdcard. You should have a update.zip file and openrecovery folder.
2. Flash official sbf.
3. Flash vulnerable recovery sbf. When the phone restarts and before it displays Moto logo, press and hold the 'x' key on your keyboard. You should see a triangle with exclamation mark. Press volume up + camera button and choose apply update menu option.
AOR should load up. Choose console option and type the following commands.
rm - rf /system/etc/install-recovery.sh
reboot
That's all.
Sent from my Milestone using Tapatalk
okay, so it seems i did all the steps EXCEPT flashing the original sbf... wait, the first link you provided was to a an official sbf - correct? then where do i get the vulnerability? or vulnerable_recovery_only_RAMDLD90_78.sbf is it? so, i have original flashed, when trying the vulnerability now it says failed, 0x7100, phone connected. what does that mean?
SuicideTree said:
okay, so it seems i did all the steps EXCEPT flashing the original sbf... wait, the first link you provided was to a an official sbf - correct? then where do i get the vulnerability? or vulnerable_recovery_only_RAMDLD90_78.sbf is it? so, i have original flashed, when trying the vulnerability now it says failed, 0x7100, phone connected. what does that mean?
Click to expand...
Click to collapse
The RAMDLD90_78 is the Vulnerable Recovery.
RSD Lite is a buggy program sometimes. What you need to do is put the sbf you want to flash on the ROOT of your C:/ drive and try it again.
I suppose there's no harm in trying that, i already had to rename it to something shorter, cause it wouldnt even give me the Start button.... brb
skadude66 said:
The RAMDLD90_78 is the Vulnerable Recovery.
RSD Lite is a buggy program sometimes. What you need to do is put the sbf you want to flash on the ROOT of your C:/ drive and try it again.
Click to expand...
Click to collapse
Buddy, please help him out with the rsdlite problem. I presume you had the same problem and someone helped you out, especially with the Windows 7 x64 error.
@SuicideTree : What is your ultimate goal? You want to have a Official ROM on your phone or you want to flash custom roms.
sileshn said:
Buddy, please help him out with the rsdlite problem. I presume you had the same problem and someone helped you out, especially with the Windows 7 x64 error.
@SuicideTree : What is your ultimate goal? You want to have a Official ROM on your phone or you want to flash custom roms.
Click to expand...
Click to collapse
You helped me out with that sileshn!
Yeah, I'll keep this thread up and I'll see what issues he's got.
sileshn said:
Buddy, please help him out with the rsdlite problem. I presume you had the same problem and someone helped you out, especially with the Windows 7 x64 error.
@SuicideTree : What is your ultimate goal? You want to have a Official ROM on your phone or you want to flash custom roms.
Click to expand...
Click to collapse
oh well, i was going for cyanogenmod, but for starters i'd like root to have some more control over my phone
EDIT: it also appears that once again it wont give me the START button, cant press it, moved files around, renamed and stuff... weird
EDIT2: by the way, is it normal for the vulnerability file not to show any file properties in RSD Lite?
SuicideTree said:
oh well, i was going for cyanogenmod, but for starters i'd like root to have some more control over my phone
EDIT: it also appears that once again it wont give me the START button, cant press it, moves files around, renamed and stuff... weird
Click to expand...
Click to collapse
Once you get VR, rooting and flashing a custom ROM is a piece of cake, so it shouldn't be that bad once you get there.
SuicideTree said:
oh well, i was going for cyanogenmod, but for starters i'd like root to have some more control over my phone
Click to expand...
Click to collapse
If you want to flash CM, just install GOT 2.2.1 from here and forget about VR. GOT has VR injected into it. Use the Retail UK sbf.
Once you have CM, you have root.
@skadude : Didn't know it was me.
is cm7 much better over cm6? cause i was looking into that ^^ however if the end goal can be achieved easier with got cm6 i should give that a try, but, what if i wanna play around with this stuff later or something? i'd like to understand what's happening at the moment... anyway, if i go with got solution what are the steps? flash uk sbf, then got or... then cm?
also, got or is better than aor? except apparently having vulnerability alreay in it... anything else?
thanks for all the help, sorry for being not too enlightened, i'll get there ;]]]
Related
Hi there,
Before anyone gets angry: I don't want to start a 1000st repetition of questions asked right 2 posts before, nor am I too lazy to use google or read the articles themself.
I just want to know, if there's somebody out there, who succeeded with exactly the same circumstances I failed.
I own a German Motorola Milestone . It is a Milestone, not a Droid! I guess, this is important, since I've read tons of these threads, which all ended in that way, that one tells that the Milestone is a lot stronger protected than the Droid from Verizon is, because it uses Signatures and stuff, to prevent anwanted development for the device.
I always was too shy to apply something like cyanogen to my phone or even root it, because I spend some hope to the (at last) shipped Froyo Update for the device, to make things better. But since Motorola not even raised the CPU clock (which runs only at 550, but 1200 MHz are reported to work without negative issues) to even 800 MHz and I can feel this with Froyos animations and Flash, I decided to give cyanogen a try. I tried to root the device (which succeeded) and tried also all overclocker apps on the market which made the device reboot instantly when applying (but did not raise the speed).
Now I'm trying to install cyanogen since several days, but all guides fail for me.
It all fails when it comes to applying the update.zip: Clockworks's rom Manager, which tells me that the recovery Programm couldn't be found at the boot prompt, opening the update.zip directly gives a message about something's failing with the certificates, ... an endless story
I come more and more to the guess, that all success messages for applying cyanogen to a milestone are only hoaxes, because someone couldn't tell the difference between a milestone and a droid on ebay and such.
I would be very thankfull for any answers, may they tell me that this is true, or that they have succeeded (and how!) Or even hand me the right guide. I have the feeling that I've allready read all the false ones
Sent from my Milestone using XDA App
Richter_Marc said:
Hi there,
Before anyone gets angry: I don't want to start a 1000st repetition of questions asked right 2 posts before, nor am I too lazy to use google or read the articles themself.
I just want to know, if there's somebody out there, who succeeded with exactly the same circumstances I failed.
I own a German Motorola Milestone . It is a Milestone, not a Droid! I guess, this is important, since I've read tons of these threads, which all ended in that way, that one tells that the Milestone is a lot stronger protected than the Droid from Verizon is, because it uses Signatures and stuff, to prevent anwanted development for the device.
I always was too shy to apply something like cyanogen to my phone or even root it, because I spend some hope to the (at last) shipped Froyo Update for the device, to make things better. But since Motorola not even raised the CPU clock (which runs only at 550, but 1200 MHz are reported to work without negative issues) to even 800 MHz and I can feel this with Froyos animations and Flash, I decided to give cyanogen a try. I tried to root the device (which succeeded) and tried also all overclocker apps on the market which made the device reboot instantly when applying (but did not raise the speed).
Now I'm trying to install cyanogen since several days, but all guides fail for me.
It all fails when it comes to applying the update.zip: Clockworks's rom Manager, which tells me that the recovery Programm couldn't be found at the boot prompt, opening the update.zip directly gives a message about something's failing with the certificates, ... an endless story
I come more and more to the guess, that all success messages for applying cyanogen to a milestone are only hoaxes, because someone couldn't tell the difference between a milestone and a droid on ebay and such.
I would be very thankfull for any answers, may they tell me that this is true, or that they have succeeded (and how!) Or even hand me the right guide. I have the feeling that I've allready read all the false ones
Sent from my Milestone using XDA App
Click to expand...
Click to collapse
OK, lets start over with your phone using some different method using my own guide. Do these steps to install CM 7 on your phone
1. Revert your phone back to stock
2. Install Androidiani OpenRecovery
3. Install Custom ROM
All from my guide: http://forum.xda-developers.com/showthread.php?t=983516
If you got any question ask them in the thread or PM me
1. Clockworks's rom Manager doesn't work on Milestone. I screwed that up too so don't feel too bad about that lol.
2. Start here http://forum.xda-developers.com/showthread.php?t=784750
You want CM so start with the CM for milestone thread that explains it directly.
From that page, get Androidian Open Recovery and prepare you SD Card.
3. Now follow instructions on this page: http://android.doshaska.net/rootable.
a. Install RSD Lite 4.6
b. Get the vulnerable recovery sbf and apply it with RSD Lite. (It's tiny... about 5mb)
c. Grab the "Disable_recovery_check_by_OTA" script and put it in sdcard/openrecovery/scripts folder.
4. Put CM6 or CM7 update.zip in the sdcard/openrecovery/updates folder.
5. Boot into Open Recovery. Apply the script from step 3
6. Install CM from the Apply Update menu.
edit: I didn't see post#2 when I hit send lol. I had started, went to do something and finished when I got back.
First of all: Thank both of you for your very nice (and unbelievable quick) replies!
Since you two suggest quite equal ways, and report that even this stupid EU-Brick is capable of running cyanogen, I'm quite enthusiastic, that I will succeed in the next days
I'll update the status here as soon as I git a new one.
eXtink said:
OK, lets start over with your phone using some different method using my own guide. Do these steps to install CM 7 on your phone
1. Revert your phone back to stock
2. Install Androidiani OpenRecovery
3. Install Custom ROM
All from my guide: http://forum.xda-developers.com/showthread.php?t=983516
If you got any question ask them in the thread or PM me
Click to expand...
Click to collapse
Hi eXtink,
I followed your guide and succeeded for an impressive long time. All went well:
I ...
applyed the german .sbf succeffully
booted / set up successfully Androidiani OpenRecovery 3.3
gained root
Installed Cyanogen 7 (0.08-11.03.16 RC3)
All these steps ran without displaying any error. But now, when I reboot the device, I only see the blue Cyanogen - Droid, skating within a blue circle. This hasn't changed several times for more than 10 Minutes now.
Can you tell what's wrong here?
do you see the first bounce again and again?
If it does, it's boot looping which isn't good.
But it usually takes a long time to load the first time...
So if it's not bootlooping, and it's going on for like 15 minutes, you can press shift alt delete to reboot and then try again and it should load quicker
No, it's not resetting or such, it just displays a smooth circle , but this rotates for over 10 Minutes (I rebooted it after that and re-issued a standard Froyo image onto the device after that.).
But you think I should wait for it to boot for ~15 minutes and then, while it still displays the loadspinner, reboot it? Did I understand you correct?
yeah, if it's not bootlooping and you're tired of waiting... just reboot it again.
Sometimes it just gags...
Say, did you feel the phone vibrate at all?
If you did, the lock screen was already up but hidden behind the animation
It godamn works !!! O.O Dunno what I've changed to make this habben, but when I try the exact eaqual steps again, it just works. Everything!
You two are my heroes!!! Thank you very much!
Cyanogenmod 7 on EU - Milestone - Working !!!
Cool Beans!
I'm glad that it worked for ya!
Bonus: this thread is a pretty good "how to"!
i must give it a try for my self. i need to install Cyanogenmod too cuz i had enough with the official one
guys i am not able to perform root, im stuch at the Open Recovery stage and it is unable to locate the Update.zip in the SD Card though it is on the root. there is a problem with the Cashe file :s. any help??
and the message is:
E: can't open cache/recovery/command
--install from sdcard..
finding update package..
openinng update package..
verifying update package..
E:EOCD marker occurs after Start of EOCD
E:signature verification failed
Installation aborted
Any Ideas??
3mar84 said:
guys i am not able to perform root, im stuch at the Open Recovery stage and it is unable to locate the Update.zip in the SD Card though it is on the root. there is a problem with the Cashe file :s. any help??
and the message is:
E: can't open cache/recovery/command
--install from sdcard..
finding update package..
openinng update package..
verifying update package..
E:EOCD marker occurs after Start of EOCD
E:signature verification failed
Installation aborted
Any Ideas??
Click to expand...
Click to collapse
Did you flash the vulnerable recovery?
If so, did you copy the openrecovery folder to the root of your sdcard?
Sent from my Milstone running CM7
Just put update.zip and OR on u SD card (directly). Tur off phone launch bootloader by RSD instal vulnarable recovery. Then turn off and then power+X update.zip and u are at home
thanks guys for your posts...
I already have placed the file on the root of the SD. but seems i had a problem with the ROM, when i tried using another ROM it worked. the problem is that when i was about to continuie Rooting the machine the Touch Screen is not working any more!!! seems i lost my piece!!
zeppelinrox said:
1. Clockworks's rom Manager doesn't work on Milestone. I screwed that up too so don't feel too bad about that lol.
2. Start here http://forum.xda-developers.com/showthread.php?t=784750
You want CM so start with the CM for milestone thread that explains it directly.
From that page, get Androidian Open Recovery and prepare you SD Card.
3. Now follow instructions on this page: http://android.doshaska.net/rootable.
a. Install RSD Lite 4.6
b. Get the vulnerable recovery sbf and apply it with RSD Lite. (It's tiny... about 5mb)
c. Grab the "Disable_recovery_check_by_OTA" script and put it in sdcard/openrecovery/scripts folder.
4. Put CM6 or CM7 update.zip in the sdcard/openrecovery/updates folder.
5. Boot into Open Recovery. Apply the script from step 3
6. Install CM from the Apply Update menu.
edit: I didn't see post#2 when I hit send lol. I had started, went to do something and finished when I got back.
Click to expand...
Click to collapse
Hey I'm new here and really want to be able to get Cyanogen 7 on my Milestone (Canadian version) My only question with your how to guide here is how to install open recovery on my phone. sorry I'm very new to this stuff and dont know a whole lot.
Led Head said:
Hey I'm new here and really want to be able to get Cyanogen 7 on my Milestone (Canadian version) My only question with your how to guide here is how to install open recovery on my phone. sorry I'm very new to this stuff and dont know a whole lot.
Click to expand...
Click to collapse
Once you flash the Vulnerable Recovery via RSD Lite, you want to place the AOR files that you can get from the sticky in Milestone development section onto the root of your SD card.
skadude66 said:
Once you flash the Vulnerable Recovery via RSD Lite, you want to place the AOR files that you can get from the sticky in Milestone development section onto the root of your SD card.
Click to expand...
Click to collapse
OK thanks! One more question though. is there a specific sbf I need? I have a vulnerable recovery sbf called "vulnerable_recovery_only_RAMDLD90_78.sbf" would this be the right sbf for a canadian Milestone on telus? if not I found a thread on this forum that has a link to a vulnerable recovery sbf for telus milestones (found here http://forum.xda-developers.com/showthread.php?t=983516 )
also my device wont show up in RSD, why would this be? I've tried hitting the show device button numerous times but nothing happens
Led Head said:
OK thanks! One more question though. is there a specific sbf I need? I have a vulnerable recovery sbf called "vulnerable_recovery_only_RAMDLD90_78.sbf" would this be the right sbf for a canadian Milestone on telus? if not I found a thread on this forum that has a link to a vulnerable recovery sbf for telus milestones (found here http://forum.xda-developers.com/showthread.php?t=983516 )
also my device wont show up in RSD, why would this be? I've tried hitting the show device button numerous times but nothing happens
Click to expand...
Click to collapse
Yes, the SBF that you have (vulnerable_recovery_only_RAMDLD90_78.sbf) is the one that you can use. I used it for rooting my Telus Milestone as well. When you want to revert back to stock, that's when you'll need a Telus-specific SBF.
skadude66 said:
Yes, the SBF that you have (vulnerable_recovery_only_RAMDLD90_78.sbf) is the one that you can use. I used it for rooting my Telus Milestone as well. When you want to revert back to stock, that's when you'll need a Telus-specific SBF.
Click to expand...
Click to collapse
k great thanks! so I got CM7 for milestone installed on my phone, and it loads up and everything but every few seconds i keep getting a message android.phone stopped responding. So I essentially cant do anything cause this message keeps coming up, also I'm getting a no service signal too, its not registering with Telus. Please help
I have been looking through the threads, and havent seen what I am looking for. So hopefully i will not get flamed to bad. I tried to install mikeymikes GR12, I got through the first stage of downloading the gingerbread rom to the phone through odin, but then it went south. I lost root and was unable to get back to the download screen. I then tried to use the all in one tool to root the phone, and that put me to the recovery screen where i could not use the ok button, just the volume up and down buttons. I just managed to get the download screen to come back, but i cant get anything else to work. Any suggestions on what to do, where to go from here.
Thank you for your help
I would go back to stock first. I believe your problem lies in the bootloaders. There are two bootloaders in the beginning and if you don't have the gingerbread ones installed, you won't install gingerbread properly.
I would use DesignGears One Click Odin to go back to stock and load the Froyo drivers. http://forum.xda-developers.com/showthread.php?t=731989. Make sure you open up Odin first before plugging in your phone, then hit the Start button.
Once that is done, you can try again, but read about getting the GB bootloaders installed properly before you try to flash a GB ROM. Any of the GB ROM instructions should get you there. Just make sure you know all the steps before you try it again.
Good Luck!!
I don't see why you would be flamed for your question. That is what Q&A is for and you are in a bad spot. The biggest thing to remember is to be as specific as possible when you post a question. This includes what you were trying to do, what steps you took, what was the result, when did the problem occur (which step) and what you have tried to do, if anything to fix it.
One more thing. It is always possible that the USB cable is bad or that the USB port you are plugging into (on the computer) isn't working properly. You might also want to plug into a different USB port.
Sorry these posts are broken up, but as I'm coming up with ideas, I'm posting.
Here's something you should try:
(I wrote this for Team Phoenix, hence the sig.. But it works the same with every ROM. There's a link to a very nice tutorial I suggest you follow).
http://forum.xda-developers.com/showpost.php?p=13503747&postcount=2
Hope it helps
You guys are awesome, Odin one click worked, It's on eclair, but it works! Thank you again
donkeyboy said:
You guys are awesome, Odin one click worked, It's on eclair, but it works! Thank you again
Click to expand...
Click to collapse
Glad it worked!
Make sure you read and understand before going forward with flashing
Otherwise... well.. I'll still be in here ready to help lol
BWolf56 said:
Glad it worked!
Make sure you read and understand before going forward with flashing
Otherwise... well.. I'll still be in here ready to help lol
Click to expand...
Click to collapse
Me too. If we can ... Remember not all things can be recovered from so please read everything twice before ever touching your phone.
10-4. My next question is: where do I get froyo from. Kies sees my eclair version as unregistered, so it wont update. And my ota sees an update is needed, but when i tried, the area im in has crappy signal, so the update failed and now i have to wait 24 hours to do it.
Any suggestions?
Thanks again
are you planning on flashing a custom rom?
if so updating to official froyo is A HUGE WASTE OF TIME
EDIT:are you Canadian by chance? if so check this thread:http://forum.xda-developers.com/showthread.php?t=979133
I only plan to root the official froyo right now, that is what I had before I jacked it up. I am not Canadian.
donkeyboy said:
I only plan to root the official froyo right now, that is what I had before I jacked it up. I am not Canadian.
Click to expand...
Click to collapse
Going on official froyo will get you the signature failed error (which you need the 3e recovery fix if you ever want to flash a custom ROM).
So, basically, if you want more than 2.2 official release. We suggest you don't update. If you're perfectly fine staying on 2.2 Froyo, then there's no problem lol
As for Kies, you shouldn't have any problem using Kies mini. Other than that, there is a 2.2 flash around here. I'm sure you'll find it doing a little search
I had root on my official froyo for a couple of months without a problem. Right now i cant get my phone to go into download mode, it only goes to the battery screen. If i can get to download i can make some headway
donkeyboy said:
I had root on my official froyo for a couple of months without a problem. Right now i cant get my phone to go into download mode, it only goes to the battery screen. If i can get to download i can make some headway
Click to expand...
Click to collapse
If the battery pull way isn't working. You could always go read on abd. It send SU commands and you could get your phone in downlaod mode that way.
Is there an easy way to get adb without getting the sdk. I downloaded the sdk and it keeps saying i need java, when i download the java crap it says the same thing.
donkeyboy said:
Is there an easy way to get adb without getting the sdk. I downloaded the sdk and it keeps saying i need java, when i download the java crap it says the same thing.
Click to expand...
Click to collapse
Did you reboot your pc?
Yes i did, no change
i believe you need microsoft .net framework installed also...
easy adb setup link in my sig.
files and everything needed to get going.
you may want to build a jig yourself or buy one online just in case:
MOD EDIT: No links to commercial products please.
I'm not sure whats going on with my D3. However, I have RSD and I have .890 and .959 downloaded as well as Fastboot.
What I want to do is just wipe the phone completely and just flash it like its a brand new phone.
Anyone know how to do so? Please post a link or instructions, I would greatly appreciate it.
atquick said:
I'm not sure whats going on with my D3. However, I have RSD and I have .890 and .959 downloaded as well as Fastboot.
What I want to do is just wipe the phone completely and just flash it like its a brand new phone.
Anyone know how to do so? Please post a link or instructions, I would greatly appreciate it.
Click to expand...
Click to collapse
http://goo.gl/7NoAv
Androidsims said:
http://goo.gl/7NoAv
Click to expand...
Click to collapse
Tried that. It keeps failing saying something about size was not as expected or something like that.
Redownload?
Avelnan said:
Redownload?
Click to expand...
Click to collapse
I have. MD5 sums match up each time. Should I try removing the ext sd card?
I would redownload everything and try agian
littleneutrino said:
I would redownload everything and try agian
Click to expand...
Click to collapse
Alright, attempt will be made again. Should I redownload RSD again or just the sbf's?
atquick said:
Alright, attempt will be made again. Should I redownload RSD again or just the sbf's?
Click to expand...
Click to collapse
Downloading the sbf's again. Went over to check and see if the phone was still on, The charging led is on, however the screen is off..
Held power, nothing. Held M + Power. Still nothing... Any thoughts on whats going on now?
I didn't see if you have pulled the SD card but yeah it can't hurt.
Sent from my DROID3 using XDA App
http://forum.xda-developers.com/showthread.php?t=1278056
Follow the first portion of the instructions on how to flash back to original 5.6.890. Note the making of a folder and it's name for the 890 flash.
Ignore the part about flashing the new ROM. These are the best instructions I've found so far for flashing back to stock via RSD lite.
Good luck, keep us posted.
Download and follow exactly and you'll be good to go.
Hope that helps.
Sent from my DROID3 using xda premium
wattnxt said:
http://forum.xda-developers.com/showthread.php?t=1278056
Follow the first portion of the instructions on how to flash back to original 5.6.890. Note the making of a folder and it's name for the 890 flash.
Ignore the part about flashing the new ROM. These are the best instructions I've found so far for flashing back to stock via RSD lite.
Good luck, keep us posted.
Download and follow exactly and you'll be good to go.
Hope that helps.
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
It keeps failing.
Step 3 mbmloader.bin
Step 4 mbm.bin
Step 8 logo.bin
Step 9 'lbl'
I'm stuck.
Let me do some looking when I get home tonight. I remember there being a file for certain versions of XP that helped some people and they couldn't flash without it.
I never had it happen personally, but I know those that did were terribly frustrated.
I also hear the 959 version is easier to flash for some reason. Never flashed that version, so this is only hear-say. But I know it did flash easier according to posts.
I will try to dig up a link for you.
i am getting the same thing also getting the bad CG boot.. now this may be a fix but idk how this guy got it it.. i have been asking eveywhere maybe you guys could help me... here is the thread http://forum.xda-developers.com/showthread.php?t=1248721
I found this by Psouza. He is likely the foremost expert on making things easy as far as unbricking your D3. Rumor has it he has a set of unbrick tools floating around this forum somewhere, though I haven't found it yet. Try in the Development thread, for sure it has to be there somewhere.
Post number 84
psouza4 said:
For those of you having problems flashing this and/or are suspicious of flashing ebr, mbr, and parts of the bootloader, you can selectively just flash the rest of it.
See attachment.
Click to expand...
Click to collapse
http://forum.xda-developers.com/attachment.php?attachmentid=715510&d=1315657647
Hope this helps.
I also saw that flashing the pre-installs file alone first helped someone. That file borked on me once, but I was able to adb it over and then execute it via adb to get my phone unbricked.
Please let us know what works for you, as all of this is a work in progress right now.
Good luck!
i don't know to much about adb and are looking for help on pre-installed files. I don't understand what that means or how to go about it? i also cant get past the bootloader screen, "invalid CG version". i can not boot up at all.
How bricked are you? can you boot into CWM? Are you able to boot into tools, or how far can you get?
What version were you running? 5.959 (stock) or 6.890 OTA or Leaked OTA or Soak test (all the same as far as 6.890 goes).
i can get into boot tools and just tryed another flash got to step 6 till it failed instead of 3.. I'm running stock. Cannot get passed boot tools... scratch all that just tried to flash again just on the off chance it mnight work and i got it. Going to try and re-root and CWN recovery with sdteel froids rom... will keep you in the loop
Awesome!!
Here is the link about the adb commands for preinstall.sh
http://forum.xda-developers.com/showpost.php?p=17196391&postcount=88
It helped me when I borked my leaked update. I ran into the same problem as limaxray did with too many files in /system. So make sure you clean out any apps you made into system apps before trying the update via the standard update route, and that all stock system apps are in place and properly named.
I had to remove some that updated partially with the leaked update when mine borked. I used the posted system dump to push them to the phone and then the update ran properly and updated them anyhow.
If for some reason re-rooting doesn't work for you. Go to /system/bin and remove su, busybox. Do the same in /system/xbin. For some reason if you already have them in there when you run the process, it will say success but no root after reboot. My 2c as it happened to me. You do not need to remove superuser.apk, but you will have to update it in the market after you re-root.
Congrats!!
I see now too there is a fastboot and moto-fastboot. moto-fastboot has worked for some who had issues from what I've found.
Keep us posted, and smile knowing you've recovered from a bork; none of us got where we are without doing it at least once, so you're in good company.
re-rooted and installed bootstrap, just got steel droid all loaded up and all is good.... thanks for your speedy responses and detailed instructions and links. I realy think all that happened was i took everything aet it sone last time tried to flash and it went threw. All i used was RSD lite and flashed the 8.6.590 fast boot file and after a several retries it went threw. If anyone needs help on this i will post the file links if you need the ones i used
(Obvious Noob warning---) A friend helped me root my Thrill, install ClockworkMod Recovery, and then install CM7 on my Thrill. But I would like to try the LG GB release. Is it necessary to backtrack all the way back to stock to do this (i.e. reinstall the stock ROM, reinstall the stock recovery, unroot, etc.)?
My friend tried using the LG upgrade tool on his LG phone without going back to stock and ended up bricking it. He says that usually within a few days of release, a CMR compatible zip file (usually already rooted) appears here on XDA (I haven't seen it), which makes things easier (but obviously he didn't wait for it himself).
Will a zip be possible for the Thrill GB? (The file seems quite large (420MB), so I'm guessing there is a lot of media included.) Or should I just bite the bullet and backtrack?
Rick
Rick Tillery said:
(Obvious Noob warning---) A friend helped me root my Thrill, install ClockworkMod Recovery, and then install CM7 on my Thrill. But I would like to try the LG GB release. Is it necessary to backtrack all the way back to stock to do this (i.e. reinstall the stock ROM, reinstall the stock recovery, unroot, etc.)?
My friend tried using the LG upgrade tool on his LG phone without going back to stock and ended up bricking it. He says that usually within a few days of release, a CMR compatible zip file (usually already rooted) appears here on XDA (I haven't seen it), which makes things easier (but obviously he didn't wait for it himself).
Will a zip be possible for the Thrill GB? (The file seems quite large (420MB), so I'm guessing there is a lot of media included.) Or should I just bite the bullet and backtrack?
Rick
Click to expand...
Click to collapse
I'm assuming that the official update method was used.
Just use this method after downloading the update. No bricking.
SEE THREAD
The Dark Lestat said:
I'm assuming that the official update method was used.
Just use this method after downloading the update. No bricking.
SEE THREAD
Click to expand...
Click to collapse
Thank you for your help!
Rick
Trojan?
Sorry, but as a noob, I can't post in that other thread.
It seems that the shttp3.exe in the LG Flash Package triggers Symantec's trojan detection. Some searching seems to indicate (assuming I'm reading all the cryptic virus sites correctly) that there is something to this, although it seems that different scanners find different trojans/viruses (can't post the link, but Google for "shttp3.exe" and "trojan"). I also found that the web site for this utility is blocked at work, because it's a "malicious site."
Has anyone seen this? Has anyone been able to verify/refute this?
Rick
There is no virus, Lestat would never do that
Sent from my LG-P925 using XDA
Just my .02 .....Get rid of Symantec !! They are known for scaring people into a virus frenzy.. Yes, it is possible that it is seeing it as a potential virus because shttp is a workaround from the usual porting of windows ip services. ...
Correct me if i'm wrong somebody please !!
Get yourself Comodo and save your money...
Regards,
Dwayne
PS: somebody on here has written a script that just uses shttp temporarily while
your doing the flash procedure, and then reverts your host files back automatically after your done. You should try it.
dwaynedman said:
Just my .02 .....Get rid of Symantec !!
Click to expand...
Click to collapse
Symantec isn't really a choice on work PC.
Get yourself Comodo and save your money...
Click to expand...
Click to collapse
I'm sorry I can't give the link yet, but if you'll Google you'll see Comodo classifies shttp3.exe as "ApplicUnwnt.Win32.ServerWeb.SmallHTTP.~A" or "UnclassifiedMalware" (I guess depending on the version). A number of scanners find issues with shttp3.exe. I'm not saying it is infected, only that it is doing something suspicious.
Rick
Rick Tillery said:
Sorry, but as a noob, I can't post in that other thread.
It seems that the shttp3.exe in the LG Flash Package triggers Symantec's trojan detection. Some searching seems to indicate (assuming I'm reading all the cryptic virus sites correctly) that there is something to this, although it seems that different scanners find different trojans/viruses (can't post the link, but Google for "shttp3.exe" and "trojan"). I also found that the web site for this utility is blocked at work, because it's a "malicious site."
Has anyone seen this? Has anyone been able to verify/refute this?
Rick
Click to expand...
Click to collapse
shttp3.exe is in no way a virus. I've scanned with AVG and MalwareBytes Anti-Malware and they check out good.
Back to square one
OK, I seem to be stuck.
With paranoia in tow, I decided to take the long way back to stock. Unfortunately, when I tried to restore the backup of my stock image I made to SD card after installing CMR, the md5 checksum failed. I'm not sure what I can do about this.
So ok, I tried following the above link. The first step is to ensure the su binary is up-to-date. But when I tried this, I get a failure downloading the manifest. This is true for WiFi and HSPA+. I Googled and found a suggestion to delete the su binary. But that didn't help (I'm not sure how it would have helped anyway).
So back to the original question. Can I use the LG upgrade process to upgrade without going backwards (as you can see above, I can't) without bricking the phone? Can I start at step 3 in the link above and succeed?
Rick
The Dark Lestat said:
shttp3.exe is in no way a virus. I've scanned with AVG and MalwareBytes Anti-Malware and they check out good.
Click to expand...
Click to collapse
Thank you, sir. I hope it didn't seem accusing.
Rick
Rick Tillery said:
Thank you, sir. I hope it didn't seem accusing.
Rick
Click to expand...
Click to collapse
It's cool, my friend.
Sent from my Samsung Galaxy S II w/ CM9
Rick Tillery said:
OK, I seem to be stuck.
With paranoia in tow, I decided to take the long way back to stock. Unfortunately, when I tried to restore the backup of my stock image I made to SD card after installing CMR, the md5 checksum failed. I'm not sure what I can do about this.
So ok, I tried following the above link. The first step is to ensure the su binary is up-to-date. But when I tried this, I get a failure downloading the manifest. This is true for WiFi and HSPA+. I Googled and found a suggestion to delete the su binary. But that didn't help (I'm not sure how it would have helped anyway).
So back to the original question. Can I use the LG upgrade process to upgrade without going backwards (as you can see above, I can't) without bricking the phone? Can I start at step 3 in the link above and succeed?
Rick
Click to expand...
Click to collapse
Is it safe to ignore the su version update?
Short of this, can I override the MD5 checksum? I realize that image could be corrupt, but if I'm just going to replace it with the GB release, does that matter?
Rick
You should just put your phone in recovery mode and update through the tool
with your IMEI #. It will give you the latest update !
If you need some help on that I think Lestat or somebody has a write-up
on doing this.
Good luck,
Dwayne
dwaynedman said:
You should just put your phone in recovery mode and update through the tool
with your IMEI #. It will give you the latest update !
If you need some help on that I think Lestat or somebody has a write-up
on doing this.
Good luck,
Dwayne
Click to expand...
Click to collapse
Can you be a bit more specific?
1. By "recovery mode," do you mean into ClockworkMod Recovery, or I should revert to stock (I made a copy of it after I rooted the stock ROM, but before I installed CMR)?
2. By "the tool," do you mean the official LGMobile Software Update, or the LG Flash Package referenced in the link above?
3. By "latest update," do you mean the file directly from LG, or the copy (v20p) linked from the link above?
4. If the latter in both previous questions, which set of steps do I need to follow from the above link? Can I do only 3 (LG Flash Tool), or do I need to follow 1 (Recovery Manager), 2 (Returning to Stock), and 3?
My friend had a different LG phone, with ClockworkMod Recover and CM7 installed. He reverted the CM7 to stock, but did not replace CMR with the stock recovery. Then he used the official LG upgrade method and bricked his phone. I'm trying to avoid this.
Are you saying I don't have to worry about this on the LG Thrill 4G? Can I go straight from the current CMR+CM7 configuration to the LG GB release using the official LG process?
If you mean I should use a different process, can you point me to it? As I mentioned, I run into dead-ends using the method linked above. And I'm not even sure whether I should be doing steps 1, 2 and 3, or if I should just use step 3.
Any and all help is appreciated, but I guess I don't understand the shorthand you're using here, so if you could be a bit more specific, I wouldn't feel so lost.
Rick
Rick Tillery said:
Can you be a bit more specific?
1. By "recovery mode," do you mean into ClockworkMod Recovery, or I should revert to stock (I made a copy of it after I rooted the stock ROM, but before I installed CMR)?
2. By "the tool," do you mean the official LGMobile Software Update, or the LG Flash Package referenced in the link above?
3. By "latest update," do you mean the file directly from LG, or the copy (v20p) linked from the link above?
4. If the latter in both previous questions, which set of steps do I need to follow from the above link? Can I do only 3 (LG Flash Tool), or do I need to follow 1 (Recovery Manager), 2 (Returning to Stock), and 3?
My friend had a different LG phone, with ClockworkMod Recover and CM7 installed. He reverted the CM7 to stock, but did not replace CMR with the stock recovery. Then he used the official LG upgrade method and bricked his phone. I'm trying to avoid this.
Are you saying I don't have to worry about this on the LG Thrill 4G? Can I go straight from the current CMR+CM7 configuration to the LG GB release using the official LG process?
If you mean I should use a different process, can you point me to it? As I mentioned, I run into dead-ends using the method linked above. And I'm not even sure whether I should be doing steps 1, 2 and 3, or if I should just use step 3.
Any and all help is appreciated, but I guess I don't understand the shorthand you're using here, so if you could be a bit more specific, I wouldn't feel so lost.
Rick
Click to expand...
Click to collapse
Remove your battery and keep the phone unplugged
Launch the mobile updater tool
Hold the volume+ button plug the phone in and keep holding the volume+ till the computer downloads the drivers your phone is now in download mode
Once the phone is picked up go to customer support on the LG updater tool and click on recovery phone put your imie number in click check (make sure its the right model) an let the updater tool do its job. Once its done flashing launch into recovery volume- plus power plus 3D button do a complete wipe and factory reset and reboot your phone ... you'll lose cwm and root and be back to full stock
Sent from my LG-P925 using XDA
Bricked?
No joy. Following the steps, the upgrade stopped at 6%. Trying a number of times, it eventually forced me to exit the program (no more restarts). Rerunning the updater (and downloading the 420 MB image yet again on a VERY slow connection) I tried again and again, with different combinations of battery and plug order with power and volume buttons, but nothing worked. Checking elsewhere I found some issues had been reported with Windows Vista/7, so I tried on an XP machine. Now the "Start Updating" bar is red (it was always gray with W7). But now when I try to restore (or even update for that matter), it asks for my S/N (it never did that before) and then says it is "no longer able to upgrade." Reading around, it seems this is an indication of the device being bricked.
Rick
It sounds like you are very close to getting it working Rick.
My update did the same thing, looped over and over until it
finally kicked me out. Just plugging and unplugging the phone etc....
And when my update stuck at 6% the last time, i took my battery out and then in real quick and that seemed to work.
Does the phone still vibrate when you plug the usb cable into it while holding volume..? If it does then I highly doubt that your phone is bricked, just in a semi flashed state....No worries
Should Rick be trying to run LG Updater as administrator ? I didn't, but it might not hurt.
Regards & Luck,
Dwayne
http://forum.xda-developers.com/showthread.php?p=22417769
Have you tried this yet cause if you can get the LG logo to come up then you can reflash the phone and get it working send a pm to the dark lestat he may be able to team viewer you and help you out
Sent from my ****ty supported LG Thrill
dwaynedman said:
It sounds like you are very close to getting it working Rick.
Click to expand...
Click to collapse
I wouldn't have believed you early this morning, but now maybe...
My update did the same thing, looped over and over until it
finally kicked me out. Just plugging and unplugging the phone etc....
And when my update stuck at 6% the last time, i took my battery out and then in real quick and that seemed to work.
Click to expand...
Click to collapse
I tried a bunch of different combinations...none seemed to make the app happy. I finally punted Windows 7 and moved to an XP machine, only to get the "no longer able to update" message. At that point I assumed I was screwed (effectively bricked).
Does the phone still vibrate when you plug the usb cable into it while holding volume..? If it does then I highly doubt that your phone is bricked, just in a semi flashed state....No worries
Click to expand...
Click to collapse
It never really vibrated, but I was able to get back into CMR. Unfortunately NONE of my backups work at all. They all have MD5 checksum failures. I tried a trick I found online and got past that step, only to have it say a failure restoring /system. So much for CMR.
JReeher said:
http://forum.xda-developers.com/showthread.php?p=22417769
Have you tried this yet cause if you can get the LG logo to come up then you can reflash the phone and get it working send a pm to the dark lestat he may be able to team viewer you and help you out
Click to expand...
Click to collapse
Which step? As I mentioned above, I can't even get the first step of the first section (updating the su binary). And if I start at the 3rd section, Symantec prohibits me from using shttp3.exe (I tried to unquarantine it, but it gives a permission error, even as Administrator, when I try to run it), so I'll have to use a different machine.
I was able to reinstall the CM7 3/15 release, so that's something. I was going to restore the stock recovery backup I made, but even that doesn't seem to work. I'm having issue with backups :-(
Rick
i have never been able to restore a backup. i dont know why... but i have tried several times in several different instances.
---------- Post added at 11:56 AM ---------- Previous post was at 11:50 AM ----------
rick tillery, if you want to get your phone back to alive and well i'd suggest doing this:
http://forum.xda-developers.com/showthread.php?t=1558723&page=3
4th post i think
Okay, so now we have 3 Atrix HD's in the house and except for the unremoveable battery thing, and the short "battery life" when actively using it, I'd say we pretty much love them. However, I decided to remove some apps, etc. and managed to get my messages, camera and gallery to the "not working" and basically non-existent point. Now on startup I'm getting the Android is Updating message with the never-ending swirl of Starting Apps... I'm positive I've waited long enough as I set it down and went back to bed just to wake up and still see it.
Info - phone IS rooted
running the "jellybean" update
Unfortuanately a couple weeks ago, I UNCHECKED the sync photots for both facebook and gmail, so there are pictures I really don't want to lose.....
I'm definitely not a "pro" like lots of them up here, but am capable of following directions. I'm pretty sure I have to "unroot" my phone via USB/SD card through my laptop....Any help would be greatly appreciated... and the more specific the directions the better!! :cyclops: LOL... Thanks so much.
/COLOR]
Sounds like you deleted a critical OS file. You need to flash back to stock again. Is your boot loader locked or unlocked?
Don't remeber...
ai6908 said:
Sounds like you deleted a critical OS file. You need to flash back to stock again. Is your boot loader locked or unlocked?
Click to expand...
Click to collapse
I Don't rememer if I unlocked the bootloader. Is there a way to check? Thanks.
Follow what's in the website to reload your stock image...
http://www.andromods.com/tips-trick...-qinara-stock-original-firmware-fastboot.html
ai6908 said:
Follow what's in the website to reload your stock image...
http://www.andromods.com/tips-trick...-qinara-stock-original-firmware-fastboot.html
Click to expand...
Click to collapse
I've been trying and I've fallowed everything to the T but everytime it says it falls.
I'm not sure...I have used it before and was able to restore...are you sure it's not a hardware issue?
Sent from my HTC_Flyer_P512_NA using xda app-developers app
Okay, here's where we're at.... it is no longer frozen on that screen and goes thru the setup w/ my gmail, etc.... but then I have a black screen (except for the top row icons...). I can pull down the settings menu and see everything there, but I have no "homescreen"....It's black. It seems like we're in the right direction and I know it's not dead. Anything??
Also wanted to thank you for the help. This place is ALWAYS amazing....
Hey, my son and I are wondering since it's already running 4.1.1 and we can't downgrade, what about flashing a custom rom? Will that flash a totally complete, full home page and everything?? Just a thought.
While trying to search for answers I came across a "xoom forums??" post with a tablet that was doing exactly the same thing....multiple people had that problem, but doesn't seem to have been answered...... not sure if I'm suppose to post links to that or not, but at least I know I'm not alone.....
If you're rooted, than I'm assuming ADB debugging is on. You should be able to unlock your boot loader and load CWM recovery. From there you can wipe cache and dalvik cache. If that doesn't help, you can reflash a stock ROM zip from Skeevys thread. Flashing a zip won't touch your SD card
There is official 4.1.1 available...you can try flashing that...you dont need to downgrade.
Okay, my son installed safetystrap (whatever that is...lol) and when you click Operating system, it says "there is no operating system installed are you sure you want to reboot????
Is this fixable?
Note: We have two other identical Atrix HD's in the house if that helps for any reason.....
Well that's what we are trying to figure out is how to install OS...Lol..
Try install system using fastboot... Look for skeevedudes guide...its in this forum somewhere...
Sent from my MB886 using xda premium
LOL....okay, so do yoiu see why my son says I'm not "ALLOWED" to have a rooted phone if this happens again..... Guess I was just glad to SEE it written out, so that it's a little more def what's going on - but I'm sure everyone up here (except me) already knew that!!!
He's not around today, so my phone is just "sitting" saying "creating rom slot" but never gets off that screen. The good thing is that we can see it's actually charging and we weren't sure before....... Does this sound like something that will eventually be repairable??
You have a soft brick...yes it is fixable...
Okay, thought I had already posted this before but I guess I never hit the submit ....
Before safety strap was installed, we could get the phone (minus the homescreen and os) to come on....the settings, wifi etc.....No we can't seem to get to that point with the safetystrap on. It just goes completely blank and won't let safestrap connect to the computer via usb.
Apparently there is also no way to remove SS without an opperating system. This doesn't sound promising.....ugggg..... I so want my phone back.
Any help would be greatly appreciated.
OK dude. Follow my instructions.
Hold down power and both volume buttons all at once until the phone screen turns black, then continue holding the volume buttons. You will get a menu. Go to AP fastboot mode using the volume down button, select it with the volume up button. Plug your phone into your computer with a data cable. Download RSD lite and the MOTOROLA drivers from the MOTOROLA website. Install both. Download the 4.1.1 sbf file for your phone, there is a thread for it here in the AHD forum. Its a zip file, extract it to your desktop. Open RSD lite, click the browse for file button, select the XML file inside the folder you just unzipped. Hit flash. If you get any errors, let me know I'll send you a different XML file with the getvar lines removed.
Okay, will get it started..... Thanks so much. My son has been working on this for hours and hours. You have no idea how much I appreciate this place and everyone who helps out!! You guys rock! Will let you know what we get.
Here is the website for what youngunn mentioned...
http://www.andromods.com/tips-trick...-qinara-stock-original-firmware-fastboot.html
[FONT="Comic [SIZE="3"]Okay, my son (BlackestPain) is too new here to post the picture links, so I copied and pasted. They're just downloads from his camera pictures. This is where we are right now after following suggestions....[/SIZE]MS"][/FONT]
Okay, here is what I've (chixwithkidz5' son) tried.... Please cut me some slack because I haven't been doing this stuff long....
Getvar file
Getvar removed
RSD Lite connected
RSD Lite failed
\
***** this is what the phone reads after everything
What am I missing ? Thanks - I can use all the decent help I can get.