Database Users

[Q] bricked my lg g2 d802,not going into download mode + my screen has white lines

hello guys,im new here i need your help..
I bricked my d802 today,i was on stock kitkat rom,what i did was rooted my device with towel root and used Autorec to install recovery,it installed successfully,then i clicked ''go to recovery'' then all i get were white lines on one side of screen and rest of screen is black(cant see anything).. after digging for hours i came to know that it is because of different Kernel version,but now i want to know how can i flash patched Kernel? as my device is bricked.. It is also not going into download mode so i cant also flash a stock rom.. tried Adb but it is not detecting my device... im completely lost
A tutorial or help will be appreciated.Thanks im waiting for your replies
EDIT:
i used fastboot commands n flashed some img. files..now my display shows up(dull white lines are still on it)..i can boot into download mode now..i flashed kdz stock rom it completed successfully.. but after reboot it is stuck on lg logo with led on... i did hard factory reset(holding volume down key + power button) but it is still stuck at lg logo.. i can still boot into download mode and i dont have a custom recovery installed what should i do now?
can i flash custom recovery using fastboot command? because ADB is not detecting my device. but computer is detecting my device(it also installed three drivers automatically)
And i flashed D80220a_00.kdz stock rom Indian version..should i try some other KDZ aswell? reply please thanks

have a similar issue with my d805. stuck in boot logo and download mode doesnt do anything to help me. someone please help

guys i really need your help,please guide me

kenennaoyeka said:
have a similar issue with my d805. stuck in boot logo and download mode doesnt do anything to help me. someone please help
Click to expand...
Click to collapse
any luck?

none bro....i sent my phone in to an XDA Super Contributor in the LG G2 section. He was in California. Try to find someone to help you around your city or country. Sorry man. If he gets it done, i would ask him how he went about it and let you know.
ahmeee123 said:
any luck?
Click to expand...
Click to collapse

okay,i figured out my problem i have d800(i removed back cover to check) while i was flashing kdz n tot. of d802,now my screen is messed up,no download mode,no recovery and no fastboot,it just stuck at lg logo with led flashing,my pc detect it as Lg androidnet phone.. what can i do now? anybody help thanks

same issue
ahmeee123 said:
hello guys,im new here i need your help..
I bricked my d802 today,i was on stock kitkat rom,what i did was rooted my device with towel root and used Autorec to install recovery,it installed successfully,then i clicked ''go to recovery'' then all i get were white lines on one side of screen and rest of screen is black(cant see anything).. after digging for hours i came to know that it is because of different Kernel version,but now i want to know how can i flash patched Kernel? as my device is bricked.. It is also not going into download mode so i cant also flash a stock rom.. tried Adb but it is not detecting my device... im completely lost
A tutorial or help will be appreciated.Thanks im waiting for your replies
EDIT:
i used fastboot commands n flashed some img. files..now my display shows up(dull white lines are still on it)..i can boot into download mode now..i flashed kdz stock rom it completed successfully.. but after reboot it is stuck on lg logo with led on... i did hard factory reset(holding volume down key + power button) but it is still stuck at lg logo.. i can still boot into download mode and i dont have a custom recovery installed what should i do now?
can i flash custom recovery using fastboot command? because ADB is not detecting my device. but computer is detecting my device(it also installed three drivers automatically)
And i flashed D80220a_00.kdz stock rom Indian version..should i try some other KDZ aswell? reply please thanks
Click to expand...
Click to collapse
Hello
I have bought my Lg g2 d802 few days ago and when I tried to root it and install recovery using autorec the phone screen went black after rebooting into recovery and still in that state.. no led, no download mode , no recovery nothing else just white lines on left corner.... I tried it to get its software repair but they said that the lcd has been fused and need to be replaced ...
I tried to connect it to pc and it is showing marshall london adb interface and in another pc it is showing Android with yellow mark which turned in to Android adb interface after installing drivers from internet
I tried fastboot.exe and adb.exe but no device found error in adb mode but some commands working as fastboot..
I want to know which partitions u flashed using fasboot and how because when i tried to flash it says cant load XXX.img (xxx belongs to the name of partition i flashed)

same problem is here....u found any solution???

AutoRec got my LG D802 bricked and now all i see white lines on screen. Can anyone help plzzzz

[Q] problems when rooting Note 4 Int

