Database Users

OK I'm sorry but I'm Having issues with Fastboot

I tried asking in the Boot Image thread but since that thread was originally posted in January, I dont think anyone even goes in there anymore. OK this is what Ive got.
Im not sure if it was the new radio update or the JF1.5 or 1.51 but ever since Ive upgraded from RC33 the fastboot screen has changed and I havent been able to change my Boot Image.
Instead of just connecting the phone to the computer and pressing back to get fastboot it now give me 4 options instead of just fastboot.Up top it says
FASTBOOT USB (highlighted in red) then
<CAMERA STEP2> HBoot Mode
<SEND> Reset Device
<ACTION> Restart to HBoot
<MENU> Power Down
Is there a new driver i have to download? or is it something else? because when i go to RUN/CMD and I type in the correct commands to change the Boot Image it does nothing it says <waiting for device>
I'm Sorry if this may seem like a dumb Q? but I figured maybe I wasn't the only one having this problem?

sorry I dont really know the answer man, sounds like you are using a new spl or some other bootloader. However, just to let you know, you really needed to post this in the dev section and not the theme section. you probably would get a better response over there.
Stericson

un install your phones drivers in device manager.
unplug your phone,
reboot your computer into safe mode.
plug your phone into usb.
a dialog box will pop up, navigate it to the sdk folder or wherever you have the g1 drivers. install them. wait till it finishes.
then unplug your phone and boot it into fastboot mode. the plug it back in again. and install the same drivers again
unplug your phone and reboot your computer. you should be able to access your phone in fast boot now.
dont push boot images in safe mode, it may be unstable

Thanx guys let me see what i can do
Editk i must have updated to another SPL so i went back to the Original HardSpl and it came back thanx stericson fo the Idea. back to normal
Message to MODS: you can close this if you want I'm sorry for wasting space

Hi,
There is a new driver for the usb connection.
Unzip this file to a folder and plug in your phone don't Mount .
The computer should ask for a driver.
if it doesn't look in control panel, system, usb controllers.
One of the devices will should a problem, update the driver with the files you downloaded and you should be ok.
The computer doesn't recognize the new bootloader until you update the driver.
When you then plug in your phone, it will say fastboot usb.
LatinSilEighty said:
Thanx guys let me see what i can do
Editk i must have updated to another SPL so i went back to the Original HardSpl and it came back thanx stericson fo the Idea. back to normal
Message to MODS: you can close this if you want I'm sorry for wasting space
Click to expand...
Click to collapse

LatinSilEighty said:
I tried asking in the Boot Image thread but since that thread was originally posted in January, I dont think anyone even goes in there anymore. OK this is what Ive got.
Im not sure if it was the new radio update or the JF1.5 or 1.51 but ever since Ive upgraded from RC33 the fastboot screen has changed and I havent been able to change my Boot Image.
Instead of just connecting the phone to the computer and pressing back to get fastboot it now give me 4 options instead of just fastboot.Up top it says
FASTBOOT USB (highlighted in red) then
<CAMERA STEP2> HBoot Mode
<SEND> Reset Device
<ACTION> Restart to HBoot
<MENU> Power Down
Is there a new driver i have to download? or is it something else? because when i go to RUN/CMD and I type in the correct commands to change the Boot Image it does nothing it says <waiting for device>
I'm Sorry if this may seem like a dumb Q? but I figured maybe I wasn't the only one having this problem?
Click to expand...
Click to collapse
the spl you have there is Haykuro's Custom SPL
I had the same trouble with getting fastboot to work
I did the same as you and went back to HardSPL
trying to find a way to get fastboot to work on the newer SPL tho
will update if i get it to work

got a bricked N1...

some guy successfully bricked his N1 as soon as he received it about 2 months ago. When this expensive brick reached my hand, he didn't even remember what he had done... and this brick had been through many many ppl for repair, so there is no way for me to know what exactly happened during the last 2 months...
Anyway, now it:
1. light doesn't turn on when charging(not sure yet whether it is actually charing)
2. trackball + power could gets it to fastboot screen, but none of the key is working then.
3. after single press of power button when powered off, red/green/blue/white color bar and 3 droids on the screen
so , now I cannot put it in fastboot nor recovery mode, stuck.
could there be anything I can do to rescue it?

