I've been having a bunch of problems recently with my rooted 7 Pro including Magisk Manager constantly "keeps stopping", not being able to access Hide to add new applications, banking apps starting to detect that I'm rooted and camera issues: the camera app not starting, the camera not popping up automatically and the image being usually reversed and occasionally upside down as well, depending on the app I'm using.
Given that Magisk appears to be dead/dying, having lost its developer to Google, I thought I'd start by getting rid of that and then performing a firmware upgrade in necessary to see if that fixes the other issues.
I uninstalled the Manager then ran the uninstall zip within TWRP. Rebooting though hangs on the initial "ASUS" screen.
I can get back to TWRP ok so I guess I'm not bricked yet. My next thought was to try a system upgrade but I seem to need to know the exact version I need, which, seemingly, I can only get via a working phone?
From the back, it says only model I002D along with SN and IMEIs.
I've done a TWRP backup to the external uSD card, and I have a syncthing copy of all of the internal memory that I can access without root.
My questions:
1. Is there something there which can help my figure out which firmware I need to download?
2. Is there any way to install this without wiping the phone?
Please see this post.
When I try to burn rom with TWRP, img burns but it doesn't start and zip gives an error and cannot burn.
When I first burned custom ROM (unofficial AEX), it did not start, so when I deleted the data from TWRP, it seems that I deleted things that should not be erased, so even if I burn it from the zip file, with the error message in the image below I...
forum.xda-developers.com
Related
I rooted my HTC EVO, then wanted a new kernel for better battery, wanted the new gingerbread ROM too but after I rooted, I deleted a few unwanted, stock apps. After I did this, I started to get a lot of force close messages. Certain apps won't even open. So I tried to unzip a new kernel and I wiped all my data from the hboot. Now it starts up, will go to locked home screen. I try to unlock it, it's the white htc screen then loads into the set up (i.e. keyboard usage, etc) and in the last step a force close message pops up then goes through the whole scenario again. Now I want to just put a whole new system on so I can have my evo back. HELP?
emiliah310 said:
I rooted my HTC EVO, then wanted a new kernel for better battery, wanted the new gingerbread ROM too but after I rooted, I deleted a few unwanted, stock apps. After I did this, I started to get a lot of force close messages. Certain apps won't even open. So I tried to unzip a new kernel and I wiped all my data from the hboot. Now it starts up, will go to locked home screen. I try to unlock it, it's the white htc screen then loads into the set up (i.e. keyboard usage, etc) and in the last step a force close message pops up then goes through the whole scenario again. Now I want to just put a whole new system on so I can have my evo back. HELP?
Click to expand...
Click to collapse
Download the rom, kernel, and Gapps (http://www.goo-inside.me/gapps/latest/7/) on your computer. Boot into recovery. I don't use Clockwork, and I'm assuming you rooted with Unrevoked, so that's probably the recovery you have, but try to find the option to mount your SD card via USB, and move the files to your SD card. Do not unzip them. They must be .zip files. Unmount your SD card, wipe your data, wipe your cache, wipe your Dalvik cache, repeat all the wipes at least one more time, then flash the .zips in this order: 1. ROM 2. Gapps 3. kernel. Then reboot, and you should have a working system.
If you use ROM Manager and created a backup then you could flash (install) the OTA ROM Sprint sent out a few months back. This OTA ROM will be for the Rooted evo, so you won't lose root. Go to youtube.com and search this, "How to install new Sprint Htc Evo OTA 3.29.651.5 and keep root." In his comments he'll provide the link to that zip file and you can flash it from the recovery mode. Make sure you wipe the dalvik/cache and then flash zip file from sd card. It will appear to look like your initial problem but it will get passed the white htc screen. You could turn it off and turn it on again if HTC screen stays longer than 10 min. Once the ROM kicks in, you'll notice its stripped of all your cusomizations. If you used rom manager to back up your ROM then redownload ROM manager from market and the superuser app that came with the OTA zip file will allow ROM manager to run. At that point select manager and restore backups from ROM manager and select your backup and it should put you back to where you were prior to the problem.
Sorry so long, but I'm very detailed and don't want to assume you know what I'm talking about.
P.S. similar situation happened to me yesterday I fixed my issue like described above.
Another Thing haha, don't delete your stock apps just freeze them using Titanium backup. Freezing does the same thing for battery life. You wont see them in app drawer and they wont run in background.
[This was already posted, I just moved it to the Shield Q&A.]
As many of you may know, Nvidia has recalled their Shield Tablets. I'll be getting a replacement soon. I'll be rooting it as soon as possible when I get it, but first I have a few questions.
First of all, I rooted my tablet using a guide at IBTimes (that used info from XDA forums) installing CWM recovery.
After rooting I installed Link2SD, pretty much the reason I rooted, to save up some space on my internal memory. Everything was going fine, until I received the recall notice. I moved all my app files back to the internal memory, deleted Link2SD, ran a full unroot on SuperSU, (after a while of hanging on the "Please Wait" screen the app just crashed, it wouldn't load up and Root Checker said I had no root access after rebooting.
I don't know whether this was supposed to happen or whether it should have gone more smoothly, please give me an answer to this and tell me if it affected my system in any way) and fastboot flashed the stock recovery.img.
However when I tried to install the update, I got a red triangle error. After checking the log I got an error saying "Package expects build fingerprint of ... or ..., this device has ...."
I can't remember what the fingerprints were, but the first one was something that began with "nvidia/", had a bunch of numbers in the middle followed by an underscore, then it ended with "/release-keys".
However the device's current build fingerprint was exactly the same as the first, except that it cut off halfway through, right after the numbers and the underscore.
I tried resetting my cache, I tried a wipe of the user data. The only way to fix this for me was to re-install a bunch of stock images - recovery.img, boot.img, system.img, etc.
I don't want to wipe my data next time. So I ask for this in my answer:
- An explanation of what the error means
- How this error is caused
- A way to fix this error without wiping my device
- How to prevent this error
- If what happened to SuperSU in my case is normal and if it affected my device in some way
- And, if possible, a way to install the update successfully without getting this error and without having to unroot or remove CWM, and details on how to do this method and any risks.
Thanks in advance. An answer soon would be appreciated.
Quick answer:
- You don't need to restore to full stock before updating to the latest OTA. This is what I did, running a rooted stock system with TWRP recovery:
-- Go to Settings > About tablet > System updates and continue to click Check Now until the update has been found. I had to click like 4 or 5 times before it was found. It'll download automatically to your device (not your SD card), but I forget where that download location is... XD
-- once you've found your downloaded OTA.zip, copy it to a location you can easily find from your custom recovery.
-- reboot into custom recovery, flash OTA.zip, reflash superSU.zip, wipe cache NOT DATA, reboot
-- wait until device boots up, wait until the Optimizing blah blah process is done.
-- enjoy!
Additional thoughts:
- I've tried the Link2SD app, but I think it messes with my system in a way I don't like; personally I'd rather delete the apps I never use via custom recovery (see THIS THREAD on how to debloat your tablet for yourself!
- I think your error happened when you flashed stock recovery on top of the custom one. To prevent this next time, simply wait for either a flashable zip in THIS OTHER THREAD, or you can check to see if nVidia released any OTA3.1 recovery images if you want that full-stock experience.
Hope this helps!
I want to switch from supersu to superuser, and having an interesting problem that supersu somehow covered up. I have a Nexus 5x running the stock rom. With every months upgrade I would flash using fastboot, go into twrp recovery before first full boot and remove a bunch of unneeded applications in /system/app. When I would boot up those applications would be gone. Somehow this isn't the case with superuser. I can still go into recovery and remove them, but when I boot up all the applications are still in /system/app. If I go back into twrp they are still shown as being missing. I've tried installing es file explorer, but it's unable to delete the applications once the system is up. remounting /system doesn't work either. Any help?
Unrooting supersu caused all the applications to come back; so does supersu not really delete them either, but somehow prevents them from showing up following the recovery scheme or something?
bsd1101 said:
I want to switch from supersu to superuser, and having an interesting problem that supersu somehow covered up. I have a Nexus 5x running the stock rom. With every months upgrade I would flash using fastboot, go into twrp recovery before first full boot and remove a bunch of unneeded applications in /system/app. When I would boot up those applications would be gone. Somehow this isn't the case with superuser. I can still go into recovery and remove them, but when I boot up all the applications are still in /system/app. If I go back into twrp they are still shown as being missing. I've tried installing es file explorer, but it's unable to delete the applications once the system is up. remounting /system doesn't work either. Any help?
Unrooting supersu caused all the applications to come back; so does supersu not really delete them either, but somehow prevents them from showing up following the recovery scheme or something?
Click to expand...
Click to collapse
You aren't doing something right or you don't have something setup correctly. With root, you should be able to unintelligible them completely.
When you removed them, did you wipe cache and dalvik/ART cache before rebooting? If not then the system probably still thinks they are there because they still have data loaded into cache.
I recommend sticking with SuperSU, superuser doesn't work as well as SuperSU
Sent from my SM-S903VL using Tapatalk
I've been googling a bit more. As it turns out there are two system partitions for nougat; in nexus 5x and some other devices apparently. This became more apparent when the file recovery-from-boot.p; which I rename in order to prevent recovery from being overwritten is not renamed when booting the OS. Nougat apparently pulls the system files from somewhere else. So whatever Chainfire did makes it boot the same partition as visible in recovery. Fully unrooting brings all those apps/system partition back. Haven't been able to find a good post that tells me how to to circumvent this without SuperSU; or exactly how this works.
Hello everyone, I was able to fix my bootloop occuring after flashing a zip on magisk, without any data loss. I wanted to share what I did to fix since it may be helpful for others. It is useful method worth trying if you know what caused the bootloop. It is definitely not a universal method of fixing bootloops or anything, but If you have a similar problem, you can try these steps.
The bootloop happened after I flashed a zip on Magisk that I downloaded using EdXposed Manager app. I remember downloading the latest alpha version zip and flashing it using Magisk (I had already had the riru core and riru edxposed modules installed on Magisk but on Edxposed manager app, it was showing some error, so I also flashed the zip that I downloaded using the app. I think this caused the bootloop somehow. ) I had no backups.
(I had also "unable to mount /data" problem on TWRP, I am explaining how I fixed that also, if you don't have the problem, you can skip this paragraph)
My TWRP version was 3.2.1.0. And when I was in recovery mode, I was getting "unable to mount /data" error. This is actually a well-known error, but I was able to fix it without a format by just updating my TWRP to 3.3.1.0. After the update, somehow, internal storage could be mounted and everything was fine. My goal by trying to fix this problem is to be able to have a backup using TWRP (using backup feature on TWRP) (just make sure that you didn't choose the compression option on options tab of TWRP backup page).
If you don't have "unable to mount data" problem at all, just make a TWRP backup. (just make sure that you didn't choose the compression option on options tab of TWRP backup page).
So, after having a TWRP backup of everything (actually just System and Data backup would also be fine), I tried to edit my backup files to fix the problem that caused the bootloop.
I changed 2 things in my backup files (you can edit the backup files ending with .win001 etc using 7zip on windows or anything similar. since the backup files are not compressed, you can just delete files) (I edited only the "Data" backup files due to my specific problem, but if your problem is something different, you may have to edit different files also):
1) I deleted everything about EDXposed manager(com.xx.edxposedmanager files) (It might have nothing to do with the fix, I am not sure)
2) In one of the data backup files (probably in the last one), there is a folder called "adb". In adb, there is a "modules" folder. I deleted riru core and riru edxmanager folders in modules.
After these steps, I restored "Data" and "System" using TWRP restore. Bootloop is fixed without any data loss.
If your bootloop is caused by something different, (the point I am trying to tell is) you can edit the nandroid backup files if you know the root of the problem and maybe fix your phone. When I was editing the backup files, I had no hope. As I said, I think this method is worth trying.
I Found this to be true. I also don't see the reason to reflash everything to fix a problem. Thank you for this tutrorial this is an undocumented tactic and i don't know why. Before i discovered this type of surgery i operated under the assumtion that android must be different from other operating systems in some way which would make this impossible. But like you i delved deeper and discovered that this is like a dark art the devs keep to themselves because of what ever but it works. I like this type of post and usually aside from asking for help or a little feed back this is the only type of post i ever make. I mean how do you expect people to learn how to do anything if you never teach them anything useful. EX: "You didn't do it exactly right from the beginning because if left out one thing in my tutorial so you would fail now erase everything and start over." "I only did that to teach you to backup" such bull ****! Thanks again for fighting the good fight.
After my experiment of trying out Beta 3 of Android Q failed apocaliptical I tried to restore the backup I made minutes before. But no matter what I do, I keep getting:
- bootloops (straight rebooting after showing the unlocked bootloader warning)
- restart into recovery
- Oxygen OS loading animation stuck and animation being very slow
- not getting it anymore but had it yesterday in the early stages of my disaster management: Qualcomm Crash POST
Despite that the backup was generated succesfully (at least thats what TWRP said)
I tried almost every guide out there.
- switching to rm -rf
- restoring only data, only boot, only system and a mix of those
- flashing the OTA before restoring backup
- uninstalling magisk und reinstallating magisk (with and without separate reboots)
-multiple wipes of single partitions and data formatting
The only good thing is that I don't get the 255 error anymore I had at the beginng, allthough I don't really know anymore how I did it.
At the end I am only able to restore everything with the MSNTOOL out there.
Is there any golden hint to get the data the be restored? The backup of /data is critical as there my authenticator and banking data are in there.
Thank you in advance
Edit: As I am slowly getting fed up with OnePlus and the problems (proximity sensor, adaptive brightness, whatspps microphone, twrp issues, lacking tech guides if at all) I thought about migrating to Pixel 5. Is it possible to migrate the data partition? Or are all backup partitions strictily device specific?
anphex said:
After my experiment of trying out Beta 3 of Android Q failed apocaliptical I tried to restore the backup I made minutes before. But no matter what I do, I keep getting:
- bootloops (straight rebooting after showing the unlocked bootloader warning)
- restart into recovery
- Oxygen OS loading animation stuck and animation being very slow
- not getting it anymore but had it yesterday in the early stages of my disaster management: Qualcomm Crash POST
Despite that the backup was generated succesfully (at least thats what TWRP said)
I tried almost every guide out there.
- switching to rm -rf
- restoring only data, only boot, only system and a mix of those
- flashing the OTA before restoring backup
- uninstalling magisk und reinstallating magisk (with and without separate reboots)
-multiple wipes of single partitions and data formatting
The only good thing is that I don't get the 255 error anymore I had at the beginng, allthough I don't really know anymore how I did it.
At the end I am only able to restore everything with the MSNTOOL out there.
Is there any golden hint to get the data the be restored? The backup of /data is critical as there my authenticator and banking data are in there.
Thank you in advance
Edit: As I am slowly getting fed up with OnePlus and the problems (proximity sensor, adaptive brightness, whatspps microphone, twrp issues, lacking tech guides if at all) I thought about migrating to Pixel 5. Is it possible to migrate the data partition? Or are all backup partitions strictily device specific?
Click to expand...
Click to collapse
Try, booting into twrp... Format data. Type yes to format. Restore. Should boot.
@soka said:
Try, booting into twrp... Format data. Type yes to format. Restore. Should boot.
Click to expand...
Click to collapse
I did just exactly that on stock 10.0.0.11 to no avail, the TWRP restore went through fine but upon system reboot the phone stayed on the bootloader unlocked warning for about two minutes, then it rebooted straight into stock recovery.
It's beyond my understanding yet how the user data partition can cause the whole system to effing die.
My only hunch is that it has something to do with Magisk I had installed during the backup (encryption was disabled btw). But as I said I already tried running Magisk installer and uninstaller on different occasions with the same result. Also the only thing that should happen is that after restore and reboot the phone should tell me that Magisk isn't installed anymore.
Edit: So for now I reverted to full stock 10.0.11 and for the sake of experimenting I made a backup with system, boot and data of this stock rom and restored it succesfully. When I restore my actual data backup I get the same old restart and then it throws me back into TWRP. Is there any log I can check to see what's happening there?
Sorry for double post, but I think this might be very interesting for people with a similar problem as this seems to be very common with OnePlus phones.
So I found a very dirty and hacky way to get a least my most importants app running in the state they had during my backup I was trying to restore. Here's what I did, without any guarantee it might work for you or be stable in the end.
Code:
1. Revert the phone to a clean stock rom and update to the latest stable version (at the time of writing 10.0.11), it should be fully factory reset, aka like new. I am not sure but it may be necessary that you install the apps you want to restore first since the I am not sure the partition we use later contains the app AND the data too.
2. Unlock bootloader and flash latest TWRP, may it be official or mauronofio's
3. Make a backup of that current stock data partition
4. Restore data partition from your actual needed twrp backup (if it ends with 255, try to format data partition before in TWRP)
5. With the TWRP file manager navigate to the /data/data folder and copy everything to an external storage (I chose USB)
6. Restore the stock data partition
7. Now again with the TWRP file manager navigate to the /data/data folder on your external storage (should be /usbstorage) and search for the apps you need to restore (probably banking apps, authenticator, etc.), the name will be something like com.google.authenticator2.
8. Copy the folder of any needed app into the /data/data folder on your phone. Best you do it one by one just to make sure.
Now you can reboot to system. The apps should be fully restored. In my case it worked with Google Authenticator, Blizzard Authenticator, Consorbank Secure Plus (shows undefined error yet), Hue Pro. Maybe I will try more.
Edit: Consorsbank Secure Plus as you might guess is a tan generation banking app. When entering the pin when opening the app it shows "An error has occured". Dunno why, maybe a security checksum error or something. I found com.android.keychain and copied for the sake of trying too but it didn't help.
If you have any questions, suggestions or improvements, feel free to post!