Database Develop

No Mobile Data after Nandroid Restore

I don't think I can edit the title so I'll write it here for anyone who wants to help: This problem is SOLVED. (Y)
So the matter is a bit complicated and I can't guarantee I even remeber everything I did but I'll try to include as much detail as I can:
I had the Stock Rom (OOS4.0.0) running, OEM unlocked & rooted when the OOS4.0.1 OTA notification kept nagging in the back of mind. I thought I should just leave it ago because I already had a feeling it would go wrong...
So I download the Full .zip and flashed it through TWRP 3.03-1 and after that it was stuck on the boot screen for more than 15 minutes or so. So I restarted it again and this time it booted butall my data was deleted and it gave me an error about the encryption having failed. But as you probably know, one can't flash anything on an encrypted phone so I checked back in TWRP and it was really encrypted. Checked back in the phone's settings: Also encrypted. I then used a tool to force decryption (it also wipes all the data) and I was back to square one.
From that moment on I tried: 1. restore nandroid (all partitions included [that includes EFS]). It got me to the booting screen, but when I unplugged it shut down and a reboot got me to the battery screen. I had 72% left so at this moment I thought it had nothing to do with it not booting at 72%. Then I wiped everything (checked every box in TWRP) and was left without any OS. Then I let my phone charge to 100% and re-restored the nandroid OOS4.00 and it worked but I had the Unlock-Bug, I was able to fix that. Then it booted but it wasn't able to recognize any SIM cards, so I fixed that by re-re-restoring with TWRP 3.03-0 (which automatically replaced 3.0.3-1 after the nandroid) and everything worked fine. until I went out today and realized I had no mobile data. I doubt it has something to do with EFS because everything else is working fine (calling, checking IMEI wih *#06#).
I then proceeded to check the APN and it looked ok, I then tried another SIM card (from the same provider) and it didn't change anything.
My provider is the german company 1&1 (1und1) but it uses vodafone APN.
I have no clue what to do right now so I am asking you guys for help.
Thanks in advance!

Well, first things first. On rooted devices with stock rom always flash a full/complete zipped image - never, never, never use an official partial image. And always wipe Dalvik/Art and common cache before reboot.
In your case now I would probably try to clean re-flash the current OOS image version (4.0.1). You'll find guides and downloads in the guides and rom section of this forum. Clean flashing your device requires you to completly wipe the data partition before flashing (the internal partition remains untouched). Don't forget to wipe Dalvik/Art and cache before rebooting. This will hopefully completly reset your device.

Inciter said:
Well, first things first. On rooted devices with stock rom always flash a full/complete zipped image - never, never, never use an official partial image. And always wipe Dalvik/Art and common cache before reboot.
In your case now I would probably try to clean re-flash the current OOS image version (4.0.1). You'll find guides and downloads in the guides and rom section of this forum. Clean flashing your device requires you to completly wipe the data partition before flashing (the internal partition remains untouched). Don't forget to wipe Dalvik/Art and cache before rebooting. This will hopefully completly reset your device.
Click to expand...
Click to collapse
First of all: Thanks for your reply.
I don't know if there was a misunderstanding but I only ever flashed the full 1,4gb .zips.
Also I am running 4.00, because I had to restore it as the 4.0.1 flash ruined my phone. Just now I flashed 3.03-1, wiped dalvik & cache and flashed the 4.02 .zip which I got from this [https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074] thread but it left me stuck on "patching image uncoditionally" or something and then I rebooted and now I am stuck on the +1 booting screen (not even the animation, just the +1 logo witht he "powered by android" signature in the bottom).
I have the feeling it's a software bug not related to what I did with my phone. it was just luck that I did not havfe that problem prior to my nandroid restore or something. I mean: Looking at it from a logical perspective: When you restore your phone with a full nandroid backup it should be exactly the same phone, shouldn't it?

Well, flashing the TugaPower rom might break the alert slider. To fix this you have to simply backup and recover the data partition. I don't know why this is happening but I believe that sometimes permissions to files and folders remain untouched in certain situations. Maybe someone else knows more details on this topic.
If you are absolutly sure that your nandroid contains all required partitions just try to wipe all cashes, data and system partition before recovery. But like I said before I would then clean re-flash your current OOS image version. In your case the error might possibly be some error resulting from faulty permission on configuration data. If it was a common bug more people would have reported it already.
If something broke and it can't be easily fixed... trying to return to point zero and resetting everything to defaults will possibly your best chance.

Inciter said:
Well, flashing the TugaPower rom might break the alert slider. To fix this you have to simply backup and recover the data partition. I don't know why this is happening but I believe that sometimes permissions to files and folders remain untouched in certain situations. Maybe someone else knows more details on this topic.
If you are absolutly sure that your nandroid contains all required partitions just try to wipe all cashes, data and system partition before recovery. But like I said before I would then clean re-flash your current OOS image version. In your case the error might possibly be some error resulting from faulty permission on configuration data. If it was a common bug more people would have reported it already.
If something broke and it can't be easily fixed... trying to return to point zero and resetting everything to defaults will possibly your best chance.
Click to expand...
Click to collapse
I have no problem with that, but my device does.
I can't flash anything because TWRP (bot 3.03-0 and 3.03-1) will be stuck at "patching system image unconditionally", ( I tried the full 4.02 .zip and the ful 3.54 .zip that I am 10000% sure used to work, because I used it before the Nougat release).
Wiping everything but Internal and USB OTG changes nothing.
If you have any idea how I can get to a fresh start, I would really appreciate it.
EDIT: I am sorry, I don't know what you mean by TugaPower Rom. I never installed anything like that - atleast not knowingly.

Due to encryption returning to OOS 3.X after having upgraded to Nougat is difficult. Just flashing wouldn't do. There's still an option to format data - not just to wipe it. Was boot, EFS and firmware partition included in your nandroid? Does the recovery still work now? Another Approach would be to use the Unbrick Tool.

Inciter said:
Due to encryption returning to OOS 3.X after having upgraded to Nougat is difficult. Just flashing wouldn't do. There's still an option to format data - not just to wipe it. Was boot, EFS and firmware partition included in your nandroid? Does the recovery still work now? Another Approach would be to use the Unbrick Tool.
Click to expand...
Click to collapse
So, I have the means to decrypt my device through a tool I found here on the forums last month. It does wipe all your data, though. Anyways: I was able to restore mobile data through an older nandroid backup (and yes: all my back ups include all partitions; glad I was smart enough to do that haha). That worked for me and made me come to the conclusion that the back up I used first was somehow corrupted. Then I restored the data partition using my most recent nandroid back up and now I am back in the game. Thanks for all your help so far!
The only thing that kind of makes me worry is that I only get ~60mbit/s through speedtest even though I should get 200. I know I was able to get 200Mbit/s at some point using that phone, but I don't remember if it was with OOS 3xx or the OOS 4.00 update. So I can't tell whether it has something to do with me restoring the phone, my WiFi connection (a speedtest with my lan-connected desktop gave me 200) or just an android bug.
I'll wait until weekend when I have the means to test it with another 200k connection - and imho 60k is enough for anything I do with my phone anyways and I don't plan on reselling the phone in the future, so it won't kill me even if it is nandroid-related.

Linux/Android backups aren't always that satisfying. I often experienced diffences between what was saved and what or how it was restored. Most problems resulted in faulty permissions or missing file execution attributes.
Nevertheless, I'm glad your devices is working again. Keep that backup save, you'll might need it again... or hopefully not.

Inciter said:
Linux/Android backups aren't always that satisfying. I often experienced diffences between what was saved and what or how it was restored. Most problems resulted in faulty permissions or missing file execution attributes.
Nevertheless, I'm glad your devices is working again. Keep that backup save, you'll might need it again... or hopefully not.
Click to expand...
Click to collapse
Thank you, I just checked the wifi-speed with an iPhone 6 and it even got lower results (>30k) so I assume it has something to do with the WiFi itself at the moment and not with the OP3t.
And even if the backups are not always satisfying: I want to quote someone I read on some forums doing my research to fix this phone: "The seasoned user knows: A backup makes the difference between an awesome phone and a beautiful brick." That is a most evident truth to me now haha.

Problems with OctOS/TWRP... or maybe I'm the problem ;)

