Database Develop

[Q] After Gingerbread install, how to use SIM for USA AT&T?

So I just installed Gingerbread on my new Galaxy Tab (AT&T). As per the instructions, in Odin I used the JK3 modem file. However my T-mobile prepaid sim card isn't working. I'm assuming I need to re-connect (in download mode or upload mode?), start Odin, and choose the JPZ modem file. Is this correct?
Will this wipe the Overcome ROM, or will that still remain?
Thanks.

lollavid said:
So I just installed Gingerbread on my new Galaxy Tab (AT&T). As per the instructions, in Odin I used the JK3 modem file. However my T-mobile prepaid sim card isn't working. I'm assuming I need to re-connect (in download mode or upload mode?), start Odin, and choose the JPZ modem file. Is this correct?
Will this wipe the Overcome ROM, or will that still remain?
Thanks.
Click to expand...
Click to collapse
If you download only the modem file, with odin without repartition, then it will work, choose the one you need correctly. It will not destroy overcome,

So I use the same PIT and PDA from the first time (from GB Stock Safe), but substitute the Phone file for the JPZ modem? and I also unclick repartition? Is that correct?

No, you only load up the modem.bin file to flash. Nothing else.
When it is done loading and the SGT resets, then go check your APN settings for your carrier. i.e. google APN settings for carrier

Okay, I tried that. I found info on the APN settings here:
http://androidcommunity.com/forums/f4/t-mobile-us-apn-settings-please-help-41160/
However, when I put my T-mobile SIM card in and start the phone, I get the message:
"enter network lock control key"

Okay, so I followed the tutorial here:
http://forum.xda-developers.com/showthread.php?t=843323
I am now stuck with adb and getting my system to reboot. Here is a screenshot of the occurrence in under the cmd prompt:
{
"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"
}

It looks like the script didn't run properly for you and I wouldn't let it delete the /efs/nv_data.bin file if I was you.
I hope you made a manual backup of the /efs folder before you started this.
Looking at is more closely I see you werent running in root mode because you still have the $ prompt instead of the # prompt
BTW, i did unlock on the phone using the Hexeditor app fromt he market and also using Root Explorer to make backup copy of the /efs folder.
If you still need help you would be better off posting in the original unlock thread:
http://forum.xda-developers.com/showthread.php?t=843323

I think I need 10 posts before I can post in that thread.

So I guess...

That's 10.

It's dumb crap like this that is keeping people away from xda - too many thoughtless posts to sift through.

XT1068 won't boot properly anymore

I got my XT1086 from Amazon.de yesterday.
There was no OTA for Lollipop yet, so I figured I could force it using this method:
http://forum.xda-developers.com/moto-g-2014/development/tool-moto-g-xt1068-andoid-l-updater-t2964933
It worked. I had an unlocked bootloader, lollipop, and root.
Wanted to remove the bootloader warning message at start-up, so I did this:
http://forum.xda-developers.com/mot...x-remove-unlocked-bootloader-warning-t2875385
It kinda worked, but took ages to start up.
Had problem with dual sim not working, did a factory reset from the phone menu. Didn't boot since then.
Get stuck on the image that replaces the unlocked boot loader warning, it appears and disappears seconds later (over and over again)
Can't turn off, automatically restarts
Don't get the normal charging screen
I can get into fastboot
I can get into recovery (takes a while to open)
So I'd like to go stock again. Found this: http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
Dev-host is impossible slow, can't download from there (with my 60Mbit/s connection). Official mirrors are all down?.
Downloaded "RETDEALL_XT1068_4.4.4_KXB21.85-23_cid7_CFC.xml.zip" from somewhere else, but that does not appear to work with the method above. I see warnings in recovery like "Unable to mount /data, /cache, /system".
Any other method to return to stock? Any help?
I flashed the cr*p out of my old Xperia X10 and HTC Sensation without big issues, but now I f*cked up...

