Related
Hi:
Really need some assistance here.
I am currently trying to install CM 7.0 RC1. From my ROM manager I selected the CM MOD and it went to reboot and install. Now it is just stuck on a screen with a little green Android Logo and Exclamation.
What can I do here? I am afraid to pull the battery but it doesn't seem to be moving past this point.
Do you have a custom recovery like Amon_RA or ClockWorkMod installed?
cyrus_mc said:
Hi:
Really need some assistance here.
I am currently trying to install CM 7.0 RC1. From my ROM manager I selected the CM MOD and it went to reboot and install. Now it is just stuck on a screen with a little green Android Logo and Exclamation.
What can I do here? I am afraid to pull the battery but it doesn't seem to be moving past this point.
Click to expand...
Click to collapse
You'll be fine pulling the battery since you're only flashing a ROM... it's a NO NO when flashing Radio though. That being said... the CORRECT way to restart when you're in a bootloop or stuck on that particular screen is to use the three finger salute and reboot by holding down the power button, volume down button, and pressing the trackball. From there, I'd immediately hold down the volume down button, which will force the phone into the bootloader and you can enter Recovery from there. Do a FULL wipe of data and cache, as well as dalvik-cache from the Advanced menu, then flash the ROM.
uansari1 said:
You'll be fine pulling the battery since you're only flashing a ROM... it's a NO NO when flashing Radio though. That being said... the CORRECT way to restart when you're in a bootloop or stuck on that particular screen is to use the three finger salute and reboot by holding down the power button, volume down button, and pressing the trackball. From there, I'd immediately hold down the volume down button, which will force the phone into the bootloader and you can enter Recovery from there. Do a FULL wipe of data and cache, as well as dalvik-cache from the Advanced menu, then flash the ROM.
Click to expand...
Click to collapse
Yup this is what to do. Quick bit of info; You can get to the boot loader by simply holding the volume button down and pressing the power button, just a little easier to do
That's what I had to do. Mine also got stuck.
Sent from my Nexus One using XDA App
Hollow.Droid said:
Yup this is what to do. Quick bit of info; You can get to the boot loader by simply holding the volume button down and pressing the power button, just a little easier to do
Click to expand...
Click to collapse
Agreed. I was just referring to what to do if you're stuck on the X or in a boot loop. ;-)
Sent from my Nexus One using Tapatalk
You're stuck with stock recovery. Reboot back to ROM, install recovery, only then reboot to install ROM.
Hey guys I'm having a similar problem, however my phone gets stuck on the initial nexus screen. I've been working on the phone problem for the better half of the day and this is what i've done, what works, and what doesn't.
WHAT I'VE DONE:
Full wipe, including Devik
Played around with installing different radios.
Download CM7-RC1 from CWM and the computer
WHAT WORKS:
MIUI Roms
Stock Gingerbread Rom
MY Back-up, which has CM7 Nightlie #45
WHAT DOESN'T:
All Cyanogen Mods
I even tried the CM6.0
So I'm a little stump on how to get my phone to run the latest Cyanogen or matter of fact, any CM Roms. Maybe my phone wants something different in her life
Any help will be great guys...thx
How much time did you wait?
Did you try erasing /system?
Well I just waited for 5 hours leaving it on the initial Nexus screen, in hopes it might do something, but it was to no success.
/system? not quite sure where that is... I am assuming it's in the roots... I can only do what I can from the recovery.
Try to install LeoGingerbread, for example. Does it work?
If yes - right after it installs, try to flash CM7.
cyrus_mc said:
Hi:
Really need some assistance here.
I am currently trying to install CM 7.0 RC1. From my ROM manager I selected the CM MOD and it went to reboot and install. Now it is just stuck on a screen with a little green Android Logo and Exclamation.
What can I do here? I am afraid to pull the battery but it doesn't seem to be moving past this point.
Click to expand...
Click to collapse
Whenever you see "little green Android Logo and Exclamation", you can press volume up and power button together to get into the bootloader menu and reboot your N1. It seems like your custom recovery did not work. Try to flash Clockworkmod recovery 2.5.1.4 (not 3.0.0.5) or RA recovery again. It may help.
Jack_R1 said:
Try to install LeoGingerbread, for example. Does it work?
If yes - right after it installs, try to flash CM7.
Click to expand...
Click to collapse
Wow that actually worked, thanks... can you explain why this is needs to be done to get it to work?
LeoGingerbread executes "format /system", that actually works and cleans the remains of the old OSes. Some other ROMs do, too.
armyshawkeye said:
Wow that actually worked, thanks... can you explain why this is needs to be done to get it to work?
Click to expand...
Click to collapse
Because you still have the stock recovery installed, that is how you access the menu for it.
Here's a flashable script that does the same thing. It was put together by temasek - I'm just sharing...
http://db.tt/wdeoIMI
Sent from my Nexus One using XDA App
danger-rat said:
Here's a flashable script that does the same thing. It was put together by temasek - I'm just sharing...
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
How I flash this? As a update.zip?
Yes. I believe it executes "FORMAT SYSTEM:" command, maybe more than once.
Yes, it formats system, boot, data, and cache, each twice...
It's quicker than flashing a full ROM to achieve the same results...
Sent from my Nexus One using XDA App
danger-rat said:
Yes, it formats system, boot, data, and cache, each twice...
It's quicker than flashing a full ROM to achieve the same results...
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
CW Recovery has options to format system, and other partitions, under Mounts and Storage.
Sent from my Nexus One using Tapatalk
Hello everyone,
Well I'm a novice to the whole rooting and flashing scene. I had an X2 with cm10 on it, but it was dropped too many times and sadly passed on to the beyond. I decided to get myself a nice razr m.
I've had my phone for a few weeks now. I did the safestrap thing and tried out energy for a while. I liked it a lot, ran fast with good batery llife and all that, but the theme wasn't exactly my thing. Next I tried out flying jelly. It was great and I used it in RomSlot1 for a good few days, eventually swapping it into the stock slot. Everything was great and fine until after having been up for work for 28 hrs, I read about some glorious app called razr m toolbox. I got it and swiftly went through the warnings with no regard for my phone's safety.
In the end I had a nice looking screen(sarcasm) with no softkeys or nav bar. I tried to delete and reflash, but that put me to a place where it would boot to the safestrap splashscreen but the continue and recovery keys wouldnt work. This baffled me until I came and saw that it's sort of a common(known at least) issue. Holding down the vol and power keys didnt work, but four seconds after letting them go it would boot into the SS spllash again. I eventually found that if I started holdingdown the three keys AT the SS splash, than I could go into fastoot.
I RSD'd and it went through that whole process, and now I'm sitting at the stock M boot animation. There's a yellow light with red light spikes coming from it with some lightning going around it. Quite a storm. The issue is that it's been stuck at this animation for a solid ten minutes now.
Should I wait? should I try to reset it and start anew?
Let it sit for a while longer, it takes a while after restoring to stock. If it doesn't work, use Matt's utility. IMO, it's the easiest method to fastboot a M.
http://www.droidrzr.com/index.php/topic/13427-droid-razr-m-utility-110-windowsmaclinux/
Always factory reset after rsd to stock. This is most likely why you are bootloooping
Sent from my XT907 using Xparent BlueTapatalk 2
yes , I agree with upstares, after flashing the stock rom with RSD, it's alwayse reconmend to wipe data/factory reset ,try it if you can go in the recovery pressing the vol up button and power at the same time.
Make sure you go to stock recovery and clear cache as well as factory reset. I had the same issue and it worked for me!
sy0120 said:
Make sure you go to stock recovery and clear cache as well as factory reset. I had the same issue and it worked for me!
Click to expand...
Click to collapse
always clear cache when flashing anything
Sent from my XT907 using Tapatalk 2
I'm a bit of a newbie with rooting and flashing but have been pretty successful up until now. I installed TWRP 2.3.6.2 and CM 10.2 on my Verizon LG G2 about a month ago.
Since then I've been updating with nightlies with much success.
When the 11.0 build showed up in the CM updates list I downloaded it and installed. It failed and I had to flash an older 10.2 nightly. My device became pretty unstable after this. Most GApps were gone or somehow corrupted. I re-installed a number of them but Google Play still didn't work.
I tried updating again to an 11.0 nightly today and again it failed. I then flashed a recent 10.2 nightly that had worked for me and now my phone is stuck an infinite spinning Cyanogenmod boot screen.
I have tried every combination of holding power and volume down to try to get into TWRP to try flashing another nightly but my device just continues to reboot to LG then Cyanogenmod spinner over and over.
I decided maybe I needed to reinstall TWRP (looks like there's a new version from today). I tried to access my device with it plugged into my computer using fastboot and adb push loki_flash and it returned "device not found."
I'm totally stuck now... no idea what to do next. Would be so grateful for some guidance on how to get my device functional again.
Thanks.
One additional comment: I've tried doing Power + Volume Down during LG logo but it doesn't do anything.
I managed to get into a Hardware Key Control Mode screen by holding Power + Volume Up + Volume Down which had some options about answering calls or turning off alarm using hardware keys.
Cannot seem to do anything to get to TWRP.
To get to TWRP:
* Hold Power until the phone shuts off
* Hold Power+Volume Down until the LG logo appears
* Release Power+Volume Down then immediately hold them both down again
You'll get a message to the effect of 'Press Power to permanently erase all user settings.' Do that (if you have a custom recovery installed, it'll just boot into that).
Also keep in mind that the first install of a custom rom like CM will sit on that logo screen for a couple of minutes.
I somehow just managed to get to a screen that says "Factory hard reset. Permanently Erase User Data & Reset Settings? Press Power key to confirm, and any other key to cancel." It says "Rooted" in the upper left corner.
The screen doesn't respond to Volume Up or Volume Down and I just let it sit there for a few minutes. It reverted back to the infinite CM spinner.
At this point I'm pretty much at a loss for what to do -- and afraid to do anything to mess things up even more.
Should I be trying to go back to stock? http://forum.xda-developers.com/showthread.php?t=2432476
antinorm said:
To get to TWRP:
* Hold Power until the phone shuts off
* Hold Power+Volume Down until the LG logo appears
* Release Power+Volume Down then immediately hold them both down again
You'll get a message to the effect of 'Press Power to permanently erase all user settings.' Do that (if you have a custom recovery installed, it'll just boot into that).
Also keep in mind that the first install of a custom rom like CM will sit on that logo screen for a couple of minutes.
Click to expand...
Click to collapse
Thanks for this suggestion -- I'll try to get back to that screen and do this. Also the CM spinner was stuck for 8 hours last night... so definitely not a function of bit of a delay for first install of a custom ROM.
tophy0 said:
I somehow just managed to get to a screen that says "Factory hard reset. Permanently Erase User Data & Reset Settings? Press Power key to confirm, and any other key to cancel." It says "Rooted" in the upper left corner.
The screen doesn't respond to Volume Up or Volume Down and I just let it sit there for a few minutes. It reverted back to the infinite CM spinner.
At this point I'm pretty much at a loss for what to do -- and afraid to do anything to mess things up even more.
Should I be trying to go back to stock? http://forum.xda-developers.com/showthread.php?t=2432476
Click to expand...
Click to collapse
This screen is what you want to see. Push Power a couple of times. It won't erase your settings. It'll boot into TWRP.
tophy0 said:
Thanks for this suggestion -- I'll try to get back to that screen and do this. Also the CM spinner was stuck for 8 hours last night... so definitely not a function of bit of a delay for first install of a custom ROM.
Click to expand...
Click to collapse
Phew, that worked! Back into TWRP.
Any additional guidance on what I should be doing to try to get back into a stable version of CM? I have many builds of CM 10.2 in internal storage that I could pick from. But before I try another one of those should I attempt to clean things up at all? Seems like my current configuration must have some sort of conflict that's leading to all the instability. I do have Titanium Pro installed so I believe I should be able to get my apps + data back as long as I don't completely clean out everything.
Thanks again for the help.
Also mods: just realized that I should have posted this thread in Q&A not General. Sorry about that! I don't think I can move it over myself or I would.
I think what I would like to do now is update TWRP to 2.6.3.3 and then install 11.0 using this build: http://www.droidforums.net/forum/lg-g2-development/258385-rom-wip-cyanogenmod-11-g2-vzw.html
Not sure how to update TWRP from 2.6.3.2 to 2.6.3.3 though. When I originally set up TWRP I used adb / loki-push but it's a bit of a blur how that worked since I was just following step 1-2-3 instructions.
Sorry for being such a noob with this stuff. Any additional guidance would be awesome.
As I suspected, flashing any CM ROM now leads to an infinite CM spinner so I think I need a plan B to get my device working again. At least I can now get to TWRP thanks to the help above.
Not sure where to go from here.
Did you try to wipe data, cache, dalvik cache and system? Then install cm. I think this is why you got a bootloop :/
Sent from my GOOPHONE i5C using XDA Premium 4 mobile app
Makrilli said:
Did you try to wipe data, cache, dalvik cache and system? Then install cm. I think this is why you got a bootloop :/
Sent from my GOOPHONE i5C using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yup, when I finally got into TWRP I did this and was able to install a version of CM 10.2 that actually loaded.
All my apps and settings are obviously gone now so it's a good time to make the leap to TWRP 2.6.3.3 and CM 11.0. Trying to figure out how to do that now (in the proper forum!):
http://forum.xda-developers.com/showthread.php?t=2563982
Thanks for the help.
tophy0 said:
Yup, when I finally got into TWRP I did this and was able to install a version of CM 10.2 that actually loaded.
All my apps and settings are obviously gone now so it's a good time to make the leap to TWRP 2.6.3.3 and CM 11.0. Trying to figure out how to do that now (in the proper forum!):
http://forum.xda-developers.com/showthread.php?t=2563982
Thanks for the help.
Click to expand...
Click to collapse
I htink the wipe would have helped from the beg. Any time you jump roms I suggest doing a wipe. Also one thing you may want to look at is a backup of all your settings and everything, I use titanium and it has helped me out in situations like this in the past.
madisonjar said:
I htink the wipe would have helped from the beg. Any time you jump roms I suggest doing a wipe. Also one thing you may want to look at is a backup of all your settings and everything, I use titanium and it has helped me out in situations like this in the past.
Click to expand...
Click to collapse
Thanks, makes a ton of sense.
I also use Titanium to backup. When I do a fresh install of TWRP and CM 11.0 can I restore my system data in addition to apps + app data? I'm not sure to what restoring extent system data could create conflicts with the CM 11.0 build. For example will all the Google Mobile Services system data from my CM 10.2 build create conflicts?
What I really want is to easily bring back ~150 apps + all of my SMS messages, Contacts, Email settings, Homescreen layout and settings, etc. Not exactly sure what's achievable.
tophy0 said:
What I really want is to easily bring back ~150 apps + all of my SMS messages, Contacts, Email settings, Homescreen layout and settings, etc. Not exactly sure what's achievable.
Click to expand...
Click to collapse
You can safely use TB to restore user apps, their data and trebutchets data if you use that. Backing up sms and contacts with TB, I'm not sure about that as I used other app "super sms backup". And about emails I have no idea. Also it's not a good idea to restore settings, better to set them again
Sent from my GOOPHONE i5C using XDA Premium 4 mobile app
antinorm said:
To get to TWRP:
* Hold Power until the phone shuts off
* Hold Power+Volume Down until the LG logo appears
* Release Power+Volume Down then immediately hold them both down again
You'll get a message to the effect of 'Press Power to permanently erase all user settings.' Do that (if you have a custom recovery installed, it'll just boot into that).
Also keep in mind that the first install of a custom rom like CM will sit on that logo screen for a couple of minutes.
Click to expand...
Click to collapse
I owe you man! Saw the erase data screen and almost freaked out. Pressed power and it booted to TWRP.
Thanks again!
Mike
WCM3 said:
I owe you man! Saw the erase data screen and almost freaked out. Pressed power and it booted to TWRP.
Thanks again!
Mike
Click to expand...
Click to collapse
You know, I was wondering as well of how to get to TWRP if a rom didn't boot. I got to that screen too and thought it would erase the phone. This is good to know and should be a sticky somewhere.
Ok, I went in today to reload MOAR ROM on my phone. I had initially thought to check if maybe there was a higher compatible firmware version than BOC4, so I posted to the thread, but then I figured everything was working fine on my phone so why bother.
I loaded NI2 and booted up into safestrap recovery.
Once in safestrap, I tapped wipe, but strangely, it was like the touch screen registered 2 rapid taps, and before I know it the phone is formatting. Me, I try to do a data wipe after this, silly me, and it doesn't work. It no longer seems to detect distinct partitions, probably cuz the entire internal drive just got formatted.
Anyways, I proceed to install MOAR, and then the BOC4 firmware. Now the phone starts to boot, gets to Samsung screen, hangs there for a few seconds, then reboots. It's caught in a boot loop. I am guessing that safestrap might have been removed, and I am looking advice as to how I might go about reloading it, if that is indeed my problem.
Or really, any pertinent advice on how I might make my phone function again would be greatly appreciated!
Worth noting, I am able to boot into Recovery, which I am pretty certain means that my phone is not bricked. Just not sure what to do from here. Thanks!
hmm.. I just tried factory reset in recovery, and now it maybe appears to be booting for first time. I have that spinning tornado boot animation that came with MOAR. Should maybe come up in 10-15 min, fingers crossed...
musiclover7 said:
hmm.. I just tried factory reset in recovery, and now it maybe appears to be booting for first time. I have that spinning tornado boot animation that came with MOAR. Should maybe come up in 10-15 min, fingers crossed...
Click to expand...
Click to collapse
Did it work? If you formatted, assuming you are not on the latest bootloader, you'll need to flash the NCG restore tar and start the root process from the beginning.
Also, I'd suggest upgrading to @jrkruse latest safestrap, as it removes the format button.
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