I apologize if this is the wrong area, but my phone is hosed and i need help.
I tried installing clockwork recovery touch, and something went horribly wrong. Phone will not boot, however i can get into recovery, but none of my backups will restore.
I can also get to the bootloader, but any fastboot cmd i run says , error: cannot load 'xxxxxxxxxx.img.'
I tried odin, but it doeesnt recognize my phone.
I can see the phone when i do adb devices in recovery
and i can also see it when i do fastboot devices in bootloader mode.
can anyone help me?
thanks in advance.
the way to flash recovery is this
fastboot flash recovery location&nameofFile.img
so if you have the recovery image (and its named recovery) in your folder where fastboot.exe is, it would be: fastboot flash recovery recovery.img
if you had the image somewhere else, say c:\downloads\, it would be fastboot flash recovery c:\downloads\recovery.img
Thank you, i have and can access recovery. that is it, phone will not boot, i need to some how flash an image, but when i do
fastboot flash bootloader xxxxxxxxxxxxxxx.img or anything for that matter
i get: error cannot load 'xxxxxxxxxx.img'
Like Zepius said, do you have the image file in the same folder as fastboot? If not, are you including the full path to the image file, rather than just the image file's name?
yea im an idiot, i thought i unzipped the image there, but i didnt. your right the files wern;t there, flashing now PHWEEWWW
Related
After attempting to install franco kernel, my nexus was stuck at the Google logo upon startup. After attempting to recover via clockwork recovery, I found it to be missing (temporary install perhaps?). Currently I have installed clockwork recovery via nexus toolkit. The problem I am now trying to address is that I have no way of putting .zip files on my phone. Some Google searches did not come up with anything quite like this. I am new to this, so any information is good information. Thanks in advance
luminuss3 said:
After attempting to install franco kernel, my nexus was stuck at the Google logo upon startup. After attempting to recover via clockwork recovery, I found it to be missing (temporary install perhaps?). Currently I have installed clockwork recovery via nexus toolkit. The problem I am now trying to address is that I have no way of putting .zip files on my phone. Some Google searches did not come up with anything quite like this. I am new to this, so any information is good information. Thanks in advance
Click to expand...
Click to collapse
Your boot image is missing...
When your phone boots in bootloadermode, it should (now, anyway) say: boot.img missing. Or something of that nature. Check this, flash it via fastboot, then everything should be back to normal...
EDIT:
It works with both: CDMA & GSM
luminuss3 said:
After attempting to install franco kernel, my nexus was stuck at the Google logo upon startup. After attempting to recover via clockwork recovery, I found it to be missing (temporary install perhaps?). Currently I have installed clockwork recovery via nexus toolkit. The problem I am now trying to address is that I have no way of putting .zip files on my phone. Some Google searches did not come up with anything quite like this. I am new to this, so any information is good information. Thanks in advance
Click to expand...
Click to collapse
do you know how to use fastboot and adb?
Excuse my lack of knowledge, but how exactly do I flash something over fastboot? Thanks in advance again.
Edit: And I do know how to use adb, however it does not connect. I do not know how to use fastboot
After some playing around with fastboot, I now have a basic understanding. However, I am not sure where I should be flashing that file you have linked.
Today, a friend suggested I try mounting via, and copying roms over that way. However, even with all the drivers installed on my computer, I get nothing.
If anyone has ANY insight on this problem, it would be be greatly appreciated. My new toy is a brick at the moment
Thanks in advance!
luminuss3 said:
Today, a friend suggested I try mounting via, and copying roms over that way. However, even with all the drivers installed on my computer, I get nothing.
If anyone has ANY insight on this problem, it would be be greatly appreciated. My new toy is a brick at the moment
Thanks in advance!
Click to expand...
Click to collapse
I'd seriously try to go back to stock first. I'm not a Windows user but if you have adb, fastboot, and your drivers setup, it should be easy. Mark is a great help in this thread and you can use his script I guess:
http://forum.xda-developers.com/showthread.php?t=1400871
You need to also realize that if you have wiped everything to install a new rom, you have nothing to boot to. Also there is install-recovery.sh file that keeps re-writing your recovery to stock erasing custom recovery (CWR) until you rename or erase that file. So going back to stock would be the safest and then you can try again.
You can use adb in recovery and fastboot in bootloader. If you have everything setup correctly (sdk, adb, fastboot, drivers for windows) either of these commands should recognize your phone:
In Bootloader (the first screen you see with big arrow on top):
Code:
fastboot devices
In recovery:
Code:
adb devices
If you don't have a recovery, then use the first one. If you see your phone's serial number like this
Code:
List of devices attached
HT12HS005115 device
you can now use it to flash things onto your phone. As I said I am not a windows user so I can't be specific, sorry. But adb and fastboot, once you are at their prompt, should work the same.
In general, when fastboot is recognizing your phone in the bootloader, you can use:
Code:
fastboot flash zip YOURFILENAME.zip
changing yourfilename of course. This zip file could be a stock imaqe or a custom recovery. Again, you need someone with windows to give you exact steps, this is just general stuff.
if your phone is yakju build then you can get the stock images from google.
download and unzip the files to your fastboot folder and use these commands, the file names in these commands are for the Android 4.0.1 (ITL41F) build so you will have to change the filenames if you use a different build.
Code:
fastboot devices (to make sure your phone is connect to fastboot)
fastboot flash bootloader bootloader-maguro-primekj10.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro-i9250xxkk1.img
fastboot reboot-bootloader
fastboot -w update image-yakju-itl41f.zip
Have completed rumrunner root for htc one.
Have installed twrp through adb using command prompt.
Then when trying to reboot system it boots up in recovery.
Need help to find out how to get back on my phone.
Have found similar sites with information but not clear enough for me to understand
I'm able to access twrp so i would assume it's a mount of the sd card but i am not seeing that option anywhere
twrp v 2.6.3.0
I know it's late guys thanks for your help!
if you ever get this issue please understand that there are websites out there that are making you use "fastboot flash boot blah.img" which is making you flash recovery on top of your boot img. please understand that you have overwritten something that is necessary for your phone to work so just open a rom you are preparing to flash and unzip. Copy the boot.img from the unzipped folder and move it to your fastboot folder where your going to open command prompt.
after you open command prompt in the same folder as your adb/fastboot/ and such using shift right click
you then type in the command prompt "fastboot flash boot boot.img" that should flash the boot image back and you should be able to turn on your phone.... wow that took a lot of stress but figured it out in the end. JUST HAD TO GET A GRIP! now happy flashing thanks!
kiit408 said:
if you ever get this issue please understand that there are websites out there that are making you use "fastboot flash boot blah.img" which is making you flash recovery on top of your boot img.
Click to expand...
Click to collapse
Either the tutorial was completely written wrong, or you read them wrong. There's no way of telling which happened, but the point is to be very careful with fastboot.
The command "fastboot flash boot file.img" doesn't flash recovery in your boot partition unless you mis-labeled your .img file and flashed the wrong file in the wrong place.
Most people modding their phones are going to be using fasboot to flash to boot, recovery, system, or bootloader. It's important to understand all of the places that fastboot can flash before you start pushing in .img files. Understanding fastboot commands can also help you possibly identify if someone made a typo in their guides.
Want to put in recovery? "fastboot flash recovery recovery.img". Want to put in a new kernel? "fastboot flash boot boot.img", and so on. Ensure that you've got files that are properly named and you won't ever have to worry about flashing the wrong thing in the wrong place.
kiit408 said:
if you ever get this issue please understand that there are websites out there that are making you use "fastboot flash boot blah.img" which is making you flash recovery on top of your boot img. please understand that you have overwritten something that is necessary for your phone to work so just open a rom you are preparing to flash and unzip. Copy the boot.img from the unzipped folder and move it to your fastboot folder where your going to open command prompt.
after you open command prompt in the same folder as your adb/fastboot/ and such using shift right click
you then type in the command prompt "fastboot flash boot boot.img" that should flash the boot image back and you should be able to turn on your phone.... wow that took a lot of stress but figured it out in the end. JUST HAD TO GET A GRIP! now happy flashing thanks!
Click to expand...
Click to collapse
Jjust understand what you're flashing, you can't 100% trust a tutorial..
If you do the command, fastboot flash boot boot.img, you BEST DAMN be sure that is a kernel/boot.img you are flashing and make sure your working is right, if you fastboot flash a boot.img to say recovery.img, you are screwed.
make sure the file is right my MD5, also make sure the tutorial is good, messing with ANYTHING in fastboot is dangerous.
Hello, I am currently rooted and on stock on pixel xl. I am trying to flash the pure nexus rom. I downloaded through the link in the op, factory reset and flashed through twrp (3.0.2rc1). When I went to reboot, it said OS not installed. Can anyone offer any assistance with this? Needless to say, I didn't reboot with that. I did however do a backup (of stock) prior to this. I decided to restore my backup but when it rebooted it said something about the vender image is not right with this system and to flash the correct image. This is exactly what its saying : Your vendor image does not match the system. Please flash the NOF27C vendor image for your device. I have managed to move the correct image file to the internal storage but from what i read, can only install through twrp.
And when it finished rebooting, now 90% of my apps are crashing, no fingerprint hardware, developer options are not available and I had to reboot back into recovery but its like twrp is gone, it looks like the stock recovery. Somehow it appears there are parts of my stock rom and pure nexus rom combined which is understandbly causing my issues. Right now I am trying to get back to having twrp but am stuck.
I have since tried to reinstall twrp but when I plug my xl into my pc, the pc recognizes it but no storage. I cant move a file from pc to xl because its saying disconnected or not responding. Tried to get a command prompt and when I shift/right click, there is no option. I don't know what else to do.
If anyone has any suggestions, please help. I am freaking over this. Can't use my phone in the state its in.
Sounds far from bricked.
Just entirely screwed up.
FASTboot the latest factory image and then refrain from tinkering for the weekend.
These are the steps i use.
I think a new ADB/FastBoot package was released yesterday you might want to install that.
Execute fastboot commands (assuming the bin is on your PATH)
fastboot flash bootloader c:\_PIXEL_XL_\bootloader.img
fastboot reboot-bootloader
fastboot flash radio c:\_PIXEL_XL_\radio.img
fastboot reboot-bootloader
fastboot flash boot_a c:\_PIXEL_XL_\boot.img
fastboot flash boot_b c:\_PIXEL_XL_\boot.img
fastboot flash system c:\_PIXEL_XL_\system.img
fastboot flash system_b c:\_PIXEL_XL_\system_other.img
fastboot flash vendor c:\_PIXEL_XL_\vendor.img
fastboot flash modem c:\_PIXEL_XL_\modem.img
fastboot reboot
To add TWRP and Root:
fastboot boot c:\_PIXEL_XL_\twrp.img
In TWRP, install twrp.zip
Reboot into the installed recovery
In TWRP, install supersu.zip
I've been following this guide:
https://forum.xda-developers.com/pi...p-flashable-monthly-update-zip-pixel-t3375591
to try and root my Pixel C. I was initially following a different guide, but I believe I now have:
bootloader-dragon-google_smaug.7900.50.0.img and TWRP_dragon_3.1.0-2.img, loaded through fastboot
I was then able to push
Update.ZIP_PixelC_Ryu_system-vendor-boot_OPP1.zip and SuperSU-v2.79-201612051815.zip to /sdcard/ via adb in TWRP. I then tried to install both, as per the guide.
I was a bit confused when the "flashing system.img... this will take some time" part took no time at all, but it had taken a while to get to that point so I figured maybe the messages were in the wrong order or something. Both said they were successful.
Tried booting to system - just came back to TWRP.
So I thought I'd try to flash the system image back on. But I can't push any files now. Everytime I try, it creates the files then fails and I start getting read-only file system errors
If I try to install update.zip again (the one above), I now get "failed to mount '/data-full' (Device or resource busy)"
So I'm quite stuck at this point. Can't revert to stock image, can't install the new image... any help would be much appreciated!
I would do the following:
Download the full factory image from here. If you want to keep all of your data extract the zip and remove "-w" from flash_all.bat or flash_all.sh (depending on your OS).
If you keep -w it wipes your settings.
Boot into fastboot and run flash_all.
It will write all data from the factory image to your device and it should boot into android again.
If your tablet is up and running you can download twrp and flash it again on your tablet.
I always flash twrp like this:
fastboot flash recovery twrp.img
fastboot boot twrp.img
if i boot into twrp it asks for a decryption-pass. I skip this and go directly to reboot and reboot into recovery. Now i will not be asked for a password and can go on flashing the latest supersu.
peter73 said:
I would do the following:
Download the full factory image from here. If you want to keep all of your data extract the zip and remove "-w" from flash_all.bat or flash_all.sh (depending on your OS).
If you keep -w it wipes your settings.
Boot into fastboot and run flash_all.
It will write all data from the factory image to your device and it should boot into android again.
If your tablet is up and running you can download twrp and flash it again on your tablet.
I always flash twrp like this:
fastboot flash recovery twrp.img
fastboot boot twrp.img
if i boot into twrp it asks for a decryption-pass. I skip this and go directly to reboot and reboot into recovery. Now i will not be asked for a password and can go on flashing the latest supersu.
Click to expand...
Click to collapse
I second this ^ except for the fastboot boot twrp.img part. Why do you do that? The first line should be enough.
Hello, on any custom roms we see recovery as img, so whats the ultimate good process to actually flash it?
img to tar bootloop
any other recovery bootloop
only one thats working is "twrp-z3s-3.5.0_10-A11_6+vbmeta_DUB5" BUT i have x1s, so pain to flash some rom.
Im currently on beyond rom 3.1, because i cant flash anything else.
Any help here?
Try flashing vbmeta.img after flashing recovery
like download mode -> recovery, then download mode again and only vbmeta?
didnt try that, ill try it right away
edit:
1) download mode -> AP EXYNOS-G98X-LINEAGE-RECOVERY-20200709
2) booted up rom
3) turned off -> download mode -> USERDATA vbmeta.tar from beyond rom
4) bootloop, up button and power same thing
i dont know if i should try stock and then go for root again or what exactly do.. i dont want to lose any data now. It got really complicated, since i go from root apk clockworkmod era.
maybe magisk is the issue? since i have it installed
Go to fastboot
Flash recovery
Flash vbmeta
Reboot
If fastboot doesn't like extensions of your images, change them to .img
how can i get to that? on TWRP if i do reboot -> fastboot, im still in TWRP and "fastboot devices" shows completely nothing (not even list of devices or whatever)
when i go to bootloader mode from magisk i just see "entering fastboot mode.." and thats about it, no fastboot commands work
b30wu1f said:
how can i get to that? on TWRP if i do reboot -> fastboot, im still in TWRP and "fastboot devices" shows completely nothing (not even list of devices or whatever)
when i go to bootloader mode from magisk i just see "entering fastboot mode.." and thats about it, no fastboot commands work
Click to expand...
Click to collapse
Move vbmeta.img to your phone and go to Install section. Install it and reboot.
Also, TWRP offers an option to reboot to bootloader. You can try it too
well, i flashed lineage recovery img and then vbmeta, phone booted up, but got probably original recovery. its really frustrating. Do you have any valid and working "tutorial" to get the recovery working ?
i just need recovery thats x1s, so it should be probably lineage recovery, but cant install it. Im starting to hate these new phones.
I'm sorry, I don't have any specific tutorial, but in general:
adb reboot-fastboot
fastboot flash recovery recovery.img
fastboot flash vbmeta vbmeta.img
fastboot reboot-recovery
If this doesn't work, search for your specific device on XDA. You shouldn't hate new phones, you should hate people who sell them, because they make everything hard so you won't switch from their software, which spies on you.
tried TWRP that works, installed as img lineage-18.1-20210224-recovery-x1s.img and now it suddenly worked. Thank you for help, after 6 hours =)