Related
EDIT: Thanks everyone for the assistance in acquiring it. All others looking for a copy can refer to this post.
NeoStuey said:
http://dl.dropbox.com/u/29251275/bootanimation.zip
Here you go, though I'd take the excellent Transformer boot animation over stock any day.
Click to expand...
Click to collapse
Original post:
I'm looking for a copy of the original boot animation for my Transformer. I'm not impressed by the custom animations, and just want something clean.
Anybody know how to get it?
Click to expand...
Click to collapse
Dont you have a backup of a rom after you got root on it???
Pull it out there
although you might have too perform: "unyaffs system.img"
unyaffs
I don't have a system.img file, I just have system.ext4 from one of the rooted ROMs repackaged for CWM, and a blob file from the stock Asus ROM.
earlyberd said:
I'm looking for a copy of the original boot animation for my Transformer. I'm not impressed by the custom animations, and just want something clean.
Anybody know how to get it?
Click to expand...
Click to collapse
If you followed the guides to install a custom animation, they tell you how to remove the one you flashed so you have the original back. Unless you flashed a custom rom with it pre-packaged I suppose. You could always flash a stock rom and rip it using ADB though.
Yeah, I flashed straight to a custom ROM without grabbing a backup of the stock animation. I guess I'll nandroid and pull from a stock ROM through adb.
down load the stock rom, extract bootanimation.zip from system/media
push it to system/media or data/local
you could also use root explorer to move the file to the proper location
http://dl.dropbox.com/u/29251275/bootanimation.zip
Here you go, though I'd take the excellent Transformer boot animation over stock any day.
NeoStuey said:
http://dl.dropbox.com/u/29251275/bootanimation.zip
Here you go, though I'd take the excellent Transformer boot animation over stock any day.
Click to expand...
Click to collapse
Thanks. At this point I've already gone and flashed a stock ROM to pull it myself, but this will help other users that also want the stock boot animation.
earlyberd said:
Thanks. At this point I've already gone and flashed a stock ROM to pull it myself, but this will help other users that also want the stock boot animation.
Click to expand...
Click to collapse
you didn't have to actually flash the rom, just down load and extract.
Sent from my Transformer TF101 using Tapatalk
baseballfanz said:
you didn't have to actually flash the rom, just down load and extract.
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
With what tool? It's not like Asus was kind enough to bundle it all in a convenient zip file. Extracting the stock update zip file leaves you with a big file simply named "blob". How the heck do I open that? And if I use a rooted version of the ROM for CWM, I get stuck with a .ext4 file instead. Neither of the two files are compatible with standard extraction tools like 7zip, so enlighten me as to how I would open them.
I accidentally pushed the wrong framework-res.apk file in adb and now im stuck in a bootloop
I have stock recovery and am rooted
I can enter download mode but I don't want to lose all my data.
What can I do?
If you didn't make a nandroid backup... You will have to re-flash your rom over again
Edited:
Just noticed your on stock... Yikes. Looks like you'll have to Odin that thing. When pushing apks. Set the permissions to rw-r-r before rebooting
And definitely watch what your pushing
Annex1 said:
If you didn't make a nandroid backup... You will have to re-flash your rom over again
Edited:
Just noticed your on stock... Yikes. Looks like you'll have to Odin that thing. When pushing apks. Set the permissions to rw-r-r before rebooting
And definitely watch what your pushing
Click to expand...
Click to collapse
I'd prefer people use the heimdall oneclick (check 'Projects' out my sig).
Odin always makes things complicated, and it's closed source.
Heimdall is open source, documented, and actively maintained.
Just a suggestion
Or try using Heimdal One-Click to flash a custom kernel only. Then find a kernel you can flash in CWM that has TWRP. Then you can copy over your original framework-res.apk in the TWRP file manager and see if it will boot.
None of that will mess with your files except framework-res.
It's been a long time since I've been on stock recovery but does ADB pick up the phone when its in recovery?
hechoen said:
It's been a long time since I've been on stock recovery but does ADB pick up the phone when its in recovery?
Click to expand...
Click to collapse
It does on the blastoff kernel in eollies oneclick
bhundven said:
It does on the blastoff kernel in eollies oneclick
Click to expand...
Click to collapse
I know it does with custom recoveries but if he can get it picked up in the stock recovery he can just push the original .apk back. Easy. If it picks it up.
hechoen said:
I know it does with custom recoveries but if he can get it picked up in the stock recovery he can just push the original .apk back. Easy. If it picks it up.
Click to expand...
Click to collapse
what does it matter? Push the apk with custom recovery. I don't know of anything you can flash with stock recovery.
bhundven said:
what does it matter? Push the apk with custom recovery. I don't know of anything you can flash with stock recovery.
Click to expand...
Click to collapse
F. I'm off topic.
You're rooted on stock recovery. Install root explorer, over write the framework-res.apk, reboot.
Thank you so much guys.
I was able to flash a custom kernal with Heimdall and I pushed the right framework-res and now everythings back to normal
I'm truly grateful for all your speedy and helpful replies.
I would advise you to flash a simple zip (take any simple mod or gapps) valid for your Android version and edit its updater script to just flash the system folder. Then add the zip a system folder with framework folder and put your right framework-res.apk,
This way you just flash, fix permissions and good to go... no Heimdall, kernel or any other change, and you're back in business.
Another even simpler way is to use our device's Aroma File Manager and simply copy the right file and fix permissions...
First of all I decided to install CM10 without making a backup on TWRP 2 (clever Kyle). Then when it was stuck on the bootanimation for about an hour, I got annoyed and looked through the forums for help. "Factory reset, clear caches before installing etc" So I deleted the ROM, factory reset via TWRP, deleted both cache and then tried to install CM10. Failed.
Then I tried to mount the SD card to my computer to try to find other ROMS to install. Viper and Energy both failed. I then tried CM10, Viper and Energy with CWM 5.8, and the installation of all gets aborted almost instantly, which I am guessing means that it failed on there as well. I then tried ADB, and pushing keeps failing. Does anybody have any ideas at all on how to get just any ROM onto the phone so that I can get the official 4.1 update again (my phone was on 4.1 before trying CM10, so the HBOOT is most likely 4.1 as well). Any advice would be greatly appreciated, because having a £350 paperweight is not what I particularly want, especially considering I have another 9 months contract to run and no spare phone on the same network as my current contract.
kylepont said:
Any advice would be greatly appreciated
Click to expand...
Click to collapse
When you say that installing ROMs fails and adb pushing fails, you should tell us what error messages you get.
If you can still get into bootloader, you're probably going to be fine.
First, check that you can mount your sdcard in recovery. I don't mean mount onto your PC over USB, but just mount the sdcard partition onto the root filesystem.
If you can not get into recovery, re-flash one.
If recovery can not mount the sdcard, then you have to go to the sticky on how to fix unmountable sdcard. It involves flashing a stock recovery and then clearing storage from bootloader.
If your recovery is good and your sdcard is mountable, adb pushing should work. If it doesn't, post error messages. Make sure your sdcard is mounted before you try to push fils to it.
In recovery, format system, data, cache, but not sdcard. Then flash a zip. Then boot back into bootloader/fastboot and fastboot flash the boot image that comes with the rom. (Did you do this last step when flashing other roms?)
If this does not work not for you, describe in detail what you do and what you see. If it does work out, I suggest you make a nandroid backup so you can get back to this state, and S-off the device.
-Jobo
touch of jobo said:
If this does not work not for you, describe in detail what you do and what you see.
Click to expand...
Click to collapse
Sometimes a print screen can speak louder than words. This is the problem, I followed the tutorial posted specifically for my phone and that didn't work. (I used a dropbox link because I could only upload 640 x 640 according to the attachments screen, so you can see the full picture here)
www(dot)dropbox(dot)com/s/ei0y16oar828dh4/Picture1(dot)png
EDIT: I used platform-tools instead of tools because Google decided to move the adb application to that folder in the most recent update
Re: [Q] Soft Brick... Can't install ROMS and pushing does not work.
kylepont said:
Sometimes a print screen can speak louder than words. This is the problem, I followed the tutorial posted specifically for my phone and that didn't work. (I used a dropbox link because I could only upload 640 x 640 according to the attachments screen, so you can see the full picture here)
www(dot)dropbox(dot)com/s/ei0y16oar828dh4/Picture1(dot)png
EDIT: I used platform-tools instead of tools because Google decided to move the adb application to that folder in the most recent update
Click to expand...
Click to collapse
Have you flashed the boot.img?
fastboot flash boot boot.img
Sent from my One S using Tapatalk 2
usaff22 said:
Have you flashed the boot.img?
fastboot flash boot boot.img
Click to expand...
Click to collapse
boot.img? (Noob question incoming, prepare your anuses) What is a boot.img and why do I need it?
kylepont said:
Sometimes a print screen can speak louder than words.
Click to expand...
Click to collapse
You get this:
cannot stat 'ROM.zip': No such file or directory
..because either you have not mounted your /sdcard partition, but more likely because you dont have ROM.zip in your working directory.
Either move ROM.zip to the same directory where adb sits, or use:
adb push C:\full\path\to\rom.zip /sdcard/
Also, is the file youre trying to push actually named 'ROM.zip' or something else, like ViperOneS_2.1.0.zip or so..
Edit:
kylepont said:
boot.img? (Noob question incoming, prepare your anuses) What is a boot.img and why do I need it?
Click to expand...
Click to collapse
The flashing instructions for your ROM will likely state that you have to 'flash the boot image (or boot.img or kernel) in fastboot before booting into the rom.
You can find a file named 'boot.img' inside your rom zip. You have to flash that in fastboot. You can do it before or after flashing the rom, but you must do it before booting into the rom.
kylepont said:
usaff22 said:
Have you flashed the boot.img?
fastboot flash boot boot.img/QUOTE]
boot.img? (Noob question incoming, prepare your anuses) What is a boot.img and why do I need it?
Click to expand...
Click to collapse
Extract the boot.img file from the ROM. Place it in your adb folder. Boot into bootloader, select fastboot and connect to PC. Type command fastboot flash boot boot img
Click to expand...
Click to collapse
touch of jobo said:
You get this:
cannot stat 'ROM.zip': No such file or directory
..because either you have not mounted your /sdcard partition, but more likely because you dont have ROM.zip in your working directory.
Either move ROM.zip to the same directory where adb sits, or use:
adb push C:\full\path\to\rom.zip /sdcard/
Also, is the file youre trying to push actually named 'ROM.zip' or something else, like ViperOneS_2.1.0.zip or so..
Click to expand...
Click to collapse
All the boxes are ticked on the TWRP Mount screen, including System and SD card. And yes, I did make sure that it is:
1) in the same folder as the adb
2) called ROM.zip. I tried re-naming it CM10.zip and tried that in the adb and still no luck, without without the .zip file suffix.
And usaff22, does that involve unzipping the ROM that I am using?
Okay, so the boot.img was flashed successfully. I then went back onto TWRP, tried to flash the zip and it failed...
kylepont said:
I did make sure that it is [...] called ROM.zip. I tried re-naming it CM10.zip and tried that in the adb and still no luck, without without the .zip file suffix.
Click to expand...
Click to collapse
It can not find the local file. Make sure the file is not actually called 'ROM.zip.zip' (with 2x .zip ... you seem to have extensions hidden for most types but it shows .zip).
kylepont said:
Okay, so the boot.img was flashed successfully. I then went back onto TWRP, tried to flash the zip and it failed...
Click to expand...
Click to collapse
Which version of TWRP? I don't use it, but I read that the latest version has issues and you should use the previous version (2.2.0? I dont know).
Also, does it say anything interesting when it fails?
Before flashing the zip, did you format your system, data, cache partitions?
EDIT: After repeatedly trying to adb push, I finally got CM10.zip.zip onto the phone. Flashing took a bit longer than last time, but booting took no time at all. Thank you touch of jobo and usaff22, your advice was a lot of help.
touch of jobo said:
It can not find the local file. Make sure the file is not actually called 'ROM.zip.zip' (with 2x .zip ... you seem to have extensions hidden for most types but it shows .zip).
Click to expand...
Click to collapse
Ah, putting .zip.zip fixed that error, but has now given me a new one: protocol failure
touch of jobo said:
Which version of TWRP? I don't use it, but I read that the latest version has issues and you should use the previous version (2.2.0? I dont know).
Click to expand...
Click to collapse
TWRP v.2.3.3.0. Do you recommend an older build then, or do you think that CWM is a better tool for the job? (I have that on standby)
touch of jobo said:
Before flashing the zip, did you format your system, data, cache partitions?
Click to expand...
Click to collapse
I haven't done that again... Should I do that again? All that is on the system is the boot.img and the CM10.zip folder
kylepont said:
Ah, putting .zip.zip fixed that error, but has now given me a new one: protocol failure
Click to expand...
Click to collapse
I can't help with that adb error. Never seen it. Try searching the forums for it. Sorry. Also, I don't use Windows, so I don't know about driver versions and things.
kylepont said:
TWRP v.2.3.3.0. Do you recommend an older build then, or do you think that CWM is a better tool for the job? (I have that on standby)
Click to expand...
Click to collapse
TWRP and CWM are both fine for flashing ROMs, just not this specific version of TWRP. Since I dont use it myself, I dont know the exact version numbers, but read around a bit and you'll find what worked for others.
Maybe flashing a different recovery will even get rid of your protocol error.
If you've made nandroid backups (I guess you havent or we wouldnt be here.. sorry) you should stay with the same recovery (same 'brand', not same version) or you can't restore them.
kylepont said:
I haven't done that again... Should I do that again? All that is on the system is the boot.img and the CM10.zip folder
Click to expand...
Click to collapse
The CM10.zip should be on your sdcard, not your system partition. You dont need the boot img at all on your device. You need it on your PC in order to fastboot flash it.
Before flashing a ROM you should wipe your 'system', 'data', and 'cache' partitions, but not your 'sdcard' partition. Only if you flash (a newer version of) the same ROM you have operational, then you can sometimes flash without wiping. This is called 'dirty flashing'. But this does not apply in your case.
Successful flash of CyanogenMod, thanks for the help.
I would like to thank touch of jobo and usaff22 for their help, I just hope that somebody else will see this thread and get all of the answers that they need.
Re: [Q] Soft Brick... Can't install ROMS and pushing does not work.
kylepont said:
I would like to thank touch of jobo and usaff22 for their help, I just hope that somebody else will see this thread and get all of the answers that they need.
Click to expand...
Click to collapse
I would rename the zip to something else like sense.zip, place it on the desktop and do adb push C:\Users\username\Desktop\sense.zip /sdcard/
Make sure you use backward slashes for the PC file location, and forward slashes for the phone paste location.
This way we are also providing the full path on the PC.
Also make sure you use the latest adb from the SDK website. You don't need the whole thing, just the platform-tools bit, and replace the files in the new folder with the old one.
Sent from my One S using Tapatalk 2
Oh, while you're here, another problem has come about. Mounting the SD card will not work, and I can't replace it with a new SD card because... Well, there is no removable cover. I know how to fix it, I've read enough on here to find that out, but the only thing that I am missing is a stock recovery image for the S4 version (CID is ORANG001 if that is required) so if anybody knows a link for this then that will be greatly appreciated.
kylepont said:
Oh, while you're here, another problem has come about. Mounting the SD card will not work, and I can't replace it with a new SD card because... Well, there is no removable cover. I know how to fix it, I've read enough on here to find that out, but the only thing that I am missing is a stock recovery image for the S4 version (CID is ORANG001 if that is required) so if anybody knows a link for this then that will be greatly appreciated.
Click to expand...
Click to collapse
You might be able to find an RUU lying around on one of the websites which give RUUs such as androidfiles.org/ruu
I tried looking, but no sign of an orange RUU. An easy way to overcome this would be to change your CID to HTC__001 and use an unbranded RUU.
kylepont said:
the only thing that I am missing is a stock recovery image for the S4 version (CID is ORANG001 if that is required)
Click to expand...
Click to collapse
You can extract the recovery image from any RUU or OTA. Recoveries do not depend on carrier.
But .. if you can see your sdcard from within recovery (when 'choosing' a zip to flash, or from an adb shell or so) and from within Android, then you do not have The Unmountable Sdcard Issue and you should not go through that process. Only if you get an 'Unable to mount /sdcard' error in recovery.
touch of jobo said:
If you can see your sdcard from within recovery (when 'choosing' a zip to flash, or from an adb shell or so) and from within Android, then you do not have The Unmountable Sdcard Issue and you should not go through that process. Only if you get an 'Unable to mount /sdcard' error in recovery.
Click to expand...
Click to collapse
So I just use the stock recovery of any RUU I can find lying around for the HTC One S?
usaff22 said:
I tried looking, but no sign of an orange RUU. An easy way to overcome this would be to change your CID to HTC__001 and use an unbranded RUU.
Click to expand...
Click to collapse
How do I change the CID? Because knowing me, I'll screw it up and brick it if that is possible.
kylepont said:
So I just use the stock recovery of any RUU I can find lying around for the HTC One S?
Click to expand...
Click to collapse
Yes. You can use the recovery image from any RUU or OTA.
But first make sure you need it. The stock recovery thing is only to fix the situation where your sdcard is unmountable and you get that error in recovery.
kylepont said:
How do I change the CID? Because knowing me, I'll screw it up and brick it if that is possible.
Click to expand...
Click to collapse
This is the thread: http://forum.xda-developers.com/showthread.php?t=1671643
It involves extracting, hex-editing, and flashing a critical part of your device. If you make the slightest mistake you have a brick. However, if you read carefully and double check every step, it's not difficult. Many have done it. Read the thread.
Once you have supercid, you may as well get s-off as well. (This is the thread: http://forum.xda-developers.com/showthread.php?t=2155135 ) That way you can always flash anything.
Whatever you decide to do, before you start on anything, read all the instructions to the end, so that you're sure you can complete the process before you start. Also, before you start any process, try to understand what each step does and why it is necessary. That may involve a lot of reading and searching, but that is a Good Thing in the end.
touch of jobo said:
Yes. You can use the recovery image from any RUU or OTA.
But first make sure you need it. The stock recovery thing is only to fix the situation where your sdcard is unmountable and you get that error in recovery.
Click to expand...
Click to collapse
It is unmountable. I tried CWM and TWRP to no avail. Also, I have HBOOT version 2.15 which I heard is a bugger to work with. Also, I got the ZIP file for the stock 4.1, and I read that the stock recovery is in the firmware folder, but I cannot access it. (https://www.dropbox.com/s/kyn9sb5x7gpd7fr/Picture2.png) Then, I tried to get to the CID, following the instructions that you gave me, and I didn't get very far (https://www.dropbox.com/s/g6ik0i3los7unde/Picture3.png)
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.
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