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.

[GUIDE] SIM-unlock your i9305

Hello guys (and girls) and welcome to (probably) my first guide
!! Be aware, I have tried the following procedure and am using S5 Elite Lite ROM by MaHo_66 !!
To start the unlocking procedure, first see if your device is actually sim-locked by inserting another sim-card from another provider and see if it asks for a code. If it asks, press on dismiss. Now, the actual steps:
Take a note of your CSC and MODEM with the help of Phone INFO.
Download from my GDrive I9305XXALI5_I9305EVRALI5.zip and copy it to either an USB OTG drive or to a MicroSD card (if you have one).
Make sure you have a custom recovery installed. Boot into it with the VOL UP+HOME+POWER button combination and make a nandroid backup of your current ROM. Make sure to do it on the MicroSD if you have one.
Go and do an advanced wipe and only wipe the following partitions: Cache, Dalvik Cache, Data and System.
Now install the zip file you previously copied on either an external USB OTG drive or on the MicroSD card.
While the rom is booting, search around on XDA for the aforementioned CSC code and a suitable modem for your BACKED UP rom.(The ZIP file I provided you will have changed the modem and CSC, so make sure you noted the CSC and modem before)
After the rom is done booting, skip the set-up wizard and the network lock screen. Now, go to the dialer and type *#197328640#
Here, go this way: [1] UMTS > [1] Debug Screen > [8] Phone Control > [6] Network Lock > [3]Perso SHA256 OFF > and wait for around 30 seconds. If you see at the Network Lock screen 4 options, you are good to go.
Press on the menu button (device) and tap on Back. Then, choose [4] NW Lock NV Data INITIALLIZ. After about 30 seconds, you should see PERSO_NV_INIT is SUCCESSFUL. From this point , you are unlocked. You can use any sim card in the device. If you have a third carrier sim card, test it out.
Reboot the phone and enjoy your unlocked phone. NOT SO FAST.
Reboot back to recovery and do an advanced wipe (the following partitions: Cache, Dalvik Cache, Data and System). Restore your nandroid backup now. Don't reboot the device to system, but go and flash the MODEM and CSC. Now, you are ready to reboot back to system and enjoy your KitKat or Lollipop ROM.
{
"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"
}
12.
Go to UMTS-COMMON-NV REBUILD and then tap Erase only Backup, then after it is done head back and tap on Make Back-up. You are all set now in case you restore the NV again by mistake, the simlock status will remain OFF.
The sim-unlocked devices do not really exist, they are just unlocked from the factory after a NV backup. If you restore the default NV, it simlocks it.
Click to expand...
Click to collapse
That's it. Now you are SIM UNLOCKED, have your device the way it was before and with a backed up NV in case something goes horribly wrong. Special thanks to @LucasBass for his thread, to RCS&RDS for their internet, and to Enel Energie Muntenia for not failing on me.
P.S. I didn't find the zip somewhere, so credits to @lamahgra for lamahgra-rom.v1.4-lite. All i did was download I9305XXALI5_I9305EVRA5_EVR.zip and extract&replace the system folder, the baseband.bin, boot.img and hidden.img and edit CSCVersion.txt and SW_Configuration.xml.

Must try that..

How can I do step 12 after I've restored my lollipop rom?

@Vvaheed, @singhdhirendra28, @Geofftey, @ZoranAncev, @newstead01, @senpdy:
Ladies & gentlemen, please be aware that this thread is for the Samsung Galaxy S3 LTE (aka GT-i9305). If you posted due to post #4 please be aware that the account of the user who posted that is already disabled.
I don't intend to ask why you need the codes or ouvertly publish IMEI's.

Thread cleaned!
Be aware that if you share your IMEI this can be used by other users and your device turns into a ded piece of hardware.
NEVER SHOW YOUR IMEI!

did not work for me
i just tried this now, it did not work for me
it had some "could not map..." error
Thank God i had a Backup, the process left my phone without an OS

