So, I just picked up my new Nexus 7, dinked around a bit with it, then wanted to unlock and root it for alternative rom support. I went about doing everything, except when I went to begin the root, which looked like it was going smoothly, I realized that I did not enable USB Debugging.
I am not able to put it back to stock, nor am I able to load anything to it. I can get into FastBoot but thats it.
Any help would be appreciated. I have searched, but I could not find anything on enabling USB debugging remotely from a Mac. I am on Mac OS.
You're fine. Just search how to setup fastboot on a Mac. (Couldn't tell you, though I'm sure its close to you'd do it on Linux, and you'll need to find the Mac fastboot binary and new system.IMG(possibly a whole reflash)), then just do these commands-
fastboot oem unlock (if you've already done this skip this step)
fastboot flash system system.img
(If this doesn't work, find the entire flash all package and do)-
./flash-all.sh
(Will be something like this, you'll have to research yourself.)
Your best bet might be to use fastboot to flash the stock recovery back on the device and then use adb sideload from recovery to flash a stock system image. That would take you completely back to stock and then you could start over.
Sent from my Galaxy Nexus using Tapatalk 4
Sorry, I should have been more specific. All of the steps listed for the all of the guides require me to eventually put my tablet into USB Debugging mode. I can't do that. I can't boot into the Android system at all. I get the lovely dead robot with read warning symbol.
Is there any way to enable USB Debugging without system access on the tablet? Is this just a paper weight now? I have rooted and such since my original Nook Color, so I am not dunce. I just don't understand how I can do any of the guides if all of them call for me to put the tablet into USB debugging mode.
You only need debugging enabled to use ADB (in recovery or the OS). Fastboot will still work regardless.
NexusChrist said:
Sorry, I should have been more specific. All of the steps listed for the all of the guides require me to eventually put my tablet into USB Debugging mode. I can't do that. I can't boot into the Android system at all. I get the lovely dead robot with read warning symbol.
Is there any way to enable USB Debugging without system access on the tablet? Is this just a paper weight now? I have rooted and such since my original Nook Color, so I am not dunce. I just don't understand how I can do any of the guides if all of them call for me to put the tablet into USB debugging mode.
Click to expand...
Click to collapse
Ddi11igaf told you wat to do.
Download the full image and reset it to stock. Start again.
You are never bricked if you can get to fastboot.
:good:
Perhaps this will help:
There is currently, for some reason, no OS installed on the tablet. I do not have any roms or a backups saved on the tablet. I just want to go back to stock and start over.
I can't get into the tablet to enable USB debugging.
Is there a way to get a rom onto the tablet without USB debugging? I realize that Fast Boot works, and so does my recovery, but there is no OS installed, and no way for me to put an OS on it if I don't have USB debugging.
We understand, but you're under the false impression that USB debugging needs to be enabled to use fastboot and flash from there. It doesn't. All you have to do is unlock the bootloader (if you didn't do that already) and flash a stock ROM from https://developers.google.com/android/nexus/images. Download the stock ROM to your Mac and use the fastboot commands someone posted above. If it's not working, it's a driver issue with your Mac.
tweaked said:
Ddi11igaf told you wat to do.
Download the full image and reset it to stock. Start again.
You are never bricked if you can get to fastboot.
:good:
Click to expand...
Click to collapse
And how would one go about putting that image on the unit to flash it?
This is what I get when I try to use the one-click method from AndroidRootz:
***************************************************************
This script will: Unroot The New Nexus 7 to Stock 4.3 & Lock your Bootloader
For more details go to AndroidRootz
***************************************************************
Warning! This will delete everything on your device! BACKUP your device!
First make sure your in FASTBOOT MODE!
Press enter to continue
sending 'bootloader' (3911 KB)... OKAY
writing 'bootloader'... OKAY
rebooting into bootloader... OKAY
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-03.14
Baseband Version.....: none
Serial Number........: 07974778
--------------------------------------------
checking product... OKAY
checking version-bootloader... OKAY
sending 'boot' (6880 KB)... OKAY
writing 'boot'... OKAY
sending 'recovery' (7424 KB)... OKAY
writing 'recovery'... OKAY
sending 'system' (603495 KB)... ERROR: usb_write failed with status e00002be
FAILED (data transfer failure (No such file or directory))
Your device is now stock and unrooted
However the bootloader is still unlocked
Let your device boot up, set up your device or skip the set-up
Place your phone in USB debugging mode
Settings > Developer Options > USB Debugging, If you don't have that option
Use this guide:
Connect USB cable if your disconnected
Press enter to relock the bootloader
If I hit enter after that it simply says device not found. Again, it's asking me to put it into USB debugging, but I can't because it failed to put the OS on the device.
Looks like it was working fine, until it went to write the OS (system). Perhaps the system.img is missing or corrupt. Try downloading it direct from the link I posted above and flashing with that.
NHLWil said:
Looks like it was working fine, until it went to write the OS (system). Perhaps the system.img is missing or corrupt. Try downloading it direct from the link I posted above and flashing with that.
Click to expand...
Click to collapse
Thanks, I have it downloaded. And installed ADB and FastBoot on my Mac.
Do you have the specific steps on how to flash a rom from my computer via fastboot?
You should just be able to:
fastboot flash system system.img
If it's not working, then you'll probably need the fastboot executable from the official Android SDK for Mac, as I know someone from work had an issue flashing with one they got from elsewhere.
NHLWil said:
You should just be able to:
fastboot flash system system.img
If it's not working, then you'll probably need the fastboot executable from the official Android SDK for Mac, as I know someone from work had an issue flashing with one they got from elsewhere.
Click to expand...
Click to collapse
I was able to download it, and it sees my device, and I can perform most of the operations, however; As soon as I try to do a flash all this is what I get:
"OTT1-COMM-CK-MBP15-2400:android xxxxxx$ ./fastboot flashall flash-all.sh
error: neither -p product specified nor ANDROID_PRODUCT_OUT set"
So here is what I did, and all went well again until the System part: Run fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-flo-flo-03.14.img
fastboot reboot-bootloader
fastboot -w update image-razor-jss15q.zip
And this was the output:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-03.14
Baseband Version.....: none
Serial Number........: 07974778
--------------------------------------------
checking product... OKAY
checking version-bootloader... OKAY
sending 'boot' (6880 KB)... OKAY
writing 'boot'... OKAY
sending 'recovery' (7424 KB)... OKAY
writing 'recovery'... OKAY
sending 'system' (603355 KB)... ERROR: usb_write failed with status e00002be
FAILED (data transfer failure (No such file or directory))
I just did the same steps on my wife's PC and it worked perfectly.
Maybe something weird with the PC, I'm not sure. But all is well.
Thanks for the help!
NexusChrist said:
So here is what I did, and all went well again until the System part: Run fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-flo-flo-03.14.img
fastboot reboot-bootloader
fastboot -w update image-razor-jss15q.zip
And this was the output:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-03.14
Baseband Version.....: none
Serial Number........: 07974778
--------------------------------------------
checking product... OKAY
checking version-bootloader... OKAY
sending 'boot' (6880 KB)... OKAY
writing 'boot'... OKAY
sending 'recovery' (7424 KB)... OKAY
writing 'recovery'... OKAY
sending 'system' (603355 KB)... ERROR: usb_write failed with status e00002be
FAILED (data transfer failure (No such file or directory))
Click to expand...
Click to collapse
Boot into recovery using Power+VolDown
Then redo your above steps, but skip the erase lines at the beginning.
See if that helps.
NexusChrist said:
So here is what I did, and all went well again until the System part: Run fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-flo-flo-03.14.img
fastboot reboot-bootloader
fastboot -w update image-razor-jss15q.zip
And this was the output:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-03.14
Baseband Version.....: none
Serial Number........: 07974778
--------------------------------------------
checking product... OKAY
checking version-bootloader... OKAY
sending 'boot' (6880 KB)... OKAY
writing 'boot'... OKAY
sending 'recovery' (7424 KB)... OKAY
writing 'recovery'... OKAY
sending 'system' (603355 KB)... ERROR: usb_write failed with status e00002be
FAILED (data transfer failure (No such file or directory))
Click to expand...
Click to collapse
Pretty sure this error was your fastboot binary. You need the one from the SDK for a mac(I guess possibly a problem with your USB port, doubt it though since fastboot was talking to your device)
Related
---------------------------------------------------------------------------
I HAVE CEASED UPDATING THIS THEAD.
The old information contained below will remain for posterity, but will no longer be updated. From this point forward, all updates to this information will be found at http://www.randomphantasmagoria.com/firmware/nexus-s
---------------------------------------------------------------------------
Below is a list of all available OTA and full ROM packages for the Nexus S, model M200.
THIS IS FOR M200 ONLY. IF YOU HAVE ANOTHER VARIANT, PLEASE FIND THE THREAD FOR YOUR VARIANT.
Typical disclaimer where I tell you that all of this stuff is at your own risk and I'm not responsible if you mess up your phone, yadda yadda.
These updates are 100% stock and are NOT rooted.
HOW TO FLASH
I'm not giving instructions on how to flash ZIP files. If you don't know how to do that, you probably shouldn't be looking for stuff in this thread. There are plenty of threads on how to flash zips through recovery. Do a little reading before proceeding.
The recovery-flashable full ROM packages will only flash if your phone has no ROM, any custom ROM, or a stock ROM that's older than the version you're trying to flash. For instance, the 2.3.4 full ROM package will flash over the stock 2.3.3 ROM, but not over the stock 2.3.6 ROM.
With fastboot images, you can flash any version over any other version.
WHAT HAPPENS IF I GET AN ERROR WHILE FLASHING?
If you get an error flashing a recovery-flashable full ROM package, it means that you are running a stock ROM that's newer than the version you're trying to flash. If you're trying to downgrade, then you must install ClockworkMod recovery, then wipe system, boot, data, cache, and Dalvik cache. You will then be able to flash the older version. Optionally, you can also flash fastboot images of a version older than the version you're trying to flash.
If you get an error flashing an incremental update, it means one of four things. Either you don't have an M200, you aren't running a stock ROM, you have changed something with your stock ROM (this includes build.prop changes, radio or bootloader changes as well), or you're running Android 4.X and trying to update manually. These incremental updates only work if you are running a completely, perfectly stock ROM exactly the way Google provides it, with the right radio and the right bootloader. There are no exceptions to this rule. Furthermore, Android 4.X ROMs can no longer be updated manually in stock recovery. See below.
A NOTE ABOUT ANDROID 4.X OTAs
Beginning with Ice Cream Sandwich, Google has made a change to stock recovery that prevents you from flashing future OTA updates manually. Instead you are now required to wait for the OTA notification on your phone and then tap "Reboot and Install."
If this pisses you off, you have the option of unlocking your bootloader, installing either a stock Gingerbread recovery or ClockworkMod recovery, and then flashing the OTA updates manually.
LATEST VERSION
The latest Android version available for M200 is Gingerbread version 2.3.6, build GRK39F.
BUILD REFERENCE
GRI54 - Android 2.3.3
GRJ22 - Android 2.3.4
GRK39F - Android 2.3.6
FULL ROMS
FASTBOOT IMAGES
If you're comfortable with fastboot, you can flash these images to return your phone back to raw stock.
Generally the best way to do this is to perform the following steps:
Put all six fastboot images in one folder, unlock your bootloader, perform the fastboot flashes, then lock the bootloader:
fastboot oem unlock
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
FLASHING FASTBOOT IMAGES WILL ERASE ALL OF YOUR PHONE'S DATA AND WILL RETURN YOU TO A FACTORY STOCK, UNROOTED STATE.
Android 2.3.6/GRK39F/KRKC1 Radio/KA3 Bootloader
Official factory fastboot images, must be flashed using fastboot on an unlocked bootloader. Contains recovery, radio, and bootloader.
THESE IMAGES MUST BE FLASHED USING BOOTLOADER VERSION I9020XXKA3
RECOVERY-FLASHABLE ROMS
Android 2.3.4/GRJ22/KRKC1 Radio/KA3 Bootloader
Official, signed, can flash with ClockworkMod or stock recovery. Contains recovery, radio and bootloader.
Still need ROMs for:
Android 2.3.3/GRI54/KRKB3 Radio/KA3 Bootloader
Android 2.3.6/GRK39F/KRKC1 Radio/KA3 Bootloader
INCREMENTAL UPDATES
The links provided here are to Google's official update package for each version. Sometimes Google provides a small incremental update package for upgrading between versions, other times they just provide full ROM packages for bigger version upgrades. For instance, Google pushed a small incremental update to upgrade from 2.3.4 to 2.3.6. If your phone was running 2.3.3, there is no 2.3.3 to 2.3.6 incremental update, so Google would push the 2.3.6 full ROM package.
Android 2.3.3 (Build GRI54/KRKB3 Radio/KA3 Bootloader)
2.3.3 -> 2.3.4
Android 2.3.4 (Build GRJ22/KRKC1 Radio/KA3 Bootloader)
2.3.4 -> 2.3.6
This does not mention ICS for the Korean Nexus S. Is that because it's not available or supported, yet? Are these only "official" ROMs?
I've been scanning these pages for an hour, and I cannot find a clear, simple answer to whether or not I can get ICS working on my Korean SHW-M200.
Frustrating.
Why doesn't XDA just offer upgrades as a service? Hell, I'll pay someone 10 bucks to just do it and get it over with, ffs.
abundantmind said:
This does not mention ICS for the Korean Nexus S. Is that because it's not available or supported, yet? Are these only "official" ROMs?
I've been scanning these pages for an hour, and I cannot find a clear, simple answer to whether or not I can get ICS working on my Korean SHW-M200.
Frustrating.
Why doesn't XDA just offer upgrades as a service? Hell, I'll pay someone 10 bucks to just do it and get it over with, ffs.
Click to expand...
Click to collapse
No. It isn't available yet.
Sent from my Xoom using Tapatalk
oldblue910 said:
No. It isn't available yet.
Click to expand...
Click to collapse
What I'm trying to find out is if there is an ics ROM that will work on my phone. If I have to wait for KT to issue an official version of ics OTA, then I'll be waiting for another year...possibly forever. Where's the fun in that?
Surely, somebody must be working on this.
abundantmind said:
What I'm trying to find out is if there is an ics ROM that will work on my phone. If I have to wait for KT to issue an official version of ics OTA, then I'll be waiting for another year...possibly forever. Where's the fun in that?
Surely, somebody must be working on this.
Click to expand...
Click to collapse
Dude, just use those ics roms in the Nexus S development section. Every rom and kernels work on M200 varient.
Sent from my Nexus S using Tapatalk
no they don't, E: signature verification fail everytime
edit: still on 2.3.4 can't get beyond it without having to flash cwm, which i dont want to do
rorio82 said:
no they don't, E: signature verification fail everytime
edit: still on 2.3.4 can't get beyond it without having to flash cwm, which i dont want to do
Click to expand...
Click to collapse
whats ur nexus s model?
I have updated the original post with some new notes and also added the 2.3.6/GRK39F fastboot images for M200.
Is is possible to flash another Stock ROM to get ICS?
Is there a tutorial for getting ICS to the M200? I just installed CyanogenMod 9 on my German Galaxy S and it was a piece of cake compared to the SHW-M200
I tried to follow this guide, but when I try to flash the herring.img (step 5), I just get an Android standing before a big warning sign.
Code:
$ ./fastboot flash recovery ~/Downloads/recovery-clockwork-herring.img
< waiting for device >
but unfortunately, you can use i9020/i9023 ICS package in M200 without any problems at all...
Well guys the Nexus S has been an amazing phone for me, but I have moved on to the Galaxy Nexus. I will still be keeping these stock images threads up to date for the remainder of the Nexus S' OTA life cycle. I know these threads have helped a lot of people so it's the least I can do to help a community of people who are so passionate about such a great device. Cheers!
Sent from my Xoom using Tapatalk
---------------------------------------------------------------------------
I HAVE CEASED UPDATING THIS THEAD.
The old information contained below will remain for posterity, but will no longer be updated. From this point forward, all updates to this information will be found at http://www.randomphantasmagoria.com/firmware/nexus-s
---------------------------------------------------------------------------
Your effort is really appreciated
oldblue910 said:
---------------------------------------------------------------------------
I HAVE CEASED UPDATING THIS THEAD.
The old information contained below will remain for posterity, but will no longer be updated. From this point forward, all updates to this information will be found at http://www.randomphantasmagoria.com/firmware/nexus-s
---------------------------------------------------------------------------
Click to expand...
Click to collapse
Thanks. The blogging at randomphantasmagoria is very useful.
I managed to locate all the official firmware for the Nexus S (M200). Cheers and enjoy your Galaxy Nexus
4.1.1 now dead
rorio82 said:
no they don't, E: signature verification fail everytime
edit: still on 2.3.4 can't get beyond it without having to flash cwm, which i dont want to do
Click to expand...
Click to collapse
I have update m200s with 4.1.1 sojuk-jro03e and now phone is dead. no sign of life.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\ahmed soft>cd c:\
C:\>cd C:\android-sdk-windows\platform-tools
C:\android-sdk-windows\platform-tools>fastboot flash recovery touch-crespo.img
error: cannot load 'touch-crespo.img'
C:\android-sdk-windows\platform-tools>
C:\android-sdk-windows\platform-tools>fastboot flash recovery recovery-clockwork
-touch-5.8.0.2-crespo.img
< waiting for device >
sending 'recovery' (3464 KB)...
OKAY [ 0.438s]
writing 'recovery'...
OKAY [ 0.453s]
finished. total time: 0.891s
C:\android-sdk-windows\platform-tools>adb reboot bootloader
error: device not found
C:\android-sdk-windows\platform-tools>adb reboot bootloader
error: device not found
C:\android-sdk-windows\platform-tools>
C:\android-sdk-windows\platform-tools>fastboot flash bootloader bootloader-cresp
o-i9020xxlc2.img
sending 'bootloader' (1536 KB)...
OKAY [ 0.188s]
writing 'bootloader'...
OKAY [ 0.359s]
finished. total time: 0.547s
C:\android-sdk-windows\platform-tools>
C:\android-sdk-windows\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
C:\android-sdk-windows\platform-tools>
C:\android-sdk-windows\platform-tools>fastboot flash radio radio-crespo-m200krkc
1.img
sending 'radio' (12288 KB)...
OKAY [ 1.547s]
writing 'radio'...
OKAY [ 1.688s]
finished. total time: 3.234s
C:\android-sdk-windows\platform-tools>
C:\android-sdk-windows\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
C:\android-sdk-windows\platform-tools>fastboot -w update image-sojuk-jro03e.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXLC2
Baseband Version.....: M200KRKC1
Serial Number........: 3435FC23CACE00EC
--------------------------------------------
checking product...
OKAY [ 0.016s]
checking version-bootloader...
OKAY [ 0.000s]
checking version-baseband...
OKAY [ 0.000s]
sending 'boot' (3964 KB)...
OKAY [ 0.500s]
writing 'boot'...
OKAY [ 0.500s]
sending 'recovery' (4308 KB)...
OKAY [ 0.547s]
writing 'recovery'...
OKAY [ 0.547s]
sending 'system' (294030 KB)...
OKAY [ 36.828s]
writing 'system'...
FAILED (remote: Write Fail)
finished. total time: 39.000s
C:\android-sdk-windows\platform-tools>adb reboot bootloader
At end says fail and now dead. on other version stop at startup. now need help.
Thanks
br, raja
raja16sep said:
I have update m200s with 4.1.1 sojuk-jro03e and now phone is dead. no sign of life.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\ahmed soft>cd c:\
C:\>cd C:\android-sdk-windows\platform-tools
C:\android-sdk-windows\platform-tools>fastboot flash recovery touch-crespo.img
error: cannot load 'touch-crespo.img'
C:\android-sdk-windows\platform-tools>
C:\android-sdk-windows\platform-tools>fastboot flash recovery recovery-clockwork
-touch-5.8.0.2-crespo.img
< waiting for device >
sending 'recovery' (3464 KB)...
OKAY [ 0.438s]
writing 'recovery'...
OKAY [ 0.453s]
finished. total time: 0.891s
C:\android-sdk-windows\platform-tools>adb reboot bootloader
error: device not found
C:\android-sdk-windows\platform-tools>adb reboot bootloader
error: device not found
C:\android-sdk-windows\platform-tools>
C:\android-sdk-windows\platform-tools>fastboot flash bootloader bootloader-cresp
o-i9020xxlc2.img
sending 'bootloader' (1536 KB)...
OKAY [ 0.188s]
writing 'bootloader'...
OKAY [ 0.359s]
finished. total time: 0.547s
C:\android-sdk-windows\platform-tools>
C:\android-sdk-windows\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
C:\android-sdk-windows\platform-tools>
C:\android-sdk-windows\platform-tools>fastboot flash radio radio-crespo-m200krkc
1.img
sending 'radio' (12288 KB)...
OKAY [ 1.547s]
writing 'radio'...
OKAY [ 1.688s]
finished. total time: 3.234s
C:\android-sdk-windows\platform-tools>
C:\android-sdk-windows\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
C:\android-sdk-windows\platform-tools>fastboot -w update image-sojuk-jro03e.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXLC2
Baseband Version.....: M200KRKC1
Serial Number........: 3435FC23CACE00EC
--------------------------------------------
checking product...
OKAY [ 0.016s]
checking version-bootloader...
OKAY [ 0.000s]
checking version-baseband...
OKAY [ 0.000s]
sending 'boot' (3964 KB)...
OKAY [ 0.500s]
writing 'boot'...
OKAY [ 0.500s]
sending 'recovery' (4308 KB)...
OKAY [ 0.547s]
writing 'recovery'...
OKAY [ 0.547s]
sending 'system' (294030 KB)...
OKAY [ 36.828s]
writing 'system'...
FAILED (remote: Write Fail)
finished. total time: 39.000s
C:\android-sdk-windows\platform-tools>adb reboot bootloader
At end says fail and now dead. on other version stop at startup. now need help.
Thanks
br, raja
Click to expand...
Click to collapse
Just unlock bootloader and execute ***.bat file.
Sent from my Nexus S using Tapatalk 2
But How Sir,
Articudos said:
Just unlock bootloader and execute ***.bat file.
Sent from my Nexus S using Tapatalk 2
Click to expand...
Click to collapse
Thanks for Answer but Phone has no sighn of life. its not powering on or not going in download mode,Nothing complete dead. Can not attach to computer. Even donot donot take Chargeing_________________ Which ***.bat file where it is?
Br, Raja
install drivers for your pnone first
open run and type
devmgmt.msc
you should see android adb interface or fastboot something,...
if u dont see them,.. please install drivers
raja16sep said:
Thanks for Answer but Phone has no sighn of life. its not powering on or not going in download mode,Nothing complete dead. Can not attach to computer. Even donot donot take Chargeing_________________ Which ***.bat file where it is?
Br, Raja
Click to expand...
Click to collapse
Maybe...As far as I remember, there is just one "bat" file. If you are running windows, just execute it.(4.1+)
(You have to run fastboot mode befor executing "bat" file)
Sent from my Nexus S using Tapatalk 2
Power Ic Problem.
Thanks for help. The phone was restarting before. After flash now there is problem in its Power Ic. Because its getting hot. Let repaired by Hardware then try other solutions.
thanks
Br, Raja
Can anyone pls upload M200 Sbl.bin.Thanks
Hi guys,
I need your help.
I rooted and unlocked my device using wug fresh toolkit 1.5.3.
After that I installed TWRP trough adb.
Next, I flashed Paranoid Android and everything was working fine.
By some stupid ideea that i had, because there was no space on my device
due to leftovers from the apps I had before, I tought I should go in TWRP and wipe everything,
than flash the Rom again.
I wiped cache, dalvik, restore factory settings and than I wiped sd card both internal and external.
Right now I cant flash the Rom again or restore a nandroid, because there is nothing on device.
Connecting to computer will not recognize it.
All I can do is, while conected to computer, use buttons and get into bootloader and from there on TWRP recovery.
Please help me with some instructions on how to make my Nexus 7 work again.
Thank you.
You can manually push ROM/Kernel/Gapps files to /sdcard using adb push from Android SDK.
I can't exactly recall if you can push the files from bootloader, or recovery, or both, but a push command would look like:
Code:
adb push FILE.zip /sdcard
adb push being the ADB command to push files from the computer to the device
FILE.zip being the name of the file you want to send to the device (for example, EOS-grouper-20120908-27.zip)
/sdcard being the place on the device you want the file to be placed in
In some cases, /sdcard may not work, but /data/media should work.
Another option is to restock using a factory image from Google and then start over with flashing CWM, and then copying over your ROM/Kernel/Gapps files.
adb push
espionage724 said:
You can manually push ROM/Kernel/Gapps files to /sdcard using adb push from Android SDK.
I can't exactly recall if you can push the files from bootloader, or recovery, or both, but a push command would look like:
Code:
adb push FILE.zip /sdcard
adb push being the ADB command to push files from the computer to the device
FILE.zip being the name of the file you want to send to the device (for example, EOS-grouper-20120908-27.zip)
/sdcard being the place on the device you want the file to be placed in
In some cases, /sdcard may not work, but /data/media should work.
Another option is to restock using a factory image from Google and then start over with flashing CWM, and then copying over your ROM/Kernel/Gapps files.
Click to expand...
Click to collapse
I cannot push as it says "device not found".
Ok, I had to restock and unroot. Now is working fine. I used also wug fresh toolkit.
Will have to root again and so on...
Thanks!
same as above
hey guys my nexus 2012 wifi running 4.3 rooted has TWERP and installed CM 10.1.3 for some dumb reason as the above mentioned i too wiped dalvik cache and sd via TWERP. Now im stuck on google logo with an unlock padlock logo I can still go to fastboot but cant open recovery when I open it I only get the green robot with red warning sign. Im desperate I used wugfresh toolkit 1.7.5 and use the FlashStock+Unroot everything is ok on the script exept for bootloader failed my device got 4.18 while it says the toolkit needs 4.2+ i dont remember anymore. now im still stuck on google logo with an unlock padlock logo. Hope you guys can help me its my daughter's tablet she'll be sad without it..:crying: well be very thankful for any help thank in advance.
heres the code
Flash Stock + Unroot...
------------------------------------------------------------------
erasing 'boot'...
OKAY [ 0.020s]
finished. total time: 0.023s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.039s]
finished. total time: 0.039s
erasing 'recovery'...
OKAY [ 0.020s]
finished. total time: 0.020s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.044s]
finished. total time: 0.045s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.977s]
finished. total time: 0.977s
sending 'bootloader' (2100 KB)...
OKAY [ 0.258s]
writing 'bootloader'...
OKAY [ 0.709s]
finished. total time: 0.968s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.23
Baseband Version.....: N/A
Serial Number........: 015d257818580418
--------------------------------------------
checking product...
OKAY [ 0.030s]
checking version-bootloader...
OKAY [ 0.022s]
sending 'boot' (4896 KB)...
OKAY [ 0.584s]
writing 'boot'...
OKAY [ 0.179s]
sending 'recovery' (5432 KB)...
OKAY [ 0.653s]
writing 'recovery'...
OKAY [ 0.186s]
erasing 'system'...
OKAY [ 0.057s]
sending 'system' (529061 KB)...
FAILED (remote: (Nv3pBadReceiveLength))
finished. total time: 4.274s
Booting up your freshly flashed stock device...
------------------------------------------------------------------
Wait for your device to finish booting up...
- It may appear to be boot looping; just wait...
- It could take 5-10 minutes; please be patient...
When its finally booted back up, please remember
to re-enable USB debugging if you plan on using
the toolkit to perform other operations.
NOTE: If this process was too quick and your device
is still in bootloader mode, then flashing stock may
have failed or been incomplete. Simply check the
log above: if you notice it skipped steps because it
didn't meet certain requirements, like the bootloader
or baseband version, then consider enabling 'Force Flash'
mode in the toolkits options menu and trying the
'Flash Stock + Unroot' processs again. Cheers.
Press any key to exit...
With what seems to be a soft-brick Google Nexus 7 2012 Wi-fi model, I tried going through comminus' tutorial on both my laptop and my desktop, but I end up with the following error message when I try to unlock the bootloader, an essential part to fixing my boot loop/soft-brick problem. I am unrooted, by the way, so TWRP and other custom recoveries are not an option unless there is a way to flash them via fastboot. I cannot access ADB in any way whatsoever.
Code:
android-sdk\platform-tools>fastboot oem unlock
...
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: (Unknown error code))
finished. total time: XX.XXXs
Of course, any attempt at flashing anything would result in no avail, neither:
Code:
android-sdk\platform-tools>fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (2100 KB)
FAILED (remote: Bootloader is locked.)
finished. total time: X.XXXs
android-sdk\platform-tools>fastboot -w update image-nakasi-jwr66y.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
———————————————————————————————————————————————————
Bootloader version...: 4.23
Baseband version.....: N/A
Serial Number........: (insert unique serial here)
———————————————————————————————————————————————————
checking product...
OKAY [ X.XXXs]
checking version-bootloader...
OKAY [ X.XXXs]
sending 'boot' (4896 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: X.XXXs
I have verified that both computers can detect my device correctly via the fastboot devices command.
I do not understand what is wrong with my device at this point. Any pointers or tips would be greatly appreciated.
Bump. I could use some help regarding this issue, preferably before I have to depart for Los Angeles on the 2nd!
RinDunois said:
Bump. I could use some help regarding this issue, preferably before I have to depart for Los Angeles on the 2nd!
Click to expand...
Click to collapse
Have you tried Wug's Toolkit? I have been here myself, checked the softbricked option and even had to flash back as far as 4.4.2. Place your device in fastboot and check the soft brick option let me know where you get with this suggestion.
I just wanted to let you know that the first thing I noticed is the following error:
FAILED (remote: Bootloader is locked.)
This has to be unlocked first before you will be able to flash the OTA. You can use wuget tool to unlock the bootloader and then try to use fastboot. Once that is done, you can relock it if you want.
PapaMag said:
Have you tried Wug's Toolkit? I have been here myself, checked the softbricked option and even had to flash back as far as 4.4.2. Place your device in fastboot and check the soft brick option let me know where you get with this suggestion.
Click to expand...
Click to collapse
That was one of the first things I tried, actually, on suggestion of some friends who have experience with the device. Sadly, none of the driver options worked nor did the softbrick option get me anywhere, so I moved onto doing it manually doing it via cmd instead.
barakisbrown said:
I just wanted to let you know that the first thing I noticed is the following error:
FAILED (remote: Bootloader is locked.)
This has to be unlocked first before you will be able to flash the OTA. You can use wuget tool to unlock the bootloader and then try to use fastboot. Once that is done, you can relock it if you want.
Click to expand...
Click to collapse
I am fully aware that I need to unlock the bootloader before doing anything. I wanted to see if the so called flash all script was going to help AFTER seeing that the unlock bootloader command did not work whatsoever as you can see in the first block of code in my post.
Note: This is NOT A FIX FOR SOFTBRICKED DEVICES. This is simply an easy way for someone who is rooted to easily update /system to the most recent build without erasing user data.
Please note this is not a clean factory flash - this does not flash radio or bootloader, and does not wipe /data. This works regardless of whether you have a custom kernel or unlocked bootloader.
This assumes that you already know how to use ADB and fastboot.
1. Download the latest factory image for your device from HERE.
2. Unzip the archive.
3. Open the folder it was unzipped to, and you will find an archive titled "image-[device]-[build number].zip. Copy this to your ADB/fastboot folder.
4. Connect your phone and reboot to bootloader.
5. Type:
Code:
fastboot update [name of image].zip
6. Wait for the process to finish. Phone will automatically reboot into system when complete.
Congratulations, you are now on the latest factory system image. This overwrites boot, dtbo, and breaks root, so reflash kernels and Magisk as desired. Be aware that the kernel you are flashing must match the security update you flashed.
If for whatever reason you do want to wipe /data when flashing this, use:
Code:
fastboot -w update [name of image].zip
If you want to update your radio, simply pull the radio.img from the factory zip, and while in bootloader, type:
Code:
fastboot flash radio [name of radio image].img
After you flash bootloader and radio, make sure you use
Code:
fastboot reboot bootloader
to ensure you're on the new firmware.
I'm getting the following, any advice? I definitely dont want to wipe, and suspect flashing a bootloader image will do that?
:
:\adb> fastboot update image.zip
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
--------------------------------------------
Bootloader Version...: mw8998-002.0066.00
Baseband Version.....: g8998-00164-1710262031
Serial Number........: XXXXXX
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
FAILED
Device version-bootloader is 'mw8998-002.0066.00'.
Update requires 'mw8998-002.0067.00.
mjondj said:
I'm getting the following, any advice? I definitely dont want to wipe, and suspect flashing a bootloader image will do that?
:
:\adb> fastboot update image.zip
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
--------------------------------------------
Bootloader Version...: mw8998-002.0066.00
Baseband Version.....: g8998-00164-1710262031
Serial Number........: XXXXXX
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
FAILED
Device version-bootloader is 'mw8998-002.0066.00'.
Update requires 'mw8998-002.0067.00.
Click to expand...
Click to collapse
Sounds like you've been without OTAs for a while.
Pull the bootloader and radio images from the .021 zip. They will be right there in the same folder as image-walleye-opm1.171019.021.zip.
Copy to fastboot folder
Code:
fastboot flash bootloader bootloader-walleye-mw8998-002.0067.00.img
fastboot reboot bootloader
fastboot flash radio radio-walleye-g8998-00164-1710262031.img
fastboot reboot bootloader
fastboot update image-walleye-opm1.171019.021.zip
socal87 said:
Pull the bootloader image from the .021 zip. It'll be right there in the same folder as image-walleye-opm1.171019.021.zip.
Copy to fastboot folder
Code:
fastboot flash bootloader bootloader-walleye-mw8998-002.0067.00.img
fastboot reboot bootloader
fastboot update image-walleye-opm1.171019.021.zip
Click to expand...
Click to collapse
---------- Post added at 04:22 PM ---------- Previous post was at 04:21 PM ----------
flashing all those won't wipe the device?
mjondj said:
Pull the bootloader image from the .021 zip. It'll be right there in the same folder as image-walleye-opm1.171019.021.zip.
Copy to fastboot folder
---------- Post added at 04:22 PM ---------- Previous post was at 04:21 PM ----------
flashing all those won't wipe the device?
Click to expand...
Click to collapse
No. Flashing without the -w flag does not wipe. Refer to bottom of first post.
socal87 said:
No. Flashing without the -w flag does not wipe. Refer to bottom of first post.
Click to expand...
Click to collapse
i appreciate the help, but now i'm soft bricked (wont go past G logo) after failing on system. i was rooted w/ magisk. i suspect thats what the problem was. is there any way to avoid a wipe at this point and get back up and running?
PS C:\adb> fastboot devices
xxx fastboot
PS C:\adb> fastboot flash bootloader boot.img
target reported max download size of 536870912 bytes
sending 'bootloader' (38652 KB)...
OKAY [ 0.913s]
writing 'bootloader'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
(bootloader) Updating: partition:1 @0000D000 sz=0000B000
(bootloader) Updating: partition:2 @00018000 sz=0000B000
(bootloader) Updating: partition:3 @00023000 sz=0000B000
(bootloader) Updating: partition:4 @0002E000 sz=0000B000
(bootloader) Updating: partition:5 @00039000 sz=0000B000
(bootloader) Updating: cmnlib64 @00044000 sz=00048000
(bootloader) Updating: cmnlib @0008C000 sz=00037000
(bootloader) Updating: devcfg @000C3000 sz=0000F000
(bootloader) Updating: hyp @000D2000 sz=00040000
(bootloader) Updating: keymaster @00112000 sz=00046000
(bootloader) Updating: lockbooter @00158000 sz=00016000
(bootloader) Updating: pmic @0016E000 sz=0000D000
(bootloader) Updating: rpm @0017B000 sz=0003A000
(bootloader) Updating: tz @001B5000 sz=001DB000
(bootloader) Updating: xbl @00390000 sz=003A2000
(bootloader) Updating: apdp @00732000 sz=00004000
(bootloader) Updating: msadp @00736000 sz=00004000
(bootloader) Updating: hosd @0073A000 sz=01E20000
(bootloader) Updating: abl @0255A000 sz=00065000
OKAY [ 0.918s]
finished. total time: 1.840s
PS C:\adb> fastboot reboot bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
PS C:\adb> fastboot flash radio radio.img
target reported max download size of 536870912 bytes
sending 'radio' (60428 KB)...
OKAY [ 1.437s]
writing 'radio'...
(bootloader) Updating: modem @00001000 sz=03B01000
OKAY [ 0.552s]
finished. total time: 2.000s
PS C:\adb> fastboot reboot bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
PS C:\adb> fastboot update image.zip
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
--------------------------------------------
Bootloader Version...: mw8998-002.0067.00
Baseband Version.....: g8998-00164-1710262031
Serial Number........: xxx
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.002s]
sending 'boot' (32768 KB)...
OKAY [ 0.775s]
writing 'boot'...
OKAY [ 0.002s]
sending sparse 'system' (524284 KB)...
OKAY [ 13.252s]
writing 'system'...
OKAY [ 0.002s]
sending sparse 'system' (524284 KB)...
FAILED (remote: No such partition.)
finished. total time: 14.383s
PS C:\adb>
Click to expand...
Click to collapse
mjondj said:
i appreciate the help, but now i'm soft bricked (wont go past G logo) after failing on system. i was rooted w/ magisk. i suspect thats what the problem was. is there any way to avoid a wipe at this point and get back up and running?
Click to expand...
Click to collapse
A factory reset in recovery will get it up and running again and afterwards you can reroot.
gee2012 said:
A factory reset in recovery will get it up and running again and afterwards you can reroot.
Click to expand...
Click to collapse
this doesnt really help. the whole point is to not wipe
mjondj said:
this doesnt really help. the whole point is to not wipe
Click to expand...
Click to collapse
Don`t think its possible without a wipe, but good luck anyways
gee2012 said:
Don`t think its possible without a wipe, but good luck anyways
Click to expand...
Click to collapse
the title of this thread includes the words "no wipe"
mjondj said:
the title of this thread includes the words "no wipe"
Click to expand...
Click to collapse
No wipe, extenuating cirumstances not withstanding. But I have an idea.
Boot TWRP and use ADB push to send the image.zip to /tmp. Flash using TWRP, see if that works.
Also, check out Deuce's tool here.
mjondj said:
the title of this thread includes the words "no wipe"
Click to expand...
Click to collapse
We know that, but the dude he is trying to help is soft bricked probably by following op instructions which I do t k ow why we have a other thread about anyway.
dobbs3x said:
We know that, but the dude he is trying to help is soft bricked.
Click to expand...
Click to collapse
This method is not a fix for, nor does it address prexisting issues. Everyone is responsible for their own phones. I will help as much as I can but the responsibility lies on the user to be familiar with flashing as well as what to do if something goes wrong.
socal87 said:
This method is not a fix for, nor does it address prexisting issues. Everyone is responsible for their own phones. I will help as much as I can but the responsibility lies on the user to be familiar with flashing as well as what to do if something goes wrong.
Click to expand...
Click to collapse
If you post instructions and someone bricks their phone from it then they are going to come here and post about it.
We already have threads that talk about updating and there was really no need for this one anyway.
dobbs3x said:
If you post instructions and someone bricks their phone from it then they are going to come here and post about it.
We already have threads that talk about updating and there was really no need for this one anyway.
Click to expand...
Click to collapse
My instructions didn't brick his phone. And while there are threads about updating from the factory zip without wiping, this is a manual way to update /system independently. If you feel the thread is unnecessary, let an admin know, and they will decide whether to remove it.
Or, you could simply be thankful that I'm trying to help.
Will this method work for nonrooted devices?
Phil_Chambers said:
Will this method work for nonrooted devices?
Click to expand...
Click to collapse
Yes. This is functionally similar to flashing the factory zip, except you're typing the commands yourself and omitting the -w (wipe) flag.
Issue solved by using this script to flash all the imgs to both slots. up and running in one pass like nothing happened:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
I'm getting this when I try to boot the OTA .zip.
">fastboot update walleye-ota-opm1.171019.021-bb894efa.zip
archive does not contain 'android-info.txt'
error: update package 'walleye-ota-opm1.171019.021-bb894efa.zip' has no android-info.txt"
Not sure what I'm doing wrong
Edit: I had to sideload the update. But worked like a charm
Phil_Chambers said:
I'm getting this when I try to boot the OTA .zip.
">fastboot update walleye-ota-opm1.171019.021-bb894efa.zip
archive does not contain 'android-info.txt'
error: update package 'walleye-ota-opm1.171019.021-bb894efa.zip' has no android-info.txt"
Not sure what I'm doing wrong
Edit: I had to sideload the update. But worked like a charm
Click to expand...
Click to collapse
Interesting. Did you modify the zip in any way?
Hello Forum,
i've buyed recently a Nexus 10 tablet in order to install a Nethunter distribution on it but on this tablet seems that bootloader is not present. Is it possible?
I've tried to enter it thousand times using buttons power - vol up - vol down but nothing, tablet vibrates but nothing appear on screen.
At the moment mu tablet is on bootloop and i don't know how to fix it without access the bootloader.
I'm continuing trying also with fastboot and adb command.
Do you have any solution?
Regards
LITTLE UPDATE: i'm able to establish a connection using fastboot but i can't flash nothing cause my OEM is locked and if i try to enter fastboot oem unlock nothig appens.
fastboot update image-mantaray-lmy49j.zip
--------------------------------------------
Bootloader Version...: MANTAMF01
Baseband Version.....: no modem
Serial Number........: R32D202YHVP
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.001s]
Checking 'version-bootloader' OKAY [ 0.000s]
extracting boot.img (4 MB) to disk... took 0.009s
archive does not contain 'boot.sig'
Sending 'boot' (4966 KB) OKAY [ 0.626s]
Writing 'boot' FAILED (remote: 'Locked - Use "fastboot oem unlock" to Unlock')
fastboot: error: Command failed
C:\Users\ShUtDoWn\Downloads\ROOT NEXUS 10\platform-tools_r31.0.0-windows\platform-tools>fastboot devices
R32D202YHVP fastboot