Would anyone here have it? I overlooked the "7.1.1" message and used TWRP anyways, THEN used the 7.1.1 boot img which threw me into a bootloop, I can boot into EDL just fine, sideload doesn't work with me, so I see obtaining my original B2017G US boot.img and reflashing it with tulip as the best option to get back on track! Hope someone is able to help
Though, would there be any other methods of flashing the boot.img and removing the bootloop, like updating my firmware to 7.1.1 or something?
https://forum.xda-developers.com/showpost.php?p=73257562&postcount=13
I see something here, downloaded "Axon7mini_Android7(SD card software).zip" but unfortunately I don't know what to do with that update.zip file.
Related
Does anyone have or know where to get a stock recovery image for the BTV-W09?
When I flashed the US "003" update manually through the dload folder method, my TWRP was replaced by the stock recovery. I have left it there, and since flashed TWRP to recovery2. The update failed, but I ended up with stock recovery and the tablet no longer rooted. I would try that first. If that doesn't work for you and if you are on the US version "002" firmware let me know and I should be able to send you a backup of my recovery partition bit if you need the eRecovery from the recovery2 partition, I will be unable to help you.
I am on the US version “003”, I updated before flashing TWRP and rooting. TWRP was flashed recovery not recovery2. No worries though, Im sure someone will post a recovery as rooted people will be needing to flash OTA updates soon.
If you are on "003", try updating the unzipped "Update.Zip" from the dload file. I found a copy of the update.zip on my internal SD in directory called HwOUC. If you can't find it, I still have my file. The Update will most likely fail, but that should give you the standard recovery back. then I suggest you flash TWRP to Recovery2. TWRP actually is easier to access from Recovery2 becuase all you have to do is hold the volume up key down for a few seconds from the unlocked bootloader screen to boot into TWRP. Once you have TWRP re-installed you can then just flash the super user zip file to regain your root.
I am not sure if it is because I now have unlocked the bootloader, have recovery2 with TWRP or updated the file to enable the 5Ghz modem , but even with having the standard recovery partition back my system did not pass the altered system check and allow me to flash the OTA. I am not quite experienced enough to try and use Flashfire to force the update, since there is a warning about Huawei devices being easy to hard brick. Hopefully someone who has updated and then rooted will post an .img file of the updated system partition so it can be flashed with TWRP (at least I think that is what those of us who have already rooted will need to do).
I looked for the update.zip but it doesn’t exist anywhere. These updates are usually removed after the update completes successfully. Plus I’ve done a factory reset since updating, which may have deleted it. I wanted to see if enabling the 5GHz radio would stick after the reset (it did). The 5GHz radio hack was really my only reason to root. I didn’t alter my system partition with TWRP, so I may still be able to take an OTA update if I had the factory recovery. Ive stopped rooting all of my non Nexus devices. Since Google releases almost monthly security updates which usually unroots anyway it’s just too much hassle to keep root. If you want to post the update.zip somewhere I could give it a try, if not that’s cool. Im sure a factory image will be available at some point.
I have posted the Update.zip file to the following location:
http://www.mediafire.com/file/ug1pe2w38ddkxm9/update.zip
Let me know how things go.
Coming from a Nexus 7 I'm use to many of the img files you flash for restoring.
Using update extractor I now see many of those files (003 update) and some I have no idea about or how to flash them.
BOOT.img - OK
CRC.img - ?
CURVER.img - ?
EFI.img - I know what EFI is just never flashed it on an Android device.
FASTBOOT - OK
FW_HIFI.img - ?
FW_LPM3.img - ?
RECOVERY.img - OK
SENSORHUB.img - ?
SHA256RSA.img - No what it is normally but never flashed.
TEEOS.img - ?
TRUSTFIRMWARE.img - Interesting, but have no idea. - ?
VERLIST.img - ?
XLOADER.img - ?
Like many of us I'm in the same boat. Unlocked, Flashed recovery and rooted and cannot install update 003.
I've flashed the recovery.img from update 03. I've done a factory reset a few times. Odd enough it maintains 5Ghz wifi after doing a reset. I'm stumped and not sure of so many of the other .img files. Might one of them help me get the update to pass if I flash it. That or we wait for a full release and not an OTA to grab all the files we need. Really think I need system.img to make it work but the update doesn't include it.
Thanks johe for providing the 003 update.zip. I may try flashing the recovery.img this weekend. Ill let you know how it goes.
Jmjm003, I believe the issue with updating with the OTA is due to changes detected in the system partition after rooting/unlocking. Im not sure of a way around this other than flashing the full system partition, and we don’t have the factory ROM available yet. Im also new to Huawei devices and their partition structure so hopefully the development community will grow around this device and provide better solutions. I also can confirm the 5GHz stayed enabled after a factory reset, the question remains would it hold after an OTA update.
I flashed TWRP on my Moto G4 after booting the TWRP img using fastboot, and now I can't seem to get Android to start. I can boot into TWRP just fine, but when I try to start Android the phone screen just goes black and the LED USB indicator blinks.
Does anyone know what happened and how / if I can fix it without flashing the stock rom?
try flashing everything from recovery again? Maybe you messed up something, like rooting your rom without knowing it
I managed to get it to boot again by flashing the stock system image, but now there are a few odd bugs and I can't get the Android 7 OTA. Fastboot is giving me issues when I try to follow Motorola's instructions (gyazo.com/38675380995061a98714678c796ba92b, motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images) saying that the images aren't signed or are corrupt. I'll try just flashing the image files from TWRP like you said.
The forum won't let me link to websites.
I had the same boot problem after trying to systemless root after 7.0 updateon twrp 3.1. Had to reflash to stock recovery and stock boot image before it would boot to anything other than fastboot or a blank screen.
So it seems like the best solution for now is to not flash twrp as recovery when running Android 7 and just booting into twrp temporarily with
Code:
fastboot boot <twrp.img file>
I didn't have any problems systemless rooting my Android 7 phone with supersu doing it this way, the problem only started after I attempted to flash twrp as my recovery.
After flashing the stock firmware, my only issue now is not getting the OTA, which is very frustrating as I had it working earlier today.
EDIT; Found a possible solution for getting the OTA for XT1625 in another thread, flash XT1625-XT1644_ATHENE-RETUS_MPJ24.139-49_cid50_subsidy-DEFAULT_CFC.xml.zip to the phone from here firmware.center/firmware/Motorola/Moto%20G4%20%28Plus%29/Stock/
* Currently testing this now, not sure if it'll work
EDIT; Worked for me, a few seconds after booting I got the OTA update. I'm on Moto G4 (XT1625 Athene) retusa
If you want to know how to flash the .49 rom, refer to this thread (forum.xda-developers.com/moto-g4/development/unbrick-hard-bricked-moto-g4-amazon-t3486578) and follow the instructions as closely as you can. There are some differences between the Amazon version and the non Amazon.
IMPORTANT: do not attempt to systemless root (at least with SuperSu 2.79 SR3), it just caused Android to not boot. For now, wait for a fix. (But if you simply must attempt a root, make a backup in twrp)
Good luck!
unprofessional hacker said:
So it seems like the best solution for now is to not flash twrp as recovery when running Android 7 and just booting into twrp temporarily with
Code:
fastboot boot <twrp.img file>
Click to expand...
Click to collapse
Thanks for this! I didn't know how to do it until now
Guys, I need some help. I need to flash the stock kernel and recovery in order to update OTA to b381 (when I try to install it it goes into Revolution Recovery and the installation fails), but I can't find it anywhere... I tried to flash the ones in the b381 update but I had problems unlocking the phone since the code was not recognised, and had to bypass it with adb. Now I'm back to Revolution Recovery and Elite Kernel V4, what could have been the problem? The kernel or the recovery? Anyway, could anyone give me a link to the b371 stock boot.img and recovery.img? My internet connection sucks and I can't dowload the whole firmware to extract the images (I probably deleted the backups I had made before changing recovery and kernel, yes, I'm dumb).
This is the latest Nougat update that was released on 06/11/2018. It does not flash recovery or laf. If you must have laf, there is an additional zip to flash.
It is still ARB 2, so you can flash back to any version of Nougat.
I have removed the recovery-from-boot.p file from system so that recovery doesn't get overwritten, but that is the only change that was made -- this is not a debloated ROM.
Please let me know if you have any problems.
ROM download: h901_v30d.zip
OK, now for my spiel on laf...
You only need to install the laf zip if you have installed TWRP on laf in addition to recovery, and you would like download mode back.
I *HIGHLY* recommend that you keep TWRP on both recovery and laf. You will never be in a situation where download mode would help you, but TWRP couldn't.
You CAN be in a situation where TWRP could have helped you, but you are just stuck with download mode.
laf download: h901_laf.zip
-- Brian
Thanks for the update. I was very quick! I wanted to report that when flashing it did not show each file flashing like it usually does, it just keeps saying " please wait" , and then it finishes and on to the next zip which was the root file flash, that acted normally. I'm grateful Brian! Thanks
I'll take a look, I am sure I messed up a progress meter.
Thanks,
-- Brian
woohoo!
runningnak3d said:
This is the latest Nougat update that was released on 06/11/2018. It does not flash recovery or laf. If you must have laf, there is an additional zip to flash.
It is still ARB 2, so you can flash back to any version of Nougat.
I have removed the recovery-from-boot.p file from system so that recovery doesn't get overwritten, but that is the only change that was made -- this is not a debloated ROM.
Please let me know if you have any problems.
ROM download: h901_v30d.zip
OK, now for my spiel on laf...
You only need to install the laf zip if you have installed TWRP on laf in addition to recovery, and you would like download mode back.
I *HIGHLY* recommend that you keep TWRP on both recovery and laf. You will never be in a situation where download mode would help you, but TWRP couldn't.
You CAN be in a situation where TWRP could have helped you, but you are just stuck with download mode.
laf download: h901_laf.zip
-- Brian
Click to expand...
Click to collapse
thank you man! it works like a charm. no problem at all. .
:highfive:
Does it matter what version I'm coming from? Receiving a refurbished phone tomorrow that is supposed to be on LP but could be MM or even Nougat. I want to install TWRP like I did on my original phone (MB died) then upgrade to this.
Nope, doesn't matter. Once you get TWRP on your phone, you can flash this and go straight to the latest.
-- Brian
Does anyone have a link to the actual kdz?
I re-locked the phone trying to fix a grayed out "Enable OEM unlock" switch that was turned off in the developers options and in the process of locking the bootloader, it is unable to boot up again but I can still get into fastboot and download modes.
I know how to restore the phone through LGUP, just need the kdz, either 30c or 30d would work, thanks.
For some reason it seems that flashing this relocked the bootloader and bricked the device. Getting the message "Your device is corrupt. It cannot be trusted"
Was on 5.1.1 and it's my wife's phone. Downloaded the zip and Magisk and rebooted into TWRP. Flashed and now just about bricked. Now to try and see if I can unbrick the phone.
NightShade00013 said:
For some reason it seems that flashing this relocked the bootloader and bricked the device. Getting the message "Your device is corrupt. It cannot be trusted"
Was on 5.1.1 and it's my wife's phone. Downloaded the zip and Magisk and rebooted into TWRP. Flashed and now just about bricked. Now to try and see if I can unbrick the phone.
Click to expand...
Click to collapse
Same thing here, had to find a KDZ, found one and flashed it and everything is good now.
KDZ 30d: https://lg-firmwares.com/downloads-file/15906/H90130d_00_0611.kdz
ziphoy said:
thank you man! it works like a charm. no problem at all. .
:highfive:
Click to expand...
Click to collapse
hey guys how do i install this? i am comming from Eliminater74's stock. think its 5.x and i have twrp so not sure if i can just flash it. reason i ask is cuz another user said he had to kdz coming from 5.x so think i might have the same problem.
Tried using this one, Flashed, but only getting a boot back into TWRP what am I missing?
lg H901 30d root needed
hello can someone help me root LG H901-30d android 7 , i need to root this device but no method for this version (TMB)
Any other download link then Gdrive ???
When I try, it just shows a faliue msg after 10%
I just updated to android 10 oxygen os 10 but can't seem to flash twrp the usual way anyone got some advice? I've saw some tutorials online about extracting boot.img patching with magisk then flashing twrp installer as a module. Is that the only way just now or has someone got an easier way ?
Cheers
Thanks for the replies, I am already on A10 and got the update from Oxygen Updater app. I am using the boot IMG from the update file and patching it through magisk however when I flash it through fastboot method the phone is constantly on the boot animation stage. The only way for me to boot my phone again is to flash the original boot image.
I saw others were having positive results using this method does anyone know why it might not be working for me even though I'm following the same process?
I had some problems with twrp and android 10, so I wouldn't recommend it. I personally wait for the official support for android 10 and then flash twrp.
I downloaded the recovery from here: https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
And did this: https://forum.xda-developers.com/showpost.php?p=79489698&postcount=2538
But yeah, I still wouldn't recommend it. And I'm not sure if I did everything right. So it's your choice.
There is a pretty good way but you have to be coming from rooted 9.0.17. If you're already on 10 then I'm not sure. There is a parched boot img but I couldn't get everything working properly using it. That's probably my fault as I screwed up getting to A10 with decryptable twrp and magisk many times.
Thanks for the replies
Factory reset your phone from within stock recovery to get rid of any previous configuration. Then fastboot flash patched IMG again.
Evidently backup everything before on a computer