Develop Bugs

[Q] Problems while Rooting a Galaxy Note II

Hey guys, I hate to make my first post in XDA forums asking noobilities but... welll..
Spoiler
I tried to root my Note not knowing that it would made me unable from further receiving upgrades from Samsung, so I'm in the disjunctive of finding a way to go back to zero, or to go on and install a new ROM (I've been looking at ProBam).
The problem is, when I first tried to root the cellphone, I used this guide:
"galaxynote2root"
But I guess their recovery was outdated, since when I tried to run it, after ODIN completed it's installation, the phone's screen went to the "Galaxy Note II" starting screen, then it started to shake glitchy, and turned-off.
The root worked, I had the Supersu and root apps worked fine. But the recovery failed. So I asked for help in a few amateur forums, and they told me unroot, and root back using CWM SuperUser and stuff.
Well, it didn't worked, while this time the reboot was fine, having the expected load-uo with the "cmd.ex"-like installation screen on the Note.
BUT. No root application works, nor CMD ROM manager, nor Titanium Backup, etc... Actually, I didn't even had a superuser... I downloaded Supersu again -since I had seen it work before- but it just keep crashing. All other apps kept asking for the Superuser authorization. Finally, I decided to press the unroot option of Supersu again to get ride of it, assuming I failed the root.
TL;DR
So, know, my question are, can I get ride of the binary counter trough a factory reset? If not, is there a safe way that doesn't implies "bricks"? At last, how could I have both the SuperUser and the recovery? what went wrong back there? Is there any more recent tutorial for rooting?

Triangle away will reset your boot counter.
Try to follow any of drketans guides for rooting unrooting.
Also mskips galaxy tool kit is what I use to root and install twrp.
Good luck
Sent from my GT-N7105 using xda app-developers app

[Q] Lost root, won't come back

So I'm not a complete and utter n00b here, as I've been rooting and installing CM for at least three years now on several different phones. But this problem vexes me...
Patient: SIII, formerly rooted and running CM10.1 just fine. A few weeks ago, I tried to install a 10.2 stable build, and it somehow took my root away. I tried every trick I knew how - installing the root files via Odin (many versions), via ADB, via Kingo Root...nothing. Absolutely nothing I try will get this thing to give me my root back, and the ads are starting to really get on my nerves.
My ticker says 15 attempted installs, but I don't think it's blocking me from rooting...is it? All the phones I've rooted I've never had a problem like this, where absolutely nothing will allow root to "take", such as it is.
Any thoughts or suggestions?
Thanks!

Wow, nothing? I figured someone would at least sigh heavily, berate me for not reading the forums completely, then point me to a thread where this has been discussed ad nauseum
Last night, I tried rooting with TWRP, CWM, every variant and trick I could find to get this thing to root for me, and while these things all seem to load fine, none of them give me my root access back. No one has any ideas?
Thanks!

help
im using rooted 4.3 stock rom in t999..
everytime i boot into recovery it says "fixed root"
any solve for this?????

Did you dirty flash CM10.2 over CM10.1? if so, it might have failed to write the partition completely/correctly. I would suggest to backup everything that you can (adb backup or similar) and then wipe everything then reflash fresh CM10.2.0 + GApps + SuperSU or Koush's Superuser flashable zip.

Can't get Note to boot.