im trying to root my phone again after updating it to the latest version of 4.4.4 from samsung but i get stuck in the boot it's trying to start recovery and then fails and restarts and it's doing it infinitive of times until i enter download mode and flash CWM in odin but my root is still not applied.. I've tried to use different ports and the original smasung usb cable.. maybe it's because i updated the phone?
and now im getting stuck here instead of the loop: http://gyazo.com/e5ec975ac4b42dc2a25e8fb8b60197b5
b4 it got stuck in RESET on odin but now it says cache only?

RaW D Coy said:
im trying to root my phone again after updating it to the latest version of 4.4.4 from samsung but i get stuck in the boot it's trying to start recovery and then fails and restarts and it's doing it infinitive of times until i enter download mode and flash CWM in odin but my root is still not applied.. I've tried to use different ports and the original smasung usb cable.. maybe it's because i updated the phone?
and now im getting stuck here instead of the loop: http://gyazo.com/e5ec975ac4b42dc2a25e8fb8b60197b5
b4 it got stuck in RESET on odin but now it says cache only?
Click to expand...
Click to collapse
no need i fixed it.. odin is **** i got odin to at least install CWM and when i entered CWM and then left it it asked if i wanted to apply root and it worked just like that. <3 love u CWM

[SOLVED] Flashed wrong recovery, now stuck in Odin mode: "Could not do normal boot"

[SOLVED] Flashed wrong recovery, now stuck in Odin mode: "Could not do normal boot"
First time venturing into rootin' 'n bootin' Android devices. Hopefully will have a long pleasant journey ahead, but due to a silly oversight, I flashed the wrong recovery file to my device (hangs head in shame). I'm an seasoned coder, but am somewhat new to Android.
Some info:
Model: SM-N910G (SnapDragon)
Device does not want to boot normally, stuck in downloading mode. The screen shows the following:
"Could not do normal boot. ODIN MODE (HIGH SPEED)" Reactivation lock is "OFF".
[x] device is rooted and was running stock TouchWizard (based on Lollipop 5.0.1)
[x] can't get the phone to enter recovery mode (by pressing PWR+Menu+Volume Up)
[x] device is not recognised in ADB (using "adb devices")
[x] Samsung Kies3 does recognise that there is a device but says it's unsupported
[x] device is recognised in Odin/Windows (blue comes up)
[x] device is recognised in Heimdall on OSX (however, I have not used Heimdall for flashing at all yet)
[x] I now have to pull the battery to turn device off
[x] my main computer is a fast MacBook Pro, but have access to older/slower Windows 7 laptops (with only 2GB RAM).
I had the device rooted and working fine except for the fact that I was getting "dm-verity verification failed" errors when trying to make a Nandroid backup. So I tried to reinstall TWRP recovery -- this time rather than going through Odin, I tried it with TWRP Manager (installed on device). I managed to select the wrong recovery file (SM-N910F instead of SM-N910G -- in TWRP Manager this was somewhat unlclear, as I selected the "Galaxy Note 4 INTERNATIONAL version"; my device could be considered "INTERNATIONAL version", I should have been MUCH more careful however).
What is the best course of action to take from here on? I have read a serious number of posts on XDA, but am somewhat unclear about best action to take from here on.
All help will be much appreciated: amazing Karma coming your way to all who can help get this device booting normally!

Have you tried to flash via ODIN the right version of TWRP?

_mone said:
Have you tried to flash via ODIN the right version of TWRP?
Click to expand...
Click to collapse
First of all, thank you for responding. Much appreciated.
One of the problems I keep running into is that Odin (various versions) gets stuck and is "Not Responding" when attempting to verify the MD5 hash of the recovery file. Mind you, this happens when the device is NOT plugged in.
Surely, verifying a 15mb recovery file should only take a few seconds (even on an older machine) ? I have tried re-downloading the same file. For now: I'll keep looking for good sources of the correct N910G TWRP recovery file.

Zef Vegas said:
First of all, thank you for responding. Much appreciated.
One of the problems I keep running into is that Odin (various versions) gets stuck and is "Not Responding" when attempting to verify the MD5 hash of the recovery file. Mind you, this happens when the device is NOT plugged in.
Surely, verifying a 15mb recovery file should only take a few seconds (even on an older machine) ? I have tried re-downloading the same file. For now: I'll keep looking for good sources of the correct N910G TWRP recovery file.
Click to expand...
Click to collapse
Correct me if I'm wrong.
Is the N910G called trltedt?
If it is like that you should download twrp-2.8.7.0-trltedt.img.tar from this official TWRP page and flash it via ODIN

