Database Users

[Q] Help

tried to install custom rom, didn't work out. tried to do a restore the phone gets to a point where it stops and says "lost+found" and won't go any further. any suggestions?
Thanks
Also when i try to reboot in recovery i get this "E:can't open/cache/recovery/log" and stops right there. Any ideas??

Odin is your friend look it up!!
Sent from my SPH-D700 using XDA App

Have odin and still can't get past the places on my previous post. Every time i try to reboot i get the "clockworkMod Recovery v2.5.1.0"
"E:can't open /cache/recovery/log"
just like that half way down the screen. won't go any further. need some serious help.

you shouldnt be using recovery mode, you need to be in download mode. power off your device then hold 1 and power on again. you should get a little android with a shovel. thats the mode your phone needs to be on in order to odin it back

Skrewup5 said:
you shouldnt be using recovery mode, you need to be in download mode. power off your device then hold 1 and power on again. you should get a little android with a shovel. thats the mode your phone needs to be on in order to odin it back
Click to expand...
Click to collapse
At this point the only way i can power it down is to remove the battery and even when i hold 1 and power back up it goes into clockwork recovery mode instead of download mode.

thats incredibly strange. ive had the same problem as you before when i installed a bunk rom but it didnt affect download mode. see if you can flash over stock dk28, after factory resetting 3 times, wiping cache and then dalvik. i think the reason its stuck on the samsung screen is because the last rom you installed is conflicting with something. but if you can get another to work, it may hopefully at least allow you to enter recovery so you can odin.
i may just be talking out my ass here, but its def a software issue, as opposed to hardware.
or it may even be a kernel conflict, make sure the one youre using is compatible with the rom

Skrewup5 said:
thats incredibly strange. ive had the same problem as you before when i installed a bunk rom but it didnt affect download mode. see if you can flash over stock dk28, after factory resetting 3 times, wiping cache and then dalvik. i think the reason its stuck on the samsung screen is because the last rom you installed is conflicting with something. but if you can get another to work, it may hopefully at least allow you to enter recovery so you can odin.
i may just be talking out my ass here, but its def a software issue, as opposed to hardware.
or it may even be a kernel conflict, make sure the one youre using is compatible with the rom
Click to expand...
Click to collapse
A friend at work, who has an EVO wanted to work on my phone while I was out of the office on business. He was able to finally get it to enter download mode, flashed odin and froyo DK28 and got me back up. Just a temporary glich that took several tries for some reason. Anyway I'm back on 2.2.1 and looking forward to rooting again but probably going to download a different rom. Thanks for help and advise. also good to have phone savy friends at work. Thanks Ashley.
Dana

Im glad it was all resolved haha. try the new bonsai4all 2.0. its very easy to install

[Resolved] Stuck in a boot loop

I was trying to re-install stock apps that i deleted in order to get the OTA update, but in the process i accidentally deleted some thing i shouldn't have(no idea what it was). I had previously been running the odex optimized apps and framework by dc13, and after copying the stock apps to the system/app folder i attempted to delete all of the .odex files. this is where i accidentally deleted some thing essential. i rebooted and was face to face with boot loop. been there ever since please help, i dont want to be stuck with an expensive brick!

swampy67 said:
I was trying to re-install stock apps that i deleted in order to get the OTA update, but in the process i accidentally deleted some thing i shouldn't have(no idea what it was). I had previously been running the odex optimized apps and framework by dc13, and after copying the stock apps to the system/app folder i attempted to delete all of the .odex files. this is where i accidentally deleted some thing essential. i rebooted and was face to face with boot loop. been there ever since please help, i dont want to be stuck with an expensive brick!
Click to expand...
Click to collapse
Would someone (aka moderator) simply sticky a bold
DO NOT REMOVE ANY FACTORY FILES, u goty plenty of room.......
to prevent this kinda stuff

Reinstall your system by using this file -
http://www.filesonic.com/file/958397621/acer_a500_0.000.00_1.122.01_emea_gen5_update.zip.html

