Database Info

[Q] Why my Galaxy Note 2 is showing as t03g and can't flash CM mod?

I am trying to flash my Galaxy note 2 (AT&T I-317). I can get into recovery mode but when flashing the rom it will always be unsuccessful and showing infomation as "your device is 't03g' and the rom you flashed is not compatible" From the CM website, seems the correct name of my device is 't0lteatt'. I have no idea why my device is detected as 't03g' and hoping anyone knows how to solve this problem.
My previous ROM is MyMIUI ROM based on android 4.1. Thanks in advance!

TWRP does not work

I attempted to flash my Samsung Galaxy note 10.1 2014 edition WI-FI tablet for the first time. When I attempted to Install TWRP it displayed an error message and rebooted my device into a TWRP UI. The touch screen would not work, prevemting me from doing anything on this UI. does anyone know how I could bypass TWRP or reinstall an older more reliable version?

Basic answer is do nothing until you understand .
Suggest you post this in the Note 10.1 2014 forum and use TWRP for your model as it reads as you have flashed for a different product .

[Completed] Can't update Samsung SCH-I415 - Status 7 error

Hi all,
I have problem updating my generally new Samsung SCH-I415 Stratosphere 2. I got an update package ZIP, that has been downloaded by Phone form Verizon directly. I took it to my SD card and tried to flash from stock recovery, but it has status 7 error. Phone was probably rooted before and now, on welcome screen, it shows unlocked padlock above Custom notification. I have managed to make system status to normal, but it didn't changed much - still got status 7 error. Is there any option to flash/install this update.zip on that phone? There is no firmware available for this model, no custom ROM or recovery. Please help :/
PS is there any modification to do in update.zip that I could make, to run it propely? I have found that in update-script I should remove some assert line, but when I have done that, it says ZIP signature failed.

Ok, I finally got it - it's really hard to find Odin flashable firmware to this device. Here it is: http://updato.com/firmware-archive-select-model?q=sch-i415&exact=1

Damn. I have downloaded updates from verizon and tried to flash again that firmware. Now I got "firmware upgrade encountered an error". Is there any chance to fix it/or get into recovery to factory reset?

Hi !
Thus thread isn`t for your device but it looks like it`s a workaround
https://forum.xda-developers.com/showthread.php?t=2088809
Good luck !

This model is not supported by kies unfortunatelly....

Can't install ROM on Note 10.1 3G (2012; GT-N8000; p4notewifi)

Hello guys,
I'm trying to install via TWRP v.2.8.6.0 different versions of CM ROMs.
(e.g. cm-12.1-20151027-UNOFFICIAL-n8000; cm-13.0-20160901-UNOFFICIAL-n8000)
I always get an error message saying: "This package is for device c0, p4noterf, n8000, GT-N8000; this device is ."
Is the ROM wrong? It always says, it's for device p4noterf. I have p4notewifi. Is there any specific ROM for this version?
Thanks for the help.

what exactly is the cause of "INSTALL_FAILED_VERIFICATION_FAILURE"

I run into this error's:
Zeff:
adb install com.huami.watch.hmwatchmanager-100395.apk
adb: failed to install com.huami.watch.hmwatchmanager-100395.apk: Failure [INSTALL_FAILED_VERIFICATION_FAILURE]
Mi Fit:
adb install com.xiaomi.hm.health-50429.apk
adb: failed to install com.xiaomi.hm.health-50429.apk: Failure [INSTALL_FAILED_VERIFICATION_FAILURE]
And I wonder what the real cause is.
Background:
the device is an Galaxy Tab A 10.1 2019 (SM-T510) with lastest stock.
since the lastest stock [1] is on the device I even can't see the above apps in playstore (running playstore on the device) and trying to install via webbrowser (from playstore site) it gives on error, something like "app not compatible with the device"
the device is listed as an playstore-compatible device list though.
I'm able to install other apps, but not the above both.
When I had @Magendanz Nexus [2] on the device I had no trouble with Mi Fit.
Mistakenly I downloaded and flashed the lastest stock instead of what @Magendanz suggested for his Nexus and I'm unable to go back to that previous stock (Odin denies the downgrade: 5 => 4)
I now have T510XXS5BUC4 instead of T510XXU4BUA1.
Interestingly I'm able to flash @Magendanz TWRP build on the previous stock [3]
I've searched the forum and found a link to this page:
android_frameworks_base/PackageManager.java at pac-5.0 · PAC-ROM/android_frameworks_base
Contribute to PAC-ROM/android_frameworks_base development by creating an account on GitHub.
github.com
But I can't even find out what the *deeper* cause of this error's are.
Idea's ???
[1]
https://samfrew.com/model/SM-T510/region/DBT/
[2]
[ROM][11.0][UNOFFICIAL] Nexus Stock for 2019 Galaxy Tab A 10.1 [SM-T510]
Well, we're finally getting some relatively stable builds of AOSP GSIs and OpenGApps for Android 11.0, so here's my first effort at migrating the Nexus Stock custom ROM for the 2019 Galaxy Tab A 10.0 [SM-T510] to the latest Android OS release...
forum.xda-developers.com
[3]
[RECOVERY][UNOFFICIAL] TWRP 3.7.0 for 2019 Galaxy Tab A 10.1 [SM-T510]
After @geiti94 and @ianmacd started the ball rolling for the Samsung Galaxy S10 series (Exynos 9820), it was really only a matter of time until we could do the same for the 2019 Galaxy Tab A 10.1 (Exynos 7904). The kernel source was released...
forum.xda-developers.com

rw_on_xda said:
I run into this error's:
Zeff:
adb install com.huami.watch.hmwatchmanager-100395.apk
adb: failed to install com.huami.watch.hmwatchmanager-100395.apk: Failure [INSTALL_FAILED_VERIFICATION_FAILURE]
Mi Fit:
adb install com.xiaomi.hm.health-50429.apk
adb: failed to install com.xiaomi.hm.health-50429.apk: Failure [INSTALL_FAILED_VERIFICATION_FAILURE]
And I wonder what the real cause is.
Background:
the device is an Galaxy Tab A 10.1 2019 (SM-T510) with lastest stock.
since the lastest stock [1] is on the device I even can't see the above apps in playstore (running playstore on the device) and trying to install via webbrowser (from playstore site) it gives on error, something like "app not compatible with the device"
the device is listed as an playstore-compatible device list though.
I'm able to install other apps, but not the above both.
When I had @Magendanz Nexus [2] on the device I had no trouble with Mi Fit.
Mistakenly I downloaded and flashed the lastest stock instead of what @Magendanz suggested for his Nexus and I'm unable to go back to that previous stock (Odin denies the downgrade: 5 => 4)
I now have T510XXS5BUC4 instead of T510XXU4BUA1.
Interestingly I'm able to flash @Magendanz TWRP build on the previous stock [3]
...
But I can't even find out what the *deeper* cause of this error's are.
Idea's ?
Click to expand...
Click to collapse
Your device is (now) not listed as compatible for those apps.
Either there were no longer available for your device, or something has changed by flashing latest stock firmware version ... what Google play service is checking.
Have you been on plain stock firmware before? Or have you rooted and changed some system settings?

It_ler said:
...or something has changed by flashing latest stock firmware version ... what Google play service is checking.
Have you been on plain stock firmware before? Or have you rooted and changed some system settings?
Click to expand...
Click to collapse
That's the background of my question:
what and how does google check.
FW was:
initial stock (elder) => nexus => Lineage OS => stock (lastest) => CaOS
with Caos all is fine again. with nexus and LOS is was fine too.
no root
no change of system setting