Related
I can't well english. sorry. I have been using a translator.
My Tablet : Lenovo yoga 2 10 Android, only WiFi version (1050F) and Lollipop version
I accidentally flashing -> delete recovery!! :crying:
but, I was rooting.
Fortunately, I have been using Android, without problems.
I know this :
(Install TWRP Recovery, but only Kitkat.. or waiting)
http://forum.xda-developers.com/android/development/twrp-t3103296?goto=newpost
(Lollipop -> Kitkat, but It is difficult and risk)
http://forum.xda-developers.com/thinkpad-tablet/general/guide-root-yoga-tablet-2-pro-8-10-13-3-t2930428/post60490907#post60490907
Is there any other way?
what do you want?
to root in lollipop?
to return to stock kitkat?
ionioni said:
what do you want?
to root in lollipop?
to return to stock kitkat?
Click to expand...
Click to collapse
Forgive me for being late.
I using lollipop(root), Android(OS) is operating normally And unlocked bootloader
I want to install Recovery
neverapple88 said:
Forgive me for being late.
I using lollipop(root), Android(OS) is operating normally And unlocked bootloader
I want to install Recovery
Click to expand...
Click to collapse
you want to install back the stock recovery? or do you want a custom one?
if stock it's easy, if you want a custom one first you will need an unlocked bootloader then the custom recovery itself (compatible with your tab)
you have an unlocked bootloader??? what? how?
also try translating with google translate it's much better at asian languages (you koreean huh?)
ionioni said:
you want to install back the stock recovery? or do you want a custom one?
if stock it's easy, if you want a custom one first you will need an unlocked bootloader then the custom recovery itself (compatible with your tab)
you have an unlocked bootloader??? what? how?
also try translating with google translate it's much better at asian languages (you koreean huh?)
Click to expand...
Click to collapse
I now, using debian noroot, Android in trying -> text delete...
I don't know (how to unlocked bootloader)
but, I use googling -> find link : http://unlock-bootloader.info/mp3-0/lenovo-yoga-tablet-2-10-1-6731.html This(Link -> Files) is malware!
I think unlocked bootloader because...
http://forum.xda-developers.com/showpost.php?p=57543871&postcount=1
here post : WARNING : This Temporary CWM / TWRP Recovery Session is for some Intel Devices with locked boot loaders.
It is not intended for installing custom roms as if the devices has a locked bootloader the device will fail to boot the unsigned images
I succeeded(rooting), therefore i think unlocked
Sorry my english.
I using korean
and i now go to word understand
neverapple88 said:
I now, using debian noroot (= therefore can't using translating), Android in trying -> text delete...
I don't know (how to unlocked bootloader)
but, I use googling -> find link : http://unlock-bootloader.info/mp3-0/lenovo-yoga-tablet-2-10-1-6731.html
I think unlocked bootloader because...
http://forum.xda-developers.com/showpost.php?p=57543871&postcount=1
here post : WARNING : This Temporary CWM / TWRP Recovery Session is for some Intel Devices with locked boot loaders.
It is not intended for installing custom roms as if the devices has a locked bootloader the device will fail to boot the unsigned images
I clear!(rooting), therefore i think unlocked
Sorry my english.
I using korean
and i now go to word understand
Click to expand...
Click to collapse
그래서 , 이 순간에 당신은 당신의 장치 에 Lollipop 가 있습니까? 그리고 당신은 root 을 갖고 싶어 ?
또는 KitKat 로 다운 그레이드 싶어?
ionioni said:
그래서 , 이 순간에 당신은 당신의 장치 에 Lollipop 가 있습니까? 그리고 당신은 root 을 갖고 싶어 ?
또는 KitKat 로 다운 그레이드 싶어?
Click to expand...
Click to collapse
Yes, I have Lollpop. (rooted)
I no want KitKat.
I want custom recovery, but can this 'only' kitkat version. (sry english)
Therefore, I want stock recovery.
and english <-> korean translate(computer) is bed
I go to translate(understand) = very better
1. for stock recovery:
boot tablet in droidboot mode (PowerOff then PowerOn+VolDown)
on your PC issue the command: fastboot flash recovery recovery.img using the recovery.img from the stock rom
(i am assuming your droidboot is functional as you were asking for recovery)
2. if you cannot boot into droidboot mode you will need to restore the droidboot: extract on your PC from the OTA Lollipop package, the files bootx64.efi (it can be found in the esp.zip in \EFI\BOOT directory) and the droidboot.img file, then boot into dnx mode (PowerOff then PowerOn+VolUp+VolDown, screen should say "starting fastboot..."), at this moment issue in order these commands:
fastboot flash osloader bootx64.efi
fastboot boot droidboot.img and after it boots in droidboot mode enter:
fastboot flash fastboot droidboot.img
the bootx64.efi and droidboot.img are both from the OTA Lollipop package (you can find the OTA over the net, YT2-1050F_USR_S100017_1505261558_WW52_CN_otafull) or you can ask someone with Lollipop installed to give them from their system (bootx64.efi is on the ESP partition and droidboot.img can be dumped with a dd from the fastboot partition)
ps. there is no custom recovery at this moment (lollipop or kitkat) as there is no unlocked bootloader (one can flash whatever wants on the boot/fastboot/recovery partition but the images will be rejected at boot for not being signed)
ionioni said:
1. for stock recovery:
boot tablet in droidboot mode (PowerOff then PowerOn+VolDown)
on your PC issue the command: fastboot flash recovery recovery.img using the recovery.img from the stock rom
(i am assuming your droidboot is functional as you were asking for recovery)
2. if you cannot boot into droidboot mode you will need to restore the droidboot: extract on your PC from the OTA Lollipop package, the files bootx64.efi (it can be found in the esp.zip in \EFI\BOOT directory) and the droidboot.img file, then boot into dnx mode (PowerOff then PowerOn+VolUp+VolDown, screen should say "starting fastboot..."), at this moment issue in order these commands:
fastboot flash osloader bootx64.efi
fastboot boot droidboot.img and after it boots in droidboot mode enter:
fastboot flash fastboot droidboot.img
the bootx64.efi and droidboot.img are both from the OTA Lollipop package (you can find the OTA over the net, YT2-1050F_USR_S100017_1505261558_WW52_CN_otafull) or you can ask someone with Lollipop installed to give them from their system (bootx64.efi is on the ESP partition and droidboot.img can be dumped with a dd from the fastboot partition)
ps. there is no custom recovery at this moment (lollipop or kitkat) as there is no unlocked bootloader (one can flash whatever wants on the boot/fastboot/recovery partition but the images will be rejected at boot for not being signed)
Click to expand...
Click to collapse
Sorry, I find stock rom -> fail
I search YT2-1050F_USR_S100017_1505261558_WW52_CN_otafull, stock rom, other..
but, download -> ???.apk or close server or other.. nowhere rom
Where is stock rom?
1. do you need the recovery.img from the stock rom? if you have a valid droidboot(fastboot), ie if you get the droidboot menu when you start with (Pwr+VolDown) then the recovery.img can be found in the stock rom, check the all in one thread for 1050F stock rom (the recovery.img is the KitKat one, the OTA doesn't update that)
2. if you need bootx64.efi and droidboot.img meaning you cannot boot in droidboot(fastboot) mode (you are sure you cannot flash with fastboot) then the two files can be found in the OTA, search baidu for YT2-1050F_USR_S100017_1505261558_WW52_CN_otafull.zip, actually this is OTA for chinese package but i think it's safe to get/flash the bootx64.efi /droidboot.img from there (and only that)
Update: find all the needed files (from stock 1050F Lollipop ROM) here https://anonfiles.com/file/1025d77353f4395d090b07c88bcf156d
1. for stock recovery reflashing: boot tablet in droidboot mode (PowerOff then PowerOn+VolDown)
on your PC issue the command: fastboot flash recovery recovery.img
2. if you cannot boot into droidboot mode you will need to restore the droidboot first: boot into dnx mode (PowerOff then PowerOn+VolUp+VolDown, screen should say "starting fastboot..."), at this moment issue in order these commands:
fastboot flash osloader bootx64.efi
fastboot boot droidboot.img and after it finishes booting in droidboot mode (screen should display "waiting commands" in the bottom) enter:
fastboot flash fastboot droidboot.img
ionioni said:
1. do you need the recovery.img from the stock rom? if you have a valid droidboot(fastboot), ie if you get the droidboot menu when you start with (Pwr+VolDown) then the recovery.img can be found in the stock rom, check the all in one thread for 1050F stock rom (the recovery.img is the KitKat one, the OTA doesn't update that)
2. if you need bootx64.efi and droidboot.img meaning you cannot boot in droidboot(fastboot) mode (you are sure you cannot flash with fastboot) then the two files can be found in the OTA, search baidu for YT2-1050F_USR_S100017_1505261558_WW52_CN_otafull.zip, actually this is OTA for chinese package but i think it's safe to get/flash the bootx64.efi /droidboot.img from there (and only that)
Update: find all the needed files (from stock 1050F Lollipop ROM) here https://anonfiles.com/file/1025d77353f4395d090b07c88bcf156d
1. for stock recovery reflashing: boot tablet in droidboot mode (PowerOff then PowerOn+VolDown)
on your PC issue the command: fastboot flash recovery recovery.img
2. if you cannot boot into droidboot mode you will need to restore the droidboot first: boot into dnx mode (PowerOff then PowerOn+VolUp+VolDown, screen should say "starting fastboot..."), at this moment issue in order these commands:
fastboot flash osloader bootx64.efi
fastboot boot droidboot.img and after it finishes booting in droidboot mode (screen should display "waiting commands" in the bottom) enter:
fastboot flash fastboot droidboot.img
Click to expand...
Click to collapse
(1, 2) Succeeded!
It has been a great help.
I will be diligent backups from today.
Thank you for your sincere answer to the question.
neverapple88 said:
but, I use googling -> find link : http://unlock-bootloader.info/mp3-0/lenovo-yoga-tablet-2-10-1-6731.html
Click to expand...
Click to collapse
nope... the only thing you will get from there is malware
ionioni said:
nope... the only thing you will get from there is malware
Click to expand...
Click to collapse
OMG,,,
Fortunately, I did not run it.
SOLVED:
Hi,
I just bricked my MX4 after trying to update system image from 4.5.6 to 4.5.7 using this guide:
Extract I version update.zip
use sdat2img to create system image
dd system image to system partition on live phone and reboot.
I used the same procedure successfully before, x-updating 4.5.4A ti I then updating to 4.5.6I.
After updating to 4.5.7, the phone goes into an infinite loop of Meizu splash screen, Flyme balloon, reboot.
I can enter fastboot and official recovery, but can't flash any partition from fastboot.
The bootloader is still locked.
Does anyone have any advice for unbricking?
Update:
The bootloop suddenly froze up for long enough for me to use adb to push an update.zip to the "sdcard" root. Have now flashed 4.2.8A from recovery and booted the phone.
As I had to clear all data I will unlock bootloader before trying anything else.
Try do flash 4.2.8.2 with uboot.img modded (to reunlock bootloader) and reboot fastboot and tell me
bobslesbricoleurs said:
Try do flash 4.2.8.2 with uboot.img modded (to reunlock bootloader) and reboot fastboot and tell me
Click to expand...
Click to collapse
Hi,
I managed to push 4.2.8.2 to sdcard then do a normal recovery reflash.
Have now successfully unlocked using the .apk method.
Now I need to find out if I can use that unlocked bootloader to flash recent "I" firmwares, or if I can only flash the unfinished cyanogen (would like to wait 'til that's a bit more polished before using it.
Anyway. Happy to have my phone back!
Maybe that newest 4.5.7I need a new kernel so you'll need to update to 4.5.7A before flashing system.img or you can flash directly 4.5.7I but you'll need to use fastboot flash boot boot.img
If a rom/firmware needs a specific kernel it'll bootloop if you don't flash it
Can I flash 4.5.7 I now that I have unlocked bootloader and custom recovery? If I understand the unlock threads correctly, I think I will relock the bootloader, or even brick if I try to flash the complete update.zip. Can I flash system and boot partitions using fastboot?
Fully BRICKED.
Now I FULLY bricked it (no more recovery).
Had successfully upgraded to 4.5.7 "I" and was installing super su for full root, before disabling update, but had forgotten that I still had official 4.2.8 rom as update.zip on "sdcard" root.
rebooted to TWRP recovery for full su install and recovery found the update.zip and flashed it.
Result: Bootloop, No recovery, locked fastboot, no possibility to flash anything.
Aaargh!
Where do I find a 4.2.8 recovery.img for this phone?
Maybe there's a possibility doing a fastboot boot recovery.img ???
NOPE:
[email protected]:/home/marius/Downloads# fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.662s]
booting...
FAILED (remote: unknown command)
Fixed with large hammer! Goodbye Meizu!
Learnincurve said:
Where do I find a 4.2.8 recovery.img for this phone?
Maybe there's a possibility doing a fastboot boot recovery.img ???
NOPE:
[email protected]:/home/marius/Downloads# fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.662s]
booting...
FAILED (remote: unknown command)
Click to expand...
Click to collapse
Fixed with large hammer! Goodbye Meizu!
fastboot boot recovery.img isn't a command at all... It's fastboot flash recovery C:/path/to/recovery.img
I don't really want to flash TWRP if it's not necessary to and I can just boot into it. And i'd rather see that I can boot into it before I flash it.
I understand that if i'm in the boot loader screen then I can issue the command fastboot boot twrp.img and it should go into the twrp boot loader without me needing to flash the boot loader to be twrp.
But it seems for some reason that when I issue that command I get a blank screen. The phone restarts and goes to a blank screen.
My phone is a nexus 4. I have android 4.3
I have downloaded twrp, from https://dl.twrp.me/mako/ I've tried the latest, that's
twrp-3.0.2-0-mako.img and i've tried the oldest, that's twrp-2.3.2.3-mako.img and I face the same issue
TIA
The bootloader is unlocked?
Yeah, bootloader is unlocked.
In the end I decided to forget about that command (fastboot boot twrp.img) and just flash the recovery. so, this command fastboot flash recovery twrp.img
I made sure to have the stock recovery too (recovery.img from an archive file from https://developers.google.com/android/nexus/images )
so I could flash that it back to stock, if flashing twrp recovery didn't work. But it worked.
I guess maybe the reason why I got/would get/get a black screen with my command, was because fastboot boot blah.img is to boot a kernel, not to boot a recovery? (I don't know if my terminology is all wrong?)
Hi there! I recently got my first android phone so wanted to install Lineage os 15.1 but messed it up right away as it's in now in boot loop! Here's what I did:
It was on Android 8.0 angler-opr5.170623.011-factory-0e60ceb6 but I unlocked its boot loader and installed custom recovery and I successfully flashed in the fastboot , vendor, radio and boot loader from Lineage OS 15.1 thread, now instead of following the rest of instructions, I madly decided to reboot the device using fastboot reboot and now I don't see anything except these colored circles which is what boot loop probably is! Please help me find a solution! Thank you!
edited: I have successfully entered into bootloader mode but don't know how to proceed!
I'd flash all the stock firmware in bootloader and start over. Grab the latest firmware package from Google's site, extract it, then run:
fastboot flash bootloader bootloader.img (name changes with version)
fastboot reboot-bootloader
fastboot flash radio radio.img (name changes with version)
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Reboot to system
You'll probably have to flash your custom recovery again in bootloader after the first boot. It usually reverts back to stock.
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page1
Part 10 in the thread above^
I recommend you installing an easy official ROM.
With them all you need to do is a clean flash of the ROM
Since I'm still a noob so I need to muster up courage to proceed but I really appreciate your valuable input guys!! Cheers!! :good:
edited: I have successfully installed stock firmware! cheers!
Hi,
I have a problem with a Moto G4. I tried to root the device and think I f***** up a bit.
After successfully installing TWRP I tried to install SuperSu using adb sideload and afterwards the device wouldn't boot anymore. Only fastboot and the recovery are still working. If I try to boot the device it just turns off. A factory reset didn't help.
I tried installing a LineageOS but nothing changed. It still boots into fastboot.
Can anybody help?
squanch123 said:
Hi,
I have a problem with a Moto G4. I tried to root the device and think I f***** up a bit.
After successfully installing TWRP I tried to install SuperSu using adb sideload and afterwards the device wouldn't boot anymore. Only fastboot and the recovery are still working. If I try to boot the device it just turns off. A factory reset didn't help.
I tried installing a LineageOS but nothing changed. It still boots into fastboot.
Can anybody help?
Click to expand...
Click to collapse
I forgot to say that I at first didn't install supersu systemless.
After I noticed that the device wouldn't boot anymore I tried installing it again systemless.
squanch123 said:
I forgot to say that I at first didn't install supersu systemless.
After I noticed that the device wouldn't boot anymore I tried installing it again systemless.
Click to expand...
Click to collapse
Hmm, did you wipe your system and data in TWRP before flashing LineageOS? You do not require root to flash LineageOS, just an unlocked bootloader and a compatible TWRP recovery (taking care to note if you need the 32 bit or 64 bit TWRP recovery for the respective custom ROM).
Also, with rooting on our G4/Plus, if you are on stock Nougat, you must flash a custom kernel (e.g. ElementalX) before you root. You'll otherwise experience the boot failures you're experiencing. Thus, to root on stock Nougat, unlock bootloader, flash/boot TWRP, backup, then flash ElementalX, then flash SuperSU/magisk.
Without knowing the current state of your device, I would suggest re-flashing your device with the stock firmware. Can you remember what stock firmware you had on your device before rooting initially?
echo92 said:
Hmm, did you wipe your system and data in TWRP before flashing LineageOS? You do not require root to flash LineageOS, just an unlocked bootloader and a compatible TWRP recovery (taking care to note if you need the 32 bit or 64 bit TWRP recovery for the respective custom ROM).
Also, with rooting on our G4/Plus, if you are on stock Nougat, you must flash a custom kernel (e.g. ElementalX) before you root. You'll otherwise experience the boot failures you're experiencing. Thus, to root on stock Nougat, unlock bootloader, flash/boot TWRP, backup, then flash ElementalX, then flash SuperSU/magisk.
Without knowing the current state of your device, I would suggest re-flashing your device with the stock firmware. Can you remember what stock firmware you had on your device before rooting initially?
Click to expand...
Click to collapse
Hi, thanks for your reply
Yes, I wiped system data and cache before flashing lineage. I just tried it again and I am still stuck in fastboot.
Unfortunately I don't remember the stock firmware version. Should I just try to flush the custom kernel and supersu afterwards?
squanch123 said:
Hi, thanks for your reply
Yes, I wiped system data and cache before flashing lineage. I just tried it again and I am still stuck in fastboot.
Unfortunately I don't remember the stock firmware version. Should I just try to flush the custom kernel and supersu afterwards?
Click to expand...
Click to collapse
Hmm, did you know if the flash of LineageOS reported okay within TWRP? Just out of interest, which TWRP and which build of LineageOS are you flashing (e.g. are you using the 32 bit TWRP or 64 bit TWRP, and are you flashing the 32 or 64 bit Lineage OS)?
That's confusing that even pressing 'start' in fastboot reboots your device rather than booting, even with a custom ROM... What happens if you boot to TWRP and try to reboot via TWRP? Is there a system to boot to?
Without the stock system on your device, there's no point to re-flashing the custom kernel/SuperSU, since you should have LineageOS on your device. Do you have a TWRP backup you could restore before you tried to root? If not, then what's your device model number (and if you can remember it, what software channel you're on, e.g. retus, reteu etc). ?
echo92 said:
Hmm, did you know if the flash of LineageOS reported okay within TWRP? Just out of interest, which TWRP and which build of LineageOS are you flashing (e.g. are you using the 32 bit TWRP or 64 bit TWRP, and are you flashing the 32 or 64 bit Lineage OS)?
That's confusing that even pressing 'start' in fastboot reboots your device rather than booting, even with a custom ROM... What happens if you boot to TWRP and try to reboot via TWRP? Is there a system to boot to?
Without the stock system on your device, there's no point to re-flashing the custom kernel/SuperSU, since you should have LineageOS on your device. Do you have a TWRP backup you could restore before you tried to root? If not, then what's your device model number (and if you can remember it, what software channel you're on, e.g. retus, reteu etc). ?
Click to expand...
Click to collapse
Yes, everything was ok with the flash.
I am using lineage-14.1-20180516-nightly-athene-signed and twrp-3.2.1-0-athene. I didn't see any options to choose between 32 and 64 bit. (Download pages: https://download.lineageos.org/athene#!name https://eu.dl.twrp.me/athene/)
It doesn't matter how I try to boot (powerbutton, fastboot, recovery) I always directly end up in fastboot.
No I don't have a backup. When I got the device it was resetted so I saw no point in making one :/ It is an XT1622 and it should be reteu.
squanch123 said:
Yes, everything was ok with the flash.
I am using lineage-14.1-20180516-nightly-athene-signed and twrp-3.2.1-0-athene. I didn't see any options to choose between 32 and 64 bit. (Download pages: https://download.lineageos.org/athene#!name https://eu.dl.twrp.me/athene/)
It doesn't matter how I try to boot (powerbutton, fastboot, recovery) I always directly end up in fastboot.
No I don't have a backup. When I got the device it was resetted so I saw no point in making one :/ It is an XT1622 and it should be reteu.
Click to expand...
Click to collapse
Okay, so they should both be 32 bit, so no worries there. There do seem to be a few reports of boot issues on the more recent official LineageOS builds https://forum.xda-developers.com/moto-g4-plus/development/rom-cyanogenmod-14-1-t3522101/page280 but I don't know if they are still existing on the build you've flashed.
As it's likely your device has been reset when you flashed LineageOS (I don't know if there are still files on your internal storage, which you can view in TWRP, so back up if you do have files), you may wish to look into a stock firmware flash. Here's the April 2018 NPJS25.93-14-18 firmware, which appears to be the build released to EU devices: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 You do not have to re-lock your bootloader if you don't wish to - if you wish to leave your bootloader unlocked, then flash the stock firmware via fastboot with the following flashing commands:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Flashing these files via ADB should put a fresh copy of the latest firmware onto your device, which should then boot. If it does boot, then you can proceed with rooting (flash TWRP, then back up, then flash ElementalX or vegito, then flash SuperSU or magisk).
echo92 said:
Okay, so they should both be 32 bit, so no worries there. There do seem to be a few reports of boot issues on the more recent official LineageOS builds https://forum.xda-developers.com/moto-g4-plus/development/rom-cyanogenmod-14-1-t3522101/page280 but I don't know if they are still existing on the build you've flashed.
As it's likely your device has been reset when you flashed LineageOS (I don't know if there are still files on your internal storage, which you can view in TWRP, so back up if you do have files), you may wish to look into a stock firmware flash. Here's the April 2018 NPJS25.93-14-18 firmware, which appears to be the build released to EU devices: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 You do not have to re-lock your bootloader if you don't wish to - if you wish to leave your bootloader unlocked, then flash the stock firmware via fastboot with the following flashing commands:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Flashing these files via ADB should put a fresh copy of the latest firmware onto your device, which should then boot. If it does boot, then you can proceed with rooting (flash TWRP, then back up, then flash ElementalX or vegito, then flash SuperSU or magisk).
Click to expand...
Click to collapse
Thanks for the help!
I can boot the stock rom and I have root access. However if I start or shut down the device it goes to fastboot. From there I can boot or shut down the device and everything seems to work Do you know how I can boot directly without fastboot?
squanch123 said:
Thanks for the help!
I can boot the stock rom and I have root access. However if I start or shut down the device it goes to fastboot. From there I can boot or shut down the device and everything seems to work Do you know how I can boot directly without fastboot?
Click to expand...
Click to collapse
Hmm, try booting back to the bootloader, attach your device to your computer, then open ADB. In ADB, type 'fastboot oem fb_mode_clear' without the quotes. Press enter to submit, then reboot and see if your device boots to system rather than to fastboot.
This command should clear fastboot mode (though useful when flashing).
echo92 said:
Hmm, try booting back to the bootloader, attach your device to your computer, then open ADB. In ADB, type 'fastboot oem fb_mode_clear' without the quotes. Press enter to submit, then reboot and see if your device boots to system rather than to fastboot.
This command should clear fastboot mode (though useful when flashing).
Click to expand...
Click to collapse
Yes that worked
Thank you very much for your help :victory: