Related
I'm obviously new to this so bare with me.
I just rooted my Sprint HTC Hero and the first thing I would like to do is use it to tether. I've tried both versions of Android_wifi_tether (1.52, 1.6) but have had no luck in getting it functional. Basically; It broadcasts the signal (I'm at work so the only way to test it was with a Macbook) just fine. The Macbook even connects to it and my phone shows "3KB down 7.8KB up" meaning it detected something has connected. Once that happens nothing else works. The Macbook indicates it has no internet connection.
I was wondering if anyone has been able to get this to work? I'm a little hesitant on installing a custom ROM because it seems like a lot of work and I'm not too knowledgeable when it comes to Linux.
Also, can my phone still be updated or is that still unkown? If I install a root app and the update kills root does that mean I lose it entirely or just for anything I try to install post update?
As a side note: Someone should make a post with step by step guides to follow. What I mean by this is put the guides in chronological order.
1) Root your phone (guide link)
2) Run Nandroid backup (guide link)
3) etc.
Anyway, really appreciate the work! This is exciting.
fatkitty420 said:
I'm obviously new to this so bare with me.
I just rooted my Sprint HTC Hero and the first thing I would like to do is use it to tether. I've tried both versions of Android_wifi_tether (1.52, 1.6) but have had no luck in getting it functional. Basically; It broadcasts the signal (I'm at work so the only way to test it was with a Macbook) just fine. The Macbook even connects to it and my phone shows "3KB down 7.8KB up" meaning it detected something has connected. Once that happens nothing else works. The Macbook indicates it has no internet connection.
I was wondering if anyone has been able to get this to work? I'm a little hesitant on installing a custom ROM because it seems like a lot of work and I'm not too knowledgeable when it comes to Linux.
Also, can my phone still be updated or is that still unkown? If I install a root app and the update kills root does that mean I lose it entirely or just for anything I try to install post update?
As a side note: Someone should make a post with step by step guides to follow. What I mean by this is put the guides in chronological order.
1) Root your phone (guide link)
2) Run Nandroid backup (guide link)
3) etc.
Anyway, really appreciate the work! This is exciting.
Click to expand...
Click to collapse
Currently the only phones that have wifi tethering working are the ones who installed MoDaCo's ROM...something in there is configured differently to allow it to work.
thecodemonk said:
Currently the only phones that have wifi tethering working are the ones who installed MoDaCo's ROM...something in there is configured differently to allow it to work.
Click to expand...
Click to collapse
How functional is the ROM?
The one thing I'm scared of is that if I install a ROM I'll be dependent on this community to make future things work?
I mean, can you still access the Market? What about future updates? Will applications I purchased already still be available?
Like I said, I'm still fairly noobish.
fatkitty420 said:
How functional is the ROM?
The one thing I'm scared of is that if I install a ROM I'll be dependent on this community to make future things work?
I mean, can you still access the Market? What about future updates? Will applications I purchased already still be available?
Like I said, I'm still fairly noobish.
Click to expand...
Click to collapse
No sweat! If you look at my join date and postcount, you can see I'm not exactly the veteran around here either.
The MoDaCo ROM doesn't modify very much yet...just adds functionality (it's not the heavily optimized kernel that the GSM users have for example). I'm finding it fairly stable...there's a few quirks but those have fixes pretty easily found so far.
I can still purchase from the market...the stuff you purchased already is tied to your google account, not your phone. I bought Docs2Go before I rooted and flashed and I was able to redownload and install without any hassle or added cost.
On a custom ROM, future updates do depend on the person who is building the ROM. However, MoDaCo has proven pretty reliable thus far in keeping up with releases so it's a bit of a trust thing, do you trust MoDaCo to continue that trend or would you rather place your trust in the manufacturer? (It's a preference thing and willingness to risk either way).
The upside is that once you root to a recovery image (Not even changing your OS), you can take a Nandroid backup of your phone, which is an image you can drop back on there to get back to stock/manufacturer spec (as if you never left).
Any changes to your phone since the backup will not show up but that's kindof the risk.
thecodemonk said:
k on there to get back to stock/manufacturer spec (as if you never left).
Any changes to your phone since the backup will not show up but that's kindof the risk.
Click to expand...
Click to collapse
This is somewhat confusing for me. My phone is currently rooted. If I restore it factory default will it still be rooted?
If not,
Then should I restore to factory default first, take a Nandroid back up (this looks difficult), then root my phone?
The recovery image is basically replacing the "Factory reset" image, right?
fatkitty420 said:
This is somewhat confusing for me. My phone is currently rooted. If I restore it factory default will it still be rooted?
If not,
Then should I restore to factory default first, take a Nandroid back up (this looks difficult), then root my phone?
The recovery image is basically replacing the "Factory reset" image, right?
Click to expand...
Click to collapse
Ah ok...the recovery image is like a second mini OS you are booting into that has menu options and specializes in updating your phone with a custom ROM, running Nandroid for backups, and enabling you to mount your SDCard to your computer, so installing that doesn't actually do anything to your phone's running OS.
Nandoid takes a backup of the phone's OS (the one you use every day) as it is right now. It places the backup onto your sdcard under a folder called "nandroid" (where you can take a copy of it and put it on your computer to be safe). So whenever you Nandroid your phone, it's taking a snapshot of how your phone is currently configured (the whole thing) and if you restore from that three weeks from now after doing a bunch of things...it restores to the phone as if you hadn't done anything to it in those three weeks.
So to make an example: if you take a backup of your phone right now (rooted, right?) and then you do a bunch of things to it...then restore from that backup, it's as if you didn't do any of those things you did since the backup (but it will still be rooted since you backed up a rooted phone).
Second Example: If you nandroid your phone when it's running MoDaCo's ROM...when you restore it, it will be running MoDaCo's rom and configured however it was configured then.
I wouldn't worry about trying to get to factory default first...HTC has an official utility that can get you back to the state your phone was in when you first openned it out of the box. (http://forum.xda-developers.com/showthread.php?t=559622)
thecodemonk said:
Ah ok...the recovery image is like a second mini OS you are booting into that has menu options and specializes in updating your phone with a custom ROM, running Nandroid for backups, and enabling you to mount your SDCard to your computer, so installing that doesn't actually do anything to your phone's running OS.
Nandoid takes a backup of the phone's OS (the one you use every day) as it is right now. It places the backup onto your sdcard under a folder called "nandroid" (where you can take a copy of it and put it on your computer to be safe). So whenever you Nandroid your phone, it's taking a snapshot of how your phone is currently configured (the whole thing) and if you restore from that three weeks from now after doing a bunch of things...it restores to the phone as if you hadn't done anything to it in those three weeks.
So to make an example: if you take a backup of your phone right now (rooted, right?) and then you do a bunch of things to it...then restore from that backup, it's as if you didn't do any of those things you did since the backup (but it will still be rooted since you backed up a rooted phone).
Second Example: If you nandroid your phone when it's running MoDaCo's ROM...when you restore it, it will be running MoDaCo's rom and configured however it was configured then.
I wouldn't worry about trying to get to factory default first...HTC has an official utility that can get you back to the state your phone was in when you first openned it out of the box. (http://forum.xda-developers.com/showthread.php?t=559622)
Click to expand...
Click to collapse
Great, this really clarified things.
I love technology but, like most of these things, it's very overwhelming at first.
Afternoon, y'all. Let me cut to the chase:
My objective: To install the custom ROM located at this link (http://forum.xda-developers.com/showthread.php?t=2591895). I don't want to lose my root functionality/benefits by taking the OTA 4.3 update (Titanium, Greenify, etc), but I want to be able to use apps like DashClock which don't work with 4.1.2.
My phone specs:
Model SCH-i535
Android Version 4.1.2
Baseband Version i535VRBMF1
Kernel Version 3.0.31-1152558 ([email protected] #1)
Build Number JZO54K.i535VRBMF1
Hardware version 1535.10
Phone IS ROOTED, and I used the Casual root tool located here: http://forum.xda-developers.com/showthread.php?t=2332825
[*]Apps I am using during this process (specific to root, backup, etc): Titanium Backup Pro (full backup made, including update.zip), ROM Manager, Root Checker, SuperSU
[*]Although I had a ton of frozen bloatware/system apps (all safe, I checked thoroughly before I did this a few months ago), I have unfrozen everything.
Previous experience: Before this S3, I had an HTC Thunderbolt which I successfully rooted and installed a custom ROM onto. So I have *some* experience, but I am no zen master.
Problems I've run into this time around:
Phone is rooted, but I am pretty sure the bootloader is NOT unlocked. Rootchecker confirms that the phone is rooted, and apps that require root access work just fine.
Related to the above point, when I run Casual (as I did just a few minutes ago), this is the log that appears in the window:
-Waiting for device...
Waiting for ADB device connection. When your OS recognizes the device, we will continue. Don't touch anything.
-Device found.
-Pushing exploit...
4298 KB/s (1283460 bytes in 0.291s)
-Pushing root tools...
2990 KB/s (96260 bytes in 0.031s)
4692 KB/s (1867568 bytes in 0.388s)
5424 KB/s (1872015 bytes in 0.336s)
-Rooting phone...
-This may take a few minutes.
Failure.
-installing superuser to system partition
-once root is confirmed you can flash the Insecure aboot
done
-Script Complete
This "FAILURE" is what catches my eye. I can't tell if the phone is "half-rooted" (no unlocked bootloader), or if it's just that Casual sees that my phone is already rooted so it doesn't bother trying to do it again (which is fine, I can understand that point, if it is true).
ClockworkRecovery Mod fails when trying to backup my current ROM (unlocked TouchWiz, no custom ROM installed yet). When I push "Backup Current ROM" in ROM Manager, it reboots the phone (crashes) and puts it into recovery mode, but there's nothing to recover. So my screen goes to the Yellow Triangle of Death screen and gives me a red error message in the top-left corner saying "secure kernel: fail". I had to reboot the phone using Volume Down+Home+Power, and it goes right back to a normal startup. This is what leads me to believe my bootloader is still locked, and I can't find a way to overcome that. I NEVER see the CWM menu to wipe cache, data, etc.
Titanium Backup failed to backup my SMS messages (everything else went fine). It gives me an XML error right away. I used a different app to back them up, which gave me no problems. Not sure if this is related to the larger problem, but I figured it was worth mentioning.
What I'm asking: I'm wanting to make sure that I've got all my bases covered. I know I've done my backups through Titanium Backup correctly, but I do remember that with my Thunderbolt I had to copy down some ID numbers related to the phone so I could sync it after installing a custom ROM (I haven't read any mention of this with the S3, so I'm a bit worried that I'm missing something).
CWM not working correctly is what's throwing me off- I don't want to get my phone stuck in bootloops like before. I want to backup my current setup, clean the cache/data/etc, install the ROM and then restore my apps and data.
I want to avoid resorting to ODIN and putting my phone back to stock (and risk getting the OTA 4.3 update, which I refuse to do) to be able to load this ROM, but if that's what I need to do, then so be it.
Any help, insights, etc would be immensely appreciated! I've read countless threads over the last few months (and especially in the last week), and the fact that there isn't much documentation regarding MF1 when it comes to installing bootchains and ODIN makes me feel like I'm groping in a dark a bit.
Many thanks!
Wow, long post.
Sounds like you're rooted, so download ez unlock v 1.2 to flash the insecure aboot. Then flash the rom after.
You should be good to go after that.
Edit : additionally, I wouldn't restore any apps or data from tibu in this case, going from 4.1.2 to 4.3 changes quite a bit of file structuring and could cause problems.
Sent from my SCH-I535 using Tapatalk 2
Thanks for the reply! And yes, sorry for the long post- I opted to be thorough and give all the relevant information up front instead of playing a cat-and-mouse game of having to post repeatedly with information I could've posted at the beginning.
I heard about EZ Unlock but wasn't sure if it was still appropriate to use in this case. Per your instructions, I will sideload the APK and make magic happen from there.
I DID encounter something new just about an hour ago- I used Casual but I got no errors this time. Hopefully that is a sign of good things to come.
And thanks for the heads up about TiBu backups not working well- that right there saved me a LOT of headaches, I'm sure.
This being the case, however, how would I link my device to Verizon/Google if no data is restored at all from the backup, like account information and such? And would I still be able to restore my SMS/call log (they're in an XML file, not in app data)?
Again, many thanks!
DuoDSG said:
Thanks for the reply! And yes, sorry for the long post- I opted to be thorough and give all the relevant information up front instead of playing a cat-and-mouse game of having to post repeatedly with information I could've posted at the beginning.
I heard about EZ Unlock but wasn't sure if it was still appropriate to use in this case. Per your instructions, I will sideload the APK and make magic happen from there.
I DID encounter something new just about an hour ago- I used Casual but I got no errors this time. Hopefully that is a sign of good things to come.
And thanks for the heads up about TiBu backups not working well- that right there saved me a LOT of headaches, I'm sure.
This being the case, however, how would I link my device to Verizon/Google if no data is restored at all from the backup, like account information and such? And would I still be able to restore my SMS/call log (they're in an XML file, not in app data)?
Again, many thanks!
Click to expand...
Click to collapse
Don't be sorry for the long post, much better to be detailed and explain as much as you can. Shows you did some research before asking. I wish everyone researched that much before posting.
Ez unlock is great to use in this case, it will brick your phone if you're on 4.3.
You can always restore your contacts from googles database, as far as restoring call logs and sms messages you should be OK. But if you encounter any lag or bugs it could have something to do with that.
Sent from my SCH-I535 using Tapatalk 2
All right, so I followed your instructions. I sideloaded EZ Unlock, which did the trick, and then I went into CWM Recovery, wiped the data, cache and dalvik.
Then I went ahead and loaded the ROM zip from the SD card, and VOILA! Without a hitch. The phone is snappier than EVER and it's just a matter of downloading the apps I want to again from the play store. Even the data speeds--whether on WiFi or 4G--are blazing fast, I never encountered speeds like this, even when I first got my phone stock from Verizon.
I was pleasantly surprised that my phone didn't have an identity crisis (as had happened when I rooted and loaded a custom ROM on my HTC Thunderbolt years ago). Right away it knew my phone number, and my Google account sync was flawless.
So far, extremely impressed. And I can breathe a sigh of relief that I OVERprepared for this instead of missing something crucial (so far! fingers crossed). Before, under 4.1.2, I used a combination of Greenify, freezing unwanted bloatware/system apps and Xposed Framework to get my phone to do incredible things, and I look forward to seeing how everything works under 4.3 without Verizon's slimy tentacles all over my phone again.
I will continue to update the thread as I run into issues or curious info that might be useful to anyone considering going through the same process. Surely my experience and effort can allow someone else to have an easier time than I did!
Thank you again for your help- it may have seemed simple, but the direction and reassurance you gave was all the help I needed to make it happen and not blow up my phone
Hey there team. I've been a long time lurker here and might not have made many posts. Getting this phone and given my time flashing, rooting, and following guides here, I really want to start getting in on the conversations and discussions. Let me go through with what happened to my last LG Volt...
I had successfully rooted the device using towelroot and been playing around with the usual root access apps. I had superuser, busybox, etc. What I came across as a problem with the device was it's RAM usage on a lot of apps and the problem was largely just OS (after purging a lot of apps off the device). The biggest problem I was having was with Skype crashing and ending calls anytime you switched out of the Skype app itself.
Being the idiot I am, I began looking into possibly using SWAP memory to try to extend my RAM a little to see if I could correct what Skype was doing (assuming it was a RAM issue, which, now thinking about it, I don't think it was because my EVO V worked fine [On custom roms granted]). So I tried doing some swap stuff and it overall just would not go. I figured it was a KitKat issue involving the SD Card and how the file structure on the LG Volt seemed to handle SD related stuff, all going to emulated memory. So. I decided it wasn't worth the trouble and research anymore, and considering not too much work had been done on the Volt yet, I decided to give up that campaign and wait for more research to get done.
In the mean time, I told the phone to do a factory reset so I can start back fresh and go about using the device normally. This might have been where I made a mistake. I told the device to factory reset and format everything through the Android OS instead of booting into the stock recovery and telling it to do a factory reset. The phone shut off and never came back. I was not able to get it to charge, I could not enter LG Download Mode, I couldn't get into the recovery, absolutely nothing. Tried seeing if I could use the LG Mobile support tool to push anything to the phone since my computer could still see the phone connected... No luck.
So, my questions to the team here on XDA is:
1. What exactly happened to cause the phone to start the factory reset, but, lose everything? I could only assume that the phone kicked the system, data, boot, recovery, and... well.. everything off and fried it's memory. I assume it had to do with what I was trying to do with swap memory and something getting seriously messed up.
2. More specific on what the phone did after, it would not turn on, charge, go to recovery, or download mode. It was completely unresponsive. Would there have been a way to resurrect this phone back from the dead that I wasn't able to find after all the looking and research I had done?
3. With the new LG Volt I recieved from Virgin, how safe would you say things would be to go about rooting again and being more careful with my apps while I wait or get involved with some of the future ROM development for the device?
4. Is there something with how LGs recovery and download partitions are set up that would cause these to be unable to function? Or something that is particular to the LG Volt?
Finally, 5. I noticed that the work done and the team researching the Volt right now have managed to get an unlocked bootloader and a custom recovery that works. Would it be safe with the research done now to go about unlocking and flashing the custom recovery on?
These questions all take into account common knowledge stuff such as, the potentially to brick a phone again is always there and to continue doing as much research and reading as I can to know what I'm doing with the device accurately. Hope my questions can be answered here, until then, cheers gentlemen.
marth141 said:
Hey there team. I've been a long time lurker here and might not have made many posts. Getting this phone and given my time flashing, rooting, and following guides here, I really want to start getting in on the conversations and discussions. Let me go through with what happened to my last LG Volt...
I had successfully rooted the device using towelroot and been playing around with the usual root access apps. I had superuser, busybox, etc. What I came across as a problem with the device was it's RAM usage on a lot of apps and the problem was largely just OS (after purging a lot of apps off the device). The biggest problem I was having was with Skype crashing and ending calls anytime you switched out of the Skype app itself.
Being the idiot I am, I began looking into possibly using SWAP memory to try to extend my RAM a little to see if I could correct what Skype was doing (assuming it was a RAM issue, which, now thinking about it, I don't think it was because my EVO V worked fine [On custom roms granted]). So I tried doing some swap stuff and it overall just would not go. I figured it was a KitKat issue involving the SD Card and how the file structure on the LG Volt seemed to handle SD related stuff, all going to emulated memory. So. I decided it wasn't worth the trouble and research anymore, and considering not too much work had been done on the Volt yet, I decided to give up that campaign and wait for more research to get done.
In the mean time, I told the phone to do a factory reset so I can start back fresh and go about using the device normally. This might have been where I made a mistake. I told the device to factory reset and format everything through the Android OS instead of booting into the stock recovery and telling it to do a factory reset. The phone shut off and never came back. I was not able to get it to charge, I could not enter LG Download Mode, I couldn't get into the recovery, absolutely nothing. Tried seeing if I could use the LG Mobile support tool to push anything to the phone since my computer could still see the phone connected... No luck.
So, my questions to the team here on XDA is:
1. What exactly happened to cause the phone to start the factory reset, but, lose everything? I could only assume that the phone kicked the system, data, boot, recovery, and... well.. everything off and fried it's memory. I assume it had to do with what I was trying to do with swap memory and something getting seriously messed up.
2. More specific on what the phone did after, it would not turn on, charge, go to recovery, or download mode. It was completely unresponsive. Would there have been a way to resurrect this phone back from the dead that I wasn't able to find after all the looking and research I had done?
3. With the new LG Volt I recieved from Virgin, how safe would you say things would be to go about rooting again and being more careful with my apps while I wait or get involved with some of the future ROM development for the device?
4. Is there something with how LGs recovery and download partitions are set up that would cause these to be unable to function? Or something that is particular to the LG Volt?
Finally, 5. I noticed that the work done and the team researching the Volt right now have managed to get an unlocked bootloader and a custom recovery that works. Would it be safe with the research done now to go about unlocking and flashing the custom recovery on?
These questions all take into account common knowledge stuff such as, the potentially to brick a phone again is always there and to continue doing as much research and reading as I can to know what I'm doing with the device accurately. Hope my questions can be answered here, until then, cheers gentlemen.
Click to expand...
Click to collapse
1. im not sure what is going on lately, but there seems to be an influx of jacked phones lately from botched modding and attempting to fdr to fix it.
a note for future reference, a fdr will fix nothing you did that required root. so if you mess something up, just go right for the stock flash to try and fix it, if it can be fixed.
2. i doubt it.
3. i would go for it.
4. cant answer that, sorry.
5. absolutely, as long as it is stable.
any body knows how te get correct spc or msl..i try with meid converter but wrong msl..please.
Hi there! I have a Stock kitkat d80020y, made root with stumproot but without custom recovery, it's running stock right now.
First of all let me tell that I have in my computer nandroid backup of it (TWRP & CWM) made with OnlineNandroid and one LGBackup made with system restore menu.
Here's the trouble:
I am about to sell my phone so i was backing up some stuff yesterday when i realized it was not syncing contacts with google, after researching a bit I deleted the "com.android.providers.settings" folder which it was situated into "data\data" and rebooted device.
Then, sync problems gone but some another problems came up, couldn't get into some settings just as language, swipe down settings didn't work neither, home button didn't work at all, etc; when tried to use that things, phone just did nothing or stayed one second and got back to home screen. Read something that factory reset would definitely solve my issue, well it did solved it at a glance, home button was functional again but, things like language submenus were still not working.
So then, I try to install an LG Backup using the system app, could restore settings and appeared to be solved, but after another factory reset, remember I'm about to sell it, the whole issues came up again.
As I have nandroid backup I've recently checked the clockworkmod folder and find the deleted folder.
Considering that i could manage to get that LGBackup installed again, could it be possible to paste "com.android.providers.settings" back into "\data\data" folder then?
Should that be the definitely fix? Or I'll have to reflash all nandroid even though I don't wanna take that risk because is just those problems, apparently related to that specific deleted folder, the other things of the phone are intact and work great.
In case of need reflashing, could you tell me about any easy tutorial on how to do it, including custom recovery installation for my stumprooted device?
I don't actually know how to ADB any android device, if you could also help me with the right tutorial and drivers for this phone so i have everything ready just in case of needing CMD to fix this device it would be great.
Hope I get some answers soon so i can quickly fix the device, any ideas are welcomed and will be utterly appreciated.
Sorry for the long text but i wanted to be as clear as i could.
Regards!
lautta10 said:
Hi there! I have a Stock kitkat d80020y, made root with stumproot but without custom recovery, it's running stock right now.
First of all let me tell that I have in my computer nandroid backup of it (TWRP & CWM) made with OnlineNandroid and one LGBackup made with system restore menu.
Here's the trouble:
I am about to sell my phone so i was backing up some stuff yesterday when i realized it was not syncing contacts with google, after researching a bit I deleted the "com.android.providers.settings" folder which it was situated into "data\data" and rebooted device.
Then, sync problems gone but some another problems came up, couldn't get into some settings just as language, swipe down settings didn't work neither, home button didn't work at all, etc; when tried to use that things, phone just did nothing or stayed one second and got back to home screen. Read something that factory reset would definitely solve my issue, well it did solved it at a glance, home button was functional again but, things like language submenus were still not working.
So then, I try to install an LG Backup using the system app, could restore settings and appeared to be solved, but after another factory reset, remember I'm about to sell it, the whole issues came up again.
As I have nandroid backup I've recently checked the clockworkmod folder and find the deleted folder.
Considering that i could manage to get that LGBackup installed again, could it be possible to paste "com.android.providers.settings" back into "\data\data" folder then?
Should that be the definitely fix? Or I'll have to reflash all nandroid even though I don't wanna take that risk because is just those problems, apparently related to that specific deleted folder, the other things of the phone are intact and work great.
In case of need reflashing, could you tell me about any easy tutorial on how to do it, including custom recovery installation for my stumprooted device?
I don't actually know how to ADB any android device, if you could also help me with the right tutorial and drivers for this phone so i have everything ready just in case of needing CMD to fix this device it would be great.
Hope I get some answers soon so i can quickly fix the device, any ideas are welcomed and will be utterly appreciated.
Sorry for the long text but i wanted to be as clear as i could.
Regards!
Click to expand...
Click to collapse
Finally solved flashing stock again with a guide on htcmania forum, this guide is really great for spanish speaking guys like me and many others,(xda doesn't allow me put the link); theres also an english guide here on xda.
I used autorec to install recovery just in case you wanna know
See you!
Hey all,
I've got a question. Most likely a question I know the answer to and I'm in denial. My phone crashed on vacation and wouldn't boot anymore. Not sure how it append but it did. A software failure. After many attempts I've tried to recover some of my vacation photo's an video's. (luckily I've added a cloud sync before going on vacation in case of theft and havn't lost all) In the restore attempts I've soft bricked my phone (from bad to worse) And had to make a clean install with odin. I've installed a clean Stock Rom and rooted it with Magisk (supersu resulted in bootloop). I've tried a few recovery programs from the first page googleling. But no results.
I'm pretty sure the previous version was encrypted and I'm hitting a dead end here.
As for my question: Have I've really given myself the answer not getting it back because of the (possible) encryption or are there better recovery options?
As soon as you started writing over everything with a new flash, you effectively became SOL. There's likely nothing left to recover.
Even before that, while recovery might have been possible, you wouldn't have liked the price tag.
Yeah, thanks. I've figured that. By now I've accepted the fact that I've lost the content and moved on.