Database Users

[Q] LG G2 stuck at black screen after LG Logo!

Hello guys.
So i installed an xposed module to change keys to Android L style and it asked me to add one line under build.prop
I restarted but my phone stucked at a black screen after the LG logo and only the LED is working.
I tried to shutdown by keep pressing the power button but it restarts again. Pressing "Power" + Volume - key doesn't work. (I think phone must be turned off for this!?)
So i don't know what else to do. I'm running 4.4.2 no custom recoverys i just rooted it.
Please someone help :crying:

keep power key pressed even when lg logo pops up... then it will shut down completely...
btw that build prop line is not for our device (afaik - because i never had to edit build.prop for this mod to work)
i also doubt that this single build.prop line broke the whole rom unless you accidentaly deleted something else in the build.prop code...
anyway, you'll first need the original build.prop for your rom (you can extract it from the rom zip you're using)
but i don't know how can you put it on the device since you don't have a custom recovery
@bender_007 might know this part better

60nine said:
keep power key pressed even when lg logo pops up... then it will shut down completely...
btw that build prop line is not for our device (afaik - because i never had to edit build.prop for this mod to work)
i also doubt that this single build.prop line broke the whole rom unless you accidentaly deleted something else in the build.prop code...
anyway, you'll first need the original build.prop for your rom (you can extract it from the rom zip you're using)
but i don't know how can you put it on the device since you don't have a custom recovery
@bender_007 might know this part better
Click to expand...
Click to collapse
I managed to shut it down with your suggestion.I need to find a way to go into recovery or download mode but i need some help for this to happen
The original build.prop is at same location i just put ".old"

spithash said:
I need to find a way to go into recovery or download mode but i need some help for this to happen
Click to expand...
Click to collapse
that's why i've mentioned bender007 in my quote... he's way more experienced in that stuff...
i never used download mode...
btw you've said that you don't have a custom recovery... or you're talking about the stock one?

60nine said:
that's why i've mentioned bender007 in my quote... he's way more experienced in that stuff...
i never used download mode...
btw you've said that you don't have a custom recovery... or you're talking about the stock one?
Click to expand...
Click to collapse
I have the stock recovery and i can't access it...

Let me guess. You can't flash the right kdz? There id also tot method with "cracked" dll which allows you to crossflash. Will seek for it after my work time
.
+ power off the device, hold volume up and connect to PC. Then try the lg support Tool.

bender_007 said:
Let me guess. You can't flash the right kdz? There id also tot method with "cracked" dll which allows you to crossflash. Will seek for it after my work time
.
+ power off the device, hold volume up and connect to PC. Then try the lg support Tool.
Click to expand...
Click to collapse
The problem is I can't enter download or recovery mode. Holding + button and plugging it in just makes the usb sound in windows and the phone shows the battery and starts charging. Is this supposed to happen?
Also I can't find it in device manager.
Sent from my C6603 using XDA Free mobile app

Might be your battery was low..and now it's empty. Install vmware and slax inside it. Try opening terminal. Type ls /dev/sd*

bender_007 said:
Might be your battery was low..and now it's empty. Install vmware and slax inside it. Try opening terminal. Type ls /dev/sd*
Click to expand...
Click to collapse
I have ubuntu in my laptop. I tried this method here: http://forum.xda-developers.com/showthread.php?t=2582142
But it stucks at this command "gdisk -l /dev/sdb" and gives me and error 123...
Also at first command "ls /dev/sd*" i have only 1 sdb without numbers after it.

Did ubuntu throw some mounting errors? Native ubuntu?

bender_007 said:
Did ubuntu throw some mounting errors? Native ubuntu?
Click to expand...
Click to collapse
I have ubuntu gnome 14.04 and it says Gdisk NOTE: Write test failed with error number 123. It will be impossible to save
changes to this disk's partition table!

No one can fix it so i sent it over at LG service. I'll update when it comes back.

O have the same problem. Went to my warranty, told that it shut down during updating. Will see what they'll say. Please update if you have any new info

vklexer said:
O have the same problem. Went to my warranty, told that it shut down during updating. Will see what they'll say. Please update if you have any new info
Click to expand...
Click to collapse
The told me it will be ready in 2 days so i think they didn't discovered my root I will let you know when i have it back

Got mine before you did. They replaced my main board well it was a long update to 20h. Only had to brick it, wait 3 days for repair, and whoaliaaa i have 20h..

How to install custom ROM in Zenfone 5 if phone never boots into recovery mode

