Related
My Vibrant is telling me that T-Mobile has kindly sent me an update. I think it must be the GPS fix. It is rather persistent in that it won't let me choose when to install it. It will only allow me to delay for at most a day. This is quite annoying as I am preparing for a trip and really don't want to mess around with my phone right now.
I am running Vibrant9. Do I want to install this update? Is it gonna break anything? Thanks!
JJMT said:
My Vibrant is telling me that T-Mobile has kindly sent me an update. I think it must be the GPS fix. It is rather persistent in that it won't let me choose when to install it. It will only allow me to delay for at most a day. This is quite annoying as I am preparing for a trip and really don't want to mess around with my phone right now.
I am running Vibrant9. Do I want to install this update? Is it gonna break anything? Thanks!
Click to expand...
Click to collapse
Shouldn't break anything. Most are still waiting for the update. Personally I was impatient and flashed it through ODIN last night.
OK. I accepted the update. Phone is now stuck on "Vibrant" at reboot. Sigh. Proceeding to trying to restore ROM.
JJMT said:
OK. I accepted the update. Phone is now stuck on "Vibrant" at reboot. Sigh. Proceeding to trying to restore ROM.
Click to expand...
Click to collapse
Go to the Development section that are a few threads about this. I looks like anyone with a lag fix, or GPS fix (from JI2) where having this issue, plus I have seen stock people having it too.
Or you can go read my blog post here. the post tells the steps I took to get back the JFD, but you could flash JI6 instead.
you will need to flash JI6 with ODIN to restore, you can not just do a nandroid restore, it is an issue with the kernel and nandroid does not restore/backup the kernel.
*facepalm*@Samsung
http://forum.xda-developers.com/showthread.php?t=803492
Anderdroid said:
*facepalm*@Samsung
Click to expand...
Click to collapse
It's not Samsung or T-Mobile.. its that the OP performed tweaks so the ROM wasn't a 100.00% version of Stock. Tweaks including lag fixes, GPS fix, etc can cause this.
Personally, I don't know why if you're performing tweaks on your phone and are on a stock ROM. If you're going to tweak your phone, go the full way and tweak everything.
This is why t-mobile had the G2 nand locked..... so this type of user error won't cost them millions, replacing phones that the user messed up with blind stupidity.... that's only for the ones under warranty, you can still call in a lost phone and get replacements..
dan0zone said:
This is why t-mobile had the G2 nand locked..... so this type of user error won't cost them millions, replacing phones that the user messed up with blind stupidity.... that's only for the ones under warranty, you can still call in a lost phone and get replacements..
Click to expand...
Click to collapse
So now instead, they get flooded with returns because the phone isn't what people expected.
zephiK said:
It's not Samsung or T-Mobile.. its that the OP performed tweaks so the ROM wasn't a 100.00% version of Stock. Tweaks including lag fixes, GPS fix, etc can cause this.
Personally, I don't know why if you're performing tweaks on your phone and are on a stock ROM. If you're going to tweak your phone, go the full way and tweak everything.
Click to expand...
Click to collapse
That's not true, it is Samsung/T-Mobile fault. I know 3 people with 100% stock, unrooted, vibrants, 2 of them got stuck when they updated. the t-mobile forums filled with stock users with their phone stuck at the vibrant screen as well.
camalot said:
That's not true, it is Samsung/T-Mobile fault. I know 3 people with 100% stock, unrooted, vibrants, 2 of them got stuck when they updated. the t-mobile forums filled with stock users with their phone stuck at the vibrant screen as well.
Click to expand...
Click to collapse
And what are the chances of this?
Everybody lies.. especially when they're desperate and unwilling to accept the fact that they modified their phone. I don't see any reason why they wouldn't lie to T-Mobile and say that they didn't modify their phones if its "bricked." Because it is not bricked, all it takes is download mode and Odin. There are threads out there that break down on how to use Odin, it's not that difficult to do.
This is why I don't endorse "One Click" anything unless it is a long process. Sure, it makes everything easier but it makes people not think about what they're doing before they do it. Before one clicking, rooting was so simple, put something on your internal sd and boot into recovery and hit reinstall packages. If something like that is too difficult then they shouldn't be doing any modifications in the first place unless they understanding what they're doing.
The T-Mobile forum is not a valid source because there is no concrete proof that they didn't root their phone and modified something. Even rooting and removing bloatware then removing access to root would cause this.
Edit: Looking at the OP's recent posts.. he did indeed run a custom ROM but has possibly did some tweaking after reverting back to stock?
zephiK said:
And what are the chances of this?
Everybody lies.. especially when they're desperate and unwilling to accept the fact that they modified their phone. I don't see any reason why they wouldn't lie to T-Mobile and say that they didn't modify their phones if its "bricked." Because it is not bricked, all it takes is download mode and Odin. There are threads out there that break down on how to use Odin, it's not that difficult to do.
This is why I don't endorse "One Click" anything unless it is a long process. Sure, it makes everything easier but it makes people not think about what they're doing before they do it. Before one clicking, rooting was so simple, put something on your internal sd and boot into recovery and hit reinstall packages. If something like that is too difficult then they shouldn't be doing any modifications in the first place unless they understanding what they're doing.
The T-Mobile forum is not a valid source because there is no concrete proof that they didn't root their phone and modified something. Even rooting and removing bloatware then removing access to root would cause this.
Edit: Looking at the OP's recent posts.. he did indeed run a custom ROM but has possibly did some tweaking after reverting back to stock?
Click to expand...
Click to collapse
Well, I know the 2 people that updated stock and got stuck at the vibrant screen were 100% stock because they both called me on what they need to do. one came over and I fixed it with ODIN back to stock (JI6) and the other just said he'd call TMO and get a replacement. they dont even know what rooting is, or that there is a site like that that they can get files to do "one click root"
OK. I'm the OP and I'm back. I was traveling today (with a phone flashed back to stock - that's as far as I got before getting kicked out of the hotel). I've now got the ROM restored and I'm where I was before trying to install the update.
My question is this (probably simple): my phone still wants to do the update. How do I make it go away? I can't install it, and I don't want to have to postpone it every day. Is there a cache I can clear or something?
You could just update it through Odin. I'm on stock with root and JAC's oc/uv kernel and the OTA failed but Odin worked perfectly.
Yes, I will try to flash it with odin when I have the time and interest, but for now I have neither, and I just want the phone to stop bugging me. Ideas?
JJMT said:
Yes, I will try to flash it with odin when I have the time and interest, but for now I have neither, and I just want the phone to stop bugging me. Ideas?
Click to expand...
Click to collapse
It will only stop once you are on JI6
camalot said:
It will only stop once you are on JI6
Click to expand...
Click to collapse
OK. I guess I will have to try to push the update through odin. Can someone point me to a link to the files?
I'm kind of irritated by this whole thing. I'm pleased with tmo for pushing the update out, but I mean, really, even Windows allows you to decline to install an update.
http://forum.xda-developers.com/showthread.php?t=798125
chad658eku said:
http://forum.xda-developers.com/showthread.php?t=798125
Click to expand...
Click to collapse
Thanks for the link. It really looks to me that I'm going to need to flash to a stock ROM before flashing JI6. That, as they say, is a bummer.
As I am actually quite content at the moment with Vibrant9, it really seems to me that it would be easier to somehow remove whatever it is on my phone that is requesting that I update. Presumably there is an update.zip file sitting somewhere, that will be copied into sdcard before the updater involves reboot recovery. Any ideas where to look?
I would really rather not do any further flashing until is an official Froyo to flash to.
JWhipple said:
So now instead, they get flooded with returns because the phone isn't what people expected.
Click to expand...
Click to collapse
Flooded with returns by morons who think they are smart.
Hi, I have problems to regiister on my carriers network. My Z Ultra can see all available networks but refuses to connect toany of them. I tried several different ROMS without success. I also took out the SIMcard and put it into an old phone (no smartphone) and with that it connected instamntly. My carrier told me to wait but I´m reaklly fed up with waiting. Does anbybody have a clue what might be the issue here?
magnusaaa said:
Hi, I have problems to regiister on my carriers network. My Z Ultra can see all available networks but refuses to connect toany of them. I tried several different ROMS without success. I also took out the SIMcard and put it into an old phone (no smartphone) and with that it connected instamntly. My carrier told me to wait but I´m reaklly fed up with waiting. Does anbybody have a clue what might be the issue here?
Click to expand...
Click to collapse
Do you have an IMEI number?
Have
I bought this phone recently and i beleive tthat the imei number is on one of the receipts. However could you perhaps tell me a way of finding IMEI without hazzle..? I scarefully start to grasp that this might be an IMEI issue of which i have no clues or experience. I+m fammiliar with adb and rooting though. What is your advice?
magnusaaa said:
I bought this phone recently and i beleive tthat the imei number is on one of the receipts. However could you perhaps tell me a way of finding IMEI without hazzle..? I scarefully start to grasp that this might be an IMEI issue of which i have no clues or experience. I+m fammiliar with adb and rooting though. What is your advice?
Click to expand...
Click to collapse
Open the dialer and enter *#06#. A new window with a bunch of numbers should pop up. If it says "0" or "0000", your IMEI is gone, and we'll take it from there.
Note: Do not post your IMEI here.
Code Zero
OK you are right i surely mesed something up because all i get from that code is a hole bunch of zeros. Would be happy for rfurther advive.
yes
By the way, my platform is ubuntu. So I am familiar with some cli actions.
magnusaaa said:
OK you are right i surely mesed something up because all i get from that code is a hole bunch of zeros. Would be happy for rfurther advive.
Click to expand...
Click to collapse
I see, so i'm assuming that you've been on 290 and then downgraded to 257 or 532? If yes, that's why you've lost your IMEI. You can easily fix this by updating to 290 again, or flash NUT's 532 version in Flashtool.
LordManhattan said:
I see, so i'm assuming that you've been on 290 and then downgraded to 257 or 532? If yes, that's why you've lost your IMEI. You can easily fix this by updating to 290 again, or flash NUT's 532 version in Flashtool.
Click to expand...
Click to collapse
NUTS 532 sounds interesting. Does it have support for init.d and so on?
Can i flash cwm to boot after? My aim is to become on latest stock but rooted. Why? Is because i purchased a sony original miracast device and i would like that to work...
Suggest?
magnusaaa said:
NUTS 532 sounds interesting. Does it have support for init.d and so on?
Can i flash cwm to boot after? My aim is to become on latest stock but rooted. Why? Is because i purchased a sony original miracast device and i would like that to work...
Suggest?
Click to expand...
Click to collapse
Yup, it supports init.d.
It has dual-recovery installed as default, so you can either flash that one and stay fully rooted on 532 (with IMEI), or you can jump straight to 290, but then you'll have to flash it in Flashtool (so you get the latest baseband), and you'll have to root it yourself and install recovery.
Reason
LordManhattan said:
Yup, it supports init.d.
It has dual-recovery installed as default, so you can either flash that one and stay fully rooted on 532 (with IMEI), or you can jump straight to 290, but then you'll have to flash it in Flashtool (so you get the latest baseband), and you'll have to root it yourself and install recovery.
Click to expand...
Click to collapse
I beleive i messed it up while flasshing different roms and so son. But still my main goal right now is to be able to use ther miracast. Do you think it would work on the 532?
magnusaaa said:
I beleive i messed it up while flasshing different roms and so son. But still my main goal right now is to be able to use ther miracast. Do you think it would work on the 532?
Click to expand...
Click to collapse
I don't use Miracast, but i can't see why it shouldn't work? Does it require a special feature on Android 4.3?
Miracast
There has been several issues on miracast. Many people seeem to have failed to get it working. Maybe Sony has fixed that in Kitkat i dont knowe. But thge 532 is jellybean right?
LordManhattan said:
I don't use Miracast, but i can't see why it shouldn't work? Does it require a special feature on Android 4.3?
Click to expand...
Click to collapse
Ok i gather that you recommend that i flash the 532 ftf..? Using flashtool in flash mode? And where can i find that ftf?
magnusaaa said:
Ok i gather that you recommend that i flash the 532 ftf..? Using flashtool in flash mode? And where can i find that ftf?
Click to expand...
Click to collapse
The NUT 532 ROM is a Recovery file, so just flash it in recovery like you usually do, and you should in theory get your IMEI back. If not, flash a stock 290 FTF in Flashtool.
I have Miracast working on .136
It never worked on prior firmware - don't know if that was the tv's fault or the phone.
Sitting duck again
I tried flashing the NUT 532 and all seemed ok until i power the device up. I get thousands of force close to the system ui. Practically rendered my ZU useless. Does anybody recognize this issue? I tried a factory reset as my hands had to dance in order to reset it. Right now i dont know what fw oi am on but as i said the phone is uselesss.
magnusaaa said:
I tried flashing the NUT 532 and all seemed ok until i power the device up. I get thousands of force close to the system ui. Practically rendered my ZU useless. Does anybody recognize this issue? I tried a factory reset as my hands had to dance in order to reset it. Right now i dont know what fw oi am on but as i said the phone is uselesss.
Click to expand...
Click to collapse
Did you do a full wipe after flashing? If not, you should've done that. Also, no reason to panic. I understand why you might be, and i've been in much worse situations than this a couple of times, but it's nothing we can't solve. It takes some effort to hard brick a Sony. It just depends on how far you're willing to go to get it up and running. The easiest way would be to just flash 290 in Flashtool and be done with it. That way you'll have a fully funtional phone again with IMEI, and you can do the rooting later on when you have a system that's actually functioning correctly. Get your stress levels down again and root and what not when you have full control over your phone again
I'm in Norway btw, so since we're in the same time zone, i can help you out tomorrow after school/work if you need it.
LordManhattan said:
Did you do a full wipe after flashing? If not, you should've done that. Also, no reason to panic. I understand why you might be, and i've been in much worse situations than this a couple of times, but it's nothing we can't solve. It takes some effort to hard brick a Sony. It just depends on how far you're willing to go to get it up and running. The easiest way would be to just flash 290 in Flashtool and be done with it. That way you'll have a fully funtional phone again with IMEI, and you can do the rooting later on when you have a system that's actually functioning correctly. Get your stress levels down again and root and what not when you have full control over your phone again
I'm in Norway btw, so since we're in the same time zone, i can help you out tomorrow after school/work if you need it.
Click to expand...
Click to collapse
What I would do is do a flash of the FTF in my guide on downgrading the ZU/recoverinf the IMEI (parse be to [NUT]) http://forum.xda-developers.com/showthread.php?t=2593918
That should give you a clean stock sony .532 firmware ready to root. To root use Bin4ry's tool linked in LordManhatton's guide, then run through the steps in [NUT]'s .290 locked BL ROM thread and the his .136 locked BL thread. This has to be done in order if you are keeping a locked BL all the way through.
THNX
I am very thankful, for your guide and assistance. I am back on stock 532. Is it possible to flash another kernel/boot since this 532 sems to be without root and reovery. All tother things are back though. I cant find te thanks button. Where is that here on xda..?
Could i jjust write fastboot flash boot and then the actual boot.img? So that i can root it...
So I've heard that some people have permanently bricked their phones by rooting them and making mistakes and I just don't understand this. I have rooted mine and it isn't bricked or anything but how is this possible?
Coming from Windows/PC Windows programming and maintenance I've fixed computer that had absolute corrupted hardware from malware or user error. No matter how bad the SOFTWARE is corrupted the computer itself is left undamaged in terms of hardware.
I'm not saying that certain forms of malware can't affect hardware under bizarre circumstances but generally this seems to be an old wives tail. If you rewrite the Master Boot Record on Windows Re flash Firmware and completely format and reinstall Windows it WILL fix even the most complex malware ROOTKITS like tdl4 which installs itself to the MBR (Master Boot Record.)
Why can't you do the same thing on an Android phone? Lets pretend the system gets extremely corrupted from being root what keeps me from removing everything and completely re-installing android? I don't get how you can permanently brick your phone from a software issue alone no matter how corrupted the phone is?
ableright said:
So I've heard that some people have permanently bricked their phones by rooting them and making mistakes and I just don't understand this. I have rooted mine and it isn't bricked or anything but how is this possible?
Coming from Windows/PC Windows programming and maintenance I've fixed computer that had absolute corrupted hardware from malware or user error. No matter how bad the SOFTWARE is corrupted the computer itself is left undamaged in terms of hardware.
I'm not saying that certain forms of malware can't affect hardware under bizarre circumstances but generally this seems to be an old wives tail. If you rewrite the Master Boot Record on Windows Re flash Firmware and completely format and reinstall Windows it WILL fix even the most complex malware ROOTKITS like tdl4 which installs itself to the MBR (Master Boot Record.)
Why can't you do the same thing on an Android phone? Lets pretend the system gets extremely corrupted from being root what keeps me from removing everything and completely re-installing android? I don't get how you can permanently brick your phone from a software issue alone no matter how corrupted the phone is?
Click to expand...
Click to collapse
Nobody has anything to say about this? I'm amazed. I've been reading online that it's hard to permanently brick your phone from rooting alone but some say it's impossible I get different theories everywhere lol?
ableright said:
Nobody has anything to say about this? I'm amazed. I've been reading online that it's hard to permanently brick your phone from rooting alone but some say it's impossible I get different theories everywhere lol?
Click to expand...
Click to collapse
Thread moved to Android Q&A, Help & Troubleshooting.
Perhaps if you post in the correct forum, you would get more responses.
ableright said:
So I've heard that some people have permanently bricked their phones by rooting them and making mistakes and I just don't understand this. I have rooted mine and it isn't bricked or anything but how is this possible?
Coming from Windows/PC Windows programming and maintenance I've fixed computer that had absolute corrupted hardware from malware or user error. No matter how bad the SOFTWARE is corrupted the computer itself is left undamaged in terms of hardware.
I'm not saying that certain forms of malware can't affect hardware under bizarre circumstances but generally this seems to be an old wives tail. If you rewrite the Master Boot Record on Windows Re flash Firmware and completely format and reinstall Windows it WILL fix even the most complex malware ROOTKITS like tdl4 which installs itself to the MBR (Master Boot Record.)
Why can't you do the same thing on an Android phone? Lets pretend the system gets extremely corrupted from being root what keeps me from removing everything and completely re-installing android? I don't get how you can permanently brick your phone from a software issue alone no matter how corrupted the phone is?
Click to expand...
Click to collapse
bricked phone can unbrick using reinstall the firmware just like you say in windows
Vaibhav Chauhan said:
bricked phone can unbrick using reinstall the firmware just like you say in windows
Click to expand...
Click to collapse
That's what I was figuring. So basically the entire concept of permanently bricking your phone from rooting alone or messing things up as root is essentially a spooky incorrect nonsense tale spread around the internet?
ableright said:
That's what I was figuring. So basically the entire concept of permanently bricking your phone from rooting alone or messing things up as root is essentially a spooky incorrect nonsense tale spread around the internet?
Click to expand...
Click to collapse
rooting is not process of brick your device .it gives access the phone as super user.it just install su bin in system/bin folder
Vaibhav Chauhan said:
rooting is not process of brick your device .it gives access the phone as super user.it just install su bin in system/bin folder
Click to expand...
Click to collapse
No I know that friend (My phone is rooted right now) but what I don't understand is all these people saying things like they accidentally deleted xyz files or programs in root and now their phone is PERMANENTLY BRICKED.
I didn't think it was possible to permanently brick something like a phone from a software issue alone? What keeps them from re-flashing the device?
ableright said:
No I know that friend (My phone is rooted right now) but what I don't understand is all these people saying things like they accidentally deleted xyz files or programs in root and now their phone is PERMANENTLY BRICKED.
I didn't think it was possible to permanently brick something like a phone from a software issue alone? What keeps them from re-flashing the device?
Click to expand...
Click to collapse
Half the time people don't know what rooting is, they just know that they want it to install and show off 'cool' root apps. Attribute it to lack of knowledge, not reading the instructions first or following the instructions religiously or, in case they mess up their phone, not wanting to search for a solution which most likely would already have been posted by someone somewhere.
I've messed up my old Motorola Defy more times than I'd like to admit - so often that I uploded a copy of all the required files on my SD card and on the cloud so that I could access it anywhere - but following the instructions posted online helped me revert to stock with no hassles.
PhaseBeta said:
Half the time people don't know what rooting is, they just know that they want it to install and show off 'cool' root apps. Attribute it to lack of knowledge, not reading the instructions first or following the instructions religiously or, in case they mess up their phone, not wanting to search for a solution which most likely would already have been posted by someone somewhere.
I've messed up my old Motorola Defy more times than I'd like to admit - so often that I uploded a copy of all the required files on my SD card and on the cloud so that I could access it anywhere - but following the instructions posted online helped me revert to stock with no hassles.
Click to expand...
Click to collapse
if you delete basic system app you will go to the boot loops but if you got hardbrick during flashing rom then it ia difficult to unbrick your device.it occurs when you remove battery while flashing is running
Vaibhav Chauhan said:
if you delete basic system app you will go to the boot loops but if you got hardbrick during flashing rom then it ia difficult to unbrick your device.it occurs when you remove battery while flashing is running
Click to expand...
Click to collapse
But that's still a software issue correct? Therefore in theory it should be fixable am I right?
ableright said:
But that's still a software issue correct? Therefore in theory it should be fixable am I right?
Click to expand...
Click to collapse
It depends. Software needs hardware to work and hardware needs software. It matters what part of software you mess. You get a permanent brick when you are ****ing the bootloader. Then you get your hard brick. Think of the bootloader like the bios of your computer. The bootloader is the boss. If you mess the bootloader you can't enter recovery and so on. So game over. But yeah when rooting you can delete some system files that are checked by the bootloader and get a secure boot fail or a bootloop. If you have the Stock Rom you can flash that if not then you are soft bricked but still can't fix the soft brick.
HIT THANKS if i helped you.
ableright said:
But that's still a software issue correct? Therefore in theory it should be fixable am I right?
Click to expand...
Click to collapse
yes it is fixable
it on bricked permanently when device hardware will damage
Vaibhav Chauhan said:
yes it is fixable
it on bricked permanently when device hardware will damage
Click to expand...
Click to collapse
That's what I figured. It seems to a large degree then that these anti rooting people are mostly silly
ableright said:
That's what I figured. It seems to a large degree then that these anti rooting people are mostly silly
Click to expand...
Click to collapse
but really you want to brick your phone?
there are also one click brick tool for bricking your phone
Vaibhav Chauhan said:
but really you want to brick your phone?
there are also one click brick tool for bricking your phone
Click to expand...
Click to collapse
No I don't want to brick my phone I was just curious if there was something I didn't know in terms of software somehow causing your phone to permanently brick in a way that couldn't be fixed and it appears from what I've heard from you guys on here that that is not possible and that's a good thing.
ableright said:
No I don't want to brick my phone I was just curious if there was something I didn't know in terms of software somehow causing your phone to permanently brick in a way that couldn't be fixed and it appears from what I've heard from you guys on here that that is not possible and that's a good thing.
Click to expand...
Click to collapse
there is one click brick tool available
after using it your device will be just a garbage
Vaibhav Chauhan said:
there is one click brick tool available
after using it your device will be just a garbage
Click to expand...
Click to collapse
So I guess that's my ultimate questions lets even say you use one of these 1 click brick tools there is still no possible way to fix your phone at that point? The hardware of the phone would remain unchanged so essentially it should be impossible to re-install the OS etc. and your phone would work again am I right?
ableright said:
So I guess that's my ultimate questions lets even say you use one of these 1 click brick tools there is still no possible way to fix your phone at that point? The hardware of the phone would remain unchanged so essentially it should be impossible to re-install the OS etc. and your phone would work again am I right?
Click to expand...
Click to collapse
i have't try it just read about it on xda
i don't want to brick my phone so i don't know it cause permanent brick or not
but this is the link
http://forum.xda-developers.com/showthread.php?t=2701969
Vaibhav Chauhan said:
i have't try it just read about it on xda
i don't want to brick my phone so i don't know it cause permanent brick or not
but this is the link
http://forum.xda-developers.com/showthread.php?t=2701969
Click to expand...
Click to collapse
I get your point on that lol I just wish I had a definitive answer on whether or not a software issue alone on android can permanently brick your phone in suck a way that you can't fix it and how scientifically that's possible as I find this interesting!
ableright said:
I get your point on that lol I just wish I had a definitive answer on whether or not a software issue alone on android can permanently brick your phone in suck a way that you can't fix it and how scientifically that's possible as I find this interesting!
Click to expand...
Click to collapse
:good:
Hi there, I'm not entirely sure if this is the right place to post this.. I'm kind of a noob at this as I have just joined the XDA community.
I have a rooted Verizon LG G3 VS985 running android 5.1.1. Software version VS98535B
I have been recently trying new root apps, but I have noticed that some require busybox. I downloaded the installer, but was hesitant to install because of hearing rumors of soft-bricks and bootloops after installing BusyBox. I am curious if anyone has installed busybox with a similar phone and if they installed BusyBox successfully. I don't know if this a dumb question or not. I am just a bit hesitant to install busybox because my LG G3 is my daily driver, and if it gets screwed up, I'm screwed.
Please help me....
P.S. Sorry again if this is the wrong place to post this thread...
I never had a problem installing it on any device. That said, it's always wise to make a TWRP backup to the MicroSD card before any major changes especially root related.
roirraW "edor" ehT said:
I never had a problem installing it on any device. That said, it's always wise to make a TWRP backup to the MicroSD card before any major changes especially root related.
Click to expand...
Click to collapse
The thing is, I don't want to risk bricking by installing TWRP
zebereeh7 said:
The thing is, I don't want to risk bricking by installing TWRP
Click to expand...
Click to collapse
I don't know what to tell you then.
When we root, and what we do with our phones after we root, is not according to how the manufacturer meant for us to use our devices. There's always some chance of something not going according to plan. The chance of that is usually somewhat slim when following (reliable) directions exactly, but there's always going to be a chance. You can brick your device without even rooting. No one can give you any 100% assurances, although some may try, but nothing is ever 100%, you know what I mean?
No matter what you're likely to do, there's hardly any chance that you won't be able to recover your phone. If you have your Android O/S and apps configured just right for you, at least use the built-in LG Backup in Settings/Backup. Backup to MicroSD and copy anything you don't want to lose from your internal storage to your MicroSD card. If you ever have to Factory Reset or reflash the completely stock unrooted ROM in a way that'll cause your internal storage to be wiped, then you'll be happy you made that backup.
There are both unofficial and official tools to recover your phone to complete stock just like from the factory.
If you weren't at least open to some kind of possibility of bricking, you probably wouldn't have rooted to begin with. Or at least, I should say, if you're going to root you have to be prepared for the possibility of things happening in a way you didn't mean to.
Using a custom recovery like TWRP is the easiest way to get your phone back to a known good state while keeping root.
I'm not trying to convince you to put TWRP on your device, but I will always recommend making a backup in TWRP before making major changes. If you don't and things go wrong enough, then you have to accept the fact that you'll effectively do the work you would've had to do to put TWRP on in the first place, to recover your phone to a usable state.
Sorry if this sounds like a rant, I don't intend it that way.
roirraW "edor" ehT said:
I don't know what to tell you then.
When we root, and what we do with our phones after we root, is not according to how the manufacturer meant for us to use our devices. There's always some chance of something not going according to plan. The chance of that is usually somewhat slim when following (reliable) directions exactly, but there's always going to be a chance. You can brick your device without even rooting. No one can give you any 100% assurances, although some may try, but nothing is ever 100%, you know what I mean?
No matter what you're likely to do, there's hardly any chance that you won't be able to recover your phone. If you have your Android O/S and apps configured just right for you, at least use the built-in LG Backup in Settings/Backup. Backup to MicroSD and copy anything you don't want to lose from your internal storage to your MicroSD card. If you ever have to Factory Reset or reflash the completely stock unrooted ROM in a way that'll cause your internal storage to be wiped, then you'll be happy you made that backup.
There are both unofficial and official tools to recover your phone to complete stock just like from the factory.
If you weren't at least open to some kind of possibility of bricking, you probably wouldn't have rooted to begin with. Or at least, I should say, if you're going to root you have to be prepared for the possibility of things happening in a way you didn't mean to.
Using a custom recovery like TWRP is the easiest way to get your phone back to a known good state while keeping root.
I'm not trying to convince you to put TWRP on your device, but I will always recommend making a backup in TWRP before making major changes. If you don't and things go wrong enough, then you have to accept the fact that you'll effectively do the work you would've had to do to put TWRP on in the first place, to recover your phone to a usable state.
Sorry if this sounds like a rant, I don't intend it that way.
Click to expand...
Click to collapse
Thank you. It didn't sound like a rant at all, more like an honest answer. Now, my question is.. is TWRP or CWM even compatible with my phone? I've heard rumors of TWRP not working on 35B
zebereeh7 said:
Thank you. It didn't sound like a rant at all, more like an honest answer. Now, my question is.. is TWRP or CWM even compatible with my phone? I've heard rumors of TWRP not working on 35B
Click to expand...
Click to collapse
You're welcome!
Yes. As far as I know, TWRP is the only one actively maintained for the VS985. The way I recommend installing it is downgrading to 10B temporarily. Since you're on 35B you'll likely have to use the TOT method with the new .DLL gotten from the 35B KDZ, which you can find toward the bottom of a post in the General section by @hokiealumnus.
There are instructions multiple places, one is here http://lgflashtool.net/index.php/tot-method/, with the exception of using the new .DLL I mentioned instead.
After downgrading to 10B, which will wipe all user data and your internal storage, root with the Stump app, then use TWRP Manager from the Play Store to install the latest TWRP. Both rooting and putting TWRP get more complicated after 10B.
There may be other ways of getting TWRP working on 35B but this is the way I recommend and in my opinion is most foolproof and easiest.
If you do this just remember that you can use the built in LG Backup on what you have now, then you can restore it when you're back on 35B, or if you choose to flash the 46A ROM.
I'm sure it's possible to put TWRP directly on 35B by flashing the right partitions - the 12B aboot.img (bootloader) and laf.img (Download mode). If you would rather use a terminal emulator with superuser permissions and use the commands and partitions found in @bweN diorD 's stickied thread in the General section, you can go about it that way instead. I copy/paste the commands from a text file. If you type them manually and you type something wrong there's a greater chance something will be flashed wrong.
The way people temporarily brick their device on 35B trying to put TWRP on is using Flashify or TWRP Manager or terminal commands without having downgraded the bootloader and download partitions. Or I've seen users use @bender_007 's autorec TWRP app made for either 23C or 24B on 35B.
The fortune is - it´s easy fixable
I´ll work on one for 35b for sure
Just a quick question
I bought a LG G3 off ebay and i got the wifi not turning on issue ive looked everywhere for a solution but none work
will LG Repair fix a phone thats been bought off ebay?
I'm sure they won't care where you got your LG device in order to take your money to repair it.
I'd try a Factory Reset first, and a TOT method restore to 10B if the factory reset alone doesn't help. Both factory reset and the TOT method will wipe all data including internal storage.
You can use the built in LG Backup to backup all your user apps and data to your Micro SD card if you have any you care about preserving yet.
Don't restore any apps before testing wifi. If you want to be in the latest stock unrooted ROM after flashing the 10B TOT, then flash the 47A KDZ after testing the WiFi while on 10B.
TOTs flash more partitions than KDZs or ROMs and can fix problems nothing else can.
Good luck !
roirraW "edor" ehT said:
I'm sure they won't care where you got your LG device in order to take your money to repair it.
I'd try a Factory Reset first, and a TOT method restore to 10B if the factory reset alone doesn't help. Both factory reset and the TOT method will wipe all data including internal storage.
You can use the built in LG Backup to backup all your user apps and data to your Micro SD card if you have any you care about preserving yet.
Don't restore any apps before testing wifi. If you want to be in the latest stock unrooted ROM after flashing the 10B TOT, then flash the 47A KDZ after testing the WiFi while on 10B.
TOTs flash more partitions than KDZs or ROMs and can fix problems nothing else can.
Good luck !
Click to expand...
Click to collapse
yeah they probably wont care and well ive tried lots of things
and well i gave up on the TOT methods because none seem to work. no matter what i try. so then i saw that a month ago i had used the Verizon software assistant and it still had a 24B KDZ so then i used that and flashed it.it worked but still no wifi. The 10B_01 KDZ didnt work for some reason.i dont get why the TOT method isnt working.For the TOT method i change usb hub,reinstall drivers and everything. But for some reason i always get a different error and no success. After it fails it just gets stuck in a Bootloop.
JustAnotherUser69245 said:
yeah they probably wont care and well ive tried lots of things
and well i gave up on the TOT methods because none seem to work. no matter what i try. so then i saw that a month ago i had used the Verizon software assistant and it still had a 24B KDZ so then i used that and flashed it.it worked but still no wifi. The 10B_01 KDZ didnt work for some reason.i dont get why the TOT method isnt working.For the TOT method i change usb hub,reinstall drivers and everything. But for some reason i always get a different error and no success. After it fails it just gets stuck in a Bootloop.
Click to expand...
Click to collapse
Since the 24B KDZ didn't help, the 10B one wouldn't make a difference either. When you flashed the 24B KDZ, did you use the CSE option (which is like Factory Reset) or Normal option? CSE is what should've been chosen but if you didn't, like I said you can just do a Factory Reset now and it's the same thing.
You shouldn't use a USB hub with epithet the KDZ or TOT methods, or when flashing any device from a PC. You should use a USB 2.0 port (not USB 3.0) that's directly connected to the motherboard of the PC - not through a hub.
You changed the port # of the device in Windows' Device Manager in the Port section to 41?
Tried the TOT method directly after rebooting the PC?
Do you know what stock ROM versions the phone was on the times you tried flashing the TOT? Have you tried the TOT method since flashing the 24B KDZ?
Using the original USB cable that came with the phone? Since you could flash the KDZ, I expect you did but just checking.
Sometimes just trying from a different PC is all that's needed.
Until you can successfully try the TOT method, there's really nothing else to do unless you want to pay LG. No idea what they'd charge.
roirraW "edor" ehT said:
Since the 24B KDZ didn't help, the 10B one wouldn't make a difference either. When you flashed the 24B KDZ, did you use the CSE option (which is like Factory Reset) or Normal option? CSE is what should've been chosen but if you didn't, like I said you can just do a Factory Reset now and it's the same thing.
You shouldn't use a USB hub with epithet the KDZ or TOT methods, or when flashing any device from a PC. You should use a USB 2.0 port (not USB 3.0) that's directly connected to the motherboard of the PC - not through a hub.
You changed the port # of the device in Windows' Device Manager in the Port section to 41?
Tried the TOT method directly after rebooting the PC?
Do you know what stock ROM versions the phone was on the times you tried flashing the TOT? Have you tried the TOT method since flashing the 24B KDZ?
Using the original USB cable that came with the phone? Since you could flash the KDZ, I expect you did but just checking.
Sometimes just trying from a different PC is all that's needed.
Until you can successfully try the TOT method, there's really nothing else to do unless you want to pay LG. No idea what they'd charge.
Click to expand...
Click to collapse
I used the CSE option because thats what people recommend to do.
And whoops yeah i meant a USB port 2.0 yeah thats what i use. sorry got them confused
yes i did change the port number to 41
yes ive tried after rebooting PC
ii was running @XDABBBEB VS985 47A - Stock Flashable Firmware
using original usb
hmm maybe a different pc is what is needed
well ill give it one last shot if it doesnt work well i guess im paying
JustAnotherUser69245 said:
I used the CSE option because thats what people recommend to do.
And whoops yeah i meant a USB port 2.0 yeah thats what i use. sorry got them confused
yes i did change the port number to 41
yes ive tried after rebooting PC
ii was running @XDABBBEB VS985 47A - Stock Flashable Firmware
using original usb
hmm maybe a different pc is what is needed
well ill give it one last shot if it doesnt work well i guess im paying
Click to expand...
Click to collapse
Good luck, hope that does the trick! You're not around Columbus, OH are you? If you were I'd offer to try the TOT method on my PCs for you. I wouldn't accept doing it by mail because knowing my luck everything that could go wrong would. I originally had all sorts of trouble getting the TOT method working so I always used KDZ when I had a choice until first there was no other way to downgrade from stock unrooted 35B and higher and then later when I had a problem that KDZs don't fix.
No idea why I had the trouble originally, haven't had one problem with the method since.
roirraW "edor" ehT said:
Good luck, hope that does the trick! You're not around Columbus, OH are you? If you were I'd offer to try the TOT method on my PCs for you. I wouldn't accept doing it by mail because knowing my luck everything that could go wrong would. I originally had all sorts of trouble getting the TOT method working so I always used KDZ when I had a choice until first there was no other way to downgrade from stock unrooted 35B and higher and then later when I had a problem that KDZs don't fix.
No idea why I had the trouble originally, haven't had one problem with the method since.
Click to expand...
Click to collapse
still no luck
and no not around there. and i would be willing to try by mail.
and update: still doesnt work
i dont know why though maybe theres something i did that i dont know of ):
JustAnotherUser69245 said:
still no luck
and no not around there. and i would be willing to try by mail.
and update: still doesnt work
i dont know why though maybe theres something i did that i dont know of ):
Click to expand...
Click to collapse
I really can't help via mail. I just know with my luck something would go wrong and I'm not going to be responsible.
roirraW "edor" ehT said:
I really can't help via mail. I just know with my luck something would go wrong and I'm not going to be responsible.
Click to expand...
Click to collapse
well thanks for all your help man.
im going to send it to LG repair lets see how that goes
JustAnotherUser69245 said:
well thanks for all your help man.
im going to send it to LG repair lets see how that goes
Click to expand...
Click to collapse
You're welcome! Please let us know what happens. At least under warranty, I had a great experience with LG repair. Got my tablet back four days after I sent it.