Develop Bugs

[GUIDE] Flash T-Mobile Galaxy Tab so that it makes calls with any sim (EDGE only)

DISCLAIMER: I AM NOT RESPONSIBLE FOR YOUR ACTIONS. IF YOU BRICK OR DAMAGE YOUR DEVICE IN SOME WAY, IT IS YOUR RESPONSIBILITY. THERE ARE SOME STEPS THAT MIGHT NOT BE LEGAL IN SOME COUNTRIES (CHANGING IMEI NUMBERS), AND I WILL NOT BE HELD RESPONSIBLE FOR THAT EITHER. EVERYTHING YOU DO WITH YOUR DEVICE IS YOUR OWN RESPONSIBILITY AND IF YOU FOLLOW ALL THESE STEPS YOU ARE AGREEING TO THAT. THIS TUTORIAL IS DONE FOR EDUCATIONAL PURPOSES.
Thanks to clubtech, rotohammer, koush, ayman07 and everyone in xda that has worked hard to make this possible. I did not come up with any of this, I only gathered it all from different sources and smashed it all together in an easy-to-read guide. Credit is due to all of those listed above, if I missed anyone please do let me know and I'll gladly add you here.
You will need
- P1000XWJJ4 firmware (pass: samfirmware.com)
- P1000XXJK5 firmware (pass: samfirmware.com)
- Odin 1.3
- Koush's zImage for T-Mobile Galaxy Tab
- flash_image
- I900AOJP3.bin Modem from HERE
1) Put you tab into download mode (Turn it off, when it's off, Press VolDown+Power until you see a yellow android and it says downloading...) (WARNING: All your data will be lost in the next step! Everything, INCLUDING the internal memory! Make sure to back everything up to your computer!)
2) Use Odin: Flash P1000XWJJ4 (PDA button) with P1_add_hidden.pit and make sure "Re-partition" is SELECTED, press Start and wait for it to finish. The device will reboot and it will turn on again, probably in russian.
3) Turn it off and put it on download mode again.
4) Use Odin: Press the reset button, then make sure "Re-partition" is UNSELECTED and there's NO PIT file, then flash P1000XXJK5 under "PDA".
5) The device will reboot with the latest euro firmware in english. The modem will probably be undetected, the device will be working kinda crazy (It might be slow and whenever you use something that uses the vibrator it'll get worse, the vibrator won't probably work, don't worry about this, it will be fixed in the next few steps)
6) Make sure you have flash_image and the tmobile_zImage in hand and issue these commands:
Code:
adb push flash_image /data/local/bin/flash_image
adb push tmobile_zImage /sdcard/
adb shell
su (make sure to select "Allow" when the Superuser dialog pops up on the tab)
chmod 755 /data/local/bin/flash_image
/data/local/bin/flash_image boot /sdcard/tmobile_zImage
sync
exit
7) Now, the kernel should be flashed, a reboot should fix all the weirdness. However, instead of rebooting, turn it off, and put it on download mode again (VolDown+Power)
8) Use Odin: Press reset on Odin, make sure "Re-partition" is UNSELECTED, and on the Phone button, flash the modem I900AOJP3.bin.
11) Wait for it to reboot. At this point, the tab should work fine, and the modem should be detected by the system. However, you won't be able to make calls or use the internet because T-Mobile is blocking data. Now, we need to change the IMEI number (READ DISCLAIMER ABOVE!)
12) Now, we need to backup all the contents in the /efs folder, that way, the IMEI will be corrupted, we want this to happen because T-Mobile is blocking the IMEIs on all T-Mo Galaxy Tabs so that data doesn't work unless you have the right plan/contract (BAD MOVE T-MO! WE DIDN'T EXPECT THAT FROM YOU, AT&T MAYBE, BUT NOT YOU!)
13) Backup the /efs folder (Notice: you must have busybox installed, get busybox installer from the market)
Code:
adb shell
su
busybox tar zcvf /sdcard/efs-backup.tar.gz /efs
busybox cat /dev/block/stl3 > /sdcard/efs_dev-block-stl3.img
exit
back to the shell in your computer, now use these commands to put those files in your computer, and save them somewhere safe.
Code:
adb pull /sdcard/efs-backup.tar.gz .
adb pull /sdcard/efs_dev-block-stl3.img .
14) Delete all contents from /efs and reboot. Easiest way to do it is using root explorer from the market. DO NOT DELETE THE ACTUAL FOLDER, JUST IT'S CONTENTS.
15) Done, you will be able to browse the web, send/receive SMS, and send/receive voice calls. The only issue at this moment is that it will only work on EDGE, 3G is not possible, YET.
Enjoy.

This method was posted earlier and is much easier i'd say. Thanks.

LordLugard said:
This method was posted earlier and is much easier i'd say. Thanks.
Click to expand...
Click to collapse
Where exactly? Please link me to the post that makes your T-Mo Tab make calls, using the Euro firmware and vibrator works and the tab doesn't go crazy.
As I said, all the guides I found were missing a few pieces. One was for AT&T Tabs, but I didn't find one that was for T-Mo tabs in a single piece, everything was scattered all around.
Sent from my mobile

velazcod said:
Where exactly? Please link me to the post that makes your T-Mo Tab make calls, using the Euro firmware and vibrator works and the tab doesn't go crazy.
As I said, all the guides I found were missing a few pieces. One was for AT&T Tabs, but I didn't find one that was for T-Mo tabs in a single piece, everything was scattered all around.
Sent from my mobile
Click to expand...
Click to collapse
The exact link i posted is how i got my Tmo Tab flashed to Euro firmware with calls and 2G data. Much easier steps. Not berating your method.
http://forum.xda-developers.com/showthread.php?t=886714
EDIT** Didn't realize i didn't post link in first reply.

LordLugard said:
The exact link i posted is how i got my Tmo Tab flashed to Euro firmware with calls and 2G data. Much easier steps. Not berating your method.
http://forum.xda-developers.com/showthread.php?t=886714
EDIT** Didn't realize i didn't post link in first reply.
Click to expand...
Click to collapse
Oh ok, didn't notice that also works for T-Mo tabs. Oh well.
Thanks.

Thanks for posting this guide. I followed the instructions and still cannot make phone calls. It seems to dial but the T-Mobile automated voice operator says "The phone you are using does not allow outgoing calls."
I removed all /efs files and rebooted, then verified that the IMEI was corrupt afterwards.
Any ideas? Maybe T-Mobile is blocking the corrupt IMEI number now?
Thanks in advance!

