Hi, all
I have a non-booting Mini, which has not been rooted. In an ideal world, I'd just like to fix the bootloader, then look at options for a newer ROM.
I can boot with the key combination, to the 'Install OS screen', but because the device isn't in 'Developer' mode, I can't get any further. I don't have a Windows box, so haven't been able to try to use Odin, but did try to use Heimdall (without success) on various Linux distros. I got confused doing this.
I was wondering if anyone with a bit more experience with this device, could help, for a fee. I've considered getting it professionally fixed, but most places just fix 'supported' (current) 'phones.
Can anyone, ideally in the UK, have a look?
Cheers,
Chris
Related
Hi, i bought a motorola milestone from ebay and was working fine so i decided to upgrade to android 2.1. now the touch panel on the phone does not work and cant find any information on how to fix this. i am getting very annoyed to the point where the phone will come in contact with the wall very hard. if anyone can please help me try and fix my amazing phone then you can contact me on here or at carter_noel at hotmail dot com. thanks guys
First, make sure you applied the right firmware update for your phone...there's several versions floating around depending on what market you live in and putting the wrong one on your phone can create issues (but usually just connection issues, not screen issues).
Did you do an Over The Air update or USB? It's possible that even if you used the right firmware, that the update wasn't applied properly, and that can cause all kinds of problems.
You can always manually re-flash it with RSD Lite via USB. Keep in mind that will wipe the phone just like a factory reset.
Very clear instructions and download links for all version of the Milestone here: http://androidforums.com/all-things-root-milestone/75460-milestone-2-1-update-root-guide.html
It's a better guide than the one here on XDA.
thank-you for replying to my problem. could it also be to do with the version of windows im using as it windows 7 64 bit but need to reinstall as loads of problems with various things including .net framework (which might be the problem?). which operating system do you or anyone reccomend to use?
I just wanted to relay my experience for anyone who might run across the same problem. There are so many solutions (some good, some bad) that I thought I'd try and help someone else out that was in one of these situations. Keep in mind, the solutions are all here at XDA, I just had to dig and try a few things.
This Captivate was on a Ginger Clone rom (2.2) from about a year ago and I wanted to go to Cyanogenmod. I personally run Cyanogenmod7 (181), and was trying to replicate that.
[Boot-Loop]
I Attempted to clear caches and go straight to Cyanogenmod. This may have been an inexperienced guess that I might be able to do this, but I know a few other folks that manage to do this. I ended up in a boot loop
[Getting to Download mode]
Can be frustrating, but seems to be if you have the usb unplugged, battery out, sim out, put the sim in, battery in, usb in (phone will turn on, so you have to move fairly quickly) and then hit the up and down volume buttons it will go into download mode.
[Go back to Factory]
I tried using the Odin 1 click solution. I believe there are more than 1 versions of this, but it would just get stuck at "Do not turn off target". I decided to try something else. The Java based Hemidal 1.3 aka "SamsungCaptivate-SGHi897-UCKB2-Rooted-One-Click.jar" seems like it is very well written and very easy. It has you update a driver in the mix and it works fantastically.
[Now I'm at Stock 2.2, rooted]
Need to turn on USB debugging, and I was expecting to be able to put
on the rom manager by copying over a file, naming it update.zip but it won't run due to some signing restriction.
[Unable to run any scripts or update.zip]
http://forum.xda-developers.com/showthread.php?t=833423
Basically, you need to turn off signing
[Went off the tracks, bricked the phone]
I decided I would try and apply the Cyanogenmod rom a different way. I went to their wiki and tried to use their Hemidal 1.1.1 update suite and script. I ended up with a brick. I didn't panic, I used the below url and it worked to get me back into download mode. I then used the previously successful Hemidal one click to fix it.
http://www.traemcneely.com/2011/05/...e-possibly-vibrant-kernel-error-black-screen/
I went back to the 3e recovery installer, ran that script, it worked and let me run unsigned code, I installed rom manager via update.zip, and from rom manager I was able to apply Cyanodenmod 7-v181 and then the Google apps and I was happy. Took about 2 1/2 hours to go through all that. Kind-of a pain... happy now.
Rich
Wish I had your kind of luck
I have a Captivate that isn't "bricked" per say but when I plug it into my computer when it's in download mode I only ever get "unknown device". Forcing a driver install causes a code 10 which makes it unusable as well. I have tried 4 different cables and 3 different computers now and tried all of the USB ports on each of the computers I tried at and always get unknown device even with the correct drivers installed. The 3 button trick doesn't work to put it in download mode but using a jig does. I have tried every operating system combo as well heimdall in OSX and Linux says no device connected, and in Windows 7 32 bit and 64 bit I get the unknown device error, also tried Windows XP and get the same error. I have tried 4 different usb cables now as well in each situation with the same unkown device/no device connected error (2 motorola cables, 1 samsung oem cable, and one no-name cable). I was going to gift this to my Dad because he's been missing Android since he gave his HD2 away and went back to a Blackberry.
OK folks, I know some of you are going to jump straight down my throat, but please, back off and stick to the friendly forums that this used to be where anyone would help anyone.
the story so far is that I once loved my Nexus One, I've had it since launch, I have ran Cynogen Mod 7 for a couple of years, I have had MUI roms running, I have played with various kernels, updated radio, upgraded hardware, all was going wonderfully.
the one thing I could never get was full SU!! Heck knows why!!
I then started getting random problems and downloaded the original google frf83 software and flashed the phone via update.zip using amon-ra recovery.
I thought all was well after this, as my phone received 3 OTA updates and now my phone is on...
Android 2.3.6
Baseband 32.41.00.32U_5.08.00.04
Kernel 2.6.35.7-59465-g42bad32 ([email protected] #1)
Build GRK394
I noticed that in the Status (settings) it was displaying my old sim card number, which is not the number for the sim in the phone now. his I thought was odd and that something had gone wrong.
So as most of us would do, I went to boot AmonRa recovery and it wasnt available, it had been overwritten with the default recovery; ok lets just ADB and reflash it, I hadnt used ADB for a couple of years because I did everything through AmonRa's awesome recovery!!
So off I go, install the SDK, all the appropriate packs including the USB driver, just like I did when I originally flashed the phone with the recovery image!
But an old problem came back that I hadnt even been bothered about because I always put stuff on SDcard via a card reader!!
I have had consistent problems with my nexus one for some time now in regards to the USB drivers, no matter what I do the phone will not install and I believe it could be some conflict in the device.
I am running Vista Ultimate (fully registered) and no matter what I do I cannot get the Nexus One to install. It will only display as unknown device, which is absolutely useless.
I have browsed every post and tried everything I have found, and yet nothing is working. I have used devmgmt, I have tried the roll backs, I have tried to install every driver available to get it working. I have uninstalled the device, updated drivers after fresh install attempts, I have even formatted my laptop thinking it may have had a corrupt OS and bought Vista Ultimate.
I am not a complete noob and I have been around these forums for some years, but I never thought I would have to cry out like a 4ucking Noob with such a seemingly simple problem, but it is not simple, I have done everything I can possibly find!!
I must get the USB working in order to get the recovery back, I can access my phones default recovery but it will not work when trying various roms as update.zip!!
I have tried the terminal commands on the phone to install the recovery.img but I do not have SU access and the phone point blank refuses.
I have attempted to change and remove the recovery files reffered that are causing the revert to default recovery, but shock.. I cannot delete because of insufficient permissions. I cannot ADB because the USB driver refuses to install.
So if I cannot change the files due to permissions, I cannot ADB because of USB, I cannot get to Ra's recovery because of bootfiles, I cannot use default recovery to update.zip... I am absolutely losing my mind and I'm going nuts browsing the forums for the second week running, yes I am now on day 12 of trying to fix this problem and at a complete loss...
Can someone please help??
I will even allow remote access to pc because I am that desperate to resurrect my beloved Nexus One.
I also have a Galaxy I9000 without 3 button download mode but that is an entirely different story!!
Please just someone, come to an oldskoolers rescue, and yes PAYMENT will be given to the knight in shiny armour!!
You could try on another computer which doesn't run Vista
tommert38 said:
You could try on another computer which doesn't run Vista
Click to expand...
Click to collapse
Or just use fastboot instead of adb...
His Nexus One isn't recognized by the computer, so that won't help unfortunately. Also, I've never heard of build GRK394..
tommert38 said:
His Nexus One isn't recognized by the computer, so that won't help unfortunately. Also, I've never heard of build GRK394..
Click to expand...
Click to collapse
Install the drivers for fastboot already Jeez and then read How to use android for dummies.
Was having wifi issues, found a tutorial on flashing firmware via usb, BUT downloaded an old firmware that made the whole device go to hell.
Has anyone managed to recover their device, or am I the only soul who was dumb enough to put myself in this situation.
I cannot get into fastboot, recovery, etc. booting leads to a blank screen.
Cheers
You will have to flash the stockrom files via Odin i am afraid
Sent from my SM-N920C using Tapatalk
Do you have any sort of instructions.
I'm sorta familiar with Odin, but I thought that fastboot was a requirement?
jewnersey said:
Was having wifi issues, found a tutorial on flashing firmware via usb, BUT downloaded an old firmware that made the whole device go to hell.
Has anyone managed to recover their device, or am I the only soul who was dumb enough to put myself in this situation.
I cannot get into fastboot, recovery, etc. booting leads to a blank screen.
Cheers
Click to expand...
Click to collapse
Hey were you able to fix this issue? I am having a similar issue currently and would appreciate any help.
jewnersey said:
Was having wifi issues, found a tutorial on flashing firmware via usb, BUT downloaded an old firmware that made the whole device go to hell.
Has anyone managed to recover their device, or am I the only soul who was dumb enough to put myself in this situation.
I cannot get into fastboot, recovery, etc. booting leads to a blank screen.
Cheers
Click to expand...
Click to collapse
Turns out i did the exact same and now i am in similar situation.
https://forum.xda-developers.com/google-glass/help/glass-wont-fastboot-mode-t3990575
did you manage to fix the problem?
Don't think it's fixable ?
[/COLOR]
jewnersey said:
Don't think it's fixable
Click to expand...
Click to collapse
I was able to make some progress. Whenever i tried to fastboot a device would popup for a second on the computer and then disappear. At first I thought it was fastboot interface but looking closely at the device "OMAP4430" with vid 0451 and pid D00F, turns out it is an interface used to flash new first stage and main bootloaders on various devices such as galaxy nexus and galaxy tab 2 along with pandaboard and certain lg phones. There are utilities such as OMAP flash (by Texas instruments) and OMAP4BOOT (unofficial open source) that could talk to the device using this protocol. People have made scripts around these utilities to unbrick other devices mentioned above. I have played with these tools and i am able to push first loader called MLO or " xloader" by TI, fortunately google provides xloader with XE23 but i am not been able to push the main bootloader perhaps someone with more experience can help write configuration scripts for these tools that would work on glass so that i can get to fastboot and restore my device.
Hey there!
I recently found my old G1 in storage and I wanted to check it out and use it for a bit. However, when I boot the G1, I get to the Android splash screen which seems to free and then it moves to a blank screen and never progresses from here.
This is a custom ROM. God knows which one it was since I flashed this back in 2009. I can get into the HBOOT screen by holding Power and Camera. I tried using my WIndows 11 PC to ADB but it looks like it's no longer supported. If someone could assist me in getting this thing to boot I would be eternally grateful. I don't want to flash a new ROM since I want to check out the old stuff that is on here from my youth!
I can provide as much information as needed for the assist.
Thank you!
mcdeezy said:
Hey there!
I recently found my old G1 in storage and I wanted to check it out and use it for a bit. However, when I boot the G1, I get to the Android splash screen which seems to free and then it moves to a blank screen and never progresses from here.
This is a custom ROM. God knows which one it was since I flashed this back in 2009. I can get into the HBOOT screen by holding Power and Camera. I tried using my WIndows 11 PC to ADB but it looks like it's no longer supported. If someone could assist me in getting this thing to boot I would be eternally grateful. I don't want to flash a new ROM since I want to check out the old stuff that is on here from my youth!
I can provide as much information as needed for the assist.
Thank you!
Click to expand...
Click to collapse
If windows is not supporting your device. You can try to live boot this tool. Burn Iso to USB drive and boot from the USB. Already has android tools and drivers on board
[LIVE-ISO][mAid][v4.0] manage all your Android devices without driver hassle
is now: (read here why) About The existence of mAid (abbreviation for [m]anage your [A]ndro[id]) has a simple reason. I wanted to have something where I were able to point users to when they came with issues on Windows because the most...
forum.xda-developers.com
mAid Linux - Browse Files at SourceForge.net
manage all your Android devices without any driver hassle
sourceforge.net
Thank you so much! I was actually able to ADB Shell into the device and pull down my SMS database. Worked like a charm! Thank you so so so much