Database Info

[Q] lock symbol

hey guys....well i downgraded my nexus s 9020T for 4.0.3 to 2.3.6...however but while switching it on the 2.3.6..im getting a lock symbol while switching it on..and when i insert my sim onto the phone ..it is recognising the network but not catching the signal
kindly help me out

The lock symbol at the bottom means your bootloader is unlocked. This means you can replace your recovery partition to CWM or the likes, as well as flash superuser to the OS and flash custom ROMs. You would have achieved this through the "fastboot oem unlock" command.
The signal issue may be related to a bad flash. I would be going into recovery, doing a factory/data reset, formatting /system and /boot, and then flash the 2.3.6 file you have again. Remembering of course to backup anything currently on the phone, and doing a NANDROID backup if you don't have a working one already.

thank so much for the information...after doing this..can my phone still OTA official updates from google once they are released??

roshan567 said:
thank so much for the information...after doing this..can my phone still OTA official updates from google once they are released??
Click to expand...
Click to collapse
As long as you flash a official update
Sent from my ice cream powered Nexus S

a friend of mine is doing the flashing...any idea as to how can i know whether he has flashed an official update or not?

also what is the different between flashable roms n the increamental updates given in this link??
http://forum.xda-developers.com/showthread.php?t=1063664
are both official versions given out by google?

Yes, all of the links in that thread are official Google builds. The full/flashable ROMs are the full operating system in one file. You can install this over any Android version/ROM since the zip will contain all of the files necessary to get the system working.
The incremental updates should only be used if you have a specific (official) Android version and wish to only install the updated files. For example, if you have the official Google release of 2.3.6 and wish to upgrade to 4.0.3, you can use the 2.3.6 -> 4.0.3 incremental update. Otherwise, if don't have one of the supported incremental update versions or if you're using a non-stock ROM then you'll need to download the full ROM.

thank you so much for the information....
i am downgrading my OS to 2.3.6 from 4.0.3..how can i find out whether the 2.3.6 OS ive installed is the original OS???

You can find out BEFORE flashing the rom by comparing checksums, the zip file should have the exact same checksum as indicated in the filename of the files in that thread. Also, that thread just links to files from googles servers used for official updates.
Once it's installed there is no point trying to finding out if it is 100% stock.

Harbb said:
You can find out BEFORE flashing the rom by comparing checksums, the zip file should have the exact same checksum as indicated in the filename of the files in that thread. Also, that thread just links to files from googles servers used for official updates.
Once it's installed there is no point trying to finding out if it is 100% stock.
Click to expand...
Click to collapse
thanks for the information...i didn understand properly how do u do checksums..can you pls explain it??im a noob..

Checksum (or hash) is a way to verify a file. It will create a word/number/pattern/etc according to an algorithm based on all the data in the file. With MD5, SHA1, etc we have a practically guaranteed chance of comparing the two files. Those files there are straight from google and google has provided the checksums in the filename (part of the checksum, at least). If you have any file at all and it has the same code as that, we can be happy that it's the exact same file - thus 100% stock
You can use software such as Checksum or my personal favourite HashTab to find the various comparing techniques.

hey thanks a lot for your information..it really helps....
when i upgraded to ICS my phone stopped receiving reception after 2 days..when i downgraded it after unlocking the bootloader it still wasnt receiving recepetion...why does this happen?

[Q] Installing ANY rom on my VZW tab2

Just wondering about something since it seems the Verizon model seems to be the least popular. Alas, what I was under the impression with the way android works is: I can flash ANY rom thats designed for this specific device (the tab 2 7.0). As long as the radio (Baseband) isn't touched then you should be ok.
Am I correct in those assumptions? Would there be an instance where this wouldn't be the case?
Finally, most Rom packages just include the OS, not the kernel, baseband or anything else, right?