Are you able to use the market ok with your imei corrupted?

droooid said:
Thanks for posting this guide. I followed the instructions and still cannot make phone calls. It seems to dial but the T-Mobile automated voice operator says "The phone you are using does not allow outgoing calls."
I removed all /efs files and rebooted, then verified that the IMEI was corrupt afterwards.
Any ideas? Maybe T-Mobile is blocking the corrupt IMEI number now?
Thanks in advance!
Click to expand...
Click to collapse
I don't think so. Are you using a SIM card with a plan that has phone calls or are you using the same SIM card? Your Tab has a webConnect plan that does not allow phone calls, so you need to put in a SIM card that has data and calling plan.
They are blocking the IMEI for data, as far as I know, so if you use your tab to go online (without using Wifi), and it goes to my.t-mobile.com even if you try to go to xda-developers.com then they are blocking it, but in your case, it's just probably the calling plan.
calebchosen said:
Are you able to use the market ok with your imei corrupted?
Click to expand...
Click to collapse
Yes sir, Market works, it even updated itself to the latest version.

T-Mobile usa modem
sorry voice failed 3 times. sorry again will update if i can figure out why I lost voice after getting it to work.
the attached file is the original t-mobile galaxy tab modem. NO VOICE but 3G on EUROFIRMWARE

hi zdentist now m use Tmobile with EURO ver all work fine
but i can get 3G data what can i do Enable 3G service ??
this MODEM.BIN work my Tmobile euro ver?

Why make this so difficult? Just flash modaco's custom rom and kernel for Tab with Odin and its done...

USED TMOBILE TAB WITH EURO VER CALLING WORK FI9 BUT CANT USE INTERNET WITH SIM DATA
AND ALSO CONFORM THAT THIS IS POSSIABLE I USE 3G DATA IN TMOBILE?
m using this tab ver

fahadz said:
USED TMOBILE TAB WITH EURO VER CALLING WORK FI9 BUT CANT USE INTERNET WITH SIM DATA
AND ALSO CONFORM THAT THIS IS POSSIABLE I USE 3G DATA IN TMOBILE?
m using this tab ver
Click to expand...
Click to collapse
Did you get your answer from the modem switcher thread? PM me if you're still stuck.

fahadz said:
hi zdentist now m use Tmobile with EURO ver all work fine
but i can get 3G data what can i do Enable 3G service ??
this MODEM.BIN work my Tmobile euro ver?
Click to expand...
Click to collapse
sorry for the late reply. yes but you won't be able to make voice calls with this modem.bin file only DATA unfortunatley

Asia Firmware DXJM4

