Looking for a TWRP complete backup. (32-bit) - HTC Desire 510

Me being me, I uninstalled an important app with "NoBloat" by accident and forgot to make a backup of my system files before booting. My home button stopped working but the back and window button would work. I couldn't get to my home screen. I restarted my phone and it got stuck into a boot loop and will not boot. I don't believe I have a way of fixing this without the backups, so I'm just looking for a complete factory reset for the phone. RUU didn't work as well. I have installed TWRP and flashed SuperSU onto the phone and that's it. Thanks in advance!

Related

Phone suddenly acting up need some help

I rooted my droid 4 a few months ago when I first got it so I could tether. I removed a couple of programs using titanium backup (blockbuster app and some other bloat). Phone worked fine until monday when the touchscreen stopped working. I did a reboot (power + volume down) whereupon it just sat at the M "Dual Core" logo. I tried booting into the recovery menu but selecting "recovery" didn't do anything - it would just hang.
Last night I was able to get it working again by going into the recovery menu and selecting asp fastboot, then using RSDLite to push a stock Droid 4 ROM onto the phone. However, it didn't wipe my old system, and didnt install over it either because all my files were there, and the programs I removed were still gone. So the phone worked for a few hours then the touchscreen stopped working again.
I repeated the process with RSDLite and after a few failed attempts where the phone would hang while booting, I finally got it to boot into the OS again. And this is where I am at now.
I am pretty sure that the problem is related to the OS that is on the phone now and that I need to wipe the phone and start fresh with either a custom ROM or the stock D4 ROM. The problem is that I can't get recovery to do a factory reset. As I mentioned above, recovery just hangs and doesn't do anything. I am reasonably literate when it comes to this stuff but I get really confused because there are so many different ways that people seem to do this stuff (safestrap, bootstrap, CM( etc). I would love to try CM9 but my priority right now is just to have a phone that works. Any help would be greatly appreciated.
Thanks.
whoisthisis said:
I rooted my droid 4 a few months ago when I first got it so I could tether. I removed a couple of programs using titanium backup (blockbuster app and some other bloat). Phone worked fine until monday when the touchscreen stopped working. I did a reboot (power + volume down) whereupon it just sat at the M "Dual Core" logo. I tried booting into the recovery menu but selecting "recovery" didn't do anything - it would just hang.
Last night I was able to get it working again by going into the recovery menu and selecting asp fastboot, then using RSDLite to push a stock Droid 4 ROM onto the phone. However, it didn't wipe my old system, and didnt install over it either because all my files were there, and the programs I removed were still gone. So the phone worked for a few hours then the touchscreen stopped working again.
I repeated the process with RSDLite and after a few failed attempts where the phone would hang while booting, I finally got it to boot into the OS again. And this is where I am at now.
I am pretty sure that the problem is related to the OS that is on the phone now and that I need to wipe the phone and start fresh with either a custom ROM or the stock D4 ROM. The problem is that I can't get recovery to do a factory reset. As I mentioned above, recovery just hangs and doesn't do anything. I am reasonably literate when it comes to this stuff but I get really confused because there are so many different ways that people seem to do this stuff (safestrap, bootstrap, CM( etc). I would love to try CM9 but my priority right now is just to have a phone that works. Any help would be greatly appreciated.
Thanks.
Click to expand...
Click to collapse
select recovery by holding the vol buttons and power on boot just like fastboot. press vol - for recovery. when u see dead droid hit both vol up and vol down and theres the recovery
Thanks, I was finally able to get into recovery. Wiped data and did a factory reset which again got stuck at the logo screen. Went back into fastboot and ran RSDlite again to flash the stock ROM which gets me to the "Welcome to Droid4" screen where it says "touch the android to start" but the touchscreen is unresponsive. Starting to think there is something physically wrong with the phone....
send it to motorola, I've heard their customer support is pretty good. but if you voided your warranty by rooting/flashing other roms, I've heard bricking the phone and sending it in works to get a new one too
The only way I can send it back is through an insurance claim so I am trying to save myself $75j if this thing will just work. I just did a reboot and now the touchscreen seems to be working so I am going through the setup process....so weird.
Update: I was able to get the phone to load up and configured my google account etc. It appears that the phone is now running on completely stock installation of OS.....
whoisthisis said:
The only way I can send it back is through an insurance claim so I am trying to save myself $75j if this thing will just work. I just did a reboot and now the touchscreen seems to be working so I am going through the setup process....so weird.
Update: I was able to get the phone to load up and configured my google account etc. It appears that the phone is now running on completely stock installation of OS.....
Click to expand...
Click to collapse
So it has been a couple days now and the phone works totally fine. It looks like the problem was that by removing whatever bloatware that I did, the phone's OS got borked when VZW pushed an update of some kind. Flashing the stock ROM without doing a factory wipe would temporarily solve the problem but eventually the update would get pushed again and the whole thing would lock up again. The factory wipe + reinstall seems to have been the solution to the problem.

[SLIMICS 4.2+Semaphore] Boot loop, can I reflash?

Hi
I have had Slim ICS 4.2 working ok for a month or so. Yesterday it suddenly started to give FC to all apps, so I rebooted it. The only thing that changed was that, when trying to update the Adaway lists, it gave me an error and could not do it. From that moment, it was stuck in the Slim logo for three reboots. After that, it started a reboot loop, showing the semaphore logo and rebooting back again. I have managed to enter Recovery by connecting it to a USB cable, after some reboots it gets into it. Three button combo was working for Download Mode but not for Recovery.
Can I simply reflash Slim ICS, without doing a wipe? I donĀ“t want to lose my apps, at least not before backing the data conveniently. It would suffice to be able to boot and do a Titanium Backup, then move on to Slimbean or something. I still have the original zips I used to install it.
Thanks!

[Q] Help! Frozen on HTC One start up screen!

I created a nandroid backup in TWRP and then hit 'reboot system' and it's frozen on the 'HTC One' start up screen. I have tried the long press power to reset and doesn't work - still frozen. I then tried restoring the backup i made and same thing - frozen on start up screen. I can get to TWRP. I don't want to reset if possible! Options?? Thanks.
poczynek said:
I created a nandroid backup in TWRP and then hit 'reboot system' and it's frozen on the 'HTC One' start up screen. I have tried the long press power to reset and doesn't work - still frozen. I then tried restoring the backup i made and same thing - frozen on start up screen. I can get to TWRP. I don't want to reset if possible! Options?? Thanks.
Click to expand...
Click to collapse
i am to in same state...
Can u please Elaborate that how can you go in TWRP?
and also you can boot to Bootloader/Fastboot.
poczynek said:
I created a nandroid backup in TWRP and then hit 'reboot system' and it's frozen on the 'HTC One' start up screen. I have tried the long press power to reset and doesn't work - still frozen. I then tried restoring the backup i made and same thing - frozen on start up screen. I can get to TWRP. I don't want to reset if possible! Options?? Thanks.
Click to expand...
Click to collapse
reflash the rom without wiping
may not be of help but tonight I managed to get my HTC One stuck at boot logo / splash screen ...
I have TWRP but did not backup or even enter initially ...
Was due XPOSED framework - was talking as looking around in XPOSED, not 100% sure what I clicked in there but I think it was INSTALL on the framework itself ... it was already installed.
Before I could blink and think WTF did I just do - phone rebooted itself unannounced.
From there stuck at splash logo on boot.
Long story short using ADB I renamed /system/bin/app_process to ../app_process.old and then copied /system/bin/app_process.orig (backup made by XPOSED at install time I am assuming?) to /system/bin/app_process
Reboot and fine again.
I read somewhere during the above learning lesson that with S-ON with HTC One (I think it was this) the XPOSED system can be removed on restart or something like that, there was an alternative way to install / patch to prevent this.
Just thought would throw it out there in case you have XPOSED, possibly recently and it may have been zapped hence stuck like I was.
Long shot.
Best of luck.

Bootloop after backup

Been using the Toolkit 1.9.8 to root and unlock my att nexus 6. Seemed to work fine and have been running well for the past few days, however after a backup attempt (nandroid) the phone is stuck in a boot loop (spinning dots). Any tips to help me get it unstuck? I've rebooted into recovery and wiped the caches. I did successfully create a backup before it started looping so I'm trying to restore from that at the moment.
I just went and did a Nandroid too after running a few days fine after having unlocked and rooted. Now on my first boot I cant get the OS to load, stuck at the spinning dots splash screen too. I left it for about 20 minutes just to make absolutely sure it was stuck. I thought maybe it had to re-compile things or something with ART. IDK, it was a theory anyway.It seemed stuck for sure so I held down all buttons to force a turn off. I then booted into TWRP and restored my nandroid I just made, which I know shouldnt make a difference cause it is the same thing and I didnt wipe anything before anyway, just made a backup. Anyway, I restored the nandroid and tried to boot and it worked fine. Odd, but worth a try for you.

Stuck in 'Phone is starting...' screen

Hi all.
So this is quite strange (i think).
I managed to root my s20 fe 4g using magisk with the help of some people from here and a guide.
I have played around with it, installed some stuff, uninstalled some apps (using titanium backup) and was all well.
When I went to restart the phone to give it a clean break, it now wont load up again. Just gets stuck on the 'Phone is starting...' screen. Now this isn't a huge problem, i thought I couldjust flashthe stock firmware again and root the same way and perhaps it will be well. The problem is it wont boot into download or recoery because it is stuck in a cycle of trying to start itself. I can force it to restart by holding the vol- and power button, but that is the only combination that will make it restart, it instantly restarts before i can change the keys held to try and get it into download mode.
Does anyone know what I can do to try and remedy this so it will start again?
UPDATE:
I think i stupidly must have deleted the one ui launcher by mistake... Now I am trying to get an APK to the phone, but ADBdoesn't recognise it at the 'phone is starting' screen. My phon is at dead stage, so i can get it to boot into download now, but it doesnt seem to want to go into recovery, and i think its stock recovery, so not sure if ADB will work?
Any other suggestions to get the launcher apk pushed and installed?
if you can get download mode flash the rom again, hopefully you still have it from rooting.
don't use titanium backup to uninstall system apps. even using it to freeze apps can be a problem if it's not gonna boot up.
get a copy of a safe debloat list and stick only those listed packages that others have found to safe to deactivate.

Categories

Resources