Hey all. Fist off, sorry about the new account and posting here in the Q&A and not development, but let me explain. I have been a member of XDA for a few years- my main account(and only account until being forced to create this one) is andr0id23. However, I am unable to login to that account. I keep getting an incorrect password error message and am constantly locked out of my account. I have emailed the people who can help with this issue, but still not having any luck. They did reset my password(even though I knew my password), but that still doesn't work. I try it once but it says i have used up all my attempts and locks me out for what is supposed to be 15 minutes, but seems to be forever instead. But I digress, just wanted to explain why I am posting from a brand new account and in this section(new accounts are not allowed to post in development). Now on to my issues I am hoping someone can help with. I typed it up in notepad last night while waiting for my account to be accessible and am just going to copy and paste it:
Hi all, I was hoping to get some help on my Galaxy Note 8.0. It is model number GT-N5110. It was given to me by a friend, who likes
to try rooting his devices, but has no experience and is actually quite computer illiterate. When I received it it wouldn't boot up,
but only go do a screen that says something like "Downloading. Please do not power off". I have no idea what is on there as far as firmware
or custom ROMs.
I am pretty comfortable with Android development as far as flashing custom ROMs, rooting, unlocking bootloaders, etc, but haven't been active for
some time now. I have owned a Droid, Droid 2, HTC Incredible, Droid X, HTC Thunderbolt, and Motorola Xoom and have rooted,
unlocked, and/or installed custom ROMs on all of them, ass well as doing so on several devices that aren't mine. I have used "one click" type methods
as well as more hands-on adb methods. I just mention so to show that while I am far from an expert, I do have some experience.
But I am stuck on this tablet. I can boot into Download Mode and was able to flash CWM Recovery via Odin. In CWM I tried
wiping data, cache and Dalvik cache, but when I go to reboot I get a message saying the device is not rooted and would I like to root. It doesn't seem to do any
good. I did try rooting thru odin, and it said it was successful. I have also flashed the stock firmware thru odin, but am still not able to boot. The
closest I get is a boot loop. Also, Kies does not recognize my device.
So, I can boot into download mode and CWM Recovery(though I don't know if I am actually rooted
and it will be of any use), and Odin does recognize the device. I have tried flashing stock firmware to no avail. If anyone
has any suggestions, I would be greatly appreciative and definitely willing to try. I can give you any additional info you
request. I was thinking of flashing a custom ROM, but not sure as I don't know what the tablet is currently running. If anyone
has anything to try as far as flashing a ROM or firmware, a d/l link would be greatly appreciated if at all possible.
I have been having the worst luck with samfirmware or sammobile(two sites that are named something like that). I have spent
literally hours waiting for the downloads, and the 2 times i did get lucky, the files were messed up. Again, I would be
extremely greatful for any and all help.

Nashtar said:
Hey all. Fist off, sorry about the new account and posting here in the Q&A and not development, but let me explain. I have been a member of XDA for a few years- my main account(and only account until being forced to create this one) is andr0id23. However, I am unable to login to that account. I keep getting an incorrect password error message and am constantly locked out of my account. I have emailed the people who can help with this issue, but still not having any luck. They did reset my password(even though I knew my password), but that still doesn't work. I try it once but it says i have used up all my attempts and locks me out for what is supposed to be 15 minutes, but seems to be forever instead. But I digress, just wanted to explain why I am posting from a brand new account and in this section(new accounts are not allowed to post in development). Now on to my issues I am hoping someone can help with. I typed it up in notepad last night while waiting for my account to be accessible and am just going to copy and paste it:
Hi all, I was hoping to get some help on my Galaxy Note 8.0. It is model number GT-N5110. It was given to me by a friend, who likes
to try rooting his devices, but has no experience and is actually quite computer illiterate. When I received it it wouldn't boot up,
but only go do a screen that says something like "Downloading. Please do not power off". I have no idea what is on there as far as firmware
or custom ROMs.
I am pretty comfortable with Android development as far as flashing custom ROMs, rooting, unlocking bootloaders, etc, but haven't been active for
some time now. I have owned a Droid, Droid 2, HTC Incredible, Droid X, HTC Thunderbolt, and Motorola Xoom and have rooted,
unlocked, and/or installed custom ROMs on all of them, ass well as doing so on several devices that aren't mine. I have used "one click" type methods
as well as more hands-on adb methods. I just mention so to show that while I am far from an expert, I do have some experience.
But I am stuck on this tablet. I can boot into Download Mode and was able to flash CWM Recovery via Odin. In CWM I tried
wiping data, cache and Dalvik cache, but when I go to reboot I get a message saying the device is not rooted and would I like to root. It doesn't seem to do any
good. I did try rooting thru odin, and it said it was successful. I have also flashed the stock firmware thru odin, but am still not able to boot. The
closest I get is a boot loop. Also, Kies does not recognize my device.
So, I can boot into download mode and CWM Recovery(though I don't know if I am actually rooted
and it will be of any use), and Odin does recognize the device. I have tried flashing stock firmware to no avail. If anyone
has any suggestions, I would be greatly appreciative and definitely willing to try. I can give you any additional info you
request. I was thinking of flashing a custom ROM, but not sure as I don't know what the tablet is currently running. If anyone
has anything to try as far as flashing a ROM or firmware, a d/l link would be greatly appreciated if at all possible.
I have been having the worst luck with samfirmware or sammobile(two sites that are named something like that). I have spent
literally hours waiting for the downloads, and the 2 times i did get lucky, the files were messed up. Again, I would be
extremely greatful for any and all help.
Click to expand...
Click to collapse
I would download stock ROM and flash with Odin 3.07. There are a number of threads that explain the process. Here is one... http://forum.xda-developers.com/showthread.php?t=2728370&page=3
GT-N5110 & GT-N5120 - 64GB 633x on board, Status Official on SafeRooted OEM ROMs with Wanam Xposed and RootCloak. The only way to fly 8+ hours!
This badboy don't play with Play & Triangle away!

