Hi all,
hoping someone can help me out. I flashed the Lineage rom and i got it working ok however i missed google pay so i decided to return to stock.
i tried placing the update.APP in the dload folder and running the force update procedure but it fails at 5% with just an update failed message. I have tried using the erecovery to download recovery and rom but that says it failed to get the package information, i have tried flashing the images from the update.app using fastboot but theres not really any decent info on which bits i need to flash to get it fully back to stock (and relocked)
If i try fastboot relock
Code:
i get error, root is risk
EDIT: fixed that if anyone needs help
djmills.uk said:
Hi all,
hoping someone can help me out. I flashed the Lineage rom and i got it working ok however i missed google pay so i decided to return to stock.
i tried placing the update.APP in the dload folder and running the force update procedure but it fails at 5% with just an update failed message. I have tried using the erecovery to download recovery and rom but that says it failed to get the package information, i have tried flashing the images from the update.app using fastboot but theres not really any decent info on which bits i need to flash to get it fully back to stock (and relocked)
If i try fastboot relock
Code:
i get error, root is risk
EDIT: fixed that if anyone needs help[/QUOTE]
use this
https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
and follow the guide for flash update.
This is how i got back from lineage to stock on mate 10 pro. use the correct file from http://pro-teammt.ru.
Click to expand...
Click to collapse
esnar said:
use this
https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
and follow the guide for flash update.
This is how i got back from lineage to stock on mate 10 pro. use the correct file from http://pro-teammt.ru.
Click to expand...
Click to collapse
Thanks. I will try that. I fortunately the exact version I had installed is not on the site hopefully using the latest version for the same phone will work.
I will let you know thanks.
esnar said:
use this
https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
and follow the guide for flash update.
This is how i got back from lineage to stock on mate 10 pro. use the correct file from http://pro-teammt.ru.
Click to expand...
Click to collapse
OK. Tried doing the parts about the public zip and hw zip and they are not found on the site so I'm hoping that doesn't matter on this phone. Did you have the same result?
EDIT: Nevermind, i was being an idiot, downloading the files now
All working as new now, but newer firmware. Thank you so much for your help!
Back to stock
djmills.uk said:
Hi all,
hoping someone can help me out. I flashed the Lineage rom and i got it working ok however i missed google pay so i decided to return to stock.
i tried placing the update.APP in the dload folder and running the force update procedure but it fails at 5% with just an update failed message. I have tried using the erecovery to download recovery and rom but that says it failed to get the package information, i have tried flashing the images from the update.app using fastboot but theres not really any decent info on which bits i need to flash to get it fully back to stock (and relocked)
If i try fastboot relock
Code:
i get error, root is risk
EDIT: fixed that if anyone needs help[/QUOTE]
Hi
Could you tell me how you removed the root, I am having the same problem on my Mate 10 Lite, I want to return to stock, but it eludes me all the time because of root. I have used what should be non-rooted backups, but they say root. The only backup that worked ended up turning my phone into another unit so no luck there either. Would love to hear how you did it?
Click to expand...
Click to collapse
Hi i am trying to flash stock on my mate 10 pro, bla l29 c432 131. could u help?
Trying to flash bla l29 c432 137.
Have full ota and data and hw.
How did u manage to do it?
And relocked bootloader?
Tried uppdat.App on otg usb device, it finds the usb but not the upgrade
Update. Zip 2gb extract to dload and then move that "dload" folder?
Extract zip to usb root directory?
Thx
djmills.uk said:
Hi all,
hoping someone can help me out. I flashed the Lineage rom and i got it working ok however i missed google pay so i decided to return to stock.
i tried placing the update.APP in the dload folder and running the force update procedure but it fails at 5% with just an update failed message. I have tried using the erecovery to download recovery and rom but that says it failed to get the package information, i have tried flashing the images from the update.app using fastboot but theres not really any decent info on which bits i need to flash to get it fully back to stock (and relocked)
If i try fastboot relock
Code:
i get error, root is risk
EDIT: fixed that if anyone needs help[/QUOTE]
hi, i tried to follow the thread, but its already edited, now my mate 10 pro is still in customized rom. do you still have the instruction? please help
Click to expand...
Click to collapse
Related
Hello Everyone,
I badly need help on my Huawei Honor U8860 phone. I have recently updated it from 2.3.6 to 4.03 over WIFI and the update went smoothly. So now here is what my phone have:
Kernel Version: 3.0.8-perf-00059-g3a757a2 [email protected] #1
Build Number: U8860IV100R001C00B923SP01
I have not rooted the phone at this time. It was working fine until 2 days ago when I started getting messages on the screen like:
"Unfortunately, 2D Home has stopped"
"Unfortunately, Google Play has stopped"
"Unfortunately, Contacts has stopped"
"Unfortunately, Settings has stopped"
"Unfortunately, Google Play Music has stopped"
"Unfortunately, Browser has stopped"
And so on, and so forth. It seems that all apps and processes have stopped when I try to use them so I literally can't use the phone. I went through several threads here just trying to restore my phone back to a
working state. I tried to do the following in order but without success:
1.) Factory data reset / erase everything - the phone boots to the recovery menu then it formats the /Data, /Cache and /HWUserData then it reboots. After reboot, the phone is back to where it was before the factory data reset with everything in it including downloaded apps.
2.) Manually uninstalled all downloaded apps. Removed screen lock (just to see if phone behavior changes). Then rebooted the phone but after reboot, all the apps are still installed and the screen lock is back as well.
3.) I tried to Force Update with the following official ROMs: B886, B919 and B923 but I always get the message "Update failed" during the update process.
4.) I downloaded the file "recovery-u8860-en.img" so I can replace the "recovery.img" file . Rebooted the phone w/ the pink screen and connected it to my PC but there is no USB mass storage device mounted.
5.) Finally, I tried to root the phone. I enabled USB debugging. I installed the ADB drivers then I downloaded the U8860 root tools and rootexplorer.apk. When I ran the "root-me.cmd", it tried to copy some files to the phone but it failed. The error was "read-only file system".
So it seems that the problem is because of the "read-only filesystem". I does not permit/allow any changes made to the phone. Can you help me restore my phone?
Please.. Can somebody help me on this?
Thanks, clint2rose
clint2rose said:
Please.. Can somebody help me on this?
Thanks, clint2rose
Click to expand...
Click to collapse
I still did not find any solution for my problem. I read from this thread that all ICS versions can be downgraded.
http://forum.xda-developers.com/showthread.php?t=1552038&page=232
Is there a way to downgrade from B923 to B919? I think this will solve the problem I'm facing.
clint2rose said:
I still did not find any solution for my problem. I read from this thread that all ICS versions can be downgraded.
http://forum.xda-developers.com/showthread.php?t=1552038&page=232
Is there a way to downgrade from B923 to B919? I think this will solve the problem I'm facing.
Click to expand...
Click to collapse
try to back-up some of the data form the partitions that are full on your phone and delete them, maybe afterwards the stock-rom-flashing procedure will work again.
kaefert said:
try to back-up some of the data form the partitions that are full on your phone and delete them, maybe afterwards the stock-rom-flashing procedure will work again.
Click to expand...
Click to collapse
thanks for the reply. it did not work. I even formatted the internal SD. Re-run the firmware update but it failed. when i boot the phone, all the contents of the internal SD remains intact. any other suggestion?
I can remember there was some talk of "downgrade patches" to flash before official ROMs if downgrades failed
http://forum.xda-developers.com/showpost.php?p=36819830&postcount=2312
http://forum.xda-developers.com/showpost.php?p=36117718&postcount=2228
http://forum.xda-developers.com/showpost.php?p=35376103&postcount=2104
http://forum.xda-developers.com/showpost.php?p=34105274&postcount=1865
http://forum.xda-developers.com/showthread.php?p=32996711&highlight=patch#post32996711
working download linka (just tested them) -->
https://docs.google.com/file/d/0B4MkDBK_iI-gWEoyaWpEekRXT00/edit
http://www.huaweidevice.com/cn/downloadCenter.do?method=toDownloadFile&flay=software&softid=NDE5Nzg=
kaefert said:
I can remember there was some talk of "downgrade patches" to flash before official ROMs if downgrades failed
http://forum.xda-developers.com/showpost.php?p=36819830&postcount=2312
http://forum.xda-developers.com/showpost.php?p=36117718&postcount=2228
http://forum.xda-developers.com/showpost.php?p=35376103&postcount=2104
http://forum.xda-developers.com/showpost.php?p=34105274&postcount=1865
http://forum.xda-developers.com/showthread.php?p=32996711&highlight=patch#post32996711
working download linka (just tested them) -->
https://docs.google.com/file/d/0B4MkDBK_iI-gWEoyaWpEekRXT00/edit
http://www.huaweidevice.com/cn/downloadCenter.do?method=toDownloadFile&flay=software&softid=NDE5Nzg=
Click to expand...
Click to collapse
I downloaded the files from both links. Can you tell me how to flash my current ROM? Because when I tried to use the file like a regular ROM (I created dload folder then put UPDATE.APP in the folder, then ran firmware update.. the update failed)..
clint2rose said:
I downloaded the files from both links. Can you tell me how to flash my current ROM? Because when I tried to use the file like a regular ROM (I created dload folder then put UPDATE.APP in the folder, then ran firmware update.. the update failed)..
Click to expand...
Click to collapse
what do you mean by flashing your current ROM? Just like any other stock ROM put the dload folder on the sd-card and start the update procedure either from the settings menu or via the boot-key-combination.
Yes the way you discribed is the correct one for flashing those patches, If those patches also don't work, I'm out of ideas, sorry.
kaefert said:
what do you mean by flashing your current ROM? Just like any other stock ROM put the dload folder on the sd-card and start the update procedure either from the settings menu or via the boot-key-combination.
Yes the way you discribed is the correct one for flashing those patches, If those patches also don't work, I'm out of ideas, sorry.
Click to expand...
Click to collapse
Thank you once more for your time. Most of the thread I read regarding these patches often used the phrase" you have to flash the current version of your ROM using the patch"...
And yes I created dload folder, place the UPDATE.APP and put it on the sdcard. I turned off the phone and removed the battery. Then I pressed vol+ vol- and power on/off button. The firmware update went to about 70% installing before displaying update failed.
I guess I will have to bring my phone to a repair center. My only problem is that there is no Huawei service center at my place (I reside here in Saudi Arabia). I got the phone as a free device on a broadband package and the warranty is already expired. I'm a little worried to take the phone to the small mobile repair shops as they might screw up the phone even more. Huawei is not a popular device here unlike iPhone, HTC and Samsung Galaxy.
As I understood that your device is rooted, you should get some custom ROM and try to install it.
okty2k said:
As I understood that your device is rooted, you should get some custom ROM and try to install it.
Click to expand...
Click to collapse
No, my device is not rooted. I tried to root it but I get the message "failed to copy file: Read-only file system".
clint2rose said:
No, my device is not rooted. I tried to root it but I get the message "failed to copy file: Read-only file system".
Click to expand...
Click to collapse
you don't need to be rooted, you only need to have a custom recovery deployed (which you can either do with root permissions, or by using the pink screen method, but some newer stock roms (you said your on 932 or something? last non-locked working is b919) this has been locked and the device will not boot if the kernel or the recovery image has been manipulated.
I think you will have to find some (huawei-certified!) repair-center, small do-it-all phone-shops probably won't be able to take care of this problem for you.. I'm sorry but I don't see any other solution
kaefert said:
you don't need to be rooted, you only need to have a custom recovery deployed (which you can either do with root permissions, or by using the pink screen method, but some newer stock roms (you said your on 932 or something? last non-locked working is b919) this has been locked and the device will not boot if the kernel or the recovery image has been manipulated.
I think you will have to find some (huawei-certified!) repair-center, small do-it-all phone-shops probably won't be able to take care of this problem for you.. I'm sorry but I don't see any other solution
Click to expand...
Click to collapse
Ok. I will try to find a repair-center experienced in Huawei devices. I have one last question if you don't mind. Is it possible to erase everything on the phone? As in completely erase or reformat after which there will not be an operating system on the phone. I read in some threads that this is possible w/ custom recovery but I want to know if it is also possible for phones without the custom recovery. I'm hoping there might be some tool or something..
U8860 not responding
clint2rose said:
Ok. I will try to find a repair-center experienced in Huawei devices. I have one last question if you don't mind. Is it possible to erase everything on the phone? As in completely erase or reformat after which there will not be an operating system on the phone. I read in some threads that this is possible w/ custom recovery but I want to know if it is also possible for phones without the custom recovery. I'm hoping there might be some tool or something..
Click to expand...
Click to collapse
Have you find the solution yet? I have the same problem. Somehow my phone system is "locked". I can't install or uninstall app. Some google apps keep showing not responding. Everything changes i made, keep showing up after the phone rebooted.
This was happen a few days after I upgrade to ICS B932SP01 and rooted my phone (to remove original chinese apps).
Luckily i have friend in huawei indonesia. He gave my u8860 to the technical support. But the result was no good.
They try everything, even install my phone with the original GB and always failed.
The last suggestion is change the phone machine, which is as same as buy a new phone.
I really appreciate is someone can help me here...
Thanks
Hi all!
I've been trying to fix my Asus fonepad K012 (FE170CG) all morning. I derped trying to root it and now I require to flash it back to a stock firmware supplied by Asus. Thus far I have been able to get my hands on the original firmware however I have not been able to find an effective tutorial how to flash it. I know I am posting in the wrong sub forum, however after 6 hours I am pretty much at loss here ... Can anyone help me, please?
I have the same problem!
F4T3 said:
Hi all!
I've been trying to fix my Asus fonepad K012 (FE170CG) all morning. I derped trying to root it and now I require to flash it back to a stock firmware supplied by Asus. Thus far I have been able to get my hands on the original firmware however I have not been able to find an effective tutorial how to flash it. I know I am posting in the wrong sub forum, however after 6 hours I am pretty much at loss here ... Can anyone help me, please?
Click to expand...
Click to collapse
I have the same problem. I tried to flash the stock firmware but the problem remains. My advice is not to flash stock firmware! But if the Demo error pops up very frequently, I can help you flash the stock firmware.
Good luck!
Ali Erfani said:
I have the same problem. I tried to flash the stock firmware but the problem remains. My advice is not to flash stock firmware! But if the Demo error pops up very frequently, I can help you flash the stock firmware.
Good luck!
Click to expand...
Click to collapse
To shed some light on what happened ...
I had updated the fonepad to 4.4 kitkat. Afterwards I used rootzenfone 1.4.6 to root it, it failed and it it started acting like I described above.
For days I looked into what I could do and how to resolve it ... Finally I found the solution to my problem.
1. Downgrade the fonepad 7 K012 back to Jelly Bean 4.3. (You can do this by putting the 4.3 Jelly Bean firmware on the root of your mini SD card, label it k012_sdupdate.zip, switch off the fonepad, boot using the power + volume up combination to get into droidboot, select SD update and let it do it's thing.
2. Once it's completed the fonepad will be downgraded to 4.3, however this isn't the end of it, the asus live demo problem still persists, so you must use rootzenfone 1.4.2 or 1.4.4 to complete the rooting process in order to get rid of it once and for all.
3. For me? It was successful and as I rebooted it got stuck in bootloop. So then I flashed the firmware utilizing ADB's fastboot with the following commands:
fastboot flash fastboot fastboot.img
fastboot flash boot boot.img
fastboot flash splashscreen splashscreen.img
4. Rebooted and my troubles were over. However I really wanted to root it ... So I went total nerdmode on xda and finally found a way to root it.
5. Follow these steps: http://forum.xda-developers.com/showpost.php?p=58782588&postcount=219
6. Enjoy the fat lady's song ...
Q&A for [RECOVERY][ROOT] Ulefone Be Touch Lollipop
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY][ROOT] Ulefone Be Touch Lollipop. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Ulefone Be Touch OTA
Hi,
I have rooted my Be Touch and installed custom recovery as well using this guide
- http://forum.xda-developers.com/android/development/recovery-ulefone-touch-lollipop-t3132204
Now, there is an available OTA from the local reseller and I can't install it due to custom recovery. How do I update my phone now? The error I am getting is System is Damaged which I have attributed to CUstom Recovery upon searching google
I have the same problem to update phone. The downloaded update.zip file over OTA could be found in my SD-card, just 18.89Mb. I've tried to install it using recovery by choosing "install zip -> choose zip from sdcard". But finally I got following error:
...
Verifying current system...
"EMMC:boot:7262208:..." has unexpected contents.
E:Error in update.zip
(Status 7)
Installation aborted.
Hofefully someone could help?
yes same with me, I am trying sideloading with ADB but I do not know about that, unable to make a connection between PC and phone. Maybe someone has stock recovery image so we can perform the OTA update? Anyone can upload their stock recovery?
Reverting back to kitkat.
I tried flashing using spflash on my Ulefone Be touch, it was on lollipop and it did not transition to kitkat. it in fact got semi bricked but i got through that and fixed it. the phone was originally rebranded so it had another skin on top of it (not ulefone). how can i get it back to kitkat? do i have to root it and manually flash it on my phone? or is flashing a downgrade not possible by just regular means?
blank_blank said:
yes same with me, I am trying sideloading with ADB but I do not know about that, unable to make a connection between PC and phone. Maybe someone has stock recovery image so we can perform the OTA update? Anyone can upload their stock recovery?
Click to expand...
Click to collapse
Here is the latest stock rom: http://ulefone.com/download/betouch.html. You will find the boot.img and recovery.img in the zip file. But I'm afraid to brick my phone to have a try. Moreover I don't know whether this root method could still work if I get phone flashed successfully...
are you using a rebrand? I already flashed the recovery of Be Touch, unrooted my phone as well but OTA is still failing, even manual zip install and sideload fails. I guess it is because my phone is a rebrand and thus, uses another recovery as stock. I have used this ROM as my base now and I can confirm that root is still working
blank_blank said:
are you using a rebrand? I already flashed the recovery of Be Touch, unrooted my phone as well but OTA is still failing, even manual zip install and sideload fails. I guess it is because my phone is a rebrand and thus, uses another recovery as stock. I have used this ROM as my base now and I can confirm that root is still working
Click to expand...
Click to collapse
I think my phone is not rebrand, because there is ulefone logo on rear cover. I got it rooted with Build 20150513 ROM.
With the rooted Build 20150513 ROM, I get phone flashed with official Build 20150529 ROM successfully. Afterwards, the root method still works!
yup and i hope we get new build soon with bug fixes! Does your phone get a lot of heat when charging and browsing 3G?
blank_blank said:
yup and i hope we get new build soon with bug fixes! Does your phone get a lot of heat when charging and browsing 3G?
Click to expand...
Click to collapse
I've used several phones and can accept this one. More faster to change the phone more heat will get produced. Surfing or gaming will need more hardware resource and power for display, no wonder that it will get warm too. Maybe a metal cover will get heat better distributed, but then it will be sold in another price...
blank_blank said:
yup and i hope we get new build soon with bug fixes! Does your phone get a lot of heat when charging and browsing 3G?
Click to expand...
Click to collapse
You should try 20150702 ROM. Phone is now not less hot when charging and surfing. I did flash back to official 20150529 ROM and then do the OTA update.
There is a ROM of ulefone be touch 2 on needrom !
Rooted Be Touch 2, Xposed, Loving it.
Hi folks. I used this process to successfuly root my Ulefone Be Touch 2. Instead of the provided recovery.img and boot.img, I used a version of Carliv Recovery and the Be Touch 2 boot.img found through needrom and it worked perfectly.
I was also able to install Xposed Framework by changing the Android version from 5.1 to 5.0 in prop settings (using BuildProp Editor) - which is fine since most say it's fake 5.1 anyway.
Does anyone know whether people have successfully installed custom roms to the Be Touch 2? I find the stock ROM laggy - more so than it should be - but I hesitate to install something like CM or Liquidsmooth without knowing.
Thanks again to the OP!!
Looking for Be Touch 2 Root and Recovery too! Any luck? Thanks in advance!
Download link dosen´t work
Hi, I don´t get the download link to work. I only gets the error code "403 forbidden". Can you please upload the files again, thanks.
[edit] Got it working, was just my antivirus that was blocking it for some reason
It worked!!
Thanks alot man.
I have looking for a root to this device since i got it, and now its rooted
I got this working on win10 (and also working on win8/8.1), but what you have to do is disable "driver signature enforcement". Check this vid if you don´t know how (youtube.com/watch?v=PAxTCvRmlio)
Please make a video
Please Im really new to rooting I have always had iOS and I would really appreciate it if anyone would like to make a video tutorial
Error while trying to root Be Touch 2
Hi,
After following http://forum.xda-developers.com/android/development/recovery-ulefone-touch-lollipop-t3132204 i get to the download part after selecting boot and recovery.
BDROM ERRPR : S_DL_GET_DRAM_SETTING_FAIL (5054)
[EMI] Obtain DRAM Failed!
[HINT] : Please check your load matches to your target which is to be downloaded.
And now the phone won't boot. It does detect when the battery is removed on com15, can I use any other tools to at least boot the phone?
all0gIc said:
Hi,
After following http://forum.xda-developers.com/android/development/recovery-ulefone-touch-lollipop-t3132204 i get to the download part after selecting boot and recovery.
BDROM ERRPR : S_DL_GET_DRAM_SETTING_FAIL (5054)
[EMI] Obtain DRAM Failed!
[HINT] : Please check your load matches to your target which is to be downloaded.
And now the phone won't boot. It does detect when the battery is removed on com15, can I use any other tools to at least boot the phone?
Click to expand...
Click to collapse
Or to download the correct files?
Fingerprint scanner
Does this include functionality for the fingerprint scanner of the ulefone be touch 2 or nah?
I can turn this into a guide if we get the right info.
I have used DC-Unlocker to unlock bootloader and FRP.
I installed v20 Phh Generic System Image via fastboot flash system.
my FRP is locked now and bootloader unlocked, and oem unlock greyed out.
i am investigating a solution and maybe it can help others.
Recovery:
can flash updates if bootloader and frp is unlocked
eRecovery:
i can connect to wifi, but no firmware is found
DLOAD:
updates performed with vol down+up+power
using the update extractor i can get the UPDATE.APP from the official firmware (SHT-W09C432B151 (8.0.0.151) i think for me)
but UPDATE.APP is over fat32 4GB limit. so i cant put it on the SDCard - and im not sure if the recovery can read exFat.
i tried with both but they fail immediately.
placing the files in the internal storage with DLOAD folder seems to send update to 5% then fail.
HWOTA:
seems to be a method used on older devices - not sure if it will work to flash this device.
the sh. script seems fairly straightforward so maybe it can be modded to work with this device
Device: SHT-W09 M5 8.4 (eu)
Build Number: 8.0.0.151 (C432)
OS: Stock 151 with Phh GSI applied
ive never had a device this difficult to recover. samsung had odin to flash firmware, nexus 5/7/9 always had a way out - when i was building roms for moto xoom it wasnt this difficult.
Good luck man, it seems like when this thing bootloops, it activates some sort of defense mechanism that makes recovery particularly challenging.
I bootlooped after editing my vendor/build.prop file. DLoad method failed. Flashing partitions via fastboot failed. Stock recovery failed. TWRP became available, and I got it working...but no partitions would mount r/w. I paid to use Funky Huawei's unbrick tool, and it failed.
Funky Huawei's eRecovery method is basically all that worked for me. But I paid to use it (I still have a few weeks remaining on a pass).
These instructions, which don't involve payment to Funky Huawei, might or might not work:
https://forum.xda-developers.com/mate-9/how-to/funky-huawei-erecovery-solution-100-t3620165
Thanks for the alternative method.
I tried with hisuite using firmware finder, it uses the same funky DNS server. When I start the process the download works fine then on hisuite it says installing, does nothing then fails. After I reboot (usb in pc, all 3 buttons) it shows a usb symbol - installing but hangs at 5% for ages.
I tried with a portable router with ERecovery and it did not work unfortunately still failed to get info
I had to result to funkyhuawei who have now added SHT-W09C432 to their system.
In the 30 days I have this I'm tdetermined to find alternative solutions to fix this issue like all other devices tend to have.
I battled it out with Huawei support and there's no chance of an frp key - at least first 3 attempts. Also tried to get them tonexplqin ERecovery but said it's for insiders only just for service repairs. They have no regard for helping developers.
I was trying to figure out where the file get stored on ERecovery so if we could adb push to it and hold vol down + up + power to recover the device. I found i could pull from /dload (not internal/externalsd) which contained firmware_update_dload.zip but when uncompressed e enwbti be referenced to Qualcomm chips.
Any ideas on patching the recovery or boot image to prevent frp lock?
I also tried to see if there is a way from adb (while OS is running) to flip the OEM unlock back to on but there's nothing in system/global/settings that represents that.
It's strange because frp should not lock if you log back into the same account.
LOGMD said:
DLOAD:
updates performed with vol down+up+power
using the update extractor i can get the UPDATE.APP from the official firmware (SHT-W09C432B151 (8.0.0.151) i think for me)
but UPDATE.APP is over fat32 4GB limit. so i cant put it on the SDCard - and im not sure if the recovery can read exFat.
i tried with both but they fail immediately.
placing the files in the internal storage with DLOAD folder seems to send update to 5% then fail.
.
Click to expand...
Click to collapse
Any conclusions why this metod isnt working? On older device this works everytime if you do it right but not on this device? is it a Oreo thing or is it because the UPDATE.APP is so big?
omaga said:
Any conclusions why this metod isnt working? On older device this works everytime if you do it right but not on this device? is it a Oreo thing or is it because the UPDATE.APP is so big?
Click to expand...
Click to collapse
In my experience using the Huawei P9 the only time I was successful upgrading the firmware from the dload folder was when the firmware version ended with MF-PV (Public Version). Even though Huawei releases versions of the firmware without the MF-PV extension from what I read these versions are for testing purposes only.
In addition to my reply to you in the 8.0.0.163 firmware update thread there is a tool called HuRUpdater that has a similar upgrade procedure to the one I described when I upgraded the firmware on my SHT-AL09 from 151 to 163.
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
OK, thanks for this info, of course I thought that this device would be as easy to utdate then my much older M2-801L via dload which worked every time. And thanks for the tool tip, I'm looking into that thread as well :good:
Butch1326 said:
In my experience using the Huawei P9 the only time I was successful upgrading the firmware from the dload folder was when the firmware version ended with MF-PV (Public Version). Even though Huawei releases versions of the firmware without the MF-PV extension from what I read these versions are for testing purposes only.
In addition to my reply to you in the 8.0.0.163 firmware update thread there is a tool called HuRUpdater that has a similar upgrade procedure to the one I described when I upgraded the firmware on my SHT-AL09 from 151 to 163.
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
Click to expand...
Click to collapse
Thank You for the info.
Used it to update my CMR-AL19 and worked like a charme
omaga said:
Any conclusions why this metod isnt working? On older device this works everytime if you do it right but not on this device? is it a Oreo thing or is it because the UPDATE.APP is so big?
Click to expand...
Click to collapse
Sorry for the late reply had some busy months!
So from what I remember it's because the UPDATE.APP was too big. I tried recreating the update.app without the non-essentials but I couldn't get it working.
Huawei support when I asked about how to update via recovery just kept saying it's only for technicians at Huawei so they won't help me in any way!
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img
If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to:
DE2117 OEM Android 11 FINAL OTA
WARNING: This WILL erase all user data.
1. Place the firmware .zip file in the user root of internal phone storage.
2. Sideload OnePlus firmware Downgrade Tool on phone and use tool to flash the Android 11 firmware.
There is an Emergency Firmware install tool that OnePlus posted to the OP forum that does NOT check root status when the need to downgrade back to A11 was first acknowledged due to modem issue with first A12 OTA release.
This file was removed in a few days when they posted the official Downgrade tool replaced it.
I have used this tool to upgrade DE2117 C_16 to DE2117 C_17 while rooted and the built in upgrade tool failed at 37%.
Nice, first thanks for the hard work you're putting in. Second, is there an advantage to converting first to DE2117 then installing lineage as opposed to just installing lineage from DE2118 that you know of? I know in the other post you answered my other question stating that the Lineage will install on either so I wasn't sure if I'd get any benefit from starting over and converting my DE2118. TIA
Link575 said:
Nice, first thanks for the hard work you're putting in. Second, is there an advantage to converting first to DE2117 then installing lineage as opposed to just installing lineage from DE2118 that you know of? I know in the other post you answered my other question stating that the Lineage will install on either so I wasn't sure if I'd get any benefit from starting over and converting my DE2118. TIA
Click to expand...
Click to collapse
Lineage is using own kernel and boot.img on A11 so in the short run it is not going too make any difference, but when Lineage moves forward to A12 the OEM Firmware has newer drivers and is updated sooner, has more OEM features and bugfixes as well as no carrier bloatware.
It is possible that OP will neuter the Carrier firmware with an OTA update to prevent cross flashing device away from the Carrier rom in the next OTA update by preventing fastbootd from flashing the us oem from a carrier phone.
They have already removed fastboot boot command to boot a boot image without flashing it for test before you flash and to allow Magisk to make a backup of the original boot.img before adding Magisk.
I would convert NOW, before they decide to slam the door on this ability with a future OTA that will not allow you to downgrade and prevent this as they are under contract with the carriers to not allow this to be done.
Ok, thank you for the explanation. Guess I'll back everything up and convert it.
scanman0 said:
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img
If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to:
DE2117 OEM Android 11 FINAL OTA
WARNING: This WILL erase all user data.
1. Place the firmware .zip file in the user root of internal phone storage.
2. Sideload OnePlus firmware Downgrade Tool on phone and use tool to flash the Android 11 firmware.
There is an Emergency Firmware install tool that OnePlus posted to the OP forum that does NOT check root status when the need to downgrade back to A11 was first acknowledged due to modem issue with first A12 OTA release.
This file was removed in a few days when they posted the official Downgrade tool replaced it.
I have used this tool to upgrade DE2117 C_16 to DE2117 C_17 while rooted and the built in upgrade tool failed at 37%.
Click to expand...
Click to collapse
This worked perfectly after following your convert guide and upgrading to 12. Downgraded back to 11 so I could install lineageOS. Thanks again!
This reddit post has a link to an English version of the downgrade apk which makes it a little easier.
keeps saying verification failed
weirdfate said:
keeps saying verification failed
Click to expand...
Click to collapse
Did you remove root (Restore boot.img) and then factory reset?
You will loose all data doing this anyway.
I m trying as well .. but stuck with verification failed message just as scanman0 I m on stock android12 no root if anyone know how to fix it ... please assit
I just downgraded. Make sure you remove root via magisk. Then proceed to rollback to Android 11. Everything worked fine. I'll install lineage tonight when I get home.
radekmazur said:
I just downgraded. Make sure you remove root via magisk. Then proceed to rollback to Android 11. Everything worked fine. I'll install lineage tonight when I get home.
Click to expand...
Click to collapse
I did not have to remove root. I used the version posted that does not check for root but maybe there's a different reason.
Does the downgrade apk have to be sideloaded via ADB?
T3CHN0T33N said:
Does the downgrade apk have to be sideloaded via ADB?
Click to expand...
Click to collapse
Just place apk in phones working directory, same path where your downloads folder is. Then install from there like any other apk and run. I also kept the FW file in the same directory but I'm not sure if that was necessary.
So, just to confirm, I press "local install" and select the firmware zip and it closes? Is the tool supposed to do anything else or am I good to flash LineageOS?
T3CHN0T33N said:
So, just to confirm, I press "local install" and select the firmware zip and it closes? Is the tool supposed to do anything else or am I good to flash LineageOS?
Click to expand...
Click to collapse
Ummm if I remember correctly hit local install and then it will prompt to point towards which FW to use. After you hit it, it will go back to the previous screen, I think verify and unpack it, then install it. Mine did appear like it was doing nothing after picking the FW and so I picked again which screwed things up so just wait after picking, it should start.
After its done it will give a message saying to restart phone I think for it to take effect, then after you restart it should ask to wipe phone, then restart again and you'd be in A11 presumably. Once in A11 your good to follow the normal procedure to install Lineage. This is all from memory though so I MAY have missed something but I don't think I did.
Link575 said:
Ummm if I remember correctly hit local install and then it will prompt to point towards which FW to use. After you hit it, it will go back to the previous screen, I think verify and unpack it, then install it. Mine did appear like it was doing nothing after picking the FW and so I picked again which screwed things up so just wait after picking, it should start.
After its done it will give a message saying to restart phone I think for it to take effect, then after you restart it should ask to wipe phone, then restart again and you'd be in A11 presumably. Once in A11 your good to follow the normal procedure to install Lineage. This is all from memory though so I MAY have missed something but I don't think I did.
Click to expand...
Click to collapse
When you say "screwed things up" what do you mean? How did it effect the install?
T3CHN0T33N said:
When you say "screwed things up" what do you mean? How did it effect the install?
Click to expand...
Click to collapse
Nothing major, caused the UI to glitch out and made it seem like the process was stuck at 81% but when I closed the app and tried to do it again it jumped to 100 and said to restart the device.
I've downgraded a second time (I'm very indecisive on which OS I want to use) and that one went as expected since I knew to give it a second to start doing its thing.
Link575 said:
Nothing major, caused the UI to glitch out and made it seem like the process was stuck at 81% but when I closed the app and tried to do it again it jumped to 100 and said to restart the device.
I've downgraded a second time (I'm very indecisive on which OS I want to use) and that one went as expected since I knew to give it a second to start doing its thing.
Click to expand...
Click to collapse
Weird, for me it just closes the app and does nothing, both the official and emergency ones. I even tried adding it to magisk's deny-list.
But I just restored the boot image via magisk (didn't restart) and it works now...
scanman0 said:
Did you remove root (Restore boot.img) and then factory reset?
You will loose all data doing this anyway.
Click to expand...
Click to collapse
Yes I factory restored the phone and tried again. Still fails every time
Has anybody had any luck figuring out the verification failed message? I too have tried both the official and emergency apps, of course I can't read the actual message in what I presume is Chinese, but it doesn't do anything and the other version says verification failed. Have not rooted. Kind of at a loss right now and all I want to do is install Lineage! I've already got my unlock token from OnePlus, but my understanding is that the phone still needs to be on A11 before installling Lineage.