I want to install custom ROM on my Zenfone 5.
Things you should know:
.. Phone OS completely corrupts unable to boot the device (even android logo also not appear)
.. It is not showing charging symbol also when connected to charger/usb
.. Phone never boots into recovery mode (it is just restarting(vibration)! and stay idle)
.. It has TeamWin recovery project that appear after 30 mins of charging (useful!!)
So, can anybody tells me how install custom ROM (http://forum.xda-developers.com/zenfone-5/orig-development/beta-cyanogenmod-12-1-tank0412-t3285392) please don't say boot into recovery mode and do some adb/fastboot commands it is not working (volume up+power or any combination). It is just showing one big red charging bar symbol without charging.. and some times TeamWin which may helpful because it has filemanager and I can browse but I don't know how to install with that.
If you have any ideas please share me..
Thanks

You can put rom on the external sdcard and install it after TWRP booting.
But i think that something wrong with bootloader on your phone so you should try to make unbrick.

tank0412 said:
You can put rom on the external sdcard and install it after TWRP booting.
But i think that something wrong with bootloader on your phone so you should try to make unbrick.
Click to expand...
Click to collapse
Thanks for the answer..
Hard bricked device - Just like it's name, your device is dead. It behaves like a real brick. You can have no operation on pressing the power button.
So we can make a conclusion: soft bricked device can’t be defined as "BRICKED"; the hard bricked device is the real "DEAD & BRICKED", and it can't be unbricked. Sorry for the answer to how to unbrcik hard bricked Android phone.
This is the situation of my phone and whenever I flash a zip file from TWRP I'm getting following error..
"E: Error executing updater binary in zip '/sdcard/.....zip'"
I'm googling this error but unable to get anything(trying some of the one plus one solutions to the similar problem).. Please help me..

wyephani said:
Thanks for the answer..
Hard bricked device - Just like it's name, your device is dead. It behaves like a real brick. You can have no operation on pressing the power button.
So we can make a conclusion: soft bricked device can’t be defined as "BRICKED"; the hard bricked device is the real "DEAD & BRICKED", and it can't be unbricked. Sorry for the answer to how to unbrcik hard bricked Android phone.
This is the situation of my phone and whenever I flash a zip file from TWRP I'm getting following error..
"E: Error executing updater binary in zip '/sdcard/.....zip'"
I'm googling this error but unable to get anything(trying some of the one plus one solutions to the similar problem).. Please help me..
Click to expand...
Click to collapse
It looks like you use TWRP by Knone which is broken a bit. So you should install TWRP by quanganh2627.
Try to flash this package via TWRP:
https://drive.google.com/file/d/0B-Fin8UxrD6PNm1NSDNQQ3JqUkU/view?usp=sharing
It will install a stable TWRP.

tank0412 said:
It looks like you use TWRP by Knone which is broken a bit. So you should install TWRP by quanganh2627.
Try to flash this package via TWRP:
It will install a stable TWRP.
Click to expand...
Click to collapse
Hi! Your zip file successfully installed but after that also I'm getting same error. Is there any file download problem (Checksum or like that) or do I have to restart my phone(No OS installed!)

wyephani said:
Hi! Your zip file successfully installed but after that also I'm getting same error. Is there any file download problem (Checksum or like that) or do I have to restart my phone(No OS installed!)
Click to expand...
Click to collapse
Thanks for your TWRP. I successfully installed custome ROM of this..(http://forum.xda-developers.com/zenfone-5/orig-development/rom-cyanogenmod-12-1-xhook-t3289543) but I'm getting these problems which are nowhere found in any forum
1. Charging stops at 10% never goes beyond this point
2. IMEI missing (seriously !!)
Thanks

wyephani said:
Thanks for your TWRP. I successfully installed custome ROM of this..(http://forum.xda-developers.com/zenfone-5/orig-development/rom-cyanogenmod-12-1-xhook-t3289543) but I'm getting these problems which are nowhere found in any forum
1. Charging stops at 10% never goes beyond this point
2. IMEI missing (seriously !!)
Thanks
Click to expand...
Click to collapse
Try to downgrage to stock rom:
https://drive.google.com/file/d/0BwEWY6gMvYOeelBEQ2J0ckxnRmc/view

tank0412 said:
Try to downgrage to stock rom:
https://drive.google.com/file/d/0BwEWY6gMvYOeelBEQ2J0ckxnRmc/view
Click to expand...
Click to collapse
Yes, I'm trying that but the problem here is I'm unable to flash TWRP now (Run the command prompt - wait for device - phone starts several times but only big red battery symbol without charging/usb cable showing red bar below - boot into installed OS) that's it without flashing the TWRP phone reboots and command prompt still waiting for device even device already booted.
Interestingly now the battery showing 100% directly (I don't know ! whether it is actual figure or something goes wronng!) but still my IMEI is empty and I want to install stock ROM on this device for this purpose.
Note: still power + volume up/down to goto recovery mode not working
Any help appreciated. Thanks!!

wyephani said:
Yes, I'm trying that but the problem here is I'm unable to flash TWRP now (Run the command prompt - wait for device - phone starts several times but only big red battery symbol without charging/usb cable showing red bar below - boot into installed OS) that's it without flashing the TWRP phone reboots and command prompt still waiting for device even device already booted.
Interestingly now the battery showing 100% directly (I don't know ! whether it is actual figure or something goes wronng!) but still my IMEI is empty and I want to install stock ROM on this device for this purpose.
Note: still power + volume up/down to goto recovery mode not working
Any help appreciated. Thanks!!
Click to expand...
Click to collapse
You bricked your device.
You should use unbrick method:
http://4pda.ru/forum/index.php?showtopic=584672&st=460#entry33842670

Damaged recovery, unable to ADB debugging, bootloop

[HELP] [URGENT]
//this is the story, skip if you prefer
so i was updating my cm 12.1 rom to rr 7.1 rom
everything was fine, no real mess just bad flash so i decided to reflash the rom (dunno why i did that actually, its just my tradition). Aaaaand the ROM went flawlessly
next step is install supersu, i checked that the rom is pre-rooted so i think its easier to get supersu via playstore. Installing supersu went flawlessly (again) and i rebooted ma phone.
//then everything starts to f***ed up
my phone bootlooped (not a big deal actually, done with this sh** all the time)
like a casual day, reflash my phone. but i cant go to recovery mode its stuck at logo i think that supersu binary damaged ma recovery.img (again not a big deal but i started to worry) i connect my phone to my pc, summon my adb, and hope the best, but my devices not listed there. then i remembered i forgot to turn on usb debugging on setting oh crap!
so here is my question:
is it possible to turn on usb debugging via pc or something else? if so how.
is it possible to use adb feature without my phone being turned on its usb debugging?
is it possible to repair my recovery <== i mean reflash beside using adb. if so how :crying:
and the last one, beside my phone not listed on adb device list. it wont showed or recognized in my pc (do i need something else beside usb and adb driver?)
any help will be appreciated :good:
this is my only phone so i put my hands on you guys, you're the superhero here
if i dont have any solution, my only way is send this phone to service centre :crying:
some info:
devices : lenovo a6k plus
old rom : cm 12.1 by ED300
new rom: rr nougat v5.8.0 (i dont remember who made this rom, sorry. by the way i found the rom somewhere in xda)
supersu ver: newest per 21 Feb 2k17 (playstore)
my pc: win 8 64x <== dunno if this info useful though
old recovey: twrp (forget the version, but im pretty sure the recovery made by russian developer and it has chicken logo during startup)
battery level when i discovered i cant go to recovery mode: somewhat near 16% <== maybe helpful
if you really care to help me just tell me what do you know, i would appreciate that really, i meant that because this phone is the only way i can contact all of my super important buddy for my business.
Thanks anyway, regards Tom

Well take out the battery and return it hold volum down + power button now you should be able to use fastboot commands go to the folder where you have your adb and fastboot there paste a recovery img file you want to use.Open cmd and type fastboot flash recovery nameofyourimg.img
And now you should be able to use recovery.If not try qfil debricking method that you can find on forum.Best of luck if somthing isnt clear enough feel free to PM me.Also download new recoveries that are now officialy developed

Thanks for replying JovanSijacki
unfortunate enough, i have done that and still dope and nope.
usually i can find my device in windows device manager named android with yellow triangle, but this one is different, my computer wont recognize my phone.
will try debricking method instead, thank you dude :smile:

Thank you for those who care to reply, friend of mine who are expert developer told me how to fix this. AS LONG AS YOU ABLE TO GET INTO FASTBOOT MODE YOU ARE SAFE. Im going to make separate thread to share the tutorial *insert smiley emoji*

Phone Bricked. PLEASE HELP

I will try to explain everything from the beginning. I was about to install a custom rom install (it was in 7.1.1 stock, unlocked bootloader) so when I was going to do full wipe with lastest TWRP there was an error. Wait for about 15 minutes just in case, but nothing happened so I decided to restart it to try again. But the phone stuck in the ZTE logo and if it tried to enter TWRP was stuck in the logo too, I tried with all versions of TWRP and no one works. Find a post that said I could use TWRP tenfars tool to recover my phone and had to enter the EDL mode. I managed to put the phone in edl mode but now I can not get out of it. I press and hold the power button for a minute and nothing happens (no vibration, no led, no ZTE logo) my pc just does the unplug windows sound. My pc recognizes the phone as QUSB_BULK. When I try to use the tenfars tool I get this message:
C:\Users\Alejandro Saavedra\Downloads\minimal_adb_fastboot_1.4.1_portable>axon7tool -w recovery
Connecting to device...
S: failed to read command
S: Failed to receive hello
terminate called after throwing an instance of 'std::runtime_error'
what(): error: Unknown error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
Also try using the xiaomi MiFlash tool (even change the drivers from QUSB_BULK to COM COM 5) but something similar happens, also tells me can not recive hello package.
I'm a little new to this so I beg you a little patience
Please work very hard to buy this phone, there has to be some way to unbrick it. :crying:
If you need any additional information just tell me

If you use axon7tool :
check in Devices Manager if is called QLIBSD.
rename recovery.img to recovery.bin.
If you use MiFlash :
get latest version : https://www.androidfilehost.com/?fid=673368273298954241
check in Devices Manager if is called Qualcomm 8004.

CelesteBlue said:
check in Devices Manager if is called QLIBSD.
rename recovery.img to recovery.bin.
Click to expand...
Click to collapse
You need two files, recovery.img and recovery.bin in same folder. (Don't forget to unzip tenfars TWRP and after that rename and make a copy)
Please read: https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
Best regards
Smedslund

Smedslund said:
You need two files, recovery.img and recovery.bin in same folder. (Don't forget to unzip tenfars TWRP and after that rename and make a copy)
Please read: https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
Best regards
Smedslund
Click to expand...
Click to collapse
anyway :
https://ab-exclusive.us/fileserver/uploads/twrp_rec_tenfar.zip
404 Not Found...
To flash a recovery file (STOCK or TWRP) with axon7tool, the file has to be called recovery.bin.

CelesteBlue said:
anyway :
https://ab-exclusive.us/fileserver/uploads/twrp_rec_tenfar.zip
404 Not Found...
To flash a recovery file (STOCK or TWRP) with axon7tool, the file has to be called recovery.bin.
Click to expand...
Click to collapse
You will find tenfar 3.0.2-2 TWRP at download center:
https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547
Once unzipped, copy it to recovery.bin:
copy twrp_rec_tenfar.img recovery.bin

Thanks to everyone for your answers, I was able to recover my phone using miflash, qualcom usb drivers and this ROM https://build.nethunter.com/misc/axon7/A2017U_B15-NEW_FULL_EDL.zip I put my phone in EDL mode and then flash the mentioned rom. It took me like 20-30 tries to finally get it. The last attempt I made was to unplug the device from the computer, I kept the power button for 10 seconds and connect it to the computer without ever releasing the power button. It was seen as always (black screen, not led) but for some reason this time works. I hope everyone can solve this problem. Can pm me if you need help, maybe i can help with something

ale0796 said:
Thanks to everyone for your answers, I was able to recover my phone using miflash, qualcom usb drivers and this ROM https://build.nethunter.com/misc/axon7/A2017U_B15-NEW_FULL_EDL.zip I put my phone in EDL mode and then flash the mentioned rom. It took me like 20-30 tries to finally get it. The last attempt I made was to unplug the device from the computer, I kept the power button for 10 seconds and connect it to the computer without ever releasing the power button. It was seen as always (black screen, not led) but for some reason this time works. I hope everyone can solve this problem. Can pm me if you need help, maybe i can help with something
Click to expand...
Click to collapse
That's because you reset the EDL that way. the method is weird but seemed to work...
If you hold the 3 buttons for ~10 secs while the device is in EDL it will reset it

@Choose an username... I am out of context, but I wonder if I can remove the ugly message on each startup telling it can't check if the device is not corrupted... I think this message is caused by the unlocked bootloader. A solution ? Thank you.

CelesteBlue said:
@Choose an username... I am out of context, but I wonder if I can remove the ugly message on each startup telling it can't check if the device is not corrupted... I think this message is caused by the unlocked bootloader. A solution ? Thank you.
Click to expand...
Click to collapse
Actually, it is a nice feature for the few seconds it lasts, but read HERE if you must. Be careful!
Good luck

CelesteBlue said:
@Choose an username... I am out of context, but I wonder if I can remove the ugly message on each startup telling it can't check if the device is not corrupted... I think this message is caused by the unlocked bootloader. A solution ? Thank you.
Click to expand...
Click to collapse
I'd advice against doing it... I had no trouble with it but a bunch of people now have paperweights. But yeah, the link is the one provided by the other guy above me

Thank you so much @Choose an username... and @amphi66 : that worked !
Anyway I am on G B04 (Nougat).
Do you know some cool mods I should do ?
Like debloat, remove the boot message (done), etc...

Recover from Hard Brick (900e) - Revive our Z2 WITHOUT DATA LOSS

Hey!
Z2 owners that like to mess around with their phones are prone to get f#ked. I was there and I faced the problem some of you probably did - a hard brick. There are a ton of tutorials on how to fix it, but I believe I found a new way that doesn't envolve resetting it. I have only tried with twice on my phone, so I'm really looking forward to know if it's universal!
Scenario - Your phone has a black screen. The notification LED is on. If you hold the power button it flashes the ZUK logo and it vibrates. If you identify with this scenario, go forward!
1 - To turn off your device (if you haven't already), press the power + volume up. The phone will vibrate, flash the ZUK logo, turn off the LED and turn it on again. Continue holding both buttons. When the LED turns off again, REMOVE your fingers from both buttons right away. If done correctly, it won't come back again and the LED will be off
2 - Hold both Volume Up and Volume Down at the same time. Connect to the computer. You should encounter your Fastboot mode (with your baseband and other info blank).
3 - Go to your email and redownload the bootloader unlocker. Yes, remember that file? Use it. You can use one of those unlock bootloader tutorials online, but if you know what you're doing, here's the command:
fastboot -i 0x2b4c flash unlock unlock_bootloader.img
4 - Right after that, run this other command
fastboot -i 0x2b4c oem unlock-go
That's it. You should be able to go to the recovery (flash it again just to be sure). Try it out and tell me how it goes.

not working...phone is gettin turned off...but holding up and down..then connecting is doin nothing..it just keeps on going on and off again

This method worked for me,thank a lot of,great trick
Sent from my Redmi Note 3 using Tapatalk

you my friend, are a god among men, i owe you a beer.

fastboot mode conncted and flash unlockbootloader.img file..but not boot mobile shows error msg .my bootloader is unlocked any suggestion plz

vardhan21 said:
fastboot mode conncted and flash unlockbootloader.img file..but not boot mobile shows error msg .my bootloader is unlocked any suggestion plz
Click to expand...
Click to collapse
Same thing happened to me..followed this link https://zukfans.eu/community/threads/how-to-unbrick-zuk-z2-from-diagnostic-port-900e.2856/ as my phone showed 900E mode in Qfil ...followed and unbricked..mine bootloader also showed as unlocked

paps2k3 said:
Same thing happened to me..followed this link https://zukfans.eu/community/threads/how-to-unbrick-zuk-z2-from-diagnostic-port-900e.2856/ as my phone showed 900E mode in Qfil ...followed and unbricked..mine bootloader also showed as unlocked
Click to expand...
Click to collapse
hey thnks bro...i successfully enabled 9008 port and flashed firmware
thanku so much

Where were you man I have to cut my wire and format my phone for flashing new firmware

My phone don't show the led light
No button combination works
I was restoring twrp backup and the next boot...And i was bricked
It shows diagnostic mode 900E
Please help

Finally done
vardhan21 said:
fastboot mode conncted and flash unlockbootloader.img file..but not boot mobile shows error msg .my bootloader is unlocked any suggestion plz
Click to expand...
Click to collapse
Had the same problem and first i went to download mode by following the the below link
https://zukfans.eu/community/threads/how-to-unbrick-zuk-z2-from-diagnostic-port-900e.2856/
then i downloaded the stock firmware and followed this guide
https://zukfans.eu/community/threads/how-to-unbrick-zuk-z2-from-diagnostic-port-900e.2856/
Both of them helped.:good::fingers-crossed: hope they work for you

Please tell me the process for recover from hard brick, because zukfans.eu is no longer available.

paps2k3 said:
Same thing happened to me..followed this link https://zukfans.eu/community/threads/how-to-unbrick-zuk-z2-from-diagnostic-port-900e.2856/ as my phone showed 900E mode in Qfil ...followed and unbricked..mine bootloader also showed as unlocked
Click to expand...
Click to collapse
What is the process??? Please tell me here because zukfans.eu is not accessable

Rit2005 said:
What is the process??? Please tell me here because zukfans.eu is not accessable
Click to expand...
Click to collapse
Hi ..very sorry..not using z2 plus for a long time..I forgot the process what I did..I followed the steps mentioned there.