Develop Bugs

Android boot problems

I have the T-mobile touch pro 2. when i try to boot it, it says directory does not exist. I downloaded the 10/4 one i think. It's the latest blazin one.

Did you format your SD card first? Did you make sure you installed the CAB to your SD? Also, questions like this should go in the Project Android thread.

it is on the SD but it was not formatted. Is it necessary to format?

charburble said:
it is on the SD but it was not formatted. Is it necessary to format?
Click to expand...
Click to collapse
Not always, but it couldn't hurt. All of those 1's and 0's get confused

Alright lol. Ill try formatting it and if it doesn't work I'll post here again

Also if you are from germany and use this android updater:
you need to edit the path from "storage card/andboot" to "speicherkarte/andboot"

it worked for a couple of days, now...i have the same "directory does not exist" problem.
what may have happened?
i can not format the card, because i have to much information on it. anything else?

bogdan_wrc said:
it worked for a couple of days, now...i have the same "directory does not exist" problem.
what may have happened?
i can not format the card, because i have to much information on it. anything else?
Click to expand...
Click to collapse
Eh, something's bungled. You can try deleting (moving, renaming) your data.img, and you know it's possible to copy the data off the card, format it, and copy the data back on to the card, right!??!
Android's still kinda fickle, as this project is still very experimental and changing very quickly. I'm hoping to get to the level that the Vogue got to, but that took a VERY long time!

arrrghhh said:
Eh, something's bungled. You can try deleting (moving, renaming) your data.img, and you know it's possible to copy the data off the card, format it, and copy the data back on to the card, right!??!
Android's still kinda fickle, as this project is still very experimental and changing very quickly. I'm hoping to get to the level that the Vogue got to, but that took a VERY long time!
Click to expand...
Click to collapse
updated with the new startup up utility..and works fine

Where would you go to update the new startup utility

charburble said:
Where would you go to update the new startup utility
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=807117

I tried installing it and rebooting. It gave me the same problem. Am I doing something wrong?

charburble said:
Where would you go to update the new startup utility
Click to expand...
Click to collapse
THIS startup utility.

I installed the startup utility. Wierd thing is, Android worked a lot better before i installed this. The speaker worked, games ran faster, and the whole phone was better.

charburble said:
I installed the startup utility. Wierd thing is, Android worked a lot better before i installed this. The speaker worked, games ran faster, and the whole phone was better.
Click to expand...
Click to collapse
You can feel free to revert to your previous setup, which I assumed never worked. You'll have to actually sort out how you broke it tho, unless you just do a fresh install of a clean build from the archives.

Alright, whenever there is a new update for the Android, the android on my phone totally crashes. It doesn't boot after even if I update. The only way to totally fix it is to redownload and install it.

charburble said:
Alright, whenever there is a new update for the Android, the android on my phone totally crashes. It doesn't boot after even if I update. The only way to totally fix it is to redownload and install it.
Click to expand...
Click to collapse
I wouldn't use the update utility, it causes issues. I manually update, and it always works.

charburble said:
Alright, whenever there is a new update for the Android, the android on my phone totally crashes. It doesn't boot after even if I update. The only way to totally fix it is to redownload and install it.
Click to expand...
Click to collapse
How does it 'totally crash'? Does it do the rhod100 thing of the HaRET loading indicator getting to the end then nothing happens, does it crash during the boot text, or does it crash somewhere else?

HOW TO: Install FXP113 Custom ROM on Xperia Play R800x

