Hey.
Ive just tried to upgrade my milestone to G.O.T's Froyo rom.
When i tried to flash the sbf with the rsd lite i just couldnt hit start.
I had the same problem with the vulnerable rom but when i renamed it to something shorterd it worked.
I tried to do the same again but it didnt worked , i tried another sbf but it didnt worked either.
I already have the drivers.
Any one knows whats the problem is?
rename the sbf file into a short name and put it into a short path.
eg:
Code:
C:\haha.sbf
it will help you
EDIT: Wrong thread sorry.
sir_shady said:
rename the sbf file into a short name and put it into a short path.
eg:
Code:
C:\haha.sbf
it will help you
Click to expand...
Click to collapse
i still cant click the start button :\
this happened to me before. not sure what caused it but if you are in bootloader, reboot and let the phone boot normally then plug it into rsd and it should work.
now it say's FAIL and on the botton there is:
"fail flashing process. (0x7100); phone connected"
I had an issue with my RSD Lite, here is what i did to solve it.
1) took the sbf out of any directory and put it straight onto the c drive
2) upgraded rsdLite to 4.6
3) opened RSD Lite and loaded the SBF -> previously i was connecting the phone first and then trying to load the SBF, apparently the order here matters.
4) connected my phone
5) hit start when I saw my phone appear in RSD Lite.
Hope this helps,
Jonathan
it works for me,thanks.
Hello!
I have a rather annoying problem on my Motorola Milestone (NOT a Droid) permrooted with z4root.
Software on Milestone:
Firmware 2.1-update1
Kernel 2.6.29-omap1
Build: SHOLS_U2_02.36.0
OS:
Vista 64bit
latest Motorola drivers (4.8.0)
At the Moment there's still the stock rom installed, I tried to install the CM-Port for Milestones.
That's what I did in order to accomplish my goal:
First, I installed Clockworkrecovery via Rom Manager.
Rom Manager said that it worked, it also tells me that the current recovery system is actually clockwork,
but when I boot into recovery mode with Power- and camera button, it says this:
http://forum.xda-developers.com/attachment.php?attachmentid=471603&stc=1&d=1293116205
Is this still the stock recoverysystem? (except from the error. What does this mean?)
I tried updating the rom to the Cyanogenmod-port from doshaska.
After starting update.zip, it says "EOCD marker occurs after start of EOCD E:signature verification failed".
So I assume, something with clockwork hasn't worked correctly and the recovery/boot is still "protected"
I also now renamed the /system/etc/install-recovery.sh file in order to prevent the phone from restoring the original recovery.
Then, I tried flashing a vulnerable sbf via RSDLite 4.6 in order to reflash another recoverysystem: openrecovery.
The problem here is, that the phone isn't recognized at all by RSDLite when it's booted into normal android OS (computer detects phone w/o problem), in recoverymode, it isn't recognized by the computer itself at all, nothing happens. As far as I know, there is no other way to flash a vulnerable sbf without RSDLite?
It's really weird, shouldn't the phone be recognized in recovery mode aswell? My Computer does _nothing_ when I connect the phone in recovery mode. No typical USB-plugin-sound, no nothing.
So, what can I do? I tried uninstalling everything, Drivers and HW found in device manager, everything. Like it has never seen a Motorola phone before, then reinstalled everything including reboots, but nothing changed.
I would like to flash openrecovery and then the CM-port, but im kinda helpless now.
Thanks!
Try RSDlite v4.6 and 32bit XP...it should recognize your phone...and I guess you can also flash an sbf by applying it as an update.zip
Do a research on this and correct me if I'm wrong!
omg, so stupid.
USB-Debugging was disabled.
Up and running cyanogenmod now
Hello guys,
I hope you get not bored by these every day "I bricked my milestone" threads, but I do really need and would appreciate your help. So here is what's going on:
After Motorola delays the official 2.2 ROM again I decides to try CM6. I asked a friend, who has flashed his Milestone before, for an instruction and he gave me one.
I had an Milestone from O2 Germany with latest 2.36 update. First I made the recovery vulnerable. I downgraded to 2.34 and flashed the vulnerable-recovery only (of course the one for my 90.78 bootloader). I checked if the system was working right after every flash via RSD, and the phone bootet properly anytime. I applied the Androidiani update.zip and entered the OR. I wiped and applied the CM update via OR.
After I applied the CM update, the OR told me to reboot and so I did. I saw the Motorola logo and then the bootloader came up with an error message (Err:A5,70,39,00,27). I wanted to restore via Nandroid, but I no longer could enter the recovery (not to mention the OR). So I asked my friend again what to do and he told me to flash vulnerable recovery again via RSD (yes, I could enter bootloader mode) to be able to enter recovery again. After I flashed I could enter the recovery, but some new mad behavior appeared. The bootloader error disappeared, but every time I tried to boot, the phone ended up in boot loops (Motorola logo --> reboot --> Motorola logo --> reboot -->...).
Then I tried to restore via Nandroid. This seemed to work well, but after a reboot I got this bootloader error again.
To conclude:
flashing via RSD --> boot loops (recovery and bootloader work)
flashing via OR --> bootloader error (only bootloader works)
Some guy from android-hilfe.de told me to flash the bootloader, but I know this is very dangerous. So I went to the #milestone-modding irc-channel and asked for help. They gave me the advice to try to flash other sbf's, maybe an old 2.0. As I tried this today I got a new problem: the sbf file won't work. When I press 'start' in RSD everything starts as usual. But when the phone should show the message "sw update in progress" nothing happens and RSD get stuck on 0%. At the and I get the following message:
'ERROR: Flash failure: Phone[0000]: Error erasing subscriber unit. Device API Error: 0xE003003F Command: ERASE (Error Code: e003003f)'
So I did not proceed. Anybody a suggestion what to do? I'm really helpless.
Greetings Luke
PS: the forum search lead me to this thread. The problem sounds pretty similar.
Try flashing a 2.1 sbf. Let me know what happens. Please use RSDlite v4.6 or higher
vladstercr said:
Try flashing a 2.1 sbf. Let me know what happens. Please use RSDlite v4.6 or higher
Click to expand...
Click to collapse
Good advice. Latest rsd and drivers. Try a different machine...rsd is moody. Try the GOT sbf, it includes the vuln recovery. I have had problems with Win7 that got solved with a different machine with xp.
If all of this does not work, we need to try fastboot. But try the rest first...
Sent from my Milestone using Tapatalk
Hey, thanks for your replie
I did this 3 hours ago. I used the full sbf for the 2.36 update for the German o2 Milestone. I also tried DACH and other versions before.
The result is always, that I end up getting boot loops like described above. RSDLite tells me the file is successfully flashed and unlike a 2.0 sbf the Milestone shows the message "sw update in progress".
I'm using RSDLite 4.9.
LukeTS said:
Hey, thanks for your replie
I did this 3 hours ago. I used the full sbf for the 2.36 update for the German o2 Milestone. I also tried DACH and other versions before.
The result is always, that I end up getting boot loops like described above. RSDLite tells me the file is successfully flashed and unlike a 2.0 sbf the Milestone shows the message "sw update in progress".
I'm using RSDLite 4.9.
Click to expand...
Click to collapse
Try a different version of RSDlite on a different machine or operating system.
Caz666 said:
Good advice. Latest rsd and drivers. Try a different machine...rsd is moody. Try the GOT sbf, it includes the vuln recovery. I have had problems with Win7 that got solved with a different machine with xp.
If all of this does not work, we need to try fastboot. But try the rest first...
Sent from my Milestone using Tapatalk
Click to expand...
Click to collapse
You mean a GOT 2.1 or the 2.2 sbf?
Unfortunately I have no machine running XP at the moment. But I have a virtual XP running on my Win 7 Pro. But I guess it's no good idea to try to flash on this?!
LukeTS said:
You mean a GOT 2.1 or the 2.2 sbf?
Unfortunately I have no machine running XP at the moment. But I have a virtual XP running on my Win 7 Pro. But I guess it's no good idea to try to flash on this?!
Click to expand...
Click to collapse
There is no GOT 2.1
GOT is only 2.2. You can try GOT 2.2 sbf and RSD v4.6
Oh, okay =)
I thought there is a version by them.
Gonna try your advices and post the results.
Thank you so far
Wow, your problem still same me.
I was tried and solved:
_Flash with any rom you have
_Milestone will auto reboot after flash done and loop
_Don't worry about that, remove battery in 5s and re-plugin
_Turn on your milestone: hold X and POWER to access Recovery. Select Wipe and reboot
killed said:
Wow, your problem still same me.
I was tried and solved:
_Flash with any rom you have
_Milestone will auto reboot after flash done and loop
_Don't worry about that, remove battery in 5s and re-plugin
_Turn on your milestone: hold X and POWER to access Recovery. Select Wipe and reboot
Click to expand...
Click to collapse
Did that before and tried it now. Didn't work for me. But thanks for your advice
I also flashed 2.2 from GOT. I was able to flash with RSD and it did not fail. But there is still the boot loop. So nothing changed.
This time I did it with my Atom-netbook and used RSD 4.6.
Ok, so I think I need to try something else. Only flashing with RSD easily doesn't work for me. Like I said in my post before: GOT 2.2 and the advice from killed did not work. Still getting boot loops.
So what would you recommend me to do?
LukeTS said:
Ok, so I think I need to try something else. Only flashing with RSD easily doesn't work for me. Like I said in my post before: GOT 2.2 and the advice from killed did not work. Still getting boot loops.
So what would you recommend me to do?
Click to expand...
Click to collapse
You tried GOT 2.2.1 sbf and it didn't work? Can you access recovery? There was a suggestion of fast boot, but I don't know what that is (just in case you wanted to google it or something, not sure). Do you have the drivers installed for your computer?
You could try this:
milestonefail said:
for some people RSDLite doesnt work properly. One way to fix that is put the SDL.bat file (attatched as .txt, change to .bat before using) in the RSDLite installation folder, move the .sbf file you are using to the same folder, and drag that .sbf to SDL.bat.
)
Click to expand...
Click to collapse
Read the end of this post: http://forum.xda-developers.com/showpost.php?p=11372663&postcount=51 Read the end
Also look here for the link for the drivers: http://forum.xda-developers.com/showpost.php?p=11163403&postcount=27
Good luck! I am not responsible if anything happens to your device.
Yep, it didn't work. RSD said the flash passed, but I always get boot loops. I can access th recovery, but even nandroid in OR doesn't work (I get back to that bootloader error I described in my first post).
I also don't know what fastboot is, but just using google won't help me, because I don't know, what I meant to do with fastboot.
The drivers are installed. Without them I guess RSD wouldn't even recognize my phone.
I also tried the batch file you posted, but it didn't work. I wasn't able to start the flashing process. I guess, the only thing the batch file does is to start RSD with admin rights.
These are all methods I tried and they just don't work. I need something different to this usual helpful stuff. That's why I posted in this forum, because I tried everything and I'm helpless at the moment.
Thanks for your advice anyway. I hope someone has a solution soon.
fastboot most likely will do nothing for you if a nandroid backup fails. Fastboot is a way to flash individiual partitions in case your recovery or nandroid does not work.
It works like adb (command line from a conected computer) and requires nothing on the phone. But if nandroid works...it will not do anything different.
Basically, a nandroid is a collection of .img files (one per partition) that a script flashes in sequence. With fastboot, you could flash all of the .img files from computer command prompt.
I would:
1) try a different nandroid...download the latest leak (01/25 from the dev forum). It is in nandroid format. I would factory reset the phone first.
2) if this does not work, i would fastboot erase and the fastboot flash (look up the syntax) every .img in the nandroid backup. This is just in case you OR is corrupted in some way...not likely, but i am out ideas.
Sent from my Milestone using Tapatalk
Hey,
thanks for your reply.
Your first recommendation would probably not work. I tried 4 different Nandroid backups and every time I get the bootloader error.
Basically I have no idea what fastboot is, where I get it from and not to mention how to get it work, so I think this is no option for me.
Right now I have resigned. Nothing seems to work. I consider getting a new phone. But before I do this I wanna ask you one last question: can flashing the bootloader theoretically effect anything? I think my phone IS bricked at the moment, so I'm not anymore afraid of flashing the bootloader. But if it would even theoretically be impossible, that this would change anything, then it's just a waste of time. So does flashing 90.78 bootloader via RSD Lite change anything?
Thank you!
LukeTS said:
Hey,
thanks for your reply.
Your first recommendation would probably not work. I tried 4 different Nandroid backups and every time I get the bootloader error.
Basically I have no idea what fastboot is, where I get it from and not to mention how to get it work, so I think this is no option for me.
Right now I have resigned. Nothing seems to work. I consider getting a new phone. But before I do this I wanna ask you one last question: can flashing the bootloader theoretically effect anything? I think my phone IS bricked at the moment, so I'm not anymore afraid of flashing the bootloader. But if it would even theoretically be impossible, that this would change anything, then it's just a waste of time. So does flashing 90.78 bootloader via RSD Lite change anything?
Thank you!
Click to expand...
Click to collapse
Why give up without trying? I believe you should flash it to see if it changes anything...How worse than this can it get?
Please...do not take my words for granted...Inform yourself from other sources before you try this...and if you do let us know if you successfully managed to get your phone back!
You misunderstood me. I wanted to try it, but if someone would have said that it's a waste of time, then I wouldn't have done it.
So I tried it, but flashing the bootloader (90.78 --> 90.78) didn't change anything. Still getting boot loops.
What do you think. Try a downgrade to 90.73? Is a downgrade even possible?
LukeTS said:
You misunderstood me. I wanted to try it, but if someone would have said that it's a waste of time, then I wouldn't have done it.
So I tried it, but flashing the bootloader (90.78 --> 90.78) didn't change anything. Still getting boot loops.
What do you think. Try a downgrade to 90.73? Is a downgrade even possible?
Click to expand...
Click to collapse
I dont think that is possible. I've read here on the forum somewhere that downgrading the bootloader is not possible...but you should search, maybe you find that it's possible.
Anyhows, I dont think your phone is lost, I just think we're missing something!
I also think it's not possible. I've read this in some forums, too.
It seems that it isn't lost. I was happy, as I found out, that I can enter recovery and bootloader. I thought it could easily be restored. But then nothing worked for me. So we must miss something, but I have no clue what.
What do you mean by:
"Then I tried to restore via Nandroid. This seemed to work well, but after a reboot I got this bootloader error again."
Are you sure you have enough battery?
You could try restoring a nandroid from other recovery. Replace the recovery from your sd-card. If you use Androidiani 3.3 try an older version of it or another OpenRecovery.
Hi, my best friend she had a HD phone, one day got stuck into the M logo, the only thing I can do is get into the fastboot, no recovery no nothing.. So i try to reinstall the rom, have download several tools but i cant do anything, after several intents to install roms i hace in AP fastboot flash mode, device is unlocked status code 1fastbookt Reason sticky bit factoy_fastboot. for a 2nd time but i can install roms, I dont know if phone bootloader unlock and cant check... I dont know if phone is usb debugging cause it wont load the system. I dont see any internal files from phone I also try rsd lite, but the same it says that it start doing the process but nothing else happen.. any ideas on how to get a rom install there..
thanks
SAME thing..
Please do help us...No recovery...No debugging...stuck at logo..!!
If you don't have an unlocked bootloader, I don't think you can use Myth or RSD to flash an ICS rom over a JB rom.
Did you load the latest Motorola USB drivers? When you connect the phone, run adb to list the devices. Does your phone appear?
not for me doesnt show any devices... and while trying to do other commands always get stuck ad *daemond started succesfully* but doesnt do anything.. also when trying to use motorola device manager it says it will update and never connect to server and close the app.
if i do fastboot commands like reboot-loader it does work it reboots the phone, but if i try to flash something doesnt it doesnt do anything.. i try using mfastboot also and the same happen.
Is there a way to flash a rom or something so i can fix this phone or it is dead?
On the Fastboot screen, if it says UNLOCKED in capitals next to "Device Status:" , then this problem is easily fixable.
Download RSD Lite from here: http://forum.xda-developers.com/showthread.php?t=2231249
Download Motorola Stock Firmwares:
Stock Jellybean for AT&T: http://sbfdownload.droid-developers...MB886_NII_TA-2-16-release-keys-NII-MX.xml.zip
Stock Jellybean for Bell Canada: http://sbfdownload.droid-developers...FFW-11-4-release-keys-BellMobility-CA.xml.zip
Open up your zip file and replace the .xml with the new XML you will download from this link: https://www.box.com/s/num1eshkf0c2or2h4160 You really can't forget to do this!
Launch RSD, connect device to PC, make sure RSD recognizes it. Navigate to your firmware file, select it, and press the start button. Sit back, relax, and let it do its work. It will take around 5-10 minutes. Do not unplug the cable, and do not attempt if you are in a situation in which you think you may lose power (especially if running from a desktop PC).
If RSD Lite won't work, then this thread will show you how to manually flash your stock firmware: http://forum.xda-developers.com/showpost.php?p=40929335
Basically, you repeat all the instructions I just gave you and then manually input some lines in Command Prompt.
Hey guys,
I accidentally selected the OTA that popped up on my phone while on a Stock ROM and now my Verizon LG G2 is stuck in a bootloop with CWM Recovery 6.0.4.4 I have tried to wipe everything and install a older CM ROM and Gummy ROM to see if that would get my phone to turn back on and it doesn't. I have researched many threads to see if there was a resolution for my issue, but everything that I tried did not work. I have a iMac and a Windows laptop and I have tried many things with Terminal and Command Prompt and nothing seems to work. I don't know if I am doing something wrong with ADB or if I am simply just missing other things, but I am trying to get my phone back un-rooted and back to stock to get my phone replaced under the warranty. PLEASE HELP!
Yokleezy said:
Hey guys,
I accidentally selected the OTA that popped up on my phone while on a Stock ROM and now my Verizon LG G2 is stuck in a bootloop with CWM Recovery 6.0.4.4 I have tried to wipe everything and install a older CM ROM and Gummy ROM to see if that would get my phone to turn back on and it doesn't. I have researched many threads to see if there was a resolution for my issue, but everything that I tried did not work. I have a iMac and a Windows laptop and I have tried many things with Terminal and Command Prompt and nothing seems to work. I don't know if I am doing something wrong with ADB or if I am simply just missing other things, but I am trying to get my phone back un-rooted and back to stock to get my phone replaced under the warranty. PLEASE HELP!
Click to expand...
Click to collapse
Try the LG tools for bricked G2. Its somewhere on these forums. All you have to do is plug up to a computer and flash the stock ROM with the tool.
Sent from my magic box.
GlitchedSoul said:
Try the LG tools for bricked G2. Its somewhere on these forums. All you have to do is plug up to a computer and flash the stock ROM with the tool.
Sent from my magic box.
Click to expand...
Click to collapse
I tried the LG Flash Tool on a PC, but it gives me an error message LG USB/Parallel Lock Key is not detected and when I hit OK, it pops up with a Login with the Country filled in with Republic of Korea, ID and Password are left empty. I don't know what to do from there.
Enter into download mode by turning off your phone, then hold vol + and plug it to your computer.
Download the official firmware for your device.
Download FlashTool.1.0.54
unzip FlashTool.1.0.54, open the folder and launch UpTestEX.exe
Select type:3GQCT
Phone mode: DIAG
Select kdz file: browse for your official firmware
Then click: normal web upgrade test
Then click: Upgrade start
a new window will show, chose english language. Country: korea, then click ok and wait untill the firmware installs.
Good luck.
Partager.info said:
Enter into download mode by turning off your phone, then hold vol + and plug it to your computer.
Download the official firmware for your device.
Download FlashTool.1.0.54
unzip FlashTool.1.0.54, open the folder and launch UpTestEX.exe
Select type:3GQCT
Phone mode: DIAG
Select kdz file: browse for your official firmware
Then click: normal web upgrade test
Then click: Upgrade start
a new window will show, chose english language. Country: korea, then click ok and wait untill the firmware installs.
Good luck.
Click to expand...
Click to collapse
I am unable to boot into download mode, unfortunately. That's where I get stuck every time.
Yokleezy said:
Hey guys,
I accidentally selected the OTA that popped up on my phone while on a Stock ROM and now my Verizon LG G2 is stuck in a bootloop with CWM Recovery 6.0.4.4 I have tried to wipe everything and install a older CM ROM and Gummy ROM to see if that would get my phone to turn back on and it doesn't. I have researched many threads to see if there was a resolution for my issue, but everything that I tried did not work. I have a iMac and a Windows laptop and I have tried many things with Terminal and Command Prompt and nothing seems to work. I don't know if I am doing something wrong with ADB or if I am simply just missing other things, but I am trying to get my phone back un-rooted and back to stock to get my phone replaced under the warranty. PLEASE HELP!
Click to expand...
Click to collapse
flash twrp and try this http://forum.xda-developers.com/showthread.php?t=2451696
datechnerd said:
flash twrp and try this http://forum.xda-developers.com/showthread.php?t=2451696
Click to expand...
Click to collapse
How can I flash TWRP when my phone won't boot? According to a post I read and a YouTube video tutorial I watched, they keep referring to turning on USB Debugging which I can not do.
Yokleezy said:
How can I flash TWRP when my phone won't boot? According to a post I read and a YouTube video tutorial I watched, they keep referring to turning on USB Debugging which I can not do.
Click to expand...
Click to collapse
ADB sideload