Develop Bugs

[Q] SGH-t999n bricked?? HELP!

I just bought this metro s3 and wanted to root it, well supersu was giving error everytime I tapped it so I decided to try an unroot with many of the methods on here and along the way ended up where my phone will not get past the galaxy siii sgh-t999n boot screen.
I used odin to do this, my phone is not being recognized under auto play but pc makes the connection sound when I plug usb in to my pc.
anyways I'm stuck at that screen and can only enter odin recovery on my phone and I have tried factory reset and still end up at the same boot screen and left it like that all night an woke up to the same screen.
I'm hoping this is not not a $300. brick.
I did download the files from a thread that described the files below were for the "T999l & T999n" and IF there was any difference int he files then the OP would point that out he said and I tripple checked to make sure in the section of the listed files to download did not mention the T999n was not for those specific files but there was nothing mentioned..

Please link the said thread.
You have not specified the firmware and android version you had before all this happened. Please specify that. Next Course of action depends on as much information you could provide about previous setup, Bootloader, Rom, Kernel & Baseband.
I think you only have a Non-Bootable Rom. I'd call that as a soft-Brick and not Hard-Brick. So there's no chance of you getting a $300 Paperweight. :laugh:
Having said that, given that all you want is Root, then
1. Flash Root66 version of your Firmware.

Perseus71 said:
Please link the said thread.
You have not specified the firmware and android version you had before all this happened. Please specify that. Next Course of action depends on as much information you could provide about previous setup, Bootloader, Rom, Kernel & Baseband.
I think you only have a Non-Bootable Rom. I'd call that as a soft-Brick and not Hard-Brick. So there's no chance of you getting a $300 Paperweight. :laugh:
Having said that, given that all you want is Root, then
1. Flash Root66 version of your Firmware.
Click to expand...
Click to collapse
Well I have solved my boot issues my installing CWM (which before would not stick after boot) and flashing 3 files from Docholiday on a thread but now the phone boots up as a T999L 4g LTE and has changed the model number under about phone. I have to unlock the phone as I only have a tmobile sim for this said Metropcs T999N device so I will see what happens after I try to unlock it.
thanks you for your prompt response!!

If Settings > About > Model is the only problem you have, then use Build.prop Editor from Playstore and change the value for RO.BUILD.DISPLAY.ID. Set it to what your device is.

Im not bothered by it myself as long as it wont effect my device?? also effect any future updates or when a program tries to sync with my device or anything other??

I don't believe there would be issues of this nature.

Tried rooting today -- soft brick

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.

Update Problems via OTA, RUU, phone.

Hi everyone, first thread in xda!
So, my friend has a m9 that bought on April of 2016 in Germany, worked just fine until these days, it has already marshmallow, he was on exchange but now he's back to Paraguay.
Yesterday we tried to update, because there were updates available (3.35.401.32), so we downloaded from the phone settings.
Downloaded just fine, and when trying to install, just installed until 25% and then the red triangle appeared. I've been looking for some info, and just found that happened to some people too, but no answer or positive help.
Then I downloaded the Nougat OTA to just flash it via recovery (sideload); once in Recovery mode, headed to ADB install, renamed the OTA zip (to be accurate OTA_HIMA_UL_N70_SENSE80_ATT_MR_NA_Gen_Unlock_4.14.617.6_R-3.35.617.31_release_490897lkj8xif5v3eoiykd.zip) just to "ota.zip" cuz i'm so lame to write the whole name.
The flashing went well until @ ±40% and then Error Status 7 appeared, saying "This Package is for 'htc_himaulatt' devices; this is a 'htc_himauhl.'"
I think that the error might be in the regional versions, but I searched for HIMAUHL and there is NOTHING, NOWHERE.
Anyways, then I just downloaded the RUU from HTC's page, and still with no positive results, still on marshmallow and no possibilities to upgrade.
Any help?