I believe you are correct (and thanks for that link). I'm currently verifying whether the N910G is indeed called trltedt. There seems to be a bit of confusion out there over that specific model. Will report back shortly.

Zef Vegas said:
I believe you are correct (and thanks for that link). I'm currently verifying whether the N910G is indeed called trltedt. There seems to be a bit of confusion out there over that specific model. Will report back shortly.
Click to expand...
Click to collapse
N910G is indeed trltedt.

Battlehero said:
N910G is indeed trltedt.
Click to expand...
Click to collapse
Thanks for confirming that. I had just come to the same conclusion. Am now looking for best source for Odin that works with my N910G device. As soon as I have found that, I'll flash the recovery file (from source suggested by _mone) on a PC w/ official Samsung USB drivers & w/ Kies uninstalled.

With ODIN 3.10.x you should be ok.

_mone said:
With ODIN 3.10.x you should be ok.
Click to expand...
Click to collapse
I am VERY happy to report that the flash worked: device booted up nicely. Thanks guys! As promised: seriously good Karma coming your way.
Now, what has made this all a fair bit trickier up to this point: each time I tried to let Odin read the MD5 hash associated with its TAR recovery file, Odin borked and became unresponsive. The recovery file suggested by _mone was processed by Odin just fine and the whole thing was done in seconds. Yay!
Think I'll have a beer now, take a breather, and toast to you guys (wish I could drink it with you two).
[EDIT] I was initially using a different recovery file to the one suggested by _mone. The recovery file I was using at first included a MD5 hash and caused Odin to become unresponsive.

Happy if you managed to solve the problems with your phone!
I'll have a beer too now! lol :cheers:

Please help!!!!!!

Today i was trying to install the Android Marshmallow 6.0.1 on my Galaxy S5 Snapdragon via Odin, i downloaded the firmware from Sammobile, i verified that the phone model was exactly the same as named on the firmware, i place the .md5 file in the AP slot and everything was ready to go! (The phone was already plugged and in Bootloader mode, and drivers were up to date) then when finishing the flash Odin FAILS to complete the flash and the phone is left with nothing than the Download mode, i panic and try to access recovery mode but realize that there´s no recovery....I proceed to install the recovery.tar into my phone and it works, i start the phone and Samsung logo comes up, finally it loads and does al the process after you flash a Samsung phone.
Everything works just fine!...except for one thing, THERE´S NO RECOVERY!!!. The phone works perfectly but when i try to enter recovery mode, it sends me to Odin mode as it displays a message saying that failed to boot into recovery.
Please help me i don´t know what to do.
Thanks!

Just flash a custom recovery like twrp or cwm

Already did...same problem, recovery won't boot

adavicco said:
Already did...same problem, recovery won't boot
Click to expand...
Click to collapse
You need to flash a pit file to complete the install correctly.

Samsung galaxy A sm-t585 stuck in bootloop

I tried rooting my tablet and I'm using arch linux on my computer, so I had to use Heimdall and Jodin to root it. I got the Heimdall to say "flashed succesfully", but I still didn't have twrp on my tablet.
Then I found Jodin and tried to use that to flash twrp on my tablet, but I really didn't got it to work. It usually said failed, because tablet would disconnect during the flash and reconnect right after.
Right now the tablet is stuck in "bootloop" it just boot's into the black screen where it says "Samsung galaxy tab a etc.". I can boot into download mode, but I really don't know how to fix this. When I boot into download mode, both jodin and heimdall detects the phone. Any tips how to fix this?

Try go to download mode by mtp from windows or micro USB with resistance
If you want to download twrp for root so you can make root with out it
Just by eftus and flash file from site or magisk apk with AP file same ver on your phone

I guess I wrote pretty confusing post. I can go to download mode, but not boot to the android. Right know I got it saying "could not do normal boot invalid kernel length"
Jodin says this when trying to flash:
<ID:0/008> Added!!Device Connected
Device Removed
Device Connected
/usr/bin/heimdallDevice Removed