Database Users

[Q] Can't boot any ROM!

Well, I think I need some help with this one.
So, I have been using Resurrection Remix as my daily driver for a while now (to be able to run lollipop). As I noticed the G2 now has an official lollipop build, so I wanted to install that(cam sucks on most ROMs and overall stability isn't always great). Since I figured the best way would be to go back to stock, and then run the OTA updates.
I made a backup of my current rom, found this, and tried the TOT method. Everything ran fine, but when the 85% reboot thing happened, it booted straight into TWRP. Decided to reboot to system via TWRP, but after showing the LG logo for about 5-10s, it goed straight back into recovery. Since i figured the install failed or something I decided to factory reset, and restore from my backup. TWRP says the restore is succesful, but it still won't boot into my ROM. Reinstalling any ROM doesn't work either
Already tried this, no result(, and I'm afraid of trying the above guide again, but let me know if i should just try again)!
I do have access to my recovery and download, and ADB still works. The only thing I see is that instead of this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Mine says this:
(My PC is in Dutch )
(The LG Driver on the guide was an older version than the one on my pc still, but I don't think that will cause a problem).
Hope my phone isn't gone forever, and thanks for helping in advance!!
-Scrytal
EDIT:
Tried the above TOT method again, apparatly it skips a lot of things, and is done in like 30s, so it's not doing its job. I have no idea what's causing that though!
EDIT2:
IF ANYONE STILL FINDS THIS, this was the solution for me. I didn't know LG had a 'official' tool for fixing our sh*t . Hope it still helps you!

You should edit the title to include the word (solved) or (fixed).
Sent from my LG-LS980 using XDA Free mobile app

Scrytal said:
Well, I think I need some help with this one.
-Scrytal
EDIT:
Tried the above TOT method again, apparatly it skips a lot of things, and is done in like 30s, so it's not doing its job. I have no idea what's causing that though!
EDIT2:
IF ANYONE STILL FINDS THIS, this was the solution for me. I didn't know LG had a 'official' tool for fixing our sh*t . Hope it still helps you!
Click to expand...
Click to collapse
Hi, i can't boot any rom too,
I can access my download mode and recovery mode (twrp),
But i can't boot any custom rom,
And ADB can't recognize my phone,
I tried to back to stock using LG Flash Tool 2014 (the kdz ones), but nothing works,
And the official lg tool link is broken

Oneplus 2 having screen issue. Help!

Hi,
My OPT has deveoped these white spots all over the screen. I have tried wiping the device several times and also tried installing a different OS and the problem still persists. Do you think it's a h/w issue? When i boot into TWRP these spots don't appear so I think it's a software issue. Can anyone suggest methods to fix this? I have attached some screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

If it were hardware, we wouldn't be able to see it through screenshots. I suggest you reflash OxygenOS (dirty flash, no need to wipe your data) and see if that fixes it.

Waterdroid said:
If it were hardware, we wouldn't be able to see it through screenshots. I suggest you reflash OxygenOS (dirty flash, no need to wipe your data) and see if that fixes it.
Click to expand...
Click to collapse
Tried that as well, When I flash a new OS does it change the drivers for the display?

wackyrish said:
Hi,
My OPT has deveoped these white spots all over the screen. I have tried wiping the device several times and also tried installing a different OS and the problem still persists. Do you think it's a h/w issue? When i boot into TWRP these spots don't appear so I think it's a software issue. Can anyone suggest methods to fix this?
Click to expand...
Click to collapse
have u rooted the device? it seems to be a display driver problem. download the latest 2.0.2 ota (zip file about 1gb) and copy it on ur phones memory. then go into the bootloader and install it by apply update through internal memory

daninantro said:
have u rooted the device? it seems to be a display driver problem. download the latest 2.0.2 ota (zip file about 1gb) and copy it on ur phones memory. then go into the bootloader and install it by apply update through internal memory
Click to expand...
Click to collapse
I tried that as well. I wasn't able to find a 2.0.2 so I installed 2.0.1 and updated OTA to 2.0.2 Yes it is un rooted. Tried installing the CM12.1 by Temasek and still the same issue.

I suggest setting up a remote session with the Customer Support. I know it's a pain in the ass to communicate with them, but they've got the images and can reflash those.

wackyrish said:
I tried that as well. I wasn't able to find a 2.0.2 so I installed 2.0.1 and updated OTA to 2.0.2 Yes it is un rooted. Tried installing the CM12.1 by Temasek and still the same issue.
Click to expand...
Click to collapse
how were u able to install cm12.1 when ur device is not rooted? anyway contact customer support or else go to the service centre. they will help u

daninantro said:
how were u able to install cm12.1 when ur device is not rooted? anyway contact customer support or else go to the service centre. they will help u
Click to expand...
Click to collapse
Oops, Sorry meant to say that the phone is rooted and I have custom recovery installed. I live in UAE no service centers here

[Q] about "Recording Failed"

i get the error "Recording Failed" when i pressed the record button.... my sd card and phone memory still have like 10gb empty... and im using Phronesis Rom v3.0. Any solution?

what do logs say

what logs do you mean?

the logs that tell you what the error is

DSA said:
the logs that tell you what the error is
Click to expand...
Click to collapse
im not sure where to find it...i just saw the pop out error when i press the record camera icon..

aronron33 said:
im not sure where to find it...i just saw the pop out error when i press the record camera icon..
Click to expand...
Click to collapse
XDA is a developers forum/site. Not an end-user forum/site.
People are expected to search for the info the need first.
So google your issue, if that not works google howto get the right logs.
If that also doesn't succeed, write down what you have done to avoid the error.
Don't forget to put in all the needed specs, software versions and so on.
And do that in a proper post, preferably with good spelling, grammar and punctuation.
If done all that, help will be more helpful, plentiful and faster.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i cant switch to the video camera mode...

I'm out

@aronron33 Yeah you dug your own grave on this one.
You will get NO HELP, if you dont read others comments and at least try.
So bubye and goodluck finding out the problem yourself!!!

HanZie82 said:
@aronron33 Yeah you dug your own grave on this one.
You will get NO HELP, if you dont read others comments and at least try.
So bubye and goodluck finding out the problem yourself!!!
Click to expand...
Click to collapse
wow you are so helpful........i google -ed and i cant find anything about extract the logs... so i have no idea what the problem is and i cant even switch to the video camera mode so how could i get an error logs?

aronron33 said:
wow you are so helpful........i google -ed and i cant find anything about extract the logs... so i have no idea what the problem is and i cant even switch to the video camera mode so how could i get an error logs?
Click to expand...
Click to collapse
I have the same problem on my N900W8, probably you can fix it installing a 5.0 bootloader.

So I solved it by:
Using Odin 3.11.1
I have already tried Factory reset, wipe cache, wipe dalvik, flashed the latest stock Lolipop or older lollipop with ODin and nothing solved the problem.
So I tried to flash the latest stock lolipop with Odin and marking checked (Auto Reboot , F. Reset Time , Phone EFS clear, Phone Bootloader update).
I suspect that the Phone EFS clear did the trick. It's function is related to the modem and radio of the phone. And clearly the modem has a problem here.
I hope this will help anybody out there having this issue.
This problem happened after trying to flash lollipop using FlashFire app to reserve the root that I had in my previos Android KK 4.4.2.
Phone: Galaxy Note3 N9005 Malaysian

Can't Re-Unlock the Bootloader

I read through the similar thread from yesterday, but this is a different issue...
I had unlocked, installed TWRP, and had been running a custom ROM (BadBoyz 1.2). This morning I re-locked so I could flash the updated firmware (v1.80) and now I am unable to re-unlock.
When I issue the command fastboot flash unlocktoken Unlock_code.bin, it works without errors, and the phone goes to the "Are you sure you want to unlock your bootloader?" screen.
However, at that screen, the volume buttons do nothing. I can't select yes OR no, it just sits there. Eventually it times out and just shows the battery charging on a black screen.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When I flashed the firmware, it removed TWRP, and with a locked bootloader, I can't re-flash it.
I was able to get a fully stock rom up and running, so I'm not in brickville anymore (had a few hours of panic earlier today), and I've been able to confirm that the OEM Unlock option is checked. I've even unchecked and re-checked to be sure. Everything works except the ability to confirm my choice and move on. I'm kind of afraid that it's a glitch in the new firmware, at this point...
Anyone got any ideas?
Thanks!!

deleted

So, it removed TWRP and replaced the stock recovery? And now you can't reinstall TWRP because bootloader is locked? Is that where you're at?
Sent from my 2PS64 using XDA-Developers mobile app

have you tried running RUU.exe? i took that route and was able to unlock my bootloader again, flash twrp and upgrade to bb 2.0 with no problems

I had the same problem and had to flash a stock rom back on the phone before the unlocker would work.

I figured it out! I can't explain WHY it worked, but it worked...
I had re-flashed several times using the official RUU, and the results never changed...
Then yesterday I went through a mental checklist of what was different when I unlocked the first time... and the only thing, was that I hadn't put my SD Card in the phone yet when I unlocked the first time. So I went through the motions again to verify that it still didn't work, and it didn't. Then I ejected the SD Card and tried it - and BOOM, I was able to unlock!
The only thing I can think of is that the SD Card did have the Firmware .zip on it, which the phone auto-detected and asked if I wanted to install... even though I said no. As soon as I tried it without the card, it worked like it always had, I'm back to unlocked, and back to the custom ROM I had been enjoying so much...
Thanks for the tips, everyone, and I hope this thread helps someone else who finds themselves in the same boat!

scottspa74 said:
So, it removed TWRP and replaced the stock recovery? And now you can't reinstall TWRP because bootloader is locked? Is that where you're at?
Sent from my 2PS64 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes, that is EXACTLY where I was at. However, finally found the way out of the mess.. (see above post)

I have some t350's with issues recovery/MDM/black screen and bootloops

I recently found at the dumps a box of t350's 6/18 didnt like combination flashing the mdm away/new firmware install. 3 failed the same way while putting on newest firmware with odin now they say mdm mode in odin again and i have no debug access. 1 black screens in bootloader and when booting no debug access mdm mode in odin again. BUT ! I have 1 with debug access and see it in ADB BUT it fails to install due to signature verifcation of the ROM's I've tried. I think the later is savable EZ just need a a little help getting TWRP onto it I guess and I'm good. I'll worry about the others later but any ideas ? my brain hurts from trying cables/roms/adb versions lol

Maybe the rom is incorrect have you checked the region and model number etc?

Kenora_I said:
Maybe the rom is incorrect have you checked the region and model number etc?
Click to expand...
Click to collapse
the issue is the MDM mode seems like, it fails to write. only time i every got them to flash was after the combination flash the download menu popped up very slow after it was working hard to explain..... i have 7.1.1 on all the working one's which seem finebut i ****ed up i shouldve TWRP them first, one of them i successfully did get twrp on and lineage after the fact and i tried again with now another boot looping tablet SMH. idk what i did to do it the first time

TDIfrogman said:
the issue is the MDM mode seems like, it fails to write. only time i every got them to flash was after the combination flash the download menu popped up very slow after it was working hard to explain..... i have 7.1.1 on all the working one's which seem finebut i ****ed up i shouldve TWRP them first, one of them i successfully did get twrp on and lineage after the fact and i tried again with now another boot looping tablet SMH. idk what i did to do it the first time
Click to expand...
Click to collapse
no matter what i write to it twrp any firmware just fails like it did when it was mdm locked

Could you provide ODIN logs?

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

it shows mdm locked and the odin log reflects that BUT they where unlocked at some point im, afraid to try and flash the other and they'll end up like this one

TDIfrogman said:
View attachment 5364601
Click to expand...
Click to collapse
They might have NAND flash erros because they arent able to write to it.

Kenora_I said:
They might have NAND flash erros because they arent able to write to it.
Click to expand...
Click to collapse
hmmmm how can i fix it ?

It could be hardware issue, I'm not sure how to fix hardware issues. Thats probably the reason they were all together in a box.

no they where in a box because they came from a school and they didn't take knox off, there was 1000+ of them I just grabbed a tray full they have these crazy polycarbonate cases on them too with security screws. they all worked until i flashed knox away with varying results 12/18 working fine 18 worked prior but in knox

Oh that info is noted.
May I help you later. Its pretty late and I have to get off.
Ill help in the mornin