ndep said:
2. trackball + power could gets it to fastboot screen, but none of the key is working then.
Click to expand...
Click to collapse
Verify this. Enter fastboot mode (connected to usb) and then try "fastboot devices" in a command prompt. It it reports a connected device then its definitely recoverable.

The only way that a N1 get bricked (software wise) is by upgrading a wrong radio, and unfortunetly the only way to recover it (now) is by sending it to Google/HTC

more explanation
thanks i did try that...fastboot devices could not detect anything,coz it just freezes at that screen and could not enter any mode using power and voldown button.
what puzzlrs me most is that screens with multicolor bars, how on earth does that happen?
britoso said:
Verify this. Enter fastboot mode (connected to usb) and then try "fastboot devices" in a command prompt. It it reports a connected device then its definitely recoverable.
Click to expand...
Click to collapse

update: the light turns orange now and then when charging, and it is actually charging no matter the light is on or not. ( using my own nexus to verify that )

Did you plugged it to your PC?
I knew a guy who bought a ''flashing device'' capable of formating any chipset over USB, so he could do a clean install of the Firmware again. Perhaps you could find one of these devices over ebay

britoso said:
Verify this. Enter fastboot mode (connected to usb) and then try "fastboot devices" in a command prompt. It it reports a connected device then its definitely recoverable.
Click to expand...
Click to collapse
That's assuming he has the android sdk installed with the correct drivers. We don't know if the op has.

@vegetaleb: the device you mentioned is somewhat mysterious... a search on ebay with "flash device" does not give me anything related, do you have a specific name?
@C.Slater: I do have them, coz I myself own a nexus too..

should be deleted, sorry
@vegetaleb: the device you mentioned is somewhat mysterious... a search on ebay with "flash device" does not give me anything related, do you have a specific name?
@C.Slater: I do have them, coz I myself own a nexus too..
edit: isn't there an option to delete this reply? I clicked the submit button twice,sorry.

does typing fastboot devices in the cmd prompt work for your non bricked nexus?
Sent from my Nexus One using the XDA mobile application powered by Tapatalk

Does holding power+trackball bring you to fastboot?
Yes=It's not bricked
No=Kiss it goodbye, it's bricked
Simple as that

TFJ4 said:
Does holding power+trackball bring you to fastboot?
Yes=It's not bricked
No=Kiss it goodbye, it's bricked
Simple as that
Click to expand...
Click to collapse
power+trackball will bring it to fastboot screen, note just the fastboot screen, it just freezes there. All the buttons does not work, and connecting to PC using a USB cable does not show "FASTBOOT USB".
However, it could enter HBOOT with power+voldown, I noticed it searches for passdiag.zip , passdiag.nbh, etc. Could I use this builtin function to flash it? which file in this post should I use?
http://android.modaco.com/content/g...-online-kitchen-optional-root-insecure-himem/
I tried to use the first one ( http://www.romraid.com/paul/nexusone/EPE76-update-nexusone-stock-images.zip ), rename to PASSDIAG.zip , but HBOOT is still complaining about "No Image"

Perhaps it's physically damaged!
It remembers me of my boss iphone that looked perfectly normal but couldn't get a FW installed because the power part has been damaged by water(power button couldn't work at all)

Try renaming it to passimg.zip and use hboot again.

speedyls91 said:
Try renaming it to passimg.zip and use hboot again.
Click to expand...
Click to collapse
tried PASSIMG.zip , still "No Image"...

You can send it to htc for repair but the downside would be that you would never know how to deal with this kind of problem yourself...
Continue the research and keep us posted ...

i maybe wrong but i think is it case-sensitive.....meaning PASSIMG.zip would fail but passimg.zip wouldn't.....Correct me if i'm wrong please....

Case sensitive
I'm pretty sure it is case sensitive. Used to be that way with other android and HTC devices. Can't imagine it's changed.

linux is case sensitive, for sure.
i say approach from the adb/fastboot route, using usb. first, ensure that you have all the correct drivers etc for adb use (the sdk, the usb drivers, and the device specific drivers).
try ur 'adb devices' command
if adb sees it, in normal mode, you should be okay. make sure the phone has 'usb debugging' turned on in settings

