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

SMS and Lollipop 5.1.1

Hello,
I rooted my phone, installed SuperSu, Xposed with Xprivacy, etc. and everything works fine. Except SMS. I didnt noticed first because I dont wirte much SMS. I read others have the same problem. But I didnt find a real solution. They reflashed or Wiped everything (not allways a success) and on my phone ohter SMS apps doesnt work neither. I dont want to setup everything again if possible.
Is there no FIX/Patch which I can flash or a simple workaround ?
Regards liqui

Flash back to 4.4.4 ( i used .93 fw ) , root and install xzdr , create a new flashable rom with prf creator 1.1 ( None Below! ) including fotakernel kernel and modem. Wipe data, do a factory reset via TWRP And flash the newly created clean rom.
Seems prf creator 1.0 wasnt able to handle the modem files... :/

Hi,
I flashed the 5.1.1 agian because I didnt want to wait. This time it works. Did nothing different then the first time

liqui666 said:
I flashed the 5.1.1 agian because I didnt want to wait. This time it works. Did nothing different then the first time
Click to expand...
Click to collapse
By that you mean you flashed the latest ftf via flashtool?
I'm asking because I have the same problem, except one specific third party app is working, while another doesn't.
Thanks in advance

Hangouts figures to work, but in fact it doesn't. You can recognise it by switching back to stock messaging app, then the "send" SMS are gone. The solution I gave already. That's the simplest way to fix it with Bootloader locked, otherwise root will be lost. UB devices should fix it by flashing the actually used fw by flashtool with a full wipe, flashing a kernel with including recovery. Now just flash the latest SuperSU via recovery

You are totally right, I just hoped there would be another, simpler way. But I got it working again yesterday using your advice. After a little bit of ol' try 'n error I'm convinced it had something to do with the data partition, because when I restored the TWRP-backup, SMS function was lost again, but could be recovered by another wipe. That said, I first was on a prerooted firmware created with PRFC 1.1 and latest firmware but flashed SLiM ROM by wajk over that, so I don't know if the error lay within that ROM, but I'm not in the mood to try any time soon.
Cheers

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

[CLOSED BY OP] No more sound (including calls) on EMUI 5/Nougat ! Please help !

