Flashing a Kernel via Recovery vs ADB - Nexus 5 Q&A, Help & Troubleshooting

I was curious as to any difference between flashing a Kernel via ADB using a boot.img or flashing it as a .zip via recovery. Is there a benefit of one over the other. I've always done it via ADB, but I recently tried via a zip file through TWRP but didn't notice any difference, but wasn't sure if I was just being oblivious or not lol
I heard someone mention that when flashing it via ADB you don't get the Modules that come with the Kernel. Which I don't know if that was BS or not, cause as I stated, after trying it both ways, I didn't notice any features taken away i.e. flashed bricked kernel via ADB and then restored stock kernel and then flashed bricked via TWRP, and I was able to activate DT2W/S2W regardless of the method of flashing, as well as OC capabilities, Fast Charge, etc etc.
Just been curious about this for awhile, and there doesn't seem to be much discussion about it, so was unable to find an answer. Dev's always seem to give you the option to download a boot.img or .zip file, and wasn't sure if htat was just due to giving peopel the choice of preferred flashing method, or because of inherit benefits between the two.

Its simply 2 different options of installation. The final result is the same: a boot.img gets extracted and written onto the appropriate partition of your device.
When you use fastboot to flash the img. the executable on your computer does this directly.
When you use a recovery to flash the zip (which also contains the boot.img), the edify script within the zip gives instructions to the recovery on how and where to write the image to.
There isnt really any advantage to doing one over the other.

Silicon Knight said:
I was curious as to any difference between flashing a Kernel via ADB using a boot.img or flashing it as a .zip via recovery. Is there a benefit of one over the other. I've always done it via ADB, but I recently tried via a zip file through TWRP but didn't notice any difference, but wasn't sure if I was just being oblivious or not lol
I heard someone mention that when flashing it via ADB you don't get the Modules that come with the Kernel. Which I don't know if that was BS or not, cause as I stated, after trying it both ways, I didn't notice any features taken away i.e. flashed bricked kernel via ADB and then restored stock kernel and then flashed bricked via TWRP, and I was able to activate DT2W/S2W regardless of the method of flashing, as well as OC capabilities, Fast Charge, etc etc.
Just been curious about this for awhile, and there doesn't seem to be much discussion about it, so was unable to find an answer. Dev's always seem to give you the option to download a boot.img or .zip file, and wasn't sure if htat was just due to giving peopel the choice of preferred flashing method, or because of inherit benefits between the two.
Click to expand...
Click to collapse
Fastboot is the tool to which you are referring to, not ADB. You use fastboot to flash image files to partitions directly through the bootloader. That being said, there's no difference which method you use, the end result is the same. Using fastboot requires an unlocked bootloader, flashing through the recovery does not. When you flash a zip through the recovery, the proper destination partition is automatically overwritten whereas when you flash an image in fastboot, you have to specify the proper partition. That's the only real difference.

Excuse me, Fastboot is what I meant yes. My bad lol.
Thanks for the info, I figured as much. Im experienced with both methods and understand how they work. Just wasn't sure if there was a benefit over one or the other when it comes to flashing custom kernels. Thanks bro I appreciate the help. I will stick to flashing via fastboot then. I just prefer to do it that way.
I also use flashify sometimes as well. Seems to work pretty good.
Sent from my Nexus 5 using XDA Premium 4 mobile app

Chromium_ said:
Its simply 2 different options of installation. The final result is the same: a boot.img gets extracted and written onto the appropriate partition of your device.
When you use fastboot to flash the img. the executable on your computer does this directly.
When you use a recovery to flash the zip (which also contains the boot.img), the edify script within the zip gives instructions to the recovery on how and where to write the image to.
There isnt really any advantage to doing one over the other.
Click to expand...
Click to collapse
i have a locked bootloader but i have root, can i "flash" throught root explorer overwriting boot.img file?
and reboot?

AXD96 said:
i have a locked bootloader but i have root, can i "flash" throught root explorer overwriting boot.img file?
and reboot?
Click to expand...
Click to collapse
Root explorer is not a flashing tool and no, it cannot modify the kernel
Sent from my Nexus 5 using Tapatalk

rootSU said:
Root explorer is not a flashing tool and no, it cannot modify the kernel
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
maybe a stupid question, but the kernel is all saved in boot.img?

AXD96 said:
maybe a stupid question, but the kernel is all saved in boot.img?
Click to expand...
Click to collapse
Yep Indeed. What you can browse is /sys, which are the "files" the kernel manipulates to do what it wants...
..but browsing here is of no benefit to changing a kernel
Sent from my Nexus 5 using Tapatalk

Unlock your device and just use the a custom recovery.
Sent from my Nexus 5 using Tapatalk

can we change kernel alone
i am using SENSONIC with stock kernel can i change kernel alone.
I want to change to franco kernel . Is it enough installing zip using recovery or i have to do fresh install of the ROM.........
Thanks in advance.

Related

Question about flashing a rom (kernel...?)