When installing FXP113 to my phone, I found that on bootup I would get an error on the phone process and I had no service. After trying a few different things, I finally found the solution: Install FXP112 first, then install FXP113 over it without wiping data. Here is a step by step tutorial on installing FXP113 on the R800x. It probably would work the same for all Xperia Plays.
Required: Rooted Xperia Play and unlocked bootloader.
Needed Files: FXP112 as modified by Chevyowner
FXP113 as modified by Chevyowner
Replacement build.prop file for R800x
Fastboot - Fastboot+ADB+Fastboot_Drivers.zip
Sony Drivers
Recommended: Boot into recovery and make a Nandroid backup before continuing.
1. Copy the files for FXP112 and FXP113 to your sdcard. You will need to access these from recovery.
2. Install Fastboot. Unzip the file into C:\fastboot.
5. 2. Extract the boot.img of your choice to the fastboot directory. You may use the one in FXP113, or DarkForest3.img or DarkForest4.img (available here.)
5. Enter into Fastboot Mode. - Turn off phone. Hold search button down. Plug in USB cable. The power light should be blue The first time you do this, you will be prompted for the fastboot drivers. They will be in C:\fastboot\fastboot drivers.
6. To flash the new boot image, go to a command prompt and change to the c:\fastboot directory. Then use the following command:
fastboot -i 0x0fce flash boot boot.img <----- the name of your boot image.
7. When finished, remove the usb cable. Power on the phone and enter into Recovery. On some kernels, you will press repeatedly the volume down button; on others, you will press repeatedly on the back button or possibly the search button.
8. You MUST clear Data, Cache and Dalvik Cache. It is also recommended by some people to clear the battery stats.
9. Install zipfile from sdcard. Select the FXP112 file first. Allow it to install and then reboot the phone. (I usually clear data, cache and dalvik again just to be sure.)
10. Activate your phone on the Verizon network.
11. Now shut down and reboot into Recovery again.
12. This time, clear ONLY cache and dalvik cache. Do NOT clear data.
13. Install zipfile from sdcard. Select the FXP113 file this time. Allow it to install and then reboot the phone.
14. Copy the build.prop file into /system. You may want to rename the current one first.
15. Reboot and enjoy! You should be up and running with full data, wifi access now.

re
So for step #10 do u get charged from verizon to activate ur new roms data?
And for #14 do u just copy it via root explorer to /system?
Thanks for taking time to write this

FPlusPS3 said:
So for step #10 do u get charged from verizon to activate ur new roms data?
And for #14 do u just copy it via root explorer to /system?
Thanks for taking time to write this
Click to expand...
Click to collapse
#10 There is no charge to activate the phone if you already have service. It's like dialing *228 and choosing option 1, only the system does it for you.
#14 Yes, you can just copy it to \system, but don't forget to change access to RW before pasting. You may also want to rename the old file first as a backup, although I never have.
Sent from my R800x using XDA

my phone gets stuck at the android screen after i flash fxp112

johnboyjr said:
my phone gets stuck at the android screen after i flash fxp112
Click to expand...
Click to collapse
What kernel did you use?
Did you clear data, cache and dalvik cache before you installed FXP112?
If yes, just for kicks, go clear it again.
Also, remember, the first boot after a clean install takes longer than normal.
Sent from my R800x using XDA

yes i cleared them and and i tried DarkForest4 and fxp112
i waited over 15 min still nothing

johnboyjr said:
yes i cleared them and and i tried DarkForest4 and fxp112
i waited over 15 min still nothing
Click to expand...
Click to collapse
OK. Well, if it were me, the next thing I would do is to flash back to totally stock and get that working. Then try it again.
Sent from my R800x using XDA

What changes are in your build.prop? I've been running fine (except for one or two small problems) with the standard build.prop from FXP112.

crono141 said:
What changes are in your build.prop? I've been running fine (except for one or two small problems) with the standard build.prop from FXP112.
Click to expand...
Click to collapse
I think it was just edited to identify the phone properly as an R800x. PaxChristos told me to use it when he helped me install FXP111 and I have used it ever since. I haven't had any issues at all with it, so you might give it a try if you're on Verizon.
Sent from my R800x using XDA

That was only needed the first time Chevy made FXP111 work, he missed some things in the build.prop that created graphical artifacts in menus and such. All of his builds after that have the correct build.prop now.
Sent from my R800x using XDA

*22899 is the shortcut for activating service in case anyone wanted to just store it for future reference
-and you can also use flashtool to flash back to stock or flash a new kernel

*228 worked fine for me. semcsuite.apk won't show up in my app drawer. I moved it to /system/app and fixed permissions. Still not there.
Sent from my R800x using XDA

