Related
I have a rooted Verizon LG G2 and have been trying to install a recovery mod. I somehow got rid of the stock recovery, but couldn't setup a new one. Now my phone is stuck on the fastboot screen. I've been able to get it to the stock recovery screen, but when it starts to wipe the drive, it just takes me back to the fastboot screen. I'm very new to this and haven't been able to figure this out through any other threads. I'm using Ubuntu. Any help would be greatly appreciated!
joshuascan said:
I have a rooted Verizon LG G2 and have been trying to install a recovery mod. I somehow got rid of the stock recovery, but couldn't setup a new one. Now my phone is stuck on the fastboot screen. I've been able to get it to the stock recovery screen, but when it starts to wipe the drive, it just takes me back to the fastboot screen. I'm very new to this and haven't been able to figure this out through any other threads. I'm using Ubuntu. Any help would be greatly appreciated!
Click to expand...
Click to collapse
I'm in the same boat. I tried to install TWRP using the Autorec but accidentally used the one for the LS980, and now I'm stuck at the fastboot screen. Did you ever solve this?
eye_rule said:
I'm in the same boat. I tried to install TWRP using the Autorec but accidentally used the one for the LS980, and now I'm stuck at the fastboot screen. Did you ever solve this?
Click to expand...
Click to collapse
Code:
1. download fastboot
2. download laf.img boot.img aboot.img for your variant
(or download your kdz, download kdz/tot extractor and extract partitions --and rename them from boot_45465757.bin to boot.img)
* boot_45465757.bin is just an example.
3. fastboot flash aboot aboot.img
4. fastboot flash boot boot.img
5. fastboot flash laf laf.img
-> download mode should be back
sorry for jumping back on this thread but im having the same problem...phone boots up to just fastboot....ive been reading for 4 days now trying to find any possible way to fix my phone...it really sucks not having a phone...so now im able to connect the phone to the laptop via fastboot but im looking for this laf.img, boot.img etc files. where can i find them?
Also vs980?
robledjl said:
sorry for jumping back on this thread but im having the same problem...phone boots up to just fastboot....ive been reading for 4 days now trying to find any possible way to fix my phone...it really sucks not having a phone...so now im able to connect the phone to the laptop via fastboot but im looking for this laf.img, boot.img etc files. where can i find them?
Click to expand...
Click to collapse
This can be fixed .
1. You Will need to Download the Stock KDZ/TOT file for your phone , find the right KDZ or TOT file from here .
2. Now you would have to extract the KDZ/TOT file that you downloaded above using WindowsLGFirmwareExtract-1.2.1.0-Release.zip , this is available in the guide here.
3. Extract all the files fro the KDZ/TOT .
4. Now flash the extracted files , based on the fastboot method , which is described here.
Code:
fastboot flash aboot aboot.img
fastboot flash boot boot.img
fastboot flash dbi dbi.img
fastboot flash laf laf.img
fastboot flash misc misc.img
fastboot flash modem modem.img
fastboot flash persist persist.img
fastboot flash recovery recovery.img
fastboot flash rpm rpm.img
fastboot flash sbl1 sbl1.img
fastboot flash tz tz.img
Let me know if you need more help.
Why so many partitions. Be sure to flash same version as your current android is at least.
Hello everyone,
I was wondering if there was a way to flash aboot.mbn to the aboot partition.
I have tried Heimdall however it does not seem to be compatible with the s5 yet and odin v3.09 and v1.85 also gives me problems and thus far have been unable to flash it. I have also tried the dd command from and android terminal emulator
Code:
dd if=/storage/extSdCard/aboot.mbn of=/dev/block/mmcblk0p6
which also did not work and i do not believe that mobile odin can flash aboot either.
So my question is is there any other way to flash aboot or am i stuck until heimdall updates compatibility?
i am on G900T s5.
Thank You.
If u got adb installed on your pc, using following command
fastboot devices
fastboot flash aboot aboot.img
babygau said:
If u got adb installed on your pc, using following command
fastboot devices
fastboot flash aboot aboot.img
Click to expand...
Click to collapse
I tried but i do not think that samsung adds support for fastboot at all since the use their own download mode for odin and stuff
I am still stuck on this last hurdle, any help welcome thanks
I could really use the help, this is the last thing in my way
cm0002 said:
I could really use the help, this is the last thing in my way
Click to expand...
Click to collapse
Can you not be able to reflash stock firmware using Odin???
babygau said:
Can you not be able to reflash stock firmware using Odin???
Click to expand...
Click to collapse
No for whatever reason odin fails to flash when i package aboot.
i package it as a tar with 7zip, just aboot.mbn file nothing special and no special settings, or am i missing something that odin needs?
cm0002 said:
No for whatever reason odin fails to flash when i package aboot.
i package it as a tar with 7zip, just aboot.mbn file nothing special and no special settings, or am i missing something that odin needs?
Click to expand...
Click to collapse
Odin doesn't flash zip file bro
Why not using Odin to flash your complete stock firmware?
Hi,
I am also stuck with flashing aboot.mbn, did you have any luck since?
ferdossi said:
Hi,
I am also stuck with flashing aboot.mbn, did you have any luck since?
Click to expand...
Click to collapse
what is the purpose of just flashing the aboot.img?
youdoofus said:
what is the purpose of just flashing the aboot.img?
Click to expand...
Click to collapse
in fact I don't just flash aboot, my issue occurs when I try to flash the I9505XXUHPK2.tar bootloader which contains also other files but ODIN stops when trying to flash aboot.mbn
FIRST OF ALL
(Also for downgrading to KitKat without softbricked phone!)
Okay, I decided to do the OTA to lollipop, everything went fine. So after some use I decided to play with the /system partition. I formatted it without making a working backup so my phone was kinda softbricked. REMEMBER THIS THREAD IS NOT FOR HARDBRICKED BOOTLOADERS, you guys have to wait.
SO WHAT TO DO?
1. Plug your phone into fastboot in your pc.
2. Flash a custom recovery, like CWM, I know you'll have a screen rimble effect due the new bootloader (doesn't matter)
3. Open recovery and keep it plugged into PC, recovery will have adb on by default so leave recovery as it is.
4. Open CMD and type:
Code:
cd directory-with-adb.exe-and-fastboot.exe-etc.
(I assume that you guys know how to use adb and fastboot with CMD)
5. Type:
Code:
adb devices
6. Your Moto's serial number should show up in the attached devices list (serialnumber, recovery), if not download the driver installer from http://adbdriver.com
7. Now download a firmware flashable zip to the directory in your CMD (CyanogenMod or stock firmwares from here)
8. Now you have to make sure you are able to mount the /sdcard in recovery: To make sure do a /data and media wipe. (Also helps on GPe ROM and the encryption problem!)
9. Now you can push the downloaded zip to the phone's sdcard using:
Code:
adb push yourrom.zip /sdcard/yourrom.zip
It will take some time.
10. Now you can install but you may face a not working SIM or WiFi, you need to download a .xml.zip firmware corresponding to your just flashed version. Navigate to your firmware folder using CMD. Then type:
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
11. Now your phone should work. You will have that annoying screen rimble. Sometimes it's gone, just turn screen off for a few minutes. It will be fixed when you install the stock recovery and then flash an lollipop OTA zip just like before! (OTA's will still show up and works with updating )
WARNING!
SOME GUYS MADE A HUGE MISTAKE AND BRICKED THEIR BOOTLOADER. THEY FLASHED LOLLIPOP OTA, THEN DOWNGRADED TO 4.4.2 AND THEY TRIED TO UPDATE TO 4.4.4 BY OTA!
THAT RUINED THE BOOTLOADER SEE BELOW!
FOR HARDBRICKED DEVICES
You ruined your bootloader, we need a mbm-ci (blankflasher tool) with the 5.0 bootloader. We have to wait till Motorola releases it. So no support yet.
Sorry guys, that was the risk!
HOPE YOU GUYS LIKE THIS TUTORIAL!
Thanks for the guide.
restore
GI0\/\NNI said:
FIRST OF ALL
Okay, I decided to do the OTA to lollipop, everything went fine. So after some use I decided to play with the /system partition. I formatted it without making a working backup so my phone was kinda softbricked. REMEMBER THIS THREAD IS NOT FOR HARDBRICKED BOOTLOADERS, you guys have to wait.
SO WHAT TO DO?
1. Plug your phone into fastboot in your pc.
2. Flash a custom recovery, like CWM, I know you'll have a screen rimble effect due the new bootloader (doesn't matter)
3. Open recovery and keep it plugged into PC, recovery will have adb on by default so leave recovery as it is.
4. Open CMD and type:
Code:
cd directory-with-adb.exe-and-fastboot.exe-etc.
(I assume that you guys know how to use adb and fastboot with CMD)
5. Type:
Code:
adb devices
6. Your Moto's serial number should show up in the attached devices list (serialnumber, recovery), if not download the driver installer from http://adbdriver.com
7. Now download a firmware flashable zip to the directory in your CMD (CyanogenMod or stock firmwares from here)
8. Now you have to make sure you are able to mount the /sdcard in recovery: To make sure do a /data and media wipe. (Also helps on GPe ROM and the encryption problem!)
9. Now you can push the downloaded zip to the phone's sdcard using:
Code:
adb push yourrom.zip /sdcard/yourrom.zip
It will take some time.
10. Now you can install but you may face a not working SIM or WiFi, you need to download a .xml.zip firmware corresponding to your just flashed version. Navigate to your firmware folder using CMD. Then type:
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
11. Now your phone should work. You will have that annoying screen rimble. Sometimes it's gone but not sure. It will be fixed when you install the stock recovery and then flash an lollipop OTA zip just like before! (OTA's will still show up and works with updating )
FOR HARDBRICKED DEVICES
You ruined your bootloader, we need a mbm-ci (blankflasher tool) with the 5.0 bootloader. We have to wait till Motorola releases it. So no support yet.
Sorry guys, that was the risk!
HOPE YOU GUYS LIKE THIS TUTORIAL!
Click to expand...
Click to collapse
thanks for this guide
but my phone is not bricked ,can i downgrade 5.0 to 4.4.4
because my moto g is asian retail, i already installed brasil firmware and ota file
mostwantedxda said:
thanks for this guide
but my phone is not bricked ,can i downgrade 5.0 to 4.4.4
because my moto g is asian retail, i already installed brasil firmware and ota file
Click to expand...
Click to collapse
Yeah just follow guide!
Hi I have updated my Asian XT 1033 to brazil 5.0 but experienced NO NETWORK on both the sim cards... and now i downgraded to my asian 4.4.4 but still NO NETWORK on both sim cards... Please help .... m worried ;(
Imei vanished
My imei numbers are vanished.... Please help me... is there any thing i can do now??
hunterhere said:
Hi I have updated my Asian XT 1033 to brazil 5.0 but experienced NO NETWORK on both the sim cards... and now i downgraded to my asian 4.4.4 but still NO NETWORK on both sim cards... Please help .... m worried ;(
Click to expand...
Click to collapse
Flash 4.4.4
NON-HLOS.bin
fsg.mbn
Read the guide!
hunterhere said:
My imei numbers are vanished.... Please help me... is there any thing i can do now??
Click to expand...
Click to collapse
@hunterhere,
I think I found a solution!
1. Download and extract zip
2. Connect phone in fastboot mode to your PC
3. Run IMEI_fix_gio.bat
4. Should work now!
first of all i dont know where to ask this Q
after i downgrade to 4.4.4 with the guide will i be able to flash CM12 or my phone will be dead?
poran123 said:
first of all i dont know where to ask this Q
after i downgrade to 4.4.4 with the guide will i be able to flash CM12 or my phone will be dead?
Click to expand...
Click to collapse
after downgrading from 5.0 i was able to flash any rom STOCK 4.4.4 of any region and 5.0 too again... so according to this u shld be able to flash....
poran123 said:
first of all i dont know where to ask this Q
after i downgrade to 4.4.4 with the guide will i be able to flash CM12 or my phone will be dead?
Click to expand...
Click to collapse
You can flash without problems. Promise!
hunterhere said:
after downgrading from 5.0 i was able to flash any rom STOCK 4.4.4 of any region and 5.0 too again... so according to this u shld be able to flash....
Click to expand...
Click to collapse
did you try any CM roms?
---------- Post added at 01:16 PM ---------- Previous post was at 01:15 PM ----------
GI0\/\NNI said:
You can flash without problems. Promise!
Click to expand...
Click to collapse
thanks for confirming ..:good:
Adb drivers not recoganizing.
when i plug in the phone some drivers get installed.
but my phone is not showing up in adb devices.
i flashed CMW & am running Windows 10 x64
Help!!!!!
I have XT1033 and i was on brazilian 5.0 soak test, after that i convert my phone to downgrade to gpe 4.4.4 and everything was fine but then i wanted to go back to stock 4.4.4 brazilian and now im stuck at the boot logo.
these are the commands i used to convert from 5.0 brazilian soak test to gpe 4.4.4
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
and these are the commands i used to convert from gpe 4.4.4 to stock brazilian 4.4.4
SET fastboot=fastboot.exe
fastboot.exe flash partition gpt.bin
fastboot.exe flash motoboot motoboot.img
fastboot.exe reboot-bootloader
fastboot.exe continue
fastboot.exe flash logo logo.bin
fastboot.exe flash boot boot.img
fastboot.exe flash recovery recovery.img
fastboot.exe flash system system.img_sparsechunk.0
fastboot.exe flash system system.img_sparsechunk.1
fastboot.exe flash system system.img_sparsechunk.2
fastboot.exe flash modem NON-HLOS.bin
fastboot.exe erase modemst1
fastboot.exe erase modemst2
fastboot.exe flash fsg fsg.mbn
fastboot.exe erase cache
fastboot.exe erase userdata
fastboot.exe reboot
exit
did i softbricked my phone or hardbricked ?
brick my moto g
My motog is brick , I updated to 5.0 and shifted in build.prop file, not launched yet , I could not successfully restore it then installed the rom 4.4.2 , then updated to 4.4.3 and when he went to 4.4.4 he gave brick and does not want to , what I do?
I'm desperate since yesterday :crying:
Lucas Amaral said:
My motog is brick , I updated to 5.0 and shifted in build.prop file, not launched yet , I could not successfully restore it then installed the rom 4.4.2 , then updated to 4.4.3 and when he went to 4.4.4 he gave brick and does not want to , what I do?
I'm desperate since yesterday :crying:
Click to expand...
Click to collapse
i'm with you, brother....i have same problem...waiting for solution
Lucas Amaral said:
My motog is brick , I updated to 5.0 and shifted in build.prop file, not launched yet , I could not successfully restore it then installed the rom 4.4.2 , then updated to 4.4.3 and when he went to 4.4.4 he gave brick and does not want to , what I do?
I'm desperate since yesterday :crying:
Click to expand...
Click to collapse
Did you read first page before flash? It s clearly stated there that some ppl bricked phones when flashed 4.4.2 then upto 4.4.3 and so on. Please next time read all that its writed...
ganeshkmr21 said:
when i plug in the phone some drivers get installed.
but my phone is not showing up in adb devices.
i flashed CMW & am running Windows 10 x64
Click to expand...
Click to collapse
Read OP, install adbdriver!
não-soi-jo said:
I have XT1033 and i was on brazilian 5.0 soak test, after that i convert my phone to downgrade to gpe 4.4.4 and everything was fine but then i wanted to go back to stock 4.4.4 brazilian and now im stuck at the boot logo.
these are the commands i used to convert from 5.0 brazilian soak test to gpe 4.4.4
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
and these are the commands i used to convert from gpe 4.4.4 to stock brazilian 4.4.4
SET fastboot=fastboot.exe
fastboot.exe flash partition gpt.bin
fastboot.exe flash motoboot motoboot.img
fastboot.exe reboot-bootloader
fastboot.exe continue
fastboot.exe flash logo logo.bin
fastboot.exe flash boot boot.img
fastboot.exe flash recovery recovery.img
fastboot.exe flash system system.img_sparsechunk.0
fastboot.exe flash system system.img_sparsechunk.1
fastboot.exe flash system system.img_sparsechunk.2
fastboot.exe flash modem NON-HLOS.bin
fastboot.exe erase modemst1
fastboot.exe erase modemst2
fastboot.exe flash fsg fsg.mbn
fastboot.exe erase cache
fastboot.exe erase userdata
fastboot.exe reboot
exit
did i softbricked my phone or hardbricked ?
Click to expand...
Click to collapse
Just follow the guide! Flashing with fastboot won't work so flash custom recovery and push a 4.4.4 stock zip.
Lucas Amaral said:
My motog is brick , I updated to 5.0 and shifted in build.prop file, not launched yet , I could not successfully restore it then installed the rom 4.4.2 , then updated to 4.4.3 and when he went to 4.4.4 he gave brick and does not want to , what I do?
I'm desperate since yesterday :crying:
Click to expand...
Click to collapse
READ OP! You didn't read it properly so you made a huge mistake!
MadL1fe said:
i'm with you, brother....i have same problem...waiting for solution
Click to expand...
Click to collapse
Same... You should have read the OP!
samsontm said:
Did you read first page before flash? It s clearly stated there that some ppl bricked phones when flashed 4.4.2 then upto 4.4.3 and so on. Please next time read all that its writed...
Click to expand...
Click to collapse
Totally agree with you....
I did that last part... :\ Guess I'll wait for Moto.
GI0\/\NNI said:
@hunterhere,
I think I found a solution!
1. Download and extract zip
2. Connect phone in fastboot mode to your PC
3. Run IMEI_fix_gio.bat
4. Should work now!
Click to expand...
Click to collapse
Hey I flashed this file now the change is that previously my both the IMEI(S) were showing 0 now 1st one is showing 0 but 2nd one has changed to null.
Secondly i request you to please come and join the below mentioned thread and please please help us all who have erased IMEI(S) with your knowledge and skills.
http://forum.xda-developers.com/moto-g/help/info-moto-g-imei0-t2925970
Edit: can you help in telling me how you modified this fsg_gio.img file? Or if you have got it from somewhere else please point...
As it is a very important file and a developer on above mentioned thread needs to know how this file got modified this will lead us further in restoring the imei numbers... as because moto g is made in a very different way... there is a lot of encryption done in its partitions which is very difficult to decrypt.
Hello, i have ZTE axon 7 ZTE A2017G model. When i bought it from china, via allieexpress, it was on stock 4.0 mifavor chinese version. It was not updating to the latest nougat. I tried updating manually via recovery mode through SD card. I was succesful to update it to 7.1.1 nougat. Unfortunately my Mobile network became completely disabled. I understand that i used an incorrect firmware. Current build number: ZTE A2017GV1.2.0B05. How and what should i do in order to restore my mobile network. I am currently living in UK. Should i completly hard reset, install chinese or Eu version, i am confused. Anyone can help me with this?
Hi,
Hardwares are different between china and europe model, therefore radio firmwares within the roms also.
I would advise you to flash the latest chinese version of the rom to go back to normal.
However if you have an unlocked bootloader, you can try flashing only the radio modem via adb.
Good luck
Cojy said:
Hi,
Hardwares are different between china and europe model, therefore radio firmwares within the roms also.
I would advise you to flash the latest chinese version of the rom to go back to normal.
However if you have an unlocked bootloader, you can try flashing only the radio modem via adb.
Good luck
Click to expand...
Click to collapse
Thank you. And maybe if you would so kind, any links for the best guide how to flash radio modem via adb?
Cheers
A bit of a late reply, I did not get any notification.
First reboot into fastboot (adb reboot bootloader, the screen ued to display fastboot on my other android phone)
After that it is a 'fastboot flash radio signed_radio.img'
You can flash every .img file that you find in a rom via fastboot (if you have issues with gyroscope, modem, radio...)
here are some common commands:
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash rpm rpm.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
It is usually fastboot flash <component> <component>.img like flash boot boot.img or flash radio radio.img...
Let us know if it solves your issue
Cojy said:
A bit of a late reply, I did not get any notification.
First reboot into fastboot (adb reboot bootloader, the screen ued to display fastboot on my other android phone)
After that it is a 'fastboot flash radio signed_radio.img'
You can flash every .img file that you find in a rom via fastboot (if you have issues with gyroscope, modem, radio...)
here are some common commands:
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash rpm rpm.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
It is usually fastboot flash <component> <component>.img like flash boot boot.img or flash radio radio.img...
Let us know if it solves your issue
Click to expand...
Click to collapse
Thanks for the reply.
Unfotrunately, i am completely new to this kind of thing. I managed to reboot into fastboot. But now im not sure what to do. Do i just put in commands? Do i need to download the radio.img files or? If you would be so kind to provide a bit more detail to this.
Thanks again
Fruktoze said:
Thanks for the reply.
Unfotrunately, i am completely new to this kind of thing. I managed to reboot into fastboot. But now im not sure what to do. Do i just put in commands? Do i need to download the radio.img files or? If you would be so kind to provide a bit more detail to this.
Thanks again
Click to expand...
Click to collapse
The usual saying is don't do that if you don't know what you are doing ! This could block your phone and you would have a hard time restoring it if you are not at ease with that sort of things.
This being said, you need to retrieve the .img file from your operating system image, put it in your adb folder (or whatever folder but you will have to add the path) and run the aforesaid commands.
i tried
fastboot flash modem non-hlos.bin
but there isnt a file by that name in the potter_NPN25.137-83.zip firmware.
should i grab another firmware or try something else?
Hmm, the firmwares should have that file included in them.
Have you extracted the stock ROM from the zip (should be about 2 GB) and copied it to the same folder as your ADB terminal?
You may wish to double check the filename case and if the file name is capitalised or not (e.g. non-hlos.bin may not be the same as NON-HLOS.bin in the file system).
Generally, if you wish to flash just the modem, provided you have all the files in your ADB directory, use the following commands:
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Ensure you're flashing the correct firmware/modem for your device - incorrect firmware/modems can cause you to lose network access/IMEIs.