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
Related
I created this thread because I have looked all over and have been unable to find someone with the exact same issue(s).
I said "sort of" in the title because twrp is working. Ok, so before everyone asks if I have nvflash, the answer is no. I did not have the right version of firmware, and did not try to install it originally. Since I was able to install roms, I figured I was fine...oops.
Twrp is not properly installing roms. More on that later. I am getting to the asus splash screen that says my device is unlocked, but it is stuck there.
My last working rom was the deodexed stock JB rom from craig gomez. I installed it with goo and when I installed that, I lost custom recovery and root, so I decided to go back to a more custom rom so Titanium backup would work. When I did that, I tried also tried again to make nvflash work. I got through the first step, it said it was successful, except I never got the little message in the upper left corner that I was supposed to get. I did not think it was a big deal because my prime would still boot like normal.
Then I installed twrp 2.3.1.0 and I have tried flashing previous restore images. I have tried installing the roms on my sdcard. I cannot get past the asus splash screen.
If I try installing a rom with the force md5 check enabled, it does detect an md5 and then quits.
If I try intalling a rom without the force md5 check, i get an error that says E:Unable to mount '/staging'
When I try installing a backup everything seems to work okay, but then I get the same error E:Unable to mount '/staging'
When I try to install roms through fastboot, I get the following errors:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
When I try using adb, I do not see any devices.
I tried putting CWM on the prime to see if I could install from that instead, but it would not load after install.
I tried putting an older version of twrp on the prime, to see if that was the issue because I used to have an older version...I could not get that to load either...so I went back to this version.
Any ideas or suggestions would be awesome guys. I am stuck.
I even went to install the naked drivers again, and when I try to flash a different recovery, I get the <waiting for device> text that never goes away.
i'm sort of on the same boat. my prime just keeps booting into twrp recovery no matter what i tried. i'm still hoping to find a solution to this problem.
godlyitem said:
i'm sort of on the same boat. my prime just keeps booting into twrp recovery no matter what i tried. i'm still hoping to find a solution to this problem.
Click to expand...
Click to collapse
For me, I can let it try to boot normally, but I get stuck at the splash screen. This device is unlocked.
If I hold down the volume down button, I can go to fastboot, or RCK for recovery...but it does not work properly.
big time noob said:
For me, I can let it try to boot normally, but I get stuck at the splash screen. This device is unlocked.
If I hold down the volume down button, I can go to fastboot, or RCK for recovery...but it does not work properly.
Click to expand...
Click to collapse
i just tried to flash cwm in the terminal, it wrote stuff on the memory, but didn't seem to do anything. it booted straight back to twrp. i can't even get it to go to fastboot!!! only if i can go to fastboot, i could save my prime!!!
godlyitem said:
i just tried to flash cwm in the terminal, it wrote stuff on the memory, but didn't seem to do anything. it booted straight back to twrp. i can't even get it to go to fastboot!!! only if i can go to fastboot, i could save my prime!!!
Click to expand...
Click to collapse
Yeah, I thought that too, but fastboot does not work properly either...argh. I wish one of the gurus would chime in here.
Same Here.. It all happened when i restored my files using titanium backup and when i rebooted im stuck at boot scrren
EDIT: Guys I did a prime fullwipe and flashed stock jb and now prime is restored to its original state..
""I also got some errors like md5 file could not be found and could not find the /staging""..but after the reboot it works perfect
EDIT 1: Now after the prime fullwipe and flashing stock jb i flashed twrp recovery and now it works perfect without a single error even the above mentioned errors were gone
mercydia said:
Same Here.. It all happened when i restored my files using titanium backup and when i rebooted im stuck at boot scrren
Click to expand...
Click to collapse
EVERYONE i fixed it!!!!!!!!!!!!!!!!!! !!!! it's alive again!!!!!!!!!!!!!!!!!
godlyitem said:
EVERYONE i fixed it!!!!!!!!!!!!!!!!!! !!!! it's alive again!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
That doesn't really help us. If possible, can you edit/delete your message so that the guys that might help do actually help? Don't want them to think this is done.
Can you clarify what the Prime fullwipe is and how you got there?
I do not know if it will help me.
I can't even do the wipe command from fastboot.
Just says <waiting for device>
I have tried the wipe command form the boot screen (the one with fastboot and RCK as options), that did not work properly either.
Ryan
mercydia said:
Same Here.. It all happened when i restored my files using titanium backup and when i rebooted im stuck at boot scrren
EDIT: Guys I did a prime fullwipe and flashed stock jb and now prime is restored to its original state..
""I also got some errors like md5 file could not be found and could not find the /staging""..but after the reboot it works perfect
EDIT 1: Now after the prime fullwipe and flashing stock jb i flashed twrp recovery and now it works perfect without a single error even the above mentioned errors were gone
Click to expand...
Click to collapse
big time noob said:
Can you clarify what the Prime fullwipe is and how you got there?
I do not know if it will help me.
I can't even do the wipe command from fastboot.
Just says <waiting for device>
I have tried the wipe command form the boot screen (the one with fastboot and RCK as options), that did not work properly either.
Ryan
Click to expand...
Click to collapse
here is what i did. get into twrp recovery. flashed full prime wipe -> right after that flash the stock jb US version directly dled from Asus -> reboot then you will be stuck at the splash screen (that's a good news). Hold down power + volume down until your prime turns off and restart (keep holding those two keys) until the 3 icons appear then flash w/e rom you want in recovery. It's alive!
In twrp I do not see anything that says Full Prime Wipe. I see something that says wipe. Are those the same? I tried doing a wipe from this screen, but it did not work for me as expected.
godlyitem said:
here is what i did. get into twrp recovery. flashed full prime wipe -> right after that flash the stock jb US version directly dled from Asus -> reboot then you will be stuck at the splash screen (that's a good news). Hold down power + volume down until your prime turns off and restart (keep holding those two keys) until the 3 icons appear then flash w/e rom you want in recovery. It's alive!
Click to expand...
Click to collapse
big time noob said:
In twrp I do not see anything that says Full Prime Wipe. I see something that says wipe. Are those the same? I tried doing a wipe from this screen, but it did not work for me as expected.
Click to expand...
Click to collapse
no full wipe is a stand alone zip file you have to google and find dl it. put it in your prime then flash it
Thanks. That is what I needed to know.
I will see if I can make this work when I get back from work.
godlyitem said:
no full wipe is a stand alone zip file you have to google and find dl it. put it in your prime then flash it
Click to expand...
Click to collapse
I am pretty sure I am F***ed.
I tried the prime full wipe. It worked the first time, I think. Then went to install a rom.
I had to do both through external SD in twrp because my adb is not working. Also, fastboot only works to install a recovery. The only version of any recovery I can make work is twrp 2.3.1.0
If I try an older version or CWM, it freezes where I try to go into recovery.
Unable to mount data error.
Unable to mount system error.
Same as before.
I tried using unbricker software I found, but since adb does not work properly, the software does not work properly.
I am going to see if I can work my charm and get them to take back my tablet at best buy for an infinity. I have read about other people pulling it off.
I think as we get closer to xmas my odds improve...UNLESS SOMEONE HAS ANOTHER IDEA??? I would love to try something else.
Eyeballer suggested a chat room channel thing, but most of the people are in europe and I would need to do it in the morning...I do not have time for that, but I may try it.
big time noob said:
Can you clarify what the Prime fullwipe is and how you got there?
I do not know if it will help me.
I can't even do the wipe command from fastboot.
Just says <waiting for device>
I have tried the wipe command form the boot screen (the one with fastboot and RCK as options), that did not work properly either.
Ryan
Click to expand...
Click to collapse
Download the zip:
http://goo.gl/hiFHB
Goto to Twrp recovery and install the zip..Since it supports microsd u can transfer the zip to microsd.
Goto TWRP -> INSTALL -> CHOOSE EXTERNAL SD -> INSTALL THE ZIP
It will completely wipe the internal storage and then download the official STOCK JB FROM ASUS SITE and follow the same steps to install. Now install the latest twrp recovery using fastboot
big time noob said:
I am pretty sure I am F***ed.
I tried the prime full wipe. It worked the first time, I think. Then went to install a rom.
I had to do both through external SD in twrp because my adb is not working. Also, fastboot only works to install a recovery. The only version of any recovery I can make work is twrp 2.3.1.0
If I try an older version or CWM, it freezes where I try to go into recovery.
Unable to mount data error.
Unable to mount system error.
Same as before.
I tried using unbricker software I found, but since adb does not work properly, the software does not work properly.
I am going to see if I can work my charm and get them to take back my tablet at best buy for an infinity. I have read about other people pulling it off.
I think as we get closer to xmas my odds improve...UNLESS SOMEONE HAS ANOTHER IDEA??? I would love to try something else.
Eyeballer suggested a chat room channel thing, but most of the people are in europe and I would need to do it in the morning...I do not have time for that, but I may try it.
Click to expand...
Click to collapse
When I was doing the fullwipe the same errors happened to me.. But dont mind..I got errors like
1. No md5 file found
2. Mount error
3. Cannot find /staging
Just follow the above the steps ull get it right
did you even follow my step by step guide? you can move the stock rom from external SD to your internal SD in advance -> file manager.
godlyitem said:
did you even follow my step by step guide? you can move the stock rom from external SD to your internal SD in advance -> file manager.
Click to expand...
Click to collapse
Yeah, I should have said I tried that first. I also tried the stock rom from asus. When that didn't work, I tried the stock rom deodexed I found in goo.
There are a bunch of permission errors going on inside my prime. When I go into the mount area, it will not let me mount the data to move it. Or, when I try to copy it over I get a failed message.
Okay. I wiped it again, from twrp.
Then it let me move the file from the ext-sdcard to the sdcard.
I used the prime full wipe.
Then I tried to install the stock rom by transferring it in twrp file manager.
I got the file onto the sdcard, but when i tried to install, it said Failed.
That was it.
I even tried installing the ICS version I got from ASUS. Same thing.
Now, I am going to try to access via unbricker...don't know if it will work, but I am out of ideas.
godlyitem said:
did you even follow my step by step guide? you can move the stock rom from external SD to your internal SD in advance -> file manager.
Click to expand...
Click to collapse
Fixed?
I am alive!
us-tf201-jro03c-10.4.2.15-stock-deodexed.zip
That is the last rom I successfully used.
I used all sorts of different wipes. I was in twrp and noticed my pc installing the transformer adb driver. So I hopped into adb to see if it would see my device with that driver. (it did, but it wasn't before from the fastboot or adb commands with naked driver).
I tried sideloading the above rom from twrp. It worked.
Thought others might want to know.
I do not know if I can install other roms or not. I am a little scared to try just yet.
big time noob said:
Okay. I wiped it again, from twrp.
Then it let me move the file from the ext-sdcard to the sdcard.
I used the prime full wipe.
Then I tried to install the stock rom by transferring it in twrp file manager.
I got the file onto the sdcard, but when i tried to install, it said Failed.
That was it.
I even tried installing the ICS version I got from ASUS. Same thing.
Now, I am going to try to access via unbricker...don't know if it will work, but I am out of ideas.
Click to expand...
Click to collapse
big time noob said:
I am alive!
us-tf201-jro03c-10.4.2.15-stock-deodexed.zip
That is the last rom I successfully used.
I used all sorts of different wipes. I was in twrp and noticed my pc installing the transformer adb driver. So I hopped into adb to see if it would see my device with that driver. (it did, but it wasn't before from the fastboot or adb commands with naked driver).
I tried sideloading the above rom from twrp. It worked.
Thought others might want to know.
I do not know if I can install other roms or not. I am a little scared to try just yet.
Click to expand...
Click to collapse
You will have the jelly bean bootloader now so as long as you stick to it you should be fine. The only other thing I would suggest is check you version of twrp, you should be running the jelly bean version of it also. And if I am not mistaken, you need to be on ics to use nvflash (although I haven't checked the op recently so I could be wrong) so definitely stay away from that unless you downgrade.
Hello! I'm new-ish here... As in I just opened an account to post after watching from the sidelines for a few months now.
Anyway,
I'm having problems with my phone. I was running ViperLTE 2.1.1 and recently switched to CyanogenMod. My sdcard wouldn't work correctly, so I tried to go back to stock, and my phone never made it past the "HTC" boot screen. I've tried reflashing and whatnot almost a dozen times, including restoring my nandroid backup, with no luck. Now I can't even access it via adb. What do I do?
Fastboot the stock boot image. The instructions are in the development section. Are you s off?
Sent from my Incredible 4G LTE using Tapatalk 2
MJL99 said:
Fastboot the stock boot image. The instructions are in the development section. Are you s off?
Sent from my Incredible 4G LTE using Tapatalk 2
Click to expand...
Click to collapse
I'm not s-off, and I have tried that multiple times, and at this point I can't get to adb or fastboot. I'm having trouble even accessing the bootloader.
EDIT: I got to the bootloader and adb/fastboot, but still flashing any boot image does nothing to fix the problem, and I'm still stuck at the htc screen.
19wolf said:
I'm not s-off, and I have tried that multiple times, and at this point I can't get to adb or fastboot. I'm having trouble even accessing the bootloader.
EDIT: I got to the bootloader and adb/fastboot, but still flashing any boot image does nothing to fix the problem, and I'm still stuck at the htc screen.
Click to expand...
Click to collapse
You are flashing the stock boot image right? From here for example.
Code:
fastboot flash boot boot.img
Are you installing a stock(-based) ROM or restoring a nandroid?
mdmower said:
You are flashing the stock boot image right? From [[Link removed because of new-user limits]] for example.
Code:
fastboot flash boot boot.img
Are you installing a stock(-based) ROM or restoring a nandroid?
Click to expand...
Click to collapse
Yeah. I'm repeatedly flashing the stock boot image and restarting, to no avail. According to the CyanogenMod forum, I need to install a stock-based ROM and then format my sdcard (to fix my initial problem)... and then restore my nandroid afterwards. At this point, it would be nice to just be able to restore the nandroid and have a phone that makes calls for a day-trip I'm going on tomorrow.
19wolf said:
Yeah. I'm repeatedly flashing the stock boot image and restarting, to no avail. According to the CyanogenMod forum, I need to install a stock-based ROM and then format my sdcard (to fix my initial problem)... and then restore my nandroid afterwards. At this point, it would be nice to just be able to restore the nandroid and have a phone that makes calls for a day-trip I'm going on tomorrow.
Click to expand...
Click to collapse
Just to check, after flashing the stock boot.img, you have installed a stock ROM or restored a stock-based ROM from a nandroid right (i.e. you're sure the backup is not from CyanogenMod)? The boot image alone isn't going to do anything. Also, depending on whether you were running Viper 1.x or 2.x, you need a different boot.img. The boot.img for Viper 1.x can be found here.
If restoring your nandroid backup doesn't work, freshly install Stock (or Viper).
mdmower said:
Just to check, after flashing the stock boot.img, you have installed a stock ROM or restored a stock-based ROM from a nandroid right (i.e. you're sure the backup is not from CyanogenMod)? The boot image alone isn't going to do anything. Also, depending on whether you were running Viper 1.x or 2.x, you need a different boot.img. The boot.img for Viper 1.x can be found here.
If restoring your nandroid backup doesn't work, freshly install Stock (or Viper).
Click to expand...
Click to collapse
I'll try that when I get to the computer, but do I need to use twrp or can I continue to use cwm? Also I can't access the sd card via my computer to put the rom onto it because it doesn't mount when I'm booted into recovery
19wolf said:
I'll try that when I get to the computer, but do I need to use twrp or can I continue to use cwm? Also I can't access the sd card via my computer to put the rom onto it because it doesn't mount when I'm booted into recovery
Click to expand...
Click to collapse
Either TWRP or CWM will work. There is a test version of CWM that enables USB mass storage support... but I haven't yet tested the feature under Windows.
I got it to work, via side-loading the zip and then flashing the boot.img. I don't know why I was having so many problems before... But they're better now. Thanks for your help
Hello im fairly new to the rooting stuff so bear with me and I hope im posting this in the right place. Iv looked for other post and most have people believe they have soft bricked there phone, I was able to get out of it
I have a Samsung galaxy s4 with Verizon
model # sch-i545,
android version 4.3,
baseband version i545vruemj7,
kernel version 3.4.0 [email protected] #1,
build # jss15j. i545vruemj7
Hope this is enough info for some help. I do have root using the chines root and terminal emulator to get supersu. I also use titanium backup pro. So here is where I have my problem I was wanting to have a recover backup just in case I messed up my phone. I looked up ways to do this and the one I picked was using goomanager.
1. Opened goomanager and opened the menu and clicked install openrecoveryscript
2. Download and installed and it said download complete
3. I rebooted my phone in recovery mode
4. Now it comes up in odin mode in the top left corner, it says in red could not do normal boot under that
product name: sch-i545,
current binary: Samsung official,
system states: custom,
knox kurnal lock:0x0,
knox warranty void: 0x0,
csb-config-lsb:0x30,
wright protection enabled,
eMAC burst mode enabled
5. And I have the big green droid with downloading… do not turn off target!!
6. This is where everyone else believes they soft bricked and are stuck in a bootloop but if you pull the battery and start up in odin and restart from there you get out of it
So I cant use recovery mode at all, is there any thing I can do to fix this or do I not get to use recovery ever again
Like I said I am new to rooting and all the great stuff it offers, I have rooted my old droid x2 and done a full recovery with it, I haven’t flashed a rom yet but I still don’t know all the in’s and out’s
Thank you for all the help
what it sounds like is you phone is going into download mode. when you are trying to enter recovery are you holding volume up or volume down when you boot? because volume down takes you to download mode and volume up take you to your recovery!
clapper66 said:
what it sounds like is you phone is going into download mode. when you are trying to enter recovery are you holding volume up or volume down when you boot? because volume down takes you to download mode and volume up take you to your recovery!
Click to expand...
Click to collapse
I hold the volume up, power and home keys and it goes in to odin mode and goomanager can boot into recovery mode and still goes into odin mode. I think goomanager doesn’t do the team win recovery and messed up the code for recovery
And thank you I double checked that and still odin mode comes up
first problem was using goo manager, your phone base does not support any custom recoveries. The only available option is safestrap after u obtain root
http://forum.xda-developers.com/showthread.php?t=2578569
Thank you again
decaturbob said:
first problem was using goo manager, your phone base does not support any custom recoveries. The only available option is safestrap after u obtain root
http://forum.xda-developers.com/showthread.php?t=2578569
Click to expand...
Click to collapse
Thanks for the help and sorry for the late reply, will this fix the recovery mode
noobjmac99 said:
Thanks for the help and sorry for the late reply, will this fix the recovery mode
Click to expand...
Click to collapse
What are you thinking "recovery mode" is?
safestrap enabled, Hyperdrive driven
decaturbob said:
What are you thinking "recovery mode" is?
safestrap enabled, Hyperdrive driven
Click to expand...
Click to collapse
What bugs me is that I can't get Into recovery anymore. *I have used recovery mode to re install some dumb apps by making a back up with Titanium Backup Pro And made a zip of the apps and re installed them through it. I just don't want to brick my phone hard. But please explain what it is and for.
All I wanted to do was be able to do a nandord backup which is what I thought I was trying todo.
noobjmac99 said:
What bugs me is that I can't get Into recovery anymore. *I have used recovery mode to re install some dumb apps by making a back up with Titanium Backup Pro And made a zip of the apps and re installed them through it. I just don't want to brick my phone hard. But please explain what it is and for.
All I wanted to do was be able to do a nandord backup which is what I thought I was trying todo.
Click to expand...
Click to collapse
You aren't making any sense, so you need to be a lot more specific about what you're doing.
One, you said above that you're on the MJ7 bootloader. That means that you can't have a custom recovery.
So what the heck does "using recovery mode to install some dumb apps by making a back up with Titanium Backup Pro" mean? You don't run Ti from recovery, you run it from a booted and rooted phone.
"All I wanted to do was to be able to make a nandord (sic) backup"
Oh well. You can't install a custom recovery on your phone since the bootloader is locked. This has been stated repeatedly in these forums.
Sadly, the moderators of this forum are refusing to post a sticky to help guide people like you to avoid this common mistake.
The only way you can back up your existing ROM is to root it and install Safestrap. Do a bit of searching around before flashing anything else.
noobjmac99 said:
What bugs me is that I can't get Into recovery anymore. *I have used recovery mode to re install some dumb apps by making a back up with Titanium Backup Pro And made a zip of the apps and re installed them through it. I just don't want to brick my phone hard. But please explain what it is and for.
All I wanted to do was be able to do a nandord backup which is what I thought I was trying todo.
Click to expand...
Click to collapse
So you are rooted...what recovery did you install? I'm still not clear in understanding your position.
safestrap enabled, Hyperdrive driven
k1mu said:
You aren't making any sense, so you need to be a lot more specific about what you're doing.
One, you said above that you're on the MJ7 bootloader. That means that you can't have a custom recovery.
So what the heck does "using recovery mode to install some dumb apps by making a back up with Titanium Backup Pro" mean? You don't run Ti from recovery, you run it from a booted and rooted phone.
"All I wanted to do was to be able to make a nandord (sic) backup"
Oh well. You can't install a custom recovery on your phone since the bootloader is locked. This has been stated repeatedly in these forums.
Sadly, the moderators of this forum are refusing to post a sticky to help guide people like you to avoid this common mistake.
The only way you can back up your existing ROM is to root it and install Safestrap. Do a bit of searching around before flashing anything else.
Click to expand...
Click to collapse
Im sorry im new to asking for help.
Yes I now know there is no custom recovery and found out the hard way and didn’t do enough research.
With Ti pro, in batch actions-All, section Recovery mode you can create “ update.zip” from apps and data backup. I know this is not a true recovery or nandorid, so I made the zip went into recovery mode and reinstalled the apps I deleted. I was just toying around with that
My original intent was to be able to do a nandorid backup
I have looked at the safestrap method and it looks like it will work for my build I just wanted to know since my recovery mode is corrupt or I believe it is will it work
thank you again for any help
decaturbob said:
So you are rooted...what recovery did you install? I'm still not clear in understanding your position.
safestrap enabled, Hyperdrive driven
Click to expand...
Click to collapse
yes i am rooted with the chinese root method and emulator now have supersu
the recovery i tried to install was team win recovery through goo manager which softbricked my phone after 30 minutes or so i finally got it out of the bootloop but now everything I try to go in to recovery it just loops
I have looked at the safestrap method and it looks like it will work for my build I just wanted to know since my recovery mode is corrupt or I believe it is will it work
thank you again for any help if there is anything else i need to proived please tell me
have the same problem :/
help please.
can't enter in recovery mode.
noobjmac99 said:
yes i am rooted with the chinese root method and emulator now have supersu
the recovery i tried to install was team win recovery through goo manager which softbricked my phone after 30 minutes or so i finally got it out of the bootloop but now everything I try to go in to recovery it just loops
I have looked at the safestrap method and it looks like it will work for my build I just wanted to know since my recovery mode is corrupt or I believe it is will it work
thank you again for any help if there is anything else i need to proived please tell me
Click to expand...
Click to collapse
read the sticky
http://forum.xda-developers.com/showthread.php?t=2606501
info there will tell you how you messed up and give you links on what you are suppose to do
safestrap says that installled correctly and i see installed on there but when i hit boot recovery it goes to lock screen and then boots normally. what did i do wrong? i have samsung galaxy s4 sgh-i337. is there another method where i can get it to boot to install the stocked root. i am on mk2 now and i am rooted
tmaddison93 said:
safestrap says that installled correctly and i see installed on there but when i hit boot recovery it goes to lock screen and then boots normally. what did i do wrong? i have samsung galaxy s4 sgh-i337. is there another method where i can get it to boot to install the stocked root. i am on mk2 now and i am rooted
Click to expand...
Click to collapse
This is a Verizon forum, and you have an AT&T phone. You may have better luck in the AT&T forums, especially since this is such an old thread.
What version of safestrap?
When you say "that installed correctly" do you mean safestrap recovery?
How did you try to enter recovery? Normally, you reboot, then press the "Recovery" button from the Safestrap splash screen. If you try the normal boot to recovery, it'll boot stock recovery, not Safestrap.
Hello everyone. I am new here. I have a samsung s4 verizon. It runned on android version 4.4.2. The hotspot was not working so i decide to root it and flash it with a new custom rom. Using odin i tried flashing it and it said failed. And now it can not boot into the recovery mode.It says when I tried to boot into recovery mode it says firmware upgrade encounter an issue. Please select recovery mode in kies and try again. I downloaded and installed kies but it not connecting in kies .
Please i need help asap
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:
Hi, I am new to the whole jailbreaking. I followed this video (hZyfWpBJpiE) to root the tablet (6 gb).
In this process, I used NT16or8gbV47SDimagefile and I set the tablet to factory setting, deleted partitions, and deleted dalvik cache. I may have repeated this process because i thought it wasnt rooted because my screen looked different from the video guys tablet
Then followed this video (GZAQpeCtFi0) to install CWM Recovery 4.0.4.8. It booted to the recovery setting screen but I started seeing green lines to the right of my screen then it shut off to restart.
It wouldnt respond when I tried it again so I repeated the first process and tried again but still, same thing happens.
Does anyone have ideas on how to fix this?
Ultimately, I want to install the CM11...
Thanks in Advance
I used the Root Recovery Tools to run the 4.0.4.8
PfanneKuchenAngriff said:
Hi, I am new to the whole jailbreaking. I followed this video (hZyfWpBJpiE) to root the tablet (6 gb).
In this process, I used NT16or8gbV47SDimagefile and I set the tablet to factory setting, deleted partitions, and deleted dalvik cache. I may have repeated this process because i thought it wasnt rooted because my screen looked different from the video guys tablet
Then followed this video (GZAQpeCtFi0) to install CWM Recovery 4.0.4.8. It booted to the recovery setting screen but I started seeing green lines to the right of my screen then it shut off to restart.
It wouldnt respond when I tried it again so I repeated the first process and tried again but still, same thing happens.
Does anyone have ideas on how to fix this?
...
Click to expand...
Click to collapse
You should not have deleted any partition. Also I am not aware of a CWM v4.0.4.8 for the Nook Tablet, are you sure you downloaded tools intended for the Nook Tablet?
I'd suggest that you try the recovery-to-stock method posted at http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/. See http://forum.xda-developers.com/showthread.php?t=2575489 for more info/pointers.
digixmax said:
You should not have deleted any partition. Also I am not aware of a CWM v4.0.4.8 for the Nook Tablet, are you sure you downloaded tools intended for the Nook Tablet?
I'd suggest that you try the recovery-to-stock method posted at http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/. See http://forum.xda-developers.com/showthread.php?t=2575489 for more info/pointers.
Click to expand...
Click to collapse
Thanks for your reply. I was able to get it back to factory setting but when following direction i get a message that says E: unable to mound /bootdata
I have no idea what is going on anymore
PfanneKuchenAngriff said:
Thanks for your reply. I was able to get it back to factory setting ...
Click to expand...
Click to collapse
Meaning you were able to get your NT back to running stock ROM?
but when following direction i get a message that says E: unable to mound /bootdata
...
Click to expand...
Click to collapse
Which direction are you referring to?
digixmax said:
Meaning you were able to get your NT back to running stock ROM?
Which direction are you referring to?
Click to expand...
Click to collapse
I was able to get back to running stock ROM. Then I followed the other linke ttp://forum.xda-developers.com/show....php?t=2575489
After I went through the directions, I got the unable to mount error
Which version of recovery did you use?
digixmax said:
Which version of recovery did you use?
Click to expand...
Click to collapse
I rooted the NT with: NT16or8gbV47SDimagefile.img
I used this version: flashable_CWM_6.0.4.8_chrmhoffmann
And I have these to install:
cm-11-20141102-NIGHTLY-acclaim
gapps-kk-20140606-signed
I think I tried 3 different ways to install it...do I need both TWRP and CMW recovery?
I read that TWRP was buggy and when it didn't work, I tried CMW recovery.
Right now, I have the NT back to rooted stated and nothing else. I followed this direction last, I think:
http://forum.xda-developers.com/showthread.php?t=2692403
The other video said I can use the root flasher app to run the CMW recovery so I tried that as well
Thanks
PfanneKuchenAngriff said:
I rooted the NT with: NT16or8gbV47SDimagefile.img
I used this version: flashable_CWM_6.0.4.8_chrmhoffmann
And I have these to install:
cm-11-20141102-NIGHTLY-acclaim
gapps-kk-20140606-signed
I think I tried 3 different ways to install it...do I need both TWRP and CMW recovery?
I read that TWRP was buggy and when it didn't work, I tried CMW recovery.
Right now, I have the NT back to rooted stated and nothing else. I followed this direction last, I think:
http://forum.xda-developers.com/showthread.php?t=2692403
The other video said I can use the root flasher app to run the CMW recovery so I tried that as well
Thanks
Click to expand...
Click to collapse
Since your NT is running (rooted) stock, you'd need SD-based recovery to flash CM/Gapps onto EMMC. Flashing CM11 requires CWM version later than 6.0.4.5 or TWRP version later than 2.6.3.0, unfortunately there does not seem to be any compilation of SD-based CWM versions 6.0.4.5 or later for the Nook Tablet, hence we are stuck with TWRP 2.6.3.0+ as the only SD-based recovery for flashing CM11 onto the NT. (The flashable_CWM_6.0.4.8_chrmhoffmann is for flashing CWM 6.0.4.8 onto your NT EMMC to replace the stock recovery; the root flasher app recovery is likely a too old recover version to be compatible with CM11).
A potential alternative course of action is to first flash CM10.x for which there are SD-based CWM recovery available (see http://forum.xda-developers.com/showpost.php?p=51377882&postcount=163), then upgrade from CM10.x to CM11 (see http://forum.xda-developers.com/showthread.php?t=2670589).
digixmax said:
Since your NT is running (rooted) stock, you'd need SD-based recovery to flash CM/Gapps onto EMMC. Flashing CM11 requires CWM version later than 6.0.4.5 or TWRP version later than 2.6.3.0, unfortunately there does not seem to be any compilation of SD-based CWM versions 6.0.4.5 or later for the Nook Tablet, hence we are stuck with TWRP 2.6.3.0+ as the only SD-based recovery for flashing CM11 onto the NT. (The flashable_CWM_6.0.4.8_chrmhoffmann is for flashing CWM 6.0.4.8 onto your NT EMMC to replace the stock recovery; the root flasher app recovery is likely a too old recover version to be compatible with CM11).
A potential alternative course of action is to first flash CM10.x for which there are SD-based CWM recovery available (see http://forum.xda-developers.com/showpost.php?p=51377882&postcount=163), then upgrade from CM10.x to CM11 (see http://forum.xda-developers.com/nook-hd/general/how-to-updating-hd-hd-internal-emmc-to-t2863171).
Click to expand...
Click to collapse
I think I was able to get through the first step in loading cm 10...
Is it normal for cyanoboot to show up before the cyanogenmod flash??
If normal, I will try to upgrade to cm11. This is a huge improvement though Thanks!
PS. the update from CM10x to CM11 seems to be only for HD or HD+...would this work with NT?
PfanneKuchenAngriff said:
I think I was able to get through the first step in loading cm 10...
Is it normal for cyanoboot to show up before the cyanogenmod flash??
Click to expand...
Click to collapse
Yes
PS. the update from CM10x to CM11 seems to be only for HD or HD+...would this work with NT?
Click to expand...
Click to collapse
Sorry, the correct URL for the NT CM10.x to CM11 update is http://forum.xda-developers.com/showthread.php?t=2670589.
digixmax said:
Yes
Sorry, the correct URL for the NT CM10.x to CM11 update is http://forum.xda-developers.com/showthread.php?t=2670589.
Click to expand...
Click to collapse
Thanks so much for all your help! For this step do I upload the files straight into the device (not the SD card)? Also, do i use the flashable_CWM_6.0.4.5_chrmhoffmann.zip or could I use the 6.0.4.8?
PfanneKuchenAngriff said:
Thanks so much for all your help! For this step do I upload the files straight into the device (not the SD card)?
Click to expand...
Click to collapse
Either way would work.
Also, do i use the flashable_CWM_6.0.4.5_chrmhoffmann.zip or could I use the 6.0.4.8?
Click to expand...
Click to collapse
Your choice.
FWIW I am using 6.0.4.8 on my NT (running CM11 snapshot M12).