dr1337 said:
Reinstall your system by using this file -
http://www.filesonic.com/file/958397621/acer_a500_0.000.00_1.122.01_emea_gen5_update.zip.html
Click to expand...
Click to collapse
but how do i reinstall when im stuck in a boot loop? is there some way to execute adb?

Rename the file Update.Zip, put the file on the root folder of your SDcard. Power on the tablet with the volume down button held

anubis13 said:
Rename the file Update.Zip, put the file on the root folder of your SDcard. Power on the tablet with the volume down button held
Click to expand...
Click to collapse
Thanks I'll give it a shot
Sent from my PC36100 using XDA Premium App

thanks this worked like a charm. Gotta love the XDA community.

A strange thing happened to me, i was working with the tab, and layed it
aside for a while, suddenly it shutted down, and rebooted.
(Not sure where i went wrong, or why this happened,cant remember doin anything out of the ordinairy)
Then i got stuck in this bootloop.
Tried to update, wich goes okee i guess, but after the reboot, i got stuck in a
different boot loop.
Im sure i didnt mess with the standard files that came with the device,
however i have another bootanimation, than stock, could this be causing the "second"
bootloop?
Kinda out of options now, hope you guys can shed more light to this, but i think
i have to return it to Acer for repairs.
Btw: great device anyway!

Just want to let you know that was not the correct update.zip for our Country you make consider going back to the USA rom. Or you will not receive the Correct Updates. If any at all. These are the files and instructions you will need to get back to stock and be able to receive all updates.
http://forum.xda-developers.com/showthread.php?t=1101859
Give thanks and support if this helps.

