So I looked around for this on the forum but I didnt see anything that was working for me.
So I was stuck on a bootloop and couldnt load into recovery (Teamwin) when I was on custom ROM (4.1 JB Rom)
So I ended up sbf a 2.3.6 file. Everything worked fine. I am on 2.3.6 now. However, when i try and run autoscript (http://forum.xda-developers.com/showthread.php?t=1182871) It just says waiting for device when in fastboot.
Is my fastboot broken? I have used fastboot before and have used this autoscript before to unlock the bootloader and flash custom recovery. I am using the same desktop as before as well. Any advice?
This is the only difference I can tell. When I plug my phone into my desktop for RSD it makes a sound that shows its connected and everything. However, when I put fastboot on my phone and plug my phone in the desktop makes another sound (one I never read before). Its not the same sound it used to make when connected in fastboot.
Please help thank you.
Fixed:
I just re-downloaded the drivers from Moto and that fixed it.
Related
PC will not identify phone in RSD or fastboot. I have tried all drivers I can find, have uninstalled and reinstalled all software, the drivers install in each mode but RSDlite or the official moto software updater will not ID the phone when connected...
I have tried 64 and 32 windows and 3 different cables just to be sure....
Anyone have an idea what to do? I have locked an unlocked this thing once before the 4.5.91 update and again after. I used the official Motorola Software Updater to "update" back to locked stock and have had this issue ever since then....
Fixed: Belkin USB print and storage drivers had to be removed.
* delete * 10 chars
anyone??????????????
Simple question, do you have debugging turned on? I was having a similar problem, when i realized it was off I totally face palmed myself
Yesy I have tried everything I can think of... the issue is before booting into android not after... something is blocking my phone from getting picked up by RSDlite and the moto update tool... everything in android functions fine, i have turned USB debug on and off both.
I was able to root through fastboot with no issues so it is ok, but I will be d*&$^d if I can get rsd running so I can unlock... it's not like this is new to me I have unlocked this thing twice before...
halfevildruid said:
I was able to root through fastboot with no issues so it is ok, but I will be d*&$^d if I can get rsd running so I can unlock... it's not like this is new to me I have unlocked this thing twice before...
Click to expand...
Click to collapse
You are trying to unlock the same atrix?
Once it's unlock, it remains!
Even if it doesn't show it at booting(maybe disapeared after installing a rom..)
Sent from my MB860 using XDA App
Nope. I am definately locked again. I flashed the official motorola GB software update over my existing GB software to attempt to revert to locked and stock again. It worked but now I am unable to unlock. RSDlite AND the same Moto update do not see my phone in RSD mode.
halfevildruid said:
Nope. I am definately locked again. I flashed the official motorola GB software update over my existing GB software to attempt to revert to locked and stock again. It worked but now I am unable to unlock. RSDlite AND the same Moto update do not see my phone in RSD mode.
Click to expand...
Click to collapse
Actually, once a bootloader is unlocked, its unlocked for good. By reflashing to stock, all that you did was copy over pudding (the SBF file that you flashed when you unlocked the bootloader). This hides the "Unlocked" text in the top corner. To reshow this text and regain access to locked fastboot features, you must reflash pudding via the "Unlock SBF file" available here:
briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
Im not sure why you can't get into RSD mode. Try the following:
- Insure that your volume buttons work
- Unplug phone, take out battery
- wait 10 seconds
- reinsert battery
- hold down UP (not down, I made that mistake once) volume button firmly
- press and hold power button
- phone should say "Starting RSD Mode"
To enter Fastboot mode do the same steps as above, only press the down volume button instead. When the word "FastBoot" appears, press the up volume button.
I can get into rsd and fastboot on the phone. The driver in rsd installs as se flash where it used to install as nf flash. Fastboot is working fine, I was able to reroot.
The problem is rsd does not identify my device and allow me to flash. I am thinking it is in the se flash driver instead of the previous nf flash driver.
Anyone have an opinion?
Sent from my MB860 using Tapatalk
SOLVED!!!
So I figured it out! As it happens I picked up a new Belkin 750 router with networked USB support a few days back for my ext drive and printer. Apperently the Belkin drivers were the culprit! After uninstalling them everything picked up and ran like it should. Some of you devs and folks creating guides should note this in the posts so we can give folks a heads up in case it happens to them. I am sure this will happen to someone else.
I have two identical nexus s phones.
Phone 1:
- has no usb connectivity, and thus can't be used with fastboot or adb
- unlocked bootloader
- stock jellybean
Phone 2:
- rooted
- has CWM 6.0.3.1 installed
- stock jellybean
I've taken a backup of phone 2 and want to flash it using the stock recovery on phone 1. I'm on OS X.
I've found a couple threads on this but they're all leading to dead ends. One used a utility called unyaffs, but the CWM file format has changed to use hashed blobs so that 's not going to work.
I've also seen a couple posts saying that CWM had a "soon to be released" option to create an update.zip file, but I don't see that option. Those posts are from last August. That sounds great if it existed and the image could be used with stock recovery.
All I really need to do is flash the bootloader from phone 2 on to phone 1 (I previously flashed the wrong bootloader on phone 1 which led to the loss of usb, which is what I'm trying to fix.) I tried zipping the correct bootloader image from the google download page and installing from stock recovery but it refuses to flash that image. (Not sure if fastboot images can be flashed in recovery mode?)
Argh, need a little help here.
Thanks in advance.
slide mon said:
I have two identical nexus s phones.
Phone 1:
- has no usb connectivity, and thus can't be used with fastboot or adb
- unlocked bootloader
- stock jellybean
Phone 2:
- rooted
- has CWM 6.0.3.1 installed
- stock jellybean
I've taken a backup of phone 2 and want to flash it using the stock recovery on phone 1. I'm on OS X.
I've found a couple threads on this but they're all leading to dead ends. One used a utility called unyaffs, but the CWM file format has changed to use hashed blobs so that 's not going to work.
I've also seen a couple posts saying that CWM had a "soon to be released" option to create an update.zip file, but I don't see that option. Those posts are from last August. That sounds great if it existed and the image could be used with stock recovery.
All I really need to do is flash the bootloader from phone 2 on to phone 1 (I previously flashed the wrong bootloader on phone 1 which led to the loss of usb, which is what I'm trying to fix.) I tried zipping the correct bootloader image from the google download page and installing from stock recovery but it refuses to flash that image. (Not sure if fastboot images can be flashed in recovery mode?)
Argh, need a little help here.
Thanks in advance.
Click to expand...
Click to collapse
ok your post isnt making sense. first of all how did you flash thethe wrong bootloader to phone 1? and when you compare the phones bootloaders, what is the bootloader version number for each one? so what youre saying is that phone 1 will never give you an adb connection at all, even when youre booted into android? when you plug phone 1 into the computer from within android what happens? and when you boot phone 1 into bootloader and execute fastboot mode then connect it to your computer do you see anything when you run the command ./fastboot devices? or ./adb devices when youre in adb mode on your phone? if your computer can see phone 2 and not phone 1 at all via usb then there is likely a problem with the usb port on your phone 1. you should be able to boot directly into fastboot mode by holding vol up and power button while powering on the phone, then it should take you straight to fastboot mode where you can then connect to the computer. remember to put the phone in fastboot mode then connect sometimes the computer wont see the phone if it was already plugged in upon entering fastboot mode/
haxin said:
ok your post isnt making sense. first of all how did you flash thethe wrong bootloader to phone 1? and when you compare the phones bootloaders, what is the bootloader version number for each one? so what youre saying is that phone 1 will never give you an adb connection at all, even when youre booted into android? when you plug phone 1 into the computer from within android what happens? and when you boot phone 1 into bootloader and execute fastboot mode then connect it to your computer do you see anything when you run the command ./fastboot devices? or ./adb devices when youre in adb mode on your phone? if your computer can see phone 2 and not phone 1 at all via usb then there is likely a problem with the usb port on your phone 1. you should be able to boot directly into fastboot mode by holding vol up and power button while powering on the phone, then it should take you straight to fastboot mode where you can then connect to the computer. remember to put the phone in fastboot mode then connect sometimes the computer wont see the phone if it was already plugged in upon entering fastboot mode/
Click to expand...
Click to collapse
I was trying to downgrade the phone to ICS using the factory image from google. I picked the wrong image from the google site (picked soju, needed sojus) and flashed it using fastboot. As soon as I flashed the wrong bootloader the USB connection stopped working so I didn't flash the radio or os. I no longer can connect to the phone using fastboot or adb, usb debugging stopped working. The USB debugging option is set in developer options. So, trying to get the phone working now without USB. Hope that makes sense now. :good:
I have searched a lot on google and xda and havn't found an answer to my issue. Either I'm searching for the wrong thing or I have a very unique problem.
My basic problem is on two Nabi 2's I can't access the bootloader in order to be able to fastboot TWRP (or any other recovery). It just perpetually hangs.
Both tablets boot just fine. Both tablets are on 1.9.37. Both tablets can be factory wiped via the stock recovery.
Both tablets were rooted via TWRP 2.3.3.0 a few years ago in order to install gapps. I wanted to be able to upgrade the tablets to JB when it came out so I used Nabilablite to "return to stock". I followed all of the prompts and it appeared as though everything worked as desired. I downloaded the OTA update told it to install and never looked at the version again...I just assumed it installed. Handed the tablets back to the kids and everyone was happy. Apparently all I did was flash the stock recovery because they are still rooted and have gapps after several factory resets.
Now (a year later) I have realized I was a dufas and didn't actually effect the change I wanted.
If I hold Vol+ & Pwr buttons it loads to the recovery/boot menu with "boot normally" "fastboot protocol" "recovery kernal" and "forced recovery". If I boot normal, the tablet works fine but I can't update via OTA.
If I choose fastboot protocol it just hangs...for ever...HOW DO I FIX THIS!?!?!
If I choose recovery kernal it loads the stock recovery but still wont install any update OTA or otherwise, even from the sd card.
If I choose forced recovery nothing happens, it also appears to just hang.
If I hold Vol- & Pwr button the nabi logo flashes then the device turns off.
If I hold Vol+ & Vol- & Pwr buttons it appears to be the same as just Vol+ & Pwr.
With the tablet on and fully booted I can see it via ADB. I tried using the adb restart bootloader. The tablet reboots but then just hangs never actually loading the boot loader...
I found http://forum.xda-developers.com/showthread.php?t=2587543. But aicjofs mentions seeing a bootloader issue once before.
Usually when it hangs at the Nabi logo it means you don't have the USB cable plugged in or that the fastboot driver is not installed.(Check device manager and see if fastboot driver is installed/no exclimation point). If that's not the issue then it's the bootloader which I have only seen one person have that issue. Depending on which OTA's you have ran there was an update to a Jellybean bootloader so it's possible. That can be fixed with nvflash or placing the bootloader blob in the staging partition.
Also you can always get recovery back without fastboot in Android by dd'ing the recovery over.
For example if the recovery image is on the internal SD
dd if=/data/media/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
Click to expand...
Click to collapse
I have NO idea what dd'ing the recover over is...
Thank you for any help fixing this.
P.S. I have a 3rd tablet that I also used TWRP 2.3.3.0 on to root and install gapps with. I did NOT use nabilablite on that tablet to return to stock. Yesturday I used fastboot to flash TWRP 2.6(something) to flash a JB OTA update which worked fine. It was also able to download and install every other OTA update all the way to the most recent KK with no problems...
najman9 said:
I have searched a lot on google and xda and havn't found an answer to my issue. Either I'm searching for the wrong thing or I have a very unique problem.
My basic problem is on two Nabi 2's I can't access the bootloader in order to be able to fastboot TWRP (or any other recovery). It just perpetually hangs.
Both tablets boot just fine. Both tablets are on 1.9.37. Both tablets can be factory wiped via the stock recovery.
Both tablets were rooted via TWRP 2.3.3.0 a few years ago in order to install gapps. I wanted to be able to upgrade the tablets to JB when it came out so I used Nabilablite to "return to stock". I followed all of the prompts and it appeared as though everything worked as desired. I downloaded the OTA update told it to install and never looked at the version again...I just assumed it installed. Handed the tablets back to the kids and everyone was happy. Apparently all I did was flash the stock recovery because they are still rooted and have gapps after several factory resets.
Now (a year later) I have realized I was a dufas and didn't actually effect the change I wanted.
If I hold Vol+ & Pwr buttons it loads to the recovery/boot menu with "boot normally" "fastboot protocol" "recovery kernal" and "forced recovery". If I boot normal, the tablet works fine but I can't update via OTA.
If I choose fastboot protocol it just hangs...for ever...HOW DO I FIX THIS!?!?!
If I choose recovery kernal it loads the stock recovery but still wont install any update OTA or otherwise, even from the sd card.
If I choose forced recovery nothing happens, it also appears to just hang.
If I hold Vol- & Pwr button the nabi logo flashes then the device turns off.
If I hold Vol+ & Vol- & Pwr buttons it appears to be the same as just Vol+ & Pwr.
With the tablet on and fully booted I can see it via ADB. I tried using the adb restart bootloader. The tablet reboots but then just hangs never actually loading the boot loader...
I found http://forum.xda-developers.com/showthread.php?t=2587543. But aicjofs mentions seeing a bootloader issue once before.
I have NO idea what dd'ing the recover over is...
Thank you for any help fixing this.
P.S. I have a 3rd tablet that I also used TWRP 2.3.3.0 on to root and install gapps with. I did NOT use nabilablite on that tablet to return to stock. Yesturday I used fastboot to flash TWRP 2.6(something) to flash a JB OTA update which worked fine. It was also able to download and install every other OTA update all the way to the most recent KK with no problems...
Click to expand...
Click to collapse
EDIT: OOOPPS. I didn't see this was in the XDA Assist section. I'm not suppose to answer questions(I was just searching for Nabi questions and didn't notice this was XDA assist), dedicated XDAers just point you in the right direction in this section. Please ask the question again in the Nabi2 section and I'l come help you. http://forum.xda-developers.com/nabi-2
This might help answer some questions http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
If it just hangs at fastboot protocol then the USB connection isn't good or fastboot driver isn't installed most of the time. Can you verify fastboot shows up in device manager?(I know the 3rd tabet worked OK) .
Nabilabite doesn't do anything that should change the bootloader, and fastboot should still work as it did before.
dd'ing recovery over means that you use the root access you have in Android to flash the recovery partition instead of using fastboot. IT's just another way of getting the TWRP recovery on the tablet.
The stock recovery won't install the OTA because when you added Gapps it changed some fies and the OTA sees those files as invalid and will fail.
Forced recovery always looks blank screen. It's waiting for you to give it a bootloader to run(beyond the scope here).
You should be able to get back on track once you have TWRP loaded. It's one of 3 things. Bad USB connection, fastboot driver not installed right, bootloader damage. Check the first 2 issues despite the fact the 3rd tablet had no such problems.
One of the XDA smart guys fixed my error of posting this in the wrong section.
I'm running Windows 7 Ultimate and have installed and re-installed the drivers several times. When the tablet's are fully booted ADB has a good connection and sucessfully sends the command to reboot. So I don't believe there is a driver or USB cable error...
When the tablets hang on the fastboot protocol my computer makes the usb connecting noise but fails to install the drivers...
When I hit forced recovery I hear the unrecognized USB device sound...
These two things make me think I don't have the proper drivers installed...but I don't understand how the driver's work when the tablet is booted but not when trying to access the boot loader.
It appears as though I'm going to have to try the dd method if you are able to point me in that direction please.
EDIT: Now I'm thinking I really DON'T have the fastboot drivers installed. I just plugged the 2nd tablet that hands on the fastboot menu and fastboot failed. I also booted the tablet completly, the adb driver's installed correctly but the fastboot driver's did not...I have installed the 64 bit driver's included with nabilablite. I can't find any actual other downloads. The 15 second ADB installer didn't change anything...
najman9 said:
One of the XDA smart guys fixed my error of posting this in the wrong section.
I'm running Windows 7 Ultimate and have installed and re-installed the drivers several times. When the tablet's are fully booted ADB has a good connection and sucessfully sends the command to reboot. So I don't believe there is a driver or USB cable error...
When the tablets hang on the fastboot protocol my computer makes the usb connecting noise but fails to install the drivers...
When I hit forced recovery I hear the unrecognized USB device sound...
These two things make me think I don't have the proper drivers installed...but I don't understand how the driver's work when the tablet is booted but not when trying to access the boot loader.
It appears as though I'm going to have to try the dd method if you are able to point me in that direction please.
EDIT: Now I'm thinking I really DON'T have the fastboot drivers installed. I just plugged the 2nd tablet that hands on the fastboot menu and fastboot failed. I also booted the tablet completly, the adb driver's installed correctly but the fastboot driver's did not...I have installed the 64 bit driver's included with nabilablite. I can't find any actual other downloads. The 15 second ADB installer didn't change anything...
Click to expand...
Click to collapse
Uninstall those nablablite and try this one. http://forum.xda-developers.com/showpost.php?p=62826514&postcount=2639
Or look at the other options in section 4 here http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
Other rather I soft bricked it and went into fast boot bootloop but somehow resolved it. Here's what happened:
I followed the instructions and unlocked my phone after seven days. I then proceeded to flash the India rom via fast boot (done this before on other xiaomi devices) as the current custom rom offerings aren't great and are buggy.
Then I think there was either a cable issue or a usb port issue (but I used the same usb port to flash other devices) which resulted in some error when doing fastboot (too many lines).
I then replaced the cable and tried again and it didn't let me flash the latest India rom (again my phone is unlocked and China set ie. Raphael). Telling me incorrect device etc. Not sure if this was the anti roll back issue or just again a cable issue.
I then tried to fastboot flash the china base rom but it failed repeatedly. Any attempt to switch off the phone results in me rebooting to the fastboot page.
Amazingly the computer detects the fastboot device but I'm unable to run any commands eg. Fastboot oem device info etc. It also now tells me that I have an incompatible device to Raphael!! So China set can't flash China rom....
With the last throw of the dice and almost concluding I now have a brick of a phone I decided to change usb port and tried flashing again the latest v15 China fastboot rom. After the third attempt there seemed to be progress... 200+ seconds later an error came up in the miflash tool and I thought here we go again.
To my surprise the phone actually rebooted which was why the error came up.
Thank God it booted and is now working but oh my God what an ordeal I had to go through.....
Sent from my ONEPLUS A3010 using Tapatalk
This is my very first time trying to flash a phone.
So far I have:
installed ADB on PC
unlocked the bootloader
downloaded a 1.17GB rom so that I could extract the 5mb boot.img
patched the boot.img using magisk
run "fastboot flash boot magisk_patched.img"
fastboot reboot
The phone never came-up after the reboot. Nothing on screen at all but because it was still connected to the PC I can hear beeping sounds through the PC every so often, like it does when you connect or disconnect a phone.
It seems like it is continually rebooting. I suspect it will continue to do that if I unplug it, until the battery dies.
I have no way to stop it and the hardware buttons in any combination don't seem to do anything. The battery is non-removable.
I'd really, really appreciate some patient assistance here please guys!
Re-flash phone's Stock ROM
Device is not detected by ADB. Is there another way?
Don't know of any.
Maybe u flashed x930.