Reference http://www.samfirmware.com/WEBPROTECT-p1000.htm
Saw under the Asia Firmware 'P1000DXJM4 ## ODIN 1.7 | P1.PIT | Version 2.2 | 2010 December' is available and to be cautious, i seek seniors' opinion before i go ahead and flash mine ^^
Any recommendation on how to proceed is appreciated, esp with ODIN (dont know what it is even read so much about this word)!
I already backup with TB
edit: Connect to Kies and says 'This device's version cannot be updated.' Stating PDA: JK2 / Phone: JJ2 / CSC: JJ2. now even more confused
edit update after flashed JME instead of JM4 (long story short):
"i will write down the event by event of recovery as reference:
1. flash the JVJL1 (no problem on reboot) by mistake then flash JM4 (missing dbdata.rfs) tar file downloaded from samfirmware.com and failed to reboot due to the missing file.
2. did some silly step and resulted in (phone .. ! .. pc) icon
3. run odin 1.7 and plug the usb and odin show is connected with tab
4. flash JM4 (yes with missing dbdata.rfs) and able to bring the tab back to download mode but unable to reboot into tab
5. flash Roto's dbdata.rfs file (http://forum.xda-developers.com/show...91&postcount=1) and able to reboot right after but missing pda & csc info (*#1234#)
6. tried the hard reset (http://forum.xda-developers.com/show...&postcount=106) but no help
7. download Roto's pre-rooted JME 3 files as mentioned (http://forum.xda-developers.com/showthread.php?t=895827) and finally boot the tab with full *#1234# details.
* So if you see the (phone .. ! .. pc) icon dont panic. like KChauJen said, able to solve with enough reading. i listed my route to recovery as reference to give you positive hope to retry.
TB's backup in Internal SD and before flashing JME, i copied the TB folder to my hdd during the missing pda & csc boot and did a backup on JME reboot, copy paste back to TB folder under internal sd and the restore work flawlessly."

cant be updated? er, i was from jk2 to jm4. did you applied oclf? if you did, try undo it b4 anything.

Hi fastcx, thanks for replying and sharing your experience. I did some further reading in some singapore forum saying have to run the kies patch (http://forum.xda-developers.com/showthread.php?t=835628) and spoof firmware version in order to update. i have yet to try due to somewhere in the same forum also said that once updated:
1. cant go back version
2. z4root wont work (which i am already using)
may i know have you rooted your SGT? need more solid info before taking the route to update the firmware as already using SGT as my primary device. I havent OCLF yet

rooted, since day 1, after every update (jj1>jj2>jk2) able to root with z4root till jm4 which requires SOC(SuperOneClick). To use kies, switch back to samsung default launcher b4 u connect using kies. I do not have any issue there. Another note is that after root, i always go back to /system/app to check n remove any apps that I do not need using adb shell.
The interface changed, to darker color, dlna client really working now, oclf performance improvement might not be obvious this time around. I suspect they really optimized it, everything is more stable now. Over protective I would say, cause any previous flashlight apps isnt going to sustain the led light for over 2sec. Default browser is a wee bit smoother now.
SuperOneClick is very easy to use anyway, so give it a try, oclf is useful only when u have over 400mb apps + loads of sms & contacts..anything related to I/O will have improvement.
The worse case scenario is just if kies still do not allow u to update, just use odin..what did you do previously? How do you update previously?

VNPython said:
Reference http://www.samfirmware.com/WEBPROTECT-p1000.htm
Saw under the Asia Firmware 'P1000DXJM4 ## ODIN 1.7 | P1.PIT | Version 2.2 | 2010 December' is available and to be cautious, i seek seniors' opinion before i go ahead and flash mine ^^
Any recommendation on how to proceed is appreciated, esp with ODIN (dont know what it is even read so much about this word)!
I already backup with TB
edit: Connect to Kies and says 'This device's version cannot be updated.' Stating PDA: JK2 / Phone: JJ2 / CSC: JJ2. now even more confused
Click to expand...
Click to collapse
Yeah... I'm in your case.
Thinking does it would be updated or not???
1. cant go back version
2. z4root wont work (which i am already using)
Click to expand...
Click to collapse
Just look at inside of tar file, and according to the Chainfire's Warning, the three files:
* boot.bin
* Sbl.bin
* zImage > 7,000K
So, this firmware would be has the protected boot loader. It would give us a lot of trouble in the future of updating and downgrading.
I think, this firmware can be updated with the help from Roto, eliminate the three files above and just take the PDA part.

I was using CSC: XEV (Vietnam) then to SIN (Singtel) and feel good and when Nov'10 update came, updated via Kies wihtout any trouble. When Dec'10 update came, tried with SIN resulted unable to update, switch back to XEV also resulted unable to update. I havent try XSO which the singapore forum stated successful for those with that CSC.
So i have to try to switch to XSO and report in later. be it protected boot loader or not, as long as we want stable and more 'juice' to service our daily SGT needs, no choice but to follow. I do believe as days goes, seniors like Roto alike will crack the nut for us to appreciate further.
on other note, my default email (not gmail) app seem got problem whenever you click reply or forward any email will result in force close. do not know if this bug related to after i switch from SIN to XEV (to try update) then switch back to SIN and follow up by restore using TB.
anyone has similar force close on the default email app?
backing up with TB now should we (those yet to update jm4) wait for Roto to do his magic for this update?
edit: tried with XSO and also unable to update... that really puzzle me.
edit 2: unroot with z4root and try still unable to update... now looking at ODIN route

perhaps odin route is the best solution for your case, but from jk2 > jm4 not sure if pit file is needed? repartitioning needs it tho, perhaps its good that u do back up of everything, let us know ur flashing result. Odin will definitely able to do the job

oh no... T_T somehow i downloaded P1000JVJL1 (Arabic) by mistake and Odin 1.7 with Auto Reboot & F. Reset Time, selecting the mistaken Arabic firmware (PDA) and flash it without any problem (JVJL1 / JXJK3 / JVJK4) and able to reboot itself.
After notice the wrong firmware, downloaded the right one (P1000DXJM4) from samfirmware.com and using Odin 1.7. Repeating the above steps but the phone briefly flash and came back the 'download mode' and nothing happened although Odin stated passed without any error.
I able to hold the power to shutoff and turn on again and the screen shows the samsung logo screen and stay flashing the word 'samsung' with 1 then 2 quick vibrate (like force close) and didnt boot into the main screen!
what should i do next?? is it bricked?? T_T
edit: the downloaded filename is 'P1000DXJM4_P1000DXJM2_P1000OLBJM1_HOME.tar' and anyone know if correct one?
edit 2: now i am downloading DXJK2 and see if i am able to revert the flash of JM4 T_T
edit 3: is over T_T saw the (phone .. ! .. pc icon)

This is due to dbdata.rfs missing. Please refer to the guide of flashing JMC/D/E series.
BTW, I have a problem is Camera Faulty error when start the camera app. Somebody mentioned that the LCD density can't set too small, but I have reverted it back to default 240, the problem still there. Any clue about it?
Sent from my GT-P1000 using XDA App

thanks dahuzi, i wonder if i choose to flash eu rom by Roto, would his rooted bring my tab back to operation? appreciate any help to bring back my tab.
i am able to bring my (phone .. ! .. pc icon) to the download mode. flashing anything before JM4 wont work anymore (fail at odin 1.7 and 1.3) and i am able to go back to hard reset option (holding vol up and power up). now i need to get the TB backup from the int SD before i try anything new. possible to retrieve in download mode?
edit: where to find the dbdata.rfs for this JM4? can anyother dbdata.rfs from other firmware able to fill it in? help ~ T_T

Hi VNPython,
Your case is complecated one, take it easy and read the thread from Chainfire "WARNING! Do not flash ... ", in there, a lot people has solved with different path.
Be patient, Bro. At that moment, your TAB is not Brick yet, but be careful because it's on the way of the End.
Wish you luck.
Take care.

ha.. i hope to win this war ^^ and learning the way of android!!
edit: just a quick question - does TB backup all user and app data in internal SD or External SD? i got bunch of files in my ext SD folder '.android_secure' and inside have files like 'com.keramidas.TitaniumBackup-1.asec' can any senior confirm is a valid TB backup files and can be used to restore my user & app data? many thanks!

TB (TitaniumBackup) file in the internal SD (in my case is the default), please double check.
Please give us your detail of winning as I'm scare of Samsung flash. My history is, 4 years ago, I bricked my Omnia phone Samsung after I flashed the rom from SIN to AUS. And, this's my second device on Samsung but this is Android and I want to learn the new OS.
Take care, Bro.

hey guess what? i managed to get a file for dbdata.rfs from Roto and got the tab back live but missing PDA and CSC field (checking with *#1234#). tried the reset to get the pda and csc back but failed.
learned quite a few things along the way and will update this thread after completing my mission to update my tab to JM4.
windows seem cant extract and tar file for android tar files. i tried to extract jm4 files and add dbdata.rfs into it but when flashing, it fail.
worst come to worst, flash the JVJL1 to get the working tab again
i hope Mr. Roto could let me know what software to install on windows that able to 'untar' and 'tar' properly with android (linux) files. tried 7z and winrar both cant untar without error.

try using winrar to do the add on of dbdata.rfs, anyway, good luck next time, double check what you downloading

fastcx said:
try using winrar to do the add on of dbdata.rfs, anyway, good luck next time, double check what you downloading
Click to expand...
Click to collapse
Wow... another Maitre!!! What's your winrar???
Look and read:
.....i hope Mr. Roto could let me know what software to install on windows that able to 'untar' and 'tar' properly with android (linux) files. tried 7z and winrar both cant untar without error.
Click to expand...
Click to collapse
Thanks

sorry for the late update as yesterday too late to post anything after able to get my tab back to life! the learning curve is nice and not stressing since many time i see the icon of (phone .. ! .. pc) yet i am able to bring the download (digging) icon back again always.
i will write down the event by event of recovery as reference:
1. flash the JVJL1 (no problem on reboot) by mistake then flash JM4 (missing dbdata.rfs) tar file downloaded from samfirmware.com and failed to reboot due to the missing file.
2. did some silly step and resulted in (phone .. ! .. pc) icon
3. run odin 1.7 and plug the usb and odin show is connected with tab
4. flash JM4 (yes with missing dbdata.rfs) and able to bring the tab back to download mode but unable to reboot into tab
5. flash Roto's dbdata.rfs file (http://forum.xda-developers.com/showpost.php?p=9305891&postcount=1) and able to reboot right after but missing pda & csc info (*#1234#)
6. tried the hard reset (http://forum.xda-developers.com/showpost.php?p=9482192&postcount=106) but no help
7. download Roto's pre-rooted JME 3 files as mentioned (http://forum.xda-developers.com/showthread.php?t=895827) and finally boot the tab with full *#1234# details.
* So if you see the (phone .. ! .. pc) icon dont panic. like KChauJen said, able to solve with enough reading. i listed my route to recovery as reference to give you positive hope to retry.
TB's backup in Internal SD and before flashing JME, i copied the TB folder to my hdd during the missing pda & csc boot and did a backup on JME reboot, copy paste back to TB folder under internal sd and the restore work flawlessly.
after 1 days usage, the trouble found is email app still being force close whenever you reply or forward any email. any senior have similar force close on original email app?

KChauJen said:
Wow... another Maitre!!! What's your winrar???
Look and read:
Thanks
Click to expand...
Click to collapse
My bad. How polite of you.
Back to topic, VNPython everything there is a first time it's good info here. Perhaps you can edit your 1st post with info from your last post?
EDIT: 1 thing though, do you have any issue regarding using samsung apps?

samsung app can use, checked my CSC and its KOR. Apps: Vlingo words to action, Vietnamese Dictionary application & blinkx Beat. didnt try any of them. just *#272*IMEI# and there's no SIN or XEV or XSO or Asian Sales Code in the Roto JME (EU) multiCSC. maybe will try to download multicsc with asian sale code.
* on the email app force close, i delete the email account and re-setup them, and the force close is gone. could be due to TB's restore? anyway, is solved ^^
I wonder will i be able to flash DXJM4 if there is a full tar file?

VNPython said:
....
I wonder will i be able to flash DXJM4 if there is a full tar file?
Click to expand...
Click to collapse
Please consider it carefully, Bro.
What I looked inside of the tar file, and according to Chainfire's Warning, it has the protected boot.
If we can eleminate the three files:
* Boot.bin
* Spl.bin
* zImage
and put back to the tar file with the encrypted code by Samsung (maybe we can ask Roto) then we can flash this modified firmware JM4.
FYI.

[Euro] back from 3.1 to stock 3.01 - so 3G/GSM is working again + all languages !!!!

Hello Dudes!!
There is a way to get back to stock 3.01 german xoom, but with the language file you can get to every language.
Go to thread [REQ] Need MZ601 Euro 3G users. READ NOW! http://forum.xda-developers.com/showthread.php?t=1073570 and load the stocks
than flash it , first boot, system and recovery than go to CWM or the installed recovry and do a wipe data/factory reset or your xoom will boot in loops!
It´s not possible to relock xoom yet.
after that you got a stock of a german 3.0.1 with G3/GSM working.
If you want another language go [MOD][HC3.1] Languages Pack for US Xoom [Updated 5/19 v0.4] http://forum.xda-developers.com/showthread.php?t=1083612 in xoom themes and apps and load the language file. than you just have to install it via CWM, if u don´t have CWM intall fist. Now u can choose any language after reboot.
I hope this will help all u europeens!!!

Hi,
it should be enough to do an "erase userdata" while in fastboot-mode.
What i saw, the userdata.img is only a formated ext4 sparse-image.
Maybe it's also possible to lock German Xooms after this (with the original 3.01 images), but no garantuee for that. I haven't tried it and don't event want to, because of the chance of bricking my Xoom!
Regards.

MediumO said:
Hi,
it should be enough to do an "erase userdata" while in fastboot-mode.
What i saw, the userdata.img is only a formated ext4 sparse-image.
Maybe it's also possible to lock German Xooms after this (with the original 3.01 images), but no garantuee for that. I haven't tried it and don't event want to, because of the chance of bricking my Xoom!
Regards.
Click to expand...
Click to collapse
You will not be able to lock the xoom after this. You need the stock images from motorola. If the 4 images are even one byte off, it will not lock.
Sent From My Evo

bwcorvus said:
You will not be able to lock the xoom after this. You need the stock images from motorola. If the 4 images are even one byte off, it will not lock.
Sent From My Evo
Click to expand...
Click to collapse
Even one bit off, no need to understate it

... taking back my assumptions...
Cheers
Michael

shmigao said:
Hi, i have a theory that we might be able to make the US MZ600 Wifi/3G HC3.1 upgrade work, however unfortunately due to work I won't be able to try it myself before this weekend.
Because of the difficulties of getting Android Market access (etc.) in China, I recently installed the US MZ600 build.prop instead of the EU MZ601 build.prop. Over wifi this gave me Android Market access (both US & Europe, depending on what settings you choose in PaidAppsEnabler). However, naturally since US MZ600 is VZW 3G (CDMA), this method broke 3G on my China Unicom network (which is the same as European standard). Thus I merged the US MZ600 build.prop with the MZ601 build.prop (side-by-side comparison with text editor), and managed to get a US build.prop (for access to US android market) with the EU 3G identifiers. This regained me 3G.
My theory therefore is that we could get HC3.1 Wifi/3G work on EU devices if we:
1. backup EU MZ601 build.prop, and probably framework-res.apk
2. update to HC3.1 Wifi/3G by the BRD method
3. exchange the US MZ600 build.prop and framework-res.apk with the EU versions we updated in step 1
Again this is a theory, and if somebody is brave enough to try it (AFTER A CWM BACKUP!) we can check.... I will try it over the weekend.
If anybody thinks this will not work for some reason, please let us know.
Cheers
Michael
Click to expand...
Click to collapse
You could not switch the framework-res.apk. This file contains the signature that all system files have to have. This is why if you push the wrong framework-res.apk you boot up to an a$$ton of fc's.

bwcorvus said:
You could not switch the framework-res.apk. This file contains the signature that all system files have to have. This is why if you push the wrong framework-res.apk you boot up to an a$$ton of fc's.
Click to expand...
Click to collapse
technically it is possible to switch the framework-res.apk - if it is the right one (as
you mentioned).
i just did that yesterday according to this thread: http://forum.xda-developers.com/showthread.php?t=1064818
....scrap that about "only the build.prop"....

Hello
Following your guide to restore stock 3.01 each time I try to open either the boot file or the system file in recovery it starts opening then gives me a message saying installation aborted. Any ideas would be great

Hello
Ignore that i managed to get that sorted out. New issue is i cannot get into recovery to flash the language pack. When i select recovery i get an android robot with an exclamation mark

@ Marshall
that is the phone´s recovery you have to install ClockworkMod Recovery http://forum.xda-developers.com/showthread.php?t=1074979

Pepsi
Thanks for that. Have tried that but everytime I flash it through fastboot it sends to the device ok but then fails to write. Message on the xoom says "Unknown partition, failed to process command error 0x30003. Other than that it all works fine albeit in german lol.

Hello Again
Right I have managed to do everything now including getting cwm recovery sorted. So i proceded to install the language pack, again all good. Now it just boot loops at the honeycomb welcome screen. Even tried a full wipe but still stuck in honeycomb welcome screen.
I have to admit I have now run out of ideas so any help would be greatly appreciated.
Thanks all

Hello again
Got everything working again and can confirm the minute I install the language pack the system goes straight into a boot loop.
Any ideas

Marshall1975 said:
Hello again
Got everything working again and can confirm the minute I install the language pack the system goes straight into a boot loop.
Any ideas
Click to expand...
Click to collapse
Do a clear data/factory reset in CWM than the loop is history

Hello
Have tried that pepsi but to no avail. Still stays stuck in boot loop. Just wondering if the the fact the language pack comes from 3.1 is maybe causing the problem

Das heisst, es ist nach dem nicht in Deutsch?
Is not German Language includet?

Procedure to get back from HC3.1 to HC3.0
Folks,
I've just got mine Brazilian Xoom (MZ605) working back with 3G GSM.
Recently I did an HC3.1 update (from USA Verizon image, MZ600) on my Xoom. I really liked the new features from HC3.1, but I can't bear pay for a 3G Xoom if I can't use its 3G modem. So, I got its 3G feature back.
It`s a really simple procedure:
1) Donwload any of those ZIP files in this website that support your language and works on UMTS network: developer.motorola.com/products/software
2) Unzip this ZIP file. You'll get 4 IMG files. One for each memmory areas inside Xoom;
3) Download and install the AndroidSDK: developer.android.com/sdk
4) Add the AndroidSDK subfolder "tools", that contains the "fastboot.exe" file, in your PC Path system variable, so You'll be able to execute fastboot command from anywhere in your system;
5) Reboot your Xoom in Fastboot Support Mode;
6) Connect your Xoom to your PC USB port;
7) Open a Command Prompt Line and go to the directory where you unzipped the Xoom ZIP file;
8) Flash the Boot, System and Userdata memmory areas using the "fastboot.exe" and the respective IMG files. You don`t need to flash the Recovery memmory area if like your actual recovery firmware. To know what are the fastboot commands you have to type, here are them:
8.1) fastboot flash boot boot.img​8.2) fastboot flash system system.img​8.3) fastboot flash userdata userdata.img​8.4) fastboot erase cache​
OBS: Remember to check on Xoom the ending of every command before You type down another one.
9) After all those steps, just reboot your Xoom and get life back smiling to You.
Check the attached images to know what You'll see on your Xoom and PC screens.
Remember to drop a "thank" here if You get success on this procedure.