gooberdude said:
I would download stock ROM and flash with Odin 3.07. There are a number of threads that explain the process. Here is one... http://forum.xda-developers.com/showthread.php?t=2728370&page=3
GT-N5110 & GT-N5120 - 64GB 633x on board, Status Official on SafeRooted OEM ROMs with Wanam Xposed and RootCloak. The only way to fly 8+ hours!
This badboy don't play with Play & Triangle away!
Click to expand...
Click to collapse
I was never able to grab any downloads from SamMobile or SamsungUpdates. It just loads forever until it times out. I did, however, grab a stock firmware download from another thread. I flashed it with Odin 3.07 but it did nothing for me. I am attempting to download the files from the 2 sites again now. Hopefully I'll have better luck. Thanks

Idiot
Ok so I am a complete tool. I was able to get it going. I knew what to do, and was doing it, but was doing it wrong. The thread you linked made it dawn on me. I was able to flash the stock firmware through odin 3.7. Sorry if I wasted your time and I thank you wholeheartedly. Now time to root and have some fun :good:

[Q] CyanogenMod not getiing installed. SuperSU Crashing.

Hello All,
I am a beginner to all this stuff. I wanted to root my phone after seeing OnePlus One running on CyanogenMod. So, first I tried to directly install the Mod using the softwares downloaded from Cyanogen's website. But the software gave the error "Unsupported Firmware". Then I researched a bit on manually installing the mod. I followed the instructions.
- First I rooted my phone with Odin 3.09v
- Installed ROM Manger on my phone (Meanwhile the SuperSU app kept on crashing)
- Somehow I managed to install ClockworkMod (What I did was downloaded SuperSU apk, installed it again. It started working and then, not losing the chance I installed ClockworkMod).
- Then I tried to install CyanogenMod through ROM Manager
- My phone re-booted and then gave a error "Can't install package on incompatible data".
- I'm having the latest snapshot version on CyanogenMod.
- Then I left the things as it is. No rooting, unrooting, etc.
- So, now I tried to take backup of my current ROM, in case something happens at least I'll be having something with me to recover
- I used ROM Manager to take backup. But it gave the error "Can't create the image"
So, now I'm stuck between middle of nowhere. Please help me out to reach to some point.

svikramajit said:
Hello All,
I am a beginner to all this stuff. I wanted to root my phone after seeing OnePlus One running on CyanogenMod. So, first I tried to directly install the Mod using the softwares downloaded from Cyanogen's website. But the software gave the error "Unsupported Firmware". Then I researched a bit on manually installing the mod. I followed the instructions.
- First I rooted my phone with Odin 3.09v
- Installed ROM Manger on my phone (Meanwhile the SuperSU app kept on crashing)
- Somehow I managed to install ClockworkMod (What I did was downloaded SuperSU apk, installed it again. It started working and then, not losing the chance I installed ClockworkMod).
- Then I tried to install CyanogenMod through ROM Manager
- My phone re-booted and then gave a error "Can't install package on incompatible data".
- I'm having the latest snapshot version on CyanogenMod.
- Then I left the things as it is. No rooting, unrooting, etc.
- So, now I tried to take backup of my current ROM, in case something happens at least I'll be having something with me to recover
- I used ROM Manager to take backup. But it gave the error "Can't create the image"
So, now I'm stuck between middle of nowhere. Please help me out to reach to some point.
Click to expand...
Click to collapse
Ok, first I think your SuperSu is not working properly. Open the Supersu app to see if it needs to update binaries. If it continues to crash, go into recovery manually (not using rom manager) and flash the latest SuperSu. Wipe Cache, go to advanced and Wipe Dalvik. Reboot. Your phone will say "android is upgrading" for a bit. Once it's booted up, go back into the supersu app and see if it needs to update binaries, if so- let it update, if not- move on. Here's a link to download SuperSu 2.02
Go back into recovery manually and select backup and restore-> backup to sdcard (or sdcard1, external sd, is my preference) This will start the backup process.
Once that is done, you need to find the CyanogenMod file specific to your phone, then you can enter recovery and flash it.
If you have trouble entering recovery, you can flash a new one via recovery or with odin.