Hey guys !
I really need some help. I installed Nougat on my device and it worked fine. I even rooted it using these files : https://forum.xda-developers.com/huawei-p9lite/development/twrp-t3588356
Everything worked fine. I could even do Nandroid backups with apparently no issue. But I think this occured when I restored.
Now I don't have any sound at all, including when someone calls me. I don't think this is hardware related. Plus, boot logo shows "android" instead of "honor".
Please tell me I can do something. Flash some file ? I tried the factory reset and wiped everything from TWRP with no luck...
Edit : Phone sent back to customer service. For your sake, I recommend you to be careful if you decide to use this TWRP. Everything seemed to work fine before I flashed a nandroid backup (I'm pretty sure this is what caused the issue), but one can never be too careful. My advice ? Don't use it on your daily device, wait for an official TWRP release (meaning stick with the stock ROM if you want EMUI 5/Nougat) or stay with Marshmallow for the time being if you need root.

problems when going back to stock rom (lineage 17.1 working fine)

hallo guys, i have issues when i try to go back to a version of the stock rom because they wont boot
not sure what im doing wrong, i hope someone can tell me..
here the full story: when i got the device, i checked the stock rom which was ok.
my plan was to use lineageos, so i unlocked the bootloader,installed TWRP and flashed the global vendor, unofficial 17.1 and gappswhich.
this is working fine and i can always reinstall this lineage the way i mentioned above, but i saw that the finger unlock is not working in that rom as expected.
since i didnt test it in stock rom, i thought lets try this and now comes the issue, i can not find any solution to go back to stock rom which is working.
#1 tried to download rom from https://mi-globe.com/miui-firmware-rom-builder-features/19/ which should be flashed with TWRP (howto there).
when flashing, this is not finishing and looks like its stuck in twrp flashing. ok, since the download for other config was broken yesterday, there might be issues.
#2 downloaded stable rom from https://forum.xda-developers.com/k20-pro/how-to/rom-miui-11-xiaomi-eu-t3984691
flashing works, but device is in boot loop then. im sure i was missing something or doing wrong, so i searched for another option.
#3 found a youtubevide about BACK2STOCK https://www.youtube.com/watch?v=KBsWNrKNZzA
downloaded all the needed packages and did it like it was in the video.
result: all flashed like shown in the video, when system reboot is done MI logo is shown around 60seconds and then rebooting to TWRP
#4 i would go for the solution to flash via MIFLASH, but before i break something i thought i better ask here.
since there are so many issues, i would need your help to point me to the mistakes im doing here.
going back to lineage 17.1 is not a problem, i just did again and this is working.
so if you read this, please find time to explain me if you want to.
thank you

yeah, you are missing a step.
you have to format data partition.
check my guide on how to install roms: https://forum.xda-developers.com/k20-pro/how-to/simple-beginners-guide-to-raphaelin-t4020543
also, may I suggest EU/masik instead of stock, its a lot better

in #3 you can see that in the video data is also formated: https://youtu.be/KBsWNrKNZzA?t=190
of course i did this too....was also not working.

reading your simple beginners guide and downloading MIUI EU ROM (xiaomi.eu_multi_HMK20ProMI9TPro_V11.0.5.0.QFKCNXM_v11-10.zip)
flashed it, was also not working/booting. tried also with flashing vendor (the one from lineage) before, no change.....
what should i do?

motorh3ad said:
reading your simple beginners guide and downloading MIUI EU ROM (xiaomi.eu_multi_HMK20ProMI9TPro_V11.0.5.0.QFKCNXM_v11-10.zip)
flashed it, was also not working/booting. tried also with flashing vendor (the one from lineage) before, no change.....
what should i do?
Click to expand...
Click to collapse
Don't flash vendor, theirs no need, eu.miui has everything in the one zip file. Just to clarify have you formatted in twrp? The option where it requires you to type 'yes'? Everything gets wiped from your photos and apps all to the rom itself. Then just flash eu.miui and reboot. Works everytime for me without fail.

no i never formatted in TWRP wipe, only used the factory reset and swiped to wipe.
just did a format and flashed xiaomi.eu_multi_HMK20ProMI9TPro_V11.0.5.0.QFKCNXM _v11-10.zip
ITS BOOTING!!
first please let me thank you very much for this help, i was already quite desperate about nothing working except LINEAGE.
fingerprint in MIUI rom is working great, unbelievable!
can you please explain me why this FORMAT in WIPE is needed and what its used for? i was not aware and i can not find it in any of the howtos..

haha, glad it's working. Knew the problem was that you didn't format.
however since you posted on xda, I just assumed you knew format data is not the same as wiping data.
(literally, the most common beginners mistake for this phone)
it's cause of the encryption keys, when moving from MIUI to AOSP (and vice-versa) a format data partition is required.
I stated this in How To Change My ROM? I wanna Try them all!
section in the first post.
under there, FOR MIUI ROMS (since that is what you were trying to do)
you missed the 7th bullet point. (you can also text me on telegram)
(also, in the same guide, I inform people to flash their vendor first -4th bullet point- then in the 5th bullet point you wipe it.)
(this is cause often miui customs and some people are usually on a vendor that isnt there's. you have to be on your region vendor, then wipe it, then allow the miui custom's vendor to take over, else you will face fingerprint problems)
This is just another point most just don't follow.
Umm, if my guide needed anything to be included, or like... needed to be more easy to read and follow... I can edit that if you like.
(use can text me on telegram as well)
edit: just read the xiaomi.eu one, I'll edit it to make it more informative

motorh3ad said:
hallo guys, i have issues when i try to go back to a version of the stock rom because they wont boot
not sure what im doing wrong, i hope someone can tell me..
here the full story: when i got the device, i checked the stock rom which was ok.
my plan was to use lineageos, so i unlocked the bootloader,installed TWRP and flashed the global vendor, unofficial 17.1 and gappswhich.
this is working fine and i can always reinstall this lineage the way i mentioned above, but i saw that the finger unlock is not working in that rom as expected.
since i didnt test it in stock rom, i thought lets try this and now comes the issue, i can not find any solution to go back to stock rom which is working.
#1 tried to download rom from https://mi-globe.com/miui-firmware-rom-builder-features/19/ which should be flashed with TWRP (howto there).
when flashing, this is not finishing and looks like its stuck in twrp flashing. ok, since the download for other config was broken yesterday, there might be issues.
#2 downloaded stable rom from https://forum.xda-developers.com/k20-pro/how-to/rom-miui-11-xiaomi-eu-t3984691
flashing works, but device is in boot loop then. im sure i was missing something or doing wrong, so i searched for another option.
#3 found a youtubevide about BACK2STOCK
downloaded all the needed packages and did it like it was in the video.
result: all flashed like shown in the video, when system reboot is done MI logo is shown around 60seconds and then rebooting to TWRP
#4 i would go for the solution to flash via MIFLASH, but before i break something i thought i better ask here.
since there are so many issues, i would need your help to point me to the mistakes im doing here.
going back to lineage 17.1 is not a problem, i just did again and this is working.
so if you read this, please find time to explain me if you want to.
thank you
Click to expand...
Click to collapse
You're not installing stock ROMs. You are installing custom ROMs based on stock.
If you want to return to true stock grab a fastboot ROM from here and flash it with the Mi Flash Tool. After fully extracting the ROM delete the flash_all_lock.bat file before flashing. That way you cannot accidentally lock the bootloader.
Then choose the 'clean all' option in the Mi Flash Tool before you hit the flash button.

thank you.
my mistake, i didnt write clear. i just wanted to test a miui rom to see how the fingerprint is working there. im happy now with the custom rom based on stock.
but i also went for this solution you mentioned and noticed that on the https://www.xiaomiflash.com/ site only older xiaomi devices are mentioned as beeing compatible.
looks like this is not the point, so im happy to have this option too.