I got my phone a few days ago and rooted it, installed most stuff etc.. So far I have TWRP and Magisk 14.0 Root active on it, not much else I can think of. The phone is running Android 7.0.
I left the Camera for last to check and when I did I noticed neither the camera nor its flash are responding. ("camera busy" error, other full-fledged cam apps showing black) I went through the initial steps of disabling OK Google's camera settings, disabling a bunch of apps that had cam access, checking safe mode etc. and none of them worked.
Finally I went into Device Helper's hardware list and noticed under "Imaging" there isn't even a camera listed. I don't know how the app works but even with cam busy it would at least be listed. I went through a few other hardware spec listing apps and all of them showed absolutely no camera hardware. Interesting enough, I know the phone has 2 cameras, I'm not sure if they're a single unified piece of hardware or not but there was no such thing as back or front camera even, there was quite simply nothing listed under camera.
At this point I'm left to wonder if the problem is either a setting or something to do with rooting, or actual hardware fault. Unfortunately having rooted the device, I also have no warranty for it.
I welcome any ideas, advices, anything about trying to detect or diagnose camera issues. If there were a TWRP way of checking the camera hardware, I'd be glad to try it out since it would rule out anything having related to the Android OS, or other versions of Magisk. 11.6 was recommended but it never worked for me. This is all before I open up the phone. I can't much afford much to do a factory reset at this point and would like to leave it as the last resort.
In the event of a camera issue, I'm of course hoping it's as simple as a loose connector, but I'd like to know of any known G5 hardware issues with the camera and if there's documented fixes.
Also in the event I DO have to do a hard reset - do I have a reliable way of backing up absolutely everything about the phone's current state(apps settings documents etc.) and restoring it all back?
I just spent good money on this phone, thank you for all advice!
Are you using stock rom or a custom rom?
You can use magisk uninstaller to remove magisk to see if that caused an issue (see magisk v14.0 thread)
In some custom roms some people did report camera stopped working - Iv never had this issue
I'm using LineageOS with the built in superuser via the su add on zip
In terms of the camera itself hardware wise & on unmodified stock there are no reported issues
TheFixItMan said:
Are you using stock rom or a custom rom?
You can use magisk uninstaller to remove magisk to see if that caused an issue (see magisk v14.0 thread)
In some custom roms some people did report camera stopped working - Iv never had this issue
I'm using LineageOS with the built in superuser via the su add on zip
In terms of the camera itself hardware wise & on unmodified stock there are no reported issues
Click to expand...
Click to collapse
Not using a custom ROM.
I went to the Magisk page where I got the install, got "latest uninstaller", ran it. It reported success but warned that no boot image backup was found. On restart it hanged indefinetly at the 5-second untrusted device warning. Did a hard poweroff and on, same result. I ended up installing the 14.0 back and the device again boots. I also did a dump of the boot logs.
In dmesg.log I see this:
Code:
<3>[ 5.684036,2] msm_camera_pinctrl_init:1277 Getting pinctrl handle failed
Code:
<3>[ 5.676660,2] msm_flash_get_pmic_source_info:895 alternate current: read failed
<3>[ 5.676664,2] msm_flash_get_pmic_source_info:915 alternate max-current: read failed
<3>[ 5.676667,2] msm_flash_get_pmic_source_info:935 alternate duration: read failed
<3>[ 5.676710,2] msm_flash_get_pmic_source_info:895 alternate current: read failed
<3>[ 5.676714,2] msm_flash_get_pmic_source_info:915 alternate max-current: read failed
<3>[ 5.676717,2] msm_flash_get_pmic_source_info:935 alternate duration: read failed
<3>[ 5.676760,2] msm_flash_get_pmic_source_info:1005 alternate current: read failed
<3>[ 5.676763,2] msm_flash_get_pmic_source_info:1025 alternate current: read failed
<3>[ 5.676806,2] msm_flash_get_pmic_source_info:1005 alternate current: read failed
<3>[ 5.676810,2] msm_flash_get_pmic_source_info:1025 alternate current: read failed
and respectively this:
Code:
<3>[ 5.664800,0] msm_camera_get_dt_vreg_data:1115 number of entries is 0 or not present in dts
I'm no expert reading these logs, is this signalling my issue?
Also this is from the non-working boot, near the end of the log:
Code:
>[ 33.292450,5] FAT-fs (mmcblk1p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
SearinoxNavras said:
Not using a custom ROM.
I went to the Magisk page where I got the install, got "latest uninstaller", ran it. It reported success but warned that no boot image backup was found. On restart it hanged indefinetly at the 5-second untrusted device warning. Did a hard poweroff and on, same result. I ended up installing the 14.0 back and the device again boots. I also did a dump of the boot logs.
In dmesg.log I see this:
Code:
<3>[ 5.684036,2] msm_camera_pinctrl_init:1277 Getting pinctrl handle failed
Code:
<3>[ 5.676660,2] msm_flash_get_pmic_source_info:895 alternate current: read failed
<3>[ 5.676664,2] msm_flash_get_pmic_source_info:915 alternate max-current: read failed
<3>[ 5.676667,2] msm_flash_get_pmic_source_info:935 alternate duration: read failed
<3>[ 5.676710,2] msm_flash_get_pmic_source_info:895 alternate current: read failed
<3>[ 5.676714,2] msm_flash_get_pmic_source_info:915 alternate max-current: read failed
<3>[ 5.676717,2] msm_flash_get_pmic_source_info:935 alternate duration: read failed
<3>[ 5.676760,2] msm_flash_get_pmic_source_info:1005 alternate current: read failed
<3>[ 5.676763,2] msm_flash_get_pmic_source_info:1025 alternate current: read failed
<3>[ 5.676806,2] msm_flash_get_pmic_source_info:1005 alternate current: read failed
<3>[ 5.676810,2] msm_flash_get_pmic_source_info:1025 alternate current: read failed
and respectively this:
Code:
<3>[ 5.664800,0] msm_camera_get_dt_vreg_data:1115 number of entries is 0 or not present in dts
I'm no expert reading these logs, is this signalling my issue?
Also this is from the non-working boot, near the end of the log:
Code:
>[ 33.292450,5] FAT-fs (mmcblk1p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Click to expand...
Click to collapse
Here is the original stock boot.img if you need to flash it after removing magisk
Stock boot image
You need to put your phone in bootloader mode & connect to pc via usb
Open a command/terminal prompt at your fastboot location
Code:
fastboot flash boot boot.img
Substitute boot.img for the name of your boot.img if different but I think I named it boot.img
You may have to flash the entire stock firmware & start again or try flashing Linageos
You can also try erasing user data by typing
Code:
fastboot erase userdata
But note this will erase all data from phone including anything in internal storage like photos music downloads etc (only data partition not system so phone will boot as if new)
The boot.img you sent me and the one I have both have the same hashes. So I was at least doing that right.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.518s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.739s]
finished. total time: 1.258s
Is "bad key" normal? Now the 5-second untlocked untrusted warning says ID: bad key instead of N/A. Sadly, the device behaves the same. It hangs indefinetly at that one screen. Maybe something's off with the uninstaller; if I wanted to manually -disable- magisk by renaming say one file or folder that is an entry point, how would I do that?
I checked the boot logs again, and I'm still seeing the same camera stuff mentioned there, so I don't know if it fixed anything since I can't boot but it doesn't look different.
I uploaded the files here: https://drive.google.com/file/d/0B5_lN_xRgoTVTUZZX0ZaWmZGNkE/view
Please tell me if there's anything there shouldn't be about the camera in them.
Once I reinstall Magisk, the ID at the boot splash warning goes back to N/A. Funny enough it -does- say it's found a stock boot image and it's backing it up when you install, but on uninstall it never finds it.
If I were to try a stock reflash or another fw, do I have a way to image absolutely everything and if I want, to restore it back as if it never changed?
I forgot to mention that when I installed TWRP I also installed no-verity-opt-encrypt-5.1.zip. Does this have anything to do with it?
SearinoxNavras said:
The boot.img you sent me and the one I have both have the same hashes. So I was at least doing that right.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.518s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.739s]
finished. total time: 1.258s
Is "bad key" normal? Now the 5-second untlocked untrusted warning says ID: bad key instead of N/A. Sadly, the device behaves the same. It hangs indefinetly at that one screen. Maybe something's off with the uninstaller; if I wanted to manually -disable- magisk by renaming say one file or folder that is an entry point, how would I do that?
I checked the boot logs again, and I'm still seeing the same camera stuff mentioned there, so I don't know if it fixed anything since I can't boot but it doesn't look different.
I uploaded the files here: https://drive.google.com/file/d/0B5_lN_xRgoTVTUZZX0ZaWmZGNkE/view
Please tell me if there's anything there shouldn't be about the camera in them.
Once I reinstall Magisk, the ID at the boot splash warning goes back to N/A. Funny enough it -does- say it's found a stock boot image and it's backing it up when you install, but on uninstall it never finds it.
Click to expand...
Click to collapse
it always says image signed with bad key for me
you can try going into twrp
click advanced
file manager
data
select magisk.img (or something like that)
then delete it
Other than reflashing the entire firmware via fastboot theres not alot else I can suggest
I would erase userdata though if you are trying the uninstall magisk as it does modify the data partition and its best to erase it if you no longer use magisk - but as I mentioned before anything on internal storage will be lost so move it to sd card
But I dont know of anyone else who has used magisk and the camera stops working so I dont even know if thats the problem
Without testing it on a fresh stock rom you wont know
I flashed LineageOS and it's seeing my camera! I haven't yet flashed the google apps, mainly to see if the camera works in as minimal a clean slate as possible. Now with that out of the way, whatever other issues I may encounter I will solve or possibly ask in another thread, but at least this fixed the cam. Now off to the long road of installing stuff.
for me is the same, flashing stock again, update all to august patch, and the camera stop working, if i uninstall magisk the phone not starts, is stuck in the boot logo, after install magisk 14 again, the phone boting but no camera works
woozie.2007 said:
for me is the same, flashing stock again, update all to august patch, and the camera stop working, if i uninstall magisk the phone not starts, is stuck in the boot logo, after install magisk 14 again, the phone boting but no camera works
Click to expand...
Click to collapse
After uninstalling magisk try flashing the kernel for your rom via fastboot
i tried but the phone won't boot
---------- Post added at 05:13 PM ---------- Previous post was at 05:12 PM ----------
the phone started only if i flash system sparsechunk0, 1, 2, 3 and 4, without these flashed the phone not starting
i flashed again the stock firmware, initial is with patch from january, i made ota update to march(the camera still works with magisk 14), and then i updated ota to august....now camera works, but i installed magisk and patched the boot....bang, the camera stops. So i decided is problem with magisk after the august update, i haven't twrp, only flash it via fastboot. I dont know what can i tried to works camera with magisk ((
woozie.2007 said:
i flashed again the stock firmware, initial is with patch from january, i made ota update to march(the camera still works with magisk 14), and then i updated ota to august....now camera works, but i installed magisk and patched the boot....bang, the camera stops. So i decided is problem with magisk after the august update, i haven't twrp, only flash it via fastboot. I dont know what can i tried to works camera with magisk ((
Click to expand...
Click to collapse
Why do you want to use magisk - it doesn't work fully on this device - eg magisk hide & modules do not work
Much better using supersu (either via twrp zip or CF-Auto-Root) or the lineageos root addon
TheFixItMan said:
Why do you want to use magisk - it doesn't work fully on this device - eg magisk hide & modules do not work
Much better using supersu (either via twrp zip or CF-Auto-Root) or the lineageos root addon
Click to expand...
Click to collapse
because i want to update via ota, cf auto root i tried but not works, i want to use stock firmware not lineageos, i have 7.0. Can you tell me how to root moto g5 without modify system, to be able to update ota? Thanks
woozie.2007 said:
because i want to update via ota, cf auto root i tried but not works, i want to use stock firmware not lineageos, i have 7.0. Can you tell me how to root moto g5 without modify system, to be able to update ota? Thanks
Click to expand...
Click to collapse
Then use supersu and flashfire app
https://play.google.com/store/apps/details?id=eu.chainfire.flash
I'm working on CF-Auto-Root - server is down at the moment - once Iv created a working package I'll post it
how? i am on stock now, not twrp, i have full stock
woozie.2007 said:
how? i am on stock now, not twrp, i have full stock
Click to expand...
Click to collapse
Flash twrp root then flash stock recovery
Obviously I presume you have unlocked the bootloader
yes, of course i have
woozie.2007 said:
yes, of course i have
Click to expand...
Click to collapse
hello
he
lp me please i have the same problem: camerera falled
Marie74 said:
hello
he
lp me please i have the same problem: camerera falled
Click to expand...
Click to collapse
i fixed the problem with clean flash stock rom, then update ota then flash twrp and root again with latest version of magisk
camera
woozie.2007 said:
i fixed the problem with clean flash stock rom, then update ota then flash twrp and root again with latest version of magisk
Click to expand...
Click to collapse
thank you for awser give me the link please please please! god bless you!
Related
I have a blackview A20 which is a low spec phone running android oreo go.
I would like to use this phone for experimentation with android development and learning about android on a cheap device without risk of breaking my main phone. To do this I would like it rooted and as a bonus with a custom recovery so I can test custom ROMs.
State of device:
Unlocked bootloader
Unchanged ROM
Unchanged Recovery
OEM unlocking enabled
USB debugging enabled
What I have tried:
Flashing recovery images with fastboot
Using fastboot flash recovery recovery.img with some TWRP and CWM recovery images all yield:
target reported max download size of 134217728 bytes
sending 'recovery' (4690 KB)...
OKAY [ 0.169s]
writing 'recovery'...
OKAY [ 0.276s]
Click to expand...
Click to collapse
finished. total time: 0.448s
or similar. Then I restart phone and select boot into recovery mode. The phone hangs for a small while before restarting and booting into the normal OS. On restart into recovery the unchanged recovery is there still.
Various 'one-tap' methods
All of which were unsuccessful. If needed I can give details.
Installing SuperSU zip from recovery
In a futile attempt I tried to use the android recovery to push a SuperSU zip with its update from zip option. I knew this wouldn't work but I found something interesting. On the Apply update from SD card option I get an error saying couldn't mount /sdcard
Booting recovery images with fastboot
I have tried the fastboot boot recovery.img command to try to boot directly into the images. I get this
downloading 'boot.img'...
OKAY [ 0.211s]
booting...
OKAY [ 0.047s]
finished. total time: 0.261s
Click to expand...
Click to collapse
output but the device just restarts and boots normally into the normal OS.
What I would like from this question (In order of importance):
A way to root the device
A way to access a custom recovery (even if temporary)
Ability to install custom ROMs
A permanent custom recovery
mejakep said:
I have a blackview A20 which is a low spec phone running android oreo go...
Click to expand...
Click to collapse
I don't have this device but, you may find the following threads helpful because they, apparently, are compatible with your specific device. Don't be afraid to ask for some member guidance within one of them too.
https://forum.xda-developers.com/showthread.php?t=3709659
https://forum.xda-developers.com/showthread.php?t=3767690
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Hello,
I'm also trying to root the Blackview A20 with no success. Where you able to find a way?
Thanks!!
I'm afraid I still haven't found a way. Other than TWRP or something making a custom recovery specifically for this phone I don't see a way to root it at all. Sorry
I have a Blackview A20 Pro (note this is probably different in specification to the A20) - Here is how I rooted it by using Magisk on a boot image read and written using SPFlash tools. I had previously unlocked the bootloader on the phone by using the Developer option for OEM unlock and then fastboot unlocking as standard.
- Obtain the MT6739_Android_Scatter file from an archive of the a20 stock rom available by googling
- Install Magisk manager apk on the phone
- Run the latest version of SP Flash tools on the PC with the associated drivers. Load the scatter file in to it.
- Work out the size of the boot partition by subtracting the start value of the next partition (Logo) from the start position of (Boot)
- I did using Windows calculator in programmer mode - set to hex, subtract the two values. Note the start position of the boot partition
- Go to the Read Back page, add an item to read back, enter a filename to save it like a20-stock-boot-image.img and then enter the start position of the boot partition and the size you calculated. Make sure to get them exactly correct and avoid changing the number of digits in the entry box as I don't know how fussy sp-flash tools is.
- Unplug the phone from PC if it is plugged in and remove the battery.
- Tell SP Flash tools to start the read-back
- Plug the phone in, within a few seconds it should read and save the boot partition from the phone. Keep this backed up. File should be something between 8-25mb I would expect.
- Put the battery in the phone and power it up and unplug/plug it in to the PC via usb and then in the notification area on the phone select "Transfer Files" from the very bottom so it appears to your PC as a drive.
- Drag over the stock boot image from your PC somewhere on the phone - like the Downloads folder.
- On the phone open magisk and select install - when prompted select to use local boot image, select the stock boot image file you transferred
- Magisk should now patch this file - make sure the text it outputs looks like it recognized the boot image and is working.
- Now unplug and replug the phone to PC as I found PC doesn't seem to see new files on the phone. Pull over the patched boot image Magisk has made. Don't worry if this is smaller than the original file. The extra bytes were likely just zeros.
- Using SP Flash tool, go back to the Download screen and select the patched boot image for the boot partition. This will write the new boot image to your phone.
- Power down the phone and remove the battery.
- Tell SP flash tool to start and then plug the phone in with no battery. It should then flash the patched boot image.
- Put the battery back in and boot the phone. When you open magisk app on the phone now it should say you are rooted.
Enjoy!
If it doesn't work, repeat the download process with the stock boot image you saved and that should restore things to how they were before. I assume if it doesn't work it will just be because you need to unlock the bootloader or because your phone is different to the scatter file, but in that case I would expect Magisk to fail to patch it before you get to that stage.
How do you remove the battery? Have I missed something?
Sorry, wrong phone!!
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!!
Mohammadreza76646 said:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!!
Click to expand...
Click to collapse
Doing the update second time is fine, and best way to restore full stock. But you needed to use Oreo version of no-check recovery and the Oreo partition to flash it to.
So if still able to get into twrp, can try with correct no-check recovery and correct partition it's flashed to.
Also
With multi tool , make sure you put check mark on emui 8. Up in upper right corner. That way it uses Oreo partition names and file not nougat.
The partition length over message usually means nougat file or partition name used on Oreo system
mrmazak said:
Doing the update second time is fine, and best way to restore full stock. But you needed to use Oreo version of no-check recovery and the Oreo partition to flash it to.
So if still able to get into twrp, can try with correct no-check recovery and correct partition it's flashed to.
Also
With multi tool , make sure you put check mark on emui 8. Up in upper right corner. That way it uses Oreo partition names and file not nougat.
The partition length over message usually means nougat file or partition name used on Oreo system
Click to expand...
Click to collapse
Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore
Mohammadreza76646 said:
Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore
Click to expand...
Click to collapse
I give my phone to a friend to work on it. If he can't fix it I try new multi tools version to flash phone.
Mohammadreza76646 said:
Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore
Click to expand...
Click to collapse
On the extractor app. On options tab uncheck the verify header option, it should extract then.
Then perhaps first do these three partitions.
Kernel.img
Ramdisk.img
Then
twrp_ramdisk or for stock use recovery_ramdisk
Mohammadreza76646 said:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!!
Click to expand...
Click to collapse
I ever have similiar problem with you dude, but it's solved now, if you always stuck on " its OK but when my phone want to start its stuck on google page "just a sec...", its call google accont verification, i'll by bypass with this script, save as to .bat and put on adb folder
adb devices
adb shell content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1
adb shell am start -n com.google.android.gsf.login/
adb shell am start -n com.google.android.gsf.login.LoginActivity
pause
in fastboot type:
fastboot -w
after all it's works to me to bypass google account verification
and if now your problem is
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
i solve with re-flash system from this
https://androidfilehost.com/?fid=673956719939830152
fastboot flash system system.img
and doing TWRP Flashing
https://forum.xda-developers.com/devdb/project/?id=25826#downloads
fastboot flash recovery_ramdisk complete_twrp_ramdisk.img
and voila my problem solved..
mrmazak said:
On the extractor app. On options tab uncheck the verify header option, it should extract then.
Then perhaps first do these three partitions.
Kernel.img
Ramdisk.img
Then
twrp_ramdisk or for stock use recovery_ramdisk
Click to expand...
Click to collapse
Hello again dude.
Finally I flashed my phone and I got the system installed.
But now my phones IMEI is lost. and I cant put sim on it!!!
what should I do now???
FRP is locked! (
Mohammadreza76646 said:
Hello again dude.
Finally I flashed my phone and I got the system installed.
But now my phones IMEI is lost. and I cant put sim on it!!!
what should I do now???
FRP is locked! (
Click to expand...
Click to collapse
So now is locked frp. Does phone have twrp or stock now.?
I think when you tried to install the oreo update for second time, you followed same tutorial as the first time. And that made you problem worse. The tutorial has you flash no-check recovery to 2 partition by block number. 22 & 29. On nougat that is "recovery" and "recovery2". On Oreo partion table it is "reserved2" & "erecovery_vendor"
I don't know how to fix imei. Have hope that if to ucan have a full ota install , maybe can be fixed.
There is available a "service rom" (used to fix most all problem) for Europe region with l21.
I can share link to site with service rom if you want , but I have not used it myself so not gonna be much help with it.
Link is to rusian language page. Google should translate for you.
https://4pda.ru/forum/index.php?showtopic=879524&view=findpost&p=73818595
mrmazak said:
So now is locked frp. Does phone have twrp or stock now.?
I think when you tried to install the oreo update for second time, you followed same tutorial as the first time. And that made you problem worse. The tutorial has you flash no-check recovery to 2 partition by block number. 22 & 29. On nougat that is "recovery" and "recovery2". On Oreo partion table it is "reserved2" & "erecovery_vendor"
I don't know how to fix imei. Have hope that if to ucan have a full ota install , maybe can be fixed.
There is available a "service rom" (used to fix most all problem) for Europe region with l21.
I can share link to site with service rom if you want , but I have not used it myself so not gonna be much help with it.
Link is to rusian language page. Google should translate for you.
https://4pda.ru/forum/index.php?showtopic=879524&view=findpost&p=73818595
Click to expand...
Click to collapse
It have stock recovery.
Mohammadreza76646 said:
It have stock recovery.
Click to expand...
Click to collapse
in summery. because i have been going back and forth in multiple different groups, multiple problem, i cant remember it all.
you have broken system, from failed root attempt, followed by failed update.
device condition is as follows.
--system not booting
--stock recovery loads
--fastboot/bootloader loads, but is in frp lock status
options are limited, at best.
I think "dload" method with service rom is best.
other option is maybe paid service like dc-unlock. But I can recall some note on there service about frp-unlock, that can only be used on device with working system. (of course if was working system, wouldn't need dc-unlock)
mrmazak said:
in summery. because i have been going back and forth in multiple different groups, multiple problem, i cant remember it all.
you have broken system, from failed root attempt, followed by failed update.
device condition is as follows.
--system not booting
--stock recovery loads
--fastboot/bootloader loads, but is in frp lock status
options are limited, at best.
I think "dload" method with service rom is best.
other option is maybe paid service like dc-unlock. But I can recall some note on there service about frp-unlock, that can only be used on device with working system. (of course if was working system, wouldn't need dc-unlock)
Click to expand...
Click to collapse
No. System boot successfully!
I will send you screenshot:
Mohammadreza76646 said:
No. System boot successfully!
I will send you screenshot:
Click to expand...
Click to collapse
here you are
Mohammadreza76646 said:
here you are
Click to expand...
Click to collapse
what about the "about phone" screen
what does it show for version?
If is all stock you should be able to go into deveolper options and enable "oem unlock". If it is greyed out and cannot switch it. Try First to remove google account (all accounts ). and reboot. See if can change then. If not, try Second to do "fastboot oem relock [enter your bootloader code here]
after relock and rebooted oem switch should be enabled again.
****RELOCK IS ONLY ADVISED IF 100% STOCK ROM****
otherwise relock could make more trouble.
Still not sure how to get IMEI back even if unlocked frp though.
**And please stop posting in other threads , the same problem , because you are getting help here.
your post in recovery thread is off topic to that thread and just makes the forum harder to maintain.
mrmazak said:
what about the "about phone" screen
what does it show for version?
If is all stock you should be able to go into deveolper options and enable "oem unlock". If it is greyed out and cannot switch it. Try First to remove google account (all accounts ). and reboot. See if can change then. If not, try Second to do "fastboot oem relock [enter your bootloader code here]
after relock and rebooted oem switch should be enabled again.
****RELOCK IS ONLY ADVISED IF 100% STOCK ROM****
otherwise relock could make more trouble.
Still not sure how to get IMEI back even if unlocked frp though.
**And please stop posting in other threads , the same problem , because you are getting help here.
your post in recovery thread is off topic to that thread and just makes the forum harder to maintain.
Click to expand...
Click to collapse
Thanks )
I'm so sorry for my posts, it's because I don't have a stable connection and I can't see notification of my thread.
I gave my phone to friend an he fix IMEI (I don't know how)
But OEM is steel lock.
I think he did it with using special box.
Mohammadreza76646 said:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!![/QUOTE
Are u able.to boot into twrp ?
Click to expand...
Click to collapse
Hello I have a Huawei Mate-SE (with bootloader unlocked and rooted with magisk v16). I have been using the android custom rom RRO v6 (RR-O-v6.0.0-20180401-bnd-OpenKirin) for around a month now. I got this exact same problem about the White Screen saying "ERROR MODE Attention...." since I updated the Magisk to latest version (from the installed application) and rebooted my phone. SInce I rebooted I am getting that same error which makes the phone loops into it for a few times and then it loads the Huawei eRecovery that offers me some options that I am not sure what would do to my phone.
I have been trying to connect to adb tools/fastboot but it doesn't detect the phone and im pretty sure I have the device drivers installed on my computer since nothing have changed in my pc for a month now since I flashed RRO on it.
Is there any other mode besides recovery that would allow me to connect adb/fastboot to it? Or does anyone knows how should I proceed?
IonDEfeso said:
Hello I have a Huawei Mate-SE (with bootloader unlocked and rooted with magisk v16). I have been using the android custom rom RRO v6 (RR-O-v6.0.0-20180401-bnd-OpenKirin) for around a month now. I got this exact same problem about the White Screen saying "ERROR MODE Attention...." since I updated the Magisk to latest version (from the installed application) and rebooted my phone. SInce I rebooted I am getting that same error which makes the phone loops into it for a few times and then it loads the Huawei eRecovery that offers me some options that I am not sure what would do to my phone.
I have been trying to connect to adb tools/fastboot but it doesn't detect the phone and im pretty sure I have the device drivers installed on my computer since nothing have changed in my pc for a month now since I flashed RRO on it.
Is there any other mode besides recovery that would allow me to connect adb/fastboot to it? Or does anyone knows how should I proceed?
Click to expand...
Click to collapse
I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.
Power off , long press power button.
Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.
Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)
mrmazak said:
I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.
Power off , long press power button.
Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.
Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)
Click to expand...
Click to collapse
Hi thank you I was able to finally detect the device now. I am unsure about the kernel is that the recovery.img or system.img files I downloaded (i saved every file i used when I installed the rom) or do I need to look for the kernel somewhere else? I do have the complete_twrp_ramdisk.img file though.
Edit, I did more research and found the stock kernel is withing the boot.img file which I dont have so I looked up for the official BND-L34 oreo update and im currently downloading to extract the stock boot.img from the update.zip and flash it. Since that download was going to take me a while anyway i tried flashing the twrp recovery file without success (didn't changed anything) so i guess I should follow the instructions you gave me by flashing the kernel first then the twrp recovery.
mrmazak said:
I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.
Power off , long press power button.
Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.
Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)
Click to expand...
Click to collapse
Do you know what the boot.img files name is after extraction?
I have extracted all 3 update zips and cannot find anything called boot.img
By the way, thank you.. After updating magisk I have been dealing with failed recovery and failed boot for over a week and this is the first reply anywhere that looks promising
IonDEfeso said:
Hi thank you I was able to finally detect the device now. I am unsure about the kernel is that the recovery.img or system.img files I downloaded (i saved every file i used when I installed the rom) or do I need to look for the kernel somewhere else? I do have the complete_twrp_ramdisk.img file though.
Edit, I did more research and found the stock kernel is withing the boot.img file which I dont have so I looked up for the official BND-L34 oreo update and im currently downloading to extract the stock boot.img from the update.zip and flash it. Since that download was going to take me a while anyway i tried flashing the twrp recovery file without success (didn't changed anything) so i guess I should follow the instructions you gave me by flashing the kernel first then the twrp recovery.
Click to expand...
Click to collapse
if you were on oreo. then there is not a boot.img, instaed there is seperate ramdisk.img and kernel.img.
i have all the files already extracted for oreo and a backup from nougat as well.
https://androidfilehost.com/?w=files&flid=265998
make sure you know what you are doing before flashing.
for example. on oreo the boot and recovery share one kernel image. SO if kernel is messed up you will not be able to boot "boot" or "recovery"
I've spent about 6 hours trying various things and I'm not sure how to continue.
I did a backup then started upgrading to Android 10. Long story short, I want to go back to 9.
Every time I try to flash-all.bat crosshatch-pq1a.181205.006.a1-factory-99bead33 back, it fails on:
Sending sparse 'vendor_b' 1/2 (262140 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
It always fails on that line, and only after succeeding on 34 other counts of flashing. I've tried multiple cables. After this, there's a constant stream of fastboot and recovery warnings, and nothing works right until I flash crosshatch-qq2a.200405.005-factory-2d1c5652 back on. I've tried a handful of manual flashing of the vendor file without success.
It seems like something changed in the phone that simply disallows flashing back.
Has anyone successfully done this?
bizaff said:
I've spent about 6 hours trying various things and I'm not sure how to continue.
I did a backup then started upgrading to Android 10. Long story short, I want to go back to 9.
Every time I try to flash-all.bat crosshatch-pq1a.181205.006.a1-factory-99bead33 back, it fails on:
Sending sparse 'vendor_b' 1/2 (262140 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
It always fails on that line, and only after succeeding on 34 other counts of flashing. I've tried multiple cables. After this, there's a constant stream of fastboot and recovery warnings, and nothing works right until I flash crosshatch-qq2a.200405.005-factory-2d1c5652 back on. I've tried a handful of manual flashing of the vendor file without success.
It seems like something changed in the phone that simply disallows flashing back.
Has anyone successfully done this?
Click to expand...
Click to collapse
I am assuming you are on a device which has an unlocked bootloader? If not, you can't go back.
Eudeferrer said:
I am assuming you are on a device which has an unlocked bootloader? If not, you can't go back.
Click to expand...
Click to collapse
Correct - first thing I did when I got it a couple years ago was unlock it. On the fastboot screen it has always said unlocked as well.
Like I said, I can flash Android 10 on it (which it has right now with Magisk installed via copying boot.img and updating it through the app), but I'd like to go back to the image I had (either 9.0.0 (PQ1A.181205.006, Dec 2018) or 9.0.0 (PQ1A.181205.006.A1, Dec 2018, Docomo) - not sure what the Docomo is).
Android 10 (crosshatch-qq2a.200405.005-factory-2d1c5652) installed from flash-all.bat just fine, but neither of the above 9.0.0 images install - they both fail on the vendor_b and only on the vendor_b.
Thoughts?
bizaff said:
Correct - first thing I did when I got it a couple years ago was unlock it. On the fastboot screen it has always said unlocked as well.
Like I said, I can flash Android 10 on it (which it has right now with Magisk installed via copying boot.img and updating it through the app), but I'd like to go back to the image I had (either 9.0.0 (PQ1A.181205.006, Dec 2018) or 9.0.0 (PQ1A.181205.006.A1, Dec 2018, Docomo) - not sure what the Docomo is).
Android 10 (crosshatch-qq2a.200405.005-factory-2d1c5652) installed from flash-all.bat just fine, but neither of the above 9.0.0 images install - they both fail on the vendor_b and only on the vendor_b.
Thoughts?
Click to expand...
Click to collapse
I'm not an expert by any means but my thoughts on this would be: perhaps some file needed is not properly extracted to the right folder. I like to extract everything to the same file and then run the commands I'm using. Don't know how necessary this is but it works for me. Also, perhaps try the commands with a .\ in front of it. For some reason, it doesn't work for me unless I do this.
Have you tried fastboot erase userdata just for giggles? I've gone back to 9 before. I always extract the contents of the factory zip to the fastboot folder directly then just run the flash-all.bat are you using the latest fastboot tools?
Check what slot it is on and switch slots.
Eudeferrer said:
I'm not an expert by any means but my thoughts on this would be: perhaps some file needed is not properly extracted to the right folder.
Click to expand...
Click to collapse
This kinda sorta seems like it might be something wrong? It always fails on the same file. If I recall correctly, I downloaded the archive again and it still failed on the same file..
Eudeferrer said:
I like to extract everything to the same file and then run the commands I'm using. Don't know how necessary this is but it works for me. Also, perhaps try the commands with a .\ in front of it. For some reason, it doesn't work for me unless I do this.
Click to expand...
Click to collapse
I don't think it's that, it's finding and executing everything.
Maybe I could try this on Linux? I don't know, I'm kind of at a loss.
UmbrellaTakedown said:
Have you tried fastboot erase userdata just for giggles? I've gone back to 9 before. I always extract the contents of the factory zip to the fastboot folder directly then just run the flash-all.bat are you using the latest fastboot tools?
Click to expand...
Click to collapse
I haven't tried that, but it's most definitely vendor_b. I wonder if I should erase that partition and see if that works.. but I'm still stumped why updating to 10 works.. just checked the archive and there is a vendor.img in the 10 image.
Yep, that's how I run it too.
I downloaded the "latest", which gave me platform-tools_r30.0.0-windows. I also went back and downloaded 27, 28, and 29, and tried a few of those - no dice.
wangdaning said:
Check what slot it is on and switch slots.
Click to expand...
Click to collapse
I guess that's one thing I didn't try.. is there a decent guide somewhere to select the slot to program, boot, and install Magisk to? I had found something about querying which slot was active, but not about selecting..
Hopefully I can update to the final 9.0 version then not worry about it till I switch to 10..
fastboot -help will tell you the command to select, something like fastboot --set-active=a/b. The bootloader screen should tell you which is active. Once you change active slot use fastboot reboot bootloader and run the flash-all of the factory image you want.
Hi all,
I'm happy to accept help as--to the extent of my abilities--this Mi 10T Lite is bricked. But it's not hard-bricked yet! Since I'm completely green to the world of ROM flashing, it's simply an issue of me following instructions I do not yet understand and butting my head against it when the result deviates from the tutorial.
Issue
The problem is this: with the help of instructions on this forum and YouTube I'm able to successfully perform an installation of LineageOS. No errors occur. But then when I reboot the device it will automatically boot to recovery instead and then it seems as if the installation has been undone or was never carried out.
Details
TWRP build: twrp_gauguin_mi10tl-rn9p5g_mi10i_3.5.a10_05-03-2021_d-bl-l_fix-mtp-after-format
LineageOS build: lineage-17.1-20210205-UNOFFICIAL-gauguin
OpenGApps version: open_gapps-arm-10.0-nano-20210314
Things I tried and phone's behavior
• I have tried other ROMs. Because perhaps it's Lineage's fault, I thought. But the same problem occurs with any ROM I try to install. Successful installation -> boot to system -> back to recovery.
• I tried rolling back to the back-up I took. But when I restore it and reboot the phone, it gets in an endless reboot cycle until I enter recovery or fastboot mode again.
• I unsuccessfully tried reinstalling the stock ROM (the stable release of MIUI 12.0). The installation was aborted with the error: assert failed: update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list")). But this is a problem probably better suited for a thread on the Xiaomi community forum where the ROM is published. I would rather get LineageOS on my phone than going back to stock, but maybe this error is significant to the solution in some way.
• Looking for existing troubleshooting threads proved difficult because I'm not even sure what to look for. Googling "custom rom installs successfully but actually it doesn't" won't yield any results.
• I'm new at flashing custom ROMs. This is the second phone I installed Lineage on. The first phone was a Samsung Galaxy J3 and I succeeded without problem by simply following the instructions, so I'm even newer at troubleshooting for this. Be aware of that please!
The instructions I followed to try an install
Prerequisite: the phone's previous OS was MIUI 12, based on Android 10.
Wipe Dalvik / ART Cache, Data, and Cache.
Flash the ROM from the external SD card.
Flash OpenGApps from the external SD card.
Format Data.
Reboot.
After wiping everything can you go to the mounts menu and mount all partitions (mainly system data and cache)
As long as all partitions can be mounted the rom should flash assuming it's the right rom for the phone/firmware
Thank you for replying.
I'm using TWRP. And I found out that system was unchecked in the mounts menu all this time. As I understood it the only purpose for mounting a partition is to present it to a device connected via USB.
So when I check the checkbox for system to mount it, then after installation system is unmounted again. The console log mentions it unmounts system just before flashing. The result is the same: a "successful" installation and then reboot back into recovery without an OS installed.
How do I check what firmware version is currently installed on my Mi 10T Lite in recovery? It was fresh off the shelves, and it had the latest software installed as of March 20th.
CyanMatter said:
Thank you for replying.
I'm using TWRP. And I found out that system was unchecked in the mounts menu all this time. As I understood it the only purpose for mounting a partition is to present it to a device connected via USB.
So when I check the checkbox for system to mount it, then after installation system is unmounted again. The console log mentions it unmounts system just before flashing. The result is the same: a "successful" installation and then reboot back into recovery without an OS installed.
How do I check what firmware version is currently installed on my Mi 10T Lite in recovery? It was fresh off the shelves, and it had the latest software installed as of March 20th.
Click to expand...
Click to collapse
A rom zip should automatically mount partitions then unmount them after
The reason I asked for manual mount is to test there's no errors in mounting
Are you sure you're on android 10 and not android 11 as android 11 was out on the date you mentioned
This might also be the reason you can't flash stock firmware if you're flashing android 10 firmware when your device is already on android 11
In fastboot mode with phone connected to pc - in cmd/terminal type
fastboot getvar all
To get firmware version and device info
TheFixItMan said:
A rom zip should automatically mount partitions then unmount them after
The reason I asked for manual mount is to test there's no errors in mounting
Are you sure you're on android 10 and not android 11 as android 11 was out on the date you mentioned
This might also be the reason you can't flash stock firmware if you're flashing android 10 firmware when your device is already on android 11
Click to expand...
Click to collapse
I'm positive it's on Android 10, but you're making me doubt that. A search shows plenty of articles announcing Android 11 has been rolling out for this device indeed.
So if in theory this device is actually on Android 11, then I should be able to flash this ROM: https://forum.xda-developers.com/t/rom-unofficial-11-0-gauguin-dotos.4231683/
I downloaded the ROM based on Android 11 mentioned above, but when I try to install it this time it throws this error:
assert failed: update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list"))
I don't understand what it means, I can find only one thread that mentions the error. In their case they solved it by formatting data a couple of times until it took. But it doesn't work for me.
EDIT: I just found out I can put a file, any random file, in my internal storage and have it disappear when I reboot to recovery. That doesn't make sense to me. That shouldn't happen, right?
EDIT 2: Disregard that. It seems to have been a weird blip because I can't reproduce it. It's strange because files I put in there disappeared without me wiping anything.
CyanMatter said:
I downloaded the ROM based on Android 11 mentioned above, but when I try to install it this time it throws this error:
assert failed: update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list"))
I don't understand what it means, I can find only one thread that mentions the error. In their case they solved it by formatting data a couple of times until it took. But it doesn't work for me.
EDIT: I just found out I can put a file, any random file, in my internal storage and have it disappear when I reboot to recovery. That doesn't make sense to me. That shouldn't happen, right?
EDIT 2: Disregard that. It seems to have been a weird blip because I can't reproduce it. It's strange because files I put in there disappeared without me wiping anything.
Click to expand...
Click to collapse
All I can suggest is try flashing one of the latest stock firmware files via fastboot so at least you'll have a working device
V12.0.2.0.RJSMIXM or V12.0.1.0.RJSEUXM (download on pc)
Download latest MIUI ROMs for Mi 10T Lite - Xiaomi Firmware
The Xiaomi Mi Note 10 Lite is a full package and it can be found under $300. The curved 6.47″ AMOLED display and aluminum bezels give the phone a premium look without sacrificing functionality. It seems like Xiaomi Mi Note 10 Lite can be the best phone you can get for this budget. The AMOLED...
xiaomifirmware.com
Instructions
How to flash Xiaomi firmware via Fastboot & Recovery mode
Flashing your Redmi/Mi smartphone with Xiaomi official firmware (MIUI) will help you fix certain software issues on the phone. It also helps you to get rid of root and all modifications made to your phone system software. To upgrade, update or fix minor software problems on your phone, flashing...
www.leakite.com
TheFixItMan said:
All I can suggest is try flashing one of the latest stock firmware files via fastboot so at least you'll have a working device
V12.0.2.0.RJSMIXM or V12.0.1.0.RJSEUXM (download on pc)
Download latest MIUI ROMs for Mi 10T Lite - Xiaomi Firmware
The Xiaomi Mi Note 10 Lite is a full package and it can be found under $300. The curved 6.47″ AMOLED display and aluminum bezels give the phone a premium look without sacrificing functionality. It seems like Xiaomi Mi Note 10 Lite can be the best phone you can get for this budget. The AMOLED...
xiaomifirmware.com
Instructions
How to flash Xiaomi firmware via Fastboot & Recovery mode
Flashing your Redmi/Mi smartphone with Xiaomi official firmware (MIUI) will help you fix certain software issues on the phone. It also helps you to get rid of root and all modifications made to your phone system software. To upgrade, update or fix minor software problems on your phone, flashing...
www.leakite.com
Click to expand...
Click to collapse
Ok, so... funny thing happened. I followed this advice and it worked, I can boot my system into MIUI 12 again!
BUT when flashing the firmware, after 7 minutes the flashing tool reported an error and seemed to have aborted the process; status: error:Not catch checkpoint (\$fastboot -s .* lock),flash is not done. Meanwhile, while I was worried it failed, the device actually rebooted into the stock OS.
Here is the relevant part of the log. The failed checkpoint does not seem to be crucial to the process. These are the last lines, and I masked my device code as I'm worried it's identifying information.
Code:
[02:13:37 {device code}]:info2:Rebooting OKAY [ 0.001s]
[02:13:37 {device code}]:info2:Finished. Total time: 0.001s
[02:13:37 {device code}]:begin FlashDone
[02:13:37 {device code}]:errMsg is null
[02:13:37 {device code}]:begin checkPoint
[02:13:37 {device code}]:error:Not catch checkpoint (\$fastboot -s .* lock),flash is not done
[02:13:37 {device code}]:process exit.
[02:13:37 {device code}]:flashSuccess False
[02:13:37 {device code}]:isFactory False CheckCPUID False
[02:13:37 {device code}]:before:flashSuccess is False set IsUpdate:True set IsDone True
[02:13:37 {device code}]:after:flashSuccess is False set IsUpdate:false set IsDone true
Still, thank you lots for your help! At least I can use my device now. Next time I'll double check my software versions before flashing a custom ROM.
Code:
/*
* Your warranty is no longer valid, unless you lie.
*
* I am not responsible for bricked devices, strained relationships,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this kernel
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
GUIDE UNLOCKING BOOTLOADER & ROOTING Xperia 10 III (PDX213)STEP 1 - UNLOCK YOUR BOOTLOADER
1- GUIDE UNLOCK BOOTLOADER XPERIA
2- WEB UNLOCK TOOLS BOOTLOADER XPERIA
STEP 2 - DOWNLOAD FIRMWARE STOCK USING XPERIFIRM
STEP 3 - extract boot_X-FLASH-ALL-8A63.sin using zip file manager ( 7zip, for ex here I used Ark zip manager from Fedora OS)
rename boot.000 to boot.img
STEP4 - install magisk manager in your phone from official github release
- open magisk patch your boot.img
STEP5 - go in fastboot and enter :
fastboot flash boot boot_patched.img
ENJOY
Nice! Now maybe someone can look into fixing that green tint.
zpk787 said:
Nice! Now maybe someone can look into fixing that green tint.
Click to expand...
Click to collapse
idk what issue your referering ( maybe thread green tint in oled
? ) here I have totally normal screen color
So I have my bootloader unlocked, developer mode on, USB debugging on, LineageOS 18 GSI installed, and reboot into fastboot with `adb reboot fastboot` but
Code:
$ fastboot boot Download/magisk_patched-23000_BOvMB.img
Sending 'boot.img' (98304 KB) OKAY [ 3.595s]
Booting FAILED (remote: 'Unrecognized command boot')
fastboot: error: Command failed
What?? I also tried to go into bootloader, but similar result. Did I mess up the boot.img?
pepijndevos said:
So I have my bootloader unlocked, developer mode on, USB debugging on, LineageOS 18 GSI installed, and reboot into fastboot with `adb reboot fastboot` but
Code:
$ fastboot boot Download/magisk_patched-23000_BOvMB.img
Sending 'boot.img' (98304 KB) OKAY [ 3.595s]
Booting FAILED (remote: 'Unrecognized command boot')
fastboot: error: Command failed
What?? I also tried to go into bootloader, but similar result. Did I mess up the boot.img?
Click to expand...
Click to collapse
For some reason bootloader no allow fastboot boot
Need : fastboot flash boot patchedboot.img
Yea it's just really scary to flash a patched firmware, what if you did it wrong and it bricks your phone. But well in the end I did it and everything worked out.
One really weird error I get from Magisk is that it says it's in an abnormal state because there is a "su" command that doesn't belong to Magisk. I have no idea where that came from. Should I be concerned? Everything seems to work as far as rooting is concerned, but mysterious su commands could be a security concern maybe. I hope it's not a sketchy GSI or something hehe.
Anyway thanks for your guide. I have MicroG and F-droid working now, as well as ACC. One thing I'd clarify about your guide is that "going into fastboot" is... actual fastboot and not bootloader or recovery which you also use with the fastboot tool. Just a thing that's obvious when you know, but uncertain when you're doing it for the first time.
Oh and another thing that was sliiiightly puzzling is that you actually have to copy the boot.img to your phone, patch it and then copy it back to your PC. Same thing, obvious when you know, kinda puzzling when it's your first time. For me it didn't show up in the file manager after patching so I had to copy it with adb, not sure what that was about.
Did anyone notice negative effects after rooting?
Is the camera working fine?
Is Bluetooth working, the microphone and calling?
Is safetynet check passing?
My main goal is to have Adaway working in root mode and have stable Wireguard VPN connection (without battery saving methods killing the process every few minutes), I will try custom ROMs after I get the rest to run.
Camera, bluetooth, microphone, calling, all working fine. No idea about safetynet haven't checked. As mentioned above, it does say I have an extra `su` that I don't know where it came from.
Did you do any backup of the TA partition (if that is even neccessary)?
I did not. Not even sure what the TA partition is haha
Of course backups are always a good idea when possible. It just seems a lot of the stuff out there assumes you have TWRP.
pepijndevos said:
I did not. Not even sure what the TA partition is haha
Of course backups are always a good idea when possible. It just seems a lot of the stuff out there assumes you have TWRP.
Click to expand...
Click to collapse
Check this: https://forum.xda-developers.com/t/does-rooting-sony-phone-still-lower-their-quality.4318171/
And more generally https://www.xda-developers.com/sony-xperia-android-pie-unlock-bootloader-drm-fix-camera/
I gather that the devices with Android 9 or above can safely be unlocked, but that does not necessarily mean everything works with root.
I just want to avoid rooting the device and realizing I need some DRM keys that I lost.
Please update us should any problems arise!
Raubsau said:
Check this: https://forum.xda-developers.com/t/does-rooting-sony-phone-still-lower-their-quality.4318171/
And more generally https://www.xda-developers.com/sony-xperia-android-pie-unlock-bootloader-drm-fix-camera/
I gather that the devices with Android 9 or above can safely be unlocked, but that does not necessarily mean everything works with root.
I just want to avoid rooting the device and realizing I need some DRM keys that I lost.
Please update us should any problems arise!
Click to expand...
Click to collapse
This is exactly the reason why I haven't rooted my device yet, too. If I understand it correctly, data in the TA partition is modified at the time the bootloader is unlocked, so if we were to create a backup, that would have to happen before unlocking.
The partition is only readable with root privileges, and rooting in general requires an unlocked bootloader. The only way forward is to wait until an exploit becomes available, allowing us to obtain a root shell with the bootloader still locked.
Hopefully it's possible to flash older firmware onto this phone, which would mean we can downgrade to an older Android security patch level if needed (i.e. the potential exploit gets patched by Google or a vendor) - does anyone here know if that's the case? When installing an OTA update, the UI says we won't be able to return to a previous version, but I suppose it's still possible to flash any of the official firmware packages at any point.
Thanks.
Is there any way to get OTA updates while rooted? That's what I loved about LOS. Maybe we'll get it on this device someday.
Thanks for this post. I have managed to unlock the bootloader which is great, but I am not sure how to -
STEP5 - go in fastboot and enter :
fastboot flash boot boot_patched.img
Update: I have not rooted
Unfortunately many users report a WLAN issue with 62.0.A.3.163.
62.0.A.3.131 cannot be downloaded anymore, except the french (FR?) localized versions. Also, I managed to install 62.0.A.3.131 on a 10 III, but denied the update to the latest version to avoid the WiFi troubles.
The boot.img from 62.0.A.3.131 (FR) and 62.0.A.3.163 (EE) differ. I wonder if anything could go wrong with the newer boot.img.
To my understanding, the boot.img contains the kernel... So, I'd like to test it with "fastboot boot boot.img" before I risk flashing, but: "remote: 'unknown command'".
Any suggestions on how to proceed from here?
You can find earlier firmware versions, including "XQ-BT52_Customized EEA_62.0.A.3.131", here: https://forum.xda-developers.com/t/stock-firmware-backups.4382229/
ZenRebel said:
Thanks for this post. I have managed to unlock the bootloader which is great, but I am not sure how to -
STEP5 - go in fastboot and enter :
fastboot flash boot boot_patched.img
Update: I have not rooted
Click to expand...
Click to collapse
If you've managed to unlock your bootloader, that means you have already entered fastboot mode.
combinedfleet said:
You can find earlier firmware versions, including "XQ-BT52_Customized EEA_62.0.A.3.131", here: https://forum.xda-developers.com/t/stock-firmware-backups.4382229/
Click to expand...
Click to collapse
Man! Thank's a lot!
Any idea why the boot_X-FLASH-ALL-8A63.sin files differ slightly even if compared between markets (with the same version numbers)?