Update for the readers wh don't want to read the rest of the thread:
I solved 2 issues ("com.android.phone has stopped" was gone after wiping system, and the updating now works smoothly after i realized that the latest firmware is 4.0.3 and not 4.0.2)
The remaining problem is:
But i still get the welcome screen (like i wiped the data) everytime i reboot from twrp
It is not a ROM issue, because during the process i switched from OctOS to lineage and i still get the problem... what can that be???
quick info: TWRP is the most recent (3.0.3-1), firmware is the newest (4.0.3), Lineage is the nightly from Feb 14.
Original post:
Hello there fellow Oneplus users,
I've got some trouble with my 3T. I changed the OS to OctN some weeks ago. Everything was fine, i din't update the first 2 weeklys and when i wanted to update a few days ago (to OCT-N-WEEKLY-20170210-2251-oneplus3.zip) i tried but there was error 7... i don't remember exactly what i did then but when i booted i got the message "com.android.phone has stopped" and i couldn't get the message away (it appeared directly again after clicking ok) in the background the phone wanted to make a fresh setup. i tried a few things out, and the only thing that worked was wiping the cache, dalvik and data and then installing the rom, that was installed before (OCT-N-WEEKLY-20170121-0348-oneplus3.zip)
the next day i thought i could try it again (i hoped it was just coincidence), but make a backup via twrp before. but then same error... So i wanted to restore the backup. It went without errors in twrp, but the booting afterwards took about 15 minutes! After the boot: again the error message and in the background the "set up new phone" screen... even though i did a restore... so again wipe cache/dalvik/data via twrp and re install the old version of the OctOS
Next day after research: maybe i needed to update the firmware (4.0.2). downloaded it but i thought i would wait a little, because i don't have that much time to deal with those problem right now.
So today i decided to give it a try, rebooted to twrp, but then i thougt: "nah, i'll do it another day". So i really did NOTHING in TWRP -> reboot to system -> same old Error (com.android.phone has stopped) and data lost (new phone setup)
Ok: reboot to twrp, flashed the new firmware (no error) tried to flash the new OctOS -> error 7...
I also have the latest LineageOS rom (lineage-14.1-20170214-nightly-oneplus3-signed.zip) on the phone to try out: wiped Cache/Dalvik/Data install Lineage: same error 7...
same with the old OctOS: everything's fine...
Longstory short: what ever i do in twrp doesn't work expect a wiping and reinstalling the same OctOS that worked the last 3 or 4 weeks...
What am i missing? Or is there really something wrong with my phone?

Try to flash the new TWRP, firmware.

and flash the rom with full wipe

svandasek said:
Try to flash the new TWRP, firmware.
Click to expand...
Click to collapse
TWRP is the newest, and (as already mentioned in the text) firmware was renewed during the process without any success.
What do you mean by full wipe? More than Cache, Dalvik and Data?
But still, i have the feeling, that this error is something not very common... I think i might return to complete stock, if the problems continue.

So,
i solved 2 issues ("com.android.phone has stopped" was gone after wiping system, and the updating now works smoothly after i realized that the latest firmware is 4.0.3 and not 4.0.2)
But is Still get the Welcome Screen (like i wiped the data) everytime i reboot from twrp
It is not a ROM issue, because during the provess i switched from OctOS to lineage and i still get the problem... what can that be???

Nobody got any idea?

felixburk said:
Nobody got any idea?
Click to expand...
Click to collapse
It's a TWRP and f2fs problem. You either need to change your data partition to EXT4 and/or update your TWRP to 3.0.4-1
https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-3t-t3543391

GrandMasterB said:
It's a TWRP and f2fs problem. You either need to change your data partition to EXT4 and/or update your TWRP to 3.0.4-1
https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-3t-t3543391
Click to expand...
Click to collapse
Thanks I'll try that out.
Might it help, if i don't set a password for the phone? Or is it not encryption related?

felixburk said:
Thanks I'll try that out.
Might it help, if i don't set a password for the phone? Or is it not encryption related?
Click to expand...
Click to collapse
It's filesystem driver related and nothing to do with the encryption.

upgrading to Nougat, trouble replacing old kernel

