[Q] Very,very bricked LG G2 - G2 Q&A, Help & Troubleshooting

OK guys I really need some help with this, I have an LGG2 that is rooted and was running on Cynogenmod 11. I also have TWRP recovery installed. Now as the device was rooted I was playing with some stuff to get Sky Go working as it wont work with root. I came across a thread which stated I should try editing the boot.prop file in /system. There is a line in this file about 5 to 10 lines down from the top which reads "test-keys". The advice in the thread was to change this to "release-keys". Now, to do this I used es-file explorer to locate the file. First I simply tried to edit it but it would not save the edit so then I tried to make a copy in the same directory. Es-file explorer stated it had made a copy but no icon appeared for the new file so then I copied the file to a new directory. This time the new file was created as expected so I re-named it to a .txt file made the change I wanted and saved it. I then moved this file back into the original /system directory it had come from and re-named the original file to a .txt then named the new file I had just changed to .prop on the understanding that the os would now use this new file. On re-starting my phone I got the LG logo an then nothing, when the power key was pressed the phone just vibrated twice.
No matter what I do I cannot get the phone to boot into TWRP or any other recovery mode. I have managed to boot into a firmware update mode and using the LG support mobile tool have re-flashed the stock rom. Now when the phone boots it goes past the LG logo screen and to the 3 mobile logo (they are my service provider) but then it just re-boots, gets to the 3 mobile screen and re boots again. Still I cannot get into TWRP or any other recovery mode so I am completely stuck as to what to do next. I can get the phone into the firmware update mode no problem but then phone is not appearing in My Computer. All I really want to do is get into the phone and delete the .prop file I created and restore the original, I presume if I do that the phone will boot properly and I can re-flash Cynogen but without the phone appearing in my computer I cannot do that and without TWRP I cannot re-flash Cynogenmod.
Does anyone have any other ideas I could try please.
Thanks
Ben

Related

HTC Tattoo bricked? Doesn't boot, goes to fastboot...

