Related
I checked Recovery mode and Download mode, and thats OK.
But i found information on Internet, and always the same: VOL UP/DOWN + HOME + POWER.
In some sites, somethind about Forced Upload (i've got one time only and i dont remember how it was.
The question: i called to technical support and asked for the way to get into fastboot mode, and the replay was the information is properly for samsung personal.
Then, i was tyred and bored.
Could anybody help me?
NOTE:
I know that download mode is enaugh, but booting directly from a recovery file in PC is good and quick, and flashing the recovery boot only.
Hey
Just played around with my Galaxy S and could retrieve the way to get into
Forced upload
I pressed Volume up and home until the black and whie Galaxy S boot Screen came
up and then right away volume up+home+powerbutton at the same time.
Hope it works for you as well and hope I remembered it correct because I am feeling
realy dizzy today paired with headaches :/
Is the forced upload mode same as fastboot? Because I am trying to install an other bootscreen as the
one from samsung is not my thing.
I have two phone, one with working 3 button hack, another one without recovery mode with 3 buttons.
on the later device i alway get the "forced upload" (whatever this is) while pressing home and vol up for 3 or more seconds when phone is of.
on the othe device (wirkoing three button mode) i did not manage to see "forced upload"
a similar question has been asked somewhere before: fastboot is htc (ADP=android development phone) specific. fastboot does not (and never will) work with samsung handsets!
Thread moved to Q&A.
jodue said:
a similar question has been asked somewhere before: fastboot is htc (ADP=android development phone) specific. fastboot does not (and never will) work with samsung handsets!
Click to expand...
Click to collapse
Want to explain why my old Galaxy I7500 had fastboot then?
Sent from my GT-I9000M using XDA App
if you simply want to reboot the phone quickly, there is an APP for that
you can choose normal reboot
reboot to Recovery Mode
reboot to Download Mode
look for Quick Boot
http://forum.xda-developers.com/showthread.php?t=765081
Fastboot is an utility from the Android SDK and normaly not made only for one brand.
Electroz said:
Want to explain why my old Galaxy I7500 had fastboot then?
Click to expand...
Click to collapse
hm. yeah looks like i was wrong there
scorpio16v said:
Fastboot is an utility from the Android SDK and normaly not made only for one brand.
Click to expand...
Click to collapse
of course it's a part of the aosp but i have (till today) never ever read anywhere that non htc devices support it ... my bad
if anyone finds out how to use fastboot with the galaxy s i will gladly buy 'em a couple of beers because i would love to have this functionality at my disposal!!!
if you simply want to reboot the phone quickly, there is an APP for that
you can choose normal reboot
reboot to Recovery Mode
reboot to Download Mode
look for Quick Boot
http://forum.xda-developers.com/showthread.php?t=765081
Click to expand...
Click to collapse
Doesn't this app solve the broken three button recovery problem?
Thats the thing i referred it. All people with Galaxy S work with REcovery and Download odes.
But anybody knows how the FastBoot Mode works in i9000, and it very important taking a native mode to change the Recovery Boot without flashing with ODIN or Rom Maneger utility (free at the moment).
I understand FAST BOOT is something in relation with android, but ¿is it posible that it need an especial recovery boot, like an intermediate, for passsing throw to FastBoot mode?
Tehpriest said:
Doesn't this app solve the broken three button recovery problem?
Click to expand...
Click to collapse
of course not
when you are bricked, how are you going to run a software on a dead phone?
the phone needs to be rooted for quick boot to work
if you do it via ADB when connected to PC
then you don't need to be rooted
mam999999 said:
Thats the thing i referred it. All people with Galaxy S work with REcovery and Download odes.
But anybody knows how the FastBoot Mode works in i9000, and it very important taking a native mode to change the Recovery Boot without flashing with ODIN or Rom Maneger utility (free at the moment).
I understand FAST BOOT is something in relation with android, but ¿is it posible that it need an especial recovery boot, like an intermediate, for passsing throw to FastBoot mode?
Click to expand...
Click to collapse
I explained more better.
If phone is bricked, it doesnt boots.
Then, ADB is worthy. For that reason, only two chioces:
1) FLASH with ODIN, if it posible with download mode
2) Samsung with JTAG ---> money!!!!
2) FastBoot Mode.
That is very important, and thats my interest
if the phone is bricked
only the 3 button Download Mode will work
JTAG, not many places have it, it's hard to find, the phone is still too new.
Fastboot mode will not work when bricked
ADB will not work when bricked
AllGamer said:
if the phone is bricked
only the 3 button Download Mode will work
JTAG, not many places have it, it's hard to find, the phone is still too new.
Fastboot mode will not work when bricked
ADB will not work when bricked
Click to expand...
Click to collapse
AllGamer, I think you should look up what fastboot actually is/does.
It's a way to flash the phone from a 3button style download mode. The thing is, you can use ADB from windows/Mac/Linux to flash it. (Yes, even when bricked, because you enter it with a different 3button combo)
All HTC Phones have the ability, as well as the Original Samsung Galaxy I7500 and I5700 phones.
People are on here wondering if there's a way to enable the function on the Galaxy S.
Responding in a thread where you have no idea what the topic at hand actually is just makes the thread harder to follow. Please refrain in the future.
Yes, i think FASTBOOT is another backdoor to revover the phone.
And, another advantage:
1) substituting the revovery boot partition (throw native flashing 3button mode) or
2) boot from PC with one recovery image without writing the recovery partion, making diagnostic and everyting like testing news images.
It is very important, and many people will be wondered to know this 3button mode.
Samsung, by call, admited to know the mode, but they dont wanto to say how to get in mode fastboot.
I'll continue to find it.
AllGamer:
How, then, do you overwrite the boot partition? With ADB? Then you need unbricked phone .....
Electroz said:
Want to explain why my old Galaxy I7500 had fastboot then?
Sent from my GT-I9000M using XDA App
Click to expand...
Click to collapse
Did samsung actualy make the phone and not just designed it? Ie the sony xperia x1 was a htc made phone but sony design. So maybe that's why u had fastboot in the 7500. Either way i have no idea on samsung phones as i never liked them
Sent from my GT-I9000 using Tapatalk
if the so call fastboot is actuall another hardware mode, and not the fastboot from ADB shell, then it'll have to be some sort of buttons to trigger it.
I know people that have posted they got into a Forced Upload mode, is that what you guys mean by fastboot mode?
However only people with the disabled 3 buttons download modes seems to have been able to get into this Forced Upload mode, problem is none of them knows exactly how they got into that mode
AllGamer said:
if the so call fastboot is actuall another hardware mode, and not the fastboot from ADB shell, then it'll have to be some sort of buttons to trigger it.
I know people that have posted they got into a Forced Upload mode, is that what you guys mean by fastboot mode?
However only people with the disabled 3 buttons download modes seems to have been able to get into this Forced Upload mode, problem is none of them knows exactly how they got into that mode
Click to expand...
Click to collapse
It IS fastboot from ADB.
You basically put the phone in fastboot mode (similar to 3 button download mode). You can then flash your phone (with the phone in fastboot mode[not booted into android]) with the fastboot command in the Android SDK Tools folder.
"fastboot flash recovery recovery.img" would flash a new recovery image to the phone, or "fastboot flash boot boot.img" would flash a new boot image to the phone.
All this can be done by entering a 3button combo to power on the phone directly into fastboot mode. (Android not required to boot, or even be functioning)
Hi,
I recently got asked by a friend to flash his google nexus one phone. like a mug i said yes and now i have a issue where it turns on, vibrates 7 times and stays at the splash screen with the x on it. I can boot into the fast boot / recovery mode but nothing works.
this happened after i tried to root the phone, it said waiting for device and didnt do anything so i killed the app (Superoneclick) the phone disappeared from device manager and now wont go past the splash screen.
Does anyone have any idea how i can get it back? .. thanks in advance for any help.
James
I'm guessing, since you used S-O-C, the bootloader is not unlocked. The only way I know how to fix it is if you OEM unlock it. You'll need fastboot and your Android SDK setup correctly.
Once you have the setup done, change directories to the tools folder, wherever you put your sdk. Boot your phone into fastboot by holding the trackball while powering it on.
Code:
cd C:\asdk\tools\
Plug your phone into USB, and check if the computer sees it
Code:
fastboot devices
Unlock the bootloader (THERE IS NO GOING BACK! You can never re-lock a Nexus)
Code:
fastboot oem unlock
Now you can flash a boot.img and system.img (preferably pre-rooted) from fastboot, and it should boot normally. If the phone boots, the phone is perma-rooted, and won't need any other rooting procedure (you just need to flash a rooted rom). Next time, be a little more careful
Hi wdfowty
at running the risk of asking for more help and making you cross could you post some links to these downloads?
I am a total newbie to these phones and want to make sure i have the right apps.
thanks again for the help and the quick response... and if i manage to get this phone back believe me it will be the last one i try to flash !!
cheers
James
Nah, you've got me wrong. I'm all about helping people that are willing and able to be helped.
Follow this guide, it'll walk you through the steps to set up your sdk and unlock the bootloader. The guide is a little dated, so the info might not be 100%, but it's generally everything you'll need to know. If you get stuck, feel free to ask.
Hi again,
when i run the command fastboot devices i get an error AdbWinApi.dll is missing.
it tells me to reinstall the app but i have done that and also run all the updates and i still get the same error?
Interstingly i also get the phone to fastboot and it says in red text on the phone fastboot.usb but i cant see anything in device manager that says Nexus one etc?
any more help appreciated.... worst case you dont fancy a christmas break over in England do you?
cheers
james
jamesabennett said:
Hi again,
when i run the command fastboot devices i get an error AdbWinApi.dll is missing.
it tells me to reinstall the app but i have done that and also run all the updates and i still get the same error?
Interstingly i also get the phone to fastboot and it says in red text on the phone fastboot.usb but i cant see anything in device manager that says Nexus one etc?
any more help appreciated.... worst case you dont fancy a christmas break over in England do you?
cheers
james
Click to expand...
Click to collapse
With the latest version of the SDK tools, they changed the directory for adb and fastboot. Unfortunately I'm not on my Windows machine... but check in the directory where you have the SDK extracted to and look for a platform-tools directory (iirc). From there, you should see fastboot.
So basically where it says this "Type: cd C:\android-sdk-windows\tools" change it to "C:\android-sdk-windows\platform-tools". Keep in mind that directory name may change... again, I'm not on my Windows machine right now.
Hi again,
thanks for the continued help. I have managed to get past that, i have OEM unlocked the phone and managed to copy the flash image to the device using the commands in the link you sent me.
problem i have now is when i go into recovery the phone again just pulls up the splash screen and vibrates 7 times.
i believe what should happen according to the link is to follow the 6 steps below.. even i can do that, but the phone doesnt get that far
//Turn phone off -> Hold Volume Down, hold Power button
//Press Volume Down to highlight Recovery -> press Power to select Recovery
//Backup/Restore -> Nand backup
//Wipe -> Wipe data/factory reset
//Wipe -> Dalvik Cache
//Flash zip from sdcard -> alpha-r##-update-modacocustomrom-nexusone-desire-withadditions-signed.zip (Or whatever other ROM you're using.)
another point is it runs a couple of lines of blue txt relating to the sd card, but it flashes up and dissapears too quickly for me to be able to read it and send across to you.
thanks again and if you can work this out i owe you a beer !!
James
jamesabennett said:
Hi again,
thanks for the continued help. I have managed to get past that, i have OEM unlocked the phone and managed to copy the flash image to the device using the commands in the link you sent me.
problem i have now is when i go into recovery the phone again just pulls up the splash screen and vibrates 7 times.
i believe what should happen according to the link is to follow the 6 steps below.. even i can do that, but the phone doesnt get that far
//Turn phone off -> Hold Volume Down, hold Power button
//Press Volume Down to highlight Recovery -> press Power to select Recovery
//Backup/Restore -> Nand backup
//Wipe -> Wipe data/factory reset
//Wipe -> Dalvik Cache
//Flash zip from sdcard -> alpha-r##-update-modacocustomrom-nexusone-desire-withadditions-signed.zip (Or whatever other ROM you're using.)
another point is it runs a couple of lines of blue txt relating to the sd card, but it flashes up and dissapears too quickly for me to be able to read it and send across to you.
thanks again and if you can work this out i owe you a beer !!
James
Click to expand...
Click to collapse
Have you flashed the recovery image using fastboot, or did you only copy the recover image to the sdcard? Step IV in that guide.
It sounds like you need to reinstall your recovery.
Download the recovery found here: http://forum.xda-developers.com/showthread.php?t=611829
Rename that file to recovery.img and place it somewhere you can remember
Boot the phone into fastboot by holding down the trackball and pressing power button.
Code:
fastboot devices
Code:
fastboot flash recovery C:\path\to\recovery.img
If all went well, there should be no errors. On the phone, use the volume keys to select "Bootloader". It will take you to a white screen with the blue text (ignore it, it's looking for update files like "PASSIMG.zip"). Select recovery, and it'll boot into recovery. If you see menu items, you are good!
I ran the fastboot command and used the flash image ending 2.0.0
this is driving me round the bend !!
What happened when you used the fastboot flash command? Did you see a bar on the top right of the phone?
wdfowty said:
It sounds like you need to reinstall your recovery.
Download the recovery found here: http://forum.xda-developers.com/showthread.php?t=611829
Rename that file to recovery.img and place it somewhere you can remember
Boot the phone into fastboot by holding down the trackball and pressing power button.
Code:
fastboot devices
Code:
fastboot flash recovery C:\path\to\recovery.img
If all went well, there should be no errors. On the phone, use the volume keys to select "Bootloader". It will take you to a white screen with the blue text (ignore it, it's looking for update files like "PASSIMG.zip"). Select recovery, and it'll boot into recovery. If you see menu items, you are good!
Click to expand...
Click to collapse
i do that and it accepts the recovery file and the progress bar goes up on the right hand side and the cmd prompt says its all good. then when i select recovery the phone goes to the black background with the four coloured cross and the unlocked padlock, vibrates 7 times and just hangs on that screen
beleive it or not it booted up a moment ago and the phone worked like it did before with v2.2 on it. so i am happy now it can be recovered... i just dont know what to do to straighten it out!
yes. the bar goes up on the right hand side of the phone. and i have definitely unlocked it as it now says unlocked at the top of the menu.
Have you tried to reimage the phone with the passimg method? Directions are provided in the wiki, under the unlock/restore heading:
http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus
Follow PASSIMG method (filename is case sensitive).
The link to the files is on the word "here" on step 2.
Use FRG33.
Sent from my Nexus One using XDA App
Hello all,
I have a friends sprint hero cdma that was rooted with z4root. He was flashing a mod that changed the text from green to orange and the phone froze. He waited quite a while then decided to hard reset. When he put the battery back in and rebooted the phone and the phone would not boot past white HTC bootlogo. The phone will not boot into recovery and the PC will recognize the phone, but the system will not mount so the ruu will not detect the phone either. HTC sync does not detect the phone being connected either. I am using a program called USBDeview and it shows the driver is there and says it is connected but none of the programs detect its connection. Any ideas?
Thanks in advance. Again this is not my phone and I am not familiar with rooting procedures with this phone, but I see a great learning experience in front of me and love these challenges.
this should be in QnA.
Hold power + vol down. will get you into HBOOT. if you flashed the eng-spl that unlocks fastboot you can erase and flash new. Tutorials are somewhere in this forum.
Sorry for the wrong forum. The phone will not hboot or boot into recovery
If it gets that far, you should be able to run the RUU. It'll restore everything to stock ;-)
Sent from my Epic using XDA App
The phone does not connect all the way for some reason. The RUU does not see device and neither does ADB. In device manger, when the device is connected it is assigned a drive letter and I can right click and go to properties and details and the description says android phone. I am out of ideas. Even when the device is connected and assigned a drive letter I can open file explorer and click on the device and the directory is blank. The SD card does not even show up, but if I take sd and put it in an adapter the sd card is still in tact with everything on it.
Sounds like a driver went haywire try searching the dev section for my thread on how to install adb. I know you have it already but try the diffrent drivers. I would post a link but I'm mobile. Hope it helps
Something.About.Me.U.Dont.Like
Its.Cool.I.Understand.
.AWAH.
Power off
hold vol up and power on
should be in fast boot mode
plug in your USB cable
should now be in fast boot usb mode
run RUU from the computer
RUU should recognise the phone and start installing
I will try this when I get home. So what would cause the phone to act like this? I have read quite a few threads in my quest to fix this phone and a ton of ppl claim bout the only way to brick the hero is by flashing a GSM vs of a. Zip instead of the cdma version. Is this true? I ask because the phone almost acts like it has been locked out somehow.
What happens when you boot into fastboot mode? I held the buttons but the hero still hangs at the white HTC screen.
nordy420 said:
I will try this when I get home. So what would cause the phone to act like this? I have read quite a few threads in my quest to fix this phone and a ton of ppl claim bout the only way to brick the hero is by flashing a GSM vs of a. Zip instead of the cdma version. Is this true? I ask because the phone almost acts like it has been locked out somehow.
Click to expand...
Click to collapse
Yes this is basically true. But if you get the HTC screen, chances are that it is not bricked. I have to ask, did you flash anything like a radio for GSM? If not, then you might need to just let it sit there for an exstended period of time and see if it boots. When I do certain things to my phone, it might take up to 15 minutes to get by the HTC logo screen.
nordy420 said:
What happens when you boot into fastboot mode? I held the buttons but the hero still hangs at the white HTC screen.
Click to expand...
Click to collapse
I wish I could take a screen shot and show you but the phone is not recognised at that point except by the RUU when it is waiting for bootloader. Bootloader is another name for fastboot.
It would be a white screen with green letters and it will say fastboot near the top under the green letters. At the bottom of the screen there will be 3 android characters on skate boards.
This is what you should see. Try again
Important: Make sure the USB is not conected at this time
Power off
Hold volume up, then press the red key (power on)
Fastboot screen comes up
At this point plug in the USB. It will change from Fastboot to Fastboot USB
Run RUU .5 or .6 from the computer
It will get to a point where the install says waiting for bootloader
from there it should start installing
If you can't get to the bootloader screen (fastboot) then I am not sure how to help you
Let me know if it works for you.
Edit: If you are not using ENG SPL or have S-Off read this post. You will need a working knowledge of how to use ADB.
http://forum.xda-developers.com/showthread.php?t=958968
Usually you are still able to get into fastboot, especially if you see the htc screen. Unless you (not really you) destroy the recovery and/or the misc partitions.Did you do this exactly (some people don't do it exactly) pull the battery, reinsert the battery, holding volume up and while holding volume up press the power (end call) button.
If you did then while the phone is stuck on the HTC screen do ......
Open up a command window. Either cd into your windows-sdk/tools folder or just type in the commands if you have the tools folder set as a global environment.
Code:
adb devices
Does it show you a device is connected? If it does you should be able to flash a new recovery image or at least a system.img to get it back up and running.
Thank you for the help by the way. I am not the owner of the phone, I am just more patient than the owner and have nothing to lose if it is screwed lol. http://androidforums.com/sprint-hero-all-things-root/259735-bricked.html. Here is his desperate cry for help after it happened. I own a Droid x and have no idea what he was actually trying to do, but maybe after you read what he did then maybe we can come up with a fix. I agree with you supporters that the phone is not bricked but it is sure being stubborn. Please let me know what ya think. Thanks.
unCoRrUpTeD said:
Usually you are still able to get into fastboot, especially if you see the htc screen. Unless you (not really you) destroy the recovery and/or the misc partitions.Did you do this exactly (some people don't do it exactly) pull the battery, reinsert the battery, holding volume up and while holding volume up press the power (end call) button.
If you did then while the phone is stuck on the HTC screen do ......
Open up a command window. Either cd into your windows-sdk/tools folder or just type in the commands if you have the tools folder set as a global environment.
Code:
adb devices
Does it show you a device is connected? If it does you should be able to flash a new recovery image or at least a system.img to get it back up and running.
Click to expand...
Click to collapse
I will try this when I get home. I did do a battery pull but I did not leave it out very long, but the screen never changed for me, just stayed white with HTC logo in the middle.
Be very sure to disconnect the USB. That was the step I was missing and I could not get it to boot to recovery when it was stuck at the logo. Once the USB was disconnected, took the battery out, put it back in, and held down the home button while pushing the power. That worked! Woot!
Lynne
No luck. The phone will not boot into anything to where a PC will recognize it.
nordy420 said:
No luck. The phone will not boot into anything to where a PC will recognize it.
Click to expand...
Click to collapse
Have you downloaded android commander and gave that a shot? androidcommander.com
android commander recognises the phone when it is at the logo screen. it will see all but the sdcard.
within android commander menu, there is a reboot to bootloader command
Ill try it, and report back
So I messed with android commander a little and could not get it to detect the device. I really think that it is a driver issue. I cannot get the HTC driver to install for the phone. A different driver has been installed for the device and windows will not let me manually install one. I can use the install legacy and the HTC driver is there but it will not correlate with the phone when connected.
RESOLVED!
so I just got my moto x dev edition, unlocked the bootloader, and then screwed it up...
i tried flashing the recovery as described here, http://forum.xda-developers.com/showthread.php?t=2458451 but didn't realize/understand that fastboot and mfastboot were not interchangeable. it looked like it went ok, but I wasn't able to reboot into recovery. so, now on boot to recovery i get the little android on his back with a red triangle. i'm pretty sure that the stock recovery is gone, but cwm is not installed either. which brings me to my next little problem...
so i did some reading and got mfastboot installed and thought ok I just need to reflash cwm on phone again. problem is, now the phone won't stay in usb debug mode so that i can see it when fastbooted. that is, when i reboot the phone into fastboot by holding the power/vol down I can't see the phone when doing 'adb devices', and whem I let it boot up i see usb debug is switched off. when i switch it on, then i can see the phone from adb again, but when i try to 'reboot bootloader' it gives me a not allowed error.
at this point i'm just sick and afraid i bricked it. i am coming from a galaxy nexus and never had anything like this happen before. i truly appreciate any help here, at this point i feel like puking and dreading telling the wife i just blew 450.... :-/
ps i'm on mac 10.7 so if i need rsd it will be via a virtual machine....
herrdrchili said:
so I just got my moto x dev edition, unlocked the bootloader, and then screwed it up...
i tried flashing the recovery as described here, http://forum.xda-developers.com/showthread.php?t=2458451 but didn't realize/understand that fastboot and mfastboot were not interchangeable. it looked like it went ok, but I wasn't able to reboot into recovery. so, now on boot to recovery i get the little android on his back with a red triangle. i'm pretty sure that the stock recovery is gone, but cwm is not installed either. which brings me to my next little problem...
so i did some reading and got mfastboot installed and thought ok I just need to reflash cwm on phone again. problem is, now the phone won't stay in usb debug mode so that i can see it when fastbooted. that is, when i reboot the phone into fastboot by holding the power/vol down I can't see the phone when doing 'adb devices', and whem I let it boot up i see usb debug is switched off. when i switch it on, then i can see the phone from adb again, but when i try to 'reboot bootloader' it gives me a not allowed error.
at this point i'm just sick and afraid i bricked it. i am coming from a galaxy nexus and never had anything like this happen before. i truly appreciate any help here, at this point i feel like puking and dreading telling the wife i just blew 450.... :-/
ps i'm on mac 10.7 so if i need rsd it will be via a virtual machine....
Click to expand...
Click to collapse
so, if i understand you correctly, u've held down the volume down button and power button? becasue that's your fastboot. That's where you need to be to use RSD, and that's what i'd do.
ADB commands aren't used in fastboot mode. You should be able to see the device in fastboot mode with the command fastboot devices. Also, remember that the stock rom will try to restore the stock recovery when it is booted so if you flash recovery in fastboot mode then let the stock rom boot it will reflash the stock recovery which shows you the little droid and the red triangle.
You should still be okay though. Shut the phone off and boot into fastboot manually with power and volume down. Reflash the recovery. I know there are warnings about using mfastboot but I used standard fastboot before I saw those and didn't have an issue. From the fastboot screen after flashing the recovery, use volume down to get to highlight recovery and then press volume up to select, not power. Power will just do a standard reboot.
If you flashed twrp recovery then rebooting system will prompt you to install su. I think clockwork does the same thing. Letting the recovery install su will also prevent the stock recovery from getting restored and from there you should be good.
herrdrchili said:
so I just got my moto x dev edition, unlocked the bootloader, and then screwed it up...
i tried flashing the recovery as described here, http://forum.xda-developers.com/showthread.php?t=2458451 but didn't realize/understand that fastboot and mfastboot were not interchangeable. it looked like it went ok, but I wasn't able to reboot into recovery. so, now on boot to recovery i get the little android on his back with a red triangle. i'm pretty sure that the stock recovery is gone, but cwm is not installed either. which brings me to my next little problem...
so i did some reading and got mfastboot installed and thought ok I just need to reflash cwm on phone again. problem is, now the phone won't stay in usb debug mode so that i can see it when fastbooted. that is, when i reboot the phone into fastboot by holding the power/vol down I can't see the phone when doing 'adb devices', and whem I let it boot up i see usb debug is switched off. when i switch it on, then i can see the phone from adb again, but when i try to 'reboot bootloader' it gives me a not allowed error.
at this point i'm just sick and afraid i bricked it. i am coming from a galaxy nexus and never had anything like this happen before. i truly appreciate any help here, at this point i feel like puking and dreading telling the wife i just blew 450.... :-/
ps i'm on mac 10.7 so if i need rsd it will be via a virtual machine....
Click to expand...
Click to collapse
ok then - i guess rsd has potential?
xpsychox said:
so, if i understand you correctly, u've held down the volume down button and power button? becasue that's your fastboot. That's where you need to be to use RSD, and that's what i'd do.
Click to expand...
Click to collapse
i can reboot into fastboot, but adb can't see the phone. I'll start trying to setup rsd and and see if it can do any better. any good links you know to get up to speed on that would be appreciated. if you know how to simply reflash the recovery via rsd that would be helpful too - thanks in advance!
herrdrchili said:
i can reboot into fastboot, but adb can't see the phone. I'll start trying to setup rsd and and see if it can do any better. any good links you know to get up to speed on that would be appreciated. if you know how to simply reflash the recovery via rsd that would be helpful too - thanks in advance!
Click to expand...
Click to collapse
the sites that I know of are for the device I have, a non devliper edition... I don't know if it makes a difference, I don't wanna make anything worse.
thanks for the sanity check,,,
btdonovan said:
ADB commands aren't used in fastboot mode. You should be able to see the device in fastboot mode with the command fastboot devices. Also, remember that the stock rom will try to restore the stock recovery when it is booted so if you flash recovery in fastboot mode then let the stock rom boot it will reflash the stock recovery which shows you the little droid and the red triangle.
You should still be okay though. Shut the phone off and boot into fastboot manually with power and volume down. Reflash the recovery. I know there are warnings about using mfastboot but I used standard fastboot before I saw those and didn't have an issue. From the fastboot screen after flashing the recovery, use volume down to get to highlight recovery and then press volume up to select, not power. Power will just do a standard reboot.
If you flashed twrp recovery then rebooting system will prompt you to install su. I think clockwork does the same thing. Letting the recovery install su will also prevent the stock recovery from getting restored and from there you should be good.
Click to expand...
Click to collapse
THANKS! just needed another set of eyes - man i need to not try doing this after a long day again i really appreciate your help. i got it now!
herrdrchili said:
THANKS! just needed another set of eyes - man i need to not try doing this after a long day again i really appreciate your help. i got it now!
Click to expand...
Click to collapse
Glad I could help!
Hi all,
A while back I installed Cyanogenmod 11 on my tf701t, and also installed Linux (Arch).
This was working perfectly - or at least gave me what I needed.
I would reboot normally and Cyanogen mod would boot - and if I booted with power+vol down, I could access the menu, choose RCK, and Linux would boot.
Recently it is only booting into Linux (RCK). Powering up normally would boot into Linux, and Power + vol down also boots into Linux - I seem to have lost the boot menu and the ability to boot Cyanogenmod. Linux itself is still running fine, but I still want access to Cyanogenmod. How can I restore the menu, and specifically make it appear on power+vol down butttons.
Any thoughts?
I've (re)downloaded the firmware from ASUS, but don't I need to power+vol down in order to install it? Is there any other way?
Thanks for reading.
Can you give a link to the boot loader or firmware that you're currently running? I'm interested in what you're talking about... it sounds like an old mod... I have never heard of Linux booting in recovery mode... Or are you talking about recovery mode how...? So, what exactly happens when you select RCK, it boots into what?? You're not getting confused between CWM recovery or similar and an actual operating system Linux?
I found the link but it seems like it has a lot of bugs. http://forum.xda-developers.com/transformer-tf701/general/native-linux-asus-tf701t-t2973119
You should post your question in that thread. That sounds like a great project and I would install it if it was more stable.
Thanks for responding.
I actually used the link you provided above and it works perfectly.
I had it booting into Linux when RCK was selected, and CyanogenMod when Android was selected.
That's what I meant by having Linux in Recovery mode. I don't have CWM Recovery installed (only used that briefly to get CM11 installed, then it wasn't required) So what I have installed is Linux + Cyanogen, but can only access Linux at the moment.
The problem now is that the boot menu no longer appears, so I can not select between them....regardless of what I press, (vol down+power etc). It would just boot into Linux each time. The only key press that I seems to do something is (vol+ & Power), which takes me to APX mode - but is there anything I can do in that mode?
What I really need is to get the menu back and/or be able to access fastboot mode. Not sure if there's some other key press combo or other hack that I'm not trying. I actually don't know how I got to this state as I wasn't messing around with anything before I lost the menu.
Can't find out the firmware version as that is displayed in the menu that isn't appearing (or in Android), but I did install the latest US version from ASUS, whatever that is.
adiabuk said:
Thanks for responding.
I actually used the link you provided above and it works perfectly.
I had it booting into Linux when RCK was selected, and CyanogenMod when Android was selected.
That's what I meant by having Linux in Recovery mode. I don't have CWM Recovery installed (only used that briefly to get CM11 installed, then it wasn't required) So what I have installed is Linux + Cyanogen, but can only access Linux at the moment.
The problem now is that the boot menu no longer appears, so I can not select between them....regardless of what I press, (vol down+power etc). It would just boot into Linux each time. The only key press that I seems to do something is (vol+ & Power), which takes me to APX mode - but is there anything I can do in that mode?
What I really need is to get the menu back and/or be able to access fastboot mode. Not sure if there's some other key press combo or other hack that I'm not trying. I actually don't know how I got to this state as I wasn't messing around with anything before I lost the menu.
Can't find out the firmware version as that is displayed in the menu that isn't appearing (or in Android), but I did install the latest US version from ASUS, whatever that is.
Click to expand...
Click to collapse
Ok, first off I understand why you cannot post in the correct thread because XDA restrictions on newbie post limits... Second, all you need to do is flash one of the latest recovery images, TWRP or CWM or cm recovery. This you will need to do with your computer in fastboot mode to flash the .img... you will possibly lose the Lenox installation and possibly all data, but if you reinstall it possibly could detect the correct partition and have your data... I would suggest that you install recovery and then install the latest cm 12.1 or another recent ROM and make sure that your Asus firmware is the latest also... Which should be US 11.4.1.29... then, I would suggest trying to install the Linux partition on your external SD card instead of internal memory as they are currently talking about on that thread... here is a link for the TWRP recovery image: http://forum.xda-developers.com/showpost.php?p=61045480&postcount=2
K94U said:
This you will need to do with your computer in fastboot mode to flash the .img...
Click to expand...
Click to collapse
This is exactly my problem - I can't get to fastboot mode - only linux and APX mode.
If fastboot is what you get to when pressing power+vol down, then this is no longer working, it seems to have no affect and will still boot into Linux. If there's another way to get into fastboot that would be ideal.
Not too worried about losing data - I have backups so can wipe everything if need be
adiabuk said:
This is exactly my problem - I can't get to fastboot mode - only linux and APX mode.
If fastboot is what you get to when pressing power+vol down, then this is no longer working, it seems to have no affect and will still boot into Linux. If there's another way to get into fastboot that would be ideal.
Not too worried about losing data - I have backups so can wipe everything if need be
Click to expand...
Click to collapse
Use this link: https://wiki.cyanogenmod.org/w/Install_CM_for_tf701t and scroll down to where it says "Installing recovery using fastboot" is not a fun process and you have to have all the correct drivers and everything on your computer... If fastboot is not working for you, then you might have to do a complete flash to stock from a ASUS which you can use the computer or your external sd card to do... fastboot mode can be a black blank screen so you never really know if you're in it or not. Have you tried to hold both volume up and down with power button? You need to try every option and then connected to computer to see if it detects it...
K94U said:
Use this link: and scroll down to where it says "Installing recovery using fastboot" is not a fun process and you have to have all the correct drivers and everything on your computer... If fastboot is not working for you, then you might have to do a complete flash to stock from a ASUS which you can use the computer or your external sd card to do... fastboot mode can be a black blank screen so you never really know if you're in it or not. Have you tried to hold both volume up and down with power button? You need to try every option and then connected to computer to see if it detects it...
Click to expand...
Click to collapse
Thanks for the suggestions
Yes, fastboot is not an option, used it before so no worries with drivers, but can't get to that mode now let alone connect to it.
Volume down and power does the same if pressing only power - just boot into Linux.
Volume Up and power takes me to APX mode (with the blank screen) - AFAIK this is different to fastboot mode. Linux detects it as Nvidia, not ASUS which it did previously when I was able to use fastboot mode. Either way, I've tried sudo fastboot mode when it's in APX mode, and it doesn't list the device. If there's something I can do in APX mode then that will work, but after reading many threads I couldn't find how to use APX mode on the tf701t.
I always thought fastboot was the bootloader (ie when the menu appears), which I'm not getting now - and this is also required for flashing back to stock from SD - am I right?
Fastboot mode is a hidden link to the root boot partition... The menu that you get to choose from RCK and such is the actual boot menu and the firmware that should be current from ASUS... The RCK option selects a certain partition of memory allocated for a separate mini os such as a recovery image or Linux...?.?.?.? Lol... if I were you, I would update the firmware to latest stock using the SD card... you can search for the link or I'll post it tomorrow because I'm about to fall asleep, good night...
K94U said:
Fastboot mode is a hidden link to the root boot partition... The menu that you get to choose from RCK and such is the actual boot menu and the firmware that should be current from ASUS... The RCK option selects a certain partition of memory allocated for a separate mini os such as a recovery image or Linux...?.?.?.? Lol... if I were you, I would update the firmware to latest stock using the SD card... you can search for the link or I'll post it tomorrow because I'm about to fall asleep, good night...
Click to expand...
Click to collapse
I'm not really sure how to flash anything at the moment as there's no bootloader
Here's a quick video I made of the current bootup: https://youtu.be/cLFXiEEVBD0
This sequence of events happens weather I press power+ vol down or not.
All instructions I've read including this: www.transformerforums.com/forum/gui...e-firmware-tf700-tf701-tf300-tf101-tf201.html
suggest that I need to have a bootloader, or fastboot, or a working android (ADB), but all of these require a working bootloader.
I tried putting the latest firmware on an SD, rebooting with power+vol down as the above instructions say, but I still get it booting into Linux as in the video. Instructions for installing TWRP/CWM etc also require fastboot or bootloader (for microSD).
So in the absence of having a bootloader (or anything provoked by power+ctrl down) - am I just stuck with my current setup?
Here is a possible solution over in the Linux thread: http://forum.xda-developers.com/showpost.php?p=62814146&postcount=179
this was a concern of mine as well about installing linux on my tf701 using this method.. I think one of the posts about multi boot recovery where linux sits actually makes mention of not being able to go back to a standard setup and losing recovery mode altogether.. As much as I'd love to run linux on my tf701, I dont know that I could deal with losing the ability to flash android roms and mods.
How did things turn out for you? Did you manage to figure a way around this dilemma?