I'm trying to install [ROM][4.4.2 CM-11.0][Cyanogenmod 11.0 Unofficial][KOT49H][08/01/14].I have Unlocked bootloader with the Asus tool and i've installed rom manager and have CWM 5.8.3.4 (not touch) installed. I was looking for a specific CWM in OP's post, but didn't find any. Now, when i reboot into recovery, i see a text saying the device is unlocked, then it goes to the screen where the Android has the hood open and a red warning triangle above it. It stays like this for a couple of minutes, then i just reboots into stock JB. What am i doing wrong? BTW, don't have a dock, US pad...
EDIT: I fixed it with a fastboot installation
You fixed it? Intradesting, I had the same problem but then read here that CWM is no good, at least on the Prime, and fastboot-flashed TWRP instead.
This does work, however I cannot restore the Stock-ROM-Backup. Not sure whether this is TWRP's fault, though.
Quote from the CM11 Unofficial thread:
ebildude123 said:
You need the recovery he provided to flash this rom
http://forum.xda-developers.com/devdb/project/?id=2229#downloads
Sent from my TF300T on CM 11 (4.4.2) using Tapatalk 4
Click to expand...
Click to collapse
I think this is a modified version, but it works like a charm
Related
After I attempted to install the CM 11 preview that just came out it seems as though I get stuck in a boot loop. I am able to get into the bootloader but not the recovery. The reason I think I am stuck in the boot loop is because I did not know you had to flash the boot.img that was inside the .zip file, and went ahead and flashed the .zip in my current recovery. I am just wondering if I could still fastboot flash the boot.img file without causing even more problems.
Yes, in the forum the ROM was posted (http://forum.xda-developers.com/xperia-z2-tablet/orig-development/z2-tabletdevelopment-cm11-android-4-4-t2809793) but I guess I didn't see that he said it was in the zip :silly:.
Nonetheless, I just don't want to hard brick the device so that is why I am asking. Thanks in advance for anyone that can help!
cmd-line34 said:
After I attempted to install the CM 11 preview that just came out it seems as though I get stuck in a boot loop. I am able to get into the bootloader but not the recovery. The reason I think I am stuck in the boot loop is because I did not know you had to flash the boot.img that was inside the .zip file, and went ahead and flashed the .zip in my current recovery. I am just wondering if I could still fastboot flash the boot.img file without causing even more problems.
Yes, in the forum the ROM was posted (http://forum.xda-developers.com/xperia-z2-tablet/orig-development/z2-tabletdevelopment-cm11-android-4-4-t2809793) but I guess I didn't see that he said it was in the zip :silly:.
Nonetheless, I just don't want to hard brick the device so that is why I am asking. Thanks in advance for anyone that can help!
Click to expand...
Click to collapse
Just to clarify first, do you have a 4G tablet or wifi version? And which one did you flash (castor or castor_windy)
kbroh said:
Just to clarify first, do you have a 4G tablet or wifi version? And which one did you flash (castor or castor_windy)
Click to expand...
Click to collapse
Opps, meant to mention that. I have the castor_windy version (Wi-Fi) model and flashed the castor_windy zip. I also meant to mention that I have an unlocked bootloader with the CWM based recovery (found here: http://forum.xda-developers.com/showthread.php?t=2708194). I don't think this is as important but I do have the 16GB storage. I earlier said I could not get into that recovery that I have installed, but the violet light still goes on when I boot, but nothing else.
cmd-line34 said:
Opps, meant to mention that. I have the castor_windy version (Wi-Fi) model and flashed the castor_windy zip. I also meant to mention that I have an unlocked bootloader with the CWM based recovery (found here: http://forum.xda-developers.com/showthread.php?t=2708194). I don't think this is as important but I do have the 16GB storage. I earlier said I could not get into that recovery that I have installed, but the violet light still goes on when I boot, but nothing else.
Click to expand...
Click to collapse
Ok no problem, Have you tried flashing CWM through fastboot, then reinstalling ROM through CWM?
If that can't be done, Can you flash this castor_windy version https://mega.co.nz/#!mJ5VTATR!Rb9pX0a4drAkVX53Mjf6_vZr8FqX0UzXcf1nSTzj_Fk
through fastboot, then immediately flash CWM to secure a recovery.
The link is the castor_windy ROM without having to flash a boot.img separately. Thats your safest solution instead of flashing boot.img
Thank you, just re-flashing the recovery from the thread I linked seemed to do the trick. Maybe I will try and flash Cyanogenmod later now that I got the stock ROM working again. At least I was smart enough to make a nandroid backup in CWM before hand though!
Again, thanks alot!
cmd-line34 said:
Thank you, just re-flashing the recovery from the thread I linked seemed to do the trick. Maybe I will try and flash Cyanogenmod later now that I got the stock ROM working again. At least I was smart enough to make a nandroid backup in CWM before hand though!
Again, thanks alot!
Click to expand...
Click to collapse
Good to hear!
Sent from my Xperia Z2 Tablet Wifi using XDA Premium 4 mobile app
Hi all,
bad day for me... It seems that I bricked my Z2 Tablet tonight.
At the beginning, I just wanted to install CM11.
My Z2 is a SGP512 Wifi only. So, regarding the page http://www.xperiablog.net/2014/07/12/cyanogenmod-11-nightly-builds-start-for-xperia-z2-tablet/ , it says : "There are currently nightly builds for the Wi-Fi variants (SGP511, SGP512) of the Xperia Z2 Tablet under codename “Castor Windy”" .
So I downloaded Castor Windy and put it in the tablet.
After that, I did had to install a recovery. I succeeded to install XZDualRecovery (http://forum.xda-developers.com/showthread.php?t=2794175). Once installled, I went into TWRP Recovery , started to wipe all. And next step, I began to install zip Castor Windy. At this time, TWRP tells me that Castor Windy is not for my tablet model. And I have to use Castor. Problem. I wiped all. So, I have to mount the Tablet systems and drives to put the new Castor zip downloaded. But I'm unable to mount. Nothing is mounted. I tried to use adb to connect while I was in TWRP but nothing worked. I wanted to use adb to send on one of partitions the new downloaded rom. I was unable to do that.
Finally, I shut down my tablet. I took the SD Card to put it into my PC and to put on it the downloaded Rom. And when I wanted to restart the Tablet, only the Sony Logo appears and I'm not anymore able to enter in recovery mode. ADB and Fastboot fail to detect my tablet.
I'm totally lost, and I fear that all is lost.
Please, help me, I just would like to enter recovery and flash Castor Rom.... :crying:
Thanks a lot by advance.
Tom.
See this thread: http://forum.xda-developers.com/xpe...ed-tablet-tried-to-install-cm-failed-t2838765
Good luck :good:
I had little issue moving up to 4.0.4 so I don't have to worry about the EMMC erase bug, but I'm realizing I have no way to get up further.
Everything seems to require CWM or a version of TWRP that has no compatible kernels with 4.0.4 best I can do is Siydah and like 6.0.1.2 and looks like CWM but its rather sparse on the details.
Final edit, I found a much better solution.
It does not seem as though you can flash a upgraded kernel from the CWM interface itself and reboot reliably failed on multiple kernels.
Solution
Download mobile Odin
Download the 4.4 ROM of your choice (compatable)
Gapps too stick them all somewhere you can find them (i just leave em in downloads)
Download and flash CWM 6.0.4.4 for Kitkat i777.. no clue where I found it wasn't on XDA though.
Turn the phone off (if you reboot and don't reboot too recovery you get a loop)
Boot to recovery (if you get in a loop here pull the battery THEN boot to recovery)
Now you'll notice your not on your old version of CWM anymore.
Install your ROM and Gapps.
Boot to rom
Boot back to recovery Now your once again on a different version of CWM.
I strongly advise cleaning everything up and installing it again I had some issue until I did.
GL to anyone who finds this thread. If there seems to be a need I could rewrite it with a better title.
TheEgonSpengler said:
I had little issue moving up to 4.0.4 so I don't have to worry about the EMMC erase bug, but I'm realizing I have no way to get up further.
Everything seems to require CWM or a version of TWRP that has no compatible kernels with 4.0.4 best I can do is Siydah and like 6.0.1.2 and looks like CWM but its rather sparse on the details.
Final edit, I found a much better solution.
It does not seem as though you can flash a upgraded kernel from the CWM interface itself and reboot reliably failed on multiple kernels.
Solution
Download mobile Odin
Download the 4.4 ROM of your choice (compatable)
Gapps too stick them all somewhere you can find them (i just leave em in downloads)
Download and flash CWM 6.0.4.4 for Kitkat i777.. no clue where I found it wasn't on XDA though.
Turn the phone off (if you reboot and don't reboot too recovery you get a loop)
Boot to recovery (if you get in a loop here pull the battery THEN boot to recovery)
Now you'll notice your not on your old version of CWM anymore.
Install your ROM and Gapps.
Boot to rom
Boot back to recovery Now your once again on a different version of CWM.
I strongly advise cleaning everything up and installing it again I had some issue until I did.
GL to anyone who finds this thread. If there seems to be a need I could rewrite it with a better title.
Click to expand...
Click to collapse
Always remember that when you flash a ROM, that you typically get the Recovery that is tied to the Kernel contained in that ROM. So, you flashed the Kernel, got Recovery A, then you flashed the ROM and got Recovery B. A KK Kernel can be flashed independent of a KK ROM, and will add different/additional/improved functionality, depending on the dev, but it also contains it's own Recovery in most cases.
desteele said:
Always remember that when you flash a ROM, that you typically get the Recovery that is tied to the Kernel contained in that ROM. So, you flashed the Kernel, got Recovery A, then you flashed the ROM and got Recovery B. A KK Kernel can be flashed independent of a KK ROM, and will add different/additional/improved functionality, depending on the dev, but it also contains it's own Recovery in most cases.
Click to expand...
Click to collapse
"Everything seems to require CWM or a version of TWRP that has no compatible kernels with 4.0.4 best I can do is Siydah and like 6.0.1.2 and looks like CWM but its rather sparse on the details. "
Yes I know, thanks for the advice.
TheEgonSpengler said:
"Everything seems to require CWM or a version of TWRP that has no compatible kernels with 4.0.4 best I can do is Siydah and like 6.0.1.2 and looks like CWM but its rather sparse on the details. "
Yes I know, thanks for the advice.
Click to expand...
Click to collapse
Oh, sorry...sounded like you expected to find the latest recoveries on JB kernels. My bad.
desteele said:
Oh, sorry...sounded like you expected to find the latest recoveries on JB kernels. My bad.
Click to expand...
Click to collapse
Nah, you just can't install the latest ROM with an older recovery.
So if you want to go up you have to do the little dance I described above. (Yes I know certain walkthroughs indicate you can do the first step in recovery, I simply found that to not be true and gained me only bootloops and the joys of reflashing stock then reinstalling a updated-er version so I could try again.)
wil this work in my situation
Quick question.. am on:
android 4.1.2
Shostock v 3.0.2
my cwm v6.0.2.7.
I want to move for a slimmer kitkat rom..
Q&A for [RECOVERY] TWRP Recovery 2.8.1.0 - Thor
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY] TWRP Recovery 2.8.1.0 - Thor. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Tried it on 13.3.2.4 with know dice. You have to hard reset a couple of times and then safestrap comes back up. Tried a few times with zero luck so I just flashed twrp2.7.1 and all is good again. Also made me post here because I have less than 10 posts.
Kudos!
Firstly - thanks very much to all people involved in this - especially vortox - excellent work!
Secondly, I've just flashed TWRP successfully on 13.3.0.5.
The only thing which seems a bit strange is that when starting TWRP, I have to wait until the HDX's display goes into power-saving mode (i. e. goes deeply black) and switch the display on again before the starting screen of TWRP can be seen & TWRP be used (before that point, the display black for a while, but not in power-saving mode).
Is this normal?
I have made a grave error and have no recovery.
Well watching this special day unfold I mistakenly lost my original backup recovery.img and after dd now have no recovery. What can I do to get a working stock recovery.img back onto /dev/block/mmcblk0p18. When I dd twrp I apparently wasn't ready and now I have no recovery. I am running the rollback 13.3.0.9 and still have root/safestrap.
Nevermind I followed this and fixed my stock recovery.
http://forum.xda-developers.com/showthread.php?t=2782159&page=20
Certainly no expert here, but can't you just flash the TWRP recovery via Rashr or Flashify while the OS is running...? Or do you just want to have the stock recovery image? If I'm misunderstanding your question - sorry.
nocmonkee said:
Well watching this special day unfold I mistakenly lost my original backup recovery.img and after dd now have no recovery. What can I do to get a working stock recovery.img back onto /dev/block/mmcblk0p18. When I dd twrp I apparently wasn't ready and now I have no recovery. I am running the rollback 13.3.0.9 and still have root/safestrap.
Click to expand...
Click to collapse
RiseT said:
Certainly no expert here, but can't you just flash the TWRP recovery via Rashr or Flashify while the OS is running...? Or do you just want to have the stock recovery image? If I'm misunderstanding your question - sorry.
Click to expand...
Click to collapse
Sure but it never would boot into recovery or it was booting into an unexploitable recovery. I hadn't fully downgraded it yet or something went wrong so I had no usable recovery. I couldn't use amazon's tools to fix it and I could properly install twrp, so after "Amazon Recovery" worked again I was able to boot into the rollback image and use amazon's own upgrade bin. "update-kindle-13.3.1.0_user_310079820.bin". Once it went through the Amazon upgrade process. I used the KFHDX Toolkit to root it, then I adb'd into it and then su'd to root and immediately dd'd the TWRP recovery and then did reboot recovery in adb and "TADA" I had working twrp recovery and was able to install the CM 11 and gapps.
I see. Great to hear that it's working now. As you've successfully installed TWRP & CM 11 now - could you confirm the above stated behaviour regarding the black screen? Additionally to TWRP, I've just installed CM as well; interestingly, the display is showing the same behaviour with CM as with TWRP (I can only see something after the display returned from power-saving mode). With Amazon stock recovery & ROM, this isn't the case, so it shouldn't be a hardware problem.
nocmonkee said:
Sure but it never would boot recovery. I hadn't fully downgraded it yet or something went wrong so I had no recovery. After "Amazon Recovery" worked again I was about to boot into the rollback image and use amazon's own upgrade bin. "update-kindle-13.3.1.0_user_310079820.bin". Once it rebooted I used the KFHDX Toolkit to root it, then I adb'd into it and then su'd to root and immediately dd'd the TWRP recovery and then did reboot recovery in adb and "TADA" I had working twrp recovery and was able to install the CM 11 and gapps.
Click to expand...
Click to collapse
RiseT said:
I see. Great to hear that it's working now. As you've successfully installed TWRP & CM 11 now - could you confirm the above stated behaviour regarding the black screen? Additionally to TWRP, I've just installed CM as well; interestingly, the display is showing the same behaviour with CM as with TWRP (I can only see something after the display returned from power-saving mode). With Amazon stock recovery & ROM, this isn't the case, so it shouldn't be a hardware problem.
Click to expand...
Click to collapse
I am not experiencing this black screen issue. I did though start from 3.2.4 and worked my way down to 3.1.0. CM boots quickly and is super responsive. When booting it flashes the all gray "kindle fire" for about 10-20 seconds before it boots into recovery or cm. Possibly you just aren't see that screen and are seeing black instead?
Thanks for the feedback!
I think I don't see the gray "Kindle Fire" for that long - so that's a possibility. Btw, I also don't see the Cyanogenmod boot logo I'm used to on mobile phones. I guess I have to investigate this further. Wondering if the fact that I started with a rather "antique" stock firmware could have something to do with it, but I would guess that this is not possible as all that old stuff is wiped away when installing TWRP & the CM rom.
Edit: The gray "Kindle Fire" logo shows up for circa 4 seconds.
nocmonkee said:
I am not experiencing this black screen issue. I did though start from 3.2.4 and worked my way down to 3.1.0. CM boots quickly and is super responsive. When booting it flashes the all gray "kindle fire" for about 20 seconds before it boots into recovery or cm. Possibly you just aren't see that screen and are seeing black instead?
Click to expand...
Click to collapse
Thanks to everyone for their hard work bringing us TWRP for the Kindle HDX models.
vortox said:
It's not working on 3.2.4, but works atleast at 3.1.0. I didn't test other versions.
Click to expand...
Click to collapse
What's the best way to downgrade a rooted/safestrapped 13.3.2.4 stock-rom to a lower version?
well
Deathcrow said:
Thanks to everyone for their hard work bringing us TWRP for the Kindle HDX models.
What's the best way to downgrade a rooted/safestrapped 13.3.2.4 stock-rom to a lower version?
Click to expand...
Click to collapse
go back to development and start reading. To have somebody here we explain everything would just be ridiculous there is a thread or several threads on rolling back..from different versions to different versions I believe in development there is even a thread started now for exactly your question. And it was started yesterday or the day before.
jimyv said:
go back to development and start reading. To have somebody here we explain everything would just be ridiculous there is a thread or several threads on rolling back..from different versions to different versions I believe in development there is even a thread started now for exactly your question. And it was started yesterday or the day before.
Click to expand...
Click to collapse
Oh yeah, I completely missed that. Thanks for pointing it out.
if i install this twrp, what would happen to my safetrap recovery and can i even access it after and use the backups i saved using safetrap on twrp?
well
latedays101 said:
if i install this twrp, what would happen to my safetrap recovery and can i even access it after and use the backups i saved using safetrap on twrp?
Click to expand...
Click to collapse
yes you will still be able to access your safestrap. And yes your safestrap backups will be compatible with your new recovery. But keep in mind that your backups from safestrap will not contain a kernel and you will have to match one up with it..
jimyv said:
yes you will still be able to access your safestrap. And yes your safestrap backups will be compatible with your new recovery. But keep in mind that your backups from safestrap will not contain a kernel and you will have to match one up with it..
Click to expand...
Click to collapse
thanks, i just installed the twrp recovery successfully, how do i boot into safetrap again if i want to use it?
lol
latedays101 said:
thanks, i just installed the twrp recovery successfully, how do i boot into safetrap again if i want to use it?
Click to expand...
Click to collapse
it probably took you longer to ask me that question then it did for you to figure it out.
if not just simply reboot it and tap recovery on the splash screen as it boots just like always if you want access to it from your system just install the APK..personally I wouldn't mess with itother than to get into the backups from my new recovery to restore data....
jimyv said:
it probably took you longer to ask me that question then it did for you to figure it out.
if not just simply reboot it and tap recovery on the splash screen as it boots just like always if you want access to it from your system just install the APK..personally I wouldn't mess with itother than to get into the backups from my new recovery to restore data....
Click to expand...
Click to collapse
yeah i tried that but seems like its just boots into twrp not safetrap and thought something weird is happening and even if i tried installing the apk and press into recovery, it just boots into the cm rom.
well
latedays101 said:
yeah i tried that but seems like its just boots into twrp not safetrap and thought something weird is happening and even if i tried installing the apk and press into recovery, it just boots into the cm rom.
Click to expand...
Click to collapse
did you open up the app and see if the recovery is installed?. Like I said I would not mess with it personally. safestrap is a version of TRWP.. but is installed in the system and may have compatibility issues with your cm 11 etc other ROM that you may install with your new true recovery.
besides if you flash cm through your new recovery nothing you can install through safestrap at this moment would be compatible with the kernel ..besides a backup of that same rom. you would have left there. Unless you flash a renamed bin file to get compatible kernel for whatever stock backup you were trying to restore from safestrap
jimyv said:
did you open up the app and see if the recovery is installed?. Like I said I would not mess with it personally. safestrap is a version of TRWP.. but is installed in the system and may have compatibility issues with your cm 11 etc other ROM that you may install with your new true recovery.
besides if you flash cm through your new recovery nothing you can install through safestrap at this moment would be compatible with the kernel ..besides a backup of that same rom. you would have left there. Unless you flash a renamed bin file to get compatible kernel for whatever stock backup you were trying to restore from safestrap
Click to expand...
Click to collapse
Hm damn i just wanted to go back into safestrap so i can delete all my rom slots that i created that are wasted space seems like i kind of screwed right now for not backing the previous safetrap recovery i guess, unless someone share a back image of safetrap that i can flash?
well .
latedays101 said:
Hm damn i just wanted to go back into safestrap so i can delete all my rom slots that i created that are wasted space seems like i kind of screwed right now for not backing the previous safetrap recovery i guess, unless someone share a back image of safetrap that i can flash?
Click to expand...
Click to collapse
you were supposed to do that somewhere in the rolling back effort just before you do your new recovery. You were supposed to do it through a stock system and stock recovery to completely wipe the device.
you can still do it in your new recovery after you back your stuff up to your PC just go into wipe options and choose the option on the right wipe complete data.but that location of that folder is someplace I'm trying to find it for you
---------- Post added at 09:31 PM ---------- Previous post was at 09:23 PM ----------
jimyv said:
you were supposed to do that somewhere in the rolling back effort just before you do your new recovery. You were supposed to do it through a stock system and stock recovery to completely wipe the device.
you can still do it in your new recovery after you back your stuff up to your PC just go into wipe options and choose the option on the right wipe complete data.but that location of that folder is someplace I'm trying to find it for you
Click to expand...
Click to collapse
Try \mnt\shell\emulated\ then delete that folder named safestrap. That is where it is on my Apollo anyway
I workerd some days before and i dont know what happend.
I unlocked my bootloader and did pretty much everything. Ive installed cm12 and everything worked perfectly. Only thing that annoys me was the Cyanogenrecovery that forced me to flash twrp manually after every update.
The TWRP App says i got 2.8.4.0 installed. But i cant boot into it. The Led blinks pink and then it goes off and cm starts booting like nothing happend. I tried to reflash the recovery but it did not work.
Please help, i just want to update cm and install xposed
xan_asmodi said:
To gain a persistent recovery, one needs to flash a recovery to the fota partition as explained here: cant post twrp sirius link here bc xda spam prevent...
I figured that it was an error with Infected's CM12 nightlies. I flashed the latest boot.img and I was sorted.
Click to expand...
Click to collapse
this fixed it for me ^^
I just installed Paranoid Android latest version; had a custom recovery that was recommended (the same as when I had used cyanogenmod previously). "LockedDualRecovery" is the file I used. I am surprised to see I am unable to root the phone with sony mobile flasher (worked before). Towelroot opens a page that has huge text and I cannot press any buttons on it.
When I try to reboot into recovery mode (to install GAPPS) I get an orange light and the "SONY" screen permanently. Holding all the buttons can shut down the phone; and it will boot into PA just fine.
I am new with the rooting/roms, and this is an impass for me. I am not sure how I can do anything without recovery, or root access.
What the hell? You installed Paranoidandroid and your looking for rooting apps?
You obviously have an unlocked bootloader so if you don't have recovery just flash a cm kernal that has recovery and flash supersu through recovery. lol.
This is a pretty basic answer, did you search?
Sent from my D6503 using Tapatalk
o0 Matt 0o said:
What the hell? You installed Paranoidandroid and your looking for rooting apps?
You obviously have an unlocked bootloader so if you don't have recovery just flash a cm kernal that has recovery and flash supersu through recovery. lol.
This is a pretty basic answer, did you search?
Sent from my D6503 using Tapatalk
Click to expand...
Click to collapse
yes I did quite extensive searching; my ignorance is not answered by those searches. I did not know some installations include custom recoveries. When flashing PA it says "superSU is not installed, you should root it and install SU Swipe to do so" with twrp. Didn't work like this, and the GAPPS package I had installed did not work. I reflashed and saw a 'flashable' TWRP that I installed after PA and it worked fine.