[Q] Kinda Bricked My Milestone - Motorola Droid and Milestone General

I had a perfectly running milestone on SHOLS_U2_02.27.B (Arabic Build). I flashed the phone using rsdlite 4.9 using G.O.T. 2.2.1 UK sbf. Everything worked perfect and the phone booted up and I had android 2.2.1.
When I tried to get into recovery mode nothing happened. I tried using the camera+power and x+power and it still didn't work.
I rooted the phone using universal androot and used quick boot to boot in recovery. I got the exclamation mark in a triangle, however, pressing the volume up and camera didn't work after like 50 tries.
I thought that something was wrong so I flashed the phone back to my original build using rsdlite.
Rsdlite works fine until it reboots the phone. The phone gets past the motorola logo however it gets stuck on the android logo. The android logo appears disappears appears... and so on. I left it there for 30 minutes and the same thing kept happening.
I reflashed back to G.O.T. UK 2.2.1 and it worked again, no problems.
I tried many official builds (UK 2.0, Arabic 2.1,Arabic 2.1update2,UK 2.1) and I get the same results.
I tried the G.O.T. 2.2.1 Telus sbf and it worked.
So to sum it all up, I can't flash anything but a G.O.T. build and I can't get into recovery mode. I can only get into bootloader.
Thanks for any help in advanced...

im new to moto droid , but if it seems to be bricked try a unrooting guide, that tends to get you back to were you need to be.
and if that does not work i say trying to download rom manager and flashing " clockwork recovery"
hope this helps bro

I tried rom manager and the main problem is that I can't access recovery so any unrooting/recovery guides are useless.
At this point I believe that the phone is damaged. I think I'll just flash it with an official rom and then return it as non working.

Have you tried restoring nandroid via ADB?

Hmm I have no idea how, could you tell me how or link me to a guide please?

Have you tried flashing the 90.78 Bootloader? cos this Bootloader allows you to enter the recovery mode by pressing the 'X'+power button and volume up+camera button after the triangle with exclamation mark appears.
Don't forget to extract G.O.T OpenRecovery.zip/Androidiani OpenRecovery.zip at the root of your sdcard. Once you've entered the recovery 2e(all the alphabets are in blue), select apply update. Without OpenRecovery installed in your sdcard,the apply update is useless.
If those method still couldn't get into the recovery mode,i suggest you need to flash vulnerable_recovery.sbf after you flash to stock ROM or any one you like. Google for OpenRecovery_v1_46_SHOLS. In the zip file contains the .sbf

I am on the 90.78 bootloader, I tried everything you just said before and nothing works. At this point I believe it's a hardware error. I will just flash the phone with the official sbf and replace it using warranty. Thanks for the suggestions though.

Related

[Q] Think I screwed up?

Ok so I have an unlocked Nexus One that I rooted when I first got the phone 6 months ago. I've been running CM6 no problems at all, everything has been great.
Heres where my problem starts I decided to flash the stock frf91 image onto the phone and did not check superuser permissions or whatever option they gave me before i did it. I was doing this because I thought I was selling my phone. Now I'm not and want to go back to CM6.
The problem is I cant get into recovery at all I get the error with the ! in a triangle with android standing next to it. I've searched everywhere and tried everything. Fastboot and ADB gives me errors like waiting for device (even though my drivers are up to date and it recognizes the phone?) or status failed too many links.
I tried doing a backup from my nandroid information through my nandroid backups on my computer (aka pulling system.img etc) I tried going through the terminal but Im getting denied superuser permissions.
Im just not sure where to go from here ive looked through so many articles and threads and posts and im very confused.
After I flashed the stock image I thought i would still be able to boot into recovery but i guess i dont have recovery? I try to flash the recovery but with no avail.
Anyone have any advice or even just somewhere to start I would really appreciate it. Thanks
When u flashed the stock rom it wasnt a rooted version so u have the stock recovery search for how to root the stock Rom once rooted u can put a custom recovery on there hope this helps
The procedures for the different handsets kind of blur together in my memory, so just want to check.
When you booted into recovery and got the "!" screen with the android did you try holding either the volume up, or volume down key <along with the power button> to bring up the menu?
The ! With the Android is the stock recovery image if I remember correctly if u press the power button the menu should pop up

[Help] Bootloop and Corrupted Recovery

