After rooting and unlocking my device and installing custom rom via fastboot commands cos couldn't s off , ADB wasn't seeing my device but after trying this http://forum.xda-developers.com/showthread.php?t=2091922 it worked and was then able to s off
Seen a lot of people having this problem so thought I would post this so it may help others !
Related
I am trying to use 'adb' from the android dev kit but I cannot see the devices, i.e. 'adb devices' doesn't report any devices. It appeared to be working earlier this evening but not any more. I was going to push a rom file to my rooted phone but obviously since I no longer see the device I am stuck. I rooted yesterday and installed the maximus rom but my phone went into a loop of restarting. Unfortunately I didn't backup before I rooted and installed Maximus rom.
Can anybody offer any help? I am using Mac OSX.
Desperate since phone is now effectively redundant
adiemask said:
I am trying to use 'adb' from the android dev kit but I cannot see the devices, i.e. 'adb devices' doesn't report any devices. It appeared to be working earlier this evening but not any more. I was going to push a rom file to my rooted phone but obviously since I no longer see the device I am stuck. I rooted yesterday and installed the maximus rom but my phone went into a loop of restarting. Unfortunately I didn't backup before I rooted and installed Maximus rom.
Can anybody offer any help? I am using Mac OSX.
Desperate since phone is now effectively redundant
Click to expand...
Click to collapse
try this: http://forum.xda-developers.com/showthread.php?t=1706918
if it didnt help u just reply and we´re gonna look whats next to unbrick ur phone
Hi
Thanks for your reply, I have hit the 'Thanks' button
I read the posting you referenced but it doesn't really offer a solution to my problem.
As described earlier I rooted my phone and flashed a Rom (Maximus) succesfully but on turning the phone on after installing the new Rom I got into a cycle of the phone rebooting without actually getting past the lock screen. My thoughts at that stage were to re flash using stock rom but on running fastboot and plugging into my Mac OSX machine via USB, the phone doesn't show up in 'devices' on the Mac. I have also tried 'adb devices' form within Android Dev Tools and although 'adb' runs fine no device is reported. Of course without devices being avaialble to 'adb' then I cannot reflash!
I have also tried from within a bootcamp installation of 'Windows XP' installed on the mac with the same results, this with 'HTC Sync' installed and therefore providing the USB Drivers required within Windows.
I have tried logging into fastboot using 'power' and 'Down Volume' at various stages of the boot process on the phone but have never seen the phone within devices.
Clearly prior to installation of the Rom (Maximus) I could see devices at both the Finder window on the Mac and from adb devices.
Any help or insight you could provide would be very gratefully received
Ok ok ok dont worry
I had to read a bit and found quit much german threads where they flash back the stock rom
as is suggested u cant flash it with odin...
the only solution i woul suggest is that u have to find a computer running windows
there its very easy to restore the stock with the methods u described earlier in the thread...
hope u get done let me know what happend
=)
The question remains; how can I flash anything be it a hacked rom or an official rom when I cant see the 'device' in both windows and mac osx?
I think what I am looking for is a reason why the phone isn't seen when plugging in via USB. Once it is seen as a 'device' I will be able to flash anything via 'adb'.
Thank you for your continued interest and assistance
ok so u know how the get it back but ur phone is not really recognized by ur computer
but i found a method using the bootloader
the problem is that the instructions are in german
but i think if u google a bit u may find it
Don't know if I misunderstood what you said..but to get into recovery, you hold volume down and the power button when the phone is turned off. Not during the boot process.
Yes you can do it with bootloader (power+volume down)
Sent from my HTC Salsa C510e using xda premium
moksha098 said:
Yes you can do it with bootloader (power+volume down)
Sent from my HTC Salsa C510e using xda premium
Click to expand...
Click to collapse
Yes, I know that. He said he attempted to do that DURING the boot process. I was stating that he had to do it while the phone was powered down.
Guys, I can get into recovery no problem. The issue is that my phone doesn't show up in devices on the mac finder window and hence when I run 'ADB Devices' from the mac when the phone is plugged into the mac with USB no device is found and so no serial number is reported in my terminal window on the mac. If I can get to see the device with 'ADB' I can push the rom and recover the phone. At the moment the phone is bricked.
Thanks guys for your continued assistance.
adiemask said:
Guys, I can get into recovery no problem. The issue is that my phone doesn't show up in devices on the mac finder window and hence when I run 'ADB Devices' from the mac when the phone is plugged into the mac with USB no device is found and so no serial number is reported in my terminal window on the mac. If I can get to see the device with 'ADB' I can push the rom and recover the phone. At the moment the phone is bricked.
Thanks guys for your continued assistance.
Click to expand...
Click to collapse
But if this doenst work why dont u try the method with the recovery mode or the bootloader i suggested
Hi, i'm starting this thread by excusing myself for this approximativly english, i'm not really an english man :angel:
I don't really like calling help on forum, but at 00:30, with studies tomorrow, i'm really bored.
So, today at 17:30, i have reboot my OPX, simply reboot, and i'm now on a bootloop... I read a looooooot of thing on internet and i deduce that : My bootloader has relocked himself.
Before this reboot, i was on OxygenOS 3.* with TWRPblu****** and an unlocked bootloader. I can't access to recovery, only to a bootloop or fastboot mode.
I've tried :
- Use fastboot commands to flash recoveries, but nothing happen because i can't unlock the bootloader
- Use the MSMdowloadtool like all guide said, but the problem is there i think. My device aren't recognize as a "Qualcomm ***********" is recognize as "Android" or "One plus bootloader device" (i haven't exact name here). I thinked Windows 10 have the faculty to identify android devices, so i've installed on dual boot windows 7, no more results. (Signed Drivers are disabled)
I have no idea, i need u :crying:
If anyone have ever see the same issue, give me ur solution please
I certainly will contact the OnePlusSupport too but i know it's not really a good idea.
I will go to sleep now, i need to go to school tomor... today.
Have a good night !
Nekkoelb said:
Hi, i'm starting this thread by excusing myself for this approximativly english, i'm not really an english man :angel:
I don't really like calling help on forum, but at 00:30, with studies tomorrow, i'm really bored.
So, today at 17:30, i have reboot my OPX, simply reboot, and i'm now on a bootloop... I read a looooooot of thing on internet and i deduce that : My bootloader has relocked himself.
Before this reboot, i was on OxygenOS 3.* with TWRPblu****** and an unlocked bootloader. I can't access to recovery, only to a bootloop or fastboot mode.
I've tried :
- Use fastboot commands to flash recoveries, but nothing happen because i can't unlock the bootloader
- Use the MSMdowloadtool like all guide said, but the problem is there i think. My device aren't recognize as a "Qualcomm ***********" is recognize as "Android" or "One plus bootloader device" (i haven't exact name here). I thinked Windows 10 have the faculty to identify android devices, so i've installed on dual boot windows 7, no more results. (Signed Drivers are disabled)
I have no idea, i need u :crying:
If anyone have ever see the same issue, give me ur solution please
I certainly will contact the OnePlusSupport too but i know it's not really a good idea.
I will go to sleep now, i need to go to school tomor... today.
Have a good night !
Click to expand...
Click to collapse
Fastboot commands : is the phone recognised?
"fastboot oem device-info" output?
Did you tried the Mega unbricked guide?
Which step precisely is a problem?
Kéno40 said:
Fastboot commands : is the phone recognised?
"fastboot oem device-info" output?
Did you tried the Mega unbricked guide?
Which step precisely is a problem?
Click to expand...
Click to collapse
Yes he used..read full op.
Nekkoelb said:
Hi, i'm starting this thread by excusing myself for this approximativly english, i'm not really an english man :angel:
I don't really like calling help on forum, but at 00:30, with studies tomorrow, i'm really bored.
So, today at 17:30, i have reboot my OPX, simply reboot, and i'm now on a bootloop... I read a looooooot of thing on internet and i deduce that : My bootloader has relocked himself.
Before this reboot, i was on OxygenOS 3.* with TWRPblu****** and an unlocked bootloader. I can't access to recovery, only to a bootloop or fastboot mode.
I've tried :
- Use fastboot commands to flash recoveries, but nothing happen because i can't unlock the bootloader
- Use the MSMdowloadtool like all guide said, but the problem is there i think. My device aren't recognize as a "Qualcomm ***********" is recognize as "Android" or "One plus bootloader device" (i haven't exact name here). I thinked Windows 10 have the faculty to identify android devices, so i've installed on dual boot windows 7, no more results. (Signed Drivers are disabled)
I have no idea, i need u :crying:
If anyone have ever see the same issue, give me ur solution please
I certainly will contact the OnePlusSupport too but i know it's not really a good idea.
I will go to sleep now, i need to go to school tomor... today.
Have a good night !
Click to expand...
Click to collapse
Power off your phone, connect to PC with power off holding volume up button. It should detect phone as Qualcomm.
Nekkoelb said:
Hi, i'm starting this thread by excusing myself for this approximativly english, i'm not really an english man :angel:
I don't really like calling help on forum, but at 00:30, with studies tomorrow, i'm really bored.
So, today at 17:30, i have reboot my OPX, simply reboot, and i'm now on a bootloop... I read a looooooot of thing on internet and i deduce that : My bootloader has relocked himself.
Before this reboot, i was on OxygenOS 3.* with TWRPblu****** and an unlocked bootloader. I can't access to recovery, only to a bootloop or fastboot mode.
I've tried :
- Use fastboot commands to flash recoveries, but nothing happen because i can't unlock the bootloader
- Use the MSMdowloadtool like all guide said, but the problem is there i think. My device aren't recognize as a "Qualcomm ***********" is recognize as "Android" or "One plus bootloader device" (i haven't exact name here). I thinked Windows 10 have the faculty to identify android devices, so i've installed on dual boot windows 7, no more results. (Signed Drivers are disabled)
I have no idea, i need u :crying:
If anyone have ever see the same issue, give me ur solution please
I certainly will contact the OnePlusSupport too but i know it's not really a good idea.
I will go to sleep now, i need to go to school tomor... today.
Have a good night !
Click to expand...
Click to collapse
You have noting to do but to flash stock oos 2.1.4 using Qualcomm flasher and driver.I faced the same issue.but I managed to flash using Qualcomm in windows 10.and got my onyx back.
My suggesting is remove the adv or oneplus drivers.just install the Qualcomm driver and connect the device.follow the device manager if the deivce detected or not.it will detect and flash using Qualcomm flasher.
Well out of all the years I have bought,rooted and modded android devices I have never asked a help question here on xda. I tried everything first and usually that led me to where I wanted to be. Well Alcatel has made it nearly impossible for me to get much further without seeking out those who may know more. So here's the dilemma. I own the Alcatel A621BL also known as the One Touch Pixi Glory. I can not gain access to fastboot using adb nor button combos on this device. Button Combos that are common just cause device to reboot. ADB commands for rebooting to bootloader cause nothing more than a device reboot. Using fastboot and its commands just give a waiting for devices message and that's it. I have correct drivers installed on PC. adb detects device fine but cant reboot to fastboot. Cant figure out a workable root method on the device without access to bootloader. Because this device checks for changes upon reboot and just deletes them after using apps like kingroot,etc. Can not edit the boot image and flash it or anything else without access to fastboot. In developer options there is the option to oem inlock but ticking it on or rather allowing unlock seems to make no difference. I did speak with others who suggest the MSM8909 chipset may be the reason for lack of fastboot access. Seems Alcatel is going in a direction which will cause them to lose some sales due to this policy. Anyone got any suggestions,ideas or anything else on this issue?
I've got the 5041 Tetra which run on a mediatek chipset and have used fastboot on several msm8909 devices. My Tetra's fastboot was locked down via ota update. I believe it is the phone service providers locking us out.
Not sure if you ever found what you were looking for on this device, but if you are still with it, the AIO thread is the place to start.
I'd like to start off by apologizing for having to waste somebody's time for something I can't find the answer to. I should preface this post by saying that I know nothing about ADB, but in the last couple of days I've done plenty of reading and to be quite honest the more research sometimes adds to the confusion with contrary and outdated information.
I'm basically trying to get TWRP onto my Mi Pad 4 LTE using ADB on my Windows 10 PC coming from the MIUI EU ROM Bootloader unlocked from the supplier. USB debugging enabled drivers installed etc
I had a lot of trouble until I came across this thread http://www.testedtechnology.co.uk/debloating-the-huawei-p30-pro/ because of an error I was getting in the Powershell window.
https://forum.xda-developers.com/attachment.php?attachmentid=4781060&stc=1&d=1561218064
So basically in short, thanks to the above thread I was able to get into fastboot mode having recognized the device using the precursor .\ as shown above, but one of my problems is I'm not sure if I should be use the .\ with all commands? My problem from here now that my device was in fastboot mode I didn't know how to direct it to the file. I just have no idea what commands to you use to find a particular directory to get to recovery-TWRP-3.3.0-0429-XIAOMI_PAD4(PLUS)-CN-wzsx150.
I'm really concerned about putting the device into bootloop as some of the problems I've seen seem almost insurmountable!
Anyway sorry again and TIA for anybody taking the time to help.
All sorted now thanks for all the help.
This Oneplus X seems to be more difficult than my previous attempts for installing TWRP and custom ROM. I keep getting stuck and nothing returning once in fastboot and executing command "fastboot devices". I just keep getting "< waiting for device >" .
I think I have ADB installed right because while the Oneplus X is on and in normal mode (developer settings enabled with OEM unlocking and USB debugging enabled also) ADB connects. The USB drivers look to work fine because I can see the device (including SD card storage) and transfer files. in ADB and typing in ADB devices, I see the device.
When I run adb reboot bootloader and execute fastboot devices using command.com with administrator privilege, it just returns another prompt. It doens't show any device. I get the same results with Powershell with administrator privelge.
I'm already on my 2nd machine trying to do this although it's a windows 10 also just w/o updates for six months (was off and on the side of office). I had the same issues on my newer machine and thought it's the windows 10 machine I'm using. Researching the internet and here, I see others mention it though I didn't see any solution. I don't have a Linux machine (never really used it though had redhat installed eons ago somewhere). I guess I can do a refresh of my 2nd/older machine and not do any updates to see if that may help with any driver conflict though I don't see any indicators since adb can see the device. I thought trying to install TWRP via sideloader may work but I don't see tutorials and commands via that way.
Also I'm using ADB 1.4.3 in the 2nd windows machine. I had the Minimal ADB and Fastboot version on the other machine.
Anything else I can try?
P.S. The Onyx seems to be harder than putting android on my old HP touchpad! Putting a Tmobile rom on a AT&T Galaxy S4 and custom rom on a Oneplus 2 seemed much easier than the Onyx though unsure why. Onyx and the Oneplus 2 were comparable manufacturing years iirc.
On the 2nd machine, i did a windows 10 reset to basically refresh it (like a fresh install). I started over again and managed to get past the fastboot device problem and it's showing it now. I think the prior problem was the device and driver and even with a re-install, can't seem to get past it. The only difference I did with ADB install was not opting to install google drivers.
I got the bootloader unlocked and the recovery.img file done. Basically I'm following the direction from this page - https://www.technobuzz.net/root-oneplus-x-install-twrp-recovery/ - which seems to be aligned with most youtube and I think same as old pages here.
Now where I'm stuck is when executing "fastboot boot recovery.img" I get the failed (remote : dtb not found) and can't seem to find a solution to this one. Some sites say something about the partition?
Thoughts? hopefully this machine is not too old/dead for some comments/guidance unless I'm posting on the wrong section.
well to share back here and for closure.. looks like the recovery image i used on the site above must be for a different OOS. doing some further searches here and different terms and jumping to another thread from a search result thread (lol), i read that i needed a specific twrp for oos 3.1.4. (odd since recovery is supposed to be independent of ROM version, but that seemed to have work). guess persistence pays after all.
it really did heavily matter having the device recognized properly by windows 10. once i got past the blank fastboot device command execution, i got the another issue due to the phone not knowing how to boot into the recovery version i was trying to install, at least that's how another poster in another thread explained it. hence the right twrp had to be used for oos 3.1.4