Press volume down+power off button for at least 3 min then release the button now you will see fastboot mode of your phone connect your phone to pc and flash twrp recovery and then restore lollipop from below link
http://forum.xda-developers.com/showthread.php?t=2964330

vikasb32 said:
[...] http://forum.xda-developers.com/showthread.php?t=2964330
Click to expand...
Click to collapse
Need to fill in my phone's serial number. I don't have that serial number written somewhere, and can not get it from the about menu 'cause I can't boot right now...
Can't copy to internal memory either (can't connect as multimedia device to pc), only external SD.

JoWannes said:
Need to fill in my phone's serial number. I don't have that serial number written somewhere, and can not get it from the about menu 'cause I can't boot right now...
Can't copy to internal memory either (can't connect as multimedia device to pc), only external SD.
Click to expand...
Click to collapse
you able to go to fastboot mode?

I found my phone's serial number by going to TWRP recovery, and trying to make a full backup to my SD card.
It didn't make a backup, but made the (empty) folders. I put the lollipop TWRP in there. I see it in recovery but can't restore it.
When I go to TWRP -> Backup, I see the following partitions and their sizes:
Data: 0MB
Cache: 0MB
System: 0MB
Boot: 9MB
PDS: 3MB
When I press the backup button, I see the error message " unable to mount '/system' " (and the other partitions). I get the same error when I try to restore that backup.
I'm on TWRP v2.8.0.1, tried to flash v2.7.1.1 from here with this tool, but that was not successful...
Edit: TWRP 2.7.1.1 is installed now. Still can't restore that lollipop archive because " unable to mount '/system' ".

I found this:
http://droiddefy.com/how-to-update-...69-to-official-android-5-0-lollipop-manually/
Same files as I used before, different method. Although I got errors at the first 2 steps, this method worked. I have a working lollipop again.
Still the US version (as before), without working dual sim. Need to figure out how to get another (Brazilian?) version working.
{
"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"
}

http://forum.xda-developers.com/moto-g-2014/development/windows-tool-moto-g-2014-xt1068-dual-t2983295#post57801996 this will restore kitkat to XT1068 Dual Sim for ALL retail

HELP: After updating to android 10

After the update, this message appears after restarting, updating by OTA, not boot
how to fix this?
translate:It is not possible to load the android system. Your data may be corrupted. If you continue to receive this message, it may be necessary to perform a reset to the original configuration and clear all user data stored on this device.
Try again OR reset to original configuration
{
"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"
}

I'm sorry for what has happened to your phone. It's probably caused by some corrupted files while uploading or the file integrity has been jeopardized since something similar happened to me while I was trying to unlock the boot loader without wiping the phone. I'd say there's not a chance to get your datas back if you've got a locked boot loader but if you're unlocked you might wanna try pulling important files from the storage using fastboot or TWRP. But at the end a wipe is necessary for phone to function correctly again.
Have a nice day.

A quick solution might work.
Solution steps:
0. Get the adb/fastboot tools from Google
1. Mobile Go to fastboot
2. use ‘fastboot getvar current-slot’ to determine what slot you are on, which is damaged. You will get either a or b
3. use ‘fastboot --set-active=b’ or ‘fastboot --set-active=a’ for setting active slot to another. Hence, set it to b if you got a from step 2.
4. Restart.
The possible reason and why doing this:
1. If ota is working, the original system partition is untouched for sure, since ota check system partition during the process.
2. The ota extract rom to another slot, and set the active slot to another after reboot.
From what I saw here, there is some problems between the original data partition and new system partition, but they might Woking with the old one.
Sent from my Mi A2 using Tapatalk

Fastboot can switch slots for fully unlocked phone only.
If phone is not unlocked, options are:
- make reset and loose data, or,
- if data is to be preserved - remove SIM, plug external power, and continue retrying reboots (bootloader of AndroidOne phone with A/B slots is supposed to determine after numerous attempts that current slot does not contain bootable OS and automatically switch to previously active slot).