Hey!
This is the issue: when I try to turn the phone on by just pressing the red button it goes directly to the fastboor menu. If I try to go to the recovery from there shows "TATTOO" for hours. If i try to go to the recovery dirctly by pressing HOME+ red button, it firsto shows the fastmenu for a second and tries to boot unsuccessfully. During this boot tries, I try to get some info with adb logcat, but the device is not casting anything. And well, if a picture is worth a thousand words, I guess a video is way better:
youtube.com/watch?v=zAejyMIVNGk (newbie, no urls!)
sorry for my english
And well, I have no idea how I got to this, this used to be my phone, but I bought a Nexus One and gave this to my sister, who has no idea what happened (as usual). Oh, this morning somehow I managed to get to the recovery menu, and booted until the android bootscreen, then vibrated and died again. I got to the recovery again, made a nandroid backup and wiped all data, it booted successfully, but the rom had no home application and ran really bad.
I was about to try to make a goldcard and install the stock RUU rom, but if I have no adb I cannot make one...
Any idea?
PS: the rom was nFinity 1.18 (2.2 Froyo) and the recovery was the lastest Clockwork.
PS2: I just realized that in every place I say fastboot I mean HBOOT, sorry again
sounds like recovery is still there, if you hold home + menu when phone if off , and then click red power button you should get recovery menu.
Then hopefully you can try full wipe and install a rom , rember the first time u boot a rom might take a few minutes
let me know how it goes
Yup, not using that method but I can manage to get to recovery sometimes. I'm trying to flash another ROM, but for some reason it doesn't let me. I've tried KalimochoAz (gingerbread) and HDCR (donut) and says something about assertion failed when checking if the device was click on the first case and in the second, complains about unsupported stuff...
I was about to try another roms by random but the SD does not refresh or even mounts, there must be something really messed up with this phone...
You can try to flash your stock rom from fastboot.
You don't need a goldcard, just run the update utility on pc, go to your temp directory and take the rom.zip file, rename it to CLICIMG.zip, copy it to sd card, put card on device and on fastboot menu pres vol down to start flashing the rom. I is the same version with the rom that device has before rooting, you will not get any errors.
I think there's a little misunderstanding here, mainly because of my confusion, it's not the fastboot menu qhat I get, but the HBOOT menu, and pressing the back button in order to access fastboot doesn't work...
oh I managed to boot something, I renamed the RUU exe to CLICDIAG.zip, because I could not find anything in C:\temp (is there where I have to look for the file?)
anyway, the zip appears to load on the phone, but once the progress bar completes, nothing happens... In my computer, the zip contains a .txt file and boot.img, but appears to be corrupt, and cannot extract any file (obviously, it's an exe)
so what do I do?
manutenfruits said:
oh I managed to boot something, I renamed the RUU exe to CLICDIAG.zip, because I could not find anything in C:\temp (is there where I have to look for the file?)
anyway, the zip appears to load on the phone, but once the progress bar completes, nothing happens... In my computer, the zip contains a .txt file and boot.img, but appears to be corrupt, and cannot extract any file (obviously, it's an exe)
so what do I do?
Click to expand...
Click to collapse
Of course will not work like this.
You must first run the RUU utility on pc and while is open to search your temp directory(maybe is inside another folder) for rom.zip file. This is the rom, the executable is an installation program which contain the rom and the app to flash the rom from pc packaged. You need only the rom.zip for flashing from sd card.
I've looked in the whole hard disk for that rom.zip after executing the RUU (I cannot get further than the step that tries to detect the tattoo, failing, so maybe it's not even created).
Apart from that, I managed to boot twice to what seems to be gingerbread, nFinity 1.18, but says in the lower left corner "Safe Mode" and I have no home application, no action on any button, just the notification bar and the lock screen. ADB doesn't work either.
manutenfruits said:
I've looked in the whole hard disk for that rom.zip after executing the RUU (I cannot get further than the step that tries to detect the tattoo, failing, so maybe it's not even created).
Apart from that, I managed to boot twice to what seems to be gingerbread, nFinity 1.18, but says in the lower left corner "Safe Mode" and I have no home application, no action on any button, just the notification bar and the lock screen. ADB doesn't work either.
Click to expand...
Click to collapse
You don't need to go so far. Just run the ruu utility and when the first screen appears go to temp dir(c:\users\you user's name\local\appdata\temp on windows 7). The executable is an encrypted package and when you run it extracts all included files and then starts the installation program. These files will deleted after this program exits(when the installation complete or an error occurs)
Cool! I just renamed it to CLICLIMG.zip and I finally loaded. The problem now is that when it finishes, instead of asking me to flash it, says
"CID Incorrect!
Update Fail!
Do you want to reboot device?
<ACTION> Yes
<POWER> No"
While running the RUU I made sure that it was for HTC Tattoo since it showed me the device during the steps. And I got it from a post describing the steps to flash it using the goldcard.
Furthermore, this error is something similar to what happened when I tried to flash from the recovery. This is REALLY weird...
Probably this isn't the sama as your device's stock rom. I think goldcard needed for flashing any htc original rom, but without goldcard only the device's version will be flashed successfully. Try to download other original roms if you don't know which you had before.
Here is a site with shipped roms for tattoo:
http://www.shipped-roms.com/index.php?category=android&model=Click
The RUU wasn't a problem, I tried now with a goldcard and flashed successfully! I could not get ADB connection to make it, but I once made one and still had the .img in my mail inbox.
But still nothing has changed...
pressing on drives me to the HBOOT screen, whose only options that work are "simlock" to flash CLICIMG.zip, and recovery (freezes on "TATTOO")
EDIT: does not freeze, but goes back to HBOOT after a while... ¬¬
You say that now you have the stock HTC rom and again you cannot boot it and instead the device reboots again to HBOOT?
Then maybe you have a hardware problem which leads to this behaviour.
OK, now I guess it still has warranty, but the problem is that I rooted it.
But now that I flashed somehow the original rom, should be no problem right?
Yes, if you successfully flash the stock rom, you're not root any more.
had that problem to, but theres easy fix for it without doing all whats being sayd here
Even tho phone dont boot annymore and stays on logo plug in the usb cable
and work with adb shell and reflash recovery (to be good tattoo-hack.ko etc tricks need to be done before doing it or you get errors)
http://forum.xda-developers.com/showthread.php?t=716282 step 1.5 and tools from step 1.3
and ether get Amon RA recovery or clockworkmod and use
Code:
./flash_image recovery /sdcard/recovery.img
then reboot into recovery
HTML:
adb shell "reboot recovery"
mount usb put in a custom rom and flash it
if all done well should work (had same problem)
bascly adb still work even if you think you bricked phone just have to let it "startup"
Greetings
I'm afraid that won't work. I've been trying all the time with adb logcat and adb devices unsuccesfully. I thought that the TATTOO bootscreeb would give me some feedback in all cases, but now doesn't seem to work...
I've had similar problems when trying to flash nfinityGB.
My problem was that I missed something on the way from
- creating a gold card
- rooting device
- installing recovery
- flashing rom
All I did was to download and execute "RUU_Click_HTC_WWE_1.67.405.6_WWE_release_signed_NoDriver.exe" (or any other ruu).
Be shure to have SDK with all drivers installed properly.
After this your device is in unrooted (original) state as dancer_69 already told you.
Now you can decide whether to claim warranty or properly follow the guides on xda to get root and flash custom roms.
I think I know from long ago what is happening here, just couldn't believe it. Maybe the keys are sticked or something, that would explain the always going into fastboot mode without pressing the VOL DOWN key. Now it boots 1 out of each 5 tries, and when it gets to the home app, it's on "safe mode" (achieved by pressing MENU key while booting).
I think they will take care for it back in the HTC support (well, I hope)
manutenfruits said:
I think I know from long ago what is happening here, just couldn't believe it. Maybe the keys are sticked or something, that would explain the always going into fastboot mode without pressing the VOL DOWN key. Now it boots 1 out of each 5 tries, and when it gets to the home app, it's on "safe mode" (achieved by pressing MENU key while booting).
I think they will take care for it back in the HTC support (well, I hope)
Click to expand...
Click to collapse
Something like this thought when I said that maybe is a hardware problem.

