fixed brick still need help - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

i bricked my galaxy s3 i747 and using enewman17s method I downloaded an mk5 file from another of his posts, and with his post here http://forum.xda-developers.com/showthread.php?t=2658486 it gives me multiple folders and a boot.img. Now correct me if I'm wrong, the phone is actually up and running now, but the main problems i have found with it is that it will not read a sim card, it says the IMEI is unknown and the sound is not working at all and videos dont want to play. Do i need the files in those folders and the .img file to make everything work properly? If so Im not sure how to flash those on to my phone. The phone was originally bricked by rooting then trying to update, and the phone would only load to the at&t logo then freeze. any other information can be provided and all is welcomed thank you.

It sounds like your IMEI/EFS was corrupted or wiped.
http://forum.xda-developers.com/showthread.php?t=1852255
This thread is what I have saved for dealing with such an issue, there maybe something newer take a look around the forum. Assuming there is nothing Restore Plan D of that thread is what I assume you will want to look at.

tried the methods, none worked. went to plan D and the link explaining how to do so no longer exists. is there any way i can atleast get audio output and videos to work?

Can you tell us the bootloader version on your phone?

Related

IMEI and Internal storage problem

I did the stupid mistake of flashing to a custom rom without backing up. Nowhere in custom rom instructions says to backup your /efs folder.
Now in "About device" Baseband version is "Unknown" IMEI is "Unknown". I've searched everywhere for a fix and nothing. I tried the following:
Flash stock rom
Format /data and /cache
On keypad, dial *#7284# ....But i dont get the "Qualcomm USB settings" option so i cant try IMEI repair tools
I tried flashing different kernels and different custom roms
Apart from the IMEI problem, the Device cant access the 16GB internal memory. The stock rom flashes with no error, but when i go to
settings > storage: under "Device memory" its full with only 182MB used by some apps. I thought the memory could be bad, but after flashing
Perseus kernel and swapping external sd card for internal memory I can use the 16GB as external memory. I cant find a fix for that either.
INTERNAL MEMORY UPDATE: it seems that internal memory is mounting read only. Still trying to find a fix
Im currently on "T889UVALK8_T889TMBALK8_TMB" rom with Perseus kernel and using "11extsd2internalsd_gs3_fat32" to swap internal to external memory.
Side note: I bought the phone from a friend 2 days ago. Its the Tmobile version and I used cellunlocker to unlock to use it with AT&T. That worked, until I started messing with ROMS. No warranty available. I am desperately looking on how to fix this since i have no spare phone. Any help is highly appreciated and thank you for your time
Eri version: Unknown???
I am having a similiar issue on t889 7105. ERI version "not available". Everything else is okay. Searched everywhere . . .not addressed. Which is strange.
this sucks
gregniel said:
I am having a similiar issue on t889 7105. ERI version "not available". Everything else is okay. Searched everywhere . . .not addressed. Which is strange.
Click to expand...
Click to collapse
I cant believe this issue hasn't been addressed
Unfortunately sir their just isnt much that can be done for you. If you read about imei loss without a backup its just about incurable. Sorry.
And the remedy for imei restoration without a backup is hit and miss at best as to whether or not it actually will restore your number. Your best bet is to use the search function and try and experiment with different ways of fixing it. Its not like there is much more damage that can be done anyways. You already screwed the pooch and basically have a functional brick.
No one is going to post a step by step guide for you though if thats what youre waiting on. This is a complicated fix and most members wont devote the time to walking you through it
And to the member that said he searched and found no Information. Well thats just not true. Ive read tons of threads and posts about it and know about SEVERAL backup and restore methods.
crap
janjannsen99 said:
Unfortunately sir their just isnt much that can be done for you. If you read about imei loss without a backup its just about incurable. Sorry.
And the remedy for imei restoration without a backup is hit and miss at best as to whether or not it actually will restore your number. Your best bet is to use the search function and try and experiment with different ways of fixing it. Its not like there is much more damage that can be done anyways. You already screwed the pooch and basically have a functional brick.
No one is going to post a step by step guide for you though if thats what youre waiting on. This is a complicated fix and most members wont devote the time to walking you through it
And to the member that said he searched and found no Information. Well thats just not true. Ive read tons of threads and posts about it and know about SEVERAL backup and restore methods.
Click to expand...
Click to collapse
Thank you for confirming my fear, I was on denial. Im getting a new one on friday. How much do you think I can sell this one for, obviously as a tablet?
Developers need to take more responsibility around here with their threads. A simple "I'm not at fault" is sub par in my opinion. Users popping up with IMEI issues are becoming more a common thing. Didn't somebody make an app to back up your efs partition? Why is there not a link to said app in every ROM and kernel thread? This stuff blows my mind.
As there is a rampant influx of "noobs" watching YouTube videos about rooting their devices (most of which for the first time) with links to ROM threads, their needs to be an influx of responsibility taken by those who cook ROMs and feed them to the general public. The issues with the IMEIs being lost is not a small one. Your device is pretty much done for without a backup. Keep reading, keep trying, but since you had no idea that losing the ability to use your device's radios was even a possibility, not your fault.
Good luck. And sorry. You should have seen a link at the very top of the thread you downloaded your ROM from ... and this whole thing would have been avoided. Here is the link, which is always shared too late and after the fact. App is called andromizer forum.xda-developers.com/showthread.php?t=2080009
This kind of thing shouldn't still be happening.
http://forum.xda-developers.com/showthread.php?t=2080009
[DEV][APP][Andromizer] Android Customizing Tools (Note2 Specific Features Added)
Here's a link to one I used to backup mine. You have to pay to unlock the backup feature. It gives you way more piece of mind flashing
saseekutz said:
http://forum.xda-developers.com/showthread.php?t=2080009
[DEV][APP][Andromizer] Android Customizing Tools (Note2 Specific Features Added)
Here's a link to one I used to backup mine. You have to pay to unlock the backup feature. It gives you way more piece of mind flashing
Click to expand...
Click to collapse
No you don't. The version I got here on xda, also same exact link I posted right before you -_- , allowed me to back up my efs partition with no issues
adam2508 said:
Thank you for confirming my fear, I was on denial. Im getting a new one on friday. How much do you think I can sell this one for, obviously as a tablet?
Click to expand...
Click to collapse
Well all is not lost. There have been reports of people restoring imei successfully.
Try and app called andromizer. If I remember right it had an efs backup and restore. Its an app
Second. Go to the tmobile galaxy s3 forum and find their thread about lost imei numbers. Use those tools and the method to try to write back your imei number. Ill try and find it
Edit. Heres the link. Try using those tools and those methods. THAT is the only method I have heard about to work AT ALL. So try it out
http://forum.xda-developers.com/showthread.php?t=1801997
cobraboy85 said:
No you don't. The version I got here on xda, also same exact link I posted right before you -_- , allowed me to back up my efs partition with no issues
Click to expand...
Click to collapse
Damn.. Lol I was told wrong, my bad on the repost dude
Agreed
cobraboy85 said:
Developers need to take more responsibility around here with their threads. A simple "I'm not at fault" is sub par in my opinion. Users popping up with IMEI issues are becoming more a common thing. Didn't somebody make an app to back up your efs partition? Why is there not a link to said app in every ROM and kernel thread? This stuff blows my mind.
As there is a rampant influx of "noobs" watching YouTube videos about rooting their devices (most of which for the first time) with links to ROM threads, their needs to be an influx of responsibility taken by those who cook ROMs and feed them to the general public. The issues with the IMEIs being lost is not a small one. Your device is pretty much done for without a backup. Keep reading, keep trying, but since you had no idea that losing the ability to use your device's radios was even a possibility, not your fault.
Good luck. And sorry. You should have seen a link at the very top of the thread you downloaded your ROM from ... and this whole thing would have been avoided. Here is the link, which is always shared too late and after the fact. App is called andromizer forum.xda-developers.com/showthread.php?t=2080009
This kind of thing shouldn't still be happening.
Click to expand...
Click to collapse
What would happen if i copied the /efs directory from the new one to this one?
Start a thread titled
Who has restored imei successfully
janjannsen99 said:
Start a thread titled
Who has restored imei successfully
Click to expand...
Click to collapse
The issue being you can't restore it without a backup.
---------- Post added at 01:57 PM ---------- Previous post was at 01:56 PM ----------
adam2508 said:
What would happen if i copied the /efs directory from the new one to this one?
Click to expand...
Click to collapse
Never done it. If you have a new one, just make a backup of the new one and don't mess with it. Now you know to make a backup
Curious
I would like to prevent myself from making this mistake in the future. Are you talking about the same type of back up you would do in TWRP or CWM? Like a nandroid? I've never heard about the backup your talking about, but I have been seeing a lot of people talking about losing their IMEI number and it sounds like really bad news.
Ill give it a try
janjannsen99 said:
Well all is not lost. There have been reports of people restoring imei successfully.
Try and app called andromizer. If I remember right it had an efs backup and restore. Its an app
Second. Go to the tmobile galaxy s3 forum and find their thread about lost imei numbers. Use those tools and the method to try to write back your imei number. Ill try and find it
Edit. Heres the link. Try using those tools and those methods. THAT is the only method I have heard about to work AT ALL. So try it out
http://forum.xda-developers.com/showthread.php?t=1801997
Click to expand...
Click to collapse
I will try this tomorrow, i dont think that there is no fix at all. There is a fix for everything, just not yet discovered. Even though i will be getting a new phone, i still want to dedicate some time on fixing this one. If I find a fix, I might help someone else.
advice
Corrupt0387 said:
I would like to prevent myself from making this mistake in the future. Are you talking about the same type of back up you would do in TWRP or CWM? Like a nandroid? I've never heard about the backup your talking about, but I have been seeing a lot of people talking about losing their IMEI number and it sounds like really bad news.
Click to expand...
Click to collapse
dude, make sure you have a back up of everything. Especially of the /efs directory. I read a few posts about people having this problem even after restoring back from CWM. I will get into conclusions that CWM does not back up the /efs directory. Anyone wants to correct me or add to this?
A little clarification
adam2508 said:
dude, make sure you have a back up of everything. Especially of the /efs directory. I read a few posts about people having this problem even after restoring back from CWM. I will get into conclusions that CWM does not back up the /efs directory. Anyone wants to correct me or add to this?
Click to expand...
Click to collapse
Any chance you could tell me where to find this? If ever lost and you have the back up, how would you restore it?
I'll be really honest
Corrupt0387 said:
Any chance you could tell me where to find this? If ever lost and you have the back up, how would you restore it?
Click to expand...
Click to collapse
After what happened to me I haven't messed with other roms. Andromizer can be found here http://forum.xda-developers.com/showthread.php?t=2080009 to make a backup of your /efs. I have also used Nandroid, which you can just download from the "play store". Nandroid apparently does make a backup of everything including /efs and bootloader. As to how to restore from those backups I would like to never find out if it actually works. I have flashed the perseus kernel with clockworkmod recovery and also rooted which allows me to overclock to 1800MHz and im very happy with it. I dont have the urge to flash any roms that "promise" any speed improvements. I have also got rid of the bloatware with titanium backup pro. And of course i made backup with it too just in case i removed something i did not suppose to. All backups are in my external SD card and on dropbox. Call me paranoid but after what ive gone through i call it being safe.
adam2508 said:
I did the stupid mistake of flashing to a custom rom without backing up. Nowhere in custom rom instructions says to backup your /efs folder.
Now in "About device" Baseband version is "Unknown" IMEI is "Unknown". I've searched everywhere for a fix and nothing. I tried the following:
Flash stock rom
Format /data and /cache
On keypad, dial *#7284# ....But i dont get the "Qualcomm USB settings" option so i cant try IMEI repair tools
I tried flashing different kernels and different custom roms
Apart from the IMEI problem, the Device cant access the 16GB internal memory. The stock rom flashes with no error, but when i go to
settings > storage: under "Device memory" its full with only 182MB used by some apps. I thought the memory could be bad, but after flashing
Perseus kernel and swapping external sd card for internal memory I can use the 16GB as external memory. I cant find a fix for that either.
INTERNAL MEMORY UPDATE: it seems that internal memory is mounting read only. Still trying to find a fix
Im currently on "T889UVALK8_T889TMBALK8_TMB" rom with Perseus kernel and using "11extsd2internalsd_gs3_fat32" to swap internal to external memory.
Side note: I bought the phone from a friend 2 days ago. Its the Tmobile version and I used cellunlocker to unlock to use it with AT&T. That worked, until I started messing with ROMS. No warranty available. I am desperately looking on how to fix this since i have no spare phone. Any help is highly appreciated and thank you for your time
Click to expand...
Click to collapse
It sounds like you did a NAND erase all in Odin. Flash back to stock, use triangle away, call samsung to fix it. I had the same issue and Samsung fixed it for free.
Free?
KillaHurtz said:
It sounds like you did a NAND erase all in Odin. Flash back to stock, use triangle away, call samsung to fix it. I had the same issue and Samsung fixed it for free.
Click to expand...
Click to collapse
Even without insurance? And what am I going to tell them?

