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

Won't boot after flashing DerTeufel'S [ROM] Jellybean [4.1.1]

Hello,
I tried searching for my problem in the forums but I didn't find my exact setup and don't want to brick my phone. (Well maybe it already is)
I had Cyanogenmod 7 for quite a while and tried the Nightlies for 9 some months ago. In the early days of my phone I used ODIN to flash the newest Stock firmwares and then used the chroot kernel to root my phone and install cwm. Since then I installed Cyanogenmod 7 and later Cyanogenmod 9 Nightlies with cwm recover and there was never a problem.
Today I tried the ROM from DerTeufel1980 http://forum.xda-developers.com/showthread.php?p=28819140
I flashed the rom, the addons, the superuser and google now fix. Then I flashed the kernel Devil3_1.0.0-Rc5_datadata_i9000_CFS_BLN_CMC_20120719.zip and fixed permissions. After that my phone wouldn't boot. The boot animation was the old standard android logo.
I managed to get into Devil Kernel Recovery and thought to try a reflash of just the ROM but when I try to "choose a zip" it always tells me
E:can't mount /sdcard/
After that I flashed the kernel with odin and now the phone seems to boot but veeeery slow and it has a ton of flickering the whole time. The bootanimation is the cyanogenmod 9 boot animation. I got into Devil Recovery and I still can't mount the sdcard. And it seems that it doesn't detect my sim card.
I hope you can help me.
Edit: Actually after rebooting several times the boot sped up and I could get into the ROM. I still can't mount the internal sdcard though and I have no phone functionality. It seems that my IMEI number is gone.

Hey
Downgrade your sgs to 2.3.6 valuepack using odin3...
Then root it and use it for a day atleast..
Then flash CM9 nightly..use that for a day too..
Then flash JB...not the same one u did earlier..
Instead Goto teamjellybean.noez.in (ad www.)
Find d latest version of jb and follow the instruction there..
Cheers
Sent from my GT-I9000 using xda app-developers app

Thanks that's exactly what I have done and it worked.

I've seen a lot of folks saying that they might have bricked their phones when some issue occured while flashing a new rom.
Personally whenever I face issues, I just goto the Download mode and Flash a GB rom and then move my way up (GB --> ICS --> JB).
As long as you can go into Download mode, shouldnt be a problem

Fwiw, I lost my IMEI for the first time trying out the JBs. Not sure if it was Slim or DerTeufel's. I ended up with the kind that allows you to connect to your mobile provider, a fake but working IMEI. But when I saw that I tried to go to GB and it didn't come back automagically. And the IMEI was totally wiped so I couldn't even register on the network. Ended up getting to ICS and only then did Root Browser let me write to the efs folder.
Lesson, in short: make a backup zip of your efs folder (to preserve permissions) and double back it up using Nitrality from the Play store.
Glad you got yours back, too.
sent from a telephonic device

tchindalia said:
Hey
Downgrade your sgs to 2.3.6 valuepack using odin3...
Then root it and use it for a day atleast..
Then flash CM9 nightly..use that for a day too..
Then flash JB...not the same one u did earlier..
Click to expand...
Click to collapse
OK, so I'm *definitely* a crappy speed-reader, because I missed this part about waiting on each version. What does the waiting do? I'm now wondering if that means I need to use the phone and, with the restored /efs folder, sometimes later /dev/block/stl3 will repopulate itself with the proper info.

Hey
I asked to wait on roms coz it can just make a few things working...like data..if it doesnt work on 1 rom it would not (probably) work on the next update..(personal experience)..
Cheers
If my post helped, don't mind hitting the Thanks button..

[Q] JellyBam Stucks at bootscreen

Hello friends of the Optimus Black.
[Introduction]
Today i started the first time flashing and android phone. Before i modiefied & flashed firmwares of serveral AVM fritzbox devices to get more features. I use linux as my everyday OS, but installed Win7 because it seems to be easier when working with android devices.
[Problem]
My LG OB stucks at the bootscreen (flying rocket) after i installed the jellybam_p970.NIGHTLY_20121215.zip and gapps-jb-20121011-signed.zip.
I have used theese instructions:
[HOW TO]The Big N00B how-to! and [ROM 4.1.2 - 4.2] JELLYBAM [15/12] [Nightlies] [P970] [PA.AOKP.CM10] [ATOMIC] .
I do know how to handle the SmartFlash Tool to get bricked phone back to live.
One problem is, that iam not shure, if the used nightly rom is corrupt or if i may have used the wrong gaps file. I had to opent this thread, because iam not allowed to post in the developer section (which might be good, if the rom is corrupt)
Another problem is, that it id like to avoid a further unbricking-process with smarttool, just because it takes so much time to:
1. unbrick
2. turn on usb-debug
3. use blackjack to root
4. connect to wifi
5. register at google
6. install rom manager app
7. backup
8. factory reset (wipe)
9. flash
Is it possible to take a shortcut?
Many thanks for your help guys.
mellhen