Or you just take the original images - freshly released - from motorola and use the guided docs there.

Riffer said:
Or you just take the original images - freshly released - from motorola and use the guided docs there.
Click to expand...
Click to collapse
oh, sorry Erledigt

edsoncfgarcia said:
Folks,
I've just got mine Brazilian Xoom (MZ605) working back with 3G GSM.
Recently I did an HC3.1 update (from USA Verizon image, MZ600) on my Xoom. I really liked the new features from HC3.1, but I can't bear pay for a 3G Xoom if I can't use its 3G modem. So, I got its 3G feature back.
....
...
..
.
Remember to drop a "thank" here if You get success on this procedure.
Click to expand...
Click to collapse
Just to say THANK YOU ! ! !
[ ] ´s

[Q] Brand new T999V running Cyanogenmod 10, camera doesn't work! Please help!

*************************SOLVED*****************************************************************************************************************************
Hi everyone!
I'm a noob. I got my Galaxy S3 T999V rooted and the boot (recovery?) runs clockworkmod. CyanogenMod 10 is running smoothly, except:
The camera doesn't work! Getting a "cannot connect to camera" error instantly upon launching the camera app (stock).
So from perusing the internet a little more, there are other phone models also suffering from this "can't connect to camera" error.
The fix involves: Booting into rooted stock. extracting the folder "cameradata" in system using a file explorer (AndroZip). Put them on the external sdcard or your computer. Then overwrite your CM10 flashed system/cameradata folder's .bin(s) and setting the permissions a certain way.
Does anyone have the stock Galaxy S3 cameradata files? And I have no idea how to change permissions!! HELP!!
*************************SOLVED*****************************I*TAKE*NO*RESPONSIBILITY*FOR*ANY*DAMAGES*OR*BRICKING*THAT*MAY*OCCUR***********
http://forum.xda-developers.com/showthread.php?t=2102981&page=2#post39859973
THOSE ARE THE FILES (or click here?)
1. Download the files, unzip them and place them somewhere on the phone (sdcard0 or sdcard1, in some separate, user-made folder)
2. Make sure you have CyanogenMod's built-in File Manager set to allow ROOT access
3. Using CyanogenMod's built-in File Manager, click the "parent folder" at the top until the top reader line says /
4. Look for a folder called system, enter it
5. Look for a folder called cameradata, enter it
6. With nothing selected, press the :: button in the bottom left, on-screen. Select "properties" and choose 'permissions', grant all properties to everything (except the S column). This allows you to copy the downloaded files into this folder.
7. Browse to where you have the files. On the left is a tick-box, tick them all.
8. Browse back to the /system/cameradata/
9. Select the :: again. Select "paste all items here". SELECT OVERWRITE.
10. Individually long-press each item and change it's properties. Select permissions and permit all except the S column again. This allows the app to be accessed, the user to change the app, and the app to save files.
11. Attempt to run the STOCK camera app. CHANGE THE SCENE "SCN" TO 'ACTION'. I've been told this keeps it from crashing again...
12. If the camera app is a bit laggy, try rebooting. If it persists (but camera app is functioning) may want to restore permissions using Recovery Boot (I use CWM).
The difference MAY be adding that one extra file (_ZH), but I recommend moving and overwriting all just to be safe.

