Related
So what I would like for someone to help me with is to get the system.img for the first somehow on my the computer so i can flash it via ADB-Fastboot and get my phone to at least power up to the homescreen; this is because just a few days ago i was testing out some 'things' though they didn't work and decided to wipe the phone. The problem is that I erased EVERYTHING on the phone including system, etc. So now because the first doesn't have an sd card slot I cannot get a way to mount a rom and flash a new system.
All i ask for is a system.img or any tutorial that would work, (I've literally spent 2 nights looking for something but they aren't compatible with the first) using the RUU is out of the question because it's apparently encrypted and won't detect my phone since it just hangs on the facebook logo, also the system dumps on the forum that I've seen don't contain the system.img file. Thank you in advance for your help and troubles!
(note that I do not have a way to access ubuntu or any linux computer right now because of various reasons, what i do have is a spare first!)
What's stopping you from flashing a ROM from recovery? ADB push the ROM file into /sdcard from recovery.
The most common fix to get RUU working is to relock your bootloader. You can run RUU from fastboot.
killall-q said:
What's stopping you from flashing a ROM from recovery? ADB push the ROM file into /sdcard from recovery.
The most common fix to get RUU working is to relock your bootloader. You can run RUU from fastboot.
Click to expand...
Click to collapse
Well recovery works perfectly but there is no rom or file in the sd card at all because of the total system wipe, and ADB doesn't seem to detect my phone since it requires USB debbuging (or am i wrong?) and usb debugging isn't accessible since it hangs on the facebook logo. Only when it's in fastboot does it get recognized; but im not aware of a way to push the rom files through fastboot? I would very appreciate a tutorial if there is! that's why im looking for a system.img that i can flash using fastboot.
And as for the RUU I can't get to the Fastboot screen on the program because it first needs to confirm my phone model and system which it can't because it requires USB Debugging to be turned on on the phone. Also would relocking the bootloader still be necessary even though I have S-off?
About doing the ADB push through recovery to sd card, I don't see any option like that on the menu. I have CWM would I need TWRP for that?
USB debugging is only needed in the OS. In recovery you can do a lot of things even without root. ADB just has trouble detecting a device that's gone through a firmware change, just type "adb kill-server" and try again. You don't need to mount anything to push to /sdcard.
Do RUU as a last resort, since getting S-off again after relocking the bootloader is an elaborate process. But don't worry about the warnings. RUU will work when your phone is in fastboot, the first thing it does is reboot your phone anyway.
Does this help?
Hey everyone, so tonight I got the 4.4 ota on my N7, I am unlocked and rooted but stock everything including recovery.
After updating, my N7 keeps going to stalk recovery and that's it.
I know I can just reflash everything but I have a few very important files. Is there a way to reflash 4.3 without losing data or accessing the data partition while soft bricked so I can recovery my files?
I may be wrong, but can't you reflash your phone as long as you don't replace the userdata.img through fastboot to retain the same information? I could be wrong.
chrisinsocalif said:
I may be wrong, but can't you reflash your phone as long as you don't replace the userdata.img through fastboot to retain the same information? I could be wrong.
Click to expand...
Click to collapse
I'm not sure. I'd like to have this confirmed before I do anything. It's not urgent as the due date on my prgect isn't for another couple of weeks. But thanks. I'll look at that as a last resort.
Is it one file or multiple files you are trying to access? Have you tried to pull them using adb to your pc? I do not know how to do it, but I am sure there is a guide somewhere. Or try a phone backup using fastboot then unpack it on your desktop and get the files you need. Again, I am not good with phones, just throwing out idea's.
chrisinsocalif said:
Is it one file or multiple files you are trying to access? Have you tried to pull them using adb to your pc? I do not know how to do it, but I am sure there is a guide somewhere. Or try a phone backup using fastboot then unpack it on your desktop and get the files you need. Again, I am not good with phones, just throwing out idea's.
Click to expand...
Click to collapse
ADB or Wugs root kit don't see my Nexus 7 as it keeps rebooting to the dead droid and I know I don't have it set for debugging. Guess I'm screwed.
When you say "dead droid", you're referring to fastboot mode, right? (Android icon with a bunch of text below it, starting with "Fastboot Mode" in red.)
If you have fastboot, you can flash TWRP Recovery 2.6.3.0. Download it from Team Win's site (Google it). Then:
fastboot flash recovery openrecovery-twrp-2.6.3.0-grouper.img
fastboot reboot-bootloader
Use the Volume keys to select "Recovery Mode" and hit Power. Once you see the TWRP menu, you should have adb root access automatically. Connect tablet to USB, and use adb pull to download the contents of /sdcard:
adb pull /sdcard /dumphere
Replace "dumphere" with whatever directory you want to dump to. I'm sure there's better guides and explanations for this, but this is the quick version.
I guess you could reflash stock recovery afterwards, but I can't think of a reason why you'd want to. It's not like it's that useful.
As a rule of thumb, you should at least know how to get around a command line, and use adb and fastboot before mucking around with your tablet.
-XCN-
P.S. I could be mistaken, but I don't think internal storage (which is /sdcard, or /data/media) is overwritten when you flash a ROM. Obviously, backup first before trying.
I started to root my phone this morning. I did the HTVDev unlock, flashed twrp, then tried to flash viperboy's disable RW system protect. This caused my phone to just hang at the HTC screen. I let my phone die and was able to get into my bootloader and fastboot. I tried to push the rom via adb but I kept getting the error of no device connected. Then i tried to flash the stock boot.img though fastboot. This brought me back to the HTC screen but now when I plug it in to my computer it shows up for everything and it installs drivers but the HTC MTP Device fails. Now I cant send commands to reboot through fastboot or adb. Im currently waiting for it to die again to get back to twrp or the bootloader. Any advice on how to proceed?
Thanks,
Paris6906
Paris6906 said:
I started to root my phone this morning. I did the HTVDev unlock, flashed twrp, then tried to flash viperboy's disable RW system protect. This caused my phone to just hang at the HTC screen. I let my phone die and was able to get into my bootloader and fastboot. I tried to push the rom via adb but I kept getting the error of no device connected. Then i tried to flash the stock boot.img though fastboot. This brought me back to the HTC screen but now when I plug it in to my computer it shows up for everything and it installs drivers but the HTC MTP Device fails. Now I cant send commands to reboot through fastboot or adb. Im currently waiting for it to die again to get back to twrp or the bootloader. Any advice on how to proceed?
Thanks,
Paris6906
Click to expand...
Click to collapse
Likely no need to let it die -- a hard reset (hold the power and vol down for a very long time) should bring you back to the bootloader (hopefully). It'll seem like a good long while -- keep pressing.
From there, select 'fastboot' and press the power button, then plug in to your computer (USB). That'll show USB on the fastboot line.
Then, on your computer, open a command window (presuming you're using Windows) in the SDK platform-tools directory and type:
fastboot devices
If that gives back your device ID, you're at least at a reasonable fastboot. I'd flash a good recovery (I use PhilZ, and while it might be foreign to you (CWM style), it lets you load a ROM via OTG cable over USB if you have such a cable -- if not, hopefully sideload works for you in TWRP if you stick with that) -- just to be sure you have a good recovery.
Then, reboot into recovery.
Your kernel (boot.img) apparently is garbage, so hopefully you can either put a ROM on USB and flash from that (OTG) or adb sideload it. All the ROMs normally have a good kernel so would flash your boot.img properly during install. Were me me, I'd flash O.M.J's stock rooted ROM just so you at least get back to some place of sanity).
If that all fails, you might have to RUU and start over.
Let us know and we'll help out.
If that gives back your device ID, you're at least at a reasonable fastboot. I'd flash a good recovery (I use PhilZ, and while it might be foreign to you (CWM style), it lets you load a ROM via OTG cable over USB if you have such a cable -- if not, hopefully sideload works for you in TWRP if you stick with that) -- just to be sure you have a good recovery.
ok. can you use adb push in fastboot? also i noticed that my captive buttons blink when i tried to turn off my phone. don't know if that means anything.
OMG it worked! Thank you so much. I uber appreciate it. Today I learned a ton about how android works and how to use adb and fastboot. While the processed about gave me a heart attack i did learn a lot. I can not believe how great of a resource xda is. The knowledge of everyone on here is incredible. I cant thank you enough.
Thanks all,
Paris6906
I bought a Nexus6 about a month ago. I wasn't planning on rooting it, but I have rooted a number of devices in the past so am reasonably comfortable doing that. I bought the phone from Amazon but I am on T-mobile's network.
After I fired up the phone and used it for a while, I got a message asking me to update to software version 5.1. When I go to the about on my phone, it says it has 5.1.1 but it says the build number is LRX22C which when I looked that up indicates that it is actually running 5.0. I told the phone to update, but it fails every time (android guy with the red exclamation mark over his belly). I did a factory reset and repartition and still the same thing. At this point, I figured I would just root and and force it to 6.0.
After installing drivers, ADB-tools, etc. my computer recognizes the phone. When I connect by a USB cable and the phone is on, it shows under devices. However, when I boot into fastboot mode, my laptop no longer recognizes the Nexus. The fastboot screen shows that the phone is unlocked, and it recognizes that it is getting power from the laptop. However, it says to connect via usb. Running the command prompt and using SDK-Windows, when I type fastboot devices it shows nothing.
Interestingly, I see that Superuser is on the phone and working. I don't think I rooted my phone at any point in the process of trying a lot of different things, although anything is possible. I have been thrashing around a bit trying to get this to get the phone on 6.0 so might have rooted accidentally although I doubt it. My suspicion is that I was given a previously used phone that someone rooted and returned.
Any suggestions/help out there?
When in Fastboot Mode, what does Device Manager show? Does it see the device correctly, or is it showing a yellow triangle w/ exclamation point over the device?
RMarkwald said:
When in Fastboot Mode, what does Device Manager show? Does it see the device correctly, or is it showing a yellow triangle w/ exclamation point over the device?
Click to expand...
Click to collapse
It shows Other Devices > Fastboot Shamu S with the yellow triangle and exclamation point. I have motorolla device manager installed and I thought that had my drivers covered but perhaps not?
These devices do have driver issues. Try downloading the correct drivers and it should fix it, a lot of people have had similar issues.
@LSquared
Download Wugfresh Nexus Root Toolkit. It has a long button on the top right "Install and test drivers" - a really helpful guide in clearing out any old drivers and installing and testing the new ones.
It can also perform many other functions, but after a lot of persuasion(!) in these forums I decided that learning to do everything manually is not only simple but safer, because you know at exactly which point an error occurs. The driver setup part of NRT is a brilliant help in setting your PC up once to get you started.
If you don't have anything valuable on your device yet, install the MMB29S factory image, then TWRP, and from there install SuperSU v2.66, and you're as up to date as you can possibly be.
Spend a few hours doing research and you will be fine. Just stay away from root kits. They only make things worse and lessen the experience of owning a nexus. As well as stops any help you may get in the forums as no one will help those that use the root kits.
Thanks for all the help/suggestions. After a lot of poking around, I realized that I had the right driver hiding in a folder (inside SDK I think) and had to just manually point to them and that got rid of the connection issue. Now I seem to be stuck on flashing the latest stock OS. I have been trying to flash via Minimal ADB and Fastboot but it isn't pushing the image there correctly. I don't want a custom rom, just stock 6.0.
LSquared said:
Thanks for all the help/suggestions. After a lot of poking around, I realized that I had the right driver hiding in a folder (inside SDK I think) and had to just manually point to them and that got rid of the connection issue. Now I seem to be stuck on flashing the latest stock OS. I have been trying to flash via Minimal ADB and Fastboot but it isn't pushing the image there correctly. I don't want a custom rom, just stock 6.0.
Click to expand...
Click to collapse
How are you trying to push the files, I assume Fastboot, are you getting an error? Is your Android SDK up-to-date?
LSquared said:
I have been trying to flash via Minimal ADB and Fastboot but it isn't pushing the image there correctly. I don't want a custom rom, just stock 6.0.
Click to expand...
Click to collapse
Google updated fastboot a little over a year ago to allow flashing the very large system.img files. Minimal ADB & Fastboot does not have this update (I believe). Download the latest Android SDK and you'll be good to go.
cam30era said:
Google updated fastboot a little over a year ago to allow flashing the very large system.img files. Minimal ADB & Fastboot does not have this update (I believe). Download the latest Android SDK and you'll be good to go.
Click to expand...
Click to collapse
I just downloaded Android SDK so it has the latest files (I believe). Android SDK doesn't connect to the phone, it just keeps an updated set of firmwear, right? If I am not using minimal ADB and fastboot to push files from my computer to the phone, what program should I be using? It seemed a lot easier on my older phones that had a micro SD card because I could just drop the new Rom on there and install that from the bootloader.
LSquared said:
If I am not using minimal ADB and fastboot to push files from my computer to the phone, what program should I be using?
Click to expand...
Click to collapse
Use the ADB and fastboot that are included with the Android SDK that you downloaded. They are in the Platform-Tools folder.
cam30era said:
Use the ADB and fastboot that are included with the Android SDK that you downloaded. They are in the Platform-Tools folder.
Click to expand...
Click to collapse
If I click on either of those to run the application, it flashes a box for a split second and then nothing. I guess I am missing a step?
LSquared said:
If I click on either of those to run the application, it flashes a box for a split second and then nothing. I guess I am missing a step?
Click to expand...
Click to collapse
I would suggest reading and following this guide >http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot
cam30era said:
I would suggest reading and following this guide >http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot
Click to expand...
Click to collapse
That guide is great and helped me get the bootloader unlocked and the phone rooted. I downloaded the image file just fine, but when I go to run root-windows.bat I get the message "fastboot is not recognized as an internal or external command." I am guessing I don't have some file in the right location?
LSquared said:
That guide is great and helped me get the bootloader unlocked and the phone rooted. I downloaded the image file just fine, but when I go to run root-windows.bat I get the message "fastboot is not recognized as an internal or external command." I am guessing I don't have some file in the right location?
Click to expand...
Click to collapse
The flash_all scripts don't work. Flash each img file individually, after you've extracted them all from the ,zip.
Yup, flash the .img files individually, the batch command doesn't work.
Here's the guide I always use: How to manually flash img files to your Nexus device
Basically, with phone connected to computer and booted to the bootloader, open Command Prompt window, change directories to where your sdk/platform-tools directory is with your Shamu files, then:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
Code:
fastboot flash bootloader "name of bootloader"
fastboot reboot-bootloader
Code:
fastboot flash radio "name of radio"
fastboot reboot-bootloader
NOTE: You'll have to extract the files from the image-shamu-mmb29s.zip file in this case to flash MMB29S.
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
Code:
fastboot reboot
I'm aware, it may be overkill, but I've never had any issues performing all of these steps to get back to 100% stock so if it "isn't broken, don't fix it". Also this will wipe your internal SD area, so any files you want to save you should save them prior to starting this.
Good summary!
RMarkwald said:
Also this will wipe your internal SD area, so any files you want to save you should save them prior to starting this.
Click to expand...
Click to collapse
To avoid wiping your internal user storage, just skip the step that flashes userdata img (and the step at the beginning that erases usedata)
Ok..so here's the situation. I was going to install a new ROM ( my son got a new phone a iphone ) but any ways. As I was in TWRP i did everything we all normally do but the phone died mid flashing GAPPS. when i went to pulg the phone to the charger and restart the phone i see that it started to boot up the it jumped straight to FASTBOOT and it's stuck. I can toggle through fastboot but that is it. when i go to restart it will show the boot animation but then goes to fast boot. it wont go to TWRP nothing. I've combed XDA and found the multi tool but don't think that is working or i might be using it wrong. the computer doesn't recognize the phone. im trying to get this phone back up and going and give to my daughter . any help is greatly appreciated. thank you in advacne.
Here's what I'm talking about just in case someone asks
Try installing a stock factory image from fastboot.
runekock said:
Try installing a stock factory image from fastboot.
Click to expand...
Click to collapse
How...I can't get my computer to recognize the phone... When I plug it in it doesn't read it...I should have the drivers already installed...adb push right.... I'll search for the command to see if it finds the phone
adb never works in fastboot mode. You'll have to use the fastboot command.
On the PC, try
fastboot devices
to see whether the phone is available. If not, check your drivers - I believe that fastboot uses a different USB driver.
With fastboot, you can't install zip-files, only image files. So download the stock factory image, not the OTA.
runekock said:
adb never works in fastboot mode. You'll have to use the fastboot command.
On the PC, try
fastboot devices
to see whether the phone is available. If not, check your drivers - I believe that fastboot uses a different USB driver.
With fastboot, you can't install zip-files, only image files. So download the stock factory image, not the OTA.
Click to expand...
Click to collapse
Thanks for the heads up I'll definitely be trying this and I'll give you an update soon