Wallrunner said:
That was only needed the first time Chevy made FXP111 work, he missed some things in the build.prop that created graphical artifacts in menus and such. All of his builds after that have the correct build.prop now.
Sent from my R800x using XDA
Click to expand...
Click to collapse
Thanks! Good to know, and one less thing to screw with in the future!
Sent from my R800x using XDA

re
Does Psxperia or XPERIA GAMEPAD games even work on cm9

For some reason, trying use videocall in gtalk worked fine at first, but changing to rear camera made gtalk fc. After that no camera works at all.
GPS only works on maps (no on gps status, or any other app), since my wifi neighbours are all on the google database i'm not sure if the true gps is really working.
And have another annoying things.
I'm hacking all my phones since android 2.1, and I cant consider this release as an true release candidate. Its more beta.
I have a r800i.

FPlusPS3 said:
Does Psxperia or XPERIA GAMEPAD games even work on cm9
Click to expand...
Click to collapse
From what I have read... no. That is why I have not jumped ship to CM. Otherwise I would be there right now. So until they get the touchpads working I will wait, although I have also read they are working on creating from scrathc their own drivers for the touchpads as the current drivers now require SE framework...... so cross your fingers.

Nighty0 said:
For some reason, trying use videocall in gtalk worked fine at first, but changing to rear camera made gtalk fc. After that no camera works at all.
GPS only works on maps (no on gps status, or any other app), since my wifi neighbours are all on the google database i'm not sure if the true gps is really working.
And have another annoying things.
I'm hacking all my phones since android 2.1, and I cant consider this release as an true release candidate. Its more beta.
I have a r800i.
Click to expand...
Click to collapse
Not to be rude or by any disrespect but how isn't it a "true" release? A release is a release..being that it's in beta status doesn't mean it's any less, cm is always changing and improving so there is no hey this is the final version kind of thing..CDMA isn't even supported by cm at all so the fact we have cm9 before verizon gives it to us is amazing. Just to point out, this isn't hacking by any means, android is open source..it's like going into an open store and saying you're breaking in

agraceful said:
Not to be rude or by any disrespect but how isn't it a "true" release? A release is a release..being that it's in beta status doesn't mean it's any less, cm is always changing and improving so there is no hey this is the final version kind of thing..CDMA isn't even supported by cm at all so the fact we have cm9 before verizon gives it to us is amazing. Just to point out, this isn't hacking by any means, android is open source..it's like going into an open store and saying you're breaking in
Click to expand...
Click to collapse
Yes, giving their release to us is amazing, but saying that camera works on changelog, and not even the basic apps like gtalk and camera works, this barely can be considered as working.
As a software engineer I label as a beta, not RC anything. beta is to fix stopper bug like this, RC is for the little annoyances lonely.
For example, my work friend installed another rom on their htc sensation, labeled as beta and all features works, with jagged areas here and there.
And yep, I know the Team FreeXperia is a one guy team
I'm happy with all this releases, only frustrated because the thing is being labeled as working, when not. So I made a report here to make sure another person doesn't make the same mistake as me.

netizenmt said:
Thanks! Good to know, and one less thing to screw with in the future!
Sent from my R800x using XDA
Click to expand...
Click to collapse
actually this build.prop works better it lets Plants Vs Zombies and Asphalt 6 RUN and work

How do install install the custom rom and set up fastboot?

Android 4.3 OTA Security Update Boot Loop Issue and Solution

I hit a boot loop snag on my Galaxy Nexus GSM after installing the recent 4.3 OTA security update. I had no issues with the initial Android 4.3 release, but the security update did something that made my device hit a boot loop. I could restore from a Nandroid backup, but about once a day I would hit the boot loop snag again. After dealing with daily restores for a couple days I dug into it a bit and found that when the phone gets mired in a boot loop I can fix it by deleting two files.
The trick is you have to be using TWRP on the recovery partition because that will let you use a file manager to delete the two files. There may well be other solutions but that's been the easiest for me. The two files which need to be deleted are:
/data/system/locksettings.db
/data/system/locksettings.db-shm
If you use Google Wallet you'll see a similarly named file there "locksettings.db-wal" -- DO NOT DELETE THIS ONE, just the two above.
If this helps anyone please post so if it doesn't people won't waste their time -- THANKS!