Strange Bootloop problems!!!

Ok, i have a mytouch 4g that has never been rooted. The problem with the phone is that all of the sudden when i try to turn it on it wont get pass the splash screen. It will just turn off and reboot to the splash screen over and over. Thing is that i can get into Hboot quite easily. I tried to reflash the stock IMAGE file and it does it well without problems. But once its done and i hit power to reboot, the phone just starts to bootloop again doing the exact same thing. I know its kinda odd but i read somewhere that if i can get into Hboot the eMMc is not fried. But then what should be the problem?

enelyam said:
Ok, i have a mytouch 4g that has never been rooted. The problem with the phone is that all of the sudden when i try to turn it on it wont get pass the splash screen. It will just turn off and reboot to the splash screen over and over. Thing is that i can get into Hboot quite easily. I tried to reflash the stock IMAGE file and it does it well without problems. But once its done and i hit power to reboot, the phone just starts to bootloop again doing the exact same thing. I know its kinda odd but i read somewhere that if i can get into Hboot the eMMc is not fried. But then what should be the problem?
Click to expand...
Click to collapse
Sounds like hardware problem = warranty replacment
RcMix 3D Darkside Glacier HD
Tdj's Demonspeed v7 Kernel
Virtuous OC Damean
ClockWorkMod Recovery 5.0.2.0

Thanks, thats what i thought. Just wanted to ask so if someone have seen this before maybe there was a solution for that. But yeah, something is not right and i also think its a hardware issue.

Same prob here...anything like odin for htc? Engineering mode? I used two diff zip files tha were supposed to be the same recovery/ stock image/zip... think it i15img.zip or something... one does not do anything cept try and parse and restart other goes thru ok ok ok ok ok ok then skips the tp tp writes and says deferred or something but looks to get the job done but nah... what are the tp writes I skips...think they are right before the radio write...arg too tired
Sent from my SPH-D700 using XDA App

vizionforever said:
Same prob here...anything like odin for htc? Engineering mode? I used two diff zip files tha were supposed to be the same recovery/ stock image/zip... think it i15img.zip or something... one does not do anything cept try and parse and restart other goes thru ok ok ok ok ok ok then skips the tp tp writes and says deferred or something but looks to get the job done but nah... what are the tp writes I skips...think they are right before the radio write...arg too tired
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
HTC's too pro to have odin
the stock image file is named "PD15IMG.zip" and should be flashed in the bootloader.

Same here, this one skip the tp tp saying Bypassed on the second tp but everything seems to run ok. Only thing is that when i hit power after the update it will just start with the bootloop again. Since this is a friend, I dont really know what version it was running. But i do know its never been rooted or anything like that. Its on .86.000 and S-on and everything. Im going to try the gingerbread just for fun and see what happens.

thinking tese are Gingerbread update fails?
Let us know how the gingerbread turns out...Someone must have a recovery zip? Its obvious the two files I am trying to flash named the same thing are not the same thing or one is corrupted....211mb takes an hour on my connection now ANYONE HAVE A RECOVERY ZIP? Is there a program like odin(OK NOW I KNOW TO USE CMD AND ADB) Now I need a mytouch button press sequence to get to ENGINEERING MODE? to write to the frickin thing...I thought HTC was gonna be better than Samsung in this respect...I have one good mytouch4g that I can get the serial using the command 'adb devices' that is once mytouch is booted up...so question is how do i get to engineering mode in my bad my touch(which wont boot) so I can PUSH the file in command line interface.

vizionforever said:
Let us know how the gingerbread turns out...Someone must have a recovery zip? Its obvious the two files I am trying to flash named the same thing are not the same thing or one is corrupted....211mb takes an hour on my connection now ANYONE HAVE A RECOVERY ZIP? Is there a program like odin(OK NOW I KNOW TO USE CMD AND ADB) Now I need a mytouch button press sequence to get to ENGINEERING MODE? to write to the frickin thing...I thought HTC was gonna be better than Samsung in this respect...I have one good mytouch4g that I can get the serial using the command 'adb devices' that is once mytouch is booted up...so question is how do i get to engineering mode in my bad my touch(which wont boot) so I can PUSH the file in command line interface.
Click to expand...
Click to collapse
Turn the phone completely off, and turn it on again using volume down+power buttons. This enters hboot, or bootloader, where you flash the stock PD15IMG.zip file.
Sent from my HTC Glacier Sense 3.5 using xda premium

