Related
I've heard ranting and raving about Malladus and I decided to flash it yesterday. It won't take the flash no matter what I do.
I've tried: Flashing 1.2.4, downloading both again to make sure it wasn't a download issue, using different gapps package, using a different lg apps package, using CWM, using TWRP, side-loading... ETC
Bottom line: My phone will not take the ROM. It flashes the LG logo and gets stuck at a black screen where the back-light is on but nothing is displayed on the screen.
I am an experienced flasher and I have no idea what is going on. I am backed up and can get into TWRP to restore so I am all good as far as not being bricked goes but I really want to try out this damn rom.
Any help would be much appreciated. Thanks.
Bump I'm having the same problem, I'm on Verizon.
NBushyy said:
Bump I'm having the same problem, I'm on Verizon.
Click to expand...
Click to collapse
Yeah same here. Verizon. Forgot to mention it.
Still a problem. Bumping.
I am in the boat with you. I thought it was just me.
Same Black Screen issue
Did anyone have any luck resolving this? Ive tried with both twrp and cwm and same issue...?
Same problem on my Verizon model. Using twrp 2.6.3.3. Other roms work fine.
How long have you left it at the black screen? Sometimes a fresh load can take up to 10 minutes.
Also, the rom will work without gapps and lgapps, so try just loading the rom. I know you downloaded twice, but did you check the md5 sum either time?
heleos said:
How long have you left it at the black screen? Sometimes a fresh load can take up to 10 minutes.
Also, the rom will work without gapps and lgapps, so try just loading the rom. I know you downloaded twice, but did you check the md5 sum either time?
Click to expand...
Click to collapse
I left it there for a good 15 minutes. I also had it plugged into my laptop. It kept detecting the phone as plugged in. Seems like it is stuck in a bootloop or something. I also tried installing only the ROM without the gapps and lgapps and had the same result. I also checked the MD5 sum and it matched. (I know I'm kinda hijacking this original post, but I think we are all having the exact same issue)
try this
trackstar1414 said:
I left it there for a good 15 minutes. I also had it plugged into my laptop. It kept detecting the phone as plugged in. Seems like it is stuck in a bootloop or something. I also tried installing only the ROM without the gapps and lgapps and had the same result. I also checked the MD5 sum and it matched. (I know I'm kinda hijacking this original post, but I think we are all having the exact same issue)
Click to expand...
Click to collapse
Can you restore your nandroid and flash say, CleanROM 1.0 or DigitalDream 2.1? OR try this:
1. Hold the power button until the device is OFF.
2. Download LG drivers to the PC (LG VZW_United_WHQL_v2.11.1) and LG mobile support tool (B2CAppSetup).
3. Install these packages.
4. Plug in you USB cable into the phone but not the computer.
5. Hold volume up and insert the USB cable to the PC- the phone should boot to 'download mode'.
6. Open the support tool and click Options>Upgrade Recovery, follow the prompts.
7. At the first prompt indentify your phone using IMEI/ESN, then click OK
8. Let it do its thing, the phone will reboot and most likely have a bunch of error messages and some FC's. Just hit okay to all messages, the phone will settle after 2 minutes or so.
9. Download freegee from market and reflash recovery of your choice.
10. Make sure you have a ROM saved to the SD to flash
11. Use freegee to reboot to recovery
12. Once in recovery you can reflash the ROM as normal.
13. Reboot and Profit!
*$* Or you could go back to Stock and start fresh!
*$* BEFORE ANY FLASH ALWAYS STOP and MAKE A NANDROID BACKUP!
Good Luck and if you get stuck let me know
geosnipe said:
Can you restore your nandroid and flash say, CleanROM 1.0 or DigitalDream 2.1? OR try this:
1. Hold the power button until the device is OFF.
2. Download LG drivers to the PC (LG VZW_United_WHQL_v2.11.1) and LG mobile support tool (B2CAppSetup).
3. Install these packages.
4. Plug in you USB cable into the phone but not the computer.
5. Hold volume up and insert the USB cable to the PC- the phone should boot to 'download mode'.
6. Open the support tool and click Options>Upgrade Recovery, follow the prompts.
7. At the first prompt indentify your phone using IMEI/ESN, then click OK
8. Let it do its thing, the phone will reboot and most likely have a bunch of error messages and some FC's. Just hit okay to all messages, the phone will settle after 2 minutes or so.
9. Download freegee from market and reflash recovery of your choice.
10. Make sure you have a ROM saved to the SD to flash
11. Use freegee to reboot to recovery
12. Once in recovery you can reflash the ROM as normal.
13. Reboot and Profit!
*$* Or you could go back to Stock and start fresh!
*$* BEFORE ANY FLASH ALWAYS STOP and MAKE A NANDROID BACKUP!
Good Luck and if you get stuck let me know
Click to expand...
Click to collapse
I am able to restore my nandroid backup so I'm not completely stuck without a phone. I will try flashing one of the other ROMs and see how it goes now. Thanks for the help so far.
trackstar1414 said:
I am able to restore my nandroid backup so I'm not completely stuck without a phone. I will try flashing one of the other ROMs and see how it goes now. Thanks for the help so far.
Click to expand...
Click to collapse
I was able to install the digital dream rom without any issue. At this point I think its the sequence I did everything. I did the latest ota before installing any Recovery. I used the loki method to install the recovery. In looking at all the roms, it appears that malladus may not be "loki patched" for people already on 12b? Other roms I have tried mention that so thats why I'm speculating this. I am by no means a developer so I might be out in left field on this one. I guess I'll stick with stock or another ROM for now until his next update.
It also looks like people are discussing this on the main ROM forum as well so hopefully it will work in the future.
Thanks again for the help and suggestions.
trackstar1414, say thanks by using the "Thanks' button like this.. keep me informed, CHEERS!
trackstar1414 said:
I was able to install the digital dream rom without any issue. At this point I think its the sequence I did everything. I did the latest ota before installing any Recovery. I used the loki method to install the recovery. In looking at all the roms, it appears that malladus may not be "loki patched" for people already on 12b? Other roms I have tried mention that so thats why I'm speculating this. I am by no means a developer so I might be out in left field on this one. I guess I'll stick with stock or another ROM for now until his next update.
It also looks like people are discussing this on the main ROM forum as well so hopefully it will work in the future.
Thanks again for the help and suggestions.
Click to expand...
Click to collapse
Wanted to share this if you haven't read it..
http://forum.xda-developers.com/showthread.php?t=2449670
I had issues originally and had to flash back to 1.2.3.
What I ended up doing was switching to CWM 6.0.4.4 ( I was using TWRP 2.6.3.3).
His boot skipped the set up wizard as well, which was odd.
His was also the only ROM I ever got stuck on the fastboot screen while using twrp.
Try ( at your own risk obviously) flashing back to an older malladus (wipe all and boot till you get through the set up wizard),
Then back to recovery, do a wipe, without wiping the system partition, Data Cache and Davlik, and flash back to 1.2.5.
I didn't try it on 1.2.5. But that's how I got into 1.2.4.
Srvisg0d said:
I've heard ranting and raving about Malladus and I decided to flash it yesterday. It won't take the flash no matter what I do.
I've tried: Flashing 1.2.4, downloading both again to make sure it wasn't a download issue, using different gapps package, using a different lg apps package, using CWM, using TWRP, side-loading... ETC
Bottom line: My phone will not take the ROM. It flashes the LG logo and gets stuck at a black screen where the back-light is on but nothing is displayed on the screen.
I am an experienced flasher and I have no idea what is going on. I am backed up and can get into TWRP to restore so I am all good as far as not being bricked goes but I really want to try out this damn rom.
Any help would be much appreciated. Thanks.
Click to expand...
Click to collapse
Are you on 12B OTA? If so, that would be your issue. I took the 12B OTA and tried flashing Malladus and got the same issue you have. You can revert your phone to 11A and that should resolve your issue. http://forum.xda-developers.com/showthread.php?t=2448960 it will erase everything on your phone and go back to unroot.
I unlocked my Nexus 10 bootloader, then installed the latest CWM, and finally the latest SuperSU, and it's all fine. But it seems that the only way to get into recovery is to first go into the bootloader (hold power, vol up and vol down) then select recovery from there. And when I leave recovery to boot back into the OS (stock - i've not flashed any other roms yet) I get a warning about how stock is going to revert my recovery and lose root, and do I want to try and fix it, and how this cannot be reversed. I select fix it, but next time I try and get into recovery it's not there. Is this normal, or a known problem? Have I done something wrong? I don't want to fiddle around too much and brick my device; it works perfectly and the only reason I did all this was so I could install an app to prevent me from having to connect my N10 to my pc to used ADB over USB - I much prefer doing it all over Wifi!
poldie said:
I unlocked my Nexus 10 bootloader, then installed the latest CWM, and finally the latest SuperSU, and it's all fine. But it seems that the only way to get into recovery is to first go into the bootloader (hold power, vol up and vol down) then select recovery from there. And when I leave recovery to boot back into the OS (stock - i've not flashed any other roms yet) I get a warning about how stock is going to revert my recovery and lose root, and do I want to try and fix it, and how this cannot be reversed. I select fix it, but next time I try and get into recovery it's not there. Is this normal, or a known problem? Have I done something wrong? I don't want to fiddle around too much and brick my device; it works perfectly and the only reason I did all this was so I could install an app to prevent me from having to connect my N10 to my pc to used ADB over USB - I much prefer doing it all over Wifi!
Click to expand...
Click to collapse
Try Quick Boot in the Playstore.
sfobrien said:
Try Quick Boot in the Playstore.
Click to expand...
Click to collapse
I might try that but really I'm more concerned about my recovery going missing when I exit it.
Strange, never seen that and can't reproduce it. I suggest switch to TWRP and maybe custom ROM and see if that corrects the issue.
Is recovery returned to stock or just flat out missing? I haven't had a permanent recovery, stock or non-stock, on mine for some time now though it will still work loading temp recoveries.
mhausig said:
Is recovery returned to stock or just flat out missing? I haven't had a permanent recovery, stock or non-stock, on mine for some time now though it will still work loading temp recoveries.
Click to expand...
Click to collapse
I don't think anything actually happened - it just warned me that it might, and that I could either do nothing, or copy some files into system.
In the end I used TWRP which doesn't have the same problem.
This allowed me to return to my original problem, where I discovered that my game doesn't have a bug; instead, every single Nexus 10 has a problem with multitouch which Google doesn't even acknowledge, let alone fix.
Hey all,
My nexus 4 got some weird software bug (the UI would crash on boot a few times then screen would go black and I couldn't do anything) and I tried to flash a new rom. Somehow I have managed to corrupt (I think) the partition and now I can't fix it. when I try to flash a rom it tells me that it can't mount /sdcard. I have tried to sideload a rom and it fails and I have also tried to mount /sdcard through adb and it also failed. I tried to follow the instructions on http://forum.xda-developers.com/showthread.php?t=1949372 and think I have now completely wrecking the partition. I can still get into recovery and fastboot to run commands but I have no idea how to fix this. If there is a way to completely reformat/set up the phone from scratch that'd be awesome.. otherwise I will need to buy a new phone.
Cheers
lilfellabob said:
Hey all,
My nexus 4 got some weird software bug (the UI would crash on boot a few times then screen would go black and I couldn't do anything) and I tried to flash a new rom. Somehow I have managed to corrupt (I think) the partition and now I can't fix it. when I try to flash a rom it tells me that it can't mount /sdcard. I have tried to sideload a rom and it fails and I have also tried to mount /sdcard through adb and it also failed. I tried to follow the instructions on http://forum.xda-developers.com/showthread.php?t=1949372 and think I have now completely wrecking the partition. I can still get into recovery and fastboot to run commands but I have no idea how to fix this. If there is a way to completely reformat/set up the phone from scratch that'd be awesome.. otherwise I will need to buy a new phone.
Cheers
Click to expand...
Click to collapse
Have you tried just loading the factory images from Google?
acejavelin said:
Have you tried just loading the factory images from Google?
Click to expand...
Click to collapse
Thanks for the reply. I did download them but figured if I couldn't flash a different rom I wouldn't be able to go to Google's one.. How would I go about that?
lilfellabob said:
Thanks for the reply. I did download them but figured if I couldn't flash a different rom I wouldn't be able to go to Google's one.. How would I go about that?
Click to expand...
Click to collapse
You don't flash it in recovery... Just follow Googles instructions from where you downloaded it.
ahh I see, through fastboot. I tried some stuff in fastboot but not sure if I tried with this - will try again tonight. Thanks again!
After getting home I have tried to get my phone into recovery mode but cannot do it. I have held the buttons for ages and ages and tried some battery reset by holding power and volume up for 60 seconds which also didn't work. I figure this could be a issue with the battery because when I try to enter recovery I get a red led that flashes. The only thing I have been able to get is 'download mode' as shown in this thread: http://forum.xda-developers.com/nexus-4/help/nexus-4-download-mode-t2102412 but I don't know how to use that to flash anything (adb and fastboot cannot see the phone).
The only other thing I have in mind is taking the cover off and disconnecting the battery bridge, apparenly this can fix it. Any ideas?
Hello,
Like the title says, I have a Samsung J5, I rooted it as soon as I got it maybe a year or so ago.
I never had any issues with it. This morning, however I made a (now in hindsight) bad decision by factory resetting, dont even ask me why I thought I needed to factory reset it, I already did it.
Anyways, I did the factory reset from the phone and it instantly rebooted into TWRP, and here's where I got lost. I don't know what to do from here.
I assumed the phone would just reset itself, but it always reboots in recovery mode.
I thought maybe I had to flash a ROM again (I flashed a custom one and then stock back when I first rooted it, but my memory is terrible and I just have faint memories of it), I looked that up and found I needed Odin, the stock rom I wanted to flash and to reboot into download mode. So I got all I required and I don't think Odin is finding my phone.
My phone just has the blue screen saying downloading... and do not turn off target. Nothing else. and Odin doesn't show anything (I think it's supposed to show the device somewhere? Anyways, I'm super lost and I have no idea what to do.
I mostly just need someone to point me in the right direction, maybe some instructions I can follow or something, I'm not super experienced as you can tell but I can follow basic instructions when I'm not being dumb.
TL;DR: Did factory reset on rooted J5, now it only boots into TWRP, no idea where to go from here, stock rom flash?
4tson said:
Hello,
Like the title says, I have a Samsung J5, I rooted it as soon as I got it maybe a year or so ago.
I never had any issues with it. This morning, however I made a (now in hindsight) bad decision by factory resetting, dont even ask me why I thought I needed to factory reset it, I already did it.
Anyways, I did the factory reset from the phone and it instantly rebooted into TWRP, and here's where I got lost. I don't know what to do from here.
I assumed the phone would just reset itself, but it always reboots in recovery mode.
I thought maybe I had to flash a ROM again (I flashed a custom one and then stock back when I first rooted it, but my memory is terrible and I just have faint memories of it), I looked that up and found I needed Odin, the stock rom I wanted to flash and to reboot into download mode. So I got all I required and I don't think Odin is finding my phone.
My phone just has the blue screen saying downloading... and do not turn off target. Nothing else. and Odin doesn't show anything (I think it's supposed to show the device somewhere? Anyways, I'm super lost and I have no idea what to do.
I mostly just need someone to point me in the right direction, maybe some instructions I can follow or something, I'm not super experienced as you can tell but I can follow basic instructions when I'm not being dumb.
TL;DR: Did factory reset on rooted J5, now it only boots into TWRP, no idea where to go from here, stock rom flash?
Click to expand...
Click to collapse
Try factory reset in TWRP under "wipe" and try rebooting then.
If that doesn't work download a rom from xda for your device onto an sd card. Then put the sd card into the phone, Reboot into twrp and flash the ROM.
The reason odin isn't picking up your device is more than likely USB debugging isn't enabled which you can only do from inside the phones settings. Enable it once you flash the new rom and then flash your old firmware using odin afterwards if you wish.
Do you know what model it is?
Or even what year model it is? 2015?/16?/17?
If you can boot into twrp you have nothing to worry about as it can be easily resolved
garylawwd said:
Try factory reset in TWRP under "wipe" and try rebooting then.
If that doesn't work download a rom from xda for your device onto an sd card. Then put the sd card into the phone, Reboot into twrp and flash the ROM.
The reason odin isn't picking up your device is more than likely USB debugging isn't enabled which you can only do from inside the phones settings. Enable it once you flash the new rom and then flash your old firmware using odin afterwards if you wish.
Do you know what model it is?
Or even what year model it is? 2015?/16?/17?
If you can boot into twrp you have nothing to worry about as it can be easily resolved
Click to expand...
Click to collapse
Hey
I have already tried doing the factory reset from TWRP, but when I reboot after that it goes back into recovery mode, if I try to reboot from recovery mode into system it just goes back to recovery mode as well.
I'll try downloading another rom, I got the stock one in there but it doesn't flash it from TWRP, which I'm pretty sure is expected behaviour anyways.
The model is SM-J510MN 2016, I'll start looking for a rom.
Thanks
4tson said:
Hey
I have already tried doing the factory reset from TWRP, but when I reboot after that it goes back into recovery mode, if I try to reboot from recovery mode into system it just goes back to recovery mode as well.
I'll try downloading another rom, I got the stock one in there but it doesn't flash it from TWRP, which I'm pretty sure is expected behaviour anyways.
The model is SM-J510MN 2016, I'll start looking for a rom.
Thanks
Click to expand...
Click to collapse
You can't flash the stock rom in TWRP because it is a .zip.tar file and twrp can only flash .zip files or .img files
garylawwd said:
You can't flash the stock rom in TWRP because it is a .zip.tar file and twrp can only flash .zip files or .img files
Click to expand...
Click to collapse
Yeah, I may or may not have already tried hehe.
You wouldn't happen to have a rom that's not being hosted on Mega would you? I exceeded my limit when I was 95% done downloading one of them.
I think I found one, whoops.
4tson said:
Hello,
Like the title says, I have a Samsung J5, I rooted it as soon as I got it maybe a year or so ago.
I never had any issues with it. This morning, however I made a (now in hindsight) bad decision by factory resetting, dont even ask me why I thought I needed to factory reset it, I already did it.
Anyways, I did the factory reset from the phone and it instantly rebooted into TWRP, and here's where I got lost. I don't know what to do from here.
I assumed the phone would just reset itself, but it always reboots in recovery mode.
I thought maybe I had to flash a ROM again (I flashed a custom one and then stock back when I first rooted it, but my memory is terrible and I just have faint memories of it), I looked that up and found I needed Odin, the stock rom I wanted to flash and to reboot into download mode. So I got all I required and I don't think Odin is finding my phone.
My phone just has the blue screen saying downloading... and do not turn off target. Nothing else. and Odin doesn't show anything (I think it's supposed to show the device somewhere? Anyways, I'm super lost and I have no idea what to do.
I mostly just need someone to point me in the right direction, maybe some instructions I can follow or something, I'm not super experienced as you can tell but I can follow basic instructions when I'm not being dumb.
TL;DR: Did factory reset on rooted J5, now it only boots into TWRP, no idea where to go from here, stock rom flash?
Click to expand...
Click to collapse
maybe install usb drivers and try this: disconnect device, hold power, home and vol up key, connect device and then press volume up to enter download mode
Dyeide said:
maybe install usb drivers and try this: disconnect device, hold power, home and vol up key, connect device and then press volume up to enter download mode
Click to expand...
Click to collapse
Yep, I tried that, although I'm not sure the USB drivers I downloaded were correct, since the official page isn't working at least for me. So I downloaded what the websites claimed were the correct drivers, I went into download mode that way, which has some debug info on the top left stating it's in Odin mode, but Odin still didn't recognize it.
I'm pretty sure usb debug options were turned on before this, but I'm not sure if the factory reset could've messed with that, thought I'm assuming it could be part of it.
I'm currently trying to download some custom roms to follow garylawwd's advice, I'll reply once I've got results.
garylawwd said:
You can't flash the stock rom in TWRP because it is a .zip.tar file and twrp can only flash .zip files or .img files
Click to expand...
Click to collapse
So I downloaded one, wiped everything, installed it via twrp, it apparently installed it correctly, rebooted the system and it went straight into recovery mode again. It's not letting me reboot into anything that isn't download or recovery. Any other ideas? Am I doing something wrong?
4tson said:
So I downloaded one, wiped everything, installed it via twrp, it apparently installed it correctly, rebooted the system and it went straight into recovery mode again. It's not letting me reboot into anything that isn't download or recovery. Any other ideas? Am I doing something wrong?
Click to expand...
Click to collapse
Uhm, so after doing that I flashed the latest twrp version (I had 3.0.2 or something), rebooted after flashing the image, did a wipe from there, rebooted and it now didn't boot into recovery mode but instead I'm now on a white screen with the samsung logo in the middle looping from light grey to black. I'll look into that I guess...
4tson said:
Uhm, so after doing that I flashed the latest twrp version (I had 3.0.2 or something), rebooted after flashing the image, did a wipe from there, rebooted and it now didn't boot into recovery mode but instead I'm now on a white screen with the samsung logo in the middle looping from light grey to black. I'll look into that I guess...
Click to expand...
Click to collapse
After it got stuck on the samsung logo I rebooted into recovery mode, flashed the custom rom once again, rebooted and it's still stuck on the samsung logo. Lost once more.
4tson said:
After it got stuck on the samsung logo I rebooted into recovery mode, flashed the custom rom once again, rebooted and it's still stuck on the samsung logo. Lost once more.
Click to expand...
Click to collapse
Go into twrp and go to wipe. Click advanced wipe and wipe system, internal, data, dalvik cache.
Then flash the ROM again and reboot
garylawwd said:
Go into twrp and go to wipe. Click advanced wipe and wipe system, internal, data, dalvik cache.
Then flash the ROM again and reboot
Click to expand...
Click to collapse
Tried this just now, it rebooted twice and on the second reboot it got stuck on the logo once again.
I think I'm done trying to mess around with it, I'll take it to a repair place :/
Thanks for looking out though, definitely appreciate your tips even if they didn't end up working out. :good:
4tson said:
After it got stuck on the samsung logo I rebooted into recovery mode, flashed the custom rom once again, rebooted and it's still stuck on the samsung logo. Lost once more.
Click to expand...
Click to collapse
https://forum.xda-developers.com/ga...nt/recovery-twrp-3-1-2-blue-dogerino-t3768707 Try flashing this recovery it's a newer version.Just download the .img file and install it through twrp as recovery when prompted.
4tson said:
So I downloaded one, wiped everything, installed it via twrp, it apparently installed it correctly, rebooted the system and it went straight into recovery mode again. It's not letting me reboot into anything that isn't download or recovery. Any other ideas? Am I doing something wrong?
Click to expand...
Click to collapse
Why would you try a ROM which has not been updated for months,get a recent one like Lineage OS just to try if it works,its also small in size.
DontTouchMaPhone said:
Why would you try a ROM which has not been updated for months,get a recent one like Lineage OS just to try if it works,its also small in size.
Click to expand...
Click to collapse
He wants to just enable USB debugging in devoloper options because he wants the stock firmware and his pc isn't recognising his phone because this option isn't enabled.
He has twrp so flashing any rom will do just to get into the phone and enable USB debugging so he can flash the stock firmware through odin
garylawwd said:
He wants to just enable USB debugging in devoloper options because he wants the stock firmware and his pc isn't recognising his phone because this option isn't enabled.
He has twrp so flashing any rom will do just to get into the phone and enable USB debugging so he can flash the stock firmware through odin
Click to expand...
Click to collapse
I understand why he is using a custom rom,I mean why did he try one that has not been updated for ages because maybe its the rom causing bootloop
DontTouchMaPhone said:
I understand why he is using a custom rom,I mean why did he try one that has not been updated for ages because maybe its the rom causing bootloop
Click to expand...
Click to collapse
Hey, so yeah, I was just looking for any rom, didn't really look for anything in particular, just got the first one I found in order to just get into the phone.
I ended up just taking it to a repair place after not having much luck myself, I don't know what exactly they did, but I now have that ROM flashed and I have access to the phone, I'm not sure if I want to try flashing either a different custom rom now, stock, or just sticking to this, since I'm sorta scared it will get messed up again and I'll have to go back to that repair place.
4tson said:
Hey, so yeah, I was just looking for any rom, didn't really look for anything in particular, just got the first one I found in order to just get into the phone.
I ended up just taking it to a repair place after not having much luck myself, I don't know what exactly they did, but I now have that ROM flashed and I have access to the phone, I'm not sure if I want to try flashing either a different custom rom now, stock, or just sticking to this, since I'm sorta scared it will get messed up again and I'll have to go back to that repair place.
Click to expand...
Click to collapse
Are you on stock now?
DontTouchMaPhone said:
Are you on stock now?
Click to expand...
Click to collapse
Nope, I'm on Extreme ux 8.0, which is what I downloaded to try to get into the phone to turn on the usb debugging option, the guy that repaired it must've noticed it was already on my SD card and flashed it without telling me.
Like I said, I kind of want to go back to stock but I'm sort of scared of touching it and having it get stuck again, I've kinda got used to this rom's little issues by now though I suppose.
4tson said:
Nope, I'm on Extreme ux 8.0, which is what I downloaded to try to get into the phone to turn on the usb debugging option, the guy that repaired it must've noticed it was already on my SD card and flashed it without telling me.
Like I said, I kind of want to go back to stock but I'm sort of scared of touching it and having it get stuck again, I've kinda got used to this rom's little issues by now though I suppose.
Click to expand...
Click to collapse
Wait,so you paid for the repair right?And he flashed you a custom rom?Looks pretty scammy to me..Anyways do you have twrp or stock recovery?
Morning
I have an issue with an OP5 I'm trying to get working again. I got this phone secondhand, it was advertised as having freezing/reboot issues. I used the phone for a while and confirmed this was the case, broadly speaking it did the following (I never wholly nailed it down):
it froze at charging so would need to be booted into bootloader and started from there
it went into a weird vegetative state sometimes after charging (black screen, LED glowing whitish), which only a reboot in the manner above would fix
it would occasionally freeze after a normal reboot (about 5-10 seconds in) if I immediately started using it
it did not execute random reboots often, mainly just freezes
there was on-screen weirdness, sometimes flickering along edges of screen, sometimes whole screen freak outs with colour inversion or whatever...rebooting the phone fixed it
The phone was on stock ROM (latest 9.0.9) so I thought I might fix it by flashing Lineage Pie onto it, which I did yesterday; I also flashed TWRP codeworx onto it too....so far so good.
The phone immediately was working much better, it was not having boot issues, it seemed to be running great, I thought it must be something on the stock ROM which was causing the issues so was happy. I got busy rooting it (Magisk) and getting gapps back on - happy days. Plugged it in last night to charge, phone was left on.
This morning, vegetative phone again. Turned it on (normal way) and got to lockscreen - entered pin, back to lockscreen, did this several times, still got to lockscreen. I now realise it wasn't recognising the pin.
Rebooted the phone. Straight to TWRP, and the 'decrypt data' screen - entering the pin here showed the 'password not recognised'. So can't now enter TWRP or decrypt. Nor can I start phone normally. It just defaults back to TWRP.
I can get to the fastboot screen. The phone is recognised by my PC, shows device number and 'fastboot' in powershell window. Works with ADB also (shows device, can switch between recovery and bootloader no problem)....so....
I tried reflashing the stock recovery....figuring I could do a factory reset...'could not load [filename]'....
So, it looks like I'm a bit stuck. Any help very gratefully accepted :good:
apologies
meant to post this in questions and answers...my bad...please feel free to move this
First wipe from bootloader, and then format from bootloader.
You will lose all you data and files, but unless your data is decrypted, you cannot enter TWRP.
Otherwise, you can try the CodeworkX Force Decrypt TWRP and then try that. That would be the only option.
GitManMatt said:
Rebooted the phone. Straight to TWRP, and the 'decrypt data' screen - entering the pin here showed the 'password not recognised'. So can't now enter TWRP or decrypt. Nor can I start phone normally. It just defaults back to TWRP.
So, it looks like I'm a bit stuck. Any help very gratefully accepted :good:
Click to expand...
Click to collapse
This is probably not related to hardware. Instead, one or more of your firmware partitions got messed up. You need to install a full stock rom and boot once. After that, you should be able to do whatever you want. Before installing stock, load TWRP. At a password prompt press cancel button and you will get to TWRP's usual screen. Swipe to allow modifications. Then go to wipe and try to format data (where you get the 'confirm' prompt). If that worked, then format system/vendor/data. Reboot to TWRP, load stock rom and flash it.
If format data doesn't work, then do the same in fastboot.
I've had the same issue using the wrong twrp for the ROM version I've been on
GitManMatt said:
meant to post this in questions and answers...my bad...please feel free to move this
Click to expand...
Click to collapse
No problem, and it's great that you noticed it yourself. I've found your thread just by accident and moved it to Q&A.
To get moderator's attention best is to simply use the report functionality.
Oswald Boelcke said:
No problem, and it's great that you noticed it yourself. I've found your thread just by accident and moved it to Q&A.
To get moderator's attention best is to simply use the report functionality.
Click to expand...
Click to collapse
Thanks Oswald ?
Thanks guys, a few questions....
vdbhb59 said:
First wipe from bootloader, and then format from bootloader.
You will lose all you data and files, but unless your data is decrypted, you cannot enter TWRP.
Otherwise, you can try the CodeworkX Force Decrypt TWRP and then try that. That would be the only option.
Click to expand...
Click to collapse
Thanks for this really appreciate it; I think that this is what I need to do - wipe and format from bootloader, clean flash of full stock ROM - I'm not worried about the data/files as having nothing on it at the moment - what commands do I need to execute to do this?
If you could point me towards the Force Decrypt TWRP would appreciate it also, though I'm guessing this might not work as I can't flash a new recovery?
optimumpro said:
This is probably not related to hardware. Instead, one or more of your firmware partitions got messed up. You need to install a full stock rom and boot once. After that, you should be able to do whatever you want. Before installing stock, load TWRP. At a password prompt press cancel button and you will get to TWRP's usual screen. Swipe to allow modifications. Then go to wipe and try to format data (where you get the 'confirm' prompt). If that worked, then format system/vendor/data. Reboot to TWRP, load stock rom and flash it.
If format data doesn't work, then do the same in fastboot.
Click to expand...
Click to collapse
OK I'm guessing this might be the Force Decrypt TWRP mentioned above...or...? I guessed it might have something to do with a partition but I'm a bit too much of a noob to know what to do to fix that, though I'm presuming a full wipe then reinstall fixes all evils... :angel:....
I welcome the commands for the wipe if you guys can help me out. Thanks for your time appreciate it
GitManMatt said:
Thanks for this really appreciate it; I think that this is what I need to do - wipe and format from bootloader, clean flash of full stock ROM - I'm not worried about the data/files as having nothing on it at the moment - what commands do I need to execute to do this?
Click to expand...
Click to collapse
Just flash like this
fastboot flash zip stock.zip
Where stock.zip is your ROM file renamed to make it easier.
Ensure you are running the CMD from the path where your stock.zip is present. Run it as admin if it gives error.
Ideally you will find your adb in c:\adb
Once you are done, boot to system. Then once first setup is done, flash twrp via fastboot by
fastboot flash recovery recovery.img
GitManMatt said:
If you could point me towards the Force Decrypt TWRP would appreciate it also, though I'm guessing this might not work as I can't flash a new recovery?
Click to expand...
Click to collapse
Download from here: https://sourceforge.net/projects/ch...signed-forcedecrypt-cheeseburger.img/download
It will work once you have flashed the stock ROM. Also once you have formatted your data.
GitManMatt said:
OK I'm guessing this might be the Force Decrypt TWRP mentioned above...or...? I guessed it might have something to do with a partition but I'm a bit too much of a noob to know what to do to fix that, though I'm presuming a full wipe then reinstall fixes all evils... :angel:....
I welcome the commands for the wipe if you guys can help me out. Thanks for your time appreciate it
Click to expand...
Click to collapse
Fastboot wipe data command is: fastboot flashall -w
It wipes the /data partition.
vdbhb59 said:
Just flash like this
fastboot flash zip stock.zip
Where stock.zip is your ROM file renamed to make it easier.
Ensure you are running the CMD from the path where your stock.zip is present. Run it as admin if it gives error.
Ideally you will find your adb in c:\adb
Once you are done, boot to system. Then once first setup is done, flash twrp via fastboot by
fastboot flash recovery recovery.img
Download from here: https://sourceforge.net/projects/ch...signed-forcedecrypt-cheeseburger.img/download
It will work once you have flashed the stock ROM. Also once you have formatted your data.
Fastboot wipe data command is: fastboot flashall -w
It wipes the /data partition.
Click to expand...
Click to collapse
Thanks guys, I sort of got there in the end. Flashing the stock ROM through fastboot did not work as outlined above. It kept saying there was insufficent space (I can't remember the exact wording, but something along those lines). Anyway I ran the 'fastboot erase recovery' line and the same for formatting then flashed the TWRP with the link above. This opened fine and decrypted. I went to the Wipe section and formatted data, got loads of error messages, but when I rebooted into recovery and did it again it went through fine. In doing so, the internal storage was now visible in Windows Explorer. I copied the Stock ROM zip across to the internal storage then flashed it - bam, up and running. Seems to be working fine but will report back if not.
GitManMatt said:
Thanks guys, I sort of got there in the end. Flashing the stock ROM through fastboot did not work as outlined above. It kept saying there was insufficent space (I can't remember the exact wording, but something along those lines). Anyway I ran the 'fastboot erase recovery' line and the same for formatting then flashed the TWRP with the link above. This opened fine and decrypted. I went to the Wipe section and formatted data, got loads of error messages, but when I rebooted into recovery and did it again it went through fine. In doing so, the internal storage was now visible in Windows Explorer. I copied the Stock ROM zip across to the internal storage then flashed it - bam, up and running. Seems to be working fine but will report back if not.
Click to expand...
Click to collapse
Trial and error always works. The first time I had ever rooted, back in 2011, was a nightmare. My phone wont boot into any mode. I got through the night at 5 in the morning. :good:
https://photos.app.goo.gl/Zi84K4jqQsoKZjZh9
Screen glitch I was on about in the opening post. Not seen it since. Still trialling the phone but seems to be running fine now. One thing... The issue with the freezing and white Led was down to the screen saver being set to on... Disabling it got rid of the unresponsive phone. Seems I was plugging it onto charge, the screen saver was kicking in and causing it to freeze. Same seemed to be happening if just left.
No obvious screen glitch now. Fingers crossed....
It's back....
GitManMatt said:
https://photos.app.goo.gl/Zi84K4jqQsoKZjZh9
Screen glitch I was on about in the opening post. Not seen it since. Still trialling the phone but seems to be running fine now. One thing... The issue with the freezing and white Led was down to the screen saver being set to on... Disabling it got rid of the unresponsive phone. Seems I was plugging it onto charge, the screen saver was kicking in and causing it to freeze. Same seemed to be happening if just left.
No obvious screen glitch now. Fingers crossed....
Click to expand...
Click to collapse
update....nope, it's not the screensaver.
Plugged phone in to charge last night and this morning got same issues....videos here (apologies for length and shakiness, just raw footage)
https://photos.app.goo.gl/m22nUMs8LJZzGfcV7
and
https://photos.app.goo.gl/YkuMSSSqMigFQUun8
Basically it's freezing and off, but with the LED glowing whitish, as shown. It took several attempts to get it to respond and reboot as you can see. Once it was up and running it crashed a couple of times - freeze/reboot, and a full screen fuzz-out (badly tuned telly kind of static) followed by a reboot...as always eventually once it gets going it seems to be running fine again. I was using it fairly extensively last night and it seemed OK, as I was going through my apps setting them up again or playing a few games (e.g. Clash which uses a fair bit of processor power and battery).
So it looks like it's something around the boot, though why it occasionally just switches off I don't know. As this is now a full and clean firmware reinstall...what could it be?
GitManMatt said:
update....nope, it's not the screensaver.
Plugged phone in to charge last night and this morning got same issues....videos here (apologies for length and shakiness, just raw footage)
https://photos.app.goo.gl/m22nUMs8LJZzGfcV7
and
https://photos.app.goo.gl/YkuMSSSqMigFQUun8
Basically it's freezing and off, but with the LED glowing whitish, as shown. It took several attempts to get it to respond and reboot as you can see. Once it was up and running it crashed a couple of times - freeze/reboot, and a full screen fuzz-out (badly tuned telly kind of static) followed by a reboot...as always eventually once it gets going it seems to be running fine again. I was using it fairly extensively last night and it seemed OK, as I was going through my apps setting them up again or playing a few games (e.g. Clash which uses a fair bit of processor power and battery).
So it looks like it's something around the boot, though why it occasionally just switches off I don't know. As this is now a full and clean firmware reinstall...what could it be?
Click to expand...
Click to collapse
Do something, install the OOS via the MSMTool for 9.0.9 and first boot it, set it up and then make any changes. The MSM Post Link: https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
vdbhb59 said:
Do something, install the OOS via the MSMTool for 9.0.9 and first boot it, set it up and then make any changes. The MSM Post Link: https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
Click to expand...
Click to collapse
Thanks I'll give it a go - may take a bit of time as I need to find a moment to do it :good:
vdbhb59 said:
Do something, install the OOS via the MSMTool for 9.0.9 and first boot it, set it up and then make any changes. The MSM Post Link: https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
Click to expand...
Click to collapse
OK, I managed that really easily, ran like a charm, didn't need to mess about loading drivers as it was recognised straight away. I'll let you know how it goes.....
Nope hasn't fixed it....
GitManMatt said:
Nope hasn't fixed it....
Click to expand...
Click to collapse
OK, back to the start again
On charge (screen off) pressing the power button to wake the phone gets this fuzzy screen....this occasionally flashes up when actually using the phone.
Otherwise, I tried using it and running screen record to see if I could capture any further moments, but nothing yet.
The phone (before I started recording) did reboot randomly during playback of a youtube video (I was trying to see if it was something to do with overloading of the processors).
It does seem to have something to do with 'active use' i.e. processor heavy use rather than normal passive use....e.g. playing a game can make is crash/soft reboot (cuts out, goes black, button lights still on, comes back and locked after a few seconds) and occasionally fully reboots.
Puzzler this one...can't see how this is a firmware issue now?
GitManMatt said:
OK, back to the start again
On charge (screen off) pressing the power button to wake the phone gets this fuzzy screen....this occasionally flashes up when actually using the phone.
Otherwise, I tried using it and running screen record to see if I could capture any further moments, but nothing yet.
The phone (before I started recording) did reboot randomly during playback of a youtube video (I was trying to see if it was something to do with overloading of the processors).
It does seem to have something to do with 'active use' i.e. processor heavy use rather than normal passive use....e.g. playing a game can make is crash/soft reboot (cuts out, goes black, button lights still on, comes back and locked after a few seconds) and occasionally fully reboots.
Puzzler this one...can't see how this is a firmware issue now?
Click to expand...
Click to collapse
actually one thing it hasn't done lately is completely go vegetative with the white light on.....
GitManMatt said:
actually one thing it hasn't done lately is completely go vegetative with the white light on.....
Click to expand...
Click to collapse
Just as an update - sold this lemon and bought a new handset (128gb OP5) so happy days