Related
I'm currently running a SynergyROM r64 nand and my lte doesn't seem to work. I checked my IMEI in phone info -> stats and it's the same as before I flashed CM10 beta 9/3 build. Could flashing CM10 have corrupted my IMEI? Before I flashed, I entered su reboot nvbackup from andriod terminal to backup my IMEI so idk if that's the problem or not. I also have a Qualcomm backup, but I shouldn't need to restore it if I already have my IMEI saved correct? Or should I just Odin back to stock?
Shibby87 said:
I'm currently running a SynergyROM r64 nand and my lte doesn't seem to work. I checked my IMEI in phone info -> stats and it's the same as before I flashed CM10 beta 9/3 build. Could flashing CM10 have corrupted my IMEI? Before I flashed, I entered su reboot nvbackup from andriod terminal to backup my IMEI so idk if that's the problem or not. I also have a Qualcomm backup, but I shouldn't need to restore it if I already have my IMEI saved correct? Or should I just Odin back to stock?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1867442
Will take care of IMEI and/or ERI problems you may have.
guyd said:
http://forum.xda-developers.com/showthread.php?t=1867442
Will take care of IMEI and/or ERI problems you may have.
Click to expand...
Click to collapse
If his IMEI is intact, then there's no reason to restore an IMEI backup or anything. Toying with it could have negative consequences. Since it seems like phone info isn't working, flash to stock through ODIN. You can make a backup prior if you want. If that doesn't work, reprovision your phone via *2767*3855# . That will wipe your entire internal SD so back up anything you want.
Zalithian said:
If his IMEI is intact, then there's no reason to restore an IMEI backup or anything. Toying with it could have negative consequences. Since it seems like phone info isn't working, flash to stock through ODIN. You can make a backup prior if you want. If that doesn't work, reprovision your phone via *2767*3855# . That will wipe your entire internal SD so back up anything you want.
Click to expand...
Click to collapse
Thank you sir! Reprovisioning did the trick. Would it be possible to use this with SynergyROM or CleanRom, or is this method strictly stock? I got my 4G lte back by dialing *2767*3885# from root66 stock touch wiz.
Sent from my SCH-I535 using xda app-developers app
You shouldn't have to do it again unless you have problems. Just flashing a Rom will not do it unless something goes wrong. It should work on clean because that is a stock Rom, I have not tested it though nor have I read where anyone else has. Good luck!
Sent from my SCH-I535 using xda premium
Shibby87 said:
Thank you sir! Reprovisioning did the trick. Would it be possible to use this with SynergyROM or CleanRom, or is this method strictly stock? I got my 4G lte back by dialing *2767*3885# from root66 stock touch wiz.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
It depends. Some of the ROMS cut out stuff that makes the number not work properly. I only know it works for sure on stock, and is unlikely to work on CM, but maybe other TW roms will allow it to work also.
Sometimes you have to put a # dialing command into your contact list and it will work from there.
I recently performed a NV rebuild on my S3 because my GPS was not working and now I am unable to send any texts or make any calls. I m currently rooted and running Eclipse v5.0 build 3 ROM with the 3.4.45 Cyanogenmod kernel. Can anyone please help me with this?
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
I have the same problem
ZacHcaZ said:
I recently performed a NV rebuild on my S3 because my GPS was not working and now I am unable to send any texts or make any calls. I m currently rooted and running Eclipse v5.0 build 3 ROM with the 3.4.45 Cyanogenmod kernel. Can anyone please help me with this?
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
I did the same thing trying to get a better GPS fix. I also cannot make calls or receive texts. I hope some experts out there can help us slove this problem.
dtfarm said:
I did the same thing trying to get a better GPS fix. I also cannot make calls or receive texts. I hope some experts out there can help us slove this problem.
Click to expand...
Click to collapse
I'm confused why people are doing this. Have you tried going back to stock with Odin?
Also can somebody link the post where someone recommends to do this so I can read it?
Sent from my SCH-I535 using Tapatalk 2
Recommendation
BadUsername said:
I'm confused why people are doing this. Have you tried going back to stock with Odin?
Also can somebody link the post where someone recommends to do this so I can read it?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I have gone back to stock with ODIN and it still have the same problem. Refer to the link below under NOTES. It offers a GPS fix. Any help would be greatly appreciated.
http://forum.xda-developers.com/showthread.php?t=2370850
did u lose your imei ?
sent from a violated Vzw Galaxy s3
No voice calls
rsswga said:
did u lose your imei ?
sent from a violated Vzw Galaxy s3
Click to expand...
Click to collapse
MY IMEI is intact. I have 4G LTE data and WIFI. I only cannot make or receive calls. The phone acts like its making a call but never connects. The phone eventually hangs up after about 30 seconds.
dtfarm said:
I have gone back to stock with ODIN and it still have the same problem. Refer to the link below under NOTES. It offers a GPS fix. Any help would be greatly appreciated.
http://forum.xda-developers.com/showthread.php?t=2370850
Click to expand...
Click to collapse
My guess is when you NV restored you messed something up that's responsible for your data that isn't imei related.
I really have no idea where to even start with that, and I saw no reference to NV restore in that post anywhere. If you made an IMEI backup before all this happened, restoring that might restore all of your NV data restoring your text and data calls. I would guess you could theoretically fix it with qpst, but I really have no idea.
You can try to odin back to an ics rom and reprovision the phone, that could rewrite your NV data.
Sent from my SCH-I535 using Tapatalk 2
same problem
Im having the exact same problem. Reflashed it to stock and took it in to VZW to see if they could replace or fix, but they don't have any authority to do that and if I send it in, the techs might determine that I changed the "root", thus voiding my warranty.
My current work-around fix is to use my google voice number and Groove IP to make calls
BadUsername said:
My guess is when you NV restored you messed something up that's responsible for your data that isn't imei related.
I really have no idea where to even start with that, and I saw no reference to NV restore in that post anywhere. If you made an IMEI backup before all this happened, restoring that might restore all of your NV data restoring your text and data calls. I would guess you could theoretically fix it with qpst, but I really have no idea.
You can try to odin back to an ics rom and reprovision the phone, that could rewrite your NV data.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
My guess is that is what happened to my cell. Called Verizon, and they were unable to do anything to fix this and sent me a replacement S3 that I just received today. I unrooted and reset my flash counter yesterday on my old S3 so I can send it back.
Unless you made a backup of your nvram before you did the NV rebuild, my guess is you are probably going to have to replace your S3 like I just had did to since it made and screwed up some network settings on your cell.
I did the same thing to my wife's phone last night (oops) now she can't make any calls today.
anyone find a fix yet?
edit: 1st - I know the info now appears to have been removed from that post. I actually did the rebuild from memory as i read it a week or so ago.
Everything worked, IMEI intact except she couldn't make calls.
So right after it was found i did a nvbackup on both our phones.
decided to try the restore options and see if that helped.
sure enough downloaded term, su - reboot nvrestore and the phone sat at the sgs3 boot screen.
hmmm
forced it into recovery, wiped, reloaded. everything is working fine now.
The reason i did this is because her GPS locking was poor. and i had previously did the tighten the screws trick and thought it couldn't be that.
well after everything was working, GPS still didn't. I gave all the screws a turn and wouldn't you know - GPS locked right away.. *sigh*
sooo the lessons for others is
1st don't do the nvrebuild
2nd for GPS locking issues try your screws 1st
3rd if you are in this mess AND you did an nvbackup early on. nvrestore should get you going again
As soon as I start having GPS issues I call Verizon and give them hell because I have already replaced 2 phones because of GPS issues. Luckily this last phone has been spot on. I never would reset the nv.
Sent from my SCH-I535 using xda premium
I had the same problem just hooked it back up to my computer and found some software online and restored my nv now works fine!
Sent from my SCH-I535 using xda app-developers app
rayraycarter4 said:
I had the same problem just hooked it back up to my computer and found some software online and restored my nv now works fine!
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
What software did you use?
(I already replaced my phone because I didn't backup my nvram, but just curious)
No problem
Sent from my C6602 using xda app-developers app
I tried flashing cm one day and after hours of not being able to connect to the network I realized my imei was deleted. I restored it flashed back to paranoid 4.3 but have been having connection issues. Next to no service in my house and places I had 4g I have 1 x or searching for service. I noticed my prl is 0, imeisv is 0 and also my eri set to 0. I flashed back to stock and everything was fine but as I excepted ota to upgrade firmware the mentioned above went back to zero. I believe I didn't do something correctly it's more than bad reception. Any ideas?
Sent from my iPhone using Tapatalk
So, to clarify, on stock you have normal connectivity and the imei and meid is present in settings>about phone>status?
Sent from my SCH-I535 using Tapatalk 2
FC127 said:
So, to clarify, on stock you have normal connectivity and the imei and meid is present in settings>about phone>status?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Sorry about that, the phone had normal connectivity when I went back to stock and in settings-about-status all values were present
Imei hex dex
Imeisv
Prl
I'm completely lost I have a feeling I didn't do something correctly when I restored imei. Either in qpst or In hidden menus on the phone. I just tried going back to out the box without any firmware updates and I have the same connectivity issues
Sent from my iPhone using Tapatalk
Restore from a previous TWRP or CWM backup. I had the same problem before and restoring a backup was the only thing that worked. I even tried manually restoring the IMEI through QPST without any progress.
I'll give it a try thanks
Sent from my iPhone using Tapatalk
For whatever reason I can't access my back ups. In twrp I go to restore and folder is empty. My back ups are on my sd card which I've used several times before. I tried going into install then go directly to that folder but nothing happens just goes into sub cater gory. I'm so lost this seems to not be a common issue so there's. Of a lot of info out there
Sent from my iPhone using Tapatalk
I recently got through this issue too. After fixing my IMEI, ERI and MEID my phone would recognize a network but could not make calls. What I had to do was ODIN back to a stock unrooted ROM then complete a factory reset from INSIDE THE ROM, not from recovery. Reflashing a nandroid from recovery wouldn't work and simply flashing to a stock ROM wouldn't work, it was only after doing a factory reset using the ROM (Menu->Settings->Backup and Reset->Factory data reset) that I got connectivity back fully. This might work with a Touchwiz rooted rom but I don't know for sure. Obviously after that you'll need to re-root and re-flash whatever ROM you want or restor from a previous saved backup. ABSOLUTELY backup your IMEI information, if I knew what I was doing the first time and knew how simple it was and how little time it takes I would have done that first and avoided all this hassle!!
postal302 said:
I recently got through this issue too. After fixing my IMEI, ERI and MEID my phone would recognize a network but could not make calls. What I had to do was ODIN back to a stock unrooted ROM then complete a factory reset from INSIDE THE ROM, not from recovery. Reflashing a nandroid from recovery wouldn't work and simply flashing to a stock ROM wouldn't work, it was only after doing a factory reset using the ROM (Menu->Settings->Backup and Reset->Factory data reset) that I got connectivity back fully. This might work with a Touchwiz rooted rom but I don't know for sure. Obviously after that you'll need to re-root and re-flash whatever ROM you want or restor from a previous saved backup. ABSOLUTELY backup your IMEI information, if I knew what I was doing the first time and knew how simple it was and how little time it takes I would have done that first and avoided all this hassle!!
Click to expand...
Click to collapse
This seemed to of worked. This is the one issue I've had with this phone that seemed I wasn't going to be able to fix. It also doesn't seem to be a common issue so there isn't a lot of discussion about it. Thanks again I though I'd be stuck with my iphone5
Sent from my iPhone using Tapatalk
Maduro78 said:
This seemed to of worked. This is the one issue I've had with this phone that seemed I wasn't going to be able to fix. It also doesn't seem to be a common issue so there isn't a lot of discussion about it. Thanks again I though I'd be stuck with my iphone5
Click to expand...
Click to collapse
I'm glad this worked for you. I was banging my head against the wall for a few days trying to figure this out. If you haven't already done it, back up your IMEI using the link in my last post. It literally takes only minutes and saves TONS of hassle.
postal302 said:
I'm glad this worked for you. I was banging my head against the wall for a few days trying to figure this out. If you haven't already done it, back up your IMEI using the link in my last post. It literally takes only minutes and saves TONS of hassle.
Click to expand...
Click to collapse
where did you find a stock rom..EVERY link I have tried, seems to be down or no longer valid.
thanks
postal302 said:
I'm glad this worked for you. I was banging my head against the wall for a few days trying to figure this out. If you haven't already done it, back up your IMEI using the link in my last post. It literally takes only minutes and saves TONS of hassle.
Click to expand...
Click to collapse
I was at the point I was gonna chalk this phone up as a loss. It doesn't seem like a common issue so there isn't a whole lot of help out there for this issue. I'm so glad I decided to check back in this thread. I can now afford to buy better presents for Xmas lol. You saved the day.
Sent from my iPhone using Tapatalk
DeathCry said:
where did you find a stock rom..EVERY link I have tried, seems to be down or no longer valid.
thanks
Click to expand...
Click to collapse
I noticed the same thing. I've been using the same file for the last couple years without fail pm if you want it. Goo manager also has it.
Sent from my iPhone using Tapatalk
OP you MUST backup your IMEI. If you don't you are going to have a serious headache getting it back.
Sent from my SCH-I535 using Tapatalk
DeathCry said:
where did you find a stock rom..EVERY link I have tried, seems to be down or no longer valid.
thanks
Click to expand...
Click to collapse
Sorry I fell off the map on this, life's been busy lately!! All the links to the files I used are infact down. Were you able to get your hands on a stock rom? For all the repair work I used CleanROM, but I only flashed a stock ROM to do the factory reset. I'm actually wondering if doing a factory reset from the menu in CleanROM will do the same thing. Do your research so you don't brick your phone.
I went and looked on my computer and saw the file I used for a stock rom was a Root66 (pre-rooted) ROM.
For what it's worth, here's the links I used:
I started with this return to stock guide. Step three led me to this guide to flash a stock rom using ODIN. Step five of that guide had the links to the stock ROMs and stock pre-rooted ROMs. I was having trouble downloading a 4.1.2 ROM so I used a 4.1.1 instead.
If you still need a stock ROM let me know and I'll find a way to get the one I used to you.
postal302 said:
Sorry I fell off the map on this, life's been busy lately!! All the links to the files I used are infact down. Were you able to get your hands on a stock rom? For all the repair work I used CleanROM, but I only flashed a stock ROM to do the factory reset. I'm actually wondering if doing a factory reset from the menu in CleanROM will do the same thing. Do your research so you don't brick your phone.
I went and looked on my computer and saw the file I used for a stock rom was a Root66 (pre-rooted) ROM.
For what it's worth, here's the links I used:
I started with this return to stock guide. Step three led me to this guide to flash a stock rom using ODIN. Step five of that guide had the links to the stock ROMs and stock pre-rooted ROMs. I was having trouble downloading a 4.1.2 ROM so I used a 4.1.1 instead.
If you still need a stock ROM let me know and I'll find a way to get the one I used to you.
Click to expand...
Click to collapse
Hey, no worries.. Life is much more important. Thanks for responding. I did get fixed.
I went back to a 4.1.2 ROM, couldn't fix everything. Eventually got back to 4.0.4. Got everything straightened out. And backed that _ _ _ _ up.
Was than able to upgrade to 4.4.2 aosp ROM, of course without needing the backup. But I have it.
Thanks again....as is usually the case, not reading enough up front did me in. Let that be a lesson kids.
Sent from my Nexus 10 using Tapatalk 4
does anyone have a link to the 4.0.4 stock rom? all of the links i have found are no longer up.
Thanks
Ok, so I probably know the answer to this already :crying:
Brief story - stock rooted ROM with custom kernel. Made backup with TWRP. Flashed stock boot,img and system.img in fastboot, flashed downloaded update from 4.4 -> 4.4.2 in recovery. Wiped cache and dalvik - started but recovery locked up. Had to hold power to reboot phone. Booted fine but no network, no IMEI, no baseband.
And no I don't have and EFS backup
I take it the phone is now buggered.
Is there anything I can do to fix this??
Appreciate anything that might help this.
Cheesy Wotsit said:
Ok, so I probably know the answer to this already :crying:
Brief story - stock rooted ROM with custom kernel. Made backup with TWRP. Flashed stock boot,img and system.img in fastboot, flashed downloaded update from 4.4 -> 4.4.2 in recovery. Wiped cache and dalvik - started but recovery locked up. Had to hold power to reboot phone. Booted fine but no network, no IMEI, no baseband.
And no I don't have and EFS backup
I take it the phone is now buggered.
Is there anything I can do to fix this??
Appreciate anything that might help this.
Click to expand...
Click to collapse
The same thing happened to me. Flash the latest version of TWRP, wipe your cache again, and your phone will be back to normal.
not true for all you may end up having to RMA I had my efs backup it still didn't fix it sorry to be the bearer of bad news but they make it sound like bringing it back is 100% but in some cases that's not true
Sent from my Nexus 4 using xda app-developers app
ddloco said:
not true for all you may end up having to RMA I had my efs backup it still didn't fix it sorry to be the bearer of bad news but they make it sound like bringing it back is 100% but in some cases that's not true
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
In his case, if he just does what I said to do he'll be fine. He didn't lose his EFS, he rebooted in the middle of a cache wipe and his partitions got messed up. Updating TWRP and wiping the cache again will set everything straight. This is a fairly common issue with older versions of TWRP.
_MetalHead_ said:
In his case, if he just does what I said to do he'll be fine. He didn't lose his EFS, he rebooted in the middle of a cache wipe and his partitions got messed up. Updating TWRP and wiping the cache again will set everything straight. This is a fairly common issue with older versions of TWRP.
Click to expand...
Click to collapse
I'm just saying the same thing happens to me and nothing that's suggested fixed it that's why I say its not 100% me and another guy both had the same problem and the only way was to RMA I also had my efs but even after doing everything from going back to stock updateubg twrp and reflashing my esf backup my phone would not correct its self so I'm not saying that this method doesn't work for some people but for me and another used it was a no go
So why are you guys still using twrp if it is causing issues?
Just use cwm instead!
Sent from my Nexus 5 using Tapatalk
Elisha said:
So why are you guys still using twrp if it is causing issues?
Just use cwm instead!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
because the majority dont have any problems.
and people, take precautionary measures and back up your efs partition, its the first thing i did as soon as i had a custom recovery. it takes 2 seconds. and store it somewhere OTHER then your phones internal storage, like on a comp or dropbox
TheAtheistOtaku said:
because the majority dont have any problems.
and people, take precautionary measures and back up your efs partition, its the first thing i did as soon as i had a custom recovery. it takes 2 seconds. and store it somewhere OTHER then your phones internal storage, like on a comp or dropbox
Click to expand...
Click to collapse
This is not an EFS issues. Simple matter of twrp messing up partitions.
Sent from my Nexus 5 using Tapatalk
Elisha said:
This is not an EFS issues. Simple matter of twrp messing up partitions.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
i know, still doesnt hurt to be caution though
ddloco said:
I'm just saying the same thing happens to me and nothing that's suggested fixed it that's why I say its not 100% me and another guy both had the same problem and the only way was to RMA I also had my efs but even after doing everything from going back to stock updateubg twrp and reflashing my esf backup my phone would not correct its self so I'm not saying that this method doesn't work for some people but for me and another used it was a no go
Click to expand...
Click to collapse
Yeah but did it happen to you the way it happened to OP? So far every single person that I have come across who was in this boat due to a bad cache wipe in TWRP was able to fix it by updating TWRP and re-wiping the cache. It's a well known issue.
_MetalHead_ said:
Yeah but did it happen to you the way it happened to OP? So far every single person that I have come across who was in this boat due to a bad cache wipe in TWRP was able to fix it by updating TWRP and re-wiping the cache. It's a well known issue.
Click to expand...
Click to collapse
Thanks for the help guys. Got it up and running again more by accident than anything. Seems like MetalHead was correct, the partition was fine but just not readable. Unfortunately in order to get up and running again I flashed all the stock images in flasboot and did a full factory reset in the stock recovery which fixed the problem. Sounds like I could have done without the full wipe after all but at least it's all fixed now.
As for backing up the EFS, lesson learned. I had the 1st official TWRP on the phone which had no option for EFS backup like the current one. Guess what I'll be doing right now??
Anyway, happy man again and thanks to all that replied :good:
I must apologize for saying its not 100% but the truth is I had the exact same thing happen and no stock or fast boot cache fixed it I'm living proof that it works for the masses but under rare circumstances this just doesn't solve it oh man how I wish this would've fixed mine I been using a inspire 4g its killing me I feel like I jumped out of a beemer and landed in a pinto lol
Sent from my Nexus 4 using xda app-developers app
Glad that the OP got the issue resolved !
on a side note , can anyone tell me what is the safest version of TWRP there ? i.e without this cache wipse issue ( taking too long to wipe ? )
ddloco said:
I must apologize for saying its not 100% but the truth is I had the exact same thing happen and no stock or fast boot cache fixed it I'm living proof that it works for the masses but under rare circumstances this just doesn't solve it oh man how I wish this would've fixed mine I been using a inspire 4g its killing me I feel like I jumped out of a beemer and landed in a pinto lol
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Thats a bummer man. What kind of phone are you using now?
Lowresolution said:
Glad that the OP got the issue resolved !
on a side note , can anyone tell me what is the safest version of TWRP there ? i.e without this cache wipse issue ( taking too long to wipe ? )
Click to expand...
Click to collapse
I believe 2.6.3.4 is the latest version. That's the one I'm on, works just fine.
Sent from my Nexus 5 using XDA Premium 4 mobile app
_MetalHead_ said:
Thats a bummer man. What kind of phone are you using now?
I believe 2.6.3.4 is the latest version. That's the one I'm on, works just fine.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Got it , thanks mate Just upgraded my version of TWRP .
the nexus 4 is my phone I gave to my wife now that its hers I'm lucky to pick it up just to hop on xda but when its her Facebook time she hurrie up and kick me off lol the phone I'm using is an HTC inspire 4g it sucks
Sent from my Nexus 4 using xda app-developers app
So my friend just rooted his phone and decided to uninstall LG IMS (without knowing what it was). He was using Titanium Backup. He had made a backup for it and all. Now the phone is having issues and even though he tried restoring the app, it won't budge. Any trick to this? He has a locked bootloader and no recovery with TWRP or CWM installed (of which I told him to do before he deleted anything). Any way this can be fixed? If he does a factory reset from the settings menu, will it restore everything (including the IMS file) and be fine, or since it has been rooted, will that not do?
Or I guess is there any way to install a custom rom onto it so that that issue will be resolved since possibly the IMS will not be needed?
Is it possible to install autorec and have it restore to stock ROM?
Andrewoidd said:
So my friend just rooted his phone and decided to uninstall LG IMS (without knowing what it was). He was using Titanium Backup. He had made a backup for it and all. Now the phone is having issues and even though he tried restoring the app, it won't budge. Any trick to this? He has a locked bootloader and no recovery with TWRP or CWM installed (of which I told him to do before he deleted anything). Any way this can be fixed? If he does a factory reset from the settings menu, will it restore everything (including the IMS file) and be fine, or since it has been rooted, will that not do?
Or I guess is there any way to install a custom rom onto it so that that issue will be resolved since possibly the IMS will not be needed?
Is it possible to install autorec and have it restore to stock ROM?
Click to expand...
Click to collapse
Why not follow my back to stock guide?
Sent from my iPhone using Tapatalk
hyelton said:
Why not follow my back to stock guide?
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Thanks. I found it and I'll show it to him. Hopefully we can get it to work.
Only question I have for you is -- do we need to have an unlocked bootloader?
Andrewoidd said:
Thanks. I found it and I'll show it to him. Hopefully we can get it to work.
Only question I have for you is -- do we need to have an unlocked bootloader?
Click to expand...
Click to collapse
No, it's all factory stock
Sent from my iPhone using Tapatalk
hyelton said:
No, it's all factory stock
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Thanks. At least now I won't have to go through the headache of unlocking his bootloader.
We'll follow your guide and hopefully get it back and working.