Basically what the topic says, every time I try installing Beta 6 using TWRP, it'll tell me there's no MD5, a warning that there's no "file_context" (if I remember correctly), and then a red "failed" message after 30-50 seconds. Then I'd have to use my backup file I created before flashing the ROM just to reboot the phone.
And just in case someone asks for what phone/ROM I'm using:
Galaxy Nexus (Toro)
Paranoid Android 3.99
Any idea why this is happening?
Have you updated twrp to the newest version. That's the most common problem
Sent from my Nexus 5
Not sure how to do that, can anyone explain how to do that? Goo.im doesn't want to update it for me, or, even want to work. ._.
Fastboot flash the image on
Sent from my Nexus 5
Pirateghost said:
Fastboot flash the image on
Sent from my Nexus 5
Click to expand...
Click to collapse
I hate to hijack this tread but how is this done? Sorry if this is a stupid question
michaelrager said:
I hate to hijack this tread but how is this done? Sorry if this is a stupid question
Click to expand...
Click to collapse
There are a million threads on xda explaining exactly how to use fastboot. Pick one for your device and go for it
Sent from my Nexus 5
The easiest way to update TWRP is to go to the play store and installing Goo market (it's a green app the the app image says "Goo") and then from there you can update painlessly with no problem.
Sparta507 said:
The easiest way to update TWRP is to go to the play store and installing Goo market (it's a green app the the app image says "Goo") and then from there you can update painlessly with no problem.
Click to expand...
Click to collapse
Goo manager has been failing for a lot of people. The best option from the phone would be flashify
Sent from my Nexus 5
Pirateghost said:
Goo manager has been failing for a lot of people. The best option from the phone would be flashify
Sent from my Nexus 5
Click to expand...
Click to collapse
Ya I know it wasn't working for a while, but I updated my TWRP last week and it was working like a charm. It's always good to have options
Download the proper twrp in goo.im and flash in bootloader using command
"fastboot flash recovery filename.img"
Sent from my Nexus 4 using XDA Premium 4 mobile app
Thanks for the replies, however, the twrp goo downloads is 2.7. I need beta .6 TWRP for the rom for my dna to use. See this thread it tells us to use:
http://forum.xda-developers.com/showthread.php?t=2648446
I tried flashify, but I don't think i am using it correctly.
Related
Koushik Dutta's Clockwork Recovery:
Attention: Some people experience problems when flashing through Rom Manager. Flashing again usually fixes the issue. Use method below for best results. If on pure stock, your recovery will be overwritten unless you delete your /system/etc/install-recovery.sh file.
To flash recovery for Nexus S 4G, download recovery 5.0.2.0 or recovery touch 5.8.0.2 and place it into your sdk tools folder. Reboot into bootloader and execute:
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo4g.img
or if you prefer the touch version:
Code:
fastboot flash recovery recovery-clockwork-touch-5.8.0.2-crespo4g.img
If you'd like simpler and more organized menus see j_r0dd's mod.
rev 5.0.1.0 Fix android_ secure backup bug.
rev 5.0.2.0 Fix root loss. Correct message when choosing "no" when wiping dalvik.
Officiality
RSVP....
outstanding
Sent from my HP Touchpad using xda premium
Backups on 4.x going tto restore properly on 5.x?
Great work by the way.
Sent from my Nexus S 4G using XDA App
...or just go into the ROM Manager app and click on "Flash Clockworkmod Recovery", your version will update to 5 automatically.
Sent from my Nexus S 4G using xda premium
Also there's a app in the app section that flashes img files quicker than you can blink.
Flash_image by gui
Sent from my HP touchpad using xda premium
jakkz said:
...or just go into the ROM Manager app and click on "Flash Clockworkmod Recovery", your version will update to 5 automatically.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
I had some issues doing it through rom manager. It was a no go so I flashed through bootloader.
I haven't checked if old backups are compatible yet. Anyone care to try and post?
Sent from my Nexus S 4G using XDA App
Every time I click on the update from inside ROM Manager, something terrible happens. I used think it was because I clicked on the link for the other Nexus S, but I was super duper careful this time.
If I try to reboot into recovery without being attached to my PC after flashing a new recovery in ROM Manager, I get stuck in fastboot. If I tell it to please boot me into recovery so can add a shiny new object to my Android, it tells me, "No ma'am." And, if im being honest, when I can't flash exciting new thingys on the go, existence begins to seem somewhat more futile. I'm sure you understand.
Might as well ask if there's a way I can fix it before I get home (in TEN HOURS) by fastbooting from a terminal or something. Okay, I'm begging.
p.s. I feel like I didn't get invited to most of Version 3 and all of Version 4.
Sent from my Nexus S 4G using xda premium
I had the same issue after using rom manager to flash 5. I just rebooted and tried flashing again from rom manager and it worked the second time
Sent from my Nexus S 4G using Tapatalk
jdkjgjjd said:
Might as well ask if there's a way I can fix it before I get home (in TEN HOURS) by fastbooting from a terminal or something. Okay, I'm begging.
p.s. I feel like I didn't get invited to most of Version 3 and all of Version 4.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Read the op. There is a reason why I gave instructions to flash through fastboot and not rom manager.
info[]box1 said:
Also there's a app in the app section that flashes img files quicker than you can blink.
Flash_image by gui
Sent from my HP touchpad using xda premium
Click to expand...
Click to collapse
This app worked great for me. Easy as 1,2,3
qbking77 said:
Backups on 4.x going tto restore properly on 5.x?
Great work by the way.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
I can confirm they do work.
Trying to upgrade from 4.0.0.2 to 5.0.0.0, I keep getting stuck on "Waiting for device"..
If on windows...your driver is bad.
Try flash_image gui by Joeykrim
Well here is the thing, I can push/pull things from the device, I can adb shell to the device.. Everytime I try flash the recovery, I get the waiting for device
Well if on Windows, fastboot driver needs to be there along with adb.driver. Two different things
Didnt work through rom manager, had to do it via fastboot. I dig the new color!
so rom manager updated my cwm to this one and when i go to reboot into recovery it goes into bootloader and which i chose recovery nothing happens .... first line says FASTBOOT - NO RECOVERY OR BOOT IMG
For anybody having flashing/ pushing/ just getting the new cwm recovery use the flash_image by GUI app located in the ns4g app section. I can't stress it enough, but it your trying to computer up to speed for Android development I understand.
Sent from my HP Touchpad using xda premium
I updated through ROM Manager and it worked just fine. I believe as long as you are running the latest version of ROM Manager you shouldn't have any issues.
I just used wugfresh to unlock bootloader and root my phone but when I tried to use rooted apps it said it couldn't find any root. I have superuser installed but nothing is rooted any help?
Sent from my Galaxy Nexus using XDA
vince7 said:
I just used wugfresh to unlock bootloader and root my phone but when I tried to use rooted apps it said it couldn't find any root. I have superuser installed but nothing is rooted any help?
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
Stop using Toolkits....
If you have a custom recovery you can download a SuperUser.zip and flash that.. this should give you what you want. Or you can download a Custom Rom and just flash that... problem solved you also dont have to go through the process of deleting the stock-recovery.sh that runs and kills your custom recovery.
I already fixed it but thanks for the reply and I should be not using tool kits thatsbfor sure but what do you mean about a custom recovery? How would I install that? So I would install the custom recovery then flash the su file and then flash a new from is this correct?
Sent from my Galaxy Nexus using xda premium
vince7 said:
I already fixed it but thanks for the reply and I should be not using tool kits thatsbfor sure but what do you mean about a custom recovery? How would I install that? So I would install the custom recovery then flash the su file and then flash a new from is this correct?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Had a look at Wugfresh thread, did you had it permanently flash cwm?
I don't think so actually
Sent from my Galaxy Nexus using xda premium
vince7 said:
I just used wugfresh to unlock bootloader and root my phone but when I tried to use rooted apps it said it couldn't find any root. I have superuser installed but nothing is rooted any help?
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
If you want to find out if your rooted check Play Movies. It will say ur appeared to be rooted and refuse service to the device.
The toolkit is amazing. I don't know why someone wouldn't recommend using it.
CWMR is a emergency thing in my opinion. It saves my butt countless amounts of time. U can flash it with Rom Manager, CWMR touch, and Rom Toolbox.
They are all available in the play store.
The toolkit isn't recommended because people don't learn things themselves. OP go superuser and see if things are given root or denied.
"Long is the way, and hard, that out of hell leads up to light."
DLD511 said:
CWMR is a emergency thing in my opinion. It saves my butt countless amounts of time. U can flash it with Rom Manager, CWMR touch, and Rom Toolbox.
They are all available in the play store.
Click to expand...
Click to collapse
Emergencies!!!
CWM is the most important tool in a crack flashers toolbox.
Flash it from rom manager he says, you can get it from play store...... kids these days.
Adb and fastboot. Research.
nodstuff said:
Emergencies!!!
CWM is the most important tool in a crack flashers toolbox.
Flash it from rom manager he says, you can get it from play store...... kids these days.
Adb and fastboot. Research.
Click to expand...
Click to collapse
I was just saying the simplest way on how to do it in my opinion.
And I don't use CWMR much. Only if something goes wrong.
Will there eventually be an app for unlocking the bootloader on the 10.3 firmware? I don't have the factory cable and it sounds like a lot of people have bricked their device doing the downgrade to 10.2.
I hope so. I am not gonna even try it... Lol instead rooted it and used Kindlefree app to install Nova and used titanium backup. So it's "like" Android but not quite lol....
Sent from my Nexus 4 using xda app-developers app
It worked for me even with the 10.3.1 bootloader. It seems that the exploit is not closed yet.
Sent from my A2109A using Tapatalk HD
I can confirm that the utilities still work fine with the latest version of the kindle software, so you shouldn't even need to downgrade.
flopower1996 said:
It worked for me even with the 10.3.1 bootloader. It seems that the exploit is not closed yet.
Sent from my A2109A using Tapatalk HD
Click to expand...
Click to collapse
But if I downgrade my bootloader I won't have to use the whole 2nd bootloader method and all that right? Won't I then just be able to use some utility to flash TWRP and then flash a ROM? This Kindle thing is probably a little more intimidating than anything else I've messed with. I have mine rooted and a bunch of other hacks but I want pure Android on. I don't want a brick though..
Sent from my Nexus 4 using xda app-developers app
---------- Post added at 01:58 PM ---------- Previous post was at 01:58 PM ----------
jwort93 said:
I can confirm that the utilities still work fine with the latest version of the kindle software, so you shouldn't even need to downgrade.
Click to expand...
Click to collapse
Which utility did you use and did you need a fastboot cable?
Sent from my Nexus 4 using xda app-developers app
You're going to need the second boot loader no matter what
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mindmajick said:
You're going to need the second boot loader no matter what
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Ok so if I use this http://forum.xda-developers.com/showthread.php?t=2216285 to downgrade my current bootloader then use this http://forum.xda-developers.com/showthread.php?t=2106463 to flash the freedom boot img and TWRP then I can just flash a ROM like normal through TWRP. Right?
Sent from my Nexus 4 using xda app-developers app
jcnbama said:
Ok so if I use this http://forum.xda-developers.com/showthread.php?t=2216285 to downgrade my current bootloader then use this http://forum.xda-developers.com/showthread.php?t=2106463 to flash the freedom boot img and TWRP then I can just flash a ROM like normal through TWRP. Right?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
No need to downgrade the bootloader. Install the apk from the dev. Thread and click install. Nothing else.
Sent from my A2109A using Tapatalk HD
flopower1996 said:
No need to downgrade the bootloader. Install the apk from the dev. Thread and click install. Nothing else.
Sent from my A2109A using Tapatalk HD
Click to expand...
Click to collapse
What about all that craziness I have been reading about locking up the bootloader due to the 10.3.1 bootloader? I can just forget about that and install that apk file and THEN I would be able to flash a ROM via TWRP? I thought that the thread said that this tool said it was for the old bootloader. This is great news! Can you confirm this? Are we on the same page?
Sent from my KFOT using xda app-developers app
jcnbama said:
What about all that craziness I have been reading about locking up the bootloader due to the 10.3.1 bootloader? I can just forget about that and install that apk file and THEN I would be able to flash a ROM via TWRP? I thought that the thread said that this tool said it was for the old bootloader. This is great news! Can you confirm this? Are we on the same page?
Sent from my KFOT using xda app-developers app
Click to expand...
Click to collapse
Yes the exploit stil exists. Tested by myself withe the 10.3.1 bootloader and confirmed by other people. Enjoy the freedom of flashing!
Sent from my A2109A using Tapatalk HD
flopower1996 said:
Yes the exploit stil exists. Tested by myself withe the 10.3.1 bootloader and confirmed by other people. Enjoy the freedom of flashing!
Sent from my A2109A using Tapatalk HD
Click to expand...
Click to collapse
Oh my goodness. This absolutely worked. WHY didn't I meet you like 3 days ago? LOL Any noob to Kindle should know about this. Root + Run a simple .apk WOW. Any thoughts on the best Rom going right now for KF2? Kernel?
jcnbama said:
Oh my goodness. This absolutely worked. WHY didn't I meet you like 3 days ago? LOL Any noob to Kindle should know about this. Root + Run a simple .apk WOW. Any thoughts on the best Rom going right now for KF2? Kernel?
Click to expand...
Click to collapse
Well, i personally use the aosp Rom by hashcode. It`s simple, nice and clean. But what you are using is your own choice. Flash different Roms and make your own mind.
Sent from my A2109A using Tapatalk HD
flopower1996 said:
Well, i personally use the aosp Rom by hashcode. It`s simple, nice and clean. But what you are using is your own choice. Flash different Roms and make your own mind.
Sent from my A2109A using Tapatalk HD
Click to expand...
Click to collapse
So, it looks like I have screwed something up. This figures as my luck is terrible with this freegin Kindle. So I got TWRP recovery working fine. I DL Cyanogenmod 10.1 and Gapps accordingly. Went into TWRP of course made a backup, then went to flash. I wiped EVERYTHING and went to flash the ROM. I received the error <Could Not Open .zip> So now I have nothing on file except a bad .zip. I did re-download the ROM assuming it was bad and restored my TWRP backup. Now I am stuck in what appears to be a Kindle Bootloop. The Kindle Fire (Orange) logo comes up, a few seconds later it blinks back off again and recycles. Now what? I can't get the Kindle to boot so I can put the .zip back on the machine. I am STUCK. This sucks... :crying:
jcnbama said:
So, it looks like I have screwed something up. This figures as my luck is terrible with this freegin Kindle. So I got TWRP recovery working fine. I DL Cyanogenmod 10.1 and Gapps accordingly. Went into TWRP of course made a backup, then went to flash. I wiped EVERYTHING and went to flash the ROM. I received the error <Could Not Open .zip> So now I have nothing on file except a bad .zip. I did re-download the ROM assuming it was bad and restored my TWRP backup. Now I am stuck in what appears to be a Kindle Bootloop. The Kindle Fire (Orange) logo comes up, a few seconds later it blinks back off again and recycles. Now what? I can't get the Kindle to boot so I can put the .zip back on the machine. I am STUCK. This sucks... :crying:
Click to expand...
Click to collapse
You have fastboot cable?
--
Sent from my mind to your screen.
mindmajick said:
You have fastboot cable?
--
Sent from my mind to your screen.
Click to expand...
Click to collapse
It's on the way lol. Ordered it today. What is terrible is I thought I was doing the right thing by doing a backup up TWRP. Just in case ya know? It *usually* works. Now I just need to know the next steps so I can get back where I need to be. Thought I was home free with TWRP.
Sent from my Nexus 4 using xda app-developers app
jcnbama said:
It's on the way lol. Ordered it today. What is terrible is I thought I was doing the right thing by doing a backup up TWRP. Just in case ya know? It *usually* works. Now I just need to know the next steps so I can get back where I need to be. Thought I was home free with TWRP.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I did the exact same thing when i got my kindle back in January. (Yeah, i had to order my cable right after that )
For some reason I've never been able to restore a stock TWRP backup on the kf2. It always borks the bootloader.
I know there is a special requirement that our bootloader uses a file called stack on the system partition- that's why you can't get into recovery now (when you wiped the system it wiped the stack file which let's us run the second bootloader.)
Anyway, Once you have the fastboot cable its really easy to get things going again. Pm me if you need a hand.. I've been through this myself a few times lol.
If you ever end up in the same situation again where you wiped the system and the zip is bad... Stay in twrp and use "adb sideload" to push a good zip from pc.
--
Sent from my mind to your screen.
mindmajick said:
I did the exact same thing when i got my kindle back in January. (Yeah, i had to order my cable right after that )
For some reason I've never been able to restore a stock TWRP backup on the kf2. It always borks the bootloader.
I know there is a special requirement that our bootloader uses a file called stack on the system partition- that's why you can't get into recovery now (when you wiped the system it wiped the stack file which let's us run the second bootloader.)
Anyway, Once you have the fastboot cable its really easy to get things going again. Pm me if you need a hand.. I've been through this myself a few times lol.
If you ever end up in the same situation again where you wiped the system and the zip is bad... Stay in twrp and use "adb sideload" to push a good zip from pc.
--
Sent from my mind to your screen.
Click to expand...
Click to collapse
I actually tried the side load through TWRP. When I typed "adb devices" it showed my device in host mode and the file wouldn't transfer although TWRP was in adb sideload mode. But then I just thought "oh well guess I'll restore my backup" lol. Yeah that didn't work out..
Sent you a P. M. BTW. thanks again!
Sent from my Nexus 4 using xda app-developers app
Thanks for the info guys. I'm glad I didn't have to change the firmware. The whole process was super easy and now I'm running jb 4.2. For those reading, just root->install one touch apk->make backup in twrp->factory reset->flash rom and gapps->success!
punkcitykid said:
Thanks for the info guys. I'm glad I didn't have to change the firmware. The whole process was super easy and now I'm running jb 4.2. For those reading, just root->install one touch apk->make backup in twrp->factory reset->flash rom and gapps->success!
Click to expand...
Click to collapse
**As a special note however DO NOT restore your factory backup if you have trouble. You will end up like me. Bootlooping with a fast boot cable in the mail.** if I could go back in time I would've downloaded the files via a hard line rather than slow wifi and maybe even double downloaded.. Oh well. This is a learning opportunity.
Sent from my Nexus 4 using xda app-developers app
Hello everybody.
I installed cm11 via cyanogenmod installer. When I was done with installing it, I installed Rom Manager application. The application then offered to install CWM Recovery, so I agreed to do so since I am more accustomed to it than TWRP.
Was working, until I the phone told me I had a new update.
The update downloads, and tries to install, but nothing happens ( or happens wrong so it just aborts), and I am left with the "there is an update for your phone".
So I figured out I might do it manually, so I went to Rom Manager and set TWRP to be default, and went to recovery.... and there was CWM.
I tried GooManager, TWRP Manager, all still reboot into CWM not TWRP.
I then tried CWM and it worked flashing the latest snapshot, but it had a serious bug, so I restored to the previous snapshot. ( Can't how that is relevant to the subject).
I really would like to install the TWRP and remove CWM. My question is: How do I remove CWM and install TWRP.
Thanks.
Just learn fastboot and manually flash TWRP image. If nothing goes wrong, TWRP will overwrite CWM as your only recovery.
Sent from Google Nexus 4 @ CM11
First download this app
https://play.google.com/store/apps/details?id=com.cgollner.flashify
Then, get your newest twrp img file (for toro is here: http://techerrata.com/file/twrp2/toro/openrecovery-twrp-2.7.0.0-toro.img
For maguro is here: http://techerrata.com/file/twrp2/maguro/openrecovery-twrp-2.7.0.0-maguro.img
Then open flashify, and install recovery img
Reboot recovery, presto magico
Goo has been messed up a while now
No Recovery!!
ashclepdia said:
First download this app
https://play.google.com/store/apps/details?id=com.cgollner.flashify
Then, get your newest twrp img file (for toro is here: http://techerrata.com/file/twrp2/toro/openrecovery-twrp-2.7.0.0-toro.img
For maguro is here: http://techerrata.com/file/twrp2/maguro/openrecovery-twrp-2.7.0.0-maguro.img
Then open flashify, and install recovery img
Reboot recovery, presto magico
Goo has been messed up a while now
Click to expand...
Click to collapse
I did as u said, but now I can't boot into recovery, and when in fastboot menu, it says I have no boot or recovery image.
But I can load into cm normally.
However what's weird is that it said the product code name was tuna, which is wrong, it should be maguro.
Any thoughts??
Mohdhamm said:
I did as u said, but now I can't boot into recovery, and when in fastboot menu, it says I have no boot or recovery image.
But I can load into cm normally.
However what's weird is that it said the product code name was tuna, which is wrong, it should be maguro.
Any thoughts??
Click to expand...
Click to collapse
Tuna is your phone. Tuna is Toro, Toro+ and maguro.. As said before learn how to use fastboot and flash it via fastboot. Plenty of guides.. Its really easy.
Sent from my Galaxy Nexus using XDA Premium HD app
Yea at this point you may need to use fastboot. If multiple tries of above haven't worked.
As said, it's REALLY easy.
You can use fastboot to clear recovery partition in case something is corrupted in it. And can just do a fastboot flash recovery recovery.img (where recovery.img is the path to recovery.img file you are installing. If you are cd'd into folder where recovery.img is located you can just use the name of the img file instead of the full path name to it.... it might sound confusing, but there are step by step fool proof guides to follow. And after you've done it once you'll be like "dang what was I worried about, this fastboot and adb stuff is easy" lol...)
Let us know if you need any clarification on the process
Thanks guys, but I have been really busy lately I couldn't learn fastboot, but I think I know how, since my first root was manual using such a command prompt.
I'll reply once I do it and report.
Thank you all very much.
Sent from my Galaxy Nexus using xda app-developers app
Mohdhamm said:
Thanks guys, but I have been really busy lately I couldn't learn fastboot, but I think I know how, since my first root was manual using such a command prompt.
I'll reply once I do it and report.
Thank you all very much.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
If you cant figure it out we will help! Good luck!
Sent from my Galaxy Nexus using xda app-developers app
Mohdhamm said:
Thanks guys, but I have been really busy lately I couldn't learn fastboot, but I think I know how, since my first root was manual using such a command prompt.
I'll reply once I do it and report.
Thank you all very much.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
mrgnex said:
If you cant figure it out we will help! Good luck!
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
agreed!
if you are unsure at all about any commands or setup, always happy to lend a helping hand.
much easier to help out with steps beforehand, rather than try to figure out where something went wrong afterwards
Hello
I managed to flash TWRP successfully and then tried to install cm update from the system update available.
However there was an error and it didn't work.
Here is the recovery log, it said something about not finding an md5.
Any thoughts as to what is happening here?
If you want a custom recovery and rom and you just unlocked your bootloader go here:
http://androidhosting.org/Devs/Dhacker29/msm8960/
Download and Flash:
XT901-XT907-TWRP-2.6.3.0-recovery.img
and
cm-11-20140615-UNOFFICIAL-RAZR-HD_M-KITKAT-TEST
and enjoy.
--
ERK
Any way to flash the recovery without a PC?
Sent from my XT907 using XDA Free mobile app
ezknives said:
Any way to flash the recovery without a PC?
Sent from my XT907 using XDA Free mobile app
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools
or
https://play.google.com/store/apps/details?id=com.cgollner.flashify
As always thank you kindly ATTACK...
Sent from my XT907 using XDA Free mobile app
Wich one of those did you use?
And did it work? Can we use rom manager?
Sent from my XT907 using XDA Free mobile app
The first one with twrp 2.7... Worked fine for me...
Sent from my XT907 using XDA Free mobile app
I can't seem to reboot into recovery correctly. Every attempt just lands me back in the stock firmware. Rebooting from there to recovery via adb just gives me the Motorola warning.
Strife89 said:
I can't seem to reboot into recovery correctly. Every attempt just lands me back in the stock firmware. Rebooting from there to recovery via adb just gives me the Motorola warning.
Click to expand...
Click to collapse
This is what I use
https://play.google.com/store/apps/details?id=com.siriusapplications.quickboot
ATTACK said:
This is what I use
https://play.google.com/store/apps/details?id=com.siriusapplications.quickboot
Click to expand...
Click to collapse
No dice. Rebooting to recovery even with that just leaves me staring at the boot image.
EDIT: I remember reading that those who took the KitKat OTA got a different boot image that makes going back to Jellybean difficult, if not impossible. Could that have anything to do with this?
Strife89 said:
No dice. Rebooting to recovery even with that just leaves me staring at the boot image.
EDIT: I remember reading that those who took the KitKat OTA got a different boot image that makes going back to Jellybean difficult, if not impossible. Could that have anything to do with this?
Click to expand...
Click to collapse
Which recovery are you flashing? It should read TWRP2710-RAZR_M-KITKAT.img.
ATTACK said:
Which recovery are you flashing? It should read TWRP2710-RAZR_M-KITKAT.img.
Click to expand...
Click to collapse
Bah, pay me no mind. I was trying to flash a CWM recovery because that's what I'm familiar with. I tried the one you just named and it works fine.
Sorry about that!
Just an FYI I couldn't get rashr to even look for the file so I tried flashify and it installed recovery with ease.
Thanks for the links attack. I don't like to try these flashing apks without a recommendation.
Sent from my XT907 using XDA Free mobile app
Strife89 said:
I can't seem to reboot into recovery correctly. Every attempt just lands me back in the stock firmware. Rebooting from there to recovery via adb just gives me the Motorola warning.
Click to expand...
Click to collapse
Are you Fastboot flashing?
Guys KEEP IN MIND:
These are not officials, these are fairly beta builds. You will get errors, I was hoping this would reach some crack-flashers.
That's basically who this is for.
ericerk said:
Guys KEEP IN MIND:
These are not officials, these are fairly beta builds. You will get errors, I was hoping this would reach some crack-flashers.
That's basically who this is for.
Click to expand...
Click to collapse
How can we get onto official CM then?
I know it has something to do with the kernel. We can't downgrade the kernel to the one CM is using? Or we have to wait until CM move up to kernel 3.4?
gtmaster303 said:
How can we get onto official CM then?
I know it has something to do with the kernel. We can't downgrade the kernel to the one CM is using? Or we have to wait until CM move up to kernel 3.4?
Click to expand...
Click to collapse
The latest Nightly is from February, which is 4.4.2.
Honestly keep checking that website, and check XDA.
Since the bootloader has been unlocked there should be a lot of movement / action in the dev section.
I would honestly not flash anything older, I mean feel free to mess around w/ kernel that are newer than 4.4.2 on CM.
I can't promise anything if you're on stock. I hope that helped at least a bit.
Didn't think this deserved its own thread, but could someone on 4.4.2 upload their systemui.apk real quick?
Sent from my One using XDA Premium 4 mobile app
Leraeniesh said:
Didn't think this deserved its own thread, but could someone on 4.4.2 upload their systemui.apk real quick?
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Odexed or Deodexed?
Here's a Deodexed SystemUI
I'm unable to boot official CM 11, yes i flashed it with TWRP2710-RAZR_M-KITKAT recovery i also try mokee 4.4.3 but same stuck on bootloader.
ericerk said:
Are you Fastboot flashing?
Click to expand...
Click to collapse
I was, but in the end I followed @ATTACK 's advice and used the apps from the Play Store. My impatience and forgetfulness caused me to butt my head against a metaphorical brick wall a few times, but I managed.