I don't know where to post this, I'm coming here all panicked and retarded, so I'm apologizing in advance.
I literally bought my Galaxy S 4G from WIND (Canada) this morning. From what I understood, upgrading the OS was dangerous, all I wanted to do was root... I followed this guide: ht tp ://w ww.gal axyforum s.ne t/forum/off-topic-forum/5053-rooting-tutorial-here-posted-permission-t-mobile-galaxy-s-4g-gingerbread.html (remove spaces)
which I found in a post on these forums. Someone who also was on WIND said it worked fine for them... They were rooted. I foolishly tried it, everything seemed FINE. When I load CWM it can't mount my SD card. I don't know what to do, it's stuck in T-Mobile boot screen loop if I try to exit.. I literally just stopped crying. My dad is going to KILL me if he finds out I ****ed up the new phone I just bought HOURS ago. I don't know what the **** to do, I don't know what's wrong. I need help, please. Anybody know what I can do? I don't care about rooting, I just need my device to work. Please, someone, anyone with any idea, what should I do? I can get back into download mode, and CWM. Is there anything I can do there? There's a recovery guide pinned but it says it's for the T-Mobile version, which I read is the same, can I use that to fix my phone?
This is my first Android device, I've never owned one before. I don't know ****, I shouldn't have tried anything... I just got cocky and made a mistake. I'm usually very good with this kind of stuff. Please someone tell me if there's something I can do to fix this, please!
I'm sorry if I sound stupid, I'm trying not to, I'm just really panicky and stressed right now.
I've tried searching through the forums - I still am searching through them, I'm sorry if I missed a post that can help me.
EDIT: I found someone who is also stuck in a boot loop... He seems to have SD Card issues as well, but doesn't speak English very well, so I don't thing he was able to communicate what his issue was...
Quote:
Originally Posted by GMK63
.......(---------THAT WHAT I FOLLOWED .
But I did the first part and They said i should get the stuff I store on my SD Card to pull out a file (``12) In CWM, use your volume up/down positions to navigate, scroll down to "Install Zip From SDcard". Select with a click of the power button. Navigate to where you put sms-T959V-KJ6-v0.1.1-rc1-unsigned-update.zip (in the root of your SDcard) and select with the power button. Confirm you want to install.
``)
but it doesn't give me the option to go get it on my SDcard and Now my Phone just turns on and off with the samsung galaxy S logo plus T-mobile exclusive logo . The only possitive thing about all the damage is that I can still put my phone on dowload mode and I just think if someone knows how to get my phone back to it state they will need me to put it on download mode.
Thank you in advance for your Help, for replying and offering to help.
I appriciate it. My phone is Mobillicity carrier just like wind .[/B]
Then, user bhundven replies to him saying:
Ok, this is really simple. I've explained it in quite a few threads in the Galaxy S 4G forums in General, Q&A, and the Dev forum. I'm going to explain this, but in a way to be more general. So I'm being verbose in case anyone else with a T959W happens to run across this and has not tried anything yet.
Again, I'm not good with windows at all, and I prefer it that way.
If you're on windows, check out our wiki:
http://forum.xda-developers.com/wiki...xy_S/SGH-T959V
There is tons of help there for setting up heimdall on windows with all the right drivers and such.
Once you have heimdall setup get AntonX's latest cwm zip for his kernel.
This kernel is a BML kernel, and this guide I am giving you right now will help you get cm9 installed which is an MTD kernel. You can find out more about BML vs. MTD here.
Once you have downloaded AntonX's kernel, extract the zImage from it and open up the terminal/cmd prompt and navigate to the directory you extracted the zImage to.
Put your phone into Download Mode and type the following in the command prompt:
Code:
heimdall flash --kernel zImage
The heimdall program will flash this kernel+initramfs to the kernel partition and reboot the phone. Do not unplug the usb cable until you see the "Galaxy S" screen. When you see that screen, unplug the usb cable and remove the battery from the back.
Assuming you downloaded CM9 and put it on your sdcard already, you can get into recovery by holding the vol+ and vol-, then pressing the power button to turn the phone on. When you see the "Galaxy S" screen, let go of the buttons, and you should be in the recovery now.
This is where things get a little tricky. If you have not tried to do anything to your phone yet. This would be a great time to use the "Backup and Recovery" menu on CWM. Do a full backup.
The "assert 7" error that the previous person got was because the cwm install script (the updater-script) checks the already installed /system/build.prop's data against the "to be installed" build.prop to verify this rom can be installed. If it doesn't exist, then it moves forward.
So the first order of business is to wipe the /system partition. Go to "Mounts and Storage" and format the system partition.
Now go back to the main screen and do "Factory Reset/Wipe Data".
Now go "Install zip from sdcard" -> "choose zip from sdcard" -> and use the volume keys to select the zip file.
After the rom is installed, navigate back to the main screen and "Reboot the system now" if it doesn't reboot by itself.
When the phone reboots, because it is going from BML to MTD, it obviously can't just install the files to what would be an MTD partition if the kernel knows nothing about MTD. So it boots into the newly installed MTD kernel and continues the installation, which in the end will also reboot again.
The first boot is very slow. It is building a cache of all the pre-installed system applications. Let it sit for a while. I know it's tempting to go play with your phone right away, but resist if you can.
The next CM9 release will be on a different kernel, and albeit a much better rom.
I will also be adding OTA Asserts for SGH-T959W so that you will not have to wipe /system before installing the rom, but I do that still just for good measure. But this also means that your phone will work properly with the google play store.
If this still does not work, please let me know what went wrong and I will be happy to assist!
-Bryan
Is what Bryan is saying my solution? I don't think he understood the SD Card mount issue. Does anyone know how to fix that? I really hope to hear from you guys ASAP before my dad catches on... Please. I really need help. I'll search more in the morning, it's 1 AM here.
Okay well first of all.. GET A GRIP OF YOUR SELF
*slaps twice across the face
This phone is unbrickable so can you get in to download mode? (power off phone then when it's off hold the volume up and down buttons at the same time, while holding them down connect your phone to a usb cable)
A green android digging thing should show on your screen. Tell me when you get this far.
Sent from my HTC VLE_U using xda app-developers app
As a matter of fact, you don't entirely need a download mode screen to recover your device too. I've gotten to a pixelized colorful screen and thought my phone was done for, but Odin/Heimdall still recognized it, so I was able to recover my phone.
Calm down and as long as your phone can still be detected on your computer, you will be fine. Odin or Heimdall should be able to show that he device was "added" when you plug it in.
bkoon1218 said:
As a matter of fact, you don't entirely need a download mode screen to recover your device too. I've gotten to a pixelized colorful screen and thought my phone was done for, but Odin/Heimdall still recognized it, so I was able to recover my phone.
Calm down and as long as your phone can still be detected on your computer, you will be fine. Odin or Heimdall should be able to show that he device was "added" when you plug it in.
Click to expand...
Click to collapse
That's true, just make sure you have the drivers installed for the phone first and for the purpose of my method of recovery download Odin. If you did everything correctly you'll see a green light in Odin under recognized devices once you're in download mode
Sent from my HTC VLE_U using xda app-developers app
lonoguge said:
Okay well first of all.. GET A GRIP OF YOUR SELF
*slaps twice across the face
This phone is unbrickable so can you get in to download mode? (power off phone then when it's off hold the volume up and down buttons at the same time, while holding them down connect your phone to a usb cable)
A green android digging thing should show on your screen. Tell me when you get this far.
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Thanks for the slaps, I needed them!
Yes! I think I am still able to get into download mode, atleast I was able to last night (After the loop issue). Also, I formatted (factory reset option or something?) my settings when I was in CWM last night assuming that would change it back to the way it was, or atleast fix the SD mount problem..I hope this doesn't cause any issues.
What should I do when I'm in download mode?
bkoon1218 said:
As a matter of fact, you don't entirely need a download mode screen to recover your device too. I've gotten to a pixelized colorful screen and thought my phone was done for, but Odin/Heimdall still recognized it, so I was able to recover my phone.
Calm down and as long as your phone can still be detected on your computer, you will be fine. Odin or Heimdall should be able to show that he device was "added" when you plug it in.
Click to expand...
Click to collapse
That's great news! It's nice to hear that someone who's phone was also messed was able to repair it.
lonoguge said:
That's true, *just make sure you have the drivers installed for the phone first and for the purpose of my method of recovery download Odin. *If you did everything correctly you'll see a green light in Odin under recognized devices once you're in download mode
Click to expand...
Click to collapse
Where can I get these drivers? Should I download the latest version of Odin?
I'll try this as soon as I get back from taking my little sister to school.
I just want to say again, this is the SGH-T959W from WIND in Canada. It's apparently the same hardware as the SGS4G from T-Mobile, just different software. I hope this isn't a problem.
Thank you both for replying so soon. After tossing and turning in bed for the last 5 hours, barely getting any sleep, it's such a relief to read these posts!
Obviously you didn't read too much if you bought the phone and tried to mess with it the same day. You would have seen if you went to the 2nd page of here and actually read something like this, http://forum.xda-developers.com/showthread.php?t=1552119 where I clearly say, it is it different, you will get boot looped, I am working on a package to fix it, and for anyone on a wind phone to hold on and wait.
I don't have time to try and help and fix every single wind phone in the world because people get too impatient and start flashing everything in the world from the first post they read. Odin and Heimdall fail at certain parts of flashing this phone. I am trying to give the Heimdall creator as much as I can to help fix this, so everyone telling to flash this or that package, it's not going to work, it will fail. I have verified this 100 times with Heimdall.
I can't put together a 1click package that fails flashing, that's why people are ending up in this position in the first place.
I can get your phone fixed but not right this second. There is no permanant damage done, and the less you just keep flashing random stuff, the more likely the chance I can help you fix it, but I'm busy, I run my own business and my paying customers come first as does my mortgage and bills before spending an hour teamviewed into someones pc to fix this.
So hang tight, I will try later to get this fixed, it's not screwed, quit flashing anything you find.
Past what getochkn just said (and please do ignore the "advice" given by people who don't experience with a T-959W), next time you see a "helpful" post on some site that starts off "get this from [the original source]" -- please, please take the time to read the original source.
Secondly, just because your phone has the a similar "trade name" as another phone doesn't mean they are even close to the same inside. Even the model numbers don't mean much. Firmware from a T-959 generally won't work on a T-959V, and, as you have found out, T-969V firmware can make a T-959W a nice paperweight for a while.
Thirdly, I just don't "get" why people even consider flashing their phone on the first day they own it, before they have any idea what it came with and what it can do, not to mention voiding their warranty before even the buyer's remorse period has expired.
While you're waiting for someone to bail you out, you might want to take the time to download Java, the Microsoft C++ executables, and a full version of Heimdall.
getochkn said:
Obviously you didn't read too much if you bought the phone and tried to mess with it the same day. You would have seen if you went to the 2nd page of here and actually read something like this, http://forum.xda-developers.com/showthread.php?t=1552119 where I clearly say, it is it different, you will get boot looped, I am working on a package to fix it, and for anyone on a wind phone to hold on and wait.
I don't have time to try and help and fix every single wind phone in the world because people get too impatient and start flashing everything in the world from the first post they read. Odin and Heimdall fail at certain parts of flashing this phone. I am trying to give the Heimdall creator as much as I can to help fix this, so everyone telling to flash this or that package, it's not going to work, it will fail. I have verified this 100 times with Heimdall.
I can't put together a 1click package that fails flashing, that's why people are ending up in this position in the first place.
I can get your phone fixed but not right this second. There is no permanant damage done, and the less you just keep flashing random stuff, the more likely the chance I can help you fix it, but I'm busy, I run my own business and my paying customers come first as does my mortgage and bills before spending an hour teamviewed into someones pc to fix this.
So hang tight, I will try later to get this fixed, it's not screwed, quit flashing anything you find.
Click to expand...
Click to collapse
THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU!
I really didn't read enough, big mistake, I was just really cocky because I've modded almost every device I own (Wii, PSP, PS3, PS2 various and iDevices [mine, and friends]). Of course, they're all different (Not saying it's all the same thing! ), I just felt very confident because I've never had issues with anything before. At least this is a good learning experience, I've really been put in my pace. I always felt that bricking was something that happened to other people, it doesn't happen to me. I know that sounds stupid, but idk, that's just how I felt. I physically feel sick over this 'whole ordeal (Seriously), I'm such an idiot. >.<'
Thanks for the warning, I won't flash anything! I'm so relieved to hear that there's no permanent damage done, and to be able to speak to someone who's familiar with this specific problem and this specific model of the SGS4G, AND is willing to help me!
Do you know when you'll be able to help me? Of course, take your time, I completely understand that you have other stuff going on, I'm just wondering to see if I can maybe think of some cover up so my dad doesn't find out.
Also, I have a 14 day warranty, is it void now even though the root didn't work? I'm assuming it is.
Edit: Yup, if what jeffsf says is true, it's void.
jeffsf said:
Past what getochkn just said (and please do ignore the "advice" given by people who don't experience with a T-959W), next time you see a "helpful" post on some site that starts off "get this from [the original source]" -- please, please take the time to read the original source.
Secondly, just because your phone has the a similar "trade name" as another phone doesn't mean they are even close to the same inside. Even the model numbers don't mean much. Firmware from a T-959 generally won't work on a T-959V, and, as you have found out, T-969V firmware can make a T-959W a nice paperweight for a while.
Thirdly, I just don't "get" why people even consider flashing their phone on the first day they own it, before they have any idea what it came with and what it can do, not to mention voiding their warranty before even the buyer's remorse period has expired.
While you're waiting for someone to bail you out, you might want to take the time to download Java, the Microsoft C++ executables, and a full version of Heimdall.
Click to expand...
Click to collapse
I'm just very impatient sometimes. I really do enjoy doing this kind of stuff, it's fun for me. I just got really excited and wasn't thinking straight and just went out and tried rooting it. I've wanted an Android for a while now, and have always planned to root it to unlock it's full potential. I've never modded anything else day 1 (and never will again), this is the first time I've done this. I feel terrible about it.
Will do, thanks for helping, jeffsf.
If your still under 14 days return it with a stupid I don't know what happened look. If its stuck just on the tmob screen they most likely will never know what you did. Your other choice is to be a man and own up to it. Tell your dad and take your lumps. That choice is yours. Give it serious thought before you choose as it might define what type of person you end up becoming.
hechoen said:
If your still under 14 days return it with a stupid I don't know what happened look. If its stuck just on the tmob screen they most likely will never know what you did. Your other choice is to be a man and own up to it. Tell your dad and take your lumps. That choice is yours. Give it serious thought before you choose as it might define what type of person you end up becoming.
Click to expand...
Click to collapse
I feel like they might know. I'm willing to try it as a last resort, I'd like to give getochkn a shot first.
I'll tell my dad what happened after it's fixed. I just can't deal with him stressing me out about it more than I already am.
I will have a package probably tomorrow that will provide as detailed instructions as I can.
getochkn said:
I will have a package probably tomorrow that will provide as detailed instructions as I can.
Click to expand...
Click to collapse
Oh, wow! That's much sooner than I was expecting! Thanks for taking the time to do this for me, it really means a lot. Thank you so much getochkn!
Package and instructions here.
http://forum.xda-developers.com/showthread.php?t=1956025
getochkn said:
Package and instructions here.
http://forum.xda-developers.com/showthread.php?t=1956025
Click to expand...
Click to collapse
Thank you so much getochkn!
I read all the instructions before attempting this. But, I have a problem. Heimdall failed to flash. It said something about failing to retrieve the PIT or something? So, I tried again. Didn't work. So, I restarted my computer, and my phone.
Phone doesn't go into download mode, instead, I end up on a screen saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
What should I do?
BagelBreath said:
Thank you so much getochkn!
I read all the instructions before attempting this. But, I have a problem. Heimdall failed to flash. It said something about failing to retrieve the PIT or something? So, I tried again. Didn't work. So, I restarted my computer, and my phone.
Phone doesn't go into download mode, instead, I end up on a screen saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
What should I do?
Click to expand...
Click to collapse
That firmware screen should detect as download mode still in Heimdall. I have gotten that and reflashed from Heimdall before. Not sure why it's trying to download the pit, it should only do that when you tell it to download pit. Flashing shouldn't trigger that. See if Heimdall will detect it in that firmware recovery mode and I guess try again, otherwise your phone is really borked.
getochkn said:
That firmware screen should detect as download mode still in Heimdall. I have gotten that and reflashed from Heimdall before. Not sure why it's trying to download the pit, it should only do that when you tell it to download pit. Flashing shouldn't trigger that. See if Heimdall will detect it in that firmware recovery mode and I guess try again, otherwise your phone is really borked.
Click to expand...
Click to collapse
Thank you for the quick reply!
It worked! I really can't thank you enough! Thanks again for taking the time to do this!
I think it may have said "Uploading Pit" because it said it again this time, but it didn't encounter a problem when it did that.
I know I have 3 choices, the one I would like to choose is ICS. Would mind pointing me in the direction of an ICS ROM that's compatible with my device? I'm afraid to use something that may not work and mess up my phone again.
EDIT: Actually, I think I'll just stick with this. I just installed the twist kernal and the modem, everything works, I'm rooted and have recovery. I'd rather not mess with it until I'm more experienced with droids.
Thanks again everyone, especially you getochkn! I'm so relieved that my phone is working again! My dad didn't notice that I wasn't using the new phone I got, so I didn't have to cover up or anything.
First of all, sorry if I am posting this in the wrong thread or wrong area.
I'm seriously depressed and deprived of sleep because I finally rooted my phone and everything went wrong.
Yeah, I fell in with that crowd. Shame on me, i know ,_,
Samsung Galaxy Note 3 SM-N900W8 is the victim. I downloaded CF AUTO ROOT HLTECAN HLTEUB SMN900W8 which, apparently, should have had no problem. Used Odin 3.07 on my laptop and the process was smooth and quick. Buuuut of course my phone got mostly wiped (no surprise here, totally worth the root). Along with that wipe came the rage of Google and Samsung.. don't know why but most apps just force close when I try to open them.
Long-story short I need to regain access to my Google account, my messages (so I can, you know, message my grandmother so she can pick me up at the university) and the ability to have a functional good phone.
I've learned my lesson, I'm leaving this rooting stuff to the more apt. However I need guidance on how to what I believe is called "flash" the system back into having all the permissions it used to have. Not sure what I'm talking about any more.
If it is possible to keep the root and somehow fix the problem (regain access to basic services such as messages and play store) that'd be nice. But really, I just wanna travel back in time and forget this ever happened so late at night that it's almost morning and my feelings are extra hurt.
Hello Dear ,
Its ok just re install the official rom for ur device n900w8 after that just do a full for ur device through stock recovery then install twrp through odin in AP tap from this link
https://twrp.me/devices/samsunggalaxynote3canada.html
After that boot ur phone to custom recovery then install supersu from this link
https://download.chainfire.eu/743/SuperSU/BETA-SuperSU-v2.52.zip
That's all for rooting ur device mate
Thank You ,
Thanks for the help! But I'm still a bit lost. I did as you suggested and found the 5.0 stock firmware, which I am currently downloading. I will open Odin, plug in my phone, put the firmware file in the AP slot and install it from the download screen on my phone. Same process as the rooting that failed earlier.
However, I don't get the TWRP part.
"after that just do a full for ur device through stock recovery then install twrp through odin in AP tap from this link"
Is that step necessary, or is it just in case I want to try rooting my device again? Also, in the list you provided doesn't seem to be 5.0/lollipop for the phone. But then again, I'm not entirely sure how all that works.
Thanks again!
Installing the Stock firmware did not work. Once the phone boots, everything stops working unexpectedly.
Oh well, I guess it's time to take it to a store ,_,
Thanks anyways!
I am in utter shock. For some strange reason, factory reset worked and my phonne is ok. Not sure how... but it actually worked!
Nice to hear that mate congrats then
I'm new to the XDA Forums and even forums in general so if I speak out of place or anything like that I apologize ahead of time. So anyway, where do I start? I'll try to give you the short version. So I bought an LG Stylo 2(model: LG K540) through Cricket the day they came out. It was $170 phone. On the second day of using my new phone I got the bright idea that I'd try and root it BY MYSELF. I knew better but for some reason I had this false burst of confidence & thought I had everything under control. Well, thanks to Kingroot that burst of confidence didn't last long and there I was with a 2 day old phone BRICKED. Reason I never posted on the forums is because I've got a buddy who , in my eyes, knows everything there is to know about Android and thats who I'd normally go to when I wanted to root a phone so he's who I immediately turned to but even he couldn't figure it out. He couldn't help me unless we had the stock firmware or someone with the exact same phone and according to him we could some how use a backup of that phone to fix mine. Cricket just wanted to sell me another phone even though I was standing there with a 2 day old phone and LG just wants me to send the phone in to them, which I have no desire to do. I've searched all over the internet trying to locate the firmware because even I can fix the phone if I had that but nothing. Had hoped by now LG would have released the firmware but at this point who knows when that'll happen. I'd even pay for it at this point. Anyway, just thought I'd give the forum a shot on the off chance someone might be able to help me or point me in the right direction. Oh and if you were wondering what the phone does now, when I turn it on the LG logo appears like it should but then right as it appears you see a message in red lettering that says: BOOT VERIFICATION FAIL!!- CAUSE: MISMATCH_SIG_LEN And it just loops this over & over until you pull the battery out. Please someone help me!
send to lg said stop working no luck with tihs hard brick
Source code to rom¿?
I ran into basically the same situation as you. I'm currently downloading Android open source project on to a fresh install Ubuntu 16.04. I am currently in the middle of running sync.
I'm curious if there is anybody out there who would be willing to give a few pointers, on compiling the ROM from LG open source code. They told me I had to use it in the readme.txt.
Im a noob with fair knowledge of modding and stylo not stylo 2. There's no way to say for sure if this will work but on lg mm on h631 u need to unlock dev option in settings 1st. Make sure to check off oem unlock and usb debugging. Connect to pc and you will get a popup or 2, one will ask to allow pc to connect to phone, the second is to allow usb debugging. After you allow both, open cmd in your adb fastboot folder. Type " adb reboot bootloader." should reboot the phone to bootloader/fastboot mode. Then you type " fastboot oem unlock." you will see sending.. Once sending is done type " fastboot reboot." when the phone restart you should see bootloader unlocked on splash screen. Then i rooted with kingroot. Then use rashr to flash twrp. Then used twrp to flash supersu to get rid of kingroot.. My h631 now in business and i just started working on a port for lg ux 5.0. This is the guild i use for a better idea http://forum.xda-developers.com/lg-g-stylo/how-to/guide-lg-g-stylo-how-to-root-t-mobile-6-t3333916. You might need lgflashtool and kdz to unbrick..
NO NEED to beg.
I don't know very much but I know $$$ talks and since no one save the few who suggested contacting lg wants to help, Ill try. At the moment I am efforting a solution via the Chinese. I expect to have a working copy in the next 48hrs. when I do, we can arrange for you to get access to the mega.nz cloud and get urs.
say a prayer......
Francis
Hello Sir, I ran into same problem trying to root. If you can, can you please send me a link so that i can use my phone again. Thank You it will be greatly appreciated
can some one help me. i cannot use adb to unbrick
Please send me the link
facorbin said:
I don't know very much but I know $$$ talks and since no one save the few who suggested contacting lg wants to help, Ill try. At the moment I am efforting a solution via the Chinese. I expect to have a working copy in the next 48hrs. when I do, we can arrange for you to get access to the mega.nz cloud and get urs.
say a prayer......
Francis
Click to expand...
Click to collapse
Hi, can you please send me the link? I need it bad thx
if you cant boot into dlmode then your hard bricked, so find a way to get back to dl mode/recovery
BIN File
Hello, I have a Stylo 2 K540 from cricket, it is having issues with the Wi-Fi, it will not connect to either Wi-Fi or bluetooth, MAC address was set at 02:00:00:00:00 or something like that, I opened the phone and it has humidity sensor active, cleaned the affected area but it seems like it was useless, eventhough I was pretty sure that was not the main problem. I looked for some troubleshooting options and found non of use, firmware is sold for $30 online so it is not an option since I am not certain loading firmware will be of any help. I tried repairing MAC address via Octoplus using other addresses but was useless as well.
I have little to no experience with software on phones, but I like to read and learn. I decided to connect the phone to the computer and "Read full flash" on Octopus, I have created the Bin file, I have a perfectly working phone as well, I was wondering if there is any way to get the KDZ file from the Bin file doing some sort of conversion, or if I could do some sort of fix or workaround with this bin file, I can share it if anybody needs it or if it can be of any use to get the firmware
estebangtz said:
Hello, I have a Stylo 2 K540 from cricket, it is having issues with the Wi-Fi, it will not connect to either Wi-Fi or bluetooth, MAC address was set at 02:00:00:00:00 or something like that, I opened the phone and it has humidity sensor active, cleaned the affected area but it seems like it was useless, eventhough I was pretty sure that was not the main problem. I looked for some troubleshooting options and found non of use, firmware is sold for $30 online so it is not an option since I am not certain loading firmware will be of any help. I tried repairing MAC address via Octoplus using other addresses but was useless as well.
I have little to no experience with software on phones, but I like to read and learn. I decided to connect the phone to the computer and "Read full flash" on Octopus, I have created the Bin file, I have a perfectly working phone as well, I was wondering if there is any way to get the KDZ file from the Bin file doing some sort of conversion, or if I could do some sort of fix or workaround with this bin file, I can share it if anybody needs it or if it can be of any use to get the firmware
Click to expand...
Click to collapse
cna you possible sned me it I might be able too
no longer have the bin file
HERPDERP202 said:
cna you possible sned me it I might be able too
Click to expand...
Click to collapse
I am sad to say my computer stopped working and just got it back today, all my information was lost so I no longer have the bin file
bsimpson1858 said:
I'm new to the XDA Forums and even forums in general so if I speak out of place or anything like that I apologize ahead of time. So anyway, where do I start? I'll try to give you the short version. So I bought an LG Stylo 2(model: LG K540) through Cricket the day they came out. It was $170 phone. On the second day of using my new phone I got the bright idea that I'd try and root it BY MYSELF. I knew better but for some reason I had this false burst of confidence & thought I had everything under control. Well, thanks to Kingroot that burst of confidence didn't last long and there I was with a 2 day old phone BRICKED. Reason I never posted on the forums is because I've got a buddy who , in my eyes, knows everything there is to know about Android and thats who I'd normally go to when I wanted to root a phone so he's who I immediately turned to but even he couldn't figure it out. He couldn't help me unless we had the stock firmware or someone with the exact same phone and according to him we could some how use a backup of that phone to fix mine. Cricket just wanted to sell me another phone even though I was standing there with a 2 day old phone and LG just wants me to send the phone in to them, which I have no desire to do. I've searched all over the internet trying to locate the firmware because even I can fix the phone if I had that but nothing. Had hoped by now LG would have released the firmware but at this point who knows when that'll happen. I'd even pay for it at this point. Anyway, just thought I'd give the forum a shot on the off chance someone might be able to help me or point me in the right direction. Oh and if you were wondering what the phone does now, when I turn it on the LG logo appears like it should but then right as it appears you see a message in red lettering that says: BOOT VERIFICATION FAIL!!- CAUSE: MISMATCH_SIG_LEN And it just loops this over & over until you pull the battery out. Please someone help me!
Click to expand...
Click to collapse
you can go into download mode by pressing volume up key and inserting usb cable .press the volume up until you see download mode a firmware readed by z3x box is available on clamgsm forum you can flash it with z3x box crack .
Not sure if my phone is a lost cause and only good as a door stop. My phone at one stage would only display a screen asking me to plug into smart switch to recover the phone so I tried that but smart switch wasn't happening. I downloaded the latest stock rom and installed it successfully via ODIN but now my phone will not get past the boot logo. I can only get into download mode, Any advise on if I can get my phone working again?
Thanks
Andrew
andrew88 said:
Not sure if my phone is a lost cause and only good as a door stop. My phone at one stage would only display a screen asking me to plug into smart switch to recover the phone so I tried that but smart switch wasn't happening. I downloaded the latest stock rom and installed it successfully via ODIN but now my phone will not get past the boot logo. I can only get into download mode, Any advise on if I can get my phone working again?
Thanks
Andrew
Click to expand...
Click to collapse
Bro, I've been there and this is why I made an account on xda to see if my s6 (G-920F) can be fixed in any way. Yesterday I had the same thing as you when I tried to re-flash the phone with its proper, latest stock-ROM (UK/EE Nougat 7.0). Given how it hadn't worked, the update attempt through Odin screaming a big "FAIL!" at me, I was afraid I had bricked it completely, so I proceeded to re-install TWRP with Odin by putting the phone in download mode. I wiped the phone again with TWRP and now I'm not sure what I have to do as I am stuck with the UK Nougat bootloader and nothing else on it.
Before this whole ordeal I had rooted the phone and unlocked the bootloader following some instructions from a Youtube video and successfully installed a nighty build of LineageOS, which was buggy as **** (couldn't answer calls, use data, use the camera and a ****ton of apps were just not working). Dumbly enough, I thought I could just remove it through a wipe and put something else back on it but oh was I wrong.
Right now I'd just want to get my phone back to working (like you), as I am out of a job and need to be able to take phone calls with a normal, working phone.
Sorry I couldn't be of much help, but yeah maybe a first step towards fixing it would be to flash TWRP recovery on it and through the terminal, see what bootloader version you have with the command "getprop ro.bootloader". At least you will know the version of the broken bootloader you're experiencing difficulties with and *hopefully* an actual dev from the forums will entertain themselves in trying to solve this noobish puzzle we've created for ourselves.
Seriously, if there is a dev ready to board this crazy adventure with us, please help.
My namesake or username is pretty much a clue to what got me into this position.
I wish it was that simple for me mate, I cant access the recovery menu, I've tried flashing various recovery options but cant boot into any of them. I'm certain I could fix the phone if I could get to recovery. I'm now leaning towards it being a hardware fault with my phone. As you have access to recovery I think you may have more luck with your phone.
TerribleChoices said:
Bro, I've been there and this is why I made an account on xda to see if my s6 (G-920F) can be fixed in any way. Yesterday I had the same thing as you when I tried to re-flash the phone with its proper, latest stock-ROM (UK/EE Nougat 7.0). Given how it hadn't worked, the update attempt through Odin screaming a big "FAIL!" at me, I was afraid I had bricked it completely, so I proceeded to re-install TWRP with Odin by putting the phone in download mode. I wiped the phone again with TWRP and now I'm not sure what I have to do as I am stuck with the UK Nougat bootloader and nothing else on it.
Before this whole ordeal I had rooted the phone and unlocked the bootloader following some instructions from a Youtube video and successfully installed a nighty build of LineageOS, which was buggy as **** (couldn't answer calls, use data, use the camera and a ****ton of apps were just not working). Dumbly enough, I thought I could just remove it through a wipe and put something else back on it but oh was I wrong.
Right now I'd just want to get my phone back to working (like you), as I am out of a job and need to be able to take phone calls with a normal, working phone.
Sorry I couldn't be of much help, but yeah maybe a first step towards fixing it would be to flash TWRP recovery on it and through the terminal, see what bootloader version you have with the command "getprop ro.bootloader". At least you will know the version of the broken bootloader you're experiencing difficulties with and *hopefully* an actual dev from the forums will entertain themselves in trying to solve this noobish puzzle we've created for ourselves.
Seriously, if there is a dev ready to board this crazy adventure with us, please help.
My namesake or username is pretty much a clue to what got me into this position.
Click to expand...
Click to collapse
andrew88 said:
I wish it was that simple for me mate, I cant access the recovery menu, I've tried flashing various recovery options but cant boot into any of them. I'm certain I could fix the phone if I could get to recovery. I'm now leaning towards it being a hardware fault with my phone. As you have access to recovery I think you may have more luck with your phone.
Click to expand...
Click to collapse
Oh dear.
Yeah it does sound like something got deeply ****ed up in this case. I had the luck to somehow get past the smart switch error when the phone died of low battery. As I attached it to the charger I quickly boot it into download mode before the screen would become a bootloop again and that's where I was able to reinstall the latest version of TWRP recovery. After that, I was able to flash a stock ROM of Nougat that didn't have a ****ed up bootloader like I had. Specifically the one from this thread: https://forum.xda-developers.com/galaxy-s6/help/device-5-binary-3-s6-sm-g920f-t3706025
by forumber2.
It's the Netherlands stock-ROM. Not sure if you're from the US and the carrier would be wrong with that CSC, but it was a good bet for me. I got my phone back to working normally now.
Worst case scenario I'd say see if you have a phone repair shop nearby and ask them an opinion on what could be wrong. I'm just an amateur like you.
Still, I wish you the best of luck with it. Maybe there's still some hope. :/