Related
Hey all,
So I received a notification for a system update to 4.4.3, and I had survival mode in SuperSU checked, so I went ahead and followed the procedure. Turns off, then reboots into TWRP. From there I reboot again using the TWRP option, and it boots into android just fine. Notification is gone, still with root. But then I go to settings >> about to find that I'm still running on 4.4.2. Manually check for update, says there isn't one available. Give it a day or so and the notification comes up again. Repeat, and same thing. I'm stuck with the notification again.
So, how do I get rid of the notification, or more preferably, how to I update to 4.4.3 keeping the root? Thanks.
UnfriendlyTurtle said:
Hey all,
So I received a notification for a system update to 4.4.3, and I had survival mode in SuperSU checked, so I went ahead and followed the procedure. Turns off, then reboots into TWRP. From there I reboot again using the TWRP option, and it boots into android just fine. Notification is gone, still with root. But then I go to settings >> about to find that I'm still running on 4.4.2. Manually check for update, says there isn't one available. Give it a day or so and the notification comes up again. Repeat, and same thing. I'm stuck with the notification again.
So, how do I get rid of the notification, or more preferably, how to I update to 4.4.3 keeping the root? Thanks.
Click to expand...
Click to collapse
You can't update the "normal way" like that with a custom recovery. When you try to do that, it tries to boot into the stock recovery to update, but since you have a custom recovery, it will fail everytime if you do it that way. What you have to do is flash the OTA zip using TWRP. You can find the OTA zip in /cache on your device. Or you can just download the update zip from these forums.
UnfriendlyTurtle said:
Hey all,
So I received a notification for a system update to 4.4.3, and I had survival mode in SuperSU checked, so I went ahead and followed the procedure. Turns off, then reboots into TWRP. From there I reboot again using the TWRP option, and it boots into android just fine. Notification is gone, still with root. But then I go to settings >> about to find that I'm still running on 4.4.2. Manually check for update, says there isn't one available. Give it a day or so and the notification comes up again. Repeat, and same thing. I'm stuck with the notification again.
So, how do I get rid of the notification, or more preferably, how to I update to 4.4.3 keeping the root? Thanks.
Click to expand...
Click to collapse
Since 4.4.4 is out, just download the full firmware package from Google and flash system, boot. Only those two.
If you don't know how to do that, the Nexus 5 forums has some great stickies that are mostly relevant to this device.
charesa39 said:
You can't update the "normal way" like that with a custom recovery. When you try to do that, it tries to boot into the stock recovery to update, but since you have a custom recovery, it will fail everytime if you do it that way. What you have to do is flash the OTA zip using TWRP. You can find the OTA zip in /cache on your device. Or you can just download the update zip from these forums.
Click to expand...
Click to collapse
Right, thanks for the information. So I repeated and booted into TWRP again. Tapped 'Install', navigated to /cache, saw a couple of folders named 'back up', 'lost+found', and then a file name of a large string of letters followed by the recognisable "razor KTU70 from KOT49H", so I went ahead and flashed the latter, checking 'verify signature'. Runs through a few commands and in a few seconds comes back as failed, so I reboot into the OS.
Any ideas?
Aerowinder said:
Since 4.4.4 is out, just download the full firmware package from Google and flash system, boot. Only those two.
If you don't know how to do that, the Nexus 5 forums has some great stickies that are mostly relevant to this device.
Click to expand...
Click to collapse
I think I have an idea, but I'll check just to be sure. Thanks for the direction.
Exactly the same for me. Installing the ota sent me to my TWRP recovery. Reboot - > still in 4.4.2.
Reading this thread, I went to TWRP recovery, installed the update from cache and like you, it failed.
Any suggestions? Did your idea work?
Where do I find the 4.4.4 mentioned here and how do I flash it in TWRP? Is install the same as flash in TWRP?
Thanks.
Anderson2 said:
Exactly the same for me. Installing the ota sent me to my TWRP recovery. Reboot - > still in 4.4.2.
Reading this thread, I went to TWRP recovery, installed the update from cache and like you, it failed.
Any suggestions? Did your idea work?
Where do I find the 4.4.4 mentioned here and how do I flash it in TWRP? Is install the same as flash in TWRP?
Thanks.
Click to expand...
Click to collapse
If it fails look to see what the specific error is. It would help to know that. If you pulled it from your cache then I assume it was downloaded by itself and should be the correct OTA. I do NOT have the "Zip file signature verification." box checked or "Enable MD5 verification of backup files." but I am extremely careful to flash/install the correct files. The OTA installed fine for me two days ago using TWRP 2.7.1.0. The 4.4.4 mentioned earlier is the factory image. You will need adb and fastboot installed on your computer to flash the factory image or any image that is pulled from inside the factory image. Wug's toolkit will work also, I think, but I've never used any toolkits. Eventually there will be a stock 4.4.4 rom that you can flash/install in TWRP but I'm not aware of one right now.
You can take the normal updates with root and TWRP (I did), but a custom kernel will prevent them from installing.
I retried to install the downloaded ota file from cache, but this time I checked zip file verification and got the error message that zip verification failed.
File name was
df43279bcf6bb6a0ae403249c3e6f314d0a7eb77.signed-razor-KTU84L-from-KOT49H.df43279b.zip
So it seems the downloaded ota file may be corrupted. How do I get my Nexus 7 2013 to re-download a new one?
(The ota download for my Nexus 5 installed with no problems - but I think it didn't go through TWRP even though TWRP is installed there too).
Thanks
---------- Post added at 04:05 AM ---------- Previous post was at 03:59 AM ----------
Further
I renamed the ota file and in settings checked for system update and got a response that my system is upto date. But it is still 4.4.2.
Need to re-download the ota. How?
Changed the system date to 2 weeks earlier and succeeded in re-downloading the ota file.
So I retried installing it and it again took me to my TWRP recovery screen. I again installed the ota from cache and again the zip verification failed : 1
And the update failed again.
Still on 4.4.2
Did not change any system files as far as I know.
Need help.
Why don't you guys download the stock firmware from Google (link in my signature), and use fastboot to flash system.img, boot.img (DO NOT run the batch file)? If it's a lack of knowledge, all you need do is ask, and I or someone else would be happy to teach you how to use it (fastboot). If you're going to be modifying your Nexus device, you need to learn fastboot. You guys have got to learn the proper way to do things.
You've put forth so much effort to fix a system that is not meant for modified (rooted, customized) phones. You can't fix it, stop trying. Just do it the proper way. And do not use a toolkit. They don't teach you anything, they spoon-feed.
Aerowinder said:
Why don't you guys download the stock firmware from Google (link in my signature), and use fastboot to flash system.img, boot.img (DO NOT run the batch file)? If it's a lack of knowledge, all you need do is ask, and I or someone else would be happy to teach you how to use it (fastboot). If you're going to be modifying your Nexus device, you need to learn fastboot. You guys have got to learn the proper way to do things.
You've put forth so much effort to fix a system that is not meant for modified (rooted, customized) phones. You can't fix it, stop trying. Just do it the proper way. And do not use a toolkit. They don't teach you anything, they spoon-feed.
Click to expand...
Click to collapse
I don't use a toolkit and would be happy to flash the system.Img and boot.img but need instructions on how to do it. You said the stock firmware link is in your signature but it isn't.
I would like to skip 4.4.3 and go directly from 4.4.2 to 4.4.4. I'm talking about a nexus 7 2013 wifi.
So I need the following information to proceed .
1. The Link to download system.img and boot.img for the nexus 7 2013 wifi. Which files exactly?
2. I have fastboot and adb installed on my windows 7 laptop because I used them (once) to root but I don't remember how I used them that one time. How exactly do I use fastboot to flash 4.4.4 ?
3. I presume I will lose root. How do I regain it after the above.
Thank you.
Anderson2 said:
I don't use a toolkit and would be happy to flash the system.Img and boot.img but need instructions on how to do it. You said the stock firmware link is in your signature but it isn't.
I would like to skip 4.4.3 and go directly from 4.4.2 to 4.4.4. I'm talking about a nexus 7 2013 wifi.
So I need the following information to proceed .
1. The Link to download system.img and boot.img for the nexus 7 2013 wifi. Which files exactly?
2. I have fastboot and adb installed on my windows 7 laptop because I used them (once) to root but I don't remember how I used them that one time. How exactly do I use fastboot to flash 4.4.4 ?
3. I presume I will lose root. How do I regain it after the above.
Thank you.
Click to expand...
Click to collapse
1. The Google firmware link in my signature is the one you want. You say you have the 2013 wifi model, aka flo, aka razor. "Factory Images "razor" for Nexus 7 [2013] (Wi-Fi)" is the proper section for you. You want 4.4.4 (KTU84P), and that's at the bottom of the razor section. Click the link to download.
2. Download the most up to date ADB/Fastboot from the link in my signature (19.0.2 (API 19)). Don't extract it yet.
3. You will lose root. Download SuperSU from my signature. 2.00 is the current version. After you download that, you can put it on your device so you can flash it in recovery in a few minutes.
The firmware you downloaded is razor-ktu84p-factory-b1b2c0da.tgz. This is a compressed archive, and you will need to extract it. If you don't know how, 7-Zip should work.
So, you've extracted the files. Delete flash-all.bat, flash-all.sh, flash-base.sh (so you don't accidentally run them).
Now, all you have left is bootloader-flo-flo-04.02.img and image-razor-ktu84p.zip.
Extract image-razor-ktu84p.zip to the current directory, so you will now have bootloader-flo-flo-04.02.img, boot.img, cache.img, recovery.img, system.img, userdata.img, android-info.txt, image-razor-ktu84p.zip in your folder.
Delete userdata.img, flashing this on accident will wipe your data. Delete image-razor-ktu84p.zip, android-info.txt, cache.img, recovery.img (this is stock recovery, you want TWRP).
Now you have boot.img, bootloader-flo-flo-04.02.img, system.img.
Remember the ADB & Fastboot zip you downloaded from my signature? Extract it to the directory with bootloader-flo-flo-04.02.img, boot.img, system.img. All 4 files. This directory now contains 7 files.
Back out of the razor-ktu84p folder. Just one step back. Now, hold shift the right-click the razor-ktu84p folder. Select Open command window here.
Reboot your device to bootloader mode. Do so by shutting it down. Then while the power is off, hold volume down and press the power button. Release these buttons when you see the big green Android.
In your command window, type the command: fastboot devices
Your device with it's serial number should show up on the list. If it does not there is a problem and you need to stop here.
If the device shows up, let's update it.
fastboot flash bootloader bootloader-flo-flo-04.02.img
<wait for it to finish>
fastboot reboot-bootloader
<wait for it to reboot>
fastboot flash system system.img
<wait for it to finish>
fastboot flash boot boot.img
<wait for it to finish>
fasboot reboot-bootloader
Done with fastboot.
At this point, enter recovery (TWRP) and wipe cache and Dalvik under advanced wipe.
Remember the SuperSU you downloaded earlier and put on your device for later? Flash that now.
Reboot, all done. Most of this is just juggling files around. If you have any questions ask.
You are wonderful aerowinder. This is just what I needed to go ahead. Thank you so much.
About your signature, it doesn't show the links when viewed in my Tapatalk version, but I went to the Web view and got it from there. (just FYI if others ask about your links).
is it possible to just flash the system img in fastboot? It's still the same bootloader, not updated? Could I just flash the whole zip by sideloading in adb and TWRP? Just a lottle confused. Thanks!
droider137 said:
is it possible to just flash the system img in fastboot? It's still the same bootloader, not updated? Could I just flash the whole zip by sideloading in adb and TWRP? Just a lottle confused. Thanks!
Click to expand...
Click to collapse
If you were already on 4.4.3, all you need to do is fastboot flash system.img, that is correct.
No, you can't flash that firmware zip in recovery.
thanks
Hi Aerowinder
Thanks again for the excellent instructions. Everything went like clockwork until it didn't ?......
I got to the point where I issued the command fastboot devices which did show the tablet serial number. But my next command to flash the bootloader img gave me the error:
Cannot open 'bootloader-flo-flo-04.02.img
(I had copy pasted the command from your instructions).
The subdirectory below the command window contains that file (one of 7 files)
Sorry. What should I do?
In case you need the info, the device screen showed
Fastboot mode
Product name - flo
Variant - flo 32G
Hw version - rev_e
Bootloader version - flo-04.02
Carrier info = none
Serial number - xxxx
Signing - yes
Secure boot enabled
Lock state - unlocked
Thanks again.
Aerowinder, you are not only an expert but an excellent teacher. Your instructions above should be a sticky.
I'm all done. Everything is fine.
The problem I had above was a file path problem. Not sure why you told me to open the command window in the parent folder. When I opened it in the folder containing the seven files all your commands worked fine. (Except for your last one where you had a spelling mistake: fasboot instead of fastboot).
Thank you very much.
SO, i'm trying to ADB sideload the latest firmware (MRA58V), but when I go to the google developers website, it downloads in a .TGZ file.
https://developers.google.com/android/nexus/images
I've tried changing it to .ZIP, then flashing, but it fails invalid signature.
What am I doing wrong?
Thanks,
If you're trying to install the full factory image, you have to unzip the file and navigate to the corresponding directory, then either use fastboot commands to flash the desired partitions to your device individually, or execute the flashall script in the file to flash all partitions.
There's a guide here http://forum.xda-developers.com/showthread.php?t=2382618 .
Edit: You will need to update specific file names/paths accordingly vs. what the guide shows of course.
PrizmaticSmoke said:
If you're trying to install the full factory image, you have to unzip the file and navigate to the corresponding directory, then either use fastboot commands to flash the desired partitions to your device individually, or execute the flashall script in the file to flash all partitions.
There's a guide here http://forum.xda-developers.com/showthread.php?t=2382618 .
Edit: You will need to update specific file names/paths accordingly vs. what the guide shows of course.
Click to expand...
Click to collapse
Okay, thanks! Got it. Will this method wipe my data?
seanvree said:
Okay, thanks! Got it. Will this method wipe my data?
Click to expand...
Click to collapse
Using the flashall script definintely will.
If you run the commands individually, you shouldn't lose your data if you don't run the "erase userdata" command (i believe, but it's been awhile since i have done this myself). But i would highly recommend backing up everything you care about off of the device before performing this process.
I've noticed that many in this forum for the Honor 7x / Mate SE want to try a few ROMS, and then eventually go back to stock - Some just want to go back to stock. I had my own issues and thankfully there were others to help along the way. This method does not use fastboot to flash partitions, it uses TWRP, so the assumption is you have a working TWRP. Also I am not responsible for any bricks, I am just explaining what I did to get back to stock (And based on all the issues people are having, I'm staying there)
If you've tried a Treble ROM or others, the route I took to get back to stock was as follows:
1.) Download your firmware from Firmware finder or the Pro-TeamMT website:
http://pro-teammt.ru/firmware-database/?firmware_model=bnd-l34&firmware_page=0
In this example, mine is the Mate SE..
You should have downloaded 3 files. The important one we want right now is the Update.zip - Extract this file. You should see UPDATE.APP within this folder.
2.) Download the Huawei extractor software by worstenbrood:
https://forum.xda-developers.com/showthread.php?t=2433454
3.) Use this software to extract the files from the Update.App - You may need to disable the Checksum checks under "Settings". When you select the UPDATE.APP file, you should get a list of the files that are compiled or compressed into the app. The main 4 files you want are Ramdisk, Vendor, System, and if you'd like the Stock recovery (Recovey_Ramdisk). Copy these files to your SD card.
4.) Assuming you still have the functioning TWRP, reboot into TWRP and wipe everything but the SD card.
5.) Flash the images to the appropriate partition, Ramdisk = Ramdisk, Vendor = Vendor Image, and System = System Image - Ensure you're flashing the image partitions. Ramdisk is necessary if you've ever rooted or used Magisk.
At this point you should be able to reboot and get back into stock...But you'll notice Themes do not work properly..That's because you've wiped / formatted data at some point in TWRP, and now the Data/hw_int has been wiped. You can fix this by flashing the update on top of itself by the instructions in this thread (Thanks to mrmazak):
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
See the "Flash update while on Oreo"...This has worked twice now to get me back my themes after wiping /data.
I counted on my TWRP backup to get me back to stock after trying a Treble ROM, and I ended up bricked. So hopefully this helps someone!
PS, if anyone has more to add this this, the more help the better.
Wait, wouldn't the recovery be the file "RECOVERY_RAMDIS.img"
???
crayonicle said:
Wait, wouldn't the recovery be the file "RECOVERY_RAMDIS.img"
???
Click to expand...
Click to collapse
You are correct...That is the name of the actual image in the UPDATE.APP, but I was basing the name off of the actual partition.
Corrections, please add to original post
smokinjoe2122 said:
You are correct...That is the name of the actual image in the UPDATE.APP, but I was basing the name off of the actual partition.
Click to expand...
Click to collapse
Just learned today that you can't flash Vendor through Fastboot, so you have to copy all the necessary files onto a SD card or USD OTG.
The files needed are: "SYSTEM.img" "RECOVERY_RAMDIS.img" and "VENDOR.img"
Flash them through twrp in the required partitions, the partition names are literally the file names.
TWRP: https://forum.xda-developers.com/devdb/project/dl/?id=28883
crayonicle said:
Just learned today that you can't flash Vendor through Fastboot, so you have to copy all the necessary files onto a SD card or USD OTG.
The files needed are: "SYSTEM.img" "RECOVERY_RAMDIS.img" and "VENDOR.img"
Flash them through twrp in the required partitions, the partition names are literally the file names.
TWRP: https://forum.xda-developers.com/devdb/project/dl/?id=28883
Click to expand...
Click to collapse
System image can fail too...that's why I said to flash everything in TWRP...Plus, flashing the update on-top of itself will not only give you theming back, but stock recovery.
crayonicle said:
Just learned today that you can't flash Vendor through Fastboot, so you have to copy all the necessary files onto a SD card or USD OTG.
The files needed are: "SYSTEM.img" "RECOVERY_RAMDIS.img" and "VENDOR.img"
Flash them through twrp in the required partitions, the partition names are literally the file names.
TWRP: https://forum.xda-developers.com/devdb/project/dl/?id=28883
Click to expand...
Click to collapse
Is this working ? Did you try ? I'm on RR ROM and couldn't get adb recognize my device. This is my only hope to return to stock as of now.
Adithya Krishnakumar said:
Is this working ? Did you try ? I'm on RR ROM and couldn't get adb recognize my device. This is my only hope to return to stock as of now.
Click to expand...
Click to collapse
Yes, I tried it. It works flawlessly.
How can I get themes to work? I don't understand the original post, it makes no sense when explaining how to get themes to work properly. I do not know what to do with the link provided in the original post.
crayonicle said:
How can I get themes to work? I don't understand the original post, it makes no sense when explaining how to get themes to work properly. I do not know what to do with the link provided in the original post.
Click to expand...
Click to collapse
What part are you stuck on?
Essentially mrmazak created a flashable file that will take the 3 firmware files you download and flash them on top of your current firmware. This is helpful for doing an update or just reloading the firmware completely (Which is what you're trying to do)...
I'd follow the exact instructions that he's put out on that thread, but the 10,000 ft overview:
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
1.) Download files from link for your device
2.) Create a correctly named folder on your SD card, along with those files properly named in that folder (Ensure these files are named properly also.)
3.) Ensure you have the stock recovery on the SD card also.
4.) Copy the "xxx_Update.zip" he created onto your SD
5.) Flash the "xxx_Update.zip"...It will will flash the stock recovery, then boot into update mode and update with the 3 files you downloaded and put into that folder. This will basically "reflash" the firmware and give you back themes.
I would go step by step on his action list and follow them to a "T". I've verified it works perfectly. He also has a "Basic-Instructions" write up in the zip also.
My device build number was BND-L21C185, I bricked my device once but I managed to get it back. Since then I have strange build number which is system 8.0.0.046(063f). Does this method fix it?
This info helped me bring my phone back to life,thank you sir for the step by step instructions.
Found a way to get back to stock without all this hassle lol
So I thought this was the only way to get back to stock... turns out there is a much easier way
This method also enables themes, I checked myself.
https://forum.xda-developers.com/honor-7x/how-to/getting-to-stock-emui-super-easily-t3804722
Is it possible to flash all of the partitions from fastboot?
I have the BND-L34 and I am unsure as to what happened.
I have been running the RROS surdu_petru posted for about 3 weeks now and it was running fine.
2 days ago I grab my phone and it was booted into error mode. Now when I try to boot into twrp I get an error code for my recovery. When I try to boot into the system it throws a different error code for boot image.
I have a twrp backup stored on an sd card, and all 3 OTA's I saved back during the June update. I have the Pro-TeamMT app on my pc and have found/extracted every file for the brick method only get the same errors, 1 right after the other.
I am no noob, (although I am not a Senior Member with a giant banner either ) but I have been rooting android devices going on 8 years now, and have never completely bricked any of them.
My last 2 phones were Oneplus 1 and Oneplus 3, so I am familiar with flashing all the partitions using fastboot. But with those phones there were about 9 different individual flashes that needed to be done in a particular order.
Any help or advice would be greatly appreciated.
I upgraded my phone to android EMUI8 and tried to install the RR 8.1 ROM but my device wouldn't boot up. Then I tried to reflash the stock system.img but it won't let me. I don't have TWRP on my phone but I can acces fastboot. Does anyone know what to do? Thanks in advance :^l
jetzecazemier said:
I upgraded my phone to android EMUI8 and tried to install the RR 8.1 ROM but my device wouldn't boot up. Then I tried to reflash the stock system.img but it won't let me. I don't have TWRP on my phone but I can acces fastboot. Does anyone know what to do? Thanks in advance :^l
Click to expand...
Click to collapse
What is it you mean , it won't let you. Does it give a message. Failed?
Are you at frp locked?
mrmazak said:
What is it you mean , it won't let you. Does it give a message. Failed?
Are you at frp locked?
Click to expand...
Click to collapse
Well when I try to flash the stock 8.0 system.img it gives me a "Invalid sparse file format at header magi" and when I try to flash TWRP it gives me a "FAILED (remote: partition length get error) I am frp unlocked by the way.
jetzecazemier said:
Well when I try to flash the stock 8.0 system.img it gives me a "Invalid sparse file format at header magi" and when I try to flash TWRP it gives me a "FAILED (remote: partition length get error)
Click to expand...
Click to collapse
Ok, that does not seem too bad, yet.
I suppose you are using system.img downloaded from web.
That image has given many that same error.
Best to use your system.img.
And the error flashing twrp, is common when using the nougat command or nougat recovery on Oreo.
Solutions.
Find your firmware on pro-teammt
http://pro-teammt.ru/firmware-database/?firmware_model=Bnd-&firmware_page=0
Then download update.zip
Extract files.
Get hauwei update extractor.
https://www.google.com/url?sa=t&sou...FjAAegQIARAB&usg=AOvVaw0xkKEyI85nY9x4Fjr1AWJl
Extract the system.img
Then fastboot flash it.
Recovery:
Oreo command== fastboot flash recovery_ramdisk twrp_ramdisk
Twrp name depends on version used. I use build 4 from here
https://forum.xda-developers.com/p10-lite/development/recovery-twrp-3-2-1-0-t3783447
mrmazak said:
Ok, that does not seem too bad, yet.
I suppose you are using system.img downloaded from web.
That image has given many that same error.
Best to use your system.img.
And the error flashing twrp, is common when using the nougat command or nougat recovery on Oreo.
Solutions.
Find your firmware on pro-teammt
http://pro-teammt.ru/firmware-database/?firmware_model=Bnd-&firmware_page=0
Then download update.zip
Extract files.
Get hauwei update extractor.
https://www.google.com/url?sa=t&sou...FjAAegQIARAB&usg=AOvVaw0xkKEyI85nY9x4Fjr1AWJl
Extract the system.img
Then fastboot flash it.
Recovery:
Oreo command== fastboot flash recovery_ramdisk twrp_ramdisk
Twrp name depends on version used. I use build 4 from here
https://forum.xda-developers.com/p10-lite/development/recovery-twrp-3-2-1-0-t3783447
Click to expand...
Click to collapse
Okay so I've downloaded the latest firmware for my model but when I try to extract the update.app inside of the update.zip file the huawei zip extractor gives me "RECOVERY_RAMDIS.img: Invalid header crc - Expected: 15200 Got: 44917
jetzecazemier said:
Okay so I've downloaded the latest firmware for my model but when I try to extract the update.app inside of the update.zip file the huawei zip extractor gives me "RECOVERY_RAMDIS.img: Invalid header crc - Expected: 15200 Got: 44917
Click to expand...
Click to collapse
yes there is a bug either in the extractor or the update files. they all do it. Go to the settings tab and take check mark off verify header.
mrmazak said:
yes there is a bug either in the extractor or the update files. they all do it. Go to the settings tab and take check mark off verify header.
Click to expand...
Click to collapse
I flashed the system.img but now the phone bootloops. It could be possible I got the wrong system.img because I don't know exactly what firmware my phone was on before I messed up. I only know it was EMUI8. Is there a way to completely reflash everything?
jetzecazemier said:
I flashed the system.img but now the phone bootloops. It could be possible I got the wrong system.img because I don't know exactly what firmware my phone was on before I messed up. I only know it was EMUI8. Is there a way to completely reflash everything?
Click to expand...
Click to collapse
Yes. I have guide thread here for that.
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
But also wipe in factory reset from stock recovery may solve the bootloop.
mrmazak said:
Yes. I have guide thread here for that.
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
But also wipe in factory reset from stock recovery may solve the bootloop.
Click to expand...
Click to collapse
Alright, I'll try that before I have a look at that thread
mrmazak said:
Yes. I have guide thread here for that.
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
But also wipe in factory reset from stock recovery may solve the bootloop.
Click to expand...
Click to collapse
I tried rebooting to stock recovery in order to factory reset but it only shows me the update, power off and reboot options so no factory reset possibility. I read through the entire thread you linked here but I'm very confused as to what to do with the full OTA file. I'm on a broken EMUI8 that bootloops and I'd like to clean flash EMUI8 again so I can flash an AOSP Oreo rom after that. What do I do?
jetzecazemier said:
I tried rebooting to stock recovery in order to factory reset but it only shows me the update, power off and reboot options so no factory reset possibility. I read through the entire thread you linked here but I'm very confused as to what to do with the full OTA file. I'm on a broken EMUI8 that bootloops and I'd like to clean flash EMUI8 again so I can flash an AOSP Oreo rom after that. What do I do?
Click to expand...
Click to collapse
Just made updates to guide last night. I think it is worded simple now.
Download my update "package" from step E
Extract it to a folder on your PC.
You are on emui8, so copy the HWOTA folder from the extracted zip to your sdcard
Also put hwota-update-7-8-auto.zip on sdcard.
Put the three (3) update files from pro-teammt.ru in the HWOTA8 folder on your sdcard
Put card into phone
Boot into twrp
Select install
Choose sdcard as source
Install hwota-update-7-8-auto.zip
mrmazak said:
Just made updates to guide last night. I think it is worded simple now.
Download my update "package" from step E
Extract it to a folder on your PC.
You are on emui8, so copy the HWOTA folder from the extracted zip to your sdcard
Also put hwota-update-7-8-auto.zip on sdcard.
Put the three (3) update files from pro-teammt.ru in the HWOTA8 folder on your sdcard
Put card into phone
Boot into twrp
Select install
Choose sdcard as source
Install hwota-update-7-8-auto.zip
Click to expand...
Click to collapse
So far so good but the FULLOTA update file I got from that website only has one file (update.zip) Do I need to extract that? And if so, what 3 files do I put on my sdcard?
jetzecazemier said:
So far so good but the FULLOTA update file I got from that website only has one file (update.zip) Do I need to extract that? And if so, what 3 files do I put on my sdcard?
Click to expand...
Click to collapse
No do not extract it.
On that site, next to link for update file, is "file list"
Click this. It gives links for all three files.
Put those three zip files into hwota folder
mrmazak said:
No do not extract it.
On that site, next to link for update file, is "file list"
Click this. It gives links for all three files.
Put those three zip files into hwota folder
Click to expand...
Click to collapse
Alright, I got it! Now I need to flash TWRP but the executable to install TWRP says my adb drivers are outdated. I have the minimal fastboot and adb installation from XDA.
jetzecazemier said:
Alright, I got it! Now I need to flash TWRP but the executable to install TWRP says my adb drivers are outdated. I have the minimal fastboot and adb installation from XDA.
Click to expand...
Click to collapse
That should be fine.
Usually means you have other adb also , probably from other tool.
If you have twrp , not need to use the terp recovery installer
mrmazak said:
That should be fine.
Usually means you have other adb also , probably from other tool.
If you have twrp , not need to use the terp recovery installer
Click to expand...
Click to collapse
Well the problem is I don't have TWRP and none of the versions i've tried to install work. The installer doesn't work either, it says closing adb daemon and stays on that.
jetzecazemier said:
Well the problem is I don't have TWRP and none of the versions i've tried to install work. The installer doesn't work either, it says closing adb daemon and stays on that.
Click to expand...
Click to collapse
Each step of the tool I put pause.
So it stopped on command and not closed.
Press spacebar
mrmazak said:
Each step of the tool I put pause.
So it stopped on command and not closed.
Press spacebar
Click to expand...
Click to collapse
Dude, you're the man! I got my device up and running again. I'll probably stay on EMUI8 since it's more stable than the current AOSP rom. I wanna root it tho so can I just use the lazy recovery tool to install twrp and simply install magisk?
jetzecazemier said:
Dude, you're the man! I got my device up and running again. I'll probably stay on EMUI8 since it's more stable than the current AOSP rom. I wanna root it tho so can I just use the lazy recovery tool to install twrp and simply install magisk?
Click to expand...
Click to collapse
Yes.
The lazy tool has recovery with encryption working
I got it working on EMUI8 but I decided to flash the aosp rom cuz i prefer stock android. Can't seem to get twrp to install tho. I keep getting "1 was unexpected at this time"
Is there any way to root a gsi? All the tutorials seem to make you flash stock everything. Any way to get magisk running on a android 12 gsi? (Descendant os)
Airpewdiepie said:
Is there any way to root a gsi? All the tutorials seem to make you flash stock everything. Any way to get magisk running on a android 12 gsi? (Descendant os)
Click to expand...
Click to collapse
You can get the boot.img from the stock firmware, lemme explain it to you:
1. Get the firmware.
2. Open the file beginning with AP
3. Extract boot.img.lz4 with WinRAR
4. Get lz4, drag the file into the lz4.exe
5. There is a new file named "boot.img"
6. install 7Zip
7. right click > 7Zip > Add to archive
8. make sure its .tar
9. Enable debugging mode and drag drop the boot.tar into any folder in your phone
10. Patch it with magisk
11. Drag it back to your PC.
12. Open ODIN, then put the magisk_patched... into the AP slot.
13. Press "Start" (i think)
Franzyy said:
You can get the boot.img from the stock firmware, lemme explain it to you:
1. Get the firmware.
2. Open the file beginning with AP
3. Extract boot.img.lz4 with WinRAR
4. Get lz4, drag the file into the lz4.exe
5. There is a new file named "boot.img"
6. install 7Zip
7. right click > 7Zip > Add to archive
8. make sure its .tar
9. Enable debugging mode and drag drop the boot.tar into any folder in your phone
10. Patch it with magisk
11. Drag it back to your PC.
12. Open ODIN, then put the magisk_patched... into the AP slot.
13. Press "Start" (i think)
Click to expand...
Click to collapse
It wont replace my rom? also, can i do it without a factory reset?
Airpewdiepie said:
It wont replace my rom? also, can i do it without a factory reset?
Click to expand...
Click to collapse
1. It wont replace your rom
2. You sadly have to do a factory reset, then reflash the boot.tar again
Never root at boot, there are many people who lost IMEI by rooting at boot.
Melky777 said:
Never root at boot, there are many people who lost IMEI by rooting at boot.
Click to expand...
Click to collapse
You have to delete the imei folder to make imei working again
Melky777 said:
Never root at boot, there are many people who lost IMEI by rooting at boot.
Click to expand...
Click to collapse
A fix has been found for it.
Franzyy said:
1. It wont replace your rom
2. You sadly have to do a factory reset, then reflash the boot.tar again
Click to expand...
Click to collapse
Any reason for the factory reset?
i was able to root my phone running crdroid 8.8. all i did was first download the firmware. after that i copied over the AP file of the firmware to my phone and then selected that in magisk to patch it. after it patched it i copied it back over to my pc and flashed the ap file along with bl, cp and CSC file. it reset and it worked fine! now any GSI i try and i install magisk v22.0 apk it works just fine.