ok, so i just rooted my One X (AT&T) running 2.20 using the unlock-bootloader method (only one out there, right? )
i want to flash the latest stable CM10 rom (named cm-10.0.0-evita.zip), but i hear all this stuff about flashing the kernel or the boot.img first before flashing the rom...? i've never rooted/flashed on HTC before, so forgive me if it seems noobish. what i have heard so far is to flash the boot.img from the rom i want to flash while in fastboot from my computer, then transfer the zip to my phone and flash the zip from TWRP. this is what i have picked up from hours of web-crawling, so please correct me if i am wrong
and *sigh* yes, i did use the search bar. i was unable to find any forums relating to my specific question. i did find one, however, under the quad-core tegra One X (the international version) and didn't want to risk bricking my phone because of differences between the AT&T and Int'l versions.
Well. I'm gonna first say you didn't search very hard as there are 100,000 threads asking this same questions. BUT I will be nice today.
Open the cm10.zip and extract the boot.img from it and place them both on your sd card. No need to rezip the rom, just leave it as is.
With your phone in fastboot, open a command prompt in your fastboot folder and type fastboot flash boot boot.img.
Boot into TWRP and flash the cm10.zip
area51avenger said:
Well. I'm gonna first say you didn't search very hard as there are 100,000 threads asking this same questions. BUT I will be nice today.
Open the cm10.zip and extract the boot.img from it and place them both on your sd card. No need to rezip the rom, just leave it as is.
With your phone in fastboot, open a command prompt in your fastboot folder and type fastboot flash boot boot.img.
Boot into TWRP and flash the cm10.zip
Click to expand...
Click to collapse
ok, thanks so much
i figured there were forums for this already but i've been looking for a week and a half and gathering all the information i needed for this moment. sorry to waste your time if it did, and thanks for the generosity i really do appreciate it
Or use flashgui app.. Its in apps and themes.. Download cm10 and gapps from your phone. Open flashgui. Browse and find cm10. Select it and let the app flash it.. IMMEDIATELY after boot into twrp, flash entire rom, once successful immediately flash gapps. Boot system and profit
Sent from my One X using Tapatalk 2
InflatedTitan said:
Or use flashgui app.. Its in apps and themes.. Download cm10 and gapps from your phone. Open flashgui. Browse and find cm10. Select it and let the app flash it.. IMMEDIATELY after boot into twrp, flash entire rom, once successful immediately flash gapps. Boot system and profit
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
thanks for the info, but i already got to flashing it in twrp. i'll keep that app in mind for later, though
dont i "wipe cache/dalvik" after flashing the rom?
ok, please disregard my last post. after restoring my backup (thank GOD i made it ) and re-flashing AFTER i cleared caches and did a factory reset, i am in CM10 thanks for everyone's help, mods this thread can be closed

how to update to 4.4.x after this... New to android

