If i put custom rom and custom kernel bassed on Android 4.4.2 with cwm and after that flash stock 4.2.2 in fastboot mode and update to 4.4.3 will I brick the device.
hercules16 said:
If i put custom rom and custom kernel bassed on Android 4.4.2 with cwm and after that flash stock 4.2.2 in fastboot mode and update to 4.4.3 will I brick the device.
Click to expand...
Click to collapse
To update 4.4.3, you needn't flash 4.2.2.Just flash using OTA or factory image.
And, when you flash stock 4.2.2 using factory image, it won't brick because it will flash your system and kernel.
CodeingBoy said:
To update 4.4.3, you needn't flash 4.2.2.Just flash using OTA or factory image.
And, when you flash stock 4.2.2 using factory image, it won't brick because it will flash your system and kernel.
Click to expand...
Click to collapse
Tell me what ''s wrong in this thread http://forum.xda-developers.com/nexus-4/help/nexus-4-dead-4-4-3-official-t2774574
hercules16 said:
Tell me what ''s wrong in this thread http://forum.xda-developers.com/nexus-4/help/nexus-4-dead-4-4-3-official-t2774574 .
Click to expand...
Click to collapse
You're not going to brick your device. The ota will just fail. You could try this which will put 4.4.3 on your device. You'll lose the custom rom and kernel but you can just re-flash those on your recovery
http://forum.xda-developers.com/showthread.php?p=53176897
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You're not going to brick your device. The ota will just fail. You could try this which will put 4.4.3 on your device. You'll lose the custom rom and kernel but you can just re-flash those on your recovery
http://forum.xda-developers.com/showthread.php?p=53176897
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
But ota will failed and the big question after all of that how to flash 4.4.3 .
Related
Just a quick question I am using bricked kernel on my nexus7 when I get the official update can I go back to stock kernel by flashing boot.IMG from my nandroid back up
Sent from my 32gb Nexus 7 using Bricked kernel 0.58 with 4.2.1 stock
elsworth1983 said:
Just a quick question I am using bricked kernel on my nexus7 when I get the official update can I go back to stock kernel by flashing boot.IMG from my nandroid back up
Sent from my 32gb Nexus 7 using Bricked kernel 0.58 with 4.2.1 stock
Click to expand...
Click to collapse
itd probably be best to figure out if 4.2.2 even updates the kernel
elsworth1983 said:
Just a quick question I am using bricked kernel on my nexus7 when I get the official update can I go back to stock kernel by flashing boot.IMG from my nandroid back up
Sent from my 32gb Nexus 7 using Bricked kernel 0.58 with 4.2.1 stock
Click to expand...
Click to collapse
No. No. No. You will lose root access after the update. You will have to re root. And which stock kernel do you want to flash back to? 4.2.1? Maybe I don't understand your question..
If you're saying when your device detects the update and you want to flash back to its factory stock kernel, then yes you can do that.
Sent
from my Nexus 7 using xda app-developers app
scream4cheese said:
No. No. No. You will lose root access after the update. You will have to re root. And which stock kernel do you want to flash back to? 4.2.1? Maybe I don't understand your question..
If you're saying when your device detects the update and you want to flash back to its factory stock kernel, then yes you can do that.
Sent
from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Cheers for the input
i was just curious of when the update comes to my nexus 7 that i will have to return to stock kernel so it updates with no issues because of running bricked kernel. I have also installed vodo root keeper (think its called not with my n7 at the moment) to help me keep root. Will i be able to flash the ota through cwm with verification signature turned of ? Or do i have to install stock to flash it
-PiLoT- said:
itd probably be best to figure out if 4.2.2 even updates the kernel
Click to expand...
Click to collapse
Sent from my HTC One X using xda app-developers app
scream4cheese said:
No. No. No. You will lose root access after the update. You will have to re root. And which stock kernel do you want to flash back to? 4.2.1? Maybe I don't understand your question..
Click to expand...
Click to collapse
Ummm... the OTA process performs binary patching on individual files. If a file is not a target of the patching process, nothing happens to it. So that beggars the question of why you think that Superuser.apk/su (or SuperSU/su) would be targeted, as they are never distributed by Google. More to the point, neither of them exist in the boot image, so your assertion is flat out wrong.
Also, a sanity check (checksum) is performed on each and every one of those targeted files; if it should happen that there is an update to the kernel or ram disk, then the boot image will be checked, and IF you have installed a new kernel (or even have a trivially changed boot image), the check of the boot image will fail and the entire OTA will abort.
So, the OP's question was not only perfectly valid and reasonable, but exactly the correct procedure if the boot image gets patched by the OTA.
I'm planning on doing exactly what the OP suggested; but good Dog, I'm also going to do a full Nandroid backup before I begin. How wrong can things go if you have a backup to revert to? (In fact, I'm even going to put the stock recovery on the tab for the purpose of the OTA too - if you have an unlocked boot loader you can reflash or soft-boot any recovery you want, and do whatever you want thereafter.)
Even if you were to "lose root" you can certainly just over flash a minimal kit containing Superuser.apk/su. It's not a big deal.
Put down the toolkit and the hash pipe, and pick up the command line!
So I am using CM10.1 with CWM recovery. What will I have to do when a new version of Android comes out? (4.2.3 or 5.0)
And will I lose my root access?
Sent from my Nexus 4 using xda app-developers app
Either flash a new ROM that's built on the new version, or go back to stock.
username8611 said:
Either flash a new ROM that's built on the new version, or go back to stock.
Click to expand...
Click to collapse
And to flash that ROM, do you have to get new bootloader and baseband or what?
And go back to stock: do you mean to flash the factory image, or can you also get OTA updates by restoring a nandroid backup of the stock rom?
once you are rooted, unlocked and with custom recovery changing ROMs is as simple as puting zip onto your devices' internal storage and flashing it through recovery. you COULD be asked to flash a newer radio version, however it is not that common.
no OTA when rooted, going back to stock only with facotry images.
anyway 5.0 will be availabale on custom ROMs shortly after or even before official google OTA so no need to unroot.
dzumagos said:
once you are rooted, unlocked and with custom recovery changing ROMs is as simple as puting zip onto your devices' internal storage and flashing it through recovery. you COULD be asked to flash a newer radio version, however it is not that common.
no OTA when rooted, going back to stock only with facotry images.
anyway 5.0 will be availabale on custom ROMs shortly after or even before official google OTA so no need to unroot.
Click to expand...
Click to collapse
So when 5.0 comes out, I just have to wait a day and flash a new CM version without flashing a new bootloader or radio?
And will it directly be stable?
Thibaultvw said:
So when 5.0 comes out, I just have to wait a day and flash a new CM version without flashing a new bootloader or radio?
And will it directly be stable?
Click to expand...
Click to collapse
Android 5.0 is far away by now, and nobody can tell you yet about stability
i´m sure it will get announced, just check the CM thread and read about (possible) bugs
Thibaultvw said:
So when 5.0 comes out, I just have to wait a day and flash a new CM version without flashing a new bootloader or radio?
And will it directly be stable?
Click to expand...
Click to collapse
As long as you read threads properly you'll know whether or not anything extra needs to be flashed. Even if there is something you need to flash in the future, it should be fairly easy. Normally a flashable .zip is released soon after the official release so you won't even need a PC. Personally I think it's useless to worry about it right now.
Thibaultvw said:
And to flash that ROM, do you have to get new bootloader and baseband or what?
And go back to stock: do you mean to flash the factory image, or can you also get OTA updates by restoring a nandroid backup of the stock rom?
Click to expand...
Click to collapse
Radios and boot loaders are completely separate from ROMs. You have to specifically flash a radio or boot loader separately. But no, you should not need to flash them but it would be worthwhile if a newer version came out
username8611 said:
Radios and boot loaders are completely separate from ROMs. You have to specifically flash a radio or boot loader separately. But no, you should not need to flash them but it would be worthwhile if a newer version came out
Click to expand...
Click to collapse
I am a bit scared of flashing bootloader and baseband, because I read someone who flashed a wrong one and his phone completely got bricked. Some other guy said in that thread why would you manually flash a bootloader..
http://forum.xda-developers.com/showthread.php?t=2108247
If I restore my Nandroid backup of 4.2.2 stock ROM, am I able to get OTA update? (I dont care if I would lose root, the question is if its possible ) or is it impossible since I am running CWM recovery?
Sent from my Nexus 4 using xda app-developers app
Guys it won't be 5.0 gmail 4.3 = android 4.3
Sent from my Nexus 4 using Tapatalk 2
Hellow guys i make a full wipe and make the ota update to 4.3 but''' i notice some bug when i in the recent and swipe to delete the app some wire black rectagular in top! And lags openinapps!!! I just want to now if i can downgrade to 4.3 to 4.2.2? I going to wait to cyanogen mod team to make a 4.3 rom. And if i yes can doit how??
Im rooted and have twrp recovery.
Thanks guys!!
Sent from my Nexus 4 using Tapatalk 2
http://forum.xda-developers.com/showthread.php?t=2010312
Flash the stock images through fastboot.
I can see this too!
Sent from my Nexus 4 using xda premium
thanks guys i download de n_cry and work perfect is a awesome tool to have in are computers.
If you are going to flash custom ROM; use a toolkit to Root it; flash custom recovery of your choice. Then copy custom ROM to ur phone; go to recovery and flash it. You don't need to downgrade your boot loader.
Sent from my Nexus 4 using Tapatalk 4 Beta
badboy47 said:
If you are going to flash custom ROM; use a toolkit to Root it; flash custom recovery of your choice. Then copy custom ROM to ur phone; go to recovery and flash it. You don't need to downgrade your boot loader.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Does this mean we can downgrade from 4.3 to 4.2.2 custom ROM?
I'm not having a good time with 4.3 stock rooted and custom kernel and thinking about going back to CM 10.1.2. All I need to do is flashing the custom ROM in recovery?
naeco said:
Does this mean we can downgrade from 4.3 to 4.2.2 custom ROM?
I'm not having a good time with 4.3 stock rooted and custom kernel and thinking about going back to CM 10.1.2. All I need to do is flashing the custom ROM in recovery?
Click to expand...
Click to collapse
Yes you will be fine. Before PA 4.3 rom was released, I was using Latest 4.3 bootloader with 4.2.2. I am going to revert to 4.2 as well. I noticed 4.3 battery is really good but sometime touchscreen doesnt response / volume buttons doesnt work.
badboy47 said:
Yes you will be fine. Before PA 4.3 rom was released, I was using Latest 4.3 bootloader with 4.2.2. I am going to revert to 4.2 as well. I noticed 4.3 battery is really good but sometime touchscreen doesnt response / volume buttons doesnt work.
Click to expand...
Click to collapse
for unresponsive screen go to 'developer options', 'hardware accelerated options', 'disable HW overlays' and select 'always use gpu for screen compositing'. Works for me but setting doesn't seem to stick on reboots.
^^ oh okay thanks but I am already back to the good old 4.2.2 .
Sent from my Nexus 4 using Tapatalk 4
Thank you dude..it works ,, i'm really stress with this unresponsive screen
Just to make sure!
badboy47 said:
If you are going to flash custom ROM; use a toolkit to Root it; flash custom recovery of your choice. Then copy custom ROM to ur phone; go to recovery and flash it. You don't need to downgrade your boot loader.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Hi I´m quite new to this and did recently flash my second custom rom. I went from CM10.1 (4.2.2) back to stock image, and flashed
[AOSP]Official 4.3- S4 Google Edition- Finaly v2.0 - Feel the Experience of Nexus. The phone is running hot and I´m kind of dissapointed with the
lack of tweaks in Google Edition. So I´d like to go back to CM
So if I understand you right I can from 4.3 flash my stock image (from TWRP) which was on 4.2.2? Without worrying.
Did you make a nandroid backup when you were stock? That should be the easiest way to get back to stock. If you didn't then you will need to use odin to flash back to stock.
Sent from my SCH-I605 using Tapatalk
Hi everyone, there is a 1.8mb update for android 4.3. Mine always fails. At first I had CWM and IN HERE I switched to TWRP and it's not working again! Please help
Rooted, Stock rom, TWRP recovery
You need stock recovery also
Sent from my Nexus 4 using Tapatalk 4
Zehlek said:
You need stock recovery also
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Why the stock recovery? And how I do that?
alipashang77 said:
Why the stock recovery? And how I do that?
Click to expand...
Click to collapse
you have made alterations to your phone so its not longer stock. the file you are flashing is for a stock rom and to be flashed in a stock recovery. to flash the update simply re-flash a stock recovery and allow the update to go through. you can also simply wait and flash an updated custom stock rom.
Edit: link deleted....may confuse you
Edit2: Using the toolkits you should be able to find the stock recovery image and flash it back
playya said:
you have made alterations to your phone so its not longer stock. the file you are flashing is for a stock rom and to be flashed in a stock recovery. to flash the update simply re-flash a stock recovery and allow the update to go through. you can also simply wait and flash an updated custom stock rom.
Edit: link deleted....may confuse you
Click to expand...
Click to collapse
I got the idea, ho do I re-flash the stock recovery? any easy way?
alipashang77 said:
I got the idea, ho do I re-flash the stock recovery? any easy way?
Click to expand...
Click to collapse
Try the toolkits you would need the stockrecovery image
I flashed a Kit Kat rom, and before I was having problems with recovery. Now I'm having problems flashing a new ROM. Every time I try to flash a different rom, it says it flashes but it just goes back to the 4.4 rom I flashed first. I can restore a backup just fine, but even from the backup it does the same thing.
Sent from my Nexus 4 using xda app-developers app
EggosEvo said:
I flashed a Kit Kat rom, and before I was having problems with recovery. Now I'm having problems flashing a new ROM. Every time I try to flash a different rom, it says it flashes but it just goes back to the 4.4 rom I flashed first. I can restore a backup just fine, but even from the backup it does the same thing.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
My MAC address keeps changing after reboot, and wifi is screwy no matter what I do. Full Wipe, factory reset, Factory image restore. Its seems the 4.4 roms change things that cant be undone. I now have to have my phone replaced.
Gah. I'd rather not have to have my phone replaced. I feel as if its just 4.4 ROMs though.
Sent from my Nexus 4 using Tapatalk
Bump. I need this fixed.
Sent from my Nexus 4 using xda app-developers app
EggosEvo said:
Bump. I need this fixed.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Try reflasing your recovery. If that doesn't work, then flash the 4.3 factory images.
EggosEvo said:
Bump. I need this fixed.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I had 4.4 ported from n5, and then i flashed a 4.3 custom rom and didn't have any problems...
What custom recovery are u using ?
sergiu9my said:
I had 4.4 ported from n5, and then i flashed a 4.3 custom rom and didn't have any problems...
What custom recovery are u using ?
Click to expand...
Click to collapse
I'm on the latest CWM touch, I believe 6.0.4.3. I haven't actually tried going from the 4.4 rom to a 4.3, but I know I can't go from 4.4 to a different 4.4 rom, or from 4.3 rom to a different 4.4 rom, it just goes to the first one I flashed.
EggosEvo said:
I'm on the latest CWM touch, I believe 6.0.4.3. I haven't actually tried going from the 4.4 rom to a 4.3, but I know I can't go from 4.4 to a different 4.4 rom, or from 4.3 rom to a different 4.4 rom, it just goes to the first one I flashed.
Click to expand...
Click to collapse
Try using the latest twrp.
sergiu9my said:
Try using the latest twrp.
Click to expand...
Click to collapse
Haven't there been people having issues flashing 4.4 with TWRP? Or has Team Win updated it since then?
EggosEvo said:
Haven't there been people having issues flashing 4.4 with TWRP? Or has Team Win updated it since then?
Click to expand...
Click to collapse
Yes it's updated.
http://forum.xda-developers.com/showthread.php?t=2002326
sergiu9my said:
Yes it's updated.
http://forum.xda-developers.com/showthread.php?t=2002326
Click to expand...
Click to collapse
GooManager is telling me that there is no recovery available for my device. That's odd.
If all else fails, download the stock 4.3 image and fastboot flash it, then try whatever other ROM you wanted.
EggosEvo said:
GooManager is telling me that there is no recovery available for my device. That's odd.
Click to expand...
Click to collapse
Here is the flashable zip: https://www.dropbox.com/s/n8li9hq74weq8t6/TWRP-2.6.3.2-mako_flashable.zip
Flash it in recovery and then twrp will be ure default recovery.
Then try to flash a 4.3 rom.
sergiu9my said:
Here is the flashable zip: https://www.dropbox.com/s/n8li9hq74weq8t6/TWRP-2.6.3.2-mako_flashable.zip
Flash it in recovery and then twrp will be ure default recovery.
Then try to flash a 4.3 rom.
Click to expand...
Click to collapse
Successfully flashed PAC with TWRP. Tested PA 4.4, and still flashed the first 4.4 rom i flashed.
EggosEvo said:
Successfully flashed PAC with TWRP. Tested PA 4.4, and still flashed the first 4.4 rom i flashed.
Click to expand...
Click to collapse
Try doing what I suggested if you're still having the revert to original 4.4 issue.
orangekid said:
Try doing what I suggested if you're still having the revert to original 4.4 issue.
Click to expand...
Click to collapse
I won't have access to a computer with ADB until late tonight. But I'll try that and report back either tonight or tomorrow.
Sent from my Nexus 4 using xda app-developers app
EggosEvo said:
I won't have access to a computer with ADB until late tonight. But I'll try that and report back either tonight or tomorrow.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
The only other thing you might try now is flashing any 4.3 or 4.2.2 ROM, reboot, and see if it's now on that one or still on 4.4...
Or is that what you already did with PAC?
You can also manually format /system then /data from TWRP or CWM then manually flash your new ROM.
orangekid said:
The only other thing you might try now is flashing any 4.3 or 4.2.2 ROM, reboot, and see if it's now on that one or still on 4.4...
Or is that what you already did with PAC?
You can also manually format /system then /data from TWRP or CWM then manually flash your new ROM.
Click to expand...
Click to collapse
That's what I did. I went from 4.4 to PAC, and it booted into PAC. Same with CM 10.2. It seems to just be happening with 4.4 roms.
EggosEvo said:
That's what I did. I went from 4.4 to PAC, and it booted into PAC. Same with CM 10.2. It seems to just be happening with 4.4 roms.
Click to expand...
Click to collapse
just manual format /system /data and /boot is the only thing I can think of besides what I've already mentioned.
weird issue...
orangekid said:
just manual format /system /data and /boot is the only thing I can think of besides what I've already mentioned.
weird issue...
Click to expand...
Click to collapse
I just wiped /system and /data, and now the 4.4 PA fails to flash, but CM 10.2 flashed. I'm gonna switch to CWM to see if it'll flash there.
UPDATE: CWM would NOT let me go back to the previous option when asking me to reflash recovery when booting, and it didn't flash PA, so now I'm stuck on the first 4.4 build with no GApps until 9 or 10 tonight. First thing I'm doing when I get home is flashing the factory image.