Touchscreen failed in TWRP(3.2.3.0) after I manually upgraded to Nov update by adb sideload (about 1.0GB OTA package). What should I do to get touchscreen back?
There is this thread addressing the problem.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Related
Hi I have an unrooted 6p I have never messed with the software but I am on the dp program I usually get the updates within hours of it being announced. But for some reason I have not gotten the 7.1.1 stable with December security patch which is odd but anyway I tried side loading the OTA and it gets to 40% and then says installation aborted. I have the and setup right and all that I can reboot into bootloader does anyone know why it would be doing this? When I was at work today I thought maybe if I disable the allow seamless update option in developer options maybe that will allow it. Any thoughts?
Ok I feel like an idiot. I tried again when I got home from work and it seems that the file I am trying to flash is from November 1 which I already have installed. It is the last one one the Google OTA page. So is it not out yet for the 6p? I'm confused can anyone help me out please
I believe you'll need to unenroll from the beta program first before attempting to sideload the OTA image. The latest OTA image is NMF26F, which includes the December security patch. And make sure you boot into recovery, and not the bootloader to install the update using adb.
redduc900 said:
I believe you'll need to unenroll from the beta program first before attempting to sideload the OTA image. The latest OTA image is NMF26F, which includes the December security patch. And make sure you boot into recovery, and not the bootloader to install the update using adb.
Click to expand...
Click to collapse
Ok if I unenrolled from the dp program I should just get the OTA then I won't have to side load is what I'm guessing. It seems that Google had the stable build done before they released the last dp because the file says November 1 build and I got mine on November 5 that is why it won't allow it.
Hi all,
Recently we find a way to go back to 8.1.0 from Android P DP1 with Verizon locked bootloader on the Android Beta Program community. Thanks Ziauddin Sameer for try it.
All you need is:
1- Google Pixel or Pixel XL with locked bootloader (Don't know if it work on Pixel 2 or Pixel 2 XL but it may work)
2- Android P DP1 installed on your device
3- Full April 2018 OTA link here https://developers.google.com/android/ota
4- ADB/FASTBOOT drivers link here https://forum.xda-developers.com/showthread.php?t=2588979
Now that you have all that and the drivers intalled let's do this:
You'll lose all your data after this, so backup before continue
1- Install the drivers
2- Put the Full April OTA zip on the adb folder located on C:/
3- Turn you Pixel off and go to recovery mode
4- Select "Apply update from ADB"
5- Plug in your Pixel via USB to the computer
6- Inside the adb folder Hold "Shift" and right click, select Open Powershell/CMD here"
7- Inside the Powershell/CMD type
Code:
abd sideload filename.zip
8- When its done your Pixel will try to boot and since it has the Android P data (cause sideloads dont erase data) it would said that the data is corrupted and it will suggest you to factory reset.
9- Select factory resert and it will boot on Android 8.1.0
Psdt: Sorry for my bad english.
You can confirm it in here https://plus.google.com/101606265756083327418/posts/cshGmedy5ZX
I can confirm that this does work! THANKS! I am happily back to 8.1! Don't get me wrong "P" is awesome and stable, but having the WiFi Calling feature broke in "P" is a deal breaker for me. I will just have to wait until DP2 to see if it gets sorted out.
EDIT do not use the May 2018 file, use April, this one is transferring now, below error is because of MAY file.
I tried this after going to Android P beta. It did not work for me.
I followed the steps and when I ran adb sideload xxx.zip I received this...
verifying update package
E:footer is wrong
update package verification took 0.2 s (result 1)
E:Signature verification failed
E:error: 21
Installation aborted.
Any help would be greatly appreciated, basically I opted into beta and then opted out but never received the image to go back and apps are not working for me...gear s3, libby and some others.
whreed said:
EDIT do not use the May 2018 file, use April, this one is transferring now, below error is because of MAY file.
.
Click to expand...
Click to collapse
So for downgrading from Android P DP2 we need to use 8.1 April OTA, right?
I ultimately did get the push of the image to my device to pass but the image didn't work for me... When I wiped and rebooted and after initial setup up I received the message to go back to Oreo from Google....I was previously in the beta but opted out.
Does not work for me even for April OTA. It says package being updated is older than the currently installed. I'm on Android P May patch.
Is it possible that I can downgrade when the June OTA is out because of the timestamp?
caloysilva said:
Does not work for me even for April OTA. It says package being updated is older than the currently installed. I'm on Android P May patch.
Is it possible that I can downgrade when the June OTA is out because of the timestamp?
Click to expand...
Click to collapse
Just opt out of the beta and an OTA will appear to go back to Oreo
It doesn't seem this method will work to downgrade the OTA 9.0 update? My phone has been completely unusable since the 9.0 update applied (the radio modem has worked all of about 2 days since the update). I've tried everything and have been on the phone with google many times over this. When I try to place a call, I'll either get the message "Radio off" or " Cannot place calls in Airplane mode" errors. Rebooting, cycling data and airplane modes have no effect, resetting networking does nothing, even factory resetting does nothing. My phone is completely useless without mobile data. I'll never purchase anything from Verizon again, with their opting to lock the bootloader on their phones!
I was also curious if this method would work for an OTA 9.0 device ?
Last ota update is from Nov. 2017 Update keeps saying phone is up to date. Google is no help. They have told me that they don't know why my phone won't update. I am on Google fi. Been told by others that I just need to sideload the latest update and it might kickstart the phone into accepting ota updates. Never done this so am concerned about mucking up my stock phone.
Anyone have any suggestions?
Was the phone in the Beta program? If so, that ended for the 6P as it isn't part of Android P beta and you won't get any further updates, even by coming out of the beta program.
Sideloading the OTA should fix it and you can do it without losing any app and personal data.
Link with OTA's and instructions from Google is at https://developers.google.com/android/ota
Nope, no beta program.
Still trying to decide if it is worth the risk for me to try the sideload......
Oh boy, Huawei trying to screw us all over. Magisk apparently is no longer working, so no root for once a new OTA installs for Huawei devices.
https://forum.xda-developers.com/showpost.php?p=77415750&postcount=6555
https://forum.xda-developers.com/showpost.php?p=77418253&postcount=6557
New issue on Huawei Phones - Mate 10, Mate 10 Pro, P9 - Huawei roll out a new OTA called: "patch01". In the changelog is some fix mentioned (example: mms...) but the main patch is to disable the possibility of Root.
That means: if someone flash Magisk with TWRP, or flash patched_boot.img to ramdisk and reboot the phone, Phone get stuck on the splash screen: "Your device cannot be trusted..."
Only flashing back the original Huawei ramdisk.img helps to boot again to system. But no Root with Magisk is anymore possible.
Downgrade helps (if available, because for some Phones like Mate 10 it is dangerous to downgrade, if the Downgrade Firmware has another Xloader.img... but this is another story)
→ So, for Users of Huawei Phones it is better not to install OTA with Patch01 and disable Systemupdate in /system/app/HwOUC - rename HwOUC.apk to HwOUC.bak
I attach here the patch from Huawei for P9 - may you take a look, thanks
Click to expand...
Click to collapse
I have dm-verity always off (not enabled in Magisk Manager) and I have also avb disabled in /vendor/etc/fstab.ext4.hi.... and fstab.f2fs.hi.... (I have different Huawei devices)
To make the issue clearer here is another summary:
I made a Rebrand Thread for Huawei P9-EVA here: https://forum.xda-developers.com/p9/...9-eva-t3820849
The main reason for this is to allow users to unofficially update their device to Android 8 Oreo. Huawei has rolled out the Oreo OTA update in China, but has no plans to release this update outside of China. Although Oreo runs much better on the devices.
To make this possible, root is an important part, otherwise the mobile network will not work on the rebranded devices. Many users were very happy because they can now also use Oreo Treble Roms by the Open Kirin Team.
Okay → Devices rebranded to EVA-AL10 and updated to the official Oreo Firmware b528. With some modification everything is working fine.
→ Yesterday OTA Patch01 was available. I flashed the unmodified original Huawei ramdisk.img, uninstalled Magisk Manager and flashed the original EMUI Recovery. Then I agreed to the OTA update. The update was succesful installed.
After that I flashed the Magisk patched_ramdisk.img again, but the phone did not boot → it booted only with original b528 ramdisk.img
We were three people who tested it. Me and @dkionline and @zgfg We tried everything that came to our mind. → flashing first original ramdisk and kernel.img and booted to system. Then flashing patched ramdisk.img b528 with Magisk 16, Magisk 16.7 with flag "force encryption" and without "force encryption" (related to - if device is with data encrypted or data decrypted)
Flashing TWRP was not a problem, and together with the original Huawei ramdisk.img phone was able to start to system. To get Root again, we must downgraded to b528 without this Patch.
→ The Patch includes a Fix for mms and Fix for gaming (changes a Line in a local.prop) and it includes also a Kernel patch.
Looking back, we should have tested a little more. What we did not test → making dd with TWRP from ramdisk.img after the OTA Patch and then patch the "dump" ramdisk.img with Magisk. → Maybe that would have worked - we do not know it now and I do not feel like reproducing it again. But perhaps @zgfg can try this in a view days (he did not downgrade yet, because he is outside).
With this last test we could say it for sure, if the Kernel patch includes something to make Huawei Phones unbootable together with Magisk.
And coincidentally I read then in the Mate 10 forum that there also a user (with ALP-L29c636) got an OTA with a Patch01 and similar problem " I got a patch notification so I download it, rebooted and the patch installed (phone booted and I checked version and it was patch1). Cool. So then I rooted using magisk and phone was soft bricked..." : https://forum.xda-developers.com/sho...&postcount=256
My first thought was simple, Huawei is now trying to prevent root with this patch01 and much confirms this theory....
→ Bootloader Unlock Site closed
→ TrustSpace is a new App in system which definitely check and disable Root (we had this app disabled and two of us has it deleted in system)
→ Downgrade with unofficial methods become danger for hardbrick, because of two different Xloader.img in the Firmware (Mate 10)
Click to expand...
Click to collapse
Big thanks to @Tecalote for bringing this to my attention.
Not sure if this will hit the Honor 7x, it probably will. I am prepared for the worst, really hate it when Huawei does this.
Its looking like Huawei just shot themselves in the foot on this if its infact the case, there is nothing worse then developers getting middle fingered and scorned. If you think a Developer using a fork (github joke) is dangerous just wait till they nuke that commit/submit button! This is not going to bold well for honor/huawei
As i have already stated if this turns out to be Honor/Huawei out right middle fingering devs and users choice I will be looking for another phone pronto.
Click to expand...
Click to collapse
Holy shiet
Yes, i can confirm this, please do not flash that Patch01, it will make your device stuck on boot message after you flash magisk.
I'm on Huawei Nova 2s.
How to root in Patch01 update : https://forum.xda-developers.com/showpost.php?p=77560239&postcount=27389
heindrix said:
How to root in Patch01 update : https://forum.xda-developers.com/showpost.php?p=77560239&postcount=27389
Click to expand...
Click to collapse
How can you tell if you've gotten the Patch01 update?
My phone is currently BND-L24 8.0.0.341(C567), with a July 1 2018 Android security patch.
For the link you posted im assuming id have to use "B) If the TWRP for your device has not access to encrypted /data then you can do the following:"
The site here http://pro-teammt.ru/firmware-database/?firmware_model= that has firmware doesn't seem to show 8.0.0.341? Should I use BND-L24AC567B330 (8.0.0.330) because it seems to be an update from May, and when I google my build number Huawei tweeted that it was a May security update? Or will using that brick my phone? Of the availible BND-L24 firmwares, which one should I use?
Also do I already need TWRP installed? can I do that on my unrooted device?
battleforce said:
How can you tell if you've gotten the Patch01 update?
My phone is currently BND-L24 8.0.0.341(C567), with a July 1 2018 Android security patch.
For the link you posted im assuming id have to use "B) If the TWRP for your device has not access to encrypted /data then you can do the following:"
The site here http://pro-teammt.ru/firmware-database/?firmware_model= that has firmware doesn't seem to show 8.0.0.341? Should I use BND-L24AC567B330 (8.0.0.330) because it seems to be an update from May, and when I google my build number Huawei tweeted that it was a May security update? Or will using that brick my phone? Of the availible BND-L24 firmwares, which one should I use?
Also do I already need TWRP installed? can I do that on my unrooted device?
Click to expand...
Click to collapse
You can see it in System->About.
See at Build Number section, it will be printed XXX-XXXX X.X.X.XXX(XXXPatch01).
You can use Huawei Firmware Finder : https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
Go to Common Base menu, and set (click gear button) this value (G:2649 g:1699), that value is identifier for Honor 7x.
And type L24 in the search box.
After that, click on search button (magnifier glass button), you'll see all available updates for Honor 7x.
And there you go, all of firmware lists for Honor 7x L24.
I made some screenshot for you.
Enjoy.
hi guys
my mia1 was on april patch and rooted.when may update came i uninstalled magisk and unrooted but phone did not update many times with(installation problem )message.
i flashed original mi image 10.4. i.e.january version and wiped phone
but the phone refused to ota update .it only sees may update (385 mb) not 70 mb and download but the same message installation problem.if somebody help me what is wrong and why phone not see feb.,march,april updates and what can be done thanks in advance
Well, you have to try again. Me too passed for that but on the January patch. So I tried once and it works. Here on may update, cheers.
Thaanks for the reply i flashed twrp stock rom april patch and will try till it can update