On 4.4 can't restore back to 4.3 - Nexus 4 Q&A, Help & Troubleshooting

I've flashed my phone with Odex 4.4 rom and I want to restore a backup of pa rc2. When I restore the back up, cwm says there's an error. The phone boots up but it spammed with a error or FC box and won't let me use the phone.
So I'm wondering if this is a common fault, if so can it be fixed?
Or will I have to wait until pa release a 4.4 rom?
Ps I didn't install a factory image before flashing 4.4
Thanks

alpha-dog said:
I've flashed my phone with Odex 4.4 rom and I want to restore a backup of pa rc2. When I restore the back up, cwm says there's an error. The phone boots up but it spammed with a error or FC box and won't let me use the phone.
So I'm wondering if this is a common fault, if so can it be fixed?
Or will I have to wait until pa release a 4.4 rom?
Ps I didn't install a factory image before flashing 4.4
Thanks
Click to expand...
Click to collapse
Hmm I done same thing yesterday. Did CWM recovery asked you a question after hiting reboot system? When i was doing it I got some message(dont remember it now) and hit Yes.
Though you can reflash the 4.3 ROM and make advanced restore.

I think so, I pressed yes and had that error/ fc box.
What's an advanced restore??

Related

[Q][HELP] Lost signal on 4.3 after reverting to 4.2.2

Hey,
Today in between flashing a new ROM i went back to 4.2.2 cm10.1.2, just to check some things out before flashing a 4.3 ROM that i was intending to do in the first place.
However after having reverted to 4.2.2 when i went and install the 4.3 ROM i noticed i had no signal, since then i've tried flashing the radio and boot from 4.3 Factory Image via fastboot, tried installing a different 4.3 ROM, all with no success.
What can I do?
Btw i still get signal in 4.2.2
Thanks.
Mottz said:
Hey,
Today in between flashing a new ROM i went back to 4.2.2 cm10.1.2, just to check some things out before flashing a 4.3 ROM that i was intending to do in the first place.
However after having reverted to 4.2.2 when i went and install the 4.3 ROM i noticed i had no signal, since then i've tried flashing the radio and boot from 4.3 Factory Image via fastboot, tried installing a different 4.3 ROM, all with no success.
What can I do?
Btw i still get signal in 4.2.2
Thanks.
Click to expand...
Click to collapse
Check APN settings?
How do I do that?
Also the phone app just crashes totally when I try to do anything with it, even entering airplane mode triggers that.
Sent from my Nexus 4 using Tapatalk 4
You should do a clean wipe before you flash 4.3 from an older version, do a factory reset and wipe the system partition, then flash 4.3 rom.
via xda app
It might have to do with TWRP.
http://forum.xda-developers.com/showthread.php?p=45323439
Try flashing TWRP 2.6.0.0 then proceed from there to flash your rom.
I guess i forgot to mention, i did a clean install, i factory reset before reverting.
And i have TWRP installed, I've tried several ROMs and in all of 4.3 ROMs i dont have signal and the Phone app FCs when i try to use it.
On that note, does TWRP Factory Reset wipes System Partition?
Factory reset does wipe system partition except /data/media.
Flash TWRP 2.6.0.0 (this version)
Factory reset
Flash Rom
Flash Gapps
Flash Modem
Flash Kernel
Flash Supersu
Wipe caches
Reboot
Btw, here is some insight on what to wipe in TWRP:
http://teamw.in/whattowipe
Oh I just saw your previous post, didn't understand it at first but now that I think about it I do actually have 2.6.1.0.
Ill try what you said and report back.
Thanks.
Sent from my Nexus 4 using Tapatalk 4
It worked, thanks alot!

[Q] Boot animation stopping kitkat update

