Forgive my ignorance, i've tried to do a few searches to answer my question but none have directly addressed it.
I recently rooted 2.20 successfully, installed CleanROM. If I want to flash a kernel, say cleanKERNEL, all I have to do is move the .zip onto the phone, boot into bootloader, and flash it that way? If I flash a kernel, will I loose all the customization I've done on the current ROM?
Any help would be appreciated.
style2burn said:
Forgive my ignorance, i've tried to do a few searches to answer my question but none have directly addressed it.
I recently rooted 2.20 successfully, installed CleanROM. If I want to flash a kernel, say cleanKERNEL, all I have to do is move the .zip onto the phone, boot into bootloader, and flash it that way? If I flash a kernel, will I loose all the customization I've done on the current ROM?
Any help would be appreciated.
Click to expand...
Click to collapse
I'm unclear on whether you can flash kernels with the new hboot in 2.20, but if you can, you flash it like anything else. It shouldn't affect the rom as long as they're compatible.
iElvis said:
I'm unclear on whether you can flash kernels with the new hboot in 2.20, but if you can, you flash it like anything else. It shouldn't affect the rom as long as they're compatible.
Click to expand...
Click to collapse
I was under the impression that you would have to use fastboot, not recovery.
style2burn said:
I was under the impression that you would have to use fastboot, not recovery.
Click to expand...
Click to collapse
Yes, I think that's correct with the new hboot.
iElvis said:
Yes, I think that's correct with the new hboot.
Click to expand...
Click to collapse
Can someone give quick instructions on how to do it through fastboot? Or link me to a resouce that says how? I've searched a bit but can't find something that exactly answers my question. Any help would be appreciated.
style2burn said:
Can someone give quick instructions on how to do it through fastboot? Or link me to a resouce that says how? I've searched a bit but can't find something that exactly answers my question. Any help would be appreciated.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1954060
if you flashed 2.20 at anytime you have to ALWAYS flash boot.img in fastboot
DvineLord said:
if you flashed 2.20 at anytime you have to ALWAYS flash boot.img in fastboot
Click to expand...
Click to collapse
Right, I did do that. But now I'm trying to flash a kernel. I have the new CleanKERNEL zip file, but I'm not seeing a boot.img in the zip.So I keep looking for some sort of .img, flash it, move CleanKERNEL zip to my phone, then flash that?
Any help would be appreciated.
Oh right... It builds the boot.img on the fly when it is installed from recovery. I believe you need to try and flash the kernel zip file from recovery. It will fail since you have to 2.20 hboot, but it will create the boot.img in a temp dir somewhere on your phone, which you can copy to your pc and flash via fastboot.
denversc said:
Oh right... It builds the boot.img on the fly when it is installed from recovery. I believe you need to try and flash the kernel zip file from recovery. It will fail since you have to 2.20 hboot, but it will create the boot.img in a temp dir somewhere on your phone, which you can copy to your pc and flash via fastboot.
Click to expand...
Click to collapse
So I have to copy the kernel to my phone, open up recovery, attempt to flash it, it will fail, open up my phone through windows, find the boot.img, manually flash it from fastboot, then go into recovery and flash the kernel??????
style2burn said:
So I have to copy the kernel to my phone, open up recovery, attempt to flash it, it will fail, open up my phone through windows, find the boot.img, manually flash it from fastboot, then go into recovery and flash the kernel??????
Click to expand...
Click to collapse
Yes, except for the very last step of re-flashing from recovery. I haven't personally tried this since I'm not on AT&T and can flash whatever from recovery, but I've seen this method discussed several times in the Blackout BeastMode custom kernel thread.
denversc said:
Yes, except for the very last step of re-flashing from recovery. I haven't personally tried this since I'm not on AT&T and can flash whatever from recovery, but I've seen this method discussed several times in the Blackout BeastMode custom kernel thread.
Click to expand...
Click to collapse
Hmmm ok thanks alot for the advice. I guess I'll have to dig through the blackout beastmode thread to see the exact directions. Again, thanks for all the advice
style2burn said:
Hmmm ok thanks alot for the advice. I guess I'll have to dig through the blackout beastmode thread to see the exact directions. Again, thanks for all the advice
Click to expand...
Click to collapse
Looks like the people in the blackout beastmode thread already have a boot.img for them to use without looking for the one created in the temp file. Unless I can just use the boot.img from cleanROM which I'm already running? Or the kernel requires its on boot.img??
style2burn said:
Looks like the people in the blackout beastmode thread already have a boot.img for them to use without looking for the one created in the temp file. Unless I can just use the boot.img from cleanROM which I'm already running? Or the kernel requires its on boot.img??
Click to expand...
Click to collapse
Hmmm... I thought Blackout BeastMode created boot.img on the fly. Perhaps not. The next thread I would direct you to is the CleanROM thread. Or you could try the BeastMode kernel haha. Sorry can't be more help. I just don't have any first-hand experience.
Has anyone else flashed CleanKernel on 2.20 AT&T device?
Related
I am new to this posting and asking questions. I have a xoom and rooted it and updated it with 3.1 and then I went and updated it with the new rom which came out the other day. I did something studpid and didn't wait for the resolution to the sdcard not being seen after flashing the new deodex rom. I looked on the kernal manager and when I what I thought was the latest kernal I decided to flash it. I now can only get to recovery mode and I don't want to make another mistake. Can someone tell me if I can safely do a wipe data/factory reset? Will that get me back so I can flash the deodex rom back? You dev guys are really awesome and I really appreciate all of your work. Thank you for your support.
razor532 said:
I am new to this posting and asking questions. I have a xoom and rooted it and updated it with 3.1 and then I went and updated it with the new rom which came out the other day. I did something studpid and didn't wait for the resolution to the sdcard not being seen after flashing the new deodex rom. I looked on the kernal manager and when I what I thought was the latest kernal I decided to flash it. I now can only get to recovery mode and I don't want to make another mistake. Can someone tell me if I can safely do a wipe data/factory reset? Will that get me back so I can flash the deodex rom back? You dev guys are really awesome and I really appreciate all of your work. Thank you for your support.
Click to expand...
Click to collapse
If you can get to recovery, just re-flash the rom, it includes its own kernel.
Ok I will and let you know if I am successful. Thank you
I tried to use recovery but my xoom won't see the sd card. I have adb running but really am afraid to use it without some help. Don't want to brick my xoom. I have the kernal zip but don't 1.4.4 and thought if I could flash the kernal to my xoom that would maybe fix it. I read somewhere that you shouldn't flash a zip file, so I don't know what to do. any help would be appreciated. Thank you
razor532 said:
I tried to use recovery but my xoom won't see the sd card. I have adb running but really am afraid to use it without some help. Don't want to brick my xoom. I have the kernal zip but don't 1.4.4 and thought if I could flash the kernal to my xoom that would maybe fix it. I read somewhere that you shouldn't flash a zip file, so I don't know what to do. any help would be appreciated. Thank you
Click to expand...
Click to collapse
Please don't flash any xip file through adb! Why not go into RomManager app and look for an earlier version of recovery, maybe 3.0.2.5, and flash that. A good recovery should allow you to flash from your sdcard through clockwork mod recovery.
I can't get to the rom manager app. Am I missing something? The OS won't boot up and I only have version 4 of the clockwork recovery. What should I do?
razor532 said:
I can't get to the rom manager app. Am I missing something? The OS won't boot up and I only have version 4 of the clockwork recovery. What should I do?
Click to expand...
Click to collapse
There is your problem, you did not read the warnings...DO NOT USE CWM 4.
Grab Recovery Image (solarnz-R4c-100611-1150) FLASHED THROUGH FASTBOOT from this post.
http://forum.xda-developers.com/showthread.php?t=1074979
Fastboot flash it, if you don't know how read the post or read my sig. Once you have a working recovery, try my post above.
bwcorvus said:
There is your problem, you did not read the warnings...DO NOT USE CWM 4.
Grab Recovery Image (solarnz-R4c-100611-1150) FLASHED THROUGH FASTBOOT from this post.
http://forum.xda-developers.com/showthread.php?t=1074979
Fastboot flash it, if you don't know how read the post or read my sig. Once you have a working recovery, try my post above.
Click to expand...
Click to collapse
Flash the .img file as bwcorvus says, not the .zip.
Take your time.
OK, Thank you very much,,, I will be more careful in the future. I am back up and running the new rom with an older recovery. That taught me a good lesson never to install an earlier version of a kernal and never to try and flash a .zip file from adb. Thank you for the instructions. Is there a book for "adb for dummies"? My name should be in it...
thank you again...
Np, glad you got it working. And guess what? You got to learn something .
razor532 said:
OK, Thank you very much,,, I will be more careful in the future. I am back up and running the new rom with an older recovery. That taught me a good lesson never to install an earlier version of a kernal and never to try and flash a .zip file from adb. Thank you for the instructions. Is there a book for "adb for dummies"? My name should be in it...
thank you again...
Click to expand...
Click to collapse
There is actually an ADB tutorial somewhere on this site...seriously, do a search. It had a lot of great information. I like to know what I'm doing...it makes me more nervous to just blindly follow instructions with something like this, but I'm still mostly blind (sigh).
So I attempted to flash viper onto my HTC One S. And screwed something up apparently, I can't load into anything besides hboot. Phone just continually reboots when I try to run anything else. What can I do? Thanks.
No worries
Crowder HTC said:
So I attempted to flash viper onto my HTC One S. And screwed something up apparently, I can't load into anything besides hboot. Phone just continually reboots when I try to run anything else. What can I do? Thanks.
Click to expand...
Click to collapse
You can try other images with fastboot. Don't worry. Check this out, Im new to. http://forum.xda-developers.com/showthread.php?t=1599363&highlight=most+stable
LowCostComputerRepair said:
You can try other images with fastboot. Don't worry. Check this out, Im new to. http://forum.xda-developers.com/showthread.php?t=1599363&highlight=most+stable
Click to expand...
Click to collapse
Ya I just think he didn't fastboot the boot.img.
Darknites said:
Ya I just think he didn't fastboot the boot.img.
Click to expand...
Click to collapse
How do I do this? Or is it too late at this point?
Crowder HTC said:
How do I do this? Or is it too late at this point?
Click to expand...
Click to collapse
Use the All-In-One Toolkit but it calls it a Kernel and after doing that reflash the rom and it should boot up fine.
Darknites said:
Use the All-In-One Toolkit but it calls it a Kernel and after doing that reflash the rom and it should boot up fine.
Click to expand...
Click to collapse
Thanks so much, I really appreciate it, I overlooked something so small yet screwed myself over. Thanks!
You shouldnt have to reinstall the rom after flashing the boot.img, as long as the boot.img is compatible with the rom.
Atleast, Ive always flashed the boot.img after the rom has been installed.
Goatshocker said:
You shouldnt have to reinstall the rom after flashing the boot.img, as long as the boot.img is compatible with the rom.
Atleast, Ive always flashed the boot.img after the rom has been installed.
Click to expand...
Click to collapse
I know it works but I find flashing the boot.img first is the best way of going about it.
Hiya. Any help appreciated here, Got hold of a Rogers One X (evita)
Heres where I am at right now:
I unlocked the bootloader and attempted to flash CM11 (Got an error regarding update package) *I made no backup- Noob, I know.*
Now, at the very most all I can get into is CWM/TWRP (I can flash both of these without issue using fastboot)
I have attempted to re-lock the bootloader (which says relocked) but I have tried the 2 rogers RUU files I managed to find and both fail with an error 115 and leave me on the htc logo, and boot to bootloader only.
I tried to flash some custom roms, some seem to flash ok but just boot-loop.
I am not SuperCID, and the phone is S-ON.
Hboot-2.14.0000
Radio-0.23a.32.09.29
Nov 26, 2012
I cannot figure what to do next. I dont care what goes on the phone as long as i can get it working. Its been a long time since I messed with android, I only bought this phone for this reason lol, but I made the mistake of staying up too late and probably skipping half of the tutorials i was following.
Any help appreciated.
:laugh:
What version of TWRP are you using? Why did you relock the bootloader? You should unlock that again. Did you flash the boot.img from the ROM zip via fastboot after flashing the ROM in TWRP? You need to do this because you're s-on. You should read the Evita FAQ thread in my signature, as well as the How-To Guide For Beginners thread.
Sent from my Evita
timmaaa said:
What version of TWRP are you using? Why did you relock the bootloader? You should unlock that again. Did you flash the boot.img from the ROM zip via fastboot after flashing the ROM in TWRP? You need to do this because you're s-on. You should read the Evita FAQ thread in my signature, as well as the How-To Guide For Beginners thread.
Sent from my Evita
Click to expand...
Click to collapse
Wow, timmaaa, thanks for the superfast answer chap!
So, unlock the bootloader, flash the Rom (CM11), then the Boot.img extracted from the rom via fastboot?
Sounds like a plan. I will try that now. I think to be honest, I came home last night and ended up following a bit of one tut, a bit of another, and never really read properly. Call it friday evening alcohol induced noobness syndrome.
That should be it. You need to make sure you use the correct version of TWRP though, you're looking for the unofficial modified TWRP 2.6.3.0 by jrior001 in our Original Android Development section.
Sent from my Evita
timmaaa said:
That should be it. You need to make sure you use the correct version of TWRP though, you're looking for the unofficial modified TWRP 2.6.3.0 by jrior001 in our Original Android Development section.
Sent from my Evita
Click to expand...
Click to collapse
Thank you. The boot.img thing got me a bit further so far. I will get that version of TWRP installed and try the CM11 again, as i think thats where I want to be at. It should be as simple as CM11 flash, Boot.img flash, then Gapps and im done, right?
Perform a full wipe (cache/dalvik cache/factory reset/system), flash CM, flash gapps, flash boot.img, reboot into ROM.
Sent from my Evita
timmaaa said:
That should be it. You need to make sure you use the correct version of TWRP though, you're looking for the unofficial modified TWRP 2.6.3.0 by jrior001 in our Original Android Development section.
Sent from my Evita
Click to expand...
Click to collapse
Ok one last question Timmaaa, I have installed that TWRP, flashed CM11, also Gapps and the boot.img , and now I just get the rom bootlogo (spinning cyanogen etc) and nothing, it just sits there. Is there anything else that may need to be done? If theres not anything obvious, ill go read some more!
Thanks for the help so far!
scibot said:
Ok one last question Timmaaa, I have installed that TWRP, flashed CM11, also Gapps and the boot.img , and now I just get the rom bootlogo (spinning cyanogen etc) and nothing, it just sits there. Is there anything else that may need to be done? If theres not anything obvious, ill go read some more!
Thanks for the help so far!
Click to expand...
Click to collapse
What is the filename of the ROM zip you flashed? Did you check the md5 of the file after you downloaded it? Are you sure the flashing of the boot.img was successful?
Timmaaa, it seems it just took ages. I went downstairs for some juice, came back up and there it was, the setup screen! Beautiful.
Thanks for the help, it seems its not the technical i need to brush up on, but my paying attention and reading - lol!
Thanks again man! :good:
I have an AT&T HTC One x. Its ***Tampered*** ***Unlocked*** HBOOT 1 .09. 0000 S-ON
I had been running an older version of TWRP, and decided I was going to clear my phone and do a fresh start. I know, I know, I should have made a backup, but I felt pretty confident in what I was doing, and was in too much of a hurry to rationalize this.
I wiped both the OS and previous version of TWRP in order to update to the new ones. While in fastboot I flashed CLEANrom and the new version of TWRP, and my administrative command prompt confirmed that they were installed successfully. Even cleared the cache afterwards. Now is the difficult part. I've researched, and researched, and cannot find a solution for this problem. I keep having a Boot Loop.... I'm stumped guys... I need some sort of help, be it technical, or something to drink lol
Previous ROM was CM 10, with TWRP and PA GAPPS :good:
Check the Evita FAQ thread in my signature, your answer probably lies within.
Sent from my Evita
timmaaa said:
Check the Evita FAQ thread in my signature, your answer probably lies within.
Sent from my Evita
Click to expand...
Click to collapse
I don't see anything in your FAQ that I haven't already tried unfortunately.....
Exactly which version of TWRP is currently installed? Did you flash the boot.img via fastboot?
Sent from my Evita
timmaaa said:
Exactly which version of TWRP is currently installed? Did you flash the boot.img via fastboot?
Sent from my Evita
Click to expand...
Click to collapse
It's the newest version of TWRP that is out, and yes, I flashed it via Fastboot, and it says successful on both the recovery install and ROM install.
Have you tried flashing another ROM? I asked for the exact recovery version for a reason, please provide that information.
Sent from my Evita
---------- Post added at 03:48 PM ---------- Previous post was at 03:43 PM ----------
Also it isn't completely clear to me that you're flashing the boot.img from the ROM zip via fastboot after flashing the ROM in TWRP. Are you extracting the boot.img from the ROM zip and doing that or not?
Sent from my Evita
1332858898
timmaaa said:
Have you tried flashing another ROM? I asked for the exact recovery version for a reason, please provide that information.
Sent from my Evita
Click to expand...
Click to collapse
TWRP 2.7. And yes, I have flashed about 4 Roms all succeeded according to fastboot and still getting the boot sequence.:good:
Yes I have extracted the boot.img
timmaaa said:
Have you tried flashing another ROM? I asked for the exact recovery version for a reason, please provide that information.
Sent from my Evita
---------- Post added at 03:48 PM ---------- Previous post was at 03:43 PM ----------
Also it isn't completely clear to me that you're flashing the boot.img from the ROM zip via fastboot after flashing the ROM in TWRP. Are you extracting the boot.img from the ROM zip and doing that or not?
Sent from my Evita
Click to expand...
Click to collapse
yes the boot.img file was extracted. I get a confirmation that it was successful when I flash it on fastboot
Exactly which ROMs have you tried to flash?
Sent from my Evita
timmaaa said:
Exactly which ROMs have you tried to flash?
Sent from my Evita
Click to expand...
Click to collapse
CM 10.2, CM 11, CLEANrom 7.0. all via fastboot with confirmations.
outcold32 said:
CM 10.2, CM 11, CLEANrom 7.0. all via fastboot with confirmations.
Click to expand...
Click to collapse
Why are you flashing roms via fastboot? -_- You're making your life difficult. Wipe everything in TWRP then flash in TWRP. ALso, you should really s-off and update your firmware/hboot. via RUU. You will likely encounter issues running a newer software on an such an old firmware.
exad said:
Why are you flashing roms via fastboot? -_- You're making your life difficult. Wipe everything in TWRP then flash in TWRP. ALso, you should really s-off and update your firmware/hboot. via RUU. You will likely encounter issues running a newer software on an such an old firmware.
Click to expand...
Click to collapse
If you would have read the thread, you would have noticed, that I am in bootloop, therefor I cannot access the recovery. And I have to have access to the ROM on my phone in order to flash anything via TWRP so this is moot. My question isn't how to flash roms, it's why am I getting a loop when I am successful on a clean partition and clean flash of both the recovery and ROM? And to me, fastboot is way easier than TWRP. I guess I could get a UART and try to debug the sequence myself, but I have more important things to do than that. I was posting to see if anyone had any similar problems. And this phone is an original model and I haven't really bothered with the security off, since I only wanted to get rid of sense in the first place. It was unlocked well before any commercial unlocker was available for the evita(Literally no stable CM10 at all at the time), so it's a little finicky in the first place. I ran the RUU after I re-locked the bootloader, and I'm at least out of the loop. I'm just going get to a more stable version so that this process will be more streamline when I re do my unlock and stuff.
So I guess the only solution at this point I have for any problem like this is to use the proper RUU. I tried a couple of times with no success, and it seemed the charm was to re lock the bootloader ( Fastboot oem lock) in order to properly and successfully get the RUU to work.:good:
Wth are you even on about? Of course you can access recovery in a bootloop. How are you getting to fastboot without accessing the bootloader? from the bootloader you can access recovery. If recovery isn't loading SCREW flashing a rom, reflash your recovery, 2.7 TWRP preferably. and then boot to recovery, mount your USB, copy the rom and flash it. Recovery is more important than having a ROM.
I know what I am talking about, do you know what you're talking about?
FFS I am trying to help you, there's no reason for you to be an ass. You're having issues BECAUSE you're flashing your rom via fastboot. You cannot flash a rom via fastboot.
exad said:
Wth are you even on about? Of course you can access recovery in a bootloop. How are you getting to fastboot without accessing the bootloader? from the bootloader you can access recovery. If recovery isn't loading SCREW flashing a rom, reflash your recovery, 2.7 TWRP preferably. and then boot to recovery, mount your USB, copy the rom and flash it. Recovery is more important than having a ROM.
I know what I am talking about, do you know what you're talking about?
FFS I am trying to help you, there's no reason for you to be an ass. You're having issues BECAUSE you're flashing your rom via fastboot. You cannot flash a rom via fastboot.
Click to expand...
Click to collapse
You didn't read the thread. I'm not being an ass. The information is already there.I can not access the recovery at all. That's why I am in in this situation. And again, if you had read the whole thread, or the even the original post, you would know that I cannot access the recovery. The only reason I'm being as detailed as I am is so I don't have to repeat myself, as well as for other people who may encounter this problem. And Yes I know what I am talking about. If I didn't I probably wouldn't have gotten to this point, right?
Okie dokie. No point in arguing. You're right. I'm wrong. Glad it's all working now.
Sent from my One XL using xda app-developers app
outcold32 said:
You didn't read the thread. I'm not being an ass. The information is already there.I can not access the recovery at all. That's why I am in in this situation. And again, if you had read the whole thread, or the even the original post, you would know that I cannot access the recovery. The only reason I'm being as detailed as I am is so I don't have to repeat myself, as well as for other people who may encounter this problem. And Yes I know what I am talking about. If I didn't I probably wouldn't have gotten to this point, right?
Click to expand...
Click to collapse
Exad is right in saying that the reason you're having problems is because you're attempting to flash ROMs with fastboot. That isn't how it's done. The correct way is to flash your ROM with recovery. You're barking up the wrong tree, not only that but you're arguing with experienced people who are only attempting to help get you out of the mess that you've gotten yourself into. You came here for advice, but there's no point in asking for advice if you're just going to argue and dismiss what you're being told to do.
You said you can't access your ROM so you can't flash anything, that makes absolutely no sense, which leads me to believe you don't really know what you're doing. Get out of the mindset that you need to use fastboot, it's wrong. You're dealing with people who have extensive and intimate knowledge of this device, trust us, we know what we're talking about.
Exactly why can't you access recovery? If you can issue fastboot commands that means you can access your bootloader, if you can access your bootloader that means you can use your volume keys to scroll through the options and the power button to select recovery. What happens when you do that? Exactly which recovery have you flashed to your device? I need to the full filename of the recovery that you've flashed.
Sent from my Evita
outcold32 said:
And this phone is an original model and I haven't really bothered with the security off, since I only wanted to get rid of sense in the first place. It was unlocked well before any commercial unlocker was available for the evita(Literally no stable CM10 at all at the time), so it's a little finicky in the first place.
Click to expand...
Click to collapse
S-on is a downright dangerous place to be, if the phone is also SuperCID (which is very likely, since its the AT&T variant). exad is right in recommending s-ff, as he is about a good many things.
Ok, so I'm just looking for final confirmation before I install my TWRP2710-RAZR-HD_M-KITKAT image...going to just fastboot flash it on there using the files in my Motopocalypse folder, but do I need to rename some file in the system folder or something before I do this? Seems like I had to do that in the JB era and I can't find much for the KK version. Noob question I know. Do I just put my phone in fastboot mode and flash away or is there a step prior to that? Thanks in advance.
Just follow the directions here: http://forum.xda-developers.com/showthread.php?t=2776515
pothole said:
Ok, so I'm just looking for final confirmation before I install my TWRP2710-RAZR-HD_M-KITKAT image...going to just fastboot flash it on there using the files in my Motopocalypse folder, but do I need to rename some file in the system folder or something before I do this? Seems like I had to do that in the JB era and I can't find much for the KK version. Noob question I know. Do I just put my phone in fastboot mode and flash away or is there a step prior to that? Thanks in advance.
Click to expand...
Click to collapse
Not sure why you think you have to rename something to flash a new recovery. Yeah, maybe the instructions had you rename the recovery image file or something, but no. Just flash it per the instructions the previous poster linked to. It's really that simple.
Good luck!
iBolski said:
Not sure why you think you have to rename something to flash a new recovery. Yeah, maybe the instructions had you rename the recovery image file or something, but no. Just flash it per the instructions the previous poster linked to. It's really that simple.
Good luck!
Click to expand...
Click to collapse
Or you could just use flashify in the play store...
https://play.google.com/store/apps/details?id=com.cgollner.flashify
Thanks gents, just the info I was looking for.
pistacios said:
Or you could just use flashify in the play store...
https://play.google.com/store/apps/details?id=com.cgollner.flashify
Click to expand...
Click to collapse
That's what I did. Worked great!
Sent from my DROID RAZR HD using Tapatalk
pistacios said:
Or you could just use flashify in the play store...
https://play.google.com/store/apps/details?id=com.cgollner.flashify
Click to expand...
Click to collapse
The only thing about Flashify that I don't like is you need to be already rooted.
Otherwise, if you're not rooted, then you can't root until you put on a custom recovery, which means you need to use fastboot to flash CWM or TWRP and then sideload root. Then you'd be able to flash TWRP or CWM. Kind of the chicken and the egg conundrum.
Everyone should know how to do it via fastboot because you may not have root to install TWRP or any other custom recovery. It's always good to know how to do things from the command line because there may come a time when you have no other option.
running official kk on xt926 here.
can i install official cm11 nightlys after flash 2.7 twrp ?
I believe they can only be installed when they update them with the new kitkat bootloader. There are some builds by dhacker29 that I have tried that worked but are in progress. You would need to reflash back to JB bootloader to use the official CM11 nightlies.
aaki_rocker said:
running official kk on xt926 here.
can i install official cm11 nightlys after flash 2.7 twrp ?
Click to expand...
Click to collapse
yujikaido79 said:
I believe they can only be installed when they update them with the new kitkat bootloader. There are some builds by dhacker29 that I have tried that worked but are in progress. You would need to reflash back to JB bootloader to use the official CM11 nightlies.
Click to expand...
Click to collapse
how can i flash back to jb bootloader without bricking ?
edit : got it..
iBolski said:
Not sure why you think you have to rename something to flash a new recovery. Yeah, maybe the instructions had you rename the recovery image file or something, but no. Just flash it per the instructions the previous poster linked to. It's really that simple.
Good luck!
Click to expand...
Click to collapse
i think it is because back in the day, correct me if im wrong, you had to rename the old recovery file so it wouldnt re-install.
but now that development has progressed, that is no longer necessary.
thats why all the, do i need to rename questions are arising.
bweN diorD said:
i think it is because back in the day, correct me if im wrong, you had to rename the old recovery file so it wouldnt re-install.
but now that development has progressed, that is no longer necessary.
thats why all the, do i need to rename questions are arising.
Click to expand...
Click to collapse
yep, that's what I was inquiring about.. all sorted now and rocking the device as it's supposed to be used. thanks.