Hey,
i've buyed a used Milestone for christmas, and it was modded with cyanogenmod, but i was kinda laggy. So i decided to wipe and clear it as described here. But now, my milestone won't boot anymore, it's booting as normal, but at the screen where it show's "android", it is booting, the screen turns black and starts again at the "android" screen. Can someone help me fix this problem?
Sure you do "3 wipes" after flashing? boot to recovery and wipe data/factory reset if you didn't. If you did... Try another rom or flash the rom again.
I got a Milestone that is stuck at the Bootloader 30.04 screen with Err:A5,70,70,00,1F
Mem_Map Blank
Service Req'd
Now I am a TRUE NOOB yes
but I have RSD Lite and the phone connects it even install/flashes the VRZ_MB810_2.3.34_1FF_01.sbf and says it will restart but restarts right back to the bootloader,
I have tried reading on other threads and forums, but nothing ever answers my question,,,,what am I missing? is it bricked?
NightDragon666 said:
Hey,
i've buyed a used Milestone for christmas, and it was modded with cyanogenmod, but i was kinda laggy. So i decided to wipe and clear it as described here. But now, my milestone won't boot anymore, it's booting as normal, but at the screen where it show's "android", it is booting, the screen turns black and starts again at the "android" screen. Can someone help me fix this problem?
Click to expand...
Click to collapse
I had the absolutely same issue. What I did is simply flashed the sbf again then wipe and it works now!
Related
My i9000 gets stuck at the GalaxyS boot logo every time I try to start it.
First it shows the Samsung boot logo, then the logo of my provider (Drei) and then it gets stuck at the S logo. After some time the screen goes off but the phone stays on (the buttons light up when I touch the phone).
I read about others having the same issue but I can't even go into recovery or download mode.I tried several three button combinations but every single one gets to the same result-> the samsung logo shows over and over.
Maybe you know how to fix it?
Thank you.
P.S.: I'm sorry for my bad english.
First you'll need to state what you did to cause that to happen?
nwsk said:
First you'll need to state what you did to cause that to happen?
Click to expand...
Click to collapse
A longer time ago I rooted it and applied the One Click Lag Fix.
Everything worked fine.
But today I installed SGS-Tools from the market, installed the hacked camera and suddenly there was no camera installed at all.
I downloaded a Galaxy S camera apk and tried to install it but it couldn't install it.
Then I installed busybox and wanted to restart the phone but it won't start again.
Hi - need some advice on my Galaxy Ace S5830T.
For some history, I rooted it a year ago and installed clockwork mod recovery. Apart from loading a few apps that need root privelage I haven't done much to it, ie has standard rom etc.
The other day a couple of applications came up with the 'Force Close' Screen (internet, facebook). Normally I just click on OK and everything is fine, but whenever I ran either app I got a force close error straight away. Used my app killer to shut down everything running, still had same problem.
Switched phone off and went to reboot, now it displays initial "samsung" screen with web address, flashes the Telstra logo in a few colours, displays "samsung" in the glowing letters, then hangs for a while. Goes back to Telstra logo and repeats.
I can boot into recovery mode. I tried restoring the boot partition from a backup I made before rooting, but it made no difference.
I've tried wip;e data/factory reset, wiping cache, and restoring the image, but it's still stuck in the boot loop.
The fact that I can boot into recovery means, I assume, that the hardware is still all functional, so can anyone advise what to try from here?
Thanks.
Hi, I got myself stuck in a bootloop and would appreciate some help! I have a D415 and installed CM11 for D415, but I wanted to switch back to the stock rom. I used an image of the stock rom which I flashed using TWRP, and now I am stuck in a bootloop after the LG splashscreen, it just keeps showing the T-Mobile splash screen, then the screen goes black while still on, and restarts the T-Mobile splashscreen. I have never broken one of my phones where I can't get into recovery, as far as I know, so how do I fix it? I'd really appreciate the help!
Update:
Found out it just needed a full wipe! Remember to wipe system when changing Android versions!
CleanSweep93 said:
Hi, I got myself stuck in a bootloop and would appreciate some help! I have a D415 and installed CM11 for D415, but I wanted to switch back to the stock rom. I used an image of the stock rom which I flashed using TWRP, and now I am stuck in a bootloop after the LG splashscreen, it just keeps showing the T-Mobile splash screen, then the screen goes black while still on, and restarts the T-Mobile splashscreen. I have never broken one of my phones where I can't get into recovery, as far as I know, so how do I fix it? I'd really appreciate the help!
Update:
Found out it just needed a full wipe! Remember to wipe system when changing Android versions!
Click to expand...
Click to collapse
Glad you figured it out. Please edit your thread title and place "[SOLVED]", without the quotes, at the beginning of it.
Hi guys, I'll try to explain my problem:
My Milestone has been running the rom "cm-7.2.4e-umts_sholes" since two years without issues... until a few days ago: aleatory restarts and freezes. Yesterday, I turned it on and was stuck on "M" logo. Several restarts later, it shows the "2ndBoot - Kernel Restart in progress" logo and nothing else.
I tried to reflash the rom and encountered some issues:
Bootloader 90.73, I flashed the vulnerable recovery "vulnerable_recovery_only_RAMDLD90_78.sbf" and enter in recovery stock. When I tried to run the "OpenRecovery_2ndbootOR_v1_2" the OR doesn't start at all. Black screen, restarts and recovery stock again. Only the "OpenRecovery_v1_46_SHOLS_inkl_ext_mmcfix_parted_update" does the trick and starts the OR with red letters. After all the obligatory wipes, applied update from "cm-7.2.4e-umts_sholes" and then reboot system. And the same "M" stuck or "2ndboot" stuck screen. I tried wipes again, but no results.
So, I tried to go back to an earlier version and installed "SHLA_U2_02.02.0_USASHLSPERARLA017.0R_USASHLSPERARLAT_P037_A015_HWp2a_1FF" with RDSLite. It boots up Android BUT the touchscreen not works at all, even with several reboots. Tried to reflash Cyanogenmod from here, but the same issues above listed appears.
I really going crazy with this... Did I make some mistake at any point? Must I reflash the bootloader 90.73 if I found it? (besides all the webs containing all the .sbf's and bootloaders appears to be offline by now).
Any solution/advice you can give me please?
Thanks in advance and sorry my english, isn't my first language.
So,
I've been around my phone for a couple months now, as you can see here (http://forum.xda-developers.com/sprint-htc-one/help/couple-issues-replacing-camera-mic-t2982125) i've replaced alot of parts and initially had a problem with bootloader stuck on bootloop. I followed the link the user, coal686 posted and it worked. But the new camera and bottom speaker were screwed so i had to replace them again, i got stuck again on a bootloop but the guide is not working anymore (for me). Could someone give me some help? What else can i do? i've tried to flash twrp and boot to recovery but it just boots again to the splash screen , turns off and boots again :\
edit:I gave it another try and now it worked, i disconnected the battery for a while.