Hopefully, there is faster way ! After more than 20-30 bricks i get bored with similar process to yours ;p
You just need to use THIS tool to convert your favourite stock firmware to smartflash format and patch it with CWM (recovery). Then, after flashing this converted firmware using SFT your phone will automatically reboot into recovery and you will be able to flash any ROM without rooting, installing cwm etc.
I don't remember exactly, but this tool should only work with v10-v20 firmware, so just download one from HERE from your country (or just with well working baseband) and let's simplify your life !

I have modified one. Many thanks for this tip. I will test it the next time the device bricks.
Do you know if i used the correct gapps file? I tried Version 10.
EDIT
[Problem solved]
After flashing an earlier nightly buld (14th of december) and the CM10 gapp file the OS starts.
Thanks for your help
mellhen

[Q] LG P990 won't boot after flash! Pls Help

Hello guys,
I'm hoping to get some help here, since I've lost 2 days trying to flash my phone with a custom ROM.
The phone was running Official Android 4.0.4 Ice Cream Sandwich V30A, and I did the following in order to flash it:
After unsuccessful rooting attempts with SuperOneClick (stuck at step 7) I found another way, using nvflash, following these instructions. Somehow I thought I need to unlock the bootloader first, in order to root the phone, so I did that first. After that, I rooted my phone with SuperSU Root as described in this tutorial, and also installed CWM.
I thought that I was ready for the flashing part, and downloaded a custom ROM along with the right GAPPS, and followed the instructions carefully.
First few attempts I got stuck at the beginning of rom flashing process, than I found a solution, where I needed to delete the first line in the META-INF\com\google\updater-script file, then the flashing came trough, but somehow to quick I thought.
After everything was wiped/cleaned/flashed I click on “reboot system now” after which the phone should reboot into the new rom, but nothing happens, the phone acts "dead", it won't turn on, or boot into recovery mod. I was sure that I've bricked my phone, but luckily I was able to get it back on using the APX method with nvflash and boot flash.
But then the phone starts with the official ICS 4.0.4, as if nothing was flashed.
After another day of searching for a solution, I've found out that there are different partitions for different rom's, than I realized that I was trying to flash
Android 4.2.2 Jelly Bean on LG Optimus 2X via Avatar Custom ROM
LG Optimus 2X P990 to Android 4.2.1 CM10.1 Jelly Bean Nightly
Jelly Bean on a ICS device wich logicaly should run on a different partition, so I downloaded a ICS based ROM EAGLESBLOOD™ ICS "AOSP" 4.0.4_r2.1 and got the same issue when flashing, where I had to delete the first line in META-INF\com\google\updater-script, but than the flashing process went trough and seemed more genuine than before as it took longer to finish, so I was happy for a moment, and rebooted the device, and voila nothing...he's deaaaad again.
Can someone please help me to find out where the problem lies.
Thanks for any help, I hope someone takes the time to read this.

No one here to help...
Finally I've managed to install TWRP over CWM with AIO Tollkit, to see if the problem was with CWM.
The flashing process/time seemed similar, but the phone actually booted this time, but not into the new "flashed" custom ROM, but into the old stock one which should be wiped/deleted...

Dont worry too much....
Just use the All In One Tool Kit by spyrosk.....just wipe everything....as I suspect that all your partitions have been disturbed.....for the link for this tool, check my signature
Flash the one from JellyCream.... (it is new bootloader ROM on the dev section) or if you want the 4.3 based CM ROM, then find the one from tonyp....
You will loose the data on the Internal SD card....if you have a backup on the external, then restore form it....
Edit: Eaglesblood ROM is not supported by the developers as far as I know....

Finally
Thank you for replying/helping :good:
As it seems, it was a bootloader issue (ord/new). My phone has the new one, and I thought that the ROMs I've downloaded
Android 4.2.2 Jelly Bean on LG Optimus 2X via Avatar Custom ROM
LG Optimus 2X P990 to Android 4.2.1 CM10.1 Jelly Bean Nightly
EAGLESBLOOD™ ICS "AOSP" 4.0.4_r2.1
would run with the newBL, since they ware recently updated or made, and there was no clear info about the boot loader version.
Now after 3-4 Days of struggling, I've tried a ROM which is made and clearly stated for the newBL,ParanoidAndroid v2.6 "p990-2.6-14-newbl-tonyp.zip" and flashed it without any problems. I didn't have to wipe the whole internal storage with AIO Toolkit, I've followed the usual flashing procedure.:victory::laugh::good: the new rom looks awesome. I hope that I won't have any lock screen or random reboot issues, like before.
Now I'm gonna help a guy, who has the same problem.