Aerobatic said:
Fastboot can switch slots for fully unlocked phone only.
If phone is not unlocked, options are:
- make reset and loose data, or,
- if data is to be preserved - remove SIM, plug external power, and continue retrying reboots (bootloader of AndroidOne phone with A/B slots is supposed to determine after numerous attempts that current slot does not contain bootable OS and automatically switch to previously active slot).
Click to expand...
Click to collapse
Tbh from several research, I can't find evidences that suggest swapping slot require unlocked bootloader.
Since we normally unlock bootloader at the very beginning.
Either way worth trying.
Sent from my Mi A2 using Tapatalk

As a matter of fact, "fastboot set_active b" in full stock phone state returns: FAILED (remote: 'Slot Change is not allowed in Lock State').
So, for those who did not unlock MiA2 beforehand, the only hope to save data in OTA-generated bootloop state is to rely on AndroidOne "A/B (Seamless) System Updates" and keep trying to boot.
https://source.android.com/devices/tech/ota/ab
https://source.android.com/devices/tech/ota/ab/ab_implement#bootcontrol

Need help flasing Paranoid Android - All TWRP'd up

Hi all! This is my first attempt to flash a custom rom and I'm stumbling. Summary below:
DEVICE AND SYSTEM:
Xiaomi Mi 6X
Running MIUI 11.0.6.0(PDCCNXM) (based on Android 9)
Device bought in China in 2018, not used until now, only updated through Xiaomi OTA.
Mi Unlock status - Unlocked
Developer options unlocked
USB debugging - activated
Phone not rooted.
Phone has no lock screen password set.
FILES TO FLASH:
1. dm-verity anti-rollback flash:
no-verity-opt-encrypt-6.0.zip
2. Paranoid Android custom ROM:
pa-quartz-5-wayne-20200924.zip
METHOD
I'm using Google pltaform-tools (https://developer.android.com/studio/releases/platform-tools) + TWRP files (https://twrp.me/xiaomi/xiaomimi6x.html) and command prompts in adb and fastboot.
WHAT HAS WORKED SO FAR
adb devices OK - cmd shows hexa key
adb reboot bootloader OK - phone enters fastboot
fastboot flash recovery twrp.img OK - cmd shows Finished. Total time: 1.504s
fastboot reboot (holding recovery key combo to avoid entering automatic MIUI recovery) OK - TWRP loads
Then the problems start. TWRP shows:
Mount
Decrypt Data
Enter Password
and no password in the realms of man or heaven works. by clicking cancel as a workaround several mounting problems appear:
THE ISSUE
Since TWRP can't decrypt internal storage, I can't find the zip files I copied to the phone's memory.
Googling around I found the OTG option and tried it. But as it turns out it's also impossible to mount OTG (on Mount, the option for OTG appears but clicking it does nothing)
Googling more I found out about abd sideload, but TWRP fails to start the feature (on Advanced -> ADB sideload -> select Wipe Dalvik Cache + Wipe Cache)
Also googling intensely I found that by wiping the memory (on Wipe - Format Data - write "yes") then reentering recovery it was possible for TWRP to enter a decrypted mode. after doing this no password is required but both OTG and ADB show the same problems as before (and of course the internal memory files are no longer there).
As a summary of my woes, this is what I've tested so far and the results:
{
"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"
}
Assorted tests with older versions of TWRP have exactly the same results.
After every wipe I have to set up MIUI11 again, open developer optios, allow USB debugging etc. My fingers hurt. Morale is low. My soul is leaking. Any ideas on where to go next? Is this some unfixable incompatibility between TWRP and MI? I think I've exhausted the paths I can find by just googling around like a progressively more hairless maniac noob.

TWRP sucks for mi 6X. Download this one (OrangeFox Recovery) and everything works fine.To install it extract the zip and flash the recovery.img that is there. After that reboot to recovery and if it still asks for password just ignore, go to menu, manage partitions, clik on data, click on the button that will show, then format data and type yes. This will clean every partitions (It's the only way i found to fix encryption since our device doesn't support sd cards)Then download the Rom you want to your pc and then copy to your phone storage and install it. Good Luck.

