What officially started my run down this rabbit hole is that my new Nexbit wont recognize my SIM that is working in another GSM phone. I bought this phone off Amazon that said "Factory Unlocked". I decided to try to reflash the ROM but even when I am in fastboot mode and tell it through the CMD prompt to "fastboot oem unlock", it hangs on "Waiting on device".
I get past everything that tells me to "adb list devices" and "adb reboot" which puts me in fast boot mode but it just hangs on the "fastboot oem unlock" command by saying "Waiting on device"
DustinMoore said:
What officially started my run down this rabbit hole is that my new Nexbit wont recognize my SIM that is working in another GSM phone. I bought this phone off Amazon that said "Factory Unlocked". I decided to try to reflash the ROM but even when I am in fastboot mode and tell it through the CMD prompt to "fastboot oem unlock", it hangs on "Waiting on device".
I get past everything that tells me to "adb list devices" and "adb reboot" which puts me in fast boot mode but it just hangs on the "fastboot oem unlock" command by saying "Waiting on device"
Click to expand...
Click to collapse
1.What is the carrier of the sim?
2. Is it said "invalid sim " or it can't detect sim at all? Reflash rom can't solve any of those issues.
3. If it can't detect sim card at all , then it is hardware issue, you need to return the phone.
4. Battery life on robin sucks. It is not recommend to buy it now
DustinMoore said:
What officially started my run down this rabbit hole is that my new Nexbit wont recognize my SIM that is working in another GSM phone. I bought this phone off Amazon that said "Factory Unlocked". I decided to try to reflash the ROM but even when I am in fastboot mode and tell it through the CMD prompt to "fastboot oem unlock", it hangs on "Waiting on device".
I get past everything that tells me to "adb list devices" and "adb reboot" which puts me in fast boot mode but it just hangs on the "fastboot oem unlock" command by saying "Waiting on device"
Click to expand...
Click to collapse
Silly question though, have you ticked the 'oem unlock' in developer settings?
Some devices might need the addition of -i 0x2c3f to the fastboot command.
Read here in troubleshooting
https://forum.xda-developers.com/nextbit-robin/general/guide-install-twrp-root-robin-t3334171
Related
Hello anyone...
I have a friend's Xperia Arc S LT18i I would like to root. I already got code to Unlock the Bootloader. I have followed all the procedures on SonyMobile. But when I hold the Menu button and plug the USB in, no Window shows up to choose the winusb driver as explained on d sony website. Instead, I just get that notification on the oc taskbar saying "installing driver...." the it fails.
I tried a trick... I ran the command to unlock the bootloder " fastboot.exe -I ..... 0x (key)" while the device was on and its says "Waiting for device" which means its waiting for the device to go into bootloader mode. So while that command is waiting... I opened a new cmd and ran "adb reboot bootloader" The first command window then said something like "InfoUnlockKey needed... " or something cos I dont have the phone with me at the moment. Thinking of getting it again when I find a solution. Who could help with what to do? Thanks
its_Khal said:
Hello anyone...
I have a friend's Xperia Arc S LT18i I would like to root. I already got code to Unlock the Bootloader. I have followed all the procedures on SonyMobile. But when I hold the Menu button and plug the USB in, no Window shows up to choose the winusb driver as explained on d sony website. Instead, I just get that notification on the oc taskbar saying "installing driver...." the it fails.
I tried a trick... I ran the command to unlock the bootloder " fastboot.exe -I ..... 0x (key)" while the device was on and its says "Waiting for device" which means its waiting for the device to go into bootloader mode. So while that command is waiting... I opened a new cmd and ran "adb reboot bootloader" The first command window then said something like "InfoUnlockKey needed... " or something cos I dont have the phone with me at the moment. Thinking of getting it again when I find a solution. Who could help with what to do? Thanks
Click to expand...
Click to collapse
Service menu (*#*#7378423#*#*), Service info - Configuration.
What does it say for Bootloader status? Which OS are you using on your computer?
Install Flashtool and on C:/Flashtool/drivers you have a exe where you can install fastboot drivers
I am using windows 10 have Xperia Arc S , i want to unlock the boot loader i have the key of it from sony but i cannot install driver for S1boot Fasboot
Please help
Hey!!!
I m tryin 2 root maah phone!!
I succesfully registered on HTC DEV.. Everything is installed..
Fastboot and ADB command are working!!
But while getting my token ID, using command: "fastboot oem get_identifier_token" , nothing happens... Just comes 3 dots blinking..
PLz help and get me a solution...
Also there is no option to disable FASTBOOT in settings<device !!!
so, HELP me.. i wanna root my phone...
To disable 'Fast Boot' (different from fastboot) in the phone go to Settings>Power and it's at the bottom
You then turn the phone off and reboot it in the bootloader and if you type fastboot devices it should show the serial number of your device. If not, your drivers aren't installed properly
My Lenovo k8 note have ghost touch problem and i think it may be a software problem so i want to flash the stock frimware but i faced that whenever i started the fastboot mode i get message says "Fastboot mode secure" and when i tried to type any fastboot command in the cmd i got a message saying "< Waiting for a device >" also i have enabled usb debugging and enabled OEM from the developers option.
Can anyone help me
Nexus 5X lost lock pattern (fastboot found, adb not found), recovery "no command"
Hello !
So, I've had the same pattern to unlock my screen AND boot my phone for months.
This morning, I can't unlock : I do not remember it, I try to connect the dot "as usual" and then start to think, and now I've got my muscle memory mixed with me trying to figure out what is the pattern! So I try different combination that I think are close.
Then I reboot...
Then... there's this lock on boot time also, I tried a few different combination, and I have only 5 tries left before device WIPE !
- I have installed Android studio, the USB Driver (which I think is the right one)
- I can either boot my phone in normal mode (stuck in the dot patern lock), either in fastboot mode
- From fasboot mode, I can go to recovery, but it says "No command"
- With the SDK tools, I can list my device with "fastboot devices" (and reboot it for example), but I can't have it to appear with "adb devices"
I'll try one or two other time later when I'm tired my patern, to see if i can do it without thinking...
BUT, Can't I remove the lockscreen somehow? I'd preferably backup some files and apps data before wiping it
What do you suggest!?
Thanks in advance
I finally had to wipe / factory reset.
On reboot, he asked me to unlock the phone WITH MY GOOGLE ACCOUNT.
So ... I had to wipe everything, then unlock it. Why, oh why, the boot screen does not have this option!?
Update #2: I've been able to connect the A2 to my PC and can detect it when in fastboot mode with the "adb/fastboot" tools and with the MiFlash utility. I attempted to flash an earlier version of a ROM but I can't. MiFlash gives:
"Erase boot_a error"
I then attempted to unlock the device with the "Mi Unlock" tool but get "Sorry, your MI ID is not associated with a phone number"
Any suggestions on how to unlock the bootloader?
Update: After waiting a few minutes the touch screen started responding for a few inputs, and then stops. Toggling the lock screen a few times allows additional inputs for a few presses.
A couple of months ago the phone started displaying issues with touch input. Locking and unlocking the screen would correct the issue for a while. However, as time progressed the issue got worse.
Today I did a factory reset and since then I have been unable to input any operations. The phone is stuck on the "Hi there" welcome screen and I cannot press "Start". Power and volume buttons work fine, so I attempted to use "adb" to flash a new ROM, or a stock ROM from before July/August.
My PC won't detect the phone when in "fastboot"
What options are left?
Can I dump the stock ROM to an SD-Card and attempt to flash that from the bootloader?
Or do I need to unlock the phone prior to any ROM manipulation?
thanks for any advice
Update #2: I've been able to connect the A2 to my PC and can detect it when in fastboot mode with the "adb/fastboot" tools and with the MiFlash utility. I attempted to flash an earlier version of a ROM but I can't. MiFlash gives:
"Erase boot_a error"
I then attempted to unlock the device with the "Mi Unlock" tool but get "Sorry, your MI ID is not associated with a phone number"
Any suggestions on how to unlock the bootloader?
mindstorms911 said:
Update #2: I've been able to connect the A2 to my PC and can detect it when in fastboot mode with the "adb/fastboot" tools and with the MiFlash utility. I attempted to flash an earlier version of a ROM but I can't. MiFlash gives:
"Erase boot_a error"
I then attempted to unlock the device with the "Mi Unlock" tool but get "Sorry, your MI ID is not associated with a phone number"
Any suggestions on how to unlock the bootloader?
Click to expand...
Click to collapse
Boot your phone in system (normally).
Find build number in settings, about phone. Tap 7 times or until you've unlock developer options.
Turn on OEM Unlock and USB Debugging.
Turn off phone and boot fastboot mode.
Type 'fastboot oem unlock' and wait until it finish wipe phone.
And it's done.
RFD80M-75679 said:
Boot your phone in system (normally).
Find build number in settings, about phone. Tap 7 times or until you've unlock developer options.
Turn on OEM Unlock and USB Debugging.
Turn off phone and boot fastboot mode.
Type 'fastboot oem unlock' and wait until it finish wipe phone.
And it's done.
Click to expand...
Click to collapse
Thanks, that worked. I am now able to flash an earlier ROM, will see if that fixes the screen input issue.
Flashed an earlier version of the ROM and still had issues, so I finally managed to flash an alternative ROM - HavocOS - and that experienced the issue as well. Looks like the phone has a hardware issue somewhere.