can you please help me with a soft unbricking of my lg g vista (vs880 [11b]) from verizon usa? i found the 880-11b firmware file, at least i think its the right one. if you know of/ come across this and are sure of its validity i would trust that more. i found and downloaded via a google search. i initially think i may have accidentally deleted the splash pic for the carrier when it boots. this caused it to just black screen after the lg logo n the backlight would flash like it was stuck in a boot loop just the image file was missing. after a little more research i figured out how to put it in the download mode so that i can use a pc to try repair or reinstall whatever it needs. i am unsure if i need the sdk or adk toolkits for a repair in the download mode to work. while on that screen it says its plugged in and waiting to download firmware via usb under the progress bar it tells me not to unplug until download is completed. its not showing up in "my computer" however. and i've never had to do s software/firmware download or setup when the phone wasn't in full normal working order. i simply want to put back the out of the box software back in place. firmware 88011b and 4.4.2 os. just want to be sure i get the proper files/and or programs/ directions to use those resources properly the last thing i want is to guess at something that i could ask someone more experienced for help with and end up bricking it beyond repair. any and all help is very appreciated and i must ask you to please explain each step as clearly and "dumbed down" as possible as you can. if i need to use a program i've never used before {i.e. i hear things like odin mentioned in the forums but i don't understand or have any experience with any pc to phone applications so the more detailed any instructions can be made the better. anything that most ppl who have started tinkering with their devices usually know as common sense or steps that seem implied if not specifically mentioned i'll miss. i have been reading n lurking for months n managed to root the device. but had another issue i accidentally caused soon after which resulted in a factory wipe and some time to remember what i did that rooted it after spending a day on it the first time n trying many things it took me a while to refind what i had done that worked. then this happened. i'm sure with the proper files/tools it'll be fine but i need help to know what those are and to be sure i do it right the first time. i know if i don't there may not be a second chance. thank you again in advance for your patience and help.
Related
I am sure by now you have caught some of my posts floating around the forum in a near panic with confusion. Here are the steps I have taken followed by the issue I am dealing with. I understand I may have taken these steps out of order and am very interested in getting some detailed help on how to fix the issue I am in.
Starting with a fresh stock Atrix I..
Step 1 - Ran Adeo for version 0.1 I downloaded all of the drivers correctly from the MobileTech video website however I honestly don't know what this even means.
Step 2 - Rooted using Super Once click.
Step 3 - I tried to install the Gingerbread theme but after much frustration and many failed attempts I found out I suffer from the missing ADBD file.. I read the thread and it said to download the file unzip it and add it to SBIN.. I have done this countless times and my phone is still unreadable but AROOT, Super once click and Adeo installer..
Rebooting removes the file as mentioned in that thread but I can never actually get anything to recognize my device while the file is in there.
I am set to USB connection NONE and using the Debugging setting in the ON position.
At this point I want to start all over.. Completely go back to stock and then try again, maybe not even that.. I am very turned off of this experience and am starting to get worried considering the investment in this phone I have. (Full Retail)
I understand many people on this forum are not only busy but do no suffer from this problem but I have also seen some incredible help given so as always anyone who is willing to help me just know it will be very appreciated. Thanks!
JoshRH said:
I am sure by now you have caught some of my posts floating around the forum in a near panic with confusion. Here are the steps I have taken followed by the issue I am dealing with. I understand I may have taken these steps out of order and am very interested in getting some detailed help on how to fix the issue I am in.
Starting with a fresh stock Atrix I..
Step 1 - Ran Adeo for version 0.1 I downloaded all of the drivers correctly from the MobileTech video website however I honestly don't know what this even means.
Step 2 - Rooted using Super Once click.
Step 3 - I tried to install the Gingerbread theme but after much frustration and many failed attempts I found out I suffer from the missing ADBD file.. I read the thread and it said to download the file unzip it and add it to SBIN.. I have done this countless times and my phone is still unreadable but AROOT, Super once click and Adeo installer..
Rebooting removes the file as mentioned in that thread but I can never actually get anything to recognize my device while the file is in there.
I am set to USB connection NONE and using the Debugging setting in the ON position.
At this point I want to start all over.. Completely go back to stock and then try again, maybe not even that.. I am very turned off of this experience and am starting to get worried considering the investment in this phone I have. (Full Retail)
I understand many people on this forum are not only busy but do no suffer from this problem but I have also seen some incredible help given so as always anyone who is willing to help me just know it will be very appreciated. Thanks!
Click to expand...
Click to collapse
At a glance I would try looking into the adb offline issue [fixed] thread in this section. though thats from the glance over what you seem to behaving and use aroot, superoneclick is sai by some devs to make a mess of things.
Sadly this is my actual problem. I do suffer from the missing ADBD file however unlike others in that thread I am unable to get anything to work after adding the file back in.
Someone has to have a solution to this. I know my OP is long but I'm at a loss here.
Sent from my MB860 using XDA App
At this point I would be willing to make a hefty donation to a devs paypal to help solve my issue.
Would anyone at least be able to offer advice on what to do from this point forward? Thanks
JoshRH said:
Would anyone at least be able to offer advice on what to do from this point forward? Thanks
Click to expand...
Click to collapse
Warning this will restore your phone to a "updated" stock build and will wipe all your data
1) Download this http://bandbinnovations.com/OLYFR_U4_1.5.2_SIGNED.rar
2) Change the .rar to .gz then extract with .7zip or Winrar
4) Install if not already the 32 bit http://www.multiupload.com/QNFILE4F07 and/or 64 bit http://www.multiupload.com/FIN3KYUD7S
5) Install RSD Lite 5.0 (from here http://www.mirrorcreator.com/files/1TFKDEHB/rsdlite_5.0.msi_links )
6) Turn off the phone
7) Turn on the phone while holding the volume button top
8) Once again, press the volume key up
9) click the ... icon in rsd lite select the firmware file and click start
10) grab a beer and wait until it says passed
Okay, So I am as NOOB as NOOB can be,
I got a used SGS2 (Bell/Virgin), I am on Telus so I figured, how hard can it be to unlock it instead of paying some dude to do it for me? (First mistake, and have been humbled every step of the way since!...)
Anyway I will try to keep this relatively short (it will be difficult)... ...I read a few things online and saw that I needed ODIN and a Rooting software, I originally used SuperOneClick, and to download the right insecure kernel to match my original one etc... ...problem is I obviously didn't read nearly enough when I started because I was almost done and then there was a hiccup when SuperOneClick said that I needed to enable SU in Kies. So I decided to go into Kies to try and do so but the instructions before I started Rooting said to put the phone in USB debugging mode. Apparently Kies doesn't see the phone if it is in that mode. Well by this time I can't get past the logo screen and this is where my downward spiral begins.
I then tried to unroot the phone to go back to stock but didn't really know what I was doing and then I read something about the cache needing to be wiped and then after that I read that maybe my OS was wiped. So at this point I did lots of reading (what I should have done in the first place) and most of anything useful I found was on XDA so that is why I am here. It seemed like yes, in fact my OS was wiped because of one of my not so S-M-R-T actions. So I fumbled through and found the right OS for my S2 and I had ODIN going strong and I had the OS loading, the green bar getting bigger in ODIN and the blue bar working it's way across the screen of my S2...I thought "finally!!, I rock!!"... ...then for some reason everything stopped! I had seen in a post that I had to uninstall Kies before doing anything, which I did...but I didn't see until after the fact that my anti-virus likely interfered (I didn't disable it for the process before I started).
At that point of course I was left with a phone that says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
So then I was afraid to try anything else because many say to steer clear of Kies and also I had read that I may need a USB jig to be able to get it back into download mode because all I was getting was the "firmware upgrade issue" screen. I did make a USB jig with a resistance of 300K Ohms and I *can* get the phone into download mode. (Though another concern is that when I plug the USB jig in and it brings the phone into download mode, the counter is not reset and I read that that was supposed to be reset by the jig.)
So last night I got brave and decided to try and run ODIN and to have another attempt at installation of OS. Now I can get ODIN to detect the phone, but I put the I9100MUGLD3_I9100MBMCLD3_I9100MXXLD3_HOME.tar.md5 file into the PDA section of ODIN and it starts and gets to the part where it says loading firmware or something and then bootload.bin and it stayed like that for like, an hour and then I gave up, fearing that I am just going to screw it up even more.
So now I decided that I am not even close to knowing what to do next but every time I found anything to move forward it was on this site so I figured I may as well join the site since I have been here so often. Now I am hoping for some kind of miracle...so, in advance, please please please and thank you thank you thank you all for your input. (Sorry for the length of this I just wanted to get all the info I could into this)
Its quite a long story and didnt bother reading it.
If you can still access your phone via odin at downloadmode. Flash a stock firmware for your device and it should fix if it is just a soft brick.
Sent from my GT-I9100 using Tapatalk
UnwiredDroid said:
Its quite a long story and didnt bother reading it.
If you can still access your phone via odin at downloadmode. Flash a stock firmware for your device and it should fix if it is just a soft brick.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Sorry for the length of the story, I thought there may be alot of useful info mixed in with the useless info... ...when you say use stock firmware do you mean the kernel or the actual OS? I tried loading ICS onto it (which I thought was stock but I may be wrong). Is it supposed to be gingerbread or something else? Also where would I find a good file for it.
Thank you again for any input, very much appreciated!
Hey ,
I also have a Virgin Samsung S2 i9100 and the first time I tried rooting it, it got stuck on the screen with the yellow triangle and wouldnt move at all. I believe it was bricked?
anyways, I m not sure I totally understand your situation, but I solved my problem using this thread
http://forum.xda-developers.com/showthread.php?p=21493413
look it under the i9100M section. hope this helps
schtiven said:
Hey ,
I also have a Virgin Samsung S2 i9100 and the first time I tried rooting it, it got stuck on the screen with the yellow triangle and wouldnt move at all. I believe it was bricked?
anyways, I m not sure I totally understand your situation, but I solved my problem using this thread
http://forum.xda-developers.com/showthread.php?p=21493413
look it under the i9100M section. hope this helps
Click to expand...
Click to collapse
Thank you all so much for your help, I could not get it to work after several tries, I even tried three or 4 different USB cables and ports on my PC and still no. I read on another thread that one person tried another PC and it worked so I tried my friend's laptop and it worked!...my SGS2 boots up and all that now! Very very happy thank you all.
Hello,
I have a Samsung Galaxy S2.
After reading this post http://forum.xda-developers.com/showthread.php?t=2382579 I decided to root my phone.
So I went ahead and started with this step http://forum.xda-developers.com/showthread.php?t=1118693 because I was unsure if I had a kernel with the MMC-SUPERBRICK-BUG.
After I flashed CWM-SuperSU-v0.97.zip using Odin version 1.85 and after the phone rebooted it was stuck at the "triangle screen" for a few seconds then the display went black and I couldn't do anything further.
Up to this point the phone was still accessible in download mode (volume up, power and center button). I believe this is called "download mode". Sorry but I am a complete noob with rooting phones, etc...
So I panicked and took the phone to a repair shop (big mistake). The guy ran it in download mode then tried to flash something onto the phone (I think he used all 4 fields: Bootloader, PDA, Phone and CSC.
Then, in the middle of the operation, Odin froze when writing "setting up connection". Then the phone died ! pressing the 3 famous buttons does nothing and the phone just stays dead.
I had to leave the phone there as the guy said they will try to bypass stuff and try to connect to the CPU directly (sorry again if this sounds noobish). I did update my modem firmware and my computer BIOS in the past... but I guess this one was more complicated.
At the shop, they asked me to check again in 3 days. I am lost here. I don't know what to do anymore.
Is the phone hard bricked ? Should they bear all expenses for what they did ? I would bring back my phone and try something like this http://forum.xda-developers.com/showthread.php?t=1878255 or even a stock flash but I am afraid I cannot do that as the phone isn't even powering up anymore after they tried to repair it at the shop.
Any advice is appreciated.
Nope. You borked it. You tried to flash custom firmware to the phone & obviously failed spectacularly at it. Instead of trying to flash it yourself via download mode (which you could easily have done unless the NAND was borked), you paid them to do it. Sometimes flashes go bad. Sounds like that's what happened in this case.
Reading between the lines they sound like they're going to try & JTAG it (or have someone else do it). And if that fails I presume they'll change motherboards. You could always get the phone back & take it to someone who does JTAGs if that shop doesn't themselves.
MistahBungle said:
Nope. You borked it. You tried to flash custom firmware to the phone & obviously failed spectacularly at it. Instead of trying to flash it yourself via download mode (which you could easily have done unless the NAND was borked), you paid them to do it. Sometimes flashes go bad. Sounds like that's what happened in this case.
Reading between the lines they sound like they're going to try & JTAG it (or have someone else do it). And if that fails I presume they'll change motherboards. You could always get the phone back & take it to someone who does JTAGs if that shop doesn't themselves.
Click to expand...
Click to collapse
Yes I know I failed at it
Or maybe the shop technician is the one who broke it. At least when I had the phone with me I was still able to boot in Odin mode.
Do you think I could have recovered my phone if I had kept it with me and it was booting in download mode ?
I feel so pissed that I took it to that shop. I just wish I hadn't panicked and I had tried, instead, to fix it at home by asking for more help.
Anyway I still haven't paid them anything so far.
We agreed that they will pay for the motherboard because I brought in a working phone (that would power up at least). The owner of the shop was nice enough to agree that he would only charge me fees for installing new software on the phone (even if they have to change the motherboard) because he knows the phone was booting in Odin mode when I came in to the shop and his technician flashed the wrong firmware.
I also wrote down the board serial number so I can be sure they changed it (if they say they did that). So you are telling me the phone can still be fixed ? What does JTAG mean ?
Even if it is fixed I think I will be too scared to try and root it again. Unless I can understand in advance, step by step, what I need to do and what file version(s) I need to use.
Ok, I got my phone today in good working condition.
According to the shop, they had to replace an IC (I don't know what damaged the IC, I am assuming this happened when they tried to electrically jolt the phone) then JTAG it to get it to work again. They charged me a small fee (and they did end up bearing more than 50% of the expenses) because I brought in a phone that was booting in download mode and they take responsibility for what happened after that (flashing wrong files which caused the phone to completely stop booting).
Anyway, long story short, this was my first attempt to root a mobile phone and I learned my lesson.
I am running the following:
Model Number: GT-I9100
Android Version: 4.0.3 (which I will need to upgrade to 4.1.2 of course)
Baseband Version: I9100XXLPW
I know you will say read the sticky posts or the guides but the truth is, that's exactly what I did (you can see the links to the guide I tried to follow in my original post) and I still ended up failing at rooting/installing cyanogen on my phone right after installing Clockwork Mod.
The truth is I am scared to try again and mess up the phone. So this time I would rather be safe than sorry.
What can I do, this time, to safely root it and install a mod like Cyanogen.
Detailed steps are appreciated:
- Do I need to upgrade to 4.1.2 before rooting as 4.0.3 might have the superbrick bug ?
- How to backup the phone.
- Odin version to use, ClockWork Mod version to use, Cyanogen version to use
- How to connect the phone, how to reboot in download mode and all the necessary actions to avoid bricking my phone.
No spoon feeding aloud on XDA.better to read and learn how to do this and that but before you flash anything after learning how to do that learn how to fix it if it doesn't work. :thumbup:
andrewwright said:
No spoon feeding aloud on XDA.better to read and learn how to do this and that but before you flash anything after learning how to do that learn how to fix it if it doesn't work. :thumbup:
Click to expand...
Click to collapse
Fair enough, I figured I'd get that reply from someone and it's normal to be honest.
I decided not to try anything on my phone before I re-read the guides and be sure I know what I am doing.
I will also keep the phone running on stock firmware (after upgrading to JB 4.1.2) to check the battery consumption behavior which, I hope, will be fine since someone tampered with my phone's electronic components at the shop.
Hi all. I've been reading (and not understanding) a lot of threads on here about flashing firmware to this old Galaxy player.
All I wanted to do originally was get a newer android version for the store and games for my 14 month old wee lad to play with.
Anyway after a fair bit of research I got Odin and the US version of a Rom and dove right in to upgrading and of course I made an unholy mess of it and bricked the device.
I chose the US version knowing it probably wasn't going to support the physical home button after but took the risk.
I plugged it into my windows 10 PC and went from there. So the process failed initially after a very quick scroll of information. Then I started ticking the check boxes in Odin to a point where the process took longer and seemed to be actually doing something instead of flying through and failing. Well then it seemed to be doing something so I left it for an hour or two and when I came beck it was stuck where it was, not doing anything. It was late so I unplugged and went to bed.
Now the device only displays the very commonly reported 'phone... ! ...PC' icons.
I have Odin v1.82 running right now and its detecting the player ( yellow box 0:[com8] ), then after a while the player shuts off and comes back on for Odin to detect it again.
Nothing else happens, windows won't read the device even to access as a storage device.
So I've been to step 2, which is trying to unbrick it. I don't really want to go the Ubuntu route as I know even less about Linux then Android.
Also theres the problem of trying to get the original international roms and pit and bootloader(?) files. All the links on here seem to be broken.
So does anyone have the actual files I need and maybe an idiots guide to doing the work?
All help would be greatly appreciated.
didihno said:
Hi all. I've been reading (and not understanding) a lot of threads on here about flashing firmware to this old Galaxy player.
All I wanted to do originally was get a newer android version for the store and games for my 14 month old wee lad to play with.
Anyway after a fair bit of research I got Odin and the US version of a Rom and dove right in to upgrading and of course I made an unholy mess of it and bricked the device.
I chose the US version knowing it probably wasn't going to support the physical home button after but took the risk.
I plugged it into my windows 10 PC and went from there. So the process failed initially after a very quick scroll of information. Then I started ticking the check boxes in Odin to a point where the process took longer and seemed to be actually doing something instead of flying through and failing. Well then it seemed to be doing something so I left it for an hour or two and when I came beck it was stuck where it was, not doing anything. It was late so I unplugged and went to bed.
Now the device only displays the very commonly reported 'phone... ! ...PC' icons.
I have Odin v1.82 running right now and its detecting the player ( yellow box 0:[com8] ), then after a while the player shuts off and comes back on for Odin to detect it again.
Nothing else happens, windows won't read the device even to access as a storage device.
So I've been to step 2, which is trying to unbrick it. I don't really want to go the Ubuntu route as I know even less about Linux then Android.
Also theres the problem of trying to get the original international roms and pit and bootloader(?) files. All the links on here seem to be broken.
So does anyone have the actual files I need and maybe an idiots guide to doing the work?
All help would be greatly appreciated.
Click to expand...
Click to collapse
'phone... ! ...PC' is merely forced download mode. Find a full international stock and flash with odin...
Meticulus said:
'phone... ! ...PC' is merely forced download mode. Find a full international stock and flash with odin...
Click to expand...
Click to collapse
Yes I have read that on here mate, that its still in download mode, however no button combo gets it to do anything else (like trying to enter recovery mode).
Also and I guess this is the main problem, I can't find the stock files anywhere, and trust me I've been reading threads here and googling elsewhere.
The links on here all seem to be broken, which given the age of the threads is no surprise.
So I'm still kind of hopeful someone reads this and can supply the files I need.
Oh and I'm open to a non stock version as long as its for the international version (home button) and proven to be good.
I'd love to be rid of the bloatware and free to install play store etc.
didihno said:
Yes I have read that on here mate, that its still in download mode, however no button combo gets it to do anything else (like trying to enter recovery mode).
Also and I guess this is the main problem, I can't find the stock files anywhere, and trust me I've been reading threads here and googling elsewhere.
The links on here all seem to be broken, which given the age of the threads is no surprise.
So I'm still kind of hopeful someone reads this and can supply the files I need.
Oh and I'm open to a non stock version as long as its for the international version (home button) and proven to be good.
I'd love to be rid of the bloatware and free to install play store etc.
Click to expand...
Click to collapse
Here is full stock RU froyo..: https://www.4shared.com/zip/vxHoJ8E0/G70JKKE3_STOK_222RU_.html
Here is full stock USA : http://www.meticulus.co.vu/p/downloads_2.html?m=1
Here are more : https://www.sammobile.com/firmwares/galaxy-player-50/YP-G70/
Hello! So awhile ago, I decided to try to root my new phone, ensuring model and etc was correct (CPH2459, this should be the usa unlocked variant right?) annddddd... it did not turn out so well. I had a friend recommend I reset- (which I mean I don't see what that would do but I have bootloader already unlocked so..) which just led me to being stuck on the setup screen where i cant get past wifi without my phone restarting- without fail to that as well. Also like touchscreen didnt work half the time and physical keys (Power, Volume) didn't seem to respond when the device was on either (excluding for a hard restart).
I followed this guide step by step (in no way blaming those individuals) https://forum.xda-developers.com/t/...guide-from-fastboot-obtain-root-more.4495801/ and my phone is now stuck in a fastboot loop.
I do wish to clarify that I am sure I followed step by step, I didn't make a backup though as the initial guide didn't present how to do so.
I'm honestly afraid to do anything more to my phone, and I really do need this to work as it just happens my other phone broke recently. Would appreciate any help so, very much, I have no idea what I'm doing and I haven't the slightest clue as to what may be wrong.
I do understand this question has been asked a bit with this phone and there are other threads, but I couldn't find my answer. So I'm hoping for some direct help.
nemmieve said:
Hello! So awhile ago, I decided to try to root my new phone, ensuring model and etc was correct (CPH2459, this should be the usa unlocked variant right?) annddddd... it did not turn out so well. I had a friend recommend I reset- (which I mean I don't see what that would do but I have bootloader already unlocked so..) which just led me to being stuck on the setup screen where i cant get past wifi without my phone restarting- without fail to that as well. Also like touchscreen didnt work half the time and physical keys (Power, Volume) didn't seem to respond when the device was on either (excluding for a hard restart).
I followed this guide step by step (in no way blaming those individuals) https://forum.xda-developers.com/t/...guide-from-fastboot-obtain-root-more.4495801/ and my phone is now stuck in a fastboot loop.
I do wish to clarify that I am sure I followed step by step, I didn't make a backup though as the initial guide didn't present how to do so.
I'm honestly afraid to do anything more to my phone, and I really do need this to work as it just happens my other phone broke recently. Would appreciate any help so, very much, I have no idea what I'm doing and I haven't the slightest clue as to what may be wrong.
I do understand this question has been asked a bit with this phone and there are other threads, but I couldn't find my answer. So I'm hoping for some direct help.
Click to expand...
Click to collapse
I'm guessing you noticed that the link they posted for the downloaded ota is the gn22000 model correct? yours is CPH (as i saw you stated) so i was just double-checking to make sure you didn't download the wrong variant's ota..