Recovering data from M22

Hi,
I have a M22 which has been hanging at the "Phone is starting" screen. I have tried almost everything I can think of the get my contact list and photo's of the phone.
After installing a game called Tap away the phone rebooted. After which is was stuck in the Phone is starting message. I'm able to start up the phone. Then the lock is displayed, but when I unlock the phone only the background of my home screen is displayed with a progress bar saying "Phone is starting".
Untill now I tried the following things:
- uninstalled the game (I'm able to access the the settings menu, but not all options work)
- Boot into recovery mode and wipe cache partition.
- Tried adb to pull data off the phone.
- Tried Driodkit. The app is installed after which nothing happens.
- Tried Smart Switch, but it does not see the phone.
- tried to install an sd card, but was unable to format and use it. Menu option not responding.
Since the phone is still under warrenty I'm a little bit hesitant the flash a new rom. It will be the first time I will be flashing an andriod phone. I've downloaded the new files. But with the new version of odin 3.14 I have an extra option called userdata that is not mentioned in any of the tutorials/how to's. I want to keep the data on my phone, so it is suggested I use the home_csc file instead of the csc file. Do I load this on the CSC line or on the USERDATA line. Do I need the USERDATA line at all. I dont want to brick the phone.
Are there any other possibilities to get the data of my phone? So I can just perform a factory reset. I would really appreciate it.

Try opening in safe mode if you haven't already.
In the future use a namebrand V30 rated SD card as a data drive and then regularly and redundantly back it up!

Tried Safe mode. But still the same message.
Do you reckon using odin to flash the phone will help keeping my data alive?
I've downloaded this firmware from sammobile, since it is the only one currently providing a Andriod 13 firmware.
OVERVIEW SPECIFICATIONS NEWS
Model SM-M225FV
Product Code PHN
Country Netherlands
Security Patch Level 2022-10-01
OS Version Android 13
PDA M225FVXXU4CVK3
CSC M225FVOXM4CVK3
Build Date Tue, 08 Nov 2022 03:12:04 +0000
Changelist 25282103
This gave me zip file with the following.
AP_M225FVXXU4CVK3_M225FVXXU4CVK3_MQB58986774_REV00_user_low_ship_MULTI_CERT_meta_OS13.tar.md5
BL_M225FVXXU4CVK3_M225FVXXU4CVK3_MQB58986774_REV00_user_low_ship_MULTI_CERT.tar.md5
CP_M225FVXXU4CVJC_CP23171316_MQB58440508_REV00_user_low_ship_MULTI_CERT.tar.md5
CSC_OXM_M225FVOXM4CVK3_MQB58986774_REV00_user_low_ship_MULTI_CERT.tar.md5
HOME_CSC_OXM_M225FVOXM4CVK3_MQB58986774_REV00_user_low_ship_MULTI_CERT.tar.md5
BL, AP, CP are self explanatory.
CSC and Userdata however are not.
As I said before, I've read HOME_CSC is for keeping your data in tact. CSC will overwrite.
Looking at the tips in odin, it is referring to HOME_CSC for the CSC line. This would mean USERDATA stays empty. Is my assumption correct?
Current build on the phone TPA1.220624.014.M225FVXXU4CVK3
Service provider info is OXM PHN (netherlands)
{
"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"
}
Do you reckon I safely flash this firmware?
Help is very much appreciated!
M.

The problem is likely on the user data partition not the firmware. Firmware rarely becomes corrupted unless there's a hardware failure. The exception to this is a Single Event Upset which are very rare and only switch 1 bit of the flash memory.
You can try it but if you lose the encryption keys you are boned. I have no idea of what will happen. If you really need that data take it to a data recovery specialist... now.

Thanks for all the help. I've decided to take the lost and have done a factory reset.