JDMpire said:
Just wondering about something since it seems the Verizon model seems to be the least popular. Alas, what I was under the impression with the way android works is: I can flash ANY rom thats designed for this specific device (the tab 2 7.0). As long as the radio (Baseband) isn't touched then you should be ok.
Am I correct in those assumptions? Would there be an instance where this wouldn't be the case?
Finally, most Rom packages just include the OS, not the kernel, baseband or anything else, right?
Click to expand...
Click to collapse
First, most ROMs flash everything. You wouldn't get a boot if it didn't flash the kernel. With that being said, you can't just flash any ROM from any Tab 2 model. There are many different models, 3113, 3110, 3100, etc.

RikRong said:
First, most ROMs flash everything. You wouldn't get a boot if it didn't flash the kernel. With that being said, you can't just flash any ROM from any Tab 2 model. There are many different models, 3113, 3110, 3100, etc.
Click to expand...
Click to collapse
Ok Im starting to understand: Correct me if I'm wrong though, but to make a device work you need :
Rom = Operating systems & drivers
Kernel = heart of the Android OS.
Bootroom = Allows unit to turn on and start the POST.
Baseband / radio = specific software on for the modem (making calls, data, tower connectivity).
Im I anywhere close here. I always assumed the "ROM" only included just that,.....the rom

JDMpire said:
Ok Im starting to understand: Correct me if I'm wrong though, but to make a device work you need :
Rom = Operating systems & drivers
Kernel = heart of the Android OS.
Bootroom = Allows unit to turn on and start the POST.
Baseband / radio = specific software on for the modem (making calls, data, tower connectivity).
Im I anywhere close here. I always assumed the "ROM" only included just that,.....the rom
Click to expand...
Click to collapse
Usually, the term "ROM" is used in an all encompassing way. You're thinking of the term ROM in a strictly PC based way. For Android, a ROM includes everything. If you DL a ROM zip and and unzip it, you'll see that baseband, boot.img (kernel), OS, etc. are all included in a ROM package.
The ROM is the "heart" of the package. The kernel is what allows the software to work with the hardware. You are right about the baseband, it is the radio "heart."

RikRong said:
Usually, the term "ROM" is used in an all encompassing way. You're thinking of the term ROM in a strictly PC based way. For Android, a ROM includes everything. If you DL a ROM zip and and unzip it, you'll see that baseband, boot.img (kernel), OS, etc. are all included in a ROM package.
The ROM is the "heart" of the package. The kernel is what allows the software to work with the hardware. You are right about the baseband, it is the radio "heart."
Click to expand...
Click to collapse
I supposed that is correct. I only questioned this because I've seen "Rom" threads that have people asking: Does it effect the kernel, does it modify the baseband. In almost all of those cases the resounding answer is NO, no id does not effect those. It only writes to the data partition.
Maybe installs of that nature have a different name or category for them, this i am not sure.

JDMpire said:
I supposed that is correct. I only questioned this because I've seen "Rom" threads that have people asking: Does it effect the kernel, does it modify the baseband. In almost all of those cases the resounding answer is NO, no id does not effect those. It only writes to the data partition.
Maybe installs of that nature have a different name or category for them, this i am not sure.
Click to expand...
Click to collapse
Most ROMs use the same baseband of the latest update for that device. Also, many use a stock based kernel. So, in that way, it really doesn't affect the baseband or kernel.

soak test

