Here I am being an idiot and not making a backup of my firmware. I was given a phone that bootloops when unplugged, so I try and flash a GSI rom, but I first flash twrp, and everything went to crap from there. Same thing that another poster said that bootloader corrupt or bad key. Have tried flashing a ton of firmware and it's all out of date files. Is there a tool or something that can grab files from Motorola servers or something?
What is happening exactly with your phone? you can't access twrp? to flash a rom?
You can get the official ROM files from lolinet or stockrom.net. If you don't trust these you can use logcat and intercept the link code when your phone tries to update, but you have a limited time to use this link because it was requested to the server and it gives a specific time to use it.
If no stock rom file works, use command fastboot getvar all and look for the version stated in the lines that show up on the console. once found download that exact same version and try to flash it, if that doesn't work you should try booting the boot.img inside the zip folder from the firmware file you downloaded and using command fastboot boot boot.img
Then try activating OEM unlock, and if this doesn't work then try updating phone.
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
Hello.
First, if this post is on wrong place, sorry. Please move it, if necessary.
So, I have a chinese clone of Sony C6. It is rooted, based on MT6580, but I don't know how or why, my kid messed up something, and now it is stuck at logo screen after restart. So, I searched for a way to flash it to brand new with a ROM dump I made some days ago with 'dd'.
It also was bootloader unlocked, but I don't know why, it locked again when I tried to flash the backup files I have (maybe I locked for so many tries to flash). It refused to re-unlock. Maybe I need to go settings and enable "allow oem unlocking" under developer settings, but as the phone don't boot, this is not an option. BTW, the fastboot mode of this phone don't have a lot of commands, is very simple. Don't have even the 'fastboot oem ?' command. It flashed boot and recovery when unlocked, but when I tried to flash system, it gives an error of 'unknow command' when erasing system. So, tried with -u option, but gives another error about 'unknow chunk size'. Searches about this don't give me anything helpful.
Some other things I tried:
Downloaded a compatible ROM for this phone (the original simply don't exists), checked the scatter file, and replace relevant files with my backup, to use with SP Flash Tools, but the download never starts. I checked the drivers and everything else and are all correct. Tried on another computer with different operating system, but it simply don't start the download. Maybe isn't compatible with my phone;
Use 'fastboot flash system', but as sayed above, with locked bootloader I can't flash the files anymore at this mode;
Make a flashable ROM on SuperR's kitchen to flash with adb sideload (as stock recovery can't flash this), but it ended with 'installation aborted' just after start;
Tried to make a CWM recovery through CWM builder, and flash the ROM made by kitchen, but it gives 'bad gateway' at the end. Tried to build one in a ubuntu virtual machine, but it can't sync the repo, so I can't build one.
On the kitchen, I sucessfully modified and flashed recovery to allow ADB commands (as the original gives me 'unauthorized'), but in the actual state, it even can't mount system, giving an '/system/bin/sh not found' error.
So, I have a working stock recovery with ADB and also fastboot mode working, but none of them helped. I need help to make that CWM, or another way to have the phone working.
Attached is the modified recovery and original boot images. Can someone please convert it for me?
Also, any suggestions in how I can put the phone working will be helpful.
Thanks in advice.
Hello friends, I have the model 1789-05 att version and it has suffered a brick I already have the firmware but with RSD I get the error then by ADB codegos are needed my question is, does anyone have the flash code by ADB of the stock firrmware?
How did you brick it? What are you trying to flash to unbrick?
Uzephi said:
How did you brick it? What are you trying to flash to unbrick?
Click to expand...
Click to collapse
I was trying to root but fail, I'm trying to flash the stock firmware by CMD
sharlyconcept said:
I was trying to root but fail, I'm trying to flash the stock firmware by CMD
Click to expand...
Click to collapse
Link to what you're flashing? I can build a .bat file for you that does all the commands for that firmware zip easily.
It hasn't been tested on a locked BL though... Mine was pseudo locked but the other slot was unlocked so that might be why it flashed just fine
1789-05 is not AT&T hardware XT-1789-4 is AT&T and Tmo hardware it could be your files are for the wrong device i seriously effed mine up trying to root it but i got it to boot again with the nougat update.
here is a link to my drive and the script i have for the moto Z2 force.
https://drive.google.com/open?id=1G0...-gsd1Mw_HZgmJ4
you still need your files from a rom site like this one:
https://firmware.center/firmware/Mot...ock/XT1789-04/
i would not roll back as some people have had issues but i was able to flash a at&t rom on my phone and go back with this. just flash oreo back in.
make sure you enabled adb before starting.
well the way it works is you download the rom from the site (yes use the oreo version) then you unzip the rom and copy all the files to your platformtools directory.
next you place the .bat i gave you to the exact same location you just copied the rom files (platformtools directory)
now open a command window from the platformtools location and then enter the following:
adb devices
this should detect the hardware, next.
adb reboot bootloader
this will reboot to the bootloader, and we now switch to fastboot.
fastboot devices
this is the same as the adb command, and confirms the hardware is being detected.
now we are set to double click the .bat file and it will auto run.
if you want you can open the .bat file in edit mode and run each command manually by copy and paste
try this one for the script
https://drive.google.com/file/d/1G0C...ew?usp=sharing
this is the rom
https://firmware.center/firmware/Mot...ock/XT1789-04/
Hi everyone, i'm kinda new here and noob i'll describe the problem.
I have already followed many guides about bricked phones, fastboot solving and xftsk.
I have this Zenfone 2 Deluxe that i have modded with Groovy Android, tried to root with magisk but it didn't work so i wiped everything with TWRP(every option). Only TWRP worked for 2 days telling me that there was no OS. So i tried to flash a stock firmware via ASUS Flash tool but it didn't work cause it couldn't enable ADB. ADB didn't work once, first it didn't detect phone, then it said device offline so I gave up. Found the xFTSK method. Tried it and worked ( it booted into bootloader with the rainbow icon and still does) but the serial changed to 0123456789ABCDEF. Tried Fastboot right after as guides said. Fastboot didn't and still don't work. He couldn't find files, couldn't load them and now it says " failed (write to device failed(unknown error)). So I tried ASUS flash tool again but he said flash image failure status read failed too many links, then that fastboot coulnd't be loaded and other errors.
Along the way recovery mode "disappeared" too. It doesn't work anymore. Plus sometimes the phone boots and keeps rebooting into a white usb icon.
What should I do? Feel free to re-link me guides, PM or something else, i'm open to almost everything to solve that.
Thanks in advance.
Edit: fastboot gaves some kinda errors with partitions too ex: can't erase cache.
Battery and cable are not ASUS original ones.
MixedFried said:
Hi everyone, i'm kinda new here and noob i'll describe the problem.
I have already followed many guides about bricked phones, fastboot solving and xftsk.
I have this Zenfone 2 Deluxe that i have modded with Groovy Android, tried to root with magisk but it didn't work so i wiped everything with TWRP(every option). Only TWRP worked for 2 days telling me that there was no OS. So i tried to flash a stock firmware via ASUS Flash tool but it didn't work cause it couldn't enable ADB. ADB didn't work once, first it didn't detect phone, then it said device offline so I gave up. Found the xFTSK method. Tried it and worked ( it booted into bootloader with the rainbow icon and still does) but the serial changed to 0123456789ABCDEF. Tried Fastboot right after as guides said. Fastboot didn't and still don't work. He couldn't find files, couldn't load them and now it says " failed (write to device failed(unknown error)). So I tried ASUS flash tool again but he said flash image failure status read failed too many links, then that fastboot coulnd't be loaded and other errors.
Along the way recovery mode "disappeared" too. It doesn't work anymore. Plus sometimes the phone boots and keeps rebooting into a white usb icon.
What should I do? Feel free to re-link me guides, PM or something else, i'm open to almost everything to solve that.
Thanks in advance.
Edit: fastboot gaves some kinda errors with partitions too ex: can't erase cache.
Battery and cable are not ASUS original ones.
Click to expand...
Click to collapse
do not use asus flash tool to flash raw firmware. use commands to flash firmware. second if you will use latest raw after xFSTK it will not work. Use old raw firmware provided in guide. Hoping that ASUS flash tool has not messed up your device. use old firmware in guide command's method. if fails once again use xFSTK and flash old firmware via commands. Stay away from asus flash tool.
sukhwant717 said:
do not use asus flash tool to flash raw firmware. use commands to flash firmware. second if you will use latest raw after xFSTK it will not work. Use old raw firmware provided in guide. Hoping that ASUS flash tool has not messed up your device. use old firmware in guide command's method. if fails once again use xFSTK and flash old firmware via commands. Stay away from asus flash tool.
Click to expand...
Click to collapse
Thanks for the advices. Fact is, fastboot commands do not work so I tried flashing varius raw files via Asus flash tool but without success. If u think u can help me I can post screenshots about the errors ( I don't know why they change everytime)
MixedFried said:
Thanks for the advices. Fact is, fastboot commands do not work so I tried flashing varius raw files via Asus flash tool but without success. If u think u can help me I can post screenshots about the errors ( I don't know why they change everytime)
Click to expand...
Click to collapse
yes a screenshot would be good. as i told earlier. new firmware version or bootloader have different set of commands. post raw firmware version number you are using along withifwi version and bootloader version you are on currently.
sukhwant717 said:
yes a screenshot would be good. as i told earlier. new firmware version or bootloader have different set of commands. post raw firmware version number you are using along withifwi version and bootloader version you are on currently.
Click to expand...
Click to collapse
Fine, bootloader version says " unknown " now, i'll try re-using xFSTK. About the screenshots here they are. http://puu.sh/D7tXU/b83ccf1502.png
Ok so i downloaded a module for lsxposed and we'll it prompted to reboot my phone and GG it was stuck in boot loop and well i tried factory reset cleared data etc etc so i have the original payload.bin but i need the actually img files so i can manually fasboot command each one since i rooted my device without PC and i don't have access to one ATM. If anyone has extracted the files from the payload.bin can u please let me know
How on earth did you root without a PC and how will you flash the images without one? Also we need to know your model (BE2012/BE2013/BE2014/BE2015) and your OOS version (10.0.1/11.0.1/11.0.7/etc/etc). Or you can attach the payload file you have so someone can extract it.
Alternatively you can try to switch slot in bootloader if you can execute fastboot commands. However if boot image is also patched on the other slot then this will probably not work.
I have to manually flash them one by one example fastboot flash vbmeta etc etc Haha yes i know it's actually quite difficult but with trial and error i managed to root it and have essentially full access all without a PC hehe trust me it took me 72plus hours and what is the command to switch from boot_a/boot_b and i will attach the payload.bin file hopefully someone can help
fastboot getvar current-slot will tell you your current slot. fastboot --set-active=[a or b] to switch.
I still don't understand how you are running the commands if you're not using a PC. Except if you're using adb on another phone.
Yeah i bricked it bad now lol i searched on Google found the same commands so i switched it to _a and we'll now it won't boot to recovery or even to the bootloader and i use bugjaeger app essentially use your phone as a pc but is limited