Hi Folks,
I had a CyanogenMod-6.1 for Nexus One :: V6.1.0-RC1 (10/28/2010) installed on my Nexus 1.
Prior to that i was using CM6.0 RC1 stable release. Did an upgrade (with full void and nandroid backup) to try out the new features.
However this afternoon, out of nowhere, my volume buttons and trackball started to malfunction.
i.e to say : I cannot adjust volumes in any part of the apps/phone and i can't select/click stuffs with the Trackball.
Hence, I thought of removing CM6.1. Here's the problem started.
#1. I can't boot into recovery. The phone itself will be stuck at the big "X" screen. After 5mins, it will boot into CM6.1
- Using ROM Manager i tried to reflash Clockwork Mod 2.5.1.0 for a couple of times but i still cannot get into Recovery.
Be it powering up with trackball held down, booting into recovery up via Rom Manager. Surprisingly, volume down was working together with power down was able to go into Bootloader
for me to select "Recovery", however, i still can't access Recovery.
#2. I tried using ./fastboot-mac flash recovery updatedclockwork.img also can't.
#3. I tried using Amon-RA. ./fastboot-mac flash recovery Amon-RA.img also to no avail.
#4. i used ./fastboot-mac update to load a StockFRF91 Froyo also can't get into recovery.
As of now, my phone is stuck continuously in bootloop, cannot access Recovery. I've tried almost 30+ fixes on XDA and other Android Forums but i still can't fix it.
Is there anyway, i can wipe everything inclusive of the "Corrupted Recovery" files and restore back my Nexus One?
Thank you all please save my phone! :'(
Dude I feel your pain. I have the exact same problem. I wonder if it is a CM6 issue?

[Q] Nexus One stuck at X/ No recovery

First of all, I have checked around quite a bit on this forum as well as others to try and avoid having to ask a question that's already been answered. Here's my problem/ what happened. I was rooted (one-click with locked bootloader) and had tried out several roms for a couple of months now. A few days ago I reverted back to an old stock 2.2 backup. My phone received two ota updates and I'm pretty sure I lost root. I had just went on using the phone for about two days when I ran into a problem today. After shutting the phone off I have now become "stuck" at the initial "X" screen (not animated). I pulled the battery and tried again several times. I then tried to reboot into recovery from the bootloader/ 3 skateboards screen with no luck. Any time I hit recovery it simply takes me back to my stuck "X" screen. I have an entire backup of my SD card from earlier as well as at least 4 nandroid backups (one of which was the stock 2.2 before the latest ota). I am thinking I need to somehow put clockwork recovery back on my phone so I can restore to one of my backups. I do not know how to do this. Sorry for the lengthy post but I want to provide as much information as possible. Any help at all would be greatly appreciated.
Just like you restore to stock 2.2. You should have used recovery.img. use adb fastboot to put the stock or anom recovery. I am not am expert but I have had the same problem few times. Always use adb commands
Sent from my Nexus One using Tapatalk
Does my n1 have to be in usb debugging mode because it's acting like it's not connected or something. I get the message "error: device not found." I'm on the fastboot screen on my n1 and using terminal on a mac. I usually didn't leave debugging mode on
No it doesn't but you have to have the drivers installed as well as the SDK with dependencies.
Whew! Thank God! I ended up getting a FRG33 stock rom onto the sd card and the bootloader detected it. I'm not sure what happened but when I tried recovery after that it took me to the android with an "!" point (meaning no recovery?) and then back to the X. This time however it loaded on through and went right back to the way it was before it was stuck. Again, not sure what happened but thanks for the replies and help.
fastbook oem unlock
install Amon RA recovery
flash new rom.
Caseyp789 said:
Whew! Thank God! I ended up getting a FRG33 stock rom onto the sd card and the bootloader detected it. I'm not sure what happened but when I tried recovery after that it took me to the android with an "!" point (meaning no recovery?) and then back to the X. This time however it loaded on through and went right back to the way it was before it was stuck. Again, not sure what happened but thanks for the replies and help.
Click to expand...
Click to collapse
The exclamation mark is just the stock Android recovery - it was re-installed when you loaded the stock FRG33 ROM.
Performing OTA updates requires you to have the stock recovery installed. Simply reverting to a stock 2.2 nandroid isn't sufficient, so trying to install those OTAs (which should have failed without stock recovery) may have broken something there.
GldRush98 said:
fastbook oem unlock
install Amon RA recovery
flash new rom.
Click to expand...
Click to collapse
This is by far the easiest (and safest) way. Google/HTC provided us an easy and safe method for gaining full access to our phones.... Why so many people refuse to use it is beyond me. If you root it the proper way (with fastboot oem unlock), it will make recovery from any further issues a lot more simple.
From what I can tell, I am having the same symptoms as the topic creator. I believe the problems started during a failed flash of cyanogenmod 6, but I am not sure by what means the flashing took place.
I can't boot the phone normally, it hangs on the X splash screen and the same occurs when trying to enter recovery mode.
I have tried the passimg approach to fix this, it either doesn't recognize my zip or starts loading it and freezes on a loading bar.
Fastboot flashing recovery completes, but doesn't fix the issue.
I can fastboot flash every image partition except system or radio, both hang.
As danger rat and dude random both know, I have posted this problem on the nexus one forums but I thought I'd post here to have some more minds look at it.

