Related
Hey everyone.
After recently hard-bricking my Google Nexus 7 2012 (nakasi/grouper) I managed to unbrick it using NvFlash. As the official guide only taught us how to back up the blob files, I had to experiment a bit.
So, after only a few hours of messing with NvFlash commands, I found a solution to unbrick the Nexus 7 by reflashing the bootloader.
IMPORTANT! This guide requires that you have already made a back up of your device's blob files by using AndroidRoot.Mobi's tutorial, located here: http://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
Step 1: Download and Install the APX Drivers
From a powered off state, connect your hard-bricked Nexus 7 to your computer, then hold down the power and volume-up buttons until your computer recognizes your device.
Download and extract the Universal APX Drivers package from the download section below. Open the Windows Device Manager, right-click on anything that resembles your Nexus 7 or an APX device and click Update Driver.
Instruct Device Manager to search for drivers in the recently extracted driver folder.
If Windows displays an error while installing the drivers, you may need to disable Driver Signature Enforcement via Windows Startup Settings.
Step 2: Set Up NvFlash
Download and extract the NvFlash package from the download section below. Open a terminal window in the recently extracted NvFlash folder. Ensure your Nexus 7 is in APX mode (power and volume-up).
Type "wheelie --blob blob.bin" without the quotes. If necessary, replace "blob.bin" with the location of your Nexus 7's blob.bin file.
NvFlash should now load, and the Google boot logo should appear on your Nexus 7.
Step 2.1 OPTIONAL: Boot the system
To test NvFlash's connection with your Nexus 7, type "nvflash -r --download 5 eks.img" without the quotes. If necessary, replace "eks.img" with the location of your Nexus 7's blob.bin file. Your Nexus 7 should reboot into the ROM you previously had installed. Just keep in mind this is a temporary way of bypassing the bootloader to boot the system; the device is technically still bricked.
Step 3: Flash the bootloader
Type "nvflash -r --download 4 bootloader.img" without the quotes. Replace "bootloader.img" with the location of the bootloader found in any Nexus 7 stock factory image. NvFlash will flash the bootloader and boot to Android.
Step 4: Access the bootloader
By now, your Nexus 7 should be unbricked. However, to be on the safe side, I recommend that you reboot into the bootloader and flash whichever factory image you find to be the most stable.
Congratulations! If you completed the above steps and are able to access the bootloader, you have successfully unbricked your Nexus 7. I recommend that in order to prevent hard-bricks in the future, make as many backups of your "blob.bin" and "eks.img" files as you can. Keep them on multiple disks, upload them to the cloud, share them with your Facebook friends or even burn them to a CD. You cannot complete the above steps without them.
See you next time.
too bad I dont have a backup of the blob files. Is there a workaround for this? my nexus 7 is stuck on Erasing and I cant access bootloader no matter how I tried. Erasing is stuck no matter how many hours. It's stuck in erasing until its drain and when I full charge it and turn it on, it goes back to that.
too bad I dont have a backup of the blob files. Is there a workaround for this? my nexus 7 is stuck on Erasing and I cant access bootloader no matter how I tried. Erasing is stuck no matter how many hours. It's stuck in erasing until its drain and when I full charge it and turn it on, it goes back to that.
Click to expand...
Click to collapse
As long as the device displays something on the screen, it's most likely not bricked.
Could you please post a screenshot of what's showing on the Nexus 7's screen, and tell me which version of Android you were using?
I am using the latest 5.1 image from google. I just factory resetted. The screen stayed with android mascot on the center and label "ERASING" but man hours has passed to the point of loosing battery but can't get pass through it. Upon loosing battery, it goes back to "ERASING". I cant still charge offline but if I turn it on it goes back to "ERASING" also. If in that screen I press UP+Power, it shows "Formatting /data" but it is stuck there.
Here are the Pictures:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Are you able to access the bootloader? Try turning off your Nexus 7 and holding down the power and volume down buttons.
You should see a screen like this:
Before I can access that but now I can't. Everytime I try to hold power button to turn off it will reboot instead. If I try to hold vol down +power button before google logo appears, theres no effect
From recovery mode, hold the power button until the screen goes blank, then immediately release the power button. After that, immediately hold the power and volume down buttons BEFORE the Google logo appears.
This is because the bootloader is a low-level part of the device, and appears before anything else.
If you wait until the Google logo appears before holding the volume down button, it will have been too late, and you'll need to try again.
Calvin Hogg said:
From recovery mode, hold the power button until the screen goes blank, then immediately release the power button. After that, immediately hold the power and volume down buttons BEFORE the Google logo appears.
This is because the bootloader is a low-level part of the device, and appears before anything else.
If you wait until the Google logo appears before holding the volume down button, it will have been too late, and you'll need to try again.
Click to expand...
Click to collapse
yes that is what I am exactly doing. as soon as the screen goes blank i immediately press and hold power+vol down before google logo appears. After that all it does is either turns off again or go to that stuck ERASING part. I can do this on this nexus 7 before but now I can't. On my Nexus 5 I can do this trick to access bootloader
amnher said:
yes that is what I am exactly doing. as soon as the screen goes blank i immediately press and hold power+vol down before google logo appears. After that all it does is either turns off again or go to that stuck ERASING part. I can do this on this nexus 7 before but now I can't. On my Nexus 5 I can do this trick to access bootloader
Click to expand...
Click to collapse
You could try the following:
- Open the Nexus 7 by sliding a credit card around the edge, and pulling it open with a fingernail
- Remove the battery's connector from its slot and leave it out for at least an hour
- Reconnect the battery and immediately hold the power and volume down buttons (with the cover off they look like little grey circles)
Refer to the images below for the location of the battery and power/volume buttons.
I have the same problem with my nexus stuck on APX mode . Bad news is i dont have a backup of the blob files... Is there another way to use your backup or something similar ?
adybaesu said:
I have the same problem with my nexus stuck on APX mode . Bad news is i dont have a backup of the blob files... Is there another way to use your backup or something similar ?
Click to expand...
Click to collapse
Bad news for you: No, there is no chance. Either you've created 'your' blobs before or ...
Calvin Hogg said:
You could try the following:
- Open the Nexus 7 by sliding a credit card around the edge, and pulling it open with a fingernail
- Remove the battery's connector from its slot and leave it out for at least an hour
- Reconnect the battery and immediately hold the power and volume down buttons (with the cover off they look like little grey circles)
Refer to the images below for the location of the battery and power/volume buttons.
Click to expand...
Click to collapse
Ill try that but you think that the volume down button can also be busted resulting not able to enter fastboot?
I did not get this problem mine was that I was getting the Supported API:3 loop and could not get into the bootloader to do anything. It may be that the answer I found may help you and other as I was at my wits end finding dead end fixes that did not work.
I had my problem with two Nexus 7 2012 tablets and have recovered them both this way.
While in the 'Supported API:3 ' loop ADB is loaded so you need to have the ADB/Fastboot drivers installed and working.
With your device attached to your PC go into the command prompt and type 'ADB Devices' without the quotes of course and hopefully it will show the ID of your tablet.
If it does then just Type' reboot bootloader' and it should boot into the bootloader.
Now you need to see if fastboot is working so type 'fastboot devices'. Again it should show you the ID of your device.
Download the latest stock update and extract the files. For the latest Nexus 7 2012 you will find the bootloader image file called 'bootloader bootloader-grouper-4.23.img'.
Type 'fastboot flash bootloader bootloader-grouper-4.23.img'
This will make sure you have the correct bootloader installed. Now type 'fastboot reboot-bootloader'
Your tablet should now boot into the bootloader again with no problem. To flash the stock image then type 'flash-all.bat' or if you wish type 'fastboot -w update image-nakasi-lmy47v.zip' then when that has finished type
'fastboot reboot' and set up your tablet again.
If you have problems make sure you have a good USB cable, the proper ADB/fastboot drivers installed and it has been suggested not to use a USB 3 port.
The only other trouble I had with one of my tablets was that when it rebooted it said that my data was encrypted or currupted and I had to enter my google password and once I found that fastboot did not work. I ran ADB devices and it found my tablet so I ran fastboot devices and it was ok then.
I could not get ADB to work at all in Windows 10 so I used Linux instead which does not need the drivers but does need the ADB/fastboot repository installed.
I installed VirtualBox on my Windows 10 laptop and installed Peppermint Linux in VirtualBox. This enabled me to get booted into bootloader on both occasions.
I realise that my problem was not the same but I hope at least it points you to a solution and you finally you have as good a result as I have and that this helps you.
I think I'm missing something. Does this also restore data, because i assumed the easiest way was to use Wugfresh's root toolkit, and that does the lot.
My Nexus 7 was stuck in APX, I got the driver on it. As I have a second (working) Nexus 7 could i use the blob files from the second tablet and how should I progress in your tutorial?
Hi. My Nexus 7 was in bootloop so tried installing the stock firmware through the Nexus Root tool. The version was correct and so was the USB connection but it somehow got stuck in Installing Bootloader part for quite some time. I rebooted it and there was no display after that. I have the bootloader image from the stock firmware but can't install it as the Nexus Root Tool is not recognizing it as fast boot device. Is there a way to get it working? Thanks
@sam214 nvflash is working for the Nexus 7 only if you have extracted your device specific binaries before. In that case you can restore the device with that binaries and get it running again. You cannot flash the extracted bootloader from the factory image with nvflash.
AndDiSa said:
@sam214 nvflash is working for the Nexus 7 only if you have extracted your device specific binaries before. In that case you can restore the device with that binaries and get it running again. You cannot flash the extracted bootloader from the factory image with nvflash.
Click to expand...
Click to collapse
Is there any way to unbrick without blobs?
TheDarkKnight said:
Is there any way to unbrick without blobs?
Click to expand...
Click to collapse
As far as I know: no, there is no way if your device is really bricked i.e. starts into APX mode only.
If the device does not start at all there is also the chance that "only" your battery power is too low ... so low that it does not even charge within the device. In that case there is the chance to revive the battery (there are several videos and instructions about that) if you are lucky.
AndDiSa said:
As far as I know: no, there is no way if your device is really bricked i.e. starts into APX mode only.
If the device does not start at all there is also the chance that "only" your battery power is too low ... so low that it does not even charge within the device. In that case there is the chance to revive the battery (there are several videos and instructions about that) if you are lucky.
Click to expand...
Click to collapse
My device only boots in APX mode So theres no way? What if I use blobs from someone with the same device?
Hello everyone, yesterday morning, Sunday 12/15/19, the system message "restart the device to make the system update effective".
So I do as I have always been.
The phone, an Mi A2, goes into bootloop and then a white screen appears on a black background with the title:
"<!> Failed to boot"
"Press the Volume keys to select then the Power button to continue.
RETRY
POWER OFF "
Choosing "RETRY" verifies bootloop 3 or 4 times and then the recovery mode screen appears which says:
"Can't Load Android system. Your data may be corrupted. You should get the message you need to perform at factory data reset and erase all user data stored on this device."
It gives me the choice between:
-Try again
-Factory data reset
Choosing "Try again" returns the same routine as when "RETRY" is selected In the previous black background screen, bootloop and then the black background white screen described at the beginning.
I MUST ACCESS AND SAVE THE VERY IMPORTANT CONTENT. :crying:
I have all the photos and videos of my newborn daughter. I usually backup but this inconvenience suddenly caught me.
I surfed and I saw that many people found this problem after an update .. but I never found any solutions. I called the Xiaomi center in Novara indicated by the site but they told me that they only serve as a collection center to send to the assistance in the company Xiaomi, saying that the assistance resets the phone to restore its functioning and does not save the data. I tried to start the fastboot, the device is recognized by the PC and shows the locked bootloader. The program MiFlash asks me to start to install a set of drivers and then immediately generate an unhandled exception and crash.
Attached the images.
Can you help me? I do not know what to do..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You should try to use adb in recovery, if it works, you could digit "adb pull /sdcard".
Continue rebooting with external power on. Android One with A/B slots is supposed to reboot into previously (before OTA) active slot.
Aerobatic said:
Continue rebooting with external power on. Android One with A/B slots is supposed to reboot into previously (before OTA) active slot.
Click to expand...
Click to collapse
Thank you, can you explain me better what I should try to do?
HTCDevil said:
You should try to use adb in recovery, if it works, you could digit "adb pull /sdcard".
Click to expand...
Click to collapse
Is there any guide to do that?
pedrix82 said:
Is there any guide to do that?
Click to expand...
Click to collapse
I don't think so, when you are in recovery you should try to verify if your device is connected with "adb devices" and then you should use the command "adb pull /sdcard". But it usually works with custom recoveries, and if you have prevently enabled usb debugging.
pedrix82 said:
Thank you, can you explain me better what I should try to do?
Click to expand...
Click to collapse
First you can try to search this forum and read dozens of discussions of the same issue. Meanwhile you can plug in power adapter and reboot several times with pauses, probably sometimes switching to stock recovery and to fastboot mode, and then leave phone powered for a night.
HTCDevil said:
I don't think so, when you are in recovery you should try to verify if your device is connected with "adb devices" and then you should use the command "adb pull /sdcard". But it usually works with custom recoveries, and if you have prevently enabled usb debugging.
Click to expand...
Click to collapse
Thanks....I will try, I don't remember if I enabled the usb debugging mode, for sure I saw with fastboot that I have the bootloader Locked.
nothing to do...i tried ADB mode, but it is not enabled, only fastboot mode where i can do nothing because the bootloader is locked.
I also tried to install the Xiaomi tool, but it doesnt recognize the device.
i dont know what to do....
Did you try the factory data reset?
1N4148 said:
Did you try the factory data reset?
Click to expand...
Click to collapse
Hello...ehm...not, the aim is to recover all the data, photos and documents that are stored inside...
Same thing happened to me. You should manually switch the active partition in fastboot.
Zedsdeadbaby said:
Same thing happened to me. You should manually switch the active partition in fastboot.
Click to expand...
Click to collapse
Hi, I already tried to do what you suggest, but it is not possible with the bootloader Locked.
Anyway, can you tell me what I have to do to change the active partition? Maybe I don't do it as I should....
@pedrix82: I can only repeat, though you do not read and trust:
- the only (legal*) way to save data in bootloop with locked device is to boot;
- all other options are blocked for a locked Mi A2, - resetting, unlocking, etc. will erase user data; switching Slots and/or loading TWRP need unlocked phone; stock recovery is useless;
- Android One partitions system with A/B Slots was specifically designed to solve problems of failed OTAs, see https://source.android.com/devices/tech/ota/ab and https://android.googlesource.com/pl...ware/+/master/include/hardware/boot_control.h
Which means that: if you have bootloop after OTA on full stock (and have not tampered device yourself), after numerous attempts to boot -> the bootloader MUST detect that active Slot does not have bootable OS and MUST switch to the other Slot.
(non-legal*) - or read memory chip content at low-level and decipher encrypted data.
Aerobatic said:
@pedrix82: I can only repeat, though you do not read and trust:
- the only (legal*) way to save data in bootloop with locked device is to boot;
- all other options are blocked for a locked Mi A2, - resetting, unlocking, etc. will erase user data; switching Slots and/or loading TWRP need unlocked phone; stock recovery is useless;
- Android One partitions system with A/B Slots was specifically designed to solve problems of failed OTAs, see https://source.android.com/devices/tech/ota/ab and https://android.googlesource.com/pl...ware/+/master/include/hardware/boot_control.h
Which means that: if you have bootloop after OTA on full stock (and have not tampered device yourself), after numerous attempts to boot -> the bootloader MUST detect that active Slot does not have bootable OS and MUST switch to the other Slot.
(non-legal*) - or read memory chip content at low-level and decipher encrypted data.
Click to expand...
Click to collapse
Thanks,
It's really long time that I'm rebooting the mobile since it happened...
But cyclically and alternate I got the two image attached to the main post....
try a "fastboot continue" in adb
hello everyone, update.
unfortunately I was unable to recover anything and proceeded with the factory reset.
The phone has reset and everything is working.
So I thought to try to do a file recovery as you do for deleted files.
for the various recovery applications I need to root the device.
For this phone should be really simple but I'm still stuck in.
I followed one guide, then another, and then another .... all with the same procedures.
the result is that twrp recovery, if loaded with Vol + and pwr button hangs on the custom recovery logo.
I can only start the twrp recovery installed in the secondary partition of the phone.
but from this recovery, even if I install Magisk, with a successful results from the recovery, I do not root the device. I verified root with Magisk manager and rootchecker.
Help.... thanks
pedrix82 said:
... So I thought to try to do a file recovery as you do for deleted files.
Click to expand...
Click to collapse
I do no believe you'll be able to undelete files after factory reset.
pedrix82 said:
... for the various recovery applications I need to root the device. ... I followed one guide, then another, and then another .... all with the same procedures.
Click to expand...
Click to collapse
This guide works for everybody, except that
(1) there is obsolete "fastboot oem unlock" command stated which should better be changed to "fastboot flashing unlock", and
(2) guide does not mention that each unlock step is to be approved on phone, and
(3) guide skips step of patching stock boot.img in phone with MagiskManager, - while exactly this step creates archived copy of stock boot image in /data root, thus allowing to restore images (actually restoring stock boot image) before downloading next OTA, and
(4) only 1st variant - that is booting into patched boot image and then making "Direct Install" is safe - it allows to check that patched boot image is suitable for ROM.
pedrix82 said:
...the result is that twrp recovery, if loaded with Vol + and pwr button hangs on the custom recovery logo.
I can only start the twrp recovery installed in the secondary partition of the phone....
Click to expand...
Click to collapse
IMHO that just means that you did not do your homework (I mean you have not read guides and discussions and Google info with links I provided) well enough to understand that with A/B slots partitions structure there is no separate /recovery partition in phone (instead, recovery is embedded into /boot image), and thus we cannot just "flash TWRP" into MiA2.
Instead, TWRP can only be embedded into boot image (patching previously flashed suitable boot image), which is made by installing TWRP.zip in temporarily booted TWRP.img. Thus, if you want to have both root and permanent TWRP (I still do not see why anybody needs permanent TWRP with rooted stock), first get root with patched boot image, and then install TWRP patching this Magisk-patched boot image once more.
And I do think that "TWRP 4pda edition" is working better than so called "official TWRP".
Found the solution,
First u need to get to the recovery menu by pressing vol up + power, tap it multiple times after retry boot...you have to be quick...and eventually will get to the android robot pic with "no command"....keep pressing till you get to the full recovery menu. (this might take multiple tries)
Then go to update using adb. (you need all the files for adb, usb drivers, latest mi a2 update zip, you can find tutorials in youtube/google )
after updating it should boot up fine with all data intact.
If latest update versions dont boot, try repeating will older version.
Make sure you backup everthing afterwards! and enable oem unlocking &usb debugging for potential future issues.
Hope this helps!
Flashed Pixel Expirience without any problems and worked just fine but i didnt like i cant remove date from top of home page
so i done flash of LineageOS 17.1 and worked fine but since i had problems with gaaps (installed but after boot to system nowhere to be found). Flashed Lineage couple more times to flash gaaps
So i installed TWRP 3.3.1 since i got iritated to temporary boot it every time from fastboot
I wipe(and done format ) everything from the phone using installed TWRP but phone still booted LineageOS !!! so i concluded that somehow must be installed on Slot A
Again boot in TWRP and wiped (and done format)Slot A, and again did same with Slot B.
after all this recovery is Lineage OS recovery !!!!!!
Now when i type any command in fastboot i get black screen with "press any key to shutdown"
downloaded stock and tried to force it with MiFlash i also get same "press any key to shutdown" error but sometimes i just get
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
when i forced MiFlash for 50 times it alegedly starts to flash but for eternity
also when i try to change slot with command fastboot set_active (a or b) i get error "Device does not support slots" !!
PS.
Im using USB2.0 and stock cable so USB3.0 is not problem
PPS.
after all this recovery is Lineage OS recovery !!!!!!
BOTTOM LINE:
I got message for whoever came up with slots. Fuk YOU !!
yrakun said:
Flashed Pixel Expirience without any problems and worked just fine but i didnt like i cant remove date from top of home page
so i done flash of LineageOS 17.1 and worked fine but since i had problems with gaaps (installed but after boot to system nowhere to be found). Flashed Lineage couple more times to flash gaaps
So i installed TWRP 3.3.1 since i got iritated to temporary boot it every time from fastboot
I wipe(and done format ) everything from the phone using installed TWRP but phone still booted LineageOS !!! so i concluded that somehow must be installed on Slot A
Again boot in TWRP and wiped (and done format)Slot A, and again did same with Slot B.
after all this recovery is Lineage OS recovery !!!!!!
Now when i type any command in fastboot i get black screen with "press any key to shutdown"
downloaded stock and tried to force it with MiFlash i also get same "press any key to shutdown" error but sometimes i just get
when i forced MiFlash for 50 times it alegedly starts to flash but for eternity
also when i try to change slot with command fastboot set_active (a or b) i get error "Device does not support slots" !!
PS.
Im using USB2.0 and stock cable so USB3.0 is not problem
PPS.
after all this recovery is Lineage OS recovery !!!!!!
BOTTOM LINE:
I got message for whoever came up with slots. Fuk YOU !!
Click to expand...
Click to collapse
search for any tutorial on how to do testpoint and then flash stock in edl
or........ try to flash lineage by using lineage recovery ....then try to enter fastboot
then start over ...
put of a photo of the problem with your fastboot
try something like :
fastboot oem edl
if screen goes black try to flash it in miflash real quick
but now that you have brick convert to wayne ...is A only ... I'm much happier since I converted
KevMetal said:
search for any tutorial on how to do testpoint and then flash stock in edl
Click to expand...
Click to collapse
You mean TO TAKE APART ?!
KevMetal said:
or........ try to flash lineage by using lineage recovery ....then try to enter fastboot
Click to expand...
Click to collapse
Only if i could copy installation zip without twrp
put of a photo of the problem with your fastboot
KevMetal said:
try something like :
fastboot oem edl
Click to expand...
Click to collapse
and i get greetings "press any key to shutdown"
KevMetal said:
but now that you have brick convert to wayne ...is A only ... I'm much happier since I converted
Click to expand...
Click to collapse
I don't understand
PS.
I noticed that in LineageOS recovery i have option ADB sideload
but when i try to do ADB Sideload rom.zip i get message "cannot read rom.zip"
yrakun said:
You mean TO TAKE APART ?!
*NO, to unscrew the screws and open the back cover of the phone
Only if i could copy installation zip without twrp
*boot to lineage recovery , then connect the usb and transfer the rom zip to the phone using file manager on pc
put of a photo of the problem with your fastboot
*yes, upload photos of the errors and what's happening
and i get greetings "press any key to shutdown"
* are you sure you are in fastboot ?
I don't understand
*what don't you understand
PS.
I noticed that in LineageOS recovery i have option ADB sideload
but when i try to do ADB Sideload rom.zip i get message "cannot read rom.zip"
Click to expand...
Click to collapse
* do you know how to use sideload ?
**put the rom in the folder of adb
***connect usb cable to phone and recovery activate sideload
**** on pc open cmd window in adb folder
***** use command :
adb sideload rom.zip
#make sure the name of the rom is rom.zip or call it update.zip
#make sure to use the lineage rom that goes with the recovery on the phone
##lastly "Wayne" or Mi X6 is the same phone as A2 or "jasmine" it just uses A only partition and comes with miui not android 1 and you can convert your phone to have A only partition by flashing miui of mi x6 on the phone which is what i did then your phone won't be a A/B device
Yes i know how to use sideload as i already wroted
"adb sideload rom. zip" get message "cannot read rom.zip"
but i made it. I needed newer version
turned on ADB in LineageOS recovery and tried to
flash stock, flashing started and stuck at 47% with some error
flashed newer stock and stuck at 47% with some error
flashed PixelExpirience and stuck at 47% with some error
flashed newer PixelExpirience and stuck at 47% with some error
flashed new Lineage and stuck on 47% with some error
flashed older Lineage and stuck on 47% with some error
flashed EvolutionX and SUCCESS
thank you Evolution, i will try to live with date at top of home screen
my 2 cents, if that's the only one working and you had it installed before they probly changed something on the default partition layout (which causes all others to fail).
your only way out of the mess is probably to flash the stock rom with miflash (which currently doesnt work because you're trying to flash the pie tgz - since xiaomi are too lazy to release a tgz for android 10). once they releases the 10 that one should let you reset the phone to stock.
I recently found myself in a predicament where I updated to the Android 11 Beta and stupidly reflashed TWRP (via TWRP A/B Retention Script magisk module), causing a recovery bootloop. I also could not get into fastboot mode via the hardware buttons. Not only that but there were NO NEW TWRP VERSIONS FOR ANDROID 11.
Uh oh. Now what do I do?
Fear not, for I have figured out how to get out of this and keep your data too! Just follow my steps and your precious phone shall be saved.
Step 1: Booting into fastboot.
Let it bootloop in the recovery (TWRP logo flashes repeatedly) and plug your phone into your PC. You need the ADB and fastboot drivers to access your phone.
Open your adb command prompt and type "adb devices" to ensure your phone is connected. If it is, then type "adb reboot bootloader". This will boot you into fastboot mode.
Step 2: Booting into system.
Once your in fastboot mode, type "fastboot devices" to ensure your phone is connected. If it is, then type "fastboot continue". This should boot it into system. It will look like it hangs on the 1+ Fastboot screen, but it will slowly boot into your system.
Step 3: Reinstalling OTA (removing twrp)
It may appear that your safe, but as soon as you restart your phone you will be in the same situation as you were earlier. What you have to do now is go to the oneplus website and download the zipped OTA update that got you in this situation. Be sure to save it in your root folder (/storage/emulated/0).
When that's done, go to settings > system > system updates. Click the gear icon and go to local upgrade. If you put the update zip in your root folder it will show up here.
Install the update. DONT REBOOT YET IF YOU WANT TO KEEP ROOT. If you don't, go ahead and reboot.
Step 4: Keeping Your Root
Exit settings and go to Magisk. Click install magisk and select Install to Inactive Slot (After OTA). After that's done then you can reboot.
For me it booted into the recovery, but you can reboot again and it will boot back into system.
Your phone should now be safe from bootloops! This should keep you comfortable until TWRP comes out with an Android 11 release for our phone.
I hope this helped you!
Yeah I just used a boot.img that was prerooted then wipe in that recovery.Youll come out of that whole mess rooted as well.
Also you should of posted this in the guide section. Be easier for them to find your info. i went there first an grabbed this boot img. just goes to show ya.
https://forum.xda-developers.com/t/made-an-ob1-magisk-patched-boot-img.4221209/
Thx for this bro...this just happened to me this weekend and I was looking everywhere for a way to fix this issue without having to completely wipe my phone. Much appreciation here fam!
My phone keeps rebooting → the boot logo always starts from the beginning after it's done. I'm on the stable OOS11
Dang i totally forgot about fastboot continue. Know your tools, I guess
Thx very much.
I fear I have lost my phone completely! I hope someone can help, I'm getting pretty desperate.
Stuck in bootloop (TWRP flashing on screen over and over)
"adb devices" shows my device is connected.
"adb reboot bootloader" works and reboots device into fastboot.
But then I'm stuck.
"fastboot devices" shows no device is connected (I hear the windows connect sound, so something's working).
"fastboot continue" just gets stuck waiting for device (since none is "connected")
Am I all out of luck here? Whatever I choose in fastboot on the phone results in getting stuck in the bootloop again.
thanx , just used Your Guide and I'm back on 11.0.0.2.GM21BA with ROOT.
This is what I've done:
-turn my device OFF
- reboot fastboot
- fastboot continue
- flashed the net 11.0.0.2.GM21BA rom and before reboot i installed magisk onto another slot (after OTA)
Now Rooted an after reboot , the phone is starting Android
Will wait for a twrp compatible with Android 11
SkellyBoy said:
I recently found myself in a predicament where I updated to the Android 11 Beta and stupidly reflashed TWRP (via TWRP A/B Retention Script magisk module), causing a recovery bootloop. I also could not get into fastboot mode via the hardware buttons. Not only that but there were NO NEW TWRP VERSIONS FOR ANDROID 11.
Uh oh. Now what do I do?
Fear not, for I have figured out how to get out of this and keep your data too! Just follow my steps and your precious phone shall be saved.
Step 1: Booting into fastboot.
Let it bootloop in the recovery (TWRP logo flashes repeatedly) and plug your phone into your PC. You need the ADB and fastboot drivers to access your phone.
Open your adb command prompt and type "adb devices" to ensure your phone is connected. If it is, then type "adb reboot bootloader". This will boot you into fastboot mode.
Step 2: Booting into system.
Once your in fastboot mode, type "fastboot devices" to ensure your phone is connected. If it is, then type "fastboot continue". This should boot it into system. It will look like it hangs on the 1+ Fastboot screen, but it will slowly boot into your system.
Step 3: Reinstalling OTA (removing twrp)
It may appear that your safe, but as soon as you restart your phone you will be in the same situation as you were earlier. What you have to do now is go to the oneplus website and download the zipped OTA update that got you in this situation. Be sure to save it in your root folder (/storage/emulated/0).
When that's done, go to settings > system > system updates. Click the gear icon and go to local upgrade. If you put the update zip in your root folder it will show up here.
Install the update. DONT REBOOT YET IF YOU WANT TO KEEP ROOT. If you don't, go ahead and reboot.
Step 4: Keeping Your Root
Exit settings and go to Magisk. Click install magisk and select Install to Inactive Slot (After OTA). After that's done then you can reboot.
For me it booted into the recovery, but you can reboot again and it will boot back into system.
Your phone should now be safe from bootloops! This should keep you comfortable until TWRP comes out with an Android 11 release for our phone.
I hope this helped you!
Click to expand...
Click to collapse
Sorry if I misunderstood what you meant, but does this mean that this method will get you rooted but we will lose TWRP access?
"fastest continue" takes me back to the original stuck boot loop. Fastboot devices shows "fastboot" next to device number.
I can confirm that I was able to upgrade from OOS 10 to 11 and keep magisk root. I did local upgrade and before rebooting, installed magisk to inactive slot, disabled all modules. Phone booted fine and is updated to OOS 11. Thank you!
SkellyBoy said:
I recently found myself in a predicament where I updated to the Android 11 Beta and stupidly reflashed TWRP (via TWRP A/B Retention Script magisk module), causing a recovery bootloop. I also could not get into fastboot mode via the hardware buttons. Not only that but there were NO NEW TWRP VERSIONS FOR ANDROID 11.
Uh oh. Now what do I do?
Fear not, for I have figured out how to get out of this and keep your data too! Just follow my steps and your precious phone shall be saved.
Step 1: Booting into fastboot.
Let it bootloop in the recovery (TWRP logo flashes repeatedly) and plug your phone into your PC. You need the ADB and fastboot drivers to access your phone.
Open your adb command prompt and type "adb devices" to ensure your phone is connected. If it is, then type "adb reboot bootloader". This will boot you into fastboot mode.
Step 2: Booting into system.
Once your in fastboot mode, type "fastboot devices" to ensure your phone is connected. If it is, then type "fastboot continue". This should boot it into system. It will look like it hangs on the 1+ Fastboot screen, but it will slowly boot into your system.
Step 3: Reinstalling OTA (removing twrp)
It may appear that your safe, but as soon as you restart your phone you will be in the same situation as you were earlier. What you have to do now is go to the oneplus website and download the zipped OTA update that got you in this situation. Be sure to save it in your root folder (/storage/emulated/0).
When that's done, go to settings > system > system updates. Click the gear icon and go to local upgrade. If you put the update zip in your root folder it will show up here.
Install the update. DONT REBOOT YET IF YOU WANT TO KEEP ROOT. If you don't, go ahead and reboot.
Step 4: Keeping Your Root
Exit settings and go to Magisk. Click install magisk and select Install to Inactive Slot (After OTA). After that's done then you can reboot.
For me it booted into the recovery, but you can reboot again and it will boot back into system.
Your phone should now be safe from bootloops! This should keep you comfortable until TWRP comes out with an Android 11 release for our phone.
I hope this helped you!
Click to expand...
Click to collapse
i had too this prob , but i cant solve that you could ,and get msmdownload , genius...i like it, i cant imagin in twrp flashing logo i could connect to adb and booting in fastboot mode...intersting.
so now i have stable 11.02 and i cant root it with patched boot image , icant find what the prob .... trying flash boot_a boot_b but nothing...
do you know how i can fix the root???
sevenstringserpent said:
I fear I have lost my phone completely! I hope someone can help, I'm getting pretty desperate.
Stuck in bootloop (TWRP flashing on screen over and over)
"adb devices" shows my device is connected.
"adb reboot bootloader" works and reboots device into fastboot.
But then I'm stuck.
"fastboot devices" shows no device is connected (I hear the windows connect sound, so something's working).
"fastboot continue" just gets stuck waiting for device (since none is "connected")
Am I all out of luck here? Whatever I choose in fastboot on the phone results in getting stuck in the bootloop again.
Click to expand...
Click to collapse
check it with turn off and do again with same is op ..if couldn't you just make too use msmdownload
SkellyBoy said:
I recently found myself in a predicament where I updated to the Android 11 Beta and stupidly reflashed TWRP (via TWRP A/B Retention Script magisk module), causing a recovery bootloop. I also could not get into fastboot mode via the hardware buttons. Not only that but there were NO NEW TWRP VERSIONS FOR ANDROID 11.
Uh oh. Now what do I do?
Fear not, for I have figured out how to get out of this and keep your data too! Just follow my steps and your precious phone shall be saved.
Step 1: Booting into fastboot.
Let it bootloop in the recovery (TWRP logo flashes repeatedly) and plug your phone into your PC. You need the ADB and fastboot drivers to access your phone.
Open your adb command prompt and type "adb devices" to ensure your phone is connected. If it is, then type "adb reboot bootloader". This will boot you into fastboot mode.
Step 2: Booting into system.
Once your in fastboot mode, type "fastboot devices" to ensure your phone is connected. If it is, then type "fastboot continue". This should boot it into system. It will look like it hangs on the 1+ Fastboot screen, but it will slowly boot into your system.
Step 3: Reinstalling OTA (removing twrp)
It may appear that your safe, but as soon as you restart your phone you will be in the same situation as you were earlier. What you have to do now is go to the oneplus website and download the zipped OTA update that got you in this situation. Be sure to save it in your root folder (/storage/emulated/0).
When that's done, go to settings > system > system updates. Click the gear icon and go to local upgrade. If you put the update zip in your root folder it will show up here.
Install the update. DONT REBOOT YET IF YOU WANT TO KEEP ROOT. If you don't, go ahead and reboot.
Step 4: Keeping Your Root
Exit settings and go to Magisk. Click install magisk and select Install to Inactive Slot (After OTA). After that's done then you can reboot.
For me it booted into the recovery, but you can reboot again and it will boot back into system.
Your phone should now be safe from bootloops! This should keep you comfortable until TWRP comes out with an Android 11 release for our phone.
I hope this helped you!
Click to expand...
Click to collapse
Hey, I am on Android 11, and facing similar issue.
You came closest to describing what I was facing(I have been all over the forum, posted my query separately as a thread and as a reply, to no avail).
You seem like you have figured this out, but man, am I stuck.
So, your method (I am pretty sure you were clear enough so I was following correctly) was working until "fastboot continue"- that just leads me back to TWRP logo blinking agony soulcrushing boot loop.
Anyhow, I also tried to use fastboot boot twrp image file(I had a copy of the version on my pc)- that seemed like it worked, but it just got stuck on the 1+ fastboot logo page.. and reading from your description I had my hopes up for a moment, but then half an hour passed up, then another hour, then three-four hours.. I don't suppose you meant this slowly, right?(I know it's silly I am hopeful.)
I am kinda in a fix, as unblocking using fastboot firmware image won't work too- as I am on Android 11, and that method only has images for until Android 10.
Any help will greatly appreciated man? Thanks if you read through till here..
saurabh_op7 said:
Hey, I am on Android 11, and facing similar issue.
You came closest to describing what I was facing(I have been all over the forum, posted my query separately as a thread and as a reply, to no avail).
You seem like you have figured this out, but man, am I stuck.
So, your method (I am pretty sure you were clear enough so I was following correctly) was working until "fastboot continue"- that just leads me back to TWRP logo blinking agony soulcrushing boot loop.
Anyhow, I also tried to use fastboot boot twrp image file(I had a copy of the version on my pc)- that seemed like it worked, but it just got stuck on the 1+ fastboot logo page.. and reading from your description I had my hopes up for a moment, but then half an hour passed up, then another hour, then three-four hours.. I don't suppose you meant this slowly, right?(I know it's silly I am hopeful.)
I am kinda in a fix, as unblocking using fastboot firmware image won't work too- as I am on Android 11, and that method only has images for until Android 10.
Any help will greatly appreciated man? Thanks if you read through till here..
Click to expand...
Click to collapse
Hi Saura, I'm facing the same issue, after gitting "fastboot continue" I'm stuck at the turning red/white dots boot screen.
But when I power the phone off I get back to the boot logo, I have never entered the recovery loop, have you been able to fix your phone?
SkellyBoy said:
I recently found myself in a predicament where I updated to the Android 11 Beta and stupidly reflashed TWRP (via TWRP A/B Retention Script magisk module), causing a recovery bootloop. I also could not get into fastboot mode via the hardware buttons. Not only that but there were NO NEW TWRP VERSIONS FOR ANDROID 11.
Uh oh. Now what do I do?
Fear not, for I have figured out how to get out of this and keep your data too! Just follow my steps and your precious phone shall be saved.
Step 1: Booting into fastboot.
Let it bootloop in the recovery (TWRP logo flashes repeatedly) and plug your phone into your PC. You need the ADB and fastboot drivers to access your phone.
Open your adb command prompt and type "adb devices" to ensure your phone is connected. If it is, then type "adb reboot bootloader". This will boot you into fastboot mode.
Step 2: Booting into system.
Once your in fastboot mode, type "fastboot devices" to ensure your phone is connected. If it is, then type "fastboot continue". This should boot it into system. It will look like it hangs on the 1+ Fastboot screen, but it will slowly boot into your system.
Step 3: Reinstalling OTA (removing twrp)
It may appear that your safe, but as soon as you restart your phone you will be in the same situation as you were earlier. What you have to do now is go to the oneplus website and download the zipped OTA update that got you in this situation. Be sure to save it in your root folder (/storage/emulated/0).
When that's done, go to settings > system > system updates. Click the gear icon and go to local upgrade. If you put the update zip in your root folder it will show up here.
Install the update. DONT REBOOT YET IF YOU WANT TO KEEP ROOT. If you don't, go ahead and reboot.
Step 4: Keeping Your Root
Exit settings and go to Magisk. Click install magisk and select Install to Inactive Slot (After OTA). After that's done then you can reboot.
For me it booted into the recovery, but you can reboot again and it will boot back into system.
Your phone should now be safe from bootloops! This should keep you comfortable until TWRP comes out with an Android 11 release for our phone.
I hope this helped you!
Click to expand...
Click to collapse
THANK YOU!!!!
`fastboot continue`
I just did the manipulation explained in first post to recover from bootloop blinking TWRP after OTA, and it went smoothly !
Everything is fine now, huge thanks for you help !
SkellyBoy, THANK YOU for the walkthrough. I tried to reset my OP 7 Pro (rooted + magisk, no custom rom) last night, and forgot I had TWRP installed. It dropped into a bootloop where it would flicker the TWRP screen but wouldn't let me get past that.
Your instructions for fastboot continue got me past that and to a proper boot... and I kept root!
You ROCK fam... many thanks
sevenstringserpent said:
I fear I have lost my phone completely! I hope someone can help, I'm getting pretty desperate.
Stuck in bootloop (TWRP flashing on screen over and over)
"adb devices" shows my device is connected.
"adb reboot bootloader" works and reboots device into fastboot.
But then I'm stuck.
"fastboot devices" shows no device is connected (I hear the windows connect sound, so something's working).
"fastboot continue" just gets stuck waiting for device (since none is "connected")
Am I all out of luck here? Whatever I choose in fastboot on the phone results in getting stuck in the bootloop again.
Click to expand...
Click to collapse
u can upgrade your pc driver using iobit driver booster. this fixes the fastboot detection, if still failed, u can download working twrp from https://forum.xda-developers.com/t/recovery-11-unofficial-teamwin-recovery-project.4289455/ and run "fastboot boot twrp.img"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
HELP!
I installed platform-tools_r33.0.2-windows and UniversalAdbDriverSetup, now i'm trying to flash TWRP on the XA2 Phone by using this cmd command:
adb devices
- daemon not running, starting now at xxx
adb flash recovery twrp.img
- waiting for any device
What am i doing wrong?? Please help!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Boot phone in fastboot mode
Execute "fastboot flash recovery twrp.img"
LR7875 said:
Boot phone in fastboot mode
Execute "fastboot flash recovery twrp.img"
Click to expand...
Click to collapse
How? Im pressing volume up and then connecting the phone to the pc, then i see a blue light. Is this fastboot mode? Thats what im already doing for 3 hours...
Yeah just did it again... volumeup+connect phone to pc, blue light appears on phone (fastboot mode i asume).
on pc in cmd i type adb devices, it starts the daemon.
then i type "fasboot flash recovery twrp.img"
result in cmd: "waiting for any device"
Wtf?
I swear this is so cancer can't handle this ****, the F is wrong with sony? This phone is buggy AF im trying to insall TWRP for like 4 hours now, this is a ****ing joke. What a waste of time.
Try the 15 seconds adb and fastboot driver if you haven't already
LR7875 said:
Try the 15 seconds adb and fastboot driver if you haven't already
Click to expand...
Click to collapse
This? https://forum.xda-developers.com/t/...vers-15-seconds-adb-installer-v1-4-3.2588979/
I doubt it will be any different from the platformtools adb? How could this help?
LR7875 said:
Try the 15 seconds adb and fastboot driver if you haven't already
Click to expand...
Click to collapse
You mean minimal adb ? or can you provide a link?
Connect the phone in fastboot mode (LED = blue) and open the device manager. Do you see the phone under "Other Devices" or "Android" with an exclamation mark? Then you need an ADB/bootloader interface driver. Get this for example:
https://developer.sony.com/file/download/xperia-xz2-driver/
(Yes, XZ2! There is no official XA2 driver)
Unzip it somewhere and force install the driver:
Right click on the device manager entry from above, "Update driver", "Browse my computer...", "Let me pick...", "List/show all...", "Have disk...", browse to the folder from above, open the selected .inf file and install.
Fastboot should work now. At least that's how I got it to work on a new PC.
BTW, just use "fastboot devices" to check whether it works. If your device doesn't appear, you don't need to try other fastboot commands - it won't work.
I have this problem, when installing twrp to my Sony Xperia XA2 (H3123), I am trying to install several versions of Twrp, for example: twrp-3.2.2-0-pioneer.img, twrp-3.7.0_9-0 -pioneer.img, my Sony is on Android 9
Carljaynp03 said:
I have this problem, when installing twrp to my Sony Xperia XA2 (H3123), I am trying to install several versions of Twrp, for example: twrp-3.2.2-0-pioneer.img, twrp-3.7.0_9-0 -pioneer.img, my Sony is on Android 9
Click to expand...
Click to collapse
Did you unlock the bootloader ?
Carljaynp03 said:
View attachment 5734133
Click to expand...
Click to collapse
I agree with faraway, if i remember correctly when i had this issue i didn't unlock the bootloader.
I typed a specific number in the phone dial app and it said that the bootloader is unlocked, however there is another step you need to take that i had overlooked, you need a bootloader unlock code.
The code is free, not like with chinese spyware huawai they want your money for the code...
Unlock Bootloader - Open Devices - Sony Developer World
developer.sony.com
https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/how-to-unlock-bootloader/#tutorial-step-4
and use one of these commands in cmd/adb
fastboot flashing unlock
fastboot oem unlock
Carljaynp03 said:
View attachment 5734133
Click to expand...
Click to collapse
What is your end goal? To flash a custom ROM like LineageOS? Then you can temporarily flash a recovery image to the boot partition:
fastboot flash boot <recovery_filename>.img
You don't really need TWRP for this, just use the latest official LOS Recovery:
https://download.lineageos.org/pioneer
Also see: https://wiki.lineageos.org/devices/pioneer/install
Or do you want to "permanently" install TWRP on an existing system? Then you need to directly boot into TWRP and install it from its GUI:
fastboot boot <twrp_filename>.img
See: https://twrp.me/sony/sonyxperiaxa2.html
I haven't tried the latter on the XA2 yet though and don't know how permanent that installation really is. It maybe gone after an OTA update.
irgendwer2 said:
What is your end goal? To flash a custom ROM like LineageOS? Then you can temporarily flash a recovery image to the boot partition:
fastboot flash boot <recovery_filename>.img
You don't really need TWRP for this, just use the latest official LOS Recovery:
https://download.lineageos.org/pioneer
Also see: https://wiki.lineageos.org/devices/pioneer/install
Or do you want to "permanently" install TWRP on an existing system? Then you need to directly boot into TWRP and install it from its GUI:
fastboot boot <twrp_filename>.img
See: https://twrp.me/sony/sonyxperiaxa2.html
I haven't tried the latter on the XA2 yet though and don't know how permanent that installation really is. It maybe gone after an OTA update.
Click to expand...
Click to collapse
Booting a temprary image did not work when i tried it, most likely because the bootloader wasn't unlock.
Privacydroid said:
Booting a temprary image did not work when i tried it, most likely because the bootloader wasn't unlock.
Click to expand...
Click to collapse
Independent from the bootloader status: you can't flash an image directly to the recovery partition on the XA2/Pioneer (like he tried, see screenshot) because such a dedicated partition doesn't exist on this and other A/B devices. Instead the recovery is built into the boot image.
That's why you have to use fastboot flash boot instead of recovery.
irgendwer2 said:
Independent from the bootloader status: you can't flash an image directly to the recovery partition on the XA2/Pioneer (like he tried, see screenshot) because such a dedicated partition doesn't exist on this and other A/B devices. Instead the recovery is built into the boot image.
That's why you have to use fastboot flash boot instead of recovery.
Click to expand...
Click to collapse
follow the next steps you mentioned use: fastboot flash boot recovery from LineageOS, and my phone went into a constant boot shutdown and restart, then this message appeared
and the bootloader is open
Shutdown the phone after flashing the recovery image (it doesn't seem like you did that). Then hold Volume Down + Power to boot into recovery.
irgendwer2 said:
Independent from the bootloader status: you can't flash an image directly to the recovery partition on the XA2/Pioneer (like he tried, see screenshot) because such a dedicated partition doesn't exist on this and other A/B devices. Instead the recovery is built into the boot image.
That's why you have to use fastboot flash boot instead of recovery.
Click to expand...
Click to collapse
I get that the recovery is only for a temporary boot, when i tried it, it didn't work but i can't remember what the error was.