[Q] Milestone 1 - can't boot after the installation - Motorola Droid and Milestone Q&A, Help & Troublesh

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.

Related

[Q] ROM flashing keeps failing need help..

EDIT: Can be closed, fixed it by going into recovery and wiping data/cache, never had to do that before in other flashes so didn't know it was needed
Hi guys,
first of all I'm not another first time flasher, I already succesfully put 4 other roms on my galaxy s but now I don't know what to do..
I came from jm5 and wanted to upgrade to jm8 today so I back upped everything and started the process, I thought I'd best follow richthoven's instructions so I first flashed the pit file + repartition, and then after pass, removed battery, back to download mode and put pda,modem,csc etc like always and started flashing.
Now my problem is from what I remember after the final reboot before odin sais pass the s logo dissapears and the phone boots into touchwiz, but now after the s logo dissappeared, my screen just stays black and after a minute or two odin sais passed, but there's nothing on my screen, and even after disconnecting and removing battery and try to boot it hangs on the s logo for a few minutes then a black screen with the backlight buttons highlighted.
Any help here would be greatly appreciated!
PS: I already tried the flashing procedure twice, same result

[Q] Milestone Bootloop

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!

Stuck at boot logo..

Hello everyone, I'm facing a problem where my n7000 which running a supernexus 2 milestone 1 stuck at boot logo. first, it started with random appearance of 'gapps.google.com has stopped working' message every 10 minutes or so. Since the messages start to appear, my stock browser which come with the rom are no longer can be use. and this morning, I'm using the phone as usual and suddenly the phone reboot, and stuck at the boot logo. Any idea on how to fix this?
Flash the rom again on top of this. If this still gives problems, you will need to wipe data.
full wipe.. flash philz kernel.. reboot recovery.. full wipe again.. flash rom..

Custom Recovery issue (XT1068) (Solved)

Hi everyone, I'm having a weird issue since this morning and could not solve it yet, maybe someone can help me.
Basically I tried to dirty flash the new nightly of CM12.1 using TWRP 2.8.6.0 and it got stuck. After rebooting the device I could not get to twrp anymore (strangely) and then I tried to reflash it (two different versions) with no success.
With my device being in this state (without booting into OS and with no recovery access) I had to download the stock 5.0.2 for the XT1068 and flash it using fastboot. It can now boot up normally into stock ROM and restored the stock recovery, but now any custom recovery I flash it does not work. I had two different results on two versions of twrp:
2.8.5.0 - After flashing it and trying to access it the device shows the "unlocked bootloader" screen and then reboots itself and goes to the ROM without even getting into TWRP.
2.8.6.0 - After flashing it and trying to access it the device goes to the "unlocked bootloader" screen and freezes there. I have then to hold the power button for a long time (about 1,5 min) and then the device boots the stock ROM.
Anyone can give any idea of what I can do? I even tried to lock and unlock the bootloader again, flash CWM, flash TWRP and nothing. At least the device is booting, so it is not a urgency, but any help is appreciated!
----------------------------
I got it, a stupid reason for all issues I was having. The issue was with my router, that was set to use a internal firewall which was screwing up a lot of my downloads, and the ROM and TWRP files just got into this issue.
After reconfiguring my router everything worked out, which make me fell stupid for not thinking about this before hahaha, but at least it is fixed
Thanks for everyone who took a time to read this and sorry for any inconvenience!

[Q] Possible partition corruption?

Here's the deal, I have a sprout8 device (the Indonesian Nexian Journey One) running stock 6.0 with some xposed mods installed on it. Suddenly the device shuts down and when I try to boot it up it only goes halfway through the bootanimation when it shuts down again. I wasn't too worried as I thought it was just a conflicting system issue and I also thought it was time to re-flash fresh stock 6.0 to freshen up my phone anyway. So I went ahead and did it.
Here's where the problems start to show up, I had a hard time booting to recovery through the power + volume up combination. The phone suddenly shuts down on its own as it boots up. I tried it a few times and finally got to recovery. After that, as I flashed stock 6.0 the phone shut down again. I thought it was an issue with my recovery so I tried wiping everything through fastboot and re-flashed recovery through fastboot aswell. From there I tried again to flash stock 6.0 through recovery and again, the phone shut down. I tried a different ROM thinking it was a ROM issue but still got the same results.
After hours of trying to flash a ROM through recovery (retrying over and over as it suddenly shut down while flashing), I finally got a ROM installed. Then I rebooted my phone, but again it freezes halfway through the bootanimation (literally freezing the bootanimation) and refused to do anything. I took off the battery and booted up the phone countless tries trying to get it to boot up. When it finally booted up, I filled in all the Google startup credentials and finally got started on a fresh stock 6.0. However, I tried to restore my previous application data through Android's application recovery on startup but everytime the device installs a new application it would freeze up and shut down. This happened countless times. Then the phone, once again, shut down and could not start the ROM. It would freeze up on the bootanimation.
Then things started to get weird, when the phone turns on it should show the "Nexian" logo in all its glory before going to bootanimation. But here the screen gets all distorted and shows these weird horizontal (and sometimes vertical) lines. Nothing's wrong with my phone screen so I assume it is a system error. From here on, the phone refused to boot. It just shows the Nexian logo and restarts over and over. The same thing happens even after I re-flashed both my recovery and ROM. I even tried using SP Flash Tool to re-flash stock but still the same results.
Now, the device wouldn't even turn on. But when I connect it using USB to a Windows computer, it still gets detected through device manager as an ordinary MediaTek device.
I'm assuming now that it may be a problem with the /system parition where we install our ROMs in. The partition may be (partially) corrupt. Seeing as the device could still boot the ROM a few hours ago but freezing upon updates to the stated partition.
If you guys have any other ideas/solutions I'm all ears.

Categories

Resources