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
Related
I have a Milestone which I rooted last week. I am from Romania.
I have overclocked it and it ran smoothly. Yesterday I was playing with the governors modfying files inside the system.
I renamed the mot_boot_mode file under system/bin in mot_boot_mode.bin and added another mot_boot_mode that had these first lines inside it "#!/system/bin/sh
export PATH=/system/bin:$PATH
#run the original binary
mot_boot_mode.bin"
I rebooted and got stuck into the M loop.
What can I do? Please help me!
vladstercr said:
I have a Milestone which I rooted last week. I am from Romania.
I have overclocked it and it ran smoothly. Yesterday I was playing with the governors modfying files inside the system.
I renamed the mot_boot_mode file under system/bin in mot_boot_mode.bin and added another mot_boot_mode that had these first lines inside it "#!/system/bin/sh
export PATH=/system/bin:$PATH
#run the original binary
mot_boot_mode.bin"
I rebooted and got stuck into the M loop.
What can I do? Please help me!
Click to expand...
Click to collapse
If you can't access recovery, then go into fastboot and reflash a sbf.
You likely did not set proper permissions for the new script.
This is not serious trouble, don't worry. If you are rooted I assume you have vulnerable recovery flashed in. Boot in openrecovery and fix the mess over adb or directly from the phone. If you are totally lost, either restore your nandroid backup (you did it right? ). Altternatively reflash the whole SBF as poster above suggested.
i didnt have a vulnerable recovery flashed in...nor a nandroid backup...but i have followed the "back to stock" thread and flashed an original sbf...I set the right permission for the file before rebooting...cant figure out what was wrong... none the less i had a titanium backup done 2 days ago which worked like a charm....
Please advise me guys into doing a nandroid backup and flashing a vulnerable recovery
Sent from my Milestone using XDA App
What advise do you need? There is an in depth instruction on top.
However, it is not very complicated, i can tell since I'm into this about 1 month and succeeded with a minimum or even less amount of knowhow.
The vulnerable recovery is working for all boot loader versions and does allow to access the update.zip.
You'll need either RSD Lite or sb_reflash, depending on your OS. So boot into bootloader mode (holding up the d-pad on start), apply the vulnerable recovery sbf and fire up your update.zip once thee flashing is done. (assuming you have followed the instructions on how to prepare your sdcard for OpenRecovery, eg. the G.O.T distro requires a differnt structure)
If you get a checksumm error, check out the log files and modify the file, or use a script to recalculate the checksum. But this is rarely the case.
Ohh.. and talking about "original sbf", you might want to read the difference between Service and "normal"
MenoDev said:
What advise do you need? There is an in depth instruction on top.
However, it is not very complicated, i can tell since I'm into this about 1 month and succeeded with a minimum or even less amount of knowhow.
The vulnerable recovery is working for all boot loader versions and does allow to access the update.zip.
You'll need either RSD Lite or sb_reflash, depending on your OS. So boot into bootloader mode (holding up the d-pad on start), apply the vulnerable recovery sbf and fire up your update.zip once thee flashing is done. (assuming you have followed the instructions on how to prepare your sdcard for OpenRecovery, eg. the G.O.T distro requires a differnt structure)
If you get a checksumm error, check out the log files and modify the file, or use a script to recalculate the checksum. But this is rarely the case.
Ohh.. and talking about "original sbf", you might want to read the difference between Service and "normal"
Click to expand...
Click to collapse
Whats the difference?
By the way...I didnt had to prepare the sd card in a special way or something...Nor to format it in a particular way...It was pretty easy the whole process though...
Now I have switched to GOT 2.2.1 Froyo with CM6 mod but I'm very dissapointed on the battery life... Think I'm gonna try other 2.2 Roms with 2.1 kernel...
Thanks for your reply!
Know what I observed in my case? Installing the 2.2.1 firmware with no "got-fix" and no root makes my battery last very long
Sent from my Milestone using XDA App
MenoDev said:
Know what I observed in my case? Installing the 2.2.1 firmware with no "got-fix" and no root makes my battery last very long
Sent from my Milestone using XDA App
Click to expand...
Click to collapse
what do you mean by "no got-fix"
Please let me know....And also...Did you have the GOT 2.2.1 where the battery last less?
vladstercr said:
what do you mean by "no got-fix"
Please let me know....And also...Did you have the GOT 2.2.1 where the battery last less?
Click to expand...
Click to collapse
You get the G.O.T 2.01 OpenRecovery Version along with the Firmware files.
Usually one supposed to boot into recovery and apply some mods, the first one would be fix 2.2.1 issues... and so on.
I was lazy and didn't, but simply flashed the Firmware. And to my surprise the battery was lasting longer.
But you know, I can't tell if it's depending on the Distro or whatever. Hovewer, I'm not that of a version junkie, rather looking for a decent distribution, and luckily i found one. Even if it was 2.0 it would have been cool for me. Now 2.3 resp. 3.0 is around the corner, then the whole race starts again...
vladstercr said:
Whats the difference?
By the way...I didnt had to prepare the sd card in a special way or something...Nor to format it in a particular way...It was pretty easy the whole process though...
Now I have switched to GOT 2.2.1 Froyo with CM6 mod but I'm very dissapointed on the battery life... Think I'm gonna try other 2.2 Roms with 2.1 kernel...
Thanks for your reply!
Click to expand...
Click to collapse
Btw... they announced froyo for next week for the milestone in this forum.. so we hopefully will all be fine, if not, we will still have to deal with the fact that Android is very nice, but not yet rock solid
MenoDev said:
You get the G.O.T 2.01 OpenRecovery Version along with the Firmware files.
Usually one supposed to boot into recovery and apply some mods, the first one would be fix 2.2.1 issues... and so on.
I was lazy and didn't, but simply flashed the Firmware. And to my surprise the battery was lasting longer.
But you know, I can't tell if it's depending on the Distro or whatever. Hovewer, I'm not that of a version junkie, rather looking for a decent distribution, and luckily i found one. Even if it was 2.0 it would have been cool for me. Now 2.3 resp. 3.0 is around the corner, then the whole race starts again...
Click to expand...
Click to collapse
Yes... I never applied those fixes too... Still the battery last very little time...
As an example:
Before I went to sleep last night the battery was fully charged...no apps running...3g disabled...everything disabled...phone idle for 7 hours...and when I woke up and check... I got 60% of the battery...
Thats frustrating...
I must admit I have the Cyanogenmod running...Would this be the issue?
hey friends,
i followed two links to root & install cusotm roms. Both in vain. I bought my milestone in India(Asia).
Links i followed are
http://forum.xda-developers.com/showthread.php?t=848951&highlight=nandroid
http://www.addictivetips.com/mobile/how-to-root-motorola-milestone/comment-page-1/#comment-38384
error pictures are below... Both the links got struck at this place.
http://cid-8399281430e1b99d.office.live.com/self.aspx/.Public/270220111080.jpg
http://cid-8399281430e1b99d.office.live.com/self.aspx/.Public/270220111079.jpg
please help me out.
-Prabhu.
Please let me know, if there is any other place to chat milestone root errors etc.
-Prabhu
tried thrice, thinking i didnt reflash correctly
tried thrice, thinking i didnt reflash correctly. All the three times i got passed message. But still wont install the update.zip.
-Prabhu
SBF file
please recommend the right SBF file for me too.
URL>>and-developers.com/sbf:milestone
phone works normal, as far as i checked
phone works normal, as far as i checked.
it booted back into the eclair. everything was in place.
recommend a root, custom rom guide for newbie
please recommend a root, custom rom guide for newbie.
hope that will help me get froyo on my MSTN. really tired of waiting for a official update. Everytime its a pain, even to check e-mails... always no space...
-Prabhu
kmpksprabhu said:
please recommend a root, custom rom guide for newbie.
hope that will help me get froyo on my MSTN. really tired of waiting for a official update. Everytime its a pain, even to check e-mails... always no space...
-Prabhu
Click to expand...
Click to collapse
Use the following thread and ask specific questions about which step doesnt work for you...
http://forum.xda-developers.com/showthread.php?t=932196
Sent from my Milestone using Tapatalk
kmpksprabhu said:
hey friends,
i followed two links to root & install cusotm roms. Both in vain. I bought my milestone in India(Asia).
Links i followed are
http://forum.xda-developers.com/showthread.php?t=848951&highlight=nandroid
http://www.addictivetips.com/mobile/how-to-root-motorola-milestone/comment-page-1/#comment-38384
error pictures are below... Both the links got struck at this place.
http://cid-8399281430e1b99d.office.live.com/self.aspx/.Public/270220111080.jpg
http://cid-8399281430e1b99d.office.live.com/self.aspx/.Public/270220111079.jpg
please help me out.
-Prabhu.
Click to expand...
Click to collapse
hey, thanks for the reply.
the above links shows the error msgs.
i got struck when i selected the "apply update:update.zip"
it gives me the above posted error msgs. i have given those links
-Prabhu
kmpksprabhu said:
hey, thanks for the reply.
the above links shows the error msgs.
i got struck when i selected the "apply update:update.zip"
it gives me the above posted error msgs. i have given those links
-Prabhu
Click to expand...
Click to collapse
Looks like you made a mistake in 1 of 2 places
1) Using RSD lite for installing vulnerable recovery (did it flash ok?)
2) Or you did not install OpenRecovery correctly.
#1 requires you to restart with RSD
#2 requires checking that you did the Following:
OpenRecovery zip file contains 2 things : an update.zip and an OpenRecovery folder. You need to extract (copy) these 2 elements to the root of you SD card.
So in your SDCard you should have an update.zip FILE and an OpenRecovery FOLDER.
Then, from the standard recovery menu, you choose apply update.zip. This will start the OTHER recovery you wish to use (to install ROM). The ROM zip files belong (unextracted) in the OpenRecovery/updates subfolder.
Does this make sense?
yes RSD showed me PASS then only i closed it. After which i switched off the phone and then went to the "apply update..." menu.
i also do had update.zip, openrecovery and openrecovery-cfg all three folders.
so do you think is there any other place to go wrong?
moreover the universal androot's APK doesnt look like an setup file in milestone, any idea about it ?
now, let me try the link you gave me.
-Prabhu
kmpksprabhu said:
yes RSD showed me PASS then only i closed it. After which i switched off the phone and then went to the "apply update..." menu.
i also do had update.zip, openrecovery and openrecovery-cfg all three folders.
so do you think is there any other place to go wrong?
moreover the universal androot's APK doesnt look like an setup file in milestone, any idea about it ?
now, let me try the link you gave me.
-Prabhu
Click to expand...
Click to collapse
Try the link, follow the guide and ask again.
Honestly, you don't really need to root using those methods.
The vulnerable recovery + OR is all you need. Most the ROMs you will install have root built-in.
I would make sure I download ANDROIDIANI recovery (it is generally considered the best for Milestone.
Thanks Caz666, the link you gave me worked like a magic. Now i am done with root and cyanogenmod 6.1.2.
Post root and MOD-cyanogen6.1.2
hey Caz666, thanks again. i did the root and then used the update.zip>>cyanogenmod6.1.2.
but now what should i do to get the market ? email ? and other stuffs in place.
my questions is>>> whats next now that i have installed 6.1.2.... i am seeing something like android applications ? (<< is there a guide on this)
-Prabhu
kmpksprabhu said:
hey Caz666, thanks again. i did the root and then used the update.zip>>cyanogenmod6.1.2.
but now what should i do to get the market ? email ? and other stuffs in place.
my questions is>>> whats next now that i have installed 6.1.2.... i am seeing something like android applications ? (<< is there a guide on this)
-Prabhu
Click to expand...
Click to collapse
also please tell me what is this "remember to wipe messgae all about" please explain, that too. and what exactly i should wipe ?
Please take your time to reply... i am struck at work too... so have to do the work or flash reflash only after i am back at home in another 4-5 hrs . Thanks again for the help.
-Prabhu
kmpksprabhu said:
also please tell me what is this "remember to wipe messgae all about" please explain, that too. and what exactly i should wipe ?
Please take your time to reply... i am struck at work too... so have to do the work or flash reflash only after i am back at home in another 4-5 hrs . Thanks again for the help.
-Prabhu
Click to expand...
Click to collapse
I am not certain i understand your questions
1. Wiping : you need to wipe all data (factory reset) if you switch to a different ROM. You only need to wipe dalvik cache and /cache if you upgrade to a newer CM6.
2. ?
Sent from my Milestone using Tapatalk
First of all thanks for all the help.got everything installed. My mile is working awesome.
When should I do wipe factory reset?
Next how can I get black colored status bar.top one.
Lastly if I have to install a new Tom should I
1. Redo sbf?flash ie firmware flash right?
2. Redo a open recovery. Is there a alternate to this?
3. Guess I can follow the rest of the instructions specific to that rom.
Sent from my Milestone using XDA App
Thanks all. Successfully installed cm6.1.2.
Sent from my Milestone using XDA App
kmpksprabhu said:
First of all thanks for all the help.got everything installed. My mile is working awesome.
When should I do wipe factory reset?
Next how can I get black colored status bar.top one.
Lastly if I have to install a new Tom should I
1. Redo sbf?flash ie firmware flash right?
2. Redo a open recovery. Is there a alternate to this?
3. Guess I can follow the rest of the instructions specific to that rom.
Sent from my Milestone using XDA App
Click to expand...
Click to collapse
1)
You should do a full wipe only when switching to a REALLY different ROM. Upgrades and version updates do not require this. Also, if you are trying out another CM6 based ROM, you *may* be able to avoid this.
If you are not sure, you should wipe. With options like apps2ext or Titanium backup, wiping is not such a big deal.
2) You do not need to do #1 or #2 for a new ROM. Only flash SBFs if you want to try a stock ROM (like when Motorola releases Froyo) or you have serious issues with the phone. OpenRecovery only needs to be reinstalled when there is a new version
3) To install a new ROM, wipe from inside OR. The 3 options are there. Always wipe Dalkvik Cache and /cache partition when applying themes or updating ROMs. Wipe data for NEW Roms
Before you tell me to 'Google it' (which I have, and leads me to 1000 posts of people telling other people with the same problem to 'Google it'), please read.
I will PayPal anyone $20 with working instructions of how to resolve this
Phone: HTC Hero w/ chin
Carrier: Alltel
Story:
Switched from WM6 Palm Treo Pro to HTC Hero. Came with 2.1 and needed apps2sd. Want CM7 stable.
-Rooted using AndRoot.
-Installed SuperUser and Root Checker. Root Checker said I was good to go. SuperUser would not show any apps in the list this whole time.
-Installed Titanium Backup which said I needed BusyBox, but it would fail to install. Tried to install busybox and it said I was not rooted. Alright...
-Installed ClockworkMod and flashed recovery. Tried to reboot into clockwork recovery, but when I clicked it, it did nothing. When I clicked rom from sd card, and clicked the CM7, it said 'going to reboot now' but again, nothing happened.
I booted into recovery manually, but it was still in Android system recovery. Apparently there was some sort of rooting problem, so I tried z4root. Permanent root was stuck on 'rebooting', and temporary root said successful, but something was still wrong as BusyBox installer would say I was not rooted, and SuperUser app didn't show any programs to allow permissions.
I turned the phone off, and back on. It goes to the white 'HTC' screen, reboots, and then comes to a black page with a picture of a Hero and a red triangle and exclamation mark. I hold home and hit power, and it takes me into the Android system recovery. I wiped data and cleared cache, rebooted, and it does the same thing.
- - -
Now i've done many hours of research, and found nothing to help me. I guess i'm a bit confused on what the SDK does and how to use it, because it won't connect to my phone since I can't even boot my phone into the OS. I tried to download the RUU and rename it update.zip, but it says signature verification failed or not found in android recovery. I've done the clear data method by holding home, back, and power, but still nothing.
I need a clearcut answer for getting back to a stock Alltel 2.1 OS on my phone. I am more advanced than a basic user, and have flashed many roms on Windows Mobile, but remember I might not exactly understand everything.
I'm a silent browser on these forums but now I come to you guys for help. I hope to grow into a dev and hopefully help someone in the future in my position.
I read somewhere to wipe EXT2, but still confused on that process as it seems I don't know how to get into adb command line on my computer.
Try reflashing the cwm recovery. Sounds like you have no recovery image.
-----
Sent from my CDMA Hero. I got some hot Gingerbread-on-Hero action here!
Dumb question...did you flash a ROM? Maybe I missed it in your post, but I see you installed Clockwork, SuperUser and all that, but don't see that you flashed a ROM. *EDIT* I see you did...
So...worst case scenario, if you can't even boot your phone, just start over from scratch...
Download the original AllTel ROM from here.
If you don't have HTC Sync set up and can't restore from your computer, use this method to flash it...your phone should now boot...
Then try to reroot, using this (preferred) or this.
Download ROM Manager from the Market and install ClockworkMod Recovery
Boot to recovery (hold home and power at the same time).
Once in recovery, wipe cache, system, data and boot (make sure you don't wipe your sd card! Do it twice for good measure)
Select install .zip from SD card, select zip and you should be good to go with a rooted phone and a new ROM.
I think that should cover it...
Ok, on your first link to flash my phone, the step says:
"With phone powered on, do "adb reboot bootloader" to enter fastboot."
How do I get the command prompt on my computer to communicate with the phone? That was my biggest problem when reading other people's posts. I guess i'm a bit lost. I installed the r10 android sdk which I believe is the first step? And when my phone is connected to the computer to enter these commands, is it okay if it is sitting at that screen with the red triangle?
Thanks for your help btw your steps sound simple, and simple is nice. One step closer!
Do you have HTC Sync set up? If you do, you should be able to restore from that to get you back to official AllTel...That's going to be the easiest way to get you back to stock I think.
And...I am on a Mac So, helping someone on a PC is not my forte with ADB
I'd try setting up HTC Sync and get yourself back to stock that way.
EDIT - To get it to communicate, you need to set up ADB and all that. Then just use command prompts...Try this thread for help/instructions.
I actually got it to load that rom with vol down + power but eventually got to 'CID incorrect! Update fail!', so i'll try connecting to sync.
damienisxcore said:
I actually got it to load that rom with vol down + power but eventually got to 'CID incorrect! Update fail!', so i'll try connecting to sync.
Click to expand...
Click to collapse
What ROM? The AllTel one?
I have to take off until about 8:30 or so...get yourself set up with HTC Sync and get the USB drivers and all that set up, first thing you need to do is get your computer to talk to your phone...download the official AllTel RUU and restore to stock. That's task 1
Then we'll get ya rooted
I think I found a rom that worked. Currently rebooting. I can follow the rest and if I need anymore help, I'll give you a hollar. I should have had it right the first time, but I was following about 5 sets of different directions and mixing them around to avoid certain programs. I like yours though.
Send me a PM with your paypal e-mail and I can send it over. Least I could do.
OP, glad you got it. What rom?
Ranger, nice!
sent from a series of tubes.
il Duce said:
OP, glad you got it. What rom?
Ranger, nice!
sent from a series of tubes.
Click to expand...
Click to collapse
He flashed CM7. Gotta get him on aospCMod
damienisxcore said:
I think I found a rom that worked. Currently rebooting. I can follow the rest and if I need anymore help, I'll give you a hollar. I should have had it right the first time, but I was following about 5 sets of different directions and mixing them around to avoid certain programs. I like yours though.
Send me a PM with your paypal e-mail and I can send it over. Least I could do.
Click to expand...
Click to collapse
It's tough sometimes to follow things...and as much as we always tell people to search, ya know, the search kinda sucks I searched for all the threads I linked for you, but I knew what I was looking for. If you don't know what to look for, searching is kinda tough. Glad you got it!
Now...if you want a real ROM, I'll just toss this one out there In all actuality, CM7 and aospCMod are quite similar, I am just partial to aosp's builds.
Let me know if you need any more help.
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 ;]]]
(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