bricked

first let me tell you how i bricked my tablet... i was on cynogenmod 10 but i wanted to go back to 9 but for some reason because of all the freezing when i was wiping i accidently loaded the official asus rom update US epad etc etc so when i rebooted it gave me that bar and its stuck there i tried to reboot it to recovery but it wont give me the option to go into recovery like it did.
its said something like checking for android ota recovery...so i cant go into adb because usb debugging is not enabled in my tablet because i wiped right so I can go into apx mode because i can see it show up in my devices but it wont do anything with the easy flasher program, it acts like its goinng thru thr proccess but nothing happens on the tablet.....so then i went to try to update the drivers but everytime that i point the apx driver into the file it said that the driver is up to date..... so that where im at now please help me......
I donwloaded NVFLASH but i get that black screen it takes the tablet out of apx mode and the black screen desappears. and i think the same is happenning with easy flasher something is happening at the end that it does not finish the process
You get the OTA message because you removed CWM and moved back to Asus recovery.
You can try to reinstall an Asus stock ROM using the stock recovery. Get an Asus stock ROM (e.g. the one you already flashed), put it on a SD, power off the device and reboot into recovery.
Stock recovery just checkes the SD and if it finds an Asus ROM there it will install it.
I don't remember if the file had to be named something special or not, sorry :silly:
CalvinH said:
You get the OTA message because you removed CWM and moved back to Asus recovery.
You can try to reinstall an Asus stock ROM using the stock recovery. Get an Asus stock ROM (e.g. the one you already flashed), put it on a SD, power off the device and reboot into recovery.
Stock recovery just checkes the SD and if it finds an Asus ROM there it will install it.
I don't remember if the file had to be named something special or not, sorry :silly:
Click to expand...
Click to collapse
Yes rename to EP101_SDUPDATE.zip
Remember to extract the zip from within the zip first, rename the extracted zip.
Thanks!
I have done it lots of time but never quite remember if I should use the zip I download or the one inside it, and which name should this file have... I always end searching the same info over and over :silly:
so even if im stuck on that screen , when i put the update in the sd card it will recognize it immidietly without doing anything special? ill try that, i have tried to install the naked driver on all my computers and it wont let me , im getting a message that said that there is no software for my device in the folder.......... i really appreciate the help guys ill try that tonight see how it goes...do i have to format the sd or something or just place the file in root any other options witll be appreciated, what i dont understand is why there is not like a stock recovery or something
i dont think its gonna work because i dont get the screen that allows you to put into recovery i just get a message that states checking for android ota recovery
Well. Ler me tell you how I did it. It's been sometime since I used stock recovery, but I think it's allright.
1. Download the desired stock ROM from Asus.
2. Unzip the file. You will find another .zip file.
3. Rename this new .zip file as baseballfanz said.
4. Put the renamed .zip in the root directory of a uSD card.
5. Power off the TF.
6. Put the card into the TF.
7. Press Vol. Dn. + Power and keep them pressed until power is on and you see a message in the screen.
(Don't do this... If you press Vol Dn again you will get two options: wipe or coldboot)
8. As soon as you get the message in small caps press Volume Up.
Now the TF will look for an update in the uSD and install it. You won't have to do any further action. If it doesn't work the TF will tell you (I think it was and android with a red X, or with the innards showing or something like that :laugh: )
If this doesn't work then maybe you don't have stock recovery installed ok, or there is some problem with the zip file.

[Q] Retrieve data from non-rooted GS4

Hello,
My Galaxy S4 (SAMSUNG-SGH-I337) is stuck in the at&t logo, I booted into recovery clear the cache and try again but nothing, the phone is still stuck there.
Unfortunately I have two recent files that I would like to copy before trying to factory reset the phone, these files are stored in the phone memory (Download folder).
Given that the phone is not rooted, is there a way to boot the phone into recovery, connect the phone to my mac (I could connect it to a Windows/laptop) and navigate the memory and copy the files?
Thanks for any help

Help Getting Backup Restored

I was given a framework-res.apk file that was going to give me a different power options menu. Before I did anything with the file I created a complete nandroid back up to the sd card. I also went the the original file and changed the name to .bak. I then or so I thought placed the apk in the folder and changed permissions. However the phone immediately restarted and now is in a boot loop stuck at the Samsung logo. Phone will not boot into recovery as it attempts to then just restarts over. i plugged the phone into the computer and it does not recognize it. Any suggestions on how I can either restore my backup or get to the original file to remove the .bak from the file to get everything working again. Thanks for the help.
Have you tried pulling the battery and manually going into recovery by holding up volume + power? Sometimes just pulling the battery and letting it boot normally will work but I doubt it in this situation.
Tried all the main things. Just fixed the problem though. I re flashed recovery allowing me to boot into recovery on the phone and backup is restoring as we speak.

Is my S4 hard bricked

Hi
I would really appreciate it if someone could help me with a problem I have, as I think I might have hard bricked my samsung galaxy s4 (i9505)
I was attempting to install clockwork recovery mod and, following some instructions, I downloaded a zip file called CWM_6.0.4.7_Touch_GT-I9505.zip
The instructions I had said to not extract the tar file within this zip but to transfer it to the S4 with odin in the compressed format.
When I first tried to do this I couldnt because odin did not recognise the zip file format. I therefore assumed I needed to transfer across the compressed file and so accessed it directly with odin
This file was called recovery.img
the odin transfer worked ok and it indicated pass when it had fininshed
However when my phone rebooted it presented lots of error messages one after the other saying (app name) has stopped.
I say ok to all these messages and am left with a blank screen.
I then tried to reboot the S4 into recovery by holding power up/home and power on but not see the normal recovery screen.
Instead I see 3 lines of text top left
1- (in blue)
2- (in red) recovery is not seanoroid enforcing
3 - in yellow) set warranty bit : recovery
I googled error message 2 and it was suggested that when I see the threee messages I should release home and power but keep holding the up button to go into recovery mode, but this does not work.
I am suspecting that by flashing this file I have overwritten the original recovery files and so wondered if there is any way I can resolve this probelm
Any help greatly appreciated
Thank you
Tony
Wrong forum buddy. This is for LG g4 not samsung
Sent from my VS986 using XDA Free mobile app
Thread moved
tonypbx said:
Hi
I would really appreciate it if someone could help me with a problem I have, as I think I might have hard bricked my samsung galaxy s4 (i9505)
I was attempting to install clockwork recovery mod and, following some instructions, I downloaded a zip file called CWM_6.0.4.7_Touch_GT-I9505.zip
The instructions I had said to not extract the tar file within this zip but to transfer it to the S4 with odin in the compressed format.
When I first tried to do this I couldnt because odin did not recognise the zip file format. I therefore assumed I needed to transfer across the compressed file and so accessed it directly with odin
This file was called recovery.img
the odin transfer worked ok and it indicated pass when it had fininshed
However when my phone rebooted it presented lots of error messages one after the other saying (app name) has stopped.
I say ok to all these messages and am left with a blank screen.
I then tried to reboot the S4 into recovery by holding power up/home and power on but not see the normal recovery screen.
Instead I see 3 lines of text top left
1- (in blue)
2- (in red) recovery is not seanoroid enforcing
3 - in yellow) set warranty bit : recovery
I googled error message 2 and it was suggested that when I see the threee messages I should release home and power but keep holding the up button to go into recovery mode, but this does not work.
I am suspecting that by flashing this file I have overwritten the original recovery files and so wondered if there is any way I can resolve this probelm
Any help greatly appreciated
Thank you
Tony
Click to expand...
Click to collapse
You are fine. CWM is highly outdated and shouldn't be used anymore.
Go to TWRP.com and download the latest TWRP. Flash it like you flashed CWM and you will be fine.
download mode
Thanks very much
After my post I remembered that I'd not checked if download mode worked, and it did so managed to restore everything
Can you please let me know with CRW or the program you mentioned if more than one ROM back up can be made because I'm thinking of, if I can, having a custom rom back up and a back up of any new roms I try until I decided what I want to stick with
Regards
Tony
PoiSpin said:
Wrong forum buddy. This is for LG g4 not samsung
Sent from my VS986 using XDA Free mobile app
Click to expand...
Click to collapse
I think you are at the wrong place
ludoke said:
I think you are at the wrong place
Click to expand...
Click to collapse
and i think you need to improve your reading skills
the thread has been moved from the incorrect section to the correct section

Categories

Resources