I Screwed Up--HELP!! - T-Mobile LG G3

Alright, I have a T-Mobile LG G3 and I rooted it and installed the Skydragon ROM. Everything was working and I accidentally wiped my ROM. This deleted everything from my internal storage except TERP. I then downloaded the skydragon rom zip file onto and external SD card using a different G3. I them put the ext card into my G3 and used TWRP to install that file. It ran through the setup procedure and shows that is successfully installed. The problem is that the phone always boots to TWRP and won't go any further. Any ideas on how to fix this issue?

Youll need to flash the phone to untoched stock using LGs flash tool. Youll find the files and instructions on the tmobile lg g3 general forum. I ran into the same problem.

I saw that tool and unfortunately the phone hard bricked when I was trying to flash a rom from an external sd card. It will not boot at all, it is like it has no power. I tried to charge the phone but it was a no go. The led light won't even come on. I took the phone to t mobile, it is 2 days old, and they replaced it free of charge. I got real lucky on this one!

izoid1 said:
I saw that tool and unfortunately the phone hard bricked when I was trying to flash a rom from an external sd card. It will not boot at all, it is like it has no power. I tried to charge the phone but it was a no go. The led light won't even come on. I took the phone to t mobile, it is 2 days old, and they replaced it free of charge. I got real lucky on this one!
Click to expand...
Click to collapse
I used LG Flash Tool because my G3 was softbricked but everythis was ok then rooted and flashed zone rom.

Related

In need of depsperate help!!!

