I'm in a bit of a pickle with my stylo 2 plus (tmobile k550)
back in 2016 sometime i rooted my phone and everything was fine and working properly, i was able to do everything i wanted to do. For a while now i've been wanting to restore my my phone back to it's original de-rooted state but the thread i went to for the rom indicated that if i used a tmobile phone it may sim lock it to metro pcs which i didn't mind and i took a gamble on it and followed the instuctions i used LGUP and installed it and everything was going fine even shows me the metropc logo/animation on startup but it gives me an error with the IMS that it was unable to start and i'd close the message and it would just pop back up and i was not able to do anything else. on top of that when i installed the rom i opted to not keep twrp installed . that was a mess that took me a better part of the day to figure how to get back on the phone but i cannot use LGUP with a proper KDZ file as every time i try to run it it tells me that my phone is a MS550 and won't install because the KDZ file is for a K550, i also tried LG Flash Tool 2014 and it analyzes the phone go up to 30% jumps back to 25% then says "Required info cannot be found." and just below that it says "Contact the system administrator.."
I've tried practically every suggestion i could find via google and youtube (man alot of those videos were repetitive broken records to boot)
if someone could please help me with this problem i'd greatly like to restore my phone back to it being seen as a k550. (i really cannot afford to buy a new phone at the moment and really like this one)
thanks for taking the time to read this.
Edit: I went into twrp and did a wipe and the IMS error is now gone and i can access the metropcs version of this phone but i'd still love to get the tmobile rom back on here if possible.
Edit2: After a little more searching I realized i am blinder than i thought and found another non-kdz stock installer for the k550 was able to restore my phone fully. thanks for anyone that stopped by and took time to read this.
Related
I don't know where else to put this since this phone does not have its own forum here.
Here is my problem...
My vista was rooted and I was going to sell it to a friend so I was doing a factory reset with the phones built-in option... And the stock factory reset makes it all the way to where I enter my first and last name and then after doing so I get this error...
LGsetupWizard has stopped (there are more words but this sums it up)
And then the Setup Wizard restarts.
I then go through the setup process again thinking it will go through this time... Same error message... LGsetupWizard has stopped, and it restarts itself.
I have searched for a fix for this EVERYWHERE and cannot find a fix... I cannot even find the stock rom/firmware for my device: AT&T LG G Vista D631
The official website has no download and the only "stock" ROM/firmware I can find is for the Verizon VS880 and it's counter parts...
Can ANYONE help me get this phone fixed and make it all the way through the LGsetupWizard without it looping/stopping/crashing???
Really need some help from the pros as I have exhausted all my tools/methods in finding a fix/solution.
EDIT: I am able to get into the settings menu (with fast fingers) right after I click OK to get rid of the error message.
I have turned on DEV MOD and enabled all the settings needed in order to flash stuff and put stuff onto the phone via computer USB...
How can I fix this problem if I am able to have access to DEV MOD on phone???
Problem solved.
I used LG D631 TOT DLL.rar and LG Flash Tool.
I forgot where I got these files from, but I am sure a simple search on a search engine will help you find them.
After I got it to boot back up, I used TitaniumBackup and found that LGSetupWizard was "frozen"... So I unfroze it and did the factory reset again and it went all the way through the LG Setup.
Hello. I'm on pi3 firmware. Verizon Galaxy s7. When I installed v2, over the original version, I followed OP steps exactly, just like when I installed the original version. Everything appeared to load fine but when it came to the setup screen, saying my phone was activated, and gave me my phone number, it would sit there for a sec, and then the screen would go blank, and send me back to the lock screen. I would have to put in my pattern each time instead of my print, because it said the phone had been restarted. I was unable to get past that point to reflash the Rom. The only option I could find was to Odin back to stock. I downloaded all the proper files from a guide on this site, but each time I tried to start the flash it would give an authorization error after working for a few seconds, in odin. After doing more research I discovered that error is usually caused when trying to flash an older firmware. The firmware on this sites was older than what I had on my phone, and I couldn't find a download of the most recent firmware. I discovered after that samsung/Verizon has an upgrade/recovery tool on their site. I was able to restore stock with that tool. Just a heads up if others have the same problem, I can't post in original thread because I haven't posted enough. Thanks for the Rom, I'll try to flash it again later. The original version was awesome.
Repair assistant for Verizon Galaxy S7, this is a windows app. http://support-us.samsung.com/VerizonSoftwareUpdateWin
This ROM blew the stock rom away. So much faster and I can't even explain how awesome the battery life is. http://forum.xda-developers.com/ver...t/stang5litre-edition-5-0-s7e-rom-s7-t3453441
That's not a brick then. Or maybe considered a soft brick I dunno. Brick is when it's unrecoverable. I could be wrong though.
Sent from my SM-G930V using XDA-Developers mobile app
V2 was repaired so it didn't get stuck on the setup and lock screen. I was able to install it. I have no data now. The 4g signal is there but it's not lit up. I've tried resetting my phone, I've tried turning data off and on in multiple locations. This ROM is G935VVRU2APE1, but my phone's baseband is G930VVRU4API3. Could that be the problem? Is there a fix? Or will I have to go back to stock?
I already opened an RMA for the phone but they have no stock so I figured I'll take another shot at it.
The short version is that my gf messed up and updated the system while transferring her data from her old phone with the tapNgo thing.
I've done multiple facory resets, downloaded the rom from ZTE support, put it on SD, flashed it from recovery and deleted cache and nothing helps.
I don't have the exact error log anymore since I don't have the phone with me now but it reads something along the lines of
loading /proc/devices/audio/sound------ cannot find file/directory.
I looked it up and after a lot of Googling it seems like the symlink to the actual driver folder is missing and I have no idea why.
Does anyone know if i can fix this with an ADB shell?
Alternatively, I tried to follow some of the many guides out there to put the phone in EDL mode and relfash it with XiamiFlash utility but after trying 3-4 downloads and 900 versions of misflash all I ever get is "reading hello packet... unable to communicate to com4"
Haaaalp please?
*edit* this is pretty much exactly the same as what I'm getting: https://forum.xda-developers.com/android/help/sound-card-detected-t3379736
The problem with the phone is it makes no sounds?
gpz1100 said:
The problem with the phone is it makes no sounds?
Click to expand...
Click to collapse
the sound drivers for the OS is missing completely, no sound no microphone.
The syslog looks like this(this is from another phone its its the exact same problem):
AudioDaemon: Opening sound card state : /proc/asound/card---/state
AudioDaemon: Open /proc/asound/card---/state failed : No such file or directory
AudioDaemon: Sleeping for 100 ms
Strange issue indeed. Which model do you have? Which specific firmware file are you flashing to it?
I would think flashing the full unmodified factory firmware using the stock recovery will wipe the phone completely, including the /data partition.
Everything worked before? Help me understand the order of events. What is tapngo?
While in the midst of transferring information to or from the phone, a software update appeared and she accepted/installed it?
Its the A2017U model.
I had tried the 1.1.0 B15 firmware from SD card as well as the 1.0.0 B29 older firmware.
Right now its on B17 Nougat 7.1.1, the phone runs and works perfectly just has no audio hardware.
I wasn't there for the exact procedure but basically she powered it on, it asked for sim, she inserted that, tapped the "transfer my data" and then held the two phones together to get the NFC process started. That starts the bluetooth transfer process and it takes a really long time where it transfers all data and apps from the old phone.
At this point the phone still made sounds when adjusting the volume etc.
Somewhere in that process the "update available" notification came up and she pressed the option to install it.
After I got home I tried to figure out what is wrong, first i thought the phone wasn't registered on the cellphone network but then after a bit i figured out the audio is the issue, then i did a factory reset both from the phone UI and tried again from recovery mode, both times chose the "erase all data" option but neither time did it help at all.
I don't really know enough about phones but i think its the bootloader/something very early on thats messed up. Either that or the audio chip really just did fry.
My hope was to get the full factory image for everything that you need to install with the EDL mode thing but I can't find any good reliable guides for that.
It's the first thread in the development section.. Stickied even.
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
Get this package - B15-NEW_FULL (Nougat)
I really don't understand zte's numbering scheme. Newer versions get lower numbers. Makes no sense. That's the full firmware except for the fastboot which passes commands. At this point it's a non issue given the issue you're having.
So I don't need to load TWRP on it, I can still keep it just stock with unlocked bootloader?
I tried that miflash thing before, i had it connected un usb download mode but nothing worked for me, I'll try doing this guide when i get home step by step again.
Their firmware numbers is based on numbers and letters 1.0a-z and then 1.1a-z so 1.0z1 is less that 1.1a1
Ok I have an update
Did miflash, nothing changed.
Ulocked bootloader and miflashed the bootloader from the sticky thread.
The phone made the startup sound and audio worked for a few seconds after android started up and then stopped again
*edit*
ok so after it showed signs of life i re-locked the bootloader, and did the OTA updates to 7.1.1 and the audio seems to be working for good now!!
Conclusion seems to be the bootloader was the key to get it working again. Hope this helps others if it comes to it.
So I've been rooting me phone for a while and have managed to never f*** up, till now, and I sincerely hope you guys can help me.
After rooting my S7 a while back, I just recently noticed SuperUser telling me that I didn't have root anymore, so I decided to follow these instructions to re-root my phone:
https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039
I successfully followed all the steps to get root, but when I opened Flashfire it told me I could install a new update while maintaining root, so since my android is at 6.0.1, I did that and it bricked my phone.
On boot it says "Startup Failed - Use the Verizon Software Repair Assistant . . . " and on top it also says "Custom binary blocked by SECURE BOOT." I have tried going into recovery mode and deleting the system cache, but that doesn't do it. So is there any way to get the phone to properly boot while not deleting my data? I was rooting my phone precisely so I could use Titanium Backup again, so I don't have any backups stored anywhere. I have heard that flashing a recovery image with Odin can work, but would that delete my files? Someone please lend me your expertise.
My phone is a Verizon S7.
Fixed
I am surprised that no one responded to me, but what's important is that, miraculously, I managed to un-brick the phone myself without losing any data! What I did was, as my last hope (since Odin wasn't able to flash the stock image, a la the traditional soft-brick fix), decide to follow the on-screen instructions my phone was giving me and to download and run something called the "Verizon Software Repair Assistant," which can be found in the top google results after searching for the quoted name (xda doesn't let me post the link).
After putting my phone into download mode, I plugged it in, ran the software and let it work overnight. Checking on it in the morning, I found my phone, not only completely functional and working, but updated to Android 7.0 (it was 6.0.1 previously before the failed Flashfire OTA update) and still holding all of my data intact.
So, the interesting thing that I learned is that flashing to stock via Odin to fix a soft-bricked phone should not be the default resolution for potentially most people, as the carrier's default (in my case, Verizon's) repair utility managed to completely fix my phone without any side effects or data loss.
Is there anyone who could chime in on why the Repair Utility did not wipe my phone's memory, even though it warned it would?
**Note**
Verizon links to the Windows version of the repair assistant on their site, but to get the Mac version (which I used), the only way you can get it is by changing the end of the url they mention within the thread from "Win" to "Mac."
Pleased you managed to fix it, and thanks for posting the method for others
As for replies, if you stick around XDA you'll see replies can take days sometimes, patience is the key here
*Detection* said:
Pleased you managed to fix it, and thanks for posting the method for others
As for replies, if you stick around XDA you'll see replies can take days sometimes, patience is the key here
Click to expand...
Click to collapse
I guess I am not acquainted with this forum enough then, thanks!
Most likely the cause of the fault would be updating via FlashFire and keeping root. When the update was flashed, it most likely flashed the stock kernel and patched it for root, which is not a compatible root for our devices. Flashing the root kernel with Odin probably would have made the phone boot normally.
I have an SAMSUNG s8 SM-G950F which I purchased threw Amazon as new from Italy, I live in the UK.
I decided to try rooting it Following these steps
1st of all I tried using Odin3.V3.10.6 and using CF-Auto-Root-dreamlte-dreamltexx-smg950f.tar.md5
Al this seemed to do was factory reset my phone it still worked fine but was not rooted.
so I tried the method below, from that site, wont let me post links so took the . out
galaxys8root com galaxy-s8-root how-to-root-galaxy-s8-or-s8-plus-exynos
When it game time to to do the 2nd key combination (step11) for the twrp, to load the boot loader i missed it, and my phone was stuck, at boot screen and would do nothing, i tired to use Odin to write the file again it never happened.
I did some more goggling saw that web site is out of date and there was a new version of twrp, downloaded twrp-3.2.1-0-dreamlte.img.tar and tried using odin to flash that, still was not having it, still stuck at the screen. Figured out how to get my phone back into usb upload mode and tried again, and then i kept getting the message that their was no P part partition and it failed.
Tried this a few times did some more goggling, saw the thing about doing it letting it fail, reboot the phone and do it straight away this did not work with the twrp-3.2.1-0-dreamlte.img.tar, but did work with CF-Auto-Root-dreamlte-dreamltexx-smg950f.tar.md5 file.
This let my phone boot again, and was rooted, but this caused me issues with running apps and I saw there was no way to hide the cf auto root so decided to just reset my phone.
This worked but now my phone fails the Safety test and i can not use apps that need it....
So was wondering if any one could advise me what my best course of action is, can i put my phone back to stock some how so it will pass the saftynet again or do I need to try the twrp so i can use magika and hide the fact its rooted?
Thanks in advance, included some screen shots from the software screen in case it helps..