Unstick my heart
I should be able to communicate with device using adb push in command line interface hboot then? I dont see any device serial with adb devices
...Was hoping there was an engineering mode like samsung has...Well some different output here getting me excited...Img zip (211mb) that used to just stall with the other stock image zip I used (that does not parse) has at least allowed the img crc to work... below are my output pictures
http://www.flickr.com/photos/[email protected]/6447958131/
and this is the .zip (output picture of it anyway) (312mb)that I first used, seemed to work better than the one I had to rename in a recent post in Q&A forum, that said the zip that seems not to work unstuck img crc so now it reads hmmm....any ideas?
http://www.flickr.com/photos/[email protected]/6447957849/

vizionforever said:
I should be able to communicate with device using adb push in command line interface hboot then? I dont see any device serial with adb devices
...Was hoping there was an engineering mode like samsung has...Well some different output here getting me excited...Img zip (211mb) that used to just stall with the other stock image zip I used (that does not parse) has at least allowed the img crc to work... below are my output pictures
http://www.flickr.com/photos/[email protected]/6447958131/
and this is the .zip (output picture of it anyway) (312mb)that I first used, seemed to work better than the one I had to rename in a recent post in Q&A forum, that said the zip that seems not to work unstuck img crc so now it reads hmmm....any ideas?
http://www.flickr.com/photos/[email protected]/6447957849/
Click to expand...
Click to collapse
Once the phone is in bootloader, connect it to the computer, and you should see "fastboot USB" on the phone. Then open up adb, and type
Code:
fastboot devices
Sent from my HTC Glacier Sense 3.5 using xda premium
EDIT: here, download THIS FILE, rename it to PD15IMG.
then place it in the ROOT of your SDcard (not in any folders)
turn off and reboot the device into bootloader
bootloader should find the file and ask if you want to update
not sure if this is the method you used... tell us how it goes

Hmm Command did not say i had any devices (blank line) but my command line interface is in fastboot / adb(whats the differnce?) seems like it sees it? tell me if Im wrong... The command 'Fastboot devices' brought up long dir of commands, then I tried the following commands faastboot push and update PD15IMG (See pic below) Thanks for your help! I will try your zip! (but I would like to push from command line fastboot)
http://www.flickr.com/photos/[email protected]/6448265267/
Currently downloading ur zip thx...23 mins left :\
THANKS!

vizionforever said:
Hmm Command did not say i had any devices (blank line) but my command line interface is in fastboot / adb(whats the differnce?) seems like it sees it? tell me if Im wrong... Fastboot devices brought up long dir of commands for adb? then I tried following commands (See pic below) Thanks for your help! I will try your zip! (but I would like to push from command line fastboot)
http://www.flickr.com/photos/[email protected]/6448265267/
Click to expand...
Click to collapse
does your device say that it's "fastboot USB" somewhere on it? if it says "HBOOT USB", manually scroll to fastboot and select it.

no it does not seem to see it is connected
http://www.flickr.com/photos/[email protected]/6448372103/
I know USB works because it attempts to orange led flashes/charges before it turns on but it does not say usb after fastboot
still waiting for download...29 mins remaining at 72kb per sec groan

vizionforever said:
no it does not seem to see it is connected
http://www.flickr.com/photos/[email protected]/6448372103/
Click to expand...
Click to collapse
hmm.. might be because you don't have the engineering bootloader.
my mom's is S-on as well, and computer can't see it through fastboot.
anyway, just use the method i told you, move it onto the SDcard manually

Computer cant see it, but can it write to it?(i want to try) What is proper command to push pd15IMG in adb/fastboot? should I do it in adb or fastboot on computer? and what mode on phone: hboot or fastboot? thx G

