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

[Q] Droid 3 Recovery

I recently Rooted my Droid and deleted/backed-up some of the wasteful apps that come stock. I was wanting to Unroot my phone and I read that I needed the original apps back on my device. So I started recovering all of the old apps with Titanium Back-up and some of them were not recoverable. So I did some more research and found out about RSD Lite and Re-Flashing your phone back to its original stock state. I followed the steps from 2 different sites (This one and RootzWiki.com) and the problem I'm having is when I go to Flash my Device it says,
"Please check input file. Either XML format is wrong or image files associated with it are missing."
I have download many off the Fast-boot files and none seem to work. I must be doing something wrong, but I have searched and I'm stumped.
Any help would be much appreciated! Thanks!

Any Ideas?! I can't post in the related post about this topic because I'm new (and it says I need 10+ post). I was hoping someone in General had a little experience on the problem I am having. Thanks!

[Q] Dead?

I was working on getting 4.4 AOSP kitkat on my Atrix HD, and it was going great. While backing up with CWM, it failed on the data, but I figured I could just restore my files from a back up. When I went to put the rom on it, I got some no_contexts error and it said somethign about metadata. I tried to restore the backup and got a md5 fail. I used the advanced restore to let it skip the data part, but all parts gave a md5 fail. Now for somereason, I'm unable to connect through ADB, though fastboot still works, so I can't try pushing a stock rom. I tried adb sideload, but that didn't even remotely work. I also can't charge my phone, and it has a low battery. Does it charge in fastboot or recovery mode? Please help.

Phew
Ok, so I was looking around for a way to get back to stock without adb, which, as I said earlier, I couldn't get working halfway through. I was looking around for a way to do it with fastboot, and found rsd lite. I downloaded the files I needed, but it always failed 1/23. I then thought to just do it manually, and it worked perfectly
On a side note though, is there a way to use fastboot to flash nonstock roms? Would I just follow the same commands I did for the stock version? Is there any specific version I should download to use fastboot with it? I am still wanting an as-close-as-possible stock version of 4.4 for atrix hd. Also, did I do anything wrong the first time, or was the download corrupt?

