PS C:\adb> fastboot --set-active b
C:\adb\fastboot.exe: unknown option -- set-active
That's the error I'm getting in fastboot. Any ideas?
localceleb said:
PS C:\adb> fastboot --set-active b
C:\adb\fastboot.exe: unknown option -- set-active
That's the error I'm getting in fastboot. Any ideas?
Click to expand...
Click to collapse
Try...fastboot --set-active=b
Badger50 said:
Try...fastboot --set-active=b
Click to expand...
Click to collapse
Same result.
localceleb said:
Same result.
Click to expand...
Click to collapse
Have you updated your platform-tools, tried a different cable, and you are in fastboot mode?
Badger50 said:
Try...fastboot --set-active=b
Click to expand...
Click to collapse
Badger50 said:
Have you updated your platform-tools, tried a different cable, and you are in fastboot mode?
Click to expand...
Click to collapse
Yes to all of those.
So, phone was fine this morning. Booted to twrp to make a backup so i could play with something different. Made the backup and rebooted, but it wouldn't boot the OS. It kept kicking me back to twrp, but twrp wouldnt fully load. Froze on the splash screen. So I rebooted to bootloader and tried to fastboot boot twrp and the same thing was happening with the splash screen. So went back to bootloader to try and swtch slots and here we are now. I've tried different cables and know that i'm up to date.
localceleb said:
Yes to all of those.
So, phone was fine this morning. Booted to twrp to make a backup so i could play with something different. Made the backup and rebooted, but it wouldn't boot the OS. It kept kicking me back to twrp, but twrp wouldnt fully load. Froze on the splash screen. So I rebooted to bootloader and tried to fastboot boot twrp and the same thing was happening with the splash screen. So went back to bootloader to try and swtch slots and here we are now. I've tried different cables and know that i'm up to date.
Click to expand...
Click to collapse
That doesn't sound good. You may have to fastboot the factory image again without the -w to get back up and running.
Badger50 said:
That doesn't sound good. You may have to fastboot the factory image again without the -w to get back up and running.
Click to expand...
Click to collapse
That was my thought, but wanted to avoid that if possible. I'm not sure why the slot command isnt working.
localceleb said:
That was my thought, but wanted to avoid that if possible. I'm not sure why the slot command isnt working.
Click to expand...
Click to collapse
Couldn't tell you my friend as to the why it happened. Dang ghosts in the machine!
What about fastboot --set-active=_b ?
rickysidhu_ said:
What about fastboot --set-active=_b ?
Click to expand...
Click to collapse
same result
localceleb said:
Any ideas?
Click to expand...
Click to collapse
fastboot set_active b, according to an OG pixel thread that I found.
You probably don't have the lastest platform tools. I had a similar problem cuz I was using platform tools from like 2 years ago. Do "fastboot --version" without quotes to see what version you're running. I'm using 28.0.1 without problems.
If you need, download the latest from here and see if that helps.
I suggest you try using Deuce's script...
He designed it so it flashes all the images on BOTH the A and B slots; it might set you back right to the correct slots. Also, he gives the option of not wiping your data (iteration of -w or not)
Good luck and hope this helps...
amartolos said:
You probably don't have the lastest platform tools. I had a similar problem cuz I was using platform tools from like 2 years ago. Do "fastboot --version" without quotes to see what version you're running. I'm using 28.0.1 without problems.
If you need, download the latest from here and see if that helps.
Click to expand...
Click to collapse
I had the same problem, I changed the platform tools, some cmd command would work then not, worked great m10,u11 & u11+ . It was the usb drivers which was giving me the problems.
Are you using PowerShell or windows terminal. I noticed this issue using those terminals...if you are using windows 10 , then navigate to the folder and then click on the address bar and type cmd..you will be redirected to the terminal..or you can always use cd {folder path}
techydawg said:
Are you using PowerShell or windows terminal. I noticed this issue using those terminals...if you are using windows 10 , then navigate to the folder and then click on the address bar and type cmd..you will be redirected to the terminal..or you can always use cd {folder path}
Click to expand...
Click to collapse
This was my problem. Thanks!
techydawg said:
Are you using PowerShell or windows terminal. I noticed this issue using those terminals...if you are using windows 10 , then navigate to the folder and then click on the address bar and type cmd..you will be redirected to the terminal..or you can always use cd {folder path}
Click to expand...
Click to collapse
I learnt today through trying to trouble shoot bad notes on unlocking the G7 bootloader that you can type CMD in powershell then you have proper working command promt withing powershell
the benefit of this is when using commands like
Code:
fastboot flash *******.img (here is where you can drag and drop file name)
You just need to make sure after the last character in the flash syntax you leave a space before you drag and drop the file into PowerShell
Hope this makes sense
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Madaz2 said:
you can type CMD in powershell then you have proper working command promt withing powershell
Click to expand...
Click to collapse
I've been doing this for several years now. I'm pretty sure in my older posts on the 2XL forum I've mentioned it. Too bad I didn't see this thread until today
localceleb said:
PS C:\adb> fastboot --set-active b
C:\adb\fastboot.exe: unknown option -- set-active
That's the error I'm getting in fastboot. Any ideas?
Click to expand...
Click to collapse
yes Its happed with me. reason: i forgot to allow pop up of USB Debbuging authorization, then i flashed magisk boot img on fastboot mode... then stucked into recovery ... for god sake i had back up apps on my Google account... but data was deleted...
Related
forgive my ignorance, i'm new in this kind of stuff, and i need some help.
i would like to flash this new kernel by franco (link below) but i'm confused/lost so can someone give me a step by step instruction? i'd really appreciate it i mean a lot! i've already unlocked the boot loader, its showing as s-on
http://forum.xda-developers.com/showthread.php?t=1646883
Flash the modules package in clockworkmod recovery.
To flash the rest you have to have the android sdk installed and you have to put the boot.img file in the same folder as fastboot.exe. From a command prompt you have to navigate to the folder that has those files and use the command "fastboot flash boot boot.img " while your phone is in fastboot.
Sent from my HTC One X using xda premium
thanks... but can you do it in more specific way? like step 1.1.3.4.5...etc..
mikey0105 said:
thanks... but can you do it in more specific way? like step 1.1.3.4.5...etc..
Click to expand...
Click to collapse
1. Download the Fastbbot files
2. Extract it to the root of your drive (C: or D So you should have a "Fastboot files" folder in your C or D drive
3. Now put the boot-r1.img in the Fastboot files folder
4. Start up command prompt (type "cmd" in the search bar) and navigate to the fast files folder. To navigate to the fastboot files folder you have to type "cd\" and then type "cd\Fastboot files".
5. Now boot your phone into bootloader (by holding down power button for a few seconds until it reboots and then press and hold down the volume down (-) button). And then once in fastboot mode select "Fastboot USB" by pressing the power button.
6. Now type the commands "fastboot flash boot boot-r1.img" and that's it.
that's what im talkin' about shadowboy! thanks so much! 1 big thank you button for you.. cheers mate!
EDIT:
oh BTW, i tried opening CMD, then entered the words above but its not opening, it says cannot find path,
i put my files under 1 folder named it "fastboot"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My mistake it suppose to be "Fastboot" folder not "Fastboot files" folder.
thanks for doing an extra mile to explain this thing to me, really appreciate it.. im starting to learn
No worries.
after it says "finished" i closed the CMD and restarted my phone, so everything is okay after that? it took like 1 second to complete
mikey0105 said:
after it says "finished" i closed the CMD and restarted my phone, so everything is okay after that? it took like 1 second to complete
Click to expand...
Click to collapse
Yes you're done. That's all you have to do.
i forgot to mention, i went to recovery, then installed the modules there via zip file then rebooted the phone
EDIT:
o shoot, is this normal, after rebooting, it wont turn on, i mean, its just showing htc and its been like 4 mins now
mikey0105 said:
i forgot to mention, i went to recovery, then installed the modules there via zip file then rebooted the phone
EDIT:
o shoot, is this normal, after rebooting, it wont turn on, i mean, its just showing htc and its been like 4 mins now
Click to expand...
Click to collapse
No it's not normal. Might have to erase the cache "fastboot erase cache" see if that works
via CMD?
mikey0105 said:
via CMD?
Click to expand...
Click to collapse
Yep via cmd.
heres what ive done, erased cache via cmd >> did the instruction you've given me, then reboot, but still, its just showing the htc logo
mikey0105 said:
heres what ive done, erased cache via cmd >> did the instruction you've given me, then reboot, but still, its just showing the htc logo
Click to expand...
Click to collapse
Instructions:
1 - Enter this command: fastboot erase cache
2 - Flash the boot.img on fastboot with: fastboot flash boot boot—rX.img (replace X by the release number)
3 - Reboot to recovery from the fastboot menu (before booting to system for the first time) and flash the modules package
Those are the instructions from the franco kernel thread..
You should follow those instructions.
i did but its not working now.. im stuck with HTC loading screen
mikey0105 said:
i did but its not working now.. im stuck with HTC loading screen
Click to expand...
Click to collapse
Go and start from scratch is your best bet.
Hello, how can i boot in recovery without hardware buttons they are broken? and another thing i dont have any rom instaled, the phone i s-off with 4ext touch recovery. please help. THX:crying:
turn on the phone (u should just get stuck at white htc splash screen) then plug in to pc and open command window and type
adb devices
if ur device shows up then type
adb reboot recovery
it doesn¨t work when i turn on the phone i get to fastboot or hboot...?
capone5 said:
it doesn¨t work when i turn on the phone i get to fastboot or hboot...?
Click to expand...
Click to collapse
oh rite, thats a balls. Dont think theres any other way. Try taking the phone apart and cleaning the buttons. ul be surprised at the dust there. Hopefully that will work. If it dont then the only other way is to flash an ruu via bootloader. What does ur phone say in bootloader?
capone5 said:
it doesn¨t work when i turn on the phone i get to fastboot or hboot...?
Click to expand...
Click to collapse
Did you try running the adb commands that jmcclue listed above while in hboot?
Maybe try running fastboot commands such as "fastboot devices" to see if its recognized.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Try "fastboot devices"
capone5 said:
http://img40.imageshack.us/img40/3765/desireintrouble.jpg[/IMG ]i have install adb and when start the process i cant find device as you can see from the picture...i get in fastboot and hboot menu but i cant navigate any futher, is there a way to flash rom threw windows beyond recovery? because i do a full wipe and i dont have any rom instaled on my precious desire :(...[/QUOTE]
Hi Capone5,
One way to do it, is by downloading a recovery img ([url]http://forum.xda-developers.com/showthread.php?t=1791371[/url] or [url]http://forum.xda-developers.com/showthread.php?t=1474327[/url]) unzip and put it in the fasboot folder, plug phone in fastboot mode and type 'fastboot boot [filename].img'
Hope this helps
Click to expand...
Click to collapse
here are the pictures...when i turn on the phone it immediately go on this screen http://img708.imageshack.us/img708/9121/img20130602212615.jpg and when i try fastboot devices in cmd
capone5 said:
here are the pictures...when i turn on the phone it immediately go on this screen http://img708.imageshack.us/img708/9121/img20130602212615.jpg and when i try fastboot devices in cmd
Click to expand...
Click to collapse
You dont do "adb fastboot devices". You do "fastboot devices"
adb only works when phone is booted or stuck at boot animation, thats why i said try turning on phone then try adb while it bootloops r stuck at splash screen but his phone boots straight into bootloader. Also there is no command for fastboot to reboot recovery. Personally i would take phone apart and clean buttons, worth a shot.
@ op what boes it say in ur bootloader ?
jmcclue said:
adb only works when phone is booted or stuck at boot animation, thats why i said try turning on phone then try adb while it bootloops r stuck at splash screen but his phone boots straight into bootloader. Also there is no command for fastboot to reboot recovery. Personally i would take phone apart and clean buttons, worth a shot.
@ op what boes it say in ur bootloader ?
Click to expand...
Click to collapse
Would fastboot work without selecting it in hboot? If fastboot is able to detect the phone, then he can use "fastboot boot recovery.img" to boot into a touch based recovery like 4ext (without actually flashing it).
Heres his bootloader:
this i get when just trying fastboot devices
jmcclue said:
adb only works when phone is booted or stuck at boot animation, thats why i said try turning on phone then try adb while it bootloops r stuck at splash screen but his phone boots straight into bootloader. Also there is no command for fastboot to reboot recovery. Personally i would take phone apart and clean buttons, worth a shot.
@ op what boes it say in ur bootloader ?
Click to expand...
Click to collapse
the buttons of volume are broken and i try everything to just press - and nothing hapened...how can i load a new recovery threw fastboot?
Check your android-sdk/platform-tools/ directory to make sure the fastboot.exe is there.
If its not there, redownload the sdk and setup adb/fastboot using this guide. Also make sure you install these fastboot drivers
Then try "fastboot devices" again and hope that the phone shows up. If it does you can boot a recovery by doing this:
-Download the 4ext recovery img from here
-Extract the zip and put the recovery img in your android-sdk/platform-tools/ directory
-Run "fastboot boot recovery.img"
If its not showing up in fastboot im not really sure that you have any options, other than to do what jmcclue suggested.
capone5 said:
this i get when just trying fastboot devices
Click to expand...
Click to collapse
have u got the fastboot drivers installed on ur computer?
follow this guide to install them. u cant use fastboot unless u do.
ADB & Fastboot
chromium96 said:
Check your android-sdk/platform-tools/ directory to make sure the fastboot.exe is there.
If its not there, redownload the sdk and setup adb/fastboot using this guide. Also make sure you install these fastboot drivers
Then try "fastboot devices" again and hope that the phone shows up. If it does you can boot a recovery by doing this:
-Download the 4ext recovery img from here
-Extract the zip and put the recovery img in your android-sdk/platform-tools/ directory
-Run "fastboot boot recovery.img"
If its not showing up in fastboot im not really sure that you have any options, other than to do what jmcclue suggested.
Click to expand...
Click to collapse
i just put recovery.img in android sdk/tools folder then ran the command fastboot boot recovery.img
and guess what? im in recovery. Nice 1 chromium, it works
heres a pic
jmcclue said:
i just put recovery.img in android sdk/tools folder then ran the command fastboot boot recovery.img
and guess what? im in recovery. Nice 1 chromium, it works
Click to expand...
Click to collapse
Yep it works. Im trying to compile TWRP for the desire, so i use that command to temporarily test it rather than actually flashing it.
chromium96 said:
Yep it works. Im trying to compile TWRP for the desire, so i use that command to temporarily test it rather than actually flashing it.
Click to expand...
Click to collapse
its handy to know coz im pretty sure hardly anyone knows that and i bet u cant find it on the old interweb lol
So today I had a problem with an app not opening correctly so I rebooted the device. The device was stuck in the kit kat boot sequence. I turned it off and charged it. Tried booting to no avail. So I go into stock recovery mode and wiped cache and then proceeded to wipe/factory reset. It then got stuck on factory reset. I let it sit there on the charger for awhile and it was still stuck on factory reset. So i rebooted to attempt again. Now it won't even go into recovery mode. It'll boot to the fastboot screen but when trying to go into recovery it gets stuck on the white Google logo. Is there anything I can do or do I need to send it back? I bought it in July-ish so it should still be on warranty.
It should be easy to restore the stock ROM. Do you have the device drivers installed and a copy of fastboot?
http://developer.android.com/sdk/win-usb.html
http://www.xda-developers.com/andro...ng-fast-adb-fastboot-and-driver-installation/
Boot your Nexus 7 to the fastboot screen, then connect it to your PC. Open a command prompt window with administrator privileges, cd to the fastboot directory (let me know if you need help here), then type the following commands:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
This will wipe everything on your Nexus 7, preparing it for a full flash of the stock recovery and ROM. You can download the stock ROM from here, and there's a "flash-all.bat" file inside that will restore recovery and the ROM all by itself.
https://developers.google.com/android/nexus/images#razor
Pandae said:
It should be easy to restore the stock ROM. Do you have the device drivers installed and a copy of fastboot?
http://developer.android.com/sdk/win-usb.html
http://www.xda-developers.com/andro...ng-fast-adb-fastboot-and-driver-installation/
Boot your Nexus 7 to the fastboot screen, then connect it to your PC. Open a command prompt window with administrator privileges, cd to the fastboot directory (let me know if you need help here), then type the following commands:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
This will wipe everything on your Nexus 7, preparing it for a full flash of the stock recovery and ROM. You can download the stock ROM from here, and there's a "flash-all.bat" file inside that will restore recovery and the ROM all by itself.
https://developers.google.com/android/nexus/images#razor
Click to expand...
Click to collapse
when trying any commands in adb it says waiting for device and hangs on that.
Use adb if your tablet is booted into Android, and use fastboot if you're only at the bootloader.
Do you have the drivers installed? At a command prompt (again must be administrator permissions), type "fastboot devices" and see if it gives a response.
Pandae said:
Use adb if your tablet is booted into Android, and use fastboot if you're only at the bootloader.
Do you have the drivers installed? At a command prompt (again must be administrator permissions), type "fastboot devices" and see if it gives a response.
Click to expand...
Click to collapse
fastboot devices does nothing. I am in the fastboot directory. I thought I had the drivers installed, but in device manager it shows up as Android with an exclamation mark
OK, that explains it. Delete the driver by hitting Del, and just to be safe, click "View" at the top, then select to show hidden devices. Delete anything else that might be for any Android devices. Then install the drivers I linked to. They're generic drivers that work with either Nexus 7 generation, plus other Nexus devices.
Pandae said:
OK, that explains it. Delete the driver by hitting Del, and just to be safe, click "View" at the top, then select to show hidden devices. Delete anything else that might be for any Android devices. Then install the drivers I linked to. They're generic drivers that work with either Nexus 7 generation, plus other Nexus devices.
Click to expand...
Click to collapse
ok done now fastboot devices shows something, typed in fastboot erase boot and it says erasing boot...seems like it is stuck on this command
wildside84 said:
ok done now fastboot devices shows something, typed in fastboot erase boot and it says erasing boot...seems like it is stuck on this command
Click to expand...
Click to collapse
Couldn't you just try to boot a recovery IMG?
fastboot boot recovery path/to/recovery.img
That will let you run recovery without flashing it
Sent from my Nexus 7 using Tapatalk 4 Pro
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Erasing boot shouldn't take too long. Hopefully the partition isn't damaged.
SwoRNLeaDejZ, I believe he couldn't get into recovery. For problems like this, I like to erase recovery and everything else anyway, especially since flash-all.bat will restore stock recovery as part of the process.
Pandae said:
Erasing boot shouldn't take too long. Hopefully the partition isn't damaged.
SwoRNLeaDejZ, I believe he couldn't get into recovery. For problems like this, I like to erase recovery and everything else anyway, especially since flash-all.bat will restore stock recovery as part of the process.
Click to expand...
Click to collapse
no commands work. on erase recovery command it says failed command write failed invalid argument
edit: fastboot boot recovery fails also "command write failed unknown error"
edit: i get a lot of fastboot.exe has stopped working errors on windows. redownloaded platform tools and still happens. I'm at a loss I guess I have to get Google to replace it entirely
I may have taken something for granted. Did you unlock the bootloader?
fastboot oem unlock
Pandae said:
I may have taken something for granted. Did you unlock the bootloader?
fastboot oem unlock
Click to expand...
Click to collapse
no and whats funny is I just got done trying that before i read your message. i restarted the device and my computer and just decided to see if it would dirty flash the flash-all.bat and it was actually going through not giving the write errors but did say bootloader is locked. so i typed fastboot oem unlock and the screen popped up on the device to say yes or no. i selected yes and it, again, got stuck for 10-15 minutes on erasing data...rebooted the device, unlock appears to have failed. argh
If you power down and reboot back into the bootloader, it still says unlocked? What if you try unlocking again?
Pandae said:
If you power down and reboot back into the bootloader, it still says unlocked? What if you try unlocking again?
Click to expand...
Click to collapse
it says the bootloader is locked. i am trying again right now. i get to the yes no screen, select yes and on the command prompt it is stuck on erasing userdata
I've never seen it take very long. Let it sit for a while, maybe plug it in and just wait?
Pandae said:
I've never seen it take very long. Let it sit for a while, maybe plug it in and just wait?
Click to expand...
Click to collapse
ill let it sit, but i think there is something wrong with the device. i had a similar prob with a gs2 and it wouldnt erase or write anything to partition. would usb debugging have to have already been enabled? i cant remember if that was checked or not. or does that matter?
USB debugging is necessary for connecting once the tablet has booted into Android, but it isn't needed for fastboot and the bootloader level. At this point I fear there's more corruption than can be fixed, but let's wait a little while and see.
Pandae said:
USB debugging is necessary for connecting once the tablet has booted into Android, but it isn't needed for fastboot and the bootloader level. At this point I fear there's more corruption than can be fixed, but let's wait a little while and see.
Click to expand...
Click to collapse
Just received an email from Google support. They are unwilling to help because I purchased the device from Best Buy rather than Google Play...WTH? Best Buy won't help either I won't even bother. At this point I'll have to hope Asus will take it in for repair. That kind of bummed me out about Google. Not sure if I want to buy another nexus device again now.
wildside84 said:
no commands work. on erase recovery command it says failed command write failed invalid argument
edit: fastboot boot recovery fails also "command write failed unknown error"
edit: i get a lot of fastboot.exe has stopped working errors on windows. redownloaded platform tools and still happens. I'm at a loss I guess I have to get Google to replace it entirely
Click to expand...
Click to collapse
use usb jig and flash via odin nice work :good:
wildside84 said:
Just received an email from Google support. They are unwilling to help because I purchased the device from Best Buy rather than Google Play...WTH? Best Buy won't help either I won't even bother. At this point I'll have to hope Asus will take it in for repair. That kind of bummed me out about Google. Not sure if I want to buy another nexus device again now.
Click to expand...
Click to collapse
Is Google writing the book "How Not to Stand Behind Your Product"? Sheesh!
Sorry I couldn't be of more help. Good luck and speedy repairs to you. I must admit that with the touchscreen problems, and that it took someone who isn't a Google employee to fix it for a lot of people, all while Google is still silent, I myself don't care to buy another product by Google and/or Asus.
---------- Post added at 12:24 AM ---------- Previous post was at 12:18 AM ----------
VerlyAnanda said:
use usb jig and flash via odin nice work :good:
Click to expand...
Click to collapse
Odin is for Samsung devices, unless something's happened I didn't hear about.
Hi,
I got a little bit of a problem on my head.... I planned to flash CM12.1 on my HOX but i flashed a different boot.img by mistake! Now i cant get the phone into debugging mode and while using hasoonss toolkit it wont see my device cause i cant get it into debugging mode . Any ideas on how to solve the problem? There are a lot of threads inhere about bricked hox but i cant find one talking about the same problem....
Hope i can get some help on this.
Ow and a bit more info, i can get into bootloader and recovery.
go_insane1981 said:
Ow and a bit more info, i can get into bootloader and recovery.
Click to expand...
Click to collapse
if you can get into bootloader then just get the good boot.img and flash it using fastboot flash boot boot.img
Tried that but it won't see my device.
It doesn't apear in my devices.
go_insane1981 said:
It doesn't apear in my devices.
Click to expand...
Click to collapse
When on bootloader/fastboot mode, type
fastboot devices
to check connection
if it returns your device serial no, then it is good for you to
fastboot flash boot boot.img
adb devices is working when in recovery or on running OS, not on bootloader/fastboot
ckpv5 said:
When on bootloader/fastboot mode, type
fastboot devices
to check connection
if it returns your device serial no, then it is good for you to
fastboot flash boot boot.img
adb devices is working when in recovery or on running OS, not on bootloader/fastboot
Click to expand...
Click to collapse
Tried both ways again but no reaction wth a list of devices. It's blank...
install htc drivers http://www.mediafire.com/?eqrqb44r3ot18g1
SÜPERUSER said:
install htc drivers http://www.mediafire.com/?eqrqb44r3ot18g1
Click to expand...
Click to collapse
Any options on how to install the drivers different from normally? Apparently the drivers won't install as it should install...
Have HTC sync on my system, can i use some of those exe's in there?
This is wat happens with HTC installer.
go_insane1981 said:
This is wat happens with HTC installer.
Click to expand...
Click to collapse
You have a newer sets of drivers installed and the installer exits instead of downgrade the version.
Are you sure you are in fastboot mode?
To enter this.
Power off your phone.
Hold Power and volume down button until phone enters a white screen with Hboot written on it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now press power button again. The screen should now change to this
Showing fastboot marked in red.
Go to device manager and look for the driver. It should look like this ( Android USB Devices, My HTC)
In cmd type fastboot devices.
My cmd returns this.
Cant seem to get the drivers in my device manager, they are installed but not showing in my device manager...
SÜPERUSER said:
You have a newer sets of drivers installed and the installer exits instead of downgrade the version.
Are you sure you are in fastboot mode?
To enter this.
Power off your phone.
Hold Power and volume down button until phone enters a white screen with Hboot written on it.
Now press power button again. The screen should now change to this
Showing fastboot marked in red.
Go to device manager and look for the driver. It should look like this ( Android USB Devices, My HTC)
In cmd type fastboot devices.
My cmd returns this.
Click to expand...
Click to collapse
Ok i used a old htc and now it sees my device again.
Device manager sees the HOX now too.
go_insane1981 said:
Device manager sees the HOX now too.
Click to expand...
Click to collapse
It was my thought at first. So now we know that htc apparently dropped the support for one x and older devices in their driver pack. Good to know
Now i need to take a look at how i can push a diff rom in there since the other rom apparently wont work..
go_insane1981 said:
Now i need to take a look at how i can push a diff rom in there since the other rom apparently wont work..
Click to expand...
Click to collapse
What rom are you trying to install?
SÜPERUSER said:
What rom are you trying to install?
Click to expand...
Click to collapse
http://forum.xda-developers.com/htc-one-x/development/rom-cyanogenmod-12-1-t3396521
go_insane1981 said:
http://forum.xda-developers.com/htc-one-x/development/rom-cyanogenmod-12-1-t3396521
Click to expand...
Click to collapse
Have you flashed this "new storage layout"?
http://forum.xda-developers.com/htc-one-x/orig-development/storage-layout-hox-endeavoru-t3022358
SÜPERUSER said:
Have you flashed this "new storage layout"?
http://forum.xda-developers.com/htc-one-x/orig-development/storage-layout-hox-endeavoru-t3022358
Click to expand...
Click to collapse
Making a new layout is something i missed, Mone said ;
Flashing instruction like usual: perform a full wipe with TWRP for new layout, flash the ROM, flash the suggested GApps, reboot into fastboot mode, flash the boot.img exctracted from the ROM.zip, reboot into system, enjoy cm-12.1.
So i wiped the damn thing( ) after making a backup offcourse(which btw doesn't help cuz its screwed...). But i completely missed that i had to make a new layout... But stil i am convinced it can be "unbricked" one way or another.
I basicly follwed all the steps mentioned in this thread; http://forum.xda-developers.com/showthread.php?t=2069904 and it al worked up to the point i flashed the wrong kernel. After that i searched the forum for hours and found some things which could be connected but with a total different view of what my problem is/was(partially solved with your help) and ended up with putting a SOS sign up for help.
Does anyone have the MSMTOOL for LE2120? bricked my phone when trying to patch the boot.img to magisk version...
Now totally stuck... even adb commands to restore does not work...
danjcxie said:
Does anyone have the MSMTOOL for LE2120? bricked my phone when trying to patch the boot.img to magisk version...
Now totally stuck... even adb commands to restore does not work...
Click to expand...
Click to collapse
What did you do to try to patch it? Why are you in adb? Does fastboot work?
craznazn said:
What did you do to try to patch it? Why are you in adb? Does fastboot work?
Click to expand...
Click to collapse
Patched the boot.img using magisk and then flashed it. After patching, it totally cant boot and can only boot to bootloader.
tried alot of version of MSMtool and it will always fail with param preload error...
Then tried manually recover via extracting the payload using python then using adbtools to wipe and flash but it will also fail because some img files are unable to flash over to the phone...
Any other solutions?
U not able to flash boot the stock boot.img?
i am able to flash the stock boot.img to the phone but some critical img files will come out with
FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
You need to be in fastbootd,
Code:
fastboot reboot fastboot
craznazn said:
You need to be in fastbootd,
Code:
fastboot reboot fastbootd
Click to expand...
Click to collapse
Nope not working too...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
danjcxie said:
Nope not working too...
View attachment 5281163
Click to expand...
Click to collapse
Sorry, fastboot reboot fastboot (without the d)
@danjcxie
To be honest, I would download the rom and boot with the recovery image instead, I'll upload the image collection...
Will post a link here once it's up.
Actually, just noticed there isn't a recovery image, so boot to the default boot.img using fastboot, then see if the storage shows on your computer, copy the latest default rom over to the main storage folder then then go into Settings > System > System Updates and use the cog to do a local update using the rom zip.
That should re-install everything back to default, you might get lucky and still have all your data
My collection is for the Europe build FYI:
OP9P_Image_Collection_BA_11.2.3.3.zip | by djsubterrain for OnePlus 9 Pro
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
MD5 : 00227014483b4913a2624fac6f492434
So you would reboot the phone into fastboot mode by holding vol up during boot
Once you are in fastboot mode connect the phone to your computer
Test that the computer can see it properly using fastboot devices
You should see a number returned, if so then your computer is recognising the phone, if you don't then try installing the latest drivers from here
If fastboot can see the device properly then copy the default boot.img to the same folder as your fastboot.exe and type the following :
fastboot boot boot.img
You should see a message saying it's transferring it to the phone, then it should boot the phone using it, it's slower than a normal boot but, if everything else on the phone is ok, then you should see it booted and it should accept your lock method
Once you get into the phone using that boot.img, try connecting the phone to your computer and see if it's recognised, if it is then copy over the latest stock rom to your main storage folder, then go to Settings > System > System Updates and use the cog to do a local update using the rom zip
I'm guessing it should let you because it will see a difference between your boot image and the one from the rom.
MSM tool for LE2125 - 11.2.2.2.LE15AA
User Type of Others for login MSM Tool for LE2125 - 11.2.2.2.LE15AA Drivers Mirrors: (provided by @djsubterrain) MSM Tool : https://sourceforge.net/projects/djsubterrain/files/OnePlus 9 Pro/OP9P_MSM_Tool.zip/download MD5 ...
forum.xda-developers.com
New problem... After i did fastboot reboot fastboot, it shows low battery whole day and is unable to charge totally... it has been charging the whole day now and totally cant turn on at all.
it keeps showing the lightning sign in the centre of the circle keeps blinking and dies off
danjcxie said:
New problem... After i did fastboot reboot fastboot, it shows low battery whole day and is unable to charge totally... it has been charging the whole day now and totally cant turn on at all.
it keeps showing the lightning sign in the centre of the circle keeps blinking and dies off
View attachment 5281971
Click to expand...
Click to collapse
Turn it off and try charging it
Also "fastboot reboot fastboot" isn't a valid command, there is an adb command "adb reboot bootloader" but that can only be run from within your rom from when you are in recovery with the phone connected
See here :
Fastboot Commands: A Beginner’s Guide
With this guide of ours, you'll be able to learn all the fastboot commands and their syntax. We've also posted some hidden commands which you never knew.
android.tutorials.how
#To reboot your device
fastboot reboot
#To reboot your device to fastboot mode
fastboot reboot-bootloader
Click to expand...
Click to collapse
djsubterrain said:
Turn it off and try charging it
Click to expand...
Click to collapse
Yup tried. Everytime you just plug in the charging cable, it will just auto boot up and show the charging sign
danjcxie said:
Yup tried. Everytime you just plug in the charging cable, it will just auto boot up and show the charging sign
Click to expand...
Click to collapse
Yeah that symbol isn't what I get, I get a blue lightning sign with the percentage underneath. Are you running OxygenOS or ColorOS?
I think it might be time for you to contact OnePlus support
djsubterrain said:
Turn it off and try charging it
Also "fastboot reboot fastboot" isn't a valid command, there is an adb command "adb reboot bootloader" but that can only be run from within your rom from when you are in recovery with the phone connected
See here :
Fastboot Commands: A Beginner’s Guide
With this guide of ours, you'll be able to learn all the fastboot commands and their syntax. We've also posted some hidden commands which you never knew.
android.tutorials.how
Click to expand...
Click to collapse
Wtf are you talking about. fastboot reboot fastboot is literally the only way to get into fastbootd if you can't get to recovery or boot normally.
Regarding battery, that I'm not sure, hopefully someone can help
craznazn said:
OP
Wtf are you talking about. fastboot reboot fastboot is literally the only way to get into fastbootd if you can't get to recovery or boot normally.
Regarding battery, that I'm not sure, hopefully someone can help
Click to expand...
Click to collapse
OK, firstly, who the hell do you think you're talking to?
Secondly, did you look at the link I posted?
djsubterrain said:
OK, firstly, who the hell do you think you're talking to?
Secondly, did you look at the link I posted?
Click to expand...
Click to collapse
Who the hell are you? Why the hell are you linking "tutorials.how"?
fastboot/fastboot.cpp - platform/system/core - Git at Google
android.googlesource.com
Lines 2178, source tells you to reboot fastbootd by reboot fastboot.
Show me it's not a valid command, go on
craznazn said:
Who the hell are you? Why the hell are you linking "tutorials.how"?
fastboot/fastboot.cpp - platform/system/core - Git at Google
android.googlesource.com
Lines 2178, source tells you to reboot fastbootd by reboot fastboot.
Show me it's not a valid command, go on
Click to expand...
Click to collapse
Go ahead and help the guy solve his problem.
Just remember it's fastboot, not fastbootd.
Now, how do you block people on here again?
danjcxie said:
Does anyone have the MSMTOOL for LE2120? bricked my phone when trying to patch the boot.img to magisk version...
Now totally stuck... even adb commands to restore does not work...
Click to expand...
Click to collapse
use the MSM Tool with the latest drivers
QDLoader HS-USB Driver_64bit_Setup
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
danjcxie said:
Does anyone have the MSMTOOL for LE2120? bricked my phone when trying to patch the boot.img to magisk version...
Now totally stuck... even adb commands to restore does not work...
Click to expand...
Click to collapse
This just worked for me minutes ago
OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)
By using these tools, you accept full responsibility for your actions. Your warranty is void should you run any of these utilities without OnePlus support present. I am not responsible for bricks, fires, nuclear war, etc. If you modified any...
forum.xda-developers.com
i downloaded Indian Variant LE2121 while my phone is LE2120 ant it worked