The soak test works on the OPS 27.104 US variant (XT1925-6)and (XT1925-13)IF you don't wanna wait for the pie soak
.this is for if the official way of installing it doesn't work
Intstuctions
unlocked bootloader is required
Find the firmware of OPS27-82-87-3
Flash all partitions.
Flash the boot.img and recovery.img from the OPS27-82-87-3 firmware in twrp do not flash twrp boot it(fastboot boot PATH ect twrp.img)
Let device boot up.setup ect...
Boot into stock recovery
Now rename the soak test to update.zip.
Sideload it with adb.itd take awhile.
Some partitions will fail to flash (error 7)(but along as it states the system and vendor was patched and boot you are up and running the pie soak test.
YOU MUST USE THE SIDELOAD METHOD.If the official method fails
use if you wanna try pie soak test on the (XT1925-6 variant)or (XT1925-13 )also confirmed
And I was able to successfully revert back to the stock OPS27-104 Stock Rom for people that may want to go back for some reason
The software update channel is retus
May work on other devices try it
Link to Get OPS27.82-87-3
https://moto.netlib.re/ali/ALI_OPSS27.82-87-3_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
I suggest trying the official way to install the soak test first then resort to this if you please to

What it should look like

You're a little late to the party and your instructions are incorrect. Please do us all a favor and remove this post before some seriously screws up their device.
Yes, the "soak test" can be flashed on all Moto G6 variants. No, it does NOT need to be flashed with adb by sideloading it. In fact, I do NOT recommend that method. It can be installed COMPLETELY without ANY errors. Also, there are two version of Pie currently, and both can be successfully installed correctly by live updating while the device is up and running as long as the user is on the correct firmware for either Pie version.

Jleeblanch said:
You're a little late to the party and your instructions are incorrect. Please do us all a favor and remove this post before some seriously screws up their device.
Yes, the "soak test" can be flashed on all Moto G6 variants. No, it does NOT need to be flashed with adb by sideloading it. In fact, I do NOT recommend that method. It can be installed COMPLETELY without ANY errors. Also, there are two version of Pie currently, and both can be successfully installed correctly by live updating while the device is up and running as long as the user is on the correct firmware for either Pie version.
Click to expand...
Click to collapse
That was the only method that worked on my device.i even tried the other builds,and the live update it always failed.i was on the OPS27.104 firmware

Forgive my ignorance, but what is a soak test and what are the benefits of it?

ImpytheBiscuit said:
Forgive my ignorance, but what is a soak test and what are the benefits of it?
Click to expand...
Click to collapse
Beta test to work out bugs... you may get a nice refreshing rain of an update... or the rain may be yellow, and smell, and not come out of your clothes.

Questions About Bootloader, Root and Roms

Looks like I'm gonna get a free P2 from my son. It maybe has 1 update left before Google abandons it. When I get it I want to root and put Lineage on it, or maybe a different rom based on opinions provided.
I have some questions:
1- I'm looking for the simplest method to unlock the bootloader and root, as I am not the most knowledgable Android/Linux user. I'm familiar with adb, although best if I can follow a written script. I would appreciate a recommendation on which method posted on XDA. I've seen Deuces and Nathanchance's methods. They seem easy enough to follow along with.
2- I'm a little confused about the Pixel factory images that folks mention in their posts. I see that Google has images catalogued on their site for downloading. How do you choose which one to flash to the phone after bootloader/root process? Does it matter? I'm located in Canada if that makes a difference.
3- I have used TWRP and never used Magisk for loading roms. I also see from one of the bootloader unlock/root methods that TWRP may not be all that reliable. Would TWRP be good enough to flash the factory image with, or should I get familiar with Magisk?
4- Am I correct in thinking that the Google image is flashed first to get the phone up and running, followed by Lineage (and gapps), or an different rom that would be flashed thereafter with TWRP/Magisk?
5- If I screw up during the unlock/root is there a recovery method available?
Thanks for any help provided.

jjcdennis said:
Looks like I'm gonna get a free P2 from my son. It maybe has 1 update left before Google abandons it. When I get it I want to root and put Lineage on it, or maybe a different rom based on opinions provided.
I have some questions:
1- I'm looking for the simplest method to unlock the bootloader and root, as I am not the most knowledgable Android/Linux user. I'm familiar with adb, although best if I can follow a written script. I would appreciate a recommendation on which method posted on XDA. I've seen Deuces and Nathanchance's methods. They seem easy enough to follow along with.
2- I'm a little confused about the Pixel factory images that folks mention in their posts. I see that Google has images catalogued on their site for downloading. How do you choose which one to flash to the phone after bootloader/root process? Does it matter? I'm located in Canada if that makes a difference.
3- I have used TWRP and never used Magisk for loading roms. I also see from one of the bootloader unlock/root methods that TWRP may not be all that reliable. Would TWRP be good enough to flash the factory image with, or should I get familiar with Magisk?
4- Am I correct in thinking that the Google image is flashed first to get the phone up and running, followed by Lineage (and gapps), or an different rom that would be flashed thereafter with TWRP/Magisk?
5- If I screw up during the unlock/root is there a recovery method available?
Thanks for any help provided.
Click to expand...
Click to collapse
Would appreciate some help...

Pixel 2 was updated to android 11, and will likely continue to to get monthly security updates until the release of android 12, so you should have about another year if staying stock.
As far as rooting, the xda guides as you mentioned are pretty straightforward and comprehensive.
Pixel factory images are the stock system images that are provided by google. They are what you would flash if you wanted to run a stock system, and also the means for 'resetting' the phone back to a factory state in the event of a screwup. On the site, you'll notice that google has each of the images organized by phone type (the Pixel 2 is walleye) and within each phone type is operating system version going from oldest at the top to newest at the bottom. Typically you'd want to flash the newest os version unless you have a special use case. There are also cases where a particular version is only for a particular carrier, in which case google will note it under the version number.
As far as flashing lineage, I'm not too sure. I run stock (rooted) on my P2, but lineage is it's own rom so would be flashed directly via twrp. I would image the lineage thread would have install instructions and q/a.

clcdev said:
Pixel 2 was updated to android 11, and will likely continue to to get monthly security updates until the release of android 12, so you should have about another year if staying stock.
As far as rooting, the xda guides as you mentioned are pretty straightforward and comprehensive.
Pixel factory images are the stock system images that are provided by google. They are what you would flash if you wanted to run a stock system, and also the means for 'resetting' the phone back to a factory state in the event of a screwup. On the site, you'll notice that google has each of the images organized by phone type (the Pixel 2 is walleye) and within each phone type is operating system version going from oldest at the top to newest at the bottom. Typically you'd want to flash the newest os version unless you have a special use case. There are also cases where a particular version is only for a particular carrier, in which case google will note it under the version number.
As far as flashing lineage, I'm not too sure. I run stock (rooted) on my P2, but lineage is it's own rom so would be flashed directly via twrp. I would image the lineage thread would have install instructions and q/a.
Click to expand...
Click to collapse
Thanks very much for the help.

Are MediaTek 6563 and 6567 ROMS interchangeable?

I have an RFinder B1+(14) that works fantastic, it has the 6567 chipset. I also have an RFinder B1 Classic with a 6563 chipset that will not boot into Android 8 on the way, and the ROM has not been easy to find.
I suspect they are NOT compatible, but if I did flash the older radio with newer firmware, I'd be able to reverse the damage as long as I didn't overwrite the preloader.
If the two are, in fact, compatible, it would save me some time.
Are they compatible?

N
shadow460 said:
I have an RFinder B1+(14) that works fantastic, it has the 6567 chipset. I also have an RFinder B1 Classic with a 6563 chipset that will not boot into Android 8 on the way, and the ROM has not been easy to find.
I suspect they are NOT compatible, but if I did flash the older radio with newer firmware, I'd be able to reverse the damage as long as I didn't overwrite the preloader.
If the two are, in fact, compatible, it would save me some time.
Are they compatible?
Click to expand...
Click to collapse
Not without porting them from one to the other, "IF" the sources to do so are available(either stock firmware for the two devices or at least the stock source code for the device the ROM will be flashed on.

I have tried without success to compile software. Of course it can be done, I just haven't got the hang of it (I need to learn though).
If there are other things I can do, learn, etc from this thread, I'm all ears. If not, thank you for the info.

shadow460 said:
I have tried without success to compile software. Of course it can be done, I just haven't got the hang of it (I need to learn though).
If there are other things I can do, learn, etc from this thread, I'm all ears. If not, thank you for the info.
Click to expand...
Click to collapse
There really isn't a 100% all in one get it right the first time guide out there. There are lots of guides that give a general idea of how to port stock ROMs but it will still require trial and error to iron out the details. Do some research to see if there are any specific security features preventing the ported ROM from flashing/booting then see if there are any tricks to bypass those specific features. You may need to unlock the bootloader and dig into trying to modify the bootloader.img located in the copy of your devices currently installed stock firmware file(or the last "official" firmware that was installed on your device before you tried to modify it).