Database Develop

[Q] [S.O.S.] A rare MILESTONE brick situation!

Fellow androiders,
I believe I am in a really rare brick situation that no matter how I try, it still does not show any turn around.
[Introduction]
I bought a Korean version Milestone(Moto Qrty, as they put], and I took it to China. Because the original phone did not support sending Chinese text message, plus, too much telco provided apps are making the phone sluggish, I decided to follow my friend advice, to switch to widely available open-sourced Froyo (I wanted the CM).
[Problem]
I thought that the flashing process would not be too difficult and I could handle it by myself. But, it turns out that I have become a victim of an overly simplified version of flashing guide. I don't know what exactly have done wrong, after successfully rooted the phone, I vaguely remember that I have used CM ROM for Droid, instead of CM ROM for Milestone.
And that made my phone a brick. My phone will turn on, but will restart again and again after M logo(So-called M boot loop).
[Background information of the Phone and my PC environment]
Phone Model: A853
Original Bootloader version: A0.20
Original Android System: Froyo
RSD lite version: 5.3.1. (later switched to 4.6 due to the suspicion of RSD bug)
Operating System: Windows 7 64 bit, English
[What I have tried so far]
I have tried to follow many tips on the internet. Tips from Korean websites, from Chinese websites, and from English websites. Basically, these tips will let you flash back to the original ROM by using RSD lite.
But, no matter what I try, it will not fix the boot loop problem.
I've tried to
1) Bring the phone to the original status [did not work.]
- flash the bootloader into A0.20 (the original bootloader) with RSD lite;
(bl_a020_umts_sholesumts_skt_consumer_replacer.sbf)
- flash with original Froyo sbf (following the advice from Korean websites, flashed Clair first, and then flashed Froyo) with RSD lite.
(A853_2.1(Eclair).SBF / A853_2.2.1(Proyo).SBF)
* According to what Koreans say, it would make your phone into the original status, will even remove signs of root.
2) Used many combination of following bootloader and ROMs
- flash the bootloader into 90.78ch
(BL_9078_umts_sholes_GC_HS_Consumer_replacer.sbf)
- flash the bootloader into 90.78
(BL_9078_umts_sholes_HS_Consumer_replacer.sbf)
- GOT221 ROM
(GOT_RTEU_2_2_1FULL.sbf)
- And some other un-name-able ROMs
SGC_U2_03.04.0_USASHLSGCB1B2B5008.0R_PDS06A_HWp2a_1FF.sbf
3) Used many different OpenRecovery Variations
OpenRecovery v1.46
OpenRecovery 3.3
OpenRecovery GOT mod v2.1
4) Restore Nandroid backup which I made right before I made my phone brick.
5) Cleaned data/cache/dalvic as I do every flash, and tried boot without SIM card and SDCard.
[Some discoveries and successes]
- With 90.78ch + GOT2.2.1, it will show "Android" screen, but it will reboot as soon as the phone OS interface show up.
- According to my friend, when he flashed back to the original bootloader A0.20 + original froyo Rom, it showed TelCo Symbol "T" once (which is the booting screen right after M).
[Final Comment]
What I really want to know is that is it the time I give up on it? or is there any value of pursuing other knowledge on bring this phone back?
I really need this phone, and it will take some times to save money to buy another smartphone, I would really really appreciate if you can help me bring this phone back to normal.
Thank you.

some users reported problems with sdcard. try to boot without sdcard, and wipe everything after or before the flash process.
and i don think it's hard bricked...

Sir, I have tried so, somehow, I did not have lucks other had.

roofghost said:
Sir, I have tried so, somehow, I did not have lucks other had.
Click to expand...
Click to collapse
So you've tried flashing different bootloaders, with no success? I always thought flashing another bootloader version different from your own was risky.
If not, you can just try flashing the SBF from here: http://android.doshaska.net/rootable , then installing OpenRecovery, rooting the phone, flashing a custom ROM, etc.

..... my bad

I have the same issue,
in recovery there is message when wiping data/factory reset:
E:Error in CACHE:fota/log
(no space left on device)
I am wondering, if I move CACHE to SD would it help??
Yesterday I have installed original Rom (shols~) and phone booted once to android and when I have rebooted it, there is M bootloop again.
Please help me

