Hello, folks,
I have a razerphone2 this was rooted for this reason I couldn't install the current update so I reset it but it didn't improve either. I don't have a chance to access the device via ADB/Fastboot and tried it on several computers. Do you have an idea? You can install updates from SD card but the rom from Razer doesn't work. I need help!
Use Razer developers
Phill_ger said:
Hello, folks,
I have a razerphone2 this was rooted for this reason I couldn't install the current update so I reset it but it didn't improve either. I don't have a chance to access the device via ADB/Fastboot and tried it on several computers. Do you have an idea? You can install updates from SD card but the rom from Razer doesn't work. I need help!
Click to expand...
Click to collapse
Hi, The Razer developer page contains instructions for installing ADB Fastboot drivers and recovering the system to its original version.
First need SDK for RP2, ADB Fastboot Drivers.
*Only whit this SDK you can access to bootloader.
I attach the links:
Fastboot drivers -> "https://dl-ssl.google.com/android/repository/latest_usb_driver_windows.zip" *Reboot in fastboot first to recognize in your system, -> "https://s3.amazonaws.com/cheryl-factory-images/How_to_Install_Android_Fastboot_Drivers_on_Windows.pdf"
SDK -> "https://dl.google.com/android/repository/platform-tools-latest-windows.zip"
Link Razer Developers
"https://developer.razer.com/razer-phone-dev-tools/factory-images/"
"https://developer.razer.com/razer-phone-dev-tools/general-instructions/"
Hi,
ist still not working when iin the Android system i can use adb to boot into Bootloader but at this Point i cant connect to the Phone.
Phill_ger said:
Hi,
ist still not working when iin the Android system i can use adb to boot into Bootloader but at this Point i cant connect to the Phone.
Click to expand...
Click to collapse
You should first install drivers for windows like in the page you were linked to above.
Related
this is what i tried to do: wanted to flash a new rom from my original froyo. read through the guide and got it rooted and installed rom manager and in turn installed recovery. booted into recovery and made a backup. tried installing a rom but it wouldnt let me so at the end installed RA recovery instead. i was able to flash a different rom. mpw tried to boot to recovery to get stock rom it display just the android and exlamation mark.
i can get into bootloader but in recovery wont show a thing as if it lost the recovery program.
tried installing sdk but adb wont see the phone.
SDK version 9, windows vista
Any ideas?
You have the stock recovery...
Read the wiki. Follow the guide for unroot/restore, using passimg method and FRG33. Start again rooting (though you probably want to read a bit more first, and make sure you can connect via adb and fastboot BEFORE you mess with stuff)...
Sent from my Nexus One using XDA App
issue is i cant connect through adb or fastboot since i dont have the debug mode before it all went
You don't need adb or fastboot to follow the unroot/restore guide. I was simply suggesting that you make sure it works before you try and root again.
Unroot/restore.
Get adb and fastboot working.
Play with phone.
Sent from my Nexus One using XDA App
how can i get adb/fastboot working. i went through the guide and dozens of other websites.
adb doesnt see a phone connected even though under device manager it shows an android device.
Install the drivers when in fastboot mode, and you'll have fastboot. It's not adb.
fastboot won't help you unless your bootloader is unlocked. adb you won't get, unless you install a ROM and enable debug, or install a custom recovery - which, again, you won't be able to install without unlocked bootloader. adb doesn't work in bootloader mode, you should have found that in at least one of the "dozen guides".
So, you have 2 options:
1) you have unlocked bootloader or you want to unlock bootloader - in that case, enter the bootloader, connect usb, install fastboot drivers, install custom recovery with fastboot.
2) you don't want to unlock bootloader - then follow the correct advice given to you in danger-rat's posts above.
So, you have 2 options:
1) you have unlocked bootloader or you want to unlock bootloader - in that case, enter the bootloader, connect usb, install fastboot drivers, install custom recovery with fastboot.
2) you don't want to unlock bootloader - then follow the correct advice given to you in danger-rat's posts above.[/QUOTE]
ok problem solved and thanks. all along the dll file for fastboot was in platform-tools instead of tool within the sdk hence why fastboot never worked. unlocked the bootloader and recovered my old image. incase anyone else have this issue.
thanks
Ok guys, brand new to forums and brand new to Androids. Bought this phone off someone for cheap, was wondering if I could fix this. Have been googling for the past 4 hours and found some info. Here is what I know about the device.
It was rooted (not sure which rom), the recovery does say unlocked and tampered. I can boot into TWRP recovery. It says no OS. I have SDK Manager and correct updates, USB driver installed, HTC Sync Manager installed. Also have Stock rom for HTC One.
I have tried to use TWRP to load a stock rom using ADB, I can not in any way get it to read the device. On the phone I go into TWRP - > Advanced - ADB Sideload -> Swiped to sideload and it says Starting ADB Sideload feature... then nothing ( I assume that's all it says), I then go into command prompt and go to the proper directory and type ADB Devices (it says List of devices attached and nothing ), I still try to load rom and it says no devices attached.
Now I am completely new to rooting of android devices, I am a little tech savvy tho. But some detailed instructions would help and be most appreciated. Basically I just need help getting PC to read the HTC One, thanks!
skempf85 said:
Ok guys, brand new to forums and brand new to Androids. Bought this phone off someone for cheap, was wondering if I could fix this. Have been googling for the past 4 hours and found some info. Here is what I know about the device.
It was rooted (not sure which rom), the recovery does say unlocked and tampered. I can boot into TWRP recovery. It says no OS. I have SDK Manager and correct updates, USB driver installed, HTC Sync Manager installed. Also have Stock rom for HTC One.
I have tried to use TWRP to load a stock rom using ADB, I can not in any way get it to read the device. On the phone I go into TWRP - > Advanced - ADB Sideload -> Swiped to sideload and it says Starting ADB Sideload feature... then nothing ( I assume that's all it says), I then go into command prompt and go to the proper directory and type ADB Devices (it says List of devices attached and nothing ), I still try to load rom and it says no devices attached.
Now I am completely new to rooting of android devices, I am a little tech savvy tho. But some detailed instructions would help and be most appreciated. Basically I just need help getting PC to read the HTC One, thanks!
Click to expand...
Click to collapse
try this Latest HTC Drivers
if this doesn't get ur device recognized Uninstall the previously installed driver and try this
skempf85 said:
Ok guys, brand new to forums and brand new to Androids. Bought this phone off someone for cheap, was wondering if I could fix this. Have been googling for the past 4 hours and found some info. Here is what I know about the device.
It was rooted (not sure which rom), the recovery does say unlocked and tampered. I can boot into TWRP recovery. It says no OS. I have SDK Manager and correct updates, USB driver installed, HTC Sync Manager installed. Also have Stock rom for HTC One.
I have tried to use TWRP to load a stock rom using ADB, I can not in any way get it to read the device. On the phone I go into TWRP - > Advanced - ADB Sideload -> Swiped to sideload and it says Starting ADB Sideload feature... then nothing ( I assume that's all it says), I then go into command prompt and go to the proper directory and type ADB Devices (it says List of devices attached and nothing ), I still try to load rom and it says no devices attached.
Now I am completely new to rooting of android devices, I am a little tech savvy tho. But some detailed instructions would help and be most appreciated. Basically I just need help getting PC to read the HTC One, thanks!
Click to expand...
Click to collapse
Buy a USB OTG cable and drag the rom of ur choice to the USB. Go to TWRP recovery nd flash the rom. I suggest Android Revolution HD 51 custom rom. Based on Sense 5.5 nd KitKat with loads of tweaks.
raghav kapur said:
Buy a USB OTG cable and drag the rom of ur choice to the USB. Go to TWRP recovery nd flash the rom. I suggest Android Revolution HD 51 custom rom. Based on Sense 5.5 nd KitKat with loads of tweaks.
Click to expand...
Click to collapse
Hey ok, so the USB OTG micro usb right? Would I use a flash drive I'm guessing??
I'm struggling to install Beanstalk on my 4X HD and I'm just so tired right now...
I somehow managed to unlock bootloaer via lock-relock app (in hidden menu, BL test shows "unlock" so I guess that's ok?)
I have root - well, I wouldn't be able to unlock BL without it...
And now, to install Beanstalk I need to flash CWM - http://forum.xda-developers.com/showthread.php?t=2523732
But to flash CWM I need to set up fastboot drivers and there's the problem :/
With the simple app - http://forum.xda-developers.com/showthread.php?t=2588979 - adb works ok, with "adb devices" it shows my device, but "fastboot devices" doesn't work at all. And I've read that there's this way to make fastboot working on Windows 8.1 - http://forums.team-nocturnal.com/index.php/topic/1362-how-to-adb-fastboot-in-windows-xp-7-81/ - but it doesn't work as well...
There's too much things... Dis I miss something? Maybe there's a faster and easier way to install Beanstalk? What do I have to do to get KitKat flavour on my O4X? :laugh:
You can flash recovery via adb or terminal emulator
I have the same problem, you should try this, http://forum.xda-developers.com/showthread.php?t=2230934....
I updated drivers while i unlocking bootloader by toolkit, you start toolkit, go unlock bootloader before that you check usb debugging, than follow instruction in toolkit, than phone will reboot and enter in donwloading mode(for bootloader unlock) go right click on This PC, Properties, Device manager, and you will see fastboot. And than just update driver... Right click on fastboot and Update Driver Software, navigate to the file and thats it....
Fastboot driver Download: http://www55.zippyshare.com/v/67020672/file.html
You will need winzip for this.
You can install cwm via this rootkit and later you just update with rom manager https://play.google.com/store/apps/details?id=com.koushikdutta.rommanager
I flashed recovery straight from my phone using a terminal emulator, no need to connect it to a computer. I can't remember the command though.
Sent from my Nexus 5 using Tapatalk
Ok, Kitkat is now powering my phone :victory:
Thanks for all the advices, but I used little app from GP called Flashify. It flashed CWM_6.0.1.1 with no problems at all.
I'm so happy to finally have Beanstalk ^.^
Hello to everyone.
I hope somebody to help me, last night i tried to update mi Lineage OS 16 (from erfanoabdi).
My device is unlocked bootloader, and i used the rom from nightly build (2018-21-09), it works fine and everything, the issue becomes when i look what was avaible a new update, so downloaded and install the new rom.
I do full wipe, after that i install the new rom, at this point everything its working fine, but after that when i changed the partition slot from A to B.
When i started to install the gapps they closed because it says what i am running Android 8.0, but its a mistake so i think that reboot the phone without install the gapps. So the phone starts well, so i decide again to boot into recovery (TWRP) to install the missing gapps.
When the device reboot in fastboot and i chosee the recovery option, the surprise was that TWRP was reemplaced by the stock recovery, and when i tried to flash the TWRP.img my device wont appear in fastboot mode, stays finding device and Windows wont recognized my phone.
I think the rom still no have usb adb support, so i cant flash TWRP
My device its unlocked and i was running the rom (but another nightly) .. without issues for a week ago... until i flashed this one
Now i have Lineage OS without GAPPS, without USB mode... Like the update from OPW 27 or 28 idk remember.
Its possible to fix? or my phone its ****ed, or there is one form to installl the gapps from anoter form?
Thanks for read this i hope somebody can help me.
My device its a XT1900-4 in Android 9.0 without google apps, only have the essencial apps like phone dialer , sms, the very very essencials app. Like an phone from 2008 jhaha
i offer some pay.
Update:
I attach some information photos from the Rom that im running:
(System Running) fine thanks
https://ibb.co/bXC7ye
(ADB is switched on, but no appears nothing)
https://ibb.co/exGpBz
(I tried with everyone of the opcions
https://ibb.co/ekv5jK
and this is my currently fastboot:
AP Fastboot Flash Mode (Secure)
BL: MBM-3.0-uefi-641a15b-180224
Baseband: M660_7042.27.01.74R PAYTON_LATAM_CUST
Product/Variant: payton xt1900-4 32GB P4
CPU: SDM630 1.0 (6)
Console [NULL]: null
Tools Mode Config: DISABLED
POWER OK
flashing_unlocked
Software status: Official
Transfer Mode: USB Connected
At this point my windows so says to my device is Error in a request for the USB device descriptor.
i tried last_usb_google driver.
Motorola Device manager 2.5.4
Minimal adb fastboot 1.4.2
and nothing works fine.
In my recovery appears this:
Android Recovery
motorola/payton/payton
8.0.0/OPW27.57.25-6-10/12
user/release-keys
Use volume to...etc and then i used the (Apply update from adb)
says:
Supported API: 3
Stopping adbd. . .
Now send the package you want to apply to the device with "adb sideload <filename>"
Help me pls:crying:
I have a Nokia 7 plus which is also a A/B device. I have observed many times that the fastboot mode isn't detected by the pc. Sometimes when I have a bootloop during experimentation, I force reboot into bootloader mode but it's not recognised. I reboot into recovery and select "reboot to bootloader", and this time it's recognised. Maybe these issues are related to A/B system, I'm not sure.
I think you should have the Motorola device manager installed if you're working on Windows. It contains the necessary drivers. I can't remember if it contains adb and fastboot executable files, but if it does then try using them (launching command prompt from there).
Broadcasted from Zeta Reticuli
Gravemind2015 said:
I have a Nokia 7 plus which is also a A/B device. I have observed many times that the fastboot mode isn't detected by the pc. Sometimes when I have a bootloop during experimentation, I force reboot into bootloader mode but it's not recognised. I reboot into recovery and select "reboot to bootloader", and this time it's recognised. Maybe these issues are related to A/B system, I'm not sure.
I think you should have the Motorola device manager installed if you're working on Windows. It contains the necessary drivers. I can't remember if it contains adb and fastboot executable files, but if it does then try using them (launching command prompt from there).
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
thanks for quicky reply, but i tried that and it doesnt work for me... :c
the motorola device manager its installed correctly, but i think the usb in the Android 9 it´s no working on running s.o and even in fastboot.
vmmiguel said:
thanks for quicky reply, but i tried that and it doesnt work for me... :c
the motorola device manager its installed correctly, but i think the usb in the Android 9 it´s no working on running s.o and even in fastboot.
Click to expand...
Click to collapse
My windows cmputer says that my device doesnt works properly, i read all night about this and i think when i some point i made wipe /system so i delete the twrp and the rom doesnt have usb adb i think so hahaha, i think now my x4 will stuck on only aosp 9.0 without g services :crying::crying::crying:
id start with a flash all of the latest stock firmware to clean it up. then start over
edufur said:
id start with a flash all of the latest stock firmware to clean it up. then start over
Click to expand...
Click to collapse
I tried but i have only stock recovey, and the usb adb it's not working, i think that i need to flash stock rom from stock recovery, but i dont know...
vmmiguel said:
I tried but i have only stock recovey, and the usb adb it's not working, i think that i need to flash stock rom from stock recovery, but i dont know...
Click to expand...
Click to collapse
You have to flash stock rom from fastboot. Try removing "fastboot erase userdata" from script flash-all.
Comby_sk said:
You have to flash stock rom from fastboot. Try removing "fastboot erase userdata" from script flash-all.
Click to expand...
Click to collapse
Hello Buddy, i tried that but doesnt work, recently i discover that my usb default mode is gray so i think i cant switch beetwen the usb option, and i tried ADB over network, in terminal emulator to run adbd service but it crash :c
@erfanoabdiadbi plz you cant help me, i really i was enjoying you excelent deveploment, but now in stuck in this without essencial apps like whatsapp, my smartphone works like only phone without been smart jajaja:crying::good:
Anyone?
vmmiguel said:
Anyone?
Click to expand...
Click to collapse
Read through this thread carefully...
https://forum.xda-developers.com/moto-x4/development/rom-lineage-16-0-developer-preview-t3849699
I have more or less the same problem.
I am stuck in LineageOS 15.1 and for some reason Windows does not recognize my phone (it does with other x4 phone from a friend).
I also don't have GApps installed and also don't have root access. Since I can't connect my phone, I can't root or flash some custom recovery.
I really need some help.
Hi Guys,
I have a pixel 4a 5G. I managed to install the CalyxOS bramble on the phone.
There where some bugs with this OS so I wanted to switch to lineageOS.
Since a few days I´m trying to install the OS.
The issues is that abd is not finding my device.
Fastboot somehow finds my devices and I was able to "fastboot flashing unlock" to unlock the phone.
Fastboot is also only working while I’m in the boot option menu.
When I’m leaving to Recovery Mode my device is not even recognized by fastboot.
Somehow, I can´t even get to the normal OS anymore to enable USB Debugging.
What I have tried:
Reinstall the drivers. (once manually and once via Android Studio in the SDK options)
Tried following Linux OS with preinstalled drivers (same issue - fastboot works in boot option - abd not): https://forum.xda-developers.com/t/...-installation-and-driver-issues-v3-2.3526755/
Download the latest platform tools.
Different PC.
Google service to install the default OS. Same issues when the API tried to boot to fastboot menu connection to the pc was gone.
What else can I try?
thanks for any help!
synced21 said:
Hi Guys,
I have a pixel 4a 5G. I managed to install the CalyxOS bramble on the phone.
There where some bugs with this OS so I wanted to switch to lineageOS.
Since a few days I´m trying to install the OS.
The issues is that abd is not finding my device.
Fastboot somehow finds my devices and I was able to "fastboot flashing unlock" to unlock the phone.
Fastboot is also only working while I’m in the boot option menu.
When I’m leaving to Recovery Mode my device is not even recognized by fastboot.
Somehow, I can´t even get to the normal OS anymore to enable USB Debugging.
What I have tried:
Reinstall the drivers. (once manually and once via Android Studio in the SDK options)
Tried following Linux OS with preinstalled drivers (same issue - fastboot works in boot option - abd not): https://forum.xda-developers.com/t/...-installation-and-driver-issues-v3-2.3526755/
Download the latest platform tools.
Different PC.
Google service to install the default OS. Same issues when the API tried to boot to fastboot menu connection to the pc was gone.
What else can I try?
thanks for any help!
Click to expand...
Click to collapse
Try a different cable.
houtx2 said:
Try a different cable.
Click to expand...
Click to collapse
houtx2 said:
Try a different cable.
Click to expand...
Click to collapse
i ordered a new one. anyway this is the original cable which was in the pixel box.
i got it had to plug it in and out in recvory mode.... **** this device