Apologies for duplicating this post but the original forum was apparently the wrong spot for this.
I need either some pointers or a reference to a how-to, if you please.
My Nexus 6 is currently running Pure Nexus 6.0.1-2060821-official, security patch 8/5/2016 with ElementalX kernel 3.10.40-ElementalX-N6-3-20.
I've updated Pure Nexus before through TWRP and all went well, but those efforts never involved updating the kernel too. I've attempted to flash the new kernel, the rom and the google apps, but the phone goes into a never ending boot effort and it's a tussle getting back to recovery mode as it tends to boot loop. The flashes are preceded by clearing Delvik and cache and cleared again after the flash.
Is the order of flashing off or perhaps not enough clearing of other items such as system? Or is a factory reset needed?
Kind of lost on this one and can't seem to string together enough search terms to find help specific to the problem.
Any help would be appreciated.

The kernel is most likely not updated to work with the rom. Each rom comes with its own kernel so you really don't have to flash a new one. I would flash the rom and gaps and see what happens. Leave the kernel out of it for now. You have to remember that not all kernels work on all roms. Many roms are making it so only their kernel works properly.

zelendel said:
The kernel is most likely not updated to work with the rom. Each rom comes with its own kernel so you really don't have to flash a new one. I would flash the rom and gaps and see what happens. Leave the kernel out of it for now. You have to remember that not all kernels work on all roms. Many roms are making it so only their kernel works properly.
Click to expand...
Click to collapse
Still no-go. Freshly downloaded purenexus_shamu-7.1.1-20170215-OFFICIAL and Full_Dynamic_GApps-7.1.x-20161215, checked the MD5s, and flashed both after cache/Dalvik. Still got the same 4-color bouncing dots. Let it run like that for about 40 minutes before getting back into recovery.
Ran the same flash but this time also wiped system. Same result.
Is 40 minutes enough time? Impatience maybe?
Now back to original 6.0.1, PureNexus 6.0.1-20160821 and 3.10.40-ElementalX-N6-3.20 kernel.
Any ideas?

jlfesslerkc said:
Still no-go. Freshly downloaded purenexus_shamu-7.1.1-20170215-OFFICIAL and Full_Dynamic_GApps-7.1.x-20161215, checked the MD5s, and flashed both after cache/Dalvik. Still got the same 4-color bouncing dots. Let it run like that for about 40 minutes before getting back into recovery.
Ran the same flash but this time also wiped system. Same result.
Is 40 minutes enough time? Impatience maybe?
Now back to original 6.0.1, PureNexus 6.0.1-20160821 and 3.10.40-ElementalX-N6-3.20 kernel.
Any ideas?
Click to expand...
Click to collapse
You are doing a full wipe right? Wiping system and data before flashing?
Also encryption could be an issue. If your device in encrypted or the kernel did not remove the force encryption flag. That could take awhile as well.

jlfesslerkc said:
Still no-go. Freshly downloaded purenexus_shamu-7.1.1-20170215-OFFICIAL and Full_Dynamic_GApps-7.1.x-20161215
Click to expand...
Click to collapse
Get the Feb 15 GApps too instead of the Dec 15 GApps. Don't use old GApps.
https://forum.xda-developers.com/android/software/gapps-dynamic-gapps-t3487192
Also make sure that the GApps are 7.1.x and not 7.x.x or you get a SDK mismatch. What does the recovery log show?

Pkt_Lnt said:
Get the Feb 15 GApps too instead of the Dec 15 GApps. Don't use old GApps.
https://forum.xda-developers.com/android/software/gapps-dynamic-gapps-t3487192
Also make sure that the GApps are 7.1.x and not 7.x.x or you get a SDK mismatch. What does the recovery log show?
Click to expand...
Click to collapse
Got the Feb GApps, wiped Dalvik and cache... this time I let it run for a bit over an hour in case the encryption was an issue. There's a little over 19 GB in files. I figured an hour would be enough but no luck. Had to recover again from backup.
TWRP gives 5 items that can be wiped, Dalvik, System, data, Internal Storage and Cache. I was of the understanding that data pertained to user data (photos, notes, etc). Most all of that is backed up but I'm unclear on what needs wiping for this Nougat upgrade. When I wiped system, it didn't seem to help - although I was using the older GApps at that point. I've seen documentation that says to wipe these items at the outset and others that suggest after the flash is complete. Both? Which ones?
I don't want to resort to drastic measures if it's something simple that I've missed.