Malumen said:
Hi everyone!
I'm new to the whole modding/cyanogen/clockwork thing. I got my Galaxy S3 T999V rooted and the boot (recovery?) runs clockworkmod. CyanogenMod 10 is running smoothly, except a few issues:
- The WiFi and mobile network connections fly between 20% and 60% (with the WiFi signal reaching 98%) when I am just sitting in my room and the phone is motionless. Do I need to update the radios to get better reception? (And how do I do that? I am on Mobilicity in Canada)
- What steps do I take to perform a restore? I've made a backup in the CWM boot/recovery of Cyanogen after I got everything working fine. If I messed some things up, what steps do I take to restore back to that point? Do I press Wipe Data/Factory Reset and Wipe Cache, or do I just select Restore and the file to restore using?
- THIS IS MY BIGGEST ISSUE: The camera doesn't work! None of the camera apps work in my CM10. Skype and Hangout using the front camera works, but no photo-taking apps work (they do not even run, just black then they back out to the Apps screen)
So how do I:
> Get more stable reception? Do I update the radios? If so, how?
> Perform a restore? What steps do I take to return to a backup I have of Cyanogen?
> Get my camera working?
Click to expand...
Click to collapse
try to reflash. wipe everything and make sure you didnt download nightly. nightlies can have some problems. are you sure you download the stable version?

