From bricking this pos I have learned a lot of what to do and what not to do. I am pretty sure but need to know for certain...is there a fix for this?
Like many others I tried to install cwm recovery from android terminal emulator and sounds like I either put the image in the wrong spot or tried to install over something important. Odin doesnt work on this phone and rom manager just kept giving me the messaging has stopped working error, I soft bricked once before this but was able to flash and fix. I installed cwm recovery from rom manager I thought but was not able to boot in recovery. Ive read tons of posts and tried all the little tricks. No download mode, never could boot in recovery, had to install the qhsusb_dload drivers and now when connected to pc its a 50/50 chance of either good connect sound or bad connect sound...either way the phone doesnt power on at all. Can someone help me or should I sell this to someone who can make use of it? I have flashed and rooted many phones in the past and used to come here regularly, this has always been the BEST site for answers and help so Im really hoping you tech devs can pull through for me on this one. Any help is appreciated!
What do you mean ROM manager stops working if your phone is hard bricked.
I'm not surprised Odin doesn't work I thought that was for Samsung phones but I've never used it.
Anyways I understand you think you might have used the adb shell and copied the cwm recovery to the wrong partition do you remember which it could have been?
boot.img at mmcblk0p8
recovery.img at mmcblk0p13
firmware.img at mmcblk0p1
baseband.img at mmcblk0p14
system.img at mmcblk0p27
Also I'm sure its been said but make sure you have a decent charge leave it plugged into the wall for at least an hour without trying anything.
I just am curious you don't see lg logo? battery animation? anything?
Sent from my LG-P930 using xda app-developers app
thanks for replying. i have tried switching batteries, waited overnight, tried everything i could find on here and no power no logo no start up whatsoever. i was getting so desperate to get cwm recovery to work that i probably followed directions i shouldnt have. i followed a youtube vid and typed the following into the terminal;
su
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p6 bs=4096
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p6 bs=4096
after this i powered off the phone and it never came back to life since. the problem with rom manager was it wouldnt update cwm recovery, even though i just installed it the night before, the next day there was a new update it said. every time i tried to install a rom from rom manager it force closed and said messaging has stopped working. (what messaging had to do with it i dont know) when i plugged in my phone to pc it said couldnt find qhsusb_dload drivers so i installed them and now my phone doesnt show up on my pc. i read somewhere to try lgtools but that comes with its own problems like smartcard driver errors. i hope this is enough info thanks
msincorporated said:
thanks for replying. i have tried switching batteries, waited overnight, tried everything i could find on here and no power no logo no start up whatsoever. i was getting so desperate to get cwm recovery to work that i probably followed directions i shouldnt have. i followed a youtube vid and typed the following into the terminal;
su
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p6 bs=4096
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p6 bs=4096
after this i powered off the phone and it never came back to life since. the problem with rom manager was it wouldnt update cwm recovery, even though i just installed it the night before, the next day there was a new update it said. every time i tried to install a rom from rom manager it force closed and said messaging has stopped working. (what messaging had to do with it i dont know) when i plugged in my phone to pc it said couldnt find qhsusb_dload drivers so i installed them and now my phone doesnt show up on my pc. i read somewhere to try lgtools but that comes with its own problems like smartcard driver errors. i hope this is enough info thanks
Click to expand...
Click to collapse
When you ran the command "dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096": you broke your phone.
Those instructions must have either been completely wrong or instructions for another phone.
Basically you installed the recovery right between boot and firmware thus bricking your phone. You can buy tools to fix it bit that costs big $$$
Sorry for the bad news. I've been trying to find out if this phone has UART capabilities. I'll post it here if I find anything useful
Sent from my LG-P930 using xda app-developers app
thanks, the news is no surprise as i have been reading other posts that say the same thing. its too bad i paid $700 for this brand new over a year ago...thats a pricey brick. hopefully someone will be able to fix it as i am not willing to spend too much more on tools to fix it i will just sell it for parts or something. thanks for taking the time to look into this for me and let this be a lesson to all you other noobs who want to make the nitro better. DO NOT FOLLOW MY LEAD
Maverick.Marq said:
When you ran the command "dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096": you broke your phone.
Those instructions must have either been completely wrong or instructions for another phone.
Basically you installed the recovery right between boot and firmware thus bricking your phone. You can buy tools to fix it bit that costs big $$$
Sorry for the bad news. I've been trying to find out if this phone has UART capabilities. I'll post it here if I find anything useful
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
Never seen a phone technically hard bricked so I ask how installing the recovery between the boot and firmware would prevent from accessing Download mode? Logic would tell me, which can be wrong , that Download Mode comes before either of those thus no matter where he flashed recovery, download mode is still accessible. Please explain. Thanks in advance.
EDIT: From what I just read, dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096 makes a backup for the NitroHD before flashing the recovery. Found here. And, according to the article, the other command he ran was the recovery flash w/ the second command he used as a repeat, or excess.
after reading the above i noticed this is where i might have gone wrong.
[ NOTE: If you inadvertently copied "recovery.img" to the external or removable SD card, replace "/sdcard/" in the command above with "/sdcard/_ExternalSD/"
i didnt see this command in the first place but i did copy the recovery.img right to the removable sd card. im guessing the mistake i made is irreversible.
http://forum.xda-developers.com/showthread.php?t=1939436
Apprently this person had the same problem as you. Many told that person it was hard bricked which is just strange to me b/c I've never seen a totally bricked phone, but apparently this is my first.
im being told its hard bricked but fingers crossed that im wrong. ive bricked many phones but always been able to fix them, this is my first possible HARD BRICKED device. when someone says they havent seen an actual hard bricked phone that kind of gives me a little hope.
msincorporated said:
im being told its hard bricked but fingers crossed that im wrong. ive bricked many phones but always been able to fix them, this is my first possible HARD BRICKED device. when someone says they havent seen an actual hard bricked phone that kind of gives me a little hope.
Click to expand...
Click to collapse
That's the same boat I'm in. I've had 4 phones and fudged all of them to the point I thought I was bricked but could ALWAYS get download mode and flash stock firmware. I'm thinking you wrote over download mode thus not being able to access it and killing the phone. That's the only explanation I can come up with. Patiently waiting for maverick.marq to explain b/c I'm cursed w/ the having to know the how-to-the-why.
Just to be clear, you're trying to get to download mode by holding the vol UP button and plugging in to PC w/ phone off, right?
I'm assuming that all of the first sector p1 to p8 must be intact for download to work and since he wrote his recovery to p6 I assume it took out both firmware and recovery as (again a lot of assuming) the processor says OK look for firmware in block p1 doesn't find a complete image and it and then fails to boot.
Sent from my LG-P930 using xda app-developers app
i have held vol up, vol down, power, home, etc ive tried all the buttons. its my only phone so i will not give up easily i will continue to try all options until i either fix or replace it. this would have not happened if i could have only gotten the cwm recovery to flash properly the first time. i dont know why rom manager kept force closing and giving me the messaging error. i tried rom toolbox and it too gave me the same error. i soft bricked it and ended up getting stuck on the logo with security error but that was an easy fix. this is the only phone ive had a problem flashing, but this is a good learning experience. if i get it back up and running im not even going to try to mess with it after that.
msincorporated said:
i have held vol up, vol down, power, home, etc ive tried all the buttons. its my only phone so i will not give up easily i will continue to try all options until i either fix or replace it. this would have not happened if i could have only gotten the cwm recovery to flash properly the first time. i dont know why rom manager kept force closing and giving me the messaging error. i tried rom toolbox and it too gave me the same error. i soft bricked it and ended up getting stuck on the logo with security error but that was an easy fix. this is the only phone ive had a problem flashing, but this is a good learning experience. if i get it back up and running im not even going to try to mess with it after that.
Click to expand...
Click to collapse
Well, best of luck b/c it doesn't look promising from all I've read on this similar issue. :/
Send it to LG. I had this same problem a while ago and sent it to them and they fixed it no charge, no questions asked.
Sent from my SAMSUNG-SGH-I747 using xda premium
rani9990 said:
Send it to LG. I had this same problem a while ago and sent it to them and they fixed it no charge, no questions asked.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
thanks this was something i was curious about, i am going to contact them monday about it
mmcblk0p6 is the secondary bootloader. The idea is if you mess up your primary bootloader, you'll still be able to access download mode since it uses its own separate bootloader. By overwriting the secondary bootloader, you're making it impossible to use download mode.
msincorporated said:
i have held vol up, vol down, power, home, etc ive tried all the buttons. its my only phone so i will not give up easily i will continue to try all options until i either fix or replace it. this would have not happened if i could have only gotten the cwm recovery to flash properly the first time. i dont know why rom manager kept force closing and giving me the messaging error. i tried rom toolbox and it too gave me the same error. i soft bricked it and ended up getting stuck on the logo with security error but that was an easy fix. this is the only phone ive had a problem flashing, but this is a good learning experience. if i get it back up and running im not even going to try to mess with it after that.
Click to expand...
Click to collapse
how did you get the security error fixed?.....im stuck and cant access the recovery or download mode...
Did u try flashing the stock kdz back on to it? Can u access download mode? Not recovery I am talking about the download mode. And yeah this phone is a pos when it comes to battery I am using a fat 3800 may battery and when I get lucky it maybe last 14 hours. This phone has so bad battery consumption. No matter what ROM I use.
Sent from my LG-P930 using XDA Free mobile app
Related
CDMA GALAXY NEXUS> Hey guys, I was running Romanbb's 4.0.4 build earlier today. I clicked on a video (which may or may not have been on a porn site) all of a sudden my screen went all wacky. Where it was kind of fuzzy and running diagnal across the screen. I could only see part of it. I thought I might have gotten a virus or something because i have never had one of my devices do this before. So I immideatly rebooted the phone into recovery and wiped eveything including formatting system. I went to flash a nandroid I had of black ice and in the middle of flashing that my phone rebooted itself and stayed there (bootlooping at the google logo) I can get into fastboot and I can get into recovery about one out of every ten times but I cant do anything in recovery because the phone turns itself off insted of booting recovery most of the time (I have clockwork touch) When I do get into recovery without it turning off it reboots if I try to flash anything. It seems to be stable in fastboot (thank god!) but When I get it connected in Wugs Root tool kit and try to flash the stock image it goes through the motions and says FAILED on every step exept the first (which I believe is checking radio). It says ( error too many links) on the first two) and I cant remember the error on the last four but I have tried it a couple times so I can replicate it if needed. Can anyone tell me what to do from here? I really appreciate in advance!!! If this is a hardware error then I would like to get it back to stock to get it replaced. It is weird that it happened while running a rom. Its not like I messed up while flashing or anything.
ADB will recognize it in Fastboot. I already set all of that up when I rooted. when I try to flash the stock+unroot option on wugfresh's toolbox it errors out on every step like there is something wrong with my internal sd on my phone? Im wondering if I should try odin. IDK? Im hoping somebody who has seen this or had this happen before will save the day and tell me what to do.
lol why did you rush into CWM and start wiping things? you should have let it reboot and it probably could have been a one off..
you can try this http://rootzwiki.com/topic/14145-od...actory-odin-restore-402-with-radios-unrooted/
It is stable in fastboot but in cwr it is still geeking out
It still is glitching in cwr. most of the time it either turns off or reboots when I try to go into cwr. i can wipe but if I flash anything it freezes at the point where it starts writing to storage. I have never seen anything like this before.
I have now tried oden as well
It looks like it is a problem with the hardware. The phone is only a couple months old if that. So I really wish I could flash the stock image or at least get rid of cwm. but that is not looking likely. Here are a couple pics of odin showing the problem. Any guidace would be much appreciated. This SUCKS
Why in the heck are you trying to use Odin?
I can only get into fastboot and odin.
CWM wont let me do anything. it crashes and reboots into a bootloop if I try to flash anything. The poster above suggested odin. I dont know what else to do. Please help if you can!
Can you get a screencap of when it fails fastbooting the stock images?
yes
yes, give me couple min and I will post it. Thank you!
I guess I cant. This is all I get now
drumdestroyer said:
yes, give me couple min and I will post it. Thank you!
I guess I cant. This is all I get now
Click to expand...
Click to collapse
How are you attempting to access fastboot?
Vol + and Vol - and power all at the same time
Vol + and Vol - and power all at the same time from powered off
And oden was Vol - and power at the same time from powered off
Now no matter what I push it goes to the screen with the yellow triangle.
That screen says you (now) have a corrupt partition.
At this point, you must use Odin, which is unfortunate. What URL did you use to download the image? The current image in that thread was on multiupload.
drumdestroyer said:
Vol + and Vol - and power all at the same time from powered off
And oden was Vol - and power at the same time from powered off
Now no matter what I push it goes to the screen with the yellow triangle.
Click to expand...
Click to collapse
during my rooting attempt I had a problem with the two vol buttons. It was quite frustrating. Keep trying them and try pressing the power button a fraction of a second sooner.
I downloaded the one later in the thread
Here's the Modem: http://dl.dropbox.co...15.EK02_LTE.tar
Here's the System: http://dl.dropbox.co...L53F_signed.tar
from this thread on page 3 housry23 posted them from his dropbox:
http://rootzwiki.com/topic/14145-od...restore-402-with-radios-unrooted/page__st__30
there were a couple other posts right around the same time with it but they all were the same file name
I thought I saw the same files in the xda thread i found also
I used that thread because it is the one that the second post linked for me.
drumdestroyer said:
Vol + and Vol - and power all at the same time from powered off
And oden was Vol - and power at the same time from powered off
Now no matter what I push it goes to the screen with the yellow triangle.
Click to expand...
Click to collapse
Send it to me. I might be able to fix it. PM me.
Sent from my Galaxy Nexus using xda premium
loveubuntu said:
during my rooting attempt I had a problem with the two vol buttons. It was quite frustrating. Keep trying them and try pressing the power button a fraction of a second sooner.
Click to expand...
Click to collapse
no luck with that. it seems to only open to the "corupted partision" screen. Thanks for the suggestion.
ljwnow said:
Send it to me. I might be able to fix it. PM me.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I pm'd you to ask how you could fix it. Just wondering if I could do it. I can follow instructions well. I have never had a problem and have been flashing stuff for a year or so. IDK what happened here.
I can't help but I wanted to share that I had a similar experience. I was bonne stock and clicked on a you tube video and my phone immediately shut down and tried to reboot itself, but only would boot loop. I had to manually reformat my partitions to recover. Sounds like your case might be even worse. Still don't know what my problem was.
Sent from my Galaxy Nexus using XDA
Thanks. Any feedback is appreciated.
so you can't get into bootloader or odin screen any more? if so try using a Jig it works to get the phone into odin mode for me. i used the same usb jig i made for the captivate.
I got the same suggestion from someone else. I have to wait until radio shack opens in the morning and I will give it a shot. Otherwise, I went by verizon and they are having samsung send me a replacment. I would much rather keep this one if I can though
I tried flashing the stock image from fastboot and it failed though when I could get there, and I also tried flashing the stock image through oden when I could get there and both failed multiple times so I don't have much hope. I think something broke.
I am headed to radio shack now. Be back soon with a answer as to wheather I can save my baby or not.
So I recently rooted my phone with this tutorial:
http://www.youtube.com/watch?v=nkkcCCjeUpI
Everything went great and I was rooted. So next I decided I wanted to flash a rom. So I decided this one:
http://forum.xda-developers.com/showthread.php?t=1817345
I looked over it and followed its instructions. So I flashed it. I also flashed the google apps.
This is where the problems started. I rebooted my phone, and It never would show the boot logo. I kept pulling the battery and it would not start. I thought the battery might be dead so I charged it, and still nothing. I noticed when I plug it into my computer and it makes the little connection noise. (Like my computer is reconising the device) But still nothing on the screen. I tried to connect it to odin and it does not show the device.
So I have looked all over the internet (including these forums) and have found no help. Sounds like I might have bricked my device.
So my last question, If I did indeed brick my device will this fix it? (I mean will it atleast get it into download mode?)
http://www.ebay.com/itm/NEW-Samsung...369526?pt=PDA_Accessories&hash=item3a77c2f8b6
Please let me know if you have any ideas.
Thanks, Griffsbrown
Boot into recovery and restore the nandroid you made before you flashed.
Man sure sounds like most the people having problems are cause they are rooted/modded. Hope its a simple fix for you. GL.
You flashed a rom for a different phone, its dead pretty much. research jtag I read its about 60-100$ read more in the future.
Sent from my SGH-T999 using xda premium
You flashed a ROM for a different phone. That is why you can not boot. Are you able to get into download mode? from the power off state, press and hold the volume down and home bottons and the power button. This should bring you into download mode. IF you can get there then you should be able to recover.
always be careful when flashing roms if you can get into download mode like the above poster said then your lucky and can odin a root66 and you will be back to before you installed the wrong ROM.
If you cant ........... your bricked my friend time to learn a lot more about jtag (which is a lot more difficult than odin READ READ READ
The only thing is people have been installing ATT roms for some reason their phones are not bricking but unless the dev says it works i wont try it.
ONLY USE ROMS FOR YOUR PHONE im really new and one of the first things to know.
Bricked! Search for mobile tech videos jtag fix.
Sent from my SGH-T999 using xda app-developers app
I downloaded the Jedi Mind Trick JB 2 ROM and installed it via clocwork mod recovery .. That went fine but it took me a few days to realize I didnt have a working video camera anymore on my phone.. so I thought to flash a stock ROOTed rom instead...
Then I found this threat about an updated version of Jedi Mind Trick's ROM labled JB 3.. So I wiped as much as I could in recovery and chose to format all the options it gave me in recover , Format system , data , cache , emms(or something) .. and now when I boot the phone , it shows the first flash screen , and the samsung logo starts to shimmer then it reboots back to the splash screen and repeats this process everal times before just going black and sitting there..
So I've successfully bootlooped my phone doing this..
MY PROBLEM -- I don't know how to charge my phone or connect to it to install anything else..
Is this a serious problem? How can I charge my phone to continue troubleshooting it? It still has some battery to try some things but I don't know how to hook it up to transfer any other roms to it via USB cable and PC in it's current state..
I'm very computer savvy but I'm trying to learn this phone modding stuff and I realy hope I didn't brick my phone in this process.
Can someone please help me out here? I'll be on the forums religiously until I figure this out.
What should I start doing first??
Any help would be greatly appreciated!! Thanks!
still working at it
I think I'm at the point of having to use ODIN to flash a new rom since i cannot simply copy this rom to the sdcard to use clockwork to flash it .. Am I correct on this ?
For some reason this rom I found (should be stock rooted tmobile gSII rom) does not want to open from ODIN's PDA button cause its in .zip and not .tar or anything... I'm not sure how to flash this rom with ODIN ( I'm not even 100% sure this is how its supposed to go) Any suggestions ?
phew
UPDATE - So I managed to research enough to find out that there is no way to flash a CUSTOM rom with ODIN.. SO I had to download a stock (presumably rooted) t-mobile rom and flash THAT ...
Now I'm back up with a rooted rom and will begin re-installing clockwork and then my custom deodexed rooted rom afterward.
Thanks for all who almost kinda tried to care to reply in this past 2 hours =) -- As previously mentioned.. I am a nerd.. I just suck at phone modding. Haha
So , looks like I'm in the clear now and don't need any more support on this particular topic yet.
zarklon said:
UPDATE - So I managed to research enough to find out that there is no way to flash a CUSTOM rom with ODIN.. SO I had to download a stock (presumably rooted) t-mobile rom and flash THAT ...
Now I'm back up with a rooted rom and will begin re-installing clockwork and then my custom deodexed rooted rom afterward.
Thanks for all who almost kinda tried to care to reply in this past 2 hours =) -- As previously mentioned.. I am a nerd.. I just suck at phone modding. Haha
So , looks like I'm in the clear now and don't need any more support on this particular topic yet.
Click to expand...
Click to collapse
Is this true? Through a recommendation (haven't done anything to my phone from rooting/flashing KANGSJUGGERNAUT2 years ago), I tried to flash CM10 and ended up with a bootloop myself. Tried flashing through ODIN but it kept crashing; does anyone know why?
Afterward, I tried to reflash it through CWM and from then on bootloops into a installation process that never completes.
For some reason my CWM turned super slow, freezes/hangs and reboots after a few minutes.
I gave the phone to a friend who does this stuff on the regular but he said my initial flash wasn't complete cause in download mode says I'm still running official? No clue.
I was told this via email/chat: "No luck, it won't even boot anymore, I think I'll just bring it back tmrw morn
10:43 PM
Sorry I'm at a wedding (yea I know random) I left my phone with coat check
OK I've narrowed down the reason but not the solution, you had an AOKP based ROM which fundamentally is based on CyanogenMod, but it wasn't correctly flashed as the phone still thought it has factory ROMs still running
11:10 PM
Clockworkmod(even though it was working before) wasn't accessing the partitions of the phone correctly so it wasn't properly wiping or flashing properly.
11:12 PM
So basically from the first time you flashed cwm it didn't flash properly then the next time you flashed using the new recovery it didn't flash anything it was supposed to do itself properly , so basically it was a chain of events in addition to a bad boot loader, that's why it never went to recovery or download mode correctly
11:13 PM
That's something that had to do with the way the phone was built meaning you may of had a bad bootloader from the very begin and are now feeling the synptoms
Basically, and I would hate to be the reason or partially the reason you have a dead phone, basically it was a matter of coincedencr that it happened as this could of happened at anytime, once you have a bad boot loader its pretty much down hill from there"
Any helpful insight as how I can rectify this? is my phone truly dead? Sorry about the quoted format, it was copied and pasted.
If I were in your boat, I'd use Odin and flash the stock 4.1.2 ROM.
Sent from my Nexus 7 using Tapatalk 4 Beta
tronmech said:
If I were in your boat, I'd use Odin and flash the stock 4.1.2 ROM.
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
The phone won't turn on, unable to go into recovery and download mode; plugged in usb (hear connection beep but pressing power button plays disconnect button) to no avail. What can I do to unbrick?
Stock 4.1.2? Possible over a hardbricked T989 with old 2.3.6?
JahJahLoO said:
The phone won't turn on, unable to go into recovery and download mode; plugged in usb (hear connection beep but pressing power button plays disconnect button) to no avail. What can I do to unbrick?
Stock 4.1.2? Possible over a hardbricked T989 with old 2.3.6?
Click to expand...
Click to collapse
sorry but i have to assume that you are not doing the 3 button recovery or download mode right.
Pull battery, put battery back in, hold power button & Vol +/- untill you see SAMSUNG on the screen ---> let go off power button(keep holding
Vol +/- button) .....u will see recovery. (assuming you did flash cwm before).
Let me know.
hit thanks.
sam.balia1012 said:
sorry but i have to assume that you are not doing the 3 button recovery or download mode right.
Pull battery, put battery back in, hold power button & Vol +/- untill you see SAMSUNG on the screen ---> let go off power button(keep holding
Vol +/- button) .....u will see recovery. (assuming you did flash cwm before).
Let me know.
hit thanks.
Click to expand...
Click to collapse
I believe I am doing it correct, I have been entering recovery and download mode many times, right before I soft bricked it.
And sorry, no, I've tried many times, many methods and my phone is confirmed as entirely hard bricked.
SUPAR SAD, but thank you!
dont give up
JahJahLoO said:
I believe I am doing it correct, I have been entering recovery and download mode many times, right before I soft bricked it.
And sorry, no, I've tried many times, many methods and my phone is confirmed as entirely hard bricked.
SUPAR SAD, but thank you!
Click to expand...
Click to collapse
you can try using adb and put the phone in dl mode.
sometimes its as easy as pull battery and wait awhile (20 min or more) and try again.
if you've exhausted all possibilities, you can use a jig to force a dl mode.
let me know
sam.balia1012 said:
you can try using adb and put the phone in dl mode.
sometimes its as easy as pull battery and wait awhile (20 min or more) and try again.
if you've exhausted all possibilities, you can use a jig to force a dl mode.
let me know
Click to expand...
Click to collapse
I don't know what adb is, or how to use it; I have, however seen my friend RDP to my desktop and do something and used the term 'adb' in his attempt to code through the phone.
I've done that battery waiting period, for nearly an hour and still no result.
After doing some researching, I have found that many people have stated a USB JIG would not be applicable to a 'hard bricked' phone. I really wanted to try as it looked like the most, simple and inexpensive solution.
JahJahLoO said:
I don't know what adb is, or how to use it; I have, however seen my friend RDP to my desktop and do something and used the term 'adb' in his attempt to code through the phone.
I've done that battery waiting period, for nearly an hour and still no result.
After doing some researching, I have found that many people have stated a USB JIG would not be applicable to a 'hard bricked' phone. I really wanted to try as it looked like the most, simple and inexpensive solution.
Click to expand...
Click to collapse
If you know for a fact that you bricked your s2, maybe wrong rom or kernel that u flashed by accident then.....
contact these guys.... http://brickedmyphone.com/contact-me/
good like and click thanks if you agree.
sam.balia1012 said:
If you know for a fact that you bricked your s2, maybe wrong rom or kernel that u flashed by accident then.....
contact these guys.... http://brickedmyphone.com/contact-me/
good like and click thanks if you agree.
Click to expand...
Click to collapse
Lols, you're really fishing for them "Thanks"; you got it buddy. Very swift responses. :cyclops:
Anyway, I'm still searching the net for anymore possible solutions.
Thanks.
JahJahLoO said:
Lols, you're really fishing for them "Thanks"; you got it buddy. Very swift responses. :cyclops:
Anyway, I'm still searching the net for anymore possible solutions.
Thanks.
Click to expand...
Click to collapse
fishing for them ???????
what the hell does that even mean? it seems that brick did hit u in the head!!!
sam.balia1012 said:
fishing for them ???????
what the hell does that even mean? it seems that brick did hit u in the head!!!
Click to expand...
Click to collapse
It might as well have... :crying:
Hello Im Terry
Well this is far from my first root and flashing roms to phones....
i recently got a lg g2 sprint device 4.2.2, and of course i came here to root it, now the root was simple went through fine using a method i found here on the site... after this i wanted to put a different rom on it... well i installed twrp recovery, then i was trying to boot up into recovery, it wouldnt work at all whatsoever, wether i tried turning the phone off and holding the power and volume down button, releasing when screen turns on for a second then pushing them both again... this would just load the normal sprint screen, so i would try through the twrp program to reboot into recovery and the exact same thing happened.....so i googled it and i found this method to "supposably" fix it...
teamw.in /project/twrp2/197 <----- sorry about the space there but the forum wouldnt let me post the link and i cant describe what i did to cause my problem if i cant post this link.
i used the method here with the file for sprint phones.
now after doing this i tried to reboot into recovery mode using the power and volume down method, still nothing, so then i tried through the twrp program, well what happens is a screen comes up, which when ive searched this its only people that cant get past this screen and there phone is soft bricked.... [470] fastboot mode started and on the line under that it says [520] udc_start()
this is a black screen and it stays there.... now i found a file here that a guy put on the phone to help get wifi working, which i can be happy with the phone if i cant figure out how to put a rom on the phone if i can atleast be able to tether my phone since that is one of the main reasons i root, well when i tried to flash this file using the twrp program with the phone on it rebooted to the black screen with fastboot and udc_start
so basically i cant get into recovery mode at all, and i havent been able to this entire time, i could never even get to the initial sprint option to erase all settings holding those 2 buttons down.
now obviously i want to fix this, i want to figure out how to get into recovery mode. and i just got this phone from sprint 2 days ago so it already has the sprint spark update, im not sure if that what might be causing all of this if its incompatible with sprint spark or not... i know the 1 rom i looked into said it was incompatible with it, but i didnt see anything with the others....
so after figuring out how to get into recovery mode and fix my recovery mode can someone please tell me which of the roms that are currently out for my phone are compatible with sprint spark if any. thanks so much and i hope somebody can help me. have a great day and take care
well just a quick update, i uninstalled and reinstalled twrp now this is what i get when trying to boot into recovery from the app
[470] fast mode started
520 udc_start()
690 - reset -
700 -port change-
890 STALL GET_DESCRIPTOR 128 6 1006 0 18
60710 fastboot: processing commands
Trippinshrumes said:
Hello Im Terry
Well this is far from my first root and flashing roms to phones....
i recently got a lg g2 sprint device 4.2.2, and of course i came here to root it, now the root was simple went through fine using a method i found here on the site... after this i wanted to put a different rom on it... well i installed twrp recovery, then i was trying to boot up into recovery, it wouldnt work at all whatsoever, wether i tried turning the phone off and holding the power and volume down button, releasing when screen turns on for a second then pushing them both again... this would just load the normal sprint screen, so i would try through the twrp program to reboot into recovery and the exact same thing happened.....so i googled it and i found this method to "supposably" fix it...
teamw.in /project/twrp2/197 <----- sorry about the space there but the forum wouldnt let me post the link and i cant describe what i did to cause my problem if i cant post this link.
i used the method here with the file for sprint phones.
now after doing this i tried to reboot into recovery mode using the power and volume down method, still nothing, so then i tried through the twrp program, well what happens is a screen comes up, which when ive searched this its only people that cant get past this screen and there phone is soft bricked.... [470] fastboot mode started and on the line under that it says [520] udc_start()
this is a black screen and it stays there.... now i found a file here that a guy put on the phone to help get wifi working, which i can be happy with the phone if i cant figure out how to put a rom on the phone if i can atleast be able to tether my phone since that is one of the main reasons i root, well when i tried to flash this file using the twrp program with the phone on it rebooted to the black screen with fastboot and udc_start
so basically i cant get into recovery mode at all, and i havent been able to this entire time, i could never even get to the initial sprint option to erase all settings holding those 2 buttons down.
now obviously i want to fix this, i want to figure out how to get into recovery mode. and i just got this phone from sprint 2 days ago so it already has the sprint spark update, im not sure if that what might be causing all of this if its incompatible with sprint spark or not... i know the 1 rom i looked into said it was incompatible with it, but i didnt see anything with the others....
so after figuring out how to get into recovery mode and fix my recovery mode can someone please tell me which of the roms that are currently out for my phone are compatible with sprint spark if any. thanks so much and i hope somebody can help me. have a great day and take care
Click to expand...
Click to collapse
Since your phone is only new, have you tried calling the tech support of Sprint? Or have you tried going to Sprint store to help you out with that?
to the post above me... yea that sounds like a great idea, hey sprint can you help me root my phone so i can tether without you charging me? thanks guys!... can you please not troll? if you're not going to help you dont have to respond. Thanks!
so i followed this post now, what i didnt do was patch loki on the newer vza firmware.... so i followed this thread here which is supposed to fix that... and yet im still having the same thing, btw as i posted the change in commands before its because i had my phone plugged into my computer that it showed me that.
forum.xda-developers.com/showthread.php?t=2522965
im not sure what im doing wrong here, but as i go through this i will surely document it incase someone else runs into the same problem in the future.
thanks for any help in advance
i made a mistake when i was doing this.... after everything when it says to use flashify to find the file... it wants you to find what is now the updated twrp 2.6.3.3 version and flash that as the last step... this is now complete. if anyone else runs into this in the future hopefully you dont do something slightly stupid like i did. thanks again xda developers cuz your all some genius ass people with all this info here
Trippinshrumes said:
well just a quick update, i uninstalled and reinstalled twrp now this is what i get when trying to boot into recovery from the app
[470] fast mode started
520 udc_start()
690 - reset -
700 -port change-
890 STALL GET_DESCRIPTOR 128 6 1006 0 18
60710 fastboot: processing commands
Click to expand...
Click to collapse
Turns out you have to downgrade your ABOOT, I had the same problem .. ...
http://forum.xda-developers.com/showthread.php?t=2627765
Follow those instructions to downgrade to zv7-aboot.img, then use FLASHIFY to flash the TWRP recovery image .. ...
also, the problem i was having with booting into recovery is i just have to hold the power and volume down buttons till i get the recovery menu.... not let go when the light comes on like a bunch of things say....
also if anyone knows, it says the d3rp g2 rom doesnt work on spark that it will guaranteed brick my device, now i have it fully backed up and i could just do a test run and see... although i dont feel like having to mess with that....
has anyone successfully flashed d3rp to the spark version? and if that is incompatible none of the other roms mention anything about it.... so if someone could tell me which roms do work on the spark version i would appreciate that...
also +1 to the guy that offered help after i figured it out. i appreciate it!
Last night I installed geefree on my phone from the app store and used it to install TWRP. I downloaded a nightly CM11 and an appropriate gapps. Using geefree I rebooted to recovery (never figured out the button combination to boot to recovery "naturally") and installed both of the zips. This could be where I made my mistake, I installed both at the same time.
Now my phone loops, displaying the LG logo for a few seconds, then shutting off and rebooting before repeating the process. I can't seem to get it to go into download mode or the recovery menu. I've tried power+up, power+down, down+up and each of those while plugging the device in, etc. I can get the device to a hardware key control mode, though it doesn't seem too useful.
How can I save my phone? This forum has been a great resource in the past and I'm very grateful for the many tutorials I've followed rooting other devices. Hopefully you guys can save the day once again!
Volume up plus power is how to access recovery on sprint.
What stock sw version were you on before you flashed cm?
Did you wipe data before flashing?
Sent from my LG-LS970 using xda app-developers app
I was using stock 4.2.2, I believe. I didn't wipe the data (shame on me), a bad habit that I picked up from my first rooted device, the Samsung Moment. It didn't ever matter on that one, afaik. Thanks for the reply!
Edit: Volume up and power whether plugged in or not takes me to the hardware key control mode screen.
Second Edit: http://forum.xda-developers.com/showthread.php?t=2432476&page=35 I also found this thread where someone seems to be experiencing similar issues and they fix it with "LG Utility." Is that a PC application? It's a little vague to google, but I've been trying!
I have a bootloop issue every time i flash a rom i have to wipe all but sd flash roms and gapps the i do a restore from twrp and oly restore my boot image only and they boot no prob
I'm kind of starting to suspect my power button doesn't work at all for whatever reason. I have a lot of difficulty getting the phone to shut down, then it doesn't seem to easily power up. It's a strange collection of problems. Would a Sprint repair place be able to fix this?
If they have parts on hand if not either a swap out or a sendoff
Same problem here - bootloop and no download mode - CWM works! - urgently need help
I guess I have the same problem as InlineFourPower (apart from that my power-button has no problem).
I am stuck in bootloop since I tried to upgrade to Kitkat a few days ago. Now I can´t get into download mode any more, nor into fastboot or anything else. Only CWM works.
From within CWM I can successfully flash ROMs but that doesn´t help, since afterwards I am still stuck in bootloop. It is possible, however, to push files via adb-commands while I am in CWM.
Does anybody have an idea how to go from here or how to get download-mode back?
Device is recognized but can´t be mounted - bricked forever?
Parinibbana said:
I guess I have the same problem as InlineFourPower (apart from that my power-button has no problem).
I am stuck in bootloop since I tried to upgrade to Kitkat a few days ago. Now I can´t get into download mode any more, nor into fastboot or anything else. Only CWM works.
From within CWM I can successfully flash ROMs but that doesn´t help, since afterwards I am still stuck in bootloop. It is possible, however, to push files via adb-commands while I am in CWM.
Does anybody have an idea how to go from here or how to get download-mode back?
Click to expand...
Click to collapse
I tried a few things on Linux.
After terminal-command "ls /dev/sd*" when the device is unplugged from the computer I get "/dev/sda".
When the device is connected via USB, I get: "/dev/sda /dev/sdb"
So sdb is my LG G2.
So I went on to the next command: "gdisk -l /dev/sdb"
As a result I get: "Problem opening /dev/sdb for reading! Error is 123."
Does it mean that the phone isn´t mounted or what? Now I´ve connected my phone to another Linux machine with the same result. It is recognised (p.e. as sdd), but there is no sdd1. Seems as if it is recognized, but can´t be mounted. Does that mean my device is bricked for good? That´s it?
to get the phone into download mode you have to plug the usb cord in and hold VOL+, so to get this right as I have a case on mine, plug the usb into the phone first then hold VOL+ and plug into usb port on the computer.
it does take a loooong time to power down the phone with the button when stuck in a boot loop, just keep holding it until it shuts off, it will shut off eventually!!
plug the phone in while in download mode to install drivers and set com ports, then unplug before you begin your flash with LGFlashTool, hope this helps you out.
Cronic2009 said:
to get the phone into download mode you have to plug the usb cord in and hold VOL+, so to get this right as I have a case on mine, plug the usb in first then hold VOL+ and plug into usb port.
it does take a loooong time to power down the phone with the button when stuck in a boot loop, just keep holding it until it shuts off, hope this helps
Click to expand...
Click to collapse
Thanks Cronic2009 for your advice.
There are, however, szenarios where download-mode is not accessible any more. Neither by using the hardware-keys, nor by using the adb-command.
After four days of resarch and a lot of trial and error, I finally unbricked my F320L using the two adb-commands outlined at the beginning of that thread: http://forum.xda-developers.com/showthread.php?t=2451696
Worked like a charm.
Thanks everyone for your advice.
no problem buddy, glad you got it figured out, good luck to you from here on out!
FYI, that link doesn't work
I just wanted to ask anyone who might know, since the bootloader of the LS980 is locked, we cannot "break" this correct, so no matter what commands we decide to run through root, we cant touch the true bootloader there for LS980 fail safe? (Besides Acts of God, EMP, ect)
Cronic2009 said:
no problem buddy, glad you got it figured out, good luck to you from here on out!
Click to expand...
Click to collapse
Thanks for letting me know. I corrected the link in my previous post.
Be sure if you use a aosp based rom to flash the ZV8 modem. Your can use dr87 or furnance kernals after you flash the zva modem althought i have encountered soft brick due to this.
so i'm having this exact issue and i don't know how to get out of it. i just need to transfer the radio to my phone somehow but nothing shows up under adb devices. i'm trying to the lg mobile support tool now. its downloading the software. but if it doesn't work does any one have any fixes?
edit: i fixed it by following this http://forum.xda-developers.com/showthread.php?p=51637410&highlight=download+fail#post51637410
pitbullmommy45245 said:
so i'm having this exact issue and i don't know how to get out of it. i just need to transfer the radio to my phone somehow but nothing shows up under adb devices. i'm trying to the lg mobile support tool now. its downloading the software. but if it doesn't work does any one have any fixes?
edit: i fixed it by following this http://forum.xda-developers.com/showthread.php?p=51637410&highlight=download+fail#post51637410
Click to expand...
Click to collapse
Thank You for sharing you fixed your issue pittbullmommy but the link you posted points back to a post about a failed run on LGFlashTool, will you please fix the link and point it to the post/guide you used to fix your phone, it may help others stuck in a similar situation, glad to hear you got it fixed and working, best of luck with it from here on out!
Hi all
was just about to start a new thread but didn't want to get into trouble..anyway I am in need of some assistance please.my ls980 has been bricked for some time now been searching all over the internet for a solution to be stuck back at square one.found this video on youtube which is pretty much exactly what my phone is doing.I have used lg flash tool to revert to stock and still nothing I lost root doing that but last night,I managed to regain root access I have no idea how but it happened when i clicked ioroot batch file i went into download mode and it stated bottom left ROOTED in red so i managed that but that is it still doing what is being shown in the video its on youtube
watch?v=PjLF-pBhZSY
please if anyone has the know how I would like to fix this phone rather then bin it thank you all happy 4th everyone
After using tot and flash tool to get back to stock, did you try going into stock recovery and do a factory data reset? I know it sounds stupid especially after a tot but try it. Couldn't hurt
Sent from my LG-LS980 using Tapatalk
Borderline noob here, so please bear with me...
I have been using TWRP 2.7.0.0 to do all my work, and I was able to get the Lego ROM installed with ZVA. I got into too big of a hurry and forgot to make a backup of stock. I've also been unsuccessful in trying to install ZVC modem and firmware. Thankfully ZVA works as does the LEGO ROM, but I'd like to have stock there to access as well. The stockZVC that's on the Android Development page has been getting stuck (bootloop?) on the Sprint Spark logo. I've done TWRP's factory reset with no success. Any help would be great.
Thanks in advance!
Yes sir I've tried that and more to no avail is there anything I can do through adb I'm on stock recovery phone doesn't stay on long enough to install anything
sarfdawg said:
Borderline noob here, so please bear with me...
I have been using TWRP 2.7.0.0 to do all my work, and I was able to get the Lego ROM installed with ZVA. I got into too big of a hurry and forgot to make a backup of stock. I've also been unsuccessful in trying to install ZVC modem and firmware. Thankfully ZVA works as does the LEGO ROM, but I'd like to have stock there to access as well. The stockZVC that's on the Android Development page has been getting stuck (bootloop?) on the Sprint Spark logo. I've done TWRP's factory reset with no success. Any help would be great.
Thanks in advance!
Click to expand...
Click to collapse
You ever get her fixed?