HTC One (M7): Encryption was interrupted and can't complete (no external SD card)

I've shut my phone off before going to bed a few nights ago, then when i woke up, i turned my phone on and all i after a default lockscreen is this message :
"Encryption was interrupted and can't complete. As a result, the data on your phone is no longer accessible. To resume using your phone , you must perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google Account."
{
"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 just borrowed this image from another forum as i cant get a screenshot of mine)
if i stay on this screen i can shut my phone off an on and the volume rocker still works, but the only other option i have is to click the RESET PHONE button.
doing so however only gives me the Android System Recovery mode with the ff options and results i get:
1. reboot : if i choose this, the dead android guy just flashes off and on and i can no longer shut my phone down. have to drain the built in battery to shut it down and try another option.
2. apply update from adb: prompts me to sideload a file.. no idea how to do this.. and i believe usb debugging might be required and i recall my usb debugging mode was off before this issue happened.
3. apply update from external storage : the htc one has a built in sd card (apart from the internal phone storage), and i have no update file on it, nor do i have a way of copying one onto it.
4. wipe data/reset : did so, after which, will need to select reboot option, and will just give same result for option # 1 as above..
5. wipe cache partition : same results as #4.
6. apply update from cache: no idea how to do this either.
i would desperately want to recover my files from the built in external storage. but i'm crossing my fingers anyone can help me get the phone fully functional. factory state will be fine. help please..

Anyone who can help? Thanks

Phone does not recognise encrypted storage, please help!

Hi,
There is this bug on LOS16 that if the pop up camera is up and then the device switches off, the camera stays up permanently until a stock rom is reflashed. I had this issue before, so I restored a backup I made on MIUI 10.3.16 using TWRP, but the device was stuck in a bootloop, and the camera was still stuck, so after restoring different backups I made, I decided to finally use MiFlash to fastboot flash MIUI 10.3.16, and I chose the 'keep user data' option, however this also bootlooped and went into MIUI recovery. I reflashed TWRP and now I face this issue:
TWRP does not recognise that my phone is encrypted, and does not ask for my password, so I can see that my files are here, but they have random folder and file names. (example shown below)
{
"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 managed to get MIUI running, however it does not ask me for my password, only my Mi account password.
I restored a LOS16 backup I made ages ago, and that also does not ask me for my password - the files I see in the file manager are all encrypted like TWRP.
I attempted the 'twrp decrypt' command, but that does not work either.
I attempted flashing backups and custom roms from a USB, using PitchBlack recovery, OrangeFox, and two TWRP versions.
All I want is for either a recovery or a rom to ask for my unlock password, so it can use that to decrypt my files.
I am not 100% sure if using MiFlash is what caused this, but is there anything else I could try? Are all my files gone? I cannot copy my encrypted files over to my PC and Windows returns an error when trying to do so. Are there any 3rd party tools I can use to decrypt my stuff?
I know I could just wipe my storage and start again, but I do not really want to do that until I know for sure that my files are gone.
I was thinking that MiFlash wiped the decryption keys from my device, but wouldn't a backup restore them?
If it is not possible to save my files, could someone explain why, so I do not make the same mistake again?
Any help would be appreciated.

Format Data, you cant go from miui to aosp or vice versa without doing that. backup your data to pc before or whatever cuz it wipes all internal.

Best thing to do is to fastboot flash again, but use the clean all option.
It's never a good idea to dirty flash when doing anything other than updating a ROM. You might sometimes be OK if flashing from one AOSP ROM to another AOSP ROM.
If your going from MIUI to a custom ROM, or from a custom ROM to MIUI, then it's not worth the aggro you'll most likely get by dirty flashing. Just spend the extra time backing up your data and save the headache.
As for the data, try installing a different TWRP and see if that will then ask for a password to decrypt the phone, before you do a clean install of MIUI.

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