KingKostas said:
try to reflash. wipe everything and make sure you didnt download nightly. nightlies can have some problems. are you sure you download the stable version?
Click to expand...
Click to collapse
May I ask quickly what steps are involved in "reflashing"? Just to make sure I don't do some extra step or miss something.
As far as the stable version goes, I looked for the d2tmo file on get.cm under the Stable tab. I'm assuming that would be the most stable build?
(Perhaps a nightly might fix it??)
Question: Is there not a way I can just install/add this "4.2" camera? I've seen videos and read that people are using that just fine on CM10. Alternately if I boot into recovery would "fix permissions" be any help?

re: odin flash
Malumen said:
Hi everyone!
I'm new to the whole modding/cyanogen/clockwork thing. I got my Galaxy S3 T999V rooted and the boot (recovery?) runs clockworkmod. CyanogenMod 10 is running smoothly, except a few issues:
- The WiFi and mobile network connections fly between 20% and 60% (with the WiFi signal reaching 98%) when I am just sitting in my room and the phone is motionless. Do I need to update the radios to get better reception? (And how do I do that? I am on Mobilicity in Canada)
- What steps do I take to perform a restore? I've made a backup in the CWM boot/recovery of Cyanogen after I got everything working fine. If I messed some things up, what steps do I take to restore back to that point? Do I press Wipe Data/Factory Reset and Wipe Cache, or do I just select Restore and the file to restore using?
- THIS IS MY BIGGEST ISSUE: The camera doesn't work! None of the camera apps work in my CM10. Skype and Hangout using the front camera works, but no photo-taking apps work (they do not even run, just black then they back out to the Apps screen)
So how do I:
> Get more stable reception? Do I update the radios? If so, how?
> Perform a restore? What steps do I take to return to a backup I have of Cyanogen?
> Get my camera working?
Click to expand...
Click to collapse
The very best advise is to do the following, doing anything else will most likely prolong
the problems you are having or making them even more difficult to resolve.
First thing you need to do is to install the stock Tmobile T999 rooted firmware.
Here are the exact step by step instructions with the download link for the firmware.
After you have followed these instructions your phone will be working properly and if
you like you will be able to flash any custom roms made for the Tmobile T999 phone
or restore any backups unless the the backup is corrupted in some way or another.
Here is the link to the Tmobile Stock & Rooted firmware you need:
http://www.androidfilehost.com/?fid=9390169635556426451
After downloading it make a folder on your desktop and unzip the file
using Winzip or 7zip so the .TAR file is in the new folder you just made.
Here is a link for ODIN which is required for flashing the stock rooted firmware
(a windows app) http://d-h.st/Q14
Download and extract Odin into the same folder you made containing the TAR file.
Here is a step by step guide for you.
Download the firmware of your choosing (use the root66 version if you want root)
Run Odin by double clicking the Odin.exe within the folder you extracted
Turn off your phone and boot into DOWNLOAD MODE (Volume Down + Home + Power Hold until phone powers up, then release and press Volume Up to enter Download Mode)
Once in Download Mode, connect the USB/Charger cable to the phone and plug into the USB port on your computer.
You should now see a COM** port listed toward the top-left of Odin (under ID:COM)
Click on the PDA button in the middle-right area of Odin.
Browse to and select the FW you downloaded (TAR file)
Make sure Auto-Reboot and F. Reset Time are the only options checked and that PDA is the only other thing checked.
TRIPLE CHECK your settings and that you have selected the correct firmware for your model phone and are using the correct options.
If you are using a laptop, make absolutely sure you are plugged in, or if on battery, that it is charged enough and will not go into sleep mode during flash.
Click Start to begin the flash. This will take a while, so be patient!
Once complete, in the top-left box in Odin, it will say PASS and the phone should have automatically rebooted.
You may unplug the phone and close Odin if you wish.
Wait at least 5-10 minutes for the system to boot the first time and then build its cache! (It may seem to hang during boot, this is normal and you must be patient!!!)

Misterjunky said:
The very best advise is to do the following, doing anything else will most likely prolong
the problems you are having or making them even more difficult to resolve.
Click to expand...
Click to collapse
I followed most of these directions the first time, using the guide from High On Android:
http://www.youtube.com/watch?v=QPeIZZVYHbY
I used Odin, got root, wiped and got CM10 working.
This seems to be a bit of a problem that has cropped up in other models (i747). The fix that was used was to get back to the Stock ROM, while rooted, and browse to the system folder /cameradata/. In there are files for permissions for the camera. Copy those to the external SD card or your computer, then get back into CM10. Replace the CyanogenMod system folder /cameradata/ with the files you got from the Stock ROM. Then change the permissions for these new files.
So does anyone have the Stock /cameradata/ files? I'd greatly appreciate it!

re: camera issue
Malumen said:
I followed most of these directions the first time, using the guide from High On Android:
http://www.youtube.com/watch?v=QPeIZZVYHbY
I used Odin, got root, wiped and got CM10 working.
This seems to be a bit of a problem that has cropped up in other models (i747). The fix that was used was to get back to the Stock ROM, while rooted, and browse to the system folder /cameradata/. In there are files for permissions for the camera. Copy those to the external SD card or your computer, then get back into CM10. Replace the CyanogenMod system folder /cameradata/ with the files you got from the Stock ROM. Then change the permissions for these new files.
So does anyone have the Stock /cameradata/ files? I'd greatly appreciate it!
Click to expand...
Click to collapse
Just download any of the custom rom zip files based on the jellybean v4.1.1 stock rom.
All of those custom roms will have the files you are looking for.

Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

