Is there any point in twrp backups, I presume you cant go back after updating rom, just got a max 3, any advice appreciated.
Thanks
The lack of answers tells me either no one knows or hasn't tried.
Related
To begin, let me assure you I've read through every forum post I can find regarding this issue and none seem related, or are too old to apply at this time. If I am mistaken I apologize and would appreciate someone pointing me in the correct direction.
I upgraded to 4.2.1 (Shiny). I have some issues so I want to restore my CWM backup of CM10. Since I upgraded and apparently did CWM as well, it is not letting me restore the old backup, giving me the "error while restoring /system" message.
It appears from researching here that the solution is to downgrade CWM, but I am unable to find a download site to get older versions of CWM anywhere. All links that have been posted here are no longer valid ("Forbidden 403"). Any ideas would really be appreciated.
Another possible cause is I updated the bootloader when I went to 4.2.1, is it possible that is causing the problem? If so, which bootloader should I replace it with?
Any help would be appreciated. Thank you very much.
Recently, I have been introduced to Android Rooting and I have successfully rooted my phone with Towelroot. My friend installed Cyanogenmod 11 on his Galaxy S3 the other day and I have been having many problems doing the process myself. I have ripped xdadevelopers to pieces trying to find a solution, but nothing has ever been simple enough, well really efficient enough to fix my problem.
I have ROM Manager installed on my device and the latest CWM Recovery and when I get to the "Recovery" mode it does not give me all the options a normal "Recovery" screen would give me. I can not backup my current stock rom because there is no option. In doing this I accidentally wiped my phone and had no way to recover, so I lost a lot of temporary things, very frustrating.
Basically what I need to know is how to get CWM Recovery to work on my device, etc. Also I forgot to mention before that FreeGee messes up too. It says something about "loki" or something. I am sick of trying several methods that fail in the end. If you can tell me how to get CWM Recovery to work on my phone. I do have an SD Card and my phone is rooted. Please help me! I apologize if all the information is not present, but if you need to know anything specific I would be more than happy to answer your question!
RyeM8 said:
Recently, I have been introduced to Android Rooting and I have successfully rooted my phone with Towelroot. My friend installed Cyanogenmod 11 on his Galaxy S3 the other day and I have been having many problems doing the process myself. I have ripped xdadevelopers to pieces trying to find a solution, but nothing has ever been simple enough, well really efficient enough to fix my problem.
I have ROM Manager installed on my device and the latest CWM Recovery and when I get to the "Recovery" mode it does not give me all the options a normal "Recovery" screen would give me. I can not backup my current stock rom because there is no option. In doing this I accidentally wiped my phone and had no way to recover, so I lost a lot of temporary things, very frustrating.
Basically what I need to know is how to get CWM Recovery to work on my device, etc. Also I forgot to mention before that FreeGee messes up too. It says something about "loki" or something. I am sick of trying several methods that fail in the end. If you can tell me how to get CWM Recovery to work on my phone. I do have an SD Card and my phone is rooted. Please help me! I apologize if all the information is not present, but if you need to know anything specific I would be more than happy to answer your question!
Click to expand...
Click to collapse
Have you tried installing the recovery from G.Pro Recovery first? Freegee will not work for me, giving me similar errors, until I first do that. See the to the Bountyman G3 v4.x thread under 'Optimus G Pro Android Development' for more info. Works for me every time (though I choose TWRP; friggin' *hate* CWM).
I picked up a sprint htc one m9 today. unfortunately no stock OS and no SD CARD with backup either. I booted into twrp but i can not do anything. everything fails. i tried to flash a rom and its a no go. I am stuck and have no idea what to try after looking for hours.
I have no OS
I can boot into twrp
twrp does not allow me to do anything FAILS on every operation.
zwp1990 said:
I picked up a sprint htc one m9 today. unfortunately no stock OS and no SD CARD with backup either. I booted into twrp but i can not do anything. everything fails. i tried to flash a rom and its a no go. I am stuck and have no idea what to try after looking for hours.
I have no OS
I can boot into twrp
twrp does not allow me to do anything FAILS on every operation.
Click to expand...
Click to collapse
Foremost: ugh. Sorry man - that sucks.
So it sounds like your best option would be to get an sd card and apply a RUU from there. Flippy498's Google Sheet is a great resource for where to get them and how to use them.
You might be able to use the Windows-executable RUU directly from Sprint. I'm pretty sure you'd need to be in download mode when you ran it though. It's not as straightforward as the sd card method, but they're usually my first fallback.
Keep in mind that both of these options are destructive - your phone will be brought to a factory state (stock firmware, recovery) and anything on the phone's internal memory will be wiped.
It might be worth exploring why TWRP keeps failing. If we could solve that, you could install the ROM of your choice and not worry about RUUs. But that's definitely more work and probably not necessary if you're not trying to save anything. Once the RUU has been successfully applied, you can just unlock the bootloader anew, install TWRP, and do whatever you want from there.
Thanks a ton that fixed it!
zwp1990 said:
Thanks a ton that fixed it!
Click to expand...
Click to collapse
Wonderful! Enjoy your new phone!
(If you're satisfied with the resolution, the convention in this forum is to mark a thread 'solved' in the title when an issue is resolved. This'll help folks know where to direct their help.)
No OS installed. I have twrp installed. So literally when i turn it on it goes directly into recovery menu. Apparently I have no back up or restore point. This is a Sprint galaxy note 4. Does anyone have any suggestions. I have been looking for a factory reset firmware somewhere online cant find one. Funny thing is my wife has the same exact phone. I thought making a back up and restore point for her phone would work on mine, but it didnt lol. Please I would be very grateful for help.
Hello, you could get the official software and use odin to get it back all the way to stock, or you can also just flash a custom rom since you already have twrp. To install a custom rom, all you need to do is download the rom and place it on a micro sd card, boot into twrp, and flash the rom from the micro sd.
Thank you for your reply how ever my trouble is finding an OS that works for my note 4 sprint device. I have downloaded dozens and dozens of different roms and so called " factory firmware" but seem to have no lucks. i have the recovery software installed twrp. when i go into there and try to load rom i still get error that says no os installed..
Thanks for the input i will close this thread now. my problem was not being patient at the bootload screen. I automatically assumed that something was wrong because it was stuck at the sprint spark yellow screen how ever little did i know a little bit of patients would have saved me numerous amounts of hours of research. Lost sleep, called off of work, and canceled weekend plans due to a little lack of patience. Well you live and you learn i really appreciate you taking time out to reply.
Hello, I recently tried to root my device, I succeed in doing so but it was systemless root, I didn't know anything at the time so I tried different versions of supersu, now my phone won't boot, only fastboot and recovery works,
I visited a thread https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
but I don't know which one is my stock and I'm afraid to mess it up even more,
image uploaderG]
Can you please advise me how to recover my basic stock system :F
I remember that my installed android before it stopped working was 6.01 afaik
Your Stock is 6.12.111.4
option 1:
TWRP backup - https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
on post #3
Make sure to use TWRP 3.x.x.x not your current one as it seems you use the outdated version.
option 2 :
RUU - https://www.androidfilehost.com/?fid=24399965296001026
follow this guide but use the above RUU - https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Thank you, my TWRP is the latest one now because my system sort of worked when I first rooted it but when I noticed that it's systemless I tried to flash system one and my phone didn't work as intended (couldn't download things on it and some other things didn't work) that's when I flashed newest twrp and newest super su and factory reset stopped working as of now and it's stuck on bootloop. Downloading that recovery, wish me luck .
Edit: it works now, thanks
One additional issue arose - my folders seem to be really wrecked, can't download anything from updates to system apps to downloading apps from playstore and even downloading apps regularly, when I made sd card my internal card I was able to download opera and wanted to select default download folder but couldn't pick any/make any and the folders were not recognizable for me (no data folder for example)
edit 2: I probably fuked up permissions too last time, fix context in twrp seems to have fixed the issue
Radenz said:
that's when I flashed newest twrp and newest super su and factory reset stopped working as of now and it's stuck on bootloop.
Click to expand...
Click to collapse
Couple words to the wise:
1) Always state exact versions numbers (TWRP, SuperSU, etc.) instead of just saying it the "latest". I've seen a lot of cases, where folks ensure us they are on the "latest" and it turns out when prompted for the actual version number, they are using something from 2 years ago!
In general when posting here, it's always best to give as much detail and specific info as possible. Vague descriptions, lack of details, and assumptions are always going to hinder more than help.
2) Always make a TWRP backup of your stock ROM before doing any mods like root or custom ROM. As you now see why, things don't always go as intended. Luckily, ckpv5 maintains a collection of stock backups. But you should already know how to revert to stock and be equipped to do so, before doing the mods. Not waiting for that "panic" moment when you need it, and can't figure it out.
I'm surprised how many folks here jump into rooting, flashing custom ROMs without leaving themselves an "escape plan" of knowing how to get back to stock. Maybe it's just my personality, but I can't fathom doing any of these things without knowing beforehand how to fix them, restore stock, etc.
Thanks for advice, to be honest 3 days ago I didn't know what rooting was and searched for "root htc one m8" and got it done by a site from 2014 with a multitool that had outdated soft. What I lacked then was big red uppercase notice how to do backup because most first time rootings end up badly.
Radenz said:
Thanks for advice, to be honest 3 days ago I didn't know what rooting was and searched for "root htc one m8" and got it done by a site from 2014 with a multitool that had outdated soft. What I lacked then was big red uppercase notice how to do backup because most first time rootings end up badly.
Click to expand...
Click to collapse
Yeah, completely understand if you are new to this; and we all had to start somewhere, at some time. Consider it lessons learned for next time.
A lot of folks skip the step of making a backup (before root, etc.). And also a lot of guides, YouTube tutorials, etc. neglect this step (which is something I cannot understand). So it's an honest mistake, and I'm definitely not saying that it's your fault that it wasn't done.