[Q] 32gb won't update to 4.1.2 - Nexus 7 Q&A, Help & Troubleshooting

I have the following 32gb Nexus-7.
Model - ME370T with Android 4.1.1.
Build no - JRO03S.
The tablet works perfectly, however I have made several attempts to update the software to the new version (4.1.2) but to no avail.
I go through the software update procedure, but unfortunately when the software tries to update I get the Android icon lying horizontally with a red exclamation mark which lasts for 5 minutes before the tablet resets itself.
When logging back in the software is still on version. 4.1.1. I have factory reset the tablet on several occasions and I cannot get version 4.1.2 to install at all.
Can anyone offer their advice as to whether this is a fault that requires a return to the store for a replacement? Or should I wait on version 4.2 coming out first then trying the newer update? As I've noticed that the new 32gb model has a different build number compared to its predecessors.
Many thanks in advance.

Related

Help! IMEI=0 only 4.2.2 boots no signal

I was on stock android version 4.2.2 with stock recovery and unrooted when I received the 4.3 version notification after updating the boot animation remained stuck on the X logo for hours and clearing cache,data from stock recovery didn't help it boot. I flashed the factory 4.2.2 image and it finally booted but I had no phone signal only wifi was working. On inspection I discovered that the baseband was 'unknown' and IMEI number, IMEI SV reset to zero. Strangely the baseband was being detected while in bootloader mode. I have tried both custom recoveries, flashed various roms through custum recovery as well as stock factory images right uptil kitkat. These are my findings:
All Android 4.2.2(and 4.2.1) based roms boot but with baseband unknown and IMEI 0 rendering the phone unable to make calls and send/receive text messages.
All Android 4.3 roms don't boot are stuck at boot animation(flashing old radios like 0.48 and other older versions didn't help)
All Android 4.4 roms also behave the same way as 4.3 i.e stuck at boot animation.
Bottom line is I am stuck on Android 4.2x with a non working radio IMEI=0.... My device is now a mere tablet with inability to be updated. I have seen many people with similar problems but all such threads remain unresolved. I don't know what bug in 4.3 has done this to my phone I even tried the 99 percent working unbrick method but to no avail. I am considering selling this phone at a big loss(cant do much because I am in Pakistan) if any experienced developer is able to help me with fixing my phone(if that's even possible) then I shall be really grateful. Otherwise its bye bye Nexus 4.
liquidmetal88 said:
I was on stock android version 4.2.2 with stock recovery and unrooted when I received the 4.3 version notification after updating the boot animation remained stuck on the X logo for hours and clearing cache,data from stock recovery didn't help it boot. I flashed the factory 4.2.2 image and it finally booted but I had no phone signal only wifi was working. On inspection I discovered that the baseband was 'unknown' and IMEI number, IMEI SV reset to zero. Strangely the baseband was being detected while in bootloader mode. I have tried both custom recoveries, flashed various roms through custum recovery as well as stock factory images right uptil kitkat. These are my findings:
All Android 4.2.2(and 4.2.1) based roms boot but with baseband unknown and IMEI 0 rendering the phone unable to make calls and send/receive text messages.
All Android 4.3 roms don't boot are stuck at boot animation(flashing old radios like 0.48 and other older versions didn't help)
All Android 4.4 roms also behave the same way as 4.3 i.e stuck at boot animation.
Bottom line is I am stuck on Android 4.2x with a non working radio IMEI=0.... My device is now a mere tablet with inability to be updated. I have seen many people with similar problems but all such threads remain unresolved. I don't know what bug in 4.3 has done this to my phone I even tried the 99 percent working unbrick method but to no avail. I am considering selling this phone at a big loss(cant do much because I am in Pakistan) if any experienced developer is able to help me with fixing my phone(if that's even possible) then I shall be really grateful. Otherwise its bye bye Nexus 4.
Click to expand...
Click to collapse
try this for reference http://blog.falcondai.com/2013/10/fixing-galaxy-nexuss-imei-number.html
But this post specifically required the IMEI number to be exactly the SAME as mentioned otherwise it says the method wont work and it also seems to be T-Mobile blocked IMEI or something I don't think this fix is for my issue(correct me if I am wrong I am a noob lol)
My IMEI issue seems to linked to the Android 4.3 update which has broken something and this problem seems quite common on Nexus 4 as I came across many threads with people with exactly the same issue as mine. All the replies given usually say wipe cache and/or flash factory image sadly the problem remains.
I am really disappointed at my decision to buy the Nexus 4(my year long experience with the Galaxy Nexus was without issues) I never expected Google to release an update that breaks radios of many users(just google this problem many seem to have exactly the same symptoms as mine but the problem remained unresolved) and then remain silent despite many complaining on their product support forums.
Seems the device is beyond repair like most affected Nexus 4 phones(some have luckily got fixed by themselves it seems and IMEI appeared again)
Guess I will have to sell it at a very low price. I am skeptical about buying even the Nexus 5 now should I run into another dreaded unfixable IMEI issue caused by Google's own update(just paranoia I guess)
If only someone comes up with some fix I guess that will help plenty of disappointed Nexus 4 owners.
liquidmetal88 said:
But this post specifically required the IMEI number to be exactly the SAME as mentioned otherwise it says the method wont work and it also seems to be T-Mobile blocked IMEI or something I don't think this fix is for my issue(correct me if I am wrong I am a noob lol)
My IMEI issue seems to linked to the Android 4.3 update which has broken something and this problem seems quite common on Nexus 4 as I came across many threads with people with exactly the same issue as mine. All the replies given usually say wipe cache and/or flash factory image sadly the problem remains.
I am really disappointed at my decision to buy the Nexus 4(my year long experience with the Galaxy Nexus was without issues) I never expected Google to release an update that breaks radios of many users(just google this problem many seem to have exactly the same symptoms as mine but the problem remained unresolved) and then remain silent despite many complaining on their product support forums.
Seems the device is beyond repair like most affected Nexus 4 phones(some have luckily got fixed by themselves it seems and IMEI appeared again)
Guess I will have to sell it at a very low price. I am skeptical about buying even the Nexus 5 now should I run into another dreaded unfixable IMEI issue caused by Google's own update(just paranoia I guess)
If only someone comes up with some fix I guess that will help plenty of disappointed Nexus 4 owners.
Click to expand...
Click to collapse
Your IMEI information should be on your box if you still have it. Now there has to be a tutorial out there somewhere to enter IMEI info for your phone. I know I found some stuff when trying to this to a Galaxy S3.... I would keep looking or contact Google for a RMA
Still no luck. Now flashing the just released Kitkat image, who knows it may work.
Edit: Still the same result.
Wonder why only 4.2.2 based roms boot but 4.3x and 4.4 based ones do not. I also don't get why baseband is detected in the bootloader mode but not within the OS.
And what is the process of this RMA thingy? Is it applicable for countries outside US? I am from Pakistan btw and got it from a local shop. Nexus 4 can't be bought from Play Store in my country
Any Luck yet?
liquidmetal88 said:
Still no luck. Now flashing the just released Kitkat image, who knows it may work.
Edit: Still the same result.
Wonder why only 4.2.2 based roms boot but 4.3x and 4.4 based ones do not. I also don't get why baseband is detected in the bootloader mode but not within the OS.
And what is the process of this RMA thingy? Is it applicable for countries outside US? I am from Pakistan btw and got it from a local shop. Nexus 4 can't be bought from Play Store in my country
Click to expand...
Click to collapse
Hi @[liquidmetal88] did you get any solution, exactly the same issue as yours. Please share if you have solved it, would be of great help
sambitshankar said:
Hi @[liquidmetal88] did you get any solution, exactly the same issue as yours. Please share if you have solved it, would be of great help
Click to expand...
Click to collapse
Am also facing this issue...only the 4.2.2 boots with no basebanc versiono no IMEI no. and doesn't detects any Sim card
Unlike Samsung phones, the imei cannot be re-injected into the phone's file system. People have had to return the phone to Google to have it fixed.
If you try to install a stock 4.3 or 4.4 ROM, the phone will not even boot to the desktop.