Told my cousin she said that it worked like a charm! What do those two files actually do?
Sent from my Galaxy Nexus using Tapatalk 4

Vekhez said:
Told my cousin she said that it worked like a charm! What do those two files actually do?
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
To be honest -- I have no idea. I found this by pure trial and error after a totally non-related post pointed to the /data/system folder.
The files appear to get recreated when the phone reboots so it's probably generated from the system partition ultimately.
From what I know now, it appears as though SuperSU is causing this somehow. Is your cousin using SuperSU do you know?
There was a recent update to version 1.60 of SuperSU which was supposed to address this and I think it did for some users, perhaps Nexus 4 users only, but I definitely have this issue still even with the newest 1.65 version.
I've ended up created a Tasker script to delete the files on reboot because I was tired of having to repetitively reboot into TWRP and manually delete them. It works well but I'd much rather fix the underlying cause.

sansnil said:
To be honest -- I have no idea. I found this by pure trial and error after a totally non-related post pointed to the /data/system folder.
The files appear to get recreated when the phone reboots so it's probably generated from the system partition ultimately.
From what I know now, it appears as though SuperSU is causing this somehow. Is your cousin using SuperSU do you know?
There was a recent update to version 1.60 of SuperSU which was supposed to address this and I think it did for some users, perhaps Nexus 4 users only, but I definitely have this issue still even with the newest 1.65 version.
I've ended up created a Tasker script to delete the files on reboot because I was tired of having to repetitively reboot into TWRP and manually delete them. It works well but I'd much rather fix the underlying cause.
Click to expand...
Click to collapse
Yeah, they are using SuperSU...they are still on 1.5, I'll tell them to update.
Sent from my Galaxy Nexus using Tapatalk 4

Vekhez said:
Yeah, they are using SuperSU...they are still on 1.5, I'll tell them to update.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Thanks, Vekhez. Let me know if that hopefully fixes the problem for them. If it does it means I'm "special" not in a good way!

sansnil said:
Thanks, Vekhez. Let me know if that hopefully fixes the problem for them. If it does it means I'm "special" not in a good way!
Click to expand...
Click to collapse
Nope it didn't.. Same problem.
Sent from my Galaxy Nexus using Tapatalk 4

Vekhez said:
Nope it didn't.. Same problem.
Click to expand...
Click to collapse
Thanks for this. I'm sorry for your cousin but happy for me because that means it's not something unique or specific to my device.
This is helpful -- I'm going to post this over in the SuperSU thread and see if Chainfire will pick it up and look into it.
Stay tuned...

sansnil said:
Thanks for this. I'm sorry for your cousin but happy for me because that means it's not something unique or specific to my device.
This is helpful -- I'm going to post this over in the SuperSU thread and see if Chainfire will pick it up and look into it.
Stay tuned...
Click to expand...
Click to collapse
Ok, so it turns out this is actually being caused by the app "Delayed Lock" if you use a pattern lock. If you use a PIN/password lock it won't happen, but if you use a pattern lock with the current version of Delayed Lock on a Galaxy Nexus this boot loop issue will occur.
I've opened a bug with the Delayed Lock Dev so hopefully he'll find a way to fix it. In the meantime, choices are to either disabled/uninstall Delayed Lock (hate!) or switch to a PIN or password lock setting.

Hey guys,
I had the same problem and found out that it could be solved, without losing any data, by directly flashing the update.
Here's what I did: http://forum.xda-developers.com/showthread.php?t=2427613
Best of luck.

Latest T-Mobile Update Slowed Down My Phone

Hi guys,
So i just downloaded and installed the latest T-mobile update and now my phone is slower.
Every time I hit the home button, the image blinks and redraws and there's just a hint of stutter.
The app drawer also takes a little longer now.
What the heck?
It used to be so zippy and fast. How do I fix it, anyone know?

cainman said:
Hi guys,
So i just downloaded and installed the latest T-mobile update and now my phone is slower.
Every time I hit the home button, the image blinks and redraws and there's just a hint of stutter.
The app drawer also takes a little longer now.
What the heck?
It used to be so zippy and fast. How do I fix it, anyone know?
Click to expand...
Click to collapse
Might help to post which update you received.

