I have a problem with a KATE SD on Miui 7-3-9 and previous versions.
After I install the phone with a fastboot rom,
I install KATE-ZCX-TWRP-3.0.2-X-20161230
I return to twrp to back up [boot, system, data, cache, misc, recovery, modem, efs, cust, persist, firmware_ROM, firmware_EMMC]
I install root, VIPER and dolby
I update the phone with an OTA via the official updater (which reboots to twrp)
The phone boots
I return to twrp to back up [boot, NOT system, NOT data, cache, misc, recovery, modem, efs, cust, persist, firmware_ROM, firmware_EMMC]
I install a kernel like radon
then I want to restore the STOCK kernel, in order to get the next OTA via the official updater,
thus I go in twrp
I mount system, data, cache, cust, persist
I restore the boot partition of the second backup I just did, but then I cannot activate the wifi !
Same result if I restore [boot, cache, misc, recovery, modem, efs, cust, persist, firmware_ROM, firmware_EMMC] of the backup after the OTA.
TO get wifi back I must :
-install a custom kernel again
OR
-restore the full update before the OTA.
OR
-restore the second backup made in twrp, (the one of the OTA ) , then install again the OTA
How can I restore the stock kernel and still get wifi ?
Somebody told me there could be a problem with the IMEIs, but my IMEIs are fine and the DATA connection works well. I can send SMS and all. ONLY the wifi fails to turn ON.
I also extract the stock boot.img form the FULL stock rom and install it in twrp, but the problem is the same.
Related
Hi, I installed CWM custom recovery, and took several backups. I wanted to check that the backups worked so I tried to restore them. This just made my phone not boot (it sticks at the second screen which says "Samsung GT-i5500". (I can recover from this by re-flashing the stock ROM, but this still leaves me with some useless backups.)
Is there some way I can try to debug to see where it is going wrong? I have tried to use ADB logcat (from the android SDK) but it doesnt report anything ("still waiting for device").
I dont get any errors reported during the backup or the restore.
What I used...
Odin 4.28
Custom recovery: ClockworkMod-Galaxy5-v0.5.tar (When it runs it reports that it is version v4.0.1.5)
Closed down Keis.
Leave Odin controls at defaults and just add the OPS file and the above file for 'one package'
When doing restore I have run, from the recovery menu: clear cache, data reset, clear dalvik cache.
and then select the restore option
I have a samsung galaxy 5500
when restoring stock only restore data then wipe dalvik and cache.
flash stock rom then advanced restore data then wipe dalvik cache and cache.
ASHLEY117 said:
when restoring stock only restore data then wipe dalvik and cache.
flash stock rom then advanced restore data then wipe dalvik cache and cache.
Click to expand...
Click to collapse
Thanks ashley117, but I didnt understand this. It was a bit too brief for me to follow (I'm just new to android).
"when restoring stock only restore data"
Not sure how to do this - it only comes as a single package.
Or did you mean when restoring my backup?
I was wondering how much this would restore. Will it do everything that would have happened if restore was working - will it preserve unlocked phone and rooted phone etc?
Hi guys,
First, let me start off with some information about my setup:
Phone: Galaxy S3 i9300
Rom: Omega v5.0 AOPK (No modded kernel, modem or anything; "stock" Omega 5.0 AOPK)
I downloaded and flashed (via CWM) this camera which I downloaded via Omega Files. I then went on to boot and got stuck on bootanimation. I took out my battery, reinserted, booted in recovery and cleared /data, /cache and dalvik cache. Rebooted the phone, and yet again it's stuck on boot animation.
Any tips on what I might've done wrong / what I can do to fix it?
Restore the nandroid you made just before you flashed the mod, if you didn't then do a super wipe and flash your whole ROM again - pray that your efs folder and partition is still intact.
boomboomer said:
Restore the nandroid you made just before you flashed the mod, if you didn't then do a super wipe and flash your whole ROM again - pray that your efs folder and partition is still intact.
Click to expand...
Click to collapse
How do I do a super-wipe? I have an EFS-backup so I guess that part should be safe.
Could I reflash the rom through recovery (which still works)?
If you have Philz recovery then that option is built in, otherwise format system, data, cache, preload and delete the android folder of your internal sd card.
Flash the ROM either through recovery or Odin.
boomboomer said:
If you have Philz recovery then that option is built in, otherwise format system, data, cache, preload and delete the android folder of your internal sd card.
Flash the ROM either through recovery or Odin.
Click to expand...
Click to collapse
Reflashing through recovery worked. Great! Thank you so much
I suppose a nandroid backup is in order. Is there any particular way that's best for such a task, or can I simply do it from CWM?
Get the ROM back to how you like it, make a nandroid in CWM then repeat regularly - simple.
I own the Nexus 9 (Wi-fi model) and am running Android 6.0 MRA58N, rooted with the TWRP recovery. I wanted to to update to android 6.0.1 so downloaded the latest factory image (MMB29R) from Google's website. I rebooted to TWRP so I could flash the new image. When I realized that you cannot flash system.img through TWRP I had already flashed the boot.img. I attempted to reboot only to get stuck in a bootloop. "Luckily me" I had taken a backup through TWRP previously (boot, data and system). So I went again in TWRP, factory reset and restored (successfully as per the message) the backup. Now every time I boot I see Google's logo, then the "Your device is corrupt" message, that I'm seeing since I installed TWRP (it doesn't seem to affect anything) and then a blank screen that goes on forever.
I had this backup moved to my hard drive and the moved it back to my device. Tried the "fix permissions" option in TWRP as well. No go.
Any suggestions?
I managed to fix it by installing the system, cache, boot and vendor partitions from the new build and the data partition from my nandroid backup.
same happen to me yesterday..what i did is,reboot into fastboot.and then flash vendor, system, boot, cache and also recovery..i have twrp install,but it show 0mb on internal storage.flash stock recovery fix that problem..and after that i flash twrp,supersu and elementalx again..it fix my problem
Sent from my Nexus 9 using Tapatalk
Hello, I unlocked my bootloader today. Immediately after flashing the official TWRP, I booted into it through ADB, and flashed DFE. After rebooting, I went back to TWRP, wiped data, cache, dalvik, system and flashed the latest vendor with pixel experience. ROM booted just fine, but after rebooting to TWRP again, it was asking me for password. I can get into TWRP by entering my device pin, and I can get back into the ROM, but during boot it always asks me for my pin. What should I do to fix this? Should I flash DFE with the ROM?
try "Format Data"
Your Data is already Encrypted. You need to Format your data/internal storage. Make sure to backup your data first before doing that.
I made a backup of Awaken OS 1.5.1, (boot, system, data, efs) and when I tried to restore it and reboot to system after, it just boots back to twrp... Why? Someone said backup vendor as well, so I tried that but this time in Fluid os 1.1 (android 11 as well) (boot, system, data, vendor, efs) but it still doesn't boot the system just goes back to twrp... Help. Please. My twrp is the latest 3.5.0_10-0
i had the same problem with xeu and DFE. just remove any screen unlock patern, pin, face rec, fingerprint and then make a backup.