Hi
I recently realised that although my "About phone" settings menu had always said that my build was called G920FXXU3QOKD, when I boot into recovery mode (the standard 3e), by the build number it said G920FXXU3QOLH
Has anyone got any idea why this occurs, and more importantly, does it even mean anything?
Thanks in advance
Its means that the recovery ur using was built from one build and ur rom from another build nothing to be worried about
Related
Hi everyone,
It seems like I received a really weird version of the Nexus S.
I ordered a Nexus S along with a new plan from Mobilicity a few days ago. When I went today to pick up the phone, the salesman opened the box and turned it on to set something up and show me how to use it.
What I immediately noticed was that the loading screen has the unlocked padlock. It also skipped the Google account sync/log-in screen when you start the phone for the first time. Instead, it went straight to the homescreen which had a red x through the Android logo in the wallpaper, with the message "* WARNING!!! S/W is not completely Installed. DOWNLOAD Full S/W Before Release"
The salesman grabbed another Nexus S but it suffered the same problem. He proceeded to "fix" the phone, which was just changing the wallpaper. (I have since restored to factory default so I can get the "warning" wallpaper again.)
I tried to sync with Google through Settings -> Account & Sync, but I get no option to choose Google, Facebook, or anything and it takes me straight to the Exchange sync screen. I can, however, use the generic email app with my gmail perfectly fine.
There are also many apps missing, most notably the Android Market. There are some weird test apps, though. LbsTestMod seems to be some sort of GPS/location testing app, and Touch noise test seems to test the touchscreen (no idea how to work them)
In the About phone screen, this is what I see
Model number: Full Android on Crespo
Android version: 2.4
Baseband version: I9020XXKD1
Kernel version: 2.6.35.7 (there's more in this section in the picture but I can't type it out because I can't post links)
Build number: full_crespo-eng 2.4 GINGERBREAD 563 test-keys
My question is, what should I do with it? This is my first android, so I have no idea what I've got here. I'd like to keep it if possible but I also need a phone that actually syncs with my Google account. Should I root it? or return it again and hope that I don't get another phone with the same problem?
I can take more pictures if anyone needs it.
install the clockworkmod make a nandroid and then flash a stock image!
Sent from my Nexus S using XDA Premium App
Borky_16 said:
install the clockworkmod make a nandroid and then flash a stock image!
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
yesss and post the system image!!!
dude u could install clockwork mod but it appears tht ur phn has been tampered with already so bettr gt it changd wit the dealer n btw ur nexus s is already unlockd
Hi Everyone,
So I recently bought the nexus s from craiglist. Its only a month old according to the person i bought it from. Now, after using the phone for few days I realized the auto-rotate feature never worked. I can not do anything in landscape mode. I went to settings>display> and checked/uncheked auto-rotate. But nothing seems to work. So I'm not sure if the hardware for this to work is defected or is it a software issue? Does anyone know anything about this or how i can figure out whether its a hardware issue or software. Also, the phone's bootloader is unlocked... i also have clockworkmod recovery.
I also see an app called super user and ROM manager. but when i open rom manager i get a msg saying "you must root your phone for ROM manager to function. Superuser was not found at "/system/bin/su" or /system/xbin/su". Use google search on your computer to find instructions to root your phone."
So, I am not sure if the phone is rooted and I don't mind rooting/unrooting as long as the auto-rotate works. so it would be great if any of you can advise me on how to get the phone's auto-rotate feature working. Thank you!
Model: I9020A
Build: GTJ61
Android Version: 2.3.4
Kernel: 2.6.35.7-ge382d80
http://forum.xda-developers.com/showthread.php?t=1007782
Read this and start from scratch.
1. Flash custom recovery
2. Flash new radio
3. Flash newest stock rom or a custom rom
New to this site but have done days of searches for my problem. Since JB update my bluetooth is not working and I have also found out Airplane mode is messed up also. Both will have slight responses for a short time after booting , then nothing. I down graded back to ICS and I get some functionality and have actually paired a device but does not work correctly. Asus wants the tablet sent back , but it sure seems to me as it is Op system causing all of this. It was working fine before. I am new to messing around with android , So one question is since I down graded to ICS 4.0 does the actual device firmware downgrade completely also ? I see that Bluetooth Version lowered and other versions lowered , but could something else not get back to that version , some type of Bios type settings? ( I was told no Bios in android ,but is there something like it ? )
So does anyone have the same problems , any answers or thoughts ?
Is there a way to erase everything completely and go back to the exact files software , kernals etc. as when in the box it came in.
Sure seems to act like a software driver type problems.
What are the "Source Code" that are offered on the Asus Site ? Can those used to be used to Factory fresh the device ?
I do not want to void any warrenty , but before I send back I want to see if it is Hardware or software.
Thanks
wadea2 said:
What are the "Source Code" that are offered on the Asus Site ? Can those used to be used to Factory fresh the device ?
Click to expand...
Click to collapse
Source code is only useful for software developers. To restore your device as close to factory state as possible, install the full firmware package of your desired version, as you already did when downgrading, and wipe data.
Things not restored by this method:
- device-dependent settings (e.g. serial number, sensor calibration data)
- DRM key
- Partition table
These usually cannot be changed by the user and therefore do not need to be restored anyway.
My main concern is the kernal, I feel that this may be the cause of my problems , if indeed the hardware does not have a problem. So when I restored to ICS , Did the kernal complete revert to factory also ? I understand now that the Kernal is the ( Bios) of Android , takes comands from software and tells hardware what to do . ( Right ? )
I am finding that the "Factory Reset " from from "Setting" does not truely reset all settings ( I set a Sound Setting before Reset , and the same setting was "on" after the reset ), therefore a "Firmware" reset back to ICS may leave the reason my bluetooth and airplane is not working.
So is there a way to use the "blob" with-out rooting or causing a warrenty issue ?
The kernel is part of the full firmware, so it is flashed when you install the firmware. It is the core of the operating system and also contains all the hardware drivers. The PC BIOS would be more comparable to the tablet's bootloader, as it only initializes the hardware and loads the kernel.
Your problem description is completely worthless. If you expect help, state exactly what you did, which error messages appear, and describe in detail what does not work and what you expected.
I thought i expalined better. I will try again. I used my bluetooth on my tablet connected to my phone and sent photos to tablet from phone. All was fine, Did not try and use bluetooth again untill a week later ( 3 days after OTA JB update ) now the bluetooth does not work and I see that Airplane mode is not working correctly either.
Since this happened right after the JB Update , It made since to me it is an update problem. I was wanting to go back to the exact state before update to see if errors were gone. I have re installed ICS and had better response from bluetooth , was able to pair a device but after pairing would not work ( headphones , sound stayed on tablet ) .
With these findings it would lead me to beleave two things , the "Firware install of ICS " left traces of the newer Kernal , that caused the problem or the Tablet hardware is the problem.
does that make more since to you ? Sorry about the first Question. I have let the tablet do the OTA back to JB and still in the same situation. I have an RMA set up , but I just like to know for sure the cause before sending back.
Thanks for you time.
wadea2 said:
now the bluetooth does not work and I see that Airplane mode is not working correctly either.
Click to expand...
Click to collapse
I'm giving up.
Ok, Well thanks for trying ? I do not have any other info. to tell you then my last reply , that is all that I can explain , What is wrong what I did and what I was trying to figure out by process of elimination.
Hi guys.I am new to forum so i didn't know where to open this thread.Also i have checked internet for a solution but never seen a dumb thing like this before in my life.So even google search engine couldn't help me about that.
One of my friend has purchased a device from dubai.it is an original device of i9505 with snapdragon 600 processor.I am personally using an i9500 octa version btw.my friend told me to check his device after he had problems with gsm service+wifi for 3g doesn't connect(or connect and drops fast) so i went to check his device.i have used some system info tools and benchmark softwares to identify the device is ok.but NO IT WAS NOT OK.all of the system info tools says that the device is i9500 but it has snapdragon processor.some idiot somehow managed to write i9500 rom to i9505 and it is working with problems.i have checked camera both ok frontal and rear.and other device properties working good as well.i should expect that it should even fail to boot but somehow working with great deal of no phone service+3g problem(phone service sometimes work i really don't know how it works or how it fails).
So i decided to make things right.Which is put the right original galaxy s4 i9505 rom to that device.i have checked sammobile and found germany version of kitkat.
general info : device is rooted.it says it has Wanamlite rom 4.2.2.
My Try list:
1)downloaded odin 3.09 and followed the instructions.(used the official rom given from sammobile.)and put the mobile to download mode(i couldn't do it with volume down+home+power button cos it is not working)but i thought i was lucky cos that custom rom had an option when i push the power button/restart/ it says there is a download menu so i choose that to put the device to download mod.after that i was hoping odin will do the job.but it FAILED DUE TO WRITE PROTECTION ENABLED on device.
2)i tried to setup cwm recovery to device(which i figured out later it was already on device but i didn't know it was there).downloaded rom manager from playstore.and i thought it would work.rom managers says i had 2 recovery programs or rom managers on the phone 1 is cwm and other is teamwin recovery.also rom manager asks me to update or upgrade cwm but it does't recognise the device cos it is i9505 with i9500 rom and rom manager couldn't identify the device as it should be.so cwm update doesn't work.also i couldn't get to the user interface of cwm which is already on the device no matter what i do.also i know old version of cwm will not make it happen for what i need to do if i was able to get in the user interface as well.i think teamwin is blocking cwm.
so on rom manager i decided to use the team win cos there is no other option for me there which puts the phone after a restart to recovery mod,the user interface works ok there but teamwin also FAILED TO WRITE THE ROM(i think it is an old version too)i couldn't say the exact version of cwm cos the device is not with me and i forget the version but team win i asked to my friend just yet and he said TWRP 2.6.00 is on it.
3)CWM i can't even get to user interface,i really don't know how to with team win there.So yeah i couldn't even give a try.
4)I am stuck.and i don't know what to do.
general user profile about me: i have a general understanding of computers,but i haven't written any rom to galaxy s4 before yet i found myself in a situation i can't handle.someone screwed up an i9505 with a i9500 rom.
ANY HELP FROM ANYONE will be very appriciated.
i have managed to upgrade tw recovery with flashify to final version but in odin still write protection is enabled in the download mod.so odin again failed.btw after upgrading tw with flashify i lost my ability to get into operating system.i just have tw recovery on the screen atm.
the rom file i tried is this one I9505XXUFNB8_I9505VFGFNB3_I9505XXUFNB8_HOME.tar.md5 which i have downloaded from sammobile.
I9505XXUFNB8_I9505VFGFNB3_VOD.zip vodafone version it says for uk.
now i have a screen of tw recovery when the device opens.strange thing is i have 2 versions of tw recovery installed at the same time.when i press volume up+home+power tw version 2.6.00 loads.
or when i open the device with only power button tw recovery 2.7 loads.no operating system yet.
i tried I9505XXUFNB8_I9505VFGFNB3_VOD.zip with tw. it gave me an error of md5 not found and failed.
what now?
anybody around there to help?
another note : i don't know if it is important or not but it says the product name is sghi337.checked google it says at-t network.is this a useful information or what to identify the problem?
all i want is any rom to make the device work again with fully functioning.
after having twrp 2.7 i tried some roms had md5 error,so after a search i wanted to try wanamlite rom wanamlite-xxufnbe-v2-4-android-kitkat-4-4-2-xposed.after installing wanamlite rom it has asked me to reboot.so i did reboot it.it had adam kernel 2.1 version.
i was expecting the device will reboot but thanks to at&t for making odin useless + making twrp useless as well.it had a message on the screen and it was written ''samsung custom'' with a locker logo open.i thought i have to wait for the first boot and be patient and after waiting about half an hour still nothing.(on the left up of the screen written red : kernel)i checked more than maybe hundreds of threads to find an answer about at&t sghi337 galaxy s4 and some ppl say i have to change the kernel.and some say i have to change it to at&t kernel i searched again for an at&t kernel i found a file name KT-SGS4-TW-JB-ATT-06-06-2013.zip.then i gave a try to that.but suddenly i realized i have lost the ability of booting to twrp 2.7.all i have left with is twrp 2.6.00 when i press volume up+home.still lucky to have it.i used that kernel reboot and got a message on the screen ''system software not authorized by at&t''.then i started searching again ppl say about loki doki.downloaded the file and flashed it on at&t kernel this time it showed samsung logo appeared and the boot sound which you know all of us familiar with and samsung led was blue.the led was like it is a pounding heart coming on and off.this should be the first load of the rom i thought again and waited and got no result.it didn't load again.failed failed and failed many times.
i also tried this file named MDOB-KERNEL2STOCK-LIB.zip.flashed it no result again.failed.this result was another strange thing.it was showing samsung custom logo boot it with sound and then turn the device off after 10 seconds.and repeats the process.reboots sounds and reboots again and again.
questions :
1) do i have a bootloader locked device?since i can't use odin to flash anything.(odin version 3.09) and if i have what can i do to fix it?
2)since i only have twrp 2.6.00 how can i upgrade it to 2.7 back with twrp.i mean twrp update using twrp.
3)with twrp 2.6.00 i used wanamlite rom kitkat version.and it says it has flashed it.but can it flash roms succesfully enough like 4.4.2?if it says it flashed everything is ok? or it misses some important features to make the rom work.what is the maximum capability of twrp 2.6.00.Do i have to try roms like 4.2.2?
4)about kernels with at&t i337 galaxy s4 what can i do?what should be the reason preventing the rom load successfully?if i have access to twrp does it mean i don't have to mess with bootloader cos i have already passed that step and got an interface for loading roms?i mean everything is ok with bootloader if i have twrp installed user interface? and after flashing a rom do i have to use the specific kernel coming with the rom or can i use any kernel for the device like stock kernels(doen't allow me to load) with loki doki or some kernels with loki doki?
i am so helpless,please enlighten me with your knowledge.any moderators or any developers can answer me?or help me?
stuck in the middle of nowhere.please help.
Getting some progress at the end!!!
Since twrp 2.6.00 is the only option i have,or i can say ''was the only option i had'' i knew i had to get an android user interface for upgrading my recovery.after a bit more search i found slimroms for android version 4.2.2 just to make the device run,and it is already loki patched.so yeah that rom flashed as lightspeed and loaded extremely fast!that worked!!! i have downloaded aptoide market since it was lacking google apps.and downloaded flashify to upgrade the version of twrp to 2.7.01.from now on i believe i can find my way to whichever kitkat rom that is loki patched would work with this recovery support.
THANKS TO SLIMROMS for making downloadable and flashable small sized roms and tnx for the guy whoever found the loki way to make it possible.Also great thanks to TWRP team!!!
PLEASE NOTE THAT : Why did i write this after no reply or no help or no messages to this thread?Because i have figured out my way reading,trying and hard pushing after failing a lot but i found my way with xda developers threads out there even no one ever replied for help.I mean thanks anyway :cyclops:
When in doubt, flash to stock ROM and proceed from there.
you mean to tell me u cant enter download mode? ask someone to press the 3 buttons together to enter it and flash the firmware specified for that S4.
Hi All,
I've had my phone for a few weeks so far, and everything is good apart from one "small" problem: sometimes screen does not turn on when I try to use it.
It happens every 2 or 3 days, but recently happend twice in one day. The only way to exit the state is to 'volume down - home - power' the phone.
What's interesting - the phone keeps working. It happened once while the phone was in tethering mode, and it kept sharing internet even after entering this 'black screen' mode.
Is it a known issue ? Can it be a hardware one ? And is there any way to know what's causing it, i.e. any kind of logs that would be on my phone after full restart ?
You can check /proc/last_kmsg for the kernel logs of the previous boot. If you're not rooted, the bug report generated in developer options includes it. If you're willing to keep usb debugging enabled you could also maybe pull a logcat while the screen is blanked using adb.
Tbh I've not heard of this problem though. What firmware build are you on?
CurtisMJ said:
You can check /proc/last_kmsg for the kernel logs of the previous boot. If you're not rooted, the bug report generated in developer options includes it. If you're willing to keep usb debugging enabled you could also maybe pull a logcat while the screen is blanked using adb.
Tbh I've not heard of this problem though. What firmware build are you on?
Click to expand...
Click to collapse
Thanks for the tip, will try to get the logs when it happens again.
I've got SM-G930FD, latest official firmware: Android 7.0, Baseband G930FXXU1DQC2, Kernel 3.18.14-10422490, Build number NRD90M.G930FXXU1DQC4.
svladimir said:
Thanks for the tip, will try to get the logs when it happens again.
I've got SM-G930FD, latest official firmware: Android 7.0, Baseband G930FXXU1DQC2, Kernel 3.18.14-10422490, Build number NRD90M.G930FXXU1DQC4.
Click to expand...
Click to collapse
That build is somewhat old actually (February security patches?). Samsung had a really rough start with Nougat, an update might fix it when available.