reTARDIS said:
Might help to post which update you received.
Click to expand...
Click to collapse
D85110r

cainman said:
D85110r
Click to expand...
Click to collapse
Try disabling hw overlays in developers options to help with that redraw stutter. Remember you have to set it everytime you boot, unless you're booted with xposed installed, then you could download the module that keeps it active at all times.
This seems to have helped a lot of people with your issue.

Thank you.
It's sadly still doing it.

cainman said:
Thank you.
It's sadly still doing it.
Click to expand...
Click to collapse
Did you take the ota or download one of the twrp upgrades floating around? Either way in your situation you probably need to do a factory reset. Alternatively follow the twrp method HERE if you haven't already and I can personally guarantee a better than ota install. If you want it to be done correctly to fix any problems you need to wipe the system and data partitions before flashing. Also don't forget to download super su if you want to keep root (linked in guide). There is another upgrade twrp file in the development section I think that is not a perfect 1:1 image and could give problems. Not saying that particular rom is bad or that it is the problem, its just not a 1:1 like the guide I linked you to it is directory/installer script dependent. The one I made transfers the whole untouched partition over and inside has all the symlinks and permissions preset by LG.

Factory Reset

Unable to install latest M8s OTA update v2.20.401.1

Hello,
I'm new to this forum, and I could not find anything related to this issue. I'm successfully downloading the latest update and when I try to install it, the installation goes up to 25% and I get the red exclamation mark afterwards. The phone then restarts, and I'm back at the beginning, where I have to re-download the update all over again. I don't have any custom ROMs flashed on my device, it's just like I bought it, the latest update that I made was the update to Android v6.0.1. Current software number is v2.10.401.1, if that is of any importance. I've factory reset the phone, and tried applying the update on a fresh phone, but it still won't work.
Also, while I'm here, I might just ask... I'm getting frequent app crashes/unresponsive app, mostly on the apps that I'm using the most, Facebook and Instagram. Facebook is more stable, crash/unresponsiveness does not happen very often, but for Instagram it's always happening after scrolling 3-4 images. Also, the Sense Home app is always getting unresponsive after a phone restart, and I have to restart it several times until it gets back to normal, since it cannot recover from it, I'm not seeing the home screen at all.
I was very satisfied with my phone before the update to Android 6, but after upgrade, I'm frequently having these minor problems, another one of which is the SD card "unexpectedly removed" error, which is happening when I open up the gallery or the file manager. I'm running low on patience, I really hoped that this last update will fix things, but I'm very close to slamming the phone off the wall, that's how frustrated I am. Please help

Well I'm no expert here but I've also experienced the freezes in such apps and even normal restart didn't work, so I had to force restart it. This happened in marshmallow and lollipop both so i tried removing my sd card and freezes were gone. In my case it was the sd card, so you can try that.
And for the update check if your bootloader is locked, assuming you bought it refurbished or used, the previous owner might have done some tinkering.
Hope you find the solution soon :good:

spiderwebmkd said:
Hello,
I'm new to this forum, and I could not find anything related to this issue. I'm successfully downloading the latest update and when I try to install it, the installation goes up to 25% and I get the red exclamation mark afterwards. The phone then restarts, and I'm back at the beginning, where I have to re-download the update all over again. I don't have any custom ROMs flashed on my device, it's just like I bought it, the latest update that I made was the update to Android v6.0.1. Current software number is v2.10.401.1, if that is of any importance. I've factory reset the phone, and tried applying the update on a fresh phone, but it still won't work.
Also, while I'm here, I might just ask... I'm getting frequent app crashes/unresponsive app, mostly on the apps that I'm using the most, Facebook and Instagram. Facebook is more stable, crash/unresponsiveness does not happen very often, but for Instagram it's always happening after scrolling 3-4 images. Also, the Sense Home app is always getting unresponsive after a phone restart, and I have to restart it several times until it gets back to normal, since it cannot recover from it, I'm not seeing the home screen at all.
I was very satisfied with my phone before the update to Android 6, but after upgrade, I'm frequently having these minor problems, another one of which is the SD card "unexpectedly removed" error, which is happening when I open up the gallery or the file manager. I'm running low on patience, I really hoped that this last update will fix things, but I'm very close to slamming the phone off the wall, that's how frustrated I am. Please help
Click to expand...
Click to collapse
If you are willing to, you can unlock the bootloader from http://www.htcdev.com/bootloader/ and flash a stock sense ROM or other custom ROMs and that might solve the app crash problem.