martynssimpson said:
Hi everyone, first thread in xda!
So, my friend has a m9 that bought on April of 2016 in Germany, worked just fine until these days, it has already marshmallow, he was on exchange but now he's back to Paraguay.
Yesterday we tried to update, because there were updates available (3.35.401.32), so we downloaded from the phone settings.
Downloaded just fine, and when trying to install, just installed until 25% and then the red triangle appeared. I've been looking for some info, and just found that happened to some people too, but no answer or positive help.
Then I downloaded the Nougat OTA to just flash it via recovery (sideload); once in Recovery mode, headed to ADB install, renamed the OTA zip (to be accurate OTA_HIMA_UL_N70_SENSE80_ATT_MR_NA_Gen_Unlock_4.14.617.6_R-3.35.617.31_release_490897lkj8xif5v3eoiykd.zip) just to "ota.zip" cuz i'm so lame to write the whole name.
The flashing went well until @ ±40% and then Error Status 7 appeared, saying "This Package is for 'htc_himaulatt' devices; this is a 'htc_himauhl.'"
I think that the error might be in the regional versions, but I searched for HIMAUHL and there is NOTHING, NOWHERE.
Anyways, then I just downloaded the RUU from HTC's page, and still with no positive results, still on marshmallow and no possibilities to upgrade.
Any help?
Click to expand...
Click to collapse
So what is the device SKU? It sounds like your phone did exactly what it was supposed to do - reject an incompatible RUU.

There is a possibility that the device is rooted, you cannot update unless the phone is stock. You need to put the phone in download mode, connect to a pc via usb cable and in cmd type: fastboot getvar all
Then you tried to flash an att firmware on a wwe international device so it rejected it, which is normal.
I can safely tell you that you'll be lucky to recover the phone from its current state. You must now do a lot of reading. Starting with flippys thread in the general section of the m9 forum.
Lucky for you I have the same device with a stock backup (except the stock recovery) at the same firmware you had before you started should you need it, I think you will. It is linked in flippy's thread.
Beamed in by telepathy.

computerslayer said:
So what is the device SKU? It sounds like your phone did exactly what it was supposed to do - reject an incompatible RUU.
Click to expand...
Click to collapse
Yes, the SKU is HIMA_UHL, european version I guess (?)
shivadow said:
There is a possibility that the device is rooted, you cannot update unless the phone is stock. You need to put the phone in download mode, connect to a pc via usb cable and in cmd type: fastboot getvar all
Then you tried to flash an att firmware on a wwe international device so it rejected it, which is normal.
I can safely tell you that you'll be lucky to recover the phone from its current state. You must now do a lot of reading. Starting with flippys thread in the general section of the m9 forum.
Lucky for you I have the same device with a stock backup (except the stock recovery) at the same firmware you had before you started should you need it, I think you will. It is linked in flippy's thread.
Beamed in by telepathy.
Click to expand...
Click to collapse
Okay m8, thanks! I'll be reading.
It's funny cuz my friend doesn't know **** about rooting and stuff like that, but i'll give a try.

Sent from my Andromax AD687G using XDA Free mobile app

[INFO][PERRY] Pulled the OTA from BOOST/Sprint phone. Don't know if it could be used.

I picked up the Moto E4 recently and rooted it. The OTA has been sitting in limbo because I didn't wanna get screwed and get stuck in an non-root attainable update. As soon as I got root, pulled it, and here ya are. I have included a list to procure as well.
Link for download HERE
I hope it helps.

emtee40 said:
I picked up the Moto E4 recently and rooted it. The OTA has been sitting in limbo because I didn't wanna get screwed and get stuck in an non-root attainable update. As soon as I got root, pulled it, and here ya are. I have included a list to procure as well.
Link for download HERE
I hope it helps.
Click to expand...
Click to collapse
Could you possibly make a back up and upload it for me before you make any system modifications. I have boost but my original backup got corrupted somehow and I want to make sure what I'm running is the right firmware. I also want a backup of that original firmware. If you could also do me another favor and pull the oem.img and modem.img and upload them along with the recovery.img? I'm making stock ROMs and for some reason a rom made with what I thought was Sprint firmware works fine, but one made with what I thought was Boost firmware gives me a boot loop for some reason and I'm trying to figure out why? I'd really appreciate it. If you don't know how to pull the imgs I can instruct you, it's really simple. Thanks!

This is the older update, right? Not a new one...

ATTACK said:
This is the older update, right? Not a new one...
Click to expand...
Click to collapse
I just bought the Verizon varient. It updated today. I plugged into my PC and ran Kingroot. It asked to "try new root strategy", something it did not ask before. Root still fails though.

