Database Users

[Q] MyTouch 4g: Multiple problems... PLEASE help.

Okay, I've searched and searched and no one seems to have the specific problem that I'm having with my phone, so I'm taking to the forums myself. I've been rooting since the G1, I know how to adb push things, I have used google and multiple forums to try to fix this problem. So here goes, anyone that can help I thank you in advance.
1-My phone, like some other MT4G users, reboots itself each time it's plugged in. Initially I thought this was because I was using a Kindle cord to plug it into the pc, so I bought an MT4G usb cable from tmobile, and still it boot loops (just the first white screen for maybe 4 seconds, then black then again and again). The only way to charge it is to let it start boot looping, take the battery out, turn it on, and if I'm lucky enough that it begins to boot up correctly I plug it in mid boot. If I wait til it's fulled loaded it just starts rebooting again.
2-It will not at all from any angle go into Recovery mode. If I try to go to recovery from Rom Manager, or from the screen you get when holding power and lower volume key or by flashing a rom through Rom Manager, it just boot loops just like mentioned above, until I pull the battery for a while (it is currently sitting next to me with the battery out) and then put it back in.
3-If by chance it's on, and plugged into the computer, it is not at all recognized. Ever. While it's booting up my computer finds something, but doesn't know what it is, and doesn't allow me to view any folders on the SD card. Yes I've installed the HTC drivers file. I've adb'ed things to this phone before, now it says device not found. I don't know when it stopped being recognized...
4-I've even tried to fastboot something over to it, but to no avail, still not found.
If I try to do a factory reset, it boot loops. If I sneeze it boot loops.... I don't know what to do, and if I trade it in under warranty, I have to reset it to stock rom, or they're going to charge me for a new phone. Any ideas!?
I have Cyanogen mod 7 on here.

have you tried a fastboot wipe? or have you tried to reboot to recovery from adb?

First, I don't trust using the actual ROM Manager app to do the flashing/installing.
Since you've been flashing since the G1 days why not use Clockwork Recovery? Just go into recovery and do the necessary wipes.
So I suggest to do a complete full wipe in Clockwork, meaning wipe data, cache, and dalvik cache. Install the newest CM nightly (Which is working wonderfully BTW) and see if your problems still persists.
Edit: I didn't realize you tried to enter recovery, oops. But yeah try what the buy above me said. Try re-installing the latest CWM recovery, if that still fails then try heading into there via ADB.

mackster248 said:
First, I don't trust using the actual ROM Manager app to do the flashing/installing.
Since you've been flashing since the G1 days why not use Clockwork Recovery? Just go into recovery and do the necessary wipes.
So I suggest to do a complete full wipe in Clockwork, meaning wipe data, cache, and dalvik cache. Install the newest CM nightly (Which is working wonderfully BTW) and see if your problems still persists.
Click to expand...
Click to collapse
I second that, flashing ROMs from ROM Manager a terrible idea.

Well...if all else fails and if you are really thinking about returning it and still under warranty...few seconds in the microwave method should work just fine. They wont be able to see that its rooted if the phone wouldn't turn on, would they???