Hello absinthesummer,
I followed every instruction you told. Now I'm done till creating backup. The problem now I'm facing is this 'Status 7' error. It says "Can't install package on incompatible data.....". Now what to do?

Status 7 is a very specific error. It means your recovery is out of date. Get the absolute newest you can find and try again. This is good news though, you've got progress!
---------- Post added at 11:48 AM ---------- Previous post was at 11:46 AM ----------
Edit: flash the latest recovery you can find via Odin. You probably won't be able to do it in recovery while you're getting the status 7 error.

absinthesummer said:
Status 7 is a very specific error. It means your recovery is out of date. Get the absolute newest you can find and try again. This is good news though, you've got progress!
---------- Post added at 11:48 AM ---------- Previous post was at 11:46 AM ----------
Edit: flash the latest recovery you can find via Odin. You probably won't be able to do it in recovery while you're getting the status 7 error.
Click to expand...
Click to collapse
No, I've got the latest recovery. But I figured out the problem. It was with the package I downloaded. The CM 11 M9 version was giving errors. I researched and tried few fixes, but still it didn't work.
The fixes I tried :-
1. Deleting some coding lines from the updater-script file. But this fix gave the status 6 error.
2. Changing the updater-script file format to UNIX format. Then again it gave the status 7 error.
So, what I did, when I had no more brain to fix it, I downloaded the CM 11 M6 version and tried installing it. And VOILA! It worked. Then I updated it to M9 version through phone. Now it's working. Though it has some bugs. And some features are missing too that I wanted badly.

svikramajit said:
No, I've got the latest recovery. But I figured out the problem. It was with the package I downloaded. The CM 11 M9 version was giving errors. I researched and tried few fixes, but still it didn't work.
The fixes I tried :-
1. Deleting some coding lines from the updater-script file. But this fix gave the status 6 error.
2. Changing the updater-script file format to UNIX format. Then again it gave the status 7 error.
So, what I did, when I had no more brain to fix it, I downloaded the CM 11 M6 version and tried installing it. And VOILA! It worked. Then I updated it to M9 version through phone. Now it's working. Though it has some bugs. And some features are missing too that I wanted badly.
Click to expand...
Click to collapse
Awesome! I'm glad you got it working. You can also try comparing the two files to see what's different, or maybe swap the updater script. Maybe you'll be able to get the one you wanted working with a little modification

absinthesummer said:
Awesome! I'm glad you got it working. You can also try comparing the two files to see what's different, or maybe swap the updater script. Maybe you'll be able to get the one you wanted working with a little modification
Click to expand...
Click to collapse
Thanks to you. You too helped me in working it out!
But, I have some more questions
Question 1 : If I flash stock ROM on my rooted phone, will I receive the new updates? If yes, will I be able to install them via Kies on my phone without getting into any trouble?
Question 2 : If I install stock ROM of any other phone, say Galaxy S5, will it work on my phone properly without any problems? If yes, will I receive the updates for that too and able to install them via Kies? If no, is there any way to install it? Cause I have seen people using S5 ROM on Note 2.

First question the answer is yes. As long as you have the stock recovery and stock kernel (along with the stock rom) you will receive ota updates. You can use ota root keeper (an app) to keep root during an ota update. There are many people who choose to stay fully stock but root to get rid of bloatware & stuff. However, if you want to get ota, I recommend freezing the bloatware instead of uninstalling, because an ota usually replaces old bloatware with new bloatware and can sometimes abort the ota if those apps are missing... but keep on mind this is not always the case, only certain devices.
Second question, no you cannot. Roms from other devices have to be ported to be compatible. But if you look in the development forums, you can find many roms that are basically stock but have specific features from other roms, along with the system ui (ie S5, note 3, & so forth). These rom devs have ported either parts/features or full on roms to be compatible on our device. They are excellent! I recommend reading up them and if you see some you like, try them out!