d2vzw
This also works on the sch-i535 as well. Thank you so much.

kingsugar said:
This also works on the sch-i535 as well. Thank you so much.
Click to expand...
Click to collapse
Yes, I tried all the other options for getting my camera back on track, but only going back to a full stock (rooted) ROM got my camera up and running again. FWIW, I was running an AOSP ROM for months without issue. What kicked my camera offline (the dreaded can't connect to camera) for some strange reason was when I updated to the most recent firmware VRBMF1. Now its straight back to AOSP for me! Thanks for creating this post! Very helpful!

My fix
I'm going around posting my fix to all the camera threads in hopes of helping people find a solution sooner. I created a thread over in d2vzw http://forum.xda-developers.com/showthread.php?t=2492304

fix camera error on i9300 with cm 9 (4.0.4)
Malumen said:
*************************SOLVED*****************************************************************************************************************************
Hi everyone!
I'm a noob. I got my Galaxy S3 T999V rooted and the boot (recovery?) runs clockworkmod. CyanogenMod 10 is running smoothly, except:
The camera doesn't work! Getting a "cannot connect to camera" error instantly upon launching the camera app (stock).
So from perusing the internet a little more, there are other phone models also suffering from this "can't connect to camera" error.
The fix involves: Booting into rooted stock. extracting the folder "cameradata" in system using a file explorer (AndroZip). Put them on the external sdcard or your computer. Then overwrite your CM10 flashed system/cameradata folder's .bin(s) and setting the permissions a certain way.
Does anyone have the stock Galaxy S3 cameradata files? And I have no idea how to change permissions!! HELP!!
*************************SOLVED*****************************I*TAKE*NO*RESPONSIBILITY*FOR*ANY*DAMAGES*OR*BRICKING*THAT*MAY*OCCUR***********
http://forum.xda-developers.com/showthread.php?t=2102981&page=2#post39859973
THOSE ARE THE FILES (or click here?)
1. Download the files, unzip them and place them somewhere on the phone (sdcard0 or sdcard1, in some separate, user-made folder)
2. Make sure you have CyanogenMod's built-in File Manager set to allow ROOT access
3. Using CyanogenMod's built-in File Manager, click the "parent folder" at the top until the top reader line says /
4. Look for a folder called system, enter it
5. Look for a folder called cameradata, enter it
6. With nothing selected, press the :: button in the bottom left, on-screen. Select "properties" and choose 'permissions', grant all properties to everything (except the S column). This allows you to copy the downloaded files into this folder.
7. Browse to where you have the files. On the left is a tick-box, tick them all.
8. Browse back to the /system/cameradata/
9. Select the :: again. Select "paste all items here". SELECT OVERWRITE.
10. Individually long-press each item and change it's properties. Select permissions and permit all except the S column again. This allows the app to be accessed, the user to change the app, and the app to save files.
11. Attempt to run the STOCK camera app. CHANGE THE SCENE "SCN" TO 'ACTION'. I've been told this keeps it from crashing again...
12. If the camera app is a bit laggy, try rebooting. If it persists (but camera app is functioning) may want to restore permissions using Recovery Boot (I use CWM).
The difference MAY be adding that one extra file (_ZH), but I recommend moving and overwriting all just to be safe.
Click to expand...
Click to collapse
thanks a lot, i read your post, i take your advice to copy "SlimISP" to built in (cm system) folder, its work for me perfectly.
Thanks a lottttttttttttttttttttttt, have a nice day.

No Mobile Data on Treble Roms

I've tried over 5+ different treble ROMs and the mobile data will not work. My friend @Spaceminer had helped me try to solve it by finding an apns-conf.xml as well as a flashable zip but no luck.
I'm using the Moto G6 Play XT1922-7 Boost Mobile Variant.
I'm sorry I haven't provided much detail to the issue but this basically sums it up.
Thank you for any help.

Same problem here with 1922-4 retail variant, i have tried to flash the vendor.img over gsi's via fastboot but it just get stuck in a bootloop. The only option i have is stay in stock pie

Alphita said:
Same problem here with 1922-4 retail variant, i have tried to flash the vendor.img over gsi's via fastboot but it just get stuck in a bootloop. The only option i have is stay in stock pie
Click to expand...
Click to collapse
Did you try to flash the vendor.img on TWRP?

sinkoo1979 said:
Did you try to flash the vendor.img on TWRP?
Click to expand...
Click to collapse
Yes and got another bootloop and the 'failed to mount /vendor' message when you try to flash anything. Idk if there's a possible fix for mobile networks

Alphita said:
Yes and got another bootloop and the 'failed to mount /vendor' message when you try to flash anything. Idk if there's a possible fix for mobile networks
Click to expand...
Click to collapse
You have to find your correct apns-config.xml, place it in /system/etc and set permissions to 0644. Then reboot, open your mobile network settings and reset your apn.
If you ever want to go from Pie to Oreo, grab your very last Oreo firmware and flash everything like normal. Some things won't flash, and that's okay. If that happens, just skip it and flash the next items in line. When you're done, reboot it normally and let it encrypt at least once. If you don't let it encrypt first it can cause a recovery bootloop and you'll have to flash everything again.

Spaceminer said:
You have to find your correct apns-config.xml, place it in /system/etc and set permissions to 0644. Then reboot, open your mobile network settings and reset your apn.
If you ever want to go from Pie to Oreo, grab your very last Oreo firmware and flash everything like normal. Some things won't flash, and that's okay. If that happens, just skip it and flash the next items in line. When you're done, reboot it normally and let it encrypt at least once. If you don't let it encrypt first it can cause a recovery bootloop and you'll have to flash everything again.
Click to expand...
Click to collapse
How do i set those permissions? Thanks in advance

Alphita said:
How do i set those permissions? Thanks in advance
Click to expand...
Click to collapse
Use a root explorer, navigate to the file, long press it and select permissions and set them to rw-r--r--. It should prompt you to mount the system automatically to make the changes. Mine does anyhow. (See sceenshot)
Or;
In TWRP, select mount > system. Then select advanced > file manager > navigate to and select the apn file, and you'll have an option to change permissions. Select it, delete the 0000 and enter 0644 then swipe to confirm. Reboot.
Or;
Using an Android Terminal enter;
su
mount -o rw,remount /system
chmod 0644 /system/etc/apns-config.xml
reboot

Spaceminer said:
Use a root explorer, navigate to the file, long press it and select permissions and set them to rw-r--r--. It should prompt you to mount the system automatically to make the changes. Mine does anyhow. (See sceenshot)
Or;
In TWRP, select mount > system. Then select advanced > file manager > navigate to and select the apn file, and you'll have an option to change permissions. Select it, delete the 0000 and enter 0644 then swipe to confirm. Reboot.
Or;
Using an Android Terminal enter;
su
mount -o rw,remount /system
chmod 0644 /system/etc/apns-config.xml
reboot
Click to expand...
Click to collapse
Thanks! I will try this the next time i flash a rom

Would someone be so kind enough to share their BOOST apn.config.xml that the replaced the one on with that does NOT work on these GSI's?? If you do I'll follow you and hit thanks all day. ??

Here's (see screenshot) the closest I've ever gotten far as having data on a gsi. I must have the wrong xml file. I am fully aware of the process described above and have even done it multiple ways after I knew the way described and how I was adding the apn xml was correct and I have zero data.
If someone will attach their apn.config.xml, the one that they acquired data from using the boost Mobile network I'll be extremely thrilled and forever greatful to add it to the thread I made over in guides section so that in the future people can solve this issue fast and get her running and have a jolly day. ? I made that thread (I'll change the name later today) initially to consolidate as much info as I could and put it all in the op so we can be a bit more organized. I just haven't figured out anything else so I can't add to it just yet. ? This would be a great addition if someone would be so cool enough to kick me down some knowledge far as what's the correct apn.config.xml to replace the og one in gsi to get data working. I've deleted the current apn xml and replaced it with the one I have, I've overwritten it, I've tried countless times messing with the telephony.db and I obviously can't do it. Please pleeeaasee post the proper apn xml so I can get this phone going and add to op over there. @Starkiller2
I hope everyone is having a good day. It hot as **** where I'm at today. ??

