Related
Hi,
I have the Z5C with the latest stock firmware.
I wanted to do a little change to the /system/etc/hosts file. I tried to be smart (and failed). I did not want to flash anything so I only booted into TWRP, changed the file in terminal and rebooted.
Unfortunately after doing so I can neither boot to recovery or to the system itself. Fastboot works fine though. If I messed up the /etc/hosts then the recovery would still work fine - this rules out this option.
So after that I tried
rebooting
fastboot boot recovery.img
fastboot flash recovery recovery.img
...
If I unplug the cable in fastboot the phone just dies. If I turn it on it gets stuck on the Sony logo.
I did not expect that just booting to a recovery without actually flashing it could break anything Any idea please?
To even boot TWRP you have to have an unlocked bootloader. You may have presumed that by unlocking the bootloader that the integrity of the other partitions are no longer checked; however, the /system partition is in fact still protected by the Android "dm-verity" feature (https://source.android.com/security/verifiedboot/) even when bootloader is unlocked. So by mounting /system as read/write on TWRP and modifying the hosts file, you have changed the checksum of the /system partition.
You have two options:
Flash a modified kernel to the boot partition that disables dm-verity. Then you should be able to get the phone to boot with your modified /system partition. (I recommend this utility: https://forum.xda-developers.com/xp...oot-automatic-repack-stock-kernel-dm-t3301605 -- use this even if you don't want to root the phone: it will ask you individually what changes you want it to make to the kernel, and you can choose to *just* disable dm-verity if that's the only change you want to have made.)
Download the FTF for your firmware, and re-flash *just* the system partition with Flashtool in order to undo the change you made (Flashtool will allow you to selectively flash only certain partitions from a given firmware).
-- Nathan
Awesome! Makes sense! Thanks a lot.
After your reply it somehow (I do not know why) allowed me to boot to recovery. Therefore I reverted the change. I should have thought that it is going to checksum to verify the system integrity.
letalvoj said:
Awesome! Makes sense! Thanks a lot.
After your reply it somehow (I do not know why) allowed me to boot to recovery. Therefore I reverted the change. I should have thought that it is going to checksum to verify the system integrity.
Click to expand...
Click to collapse
You mean you simply edited the 'hosts' file and put the contents back to the way that they were? Honestly, if so, I'm surprised that worked...as I understand it, dm-verity happens on a block-level basis, not a file-level one, so even restoring the contents of particular files would not cause the checksum to go back to matching what the system is expecting (file contents now stored at different blocks/LBAs, file timestamps changed, etc.), which is why I thought flashing the original stock contents of the system partition would be necessary. In any case, glad to hear you are back in business.
-- Nathan
I screwed up my phone lol, when I was updating it to oreo, I didn't know that the update.zip file was corrupted.
Now I'm stuck on
Error!
Func NO : 9 (hifi image)
Error NO : 1 (security image failed)
My version was...
STF-L09C185B170
What i tried to install that failed is...
STF-L09C185B361 (8.0.0.361)
I can still go to fastboot with everything unlocked, I can also flash a twrp recovery, but only by typing flash recovery_ramdisk(instead "recovery"), and when I try to do the update method by pressing vol up, vol down, and power, it doesnt take me to the update section, it just show me a crashed screen, then goes back to error message.
I also tried volup and power, I can't seem to go to twrp(I think booting to twrp and flashing zip files can be one of the only ways to fix this). Is there a way to go to twrp recovery using fastboot?
I've also tried flashing extracted files from update.app manually, it doesn't work. Some files can be flashed, while some can't.
Please I'm begging u guys, pls halp :crying:
also I guess the lesson here is: double check if your file is corrupted before installing/flashing
First, what is the way you took triying to update ?
(When done from system UI, official or FF, there is an integrity check of downloaded files.)
It seems you got oreo partition scheme during your failed update.
First see this guide:
https://forum.xda-developers.com/mate-8/general/fastboot-erecovery-recovery-upgrade-mode-t3543441
Try to restore using erecovery. (download and update firmware via wifi)
If not working you could use HWOTA8.
For launching recovery (stock or twrp) from bootloader type "fastboot reboot recovery".
oslo83 said:
First, what is the way you took triying to update ?
(When done from system UI, official or FF, there is an integrity check of downloaded files.)
It seems you got oreo partition scheme during your failed update.
First see this guide:
https://forum.xda-developers.com/mate-8/general/fastboot-erecovery-recovery-upgrade-mode-t3543441
Try to restore using erecovery. (download and update firmware via wifi)
If not working you could use HWOTA8.
For launching recovery (stock or twrp) from bootloader type "fastboot reboot recovery".
Click to expand...
Click to collapse
I downloaded the oreo file using a browser and installed it with HWOTA, everything got inserted into my device, but the update failed and it gave me the error when I reboot. Also I can't get to erecovery or upgrade mode(that's the crashed screen), and "fastboot reboot recovery" doesn't work, it just show me a list of commands(which I assume happens if the command is invalid).
Ok I'll try HWOTA8, but I need to configure it so it recognizes my device, only my adb recognizes it.
Do 'fastboot devices work'?
Try english hwota8.
oslo83 said:
Do 'fastboot devices work'?
Try english hwota8.
Click to expand...
Click to collapse
Nah, I figured it out, I backed up my adb folder and just merged hwota8 with it. Yes, it does work.
Btw how do I fully turn off the device? it just keeps bootlooping if i hold down the volup and power key, maybe this is the reason why I can't get into twrp recovery.
My only hope is that I can flash something on fastboot that will let me go to update mode(or erecovery) or twrp.
Like.. anything, even boot.img fails when I try to flash it. It must be stuck on oreo partition.
Also I did considered dc phoenix, but I don't have the money to pay for an account. Man, why is unbricking not free on huawei devices? That guy prolly made a fortune by now(for holding everyone with unbrick leverage lel), and it's a huge mistake for me to fiddle with a huawei device, it has so many problems with twrp and root.
If anyone can find a way to do unbrick it, like anything, that would be great.
So you didn't manage to use honor9's hwota8 ?
oslo83 said:
So you didn't manage to use honor9's hwota8 ?
Click to expand...
Click to collapse
I used it but it didn't worked, I need to be either booted in the phone's os or inside twrp recovery bec. all of the commands executed by hwota8 are adb shell, not fastboot. Like I said, I only have access to fastboot, but I'll try again tomorrow. This is taking a lot of my time and I'm having panic attacks that I may not be able to fix this lol. Oh yeah, thanks for helping out.
Note: Since Oreo, partitions names have changed ; "recovery" changed to "recovery_ramdisk" now.
Use this command to flash recovery: fastboot flash recovery_ramdisk YourStockOrTwrpRecovery.img
Use oreo stock recovery or oreo twrp.
But I thought with hwotas available for honor 9 you started from bootloader...
oslo83 said:
Note: Since Oreo, partitions names have changed ; "recovery" changed to "recovery_ramdisk" now.
Use this command to flash recovery: fastboot flash recovery_ramdisk YourStockOrTwrpRecovery.img
Use oreo stock recovery or oreo twrp.
But I thought with hwotas available for honor 9 you started from bootloader...
Click to expand...
Click to collapse
I already did that, read the OP. Like I said, I can't boot into any recovery, not twrp not stock, not even upgrade mode, nothing.
As for hwota8, nope, it doesnt start from the bootloader, it's already trying to use the adb shell commands.
Anyway I'm taking all chances, I'm trying to research oreo's partitions names, and I'm also trying to find out how to bypass this message "FAILED (remote: Command not allowed)" bec. it might be the only way I can salvage this phone.
edit: ok im trying hwota8 again, maybe i missed something, and yes it has fastboot, sorry i was rushing but im trying again now, i'll post my progress later
MANUALLY INSTALLING FULL NOUGAT 7.11 FIRMWARE 2018/03/15(security_patch 2018-02-05) (RECOVERY, BOOT, SYSTEM) Even If Its Soft Bricked Because You Messed Up Somewhere. Files Here Are For Asus Zenfone 3 Zoom ZE553KL Z01HD WW Sku .
Its The Last Nougat Update Before Oreo Was Released.
MORE FIRWARES HERE
Story Time:
As I Remember It.....Condensed Version, This Was Over A Few Days Of Trial And Error, Mainly Because Adb SideLoad Refused To Flash Asus's Stock Firmware Zip Files.
I Messed Up My Friends Asus Zenfone 3 Zoom, ZE553KL.
He Bought Used, He Quickly Updated To Oreo From Within The Phones Update But Was Having Missed Texts And Slow Lte(4g) Speeds, He Wasnt Sure If It Happened On Nougat Which The Phone Was On Originally.
Downgraded To 6.01, Installed Twrp, Magisk, Still Having Same Issues, Flashing An Update Zip W/a Modded Updater Script Via Twrp Caused A Soft Bricked Phone, It Never Completed The Flash, Twrp Backup Didnt Work, Factory Reset A No Go, Couldn't Manually Flash Stock Rom As Adb Sideload Always Gave Errors, Fastboot System images Didnt Help For One Reason Or Another, Phone Was Just Bootlooping Back To The Unlocked Bootloader Menu.
Down Loaded Alot Of Stuff, Read Countless Pages, And Somehow Got The Right Firmware Files(recovery, boot, system img files) That Was Flashable Via Fastboot Extracted From A Zip, My Fix Is Below. These Are Not My Files But I Cant Remember Where I Got Them From As I Dl-ed Alot Of Stuff Trying To Get This Phone To A Running State. No I Havent Tried Oreo Yet, He Has His Phone Back Now And Not Sure When He'll Let Me Play With It Again, Lol.
UPDATE TO THIS STORY
HOWTO FLASH
PREREQUISITES:
Make A Nandroid Backup
If Bootable Remove/Signout Of Google Account
(Might Work With Locked Bootloader, IDK)
Ze553kl(Zenfone3 Zoom) Phone With Unlocked Bootloader(used unlocker apk from asus website when phone was in running state)
Unlocking Bootloader App Available From Asus - was for upto nougat 7.11
Usb Asus Drivers
Usb Debugging Enabled On Phone, Maybe Not But Wont Hurt To Try
Adb Fastboot Program(Included)
Recovery, Boot, And System Img Files Of Nougat 7.11(Included)
Computer Running Windows
Usb Data Cable For Phone
ON PHONE-
If Bootable Enable Usb Debugging, Uncheck Verify Apps Via Usb, Install From Unknown Sources, Remove Google Account
Backup Internal Sdcard - Most Def
Remove Sdcard, Just In Case
Put Phone Into Fast Boot Mode- Unplugged, Phone Powered Off - Vol Up + Power Button Pressed, Hold Both Until Screen Comes On.
Plug Usb In Cable To Phone From Pc.
ON COMPUTER-
From The Download Section Below Dl ADB_FASTBOOT_1.4.1.ZIP File And Extract It Into A New Empty Folder.
Download And Copy The Three .Img Files From The Download Section Below Into This New Adb Folder
HOW TO RUN ADB VIA COMMAND PROMPT? -
From Within Adb-fastboot Folder You Created, Nothing Selected, Hold Down The Shift Key Then Use The Right Mouse Button To Click In Empty Space In The Adb-fastboot Folder, Select "Open Command Window Here" From The Menu That Pops Up.
From Within Command Prompt Type-
Adb Devices
It Should Output A Device With A String Of Letters And Numbers, Thats Your Phone.
Next Steps Will Install Nougat 7.11 And Consequently Wipe Your Phone
Run These 5 "fastboot" Commands One At A Time.
When Each Step Is Completed Run The Next Command, You Can Copy And Paste These Five (5) Fastboot Commands Into The Command Prompt Window
----------------------------------------------------------------------
1.
Code:
fastboot flash recovery recovery-zoom-7.11.img
2.
Code:
fastboot flash boot boot-zoom-7.11.img
3.
this one @ ~4gb will take awhile to initialize and complete, patience needed
CAN REDO THIS SYSTEM FLASH NOW TO MAKE SURE IT "STICKS"
Code:
fastboot flash system system-zoom-7.11.img
4.
wipes internal sdcard
Code:
fastboot format userdata
5.
Code:
fastboot reboot
-------------------------------------------------------------------------------------------
if you were successfull it will boot into 7.11, takes about 3-5 mins to boot.
IF DID NOT FLASH PROPERLY OR ODD BEHAVIOR AFTER REBOOT THEN REDO STEPS AGAIN....ELSE KEEP READING!
------------------------------------------------------------------------
IF STILL BRICKED OR ODD BEHAVIOR BUT CAN BOOT TO BOOTLOADER/FASTBOOT THEN DO THESE COMMANDS WHEN IN FASTBOOT MODE
Code:
fastboot erase system
fastboot erase recovery
fastboot erase boot
fastboot erase userdata
fastboot -w
fastboot erase splash
fastboot erase cache
THEN RE-BOOT BACK INTO BOOTLOADER AND DO THE FLASH FOR 7.11 FIRMWARE
STILL HAVING ISSUES, RESTORE USING TECH FW THAT REFLASHES ALL MDMS, RADIOS, DRIVERS ETC FROM HERE
[FW] 7.1.1 & 6.0.1 Service Tech Firmwares - Debrick - Upgrade - Downgrade
- -------------------------------------------------------------------------------------
disclaimer im not responsible for yours or anyone elses devices, do at your own risk
DOWNLOADS
PHONE FILES ARE FROM A Asus Zenfone 3 Zoom ZE553KL WW SKU FIRMWARE Version WW-71.60.139.30 2018/03/15
RECOVERY-ZOOM-7.11.IMG
md5 03d8358e1341a73b5a492c12e3dbe39e
BOOT-ZOOM-7.11.IMG
md5 1ad55f9852d56b79a95654173af5649a
SYSTEM-ZOOM-7.11.IMG
md5 7217f778701c988271739ab18fb0fb30
ADB_FASTBOOT_1.4.1.ZIP
..
Thanks for the information...
I can provide you latest system,boot, recovery.img files if you want...
Do you know how to make raw firmware?? Because that could come handy for hard bricked phones.
Deleted. Double post
Naman Vashishth said:
Thanks for the information...
I can provide you latest system,boot, recovery.img files if you want...
Do you know how to make raw firmware?? Because that could come handy for hard bricked phones.
Click to expand...
Click to collapse
What do u mean by raw. In what format is it in.
I've converted oreo stock firmware .dat files to .img files but I can't test them as I don't have the phone. My friend seems happy on nougat and I don't think he'll let me flash it on his phone.
I haven't tried dl-ing official stock and seeing if phone will see it as an update to manually self install via nougat recovery or maybe to try adb sideload again.
Naman Vashishth said:
I can provide you latest system,boot, recovery.img files if you want...
Click to expand...
Click to collapse
Please do - I could sure use them.
Work very well !
ciao
God bless you! You made my quite dead phone, live again!
Thank you
I can't update to Oreo via ota... do you know why?
the op here. lol, my friend dropped the phone and now its dead screen, no display/no touch but phone still works.
he doesnt want to get a screen for it as it will cost almost as much as he paid for it.......so its mine now.
been flashing stuff to it, gave it a very hard soft brick, still dealing with that.
my goal was to run it remotely but get adb/usb debugging enabled and get pc trusted by phone. i thought he wanted to sell it as is but decided to give to me to do whatever i want to it
got out of the hard soft brick, installed twrp, use twrp cli, twrp backups and restore, rooted w/magisk, installed 6.0.1 (fluked it), 7.11 using my method above with the extra erase commands, removed frp, got adb /usb debugging enabled and device adb authorized by hacking , got vysor, a remote control mirroring app running, all without a working screen.
i'll write up a tut for any1 else that needs help. fyi, weak screen if dropped even short distance, but he had no cover, but pretty to hard to brick it, imo, ymmv
So can i downgrade my phone from android 8 to 7.1.1 following this process.
kingairtel08 said:
So can i downgrade my phone from android 8 to 7.1.1 following this process.
Click to expand...
Click to collapse
yes, i went from 8.0 to 7.11 then to 6.01
more fw here https://forum.xda-developers.com/ze...fw-7-11-6-0-1-service-tech-firmwares-t3850000
Bro i am on 8.0 and want to unlock bootloader and root it n enable cam2api in it, as unlocker nt working in android 8.0 so i want to back to 7.1.1. thank u bro,i will try it tonight.
Bro installed successfully 7.1.1 but microphone sound stopped.when calling cant hear anything.what to do ?unlock tool not working on it.
kingairtel08 said:
Bro installed successfully 7.1.1 but microphone sound stopped.when calling cant hear anything.what to do ?unlock tool not working on it.
Click to expand...
Click to collapse
after flashing did u, in stock recovery, do a factory reset and wipe caches aka wipe user data in fastboot.
else do a complete wipe as outlined in op
yes bro i m on stock recovery ,did wipe cache etc.
kingairtel08 said:
yes bro i m on stock recovery ,did wipe cache etc.
Click to expand...
Click to collapse
does etc mean factory reset?
did u do the extra procedure to completely erase everything as posted in op in the section of when still having issues
yes bro. i followed all steps .
kingairtel08 said:
yes bro.
Click to expand...
Click to collapse
yes to which
this?
fastboot erase system
fastboot erase recovery
fastboot erase boot
fastboot erase userdata
fastboot -w
fastboot erase splash
fastboot erase cache
if yes then do a full restore of radio, mdm etc from here using method 1 or 2
https://forum.xda-developers.com/att-s7-edge/how-to/fw-7-11-6-0-1-service-tech-firmwares-t3850000
i did all this steps then flash firmware img.
kingairtel08 said:
i did all this steps then flash firmware img.
Click to expand...
Click to collapse
which method did u use from the link i posted
bro i dnt have the 7.1..1 zip file ,i used ur 7.1.1.img file,used method 2.
i will try once again ,wil reply within 2hours.
bro i want to unlock my phone whats why i downgrade,but after downgrading checked official unlock tool gives the same network error that gives on android 8.0.is there any way to unlock it on this 7.1.1 firmware?
I have a US Unlocked Nord N200 5G that I bought recently.
I was trying to flash a GSI ROM to it, but apparently the ROM was in the wrong format or otherwise incompatible, because it just kept boot-looping with the OnePlus logo instead of actually booting into the ROM. (I got one that said it was "A/B format")
So, thankfully I get the Fastboot screen when I try to turn it on now. Either that or the Qualcomm CrashDump screen.
Easiest way would be to use the MSM tool, however only the T-Mobile variant of that has leaked. The program immediately told me I had the wrong model when I tried it.
I contacted OnePlus support, and after about 48 hours they said "sorry, we can't help you, wait for the next firmware update" so the idea of having them do a remote session to use the MSM tool is out of the question.
I have the extracted stock firmware files, however I don't have the fastboot commands to flash them. I tried to wing it, and get various errors.
So instead I followed the commands from this thread about converting the T-Mobile one to stock, and this is what I get.
First, "fastboot reboot fastboot" doesn't work - somehow the stock "recovery" thing got corrupted, so it's just the one that has START written in ASCII art at the top.
>fastboot flash system system.img
Invalid sparse file format at header magic
Sending sparse 'system' 1/3 (689036 KB) OKAY [ 17.058s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Click to expand...
Click to collapse
And it does the same for the other ones too. It won't let me flash "bluetooth" saying "Flashing is not allowed for Critical Partitions"
Other stuff gives me "fastboot: error: Could not check if partition vbmeta has slot all"
I'm using a current version of fastboot.exe.
I think the issue is I'm stuck in that fastboot mode, not the "fastbootd" mode with the fancier text on it... that seems to have been erased. "fastboot reboot recovery" takes me right back to the original fastboot screen.
I can put the phone in EDL mode, but without the right files I can't do anything else with it. What do you guys suggest? I have the OxygenOS 11.0.5.0.DE17AA files.
Sounds like the phone's not booting because the GSI you flashed doesn't match with the signatures in the stock vbmeta image. To fix this, you should flash a blank vbmeta image such as the one I attached with the following command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta AOSPvbmeta.img
After that, your phone should stop bootlooping or crashdumping every time you try to boot it. After that, you can either flash a GSI or use the guide for converting the T-Mo N200 to stock to restore back to OxygenOS.
lzgmc said:
Sounds like the phone's not booting because the GSI you flashed doesn't match with the signatures in the stock vbmeta image. To fix this, you should flash a blank vbmeta image such as the one I attached with the following command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta AOSPvbmeta.img
After that, your phone should stop bootlooping or crashdumping every time you try to boot it. After that, you can either flash a GSI or use the guide for converting the T-Mo N200 to stock to restore back to OxygenOS.
Click to expand...
Click to collapse
Thanks for the blank vbmeta.
I was able to flash that fine; but the phone still doesn't do anything. As I explained, my tinkering with it trying to follow the T-Mobile instructions to reflash partitions, I somehow managed to delete almost everything from the phone. Even doing "fastboot reboot fastboot" *does not get me into fastbootd mode*, just back to the original "dumb" fastboot mode.
Nothing is booting anymore because there's nothing left to boot!
And I can't use the MSM tool because this is not a T-Mobile phone, and the program knows that. It immediately fails saying the target model doesn't match the ROM I'm flashing to it.
Is there a way to override that with the MSM tool? Or am I SOL until OnePlus helps me? I was able to use fastbootd to delete the partitions but then it errored trying to remake them, and I'm left with basically nothing usable.
Possible answer Here
drfsupercenter said:
I have a US Unlocked Nord N200 5G that I bought recently.
I was trying to flash a GSI ROM to it, but apparently the ROM was in the wrong format or otherwise incompatible, because it just kept boot-looping with the OnePlus logo instead of actually booting into the ROM. (I got one that said it was "A/B format")
So, thankfully I get the Fastboot screen when I try to turn it on now. Either that or the Qualcomm CrashDump screen.
Easiest way would be to use the MSM tool, however only the T-Mobile variant of that has leaked. The program immediately told me I had the wrong model when I tried it.
I contacted OnePlus support, and after about 48 hours they said "sorry, we can't help you, wait for the next firmware update" so the idea of having them do a remote session to use the MSM tool is out of the question.
I have the extracted stock firmware files, however I don't have the fastboot commands to flash them. I tried to wing it, and get various errors.
So instead I followed the commands from this thread about converting the T-Mobile one to stock, and this is what I get.
First, "fastboot reboot fastboot" doesn't work - somehow the stock "recovery" thing got corrupted, so it's just the one that has START written in ASCII art at the top.
And it does the same for the other ones too. It won't let me flash "bluetooth" saying "Flashing is not allowed for Critical Partitions"
Other stuff gives me "fastboot: error: Could not check if partition vbmeta has slot all"
I'm using a current version of fastboot.exe.
I think the issue is I'm stuck in that fastboot mode, not the "fastbootd" mode with the fancier text on it... that seems to have been erased. "fastboot reboot recovery" takes me right back to the original fastboot screen.
I can put the phone in EDL mode, but without the right files I can't do anything else with it. What do you guys suggest? I have the OxygenOS 11.0.5.0.DE17AA files.
Click to expand...
Click to collapse
i have a bricked unlocked phone myself .. having the latest platform-tools is not enough for me to get anything on this phone .. mine is also rebooting on loop as i made the mistake and didn't unlock the OEM
I found (on this website) an LGUP tool (version) that is for the MS330. So it works (albeit not so consistently). The LGUP tool was able to flash a .kdz file after several trials. Apparently when LGUP connects, it puts the MS330 in bootloader mode, waits 15 seconds for the device to respond and then begins flashing.
Now, here's the problem. I have a .tot file I'd like to flash. When trying to flash a .tot file, 15 seconds is not enough time for the device to respond, and I get an error for what appears to be an asynch error. That is to say, the MS330 took a second or two more that the 15 seconds to respond saying, yes I'm in bootloader mode.
Is there any way to give it a bit more time? Surely the members who use LGUP tool would have encountered this behavior, and would have found a solution.
Tried changing ports, cables, computers. No improvement
Words of wisdom, anyone?
BigZ1 said:
I found (on this website) an LGUP tool (version) that is for the MS330. So it works (albeit not so consistently). The LGUP tool was able to flash a .kdz file after several trials. Apparently when LGUP connects, it puts the MS330 in bootloader mode, waits 15 seconds for the device to respond and then begins flashing.
Now, here's the problem. I have a .tot file I'd like to flash. When trying to flash a .tot file, 15 seconds is not enough time for the device to respond, and I get an error for what appears to be an asynch error. That is to say, the MS330 took a second or two more that the 15 seconds to respond saying, yes I'm in bootloader mode.
Is there any way to give it a bit more time? Surely the members who use LGUP tool would have encountered this behavior, and would have found a solution.
Tried changing ports, cables, computers. No improvement
Words of wisdom, anyone?
Click to expand...
Click to collapse
What is going on? Wierd error/problem here.
OK! All of this above is OBE. I managed to get the bootloader unlocked, so I am now free to load custom roms. Well, sort of. I rooted the system, and tried to install TWRP from the playstore. When I got to the part about flashing recovery with the TWRP image, it fails. Just says Flash failed.
So, I went back to using adb and fastboot. I used "flashboot flash recovery TWRPfilename". That worked. Then "adb reboot recovery" took me to TWRP. So far, so good. When I shut down the phone and use the power/volume keys to boot into recovery, I get the stock rom recovery, not TWRP. If I connect the usb cable and use "fastboot reboot recovery" I get TWRP
What is going on here? Anybody who has a clue, please share your thought of the problem and/or possible fixes.
Thanks!
BigZ1 said:
What is going on? Wierd error/problem here.
OK! All of this above is OBE. I managed to get the bootloader unlocked, so I am now free to load custom roms. Well, sort of. I rooted the system, and tried to install TWRP from the playstore. When I got to the part about flashing recovery with the TWRP image, it fails. Just says Flash failed.
So, I went back to using adb and fastboot. I used "flashboot flash recovery TWRPfilename". That worked. Then "adb reboot recovery" took me to TWRP. So far, so good. When I shut down the phone and use the power/volume keys to boot into recovery, I get the stock rom recovery, not TWRP. If I connect the usb cable and use "fastboot reboot recovery" I get TWRP
What is going on here? Anybody who has a clue, please share your thought of the problem and/or possible fixes.
Thanks!
Click to expand...
Click to collapse
One more tidbit of info. I tried flashing TWRP (installed from the playstore) several times. At first all I got was Flash Failed. Now (for no apparent reason) it was able to flash the TWRP file. So I thought I'd test it out. No change. Still can't boot into recovery by using vol-and pwr. Still takes me to stock rom recovery. But (same as before) adb reboot recovery takes me right to TWRP, and it's working fine.
I am not doing any data wipes, formatting, changing permissions, etc. . Anybody have any experience with this problem, or any thoughts on how to fix it????
BTW, this is for an LG K7 MS330m1.