Needs Nougat bootloader and latest radio--flash in TWRP. This allows flashing N ROMs while will still work with all MM or even 5.1 ROMs
http://batakang.com/ftp/devs/mhous33/shamu/bootloaders/shamu_bootloader_moto-apq8084-72.01.zip
http://batakang.com/ftp/devs/mhous33/shamu/7.1.1/shamu_baseband_D4.01-9625-05.44+FSG-9625-02.115.zip

jlfesslerkc said:
Got the Feb GApps, wiped Dalvik and cache... this time I let it run for a bit over an hour in case the encryption was an issue. There's a little over 19 GB in files. I figured an hour would be enough but no luck. Had to recover again from backup.
TWRP gives 5 items that can be wiped, Dalvik, System, data, Internal Storage and Cache. I was of the understanding that data pertained to user data (photos, notes, etc). Most all of that is backed up but I'm unclear on what needs wiping for this Nougat upgrade. When I wiped system, it didn't seem to help - although I was using the older GApps at that point. I've seen documentation that says to wipe these items at the outset and others that suggest after the flash is complete. Both? Which ones?
I don't want to resort to drastic measures if it's something simple that I've missed.
Click to expand...
Click to collapse
What TWRP version? Old one cause problems on newer ROMS. Newest is 3.1.0, but 3.0.3 or 3.0.2 should be ok.
Wipe everything - /system, /data, /cache. /dalvik. Do NOT wipe Internal Storage (camera photos, downloads, etc.) before flashing. Data is usually app data, so make a nandroid first to save it, but app data can usually be restored with Titanium Backup or Google will restore it on setup. Just do not restore any system data.
Bootup on clean flash does take time, but normally no more than 20-25 minutes.

Try reverting to stock
Install stock firmware using adb

TWRP version might be the glitch.... Mine reports 2.8.5.0 in recovery mode. I'll update to the latest and retry after wiping all but internal storage. If that fails, I'll flash the boatloader and radio.
Once more into the breach.

jlfessler said:
TWRP version might be the glitch.... Mine reports 2.8.5.0 in recovery mode. I'll update to the latest and retry after wiping all but internal storage. If that fails, I'll flash the boatloader and radio.
Once more into the breach.
Click to expand...
Click to collapse
Hi... Save your internal storage before processing. Just in case... TWRP 2.8.5.0 is pre nougat and incompatible.

jlfessler said:
TWRP version might be the glitch.... Mine reports 2.8.5.0 in recovery mode. I'll update to the latest and retry after wiping all but internal storage. If that fails, I'll flash the boatloader and radio.
Once more into the breach.
Click to expand...
Click to collapse
You should really update the bootloader/radio to the latest once you update the TWRP. Updating the bootloader/radio will not affect your internal storage.

Pkt_Lnt said:
What TWRP version? Old one cause problems on newer ROMS. Newest is 3.1.0, but 3.0.3 or 3.0.2 should be ok.
Wipe everything - /system, /data, /cache. /dalvik. Do NOT wipe Internal Storage (camera photos, downloads, etc.) before flashing. Data is usually app data, so make a nandroid first to save it, but app data can usually be restored with Titanium Backup or Google will restore it on setup. Just do not restore any system data.
Bootup on clean flash does take time, but normally no more than 20-25 minutes.
Click to expand...
Click to collapse
Wiping system, data, cache and Dalvik seems to have gotten me to Nougat but apparently root did not come along for the ride. Wasn't expecting that. Is that par for the course?

jlfesslerkc said:
Wiping system, data, cache and Dalvik seems to have gotten me to Nougat but apparently root did not come along for the ride. Wasn't expecting that. Is that par for the course?
Click to expand...
Click to collapse
yup
Item 1.8 and 1.9 here