Hard Bricked Phone, long story.

I assume since this is the AT&T Galaxy S 3 section, you already know that I have the SGH-i747 model.
So I've been looking for a while, and I can't find anyone that has caused my same problem the way I did. I'll give the entire story: After having my S3 for a while, I decided to try rooting. I did it successfully, and got CyanogenMod installed. I don't know what, but I wanted to go back to touchwiz. I loaded a backup because it was exactly what I had before CM. fast forward about a month and a half, AT&T keeps bugging me about some update. It's the 4.3 update, I find out, after I installed it. Now, here's the confusing part. The SuperUser app was left over, but I have no CWM and no root privileges. I used this watch?v=yuBuD9aL12o (Paste after yt url) tutorial to root and get SuperSU, and it worked. The phone restarted many times in that entire process, and in the end it worked. One forum told me to install and apk called EZ-Unlock12.apk to unlock my boot loader. (I have included the exact APK if you want to look at it.) It just said successful and I closed out. Now, I wanted to flash CWM again with ODIN. I installed the drivers, and booted up ODIN. This is when it happened. I loaded up the CWM.tar.md5 file into ODIN, (not exact file name but you get what I mean), and it did it's verification and said it was good. I don't remember having my phone plugged in while doing this. I went to shut down my phone and put it in DL/ODIN mode. But now it has happened. I tried to bring my phone back up, but it didn't give ANY feedback. The only possible way to make it do ANYTHING is to plug it in without the battery, and i get the red light. I think it may have been that boot loader unlock program that messed it up, but I can't say for sure.
TL;DR I hardbricked my phone and don't know what went wrong.
Is that app for the verizon version of the s3? I believe the AT&T version of the s3 is the SGH-i747; however, your post refers to the sch-747 in the first line. From everything I have read, there is no way to unlock the AT&T s3 bootloader.
Not sure if this would help: http://forum.xda-developers.com/showthread.php?t=2549068
audit13 said:
Is that app for the verizon version of the s3? I believe the AT&T version of the s3 is the SGH-i747; however, your post refers to the sch-747 in the first line. From everything I have read, there is no way to unlock the AT&T s3 bootloader.
Not sure if this would help: http://forum.xda-developers.com/showthread.php?t=2549068
Click to expand...
Click to collapse
I meant SGH-i747, sorry for any confusion.
Did you try the unbricking method I linked? I think that may be the only way to unbrick the phone since it appears that your bootloader has been corrupted. If the unbrick method doesn't work, you'll probably have to have it repair via jtag.
Were you able to get it back to normal state? I am in the same situation as you with the same problem and was wondering if i should go do the method someone provided or just go ahead and pay for a jtag service.