[Solved] [Milestone] Clockwork not working at all

Turns out I had missed the part where you had to flash it with a vulnerable bootloader.
Hi, trying to install some custom roms after it turns our Motorola Europe sucks magnificently. But Clockwork Recovery isn't working, neither "boot into recovery" from Rom manger, nor booting into it manually via update.zip.
What happens is:
1. Phone out of box icon. Loads half way
2. Phone next to ! triangle, half a second
3. Reboots like nothings ever happened.
Any idea what could be wrong? It's rooted and everything should be in order that way.
lol newb!
u cant use clockwork on milestone !!!! bootloader is locked .......
But there's a own Clockwork version for Milestone, and all guides requires to use it? It was to my understanding that there have been workarounds.
you will need to use the bootstrap type recovery
but i try the all recovery for milestone but they cann't format the boot partition on my xt720 froyo

[Q] Can't boot into recovery / flash vulnerable recovery

Hello,
I got now 3 Milestones (+1 as "spare parts donor"), but Nr. 3 is making problems.
After I got it, I tried to do the normal stuff: Flashing Vulnerable Recovery 90.78, going into Recovery Mode and OpenRecovery, and then installing CM7. I did that quite some times, but now it does not work at all.
The phone is on 90.73, by the way.
1.) Flashing 90.78 does work in the case of RSDLite is running through successfully.
But after rebooting in bootloader mode, 90.73 is still shown.
And more funny: I can flash the BL_9073_umts_sholes_HS_Consumer_replacer.sbf, BL_9074_umts_sholes_HS_Consumer_replacer.sbf and BL_9078_umts_sholes_HS_Consumer_replacer.sbf files anytime, and the version change is shown properly - and I even can DOWNGRADE. I thought that was impossible...
But flashing to 90.78 in case of the version from our awesome nadlabak does not work somehow...
2.) I can boot into the recovery mode and come to the Yellow Exclamation Mark / Triangle sign. But thats it. I can press volume up and camera button as long and in many ways as I want. I did even change the casing and button part to make sure this thing isn't broken - it is working! I just can't enter the recovery mode...
As I tried that last night for serval hours and this morning, I kinda like "give in" and try to ask you, wheter you got any idea !
( Or is there any other way to get an recent version of CM7 to the phone. Maybe some sbf file? )
I also tried flashing the O2 2.1 full file, did not boot from bootloader to android to prevent any OTA problems and such. It just did not make it !
Thank you very much,
Xeno
Maybe vuln. recovery sbf contains only recovery. So you should flash 90.78 bootloader by other means. And then vuln. recovery.
mrvek said:
Maybe vuln. recovery sbf contains only recovery. So you should flash 90.78 bootloader by other means. And then vuln. recovery.
Click to expand...
Click to collapse
which sbf do you usally use?
thank you very much for your answer!
Here you can find the bootloader images: http://sbf.droid-developers.org/umts_sholes/list.php
Yeah, I tried these already.
Flashed to 90.78 and then applied the vul. recovery 90.78.
But - I still can't enter recovery mode .
Is the bootloader version displayed in bootloader mode correctly?
What is the issue with entering recovery? error messages, something displayed on screen...?
And most importantly:
1) Have you verified that recovery is correctly placed in /sdcard? i.e. OpenRecovery folder and update.zip are in their place.
2) Have you prevented booting to Android OS after flashing vuln. recovery and deleted /system/etc/install-recovery.sh (or made sure it is not there)?
Ok, I got it done now.
I planted the motherboard into another milestone.
I did upgrade the Bootloader to 90.78 and then flashed the Vulnerable Recovery after that.
Then I booted into Recovery Mode and could access it, via Pressing and Holding Volume Up and then Pressing Camera Button.
From then on, flashing CM7 was a piece of cake.
Seems like the button weren't working that good.
After all the stuff I reinstalled the Motherboard in the old casing and found out (after booting into Recovery Mode, which entered itself automatically to OpenRecovery...) that the Volume Down Button is almost not working and the Volume Up Button only with a big "lag" of about a Second. Camera Button however is working fine...
Very strange, but however, I got CM7 on it, and I am fine with that now.
Thanks to all of you for your help !

Categories

Resources