Related
How to USE FASTBOOT commands in case your Device got Soft-Bricked with NO DISPLAY
Click to expand...
Click to collapse
Let's describe Softbrik:-Anything caused to your phone except damage to Hardware of your phone which put your Device into a state where it is not booting up and kept showing White, Gray, Blue or Black Screen or Either It gets stuck at Company logo Screen. This may occur if something goes wrong during Rooting, flashing Recovery or ROMs or during Updating in Recovery Mode or either being caught by some wrong software or VIRUS !!!
Preface to the Guide:
Fastboot is a command line tool used to directly flash the filesystem in Android devices from a host computer via USB. It allows flashing of unsigned partition images and also can erase partitions. Its a part of Android Developement Kit (Android SDK).
Use of FASTBOOT is disabled in production devices since USB support has been disabled in the bootloader. You must have an Engineering SPL, or an SPL that is S-OFF or Unlocked bootloader to use 'fastboot'.
After installing the Android SDK or ADB Standalone you can use 'fastboot' in addition to the more common ADB.
One can use the attached .android folder if u want to skip downloading Android SDK. (Refer Attachment)
Verify SPL S-OFF or Bootloader Unlocked:
Not required for Micromax !! But certain Production Devices like Sony HTC LG etc may need bootloader to be unlocked before carrying out this process. My simple advice to people is.. "If you enjoy experiments on your device, you must be ROOTED and to ROOT you device you may need to have unlock bootloader"
Preparations:
(1) Download attached .android.zip, Extract and place .androidfolder on C:/ drive of your PC. So the path of this folder will look likeC:/.android
(Never remove this ".android" folder from C:/ coz you will require it whenever u want to experiment with you Droid using ADB or FASTBOOT methods. I assure... You can do a lot more with it; if you really explore how to use various commands !!!)
.android folder is containing adb.exe, fastboot.exe and related drivers adb_usb.ini, android_winusb.ini AdbWinApi.dll and AdbWinUsbApi.dll and other files; all together not more than 800KB
(2) Connect Device in 'USB debugging ON' mode.
Ensure Drivers for your Device are already installed on the host computer
Note: I recommend you should always keep USB Debugging opetion 'ON' as it only can help you, in case, your device get SoftBricked and you cant see anything on Device Screen. Remember that with USB debugging 'OFF' your Device can't communicate with your Host Computer.
(3) Host Computer Ability to Launch Command Prompt:
On Windows-XP or earlier, to start ADB (Android Debug Bridge) You need to locate your folder containing adb.exe where as Windows-7/Vista/Other-Latest-OS can directly launch command prompt from the Folder itself by Shift+Right Click on Mouse and Selecting "Open Command Prompt from here".
Hence 'Locating 'adb' folder-steps' are for XP users only, However higher OS users can skip it and can directly start giving 'adb' commands after opening cmd from .android folder.
(4) So now, Open Command Prompt (in Windows XP), it will return like this:
Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\USERNAME>
(As our adb.exe is in C:/.android.... we will type: Cd C:\.android)
C:\Documents and Settings\USERNAME>Cd C:\.android (Hit Enter)
C:\.android>
Let's give command to detect attached device by writing: 'adb device'. On hitting enter it will list all devices attached to your PC.
Code:
C:\.android>adb devices
List of devices attached
XXXXXXXX-XXXX device
Now u can do a lot while your Device is attached in 'adb mode' e.g.:
Code:
1. Rebooting into Bootloader (FASTBOOT)
2. Installing apps on as /system/app or /data/app
3. Copying Files to/from your SDCARD
4. Pulling Files or Apps already installed on your /system or /data partition
To Understand adb commands and how they work please read:
http://developer.android.com/tools/help/adb.html#commandsummary
Let's come back to ISSUE: "We have a SOFTBRICKED devices !!!"
(1) Booting into FASTBOOT mode:
Let's come back to'fastboot' as we need to flash new ROM or to apply update.zip in a Softbricked deviceNote: Let your device remain connected to PC and don't disconnect untill You finish you job-successfully and get your Device again in working Factory Condition.
""fastboot reboot-bootloader" This command is used to reboot your device into bootloader i.e into fastboot mode) and In this Mode your device will stuck into boot logo only and u cant operate it. ;D Well we are not concerned as we already have a bricked device with no screen display !!!. Lets go ahead...on cmd follow:
Code:
C:\.android>adb reboot-bootloader
C:\.android>fastboot devices
XXXXXXXXXXXX fastboot
(2) Unlocking-ReLocking Bootloader:
(Skip if u working with pre-unlocked devices)
C:\.android>fastboot oem unlock
...
SUCCESSFUL
finished. total time: 118.063s
Click to expand...
Click to collapse
(Accept/Decline warning on your devices screen. Select YES to Unlock)
(Once ROM is flashed) To relock Bootloader use command: fastboot oem lock:
Code:
C:\.android>fastboot oem unlock
...
SUCCESSFULL
finished. total time: 118.063s
(Accept/Decline warning on your devices screen. Select YES to ReLock)]
(Skip if u working with pre-unlocked devices)
(3)Get 'Recovery.img' and 'Update.zip' for your Device:
Lets Wipe the Data and then proceed to Flash new ROM/Update.zip
IMPORTANT: Copy the stock recovery.img and your devices' Update.zip[ in .android folder(You can get it even by searching it in this forum or by Googling for it..) So I assume that you have it....in your .android
Abbreviations:
recovery.img = Stock Recovery of your Device
Update.zip = Update Package/Stock ROM of your Device
Let's start wiping and updating process with following commands:
(4)Wiping Old Data and Flashing new Update.zip:
Code:
C:\.android>fastboot -w
SUCCESSFUL
C:\.android>fastboot update Update.zip
(Here Replace Update with Full Name of your any Update.zip that you copied to .android folder)
Your phone will update and automatically reboot into the Factory State. Cheers !!!
Note: Its important to spell the file name correctly that u want to flash/update. No space between name are allowed. This process will only be successful if your device is still carrying recovery partition 'intact'.
.....If above wiping/updating FAILS....
If you still in "No Display State", extract update.zip to .android folder (U can use 7zip).
You will find following main .img files, each incorporate specific partition on any android device. In our case we can extract following:
boot.img -The main kernel and initrd
recovery.img -A 'backup' kernel, initrd, and OS 4 sysm recovery/maintanance
sytem.img -The main OS
userdata.img -User data and settings
splash.img -Has Boot image. can be splash1 as well.
cache.img -Temp storage
...there can be similar partition names depends on your device type.... but basically these 6 partitions constitute a ROM. Copy all of (6) files to .android folder. (Henceforth, we can use this recovery.img as stock recovery for your device.)
"As your device is bricked/corrupted, we need to erase all old Partitions and flash (rewrite) new partitions that we have extracted from Update zip and placed in .android."
(1) Lets erase all partitions first (one by one)using: fastboot erase <partition>
Code:
C:\.android>fastboot erase system
Successful
C:\.android>fastboot erase recovery
Successful
C:\.android>fastboot erase boot
Successful
C:\.android>fastboot erase userdata
Successful
C:\.android>fastboot erase splash
Successful
C:\.android>fastboot erase cache
Successful
(2) Continuing with Flashing new partionsusing the Images copied in .android:
Command: fastboot flash <partition> <partition_name.img>
Code:
C:\.android>fastboot flash boot boot.img
Successful
C:\.android>fastboot flash recovery recovery.img
Successful
C:\.android>fastboot flash system system.img :(here people gen. get stuck
Successful
C:\.android>fastboot flash userdata userdata.img
Successful
C:\.android>fastboot flash splash splash.img
Successful
C:\.android>fastboot reboot
If all successful, Your phone will update and automatically reboot into the Factory State. Cheers !!!
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
..If you are Unable to flash 'system.img' successfully...
Reason: Your device is not allowing to format and rewrite 'system' partition manually. If your device is Rooted then probably such failure will never occur.
Let's overcome this Issue as well...Try Following...
First, Understand current State of Device...
We Wiped out old partitions and Flashed new partitions except :-\ system :-\ So No System on your Device at present.
What we will do now..
We will now wipe all partitions again
We will then flash only recovery.img saved in .android folder
We will use update.zip saved in .android folder to Flash it using SD Card.
We will copy update.zip on SD Card (using adb). If you can do it manually using a card reader skip step-II in below process.
Step-I: Wiping 'partitions' and Flashing 'recovery.img':Let's wipe all partitions again:
Code:
C:\.android>fastboot -w
C:\.android>fastboot reboot-bootloader
C:\.android>fastboot flash recovery recovery.img
C:\.android>reboot
Step-II: Copy update.zip on SDCARD
Code:
C:\.android>adb push update.zip /data/sdcard
Step-III: As you can't manage to see what is happening on screen(No Display) hence Don't do mistakes here, read carefully and follow exactly:
1.Reboot Device into Recovery Mode:
On cmd type:
Code:
C:\.android>adb reboot recovery
2.Now Press 'Volume(-)' button ONCE. (Once means 'once only'-if you did mistake here repeat the Step-III)
3.Press 'Power' Button TWICEand Leave you Device for some 10 Minutes time.
If phone don't get alive in 10 Minutes Repeat Step-III again.
You may not able to see but Your phone will update and automatically reboot into the Factory State. Cheers !!!
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Explaining Last Step:
We used simple logic in last procedure/ Its nothing but updating using Recovery Mode. Always remember Custom Recovery of Micromax A56/57 has following options: (May be diferent for other devics)
As the default curser in recovery UI remains on Option-1 and we needed to choose Option-2.
Hence to select "Apply update for sdcard" we pressed 'Vol(-)'ONCE and then to Confirm and execute that option Tapped 'POWER' button TWICE.
Hope this Guide helped you or ...will Help you to help others !!!
One quick question...
What if my device detected in fastboot but not in adb devices?
How to enter recovery or solve my softbricked issue?
RmatriX1218 said:
One quick question...
What if my device detected in fastboot but not in adb devices?
How to enter recovery or solve my softbricked issue?
Click to expand...
Click to collapse
bro if your volume + key is not working so how can u say that your device is soft bricked...
i think you should repair your volume keys and than try to move to recovery...
& one more thing without installing all drivers/thing u will not be able to access fastboot mode.....
Hey!!
Please please help me!!
I have MICROMAX a54 ninja 3.5.my mobile stuck in bootloop and soft bricked!!
When I turn on my devices it stuck in logo ninja 3.5.
I also try to go in recovery mode by pressing volume up+home key+lock key!
But it doesn't enter in recovery mod!!
Now what am I do??
Please please help me.
Thank you in advance..
I think for going in recovery:-
1. Press and hold power button.
2. While holding power key, press and hold both volume keys, (vol+ & vol-)
3. When mmx logo comes it will display a message vol(+) for recovery and vol(-) for fast boot then again press vol(+) for once,
And now your in recovery
I lost my recovery.
And I can't go into recovery mod!!
Please help me
Sent from my YU5010 using XDA Free mobile app
What do u mean by, lost your recovery???
I am not able to go to recovery!!
When I m try to gobto recovery mod it doesn't happen only logo ninja 3.5 is there
Sent from my YU5010 using XDA Free mobile app
Ok ok just try flashing your official rom
---------- Post added at 10:35 AM ---------- Previous post was at 10:17 AM ----------
Aakash mehta said:
I am not able to go to recovery!!
When I m try to gobto recovery mod it doesn't happen only logo ninja 3.5 is there
Sent from my YU5010 using XDA Free mobile app
Click to expand...
Click to collapse
Just download your official rom, Your device driver for pc, and install the rom to your device using "sp flash tool"
Please give me steps and link of above method!!!
Thank you for help me
Sent from my YU5010 using XDA Free mobile app
Aakash mehta said:
Please give me steps and link of above method!!!
Thank you for help me
Sent from my YU5010 using XDA Free mobile app
Click to expand...
Click to collapse
1.First download your stock recovery for your mmx a54 from here http://d-h.st/D7G
2. Now download sp flash tool from here https://drive.google.com/file/d/0B9S_ERLSMngHVE9Qc25ObGU1UU0/edit?pli=1 install it to your pc.
3. Download drivers for a54 from here singledrivers.blogspot.in/2013/12/micromax-ninja-a54-usb-driver-for.html?m=1 install the driver to your pc.
4. Download your phone stock rom from here http://d-h.st/fg2 place it in your external sd card(mmc) of your device.
5. Download scatter file from here www.mediafire.com/view/rvz1c5tiifx7yck/MT6575_Android_scatter.txt
6. Now run sp flash tool in your pc, browse to the scatter file.txt, turn off your phone remove the battery and connect it through usb to your pc. (Connect the device without battery)
7. Now select the recovery tab in sp flash tool browse to the recovery.img file (Which we hv downloaded before). Now select the option download in sp flash tool it will Start flashing your stock recovery to the device, A green tick marked will be comes as the flashing complete, now remove your device from pc.
8. Now goto recovery by vol key combination.
9. Now select apply update from sd card and select the stock rom.zip file
10. When flashing done then, Wipe Cache Partition and factory data reset of your device.
Now just select reboot device now it will take around 10min to boot for the first time so wait. Hope this helps you
Thank you for giving me whole information!!
Sent from my YU5010 using XDA Free mobile app
Aakash mehta said:
Thank you for giving me whole information!!
Sent from my YU5010 using XDA Free mobile app
Click to expand...
Click to collapse
Don't say thanks my Buddy just press thanks button.
Hello
I tried sp tool flasher!!
I followed all steps which were given by you!!
BT although not any change in my mobile..
When I tick recovery and then browse recovery.img file and click download button but nothing had happened..
It didn't detect my mobile and didn't go for procedure!!
So now what am I do???
You helped me very much!!
Bu please further help me...
Sent from my YU5010 using XDA Free mobile app
Hv u installed driver properly, just trust me try different usb ports
Yeah i installed drivers properly!!!
Sent from my YU5010 using XDA Free mobile app
So your device is not recognizing by sp flash tool r8
I think so
Sent from my YU5010 using XDA Free mobile app
micromax a210
I have a problem with fastboot stuck on system erasing on adb fastboot mood also userdata and cache only flash recovery and boot img sp flash not working with this phone I do other mtk android with sp tool successfully what I do
What if the device is recongised in adb as : (device name) recovery, but can't actually boot into recovery (twrp) and thus when entering the command : adb reboot fastboot it can never actually boot into fastboot ?
Are there any adb commands that can do the trick or is it game over ?
whenever I try to flash the TWRP I get an error saying:
writing 'recovery'...
FAILED <remote: invalid signature and data>
I'm using p1a42 twrp. with a p1a41.
Is your device lenovo vibe p1 or lenovo vibe p1m
Reply me and i will give you the solution....
Regards milkyway3
milkyway3 said:
Is your device lenovo vibe p1 or lenovo vibe p1m
Reply me and i will give you the solution....
Regards milkyway3
Click to expand...
Click to collapse
I'm sorry that I didn't make it clear. It is a P1 and has it's build number is P1a41_S271.
First of all let me know weather you flashed the recovery img with or without the pc
If with pc then using which software.......
Regards milkyway3
milkyway3 said:
First of all let me know weather you flashed the recovery img with or without the pc
If with pc then using sp flash tools or some other software
Regards milkyway3
Click to expand...
Click to collapse
Recovery img with pc using qfil and adb.
First I tried with QFIL, but then I tried to do with basic adb and fastboot. sp flash tool is what I never heard of. Should I be trying to do it with that?
[WARNING:I AM NOT RESPONSIBLE IF ANYTHING HAPPENS TO YOUR DEVICE.DO IT AT YOUR OWN RISK]
Download adb fastboot drivers using this link:
http://androidhost.org/hUhuh
Download cwm recovery using this link:
http://androidhost.org/hUhuh
Now follow the steps:
Step 1: Download ADB fastboot drivers and install it on PC.
Step 2: Download CWM recovery for Lenovo Vibe P1.
Step 3: Copy this file to your PC where you installed ADB fastboot drivers.
Step 4:Now Go to directory where you have installed ADB fastboot drivers and press and hold shift key and right click anywhere inside the folder at the empty space and choose open command window here.
Step 4: Now enter the following commands.
Code:
adb reboot bootloader
fastboot oem unlock
fastboot flash recovery.img OR fastboot boot recovery.img
fastboot reboot
After first command your device will reboot in fastboot mode. The second command will flash recovery image on your device. The third command will reboot your phone.
All the best:good::good:
Please press the thanks button if it was helpful.
Regards milkyway3
Thank you for your help, I'll do as instructed.
There was no img file in the link, just cwm zip. So there was nothing to flash, at least nothing in a way that I know of.
nnmaiden said:
There was no img file in the link, just cwm zip. So there was nothing to flash, at least nothing in a way that I know of.
Click to expand...
Click to collapse
You have to unzip the zip file using winrar or any other such software and then copy recover.img file where you have kept the adb drivers
Regards milkyway3
That's what I was trying to say. Unless I downloaded the wrong thing somehow, or my pc has some sort of an issue, there's no img file inside none of the zipped folders.
nnmaiden said:
That's what I was trying to say. Unless I downloaded the wrong thing somehow, or my pc has some sort of an issue, there's no img file inside none of the zipped folders.
Click to expand...
Click to collapse
Sorry for the wrong link
This is the correct link for direct download
https://www.androidfilehost.com/?fid=24591000424964938
Follow these steps:
Download the TWRP recovery image to be installed on your Android.
Enable USB Debugging under Developer Options.
Install ADB and Fastboot utility on your PC via
https://devs-lab.com/download-lenovo-usb-drivers-adb.html
(extract the above rar and install exe file)
Go to the directory where you have downloaded the TWRP image file and then open the command console or termianl on this directory on your PC. To open a command window on Windows OS in the current directory, press shift + Right Click anywhere on Windows explorer, or some folder. Then on the menu opened, just press the “w” key on the keyboard or select “Open command window here” to open a command window.
Now connect your Android to the PC using a USB cable.
Enter the following command on the command window opened:
adb reboot bootloader
to put your Android into bootloader mode where you can flash/install the TWRP recovery.
If your Android device asks permission such as “Allow USB debugging” then just tap on OK to proceed.
Now when your Android is on the bootloader mode just execute the following command on the console:
fastboot flash recovery twrp-3.0.x.x-xxx.img
While executing this command make sure to replace the twrp-3.0.x.x-xxx.img with the actual file name of the TWRP that you have downloaded for your Android.
Wait for the TWRP to be flashed. Once it is done execute the following command:
fastboot reboot
on the command console and done, your Android is now installed with TWRP recovery.
Hope this helps you out
Regards milkyway3
I'll do it as soon as I can. Thanks again.
nnmaiden said:
I'll do it as soon as I can. Thanks again.
Click to expand...
Click to collapse
Hey,
I would prefer you thanking me using the thanks button instead of saying it in comments
And by the way
You're welcome
Regards milkyway3
failed process
When I flash twrp in vibe P1 it's show fail ,I try many time bt fail every time ,plz suggest me solution
I try this method many bt fail every time,my vibe P1 bootloader is unlocked
Is this method applicable to vibe p1 c58 model (2gb ram 16gb storage) model? Thanks
milkyway3 said:
[WARNING:I AM NOT RESPONSIBLE IF ANYTHING HAPPENS TO YOUR DEVICE.DO IT AT YOUR OWN RISK]
Download adb fastboot drivers using this link:
http://androidhost.org/hUhuh
Download cwm recovery using this link:
http://androidhost.org/hUhuh
Now follow the steps:
Step 1: Download ADB fastboot drivers and install it on PC.
Step 2: Download CWM recovery for Lenovo Vibe P1.
Step 3: Copy this file to your PC where you installed ADB fastboot drivers.
Step 4:Now Go to directory where you have installed ADB fastboot drivers and press and hold shift key and right click anywhere inside the folder at the empty space and choose open command window here.
Step 4: Now enter the following commands.
Code:
adb reboot bootloader
fastboot oem unlock
fastboot flash recovery.img OR fastboot boot recovery.img
fastboot reboot
After first command your device will reboot in fastboot mode. The second command will flash recovery image on your device. The third command will reboot your phone.
All the best:good::good:
Please press the thanks button if it was helpful.
Regards milkyway3
Click to expand...
Click to collapse
I did the exact same way but still shows the error "failed (status read failed (too many links)) lenovo vibe p1". Can anyone help please?
Hi to everyone!
I just bought a Lenovo Vibe P1 version P1C72 ( 3gb Ram and 16GB memory) from China and it came with Android 6.0.1 installed, VIBE UI.
Unfortunately there are o lot of bugs in this version, and i want to downgrade my phone to Android 5.1.
Could somebody tell me if i can do that by following the method from androidMTK.com, using QcomDloader Tool and lenovo P1a42 stock rom?
Or there is another way to downgrade my phone, because that seller guy from China told me there is no way to go back to Android 5.1 ?
Thanks in advance !
leviathanus said:
Hi to everyone!
I just bought a Lenovo Vibe P1 version P1C72 ( 3gb Ram and 16GB memory) from China and it came with Android 6.0.1 installed, VIBE UI.
Unfortunately there are o lot of bugs in this version, and i want to downgrade my phone to Android 5.1.
Could somebody tell me if i can do that by following the method from androidMTK.com, using QcomDloader Tool and lenovo P1a42 stock rom?
Or there is another way to downgrade my phone, because that seller guy from China told me there is no way to go back to Android 5.1 ?
Thanks in advance !
Click to expand...
Click to collapse
The nfc will not work with 01a42 lollipop, and i dont have chinese 5.1 sorry. Maybe u can try some good custom rom from the developers
If only NFC is the problem, i don't mind. I'm not using it, anyway.
But the method, using QcomDloader Tool, or another tool, is safe?
I'm not risking to brick my phone?
I'm still thinking to flash my phone using Qfil and put version P1a42_S135_1510131022_Q20248.2_ROW instead of Android 6.0 Marhmallow and get rid of those problems.
Could it be done such downgrade?
also looking to upgrade my p1a42 to nougat rom that is stable no bugs. is there a reason you gave cwm instead of twrp? say we go with cwm are there any rom it will not flash or just about any rom it will handle? i prefer twrp by the way there is one for the p1 but people are having issues flashing it. your advice is truly appreciated.
Hi, I am i dire straits. I have a pixel xl running pure nexus, rooted and on tmobile. I am trying to get back to completely stock. i tried followig the instructions but somewhere I messed up. Currently phone will just bootloop. I went into cmd, typed adb devices, nothing came up so stupid me, I continued anyways with flash-all.bat, something went wrong in command prompt, then i proceeded to reboot from fastboot, this is where i am now. I have attached pictures of the command prompt screens and of the folder in adb fastboot on my pc that I think contained all the files. I do't know where I went wrong. If you can help, it would be greatly appreciated. I can only correspond via pc. Please, I hope someone can help me.
If someone has the time to walk me through step by step, it would much appreciated.
Doesnt looked bricked to me
maybe your factory image is incomplete.
Flash the parts individually see what happens.
Commands i use. note you need to use your own paths or copy mine
) Execute fastboot commands
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-bootloader
fastboot boot c:\_PIXEL_XL_\twrp.img
In TWRP, install twrp.zip
Reboot into the installed recovery
In TWRP, install supersu.zip <--- if you want to root.
5 Still in twrp flash verifiedboot signer.zip
6 Reboot
parakleet said:
Doesnt looked bricked to me
maybe your factory image is incomplete.
Flash the parts individually see what happens.
Commands i use. note you need to use your own paths or copy mine
) Execute fastboot commands
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-bootloader
fastboot boot c:\_PIXEL_XL_\twrp.img
In TWRP, install twrp.zip
Reboot into the installed recovery
In TWRP, install supersu.zip <--- if you want to root.
5 Still in twrp flash verifiedboot signer.zip
6 Reboot
Click to expand...
Click to collapse
No offence but i am lost by what you said, I am trying to get back to completely stock. Is part of my issue the fact that command prompt didn't detect my device? or no?
I'm not exactly sure what to do with the information you shared, sorry
I the tutorial i found it says to make sure the command prompt sees your device but doesnt say what to do when it doesnt see it.
Also, I downloaded the may factory image, i believe it was version O
Am I suppose to use the O image or the L image (verizon). I am on tmobile. I used the O image when i ran into trouble
jreink01 said:
Am I suppose to use the O image or the L image (verizon). I am on tmobile. I used the O image when i ran into trouble
Click to expand...
Click to collapse
If you did not get your phone from Verizon use this
7.1.2 (N2G47O, May 2017)
Download the zip
unpack all the zip files some are nested so unzipping one creates more keep unzipping until there are no more then gather the following img files
bootloader.img
radio.img
boot.img
system.img
system_other.img
vendor.img
modem.img
Some of those names are cut down as i hate typing long strings, jsut rename them as such.
Create a folder on root of c:\_PIXEL_XL_
put all the files there.
You will use way less files than you unpacked
once you have done that run the following commands
copy and paste
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
After last reboot just wait and you will be back at stock
if that doesnt work
Download latest version of TWRP place it in C:\_PIXEL_XL_
rename it twrp.img, again i hate typing long strings
from bootloader run
fastboot boot c:\_PIXEL_XL_\twrp.img
This will take you into twrp
you might need to wipe system and cache and data,
From memory the fourth entry at bottom is internal memory or user data, in any event if you do not check that your data stays on the phone.
Once you have wiped the other 3 rerun the fastboot commands and you will be back at stock
add the twrp and supersu commands from earlier to add root.
dont forget the signatureverify.img if you are doing that.
good luck.
you arent bricked
you just need to find the correct combination of steps to get your phone where you want it to be
Thanks for the response. I am having a hard time with this, the zip file i downloaded from the google website, when i open it, there are only 6 files, 1 of which is a zip file (marlin). When I open marlin it shows a bunch of files, none of which you mentioned. I am confused, was wondering if you would be nice enough to walk me through this over the phone, i would be really grateful.
Is there anyone that can walk me through this this on the phone, the more i try to understand this, the more cofused i get. pLeASE!!!!
jreink01 said:
Is there anyone that can walk me through this this on the phone, the more i try to understand this, the more cofused i get. pLeASE!!!!
Click to expand...
Click to collapse
Yes, i sent you a PM.
HALV0RS3N said:
Yes, i sent you a PM.
Click to expand...
Click to collapse
thanks, sent you my #
Okay so I had the exact problem yesterday. To to the Google developers site and download the official Google pixel or xl 7.1.2 nougut ota update. Once that's downloaded, go to your phone, I had all the exact same screens on my phone so it should work. Hold down the power button until it completely shuts down. Then hold the power and volume down to go to recovery mode, if it goes back to the ext 4 screen, try it again until it goes to recovery mode, then on command prompt type, fastboot boot twrp.img then once it's in twrp, go to advanced-then adb sideload and click both boxed and then swipe to enter sideload. Then on your computer, type adb sideload "file name for Google update" and hit enter. That should do the trick. Like I said, I had the exact same problem yesterday
---------- Post added at 06:56 PM ---------- Previous post was at 06:50 PM ----------
Also, I forgot to mention, download the twrp image file from the Internet. Shouldn't be hard to find just make sure it's the latest. Put that file in the adb file on your computer same with the Google update for your phone. Do not unzip either file. That's very important. DO NOT UNZIP THE UPDATE File. When you type in the twrp.img make sure you type img. And when you flash the update, make sure at the end of the file name you put
.zip ex( marlinpixelxl7.1.2.zip)
jreink01 said:
Hi, I am i dire straits. I have a pixel xl running pure nexus, rooted and on tmobile. I am trying to get back to completely stock. i tried followig the instructions but somewhere I messed up. Currently phone will just bootloop. I went into cmd, typed adb devices, nothing came up so stupid me, I continued anyways with flash-all.bat, something went wrong in command prompt, then i proceeded to reboot from fastboot, this is where i am now. I have attached pictures of the command prompt screens and of the folder in adb fastboot on my pc that I think contained all the files. I do't know where I went wrong. If you can help, it would be greatly appreciated. I can only correspond via pc. Please, I hope someone can help me.
If someone has the time to walk me through step by step, it would much appreciated.
Click to expand...
Click to collapse
Looking at your screen shot you didn't let the file finish flashing. It sticks at the "does not contain" for a bit before it continues.
You were doing it right. You just didn't wait.
If it wasn't going to work it would eventually give you a failure and jump to the command prompt.
jreink01 said:
Hi, I am i dire straits. I have a pixel xl running pure nexus, rooted and on tmobile. I am trying to get back to completely stock. i tried followig the instructions but somewhere I messed up. Currently phone will just bootloop. I went into cmd, typed adb devices, nothing came up so stupid me, I continued anyways with flash-all.bat, something went wrong in command prompt, then i proceeded to reboot from fastboot, this is where i am now. I have attached pictures of the command prompt screens and of the folder in adb fastboot on my pc that I think contained all the files. I do't know where I went wrong. If you can help, it would be greatly appreciated. I can only correspond via pc. Please, I hope someone can help me.
If someone has the time to walk me through step by step, it would much appreciated.
Click to expand...
Click to collapse
i had the same issue and this worked
https://forum.xda-developers.com/showpost.php?p=70972735&postcount=3
dont follow it word for word as that its not the XL version in the post.
RedBlueGreen said:
i had the same issue and this worked
https://forum.xda-developers.com/showpost.php?p=70972735&postcount=3
dont follow it word for word as that its not the XL version in the post.
Click to expand...
Click to collapse
OP was flashing to stock. Didn't let it finish though.
I'M NOT AT ALL RECOMMENDING Y'ALL TO TRY THIS OUT ! CUSTOM ROMS WILL COME SOON WHICH IS FAR BETTER THAN GSIs
PLEASE FOLLOW THIS GUIDE AT YOUR OWN RISK !, THIS GUIDE MIGHT BE THE SAME FOR MOST DEVICES BUT IM SPECIFICALLY MAKING THIS FOR G40 FUSION / G60
GSI IS NOT MADE SPECIFICALLY FOR A DEVICE THEREFORE IT MAY DAMAGE YOUR DEVICE AND IM NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR DEVICE, SO DON'T BLAME ME IN THE END !
TO FLASH GSI THROUGH FASTBOOT BOOTLOADER NEEDS TO BE UNLOCKED AND YOU WILL NEED A PC/LAP WITH PLATFORM-TOOLS (ADB & FASTBOOT)
IF UR RUNNING A CMD FROM 'PLATFORM-TOOLS' FOLDER, YOU MIGHT WANT TO ADD ./ BEFORE TYPING ADB/FASTBOOT FOR EVERY COMMAND
GET THE LATEST PLATFORM-TOOLS FROM HERE.
OK, So First Step will be to download a GSI, and for that my go-to places will be NipponGSI or GSITutorials.
Try not to go for MIUI or OOS GSI because they never booted when i tried them ( it will be a waste of time, but u can still try if u want to )
Now the files from NipponGSI will be in a img.gz, just extract it using rar/7zip whereas when extracting the downloaded file from GSITutorials, it shall come as a folder. just take the system.img and vbmeta.img
Store the .img files inside the 'platform-tools' folder & rename it something that u can type easily so that u wont have to worry later. ( For Users who downloaded the GSI from GSITutorials, copy both the system.img and vbmeta.img to platform-tools and u wont need to rename it since its already in a easy-to-type manner )
Now that you have all the files set up, reboot your mobile phone to fastboot by powering off your phone then pressing both Power Button + Volume Down Button together until a fastboot until a "belly-open android" image comes with many text below it.
Open your 'platform-tools', if you're in Windows ( which presumably most ppl would be ) just run Command Prompt as Admin and type cd "path to your platfrom-tools folder" and click enter and now type ur adb/fastboot commands. ( this should be done everytime u want to use adb )
Now that you have opened platform-tools and have it all ready, connect ur mobile to the computer/laptop via USB Cable and then type fastboot reboot fastboot.
( ik, you might think this step is silly but in G40F/G60 and many other devices there's a fastboot and a fastbootd. and the one we are in now is fastboot and the one we will go to after entering the command will be fastbootd )
Now that you're in fastbootd, just type and enter fastboot --disable-verification flash vbmeta vbmeta.img reboot fastboot, ( ppl who used GSI from NipponGSI need to have a vbmeta.img for this command to work, which i'll have attached below. just download and copy that file to platform-tools directory )
Now after the fastboot has rebooted back to fastboot, type fastboot erase system flash system "name of the gsi/img file".img reboot recovery ( for GSIs from GSITutorials, it should be system.img, for GSIs from NipponGSI it would be a long name which you can rename like said in 3rd step ), Edit : You've must type this command " fastboot delete-logical-partition product_a " before you do the above command when you do this for the first time, else you'll get an error saying " FAILED (remote: 'Not enough space to resize partition') "
You will end up in a screen with an image of an "Android with belly open with a warning symbol" and a text saying "No Command", this is the recovery. Just hold the power button and press volume up button once to get all the options in the recovery, now use ur volume buttons and navigate to Wipe data/factory reset and press power button once, again navigate to Factory data reset and press power button once. ( You have now done the alternative for fastboot -w, which doesnt work in motorola devices as their partitions are not supported by platform-tools )
After you've did the above step, navigate to Reboot system now and press power button once and then your phone would reboot to your installed GSI, if it fails to boot then you dont have to worry, you can always revert back to the stock rom using LMSA which unfortunately wouldn't be applicable to users in OS other than Windows
USING LMSA TO REVERT BACK TO STOCK ROM
Just install LMSA and connect ur device to computer while ur phone is in fastboot mode ( power + volume down ), and the device will be automatically recognized and just click on "Rescue my Device" and follow their instructions and ur device will be back to stock rom ( Internet connection needed with capacity to download 2/3gb of firmware )
HOPE IT HELPS,
A QUICK NOTE
GSIs is not great for daily users, currently Fingerprint and voLTE doesnt work and u cant change refresh rate, depends on which device's GSI u use, eg: Pixel 5's A12 GSI has 90hz option
Hello,
Thank you for the tutorial.
Also, does the vbmeta file need to be from the image you're trying to install? Can it be the default vbmeta from stock ROM instead, in case you don't have access to the vbmeta from the img file?
Maybe some of these questions are stupid. And I apologise for that. I've still got a ton of things to learn.
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