vizionforever said:
Computer cant see it, but can it write to it?(i want to try) What is proper command to push pd15IMG in adb/fastboot? should I do it in adb or fastboot on computer? and what mode on phone: hboot or fastboot? thx G
Click to expand...
Click to collapse
i meant taking out the SDcard and connecting the SDcard to the computer, and transfer files that way.

Understood what u meant, just wanted to try usb push ind adb while file is downloading...

vizionforever said:
Understood what u meant, just wanted to try usb push ind adb while file is downloading...
Click to expand...
Click to collapse
don't think that's gonna work :/
sorry

ehh crap same thing skips tp writes....Still stuck, any other .zip to try? HTC Device(without seperate engineering mode does not seem to more "pro" (but the htc windows drivers, they seem more robust
What to do now :| ???
thx G
---------- Post added at 09:36 PM ---------- Previous post was at 09:12 PM ----------
same thing bootloop
computer now sees a unknown usb device anyone have the .inf? Google search for "mytouch .inf" showed only 6 results none I can use... Would rather use a .inf and install from disk than use .exe
EDIT: flashed http://forum.xda-developers.com/show....php?t=1174344
not it writes to #7 TP but not #8 still in bootloop... Now cant flash cause that is most recent... Can I try to flash any custom roms? or... My s is on

Its a waste of time people, sorry to say but this is definetly a hardware issue and its been spreading all over the world with people having issues on that same subject.

[Q]Bricked ?

This is what happens :
1. When I normally turn my N7 on , it goes throught the google logo and gets stuck on the ROM logo .
2. I can get into the bootloader when the USB is plugged off , but i cant get into recovery it just gets stuck on the google logo .
3.If I plug my USB in while in the bootloader the bootloader gets stucked and i cant move around in it or flash anything , but my PC recognize that an android device is connected . (if i get into the bootloader when the USB is allready connected it gets in the bootloader main screen but i cant move) .
So i cant flash , get into the rom or return to stock .
ANY IDEAS ?? please help me :crying::crying:

Bump

Definitely not bricked since of powers on. Fastboot flash the stock image and you should be good as new.
Sent from my Nexus 7 using Tapatalk 2

Strange, it shouldn't make a difference whether your USB is plugged or not when trying to get to the recovery.
If you get into the fast boot menu or "boot loader main screen" and you press the volume down button a few times you get no response? Sometimes it takes a few seconds for mine to switch to recovery,etc.
Also, what caused your tablet to get stuck in that state?

brGabriel said:
Strange, it shouldn't make a difference whether your USB is plugged or not when trying to get to the recovery.
If you get into the fast boot menu or "boot loader main screen" and you press the volume down button a few times you get no response? Sometimes it takes a few seconds for mine to switch to recovery,etc.
Also, what caused your tablet to get stuck in that state?
Click to expand...
Click to collapse
If I press the volum dowm bottom while on fast boot menu I can move around the menu if the usb is plugged off , but I can only shutdown or restart the fastboot since the start and recovery options just gets stuck on the google/rom logo if it is plugged in I just gets stuck in the menu and I cant even scroll . yea I waited about half an hour on the google logo trying to get to my recovery and nothing happened .
I JUST DONT KNOW WHAT I DID ! I really dont ! I am an experienced flahser and had been so for almost 2 years now ! I just left my N7 on the table and didnt touch it at all for a week and when I tried to turn it on after that I just got that prob . but I did nothing related to flashing or so - it just happened by staying at the table !
any help ?? PLEASE
I CANT RETURN TO STOCK , if i plugg in the usb fastboot gets stuck .

have you tried charging it on the wall charger to make sure the battery has got a full charge, don't know, just throwing out options

Hmmm, well at least you're able to boot the tablet and get to fastboot menu so its not a hard brick. Sounds like a corrupted partition of sorts if you can't get into ROM or recovery. Someone with more expertise might have a possible solution. I wouldn't lose hope yet.

yes , i did charged it to full batt .
i can get into fastboot but not rom or recovery and when i plugg in usb i have no fastboot , doesnt that mean i wont ever be able to flash ?
if i will make a vid of the prob it will help ?

Get to boot loader and do
fastboot flash recovery C:\File path to recovery on computer
Once you have a recovery installed you can push a ROM to your Nexus via adb.
Sent from my Nexus 7

Or you can always use wugfreshs toolkit and click flash back to stock option and check device won't boot, the same thing happened to me awhile ago and the bootloader problem is cause you have the old bootloader the knew 4.13 bootloader fixed that
Sent from my Nexus 7 using Tapatalk HD

i've had good luck with mskip's toolkit in a similar situation

veeman said:
Get to boot loader and do
fastboot flash recovery C:\File path to recovery on computer
Once you have a recovery installed you can push a ROM to your Nexus via adb.
Sent from my Nexus 7
Click to expand...
Click to collapse
xfrancis14 said:
Or you can always use wugfreshs toolkit and click flash back to stock option and check device won't boot, the same thing happened to me awhile ago and the bootloader problem is cause you have the old bootloader the knew 4.13 bootloader fixed that
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Guys , I told you that my bootloader gets stuck when I connect the usb - so how can I possibly flash anything ? please read the whole post

rkiller51 said:
Guys , I told you that my bootloader gets stuck when I connect the usb - so how can I possibly flash anything ? please read the whole post
Click to expand...
Click to collapse
It says you can get to the boot loader with the cable unplugged. So get to the boot loader and then plug in the USB.
Sent from my Nexus 7
Stop... MUFFIN TIME!!!

veeman said:
It says you can get to the boot loader with the cable unplugged. So get to the boot loader and then plug in the USB.
Sent from my Nexus 7
Stop... MUFFIN TIME!!!
Click to expand...
Click to collapse
Are you kidding ? "3.If I plug my USB in while in the bootloader the bootloader gets stucked and i cant move around in it or flash anything , but my PC recognize that an android device is connected ."
I really appreciate any kind of help, but why even write and answer when you didnt even fully read the question ?

rkiller51 said:
Are you kidding ? "3.If I plug my USB in while in the bootloader the bootloader gets stucked and i cant move around in it or flash anything , but my PC recognize that an android device is connected ."
I really appreciate any kind of help, but why even write and answer when you didnt even fully read the question ?
Click to expand...
Click to collapse
Lol just calm down man we're all just trying to help you!
Now, you need to get your N7 into the bootloader, it does not matter if you can't navigate the bootloader on your N7. Once in the bootloader, connect the N7 to your computer with the USB cable.
Once you're connected, make sure you've downloaded the Android SDK and open a command prompt. Navigate your command prompt (make sure you ran that command prompt as administrator) to the "platform-tools" directory.
Once in the platform-tools directory run the following command without quotes:
"fastboot devices"
It should return the serial number for your device, indicating that fastboot sees your N7 and can work with it.
After that type
"fastboot flash recovery *.img"
You'll need to head to clockworkmod.com to download the N7 recovery image. Place the downloaded image in the platform-tools directory and replace "*.img" with the filename of the recovery image you downloaded.
That's it! Unplug your N7 and go into recovery, and sideload whatever ROM you want!
Let us know how it goes!
PS: If fastboot devices shows nothing, we have a bigger problem...

TMan459 said:
Lol just calm down man we're all just trying to help you!
Now, you need to get your N7 into the bootloader, it does not matter if you can't navigate the bootloader on your N7. Once in the bootloader, connect the N7 to your computer with the USB cable.
Once you're connected, make sure you've downloaded the Android SDK and open a command prompt. Navigate your command prompt (make sure you ran that command prompt as administrator) to the "platform-tools" directory.
Once in the platform-tools directory run the following command without quotes:
"fastboot devices"
It should return the serial number for your device, indicating that fastboot sees your N7 and can work with it.
After that type
"fastboot flash recovery *.img"
You'll need to head to clockworkmod.com to download the N7 recovery image. Place the downloaded image in the platform-tools directory and replace "*.img" with the filename of the recovery image you downloaded.
That's it! Unplug your N7 and go into recovery, and sideload whatever ROM you want!
Let us know how it goes!
PS: If fastboot devices shows nothing, we have a bigger problem...
Click to expand...
Click to collapse
Its hard to be calm then you new N7 is dying :/
somthing like this ? (pic attached)
If i did everything like you said it means i do have the bigger prob help me!

OK. Next thing is to ensure your N7 is properly detected in Windows.
Just head to the device manager. You should see Original Android Interface or something along those lines.
Report back with a screenshot, those are very helpful!

TMan459 said:
OK. Next thing is to ensure your N7 is properly detected in Windows.
Just head to the device manager. You should see Original Android Interface or something along those lines.
Report back with a screenshot, those are very helpful!
Click to expand...
Click to collapse
Here you go (attached) ! you have everything you need mate ?
I really appreciate the help ! :good::good:

I had similar issues and was able to get back to stock using WugFresh's Nexus Root Toolkit. Highly recommended!

From the same command Window, in the same platform - tools directory, does adb devices show your device?
I'm not the lowest of the low, but I am the slowest of the slow.

[Q] Stuck in safe mode

Hi everybody.
I don't know how it happened (I just wanted to do a reboot in the recovery mode), but now I've got the blue led when normally turn my phone on. I can't even access to the fastboot (blue led too).
The only thing I can do, is boot in the safe mode, by booting my phone (connected to the charger) after removing the battery... I tried "reboot to bootloader", without success...
I think it's because of the recovery, because I had some problems during the installation of my last ROM, a few months ago. So I'd think I must flash a new recovery.
ow can I get out???? ADB? Special "trick"? Factory reset from the ROM? Flashing a new recovery (I don't know how...)?
Thank you, Roumaru

I tried to flash a new recovery with ADB, and then reboot to the bootloader, but it didn't work.... I'm really stuck!

Try RUU method if you are able to acces bootloader mode ,or try to search the forum or look into FAQ,for the answer of your problem.
Sent from my HTC Magic using xda app-developers app

george.wgx said:
Try RUU method if you are able to acces bootloader mode ,or try to search the forum or look into FAQ,for the answer of your problem.
Sent from my HTC Magic using xda app-developers app
Click to expand...
Click to collapse
I can't access to the bootloader... I can just access to the safe mode! It's really strange. I'll search in other forums, but I haven't found any answer yet

Roumaru said:
I can't access to the bootloader... I can just access to the safe mode! It's really strange. I'll search in other forums, but I haven't found any answer yet
Click to expand...
Click to collapse
Install mumilover's Fastboot Commander. Connect it to your PC with a USB cable, turn it on, and run Fastboot Commander. It will display a bunch of information about your phone that will help us diagnose the problem.
Just cut and paste the info it gives you. If it doesn't work, just tell us what information you see on the phone's screen.
You should see something like:
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.76.0007 (SAPP10000)
CPLD-10
RADIO-6.35.07.29
Aug 4 2009, 19:43:30
Later.

DasBub, he cannot acces bootloader,so he 's not able to see that info

george.wgx said:
DasBub, he cannot acces bootloader,so he 's not able to see that info
Click to expand...
Click to collapse
Yes, I understand that he can't get into HBOOT, FASTBOOT, or Recovery using physical buttons. But there are other possibilities we can check. I don't know his skill level, knowledge about the device, or the complete state of his device, so I'm trying to build a clearer picture.
If fastboot reports nothing, what about adb? If adb reports nothing, check device manager to see if it's even noticed by the PC.
When I said "just tell us what information you see on the screen" what I meant was "tell us what the screen is showing, even if it is nothing at all and the blue LED is on". My fault.
I'm curious about the whole "safe mode" business. Is it truly booting into safe mode, where you can see the words "safe mode" on the screen, or is it something else?

DasBub said:
Yes, I understand that he can't get into HBOOT, FASTBOOT, or Recovery using physical buttons. But there are other possibilities we can check. I don't know his skill level, knowledge about the device, or the complete state of his device, so I'm trying to build a clearer picture.
If fastboot reports nothing, what about adb? If adb reports nothing, check device manager to see if it's even noticed by the PC.
When I said "just tell us what information you see on the screen" what I meant was "tell us what the screen is showing, even if it is nothing at all and the blue LED is on". My fault.
I'm curious about the whole "safe mode" business. Is it truly booting into safe mode, where you can see the words "safe mode" on the screen, or is it something else?
Click to expand...
Click to collapse
I took a look at "fastboot commander", but naturally I need to be in the fastboot to make it work, and I can't access fastboot...
I can NOT boot in HBOOT, FASTBOOT, and Recovery, but when I remove the battery, put it in the phone, plug my charger, and then press the power button, the phone boot normally, except he's in the "safe mode" (can't access some applications, no network). I can control my phone with ADB, but when I tried "adb reboot bootloader", the blue led was here again...
I also tried the RUU method, but the RUU doesn't recognize my phone.
I think it would be good if I could do a "total reset" of my phone, like flashing it or something that can reset the bootloader.
Thank you for your interest

Yeah dude there is fix for you its named JTAG Google it and you will find out what is it.
In my country its cost me 40 Euro to fix i hope in your is cheaper or even better - you can make your own

Roumaru said:
I took a look at "fastboot commander", but naturally I need to be in the fastboot to make it work, and I can't access fastboot...
I can NOT boot in HBOOT, FASTBOOT, and Recovery, but when I remove the battery, put it in the phone, plug my charger, and then press the power button, the phone boot normally, except he's in the "safe mode" (can't access some applications, no network). I can control my phone with ADB, but when I tried "adb reboot bootloader", the blue led was here again...
I also tried the RUU method, but the RUU doesn't recognize my phone.
I think it would be good if I could do a "total reset" of my phone, like flashing it or something that can reset the bootloader.
Thank you for your interest
Click to expand...
Click to collapse
Could you try something? Make sure your phone is accessible using adb, then do this:
adb -s [serial number for phone, without brackets] reboot oem-78
The serial number can be found using "adb devices".
That should reboot you into RUU mode. If it doesn't work, safe mode should still be accessible.

Please don't post Q&A in the development section.
Thread Moved
Moderating from my One Xl

DasBub said:
Could you try something? Make sure your phone is accessible using adb, then do this:
adb -s [serial number for phone, without brackets] reboot oem-78
The serial number can be found using "adb devices".
That should reboot you into RUU mode. If it doesn't work, safe mode should still be accessible.
Click to expand...
Click to collapse
Doesn't work, the blue led is coming again...
Another idea, except Jtag? Because I don't want to spend money on my Magic, and I don't think I've got the material to do the Jtag...
However, thank you everybody!

Roumaru said:
Doesn't work, the blue led is coming again...
Another idea, except Jtag? Because I don't want to spend money on my Magic, and I don't think I've got the material to do the Jtag...
However, thank you everybody!
Click to expand...
Click to collapse
Hey, we're not giving up yet
You can access ADB, so it may be possible to push a recovery image onto the device and flash it.
For the original instructions, click this link and focus on Step 9.
Here's a shortened version:
Download roottools and unzip it somewhere on your PC.
With your phone in Safe Mode and connected to your PC, open a command prompt.
If you know which radio you were on (3.X or less, or 6.X), cd to that directory in roottools and push the recovery image.
Example: If you have 6.X, you would
cd c:\roottools\6.35Radio\​adb push Recovery-RA-hero-v1.6.2.img /sdcard​
Next:
cd to the "App" directory of roottools, then
adb push flash_image /data/local/tmp
adb shell
su
cd /data/local/tmp
chmod 777 flash_image (you might have to use /data/local/tmp/flash_image or ./flash_image)
flash_image recovery /sdcard/Recovery-RA-hero-v1.6.2.img​
If you get through that with no errors, we should be good. If it throws an error at "su" then you should try using SuperOneClick to get temporary root.
If it flashes without errors, you can try "adb reboot recovery" and see what happens.

Resolved
A few days ago, the "safe mode" logo disappeared. Really didn't understand why, but now my problem is solved!
Thank you for all, Roumaru

Roumaru said:
A few days ago, the "safe mode" logo disappeared. Really didn't understand why, but now my problem is solved!
Thank you for all, Roumaru
Click to expand...
Click to collapse
That's great news! Everything works normally now?
I have heard that a stuck button or trackball is a possible cause. Maybe that was the problem with your phone, but it became unstuck?
Cheers!