I was running LineageOS 16, the unit went into a bootloop while I was restoring the call and sms history to update it from my main phone. It is something I have been doing weekly for a year now.
I can boot into 'fastboot mode' but not 'recovery mode'.
In fastboot it is recognised by the comand
Code:
fastboot devices -l
. Typing
Code:
fastboot boot /<path_to_file>/twrp-3.3.1-0-bacon.img
puts it back into the bootloop, as does the command
Code:
fastboot reboot-bootloader
.
What can I try next to recover the unit?
Are you hesitant in flashing TWRP instead? Also, use the K-releases of TWRP (see the guide in my signature). They work better opposed to the official releases.
Wrapped with delicious Fajita [emoji896]
I was hoping to recover the unit rather than avoiding re-flashing it.
Is the operating system and all the data lost?
If that is what has happened then I will rebuild, trying the version of TWRP you suggested.
Regards.
alistairrc said:
I was hoping to recover the unit rather than avoiding re-flashing it.
Is the operating system and all the data lost?
If that is what has happened then I will rebuild, trying the version of TWRP you suggested.
Regards.
Click to expand...
Click to collapse
Perhaps the NAND memory sector was damaged, which was very important to boot. It is possible because the memory is overwritten all the time.
Read the entire story of another user who had a similar system loss problem.
The best TWTP was made by The Muppets
twrp-3.2.3-20190125-bacon.img
It is based on a toybox, and not like other TWRP in which there is a busybox. Toybox contains more repair tools and is therefore better than busybox.
have tried to recover using "cm-13.1.2-ZNH2KAS3P0-bacon-signed-fastboot"
but I get an error when I try the command:
Code:
fastboot flash modem NON-HLOS.bin
error: cannot load 'NON-HLOS.bin'
I am now struggling to find any guides that can help me.
(Most of the guides I have read state "connect phone and boot into fastboot mode" but my unit will not boot to fastboot mode when it is connected.)
I have tried to restore the unit twice using
cm-13.1.2-ZNH2KAS3P0-bacon-signed-fastboot.zip
First using the all in one tool on a windows 8.1 box, then using these commands on a linux box:
Code:
fastboot oem unlock
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash oppostanvbk static_nvbk.bin
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata_64G.img
The phone is still stuck either in a bootloop, or in fastboot mode.
What can I try now?
Related
Hey guys,
recently joined this place and its awesome. So many things you can learn...
Ok onto the issue - I was gifted a Micromax A092 a few days back. Qualcomm quad core processor, 1GB Ram, Jelly Bean 4.3.
Well after rooting it somehow (total nightmare - there are a couple of guys in another thread I have been posting in out here, who are still unsuccessfully trying to root theirs) and installing SuperSU and enabling USB debugging, I have hit a brick wall with fastboot mode. The Vol down + Power button combo gets me to the logo screen where it stays till I am forced to pull the battery out to reboot.
Phone does get detected under Device Manager while its stuck on the logo screen and I can install drivers to get it to show up as Android ADB Interface/Android ADB Composite Interface but fast boot refuses to detect it even though adb does when connected normally and executes all commands properly.
Well here's a list of things I have tried:
15 seconds ADB Installer - check
Minimal ADB and fastboot - check
Android SDK with google drivers and unnecessary packages - check
Universal naked drivers - check
Modding the inf files with my devices hardware id's - check
Pdanet+ driver installation method - check
Mobrobo/Mobogenie - check
Manual driver installation - check
Different USB cables - check
Few other random hacks - check
Later gave adb sideloading a shot hoping I could flash a custom recovery onto it via command prompt. No dice there either. Being unable to flash anything means I am still rocking "android system recovery 3e" as my recovery mode which in turn means the dreaded signature verification failed message trying to install 3rd party apps in recovery and sideload mode. I have also tried installing a couple of these custom recovery modes via .bat files but I guess its failing due to the same damn signature verification reason.
Now I know all phones don't ship with fastboot mode but given that this phone was released just a couple of months back and 2 year old inferior phones from Micromax have said feature gives me hope that maybe there indeed exists a way to flash it.
Also got this .dat file from somewhere for apparently flashing my phone with a stock ROM :
@ECHO off
adb reboot bootloader
echo for not erase modemst1 and modest2
rem fastboot flash partition gpt_both0.bin
fastboot flash aboot emmc_appsboot.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash rpm rpm.mbn
fastboot flash sdi sdi.mbn
rem fastboot flash fsg fs_image.tar.gz.mbn.img
rem fastboot flash modemst1 dummy.bin
rem fastboot flash modemst2 dummy.bin
fastboot flash modem NON-HLOS.bin
echo for not erase bt and wifi information
rem fastboot flash persist persist.img
fastboot flash cache cache.img
fastboot flash usbmsc usbdisk.img
fastboot erase splash
fastboot flash splash splash.img
fastboot -S 256M flash system system.img
fastboot flash recovery recovery.img
fastboot -S 256M flash userdata userdata.img
fastboot flash boot boot.img
fastboot reboot
Seeing a lot of fastboot commands in there make me slightly optimistic if might have a fastboot mode after all?
So anyways what am I missing here? Or does the phone not have fastboot mode at all? Coupled with the fact that the asinine default recovery mode won't allow me to load custom apps via side load, what other options do I have? Is fastboot a prerequisite for flashing?
Really frustrated...a little help please guys...thanks.
PS: What is the difference between bootloader and fastboot mode? I can get my phone into bootloader mode via the necessary adb command but it's still stuck at the logo screen so don't know what to make of it.
Hello,
I have been updating my cyanogenmod 12s using the nightlies for a while now.
While I was updating with the update on the 18th, my phone got stuck at the 'upgrading apps' step and keeps repeating the upgrade for hours.
I accidentally then wiped the phone completely in TWRP while trying to restore the phone.
I lost the backups and OS. The warning saying 'No OS installed' shows up when I try rebooting.
My PC does not show the phone when I connect it via USB. I have nothing on TWRP to install either.
Can anyone please suggest how I should proceed?
Thank you,
Abhi2488
1. If you can boot into fastboot, just download stock CM11S fastboot package (you wont have trouble find it, just search forum) and simply flash it with fastboot, one by one partition.
I will just qoute some instructions from oneplus forum:
"Once you're on ColorOS and want to go to Cyanogenmod 11S, you have a few options. The easiest way if to use a toolkit from http://forum.xda-developers.com/onep...9-gui-t2807418, or you can download an image manually from: http://forum.xda-developers.com/onep...stock-t2826541 and run the following commands in fastboot mode:
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
Make sure you have the proper image. I accidentally installed the 16GB version on my 64GB OPO first time and obviously didn't get 64GB of space.
That's about it. I think if people are still having problems then it's likely due to drivers, or Windows 7/8 issue. If you're still getting stuck, let me know, I'll see if I can help."
2. If you allready have custom recovery installed, you can try to flash any custom rom from OTG USB disc (you need OTG cable or OTG adapter and USB fat32 formatted disc where you will copy some custom firmware).
Hello everybody,
I did a mistake :crying:
On my Mi4 was installed a CyanogenMod 13 ROM. To do this, I resize the phone partitions in the past.
Now I want to update to LineageOS 14.1 but at the installation I got the error: "assert failed cancro.verify baseband mpss.di.4.0 == 1".
At the Lineage Community I found the solution, to install first a newer Stock OS and then the Lineage Rom.
But to install the Stock OS I had to resize the system partitions to the original size.
This article was helping me:
http://en.miui.com/thread-93248-1-1.html
After the successfully resizing, I wanted to flash the cancro_global_images_V8.1.6.0.MXDMIDI_20161230.0000.00_6.0_global
with the FLASHING FASTBOOT MiUI ROMS Guide from xda:
https://forum.xda-developers.com/xiaomi-mi-3/general/guide-flashing-fastboot-miui-roms-t2938279
To flash following parts was successfully:
fastboot flash tz tz.mbn
fastboot flash dbi sdi.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash rpm rpm.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot erase boot
fastboot flash misc misc.img
fastboot flash modem NON-HLOS.bin
The error was displayed by the "fastboot flash system system.img" command:
I think the resizing zip was wrong.
Now my Phone doesn't display anything. Not fastboot with power+volume down or cwm with power+volume up.
Only my PC is showing me a lot of partitions and two images folders:
Please help me!
everything ok
I found a possibility, to restore the phone
with the old MiFlash Tool. The newer one does not work.
I'm not able to post the link.
It's the link inside this thread:
https://forum.xda-developers.com/mi-4/help/hard-bricked-mi-4s-black-screen-t3512501
Almost everything possible with the tools provided at MIUI forums. Let us know if your device booted up. Good luck!
Recently I rooted my phone and flash the resurrection remix naught in moto g3 xt1550....
For some reason I start to flash firmware ROM .....but it is not flashing.... Shows " preflash validation failed " and on system image " invalid image" .......... I tried many times but it didn't flash......when I skip the partition gpt file then every image file start flashing and phone start..,..
But their is no network......
After that whenever I switch off or reboot or go to recovery rather than that it start boot loader....
Then I flashed the resurrection remix again..... When I press reboot after flashing then it goes to boot loader......
At boot loader I press power on then it start booting and there is no network in this ROM too......
What can I do now ...... Please help.........
To clear the Fastboot mode, in fastboot enter "fastboot oem fb_mode_clear" and after that it should start the OS without going into fastboot each time.
The fact this is happening leads me to believe your other problem is related... meaning you didn't flash the stock images properly. If you have no network then you need to reflash the radio stack and boot.img file, they must match and you have to erase the modemstX partitions for the radios to work properly.
yes U will get the error of "preflash validation failed" cause of the security update which motorola released for the month of October, January and recent April.... Do one thing again flash the appropriate stock rom according to ur mobile But skip these two steps/Files >>> 1) fastboot flash partition gpt.bin and 2) fastboot flash bootloader bootloader.img and enter the remaining command/or follow the whole procedure but skip these two file mentioned above U will succed:fingers-crossed::good:
For ur simplicity im providing u commands and plz CHECK UR SPARSECHUNK Files it varies according to mobile I have 7 thats y 7 sparsechunk files DO CHECK URs ok>>>>
fastboot oem fb_mode_set
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Do it ur own risk Im not responsible for any damage :laugh:
everything went well except my network .........i checked in about phone < status < imei no is " 0 ".......how to restore that...........i think thats why the network isn't showing.......................
acejavelin said:
To clear the Fastboot mode, in fastboot enter "fastboot oem fb_mode_clear" and after that it should start the OS without going into fastboot each time.
The fact this is happening leads me to believe your other problem is related... meaning you didn't flash the stock images properly. If you have no network then you need to reflash the radio stack and boot.img file, they must match and you have to erase the modemstX partitions for the radios to work properly.
Click to expand...
Click to collapse
where I find radio stack...... I don't know........and I didn't flash the stock images correctly because I have to skip the partition gpt and bootloader......
give me something else to solve it......
btw thanks sir......:good:
heisenberg1546 said:
where I find radio stack...... I don't know........and I didn't flash the stock images correctly because I have to skip the partition gpt and bootloader......
give me something else to solve it......
btw thanks sir......:good:
Click to expand...
Click to collapse
The "radio stack" is the relevant radio portions of the firmware image...
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
It is not uncommon that they don't take the first time, repeat it and the boot.img command. Verify EVERY command returns an OKAY response, if not, repeat it.
And do not copy and paste the commands all at once, type them out and look at the response, or at least copy and paste each command individually.
acejavelin said:
The "radio stack" is the relevant radio portions of the firmware image...
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
It is not uncommon that they don't take the first time, repeat it and the boot.img command. Verify EVERY command returns an OKAY response, if not, repeat it.
And do not copy and paste the commands all at once, type them out and look at the response, or at least copy and paste each command individually.
Click to expand...
Click to collapse
isn't working sir........
I did without copy paste.........
boot img command gives preflash validation failed....
heisenberg1546 said:
It is not uncommon that they don't take the first time, repeat it and the boot.img command. Verify EVERY command returns an OKAY response, if not, repeat it.
And do not copy and paste the commands all at once, type them out and look at the response, or at least copy and paste each command individually.
isn't working sir........
I did without copy paste.........
boot img command gives preflash validation failed....
Click to expand...
Click to collapse
You didn't do the boot.img... but Might want to look at the IMEI 0 recovery thread... I don't have any more ideas.
acejavelin said:
You didn't do the boot.img... but Might want to look at the IMEI 0 recovery thread... I don't have any more ideas.
Click to expand...
Click to collapse
After those commands ...... I flash again all img's including the boot.img......
How to restore the imei file ..... Like in mediatek device ,,, we can write by sn tools .....
heisenberg1546 said:
After those commands ...... I flash again all img's including the boot.img......
How to restore the imei file ..... Like in mediatek device ,,, we can write by sn tools .....
Click to expand...
Click to collapse
I don't know... There is a thread here specifically about it, you will have to look there.
I want to keep the custom rom (RR-O-v6.0.0-20180511-ospreyl) with all networks
acejavelin said:
To clear the Fastboot mode, in fastboot enter "fastboot oem fb_mode_clear" and after that it should start the OS without going into fastboot each time.
The fact this is happening leads me to believe your other problem is related... meaning you didn't flash the stock images properly. If you have no network then you need to reflash the radio stack and boot.img file, they must match and you have to erase the modemstX partitions for the radios to work properly.
Click to expand...
Click to collapse
Hey, I have installed RR-O-v6.0.0-20180511-osprey on Moto G(3rd Generation), and now the error is: "No sim Detected ", IMEI number is fine. I want to flash radio firmware in this custom Rom. Will flashing radio stack of stock rom 6.0.1 (Moto G3 x1550) work?
adb reboot bootloader
fastboot flash modem NON-HLOS.bin (That must of Moto G3?)
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash boot boot.img (Is it to be of RR or of Moto?)
fastboot reboot
Is there any other option or solution then please mention.
You need to flash stock firmware first then your network problem solved then you can install custom roms?
Good Luck!
Hello everyone, i have big problem with my new motorola x force, i bought it with dead software. And i tried install new, (I'm doing it isnt first time). I get key for unlock from motorola service but is imposible. I get an error. This device can not be unlocked.
I guess first owner, forgot turn on develop mode.
Any idea? I'm tried flashing it with instructions from other thread https://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515.
I download soft from motorola, I'm tried first ver. android and new one. Everything without result.
Rasah97 said:
Hello everyone, i have big problem with my new motorola x force, i bought it with dead software. And i tried install new, (I'm doing it isnt first time). I get key for unlock from motorola service but is imposible. I get an error. This device can not be unlocked.
I guess first owner, forgot turn on develop mode.
Any idea? I'm tried flashing it with instructions from other thread https://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515.
I download soft from motorola, I'm tried first ver. android and new one. Everything without result.
Click to expand...
Click to collapse
You do not need to unlock the bootloader to flash original moto firmware
Just put it in bootloader mode and on your pc where you have fastboot and all the firmware files open a command/terminal prompt and type the following
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img (not all devices have this)
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk0 (flash all sparsechunks in number order - for example)
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
TheFixItMan said:
You do not need to unlock the bootloader to flash original moto firmware
Just put it in bootloader mode and on your pc where you have fastboot and all the firmware files open a command/terminal prompt and type the following
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img (not all devices have this)
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk0 (flash all sparsechunks in number order - for example)
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Click to expand...
Click to collapse
Sure, but When i done it phone starting with Motorola logo and restarting, I didn't have this file img with nr 1/4 I mean this fastboot flash system system.img_sparsechunk4
I download soft from Motorola, I don't remember version but it like 5.1? Middle one from list and in another one first vet same
Rasah97 said:
Sure, but When i done it phone starting with Motorola logo and restarting, I didn't have this file img with nr 1/4 I mean this fastboot flash system system.img_sparsechunk4
I download soft from Motorola, I don't remember version but it like 5.1? Middle one from list and in another one first vet same
Click to expand...
Click to collapse
Some phones may not have sparsechunks 0 & 4 - as long as you flash all the ones in the firmware in number order
I don't have your phone so I couldn't tell you what firmware to use
I have Motorola g5 so I can just tell you the process
And looking on that firmware thread it says you need to use mfastboot for system images - so see that thread for details
Long as everything is flashed successfully in the order I have written above including erasing user data
Sooo.... Could you tell me which comand i have to use ?
Related to no sim card issue?
I'm wondering if this is related to a problem I am having with mine phone. I flashed the official firmware (6.0) on my moto x force and everything works but the simcard. It says it's not loaded so I have no phone or cell data. My sim card works in other moto phones so its not that.