Stuck on Samsung boot screen

I rooted my old milestone many years ago but havee been keeping my devices stock ever since, until today that is. Today I decided I wanted to try to root my Samsung SGH-I747M with Telus and everything seemed to start off smoothly. Once installed the SuperSU stopped working. I tried fixs I had read online such as updating the app, but this did not work. I read on a forum that you could flash something to disable know to help fix the problem. When I tried going this avenue I was not able to reboot my phone. I tried restoring from a backup taken before flashing, but I havent done any of this in so long im not entirely sure the backup took properly. At one point I got a message saying no OS was installed but after restoring this seemed to go away. I apparently do not remember anything about rooting from my milestone and am hoping someone may be able to help me get out of this mess. I am currently downloading the stock firmware and I think I will try flashing it tomorrow. I also was hoping someone could point me in the direction of a thread on xda that went into a more detailed explanation of how rooting works, what specifically roms and flashing all is and does. Any help is greatly appreciated.
cdriver said:
I rooted my old milestone many years ago but havee been keeping my devices stock ever since, until today that is. Today I decided I wanted to try to root my Samsung SGH-I747M with Telus and everything seemed to start off smoothly. Once installed the SuperSU stopped working. I tried fixs I had read online such as updating the app, but this did not work. I read on a forum that you could flash something to disable know to help fix the problem. When I tried going this avenue I was not able to reboot my phone. I tried restoring from a backup taken before flashing, but I havent done any of this in so long im not entirely sure the backup took properly. At one point I got a message saying no OS was installed but after restoring this seemed to go away. I apparently do not remember anything about rooting from my milestone and am hoping someone may be able to help me get out of this mess. I am currently downloading the stock firmware and I think I will try flashing it tomorrow. I also was hoping someone could point me in the direction of a thread on xda that went into a more detailed explanation of how rooting works, what specifically roms and flashing all is and does. Any help is greatly appreciated.
Click to expand...
Click to collapse
General section is most likely the best place for that.
Here's a How-to that should get you started: http://forum.xda-developers.com/showthread.php?t=2538991
And here is the Sticky index: http://forum.xda-developers.com/showthread.php?t=1725839 Lots of good guides and info in there!
General section is most likely the best place for that.
Click to expand...
Click to collapse
The Only problem is I already attempted to follow this and my phone will no longer boot up. Also I tried navigating through the stickies. couldn't find much info for my device. I will be trying to flash the stock firmware tonight but I want to have a clear understanding on what flashing is and what the difference is between os firmware kernel and rom and such BEFORE flashing this firmware tonight. I hope someone will be able to help.
cdriver said:
The Only problem is I already attempted to follow this and my phone will no longer boot up. Also I tried navigating through the stickies. couldn't find much info for my device. I will be trying to flash the stock firmware tonight but I want to have a clear understanding on what flashing is and what the difference is between os firmware kernel and rom and such BEFORE flashing this firmware tonight. I hope someone will be able to help.
Click to expand...
Click to collapse
Well that info is already in the Sticky Index. Understanding what you're doing (or about to do) is really important but you gotta start reading, it's all there.
OS, firmware and ROM are the same thing.
When your phone boots, it basically goes: Bootloaders -> Kernel -> ROM (OS).
The kernel has pretty much all the "underground" controls (RAM, Mhz, governor, scheduler, BT, Wifi, etc).
I won't write everything but those are the basics.
Also, having a Canadian variant of the S3 (that's what the M is for), doesn't change much other than flashing bootloaders and stock ROM (which you'll wanna use the Canadian variant bootloaders and Telus ROM for stock). Everything else is basically the same.
Also, having a Canadian variant of the S3 (that's what the M is for), doesn't change much other than flashing bootloaders and stock ROM (which you'll wanna use the Canadian variant bootloaders and Telus ROM for stock). Everything else is basically the same.
Click to expand...
Click to collapse
Sweet I will definitely check that out. So I did flash twrp to my phone. Is it possible that I flashed the version say for the i747 but not the m version and that is why the phone wont move past the samsung screen? Also should I attempt to get rid of twrp before flashing the stock firmware. This should answer all my questions and then I will explore the stickies some more.
cdriver said:
Sweet I will definitely check that out. So I did flash twrp to my phone. Is it possible that I flashed the version say for the i747 but not the m version and that is why the phone wont move past the samsung screen? Also should I attempt to get rid of twrp before flashing the stock firmware. This should answer all my questions and then I will explore the stickies some more.
Click to expand...
Click to collapse
If flashing a stock ROM, flash the Telus one. If flashing a custom ROM, it doesn't matter (I747 or M variant), as long as it's D2LTE.
Your recovery doesn't change anything to flashing with Odin, it will overwrite it.
Flashing the stock firmware fixed my problems. Thanks for all of your help and I will definitely be checking out the links that you sent me before trying to root again tomorrow.

Device variant/ROM question

Hello,
I have an LG G3 AS990 (Ntelos). I would like to root and flash a different ROM, but am having trouble finding my variant as Ntelos is a smaller carrier. Does anyone have any advice on compatibility between any other variants? Any advice would be greatly appreciated.
Thank you
I've continued to search, but haven't found anything. Just hoping someone may have some information.
Same Boat
Snakemanc6 said:
I've continued to search, but haven't found anything. Just hoping someone may have some information.
Click to expand...
Click to collapse
I've been researching this as well. You could try finding the beta version of CM for Sprint's LS990. I would try it just for the fun of it, but I'm nervous that I don't have the stock rom for AS990 to revert back to. I have my system backed up, but I'm not comfortable enough to rely on that to save my phone if I brick it trying to install CM.
Bump. I have the same problem here, except that mine got pushed an OTA patch that prevents stump and others. So far no firmware I have found is compatible with this device to even downgrade in order to root in the first place. If anyone has succeeded with as990 NTelos please help.
Bumping the necro in hopes of support. XD my software says as99020a but the writing on the back under the cover says us990... So I'm not sure what I'm supposed to do especially since I can't even find a place to download the firmware for manual updates.. Etc. :-[ Damn ntelos
AS990 Recovery?
Has anyone found a recovery that works with the AS990?
I have an option
I've posted a way to use TWRP and ROMs for the LS990 on the LG G3 subreddit, I need 10 helpful posts before I can post it here because I have a few xda posts and downloads linked.
AS990 experience
Hi all,
I have tried different roms on my as990 (Carolina West Wireless) by using the method on reddit (HERE) and everything works just a few things to keep in mind
To get your sim to work on a custom rom you may need to change the build.prop ro.build.target_operator=, and ro.afwdata.LGfeatureset=
Take note of these settings before you try to reflash the phone. If you change one, change both if applicable.
Remember to backup your old build.prop
Backup all apns before you start using method found (HERE)
Backup build.prop
Oh and did I mention backup build.prop
The restore files can be found (HERE) and use the guide found (HERE) replacing the files mentioned with the ones in the post. If you use this method to restore you phone, the build.prop from the reddit post will not work so use the old build.prop that I'm sure by now you have backed up or you will have to get the custom .dll file elsewhere to restore.
For all who have taken the ota update, the restore method works for that too
Your carrier files are automatically restored if you use the firmware in the above post. That is to say they were for me but if anyone else test this
no guarantees but it did work flawlessly for me.
Also I am currently working on a recovery for AS990 if anyone has any ideas feel free to chime in
A couple of side notes
The method by tybskinner may also work if you flash to US990 as well, but I have not tried this yet. To do so you would need the custom .dll or the build.prop for US990
Users have reported that SIM unlock is possible by changing the the build.prop ro.build.target_operator= to global or open however I have not tried this yet
If anyone has a method to change the PRL on the device please let me know I have tried several options but no method I have tried will allow the PRL to stick
P.S. not trying to steal your thunder tybskinner just making it easier for people to find the links
Thanks for the info guys. At this point I'm having issues just trying to root the thing. Lost root with Lollipop, and for some reason I cant seem to regain it. Oh well. The price you often pay for having a smaller carrier (I actually work for nTelos, so its my work provided device).
Thanks again. I hope you guys are able to get yours setup the way you like. :good:
Snakemanc6 said:
Thanks for the info guys. At this point I'm having issues just trying to root the thing. Lost root with Lollipop, and for some reason I cant seem to regain it. Oh well. The price you often pay for having a smaller carrier (I actually work for nTelos, so its my work provided device).
Thanks again. I hope you guys are able to get yours setup the way you like. :good:
Click to expand...
Click to collapse
Currently there is no root method for the AS990 device on the newest ROM however if you follow the guide posted you can downgrade to the previous version and go from there.
Have a look here...I found a way around the whole super secure as990 crap
http://forum.xda-developers.com/lg-g3/help/how-to-as990-custom-recovery-roms-t3216133
It may seem like a bit much but it works like a champ!
HI
bobo040 said:
bump. I have the same problem here, except that mine got pushed an ota patch that prevents stump and others. So far no firmware i have found is compatible with this device to even downgrade in order to root in the first place. If anyone has succeeded with as990 ntelos please help.
Click to expand...
Click to collapse
you need to download iroot on your computer then connect your phone on the portable usb outlet make shure your phone is debbugged then open iroot it will read your phone wait wor a while and you are golden
yorimoto1987 said:
you need to download iroot on your computer then connect your phone on the portable usb outlet make shure your phone is debbugged then open iroot it will read your phone wait wor a while and you are golden
Click to expand...
Click to collapse
You can still use the method in this post to downgrade.
hi need help
thjubeck said:
Hi all,
I have tried different roms on my as990 (Carolina West Wireless) by using the method on reddit (HERE) and everything works just a few things to keep in mind
To get your sim to work on a custom rom you may need to change the build.prop ro.build.target_operator=, and ro.afwdata.LGfeatureset=
Take note of these settings before you try to reflash the phone. If you change one, change both if applicable.
Remember to backup your old build.prop
Backup all apns before you start using method found (HERE)
Backup build.prop
Oh and did I mention backup build.prop
The restore files can be found (HERE) and use the guide found (HERE) replacing the files mentioned with the ones in the post. If you use this method to restore you phone, the build.prop from the reddit post will not work so use the old build.prop that I'm sure by now you have backed up or you will have to get the custom .dll file elsewhere to restore.
For all who have taken the ota update, the restore method works for that too
Your carrier files are automatically restored if you use the firmware in the above post. That is to say they were for me but if anyone else test this
no guarantees but it did work flawlessly for me.
Also I am currently working on a recovery for AS990 if anyone has any ideas feel free to chime in
A couple of side notes
The method by tybskinner may also work if you flash to US990 as well, but I have not tried this yet. To do so you would need the custom .dll or the build.prop for US990
Users have reported that SIM unlock is possible by changing the the build.prop ro.build.target_operator= to global or open however I have not tried this yet
If anyone has a method to change the PRL on the device please let me know I have tried several options but no method I have tried will allow the PRL to stick
P.S. not trying to steal your thunder tybskinner just making it easier for people to find the links
Click to expand...
Click to collapse
Iam actually stuck in the in blue screen and a red number 2 factory status everytime i turn on my phone it says miniOS icant actually find any stock firmware for my lg g3 as990 it really does sucks doe becouse i had a lot of stuff in my phone that really needed but if you can help i will be really regretful ive been trying for a weak now
yorimoto1987 said:
Iam actually stuck in the in blue screen and a red number 2 factory status everytime i turn on my phone it says miniOS icant actually find any stock firmware for my lg g3 as990 it really does sucks doe becouse i had a lot of stuff in my phone that really needed but if you can help i will be really regretful ive been trying for a weak now
Click to expand...
Click to collapse
You need to hold the power button and press normal boot
The as990 stock rom is http://forum.xda-developers.com/lg-g3/general/lg-g3-as990-firmware-as99010a-t3183928

HTC ONE M9 Stuck in BOOTLOADER LOOP - Willing to Compensate

I recently bought a new HTC One M9 from Ebay brand new, the listing said it was unlocked and gsm. Unfortunately this was not true, so when i finally got it I had to unlock it myself which i managed but i went further and wanted to root my phone, as far as rooting after the step to install Team Win Recovery Project, I followed this tutorial: (youtube.com/watch?v=rOHN8byHAzk&t=941s) and basically im like all the other guys who have their phone stuck in bootloader loop, i've tried the RUU exe's from HTC they end up giving me a "Signagure" (spelt that way) error so i cant use that, i've cycled through multiple micro sd cards to try get the stock os to install in the download boot. i've getting roms they dont work and the loop just continues. Im lost guys...and heartbroken with a new uselss phone...IM WILLING TO PAY(within reason) anyone that can help me to get my phone back to normal.
The phone was from USA under Sprint, I tested my GSM network when I had it unlocked and it worked, I dont care if I can only get it back on Sprint, I just want it working again. Again I'm willing to Pay the person via PayPal to Help me out.
Thank you. you can contact me at [email protected]
Never ever follow video tutorials. They're outdated as soon as they get uploaded.
Depending on the firmware version of your phone you need different files for rooting your M9. That's why you ended up with a bootloop. The video doesn't give you that information.
Take a look at the ReadMe thread. It should explain all you need to know and contains all files you might need for recovering your phone.
Flippy498 said:
Never ever follow video tutorials. They're outdated as soon as they get uploaded.
Depending on the firmware version of your phone you need different files for rooting your M9. That's why you ended up with a bootloop. The video doesn't give you that information.
Take a look at the ReadMe thread. It should explain all you need to know and contains all files you might need for recovering your phone.
Click to expand...
Click to collapse
THank you for replying im still busy looking for help on how to do this, I stand by my promise i will PayPal anyone that can help me save my device, I consider myself tech efficient in general, im just new to android - this is my first andeoid.
As said before, just look at the ReadMe thread. A bootloop isn't the end of the world. There's no need to pay anyone at this point since all files and information you need are available for free.

Categories

Resources