First of all, I have been reading this forum for about two weeks and just registered in order to get some help as I do not want to break my one week old nexus 5.
From my reading, the updates can be done in quite different ways and because of that I want to be sure what I should do.
I started by:
- root the mobile with cf-auto root. It did everything for me, got the superuser icon automatically
- installed clockwork mod and I have the custom recovery. By the way, I made a backup with it but where was it written? I want to copy it to my pc.
- other than that, I have installed some root only apps like rom manager, greenify, root Explorer, etc. I supported those developers with purchase. Those guys deserve it.
Anyway, i am looking for the safe way to update to 4.4.1. I read some members saying they lost root after the update, others lost something else (I am referring to the thread on nexus 5 general forum).
Can you help me? What path shall I go? Thanks a lot.
To update you'll basically have to go back to stock in a way. By that I mean you can either flash the System.img file from the Factory Image and then update using the update files for 4.4.1 by flashing it in recovery (via Sideload) and then just root again. OR you can install an updated "Stock" 4.4.1 image from the development section and root that.
cesar.maranhao said:
- installed clockwork mod and I have the custom recovery. By the way, I made a backup with it but where was it written? I want to copy it to my pc.
Click to expand...
Click to collapse
Hi, your backups are in /mnt/shell/emulated/clockworkmod/backup/
Copy to your PC with 'adb pull /mnt/shell/emulated/clockworkmod/backup'
Cheers
shotta35 said:
To update you'll basically have to go back to stock in a way. By that I mean you can either flash the System.img file from the Factory Image and then update using the update files for 4.4.1 by flashing it in recovery (via Sideload) and then just root again. OR you can install an updated "Stock" 4.4.1 image from the development section and root that.
Click to expand...
Click to collapse
i sense i am getting somewhere but how do i do that? i am new to this and been reading a lot but the first time all seems very vague. i need a little more help from you!
lets assume i want to just apply the 4.4.1 update (maybe this is the easiest way for now). how do i do it?
also, after the update succeds, i need to root again correct? what happens to all the apps i have right now with root permissions? do they stop working until i root again and give them root privileges again? can i use the cf auto root again?
also, i am on ART, i thought of letting you know since that can cause some problems updating(??)
finistere said:
Hi, your backups are in /mnt/shell/emulated/clockworkmod/backup/
Copy to your PC with 'adb pull /mnt/shell/emulated/clockworkmod/backup'
Cheers
Click to expand...
Click to collapse
thanks!
one more thing...
can't i copy that folder like a regular folder? just copy paste?
or move that folder (with root explorer) to my dropbox folder?
cesar.maranhao said:
i sense i am getting somewhere but how do i do that? i am new to this and been reading a lot but the first time all seems very vague. i need a little more help from you!
lets assume i want to just apply the 4.4.1 update (maybe this is the easiest way for now). how do i do it?
also, after the update succeds, i need to root again correct? what happens to all the apps i have right now with root permissions? do they stop working until i root again and give them root privileges again? can i use the cf auto root again?
also, i am on ART, i thought of letting you know since that can cause some problems updating(??)
Click to expand...
Click to collapse
If you want to apply the new update it all depends on your current setup. I gave you vague options because I don't know what you've done to your phone. If you've only rooted and not changed any of the files in system then it's easy to just flash the update with the recovery. You can download the update and then start recovery (look it up). Once in recovery start ADB sideload and connect to your PC (this assumes you already have working ADB, if not.... look it up ). To sideload you just need to adb sideload filename.zip. You can probably use WugFresh's Toolkit to also sideload but I generally don't use those so dunno what they do these days. Much easier to learn and understand what it does then do it yourself.
If you have a custom recovery you might just be able to flash the update with the recovery like you normally flash any zip in recovery.
cesar.maranhao said:
thanks!
one more thing...
can't i copy that folder like a regular folder? just copy paste?
or move that folder (with root explorer) to my dropbox folder?
Click to expand...
Click to collapse
You can just copy it, no need to use ADB but this is why it's good to know how to use ADB.
shotta35 said:
If you want to apply the new update it all depends on your current setup. I gave you vague options because I don't know what you've done to your phone. If you've only rooted and not changed any of the files in system then it's easy to just flash the update with the recovery. You can download the update and then start recovery (look it up). Once in recovery start ADB sideload and connect to your PC (this assumes you already have working ADB, if not.... look it up ). To sideload you just need to adb sideload filename.zip. You can probably use WugFresh's Toolkit to also sideload but I generally don't use those so dunno what they do these days. Much easier to learn and understand what it does then do it yourself.
If you have a custom recovery you might just be able to flash the update with the recovery like you normally flash any zip in recovery.
You can just copy it, no need to use ADB but this is why it's good to know how to use ADB.
Click to expand...
Click to collapse
thanks for the reply. i am reading on the adb sideload right now... i already have the update zip inside the platform tools. however, in the command prompt, it says my device is unauthorized (i have both the usb debugging and unknown sources ticked). the nexus 5 is connected as MTP.
any clues?
about what i have done to my nexus, i applied the cf autoroot, installed clockwork mod... nothing much besides some play store apps..
as for this paragraph:
"If you have a custom recovery you might just be able to flash the update with the recovery like you normally flash any zip in recovery. "
i have never done it, hence all these questions!
cesar.maranhao said:
thanks for the reply. i am reading on the adb sideload right now... i already have the update zip inside the platform tools. however, in the command prompt, it says my device is unauthorized (i have both the usb debugging and unknown sources ticked). the nexus 5 is connected as MTP.
any clues?
about what i have done to my nexus, i applied the cf autoroot, installed clockwork mod... nothing much besides some play store apps..
as for this paragraph:
"If you have a custom recovery you might just be able to flash the update with the recovery like you normally flash any zip in recovery. "
i have never done it, hence all these questions!
Click to expand...
Click to collapse
You do it from Recovery. So just copy the file to the phone in some folder. You can't update the phone with it running. So reboot to CWM and then choose Install from ZIP then find the file on your storage and then choose update. That may or may not work as I said depending.
-----------------
Plenty of these questions around... check them out first.
http://forum.xda-developers.com/showthread.php?t=2561198
http://forum.xda-developers.com/showthread.php?p=47369234
http://forum.xda-developers.com/showthread.php?t=2561076
shotta35 said:
If you want to apply the new update it all depends on your current setup. I gave you vague options because I don't know what you've done to your phone. If you've only rooted and not changed any of the files in system then it's easy to just flash the update with the recovery. You can download the update and then start recovery (look it up). Once in recovery start ADB sideload and connect to your PC (this assumes you already have working ADB, if not.... look it up ). To sideload you just need to adb sideload filename.zip. You can probably use WugFresh's Toolkit to also sideload but I generally don't use those so dunno what they do these days. Much easier to learn and understand what it does then do it yourself.
If you have a custom recovery you might just be able to flash the update with the recovery like you normally flash any zip in recovery.
You can just copy it, no need to use ADB but this is why it's good to know how to use ADB.
Click to expand...
Click to collapse
cesar.maranhao said:
thanks for the reply. i am reading on the adb sideload right now... i already have the update zip inside the platform tools. however, in the command prompt, it says my device is unauthorized (i have both the usb debugging and unknown sources ticked). the nexus 5 is connected as MTP.
any clues?
about what i have done to my nexus, i applied the cf autoroot, installed clockwork mod... nothing much besides some play store apps..
as for this paragraph:
"If you have a custom recovery you might just be able to flash the update with the recovery like you normally flash any zip in recovery. "
i have never done it, hence all these questions!
Click to expand...
Click to collapse
shotta35 said:
You do it from Recovery. So just copy the file to the phone in some folder. You can't update the phone with it running. So reboot to CWM and then choose Install from ZIP then find the file on your storage and then choose update. That may or may not work as I said depending.
-----------------
Plenty of these questions around... check them out first.
http://forum.xda-developers.com/showthread.php?t=2561198
http://forum.xda-developers.com/showthread.php?p=47369234
http://forum.xda-developers.com/showthread.php?t=2561076
Click to expand...
Click to collapse
yes, i have been reading those topics and many others.. i managed to solve the adb device unauthorized anyway. just flashed the 4.4.1 zip file under clockwork mod recover.. android is upgrading at the moment. lets see if everything is work as it should.
No need to sideload adb bla bla..
copy the OTA zip into the phone, and just flash it in CWM (install file from internal storage).. 1 minute and done.
You'll get error status 7 at checking if you changed something in system (apart from rooting), else you shouldn't have any problem.
RusherDude said:
No need to sideload adb bla bla..
copy the OTA zip into the phone, and just flash it in CWM.. 1 minute and done.
You'll get error status 7 at checking if you changed something in system (apart from rooting), else you shouldn't have any problem.
Click to expand...
Click to collapse
yes, everything is fine. 4.4.1 loaded fine without any errors. i have root checker and when i tested, it says i do not have proper root access. i also lost my clockwork mod recovery.
i am now checking into it to see what needs to be done to gain root access again and get the custom recovery as it was before the update.
cesar.maranhao said:
yes, everything is fine. 4.4.1 loaded fine without any errors. i have root checker and when i tested, it says i do not have proper root access. i also lost my clockwork mod recovery.
i am now checking into it to see what needs to be done to gain root access again and get the custom recovery as it was before the update.
Click to expand...
Click to collapse
You need to flash the recovery again via fastboot (youll lose it every time, unless you flash the flashable recovery ZIP just after flashing the OTA and before rebooting the phone).You'll have this problem every OTA unless you flash the zipped version everytime.
I'd recommend the easy way to root, get the SuperSU binaries and flash them through the custom recovery and you're done..
RusherDude said:
No need to sideload adb bla bla..
copy the OTA zip into the phone, and just flash it in CWM (install file from internal storage).. 1 minute and done.
You'll get error status 7 at checking if you changed something in system (apart from rooting), else you shouldn't have any problem.
Click to expand...
Click to collapse
RusherDude said:
You need to flash the recovery again via fastboot (youll lose it every time, unless you flash the flashable recovery ZIP just after flashing the OTA and before rebooting the phone).You'll have this problem every OTA unless you flash the zipped version everytime.
I'd recommend the easy way to root, get the SuperSU binaries and flash them through the custom recovery and you're done..
Click to expand...
Click to collapse
i see. things are starting to make sense for me.
before reading you post, i tried to get the clockwork mod recovery through the Rom Manager App. it failed. i am now looking for those files you mentioned.
EDIT: i am at the clockworkmod recovery website... is the file i want an IMG?
cesar.maranhao said:
i see. things are starting to make sense for me.
before reading you post, i tried to get the clockwork mod recovery through the Rom Manager App. it failed. i am now looking for those files you mentioned.
EDIT: i am at the clockworkmod recovery website... is the file i want an IMG?
Click to expand...
Click to collapse
You'd only be looking for the supersu binaries, since you already have the recovery IMG from te previous time, right? (the one that you need for fastboot).
EDIT: Yes, IMG files are for fastboot, ZIP files for recovery.
RusherDude said:
You'd only be looking for the supersu binaries, since you already have the recovery IMG from te previous time, right? (the one that you need for fastboot).
EDIT: Yes, IMG files are for fastboot, ZIP files for recovery.
Click to expand...
Click to collapse
but how do i install it? when i go into recovery it only gives me 4 options:
reboot system now
apply update from adb
wipe cache/factory reset
wipe cache partition
i am lost
cesar.maranhao said:
but how do i install it? when i go into recovery it only gives me 4 options:
reboot system now
apply update from adb
wipe cache/factory reset
wipe cache partition
i am lost
Click to expand...
Click to collapse
That's the stock recovery, you can't do nothing from there.
You need to flash the recovery via fastboot (didn't you do that the first time to get your custom recovery..?)
Check this tutorial mate: http://forum.xda-developers.com/showthread.php?t=2507905
RusherDude said:
You'd only be looking for the supersu binaries, since you already have the recovery IMG from te previous time, right? (the one that you need for fastboot).
EDIT: Yes, IMG files are for fastboot, ZIP files for recovery.
Click to expand...
Click to collapse
RusherDude said:
That's the stock recovery, you can't do nothing from there.
You need to flash the recovery via fastboot (didn't you do that the first time to get your custom recovery..?)
Check this tutorial mate: http://forum.xda-developers.com/showthread.php?t=2507905
Click to expand...
Click to collapse
no, i got the custom recovery when i installed clockworkmod recovery from the play store. i am now reading the thread you linked me! thanks!
cesar.maranhao said:
no, i got the custom recovery when i installed clockworkmod recovery from the play store. i am now reading the thread you linked me! thanks!
Click to expand...
Click to collapse
done it! i now have root again and the clockworkmod custom recovery! nice!
:good:
RusherDude said:
You need to flash the recovery again via fastboot (youll lose it every time, unless you flash the flashable recovery ZIP just after flashing the OTA and before rebooting the phone).You'll have this problem every OTA unless you flash the zipped version everytime.
I'd recommend the easy way to root, get the SuperSU binaries and flash them through the custom recovery and you're done..
Click to expand...
Click to collapse
from where can i get the flashable clokwork mod recovery zip file?
i am going to apply the 4.4.2 update now and will be doing it this way:
from the recovery apply the 4.4.2 zip. after this apply the supersu zip. i want to install the custom recovery zip too so when the phone restarts everything will be configured. is this possible?
RusherDude said:
You need to flash the recovery again via fastboot (youll lose it every time, unless you flash the flashable recovery ZIP just after flashing the OTA and before rebooting the phone).You'll have this problem every OTA unless you flash the zipped version everytime.
I'd recommend the easy way to root, get the SuperSU binaries and flash them through the custom recovery and you're done..
Click to expand...
Click to collapse
well, it seems i haven't lost my custom recovery. was it because i installed the supersu before rebooting?

[Q] how to reflesh stock kernel?

Ok so i flashed francos kernel trough FKU updater app and i want to go back to stock just to compare the battery life and some stuff again and to decide what to use.
How can i flash stock kernel back, do i flash all factory images or is there .zip file to flash trough recovery, or there is another way to do this? thanks for your replays.
Hi,
Stock kernel here (recovery zip file): http://forum.xda-developers.com/showthread.php?p=47269605.
You can also take a look here to fastboot the boot.img (kernel): http://forum.xda-developers.com/showthread.php?t=2513701.
Alexandar92zr said:
Ok so i flashed francos kernel trough FKU updater app and i want to go back to stock just to compare the battery life and some stuff again and to decide what to use.
How can i flash stock kernel back, do i flash all factory images or is there .zip file to flash trough recovery, or there is another way to do this? thanks for your replays.
Click to expand...
Click to collapse
boot.img is the kernel. If you have the factory images you can just fastboot flash that,
Hammer_Of_The_Gods said:
Hi,
Stock kernel here (recovery zip file): http://forum.xda-developers.com/showthread.php?p=47269605.
You can also take a look here to fastboot the boot.img (kernel): http://forum.xda-developers.com/showthread.php?t=2513701.
Click to expand...
Click to collapse
ok so i just download the zip and flash trough twrp right?
rootSU said:
boot.img is the kernel. If you have the factory images you can just fastboot flash that,
Click to expand...
Click to collapse
oh ok did not know that im quite new to this, but now i know thanks for information.
Alexandar92zr said:
ok so i just download the zip and flash trough twrp right?
Click to expand...
Click to collapse
That's right, download the right zip (4.4 or 4.4.1/4.4.2) put it "in your sdcard", reboot in recovery, flash and reboot, that's all
Hammer_Of_The_Gods said:
That's right, download the right zip (4.4 or 4.4.1/4.4.2) put it "in your sdcard", reboot in recovery, flash and reboot, that's all
Click to expand...
Click to collapse
thanks man i clicked on that thanks button
Alexandar92zr said:
thanks man i clicked on that thanks button
Click to expand...
Click to collapse
No worries, thanks
Last thing since you came from Franco kernel (the following procedure is specific):
The Gingerbread Man said:
Return to stock romz
Franco's kernel changes these system files below, so to change them back you can remove the .bak extension, or fastboot system.IMG and boot.IMG from a Google factory image which is probably easier and faster.
1 - Rename /system/lib/hw/power.msm8974.so.bak to /system/lib/hw/power.msm8974.so
2 - Rename /system/bin/thermal-engine-hh-bak to /system/bin/thermal-engine-hh
3 - Reboot to the boot loader and flash stock Kernel by downloading the Nexus images and then fastboot flash boot boot.img
...
Click to expand...
Click to collapse
So before flashing the stock kernel in recovery do the step 1 and 2 (even after if you forgot, it should be good).
Alexandar92zr said:
thanks man i clicked on that thanks button
Click to expand...
Click to collapse
May i suggest you start reading up before you get into serious rouble. Read the first 4 threads in the General section.
Verstuurd vanaf mijn Nexus 5 met Tapatalk
Hammer_Of_The_Gods said:
No worries, thanks
Last thing since you came from Franco kernel (the following procedure is specific):
So before flashing the stock kernel in recovery do the step 1 and 2 (even after if you forgot, it should be good).
Click to expand...
Click to collapse
ok lets see if i understood right.
im comeing from the stock rom just with francos kernel and now to go back to the stock i need to do step 1 and 2, how do i rename that files i connect my phone to pc or i need to download some file menager that can see that files? and about step 3 do i need to flash boot.img via fast boot or i can do it trough twrp as well?
sorry about the many questions but i do not want do do something wrong
Alexandar92zr said:
ok lets see if i understood right.
im comeing from the stock rom just with francos kernel and now to go back to the stock i need to do step 1 and 2, how do i rename that files i connect my phone to pc or i need to download some file menager that can see that files? and about step 3 do i need to flash boot.img via fast boot or i can do it trough twrp as well?
sorry about the many questions but i do not wont do do something wrong
Click to expand...
Click to collapse
With a file explorer, directly from your phone, (Root Explorer, Es File Explorer, etc...) follow the path to the files in point 1 and 2, rename the files and save. Then reboot in recovery and flash the stock kernel if you want to flash it via recovery (equal to step 3).
If you are not used with this kind of stuff (modify system files by yourself), flash the system.img and boot.img by following the link I provided above (http://forum.xda-developers.com/showthread.php?t=2513701).
Hammer_Of_The_Gods said:
With a file explorer, directly from your phone, (Root Explorer, Es File Explorer, etc...) follow the path to the files in point 1 and 2, rename the files and save. Then reboot in recovery and flash the stock kernel if you want to flash it via recovery (equal to step 3).
If you are not used with this kind of stuff (modify system files by yourself), flash the system.img and boot.img by following the link I provided above (http://forum.xda-developers.com/showthread.php?t=2513701).
Click to expand...
Click to collapse
i founded the files that i need to rename via es file explorer and now i understand it all and im not confused anymore about how to get stock kernel back.
im not used to this stuff yet because i rooted my phone yesterday and im quite new to this because last device i rooted and flashed lots of custom roms and stuff is to HD2 so i know the basic stuff but not much
and one of the topic question. why does my colors look a little diferent when i flashed the francos kernel? i know that there is something about color profiles etc. but i do not know where to start and look into that
Alexandar92zr said:
i founded the files that i need to rename via es file explorer and now i understand it all and im not confused anymore about how to get stock kernel back.
im not used to this stuff yet because i rooted my phone yesterday and im quite new to this because last device i rooted and flashed lots of custom roms and stuff is to HD2 so i know the basic stuff but not much
and one of the topic question. why does my colors look a little diferent when i flashed the francos kernel? i know that there is something about color profiles etc. but i do not know where to start and look into that
Click to expand...
Click to collapse
Okay, so all is fine to go back to stock, take your time and read all closely
About the colors, take a look here: http://forum.xda-developers.com/showpost.php?p=49561443 (links for profiles are down, for example: http://192.227.135.147/N5_ColorProfiles/Latest_Profiles/ from vomer).
Hammer_Of_The_Gods said:
Okay, so all is fine to go back to stock, take your time and read all closely
About the colors, take a look here: http://forum.xda-developers.com/showpost.php?p=49561443 (links for profiles are down, for example: http://192.227.135.147/N5_ColorProfiles/Latest_Profiles/ from vomer).
Click to expand...
Click to collapse
thanks i will look into this.
I made a stock kernel backup on Franco app and used it to restore back to stock kernel after using Franco was this process ok
Sent from my Nexus 5 using xda app-developers app

Screen went blank after flashing boot.img

Meaning to install CyanogenMod I followed CyanogenMod wiki instructions (can't post link here)
Only that I have TWRP instead of CWM.
When I got to installing "CyanogenMod from recovery" I got a message saying that the pushing had failed because permissions did not allow it.
So I tried a solution they suggested for a similar message which did not work, and then I read the note at the bottom that says the kernel should be flashed via fastboot, I flashed it but now it's just blank (I guess because it has an alien kernel and the rest is the same)
I dont have a copy of my previous boot.img
Not enough information provided, please provide the following:
-Your bootloader details
-Your current TWRP version
-The exact filename of the ROM zip you flashed
-Is the phone powering on at all
Sent from my Evita
timmaaa said:
Not enough information provided, please provide the following:
-Your bootloader details HBOOT 2.15.0000 S-OFF
-Your current TWRP version 2.6.3
-The exact filename of the ROM zip you flashedcm-10.2.1-evita.zip I tried to flash it but couldnt do it on adb only flash the boot.img
-Is the phone powering on at all yes it is, it goes through the start screen and when it would show the icons it's just black with the backlight on
Sent from my Evita
Click to expand...
Click to collapse
Answers
What do you mean you couldn't do it on adb? Do what on adb? You don't use adb to flash a ROM.
Sent from my Evita
timmaaa said:
What do you mean you couldn't do it on adb? Do what on adb? You don't use adb to flash a ROM.
Sent from my Evita
Click to expand...
Click to collapse
I mean to push the rom on the root of the sdcard: look at the instructions I followed:
Place the CyanogenMod rom .zip file on the root of the SD card using adb:
Transfer your file(s): adb push YOURROMZIP.zip /sdcard/
If you boot directly to recovery and have an internal sdcard, you may need to run adb shell mount /sdcard or mount data through the recovery menu before transferring.
If you see "error: device not found" there is likely a driver issue on the PC.
If you see "error: insufficient permissions for device", try "adb kill-server" and then run "adb devices" to see if the device is attached.
On some devices, the zip file can be copied to the device using standard USB Mass Storage or MTP support. Boot the device normally and transfer the file to it.
Optional: Place any supplemental packages (e.g. Google Apps[1] or kernel) .zip file(s) on the root of the SD card.
Boot to recovery mode on the device by holding With the device powered down, hold the Volume Down and Power buttons until HBOOT appears, then release the buttons. Navigate using the volume keys and select RECOVERY using the Power key..
Once the device boots into the ClockworkMod Recovery, use the physical volume buttons to move up and down. On most devices, the power button is used to confirm your selection, although for some devices the power button is used as a "back" button to go up one level, in which case the home button is used to confirm the selection.
Optional/Recommended: Select backup and restore to create a backup of the current installation on the device. If this option is missing, it's likely because the stock ROM has overwritten your custom recovery on boot.
Select the option to wipe data/factory reset.
Select install zip from sdcard.
Select choose zip from sdcard.
Select the CyanogenMod file you placed on the sdcard. You will then need to then confirm that you do wish to flash this file.
Optional: Install any additional packages you wish using the same method.
Once the installation has finished, return back to the main menu, and select the reboot system now option. The device should now boot into CyanogenMod.
Click to expand...
Click to collapse
And the note I mentioned:
Note:
This device, if unlocked with HTC Dev Unlock, MUST have its kernel flashed via fastboot! Extract the boot.img from the rom zip and flash using fastboot flash boot boot.img
Click to expand...
Click to collapse
dvdmrn said:
I mean to push the rom on the root of the sdcard: look at the instructions I followed:
Click to expand...
Click to collapse
So you never actually flashed the ROM but you flashed the boot.img from the ROM zip anyway? No wonder it isn't working, you've flashed an incompatible boot.img onto whatever ROM you previously had installed (which is still installed by the way because flashing a boot.img does not flash a ROM).
All you needed to do was mount your sd card using TWRP (menu/mount/mount usb storage) and copy the ROM zip across, then install it. You have s-off so you don't ever need to flash the boot.img separately.
I really think you need to do some research, it seems you lack even a basic understanding of what you're doing. You don't know what a boot.img is or what it does or how or why you would need to flash it. You don't seem to know how to use your custom recovery. You don't seem to know how to install a ROM.
A lack of knowledge is almost always what leads to somebody bricking their phone, which I'm sure you don't want to happen. Do yourself a favour and spend the next couple of days reading up so you have a better understanding of modified devices. A great place to start would be my Evita FAQ thread and my How-To Guide For Beginners thread, you'll find both in my signature.
Sent from my Evita
---------- Post added at 06:17 AM ---------- Previous post was at 06:14 AM ----------
dvdmrn said:
And the note I mentioned:
Click to expand...
Click to collapse
I'm not sure where you found that note but it isn't entirely correct. Only Evitas with s-on and a hboot greater than 1.09 need to flash the boot.img via fastboot.
Sent from my Evita
timmaaa said:
So you never actually flashed the ROM but you flashed the boot.img from the ROM zip anyway? No wonder it isn't working, you've flashed an incompatible boot.img onto whatever ROM you previously had installed (which is still installed by the way because flashing a boot.img does not flash a ROM).
All you needed to do was mount your sd card using TWRP (menu/mount/mount usb storage) and copy the ROM zip across, then install it. You have s-off so you don't ever need to flash the boot.img separately.
I really think you need to do some research, it seems you lack even a basic understanding of what you're doing. You don't know what a boot.img is or what it does or how or why you would need to flash it. You don't seem to know how to use your custom recovery. You don't seem to know how to install a ROM.
A lack of knowledge is almost always what leads to somebody bricking their phone, which I'm sure you don't want to happen. Do yourself a favour and spend the next couple of days reading up so you have a better understanding of modified devices. A great place to start would be my Evita FAQ thread and my How-To Guide For Beginners thread, you'll find both in my signature.
Sent from my Evita
---------- Post added at 06:17 AM ---------- Previous post was at 06:14 AM ----------
I'm not sure where you found that note but it isn't entirely correct. Only Evitas with s-on and a hboot greater than 1.09 need to flash the boot.img via fastboot.
Sent from my Evita
Click to expand...
Click to collapse
This is where it's from
wiki cyanogenmod org / w / Install_CM_for_evita
I'm sorry for having hurried and done that but I couldn't flash the ROM and there were no more instructions, I've been reading for the last months, and even though I thought replacing the kernel could not be the best idea, it was the only idea I could get from those instructions and I thought maybe the kernel would have to be moved first for some reason. Anyway, thank you very much for your patience, I have to do it today because I have to travel and at&t limitations on the network -since it forces 4G- won't allow me to use my current carrier. I tried just moving the ROM by mounting and it worked. Thanks man

[5.0] Nexus 5 Refuses To Flash OTA or Different ROM's

Hello,
So I just discovered this while trying to flash the 5.0.1 OTA from 5.0. I'm rooted on LRX21O via the Nexus Root Toolkit 1.9.9 (which is what I've always used in the past with no issues).
1 Tried flashing the OTA via Google notification push. It reboot, and no changes occur.
2 Fine - I try to use the Root Toolkit again. Boots into bootloader, appears to flash the radio and other necessary components. Reboots - no changes occur.
3 I then tried to just download the 5.0.1 package and flash everything manually via adb. Everything appears to go smoothly, and upon bootup Android updates all of its apps - still nothing. I appear to be completely stuck on LRX21O without any way to reflash stock or OTA's.
Anyone have any clue why this is occurring or have heard of such an issue before?
Thanks all.
Just flash factory images. With fastboot/flash-all script.
https://developers.google.com/android/nexus/images
You flash these in fastboot not adb
Sent from my Nexus 5 using Tapatalk
Did you not understand? I did flash in boot loader USING adb on my computer. All that bat script does is just automate the flashing of each image for you (system, radio, etc) so this is not helpful. I know how to flash, but flashing seems to have no effect despite successfully flashing via manually installing or just using the script
Sane116 said:
Did you not understand? I did flash in boot loader USING adb on my computer.
Click to expand...
Click to collapse
You use fastboot in bootloader, not adb.
I'm not the one asking for help. Anyways, carry on.
Your device's /system partition is tampered (you say you rooted it) and thus the OTA fails. Flash the 5.0 factory image (LRX21O) WITHOUT rooting/flashing kernels/whatever and then use the OTA zip to do adb sideload in the stock recovery to update to 5.0.1 LRX22C.
Manually use fastboot commands to flash system.img and boot.img of the full 5.0.1 factory image (not script). post the output please
I'm not the one asking for help. Anyways, carry on.
Click to expand...
Click to collapse
Sorry about that - didn't mean to come across snippy
It worked this time with fastboot. For future reference can this be done the same way with the OTA update zip instead of reflashing the entire image?
Sane116 said:
Sorry about that - didn't mean to come across snippy
It worked this time with fastboot. For future reference can this be done the same way with the OTA update zip instead of reflashing the entire image?
Click to expand...
Click to collapse
No, but if your phone is setup correctly you can sideload the ota zip in the stock recovery
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
No, but if your phone is setup correctly you can sideload the ota zip in the stock recovery
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Would you mind explaining this? I've used sideload in cwm and twrp before but I'm unsure of how to operate anything within stock recovery. adb won't even connect while in recovery. I would like to just remain on unrooted stock until xposed eventually get's developed for ART and flash zips that way.
Sane116 said:
Would you mind explaining this? I've used sideload in cwm and twrp before but I'm unsure of how to operate anything within stock recovery. adb won't even connect while in recovery. I would like to just remain on unrooted stock until xposed eventually get's developed for ART and flash zips that way.
Click to expand...
Click to collapse
Sideloading in the stock recovery works much the same as in a custom recovery. Boot into the stock recovery and there is an option to sideload. Then on your pc in a command window you type adb sideload update.zip. or whatever the file name is that you're trying to sideload. Obviously, if you can't get adb to recognize your device that's a problem. But that's a separate driver issue.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Sideloading in the stock recovery works much the same as in a custom recovery. Boot into the stock recovery and there is an option to sideload. Then on your pc in a command window you type adb sideload update.zip. or whatever the file name is that you're trying to sideload. Obviously, if you can't get adb to recognize your device that's a problem. But that's a separate driver issue.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
How can this be possible though without a custom recovery with the sideload feature? Stock recovery is essentially unusable as it just displays a picture of a dead android on a black screen.
Perhaps we're on different pages, or am I just confused still?
sideloading an OTA update from stock recovery
Hello, to make it work you will need to use the Google USB drivers you downloaded when you go into stock recovery then press the power button and volume up once then you will see a menu option with the "install update from adb option select this and plug in your phone to the computer. After this is done you will need to go to device manager and install the USB drivers from the Google USB drivers you downloaded. at this point after that is done you then go into the folder that has ADB installed and use adb sideload filename.zip
at this point your phone will accept the ota update package and you wont lose any data, I hope this helps..
-cs
Sane116 said:
How can this be possible though without a custom recovery with the sideload feature? Stock recovery is essentially unusable as it just displays a picture of a dead android on a black screen.
Perhaps we're on different pages, or am I just confused still?
Click to expand...
Click to collapse
When you get the dead android you need to press vol up and then press and release power. That'll get you into the stock recovery. It's stupid and I don't know why they made it that way
Sent from my Nexus 9 using XDA Free mobile app
thanks all, can't believe i never knew that volumeup+power got me into stock recovery options.
new issue: sideload works all well and perfect, but how can I bypass the "signature verification failed" flag that kicks me from the zip install every time?
Sane116 said:
thanks all, can't believe i never knew that volumeup+power got me into stock recovery options.
new issue: sideload works all well and perfect, but how can I bypass the "signature verification failed" flag that kicks me from the zip install every time?
Click to expand...
Click to collapse
Well you can't. The limitation of the stock recovery is you can only flash files signed by Google. That's why you need a custom recovery to flash most files
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Well you can't. The limitation of the stock recovery is you can only flash files signed by Google. That's why you need a custom recovery to flash most files
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
So can I just flash twrp with fastboot and go about that method? I believe it can bypass the signature. I am unlocked without root currently.
Sane116 said:
So can I just flash twrp with fastboot and go about that method? I believe it can bypass the signature. I am unlocked without root currently.
Click to expand...
Click to collapse
If you're trying to flash the update.zip to 5.0.1 you need to do that in the stock recovery. It will not work in twrp or cwm. I'm not sure what you're trying to do right now
Sent from my Nexus 9 using XDA Free mobile app
my apologies.
so originally i wanted to just flash the OTA. ended up performing a fresh install and un-rooted. but there's a few unsigned zips i like to have installed.
So I think I'm going to re-root, flash twrp, install my zips, and leave it at that. i'll just flash stock recovery whenever I need the OTA which should be quick now that I know what to do.
hope that sounds correct. thanks for all the help!

Categories

Resources