absinthesummer said:
First question the answer is yes. As long as you have the stock recovery and stock kernel (along with the stock rom) you will receive ota updates. You can use ota root keeper (an app) to keep root during an ota update. There are many people who choose to stay fully stock but root to get rid of bloatware & stuff. However, if you want to get ota, I recommend freezing the bloatware instead of uninstalling, because an ota usually replaces old bloatware with new bloatware and can sometimes abort the ota if those apps are missing... but keep on mind this is not always the case, only certain devices.
Second question, no you cannot. Roms from other devices have to be ported to be compatible. But if you look in the development forums, you can find many roms that are basically stock but have specific features from other roms, along with the system ui (ie S5, note 3, & so forth). These rom devs have ported either parts/features or full on roms to be compatible on our device. They are excellent! I recommend reading up them and if you see some you like, try them out!
Click to expand...
Click to collapse
- Stock Recovery
- Stock Kernel
- OTA Root Keeper
- Bloatware
Well, to be honest, just right now I learned these new terms but know nothing about them. Can you please give me a brief description for these four terms so that when I do advanced search on them, I'd have a idea in my mind about what these are. It will make it easy for me to understand the advance things.
And I'm looking for S5 ROM for my phone. Let's see what I get.

One more question. I made a backup of my rooted stock ROM via latest ClockwordMod, manually. Now, if I reset the binary counter using Triangle Away and then wipe Cache and Dalvik and then flash my stock ROM which is located on my memory card and then after flashing I use SuperSU to unroot and then a factory reset (I don't know the method of factory reseting cause I'm confused. Whether to do it manually, like going into recovery mode or just from the phone settings. So please tell me this also.), will my phone be unrooted totally?
And sorry for bugging you so much. I hate to do that, but I don't want to take risk with my phone. So I am just collecting information. I hope so many queries are not a problem for you.

Ok...
You already know what a rom is. A kernel is a lower-level base. It controls the hardware. So when you do something on the interface, in the rom, it tells the hardware how to react. (Ie if you're playing music it tells which speakers to play and how loudly). The kernel controls almost everything you can't see, it relates to performance. Most stock kernels can be limiting as they underclock the cpu by a certain percentage. Because of this, people seek out custom kernels to max out their device's potential. Louder speakers, faster cpu, better graphics, etc. This is all stuff the kernel can optimize... but because you can change so many factors there is a risk of instability if you push your device too hard (max performance) or limit it too much (max battery saving).
Recovery is exactly what it sounds like. When you boot your device the very first screen that pops up is the bootloader. It's giving you time to boot in 3 different modes. The first mode, by doing nothing, is a normal boot into the rom/OS. The second mode, which you get to by one button combination, takes you to recovery. The stock recovery is very limited. It gives you the option to factory restore, wipe cache, update, or boot normally. Stock recovery only exists for emergencies, if your phone fails to boot normally. We have custom recoveries so we can do more stuff, flash custom roms and tinker with things. The third mode is download mode/Odin mode. This is the bootloader interface itself. It's the last resort for recovery if your recovery has been damaged or corrupted. It allows you to connect to Odin or kies and perform an emergency recovery of the device. If you damage your bootloader, your device is completely bricked.
So the order of operation is this:
Lowest level- bootloader
Second level- recovery
Third level- kernel
Fourth level- rom
Bloatware is all the pre-installed apps that your carrier adds to your phone. Most people don't use it, don't like it, and don't want it. That why we root. Without root we basically are just guest users of the device. With root we become the administrators of the device. Until you root, your carrier has admin rights over your phone (to use windows terms).
When you receive an ota update, your carrier can make it to where the update won't proceed if their pre-installed apps have been removed (although this isn't always the case). Additionally, the update package itself checks the integrity of the device. It checks recovery, kernel, and rom. If any have been altered, it will not proceed because it could cause conflict and potentially brick your device. That's why those things have to be stock.
Ota root keeper is simply an app that backs up your superuser rights before an update and restores them after its done.
You should be able to find plenty of roms with S5 features. I'm using one that makes my device fully like an S5 (my device even thinks it is an S5 and every app identifies it as such) I can think of at least 2 others as well. There's plenty to choose from, and if you see a rom you like but it's mudding a particular feature, you can probably find that feature as a stand-alone installation in the forum's themes & apps section. Just about every feature of S5, S4, and note 3 has been ported to this device, so look around!
Also, for future reference, if someone helps you on the forum, hit the thanks button instead of saying it. I don't mind either way, but some people get annoyed and will stop helping them if they don't hit that button lol. It's silly, but it's part of "forum decorum"
---------- Post added at 12:54 AM ---------- Previous post was at 12:44 AM ----------
svikramajit said:
One more question. I made a backup of my rooted stock ROM via latest ClockwordMod, manually. Now, if I reset the binary counter using Triangle Away and then wipe Cache and Dalvik and then flash my stock ROM which is located on my memory card and then after flashing I use SuperSU to unroot and then a factory reset (I don't know the method of factory reseting cause I'm confused. Whether to do it manually, like going into recovery mode or just from the phone settings. So please tell me this also.), will my phone be unrooted totally?
And sorry for bugging you so much. I hate to do that, but I don't want to take risk with my phone. So I am just collecting information. I hope so many queries are not a problem for you.
Click to expand...
Click to collapse
You're fine, I don't mind answering your questions. Yes, you can unroot fully in the way you just mentioned but you don't even have to go through all the trouble of factory reset. Just unroot in the app. The app can be uninstalled afterwards via the play store.
You can factory reset either way, the same commands are given no matter which way you go about it. But it can be more efficient to do it from recovery because when you do it from the rom it has to create a wipe script for when it reboots, and it has to shut down the rom first. If you do it from recovery it doesn't have to anything, the rom isn't running and it can execute the wipe command immediately. (The wipe command is wipe /data /cache etc)

