Hello,
hopefully you can help me with my seemingly bricked Honor Pro 8 because of root and stock rom update procedures. I bought the phone with amazon and the package seemes to give me the information to have an EU-version of the phone.
The fastboot get-oem-information code or so also puts out the status of an European bootloader.
Regarding my working steps first of all the phone took the new update. Then I was successful in unlocking the bootloader, installing TWRP and rooting it by supersu.
But after that I was curious about the "Magisk" rooting abilities. Therefore I tried a superuser-unroot via script finding inside this forum following by flashing a extracted boot.img of an update.app file of a DUK-L09C432B130 update. After ending in a bootloop by trying the 1.30 beta version of magisk I was able to boot the normal android desktop after I uninstalled the beta version and having flashed the normal 1.20 version.
But then I tried to install 2 certain modules inside of magisk. In consequence the problem was to see the rebooted android not to load any icons. In the other side it put up the message of not having enough mobile disk memory after some minutes which couldn't be true in fact. So I tried a factory reset inside TWRP and also a full wipe. Disappointingly I haven't been successful in rebooting android once more.
Therefore I unseccessfully tried to flash the Full-OTA-MF stock rom of DUK-L09C432B130 in two versions and the L09-C432b120a via the EMUI-install mode by pressing vol+ and - and power buttons. To do that I prepared a SD card as a exfat format. But I just received the message of "software install failed" when reaching 5 %.
So I got to the frustrating point not to know what stock rom I can flash in another try or doing anything else. I would be very glad if U could help me in this desperating situation. :fingers-crossed:
Thanks and best regards.
Can you boot to erecovery?
adriansticoid said:
Can you boot to erecovery?
Click to expand...
Click to collapse
I can but it just puts out the message "Getting package info failed"
Filo83 said:
I can but it just puts out the message "Getting package info failed"
Click to expand...
Click to collapse
Please try another version of firmware.
adriansticoid said:
Please try another version of firmware.
Click to expand...
Click to collapse
That is my problem not to know which version to use because three dowloaded EU-versions weren't successful to install. It resulted in an error at 5 % of the 3-buttons-install mechanism.
Filo83 said:
Hello,
hopefully you can help me with my seemingly bricked Honor Pro 8 because of root and stock rom update procedures. I bought the phone with amazon and the package seemes to give me the information to have an EU-version of the phone.
The fastboot get-oem-information code or so also puts out the status of an European bootloader.
Regarding my working steps first of all the phone took the new update. Then I was successful in unlocking the bootloader, installing TWRP and rooting it by supersu.
But after that I was curious about the "Magisk" rooting abilities. Therefore I tried a superuser-unroot via script finding inside this forum following by flashing a extracted boot.img of an update.app file of a DUK-L09C432B130 update. After ending in a bootloop by trying the 1.30 beta version of magisk I was able to boot the normal android desktop after I uninstalled the beta version and having flashed the normal 1.20 version.
But then I tried to install 2 certain modules inside of magisk. In consequence the problem was to see the rebooted android not to load any icons. In the other side it put up the message of not having enough mobile disk memory after some minutes which couldn't be true in fact. So I tried a factory reset inside TWRP and also a full wipe. Disappointingly I haven't been successful in rebooting android once more.
Therefore I unseccessfully tried to flash the Full-OTA-MF stock rom of DUK-L09C432B130 in two versions and the L09-C432b120a via the EMUI-install mode by pressing vol+ and - and power buttons. To do that I prepared a SD card as a exfat format. But I just received the message of "software install failed" when reaching 5 %.
So I got to the frustrating point not to know what stock rom I can flash in another try or doing anything else. I would be very glad if U could help me in this desperating situation. :fingers-crossed:
Thanks and best regards.
Click to expand...
Click to collapse
you download the nocheck recoveries from my rebranding guide, download the corresponding firmware by morph (important!), flash both recovery images just like stated in the guide, boot into recovery mode like you would do to boot into twrp, do a factory reset, reboot and insert the microsd with the dload folder from extracted downloaded firmware and boot into force dload mode (vol+ and vol- and power) - the installation should start now and reset everything back to full stock.
Regards
Thank you very much OldDroid. You're my hero. It worked fine.
But to install the new 130-update the phone starts inside TWRP and ends with an "error 9" and the words "block image verify", "asserts failed". Could it be possible to perform the update by starting the forced update process by pressing the three hardware buttons on booting? And is it possible not to wipe the data and losing root by using a update?
Viele Grüße aus Berlin nach Berlin
Filo83 said:
Thank you very much OldDroid. You're my hero. It worked fine.
But to install the new 130-update the phone starts inside TWRP and ends with an "error 9" and the words "block image verify", "asserts failed". Could it be possible to perform the update by starting the forced update process by pressing the three hardware buttons on booting? And is it possible not to wipe the data and losing root by using a update?
Viele Grüße aus Berlin nach Berlin
Click to expand...
Click to collapse
OTA packages cannot be installed via twrp at the moment
you should use stock recovery for that!
Best regards
Grüße zurrück aus Berlin nach Berlin
Could you explain me a bit more please? Is it the standard system update ins the systems menu, here it wants to load the 2,9 GB file. Updating this way with the "no check recovery" resulted in an checking error at about 12 %.
Or could it be via recovery shortly after starting the phone? But there are no choices to choice. It just automaticely begins installing something stopping at 5 %.
Hope you can help one more please.
Filo83 said:
Could you explain me a bit more please? Is it the standard system update ins the systems menu, here it wants to load the 2,9 GB file. Updating this way with the "no check recovery" resulted in an checking error at about 12 %.
Or could it be via recovery shortly after starting the phone? But there are no choices to choice. It just automaticely begins installing something stopping at 5 %.
Hope you can help one more please.
Click to expand...
Click to collapse
soooo, if you flashed one of @-=MoRpH=- 's firmwares, your device is back to stock and the recoveries have been overwritten again! I don't recommend flashing OTA updates or other things through the NoCheck version as it is only intended for worst-case cenarios.
But could you tell me the single steps to update from Morph's DUK-L09C432B120 version to the newest version DUK-L09C432B130?
I only got errors to update the firmware DUK-L09C432B130 from the stock rom thread in this forum and the russian website mentioned there.
Filo83 said:
But could you tell me the single steps to update from Morph's DUK-L09C432B120 version to the newest version DUK-L09C432B130?
I only got errors to update the firmware DUK-L09C432B130 from the stock rom thread in this forum and the russian website mentioned there.
Click to expand...
Click to collapse
extract the firmware and flash manualy using fastboot
thilak devraj said:
extract the firmware and flash manualy using fastboot
Click to expand...
Click to collapse
That is just needed to be done as last resort. Better stick with dload.
adriansticoid said:
That is just needed to be done as last resort. Better stick with dload.
Click to expand...
Click to collapse
he said he got some errors doing dload, so this method works too
thilak devraj said:
he said he got some errors doing dload, so this method works too
Click to expand...
Click to collapse
He must find the right firmware first.
adriansticoid said:
He must find the right firmware first.
Click to expand...
Click to collapse
finding a firmware for huawei devices is a pain in the ass, you know
thilak devraj said:
finding a firmware for huawei devices is a pain in the ass, you know
Click to expand...
Click to collapse
That's why we have Firmware Finder.
adriansticoid said:
That's why we have Firmware Finder.
Click to expand...
Click to collapse
even in firmware finder, it will be difficult sometimes for sone devices
thilak devraj said:
even in firmware finder, it will be difficult sometimes for sone devices
Click to expand...
Click to collapse
Maybe. But they are constantly improving.
adriansticoid said:
Maybe. But they are constantly improving.
Click to expand...
Click to collapse
i appreciate the firmware finder, but sometimes, its just inappropriate
Related
I have an AT&T SM-N910A Note 4, currently on Lollipop 5.0.1. It is permanent unlocked via CODE and I'm using it outside the US with a foreign SIM with no problems.
Last April 14 ATT released a firmware update (OTA) to 5.0.1 with new:
Baseband Version: N910AUCU1COC4
Kernel Version: [email protected]#1
Build Number: LRX22C.N910AUCU1COC4
When i try to get that update via ">Settings>General>About Device> Software Updates"... it does NOTHING. Just display a text saying "No Firmware".
To me it seems I'm being ruled out from updates....
Does anyone knows why is this? Do I need to be a current AT&T customer to have updates?
IS THERE ANY PLACE TO FIND THE LATEST 5.0.1 FIRMWARE files to update from ODIN??
Thank you guys for your help!!
jomeza001 said:
I have an AT&T SM-N910A Note 4, currently on Lollipop 5.0.1. It is permanent unlocked via CODE and I'm using it outside the US with a foreign SIM with no problems.
NOW... when I Try to manually update to 5.0.2 via ">Settings>General>About Device> Software Updates"... it does NOTHING. Just display a text saying "No Firmware".
To me it seems I'm being ruled out from updates....
Does anyone knows why is this? Do I need to be a current AT&T customer to have updates?
IS THERE ANY PLACE TO FIND THE 5.0.2 FIRMWARE files to update from ODIN??
Thank you guys for your help!!
Click to expand...
Click to collapse
There is no 5.0.2 as far as I know
jomeza001 said:
I have an AT&T SM-N910A Note 4, currently on Lollipop 5.0.1. It is permanent unlocked via CODE and I'm using it outside the US with a foreign SIM with no problems.
NOW... when I Try to manually update to 5.0.2 via ">Settings>General>About Device> Software Updates"... it does NOTHING. Just display a text saying "No Firmware".
To me it seems I'm being ruled out from updates....
Does anyone knows why is this? Do I need to be a current AT&T customer to have updates?
IS THERE ANY PLACE TO FIND THE 5.0.2 FIRMWARE files to update from ODIN??
Thank you guys for your help!!
Click to expand...
Click to collapse
Happened to me too on the initial Lollipop update. Basically, the update was downloading, but would fail at install. Eventually, I got the "No Firmware" toast every time I tried to check for updates.
I had to go to Best Buy and they reflashed Kitkat (Because they didn't have the update yet). After that, the update check worked again and the update installed.
And as just stated, there is no 5.0.2 update. Only 2x 5.0.1 updates. First update was the Lollipop OS. The second was just a patch to correct some things.
spexwood said:
Happened to me too on the initial Lollipop update. Basically, the update was downloading, but would fail at install. Eventually, I got the "No Firmware" toast every time I tried to check for updates.
I had to go to Best Buy and they reflashed Kitkat (Because they didn't have the update yet). After that, the update check worked again and the update installed.
And as just stated, there is no 5.0.2 update. Only 2x 5.0.1 updates. First update was the Lollipop OS. The second was just a patch to correct some things.
Click to expand...
Click to collapse
Yes I did read your post man. I would really love to NOT do a factory reset... Thanks for your reply.
stevenj05 said:
There is no 5.0.2 as far as I know
Click to expand...
Click to collapse
You're right. I edited my post. Thanks!
jomeza001 said:
Yes i read your post man. I would really love to NOT do a factory reset... Thanks for your reply.
You're right. I edited my post. Thanks!
Click to expand...
Click to collapse
It wasn't a factory reset. It was a reflash. I didn't lose any of my files, apps, or settings. It was like updating via OTA, except the Best Buy guy did it via USB and the update was the same exact firmware version that I already had.
I'm not even sure if Best Buy is an option for you, but using Odin to reflash the latest Kitkat firmware should do the same thing. I say this because I've done it on my Samsung tablet and I don't lose apps, settings or data. I do lose root though (easy to regain), but that won't matter with the n910a anyways.
Edit:
Using the firmware repair option in Kies may work too, but not 100% sure if it'll retain your data since I've never tried this before.
spexwood said:
It wasn't a factory reset. It was a reflash. I didn't lose any of my files, apps, or settings. It was like updating via OTA, except the Best Buy guy did it via USB and the update was the same exact firmware version that I already had.
I'm not even sure if Best Buy is an option for you, but using Odin to reflash the latest Kitkat firmware should do the same thing. I say this because I've done it on my Samsung tablet and I don't lose apps, settings or data. I do lose root though (easy to regain), but that won't matter with the n910a anyways.
Edit:
Using the firmware repair option in Kies may work too, but not 100% sure if it'll retain your data since I've never tried this before.
Click to expand...
Click to collapse
Just tried it but there is a warning about loosing all data if performing that.
Best Buy is not an option for me.
Unfortunately, flashing the update via Odin is your only option at this time. You will not be able to upgrade firmware via OTA, if not on an ATT network. There are apps that will allow you to backup and restore your call history and text messages without root. You can try copying your android data to your external storage card and copying the files back to the device after the firmware has been flashed.
bigron77 said:
Unfortunately, flashing the update via Odin is your only option at this time. You will not be able to upgrade firmware via OTA, if not on an ATT network. There are apps that will allow you to backup and restore your call history and text messages without root. You can try copying your android data to your external storage card and copying the files back to the device after the firmware has been flashed.
Click to expand...
Click to collapse
Good day,
I am with my ATT Note 4 N910A (ATT locked) is in this situation ,pls. see the att. pictures
once the phone reboot doesn't go over 5 update and reboot again every minute doing the same thing.
can I do something via odin? I have already used odin and installed some rom to my old note 2 but with this new note 4 I am lost and I need you :crying:
any suggestion/help?
thanks and have a good day.
thepinkpanter said:
Good day,
I am with my ATT Note 4 N910A (ATT locked) is in this situation ,pls. see the att. pictures
once the phone reboot doesn't go over 5 update and reboot again every minute doing the same thing.
can I do something via odin? I have already used odin and installed some rom to my old note 2 but with this new note 4 I am lost and I need you :crying:
any suggestion/help?
thanks and have a good day.
Click to expand...
Click to collapse
Hey @thepinkpanter, just saw your post.
First, if you haven't already, remove the battery, boot into recovery mode and do a factory data reset, then reboot.
If you already tried that, then I would try flashing back to KK (NIE or NK3) both files can be found in the General Thread for the ATT N4. Use can use ODIN ver 3.0.7, 3.0.9 or 3.10.6, just follow the instructions for the specific ver you choose.
Let me know if you need further assistance..
bigron77 said:
Hey @thepinkpanter, just saw your post.
First, if you haven't already, remove the battery, boot into recovery mode and do a factory data reset, then reboot.
If you already tried that, then I would try flashing back to KK (NIE or NK3) both files can be found in the General Thread for the ATT N4. Use can use ODIN ver 3.0.7, 3.0.9 or 3.10.6, just follow the instructions for the specific ver you choose.
Let me know if you need further assistance..
Click to expand...
Click to collapse
I have already one the factory data reset......so i'll try flashing back to KK (NIE or NK3) and let you know
thanks again
bigron77 said:
Hey @thepinkpanter, just saw your post.
First, if you haven't already, remove the battery, boot into recovery mode and do a factory data reset, then reboot.
If you already tried that, then I would try flashing back to KK (NIE or NK3) both files can be found in the General Thread for the ATT N4. Use can use ODIN ver 3.0.7, 3.0.9 or 3.10.6, just follow the instructions for the specific ver you choose.
Let me know if you need further assistance..
Click to expand...
Click to collapse
as you can see from the att. pictures in my previous help request I have the LRX22C.N910AUCU1COC4 5.0.1 , yesterday I reflashed the N910AUCU1COC4 just in case ......and nothing happened then I checked what is on the outer box lable and the version of my unit is N910AUCU1ANIE same version you suggested me to flash,
but at this point my question is can I flash to the N910AUCU1ANIE over the N910AUCU1COC4 ??????
thanks again
thepinkpanter said:
as you can see from the att. pictures in my previous help request I have the LRX22C.N910AUCU1COC4 5.0.1 , yesterday I reflashed the N910AUCU1COC4 just in case ......and nothing happened then I checked what is on the outer box lable and the version of my unit is N910AUCU1ANIE same version you suggested me to flash,
but at this point my question is can I flash to the N910AUCU1ANIE over the N910AUCU1COC4 ??????
thanks again
Click to expand...
Click to collapse
Hey @thepinkpanter
You can flash NIE over OC4. I have done so a few times myself. Currently I'm using NK3.
It looks to me like your data partition is not being wiped. If I am remembering correctly, you do not get the android is updating screen on initial boot.
bigron77 said:
Hey @thepinkpanter
You can flash NIE over OC4. I have done so a few times myself. Currently I'm using NK3.
It looks to me like your data partition is not being wiped. If I am remembering correctly, you do not get the android is updating screen on initial boot.
Click to expand...
Click to collapse
I did try everything.....I also did wipe the data partition just after factory recovery ........
and the system once reboot start the android upgrading and the optimizing stop almost every time to 6 or 10 to 48 ..........
as soon I am back home i'll download the NIE from this forum http://forum.xda-developers.com/note-4-att/general/stock-to-stock-odin-flashable-tested-t2915915
thanks again for your kind help
thepinkpanter said:
I did try everything.....I also did wipe the data partition just after factory recovery ........
and the system once reboot start the android upgrading and the optimizing stop almost every time to 6 or 10 to 48 ..........
as soon I am back home i'll download the NIE from this forum http://forum.xda-developers.com/note-4-att/general/stock-to-stock-odin-flashable-tested-t2915915
thanks again for your kind help
Click to expand...
Click to collapse
@thepinkpanther
I would suggest selecting Nand Erase All, F. Reset Time, along with Auto Reboot in Odin on your next attempt. This will erase all of your partitions (system, data, etc) prior to flashing the ROM files. Unfortunately, this will erase all of the data on your internal storage card, but I believe this will fix the problem you're experiencing.
Do not select Re-Partition or EFS Clear, this will wipe your phones IMEl.
bigron77 said:
@thepinkpanther
I would suggest selecting Nand Erase All, F. Reset Time, along with Auto Reboot in Odin on your next attempt. This will erase all of your partitions (system, data, etc) prior to flashing the ROM files. Unfortunately, this will erase all of the data on your internal storage card, but I believe this will fix the problem you're experiencing.
Do not select Re-Partition or EFS Clear, this will wipe your phones IMEl.
Click to expand...
Click to collapse
So maybe by selecting Nand I could also try first with the actual N910AUCU1COC4 ?????
thanks again
thepinkpanter said:
So maybe by selecting Nand I could also try first with the actual N910AUCU1COC4 ?????
thanks again
Click to expand...
Click to collapse
Yes, that should completely remove the current firmware prior to flashing.
Samsung Galaxy Note 4 AT&T 5.0.1 Baseband gone auto and continuously restart now Help
Samsung Galaxy Note 4 AT&T 5.0.1 Baseband Unknown auto and continuously restarting now....
History of this phone is,... :
01. Customer came for Unlock Note 4 SM-N910A 5.0.1 N910AUCU1COC4 Baseband.
02. First I was put into recovery mode and " Enable CP logging " then restart phone.
03. Second reboot normal mode, I dial *#0808# and Select " DM+Modem+ADB ".
04. thirdly I dialed *#9090# and Select first option " DM/DUN over USB " ( and after selected then auto restart mobile , and when power on then about 10-15 Second it restart auto again and again same. Then I checked Settings> "Baseband" I saw show "Unknown" and IMEI " null/null ".
05. Then I do Factory Reset then mobile and then it show " Android is upgrading... Optimizing app 6 of 48. " Then Restart again.... Continuous ....
06. I downloaded N910AUCU1COC2 Firmware BL,AP,CP,CSC_ATT file and Flash with Odin by Ticked, " Nand Erase All " F.Reset Time and Auto Reboot.
07. But Still Same " Android is Upgrading.... " restart...
Help Need for solve this problem please...
Problem Solved
http://forum.gsmhosting.com/vbb/f68...ting-problem-5-0-1-coc4-1973984/#post11194760
Here is unreleased B163 OTA update. (Must be on B156)
https://drive.google.com/file/d/0B79PB4FhWfJAM0hMUWNDanE1ZW8/view?usp=sharing
Note that I haven't found a way to install it yet.
Change log is:
Dear customers, this update improved experience of camera and system performance. involved latest Google patch, Please update your device for improved experience.
Optimized experience of camera.
Improved system performance.
Improved security of system.
Improved system stability.
I have found a way to get all OTA and full updates. Unfortunately, this update only exists in OTA form right now.
I'm hoping someone who has a non-Chinese Mate8 can get in touch with me and I can find all the updates for it as well.
Thank you. How would you install it on the AL10 (stock recovery/unrooted) device?
wow, good work there buddy! looking forward to more OTA leaks from your side
Hiw to install?
please read the first post: "Note that I haven't found a way to install it yet."
Guys full rom (B156) here to hope to pass to B163
https://androidfilehost.com/?fid=24399994186367275
i think this technique can be used if we are able to extract the files into the OTA file.
http://forum.xda-developers.com/showpost.php?p=65113953&postcount=166
CyberMomo said:
i think this technique can be used if we are able to extract the files into the OTA file.
http://forum.xda-developers.com/showpost.php?p=65113953&postcount=166
Click to expand...
Click to collapse
No, mate ota file don't work in this way
If I have enough free time, I will create a way to install whatever OTA you want by reverse-engineering the network protocol. Stay tuned
good stuff, hope we manage on how to update by ota zip .
it seems mate8 is not allow local ota update.
hkfriends said:
good stuff, hope we manage on how to update by ota zip .
it seems mate8 is not allow local ota update.
Click to expand...
Click to collapse
download the ota zip file but it in dload folder and but it in sd card
then power off mate 8
and push volume up+down+power for 10 second
the update will begin
rowihel2012 said:
download the ota zip file but it in dload folder and but it in sd card
then power off mate 8
and push volume up+down+power for 10 second
the update will begin
Click to expand...
Click to collapse
I tried that with B156 and it froze at 5%
ajsmsg78 said:
I tried that with B156 and it froze at 5%
Click to expand...
Click to collapse
I confirm that...putting the zip on internal sd it doesn't give the message "impossible to find the update package" (or similar I don't remember) as you put it in the external...the verification starts, starts also the "updating phase" but it freezes immediately at 5% (in my opinion without modifying anything, cause I was able to reboot normally)....just to be clear, I'm on B156 but I've root and decrypted boot...maybe the success could be obtained starting from a clean b156....maybe rowihel2012 could kindly give us more details on his upgrade success (phone model, starting firmware status,...)
lukemo said:
I confirm that...putting the zip on internal sd it doesn't give the message "impossible to find the update package" (or similar I don't remember) as you put it in the external...the verification starts, starts also the "updating phase" but it freezes immediately at 5% (in my opinion without modifying anything, cause I was able to reboot normally)....just to be clear, I'm on B156 but I've root and decrypted boot...maybe the success could be obtained starting from a clean b156....maybe rowihel2012 could kindly give us more details on his upgrade success (phone model, starting firmware status,...)
Click to expand...
Click to collapse
Non-root stock does not work either to install this. There's an .app file that HiSuite recognizes if you unzip the file that you downloaded... However once loaded and phone restarts it just takes you to a screen where you can wipe or restart. Tried the other way too and get the 5% and then freezes. Something isn't right with the archive. Saw another dload folder on root but can't mess with it since I'm stock. Maybe you could try that directory
acer73 said:
Guys full rom (B156) here to hope to pass to B163
https://androidfilehost.com/?fid=24399994186367275
Click to expand...
Click to collapse
This rom is for NXT-L29 version?
theyre both for AL10 but u can crossflash. also, no one has gotten B163 to work yet
Sent from my Huawei Mate 8 NXT-AL10 using Tapatalk
In the root directory there is a folder called dload and inside is a file called update_huawei_dload. Has anyone tried renaming the update to that same name and putting it in that folder?
Has anyone tried to flash this OTA zip file by TWRP ?
I just opened this zip file and found some of scripts which are similar with that's used in TWRP.
I flashed L29 152 update NXT-l29C432B152-FULL-OTA in TWRP on my AL10 after deleting all data. And everything works, so far, apart from themes.
They apply but doesnt do anything. Also it did throw up some error but forgot to take note of it.
I presume b163 will do the same thing,
ajsmsg78 said:
In the root directory there is a folder called dload and inside is a file called update_huawei_dload. Has anyone tried renaming the update to that same name and putting it in that folder?
Click to expand...
Click to collapse
it dosn't work.
hey community
I've tested CAN-L11C432B320 a while and miss the equalizer-app, also have an extreme powersaving device (...) but if i'm running runtastic they will turn off gps after 30 seconds display-off-time, background-services like whatsapp, pushbullet, etc.. will close after a few hours "inactivity", bad fingerprint-performace, some xposed-plugins have massive battery-drain and wont work....
so on.. i still search a while if its possible to get my stock emui 4.1 back...
...and yesterday i found this post:
h**p://w*w.htcmania.com/showthread.php?p=24388723
it looks like there was a full CAN-L11C432B100 and CAN-L01C432B100 firmware but i could not install them
i put the update.app in SDCARD:\dload and tried to install them with original EMUI5-recovery and the extracted EMUI4.1-recovery - everytime it hangs up at 5% and reboots after ~5 minutes.
i'm clueless.. maybe someone will also downgrade and found a solution how to get them work...
sorry from my bad english and the link-modification but i'm new here
I think we need to flash first the EMUI 4.1 recovery.img
Houamei said:
I think we need to flash first the EMUI 4.1 recovery.img
Click to expand...
Click to collapse
i've flash erecovery.img and recovery.img extracted from the update.app --> reboots too on 5%
extracted 4.1 Recovery: mega.nz/#!1MdXmART!Bbd3COTNnCsOB4iVMwQ0vOQhdEvzWDaWVnRhMwFMg08
xCite86 said:
hey community
I've tested CAN-L11C432B320 a while and miss the equalizer-app, also have an extreme powersaving device (...) but if i'm running runtastic they will turn off gps after 30 seconds display-off-time, background-services like whatsapp, pushbullet, etc.. will close after a few hours "inactivity", bad fingerprint-performace, some xposed-plugins have massive battery-drain and wont work....
so on.. i still search a while if its possible to get my stock emui 4.1 back...
...and yesterday i found this post:
h**p://w*w.htcmania.com/showthread.php?p=24388723
it looks like there was a full CAN-L11C432B100 and CAN-L01C432B100 firmware but i could not install them
i put the update.app in SDCARD:\dload and tried to install them with original EMUI5-recovery and the extracted EMUI4.1-recovery - everytime it hangs up at 5% and reboots after ~5 minutes.
i'm clueless.. maybe someone will also downgrade and found a solution how to get them work...
sorry from my bad english and the link-modification but i'm new here
Click to expand...
Click to collapse
There is a link for a rollback update, but i'm not home. When I get there, I send it. About battery, try to use greenify to help it to last long.
You can't just try to use a full package because of versioning scheme they use.
Here http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v72696/f1/full/update.zip
Same problem here, still drops at 5% even with the new file
I just wana know the best way to revert to stock
---------- Post added at 07:32 PM ---------- Previous post was at 07:28 PM ----------
and sorry I don't have an SD Card
Vinnom said:
Here http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v72696/f1/full/update.zip
Click to expand...
Click to collapse
thanks for the file but it won't work for me too..
the install process stops at 5% "Installing update" and reboots after a few minutes
can we extract all from the ota update zip and install via flash? can this work?
xCite86 said:
thanks for the file but it won't work for me too..
the install process stops at 5% "Installing update" and reboots after a few minutes
Click to expand...
Click to collapse
Hmmm, sorry, I thought it would help. In fact, the package is listed as a rollback to M, but it is for CAN-L11. The rollback for CAN-L01, I didn't find. As there isn't many differences between those models, I thought it would work
EDIT: now that I read the op again, I noticed that your model is CAN-L11. I wonder why it didn't work
Houamei said:
can we extract all from the ota update zip and install via flash? can this work?
Click to expand...
Click to collapse
No, it won't.
The reason behind this is because system partition get smaller (because nougat way of update) after updating it to emui 5. So the old system.img won't fit the new partition
My phone only hangs up at 5% when the usb cable is connected. When i open the download mode without connected usb cable, it works.
Mikey94 said:
My phone only hangs up at 5% when the usb cable is connected. When i open the download mode without connected usb cable, it works.
Click to expand...
Click to collapse
So you downgraded?
Mikey94 said:
My phone only hangs up at 5% when the usb cable is connected. When i open the download mode without connected usb cable, it works.
Click to expand...
Click to collapse
did you downgrade your nougat successfully with the files above??
edit: i tried it without a connected usb cable and got "software install failed!" after short time
Is a restore of a CAN-L11 backup from Android 6 in TWRP not possible?
i think this should work if you or someone else share a backup i could try..
Michiel0912 said:
Is a restore of a CAN-L11 backup from Android 6 in TWRP not possible?
Click to expand...
Click to collapse
no, in my opinion the nougat bootloader want work with mm.
I would flash the firmeware of mm and after that flash twrp and restore the backup after that [emoji106]
It will work. There is a backup within twrp thread, from bluesmothie.
Vinnom said:
It will work. There is a backup within twrp thread, from bluesmothie.
Click to expand...
Click to collapse
found it...
https://forum.xda-developers.com/showpost.php?p=70259615&postcount=2
re-unlocked bootloader
flashed twrp with fastboot flash recovery twrp_huawei_generic_a53_YYYYMMDD.img
copied all the dropbox files to /external_sd/TWRP/BACKUPS/FPFDU16930014596/1970-03-18--16-40-58_CANC432B100/...
wipe all partitions except sd-card
recover the complete backup
so @Vinnom many thanks for your help. i got my phone back to life (after fomatted data partition) and got downgraded to CANC432B100 now.
Michiel0912 said:
Is a restore of a CAN-L11 backup from Android 6 in TWRP not possible?
Click to expand...
Click to collapse
Yeah, thanks Vinnom...
xCite86 said:
found it...
https://forum.xda-developers.com/showpost.php?p=70259615&postcount=2
re-unlocked bootloader
flashed twrp with fastboot flash recovery twrp_huawei_generic_a53_YYYYMMDD.img
copied all the dropbox files to /external_sd/TWRP/BACKUPS/FPFDU16930014596/1970-03-18--16-40-58_CANC432B100/...
wipe all partitions except sd-card
recover the complete backup
so @Vinnom many thanks for your help. i got my phone back to life (after fomatted data partition) and got downgraded to CANC432B100 now.
Click to expand...
Click to collapse
Did the same thing, but first TWRP didn't find the backup. So i did a small backup just of the boot partition, so that TWRP makes a new backupfolder "FPF4C16A07000014"". Now i renamed the " FPFDU16930014596" to the new "FPF4C16A07000014" and TWRP found the backup and i was able to restore :highfive::highfive:
Small Addition:
It was a freaking fight to get my bootloader unlocked again, cause i lost the unlock code.
The websites (english and asian) are freaking BS. Was not able to get to the page where you get the code, so i downloaded DC-Tool and payed 4 dollars for the damn code.
Now the code is saved in my owncloud, dropbox, google drive, on a sheet of paper and google notes. No way to lose it again
B100 firmware is much smoother than B320 but has a lack of comfort, like i'm missing the new quick settings with double pull down and the touch responsibility of slide bars (like the volume bars) is not very good in B100... But i won't upgrade to 320 again, because of the following points that make it a no go for daily driver:
- Camera is very slow and hangs up
- Video playback is very slow and buggy (no matter if it's in the galery or youtube, ect.)
- Fingerprint is too slow
- Whole system gets very slw if you dont clean up the app history
Will upgrade again when there is a new version out
please am having same issue here. tried restore but still not booting.
problem is cust. what do i do about it.
HELP ME
Hello all!
This morning I updated Magisk Manager.
Once updated (or perhaps only downloaded update) the app prompted a reboot.
I rebooted and ended up in TWRP.
But I did not know what to do in TWRP so I rebooted system...
However, now the phone cannot boot and after one try it reboots into TWRP again.
PLEASE HELP ME!
I need my phone for work! Like now-now! :silly: :crying:
dustylambo said:
Hello all!
This morning I updated Magisk Manager.
Once updated (or perhaps only downloaded update) the app prompted a reboot.
I rebooted and ended up in TWRP.
But I did not know what to do in TWRP so I rebooted system...
However, now the phone cannot boot and after one try it reboots into TWRP again.
PLEASE HELP ME!
I need my phone for work! Like now-now! :silly: :crying:
Click to expand...
Click to collapse
How soon is now ? follow the white rabbit:good:
https://forum.xda-developers.com/zenfone2/help/help-bootloop-to-recovery-t3577504
timbernot said:
How soon is now ? follow the white rabbit:good:
https://forum.xda-developers.com/zenfone2/help/help-bootloop-to-recovery-t3577504
Click to expand...
Click to collapse
Well, that rabbit went into quite the hole... hehe
However, at the other end was a person who restored an old backup to revert this problem... And I -MAYBE- have an old backup on my external hdd, but won't that wipe all data that has been written to my phone since that "MAYBE" backup?
The other suggestion was wiping my MISC-partition using commands through ADB - something I have no clue how to setup and/or execute.
Still, thank you so much for your effort!
Reading all of this made me remember that one time I spaced out and tried to install an official firmware update upon release and prompt, which lead to the same issue. I could then just reinstall an older raw firmware version, which left all my files and data intact. Hopefully this will work here too.
BUT... It still feels very risky. If anyone out there has any sure-fire solution to this update Magisk Manager through the built-in updater no-boot issue, then please feel free to let me know - I would be forever in your debt
The best surefire solution is just don't. And BTW always backup before you flash anything in twrp.
Sent from my ASUS_Z00A using Tapatalk
---------- Post added at 08:49 AM ---------- Previous post was at 08:47 AM ----------
timbernot said:
How soon is now ? follow the white rabbit:good:
https://forum.xda-developers.com/zenfone2/help/help-bootloop-to-recovery-t3577504
Click to expand...
Click to collapse
I love what you did there! Lol
Sent from my ASUS_Z00A using Tapatalk
kenbo111 said:
The best surefire solution is just don't. And BTW always backup before you flash anything in twrp
Click to expand...
Click to collapse
I didn't flash anything in twrp. If you're gonna reply at least read the post. Also, none of what you wrote is a solution, unless you're in possession of a time machine. I'll keep it in mind for the next time though (of which there won't be one). Thanks, captain hindsight.
dustylambo said:
I didn't flash anything in twrp. If you're gonna reply at least read the post. Also, none of what you wrote is a solution, unless you're in possession of a time machine. I'll keep it in mind for the next time though (of which there won't be one). Thanks, captain hindsight.
Click to expand...
Click to collapse
That's what the update does. Reboots to twrp and installs the download. Maybe you should know what you're doing before you snap at us.
Sent from my ASUS_Z00A using Tapatalk
dustylambo said:
However, at the other end was a person who restored an old backup to revert this problem... And I -MAYBE- have an old backup on my external hdd, but won't that wipe all data that has been written to my phone since that "MAYBE" backup?
Click to expand...
Click to collapse
No, just restore the boot partition (16MB).
I learnt the hard way about backup, when years ago I didn't make one for my Galaxy S2 and lost everything (pictures, etc). Now after installing TWRP I always do a backup...
You should be able to reflash your boot partition with a fastboot command like "fastboot flash boot boot.img" (people with more knowledge than me can help you)
EDIT: the problem is that our Zenfone2 needs a signature for the boot partition, this is why we have a special Magisk installer that just add the signature to the image. The automatic update installer of Magisk has no clue about this, me and a few others here made the same mistake as you when Magisk popup "I have an update!" and we clicked "Install"...
All your data and app are still there, do not worry, no need to wipe anything, just reflash a signed boot.
kenbo111 said:
That's what the update does. Reboots to twrp and installs the download. Maybe you should know what you're doing before you snap at us.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Look... I am sorry if I "snapped" as you put it... But let's make one thing clear - I snapped at YOU; there is no "us" in this case, as you tried to skew it. Don't lump yourself together with these other helpful people, because so far you have nothing in common to me. If I were looking for someone to go "Hey, I got a solution - you know that thing you did? - Don't do it again!" I'd just go stand on the street corner with a sign asking for someone to slap my face.
As for your principal of don't do things if your not sure of how they work, I am totally behind that. But it has NOTHING to offer here as we are past that point. A broad comparison would be like "a solution to world hunger = eat food" ("but we don't have any food!" "you should have thought of that before you started starving now shouldn't you...?!").
In your defense, I guess you really believe you are trying to help. But compare your comment to the other ones posted and it is quickly clear that you are not. However, YOU ARE RIGHT, I should've known better and shouldn't do it again. And obviously I am enerved at this situation, but equally obvious (now) is that what you wrote is NOT "the best sure-fire solution" as what was posted afterward seems at least 100% (would have been more if possible) more applicable to my issue.
Anyway, I'll do the right thing here in the end, after having said so many things, and admit, once again, that I was wrong, you were right, I snapped for no good reason and you were just trying to help.
And I sincerely apologize for my rude behaviour. Hopefully now you can at least understand my reaction.
Also, fair is fair - Maybe TWRP flashes the update before it even enters into it. It would be the first I've EVER heard of something like that. But I am out of my element a bit here, so I will withdraw that comment and once again apologize for snapping at you because of it.
Magister54 said:
No, just restore the boot partition (16MB).
I learnt the hard way about backup, when years ago I didn't make one for my Galaxy S2 and lost everything (pictures, etc). Now after installing TWRP I always do a backup...
You should be able to reflash your boot partition with a fastboot command like "fastboot flash boot boot.img" (people with more knowledge than me can help you)
EDIT: the problem is that our Zenfone2 needs a signature for the boot partition, this is why we have a special Magisk installer that just add the signature to the image. The automatic update installer of Magisk has no clue about this, me and a few others here made the same mistake as you when Magisk popup "I have an update!" and we clicked "Install"...
All your data and app are still there, do not worry, no need to wipe anything, just reflash a signed boot.
Click to expand...
Click to collapse
NOW THIS IS HELPING!
THANK YOU SO MUCH!
Basically, you are saying that I would, in theory, just have to use fastboot and flash boot.img (extracted from any firmware?) again, which I am very familiar with how to do, and presto - boot partition restored and working (once again, in theory)?
Sounds amazing!:good:
dustylambo said:
NOW THIS IS HELPING!
THANK YOU SO MUCH!
Basically, you are saying that I would, in theory, just have to use fastboot and flash boot.img (extracted from any firmware?) again, which I am very familiar with how to do, and presto - boot partition restored and working (once again, in theory)?
Sounds amazing!:good:
Click to expand...
Click to collapse
Yes, if you have a Z00A for instance with MM version 223, take the Z00A.zip file from https://forum.xda-developers.com/zenfone2/general/bl-unlock-ze551ml-toolkit-t3546293 and use the file stock\z00a\223\boot.img
This is stock unsigned boot.img file for M .223
http://www.mediafire.com/file/rw73099svgbv0kv/boot.img
timbernot said:
boot.img file for M .223
http://www.mediafire.com/file/rw73099svgbv0kv/boot.img
Click to expand...
Click to collapse
Is there any way to check from TWRP or using fastboot, or otherwise find out what version of the rom I have (had)?
I am definitely still on LolliPo... I think I am one or two official updates from the switch to MarshMallow... But how can I be sure?
WW_ZE551ML_2.20.40.139_sal358-amtech.vn
Last year sometime I ran into a similar problem, where I had to flash raw firmware in order to unbrick the phone... This is the firmware that I downloaded and flashed then.
However, within this .raw-file there is no boot.img ...? There are a couple of .img-files, but none named boot.
On a side-note: When I bricked it last year and had to flash this raw firmware, which I did with Asus Flash Tool, if I am not mistaken... However, whichever way I did it, I managed to flash and then boot as usual. The phone then updated all apps, and I was just blessed with this wonderful sight of "my phone" with all the apps, files and data still intact.
And this problem, which resulted in the same boot issue, came from trying to apply an official OTA update, just after rooting and unlocking the bootloader (forgot myself for just a moment there), which to me seems like a way more serious screw-up than what I just managed to do today...?
@dustylambo
You still boot to TWRP ?
Simple questions
check date of back ups , course you won't be able to restore but title will have builds.
What twrp build ?
Then....
Select reboot in twrp then power off in twrp .
Wait 15 seconds...
Power plus vol+ , you can now boot to bootloader.
What IFWI version ?
0094.0177 or .0173 is LP
0094.0183 is M
Flash relevant raw , without ticking wipe data in AFT.
Check my unbrick thread in my signature for AFT and links to raws
Enjoy
timbernot said:
@dustylambo
You still boot to TWRP ?
Simple questions
check date of back ups , course you won't be able to restore but title will have builds.
What twrp build ?
Then....
Select reboot in twrp then power off in twrp .
Wait 15 seconds...
Power plus vol+ , you can now boot to bootloader.
What IFWI version ?
0094.0177 or .0173 is LP
0094.0183 is M
Flash relevant raw , without ticking wipe data in AFT.
Check my unbrick thread in my signature for AFT and links to raws
Enjoy
Click to expand...
Click to collapse
Yes, I still boot into TWRP.
I can't find my old backup for some reason, but after flashing the previously mentioned raw firmware I never up- or downgraded the ROM, so it MUST be that version. It's the only one I've ever downloaded and flashed.
IFWI version is 0094.0183
But so you are saying I could basically just flash [correct version FW].raw via AFT, without wiping data, and all should be good?
I am on your unbrick thread aws.
I will def bookmark it.
But I already have AFT and the same FW... so I could just go-go-go, right? Or is the IFWI version being M an issue?
Also, I downloaded the official Asus FW from their ZF2 website. In that .zip is in fact a "boot.img" - can I flash this via fastboot you think?
Thanks again for all your help!
You are unbelievable!
@dustylambo
0094.0183 is M
So flash a M raw.
You must've upgraded bootloader since flashing the last raw .139 which is LP to get to M bootloader .0183
In bootloader .0183
You flash raw for M, these have just been added by realyoti
drop him a thanks .
Flash without ticking wipe data in AFT
Damnit! I don't like where this is going... But it's late and I'm dumb
I never upgraded to M because I read that there were several apps that would lose support, MUSIC in particular, but there were others as well.
Will an M raw-file flash and still boot with all my old apps?
@dustylambo
It's simple really , what is the twrp build number ?
You never said
0094.0177
Is locked 5 LP bootloader.
.0173 is 5 unlocked bootloader
.0183 is M
What twrp build is yours ?
Ps , I don't think it matters which version raw you flash , only that it may fail and might have to wipe data to succeed which is better than what you have and are struggling with right now
gnite , enjoy
---------- Post added at 11:45 PM ---------- Previous post was at 11:30 PM ----------
Pls , remember the reason you installed twrp initially ?
For backing up
Sounds like you didn't only update Magisk Manager, you update Magisk itself. A non-signed Magisk update will always result in bootloop.
adobrakic said:
Sounds like you didn't only update Magisk Manager, you update Magisk itself. A non-signed Magisk update will always result in bootloop.
Click to expand...
Click to collapse
To be corrected: Not the Magisk, but the repacked boot.img. ?
Sent from my Redmi 3 using XDA Labs
Hi, recently I got this a32 from a friend because my phone is broken, but there's a problem. Some time ago she updated this phone from android 11 to 12 and the touchscreen completely stopped working, i got the phone yesterday hoping to fix this problem but i updated to android 13 (oneui 5.1) and it still doesnt work, i tried do downgrade to android 11 but its impossible and for last i tried to install twrp and then a gsi (following a guide here on the forum), i noticed that in twrp the touchscreen does actually work but after installing lineage os 20 it didn't again, is there any hope for this phone?
persifele said:
Hi, recently I got this a32 from a friend because my phone is broken, but there's a problem. Some time ago she updated this phone from android 11 to 12 and the touchscreen completely stopped working, i got the phone yesterday hoping to fix this problem but i updated to android 13 (oneui 5.1) and it still doesnt work, i tried do downgrade to android 11 but its impossible and for last i tried to install twrp and then a gsi (following a guide here on the forum), i noticed that in twrp the touchscreen does actually work but after installing lineage os 20 it didn't again, is there any hope for this phone?
Click to expand...
Click to collapse
Did you contacted the assistance? Seems a bad driver or kernel problem.
zSyntex said:
Did you contacted the assistance? Seems a bad driver or kernel problem.
Click to expand...
Click to collapse
no because i dont know how much it would cost and the phone isnt mine either so if possible i dont want to spend money
persifele said:
no because i dont know how much it would cost and the phone isnt mine either so if possible i dont want to spend money
Click to expand...
Click to collapse
We couldn't provide support for the hardware, mostly because you said that you've tried to reset the device and flash the stock ROM again.
If this doesn't fix the hardware issue, the assistance is the only way.
Probably a failure batch etc.
to be completely honest i flashed the stock rom by a backup i did before flashing lineage os, so if there's a guide on how to flash one ui 5.1 in order to have a clean installation it would be rlly helpful
persifele said:
to be completely honest i flashed the stock rom by a backup i did before flashing lineage os, so if there's a guide on how to flash one ui 5.1 in order to have a clean installation it would be rlly helpful
Click to expand...
Click to collapse
Simply download the latest firmware from SamLoader (Bifrost) and use Odin in order to flash it.
Tell me if you couldn't flash
I tried installing the latest firmware with odin, everything went fine but nothing, touch still doesn't work, i think tomorrow i'll take it to someone to fix it.
persifele said:
Hi, recently I got this a32 from a friend because my phone is broken, but there's a problem. Some time ago she updated this phone from android 11 to 12 and the touchscreen completely stopped working, i got the phone yesterday hoping to fix this problem but i updated to android 13 (oneui 5.1) and it still doesnt work, i tried do downgrade to android 11 but its impossible and for last i tried to install twrp and then a gsi (following a guide here on the forum), i noticed that in twrp the touchscreen does actually work but after installing lineage os 20 it didn't again, is there any hope for this phone?
Click to expand...
Click to collapse
what model of a32 is it? SM-A325F or??
One ui 5.1 firmware cannot be downgraded. I currently daily drive crdroid from nazim on one ui 5.1 firmware. my touch has never had issues. May be a hardware issue. Maybe a custom kernel would solve it. I built one for A325F that works on one ui 5.1 firmware. Give it a try from here. Its permissive btw. Just flash it in twrp. Although take a backup of boot before flashing incase something goes wrong
Captain_cookie_200 said:
what model of a32 is it? SM-A325F or??
One ui 5.1 firmware cannot be downgraded. I currently daily drive crdroid from nazim on one ui 5.1 firmware. my touch has never had issues. May be a hardware issue. Maybe a custom kernel would solve it. I built one for A325F that works on one ui 5.1 firmware. Give it a try from here. Its permissive btw. Just flash it in twrp. Although take a backup of boot before flashing incase something goes wrong
Click to expand...
Click to collapse
Hi, I tried to flash from twrp but it just gives me a series of "unable to unlock /dev/block/mmcblk0p14" and so on, btw yes its a A325F.
persifele said:
Hi, I tried to flash from twrp but it just gives me a series of "unable to unlock /dev/block/mmcblk0p14" and so on, btw yes its a A325F.
Click to expand...
Click to collapse
its fine. those are normal. if the flash suceeds at last that is all that matters
Captain_cookie_200 said:
its fine. those are normal. if the flash suceeds at last that is all that matters
Click to expand...
Click to collapse
The problem is that after flashing it goes in a bootloop where it says that "this phone's bootloader is unlocked, press power button" i do it and it starts the galaxy logo with above the writing "the software you are using isnt official, you may have problems with security and features" and it gets stuck there, rn i flashed the original firmware with odin and the phone is working but touch still isn't.
EDIT: i forgot to add that when i flashed with odin everything was going fine until the phone's screen went from green to red, i've never seen this so idk if i should be worried or not (phone is still running normally).
persifele said:
The problem is that after flashing it goes in a bootloop where it says that "this phone's bootloader is unlocked, press power button" i do it and it starts the galaxy logo with above the writing "the software you are using isnt official, you may have problems with security and features" and it gets stuck there, rn i flashed the original firmware with odin and the phone is working but touch still isn't.
EDIT: i forgot to add that when i flashed with odin everything was going fine until the phone's screen went from green to red, i've never seen this so idk if i should be worried or not (phone is still running normally).
Click to expand...
Click to collapse
oh weird . you are using one ui 5.1 right? whats the firmware name or version. Also those things def look like hardware issue. you should get it checked.
Captain_cookie_200 said:
oh weird . you are using one ui 5.1 right? whats the firmware name or version. Also those things def look like hardware issue. you should get it checked.
Click to expand...
Click to collapse
yes i'm on android 13 one ui 5.1, the firmware is A325FXXU3DWB8_A325FOXM3DWB8_ITV. I got it checked and they said that it cant be fixed because i cant downgrade from android 13 to another one, i could try installing crdroid like you and if you could send me a guide it would be amazing, thanks again.
persifele said:
yes i'm on android 13 one ui 5.1, the firmware is A325FXXU3DWB8_A325FOXM3DWB8_ITV. I got it checked and they said that it cant be fixed because i cant downgrade from android 13 to another one, i could try installing crdroid like you and if you could send me a guide it would be amazing, thanks again.
Click to expand...
Click to collapse
Just flash twrp for this thing from here. Follow steps on that thread to decrypt your storage and stuff. Then download crdroid gsi. Extract it. flash img file to system partition in twrp. Afterwards wipe dalvik, cache, internal storage
(internal storage is not necessary). You should be able to boot into twrp sucessfully.
I also have some workarounds and the stuff i use for my daily driving in this thread here.
If you need any further help i'll be here to assist.
Captain_cookie_200 said:
Just flash twrp for this thing from here. Follow steps on that thread to decrypt your storage and stuff. Then download crdroid gsi. Extract it. flash img file to system partition in twrp. Afterwards wipe dalvik, cache, internal storage
(internal storage is not necessary). You should be able to boot into twrp sucessfully.
I also have some workarounds and the stuff i use for my daily driving in this thread here.
If you need any further help i'll be here to assist.
Click to expand...
Click to collapse
Oh um i am sorry looks like thread doesnt contain instructions to that. I'll write em here myself
When you boot into twrp after flashing go to advanced and go to terminal
type
multidisabler
run it two times. Then go to format. Then press format data and type yes. Once its done reboot back into twrp again. Then flash crdroid as i said in my post above. and format the things i said. you should be able to boot into crdroid normally.
Captain_cookie_200 said:
Oh um i am sorry looks like thread doesnt contain instructions to that. I'll write em here myself
When you boot into twrp after flashing go to advanced and go to terminal
type
multidisabler
run it two times. Then go to format. Then press format data and type yes. Once its done reboot back into twrp again. Then flash crdroid as i said in my post above. and format the things i said. you should be able to boot into crdroid normally.
Click to expand...
Click to collapse
I followed everything you said, flashed crdroid but nothing, touch still doesnt work if not for when im twrp, i tried to flash kernel again and it still didn't so i don't know what to do anymore.
persifele said:
I followed everything you said, flashed crdroid but nothing, touch still doesnt work if not for when im twrp, i tried to flash kernel again and it still didn't so i don't know what to do anymore.
Click to expand...
Click to collapse
So uh looks like you have no options left. I just want to make sure. could you list the exact methods you used to flash the fw. Along with where u got the fw from? Lets see if the fw itself is broken or something.
Also this is very unrelated and time wasting. but you could try download one ui 5 firmware. Then extract super.img from ap. unsparse it and extract vendor.img and flash it to vendor partition using twrp. Then decrypt by typing
multidisabler twice in terminal as said in my previous post. Check if maybe an older version one ui 5 firmware has this issue fixed. one ui 5's kernel boots so one ui 5 vendor should work on 5.1 as well. It may not work but worth a try. you could also try doing this with android 12 firmware if that fixes it. if you do not have a linux machine availible i'll do it for you and upload the files for both firmwares here. Otherwise if its a hardware issue get your phone replaced or try getting the screen replaced. if still nothing happens ig switching to a new phone would be the only optiion.
So, to flash the firmware I used odin, the fw was from sammobile.
For trying to extract super.img and so on idk how to actually do it so if you could explain it would be really helpful. Btw trying to flash android 12 firmware is impossible because samsung made it so,
thank you again for the help.
persifele said:
So, to flash the firmware I used odin, the fw was from sammobile.
For trying to extract super.img and so on idk how to actually do it so if you could explain it would be really helpful. Btw trying to flash android 12 firmware is impossible because samsung made it so,
thank you again for the help.
Click to expand...
Click to collapse
i use samfw mostly for my firmwares. anyways. You need a linux machine nearby. ubuntu or arch. any distro based on them would work.
first you need to unsparse the super.img
for that we use
simg2img super.img super-raw.img
then we can use lpunpack or mount it to get our vendor.
we flash it using twrp and then we run multidisabler twice like we did when we first flashed gsi.
As you said above if you could do it for me it'd be awesome because i don't have a pc with linux rn.