Good afternoon everyone,
I have just bought a N4 with 4.2.2 installed on it. Right after turning it on for the first time it asked if I would like to install the new 4.3 version. Of course I said yes, and then ended up stucked in the X logo screen indefenitely. After this annoying situation I've been told that it could take up to 90 days to replace it on the store, so I used fastboot to return it to the stock 4.2.2 version, following the tutorial presented on this forum, the SO booted smoothly but after it my IMEI info is completely gone.
My concern lays primary on the warranty, and secondly, is there a noob tutorial on how to recover my original IMEI number with 4.2 ROM?
Thanks for your time and congratulations for the amazing forum.
After trying every single tutorial presented on this forum I gave up. Returned it back to the 4.2.2, unrooted, blocked the bootloader, upgraded to the 4.3 to generate the original error and called tech support. I will return the thing and get a new one.
I'm most certainly sure the problem lays on the baseband, something with the first 4.3 upgrade damaged files and the system isn't able to rebuild itself, and I couldn't find a way to do it manually.
Unfortunately I will avoid upgrading it to the 4.3 untill google says something about this bizarre bug that is making several people go nuts with android.
Have you tried reflashing the radio through fastboot? Maybe that will fix it.
Or maybe flash an older radio (eg. .27 or .33) and see if you get your baseband/IMEI back.
Sent from my Nexus 4 using xda app-developers app
mumaster20 said:
Have you tried reflashing the radio through fastboot? Maybe that will fix it.
Or maybe flash an older radio (eg. .27 or .33) and see if you get your baseband/IMEI back.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Both 27 and 33, not to mention 48 84, and every stock ROM I could find.
I have come to a conclusion that the problem do not lays on the radio I chose, because when I fastboot it shows me exactly which radio is installed. The problem seems to be that when I boot to android it fails loading the radio.
ScrewedImei said:
Both 27 and 33, not to mention 48 84, and every stock ROM I could find.
I have come to a conclusion that the problem do not lays on the radio I chose, because when I fastboot it shows me exactly which radio is installed. The problem seems to be that when I boot to android it fails loading the radio.
Click to expand...
Click to collapse
Have you tried reflashing a cimplete stock image from google, including userdata.img? Would be my last bet...
mumaster20 said:
Have you tried reflashing a cimplete stock image from google, including userdata.img? Would be my last bet...
Click to expand...
Click to collapse
Yeah, as it was a brand new mobile and I didn't have to worry about lost files, that was the very first thing I did.
Thanks for your persistence.
ScrewedImei said:
Yeah, as it was a brand new mobile and I didn't have to worry about lost files, that was the very first thing I did.
Thanks for your persistence.
Click to expand...
Click to collapse
Sorry that i could not help you, best bet now is to send it back to the store you bought it from, and hoping that you will get a replacement.
Goodluck!
mumaster20 said:
Sorry that i could not help you, best bet now is to send it back to the store you bought it from, and hoping that you will get a replacement.
Goodluck!
Click to expand...
Click to collapse
Just so I won't let you hanging, we did got a replacement, and it have the same Android version. Since then I didn't had the guts to update the Android.
Related
Hi All,
After flashing new ROM, my first time, the device couldn't connect to the network due to missing IMEI.
I don't know how and why it was deleted.
I have tryied to revert back to the Stock ROM and the same.
I have no support from my service provider because the device is hacked...
Any solutions?
same case happened to me
hi there, just the same thing happened to me when I newly bought samsung galaxy S2, I did many trials to find a solution and a lot of internet research but I could not find any, and a lot of new flashes.
At the end, I re- installed again a stock ROM and went to the service shop where it is still under guaranty, the guys there did not know how to fix it back although they have contacted the VENDER (samsung firm), and at the end they replace it with BRAND New one, I was lucky.
However, when you get a new one, you have to back up a directory called "efs" using root explorer application (have to buy it from market),while u must be rooted, they folder includes the imei data needed, and if you have it already back it up some time back, try to restore it and may be you will have your imei back, (i could not dare to try this after i got the replacement).
My cousin had this problem when he flashed lite'ning rom 6.1 on his new galaxy s 2. I flashed it back to stock XXKH3 and imei and baseband returned. Tried flashing back to 6.1 and again went off so back to stock and everything working fine.
Try restore IMEI technqiues (part of my reserches atthat time):
www(dot)youtube(dot)com(slash)watch?v=JqLK_2I-SBM
and
www(dot)youtube(dot)com(slash)watch?v=SluVXRxgvpc&feature=related
Good Luck
chipxtreme said:
My cousin had this problem when he flashed lite'ning rom 6.1 on his new galaxy s 2. I flashed it back to stock XXKH3 and imei and baseband returned. Tried flashing back to 6.1 and again went off so back to stock and everything working fine.
Click to expand...
Click to collapse
Can you please provide me a link for the stock XXKH3 ROM ?
Thanks in advance.
gentle10 said:
hi there, just the same thing happened to me when I newly bought samsung galaxy S2, I did many trials to find a solution and a lot of internet research but I could not find any, and a lot of new flashes.
At the end, I re- installed again a stock ROM and went to the service shop where it is still under guaranty, the guys there did not know how to fix it back although they have contacted the VENDER (samsung firm), and at the end they replace it with BRAND New one, I was lucky.
However, when you get a new one, you have to back up a directory called "efs" using root explorer application (have to buy it from market),while u must be rooted, they folder includes the imei data needed, and if you have it already back it up some time back, try to restore it and may be you will have your imei back, (i could not dare to try this after i got the replacement).
Click to expand...
Click to collapse
Using the root explorer method I'm not sure you will be able to restore the IMEI if you corrupt the /efs folder. Have a look at this!
Dude, read the f**king rules!
This is the wrong section, and you obviously haven't even tried to use the search button.
Sent from my GT-I9100 using XDA App
sagytb said:
Hi All,
After flashing new ROM, my first time, the device couldn't connect to the network due to missing IMEI.
I don't know how and why it was deleted.
I have tryied to revert back to the Stock ROM and the same.
I have no support from my service provider because the device is hacked...
Any solutions?
Click to expand...
Click to collapse
If your /efs directory got erased due to a flash.. Short answer: Without a backup you cannot restore it. A support request from samsung maybe, but unlikely due to the modified nature of the device.
bruflot said:
Dude, read the f**king rules!
This is the wrong section, and you obviously haven't even tried to use the search button.
Click to expand...
Click to collapse
How hard was that? A civil and informative response in same time it took you to swear at him..
bruflot said:
Dude, read the f**king rules!
This is the wrong section, and you obviously haven't even tried to use the search button.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
wow, how helpful you were, you should be "flashed" to CEO of XDA-developers and not remaining senior member.
you amazed us really...
bruflot said:
Dude, read the f**king rules!
This is the wrong section, and you obviously haven't even tried to use the search button.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
If only. It's funny how people lose their efs folder then come complaining and researching afterwards. All they have to do is simply back it up.
Return the phone to samsung under warranty and hope for the best OP.
Sent from my GT-I9100 using xda premium
for me, after installing Lite... Rom 6.1, i miss my IMEI, but after installing first rom(with three files!) of middle east, its back to me!!!
Lost IMEI
Are you sure the IMEI is realy lost? sometimes when the modem ****s up or compatibility issues.
I think maybe you should download only the modem which corasponds to the rom you are using, ie, use KH3 modem if KH3 ROM etc.
Give that a try my friend...dont forget to read the instructions in the other threads about the use of odin, I know this is not the appropriate place for this thread but there is no need to be agresive towards people who are learning the ropes
indeed try to flash back to stock rom and then root Backup your efs folder then try flashing a rom again.
i got this also that my Imei was gone flashed back to stock and it was back again.
Someone knows how to reproduce this?
I already have an efs backup but want to try to get a new sgs2 (yellow tint prob).
Cheers
Same here, have had Litening Rom 6.1 (for a couple of months already) and IMEI gone since this morning. The phone can't find the network anymore. It also has problems booting up sometimes. In some cases I need to pull the battery and boot it 5 times in a row before it boots past the first screen.
I guess I need to downgrade as well. (Or upgrade to the latest Litening version, but I'll first downgrade to the original firmware.)
on newer phones they have made it harder to fff up your imei the efs directory no longer exists and the data is saved in a private partition instead..
that is the way it is on my wifes galaxy s gio that i just setup..
just info for thought.
Good evening, I'm having issues with my nexus .
Days ago a friend of mine told me about the Xenon HD rom, and I decided to try it (Im a CM user).
Today, I made a backup with TWRP and flashed the rom, I tested it for a few hours and I did not liked it, so I decided to go back to the previous rom, so I restored the backup. I realized that all my applications were not installed, so then I decided to do a Factory Reset and restore the backup again, my apps were still missing.
So I decided and start from scratch, doing another factory reset and installing CM on it, I factory reset it and I realize that my phone did not have any signal!
Wifi and everything is working but iit is not receiving any signal!
Can anyone help? I even tested it with a simcard from another company and nothing!
Are there any settings that may have been moved? Some option? please help me!
Flash boot loader radio again
Nexus ⁴ paranoid android
If you are coming from a Android 4.3 stock rom to 4.2.2 then you need to flash this selecting the first option and flash it before flashing a Android 4.2.2 rom: http://forum.xda-developers.com/showthread.php?t=2147194
Sent from my Nexus 4 using Tapatalk 4
andyabc said:
If you are coming from a Android 4.3 stock rom to 4.2.2 then you need to flash this selecting the first option and flash it before flashing a Android 4.2.2 rom: http://forum.xda-developers.com/showthread.php?t=2147194
Click to expand...
Click to collapse
Hi, thanks for your answer, I just wanted to let you know that I went from an custom 4.2.2 (cm) to another 4.2.2 (xenonhd) and again to a 4.2.2 rom... Is there any way to check if my radio is ok?
I just flashed the radio&bootloader file and nothing
Im really lost here!
Please help me!
Do you recommend to make a system wipe and restore afactory image from the Nexus 4 Toolkit?
Please help me, I just returned it to stock using the toolkit and nothing...
Check your SIM card...remove it and reboot your phone then attach your SIM again and reboot...
Sent from my Nexus 4 using Tapatalk 4 Beta
vista_vz said:
Check your SIM card...remove it and reboot your phone then attach your SIM again and reboot...
Click to expand...
Click to collapse
Done and nothing!
Please help me out here!
donchele said:
Done and nothing!
Please help me out here!
Click to expand...
Click to collapse
Upgrade your phone to 4.3 and latest radio(using Google factory image) if problem persists call Google...
Sent from my Nexus 4 using Tapatalk 4 Beta
vista_vz said:
Upgrade your phone to 4.3 and latest radio(using Google factory image) if problem persists call Google...
Click to expand...
Click to collapse
Done! and nothing!
donchele said:
Done! and nothing!
Click to expand...
Click to collapse
Take soon card out. Then reboot . when phone is on , put Sim card in . if their is no , need to restart popup then its your Sim ,Sim tray, or sim reader
★Nexus⁴★PA3.94★Matr1x 10.5★LTE★
anyone else?
If you already flashed the factory image
Just let it be, insert your sim card and let the phone on for awhile
That happened to me with PA in 4.2.2 you got to wait a bit
Sent from the outside of the Eternity Gate at Holy Terra on a Paranoid Nexus
ofteno said:
If you already flashed the factory image
Just let it be, insert your sim card and let the phone on for awhile
That happened to me with PA in 4.2.2 you got to wait a bit
Click to expand...
Click to collapse
I dont think this will help that much, Its like waiting for it to fix itself, Thanks pal
At this point, my phone is fully stock and ready to go to the US for a claim process...
I just want to make sure everything is as stock as it should be, please take a look at the following and let me know:
Bootloader
Recovery
Anything else should be done? do you think that google will find out that the phone was rooted or something?
donchele said:
I dont think this will help that much, Its like waiting for it to fix itself, Thanks pal
At this point, my phone is fully stock and ready to go to the US for a claim process...
I just want to make sure everything is as stock as it should be, please take a look at the following and let me know:
Bootloader
Recovery
Anything else should be done? do you think that google will find out that the phone was rooted or something?
Click to expand...
Click to collapse
Glad yo help you out.
I know, it isn't logical but it works
Sent from the outside of the Eternity Gate at Holy Terra on a Paranoid Nexus
ofteno said:
Glad yo help you out.
I know, it isn't logical but it works
Sent from the outside of the Eternity Gate at Holy Terra on a Paranoid Nexus
Click to expand...
Click to collapse
I will try this tomorrow, please if anyone can take a look at the pictures and confirm that everythis is as stock as it shoul...
thanks
For 4.3 its good
Rooting i don't think so
About other think i really dont know
Sent from the outside of the Eternity Gate at Holy Terra on a Paranoid Nexus
Good day, I just wanted to let you guys know that the weirdest thing just happened to me.
I just came from my office and thought about going and turning on my phone, I did, and enabled airplane mode, (also turned on and off nfc) when I disabled it, my phone detected the network signal! I even received a sms, I also made a call! and thought, wow! it fixed itself up! I was literally dancing in my room and changing my simcard... (because I did all the above with a replacement chip that I have) and when I finally put my chip back, I made a call and it lost the signal again... It is now again without signal... I’m beginning to think this is a hardware problem...
Any update on this?
I've had the same problem for a few weeks now, the 3G/H signal just drops out, rebooting, airplane mode switching, returning to stock, different apn's, changing radios, replacing sims have all had no effect.
It's getting embarrassing now, seems to be such a common problem and yet no acknowledgement from Google about the issue which I believe to be deep in the settings/software and relating to the hardware in the original batch of Nexus phones.
I could arrange a return and get a replacement but I've read that even replacements have the same issue.
Apart from throwing the thing against the wall is there any other fixes out there?
If it helps I'm on 02 UK pay monthly, surrounded by cell towers, the phone is rooted and running stock 4.3
Just checking it now and I have H and 4 full blue bars - Ok update twitter.. nope, ok go to the play store..nope...
Fricken piece of Junk
Hey guys, I've been having A LOT of issues with the new updates. First the 4.4 and then the 4.4.2 that didn't solve a thing. I've installed them via OTA but after that i've already did:
- factory reset
- installed via fastboot 4.3, then updated via OTA to 4.4.2
- installed via fastboot 4.4, then updated via OTA to 4.4.2
- factory reset AGAIN - installed via fastboot 4.4.2.
I don't know what do to anymore! I can't take pictures because nexus just turns off the moment i take one. I can't install facebook, twitter or instagram and another random apps... And btw, is it normal that in 10 minutes the battery charges to 1% to 50%? i think i never noticed that...
BUT WHAT DO I DO? PLEASE HELP!
UPDATE:
This problem is solved, it was the battery. I've changed the screen recently and it needed a new battery too. Thanks to everyone that tried to help me
just flash the factory images for 4.4.2 via fastboot
Sent from my Nexus 4 using XDA Premium 4 mobile app
saifulh2304 said:
just flash the factory images for 4.4.2 via fastboot
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
how do I do that? sorry but I'm a little noob.
maznex said:
how do I do that? sorry but I'm a little noob.
Click to expand...
Click to collapse
follow the guide here: http://rirozizo.blogspot.com/2013/11/guide-how-to-flash-factory-images-from.html
maznex said:
how do I do that? sorry but I'm a little noob.
Click to expand...
Click to collapse
If you don't know how to use fastboot, use the Wugfresh toolkit, makes life very easy. It has the drivers, downloads recoveries, root files and the factory images. Really is easy with that.
Riro Zizo said:
follow the guide here: rirozizo.blogspot.com/2013/11/guide-how-to-flash-factory-images-from.html
Click to expand...
Click to collapse
maritimesbob said:
If you don't know how to use fastboot, use the Wugfresh toolkit, makes life very easy. It has the drivers, downloads recoveries, root files and the factory images. Really is easy with that.
Click to expand...
Click to collapse
Guys, like I said I used fastboot to install 4.4.2, it still didn't work. I followed this guide googlenexusforum.com/forum/nexus-4-roms/4046-guide-flash-stock-option-using-android-sdk-tools.html
Hey, guys, I haven't updated it to 4.4.2 yet cause my phone is rooted so I'm asking is it worth to go through all the process again? And if yes can anyone state the new features? ☺ thx a lot!
Sent from my Nexus 4 using XDA Premium 4 mobile app
Looks like a hardware issue to me. Probably your battery is faulty... Could explain the shut downs and trying to use the camera usually drains more battery so again that could it be. Could you be more specific about the other errors that you get?
Sent from my Nexus 4 using xda app-developers app
evdrmr said:
Looks like a hardware issue to me. Probably your battery is faulty... Could explain the shut downs and trying to use the camera usually drains more battery so again that could it be. Could you be more specific about the other errors that you get?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Hardware? It started to happen only when I updated the first time via OTA to 4.4.
I open the camera, I try to take a picture, the flash goes on and then the phone goes off. Sometimes I can turn it on and the battery it's the same, sometimes I can't turn it on without connecting to the charger because it goes off when I go to insert the PIN.
Well, after I understood that the problem was that apps, when I turned the WI-FI on, the phone immediately turned off after that I unistalled that apps and when I turned the WI-FI on I could go on Chrome and Play Store, and installed some apps (like n7 player) and everything was OK.
One time I installed Twitter and I used it for a bit and everything seemed fine but then I installed Facebook and the phone crashed again so I unistalled both. Same with Instagram.
I don't know how much more specific I can be... I really need help :s
it's not hardware. anyone who had this phone running pre 4.3 aosp will remember the camera issues and the clicking noises that went along with the focusing and then the reboots. the battery charging is also a widely experienced issue as well as going from a full charge to 50% in a few minutes. I'm getting the camera bug again on 4.4.2 hope a .3 build pops up soon to deal with it. I'm also 100% stock no root
aaronrw said:
it's not hardware. anyone who had this phone running pre 4.3 aosp will remember the camera issues and the clicking noises that went along with the focusing and then the reboots. the battery charging is also a widely experienced issue as well as going from a full charge to 50% in a few minutes. I'm getting the camera bug again on 4.4.2 hope a .3 build pops up soon to deal with it. I'm also 100% stock no root
Click to expand...
Click to collapse
exactly this is happening but on 4.4.2
BTW, when I'm charging the phone, none of this problems happens. I can install and use all apps and use the camera.
maznex said:
exactly this is happening but on 4.4.2
BTW, when I'm charging the phone, none of this problems happens. I can install and use all apps and use the camera.
Click to expand...
Click to collapse
if I were having all those issues I'd try installing the Factory Image again or maybe try 4.4.1 and then use the OTA to update. BUT there is definitely some bugs in the latest KK release
aaronrw said:
if I were having all those issues I'd try installing the Factory Image again or maybe try 4.4.1 and then use the OTA to update. BUT there is definitely some bugs in the latest KK release
Click to expand...
Click to collapse
I did all of that as I refered in the beggining... I will try to install 4.4.1 though, that was the only thing I didn't do, but I doubt it's gonna work, because installing 4.4 and 4.4.2 didn't solve a thing
sorry about the double post but there isn't the factory image for 4.4.1 here... https://developers.google.com/android/nexus/images#occamkot49h .
I tried to flash 4.4.2 following this guide http://rirozizo.blogspot.pt/2013/11/guide-how-to-flash-factory-images-from.html and when I turned it on I had no signal.. what does that mean? I guess it didn't worked..
maznex said:
sorry about the double post but there isn't the factory image for 4.4.1 here... https://developers.google.com/android/nexus/images#occamkot49h .
I tried to flash 4.4.1 following this guide http://rirozizo.blogspot.pt/2013/11/guide-how-to-flash-factory-images-from.html and when I turned it on I had no signal.. what does that mean? I guess it didn't worked..
Click to expand...
Click to collapse
The latest factory images are 4.4.2, that's why you didn't see 4.4.1 on Google's server. When you flash factory images, your radio will also be updated. When you flash a custom ROM, your radio doesn't get updated, that's why you had problem with cell signal. Or flash the appropriate radio for the ROM.
taodan said:
The latest factory images are 4.4.2, that's why you didn't see 4.4.1 on Google's server. When you flash factory images, your radio will also be updated. When you flash a custom ROM, your radio doesn't get updated, that's why you had problem with cell signal. Or flash the appropriate radio for the ROM.
Click to expand...
Click to collapse
The phone asked me to insert PIN and then I had cell signal again.. Should I flash 4.4.2 again flashing the radio too? Because I have the feeling that this will not solve my problem. Like I said in the beggining I followed another guide to flash my phone, and in that guide it said to flash radio and "bootloader-mako..." (not sure what that is) and the cell signal problem still happened and then I couldnt install Facebook or Twitter or had my location on or using the camera without the phone turning off or rebooting...
EDIT: The phone just turned off when updating Google apps, so yeah... Didn't work :s
maznex said:
The phone asked me to insert PIN and then I had cell signal again.. Should I flash 4.4.2 again flashing the radio too? Because I have the feeling that this will not solve my problem. Like I said in the beggining I followed another guide to flash my phone, and in that guide it said to flash radio and "bootloader-mako..." (not sure what that is) and the cell signal problem still happened and then I couldnt install Facebook or Twitter or had my location on or using the camera without the phone turning off or rebooting...
EDIT: The phone just turned off when updating Google apps, so yeah... Didn't work :s
Click to expand...
Click to collapse
You said that when a PIN is input, the phone has signal again which means it's not a radio issue. Did you set up a PIN in the security section in your phone?
taodan said:
You said that when a PIN is input, the phone has signal again which means it's not a radio issue. Did you set up a PIN in the security section in your phone?
Click to expand...
Click to collapse
No this is just something that started to happen along with the other problems... Sometimes the phone loses signal for no reason and goes to the PIN input screen.
maznex said:
No this is just something that started to happen along with the other problems... Sometimes the phone loses signal for no reason and goes to the PIN input screen.
Click to expand...
Click to collapse
Which radio are you using? It should be .98 if you are on KitKat 4.4.2. You can flash a standalone radio zip file in recovery.
taodan said:
Which radio are you using? It should be .98 if you are on KitKat 4.4.2. You can flash a standalone radio zip file in recovery.
Click to expand...
Click to collapse
I don't know I will check later because now I'm not home. But when can I find that zip file and if I flash that it will only solve the cell signal thing right?
I bought my nexus 4 about a month ago and now i decided to root it and flash a custom rom. I flashed the omni rom nightly dated 9th feb.afterthat it started giving me problems as in the area just above the navigation bar did not respond to touch inpuuts. So fearing that i spoiled my new phone i went back to my stock rom and unrooted it. but now the problem still persists and the options to go to my menu work but when i open an app like google play or any other for that matter the play/pause options do not work. So i really need some help as to what i should do next and how i will be able to solve my problem. Thank you. Hoping that someone will be able to help me.
You've flashed the factory image and you still have the problem?
Sent from my Nexus 5
jd1639 said:
You've flashed the factory image and you still have the problem?
Sent from my Nexus 5
Click to expand...
Click to collapse
yes i did flash the factory image and i still have the problem. I even went to the lengths of flashing the factory image for 4.3 and it still doesnt work.
Thank you.
I suggest you use the Wugfresh Nexus Root Toolkit.
steci86 said:
I suggest you use the Wugfresh Nexus Root Toolkit.
Click to expand...
Click to collapse
Thanks so much for your help but I used the wigs fresh toolkit itself. Now m not sure of its a software or a hardware problem. And if it will get solved by giving it to the service centre for a software update.
rishikelkar said:
Thanks so much for your help but I used the wigs fresh toolkit itself. Now m not sure of its a software or a hardware problem. And if it will get solved by giving it to the service centre for a software update.
Click to expand...
Click to collapse
If it's not working after correct factory image flash it's probably a hardware issue.
redhunter22 said:
If it's not working after correct factory image flash it's probably a hardware issue.
Click to expand...
Click to collapse
Buy then wouldn't the whole screen not work , wouldn't my keypad also not work ?
I've tried this two times and both I had the same result. I downgraded back to 4.2.2 with the D80110g_00.kdz for the tmobile g2. Then I rerooted it and added philz touch recovery. I flashed with the kitkat baseband in the cloudystock 1.1 fourm, then the rom with the patched 801 kernel after. Everything boot's up ok, and the phone works. But when I turn off the screen and back on its all grayed out with yellow lines. I have the reboot the phone for the screen to show up again. Can someone tell me what I am doing wrong?
Do the same process except do not use 80110g. Find the 80110c kdz.
Sent from my LG-D801 using xda app-developers app
Thank you, that fixed the problem. Another question I have is that when I flash the baseband, do I have to keep reflashing it when I move to another kitkat rom?
JPrinceStar said:
Thank you, that fixed the problem. Another question I have is that when I flash the baseband, do I have to keep reflashing it when I move to another kitkat rom?
Click to expand...
Click to collapse
baseband stays the same when flashing other roms. Pretty sure the rom zips don't touch baseband unless specified otherwise. Glad it worked for ya btw
Sent from my LG-D801 using xda app-developers app
Problem came back, turn off screen and its grayed out when back on unless reboot. I dont have this problem when I root 4.2.2. Am I flashing the files in the wrong order, or am I missing something.
JPrinceStar said:
Problem came back, turn off screen and its grayed out when back on unless reboot. I dont have this problem when I root 4.2.2. Am I flashing the files in the wrong order, or am I missing something.
Click to expand...
Click to collapse
Doesn't seem like you are flashing in wrong order. If you boot up and everything runs...it's probably just due to the fact this isn't an official release and there may be bugs
Sent from my LG-D801 using xda app-developers app
v2.2v said:
Doesn't seem like you are flashing in wrong order. If you boot up and everything runs...it's probably just due to the fact this isn't an official release and there may be bugs
Sent from my LG-D801 using xda app-developers app
Click to expand...
Click to collapse
I have the exact issue...here is a picture of what it looks like, maybe this will help so that people can see what we talking about
batmanonastick said:
I have the exact issue...here is a picture of what it looks like, maybe this will help so that people can see what we talking about
Click to expand...
Click to collapse
same issue here. Cannot run any stock KK roms at all. I've flashed so many times and have had to return to stock. I wish this problem could be identified.
Did anyone out there figure this out?
I'm having the same problem on my device, tried several stock ROMs but nothing works even when using different basebands.
I have this problem as well and no, you're not doing anything wrong. Devs have absolutely no idea why this is happening. It seems that this is only happening with users that bought the phone and have the G build pre-installed. People that bought the phone earlier with the C build don't have this problem.
I gave up and just flashed the official KK TMO ROM with root installed. I lost my recovery but hopefully devs can get recovery on stock KK. If anything, I can always KDZ back to 4.2.2 and re-install the recovery if I want to go back to AOSP ROM's.
FWIW, I bought the G2 a week ago. When did you get yours?
I think you hit the nail on the head with G build comment. I got my phone about a month ago from TMO and it came pre-installed. I wonder if something in the actual hardware is ever so slightly different with the latest G2s...
I flashed with the C build and it didn't fix it also, guess I'll stay on 4.2.2 till there is a official kitkat root.
Anyone around in this thread with the line problem willing to test a kernel?
mackster248 said:
I have this problem as well and no, you're not doing anything wrong. Devs have absolutely no idea why this is happening. It seems that this is only happening with users that bought the phone and have the G build pre-installed. People that bought the phone earlier with the C build don't have this problem.
I gave up and just flashed the official KK TMO ROM with root installed. I lost my recovery but hopefully devs can get recovery on stock KK. If anything, I can always KDZ back to 4.2.2 and re-install the recovery if I want to go back to AOSP ROM's.
FWIW, I bought the G2 a week ago. When did you get yours?
Click to expand...
Click to collapse
How do you find if you have G or C build? I thought all tmobile g2's are c build. I am getting mine tomorrow, hope it is shipped with JB rom - if so, i think it will be better to stay. After reading a bit, i heard many say tot method is working fine as explained here.
Which rom (xd thread?) are you using? Does wifi calling work?
sam298 said:
How do you find if you have G or C build? I thought all tmobile g2's are c build. I am getting mine tomorrow, hope it is shipped with JB rom - if so, i think it will be better to stay. After reading a bit, i heard many say tot method is working fine as explained here.
Which rom (xd thread?) are you using? Does wifi calling work?
Click to expand...
Click to collapse
If you go to software you can see the build, it either ends with C or D. Most likely D since you'll just be getting it. And it will be JB not KK. There's a new AutoRec file that gives KK users recovery, but since you'll be getting the D version, you'll most likely have the white line glitch issue. There's a way around it, just PM me for further questions and I'll help ya out.
v2.2v said:
Do the same process except do not use 80110g. Find the 80110c kdz.
Sent from my LG-D801 using xda app-developers app
Click to expand...
Click to collapse
KennyJive said:
same issue here. Cannot run any stock KK roms at all. I've flashed so many times and have had to return to stock. I wish this problem could be identified.
Click to expand...
Click to collapse
JPrinceStar said:
Did anyone out there figure this out?
Click to expand...
Click to collapse
SeVIIn said:
I'm having the same problem on my device, tried several stock ROMs but nothing works even when using different basebands.
Click to expand...
Click to collapse
i really want to root but this is making me nervous. Only things i want to change is the camera mod and sound mod really.
dr87 said:
Anyone around in this thread with the line problem willing to test a kernel?
Click to expand...
Click to collapse
I am in the same boat as most these people.. bought my phone a week ago, i am rooting as i type. Will probably have the issue and completely willing to test a kernel. Should i flash your rom as well first?
---------- Post added at 11:59 AM ---------- Previous post was at 11:56 AM ----------
mackster248 said:
If you go to software you can see the build, it either ends with C or D. Most likely D since you'll just be getting it. And it will be JB not KK. There's a new AutoRec file that gives KK users recovery, but since you'll be getting the D version, you'll most likely have the white line glitch issue. There's a way around it, just PM me for further questions and I'll help ya out.
Click to expand...
Click to collapse
Hmmm.. so i have a completely stock g2 non rooted (working on rooting right now actually) but when i go into settings, my build number ends with an 'A' ?? not c, d or g.... what does this mean? Man, rooting seemed so much easier on my HTC or samsung phones! No complaints though, i love this phone
frettfreak said:
i really want to root but this is making me nervous. Only things i want to change is the camera mod and sound mod really.
I am in the same boat as most these people.. bought my phone a week ago, i am rooting as i type. Will probably have the issue and completely willing to test a kernel. Should i flash your rom as well first?
---------- Post added at 11:59 AM ---------- Previous post was at 11:56 AM ----------
Hmmm.. so i have a completely stock g2 non rooted (working on rooting right now actually) but when i go into settings, my build number ends with an 'A' ?? not c, d or g.... what does this mean? Man, rooting seemed so much easier on my HTC or samsung phones! No complaints though, i love this phone
Click to expand...
Click to collapse
It does seem confusing, but I promise you that it's a bit more painless than you think. I'm assuming your phone did indeed ship with TMO KitKat? Then in that case, once you're done rooting, all you have to do is install the AutoRec apk and that's it! Let me know if you need a link for AutoRec.
mackster248 said:
It does seem confusing, but I promise you that it's a bit more painless than you think. I'm assuming your phone did indeed ship with TMO KitKat? Then in that case, once you're done rooting, all you have to do is install the AutoRec apk and that's it! Let me know if you need a link for AutoRec.
Click to expand...
Click to collapse
yeah it did ship with KK. pretty sure i have seen the thread regarding the autorec app. But will let you know! Thanks!
mackster248 said:
It does seem confusing, but I promise you that it's a bit more painless than you think. I'm assuming your phone did indeed ship with TMO KitKat? Then in that case, once you're done rooting, all you have to do is install the AutoRec apk and that's it! Let me know if you need a link for AutoRec.
Click to expand...
Click to collapse
Mackster I'm on 4.2.2 which is rooted, is there anyway I could use a custom kitkat rom without getting the white lines? I dont want to keep downgrading everytime it happens.