[Q] only boots into recovery

ive had the phone since at&t had it on display. rooted it and had various roms for the last couple years and never had any serious issues. last night i flashed jellycream v2 and then did a factory reset inside the rom. the phone prompted that it would reboot twice and that it was normal. it rebooted into twrp and did nothing afterwards. i rebooted it from the recovery and all it did was reboot back into recovery. i decided to flash a different version of twrp and still the same. then flashed clockwork and still got the same result. i wiped the bootloader and basically went through the rooting process again. flashed the latest version of twrp and the phone is still only booting into recovery.
i am at a loss because this is as far as my knowledge goes. its like the phone is stuck still trying to wait for that factory reset from the jellycream rom or something and it wont do anything else but load TWRP.

If factory hard reset will not work (with phone off, press power and volume up together for some seconds. You might want to try also holding home on the touch screen.) flashing firmware will fix it unless you have hardware failure, which I doubt.
http://forum.xda-developers.com/showthread.php?p=39269819
Part 1 can be tricky, so take your time and get that right before proceeding.

drastic00 said:
If factory hard reset will not work (with phone off, press power and volume up together for some seconds. You might want to try also holding home on the touch screen.) flashing firmware will fix it unless you have hardware failure, which I doubt.
http://forum.xda-developers.com/showthread.php?p=39269819
Part 1 can be tricky, so take your time and get that right before proceeding.
Click to expand...
Click to collapse
so far i get the grey LG screen with 'booti mmc_read xxxx' at the upper left with the hard reset. it only takes 2 seconds to show up but the phone shuts off if i continue to hold the power and volume buttons. ill read up on that link here.

I missed that you wiped bootloader. You need that . So you could maybe just install the wkpark bootloader in recovery. You would do 1 and 3 here (1.25a file is down the page)
http://forum.xda-developers.com/showthread.php?p=39130435
I think Jellycream actually requires you have it, if I remember correctly.
Not sure why factory reset would cause that issue, but it will definitely not start without bootloader.
Flashing firmware will also write the (stock) bootloader if that does not do it. It will also reinstall the OS if system is corrupt or missing.

I can't find the thread for Jellycream2. Would you post a link? Are you sure it is for P920/P925 (same device, one is AT&T branded. I have the Thrill P925). If it is not for those device numbers, you may need xbsall's unbrick guide.
Also, if Jellycream2 is based on ICS and you were on a GB ROM, you would likely have needed to first upgrade to ICS and then install the ROM.
I'm just trying to understand why a factory reset could brick your phone...

drastic00 said:
I can't find the thread for Jellycream2. Would you post a link? Are you sure it is for P920/P925 (same device, one is AT&T branded. I have the Thrill P925). If it is not for those device numbers, you may need xbsall's unbrick guide.
Also, if Jellycream2 is based on ICS and you were on a GB ROM, you would likely have needed to first upgrade to ICS and then install the ROM.
I'm just trying to understand why a factory reset could brick your phone...
Click to expand...
Click to collapse
ok basic rundown of what i did in the last year;
when first played around with rooted it about a year ago i used all-in-one to do it. i had already upgraded to ics using the lg mobile support tool prior to rooting. rooting went off fine until i installed a Beats Audio app from the play store. when the phone rebooted after it would be stuck at the grey LG logo. i didnt know what to do so i used twrp and wiped the whole phone. then i used all-in-one and flashed the ICS bootloader and did the flash kernel 4 fix or something its one of the last options to do. then using twrp i flashed ICS_V20_P20, Stock_V20P_Rooted, and a Thrill Update, the phone rebooted fine in an ICS rom but it ran like complete ****, so i tried various roms and the one i settled with was called OptimusRS V1. i used that up until 2 days ago when i flashed the jellycream rom.
after i factory reset that i tried to flash the different wkpark bootloader and twrp that came with the megatron tool hoping that would fix the issue. but it did so i reflashed the original twrp and ics bootloader from all-in-one.
failed to mention this before but i tried 3 different recovery files in between each attempt and it would flash and reboot fine but the phone would still do the same thing and just load recovery.
ill find links when i get off work today. thats the basic history of the phone though.

Hmm. Stil not sure then . Maybe a corrupt zip or you wiped something important. Flashing with LG Flashtool should recover it. And always make a Nandroid backup before installing anything from recovery.

http://forum.xda-developers.com/showthread.php?t=2392309
thats the jellycream rom.
im downloading the files for your xbsa rom at the moment. i do remember yesterday when i used the megatron tool i saw an option to flash the stock bootloader and recovery. i tried it but all i got was the pink LG logo then a security error message below it and the phone shut off.