"This is the older update, right? Not a new one..."
Probably, it will bring NCQ26.69-33 to NCQ##.##-35 for Boost. (According to meta file in zip)
"I also want a backup of that original firmware"
Since I've already rooted, unrooted, lost cell service, lost system, and, just today, bringing it back to a usable state, I can vouch for the NCQ26.69-33 located here
Use the RSD XML-to-flash tool. Found it on Google somewhere.
My best advice is to use the "dm-verity-opt-encrypt.zip" located in root guide before any flash, especially if it entails a system related modification (ie magisk, scripts, etc). If ya get a non-flashable state, flash the boot.img again in twrp, reboot and redo the flash "dm-verity-opt-flash.zip"
Many thanks for kartik verma for posting the OEM device files link.

ATTACK said:
This is the older update, right? Not a new one...
Click to expand...
Click to collapse
DragonFire1024 said:
I just bought the Verizon varient. It updated today. I plugged into my PC and ran Kingroot. It asked to "try new root strategy", something it did not ask before. Root still fails though.
Click to expand...
Click to collapse
Using Motorola's company website to get the unlock key and using fastboot to flash, as stated in the rooting guide, is most thorough. Less 3rd party spam too
I have Boost but digging in the device files has shown a lot of 'verizon' being in various system files. Sprint, is Sprint, especially in prepaid flavors, imho.

...35? I have NCQ26-69-48 on a Boost E4. So yeah, older firmware.

Yes, the newest Boost firmware is this one from the link posted above.
SPERRY_SPRINT_7.1.1_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
1.6 GiB
The one without 7.1.1 in the name is Sprint.
Sent from my Moto E (4) using XDA Labs

Question Reinstalling from "https://pixelrepair.withgoogle.com/"

Hi all. I would like to reinstall the firmware on my P6Pro, and though it's a UK unlocked, unbranded Vodafone model can I reinstall it with the EE firmware as it's the SIM I've used from day one?
My phone firmware is :
SQ1D. 220105.007

As far as I know, SQ1D.220105.007 is the only latest (January) firmware available for the Pixel 6 Pro. Correct me if I'm wrong, though. It's the only one listed at that official Google Pixel firmware webpage.

The above is correct, as is often the case they have consolidated all of it into one image in January.

Thanks people.
I have the Jan update.
Do you know why they even list selecting a carrier first?

greycounciller said:
Thanks people.
I have the Jan update.
Do you know why they even list selecting a carrier first?
Click to expand...
Click to collapse
Probably just a generic prompt for those devices or months that there are separate firmwares for different carriers.

Can't seem to get this feature to work.
When I go to "rescue" mode and connect phone, the repair doesn't seem to connect to phone and remains on loader page with phone showing "No Command"with the android bot on his back with a triangle above his open chest.
Retried it with different UK carriers and unlocked carrier.
Any thoughts?

greycounciller said:
Can't seem to get this feature to work.
When I go to "rescue" mode and connect phone, the repair doesn't seem to connect to phone and remains on loader page with phone showing "No Command"with the android bot on his back with a triangle above his open chest.
Retried it with different UK carriers and unlocked carrier.
Any thoughts?
Click to expand...
Click to collapse
You could try Official Google Android Flash Tool instead and see if that helps any better. I know Official Google Pixel Update and Software Repair is official, too - I'm not even clear on when the repair site will help that the flash site won't, since I've never used either. Lots of folks on here have used Official Google Android Flash Tool with great success, though. Let us know what happens.

Pixel repair tool hasn't been updated to support the 6/Pro yet - the only part of that website that works for either phone is the Fingerprint Calibration tool.
As above, install Google adb/fastboot drivers & then try to use the Android Flash Tool, that should work for you

DanielF50 said:
Pixel repair tool hasn't been updated to support the 6/Pro yet - the only part of that website that works for either phone is the Fingerprint Calibration tool.
As above, install Google adb/fastboot drivers & then try to use the Android Flash Tool, that should work for you
Click to expand...
Click to collapse
Thanks so much. That all makes sense.

DanielF50 said:
Pixel repair tool hasn't been updated to support the 6/Pro yet - the only part of that website that works for either phone is the Fingerprint Calibration tool.
As above, install Google adb/fastboot drivers & then try to use the Android Flash Tool, that should work for you
Click to expand...
Click to collapse
this is the right answer. Also, for every other Pixel that supports this Pixel Repair website (Pixel 3+), it's actually really hit or miss if the phone ever gets recognized at all.
Considering how amazing the Android Flash Tool works - unfortunately it looks like pixelrepair isn't getting the attention it deserves - probably for reasons that we aren't aware of - but development time is probably one of them.

Hi guys, just to let you know, eventually managed to do a flash with the 'Flash.andriod.com' tool. 5 mins and all easily done.
Thanks for all the help though.