Hi all!!
On my Nexus 7 2012 (rooted) I'm running android 4.3 rom and I'm trying to manually update it to the new 4.4. It's not letting me flash the update because I changed the boot animation, and (of course) I forgot to backup the stock animation before adding the new one. I downloaded the stock "X" animation from someone and replaced the old one with the stock animation, but it still comes up with an error. Is there any way I can get it back to it's unaltered state so the update won't flag it as a problem? Also, if that's the only thing I altered and I can get it back to normal, can I just wait for the OTA update?
Other info:
Running M-Kernel
Using TWRP
Thanks!!
Same here
Download the factory image for 4.4 and flash it over adb, can't go wrong with that. Only thing is you'll have to re-root and reflash TWRP after that.
Sent from my non-Apple device via XDA App
cr0wnest said:
Download the factory image for 4.4 and flash it over adb, can't go wrong with that. Only thing is you'll have to re-root and reflash TWRP after that ...
Click to expand...
Click to collapse
+1 on flashing the factory image via ADB - easy enough to re-install Custom Recovery & then Root by pushing SU v1.69
Otherwise, if running TWRP - look here, download the zip file and flash it from Recovery (first, full wipe - cache, dalvik & factory reset) - it will bring you to KitKat 4.4 (KRT16O)
There is a minor update (1.4MB in size) to KRT16S - flash it next once it's downloaded, and, then, reinstall TWRP and then root it.
Setup tablet, restore google account & customize home screen - enjoy.
Backup important files & data first, as always.

Having Problems in flashing roms

