I have just bought a manufacturer refurbished TF300TG and have some concerns about a number of issues.
The first thing I noticed was that it did not seem to recognise the SIM card I put in it (the SIM card works fine in an HD2 running Android 4.0.4). There are no APNs listed. When I ried to manually enter the APN, the drop-down menu only has New APN and Reset to default options - no Save option, therefore I can't save the APN details. If I try to search for networks or choose automatically, I just get either "Error while searching for networks" or "Cant connect to this network right now. Try again later."
Later, after installing a few apps (via WiFi), I noticed that the drop-down menu in Google Play has no My Apps option (the first option is My Wishlist).
I saw some suggestions that the reason might be a bad firmware installation. When I try to check for System Updates, the Check Updates buttion does nothing so I downloaded all of the WW ROMs from the ASUS site (10.4.3.9, 10.6.2.3 and 10.6.2.6), extracted the .zip file from each and transferred them one at as time to microSD. Each time the system detected an update and I initiated an update from the notification pane. Each time the installation progressed until the progress bar was at about 20% and then I got the android on its back withe the red triangle/exclaimation mark (failed update, I assume, since there is a failed upograde notification when it reboots). I have also tried flashing the ROMs using the RSK method (volume down and power button from a powered-down state) with the same result, only no progress bar - the failure is almost immediate.
I also notice in About tablet/Status that the IMEI and IMEI SV are unknown.
Other information that might be relevant:
Android version: 4.1.1
Baseband version: unknown
Kernel version: 3.1.10-00003-g6293ea6 [email protected])) #1 SMP PREEMPT Thu Aug 9 15:55:41 CST 2012
Build number:JRO03C.WW_epad-10.4.2.9-20120809
I have contacted the seller but have not yet received a reply.
Any advice on what could be the problem and whether I should be able to sort it out? I'm a bit of an Android noob, so might need things explained in words of one sylable - or less.
So, nobody has any advice?
Sent from my GT-I9305T using xda app-developers app
It might be a fake?
if you have those ww .zip's extract it: there should be another zip exctract that aswell! then you see a file named "blob.blob" you need to flash that! unfortunatly you need an unlocked bootloader (i think, am i right?)
here is a link: http://forum.xda-developers.com/showthread.php?p=39069538 (i know it is about downgrading and upgrading but it will show you how to flash a blob!)
YOU HAVE TO GO TO "[UNLOCKED BL] Method 2: update using fastboot"
(Yes, unfortunatly you need an unlocked bootloader so you have to go to the official asus site and download the OFFICIAL unlock tool and unlock your bootloader)
FLASHING A BLOB TAKES ABOUT 15 MIN (ATLEAST ON MY 300T) USE YOUR FIRMWARE ZIP'S!!
right now i don't see another way of reflashing the firmware without an unlocked bootloader, sorry!
Sent from my TF300T using xda app-developers app
Thanks. I hoped that a reflash would fix it quickly. It's supposed to have a 12 month warranty so I'll go down that path and see how I go, that means I won't be able to unlock the boatloader. I'll soon find out if it's a fake, at least. If I have no luck there then I'll get the credit card payment reversed.
Sent from my GT-I9305T using xda app-developers app
unlocking your bootloader registers your serial number with asus so if unlocking the bootloader doesn't work either it's probably a fake
Sent from my Transformer Pad TF300T using xda app-developers app
Related
Hi all,
I just got a new NS 9023.
When I got it, the system was 2.3.6(I dont remember if that is official or not)
After some simple tests, I flash the rom to MIUI. And MIUI works fine.
One day later, I want my phone go back to official rom. So I download a 2.3.3 official rom from google.(The link was found on this forum)
Then the problem came - The signal is worse then before. I can't get EDGE, but before I flash the "official rom", EDGE works well. i tried lots of baseband packages but none of them works.
Can someone tell me what should I do now?
Here are some information:
product name herring
hw version: rev 52
bootloader: i9020xxka3
baseband: i9020xxdk1
carrier info: vof
A friend of mine bought a 9023 the same time as mine.
I checked his bootloader, only one different is the carrier info, it is EUR on his phone.
check the IMEI number and see whether it's true or not ?
system -> about -> status
X1111 said:
check the IMEI number and see whether it's true or not ?
system -> about -> status
Click to expand...
Click to collapse
Baseband seen from system is I9023XXKD1, which I consider is correct.
and signal strength usually between -83 ~ -93dBm both in office and outside.
Also, I found a radio dump bin on sdcard. Is there any way I can use that file?
baileifirst said:
Hi all,
I just got a new NS 9023.
When I got it, the system was 2.3.6(I dont remember if that is official or not)
After some simple tests, I flash the rom to MIUI. And MIUI works fine.
One day later, I want my phone go back to official rom. So I download a 2.3.3 official rom from google.(The link was found on this forum)
Then the problem came - The signal is worse then before. I can't get EDGE, but before I flash the "official rom", EDGE works well. i tried lots of baseband packages but none of them works.
Can someone tell me what should I do now?
Here are some information:
product name herring
hw version: rev 52
bootloader: i9020xxka3
baseband: i9020xxdk1
carrier info: vof
A friend of mine bought a 9023 the same time as mine.
I checked his bootloader, only one different is the carrier info, it is EUR on his phone.
Click to expand...
Click to collapse
At the top you say you have an i9023 but your bootloader and radio are i9020. So which is it? Is your problem because you flashed your phone with a stock rom for a different model?
Sent from my Nexus S 4G using xda premium
Don't post your IMEI in public. I suggest you remove it. X1111 just wanted to check if your IMEI is changed, but that as nothing to do with your problem. Because if that was a problem, you couldn't get any signal at all.
As I can see, you are surely cofused which device do u have, and therefore flash wrong ROM/Radio. Did you try *#*#4636#*#*? If not try dial it, choose "Phone information", pres menu button, choose "Select radio band" and choose EUR band...
If that doesn't help you, wipe /data /cache and /system in recovery and flash correct stock rooted ROM. Hope that will help...
yes. i have a 9023 device and all 9023 around me have 9020XXKD1 information on boot screen.
Sent from my Google Nexus S using XDA App
Thanks tenhi.
I tried 4636 code and change my baseband to EUR. seems better now. but still not so good. i will keep testing.
Sent from my Google Nexus S using XDA App
I got a new Desire S
It is fresh and not rooted, not unlocked and everything is just the same as the factory.
I updated it to Android 2.3.5 with HTC Sence 3.0 (using the software uodate in the phone)
Baseband: 20.4801.30.0822U_3822.10.04_M
Kernel Version: 2.6.35.10-g9ac6c7a
Build No.: 2.10.163.5 CL156318 release-keys
No I dont have any kayboard! When I tap in the fields to enter any text (message, email and all text type) nothing happens.
Attached you can see the keyboard and language pictures of the phone.
What has happened?
What can I do?
Please describe in detail
Thanks in advance.
Try a factory reset
I tryed but nothing changed!
As you see in pics,there are too few languages
What shall I do? :-(
Try installing any other free keyboard from market, for now.
You can do it from PC.
Sent from my HTC Desire S
Correct me if I'm wrong, but I think you can connect the phone to your pc and run the RUU file that matches with your carrier/phone. It just wipe and reinstall everything
Sent from my HTC Desire S using XDA
What about just installing the keyboard?
Here is the apk:
http://www.4shared.com/android/dv_M9Fh7/HTC_IME.html
See if it works.
Also since it's been wiped you may need to allow outside sources. It's usually in settings > security and then tick the unknown sources box
Thanks for all answers. But it seems something is wrong.
I installed the HTC_IME.apk from the link above, but when I want to type, it says FORCE QUIT !
Can anybody give me the original link for the RUU?
Also when I select the available languages (as shown in picture attached to the first post), all writes Austria. For example: English (Austria) or Espanyol (Austria) and so on
Also, I can not enter the Recovery menu from the bootloader. When I select the Recovery a pics comes up with the Alert Symbol (in red color). How can I enter the Recovery?
Serial Number: SH1B9TJ05334
IMEI: 358967043063815
IMEI SV: 02
aref_tmu said:
Thanks for all answers. But it seems something is wrong.
I installed the HTC_IME.apk from the link above, but when I want to type, it says FORCE QUIT !
Can anybody give me the original link for the RUU?
Also when I select the available languages (as shown in picture attached to the first post), all writes Austria. For example: English (Austria) or Espanyol (Austria) and so on
Also, I can not enter the Recovery menu from the bootloader. When I select the Recovery a pics comes up with the Alert Symbol (in red color). How can I enter the Recovery?
Serial Number: SH1B9TJ05334
IMEI: 358967043063815
IMEI SV: 02
Click to expand...
Click to collapse
That IS the recovery man... the stock HTC recovery. That's because you're still S-On and so cannot use a custom recovery until you've either S-Off'ed or Unlocked using HTCDev. Once you've done that, you can install a custom ROM with everything working....
As for your problem, i think its un-solvable because you're S-on, and basically you had a bad update that screwed up your text input.
The way i see it, you havce two options:
1. Approach HTC and ask for a reinstallation of software, since its their update that borked your phone.
2. S-Off or Unlock, and load up a custom ROM.
The choice is yours...
Hello all -
New to Android platform. Hope someone from this great forum can assist ... I'll try to be brief. First, my device:
Razr HD LTE xt925
FIDO
Android v.4.1.2
Had attempted a little while ago to unroot my phone, as I was curious about better customization options. For various reasons, I tried to 're-root' and go back to factory. Did that, upgraded from ICS Jellybean 4.1.2 (which is what my phone was on when purchased).
Now, when I boot the phone, I still get the message 'Bootloader is unlocked'. After upgrading from ICS to Jellybean, I saw a large number of Verizon specific apps. When booting the phone, instead of the Motorolla 'M' icon/splash, I get a 'Droid' icon, with sound-effects. Also, System Version shows as 9.16.XT926.Verizone.en.US (even though my phone is an XT925 on FIDO). I obviously fudged something up... !
Most importantly, ever since, my GPS is very spotty, and I cannot get on the FIDO LTE network. In Mobile Networks setting, I have to always have 'Global' selected as network. If I choose LTE/CDMA or GSM/UMTS, it can never find an available network.
I'm really just trying to get my phone back to the state is was when I purchased it.
Any ideas would be GREATLY appreciated!
Canlin said:
Hello all -
New to Android platform. Hope someone from this great forum can assist ... I'll try to be brief. First, my device:
Razr HD LTE xt925
FIDO
Android v.4.1.2
Had attempted a little while ago to unroot my phone, as I was curious about better customization options. For various reasons, I tried to 're-root' and go back to factory. Did that, upgraded from ICS Jellybean 4.1.2 (which is what my phone was on when purchased).
Now, when I boot the phone, I still get the message 'Bootloader is unlocked'. After upgrading from ICS to Jellybean, I saw a large number of Verizon specific apps. When booting the phone, instead of the Motorolla 'M' icon/splash, I get a 'Droid' icon, with sound-effects. Also, System Version shows as 9.16.XT926.Verizone.en.US (even though my phone is an XT925 on FIDO). I obviously fudged something up... !
Most importantly, ever since, my GPS is very spotty, and I cannot get on the FIDO LTE network. In Mobile Networks setting, I have to always have 'Global' selected as network. If I choose LTE/CDMA or GSM/UMTS, it can never find an available network.
I'm really just trying to get my phone back to the state is was when I purchased it.
Any ideas would be GREATLY appreciated!
Click to expand...
Click to collapse
Here's the JB file for Fido/Rogers:
http://sbf.droid-developers.org/van...12.2_CANADA_VANQJBLTEFRCI_P004_CFC_fb.xml.zip
Thanks very much for your reply. I did try flashing with the FIDO file you quoted, and my phone didn't take it. I booted to fastboot, current drivers, and the RSD Lite message I got was:
Failed flashing process. 1/21 flash partition "partition_signed" -> Phone returned FAIL
The corresponding message on my phone was: Failed flashing process. 1/21 flash partition "partition_signed" -> Phone returned FAIL
Hope someone has an idea on how to successfully get back to the FIDO Android v.4.1.2.
Thank you all!
Have you removed the Getvar lines? You can also try the Telcel rom with Fido modem/fsg files placed into it. (That's what I had before custom roms because Fido was slow with JB).
Yes, I did try when removing getvar line in the xml.
I stated erroneously the error on my phone after trying the intitial FIDO flash - the phone error in fact was:
downgraded security version
update gpt_main version failed
preflash validation failed for GPT
I appreciate the input. Any other thoughts on this? I regret trying to unroot the damned thing in the first place... !
Canlin said:
Yes, I did try when removing getvar line in the xml.
I stated erroneously the error on my phone after trying the intitial FIDO flash - the phone error in fact was:
downgraded security version
update gpt_main version failed
preflash validation failed for GPT
I appreciate the input. Any other thoughts on this? I regret trying to unroot the damned thing in the first place... !
Click to expand...
Click to collapse
From what I can see, those errors come when trying to downgrade to ICS through RSD but you are trying to install JB so that makes no sense. Since you are bootloader unlocked you can probably flash the files through fastboot?
no worries man...calm down...you'll be fine...i had the same issue..i'm actually using an xt925 as well; had the same issue a couple of days back...see the issue is the ROMs that you see for xt925/926 is actually the ROM for verizon, so when you flashed a custom ROM, it actually flashed your GSM radio to the version radio, which is CDMA; These are the steps you need to follow, and you're good to go, trust me:
1). After deleting the getvar line, delete 2 lines below it as well, so lines 12 and 13, then try flashing with this new xml file. really imp, this will take about 5-10 mins, then the phone will reboot, dont unplug the cable yet, it's gonna reboot, and ask to sync phone with SIM, do that....and you're good to go.
2). Root.
3). Install TWRP, preferably 2.5, then backup your stockROM.
4). I would recommend using Matt's utility for xt926, and you can perform all the steps in sequence.
note: Since you unlocked your bootloader, you will always get that warning message, it's normal.
lemme know if it works!
eomahos I am in your debt. Worked like a charm!
In step 4 you indicated using 'Matt's utility for xt926' ... I'm not familiar with the utility. Do I use this to install TWRP?
Thanks again man!
Good Afternoon everyone
I'm of average knowledge and have had an issue that im hoping you kind people can assist with. I will happily add more details if necessary but I'll try and keep it simple and clear for now for my current sitation and what I'm looking to do.
I've been happily using AOKP on my XT925 for a few months now and updating it every now and again. After an infinite bootloop issue last night, I was kind of buggered but after toing and froing I got into Fastboot. After not much and desperate to attempt was working I used Mr Parkinsons 2.0 tool, and with it listing flashing to stock XT925 / XT926 as its option 1, I clicked that. Successfully it flashed it with the package it uses and booted fine. I have functionality, on the phone settings strangely its now listing as XT926 but again it works HOWEVER unbeknowst (probably stupidly) to me its a VZW American default and naturally won't recognise my SIM and I can't make calls.
I'm currently trying to flash it again through Fastboot with RSD Lite 6.15 to a Stock Xt925 Firmware, ones I acquired through the thread in the XDA Dev. I'm based in the UK and my SIM / Network provider is O2. The nearest fit Firmware wise seems to be the Orange UK package or the Vodafone France ones.
The Orange UK package won't decompress in RSD as it's saying 'the filename may be too long'. The Vodafone France one will decompress - however originally it said 'unknown flashboot command - flash failed' (getvar). Having done some reading I deleted the sole line 'Getvar' string in the XML through notepad, saved it and tried again. This time is said something along the lines of 'Flash failed 2/22 - phone returned'. I've tried Googling this error and all the forums that mention it seem to be in Spanish or French.
I'm tired and it's been a long day for family issues - however I could do with having my phone back on an even keel. Please can someone help or at least point me in the right direction? I'd be very VERY grateful for any dialogue.
SHORT VERSION OF PROBLEM: Currently running the Stock Recovery Package included in Mr Parkinsons 2.0 utility. Phone is functional bar not recognising my SIM and Im in the UK on O2 and it's US centric. Concerned that in phone settings it says XT926. Recovery and fastboot options available. RSD Lite is returning primarily saying 'flash failed 2/22'
Are there any other utilities to recommend that would get me where I want to be other than RSD?
Please go easy on me! If I've not explained myself very well then and someone may know the answer then I'm happy to be more descriptive in terms of details
Additional details:
- On startup its saying 'SIM is from unrecognised source
- My current system version is 9.16.6.XT926.Verizon.en.US / Baseband: VANQUISH_BP_100730.081.64.09P
After some playing I resolved this.
In terms of anyone who should be faced with this issue, the answer lies in deleting more of the .xml file in your zip that your flashing via RSD
I browse this forum every now and again so reply if you need assitance and need me to be more specific, otherwise mods can lock this as closed.
Hi,
I recently got a Samsung Galaxy S2 GT-I9100 from my girlfriend which was locked to T-Mobile (it had been a contract phone). My contract is on Orange so I flashed an insecure kernel in Odin and used Samsung Quick Root to root the phone. I booted it up and managed to unlock (though i'm now not sure if this was a full unlock or some kind of soft-unlock, I don't know if that's even a thing - I used an app called "Galaxy S Unlock"). Anyway I tried sending a text just to make sure and it was fine. I decided to install CyanogenMod (latest version on the website), I did and all was fine. Then I was prompted to update on my phone so I did, halfway through it crashed and - being an idiot - I turned off the phone. After that I could only get as far as the Samsung logo when trying to boot and after that it would return to a black screen.
I did some Googling and decided to flash back to a stock ROM which worked and the phone booted fine. Now however, the phone asks me for the SIM unlock code (making me think this was a soft-unlock) yet I still get bars of signal but if I try to text or call I get the "Not Registered on Network" error. I've tried adding Orange's APN manually but it won't save, everytime I press save and go back into the APN it's blank. I've also tried to select the network using the "Select automatically" as well as trying both Orange and T-Mobile in the network options and simply get an "Unable to connect. Try Later" error. I've also tried to update through the phone and it says it's upto date. I'm currently running Android 4.1.2. The Baseand Version is I9100BVLS4 and the Kernel Version is 3.0.31-889555 with Build Number JZO54K.I9100XWLSY.
Could anyone give me any advice as to what to do? Thanks!
Jamie3213 said:
Hi,
I recently got a Samsung Galaxy S2 GT-I9100 from my girlfriend which was locked to T-Mobile (it had been a contract phone). My contract is on Orange so I flashed an insecure kernel in Odin and used Samsung Quick Root to root the phone. I booted it up and managed to unlock (though i'm now not sure if this was a full unlock or some kind of soft-unlock, I don't know if that's even a thing - I used an app called "Galaxy S Unlock"). Anyway I tried sending a text just to make sure and it was fine. I decided to install CyanogenMod (latest version on the website), I did and all was fine. Then I was prompted to update on my phone so I did, halfway through it crashed and - being an idiot - I turned off the phone. After that I could only get as far as the Samsung logo when trying to boot and after that it would return to a black screen.
I did some Googling and decided to flash back to a stock ROM which worked and the phone booted fine. Now however, the phone asks me for the SIM unlock code (making me think this was a soft-unlock) yet I still get bars of signal but if I try to text or call I get the "Not Registered on Network" error. I've tried adding Orange's APN manually but it won't save, everytime I press save and go back into the APN it's blank. I've also tried to select the network using the "Select automatically" as well as trying both Orange and T-Mobile in the network options and simply get an "Unable to connect. Try Later" error. I've also tried to update through the phone and it says it's upto date. I'm currently running Android 4.1.2. The Baseand Version is I9100BVLS4 and the Kernel Version is 3.0.31-889555 with Build Number JZO54K.I9100XWLSY.
Could anyone give me any advice as to what to do? Thanks!
Click to expand...
Click to collapse
The Galaxy S unlocker mods the EFS folder and putting it back to stock might have messed up something. I would re-root and re-do the unlock. hope you have a copy of the original EFS partition before you started or that the app made a backup for you in case...