Oh, ok, OptimusRS's ROM.
Hmm, I thought v20 was GB or something... If it is not ICS then that would be the problem. Also it does say there you need wkpark bootloader for that ROM.
Also, xbsall's v28B includes recovery but it is in system partition. I don't know if that ROM requires you install it from recovery partition or not.
If you still want Jellycream you should be able to flash xbsall's ICS v28B (the normal partitions one, not large partitions), then install wkpark bootloader 1.25a in recovery, then the ROM.

drastic00 said:
Oh, ok, OptimusRS's ROM.
Hmm, I thought v20 was GB or something... If it is not ICS then that would be the problem. Also it does say there you need wkpark bootloader for that ROM.
Also, xbsall's v28B includes recovery but it is in system partition. I don't know if that ROM requires you install it from recovery partition or not.
If you still want Jellycream you should be able to flash xbsall's ICS v28B (the normal partitions one, not large partitions), then install wkpark bootloader 1.25a in recovery, then the ROM.
Click to expand...
Click to collapse
well that breaks down that a bit better. my progress at the moment is step f6. when i connect the phone nothing installs though. it just reconnects and disconnects every second or so. im guessing its because i already have those files. dunno though. i cant get my pc to install the adb drivers for the life of me when the phone is connected in recovery mode.it sees the new hardware just cant find the files.

actually i got it. for some reason the phone wouldnt install anything until i put the battery back in at that step. i continued successfully to step M. the phone is setting up my google account at the moment.
will flashing the baseband be necessary if my apn and sim work like the phone is now? my provider is h20(canadian i heard) but im the usa.
HUGE thanks regardless

Cool :thumbup::beer:
The no battery part is just for driver install, which is fiddly for this phone. Sometimes trial and error is a factor.
The baseband you have now would be the one you had previously. If it works, no problem. The one in the v28B pack is supposed to be optimized for the v28B .bin file, but hey, whatever works.

drastic00 said:
Cool :thumbup::beer:
The no battery part is just for driver install, which is fiddly for this phone. Sometimes trial and error is a factor.
The baseband you have now would be the one you had previously. If it works, no problem. The one in the v28B pack is supposed to be optimized for the v28B .bin file, but hey, whatever works.
Click to expand...
Click to collapse
im only getting E for data. i tried to flash a baseband meant for at&t but it says failed after about 90 seconds. still no 4g though. i did flash the xbsav8 before i set my apn up. i might just go with an optimusRS rom again though. i was happy with it. probably not jellycream this time.

Baseband fail after 80 or so sec is normal. It means it worked. Check your baseband in android settings/about phone.
You might try speed test app to compare actual speed. ATT 4G icon is a lie on this phone IMO.
Now that your pc is set up you can flash any P925/920 bin. Kdz files (combo of bin and fls, there is another tool for flashing those files) can be extracted into separate bin and fls, but I have not done it. The advantage is you can flash baseband separately.
Xbsalls vX3D (see his page) with the P925G fls file gives me 4G icon on Straight Talk in the US, but I like his vR3D better, and I can't tell a speed difference, honestly.
I have not actually measured the speed in either, however.
And for either of those ROMs, you must flash his large partition version of v28B first...very important.

oh its definitely like 2g speeds. its pretty slow. i tried using my providers app and website and its saying the phone i have isnt registered to them anymore so it might be just that. if thats the case ill just bring it in so they can do that for me. when i rooted it the first time i wasnt getting any data and they had to re-register the phone to get it to work right.
my baseband says OMAPP4430/XMM6260. for comparison and/or confirm differences. i have no idea lol.
side question though; my sdcard still has recovery files for the optimusRS v1 rom i had on it. i really liked the setup i had when i made the recovery for it. Im tempted to reinstall it but im really not too sure if itll work or worse harm my phone again.

Lots of variables, but you must remember that xbsall's P940 recovery app he he uses has recovery in system partition. The recovery you had before was probably in recovery partition. They write restores from two different places. Probably you would get an error, but not positive. Understanding that may take some Googling...
If you try it, back up before trying to restore the old backup. Then you could hopefully restore if the restore fails, know what I mean?
Probably the safest thing is to use the all in one tool to install recovery in recovery partition and use that one to restore backup.
I do know when I have restored backups, I have wiped Dalvik, Cache, and Factory Reset (in recovery) and then restore. Then it works. Some people wipe system too.
You can usually flash to recover from a problem, but then you have to set your phone up again

Well I recovered everything. All settings and personalized stuff. Just everything. Everything is running normal again. Just now my data is saying im using an h20 microcell instead of just H20 with a 4g connection. This 2g stuff is for the birds. I'm almost thinking the firmware we flashed has something to do with it. The phone is functional though. Just slow and no mms. I haven't been able to find much on the forums about it. I'll poke around more tomorrow.
Sent from my LG-P920 using xda app-developers app

I'd try another baseband.