On flashing a Custom Rom, my phone gets stucked with continous FC ("Unfortunately Phone Crashed","Press OK") just after the phone boots.
I had faced the same problem earlier so someone on XDA suggested to use twrp recovery. Then i flashed the purity rom and it worked fine, but then as you may know now, as PA is out, so flashed it and again i'm getting continuous fc error....
currently i'm using purity rom, stock kernel and twrp recovery (2.6.3.3)
I would flash back to a stock 4.2.2 and start over. I find that this is the only way I can install certain roms.
audit13 said:
I would flash back to a stock 4.2.2 and start over. I find that this is the only way I can install certain roms.
Click to expand...
Click to collapse
I already did this and again i'm facing the same problem
htrapy said:
I already did this and again i'm facing the same problem
Click to expand...
Click to collapse
Strange. Are you updating the bootloader and radio before flashing a 4.4 rom?
Are you doing a factory reset???? And flashing a proper gapps after ROM? You should always do this when going from one ROM to another. Sometimes a manual format of /system is necessary also.
no i am not updating my bootloader and radio before flashing (rather didn't know if i had to update them,fyi i bought my nexus 4 this september)....and yes i'm doing a factory reset (using the wipe option in twrp recovery which warns clearing of data, cache and dalvik memory)

soft brick phone flashing rom

I downloaded twrp and CM 10.1 CR2 for my MK2 4.3JB galaxy S4.
I made nandroids on the extra then went in used the wipe feature in twrp then loaded cm and gapps. Worked great and I love the ROM.
Went to put back nandroids. Used the wipe feature again then restored nandroid. Bootleg and stuck on the yellow sprint screen. Tried to flash Odin .tar and it started with a ton of FC then said something about data partition.
I had no choice but to factory wipe and I wanted to keep all my internal stuff. The stock to CM worked fine but just doing general wipe did not work to restore my nandroid.
The CM I noticed is 4.2.2. Is this an issue going back to stock 4.3 nandroid ?
I'm restoring the phone completely so it's fresh out of the box then rooting then using twrp to try to get back my old nandroid.
What did I do wrong in the process that caused it to stall on the yellow sprint screen ?
Now that I think about it I did probably a "dirty" flash since. I did not completely factory wipe the phone just the dalvik cache, cache and the last item on TWRP.
Once you go to 4.3...aka MJA or MK2 you cannot go backwards. So that may have been your issue. Try stayin with 4.3 or up
If you say "Please"... be sure and "Hit Thanks!!!"
OK I tried again after wiping, flashing 4.3, rooting, setting up TWRP.
I wiped everything and when I made my nandroids I checked ALL the boxes. I'm currently on CyanogenMod which works fine but I cant restore my nandroid. I wiped all then used restore from my SD card. I have twrp 2.6.3.0 I think.
I'm still getting stuck on the sprint screen. Help !
Don know about checking everything?? I make sure that SE Linux is checked (i use philz) and then save to SD. Have had zero issues so far and I bounce from 4.3 TW to 4.4 AOSP daily. Sorry I've never used TWRP so I cannot begin to help troubleshoot.
If you say "Please"... be sure and "Hit Thanks!!!"
I just want to make sure you are not wiping before you create the nandroid backup. I reread your post and it was unclear. When creating the backup you should not wipe first. Next, when switching between AOSP and Touchwiz things can get tricky. Usually a failure to boot is after doing a nandroid is caused by the kernel not being correct for the rom installed. It would probably be best to keep an AOSP kernel and a Touchwiz Kernel on your sdcard so you can flash it after you restore the nandroid backup to ensure the proper kernel is in place.
Secondly, it was mentioned above that you can't go back to 4.2.2 after going 4.3. This is actually incorrect. You cannot flash a stock tar of an older 4.2.2 rom through odin if you have the MJA (AKA Knox bootloader). You can however flash a 4.2.2 rom using recovery since it does not attempt to change the bootloader.
cruise350 said:
I just want to make sure you are not wiping before you create the nandroid backup. I reread your post and it was unclear. When creating the backup you should not wipe first. Next, when switching between AOSP and Touchwiz things can get tricky. Usually a failure to boot is after doing a nandroid is caused by the kernel not being correct for the rom installed. It would probably be best to keep an AOSP kernel and a Touchwiz Kernel on your sdcard so you can flash it after you restore the nandroid backup to ensure the proper kernel is in place.
Secondly, it was mentioned above that you can't go back to 4.2.2 after going 4.3. This is actually incorrect. You cannot flash a stock tar of an older 4.2.2 rom through odin if you have the MJA (AKA Knox bootloader). You can however flash a 4.2.2 rom using recovery since it does not attempt to change the bootloader.
Click to expand...
Click to collapse
I don't think I wiped before making the nandroid, but I'm not sure. I have the Sprint GS4, and the nandroid was a 4.3 (Dec 2013) firmware.
Can you help me out here, I'm really lost. Do I need to flash a Touchwiz kernel on top of the nandroid through TWRP (flashing multiple zips) ? Where do I get the kernel ?
Made a nandroid of my Cyanogen Mod. Wiped phone and restored Cyanogen Mod nandroid. No problem. Worked fine. Just the original that I made is not working.
mikeprius said:
Made a nandroid of my Cyanogen Mod. Wiped phone and restored Cyanogen Mod nandroid. No problem. Worked fine. Just the original that I made is not working.
Click to expand...
Click to collapse
There are a lot of people that have had problems switching between Cyanogen Mod and Touchwiz using nandroid restores. It usually is the Touchwiz kernel not being restored when restoring the backup. When you boot up, you won't get past the initial boot screen. If this happens, you should just have to reboot back in to recovery and flash a TW kernel then reboot or after your restore your nandroid backup, just flash the TW kernel before rebooting. Look in the Android Development section for a custom TW kernel or you can try this kernel that unkownforce posted from his Triforce rom: http://www.androidfilehost.com/?fid=23321874045862620
cruise350- You are my hero. The nandroid DID come back and is working This has racked my brain all night and I am so so glad that I got my nandroid back.
I do have a few more questions:
1. The Wifi is not working ?
2. It appears that my Sprint is on 3G, and not going to 4G LTE ? Do I need to do something with this ? I also am getting errors trying to update my profile and PRL.
3. Is a custom TW kernel always required to be used, is there a stock Samsung TW kernel ?
Thanks a TON ! I couldn't figure out it for the life of me. Other than that I have been enjoying Cyanogen Mod. Using goomanager it looks like some CM versions are not flashable with TWRP and only by Clockworkmod.
on some roms i know that if you don't use the kernel that comes with it the wifi doesn't work. maybe try stock? in your mobile network settings, is your preferred network type "lte/cdma/evdo'? i'm sure there's a stock kernel on the forum somewhere.
It was set on global, so I switched it thanks for the heads up. Wifi still out of commission though. Once I get this set up, I'm eager to try new ROMs. I'm still on the fence about TWRP though. It's a nice interface vs. Clockwork, but it seems like most files out there cater more to CWM
mikeprius said:
It was set on global, so I switched it thanks for the heads up. Wifi still out of commission though. Once I get this set up, I'm eager to try new ROMs. I'm still on the fence about TWRP though. It's a nice interface vs. Clockwork, but it seems like most files out there cater more to CWM
Click to expand...
Click to collapse
i can't really give advice on that since all i've used is cwm. idk what kernel that one is, but i think it now comes with kt-sgs4. maybe the one from before? i looked around and i couldn't find a stock kernel by itself for mja or later. if you extract the boot.img from a stock rom the kernel and ram disk are in there. how easily you could screw up your phone doing that is beyond my experience, so maybe try a different custom kernel and wait for somebody else's advice for the boot.img thing?
Wifi AND booting (as @cruise350 mentioned) are almost always a kernel issue.
What ROM are you actaully on?
How did you get there, your nandroid?
What kernel are you now using and how did you flash it?
Have you tried gonig into settings, turning off wifi, wait a moment and then trying to turn back on?
Sounds like you should flash a stock(based) TW ROM and go from there. That often clears up connection issues.
Also might want to set your 'network type' back to automatic.
As for CWM and TWRP both are superb just make sure you follow the ROM developers recommendation as to which to use. (Philz is a CWM based recovery). There are .tars and zips of the latest of each here in these forums.
Please spend some time here reading, searching and then reading some more. You will find all the answers to your questions and it will give you a huge grasp of what is what and how to do things properly.
Good luck.
I am currently on the L720VPUEMK2 ROM 4.3 for Sprint. Android version 4.3 (Dec 2013 update).
I used TWRP 6.2.3.0 to flash Cyanogen Mod 10.2 nightly version (not sure if matters specifically which one).
My kernel was from TriForceKernel on the link above. It says 3.4.0-gb72521e-dirty. I flashed it after I flashed my recovery after wiping the device including internal data, cache, dalvik cache via install .zip in TWRP then rebooted.
The phone has loaded up but does not seem to be toggling between 4G LTE and the wifi is busted. I checked my nandroid and it says there is a boot file in it.
When I created my nandroid, I checked all the boxes, then slide the toggle which was supposed to create a back up for all 6 segments. I'm not sure why the boot.img isn't loading, it's part of the recovery that saved it. The settings seem to be as I left them....there are just some little things that are problematic.
I have a boot.emmc and boot.emmc.win both that are part of the nandroid recovery that has been flashed yet it gets stuck on the splash screen.
Well I'd just wipe and try any one of the FIVE TW ROMs that have been dropped in the last 7 days.
Trying to fix whatever is your issue could take hours or days.
Wiping completely (as per whichever dev's ROM you choose), installing said ROM, and starting from scratch will assure you phone works AND give you the best chance to get stuff working.
I dirty flash, restore and install ROMs all the time.
However When I absolutely want to know I'll have a good working ROM I clean flash. Wipes, setup, let Google restore apps, debloat restored (and stock apps!) then setup each setting and app to my liking. Titanium comes in real handy - after all my apps are re-downloaded I can selectively restore data to those that need it (Kindle, newsreader, SMS, Call Logs etc.)
Try that - installing clean new ROM and see what happens. Then go from there. Or don't and spend another couple days without a completely working phone.

[Q] Restore CWM backup on CM11

Hello guys.
I want to downgrade my defy+ from CM11 to stock android.
Before update the recovery and install CM11 i made a backup with CWM and now i want to restore this backup.
How can i do this? Can i install CWM using the kitkat on my phone?
Sorry for the dumb question, but I'm afraid of doing something wrong.
lucashs said:
Hello guys.
I want to downgrade my defy+ from CM11 to stock android.
Before update the recovery and install CM11 i made a backup with CWM and now i want to restore this backup.
How can i do this? Can i install CWM using the kitkat on my phone?
Sorry for the dumb question, but I'm afraid of doing something wrong.
Click to expand...
Click to collapse
I have discovered that I need it too because my phone is loked and, to enter my carrier unlock code, i need to restore my backup made with CWM.
Looking for the same.
Yesterday i have installed 2ndInit to get back CWM recovery and restore my original stock ROM image.
Android can not complete the full boot, showing the intro of my carrier during a hour while loading Android.
Reinstalled TWRP and recovered my CM11 backup.
I will try again and, if not suceded, i will flash my carrier SBF to unlock my phone.
I will inform any news about CWM restore stock ROM.
TicoDePano said:
Yesterday i have installed 2ndInit to get back CWM recovery and restore my original stock ROM image.
Android can not complete the full boot, showing the intro of my carrier during a hour while loading Android.
Reinstalled TWRP and recovered my CM11 backup.
I will try again and, if not suceded, i will flash my carrier SBF to unlock my phone.
I will inform any news about CWM restore stock ROM.
Click to expand...
Click to collapse
I think this happens because the roms use different file systems
Try the Aroma Wiper to change the file system:
http://forum.xda-developers.com/showthread.php?t=2202674
I'll try this, but now i'm without time, then i report if it work.
I got my phone working.
http://forum.xda-developers.com/motorola-defy/help/tim-brasil-signal-cm11-t2824983#post54683596
About revert to stock ROM, only doing a factory reset to format my data partition fix the boot (I did not try AROMA or safewipe.zip).
I do not tried to restore data from my stock dump after got my phone working because it was not my objective, but i think that it is possible and simple after get it working.
Thanks.

Categories

Resources