It is just as the title states. I would like to somehow fix my phone instead of just recovering.
I can still access twrp, and the app(https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp) is used to create it with has created some backup files that i can still access. Is there still hope?
Mi 8 Pro with lineage os 18 unofficial
PalanixYT said:
It is just as the title states. I would like to somehow fix my phone instead of just recovering.
I can still access twrp, and the app(https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp) is used to create it with has created some backup files that i can still access. Is there still hope?
Mi 8 Pro with lineage os 18 unofficial
Click to expand...
Click to collapse
If you have some idea which apps you uninstalled then you can put them back in the right directory/folder, the app you used probably created a folder to backup them anyway for the next this app is not recommended to use it blindly; it doesn´t have a good criteria to determine what´s important and what´s not.
Or you can flash only the system image and after that wipe caches, reboot.
SubwayChamp said:
If you have some idea which apps you uninstalled then you can put them back in the right directory/folder, the app you used probably created a folder to backup them anyway for the next this app is not recommended to use it blindly; it doesn´t have a good criteria to determine what´s important and what´s not.
Or you can flash only the system image and after that wipe caches, reboot.
Click to expand...
Click to collapse
do you know of a way to find out exactly whats missing? like some log or something like that?
PalanixYT said:
do you know of a way to find out exactly whats missing? like some log or something like that?
Click to expand...
Click to collapse
Yes, there are some apps on PlayStore that can do that but you can´t boot right now to use it, probably you can take some logs through adb while in TWRP, check this https://github.com/IzzySoft/Adebar
The app you used creates a folder in the SDCard, probably it keeps the apps there, if you have TWRP you can navigate to it and you´ll find them.
the app has created an xyz.apk.backup can i just use adb install, or should i do something different?
hmm, i think just reflashing the system image would be easier. So should i just reflash the lineageos.zip?
PalanixYT said:
the app has created an xyz.apk.backup can i just use adb install, or should i do something different?
Click to expand...
Click to collapse
Yes, the first is identify the apps and then you can install them using adb through TWRP or copying the app to the folder where it was previosuly.
PalanixYT said:
hmm, i think just reflashing the system image would be easier. So should i just reflash the lineageos.zip?
Click to expand...
Click to collapse
You can flash it just wiping caches.
ok thank you very much, you are a life saver
i'm sorry i messaged you
it didn't work. Maybe also flash gapps?
PalanixYT said:
it didn't work. Maybe also flash gapps?
Click to expand...
Click to collapse
What´s inside the LOS zip? And what exactly didn´t work?
it's just the zip i used when installing the custom rom. i can send the file if you wnat.
META-INF/com/android/metadata
system.new.dat.br
system.patch.dat
vendor.new.dat.br
vendor.patch.dat
META-INF/com/google/android/update-binary
META-INF/com/google/android/updater-script
boot.img
install/bin/backuptool.functions
install/bin/backuptool.sh
system.transfer.list
vendor.transfer.list
META-INF/com/android/otacert
i was still inside a boot loop
PalanixYT said:
it's just the zip i used when installing the custom rom. i can send the file if you wnat.
META-INF/com/android/metadata
system.new.dat.br
system.patch.dat
vendor.new.dat.br
vendor.patch.dat
META-INF/com/google/android/update-binary
META-INF/com/google/android/updater-script
boot.img
install/bin/backuptool.functions
install/bin/backuptool.sh
system.transfer.list
vendor.transfer.list
META-INF/com/android/otacert
i was still inside a boot loop
Click to expand...
Click to collapse
It could work if you do it correctly:
- Wipe system, caches and data (not format)
- Flash the LOS zip.
- Flash the GApps (if you had previously Google apps on it)
- Reboot.
it worked, thank you very much. Is there a way to restore my phone to its previous state? i made a twrp backup just in case
PalanixYT said:
it worked, thank you very much. Is there a way to restore my phone to its previous state? i made a twrp backup just in case
Click to expand...
Click to collapse
Great, you can restore it just at the same time you did take the backup, if at the moment that this happened you didn´t take a backup of course you can´t anyway if you had some apps synchronizing with the cloud then this will be the only way. It works similarly as Windows (or Linux distros) also work if you have some idea from.
Related
Today I was trying to back everything up because I needed to do a clean install. I used to have CMW, and it would work perfectly. Few days ago I switch to TWRP because of its friendly UI. Everytime I try to make a backup, I get this "Failed to make backup folder". When I go to the mount tab, or explorer, it shows my sd card and the folder named TWRP...is there any solution to this? Or should I switch back to cmw?
Thanks
elias.acab said:
Today I was trying to back everything up because I needed to do a clean install. I used to have CMW, and it would work perfectly. Few days ago I switch to TWRP because of its friendly UI. Everytime I try to make a backup, I get this "Failed to make backup folder". When I go to the mount tab, or explorer, it shows my sd card and the folder named TWRP...is there any solution to this? Or should I switch back to cmw?
Thanks
Click to expand...
Click to collapse
If you're using the version of TWRP modified to work with SELinux (needed for KitKat 4.4.x ROMs) you may need to shorten the name of the target file before starting the backup.
benyto said:
If you're using the version of TWRP modified to work with SELinux (needed for KitKat 4.4.x ROMs) you may need to shorten the name of the target file before starting the backup.
Click to expand...
Click to collapse
Thanks a lot!! that fixed my problem. One more question: TWRP backups dont have the boot.img file in their folders. I read that it automatically flashes the boot.img when Im restoring the backup. Will it still flash it even though Im s-on?
Thanks
elias.acab said:
Thanks a lot!! that fixed my problem. One more question: TWRP backups dont have the boot.img file in their folders. I read that it automatically flashes the boot.img when Im restoring the backup. Will it still flash it even though Im s-on?
Thanks
Click to expand...
Click to collapse
TWRP should backup your /boot partition to the boot.emmc.win file. As far as I know it should also be able to restore this, even if you are S-On. However, I am not positive about that
how to copy TWRP nandroid backup to device?
I need to restore and I don't know how to copy from my hdd to the phone.
The phone is not booting but I can get to twrp recovery.
Latest TWRP has MTP mode.
but it doesn't allow me to copy one of the backup files which is: data.ext4.win000 and it's 1.5GB
You'll need to give us more information.
Why did it fail? Why did your phone stop booting?
1. flashed bigxie_hammerhead_LRX21O-signed.zip
2. flashed CF-Auto-Root-hammerhead-hammerhead-nexus5
3. booted fine but still had apps like Ti backup & TWRP not working due to root permissions
4. Went to recovery and performed Fix permission.
5. stuck in boot loop
gil80 said:
but it doesn't allow me to copy one of the backup files which is: data.ext4.win000 and it's 1.5GB
Click to expand...
Click to collapse
I have had the same problem with my motox 14 the way I found around it was to copy the file to a different fold and use twrp file explore to move it to the back up folder. That has worked for me and a few others try it out it will work.
how can you copy using twrp while in recovery? are you able to access your PC from recovery?
gil80 said:
1. flashed bigxie_hammerhead_LRX21O-signed.zip
2. flashed CF-Auto-Root-hammerhead-hammerhead-nexus5
3. booted fine but still had apps like Ti backup & TWRP not working due to root permissions
4. Went to recovery and performed Fix permission.
5. stuck in boot loop
Click to expand...
Click to collapse
You'll need to factory reset then reflash the ROM
Fix permissions was not required here. You need titanium beta from his twitter feed.
ok i got the phone working and lost my data but I have it backed on PC.
I just see that 10GB is used but when I browse the phone using file explorer, the device is empty.... what??
Is it a known issue?
when the phone is connected to PC I see that 10GB is used but when I i browse the device it shows as empty
No. Do a full flash of userdata.img
Please explain
What would I achieve by flashing it?
gil80 said:
Please explain
What would I achieve by flashing it?
Click to expand...
Click to collapse
A fix for your problem. I shouldn't really need to explain that.
Thanks!
I got it working now. Only need to figure out why it shows 16GB instead of 32 and why root permissions are not working
gil80 said:
Thanks!
I got it working now. Only need to figure out why it shows 16GB instead of 32 and why root permissions are not working
Click to expand...
Click to collapse
Well the answer in the 100 other threads about space say that you must wipe data and cache.
Root should be fine, but as already mentioned, not with official titanium release.
I already did a wipe data and cache. So I don't understand why I still get this but I'll try again.
The Ti Backup link in the twitter feed is no longer valid, but for example, ES file explorer and clean master and also TWRP app are not performing as if they are rooted.
I'll try to re-install CF-Auto-Root-hammerhead-hammerhead-nexus5
gil80 said:
I already did a wipe data and cache. So I don't understand why I still get this but I'll try again.
The Ti Backup link in the twitter feed is no longer valid, but for example, ES file explorer and clean master and also TWRP app are not performing as if they are rooted.
I'll try to re-install CF-Auto-Root-hammerhead-hammerhead-nexus5
Click to expand...
Click to collapse
ES doesn't work properly, correct. Not all apps have been updated to work with L yet either.
L is much more secure than KK. There are ways to root.
1) chain fire - makes small change in RAMdisk that allows sudaemon to work at boot
2)flash a permissive kernel - this lowers protection within selinux.
More apps work with the 2nd method, but still not all.
New titanium coming to play soon.
https://twitter.com/titaniumbackup
Ive held off, but before I update to 5.1, I figured I'd ask before running into problems
Im able to navigate to the TWRP folder when in recovery and restore backups, though the folder is nowhere to be found when looking with a file manager.
I've used Astro, Amaze and Cabinet file managers and the TWRP folder is missing. I did notice a file named TWRP, but it does not open and is not a folder.
How can I get the folder back to manage my backups?
randysoto5 said:
Ive held off, but before I update to 5.1, I figured I'd ask before running into problems
Im able to navigate to the TWRP folder when in recovery and restore backups, though the folder is nowhere to be found when looking with a file manager.
I've used Astro, Amaze and Cabinet file managers and the TWRP folder is missing. I did notice a file named TWRP, but it does not open and is not a folder.
How can I get the folder back to manage my backups?
Click to expand...
Click to collapse
TWRP folder is in /data/media/0. It has been answered for thousand times.
zagorteney said:
TWRP folder is in /data/media/0. It has been answered for thousand times.
Click to expand...
Click to collapse
No it is not. I just recently had this problem, say a month. Ive dealt with what youre talking about when switching from kitkat to lp, but that was loong ago and has been fixed. This is a random thing. All my folders and data are available except TWRP, so try again
randysoto5 said:
No it is not. I just recently had this problem, say a month. Ive dealt with what youre talking about when switching from kitkat to lp, but that was loong ago and has been fixed. This is a random thing. All my folders and data are available except TWRP, so try again
Click to expand...
Click to collapse
Install Terminal, type in:
su
restorecon -FR /data/media/0
Then reboot your device. You should have your TWRP folder back normally. This happens when you perform a backup via TWRP which disalign the partitions. Try updating your TWRP recovery to 2.8.5+, they seem to resolve the issue on later versions.
(you must be rooted, and grant access to terminal).
zagorteney said:
TWRP folder is in /data/media/0. It has been answered for thousand times.
Click to expand...
Click to collapse
happiness4u said:
Install Terminal, type in:
su
restorecon -FR /data/media/0
Then reboot your device. You should have your TWRP folder back normally. This happens when you perform a backup via TWRP which disalign the partitions. Try updating your TWRP recovery to 2.8.5+, they seem to resolve the issue on later versions.
(you must be rooted, and grant access to terminal).
Click to expand...
Click to collapse
Duuuude, it worked. Thanks a million
randysoto5 said:
Duuuude, it worked. Thanks a million
Click to expand...
Click to collapse
You're welcome!
happiness4u said:
You're welcome!
Click to expand...
Click to collapse
Will this also work on 5.1 with 2.8.5.2 version? I can see TWRP folder in /data/media/0, but not on my PC.
zagorteney said:
Will this also work on 5.1 with 2.8.5.2 version? I can see TWRP folder in /data/media/0, but not on my PC.
Click to expand...
Click to collapse
My TWRP folder is visible on my computer, even its contents inside. You could try, I'm still on TWRP 2.8.5.0. it should work with 2.8.5.2 as well.
Edit: Youl probably know when something's wrong with your internal storage partitions if you are having a folder named "0", it shouldn't be there in the 1st place.
happiness4u said:
My TWRP folder is visible on my computer, even its contents inside. You could try, I'm still on TWRP 2.8.5.0. it should work with 2.8.5.2 as well.
Edit: Youl probably know when something's wrong with your internal storage partitions if you are having a folder named "0", it shouldn't be there in the 1st place.
Click to expand...
Click to collapse
Is it possible, that TiB has created it and that is somehow connected with folder storage, visible on PC, but not on phone? And if you delete this folder on PC all content of storage will gone.
zagorteney said:
Is it possible, that TiB has created it and that is somehow connected with folder storage, visible on PC, but not on phone? And if you delete this folder on PC all content of storage will gone.
Click to expand...
Click to collapse
Yep, if you delete that "0" folder, it will wipe out the entire internal storage. I always experience this issue on old TWRP recoveries, when transitioning to lollipop or by making a backup. As for my observation with Titanium Backup, it creates a folder named "storage", I delete that folder before and it wiped my internal storage as well. That thing, I could not sorted out atm.
happiness4u said:
Yep, if you delete that "0" folder, it will wipe out the entire internal storage. I always experience this issue on old TWRP recoveries, when transitioning to lollipop or by making a backup. As for my observation with Titanium Backup, it creates a folder named "storage", I delete that folder before and it wiped my internal storage as well. That thing, I could not sorted out atm.
Click to expand...
Click to collapse
Me neither.
Offtopic: Don't you use CM12 anymore?
zagorteney said:
Me neither.
Offtopic: Don't you use CM12 anymore?
Click to expand...
Click to collapse
As of this moment, I'm kind of enjoying the stock 5.1. Google has made a pretty decent job with this update. I will surely be back to CM12 once they release the 5.1 builds. Plus OmniRom 5.1 is out too, I might also try that before really going back to CM. I really like CM because of their CAF roms.
happiness4u said:
As of this moment, I'm kind of enjoying the stock 5.1. Google has made a pretty decent job with this update. I will surely be back to CM12 once they release the 5.1 builds. Plus OmniRom 5.1 is out too, I might also try that before really going back to CM. I really like CM because of their CAF roms.
Click to expand...
Click to collapse
Yeah. Rom is fast as hell. Its just funny with that scrolling bug and pissed me of - I still can't figured it out how to integrate updated system apps into rom.
zagorteney said:
Yeah. Rom is fast as hell. Its just funny with that scrolling bug and pissed me of - I still can't figured it out how to integrate updated system apps into rom.
Click to expand...
Click to collapse
On what rom are you trying to integrate the apps? Let's go back to your thread regarding this matter. We might get infractions if we flood this one with off topics.
happiness4u said:
On what rom are you trying to integrate the apps? Let's go back to your thread regarding this matter. We might get infractions if we flood this one with off topics.
Click to expand...
Click to collapse
Hey! The problem of OP is solved with your help. You can talk here as you wan't.
Its different story with me - I just like to chat with nice people. Stay cool.
Forget to answer you: on stock 5.1.
zagorteney said:
Hey! The problem of OP is solved with your help. You can talk here as you wan't.
Its different story with me - I just like to chat with nice people. Stay cool.
Forget to answer you: on stock 5.1.
Click to expand...
Click to collapse
Have you tried it on stock 5.0.1/2 before? I haven't tried integrating updated apps with libs to 5.1 yet. I've tried with Play music and Messenger, just replaced the Music2 in priv-app by overwriting. But I think you should put the lib files (.so) on the /system/libs for it to work. Like on GooglePlayServices.
Edit: I backread some on your thread, as my statement above was already addressed. That's strange, I might try integrating some apps and report back later.
deleted @happiness4u was faster
happiness4u said:
Install Terminal, type in:
su
restorecon -FR /data/media/0
Then reboot your device. You should have your TWRP folder back normally. This happens when you perform a backup via TWRP which disalign the partitions. Try updating your TWRP recovery to 2.8.5+, they seem to resolve the issue on later versions.
(you must be rooted, and grant access to terminal).
Click to expand...
Click to collapse
Thanx. This is working also on CM12. About TiB storage folder we were talking abour - funny - on CM12 I simply deleted and it's gone. Just folder - anything else stayed.
zagorteney said:
Thanx. This is working also on CM12. About TiB storage folder we were talking abour - funny - on CM12 I simply deleted and it's gone.
Click to expand...
Click to collapse
That command will work on any android device. I was on CM12 when I deleted that "storage" folder, and I got wiped. That's kind of unfair to me. LOL
happiness4u said:
That command will work on any android device. I was on CM12 when I deleted that "storage" folder, and I got wiped. That's kind of unfair to me. LOL
Click to expand...
Click to collapse
As you are now on 5.1, may I ask if it happened to you also that somethimes the name of Provider is missing in Quick Settings - status bar?
Hello XDA,
I need help. I read online that this problem can be solved by doing "pm remove-user 999". I already did, rebooted, i don't have parallel apps, but i still get Error 255 and can't do a backup. Does anyone know how to solve this issue?
I want to do OTA update, but i would like to backup first. Any other way to backup the whole phone?
Will error 255 prevent me fromdoing the update later on?
what version of TWRP are you using?
Bradl79 said:
what version of TWRP are you using?
Click to expand...
Click to collapse
3.2.3-1
Try this one
Unofficial TWRP
Remove any securities before backing up
Bradl79 said:
Try this one
Unofficial TWRP
Remove any securities before backing up
Click to expand...
Click to collapse
You think that could solve the backup problem? Should i install it as the guide says over Official TWRP?
Paco020293 said:
You think that could solve the backup problem? Should i install it as the guide says over Official TWRP?
Click to expand...
Click to collapse
I am able to do a backup and restore with it, no issues. You can install over Offiical TWRP.
one of 3 methods
1. Download the Installer zip and boot to TWRP and flash the Installer, Reboot to recovery.
2. Download the IMG and flash via fastboot
Code:
fastboot flash boot nameoffile.img
3. Download img file and boot to TWRP
Advanced > Install Recovery Ramdisk > click on twrp img file
Paco020293 said:
Hello XDA,
I need help. I read online that this problem can be solved by doing "pm remove-user 999". I already did, rebooted, i don't have parallel apps, but i still get Error 255 and can't do a backup. Does anyone know how to solve this issue?
I want to do OTA update, but i would like to backup first. Any other way to backup the whole phone?
Will error 255 prevent me fromdoing the update later on?
Click to expand...
Click to collapse
If you read my solution at this link:
https://forum.xda-developers.com/oneplus-6/how-to/255-error-twrp-backup-restore-999-t3801632
Make sure that you go back into your device using a Root browser. Search for any residual folders that are listed in the link above. If you find any of those folders delete them. If you find any folders marked 999 delete those as well. Reboot your phone and check again
dgunn said:
If you read my solution at this link:
https://forum.xda-developers.com/oneplus-6/how-to/255-error-twrp-backup-restore-999-t3801632
Make sure that you go back into your device using a Root browser. Search for any residual folders that are listed in the link above. If you find any of those folders delete them. If you find any folders marked 999 delete those as well. Reboot your phone and check again
Click to expand...
Click to collapse
I have a 999 folder in
/proc/irq/
/sys /kernel/irq/
Then a 9999 folder in
/proc/uid/
And a user_999 folder in
/data/misc/keystore/
Should i delete this too? All of them? Some?
I am developing this method because TWRP will not restore correctly ever since I upgraded my bootloader from U2 to U4.
Boot and Data will restore but System will not, so I do the following.
Backup
1. Use TWRP to backup Boot and Data and reboot
2. Use a root explorer to copy /system/app to external sd
3. Copy /system/priv-app to external sd
Debloat by deleting apps from these 2 backup files
Restore
1. Boot into TWRP and install system.img (extract from ap section of downloaded firmware for stock) or install UPie
2. Restore Boot and Data as usual
3. Go to Advanced - File Manager
4. Delete /system/system/app and /system/system/priv-app
5. Copy and paste backup app files to /system/system
6. Reboot
Note: TWRP has its own system which holds the ROM system as a sub directory.
If anyone can think of another system directory which I can backup and restore please let me know.
physwizz said:
I am developing this method because TWRP will not restore correctly ever since I upgraded my bootloader from U2 to U4.
Boot and Data will restore but System will not, so I do the following.
Backup
1. Use TWRP to backup boot and Data and reboot
2. Use a root explorer to copy /system/app to external sd
3. Copy /system/priv-app to external sd
Debloat by deleting apps from these 2 backup files
Restore
1. Boot into TWRP and install system.img
2. Restore boot and Data as usual
3. Go to Advanced - File Manager
4. Delete /system/system/app and /system/system/priv-app
5. Copy and paste backup app files
6. Reboot
Note: TWRP has its own system which holds the ROM system as a sub directory.
Click to expand...
Click to collapse
This is great. I have issues that caused my settings app to show extra and weird options after a restore from TWRP in the past. But since then I've updated to a new TWRP but haven't done any restoring because of what the previous one did. Hope this works when I need it to.
Jeremy_J7 said:
This is great. I have issues that caused my settings app to show extra and weird options after a restore from TWinRP in the past. But since then I've updated to a new TWRP but haven't done any restoring because of what the previous one did. Hope this works when I need it to.
Click to expand...
Click to collapse
I think the system settings are stored in /data
I'll add it to the list.
physwizz said:
I think the system settings are stored in /data
I'll add it to the list.
Click to expand...
Click to collapse
Test it before you add to the list, can't be giving these people false information bro ?
Jeremy_J7 said:
Test it before you add to the list, can't be giving these people false information bro
Click to expand...
Click to collapse
True
I debloated from here
https://forum.xda-developers.com/galaxy-a20/development/debloat-samsung-a20-variants-t4070957
Then I added the updated camera from Ultimate Pie.
My app folders are here
https://mega.nz/file/dtkkES5L#YfHwWC3rlswwYUeA_cdUESCMQo8rvq8k8n20N-oc-8w
Alright will take a look, is this bootloader specific?
Jeremy_J7 said:
Alright will take a look, is this bootloader specific?
Click to expand...
Click to collapse
Not sure.
If it doesn't work it might reboot into recovery and then you need to copy and paste your own /app and /priv-app folders back in place.
@jajk
Try this
@physwizz My appetite for being screwed by Samsung and the dirty traps they lay is severely diminished. Since going to U4, I can't reliably get TWRP to work without triggering the evil red text screen of death.... I have been watching what is happening with the work on custom kernels and Ultimate Pie ROMs but definitive information on what is actually working reliably or not is very patchy..... one person will say "Yep, this definitely works" the other will say "nope can't even boot"... almost like some people don't even own this phone or have not actually tried what they are promoting or are unable to follow instructions properly....
So....starting from stock U4, I can root and install TWRP, magisk and dmverity no problems at all but after going back into the O.S and attempting to reboot into recovery a 2nd time....bang! Samsung screws me!!!! The question is.....is there a custom kernel for U4 and above that truly removes all of Samsung's dirty tricks (security features) and a custom ROM that also holds no hidden surprises?
jajk said:
@physwizz My appetite for being screwed by Samsung and the dirty traps they lay is severely diminished. Since going to U4, I can't reliably get TWRP to work without triggering the evil red text screen of death.... I have been watching what is happening with the work on custom kernels and Ultimate Pie ROMs but definitive information on what is actually working reliably or not is very patchy..... one person will say "Yep, this definitely works" the other will say "nope can't even boot"... almost like some people don't even own this phone or have not actually tried what they are promoting or are unable to follow instructions properly....
So....starting from stock U4, I can root and install TWRP, magisk and dmverity no problems at all but after going back into the O.S and attempting to reboot into recovery a 2nd time....bang! Samsung screws me!!!! The question is.....is there a custom kernel for U4 and above that truly removes all of Samsung's dirty tricks (security features) and a custom ROM that also holds no hidden surprises?
Click to expand...
Click to collapse
If you're talking about the red text that talks about 'official binaries' when booting after you flash TWRP (FRP LOCK) then there's a very easy fix.
@physwizz Yes the evil red text...but it is not after flashing TWRP, it is only if you try to go back into TWRP.
I already know of one easy fix... called don't buy Samsung. All this wouldn't be a problem if manufacturers could resist the temptation to "monetize" private data but that ain't going to happen anytime soon in this dog eat dog world.....
jajk said:
@physwizz Yes the evil red text...but it is not after flashing TWRP, it is only if you try to go back into TWRP.
I already know of one easy fix... called don't buy Samsung. All this wouldn't be a problem if manufacturers could resist the temptation to "monetize" private data but that ain't going to happen anytime soon in this dog eat dog world.....
Click to expand...
Click to collapse
I got that because i was using old data
solved by doing a clean install
The data was then good in future
@physwizz Went through the Samsung dance from scratch, installed UltimatePie4, rebooted into Ultimate Pie no problems, completed the initial setup.....rebooted and back to red text of death!!!
Yes, I did all the format /data etc.... it is not a procedural problem on my part but my phone has always given me more grief than you appear to have - something is different
jajk said:
@physwizz Went through the Samsung dance from scratch, installed UltimatePie4, rebooted into Ultimate Pie no problems, completed the initial setup.....rebooted and back to red text of death!!!
Yes, I did all the format /data etc.... it is not a procedural problem on my part but my phone has always given me more grief than you appear to have - something is different
Click to expand...
Click to collapse
You didn't restore old data?
Clean install?
@physwizz Did nothing but complete the initial setup after install and rebooted.....all started from a clean install of U4, then rooted and TWRP from your tar file, then installed new ROM with data freshly formatted i.e. absolutely no messing around with the stock ROM or custom ROM through the entire process and never getting to the point of rebooting into TWRP which triggered the previous red text of death.....
jajk said:
@physwizz Did nothing but complete the initial setup after install and rebooted.....all started from a clean install of U4, then rooted and TWRP from your tar file, then installed new ROM with data freshly formatted i.e. absolutely no messing around with the stock ROM or custom ROM through the entire process and never getting to the point of rebooting into TWRP which triggered the previous red text of death.....
Click to expand...
Click to collapse
What does red writing say?
@physwizz Writing says "You have just been screwed by Samsung yet again" or something about official binaries which is the same thing....
jajk said:
@physwizz Writing says "You have just been screwed by Samsung yet again" or something about official binaries which is the same thing....
Click to expand...
Click to collapse
I've had that twice
1. When I forced reboot before UPie was finished installing
2 when I didn't wipe caches , data and system before installing UPie
Could also be Samsung Conspiracy Theorist Detection Program (SCTDP) lol