Database Users

Brick (I guess)

I just bricked my device I guess.
First off flashed:
http://forum.xda-developers.com/showthread.php?t=1162302
TouchWiz UX for 10.1
- Cleared all (factory reset)
Which was working nicely, but then I needed some extra kernel modules, so I installed:
http://forum.xda-developers.com/showthread.php?t=1175299
3.1 Galaxy Tab Wifi OC1.6
- Cleared all (factory reset)
It booted at first, but then rebooted and eventually went to black screen. Now powering up won't work.
So yes it really won't come to life out of it's own.
-------------
My first step: Hang it to a PC
Well it recognized the tab, and was asking for the APX driver, which I found over here: http://forum.xda-developers.com/showpost.php?p=11901016&postcount=75
Which installed correctly, and is recognizing my device (for now).
Who can help me further (it is possible to backup and restore using nvflash)
-- Update 0x4 error...
NVFlash seems to be a dead end. You can't use it without sbk, which we don't have. Any more suggestions?

Use Odin to flash CWM recovery (if you haven't already), then reinstall a ROM using Clockwork Mod.
sassafras

Could be "sleep of death" there are other threads on here about it. There are various ideas about waking it up, but just letting the battery discharge and then charging it worked for my (unmodded) tab. Admittedly that is a little tricky when you can't power it on in the first place!
Sent from my GT-I9000 using XDA App

sassafras_ said:
Use Odin to flash CWM recovery (if you haven't already), then reinstall a ROM using Clockwork Mod.
sassafras
Click to expand...
Click to collapse
Been there, done that... I've flashed all through CWM recovery, always made a backup, but it doesn't go through the bootloader anymore, so I can't access the recovery, nor the download mode (for Odin flashing).
The only thing I can access at the moment is that stupid NVFlash, and since my device is I/O locked, I can't flash anything.

tmbk said:
Could be "sleep of death" there are other threads on here about it. There are various ideas about waking it up, but just letting the battery discharge and then charging it worked for my (unmodded) tab. Admittedly that is a little tricky when you can't power it on in the first place!
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I will check on this. It's the only way to fully reset my device. Since it is I/O locked, it can't have harmed my bootloader or CWM recovery.
I made sure before flashing that the MD5 checksum was right (which it was). The only thing it flashed was a kernel. Well I will drain my battery and check if it is possible to boot it up after that. Else I buy a new one

Exact same thing happened to me.. ran poitee kernel over OTA update.. killed everything but nvflash + all black screen.
Cannot get it to flash w/ bootloader.. Have 2 days to RMA and I really don't want my data out there in the event this thing comes back up after the battery dies.
PS- My unit was bootloader unlocked and rooted.

[Q] Stuck in bootloop - from stupidity?

So. I've finally done it - gone way beyond my comprehension. I'm not exactly new to flashing roms/kernels, but I'm certainly still at the noob level.
Here's what I did: I have Pac Man rom (22.2.0-rc1). I've tried different kernels but have a very poor signal at home and it's very hard to connect to wifi at home even though other devices connect flawlessly. Even the latest Franco (both stable and nightly) have a lot of problems with the wifi. So, I just made a nandroid in TWRP, flashed cwm-radio-m9615a-cefwmazm-2.0.1700.54.zip, then flashed Faux123+Shaky156V0.4.zip, then wiped cache/delvik then rebooted system. (I did all of this by copying the files into the ready-to-flash/root files and simply flashed them via TWRP.
Here's the problem: I'm stuck on PACs boot screen. The little pac man game-type animation runs, then it goes to the PAC is loading screen and stays there. And I can't get back to TWRP. If I hold the power/volume up& down keys, it simply reboots right to the rom and goes back to the bootloop.
I've tried searching XDA for a solution but can't find one. Any advice? Thanks!

david251 said:
So. I've finally done it - gone way beyond my comprehension. I'm not exactly new to flashing roms/kernels, but I'm certainly still at the noob level.
Here's what I did: I have Pac Man rom (22.2.0-rc1). I've tried different kernels but have a very poor signal at home and it's very hard to connect to wifi at home even though other devices connect flawlessly. Even the latest Franco (both stable and nightly) have a lot of problems with the wifi. So, I just made a nandroid in TWRP, flashed cwm-radio-m9615a-cefwmazm-2.0.1700.54.zip, then flashed Faux123+Shaky156V0.4.zip, then wiped cache/delvik then rebooted system. (I did all of this by copying the files into the ready-to-flash/root files and simply flashed them via TWRP.
Here's the problem: I'm stuck on PACs boot screen. The little pac man game-type animation runs, then it goes to the PAC is loading screen and stays there. And I can't get back to TWRP. If I hold the power/volume up& down keys, it simply reboots right to the rom and goes back to the bootloop.
I've tried searching XDA for a solution but can't find one. Any advice? Thanks!
Click to expand...
Click to collapse
Its volume down + power button... not power + vol up/down. Do that then use the volume up/down buttons to go to RECOVERY and then boot into recovery.
I don't see why flashing those two would cause it to bootloop.... maybe bad MD5 hash?

zephiK said:
Its volume down + power button... not power + vol up/down.
Click to expand...
Click to collapse
Thanks - got it. I definitely appreciate your time and help.

david251 said:
Thanks - got it. I definitely appreciate your time and help.
Click to expand...
Click to collapse
Welcome, hit the thanks button .... just reflash the ROM without wiping and then reboot. See if it loads up, it should boot up without having it boot loop.

zephiK said:
Its volume down + power button... not power + vol up/down. Do that then use the volume up/down buttons to go to RECOVERY and then boot into recovery.
I don't see why flashing those two would cause it to bootloop.... maybe bad MD5 hash?
Click to expand...
Click to collapse
By the way, your question of possibly a bad MD5 hash.... lol... I have no idea. I tend to think it's more due to me doing things to my phone that I really have no business doing since I have only the vaguest clue of what I'm doing at any given time.

david251 said:
By the way, your question of possibly a bad MD5 hash.... lol... I have no idea. I tend to think it's more due to me doing things to my phone that I really have no business doing since I have only the vaguest clue of what I'm doing at any given time.
Click to expand...
Click to collapse
Basically, if you're going to be flashing things. Especially when it comes to a flashing a bootloader or radio (baseband) you should verify its MD5 hash.
MD5 hash just verifies that your download was indeed a good download and nothing screwed up. Flashing a bootloader/baseband with the wrong MD5 hash will lead to problems and ultimately possibly to a brick (not to scare you or anything).
Nah what you did was fine, I don't know why would boot loop. But stuff happens, at least you didn't say "omg i bricked my phone??!" like some other people hehe.
For example, http://forum.xda-developers.com/showthread.php?t=2087227 If we look at 0.54 baseband on the website,
MD5 Sum: 0d556693de6c6af086d8d9a74a5dc164
It has that.... you would then use a program such as http://www.softpedia.com/get/System/File-Management/HashTab.shtml
Which when you download the file, right click -> properties -> file hashes -> you can copy paste the md5 hash and it'll have a check (same md5 hash as the one you copy pasted) or X which is NOT the same md5 hash. If its a green check mark... go ahead and flash away, else... redownload it until you get the right md5 hash (use another browser to download if it fails the second time again).
Better safe than sorry, right? especially when flashing bootloader/basebands. Both are very fragile components of the phone. As far as kernels, roms, etc... doesn't mean as much.

In case it helps anyone, I'll say that it has something to do with the kernel I used. Here's why I say that:
After getting back into TWRP, I restored the nandroid I'd made and everything booted very well, back to just the way it was. Since I'm not one to give up so easily, I went back to TWRP and flashed the radio .54, wiped cache/delvik and rebooted the system - the idea here was to try one at a time and see what happened. Phone rebooted normally and everything as before (meaning it showed (in About Phone) the baseband version 54 but still wouldn't connect to wifi without trouble. So - everything was normal. (Just for the record, the only ROM/Kernel I've found that had no problems at all (in terms of my own Nexus 4) was Paranoid Android v.3.56 from 22MAY2013. This one connected pretty well consistently. But then an update to that rom came out and after flashing, it booted fine but I kept getting an error of "Android Process Acore has stopped" and I couldn't do anything at all - which is what led me to the PAC rom.)
Anyway, so after flashing the radio .54 the phone booted and worked normally. Then I went back into TWRP and flashed the Faux123+Shaky kernel, wiped cache/delvik and rebooted system. Now it went back into the same bootloop and stayed there. So... maybe it's just that this kernel isn't compatible with my PAC rom??
So now I've again restored the nandroid. It's a bummer because I love the PAC rom but I have to be able to connect to wifi. And from what I've read, I'm surprised the Franco kernel doesn't help that. It will eventually connect but often takes 30 to 60 minutes to connect and will then often disconnect after the phone sleeps for 10 minutes or so.

From what I have experienced , faux kernel can not be directly flashed over Franco kernel due to something wrong I didn't know with Franco kernel, I did it and went into boot loop then searched and found that you have to flash reset kernel from faux first over Franco then flash faux kernel,
Official notice from faux kernel thread
NOTICE: If you come from Franco Kernel, YOU MUST FLASH RESET KERNEL FIRST otherwise it will result in a boot loop due to NON-STOCK ramdisk used in Franco Kernel!
Hope that helps
Sent from my Nexus 4 using Tapatalk 2

The reset kernel has helped me a couple of times when had bootloops. The 2 I've had wouldn't ever get to the boot animation though, just the Google logo with padlock, then reboot and same again.
This is the reset kernel I've used. I don't know where I got it or who to give credit to, but it works well
back.to.stock_kernel_and_components.zip here http://www.multiupload.nl/BHFJSGU3QD
MD5: f801fc7702e29d85447e9b6fdc880549
SHA-1: a6e60cf80ba29da4eff4c2048934e8627fb682ac

Pretty sure that Franco changed the ramdisk back to the stock ramdisk A LONG time ago and Faux forgot to change the OP post.
Wouldn't hurt to try the 'reset kernel' though but I don't think that is the case.
Source:
r85:
* Add a bunch of patches from CAF to test if the msm_hsic wakelock can get lower.
* Fix the boot.img packing derp that could bootloop the device after flashing another custom kernel on top of franco.Kernel.
* Make the thermal driver poll twice as fast when the device hits the hot threshold as by showp1984 suggestion.
* Disable sched_autogroup because of one Google's engineer answer to my question: https://android-review.googlesource.com/#/c/51323/
* Add a sampling_timer option for the hotplug driver: /sys/module/auto_hotplug/parameters/sampling_timer - it controls how often the hotplug decision is called. The value is in jiffies. For reference 1 second is 100.
* Merge a patch from Linux Kernel that adds a new hashtable (http://en.wikipedia.org/wiki/Hash_table) implementation to be used in the block layer (block layer is the layer that controls the IO on the several block nodes).
Source: http://minooch.com/franciscofranco/Nexus4/4.2.2/appfiles/nightly-changelog
Click to expand...
Click to collapse
(in bold)

zephiK said:
Pretty sure that Franco changed the ramdisk back to the stock ramdisk A LONG time ago and Faux forgot to change the OP post.
Wouldn't hurt to try the 'reset kernel' though but I don't think that is the case.
Source:
(in bold)
Click to expand...
Click to collapse
Wrong Franco still uses a modified ramdisk. What he's talking about is a drep in the packaging of the boot.IMG that caused bootloops
Sent from my Nexus 4

spaceman860 said:
Wrong Franco still uses a modified ramdisk. What he's talking about is a drep in the packaging of the boot.IMG that caused bootloops
Sent from my Nexus 4
Click to expand...
Click to collapse
K no need to be rude about it with saying "wrong" this is XDA a place to learn from each other. Sorry I don't follow every single word that is being said in the Franco thread or any other related kernel thread.
You need to work on your articulation to make yourself not come off as an aggressive person for absolutely no reason.

zephiK said:
K no need to be rude about it with saying "wrong" this is XDA a place to learn from each other. Sorry I don't follow every single word that is being said in the Franco thread or any other related kernel thread.
You need to work on your articulation to make yourself not come off as an aggressive person for absolutely no reason.
Click to expand...
Click to collapse
I wasn't being rude :beer::thumbup:
Sent from my Nexus 4

I appreciate all the input from everyone. As a final update to this thread, what I finally did is flashed the Xenon HD rom and GAPPS with photosphere (as recommended by the developer). Wifi and signal issues are completely resolved and it seems to be an awesome rom for me. I'm stoked and think I'll wait at least a few days before I go in and screw up anything else.

david251 said:
I appreciate all the input from everyone. As a final update to this thread, what I finally did is flashed the Xenon HD rom and GAPPS with photosphere (as recommended by the developer). Wifi and signal issues are completely resolved and it seems to be an awesome rom for me. I'm stoked and think I'll wait at least a few days before I go in and screw up anything else.
Click to expand...
Click to collapse
PSST, if you're scared you might screw up, make a NANDROID when your phone is still fine. If you get into a bootloop, just restore the NANDROID. It does take quite a lot of space though, so keep that in mind.

ADB worked while bootlooping...

I had flashed CM10 but forgot to reboot into fastboot and boot the CM10 kernel. As the thing was bootlooping, I was able to successfully do an adb reboot recovery, completely skipping using a USB keyboard and pressing Ctrl - Print Screen - I key combination normally used to get to recovery. Apparently at some point, even if the rom isn't booting, the kernel somehow starts adb. Anybody else have any luck with this or know any reason why this even worked? If this is the normal way for android to boot, maybe it would be possible to still get into recovery even if we flash a different kernel.

hecksagon said:
I had flashed CM10 but forgot to reboot into fastboot and boot the CM10 kernel. As the thing was bootlooping, I was able to successfully do an adb reboot recovery, completely skipping using a USB keyboard and pressing Ctrl - Print Screen - I key combination normally used to get to recovery. Apparently at some point, even if the rom isn't booting, the kernel somehow starts adb. Anybody else have any luck with this or know any reason why this even worked? If this is the normal way for android to boot, maybe it would be possible to still get into recovery even if we flash a different kernel.
Click to expand...
Click to collapse
Interesting I wonder if its repeatable? I guess its will be hard to test unless you already messed up, nobodys gonna mess up on purpose just to try this out without a hardware recovery option but maybe someone who messes up on accident will report back here on what they found out.

Wasn't able to repeat it on the Ouya kernel with CM ROM installed but it seems to work all the time if you get a boot loop in CM10 kernel and CM ROM. I'm still not feeling safe enough to actually flash the CM kernel, so I am still using fast boot to boot the kernel from a laptop.
On a side note, I do have xbmc set up as my launcher and have list of working skins that can launch android apps from. Once I figure out how to get the crazy CPU usage I am getting worked out I plan to make a guide for a full media center.

[Q] Rooting Nexus10 - Is losing recovery all the time normal?

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.

Encryption Issues/TWRP/password

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