bilal.fanatic said:
Well I'm no expert here but I've also experienced the freezes in such apps and even normal restart didn't work, so I had to force restart it. This happened in marshmallow and lollipop both so i tried removing my sd card and freezes were gone. In my case it was the sd card, so you can try that.
And for the update check if your bootloader is locked, assuming you bought it refurbished or used, the previous owner might have done some tinkering.
Hope you find the solution soon :good:
Click to expand...
Click to collapse
I've already tried removing the SD card, and I've seen slight improvement in the app crashes, but they were still occurring. My bootloader is locked, but I'm going to unlock it now and flash a new ROM, I can't play around with it anymore

spiderwebmkd said:
I've already tried removing the SD card, and I've seen slight improvement in the app crashes, but they were still occurring. My bootloader is locked, but I'm going to unlock it now and flash a new ROM, I can't play around with it anymore
Click to expand...
Click to collapse
Before you do that .. as there is almost no custom ROM available for M8s except CM which is in progress, I don't suggest to unlock bootloader.. try to find and install 2.10.401.1 RUU
Installing RUU will usually fix this kind of problem if the data partition is sort of corrupted but not damaged.

ckpv5 said:
Before you do that .. as there is almost no custom ROM available for M8s except CM which is in progress, I don't suggest to unlock bootloader.. try to find and install 2.10.401.1 RUU
Installing RUU will usually fix this kind of problem if the data partition is sort of corrupted but not damaged.
Click to expand...
Click to collapse
You are suggesting to install the same software version that I currently have? Where do I find it and how do I install it manually?

spiderwebmkd said:
You are suggesting to install the same software version that I currently have? Where do I find it and how do I install it manually?
Click to expand...
Click to collapse
Yeah, same version then after OTA to 2.20.401.1
You can read this - http://forum.xda-developers.com/htc...lp-thread-htc-one-m8s-to-stock-howto-t3190238
and this - http://forum.xda-developers.com/htc-one-m8/one-m8s-general/make-custom-recovery-htc-one-m8s-t3114245
on how to manually install RUU
And for the RUU .. I have to check my PC for the full filename so it is easier to find link. I'll let you know tomorrow (on mobile now)

spiderwebmkd said:
I've already tried removing the SD card, and I've seen slight improvement in the app crashes, but they were still occurring. My bootloader is locked, but I'm going to unlock it now and flash a new ROM, I can't play around with it anymore
Click to expand...
Click to collapse
If thats what you want to do I'd suggest you try cm12.1 . Unfortunately its the only ROM available to us but its way better than stock in terms of performance imho. But do that if you're willing to sacrifice some things such as double tap to wake and also any 3rd party camera apps, because they crash alot and yeah no boomsound. :fingers-crossed:

bilal.fanatic said:
If thats what you want to do I'd suggest you try cm12.1 . Unfortunately its the only ROM available to us but its way better than stock in terms of performance imho. But do that if you're willing to sacrifice some things such as double tap to wake and also any 3rd party camera apps, because they crash alot and yeah no boomsound. :fingers-crossed:
Click to expand...
Click to collapse
I'll try with @ckpv5 suggestion, to install 2.10.401.1 RUU and then try OTA upgrade to 2.20.401.1. If it fails, or if it succeeds but apps are still crashing as they were before, I'll definitely switch to cm, whatever version is stable at the moment. Double tap to wake is really annoying and I don't need it, I don't use 3rd party camera apps, and I guess I'll have to live without boomsound Thanks for the tip, though.