SAMSUNG NOTE 3 SM9005ZSUGOL1 PROBLEM AFTER LOLLIPOP UPDATE via KIES/ SMARTSWITCH

Hi Guys, Please I need your help.
I purchased a used Samsung Galaxy Note 3 N9005 (LTE Hongkong TGY Variant) in the Philippines.
Its is not rooted. Android version still at 4.3 when i bought it.
Tried to update it via OTA at 32% it will fail and then reboot. No changes will be made after the reboot.
I tried to update it via Samsung Kies / Smartswitch it worked.
From Android Jellybean 4.3 , I updated it to Android Lollipop 5 via Kies / Smartswitch.
But........
After the update If i will use or touch a certain application the phone will start to reboot by itself.
This happens very often like every 15 minutes.
The batter drains fast and the device heats up like crazy when i use the camera or i open up a game app then it will reboot automatically.
-Tried to do a soft and hard reset already by pressing volume up, menu key & power of button,
I cleared the cache and wiped user data already. But still nothing has changed.
-Tried to re-update the handset via USB on Smartswitch for Android 5 Lollipop but its still the same.
Here are my Note 3 handset info:
-Handset is from Hongkong(TGY)
-Baseband Version before the update: N9005XXUBMI5 (Android 4.3)
-Baseband Version after the update: N9005ZSUGOL1 (Android 5) ( i provided a screenshot)
-Is it safe to update the phone via Odin 3.10, then get a Firmware from Sammobile then flash it?
-The phone is from Hongkong (TGY), should i choose a Firmware from Hongkong? Or Is it ok to choose a Firmware from the Philippines? since i am here right now.
-Is it okay to downgrade from Android 5 to Android 4.3 or 4.4.2? ( Would you recommend it or no?, others are saying if i have upgraded my handset to the latest android update I cannot go back anymore to a lower Android version, if i do i might encounter problems or worst case i might brick the phone.
-If possible i do not want to root my handset, but if it is needed im willing to do it.
Please guys , i need your expertise on this. I really need your help badly to get my phone on its working state again.
Your reply and tutorials will be much appreciated.
Thank you and more power.
-Bero2x
Email: [email protected]

Need help getting GS5 back to stock and able to udpate

Alright....
So I've gotten a new phone, and I intend on selling my AT&T GS5. Only problem with it is that it will not update. I had rooted it awhile back, I can't remember how I did (something rain comes to mind when I to remember). Anyways, I've factory reset it, and tried to load a complete stock rom onto it. It still won't update.... When I download the OTA update, it will begin to install and then at 28% it will say "Update failed" and then reboot the phone. Any help?
Model: SAMSUNG-SM-G900A
Android version: 4.4.2
Kernel Version 3.4.0-2178781
Build Number: KOT49H.G900AUCU2ANG3
As of right now the device is fully stock (freshly factory reset), even says "official".
Let me know what you need, thanks.
Make sure that your Build Number and Baseband Version match (last 3 being NG3)
Here's a similar post that I got that information from:
http://forum.xda-developers.com/showthread.php?t=1914786

Issue when trying to upgrade to MM from Z00A-2.20.40.198

So, today I finally decided to get around to rooting/updating my Zenfone 2 after having it for about a year and a half. Get the rooting done, then I see a way to switch to the WW version instead of the one I'm on. Of course, since I'm stuck on Android 5.0 and the WW firmware goes up to MM, I immediately wanted to switch.
Tried following a bunch of different instructions on how to upgrade, and everything I've tried fails, even after unrooting my device. Most of the methods I've tried (manual install from recovery, system update after moving files onto phone, etc.) look like they start to work, then about halfway through the update I get a message on the screen that just says "error" with the bot laying down. Try to run the sideload with adb, get a message that "error: device not found" but figure it would be the same if I even did get it to work.
Anyone have any suggestions for what I can try, or am I overlooking something dumb? Thanks.
Oh, also, tried a few different editions of the WW firmware, all do the same thing, so it's not just one bad file.
daft_inquisitor said:
So, today I finally decided to get around to rooting/updating my Zenfone 2 after having it for about a year and a half. Get the rooting done, then I see a way to switch to the WW version instead of the one I'm on. Of course, since I'm stuck on Android 5.0 and the WW firmware goes up to MM, I immediately wanted to switch.
Tried following a bunch of different instructions on how to upgrade, and everything I've tried fails, even after unrooting my device. Most of the methods I've tried (manual install from recovery, system update after moving files onto phone, etc.) look like they start to work, then about halfway through the update I get a message on the screen that just says "error" with the bot laying down. Try to run the sideload with adb, get a message that "error: device not found" but figure it would be the same if I even did get it to work.
Anyone have any suggestions for what I can try, or am I overlooking something dumb? Thanks.
Oh, also, tried a few different editions of the WW firmware, all do the same thing, so it's not just one bad file.
Click to expand...
Click to collapse
After doing a Google search, I think you should first switch to WW version of Stock 5.0 than upgrade to Stock 6.0.1
You are in CN or TW , right?
Going by everything I've seen, I'd assume I'm on a CN version, going by what release I'm currently on. However, the firmware on my phone claims it's a WW version, so I'm not completely sure. Guessing it started out as a CN, then switched to a CERTAIN version of WW at some point, but doesn't seem to be in-line with the other WW updates, seeing how I'm visibly several iterations back from the most current WW release.
If it helps:
Model Number: ASUS_Z00AD
Baseband Version: 1603_5.0.68.9_0810,1546_7.0.29.0_0413
Kernel Version: 3.10.20-x86_64_moor-265437-g6ab076a
Build Number: LRX21v.WW-ASUS_Z00A-2.20.40.198_20160930_8756_user
daft_inquisitor said:
Going by everything I've seen, I'd assume I'm on a CN version, going by what release I'm currently on. However, the firmware on my phone claims it's a WW version, so I'm not completely sure. Guessing it started out as a CN, then switched to a CERTAIN version of WW at some point, but doesn't seem to be in-line with the other WW updates, seeing how I'm visibly several iterations back from the most current WW release.
If it helps:
Model Number: ASUS_Z00AD
Baseband Version: 1603_5.0.68.9_0810,1546_7.0.29.0_0413
Kernel Version: 3.10.20-x86_64_moor-265437-g6ab076a
Build Number: LRX21v.WW-ASUS_Z00A-2.20.40.198_20160930_8756_user
Click to expand...
Click to collapse
From your build number, you are already on the latest version of WW stock 5.0
In order to upgrade to Android 6.0.1 Download the firmware file(WW-4.21.40.223) from ASUS ( https://www.asus.com/Phone/ZenFone_2_ZE551ML/HelpDesk_Download/ )and rename it to MOFD_SDUPDATE.zip Put the MOFD_SDUPDATE.zip in internal storage as well as micro sd card (if you have one). Boot into recovery and it will update automatically.
Well, I'll be darned. That actually did it. Before, i was trying with the update file on EITHER my internal storage or my SD card, and that ended up just giving me an error message. Putting it on both at once caused it to go through properly. Thanks!

Stock ROM upgrade needed for G7-L01

Hi
I have a Huawei ascend G7 purchased in the UK from “Carphone warehouse” who seem to have been the only UK supplier of this model
The model is G7-L01
Android 4.4.4
EMUI 3.0
Custom version CUSTC432D001
My problem is a few banking apps I rely on have now stopped working as their updated versions insist on android 5 or higher
There has never been an OTA update for this phone since I purchased It
The only official ROMS listed on their website I can find seem to be for the G7-L11
I contacted Huawei support who confirmed that the particular model and custom version I have has no official updates newer than I am currently running and there no planned updates for it.
What are my options for getting this phone upgraded ? if possible I’d like to go with a stock ROM. could I use one from another region ?
Although I’ve had lots of phones in the past that I’ve put custom ROMS on I’ve always tried to keep this phone as stock because the same banking apps I rely on wouldn’t work properly on my last phone because they detected it had been rooted.
Searching these forums I’ve found a few guides but nothing for the particular custom version I have. I don’t know if this matters ? I don’t want to risk bricking it with an incompatible ROM
Thanks in advance for any advice you can offer
OK this is weird.
3+ years of no OTA updates. I enquire with Huawei and am told there are none and it is out of support.
Less than a week later and I'm being offered an OTA update.
Staggering coincidence ?
Only thing is it is reporting that I should download and do an SD card update instead of an OTA update as it is detecting that my device has been "modified".
I seem to recall I unlocked it a long time ago to try and root it but the root was unsuccessful.
Update is Android 5.1
EMUI 3.1
G7-L01C432B350CUSTC43D002
I just need to find it somewhere :-/
Harani said:
Hi
I have a Huawei ascend G7 purchased in the UK from “Carphone warehouse” who seem to have been the only UK supplier of this model
The model is G7-L01
Android 4.4.4
EMUI 3.0
Custom version CUSTC432D001
My problem is a few banking apps I rely on have now stopped working as their updated versions insist on android 5 or higher
There has never been an OTA update for this phone since I purchased It
The only official ROMS listed on their website I can find seem to be for the G7-L11
I contacted Huawei support who confirmed that the particular model and custom version I have has no official updates newer than I am currently running and there no planned updates for it.
What are my options for getting this phone upgraded ? if possible I’d like to go with a stock ROM. could I use one from another region ?
Although I’ve had lots of phones in the past that I’ve put custom ROMS on I’ve always tried to keep this phone as stock because the same banking apps I rely on wouldn’t work properly on my last phone because they detected it had been rooted.
Searching these forums I’ve found a few guides but nothing for the particular custom version I have. I don’t know if this matters ? I don’t want to risk bricking it with an incompatible ROM
Thanks in advance for any advice you can offer
Click to expand...
Click to collapse
Harani said:
3+ years of no OTA updates. I enquire with Huawei and am told there are none and it is out of support.
Less than a week later and I'm being offered an OTA update.
Staggering coincidence ?
Only thing is it is reporting that I should download and do an SD card update instead of an OTA update as it is detecting that my device has been "modified".
I seem to recall I unlocked it a long time ago to try and root it but the root was unsuccessful.
Update is Android 5.1
EMUI 3.1
G7-L01C432B350CUSTC43D002
I just need to find it somewhere :-/
Click to expand...
Click to collapse
Hi,
I also got this update notification on Saturday night. I have had this phone for 2 years now and never got a OTA notification until 2 days ago. The phone was working great, good battery life after 2 years and good performance. I use it mainly for youtube, whatsapp, some browsing, music, and calling.
Well, decided that updating to 5.1 would be a good idea but it hasnt. I cannot make any calls (phone disconnects and connects constantly to the mobile network, so every 2 seconds the "only emergency calls" message pops up and doesnt let me make calls). Same for receiving calls, when someone calls me it rings for 2 seconds and then it appears that call has been hung up, then it rings again, 2 seconds and hang up again... the constants connections and disconnections are drainning my battery (from 100% to 7% in 1.5 hours). Contacts didnt work and also messages either. As you go into one of them, it kicks you out of the list to the main screen. Of course this issue affects Data Mobile; I cannot use my phone internet unless its by Wifi.
Going into airplane mode stopped drainning problem plus contacts and messages are working now, but as soon as you turn airplane mode off you wont be able to go into contacts or messages/signal problems back.
Nothing of this happened when I had 4.4.4 version, so its clearly a software issue. Im gonna try doing a hard reset/factory defaults, since I could backup my contacts. And if this doesnt solve the problem, I think the best idea would be custom ROM/go back to 4.4.4.
This is a good phone, if good software is installed on it. It can last some more years.
@g7l01
Hi. I had exactly the same problems on my moms Ascend G7. She updated that OTA and mobile network got constantly shut off and on again. I solved it by doing a backup by Huawei HiSuite over PC. And then reflashed version 340 again manually (instructions at Huawei-Blog). Mobile networks are working again after flash but phone is still not working 100% correct. She gets randomly her mic muted in most calls, or recently her "back" button in navbar disappeared today...?
I'll either downgrade to 4.4.4 version or try lineage os soon.
MIKM.xda said:
@g7l01
Hi. I had exactly the same problems on my moms Ascend G7. She updated that OTA and mobile network got constantly shut off and on again. I solved it by doing a backup by Huawei HiSuite over PC. And then reflashed version 340 again manually (instructions at Huawei-Blog). Mobile networks are working again after flash but phone is still not working 100% correct. She gets randomly her mic muted in most calls, or recently her "back" button in navbar disappeared today...
I'll either downgrade to 4.4.4 version or try lineage os soon.
Click to expand...
Click to collapse
I solved it too! In my case I backed up my contacts to the micro SD card and did factory wipe/reset from the recovery menu (by restarting and pressing vol+ + power). I had all my data in my micro SD card so there wasnt any need to backup or anything. After doing this factory reset everything is working fine: phone signal, calls, contacts, messages, battery life, etc. I installed back the few apps I had and now everything fine, even performance is good! same as in 4.4.4. Im gonna stick with lollipop for a while, If I find any issue itll be time for a custom ROM or downgrade to 4.4.4
Cheers:good:
Hey you know how to to root g7l01

Categories

Resources