Related
well i happened to have some problems with a theme i was using that made the icons appear themed even in cyanogens roms , and i was told that i needed to flash the htc adp image to fix that
the problem comes here i flashed the htc adp image but i forgot to read what cyanogen said that i had to flash his rom before rebooting
so i just found that cyanogen gives us something to follow just in case it happens what happened to me here http://wiki.cyanogenmod.com/index.php/RE-recovery-img
i went to ''if you currently have an engineering or a Hard SPL'' and followed all the procedures until i got to number 4 where it asks me to Change directory to where you have saved your recovery image..i've tried lots of paths but none seems to work...ADB NOOB HERE so please help
when you didnt follow the process, you lost root.
you have to start from scratch.
.............................................................................
i typed
cd C:\recovery-RA-dream-v1.5.2.img
and it tells me the directory name is invalid what am i doing wrong?
recovery image is not a directory, it'a file. What are you trying to do?
borodin1 said:
recovery image is not a directory, it'a file. What are you trying to do?
Click to expand...
Click to collapse
im trying to flash amon ra recovery via fastboot
Easier to do it from adb
Code:
adb remount
adb shell flash_image recovery C:\recovery-RA-dream-v1.5.2.img
reboot
Just a tip: I usually rename files into something easier to type, like ra152.img. Up to you though.
You can also do it from terminal (place file on the root of sdcard)
Code:
su
flash_image recovery /sdcard/filename.img
reboot
If you must do it via fastboot
Start your phone in fastboot mode (camera/power)
Code:
fastboot flash recovery recovery-RA-dream-v1.5.2.img
fastboot reboot
borodin1 said:
Easier to do it from adb
Code:
adb remount
adb shell flash_image recovery C:\recovery-RA-dream-v1.5.2.img
reboot
Just a tip: I usually rename files into something easier to type, like ra152.img. Up to you though.
You can also do it from terminal (place file on the root of sdcard)
Code:
su
flash_image recovery /sdcard/filename.img
reboot
If you must do it via fastboot
Start your phone in fastboot mode (camera/power)
Code:
fastboot flash recovery recovery-RA-dream-v1.5.2.img
fastboot reboot
Click to expand...
Click to collapse
i would do this..but i cant since i messed up when flashing the htc adp image im following cyanogens tutorial http://wiki.cyanogenmod.com/index.php/RE-recovery-img and it says that i have to flash the new recovery through fastboot , and the part im stuck at is step 4 where he says that i need to Change directory to where you have saved your recovery image
if you can get into the main phone operating system via a boot up then use linda file manager to move them
when i type this
fastboot recovery recovery-RA-dream-v1.5.2.img
i get this message "error: cannot load 'recovery-RA-dream-v1.5.2.img
then i changed the directory to where the recovery image was and when i tried to flash i got this message
'fastboot' is not recognized as an internal or external command, operable program or batch file
Not sure, I'm not anywhere near my computer. Try putting your recovery image into different locations (i always put it on desktop) and rename it to something simpler, without any punctuation or special characters (i suggest rec.img). Also... make absolutely sure that you're NOT naming it rec.img.img . Make sure that your PC is not hiding your extensions.
Then, connect your phone to the computer, start your phone in fastboot mode (not Hboot or serial, if you see serial or Hboot on your screen then tap return button)
In command line type
Code:
fastboot devices
to make sure that you're connected
then type
Code:
cd desktop
your directory should change to something like C:\user\desktop (make SURE there are no spaces anywhere in user name, fastboot has problem with that. I had to rename my account to "EugeneAndLiz"a from "Eugene and Liza" because of that)
then type
Code:
fastboot recovery rec.img
fastboot reboot
and let us know how did it go for you. I'l be lurking around here for a while, hopefully we can resolve this.
Good luck
borodin1 said:
Not sure, I'm not anywhere near my computer. Try putting your recovery image into different locations (i always put it on desktop) and rename it to something simpler, without any punctuation or special characters (i suggest rec.img). Also... make absolutely sure that you're NOT naming it rec.img.img . Make sure that your PC is not hiding your extensions.
Then, connect your phone to the computer, start your phone in fastboot mode (not Hboot or serial, if you see serial or Hboot on your screen then tap return button)
In command line type
Code:
fastboot devices
to make sure that you're connected
then type
Code:
cd desktop
your directory should change to something like C:\user\desktop (make SURE there are no spaces anywhere in user name, fastboot has problem with that. I had to rename my account to "EugeneAndLiz"a from "Eugene and Liza" because of that)
then type
Code:
fastboot recovery rec.img
fastboot reboot
and let us know how did it go for you. I'l be lurking around here for a while, hopefully we can resolve this.
Good luck
Click to expand...
Click to collapse
im going to tell you step by step what i do
turn the phone off
hold power and back
i see the androids on skateboards and it says fastboot in red letters
i connect my phone via usb then the name changes to fastboot usb
run the cmd
once there i type where adb is located which is cd C:\android-sdk-windows\tools
then when i type fastboot devices
i see the serial number of my phone
now when i type cd desktop i get this message "the system cannot find the path specified"
and if i ignore that and try to flash
fastboot flash recovery rec.img (yes i did rename the recovery image)
it says that it cant load 'rec.img'
Got it! Put your image file into the "tools' folder and once you see your device in the fastboot just flash it from there
Code:
cmd
cd C:\android-sdk-windows\tools
fastboot devices
fastboot flash recovery rec.img
fastboot reboot
Sorry about all this complication... the main idea is that your recovery needs to be in the same directory as you're when you're flashing. So if earlier you went to tools folder then your file needs to be there as well.
Try it out.
it worked...it said sending 'recovery' <4456 KB>... okay
writting 'recovery'...okay
fastboot reboot
then when i go to the system recovery..its the same htc adp one
i tried to flash amon ra's recovery and cyanogens
oh nevermind..instead of rebooting the phone i just unpluged the device and wnet directly into the system recovery and YES i have cyanogens recovery thank you so much borodin1
hmmmm that's weird because you got confirmation....
1. Did you download right recovery? You had to becaue you tried 2 of them and you can only make the same mistake once lol
2. AmonRA's recovery has the same image in the background as HTCs, are you sure that it's still HTC's recovery?
Other then that... I'm clueless
Can you get su in the adb shell? Try flashing it from adb....
You got me stomped on this.... Anyone else wants to take a shot at this????
i dont know what happened but when i flashed the recovery image on fastboot and then rebooted the phone...then turn off the phone and went to the system recovery and the htc adp recovery appeared...blue letters and the scrolling options..but when i did not reboot the phone after flashing the image and went directly to the system recovery i had the recovery i flashed...then i applyed the updateand everything is good now
weird uh?
will that new recovery stick?... I'm starting to remember something but it's vague... give me few minutes Reboot couple of times into recovery and back for now and see what happens...
it did stick..i just rebooted into recovery and i have the new recovery..haha
Great! Happy modding!
I installed the new zen2.2 rom today and had a working clockwork recovery. Here is where I went stupid, I downloaded the kernel update but rather than running it via update.zip I flashed it using flash_image recovery via adb shell.
Now my phone comes up to fastboot usb and never goes any further, been waiting hours! I have tried booting into fastboot/hboot and it does nothing. I have booted to hboot before successfully but now nothing.
If I run adb devices it shows no devices. If I run fastboot devices it does show my device.
Whats next?
If you cant get into fastboot and you cant get into recovery then you m ight have bricked your phone. Did you try a hard reset?
How do you do a hard reset?
Here is a little more info. I believe it does actually get to fastboot usb as it says so on the top left of the screen and I can run fastboot commands but most commands say error. If I do fastboot devices it shows the device connected.
Little more info - when I try doing a back to basics RUU update it connects, shows the rom version, starts the update and then at about 88% every time, it goes right to a error [171] usb connection error. So its communicating but never finishes. Tried with the sprint RUU stock rom, another that was built by one of the devs in the Hero community and still both do the same.
I'm pretty sure you can flash a custom recovery from fastboot. Using something like fastboot flash xxx dont quote me on this but it sounds like you have a soft brick and you just need to get a recovery back on the phone. From there you can then flash and rom back on the phone. Do some research on flash a recovery from fastboot.
ASimmons said:
I'm pretty sure you can flash a custom recovery from fastboot. Using something like fastboot flash xxx dont quote me on this but it sounds like you have a soft brick and you just need to get a recovery back on the phone. From there you can then flash and rom back on the phone. Do some research on flash a recovery from fastboot.
Click to expand...
Click to collapse
Right, I also believe that if I could get a recovery back on the phone I would be good as gold! Here is the problem though. I have tried running "fastboot flash recovery [recovery.img]" but it gives me the below error. I have tried multiple key combination's to get into hboot but nothing works. If anyone has any other key combination's I could try please let me know!
Code:
D:\android-sdk-windows\tools>fastboot flash recovery recovery.img
sending 'recovery' (3720 KB)... FAILED (remote: not allow)
finished. total time: 0.001s
1st:The ONLY time you use flash_image recovery is when you are installing a recovery console, NOT a kernel
If you notice the kernel is in a signed .zip folder. When you use flash_image command it needs to be .img file
2nd: Put the recovery image on your sdcard
Put it in the tools folder of AndroidSDK and do
Code:
adb push recovery.img /sdcard
Now type in
Code:
$ adb shell
$ su
# flash_image recovery /sdcard/recovery.img
unCoRrUpTeD said:
1st:The ONLY time you use flash_image recovery is when you are installing a recovery console, NOT a kernel
If you notice the kernel is in a signed .zip folder. When you use flash_image command it needs to be .img file
2nd: Put the recovery image on your sdcard
Put it in the tools folder of AndroidSDK and do
Code:
adb push recovery.img /sdcard
Now type in
Code:
$ adb shell
$ su
# flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
Yeah I think he knows now not to flash kernels... atleast I hope so. +1 for your post.
unCoRrUpTeD said:
1st:The ONLY time you use flash_image recovery is when you are installing a recovery console, NOT a kernel
If you notice the kernel is in a signed .zip folder. When you use flash_image command it needs to be .img file
2nd: Put the recovery image on your sdcard
Put it in the tools folder of AndroidSDK and do
Code:
adb push recovery.img /sdcard
Click to expand...
Click to collapse
I am fully aware of how the how-to's and what not to do's. Like I said, it was a mistake, call it a bit of anxiety due to the new 2.2 rom that I was trying to get installed. I did it too quick and without much common sense .
Now type in
Code:
$ adb shell
$ su
# flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
For the second part, I am unable to do anything with adb as my computer does not see the phone. When running adb devices it is not listed. Only command that sees my phone is fastboot devices, but again I am unable to run anything aside from that due to previous error.
casualonejp said:
I am fully aware of how the how-to's and what not to do's. Like I said, it was a mistake, call it a bit of anxiety due to the new 2.2 rom that I was trying to get installed. I did it too quick and without much common sense .
For the second part, I am unable to do anything with adb as my computer does not see the phone. When running adb devices it is not listed. Only command that sees my phone is fastboot devices, but again I am unable to run anything aside from that due to previous error.
Click to expand...
Click to collapse
First do you have the eng spl, does your hoot say s (on)
Have you tried that command but point it to the sdcard? Also do you have any files on your sdcard like say a recovery.img or an update zip. If you don't you might need to manually move the file to it and try some of these commands
fastboot update /sdcard/<imagepackage>.zip [-w] -w will wipe the cache and the user/data
or your previous flash recovery but with the file pointing to the file on the sdcard
edit: sorry i dont think fastboot will see the sdcard but try anyways.
ASimmons said:
First do you have the eng spl, does your hoot say s (on)
Have you tried that command but point it to the sdcard? Also do you have any files on your sdcard like say a recovery.img or an update zip. If you don't you might need to manually move the file to it and try some of these commands
fastboot update /sdcard/<imagepackage>.zip [-w] -w will wipe the cache and the user/data
or your previous flash recovery but with the file pointing to the file on the sdcard
Click to expand...
Click to collapse
I will try the fastboot command right now. I am unable to get to hboot with any of the key combination I have tried, before I was able to. Only thing that always comes up is the HTC white screen with fastboot usb at the top left. Can't see what hboot version or anything else I have due to that limitation.
casualonejp said:
I will try the fastboot command right now. I am unable to get to hboot with any of the key combination I have tried, before I was able to. Only thing that always comes up is the HTC white screen with fastboot usb at the top left. Can't see what hboot version or anything else I have due to that limitation.
Click to expand...
Click to collapse
After reading a bit you should be able to do something like i described
- copy amon_ra image to yor sd
- flash_image recovery /sdcard/name-of-recovery.img
hopefully you have a way to copy the files to your sd card like say a microsd card converter and stick it in your comp. Or I have had to use a freaking camera once for my g1 after being in a similar situation.
edit: ok so maybe you wont be able to if you spl is in s-off mode.
if you can access your card and see if you have nadroids you could also try this
fastboot flash system /path/to/nandroid/system.img
fastboot flash boot /path/to/nandroid/boot.img
fastboot flash userdata /path/to/nandroid/userdata.img
fastboot reboot
hopefully you have these backed up on your puter to.
ASimmons said:
After reading a bit you should be able to do something like i described
- copy amon_ra image to yor sd
- flash_image recovery /sdcard/name-of-recovery.img
hopefully you have a way to copy the files to your sd card like say a microsd card converter and stick it in your comp. Or I have had to use a freaking camera once for my g1 after being in a similar situation.
edit: ok so maybe you wont be able to if you spl is in s-off mode.
if you can access your card and see if you have nadroids you could also try this
fastboot flash system /path/to/nandroid/system.fimg
fastboot flash boot /path/to/nandroid/boot.img
fastboot flash userdata /path/to/nandroid/userdata.img
fastboot reboot
hopefully you have these backed up on your puter to.
Click to expand...
Click to collapse
Negative on the fastboot commands. Also did have a nandroid but on old sdcard which died. I read that I could use anothers nandroid backup but I am currently trying to find one to test.
Tried doing the RUU method with stock/custom roms and it gets as far as seeing the image but when I click on "ok" to start the recovery, it goes to "waiting on bootloader" and then at 88% it errors to a 171 error stating usb connection error.
I would do some research its my understanding that you can't be bricked since you can get into spl. You should be able to put an .img file on your sd card and flash it. Sorry I can give you any more input.
ASimmons said:
I would do some research its my understanding that you can't be bricked since you can get into spl. You should be able to put an .img file on your sd card and flash it. Sorry I can give you any more input.
Click to expand...
Click to collapse
Ya I have been researching non stop all yesterday evening and today so far all day. I just cant get it to do anything. I will keep researching though. Thanks
Did you fix this yet?
Anyone figure this out yet...I have the same issue and haven't been able to resolve it yet. Still with a brick at this point!
Hey guys,if your stuck at fastboot(As I just was tonight), try in your CMD(if running Windows) fastboot reboot-bootloader or fastboot reboot to reboot as normal,I'll try to keep you updated to get through all this. I am at a loss right now but searching for answers first before i go about asking.
Answer to MY problem(maybe not yours): OK,I have come to the conclusion here tonight that I had a soft brick. What I did was remove the battery,put the battery back in,restarted the phone normally,then I ran the HTC Sprint Hero MR 2.27.651.6 on my computer(essentially restoring back to unrooted factory settings). This worked for me. I am totally refreshed and happy that my phone is ok and all. Yes I may have to go back and re-root but this only take me bout 20 minutes most to root and re-flash a CyanMod7 Nightly Rom. Hope my info can help out somebody!
I accidentally erased all data using recovery. Now I only have access to fastboot and recovery mode. Systems indicate i do not have any OS installed. I can't seem to hook up the phone to pc so that i can transfer the .zip file so that i can flash. I know there is a way to fastboot flash a rom but the instuctions provided is not working somehow. Phone is just stuck on white window. If someone could give me a hand I would appreciated.
i got it.
ADB Push file.zip /sdcard/
those of you who are stupid like me and deleted all the data on the phone. LOL.
Here is the story in a nutshell I flashed xdabbeb's bootstack, then his rom. Then I did something stupid such as wipe everything folks, I mean everything. So my phone then restarted and I am able to get into recovery twrp 2.7.
I have tried in twrp to sideload, mount neither which work.
I have my drivers installed it says in device manager when I plug the phone up for download mode
android- galaxy nexus adb
and under ports it says LGE AndroidNet for VZW ADB Interface com41
I tried lg flash tool, tried with old vs98010b rom
pid:
imei:
model:
dll: vs980
bin: vs98010b_13.tot
swv:
swov:
model information check fail!
00000000
I really need help guys, are there any adb commands I can type or are there any drivers I need to install
Ok when i hold the up and plug in it takes me to fastboot
[500] fastboot mode started
[550] udc_start()
[720] reset
[730] portcharge
[740] reset
[750] portcharge
and the device only registers as android under other on my computer
i've installed lg drivers
How can you fastboot flash? When I hold up and plug in for fastboot my computer wont register a driver just shows android what are the commands and how do I use fastboot
timenewton said:
How can you fastboot flash? When I hold up and plug in for fastboot my computer wont register a driver just shows android what are the commands and how do I use fastboot
Click to expand...
Click to collapse
Download mode is not going to work because the laf partition (this allows for download mode to work) is wiped when you flash xdabbeb's bootstack in favor of fastboot mode.
I suggest you pm xdabbeb; he will guide you on the steps to using the necessary fastboot commands to get your phone working again. He's already helped a few people that were in the same situation as you are in right now.
Fastboot is good because you can write certain partitons at a time without having to .tot and wipe your whole phone.
You could also flash his xdabbeb_vs98024a_laf.zip http://www.androidfilehost.com/?fid=23329332407586639 file in TWRP 2.7 to restore download mode, but you will end up wiping your whole phone by using the LG Flash Tool, even your sd card when you restore your phone.
You said you "wiped everything", I'm not sure if that means your sd card too, if so, then that might be the easiest thing to do since you still have access to recovery. You will need an otg cable and a flash drive to mount the flash drive in TWRP 2.7 and flash the file, unless you can side load the file with adb.
Either way, like I mentioned earlier, it might be a good idea to pm xdabbeb first.
Hey my phone is already wiped even sdcard, but the thing is i cant flash that file because I can not get it on my phone. So ill ask xdabbeb the fastboot commands. Yeah and I read about the otg cable, ordered one of those babies should be here this saturday and hopefully it will mount my flash drive in that case id be golden untill then ill see what mr xdabbeb has to say.
cant sideload
everytime i try to sideload the file it just says cant read file or something like that
And I really appreciate you responding. Always nice to get support from somebody when your just sitting here and your phone seems like it hasnt been working for an eternity. Almost depressing not hearing from anyhbody and just seeing all the views but no replys. Thank you
Hey there...Fastboot is about as basic/simple/reliable as it comes. If you have adb/fastboot set up properly then command is:
fastboot flash <partition> <filename>
for example:
fastboot flash recovery recovery.img
In your case, you claim to have a working recovery (twrp 2.7), but are unable to copy files from your computer to your phone. It sounds like you don't have the proper drivers installed so that you can use adb from recovery. This is a common/known issue with windows and I believe I replied to you in the rom thread already about this, but you need to install/use Koush's universal adb driver and simply copy the rom file over to your phone using the following command:
adb push <filename> /sdcard/
After you have the file there you can flash it as normal in recovery.
If you want to use a kdz/tot method to restore your phone, just download the laf zip file from my thread, extract the laf.img file from the zip, and use the following command to put it in place:
fastboot flash laf laf.img
Then you can go about the tot restore method described in the thread here. You don't need to put the tot file itself on your phone. It just needs to be on your computer.
I get to sdk and open cmd
type adb devices it says
List of devices attached
0215817d960ce580 sideload
Then I type adb push rom.zip /sdcard/
error: closed
When phone is plugged in for adb device manager says under android device- Google galaxy Nexus ADB Interface
I have universal drivers installed and I goto device manger to update drivers where clockworkmod is installed and it doesnt do anything
Fastboot it says in other devices in device manager
Android
PCI Data Acquisition and Signal Processing Controller
I type fastboot flash recovery laf.img
<waiting for device>
timenewton said:
I get to sdk and open cmd
type adb devices it says
List of devices attached
0215817d960ce580 sideload
Then I type adb push rom.zip /sdcard/
error: closed
When phone is plugged in for adb device manager says under android device- Google galaxy Nexus ADB Interface
I have universal drivers installed and I goto device manger to update drivers where clockworkmod is installed and it doesnt do anything
Fastboot it says in other devices in device manager
Android
PCI Data Acquisition and Signal Processing Controller
I type fastboot flash recovery laf.img
<waiting for device>
Click to expand...
Click to collapse
Wait, I'm confused here a little bit. Are you trying to do sideload mode in TWRP or are you using fastboot mode?
And the command you typed is not correct fastboot flash recovery laf.img...you don't want to do that...this would flash the laf.img in your recovery partition.
xdabbeb referenced two methods to you...one was pushing a Rom to your sdcard and then flashing that Rom in TWRP to get your phone booting...the other was to flash the laf.img file and do a .tot if that's what you prefer.
It seems like you want to do a .tot restore, so do the second method xdabbeb suggested.
Get into fastboot mode and type fastboot flash laf laf.img
Make sure you use the correct laf.img...you can extract it from the zip in my previous post/link.
After this your download mode should be working again.
I was trying either one
For fastboot I downloaded xdabbebs laf
the image file in his file is laf.img, if thats not the right file then where is the recovery.img
So the recovery.img would have been one that i made?
and laf is so I can us lg tool to tot flash?
Even when i try to flash the laf it keeps saying waiting for device. I have the drivers koushu installed and lg
timenewton said:
I was trying either one
For fastboot I downloaded xdabbebs laf
the image file in his file is laf.img, if thats not the right file then where is the recovery.img
So the recovery.img would have been one that i made?
and laf is so I can us lg tool to tot flash?
Click to expand...
Click to collapse
Yes, download xdabbeb's laf.img, it's the link I gave you originally. You will have to take out the laf.img file from the zip file that is called xdabbeb_vs98024a_laf.zip
The recovery command he gave was just an example, there was no need for you to use it.
Yes, flashing the laf.img will fix your download mode and you will be able to do the .tot method.
What am I suppose to do about it saying wiating for device, its not detecting it
timenewton said:
What am I suppose to do about it saying wiating for device, its not detecting it
Click to expand...
Click to collapse
That sounds like a driver issue. Reboot your computer and turn off the phone and start again. See if that helps. You can also remove the drivers and re-install...I suggest you reboot your computer every time you install new drivers.
EDIT:
Are you using a newer adb.exe from your android sdk? If you have ioroot25 installed on your computer I suggest you use the folder/files from there. It has a newer adb.exe in there; put your laf.img file in that folder too if you do use that instead, and run the command prompt from within that folder.
Ok when my phone is plugged into my comp, im on win 7 it shows up as android under other devices when started in fastboot mode. When I browse to the driver location to load for the android it says no driver found for it.
Yes i just installed the sdk like 2 days ago so I know its current.
As far as the driver situation, why would I need to uninstall if it isnt even installing a driver.
This is terrible
timenewton said:
Ok when my phone is plugged into my comp, im on win 7 it shows up as android under other devices when started in fastboot mode. When I browse to the driver location to load for the android it says no driver found for it.
Click to expand...
Click to collapse
timenewton said:
Yes i just installed the sdk like 2 days ago so I know its current.
As far as the driver situation, why would I need to uninstall if it isnt even installing a driver.
This is terrible
Click to expand...
Click to collapse
For me it shows up under "ADB Interface", but I don't have the universal driver installed.
I didn't realize it wasn't installing the driver for you.
You have to get that driver going or you won't be able to get your phone fixed. Maybe try a different usb port or a different computer.
Man yeah mine doesnt look at all like that. Im uninstalling lg driver and universal one and clearing temp folder. Then restart and reinstall maybe that will work. So its just the koushu driver that works for fastboot and adb right?
timenewton said:
Man yeah mine doesnt look at all like that. Im uninstalling lg driver and universal one and clearing temp folder. Then restart and reinstall maybe that will work. So its just the koushu driver that works for fastboot and adb right?
Click to expand...
Click to collapse
Yeah, it should work. I've read posts by others stating that it works.
Yep just reinstalled the universal drivers, plug phone up into fastboot and still get the same result
Can you perhaps send me that driver you have? Because I know if you have that one and it works for you it SHOULD work for me. Murphs law is killing me. I can pm you my email address
Hello guys, ive been generally lucky in the sense that i have had no issues...until now.
I have tried installing the most recent updates (7.0, and now 7.1.1) and i continue to get this error through cmd. It does not seem to want to flash anything, and i have gotten it to flash, root, and twrp, but it still acted funky. Today, trying to remedy the situation, i attempted to flash the new 7.1.1 update, and return to stock (to later return to power user) but it is still doing it.
It says Bootloader: has-slot (not found), and a couple other things. When i try to flash individual pieces, it does not retain it. when i try to flash the flashall.bat, it flashes but does not flash everything, it will say the stuff has transferred 0 and skips it as it looks like. I cannot get my bootloader off the october one, and i have looked everywhere i can to try to fix this.. please help, its driving me mad. I will be happy to provide any information needed.
Thanks Community! You rock!
Have you tried a different USB cable? A different computer? How about a different USB AND a different computer? I think this would be a good place to start.
Can i ask you why this would matter? My usb seems to work fine, and my computer had no issues before this... i can still perform different actions, and my phone is showing up as ADB and Fastboot.
If it's not pc or usb cable related you can try to flash latest factory image step by step via fastboot without your simcard
Well, you might want to post the complete output of your flashing attempt, but if the bootloader slot isn't found, that's usually a sign of a hardware problem. Hopefully I'm wrong, but until we see more from you, I simply don't have an answer for you.
Ive tried to fastboot everything individually, and it refuses to take. I tried the flashall, same thing. I used NRT and it partially worked, but has sorta the same error. I will be flashing again and providing screenshots right now. I was able to get into a rom, root, twrp but i still cannot update all of those core things (bootloader, radio, and such) Thank you guys for the help. Much needed.
Here is the attempt to just flash the bootloader, i have tried from a different location but this is directly in Platform-Tools of the SDK. As you can also see, it does register under fastboot...
Try to flash radio and bootloader via twrp
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Did you try without simcard?
coremania said:
Try to flash radio and bootloader via twrp
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Did you try without simcard?
Click to expand...
Click to collapse
yes i have, i only do it with the simcard removed. Now whats weird is it says my bootloader is on 72.01, but my cmd clearly tells me its not working correctly...
coremania said:
Try to flash radio and bootloader via twrp
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Did you try without simcard?
Click to expand...
Click to collapse
I just tried what you suggest, and im not sure if it worked. It said everything wrote (on twrp) but it was very quickly done. I feel it did the same thing as CMD did.
You could try using the correct Fastboot command...
fastboot flash bootloader bootloader.img
The command is fastboot flash <partition> <image>
Your screenshot says only "fastboot flash image" but doesn't state the partition you're trying to load, hence "unknown partition".
And since we're on the subject, perhaps a repetition of the procedure I used to use before the full OTA days might be useful to you and other people.
Preparation.
- Take a TWRP backup and save it on your PC.
- Download factory image (https://developers.google.com/android/nexus/images#shamu) and unzip all files, including the zip within the zip. Rename the *.img files to the names below. Copy all of them to the same folder as your ADB/fastboot executables.
- Download the relevant TWRP and rename to twrp.img - also put in ADB/fastboot folder.
- Copy SuperSU to device (if root wanted).
- Set USB debugging in Developer options & attach to your PC.
- Open a CMD window, navigate to your ADB folder, and check connectivity with "adb devices". If it's ok, copy & paste each command below into the CMD window and run them - the only lengthy one is the system.img.
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash superSu
dahawthorne said:
You could try using the correct Fastboot command...
fastboot flash bootloader bootloader.img
The command is fastboot flash <partition> <image>
Your screenshot says only "fastboot flash image" but doesn't state the partition you're trying to load, hence "unknown partition".
And since we're on the subject, perhaps a repetition of the procedure I used to use before the full OTA days might be useful to you and other people.
Preparation.
- Take a TWRP backup and save it on your PC.
- Download factory image (https://developers.google.com/android/nexus/images#shamu) and unzip all files, including the zip within the zip. Rename the *.img files to the names below. Copy all of them to the same folder as your ADB/fastboot executables.
- Download the relevant TWRP and rename to twrp.img - also put in ADB/fastboot folder.
- Copy SuperSU to device (if root wanted).
- Set USB debugging in Developer options & attach to your PC.
- Open a CMD window, navigate to your ADB folder, and check connectivity with "adb devices". If it's ok, copy & paste each command below into the CMD window and run them - the only lengthy one is the system.img.
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash superSu
Click to expand...
Click to collapse
hahahaha well that could surely be the issue :silly:, but the one thing im wondering is why it wouldnt work through NRT, and i also "successfully" sideloaded the ota... Gonna try this now and hopefully it works! I shall report back when finished
dahawthorne said:
You could try using the correct Fastboot command...
fastboot flash bootloader bootloader.img
The command is fastboot flash <partition> <image>
Your screenshot says only "fastboot flash image" but doesn't state the partition you're trying to load, hence "unknown partition".
And since we're on the subject, perhaps a repetition of the procedure I used to use before the full OTA days might be useful to you and other people.
Preparation.
- Take a TWRP backup and save it on your PC.
- Download factory image (https://developers.google.com/android/nexus/images#shamu) and unzip all files, including the zip within the zip. Rename the *.img files to the names below. Copy all of them to the same folder as your ADB/fastboot executables.
- Download the relevant TWRP and rename to twrp.img - also put in ADB/fastboot folder.
- Copy SuperSU to device (if root wanted).
- Set USB debugging in Developer options & attach to your PC.
- Open a CMD window, navigate to your ADB folder, and check connectivity with "adb devices". If it's ok, copy & paste each command below into the CMD window and run them - the only lengthy one is the system.img.
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash superSu
Click to expand...
Click to collapse
Unfortunately, it did not work. Now google app keeps crashing. Phone is extremely buggy.
Calko2882 said:
Unfortunately, it did not work. Now google app keeps crashing. Phone is extremely buggy.
Click to expand...
Click to collapse
Can you give a bit more detail? So the phone is crashing, but is it now on the version that you wanted to have (7.0, 7.1.1)? There is rarely such a thing as "too much information".
dahawthorne said:
Can you give a bit more detail? So the phone is crashing, but is it now on the version that you wanted to have (7.0, 7.1.1)? There is rarely such a thing as "too much information".
Click to expand...
Click to collapse
Ok, so what happens is that it says i am on 7.1.1 with i guess the related info, but it does not load in properly as you can see with the screenshots. I start up the initial setup, and i can get through most of it fine, but some areas *permissions* are all blotchy. like i can toggle them on to submit data but i cant see what it is exactly im agreeing to. Then i start the phone, Google App automatically crashes, along side system ui. When i updated them, it seemed to fix the problem. But the issue is, i am not receiving phone calls and texts until possibly days later, and when i send texts it says "sending" and proceeds to spam the hell outta whoever its going to (sends literally 30+ texts). When i call someone, my phones Do Not Disturb mode gets enabled, and then nicely cuts out my audio. I can turn this feature off when im in the call, but sometimes it will then glitch the phone app, and i cannot essentially "hangup". My phone also now dies at 9%, where it had not previously (when i was on other rom / older stock) This all started after i updated to the october patch, and i noticed in december that i didnt have the december patch / update. I went to install it, and the same exact thing occurred. Ive attempted a rescue ota, and a sideload ota, and now this stuff as well, but i fear the worst for my phone. Let me know if i need to add anything else
Strephon may be right in suggesting a hardware fault, but equally it may just be that your phone is now somehow corrupted. My only suggestion is that you nuke it - factory reset, TWRP, wipe everything again in TWRP, and then try installing from fresh using the 7.1.1 full (not OTA) image and the instructions I posted earlier. If it still doesn't work I'm out of ideas, but there are people with far greater experience here than I have, so don't give up. It's too nice a device to just write off.
Calko2882 said:
When i call someone, my phones Do Not Disturb mode gets enabled
Click to expand...
Click to collapse
That's a new feature of 7.1.1. So you won't have to listen to notifications while on the phone. It's disabled as soon as the phone call is over.
dahawthorne said:
Strephon may be right in suggesting a hardware fault...
Click to expand...
Click to collapse
I hope I'm wrong.