skadude66 said:
So you've tried flashing different bootloaders, with no success? I always thought flashing another bootloader version different from your own was risky.
If not, you can just try flashing the SBF from here: android.doshaska.net/rootable , then installing OpenRecovery, rooting the phone, flashing a custom ROM, etc.
Click to expand...
Click to collapse
Thanks, did not work.
I have a feeling that the "doshaska" will know how to solve this. Anyone know how to contact or PM him?
Thanks.

By the way,
in this case, is there anyway can fix the brick via "console" in the OpenRecovery?
Thanks.

So... you have open recovery and can get to the console...
What happens if you copy CM to the updates folder and flash CM?

zeppelinrox said:
So... you have open recovery and can get to the console...
What happens if you copy CM to the updates folder and flash CM?
Click to expand...
Click to collapse
Yes, I can enter OpenRecovery and can get to the console.
And,
sorry about the CM, I think I will have to try that again and let you know then.
Is there any CM ROM you want me to try? (Hopefully with a reliable instruction. If you are busy, you can just leave this part, I will look for myself about the instruction.)
Truly thank you and glad to see new reply under this topic.

Well, use OR's mount as usb function and plug into your computer.
Copy the latest CM7 (I think that's what you want - or any ROM really) to the updates folder.
Wipe all caches
Then apply the update
It should "just work"
I mean, the hardest part is getting into OR lol
I'm surprised that your battery hasn't died yet

zeppelinrox said:
Well, use OR's mount as usb function and plug into your computer.
Copy the latest CM7 (I think that's what you want - or any ROM really) to the updates folder.
Wipe all caches
Then apply the update
It should "just work"
I mean, the hardest part is getting into OR lol
I'm surprised that your battery hasn't died yet
Click to expand...
Click to collapse
Can I install CM7 on Froyo? I thought that was for the Android 2.3.
I have just flashed back to the original bootloader of A0.20 (it was 90.78 as I play around with it.), and flashed the original korean .sbf froyo. Just to follow your suggestion.
I will try to install vulnerable recovery. I think in this way, I can use OpenRecovery again.
About my batter, I purchased a separate battery charger.
I will keep my status updated as soon as I try this out.
Thanks.

same problem and flash so many rom My milestone can't acess sdcard on recovery mode and android os.
Sent from my Milestone using XDA App

guys same problem here, help us

Tried going from 2.2 Andrometa3 to ICS ROM 4.0.3. Houston we have a problem.

I used AdamOutler 's guide to root and put a custom ROM on Captivate 2.2 found here:
http://forum.xda-developers.com/showthread.php?t=1012769
And everything went swiftly. AT THIS POINT, I MADE A NANDROID BACKUP
I then wanted to step up to an Ice Cream Sandwich ROM, which was the main purpose of my rooting in the first place. So, I downloaded the ROM found in this forum, as it is the most popular amongst the forums, so to seem. I found it here:
http://forum.xda-developers.com/showthread.php?t=1363760
Well I downloaded the ROM straight from my phone on the browser, then put it on the Root of my internal memory.
I booted into recovery, Factory Reset/Wipe Cache Partition/Wipe Dalvik Cache.
Went to install .zip from SD card, then clicked on install the ICS ROM.
Began to seem as if it was updating, then the phone shut off, started bootlooping.
No big deal I thought, just boot into recovery, right? I booted into recovery. It went from the Red CWM that i had seen before, to a Blue one.
I selected my nandroid backup, and it gave me all sorts of errors.
Got to the point where CWM was acting as if it could even find where it was supposed to work from?
Now I have the Phone>!<Computer on the black screen when I try to turn on.
Anyone else ever had this problem, or could someone tell me what went wrong? Not in a huge rush as this is just my development phone, but do I need to go ahead and use the Odin3 One Click to do a full complete restore or is there any way of saving what I had?
Thanks guys, God Bless.

LOL OOPS thought i was in the dev section.... ignore..help below.

xCaptivateRx said:
I used AdamOutler 's guide to root and put a custom ROM on Captivate 2.2 found here:
http://forum.xda-developers.com/showthread.php?t=1012769
And everything went swiftly. AT THIS POINT, I MADE A NANDROID BACKUP
I then wanted to step up to an Ice Cream Sandwich ROM, which was the main purpose of my rooting in the first place. So, I downloaded the ROM found in this forum, as it is the most popular amongst the forums, so to seem. I found it here:
http://forum.xda-developers.com/showthread.php?t=1363760
Well I downloaded the ROM straight from my phone on the browser, then put it on the Root of my internal memory.
I booted into recovery, Factory Reset/Wipe Cache Partition/Wipe Dalvik Cache.
Went to install .zip from SD card, then clicked on install the ICS ROM.
Began to seem as if it was updating, then the phone shut off, started bootlooping.
No big deal I thought, just boot into recovery, right? I booted into recovery. It went from the Red CWM that i had seen before, to a Blue one.
I selected my nandroid backup, and it gave me all sorts of errors.
Got to the point where CWM was acting as if it could even find where it was supposed to work from?
Now I have the Phone>!<Computer on the black screen when I try to turn on.
Anyone else ever had this problem, or could someone tell me what went wrong? Not in a huge rush as this is just my development phone, but do I need to go ahead and use the Odin3 One Click to do a full complete restore or is there any way of saving what I had?
Thanks guys, God Bless.
Click to expand...
Click to collapse
Different kernels have different colour recoveries. kernels change with rom.
Different CWM version recoveries are incompatible.
Almost anyone that has flashed a samsung galaxy phone has seen that screen, and it is correctly written " Phone /!\ PC " (you can choose to underline the /!\ if you want to be fancy). it is called the "soft brick screen" hint hint.. go search.
yes
yes. restore with same kernel you used to back it up.

TRusselo said:
Different kernels have different colour recoveries. kernels change with rom.
Different CWM version recoveries are incompatible.
Almost anyone that has flashed a samsung galaxy phone has seen that screen, and it is correctly written " Phone /!\ PC " (you can choose to underline the /!\ if you want to be fancy). it is called the "soft brick screen" hint hint.. go search.
yes
yes. restore with same kernel you used to back it up.
Click to expand...
Click to collapse
Very good responce...however after odin3 one clicking back to stock 2.1 eclair, I lost my clockwork mod folder that was on the internal SD, of course. Rookie mistake, I should've definately copied it on to the external SD card. Thanks for informing me of proper terminology. Also, after downloading rom manager and flashing, booting recovery, I can only access cwm through the rom manager, the three button fix doesn't work.
Why was this moved? I posted in general..

because you have a question/problem
rom manager is only used with 2.1 (for captivate). doesnt work on 2.2 or 2.3.X or 4.0.X
in all newer versions of android we "bake" cwm into the custom kernels we package into the custom roms. so there is no stock recovery and you dont need the update.zip.
dunno why you would flash all the way back to 2.1... EWWW.
in the dev section there is a sticky called odin master collection. use a newer stock rom. the master collection also has stocks versions, pre-packcaged with a custom cwm kernel so you can skip a step of getting it after going back to stock.

Do we know why this happened in the first place? Incompatible kernel? Is there a guide somewhere for moving from GB to ICS?
Sent from my SGH-I897 using XDA App

I thought you had to have GB bootloaders before you flashed any ICS roms ? I know I've read that ,then again I've read 10,000 threats and sometimes it becomes mind numbing.

Do you not have to flash back to 2.1 after having these problems? Right now my phone is at the soft brick screen, no button combo working. Not recognized by the computer either. I'm heading out to radio shack and make a USB jig in a bit. I'd love to just flash straight up to a gingerbread ROM if I can possibly get this thing in download mode. Anybody help a brotha out!
Edit: the sim is not activated, I just run it off Wi-Fi because big red is my carrier. This is my development phone. So I can't just KIES update to whatever the newest is.
Sent from my DROID X2 using XDA App

Any firmware should work, no need to go all the way to eclair...just flash gingerbread.

Don't think its been mentioned yet but when going from 2.2 to ICS, you have to flash the rom twice to get out of the bootloops. Sounds like you were at that point but when you flashed your nandroid instead of the ICS rom again, your phone must not have liked it.

aww.W.T.F? said:
I thought you had to have GB bootloaders before you flashed any ICS roms ? I know I've read that ,then again I've read 10,000 threats and sometimes it becomes mind numbing.
Click to expand...
Click to collapse
Not all ICS ROM's require GB bootloaders. I ran THS, and am now on vibranturk's AOKP and I came straight from 2.1

I think the issue was you're supposed to flash them twice. Well that fixed it for me. I dkbhave the gingerbread boot loaders now though
Sent from my SGH-I897 using xda premium

I went from bone stock Froyo 2.2 straight to THS ICS with no problems whatsoever. So some ICS Roms doesn't need GB bootloaders.
Sent from my SGH-I897 using xda premium

I'm on the same situation as the original poster: I'm on andromeda3 and now I want to upgrade to ICS. Right now my captivate has cwm 2.5.1.2 can I flash any ICS mod from there or do I need to do something else?

See this.... TRusselo's "Guide..." that is a Stickied Thread in the Q & A Forum.
I believe u will need the Gingerbread Bootloaders...
Sent from my SAMSUNG-SGH-I777 using xda premium

[Q] Installing ICS from CM7.2?

Hi,
Sorry if this seems like a dumb question - A bit confused from reading up all the info on upgrading to ICS on the p990.
Im running a volk custom kernel, and CM 7.2 - OS Version 2.3.7.
Whats the "best" way to upgrade to the new ICS? I tried running the LG software update but it doesnt go too well, fails after it tries to detect phone - even though it detects it initially.
Can I get the release that LG released with my setup?
Please advise.
Thanks!

Same situation here. I'm on official cm7.2 and would like to upgrade to ics. But don't think that useing official lg update tool is so good idea - it might brick your phone. It won't update to ics because you aren't running the official GB rom so lg update tool won't upgrade (correct me if i'm wrong).
Maybe the AIO tool would do the trick.
Anyways, people we need your advice!

LOL, use NVflash ICS rom like TG.

for me the best way is using the toolkit to install new partition, new bootloader and recovery
than boot into recovery and flash the room as usual

Thanks Wakata.
Much appreciated. I have tried downloading the toolkit but its always corrupt.. ill download the 7 zip format.
I take it that I will need to back everything up and wipe everything, install new partition, boot loadder and recovery(CWM??), then flash with the new rom and kernel?

I've also used the All-In-One P990-Toolkit to upgrade to ICS.
You can use 1. to backup your internal SD in case you need it later.
Then hit 4. to change the partition layout and after that 8. to flash the new unlocked bootloader. That's all.

Thanks again
Slight problem - I downloaded the 7z file, and extracted them, but cant seem to run the .cmd file? What am i doing wrong here?

scratch that last question.. for some reason the files are corrupt when i download them.. grrrr.

So I followed the instructions, and suprise suprise, I get an error -
Nvflash started
nvflash configuration file error: file not found
An error occured. Read above lines for details
Help please

Nevermind, I had a fiddle and flashed ics 6.0.xxx.. lets see how it goes. Hopefully I havent bricked it lol

Sorry, problem.
I first tried option 1, then 4, then 8.. after its all done, no errors - I boot the phone, and its stuck on the red LG logo.. I've left it there for around 10-15 mins with no luck? Help!

Haha, actually I figured it out. I did realise I didnt have a ROM! Doh! lol rookie mistake.
I downloaded this rom and kernel(1.4ghz OC) and its running pretty well, no bugs so far(touch wood)

[Q] Hi I'm on old bootloader and would like help on how to flash the new to my phone.

Hi I've searched the forum and the stickies but no I'm on old bootloader and would like help on how to flash the new to my phone. Is ther any good guides available?
Thanks!

kiranos said:
Hi I've searched the forum and the stickies but no I'm on old bootloader and would like help on how to flash the new to my phone. Is ther any good guides available?
Thanks!
Click to expand...
Click to collapse
Go here
And follow the directions.
Or use the link for the AIO tool in my sig below,

thanks for the input, but option one is actually converting the rom between bootloaders right? not swithing to the new bootloader on my phone.
And I looked at the All-in-One tool, is it "4 - Repartition your device with preferred layout and bootloader" which is beeing refered to when switching bootloaders between old and new?

kiranos said:
thanks for the input, but option one is actually converting the rom between bootloaders right? not swithing to the new bootloader on my phone.
And I looked at the All-in-One tool, is it "4 - Repartition your device with preferred layout and bootloader" which is beeing refered to when switching bootloaders between old and new?
Click to expand...
Click to collapse
Yep, that would be the right option. Note that your internal SD will be wiped, so back it up and follow the instructions carefully when you execute it.

kiranos said:
thanks for the input, but option one is actually converting the rom between bootloaders right? not swithing to the new bootloader on my phone.
And I looked at the All-in-One tool, is it "4 - Repartition your device with preferred layout and bootloader" which is beeing refered to when switching bootloaders between old and new?
Click to expand...
Click to collapse
This type of question, shouldn't be asked in this section. (as there is a Questions and Answers section, that this and your previous question has been answered)
I gave you both options in case you wished to stay on the old Bootloader.
The AIO tool is very straight forward. as long as the correct drivers are installed. and you have made a backup of all your personal things you'd like to keep (pictures / movies) - as you cannot restore data from one bootloader to the other. so moving is a clean slate.
i use 9 - to edit the layout of the partitions (to make the best of space since i dont use alot of the other (new) partitions created in the new bootloader, then i use 4 to flash the new partition using my custom edit table. and i choose the TWRP for recovery. after the process is finished it will ask you to turn on the phone, to enter recovery, and connect phone again, to fix your SD card. (as it was not formatted properly during the repartition) once thats done, your ready to flash NBL roms.
The process for going back to the old BL is the exact same. - full back, (manual backup of personal items) repartition, fix SD, flash rom.

Noob still on CM 7.1 needs KK.

Every time I trie to update to the latest ROMs I notice they specifically target the new bootloader. I have no idea what the old vs new bootloader dilemma is about but I bet my device runs the old one, I read somewhere the white LG logo on startup hints to an old bootloader,
My question is how to upgrade my bootloader or ROM directly to Kitkat the easiest way possible, I bought my handset already CMed and unrooted but I have never done it myself.
Thank you in advance, and if you could bother throw in some links to relevant threadshttp://forum.xda-developers.com/images/icons/icon8.gif

xdaCyborg said:
Every time I trie to update to the latest ROMs I notice they specifically target the new bootloader. I have no idea what the old vs new bootloader dilemma is about but I bet my device runs the old one, I read somewhere the white LG logo on startup hints to an old bootloader,
My question is how to upgrade my bootloader or ROM directly to Kitkat the easiest way possible, I bought my handset already CMed and unrooted but I have never done it myself.
Thank you in advance, and if you could bother throw in some links to relevant threadshttp://forum.xda-developers.com/images/icons/icon8.gif
Click to expand...
Click to collapse
for tonyps kitkat , the only one for daily usage workign at the moment. you need his version of twrp 2.6 or as i know the cwm version 6.0.4.7, which can be found somewhere in the development forum.
tonyps cm11 : tonyps Cm11
kowalski kernel: kowalski kernel by pengus
dl links: cm11 by tonyp and bs86
working twrp by tonyp

They are New Bootloader only! The process seems as easy as full wipe + flash the zip (my phone came with ROM Manager 4.5.0.1 with old recovery) but I fear my bootloader in incompatible. Is there a way to update or something.
Also does my sd card and all applications get removed, and how to back them up, also if I brick my device does the recovery still work to flash the back up or what? very noob I know, I learned alot of terms but never managed to make good sense of it all, thank you.............
Oh one minute my ROM Manager has an Install ROM from SD Card button, can I do it right inside ROM Manager?

xdaCyborg said:
They are New Bootloader only! The process seems as easy as full wipe + flash the zip (my phone came with ROM Manager 4.5.0.1 with old recovery) but I fear my bootloader in incompatible. Is there a way to update or something.
Also does my sd card and all applications get removed, and how to back them up, also if I brick my device does the recovery still work to flash the back up or what? very noob I know, I learned alot of terms but never managed to make good sense of it all, thank you.............
Oh one minute my ROM Manager has an Install ROM from SD Card button, can I do it right inside ROM Manager?
Click to expand...
Click to collapse
With that you can backup/resotre and change the bootloader and alot more AiO-Toolkit
If you change the bootloader layout, as i know all stuf will be removed. so make a nandroid backup, if your new rom is not working and make a sdcard backup(also in aio) to get appdata back if you want.
If you dont want to download all apps new after having new rom use titanium backup. the recovery is not breakable. it will always work. not important if you **** your rom

xdaCyborg said:
They are New Bootloader only! The process seems as easy as full wipe + flash the zip (my phone came with ROM Manager 4.5.0.1 with old recovery) but I fear my bootloader in incompatible. Is there a way to update or something.
Also does my sd card and all applications get removed, and how to back them up, also if I brick my device does the recovery still work to flash the back up or what? very noob I know, I learned alot of terms but never managed to make good sense of it all, thank you.............
Oh one minute my ROM Manager has an Install ROM from SD Card button, can I do it right inside ROM Manager?
Click to expand...
Click to collapse
As you do have CM 7.1 installed, I guess you've got a custom recovery installed too? I don't think you can directly use ROM manager to install a kernel, but you can use ROM manager to boot into recovery mode and flash the zip from there Just be sure to make a nandroid backup, just in case KK isn't compatible with 7.1.
If you ever want to get tonyp's CM 11 though, the AIO toolkit, as @Zubeplanet pointed out, is really easy to use to get the new bootloader.
Happy flashing!