Related
hi everyone, i've a totally noobish and technologically dumb question, you know there are partitions in android like /system and /sdcard etc etc, now my question is that is the /system partition write protected on an unrooted phone? can /system files be modified on an unrooted phone? i have an unrooted phone and i can view the system partition via a file manager but i dont know if i can modify it or not. Does rooting the phone remove the write protection? plus, i have s off, can having s off disable the write protection, if there is any on the android /system partition? thanks in advance
muhammad.uzi1994 said:
hi everyone, i've a totally noobish and technologically dumb question, you know there are partitions in android like /system and /sdcard etc etc, now my question is that is the /system partition write protected on an unrooted phone? can /system files be modified on an unrooted phone? i have an unrooted phone and i can view the system partition via a file manager but i dont know if i can modify it or not. Does rooting the phone remove the write protection? plus, i have s off, can having s off disable the write protection, if there is any on the android /system partition? thanks in advance
Click to expand...
Click to collapse
pretty much NO, to all your questions.
what you need to be able to modify /system
1- a kernel with write-protection disabled
2- root access with /system mounted as read/write, you can achieve this in more than one way, two possible methods:
A) don't want to root the ROM?: flash a custom recovery, and use adb shell commands, a recovery file manager (TWRP has one), or Aroma File Manager
or
B) root the ROM
nkk71 said:
pretty much NO, to all your questions.
what you need to be able to modify /system
1- a kernel with write-protection disabled
2- root access with /system mounted as read/write, you can achieve this in more than one way, two possible methods:
A) don't want to root the ROM?: flash a custom recovery, and use adb shell commands, a recovery file manager (TWRP has one), or Aroma File Manager
or
B) root the ROM
Click to expand...
Click to collapse
once again, you summed it up really good, i understand the write protection thing now, so basically it depends on kernel and root access/custom recovery file manager
muhammad.uzi1994 said:
once again, you summed it up really good, i understand the write protection thing now, so basically it depends on kernel and root access/custom recovery file manager
Click to expand...
Click to collapse
yes stock kernel has write-protection enabled, so any changes you do with ROOT, will be gone as soon as you reboot.
nkk71 said:
yes stock kernel has write-protection enabled, so any changes you do with ROOT, will be gone as soon as you reboot.
Click to expand...
Click to collapse
i have stock kernel and i'm unrooted, i guess i cant make changes in /system at all. Well, everyday i learn something new about Android, i'll mark this thread as solved
nkk71 said:
.............
Click to expand...
Click to collapse
You seem to know much about android
1) Can tell me why a message is displayed on top every time I reboot or poweron (on the logo screen) "write protection : kernel".
2) Is it an indication that I have unlocked by bootloader ? While rebooting it stays on that screen for 60-65 sec since I did rooted with Magisk (usually takes 7 secs before doing with Magisk-[message wasnt there at that time] )
3) What does it mean ? It came after I rooted with Magisk....
4) Does it mean I wont be able to go back to stock in the future using odin.
Im using SM-G503FZ. (5.0.2), Grand Prime
---------- Post added at 04:10 PM ---------- Previous post was at 03:12 PM ----------
nkk71 said:
yes stock kernel has write-protection enabled, so any changes you do with ROOT, will be gone as soon as you reboot.
Click to expand...
Click to collapse
Please reply to my above post.
mdmaher said:
Im using SM-G503FZ. (5.0.2), Grand Prime
Click to expand...
Click to collapse
You should ask in your device forum, this is HTC One M7 forum.
Need assistance
I unlocked my asus zenfone max pro m1 , when restarted its stuck in boot logo so I tried to flash a recovery and also a custom rom but it says write protected. I erased system in fastboot mode but unable to do anything other than entering into fastboot mode. can anyone help me to bypass write protection and flash a new rom or recovery to get my phone back in to the working state. Any help would be appreciated. Thank you guys...
hello ppls
when i install mods on the recovery like "fly on mod" or "PurePerfomance X"
the recovery give me error status 7 any help please ?
iSpammer said:
hello ppls
when i install mods on the recovery like "fly on mod" or "PurePerfomance X"
the recovery give me error status 7 any help please ?
Click to expand...
Click to collapse
I've been given this link, it did not work for me but nevertheless, it's worth a try
http://forum.xda-developers.com/showthread.php?t=2302599
peter-k said:
I've been given this link, it did not work for me but nevertheless, it's worth a try
http://forum.xda-developers.com/showthread.php?t=2302599
Click to expand...
Click to collapse
nothing work :s
while flashng the mod it say
Fixing permissions
set_perm : some changes failed
E: Error in /storage/sdcard0/bluetooth/signed_fly-on_mod__v4.0-beta6.zip
(Status 7)
installation aborted
press any key to continue
iSpammer said:
nothing work :s
while flashng the mod it say
Fixing permissions
set_perm : some changes failed
E: Error in /storage/sdcard0/bluetooth/signed_fly-on_mod__v4.0-beta6.zip
(Status 7)
installation aborted
press any key to continue
Click to expand...
Click to collapse
I don't think it would be a problem with the updater-script, but on the other hand, you could try changing recoveries. Honestly, I wouldn't think this is the problem; I've flashed just about everything using different recoveries, and the only time I've had problems is with what @peter-k posted.
Then again, it's not like you're flashing a ROM or replacing system files, so you could always copy the files manually with Root Explorer and correct permission.
Also, since your problem is at a permission level, you might just have to fix permission (Root Explorer).
Open a terminal emulator (or ADB) and type:
Code:
su
Fly-On
That should tell you if it's installed or not, regardless of the error you got in recovery.
Maybe you'd want to try with the RC1, instead of the Beta version. I just flashed it and got no errors (CWM 6.0.5.0), although both updater scripts are identical except for the "delete("/system/etc/init.d/03kill_media_server");" line.
What ROM are you on?
Antiga Prime said:
Maybe you'd want to try with the RC1, instead of the Beta version. I just flashed it and got no errors (CWM 6.0.5.0), although both updater scripts are identical except for the "delete("/system/etc/init.d/03kill_media_server");" line.
What ROM are you on?
Click to expand...
Click to collapse
thanks i will try it now
i am on stock rom 4.3 locked bootloader , i am using an app called "Universal int.d" for int.d script support
edit : dosnt work also
even when downloading and installing the cwm v8 for locked bootloader i get the same error :/
iSpammer said:
thanks i will try it now
i am on stock rom 4.3 locked bootloader , i am using an app called "Universal int.d" for int.d script support
edit : dosnt work also
even when downloading and installing the cwm v8 for locked bootloader i get the same error :/
Click to expand...
Click to collapse
Well then don't flash it, copy the files manually and set permissions manually, there aren't that many files.
Files in /system/etc/rngd and /data/Fly-On should be assigned to user/group: root/shell, permissions: rwxrwxrwx.
Every other file should have user/group set to: root/root, and same permissions as before.
Antiga Prime said:
Well then don't flash it, copy the files manually and set permissions manually, there aren't that many files.
Files in /system/etc/rngd and /data/Fly-On should be assigned to user/group: root/shell, permissions: rwxrwxrwx.
Every other file should have user/group set to: root/root, and same permissions as before.
Click to expand...
Click to collapse
thanks you
Hey there,
in the p7 bootloop thread I told you about that i deleted all (!) in / by twrp File Manager
It even deleted my sd card (argh).
Since then the phone constantly reboots and it's showing a green android logo with silver lens flare and boots up into OS and reboots.
Doesn't matter which OS I flash or fastboot. Even TWRP reboots but Just 2.8.x.x. The only stable one is 2.7.1.0 (!!)
More and detailed information by me and other users here: http://forum.xda-developers.com/showpost.php?p=57536337&postcount=29
This brings to me to the idea to push the original Files of everything by another user into my phone. Maybe it will then work again and help the other's to do so as well!
I need someone who uploads the original Files of a working P7-L10 phone with TWRP with the TWRP FIle Manager.
Im not interested in System and Data Files! So i don't need personal data. Im talking about all the other folders
TWRP -> Advanced -> File Manager -> for example: dev, dsp0, etc, licence, mnvm1:0, mnvm2:0, proc etc.....
I will report my progress then and mabye this will bring the phone to life again. Since the Bootlogo is missing I assume there are missing files even when flashing back system.img recovery.img and so on!
Im reporting my progress then! Your benefit would be the information and a fall back for yourself too!
Otherwise i'm sending it for repair to HUAWEI.
regards,
ManuelHH
By the way.... if you extract the dload with the huawei extractor tools... I get some more files like dsp.img.
But I can't flash them:
fastboot flash dsp dsp.img
sending `dsp´
okay
writing dsp
failed (remote: command not allowed)
finished.
So if I could decompress the other files and but them into my phone by twrp or could flash them otherwise this might help too?
Just another idea.
Otherwise I still hope another user can help by providing his files or some other Guru with another option
Okaay, i decompressed some .img Files and put them back manually for example: system.img... now the huawei bootlogo is up there again!
But I've still got a lot of empty folders like dsp etc mnvm0: and so on and i can't decompress dsp.img and other files. So If someone could please upload everything from a working P7 it would be highly appriciated.... (just copy to sd card, compress and upload). Thanks!
Google has no answer for me.
Every time I enter into the recovery and push the message button I get this ERROR: 2.
Everything works fine, its latest TWRP 3.0.2.
Could you tell me something about this error message 2?
What is 'postrecoveryboot.sh'?
How can I get this red message off / without error?
thanx in advance
How do I edit my boot script?
MichaBit said:
Google has no answer for me.
Every time I enter into the recovery and push the message button I get this ERROR: 2.
Everything works fine, its latest TWRP 3.0.2.
Could you tell me something about this error message 2?
What is 'postrecoveryboot.sh'?
How can I get this red message off / without error?
thanx in advance
Click to expand...
Click to collapse
Hi,
I have the same problem. Also on TWRP 3.0.2. and everything seems to work.
Can't find anything about this 'postrecoveryboot.sh' Error 2.
Did you find a solution in the meantime?
Thanks for any help in advance.
Arninho said:
Did you find a solution in the meantime?
Click to expand...
Click to collapse
No, unfortunately not.
If XDA has no solution, who else?
I have the same problem, this is inside the file
Code:
#!/sbin/sh
# Include device-specific vars
source /sbin/bootrec-device
# Turn the LED off
echo 0 > ${BOOTREC_LED_RED}
echo 0 > ${BOOTREC_LED_GREEN}
echo 0 > ${BOOTREC_LED_BLUE}
that error is because this file bootrec-device located at sbin folder always missing when reboot system or recovery
I have try many way
-flash stock rom with flashtool
-flash rom via recovery
-wipe via adb and fastboot
-chmod this file bootrec-device to read only
-remove this file postrecoveryboot.sh just come back after reboot recovery
all that way doesn't work
my Xperia unable to boot right know :crying:
maybe i'll try search what's file that create this??? postrecoveryboot.sh
where's boot script locate???
any help would be apreciated
InAMovies said:
my Xperia unable to boot right know :crying:
Click to expand...
Click to collapse
Thanks for that much information. :good:
A possible 'emergency solution' so that your device reboots again could be attached link.
What really surprised me, no one else has this ERROR: 2, and if not, why not?
http://www.flashtool.net/index.php
You can fix this 'postrecoveryboot.sh' Error 2 with a lower version twrp
I use twrp 2.8.7 which has been uploaded by someone from here androidfilehost.com/?fid=24052804347811669
flash with "fastboot flash boot boot.img" only if you UB, on LB try downgrade your twrp version
and then via file manager, just chmod the file bootrec-device located at sbin folder with read only access
my phone can only be booted only with rom existenz, and it was frequently rebooted and my battery status is unclear, sometimes 65% during the initial boot, and then only a 5% reboot afterwards
I have flash using flashtool with many based rom from 10.5.1.A, 10.6.1.A, 10.7.1.A latest, but it still does not make my phone work just to show sony screen flickered and died with the indicator is still red
all the problems occurred after I had this problem 'postrecoveryboot.sh' Error 2
I still do not know how to turn off the script, when I delete the file after reboot definitely go back there
hoping my phone can be normal again sometime
InAMovies said:
I still do not know how to turn off the script, when I delete the file after reboot definitely go back there
Click to expand...
Click to collapse
Could the cause for the error be a kind of provider branding?
So deeper implemented than the usual firmware.
My device was delivered via German Telekom.
[B]Solution![/B]
After installing Multirom v33 the error message is gone!
Dont ask why, both recoverys, the new one into the FOTA partition from attached link und the older, normal one 3.0.2.0 are error-free! :good:
https://forum.xda-developers.com/xperia-z/orig-development/mod-multirom-v33x-xperia-z-t3432385
I have installed the Modified recovery FOTA, before this error happen all working fine any custom rom working
but after this error, i can boot into recovery and install rom then reboot got bootloop, charger just show blip screen logo
just wanna try your idea with the Multirom v33 non modified
MichaBit said:
Google has no answer for me.
Every time I enter into the recovery and push the message button I get this ERROR: 2.
Everything works fine, its latest TWRP 3.0.2.
Could you tell me something about this error message 2?
What is 'postrecoveryboot.sh'?
How can I get this red message off / without error?
thanx in advance
Click to expand...
Click to collapse
Can You be so Kind to tell me how to flash in the correct way the latest version of TWRP with no error? Thank You very much!!
Ricky_Karmator said:
Can You be so Kind to tell me how to flash in the correct way the latest version of TWRP with no error? Thank You very much!!
Click to expand...
Click to collapse
Download latest recovery 'twrp-3.0.2-0-yuga.img' from link 1.
Put it to your Phone, turn of, push volume + and insert USB-cable for flashmode.
Blue LED-light appears.
Type -fastboot flash boot boot.img
-fastboot reboot
in ADB-connection CMD on your PC --> thats all.
Optional you can use the Tool in link 2.
*Flashing recovery successfully*
https://dl.twrp.me/yuga/
https://twrp.me/app/
MichaBit said:
Download latest recovery 'twrp-3.0.2-0-yuga.img' from link 1.
Put it to your Phone, turn of, push volume + and insert USB-cable for flashmode.
Blue LED-light appears.
Type -fastboot flash boot boot.img
-fastboot reboot
in ADB-connection CMD on your PC --> thats all.
Optional you can use the Tool in link 2.
*Flashing recovery successfully*
https://dl.twrp.me/yuga/
https://twrp.me/app/
Click to expand...
Click to collapse
I wa sure to copy the .img file in "platform-tools" folder in my PC and with cmd type "-fastboot flash boot boot.img" and not to have the file inside the internal memory of my Xperia Z. Obviously i think to rename "Twrp-3.0.blablabla" into boot.img
Ricky_Karmator said:
I wa sure to copy the .img file in "platform-tools" folder in my PC and with cmd type "-fastboot flash boot boot.img" and not to have the file inside the internal memory of my Xperia Z. Obviously i think to rename "Twrp-3.0.blablabla" into boot.img
Click to expand...
Click to collapse
Yes, very correct, copy and rename the file into 'boot.img' to your ADB-folder and flash it. :angel:
Finally with some free time i unlocked and flash the latest TWRP on my old Xperia Z. And yes i've got the same error "ERROR: 2". But everything works from backup to restore and flash Custom ROM. So i think we can nevermind about that
I have the same.
Sometimes my phone randomly reboot, and seems to be some app cause this reboots.
It was happend more and more often. And suddenly couple days ago my phone start to bootloop (just endlesly booting at xperia logo).
I have F5121 stock 8.0 Oreo and done all like in this manual https://forum.xda-developers.com/t/...els-latest-34-4-a-2-118-25-sept-2018.3594502/
So I was have rooted kenrnel twrp 3.2.3.0+DRM-Fix +magisk +FCS_1.3 +debloat script.
Almost 2 years of no problems and this surprise.
When I load to twrp and press menu button i see this:
Updating partition details...
...done
Unable to mount storage
So I was trying do backup of all partitions and after that I go in in wipe menu => advanced wipe => checkbox cache partition => fix patition
than I try to fix all patitions - it doesn't help.
So I do this:
wipe menu => advanced wipe => checkbox data partition => change to exFAT filesystem then => change back to EXT4 filesystem and restore data from backup. And do system/data partitions
and try to restore my backup - and it don't work.
EVEN my older backups don't works - I always become bootloop on xperia logo.
When I download twrp backup to PC and unpack cache.ext4.win\recovery I see file with name last_log.
Thats how last strings of file last_log look like:
~
ro.bootimage.build.date.utc=1533015130
ro.bootimage.build.fingerprint=Sony/omni_suzu/suzu:8.1.0/OPM4.171019.021.R1/4:eng/test-keys
ro.bootloader=s1
ro.debuggable=1
ro.property_service.version=2
init.svc.adbd=running
init.svc.ueventd=running
init.svc.recovery=running
init.svc.ldconfigtxt=stopped
init.svc.set_permissive=stopped
twrp.crash_counter=0
keyguard.no_require_sim=true
tombstoned.max_tombstone_count=50
Running boot script...
I:/sbin/postrecoveryboot.sh process ended with RC=0
Done.
I would like to hear some ideas why that may happen (Unable to mount storage). Coz i lost part of my data and don't wanna have the same experience again and again in future.
Hi guys,
I tried to root my P9 today but now I'stuck with a bricked P9.
I can fastboot and use TWRP
The main problem is that I get always failed to mount /data (Invalid argument)
I've tried to Change the file system with TWRP and Format Data but nothing
I've tried the unbrick procedure with Multi-Tool and an old firmware but nothing
Code:
19:21:37: Unbricking started. Your computer may freezes during the process.
19:21:37: flash boot "C:\Users\franc\Desktop\Nuova cartella\boot.img"
19:21:37: The Boot image is flashing successfully
19:21:37: flash system "C:\Users\franc\Desktop\Nuova cartella\system.img"
19:21:53: target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (449861 KB)...
OKAY [ 10.490s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 10.551s
19:21:53: Error#1
19:21:53: flash cust "C:\Users\franc\Desktop\Nuova cartella\cust.img"
19:21:58: Error! You are trying to flash the wrong image!
19:21:58: flash recovery "C:\Users\franc\Desktop\Nuova cartella\recovery.img"
19:22:00: The Recovery image is flashing successfully
19:22:00: Completed
19:22:00: Something went wrong (((
bomba697 said:
Hi guys,
I tried to root my P9 today but now I'stuck with a bricked P9.
I can fastboot and use TWRP
The main problem is that I get always failed to mount /data (Invalid argument)
I've tried to Change the file system with TWRP and Format Data but nothing
I've tried the unbrick procedure with Multi-Tool and an old firmware but nothing
Code:
19:21:37: Unbricking started. Your computer may freezes during the process.
19:21:37: flash boot "C:\Users\franc\Desktop\Nuova cartella\boot.img"
19:21:37: The Boot image is flashing successfully
19:21:37: flash system "C:\Users\franc\Desktop\Nuova cartella\system.img"
19:21:53: target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (449861 KB)...
OKAY [ 10.490s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 10.551s
19:21:53: Error#1
19:21:53: flash cust "C:\Users\franc\Desktop\Nuova cartella\cust.img"
19:21:58: Error! You are trying to flash the wrong image!
19:21:58: flash recovery "C:\Users\franc\Desktop\Nuova cartella\recovery.img"
19:22:00: The Recovery image is flashing successfully
19:22:00: Completed
19:22:00: Something went wrong (((
Click to expand...
Click to collapse
"P9" - EMUI 4 / Android MM, EMUI 5 / N or EMUI 8 / O
What was exacrly your full firmware name and number (like EVA-L09c532b505 or what)
"TWRP" - which/where from?
(diff TWRP installations must be used for MM, N or N), and if TWRP from TWRP site - that one is definitely not good for N and O
"root" - by SuperSU, Magisk or something else (hopefully not King.... tools or so)
So, from which Huawei firmware did you start, which steps did you perform and by which tools
Btw, rooting N by SuperSU or O by Magisk is pretty straightforward, but is important that proper, corresponding TWRPs are used.
And if anything goes wrong (brick or so) stock Boot partition (N) or stock Ramdisk partition (O) can be easily flashed over to go back
zgfg said:
"P9" - EMUI 4 / Android MM, EMUI 5 / N or EMUI 8 / O
What was exacrly your full firmware name and number (like EVA-L09c532b505 or what)
"TWRP" - which/where from?
(diff TWRP builds must be used for MM, N or N), and if TWRP from TWRP site - that one is definitely not good for N and O
"root" - by SuperSU, Magisk or something else (hopefully not King.... tools or so)
So, from which Huawei firmware did you start which steps did you perform and by which tools
Btw, rooting N by SuperSU or M by Magisk is pretty straightforward, but it is important that proper corresponding TWRPs are used.
And if anything goes wrong (brick or so) stock Boot partition (N) or stock Ramdisk partition (O) can be easily flashed over to go back
Click to expand...
Click to collapse
I'm sorry for the poor description but I was in panic.
Starting from EVA-L09C432B3xx, don't remember the exact version, N 5.0.1
TWRP 3.1.0.-1
SuperSU, https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258. I had big trouble trying to root because every time the phone rebooted before finishing the procedure.
I didn't use any tool at all for unlocking bootloader, flash recovery and root. Just adb and fastboot in cmd + TWRP.
BTW, I recovered the phone! Used DC-Phoenix to reset the phone from fastboot and then made a downgrade to b182.
PS: Why did you flash Cust?
For TWRP or to go back to stock Recovery, you only need to flash recovery (for N) or ramdisk_recovery (for O)
To flash root patch for SuperSU for N (or to restore back) you only need to flash boot partition, similarly for Magisk (O) ramdisk partution.
zgfg said:
PS: Why did you flash Cust?
For TWRP or to go back to stock Recovery, you only need to flash recovery (for N) or ramdisk_recovery (for O)
To flash root patch for SuperSU for N (or to restore back) you only need to flash boot partition, similarly for Magisk (O) ramdisk partution.
Click to expand...
Click to collapse
Because Multi-Tool 8 was asking to flash also CUST to apply unbrik procedure.
The problem was that I wasn't able to mount /data partition. Also from stock recovery I wasn't able to format /data, only wipe the cache
bomba697 said:
Because Multi-Tool 8 was asking to flash also CUST to apply unbrik procedure.
The problem was that I wasn't able to mount /data partition. Also from stock recovery I wasn't able to format /data, only wipe the cache
Click to expand...
Click to collapse
If you recovered and if you are on b182 now, you will hopefully receive OTA upgrades tp go back to N
Btw, working procedure for rooting N was described in thread
https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258
Again, if TWRP was not able to mount Data, was it really proper TWRP from XDA Huawei Nougat threads (adapred to support Huawei N and its encryption), like
https://forum.xda-developers.com/p9/development/twrp-t3565703
Some other TWRP 3.1.x.x, even declared for Huawei, maybe good for EMUI 4 / MM but not for EMUI 5 / N
EDIT: noticed that you fixed it through DC-Phoenix. Do you have a link where you found it and how to use? I don't mind downgrading coz I'm just gonna use the phone as a backup phone
I got the same issue. If you find an answer please tag me. I think i was using EVA-L19C636B180 Quite sure about the C636 part. TWRP 3.1.0.-3 and using SU but I can't recall the version
Quick background on mine:
I bricked my phone when I did a factory reset and deleted internal storage and accidentally deleted important files while doing so. I flashed a stock update from the warehouse and completely deleted the system instead. I then flashed Lineage ROM which reinstalled the system but now causes me to get stuck in bootup. When I installed Lineage ROM, I got the following error.
Attached photo
https://imgur.com/a/nx6U5bC
kazshizka said:
EDIT: ...DC-Phoenix. Do you have a link and how to use...
Click to expand...
Click to collapse
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
kazshizka said:
EDIT: noticed that you fixed it through DC-Phoenix. Do you have a link where you found it and how to use? I don't mind downgrading coz I'm just gonna use the phone as a backup phone
I got the same issue. If you find an answer please tag me. I think i was using EVA-L19C636B180 Quite sure about the C636 part. TWRP 3.1.0.-3 and using SU but I can't recall the version
Quick background on mine:
I bricked my phone when I did a factory reset and deleted internal storage and accidentally deleted important files while doing so. I flashed a stock update from the warehouse and completely deleted the system instead. I then flashed Lineage ROM which reinstalled the system but now causes me to get stuck in bootup. When I installed Lineage ROM, I got the following error.
Attached photo
https://imgur.com/a/nx6U5bC
Click to expand...
Click to collapse
I didn't use the method posted by @zgfg. What I did was: (this procedure is going to lock back your FRP setting and bootloader, so you can try it but at your own risk)
Use Multi-Tool 8 (https://forum.xda-developers.com/honor-8/development/tool-huawei-multi-tool-team-mt-t3523923) to reinstall stock recovery and recovery2
Download https://www.dc-unlocker.com/downloads/get/jvObBBIo
Put the phone in fastboot
Use the FRP Erase option to recover/format /data (it cost you 15 credit, $15), it was successful
Take empty SD card formatted in NFTS
Put in dload folder the rollback UPDATE.APP file taken from http://download-c1.huawei.com/download/downloadCenter?downloadId=92765&siteCode=it and install it
Last, put in dload folder b182 UPDATE.APP file from http://download-c1.huawei.com/download/downloadCenter?downloadId=91783&siteCode=it
This functioned for me, you can try to skip step 5 and install directly b182.
zgfg said:
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
Click to expand...
Click to collapse
bomba697 said:
I didn't use the method posted by @zgfg. What I did was: (this procedure is going to lock back your FRP setting and bootloader, so you can try it but at your own risk)
Use Multi-Tool 8 (https://forum.xda-developers.com/honor-8/development/tool-huawei-multi-tool-team-mt-t3523923) to reinstall stock recovery and recovery2
Download https://www.dc-unlocker.com/downloads/get/jvObBBIo
Put the phone in fastboot
Use the FRP Erase option to recover/format /data (it cost you 15 credit, $15), it was successful
Take empty SD card formatted in NFTS
Put in dload folder the rollback UPDATE.APP file taken from http://download-c1.huawei.com/download/downloadCenter?downloadId=92765&siteCode=it and install it
Last, put in dload folder b182 UPDATE.APP file from http://download-c1.huawei.com/download/downloadCenter?downloadId=91783&siteCode=it
This functioned for me, you can try to skip step 5 and install directly b182.
Click to expand...
Click to collapse
Will check out both methods. I'll try it through TWRP first since it should be easier to use an open bootloader rather than a locked one.
@bomba697 will reinstalling stock recovery fix my deleted system issue? coz I'm not sure if I flashed the custom ROM properly anymore
UPDATE:
Tried @bomba697 method and fixed my system but I skipped the FRP Erase portion. I just installed the stock recovery straight (thus not paying 15 credits) from the multi tool then rollback using dload then update to b182. Though it did change my system to C900 from C636.
Thank you very very much!!
kazshizka said:
UPDATE:
Tried @bomba697 method and fixed my system but I skipped the FRP Erase portion. I just installed the stock recovery straight (thus not paying 15 credits) from the multi tool then rollback using dload then update to b182. Though it did change my system to C900 from C636.
Thank you very very much!!
Click to expand...
Click to collapse
Happy that you found the solution! I tried directly flashing the rom but I wasn't able beacuse of the \data mount error.