ckpv5 said:
Yeah, same version then after OTA to 2.20.401.1
You can read this - http://forum.xda-developers.com/htc...lp-thread-htc-one-m8s-to-stock-howto-t3190238
and this - http://forum.xda-developers.com/htc-one-m8/one-m8s-general/make-custom-recovery-htc-one-m8s-t3114245
on how to manually install RUU
And for the RUU .. I have to check my PC for the full filename so it is easier to find link. I'll let you know tomorrow (on mobile now)
Click to expand...
Click to collapse
I did a bit of digging, and what I found is this:
0PKVIMG_M8_QL_UL_M60_SENSE70_HTC_Europe_2.10.401.1_Radio_1.0.U20410.1 @ 60201_20.05_018_F_release_479349_combined_signed.zip
which I downloaded from https://ruu.lalleman.net/ -> Firmware (Expert) -> Firmware Crypted (Original HTC)
I'll wait for you to confirm that this is the one that I need, before I continue with the procedure (rename, put to SD, boot to bootloader, fastboot)

does someone have stock marshmallow twrp backup. I accidentally deleted mine and now stuck with cm only

spiderwebmkd said:
I did a bit of digging, and what I found is this:
0PKVIMG_M8_QL_UL_M60_SENSE70_HTC_Europe_2.10.401.1_Radio_1.0.U20410.1 @ 60201_20.05_018_F_release_479349_combined_signed.zip
which I downloaded from https://ruu.lalleman.net/ -> Firmware (Expert) -> Firmware Crypted (Original HTC)
I'll wait for you to confirm that this is the one that I need, before I continue with the procedure (rename, put to SD, boot to bootloader, fastboot)
Click to expand...
Click to collapse
I can't access that site but it is the same file that I have that I got from different link.
Yes .. use that one.

I cant update the firmware either. Stucks at 25% the same. Couldn't solve. Tried to flash the firmware mentioned above. Didnt change. :/
EDit: Nevermind it passed 25% barrier lol. 70% and installing

parser said:
I cant update the firmware either. Stucks at 25% the same. Couldn't solve. Tried to flash the firmware mentioned above. Didnt change. :/
EDit: Nevermind it passed 25% barrier lol. 70% and installing
Click to expand...
Click to collapse
It passed after you flashed the RUU? the same procedure that I'm about to do?

spiderwebmkd said:
It passed after you flashed the RUU? the same procedure that I'm about to do?
Click to expand...
Click to collapse
yep sameway. Downloaded and flashed the firmware after renaming. Downloaded the ota via software update and voila.
took a little long but worked at the and.

parser said:
yep sameway. Downloaded and flashed the firmware after renaming. Downloaded the ota via software update and voila.
took a little long but worked at the and.
Click to expand...
Click to collapse
Worked for me as well. I'm at v2.20 now, so far no app crashes, the "SD card unexpectedly removed" is still there, but I'll live. Thanks a lot @ckpv5 for your suggestion, I practically got a brand new phone now!

spiderwebmkd said:
Worked for me as well. I'm at v2.20 now, so far no app crashes, the "SD card unexpectedly removed" is still there, but I'll live. Thanks a lot @ckpv5 for your suggestion, I practically got a brand new phone now!
Click to expand...
Click to collapse
hey! can you, if you have, send me a clean backup of the v2.20. I kinda rushed in and forgot to take a backup and now I am stuck with cm :/.

parser said:
hey! can you, if you have, send me a clean backup of the v2.20. I kinda rushed in and forgot to take a backup and now I am stuck with cm :/.
Click to expand...
Click to collapse
I don't have a backup of v2.20. I flashed the v2.10 from https://ruu.lalleman.net/ -> Firmware (Expert) -> Firmware Crypted (Original HTC) , and then I downloaded the OTA update on top of it.

spiderwebmkd said:
https://ruu.lalleman.net/ -> Firmware (Expert) -> Firmware Crypted (Original HTC)
Click to expand...
Click to collapse
no no not that. I mean TWRP backup. I dont want to go back to zero relock the phone and flash the zip and re-unlock the phone root again bla bla.
Since you did the same process, I thought maybe you took a backup of the rom after you updated it.
I made a mistake by not taking a backup of it so now it is a problem for me :/
Edit: damn! thanks anyway. I have a long night in front of me clearly. I hate this phone :/

V4A is not working anymore with the latest update. Is it me or everyone has the same problem.