Ok, so I wasn't paying attention to what I downloaded and ended up trying to flash an AT&T Galaxy S2 ROM on my T989. I ended up with a total brick and the only way it can be read is via QPST, the Qualcomm tool.
Now, from what I can tell - and I've not messed with this before - I need to flash back a restore image in order to get the phone back. But I haven't been able to find one anywhere. I might be very naive (and probably am...) but it would seem to me that if someone downloaded the QPST tool and did a backup then I could use those files.
Again, if anyone has any experience with this it would be much appreciated. Clearly the phone is salvageable, but just not without a lot of work
msingh11 said:
Ok, so I wasn't paying attention to what I downloaded and ended up trying to flash an AT&T Galaxy S2 ROM on my T989. I ended up with a total brick and the only way it can be read is via QPST, the Qualcomm tool.
Now, from what I can tell - and I've not messed with this before - I need to flash back a restore image in order to get the phone back. But I haven't been able to find one anywhere. I might be very naive (and probably am...) but it would seem to me that if someone downloaded the QPST tool and did a backup then I could use those files.
Again, if anyone has any experience with this it would be much appreciated. Clearly the phone is salvageable, but just not without a lot of work
Click to expand...
Click to collapse
Search for this user: darkspr1te, he has a guide up on one of the forums that might be able to help you.
Edit: http://forum.xda-developers.com/showthread.php?t=1914359
Related
I bought a used nexus its in great condition everything works but the buyer didnt tell me it was rooted already. Thats fine cause i was going to but i wanted to learn the ropes myself. So is there anyone to get back to 100% stock? He flashed a CWM too. I just want to do it myself. And is there anyway to wipe format the internal memory aswell? Thanks!
you can use this guide : http://forum.xda-developers.com/showthread.php?t=1626895
even if you don't want to convert and already have yakju or takju, this is the way you can go back to pure stock
bgdxv said:
you can use this guide : http://forum.xda-developers.com/showthread.php?t=1626895
even if you don't want to convert and already have yakju or takju, this is the way you can go back to pure stock
Click to expand...
Click to collapse
Yup this guide is the way to go. Flash the "takju" images. There's full 4.1.1 images now too.
Thanks guys i have a usa gsm model and I guess i looked around and found out a way to wipe the internal data with those tools so i think im good and im kinda getting the hang of using the tool kit. But the phone has 4.1 i wanted to install rooted 4.1.1 is that possible? or how would i go about doing that? Thanks alot for your quick and helpful responses!
Nocturnal86 said:
Thanks guys i have a usa gsm model and I guess i looked around and found out a way to wipe the internal data with those tools so i think im good and im kinda getting the hang of using the tool kit. But the phone has 4.1 i wanted to install rooted 4.1.1 is that possible? or how would i go about doing that? Thanks alot for your quick and helpful responses!
Click to expand...
Click to collapse
Don't use a toolkit. Follow that guide posted. That guide will wipe the device completely and put you on 100% stock 4.1.1. If you want root, you can follow the last part of the guide, which has a step-by-step routine to root also.
martonikaj said:
Don't use a toolkit. Follow that guide posted. That guide will wipe the device completely and put you on 100% stock 4.1.1. If you want root, you can follow the last part of the guide, which has a step-by-step routine to root also.
Click to expand...
Click to collapse
Why shouldnt i use the tools? they seem pretty straight foward is there something bad about them? But Im finally going to get a chance to follow that guide hopefully and go to 4.1.1 and then root it cause i just want root right now for back up purposes. But thans for the info!
Nocturnal86 said:
Why shouldnt i use the tools? they seem pretty straight foward is there something bad about them? But Im finally going to get a chance to follow that guide hopefully and go to 4.1.1 and then root it cause i just want root right now for back up purposes. But thans for the info!
Click to expand...
Click to collapse
The tools aren't inherently bad, but they're kind of a "black box" to new users, where they put their phone in and it comes out rooted/flashed. The issue occurs when something goes wrong, and the user doesn't know why because they don't understand the procedure, and they can't reverse engineer what happened to fix it. So what they end up doing is coming and posting threads, etc.
If they were doing it the "real" (manual) way, via Fastboot, they'd know what was going on and have a better understanding of what they're doing to their phone. Because we have a Nexus, there's really no reason not to just use Fastboot because it's the tool that Google gives us. You own a ~$650 (much cheaper now w/ the Play Store, but still) device, why not spend 15 minutes learning how to work with it properly?
martonikaj said:
The tools aren't inherently bad, but they're kind of a "black box" to new users, where they put their phone in and it comes out rooted/flashed. The issue occurs when something goes wrong, and the user doesn't know why because they don't understand the procedure, and they can't reverse engineer what happened to fix it. So what they end up doing is coming and posting threads, etc.
If they were doing it the "real" (manual) way, via Fastboot, they'd know what was going on and have a better understanding of what they're doing to their phone. Because we have a Nexus, there's really no reason not to just use Fastboot because it's the tool that Google gives us. You own a ~$650 (much cheaper now w/ the Play Store, but still) device, why not spend 15 minutes learning how to work with it properly?
Click to expand...
Click to collapse
I can understand that and i usually do want to learn the ropes but i was kind of thrust into the middle cause i bought a used nexus and it was rooted and had CWM 6 flashed to it so I am just trying to figure things out a bit or at least go back to Full stock and no recovory flashed so i can learn the ropes myself and flash recoverys myself if needed and i want to get 4.1.1 and root it myself. If possible can i use the tools to just go to stock and then learn the manual ways from there? I got adb and the fastboot.exe finally so i never had that or new i needed it and when i first used the toolkit to wipe my sd I think it installed some drivers that the tool kit told me to which im hoping are correct. I really hate to ask questions unless its needed and i apprecieate it.
Nocturnal86 said:
I can understand that and i usually do want to learn the ropes but i was kind of thrust into the middle cause i bought a used nexus and it was rooted and had CWM 6 flashed to it so I am just trying to figure things out a bit or at least go back to Full stock and no recovory flashed so i can learn the ropes myself and flash recoverys myself if needed and i want to get 4.1.1 and root it myself. If possible can i use the tools to just go to stock and then learn the manual ways from there? I got adb and the fastboot.exe finally so i never had that or new i needed it and when i first used the toolkit to wipe my sd I think it installed some drivers that the tool kit told me to which im hoping are correct. I really hate to ask questions unless its needed and i apprecieate it.
Click to expand...
Click to collapse
The guide that was linked earlier is extremely simple to follow. It breaks everything down step by step, and you will be fully stock.
I am trying to get my vm intercept to work on page plus. First I tried to root it and was unsuccessful. Next I tried to us SWUpdate to flash a sprint rom. It gave me the error unable to open bin file. Also my sd card slot is broken. I really want to flash the sprint rom so I can update the prl. Any help would be greatly appreciated.
I don't think anyone will want to help us. I asked for help with rooting my backup phone, which is an Intercept. Still no response. I hope you get it taken care of!
Yeah, I was getting that feeling when I looked around this part of the forums. Maybe Someone can help me with SWUpgrade(cannot open bin file), I think I could achieve the rest if I could get that to work. This is where I got the sprint rom: http://www.howardforums.com/showthread.php/1691827-Intercept-free-stock-ROMs-and-apps!
Hi! I need some serious help. I accidentally bricked my phone while updating the Bootloader.
It's a Samsung Galaxy S3 SGH-T999L (T-Mobile, but it works with my Vodaphone SIM)
Absolutely nothing on the screen, no boot, no recovery mode (just installed CWM), no download mode. Just a red LED when plugged in via USB.
Device Manager shows this: "QHSUSB_DLOAD"
I live in Egypt so there's no such thing as 'insurance' or 'warranty'.
I tried the instructions here: http://forum.xda-developers.com/showthread.php?t=2439367
Didn't work.
Is this the end? Or is there yet hope for it?
Need to know the details of what you flashed and what steps you followed.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Need to know the details of what you flashed and what steps you followed.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I just installed the CWM custom recovery via Android Toolkit, and was preparing to flash Cyanogen. It said that an S3 needed a Bootloader update to install Cyanogen versions greater than 10.1, So I followed the links and I think I accidentally flashed the Bootloader for SGH-T999 (not the T999L).
CWM said it succeeded, rebooted the phone (did not fix root when it asked), and it just never turned on since (it's been a while)
P.s: Idk if this even matters when its as deep as the Bootloader, but the phone had been rooted for months before.
Oh, and I found this and am downloading the latest T999L in case I need it if ODIN can help: http://forum.xda-developers.com/showthread.php?t=2439367
And from yet more Google I found these drivers, but it won't let me post outside links
But Device Manager says "Driver is not intended for this platform."
That's all I got so far, will keep looking for a good driver and check this thread as often as I can
This is gonna probably sound stupid, but I tried an emergency recovery with Kies, but it needed me to get it in Recovery Mode.
No change so far. Any help finding the right drivers would be very helpful.
Kygies27 said:
This is gonna probably sound stupid, but I tried an emergency recovery with Kies, but it needed me to get it in Recovery Mode.
No change so far. Any help finding the right drivers would be very helpful.
Click to expand...
Click to collapse
YAY! Found working drivers here: http://forum.xda-developers.com/showthread.php?t=1536354&page=4
By: richardlibeau
ATTACHED FILES
File Type: zip QHSUSB_Drivers_(x64).zip - [Click for QR Code] (72.3 KB, 568 views)
File Type: rar qhsusb_dload_Drivers.rar - [Click for QR Code] (56.0 KB, 584 views)
More Google (Where is everybody?)
Found this: http://forum.gsmhosting.com/vbb/f824/karbonn-a9-dead-qualcomm-hs-usb-qdloader-9008-how-fix-1740061/
It seems if I can just find the corresponding hex files, etc, this could work.
Or I could somehow reprogram my CPU and make things even worse...
I'm really stuck now.
P.s: I've ofc by now seen nearly everyone go for a JTAG repair. I will check the shops around here when they open, but I don't know if they can do anything about it.
Jtag should be able to repair that kind of brick. Unfortunately, when its due to flashing a different devices firmware, our device methods won't usually work.
You can try the d ebrick method we have posted in development, but just don't expect much. (You never know though, you might get lucky).
I doubt following this instructions will work as they are for a different device. Big risk to try it imo. Might make it non-recoverable by any means. (The process might work, I don't know, but you'd likely need specific files for your device).
Jtag is probably your best option. And in the future, stay away from the toolkit! Its bricked a number of devices and the dev just ignores support requests, even from those who buy it...
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Jtag should be able to repair that kind of brick. Unfortunately, when its due to flashing a different devices firmware, our device methods won't usually work.
You can try the d ebrick method we have posted in development, but just don't expect much. (You never know though, you might get lucky).
I doubt following this instructions will work as they are for a different device. Big risk to try it imo. Might make it non-recoverable by any means. (The process might work, I don't know, but you'd likely need specific files for your device).
Jtag is probably your best option. And in the future, stay away from the toolkit! Its bricked a number of devices and the dev just ignores support requests, even from those who buy it...
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Yeah, shops open soon so hopefully I can see what can be done.
I figured not to bother with the qualcomm tools, messing with things I didn't quite understand was how I got in this trouble in the first place.
But just to clarify something, the Android Toolkit wasn't what bricked it, I tried to install the firmware from a .zip on my SDcard viz CWM recovery, but it was the wrong one (I was so damn sure I was T999, not T999L).
Thank you guys for all the help, I'll post if the guy fixes it!
I know, I only mentioned it because you mentioned using it. Just warning you for the future is all.
Good luck!
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
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.