ace_case said:
Ok, so I was looking around for a way to get back to stock without adb, which, as I said earlier, I couldn't get working halfway through. I was looking around for a way to do it with fastboot, and found rsd lite. I downloaded the files I needed, but it always failed 1/23. I then thought to just do it manually, and it worked perfectly
On a side note though, is there a way to use fastboot to flash nonstock roms? Would I just follow the same commands I did for the stock version? Is there any specific version I should download to use fastboot with it? I am still wanting an as-close-as-possible stock version of 4.4 for atrix hd. Also, did I do anything wrong the first time, or was the download corrupt?
Click to expand...
Click to collapse
I'm glad to hear you got things back into working order! With regards to flashing any custom ROM, the safest way is to use a custom recovery. Currently, as far as I can tell, the only official recovery for the Atrix HD is CWM but that's fine. You do want to be sure that you have the latest, most up to date version of CWM installed. As of right now, I believe that is 6.0.4.4 (http://clockworkmod.com/rommanager, mine already might be out of date again) and that may be where your problems came from when you were wiping and getting errors.
With regards to a close to stock 4.4 for the Atrix HD, there is an official build of CM available here: http://download.cyanogenmod.org/?device=mb886 although the latest build is from February, I can assure you that from running it on my Atrix HD it is definitely much smoother than what Motorola has offered (to date) for this device. There have been promises of official 4.4 support but I haven't seen anything come from that as of today (see here for more info: http://goo.gl/oK34W0)
CORRECTION: The official support for Atrix HD is here: http://download.cyanogenmod.org/?device=moto_msm8960
It is a merged thread for all of the devices mentioned here: http://wiki.cyanogenmod.org/w/Moto_msm8960_Info
I can't vouch for it personally but others have said that it has fixed a lot of bugs since the single device support that ended in February...

Help a newbie; LG Optimus L90; learning to flash

Current situation: pretty much complete newbie. I broke my factory OS after rooting it, I think I deleted something Settings needs, so anytime it needs to access settings I get "Unfortunately, Settings has stopped." I factory reset it hoping that would help, but now after loading it gets stuck on a cycling white screen reporting that error (I think it's trying to set up the phone.) The error message prevents me from doing the touch-four-screen-corners trick I've read about and bypass set up. So, stuck on phone setup errors as near as I can tell.
I do have my user apps backed up with TiBu, but couldn't get the recovery zip from TiBu to work. I downloaded CWM but didn't figure it out yet. Also unfortunately I can't get the USB drivers to work (the LGE Android MTP Device won't install), so I think my only way of getting files to my phone now is using the microSD cards.
I'd love some help! I think my factory OS is FUBAR, so I'm not trying to fix that, instead I'd rather just get a cool ROM loaded so I can continue learning with a working device with said cool ROM. I don't fully understand terms that I know I need to like "bootloader" or what CWM / TWRP actually does or how to use them (I need to make a custom recovery ROM?). Or where to get a cool ROM or which to pick, some step by step basics on from some experienced users would be fantastic! Thank you so much!

So you were on stock, rooted, backed up and then messed the ROM? Flash stock ROM again using LG Flash tool (there is a thread in the main section), it should not wipe your data but you'll lose root. Hard to fix if you're not sure about the problem and have no easy access to files. Just make sure you flash the correct version for your model (D405, D410hn, etc), preferably the same version you have now so you won't need a factory reset after flashing...

lfom said:
So you were on stock, rooted, backed up and then messed the ROM? Flash stock ROM again using LG Flash tool (there is a thread in the main section), it should not wipe your data but you'll lose root. Hard to fix if you're not sure about the problem and have no easy access to files. Just make sure you flash the correct version for your model (D405, D410hn, etc), preferably the same version you have now so you won't need a factory reset after flashing...
Click to expand...
Click to collapse
Thank you, this put me in the right direction. I ended up discovering that even though the " LGE Android MTP Device won't install," the flashing process worked with this program via USB anyway. I'm going to lick my wounds a bit before trying to flash a custom ROM. Thank you!

For the rom installation, after unlocking your bootloader and rooting, download the app Flashify from Google Play, then install TWRP or CWM zip file as recovery image. Then, from there, you can install custom ROMs or make backups of your phone, etc. A cool custom ROM I recommend is CyanogenMod, it ports newer versions for older devices. So, you can have Android 6.0.1 in your phone

I screwed up and I'm on a Mac

Ok. So I am brand spanking new to rooting and flashing on the Turbo. I did it for a few years on the HTC Thunderbolt and the One. I followed the directions in the How To in the General subforum, used Sunshine, and then since I am on a Mac, I used Kingroot to root and then Flashify to install TWRP. I then did a full wipe in TWRP, installed the Brazilian ROM in the development forum, and then rebooted.
Then my troubles began.
It boots all the way to the "Select your language" screen, freezes, then reboots. Repeatedly. I can get into the stock recovery, but I can't find TWRP, so I figured that I had to install the linked kernel in the Brazilian forum. I installed it in the stock recovery, since I couldn't figure out how to boot into TWRP, but it didn't make a difference. Still freezes and bootloops. I've factory reset in the stock recovery, but nothing. I made a newb mistake and failed to make a backup of my original stock rom, and now I don't know what to do. I have a feeling I have to figure out how to connect to the phone storage via the Mac and load something else to install, but I don't know what. Help! Also, since I factory reset, I no longer have the Brazilian ROM on my phone. What the hell do I do?

Not a Mac person...
I'd find a Windows machine and flash the original firmware and start over. ... Never used it myself
But I believe the software is called rsd lite.

I figured it out!
Sent from my XT1254 using Tapatalk

Do tell?

I expect the OP followed the wrong instructions? They mentioned using Kingroot, which is NOT recommended for rooting these phones. Sunshine is all you need... I figure he had issues because Kingroot has issues....
The joke response I was going to give was: "I screwed up and I'm on a Mac"... yeah, I agree... that's one hell of a screwup.

You have to use King root if you want to install flashify. Sunshine no longer allows temproot outside of sunshine.

This might help future mac users:
http://www.bestandroidblog.com/how-to-setup-adb-and-fastboot-on-a-mac/