OK, so I have a big problem.
My screen suddendly stopped reponding on a large middle portion of it, so I'm sending it off for repair or exchange. I was rooted and running a custom rom (infected CM11), so I wanted to get it back to stock before.
But I followed every damn tutorial I could find in here, as well as in LG G2 and Optimus' forums, but it just won't work. R&D test tool keeps opening LG flash tool, and just refuses to flash the KDZ I have sideloaded.
The big issue might be this : I have lost my serial number when I flashed the KK leak, and I have sent my original sticker to LG because where I live, there was a 50€ off offer that required me to send it to them. I found on the internet a serial number, and it seems to be working.
Anyone has an idea as to what I might do ?
Mercvtio said:
OK, so I have a big problem.
My screen suddendly stopped reponding on a large middle portion of it, so I'm sending it off for repair or exchange. I was rooted and running a custom rom (infected CM11), so I wanted to get it back to stock before.
But I followed every damn tutorial I could find in here, as well as in LG G2 and Optimus' forums, but it just won't work. R&D test tool keeps opening LG flash tool, and just refuses to flash the KDZ I have sideloaded.
The big issue might be this : I have lost my serial number when I flashed the KK leak, and I have sent my original sticker to LG because where I live, there was a 50€ off offer that required me to send it to them. I found on the internet a serial number, and it seems to be working.
Anyone has an idea as to what I might do ?
Click to expand...
Click to collapse
I also lost my serial with the leaked 4.4.2, however I just flashed my backup and got it back. If you have a backup (which you really always should do), flash it and then follow the tutorial to return to stock again. If you dont have a backup I dont really know but you could try flash CM again.
extremex93 said:
I also lost my serial with the leaked 4.4.2, however I just flashed my backup and got it back. If you have a backup (which you really always should do), flash it and then follow the tutorial to return to stock again. If you dont have a backup I dont really know but you could try flash CM again.
Click to expand...
Click to collapse
I had a backup, but not from Stock Rom, and my serial with AOSP seems to be different... I'm in the process of flashing with an offline procedure, but it's hanging at 4%.
Related
Hi there guys searched around and relaly dont see a similiar problem I am having and any help would be appreciated. So I flashed the ics leak forthe unrooted v ersion of my att&t nitro that worked fine(its the exact same one as hono's but for unrooted roms) Anyways now that att official is coming out I wish to downgrade back to a stock rom so it will update to official. problem is during the unbrick method as its at some points in broken english(not a dis) just saying can get a bit confusing.
So I get to the step where the lg tool is updating and reboots phone and phone is back on and we are at about 93 percent that the problem occurs. the program(lg tool) says that there is a problem with the usb connection to the phone communicating please pull out usb remove battery and turn phone back on and hit restart ive tried that and still gets to same point to eventually program gives up and say exit.
ive reinstalled teh shttp server and all the tools redownloaded the linked kdz file etc...cant i just flash the official att rom since im not actually bricked. or is it better to dowgrade and redo it how i am trying to do now. Any hlep is appreciated seems as newer phones come out things get more confusing then easier
talrune said:
Hi there guys searched around and relaly dont see a similiar problem I am having and any help would be appreciated. So I flashed the ics leak forthe unrooted v ersion of my att&t nitro that worked fine(its the exact same one as hono's but for unrooted roms) Anyways now that att official is coming out I wish to downgrade back to a stock rom so it will update to official. problem is during the unbrick method as its at some points in broken english(not a dis) just saying can get a bit confusing.
So I get to the step where the lg tool is updating and reboots phone and phone is back on and we are at about 93 percent that the problem occurs. the program(lg tool) says that there is a problem with the usb connection to the phone communicating please pull out usb remove battery and turn phone back on and hit restart ive tried that and still gets to same point to eventually program gives up and say exit.
ive reinstalled teh shttp server and all the tools redownloaded the linked kdz file etc...cant i just flash the official att rom since im not actually bricked. or is it better to dowgrade and redo it how i am trying to do now. Any hlep is appreciated seems as newer phones come out things get more confusing then easier
Click to expand...
Click to collapse
i recommend you to use the original data cable that came alongwith the phone package and the usb ports at the back of the pc !
do this and try again !
yeah I am using the data cable that came with it and using the usb ports on back of pc. also i assume I cannot access the adb commands via the command line if phone isnt rooted correct? because i have t ried but thats a no go but as i said i assume thats because im not rooted.
You shouldn't have any reason to downgrade. You should just be able to use the LG tool to install the new ICS version when it "officially" comes out without any fuss.
If you want to install it right away (but slightly more difficult method), then follow the unbricking guide but use the new AT&T KDZ file instead of the one listed in the guide. And stop after it flashes that because you're done.
ok i assume the new att kdz is on this forum so i will look for it and give it a go i know the link hono had up yesterday for official attv20 was dead link.
oh another question when ya luanch the R&D test tool(UpTestEX_mod2_marwin.exe ) for select type do i leave it at cdma? and for phone mode leave it in diag? or should it be in emergency or cs_emergency that is not listed in the guide
ok got it to work i had to block the 127.0.0.1 lgmobile line in host and rebooted computer and pointed model dll on the R&D tool to the one in kd folder and then used the v20 official att ics and slet it stay on korean as country but chose english as language,thanks for hte help.
I've got this situation with my LGOG E975: a week ago i turned it on and after like 20 seconds after STOCK ROM was running , it rebooted.Then I also noticed the IMEI had gone. I wasn't rooted and the bootloader was locked. I tried everything from hard reset to flashing stock kdz. The only solution to the reboots is to flash teenybin and then a custom rom. Although I have no service and no IMEI. It's like having a 32 gigs ipod, almost useless. Also warranty was voided because the phone was disassembled.
Reading around the internet seems a EFS related issue but I have no idea how to fix it
Whats your advice? Hardware or software fault?
PS Also I noticed that ,with the stock rom, it doesn't scan the memory at startup, like it used to do.
Any help/idea would be appreciated!
Use ur EFS backup... U do have one?
Sent from my Optimus G using Tapatalk
Go to a gsm service and jtag it.
Sent from Omega pwd GT-I9505/smart phones,dumb people.
davevinci said:
Use ur EFS backup... U do have one?
Sent from my Optimus G using Tapatalk
Click to expand...
Click to collapse
nope:crying:
http://forum.xda-developers.com/showthread.php?t=2436647
http://forum.xda-developers.com/showthread.php?t=2510349
same problem here
Same problem here using stock rom and no root.
Phone reboot after a few seconds and no signal, no IMEI.
Is there a way to backup my data/photos in LG Recovery Mode ?
When the phone boots up I can see the files on pc but not enough time to save.
kimitza said:
Go to a gsm service and jtag it.
Sent from Omega pwd GT-I9505/smart phones,dumb people.
Click to expand...
Click to collapse
I have jtag but it's possible to restore imei for our device(only for htc devices).Only bootloader.
Search for someone with OCTOBUS BOX.
solution suggest
Rockguy40 said:
I've got this situation with my LGOG E975: a week ago i turned it on and after like 20 seconds after STOCK ROM was running , it rebooted.Then I also noticed the IMEI had gone. I wasn't rooted and the bootloader was locked. I tried everything from hard reset to flashing stock kdz. The only solution to the reboots is to flash teenybin and then a custom rom. Although I have no service and no IMEI. It's like having a 32 gigs ipod, almost useless. Also warranty was voided because the phone was disassembled.
Reading around the internet seems a EFS related issue but I have no idea how to fix it
Whats your advice? Hardware or software fault?
PS Also I noticed that ,with the stock rom, it doesn't scan the memory at startup, like it used to do.
Any help/idea would be appreciated!
Click to expand...
Click to collapse
do you know where's your phone from?? I meet a lot optimus G from Korea with this kind of problem when owners tried to flash it with an international ROM (Korean versions use different ROM but you can flash it with international ROM with some CAUTIONS, or you lost your IMEI) look for an able-to-pull-out antena on top of it, next to heaphone jack. if there is one, that's Korean version.
I know one way to recover IMEI for those phones, may be it works for your case:
1. Find out what is your phone REAL version (E97x or F180L,F180K,F180S ...) because it can be changed after you flash new ROM.
2. FInd s.o with the exact version of your phone and beg for the IMEI back up from their phones with this tool
mediafire.com/download/iy0rhx8yv7lkvlb/IMEI_Backup_Restore.zip (cant post links)
3. Restore your phone with that IMEI with the same tool, your phone will have new IMEI and .... service (I hope so)
remember to turn on "USB debugging". the phone will restart after done (may be twice)
Good luck!!
P/S: use at your own risks
bluesight said:
do you know where's your phone from?? I meet a lot optimus G from Korea with this kind of problem when owners tried to flash it with an international ROM (Korean versions use different ROM but you can flash it with international ROM with some CAUTIONS, or you lost your IMEI) look for an able-to-pull-out antena on top of it, next to heaphone jack. if there is one, that's Korean version.
I know one way to recover IMEI for those phones, may be it works for your case:
1. Find out what is your phone REAL version (E97x or F180L,F180K,F180S ...) because it can be changed after you flash new ROM.
2. FInd s.o with the exact version of your phone and beg for the IMEI back up from their phones with this tool
mediafire.com/download/iy0rhx8yv7lkvlb/IMEI_Backup_Restore.zip (cant post links)
3. Restore your phone with that IMEI with the same tool, your phone will have new IMEI and .... service (I hope so)
remember to turn on "USB debugging". the phone will restart after done (may be twice)
Good luck!!
P/S: use at your own risks
Click to expand...
Click to collapse
If it will work I will love you <3
Yeah I think that could be possible.. just make sure the phone EFS u will be copying from is not the same with your network u can't have same IMEI on same network at same time
Sent from my LG-E975 using Tapatalk
davevinci said:
Yeah I think that could be possible.. just make sure the phone EFS u will be copying from is not the same with your network u can't have same IMEI on same network at same time
Sent from my LG-E975 using Tapatalk
Click to expand...
Click to collapse
actually, you dont need IMEI to be the same, just the same kind of version (eg. International ~ E975, AT&T ~E973 ...). we call that "fake IMEI" in our place :lol:
This methods works 100% with korean version, and some of my friends confirm it works on international version, even the AT&T's or Canada's (E973,E970). the most important is to clarify your phone's version, if you did wrong version, you have to "fake baseband". and then everytime you flash a ROM you have to do the 2 fake
bluesight said:
actually, you dont need IMEI to be the same, just the same kind of version (eg. International ~ E975, AT&T ~E973 ...). we call that "fake IMEI" in our place :lol:
This methods works 100% with korean version, and some of my friends confirm it works on international version, even the AT&T's or Canada's (E973,E970). the most important is to clarify your phone's version, if you did wrong version, you have to "fake baseband". and then everytime you flash a ROM you have to do the 2 fake
Click to expand...
Click to collapse
does not work on my e975
NOOB ALERT: I am very new to this, but have done a bunch of searching and have come up empty. If I missed any threads that may have addressed this, my apologies.
Hello,
I recently tried flashing a custom rom on my e971 for the first time after 2 years of ownership and getting bored of stock rom. Rooted as described in the ROOT/BL-U/L/Install custom recovery thread for Canadian G's (zv9-zvb universal root), U/L BL with freegee and installed cwm (also through freegee). I then flashed pacman rom 4.4.4 for the e973, as it was my understanding that it would work properly. Rom flashed successfully and the phone worked for the most part (though there seemed to be some bugs with the rom).
One thing I noticed was that my imei was displaying as 0 in settings, which was a concern. After searching the forums for this problem, i found that most people with this problem couldn't connect to their operator, whereas I could connect fine (though my network speeds seemed slower than usual). No problem making calls, SMS, or using mobile data (MMS was hit and miss though).
I've since successfully restored my stock backup via cwm, tried restoring my efs partition via freegee (used freege to backup), re-flashed the JB radio for my model, but have had no luck getting my imei back (phone still works though).
The only other thing I can think of trying is the Unbrick guide using a kdz, however the kdz downloader app gives me an error when i input my model and serial. My other concern with this method would be ruining a phone that's currently working.
Can anyone recommend any solutions or offer any insight as to why this may have happened?
Thanks very much.
A couple of things... First off, to flash a KDZ, try using a flash tool 2014, it should work (worked on my F180S). Second, you could just leave your phone as is, unless you are planning to use it abroad (I am assuming you are in Canada). Unlike in other places in the world, e.g. Europe, nulled IMEI somehow works perfectly fine in Canada, which I know from my own experience with at least two different phones. Weird, but true. So, if you are only planning to use it locally, it shouldn't be much of a concern, really...
Thanks for the reply. Yes, in Canada, but unfortunately, I can no longer connect to Rogers at all. I'll take a look at the LG flash tool thread and see if I can figure it out. Still not sure where to find the kdz file though...
You mentioned you've experienced the IMEI problem. Do you happen to know if flashing the kdz will restore the IMEI (not sure if that's what you meant by "worked on my F180s"?
ff_29 said:
Still not sure where to find the kdz file though...
Click to expand...
Click to collapse
Take a look here: http://lg-phone-firmware.com/index.php?id_mod=20
The KDZ you need is listed under "Rogers".
You mentioned you've experienced the IMEI problem. Do you happen to know if flashing the kdz will restore the IMEI (not sure if that's what you meant by "worked on my F180s"?
Click to expand...
Click to collapse
I just meant that when I had to flash stock KDZ on my F180 (several times, for various reasons), Flash Tool 2014 worked perfectly for me. So, if you are having issues flashing KDZ by other methods, it's the best tool to use.
My IMEI problems were on totally different phones... I haven't encountered any IMEI issues with OG. Some people say that flashing KDZ does restore IMEI, others indicate that it doesn't. I can't say... If you used FreeGee in the past, you might have made an EFS backup. Restoring from it would be your best bet.
Thanks again. I did make a backup using freegee, but restoring through freegee doesn't seem to do anything (I get a message saying the process is complete, but still no IMEI).
I'll give the flash tool a try and report back.
Update: successfully flashed back to stock by kdz, but no change with the IMEI, and still not connecting to network. Still have the backup EFS partitions saved, but unless there's another way to restore them besides freegee, I think I'm SOL.
Update 2: After a day of showing no connection to the network, my phone decided to connect to rogers wireless today. Didn't change anything, and IMEI is still 0.
I hope you can fix it: http://forum.xda-developers.com/showpost.php?p=55471364&postcount=4
Good Luck :good:
---------- Post added at 11:56 PM ---------- Previous post was at 11:45 PM ----------
For more information and help you can check the B method this Post (has some pictures of help): http://customlgoptimusg.blogspot.com/2014/07/imei-copia-de-seguridad-restauracion-y.html
Thanks! Successfully restored IMEI
ff_29 said:
Thanks! Successfully restored IMEI
Click to expand...
Click to collapse
You're welcome and excellent. Greetings :good:
Edit: The Verizon repair assistant put my phone back to PHE build [100% battery].
Man I knew I shouldn't have tried to root after all this time. I'm not sure which firmware my phone was on [it was the 60% battery update], either PHE or PK1, as it displays in recovery right now. I tried to follow Lrileys modification of freeza's root guide, which neither of them specify a base firmware to go off of, lol.
Anyways, flashing the userdebug sprint firmware with ODIN 3.12.4 failed and my device softbricked. It boots into recovery and download mode.
I have tried factory reset, wiping cache partition, flashing an AP PH1 firmware, and repair through Verizon software/upgrade assistant.
The closest I've gotten to restoring it was with VUA, however when I go to the repair assistant page, it tells me to put phone in download mode [which I do] but the repair button stays greyed out.
Any help would be greatly appreciated.
Edit: The Verizon Upgrade Assistant wasn't starting, saying it was missing mfc90.dll. Well I downloaded the dll, dropped it in the folder, and was able to get UA to recognize phone. Repair assistant is downloading software right now, we'll see how it goes.
IF you would have read there is no root for the PHE.. you also could have checked this via phone settings before you rooted.
You can also use the verizon app to restore your firmware from even the most bricked of phones. Also in in this forum..(looks like you might have tried this?)
I wouldnt even bother at this point, go get your temp phone =]
ars0n said:
IF you would have read there is no root for the PHE.. you also could have checked this via phone settings before you rooted.
You can also use the verizon app to restore your firmware from even the most bricked of phones. Also in in this forum..(looks like you might have tried this?)
I wouldnt even bother at this point, go get your temp phone =]
Click to expand...
Click to collapse
Well the repair assistant seems to be working atm, so hopefully it goes through without any problems. Neither of these threads in the original post mentioned anything about incompatible firmware though [https://forum.xda-developers.com/verizon-note-7/how-to/root-vzw-note-7-t3448711 and https://forum.xda-developers.com/sprint-note-7/how-to/root-super-leaky-bros-sprint-galaxy-t3447202]. I suppose I should have known trying to use a method that dated.
You shouldn't be messing with this stuff if you don't even know how to see what version your on and read.
very helpful
jjayzx said:
You shouldn't be messing with this stuff if you don't even know how to see what version your on and read.
Click to expand...
Click to collapse
Thank you for the gratuitous reply. Despite your sour attitude I was able to return to PHE through VUA. I was running PK1 firmware, however, again, neither root method specified/recommended/listed a base or stock firmware to flash from [or even posted what they were running]. This place used to be helpful.
I rooted my a325m by patching the stock AP file with magisk, had to use FRP hijacker by hagard to be able to flash the patched file. I root uninstalled several apps for debloating. The phone worked fine for like a couple of weeks, and now, suddenly I find there's the no SIM indication, and in settings -> about phone it says IMEI: unknown, and in software information it says bandbase version: unknown.
The firmware version I used was exactly the same as when I bought it, A325MUBU2AUJ4, with the right csc (ARO in my case).
EDIT: after a couple reboots, the bandbase version now shows, but still no IMEI or SIM detected.
Can anyone help me? What happened? What can I do? Thanks in advance!
flash all the with odin the correct rom. the twrp unstable and more like shell and who knows what bugs have magisk. until why have a good recovery i would no root my phone reallly if you want to unisstall the software from samsung and google i would say to use the universal debload https://github.com/0x192/universal-android-debloater.
UPDATE: it got unknown baseband againI
I relocked the bootloader and now in download mode I have an option to "show barcodes" pressing the side button. The barcodes show the right IMEI and serial number. Maybe stuff wasn't erased, just inaccesible by the rom?
I was told by a technician to flash the original ROM (already did) then root again. Tried several versions but not an older bandbase because downgrade is forbidden by the bootloader, apparently, to no avail. Would try a newer baseband but i'm afraid it will not work and will be unable to go back to the origial baseband version.
Weird thing is, there is the EFS directory but no /data/nvram or /dev/nvram
Same happened to me.
I tried everything I could think of to get the IMEI back and couldn't.
It was still under warranty and I took it to Samsung.
Before taking it I unrooted it and locked it again.
They fixed it for me with no problem.
edukardo said:
Same happened to me.
I tried everything I could think of to get the IMEI back and couldn't.
It was still under warranty and I took it to Samsung.
Before taking it I unrooted it and locked it again.
They fixed it for me with no problem.
Click to expand...
Click to collapse
How did you root it?
as I understand, after rooting, warranty is void since it implies flashing a magisk patched boot image or AP tar. In my case I was indeed able to relock the bootloader and flash the original firmware but upon entering download mode, it shows "warranty void 0x01".
was it the same in your case?
Flashed original firmware, relocked phone, and then went to Samsung Office. I had no problem with it
edukardo said:
Flashed original firmware, relocked phone, and then went to Samsung Office. I had no problem with it
Click to expand...
Click to collapse
most likely the warranty vod bit was on (you can check it yoursef by entering odin mode) and they didn't notice
so you got it fixed for free?
did they mention what did the fix consist in? I heard they say they change the motherboard, which is a lie, they just write the nvram or efs with the right stuff
ah sos de argentina? lol where did you take it? to a samsung store? I'm from neuquen and got it at musimundo, but here's a samgung store too
myself i was thinking of waiting for an update which should be soon, lock bootloader, flash some official rom and pull off the cable so it gives an upgrade error and doesn't enter download mode, then take it to the store
Unroot before update and unlock
wipe the cache partition . then reset the phone using recovery mode . this is at you own risk .
did you fix it?
applesucksLmao said:
did you fix it?
Click to expand...
Click to collapse
nope, went to samsung, got rejected cause warranty bit on, no choice but take it to a service and I suppose they could do something with Chimera Tool, Z3X or something like that, which, as I've seen, claims to fix it in minutes (and the client gets charged handsomely, like 100 USD)
From Samsung I got the same bullsh*t I read in some threads: "this phone has been tampered with and it's a hardware problem, the board must be replaced"
For the technically savvy, I got a strange Magisk log which kind of looks like it may be the problem. It seems to try to "unlock"* some devices on bootup but gets "permission denied". One of them may be the nvram or something like that. I have an EFS directory but no NVRAM directory anywhere or /dev/nvram.
very strange, i guess we gotta not use magisk until its bug fixed.. i have seen other people have the same problem too, but anyways, i sent my phone to get probably JTagged for 54 us dollars, if they fix it well, great right, but if they dont i guess ill have to buy another motherboard from samsung or go to another city... and the best part is that while my phone is there, im using an S4 mini from 2013 with custom android 11 rom hehe
i saw that auh firmware causes empty imei in another thread and to flash aug, maybe you could try this? https://forum.xda-developers.com/t/has-anyone-successfully-rooted-this-a32-4g.4326193/post-85788523
applesucksLmao said:
very strange, i guess we gotta not use magisk until its bug fixed.. i have seen other people have the same problem too, but anyways, i sent my phone to get probably JTagged for 54 us dollars, if they fix it well, great right, but if they dont i guess ill have to buy another motherboard from samsung or go to another city... and the best part is that while my phone is there, im using an S4 mini from 2013 with custom android 11 rom hehe
Click to expand...
Click to collapse
or atleast use magisk with aug or even older firmware if you can... is your a32 A325M or A325F?
well, your firmware is A325MUB"U2"AUJ4 and that means u cant downgrade to older versions that have binary1 so maybe you could try using samsung's new version which was released past month
applesucksLmao said:
very strange, i guess we gotta not use magisk until its bug fixed.. i have seen other people have the same problem too, but anyways, i sent my phone to get probably JTagged for 54 us dollars, if they fix it well, great right, but if they dont i guess ill have to buy another motherboard from samsung or go to another city... and the best part is that while my phone is there, im using an S4 mini from 2013 with custom android 11 rom hehe
Click to expand...
Click to collapse
what's JTagged?
applesucksLmao said:
i saw that auh firmware causes empty imei in another thread and to flash aug, maybe you could try this? https://forum.xda-developers.com/t/has-anyone-successfully-rooted-this-a32-4g.4326193/post-85788523
Click to expand...
Click to collapse
I found it impossible to downgrade, download mode doesn't allow it. Couldn't find a tutorial to do it either.
applesucksLmao said:
well, your firmware is A325MUB"U2"AUJ4 and that means u cant downgrade to older versions that have binary1 so maybe you could try using samsung's new version which was released past month
Click to expand...
Click to collapse
I did, I tried all combinations rooting/unrooting with the new magisk 24.1 the new version, A325MUBS2AVA1
It's a 325m btw