Try to flash to JH2 (and repartition 512) - the stock B model firmware.
If it fails - try to push one of complete roms (doc_kalpik) and install it using clockwork.
Otherwise have no idea what is wrong.
.....
I will download the firmware files now,
any instructions on how to use clockwork? and install the complete rom?
Did you perform a repartition when you reflashed ?
ignore me wrong thread!
inshadesofgrey said:
I will download the firmware files now,
any instructions on how to use clockwork? and install the complete rom?
Click to expand...
Click to collapse
isnt there a install guide in doc-kaplik topic? In clockwork (might need to push update.zip and rom manually - dont remember how) choose install zip from sdcard and navigate to file you need.
i did......still didnt work
Sounds like what mine was doing when the internal SD died.
dupel said:
isnt there a install guide in doc-kaplik topic? In clockwork (might need to push update.zip and rom manually - dont remember how) choose install zip from sdcard and navigate to file you need.
Click to expand...
Click to collapse
will this work even if i didnt have clockwork on my phone?
I flashed the stock JH2 with 512.pit and reparition checked, but the phone goes to the samsung logo, and flash animation and to a blank screen with only the buttons lit up........ah, am losing all hopes really fast.
Now that you are on jh2 take out sim leave external sd inside charge it til full, turn on while and it will boot, saying no memory going internal or external.
So far that would be doa, unless someone found a way to fix or reformat external card but most people that sent it for repair with these symptoms had done doa exchange like me twice or samsung replaced external module meaning it was hardware issue. Sorry.
Sent from my i9000M
it's a long shot, but can I buy an external SD card and run android from there?
I am guessing the only hope is to buy a new phone then?
inshadesofgrey said:
Hi guys, I have been a silent observer of XDA for a while now and you guys have helped through the past 4-5 phones that I've had - but now, I am stuck, so I thought I'll ask for help.
I have a galaxy S (i90000-GT) - originally from Bell, Canada but unlocked. I was running the XJPH with lag-fix and two days ago, when the phone rebooted, it got stuck in a boot loop, samsung logo with black screen comes on, and it starts all over again. Now, I can get into download mode and I followed the process to install JM8, and the stock file (the US Vibrant stock file) and I tried this as well:howto-froyo-fw-i9000xxjpm-upgrade-via-odin-root-recovery-2e-lagfix/[
But to no avail. The boot loop is still there. With JM8, the phone boots up and the goes beyond the flash samsung logo (with the music) but loads to a black screen, with the lights on.
Am really frustrated as this is my only work phone (and I go back to work tomorrow). Without the phone, I am pretty much screwed. I dont care about the Data on the phone (have performed 3-4 data wipes during installing the above mentioned roms) . So anything you can advise, will help!
any ideas?
Click to expand...
Click to collapse
Have you wiped your data/factory reset & wiped your cache? Many phones get stuck at startup because of them.

Galaxy Note II N7100 Not Booting

Hi All,
This is my first post here and I really would appreciate any help one of you experts here could give me.
So to cut a long story short, I purchased my shiny new Note II yesterday, today I tried to root it and install a custom ROM. The rooting part went fine however since trying to install a custom ROM the phone is now no longer turning on but instead is getting stuck at the loading screen.
The phone.....
The phone is a Vodafone UK handset however was unlocked and I've been using my o2 sim card in there since I got it yesterday.
What I did.....
The first thing I did was root it using Odin3 v1.85. This part went fine and I successfully installed SuperUser.
Next what I wanted to do was install Android Revolution HD Custom ROM so I took out the SD card, put it in the SD card reader on my laptop and copied over the "Android_Revolution_HD-Note2_4.2" and "Android_Revolution_HD_Super_Wipe_Note_2". I then went into the menu (holding down Vol Up, Home, Power) and first flashed the Super wipre then the ROM. The super wipe went fine but not the ROM. When I tried to install the rom I was given an error message. I then tried again with version 4.2 and it looked like it was going to work but didn't. My phone is now not booting.
Somebody PLEASE help, it would really mean a lot!
Thanks!
Tommy
tcorbyn said:
Hi All,
This is my first post here and I really would appreciate any help one of you experts here could give me.
So to cut a long story short, I purchased my shiny new Note II yesterday, today I tried to root it and install a custom ROM. The rooting part went fine however since trying to install a custom ROM the phone is now no longer turning on but instead is getting stuck at the loading screen.
The phone.....
The phone is a Vodafone UK handset however was unlocked and I've been using my o2 sim card in there since I got it yesterday.
What I did.....
The first thing I did was root it using Odin3 v1.85. This part went fine and I successfully installed SuperUser.
Next what I wanted to do was install Android Revolution HD Custom ROM so I took out the SD card, put it in the SD card reader on my laptop and copied over the "Android_Revolution_HD-Note2_4.2" and "Android_Revolution_HD_Super_Wipe_Note_2". I then went into the menu (holding down Vol Up, Home, Power) and first flashed the Super wipre then the ROM. The super wipe went fine but not the ROM. When I tried to install the rom I was given an error message. I then tried again with version 4.2 and it looked like it was going to work but didn't. My phone is now not booting.
Somebody PLEASE help, it would really mean a lot!
Thanks!
Tommy
Click to expand...
Click to collapse
Sounds like you placed the ROM on your external SD card and the phone cannot find it or you did not select it.
If CWM allows mount the phone in recovery and hope BOTH SD card are mounted. Move the ROM to the Internal SD card and flash from there. OR you can flash the zip from you Internal card. IF it will mount in recovery.
OR if you have a TAR file of the ROM use Odin to flash it.

[Q] Need help un-soft bricking my T-Mobile M8

Hello,
I have an HTC One M8 (T-Mobile) that I had a friend root (he has a PC, I have a Mac, plus he's done it before) and all was going well until I installed a rooted app (I think it was Super SU or something) and my phone went into a boot loop, showing nothing but the HTC logo when I tried to turn it on. I panicked, even though it wasn't the end of the world, as I had just bought this phone from a classifieds source and had no personal info/pictures/contacts/anything on it yet.
However, I am still stuck with a soft bricked phone. My friend suggested going into recovery mode and rebooting (see attached picture) but it didn't help. Then he tried side-loading a ROM onto the device, but his computer (both of them, PCs, and even his brother's PC for good measure) didn't show it recognized the phone anywhere in the file system. And he said he looked EVERYWHERE and tried everything. Then he tried downloading HTC's own proprietary system for installing a custom ROM (I forget what it's called) but his PC wouldn't recognize it, so he couldn't use it either). He all but gave up on trying to restore my phone to how it was after he ran into the last of these problems.
I, however, refuse to believe that with the wealth of knowledge at my disposal via the internet that there is no way to fix this, even though I have a Mac. Is there ANYONE who's patient and Terminal-savvy that can help me get my M8 back to normal working condition? I don't even care about rooting it anymore. Thanks in advance for your instructions/suggestions.
I would just go into TWRP and mount the internal storage as usb, copy a ROM to the phone, umount internal storage and do a full wipe and install the ROM.
Do you want Stock, modified stock, CM??, GPE? you just need to figure out which version of ROM you want.
I think I already tried this...
I was just trying to install the stock firmware via a micro USB but the phone wouldn't recognize it on the micro USB stick in TWRP, is there a reason for this? As I'm assuming a restore to stock firmware is impossible if it can't recognize or read the firmware I'm trying to restore it to. Thank you
Hello? Anyone?

[Q] Can't debrick SGH-1747M using SD card method...

FINAL UPDATE:
Everything worked out fine. The phone went to 50% charge, I took it off charge, and it booted normally. Now I'm installing the stock firmware, and I guess I can move on from there. I hope this is useful for anyone else. The debrick image that finally worked out for me was I747M_NE6_128
UPDATE:
Ok I think I might have have something working. My battery was dead which is why I wasn't going into download mode. I saw somewhere one of the SD card methods saying that once I put my SD card into my phone after I have placed the image on it, I should connect it with my computer. I did so and tried booting and I felt a vibration (the one you feel when you're booting your device normally). My phone showed the grey battery symbol, then it showed the "Samsung Galaxy S III" text, with the Crynogen ROM guy on the bottom. Finally it is now showing my battery charging (battery icon matches Lollipop firmware I had on). Also I'm not sure if this is normal behavior for a hardbricked phone, if it is then nothing has changed. Though, when I plugged it into my computer, some Samsung ABD thing installed, and now everytime I plug it in, some MTP thing attempts to install but fails (so no QHUB thingy).
Now I want to know (if the device boots up after full charge), how do I proceed from here? I try to put it into download mode, and install a 4.4.2 stock firmware? I want to be able to use my SD card for other purposes.
OLD:
I'm having trouble debricking my SGH-1747M Telus. I have tried all of the debrick images found in this video:
https://www.youtube.com/watch?v=8MnikrpUKZw
But nothing works. My phone was debricked after I installed a Lollipop ROM from this thread:
http://forum.xda-developers.com/galaxy-s3-sprint/development/rom-unofficial-cm12-lollipop-t2953040
The ROM installed perfectly fine but the camera wasn't working. So I tried the fix from this video and flashed the camera file:
https://www.youtube.com/watch?v=U8obKmPrAh4
It hard bricked my phone, it just wasn't for my device (stupid me). Now I saw the debrick method using an SD card, I bought a 16GB class 10 SD card:
http://www.thesource.ca/estore/prod...ne&category=Memorycard_miniSD&product=8017621
I have tried all the debrick images but none worked. I'm not sure what my bootloader was, but I have tried both 4.3 and 4.4.2. I was expecting one of them to work, or something to work since I didn't do something like flash the wrong bootloader or remove my battery midway through installation, so I'm surprised nothing has worked thus far.
If someone can provide some more debrick images (for SGH-1747M d2att or d2lte) or point me in the right direction, it would be great.
It's just that I didn't do anything crazy like install the wrong bootloader, so I was really hoping it would have been unbricked using the method.

[Q] Phone Won't Boot - Possibly dead eMMC

Hello XDA,
Recently, a Samsung Captivate Glide was given to me to see if I could repair it. They told me the phone wouldn't turn on anymore, the screen remained black. Although they said they had just replaced the battery, I insisted that the battery was the problem. Upon hooking it up to a multimeter it became apparent that the battery was in deep sleep so I recovered it with a sliced USB cable. The phone then turned on to charge, but since I didn't feel like waiting for it to charge I inserted my S2 battery to boot it up.
Upon booting up the phone the Rogers screen came up (it's the Rogers model - sch-i927r), it adjust the brightness a bit and then proceeded to sit there forever. Since it wouldn't boot up I tried checking if Download Mode was still working. And it was! Same goes for the Android Recovery. Since this phone was never rooted or had a custom recovery it still had Gingerbread. Since the owner needed some files that were still on the phone I decided to flash TWRP, the CM11 compiled one, copy all the files to my PC and proceed to flash CM11 after making a backup.
However the phone refused to flash TWRP. I also tried CWM and going back to Stock but had no positive results. I even tried different Odin versions and different PCs. All of them gave out the same error that I have attached as a Picture. Upon googling it it seems like the storage is in read only mode, which I learnt from the Galaxy Tab 10.1 forums and also that the only solution would be to go back to Samsung.
Lastly I attempted to wipe from the built in recovery It asked for a password, however the original owner claimed he never had one. Upon forcing the flash by entering the wrong password the phone said it completed successfully but looking at the internal storage proves otherwise as all the files are still there. Trying to reboot to the system makes it either go to a black screen or corrupt the GPU memory (possibly - see attached pics.).
Looking around on the XDA forums I stumbled upon a thread by @steadfasterX which made a mod to boot the phone from an SD card. Since the eMMC of the phone is likely corrupt and causing this, could we use an SD card as the internal storage and boot up from there?
I am out of ideas. I don't have a backup of the EFS so I am being really cautious and fixing it wouldn't be worth it. So please help me! Any help is very much appreciated!
Thanks in advance!
chrismin13 said:
Hello XDA,
Recently, a Samsung Captivate Glide was given to me to see if I could repair it. They told me the phone wouldn't turn on anymore, the screen remained black. Although they said they had just replaced the battery, I insisted that the battery was the problem. Upon hooking it up to a multimeter it became apparent that the battery was in deep sleep so I recovered it with a sliced USB cable. The phone then turned on to charge, but since I didn't feel like waiting for it to charge I inserted my S2 battery to boot it up.
Upon booting up the phone the Rogers screen came up (it's the Rogers model - sch-i927r), it adjust the brightness a bit and then proceeded to sit there forever. Since it wouldn't boot up I tried checking if Download Mode was still working. And it was! Same goes for the Android Recovery. Since this phone was never rooted or had a custom recovery it still had Gingerbread. Since the owner needed some files that were still on the phone I decided to flash TWRP, the CM11 compiled one, copy all the files to my PC and proceed to flash CM11 after making a backup.
However the phone refused to flash TWRP. I also tried CWM and going back to Stock but had no positive results. I even tried different Odin versions and different PCs. All of them gave out the same error that I have attached as a Picture. Upon googling it it seems like the storage is in read only mode, which I learnt from the Galaxy Tab 10.1 forums and also that the only solution would be to go back to Samsung.
Lastly I attempted to wipe from the built in recovery It asked for a password, however the original owner claimed he never had one. Upon forcing the flash by entering the wrong password the phone said it completed successfully but looking at the internal storage proves otherwise as all the files are still there. Trying to reboot to the system makes it either go to a black screen or corrupt the GPU memory (possibly - see attached pics.).
Looking around on the XDA forums I stumbled upon a thread by @steadfasterX which made a mod to boot the phone from an SD card. Since the eMMC of the phone is likely corrupt and causing this, could we use an SD card as the internal storage and boot up from there?
I am out of ideas. I don't have a backup of the EFS so I am being really cautious and fixing it wouldn't be worth it. So please help me! Any help is very much appreciated!
Thanks in advance!
Click to expand...
Click to collapse
you can not boot from sd card, you can use sd card as system partition, but you still need place kernel+ramdisk on internal flash.
You can try to replace bootloader
bubor said:
you can not boot from sd card, you can use sd card as system partition, but you still need place kernel+ramdisk on internal flash.
You can try to replace bootloader
Click to expand...
Click to collapse
Thanks for the reply, I'll try updating the bootloader. Would it be risky though? I couldn't flash anything else and have no nandroid backup. Also, how would I go about using the SD Card as system?
EDIT: Risked it, flashed correctly but I still get the same error and I still have the Rogers bootloader. Any other ideas?
chrismin13 said:
Thanks for the reply, I'll try updating the bootloader. Would it be risky though? I couldn't flash anything else and have no nandroid backup. Also, how would I go about using the SD Card as system?
EDIT: Risked it, flashed correctly but I still get the same error and I still have the Rogers bootloader. Any other ideas?
Click to expand...
Click to collapse
maybe check "phone bootloader update" on the left side, I think I didnt check when I did update, and it worked without checking.
First try this pack: http://dualhoki.vim.hu/bubor/dev/I927UCLG9_OneClick.exe
Try to repartition with pit file ( put pit file in pit box, no other files, and check re-partition)
You can find an alternative of odin http://glassechidna.com.au/heimdall/ . I remember there are many other options in heimdall, maybe you can find usefull error messages.
bubor said:
maybe check "phone bootloader update" on the left side, I think I didnt check when I did update, and it worked without checking.
First try this pack: http://dualhoki.vim.hu/bubor/dev/I927UCLG9_OneClick.exe
Try to repartition with pit file ( put pit file in pit box, no other files, and check re-partition)
You can find an alternative of odin http://glassechidna.com.au/heimdall/ . I remember there are many other options in heimdall, maybe you can find usefull error messages.
Click to expand...
Click to collapse
Hello,
Sorry for the late response. I got around to trying most of that. First off the PIT File was something that I was looking forward to since it seemed the most likely solution. However it didn't work, giving out a similar message as everything else. The OneClick also failed with a similar message. As for heimdall I couldn't get the drivers to work but even if I had it wouldn't have helped anymore most likely.
I am out of ideas. I highly doubt this phone is recoverable at this point.
Thank you for all the help so far!
Anyone got any other ideas? I think it's safe to call it dead at this point, but I am willing to try anything to fix it!
Thanks.

Categories

Resources