Chaz36 said:
A strange thing happened to me, i was working with the tab, and layed it
aside for a while, suddenly it shutted down, and rebooted.
(Not sure where i went wrong, or why this happened,cant remember doin anything out of the ordinairy)
Then i got stuck in this bootloop.
Tried to update, wich goes okee i guess, but after the reboot, i got stuck in a
different boot loop.
Im sure i didnt mess with the standard files that came with the device,
however i have another bootanimation, than stock, could this be causing the "second"
bootloop?
Kinda out of options now, hope you guys can shed more light to this, but i think
i have to return it to Acer for repairs.
Btw: great device anyway!
Click to expand...
Click to collapse
Okay so this is what i did as directed by the guys above.
1. Download this file. have to warn you though this service is horribly slow http://api.viglink.com/api/click?fo...ww.filesonic.com/file/958397...pdate.zip.html
2. Put your external SD card into your computer, and copy over the file to the root of the card.
3. Rename the file update.zip(make sure it isn't named update.zip.zip)
4. Put the SD card back it the tab.
5. Make sure your tab is completely shut down.
6. Hold down the volume down button and press the power button.( dont let go of the volume down button till the screen turns on)
7. The recovery will boot and the update should hopefully restore your tab.
8.(optional but recommended) follow these steps in order to revert back to the latest OTA american version so that your able to upgrade to 3.1 when it comes out.http://forum.xda-developers.com/showthread.php?t=1101859
Hope this helps.

Thanks for quick reply, i did exactly those steps before, and it seems that the
update goes well, then after the update, the tablet reboots loads up a bit, and then
again runs into a bootloop.
That is what is different in comparison with the un brick methods come-out, i read all over this forum.
So im a little affraid something different is goin on, with or in my tablet after the update completes.
It just never really recovers from the boot loop with or without the update.
sadly.

Chaz36 said:
Thanks for quick reply, i did exactly those steps before, and it seems that the
update goes well, then after the update, the tablet reboots loads up a bit, and then
again runs into a bootloop.
That is what is different in comparison with the un brick methods come-out, i read all over this forum.
So im a little affraid something different is goin on, with or in my tablet after the update completes.
It just never really recovers from the boot loop with or without the update.
sadly.
Click to expand...
Click to collapse
Well sorry that didn't work, i am not to experienced with development for this tab, so im fresh out of ideas. It might help to start a new thread explaining that you tried to un-brick your tab via this method and that a boot loop still occurs. Maybe some super smart devs can help you.

Crsdr37 said:
Just want to let you know that was not the correct update.zip for our Country you make consider going back to the USA rom. Or you will not receive the Correct Updates. If any at all. These are the files and instructions you will need to get back to stock and be able to receive all updates.
http://forum.xda-developers.com/showthread.php?t=1101859
Give thanks and support if this helps.
Click to expand...
Click to collapse
yeah i did that right after i un-bricked it, but thanks for the heads up anyways.

For anyone else who has bootloop problems and finds his/her way to this thread, there is another option. Plug in a USB keyboard, then boot up the tab by holding the power button and volume down (the side closest to the power button) at the same time until text starts appearing in the upper left corner of the screen. Hit the home button on the keyboard, and boom! You are in a recovery screen. Use the keyboard to select factory reset, and your tab is back to the original state. You will lose root and all of your info, but you have your tab working again. There really should be a way to do this without adding a keyboard, but it works fine.

SmittyRN said:
For anyone else who has bootloop problems and finds his/her way to this thread, there is another option. Plug in a USB keyboard, then boot up the tab by holding the power button and volume down (the side closest to the power button) at the same time until text starts appearing in the upper left corner of the screen. Hit the home button on the keyboard, and boom! You are in a recovery screen. Use the keyboard to select factory reset, and your tab is back to the original state. You will lose root and all of your info, but you have your tab working again. There really should be a way to do this without adding a keyboard, but it works fine.
Click to expand...
Click to collapse
Dude, you just made my day.
Thanks.!!!!!

[Q] Please help me out of my own stupidity

Hello, I am a pure noob here, and one to android in general.
I bought a TF101 a while back, and while complaining to a friend (over xbox live) that it was a bit slow at times, he told me to root it and install cyanogenmod.
So I started looking into it, and thought it looked well within my capabilities to do, so I went for it. I followed the instructions at the cyanogenmod wiki.
Wthout knowing the issues I was going to encounter before encountering them, I really didn't know what pitfalls to research, and thought I'd be fine if I just followed the instructions above.
So, I used Wheelie to root and installed CWM 6.0.1.3 using NVFlash. A little trouble, but I got through it, so far so good.
Here is my problem, in the instructions when they refer to the SD card, I took that to mean the microSD card. So now, when I go into CWM, I cannot install the rom from my external storage (CWM does not support this).
I thought I had created a backup of my current installation, but apparently, I failed at that as well.
And of course, since the instructions above, or the instructions on the Wheelie page don't mention it, I didn't enable debugging through USB before doing all of this.
So now, my tablet does nothing unless I access it with Wheelie and use NVFlash. Otherwise, it does nothing when i turn it on. I've looked around this forum and others this morning for about 2 hours and have not found any solution that will work for me. They all involve a backup on the internal SD storage (which I don't have) or using ADB (which I can't do without USB Debugging being enabled).
If any of you more knowledgeable about this stuff could take pity on my, I would appreciate any help.
Is my tablet now useless?
Thank you!

try this method at least you can go back how your tablet was before...let me know
http://forum.xda-developers.com/showthread.php?t=1688012
curmud6e0n said:
Hello, I am a pure noob here, and one to android in general.
I bought a TF101 a while back, and while complaining to a friend (over xbox live) that it was a bit slow at times, he told me to root it and install cyanogenmod.
So I started looking into it, and thought it looked well within my capabilities to do, so I went for it. I followed the instructions at the cyanogenmod wiki.
Wthout knowing the issues I was going to encounter before encountering them, I really didn't know what pitfalls to research, and thought I'd be fine if I just followed the instructions above.
So, I used Wheelie to root and installed CWM 6.0.1.3 using NVFlash. A little trouble, but I got through it, so far so good.
Here is my problem, in the instructions when they refer to the SD card, I took that to mean the microSD card. So now, when I go into CWM, I cannot install the rom from my external storage (CWM does not support this).
I thought I had created a backup of my current installation, but apparently, I failed at that as well.
And of course, since the instructions above, or the instructions on the Wheelie page don't mention it, I didn't enable debugging through USB before doing all of this.
So now, my tablet does nothing unless I access it with Wheelie and use NVFlash. Otherwise, it does nothing when i turn it on. I've looked around this forum and others this morning for about 2 hours and have not found any solution that will work for me. They all involve a backup on the internal SD storage (which I don't have) or using ADB (which I can't do without USB Debugging being enabled).
If any of you more knowledgeable about this stuff could take pity on my, I would appreciate any help.
Is my tablet now useless?
Thank you!
Click to expand...
Click to collapse

kokobsb said:
try this method at least you can go back how your tablet was before...let me know
http://forum.xda-developers.com/showthread.php?t=1688012
Click to expand...
Click to collapse
Wow, thanks so much. This worked! I thought it was done for.
Thank you!
Is there a thank 100 times button?

Ok, so I used this tool, and put a stock ICS on the tablet I downloaded from Asus. As I was setting everything back up, content to just have my old tablet back, it froze on me. I restarted, the tablet, and now it won't load again. It gets stuck at the EEE pad screen. Worse, when I turn it off, it automatically turns right back on.
I can manage to get this to load in recovery mode (vol down; I don't even need to hit the power button because it just automatically turns on) but I can't get it to boot up in APX for me to flash and restore again. I've tried several times, but there doesn't seem to be enough time to plug the cable in between reboots for it to not boot up regularly.
When I boot up recovery mode, it freeze there, unable to load any recovery tools.
Any more ideas? The help is much appreciated.

hmmm interesting try to reflash a recovery on it via this tool
http://forum.xda-developers.com/showthread.php?t=1681155
curmud6e0n said:
Ok, so I used this tool, and put a stock ICS on the tablet I downloaded from Asus. As I was setting everything back up, content to just have my old tablet back, it froze on me. I restarted, the tablet, and now it won't load again. It gets stuck at the EEE pad screen. Worse, when I turn it off, it automatically turns right back on.
I can manage to get this to load in recovery mode (vol down; I don't even need to hit the power button because it just automatically turns on) but I can't get it to boot up in APX for me to flash and restore again. I've tried several times, but there doesn't seem to be enough time to plug the cable in between reboots for it to not boot up regularly.
When I boot up recovery mode, it freeze there, unable to load any recovery tools.
Any more ideas? The help is much appreciated.
Click to expand...
Click to collapse

kokobsb said:
hmmm interesting try to reflash a recovery on it via this tool
http://forum.xda-developers.com/showthread.php?t=1681155
Click to expand...
Click to collapse
Thanks again for your help, but I got it another way. Holding volume + and power got the tablet to shut off and stay off. From there I was able to use the first tool you gave me pointed me to again, restored it all again, re-installed the stock OS.
From there I reflashed, re-rooted and all my issues with installing cyanogen went away. I'm not sure what went wrong the first time I tried to do this, but it all went away and installed with no issues.
Thanks again for all your help. Without it I'd have no tablet anymore.
Thanks!

yeah happy to hear you have your tab back ...i am using android revolution hd rom can you tell me which built of cyanogen your using and if you are happy with? cuz i tried a jb rom i hated it...
curmud6e0n said:
Thanks again for your help, but I got it another way. Holding volume + and power got the tablet to shut off and stay off. From there I was able to use the first tool you gave me pointed me to again, restored it all again, re-installed the stock OS.
From there I reflashed, re-rooted and all my issues with installing cyanogen went away. I'm not sure what went wrong the first time I tried to do this, but it all went away and installed with no issues.
Thanks again for all your help. Without it I'd have no tablet anymore.
Thanks!
Click to expand...
Click to collapse

[Q] Recovery Rebooting Issue

Hello,
I sure could use some help here! I just upgraded to BajaROM 16 in my stock rom slot. All was fine until I did a boneheaded thing. I wanted to go into recovery to attempt to install another ROM in slot 1 so by mistake I clicked on "recovery" in the drop screen that also has the restart and shut down buttons. Now I appear to be in a endless loop trying to find recovery. I have no idea what to do now. I tried doing the three button approach but nothing happened. I have pulled the battery and waited a few minutes but as soon as I re-start the phone, I get that damn "Recovery Reboot" message again on the top left side of the screen.
Any ideas?
Thanks!

I'm in the same boat, phone has been constantly rebooting for the last 12 hours and I can't figure out how to make it work again...

same boat here.
edit...
Resolved...

I have encountered this as well. I fixed it by Odin flashing the modem back to the phone. Once flashed, it rebooted and I had Safestrap and my rom back. Just be sure you flash the right modem file as the wrong one will brick your phone. I have done that in the past as well.

Bizack said:
same boat here.
edit...
Resolved...
Click to expand...
Click to collapse
What was the resolution? I'm in the same boat and can't get ODIN to recognize the phone.

tdamore said:
What was the resolution? I'm in the same boat and can't get ODIN to recognize the phone.
Click to expand...
Click to collapse
Whoa, Odin wont recognize the phone in download mode?
vol dn + home & Power?
You need to not use USB3, switch USB ports, change cables, if your computer wont recognize switch computers.
Open up Kies3 and re-install drivers.
Many options, try them all, don't give up. It your shot won't even turn on, then take that **** back!!!
What IO did to achieve salvation...
I flashed NC4, Rooted using towl root, then busy box and Safe Strapped flashed the NC2 kernel and bamm(no relation) back on Baja16....
(there is a process, please don't follow the steps above, go here...)

I was in the same boat...
tdamore said:
What was the resolution? I'm in the same boat and can't get ODIN to recognize the phone.
Click to expand...
Click to collapse
I was also rebooting into recovery mode over and over again after my first boot up of the recent Baja and rebooting into Recovery after updating to the new version of SS.
The only thing I could do was pull the battery and it would do again. I read the above about updating the modem, but unsure what that was, I tried rebooting into download mode again. From here, instead of hitting UP VOLUME to continue, I hit DOWN VOLUME and low and behold, I got the baja flash and it booted up my phone again.
PHEW!
Just thought I'd share what worked for me...

what am i doing wrong i did the root methods and setup the safestrap(3.75) and have been trying all evening to install bigginsRom+v6. i go thru all the steps and when i hit continue for it to reboot it just dies and does nothing. i have to pull the battery and get it back to safestrap and reinstall the stock rom. i am supposed to set it up on slot 1 instead of stock right?

downloaded another rom and tried it in another slot and the same thing. the only one i can get to load is the stock backup. anything else it just goes black and does nothing. have to pull the battery to even get it to power back on

BigHoss3 said:
what am i doing wrong i did the root methods and setup the safestrap(3.75) and have been trying all evening to install bigginsRom+v6. i go thru all the steps and when i hit continue for it to reboot it just dies and does nothing. i have to pull the battery and get it back to safestrap and reinstall the stock rom. i am supposed to set it up on slot 1 instead of stock right?
Click to expand...
Click to collapse
BigHoss3 said:
downloaded another rom and tried it in another slot and the same thing. the only one i can get to load is the stock backup. anything else it just goes black and does nothing. have to pull the battery to even get it to power back on
Click to expand...
Click to collapse
Guys, Please Go here.
Follow these directions to the letter.
First ting is figure out where you are at and use the correct method to get your s**T back up and running...

Bizack said:
Guys, Please Go here.
Follow these directions to the letter.
First ting is figure out where you are at and use the correct method to get your s**T back up and running...
Click to expand...
Click to collapse
It took some work but I got it booted back to the stock rom

I also had problems getting Odin to see my phone. In my case I just needed to unistall the USB drivers bundled with my phone and install the latest drivers FROM Samsung's website.

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