I got nothing on xml. I only ever found one way to get it to work on boost, that was with the sqlite editor.
https://play.google.com/store/apps/details?id=com.dundastech.sqlitemasterlight

Starkiller2 said:
I got nothing on xml. I only ever found one way to get it to work on boost, that was with the sqlite editor.
https://play.google.com/store/apps/details?id=com.dundastech.sqlitemasterlight
Click to expand...
Click to collapse
Next time you're running a custom rom and you get data working, you can just copy /system/etc/apns-conf.xml and save it for later. You won't have to mess with any apps after that.

Starkiller2 said:
I got nothing on xml. I only ever found one way to get it to work on boost, that was with the sqlite editor.
https://play.google.com/store/apps/details?id=com.dundastech.sqlitemasterlight
Click to expand...
Click to collapse
Vague and unhelpful. Need better directions on that I messed with sqlite editor for days on end swapping out telephony.db things and never did get it going.
Did you swap both of them??
Did you swap other files in telephony.db too?
Details...?
What files exactly did you extract in telephony.db?
Vague comments never help anyone. Better to not post at all then post some two word comment with a link.

I apologise, I'm driving across country and was making an effort to help in the little time I had, but you're right, better to not try at all. Which may be why you aren't getting any answers to your questions. Some info is usually better than none and can sometimes lead you in the right direction, but you won't even get that much snapping at everyone who doesn't immediately solve the problem you have and then rage quitting when you can't do it yourself. It makes people not want to put in any effort. You have 4000 posts I assumed you could figure out how to edit apns with an app from the play store. You're right. I should absolutely stop offering any input at all, but rather I should just start *****ing and whining when I'm not spoon fed like I see so much here.
And as I have posted directions in multiple other threads, I assumed you had done at least a cursory search for your answer(as per forum rules) which would've found those posts but I was apparently wrong there as well.
---------- Post added at 07:00 PM ---------- Previous post was at 06:45 PM ----------
Spaceminer said:
Next time you're running a custom rom and you get data working, you can just copy /system/etc/apns-conf.xml and save it for later. You won't have to mess with any apps after that.
Click to expand...
Click to collapse
Thank you. That's good to know

hi, there is in the web a file apns-conf.xml to download? or sombody take us a backup? Thanks

Hey gang, I too am having issues trying to simply get mobile data working on GSI's. I have a Pixel 3a, and have tried multiple Android 10 GSI's, all of them don't allow me to use mobile data. I have not tried the apns-conf.xml trick yet, as I am unsure if that's the answer if it hasn't worked for others. Android 11 does not use an apns-conf.xml in system/etc/ so I couldn't extract it from my current setup unfortunately. Wish you all luck, post back if you get something working.

not working, moist do you have rooted phone? because only on rooted phones you can do this trick

doid1 said:
not working, moist do you have rooted phone? because only on rooted phones you can do this trick
Click to expand...
Click to collapse
I'll probably flash a ROM this weekend and pull my xml to test this. I have Telus so I unfortunately can't help with the Boost users, but can at least help confirm whether this method works or not.

ok thanks i wait, my phone seems to be dead on 4g.. says: no registration..
I tried everything imaginable and perhaps even the unimaginable .. heheheh .. but the result is always the same: no recording on the 4g, so I'm more and more inclined that it is a hardware failure or even a damage to the eeprom memory because 'I have formatted everything and the mobile phone has recharged everything correctly but it was useless ..
I tried to see that maybe it has a sim locked, but I didn't manage to enter meta mode and try to force it also because only with miracle box there is a guide ... umh ... and I do not stop until I succeed in the objective, and then the next step will be to take a complete image of another mobile phone identical to mine and copy it over it (but it is almost impractical because I cannot find anyone who gives me a full backup of this phone) and then I will brutally try to put another image of another working smartphone on it, leaving only the crucial sectors intact (system, boot, vendor, recovery, preloader, everything else I format it hehehehh) I will know..

Well I have a ROM flashed and found the apns-conf.xml, which is not included on my stock ROMs (10 or 11). Now going to flash a GSI or two and do some tests to see if I can get any data working.
Edit: Couldn't get the apns-conf.xml to work. However, I did find out the some GSI's work right out of the box for my Pixel 3A, those included AOSP 10 / 11 by Phh, and the CAOS R build. Bless, qidroid, havoc booted fine but did not have mobile data working.