Thanks again for all that great info!
Questions : Is there no way to fix the Bootloader if it gets damaged by chance? And which S5 ROM are you using?

svikramajit said:
Thanks again for all that great info!
Questions : Is there no way to fix the Bootloader if it gets damaged by chance? And which S5 ROM are you using?
Click to expand...
Click to collapse
If you damage the bootloader it's a hard brick and you would have to send it in for jtag services (this is a low level emmc chip flash service) The bootloader won't get damaged unless you do something to corrupt it. If you ever feel the need to flash a new bootloader, do it via Odin, never recovery! If you remember that you should be fine.

svikramajit said:
Thanks again for all that great info!
Questions : Is there no way to fix the Bootloader if it gets damaged by chance? And which S5 ROM are you using?
Click to expand...
Click to collapse
I meant to tell you I'm using DN3 rom. It has an aroma installer that lets you choose whether you want an S5 ui, a note 3 ui or a mixed ui. Choosing S5 ui & S5 build prop allows your device to work with S5 apps & it looks just like an S5. It's not the only rom out there, but it's beautiful, fast, and stable & the team works hard on it.

absinthesummer said:
I meant to tell you I'm using DN3 rom. It has an aroma installer that lets you choose whether you want an S5 ui, a note 3 ui or a mixed ui. Choosing S5 ui & S5 build prop allows your device to work with S5 apps & it looks just like an S5. It's not the only rom out there, but it's beautiful, fast, and stable & the team works hard on it.
Click to expand...
Click to collapse
Hey absinthesummer!
I tried to unroot my phone with the method I told you. But in the restore option, I am stuck at 'Checking MD5 Sums..'. What to do now?

MD5 checking takes forever! You have to wait it out. Most recoveries offer a way to turn it off. You shouldn't have to factory reset though, just click unroot in the super su app and then uninstall the app from the play store.

absinthesummer said:
MD5 checking takes forever! You have to wait it out. Most recoveries offer a way to turn it off. You shouldn't have to factory reset though, just click unroot in the super su app and then uninstall the app from the play store.
Click to expand...
Click to collapse
I waited and the system was restored. But I got an error on 'Restoring Data'. I rebooted the phone and now it's showing glowing Samsung logo from like 3-4 minutes.

I've seen that before. Can you get back into recovery? You may have to flash stock in Odin, flash recovery and then do the Restore again. Data got messed up.

absinthesummer said:
I've seen that before. Can you get back into recovery? You may have to flash stock in Odin, flash recovery and then do the Restore again. Data got messed up.
Click to expand...
Click to collapse
I'll try removing the battery now. Let's see what happens.

Ok if you can get into recovery, do a fresh flash and then try to restore again. And see if it offers a way to turn off MD5 checking. That's why I use philz or twrp, they offer that and move much faster through MD5 check by default.
---------- Post added at 11:13 AM ---------- Previous post was at 11:12 AM ----------
If you still fail on data, flash stock in Odin, flash custom recovery, then you should be able to enter recovery and have a successful restore.

Bootloop, how to download stock for TWRP

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.