glimmer of hope...
So by the grace of god I did get it flashed back to unrooted, stock 2.2 by putting it as pd15img.zip on my sd card and going into bootloader. Once that was done I thought I would be out of the woods... I even plugged it in last night and no boot loop!! but this morning I unpllugged it (and I'm using a tmobile cable for the phone attached to my pc) and here it sits, next to me again with the battery out of it because everytime I try to turn it on (for over 40 minutes now) it boot loops to that stupid white screen (that is honestly driving me insane at this point). I know that it isn't rooted (because I dl'ed rom manager and it won't let me do anything without being rooted) so do we think that I'm safe to go to the store today to request a new one be sent? Thoughts? And thanks for the help thus far!

yeah I would send that back

Bad emmc chip? I'm sorry man, that's a terrible story.
Sent from my HTC Glacier using XDA App

Lost Boot/Recovery Img

Strange happenings going on with my Nexus S.
It has been rooted for a while and have been running Genexus S 2.0 ROM which was fine to start with but I have recently been getting lag issues with the screen, issues with character selection on the keyboard etc.
However, I have had a few crashes when the phone has been charging and the phone is being not just hot, I'm talking boiling to the touch!
I have rebooted into recovery but....recovery img and boot img have disappeared. They have been present in recent weeks but for some reason they have disappeared.
I have reinstalled clockworkrecovery via ROM Manager a couple of times but there is still no change. TBH I'm sick of the issues I've had with the phone since rooted and it's not for me so plan on going back to stock whenever I can, however, I need recovery!
Can anyone point me in the right direction to sort this out and if possible not by plugging my phone into a PC. I am away with work and don't have my own computer for a while.
Thanks

you can always flash the boot recovery back into the phone, just follow any of the how to root guides

meso100 said:
Strange happenings going on with my Nexus S.
It has been rooted for a while and have been running Genexus S 2.0 ROM which was fine to start with but I have recently been getting lag issues with the screen, issues with character selection on the keyboard etc.
However, I have had a few crashes when the phone has been charging and the phone is being not just hot, I'm talking boiling to the touch!
I have rebooted into recovery but....recovery img and boot img have disappeared. They have been present in recent weeks but for some reason they have disappeared.
I have reinstalled clockworkrecovery via ROM Manager a couple of times but there is still no change. TBH I'm sick of the issues I've had with the phone since rooted and it's not for me so plan on going back to stock whenever I can, however, I need recovery!
Can anyone point me in the right direction to sort this out and if possible not by plugging my phone into a PC. I am away with work and don't have my own computer for a while.
Thanks
Click to expand...
Click to collapse
its because you installed your recovery via rom manager. you want to reflash your clockwork recovery through fastboot so that it will stay permanently. look in the development section for instructions.
---------- Post added at 05:30 PM ---------- Previous post was at 05:29 PM ----------
AllGamer said:
you can always flash the boot recovery back into the phone, just follow any of the how to root guides
Click to expand...
Click to collapse
i got to say that youre the only xda mod, that i know of, that also helps out people with issues and not just xda/site stuff. thank you!

Thanks for your help guys.
I flashed the cwm recovery via fastboot and loaded up cm7 but each new ROM I used (that had been there previously) didn't boot into a fresh version, it had elements of the previous versions I had run such as MIUI (the clock), the Genexus S 2.0 drag and drop lock and wallpaper and some elements from The Infinity ROM. Very strange.
Prior to the latest mix up the phone had become very unstable, especially the touch screen and I am not exaggerating when I say the phone just wasn't usable. I even considered getting a BlackBerry Torch 9810!!! I mean wtf?!
Anyway, I have reflashed a stock nandroid backup via CMW and relocked the bootloader. I had a few permission errors but when I rebooted that seemed to go away. I'm now quite happy I'm back to standard because of the reliability issues I experienced.
When I reboot to recovery it comes up with a White box with an arrow coming out with the android at the side of it. Is this normal or should there be a standard recovery img? However, I have noticed if I press the volume up and power again it goes to a purple recovery screen with wipe cache partition, factory reset etc.
Also, all my ROMS and Titanium Backup files are still viewable from recovery, is that usual? Would I be ok to mount as USB and delete those individual files?
Thanks

When you switch roms you MUST wipe data factory reset, wipe cache, wipe dalvic cache. Then flash the new rom.
Sent from my Nexus S 4G using xda premium

I survived the Encryption Unsuccessful error unscathed?!

I've been a stalker on here for a long time, as I've been interested in custom ROMs but I never pulled the trigger, until last night. My Vibrant has served me well for a many years, I bought it shortly after they came out. All I'd ever done to it was network unlock it so I could keep using it after I moved to the UK.
I've been toying with getting a new phone for a few months now so I decided why not try and flash a custom ROM and get ICS on my Vibrant, if I got the EU error and bricked it, oh well, I'd get a new phone. So I after much reading and research, studying the tutorials on here I went for it. I am vary tech and computer savvy. I build my own computers from scratch, I've flashed my routers and set up networks so I was pretty confident I could do this with the help of the forums here.
I've read every thread I can find on the EU on here and I know that the community needs as much info as possible to try and solve this bug, so I will try and be as specific as possible and list everything I did. But bear in mind, I'm new to this and this was my first time doing much of this so some things may be muddled as I was up til quite late messing with all this.
To start my phone was running 2.2 which was updated using Kies Mini. The only thing I'd ever done to it was network unlock, and for that all I did was find the file on the phone with the code and then enter it to unlock.
I decided to follow Woodrube's guide (http://forum.xda-developers.com/showthread.php?t=1464423)
I followed the guide to the "T".
1. Used Odin to flash back to stock 2.1, worked fine, phone booted back up and everything worked. Phone Data showed I was on 2.1.
2. I put Clockwork Recovery downloaded from Woodrube's sig block on my internal sdcard labeled as Update.zip
3. Created a folder called ICS on my internal sdcard. Found and downloaded CM7 from the forums here and dropped it into the ICS folder. Found and downloaded the ICS Passion ROM from the forums and dropped it into the ICS folder
4. Booted to recovery mode and did Reinstall Packages. It ran but brought me back to the blue recovery screen. so per Woodrube's guide I did it again and the second time it brought me to the green CWR recovery screen
5. I did wipe data/ factory reset
6. I did wipe cache
7. I went to advanced and did wipe dalvik cache
8. I went to mounts and storage and did format system
9. I went to install from sdcard and found the ICS folder I made and ran the CM7 fille I dropped there. It worked the first time and booted right up, I let it sit for about 5 mins waiting for the request to install my google password as Woodrube mentions, but it never appeared, so I moved on after 5-6 min of waiting.
10. I then booted back into recovery mode using the extended power button menu
11. I went to install from sdcard again and this time ran the ICS Passion file. It ran some text lines showed on the screen as id did somethings and then I sw a Random Offset error and a small hex string but then it said successfully installed but didn't leave the recovery screen. So i scrolled up to reboot system.
12. The phone rebooted, showed me the Passion splash screens and a progress bar which filled and completed, then showed a few other splash screens and then it booted up showing my signal strength bar and notifications bar. I thought YES! I did it and it worked. then the screen flashed, it showed a single multi-colored line horizontally across the middle of the screen and then flashed again and I was looking at the Encryption Unsuccessful screen.
13. I DID NOT PUSH THE RESET BUTTON, I set the phone aside and followed Woodrube's link to the Captivate Forums and read up on the error, read all of it, then searched the forums for more threads on the error and read all of those, then I Googled the error and read everything else I could find.
14. First i tried just shutting the phone down with the power button and then restarting it. I did this about 5-6 times. Every time it rebooted it showed me the Passion splash screens then boots up shows my notification bar and signal strength meter and the EU screen. That didn't work. I next tried rebooting 5 times without my external sd card installed. Same results
15. Next I decided to see if I had lost access to my internal sdcard as I had read about. I wasn't sure if I had because I had never pushed the EU screen reset button. So I booted into recovery mode, went to install from sdcard and my sdcard list popped up. I still had access to my internal sdcard.
At this point I was torn... do I stop playing with fire and just got back to stock, update with Kies Mini and go back to using the phone as I had always been and forget all this or do I try and figure this out? Well my stubborn side hating to be stumped had encountered a problem and so wanted to move forward... on i went.
16. I decided, ok, I can still see my internal sdcard so why not try reflashing the ISC Passion and see if maybe it will take this time with no EU. I ran it and exactly the same thing happened as the first time.. right down to the flash with the horizontal line and all. (I did not wipe data, cache or anything, just reflashed. Not sure if I should have or not)
17. Back to recovery mode and check... yes still see my internal sdcard. hmmm
18. Decide ok, how about it I do Woodrube's guide all over again from the start? Maybe that will work. I followed the guide again using all the same files and wound up right back at the EU screen again.
19. Hmmm, how about a different ICS ROM? Went and found ICZen and downloaded it. Hmm, how do I get this unto my internal sdcard if the phone won't boot all the way? Booted it back to the EU screen and just plugged the phone into the usb on my computer, windows recognized it, made the device plugged in noise, and both my internal and external sdcards on the phone showed up as drives. Navigated to the ICS folder in the internal sdcard and dropped the ICZen file into it.
20. Rebooted the phone into recovery mode using the power button menu
21. Used install from sdcard and flashed the ICZen. (Again, I didn't wipe anything before hand. Again not sure if I was supposed to)
22. The ROM installed and got stuck in a boot loop. I pulled the battery and rebooted to recovery and reflashed the ICZen again with no wipes. This time it worked and the phone rebooted and I got the ICZen splash screens, then the notification bar and signal strength meter showed up.. and AGAIN the weird flash with the horizontal bar and then the EU screen. SIGH
23. Booted back to recovery mode and checked if I still had access to internal sdcard. yes it was still there.
24. Shut down and booted to download mode and ran Odin and flashed back to stock 2.1
This is where I am now, It was too late to try anything else and my wife was glaring at me to go to bed so shut off the phone and went to bed.
I tried to put everything I did down with as much detail as I could. I'm sure some of you pros out there might be wincing at stuff I did, but again this is all new stuff for me and I'm slowly learning.
If you have any questions or need clarification just ask and I will try and help/explain better.
Hopefully this might help in the quest to solve this bug or it may just be a waste of time to read, dunno.

I got to:
"To start my phone was running 2.2 which was updated using Kies Mini."
and stopped there
Come back to Froyo - always welcome here

Moped_Ryder said:
I got to:
"To start my phone was running 2.2 which was updated using Kies Mini."
and stopped there
Come back to Froyo - always welcome here
Click to expand...
Click to collapse
LOL, yea I know, but up until this adventure last night, I just used the phone with the Samsung updates as it was, didn't really have a need to do otherwise.

I think that you should flash one of Moped's ROMs and make sure that it will boot up and run ok and that you did, in fact get out of the EU bug safely.
Couple of things:
I did get your PM and I thank you for the info. This post is far more detailed, which is a ton better.
You say that you were unlocked. There was a theory not too long ago about a corrupted EFS file, but AdamOutler uploaded his and someone else replaced theirs with it and it didn't work. But I am thinking that there might be a link here bc I have seen several posts over the last few months that ICS ROMs have been out where someone's data has been borked or their IMIE was gone. Wonder if there is a correlation to that? I'll have to ask some people onver in the Captivate thread and if anyone in the Vibrant thread can chime in too(?).
If you want to flash another ROM, just follw my ICS guide but where it says to install CM7, just install your shiny, new 2.2 instead and there you are.
Great Job dodging that bullet and hope that you no longer lurk, but be a part of the community at large. If your intelligence is reflected in your post, you are welcome here anytime.

Thanks Woodrube,
I was thinking the same thing about loading a 2.2 ROM and be sure I'm all good.
I know the 2.1 I loaded last thing last night seemed to work fine. But I will try a 2.2 once I get home and will update on here after I do.
Funny thing about all this is that my wife now won't let me near her Captivate ROFL.

Can you blame her ?
For the sake of the thread i can chime in on the unlock part. I'm still untouched by the EU bug "touching wood(rube)" . I'm using the i896 version of the Captivate from Rogers and there was never codes inside of it so most app were unsuccesfull at pulling them. I had to use the free SGS Unlock website where you upload your nv_data.bin and it returns you a unlocked version. I also never encountered any efs/imei issue.

hi.
I saw you have not wiped when installing the ROMs. I think maybe you should try and do the wipe before installing the ICS ROM.
Wipe system, data, cache.
Good luck

romitkin said:
hi.
I saw you have not wiped when installing the ROMs. I think maybe you should try and do the wipe before installing the ICS ROM.
Wipe system, data, cache.
Good luck
Click to expand...
Click to collapse
BINGO!
So I followed Woodrube's guide again.. started from scratch... only change I made was I wiped data factory reset, wiped cache, wiped Dalvik cache, and under mounts and storage I format system BEFORE flashing the ICS Passion.
Logged into Google Account and set up phone and now I'm rockin' ICS
Not sure how or why this worked but it did.
Thoughts?

Stuck in bootloop after N7 reset on it's own

My N7 is rooted and stock... I used the N7 Toolkit method... My N7 is 32gb non-3G version...
It's been working fine, no problems. I thought that it was a little laggy since I installed a 2nd account on it ... so a day ago I deleted the 2nd account hoping to get rid of the lagginess that started after installing the 2nd account.
Today I came home with the N7 and I heard some notifications when it logged into my Wifi... And about 30 mins later I went to use it and the wall paper that is usually showing went black, the screen did some funny things and the tablet reset.
Now it's stuck in a boot loop...
I can get into the bootloader and recovery, but whenever I exit, it goes back into the boot loop.
Since I hadn't installed anything custom when rooting, do I even have Nandroid? Can I back it up and connect to USB before wiping?
Does wiping erase the SD portion of the memory?
Any ideas for troubleshooting? Would love to know what happened here...
Thanks...

What did you come up with by searching the forums or Google?

Hemidroids said:
What did you come up with by searching the forums or Google?
Click to expand...
Click to collapse
As with many things, the info that I found is conflicting. Since I had been burned by trying things before verifying what I was doing, for once, I decided to reach out for advice BEFORE I erased something that isn't recoverable.
Yes, I know that many on XDA hate users who ask for help before researching on their own. The problem for me is that I couldn't find a clear answer.
Since I made my post, I tried a few things...
Details and questions are here: http://forum.xda-developers.com/showthread.php?t=2089144
Thanks for your response, although I get the feeling that you had expected me to know the answer to my question...

OldDogEyes said:
My N7 is rooted and stock... I used the N7 Toolkit method... My N7 is 32gb non-3G version...
It's been working fine, no problems. I thought that it was a little laggy since I installed a 2nd account on it ... so a day ago I deleted the 2nd account hoping to get rid of the lagginess that started after installing the 2nd account.
Today I came home with the N7 and I heard some notifications when it logged into my Wifi... And about 30 mins later I went to use it and the wall paper that is usually showing went black, the screen did some funny things and the tablet reset.
Now it's stuck in a boot loop...
I can get into the bootloader and recovery, but whenever I exit, it goes back into the boot loop.
Since I hadn't installed anything custom when rooting, do I even have Nandroid? Can I back it up and connect to USB before wiping?
Does wiping erase the SD portion of the memory?
Any ideas for troubleshooting? Would love to know what happened here...
Thanks...
Click to expand...
Click to collapse
First if you have a custom recovery, boot into that, wipe cache, then dalvik, and try rebooting. See if that works.
Nandroid would be the backup of your entire ROM that you made either using ROM Manager or manually initiating a backup in recovery.
Wiping using ClockworkMod Recovery or TWRP Recovery will leave the /sdcard area (/data/media) alone, however it'll remove your ROM. At that point, you'll need to re-flash a custom ROM to your device. If you reload the stock N7 images from Google, it WILL erase your /sdcard section!
You can push files to your device while in recovery using the adb push command. You can also pull files from your device using the adb pull command.
adb push <name of file> <location on device you want to push to>
EXAMPLE: adb push ROM.zip /sdcard/
adb pull <location of file on device>
EXAMPLE: adb pull /sdcard/ROM.zip
Research adb, adb push, adb pull commands.

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