Pkt_Lnt said:
yup
Item 1.8 and 1.9 here
Click to expand...
Click to collapse
Thanks. 1.9 refers to SuperSU which is what I used earlier.
Also I take it reinstalling TitaniumBackup will then let me restore the apps. Still on track?

jlfesslerkc said:
Thanks. 1.9 refers to SuperSU which is what I used earlier.
Also I take it reinstalling TitaniumBackup will then let me restore the apps. Still on track?
Click to expand...
Click to collapse
That is what Titanium Backup (and Restore) does, yes.

Havoc OS won't install

hey y'all, i hope everyone is okay.
I have (well now it's "i had") Havoc OS installed on my Redmi 8 but i wanted to return to the MIUI. I taught that I could do the installation just like with havocOS, but if it was like that i wouldn't post here. After it "installed" I rebooted it but it was in bootloop and i entered OrangeFox. I then tried to install HavocOS again but it again got in a bootloop. I was thinking that I should wipe something, and I selected Dalvik/ART Cache, Data, Internal Storage, Cache and System. When i got back to the Files section it says "Folder is empty". I taught it was okay and then i tried to copy HavocOS to the Internal Storage but when I entered that folder on my computer there was, and still is, 3 internal storages ("18.1 GB free of 20.4 GB) and one micro sd card folder. I don't know what I did and now whenever i try to copy some file to the Internal Storage it does not show on the OrangeFox. I am scared of restarting the phone so please, if you want to help me don't say i have to restart it unless I really have to.
Thanks!

p_vujic07 said:
hey y'all, i hope everyone is okay.
I have (well now it's "i had") Havoc OS installed on my Redmi 8 but i wanted to return to the MIUI. I taught that I could do the installation just like with havocOS, but if it was like that i wouldn't post here. After it "installed" I rebooted it but it was in bootloop and i entered OrangeFox. I then tried to install HavocOS again but it again got in a bootloop. I was thinking that I should wipe something, and I selected Dalvik/ART Cache, Data, Internal Storage, Cache and System. When i got back to the Files section it says "Folder is empty". I taught it was okay and then i tried to copy HavocOS to the Internal Storage but when I entered that folder on my computer there was, and still is, 3 internal storages ("18.1 GB free of 20.4 GB) and one micro sd card folder. I don't know what I did and now whenever i try to copy some file to the Internal Storage it does not show on the OrangeFox. I am scared of restarting the phone so please, if you want to help me don't say i have to restart it unless I really have to.
Thanks!
Click to expand...
Click to collapse
Oh my God I'm so dead. I just wiped Micro SD card and now it isn't showing as well. I'm just so stupid. When i click reboot to the recovery it says "No OS installed! Are you sure you wish to reboot to the recovery?"

p_vujic07 said:
Oh my God I'm so dead. I just wiped Micro SD card and now it isn't showing as well. I'm just so stupid. When i click reboot to the recovery it says "No OS installed! Are you sure you wish to reboot to the recovery?"
Click to expand...
Click to collapse
I feel so stupid to reply on my posts every 2 minutes but I got the guts and I restarted the phone to the recovery and now it shows everything again. What it doesn't do is installing havoc OS. I installed it again but it booted in to the recovery. I don't know what to do

p_vujic07 said:
I feel so stupid to reply on my posts every 2 minutes but I got the guts and I restarted the phone to the recovery and now it shows everything again. What it doesn't do is installing havoc OS. I installed it again but it booted in to the recovery. I don't know what to do
Click to expand...
Click to collapse
Finally I done it, i formatted the data and then installed Havoc OS. Thanks @p_vujic07 (myself)! You are such a genius!

sorry for the late response, i do tend to watchover here in case someone needs help.
which miui are you flashing? if its xiaomi.eu, that requires stock. since youre using havoc, you deleted most of stock stuff (remember the install steps wiping stuff). also remember to format data (like you did in the last post) to remove most encryption (which also nterferes with recovery).
also which zip did you flash in the last thread? an encryption disabler?
are you still on havoc? does your internal still show as 20GB? 48 (out of 64) is the normal amount in sdcard0 and you should prolly reinstall stock if it isnt correct
upd
for our phone, its possible to install using an otg in case of derps
also for custom roms based on a11, its recd to use the beta 11.1_0

fonzacus said:
sorry for the late response, i do tend to watchover here in case someone needs help.
which miui are you flashing? if its xiaomi.eu, that requires stock. since youre using havoc, you deleted most of stock stuff (remember the install steps wiping stuff). also remember to format data (like you did in the last post) to remove most encryption (which also nterferes with recovery).
also which zip did you flash in the last thread? an encryption disabler?
are you still on havoc? does your internal still show as 20GB? 48 (out of 64) is the normal amount in sdcard0 and you should prolly reinstall stock if it isnt correct
upd
for our phone, its possible to install using an otg in case of derps
also for custom roms based on a11, its recd to use the beta 11.1_0
Click to expand...
Click to collapse
heyy, please sorry for this late answer. i was moving out so i couldn't answer you. it wasn't xiaomi.eu, but it was mi-globe. i tried to install with root (magisk) or wihout it but it wouldn't work. i tried xiaomi.eu, but when i saw that MIUI won't be supported on Redmi 8 i installed havoc again.
the encryption wasn't a problem so i really don't know what was it. maybe i am stupid so i get this now, but do you need to have official MIUI for mi-globe to work? i don't know, and, honestly, i don't want to. i am happy with my havoc, so anyways thank you and sorry for the latest answer you'll ever see!

like i said, most miui roms do require stock stuff (remember the wipes), you could also manually install a miui imgs and (theoretically) install miui roms but yeah i havent tried that.
how much internal storage does it show
are you using orfox 11.1_0 beta
did you flash an encryption disabler

Now it shows 32gb,so it's good
I'll now boot into recovery to see what is the version
I don't think that I used encryption disabled, I just used havoc is zip (also gapps and magisk)

p_vujic07 said:
Now it shows 32gb,so it's good
I'll now boot into recovery to see what is the version
I don't think that I used encryption disabled, I just used havoc is zip (also gapps and magisk)
Click to expand...
Click to collapse
Orange fox is R11.0_2

I installed havoc os only because I can't receive messages, like from what's up. With havoc os it works perfectly fine so I just wanted to install MIUI to see if they fixed the problem in 12.5 (or what was it) version

you should prolly reinstall stock again as sdcard0 should show 48gb (max 64). something messed up your partition. if its a low priority you could let it slide.
miui based roms wont work from most custom roms since they are using different system|vendor imgs.

Oh, you didn't understand. My phone has 32 gb, so it's all good. I don't want to install MIUI now because I don't know if my problem if solved (notifications) and MIUI 13 is going to come out, and Redmi 8 won't support it

ah sorry, i completely forgot about the 3/32 variant (ive only seen the 4/64).
i doubt 11 will even come out as fastboot 12.5.1 is only out for china only, and its been months lol. wouldnt matter to me for tons of reasons

Question A12 having issues flashing updated custom rom - not sure what to do

Okay sorry for coming here with this, but I've searched for a way to resolve this on my own and can't seem to be able to.
I'm using Octavi Rom on my Redmi Note 10 Pro, and I recently tried to do the update from 3.0 to 3.2. I use TWRP custom recovery, and ofc no device decryption, so I had issues wiping dalvik/cache. I already assume I did something wrong because everyone else was able to install fine. My device didn't boot loop but from the first time it loaded, I had issues logging in because my settings crashed, system crashed, my phone is very slow, and I have no idea what to do to fix it. https://hastebin.com/osihiyibal This is the log I get when the settings crashes.
Can someone give advice on what I can do? I can't open device settings *at all*. I can't wipe data or do a factory reset. I would just like some help because my phone is pretty unusable sometimes in this state, and not sure if I can wait for A12 decryption to be a thing. Thanks in advance.

If you are okay with losing everything and just want a clean install and use the device you can try the following. If you already have TWRP installed but are getting the decryption error, Go into TWRP go to Wipe, Format data, Type yes, then click the blue check mark. It should clear the decryption and you can do a fresh install of whatever operating system you want to install.

Thank you so much! You're a life saver. I was able to reinstall the rom with no issues by wiping the data. Everything is working great too. Like having a new phone all over again, but I don't care. So much better than the crashing and slowness. <3 Thank you!