Related
Hey guys. I am running ubuntu 10.10 and i have successfully installed android sdk and the eclipse in their proper places and added the neccessary coding to make everything work. One problem though. When i have my G1 32B in fastboot mode, it wont recognize my phone so i can use fastboot to flash the newest radio and SPL. i know others have achieved to being able to flash it without a problem.. I have tried to troubleshoot this myself with the help of the internet and xda... but still the same problem keeps re occuring. and to tell you the truth, it is really pissing me off. I have downloaded fastboot drivers and placed them in the sdk/tools folder and moved adb to that folder as well for easier access. I dont know what else to do. If any one has any solutions or would be a help please. Thank you for reading.
bosna110 said:
. When i have my G1 32B in fastboot mode, it wont recognize my phone so i can use fastboot to flash the newest radio and SPL
Click to expand...
Click to collapse
The question is: can linux see the phone (plug in the phone while in fastboot mode and check dmesg)
If linux sees it and fastboot can't.. make sure its not permission issues [read is fastboot running as root? if not can your user read the USB device?] The phone identifies its self differently in fastboot mode vs. adb/mass storage mode. So don't assume the fact adb works from your normal login means fastboot will also.
linux sees it no problem.. but when im in fastboot mode, its not wanting to list the device.
Try executing fastboot as root.
Sent from my Gingerbread on Dream using XDA App
ok give me 1 sec.. ill go try it our right now. i am trying to flash terry's spl and radio so i can have the extra 14 or 15 megs of ram extra because my g1 is so sluggish right now i can barely use it for anything.
Strange thing with me is that it loads a different driver in fastboot. If I have it turned on normally, in my Device Manager it shows as "ADB interface -> HTC Dream Composite ADB Interface". (I think it used to show as just "HTC Dream"). I had to switch to HTC Bootloader. :/
Edit: only skimmed. Missed anything about Linux.
He's on linux ... the drivers should load automatically.
Sent from my Gingerbread on Dream using XDA App
ok i must be doing something wrong its either me or the laptop.. im doing "su" on the terminal and then when i enter in my password, it says auth failed.... this is friggen bee ess
Try
sudo fastboot devices
And when asking for the password you enter your user's password.
Sent from my Gingerbread on Dream using XDA App
still doing the same thing.
ok, what i did was
1. open terminal
2. cd sdk/tools
3. now i make sure my phone is recognizable while in fastboot mode so i do ./adb devices
4. then when i look at the listed devices, my phone isnt listed..
5. then i try doing sudo fastboot devices and entering my password and its still not working.
let me try restarting my laptop.. perhaps that is going to fix it..
ok, just to make my self look dumber lol.. when my phone is shut off
i pressed back and the power buttons at the same time until the white screen with the android skateboards come up.. am i supposed to then press the trackball button to get into fastboot mode?
cause maybe i am not pressing something correctly to get it to work right. ill keep refreshing this page every minute for a reply..
bosna110 said:
3. now i make sure my phone is recognizable while in fastboot mode so i do ./adb devices
Click to expand...
Click to collapse
adb will never work if you are in fastboot mode... and fastboot will only work when in fastboot mode.
so Dont run './adb devices' run './fastboot devices' or as we mentioned to run it as root 'sudo ./fastboot devices'
ok, gotcha. when i did the ./fastboot devices, it told me the Permission denied.
im sorry, i must be really brain dead right now.. i totally forgot to checkmark fastboot as an exectuable on its properties.. now its recognizing my G1 no problem. now its the flashing that is giving me some trouble
Hello!
I think i've bricked my Mi A2.
I have unlocked bootloader but locked critical partition which i cant unlock cause theres no OS to boot into and check the OEM option. Are there any alternatives before opening the phone for EDL?
xunixbeatsx said:
Hello!
I think i've bricked my Mi A2.
I have unlocked bootloader but locked critical partition which i cant unlock cause theres no OS to boot into and check the OEM option. Are there any alternatives before opening the phone for EDL?
Click to expand...
Click to collapse
if you can at least boot on fastboot and it's working, you can enter on edl mode from fastboot, there is a command to do it
Adairo said:
if you can at least boot on fastboot and it's working, you can enter on edl mode from fastboot, there is a command to do it
Click to expand...
Click to collapse
Yeah already tried that but adb wont work
"no devices / emulators found". I think my computer cant see this devices mode, i also cant mount it when i use Clockwork.
I can use fastboot commands just fine though
xunixbeatsx said:
Yeah already tried that but adb wont work
"no devices / emulators found". I think my computer cant see this devices mode, i also cant mount it when i use Clockwork.
I can use fastboot commands just fine though
Click to expand...
Click to collapse
You should try flashing the ROM normally. Just use the included script
ADB commands works only booted phone with USB dev mode.
Fastboot commands with fastboot mode. So you cant use ADB commands when your phone not booted up.
Daniesz said:
ADB commands works only booted phone with USB dev mode.
Fastboot commands with fastboot mode. So you cant use ADB commands when your phone not booted up.
Click to expand...
Click to collapse
You dont have to boot phone to use ADB, you can adb sideload inside Clockwork (i sideloaded no-verity just fine).
By the way i managed to fix my phone by extracting the firmware and fastboot flash files one by one (2 files couldnt be installed cause they needed critical partition unlocked but it seems they werent anything critical cause phone works fine).
xunixbeatsx said:
Yeah already tried that but adb wont work
"no devices / emulators found". I think my computer cant see this devices mode, i also cant mount it when i use Clockwork.
I can use fastboot commands just fine though
Click to expand...
Click to collapse
Enter to fastboot Is all you need to get into edl mode and attemp to flash stock rom
Adairo said:
Enter to fastboot Is all you need to get into edl mode and attemp to flash stock rom
Click to expand...
Click to collapse
I tried that and was no response from the phone.
I also tried edl from ADB, phone restarted but no edl mode.
xunixbeatsx said:
I tried that and was no response from the phone.
I also tried edl from ADB, phone restarted but no edl mode.
Click to expand...
Click to collapse
I've thé same issue. If you fastboot is "broken" you dont have choice you need to short pin (it's easy)..
xunixbeatsx said:
I tried that and was no response from the phone.
I also tried edl from ADB, phone restarted but no edl mode.
Click to expand...
Click to collapse
Did you try to just run the script with the fastboot commands? If you didn't modify critical partitions it should just work fine. Just ignore the error messages
Benjamin_L said:
Did you try to just run the script with the fastboot commands? If you didn't modify critical partitions it should just work fine. Just ignore the error messages
Click to expand...
Click to collapse
I manually fastboot flash the files which i suppose is the same as with running the script, but i wanted to see which files wont get transfered cause of the locked critical partition. Android installed fine but couldnt install updates (edit: Thats probably because i rooted my device, it seems you cant automatic upgrade if you root) so i enabled OEM, unlocked critical partition, flashed normally with MiFlash tool, everythings like new now.
Now i only need a working Xposed Framework version.
Ok..so here's the situation. I was going to install a new ROM ( my son got a new phone a iphone ) but any ways. As I was in TWRP i did everything we all normally do but the phone died mid flashing GAPPS. when i went to pulg the phone to the charger and restart the phone i see that it started to boot up the it jumped straight to FASTBOOT and it's stuck. I can toggle through fastboot but that is it. when i go to restart it will show the boot animation but then goes to fast boot. it wont go to TWRP nothing. I've combed XDA and found the multi tool but don't think that is working or i might be using it wrong. the computer doesn't recognize the phone. im trying to get this phone back up and going and give to my daughter . any help is greatly appreciated. thank you in advacne.
Here's what I'm talking about just in case someone asks
Try installing a stock factory image from fastboot.
runekock said:
Try installing a stock factory image from fastboot.
Click to expand...
Click to collapse
How...I can't get my computer to recognize the phone... When I plug it in it doesn't read it...I should have the drivers already installed...adb push right.... I'll search for the command to see if it finds the phone
adb never works in fastboot mode. You'll have to use the fastboot command.
On the PC, try
fastboot devices
to see whether the phone is available. If not, check your drivers - I believe that fastboot uses a different USB driver.
With fastboot, you can't install zip-files, only image files. So download the stock factory image, not the OTA.
runekock said:
adb never works in fastboot mode. You'll have to use the fastboot command.
On the PC, try
fastboot devices
to see whether the phone is available. If not, check your drivers - I believe that fastboot uses a different USB driver.
With fastboot, you can't install zip-files, only image files. So download the stock factory image, not the OTA.
Click to expand...
Click to collapse
Thanks for the heads up I'll definitely be trying this and I'll give you an update soon
I was in a13, my recovery was twrp. Since it can't decrypt a13, i flashed ofox
fastboot flash recovery ofox
fastboot reboot recovery
after this command, it went into fastboot mode.
I'm trying all key combinaton, it is rebooting to fastboot page only.
Unable to get into recovery nor system.
I tried flashing recovery again, since it is in fastboot page,
But in my pc it is showing
C:\Users\Lenovo>fastboot flash recovery "E:\New folder\OrangeFox-R12.1_3-Unofficial-sweet.zip"
< waiting for any device >
What to do!?
Siv231 said:
I was in a13, my recovery was twrp. Since it can't decrypt a13, i flashed ofox
fastboot flash recovery ofox
fastboot reboot recovery
after this command, it went into fastboot mode.
I'm trying all key combinaton, it is rebooting to fastboot page only.
Unable to get into recovery nor system.
I tried flashing recovery again, since it is in fastboot page,
But in my pc it is showing
C:\Users\Lenovo>fastboot flash recovery "E:\New folder\OrangeFox-R12.1_3-Unofficial-sweet.zip"
< waiting for any device >
What to do!?
Click to expand...
Click to collapse
The latest 3.7 TWRP can. If you are stuck in fastboot like this, you can get out of that soft brick yourself. Just reflash each .img of the original ROM one at a time, then reboot system.
Siv231 said:
I was in a13, my recovery was twrp. Since it can't decrypt a13, i flashed ofox
fastboot flash recovery ofox
fastboot reboot recovery
after this command, it went into fastboot mode.
I'm trying all key combinaton, it is rebooting to fastboot page only.
Unable to get into recovery nor system.
I tried flashing recovery again, since it is in fastboot page,
But in my pc it is showing
C:\Users\Lenovo>fastboot flash recovery "E:\New folder\OrangeFox-R12.1_3-Unofficial-sweet.zip"
< waiting for any device >
What to do!?
Click to expand...
Click to collapse
"recovery.img" is inside "OrangeFox-R12.1_3-Unofficial-sweet.zip".
Wait for someone to confirm if you can use fastboot directly with it (I haven't used OFox yet).
Never mind. OFox was the one that caused your issues.
Compass.
Siv231 said:
I was in a13, my recovery was twrp. Since it can't decrypt a13, i flashed ofox
fastboot flash recovery ofox
fastboot reboot recovery
after this command, it went into fastboot mode.
I'm trying all key combinaton, it is rebooting to fastboot page only.
Unable to get into recovery nor system.
I tried flashing recovery again, since it is in fastboot page,
But in my pc it is showing
C:\Users\Lenovo>fastboot flash recovery "E:\New folder\OrangeFox-R12.1_3-Unofficial-sweet.zip"
< waiting for any device >
What to do!?
Click to expand...
Click to collapse
Not flashing zip via fastboot. Try unzip the image and flash it with correct name and IMG extension.
(The zip you can only flash via working recovery)
Though the phone is in fastboot page, it is not showing in pc
when i type
>fastboot devices
It's showing
<waiting for any device>
Siv231 said:
Though the phone is in fastboot page, it is not showing in pc
when i type
>fastboot devices
It's showing
<waiting for any device>
Click to expand...
Click to collapse
I had this problem too and got it to work like this:
Connect phone to PC;
Enter fastboot mode;
Profit.
If I enter fastboot mode and then connect to my PC it doesn't get detected. Silly, I know.
Compass.
Compass Linux said:
I had this problem too and got it to work like this:
Connect phone to PC;
Enter fastboot mode;
Profit.
If I enter fastboot mode and then connect to my PC it doesn't get detected. Silly, I know.
Compass.
Click to expand...
Click to collapse
Bro, my phone is only in fastboot mode.
If long pressed power button, it reboot and enter fastboot page again.
I dont see anything other than android machine repairing image ??Fastboot page.
Siv231 said:
Bro, my phone is only in fastboot mode.
If long pressed power button, it reboot and enter fastboot page again.
I dont see anything other than android machine repairing image ??Fastboot page.
Click to expand...
Click to collapse
Try the following:
In fastboot mode connect your phone to your PC;
Long press the Power button and let it enter fastboot mode again;
See if "fastboot devices" detects your phone.
I hope this works.
Compass.
Compass Linux said:
Try the following:
In fastboot mode connect your phone to your PC;
Long press the Power button and let it enter fastboot mode again;
See if "fastboot devices" detects your phone.
I hope this works.
Compass.
Click to expand...
Click to collapse
No, it is not detecting the device.
fastboot devices
<empty_line>
Siv231 said:
No, it is not detecting the device.
fastboot devices
<empty_line>
Click to expand...
Click to collapse
That's as far as my knowledge goes.
If it was working before then your drivers are OK. I hope someone else can help you.
Compass.
Compass Linux said:
That's as far as my knowledge goes.
If it was working before then your drivers are OK. I hope someone else can help you.
Compass.
Click to expand...
Click to collapse
I regret my action of getting in it(flashing) today. Thanks. at leaast i had a hope someone is there to help.
Compass Linux said:
That's as far as my knowledge goes.
If it was working before then your drivers are OK. I hope someone else can help you.
Compass.
Click to expand...
Click to collapse
Good news!
What happened is the same thing..
Reiboot tool, that helped me in getting out of that false fastboot screen and enter into the real working fastboot screen.
after that, it was detected in my pc..
I flashed twrp and rebooted to system.
i'm gonna stay in the same rom.//atleast for now
Many a thanks to you....
@Laptapper @Compass Linux @Sheist!
I'll do the same as u said, wrt ofox. @Laptapper
I'll check o [email protected]!
Special Thanks to Google = shown me the tool
Siv231 said:
Good news!
What happened is the same thing..
Reiboot tool, that helped me in getting out of that false fastboot screen and enter into the real working fastboot screen.
after that, it was detected in my pc..
I flashed twrp and rebooted to system.
i'm gonna stay in the same rom.//atleast for now
Many a thanks to you....
@Laptapper @Compass Linux @Sheist!
I'll do the same as u said, wrt ofox. @Laptapper
I'll check o [email protected]!
Special Thanks to Google = shown me the tool
Click to expand...
Click to collapse
Pls share the tool you've found
Laptapper said:
Pls share the tool you've found
Click to expand...
Click to collapse
Click Here for Reiboot Tool.
This helps in force exit the Fastboot mode.
With premium, we can get more options.
Siv231 said:
...
This helps in force exit the Fastboot mode.
...
Click to expand...
Click to collapse
I will believe you, because you are up and running again, but can't imagine how this is possible without the recognition of devices.
Siv231 said:
Click Here for Reiboot Tool.
This helps in force exit the Fastboot mode.
With premium, we can get more options.
Click to expand...
Click to collapse
For those interested, 10 bucks USD a month, 20 for a year, 30 for a lifetime. Apparently the free trial only lets you test the interface and enter recovery mode, but I am not testing it myself.
I hope the OP isn't an employee of Tenorshare since his join of XDA was only 2 weeks ago.
Sheist! said:
For those interested, 10 bucks USD a month, 20 for a year, 30 for a lifetime. Apparently the free trial only lets you test the interface and enter recovery mode, but I am not testing it myself.
I hope the OP isn't an employee of Tenorshare since his join of XDA was only 2 weeks ago.
Click to expand...
Click to collapse
Hahah. I'm not...
Lemme Explain....
I tried many custom rom and found Arrow OS as perfect fit for me in BB. I use only official build. But then the evening of that day, I got suggestion(rn10p Telegram group), that LOS 20 Pulkit ver. is far better than arrow in terms of BB, aryan is good for gaming.
I'm not a developer or anywhere related to programming.
In fact my first post is how to build my own Custom Rom.
(I tried that, upon seeing the repo downloading, i stopped..)
Ok...
That's a brief.
LOS will be smooth, no doubt in it. But after reading his suggestions, I was so attracted to it.
TWRP 3.6.10, since it can't decrypt, I flashed OFOx via adb sideload, and rebooted it.
I think the error is happened here.//still I dont what exactly was happened. explain if u have any idea.
After that i can see only fastboot screen on my mob. But PC is not detecting it.
In device manager, I saw android connected with yellow warning sign.
I dont have any spare mobile, mid night, I'm staying in city, far from natives. So stressed. By then, I was messaging in that group(Fortunately, i opened telgarm web, gmail on PC). None is responding.
Then thought of posting here.
Upon googling it out of hope, I came across, force exiting fastboot screen(From a Quora page). I tried that with Zero hope.
I got it.
With happy face, I came here to thank. Since Laptapper asked me to share that tool, I shared here.
Sorry for this long texts. This is me.
Elinx said:
I will believe you, because you are up and running again, but can't imagine how this is possible without the recognition of devices.
Click to expand...
Click to collapse
Even I have no idea. I was trying all key combinations, and cmd command again and again.
I tried that in no hope.
Fortunately, it worked.
Hello all, I'm trying to install a new ROM but one of the first steps consists in getting access to adb and fastboot mode.
Unfortunately, I can easily access to adb mode, and adb commands respond well, but when I then go in fastbood mode 'adb reboot fastboot", My phone goes to fastboot with the icon on the screen, but won't answer to any fastboot commands.
I've tried to install adb drivers, uninstall/reinstall the drivers (but it's always the windows drivers that installs first). I even tried to install google usb drivers using SDK manager, but didn't succeed this step.
I've tried to change the usb cable, but with another one, it was worse: even the adb commands would not work. So I guess the one I'm using is ok.
I'd be very happy if someone could help me fixing this frustrating bug!
Model:M1903F11A
kernel:4.14.117-perf-g0f2347b
MIUI Global 12.0.6
Android version : 10 QKQ1.190825.002
Cyjam said:
.. new ROM but one of the first steps consists in getting access to adb and fastboot mode.
...
Click to expand...
Click to collapse
The first step is to unlock the bootloader.
Cyjam said:
... when I then go in fastbood mode 'adb reboot fastboot", My phone goes to fastboot with the icon on the screen, but won't answer to any fastboot commands.
....
Click to expand...
Click to collapse
For fastboot try:
adb devices
........... (here you must see a number)
adb reboot bootloader
fastboot devices
........... (here you must see that number again)
Hi, thanks for trying to help me:
you're right , first is the unlock, but it's done. it's even in "grey" on the screen and written: bootloader is already unlocked. I've tested my phone with "root checker" and test is ok.
you're right about the command, this is the one I've used to go to fastmode and actually this command works: as I said, when in adb mode, it's all good: my phone is connected to pc and accepts the adb commands. But once I switch to fastboot, this is when it's going wrong: my phone's not answering to any commands.
To be more precise: when prompting: adb devices: i get a number. When prompting, in fastbood mode, fastboot devices: i get nothing.
Alleluia!!
Finally found out how to fix it!
After going in fasboot mode with the command: adb reboot bootloader, i opened the windows device manager: There I found a android XXx interface, or something like this: anyway, something barely identified by windows. Right clik, update drivers, manually update, pointing to the folder I store the google usb drivers and : Bingo! It works like a treat.
I now can step further in the process... Hope I won't need to come back with another question in the next minutes!