Related
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!
DisclaimerThis software comes wth no warranty,XDA staff ,myself or TeamWin stuff can't be hold responsible for any damage it may cause to your device.
Note: Currently Oreo 8.1 custom roms are not supported,only stock EMUI 8.x .
Download and Installation
* Download twrp recovery
* Start your device in fastboot mode
* Install the recovery using the following command:
Code:
fastboot flash recovery_ramdisk [filename].img --> ex: fastboot flash recovery_ramdisk twrp_p10_lite_0.1.img
* Restart with this command:
Code:
fastboot reboot
* As soon as you execute the restart command,remove the USB cable and keep pressing Volume UP,so the device will boot to TWRP.This is to avoid that the device boot to OS,overwritting TWRP recovery.
Features
Internal storage decryption = working
MTP and OTG connection = working
Backup&Restore = working
Note: There are no sources for this yet,because is based on the work of @zxz0O0 ,from Honor 9.
Contributors
**** Pretoriano80
**** @zxz0O0 - This wouldn't be possible without this guy,so big big thank to him.I used his base to make this recovery work ,so in sign of respect his nick will also be on the TWRP boot screen.Thank again buddy!
**** TeamWin project ,obviously.
**** @Tecalote - He was the main tester for the Mate 9
**** @Blackball
**** @Eurofighter_ty for testing on P10 Lite
**** Team OpenKirin - thanks for the "Oem Path wipe esclusion" code
Download links
twrp_p10_lite_0.1.img - initial release,OTG connection not working
twrp_p10_lite_0.2.img - minor fixes,OTG connection should be fixed (please test and report)
twrp_p10_lite_0.3.img - OTG is now fixed
twrp_p10_lite_0.4.img - fixed mount issues
Why after entering into TWRP I got "Mount Decrypt Data" menu and ask me for some password? What is this?
Then I press Cancel because I don't know what is this menu.
Also I can't make any backups because I got an error: "Failed to unmount '/data' (device or resource busy)" and "Failed to unmount '/system' (device or resource busy)"
Something is wrong with this TWRP.
Aalesund said:
Why after entering into TWRP I got "Mount Decrypt Data" menu and ask me for some password? What is this?
Then I press Cancel because I don't know what is this menu.
Also I can't make any backups because I got an error: "Failed to unmount '/data' (device or resource busy)" and "Failed to unmount '/system' (device or resource busy)"
Something is wrong with this TWRP.
Click to expand...
Click to collapse
Obviously it's asking for password, otherwise it couldn't decrypt the internal storage.
You have to use the same password/pin/pattern that you use in Android.
The feature Internal Storage Decryption is really cool!
And this TWRP has better compatibility with magisk, at last I can use recovery mode for mm.
Thanks!
The problem of not being able to unmount /system means that it'll always be mount read-only, which then means unless a whole system image is flashed, no modifications can be made to /system. This is the only gripe I have about this TWRP; otherwise it works brilliantly.
AndyYan said:
The problem of not being able to unmount /system means that it'll always be mount read-only, which then means unless a whole system image is flashed, no modifications can be made to /system. This is the only gripe I have about this TWRP; otherwise it works brilliantly.
Click to expand...
Click to collapse
Yes, that's right - I saw the issue with keeping system ready only yesterday night on Huawei Mate 10 Lite.
This TWRP works except this also brilliantly on Mate 10 Lite
i tried to flash my emui 5 p10lite with no success:
#
Code:
fastboot flash recovery_ramdisk ./twrp_p10_lite_0.3.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24952 KB)...
OKAY [ 3.186s]
writing 'recovery_ramdisk'...
FAILED (remote: partition length get error)
finished. total time: 3.194s
dlewando said:
i tried to flash my emui 5 p10lite with no success:
#
Code:
fastboot flash recovery_ramdisk ./twrp_p10_lite_0.3.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24952 KB)...
OKAY [ 3.186s]
writing 'recovery_ramdisk'...
FAILED (remote: partition length get error)
finished. total time: 3.194s
Click to expand...
Click to collapse
It only works on EMUI 8.
Tecalote said:
Yes, that's right - I saw the issue with keeping system ready only yesterday night on Huawei Mate 10 Lite.
This TWRP works except this also brilliantly on Mate 10 Lite
Click to expand...
Click to collapse
Here's a test build,i hope that system unmount issue is fixed -- > https://mega.nz/#!AscFxY5R!UdDKb-FIlZI2rjJyCZiMu2er1-HnTWdKYJfGpAoGJdM
Pretoriano80 said:
Here's a test build,i hope that system unmount issue is fixed -- > https://mega.nz/#!AscFxY5R!UdDKb-FIlZI2rjJyCZiMu2er1-HnTWdKYJfGpAoGJdM
Click to expand...
Click to collapse
Same deal unfortunately. Device is a Honor 7X, btw.
AndyYan said:
Same deal unfortunately. Device is a Honor 7X, btw.
Click to expand...
Click to collapse
Well, my magic crystal ball is broken so i will need logs this time.Next time please grab recovery.log and dmesg, otherwise i will start ignoring all these "not working" posts.
Pretoriano80 said:
Well, my magic crystal ball is broken so i will need logs this time.Next time please grab recovery.log and dmesg, otherwise i will start ignoring all these "not working" posts.
Click to expand...
Click to collapse
Done.
I'd need to know how to help (what logs you need) before I do so, no?
AndyYan said:
Done.
I'd need to know how to help (what logs you need) before I do so, no?
Click to expand...
Click to collapse
Just had a quick look, which device you were using to get the logs, it doesn't seem to be a Honor 7x?!
Pretoriano80 said:
Just had a quick look, which device you were using to get the logs, it doesn't seem to be a Honor 7x?!
Click to expand...
Click to collapse
Weird, I didn't have another device at hand when I was taking the logs, I'm fairly certain that it's from my 7X. I do see it mention this in the recovery.log:
Code:
persist.radio.current_version=BND-AL10 8.0.0.331(C00)
I captured logs again just in case.
I was on Oreo beta B331 and am now on LineageOS Treble GSI, if that matters.
AndyYan said:
Weird, I didn't have another device at hand when I was taking the logs, I'm fairly certain that it's from my 7X. I do see it mention this in the recovery.log:
I captured logs again just in case.
I was on Oreo beta B331 and am now on LineageOS Treble GSI, if that matters.
Click to expand...
Click to collapse
As far as i can see, your device is not encrypted! Also, custom roms are not supported yet. I will have a look later, after work, but loke i said, from logs is seems that your storage is not encrypted.
Pretoriano80 said:
As far as i can see, your device is not encrypted! Also, custom roms are not supported yet. I will have a look later, after work, but loke i said, from logs is seems that your storage is not encrypted.
Click to expand...
Click to collapse
Yes, I have modified fstab in vendor to disable storage encryption on /data (various reasons); I don't see how that's related to not being able to mount /system properly, however.
Probably the other guy who reported a similar problem would be able to get you the "clean" logs you need.
AndyYan said:
Yes, I have modified fstab in vendor to disable storage encryption on /data (various reasons); I don't see how that's related to not being able to mount /system properly, however.
Probably the other guy who reported a similar problem would be able to get you the "clean" logs you need.
Click to expand...
Click to collapse
I already know why it's happening in your case, the cause being the unencrypted storage. This TWRP was especially created to support encryption, otherwise there's already official TWRP without encryption support.
However, your logs are still useful! ?
Pretoriano80 said:
I already know why it's happening in your case, the cause being the unencrypted storage. This TWRP was especially created to support encryption, otherwise there's already official TWRP without encryption support.
However, your logs are still useful!
Click to expand...
Click to collapse
Pardon me, but which official? I don't see 7X / P10Lite / M10Lite on official TWRP site.
AndyYan said:
Pardon me, but which official? I don't see 7X / P10Lite / M10Lite on official TWRP site.
Click to expand...
Click to collapse
Oh, my bad, i thought someone already ported TWRP from Mate 10 Pro.
I might be able to fix system unmount issue with unencrypted devices, but i will need your help with testing cause i only have a Mate 10 Pro and it's encrypted. The best solution would be to add a workaround in the current version without building a new one for unencrypted devices.
Pretoriano80 said:
Oh, my bad, i thought someone already ported TWRP from Mate 10 Pro.
I might be able to fix system unmount issue with unencrypted devices, but i will need your help with testing cause i only have a Mate 10 Pro and it's encrypted. The best solution would be to add a workaround in the current version without building a new one for unencrypted devices.
Click to expand...
Click to collapse
I had for some days Mate 10 Lite - rebranded it from c432 to c185 on Android 7 (cause there was not Oreo-Update available for c432) and updated the phone to Oreo with Nocheck Recovery. I tested your TWRP for P10 Lite for Mate 10 Lite - on Stock its working pretty good. I had not any issues.
The owner of the phone like to have a Stock based Custom Rom, I flashed it and tested 3 different TWRPs.
The Dev of the Rom made one, but it does not working properly - Backup /restore without data is only possible on internal storage, no permission to external SD.... Same with two others.
Your TWRP had only issues with data (cause of the modified vendor/etc/fstab.hi6250 - avb and encryption disabled) and issues with system mount/unmount on Custom Rom. But on Stock Rom no issues.
Here are some Logs (from your TWRP). I had not time before to post it
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Note - Iam Not Responsible for bricked devices
About Team win recovery project
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
Installation procedure
Note - download twrp according to your phone security patch
1 . Download twrp-3.4.0-0-DDV_sprout_sprout.img copy in one folder
2. connect phone to pc boot your phone to bootloader mode
3. open cmd in that folder
4. type fastboot devices
5. type fastboot flash boot twrp-3.4.0-0-DDV_sprout.img
6. now get back to phone select recovery mode and now your phone boots in to twrp
7. now flash magisk or what ever your wish and press reboot system
bugs- none
well still you people can flash magisk.zip using sideload
just download magisk.zip & and click on sideload in twrp and open cmd and type adb sideload magisk.zip and after completion reboot system
Download Android 9 Twrp-3.3.1-0 From Here
Download Android 10 Twrp-3.4.0-0 From Here
For More Information About Status Official Click Here
Join Nokia 7.2 Community
XDA:DevDB Information
TWRP 3.4.0-0 , for the Nokia 7.2
Contributors
Raghu varma
My build script: https://github.com/RaghuVarma331/scripts
Source Code: https://github.com/omnirom/android_bootable_recovery
Device Source Code: https://github.com/TeamWin/android_device_nokia_DDV_sprout.git
Version Information
Status: beta
Created 2019-11-07
Last Updated 2020-06-25
Thanx.
Thanx for the effort and hope this phone will have good Custom
ROMs too
nuwanmw1988 said:
Thanx for the effort and hope this phone will have good Custom
ROMs too
Click to expand...
Click to collapse
Soon roms will be out
Does anyone have a stock recovery.img? In case that i will install OTA.
pinh3ad said:
Does anyone have a stock recovery.img? In case that i will install OTA.
Click to expand...
Click to collapse
Nokia 7.2 is an A/B system, not sure where you would get a recovery.img
Additionally, coming from 00WW_1_200 (September update), WiFi module fails after flashing TWRP, and it seems you have to reflash original kernel/boot.img to get the WiFi back. It would be helpful if someone is willing/able to provide it.
KohGeek said:
Nokia 7.2 is an A/B system, not sure where you would get a recovery.img
Additionally, coming from 00WW_1_200 (September update), WiFi module fails after flashing TWRP, and it seems you have to reflash original kernel/boot.img to get the WiFi back. It would be helpful if someone is willing/able to provide it.
Click to expand...
Click to collapse
The reason behind this we need a proper kernel sources from hmd Nokia . For that reason i used prebuilt kernel from stock rom and that rom is based on August so here August kernel & wifi modules signed with different keys and September kernel & wifi modules signed with different keys so here August kernel and September wifi modules signatures are different that's why wifi got broken
Hi Guys,
i'm having a problem, I' able to fastboot flash boot twrp-3.3.1-0-DDV_sprout-9.0-20191119.img but when I restart it, i still not having twrp booting and now, the wireless module is not booting
Anyone to help?
D:\userdata\...\Desktop\Nokia 7.2> fastboot flash boot "D:\userdata\...\Desktop\Nokia 7.2\twrp-3.3.1-PL2.img"
target reported max download size of 536870912 bytes
sending 'boot' (38736 KB)...
OKAY [ 0.849s]
writing 'boot'...
OKAY [ 0.246s]
finished. total time: 1.101s
D:\userdata\...\Desktop\Nokia 7.2> fastboot reboot
rebooting...
finished. total time: 0.002s
JoSoFer said:
Hi Guys,
i'm having a problem, I' able to fastboot flash boot twrp-3.3.1-0-DDV_sprout-9.0-20191119.img but when I restart it, i still not having twrp booting and now, the wireless module is not booting
Anyone to help?
D:\userdata\...\Desktop\Nokia 7.2> fastboot flash boot "D:\userdata\...\Desktop\Nokia 7.2\twrp-3.3.1-PL2.img"
target reported max download size of 536870912 bytes
sending 'boot' (38736 KB)...
OKAY [ 0.849s]
writing 'boot'...
OKAY [ 0.246s]
finished. total time: 1.101s
D:\userdata\...\Desktop\Nokia 7.2> fastboot reboot
rebooting...
finished. total time: 0.002s
Click to expand...
Click to collapse
You have to flash twrp According to your security patch
For example September security patch download from 2019-09-19
For example August security patch download from
2019-08-19
And also if you want to boot back to twrp after flashing twrp and rebooting in to system
Just power off your phone and reboot to download mode and press reboot to recovery now you will boot in to twrp.
If you know what exactly you are doing you won't get confused just follow steps
If you still can't able to boot then you are unlucky because all of the people who viewed this thread successfully booted as well
Hi, I tried to flash this TWRP 2 times, and in all cases the touch does not work. Nokia 7.2 TA-1196. Any ideas how to fix this?
Which TWRP to Flash?
i have model TA-1193 on november 5 security patch, os version is 00ww_1_200_SP01.
was able to successfully un lock bootloader today. Which TWRP should i flash? there are multiple images in https://sourceforge.net/projects/ddv-sprout/files/TWRP/PIE/2019-11-05/\
tried Flashing all the recoveries from the folder, wifi doesnt work.! any help how to fix it?
I wiped my SD card, now instead of 256GB it shows as 16MB, any ideas? Crap, now when i boot into Recovery, i just get a dead robot and 'No Command".
Why do the instructions here say to flash it to the boot partition, but the instructions on the twrp site say to flash it to the recovery partition? IMO recovery makes more sense but I'm no expert.
Which one is correct?
Code:
fastboot flash boot twrp.img
or
Code:
fastboot flash recovery twrp.img
I've had bat luck flashing things to boot in the past so want to make sure.
----- EDIT -----
Nvm my silly question. I've been out of the loop for a while and didn't realise there isn't even a recovery partition anymore. I've now flashed TWRP, boots up fine. No issues with anything on the stock rom afterwards.
However, my question now is how to get TWRP to work with the internal storage? I wanted to make a somewhat stock backup before rooting and the internal storage is full of jibberish folders and files. (See attached image)
CGarz said:
Why do the instructions here say to flash it to the boot partition, but the instructions on the twrp site say to flash it to the recovery partition? IMO recovery makes more sense but I'm no expert.
Which one is correct?
Code:
fastboot flash boot twrp.img
or
Code:
fastboot flash recovery twrp.img
I've had bat luck flashing things to boot in the past so want to make sure.
----- EDIT -----
Nvm my silly question. I've been out of the loop for a while and didn't realise there isn't even a recovery partition anymore. I've now flashed TWRP, boots up fine. No issues with anything on the stock rom afterwards.
However, my question now is how to get TWRP to work with the internal storage? I wanted to make a somewhat stock backup before rooting and the internal storage is full of jibberish folders and files. (See attached image)
Click to expand...
Click to collapse
Well even I appreciate the work of this guy, you have to be careful. 1st - if you on Nokia 7.2 keep in mind that all his stuff based not on Nokia 7.2 sources because Nokia not released any souses yet. 2nd - he warned about it if read carefully. 3rd - all his ROMs for Nokia 7.2 have same trouble as LineageOS and treble. I prefer stay on stock with MicroG, at least all stuff works. 4th - for internal access from twrp you have flash DisableForceEncryption_Treble. Don't use Disable_Dm-Verity_ForceEncrypt_10.20.2019 it has bugs and not works. Just look for same name as I give Disable_Forse_Encryption_Treble. Careful with, it removes encryption but leaves verity in tact. Read all warning about using it, google in help. After reboot in twrp you would read internal and data. Hope that helps. Also check version twrp that he uploading, they base on security patch and I guess it have to match your system. But I'm using fine 11/28 on august security patch.
O, and one more thing - don't relay completely on twrp backups, they not working in 100%, just try restore before. Good luck.
Thanks for the tips boomo15. I ended up installing the Lineage OS rom though.
WiFi works now, data is decrypted and the other system UI crashing bug I had has gone as well. Very pleased with the phone now.
NFC and DDTW don't work and cam quality is poor but even with those issues Lineage is still preferable to me.
CGarz said:
Thanks for the tips boomo15. I ended up installing the Lineage OS rom though.
WiFi works now, data is decrypted and the other system UI crashing bug I had has gone as well. Very pleased with the phone now.
NFC and DDTW don't work and cam quality is poor but even with those issues Lineage is still preferable to me.
Click to expand...
Click to collapse
As I told before stock works best for me, but last week I install AOSP phh_treble version for Pie 123. Since 109 a lot off better.All works smooth and fine, detects my sim card w/o problems (got 1 sim not dual). Replaced camera (crashed all time) with ported by Balu GCam works fine for me. Got one issue - can send sms but can't receive. Tried fix myself but no luck, so asked for help on AOSP treble tread. Hope somebody know what's going on. Don't use NFC can't tell if it works or not.
boomo15 said:
As I told before stock works best for me, but last week I install AOSP phh_treble version for Pie 123. Since 109 a lot off better.All works smooth and fine, detects my sim card w/o problems (got 1 sim not dual). Replaced camera (crashed all time) with ported by Balu GCam works fine for me. Got one issue - can send sms but can't receive. Tried fix myself but no luck, so asked for help on AOSP treble tread. Hope somebody know what's going on. Don't use NFC can't tell if it works or not.
Click to expand...
Click to collapse
That' strange about SMS. Did you set your APN correctly? Or does your carrier auto set it like mine does?
Also for NFC could you see if you have the option for it in settings? It should be around WiFi, Bluetooth, etc.
Hi,
I was trying to install the TWRP recovery but when I saw people in a other XDA forum everyone crying about there WiFi that wont work.
So I was wondering can I install the TWRP recovery without those problems.
Here some info about my phone:
Nokia 7.2 TA-1196
Android version: 9
Security patch level: December 5, 2019
Some help would be appreciated.
VictorAcid said:
Hi,
I was trying to install the TWRP recovery but when I saw people in a other XDA forum everyone crying about there WiFi that wont work.
So I was wondering can I install the TWRP recovery without those problems.
Here some info about my phone:
Nokia 7.2 TA-1196
Android version: 9
Security patch level: December 5, 2019
Some help would be appreciated.
Click to expand...
Click to collapse
Not sure about your version, I got Nokia 7.2 TA-1178 no any problems on stock. The problem that I experienced with was when I used Disable_Dm-Verity_ForceEncrypt_10. - bootloop. For root I used Magisk versions from 19.3-20.2 w/o any problems. Read couple treads above what I used to disable encryption. Also I use w/o problems Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip - it do all job remove encryption and verity if you interested. Also not all backups that I made using TWRP posted here worked.
---------- Post added at 05:31 PM ---------- Previous post was at 05:23 PM ----------
CGarz said:
That' strange about SMS. Did you set your APN correctly? Or does your carrier auto set it like mine does?
Also for NFC could you see if you have the option for it in settings? It should be around WiFi, Bluetooth, etc.
Click to expand...
Click to collapse
Sorry I can't tell you anything about NFC. As I told before can't receive SMS and this I my business phone not playing toy I return back on stock. For me root and removing not wanted stuff enough. Bad that not all my TWRP backups working, have to always format data. Right now I do adb backup.
boomo15 said:
Not sure about your version, I got Nokia 7.2 TA-1178 no any problems on stock. The problem that I experienced with was when I used Disable_Dm-Verity_ForceEncrypt_10. - bootloop. For root I used Magisk versions from 19.3-20.2 w/o any problems. Read couple treads above what I used to disable encryption. Also I use w/o problems Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip - it do all job remove encryption and verity if you interested. Also not all backups that I made using TWRP posted here worked.
---------- Post added at 05:31 PM ---------- Previous post was at 05:23 PM ----------
Sorry I can't tell you anything about NFC. As I told before can't receive SMS and this I my business phone not playing toy I return back on stock. For me root and removing not wanted stuff enough. Bad that not all my TWRP backups working, have to always format data. Right now I do adb backup.
Click to expand...
Click to collapse
Okay lets not try it this is my main phone :/
I tried to build TWRP myself using your device tree and the latest stock kernel that I extracted from the OTA. The result was a working wifi module, but whenever I set a device unlock PIN, entering the correct PIN doesn't unlock the device. It just says "Wrong PIN". Do you have any thoughts about what could be happening? I'm at a loss.
This is a guide how I flashed Android 10 to my Cubot Power.
Preparation:
HINT:
Make a Backup! You will definitely loose all your data on the phone due to several factory resets!
First make sure your Device can use treble and also which one you need with this app:
https://play.google.com/store/apps/details?id=tk.hack5.treblecheck
(according to this post https://forum.xda-developers.com/pr...velopment/aosp-10-0-quack-phh-treble-t3992559)
note down:
Architecture: (Cubot Power: arm64)
System as Root: (Cubot Power: A-only)
then you will need fastboot and adb:
Windows:
https://forum.xda-developers.com/showthread.php?t=2588979
Linux:
Code:
sudo apt-get install android-tools-adb
Code:
sudo apt-get install android-tools-fastboot
Then you need twrp Recovery or something similar. Cubot Power is not supported by the official twrp project, but there is this unofficial version:
https://unofficialtwrp.com/twrp-3-2-3-recovery-cubot-power/
And you will probably need gapps:
https://opengapps.org/
For cubot power you will need "arm64" and "anrdoid 10" of course.
For the variant version I went with "nano" but you can probably choose what you like.
If you have a external sd card you want to copy the gapps, supersu and no-verty-opt-encrypt ZIP onto it.
Now download the android 10 treble image from:
https://github.com/phhusson/treble_experimentations/releases?after=v211
For the Cubot Power i went for the system-quack-arm64-aonly-vanilla.img.xz. But you should select the right one according to the treble app.
I went for vanilla because with gapps it did not seem to work.
Optional:
From this site:
https://romprovider.com/cubot-power-root-twrp/
Download SuperSu (https://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip)
and no-verty-op-encrypt (https://romprovider.com/download-no-verity-opt-encrypt-version/)
this prevents bootloops.
In case something goes wrong have your stock rom and sp flash tool ready:
Cubot Power: http://forum.cubot.net/viewtopic.php?f=21&t=2419
Flashing
Make sure your phone is charged probably. Booting might take up to an hour. At least 70% is recommended.
Go to developer settings and enable usb -debugging and disable oem.
now type:
Code:
adb reboot bootloader
the device should now restart and boot into fastboot
now disable oem in fastboot and unlock flashing: (WARNING: this will factory reset your phone)
Code:
fastboot oem unlock
Code:
fastboot flashing unlock
now we want to "install" twrp:
Code:
fastboot flash recovery TWRP_cubot_power-030918.img
--(Optional) check if twrp is working:
Code:
fastboot reboot
and restart with the volume up button
in twrp go to mount and check if you can mount data. If not: https://appuals . com/how-to-fix-twrp-unable-to-mount-storage-internal-storage-0mb/.
Make a Backup. Then wipe "dalvik cache", "cache" and "data"
Then go to install and install no-verty-op-encrypt.
then got to reboot and select bootloader.
--
continue with flashing android 10:
unzip the xz file
Code:
fastboot flash system system-quack-arm64-aonly-vanilla.img
this might take a while.
Then reboot
Code:
fastboot reboot
now your phone should boot into android 10. This can take very long for me it took about 30 minutes. If it takes longer then one hour you can probably start troubleshooting.
Install google apps(playstore)
once it has booted you either can start the login process and enable usb debugging again and reboot into recovery:
Code:
adb reboot recovery
or turn it off and restart into twrp (power button and volume up).
In twrp again check if you can mount data (see the optional step).
Make a Backup. Then wipe "dalvik cache", "cache" and "data"
Install super su and gapps.
Now reboot to system.
Now again the phone will boot a very long time (up to a hour).
Conclusion:
For me it is pretty stable but sometimes the fingerprint sensor does not work or the sim card is not recognized. But a reboot fixes it (sometimes).
But rebooting always takes time. At least 5 minutes sometimes up to 30 minutes. Once the system is booted there are no feel-able performance issues.
Hy there !
My Treble Info says:
Trable & VNDK supports old Version with VNDK version 27.0
System as Root:
Not supported, use A-only-OS
Will this flash to Android 10 work on this Cubot Power ?
The Phone is currently rooted.
regards
Al
Virtu-Al said:
Hy there !
My Treble Info says:
Trable & VNDK supports old Version with VNDK version 27.0
System as Root:
Not supported, use A-only-OS
Will this flash to Android 10 work on this Cubot Power ?
The Phone is currently rooted.
regards
Al
Click to expand...
Click to collapse
Probably it will work, but I can give you no guarantee for that.
Thank you!
Hi Johanno,
Thank you for this great tutorial! I think I already downloaded the treble check tool in March and I also found the github page, but I didn't find any experience on the net related to Cubot Power, so I didn't dare to upgrade.
Did you try later releases?
Should I go with latest release v222 or do you know about any change in v211 that prevents us from upgrading to a later version? ( your link in the tutorial shows only older versions: https://github.com/phhusson/treble_experimentations/releases?after=v211 )
Did you use windows or linux?
Did you experiment with V25 ROM?
https://www.cubot.net/platform/Support/detail/id/192/cid/23.html
Br,
taarzaan
I'm trying the latest release v222. I'm after the last reboot. It's not fast, but I would say it's less than 30 minutes. It should boot in 5 or 10 minutes.
Br,
taarzaan
Results of my experiments
Fingerprint sensor has similar issues like other Cubot devices:
https://github.com/phhusson/treble_experimentations/issues/1273
https://github.com/phhusson/treble_experimentations/issues/1319
I failed to install MS Outlook, Office, Company Intune app and things like that. I tried to unroot the phone, but it didn't help.
Maybe this Magisk thing worse a try next time:
https://github.com/phhusson/treble_experimentations/issues/31
https://github.com/phhusson/treble_experimentations/issues/909
Br,
taarzaan
Virtu-Al said:
Hy there !
My Treble Info says:
Trable & VNDK supports legacy Version with VNDK version 27.0
System as Root:
Not supported, use A-only-OS
regards
Al
Click to expand...
Click to collapse
hi
i just want to understand what is legacy version? and vndk27 ? i googled but few info
my phone say same info here
i ll post the results but if one could explain those 2 things
thank u in advance
taarzaan said:
Fingerprint sensor has similar issues like other Cubot devices:
https://github.com/phhusson/treble_experimentations/issues/1273
https://github.com/phhusson/treble_experimentations/issues/1319
I failed to install MS Outlook, Office, Company Intune app and things like that. I tried to unroot the phone, but it didn't help.
Maybe this Magisk thing worse a try next time:
https://github.com/phhusson/treble_experimentations/issues/31
https://github.com/phhusson/treble_experimentations/issues/909
Br,
taarzaan
Click to expand...
Click to collapse
notes for the next experiment (we should open a proper ticket for phhusson):
"What does "can't be used" mean? Does the pone vibrate? Does screen lights on? If you go in Fingerprint settings, do you see the enrolled fingerprint? Can you enroll a second one? If you press your fingerprint sensor when you're on that screen, what happens?"
I've tried with both v211 and v222 - but I don't seem to get past boot screen.
After using fastboot flash (and I've also tried SP flash tool flash) the phone shows cubot boot screen (with a warning about "orange mode" not being trusted) and can boot into TWRP but when booting system it shows a black screen with white slowly flashing "android" for a long time. More than one hour. I lose faith and re-install stock each time.
Any ideas how to debug and see what's happening?
Any improvements to this? I am having a P20/cubot and had same problems. AOSP v222 does not boot but I tried lineage-17.1-20201215-UNOFFICIAL-treble_arm64_avS.img.xz from https://sourceforge.net/projects/andyyan-gsi/files/lineage-17.x/
Surprise. it works but a bit slowly. Due to large battery I am thinking of cubot power?
I have 2 questions:
1. Can you please try the lineage-17.1 rom?
2. BTW, did AOSP8 work OK in cubot power? (i like oreo more than android 10)
Thanks for your replies.
htorsten2020 said:
1. Can you please try the lineage-17.1 rom?
Click to expand...
Click to collapse
Thanks, sorry, I'll check it only next month. Any other issues besides slowness?
htorsten2020 said:
2. BTW, did AOSP8 work OK in cubot power?
Click to expand...
Click to collapse
I don't know what you mean. Do you mean treble roms? I haven't tried any yet.
taarzaan said:
Thanks, sorry, I'll check it only next month. Any other issues besides slowness?
Click to expand...
Click to collapse
Call/SMS/data stability. A lot of devices that came with oreo (vendor) have lots of issues with signal (mobile SIM) dropping after some hours. Thanks
taarzaan said:
I don't know what you mean. Do you mean treble roms? I haven't tried any yet.
Click to expand...
Click to collapse
Cubot Power ships with Android 8.1 (oreo). So I asked if you tried the old AOSP from phhusson (v32 - this is AOSP8 equivalent treble ROM). I found the AOSP from the same version (oreo as the device) is faster than installing newer ROM.
Hi guys, as you may have noticed I am not very active here ;-)
I actually went back to stock firmware after a few weeks because I couldn't get the phone working again. And since I want to use my smart phone and not tinker on it every few days I gave up. But now I am thinking about using Lineage os.
But first I need to back up everything and that's probably the thing that will hinder me the most.
Hi. I provide you my story with CUBOT power. It took me 2 days. I worked with a device that was never before modified. Guide on this page is very helpful. Johanno thank you very much!
By TWRP install an Orange mode has been triggered (you see small black text on the white screen with CUBOT POWER logo during boot. First I went step-by-step from this guide and I installed AOSP 11.0 v313. But it didnt want to boot because of boot loops. The no-verty-op-encrypt (last version) solved. I did not installed before because I did not want any root (I dont need). The boot time itself is really very long (I did not measure but guess 30 minutes) and after boot 3 buttons at bottom of screen (back/home/change task) were missing. As it was first run of fresh installed Android maybe restarting could help maybe not. I did not try because the boot time is really unacceptable...
Then I downloaded LineageOS 18.1 (lineage-18.1-20220120-UNOFFICIAL-treble_arm64_avS) and tried this one (before install I wiped cache, data, dalvik cache). After install phone started booting - there was some screen about encrypting partitions or so, then animation and there it frozen (I let it run full night without progress). At morning I turned phone off and on and it surpriesd me by just normal boot of working LineageOS 18.1.
Boot time is completely normal (lets say up to 3 minutes) each time I restart.
I tried fingerprint sensor - it works but maybe daily usage is not 100% reliable (Few times during phone unlock it completely ignored fingers). But honestly this sensor is not reliable (from past experiences)
Original LineageOS camera app cannot change some camera settings (I think ISO) because you see only very dark image. But after install F-droid and Simple camera app then it just works without issues.
Another issue i found was the night mode - you will find out that the "low temperature white" color is not stable - it flickers little bit. After some time it started bothering me. I completely solved it by activating developer mode and there I turned on some graphics hardware acceleration (I dont understand why is it turned off by default). Videos playback is working with this with no issues.
This lineageOS has 2 "Music" apps. I did not study the difference but one works and other one crashes.
I did not find any other issue. Gapps works (I installed nano), our local bank apps work (no issues cased by "Orange mode").
kezyr said:
Hi. I provide you my story with CUBOT power. It took me 2 days. I worked with a device that was never before modified. Guide on this page is very helpful. Johanno thank you very much!
By TWRP install an Orange mode has been triggered (you see small black text on the white screen with CUBOT POWER logo during boot. First I went step-by-step from this guide and I installed AOSP 11.0 v313. But it didnt want to boot because of boot loops. The no-verty-op-encrypt (last version) solved. I did not installed before because I did not want any root (I dont need). The boot time itself is really very long (I did not measure but guess 30 minutes) and after boot 3 buttons at bottom of screen (back/home/change task) were missing. As it was first run of fresh installed Android maybe restarting could help maybe not. I did not try because the boot time is really unacceptable...
Then I downloaded LineageOS 18.1 (lineage-18.1-20220120-UNOFFICIAL-treble_arm64_avS) and tried this one (before install I wiped cache, data, dalvik cache). After install phone started booting - there was some screen about encrypting partitions or so, then animation and there it frozen (I let it run full night without progress). At morning I turned phone off and on and it surpriesd me by just normal boot of working LineageOS 18.1.
Boot time is completely normal (lets say up to 3 minutes) each time I restart.
I tried fingerprint sensor - it works but maybe daily usage is not 100% reliable (Few times during phone unlock it completely ignored fingers). But honestly this sensor is not reliable (from past experiences)
Original LineageOS camera app cannot change some camera settings (I think ISO) because you see only very dark image. But after install F-droid and Simple camera app then it just works without issues.
Another issue i found was the night mode - you will find out that the "low temperature white" color is not stable - it flickers little bit. After some time it started bothering me. I completely solved it by activating developer mode and there I turned on some graphics hardware acceleration (I dont understand why is it turned off by default). Videos playback is working with this with no issues.
This lineageOS has 2 "Music" apps. I did not study the difference but one works and other one crashes.
I did not find any other issue. Gapps works (I installed nano), our local bank apps work (no issues cased by "Orange mode").
Click to expand...
Click to collapse
hi, how exactly did you install the lineageos 18.1 with the twrp 3.2.3? thank you in advance for your help
i just get boot loop on every rom i try on cubot power
I had the same problem and gave up
I tried using the XDA Discord server to get a quick response, but apparently, some people just ignore me or don't even know how to help me. So I will try here...
I was following that tutorial so that I can use Joycon Droid on my phone. I installed TWRP Recovery and gone in his recovery mode. I wiped what the tutorial asked to wipe and began the flash process. Unfortunately, I mistakenly downloaded the flash files on the computer. I tried removing my SD Card and putting inside it the files I need, but TWRP was not able to read any data for the SD Card. So I tried to find a way to cancel the recovery menu, and I did by clicking Reboot System. Since then, my phone was locked in the logo screen. After many attempts, I've gone from the charging screen and finished by the "An error occurred while updating the device software.". I can enter the download mode, but nothing else. My phone is an A520W and I think the root was not properly installed. I researched everywhere without any solution, so I came to this discord server, hoping someone would save my phone. I tried flashing the official A520W OS, but Odin always does a FAIL message or freezes. I later tried to use another firmware file, reinstalled the Samsung USB driver and Odin, and know it says on the Download Mode screen:
SV REV. CHECK FAIL(BOOTLOADER) DEVICE: 9, BINARY 7. (it failed)
Can someone help me? I really need help!
Your phone partition table is crushed probably!
Use emmc programmer to repairing your partitions! (ask from someone expert)
Also, "easy-jtag" may be useful(search this)
matkali said:
Your phone partition table is crushed probably!
Use emmc programmer to repairing your partitions! (ask from someone expert)
Also, "easy-jtag" may be useful(search this)
Click to expand...
Click to collapse
Kay I'll try the easy-jtag, but if it doesn't work, who is an expert at emmc programming stuff?
Is there a way to fix the crushed partition table without buying stuff?
Ok so, I used a certain program that added galaxy s6 data and now it is stuck in bootloop
Akurio64 said:
Ok so, I used a certain program that added galaxy s6 data and now it is stuck in bootloop
Click to expand...
Click to collapse
better than the error screen right? the program name is fonepaw
Akurio64 said:
Ok so, I used a certain program that added galaxy s6 data and now it is stuck in bootloop
Click to expand...
Click to collapse
It is dangerous for your phone, because every phone have different partition table and different architecture!
Pit file in a520w stock firmware have partition table structures information. (use PIT_Magic.exe to see)
In old architecture of Samsung(e.g. s3) when partition table cleaned from emmc (phone internal storage), they use micro sdcard to boot from it! (to identity correct info for Odin) (same boot from USB when you are installing windows.) then by going to download mode they flash stock Rom!
But I suggest to you find one knows enough information and requirements stuffs.